diff --git a/marked/Q/T-REC-Q.107-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.107-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a739dd7bb4937677a53e6e4389d996583d341a7d --- /dev/null +++ b/marked/Q/T-REC-Q.107-198811-I_PDF-E/raw.md @@ -0,0 +1,333 @@ + + +![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** + +**Q.107** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**GENERAL RECOMMENDATIONS ON TELEPHONE +SWITCHING AND SIGNALLING** + +**CLAUSES APPLICABLE TO ITU-T STANDARD +SYSTEMS** + +--- + +**STANDARD SENDING SEQUENCE OF +FORWARD ADDRESS INFORMATION** + +**ITU-T Recommendation Q.107** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.107 was published in Fascicle VI.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. + +# **STANDARD SENDING SEQUENCE OF FORWARD ADDRESS INFORMATION** + +*(Geneva, 1980; modified at Melbourne, 1988)* + +A distinction is made in this Recommendation between the information to be sent by the telephone user for different types of calls and the corresponding information to be sent by the international signalling equipment. + +With regard to the latter, the sequence of forward address information signals is dealt with in detail. The detailed exchange of other signalling information is covered by the procedures described in the specifications of the CCITT signalling systems concerned. + +## **1 Information to be sent by the telephone user** + +The normal sequence of address information required for the set-up of an international call and to be sent by the user, i.e. the calling subscriber or operator, is as shown in Table 1/Q.107. This sequence does not depend on the CCITT signalling system used in the international network. Here five different types of call, from *a*) to *e*) are covered. + +TABLE 1/Q.107 + +### **Standard sequence of the address information to be sent by the telephone user** + +| Type | Call to : | Address information sent by the user | +|------------|---------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| a ) | A subscriber (automatic) | 1. International prefix a )
2. Country code b )
3. National (significant) number c ) | +| b ) | A subscriber (semi-automatic) | 1. Country code b ), d )
2. National (significant) number c )
3. Sending-finished | +| c ) | Any incoming or delay operator's position (semi-automatic) | 1. Country code b ), d )
2. Extra digit designating the incoming international exchange e )
3. Code 11 or code 12 f )
4. Sending-finished | +| d ) | An particular delay operator, or one of those operating a particular group of delay operator's positions (semi-automatic) | 1. Country code b ), d )
2. Extra digit designating the incoming international exchange e )
3. Code 12 f )
4. Number of a particular position or a group of positions
5. Sending-finished | +| e ) | An information operator or a special service operator | 1. Special numbers | + +a) The recommended international prefix is 00, see Recommendation Q. 11 *bis*, § 4.1. + +b) The country code consists of one these digit combinations: I1, I1 I2, I1 I2 I3. + +c) The national (significant) number consists of the subscriber number and the trunk code: N1, N2, N3.... It does not contain the national (trunk) prefix (the preferred national prefix is 0 - see Recommendation Q.11 *bis* § 4.5.2). The subscriber using the + +international automatic telephone network should be informed in an appropriate manner that the national prefix after the country code must not be sent. + +- d) If, in the case of semi-automatic calls, the language digit $L = 1, 2, 3, \dots$ is not sent automatically by the outgoing signalling equipment, it has to be sent by the operator to the outgoing equipment. In this case, the operator must send the $L$ digit immediately following the country code. +- e) The extra digit ( $N_1$ ) designating the incoming international exchange is used in cases where more than one incoming international exchange can be reached in the country of destination. (It is recognized that the existing design of some equipment does not permit the insertion of the extra digit.) +- f) See Recommendation Q.101. + +## 2 Sequence of forward address information to be sent by the outgoing international signalling equipment + +The information to be sent in the forward direction by the outgoing international signalling equipment in order to set up telephone connections differs from the information to be sent by the telephone user. The content and the sequence of forward address information is furthermore dependent on the signalling systems used in the international network. In the following, a distinction is made between common channel and channel associated signalling systems. + +### 2.1 Common channel signalling systems + +In the case of common channel Signalling Systems No. 6 and No. 7, the first signal to be sent to an (international) signalling data link relating to the set up of a telephone connection is the initial address message. According to the definitions in Recommendations Q.254 [1], Q.722 [2] and Q.762 [7], the initial address message normally contains, among others, the following forward address information: + +- a) nature-of-address indicator indicating that the + - international number, + - national (significant) number, or + - subscriber number is included; +- b) nature-of-circuit indicator indicating that + - a satellite circuit is included + - no satellite circuit is included; +- c) echo-suppressor indicator indicating that + - an outgoing half-echo suppressor is included + - no outgoing half-echo suppressor is included; +- d) calling-party's-category indicator including, among others, + - a language digit, $L$ + - the discriminating digit $D$ ; +- e) address signals + - country code + - national (significant) numbers + - code 11 + - code 12 + - end-of-pulsing (ST) signal or code 15. + +As the initial address message of Signalling Systems No. 6 and No. 7 carries at least the information mentioned above, it is not necessary to describe here in detail the sequence of the forward address information to be sent by the outgoing international signalling equipment; reference is made to Recommendations Q.258 [3], Q.723 [6] and Q.763 [8], instead. + +Nevertheless, the following additional comments are made: + +- a) In cases where the international call is routed + - from an originating international exchange (CT) to an international transit CT, or + - from one international transit CT to another international transit CT + +(i.e. for international transit calls) the appropriate nature-of-address indicator (international number - Signalling System No. 7) or country code indicator (country code included - Signalling System No. 6) will be used together with the country code. + +- b) If a terminal international link is selected; i.e. in cases where the call is routed + - from an originating CT direct to a destination CT, or + - from a transit CT to a destination CT + +the nature-of-address indicator [national (significant) number: Signalling System No. 7] or the country code indicator (country code not included: Signalling System No. 6) will be used. In this case, no country code has to be sent. + +In both cases a) and b) described above, further routing information will be included in the initial address message. For further details, see Recommendations Q.258 [3], Q.723 [6] and Q.763 [8]. + +### 2.2 *Channel associated signalling systems* + +For channel associated signalling systems, it is important to determine the first interregister signal and the sequence of forward address information. This matter is dealt with in the following, taking into account various types of calls and Signalling Systems No. 4, No. 5, R1 and R2. + +With the exception of the seizing signals in Signalling System No. 4, no line signals are dealt with. + +#### 2.2.1 *The first signals to be sent on international links* + +Table 2/Q.107 shows the first type of signal to be sent on four different types of international links in the case where channel associated signalling systems are used. + +TABLE 2/Q.107 + +###### First signal to be sent on international links + +| Type | International link | | First signal sent
on the international link | +|-----------|---------------------|---------------------|-------------------------------------------------------------| +| | from | to | | +| a) | Originating country | Designation country | Terminal-call indicator or discriminating or language digit | +| b) | Originating country | Transit country | Transit-call indicator | +| c) | Transit country | Transit country | Transit-call indicator | +| d) | Transit country | Destination country | Terminal-call indicator or discriminating or language digit | + +The terminal-call indicator is a type of signal indicating that an international terminal link *a)* or *d)* is involved and that no country code has to be sent to the incoming CT. In the case of Signalling System No. 4, the terminal-call indicator is represented by the terminal seizing signal - a forward line signal. For the other channel associated signalling systems, interregister signals are used. The discriminating digit D and the language digit L (both are also called the characteristic digit Z) must be in accordance with Recommendation Q.104. + +The transit-call indicator is a type of signal indicating that an international transit link *b)* or *c)* is involved and that the country code will be included in the signalling sequence. In the case of Signalling System No. 4, the transit-call indicator is represented by the transit seizing signal - a forward line signal. For the other channel associated signalling systems, interregister signals are used. + +#### 2.2.2 *Sequence of forward address information for automatic and semi-automatic calls to a subscriber* + +The forward address information to be sent by the outgoing international signalling equipment differs from the information sent by the telephone user as described in § 1. + +Details covering the different channel associated CCITT signalling systems are shown in Table 3/Q.107. + +#### 2.2.3 *Sequence of forward address information for calls to any incoming or delay operator's position* + +Table 4/Q.107 shows in detail the standard sequence of forward address information for calls to any incoming or delay operator's position to be sent by the outgoing international signalling equipment. A distinction is made between international transit and terminal calls as well as between different channel associated CCITT signalling systems. + +TABLE 3/Q.107 + +#### **Sequence of forward address information for automatic and semi-automatic calls to a subscriber to be sent by the outgoing international signalling equipment** + +| Channel associated CCITT signalling system | | No. 4 | No. 5 | R2 | R1 a) | +|--------------------------------------------|------------------------------------|---------------------------------------------------------------------------------------------------------|-------|------------------------------------------|------------------| +| sending sequence | International transit call | Transit seizing b) | KP 2 | I-12 or
I-14 or
I-11 c) | — | +| | Echo-suppressor indicator | — d) | — | | — | +| | Nature-of-circuit indicator | — | — | I-13 or I-14 e) | — | +| | Country code | I 1 I 1 I 2 I 1 I 2 I 3 f) | | | — | +| | Calling-party's-category indicator | D = 0 or L = 1, 2, 3, ... | | | — | +| | National (significant) number | N 1 N 2 N 3 ... | | | — | +| | Sending-finished | Code 15 | ST | Code 15 | — | +| International terminal call | Terminal-call indicator | Terminal seizing b) | KP 1 | | KP h) | +| | Calling-party's-category indicator | D = 0 or L = 1, 2, 3 ... g) | | | — | +| | Echo-suppressor indicator | — d) | — | 1-14 e) | — | +| | Nature-of-circuit indicator | — | — | 1-13 or 1-14 e) | — | +| | National (significant) number | N 1 N 2 N 3 ... | | | — | +| | Sending-finished | Code 15 | ST | Code 15 | — | + +a) Signalling system R1 is not used for international transit calls. + +b) For Signalling System No.4, the transit and the terminal-call indicators are represented by line signals. For the other signalling systems, no line signals are shown. + +c) The use of signal I-11 in international working is subject to bilateral agreements. + +d) Code 14 can be used for echo-suppressor control to bilateral or multilateral agreements. + +e) These signals are sent on request. + +f) See Recommendation Q.101. + +g) For Signalling System R2, the L digit is also used as terminal-call indicator. + +h) The KP signal is only used to prepare the incoming signalling equipment for the reception of the subsequent interregister signals; see also footnote a) above. + +TABLE 4/Q.107 + +#### Sequence of forward address information for calls to any incoming or delay operators' position + +| Channel associated CCITT signalling system | | No. 4 | No. 5 | R2 | R1 a) | +|--------------------------------------------|-----------------------------------------------|-----------------------------------------------------------------------------------------------|-------|------------------------------------------|---------------------| +| Sending sequence | International transit call | Transit seizing b) | KP 2 | I-12 or
I-14 or
I-11 c) | — | +| | Echo-suppressor indicator | — d) | — | | — | +| | Nature-of-circuit indicator | — | — | I-13 or I-14 e) | — | +| | Country code | I 1 , I 1 I 2 , I 1 I 2 I 3 | | | — | +| | Language digit | L = 1, 2, 3, ... | | | — | +| | Extra digit designating the incoming exchange | N 1 | | | — | +| | Access to operator's position | Code 11 or code 12 f) | | | — | +| | Sending-finished | Code 15 | ST | Code 15 | — | +| International terminal call | Terminal-call indicator | Terminal seizing b) | KP 1 | | KP h) | +| | Language digit | L = 1, 2, 3, ... g) | | | — | +| | Echo-suppressor indicator | — d) | — | 1-14 e) | — | +| | Nature-of-circuit indicator | — | — | 1-13 or 1-14 e) | — | +| | Extra digit designating the incoming exchange | N 1 | | | — | +| | Access to operator's position | Code 11 or code 12 f) | | | e.g. 121
or 1150 | +| | Sending-finished | Code 15 | ST | Code 15 | ST | + +a) Signalling System R1 is not used for international transit calls. + +b) For Signalling System No.4, the transit and the terminal-call indicators are represented by line signals. For the other signalling systems, no line signals are shown. + +c) The use of signal I-11 in international working is subject to bilateral agreements. + +d) Code 14 can be used for echo-suppressor control subject to bilateral or multilateral agreements. + +e) These signals are sent on request. + +f) See Recommendation Q.101. + +g) For Signalling System R2, The L digit is also used as terminal-call indicator. + +h) The KP signal is only used to prepare the incoming signalling equipment for the reception of the subsequent interregister signals; see also Note a). + +##### 2.2.4 Sequence of forward address information for calls to a particular delay operator + +The standard sequence of forward address information for calls to a particular delay operator or one of those operating a particular group of delay operator's position is shown in detail in Table 5/Q.107. Again a distinction is made between international transit and terminal calls as well as between different channel associated CCITT signalling systems. + +The footnotes relating to Table 4/Q.107 are also valid for Table 5/Q.107. + +## **3 Standard sending sequence of forward address information in the case of calls to testing and measuring devices** + +International calls to testing and measuring devices are terminal calls. Therefore, the outgoing signalling equipment will not send the country code. In Signalling System No. 4, the terminal-call indicator is a line signal. + +Table 6/Q.107 contains the standard sending sequence and forward address information in the case of calls to testing and measuring devices to be sent by the outgoing signalling equipment for Signalling Systems No. 4, No. 5, No. 6, No. 7, R1 and R2. + +Recommendation O.11 [4] contains the detailed specifications for CCITT manual maintenance access lines. Recommendation O.22 [5] contains the detailed specifications for the CCITT ATME No. 2. Further information with regard to calls to testing and measuring devices can be found in the detailed specifications of the relevant CCITT signalling systems. + +In the case of the common channel Signalling Systems No. 6 and No.7, all information will be carried by means of an initial address message in which the message indicators will be set to their appropriate values as specified in Recommendations Q.258 [3], Q.723 [6] and Q.763 [8]. + +In Table 7/Q.107 the access codes required to reach the testing and measuring devices in the exchange of destination are given for CCITT Signalling Systems No. 4, No. 5, No. 6, No. 7 and R2. + +TABLE 5/Q.107 + +### Sequence of forward address for calls to a particular delay operator's position + +| Channel associated CCITT signalling system | | No. 4 | No. 5 | R2 | R1 a) | +|------------------------------------------------|-----------------------------------------|-----------------------------------------------------------------------------------------------|-------|------------------------------------------|--------------------------------------| +| Sending sequence
International transit call | Transit-call indicator | Transit seizing b) | KP 2 | I-12 or
I-14 or
I-11 c) | — | +| | Echo-suppressor indicator | — d) | — | | — | +| | Nature-of-circuit indicator | — | — | I-13 or I-14 e) | — | +| | Country code | I 1 , I 1 I 2 , I 1 I 2 I 3 | | | — | +| | Language digit | L = 1, 2, 3, ... | | | — | +| | Extra digit designating the incoming CT | N 1 | | | — | +| | Access to operator's position | Code 12 | | | — | +| | Number of a particular position | x 1 (x 2 x 3 ...) | | | — | +| | Sending-finished | Code 15 | ST | Code 15 | — | +| International terminal call | Terminal-call indicator | Terminal seizing b) | KP 1 | | KP g) | +| | Language digit | L = 1, 2, 3, ... f) | | | — | +| | Echo-suppressor indicator | — d) | — | 1-14 e) | — | +| | Nature-of-circuit indicator | — | — | 1-13 or 1-14 e) | — | +| | Extra digit designating the incoming CT | N 1 | | | — | +| | Access to operator's position | Code 12 | | | e.g. 1150 | +| | Number of a particular position | x 1 (x 2 x 3 ...) | | | e.g. 11x 1 x 2 | +| | Sending-finished | Code 15 | ST | Code 15 | ST | + +a) Signalling System R1 is not used for international transit calls. + +b) For Signalling System No.4, the transit and the terminal-call indicators are represented by line signals. For the other signalling systems, no line signals are shown. + +c) The use of signal I-11 in international working is subject to bilateral agreements. + +d) Code 14 can be used for echo-suppressor control subject to bilateral or multilateral agreements. + +e) These signals are sent on request. + +f) For Signalling System R2, the L digit is also used as terminal-call indicator. + +g) The KP signal is only used to prepare the incoming signalling equipment for the reception of the subsequent interregister signals; see also Note a). + +TABLE 6/Q.107 + +### **Sending sequence of forward address information in the case of calls to testing and measuring devices** + +| CCITT signalling system | No. 4 | No. 5 | No. 6 | No. 7 | R2 | R1 | +|----------------------------------------------------------|----------------------------|----------------------------|----------------------------------------|---------------|---------------------------|------------------------------------------| +| Terminal-call indicator | Terminal seizing | KP 1 | Together with other message indicators | | | KP | +| Calling party's category indicator | D = code 13 | D = 7 | Test call | Test call | D = code 13 a) | — | +| Test-call indicator | Code 12 | Code 12 | — | — | Code 13 | — | +| Access code for a particular testing or measuring device | Digit 0 plus 2 digits x, y | Digit 0 plus 2 digits x, y | 16 combinations | 2 digits x, y | 2 digits x, y | Digits to be agreed upon (minimum three) | +| Sending-finished | Code 15 | ST | ST | ST | Code 15 | ST | + +a) For signalling System R2, the D digit is also used as terminal-call indicator. + +TABLE 7/Q.107 + +#### **Access codes for a particular testing or measuring device** + +| CCITT signalling system | Access codes | | | | | +|---------------------------------------------------------------|--------------|-------|-------|-------------|-------| +| | No. 4 | No. 5 | R2 | No. 6 | No. 7 | +| Multiple address capability for transmission access test line | 21-29 | 21-29 | 21-29 | 6
7
8 | 21-29 | +| ATME 2 Type a | 61 | 61 | 61 | 1 | 61 | +| ATME 2 Type b | 62 | 62 | 62 | 2 | 62 | +| ATME 2 Type c | 63 | 63 | — | — | 63 | +| Quiet termination | 64 | 64 | 64 | 3 | 64 | +| Echo suppressor test | 65 | 65 | 65 | 4 | 65 | +| Loop around | 66 | 66 | 66 | 5 | 66 | +| Echo canceller test | 67 | 67 | 67 | 9 | 67 | +| Loop back test line | 68 | 68 | 68 | 10 | 68 | +| Simplified test | — | — | 90 | — | — | +| Good/no good transmission Test | 00 | — | 00 | — | — | +| Continuity check | — | — | — | 0 | 00 | + +# References + +- [1] CCITT Recommendation *Telephone signals*, Vol. VI, Fascicle VI.3, Rec. Q.254. +- [2] CCITT Recommendation *General function of telephone messages and signals*, Vol. VI, Fascicle VI.8, Rec. Q.722. +- [3] CCITT Recommendation *Telephone signals*, Vol. VI, Fascicle VI.3, Rec. Q.258. +- [4] CCITT Recommendation *Specifications for manual maintenance access lines*, Vol. IV, Fascicle IV.4, Rec. O.11. +- [5] CCITT Recommendation *CCITT automatic transmission measuring and signalling testing equipment (ATME No. 2)*, Vol. IV, Fascicle IV.4, Rec. O.22. +- [6] CCITT Recommendations, *Formats and codes*, Vol. VI, Fascicle VI.8, Rec. Q.723. +- [7] CCITT Recommendations, *General function of messages and signals*, Vol VI, Fascicle VI.8, Rec. Q.762. +- [8] CCITT Recommendations, *Formats and codes*, Vol. VI, Fascicle VI.8, Rec. Q.763. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.108-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.108-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..807b547a5cfee797acddf35ec4f876702c8c2a1d --- /dev/null +++ b/marked/Q/T-REC-Q.108-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** + +**Q.108** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**GENERAL RECOMMENDATIONS ON TELEPHONE +SWITCHING AND SIGNALLING** + +**CLAUSES APPLICABLE TO ITU-T STANDARD +SYSTEMS** + +--- + +**ONE-WAY OR BOTH-WAY OPERATION OF +INTERNATIONAL CIRCUITS** + +**ITU-T Recommendation Q.108** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.108 was published in Fascicle VI.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. + +## **1.8 ONE-WAY OR BOTH-WAY OPERATION OF INTERNATIONAL CIRCUITS** + +### **1.8.1 *One-way operation*** + +In order to have as simple as possible equipment in international exchanges and to avoid double seizures, System No. 4 has been designed in 1949-1954 for one-way operation of international circuits in semi-automatic and automatic working. + +### **1.8.2 *Both-way operation*** + +1.8.2.1 These advantages of one-way operation naturally hold good in the case of long international (intercontinental) circuits. However, for these circuits the following considerations have been determining factors in providing both-way circuit operation: + +- a) When a group of circuits is composed of a small number of circuits, the increase in efficiency due to both-way operation is obviously very important. Moreover, long international (intercontinental) circuits are very costly. Finally, the increase in the cost of terminal equipment which results from both-way operation is small compared with the considerable economic advantage derived from this mode of operation. +- b) The two ends of a long international (intercontinental) group of circuits may belong to two time zones which are very far apart and, depending on the difference in time, this is likely to result in important and variable differences between the traffic in the two directions. + +1.8.2.2 All circuits in System No. 5 and the speech circuits in Systems No. 6 and 7 should be equipped to work in both-way operation. Nevertheless, the both-way method of operation would be applied only if it offered a considerable economic advantage. Hence in the case of large groups (for example, more than 40 circuits in each direction), the possibility of maintaining one-way operation might be considered, because of the extra reliability of this type of operation. If, in circumstances necessitating the use of large groups, there are great differences between the busy hours at each end, it would be advisable, if it were desired to maintain one-way operation, to arrange that the circuits be used successively in one or the other direction according to the time of day. This availability of the circuits for routing traffic from country A to country B or vice versa would be arranged by a convenient method. + +In certain cases another solution is worthy of consideration. This consists of setting up three groups of circuits, two operated one-way and the third both-way, it being understood that the latter would be used as an overflow route for calls which could not be routed on the first two groups. + +1.8.2.3 Attention is drawn to the conditions which should be introduced to avoid double seizing and false blocking on both-way international circuits. In addition, attention is drawn to the fact that in semi-automatic working, as in automatic working, access to the circuits at both ends should be automatic. + +In semi-automatic operation, in the event of double seizing, automatic selection of a new circuit should be preferred to the operator's setting up the call again, so that the operator does not become aware of the double seizing. In automatic operation, automatic selection of a new circuit should naturally be the rule. + +The necessary arrangements have been made in the specifications of the systems concerning simultaneous seizing in both-way operation. + +1.8.2.4 The digital circuits in System R2 and the circuits in System R1 may be equipped to work in both-way operation. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1100-199303-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1100-199303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0a40c1f3a5ca265256945019dfe34e875ee62e08 --- /dev/null +++ b/marked/Q/T-REC-Q.1100-199303-I_PDF-E/raw.md @@ -0,0 +1,132 @@ + + +![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** + +**Q.1100** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(03/93) + +**INTERWORKING WITH SATELLITE +MOBILE SYSTEMS** + +--- + +**INTERWORKING WITH STANDARD A +INMARSAT SYSTEM – STRUCTURE OF THE +RECOMMENDATIONS ON THE INMARSAT +MOBILE SATELLITE SYSTEMS** + +**ITU-T Recommendation Q.1100** + +(Previously "CCITT Recommendation") + +--- + +# FOREWORD + +The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecommunication Union. 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, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +ITU-T Recommendation Q.1100 was revised by the ITU-T Study Group XI (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993). + +# --- NOTES + +1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector. + +In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms "CCITT, CCIR or IFRB" or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure. + +2 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 Terminology ..... | 1 | +| 3 Overview of Recommendations ..... | 2 | +| 3.1 Recommendation Q.1101 ..... | 2 | +| 3.2 Recommendation Q.1102 ..... | 2 | +| 3.3 Recommendation Q.1103 ..... | 2 | +| 3.4 Recommendation Q.1111 ..... | 2 | +| 3.5 Recommendation Q.1112 ..... | 2 | +| 3.6 Recommendation Q.1151 ..... | 2 | +| 3.7 Recommendation Q.1152 ..... | 2 | + + + +# INTERWORKING WITH STANDARD A INMARSAT SYSTEM – STRUCTURE OF THE RECOMMENDATIONS ON THE INMARSAT MOBILE SATELLITE SYSTEMS + +(Melbourne, 1988, modified at Helsinki, 1993) + +# 1 General + +This Recommendation gives an overview of those in the Q.1100-Series for interworking between the international public switched telephone network/ISDN and the INMARSAT mobile satellite systems. It also contains definitions of the terminology used in these Recommendations. + +The interworking of all INMARSAT standard systems with the PSTN/ISDN is based on a common set of principles. However, due to the differences between the various INMARSAT standard signalling systems, the specific interworking procedures for each particular INMARSAT standard system is unique. + +# 2 Terminology + +For the purpose of this Recommendation, the following definitions apply: + +**2.1 aeronautical (ground) earth station (GES):** An earth station in the fixed-satellite service or, in some cases, in the aeronautical mobile-satellite service, located at a specified fixed point on land to provide a feeder link for the aeronautical mobile-satellite service (see *Radio Regulations*, Article 1). + +**2.2 aircraft earth station (AES):** A mobile earth station in the aeronautical mobile-satellite service located on board an aircraft (see *Radio Regulations*, Article 1). + +**2.3 mobile satellite switching centre (MSSC):** Indicates the signalling interworking point between the fixed networks and the mobile satellite system which works to a single ocean area. The MSSC may be located at the antenna site of the aeronautical ground earth station or coast earth station, in which case it may operate as an independent international switching centre (ISC) connected to one or more ISCs, on national switching centres. It may also be located remotely from the antenna site, as a supplement to, or a part of an ISC. The term MSSC may also indicate a maritime satellite switching centre, with an identical functional definition to the above. + +**2.4 international switching centre (ISC):** The exchange (at the end of an international circuit) which switches calls destined to or originating from another country. + +**2.5 ship earth station (SES):** A station in the maritime mobile satellite service intended to be used while in motion or during halts at unspecified points and which is located on board a ship (see *Radio Regulations*, Article 1). + +**2.6 integrated services digital network (ISDN):** An integrated digital network in which the same digital switches and digital paths are used to establish connections for different services, such as telephony, data, and so on (see the I-Series Recommendations). + +**2.7 telephone user part (TUP):** This defines the necessary telephone signalling functions for use of Signalling System No. 7 (SS No. 7) for international call control signalling. It is specified with the aim of providing the same feature for telephone signalling as other CCITT telephone signalling systems (see Recommendation Q.721). + +**2.8 ISDN user part (ISUP):** This encompasses the signalling functions in SS No. 7 required to provide switched services and user facilities for voice and non-voice applications in an ISDN (see Recommendation Q.761). + +**2.9** **signalling connection control part (SCCP)**: This provides in SS No. 7 additional functions to the message transfer part to cater for both connectionless as well as connection oriented network services, to transfer circuit related, non-circuit related signalling information, and other types of information between exchanges and specialised centres in telecommunication networks (see Recommendation Q.711). + +**2.10** **coast earth station (CES)**: An earth station operating in the fixed satellite service frequency bands or, in some cases, in the maritime mobile-satellite service frequency bands located at a specified fixed point on land to provide a feeder link for the maritime mobile-satellite service (see *Radio Regulations*, Article 1). + +# **3 Overview of Recommendations** + +## **3.1 Recommendation Q.1101** + +Sets out the general requirements for interworking between the first generation (Standard A) INMARSAT system and the international public telephone network. A brief description of the INMARSAT Standard A system is also included. + +## **3.2 Recommendation Q.1102** + +Specifies the interworking between the INMARSAT Standard A system and Signalling System R2. + +## **3.3 Recommendation Q.1103** + +Specifies the interworking between the INMARSAT Standard A system and Signalling System No. 5. + +## **3.4 Recommendation Q.1111** + +Provides information on services offered in the INMARSAT Standard B system, and describes the requirements for connection and internetworking with the public networks. A brief description of the Standard-B system is appended. + +## **3.5 Recommendation Q.1112** + +Presents the procedures for interworking between the INMARSAT Standard B system and the signalling systems of the international public network. + +## **3.6 Recommendation Q.1151** + +Provides information on the services offered in the INMARSAT aeronautical system and describes the requirements for connection and interworking with the public networks. A brief description of the aeronautical system is appended. + +## **3.7 Recommendation Q.1152** + +Presents the procedures for interworking between the INMARSAT aeronautical system and the signalling systems of the international public network. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.112-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.112-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9e8fbde730dd2752b7582734b9e9b317518e84bb --- /dev/null +++ b/marked/Q/T-REC-Q.112-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 latitude and longitude lines. A lightning bolt symbol is positioned to the right of the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**Q.112** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**GENERAL RECOMMENDATIONS ON TELEPHONE +SWITCHING AND SIGNALLING** + +**CLAUSES APPLICABLE TO ITU-T STANDARD +SYSTEMS** + +--- + +**SIGNAL LEVELS AND SIGNAL RECEIVER +SENSITIVITY** + +**ITU-T Recommendation Q.112** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.112 was published in Fascicle VI.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. + +## **2.1 SIGNAL LEVELS AND SIGNAL RECEIVER SENSITIVITY** + +### *2.1.1 Standardized transmitted power* + +The values of the standardized transmitted power for the different line and interregister signals are defined in the relevant parts of the specifications for the CCITT Systems No. 4, No. 5, R1 and R2. + +*Note* - The level of leak current which might be transmitted to line, for example when static modulators are used for signal transmission, should be considerably below signal level, as specified. + +### *2.1.2 Variations of the absolute power level of received signals* + +The standardized absolute power level of the signalling current to be transmitted is fixed at the maximum value compatible with circuit transmission requirements and the extreme values of absolute power level, between which received signalling currents may lie, depend on three factors: + +- 1) the overall loss and the variation with time of this loss of the international circuit (link-by-link signalling) or of the chain of international circuits (end-to-end signalling) at 800 Hz; +- 2) the variation with frequency of the overall loss of these circuits, in relation to the nominal value at 800 Hz; +- 3) the tolerance on the transmitted absolute power level in relation to the nominal value. + +The operate level range of the signal receivers about a nominal value should take account of these three factors. In System No. 4, the operate range ( $\pm 9$ dB) is appropriate for end-to-end signalling. The maximum number of circuits in the end-to-end signalling situation is normally three but more may be possible depending upon the actual conditions. In System No. 5 the operate range, ( $\pm 7$ dB) for line signals and for register signals is appropriate for each circuit in link-by-link signalling. For the other CCITT systems see the relevant parts of their specifications. + +### *2.1.3 Maximum sensitivity of the signal receiver* + +It is desirable to limit the maximum sensitivity of the signal receiver, particularly on account of crosstalk between the GO and RETURN paths of a 4-wire circuit, leak currents, etc. \ No newline at end of file diff --git a/marked/Q/T-REC-Q.1237-200006-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1237-200006-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8021a2cf06e7baba1fd809f07390351ddfc3a954 --- /dev/null +++ b/marked/Q/T-REC-Q.1237-200006-I_PDF-E/raw.md @@ -0,0 +1,3191 @@ + + +![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 + +**Q.1237** + +(06/2000) + +SERIES Q: SWITCHING AND SIGNALLING +Intelligent Network + +# --- **Extensions to Intelligent Network Capability Set 3 in support of B-ISDN** + +ITU-T Recommendation Q.1237 + +(Formerly CCITT Recommendation) + +--- + +## ITU-T Q-SERIES RECOMMENDATIONS + +## SWITCHING AND SIGNALLING + +| | | +|----------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| BROADBAND ISDN | Q.2000-Q.2999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Extensions to Intelligent Network Capability Set 3 in support of B-ISDN** + +# **Summary** + +This Recommendation describes the call model, the application protocol and the procedures for Intelligent Network capabilities associated with B-ISDN. It describes an application protocol that is fully compatible with INAP in ITU-T Q.1238. It describes SSF to SCF call control that is based on service aspect requirements and on network aspect requirements of ITU-T Q.1231. + +## **Source** + +ITU-T Recommendation Q.1237 was prepared by ITU-T Study Group 11 (1997-2000) and approved under the WTSC Resolution 1 procedure on 15 June 2000. + +## **Keywords** + +Broadband, B-ISDN, B-ISUP, DSS2, Intelligent 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 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 | Definitions ..... | 2 | +| 4 | Abbreviations..... | 2 | +| 5 | Relationship of this Recommendation to ITU-T Q.1238..... | 3 | +| 5.1 | Call model..... | 3 | +| 5.1.1 | Examples of specific narrow-band information ..... | 4 | +| 5.1.2 | Examples of specific broadband information..... | 4 | +| 5.2 | Detection point criteria and triggers..... | 4 | +| 6 | CCF/SSF model ..... | 4 | +| 6.1 | CCF/SSF FE model ..... | 4 | +| 6.2 | CCF/SSF functional model components..... | 5 | +| 6.3 | Basic call manager (BCM)..... | 5 | +| 6.3.1 | BCSM model ..... | 5 | +| 6.3.2 | BCSM description ..... | 5 | +| 6.3.3 | BCSM resume points and BCSM transitions ..... | 30 | +| 6.3.4 | BCSM indications for the call model ..... | 31 | +| 6.3.5 | Mapping from cause to DP ..... | 31 | +| 6.3.6 | BCSM detection point ..... | 33 | +| 6.3.7 | DP criteria..... | 33 | +| 6.3.8 | Trigger types and trigger precedence for B-ISDN when carrying N-ISDN services ..... | 50 | +| 6.3.9 | Trigger types and trigger precedence for B-ISDN ..... | 50 | +| 6.4 | Feature interaction manager (FIM)/Call manager (CM)..... | 63 | +| 6.4.1 | DP handling ..... | 63 | +| 6.5 | IN-Switching manager (IN-SM) ..... | 64 | +| 6.5.1 | The connection view model..... | 64 | +| 7 | SCF model ..... | 66 | +| 8 | Finite state model for SSF ..... | 66 | +| 9 | Finite state model for SCF ..... | 66 | +| 10 | Finite state model for USI..... | 66 | +| 11 | Operation procedures ..... | 66 | +| 11.1 | Connect procedure ..... | 66 | +| 11.1.1 | General description..... | 66 | + +| | Page | +|-------------------------------------------------------------------------------------|-------------| +| 11.2 ContinueWithArgument procedure..... | 67 | +| 11.2.1 General description..... | 67 | +| 11.3 EventReportBCSM procedure ..... | 67 | +| 11.3.1 General description..... | 67 | +| 11.4 InitialDP procedure ..... | 67 | +| 11.4.1 General description..... | 67 | +| 11.5 InitiateCallAttempt procedure ..... | 67 | +| 11.5.1 General description..... | 67 | +| 11.6 RequestReportBCSMEVENT procedure ..... | 68 | +| 11.6.1 General description..... | 68 | +| 12 Parameter descriptions ..... | 69 | +| 12.1 AALParameters..... | 69 | +| 12.2 AdditionalATMCellRate ..... | 69 | +| 12.3 AESACalledParty ..... | 69 | +| 12.4 AESACallingParty ..... | 69 | +| 12.5 AlternativeATMCellRate..... | 69 | +| 12.6 ATMCellRate..... | 69 | +| 12.7 BearerCapability ..... | 69 | +| 12.8 CalledPartySubaddress ..... | 70 | +| 12.9 CDVTDescriptor..... | 70 | +| 12.10 ConnectionIdentifier ..... | 70 | +| 12.11 CumulativeTransitDelay ..... | 70 | +| 12.12 EndtoEndTransitDelay..... | 70 | +| 12.13 EventSpecificInformationBCSM ..... | 71 | +| 12.14 GenericIdentifier ..... | 71 | +| 12.15 MinimumATMCellRate..... | 71 | +| 12.16 QoSParameter ..... | 71 | +| 13 Errors ..... | 72 | +| 14 ASN.1 definitions ..... | 72 | +| 14.1 Data types..... | 72 | +| 14.2 Classes ..... | 74 | +| 14.3 Operations and arguments..... | 75 | +| Appendix I – Mapping of Setup Request Primitive signalling information to PIC ..... | 76 | +| I.1 O_BCSM mapping of setup request primitive signalling information to PIC..... | 76 | +| I.1.1 O_Null PIC ..... | 76 | +| I.1.2 Collect_Information PIC ..... | 79 | + +| | Page | +|-----------------------------------------------------------------------------------|-------------| +| I.1.3 O_Active PIC..... | 80 | +| I.1.4 O_Bearer_Modify PIC..... | 80 | +| I.1.5 O_Bearer_Active PIC..... | 80 | +| I.2 T_BCSM mapping of setup request primitive signalling information to PIC ..... | 80 | +| I.2.1 T_Null PIC ..... | 80 | +| I.2.2 T_Active PIC..... | 82 | +| I.2.3 T_Bearer_Modify PIC ..... | 82 | +| I.2.4 T_Bearer_Active PIC ..... | 82 | +| Appendix II – Relationship of DP criteria to Signalling Parameters ..... | 82 | +| II.1 Relationship of DP criteria to signalling parameters ..... | 82 | +| II.1.1 Analyse_Information PIC ..... | 82 | +| II.1.2 Authorize_Termination_Attempt PIC ..... | 86 | + +# **Extensions to Intelligent Network Capability Set 3 in support of B-ISDN** + +# **1 Scope** + +This Recommendation describes the call model, the application protocol and the procedures for Intelligent network capabilities associated with DSS2, B-ISUP, DSS2 carrying 64 kbit/s circuit emulated services, and B-ISUP carrying 64 kbit/s circuit emulated services. + +The application protocol described in this Recommendation is fully compatible with INAP in ITU-T Q.1238, and contains extensions to ITU-T Q.1238. The SSF to SCF call control is based on service aspect requirements and on network aspect service requirements of ITU-T Q.1231. + +# **2 References** + +The following ITU-T Recommendations and other references contain provisions, which through references 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 Q.931 (1998), *ISDN user-network interface layer 3 specification for basic call control*. +- ITU-T Recommendation Q.932 (1998), *Digital subscriber signalling system No. 1 – Generic procedures for the control of ISDN supplementary services*. +- ITU-T Recommendation Q.1231 (1999), *Introduction to Intelligent Network Capability Set 3*. +- ITU-T Recommendations Q.1238, Q.1238.1 (2000), Q.1238.2 (2000), Q.1238.3 (2000), Q.1238.4 (2000), Q.1238.5 (2000), Q.1238.6 (2000), Q.1238.7 (2000), *Interface Recommendation for Intelligent Network Capability Set 3*. +- ITU-T Recommendation Q.1290 (1998), *Glossary of terms used in the definition of Intelligent Networks*. +- ITU-T Recommendation Q.2610 (1999), *Usage of cause and location in B-ISDN user part and DSS2*. +- ITU-T Recommendation Q.2723.1 (1996), *B-ISDN user part – Support of additional traffic parameters for sustainable cell rate and quality of service*. +- ITU-T Recommendation Q.2725.1 (1996), *B-ISDN user part, Support of negotiation during connection setup*. +- ITU-T Recommendation Q.2725.2 (1996), *B-ISDN user part – Modification procedures*. +- ITU-T Recommendation Q.2761 (1999), *Functional description of the B-ISDN user part (B-ISUP) of signalling system No. 7*. +- ITU-T Recommendation Q.2762 (1999), *General functions of messages and signals of the B-ISDN user part (B-ISUP) of signalling system No. 7*. +- ITU-T Recommendation Q.2763 (1999), *Signalling system No. 7 B-ISDN user part (B-ISUP) – Formats and codes*. + +- ITU-T Recommendation Q.2769.1 (2000), *Support of number portability information across B-ISUP*. +- ITU-T Recommendation Q.2931 (1995), *Digital subscriber signalling system No. 2 – User network interface (UNI) layer 3 specification for basic call/connection control*. +- ITU-T Recommendation Q.2932.1 (1996), *Digital subscriber signalling system No. 2 – Generic functional protocol: Core functions*. +- ITU-T Recommendations Q.2961, Q.2961.1 (1995), Q.2961.2 (1997), Q.2961.3 (1997), Q.2961.4 (1997), Q.2961.5 (1999), Q.2961.6 (1998), *Digital subscriber signalling system No. 2 – Additional Traffic Parameters*. +- ITU-T Recommendation Q.2962 (1998), *Digital subscriber signalling system No. 2 – Connection characteristics negotiation during call/connection establishment phase*. +- ITU-T Recommendation Q.2963.1 (1999), *Peak cell rate modification by the connection owner*. + +# 3 Definitions + +The definitions of ITU-T Recommendation Q.1238 and ITU-T Recommendation Q.1290 are applicable. See also parameter descriptions in this Recommendation. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|----------|------------------------------------------------------| +| AAL | ATM Adaptation Layer | +| ACM | Address Complete Message | +| AESA | ATM End System Address | +| ATM | Asynchronous Transfer Mode | +| BCSM | Basic Call State Model | +| B-ISDN | Broadband Integrated Services Digital Network | +| B-ISUP | Broadband ISDN User Part | +| BTC | Broadband Transfer Capability | +| CBR | Constant Bit Rate | +| CCF | Call Control Function | +| CDVT | Cell Delay Variation Tolerance | +| CPCS-SDU | Common Part Convergence Sublayer – Service Data Unit | +| CPH | Call Party Handling | +| CS | Call Segment | +| CSCV | Call Segment Connection View | +| DP | Detection Point | +| DSS2 | Digital Subscriber Signalling System 2 | +| EDP | Event Detection Point | +| FRL | Facility Restriction Level | + +| | | +|----------|-------------------------------------------| +| FSM | Finite State Machine | +| GIT | Generic Identifier Transport | +| IAA | IAM Acknowledgment Message | +| IAM | Initial Address Message | +| ISDN | Integrated Services Digital Network | +| PIC | Point in Call | +| QoS | Quality of Service | +| SCF | Service Control Function | +| SLPI | Service Logic processing Program Instance | +| SS No. 7 | Signalling System No. 7 | +| SSCS | Service Specific Convergence Sublayer | +| SSF | Service Switching Function | +| TDM | Time Division Multiplex | +| TDP | Trigger Detection Point | +| TNS | Transit Network Selection | +| UNI | User Network Interface | +| USI | User Service Information | +| VCI | Virtual Channel Identifier | +| VPCI | Virtual Path Connection Identifier | + +# 5 Relationship of this Recommendation to ITU-T Q.1238 + +ITU-T Q.1237 describes IN services in a B-ISDN environment. It includes descriptions for implementing existing narrow-band IN services and new broadband IN services over a network that uses B-ISDN signalling. In cases of ambiguities between ITU-T Q.1237 and ITU-T Q.1238, the operations, procedures, formats, and codes of ITU-T Q.1238 take precedence. + +ITU-T Q.1237 is based on the functional model, call model, procedures, operations, formats, and codes of ITU-T Q.1238. It includes some enhancements to reflect uniqueness of B-ISDN. The enhancements can be categorized into two major topics: + +- 1) Call Model; +- 2) DP Criteria and Triggers. + +## 5.1 Call model + +ITU-T Q.1237 includes one major change to the Q.1238 call model to accommodate broadband connection modification, as well as minor changes to the information available in the originating and terminating Points in Call (PICs). + +The call model is changed to accommodate the connection modification capability that is included in B-ISDN signalling. This is accomplished through the addition of a subordinate call state model in both the originating and terminating BCSMs. The subordinate state model assumes that the BCSM creates a subordinate process when it enters the O/T\_Active PIC. This subordinate process reflects the status of the broadband bearer connection. + +The call model is also changed to reference information available in broadband signalling for each PIC. Implementation of existing narrow-band IN services in B-ISDN is based on the existence of specific narrow-band signalling information in the ITU-T Recommendations for broadband signalling. Implementation of broadband IN services is based on the extensions of signalling information in ITU-T Recommendations to support broadband bearers. Therefore, references are included in an informative appendix to provide broadband references for both narrow-band and broadband signalling information. + +### **5.1.1 Examples of specific narrow-band information** + +Narrow-band Bearer Capability is carried in DSS2 and in B-ISUP, providing an instance of DSS1 Bearer Capability and of ISUP User Service Information (USI) in broadband signalling. + +Forward Narrow-band Interworking Indicator and the National/International Call Indicator are carried in B-ISUP, providing an instance of ISUP Forward Call Indicators in broadband signalling. + +Many parameters carried in B-ISUP are identical to parameters provided in ISUP. The Forward Global Virtual Network Service (Forward GVNS), Backward GVNS parameters are examples, as are Called Directory Number and Number Portability Forward Information. + +Other narrow-band signalling information, relating to Supplementary Services and to Call Progress, is included in broadband signalling by reference. The Notification indicator, carried in ITU-T Q.2931 DSS2, cites ITU-T Q.932 as the example for the content to be included in its information field. The Progress Indicator, carried in ITU-T Q.2931, cites ITU-T Q.931 to define the content to be included in its information field. The Facility information element referenced in ITU-T Q.2932 may be used to invoke service features described in ITU-T Q.932. For example, the content carried in the Facility information element may include Keypad Facility, Display, Feature Activation, Feature Indication, and Facility Information. + +### **5.1.2 Examples of specific broadband information** + +New IN capabilities include recognition and selection of Broadband Transfer Capabilities, ATM Traffic Descriptors, Quality of Service classes and ATM Adaptation Layer characteristics of importance to the services carried over the connection. These new IN capabilities are added to capabilities described in ITU-T Q.1238 for IN services in a narrow-band environment. + +## **5.2 Detection point criteria and triggers** + +ITU-T Q.1237 includes changes to Q.1238 Detection Point Criteria that reflect the change in bearer from Time Division Multiplex (TDM) to Asynchronous Transfer Mode (ATM). Specific B-Channel Identifier detection point criteria, Channel\_Setup\_PRI trigger, and Shared\_Interoffice\_Trunk trigger, are changed to acknowledge implementation over a broadband bearer. + +ITU-T Q.1237 includes new detection point criteria and new triggers for specific attributes of the broadband connection. Examples are ATM Traffic Descriptor, Quality of Service, and ATM Adaptation Layer. + +Descriptions, such as Facility Group, Facility Group Member are changed to reflect the attributes of the broadband bearer. For example, Facility Group is used to indicate Virtual Facilities (Virtual Paths, Virtual Channels) rather than physical channels. + +# **6 CCF/SSF model** + +## **6.1 CCF/SSF FE model** + +The overview of the CCF/SSF Functional Entity model in 6.1/Q.1238.2 applies. + +## **6.2 CCF/SSF functional model components** + +The functional model described in 6.2/Q.1238.2 applies. + +## **6.3 Basic call manager (BCM)** + +The descriptions for Basic Call Manager in 6.3/Q.1238.2 apply. + +### **6.3.1 BCSM model** + +The descriptions for the BCSM Model in 6.3.1/Q.1238.2 apply. + +Any discrepancies in the Point in Call (PIC) descriptions in 6.3.2, between ITU-T Q.1238 and this Recommendation, should be resolved using the descriptions in ITU-T Q.1238. + +### **6.3.2 BCSM description** + +The descriptions for the BCSM in 6.3.2/Q.1238.2 apply, however, the call model is enhanced to accommodate the B-ISDN bearer modification capability. B-ISDN (DSS2 and B-ISUP) signalling allows the modification of the connection characteristics by the originating party during the active phase of the call. + +For B-ISDN, the BCSM creates a subordinate process when it encounters the O\_Answer\_DP at the O\_Active PIC. This subordinate process models the status of the bearer connection. The process initiates in the O\_Bearer\_Active PIC. It transitions to O\_Bearer\_Modify PIC on receipt of a modification request. It returns to the O\_Bearer\_Active PIC through the O\_Modify\_Result DP when the modification request is acknowledged or rejected, or when modification fails. The subordinate process is removed when the O-BCSM transitions to the O\_Disconnect DP, or on any transition of the O-BCSM to exception. The T-BCSM for the bearer is modelled equivalently. + +#### **6.3.2.1 Originating BCSM** + +The originating half of the BCSM corresponds to that portion of the BCSM associated with the originating party (see Figure 1). + +![Figure 1/Q.1237 – Originating BCSM for ITU-T Q.1237: Basic set of transitions. This state transition diagram shows the flow of an originating call through various states: O_Null, Authorize_Origination_Attempt, Collect_Information, Analyse_Information, Select_Route, Authorize_Call_Setup, Send_Call, O_Alerting, O_Active, and O_Suspended. Transitions are triggered by internal events (Origination_Attempt, Collected_Information, Analysed_Information, O_Term_Seized, O_Suspend) or external signals (O_Abandon, O_Mid_Call, O_Disconnect, O_Exception, Origination_Denied, collect_timeout, invalid_information, route_busy, route_failure, Route_Select_Failure, Authorize_Route_Failure, O_Called_Party_Busy, O_No_Answer, O_Re-answer, O_suspend_failure). A 'Create Subordinate' action leads to a sub-state machine containing O_Bearer_Active and O_Bearer_Modify states with O_Modify_Request and O_Modify_Result transitions. A 'Remove Subordinate' action returns to the main flow. The diagram is labeled T11107100-00.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Figure 1/Q.1237 – Originating BCSM for ITU-T Q.1237: Basic set of transitions. This state transition diagram shows the flow of an originating call through various states: O\_Null, Authorize\_Origination\_Attempt, Collect\_Information, Analyse\_Information, Select\_Route, Authorize\_Call\_Setup, Send\_Call, O\_Alerting, O\_Active, and O\_Suspended. Transitions are triggered by internal events (Origination\_Attempt, Collected\_Information, Analysed\_Information, O\_Term\_Seized, O\_Suspend) or external signals (O\_Abandon, O\_Mid\_Call, O\_Disconnect, O\_Exception, Origination\_Denied, collect\_timeout, invalid\_information, route\_busy, route\_failure, Route\_Select\_Failure, Authorize\_Route\_Failure, O\_Called\_Party\_Busy, O\_No\_Answer, O\_Re-answer, O\_suspend\_failure). A 'Create Subordinate' action leads to a sub-state machine containing O\_Bearer\_Active and O\_Bearer\_Modify states with O\_Modify\_Request and O\_Modify\_Result transitions. A 'Remove Subordinate' action returns to the main flow. The diagram is labeled T11107100-00. + +**Figure 1/Q.1237 – Originating BCSM for ITU-T Q.1237: Basic set of transitions** + +The following information is available at all PICs in the O-BCSM: + +- Calling Party Class of Service (where locally available, e.g. subscriber profile including calling party category information). +- Call Reference (where locally assigned in the switch). +- Terminal Type – See ITU-T Q.1290. The SCF uses this to determine the most appropriate form of user-interaction to use (e.g. in-band announcements). This information may only be available at originating local exchanges. +- Calling Party Facility Restriction Level (FRL) – The permission level associated with an incoming facility, e.g. trunk line. + +- Calling Party BGID (Business Group Identity) – The Basic Business Group or Multiswitch Business Group Identity of the calling party, e.g. group-based services. +- Charge Number – See ITU-T Q.1290. This information is available at the CCF/SSF for a B-ISDN DSS2 interface served by the CCF/SSF and may be available for a SS No. 7 B-ISUP interface. +- Class of Service – See ITU-T Q.1290. +- Calling Party's Carrier, Carrier Identification Code, Carrier Selection; Route Index; and Travelling Class Mark. +- Calling Facility Group – See ITU-T Q.1290. Available on DSS2 or SS No. 7 B-ISUP interfaces. +- Calling Facility Group Member – See ITU-T Q.1290. Available on DSS2 or SS No. 7 B-ISUP interfaces. + +The above information applies in addition to Signalling Information received from the signalling interface and from the peer T\_BCSM. The Signalling Information depends on the signalling interface arrangement applied: DSS2, or B-ISUP, etc. + +The descriptions for each of the PICs in the originating half of the BCSM are described below: + +##### 6.3.2.1.1 O\_Null + +**Entry event:** Disconnect and clearing of a previous call (DPs: O\_Disconnect and O\_Abandon), or default handling of exceptions by CCF/SSF completed. + +**Functions:** Interface (DSS2/B-ISUP) is idled (no call exists, no call reference exists, etc.). Supervision is being provided. + +**Information available:** After detecting the Origination Attempt event, it is assumed that the CCF/SSF has information received from the signalling interface arrangement (e.g. as a Setup service request primitive is received due to a DSS2 Setup, B-ISUP IAM) available associated with the originating call portion, with restrictions as noted. If the CCF/SSF determines that the origination is denied, the cause of the failed authorization is also known. + +Any information relating to switch-based features that have already been invoked for the call will also be available. + +###### Exit events: + +- Indication of desire to place outgoing call (e.g. Q.2931 setup message, B-ISDN-UP IAM message). (DP: Origination\_Attempt). +- The following exception exit events are applicable to the O\_Null PIC: +For this PIC, if the call encounters one of these exceptions during O\_Null PIC processing, the exception event is not visible because there is no corresponding DP. +- The O\_Abandon occurs when the calling party disconnects. +For example, this event can result from one of the following: + - the CCF/SSF receives a call clearing message from a caller served by a DSS2 B-ISDN interface; + - the CCF/SSF receives a Release Message from an SS No. 7 B-ISUP interface. + +**Corresponding Q.2931 call state:** O\_Null (N0). + +##### 6.3.2.1.2 Authorize\_Origination\_Attempt + +**Entry event:** An indication is available that the originating terminal needs to be authorized. (DP: Origination\_Attempt). + +###### Functions: + +- The originating terminal rights should be checked using the calling party's identity and service profile. The authority/ability of the party to place the call with given properties (e.g. bearer capability, connection restrictions) is verified. The types of authorization to be performed may vary for different types of originating resources (e.g. for DSS2 interfaces vs. B-ISUP interfaces). +- Other features, such as some content retained in service profiles, which might be required during this PIC are not described in the Q.1237 BCSM. + +**Information available:** After detecting the Origination\_Attempt\_Authorized event, it is assumed that the SSP has the same information available associated with the originating call portion as it did after detecting the Origination\_Attempt event in the O\_Null PIC. + +- Information as per the O\_Null PIC. +- Authorization result – If the SSP determines that the origination is denied, the cause of the failed authorization is also known. + +###### Exit events: + +- An indication is received that the authorization is successful. The O\_BCSM moves to the Collect\_Information PIC (DP: Origination\_Attempt\_Authorized). +- The O\_Abandon event occurs when an indication of clearing or of originating party abandon is received. This event causes call processing to move to the O\_Abandon DP. +- An indication is received that the call origination is denied. The O\_BCSM moves to the Origination\_Denied DP. + +##### 6.3.2.1.3 Collect\_Information + +**Entry event:** Authority/ability to place outgoing call verified (DP: Origination\_Attempt\_Authorized). + +###### Functions: + +- Initial information (e.g. service codes, prefixes, address digits, connection information) is collected from originating party. Information is examined according to addressing plan to determine end of collection in the case of overlap sending. No further action may be required if an *en bloc* signalling method is in use (e.g. an ISDN DSS2 user using *en bloc* signalling, or an incoming SS No. 7 B-ISUP interface). +- The CCF/SSF shall be able to support subsequent digit collection according to trigger criteria assigned before sending the query. For example, if a feature code (e.g. \*64) is entered, the CCF/SSF may: + - collect digits according to the normal dialling plan; or + - collect a variable number of digits. + +**Information available:** After the CCF/SSF determines that information collection is complete, it is assumed that the CCF/SSF has the following information available associated with the originating call portion: + +- Information as per the O\_Null PIC. +- Collected Information – As obtained from Setup Service Request primitive. + +###### Exit events: + +- Availability of complete initial information from originating party. (This event may have already occurred in the case of *en bloc* signalling, in which case the waiting duration in this PIC is zero.) (DP: Collected\_Info). + +- The following exception exit events are applicable to this PIC: Collect\_Failure. The Collect\_Failure event encompasses events such as CollectTimeout, CollectInfoFailure and InvalidInformation. +- The CollectTimeout event is detected when enough information to process the call was not received by the CCF/SSF before a normal timer expires. For an SS No. 7 B-ISUP or DSS2 interface, this event corresponds to the IAM or SETUP not containing the information necessary to process the call. There may be no timing involved, unless overlap sending is used by ISDN services carried across a DSS2 interface (Note 1). +- The CollectInfoFailure event is detected when the CCF/SSF is unable to perform the information collection due to a lack of switch resources. +- The InvalidInformation event occurs when the information received from the caller is not valid, for instance the information received includes an invalid address or invalid information. +- The O\_Abandon event occurs when an indication of clearing or of originating party abandon is received. This event causes call processing to move to the O\_Abandon DP. + +**Comment:** Some digit analysis is required to determine the end of dialling in the case of N-ISDN overlap sending in DSS2. However, it is assumed that this analysis may be modelled as separable from the rest of digit analysis, which occurs in the Analyse\_Information PIC. There is no intention to specify an implementation. However, a switch should externally present the separable view described for closed numbering plans (Note 2). + +In the case of ISDN *en bloc* sending in DSS2, the receipt of a SETUP message detected at the Origination\_Attempt\_Authorized DP causes the BCSM to pass through the Collect\_Information PIC to the Collected\_Information DP, without further processing in the Authorized\_Origination\_Attempt PIC. Note that the BCSM transitions to Collected\_Information DP when the initial information package/dialling string is received from the calling party – this occurs when enough information is received to proceed with call processing (e.g. as in the case of ISDN overlap sending). Specifically, for the digit by digit collection case, if the Collected\_Information DP is armed as a Trigger detection Point-Request (TDP-R), the SSF sends the query, i.e. an initialling DP request (i.e. Initial DP or CollectedInformation operation) to the SCF when enough is received to determine if the TDP criteria is met. It suspends BCSM processing but will collect further digits. It is network operator specific to determine when complete information is available (Note 3). + +NOTE 1 – B-ISDN terminal equipment (B-TE) shall use *en bloc* sending in B-ISDN, implying that complete address information is included in the SETUP message. In order to allow terminal equipment designed for N-ISDN to be connected to the B-ISDN via a terminal adapter, the DSS2 protocol also supports overlap sending (see ITU-T Q.2931). + +NOTE 2 – This separable view is provided by supporting distinct DPs. The Collected\_Information DP is used after digit collection and the Analysed\_Information DP is used after the rest of the digit analysis. + +NOTE 3 – In some networks, it may not be possible for the CCF/SSF to determine when the called number information is complete. Therefore, TDP criteria for Collected\_Information DP may be met in such networks before the called number information is complete. + +**Corresponding Q.2931 call state:** Call Initiated (N1), and (optionally) Overlap Sending (N2). + +##### 6.3.2.1.4 Analyse\_Information + +**Entry event:** Availability of complete initial information from originating party (DP: Collected\_Information) or Route Busy event reported from the Select Route PIC. + +**Function:** Information being analysed and/or translated according to dialling plan to determine routing address and call type (e.g. local exchange call, transit exchange call, international exchange call), as well as service subscription and access parameters. In the case that the SSF has received a + +list of destination addresses in a Connect or AnalyseInformation operation, the CCF/SSF shall use the next destination address in the list. + +The following provides details as to when the next destination address/Route should be tried under each condition. + +| | | +|----------------------|---------------------------| +| Parameters Received: | DestinationRoutingAddress | +| Result: | Busy or No Answer | +| Processing Order: | Destination address1 | + +Since no forwarding condition is specified, only the first destination address is tried. + +| | | +|----------------------|----------------------------------------------------------------------| +| Parameters Received: | DestinationRoutingAddress, ForwardingCondition | +| Result: | Busy/No Answer | +| Processing Order: | Destination address1
Destination address2
Destination address3 | + +So long as the forwarding condition is met, the next destination address is tried. + +| | | +|----------------------|----------------------------------------------------------------------------------------------| +| Parameters Received: | RouteList, DestinationRoutingAddress | +| Result: | No route out of local switch (busy) | +| Processing Order: | Route1, destination address1
Route2, destination address1
Route3, destination address1 | + +No other destination addresses need be tried since there are no routes out of the switch. + +| | | +|----------------------|---------------------------------------------------------------| +| Parameters Received: | RouteList, DestinationRoutingAddress | +| Result: | Route busy is found to be at a switch other than local switch | +| Processing Order: | Route1, destination address1 | + +No other routes need be tried since the local route is successful, but a busy condition was encountered elsewhere. No other destination addresses are tried since forwarding condition does not apply. + +| | | +|----------------------|--------------------------------------| +| Parameters Received: | RouteList, DestinationRoutingAddress | +| Result: | No answer received | +| Processing Order: | Route1, destination address1 | + +No other routes need be tried since the route is successful, but a no answer condition was encountered. + +No other destination addresses are tried since forwarding condition does not apply. + +Only after the appropriate destination addresses/Routes have been tried will the call move onto the O\_Called\_Party\_Busy DP, O\_No\_Answer DP, or Route\_Select\_Failure DP as appropriate. + +One of the results of processing in this PIC is determination of routing address: + +- called party number only (called party number is served by the SSF); +- called party number and route index, where the route index is a pointer to an outbound path on which to route an outgoing call attempt (called party number is served by another SSF); +- called party number and route index, where the route index is a pointer to a list of outbound paths on which to route an outgoing call attempt (called party number is served by another SSF). + +**Information available:** After the CCF/SSF determines the information has been analysed, it is assumed that the CCF/SSF has the following information available associated with the originating call portion: + +- Information as per the O\_Null PIC. +- Analysis Results (of the Collected Information) – as described in the examples below. + +From a DSS2 interface that supports 64 kbit/s based ISDN circuit mode services, this consists of one or more of the following: + +- Called Party Number. +- Numbering Plan Indicator – See Q.2931 Numbering Plan Indicator signalling information. +- Type Of Call – See ITU-T Q.1290. +- Carrier – See ITU-T Q.1290. +- Carrier Identification Code – See ITU-T Q.1290. +Available for Internetwork carrier calls. +- Carrier Selection – See ITU-T Q.1290. +Available for Inter Serving Area ID carrier calls. +- Route List – See ITU-T Q.1290. +- Collected Information – Access Code within a CDP, Feature Code, Feature Activation, Prefix, Carrier Access Code/Carrier Identification Code, Collected Address Information/Digits – as described under the Collect\_Information PIC. + +From a SS No. 7 B-ISUP interface that supports ISUP parameters, this consists of one or more of the following: + +- Charge Number – as defined in the O\_Null PIC (for a SS No. 7 B-ISUP Interface). +- Called Party Number and Numbering Plan Indicator (as defined above for DSS2 interface). +- Carrier Identification – available for Inter Serving Area ID carrier calls. +- Carrier Selection – See ITU-T Q.1290. Available for Inter Serving Area ID carrier calls. +- Originating Line Information – See ITU-T Q.1290. Available for Inter Serving Area ID carrier calls. +- Route Index – See ITU-T Q.1290. +Available if this call does not terminate on this CCF/SSF. + +From B-ISDN DSS2 and SS No. 7 B-ISUP interfaces, this consists of one or more of the following: + +- Collected Information as defined for the Collect\_Information PIC. +- Service Profile and Access Parameter Information. (Reflected in the information returned in analysis results if provisioned and enabled on the interface.) +- Analysis Results of the collected information. Following are examples of analysis results that may be returned in the connect operation: + - VPCI/VCI to be returned to the connection originator in a DSS2 Call Proceeding Message or in a B-ISUP IAM Acknowledge message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the O\_Answer DP as the Cell Rate possibly returned to the connection originator in the DSS2 CONNECT message or B-ISUP ANswer Message. + - Called Party Address (routing address) to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Called Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + +- Calling Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. +- Transit Network Selection parameter to be forwarded toward the destination in a B-ISUP IAM. +- Calling Party Address to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. +- Calling Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. +- Cumulative Transit Delay to be included in a DSS2 SETUP or a B-ISUP IAM. +- Cause value to be returned to the connection originator in a Release Message. + +###### **Exit events:** + +- Availability of routing address and nature of address. This event causes call processing to move to the Analysed\_Information DP. +- The following exception exit events are applicable to this PIC: InvalidInformation. The InvalidInformation event occurs when the information received from the caller is not valid and no further treatment (e.g. routing of the call to an announcement in case of a wrong dialled number) can be applied to the call, for instance in case the information received violates the dialling plan in force. +- The O\_Abandon event occurs when an indication of clearing or of originating party abandon is received. This event causes call processing to move to the O\_Abandon DP. + +**Comments:** Note that routing address does not necessarily mean that the final physical route has been determined (e.g. route list has not been searched, directory number has not yet been translated to physical port address), though this may be the case (e.g. when routing to a specific path). + +**Corresponding Q.2931 call state:** Not applicable. + +##### 6.3.2.1.5 Select route + +**Entry events:** Availability of routing address and call type. (DP: Analysed\_Information) or route busy event reported from the Send\_Call or O\_Alerting PICs. + +###### **Functions:** + +- Routing address and connection parameters are being interpreted. The VPCI and VCI for the originating access segment are selected. The next route on the terminating side is being selected. This may involve sequentially searching a route list, translating a directory number into physical port address, etc. + +NOTE – In a broadband environment, the switching system may select path (VPI) and channel (VCI) in two directions of the connection: + +- 1) toward the originating end system, and + - 2) toward the terminating end system or toward the transit network. +- When the entry event is the route failure event from the Send\_Call PIC (see below), the CCF/SSF must first check the Route Failure Condition 1, Route Failure Condition 2, or Route Failure Condition 3 as defined under the Send\_Call PIC exit events. If these conditions are true, then the call shall proceed to the Analyse Information PIC in order to use the next Destination Address. + +If these three conditions are not met, then depending on the location in the network where the route is busy, the action is one of the following: + +- If the route selected for the connection is busy at this switch, the CCF/SSF attempts to route the connection on the next route that has been specified for the connection (when a route list is being searched or alternate routes are specified by the SCF). Call processing moves to the Analyse\_Information PIC when one of two conditions occurs: all private-facility trunk groups have been tried and routing over a public facility is allowed, or routing to a particular intra or internetwork carrier has been tried and an alternate carrier is allowed. +- If all of the routes (private and public) have been tried and no route is available, the Route\_Select\_Failure event is detected. +- If route busy is detected at another switch, an indication of this condition may be received via SS No. 7 signalling. In this case, a Route\_Select\_Failure event is detected. + +**Information available:** After the CCF/SSF determines the route has been selected, it is assumed the CCF/SSF has the following information available and associated with the originating portion of the connection: + +For a DSS2 interface that supports 64 kbit/s based ISDN circuit mode services or for a SS No. 7 B-ISUP interface that supports ISUP parameters: + +- Information as per the O\_Null PIC. +- Analysis Results – See description in the Analyse\_Information PIC. +- Routing Information – When more than one route has been specified for the connection (either by the SCF or as part of the information stored at the CCF/SSF), the CCF/SSF remembers what routes have been tried for this connection and which route to select next. + +For a DSS2, or for a SS No. 7 B-ISUP interface: + +- Information as per the O\_Null PIC. +- Service Profile and Access Parameter Information – See description in the Analyse\_Information PIC. +- Analysis Results – See description in the Analyse\_Information PIC. +- Routing Information – When more than one route has been specified for the connection (either by the SCF or as part of the information stored at the CCF/SSF), the CCF/SSF remembers what routes have been tried for this connection and which route to select next. + +###### **Exit events:** + +- Route Selected event. +- Unable to select a route (e.g. unable to determine a correct route, no more routes on route list) or indication from the terminating half BCSM that call cannot be presented to the terminating party (e.g. network congestion). This event causes call processing to move to the Route\_Select\_Failure DP. The event indication received from T\_BCSM that causes call processing to move to the O\_Route\_Select\_Failure DP depends upon the event reason (cause value) as defined according to ITU-T Q.1238.2 "O\_BCSM: Mapping Cause value to DP". +- The route busy event leading to the Analyse\_Information PIC as described above, or the following four conditions are met: + - a) unable to select a route (e.g. unable to determine a correct route, no more routes on route list) or indication from the terminating half BCSM that call cannot be presented to the terminating party (e.g. network congestion); + - b) the forwarding condition is busy, as specified by the ForwardingCondition parameter; + +- c) the route was determined by switch translations at the Analyse\_Information PIC; +- d) there are more destination addresses left to try. + +Route busy is a non-IN transition which is part of a basic call. This is needed in case the CCF/SSF needs to process a list of destination addresses. These destination addresses can be returned in a Connect or Analyse\_Information message. Upon being unable to select a route, the route busy BCSM transition returns to the Analyse\_Information PIC to analyse the next destination address in the list. + +- Originating party abandons call (DP: Abandon). + +##### 6.3.2.1.6 Authorize\_Call\_Setup + +**Entry event:** Route Selected event. + +**Function:** The authority of the calling party to obtain this particular connection is verified. + +**Information available:** After the CCF/SSF determines the call setup has been authorized, it is assumed the CCF/SSF has the following information available with restrictions as noted. + +For a DSS2 interface that supports 64 kbit/s based ISDN circuit mode services or for a SS No. 7 B-ISUP interface that supports ISUP parameters: + +- Information as per the O\_Null PIC. +- Analysis Results – See description in the Analyse\_Information PIC. +- Routing Information – See description in the Select\_Route PIC. + +For a DSS2, or for a SS No. 7 B-ISUP interface: + +- Information as per the O\_Null PIC. +- Service Profile and Access Parameter Information – See description in the Analyse\_Information PIC. +- Analysis Results – See description in the Analyse\_Information PIC. +- Routing Information – See description in Select\_Route PIC. + +###### **Exit events:** + +- Call Setup Authorized event. The Call Setup Authorized event occurs when the authority to obtain the connection is verified. +- The O\_Abandon event occurs when an indication of clearing or originating party abandon is received. This event causes connection processing to move to the O\_Abandon DP. +- The Authorization Failure event occurs when the authority to obtain the connection is denied (e.g. service not subscribed, access facility limitations exceeded, business group restriction mismatch). This event causes a BCSM transition to the Authorize\_Route\_Failure DP. + +##### 6.3.2.1.7 Send\_Call + +**Entry event:** Call Setup Authorized event. + +**Functions:** The CCF/SSF sends an indication of the desire to set up a call to the specified Called Party ID to the terminating call portion. + +For a DSS2 interface that supports 64 kbit/s based ISDN circuit mode services or for a SS No. 7 B-ISUP interface that supports ISUP parameters: + +The information that may be passed to the terminating call portion is for example: Charge Number; Calling Party ID; Calling Party BGID; Calling Party Category; Bearer Capability; Called Party ID; Calling Party Subaddress; Called Party Subaddress; Forward GVNS, Carrier; Route Index; Carrier Identification Code; Carrier Selection; and TCM. Other feature-information not used by the + +processing modelled by this PIC (e.g. call forwarding, generic name, and business group information) may also be passed to the terminating call portion. + +For a DSS2 or for a SS No. 7 B-ISUP interface: + +The information that may be passed to the terminating call portion is described in the Analyse\_Information PIC. + +For a DSS2 caller, during the processing that this PIC models, the CCF/SSF returns a CALL PROCEEDing message. For a B-ISDN B-ISUP connection, the SSF/SCF sends an IAM acknowledgment message (IAA). + +**Information available:** After the CCF/SSF determines the call has been delivered (to the terminating half), it is assumed the CCF/SSF has the following information available with restrictions as noted. + +For a DSS2 interface that supports 64 kbit/s based ISDN circuit mode services or for a SS No. 7 B-ISUP interface that supports ISUP parameters: + +- Information as per the O\_Null PIC. +- Analysis Results – See description in the Analyse\_Information PIC. +- Routing Information – See description in the Select\_Route PIC. +- Feature Activation Information – See description below: +A service feature request is received from the originating party: e.g. feature activator. + +For a DSS2, or for a SS No. 7 B-ISUP interface: + +- Information as per the O\_Null PIC. +- Service Profile and Access Parameter Information – See description in the Analyse\_Information PIC. +- Analysis Results – See description in the Analyse\_Information PIC. +- Routing Information – See description in Select\_Route PIC. + +###### **Exit events:** + +- A route failure event is detected when: + - i) an indication of a T\_Busy event specifying route busy; or + - ii) a Call Rejected event specifying route busy (received when the route is found to be busy at a switch other than the local switch) is received from the terminating call portion; + - iii) the following four conditions are met, hereafter called Route Failure Condition 1: + - a) an indication of a T\_Busy event specifying route busy (received when the route at the local switch is found to be busy) is received from the terminating call portion (presentation failure event from the Present Call DP); + - b) the forwarding condition is busy, as specified by the ForwardingCondition parameter; + - c) the route was determined by switch translations at the Analyse\_Information PIC; + - d) there are more destination addresses left to try; + - iv) the following four conditions are met, hereafter called Route Failure Condition 2: + - a) a Call Rejected event specifying route busy (received when the route is found to be busy at a switch other than the local switch) is received from the terminating call portion (presentation failure event from the Present Call PIC); + - b) the forwarding condition is busy, as specified by the ForwardingCondition parameter; + +- c) the route was determined by the switch translations at the Analyse\_Information PIC; + - d) there are more destination addresses left to try; +- v) the following four conditions are met, hereafter called Route Failure Condition 3: +- a) O\_Called\_Party\_Busy event or O\_No\_Answer event occurs (as specified below); + - b) the forwarding condition is met, as specified by the ForwardingCondition parameter; + - c) there are more destination addresses left to try. + +NOTE – The Route\_Failure event takes precedence over the O\_Called\_Party\_Busy and O\_No\_Answer events. + +In all five cases, the originating call portion returns to the Select\_Route PIC, if this event is not detected at a DP (e.g. more CDPNs left to try). + +Otherwise this event causes call processing to move to the O\_Route\_Select\_Failure DP or O\_Called\_Party\_Busy DP [e.g. User Busy, Subscriber absent (not reachable) or O\_No\_Answer DP or O\_Exception]. Which DP depends upon the event reason (cause value) as defined according to ITU-T Q.1238.2 "O\_BCSM: Mapping Cause value to DP". + +- An O\_Answer event occurs when an indication of a T\_Answer event is received from the terminating call portion. This occurs in reaction to a DSS2 CONNECT or to a B-ISUP Answer message. This event causes call processing to move to the O\_Answer DP. +- An O\_Term\_Seized event occurs when an indication of a call accepted event is received from the terminating call portion. In B-ISDN DSS2 this occurs, for example, when a call is offered to the interface with a SETUP message and the call setup timer T303 is initiated. The destination exchange sends a Call Progress message toward the originating exchange or an ALERTING message to the Calling User. If T303 expires and no response is received, the switch retransmits the SETUP message, and re-initializes T303. In this case, the calling party receives an alerting message, however, the called party has not accepted the call. When the O\_Term\_Seized event occurs, the treatment applied depends on the originating access type. +- A service feature request is received from the originating party: e.g. feature activator in a FACILITY message (DP: O\_Mid\_Call). + +For a call originating from a B-ISDN DSS2 interface, the caller also receives an ALERTing message or under certain conditions a PROgress message containing progress indicator information set to "in-band information or pattern now available". + +For SS No. 7 B-ISUP, an Address Complete Message (ACM) is sent. + +- The O\_No\_Answer event, which is an IN event, occurs. That is, it can only occur when an O\_No\_Answer trigger is assigned and detected or when requested by a RequestReportBCSMEVENT. If the O\_No\_Answer timer expires or an indication of the T\_No\_Answer event is received before an O\_Answer event is detected (i.e. before the called party answers), the CCF/SSF reports the event to the SCF. The event indication received that causes call processing to move to the O\_No\_Answer DP depends upon the event reason (cause value) as defined according to ITU-T Q.1238.2 "O\_BCSM: Mapping Cause value to DP". +- The O\_Called\_Party\_Busy event occurs when an indication of a T\_Busy event specifying user busy is received from the terminating portion of the call (i.e. network-determined-user-busy). This event also occurs when an indication of a Call Rejected event specifying user busy (i.e. user-determined-user-busy, user not reachable) is received from the terminating portion of the call. In addition to these busy events, "Call Rejected" conditions are also treated as O\_Called\_Party\_Busy events. In this case, the terminating portion of the call is cleared. The events that cause call processing to move to the O\_Called\_Party\_Busy DP + +depend on the event reason (cause value) as defined according to the "O\_BCSM: Mapping Cause Value to DP" in ITU-T Q.1238.2. + +- The O\_Abandon event occurs when an indication of clearing or of originating party abandon is received. This event causes call processing to move to the O\_Abandon DP. + +**Corresponding Q.2931 call state:** Outgoing Call Proceeding (N3). + +##### 6.3.2.1.8 O\_Alerting + +**Entry event:** O\_Term\_Seized event (DP: O\_Term\_Seized). + +###### **Functions:** + +- Wait for the terminating party to answer for a call originating from a B-ISDN DSS2 interface, the caller also receives an ALERTing message or, under certain conditions, a PROGress message containing progress indicator information set to "in-band information or pattern now available". +- An indication of a call progress event may be received from the terminating call portion. This may result in a call progress indication being sent backward, e.g. CPG being sent in SS No. 7 B-ISUP (if the originating access is a SS No. 7 B-ISUP interface) or an ALERTing or PROGress message being sent on a B-ISDN DSS2 interface (if the originating access is a B-ISDN interface). + +**Information available:** When the CCF/SSF is in this PIC, it is assumed the CCF/SSF has the following information available and associated with the originating portion of the call: + +For a DSS2 interface that supports 64 kbit/s based ISDN circuit mode services or for a SS No. 7 B-ISUP interface that supports ISUP parameters: + +- Information as per the O\_Null PIC. +- Analysis Results – See description in the Analyse\_Information PIC. +- Routing Information – See description in the Select\_Route PIC. +- Feature Activation Information – See description below: +A service feature request is received from the originating party: e.g. ISDN feature activator. + +For a DSS2, or for a SS No. 7 B-ISUP: + +- Collected Information as defined for the Collect\_Information PIC. +- Service Profile and Access Parameter Information – See description in the Analyse\_Information PIC. +- Analysis Results – See description in the Analyse\_Information PIC. +- Routing Information – See description in Select\_Route PIC. + +###### **Exit events:** + +- The O\_Answer event occurs when an indication of a T\_Answer event is received from the terminating portion of the call (e.g. Q.2931 Connect message received, B-ISUP Answer message received). This event causes call processing to move to the O\_Answer DP (DP: O\_Answer). When the O\_Answer event occurs, the treatment applied is described in the Send\_Call PIC. +- A service feature request is received from the originating party: e.g. in a facility information element or in a FACILITY message. (DP: O\_Mid\_Call). +- A route failure event is detected when: + - the following conditions are met, hereafter called Route Failure Condition 3: + - O\_Called\_Party\_Busy event or O\_No\_Answer event occurs (as specified below); + +- b) the forwarding condition is met, as specified by the ForwardingCondition parameter; +- c) there are more destination addresses left to try. + +NOTE – The Route Failure event takes precedence over the O\_Called\_Party\_Busy and O\_No\_Answer events. + +In this case, the originating call portion returns to the Select\_Route PIC if this event is not detected at a DP (e.g. more CDPNs left to try). Otherwise this event causes call processing to move to the O\_Route\_Select\_Failure DP [e.g. User Busy, Subscriber absent (not reachable) or O\_No\_Answer DP or O\_Exception] dependent upon the event reason (cause value) as defined according to the "O\_BCSM: Mapping Cause value to DP" in ITU-T Q.1238.2. + +- The O\_No\_Answer event from this PIC is the same as the O\_No\_Answer event defined as an Exit Event from the Send\_Call PIC. That is, the event indication received that causes call processing to move to the O\_No\_Answer DP depends upon the event reason (cause value) as defined according to "O\_BCSM: Mapping Cause value to DP" in ITU-T Q.1238.2. +- From this PIC, the O\_Called\_Party\_Busy event occurs either: + - i) when a Call Rejected event specifying user busy is received; or + - ii) when an indication of a Call Rejected event not specifying busy is received from the terminating call portion (as described in the Send\_Call PIC). + +In addition, for a call to a B-ISDN DSS2 user, after the SETUP message is offered and an ALERTing message has been received (i.e. the terminating call portion is in the T\_Alerting PIC), the B-ISDN DSS2 user may reject the call. This Call Rejected event is treated as an O\_Called\_Party\_Busy event by the originating call portion (DP: O\_Called\_Party\_Busy). + +The event that causes call processing to move to the O\_Called\_Party\_Busy DP depends upon the event reason (cause value) as defined according to "O\_BCSM: Mapping Cause value to DP" in ITU-T Q.1238.2. + +- The O\_Abandon event occurs when an indication of clearing or of originating party abandon is received. This event causes call processing to move to the O\_Abandon DP. + +**Corresponding Q.2931 call state:** Call Delivered (N4). + +##### 6.3.2.1.9 O\_Active + +**Entry event:** Indication from the terminating half BCSM that the call is accepted and answered by terminating party (DP: O\_Answer). + +**Functions:** In this PIC several processes may be initiated: + +- Connection established between originating and terminating party. Message accounting/charging data may be being collected. Call supervision is being provided. +- The called party may be put on hold and returned to the active phase by a service logic. +- The called party may be put on hold by a service logic and when the calling party disconnects, the calling party can be reconnected to the held call by the Reconnect operation. The calling user receives appropriate information (e.g. alerting) and a reconnection timer is applied. +- The calling party may request Modification of the connection. The called user receives a Modification Request. The calling user receives appropriate information (e.g. Modify Acknowledge) and a reconnection timer is applied. + +**Information available:** Once the CCF/SSF has received an indication from the terminating half BCSM that the call has been answered, it is assumed the CCF/SSF has the following information available and associated with the originating portion of the call: + +For a DSS2 interface that supports 64 kbit/s based ISDN circuit mode services or for a SS No. 7 B-ISUP interface that supports ISUP parameters: + +- Information as per the O\_Alerting PIC. +- Feature Activation – A service or feature request from the originating party (e.g. in a facility information element or a FACILITY message) (O\_Mid\_Call DP). + +For a DSS2 or for a SS No. 7 B-ISUP interface: + +- Information as per the O\_Alerting PIC. +- Connection Modification – A request to change the connection parameters by the connection originator (O\_Modify\_Request DP). + +###### **Exit events:** + +- A service/service feature request is received from a party (e.g. a feature activator, or a HOLD or RETRIEVE from the originating party only, in a facility information element or a FACILITY message). The detection of this event causes call processing to move to the O\_Mid\_Call DP. +- A disconnect indication is received from the terminating party via the terminating half BCSM. This event causes call processing to move to the O\_Suspend DP. A disconnect timing is associated with this BCSM transition. +- A disconnect indication (e.g. Q.2931 disconnect message, SS No. 7 B-ISUP release message) is received from the originating party. This event causes call processing to move to the O\_Disconnect DP. +- An indication of expiration of the reconnection timer is received (O\_Exception). +- A connection failure occurs (O\_Exception). +- A RESTART message is received (O\_Exception). + +###### **Comments:** + +- If originating party abandons call while suspended at O\_Answer DP a transition to DP: O\_Abandon shall occur. +- Disconnect treatment and timing is different for call attempts originating from B-ISDN DSS2 and B-ISUP interfaces. + +**Corresponding Q.2931 call state:** Active (N10). + +Q.2931 call states corresponding to disconnect: Release indication (N12) and Release request (N11). + +##### **6.3.2.1.10 O\_Suspended** + +**Entry event:** A suspend indication is received from the T\_BCSM when the terminating party has disconnected (e.g. DSS2 RELEASE message, DSS2 RESTART message, B-ISUP RELEASE message, B-ISUP Reset message, B-ISUP SUSpend message) (DP: O\_Suspend). + +###### **Functions:** + +- The connection between the originating and terminating party is maintained and depending on the incoming network connection, appropriate backward signalling takes place. + - In case that a disconnect indication is received from the T\_BCSM, this PIC is immediately exited to the O\_Disconnect DP without any action. As an option, the call can be continued for an appropriate period in order to offer follow-on initiated by O\_Mid\_Call DP. + - If the re-answer indication from the T\_BCSM is received, the originating and terminating parties are reconnected. + +- Other features which might be required during this PIC are not described in this IN Capability Set BCSM. +- The called party may be put on hold and returned to the active phase by a service logic. +- The called party may be put on hold by a service logic and when the calling party disconnects, the calling party can be reconnected to the suspended call by the Reconnect operation. The calling user receives appropriate information (e.g. alerting) and a reconnection timer is applied. The timer may have been started in the active phase. + +**Information available:** It is assumed that the information available in this PIC is the same as the information available in the O\_Active PIC. + +###### **Exit events:** + +- Connection to the terminating party is resumed. The O\_BCSM returns to the O\_Active PIC. This event causes call processing to move to the O\_Re-answer DP. +- A service feature request is received from the originating party, e.g. feature activator of facility or a new reply from calling party (Reconnect procedure). The detection of this event causes call processing to move to the O\_Mid\_Call DP. +- A disconnection indication is received from the originating party. This event causes call processing to move to the O\_Disconnect DP. +- A disconnection indication is received from the terminating party. This event causes call processing to move to the O\_Disconnect DP. +- An indication of expiration of the timer waiting for re-answer request is received from the T\_BCSM. This event causes call processing to move to the O\_Disconnect DP. +- A trigger at O\_Mid\_Call is not initiated during an appropriate period (DP: O\_Disconnect). +- An indication of expiration of the calling party reconnection timer is received (O\_Exception). +- An exception event is encountered (O\_Exception). + +NOTE 1 – A Call Retention timer may exist. Disconnect treatment and timing is different for call reconnection, call suspension and call retention. + +NOTE 2 – After the release of the outgoing connection, the originating party may initiate another call, e.g. follow-on calling. + +##### 6.3.2.1.11 O\_Exception + +**Entry event:** An exception condition is encountered (as described above for each PIC). + +**Functions:** Default handling of the exception condition is being provided. This includes general actions necessary to ensure no resources remain inappropriately allocated, such as: + +- If any relationships exist between the SSF and SCF(s), send an error information to the SCF(s) closing the relationships and indicating that any outstanding call handling instructions will not run to completion (Note). +- If an SCF previously requested that call parameters be provided at the end of the call (see the CallInformationRequest operation), these should be included in the error information. +- The CCF/SSF should make use of vendor-specific procedures to ensure release of resources within the CCF/SSF so that bearer connection resources, signalling connection resources, and other resources are made available for new calls. + +NOTE – Depending on the connection view state this should be handled in the physical plane via an ABORT protocol procedure to close the relationship (i.e. close the TCAP transaction) or via the sending of an EntityReleased operation with the relevant cause. This indicates in both cases that any outstanding operations on the corresponding entity (leg or CS) will not be run to completion. + +**Information available:** Once the CCF/SSF has determined an exception condition has occurred, it is assumed the CCF/SSF has information available as to when the exception within the PIC occurred. + +**Exit event:** Default handling of the exception condition by the CCF/SSF completed (BCSM transition to O\_Null PIC). + +#### 6.3.2.2 Terminating BCSM + +The terminating half of the BCSM corresponds to that portion of the BCSM associated with the terminating party (see Figure 2). + +![Figure 2/Q.1237 – Terminating BCSM for ITU-T Q.1237: Basic set of transitions. This state transition diagram shows the flow of a call through various states: T_Exception, T_Null, Authorize_Termination_Attempt, Select_Facility, Present_Call, T_Alerting, T_Active, and T_Suspended. Transitions are triggered by events like Termination_Attempt, Termination_Denied, T_Busy, SS No. 7 failure, presentation_failure, call_rejected, T_No_Answer, T_active_failure, T_Re-answer, T_suspend_failure, T_Disconnect, T_Abandon, T_Mid_Call, Calling Party, Called Party, T_Suspend, T_Bearer_Active, T_Modify_Request, and T_Modify_Result. A dashed box on the right contains sub-states T_Bearer_Active and T_Bearer_Modify with transitions Create Subordinate and Remove Subordinate.](eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg) + +``` + +stateDiagram-v2 + [*] --> T_Exception + T_Exception --> T_Null + T_Null --> Authorize_Termination_Attempt : Termination_Attempt + Authorize_Termination_Attempt --> T_Exception : Termination_Denied + Authorize_Termination_Attempt --> Select_Facility : Termination_Attempt_Authorized + Select_Facility --> T_Exception : T_Busy + Select_Facility --> Present_Call : Facility_Selected_and_Available + Present_Call --> T_Exception : SS No. 7 failure, presentation_failure + Present_Call --> T_Alerting : Call_Accepted + T_Alerting --> T_Exception : call_rejected, T_No_Answer + T_Alerting --> T_Active : T_Answer + T_Active --> T_Exception : T_active_failure + T_Active --> T_Suspended : T_Suspend + T_Suspended --> T_Exception : T_suspend_failure + T_Suspended --> T_Active : reconnect + T_Suspended --> [*] : T_Disconnect + T_Active --> [*] : T_Abandon + T_Active --> T_Mid_Call : T_Mid_Call + T_Mid_Call --> T_Exception : T_Abandon + T_Mid_Call --> T_Bearer_Active : Create Subordinate + T_Bearer_Active --> T_Bearer_Modify : T_Modify_Request + T_Bearer_Modify --> T_Bearer_Active : T_Modify_Result + T_Bearer_Active --> [*] : Remove Subordinate + +``` + +Figure 2/Q.1237 – Terminating BCSM for ITU-T Q.1237: Basic set of transitions. This state transition diagram shows the flow of a call through various states: T\_Exception, T\_Null, Authorize\_Termination\_Attempt, Select\_Facility, Present\_Call, T\_Alerting, T\_Active, and T\_Suspended. Transitions are triggered by events like Termination\_Attempt, Termination\_Denied, T\_Busy, SS No. 7 failure, presentation\_failure, call\_rejected, T\_No\_Answer, T\_active\_failure, T\_Re-answer, T\_suspend\_failure, T\_Disconnect, T\_Abandon, T\_Mid\_Call, Calling Party, Called Party, T\_Suspend, T\_Bearer\_Active, T\_Modify\_Request, and T\_Modify\_Result. A dashed box on the right contains sub-states T\_Bearer\_Active and T\_Bearer\_Modify with transitions Create Subordinate and Remove Subordinate. + +Figure 2/Q.1237 – Terminating BCSM for ITU-T Q.1237: Basic set of transitions + +The following information is available at all PICs in the T-BCSM: + +- Same information as associated with the originating BCSM is assumed to be available. See subclause defining the information available at all PICs in the O\_BCSM. +- Called Party Class of Service (where locally available, e.g. subscriber profile including called party category information). +- Call Reference (where locally assigned in the switch). + +- Called Party Terminal Type – See ITU-T Q.1290. The SCF uses this to determine the most appropriate form of user-interaction to use (e.g. in-band announcements). This information may only be available at terminating local exchanges. +- Called Party Facility Restriction Level (FRL) – The permission level associated with an outgoing facility, e.g. trunk line. +- Called Party BGID (Business Group Identity) – The Basic Business Group or Multiswitch Business Group Identity of the called party, e.g. group-based services. +- Service Compatibility ID – See ITU-T Q.1290. This information is received from the originating call portion and may be enhanced by CCF/SSF. +- Charge Number – See ITU-T Q.1290. This information is available at the CCF/SSF for a B-ISDN DSS2 interface served by the CCF/SSF and may be available for a SS No. 7 B-ISUP interface. +- Called Party's Carrier, Carrier Identification Code, Carrier Selection; Route Index; and Travelling Class Mark. +- Called Facility Group – See ITU-T Q.1290. Available on DSS2 or SS No. 7 B-ISUP interfaces. +- Called Facility Group Member – See ITU-T Q.1290. Available on DSS2 or SS No. 7 B-ISUP interfaces. + +The above information applies in addition to Signalling Information received from the signalling interface and from the peer O\_BCSM. The Signalling Information depends on the signalling interface arrangement applied: DSS2, B-ISUP, etc. The descriptions for each of the PICs in the terminating half of the BCSM are described below. + +NOTE – See subsequent subclause description on "BCSM Indications for the CS-3 Call Model" for more information concerning PICs. + +##### 6.3.2.2.1 T\_Null + +**Entry event:** Disconnect and clearing of a previous connection (DPs: T\_Disconnect or T\_Abandon), or default handling of exceptions by CCF/SSF completed. + +**Function:** Interface (DSS2/B-ISUP) is idled (no connection exists, no connection reference exists, etc.). Supervision is being provided. + +**Information available:** Once the CCF/SSF has detected the Termination\_Attempt event, it is assumed that the CCF/SSF has the information corresponding to the Signalling Information received from the signalling interface (e.g. as a Setup service request message is received like DSS2 Setup, B-ISUP IAM) available and associated with the terminating portion of the call. + +The above information applies in addition to the information available at all PICs in the T\_BCSM. + +NOTE 1 – Information associated with the originating portion of the call as per the Send\_Call PIC is assumed to be available – this information is received from the originating call portion, i.e. the peer O\_BCSM. + +Any information relating to switch-based features that have already been invoked for the call will also be available. + +###### Exit events: + +- Indication of incoming call received from originating half BCSM (DP: Termination\_Attempt). +- The following exception exit event is applicable to this PIC: T\_Abandon. If the call encounters T\_Abandon during PIC processing, the exception event is not visible because there is no corresponding DP. + +NOTE 2 – The T\_Abandon event occurs when an indication of call disconnection is received from the originating portion of the call before the call has been answered, i.e. when the calling party disconnects. + +For example, this event can result from one of the following: + +- the CCF/SSF receives a call clearing message from a caller served by a B-ISDN interface; +- SSF receives a Release Message from a SS No. 7 B-ISUP interface. + +**Corresponding Q.2931 call state:** Null (N0). + +##### 6.3.2.2.2 Authorize Termination Attempt + +**Entry event:** Termination\_Attempt event (DP: Termination\_Attempt). + +**Function:** Verifies the authority to route this connection to the terminating access, e.g. check business group restrictions, restricted incoming access or bearer capability compatibility. + +**Information available:** It is assumed that the CCF/SSF has the same information available for the terminating connection portion after the Termination\_Attempt\_Authorized event is detected as it does when the Termination\_Attempt event is detected in the T\_Null PIC. + +- Information as per the T\_Null PIC. +- Service Profile and Access Parameter Information of the Terminating Access, if provisioned and enabled. +- Authorization result – If the CCF/SSF determines that the termination attempt is denied, the cause of the failed authorization is also known. + +###### Exit events: + +- Termination\_Attempt\_Authorized event. This event occurs when the switch has verified the authority to terminate the connection to the terminating access (DP: Termination\_Attempt\_Authorized). +- The Termination Denied event occurs when the authority to route this connection to the terminating user is denied. (This causes a BCSM transition to the Termination\_Denied DP.) +- The T\_Abandon event occurs when an indication of clearing is received from the originating portion of the connection (DP: T\_Abandon). + +##### 6.3.2.2.3 Select facility + +**Entry event:** Termination\_Attempt\_Authorized event (DP: Termination\_Attempt\_Authorized) or a B-ISDN failure occurs causing a re-attempt in SS No. 7 B-ISUP or DSS2. The failure in the Present\_Call can be caused by a timer expiry upon sending the first Initial Address Message (IAM) or the first SETUP message. + +**Function:** The busy/idle status of the terminating access is determined. + +- For a connection terminating to a B-ISUP interface, network-determined user busy is the detection of one or more of the following cause values in an Incoming Resources Rejected Request: + - Resource Unavailable – Unspecified: There are no idle Signalling Identification Values. + - No VPCI/VCI Available: There is no VPCI or VCI available. + - User Cell Rate Not Available: There is a lack of bandwidth for the connection. +- For a call terminating to a B-ISDN DSS2 interface, network-determined user busy is the detection of one or more of the following conditions: + - VPCI/VCI Not Available: There are no VPCIs or VCIs available to allocate to the connection. + +- Requested VPCI/VCI Not Available: The requested VPCI or VCI is not available to allocate to the connection. +- Quality of Service unavailable: Requested Quality of Service or End-to-End Transit Delay not acceptable. +- Resources Unavailable – Unspecified: Requested Cell rate in the ATM Traffic Descriptor is not available. + +**Information available:** When the Facility\_Selected and Available event is detected, it is assumed the following information is available and associated with the terminating portion of the call with restrictions as detailed below: + +- Information as per the Authorize\_Termination\_Attempt PIC. In particular, the authorized and available VPCI/VCI for the terminating interface must be known. +- Facility Group – See ITU-T Q.1290. For calls routed out of this CCF/SSF, this identifies the Virtual Path(s) that has been selected on which to route the call. +- Facility Group Member – See ITU-T Q.1290. For calls out of this CCF/SSF, this identifies the Virtual Channel that has been selected on which to route the call. + +###### **Exit events:** + +- Facility\_Selected\_and\_Available event: This event occurs when the terminating access is not busy (i.e. an idle resource [e.g. VPCI/VCI, call reference or channel ID] could be found). This event causes call processing to move to the Facility\_Selected\_and\_Available DP. +- A T\_Busy event occurs when the terminating access is busy (as defined above). The T\_busy event may also be detected as a result of certain maintenance actions. The event indication that causes call processing to move to the T\_Busy DP depends upon the event reason (cause value) as defined according to "T\_BCSM: Mapping Cause value to DP" in ITU-T Q.1238.2. +After detecting T\_Busy, if IN service logic is not needed on the call and no switch-based features apply, an indication of the T\_Busy event describing the type of busy (e.g. user or network) is passed to the originating call portion. If a terminating feature acts on the T\_Busy event and changes the event (e.g. as in the call Waiting feature), the event is not passed to the Originating BCSM. +- The T\_Abandon event occurs when an indication of clearing or of originating party abandon is received from the originating portion of the call. This event causes call processing to move to the T\_Abandon DP. + +##### **6.3.2.2.4 Present Call** + +**Entry event:** Facility\_Selected\_and\_Available event (DP: Facility\_Selected\_and\_Available). + +**Function:** Terminating resource informed of incoming call (e.g. Q.2931 Setup message, B-ISUP IAM message). + +**Information available:** When the Call\_Accepted event is detected, it is assumed the following information is available and associated with the terminating portion of the call with restrictions as detailed below: + +- Information as per the T\_Null PIC. +- Facility Group, Facility Group Member – See description in the Select Facility PIC. +- Information regarding the connection – This information includes whether the call is end-to-end SS No. 7 or not, and whether the originating access is ISDN or B-ISDN as determined by the presence of Narrow-band and Broadband Bearer Capability Information Elements or Parameters in the DSS2 SETUP or B-ISUP IAM. +- Service Profile and Access Parameter Information of the Terminating Access, if provisioned and enabled. + +###### **Exit events:** + +- Terminating party is being alerted (e.g. Q.2931 ALERTING message, B-ISUP ACM message). This event causes call processing to move to the Call\_Accepted DP. +- Call is accepted and answered by terminating party (e.g. Q.2931 Connect message received, B-ISUP answer message received). This event causes call processing to move to the T\_Answer DP. +- The T\_No\_Answer event occurs when the terminating party does not answer before the No\_Answer timer expires or when a B-ISDN user rejects the call with an explicit "no answer" indication. An indication of T\_No\_Answer event is passed to the originating half of the BCSM. The event indication received that causes call processing to move to the T\_No\_Answer DP depends upon the event reason (cause value) as defined according to the "T\_BCSM: Mapping Cause value to DP" in ITU-T Q.1238.2. +- The T\_Abandon event occurs when an indication of clearing or of originating party abandon is received from the originating portion of the call. This event causes call processing to move to the T\_Abandon DP. +- A timer expiry upon sending the second DSS2 SETUP message or the first Initial Address Message (IAM) in B-ISUP (SS No. 7 failure). This event causes call processing to move to the Select Facility PIC. +- Presentation Failure exception event may happen if the call cannot be presented by the T-Busy event. +- The T-Busy event occurs if the call cannot be presented due to a B-ISDN user determined busy, B-ISUP release message with busy cause, not reachable subscriber condition; this event is notified to the originating call portion (send Call PIC). The event indication that causes call processing to move to the T\_Busy DP depends upon the event reason (cause value) as defined according to "T\_BCSM: Mapping Cause value to DP" in ITU-T Q.1238.2. Otherwise this event causes call processing to move to the T\_Exception. + +**Corresponding Q.2931 call state:** Call present (N6). + +##### **6.3.2.2.5 T\_Alerting** + +**Entry event:** Terminating party is being alerted of incoming connection request (DP: Call\_Accepted). + +**Function:** An indication is sent to the originating half BCSM that the terminating party is being alerted. Continued processing of call setup (e.g. retransmit of SETUP message in DSS2) is taking place. Waiting for the call to be answered by terminating party. + +**Information available:** Once the terminating party is being alerted of the incoming call, it is assumed that the CCF/SSF has the following information available and associated with the terminating portion of the call: + +- Information as per the Present\_Call PIC. +- Called Party's Indicator and the Charge Indicator may also be available. + +###### **Exit events:** + +- Connection is accepted and answered by terminating party (e.g. Q.2931 CONNECT message received, B-ISUP answer message received). This event causes call processing to move to the T\_Answer DP. +- The following exception exit events are applicable to this PIC: call rejected, T\_No\_Answer, T\_Busy and T\_Abandon. +- Call rejected exception event may happen when a B-ISDN DSS2 user rejects a call while being alerted. + +- The T\_No\_Answer event occurs when the terminating party does not answer before the No\_Answer timer expires or when a user rejects the call with an explicit "no answer" indication. An indication of T\_No\_Answer event is passed to the originating half of the BCSM. The event indication received that causes call processing to move to the T\_No\_Answer DP depends upon the event reason (cause value) as defined according to "T\_BCSM: Mapping Cause value to DP" in ITU-T Q.1238.2. +- The T\_Busy event occurs if the call cannot be presented, due to e.g. B-ISDN DSS2 user determined busy, B-ISUP release message with busy cause, not reachable subscriber, etc. This event causes call processing to move to the T\_Busy DP and is notified to the originating call portion (Alerting PIC). The events that cause call processing to move to the T\_Busy DP depends upon the event reason (cause value) as defined according to "T\_BCSM: Mapping Cause value to DP" in ITU-T Q.1238.2. Otherwise this event causes call processing to move to the T\_Exception. +- The T\_Abandon event occurs when an indication of clearing or of originating party abandon is received from the originating portion of the call. This event causes call processing to move to the T\_Abandon DP. + +**Comment:** For terminations to SS No. 7 B-ISUP interfaces, this PIC is entered upon the receipt of an address complete (ACM) message. + +**Corresponding Q.2931 call states:** Call received (N7), Connect request (N8), and Incoming Call Proceeding (N9). + +##### 6.3.2.2.6 T\_Active + +**Entry event:** Connection is accepted and answered by terminating party (e.g. Q.2931 Connect message received, B-ISUP answer message received) (DP: T\_Answer). + +**Functions:** In this PIC several processes may be initiated: + +- An indication is sent to the origination half BCSM that the terminating party has accepted and answered the call. Connection established between originating and terminating party. Call supervision is being provided. +- The calling party may be put on hold and returned to the active phase by a service logic. +- The calling party may be put on hold by a service logic and when the called party disconnects, the called party can be reconnected to the held call by the Reconnect operation. The called user receives appropriate information (e.g. alerting) and a reconnection timer is applied. The timer may have been started in the active phase. The calling party may request modification of the connection. The called party receives a request to modify the connection, and returns a MODIFY ACKNOWLEDGE in DSS2 or a MODIFY Confirm in B-ISUP. In DSS2 the called party sets a timer and awaits receipt of CONNECTION AVAILABLE. + +**Information available:** Once the call is accepted and answered by the terminating party, it is assumed the following information is available and associated with the terminating portion of the call with restrictions as noted. + +For a DSS2 interface that supports 64 kbit/s based ISDN circuit mode services or for a SS No. 7 B-ISUP interface that supports ISUP parameters: + +- Information as per T\_Alerting. +- Feature Activation – See description below. A service feature request is received from a party: [e.g. in a Q.2932 FACILITY message and Q.932 ISDN feature activator, and Q.932 HOLD or RETRIEVE message (for a terminating party only)]. + +For a DSS2 or for a SS No. 7 B-ISUP interface: + +- Information from the Authorize\_Termination\_Attempt PIC, specifically, the Cell Rate possibly returned to the connection originator in the DSS2 CONNECT message or B-ISUP ANswer Message. +- Connection Modification – A connection modification request from the originating party (e.g. DSS2 Q.2963.1 MODIFY REQUEST, B-ISUP Q.2725.2 MODify request) (T\_Modify\_Request DP). Note that connection modification is available only to the connection owner, i.e. the connection originator. + +###### **Exit events:** + +- A service/service feature request is received from a party (e.g. feature activator, Q.931 HOLD or RETRIEVE message from a terminating party only, in a Facility information element or in a FACILITY message). The detection of this event causes call processing to move to the T\_Mid\_Call DP. +- A disconnect indication (e.g. Q.2931 disconnect message, SS No. 7 B-ISUP release message) is received from the terminating party. This event causes call processing to move to the T\_Suspend DP. +- A disconnect indication is received from the originating party via the originating half BCSM. This event causes call processing to move to the T\_Disconnect DP. +- An indication of expiration of the reconnection timer is received (T\_Exception). +- A connection failure occurs (T\_Exception). +- A RESTART message is received (T\_Exception). + +###### **Comments:** + +- If originating party abandons call while suspended at T\_Answer DP a transition to DP: T\_Abandon shall occur. +- Disconnect indications and treatment are asymmetrical in the way disconnect timing is applied. + +**Corresponding Q.2931 call state:** Active (N10). + +**Q.2931 call states corresponding to T\_Disconnect:** Release indication (N12), and Release request (N11). + +##### **6.3.2.2.7 T\_Suspended** + +**Entry event:** An indication is received from the outgoing network that the terminating party has disconnected (e.g. DSS2 Release message, or B-ISUP RELease message) (DP: T\_Suspend). + +**Function:** The physical resources associated with the call remain connected. + +According to the received indication the following applies: + +- A suspend indication is sent to the originating half BCSM. +- For a SS No. 7 B-ISUP interface or a B-ISDN DSS2 interface, in the case that a disconnect indication (e.g. Q.2931 release message, SS No. 7 B-ISUP release message) is received from the terminating party, this PIC is immediately exited to the T\_Disconnect DP without any action. +- In the following case, the timer is started and the call waits for re-answer request from the terminating party: + - For a SS No. 7 B-ISUP interface, in case of receiving network initiated suspend message. + +If re-answer request (e.g. SS No. 7 B-ISUP resume message) is received from the terminating party before the timer expires, the originating and terminating parties are reconnected. + +NOTE – Both a Call Resume timer and a Call Retention timer may exist in this PIC. IN implementations may use a single timer for both conditions. + +**Information available:** While in the T\_Suspended PIC, it is assumed that the CCF/SSF has the following information available and associated with the terminating call portion. + +- Information as per the T\_Active PIC. + +###### **Exit events:** + +- The terminating party re-answers or a resume message is received before the timer expires; the T\_BCSM returns to the T\_Active PIC (DP: T\_Re-answer). +- The timer expires (DP: T\_Disconnect). +- A disconnection indication is received from the terminating party (DP: T\_Disconnect). +- A disconnection indication is received from the originating party (DP: T\_Disconnect). +- An exception event is encountered (T\_Exception). + +##### **6.3.2.2.8 T\_Exception** + +**Entry event:** An exception condition is encountered (as described above for each PIC). + +**Functions:** An indication of the exception condition is sent to the originating half BCSM. Default handling of the exception condition is being provided. This includes general actions necessary to ensure no resources remain inappropriately allocated, such as: + +- If any relationships exist between the SSF and SCF(s), send an error information to the SCF(s) closing the relationships and indicating that any outstanding call handling instructions will not be run to completion (Note). +- If an SCF previously requested that call parameters be provided at the end of the call (see the CallInformationRequest operation), these should be included in the error information. + +The CCF/SSF should make use of vendor-specific procedures to ensure release of resources within the CCF/SSF so that DSS2 interfaces, B-ISUP interfaces, and other resources are made available for new calls. + +NOTE – Depending on the connection view state this should be handled in the physical plane via an ABORT protocol procedure to close the relationship (i.e. close the TCAP transaction) or via the sending of an EntityReleased operation with the relevant cause. This indicates in both cases that any outstanding operations on the corresponding entity (leg or CS) will not be run to completion. + +**Information available:** Once the CCF/SSF has determined an exception condition has occurred, it is assumed the SSF/CF has information available as when the exception within the PIC occurred. + +**Exit event:** Default handling of the exception condition by CCF/SSF completed (BCSM transition to T\_Null PIC). + +#### **6.3.2.3 Subordinate Process for Bearer Modelling** + +For B-ISDN, the BCSM creates a subordinate process to model the status of the bearer connection. + +The subordinate process is created in the O/T\_Bearer\_Active PIC, when the BCSM encounters the O/T\_Answer\_DP. The subordinate process is removed when the O-BCSM transitions to the O/T\_Disconnect\_DP, or on any transition of the O/T-BCSM to exception. For the detailed set of O\_BCSM transitions described in ITU-T Q.1238, the subordinate process must be removed on any transition from O\_Mid\_Call\_DP to any PIC other than O\_Active or O\_Suspend. + +##### 6.3.2.3.1 O\_BCSM Subordinate Process + +The subordinate process transitions to O\_Bearer\_Modify PIC on receipt of a modification request. It returns to the O\_Bearer\_Active PIC through the O\_Modify\_Result DP when the modification request is acknowledged, or rejected, or when modification fails. + +###### 6.3.2.3.1.1 O\_Bearer\_Active + +**Entry event:** Request from O\_BCSM to create subordinate process on transition of call to O\_Active state (DP: O\_Answer). + +###### Functions: + +- Both call and bearer are monitored in the active state. + +###### Exit events: + +- Indication of desire to update (modify) the connection characteristics is received (e.g. reception of a MODIFY request from originating user) (DP: O\_Modify\_Request). +- A service feature request is received from the originating party (DP: O\_Mid\_Call), and the call transitions to any PIC other than O\_Active and O\_Suspend. +- An exception event is encountered in the O-BCSM (O\_Exception). +- Connection released in the O\_BCSM by remote party (DP: O\_Suspend), and the O-BCSM transitions to disconnect (DP: O\_Disconnect). +- Connection released in the O\_BCSM by originating party (DP: O\_Disconnect). + +###### 6.3.2.3.1.2 O\_Bearer\_Modify + +**Entry event:** Indication of desire to update (modify) the connection characteristics is received (e.g. reception of a MODIFY request from originating user) (DP: O\_Modify\_Request). + +###### Functions: + +- The authority/ability of the calling party to modify the connection is verified. If updating is impossible or not permitted, the active state is resumed (transition to O\_Active PIC via O\_Modify\_Result DP), and a message is sent to the originating party (e.g. MODIFY reject). +- If the modification is possible, an appropriate message is sent to the next relay. +- An answer (e.g. MODIFY acknowledgement/confirm/reject) is awaited. If a reject message is obtained, the connection is resumed to the active state, and a message is sent to the originating party (e.g. MODIFY reject). If an acknowledgement message is received, local network resources are modified and the modification is confirmed, both to the originating party and to the other end of the connection (MODIFY confirm). + +###### Exit events: + +- Connection update completed successfully (DP: O\_Modify\_Result-modifyAcknowledge). +- Connection update unauthorized or unsuccessful (DP: O\_Modify\_Result-modifyReject). +- Connection modification failure (DP: O\_Modify\_Result-modifyReject). +- A service feature request is received from the originating party (DP: O\_Mid\_Call), and the call transitions to any PIC other than O\_Active and O\_Suspend. +- An exception event is encountered in the O\_BCSM (O\_Exception). +- Connection released in O\_BCSM by remote party while attempting modification (DP: O\_Suspend), and the O-BCSM subsequently transitions to disconnect (DP: O\_Disconnect). +- Connection released in O\_BCSM by originating party while attempting modification (DP: O\_Disconnect). + +##### 6.3.2.3.2 T\_BCSM Subordinate Process + +The subordinate process transitions to T\_Bearer\_Modify PIC on receipt of a modification request. It returns to the T\_Bearer\_Active PIC through the T\_Modify\_Result DP when the modification request is acknowledged, or rejected, or when modification fails. + +###### 6.3.2.3.2.1 T\_Bearer\_Active + +**Entry event:** Request from T\_BCSM to create subordinate process on transition of call to T\_Active state (DP: T\_Answer). + +###### **Function:** + +- Both call and bearer are monitored in the active state. + +###### **Exit events:** + +- Indication of desire to update (modify) the connection characteristics is received (e.g. reception of a MODIFY request from originating user) (DP: T\_Modify\_Request). +- An exception event is encountered in the T\_BCSM (T\_Exception). +- Connection released by connection originator in the T\_BCSM while attempting modification (DP: T\_Disconnect). +- Connection released by terminating party in the T\_BCSM during modification request (DP: T\_Suspend), that subsequently transitions to disconnect (DP: T\_Disconnect). + +###### 6.3.2.3.2.2 T\_Bearer\_Modify + +**Entry event:** Indication of desire to update (modify) the connection characteristics is received (e.g. reception of a MODIFY request from originating user) (DP: T\_Modify\_Request). + +###### **Functions:** + +- The authority/ability of the calling party to modify the connection is verified. If updating is impossible or not permitted, the active state is resumed (transition to T\_Active PIC via T\_Modify\_Result DP), and a message is sent to the originating party (e.g. MODIFY reject). +- If the modification is possible, an appropriate message is sent to the next relay. +- An answer (e.g. MODIFY acknowledgement/confirm/reject) is awaited. If a reject message is obtained, the connection is resumed to the active state, and a message is sent to the originating party (e.g. MODIFY reject). If an acknowledgement message is received, local network resources are modified and the modification is confirmed, both to the originating party and to the other end of the connection (MODIFY confirm). + +###### **Exit events:** + +- Connection update completed successfully (DP: T\_Modify\_Result-modifyAcknowledge). +- Connection update unauthorized or unsuccessful (DP: T\_Modify\_Result-modifyReject). +- Connection modification failure (DP: T\_Modify\_Result-modifyReject). +- An exception event is encountered in the T\_BCSM (T\_Exception). +- Connection released in the T\_BCSM by connection originator while attempting modification (DP: T\_Disconnect). +- Connection released by terminating party in the T\_BCSM during modification request (DP: T\_Suspend), that subsequently transitions to disconnect (DP: T\_Disconnect). + +### 6.3.3 BCSM resume points and BCSM transitions + +The descriptions of resume points and transitions in 6.3.3/Q.1238.2 apply. + +### **6.3.4 BCSM indications for the call model** + +The descriptions of BCSM indications in 6.3.4/Q.1238.2 apply. + +### **6.3.5 Mapping from cause to DP** + +A normative mapping between signalling release cause values and DPs is defined by Mapping Tables, i.e. the table covers only cause values received by the basic call signalling. + +The tables are based on the Call States. In some cases the mapping of a particular cause value to a DP depends on the PIC in which the release message is received. This is indicated where appropriate by notes. + +This Mapping from Cause value to DP as indicated in ITU-T Q.1238 applies. The tables below show mapping for only B-ISDN cause codes. The tables for O-BCSM and respective T\_BCSM are normative, except where the table indicates that receipt of the cause value leads to the O/T\_Exception PIC. In the latter case, network operators may decide to map some of these cause values to a specific DP. + +#### **6.3.5.1 O\_BCSM: Mapping table from cause to DP** + +A flexible mapping is provided as the DP\_Route\_Select Failure is used as a possible transition, e.g. the PICs Send\_Call and O\_Alerting. The transitions are done through an internal transition in the O\_BCSM. + +The following mapping of O\_BCSM PICs is applied: + +For ease of reference, the PICs have been categorized as follows: + +- Category: Originating Call setup: +PICs: Authorize\_Origination\_Attempt, Collect\_Information, Analyse\_Information, Select\_Route, Authorize\_Call\_Setup. +- Category: Originating Stable Call: +PICs: Send-Call, O\_Alerting, O\_Active. +- Category: Originating Call Clearing: +PICs: O\_Suspended. + +See Table 1. + +**Table 1/Q.1237 – O\_BCSM: Mapping cause value to DP** + +| No. | Reason | Originating CallSetup | Originating Stable Call | | Originating CallClearing | +|-----|-----------------------------------------------|-----------------------|-------------------------|-----------|--------------------------| +| | | | (Note 1) | (Note 2) | | +| 35 | Requested VPCI/VCI not available | Exception | O_Called_Party_Busy | Exception | Exception | +| 36 | VPCI/VCI assignment failure | Route_Select_Failure | Route_Select_Failure | Exception | Exception | +| 37 | User cell rate not available | Route_Select_Failure | Route_Select_Failure | Exception | Exception | +| 45 | No VPCI/VCI available | Exception | O_Called_Party_Busy | Exception | Exception | +| 73 | Unsupported combination of traffic parameters | Route_Select_Failure | Route_Select_Failure | Exception | Exception | +| 93 | AAL parameters cannot be supported | Route_Select_Failure | Route_Select_Failure | Exception | Exception | + +NOTE 1 – A transition to Route\_Select\_Failure DP occurs directly when due to the receipt of a route failure event from the called destination (provided that no more CDPNs left to try). +NOTE 2 – Transition valid for O\_Active PIC only. + +#### 6.3.5.2 T\_BCSM: Mapping table from cause to DP + +The transitions are done through an internal transition in the BCSM. + +The following mapping of T\_BCSM PICs is applied: + +For ease of reference, the PICs have been categorized as follows: + +- Category: Terminating Call setup: +PICs: Authorize\_Termination\_Attempt, Select\_Facility\_Present\_Call, T\_Alerting. +- Category: Terminating Active Call: +PICs: T\_Active. +- Category: Terminating Call Clearing +PICs: T\_Suspended. + +See Table 2. + +**Table 2/Q.1237 – T\_BCSM: Mapping cause value to DP** + +| No. | Reason | Terminating CallSetup | Terminating Stable Call | | Terminating CallClearing | +|-----|-----------------------------------------------|-----------------------|-------------------------|-----------|--------------------------| +| | | | T-Alerting | T-Active | | +| 35 | Requested VPCI/VCI not available | T_Busy (Note 2) | T_Busy | Exception | Exception | +| 36 | VPCI/VCI assignment failure | Exception | Exception | Exception | Exception | +| 37 | User cell rate not available | Exception | Exception | Exception | Exception | +| 45 | No VPCI/VCI available | T_Busy (Note 2) | T_Busy | Exception | Exception | +| 73 | Unsupported combination of traffic parameters | Exception | Exception | Exception | Exception | +| 93 | AAL parameters cannot be supported | Exception | Exception | Exception | Exception | + +NOTE 1 – The transition to the indicated DP is valid only for Present\_Call PIC (used in ITU-T Q.1238.2). + +NOTE 2 – The transition to the indicated DP is valid except for the Authorize\_Termination\_Attempt PIC. + +NOTE 3 – The following rule applies for the stable call phase: The receipt of any cause value received during the stable call phase (O\_Active/T\_Active) shall in such states be mapped to O/T Disconnect DP. + +### 6.3.6 BCSM detection point + +The descriptions of BCSM Detection Point in 6.3.6/Q.1238.2 apply. + +### 6.3.7 DP criteria + +DP criteria are conditions that must be met in order to notify the SCF that the DP was encountered. These criteria can be assigned to a DP from the viewpoint of range of effectiveness, as identified by the trigger categories. + +The following categories are DP trigger categories, as applicable for a given DP: + +- **Individual-based** (also denoted "subscribed or line-based") + +This type of trigger category applies to each subscriber address. For example, SCF processing is invoked when a connection is originated from an address belonging to subscriber A. This criteria could be said to be specific for subscriber A. + +- **Group-based** + +This type of trigger category applies to a certain group of addresses or users. For example, when a connection origination from any user in a certain address group invokes SCF processing the trigger should apply to that specific address group. + +This type of trigger category may also apply to selected connection identifiers (VPCI/VCI). For example, when connections originated with requests for specific connection identifiers (including "no indication" for VPCI/VCI) invoke SCF processing, the trigger should apply to all connections requesting the specific connection identifiers. This type of trigger category includes Virtual Path(s) within the definition of facility group. + +This type of trigger category may also apply to selected connection parameters (e.g. Quality of Service, QoS). For example, when connections originate with requests for specific QoS invoke SCF processing, the trigger should apply to all connections requesting the specific QoS. + +This type of trigger category may also apply to a particular interface to the switch (e.g. switch port; or virtual User-Network Interface, UNI). For example, when connections that originate from specific interfaces invoke SCF processing, the trigger should apply to all connections requested at that interface. + +#### – **Switch-based** (also denoted "Office-based") + +This type of trigger category applies to the entire switch. Any connections generated in the switching system will be subject to this criteria. For example, any connection which makes access to specific terminating addresses (e.g. well-known ATM addresses) is triggered and SCF processing is invoked. + +The following are DP criteria for IN Capability Set for B-ISDN, as applicable for a given DP: + +- Trigger assigned1 (unconditional/conditional on other criteria); +- AAL Parameters; +- ATM Traffic Descriptor; +- ATM Cell Rate; +- Additional ATM Cell Rate; +- Alternative ATM Traffic Descriptor/Alternative ATM Cell Rate; +- Minimum Acceptable ATM Traffic Descriptor/Minimum ATM Cell Rate; +- Broadband Bearer capability; +- Addressing/Numbering Plan Identification (called party); +- Specific called party digit strings; +- Specific called party address; +- AESA for Called Party; +- Called party subaddress; +- Called party indicators; +- Charge indicator; +- Addressing/Numbering Plan Identification (calling party); +- Specific calling party digit strings; +- Specific calling party address; +- AESA for Calling Party; +- Calling party subaddress; +- Calling party Category; +- Feature codes or Escape Digits (e.g. \*XX, #); +- Prefixes (e.g. 0+, 00+, 011, 01, 1+); +- Access codes (e.g. 8+) for customized numbering plan; +- Specific Connection Identifier; +- End-to-End Transit Delay; +- Maximum End-to-End Transit Delay; + +--- + +1 It is possible that some DPs are always conditional. + +- Propagation Delay Counter; +- QoS Class; +- CDVT descriptor; +- Generic Identifier; +- Transit Network Selection; +- Connection Modify; +- Cause (unconditional/conditional on specific cause patterns). + +With respect to the DP criteria listed above, note that these DP criteria only apply to TDPs. DP criteria for Event Detection Points (EDPs) are addressed by the RequestReportBCSMEEvent information flow. In addition, note that one or more DP criteria may be applicable at a given DP. + +The assignment of DP criteria to a TDP and the combinations of DP criteria applicable at a given DP continue to evolve. Further DP criteria and specific assignment of DP criteria to TDPs/EDPs may evolve through future capability sets. + +Note further that the assignment of DP criteria to a TDP on either an individual, group or switch basis may have an impact on the memory and real-time performance requirements of the CCF/SSF. + +Note that the applicability of DP criteria at a given DP depends on when call processing information is available and how long it is retained. + +If network and service providers plan to implement IN services in a multi-supplier environment, they should consider formulating such requirements to ensure consistent implementations across supplier equipment. + +Such requirements should be considered carefully so as not to adversely impact memory and real-time performance aspects of CCF/SSF processing. + +#### **6.3.7.1 DP criteria, as applicable to a given TDP for IN Capability Set for B-ISDN carrying N-ISDN services** + +Narrow-band ISDN services may be implemented over a B-ISDN network by carrying ISDN signalling information in the broadband protocols. As a result, DP criteria for narrow-band services as defined in ITU-T Q.1238 may be applicable. Applicability of narrow-band DP criteria is contingent on the availability of appropriate narrow-band DSS1 or ISUP signalling information in the broadband protocol and on changes to the DP criteria descriptions to recognize the broadband bearer rather than the narrow-band bearer, e.g. connection identifier for B-ISDN rather than B-channel identifier in ISDN. A list of DP Criteria that may be available for narrow-band services is provided below as an example. + +- trigger assigned (unconditional/conditional on other criteria); +- class of service; +- specific connection identifier; +- specific digit strings; +- feature codes (e.g. \*XX, #); +- prefixes (e.g. 0+, 00+, 0–, 00–, 011, 01, 1+); +- access codes (e.g. 8+) for customized numbering plan; +- specific abbreviated dialling strings for customized numbering plan; +- specific calling party number strings; +- specific called party number strings; +- nature of address (e.g. subscriber significant number, national significant number, international number); + +- bearer capability; +- feature activation/indication (unconditional/conditional on specific feature patterns); +- facility information (unconditional/conditional on specific facility information patterns); +- cause (unconditional/conditional on specific cause patterns); +- USI Service Indicator value (unconditional/conditional on specific value that identifies an IN service/service feature). + +#### 6.3.7.2 DP criteria for IN Capability Set for B-ISDN, as applicable to a given TDP + +- 1) *Trigger assigned*2 (unconditional/conditional on other criteria) – An indicator of the armed/disarmed status of a TDP assigned on an individual, group, or switch basis. + +The trigger assigned criterion can be used by itself or in conjunction with other criteria at a TDP. If the trigger assigned criterion is unconditional at a TDP, then it is used by itself – no other DP criterion needs to be satisfied at the TDP before informing the SCF that the TDP was encountered. If the trigger assigned criterion is conditional at a TDP, then it is used in combination with other criteria at the TDP – all of the other DP criteria in the combination need to be satisfied before informing the SCF that the TDP was encountered. + +Applies at all DPs (all DPs can be provisioned as TDPs). + +- 2) *AAL Parameters* – An indicator of the ATM adaptation layer and associated parameters used for the connection as defined in ITU-T Q.2931 and ITU-T Q.2763. + +The ATM adaptation information is available at the Origination\_Attempt DP and the Termination\_Attempt DP. This criterion could be applicable at all originating and terminating DPs. Since AAL parameter information may not be analysed until the Analyse\_Information PIC (except to identify AAL type in the Collect\_Information PIC), this criterion could be applicable at the Analysed\_Info DP and beyond. The Collected\_Information DP [mandatory], Analysed\_Info DP [mandatory] and all other originating DPs that may be encountered after Origination\_Attempt [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. The Termination\_Attempt\_Authorized DP [mandatory] and all terminating DPs that may be encountered other than Termination\_Attempt\_Authorized [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. + +- 3) *ATM Traffic Descriptor* – An indicator of the forward and backward cell rates and associated traffic parameters for the connection as defined in ITU-T Q.2931. + +The ATM traffic descriptor information is available at the Origination\_Attempt DP and the Termination\_Attempt DP. This criterion could be applicable at all originating and terminating DPs. Note that the forward and backward peak cell rates may be altered at the O\_Mid Call DP by an attempt from the connection originator to modify the connection parameters (see ITU-T Q.2963.1). Since ATM Traffic Descriptor information may not be analysed until the Analyse\_Information PIC, this criterion could be applicable at the Analysed\_Info DP and beyond. The Analysed\_Info DP [mandatory] and all other originating DPs that may be encountered after Origination\_Attempt [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. The Termination\_Attempt\_Authorized DP [mandatory] and all those terminating DPs that may be encountered other than Termination\_Attempt\_Authorized [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. + +--- + +2 It is possible that some DPs are always conditional. + +- 4) *ATM Cell Rate* – An indicator of the forward and backward cell rates and associated traffic parameters for the connection as defined in ITU-T Q.2763. +- The ATM cell rate information is available at the Origination\_Attempt DP and the Termination\_Attempt DP. This criterion could be applicable at all originating and terminating DPs. Note that the forward and backward peak cell rates may be altered at the O\_Mid Call DP by an attempt from the connection originator to modify the connection parameters (see ITU-T Q.2725.2). Since ATM Cell Rate information may not be analysed until the Analyse\_Information PIC, this criterion could be applicable at the Analysed\_Info DP and beyond. The Analysed\_Info DP [mandatory] and all other originating DPs that may be encountered after Origination\_Attempt [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. The Termination\_Attempt\_Authorized DP [mandatory] and all terminating DPs that may be encountered other than Termination\_Attempt\_Authorized [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. +- 5) *Additional ATM Cell Rate* – An indicator of the forward and backward cell rates and associated traffic parameters for the connection as defined in ITU-T Q.2763. +- The additional ATM cell rate information is available at the Origination\_Attempt DP and the Termination\_Attempt DP. This criterion could be applicable at all originating and terminating DPs. Since ATM Cell Rate information may not be analysed until the Analyse\_Information PIC, this criterion could be applicable at the Analysed\_Info DP and beyond. The Analysed\_Info DP [mandatory] and all other originating DPs that may be encountered after Origination\_Attempt [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. The Termination\_Attempt\_Authorized DP [mandatory] and all those terminating DPs that may be encountered other than Termination\_Attempt\_Authorized [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. +- 6) *Alternative ATM Traffic Descriptor/Alternative ATM Cell Rate* – An indicator of the potentially negotiated forward and backward cell rates and associated traffic parameters for the connection as defined in ITU-T Q.2962.1 and ITU-T Q.2725.1. +- The alternative ATM traffic information is available at the Origination\_Attempt DP and the Termination\_Attempt DP. This criterion could be applicable at all originating and terminating DPs. Since ATM Traffic Descriptor information may not be analysed until the Analyse\_Information PIC, this criterion could be applicable at the Analysed\_Info DP and beyond. The Analysed\_Info DP [mandatory] and all other originating DPs that may be encountered after Origination\_Attempt [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. The Termination\_Attempt\_Authorized DP [mandatory] and all those terminating DPs that may be encountered other than Termination\_Attempt\_Authorized [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. +- 7) *Minimum Acceptable ATM Traffic Descriptor/Minimum ATM Cell Rate* – An indicator of the potentially negotiated forward and backward cell rates and associated traffic parameters for the connection as defined in ITU-T Q.2962.1 and ITU-T Q.2725.1. +- The minimum ATM traffic information is available at the Origination\_Attempt DP and the Termination\_Attempt DP. This criterion could be applicable at all originating and terminating DPs. Since ATM Traffic Descriptor information may not be analysed until the Analyse\_Information PIC, this criterion could be applicable at the Analysed\_Info DP and beyond. The Analysed\_Info DP [mandatory] and all other originating DPs that may be encountered after Origination\_Attempt [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. The Termination\_Attempt\_Authorized DP [mandatory] and all those terminating DPs that may + +be encountered after Termination\_Attempt\_Authorized [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. + +- 8) *Broadband Bearer capability* – An indicator of the bearer transfer capability as defined in ITU-T Q.2931 and ITU-T Q.2763, e.g. Deterministic Bit Rate (DBR), Statistical Bit Rate (SBR), Available Bit Rate (ABR), ATM Block Transfer (ABT). Contents of the Broadband Bearer Capability may be used to apply routing for the connection or to authorize other ATM connection parameters through ATM negotiation procedures. + +The bearer capability information is available at the Origination\_Attempt DP and the Termination\_Attempt DP. This criterion could be applicable at all originating and terminating DPs. The Analysed\_Info DP [mandatory] and all other originating DPs that may be encountered after Origination\_Attempt [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. The Termination\_Attempt\_Authorized DP [mandatory] and all those terminating DPs that may be encountered after Termination\_Attempt\_Authorized [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. + +- 9) *Addressing/Numbering Plan Identification (called party)* – An indicator of how the called party address is coded (e.g. E.164, NSAP, private). + +The addressing/numbering plan identification is available at the Origination\_Attempt DP and the Termination\_Attempt DP. These criteria could be applicable at the Origination\_Attempt DP and Termination\_Attempt DP, and beyond. The Origination\_Attempt DP [mandatory] and all those originating DPs that may be encountered after Origination\_Attempt [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. The Termination\_Attempt DP [mandatory] and all those terminating DPs that may be encountered after Termination\_Attempt [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. + +- 10) *Specific called party digit strings* – A string of digits that must match collected digit strings for numbering plans in which selected strings of digits have significance in routing of the connection, in selecting services provided to the subscriber, or in determining the administrative authority for the addressing plan. It could be zero or more digits. + +The string of digits should be consistent with the structure of the addressing plan and should be administrable. For example, the network provider may specify the first N digits where N is consistent with the structure of the E.164 numbering plan, or any other appropriate numbering plan such as NSAP. + +Collected digit strings can be available at the Origination\_Attempt DP or the Termination\_Attempt DP for a party served by either a B-ISDN DSS2 interface or a B-ISDN B-ISUP interface and could be applicable at all originating or terminating DPs. Since collected digit strings are not analysed until the Analyse\_Information PIC (except to determine if a valid sequence has been provided), this criterion could be applicable at the Analysed\_Info DP and beyond. The Analysed\_Info DP [mandatory] and all those originating DPs that may be encountered after Analysed\_Info [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. The Termination\_Attempt\_Authorized DP [mandatory] and all those terminating DPs that may be encountered other than Termination\_Attempt\_Authorized [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. + +- 11) *Specific called party address* – An address that must match the complete called party address, which is unknown NSAP, international, national, network specific, subscriber or abbreviated, or a number in a customized numbering plan. + +The called party address can be available at the Origination\_Attempt DP for a party served by a B-ISDN interface using *en bloc* sending or for a SS No. 7 B-ISUP interface. Since collected address information may not be analysed until the Analyse\_Information PIC (except to determine if sufficient information has been collected), this criterion could be applicable at the Analysed\_Info DP and beyond, and at all terminating DPs. In the originating BCSM, the Analysed\_Info DP [mandatory] and all those originating DPs that may be encountered after Analysed\_Info [optional] are proposed. The Termination\_Attempt\_Authorized DP [mandatory] and all those terminating DPs that may be encountered other than Termination\_Attempt\_Authorized [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. + +- 12) *AESA for called party* – An indication that the AESA may be used for routing. Additionally, fields within the particular AESA may match fields that have significance in routing of the connection, in selecting services provided to the subscriber, or in determining the administrative authority for the addressing plan. The fields may be composed of one or more digits, or of binary fields, depending on the addressing plan. + +The AESA for called party can be available at the Origination\_Attempt DP for a party served by a SS No. 7 B-ISUP interface. Since collected address information may not be analysed until the Analyse\_Information PIC (except to determine if sufficient information has been collected), these criteria could be applicable at the Analysed\_Info DP and beyond, and at all terminating DPs. In the originating BCSM, the Analysed\_Info DP [mandatory] and all those originating DPs that may be encountered after Analysed\_Info [optional] are proposed. The Termination\_Attempt\_Authorized DP [mandatory] and all those terminating DPs that may be encountered other than Termination\_Attempt\_Authorized [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. + +- 13) *Called party subaddress* – An indicator of whether the subaddress is NSAP, user-specified ATM, or other user-specified, and the contents of the subaddress. + +The called party subaddress can be available at the Origination\_Attempt DP in the originating BCSM and the Termination\_Attempt DP in the terminating BCSM for a call originating from a B-ISDN interface, and can be available at the Origination\_Attempt DP and the Termination\_Attempt DP for SS No. 7 B-ISUP interfaces. Since collected address information may not be analysed until the Analyse\_Information PIC (except to determine if sufficient information has been collected), this criterion could be applicable at the Analysed\_Info DP and beyond, and at all terminating DPs. In the originating BCSM, the Analysed\_Info DP [mandatory] and all those originating DPs that may be encountered after Analysed\_Info [optional] are proposed. The Termination\_Attempt\_Authorized DP [mandatory] and all those terminating DPs that may be encountered other than Termination\_Attempt\_Authorized [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. + +- 14) *Called party indicators* – An indicator of whether the called party is an ordinary subscriber or a payphone. + +The called party indicators can be available at the Call\_Accepted DP in the terminating BCSM and at the O\_Term\_Seized DP in the originating BCSM for a call terminating on a SS No. 7 B-ISUP interface. This criterion could be applicable at all subsequent DPs. + +- 15) *Charge indicator* – An indicator of whether the call will receive a charge or not receive a charge. + +The charge indicator can be available at the Call\_Accepted DP in the terminating BCSM and at the O\_Term\_Seized DP in the originating BCSM for a call terminating on a SS No. 7 B-ISUP interface. This criterion could be applicable at all subsequent DPs. + +- 16) *Addressing/Numbering Plan Identification (calling party)* – An indicator of how the called party address is coded (e.g. E.164, NSAP, private). +- The addressing/numbering plan identification is available at the Origination\_Attempt DP and the Termination\_Attempt DP. This criterion could be applicable at the Origination\_Attempt DP and Termination\_Attempt DP, and beyond. The Origination\_Attempt DP [mandatory] and all those originating DPs that may be encountered other than Origination\_Attempt [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. The Termination\_Attempt Authorized DP [mandatory] and all those terminating DPs that may be encountered other than Termination\_Attempt Authorized [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. +- 17) *Specific calling party digit strings* – A string of digits that must match collected digit strings for numbering plans in which selected strings of digits have significance in routing of the connection, in selecting services provided to the subscriber, or in determining the administrative authority for the addressing plan. It could be zero or more digits. +- The string of digits should be consistent with the structure of the addressing plan and should be administrable. For example, the network provider may specify the first N digits where N is consistent with the structure of the E.164 numbering plan, or any other appropriate numbering plan such as NSAP. +- Collected digit strings can be available at the Origination\_Attempt DP or the Termination\_Attempt DP for a party served by either a B-ISDN DSS2 interface or a B-ISDN B-ISUP interface and could be applicable at all originating or terminating DPs. Since collected digit strings are not analysed until the Analyse\_Information PIC (except to determine if a valid sequence has been provided), this criterion could be applicable at the Analysed\_Info DP and beyond. The Analysed\_Info DP [mandatory] and all those originating DPs that may be encountered other than Analysed\_Info [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. +- 18) *Specific calling party address* – An address that must match the complete calling party address, which is unknown NSAP, international, national, network specific, subscriber or abbreviated, or a number in a customized numbering plan. +- The calling party number is available at the Origination\_Attempt DP in the originating BCSM and the Termination\_Attempt DP in the terminating BCSM for a call originating from a B-ISDN interface, and can be available at the Origination\_Attempt DP and the Termination\_Attempt DP for SS No. 7 B-ISUP interfaces. Since collected address information may not be analysed until the Analyse\_Information PIC (except to determine if sufficient information has been collected), this criterion could be applicable at the Analysed\_Info DP and beyond, and at all terminating DPs. In the originating BCSM, the Analysed\_Info DP [mandatory] and all those originating DPs that may be encountered other than Analysed\_Info [optional] are proposed. +- 19) *AESA for calling party* – Fields within the particular AESA may match fields that have significance in routing of the connection, in selecting services provided to the subscriber, or in determining the administrative authority for the addressing plan. The fields may be composed of one or more digits, or of binary fields, depending on the addressing plan. +- The AESA for calling party is available at the Origination\_Attempt DP in the originating BCSM and the Termination\_Attempt DP in the terminating BCSM for a call originating from a SS No. 7 B-ISUP interface. Since collected address information may not be analysed until the Analyse\_Information PIC (except to determine if sufficient information has been collected), this criterion could be applicable at the Analysed\_Info DP and beyond, and at all terminating DPs. In the originating BCSM, the Analysed\_Info DP [mandatory] and all those originating DPs that may be encountered other than Analysed\_Info [optional] are proposed. + +- 20) *Calling party subaddress* – An indicator of whether the subaddress is NSAP, user-specified ATM, or other user-specified, and the contents of the subaddress. +- The calling party subaddress can be available at the Origination\_Attempt DP in the originating BCSM and the Termination\_Attempt DP in the terminating BCSM for a call originating from B-ISDN interfaces, and can be available at the Origination\_Attempt DP and the Termination\_Attempt DP for SS No. 7 B-ISUP interfaces. Since collected address information may not be analysed until the Analyse\_Information PIC (except to determine if sufficient information has been collected), this criterion could be applicable at the Analysed\_Info DP and beyond, and at all terminating DPs. In the originating BCSM, the Analysed\_Info DP [mandatory] and all those originating DPs that may be encountered other than Analysed\_Info [optional] are proposed. +- 21) *Calling party Category* – A parameter that indicates operator language, calling subscriber priority, data call, payphone. The calling party category is available at the Origination\_Attempt DP in the originating BCSM and the Termination\_Attempt DP in the terminating BCSM for a call originating from a SS No. 7 B-ISUP interface. This criterion could be applicable at all DPs. +- 22) *Feature codes or Escape Digits* (e.g.\*XX, #) – A vertical service code, such as a "#" or a two-digit or three-digit code preceded by "" or ""11"" that precedes any subsequent digit collection (e.g. according to the ""normal addressing plan""). +- Feature codes can be available at the Origination\_Attempt DP for a party served by a B-ISDN interface using *en bloc* sending. Since collected digit strings are not analysed until the Analyse\_Information PIC (except to determine if sufficient information has been collected), this criterion could be applicable at the Analysed\_Info DP and beyond. The Analysed\_Info DP [mandatory] and all those originating DPs that may be encountered after Analysed\_Info [optional] are proposed since not all SSP suppliers may retain this information for the duration of the call/attempt. +- 23) *Prefixes* (e.g. 0+, 00+, 011, 01, 1+) – A string of digits that are not feature codes or access codes and which precede any subsequent digit collection (e.g. according to the ""normal numbering plan""). +- Prefixes can be available at the Origination\_Attempt DP for a party served by a B-ISDN interface using *en bloc* sending. Since collected prefix information is not analysed until the Analyse\_Information PIC (except to determine if sufficient information has been collected), this criterion could be applicable at the Analysed\_Info DP and beyond. The Analysed\_Info DP [mandatory] and all those originating DPs that may be encountered after Analysed\_Info [optional] are proposed since not all SSP suppliers may retain this information for the duration of the call/attempt. +- 24) *Access codes* (e.g. 8+) for customized numbering plan – A string of digits in a customized numbering plan that matches access codes such as attendant access codes, access codes to escape to the public network, access codes to access a private facility, access codes to access a private network, and feature access codes. +- Access codes can be available at the Origination\_Attempt DP for a party served by a B-ISDN interface using *en bloc* sending. Since collected access codes are not analysed until the Analyse\_Information PIC (except to determine if sufficient information has been collected), this criterion could be applicable at the Analysed\_Info DP and beyond. The Analysed\_Info DP [mandatory] and all those originating DPs that may be encountered after Analysed\_Info [optional] are proposed since not all SSP suppliers may retain this information for the duration of the call/attempt. +- 25) *Specific Connection Identifier* – An identifier of the specific Virtual Path Connection on a B-ISDN interface from which a specific connection attempt is to be originated or to which a specific connection attempt is to be terminated. + +The connection identifier is used in two contexts. The first context, Origination\_Attempt DP and Facility\_Selected\_and\_Available DP, allows service logic to select the VPCI of the originating and terminating call portions. The second context, Analysed\_Information DP, is used to authenticate that the VPCI requested by the subscriber is consistent with the service profile. + +The Connection Identifier is available at the Origination\_Attempt DP for a party served by either a B-ISDN DSS2 interface or a B-ISDN B-ISUP interface and could be applicable at all originating DPs. The Connection Identifier is also available during the Facility\_Selected\_and\_Available DP after an appropriate terminating connection identifier has been selected for a party served by a B-ISDN DSS2 interface or by a B-ISDN B-ISUP interface and could be applicable at the Facility\_Selected\_and\_Available, T\_No\_Answer, T\_Answer, T\_Mid\_Call, T\_Suspended, T\_Re\_Answer and T\_Disconnect DPs and at the T\_Abandon DP (only after a terminating connection identifier appropriate for the connection has been selected). + +- 26) *End-to-End Transit Delay* – An indicator of the requested and accumulated transit delay as defined in ITU-T Q.2931. + +The transit delay information is available at the Origination\_Attempt DP and the Termination\_Attempt DP. The accumulated transit delay may be updated before Authorize\_Origination\_Attempt and before Present\_Call. The Analysed\_Info DP [mandatory] and all originating DPs other than Analysed\_Info [optional]. The Termination\_Attempt\_Authorized [mandatory] and all other terminating DPs [optional]. + +- 27) *Maximum End-to-End Transit Delay* – An indicator of the requested transit delay as defined in ITU-T Q.2763. + +The transit delay information is available at the Origination\_Attempt DP and the Termination\_Attempt DP. The Analysed\_Info DP [mandatory] and all originating DPs other than Analysed\_Info [optional]. The Termination\_Attempt\_Authorized [mandatory] and all other terminating DPs [optional]. + +- 28) *Propagation Delay Counter* – An indicator of the accumulated transit delay as defined in ITU-T Q.2763. + +The accumulated transit delay information is available at the Origination\_Attempt DP and at the Termination\_Attempt DP. The accumulated transit delay may be updated before Authorize\_Origination\_Attempt and before Present\_Call. The Analysed\_Info DP [mandatory] and all originating DPs other than Analysed\_Info [optional]. The Termination\_Attempt\_Authorized [mandatory] and all other terminating DPs [optional]. + +- 29) *QoS Class* – This is a set of parameterized values that indicate the QoS classes allowed in the forward and backward directions of the connection across the DSS2 and B-ISUP interfaces. + +The QoS parameter information element is present in B-ISDN DSS2 and in B-ISUP Q.2763. The codepoint indicates No specific QoS class explicitly requested, Class 1 (Stringent class), Class 2 (Tolerant class), and Class 3 (Bi-level class). + +The QoS class is available at the Origination\_Attempt DP and could be applicable at any of the originating DPs. QoS class is available at the Termination\_Attempt DP and could be applicable at any of the terminating DPs. The Analysed\_Info DP [mandatory] and all originating DPs other than Analysed\_Info [optional]. The Termination\_Attempt\_Authorized [mandatory] for DSS2 and all other terminating DPs [optional]. + +- 30) *CDVT Descriptor* – This indicates the Cell Delay Variation Tolerance of the requested connection. The CDVT descriptor is present in B-ISDN DSS2 and in B-ISUP. + +The CDVT descriptor is available at the Origination\_Attempt DP and could be applicable at any of the originating DPs. The CDVT descriptor is available at the Termination\_Attempt DP and could be applicable at any of the terminating DPs. The Analysed\_Info DP [mandatory] and all originating DPs other than Analysed\_Info [optional]. The Termination\_Attempt\_Authorized [mandatory] for DSS2 and all other terminating DPs [optional]. + +- 31) *Generic Identifier Transport* – The Generic Identifier Transport information element is used to carry identifiers for Digital Storage Media – Command and Control (DSM-CC), H.310, ATM Signalling VCC, Internet, Multiprotocol over ATM (MPOA) VPN, among others. It is present in B-ISDN DSS2 and in B-ISUP. + +The Generic Identifier is available at the Origination\_Attempt DP and could be applicable at any of the originating DPs. The Generic Identifier is available at the Termination\_Attempt DP and could be applicable at any of the terminating DPs. Because information may not be analysed until the Analyse\_Information PIC, this criterion could be applicable at the Analysed\_Info DP and beyond. The Collected\_Information DP [mandatory], Analysed\_Info DP [mandatory] and all originating DPs that may be encountered other than Origination\_Attempt [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. The Termination\_Attempt\_Authorized [mandatory] and all terminating DPs that may be encountered other than Termination\_Attempt\_Authorized [optional] are proposed since not all SSP suppliers may retain this information for the duration of the connection. Note that terminating triggers may not be applicable to all service contexts. The reference is included only for those contexts that may use them. + +- 32) *Transit Network Selection* – An indicator of the network routing as defined in ITU-T Q.2931 and ITU-T Q.2763. + +The transit network information is available at the Origination\_Attempt DP and the Termination\_Attempt DP. The Analysed\_Info DP [mandatory] and all originating DPs other than Analysed\_Info [optional]. The Termination\_Attempt\_Authorized [mandatory] and all other terminating DPs [optional]. + +- 33) *Connection Modify Request* – A detection of a Q.2931 (Q.2963.1) or Q.2763 (Q.2725.2) connection modification request. + +Modification procedure is allowed during the active phase, O\_Active and T\_Active, at the six exchange types and shall not be combined with narrow-band emulation service. + +- 34) *Cause* (unconditional/conditional on specific cause patterns) – A match on the Cause IE contained in a signalling message as defined in DSS2 and B-ISUP or an indicator of the cause of specific events of interest. Further study is required to identify the cause values needed as DP criteria for IN Capability Set for B-ISDN services from the complete list of cause values. + +Route selection failure information is available at the Route\_Select\_Failure DP, busy cause information is available at the O\_Called\_Party\_Busy and T\_Busy DPs, and release cause information is available at the O\_Disconnect, O\_Abandon, T\_Disconnect and T\_Abandon DPs. This criterion is applicable at the identified DPs. + +DP criteria assignment to a TDP is dependent on the information available at that DP. + +The following two tables (Table 3 and Table 4) denote applicability of DP criteria to all the DPs. + +The entries in the table can be of one of the following trigger categories: + +- Individual-Based; +- Group-Based; +- Switch-Based. + +##### Notes relating to Tables 3 and 4 + +NOTE 1 – Interpretation of Bearer Capability as optional for all DPs other than Origination\_Attempt needs further clarification (e.g. Origination\_Attempt DP mandatory means Termination\_Attempt DP mandatory). + +NOTE 2 – A trigger requiring analysis of a specific number of received digits. The analysis can be based on the complete number of received digits or can be based on a predefined number of digits starting from the most significant digit of the received information. + +NOTE 3 – In a local switch only. The BCSM has to analyse (if facility is allowed, stored as Class of Service attribute) the received information and has to initiate an IN trigger if required. A feature activation/indication can be available at all DPs in the originating BCSM for a party served by a B-ISDN DSS2 interface. A feature activation/indication can be available at the T\_No\_Answer, T\_Answer, T\_Mid\_Call, T\_Suspend, T\_Re\_Answer, T\_Disconnect and T\_Abandon DPs in the terminating BCSM for a party served by a B-ISDN interface. + +NOTE 4 – May be based on a match on contents of the Facility Information Element contained in a signalling message as defined for DSS2. + +NOTE 5 – The Connection ID criteria is applicable to the Origination\_Attempt DP if enabled to influence the selection of VPCI on the originating call portion. In this situation, a VPCI must be returned in the connect operation for insertion in the DSS2 SETUP Acknowledge or Call Proceeding messages, or the B-ISUP IAM Acknowledge message for the originating call portion. + +Similarly, the Connection ID criteria is applicable at the Facility\_Selected\_and\_Available DP, if enabled to influence the selection of VPCI on the terminating call portion. + +The Connection ID criteria is applicable at the Analyse\_Information DP to determine if the calling party has signalled a VPCI consistent with the service profile. If not, the connection would typically be released with cause. + +Further, specific Connection Identifier selection by the user is outside the scope of this capability set. The network can override user selection of the Connection Identifier. + +If a criteria is marked with an "X" for a Detection Point, then this means that the criteria specific information associated with the trigger criteria shall be kept available until the DP is reached. If a criteria is marked with an "O" for a Detection Point, then this means that it is implementation dependent if the criteria specific information is still present at that DP because not all suppliers may retain this information for the duration of the call/attempt. If the information is still present, the treatment is the same as for a criteria marked with an "X". + +**Table 3/Q.1237 – Originating DP criteria for B-ISDN interfaces** + +| DP Criteria | Originating DP | | | | | | | | | | | | | | | | | +|----------------------------------------|----------------|----|-----|-----|----|----|-----|-----|------|-----|------|-----|-----|----|-----|----|-----| +| | ARF | OA | OAD | OAA | CI | AI | RSF | OTS | OCPB | ONA | oAns | OMC | OMR | OS | ORA | OD | oAb | +| Trigger Assigned | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | +| AAL Parameter | O | O | O | O | X | X | O | O | O | O | O | O | – | O | O | O | O | +| ATM Traffic Descriptor | O | O | O | O | O | X | O | O | O | O | O | O | O | O | O | O | O | +| ATM Cell Rate/Additional ATM Cell Rate | O | O | O | O | O | X | O | O | O | O | O | O | O | O | O | O | O | +| Alternative ATM Traffic Descriptor | O | O | O | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Minimum ATM Traffic Descriptor | O | O | O | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Broadband Bearer Capability (Note 1) | O | O | O | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Addressing Plan Called | O | O | O | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Called Party Digits (Note 2) | O | O | O | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Called Party Address | O | O | O | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| AESA for Called Party | O | O | O | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Called Subaddress | O | O | O | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Called Party Indicators | – | – | – | – | – | – | – | X | O | O | O | O | – | O | O | O | O | +| Charge Indicator | – | – | – | – | – | – | – | X | O | O | O | O | – | O | O | O | O | +| Address Plan Calling | – | O | O | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Calling Party Digits (Note 2) | – | O | O | O | O | X | O | O | O | O | O | O | – | O | O | O | O | + +**Table 3/Q.1237 – Originating DP criteria for B-ISDN interfaces (continued)** + +| DP Criteria | Originating DP | | | | | | | | | | | | | | | | | +|----------------------------------|----------------|----|-----|-----|------------------|----|-----|-----|------|-----|------|-----|------------|----|-----|----|-----| +| | ARF | OA | OAD | OAA | CI | AI | RSF | OTS | OCPB | ONA | oAns | OMC | OMR | OS | ORA | OD | oAb | +| Calling Party Address | – | O | O | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| AESA Calling Party | – | O | O | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Calling Subaddress | – | O | O | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Calling Party Category | – | O | O | O | O | O | O | O | O | O | O | O | – | O | O | O | O | +| Feature Codes (Notes 2, 3 and 4) | X | – | – | – | – | X | O | O | O | O | O | O | – | O | O | O | O | +| Prefixes (Note 2) | O | – | – | – | – | X | O | O | O | O | O | O | – | O | O | O | O | +| Access Codes (Note 2) | O | – | – | – | – | X | O | O | O | O | O | O | – | O | O | O | O | +| Connection ID (Note 5) | O | X | O | X | X | X | O | O | O | O | O | O | – | O | O | O | O | +| Transit Delay | O | O | O | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Propagation Delay | O | O | O | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| QoS Class | O | O | O | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| CDVT | O | O | O | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Generic Identifier | O | O | O | O | X | X | O | O | O | O | O | O | – | O | O | O | O | +| Transit Network | O | O | O | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Modify Request | – | – | – | – | – | – | – | – | – | – | – | – | X | – | – | – | – | +| Cause | – | – | – | – | – | – | X | – | X | – | – | – | – | – | – | X | X | +| X Applicable | | | | | – Not Applicable | | | | | | | | O Optional | | | | | + +**Table 3/Q.1237 – Originating DP criteria for B-ISDN interfaces (concluded)** + +The DPs in the table are abbreviated as follows: + +| | | | | +|------|--------------------------------|------|------------------| +| OA | Origination_Attempt | ONA | O_No_Answer | +| OAA | Origination_Attempt_Authorized | Oans | O_Answer | +| OAD | Origination_Attempt_Denied | OMC | O_Mid_Call | +| CI | Collected_Info | OMR | O_Modify_Request | +| AI | Analysed_Info | OS | O_Suspend | +| ARF | Authorize_Route_Failure | ORA | O_Re_Answer | +| RSF | Route_Select_Failure | OD | O_Disconnect | +| OCPB | O_Called_Party_Busy | OAb | O_Abandon | +| OTS | O_Term_Seized | | | + +**Table 4/Q.1237 – Terminating DP criteria for B-ISDN interfaces** + +| DP Criteria | Terminating DP | | | | | | | | | | | | | | +|----------------------------------------|----------------|-----|-----|----|-----|----|-----|------|-----|-----|----|-----|----|-----| +| | TA | TAD | TAA | TB | FSA | CA | TNA | tAns | TMC | TMR | TS | TRA | TD | Tab | +| Trigger Assigned | X | X | X | X | X | X | X | X | X | X | X | X | X | X | +| AAL Parameter | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| ATM Traffic Descriptor | O | O | X | O | O | O | O | O | O | O | O | O | O | O | +| ATM Cell Rate/Additional ATM Cell Rate | O | O | X | O | O | O | O | O | O | O | O | O | O | O | +| Alternative ATM Traffic Descriptor | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Minimum ATM Traffic Descriptor | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Broadband Bearer Capability (Note 1) | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Addressing Plan Called | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Called Party Digits (Note 2) | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Called Party Address | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| AESA for Called Party | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Called Subaddress | O | O | X | O | O | O | O | O | O | – | O | O | O | O | +| Called Party Indicators | – | – | – | – | – | X | O | O | O | – | O | O | O | O | +| Charge Indicator | – | – | – | – | – | X | O | O | O | – | O | O | O | O | +| Address Plan Calling | X | X | O | O | O | O | O | O | O | – | O | O | O | O | +| Calling Party Digits (Note 2) | – | – | – | – | – | – | – | – | – | – | – | – | – | – | +| Calling Party Address | – | – | – | – | – | – | – | – | – | – | – | – | – | – | +| AESA for Calling Party | – | – | – | – | – | – | – | – | – | – | – | – | – | – | +| Calling Subaddress | – | – | – | – | – | – | – | – | – | – | – | – | – | – | +| Calling Party Category | X | X | O | O | O | O | O | O | O | – | O | O | O | O | + +**Table 4/Q.1237 – Terminating DP criteria for B-ISDN interfaces (concluded)** + +| DP Criteria | Terminating DP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|------|------------------|------------------|-----|----|-----|------|-----|------------|----|-----|----|-----|----|---------------------|------|----------|-----|--------------------------------|-----|------------|-----|----------------------------|-----|------------------|----|---------------------------|----|-----------|----|--------|-----|-------------|-----|---------------------------------|----|--------------|-----|-------------|-----|-----------| +| | TA | TAD | TAA | TB | FSA | CA | TNA | tAns | TMC | TMR | TS | TRA | TD | Tab | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Feature Codes (Notes 2, 3 and 4) | – | – | – | – | – | – | – | – | – | – | – | – | – | – | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Prefixes (Note 2) | – | – | – | – | – | – | – | – | – | – | – | – | – | – | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Access Codes (Note 2) | – | – | – | – | – | – | – | – | – | – | – | – | – | – | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Connection ID (Note 5) | – | – | – | – | X | O | O | O | O | – | O | O | O | O | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Transit Delay | O | O | X | O | O | O | O | O | O | – | O | O | O | O | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Propagation Delay | O | O | X | O | O | O | O | O | O | – | O | O | O | O | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| QoS Class | O | O | X | O | O | O | O | O | O | – | O | O | O | O | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CDVT | O | O | X | O | O | O | O | O | O | – | O | O | O | O | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Generic Identifier | O | O | X | O | O | O | O | O | O | – | O | O | O | O | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Transit Network | O | O | X | O | O | O | O | O | O | – | O | O | O | O | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Modify Request | – | – | – | – | – | – | – | – | – | X | – | – | – | – | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Cause | – | – | – | X | – | – | – | – | – | – | – | – | X | X | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| X Applicable | | | | – Not Applicable | | | | | | O Optional | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

The DPs in the table are abbreviated as follows:

TA Termination_Attempt tAns T_Answer
TAA Termination_Attempt_Authorized TMC T_Mid_Call
TAD Termination_Attempt_Denied TMR T_Modify_Request
CA Terminating_Call_Accepted TS T_Suspend
TB T_Busy TRA T_Re_Answer
FSA Facility_Selected_and_Available TD T_Disconnect
TNA T_No_Answer Tab T_Abandon
| | | | | | | | | | | | | | | TA | Termination_Attempt | tAns | T_Answer | TAA | Termination_Attempt_Authorized | TMC | T_Mid_Call | TAD | Termination_Attempt_Denied | TMR | T_Modify_Request | CA | Terminating_Call_Accepted | TS | T_Suspend | TB | T_Busy | TRA | T_Re_Answer | FSA | Facility_Selected_and_Available | TD | T_Disconnect | TNA | T_No_Answer | Tab | T_Abandon | +| TA | Termination_Attempt | tAns | T_Answer | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TAA | Termination_Attempt_Authorized | TMC | T_Mid_Call | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TAD | Termination_Attempt_Denied | TMR | T_Modify_Request | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CA | Terminating_Call_Accepted | TS | T_Suspend | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TB | T_Busy | TRA | T_Re_Answer | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| FSA | Facility_Selected_and_Available | TD | T_Disconnect | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| TNA | T_No_Answer | Tab | T_Abandon | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### **6.3.8 Trigger types and trigger precedence for B-ISDN when carrying N-ISDN services** + +The descriptions of Trigger Types and Trigger Precedence in 6.3.8/Q.1238.2 apply. Following are comments regarding the implementation of N-ISDN services in a broadband environment. + +Narrow-band ISDN services may be implemented over a B-ISDN network by carrying ISDN signalling information in the broadband protocols. As a result, triggers for narrow-band services as defined in ITU-T Q.1238 may be applicable. + +Applicability of narrow-band triggers is contingent on the availability of appropriate narrow-band DSS1 or ISUP signalling information in the broadband protocol. It is also contingent on changes to the trigger descriptions to recognize the broadband bearer rather than the narrow-band bearer, e.g. Shared Interoffice Path or Channel for B-ISDN rather than Shared Interoffice Trunk in ISDN, and Connection Setup VPCI or VCI for B-ISDN rather than Channel Setup PRI in ISDN. A list of Triggers that may be available for narrow-band services is provided below as an example. + +- Origination\_Attempt\_Authorized; +- Off-Hook\_Delay; +- Connection\_Setup\_VPCI; +- Shared\_Interoffice\_Path; +- BRI\_Feature\_Activation\_Indicator; +- Public\_Feature\_Code; +- Specific\_Feature\_Code; +- Customized\_Dialling\_Plan; +- Specific\_Digit\_String; +- Emergency\_Service; +- Call\_Authorization\_Denied; +- AFR; +- O\_Called\_Party\_Busy; +- O\_No\_Answer; +- O\_Answer; +- O\_Disconnect; +- Termination\_Attempt; +- Term\_Attempt\_Authorized; +- T\_Busy; +- Term\_Resource\_Available; +- T\_No\_Answer; +- T\_Answer; +- T\_Disconnect. + +### **6.3.9 Trigger types and trigger precedence for B-ISDN** + +The descriptions of Trigger Types and Trigger Precedence in 6.3.8/Q.1238.2 apply. The trigger types given are described in terms of: + +- 1) TDP – The TDP at which the trigger can be detected. +- 2) DP Criteria – The conditions needed to trigger. + +- 3) Category – Switch, group or individual. +- 4) Interface – Type of interface to which it can be assigned (e.g. DSS2 interface). +- 5) Trigger Type – The value that identifies the type of criteria that cause the CCF/SSF to detect a valid trigger condition at this TDP (i.e. the trigger type). +- 6) Fault handling – Defines fault handling procedures for the case when the SCF does not respond to the CCF/SSF message. Details on possibilities for fault handling is for further study. + +The same DP may be armed multiple times as a TDP-R. To accommodate this, precedence rules for trigger processing are specified as follows: + +- 1) For DSS2 interfaces, a trigger assigned to the interface may depend on a query of the subscriber's Service Profile. The trigger at the DSS2 interface and the Service Profile may be provisioned with different SCFs as the destination. The sequence of processing shall be Service Profile first and DSS2 interface last. +- 2) Individual triggers have precedence over group triggers. +- 3) Group triggers have precedence over switch triggers. + +The sequence for processing IN Capability Set for B-ISDN triggers is implementation dependent, within the precedence rules stated above. There is significant flexibility for using the triggers for IN Capability Set for B-ISDN and it is expected that not all triggers will be enabled in a network at any given time. Table 5 lists the triggers available for each TDP. Precedence rules for network operator defined trigger types are for further study. + +**Table 5/Q.1237 – IN Capability Set for B-ISDN – Trigger availability** + +| Trigger Detection Point | Trigger Type | Trigger Detection Point | Trigger Type | +|-------------------------|-----------------------------|--------------------------------|-----------------------------| +| Collected_Information | AAL_Parameter | Termination_Attempt_Authorized | AAL_Parameter | +| | Shared_Interoffice_Path | | ATM_Traffic_Descriptor | +| | Generic_Identifier | | Alternative_Cell_rate | +| | Served_User_Transport | | CDVT_Descriptor | +| Analysed_Information | ATM_Traffic_Descriptor | | Broadband_Bearer_Capability | +| | Alternative_Cell_Rate | | Called_Party_Plan | +| | CDVT_Descriptor | | Called_Party_Digits | +| | Broadband_Bearer_Capability | | Called_Party_Address | +| | Feature_Code | | AESA_Called_Party | +| | Specific_Feature_Code | | Called_Party_Subaddress | +| | Called_Party_Plan | | Connection_Setup_VPCI | +| | Called_Party_Digits | | Transit_Delay | +| | Called_Party_Address | | QoS_Parameter | +| | AESA_Called_Party | | Generic_Identifier | +| | Called_Party_Subaddress | | TNS_Parameter | +| | Calling_Party_Plan | | Served_User_Transport | + +**Table 5/Q.1237 – IN Capability Set for B-ISDN – Trigger availability (concluded)** + +| Trigger Detection Point | Trigger Type | Trigger Detection Point | Trigger Type | +|-------------------------|---------------------------|-------------------------|--------------------------| +| | Calling_Party_Digits | T_Call_Accepted | Called_Party's_Indicator | +| | Calling_Party_Address | | Charge_Indicator | +| | AESA_Calling_Party | | | +| | Calling_Party_Subaddress | | | +| | Connection_Setup_VPCI | | | +| | Transit_Delay | | | +| | QoS_Parameter | | | +| | TNS_Parameter | | | +| | Emergency_Service | | | +| O_Term_Seized | Called_Party's_Indicators | | | +| | Charge_Indicator | | | + +#### 6.3.9.1 Setup\_Immediate + +The CCF/SSF detects the Setup\_Immediate trigger when an origination indication from the interface is detected. The Origination\_Attempt TDP has been reached. + +- 1) TDP: Origination\_Attempt. +- 2) DP Criteria: Trigger assigned (unconditional). +- 3) Category: Individual, Group. +- 4) Trigger assigned to: Originating Address, Group of Addresses, Switch Interface, virtual User-Network Interface (UNI). +- 5) Trigger Type: setUpImmediate. +- 6) Fault Handling: Final treatment (other treatment such as Default Routing or Continue Call Processing are for further study). + +#### 6.3.9.2 Origination\_Attempt\_Authorized + +Refer to ITU-T Q.1238.2. + +#### 6.3.9.3 AAL\_Parameter + +The AAL\_Parameter trigger type denotes the detection of a request for the services of a particular ATM Adaptation Layer (AAL). It is used when there is a desire to deliver ATM connections of specific AAL types over selected paths (VPCIs), as well as to validate the availability of the requested AAL to the subscriber. + +- 1) TDP: Collected\_Information, Termination\_Attempt\_Authorized. +- 2) DP criteria: Trigger assigned (conditional). AAL Type. +- 3) Category: Individual, Group, Switch. +- 4) Trigger assigned to: Address (originating, terminating), Group of Addresses, Switch Interface, virtual UNI, all addresses or interfaces assigned on the switch. + +- 5) Trigger Type: aalParameter. +- 6) Fault handling: Final Treatment (other treatments such as Default Routing or Continue Call Processing are for further study). + +#### **6.3.9.4 Shared\_Interoffice\_Path** + +The Shared\_Interoffice\_Path trigger type denotes a class of events in which a CCF/SSF performs trigger processing for a CCF. It is detected for connections routed to a CCF/SSF from a CCF: an assist procedure is to be invoked. The CCF/SSF supports a shared interoffice path trigger for the interface to a CCF. On this interface, SS No. 7 B-ISUP signalling, used by the CCF to route the call, is used by the CCF/SSF for triggering a query to the SCF. For example, this trigger may be used in providing a feature to supply specific routing of a call when an assist has been invoked. + +- 1) TDP: Collected\_Information. +- 2) DP criteria: Trigger assigned (unconditional). +- 3) Category: Group (on path basis). +- 4) Trigger assigned to: Specific VPCI. +- 5) Trigger Type: sharedIOPath. +- 6) Fault handling: Final Treatment (other treatments such as Default Routing or Continue Call Processing are for further study). + +#### **6.3.9.5 ATM\_Traffic\_Descriptor, ATM\_Cell\_Rate, Additional\_Cell\_Rate** + +The ATM\_Traffic\_Descriptor trigger type denotes the detection of a request for a particular ATM Cell Rate. It is used to select network paths (VPCI/VCI) appropriate for the connection, and to ascertain the availability of the requested traffic descriptor to the subscriber. + +- 1) TDP: Analysed\_Information, Termination\_Attempt\_Authorized. +- 2) DP criteria: Trigger assigned (conditional). Subscribed Service Profile and Access Parameters. +- 3) Category: Individual, Group. +- 4) Trigger assigned to: Address (originating, terminating), Group of Addresses, Switch Interface, virtual UNI. +- 5) Trigger Type: aTMTrafficDescriptor. +- 6) Fault handling: Connection Negotiation, or Final Treatment. + +#### **6.3.9.6 Alternative\_Cell\_Rate, Minimum\_Cell\_Rate** + +The Alternative\_Cell\_Rate trigger type denotes the detection of a request for alternative ATM Cell Rates for the connection. This trigger is used to validate the requested ATM Traffic Parameters with those subscribed for the connection during the negotiation process. + +- 1) TDP: Analysed\_Information, Termination\_Attempt\_Authorized. +- 2) DP criteria: Trigger assigned (conditional). Subscribed Service Profile and Access Parameters. +- 3) Category: Individual, Group. +- 4) Trigger assigned to: Address (originating, terminating), Group of Addresses, Switch Interface, virtual UNI. +- 5) Trigger Type: alternativeCellRate. +- 6) Fault handling: Final Treatment. + +#### **6.3.9.7 CDVT\_Descriptor** + +The CDVT Descriptor trigger type denotes a connection attempt with a request for a limit on Cell Delay Variation. It is detected when CCF/SSF receives a SETUP message on a DSS2 interface or an Initial Address Message (IAM) on a B-ISUP interface. This trigger is used to select the preferred path (VPCI) for a connection when the available transmission paths have varying CDV capability. It may subsequently provide information for ATM Parameter Negotiation procedures over the selected VPCI. + +- 1) TDP: Analysed\_Information, Termination\_Attempt\_Authorized. +- 2) DP criteria: Trigger assigned (conditional), Subscribed Service Profile and Access Parameters. +- 3) Category: Individual, Group, Switch. +- 4) Trigger assigned to: Address (originating, terminating), Group of Addresses, Switch Interface, Virtual UNI, all addresses or interfaces assigned on the switch. +- 5) Trigger Type: cDVTDDescriptor. +- 6) Fault handling: Final Treatment. + +#### **6.3.9.8 Broadband\_Bearer\_Capability** + +The Broadband\_Bearer\_Capability trigger type denotes the detection of a request for specific bearer capabilities. It is used when there is a desire to deliver ATM connections of specific bearer capabilities over selected paths (VPCIs), as well as to validate the availability of the requested bearer capability to the subscriber. + +- 1) TDP: Analysed\_Information, Termination\_Attempt\_Authorized. +- 2) DP criteria: Trigger assigned (conditional). Subscribed Service Profile and Access Parameters. +- 3) Category: Individual, Group, Switch. +- 4) Trigger assigned to: Address (originating, terminating), Group of Addresses, Switch Interface, virtual UNI, all addresses and interfaces assigned on the switch. +- 5) Trigger Type: broadbandBearerCapability. +- 6) Fault handling: Final Treatment. + +#### **6.3.9.9 Feature\_Code** + +The Feature\_Code trigger type is detected when any of the CCF/SSF supported feature codes (e.g. \*XX) are included in the called party address. Although several feature codes may cause the trigger to be detected, the CCF/SSF shall not differentiate between them for subscription purposes (e.g. \*46, \*53, \*58 all cause the trigger to be detected). For example, this trigger may be used within a service provider's network to advertise other capabilities to the user when an existing feature code is used. + +- 1) TDP: Analysed\_Information. +- 2) DP criteria: Trigger assigned (conditional), Feature Code (unconditional). +- 3) Category: Individual, Group, Switch. +- 4) Trigger assigned to: Originating Address, Group of Addresses, Switch Interface, Virtual UNI, all addresses and interfaces assigned on the switch. + +- 5) Trigger Type: verticalServiceCode. +- 6) Fault handling: Final Treatment (other treatments such as Default Routing or Continue Call Processing are for further study). + +#### **6.3.9.10 Specific\_Feature\_Code** + +The Specific\_Feature\_Code trigger type is detected when the CCF/SSF analyses a specific feature code which is administered as a DP criterion (e.g. only \*46 causes the trigger to be detected). Restriction of Calling Number Delivery can be supported by this trigger type. + +- 1) TDP: Analysed\_Information. +- 2) DP criteria: Trigger assigned (conditional), feature code on specific feature pattern. +- 3) Category: Individual, Group, Switch. +- 4) Trigger assigned to: Originating Address, Group of Addresses, Switch Interface, Virtual UNI, all addresses or interfaces assigned on the switch. +- 5) Trigger Type: specificFeatureCode. +- 6) Fault handling: Final Treatment (other treatments such as Default Routing or Continue Call Processing are for further study). + +#### **6.3.9.11 Called\_Party\_Plan** + +The Called\_Party\_Plan trigger type is detected when the numbering plan information in the address is analysed. This can be used to query databases for routing between administrative domains that use different addressing authorities. Results of this query may be used to populate the Called Party Address (routing address), Called Party Subaddress, Transit Network Selection, as well as the ATM Cell Rate and Connection Identifier. + +- 1) TDP: Analysed\_Information, Termination\_Attempt\_Authorized. +- 2) DP criteria: Trigger assigned (conditional), Called Party Addressing Plan. +- 3) Category: Individual, Group, Switch. +- 4) Trigger assigned to: Originating Address, Group of Addresses, Switch Interface, Virtual UNI, all addresses or interfaces assigned on the switch. +- 5) Trigger Type: calledPartyPlan. +- 6) Fault handling: Final Treatment (other treatments such as Default Routing or Continue Call Processing are for further study). + +#### **6.3.9.12 Called\_Party\_Digits** + +The Called\_Party\_Digits trigger type is detected when the appropriate sequence of digits is included in the called party address. For example, a 3, 6, or 10-digit sequence of digits can be provisioned as the trigger. Trigger provisioning specifies whether the CCF/SSF performs some manipulation of the dialled digits (e.g. digit insertion, deletion, or translation to other addresses), or queries the SCF with the digits as presented in the SETUP message. The numbering plan in force should ensure that emergency service numbers are distinct from provisionable specific digit strings. Precedence should be specified (e.g. most to least specific). For example, this trigger could be used to provide for customized connection routing on a specific address. Results of this query may be used to populate the Called Party Address (routing address), Called Party Subaddress, Transit Network Selection, as well as the ATM Cell Rate and Connection Identifier. + +- 1) TDP: Analysed\_Information, Termination\_Attempt\_Authorized. +- 2) DP criteria: Trigger assigned (conditional), Specific called party number string. + +- 3) Category: Individual, Group, Switch. +- 4) Trigger assigned to: Originating Address, Group of Addresses, Switch Interface, Virtual UNI, all addresses or interfaces assigned on the switch. +- 5) Trigger Type: calledPartyDigits. +- 6) Fault handling: Final Treatment (other treatments such as Default Routing or Continue Call Processing are for further study). + +#### 6.3.9.13 Called\_Party\_Address + +The Called\_Party\_Address trigger type is detected when the appropriate called party address is included in the DSS2 SETUP or the B-ISUP IAM. For example, this trigger could be used to provide for customized connection routing on a specific address. Results of this query may be used to populate the Called Party Address (routing address), Called Party Subaddress, Transit Network Selection, as well as the ATM Cell Rate and Connection Identifier. + +- 1) TDP: Analysed\_Information, Termination\_Attempt\_Authorized. +- 2) DP criteria: Trigger assigned (conditional), Specific called party number string. +- 3) Category: Individual, Group, Switch. +- 4) Trigger assigned to: Originating Address, Group of Addresses, Switch Interface, Virtual UNI, all addresses or interfaces assigned on the switch. +- 5) Trigger Type: calledPartyAddress. +- 6) Fault handling: Final Treatment (other treatments such as Default Routing or Continue Call Processing are for further study). + +#### 6.3.9.14 AESA\_Called\_Party + +The AESA\_Called\_Party trigger type is detected when the called party AESA is included in the DSS2 SETUP Called Party Address or the B-ISUP IAM AESA for Called Party. For example, this trigger could be used to provide for customized connection routing on a specific address. Results of this query may be used to populate the Called Party Address (routing address), Called Party Subaddress, Transit Network Selection, as well as the ATM Cell Rate and Connection Identifier. + +- 1) TDP: Analysed\_Information, Termination\_Attempt\_Authorized. +- 2) DP criteria: Trigger assigned (conditional), Called party AESA content. +- 3) Category: Individual, Group, Switch. +- 4) Trigger assigned to: Originating Address, Group of Addresses, Switch Interface, Virtual UNI, all addresses or interfaces assigned on the switch. +- 5) Trigger Type: aESACalledParty. +- 6) Fault handling: Final Treatment (other treatments such as Default Routing or Continue Call Processing are for further study). + +#### 6.3.9.15 Called\_Party\_Subaddress + +The Called\_Party\_Subaddress trigger type is detected when the appropriate called party subaddress is included in the DSS2 SETUP or the B-ISUP IAM. For example, this trigger could be used to provide for customized connection routing on a specific address. Results of this query may be used to populate the Called Party Address (routing address), Called Party Subaddress, Transit Network Selection, as well as the ATM Cell Rate and Connection Identifier. + +- 1) TDP: Analysed\_Information, Termination\_Attempt\_Authorized. +- 2) DP criteria: Trigger assigned (conditional), Specific called party number string. + +- 3) Category: Individual, Group, Switch. +- 4) Trigger assigned to: Originating Address, Group of Addresses, Switch Interface, Virtual UNI, all addresses or interfaces assigned on the switch. +- 5) Trigger Type: calledPartyAddress. +- 6) Fault handling: Final Treatment (other treatments such as Default Routing or Continue Call Processing are for further study). + +#### **6.3.9.16 Called\_Party's\_Indicator** + +The Called\_Party's\_Indicator trigger type is detected when the specific called party indicator information is included in the B-ISUP Address Complete or Progress message. For example, this trigger could be used to provide special treatment to connections terminating on specific terminal equipment as specified in the Called Party's Indicators. + +- 1) TDP: O\_Term\_Seized, T\_Call\_Accepted. +- 2) DP criteria: Trigger assigned (conditional), Specific called party's indicators. +- 3) Category: Individual, Group, Switch. +- 4) Trigger assigned to: Originating Address, Group of Addresses, Switch Interface, Virtual UNI, all addresses or interfaces assigned on the switch. +- 5) Trigger Type: calledPartysIndicator. +- 6) Fault handling: Final Treatment (other treatments such as Default Routing or Continue Call Processing are for further study). + +#### **6.3.9.17 Charge\_Indicator** + +The Charge\_Indicator trigger type is detected when the charge indicator information is included in the B-ISUP Address Complete or Progress message. For example, this trigger could be used to provide special treatment to connections indicating that a charge will apply. + +- 1) TDP: O\_Term\_Seized, T\_Call\_Accepted. +- 2) DP criteria: Trigger assigned (conditional), Specific charge indicator. +- 3) Category: Individual, Group, Switch. +- 4) Trigger assigned to: Originating Address, Group of Addresses, Switch Interface, Virtual UNI, all addresses or interfaces assigned on the switch. +- 5) Trigger Type: chargeIndicator. +- 6) Fault handling: Final Treatment (other treatments such as Default Routing or Continue Call Processing are for further study). + +#### **6.3.9.18 Calling\_Party\_Plan** + +The Calling\_Party\_Plan trigger type is detected when the numbering plan information in the address is analysed. This can be used to query databases for routing between administrative domains that use different addressing authorities. Results of this query may be used to populate the Called Party Address (routing address), Called Party Subaddress, Calling Party Address, Calling Party Subaddress, Transit Network Selection, as well as the ATM Cell Rate and Connection Identifier. + +- 1) TDP: Analysed\_Information, Termination\_Attempt\_Authorized. +- 2) DP criteria: Trigger assigned (conditional), Called Party Addressing Plan. +- 3) Category: Individual, Group, Switch. + +- 4) Trigger assigned to: Originating Address, Group of Addresses, Switch Interface, Virtual UNI, all addresses or interfaces assigned on the switch. +- 5) Trigger Type: callingPartyPlan. +- 6) Fault handling: Final Treatment (other treatments such as Default Routing or Continue Call Processing are for further study). + +#### **6.3.9.19 Calling\_Party\_Digits** + +The Calling\_Party\_Digits trigger type is detected when the appropriate sequence of digits is included in the called party address. For example, a 3, 6, or 10-digit sequence of digits can be provisioned as the trigger and the CCF/SSF queries the SCF with the digits as presented in the SETUP message. The numbering plan in force should ensure that emergency service numbers are distinct from provisionable specific digit strings. Precedence should be specified (e.g. most to least specific): for further study. For example, this trigger could be used to provide for customized connection routing on a specific address. Results of this query may be used to populate the Called Party Address (routing address), Called Party Subaddress, Transit Network Selection, as well as the ATM Cell Rate and Connection Identifier. + +- 1) TDP: Analysed\_Information. +- 2) DP criteria: Trigger assigned (conditional), Specific called party number string. +- 3) Category: Individual, Group, Switch. +- 4) Trigger assigned to: Originating Address, Group of Addresses, Switch Interface, Virtual UNI, all addresses or interfaces assigned on the switch. +- 5) Trigger Type: callingPartyDigits. +- 6) Fault handling: Final Treatment (other treatments such as Default Routing or Continue Call Processing are for further study). + +#### **6.3.9.20 Calling\_Party\_Address** + +The Calling\_Party\_Address trigger type is detected when the appropriate calling party address is included in the DSS2 SETUP or the B-ISUP IAM. For example, this trigger could be used to provide for customized connection routing on a specific address. Results of this query may be used to populate the Called Party Address (routing address), Called Party Subaddress, Calling Party Address, Calling Party Subaddress, Transit Network Selection, as well as the ATM Cell Rate and Connection Identifier. + +- 1) TDP: Analysed\_Information. +- 2) DP criteria: Trigger assigned (conditional), Specific called party number string. +- 3) Category: Individual, Group, Switch. +- 4) Trigger assigned to: Originating Address, Group of Addresses, Switch Interface, Virtual UNI, all addresses or interfaces assigned on the switch. +- 5) Trigger Type: callingPartyAddress. +- 6) Fault handling: Final Treatment (other treatments such as Default Routing or Continue Call Processing are for further study). + +#### **6.3.9.21 AESA\_Calling\_Party** + +The AESA\_Calling\_Party trigger type is detected when the calling party AESA is included in the DSS2 SETUP Calling Party Address or the B-ISUP IAM AESA for Calling Party. For example, this trigger could be used to provide for customized connection routing on a specific address. Results of this query may be used to populate the Called Party Address (routing address), Called + +Party Subaddress, Calling Party Address, Calling Party Subaddress, Transit Network Selection, as well as the ATM Cell Rate and Connection Identifier. + +- 1) TDP: Analysed\_Information. +- 2) DP criteria: Trigger assigned (conditional), Calling party AESA content. +- 3) Category: Individual, Group, Switch. +- 4) Trigger assigned to: Originating Address, Group of Addresses, Switch Interface, Virtual UNI, all addresses or interfaces assigned on the switch. +- 5) Trigger Type: aESACallingParty. +- 6) Fault handling: Final Treatment (other treatments such as Default Routing or Continue Call Processing are for further study). + +#### **6.3.9.22 Calling\_Party\_Subaddress** + +The Calling\_Party\_Subaddress trigger type is detected when the appropriate calling party subaddress is included in the DSS2 SETUP or the B-ISUP IAM. For example, this trigger could be used to provide for customized connection routing on a specific address. Results of this query may be used to populate the Called Party Address (routing address), Called Party Subaddress, Calling Party Address, Transit Network Selection, as well as the ATM Cell Rate and Connection Identifier. + +- 1) TDP: Analysed\_Information. +- 2) DP criteria: Trigger assigned (conditional), Specific called party number string. +- 3) Category: Individual, Group, Switch. +- 4) Trigger assigned to: Originating Address, Group of Addresses, Switch Interface, Virtual UNI, all addresses or interfaces assigned on the switch. +- 5) Trigger Type: callingPartySubaddress. +- 6) Fault handling: Final Treatment (other treatments such as Default Routing or Continue Call Processing are for further study). + +#### **6.3.9.23 Connection\_Setup\_VPCI** + +The Connection\_Setup\_VPCI trigger type denotes a connection attempt on a specific Virtual Path Connection Identifier (VPCI), or Virtual Channel Identifier (VCI). It is detected when CCF/SSF receives a SETUP message on a DSS2 interface, or an Initial Address Message (IAM) on a B-ISUP interface. This trigger occurs for all connections that use the identified VPCI or VPCI/VCI in a SETUP or IAM. For example, if a VPCI is dedicated to a specific service, this trigger could be used in providing this service on that VPCI. It may subsequently provide information for ATM Parameter Negotiation procedures over the selected VPCI. + +- 1) TDP: Origination\_Attempt, Facility\_Selected\_and\_Available. +- 2) DP criteria: Trigger assigned (conditional), Specific Virtual Path Connection identifier. +- 3) Category: Individual, Group, Switch. +- 4) Trigger assigned to: Address (originating, terminating), Group of Addresses, Switch Interface, Virtual UNI, all addresses or interfaces assigned on the switch. +- 5) Trigger Type: connectionSetupVPCI. +- 6) Fault handling: Final Treatment. + +#### **6.3.9.24 Transit\_Delay** + +The Transit\_Delay trigger type denotes a connection attempt with a specified Maximum Allowable End-to-End Transit Delay. It is detected when CCF/SSF receives a SETUP message on a DSS2 interface or an Initial Address Message (IAM) on a B-ISUP interface. This trigger is used to select the preferred path (VPCI) for a connection when the transmission layer has multiple latency capability. It may subsequently provide information for ATM Parameter Negotiation procedures over the selected VPCI and may be used to update the Propagation Delay value based on the attributes of the originating or terminating access network. + +- 1) TDP: Analysed\_Information, Termination\_Attempt\_Authorized. +- 2) DP criteria: Trigger assigned (conditional), Subscribed Service Profile and Access Parameters. +- 3) Category: Individual, Group, Switch. +- 4) Trigger assigned to: Address (originating, terminating), Group of Addresses, Switch Interface, Virtual UNI, all addresses or interfaces assigned on the switch. +- 5) Trigger Type: transitDelay. +- 6) Fault handling: Final Treatment. + +#### **6.3.9.25 QoS\_Parameter** + +The QoS\_Parameter trigger type denotes a connection attempt with a request for a particular QoS class. It is detected when CCF/SSF receives a SETUP message on a DSS2 interface or an Initial Address Message (IAM) on a B-ISUP interface. This trigger is used to select the preferred path (VPCI) for a connection when the transmission path has multiple QoS capability. It may subsequently provide information for ATM Parameter Negotiation procedures over the selected VPCI. + +- 1) TDP: Analysed\_Information, Termination\_Attempt\_Authorized. +- 2) DP criteria: Trigger assigned (conditional), Subscribed Service Profile and Access Parameters. +- 3) Category: Individual, Group, Switch. +- 4) Trigger assigned to: Address (originating, terminating), Group of Addresses, Switch Interface, Virtual UNI, all addresses or interfaces assigned on the switch. +- 5) Trigger Type: qosParameter. +- 6) Fault handling: Final Treatment. + +#### **6.3.9.26 Generic identifier** + +The Generic Identifier trigger type denotes a connection attempt with a request for a specific service context to be provided by a network service node. It is detected when CCF/SSF receives a SETUP message on a DSS2 interface or an Initial Address Message (IAM) on a B-ISUP interface. This trigger may be used to connect the originating party to a network service node with the requested service context. Note that the Generic Identifier may exist in signalling for a non-subscribed originating party. In such case, it will be ignored. + +- 1) TDP: Collected\_Information, Analysed\_Information, Termination\_Attempt\_Authorized. +- 2) DP criteria: Trigger assigned (conditional), Subscribed Service Profile, or specific served user reference. +- 3) Category: Individual, Group, Switch. + +- 4) Trigger assigned to: Address (originating, terminating), Group of Addresses, Switch Interface, Virtual UNI, all addresses or interfaces assigned on the switch. +- 5) Trigger Type: genericIdentifier. +- 6) Fault handling: Final Treatment (other treatments such as continue call processing may also apply based on network specific arrangements). + +#### **6.3.9.27 TNS\_Parameter** + +The TNS\_Parameter trigger type denotes a connection attempt with a request for particular TNS parameters. It is detected when CCF/SSF receives a SETUP message on a DSS2 interface or an Initial Address Message (IAM) on a B-ISUP interface. This trigger is used to select the preferred path (VPCI) for a connection. It may also be used to populate addressing information into the appropriate addressing fields based on network provider agreements. It may subsequently provide information for ATM Parameter Negotiation procedures over the selected VPCI. + +- 1) TDP: Analysed\_Information, Termination\_Attempt\_Authorized. +- 2) DP criteria: Trigger assigned (conditional), Subscribed Service Profile and Access Parameters. +- 3) Category: Switch. +- 4) Trigger assigned to: All addresses or interfaces assigned on the switch. +- 5) Trigger Type: tNSParameter. +- 6) Fault handling: Final Treatment. + +#### **6.3.9.28 Emergency service** + +The Emergency\_Service trigger type is detected when a digit string denoting emergency service is dialled. The CCF/SSF detects the Emergency Service trigger on any call with access to the public office numbering plan when a designated Emergency Service (e.g. 911) number is dialled. This trigger can provide for emergency call handling under control of the SCF. + +- 1) TDP: Analysed\_Information. +- 2) DP criteria: Trigger assigned (conditional), Specific called party number string. +- 3) Category: Switch. +- 4) Trigger assigned to: All addresses or interfaces assigned on the switch. +- 5) Trigger Type: emergencyService. +- 6) Fault handling: Final Treatment (other treatments such as Default Routing or Continue Call Processing are for further study). + +#### **6.3.9.29 O\_Term\_Seized** + +Refer to ITU-T Q.1238.2. + +#### **6.3.9.30 O\_Called\_Party\_Busy** + +Refer to ITU-T Q.1238.2. + +#### **6.3.9.31 O\_No\_Answer** + +Refer to ITU-T Q.1238.2. + +#### **6.3.9.32 O\_Answer** + +Refer to ITU-T Q.1238.2. + +#### **6.3.9.33 O\_Disconnect** + +Refer to ITU-T Q.1238.2. + +#### **6.3.9.34 O\_Modify\_Request** + +The CCF/SSF detects the oModify trigger when a DSS2 or B-ISUP Modify Request message is sent by the connection originator. The originating subscriber database is queried to verify that the requested parameters are authorized for the subscriber and the originating access network. + +- 1) TDP: O\_Modify\_Request. +- 2) DP Criteria: Trigger assigned (unconditional). +- 3) Category: Individual, Group. +- 4) Trigger assigned to: Individual – Origination Address, Group – DSS2 interface, or switch interface. +- 5) Trigger Type: oModifyRequest. +- 6) Fault Handling: Modify\_Result-modifyReject and resume call in active state. + +#### **6.3.9.35 Termination\_Attempt** + +Refer to ITU-T Q.1238.2. + +#### **6.3.9.36 Term\_Attempt\_Authorized** + +Refer to ITU-T Q.1238.2. + +#### **6.3.9.37 T\_Busy** + +Refer to ITU-T Q.1238.2. + +#### **6.3.9.38 Facility\_Selected\_And\_Available** + +Refer to ITU-T Q.1238.2. + +#### **6.3.9.39 Call\_Accepted** + +Refer to ITU-T Q.1238.2. + +#### **6.3.9.40 T\_No\_Answer** + +Refer to ITU-T Q.1238.2. + +#### **6.3.9.41 T\_Answer** + +Refer to ITU-T Q.1238.2. + +#### **6.3.9.42 T\_Disconnect** + +Refer to ITU-T Q.1238.2. + +#### **6.3.9.43 T\_Modify\_Request** + +The CCF/SSF detects the tModify trigger when a DSS2 or B-ISUP Modify Request message is sent by the connection originator. The terminating subscriber database is queried to verify that the requested parameters are authorized for the subscriber and the terminating access network. + +- 1) TDP: T\_Modify\_Request. +- 2) DP Criteria: Trigger assigned (unconditional). +- 3) Category: Individual, Group. + +- 4) Trigger assigned to: Individual – Destination Address, Group – DSS2 interface, or switch interface. +- 5) Trigger Type: tModifyRequest. +- 6) Fault Handling: Modify\_ Result-modifyReject and resume call in active state. + +## 6.4 Feature interaction manager (FIM)/Call manager (CM) + +The descriptions of FIM and CM in 6.4/Q.1238.2 apply. + +### 6.4.1 DP handling + +The Detection Point handling rules of ITU-T Q.1238 apply, however, the implicit disarming rules are expanded for the B-ISDN modify capability. + +#### 6.4.1.1 Implicit EDP disarming rules + +Implicit EDP disarming rules are specified in ITU-T Q.1238 for Originating BCSM and respectively Terminating BCSM. The following tables include extensions to ITU-T Q.1238. Only EDPs that are impacted by broadband are included in the tables, for simplicity. + +**Table 6/Q.1237 – O\_BCSM: Implicit EDP disarming table** + +| EDP Disarmed | O
Modify
Request
C-Leg | O
Modify
Request
P-Leg | O
Modify
Result
C-Leg | O
Modify
Result
P-Leg | +|-----------------------------------------------------|---------------------------------|---------------------------------|--------------------------------|--------------------------------| +| EDP Encountered | | | | | +| O_Disconnect Controlling Leg | X | | X | | +| O_Disconnect Passive Leg | | X | | X | +| O_Modify_Request | X | X | | | +| O_Modify_Result | | | X | X | +| X Represents IN CS-3 SSF Implicit Disarming of EDP. | | | | | + +**Table 7/Q.1237 – T\_BCSM: Implicit EDP disarming table** + +| EDP Disarmed | T
Modify
Request
C-Leg | T
Modify
Request
P-Leg | T
Modify
Result
C-Leg | T
Modify
Result
P-Leg | +|-----------------------------------------------------|---------------------------------|---------------------------------|--------------------------------|--------------------------------| +| EDP Encountered | | | | | +| T_Disconnect Controlling Leg | X | | X | | +| T_Disconnect Passive Leg | | X | | X | +| T_Modify_Request | X | X | | | +| T_Modify_Result | | | X | X | +| X Represents IN CS-3 SSF Implicit Disarming of EDP. | | | | | + +## **6.5 IN-Switching manager (IN-SM)** + +The descriptions of IN-Switching Manager in 6.5/Q.1238.2 apply. + +### **6.5.1 The connection view model** + +The Connection View Model of ITU-T Q.1238 applies to ITU-T Q.1237. The treatment for added broadband DPs to accommodate bearer modification is included in this clause. + +#### **6.5.1.1 CSCV transitions on DP notification** + +Modify is permitted during the Active phase of a connection. It applies to stable states of the CSCV: Stable 1 Party, Stable 2 Party, and Stable Multi-Party. Modify also applies to other states of the CSCV that occur when the call is in the Active phase: 1\_Party, Forward, Transfer, On-Hold. The detection of the Modify DPs will not transition the CSCV to a new state. + +**Table 8/Q.1237 – Transitions of DPs and signalling events to the CSCV states** + +| Transition to CSCV State →
Detection of DP↓ | Originating
_Setup | Originating
_1_Party
_Setup | Stable_1
_Party | Terminating
_Setup | 1_Party | Stable_2
_Party | Forward | Transfer | On_Hold | Stable_Multi
_Party | +|--------------------------------------------------------|-------------------------------|--------------------------------------------|----------------------------|-------------------------------|---------------------------------------------------------|----------------------------|---------------------------------------------------------|----------------------------------------------------------|---------------------------------------------------------|--------------------------------| +| O_Modify_Request DP
for leg c and leg p | Not applicable | Not applicable | Stable_1
_Party | Not applicable | 1_Party
(if_Active)
Not applicable
(Otherwise) | Stable_2
_Party | Forward
(if_Active)
Not applicable
(Otherwise) | Transfer
(if_Active)
Not applicable
(Otherwise) | On_Hold
(if_Active)
Not applicable
(Otherwise) | Stable
MultiParty | +| O_Modify_Result DP
for leg c and leg p | Not applicable | Not applicable | Stable_1
_Party | Not applicable | 1_Party
(if_Active)
Not applicable
(Otherwise) | Stable_2
_Party | Forward
(if_Active)
Not applicable
(Otherwise) | Transfer
(if_Active)
Not applicable
(Otherwise) | On_Hold
(if_Active)
Not applicable
(Otherwise) | Stable
MultiParty | +| T_Modify_Request DP
for leg c and leg p | Not applicable | Not applicable | Stable_1
_Party | Not applicable | 1_Party
(if_Active)
Not applicable
(Otherwise) | Stable_2
_Party | Forward
(if_Active)
Not applicable
(Otherwise) | Transfer
(if_Active)
Not applicable
(Otherwise) | On_Hold
(if_Active)
Not applicable
(Otherwise) | Stable_Multi
_Party | +| T_Modify_Result DP
for leg c and leg p | Not applicable | Not applicable | Stable_1
_Party | Not applicable | 1_Party
(if_Active)
Not applicable
(Otherwise) | Stable_2
_Party | Forward
(if_Active)
Not applicable
(Otherwise) | Transfer
(if_Active)
Not applicable
(Otherwise) | On_Hold
(if_Active)
Not applicable
(Otherwise) | Stable
MultiParty | + +# **7 SCF model** + +The descriptions of the SCF model in clause 7/Q.1238.2 apply. + +# **8 Finite state model for SSF** + +The descriptions of the Finite state model for the SSF in clause 8/Q.1238.2 apply. + +# **9 Finite state model for SCF** + +The descriptions of the Finite state model for the SCF in clause 9/Q.1238.2 apply. + +# **10 Finite state model for USI** + +The descriptions of the Finite state model for User Service Information in clause 10/Q.1238.2 apply. + +# **11 Operation procedures** + +The following operations are modified for B-ISDN service contexts. They are included here to provide additional description. Operations described in ITU-T Q.1238 that are not listed here are not changed and may apply to the B-ISDN service contexts. The operations are numbered consistently with their sequence in ITU-T Q.1238.2. + +In case of discrepancies between the Call Segment Connection View (CSCV) state transition tables and diagrams described in ITU-T Q.1238 and the state transition tables provided in the following detailed operation procedure descriptions, the former tables take precedence. + +NOTE – A detailed description of each of the parameters associated with the operation procedure descriptions can be found in clause 12. + +## **11.1 Connect procedure** + +### **11.1.1 General description** + +The description, procedures, and parameters in ITU-T Q.1238 apply, subject to the availability of parameters in B-ISDN signalling. The following parameters are added for B-ISDN. + +#### **11.1.1.1 Parameters** + +- aALParameters; +- additionalATMCellRate(aTMTrafficDescriptor); +- aESACalledParty; +- aESACallingParty; +- alternativeATMTrafficDescriptor (alternativeATMCellRate); +- aTMCellRate(aTMTrafficDescriptor); +- calledPartySubaddress; +- cDVTDescriptor; +- connectionIdentifier; +- cumulativeTransitDelay(propagationDelayCounter); +- endToEndTransitDelay(maximumEndtoEndTransitDelay); + +- genericIdentifier; +- minimumAcceptableATMTrafficDescriptor(minimumATMCellRate); +- qosParameter. + +## **11.2 ContinueWithArgument procedure** + +### **11.2.1 General description** + +The description, procedures, and parameters in ITU-T Q.1238 apply, subject to the availability of parameters in B-ISDN signalling. The following parameters are added for B-ISDN. + +#### **11.2.1.1 Parameters** + +- connectionIdentifier. + +## **11.3 EventReportBCSM procedure** + +### **11.3.1 General description** + +The description, procedures, and parameters in ITU-T Q.1238 apply. + +## **11.4 InitialDP procedure** + +### **11.4.1 General description** + +The description, procedures, and parameters in ITU-T Q.1238 apply, subject to the availability of parameters in B-ISDN signalling. The following parameters are added for B-ISDN. + +#### **11.4.1.1 Parameters** + +- aALParameters; +- additionalATMCellRate(aTMTrafficDescriptor); +- aESACalledParty; +- aESACallingParty; +- alternativeATMTrafficDescriptor (alternativeATMCellRate); +- aTMCellRate(aTMTrafficDescriptor); +- calledPartySubaddress; +- cDVTDescriptor; +- connectionIdentifier; +- cumulativeTransitDelay(propagationDelayCounter); +- endToEndTransitDelay(maximumEndtoEndTransitDelay); +- genericIdentifier; +- minimumAcceptableATMTrafficDescriptor(minimumATMCellRate); +- qosParameter. + +## **11.5 InitiateCallAttempt procedure** + +### **11.5.1 General description** + +The description, procedures, and parameters in ITU-T Q.1238 apply, subject to the availability of parameters in B-ISDN signalling. The following parameters are added for B-ISDN. + +#### 11.5.1.1 Parameters + +- aALParameters; +- additionalATMCellRate(aTMTrafficDescriptor); +- aESACalledParty; +- aESACallingParty; +- alternativeATMTrafficDescriptor (alternativeATMCellRate); +- aTMCellRate(aTMTrafficDescriptor); +- calledPartySubaddress; +- bearerCapability; +- cDVTDescriptor; +- connectionIdentifier; +- cumulativeTransitDelay(propagationDelayCounter); +- endtoEndTransitDelay(maximumEndtoEndTransitDelay); +- genericIdentifier; +- minimumAcceptableATMTrafficDescriptor(minimumATMCellRate); +- qoSParameter. + +## 11.6 RequestReportBCSMEVENT procedure + +### 11.6.1 General description + +The description, procedures, and parameters in ITU-T Q.1238 apply, subject to the availability of parameters in B-ISDN signalling. The following DPs are added to the arming tables for the B-ISDN modify capability. See Tables 9 and 10. + +**Table 9/Q.1237 – DP arming table for O-BCSM** + +| O_BCSM | Controlling leg | Passive leg | Default leg ID | +|----------------------------------------------|-----------------|-------------|----------------| +| O_Modify_Request DP | X | X | – o2) | +| O_Modify_Result DP | X | X | – o2) | +| o2) The "legID" parameter shall be included. | | | | +| X Arming Applicable
– Not Applicable | | | | + +**Table 10/Q.1237 – DP arming table for T-BCSM** + +| T_BCSM | Controlling leg | Passive leg | Default leg ID | +|-----------------------------------------------|-----------------|-------------|----------------| +| T_Modify_Request DP | X | X | – t2) | +| T_Modify_Result DP | X | X | – t2) | +| t2) The "legID " parameter shall be included. | | | | +| X Arming Applicable
– Not Applicable | | | | + +# 12 Parameter descriptions + +The descriptions of ITU-T Q.1238.2 apply with the following added definitions for the additional parameters included in operations for B-ISDN. + +## 12.1 AALParameters + +This parameter specifies the ATM adaptation layer parameters information element which provides a means to convey information related to the ATM adaptation layer between endpoints. The information is of significance to both users and local exchanges. The ATM adaptation layer parameters information element is transferred transparently between ATM endpoints by the network. Refer to ITU-T Q.2931. + +## 12.2 AdditionalATMCellRate + +This parameter indicates information sent in the forward and backward direction to support the use of additional traffic parameters to the application process procedures. Refer to ITU-T Q.2762 for the actual definition of this parameter. + +## 12.3 AESACalledParty + +This parameter indicates information sent in the forward direction to carry the AESA received in the UNI Called party number IE across public network(s). Refer to ITU-T Q.2762 for the actual definition of this parameter. + +## 12.4 AESACallingParty + +This parameter indicates information sent in the forward direction to carry the AESA received in the UNI Calling party number IE across public network(s). Refer to ITU-T Q.2762 for the actual definition of this parameter. + +## 12.5 AlternativeATMCellRate + +This parameter indicates the Alternative ATM Cell Rate or the Alternative ATM traffic descriptor information element. It is used to negotiate alternative traffic parameters during call/connection setup. Refer to ITU-T Q.2763 for the actual definition of Alternative ATM Cell Rate and ITU-T Q.2931 for the actual definition of Alternative ATM traffic descriptor. + +## 12.6 ATMCellRate + +This parameter indicates information classified by the cell rate identifier indicating the number of cells per second that are required for the call. The cell rate value is unchanged as it traverses the B-ISDN network. Refer to ITU-T Q.2762 for the actual definition of this parameter. + +## 12.7 BearerCapability + +This parameter indicates the type of bearer capability connection or transmission medium requirements to the user. It is a network option to select one of the two parameters to be used: + +- bearerCap: + +This parameter contains the value of the DSS1 Bearer Capability parameter (ITU-T Q.931) in case the SSF is at local exchange level or the value of the ISUP User Service Information parameter (ITU-T Q.763) in case the SSF is at transit exchange level. + +The parameter "bearerCapability" shall only be included in the "InitialDP" operation in case the DSS1 Bearer Capability parameter or the ISUP User Service Information parameter is available at the SSP. + +If two values for bearer capability are available at the SSF, or if User Service Information and User Service Information Prime are available at the SSF, the "bearerCap" shall contain the value of the preferred bearer capability, respectively the value of the User Service Information Prime parameter. + +– tmr: + +The tmr is encoded as the Transmission Medium Requirement parameter of the ISUP according to ITU-T Q.763. + +If two values for transmission medium requirement are available at the SSF or if Transmission Medium Requirement and Transmission Medium Requirement Prime are available at the SSF, the "bearerCap" shall contain the value of the preferred transmission medium requirement, respectively the value of the Transmission Medium Requirement Prime parameter. + +– BroadbandBearerCapability: + +This alternative subparameter indicates a requested broadband connection-oriented bearer service (see ITU-T F.811) to be provided by the network. It explicitly identifies the ATM transfer capability. It contains only information that may be used by the network. Refer to ITU-T Q.2931 for the definition of this parameter. + +## 12.8 CalledPartySubaddress + +This parameter is used to identify a subaddress associated with the termination of a call, identifying the called party (e.g. specific CPE beyond the S/T reference point). Refer to ITU-T Q.931 (or ITU-T Q.2931) for the actual definition of this parameter. + +## 12.9 CDVTDescriptor + +This parameter indicates information sent in the forward and backward direction to determine the upper bound of the tolerance admitted for the time interval between cells pertaining to a given cell flow. The calling user may request CDVT values applicable for the forward direction and the maximum acceptable CDVT value for the backward direction. The received CDVT values are handled by the network and conveyed to the called user. The network(s) may use the signalled CDVT values for policing and decisions regarding resource allocation and shaping. The backward CDVT values shall be interpreted as maximum acceptable values for the cell flow in the backward direction. Refer to ITU-T Q.2931 for the actual definition of this parameter. + +## 12.10 ConnectionIdentifier + +This parameter indicates information sent to identify the ATM virtual connection. It includes the virtual path connection identifier and the virtual channel identifier. Refer to ITU-T Q.2931 for the actual definition of this parameter. + +## 12.11 CumulativeTransitDelay + +This parameter indicates the cumulative transit delay to be expected for a virtual channel connection. The support of the cumulative transit delay information element is mandatory for the network and optional for the user. Refer to ITU-T Q.2931 for the actual definition of this parameter. + +## 12.12 EndtoEndTransitDelay + +This parameter indicates the End-to-end transit delay information element which indicates the maximum end-to-end transit delay acceptable for a connection. The support of the End-to-end transit delay information element is mandatory for the network and optional for the user. Refer to ITU-T Q.2931 for the actual definition of this parameter. + +## 12.13 EventSpecificInformationBCSM + +This parameter indicates the call related information specific to the event. It comprises the alternatives listed in ITU-T Q.1238.2, as well as the alternative listed here. + +- . + - . + - . +- or +- oModifyRequestSpecificInfo + - aTMCellRate + - additionalATMCellRate +- or +- oModifyResultSpecificInfo + - modifyResultType + - aTMCellRate + - additionalATMCellRate +- or +- tModifyRequestSpecificInfo + - aTMCellRate + - additionalATMCellRate +- or +- tModifyResultSpecificInfo + - modifyResultType + - aTMCellRate + - additionalATMCellRate + +## 12.14 GenericIdentifier + +This parameter indicates the DSS2 generic identifier transport capability. This capability allows the transport through the B-ISDN of identifiers required and used by various distributed applications. This signalling capability is a means of end-to-end signalling using identifiers having a specific purpose which the network can optionally access but not change. In some cases the network may create an identifier on behalf of the user or at its request. Refer to ITU-T Q.2931 for the actual definition of this parameter. + +## 12.15 MinimumATMCellRate + +This parameter indicates the Minimum acceptable ATM Cell Rate or Minimum acceptable ATM traffic descriptor. It is used to negotiate traffic parameters during call/connection setup. The minimum acceptable ATM Cell Rate parameters are the lowest values that the user is willing to accept for the call/connection. Refer to ITU-T Q.2763 for the actual definition of Minimum ATM Cell Rate and to ITU-T Q.2931 for the actual definition of Minimum ATM Traffic Descriptor. + +## 12.16 QoSParameter + +This parameter enables the optional signalling of individual Quality of Service (QoS) parameters while establishing a new ATM connection (VP or VC). The calling user can optionally signal individual QoS parameters in addition to the mandatory signalling of the QoS. Refer to ITU-T Q.2931 for the actual definition of this parameter. + +# 13 Errors + +The descriptions of errors and procedures in clause 13/Q.1238.2 apply. + +# 14 ASN.1 definitions + +The ASN.1 definitions of ITU-T Q.1238 are applicable subject to the availability of services and features in signalling. Definitions for added B-ISDN capabilities and services are provided in the following clauses. + +## 14.1 Data types + +**AALParameters {B2 : b2} ::= OCTET STRING (SIZE(b2.&minAALPLength..b2.&maxAALPLength))** + +*-- Indicates the AAL Parameters Information Element. Refer to Q.2931 for encoding.* + +**AdditionalATMCellRate {B2 : b2} ::= OCTET STRING (SIZE(b2.&minAdditionalATMCellRateLength..b2.&maxAdditionalATMCellRateLength))** + +*-- Indicates the AdditionalATMCellRate Information Element. Refer to Q.2763 for encoding.* + +**AESACalledParty {B2 : b2} ::= OCTET STRING** + +**(SIZE(b2.&minAESACalledPartyLength..b2.&maxAESACalledPartyLength))** + +*-- Indicates the AESACalledParty Information Element. Refer to Q.2763 for encoding.* + +**AESACallingParty {B2 : b2} ::= OCTET STRING** + +**(SIZE(b2.&minAESACallingPartyLength..b2.&maxAESACallingPartyLength))** + +*-- Indicates the AESACallingParty Information Element. Refer to Q.2763 for encoding.* + +**AlternativeATMTrafficDescriptor {B2 : b2} ::= OCTET STRING** + +**(SIZE(b2.&minAlternativeATMTrafficDescriptorLength..b2.&maxAlternativeATMTrafficDescriptorLength))** + +*-- Indicates the AlternativeATMTrafficDescriptor Information Element. Refer to Q.2931 for encoding.* + +**ATMCellRate {B2 : b2} ::= OCTET STRING** + +**(SIZE(b2.&minATMCellRateLength..b2.&maxATMCellRateLength))** + +*-- Indicates the ATMCellRate Information Element. Refer to Q.2763 for encoding.* + +**BearerCapability {B2 : b2} ::= CHOICE {** + +**bearerCap [0] OCTET STRING** + +**(SIZE(2..b2.&maxBearerCapabilityLength)),** + +**tmr [1] OCTET STRING (SIZE(1)),** + +**broadbandBearerCap [2] OCTET STRING** + +**(SIZE (b2.&minBroadbandBearerCapabilityLength.. +b2.&maxBroadbandBearerCapabilityLength))** + +**}** + +*-- Indicates the type of bearer capability connection to the user. For narrow-band bearerCapability, either* + +*-- DSS1 (Q.931) or the ISUP User Service Information (Q.763) encoding can be used. Refer* + +*-- to the Q.763 Transmission Medium Requirement parameter for tmr encoding.* + +*-- For broadband ISDN: Indicates the Broadband Bearer Capability. Refer to Q.2961 for encoding.* + +**CalledPartySubaddress {B2 : b2} ::= OCTET STRING (SIZE(b2.&minCalledPartySubaddressLength..b2.&maxCalledPartySubaddressLength))** + +*-- Indicates the CalledPartySubaddress Information Element. Refer to Q.2763 for encoding.* + +**CDVTDescriptor {B2 : b2} ::= OCTET STRING (SIZE(b2.&minCDVTDescriptorLength..b2.&maxCDVTDescriptorLength))** + +*-- Indicates the CDVTDescriptor Information Element. Refer to Q.2763 for encoding.* + +**ConnectionIdentifier {B2 : b2} ::= OCTET STRING** + +**(SIZE(b2.&minConnectionIdentifierLength..b2.&maxConnectionIdentifierLength))** + +*-- Indicates the ConnectionElementIdentifier Information Element. Refer to Q.2763 for encoding.* + +**CumulativeTransitDelay {B2 : b2} ::= OCTET STRING (SIZE(b2.&minCumulativeTransitDelayLength..b2.&maxCumulativeTransitDelayLength))** + +*-- Indicates the CumulativeTransitDelay Information Element. Refer to Q.2763 for encoding.* + +**EndToEndTransitDelay {B2 : b2} ::= OCTET STRING** + +**(SIZE(b2.&minEndToEndTDLength..b2.&maxEndToEndTDLength))** + +*-- Indicates the MaximumEndToEndTransitDelay Information Element. Refer to Q.2763 for encoding.* + +**GenericIdentifier {B2 : b2} ::= OCTET STRING (SIZE(b2.&minGenericIdentifierLength..b2.&maxGenericIdentifierLength))** + +*-- Indicates the GenericIdentifier Information Element. Refer to Q.2931 for encoding.* + +**MinAcceptableATMTrafficDescriptor {B2 : b2} ::= OCTET STRING** +(SIZE(b2.&minMinAcceptableATMTrafficDescriptorLength..b2.&maxMinAcceptableATMTrafficDescriptor Length)) + +-- Indicates the MinimumAcceptableATMTrafficDescriptor Information Element. Refer to Q.2931 for encoding. + +**QoSParameter {B2 : b2} ::= OCTET STRING** +(SIZE(b2.&minQoSParameterLength..b2.&maxQoSParameterLength)) + +-- Indicates the QoS. Refer to Q.2961 for encoding. + +**EventSpecificInformationBCSM {B2 : b2} ::= CHOICE {** + +- . +- . +- . +- oModifyRequestSpecificInfo [40] SEQUENCE {** +    aTMCellRate [0] ATMCellRate {b2} OPTIONAL, +    additionalATMCellRate [1] AdditionalATMCellRate {b2} OPTIONAL, +    ... +}, +- oModifyResultSpecificInfo [41] SEQUENCE {** +    modifyResultType [0] ModifyResultType DEFAULT +    modifyAcknowledge, +    aTMCellRate [1] ATMCellRate {b2} OPTIONAL, +    additionalATMCellRate [2] AdditionalATMCellRate {b2} OPTIONAL, +    ... +}, +- tModifyRequestSpecificInfo [42] SEQUENCE {** +    aTMCellRate [0] ATMCellRate {b2} OPTIONAL, +    additionalATMCellRate [1] AdditionalATMCellRate {b2} OPTIONAL, +    ... +}, +- tModifyResultSpecificInfo [43] SEQUENCE {** +    modifyResultType [0] ModifyResultType DEFAULT +    modifyAcknowledge, +    aTMCellRate [1] ATMCellRate {b2} OPTIONAL, +    additionalATMCellRate [2] AdditionalATMCellRate {b2} OPTIONAL, +    ... +} + +**}** + +**ModifyResultType ::= ENUMERATED {** +    modifyAcknowledge(0), +    modifyReject(1) +} + +**EventTypeBCSM ::= ENUMERATED {** + +- . +- . +- . +- oModifyRequest(100), +- oModifyResult(101), +- tModifyRequest(102), +- tModifyResult(103) + +**}** + +**TriggerType ::= ENUMERATED {** + +- . +- . +- . +- oModifyRequest(100), +- tModifyRequest(101) + +**}** + +## 14.2 Classes + +SCF-SSF-BOUNDS ::= CLASS { + +. + . + . + &minAALPLength INTEGER OPTIONAL, + &maxAALPLength INTEGER OPTIONAL, + &minAdditionalATMCellRateLength INTEGER OPTIONAL, + &maxAdditionalATMCellRateLength INTEGER OPTIONAL, + &minAESACalledPartyLength INTEGER OPTIONAL, + &maxAESACalledPartyLength INTEGER OPTIONAL, + &minAESACallingPartyLength INTEGER OPTIONAL, + &maxAESACallingPartyLength INTEGER OPTIONAL, + &minATMCellRateLength INTEGER OPTIONAL, + &maxATMCellRateLength INTEGER OPTIONAL, + &minCalledPartySubaddressLength INTEGER OPTIONAL, + &maxCalledPartySubaddressLength INTEGER OPTIONAL, + &minCDVTDescriptorLength INTEGER OPTIONAL, + &maxCDVTDescriptorLength INTEGER OPTIONAL, + &minConnectionIdentifierLength INTEGER OPTIONAL, + &maxConnectionIdentifierLength INTEGER OPTIONAL, + &minCumulativeTransitDelayLength INTEGER OPTIONAL, + &maxCumulativeTransitDelayLength INTEGER OPTIONAL, + &minEndToEndTDLength INTEGER OPTIONAL, + &maxEndToEndTDLength INTEGER OPTIONAL, + &minGenericIdentifierLength INTEGER OPTIONAL, + &maxGenericIdentifierLength INTEGER OPTIONAL, + &minMinAcceptableATMTrafficDescriptorLength INTEGER OPTIONAL, + &maxMinAcceptableATMTrafficDescriptorLength INTEGER OPTIONAL, + &minQoSParameterLength INTEGER OPTIONAL, + &maxQoSParameterLength INTEGER OPTIONAL, + + &maxBearerCapabilityLength INTEGER OPTIONAL, + &minBroadbandBearerCapabilityLength INTEGER OPTIONAL, + &maxBroadbandBearerCapabilityLength INTEGER OPTIONAL, + } + +WITH SYNTAX + +{ + . + . + . + [MINIMUM-FOR-AAL-PARAMETERS &minAALPLength] + [MAXIMUM-FOR-AAL-PARAMETERS &maxAALPLength] + [MINIMUM-FOR-ADDITIONAL-ATM-CELL-RATE &minAdditionalATMCellRateLength] + [MAXIMUM-FOR-ADDITIONAL-ATM-CELL-RATE &maxAdditionalATMCellRateLength] + [MINIMUM-FOR-AESA-CALLED-PARTY &minAESACalledPartyLength] + [MAXIMUM-FOR-AESA-CALLED-PARTY &maxAESACalledPartyLength] + [MINIMUM-FOR-AESA-CALLING-PARTY &minAESACallingPartyLength] + [MAXIMUM-FOR-AESA-CALLING-PARTY &maxAESACallingPartyLength] + [MINIMUM-FOR-ATM-CELL-RATE &minATMCellRateLength] + [MAXIMUM-FOR-ATM-CELL-RATE &maxATMCellRateLength] + [MINIMUM-FOR-CALLED-PARTY-SUBADDRESS &minCalledPartySubaddressLength] + [MAXIMUM-FOR-CALLED-PARTY-SUBADDRESS &maxCalledPartySubaddressLength] + [MINIMUM-FOR-CDVT-DESCRIPTOR &minCDVTDescriptorLength] + [MAXIMUM-FOR-CDVT-DESCRIPTOR &maxCDVTDescriptorLength] + [MINIMUM-FOR-CONNECTION-IDENTIFIER &minConnectionIdentifierLength] + [MAXIMUM-FOR-CONNECTION-IDENTIFIER &maxConnectionIdentifierLength] + [MINIMUM-FOR-CUMULATIVE-TRANSIT-DELAY &minCumulativeTransitDelayLength] + [MAXIMUM-FOR-CUMULATIVE-TRANSIT-DELAY &maxCumulativeTransitDelayLength] + [MINIMUM-FOR-END-TO-END-TRANSIT-DELAY &minEndToEndTDLength] + [MAXIMUM-FOR-END-TO-END-TRANSIT-DELAY &maxEndToEndTDLength] + } + +``` + +[MINIMUM-FOR-GENERIC-IDENTIFIER &minGenericIdentifierLength] +[MAXIMUM-FOR-GENERIC-IDENTIFIER &maxGenericIdentifierLength] +[MINIMUM-FOR-MIN-ACCEPTABLE-ATM-TRAFFIC-DESCRIPTOR + &minMinAcceptableATMTrafficDescriptorLength] +[MAXIMUM-FOR-MIN-ACCEPTABLE-ATM-TRAFFIC-DESCRIPTOR + &maxMinAcceptableATMTrafficDescriptorLength] +[MINIMUM-FOR-QOS-PARAMETER &minQoSParameterLength] +[MAXIMUM-FOR-QOS-PARAMETER &maxQoSParameterLength] + +[MAXIMUM-FOR-BEARER-CAPABILITY &maxBearerCapabilityLength] +[MINIMUM-FOR-BROADBAND-BEARER-CAPABILITY &minBroadbandBearerCapabilityLength] +[MAXIMUM-FOR-BROADBAND-BEARER-CAPABILITY &maxBroadbandBearerCapabilityLength] +} + +``` + +## **14.3 Operations and arguments** + +**ConnectArg {B1 : b1, B2 : b2} ::= SEQUENCE {** + +``` + + . + . + . + calledPartySubaddress [60] CalledPartySubaddress {b2} OPTIONAL, + connectionIdentifier [61] ConnectionIdentifier {b2} OPTIONAL, + genericIdentifier [62] GenericIdentifier {b2} OPTIONAL, + qOSParameter [63] QoSParameter {b2} OPTIONAL, + bISDNParameters [64] BISDNParameters OPTIONAL, + ... +} + +``` + +**ContinueWithArgumentArg {B1 : b1, B2 : b2} ::= SEQUENCE {** + +``` + + . + . + . + connectionIdentifier [60] ConnectionIdentifier {b2} OPTIONAL, + ... +} + +``` + +**InitialDPArg {B1 : b1, B2 : b2} ::= SEQUENCE {** + +``` + + . + . + . + calledPartySubaddress [60] CalledPartySubaddress {b2} OPTIONAL, + connectionIdentifier [61] ConnectionIdentifier {b2} OPTIONAL, + genericIdentifier [62] GenericIdentifier {b2} OPTIONAL, + qOSParameter [63] QoSParameter {b2} OPTIONAL, + bISDNParameters [64] BISDNParameters OPTIONAL, + ... +} + +``` + +**InitiateCallAttemptArg {B1 : b1, B2 : b2} ::= SEQUENCE {** + +``` + + . + . + . + bearerCapability [60] BearerCapability {b2} OPTIONAL, + calledPartySubaddress [61] CalledPartySubaddress {b2} OPTIONAL, + connectionIdentifier [62] ConnectionIdentifier {b2} OPTIONAL, + genericIdentifier [63] GenericIdentifier {b2} OPTIONAL, + qOSParameter [64] QoSParameter {b2} OPTIONAL, + bISDNParameters [65] BISDNParameters OPTIONAL, + ... +} + +``` + +``` + +BISDNParameters {b2:b2} ::= SEQUENCE { + aALParameters [0] AALParameters {b2} OPTIONAL, + additionalATMCellRate [1] AdditionalATMCellRate {b2} OPTIONAL, + aESACalledParty [2] AESACalledParty {b2} OPTIONAL, + aESACallingParty [3] AESACallingParty {b2} OPTIONAL, + alternativeATMTrafficDescriptor [4] AlternativeATMTrafficDescriptor {b2} OPTIONAL, + aTMCellRate [5] ATMCellRate {b2} OPTIONAL, + cDVTDescriptor [6] CDVTDescriptor {b2} OPTIONAL, + cumulativeTransitDelay [7] CumulativeTransitDelay {b2} OPTIONAL, + endToEndTransitDelay [8] EndToEndTransitDelay {b2} OPTIONAL, + minAcceptableATMTrafficDescriptor [9] MinAcceptableATMTrafficDescriptor {b2} OPTIONAL, + ... +} + +``` + +# APPENDIX I + +## Mapping of Setup Request Primitive signalling information to PIC + +This appendix provides examples of signalling information that may be available at the Points in Call (PICs) for the originating and terminating BCSM. It includes references to signalling Recommendations that are relevant at the time of writing. + +## I.1 O\_BCSM mapping of setup request primitive signalling information to PIC + +### I.1.1 O\_Null PIC + +After detecting the Origination Attempt event, it is assumed that the CCF/SSF has information received from the signalling interface arrangement (e.g. as a Setup service request primitive is received due to a DSS2 Setup, B-ISUP IAM) available, associated with the originating call portion, with restrictions as noted. + +ITU-T Q.2931 supports interworking between N-ISDN and B-ISDN. As a result, several information elements in support of 64 kbit/s based ISDN circuit mode services are carried through DSS2 B-ISDN. The CCF/SSF receives a SETUP message from a DSS2 interface and this SETUP message can contain the following information: + +- Bearer Capability – See Q.2931 Narrow-band Bearer Capability information element. +- Progress Indicator – See Q.2931 Progress Indicator information element. +- Keypad Facility – See Q.2932 Facility information element and Q.932 Keypad Facility. This information may be available at the CCF/SSF if ITU-T Q.2932 is supported on the interface. +- Feature activation – See Q.2932 Facility information and Q.932 Feature Activation information element. This information may be available at the CCF/SSF if ITU-T Q.2932 is supported on the interface. +- Calling party number – See Q.2931 Calling Party Number information element. +- Called party number – See Q.2931 Called Party Number information element. + +The called party number information element is sent when *en bloc* sending is used. When the type of number and numbering plan identification field within the called party number information element is set to "unknown", the CCF/SSF treats the string as if it has been received within a keypad information element that is defined in ITU-T Q.932. In this case, it is not expected to be sent with the transit network selection or Operator Services Information elements. + +- Calling party subaddress and called party subaddress – See Q.2931 Calling Party Subaddress and Called Party Subaddress information elements. + +- Carrier Access Code/Carrier Identification Code – See ITU-T Q.1290. The caller may dial a Carrier Access Code (CAC) (e.g. 101XXXX for use on this call). When the caller is served by a B-ISDN interface, a Carrier Identification Code, i.e. XXXX, may be received by the CCF/SSF within the transit network selection information element of the B-ISDN SETUP message. +- Transit Network Selection – See Q.2931 Transit Network Selection information element. This information element is included in a SETUP message containing other information elements than the Keypad information that is defined in ITU-T Q.932. +- Additional Calling Party Number – See Q.2931 Calling Party Number element. +- Feature Code – See Q.1290 Feature Code. Available, if used, for a party served by a DSS2 interface using *en bloc* sending or for an SS No. 7 B-ISUP interface. +- Access Code – See ITU-T Q.1290. Available, if used, for a party served by a DSS2 interface using *en bloc* sending. +- Service Profile Identifier (SPID) – See Q.2932 FACILITY message and Facility information element and Annex A/Q.932. This information may be available at the CCF/SSF if ITU-T Q.2932 is supported on the interface. +- Facility Information – See Q.2932 Facility information and Q.932 Facility Information element. This information may be available at the CCF/SSF if ITU-T Q.2932 is supported on the interface. This element may identify USI Information or Facility Information. +- Other information, as defined by Q.932 Generic Procedures for the Control of ISDN Supplementary Services, can be included in the Q.2931 NOTIFY message and in the Notification Indicator contained in other Q.2931 messages or the Q.2932 FACILITY message and the Facility information element. Some of this information may be of interest to the SCF. + +ITU-T Q.2931 supports the services of B-ISDN. As a result, information elements in support of B-ISDN services are carried through DSS2. The CCF/SSF receives a SETUP message from a DSS2 interface and this SETUP message can contain the following information: + +- AAL Parameters – See Q.2931 AAL Parameters information element. +- Bearer Capability – See Q.2931 Broadband Bearer Capability parameter. +- Calling Party Number – See Q.2931 Calling Party Number parameter. +- Called Party Number – See Q.2931 Called Party Number parameter. +- Called Party Subaddress – See Q.2931 Called Party Subaddress parameter. +- Calling Party Subaddress – See Q.2931 Called Party Number parameter. +- Connection Identifier – See Q.2931 Connection Identifier information element. +- End-to-End Transit Delay – See Q.2931 End-to-End Transit Delay information element. +- QoS Parameter – See Q.2931 QoS parameter. +- CDVT descriptor – See Q.2931 CDVT descriptor. +- Generic Identifier Transport – See Q.2931 Generic Identifier Transport. +- ATM Traffic Descriptor – See ITU-T Q.2931. +- Alternative ATM Traffic Descriptor – See Q.2962.1 Alternative ATM Traffic Descriptor information element. +- Minimum Acceptable ATM Traffic Descriptor – See Q.2962.1 Minimum Acceptable ATM Traffic Descriptor information element. +- Transit Network Selection – See Q.2931 Transit Network Selection information element. + +ITU-T Q.2763 supports interworking between N-ISDN and B-ISDN. As a result, parameters in support of N-ISDN are carried in B-ISUP. The CCF/SSF receives an IAM message from a B-ISUP interface and this message can contain the following information: + +- Forward Call indicators – See Q.2763 Forward Narrow-band Interworking Indicators parameter. The caller's access is identified as ISDN or non-ISDN, and an indication is given of whether an end-to-end SS No. 7 supported connection is required. +- Forward Call indicators – See Q.2763 National International Call Indicators parameter. The caller is identified as national or international. +- Narrow-band Bearer Capability – See Q.2763 Narrow-band Bearer Capability. For the purposes of IN Capability Set for B-ISDN, this parameter identifies the call as circuit-mode/speech, circuit-mode/3.1 kHz audio, circuit-mode/unrestricted digital information (64 kbit/s), or circuit-mode/restricted digital information. +- Called party number – See Q.2763 Called Party Number parameter. +- Calling party number – See Q.2763 Calling Party Number Parameter. +- Generic Number – See Q.2763 Additional Calling Party Number. +- Charge number – See Q.2763 Charged Party Identification. +- Carrier selection – See Q.2763 Transit Network Selection parameter. This parameter, if present, identifies the Carrier Identification Code. +- Feature Code – See Q.2763 Service Activation parameter. +- Location Number – See Q.2763 Location Number signalling information. Used if the calling party is a mobile subscriber. +- Called Directory Number – See Q.2769.1 Called Directory Number. +- Number Portability Forward Information – See Q.2769.1 Number Portability Forward Information. +- Redirecting Party ID – See Q.2763 Redirecting Number. +- Redirection Information – See Q.2763 Redirection Information. +- USI Information – See Q.2763 Narrow-band Bearer Capability. +- Other parameters may be included in the IAM. These parameters may be included because of features provided by other switches in the connection (e.g. information relating to the call being forwarded). + +ITU-T Q.2763 supports the services of B-ISDN. As a result, information elements in support of B-ISDN services are carried through B-ISUP. The CCF/SSF receives an IAM message from a B-ISUP interface and this IAM message can contain the following information: + +- AAL Parameters – See Q.2763 AAL Parameters parameter field. +- ATM Cell Rate – See Q.2763 ATM Cell Rate parameter field. +- Additional ATM Cell Rate – See Q.2763 Additional ATM Cell Rate parameter field. +- Alternative ATM Cell Rate – See Q.2763 Alternative ATM Cell Rate parameter field. +- Minimum ATM Cell Rate – See Q.2763 Minimum ATM Cell Rate parameter field. +- Broadband Bearer Capability – See Q.2763 Broadband Bearer Capability parameter. +- Calling Party Number – See Q.2763 Calling Party Number parameter. +- AESA for Calling Party – See Q.2763 AESA for Calling Party parameter. +- Called Party Number – See Q.2763 Called Party Number parameter. +- AESA for Called Party – See Q.2763 AESA for Called Party parameter. +- Called Party Subaddress – See Q.2763 Called Party Subaddress parameter. + +- Calling Party Subaddress – See Q.2763 Calling Party Number parameter. +- Connection Identifier – See Q.2763 Connection Identifier parameter field. +- Maximum End-to-End Transit Delay – See Q.2763 Maximum End-to-End Transit Delay parameter field. +- Propagation Delay Counter – See Q.2763 Propagation Delay Counter parameter field. +- QoS parameter – See Q.2763 Forward and Backward QoS class parameter. +- CDVT descriptor – See Q.2763 CDVT descriptor. +- Generic Identifier Transport – See Q.2763 Application generated identifier. +- Transit Network Selection – See Q.2763 Transit Network Selection parameter field. + +### I.1.2 Collect\_Information PIC + +After the CCF/SSF determines that information collection is complete, it is assumed that the CCF/SSF may have collected the following additional information available associated with the originating call portion. + +From a DSS2 interface that supports 64 kbit/s based ISDN circuit mode services, the collected information consists of one or more of the following: + +- Access Codes within a Customized Dialling Plan (CDP) – See ITU-T Q.1290. + +The Customized Dialling Plan (CDP) in force may specify that after a given access code is dialled, more digits are to be collected according to the "normal dialling plan", i.e. the dialling plan in force. In this case, Access Code and Collected Address Information are known. If the CDP in force specifies that after a given access code is dialled, a variable number of digits are to be collected, then Access Code and Collected Digits are known. + +- Feature Code – See Q.1290 Feature Code. + +If the numbering plan in force specifies that after a given feature code is dialled, more digits are to be collected according to the "normal dialling plan", then Feature Code and Collected Address Information are known. If the dialling plan in force specifies that after a given feature code is dialled, a variable number of digits are to be collected, then Feature Code and Collected Digits are known. The service associated with the feature code is dependent upon the users' service profile. + +- Facility Code – See ITU-T Q.1290. + +This information may be provided if and when Q.2932 Facility information is supported on the interface. + +- Feature Activation – See Q.2932 Facility information element and Q.932 Feature Activation information element. + +If the CDP in force specifies that after a given feature activator is received, more digits are to be collected according to the numbering plan, then Feature Activation Indicator and Collected Address Information are known. + +If the CDP in force specifies that after a given feature activator is received, a variable number of digits are to be collected, then Feature Activation Indicator and Collected Digits are known. + +- Prefix – See ITU-T Q.1290. + +- Carrier Access Code/Carrier Identification Code – See ITU-T Q.1290. + +The caller may dial a Carrier Access Code (CAC) (e.g. a 101XXXX for use on this call). When the caller is served by a B-ISDN interface, a Carrier Identification Code, i.e. XXXX, may be received by the CCF/SSF within a FACILITY message. + +- Collected Address Information – See ITU-T Q.1290. + +Available as per the numbering plan. + +- Collected Digits – See ITU-T Q.1290. + +The numbering plan in force may specify that after a given Feature Activation, Feature Code, or Access Code within a CDP is dialled, a variable number of digits are to be collected. In this case, these collected digits are also known at this time. + +### **I.1.3 O\_Active PIC** + +A service feature request is received from a party: [e.g. in a Q.2932 FACILITY message and Q.932 ISDN feature activator, and Q.932 HOLD or RETRIEVE message (for a terminating party only)]. + +- Feature Activation – See Q.2932 Facility information element and Q.932 Feature Activation information element. + +If the CDP in force specifies that after a given feature activator is received, more digits are to be collected according to the numbering plan, then Feature Activation Indicator and Collected Address Information are known. + +If the CDP in force specifies that after a given feature activator is received, a variable number of digits are to be collected, then Feature Activation Indicator and Collected Digits are known. + +### **I.1.4 O\_Bearer\_Modify PIC** + +After detecting the O\_Modify\_Request DP the CCF/SSF may have additional information available from the signalling interface. This information may include the following: + +- ATM Cell Rate – See Q.2763 ATM Cell Rate parameter field. +- Additional ATM Cell Rate – See Q.2763 Additional ATM Cell Rate parameter field. + +### **I.1.5 O\_Bearer\_Active PIC** + +After detecting the O\_Modify\_Acknowledge DP the CCF/SSF may have additional information available from the signalling interface. This information may include the following: + +- ATM Cell Rate – See Q.2763 ATM Cell Rate parameter field. +- Additional ATM Cell Rate – See Q.2763 Additional ATM Cell Rate parameter field. + +## **I.2 T\_BCSM mapping of setup request primitive signalling information to PIC** + +### **I.2.1 T\_Null PIC** + +Once the CCF/SSF has detected the Termination\_Attempt event it is assumed the following information is available and associated with the terminating portion of the call with restrictions as noted (information associated with the originating portion of the call as per the Send\_Call PIC is assumed to be still available). + +For a DSS2 interface that supports 64 kbit/s based ISDN circuit mode services or for a SS No. 7 B-ISUP interface that supports ISUP parameters: + +- Calling Party Category – See Q.2763 Determined by the Class of Service information. +- Called Party Subaddress – See ITU-T Q.2931. +- Calling Party Subaddress – See ITU-T Q.2931. + +- Location Number – See Q.2763 Location Number signalling information. Used if the calling party is a mobile subscriber. +- Original Called Party Number – See Q.2763 Original Called Number. +- Redirecting Party ID – See Q.2763 Redirecting Number. +- Redirection Information – See Q.2763 Redirection Information. +- USI Information – See Q.2763 Narrow-band Bearer Capability. + +ITU-T Q.2931 supports the services of B-ISDN. As a result, information elements in support of B-ISDN services are carried through DSS2. The CCF/SSF receives a SETUP message from a DSS2 interface and this SETUP message can contain the following information: + +- AAL Parameters – See Q.2931 AAL Parameters information element. +- Broadband Bearer Capability – See Q.2931 Broadband Bearer Capability parameter. +- Calling Party Number – See Q.2931 Calling Party Number parameter. +- Called Party Number – See Q.2931 Called Party Number parameter. +- Called Party Subaddress – See Q.2931 Called Party Subaddress parameter. +- Calling Party Subaddress – See Q.2931 Called Party Number parameter. +- Connection Identifier – See Q.2931 Connection Identifier information element. +- End-to-End Transit Delay – See Q.2931 End-to-End Transit Delay information element. +- QoS Parameter – See Q.2931 QoS parameter. +- CDVT descriptor – See Q.2931 CDVT descriptor. +- Generic Identifier Transport – See Q.2931 Generic Identifier Transport. +- ATM Traffic Descriptor – See Q.2931 ATM Traffic Descriptor. +- Alternative ATM Traffic Descriptor – See Q.2931 Alternative ATM Traffic Descriptor information element. +- Minimum Acceptable ATM Traffic Descriptor – See Q.2931 Minimum Acceptable ATM Traffic Descriptor information element. +- Transit Network Selection – See Q.2931 Transit Network Selection information element. + +ITU-T Q.2763 supports the services of B-ISDN. As a result, information elements in support of B-ISDN services are carried through B-ISUP. The CCF/SSF receives an IAM message from a B-ISUP interface and this IAM message can contain the following information: + +- AAL Parameters – See Q.2763 AAL Parameters parameter field. +- ATM Cell Rate – See Q.2763 ATM Cell Rate parameter field. +- Additional ATM Cell Rate – See Q.2763 Additional ATM Cell Rate parameter field. +- Alternative ATM Cell Rate – See Q.2763 Alternative ATM Cell Rate parameter field. +- Minimum ATM Cell Rate – See Q.2763 Minimum ATM Cell Rate parameter field. +- Broadband Bearer Capability – See Q.2763 Broadband Bearer Capability parameter. +- Calling Party Number – See Q.2763 Calling Party Number parameter. +- AESA for Calling Party – See Q.2763 AESA for Calling Party parameter. +- Called Party Number – See Q.2763 Called Party Number parameter. +- AESA for Called Party – See Q.2763 AESA for Called Party parameter. +- Called Party Subaddress – See Q.2763 Called Party Subaddress parameter. +- Calling Party Subaddress – See Q.2763 Calling Party Number parameter. +- Connection Identifier – See Q.2763 Connection Identifier parameter field. + +- Maximum End-to-End Transit Delay – See Q.2763 Maximum End-to-End Transit Delay parameter field. +- Cumulative Transit Delay – See Q.2763 Propagation Delay Counter parameter field. +- QoS Class – See Q.2763 Forward and Backward QoS Class parameter field. +- CDVT descriptor – See Q.2763 CDVT descriptor. +- Generic Identifier Transport – See Q.2763 Application generated identifier. +- Transit Network Selection – See Q.2763 Transit Network Selection parameter field. + +### **I.2.2 T\_Active PIC** + +A service feature request is received from a party: [e.g. in a Q.2932 FACILITY message and Q.932 ISDN feature activator, and Q.932 HOLD or RETRIEVE message (for a terminating party only)]. + +- Feature Activation – See Q.2932 Facility information element and Q.932 Feature Activation information element. + +If the CDP in force specifies that after a given feature activator is received, more digits are to be collected according to the numbering plan, then Feature Activation Indicator and Collected Address Information are known. + +If the CDP in force specifies that after a given feature activator is received, a variable number of digits are to be collected, then Feature Activation Indicator and Collected Digits are known. + +### **I.2.3 T\_Bearer\_Modify PIC** + +After detecting the T\_Modify\_Request DP the CCF/SSF may have additional information available from the signalling interface. This information may include the following: + +- ATM Cell Rate – See Q.2763 ATM Cell Rate parameter field. +- Additional ATM Cell Rate – See Q.2763 Additional ATM Cell Rate parameter field. + +### **I.2.4 T\_Bearer\_Active PIC** + +After detecting the T\_Modify\_Acknowledge DP the CCF/SSF may have additional information available from the signalling interface. This information may include the following: + +- ATM Cell Rate – See Q.2763 ATM Cell Rate parameter field. +- Additional ATM Cell Rate – See Q.2763 Additional ATM Cell Rate parameter field. + +# **APPENDIX II** + +## **Relationship of DP criteria to Signalling Parameters** + +This appendix provides examples of signalling information that may be used at selected Points in Call (PICs) to establish a connection under control of service logic. + +## **II.1 Relationship of DP criteria to signalling parameters** + +### **II.1.1 Analyse\_Information PIC** + +Information is being analysed and/or translated according to service subscription and access parameters. After the CCF/SSF determines the information has been analysed, the CCF/SSF may have analysis results associated with selected DP Criteria for the originating call portion. Following are examples of analysis results that may be returned for each DP Criteria for the connect operation: + +- AAL Parameters DP Criteria: + - VPCI/VCI to be returned to the connection originator in a DSS2 Call Proceeding Message or in a B-ISUP IAM Acknowledge message. + - Cause value to be returned to the connection originator in a Release Message. +- ATM Traffic Descriptor, Alternative ATM Traffic Descriptor, Minimum Acceptable ATM Traffic Descriptor, ATM Cell Rate, Additional ATM Cell Rate, Alternative ATM Cell Rate, Minimum ATM Cell Rate DP Criteria: + - VPCI/VCI to be returned to the connection originator in the DSS2 Call Proceeding Message or in the B-ISUP IAM Acknowledge message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the O\_Answer DP as the Cell Rate possibly returned to the connection originator in the DSS2 CONNECT message or B-ISUP ANswer Message. + - Cause value to be returned to the connection originator in a Release Message. +- Broadband Bearer Capability DP Criteria: + - VPCI/VCI to be returned to the connection originator in the DSS2 Call Proceeding Message or in the B-ISUP IAM Acknowledge message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the O\_Answer DP as the Cell Rate possibly returned to the connection originator in the DSS2 CONNECT message or B-ISUP ANswer Message. + - Cause value to be returned to the connection originator in a Release Message. +- Addressing/Numbering Plan Identification (called party) DP Criteria: + - VPCI/VCI to be returned to the connection originator in the DSS2 Call Proceeding Message or in the B-ISUP IAM Acknowledge message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the O\_Answer DP as the Cell Rate possibly returned to the connection originator in a DSS2 CONNECT message or in a B-ISUP ANswer Message. + - Called Party Address (routing address) to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Called Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Calling Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Transit Network Selection parameter to be forwarded toward the destination in a B-ISUP IAM. + - Cause value to be returned to the connection originator in a Release Message. +- Specific Called Party Digit Strings DP Criteria: + - VPCI/VCI to be returned to the connection originator in a DSS2 Call Proceeding Message or in a B-ISUP IAM Acknowledge message. + - Called Party Address (routing address) to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Called Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Calling Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Transit Network Selection parameter to be forwarded toward the destination in a B-ISUP IAM. + +- Cause value to be returned to the connection originator in a Release Message. +- Specific Called Party Address DP Criteria: + - VPCI/VCI to be returned to the connection originator in a DSS2 Call Proceeding Message or in a B-ISUP IAM Acknowledge message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the O\_Answer DP as the Cell Rate possibly returned to the connection originator in a DSS2 CONNECT message or in a B-ISUP ANswer Message. + - Called Party Address (routing address) to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Called Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Calling Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Transit Network Selection parameter to be forwarded toward the destination in a B-ISUP IAM. + - Cause value to be returned to the connection originator in a Release Message. +- Called Party Subaddress DP Criteria: + - VPCI/VCI to be returned to the connection originator in the DSS2 Call Proceeding Message or in the B-ISUP IAM Acknowledge message. + - Called Party Address (routing address) to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Called Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Calling Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Transit Network Selection parameter to be forwarded toward the destination in a B-ISUP IAM. + - Cause value to be returned to the connection originator in a Release Message. +- Addressing/Numbering Plan Identification (calling party) DP Criteria: + - VPCI/VCI to be returned to the connection originator in the DSS2 Call Proceeding Message or in the B-ISUP IAM Acknowledge message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the O\_Answer DP as the Cell Rate possibly returned to the connection originator in a DSS2 CONNECT message or in a B-ISUP ANswer Message. + - Calling Party Address to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Calling Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Transit Network Selection parameter to be forwarded toward the destination in a B-ISUP IAM. + - Cause value to be returned to the connection originator in a Release Message. + +- Specific Calling Party Digit Strings DP Criteria: + - VPCI/VCI to be returned to the connection originator in a DSS2 Call Proceeding Message or in a B-ISUP IAM Acknowledge message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the O\_Answer DP as the Cell Rate possibly returned to the connection originator in a DSS2 CONNECT message or in a B-ISUP ANswer Message. + - Calling Party Address to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Calling Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Transit Network Selection parameter to be forwarded toward the destination in a B-ISUP IAM. + - Cause value to be returned to the connection originator in a Release Message. +- Specific Calling Party Address DP Criteria: + - VPCI/VCI to be returned to the connection originator in the DSS2 Call Proceeding Message or in the B-ISUP IAM Acknowledge message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the O\_Answer DP as the Cell Rate possibly returned to the connection originator in the DSS2 CONNECT message or B-ISUP ANswer Message. + - Calling Party Address to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Calling Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Transit Network Selection parameter to be forwarded toward the destination in a B-ISUP IAM. + - Cause value to be returned to the connection originator in a Release Message. +- Calling Party Subaddress DP Criteria: + - VPCI/VCI to be returned to the connection originator in the DSS2 Call Proceeding Message or in the B-ISUP IAM Acknowledge message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the O\_Answer DP as the Cell Rate possibly returned to the connection originator in the DSS2 CONNECT message or B-ISUP ANswer Message. + - Calling Party Address to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Calling Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Transit Network Selection parameter to be forwarded toward the destination in a B-ISUP IAM. + - Cause value to be returned to the connection originator in a Release Message. +- Specific Connection Identifier DP Criteria: + - VPCI/VCI to be returned to the connection originator in the DSS2 Call Proceeding Message or in the B-ISUP IAM Acknowledge message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the O\_Answer DP as the Cell Rate possibly returned to the connection originator in the DSS2 CONNECT message or B-ISUP ANswer Message. + - Cause value to be returned to the connection originator in a Release Message. + +- End-to-End Transit Delay, Maximum End-to-End Transit Delay DP Criteria: + - VPCI/VCI to be returned to the connection originator in the DSS2 Call Proceeding Message or in the B-ISUP IAM Acknowledge message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the O\_Answer DP as the Cell Rate possibly returned to the connection originator in the DSS2 CONNECT message or B-ISUP ANswer Message. + - Cumulative Transit Delay to be included in a DSS2 SETUP or a B-ISUP IAM. + - Cause value to be returned to the connection originator in a Release Message. +- QoS Class DP Criteria: + - VPCI/VCI to be returned to the connection originator in the DSS2 Call Proceeding Message or in the B-ISUP IAM Acknowledge message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the O\_Answer DP as the Cell Rate possibly returned to the connection originator in the DSS2 CONNECT message or B-ISUP ANswer Message. + - Cause value to be returned to the connection originator in a Release Message. +- TNS Parameter DP Criteria: + - VPCI/VCI to be returned to the connection originator in the DSS2 Call Proceeding Message or in the B-ISUP IAM Acknowledge message. + - Called Party Address (routing address) or Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Called Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + +### II.1.2 Authorize\_Termination\_Attempt PIC + +The authority to route this connection to the terminating access is verified. Following are examples of information for selected DP criteria that may be received from the O\_BCSM to proceed with the connection: + +- AAL Parameters DP Criteria: + - VPCI/VCI to be forwarded toward the destination in a DSS2 SETUP Message or in a B-ISUP IAM message. +- ATM Traffic Descriptor, Alternative ATM Traffic Descriptor, Minimum Acceptable ATM Traffic Descriptor, ATM Cell Rate, Additional ATM Cell Rate, Alternative ATM Cell Rate, Minimum ATM Cell Rate DP Criteria: + - VPCI/VCI to be forwarded toward the destination in a DSS2 SETUP Message or in a B-ISUP IAM message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the T\_Answer DP as the Cell Rate possibly returned to the connection originator in the DSS2 CONNECT message or B-ISUP ANswer Message. +- Broadband Bearer Capability DP Criteria: + - VPCI/VCI to be forwarded toward the destination in a DSS2 SETUP Message or in a B-ISUP IAM message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the T\_Answer DP as the Cell Rate possibly returned to the connection originator in the DSS2 CONNECT message or B-ISUP ANswer Message. + +- Addressing/Numbering Plan Identification (called party) DP Criteria: + - VPCI/VCI to be forwarded toward the destination in a DSS2 SETUP Message or in a B-ISUP IAM message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the T\_Answer DP as the Cell Rate possibly returned to the connection originator in a DSS2 CONNECT message or in a B-ISUP ANswer Message. + - Called Party Address (routing address) to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Called Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Transit Network Selection parameter to be forwarded toward the destination in a B-ISUP IAM. +- Specific Called Party Digit Strings DP Criteria: + - VPCI/VCI to be forwarded toward the destination in a DSS2 SETUP Message or in a B-ISUP IAM message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the T\_Answer DP as the Cell Rate possibly returned to the connection originator in a DSS2 CONNECT message or in a B-ISUP ANswer Message. + - Called Party Address (routing address) to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Called Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Transit Network Selection parameter to be forwarded toward the destination in a B-ISUP IAM. +- Specific Called Party Address DP Criteria: + - VPCI/VCI to be forwarded toward the destination in a DSS2 SETUP Message or in a B-ISUP IAM message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the T\_Answer DP as the Cell Rate possibly returned to the connection originator in a DSS2 CONNECT message or in a B-ISUP ANswer Message. + - Called Party Address (routing address) to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Called Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Transit Network Selection parameter to be forwarded toward the destination in a B-ISUP IAM. +- Called Party Subaddress DP Criteria: + - VPCI/VCI to be forwarded toward the destination in a DSS2 SETUP Message or in a B-ISUP IAM message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the T\_Answer DP as the Cell Rate possibly returned to the connection originator in a DSS2 CONNECT message or in a B-ISUP ANswer Message. + - Called Party Address (routing address) to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Called Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + +- Transit Network Selection parameter to be forwarded toward the destination in a B-ISUP IAM. +- End-to-End Transit Delay, Maximum End-to-End Transit Delay DP Criteria: + - VPCI/VCI to be forwarded toward the destination in a DSS2 SETUP Message or in a B-ISUP IAM message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the T\_Answer DP as the Cell Rate possibly returned to the connection originator in the DSS2 CONNECT message or B-ISUP ANswer Message. +- QoS Class DP Criteria: + - VPCI/VCI to be forwarded toward the destination in a DSS2 SETUP Message or in a B-ISUP IAM message. + - Cell Rate to be forwarded toward the destination in a DSS2 SETUP or a B-ISUP IAM. Also used at the T\_Answer DP as the Cell Rate possibly returned to the connection originator in the DSS2 CONNECT message or B-ISUP ANswer Message. +- TNS Parameter DP Criteria: + - VPCI/VCI to be forwarded toward the destination in a DSS2 SETUP Message or in a B-ISUP IAM message. + - Called Party Address (routing address) to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + - Called Party Subaddress to be forwarded toward the destination in a DSS2 SETUP or in a B-ISUP IAM. + +# **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/Q/T-REC-Q.1290-199805-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1290-199805-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1b82cb7d2cf87e3f617bd3e86d07a50c9f2b25ef --- /dev/null +++ b/marked/Q/T-REC-Q.1290-199805-I_PDF-E/raw.md @@ -0,0 +1,647 @@ + + +![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 + +**Q.1290** + +(05/98) + +SERIES Q: SWITCHING AND SIGNALLING + +Intelligent Network + +--- + +**Glossary of terms used in the definition of +intelligent networks** + +ITU-T Recommendation Q.1290 + +(Previously CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +## **SWITCHING AND SIGNALLING** + +| | | +|----------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +## **ITU-T RECOMMENDATION Q.1290** + +# **GLOSSARY OF TERMS USED IN THE DEFINITION OF INTELLIGENT NETWORKS** + +## **Summary** + +This Recommendation provides a glossary of terms and definitions which have been studied for application in the documentation of intelligent networks. These terms will also be incorporated in Recommendation Q.9, "Vocabulary of Switching and Signalling Terms". + +TMN management systems terminology needs to be harmonized with IN terms and is not included in this version of this Recommendation. + +The text in this Recommendation is considered to be stable. Companion Recommendations include the Q.1200 series of Recommendations. + +### **Source** + +ITU-T Recommendation Q.1290 was revised by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 15th of May 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 General ..... | 1 | +| 1.1 Introduction..... | 1 | +| 1.2 Conventions ..... | 1 | +| 2 Terms and definitions (listed alphabetically)..... | 1 | +| Annex A – Acronyms ..... | 14 | + + + +# GLOSSARY OF TERMS USED IN THE DEFINITION OF INTELLIGENT NETWORKS + +*(revised in 1998)* + +# 1 General + +## 1.1 Introduction + +This Recommendation provides a glossary of terms and definitions which have been studied for application in the documentation of intelligent networks. These terms will also be incorporated in Recommendation Q.9, "Vocabulary of Switching and Signalling Terms". + +To the extent practicable, terms that have been defined previously are used unchanged and reference to the source of the definition is shown next to the term in parenthesis. The definitions that have been changed to make them appropriate for this application are considered to be new definitions; however, reference to the source definition is also shown in parenthesis. + +## 1.2 Conventions + +The following notations and styles are used in the text of this Recommendation as appropriate: + +- 1) The names of IN SIBs are written with each component word capitalized and spaces between the words (e.g. LOG CALL INFORMATION). +- 2) The names of IN information flows are written with each component word capitalized and spaces between the words and the appropriate type descriptor is included (e.g. Call Information Report req.ind.). +- 3) The names of information elements in IN information flows are written with each component word capitalized and spaces between the words (e.g. Request Information). +- 4) The abbreviation for the word identity in an IN information element is written ID. +- 5) The names of IN detection points are written with each component word capitalized and underscores between the words (e.g. O\_Disconnect). +- 6) Other names defined are not capitalized (e.g. detection points). +- 7) The names of information flows defined in Recommendation Q.71 are written in upper case and the appropriate type descriptor is included (e.g. SETUP req.ind). +- 8) The names of the personal mobility procedures defined in draft Recommendation F.851 are written as in InCall, OutCall and AllCall registration and deregistration. + +## 2 Terms and definitions (listed alphabetically) + +For the purpose of this Recommendation, the following definitions apply: + +- 2.1 **access:** A means of interaction between a user and a network. +- 2.2 **access channel (Q.9 – 0008, I.112 – 414):** A designated part of the information transfer capability having specified characteristics, provided at the user-network interface. +- 2.3 **access code:** A code(s) for "customized numbering plan": attendant access, escapes to public network, etc. + +- 2.4 **access function:** A set of processes in a network that provide for interaction between the user and a network. +- 2.5 **Adjunct (AD):** An entity in the intelligent network that is functionally equivalent to a service control point but is directly connected to a service switching point. +- 2.6 **Administration:** In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunications Administration and a recognized operating agency. +- 2.7 **agent:** Entity acting on behalf of another. +- 2.8 **alerting pattern:** a specific pattern used to alert a subscriber (e.g. distinctive ringing, tones etc.). Recommendation Q.931 refers. +- 2.9 **Analogue Display Service Interface (ADSI) server:** A network element capable of sending textual messages for display on suitably equipped analog terminals. +- 2.10 **application:** Refer to Fascicle I.3 of the *Blue Book*. +- 2.11 **Application Context (AC):** Refer to Recommendation X.207. +- 2.12 **Application Context Negotiation (ACN):** The process of negotiation at the beginning of a transaction that determines which set of user protocol ASEs will be potentially exchanged during a transaction. +- 2.13 **Application Entity (AE) (Q.9 – 2156 modified):** The set of system-independent application activities that are made available as application services to the application agent, e.g. a set of application service elements which together perform all or part of the communication aspects of an application process. +- 2.14 **Application Entity Invocation (AEI):** The actual "run-time" program that performs all, or a subset, of the communication functions that comprise the AE-type. +- 2.15 **Application Protocol Data Unit (APDU):** A PDU carrying application layer control information and data. +- 2.16 **Application Service Element (ASE):** Refer to Recommendation X.207. +- 2.17 **attribute:** Refer to 8.1/X.501 +- 2.18 **Automatic Speech Recognition (ASR):** The function of converting the spoken word into a machine understandable form. +- 2.19 **basic call:** A call between two users that consists of communication only, and does not include additional features. +- 2.20 **Basic Call Process (BCP):** The sequence of activities used in establishing, maintaining and releasing a basic call. +- 2.21 **Basic Call State Model (BCSM):** A high-level finite state machine model of call processing for basic call control (i.e. a two-party non-IN call). The model might only cover a portion of a call attempt, e.g. an originating BCSM or terminating BCSM, or the whole attempted call connection, originating user to terminating user. +- 2.22 **Basic Rate Interface (BRI):** Refer to Recommendation Q.9. +- 2.23 **bearer control:** The set of functions used to direct the low layer (common) means of transmission. +- 2.24 **bind:** A mechanism used during Association Control for authentication. Refer to Recommendation X.500. +- 2.25 **business group:** A logical grouping of service subscribers, who share a set of service properties. + +- 2.26 Business Group Identity (BGID):** The Basic Business Group or Multiswitch Business Group Identity of the calling/called party, e.g. group-based services. +- 2.27 call (Q.9 – 0009-2):** The use, or possible use, of one or more connections set up between two or more users and/or service(s). +- 2.28 call control:** The set of functions used to process a call (e.g. provide service features and establish, supervise, maintain and release connections). +- 2.29 Call Control Agent Functional Entity (CCAF):** A functional entity that provides network access functions for users, interacting with call control functional entities in providing services. +- 2.30 Call Control Function (CCF):** The application process that provides call/connection processing and control. +- 2.31 call control functional entity:** Functional entities which cooperate with each other to provide network call processing functions. +- 2.32 call related:** Service interaction(s) performed by the network on behalf of an end user, which require switching capabilities and a call reference to exist within the SSP. +- 2.33 call unrelated:** Service interaction(s) performed by the network on behalf of an end user, which do not require switching capabilities in the SSP. Also the interaction(s) do not require that a call reference exist within the SSP. Also referred to as non-call related. +- 2.34 called party/user:** The entity which receives a call. +- 2.35 calling party/user:** The entity which initiates a call. +- 2.36 called party business group ID:** Identifies the business group associated with the called party. +- 2.37 called party subaddress:** Address information additional to the called party that identifies a specific CPE beyond the S/T reference point. +- 2.38 call gapping encountered:** Indicates the type of gapping the request for instructions have been subjected to, if any. +- 2.39 calling facility group:** Identifier for incoming trunks or private facilities. +- 2.40 calling facility group member:** Identifier for individual member of a facility group. +- 2.41 calling party business group ID:** Identifies the business group associated with the calling party. +- 2.42 calling party subaddress:** the subaddress information identifying the calling party. +- 2.43 call model:** A representation of functions involved in processing a call. +- 2.44 call party handling:** A description of a network's ability to manipulate individual parties to a call independently. +- 2.45 call/service processing:** The execution of logic by a switching or control function to advance a call attempt or a service request. +- 2.46 Call Segment (CS):** A grouping of all the legs connected to a particular connection point. +- 2.47 Call Segment Model (CSM):** A representation of the processing of a call in terms of call segments. + +- 2.48 Capability Set (CS):** A coherent and consistent set of network capabilities which have been standardized in a particular release. +- 2.49 Carrier Access Code (CAC):** A code used to select a carrier. +- 2.50 carrier (commercial telecommunications):** The organization whose function is to provide the particular service, e.g. an agent of a private network/facility, intra-serving area, or a specific inter-exchange carrier or international carrier. +- 2.51 carrier identification code:** Identifies the carrier. +- 2.52 carrier selection:** The act or ability to select or choose between telecommunications service providers. +- 2.53 charge number:** The number that identifies the entity to be charged for the call. +- 2.54 class of service:** This is either a Customer Class of Service, a Trunk Class of Service, or a Private-Facility Class of Service. It may refer to either originating or terminating accesses. +- 2.55 collected address information:** An interpretation of the dialled digits specifying the nature of address and the called party number. +- 2.56 collected digits:** A variable number of digits collected. +- 2.57 Common Management Information System (CMIS):** See Recommendation X.700. +- 2.58 confidentiality (ITU-T X.800):** The property that information is not made available or disclosed to unauthorized individuals, entities or processes. +- 2.59 connection:** Refer to Recommendation Q.9. +- 2.60 connection control:** The set of functions used for setting up, maintaining and releasing a communication path between two or more users or a user and a network entity, e.g. a dual tone multi-frequency receiver. +- 2.61 connection view state:** The set of Call Party Handling functionality supported by an SSF can be defined as a catalogue of Connection View States. +- 2.62 connection point:** A connection point is a representation of the interconnection of legs, as viewed from the CSA, that allows information to flow between legs. +- 2.63 consumer:** Refer to Recommendation X.880. +- 2.64 control:** To exercise a directing influence. +- 2.65 controlling leg:** For IN CS-2, the controlling leg is the leg that represents the local access interface at local exchange or the remote access interface at transit exchange (e.g. the incoming line or trunk in an originating call segment, or the outgoing line or trunk in a terminating call segment). +- 2.66 control window:** An interval during which an entity involved in call/service processing is subject to the control of the service control function. +- 2.67 core feature:** A service feature that is fundamental to a service, i.e. in the absence of the feature, the service is not a viable service offering. +- 2.68 Customized Dialling Plan (CDP):** Also known as "customer numbering plan" or "private numbering plan"; see "Access Code". +- 2.69 data:** User and/or network information. +- 2.70 database:** An entity that stores user and/or network information. +- 2.71 data management:** Establishing, updating and administering databases in the network. + +- 2.72 **data object:** An individually addressable unit of information. +- 2.73 **data integrity (ITU-T X.800):** The property that data has not been altered or destroyed in an unauthorized manner. +- 2.74 **data origin authentication (ITU-T X.800):** The corroboration that the source is as claimed. +- 2.75 **data template:** A specified logical structure for a collection of data objects, including allowable ranges for their values and other data consistency specifications. +- 2.76 **destination routing address:** A list of called party numbers (primary and alternative). +- 2.77 **Detection Point (DP):** A point in basic call processing at which a processing event may be reported to the service control function and transfer of processing control can occur. +- 2.78 **destination user:** The entity to which calls are directed. +- 2.79 **dialled digits:** Untranslated address information collected/received from the originating user/line/trunk. +- 2.80 **dialogue:** A conversation or an exchange of information. +- 2.81 **Digital Subscriber Signalling System No. 1 (DSS 1):** The standardized message-based user-network signalling system for narrow-band ISDN. +- 2.82 **directory:** Refer to clause 12/X.500. +- 2.83 **Directory Access Protocol (DAP):** Refer to clause 12/X.500. +- 2.84 **Directory Entry (DE):** Refer to 7.1/X.501. +- 2.85 **Directory Information Tree (DIT):** Refer to 7.1/X.501. +- 2.86 **Directory System Protocol (DSP):** Refer to clause 12/X.500. +- 2.87 **directory user agent:** Refer to 6.1/X.500. +- 2.88 **Distinguished Name (DN):** Refer to 9.1/X.501. +- 2.89 **Distributed Functional Plane (DFP):** The plane in the unified functional model containing functional entities and their relationships. +- 2.90 **Distributed Service Logic (DSL):** Logic in the distributed functional plane that is used to realize service-independent building blocks. +- 2.91 **domain:** Refer to IN domain. +- 2.92 **Dual Tone Multi-Frequency (DTMF):** An analogue inband access signalling system. +- 2.93 **dynamic arming/disarming:** Enabling/disabling of a detection point by a service control function in the course of service control execution for a particular call/service attempt. +- 2.94 **dynamic data:** Information subject to change as a result of an event. +- 2.95 **element:** An identifiable physical unit. +- 2.96 **elementary function:** A primary or basic function that cannot be further decomposed. +- 2.97 **entity (Q.9 – 7110):** A part, device, subsystem, functional unit, equipment or system that can be individually considered. In ISDN the term is used to refer to a particular system or subsystem such as a user terminal or a digital exchange. It is also used to refer to a set of functions of a particular system at a location, e.g. the layer 2 functions of a signalling system at a user terminal. + +- 2.98 event:** A specific input to and/or output from a given state in a finite state machine model that causes a transition from one state to another. +- 2.99 Event Detection Point (EDP):** A detection point that is armed for a particular instance of a call. +- 2.100 executive process:** A process that controls the execution of other processes. +- 2.101 Extended User Interface (EUI) Server:** This is an example of SRF that provides the functionality to interact with callers using speech recognition, DTMF, Text-To-Speech Synthesis, context-sensitive announcements, and ADSI CPE with context-sensitive display. +- 2.102 facility code:** Code(s) used to select/activate a facility related service, e.g. a two-digit code preceded by "#" to select a preferred routing. +- 2.103 facility group:** Indicates the particular group of facilities to route the call. +- 2.104 facility group member:** Indicates the specific member of a trunk group or a multi-line hunt group. +- 2.105 Facility Restriction Level (FRL):** The permission level associated with an incoming facility, e.g. trunk line. +- 2.106 feature:** A reusable capability provided to a user by one or more services in a network. +- 2.107 feature code:** Code(s) used to select/activate a service feature (e.g. forwarding, using two or three digit codes preceded by \* or 11 or #, and which may precede subsequent digit selection). +- 2.108 feature interaction:** A situation that occurs when an action of one feature affects an action or capability of another. This situation is sometime referred to as Service Interaction. This situation may be desirable or undesirable. A desirable Feature Interaction is referred to as Feature cooperation. An undesirable Feature Interaction is referred to as Feature Interference. +- 2.109 feature interactions manager:** The entity in the SSF that provides mechanisms to support multiple concurrent instances of IN service logic instances and non-IN service logic instances on a single call. +- 2.110 Finite State Machine (FSM):** A system having a finite number of states and specified transitions between states. +- 2.111 finite state machine model:** An operational model of an entity that is described by the finite set of states the entity can be in and the finite set of transitions possible from one state to another. +- 2.112 function (I.112 – 403):** A set of processes defined for the purpose of achieving a specified objective. +- 2.113 functional entity (Q.9 – 7112):** An entity that comprises a specific set of functions at a given location. +- 2.114 functional entity (In telecommunications service provision applications) (Q.9 – 7113):** A grouping of service providing functions in a single location and a subset of the total set of functions required to provide the service. +- 2.115 Functional Entity Action (FEA):** An action performed by a functional entity as a result of a specific stimulus while the functional entity is in a specific state. +- 2.116 functional routine:** Logic that controls the performance of a set of actions to accomplish "routine" tasks, e.g. retrieve information, pass information, etc. +- 2.117 generic name:** This identifier, if present, carries name characters and presentation status for the calling and redirecting users. + +- 2.118 global control:** Control of functions that are distributed among several entities. +- 2.119 Global Functional Plane (GFP):** The plane in the unified functional model that defines Service-Independent Building Blocks (SIBs) used in providing service features. +- 2.120 Global Service Logic (GSL):** Logic in the global functional plane that is used to realize features. +- 2.121 Global Virtual Network Services (GVNS):** These are the participating services of the global switched GVNS service. +- 2.122 home network:** The network to which the user is normally connected, or the service provider with which the user is associated. +- 2.123 High-Level SIB (HLSIB):** A reusable part of a service feature as normal SIBs, but composed out of SIBs and other HLSIBs which can be executed sequentially. An HLSIB stands for abstraction by hiding service logic and parts of the "service support data" that is considered to be local to the HLSIB. +- 2.124 inband (inband signalling Q.9 – 2010):** A signalling method in which signals are sent over the same transmission channel or circuit as the user's communication and in the same frequency band as that provided for the users – an example is DTMF. +- 2.125 information flow (Q.9 – 7120):** An interaction between a communicating pair of functional entities. +- 2.126 Intelligent Network (IN):** A telecommunications network architecture that provides flexibility for facilitating the introduction of new capabilities and services, including those under customer control. +- 2.127 Intelligent Network Application Protocol (INAP):** A protocol for intelligent network applications. +- 2.128 IN Conceptual Model (INCM):** A planar model used for defining the intelligent network architecture. +- 2.129 IN DataBase (INDB):** A physical entity used for information storage in the intelligent network. +- 2.130 IN DataBase Management System (INDBMS):** A system used for establishing and/or administering information storage in the INDB. +- 2.131 IN domain:** A part of an IN encapsulating predefined roles (e.g. network operator or service provider). +- 2.132 IN supported service:** A service provided using the capabilities of the intelligent network. +- 2.133 IN Switching Manager (IN-SM):** The entity in the SSF that interacts with the SCF in the course of providing IN service features to users. +- 2.134 IN Switching State Model (IN-SSM):** Provides a finite state machine description of SSF/CCF IN call/connection processing in terms of IN call/connection states. +- 2.135 integrated services digital network (ISDN):** see 2.3/I.112, 2.3, Definition 308. +- 2.136 Intelligent Peripheral (IP):** A physical entity that implements a specialized resource function. +- 2.137 ISDN User Part (ISDN-UP):** The Signalling System No. 7 protocol which provides the signalling functions required to support basic bearer services and supplementary services for voice and non-voice applications in an integrated services digital network. + +- 2.138 interworking function:** Functionality separating interworking functions from other independent functional or physical architectures. +- 2.139 interface (Q.9 – 4001):** A shared boundary, for example, the boundary between two subsystems or two devices. +- 2.140 IP available:** Indication whether or not an IP is attached, and available at the SSP. +- 2.141 IPSSP capabilities:** Indication of which IP resources are supported, and attached at the SSP from which the call was suspended. +- 2.142 layer (Q.9 – 2160):** A conceptual region that embodies one or more functions between an upper and a lower logical boundary within a hierarchy of functions. +- 2.143 leg:** A representation within a call processing state model representing a telecommunication path towards some addressable entity (e.g. a path toward a user, intelligent peripheral unit etc.). +- 2.144 Local Exchange (LE) (local central office) (Q.9 – 1002):** An exchange in which subscriber lines terminate. +- 2.145 management function (M.60 modified):** A set of processes used for the management of an entity (e.g. database management capabilities covering maintenance of operations, administration, maintenance, and provisioning). +- 2.146 management building block:** A reusable set of functional entity actions and information flows used to provide service management functions in the network. +- 2.147 monitor window:** An interval during which an entity performs the monitoring function. +- 2.148 Multiple Association Control Function (MACF):** Represents the rules and regulations governing the coordination of set of peer-to-peer communications within an Application Entity Invocation (AEI). +- 2.149 network:** See Volume I, Fascicle I.3 of the *Blue Book*. +- 2.150 Network Access Point (NAP):** The point of connection of a physical entity that provides network access for users. +- 2.151 Network Functional Architecture (NFA):** The functional block which consists of the network elements. +- 2.152 Network Manager (NM):** The Network Manager is the entity providing the basic switching and transmission capabilities as well as the service execution capabilities (offered by the SCP, SDP and IP) to the Service Manager. The NM is also responsible for the development and maintenance of the transmission, switching and service execution capabilities. The NM encompasses both the TMN network management functionality and the network element management functionality. +- 2.153 network operator:** The network operator is responsible for the development, provision and maintenance of real-time networking services and for operating the corresponding networks. +- 2.154 network provider:** The organization that maintains and operates the network components required for IN functionality. A network provider may also take more than one role, e.g. also acting as Service Provider. +- 2.155 operator services information:** Information sent between operator services entities identifying charging and service type options. +- 2.156 optional feature:** A service feature added to core features to optionally enhance a service offering. +- 2.157 open systems interconnection (OSI):** Refer to Recommendation X.200 – Basic reference model. + +- 2.158 **original called party ID:** Refer to Recommendation Q.762. +- 2.159 **Originating Line Information (OLI):** Information indicating a toll class of service for the call. +- 2.160 **persistent data:** Information that endures beyond a single instance of use, e.g. longer than one call attempt. +- 2.161 **Personal Mobility (PM):** The flexibility of the user's access to telecommunications service provision enabling the user to associate with and/or configure any terminal to meet individual requirements. +- 2.162 **private network:** A network which provides services to a specific set of users only (see Recommendation I.570). +- 2.163 **physical plane:** The plane in the unified functional model containing elements and their interfaces that implement functional entities. +- 2.164 **Plain Old Telephone Service (POTS):** A call that requires nothing more than basic call handling. +- 2.165 **plane:** A part of the unified functional model. +- 2.166 **Point In Call (PIC):** A state in a basic call state model. +- 2.167 **Point of Control (POC):** The point in service logic where two different service processes may interact. Possible points of control are: "Point of Initiation (POI)", "Point of Synchronization (POS)", and "Point of Return (POR)" which is considered to be a specialized point of synchronization. Inter process data is conveyed via point of controls. +- 2.168 **Point of Initiation (POI):** A functional interface between a service process (including the basic call process) and service logic of another service process to initiate (further) service processing. +- 2.169 **Point of Return (POR):** A functional interface between service logic of a service process and basic call processing over which call processing control is returned to basic call processing, whereby the execution of the service logic of the service process is terminated. A point of return is considered to be a specialized point of synchronization. +- 2.170 **Point of Synchronization (POS):** A functional interface between service logic of two service processes over which asynchronous communication is initiated, i.e. the execution of the service logic that has a point of synchronization connected to it has to wait until the synchronization signal has arrived. Synchronous communication may be achieved by performing a handshake with the two points of synchronization. +- 2.171 **Primary Rate Interface (PRI):** Refer to Recommendation Q.9. +- 2.172 **Private Telecommunication Network Exchange (PTNX):** A physical realization of automatic telecommunications switching functionality for private telecommunications network(s) providing call functions for various types of customer premises equipment. +- 2.173 **Protocol Data Unit (PDU):** Refer to Recommendation X.200 – OSI Basic Reference Model. +- 2.174 **protocol layer (based on Q.9 – 2160 – definition of "layer"):** A group of one or more functions within an upper and lower logical boundary within a protocol reference model. [Layer (N) has boundaries to layer (N + 1) and to layer (N – 1).] +- 2.175 **Public Switched Telephony Network (PSTN):** A telecommunications network established to perform telephone services for the public subscribers. +- 2.176 **redirection information:** Refer to Recommendation Q.763. + +- 2.177 **relationship (Q.65):** The complete set of information flows, where they exist, between two functional entities. +- 2.178 **Recognized Operating Agency (ROA):** Refer to "Administration". +- 2.179 **Relative Distinguished Name (RDN):** Refer to 9.1/X.501. +- 2.180 **route index:** A pointer to a specific trunk routing group. +- 2.181 **service (Q.9 – 7011, modified):** That which is offered by an Administration or ROA to its customers in order to satisfy a telecommunication requirement. +- 2.182 **service address information:** A sequence of digits that identifies a specific service. +- 2.183 **service control:** Direction of the functions or processes used to provide a specific telecommunications service. +- 2.184 **service control customization:** Functionality to personalize a stand-alone commercial telecommunications service offering, by the server on behalf of a client. +- 2.185 **Service Control Function (SCF):** The application of service logic to control functional entities in providing intelligent network services. +- 2.186 **Service Control Function Identifier (SCFID):** The means of identification of an SCF. +- 2.187 **Service Control Point (SCP):** A physical entity in the intelligent network that implements a service control function. +- 2.188 **Service Creation Environment (SCE):** The set of functions to support service creation processing by altering service logic and service data on behalf of the controlling node. +- 2.189 **Service Creation Environment Function (SCEF):** The set of functions that support the service creation process, the output of which includes both service logic programs and service data. +- 2.190 **Service Creation Environment Point (SCEP):** A physical entity that implements the service creation environment function. +- 2.191 **service creation platform:** A set of service-independent objects or functions that allow the creation of services in an intelligent network. +- 2.192 **service creation process:** The conception, design and implementation of a capability to provide a service. +- 2.193 **service data:** Customer and/or network information required for the proper functioning of a service. +- 2.194 **Service Data Function (SDF):** The set of functions that provides for the management of service data in accordance with a service data template. +- 2.195 **Service Data Point (SDP):** A physical entity that implements a service data function. +- 2.196 **service data template:** A data template related to a specific service logic program. +- 2.197 **Service Feature (SF):** A reusable part of one or more service capabilities forming all or part of a service. +- 2.198 **service independent:** +- 1) not dependent on the availability of other services; or + - 2) having freedom to create any service desired. + +- 2.199 Service independent Building block (SIB):** A reusable set of functional entity actions and information flows used to support a service feature or a part of a service feature in an intelligent network. +- 2.200 service instance data:** Service instance data template defines data related to a service subscriber's profile that exist before the service is invoked and can be modified and updated as a result of the service processing activity. This type of data can be read within the service execution and be stored to be used in further service invocations. +- 2.201 service interaction:** See "feature interaction". +- 2.202 Service Logic (SL):** A sequence of processes/functions used to support a specific service. +- 2.203 Service Logic Control Program (SLCP):** A program that may be run to realize an instance of a service feature. +- 2.204 Service Logic Management Program (SLMP):** A program that may run to realize the management of user and/or network information. +- 2.205 Service Logic processing Program (SLP):** A software program containing service logic. +- 2.206 Service Logic processing Program (use) Instance (SLPI):** The invocation and application of a particular service logic program in providing a service or a service feature for a specific call/service attempt. +- 2.207 Service Manager (SM):** The entity that provides the services to its customers on a contractual basis, and which is responsible for the services offered. The SM uses the service execution, transmission and switching capabilities offered by the Network Manager to offer the services to its customers. +- 2.208 service management:** Management of user and/or network information required for the proper operation of a service. +- 2.209 Service Management Access Function (SMAF):** A functional interface between network operators and/or subscribers and network service management functional entities. +- 2.210 Service Management Agent Function (SMAF):** The entity equivalent to the work station function between network operators and/or subscribers and network service management functional entities. +- 2.211 Service Management Function (SMF):** The set of processes that support the management of user and/or network information, including service data and service logic programs that are required for the proper operation of a service. +- 2.212 Service Management Point (SMP):** A physical entity that implements a service management function. +- 2.213 Service Management System (SMS):** A set of service management functions. +- 2.214 Service Node (SN):** A physical entity that contains the service control function, service data function, specialized resource function and service switching/call control functions. +- 2.215 service plane:** The plane in the unified functional model that describes services. + +**2.216 service process:** A chain of "service-independent building blocks" or "high-level service-independent building blocks" executed sequentially, but may be in parallel with other service processes. Service processes are initiated via a "point of initiation" and synchronized via "point(s) of synchronization". A service process is always contained within one "domain". A process in one domain is able to spawn new processes and to communicate with processes in other domains or its own domain. The "points of control" and "call instance data" crossing the border of two domains is part of their logical interface. The "basic call processing" can be regarded as a specialized service process. + +**2.217 service processing:** The execution of service control and basic call processing functions to provide a service. + +**2.218 Service Subscriber (SS):** An entity that contracts to receive services offered by Service Providers. + +**2.219 Service Switching and Control Point (SSCP):** The physical entity that contains the service control function, service data function and the service switching/call control functions. + +**2.220 Service Support Data (SSD):** An identifier that defines data parameters of specific service feature descriptions in the global functional plane. + +**2.221 Service Switching Function (SSF):** The set of processes that provide the communication path for interaction between a call control function and a service control function. + +**2.222 Service Switching function Management Entity (SSME):** Functionality of an entity controlling the system management of the node. + +**2.223 Service Switching Point (SSP):** The physical entity that implements the service switching function. + +**2.224 Service Trigger Information (STI):** Information whose reception initiates an action in support of a service. + +**2.225 Service User (SU):** An entity external to the network that uses its services. + +**2.226 serving area ID:** The identity of the local area where a service is available from the server. + +**2.227 Single Association Control Function (SACF):** Represents the rules and regulation governing the use of the ASEs that are being used for communication over a single Application Association to a peer. + +**2.228 Single Association Object (SAO):** The representation of the functions that are needed to communicate over a single Application Association to a peer. + +**2.229 single-ended service feature:** A feature, e.g. call/service attempt manipulation, that applies to only one of the parties that may be involved on a call/service attempt. + +**2.230 Specialized Resource Function (SRF):** The set of functions that provide for the control and access to resources used in providing services. + +**2.231 state (in FSM):** A description of an entity defined by the values of its object attributes at a given point in time. + +**2.232 state (in SDL) (Q.9 – 6942):** A condition in which the action of a process is suspended awaiting an input. + +- 2.233 static arming/disarming:** Enabling/disabling of a detection point, as directed by a service management function, to cause a specified action by call/service processing whenever a specific point in call is encountered. +- 2.234 static data:** Information that remains unchanged for the duration of several calls or instance of use of a service. (Usually controlled by a source external to the network.) +- 2.235 supplemented call:** A basic call with added service features or capabilities. +- 2.236 supplier:** See Recommendation X.880. +- 2.237 Telecommunication Management Network (TMN):** The entity which provides the means used to transport and process information related to management functions for the telecommunications network. +- 2.238 terminal type:** Indicates the type of terminal to the SCF (e.g. DTMF phone, ISDN terminal). +- 2.239 transaction (Fascicle I.3):** An association between two TC providers. +- 2.240 Transaction Capabilities (TC):** A peer-to-peer protocol used to support remote operations in telecommunication networks. +- 2.241 Transaction Capabilities Application Part (TCAP):** The Application layer services and protocols of TC consisting of the component sublayer and the Transaction sublayer, dialogue control. +- 2.242 transit network selection:** This identifier if present, identifies the Carrier Identification Code and the Circuit Code. +- 2.243 transition:** In a finite state machine model, a change in the state of an entity resulting from a change in the values of its object attributes. +- 2.244 travelling class mark:** Provides information for routing or screening and allows for carrying class of service information along with calling number through a network. +- 2.245 trigger:** A stimulus for initiating an action. +- 2.246 Trigger Detection Point (TDP):** A detection point in basic call processing that is statically armed. +- 2.247 Universal Personal Telecommunications (UPT):** A telecommunications service which uninterrupted enables access to telecommunications services while allowing personal mobility. +- 2.248 unbind:** A mechanism used during Association Control for authentication. Refer to Recommendation X.500. +- 2.249 user:** An entity external to the network that uses its service(s). +- 2.250 User-to-Service Information (USI):** This information element is used to convey information from the user to the network. +- 2.251 vendor- or implementation-independent:** The characteristic that products from different vendors are able to work together in the same environment, and/or, physical units serving as the same functional entity(ies) produced by different vendors can be used interchangeably. +- 2.252 Virtual Private Network (VPN):** A network consisting of physical components of both public and private networks that together behave as a private network. + +## Annex A + +### Acronyms + +| | | +|-------|---------------------------------------------| +| AC | Application Context | +| ACN | Application Context Negotiation | +| ACSE | Application Control Service Element | +| AD | Adjunct | +| ADSI | Analogue Display Service Interface (Server) | +| AE | Application Entity | +| AEI | Application Entity Invocation | +| AOC | Advice of Charge | +| APC | Apply Charging | +| APCI | Application Protocol Control Information | +| APDU | Application Protocol Data Unit | +| API | Application Programming Interface | +| APR | Apply Charging Report | +| ASE | Application Service Element | +| ASR | Automatic Speech Recognition | +| BCP | Basic Call Process | +| BCSM | Basic Call State Model | +| BCUP | Basic Call Unrelated Process | +| BCUSM | Basic Call Unrelated State Model | +| BGID | Business Group Identity | +| BRI | Basic Rate Interface | +| CAC | Carrier Access Code | +| CCAF | Call Control Agent Function | +| CCF | Call Control Function | +| CDP | Customized Dialling Plan | +| CHA | Component Handler | +| CID | Call Instance Data | +| CM | Call Manager | +| CMIS | Common Management Information System | +| CS | Call Segment | +| CS | Capability Set | +| CSM | Call Segment Model | +| CUSF | Call-Unrelated Service Function | +| DAP | Directory Access Protocol | +| DE | Directory Entry | +| DET | Determination | + +| | | +|----------|----------------------------------------------------------------------------------| +| DFP | Distributed Functional Plane | +| DHA | Dialogue Handler | +| DIT | Directory Information Tree | +| DLE | Destination Local Exchange | +| DN | Directory Number | +| DN | Distinguished Name | +| DP | Detection Point | +| DSA | Directory System Agent | +| DSL | Distributed Service Logic | +| DSP | Directory System Protocol | +| DSS 1 | Digital Subscriber Signalling System No. 1 | +| DTMF | Dual Tone Multi-Frequency | +| DUA | Directory User Agent | +| EDP | Event Detection Point | +| EDP-N | Event Detection Point-Notification | +| EDP-R | Event Detection Point-Request | +| EUI | Extended User Interface Server | +| FCI | Furnish Charging Information | +| FEA | Functional Entity Action | +| FEAM | Functional Entity Access Manager | +| FIM | Feature Interactions Manager | +| FRL | Facility Restriction Level | +| FSM | Finite State Machine | +| GEN | Generation | +| GFP | Global Functional Plane | +| GSL | Global Service Logic | +| GVNS | Global Virtual Network Services | +| HLSIB | High-Level Service Independent Block | +| IAF | Intelligent Access Function | +| IEC | International Electrotechnical Commission | +| IMT-2000 | International Mobile Telecommunications-2000 | +| IN | Intelligent Network | +| INAP | Intelligent Network Application Protocol | +| INCM | IN Conceptual Model | +| INDB | IN DataBase | +| INDBMS | IN DataBase Management System | +| IN-SM | IN Switching Manager | +| IN-SSM | IN Switching State Model | +| IP | Intelligent Peripheral | +| ISDN | Integrated Services Digital Network | +| ISDN-UP | ISDN User Part | +| ISO | International Organization for Standardization | +| ISUP | Integrated Services Digital Network-User Part | +| ISUP | ISDN-UP | +| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector | +| LE | Local Exchange | + +| | | +|------|----------------------------------------------------| +| MACF | Multiple Association Control Function | +| NAP | Network Access Point | +| NEF | Network Element Function | +| NFA | Network Functional Architecture | +| NM | Network Manager | +| NSAP | Network Service Access Point | +| OFC | Off-line Charging (billing/accounting information) | +| OLE | Originating Local Exchange | +| OLI | Originating Line Information | +| ONC | On-line Charging (user access information) | +| OSF | Operation System Function | +| OSI | Open Systems Interconnection | +| OUT | Output | +| PDU | Protocol Data Unit | +| PIC | Point in Call | +| PM | Personal Mobility | +| POC | Point of Control | +| POI | Point of Initiation | +| POR | Point of Return | +| POS | Point of Synchronization | +| POTS | Plain Old Telephone Service | +| PRI | Primary Rate Interface | +| PSTN | Public Switched Telephony Network | +| PTNX | Private Telecommunication Network Exchange | +| RCP | Resource Control Part | +| RDN | Relative Distinguished Name | +| REG | Registration | +| RFP | Resource Function Part | +| RLF | Radio Link Function | +| RPOA | Recognized Operating Agency | +| ROS | Remote Operations | +| ROSE | Remote Operations Service Element | +| SACF | Single Association Control Function | +| SAO | Single Association Object | +| SCCP | Signalling Connection Control Part | +| SCE | Service Creation Environment | +| SCEF | Service Creation Environment Function | +| SCEP | Service Creation Environment Point | + +| | | +|----------|-----------------------------------------------------------------| +| SCF | Service Control Function | +| SCF FSM | Service Control Function Finite State Machine | +| SCFID | Service Control Function Identifier | +| SCI | Send Charging Information | +| SCME | Service Control function Management Entity | +| SCME FSM | Service Control function Management Entity Finite State Machine | +| SCP | Service Control Point | +| SCSM | Service Control Function Call State Model | +| SDF | Service Data Function | +| SDF FSM | Service Data function Finite State Machine | +| SDL | Specification and Description Language | +| SDME | Service Data function Management Entity | +| SDP | Service Data Point | +| SDSM | Service Data function Call State Model | +| SF | Service Feature | +| SIB | Service Independent Building Block | +| SL | Service Logic | +| SLCP | Service Logic Control Program | +| SLMP | Service Logic Management Program | +| SLP | Service Logic Processing Program | +| SLPI | Service Logic Processing Program Instance | +| SM | Service Manager | +| SMAF | Service Management Access Function | +| SMAF | Service Management Agent Function | +| SMF | Service Management Function | +| SMP | Service Management Point | +| SMS | Service Management System | +| SN | Service Node | +| SRF | Specialized Resource Function | +| SRF FSM | Specialized Resource Function Finite State Machine | +| SRME | Specialized Resource Function Management Entity | +| SRSM | Specialized Resource Function Call State Model | +| SS | Service Subscriber | +| SS7 | Signalling System No. 7 | +| SSCP | Service Switching and Control Point | +| SSD | Service Support Data | + +| | | +|----------|-------------------------------------------------------------------| +| SSF | Service Switching Function | +| SSF FSM | Service Switching Function Finite State Machine | +| SSME | Service Switching Function Management Entity | +| SSME FSM | Service Switching Function Management Entity Finite State Machine | +| SSN | Sub-System Number | +| SSP | Service Switching Point | +| STI | Service Trigger Information | +| SU | Service User | +| TC | Transaction Capabilities | +| TCAP | Transaction Capabilities Application Part | +| TDP | Trigger Detection Point | +| TDP-N | Trigger Detection Point-Notification | +| TDP-R | Trigger Detection Point-Request | +| TMN | Telecommunications Management Network | +| TTS | Text To Speech | +| UPT | Universal Personal Telecommunication | +| VPN | Virtual Private Network | +| WCR | Wireless Call Related | +| WCU | Wireless Call Unrelated | + +# 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/Q/T-REC-Q.1742.6-200708-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1742.6-200708-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4c87deefd1ecee173b6f4af7c56982314d695639 --- /dev/null +++ b/marked/Q/T-REC-Q.1742.6-200708-I_PDF-E/raw.md @@ -0,0 +1,4276 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.1742.6** + +(08/2007) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for IMT-2000 + +--- + +**IMT-2000 references (approved as of +31 December 2006) to ANSI-41 evolved core +network with cdma2000 access network** + +ITU-T Recommendation Q.1742.6 + +# ITU-T Q-SERIES RECOMMENDATIONS + +# SWITCHING AND SIGNALLING + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **ITU-T Recommendation Q.1742.6** + +## **IMT-2000 references (approved as of 31 December 2006) to ANSI-41 evolved core network with cdma2000 access network** + +### **Summary** + +ITU-T Recommendation Q.1742.6 associates the published core network standards from the regional standards development organizations (SDOs) with those 3GPP2 specifications that were approved as of 31 December 2006 for the IMT-2000 family member "ANSI-41 evolved core network with cdma2000 access network". + +3GPP2 specifications that were approved as of 17 July 2001 were associated with the published core network standards from the regional standards development organizations in ITU-T Recommendation Q.1742.1. 3GPP2 specifications that were approved as of 11 July 2002 were associated with the published core network standards from the regional standards development organizations in ITU-T Recommendation Q.1742.2. 3GPP2 specifications that were approved as of 30 June 2003 were associated with the published core network standards from the regional standards development organizations in ITU-T Recommendation Q.1742.3. 3GPP2 specifications that were approved as of 30 June 2004 were associated with the published core network standards from the regional standards development organizations in ITU-T Recommendation Q.1742.4. 3GPP2 specifications that were approved as of 31 December 2005 were associated with the published core network standards from the regional standards development organizations in ITU-T Recommendation Q.1742.5. + +3GPP2 specifications that are approved as of 31 December 2007 will be associated with published core network standards in future ITU-T Recommendation Q.1742.7. The radio interface and radio access network and standards from the SDOs for this IMT-2000 family member are associated in ITU-R Recommendation M.1457-6. The associations for other IMT-2000 family members are identified in ITU-T Q.174x-series Recommendation. + +This Recommendation combines and associates the regional standards for the core network of this IMT-2000 family member into a global Recommendation. + +### **Source** + +ITU-T Recommendation Q.1742.6 was approved on 13 August 2007 by ITU-T Study Group 19 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +### **Keywords** + +ANSI-41, cdma2000, core network, IMT-2000, third generation 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. + +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 ..... | 2 | +| 4 | Abbreviations and acronyms ..... | 5 | +| 5 | Introduction ..... | 9 | +| 6 | Basic architecture for the ANSI-41 evolved core network with cdma2000 access network family member..... | 9 | +| 7 | Network entities..... | 16 | +| 7.1 | Authentication, authorization and accounting (AAA)..... | 16 | +| 7.2 | Authentication centre (AC) ..... | 16 | +| 7.3 | Call data collection point (CDCP)..... | 16 | +| 7.4 | Call data generation point (CDGP) ..... | 16 | +| 7.5 | Call data information source (CDIS)..... | 16 | +| 7.6 | Call data rating point (CDRP) ..... | 17 | +| 7.7 | Collection function (CF) – [Intercept]..... | 17 | +| 7.8 | Coordinate routing database (CRDB) ..... | 17 | +| 7.9 | Customer service centre (CSC) ..... | 17 | +| 7.10 | Delivery function (DF) – [Intercept] ..... | 17 | +| 7.11 | Equipment identity register (EIR) ..... | 17 | +| 7.12 | Home agent (HA) ..... | 18 | +| 7.13 | Home location register (HLR)..... | 18 | +| 7.14 | Intelligent peripheral (IP) ..... | 18 | +| 7.15 | Intercept access point (IAP) ..... | 18 | +| 7.16 | Interworking function (IWF)..... | 18 | +| 7.17 | Local position determining entity (LPDE) ..... | 18 | +| 7.18 | Managed wireless network entity (MWNE)..... | 18 | +| 7.19 | Message centre (MC) ..... | 18 | +| 7.20 | Mobile position centre (MPC)..... | 18 | +| 7.21 | Mobile switching centre (MSC) ..... | 19 | +| 7.22 | Number portability database (NPDB) ..... | 19 | +| 7.23 | Over-the-air service provisioning function (OTAF) ..... | 19 | +| 7.24 | Packet data network (PDN) ..... | 19 | +| 7.25 | Packet data serving node (PDSN) ..... | 19 | +| 7.26 | Position-determining entity (PDE)..... | 19 | +| 7.27 | Service control point (SCP)..... | 19 | +| 7.28 | Service node (SN)..... | 19 | +| 7.29 | Short message entity (SME)..... | 19 | +| 7.30 | Visitor location register (VLR) ..... | 19 | + +| | | Page | +|------|---------------------------------------------------------|------| +| 7.31 | Voice message centre (VMS)..... | 19 | +| 7.32 | Wireless network entity (WNE) ..... | 20 | +| 7.33 | Access gateway (AGW) ..... | 20 | +| 7.34 | Application server (AS)..... | 20 | +| 7.35 | Authentication, authorization and accounting (AAA)..... | 20 | +| 7.36 | Border router (BR) ..... | 20 | +| 7.37 | Breakout gateway control function (BGCF) ..... | 20 | +| 7.38 | Call session control function (CSCF)..... | 20 | +| 7.39 | Databases (DB)..... | 21 | +| 7.40 | IP multimedia client ..... | 21 | +| 7.41 | IP network ..... | 21 | +| 7.42 | Media gateway (MGW)..... | 21 | +| 7.43 | Media gateway control function (MGCF) ..... | 21 | +| 7.44 | Media resource function controller (MRFC)..... | 21 | +| 7.45 | Media resource function processor (MRFP) ..... | 21 | +| 7.46 | Mobile IP home agent (HA) ..... | 21 | +| 7.47 | Mobile station (MS) ..... | 22 | +| 7.48 | OSA service capability server (OSA-SCS) ..... | 22 | +| 7.49 | Policy decision function (PDF) ..... | 22 | +| 7.50 | Position determining entity (PDE) ..... | 22 | +| 7.51 | Position server ..... | 22 | +| 7.52 | Public switched telephone network (PSTN)..... | 22 | +| 8 | Reference points ..... | 22 | +| 8.1 | Reference point B ..... | 22 | +| 8.2 | Reference point C ..... | 22 | +| 8.3 | Reference point D ..... | 22 | +| 8.4 | Reference point d..... | 22 | +| 8.5 | Reference point D 1 ..... | 23 | +| 8.6 | Reference point D i ..... | 23 | +| 8.7 | Reference point E ..... | 23 | +| 8.8 | Reference point E 3 ..... | 23 | +| 8.9 | Reference point E 5 ..... | 23 | +| 8.10 | Reference point E 9 ..... | 23 | +| 8.11 | Reference point E 11 ..... | 23 | +| 8.12 | Reference point E 12 ..... | 23 | +| 8.13 | Reference point e..... | 23 | +| 8.14 | Reference point F ..... | 23 | +| 8.15 | Reference point G..... | 23 | +| 8.16 | Reference point H..... | 23 | +| 8.17 | Reference point I ..... | 23 | + +| | Page | +|----------------------------------|------| +| 8.18 Reference point J ..... | 23 | +| 8.19 Reference point K..... | 24 | +| 8.20 Reference point L ..... | 24 | +| 8.21 Reference point $M_1$ ..... | 24 | +| 8.22 Reference point $M_2$ ..... | 24 | +| 8.23 Reference point $M_3$ ..... | 24 | +| 8.24 Reference point N..... | 24 | +| 8.25 Reference point $N_1$ ..... | 24 | +| 8.26 Reference point $O_1$ ..... | 24 | +| 8.27 Reference point $O_2$ ..... | 24 | +| 8.28 Reference point $P_i$ ..... | 24 | +| 8.29 Reference point Q..... | 24 | +| 8.30 Reference point $Q_1$ ..... | 24 | +| 8.31 Reference point $T_1$ ..... | 24 | +| 8.32 Reference point $T_2$ ..... | 24 | +| 8.33 Reference point $T_3$ ..... | 25 | +| 8.34 Reference point $T_4$ ..... | 25 | +| 8.35 Reference point $T_5$ ..... | 25 | +| 8.36 Reference point $T_6$ ..... | 25 | +| 8.37 Reference point $T_7$ ..... | 25 | +| 8.38 Reference point $T_8$ ..... | 25 | +| 8.39 Reference point $T_9$ ..... | 25 | +| 8.40 Reference point V ..... | 25 | +| 8.41 Reference point X..... | 25 | +| 8.42 Reference point Y ..... | 25 | +| 8.43 Reference point Z ..... | 25 | +| 8.44 Reference point $Z_1$ ..... | 25 | +| 8.45 Reference point $Z_2$ ..... | 25 | +| 8.46 Reference point $Z_3$ ..... | 25 | +| 8.47 Reference point 1 ..... | 26 | +| 8.48 Reference point 2..... | 26 | +| 8.49 Reference point 3..... | 26 | +| 8.50 Reference point 4..... | 26 | +| 8.51 Reference point 5/Mk ..... | 26 | +| 8.52 Reference point 6..... | 26 | +| 8.53 Reference point 7..... | 26 | +| 8.54 Reference point 8/OSA..... | 26 | +| 8.55 Reference point 9/Mi ..... | 26 | +| 8.56 Reference point 10..... | 26 | +| 8.57 Reference point 11/Sh ..... | 26 | + +| | | Page | +|------|------------------------------|-------------| +| 8.58 | Reference point 12/ISC ..... | 27 | +| 8.59 | Reference point 13..... | 27 | +| 8.60 | Reference point 14..... | 27 | +| 8.61 | Reference point 15..... | 27 | +| 8.62 | Reference point 16/Cx..... | 27 | +| 8.63 | Reference point 17/Mg..... | 27 | +| 8.64 | Reference point 18..... | 27 | +| 8.65 | Reference point 19..... | 27 | +| 8.66 | Reference point 20..... | 27 | +| 8.67 | Reference point 21..... | 27 | +| 8.68 | Reference point 22..... | 27 | +| 8.69 | Reference point 23..... | 27 | +| 8.70 | Reference point 24/Mr..... | 28 | +| 8.71 | Reference point 25/Mp..... | 28 | +| 8.72 | Reference point 26/PSTN..... | 28 | +| 8.73 | Reference point 27..... | 28 | +| 8.74 | Reference point 28/Go..... | 28 | +| 8.75 | Reference point 29..... | 28 | +| 8.76 | Reference point 30/Mc ..... | 28 | +| 8.77 | Reference point 31..... | 28 | +| 8.78 | Reference point 32/Mb ..... | 28 | +| 8.79 | Reference point 33/Mb ..... | 28 | +| 8.80 | Reference point 34/Mb ..... | 28 | +| 8.81 | Reference point 35..... | 28 | +| 8.82 | Reference point 36/Mb ..... | 29 | +| 8.83 | Reference point 37/Mb ..... | 29 | +| 8.84 | Reference point 38/Mb ..... | 29 | +| 8.85 | Reference point 39..... | 29 | +| 8.86 | Reference point 40/Mb ..... | 29 | +| 8.87 | Reference point 41..... | 29 | +| 8.88 | Reference point 42/Mb ..... | 29 | +| 8.89 | Reference point 43/Mb ..... | 29 | +| 8.90 | Reference point 44/Mb ..... | 29 | +| 8.91 | Reference point 45/Mb ..... | 29 | +| 8.92 | Reference point 46/Mb ..... | 29 | +| 8.93 | Reference point 47..... | 29 | +| 8.94 | Reference point 48..... | 30 | +| 8.95 | Reference point 49/Mj ..... | 30 | +| 8.96 | Reference point 50..... | 30 | + +| | Page | +|------|-----------------------------------------------------| +| 9 | Technical specifications structure..... 30 | +| 10 | Technical specifications..... 31 | +| 10.1 | A series RAN specifications..... 31 | +| 10.2 | Intersystem specifications ..... 31 | +| 10.3 | Packet data specifications..... 41 | +| 10.4 | Services and system aspects specifications ..... 42 | +| 10.5 | Core network specifications ..... 84 | + + + +# **IMT-2000 references (approved as of 31 December 2006) to ANSI-41 evolved core network with cdma2000 access network** + +## **1 Scope** + +This Recommendation identifies the IMT-2000 family member: "ANSI-41 evolved core network with cdma2000 access network". This set of referenced specifications includes those 3GPP2 specifications that were approved as of 31 December 2006. + +The core network interfaces identified in this Recommendation and the radio interfaces and radio access network interfaces identified in [ITU-R M.1457-6] constitute a complete system specification for the third generation mobile system for terrestrial usage of this IMT-2000 family member. + +It is the intent of ITU-T that the references in this Recommendation are only to specifications that specify the network aspects of this IMT-2000 family member. In the event that a referenced specification also includes material that specifies any of the radio aspects of this IMT-2000 family member, [ITU-R M.1457-6] shall take precedence. + +## **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 M.1457-6] ITU-R Recommendation M.1457-6 (2006), *Detailed specifications of the radio interfaces of international mobile telecommunications-2000 (IMT-2000)*. +- [ANSI/TIA/EIA 41-D] ANSI/TIA/EIA 41-D (1997), *Cellular Radio Telecommunications Intersystem Operations (ANSI/TIA/EIA-41-D-97)*. +- [ANSI/TIA/EIA 95-B] ANSI/TIA/EIA 95-B (1999), *Mobile Station-Base Station Compatibility Standard for Wideband Spread Spectrum Cellular Systems (ANSI/TIA/EIA-95-B-99)*. +- [ANSI/TIA/EIA 124-D] ANSI/TIA/EIA 124-D (2001), *Wireless Radio Telecommunications Intersystem Non-Signaling Data Communication DMH (Data Message Handler) (ANSI/124-D-2001)*. +- [ANSI/TIA/EIA 136] ANSI/TIA/EIA 136 (2001), *TDMA Cellular PCS (ANSI/TIA/EIA-136, Rev C-2001)*. +- [ANSI/TIA/EIA 553-A] ANSI/TIA/EIA 553-A (1999), *Mobile Station – Base Station Compatibility Standard (ANSI/TIA/EIA-553-A-99)*. +- [ANSI/TIA/EIA 664-A] ANSI/TIA/EIA 664-A (2000), *Wireless Features Description (ANSI/TIA/EIA-664-A-2000)*. + +| | | +|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [CWTS-MC-N.S0037] | CWTS-MC-N.S0037 (2002), IP Network Architecture Model for cdma2000 Spread Spectrum Systems. | +| [CWTS-MC-S.R0005-B] | CWTS-MC-S.R0005-B (2002), Network Reference Model for cdma2000 Spread Spectrum Systems. | +| [TIA/EIA/IS-91-A] | TIA/EIA/IS-91-A (1999), Base Station – Mobile Station Compatibility Specification for 800 MHz Cellular, Auxiliary, and Residential Services (TIA/EIA/IS-91-A). | +| [TIA/EIA/IS-826-A] | TIA/EIA/IS-826-A (2003), TIA/EIA-41-D Based Pre-Paid Charging Enhancements for Circuit-Switched Data and Short Message services. | +| [TIA/EIA/IS-2000-A] | TIA/EIA/IS-2000-A (2000), CDMA 2000 Series (TIA/EIA/IS-2000 Series Revision A). | +| [TIA/EIA/IS-2001-A] | TIA/EIA/IS-2001-A (2001), Interoperability Specifications (IOS) for CDMA2000 Access Network Interfaces (TIA/EIA/IS-2001-A). | +| [TIA/EIA TSB-29-E] | TIA/EIA/TSB-29-E (2002), International Implementation of Wireless Telecommunication Systems Compliant with TIA/EIA-41. | +| [TIA TSB-100-A] | TIA TSB-100-A (2001), Wireless Network Reference Model. | +| [TTC TS-3GB-S.R0005-Bv1.0] | TTC TS-3GB-S.R0005-Bv1.0 (2001), Network Reference Model for cdma2000 Spread Spectrum Systems. | +| [TTC TS-3GB-S.R0037-0v3.0] | TTC TS-3GB-S.R0037-0v3.0 (2003), IP Network Architecture Model for cdma2000 Spread Spectrum Systems. | +| [TTA TTAE.3G-S.R0005-B] | TTA TTAE.3G-S.R0005-B (2001), 3GPP2 Network Reference Model for cdma2000 Spread Spectrum Systems. | +| [TTA TTAT.3G-S.R0037-0v3.0] | TTA TTAT.3G-S.R0037-0v3.0 (2003), IP Network Architecture Model for cdma2000 Spread Spectrum Systems. | + +## 3 Definitions + +This Recommendation defines the following terms: + +**3.1 access denial call treatment:** A tone, announcement, or call redirection applied as appropriate. + +**3.2 access network:** Network that connects access technologies (such as a radio access network) to the core network. + +**3.3 active:** The MS is available for call delivery. This state is maintained by the MSC, the VLR and the HLR (see also available, inactive and unavailable). + +**3.4 adjunct MSC:** A mobile switching centre (MSC) that is providing adjunct services such as voice response, voice recognition, DTMF tone detection, voice message storage, etc. + +**3.5 anchor MSC:** The mobile switching centre (MSC), that is the first to assign a traffic channel to a call on origination or termination is called the anchor MSC. For the duration of this call, this MSC shall be the anchor (fixed) point in the event that the mobile station (MS) should be handed off to other MSCs. + +**3.6 authentication:** The act of verifying the identity of an entity (e.g., a user, device). + +- 3.7 available:** The MS can accept a call delivery (i.e., the MS is in a known location and it is in a state able to accept call deliveries). The availability of an MS to accept a call delivery is maintained only by the MSC (see also active, inactive and unavailable). +- 3.8 base transceiver station:** A piece of radio access network equipment that contains the radios and serves a geographic area. +- 3.9 call delivery:** The process by which calls directed to the cellular subscriber are delivered to the subscriber while roaming in a visited system. +- 3.10 call delivery method:** Method by which a call is delivered to a subscriber in MSC-V. +- 3.11 call disconnect:** The process of requesting the release of a connection between two or more network addresses. +- 3.12 call release:** The process of relinquishing the facilities and circuits used for a call. +- 3.13 call termination:** The process of connecting a subscriber to an incoming call. +- 3.14 candidate MSC:** This term is used during the handoff measurement request by the current serving MSC to reference the MSC that is being requested to provide its best CELL ID and SIGNAL QUALITY values. +- 3.15 cell site:** The physical location of a cell's radio equipment and supporting systems. This term is also used to refer to the equipment located at the cell site. +- 3.16 clearinghouse:** A service used for the exchange and management of information. +- 3.17 data communications:** The digital transmission of information (other than voice). +- 3.18 dialogue:** A user interaction sequence composed of tones and announcements that may gather information. +- 3.19 gateway MSC:** See MSC-G. +- 3.20 home system:** The system which is transmitting the system identifier (SID) (refer to [ANSI/TIA/EIA 553-A] which is recognized by the MS as the "home" SID). +- 3.21 inactive:** The MS is not available for call delivery. The MS may not be registered. The MS may be registered, but is out of radio contact (e.g., missing autonomous registrations) or is intentionally inaccessible for periods of time (e.g., slotted mode, paging frame class, or sleep mode). An inactive MS may accept SMS message deliveries. This state is maintained by the MSC, the VLR and the HLR (see also active, available and unavailable). +- 3.22 market identification (MarketID):** A unique market identifier that is specified by the service provider (e.g., FCC assigned SID, CIBERNET assigned BID – see [TIA/EIA TSB-29]). +- 3.23 mobile assisted handoff (MAHO):** A process where handoff measurements are done by the MS under the control of the MSC and base station. The MSC and base station retain the control over when the handoff actually occurs. +- 3.24 mobility:** The ability to access services from any point in the network. The degree of service availability may depend on the access network capabilities, as well as any service level agreements between the user's home network and the visited network. Types of mobility include personal mobility, service mobility, and terminal mobility. +- 3.25 mobility management:** The set of functions used to manage a mobile user accessing a network other than that user's home network. These functions include communication with the home network for purposes of authentication, authorization, location updating and download of user information. +- 3.26 MSC-G:** An MSC that is capable of the intersystem procedures, defined in this Recommendation, between entities in the network reference model so as to provide service. + +- 3.27 MSC-H:** The "home" MSC of an MS which is broadcasting the SID that is recorded in the MS's security and identification memory, and to which the MS's directory number is assigned. +- 3.28 MSC-V:** A "visited" MSC in whose service area a roamer is operating. +- 3.29 network reference model:** The functional entities and the associated interface reference points that may logically comprise a cellular network (see clause 6). +- 3.30 number portability:** A mechanism that allows a user to retain the same directory number, regardless of the subscribed-to service provider. Number portability may be limited to specific geographical areas. In the context of the all-IP network, the term "number portability" refers specifically to E.164 numbers used for telephony. +- 3.31 originating MSC:** The MSC-H or MSC-G that initiates the call delivery procedures defined in this Recommendation. +- 3.32 originating SMS supplementary service:** Services or features that affect SMS message originations and are requested on a per message basis as supported by a particular teleservice, for example, delayed delivery, or message distribution to a list of destinations. +- 3.33 personal mobility:** The ability of users to change their association with one or more terminals at any point and time. The user should continue to receive subscribed and otherwise authorized services as supported by the current MS and access network. +- 3.34 personalized services:** Services that need access to the subscriber profile and/or are dependent on the overall call/session state (of the user) for reasons of service interaction. An example: a call termination service such as "call forward on busy" in [ANSI/TIA/EIA 41-D]. +- 3.35 protocol extension:** A mechanism provided to allow systems with a common bilateral agreement to extend the TIA/EIA-41 protocol. There is a range of reserved error codes, operation codes, parameter identifiers (in addition to PRIVATE parameter identifiers), and ranges of values in enumerated parameter types and data fields. The only mechanism to resolve conflicting uses of protocol extension is to standardize their usage. The protocol extension mechanism is used at the risk of the implementation. Protocol extensions should not be used unless the message recipient is known to support them. +- 3.36 radio access network:** The network that connects radio base stations to the core network. The RAN provides and maintains radio-specific functions, which may be unique to a given radio access technology, that allow users to access the core network. +- 3.37 registered:** The HLR has a pointer to a system serving an MS. A registered MS may be active or inactive. +- 3.38 registration:** The procedure by which an MS becomes listed as being present in the service area of an MSC. +- 3.39 remote feature control port (RFC port):** A terminating directory number supporting service profile modification. +- 3.40 roamer port:** A terminating directory number supporting call delivery to mobile stations. +- 3.41 roamer service profile:** The specific set of features, capabilities and/or operating restrictions, other than financial accountability, associated with the subscriber. +- 3.42 roamer validation:** That aspect of roamer service qualification dealing with financial accountability. Also, the general procedure by which a roamer's financial accountability is established. +- 3.43 roaming:** Action whereby users access services while outside of their subscribed home network. + +- 3.44 service qualification:** The service capabilities, features and privileges to which an MS is entitled. Also, the general procedure by which such service capabilities, features and privileges become established in an MSC. +- 3.45 serving MSC:** The MSC which currently has the MS obtaining service at one of its cell sites within its coverage area. +- 3.46 signalling:** The information exchanged between the mobile station and the network, or within the network, for the purposes of service provision (e.g., connection establishment). +- 3.47 switch number (SWNO):** A number uniquely identifying a particular switch (i.e., a group of cell sites and the associated switch resources) within a group of switches associated with a common MarketID. +- 3.48 target MSC:** The MSC which was selected from the candidate list as having the cell site with the best signal quality value for the MS during the location request function. +- 3.49 temporary local directory number (TLDN):** A network address temporarily assigned for call setup. +- 3.50 terminating SMS supplementary service:** Services or features that affect SMS message terminations, for example, screening, forwarding, delivery to an MS, delayed delivery while roaming, or distribution to a group based upon a destination address. +- 3.51 termination address:** One or more digits, as determined by the home system, which identify the terminating party. This could include speed call codes (when supported by the home service provider), other mobile telephone numbers or any valid world telephone number. +- 3.52 traffic:** The information generated by the subscriber that is transported on the network (i.e., user voice or data). +- 3.53 unavailable:** The MS cannot accept a normal call delivery (i.e., the MS is in an unknown location or it is in a state unable to accept call deliveries). The availability of an MS to accept a call delivery is maintained only by the MSC (see also active, available and inactive). +- 3.54 unregistered:** A state where the MS is unavailable for any type of termination event and the HLR pointer is not directed to any visited system. +- 3.55 visited network:** The visited network is a carrier's network where a subscriber is currently roaming. The term visited network is more business significant than geographically significant. +- 3.56 visited system:** From the MS's perspective, a system which is transmitting a SID which is not recognized by the MS as the "home" SID. From a network perspective, the system in which an MS is currently registered. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|---------------------------------------------| +| 3G | Third Generation | +| 3GPP2 | Third Generation Partnership Project (2) | +| AC | Authentication Centre | +| ADDS | Application Data Delivery Service | +| ADPCM | Adaptive Differential Pulse Code Modulation | +| ADS | Asynchronous Data Service | +| AH | Answer Hold | +| AMPS | Advanced Mobile Phone System | + +| | | +|-------|------------------------------------------------| +| AoC | Advice of Charge | +| API | Application Programming Interface | +| ARIB | Association of Radio Industries and Businesses | +| AS | Application Server | +| BCMCS | Broadcast-Multicast Services | +| BCSM | Basic Call State Model | +| BS | Base Station | +| BSC | Base Station Controller | +| BTS | Basic Transceiver System | +| CCF | Call Control Function | +| CDCP | Call Data Collection Point | +| CDGP | Call Data Generation Point | +| CDIS | Call Data Information Source | +| CDMA | Code Division Multiple Access | +| CDRP | Call Data Rating Point | +| CN | Core Network | +| CNAP | Calling Name Presentation | +| CNAR | Calling Name Restriction | +| CNIP | Calling Number Identification Presentation | +| CSC | Customer Service Centre | +| CSCF | Call Session Control Function | +| CWTS | China Wireless Telecommunication Standard | +| DCCH | Dedicated Control Channel | +| DFP | Distributed Functional Plane | +| DMH | Data Message Handler | +| DP | Detection Point | +| DP | Data Privacy | +| DSA | Data Subscriber Authentication | +| DTMF | Dual Tone Multi-Frequency | +| E2E | End-to-End | +| EIR | Equipment Identity Register | +| EMS | Enhanced Message Service | +| ESN | Electronic Serial Number | +| ESP | Encapsulating Security Payload | +| FCC | Federal Communications Commission | +| FFMA | File Format for Multimedia Services | +| FPH | FreePhone | + +| | | +|----------|---------------------------------------------------------------------| +| FPLMTS | Future Public Land Mobile Telecommunications Systems – now IMT-2000 | +| GECO | Global Emergency Call Origination | +| GSM | Global System for Mobile Communications | +| HA | Home Agent | +| HLR | Home Location Register | +| HSS | Home Subscriber Server | +| IM | IP Multimedia | +| IMS | IP Multimedia Subsystem | +| IMSI | International Mobile Subscriber Identity | +| IMT-2000 | International Mobile Telecommunications – 2000 | +| IOTA | IP Over-the-Air | +| IOTA HCM | Internet Over-the-Air Handset Configuration Management | +| IP | Internet Protocol | +| IP | Intelligent Peripheral | +| IPE | In Path Equipment | +| IS | Interim Standard | +| ISDN | Integrated Services Digital Network | +| ISIM | IP Multimedia Services Identity Module | +| ISLP | InterSystem Link Protocol | +| IWF | InterWorking Function | +| LBSS | Location-Based Services System | +| LMSD | Legacy Mobile Station Domain | +| MAP | Mobile Application Part | +| MC | Multi-Carrier | +| MC | Message Centre | +| MDN | Mobile Directory Number | +| MEID | Mobile Equipment Identifier | +| MGW | Media Gateway | +| MM | Multimedia Message | +| MMS | Multimedia Messaging Service | +| MS | Mobile Station | +| MSC | Mobile Switching Centre | +| MSID | Mobile Station Identifier | +| NAM | Number Assignment Module | +| NAMPS | Narrow-band Advanced Mobile Phone Service | +| NDSS | Network Directed System Selection | +| NRM | Network Reference Model | + +| | | +|--------|----------------------------------------------------------| +| OAM&P | Operations, Administration, Maintenance and Provisioning | +| OSA | Open Service Access | +| OTAF | Over the-Air Function | +| OTAPA | Over-the-Air Parameter Administration | +| OTASP | Over-the-Air Service Provisioning | +| P-CSCF | Proxy Call Session Control Function | +| PCF | Packet Control Function | +| PCS | Personal Communications System | +| PDE | Positioning-Determining Entity | +| PDS | Packet Data Subsystem | +| PDSN | Packet Data Serving Node | +| PL | Preferred Language | +| PN | Project Number | +| PPC | Pre-Paid Charging | +| PPP | Point-to-Point Protocol | +| PRC | Premium Rate Charging | +| RAN | Radio Access Network | +| RUAC | Rejection of Undesired Annoying Calls | +| R-UI | Removable User Identity Module | +| SC | Subscriber Confidentially | +| SCF | Selective Call Forwarding | +| SCF | Session Control Function | +| SCP | Service Control Point | +| SCS | Service Capability Server | +| SDO | Standards Development Organization | +| SDP | Session Description Protocol | +| SID | System Identifier | +| SIP | Session Initiation Protocol | +| SME | Short Message Entity | +| SMS | Service Management System | +| SMS | Short Message Service | +| SMTP | Simple Mail Transfer Protocol | +| SN | Service Node | +| SRG | System Release Guide | +| SS7 | Signalling System 7 | +| SSF | Service Switching Function | +| SSG | Special Study Group | + +| | | +|------|---------------------------------------------------| +| TFO | Tandem Free Operation | +| TrFO | Transcoder Free Operation | +| TMSI | Temporary Mobile Station Identification | +| TR | Transmit-Receive (as in TR45) | +| TRAU | Transcoder and Rate Adaptor Unit | +| TSB | Telecommunications Systems Bulletin | +| TTA | Telecommunications Technology Association (Korea) | +| TTC | Telecommunication Technology Committee (Japan) | +| UICC | Universal Integrated Circuit Card | +| UIM | User Identity Module | +| USCF | User Selective Call Forwarding | +| VASP | Value-Added Service Provider | +| VLR | Visitor Location Register | +| WIN | Wireless Intelligent Network | +| WLL | Wireless Local Loop | +| WNP | Wireless Number Portability | + +## 5 Introduction + +The core network for cdma2000 is based on an evolved ANSI-41 second generation mobile system. The core network technical specifications have been developed in a third generation partnership project (approved in 3GPP2 as of 31 December 2006) and transposed to the involved regional standards development organizations (SDOs). The system will support different applications ranging from narrow-band to wideband communications capability with integrated personal and terminal mobility to meet the user and service requirements. + +The core network interfaces identified in this Recommendation and the radio interfaces and radio access network interfaces identified in [ITU-R M.1457-6] constitute a complete system specification for the third generation mobile system for terrestrial usage of this IMT-2000 family member. + +The descriptions in clauses 6, 7 and 8, and the descriptions of the technical specifications listed in clause 10 are for informative purposes only. Normative information is in the tables for the respective specification. + +## 6 Basic architecture for the ANSI-41 evolved core network with cdma2000 access network family member + +The basic architecture for the ANSI-41 evolved core network with cdma2000 access network family member includes a circuit-based and packet-based core network and an all-IP multimedia domain. + +The following text is based on clause 2.1 of [CWTS-MC-S.R0005-B], [TIA TSB-100-A], [TTA TTAE.3G-S.R0005-B], [TTC TS-3GB-S.R0005-Bv1.0]. + +Figure 6-1 presents the network entities and associated reference points that comprise the ANSI-41 evolved core network with cdma2000 access network. The network entities are represented by squares, triangles and rounded corner rectangles; circles represent the reference points. The network + +reference model in this Recommendation is the compilation of several reference models currently in use. + +- The network reference model is a functional block diagram. +- A network entity represents a group of functions, not a physical device. For example, a mobile switching centre (MSC) is a physical device; it comprises frames, shelves, circuit packs, etc. The physical device may comprise a single network entity such as the MSC, or it may comprise some combination such as the MSC, the visitor location register (VLR), the home location register (HLR), and the authentication centre (AC). The physical realization is an implementation issue; a manufacturer may choose any physical implementation of network entities, either individually or in combination, as long as the implementation meets the functional requirements. Sometimes, for practical reasons, the functional network entity is a physical device. The mobile station (MS) is an excellent example. +- A reference point is a conceptual point that divides two groups of functions. It is not necessarily a physical interface. A reference point only becomes a physical interface when the network entities on either side of it are contained in different physical devices. +- A "collective entity" contains encompassed network entities that are an instance of the collective. +- A "composite entity" contains encompassed network entities that are part of the composite. +- The portion of the figure within the solid line is the core network. + +![Figure 6-1 – ANSI-41 evolved core network with cdma2000 access network reference model. The diagram shows a complex network architecture with various entities and interfaces. On the left, a Mobile Station (MS) contains a Mobile Equipment (ME) with MT0, MT1, and MT2, and a UIM. The ME connects to the network via interfaces TE1, TE2, and Rm. The UIM connects to a Vehicle via interface Uv. The network itself is divided into several functional blocks. A dashed box labeled 'CDIS' contains the Base Station (BS) with BTS and BSC, and the Base Station Controller (BSC). The BS connects to the Mobile Switching Center (MSC) via interface Um. The MSC is connected to various other entities: IP, SCP, SN, NPDB, LPDE, VMS, EIR, PSTN, PDN, ISDN, CSC, TA, IWF, PDSN, AAA, HA, MPC, PDE, ESME, CRDB, MWNE, OSF, CDGP, CDCP, DF, CF, and CDRP. Interfaces are labeled with letters (A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z) and subscripts (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12). A 'Key' at the bottom left defines the symbols: Specific Network Entity (triangle with rectangle), Composite Entity (rounded rectangle), Collective Entity (dashed rectangle), Interface Reference Point (circle with H), Interface to another instance of same network entity (circle with X), and Line intersection (cross).](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +Figure 6-1 – ANSI-41 evolved core network with cdma2000 access network reference model. The diagram shows a complex network architecture with various entities and interfaces. On the left, a Mobile Station (MS) contains a Mobile Equipment (ME) with MT0, MT1, and MT2, and a UIM. The ME connects to the network via interfaces TE1, TE2, and Rm. The UIM connects to a Vehicle via interface Uv. The network itself is divided into several functional blocks. A dashed box labeled 'CDIS' contains the Base Station (BS) with BTS and BSC, and the Base Station Controller (BSC). The BS connects to the Mobile Switching Center (MSC) via interface Um. The MSC is connected to various other entities: IP, SCP, SN, NPDB, LPDE, VMS, EIR, PSTN, PDN, ISDN, CSC, TA, IWF, PDSN, AAA, HA, MPC, PDE, ESME, CRDB, MWNE, OSF, CDGP, CDCP, DF, CF, and CDRP. Interfaces are labeled with letters (A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z) and subscripts (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12). A 'Key' at the bottom left defines the symbols: Specific Network Entity (triangle with rectangle), Composite Entity (rounded rectangle), Collective Entity (dashed rectangle), Interface Reference Point (circle with H), Interface to another instance of same network entity (circle with X), and Line intersection (cross). + +Q.1742.6(07)\_F01 + +**Figure 6-1 – ANSI-41 evolved core network with cdma2000 access network reference model** + +The basic architecture for the ANSI-41 evolved core network with cdma2000 access network family member also includes an all-IP multimedia domain. The following text is based on clause 2.1 of [CWTS-MC-N.S0037], [TTA TTAT.3G-S.R0037-0v3.0], [TTC TS-3GB-S.R0037-0v3.0]. + +All-IP MMD core network architecture: + +Figure 6-2 presents the core network entities and associated reference points that comprise the multimedia domain (MMD) of the wireless all-IP network architecture model. The network entities are represented by squares and rectangles; the interfaces between network entities are reference points identified by numbers. Figure 6-2 includes several reference points that have dual labels. Either of these labels may be used in the specifications relating to these reference points. + +NOTE 1 – In Figure 6-2, the network elements and reference points shaded in blue identify the "IP MMD core network". + +![Diagram of ANSI-41 evolved core network with cdma2000 access network IP MMD core network architecture model. The diagram shows various network entities connected by reference points. Entities include Databases (EIR, DSI, Subscription profile, Network policy rules), OSA Application server, SIP application server, OSA service capability server, Breakout gateway control function, Position server, AAA, Call session control function, Policy decision function, Position determining entity, Media resource function controller, Media gateway control function, cdma2000 access network (BTS, BSC/RNC+PCF, MM), Other access networks, Mobile station, Access gateway, FA/attendant, Media resource function processor, Mobile IP home agent, Media gateway, Border router, PSTN, and IP network. Reference points are labeled with numbers and letters (e.g., 11/Sh, 12/ISC, 16/Cx, 24/Mr, 32/Mb, 40/MbI).](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg) + +The diagram illustrates the architecture of an ANSI-41 evolved core network with a cdma2000 access network. It shows the following components and interfaces: + +- Databases:** EIR, DSI, Subscription profile, Network policy rules, and others. They connect to the AAA via reference points 1, 2, 3, and 4. +- OSA Application server** and **SIP application server:** Both connect to the OSA service capability server via reference point 8/OSA. +- OSA service capability server:** Connects to the Call session control function via reference point 10. +- Breakout gateway control function:** Connects to the SIP application server via reference point 12/ISC and to the Policy decision function via reference point 49/Mj. +- Position server:** Connects to the AAA via reference point 15 and to the Position determining entity via reference point 18. +- AAA:** Connects to the Position server (15), Call session control function (16/Cx), and Access gateway (21). +- Call session control function:** Connects to the AAA (16/Cx), OSA service capability server (10), Policy decision function (23), and Media resource function controller (24/Mr). +- Policy decision function:** Connects to the Call session control function (23), Breakout gateway control function (49/Mj), and Media gateway control function (28/Go). +- Position determining entity:** Connects to the Position server (18). +- Media resource function controller:** Connects to the Call session control function (24/Mr) and the Media resource function processor (25/Mp). +- Media gateway control function:** Connects to the Policy decision function (28/Go) and the Media gateway (26/PSTN). +- cdma2000 access network:** Contains BTS, BSC/RNC + PCF, and MM. It connects to the Access gateway via reference point 31. +- Other access networks:** Connect to the FA/attendant via reference point 47. +- Mobile station:** Connects to the FA/attendant via reference point hh. +- Access gateway:** Connects to the AAA (21), FA/attendant (32/Mb), and Mobile IP home agent (33/Mb). +- FA/attendant:** Connects to the Access gateway (32/Mb), Mobile IP home agent (36/Mb), and Mobile station (hh). +- Media resource function processor:** Connects to the Media resource function controller (25/Mp) and the Mobile IP home agent (37/Mb). +- Mobile IP home agent:** Connects to the Access gateway (33/Mb), FA/attendant (36/Mb), Media resource function processor (37/Mb), and Media gateway (42/Mb). +- Media gateway:** Connects to the Media gateway control function (26/PSTN) and the Mobile IP home agent (42/Mb). +- Border router:** Connects to the Mobile IP home agent (44/Mb), PSTN (34/Mb), and IP network (46/Mb). +- PSTN:** Connects to the Media gateway (26/PSTN) and the Border router (34/Mb). +- IP network:** Connects to the Border router (46/Mb). + +Diagram of ANSI-41 evolved core network with cdma2000 access network IP MMD core network architecture model. The diagram shows various network entities connected by reference points. Entities include Databases (EIR, DSI, Subscription profile, Network policy rules), OSA Application server, SIP application server, OSA service capability server, Breakout gateway control function, Position server, AAA, Call session control function, Policy decision function, Position determining entity, Media resource function controller, Media gateway control function, cdma2000 access network (BTS, BSC/RNC+PCF, MM), Other access networks, Mobile station, Access gateway, FA/attendant, Media resource function processor, Mobile IP home agent, Media gateway, Border router, PSTN, and IP network. Reference points are labeled with numbers and letters (e.g., 11/Sh, 12/ISC, 16/Cx, 24/Mr, 32/Mb, 40/MbI). + +Figure 6-2 – ANSI-41 evolved core network with cdma2000 access network IP MMD core network architecture model + +The MMD of the all-IP network offers both general packet data support and multimedia session capabilities. The multimedia session capabilities are built on top of the general packet data support capabilities. The general packet data capabilities may be deployed without the multimedia session capabilities. Some network entities are common to providing both capabilities. + +Figure 6-3 shows the entities that comprise the general packet data support portion of the MMD core network. These are known collectively as the packet data subsystem (PDS). Figure 6-3 includes several reference points that have dual labels. Either of these labels may be used in the specifications relating to these reference points. + +NOTE 2 – In Figure 6-3, the network elements and reference points highlighted in blue identify the "packet data subsystem". + +![Figure 6-3: ANSI-41 evolved core network with cdma2000 access network packet data subsystem core network architecture model. The diagram shows various network elements and their interconnections. On the left, a 'Databases' box contains EIR, DSI, Subscription profile, Network Policy Rules, and others. Above it are OSA and SIP Application servers. Below the databases are Position server, Position determining entity, and cdma2000 access network (BTS, BSC/RNC + PCF, MM). A central 'AAA' box is connected to many other elements. To its right are OSA service capability server, Call session control function, Policy decision function, Media resource function controller, Media resource function processor, Media gateway control function, and Media gateway. Below these are FA/attendant, Mobile IP home agent, and Border router. At the bottom are Mobile station, PSTN, and IP network. Reference points are labeled with numbers and letters (e.g., 1, 2, 3, 4, 5/Mk, 8/OSA, 11/Sh, 12/ISC, 15, 16/Cx, 17/Mg, 18, 19, 20, 21, 22, 23, 24/Mr, 25/Mp, 26/PSTN, 28/Go, 29/I, 30/Mc, 31, 32/Mb, 33/Mb, 34/Mb, 35, 36/Mb, 37/Mb, 38/Mb, 40/Mb, 41, 42/Mb, 43/Mb, 44/Mb, 45/Mb, 46/Mb, 47, hh). Some elements and lines are highlighted in blue.](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +Figure 6-3: ANSI-41 evolved core network with cdma2000 access network packet data subsystem core network architecture model. The diagram shows various network elements and their interconnections. On the left, a 'Databases' box contains EIR, DSI, Subscription profile, Network Policy Rules, and others. Above it are OSA and SIP Application servers. Below the databases are Position server, Position determining entity, and cdma2000 access network (BTS, BSC/RNC + PCF, MM). A central 'AAA' box is connected to many other elements. To its right are OSA service capability server, Call session control function, Policy decision function, Media resource function controller, Media resource function processor, Media gateway control function, and Media gateway. Below these are FA/attendant, Mobile IP home agent, and Border router. At the bottom are Mobile station, PSTN, and IP network. Reference points are labeled with numbers and letters (e.g., 1, 2, 3, 4, 5/Mk, 8/OSA, 11/Sh, 12/ISC, 15, 16/Cx, 17/Mg, 18, 19, 20, 21, 22, 23, 24/Mr, 25/Mp, 26/PSTN, 28/Go, 29/I, 30/Mc, 31, 32/Mb, 33/Mb, 34/Mb, 35, 36/Mb, 37/Mb, 38/Mb, 40/Mb, 41, 42/Mb, 43/Mb, 44/Mb, 45/Mb, 46/Mb, 47, hh). Some elements and lines are highlighted in blue. + +**Figure 6-3 – ANSI-41 evolved core network with cdma2000 access network packet data subsystem core network architecture model** + +Figure 6-4 shows the entities that comprise the multimedia session capabilities of an all-IP network. These entities are known collectively as the IP multimedia session subsystem (IMS). Figure 6-4 includes several reference points that have dual labels. Either of these labels may be used in the specifications relating to these reference points. + +NOTE 3 – In Figure 6-4 the "IP multimedia session subsystem" is identified by the network elements and reference points highlighted in blue. + +![Figure 6-4: ANSI-41 evolved core network with cdma2000 access network IP multimedia session subsystem core network architecture model. The diagram shows various network elements and their interconnections with numbered reference points. Elements include Databases (EIR, DSI, Subscription profile, Network Policy Rules, ...), OSA Application server, SIP application server, OSA service capability server, Breakout gateway control function, Position server, AAA, Call session control function, Policy decision function, Position determining entity, Media resource function controller, Media gateway control function, cdma2000 access network (BTS, BSC/RNC + PCF, MM), Access gateway, Media resource function processor, Media gateway, FA/attendant, Mobile IP home agent, Border router, Mobile station, PSTN, and IP network. Reference points are labeled with numbers and letters such as 1, 2, 3, 4, 5/Mk, 7, 8/OSA, 9/Mi, 10, 11/Sh, 12/ISC, 15, 16/Cx, 17/Mg, 18, 19, 20, 21, 22, 23, 24/Mr, 25/Mp, 26/PSTN1, 28/Go, 29, 30/Mc, 31, 32/Mb, 33/Mb, 34/Mb, 35, 36/Mb, 37/Mb, 38/Mb, 40/Mb, 41, 42/Mb, 43/Mb, 44/Mb, 45/Mb, 46/Mb, 47, and hh.](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +Figure 6-4: ANSI-41 evolved core network with cdma2000 access network IP multimedia session subsystem core network architecture model. The diagram shows various network elements and their interconnections with numbered reference points. Elements include Databases (EIR, DSI, Subscription profile, Network Policy Rules, ...), OSA Application server, SIP application server, OSA service capability server, Breakout gateway control function, Position server, AAA, Call session control function, Policy decision function, Position determining entity, Media resource function controller, Media gateway control function, cdma2000 access network (BTS, BSC/RNC + PCF, MM), Access gateway, Media resource function processor, Media gateway, FA/attendant, Mobile IP home agent, Border router, Mobile station, PSTN, and IP network. Reference points are labeled with numbers and letters such as 1, 2, 3, 4, 5/Mk, 7, 8/OSA, 9/Mi, 10, 11/Sh, 12/ISC, 15, 16/Cx, 17/Mg, 18, 19, 20, 21, 22, 23, 24/Mr, 25/Mp, 26/PSTN1, 28/Go, 29, 30/Mc, 31, 32/Mb, 33/Mb, 34/Mb, 35, 36/Mb, 37/Mb, 38/Mb, 40/Mb, 41, 42/Mb, 43/Mb, 44/Mb, 45/Mb, 46/Mb, 47, and hh. + +**Figure 6-4 – ANSI-41 evolved core network with cdma2000 access network IP multimedia session subsystem core network architecture model** + +The session control functions within the IMS are logically interconnected in various ways in the session scenarios. Figure 6-5 identifies the reference points within the IMS between these session control entities. In many cases there are dual labels for these reference points, either of which may be used in the applicable specifications. + +![Figure 6-5 – Session control reference model diagram showing the interaction between various network entities. At the top, an IP multimedia client (dashed box) connects to a (Proxy) Call session control function (dashed box) via an hh/Gm interface. The (Proxy) Call session control function connects to an (Interrogating) Call session control function via a dd/Mw interface. The (Interrogating) Call session control function connects to a (Serving) Call session control function via an ff/Mw interface. Below the (Proxy) Call session control function is a Media gateway control function, connected via a 17/Mg interface. The (Interrogating) Call session control function connects to a Breakout gateway control function via a 9/Mi interface. The (Serving) Call session control function connects to another Breakout gateway control function via a 9/Mi interface. The Media gateway control function connects to the first Breakout gateway control function via a 49/Mj interface. The two Breakout gateway control functions are connected to each other via a 5/Mk interface. A dashed line also connects the (Interrogating) Call session control function to the Media gateway control function. A label 'Q.1742.6(07)_F05' is in the bottom right corner.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +Figure 6-5 – Session control reference model diagram showing the interaction between various network entities. At the top, an IP multimedia client (dashed box) connects to a (Proxy) Call session control function (dashed box) via an hh/Gm interface. The (Proxy) Call session control function connects to an (Interrogating) Call session control function via a dd/Mw interface. The (Interrogating) Call session control function connects to a (Serving) Call session control function via an ff/Mw interface. Below the (Proxy) Call session control function is a Media gateway control function, connected via a 17/Mg interface. The (Interrogating) Call session control function connects to a Breakout gateway control function via a 9/Mi interface. The (Serving) Call session control function connects to another Breakout gateway control function via a 9/Mi interface. The Media gateway control function connects to the first Breakout gateway control function via a 49/Mj interface. The two Breakout gateway control functions are connected to each other via a 5/Mk interface. A dashed line also connects the (Interrogating) Call session control function to the Media gateway control function. A label 'Q.1742.6(07)\_F05' is in the bottom right corner. + +**Figure 6-5 – Session control reference model** + +# 7 Network entities + +Clauses 7.1 to 7.32 are based on reference clause 2.1.1 of [CWTS-MC-S.R0005-B], [TIA TSB-100-A], [TTA TTAE.3G-S.R0005-B], [TTC TS-3GB-S.R0005-Bv1.0] and clauses 7.33 to 7.52 are based on clause 2.1 of [CWTS-MC-N.S0037], [TTA TTAT.3G-S.R0037-0v3.0], [TTC TS-3GB-S.R0037-0v3.0]. + +### 7.1 Authentication, authorization and accounting (AAA) + +The AAA is an entity that provides IP-based authentication, authorization and accounting. The AAA maintains security associations with peer AAA entities to support intra- and/or inter-administrative domain AAA functions. + +- The authentication function provides authentication of users. +- The authorization function of AAA provides authorization of service requests based on subscriber profiles and network policy. It also generates keys required for establishing security associations between PDSNs in access provider networks and HAs in home IP networks. +- The accounting function gathers accounting data concerning the services used by individual subscribers. + +### 7.2 Authentication centre (AC) + +The AC is an entity that manages the authentication information related to the MS. The AC may or may not be located within, and be indistinguishable from, an HLR. An AC may serve more than one HLR. + +### 7.3 Call data collection point (CDCP) + +The CDCP is the entity that collects the call detail information. + +### 7.4 Call data generation point (CDGP) + +The CDGP is an entity which provides call detail information to the CDCP (in ANSI-124 format). This may be the entity that converts call detail information from a proprietary format into a standard format. All information from the CDGP to the CDCP must be in this standard format. + +### 7.5 Call data information source (CDIS) + +The CDIS is an entity that can be the source of call detail information. This information may be in proprietary format. It is not required to be in the standard format. + +### **7.6 Call data rating point (CDRP)** + +The CDRP is the entity that takes the unrated call detail information and applies the applicable charge- and tax-related information. The charge and tax information is added using the standard format. + +### **7.7 Collection function (CF) – [Intercept]** + +The CF is an entity that is responsible for collecting intercepted communications for a lawfully authorized law enforcement agency. + +The CFs typically include: + +- The ability to receive and process call content information for each intercept subject. +- The ability to receive and process information regarding each intercept subject (e.g., call associated or non-call associated) from the delivery function. + +### **7.8 Coordinate routing database (CRDB)** + +The CRDB is an entity that stores information to translate a given position, expressed as a latitude and longitude, to a string of digits. + +### **7.9 Customer service centre (CSC)** + +The CSC is an entity where service provider representatives receive telephone calls from customers wishing to subscribe to initial wireless service or request a change in the customer's existing service. The CSC interfaces proprietarily with the OTAF to perform network- and MS-related changes necessary to complete the service provisioning request. + +### **7.10 Delivery function (DF) – [Intercept]** + +The DF is an entity that is responsible for delivering intercepted communications to one or more collection functions. + +The DFs typically include: + +- The ability to accept call contents for each intercept subject over one or more channels from each access function. +- The ability to deliver call contents for each intercept subject over one or more channels to a collection function as authorized for each law enforcement agency. +- The ability to accept information over one or more data channels and combine that information into a single data flow for each intercept subject. +- The ability to filter or select information on an intercept subject before delivery to a collection function as authorized for a particular law enforcement agency. +- The optional ability to detect audio in-band DTMF digits for translation and delivery to a collection function as authorized for a particular law enforcement agency. +- The ability to duplicate and deliver information on the intercept subject to one or more collection functions as authorized for each law enforcement agency. +- The ability to provide security to restrict access. + +### **7.11 Equipment identity register (EIR)** + +The EIR is an entity that is the register to which user equipment identity may be assigned for record purposes. The nature, purpose and utilization of this information is an area for further study. + +### **7.12 Home agent (HA)** + +The HA is an entity that: + +- authenticates mobile IP registrations from the MS; +- redirects packets to the foreign agent component of the PDSN, and optionally receives and routes reverse packets from the foreign agent component of the PDSN; +- may establish, maintain and terminate secure communications to the PDSN; +- receives provisioning information from the AAA function for users; +- may assign a dynamic home IP address. + +### **7.13 Home location register (HLR)** + +The HLR is the location register to which a user identity is assigned for record purposes such as subscriber information (e.g., electronic serial number (ESN), mobile directory number (MDN), profile information, current location, authorization period). + +### **7.14 Intelligent peripheral (IP)** + +The IP is an entity that performs specialized resource functions such as playing announcements, collecting digits, performing speech-to-text or text-to-speech conversion, recording and storing voice messages, facsimile services, data services, etc. + +### **7.15 Intercept access point (IAP)** + +The IAP is an entity that provides access to the communications to or from the equipment, facilities or services of an intercept subject. + +### **7.16 Interworking function (IWF)** + +The IWF is an entity that provides information conversion for one or more WNEs. An IWF may have an interface to a single WNE providing conversion services. An IWF may augment an identified interface between two WNEs, providing conversion services to both WNEs. + +### **7.17 Local position determining entity (LPDE)** + +The LPDE facilitates the determination of the position or geographical location of a wireless terminal. Each LPDE supports one or more position-determining technologies. Multiple LPDEs using the same technology may serve the coverage area of a mobile position centre (MPC) and the multiple LPDEs each using a different technology may serve the same coverage area of an MPC. Local PDEs (LPDEs) reside at the base station (BS). + +### **7.18 Managed wireless network entity (MWNE)** + +A MWNE (within the collective entity) or any specific network entity having operation system wireless management needs, including another operations system. + +### **7.19 Message centre (MC)** + +The MC is an entity that stores and forwards short messages. The MC may also provide supplementary services for short message service (SMS). + +### **7.20 Mobile position centre (MPC)** + +The MPC selects a PDE to determine the position of a mobile station. The MPC may restrict access to position information (e.g., require that the MS be engaged in an emergency call or only release position information to authorized network entities). + +### **7.21 Mobile switching centre (MSC)** + +The MSC switches circuit mode MS-originated or MS-terminated traffic. An MSC is usually connected to at least one BS. It may connect to the other public networks (PSTN, ISDN, etc.), other MSCs in the same network, or MSCs in different networks. The MSC may store information to support these capabilities. + +### **7.22 Number portability database (NPDB)** + +The NPDB is an entity which provides portability information for portable directory numbers. + +### **7.23 Over-the-air service provisioning function (OTAF)** + +The OTAF is an entity that interfaces proprietarily to CSCs to support service provisioning activities. The OTAF interfaces with the MSC to send MS orders necessary to complete service provisioning requests. + +### **7.24 Packet data network (PDN)** + +A PDN, such as the Internet, provides a packet data transport mechanism between processing network entities capable of using such services. + +### **7.25 Packet data serving node (PDSN)** + +The PDSN routes MS-originated or MS-terminated packet data traffic. The PDSN establishes, maintains and terminates link layer sessions to MSs. The PDSN may interface to one or more MS(s) and may interface to one or more PDN(s). + +### **7.26 Position-determining entity (PDE)** + +A PDE facilitates determination of the position or geographical location of a wireless terminal. Each PDE supports one or more position-determining technologies. Multiple PDEs using the same technology may serve the coverage area of a mobile position centre (MPC) and multiple PDEs, each using a different technology, may serve the same coverage area of an MPC. + +### **7.27 Service control point (SCP)** + +The SCP is an entity that acts as a real-time database and transaction processing system that provides service control and service data functionality. + +### **7.28 Service node (SN)** + +The SN is an entity that provides service control, service data, specialized resources and call control functions to support bearer-related services. + +### **7.29 Short message entity (SME)** + +The SME is an entity that composes and decomposes short messages. A SME may or may not be located within, and be indistinguishable from, an HLR, MC, VLR, MS or MSC. + +### **7.30 Visitor location register (VLR)** + +The VLR is the location register other than the HLR used by an MSC to retrieve information for handling of calls to or from a visiting subscriber. The VLR may or may not be located within, and be indistinguishable from, an MSC. The VLR may serve more than one MSC. + +### **7.31 Voice message centre (VMS)** + +A VMS stores received voice messages, data messages (e.g., email) or both message types, and supports a method to retrieve previously stored messages. A VMS may also support (on a directory + +number basis) notification of the presence of stored messages and notification of a change in the number of voice messages, data messages or both message types that are waiting retrieval. + +### **7.32 Wireless network entity (WNE)** + +A network entity in the wireless collective entity. + +### **7.33 Access gateway (AGW)** + +The cdma2000 AGW consists of the PDSN and other logical functions required to interface the core network to the cdma2000 RAN. + +- The PDSN routes MS-originated or MS-terminated packet data traffic. The PDSN establishes, maintains and terminates link layer sessions to MSs. The PDSN may interface to one or more MSs and may interface to one or more PDNs. + +### **7.34 Application server (AS)** + +Application servers provide value-added network-based services for wireless subscribers. These services may be accessed via the OSA service capability server (OSA-SCS) or accessed directly from the user's mobile station via other network entities, by-passing the OSA-SCS. + +### **7.35 Authentication, authorization and accounting (AAA)** + +The AAA is an entity that provides IP-based authentication, authorization and accounting. The AAA maintains security associations with peer AAA entities to support intra- and/or inter-administrative domain AAA functions. + +- The authentication function is an entity that provides authentication of terminal devices and subscribers. +- The authorization function of AAA provides authorization of requests for services and/or bandwidth, etc., and has access to the policy repository, directory services, subscriber profiles and the device register. +- The accounting function gathers data concerning the services, QoS and multimedia resources requested and used by individual subscribers. + +### **7.36 Border router (BR)** + +The BR connects the core network with peer networks (e.g., other service providers, corporate networks, Internet). The BR performs IP packet routing, exterior gateway routing protocols, and policing of incoming and outgoing traffic, ensuring traffic complies with defined service level agreements established with peer networks. The BR may intercept any QoS allocation request and issue a request to the policy decision function (PDF), which shall verify that the requested inbound and/or outbound QoS is available. A successful response from the PDF may cause the BR to forward the bandwidth allocation request to its final destination. + +### **7.37 Breakout gateway control function (BGCF)** + +The BGCF selects the network in which PSTN breakout is to occur and, within the network where the breakout is to occur, selects the MGCF. + +### **7.38 Call session control function (CSCF)** + +The CSCF establishes, monitors, supports and releases multimedia sessions, and manages the user's service interactions. + +### **7.39 Databases (DB)** + +The information in the core network DBs may include but is not limited to EIR, dynamic subscriber information, network policy rules and subscriber profile data. + +### **7.40 IP multimedia client** + +The IP multimedia client communicates with application servers, P-CSCFs and other IP multimedia clients. The IP multimedia client is an application that resides in the MS. + +### **7.41 IP network** + +The IP network corresponds to IP-based packet data networks that provide a transport mechanism between the core network and external IP networks. IP network represents packet networks connected to the core network including the public Internet, private IP backbone networks and private IP networks such as corporate intranets. + +### **7.42 Media gateway (MGW)** + +The MGW provides an interface between the packet environment of the core network and the circuit switched environment of the PSTN for bearer traffic, when equipped with circuit capabilities. The MGW may provide vocoding and/or transcoding functions to the bearer traffic. The MGW may also provide modem functions to convert digital byte streams to and from audio modem tones placed on circuits, and may provide the capability to terminate point-to-point protocol (PPP) connections. It also provides policy enforcement relative to its activities and resources. + +### **7.43 Media gateway control function (MGCF)** + +The MGCF provides the ability to control a media gateway through standardized interfaces. Such control includes allocation and deallocation of resources of the media gateway, as well as modification of the usage of those resources. + +### **7.44 Media resource function controller (MRFC)** + +The MRFC, in conjunction with the MRFP, provides a set of resources within the core network that are useful in supporting services to subscribers. The MRFC, in conjunction with the MRFP, provides multi-way conference bridges, announcement playback services, tone playback services, etc. + +### **7.45 Media resource function processor (MRFP)** + +The MRFP, in conjunction with the controlling entity, provides multi-way conference bridges, announcement playback services, tone playback services, etc. + +### **7.46 Mobile IP home agent (HA)** + +The HA provides two major functions: registering the current point of attachment of the user, and forwarding of IP packets to and from the current point of attachment (IPv4 care of address [CoA] and/or IPv6 co-located CoA) of the user. The HA accepts registration requests using the mobile IP protocol and uses the information in those requests to update internal information about the current point of attachment of the user, i.e., the current IP address to be used to transmit and receive IP packets to and from that user. The HA interacts with the AAA to receive mobile IP registration requests that have been authenticated, and to return mobile IP registration responses. The HA also interacts with the access gateway to receive subsequent mobile IP registration requests. The HA may interact with several network entities in performing its work of forwarding IP packets to the current point of attachment of the user. + +### **7.47 Mobile station (MS)** + +The MS is a wireless terminal used by subscribers to access the legacy MS domain or the IP multimedia domain services over a radio interface. MSs include portable units (e.g., hand-held units), units installed in vehicles, and somewhat paradoxically, fixed location MSs. The MS is the interface equipment used to terminate the radio path at the subscriber. An MS is an ME with a programmed UIM. + +### **7.48 OSA service capability server (OSA-SCS)** + +The OSA-SCS provides access to network resources needed during service application execution. The interface towards the application server uses application programming interfaces such as open service architecture (OSA). The interfaces towards other network entities use the relevant protocols. + +### **7.49 Policy decision function (PDF)** + +The PDF provides management of core network QoS resources within its own core network necessary to support services to network users. It communicates with the access gateway to provide authorization of resource allocations. The PDF makes policy decisions with regard to use of core network QoS resources within its own network, including consideration of service level agreements (SLAs). QoS policy information for network resource utilization may be forwarded to and cached by the PDF. + +NOTE – The maintenance of SLAs is for further study. + +### **7.50 Position determining entity (PDE)** + +The PDE communicates with the position server to determine the precise geographic position of the MS based on input data provided by the position server. + +### **7.51 Position server** + +The position server provides geographic position information to requesting entities. + +### **7.52 Public switched telephone network (PSTN)** + +The PSTN is defined in accordance with the appropriate applicable national and regional standards. + +## **8 Reference points** + +Clauses 8.1 to 8.46 are based on clause 2.1.2 of [CWTS-MC-S.R0005-B], [TIA TSB-100-A], [TTA TTAE.3G-S.R0005-B], [TTC TS-3GB-S.R0005-Bv1.0], and clauses 8.47 to 8.96 are based on clause 2.1 of [CWTS-MC-N.S0037], [TTA TTAT.3G-S.R0037-0v3.0], [TTC TS-3GB-S.R0037-0v3.0]. + +### **8.1 Reference point B** + +Reference point B is the interface between the MSC and the VLR. + +### **8.2 Reference point C** + +Reference point C is the interface between the MSC and the HLR. + +### **8.3 Reference point D** + +Reference point D is the interface between the VLR and HLR. + +### **8.4 Reference point d** + +Reference point d is the interface between an IAP and the DF. + +### **8.5 Reference point D1** + +Reference point D1 is the interface between the OTAF and the VLR. + +### **8.6 Reference point Di** + +Reference point Di is the interface between: + +- the IP and the ISDN; +- the IWF and the ISDN; +- the MSC and the ISDN (ESBE); +- the SN and the ISDN. + +### **8.7 Reference point E** + +Reference point E is the interface between the MSC and MSC. + +### **8.8 Reference point E3** + +Reference point E3 is the interface between the MPC and the MSC. + +### **8.9 Reference point E5** + +Reference point E5 is the interface between the MPC and the PDE. + +### **8.10 Reference point E9** + +Reference point E9 is the interface between the MPC and the SCP. + +### **8.11 Reference point E11** + +Reference point E11 is the interface between the CRDB and the MPC. + +### **8.12 Reference point E12** + +Reference point E12 is the interface between the MSC and the PDE. + +### **8.13 Reference point e** + +Reference point e is the interface between the CF and the DF. + +### **8.14 Reference point F** + +Reference point F is the interface between the MSC and the EIR. + +### **8.15 Reference point G** + +Reference point G is the interface between the VLR and the VLR. + +### **8.16 Reference point H** + +Reference point H is the interface between the HLR and the AC. + +### **8.17 Reference point I** + +Reference point I is the interface between the CDIS and the CDGP. + +### **8.18 Reference point J** + +Reference point J is the interface between the CDGP and the CDCP. + +### **8.19 Reference point K** + +Reference point K is the interface between the CDGP and the CDRP. + +### **8.20 Reference point L** + +Reserved. + +### **8.21 Reference point M1** + +Reference point M1 is the interface between the SME and the MC. + +### **8.22 Reference point M2** + +Reference point M2 is the MC to MC interface. + +### **8.23 Reference point M3** + +Reference point M3 is the SME to SME interface. + +### **8.24 Reference point N** + +Reference point N is the interface between the HLR and the MC. + +### **8.25 Reference point N1** + +Reference point N1 is the interface between the HLR and the OTAF. + +### **8.26 Reference point O1** + +Reference point O1 is the interface between an MWNE and the OSF. + +### **8.27 Reference point O2** + +Reference point O2 is the interface between an OSF and the OSF. + +### **8.28 Reference point Pi** + +Reference point Pi is the interface between: + +- the AAA and the AAA; +- the AAA and the PDN; +- the IWF and the PDN; +- the MSC and the PDN; plus +- the PDSN and the PDN. + +### **8.29 Reference point Q** + +Reference point Q is the interface between the MC and the MSC. + +### **8.30 Reference point Q1** + +Reference point Q1 is the interface between the MSC and the OTAF. + +### **8.31 Reference point T1** + +Reference point T1 is the interface between the MSC and the SCP. + +### **8.32 Reference point T2** + +Reference point T2 is the interface between the HLR and the SCP. + +### **8.33 Reference point T3** + +Reference point T3 is the interface between the IP and the SCP. + +### **8.34 Reference point T4** + +Reference point T4 is the interface between the HLR and the SN. + +### **8.35 Reference point T5** + +Reference point T5 is the interface between the IP and the MSC. + +### **8.36 Reference point T6** + +Reference point T6 is the interface between the MSC and the SN. + +### **8.37 Reference point T7** + +Reference point T7 is the interface between the SCP and the SN. + +### **8.38 Reference point T8** + +Reference point T8 is the interface between the SCP and the SCP. + +### **8.39 Reference point T9** + +Reference point T9 is the interface between the HLR and the IP. + +### **8.40 Reference point V** + +Reference point V is the interface between the OTAF and the OTAF. + +### **8.41 Reference point X** + +Reference point X is the interface between the CSC and the OTAF. + +### **8.42 Reference point Y** + +Reference point Y is the interface between a wireless network entity (WNE) and the IWF. + +### **8.43 Reference point Z** + +Reference point Z is the interface between the MSC and the NPDB. + +### **8.44 Reference point Z1** + +Reference point Z1 is the interface between the MSC and the VMS. + +### **8.45 Reference point Z2** + +Reference point Z2 is the interface between the HLR and the VMS. + +### **8.46 Reference point Z3** + +Reference point Z3 is the interface between the MC and the VMS. + +An interface exists when two network entities are interconnected through exactly one signalling or bearer stream reference point. The reference points and their associated network entities are as follows. + +### **8.47 Reference point 1** + +Reference point 1 is the signalling interface between the databases and the position server (multimedia domain only). + +### **8.48 Reference point 2** + +Reference point 2 is the signalling interface between the databases and the cdma2000 access network. + +### **8.49 Reference point 3** + +Reference point 3 is the signalling interface between the databases and the policy decision function (multimedia domain only). + +### **8.50 Reference point 4** + +Reference point 4 is the signalling interface between the databases and the AAA. + +### **8.51 Reference point 5/Mk** + +Reference point 5/Mk is the signalling interface between breakout gateway control functions (multimedia domain only). + +### **8.52 Reference point 6** + +Reference point 6 is the signalling interface between the databases and the legacy MS domain support (legacy MS domain only). + +### **8.53 Reference point 7** + +Reference point 7 is the signalling interface between the OSA service capability server and the databases. + +### **8.54 Reference point 8/OSA** + +Reference point 8/OSA is the signalling interface between the OSA application server and the OSA service capability server. Reference point 8/OSA may employ interfacing techniques that support a wide spectrum of capabilities, ranging from secure (e.g., application programming interfaces such as Parlay, used for un-trusted parties) to non-secure (e.g., used for trusted parties). + +### **8.55 Reference point 9/Mi** + +Reference point 9/Mi is the signalling interface between the visited network's BGCF and the home service network's serving-CSCF. + +### **8.56 Reference point 10** + +Reference point 10 is the signalling interface between the position server and the OSA service capability server (multimedia domain only). + +### **8.57 Reference point 11/Sh** + +Reference point 11/Sh is the signalling interface between the SIP application server and the AAA and between the OSA service capability server and the AAA for user's service authentication and/or authorization, and for retrieving information from the MMD database (multimedia domain only). + +### **8.58 Reference point 12/ISC** + +Reference point 12/ISC is the signalling interface between the SIP application server and call session control function and between the OSA service capability server and the call session control function for service control (multimedia domain only). + +### **8.59 Reference point 13** + +Reference point 13 is the signalling interface between the legacy MS domain support and the PSTN (legacy MS domain only). + +### **8.60 Reference point 14** + +Reference point 14 is the signalling interface between the legacy MS domain support and the MAP [ANSI/TIA/EIA-4-D] and GSM (legacy MS domain only). + +### **8.61 Reference point 15** + +Reference point 15 is the signalling interface between the position server and AAA. + +### **8.62 Reference point 16/Cx** + +Reference point 16/Cx is the signalling interface between the AAA and the call session control function (multimedia domain only). + +### **8.63 Reference point 17/Mg** + +Reference point 17/Mg is the signalling interface between the call session control function and the media gateway control function (multimedia domain only). + +### **8.64 Reference point 18** + +Reference point 18 is the signalling interface between the position server and the position determining entity. + +### **8.65 Reference point 19** + +Reference point 19 is the signalling interface between the position server and the access gateway (multimedia domain only). + +### **8.66 Reference point 20** + +Reference point 20 is the signalling interface between the AAA and the cdma2000 access network (multimedia domain only). + +### **8.67 Reference point 21** + +Reference point 21 is the signalling interface between the AAA and access gateway. + +### **8.68 Reference point 22** + +Reference point 22 is the signalling interface between the AAA and the mobile IP home agent. + +### **8.69 Reference point 23** + +Reference point 23 is the signalling interface between the AAA and the policy decision function (multimedia domain only). + +### **8.70 Reference point 24/Mr** + +Reference point 24/Mr is the signalling interface between the call session control function and the media resource function controller (multimedia domain only). + +### **8.71 Reference point 25/Mp** + +Reference point 25/Mp is the signalling interface between the media resource function controller and the media resource function processor. + +### **8.72 Reference point 26/PSTN** + +Reference point 26/PSTN is the signalling interface between the media gateway control function and the PSTN (multimedia domain only). + +### **8.73 Reference point 27** + +Reference point 27 is the bearer stream interface between the cdma2000 access network and the media gateway (legacy MS domain only). + +### **8.74 Reference point 28/Go** + +Reference point 28/Go is the signalling interface between the policy decision function and access gateway. + +### **8.75 Reference point 29** + +Reference point 29 is the signalling interface between policy decision function and the border router. + +### **8.76 Reference point 30/Mc** + +Reference point 30/Mc is the signalling interface between the media gateway control function and the media gateway (multimedia domain only). + +### **8.77 Reference point 31** + +Reference point 31 is the bearer stream interface between cdma2000 access network and the access gateway. + +### **8.78 Reference point 32/Mb** + +Reference point 32/Mb is the bearer stream interface between the access gateway and the media resource function processor (multimedia domain only). + +### **8.79 Reference point 33/Mb** + +Reference point 33/Mb is the bearer stream interface between the media resource function processor and the media gateway. + +### **8.80 Reference point 34/Mb** + +Reference point 34/Mb is the bearer stream interface between the media gateway and the PSTN. + +### **8.81 Reference point 35** + +Reference point 35 is the signalling interface between the cdma2000 access network and the access gateway. + +### **8.82 Reference point 36/Mb** + +Reference point 36/Mb is the bearer stream interface between the access gateway and the media gateway (multimedia domain only). + +### **8.83 Reference point 37/Mb** + +Reference point 37/Mb is the bearer stream interface between the media resource function processor and the mobile IP home agent (multimedia domain only). + +### **8.84 Reference point 38/Mb** + +Reference point 38/Mb is the bearer stream interface between the media gateway and the mobile IP home agent (multimedia domain only). + +### **8.85 Reference point 39** + +Reference point 39 is the signalling interface between the media gateway and the legacy MS domain support (legacy MS domain only). + +### **8.86 Reference point 40/Mb** + +Reference point 40/Mb is the bearer stream interface between the media gateway and the border router. + +### **8.87 Reference point 41** + +Reference point 41 is the signalling interface between the access gateway and the mobile IP home agent. + +### **8.88 Reference point 42/Mb** + +Reference point 42/Mb is the bearer stream interface between the media resource function processor and the border router. + +### **8.89 Reference point 43/Mb** + +Reference point 43/Mb is the bearer stream interface between the access gateway and the mobile IP home agent. + +### **8.90 Reference point 44/Mb** + +Reference point 44/Mb is the bearer stream interface between the mobile IP home agent and the border router. + +### **8.91 Reference point 45/Mb** + +Reference point 45/Mb is the bearer stream interface between the access gateway and the border router. + +### **8.92 Reference point 46/Mb** + +Reference point 46/Mb is the bearer stream interface between the border router and the IP network. + +### **8.93 Reference point 47** + +Reference point 47 is the radio link (air interface) between the mobile station and the cdma2000 access network. + +### **8.94 Reference point 48** + +Reference point 48 is the signalling interface between the cdma2000 access network and the legacy MS domain support (legacy MS domain only). + +### **8.95 Reference point 49/Mj** + +Reference point 49/Mj is the signalling interface between the breakout gateway control function and the media gateway control function (multimedia domain only). + +### **8.96 Reference point 50** + +Reference point 50 is the signalling interface between the policy decision function and the P-CSCF (multimedia domain only). + +# **9 Technical specifications structure** + +This clause provides an overview of the specifications for this IMT-2000 family member based on ANSI-41 evolved core network with cdma2000 access network. Details for these specifications may be found in clause 10. + +The following text describes the numbering scheme for the specifications and reports for the 3GPP2 third generation mobile system. + +The 3GPP2 document numbering scheme is indicated as follows: + +A.Bcccc-w-x version y.z + +where: + +- 1) A denotes the TSG (A, C, N, P, S) which developed the specification where: + - TSG-A develops RAN (i.e., A-interface) specifications; + - TSG-C develops air interface specifications; + - TSG-N develops intersystem interface specifications; + - TSG-P develops packet data specifications; + - TSG-S develops service and system aspects specifications including stage 1 requirements descriptions and OAM&P specifications. +- 2) B denotes project, report, specification (P, R, S). +- 3) cccc denotes a four (4) digit number which identifies the specific specification. +- 4) w denotes revision: + - 0 is the first release (0th revision); + - A is the first revision; + - and so on. +- 5) x denotes whether this is the prime revision or an addendum: + - 0 is the prime revision, and is used when the document is first created; + - 1 is the first addendum; + - 2 is the second addendum; + - and so on. +- 6) y is the "point release" indicator – 0 is used when the document is first created; the number is incremented whenever approved for publishing by the plenary of a TSG (e.g., 1 is the first approval by the plenary for publishing). + +- 7) z is an internal edit level. The internal edit level z is always reset to 0 when the document is approved by the applicable plenary. It is incremented by the entity (e.g., working group) that is developing the document for each new edit release. + +NOTE 1 – If the designator w and the designator x are both equal to 0, then neither designator needs to be included. + +NOTE 2 – The document reference section does not need to include "version y.z" unless specifically needed to resolve a technical incompatibility that would exist. + +# 10 Technical specifications + +All dates in the tables of clause 10 are formatted day-month-year. If no day is shown for the document, then the format is -month-year1. + +### 10.1 A series RAN specifications + +The 3GPP2 A series RAN specifications are outside of the scope of this Recommendation. The radio access network to core network interface specifications for the cdma2000 (ANSI-41 evolved core network with cdma2000 access network) system family will be referenced in a new issue of [ITU-R M.1457-6]. + +### 10.2 Intersystem specifications + +#### 10.2.1 N.S0003-0 v.1.0 User Identity Module (April 2001) + +This standard defines the enhancements required for the support of mobile stations equipped with user identification modules (UIM). The UIM provides functionality to certain types of mobile stations to enable them to operate in the wireless network. + +This document defines requirements for the wireless network to support operation of UIM-equipped mobile stations. A UIM provides compatible mobile stations with the parameters required of mobile stations operating in the TIA/EIA-41 environment and specific additional functionality unique to UIM-equipped mobile stations. + +The UIM can be in one of two forms, as either integrated within the mobile or removable that can be inserted or removed from the mobile equipment. This document addresses removable UIM (R-UIM) only. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0003-0 | 6.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-808 | | Published | -- 12-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0003 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0003.zip | +| TTC | TS-3GB-N.S0003v1.0 | 1.0 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0003-v10.pdf | + +1 Note on nomenclature of TIA documents: before TIA was accredited, documents were created under EIA. After TIA was accredited as a standards development organization, documents were named beginning with TIA/EIA. TIA documents can now stand by themselves so, since 2000, documents are now titled TIA only. The IS was an interim standard valid for 3 years and that naming system is no longer used for new documents. + +#### 10.2.2 N.S0004-0 v 1.0 WIN Phase 2 (April 2001) + +- Triggers for preferred language. +- Advice of charge. +- Rejection of undesired annoying calls. +- Premium rate charging. +- Freephone. + +Premium rate charging (PRC), freephone (FPH) and advice of charge (AoC) are charging-related services that provide a set of advanced wireless charging capabilities. Rejection of undesired annoying calls (RUAC) is a screening service that blocks undesired annoying calls to the subscriber. Enhanced preferred language (EPL) uses wireless intelligent network (WIN) capabilities to provide announcements to the subscriber in the subscriber's preferred language. This specification presents a recommended plan for the implementation of WIN capabilities that support these features. The WIN capabilities are for use in the wireless radiotelephone service. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0004-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-848 | | Published | -- 12-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0004 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0004.zip | +| TTC | TS-3GB-N.S0004-0v1.0 | 1.0 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0004-0v10.pdf | + +#### 10.2.3 N.S0005-0 Version 1.0 Cellular Radiotelecommunications Intersystem Operations (no date) + +(O) The purpose of this document is to identify those cellular services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principle considerations which have governed and directed the particular approaches taken in the procedural recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | YDT 1031-1999 | 1.0 | Published | -12-1999 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA-41-D | | Published | -- 12-1997 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0005 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0005.zip | + +#### 10.2.4 N.S0006 Version 1.0.0 PCS Multi-band Based on IS-41-C Revision: 0 (28 January 2000) + +The 3GPP2 document was withdrawn. + +#### 10.2.5 N.S0008 Version 1.0 Circuit Mode Services (no date) + +This standard presents a recommended plan for the implementation of uniform features for use in the cellular radiotelephone service. Its intent is to describe services and features so that the manner in which a subscriber may place calls using such features and services may remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. + +##### Services: + +- Asynchronous data service (ADS). +- Data privacy (DP). +- Group 3 facsimile service (G3 Fax). +- Service negotiation (SN). +- Mobile termination functions. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0008 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-737 | | Published | -- 01-2002 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0008 V1.0 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N.S0008v1.0.pdf | +| TTC | JP-3GB-N.S0008 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0008.pdf | + +#### 10.2.6 N.S0009-0 Version 1.0 IMSI (no date) + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0009-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-751 | | Published | -- 01-2002 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0009 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0009.zip | +| TTC | JP-3GB-N.S0009 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0009.pdf | + +#### 10.2.7 N.S0010-0 Version 1.0 Advanced features in Wideband Spread Spectrum Systems (no date) + +For this revision of this standard, the advanced CDMA features include: network directed system selection (NDSS) and subscriber confidentiality (SC) supported by TMSI. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0010-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-735 | | Published | -- 01-2002 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0010 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N.S0010-0v1.0.pdf | +| TTC | JP-3GB-N.S0010-0 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0010.pdf | + +#### 10.2.8 N.S0011-0 Version 1.0 OTASP and OTAPA (no date) + +This document presents recommendations for supporting the over-the-air "service provisioning" (OTASP) and "parameter administration" (OTAPA) capability. + +Specifically, this document includes stage 1 recommendations for OTASP subscriber feature and OTAPA network feature descriptions. It also provides intersystem operation recommendations for supporting the OTASP and OTAPA capability for the CDMA and TDMA air interfaces, with + +stage 2 operations and scenarios, stage 3 operations and parameter definitions plus stage 3 procedures. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0011-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-725-A | | Published | -- 07-1999 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0011 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0011.zip | +| TTC | JP-3GB-N.S0011 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0011.pdf | + +#### 10.2.9 N.S0012-0 CNAP/CNAR Revision: 0 (28 January 2000) + +This document presents a recommended plan for the implementation of calling name presentation (CNAP) and calling name restriction (CNAR) for use in the wireless radiotelephone service. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0012-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-764 | | Published | -- 01-2002 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0012 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0012.zip | +| TTC | JP-3GB-N.S0012 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0012.pdf | + +#### 10.2.10 N.S0013-0 Version 1.0 WIN Phase 1 (no date) + +The wireless intelligent network (WIN) is a network which supports the use of intelligent network capabilities to provide seamless terminal services, personal mobility services and advanced network services in mobile environment. + +This document presents a recommended plan for the implementation of the wireless intelligent network (WIN) for use in the wireless radiotelephone service. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0013-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-771 | | Published | -- 07-1999 | http://www.tiaonline.org/standards/catalog/search.cfm | +| | TIA/EIA/IS-771-1 | | Published | -- 08-2001 | | +| TTA | TTAE.3G-N.S0013 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0013.zip | +| TTC | JP-3GB-N.S0013 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0013.pdf | + +#### 10.2.11 N.S0014-0 Version 1.0 Authentication Enhancements (no date) + +This standard presents a recommended plan for the implementation of authentication enhancements for use in the wireless radiotelephone service. Its intent is to describe the authentication enhancements so that the manner in which a system implements them may remain reasonably consistent from system to system. + +The authentication enhancements include: + +- Count update after handoff. +- Obtaining subscriber profile before authentication on initial system access. +- Handling of suspicious call originations. +- Identifying the serving MSC when reporting the outcome of a requested authentication operation. +- Handling of authentication capable mobile stations when the home system is not authentication capable. +- Clarification and editorial correction of authentication procedures. +- Miscellaneous authentication enhancements. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0014-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-778 | | Published | -- 03-1999 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0014 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0014.zip | +| TTC | JP-3GB-N.S0014 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0014.pdf | + +#### 10.2.12 N.S0015 Version 1.0.0 ANSI-41-D Miscellaneous Enhancements (28 January 2000) + +This document is intended to justify TIA/EIA-41-D technical enhancement or technical correction contributions that have been supported for incorporation into PN-3590 (TIA/EIA-41-E) but are not expected to be published in a TIA/EIA-41-D enhancement interim standard (IS). + +This document is for tracking purposes only, there is no intention of publishing the contents of this document independently of ANSI/TIA/EIA-41-E. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0015 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-N.S0015 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N.S0015v1.0.0.pdf | + +#### 10.2.13 N.S0016-0 Version 1.0 TIA/EIA-41-D Internationalization (no date) + +This document specifies the ANSI/TIA/EIA-41-D chapter 1, 3, 5 and 6 enhancements that are necessary to support international intersystem operations. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------------------|---------|------------------------|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0016-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-807
TIA/EIA/IS-807-1 | | Published
Published | -- 08-1999
-- 03-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0016 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0016.zip | +| TTC | JP-3GB-N.S0016 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0016.pdf | + +#### 10.2.14 N.S0017-B Version 1.0.0 International Implementation of Wireless Telecommunication Systems Compliant with TIA/EIA-41 Revision: B (December 2002) + +When the first edition of Mobile Station – Land Station Compatibility Specification (IS-3, now TIA/EIA 553-A) was issued, it was envisioned that it would be adopted for use within northern America. Provisions were included for international implementation; however, detailed guidelines to assist with such implementations were not included. Subcommittee TR-45.2 recognized the need to provide such guidance, and charted a working group (Working Group VI) with this responsibility. The result of this working group's deliberations has been the production of TSB-29 as well as ongoing internationalization of other TIA standards, such as TIA/EIA-41-D (N.S0005), TIA-751 (N.S0009), TIA/EIA/IS-807 (N.S0016), TIA/EIA/IS-875 (N.S0027), TIA/EIA-124 (N.S0026), TIA/EIA-136, IS-95, IS-91 and TIA/EIA-2000 (C.S0001). TSG-N has taken TSB-29 and produced the specification N.S0017. + +The principle aspects of international implementation addressed by this document are: + +- the administration and assignment of system identification numbers (SIDs); +- the administration and assignment of mobile identification numbers (MINs); +- format of international mobile subscriber identifiers (IMSIs). + +The goal of this publication is to provide the international wireless telecommunications industry with the framework permitting the coordinated implementation of wireless radio telecommunication systems in compliance with the provisions of the AMPS family of air interface standards (e.g., TIA/EIA-553, IS-54, IS-91, IS-95, TIA/EIA-2000 and TIA/EIA-136). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-N.S0017-0 | 1.0.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TIA | TSB-29E | | Published | -- 12-2002 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-N.S0017-B_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-N.S0017-B_v1.0.zip | +| TTC | TS-3GB-N.S0017-Bv1.0 | 1.0 | TTC Published | 30-05-2003 | http://www.ttc.or.jp/imt2000/ts/tsns0017-Bv10.pdf | + +#### 10.2.15 N.S0018 Version 1.0.0 TIA/EIA-41-D Prepaid Charging (14 July 2000) + +Pre-Paid Charging (PPC) allows the subscriber to pay for voice telecommunication services prior to usage. This document presents a recommended plan for the implementation of Wireless Intelligent Network (WIN) capabilities that support PPC. The WIN capabilities that support PPC are for use in the Wireless Radiotelephone Service. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0018 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-826 | | Published | -- 09-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0018 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0018.zip | +| TTC | JP-3GB-N.S0018 | 2 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpns0018.pdf | + +#### **10.2.16 N.S0019 Version 1.0.0 Intersystem Link Protocol Revision: 0 (28 January 2000)** + +This document specifies an intersystem link protocol (ISLP) for circuit-mode data services. These data services include asynchronous data service (ADS) and Group-3 Fax as specified in IS-99 and IS-135. The ISLP adapts between air-interface data rates and higher-speed intersystem rates. The ISLP may be used between a serving system and an anchor system, possibly through one or more tandem systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0019 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA-728 | | Published | -- 01-2002 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0019 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0019.zip | +| TTC | JP-3GB-N.S0019 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0019.pdf | + +#### **10.2.17 N.S0020 TIA/EIA-41-D Message Segmentation (August 1999)** + +The 3GPP2 document was withdrawn. + +#### **10.2.18 N.S0021 Version 1.0.0 User Selective Call Forwarding Revision: 1 (14 July 2000)** + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the user selective call forwarding (USCF) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0021 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-838 | | Published | -- 07-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0021 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N.S0021v1.0.0.pdf | +| TTC | JP-3GB-N.S0021 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpns0021.pdf | + +#### **10.2.19 N.S0022 Version 1.0.0 Answer Hold (14 July 2000)** + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the answer hold (AH) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0022 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-837 | | Published | -- 09-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0022 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N.S0022v1.0.0.pdf | +| TTC | JP-3GB-N.S0022 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpns0022.pdf | + +#### 10.2.20 N.S0023-0 Version 1.0 Automatic Code Gapping (no date) + +This document presents a recommended plan for the implementation of automatic code gapping (ACG) for use in the wireless radiotelephone service. ACG is used to reduce the rate at which a network entity, typically an MSC, sends service request messages to a session control function (SCF) network entity. ACG controls can be applied automatically by the SCF when it is in overload. ACG controls can also be applied by an SCF for purposes of SCF service management. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0023-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-786 | | Published | -- 11-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0023-0 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0023-0v1.0.pdf | +| TTC | JP-3GB-N.S0023 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpns0023.pdf | + +### 10.2.21 N.S0024-0 Version 1.0 Network support for MDN-Based Message Centres (November 2000) + +This document is intended to identify TIA/EIA-41-D wireless number portability Phase III (WNP-PH3) technical enhancements required to support short message service (SMS) delivery to mobile directory number (MDN) based message centres (MCs). These enhancements have been supported for incorporation into PN-3590 (TIA/EIA-41-E) and are being published as a TIA/EIA-41-D enhancement interim standard (IS). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0024-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-841 | | Published | -- 09-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0024-0 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0024-0v1.0.pdf | +| TTC | TS-3GB-N.S0024v1.0 | 1.0 | TTC Published | 29-08-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0024-v10.pdf | + +### 10.2.22 N.S0025 Version 1.0.0 Roamer Database Verification (January 2001) + +This document presents a recommended plan for the implementation of roamer database verification (RDV) for use in the wireless radiotelephone service. RDV enables a home system to verify that a roaming partner's VLF database is correctly loaded for the MSID number ranges that "belong" to the home service provider. At the request of the HLR, the VLR examines its roamer database to verify that subscribers within the requested MSID range are allowed to roam in the visited system. + +RDV provides a tool to assist in resolving problems experienced by home system subscribers when roaming in the visited system. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0025 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-N.S0025 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0025v1.0.0.pdf | +| TTC | TS-3GB-N.S0025v1.0 | 1.0 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0025-v10.pdf | + +#### 10.2.22.1 N.S0025-A Version 1.0.0 Roamer Database Verification Revision: A (June 2002) + +This document presents a recommended plan for the implementation of roamer database verification (RDV) for use in the wireless radiotelephone service. + +Several types of network entities (NE) can initiate RDV service queries to verify the contents of databases relating to roaming in other network entities. + +RDV enables a home system to verify that a roaming partner's VLF database is correctly loaded for the MSID number ranges that "belong" to the home service provider. At the request of the HLR, the VLR examines its roamer database to verify that subscribers within the requested MSID range are allowed to roam in the visited system. + +RDV provides a tool to assist in resolving problems experienced by home system subscribers when roaming in the visited system. + +RDV may also be used to verify other message routing databases that may be used to support newer capabilities introduced in IS-41-C or in subsequent intersystem standards, including three message routing databases that may be maintained at an MSC and two message routing databases that may be maintained at an MC. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0025-A | 1.0.0 | Published | -09-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TIA | TIA/EIA/IS-847-A | | Published | -- 07-2002 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-N.S0025-A v1.0.0 | 1.0.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-N.S0025-A v1.0.0.zip | + +#### 10.2.22.2 N.S0025-B Version 1.0.0 Roamer Database Verification Revision: B (October 2002) + +This document presents a recommended plan for the implementation of roamer database verification (RDV) for use in the wireless radiotelephone service. + +Several types of network entities (NE) can initiate RDV service queries to verify the contents of databases relating to roaming in other network entities. + +RDV enables a home system to verify that a roaming partner's VLF database is correctly loaded for the MSID number ranges that "belong" to the home service provider. At the request of the HLR, the VLR examines its roamer database to verify that subscribers within the requested MSID range are allowed to roam in the visited system. + +RDV may also be used to verify other message routing databases that may be used to support newer capabilities introduced in IS-41-C or in subsequent intersystem standards, including three message routing databases that may be maintained at an MSC and two message routing databases that may be maintained at an MC. + +RDV provides a tool to assist in resolving problems experienced by home system subscribers when roaming in the visited system as well as other message routing database related problems. + +This document describes the RDV network capability and the intersystem operations to enable a wireless system to use RDV. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-N.S0025-B | 1.0.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-N.S0025-B_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-N.S0025-B_v1.0.zip | + +### 10.2.23 N.S0026 Version 1.0.0 Wireless Radio Telecommunication Intersystem Non-Signaling Data Communication DMH (August 2000) + +This standard is complementary to the ANSI-41, cellular radiotelecommunications intersystem operations, series of standards and identifies wireless services specifically involving non-signalling data communications which require intersystem cooperation, presents the general background against which those services are to be provided, and summarizes the principle considerations which have governed and directed the particular approaches taken in the procedural recommendations. + +This standard describes the messages and procedures required to perform call detail record data transmission between systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0026 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA-124-C | | Published | -- 09-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0026 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0026v1.0.0.pdf | + +#### 10.2.23.1 N.S0026-A Version 1.0.0 Wireless Radio Telecommunication Intersystem Non-Signaling Data Communication DMH Revision A (December 2001) + +This standard is complementary to the ANSI-41, cellular radiotelecommunications intersystem operations, series of standards and identifies wireless services specifically involving non-signalling data communications which require intersystem cooperation, presents the general background against which those services are to be provided, and summarizes the principle considerations which have governed and directed the particular approaches taken in the procedural recommendations. + +This standard describes the messages and procedures required to perform call detail record data transmission between systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-N.S0026-A | 1.0.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TIA | TIA/EIA-124-D | | Published | -- 12-2001 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-N.S0026-A_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-N.S0026-A_v1.0.zip | + +### 10.2.24 N.S0027 Version 1.0.0 Enhanced International Dialing, Calling Number Identification & Callback, Calling Party Category Identification (April 2001) + +This document presents a recommended plan for the implementation of enhanced international dialling, calling number identification and callback, and calling party category identification for use in the wireless radiotelephone service. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0027 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-875 | | Published | -- 05-2001 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-N.S0027 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0027v1.0.0.pdf | +| TTC | TS-3GB-N.S0027v1.0 | 1.0 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0027-v10.pdf | + +### **10.2.25 N.S0028 Version 1.0.0 Network Interworking Between GSM MAP and ANSI-41 MAP Rev. B Revision: 0 (April 2002)** + +The 3GPP2 document was superseded by X.S0023-B v1.0. + +### **10.2.26 N.S0029 Version 1.0.0 TIA/EIA-41-D Based Network Enhancements for CDMA Packet Data Service (C-PDS), Phase 1 Revision: 0 (June 2002)** + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with packet data service. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-N.S0029 | 1.0.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TIA | TIA/EIA-IS-880 | | Published | -- 07-2002 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-N.S0029-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-N.S0029-0 v1.0.zip | +| TTC | TS-3GB-N.S0029-0v1.0 | 1.0 | TTC Published | 27-08-2002 | http://www.ttc.or.jp/imt2000/ts/tsns0029-0v10.pdf | + +### **10.2.27 N.S0030 Version 1.0.0 Enhanced Wireless 9-1-1 Phase 2 Revision: 0 (April 2002)** + +The 3GPP2 document was withdrawn. + +## **10.3 Packet data specifications** + +### **10.3.1 P.S0001-A Version 3.0.0 Wireless IP Network Standard (16 July 2001)** + +This standard defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification is based on P.R0001; cdma2000 wireless IP network architecture based on IETF protocols. + +This standard defines the two methods for accessing public networks (Internet) and private networks (intranets): simple IP and mobile IP, and the required quality of service and accounting support. IETF protocols are widely employed whenever possible to minimize the number of new protocols required and to maximize the utilization of well accepted standards and hence the speed to market. Reference to the required IETF protocols is provided in section 3 of this standard. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-P.S0001-A | 3.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA/IS-835-A | | Published | -- 05-2001 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-P.S0001-A v3.0.0 | 3.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-P.S0001-Av3.0.0.pdf | +| TTC | TS-3GB-P.S0001-Av3.0 | 3.0 | TTC Published | 29-08-2001 | http://www.ttc.or.jp/imt2000/ts/tsps0001-A-v30.pdf | + +### 10.3.2 P.S0001-B Version 1.0.0 Wireless IP Network Standard (25 October 2002) + +The 3GPP2 document was superseded by X.S0011-C. + +### 10.3.3 P.S0001-B Version 2.0 cdma2000 Wireless IP Network Standard (September 2004) + +The 3GPP2 document was superseded by X.S0011-C. + +## 10.4 Services and system aspects specifications + +### 10.4.1 S.R0003 Version 1.0.0 3GPP2 System Capability Guide Release A (20 January 2000) + +The 3GPP2 document is re-numbered as SC.R2001-001 v1.0 + +#### 10.4.1.1 S.R0003-A Version 1.0 3GPP2 System Capability Guide Release B (14 June 2001) + +This document is re-numbered as SC.R2002-001 v1.0 + +### 10.4.2 S.R0004 Version 1.0.0 Service Implementation Guide Revision: 0 (20 January 2000) + +This service implementation document describes and defines features adopted by 3GPP2 TSG-S. The features descriptions may include both stage 1 and stage 2 functional levels. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0004 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0004v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0004v1.0.0.pdf | + +### 10.4.3 S.R0005-B Version 1.0 Network Reference Model for cdma2000 Spread Spectrum Systems Revision: B (16 April 2001) + +This document recommends the basic 3GPP2 wireless network reference model. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0005-B | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TSB-100-A | | Published | -- 03-2001 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-S.R0005-B | 1 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0005-B.zip | +| TTC | TS-3GB-S.R0005-Bv1.0 | 1.0 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsr0005-B-v10.pdf | + +#### **10.4.4 S.R0006 Version 1.0.0 Wireless Features Description Revision: 0 (13 December 1999)** + +This standard presents a recommended plan for the implementation of uniform features for use in the wireless radiotelephone service. Its intent is to describe services and features so that the manner in which a subscriber may place calls using such features and services may remain reasonably consistent from system to system. It is not intended that specific service offerings be required of all service providers. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0006 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TIA | TIA/EIA-664-A | | Published | -- 12-2000 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-S.R0006 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0006v1.0.0.pdf | +| TTC | JP-3GB-S.R0006 | 1 | TTC
Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0006.pdf | + +#### **10.4.5 S.R0007 Version 1.0.0 User Selective Call Forwarding (Stage 1) Revision: 0 (13 December 1999)** + +This interim standard (IS) presents stage 1 (new chapter TIA/EIA-664-B), stage 2 (TIA/EIA-41.3-D enhancements), and stage 3 (TIA/EIA-41.5-D and TIA/EIA-41.6-D enhancements) recommendations for supporting the user selective call forwarding (USCF) feature use in the wireless radiotelephone service. + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the user selective call forwarding (USCF) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0007 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0007 v1.0 | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0007_v1.0.zip | + +##### **10.4.5.1 S.R0007 Version 2.1 User Selective Call Forwarding (Stage 1) (31 January 2001)** + +This interim standard (IS) presents stage 1 (new chapter TIA/EIA-664-B), stage 2 (TIA/EIA-41.3-D enhancements), and stage 3 (TIA/EIA-41.5-D and TIA/EIA-41.6-D enhancements) recommendations for supporting the user selective call forwarding (USCF) feature use in the wireless radiotelephone service. + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the user selective call forwarding (USCF) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0007 v2.1 | 2.1 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0007 v2.1 | 2.1 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0007_v2.1.zip | +| TTC | TS-3GB-S.R0007v2.1 | 2.1 | TTC
Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0007-v21.pdf | + +#### **10.4.6 S.R0008 Version 1.0.0 Answer Hold (Stage 1) Revision: 0 (13 December 1999)** + +This interim standard (IS) presents stage 1 (new chapter TIA/EIA-664-B), stage 2 (TIA/EIA-41.3-D enhancements), and stage 3 (TIA/EIA-41.5-D and TIA/EIA-41.6-D enhancements) recommendations for supporting the answer hold (AH) feature use in the wireless radiotelephone service. + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the answer hold (AH) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0008 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0008 V.1.0 | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0008 v1.0.zip | + +#### **10.4.6.1 S.R0008 Version 2.0 Answer Hold (Stage 1) Revision: 0 (8 December 2000)** + +This interim standard (IS) presents stage 1 (new chapter TIA/EIA-664-B), stage 2 (TIA/EIA-41.3-D-enhancements), and stage 3 (TIA/EIA-41.5-D and TIA/EIA-41.6-D enhancements) recommendations for supporting the answer hold (AH) feature use in the wireless radiotelephone service. + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the answer hold (AH) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0008 v2.1 | v2.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0008 V.2.0 | 2.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0008 v2.0.zip | +| TTC | JP-3GB-S.R0008 | 2 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0008.pdf | + +#### **10.4.7 S.R0009-0 v1.0 User Identity Module (Stage 1) Revision: 0 (13 December 1999)** + +This standard defines the enhancements required for the support of mobile stations equipped with user identification modules (UIMs). The UIM provides functionality to certain types of mobile stations to enable them to operate in the wireless network. + +This document defines requirements for the wireless network to support operation of UIM-equipped mobile stations. A UIM provides compatible mobile stations with the parameters required of mobile stations operating in the TIA/EIA-41 environment and specific additional functionality unique to UIM-equipped mobile stations. + +The UIM can be in one of two forms: as either integrated within the mobile, or removable that can be inserted or removed from the mobile equipment. This document addresses removable UIM (R-UIM) only. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0009-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0009 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0009.zip | +| TTC | TS-3GB-S.R0009 | 1 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0009-v10.pdf | + +#### **10.4.8 S.R0010 Version 1.0.0 Preferred Language (Stage 1) Revision: 0 (13 December 1999)** + +Preferred language (PL) provides the subscriber the ability to specify the language for network services. + +Network services which could be offered in the subscriber's preferred language include: + +- recorded announcements; +- directory assistance; +- operator services; +- emergency services; +- "Help" lines; +- message waiting notification; +- CNIP number not available; and +- CNIP number restricted. + +If the subscriber's preferred language is not available, service shall be provided in the default language, which shall be determined by the wireless network operator. + +PL does not impact a subscriber's ability to originate calls or to receive calls. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0010 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0010 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0010.zip | +| TTC | JP-3GB-S.R0010 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0010.pdf | + +#### **10.4.9 S.R0011 Version 1.0.0 Advice of Charge (Stage 1) Revision: 0 (13 December 1999)** + +This specification presents stage 1 for supporting the advice of charge feature for use in the wireless radiotelephone service. + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the advice of charge (AoC) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0011 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0011 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0011.zip | +| TTC | JP-3GB-S.R0011 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0011.pdf | + +#### **10.4.10 S.R0012 Version 1.0.0 Rejection of Undesired Annoying Calls (Stage 1) Revision: 0 (13 December 1999)** + +This specification presents stage 1 for supporting rejection of undesired annoying calls feature for use in the wireless radiotelephone service. + +This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the rejection of undesired annoying calls (RUAC) feature. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0012 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0012 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0012.zip | +| TTC | JP-3GB-S.R0012 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0012.pdf | + +#### 10.4.11 S.R0013 Version 1.0.0 Global Emergency Call Origination (GECO) Revision: 0 (13 December 1999) + +This document presents a stage 1 description for a global emergency call origination (GECO) which will increase the probability that any user can originate a call to a public service access point (PSAP) even in those service areas where the emergency service access number (ESAN) is not known to the user. + +The intent of GECO is described as follows: + +- The MS may provide a means for the user to initiate an emergency call. +- A special form of the call origination message (defined as a global emergency call origination message (GECO\_MSG)) may be issued by the MS in lieu of the normal call origination message to indicate that the call origination being requested is an emergency call origination. GECO\_MSGs may be accepted and the GECO call connected by the network from both subscribed and unsubscribed mobiles. The system may support "implicit registration" for GECO calls such that the use of registration request/acceptance protocol is not required prior to the issuance of a GECO\_MSG. +- If the MS is currently registered on and accessing an operating network when the GECO call is initiated by the user, the MS may use that system to initiate the GECO call. If the MS is not currently accessing a system, the MS may attempt to access its preferred service as indicated by its internal system selection and system access restriction programming to maximize the probability that the GECO call will be accepted by the system. If no preferred system is available, the MS may override its internal system selection and system access restriction programming in an attempt to access any available system. +- Initiation of a GECO call by the MS shall in no way degrade the user's access to any other feature/service which would normally be available to him from the accessed service provider's network. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0013 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0013 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0013.zip | +| TTC | JP-3GB-S.R0013 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0013.pdf | + +#### 10.4.12 S.R0014 Version 1.0.0 Tandem Free Operation (Stage 1) Revision: 0 (13 December 1999) + +It is expected that the need for tandem free operations will be driven by the increasing market penetration of digital technologies which will result in an increase in percentage of mobile-to-mobile calls. In addition, given that the effects of tandem vocoding are greater for lower bit rate vocoders, the need for this feature becomes greater as the use of low bit rate vocoders increases. The tandem free operation (TFO) feature, also known as vocoder bypass, improves the end-to-end voice quality observed in mobile-to-mobile voice calls in wireless networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0014 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0014 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0014.zip | +| TTC | JP-3GB-S.R0014 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0014.pdf | + +#### **10.4.13 S.R0015 Version 1.0.0 ISDN Interworking (Stage 1) Release A (13 December 1999)** + +This document presents stage 1 (new chapter TTA/EIA-664-B) recommendations for supporting the ISDN interworking feature use in wireless radiotelephone service. + +This document specifies the wireless intersystem network operation enhancements required for supporting subscribers with the ISDN interworking feature. This document defines the functional characteristics for interconnecting to ISDN in circuit-switched mode. The interworking function in ISDN packet mode, i.e., B-channel packet is out of scope at present. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0015 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0015 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0015.zip | +| TTC | JP-3GB-S.R0015 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0015.pdf | + +#### **10.4.14 S.R0016 Version 1.0.0 Automatic Code Gapping (Stage 1) Revision: 0 (13 December 1999)** + +Automatic code gapping (ACG) is intended to provide a network entity, such as a service control point (SCP) or session control function (SCF), the ability to turn off selected types of traffic that may be passing through its domain of operation. The purpose for ACG may be load-related or in response to a traffic engineering command as from a service management system (SMS). This report provides a general description of ACG as it applies to 3G network operations. Specific applications will be defined in other documents or later versions of this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0016 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0016 V.1.0 | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0016.zip | + +#### **10.4.14.1 S.R0016 Version 2.0 Automatic Code Gapping (Stage 1) Revision: 0 (8 December 2000)** + +Automatic code gapping (ACG) is intended to provide a network entity, such as a service control point (SCP) or session control function (SCF), the ability to turn off selected types of traffic that may be passing through its domain of operation. The purpose for ACG may be load-related or in response to a traffic engineering command as from a service management system (SMS). This report provides a general description of ACG as it applies to 3G network operations. Specific applications will be defined in other documents or later versions of this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0016 v2.0 | 2.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0016 V.2.0 | 2.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0016_v2.0.zip | +| TTC | JP-3GB-S.R0016 | 2 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0016.pdf | + +#### 10.4.15 S.R0017 3G Wireless Network Management System High Level Requirements Revision: 0 (13 December 1999) + +This report specifies the 3G wireless network management system high level requirements including: OAM&P TMN applications required network and systems management processes and network reference model (NRM) + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0017 | | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0017 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0017.zip | +| TTC | TR-3GB-S.R0017-0v1.0 | 1.0 | TTC Published | 26-02-2002 | http://www.ttc.or.jp/imt2000/tr/trsr0017-0v10.pdf | + +#### 10.4.16 S.R0018 Version 1.0.0 Pre-Paid Charging (Stage 1) Revision: 0 (13 December 1999) + +PPC allows the subscriber to pay for voice telecommunication services prior to usage. + +A PPC subscriber establishes an account with the service provider to access voice telecommunication services in home and roaming networks. Charges for voice telecommunication services are applied to the PPC account by decrementing the account in real time. The PPC subscriber may be notified about the account information at the beginning, during, or at the end of the voice telecommunications service. When the account balance is low the subscriber may be notified so that the subscriber may refill the account. When the account balance is below a pre-defined threshold, the subscriber's use of voice telecommunications services may be de-authorized. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0018 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0018 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0018.zip | +| TTC | JP-3GB-S.R0018 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0018.pdf | + +#### 10.4.17 S.R0019 Version 1.0.0 Location-Based Services System (LBSS) Stage 1 Description (22 September 2000) + +This document defines LBSS for implementation in 3GPP2 systems. The location services functionality has been adopted from existing TR-45 standards as defined and also as described within the document. + +The scope of this document includes 3GPP2 system support required to facilitate location-based services. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0019 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0019 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0019v1.0.0.pdf | +| TTC | JP-3GB-S.R0019 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0019.pdf | + +#### 10.4.18 S.R0021 Version 1.0 Video Streaming Service – Stage 1 (10 July 2000) + +The objective is to define and to standardize the functionality of video services that can be incorporated into the operations of wireless telecommunication networks. Audio-only streaming is a special case of video streaming. This document defines the functional characteristics and requirements of the video streaming services. The areas that must be defined are service features and system requirements, necessary for video streaming services to be provided in wireless telecommunication networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0021 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0021 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0021v1.0.pdf | +| TTC | JP-3GB-S.R0021 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0021.pdf | + +#### 10.4.18.1 S.R0021 Version 2.0 Multimedia Streaming Service – Stage 1 (18 April 2002) + +The objective is to define and to standardize the functionality of multimedia services that can be incorporated into the operations of wireless telecommunication networks. Audio-only or video-only streaming are a special case of multimedia streaming. This document defines the functional characteristics and requirements of the multimedia streaming services. The areas that must be defined are service features and system requirements, necessary for multimedia streaming services to be provided in wireless telecommunication networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0021 | 2.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0021-0_v2.0 | 2.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0021-0_v2.0.zip | +| TTC | TS-3GB-S.R0021-0v2.0 | 2.0 | TTC Published | 27-08-2002 | http://www.ttc.or.jp/imt2000/ts/tssr0021-0v20.pdf | + +#### 10.4.19 S.R0022 Version 1.0 Video Conferencing Service – Stage 1 (10 July 2000) + +The objective is to define and to standardize the functionality of video services that can be incorporated into the operations of wireless telecommunication networks. This report defines the functional characteristics and the requirements of the video conferencing services. The areas that must be defined are service features and system requirements in order for voice conferencing services to be provided in wireless telecommunication networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0022 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0022 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-R0022v1.0.pdf | +| TTC | JP-3GB-S.R0022 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0022.pdf | + +#### 10.4.20 S.R0023 Version 1.0 High-Speed Data Enhancements for cdma2000 1x – Data Only (9 June 2000) + +This document outlines the key operator requirements for the evolution of the cdma2000 1x (current versions of C.S0001 through C.S0005) standard. This document will refer to this evolution as 1x evolved high-speed data only (1xEVDO). These requirements are defined to drive improvements to the fundamental packet data capabilities and efficiencies of cdma2000 1x systems to better meet the rapidly evolving needs of subscribers. This report is intended as a guide for wireless operators in the implementation of high-speed data-only systems beyond cdma2000 1x, to provide increased spectral efficiency and the capability to satisfy customer demand for wireless packet data applications. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0023 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0023 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-R0023v1.0.pdf | + +#### 10.4.20.1 S.R0023 Version 2.0 High-Speed Data Enhancements for cdma2000 1x – Data Only Stage 1 Requirements (5 December 2000) + +This document outlines the key operator requirements for the evolution of the cdma2000 1x (current versions of C.S0001 through C.S0005) standard. This document will refer to this evolution as 1x evolved high-speed data only (1xEVDO). These requirements are defined to drive improvements to the fundamental packet data capabilities and efficiencies of cdma2000 1x systems to better meet the rapidly evolving needs of subscribers. This report is intended as a guide for wireless operators in the implementation of high-speed data-only systems beyond cdma2000 1x, to provide increased spectral efficiency and the capability to satisfy customer demand for wireless packet data applications. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | TR-T13-S.R0023 v2.0 | 2.0 | ARIB Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_TR-T13-S.R0023_V2.PDF | +| CCSA | CWTS-MC-S.R0023 v2.0 | 2.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0023 v2.0 | 2.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S_R0023_v2.0.zip | + +#### 10.4.21 S.R0024 Version 1.0 Wireless Local Loop – Stage 1 Description (22 September 2000) + +Wireless local loop (WLL) is a feature implementation using a serving system that utilizes a wireless connection to a wireless device, such as a mobile station or a network interface unit, to provide local loop service to an end user. WLL permits local loop service for subscriber call origination and for receipt of calls. WLL applies to voice and data services. WLL provides signalling mechanisms between the serving system and the mobile station or the network interface unit. This signalling mechanism permits the exchange of call control information. + +The essential signalling elements of WLL are: + +- Mobile station or network interface unit device type specification and request for WLL of the serving system or optional serving system device type specification. +- Mobile station or network interface unit dial tone or optional dial tone of the serving system. +- Mobile station or network interface unit hook status enabling WLL call control of the serving system. +- Serving system autonomous message interval specification and request of the mobile station or the network interface unit or optional network interface unit autonomous message interval specification. +- Serving system call waiting indicator notification to the mobile station or the network interface unit. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0024 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0024 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0024v1.0.pdf | + +#### 10.4.22 S.R0025 Version 1.0 Wireless Pay Phone – Stage 1 Description (22 September 2000) + +Wireless pay phone is a public telecommunication service feature that allows mobile station support of pay phone applications. The wireless pay phone feature is useful to subscribers that originate or receive calls at a pay phone. + +The feature may be comprised of two signalling capabilities. The first signalling capability is that which allows a serving system to convey answer supervision. The second signalling capability is that which allows a serving system to meter calls. + +NOTE – A serving system may convey answer supervision using alert-signalled or flash-signalled line control. A serving system may meter using alert-signalled or flash-signaled meter pulses. + +Answer element of supervision is used by the mobile station to convey line polarity, which is useful as an answer supervision indication. Line control specification and notification of the mobile station enables specification of polarity included, toggle mode, reverse polarity and power denial time. These are specified in IS-95B section 7.7.5.15. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0025 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0025 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0025v1.0.pdf | + +#### 10.4.23 S.R0026 Version 1.0 High Speed Data Enhancements for cdma 2000 1x – Integrated Data and Voice Stage 1 Requirements (17 October 2000) + +This document outlines the key operator requirements for the evolution of the cdma2000 1x (current versions of C.S0001 through C.S0005) standard. This document will refer to this evolution as 1x-evolved high-speed integrated data and voice (1xEV-DV). These requirements are defined to drive improvements to the fundamental packet data capabilities and efficiencies of cdma2000 1x systems to better meet the rapidly evolving needs of subscribers. This document is intended as a guide for 3GPP2 TSGs in the development of specifications for high-speed integrated data and voice systems beyond cdma2000 1x services (voice, fax, circuit switched data), to provide increased + +spectral efficiency and the capability to satisfy customer demand for wireless voice and packet data applications. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0026 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0026 | 1 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0026.zip | + +#### **10.4.24 S.R0027 Version 1 Personal Mobility Stage 1 Requirements (8 December 2000)** + +The objective is to define and standardize the functionality of personal mobility that can be incorporated into the operations of both 2G/3G TTA/EIA-41 and 2G/3G GSM-derived wireless telecommunications networks. This document defines the requirements of personal mobility features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0027 | 1 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0027 | 1 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0027.zip | +| TTC | JP-3GB-S.R0027 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0027.pdf | + +#### **10.4.25 S.S0028 Version 1.0 OAM&P for cdma2000 (3GPP Delta Specification) (18 April 2001)** + +This document contains the OAM&P requirements and interface definitions for cdma2000-based systems. It is an extension of operations and maintenance requirements, per latest 3GPP 32-series specifications capabilities to enable operation in a cdma2000 systems environment as part of the TTA/EIA/IS-2000 family of standards. They are in alignment with OAM&P Stage 1 IS-2000 requirements. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.S0028 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.S0028 V.1.0 | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_S0028_v1.0.zip | +| TTC | JP-3GB-S.S0028v1.0 | 1.0 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsss0028-v10.pdf | + +#### **10.4.25.1 S.S0028 Version 2.0 OAM&P for cdma2000 (3GPP Delta Specification) (23 July 2001)** + +This document is intended to define the OAM&P stage 2 and stage 3 requirements and interface definitions for cdma2000-based systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.S0028 | 2.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAE.3G-S.S0028 V.2.0 | 2.0 | Approved | 19-12-2001 | http://www.tta.or.kr/imt2000/TTAE_3G-S_S0028_v2.0.zip | +| TTC | TS-3GB-S.S0028-0v2.0 | 2.0 | TTC Published | 28-11-2001 | http://www.ttc.or.jp/imt2000/ts/tsss0028-0v20.pdf | + +#### 10.4.25.2 S.S0028 Version 3.0 OAM&P for cdma2000 (3GPP Delta Specification) (11 March 2002) + +This document is intended to define the OAM&P stage 2 and stage 3 requirements and interface definitions for cdma2000-based systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.S0028 | 3.0 | Published | -06-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.S0028-0 v3.0 | 3.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.S0028-0_v3.0.zip | +| TTC | TS-3GB-S.S0028-0v3.0 | 3.0 | TTC Published | 28-05-2002 | http://www.ttc.or.jp/imt2000/ts/tsss0028-0v30.pdf | + +#### 10.4.25.3 S.S0028-A Version 1.0 OAM&P for cdma2000 (3GPP R4 Delta Specification) Revision: A (12 December 2002) + +This document is intended to define the OAM&P stage 2 and stage 3 requirements and interface definitions for cdma2000-based systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-A | 1.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.S0028-A_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-A_v1.0.zip | + +#### 10.4.25.4 S.S0028-A Version 2.0 OAM&P for cdma2000 (3GPP R4 Delta Specification) Revision: A (20 February 2003) + +This document is intended to define the OAM&P stage 2 and stage 3 requirements and interface definitions for cdma2000-based systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-A | 2.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.S0028-A_v2.0 | 2.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-A_v2.0.zip | +| TTC | TS-3GB-S.S0028-Av2.0 | 2.0 | TTC Published | 30-05-2003 | http://www.ttc.or.jp/imt2000/ts/tsss0028-Av20.pdf | + +#### 10.4.25.5 S.S0028-A Version 3.0 OAM&P for cdma2000 (3GPP R4Delta Specification) Revision: A (20 February 2003) + +This document is intended to define the OAM&P stage 2 and stage 3 requirements and interface definitions for cdma2000-based systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-A | 3.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-A v3.0 | 3.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-A v3.0.zip | +| TTC | S.S0028-A v3.0 | 3.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-av30.pdf | + +#### 10.4.25.6 S.S0028-000-B Version 1.0 OAM&P for cdma2000 (Overview) (17 February 2005) + +This document is the overview component of a multipart specification intended to define the OAM&P stage 2 and stage 3 requirements and interface definitions for CDMA- and cdma2000®-based systems. This multipart specification consists of: + +- **S.S0028-000-B: "OAM&P for cdma2000 (Overview)"**. +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)" +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)" +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)" +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)" + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-000-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-000-B v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-000-B v1.0.zip | +| TTC | TS-3GB-S.S0028-000-Bv1.0 | 1.0 | TTC published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-000-bv10.pdf | + +#### 10.4.25.7 S.S0028-000-C Version 1.0 OAM&P for cdma2000 (Overview) Revision: C (18 January 2006) + +This document is the overview component of a multipart specification intended to define the OAM&P stage 2 and stage 3 requirements and interface definitions for CDMA- and cdma2000®-based systems. This multipart specification consists of: + +- **S.S0028-000-C: "OAM&P for cdma2000 (Overview)"**. +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)" +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)" +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)" +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)" + +2 cdma2000® is the trademark for the technical nomenclature for certain specifications and standards of the organizational partners (OPs) of 3GPP2. Geographically (and at the date of publication) cdma2000® is a registered trademark of the Telecommunication Industry Association (TIA-USA) in the United States. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0028-000-C v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0028-000-C v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-000-C v1.0.zip | +| TTC | TS-3GB-S.S0028-000-Cv1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0028-000-cv10.pdf | + +#### 10.4.25.8 S.S0028-001-B Version 1.0 OAM&P for cdma2000 (3GPP R5 Delta Specification) (17 February 2005) + +This document is the 3GPP R5 delta specification component of a multipart specification intended to define the OAM&P stage 2 and stage 3 requirements and interface definitions for CDMA- and cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)". +- **S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)"**. +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)". +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)". +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-001-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-001-B v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-001-B v1.0.zip | +| TTC | TS-3GB-S.S0028-001-Bv1.0 | 1.0 | TTC published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-001-bv10.pdf | + +#### 10.4.25.9 S.S0028-001-B Version 2.0 OAM&P for cdma2000 (3GPP R5 Delta Specification) Revision: B (18 July 2005) + +This document is the 3GPP R5 delta specification component of a multipart specification intended to define the OAM&P stage 2 and stage 3 requirements and interface definitions for CDMA- and cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)". +- **S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)"**. +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)". +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)". +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-001-B | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-001-B v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-001-B v2.0.zip | +| TTC | S.S0028-001-B v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-001-bv20.pdf | + +#### 10.4.25.10 S.S0028-001-C Version 1.0 OAM&P for cdma2000 (3GPP R6 Delta Specification) Revision: C (18 January 2006) + +This document is the 3GPP R6 delta specification component of a multipart specification intended to define the OAM&P stage 2 and stage 3 requirements and interface definitions for CDMA- and cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)". +- **S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)".** +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)". +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)". +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0028-001-C v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0028-001-C v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-001-C v1.0.zip | +| TTC | S.S0028-001-C v1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0028-001-cv10.pdf | + +#### 10.4.25.11 S.S0028-002-B Version 1.0 OAM&P for cdma2000 (3GPP2 Generic NRM IRP) (17 February 2005) + +This document is the 3GPP2 generic NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and stage 3 requirements and interface definitions for CDMA- and cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)". +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)". +- **S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)".** +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)". +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-002-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-002-B v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-002-B v1.0.zip | +| TTC | TS-3GB-S.S0028-002-Bv1.0 | 1.0 | TTC published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-002-bv10.pdf | + +#### 10.4.25.12 S.S0028-002-C Version 1.0 OAM&P for cdma2000 (3GPP2 Generic NRM IRP) Revision: C (18 January 2006) + +This document is the 3GPP2 generic NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and stage 3 requirements and interface definitions for CDMA- and cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)". +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)". +- **S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)".** + +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)". +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0028-002-C v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0028-002-C v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-002-C v1.0.zip | +| TTC | TS-3GB-S.S0028-002-Cv1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0028-002-cv10.pdf | + +#### 10.4.25.13 S.S0028-003-B Version 1.0 OAM&P for cdma2000 (3GPP2 Core NRM IRP) (17 February 2005) + +This document is the 3GPP2 Core NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and stage 3 requirements and interface definitions for CDMA- and cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)". +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)". +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)". +- **S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)".** +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-003-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-003-B v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-003-B v1.0.zip | +| TTC | TS-3GB-S.S0028-003-Bv1.0 | 1.0 | TTC published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-003-bv10.pdf | + +#### 10.4.25.14 S.S0028-003-B Version 2.0 OAM&P for cdma2000 (3GPP2 Core NRM IRP) Revision: B (18 July 2005) + +This document is the 3GPP2 core NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and stage 3 requirements and interface definitions for CDMA- and cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)". +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)". +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)". +- **S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)".** +- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-003-B | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-003-B v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-003-B v2.0.zip | +| TTC | S.S0028-003-B v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-003-bv20.pdf | + +#### 10.4.25.15 S.S0028-003-C Version 1.0 OAM&P for cdma2000 (3GPP2 Core NRM IRP) Revision: C (18 January 2006) + +This document is the 3GPP2 Core NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and stage 3 requirements and interface definitions for CDMA- and cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)". +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)". +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)". +- **S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)".** +- S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)". + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0028-003-C v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0028-003-C v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-003-C v1.0.zip | +| TTC | TS-3GB-S.S0028-003-Cv1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0028-003-cv10.pdf | + +#### 10.4.25.16 S.S0028-004-B Version 1.0 OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP) (17 February 2005) + +This document is the 3GPP2 radio access NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and stage 3 requirements and interface definitions for CDMA- and cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)". +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)". +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)". +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)". +- **S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)".** + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-004-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-004-B v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-004-B v1.0.zip | +| TTC | TS-3GB-S.S0028-004-Bv1.0 | 1.0 | TTC published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-004-bv10.pdf | + +#### 10.4.25.17 S.S0028-004-B Version 2.0 OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP) (17 February 2005) + +This document is the 3GPP2 radio access NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and stage 3 requirements and interface definitions for CDMA- and cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-B: "OAM&P for cdma2000 (Overview)". +- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)". +- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)". +- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)". +- **S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)".** + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0028-004-B | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0028-004-B v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-004-B_v2.0.zip | +| TTC | S.S0028-004-B v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-004-bv20.pdf | + +#### 10.4.25.18 S.S0028-004-C Version 1.0 OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP) Revision: C (18 January 2006) + +This document is the 3GPP2 radio access NRM IRP component of a multipart specification intended to define the OAM&P stage 2 and stage 3 requirements and interface definitions for CDMA- and cdma2000®-based systems. This multipart specification consists of: + +- S.S0028-000-C: "OAM&P for cdma2000 (Overview)". +- S.S0028-001-C: "OAM&P for cdma2000 (3GPP R6 Delta Specification)". +- S.S0028-002-C: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)". +- S.S0028-003-C: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)". +- **S.S0028-004-C: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)".** + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0028-004-C v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0028-004-C v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-004-C_v1.0.zip | +| TTC | TS-3GB-S.S0028-004-Cv1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0028-004-cv10.pdf | + +#### 10.4.26 S.R0029 Version 1.0.0 Access Control Based on Call Type – Stage 1 Description (22 September 2000) + +This document defines requirements for the cdma2000 air interface to support access control based on call type (ACCT). ACCT provides the control of access attempt from mobile stations by service option or a set of service options. + +Control for terminating calls to mobile stations is outside the scope of this feature description. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0029 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0029 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0029v1.0.0.pdf | +| TTC | TS-3GB-S.R0029v1.0 | 1.0 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0029-v10.pdf | + +#### 10.4.27 S.R0030 Version 1.0 Broadcast/Multicast Services – Stage 1 (22 August 2001) + +The objective of this document is to define and to standardize the functionality of broadcast/multicast services that can be incorporated into the operations of cdma2000-based wireless telecommunication networks. This document defines the functional characteristics and requirements of broadcast/multicast services. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0030 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAE.3G-S.R0030-0 v1.0 | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/imt2000/TTAE.3G-S.R0030-0 v1.0.zip | +| TTC | TS-3GB-S.R0030-0v1.0 | 1.0 | TTC Published | 28-11-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0030-0v10.pdf | + +#### 10.4.27.1 S.R0030-A Version 1.0 Broadcast/Multicast Services – Stage 1 Revision A (15 January 2004) + +The objective of this document is to define and to standardize the functionality of broadcast/multicast services that can be incorporated into the operations of cdma2000-based wireless telecommunication networks. This document defines the functional characteristics and requirements of broadcast/multicast services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0030-A v1.0 | 1 | Approved | 15-01-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0030-A v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0030-A v1.0.zip | +| TTC | TS-3GB-S.R0030-Av1.0 | 1.0 | TTC published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0030-av10.pdf | + +#### 10.4.28 S.R0032 Version 1.0 Enhanced Subscriber Authentication (ESA) and Enhanced Subscriber Privacy (ESP) (6 December 2000) + +This document defines requirements for the cdma2000 air interface to support enhanced subscriber authentication (ESA) and enhanced subscriber privacy (ESP). ESA provides enhanced security in authentication and ESP provides enhanced privacy of user data. Selection of cryptographic algorithms is outside the scope of this feature description. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0032 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0032 | 1 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0032.zip | +| TTC | JP-3GB-S.R0032 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0032.pdf | + +#### **10.4.29 S.R0033 Version 1.0 Realm Configured Packet Data Session Dormancy Timer (06 December 2001)** + +This document specifies the requirements for the operations of the realm configured packet data session dormancy timer (RC-PDSDT) feature from the perspective of the user(s) and/or the system operator. The RC-PDSDT is a timer which is used to measure the duration of dormancy of a packet data session. The purpose of this timer is similar to the packet data inactivity timer specified in the C.S0017 standard. + +The objective is to define and to standardize the functionality of this feature/service that can be incorporated into the operations of cdma2000-based wireless telecommunication networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0033 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0033-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0033-0 v1.0.zip | + +#### **10.4.30 S.R0034 Version 1.0 User Identification Module ID Manufacturer's Code Assignment Guidelines and Procedures (18 April 2001)** + +These guidelines are based on the content of the ANSI TIA/EIA-41 family of standards (e.g., AMPS (EIA/TIA-553), CDMA (TIA/EIA-95 and TIA/EIA/IS-2000), and TDMA (IS-54, IS-136)). It is recommended that systems which are based on the ANSI TIA/EIA-41 family of standards and which are deployed outside of the United States follow these guidelines. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0034 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0034 | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0034.zip | +| TTC | TS-3GB-S.R0034v1.0 | 1.0 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsr0034-v10.pdf | + +#### **10.4.30.1 S.R0034 Version 2.0 User Identification Module ID Manufacturer's Code Assignment Guidelines and Procedures (29 August 2002)** + +These guidelines are based on the content of the ANSI TIA/EIA-41 family of standards (e.g., AMPS (EIA/TIA-553), CDMA (TIA/EIA-95 and TIA/EIA/IS-2000), and TDMA (IS-54, IS-136)). It is recommended that systems which are based on the ANSI TIA/EIA-41 family of standards and which are deployed outside of the United States follow these guidelines. This is to facilitate international roaming and to minimize fraud. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0034 | 2.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0034-0_v2.0 | 2.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0034-0_v2.0.zip | +| TTC | TS-3GB-S.R0034-0v2.0 | 2.0 | TTC Published | 26-11-2002 | http://www.ttc.or.jp/imt2000/ts/tssr0034-0v20.pdf | + +#### **10.4.31 S.R0037-0 Version 2.0 IP Network Architecture Model for cdma2000 Spread Spectrum Systems (14 May 2002)** + +The 3GPP2 document is superseded by S.R0037-0 version 3. + +##### **10.4.31.1 S.R0037-0 Version 3.0 IP Network Architecture Model for cdma2000 Spread Spectrum Systems (21 August 2003)** + +This document recommends the basic 3GPP2 wireless IP network architecture model. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0037-0 v3.0 | 3.0 | Published | 21-08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TSB-151 | | Published | -- 12-2003 | http://www.ttaonline.org/standards/catelog/search.cfm | +| TTA | TTAT.3G-S.R0037-0 V3.0 | 3.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0037-0_v3.0.zip | +| TTC | TS-3GB-S.R0037-0V3.0 | 3.0 | TTC published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tssr0037-0v30.pdf | + +#### **10.4.32 S.R0048 Version 1.0 3G Mobile Equipment Identifier (MEID) (10 May 2001)** + +The objective of this document is to define and standardize the structure of the 3G mobile equipment identifier. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0048 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC | +| TTA | TTAE.3G-S.R0048-0 V.1.0 | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0048_v1.0.zip | +| TTC | TS-3GB-S.R0048v1.0 | 1.0 | TTC Published | 29-08-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0048-v10.pdf | + +##### **10.4.32.1 S.R0048-A Version 1.0 3G Mobile Equipment Identifier (MEID) (22 August 2003)** + +The objective of this document is to define and standardize the structure of the 3G mobile equipment identifier. To facilitate mobile equipment identification and reduce the need to rely on ESNs to track mobiles, the need for a new identifier is required. The mobile equipment identifier (MEID) is proposed as a means to achieve these goals. Additionally, as global roaming and harmonization between 3G technologies become a reality, the need for a universal mobile equipment identifier is needed. The MEID is meant to address these issues. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0048-A v1.0 | 1.0 | Approved | 22-08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0048-A V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0048-A v1.0.zip | +| TTC | TS-3GB-S.R0048-AV1.0 | 1.0 | TTC Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tssr0048-av10.pdf | + +#### 10.4.32.2 S.R0048-A Version 2.0 3G Mobile Equipment Identifier (MEID) Stage 1 (22 April 2004) + +The objective of this document is to define and standardize the structure of the 3G mobile equipment identifier. To facilitate mobile equipment identification and reduce the need to rely on ESNs to track mobiles, the need for a new identifier is required. The mobile equipment identifier (MEID) is proposed as a means to achieve these goals. Additionally, as global roaming and harmonization between 3G technologies become a reality, the need for a universal mobile equipment identifier is needed. The MEID is meant to address these issues. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0048-A v2.0 | 1.0 | Approved | 22-04-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-928-1 | | Approved | -- 04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.R0048-A V2.0 | 2.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0048-A v2.0.zip | +| TTC | TS-3GB-S.R0048-AV2.0 | 2.0 | TTC Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0048-av20.pdf | + +#### 10.4.32.3 S.R0048-A Version 3.0 3G Mobile Equipment Identifier (MEID) Stage 1 (23 September 2004) + +The objective of this document is to define and standardize the structure of the 3G Mobile Equipment Identifier. To facilitate mobile equipment identification and reduce the need to rely on ESNs to track mobiles, the need for a new identifier is required. The Mobile Equipment Identifier (MEID) is proposed as a means to achieve these goals. Additionally, as global roaming and harmonization between 3G technologies becomes a reality, the need for a universal mobile equipment identifier is needed. The MEID is meant to address these issues. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0048-A | 3.0 | Approved | 09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0048-A V3.0 | 3.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0048-A v3.0.zip | +| TTC | TS-3GB-S.R0048-AV3.0 | 3.0 | TTC Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0048-av30.pdf | + +#### 10.4.32.4 S.R0048-A Version 4.0 3G Mobile Equipment Identifier (MEID) Stage 1 (23 June 2005) + +The objective of this document is to define and standardize the structure of the 3G mobile equipment identifier. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0048-A | 4.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0048-A V4.0 | 4.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0048-A v4.0.zip | +| TTC | TS-3GB-S.R0048-A V4.0 | 4.0 | TTC Published | 03-03-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0048-av40.pdf | + +#### 10.4.33 S.R0051 Version 1.0 Enhanced Message Service (EMS) Stage 1 Description (25 July 2001) + +This document specifies the system requirements for enhanced message service (EMS). + +The objective is to define and to standardize the functionality of this capability that can be incorporated into the operation of cdma2000-based wireless telecommunication networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0051 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAE.3G-S.R0051-0 V.1.0 | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/imt2000/TTAE.3G-S_R0051 v1.0.zip | +| TTC | TS-3GB-S.R0051-0v1.0 | 1.0 | TTC Published | 28-11-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0051-0v10.pdf | + +#### 10.4.34 S.R0052-0 Version 1.0 System Release Guide for the Release (ALPHA) of the cdma2000 System Specifications (15 January 2004) + +This document is re-numbered as SC.R2003-002 v1.0. + +#### 10.4.35 S.S0053 Version 1.0 Common Cryptographic Algorithms (21 January 2002) + +This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mobile station authentication, subscriber message encryption, and encryption key and subscriber voice privacy key generation within wireless equipment. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | STD-T64-S.S0053-0 v1.0 | 1.0 | ARIB Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_STD-T64-S.S0053-0_V1.0.PDF | +| TIA | (none) | | | | | +| TTA | TTAE.3G-S.S0053 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/imt2000/TTAE.3G-S.S0053-0v1.0.pdf | + +#### 10.4.36 S.S0054 Version 1.0 Interface Specification for Common Cryptographic Algorithms (21 January 2002) + +This document describes the interfaces to cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mobile station authentication, subscriber message encryption, and encryption key and subscriber voice privacy key generation within wireless equipment. The procedures are described in detail in common cryptographic algorithms. + +The purpose of this specification is to describe the cryptographic functions without revealing the technical details that are subject to export controls under regional laws. It is intended that developers of 3GPP2 specifications for systems using these cryptographic functions use the information in this document in standards that are not subject to export restrictions. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | STD-T64-S.S0054-0 v1.0 | 1.0 | ARIB Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_STD-T64-S.S0054-0_V1.0.PDF | +| TIA | (none) | | | | | +| TTA | TTAE.3G-S.S0054 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/imt2000/TTAE.3G-S.S0054-0v1.0.pdf | + +#### 10.4.37 S.S0055 Version 1.0 Enhanced Cryptographic Algorithms (21 January 2002) + +This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mutual authentication between mobile stations and base stations, subscriber message encryption, and key agreement within wireless equipment. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | STD-T64-S.S0055-0 v1.0 | 1.0 | ARIB Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_STD-T64-S.S0055-0_V1.0.PDF | +| TIA | TIA-946 | | Published | -- 06-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAE.3G-S.S0055 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/imt2000/TTAE.3G-S.S0055-0v1.0.pdf | + +#### 10.4.37.1 S.S0055-A Version 1.0 Enhanced Cryptographic Algorithms (-- November 2003) + +This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mutual authentication between mobile stations and base stations, subscriber message encryption, and key agreement within wireless equipment. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0055-A v1.0 | 1 | Approved | -- 11-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-946 | | Published | -- 06-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.S0055-A V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0055-A v1.0.zip | + +#### 10.4.37.2 S.S0055-A Version 2.0 Enhanced Cryptographic Algorithms (17 January 2005) + +This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mutual authentication between mobile stations and base stations, subscriber message encryption, and key agreement within wireless equipment. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | STD-T64-S.S0055-A v2.0 | 2.0 | ARIB Published | 29-09-2005 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/T64forQ.1742_5/ARIB_STD-T64-S.S0055-A_v2.0.pdf | +| CCSA | CCSA-TSD-MC-S.S0055-A | 2.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742_5 | +| TTA | TTAT.3G-S.S0055-A V2.0 | 2.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0055-A_v2.0.zip | + +### 10.4.37.3 S.S0055-A Version 3.0 Enhanced Cryptographic Algorithms (26 September 2005) + +This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mutual authentication between mobile stations and base stations, subscriber message encryption, and key agreement within wireless equipment. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0055-A | 3.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742_5 | +| TTA | TTAT.3G-S.S0055-A V3.0 | 3.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0055-A_v3.0.zip | + +### 10.4.38 S.R0057 Version 1.0 IP-based Service Architecture System Requirements (09 July 2002) + +This document specifies the system requirements for the "IP-based service architecture" from the perspective of the user(s) and/or the network operator for the support of IP multimedia applications. + +IP multimedia applications are supported by IP multimedia sessions that use IP connectivity bearers of the all-IP network. This document identifies stage 1 architectural requirements for the all-IP network to support the applications. + +The objective is to define and to standardize the "IP-based service architecture" that can be incorporated into the operations of cdma2000-based wireless telecommunication networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0057 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0057-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0057-0_v1.0.zip | +| TTC | TS-3GB-S.R0057-0v1.0 | 1.0 | TTC Published | 26-11-2002 | http://www.ttc.or.jp/imt2000/ts/tssr0057-0v10.pdf | + +### 10.4.39 S.R0058 Version 1.0 IP Multimedia Domain System Requirements (17 April 2003) + +This document specifies the system requirements for and operations of the IP multimedia domain (IP-MM domain) system. The IP multimedia domain system encompasses the mobile station, the access network and the core network. The various major functions and capabilities of the IP-MM domain system are discussed with a focus on the broad requirements that shall be met in providing those functions and capabilities. + +The requirements contained in this document apply to the complete IP multimedia domain system. Actual development of stage 2 and stage 3 work is expected to be done in a phased manner, with + +releases of the specifications containing successively more complete implementations of these requirements. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0058 | 1.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0058_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0058_v1.0.zip | + +#### **10.4.40 S.R0059 Version 1.0 Legacy MS Domain – Step 1 System Requirements (16 May 2002)** + +This document specifies the system requirements for and operations of the initial release (step 1) of the legacy MS domain (LMSD) of the all-IP network. Each of the functional entities of the LMSD is described with respect to functionality, interfaces and the roles it plays in the functioning of the network. + +The requirements contained in this document apply only to the initial step of the LMSD. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0059 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0059-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0059-0 v1.0.zip | + +#### **10.4.41 S.R0060 Version 1.0 Removable User Identity Module (R-UIM)/Mobile Equipment (ME) Interface Testing Stage 1 Description (14 March 2002)** + +This document specifies the product conformance objectives to be met by the removable user identity module (R-UIM)/mobile equipment (ME) interface test specification. The overall objective of this activity is the development of an industry standard compliance test specification, which can be employed to ensure that R-UIM-equipped handsets properly interface with various vendor-provided R-UIM cards. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | TR-T13-S.R0060-0 v1.0 | 1.0 | ARIB Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_TR-T13-S.R0060-0_V1.0.PDF | +| CCSA | CWTS-MC-S.R0060 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0060-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0060-0 v1.0.zip | + +#### **10.4.42 S.R0061 Version 1.0 Wireless Immediate Messaging Stage 1 Requirements (25 October 2002)** + +This document specifies the requirements for and operations of the immediate messaging feature from the perspective of the user(s) and/or the system operator. Immediate messaging (IM) is one of the most popular services on the Internet because of its near real-time, interactive nature. IM, using presence information, allows users to determine when their friends are online and communicate with them in near real-time. + +The objective is to define and to standardize the functionality of this feature/service that can be incorporated into the operations of 3GPP2-based wireless telecommunication networks. This + +document makes extensive use of the Internet terminology to ensure alignment with immediate messaging service description and behaviour in Internet recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0061 | 1.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0061-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0061-0_v1.0.zip | + +#### 10.4.43 S.R0062 Version 1.0 Presence for Wireless Systems Stage 1 Requirements (30 October 2002) + +This document defines stage 1 level requirements of the presence service from the perspective of the user and the system operator, so that it may be incorporated into cdma2000-based wireless networks. This document limits itself to presence service and does not delve into other applications that make use of presence, such as instant messaging. + +Presence is an attribute related to, but quite different from, mobility information and is a service that can be exploited to create additional services. The presence service enables presence information to be made available to other users or services. This stage 1 makes extensive use of Internet terminology to ensure alignment with the presence service description and behaviour in Internet recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0062 | 1.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0062-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0062-0_v1.0.zip | + +#### 10.4.44 S.R0064-0 Version 1.0 Multimedia Messaging Services (MMS) Stage 1 Requirements (30 October 2002) + +This document defines the stage 1 description of the non-real-time multimedia messaging service (MMS). MMS will allow users to send and receive messages exploiting the whole array of media types available today, e.g., text, images, audio and video, while also making it possible to support new content types as they become popular. A multimedia message (MM), as observed by the user, is a combination of one or more different media elements in a multimedia presentation that can be transferred without the need to be transferred in real-time. The multimedia messaging service shall be capable of supporting current and future multimedia types, and exploit the advances being made in the multimedia technology, with additional mobile requirements. Stage 1 is the set of requirements seen primarily from the subscriber's and service providers' points of view. It includes information of relevance to network operators, media content suppliers, service providers, and terminal and network manufacturers. + +It contains core requirements for the multimedia messaging service, sufficient to provide a complete service. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0064-0 | 1.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0064-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTA_T.3G-S.R0064-0_v1.0.zip | +| TTC | TS-3GB-S.R0064-0v1.0 | 1.0 | TTC Published | 14-02-2003 | http://www.ttc.or.jp/imt2000/ts/tssr0064-0v10.pdf | + +#### **10.4.45 S.R0065 Version 1.0 Fast Call Set-up System Requirements (15 April 2002)** + +This document specifies the system requirements for fast call set-up. This feature allows accelerated process in call setup (bearer resource assignment), which is particularly beneficial when a connection is returned from dormancy as a result of a packet arrival to the wireless network. The feature can be considered as falling into the category of standing requirements for network performance improvement. + +The objective is to define and to standardize the functionality of this capability that can be incorporated into the operations of cdma2000-based wireless telecommunication networks. + +The fast call set-up feature is a set of enhancements/mechanisms that reduce the latency involved in MS-terminated and MS-originated call set-up. + +Call-setup involves a set of signalling message exchanges between the mobile station, base station and the network in order to allocate resources and allow user communication to proceed. Each step of this process introduces delay that contributes to the end-to-end call set-up latency. Enhancements that reduce the delay in each step of this process and enhancements that streamline this process result in reduced call set-up latency which is beneficial to cdma2000 services. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0065 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0065-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0065-0_v1.0.zip | +| TTC | TS-3GB-S.R0065-0v1.0 | 1.0 | TTC Published | 27-08-2002 | http://www.ttc.or.jp/imt2000/ts/tsr0065-0v10.pdf | + +#### **10.4.46 S.R0066-0 Version 1.0 IP Based Location Services Stage 1 Requirements (17 April 2003)** + +This version of the Stage 1 supports location through IP in current packet data connections offered in cdma2000. SIP-based services in the all-IP domain (MMD), such as VoIP, are not assumed to be supported. Thus deployment of IP-Based Location Services will be possible prior to a full standardization and deployment of MMD. By the same token, there is no concept of an "emergency call" in the current packet data domain. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0066-0 | 1.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TIA | TIA-1020 | 1.0 | Approved | -- 04-2003 | http://www.tiaonline.org/standards/catelog/search.cfm | +| TTA | TTAT.3G-S.R0066-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0066-0_v1.0.zip | + +#### **10.4.47 S.R0068 Version 1.0 Link Layer Assisted Robust Header Compression Stage 1 Requirements (11 June 2002)** + +This document specifies the requirements for and operations of the link layer assisted header compression (LLA HC) from the perspective of the user and the system operator. + +The objective is to define and to standardize the functionality of this feature that can be incorporated into the operations of cdma2000-based wireless telecommunication networks. + +The scope of this feature is in support of QoS-enabled packet data service. This feature may also be used to support the all-IP multimedia domain, although all-IP is not the only application. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0068 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0068-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0068-0 v1.0.zip | +| TTC | TS-3GB-S.R0068-0v1.0 | 1.0 | TTC Published | 26-11-2002 | http://www.ttc.or.jp/imt2000/ts/tssr0068-0v10.pdf | + +#### **10.4.48 S.R0069 Version 1.0 Header Stripping and Generation Stage 1 Requirements (15 March 2002)** + +This document specifies the requirements for and operations of the header stripping and generation feature from the perspective of the user and the system operator. + +The objective is to define and to standardize the functionality of this feature that can be incorporated into the operations of cdma2000-based wireless telecommunication networks. + +The scope of this feature is in support of QoS-enabled packet data service. This feature may also be used to support the all-IP multimedia domain, although all-IP is not the only application. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0069 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0069-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0069-0 v1.0.zip | + +#### **10.4.49 S.R0070 Version 1.0 Work Item, Stage 1 and System Requirements Process Guidelines (16 May 2002)** + +The 3GPP2 document is superseded by SC.R1003-0 v1.0 + +#### **10.4.50 S.R0071 Version 1.0 Legacy System Packet Data Surveillance Requirements Stage 1 Requirements (18 April 2002)** + +The 3GPP2 steering committee found that the packet data surveillance feature (also known as packet data intercept, legal surveillance, lawful surveillance, or electronic surveillance) was regional in nature and should be left to the appropriate SDOs to develop, with 3GPP2 consulting as requested. + +This document serves as a pointer to the appropriate standards development organization (SDO) documents for packet data surveillance (PDS) for 3GPP2 all-IP systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0071 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0071-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0071-0 v1.0.zip | + +#### **10.4.51 S.R0072 Version 1.0 All IP Packet Data Surveillance Requirements Stage 1 Requirements (18 April 2002)** + +The 3GPP2 steering committee found that the packet data surveillance feature (also known as packet data intercept, legal surveillance, lawful surveillance, or electronic surveillance) was + +regional in nature and should be left to the appropriate SDOs to develop, with 3GPP2 consulting as requested. + +This document serves as a pointer to the appropriate standards development organization (SDO) documents for packet data surveillance (PDS) for 3GPP2 all-IP systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0072 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0072-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0072-0 v1.0.zip | + +#### **10.4.52 S.R0073 Version 1.0 Internet Over-the-Air Handset Configuration Management (IOTA) Stage 1 (11 July 2002)** + +This document specifies the requirements for and operation of Internet-based over-the-air handset configuration management (IOTA HCM) from the perspective of the users and system operators. + +The objective of this document is to define the requirements of this feature for incorporation into the operations of cdma2000-based wireless telecommunication systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CWTS-MC-S.R0073 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC | +| TTA | TTAT.3G-S.R0073-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0073-0 v1.0.zip | +| TTC | TS-3GB-S.R0073-0v1.0 | 1.0 | TTC Published | 26-11-2002 | http://www.ttc.or.jp/imt2000/ts/tssr0073-0v10.pdf | + +#### **10.4.53 S.R0074 Version 1.0 File Format for Multimedia Services (FFMS) Stage 1 Requirements (17 April 2003)** + +This document specifies the requirements for the file format for multimedia services (FFMS) feature from the perspective of the user(s) and/or the system operator. The objective is to define and to standardize the file that can be used for interchanging multimedia data in general multimedia services including the multimedia messaging services and the multimedia streaming services. Multimedia data will be stored in a single file. Employing a common file format also enables combined services. For example, a multimedia message is sent to and stored in a multimedia streaming server, and then it is used for streaming to a multimedia streaming client terminal. This document does not specify how this file format is used in specific services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0074 | 1.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0074_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0074_v1.0.zip | + +#### **10.4.54 S.R0075-0 Version 1.0 Accounting and Auditing All-IP System Requirements (17 April 2003)** + +This document specifies the system requirements for accounting and auditing in the all-IP network architecture model (NAM – S.R0037-0). The AAA is the primary functional entity with respect to the accounting and auditing functionality, interfaces, and the role it plays in the support of facilities and services message accounting in the network. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0075-0 | 1.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0075-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0075-0_v1.0.zip | + +#### 10.4.55 S.S0078-0 Version 1.0 Common Security Algorithms (12 December 2002) + +This document defines detailed cryptographic procedures for common security algorithms in 3GPP2. The procedures include authentication algorithms and privacy algorithms that are intended to satisfy the export restriction requirements of 3GPP2 organizational partners' host countries. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | STD-T64-S.S0078-0 v1.0 | 1.0 | ARIB Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_STD-T64-S.S0078-0_V1.0.PDF | +| CCSA | CCSA-TSD-MC-S.S0078-0 | 1.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.S0078-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0078-0_v1.0.zip | + +#### 10.4.55.1 S.S0078-A Version 1.0 Common Security Algorithms (13 December 2004) + +This document defines detailed cryptographic procedures for common security algorithms in 3GPP2. The procedures include authentication algorithms and privacy algorithms that are intended to satisfy the export restriction requirements of 3GPP2 organizational partners' host countries. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0078-A | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0078-A v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0078-A_v1.0.zip | + +#### 10.4.55.2 S.S0078-A Version 2.0 Common Security Algorithms (17 January 2005) + +This document defines detailed cryptographic procedures for common security algorithms in 3GPP2. The procedures include authentication algorithms and privacy algorithms that are intended to satisfy the export restriction requirements of 3GPP2 organizational partners' host countries. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | STD-T64-S.S0078-A v2.0 | 2.0 | ARIB Published | 29-09-2005 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/T64forQ.1742_5/ARIB_STD-T64-S.S0078-A_v2_0.pdf | +| CCSA | CCSA-TSD-MC-S.S0078-A | 2.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0078-A v2.0 | 2.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0078-A_v2.0.zip | + +### 10.4.55.3 S.S0078-A Version 3.0 Common Security Algorithms (26 September 2005) + +This document defines detailed cryptographic procedures for common security algorithms in 3GPP2. The procedures include authentication algorithms and privacy algorithms that are intended to satisfy the export restriction requirements of 3GPP2 organizational partners' host countries. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0078-A | 3.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.S0078-A v3.0 | 3.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0078-A v3.0.zip | + +### 10.4.56 S.R0079-0 Version 1.0 Support for End-to-End QoS Stage 1 Requirements (13 May 2004) + +This document describes the requirements necessary to support end-to-end (E2E) QoS in the cdma2000 wireless IP network. The requirements are based on leveraging and extending, where applicable, the standard IETF protocols for QoS. The proposed functionality described by the requirements include the use of int-serv, diff-serv, int-serv to diff-serv interworking, network policy and subscriber profile, network provisioning and link layer to upper layer QoS adaptation. The document also specifies the requirements for the cdma2000 radio link QoS. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0079-0 v1.0 | 1 | Approved | 13-05-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0079-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0079-0 v1.0.zip | +| TTC | TS-3GB-S.R0079-0V1.0 | 1.0 | TTC Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tsr0079-0v10.pdf | + +### 10.4.56.1 S.R0079-A Version 1.0 Support for End-to-End QoS Stage 1 Requirements (29 June 2006) + +This document describes the requirements necessary to support end-to-end (E2E) QoS in the cdma2000 wireless IP network. The requirements are based on leveraging and extending, where applicable, the standard IETF protocols for QoS. The proposed functionality described by the requirements include the use of int-serv, diff-serv, int-serv to diff-serv interworking, network policy and subscriber profile, network provisioning and link layer to upper layer QoS adaptation. The document also specifies the requirements for the cdma2000 radio link QoS. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.R0079-A v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0079-A V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0079-A v1.0.zip | +| TTC | TS-3GB-S.R0079-AV1.0 | 1.0 | TTC Published | 25-08-2006 | http://www.ttc.or.jp/imt2000/ts/tsr0079-av10.pdf | + +#### 10.4.57 S.R0080-0 Version 1.0 cdma2000 Wideband Speech Codec Stage 1 Requirements (20 February 2003) + +Wideband speech and audio coding has been gaining popularity in recent years. The emergence of the third generation cellular systems as well as increasing public demand for applications such as wireless multimedia, voice-over-IP, videophone, ISDN teleconferencing systems, multipoint interactive audiovisual communication and audio streaming require improved voice quality and intelligibility. Multimedia services are among the main deliverables of 3G wireless communications. This implies the use of high quality audio and speech in multimedia content. Even in 3G voice applications, the introduction of wideband speech would be an important step for CDMA service providers to deliver speech quality beyond the traditional limits of wireline communication systems. + +This document describes the cdma2000 wideband speech codec stage 1 requirements. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ARIB | TR-T13-S.R0080-0v1.0 | 1.0 | ARIB Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_TR-T13-S.R0080-0_v1.pdf | +| CCSA | CCSA-TSD-MC-S.R0080-0 | 1.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TTA | TTAT.3G-S.R0080-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0080-0_v1.0.zip | + +#### 10.4.58 S.R0082 Version 1.0 Enhanced Packet Data Air Interface Security (22 August 2003) + +This document defines requirements for the cdma2000 air interface to support data subscriber authentication (DSA) and data privacy (DP) for packet data services. DSA provides enhanced security in authentication and DP provides enhanced privacy of user data. DSA provides mutual authentication between the access terminal and the serving access network. DP provides encryption to prevent signalling and user traffic from unauthorized disclosure, and to prevent hijacking of user data channels. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0082 v1.0 | 1 | Approved | 22-08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0082 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0082_v1.0.zip | +| TTC | TS-3GB-S.R0082-0V1.0 | 1.0 | TTC Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tssr0082-0v10.pdf | + +#### 10.4.59 S.S0083-A Version 1.0 Broadcast-Multicast Service Security Framework (26 August 2004) + +This document defines the security framework for the broadcast-multicast services (BCMCS). The security framework provides a logical description of the security information, functions and protocols for BCMCS. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0083-A | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-1053 | | Published | -- 09-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.S0083-A V1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0083-A v1.0.zip | +| TTC | TS-3GB-S.S0083-AV1.0 | 1.0 | TTC Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/ts0083-av10.pdf | + +#### 10.4.60 S.R0084-0 Version 2.0 Prepaid Packet Data Service in cdma2000 Wireless IP Network, Stage 1 Requirements (18 September 2003) + +Prepaid service allows the subscriber to pay for packet data services prior to usage. A prepaid subscriber establishes an account with the service provider to access packet data services in home and roaming networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0084-0v2.0 | 1 | Approved | 18-09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0084-0 V2.0 | 2.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0084-0 v2.0.zip | +| TTC | TS-3GB-S.R0084-0V2.0 | 2.0 | TTC Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/ts0084-0v20.pdf | + +#### 10.4.61 S.R0086-A Version 1.0 IMS Security Framework (10 June 2004) + +This document addresses the access and network security for IP-based services. The scope of this technical specification is to specify the security features and mechanisms for secure access to the IM subsystem (IMS) for the 3G mobile telecommunication system. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0086-Av1.0 | 1 | Approved | 10-06-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0086-A V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0086-A v1.0.zip | +| TTC | TS-3GB-S.R0086-AV1.0 | 1.0 | TTC Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/ts0086-av10.pdf | + +##### 10.4.61.1 S.S0086-B Version 1.0 IMS Security Framework (08 December 2005) + +This document addresses the access and network security for IP-based services. The scope of this technical specification is to specify the security features and mechanisms for secure access to the IM subsystem (IMS) for the 3G mobile telecommunication system. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0086-B | 1 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-1091 | | Published | -- 12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-S.S0086-B V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0086-B v1.0.zip | +| TTC | S.S0086-B V1.0 | 1.0 | TTC Published | 03-03-2006 | http://www.ttc.or.jp/imt2000/ts/ts0086-bv10.pdf | + +### 10.4.62 S.R0087-0 Version 1.0 3GPP2 – WLAN Interworking Stage 1 Requirements (22 July 2004) + +This document describes requirements of interworking between 3GPP2 systems and wireless local area networks (WLANs). The intent of 3GPP2-WLAN interworking is to extend 3GPP2 packet data services and/or capabilities to the WLAN environment. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0087-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0087-0 v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0087-0_v1.0.zip | +| TTC | TS-3GB-S.R0087-0V1.0 | 1.0 | TTC Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0087-0v10.pdf | + +### 10.4.62.1 S.R0087-A Version 1.0 cdma2000 – WLAN Interworking Stage 1 Requirements (23 February 2006) + +This document describes requirements of interworking between cdma2000® systems and wireless local area networks (WLANs). The intent of cdma2000-WLAN is to extend cdma2000® packet data and multimedia services and/or capabilities to the WLAN environment, and to support the handoff of voice calls between WLAN and cdma2000 1x circuit-switched (CS) environments. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.R0087-A v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0087-A v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0087-A_v1.0.zip | +| TTC | TS-3GB-S.R0087-AV1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0087-av10.pdf | + +### 10.4.63 S.R0090-0 Version 1.0 Network Initiated Data Session (NIDS) Stage 1 Requirements (10 June 2004) + +This document defines the requirements for providing the network initiated data session (NIDS) capability. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0090-0 v1.0 | 1 | Approved | 10-06-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0090-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0090-0_v1.0.zip | +| TTC | TS-3GB-S.R0090-0V1.0 | 1.0 | TTC Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0090-0v10.pdf | + +### 10.4.64 S.R0092-0 Version 1.0 Legacy MS Domain Step 2 System Requirements (18 March 2004) + +This document specifies the system requirements for and operations of the second release (step 2) of the legacy MS domain (LMSD) of the all-IP network. Each of the functional entities of the LMSD is described with respect to functionality, interfaces, and the roles it plays in the functioning of the network. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0092-0 v1.0 | 1 | Approved | 18-03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0092-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0092-0 v1.0.zip | +| TTC | TS-3GB-S.R0092-0V1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsrr0092-0v10.pdf | + +#### **10.4.65 S.S0093-0 Version 1.0 cdma2000 Network Performance Measurement Types (11 December 2003)** + +This document defines the performance measurement types applicable to CDMA and cdma2000® systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0093-0 v1.0 | 1 | Approved | 11-12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0093-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0093-0 v1.0.zip | +| TTC | TS-3GB-S.S0093-0V1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsrr0093-0v10.pdf | + +#### **10.4.65.1 S.S0093-0 Version 2.0 cdma2000 Network Performance Measurement Types Revision: 0 (18 January 2006)** + +This document defines the performance measurement types applicable to CDMA and cdma2000® systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.S0093-0 v2.0 | 2.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0093-0 V2.0 | 2.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0093-0 v2.0.zip | +| TTC | TS-3GB-S.S0093-0V2.0 | 2.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsrr0093-0v20.pdf | + +#### **10.4.66 S.R0094-0 Version 1.0 Rm Interface Enhancements for cdma2000 System Requirements (17 February 2005)** + +This document specifies the system requirements for an enhanced Rm interface. The objective is to define and to standardize the functionality of this interface for incorporation into the operations of cdma2000® based wireless telecommunication networks. + +The Rm interface is between a mobile termination 2 (MT2) and a terminal equipment 2 (TE2). An MT2 is a cdma2000 network interface device, such as a hand-held phone. A TE2 is a general-purpose computer such as a laptop. The Rm Interface is currently specified in C.S0017 to support only a best-effort, point-to-point packet data link assuming the presence of an RS-232 physical layer. Enhancements are needed to support applications hosted on the TE2 that require quality of service (QoS) from the cdma2000 network, and to support a network-layer interface that can be re-used across many different physical layer technologies. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0094-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0094-0 V1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0094-0 v1.0.zip | +| TTC | TS-3GB-S.R0094-0V1.0 | 1.0 | TTC Published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tssr0094-0v10.pdf | + +#### **10.4.67 S.R0095-0 Version 1.0 Support for IP Multimedia Services identity Module (ISIM) on Universal Integrated Circuit Card (UICC) in 3GPP2 Systems Stage 1 Requirements (10 June 2004)** + +This document defines the enhancements required for the support of IMS-capable mobile stations equipped with universal integrated circuit card (UICC). This document specifies the requirements and operations for the support of ISIM on UICC. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0095-0-v1.0 | 1 | Approved | 10-06-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0095-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0095-0 v1.0.zip | +| TTC | TS-3GB-S.R0095-0V1.0 | 1.0 | TTC Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0095-0v10.pdf | + +#### **10.4.68 S.R0096-0 Version 1.0 Transcoder Free Operation Stage 1 Requirements (18 March 2004)** + +This document states that transcoder free operation (TrFO) is the transport of compressed speech, from legacy mobiles, in a packet transport network through the elimination of unnecessary coding and decoding of the signal by intermediate elements in the bearer path. Transcoders may be associated either with the RAN or media gateway (MGW). By transporting only the compressed speech, TrFO achieves bandwidth efficiencies in the bearer stream and reduces round-trip delays introduced by unnecessary transcoding. Also, TrFO may increase voice quality. TrFO is not applicable to VoIP. TrFO is a capability of the legacy MS domain. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0096-0 v1.0 | 1 | Approved | 18-03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0096-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0096-0 v1.0.zip | +| TTC | TS-3GB-S.R0096-0V1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0096-0v10.pdf | + +#### **10.4.69 S.R0103-0 Version 1.0 Network Firewall Configuration and Control (NFCC) – Stage 1 Requirements (09 December 2004)** + +This document specifies the system requirements and operation of the network firewall configuration and control (NFCC) feature, from both the perspective of the subscriber and the system operator. The objective is to define and to standardize the functionality of this feature to be incorporated into the operations of cdma2000®-based wireless telecommunication networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0103-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0103-0 V1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0103-0 v1.0.zip | +| TTC | TS-3GB-S.R0103-0V1.0 | 1.0 | TTC Published | 03-03-2005 | http://www.ttc.or.jp/imt2000/ts/tssr0103-0v10.pdf | + +#### **10.4.70 S.R0104-0 Version 1.0 HRPD Network Access Authentication for a Hybrid Access Terminal (HAT) with an R-UIM Used to Access Spread Spectrum Systems – Systems Requirements (21 October 2004)** + +A hybrid access terminal (referred to herein as a hybrid access terminal or HAT) is a device which can access both cdma2000® 1x and HRPD networks for packet data services. + +To access the cdma2000 1x network, a HAT that has an R-UIM uses R-UIM-supported CAVE-based authentication. To access the HRPD network, an optional network access authentication step may be required by the HRPD network. This optional step uses CHAP to exchange a challenge and response between the HAT and HRPD network. Currently, CHAP specifies that MD5 is used to compute the response. It is important to note that MD5 is not currently supported by all R-UIMs used to access a cdma2000 1x network. + +For an operator that deploys both cdma2000 1x and HRPD networks, there can be benefits to using common authentication credentials and authentication methods for accessing both networks. + +These requirements allow a properly configured HAT with an R-UIM to use CAVE-based authentication for access to both networks. These requirements specify the HAT authentication requirements and also the support required by the HRPD AN-AAA to authenticate such a HAT. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0104-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0104-0 V1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0104-0 v1.0.zip | +| TTC | TS-3GB-S.R0104-0V1.0 | 1.0 | TTC Published | 03-03-2005 | http://www.ttc.or.jp/imt2000/ts/tssr0104-0v10.pdf | + +#### **10.4.71 S.R0105-0 Version 1.0 Hot-lining Service (Packet Data) Stage 1 Requirements (08 December 2004)** + +This document specifies the system requirements for hot-lining for packet data service. The objective is to define and to standardize the functionality of this capability that can be incorporated into the operations of cdma2000®-based wireless IP networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0105-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0105-0 V1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0105-0 v1.0.zip | +| TTC | TS-3GB-S.R0105-0V1.0 | 1.0 | TTC Published | 03-03-2005 | http://www.ttc.or.jp/imt2000/ts/tsr0105-0v10.pdf | + +#### **10.4.72 S.R0106-0 Version 1.0 Packet-Switched Video Telephony Stage 1 (21 July 2005)** + +This document defines the functional characteristics and the requirements of the packet-switched video telephony (VT) services, sometimes also referred to as multimedia conversational services (MCS). Video telephony is defined as one-to-one video/speech communication capability. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0106-0 | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0106-0 V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0106-0 v1.0.zip | +| TTC | S.R0106-0 V1.0 | 1.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsr0106-0v10.pdf | + +#### **10.4.73 S.R0108-0 Version 1.0 HRPD-cdma2000 1x Interoperability for Voice and Data System Requirements (23 February 2006)** + +This document defines the system requirements for HRPD-cdma2000 1x interoperability for voice and data. The cellular network includes multimedia domain (MMD), legacy mobile station domain (LMSD) support, and HRPD/cdma2000 1x radio access networks (RANs) for the delivery of voice, video and data services. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.R0108-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0108-0 V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0108-0 v1.0.zip | +| TTC | TS-3GB-S.R0108-0V1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsr0108-0v10.pdf | + +#### **10.4.74 S.S0109-0 Version 1.0 Generic Bootstrapping Architecture (GBA) Framework (30 March 2006)** + +This document describes the security features and a mechanism to bootstrap keys for application security. The scope of this specification includes a generic bootstrapping function, an architecture overview and the detailed procedure how to bootstrap the credential. The specification also describes a mechanism, called GBA\_U, to bootstrap keys inside the (R-)UIM as well as keys in the ME. GBA\_U requires GBA support in the (R-)UIM, but provides enhanced security by storing certain derived keys on the (R-)UIM. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0109-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0109-0 V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0109-0 v1.0.zip | +| TTC | TS-3GB-S.S0109-0V1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0109-0v10.pdf | + +#### **10.4.75 S.S0110-0 Version 1.0 IP-Based Location Services Security Framework (23 February 2006)** + +This document defines the security framework for the IP-based location services. The security framework provides a logical description of the security information, functions and protocols for IP-based location services. The architectural design of the network that supports these functions is outside the scope of this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0110-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0110-0 V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0110-0 v1.0.zip | +| TTC | TS-3GB-S.S0110-0V1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0110-0v10.pdf | + +#### **10.4.76 S.R0111-0 Version 1.0 Expanded R-UIIM Identifier (26 October 2005)** + +An expanded R-UIIM identifier (EUIIM-ID) solution is needed in time to address issues associated with the impending exhaustion of the existing 32-bit UIM\_ID/ESN numbering space in CDMA networks. The purpose of introducing a new identifier is to define a larger numbering space, and also set the stage for moving away from the functions such as authentication and reverse long code mask generation. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0111-0 | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0111-0 V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0111-0 v1.0.zip | +| TTC | S.R0111-0 V1.0 | 1.0 | TTC Published | 03-03-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0111-0v10.pdf | + +#### **10.4.77 S.R0112-0 Version 1.0 Generic Bootstrapping Architecture System Requirements (08 December 2005)** + +This specification contains the high level requirements for the generic bootstrapping architecture work. The aim of this work is to specify a general method of providing an application and a mobile with some shared keying material. The requirements on how the application and mobile use this shared keying material is outside the scope of this specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-S.R0112-0 | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-S.R0112-0 V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0112-0 v1.0.zip | +| TTC | S.R0112-0 V1.0 | 1.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tssr0112-0v10.pdf | + +#### **10.4.78 S.R0113-0 Version 1.0 cdma2000 Enhanced Packet Data Air Interface System – System Requirements Document (25 May 2006)** + +This document specifies the system requirements for the development of the cdma2000® enhanced packet data air interface (E-PDAI) system. E-PDAI is a part of cdma2000 evolution effort. This document is intended to be used to guide the formal technical development of the E-PDAI air interfaced system and applicable IOS support. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.R0113-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0113-0 V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0113-0 v1.0.zip | +| TTC | TS-3GB-S.R0113-0V1.0 | 1.0 | TTC Published | 25-8-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0113-0v10.pdf | + +#### **10.4.79 S.S0114-0 Version 1.0 Security Mechanisms using GBA (30 March 2006)** + +This document describes the profile of security mechanisms such that the mechanism can utilize keys that have been generated using the generic bootstrapping architecture (GBA). GBA is a method of providing keys in a generic manner based on the 3GPP2 authentication methods. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.S0114-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.S0114-0 V1.0 | 1.0 | Approved | 02-15-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0114-0 v1.0.zip | +| TTC | TS-3GB-S.S0114-0V1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0114-0v10.pdf | + +#### **10.4.80 S.R0115-0 Version 1.0 All-IP Network Emergency Call Support Stage 1 Requirements (14 September 2006)** + +This document specifies the system requirements for all-IP network emergency call support as described in [ITU-R M.1457-6]. With the introduction of VoIP in HRPD, WLAN, or other air interfaces, it is important to add support for emergency calls. The intent of this specification is to provide a general set of functionality with the flexibility needed to support variances in regional regulatory requirements. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.R0115-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0115-0 V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0115-0 v1.0.zip | +| TTC | TS-3GB-S.R0115-0V1.0 | 1.0 | TTC Published | 01-12-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0115-0v10.pdf | + +#### **10.4.81 S.R0117-0 Version 1.0 Multimedia Priority Service (MMPS) for MMD-based Networks – Stage 1 Requirements (29 June 2006)** + +The scope of this document is to define the requirements for multimedia priority service for MMD-based networks. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.R0117-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0117-0 V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0117-0 v1.0.zip | +| TTC | TS-3GB-S.R0117-0V1.0 | 1.0 | TTC Published | 25-08-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0117-0v10.pdf | + +#### **10.4.82 S.R0118-0 Version 1.0 Telephone Number Mapping (ENUM) Stage 1 Requirements (25 May 2006)** + +This document specifies the requirements for the development of a specification in support of Public ENUM. The requirements pertain to the content, format and meaning of information included in the ENUM NAPTR resource records associated with an E.164 number, the handling of this information by the Public ENUM name servers and the ENUM clients. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-S.R0118-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-S.R0118-0 V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0118-0 v1.0.zip | +| TTC | TS-3GB-S.R0118-0V1.0 | 1.0 | TTC Published | 25-08-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0118-0v10.pdf | + +#### **10.4.83 SC.R1003-0 Version 1.0 Work Item, Stage 1 and System Requirements Process Guidelines (16 May 2002)** + +This 3GPP2 document is renamed from S.R0070 version 1.0. This document is to provide uniform procedures and guidance for the development, completion, distribution and approval of work items, stage 1 and system requirements across all TSGs. + +| | Document No. | Version | Status | Issued date | Location | +|------|-----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-SC.R1003-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TS-3GB-SC.R1003-0v1.0 | 1.0 | TTC Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsscr1003-0v10.pdf | + +#### **10.4.84 SC.R2001-001 Version 1.0 3GPP2 System Capability Guide Release A (20 January 2000)** + +This document is the 3GPP2 system capability guide (SCG) for 3GPP2 wireless telecommunication systems. It is developed and maintained under the auspices of 3GPP2 TSG-S, the TSG for services and systems aspects for 3GPP2. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-SC.R2001-001 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-SC.R2001-001 v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-SC.R2001-001 v1.0.zip | + +#### **10.4.85 SC.R2002-001 Version 1.0 3 GPP2 System Capability Guide Release B (14 June 2001)** + +This document is the 3GPP2 System Capability Guide (SCG) for 3GPP2 wireless telecommunication systems. It is developed and maintained under the auspices of 3GPP2 TSG-S, the TSG for services and systems aspects for 3GPP2. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-SC.R2002-001 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-SC.R2002-001 v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-SC.R2002-001 v1.0.zip | + +#### **10.4.86 SC.R2003-002 Version 1.0 System Release Guide for the Release (Alpha) of the cdma2000 System Specifications (15 January 2004)** + +This 3GPP2 document is renamed from S.R0052-0 version 1.0. This document is the system release guide (SRG) for the 3GPP2 wireless telecommunication system. It is developed and maintained under the auspices of 3GPP2 TSG-S, the TSG for services and systems aspects for 3GPP2. The objective of this document is to provide an informative overview for and reference to the release (Alpha) of the 3GPP2 wireless telecommunication system (cdma2000) capabilities, features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|---------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-SC.R2003-002 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-SC.R2003-002 V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-SC.R2003-002 v1.0.zip | +| TTC | TS-3GB-SC.R2003-002-0V1.0 | 1.0 | TTC Published | 08-25-2006 | http://www.ttc.or.jp/imt2000/ts/tsscr2003-002-0v10.pdf | + +### **10.5 Core network specifications** + +#### **10.5.1 X.S0002-0 Version 1.0 TIA/EIA-41-D Location Services Enhancements (-- March 2004)** + +This document presents a recommended plan for the implementation of location services enhancements for use in the wireless radiotelephone service. The purpose of this document is to specify the intersystem operations that enable a wireless system to provide enhanced location services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0002-0 v1.0 | | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-881 | | Published | -- 03-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0002-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0002-0 v1.0.zip | +| TTC | TS-3GB-X.S0002-0V1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0002-0v10.pdf | + +### 10.5.1.1 X.S0002-0 Version 2.0 MAP Location Services Enhancements (-- May 2006) + +This document presents a recommended plan for the implementation of location services enhancements for use in the wireless radiotelephone service. The purpose of this document is to specify the intersystem operations that enable a wireless system to provide enhanced location services. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0002-0 v2.0 | 2.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0002-0 V2.0 | 2.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0002-0 v2.0.zip | +| TTC | TS-3GB-X.S0002-0V2.0 | 2.0 | TTC Published | 25-08-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0002-0v20.pdf | + +### 10.5.2 X.S0003-0 Version 1.0 One-Way Roaming from X.S0004 to GSM (-- January 2005) + +This document provides recommended ANSI/TIA/EIA-41-D enhancements required to support TIA/EIA-41 subscription identification module (SIM) roaming one-way into GSM serving areas (without modification to the GSM serving network). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0003-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-868 | | Published | -- 01-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0003-0 V1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0003-0 v1.0.zip | +| TTC | TS-3GB-X.S0003-0V1.0 | 1.0 | TTC published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0003-0v10.pdf | + +### 10.5.3 X.S0004-000-E Version 1.0.0 Introduction to TIA-41 (-- March 2004) + +This document is to identify those cellular services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principle considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-000-E
v1.0.0 | 1 | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.000-E | | Published | -- 04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-000-E
V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-000-E_v1.0.0.zip | + +### 10.5.3.1 X.S0004-000-E Version 2.0.0 Introduction to TIA-41 (-- March 2004) + +The purpose of this standard is to identify those wireless services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principle considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-000-E | 2.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-X.S0004-000-E
V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-000-E_v2.0.zip | + +### 10.5.3.2 X.S0004-000-E Version 3.0.0 Introduction to MAP (-- October 2005) + +The purpose of this standard is to identify those wireless services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principle considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|-------------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-000-E | 3.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-X.S0004-000-E
V3.0 | 3.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-000-E_v3.0.zip | + +### 10.5.3.3 X.S0004-000-E Version 4.0 Mobile Application Part (MAP) – Introduction (-- May 2006) + +The purpose of this standard is to identify those wireless services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principle considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0004-000-E v4.0 | 4.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0004-000-E V4.0 | 4.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-000-E v4.0.zip | + +### 10.5.3.4 X.S0004-200-E Version 1.0 Mobile Application Part (MAP) – Intersystem Handoff (-- May 2006) + +This specification defines intersystem handoff by describing the information flows between functional entities which occur in a number of intersystem handoff scenarios. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0004-200-E v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0004-200-E V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-200-E v1.0.zip | + +### 10.5.3.5 X.S0004-290-E Version 1.0 Mobile Application Part (MAP) – Intersystem Handoff Annexes (-- May 2006) + +This annex is normative and is considered part of the specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0004-290-E v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0004-290-E V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-290-E v1.0.zip | + +### 10.5.3.6 X.S0004-400-E Version 1.0 Operations, Administration and Maintenance (-- July 2005) + +This document defines the intersystem operations, administration and maintenance (OA&M) information flows and procedures required for intersystem trunk maintenance. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-400-E | 1.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.400-E | | Published | -- 12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-400-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-400-E v1.0.zip | + +### 10.5.3.7 X.S0004-500-E Version 1.0.0 Introduction to Signaling Protocols (-- March 2004) + +This document introduces the signalling protocols for this standard. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-500-E v1.0.0 | 1 | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.500-E | | Published | -- 04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-500-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-500-E v1.0.0.zip | + +### **10.5.3.8 X.S0004-510-E Version 1.0.0 X.25 Transport Signaling Protocols (-- March 2004)** + +This document describes X.25 transport signalling protocols. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-510-E v1.0.0 | 1 | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.510-E | | Published | -- 04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-510-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-510-E v1.0.0.zip | + +### **10.5.3.9 X.S0004-511-E Version 1.0.0 ANS/SS7 Transport Signaling Protocols (-- March 2004)** + +This document describes ANS/SS7 transport signalling protocols. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-511-E v1.0.0 | 1 | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.511-E | | Published | -- 04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-511-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-511-E v1.0.0.zip | + +### **10.5.3.10 X.S0004-512-E Version 1.0.0 ITU-T SS7 Transport Signaling Protocols (-- March 2004)** + +This document describes ITU-T SS7 transport signalling protocols. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-512-E V1.0.0 | 1 | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.512-E | | Published | -- 04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-512-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-512-E v1.0.0.zip | + +### **10.5.3.11 X.S0004-520-E Version 1.0.0 TCAP Application Signaling Protocols (-- March 2004)** + +This document describes TCAP application signalling protocols. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-520-E v1.0.0 | 1 | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.520-E | | Published | -- 04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-520-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-520-E v1.0.0.zip | + +### **10.5.3.12 X.S0004-540-E Version 1.0.0 MAP Operations Signaling Protocols (-- March 2004)** + +This document supports systems conforming to air-interface technology, AMPS, NAMPS, TDMA, CDMA, including cdma2000. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-540-E V1.0.0 | 1 | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.540-E | | Published | -- 04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-540-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-540-E v1.0.0.zip | + +### 10.5.3.13 X.S0004-550-E Version 1.0.0 MAP Parameters Signaling Protocols (-- March 2004) + +This document supports systems conforming to air-interface technology, AMPS, NAMPS, TDMA, CDMA, including cdma2000. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-550-E V1.0.0 | 1 | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.550-E | | Published | -- 04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-550-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-550-E v1.0.0.zip | + +### 10.5.3.14 X.S0004-551-E Version 1.0.0 Parameter Types Signaling Protocols (-- March 2004) + +This document provides the definitions of the parameter types used in this standard. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-551-E V1.0.0 | 1 | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.551-E | | Published | -- 04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-551-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-551-E v1.0.0.zip | + +### 10.5.3.15 X.S0004-590-E Version 1.0.0 MAP Compatibility Signaling Protocols (-- March 2004) + +While this document outlines guidelines and rules, which will in the near term be beneficial to implementation of this standard, other activities which may impact these rules are in progress. As such, the remainder of the section "MAP compatibility guidelines and rules" may be subject to change and revision. This is to ensure that there is no long-term impediment to cellular radiotelecommunication networks to evolve and implement significant new functionality. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-590-E V1.0.0 | 1 | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.590-E | | Published | -- 04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-590-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-590-E v1.0.0.zip | + +### 10.5.3.16 X.S0004-600-E Version 1.0 Introduction to Procedures (-- July 2005) + +This document describes the signalling and call processing procedures required to perform automatic roaming features and services. The messages required to perform the automatic roaming + +are defined in Part 540. Conformance with this document shall mean that a system's externally visible behaviour is the same as the externally visible behaviour of the abstract system described here. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-600-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.600-E | | Published | -- 12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-600-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-600-E v1.0.zip | + +### 10.5.3.17 X.S0004-630-E Version 1.0 Basic Call Processing (-- July 2005) + +This document describes the signalling and call processing procedures required to perform automatic roaming features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-630-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.630-E | | Published | -- 12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-630-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-630-E v1.0.zip | + +### 10.5.3.18 X.S0004-640-E Version 1.0 Intersystem Procedures (-- July 2005) + +This document describes the signalling and call processing procedures required to perform automatic roaming features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-640-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.640-E | | Published | -- 12-2006 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-640-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-640-E v1.0.zip | + +### 10.5.3.19 X.S0004-641-E Version 1.0 Short Message Services (SMS) (-- July 2005) + +This document describes the signalling and call processing procedures required to perform automatic roaming features and services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-641-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.641-E | | Published | -- 12-2006 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-641-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-641-E v1.0.zip | + +### 10.5.3.20 X.S0004-642-E Version 1.0 Segmentation (-- July 2005) + +This section describes procedures to allow the transmission of messages, which may or may not require segmentation and reassembly (S&R). + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-642-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.642-E | | Published | -- 12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-642-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-642-E v1.0.zip | + +### 10.5.3.21 X.S0004-650-E Version 1.0 Common Voice Feature Procedures (-- July 2005) + +This section describes common voice feature procedures to implement individual features. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-650-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.650-E | | Published | -- 12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-650-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-650-E v1.0.zip | + +### 10.5.3.22 X.S0004-651-E Version 1.0 Voice Feature Procedures (-- July 2005) + +This section describes modular procedures to implement individual features. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-651-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.651-E | | Published | -- 12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-651-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-651-E v1.0.zip | + +### 10.5.3.23 X.S0004-660-E Version 1.0 Wireless Intelligent Network (WIN) Procedures (-- July 2005) + +In addition to the specific procedures described in this part of the standard, the functional entity call and service logic processing models provide a tool used by WIN architects to model a call and to understand and describe the distribution of functions between functional entities and functional entity relationships. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-660-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.660-E | | Published | -- 12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-660-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-660-E v1.0.zip | + +### 10.5.3.24 X.S0004-690-E Version 1.0 Operation Timer Values (-- July 2005) + +The following references provide a summary of the timers used for MAP operations. The timer values specified are default values only and should be optimized for actual operating environments. Some timers are locally defined and are not in this table (e.g., alerting timer, no answer timer, page response timer, maximum interaction timer, interdigit timer). + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-690-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-41.690-E | | Published | -- 12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-690-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-690-E v1.0.zip | + +### 10.5.3.25 X.S0004-691-E Version 1.0 Annexes (-- July 2005) + +This annex describes an algorithm for verifying the value of RANDC received from an MS. The algorithm used to verify RANDC is internal to an MSC and, as such, it does not constitute an intersystem operation. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-691-E | 1.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-X.S0004-691-E V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-691-E v1.0.zip | + +### 10.5.3.26 X.S0004-691-E Version 2.0 Annexes (-- September 2005) + +This annex describes an algorithm for verifying the value of RANDC received from an MS. The algorithm used to verify RANDC is internal to an MSC and, as such, it does not constitute an intersystem operation. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-691-E | 2.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-X.S0004-691-E V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-691-E v2.0.zip | + +### 10.5.3.27 X.S0004-700-E Version 1.0.0 Wireless Intelligent Networks (-- March 2004) + +This document part of TIA-41 defines the distributed functional plane (DFP) for the wireless intelligent network (WIN). + +Specifically, the scope of this part of the standard is: + +- 1) To define the WIN functional entities and the relationships applicable to WIN. +- 2) To specify a high-level model description of call control function (CCF) activities required to establish and maintain communication paths for users. +- 3) To specify a high-level model description of service switching function (SSF) activities required for interaction between the CCF and a session control function (SCF). +- 4) To specify WIN triggers and provide a high level model description of detection point processing. +- 5) To describe mobility management and radio access control functions in the context of WIN. +- 6) To illustrate how the WIN basic call state models interact with TIA-41 signalling. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-700-E V1.0.0 | 1 | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.700-E | | Published | -- 04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-700-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-700-E v1.0.0.zip | + +### 10.5.3.28 X.S0004-730-E Version 1.0.0 WIN Distributed Functional Model (-- March 2004) + +This document depicts the functional entities and relationships applicable to WIN. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-730-E V1.0.0 | 1 | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.730-E | | Published | -- 04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-730-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-730-E v1.0.0.zip | + +### 10.5.3.29 X.S0004-750-E Version 1.0.0 SSF/CCF Call and Service Logic Model (-- March 2004) + +This document describes WIN call and service logic processing in terms of call modelling and modelling of service logic processing. WIN call and service logic encompasses call and connection processing in the SSF/CCF, service logic execution in the SCF, and the use of supporting resources and data in the SRF and SDF, respectively. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-750-E V1.0.0 | 1 | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.750-E | | Published | -- 04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-750-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-750-E v1.0.0.zip | + +### 10.5.3.30 X.S0004-790-E Version 1.0.0 WIN Call Delivery (-- March 2004) + +These annexes describe how MS-to-MS call delivery can be modelled using the WIN basic call state models (BCSMs). The message sequences shown in the annex are as in TIA-41. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0004-790-E V1.0.0 | 1 | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-41.790-E | | Published | -- 04-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0004-790-E V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-790-E v1.0.0.zip | + +### 10.5.4 X.S0006-0 Version 1.0 Map Support of Authentication and Key Agreement (AKA) (-- October 2005) + +Enhanced subscriber authentication (ESA) uses 3GPP authentication and key agreement (AKA) procedures for mutual authentication of the MS and the network in the serving system. The successful execution of AKA results in the establishment of a security association (i.e., a set of + +security data) between the MS and the serving system. This enables a set of security services to be provided (e.g., data integrity of a signalling message, signalling information element encryption, user data encryption). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0006-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0006-0 V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0006-0 v1.0.zip | +| TTC | TS-3GB-X.S0006-0V1.0 | 1.0 | TTC Published | 03-03-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0006-0v10.pdf | + +### 10.5.5 X.S0008-0 Version 1.0 Support for the Mobile Equipment Identity (MEID) (-- June 2004) + +TIA-41 support for the mobile equipment identity (MEID). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0008-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-928-1 | | Published | -- 06-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0008-0 V1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0008-0 v1.0.zip | +| TTC | TS-3GB-X.S0008-0V1.0 | 1.0 | TTC published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0008-0v10.pdf | + +#### 10.5.5.1 X.S0008-0 Version 2.0 Map Support for the Mobile Equipment Identity (MEID) (-- October 2005) + +TIA-41 support for the mobile equipment identity (MEID). + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0008-0 | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-928-2[E] | | Published | -- 01-2006 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0008-0 V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0008-0 v2.0.zip | +| TTC | TS-3GB-X.S0008-0V2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0008-0v20.pdf | + +### 10.5.6 X.S0009-0 Version 1.0 Wireless Intelligent Network Support for Location Based Services (-- June 2004) + +The purpose of this document is to describe FAM, LBC, LBIS and ECR, and to specify the intersystem operations that enable a wireless system to provide these location-based services. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0009-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-843 | | Published | -- 08-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0009-0 V1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0009-0 v1.0.zip | +| TTC | TS-3GB-X.S0009-0V1.0 | 1.0 | TTC published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/sxss0009-0v10.pdf | + +### 10.5.7 X.S0010-A Version 1.0 Pre-Paid Charging Enhancements for Circuit-Switched Data and Short Message Services (05 January 2004) + +This document describes the additions and modifications to TIA/EIA/IS-826, wireless intelligent network capabilities for pre-paid charging, to support circuit-switched data and short message services. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0010-A v1.0 | 1 | Approved | 05-01-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-826-A | | Published | -- 12-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0010-A V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0010-A v1.0.zip | +| TTC | TS-3GB-X.S0010-AV1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/sxss0010-av10.pdf | + +### 10.5.8 X.S0011-001-C Version 1.0.0 cdma2000 Wireless IP Network Standard: Introduction (-- August 2003) + +This specification defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification defines the two methods for accessing public networks (Internet) and private networks (intranets): simple IP and mobile IP. It describes the required quality of service, security, mobility management and accounting capabilities needed to support both methods. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-001-C v1.0.0 | 1 | Approved | -- 08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C | | Published | -- 08-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0011-001-C V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-001-C v1.0.0.zip | +| TTC | TS-3GB-X.S0011-001-Cv1.0.0 | 1.0.0 | TTC published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/sxss0011-001-cv100.pdf | + +### 10.5.8.1 X.S0011-001-C Version 2.0 cdma2000 Wireless IP Network Standard: Introduction (-- July 2005) + +This specification defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification supports the services and architecture. This specification defines the two methods for accessing public networks (Internet) and private networks (intranets): simple IP and mobile IP. It describes the required quality of service, security, mobility management and accounting capabilities needed to support both methods. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-001-C | 2.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0011-001-C V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-001-C v2.0.zip | +| TTC | TS-3GB-X.S0011-001-Cv2.0 | 2.0 | TTC Published | 26-08-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-001-cv20.pdf | + +### 10.5.8.2 X.S0011-001-C Version 3.0 cdma2000 Wireless IP Network Standard: Introduction (-- October 2006) + +This specification defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification supports the services and architecture. This specification defines the two methods for accessing public networks (Internet) and private networks (intranets): simple IP and mobile IP. It describes the required quality of service, security, mobility management and accounting capabilities needed to support both methods. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-001-C v3.0 | 3.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-001-C V3.0 | 3.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-001-C v3.0.zip | +| TTC | TS-3GB-X.S0011-001-Cv3.0 | 3.0 | TTC Published | 23-02-2007 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-001-cv30.pdf | + +### 10.5.8.3 X.S0011-001-D Version 1.0 cdma2000 Wireless IP Network Standard: Introduction (-- February 2006) + +This specification defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification supports the services and architecture. This specification defines the two methods for accessing public networks (Internet) and private networks (intranets): simple IP and mobile IP. It describes the required quality of service, security, mobility management and accounting capabilities needed to support both methods. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-001-D v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-001-D V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-001-D v1.0.zip | +| TTC | TS-3GB-X.S0011-001-Dv1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-001-dv10.pdf | + +### 10.5.8.4 X.S0011-002-C Version 1.0.0 cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Access Services (-- August 2003) + +This document describes the required capabilities at the MS, the PDSN, the HA and the RADIUS servers to provide simple IPv4, simple IPv6 and mobile IPv4 access services over PPP. It describes the mechanisms of updating the DNS with the user's assigned IP address as described in the IP reachability service capability. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-002-C v1.0.0 | 1 | Approved | -- 08-03 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C | | Published | -- 08-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0011-002-C V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-002-C v1.0.0.zip | +| TTC | TS-3GB-X.S0011-002-Cv1.0.0 | 1.0.0 | TTC published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-002-cv100.pdf | + +#### **10.5.8.5 X.S0011-002-C Version 2.0 cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Services (-- July 2005)** + +This document describes the required capabilities at the MS, the PDSN, the HA and the RADIUS servers to provide simple IPv4, simple IPv6 and mobile IPv4 access services over PPP. It describes the mechanisms of updating the DNS with the user's assigned IP address as described in the IP reachability service capability. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-002-C | 2.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742_ | +| TTA | TTAT.3G-X.S0011-002-C V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-002-C v2.0.zip | +| TTC | TS-3GB-X.S0011-002-Cv2.0 | 2.0 | TTC Published | 26-08-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-002-cv20.pdf | + +#### **10.5.8.6 X.S0011-002-C Version 3.0 cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Services (-- October 2006)** + +This document describes the required capabilities at the MS, the PDSN, the HA and the RADIUS servers to provide Simple IPv4, simple IPv6 and mobile IPv4 access services over PPP. It describes the mechanisms of updating the DNS with the user's assigned IP address as described in the IP reachability service capability. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-002-C v3.0 | 3.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-002-C V3.0 | 3.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-002-C v3.0.zip | +| TTC | TS-3GB-X.S0011-002-Cv3.0 | 3.0 | TTC Published | 23-02-2007 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-002-cv30.pdf | + +#### **10.5.8.7 X.S0011-002-D Version 1.0 cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Access Services (-- February 2006)** + +This document describes the basic IP access services: simple IPv4/IPv6, MIP6 and MIP4 with home agent (HA) and/or dynamic home IP address assignment. It also addresses the security requirements between the wireless IP network nodes: PDSN, HA and RADIUS servers. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-002-D v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-002-D V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-002-D v1.0.zip | +| TTC | TS-3GB-X.S0011-002-Dv1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-002-dv10.pdf | + +### 10.5.8.8 X.S0011-003-C Version 1.0.0 cdma2000 Wireless IP Network Standard: Packet Data Mobility and Resource Management (-- August 2003) + +This document describes the mechanisms at the PDSN resulting from handoff of an MS from one BS/PCF to another BS/PCF, and which may result in changing the serving PDSN for the MS. This chapter describes an optional fast handoff capability, which is a low latency, low data loss handoff mechanism between PDSNs. Fast handoff mechanism delays re-negotiation of PPP until the MS becomes dormant at the Target PDSN. This document also describes resource management procedures at the PDSN and the HA that are used following an inter PDSN handoff or under other conditions that require release of resources. Furthermore, a procedure for provisioning the RAN with resource management parameters such as RN packet data inactivity timers is specified in this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-003-C v1.0.0 | 1 | Approved | -- 08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C | | Published | -- 08-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0011-003-C V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-003-C v1.0.0.zip | +| TTC | TS-3GB-X.S0011-003-Cv1.0.0 | 1.0.0 | TTC published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-003-cv100.pdf | + +### 10.5.8.9 X.S0011-003-C Version 2.0 cdma2000 Wireless IP Network Standard: Packet Data Mobility and Resource Management (-- July 2005) + +This document describes the mechanisms at the PDSN resulting from handoff of an MS from one BS/PCF to another BS/PCF, and which may result in changing the serving PDSN for the MS. This document describes an optional fast handoff capability, which is a low latency, low data loss handoff mechanism between PDSNs. Fast handoff mechanism delays re-negotiation of PPP until the MS becomes dormant at the Target PDSN. This document also describes resource management procedures at the PDSN and the HA that are used following an inter PDSN handoff or under other conditions that require release of resources. Furthermore, a procedure for provisioning the RAN with resource management parameters such as RN packet data inactivity timers is specified in this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-003-C | 2.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0011-003-C V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-003-C v2.0.zip | +| TTC | TS-3GB-X.S0011-003-Cv2.0 | 2.0 | TTC Published | 26-08-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-003-cv20.pdf | + +### 10.5.8.10 X.S0011-003-C Version 3.0 cdma2000 Wireless IP Network Standard: Packet Data Mobility and Resource Management (-- October 2006) + +This document describes the mechanisms at the PDSN resulting from handoff of an MS from one BS/PCF to another BS/PCF, and which may result in changing the serving PDSN for the MS. This document describes an optional fast handoff capability, which is a low latency, low data loss handoff mechanism between PDSNs. Fast handoff mechanism delays re-negotiation of PPP until the MS becomes dormant at the target PDSN. This document also describes resource management procedures at the PDSN and the HA that are used following an inter PDSN handoff or under other conditions that require release of resources. Furthermore, a procedure for provisioning the RAN with resource management parameters such as RN packet data inactivity timers is specified in this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-003-C v3.0 | 3.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-003-C V3.0 | 3.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-003-C v3.0.zip | +| TTC | TS-3GB-X.S0011-003-Cv3.0 | 3.0 | TTC Published | 23-02-2007 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-003-cv30.pdf | + +### 10.5.8.11 X.S0011-003-D Version 1.0 cdma2000 Wireless IP Network Standard: Data Mobility and Resource Management (-- February 2006) + +This document describes the mechanisms at the PDSN resulting from handoff of an MS from one BS/PCF to another BS/PCF, and which may result in changing the serving PDSN for the MS. This document describes an optional fast handoff capability, which is a low latency, low data loss handoff mechanism between PDSNs. Fast handoff mechanism delays re-negotiation of PPP until the MS becomes dormant at the target PDSN. This document also describes resource management procedures at the PDSN and the HA that are used following an inter PDSN handoff or under other conditions that require release of resources. Furthermore, a procedure for provisioning the RAN with resource management parameters such as RN packet data inactivity timers is specified in this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-003-D v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-003-D V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-003-D v1.0.zip | +| TTC | TS-3GB-X.S0011-003-Dv1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-003-dv10.pdf | + +### 10.5.8.12 X.S0011-004-C Version 1.0.0 cdma2000 Wireless IP Network Standard: Quality of Service and Header Reduction (-- August 2003) + +This document describes flow mapping/treatment mechanisms and protocol used when more than one service instance is established for the MS. It also describes two optional header reduction techniques that are specific to service instances of SO type 60 and 61, that may be established by the MS for applications that require a synchronous flow of 20-ms frames, such as VoIP application. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-004-C V1.0.0 | 1 | Approved | -- 08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C | | Published | -- 08-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0011-004-C V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-004-C v1.0.0.zip | +| TTC | TS-3GB-X.S0011-004-Cv1.0.0 | 1.0.0 | TTC published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-004-cv100.pdf | + +### 10.5.8.13 X.S0011-004-C Version 2.0 cdma2000 Wireless IP Network Standard: Quality of Service and Header Reduction (-- July 2005) + +This document describes flow mapping/treatment mechanisms and protocol used when more than one service instance is established for the MS. It also describes two optional header reduction techniques that are specific to service instances of SO type 60 and 61, that may be established by the MS for applications that require a synchronous flow of 20-ms frames, such as VoIP application. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-004-C | 2.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0011-004-C V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-004-C v2.0.zip | +| TTC | TS-3GB-X.S0011-004-Cv2.0 | 2.0 | TTC Published | 26-08-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-004-cv20.pdf | + +### 10.5.8.14 X.S0011-004-C Version 3.0 cdma2000 Wireless IP Network Standard: Quality of Service and Header Reduction (-- October 2006) + +This document describes flow mapping/treatment mechanisms and protocol used when more than one service instance is established for the MS. It also describes two optional header reduction techniques that are specific to service instances of SO type 60 and 61, that may be established by the MS for applications that require a synchronous flow of 20-ms frames, such as VoIP application. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-004-C v3.0 | 3.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-004-C V3.0 | 3.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-004-C v3.0.zip | +| TTC | TS-3GB-X.S0011-004-Cv3.0 | 3.0 | TTC Published | 23-02-2007 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-004-cv30.pdf | + +### 10.5.8.15 X.S0011-004-D Version 1.0 cdma2000 Wireless IP Network Standard: Quality of Service and Header Reduction (-- February 2006) + +This document describes flow mapping/treatment mechanisms and protocols used when more than one service connection is established between the MS and the PDSN. Furthermore, a signalling mechanism between the MS, the RAN and the PDSN is presented in this document to support QoS on a per application flow basis. It also describes two optional header reduction techniques that are specific to service instances of SO type 60 and 61, which may be established by the MS for applications that require a synchronous flow of 20-ms frames, such as VoIP application. This document also specifies the requirement and procedures for MS and PDSN to support SO type 67. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-004-D v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-004-D V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-004-D v1.0.zip | +| TTC | TS-3GB-X.S0011-004-Dv1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-004-dv10.pdf | + +### 10.5.8.16 X.S0011-005-C Version 1.0.0 cdma2000 Wireless IP Network Standard: Accounting Services and 3GPP2 RADIUS VSAs (-- August 2003) + +This document describes the off-line accounting procedures and the usage data records. It describes all the 3GPP2 VSAs used to support the capabilities described in this series of specifications X.S0011-001-C to X.S0011-006-C. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-005-C v1.0.0 | 1 | Approved | -- 08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C | | Published | -- 08-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0011-005-C V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-005-C v1.0.0.zip | +| TTC | TS-3GB-X.S0011-005-Cv1.0.0 | 1.0.0 | TTC Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-005-cv100.pdf | + +### 10.5.8.17 X.S0011-005-C Version 2.0 cdma2000 Wireless IP Network Standard: Accounting Services and 3GPP2 RADIUS VSAs (-- July 2005) + +This document describes the off-line accounting procedures and the usage data records. It describes all the 3GPP2 VSAs used to support the capabilities described in this series of specifications X.S0011-001-C to X.S0011-006-C. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-005-C | 2.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0011-005-C V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-005-C v2.0.zip | +| TTC | TS-3GB-X.S0011-005-Cv2.0 | 2.0 | TTC Published | 26-08-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-005-cv20.pdf | + +### 10.5.8.18 X.S0011-005-C Version 3.0 cdma2000 Wireless IP Network Standard: Accounting Services and 3GPP2 RADIUS VSAs (-- October 2006) + +This document describes the off-line accounting procedures and the usage data records. It describes all the 3GPP2 VSAs used to support the capabilities described in this series of specifications X.S0011-001-C to X.S0011-006-C. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-005-C v3.0 | 3.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-005-C V3.0 | 3.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-005-C v3.0.zip | +| TTC | TS-3GB-X.S0011-005-Cv3.0 | 3.0 | TTC Published | 23-02-2007 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-005-cv30.pdf | + +### 10.5.8.19 X.S0011-005-D Version 1.0 cdma2000 Wireless IP Network Standard: Accounting Services and 3GPP2 RADIUS VSAs (-- February 2006) + +This document describes the off-line accounting procedures and the usage data records. It describes all the 3GPP2 VSAs used to support the described capabilities. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-005-D v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-005-D V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-005-D v1.0.zip | +| TTC | TS-3GB-X.S0011-005-Dv1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-005-dv10.pdf | + +### 10.5.8.20 X.S0011-006-C Version 1.0.0 cdma2000 Wireless IP Network Standard: PrePaid Packet Data Service (-- August 2003) + +Support for prepaid packet data services is optional in this specification. The prepaid packet data service allows a user to purchase packet data service in advance based on volume or duration. In order to support prepaid packet data service the PDSN and/or the HA shall support the prepaid client (PPC) function and the prepaid server (PPS) function may be co-located with the home RADIUS server. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-006-C V1.0.0 | 1 | Approved | -- 08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-835-C | | Published | -- 08-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0011-006-C V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-006-C v1.0.0.zip | +| TTC | TS-3GB-X.S0011-006-Cv1.0.0 | 1.0.0 | TTC Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-006-cv100.pdf | + +### 10.5.8.21 X.S0011-006-C Version 2.0 cdma2000 Wireless IP Network Standard: PrePaid Packet Data Services (-- July 2005) + +Support for prepaid packet data services is optional in this specification. The prepaid packet data service allows a user to purchase packet data service in advance based on volume or duration. In order to support prepaid packet data service the PDSN and/or the HA shall support the prepaid client (PPC) function and the prepaid server (PPS) function may be co-located with the home RADIUS server. In this revision of the specification, the prepaid packet data service supports a set of capabilities as described in section 3 of the specification. Additional capabilities may be supported in future revisions of this specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0011-006-C | 2.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0011-006-C V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-006-C v2.0.zip | +| TTC | TS-3GB-X.S0011-006-Cv2.0 | 2.0 | TTC Published | 26-08-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-006-cv20.pdf | + +### **10.5.8.22 X.S0011-006-C Version 3.0 cdma2000 Wireless IP Network Standard: PrePaid Packet Data Services (-- October 2006)** + +Support for prepaid packet data services is optional in this specification. The prepaid packet data service allows a user to purchase packet data service in advance based on volume or duration. In order to support prepaid packet data service the PDSN and/or the HA shall support the prepaid client (PPC) function and the prepaid server (PPS) function may be co-located with the home RADIUS server. In this revision of the specification, the prepaid packet data service supports a set of capabilities as described in section 1. Additional capabilities may be supported in future revisions of this specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-006-C v3.0 | 3.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-006-C V3.0 | 3.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-006-C v3.0.zip | +| TTC | TS-3GB-X.S0011-006-Cv3.0 | 3.0 | TTC Published | 23-02-2007 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-006-cv30.pdf | + +### **10.5.8.23 X.S0011-006-D Version 1.0 cdma2000 Wireless IP Network Standard: PrePaid Packet Data Services (-- February 2006)** + +Support for prepaid packet data services is optional in this specification. The prepaid packet data service allows a user to purchase packet data service in advance based on volume or duration. In order to support prepaid packet data service the PDSN and/or the HA shall support the prepaid client (PPC) function and the prepaid server (PPS) function may be co-located with the home RADIUS server. In this revision of the specification, the PrePaid packet data service supports a set of capabilities as described in section 3. Additional capabilities may be supported in future revisions of this specification. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0011-006-D v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0011-006-D V1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-006-D v1.0.zip | +| TTC | TS-3GB-X.S0011-006-Dv1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-006-dv10.pdf | + +### **10.5.9 X.S0012-0 Version 2.0 Legacy MS Domain Step 1 (-- March 2004)** + +This recommendation supports the 3GPP2 all-IP step 1 evolution path by providing stage 1, 2 and 3 for the architecture identified. The legacy MS domain provides support for existing MSs in an IP core network environment. The legacy MS domain supports the features and capabilities provided in a legacy network in a manner transparent to the user. New features and capabilities supported by the IP core network may be made available to subscribers where they are supported by MS capabilities. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0012-0 v2.0 | 1 | Approved | -- 03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-872-A | | Published | -- 05-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0012-0 V2.0 | 2.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0012-0 v2.0.zip | +| TTC | TS-3GB-X.S0012-0v2.0 | 2.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0012-0v20.pdf | + +### 10.5.10 X.S0013-000-0 Version 1.0 All-IP Core Network Multimedia Domain Overview (-- December 2003) + +This document contains the introduction of the stage 1, stage 2, and stage 3 recommendations for the 3GPP2 all-IP multimedia domain. It includes an overview of the system elements and interfaces, and lists the series of documents that provide the complete specifications for the core network portions of the MMD. Not all MMD entities and interfaces may be covered by this version of this series of specifications. The specific entities and interfaces covered by a particular version are identified in each of the individual specifications. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-000-0 v1.0 | 1 | Approved | -- 12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.000 | | Published | -- 12-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0013-000-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-000-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-000-0v1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-000-0v10.pdf | + +### 10.5.10.1 X.S0013-000-0 Version 2.0 All-IP Core Network Multimedia Domain Overview (-- July 2005) + +The multimedia domain (MMD) is a CDMA-based wireless network providing third generation capabilities and based on IP protocols, elements and principles. This document provides an introduction to the core network elements and interfaces that make up a portion of the MMD. This document also introduces the series of documents that provide the complete specification of the core network interfaces and protocols that provide this part of the MMD capabilities. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-000-0 | 2.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742_ | +| TTA | TTAT.3G-X.S0013-000-0 V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-000-0 v2.0.zip | +| TTC | TS-3GB-X.S0013-000-0v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-000-0v20.pdf | + +### 10.5.10.2 X.S0013-000-A Version 1.0 All-IP Core Network Multimedia Domain Overview (-- November 2005) + +The multimedia domain (MMD) is a collection of core network entities providing third generation capabilities and based on IP protocols, elements and principles. This document provides an introduction to the core network elements and interfaces that make up a portion of the MMD. This document also introduces the series of documents that provide the complete specification of the core network interfaces and protocols that provide this part of the MMD capabilities. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-000-A | 1.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742_ | +| TTA | TTAT.3G-X.S0013-000-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-000-A v1.0.zip | + +### **10.5.10.3 X.S0013-002-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem – Stage 2 (-- December 2003)** + +This document defines stage 2 service description for the IP multimedia core network subsystem (IMS), which includes the elements necessary to support IP multimedia (IM) services in PLMNs and perhaps other networks. This document identifies the mechanisms to enable support for IP multimedia applications. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-002-0 v1.0 | 1 | Approved | -- 12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TIA-873.002 | | Published | -- 12-2003 | http://www.ttaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0013-002-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-002-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-002-0v1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-002-0v10.pdf | + +### **10.5.10.4 X.S0013-002-A Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem – Stage 2 (-- November 2005)** + +This document defines stage 2 service description for the IP multimedia core network subsystem (IMS), which includes the elements necessary to support IP multimedia (IM) services. ITU-T Rec. I.130 describes a three-stage method for characterization of telecommunication services, and ITU-T Rec. Q.65 defines stage 2 of the method. This document identifies the mechanisms to enable support for IP multimedia applications. In order to align IP multimedia applications wherever possible with non-IMS IP applications, the general approach is to adopt non-IMS specific IP-based solutions. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-002-A | 1.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742_ | +| TTA | TTAT.3G-X.S0013-002-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-002-A v1.0.zip | + +### **10.5.10.5 X.S0013-003-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia (IMS) Session Handling; IP Multimedia (IM) Call Model; Stage 2 (-- December 2003)** + +This document specifies the IP multimedia (IM) call model for handling of an IP multimedia session origination and termination for an IP multimedia subscriber. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-003-0 v1.0 | 1 | Approved | -- 12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.003 | | Published | -- 12-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0013-003-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-003-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-003-0v1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-003-0v10.pdf | + +### **10.5.10.6 X.S0013-003-0 Version 2.0 All-IP Core Network Multimedia Domain IP Multimedia (IMS) Session Handling; IP Multimedia (IM) Call Model; Stage 2 (-- July 2005)** + +This document specifies the IP multimedia (IM) call model for handling of an IP multimedia session origination and termination for an IP multimedia subscriber. This document includes interactions between an application server and IP multimedia sessions. The IP Multimedia (IM) Subsystem stage 2 and stage 3 for the IP multimedia call control based on SIP and SDP are specified in other documents. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-003-0 | 2.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-003-0 V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-003-0 v2.0.zip | +| TTC | TS-3GB-X.S0013-003-0v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-003-0v20.pdf | + +### **10.5.10.7 X.S0013-003-A Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia (IMS) Session Handling; IP Multimedia (IM) Call Model; Stage 2 (-- November 2005)** + +This document specifies the IP multimedia (IM) call model for handling of an IP multimedia session origination and termination for an IP multimedia subscriber. This document includes interactions between an application server and IP multimedia sessions. The IP multimedia (IM) subsystem stage 2 and stage 3 for the IP multimedia call control based on SIP and SDP are specified in other documents. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-003-A | 1.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-003-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-003-A v1.0.zip | + +### **10.5.10.8 X.S0013-004-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Call Control Protocol Based on SIP and SDP Stage 3 (-- December 2003)** + +This document defines a call control protocol for use in the IP multimedia (IM) core network (CN) subsystem based on the session initiation protocol (SIP), and the associated session description protocol (SDP). + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-004-0 v1.0 | 1 | Approved | -- 12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.004 | | Published | -- 12-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0013-004-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-004-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-004-0v1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-004-0v10.pdf | + +### **10.5.10.9 X.S0013-004-0 Version 2.0 All-IP Core Network Multimedia Domain IP Multimedia Call Control Protocol Based on SIP and SDP Stage 3 (-- July 2005)** + +This document defines a call control protocol for use in the IP multimedia (IM) core network (CN) subsystem based on the session initiation protocol (SIP), and the associated session description protocol (SDP). + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-004-0 | 2.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-004-0 V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-004-0 v2.0.zip | +| TTC | TS-3GB-X.S0013-004-0v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-004-0v20.pdf | + +### **10.5.10.10 X.S0013-004-A Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Call Control Protocol Based on SIP and SDP Stage 3 (-- November 2005)** + +This document defines a call control protocol for use in the IP multimedia (IM) core network (CN) subsystem based on the session initiation protocol (SIP), and the associated session description protocol (SDP). + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-004-A | 1.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-004-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-004-A v1.0.zip | + +### **10.5.10.11 X.S0013-005-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem Cx interface Signaling flows and Message Contents (-- December 2003)** + +This specification specifies the interactions between the home subscriber server (HSS) and the call session control functions (CSCF), referred to as the Cx interface. This document addresses the signalling flows for the Cx interface. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-005-0 v1.0 | 1 | Approved | -- 12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.005 | | Published | -- 12-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0013-005-0V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-005-0v1.0.zip | +| TTC | TS-3GB-X.S0013-005-0v1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-005-0v10.pdf | + +### **10.5.10.12 X.S0013-005-0 Version 2.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem Cx interface Signaling flows and Message Contents (-- July 2005)** + +This specification specifies the interactions between the home subscriber server (HHS) and the call session control functions (CSCF), referred to as the Cx interface. This document addresses the signalling flows for the Cx interface. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-005-0 | 2.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-005-0 V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-005-0 v2.0.zip | +| TTC | 3GB-X.S0013-005-0v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-005-0v20.pdf | + +### **10.5.10.13 X.S0013-005-A Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem Cx interface Signalling flows and Message Contents (-- November 2005)** + +This specification specifies the interactions between the home subscriber server (HHS) and the call session control functions (CSCF), referred to as the Cx interface. This document addresses the signalling flows for the Cx interface. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-005-A | 1.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-005-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-005-A v1.0.zip | + +### **10.5.10.14 X.S0013-006-0 Version 1.0 All-IP Core Network Multimedia Domain Cx Interface Based on the Diameter Protocol; Protocol Details (-- December 2003)** + +This document defines a transport protocol for use in the IP multimedia (IM) core network (CN) subsystem based on Diameter. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-006-0 v1.0 | 1 | Approved | -- 12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.006 | | Published | -- 12-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0013-006-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-006-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-006-0v1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-006-0v10.pdf | + +### 10.5.10.15 X.S0013-006-0 Version 2.0 All-IP Core Network Multimedia Domain Cx Interface Based on the Diameter Protocol; Protocol Details (-- July 2005) + +This document defines a transport protocol for use in the IP multimedia (IM) core network (CN) subsystem based on Diameter. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-006-0 | 2.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-006-0 V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-006-0 v2.0.zip | +| TTC | TS-3GB-X.S0013-006-0v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-006-0v20.pdf | + +### 10.5.10.16 X.S0013-006-A Version 1.0 All-IP Core Network Multimedia Domain Cx Interface Based on the Diameter Protocol; Protocol Details (-- November 2005) + +This document defines a transport protocol for use in the IP multimedia (IM) core network (CN) subsystem based on Diameter. This document is applicable to the Cx interface between the I-CSCF/S-CSCF and the HSS. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-006-A | 1.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-006-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-006-A v1.0.zip | + +### 10.5.10.17 X.S0013-007-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem – Charging Architecture (-- December 2003) + +This document describes the architecture for charging and billing for IMS services. For the purpose of this document, the charging data is considered to be generated and collected by charging functions in the network elements. The objectives of the present document are to describe principles of charging in an IMS network, to provide a description of the charging architecture, and to provide the descriptions of events and triggers for the generation of charging data. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-007-0 v1.0 | 1 | Approved | -- 12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0013-007-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-007-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-007-0v1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-007-0v10.pdf | + +### **10.5.10.18 X.S0013-007-A Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem – Charging Architecture (-- November 2005)** + +This document describes the architecture for charging and billing for IMS services. For the purpose of this document, the charging data is considered to be generated and collected by charging functions in the network elements. The objectives of the present document are to describe principles of charging in an IMS network, to provide a description of the charging architecture, and to provide the descriptions of events and triggers for the generation of charging data. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-007-A | 1.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-007-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-007-A v1.0.zip | + +### **10.5.10.19 X.S0013-008-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem – Accounting Information Flows and Protocol (-- December 2003)** + +This document defines a transport protocol for use in the IP multimedia (IM) core network (CN) subsystem based on Diameter. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-008-0 v1.0 | 1 | Approved | -- 12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.008 | | Published | -- 12-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0013-008-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-008-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-008-0v1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-008-0v10.pdf | + +### **10.5.10.20 X.S0013-008-0 Version 2.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem – Accounting Information Flows and Protocol (-- July 2005)** + +This document covers offline charging for the IMS. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-008-0 | 2.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-008-0 V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-008-0 v2.0.zip | +| TTC | TS-3GB-X.S0013-008-0v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-008-0v20.pdf | + +### **10.5.10.21 X.S0013-008-A Version 1.0 All-IP Core Network Multimedia Domain Offline Accounting Information Flows and Protocols (-- November 2005)** + +This document covers offline charging for the IMS. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-008-A | 1.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742 | +| TTA | TTAT.3G-X.S0013-008-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-008-A v1.0.zip | + +### **10.5.10.22 X.S0013-010-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem Sh Interface; Signaling flows and message contents – Stage 2 (-- December 2003)** + +This document specifies the interactions between the home subscriber server (HSS) and the SIP application server (AS) and between the HSS and the OSA service capability server (SCS). This interface is referred to as the Sh reference point. This document addresses the signalling flows and message contents for the protocol at the Sh interface. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-010-0 v1.0 | 1 | Approved | -- 12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-873.010 | | Published | -- 12-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0013-010-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-010-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-010-0v1.0 | 1.0 | TTC Published | 2-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-010-0v10.pdf | + +### **10.5.10.23 X.S0013-010-0 Version 2.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem Sh Interface; Signaling flows and message contents – Stage 2 (--July 2005)** + +This document specifies the interactions between the home subscriber server (HSS) and the SIP application server (AS) and between the HSS and the OSA service capability server (SCS). This interface is referred to as the Sh reference point. This document addresses the signalling flows and message contents for the protocol at the Sh interface. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-010-0 | 2.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-X.S0013-010-0 V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-010-0 v2.0.zip | +| TTC | TS-3GB-X.S0013-010-0v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-010-0v20.pdf | + +### **10.5.10.24 X.S0013-010-A Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Subsystem Sh Interface; Signaling flows and message contents – Stage 2 (-- November 2005)** + +This document specifies the interactions between the home subscriber server (HSS) and the SIP application server (AS) and between the HSS and the OSA service capability server (SCS). This interface is referred to as the Sh reference point. This document addresses the signalling flows and message contents for the protocol at the Sh interface. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-010-A | 1.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-X.S0013-010-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-010-A v1.0.zip | + +### **10.5.10.25 X.S0013-011-0 Version 1.0 All-IP Core Network Multimedia Domain IP Multimedia Sh Interface based on Diameter Protocols – Protocol Details – Stage 3 (-- December 2003)** + +This document defines a transport for use in the IP multimedia (IM) core network (CN) subsystem based on Diameter. The present document is applicable to the Sh interface between an SIP AS and the AAA, and the Sh interface between an SCS and the AAA. + +| | Document No. | Version | Status | Issued date | Location | +|------|--------------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-011-0 v1.0 | 1 | Approved | -- 12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TIA-873.011 | | Published | -- 12-2003 | http://www.ttaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0013-011-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-011-0 v1.0.zip | +| TTC | TS-3GB-X.S0013-011-0v1.0 | 1.0 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-011-0v10.pdf | + +### **10.5.10.26 X.S0013-011-0 Version 2.0 All-IP Core Network Multimedia Domain Sh Interface based on Diameter Protocols – Protocol Details – Stage 3 (-- July 2005)** + +This document defines a transport for use in the IP multimedia (IM) core network (CN) subsystem based on Diameter. The present document is applicable to the Sh interface between an SIP AS and the AAA, and the Sh interface between an SCS and the AAA. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-011-0 | 2.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-X.S0013-011-0 V2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-011-0 v2.0.zip | +| TTC | TS-3GB-X.S0013-011-0v2.0 | 2.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-011-0v20.pdf | + +### **10.5.10.27 X.S0013-011-A Version 1.0 All-IP Core Network Multimedia Domain Sh Interface based on Diameter Protocols Protocol Details – Stage 3 (-- November 2005)** + +This document defines a transport for use in the IP multimedia (IM) core network (CN) subsystem based on Diameter. The present document is applicable to the Sh interface between an SIP AS and the AAA, and the Sh interface between an SCS and the AAA. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0013-011-A | 1.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-X.S0013-011-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-011-A v1.0.zip | + +### **10.5.11 X.S0014-E Version 1.0 Wireless Radio Telecommunication Intersystem Non-Signaling Data Communication DMH (Data Message Handler) (-- December 2004)** + +This document describes the messages and procedures required to perform call detail record data transmission between systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0014-E | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-124-E | | Published | -- 05-2005 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0014-E V1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0014-E v1.0.zip | +| TTC | TS-3GB-X.S0014-Ev1.0 | 1.0 | TTC Published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/sxss0014-ev10.pdf | + +### **10.5.11.1 X.S0014-E Version 2.0 Wireless Radio Telecommunication Intersystem Non-Signaling Data Communication DMH (Data Message Handler) (-- August 2006)** + +This document describes the messages and procedures required to perform call detail record data transmission between systems. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0014-E v2.0 | 2.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0014-E V2.0 | 2.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0014-E v2.0.zip | +| TTC | TS-3GB-X.S0014-Ev2.0 | 2.0 | TTC Published | 01-12-2006 | http://www.ttc.or.jp/imt2000/ts/sxss0014-ev20.pdf | + +### **10.5.12 X.S0017 Version 1.0.0 Open Service Access (OSA) Application Programming Interface (API) OSA API Revision: 0 (-- June 2003)** + +This document is intended to define the OSA API stage 3 interface definitions and it provides the complete OSA specifications for cdma2000-based systems. This document is an extension of OSA API, per latest 3GPP TS 29.198 series specifications capabilities to enable operation in cdma2000 systems environment as part of the TIA/EIA/IS-2000 family of standards. The information given here is to be used by developers in 3GPP2 cdma2000 network architecture to the 3GPP OSA specifications. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0017 v1.0.0 | 1 | Approved | -- 06-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TIA | TIA-937 | | Published | -- 06-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0017 V1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0017 v1.0.0.zip | +| TTC | TS-3GB-X.S0017-0v1.0.0 | 1.0.0 | TTC Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/sxss0017-0v100.pdf | + +### 10.5.13 X.S0018 Version 1.0.0 Legacy Mobile Station Domain (LMSD) Step 1 Revision: 0 (May 2003) + +This standard specifies the necessary interfaces to support the bearer traffic between media gateways in the initial step of the legacy mobile station domain (LMSD). The requirements for this work and the overall architecture model are defined in other documents. + +This standard defines bearer support of G.711 PCM encoded voice over IP as defined in RFC 1890 at a minimum, for use between media gateways in a cdma2000 legacy mobile station domain. This standard utilizes existing IETF and 3GPP2 protocols when applicable to minimize the new work needed. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0018-0 | 1.0.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 | +| TIA | TIA-930 | | Published | -- 01-2003 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0018_v1.0.0 | 1.0.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0018_v1.0.0.zip | + +### 10.5.14 X.S0021-B Version 1.0 Roamer Database Verification (-- July 2004) + +The purpose of this document is to describe the RDV network capability and to specify the operation of RDV so that wireless systems can use RDV. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0021-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-847-B | | Published | -- 08-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0021-B v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0021-B v1.0.zip | +| TTC | TS-3GB-X.S0021-Bv1.0 | 1.0 | TTC Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0021-bv10.pdf | + +### 10.5.15 X.S0023-B Version 1.0 Network Interworking Between GSM MAP and TIA-41 Map – cdma 2000 Support (-- July 2004) + +The purpose of this standard is to define and describe the functions necessary for roaming between ANSI-41 MAP and GSM MAP-based networks in the support of roaming subscribers. This includes a capability to allow a subscriber to an ANSI-41-based network (e.g., a TDMA or CDMA native subscriber) with a mobile terminal supporting GPRS service to roam to a GPRS network in GSM foreign mode. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0023-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | J-STD-038-B | | Published | -- 08-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0023-B v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0023-B v1.0.zip | +| TTC | TS-3GB-X.S0023-Bv1.0 | 1.0 | TTC Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0023-bv10.pdf | + +### 10.5.16 X.S0025-0 Version 1.0 Legacy MS Domain Step 2 (-- February 2006) + +The legacy MS domain (LMSD) provides support for existing MSs in a network that supports IP bearers. This specification provides support for transport of compressed speech (e.g., 13K, SMV, EVRC, etc.) over IP bearers. All bearer features in the legacy network are supported. Additionally, this specification provides support for placing bearer signal processing transcoders in the base station (BS) and/or in the media gateway (MGW). Network capabilities that support minimizing the number of transcoders in the bearer path are also supported. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0025-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0025-0 v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0025-0 v1.0.zip | +| TTC | TS-3GB-X.S0025-0v1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0025-0v10.pdf | + +### 10.5.17 X.S0027-000-0 Version 1.0 Presence Overview (-- September 2004) + +This document describes network aspects of the presence service. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0027-000-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-1032.000 | | Published | -- 11-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0027-000-0 v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0027-000-0 v1.0.zip | +| TTC | TS-3GB-X.S0027-000-0v1.0 | 1.0 | TTC Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0027-000-0v10.pdf | + +#### 10.5.17.1 X.S0027-001-0 Version 1.0 Presence Service: Architecture and Functional Description (-- September 2004) + +This document describes the stage 2 (architectural solution and functionalities) for the presence service, which includes the elements necessary to realize the stage 1 requirements. + +| | Document No. | Version | Status | Issued date | Location | +|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0027-001-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-1032 | | Published | -- 11-2004 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0027-001-0 v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0027-001-0 v1.0.zip | +| TTC | TS-3GB-X.S0027-001-0v1.0 | 1.0 | TTC Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0027-001-0v10.pdf | + +### 10.5.18 X.S0030-0 Version 1.0 MAP Enhancements to Support Enhanced Message Waiting Notification (MWN) (-- September 2005) + +This document provides automatic roaming information flows that illustrate enhanced message waiting count operation. This document also describes the signalling protocol and signalling procedure modifications needed for enhanced message waiting count operation. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0030-0 | 1 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-X.S0030-0 v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0030-0 v1.0.zip | +| TTC | TS-3GB-X.S0030-0v1.0 | 1.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/sxso030-0v10.pdf | + +### 10.5.19 X.S0033-0 Version 1.0 OTA Support for MEID (-- October 2005) + +This document presents a recommended plan for the implementation of over-the-air (OTA) support for the mobile equipment identity (MEID) + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0033-0 | 1.0 | Approved | -- 01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TIA | TIA-1074 | | Published | -- 03-2006 | http://www.tiaonline.org/standards/catalog/search.cfm | +| TTA | TTAT.3G-X.S0033-0 v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0033-0 v1.0.zip | +| TTC | TS-3GB-X.S0033-0v1.0 | 1.0 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/sxso033-0v10.pdf | + +### 10.5.19.1 X.S0033-0 Version 2.0 OTA Support for MEID (-- February 2006) + +This document presents a recommended plan for the implementation of over-the-air (OTA) support for the mobile equipment identity (MEID) + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0033-0 v2.0 | 2.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0033-0 v2.0 | 2.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0033-0 v2.0.zip | +| TTC | TS-3GB-X.S0033-0v2.0 | 2.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/sxso033-0v20.pdf | + +### 10.5.20 X.S0034-0 Version 1.0 cdma2000/GPRS Roaming (-- September 2004) + +The scope of this document includes the roaming of a subscriber homed in a cdma2000 packet data system to a GPRS system and vice versa. The roaming between cdma2000 packet data systems is outside the scope of this document. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-TSD-MC-X.S0034-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 | +| TTA | TTAT.3G-X.S0034-0 v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0034-0 v1.0.zip | +| TTC | TS-3GB-X.S0034-0v1.0 | 1.0 | TTC Published | 26-08-2005 | http://www.ttc.or.jp/imt2000/ts/sxso034-0v10.pdf | + +### **10.5.21 X.S0037-0 Version 1.0 Tunneling Support in Simple IP (-- May 2006)** + +The scope of this specification includes tunnelling support for the simple IP packet data subscriber roaming across cdma2000 packet data systems that are administered by different service providers. In this specification, the tunnelling scheme is specified in the context of layer-two tunnelling. Other tunnelling schemes are not precluded. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.S0037-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.S0037-0 v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0037-0 v1.0.zip | +| TTC | TS-3GB-X.S0037-0v1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxs0037-0v10.pdf | + +### **10.5.22 X.R0039-0 Version 1.0 Packet Switched Voice (over IP) and Video Telephony Services End-to-End Design Technical Report (-- November 2005)** + +This document describes the end-to-end protocols and procedures for support of packet switched Video Telephony (PSVT) and Voice-Over-IP (VoIP) Services over cdma2000® networks. The document describes the end-to-end PSVT and VoIP services and architectures. + +| | Document No. | Version | Status | Issued date | Location | +|------|------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| CCSA | CCSA-X.R0039-0 v1.0 | 1.0 | Approved | 31-01-2007 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 | +| TTA | TTAT.3G-X.R0039-0 v1.0 | 1.0 | Approved | 15-02-2007 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.R0039-0 v1.0.zip | +| TTC | TS-3GB-X.R0039-0v1.0 | 1.0 | TTC Published | 02-06-2006 | http://www.ttc.or.jp/imt2000/ts/tsxr0039-0v10.pdf | + + + + + +## 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/Q/T-REC-Q.1751-200006-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1751-200006-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3427adc8687b158f99d4ec5b90824caf65514cf4 --- /dev/null +++ b/marked/Q/T-REC-Q.1751-200006-I_PDF-E/raw.md @@ -0,0 +1,1532 @@ + + +![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 + +**Q.1751** + +(06/2000) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for IMT-2000 + +--- + +**Internetwork signalling requirements for +IMT-2000 capability set 1** + +ITU-T Recommendation Q.1751 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +# **SWITCHING AND SIGNALLING** + +| | | +|-----------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| BROADBAND ISDN | Q.2000-Q.2999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Internetwork signalling requirements for IMT-2000 capability set 1** + +## **Summary** + +This ITU-T Recommendation contains signalling requirements for the Network-to-Network Interface (NNI) protocol. The requirements are to support the capabilities that are recommended in the IMT-2000 Framework document and specified as Capability Set 1 (CS-1). This ITU-T Recommendation covers requirements for four communication groups of the NNI: Call and Bearer Control; Mobility Management; Virtual Home Environment (VHE) Service Control; and Packet Data Services and Internet Access Control. The requirements for inter-network security are described at a high level, and its functionality is incorporated into applicable communications group protocols. The requirements specified in this ITU-T Recommendation are non-information flow related, and they should be viewed as complementary to the information flows of ITU-T Recommendation Q.1721. They include general NNI protocol requirements, NNI functional models, NNI reference points, state models for selective functional entities, and the choice of various protocol suites. + +## **Source** + +ITU-T Recommendation Q.1751 was prepared by ITU-T Study Group 11 (1997-2000) and approved under the WTSC Resolution 1 procedure on 15 June 2000. + +## **Keywords** + +AMF, BICC, CN, CS-1, IMT-2000, INAP, LMFh, LMFv, MT, NNI, RAN, UIM, VHE. + +## 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 | Definitions ..... | 2 | +| 4 | Abbreviations..... | 2 | +| 5 | Introduction..... | 5 | +| 6 | General requirements ..... | 5 | +| 6.1 | NNI requirements..... | 5 | +| 6.2 | VHE Service control requirements ..... | 6 | +| 6.2.1 | Remote programming-based VHE ..... | 6 | +| 6.2.2 | Service capabilities ..... | 6 | +| 6.3 | CN data storage requirements for subscriber (user) profile..... | 6 | +| 6.4 | Global roaming requirement..... | 7 | +| 6.5 | NNI communication grouping ..... | 7 | +| 6.6 | Internet services ..... | 8 | +| 6.7 | Security Requirements ..... | 9 | +| 6.7.1 | Requirements for the support of user authentication..... | 9 | +| 6.7.2 | Encryption requirements for Network-to-Network Interface ..... | 9 | +| 6.7.3 | Key Management requirements for Network-to-Network Interface..... | 9 | +| 7 | Interconnection model ..... | 10 | +| 8 | NNI functional interface ..... | 10 | +| 8.1 | Functional model ..... | 10 | +| 8.2 | Reference Points ..... | 11 | +| 8.2.1 | Reference Point N01 ..... | 12 | +| 8.2.2 | Reference Point N02..... | 12 | +| 8.2.3 | Reference Point N03..... | 12 | +| 8.2.4 | Reference Point N04..... | 12 | +| 8.2.5 | Reference Point N05..... | 12 | +| 8.2.6 | Reference Point N06..... | 13 | +| 8.2.7 | Reference Point N07..... | 13 | +| 8.2.8 | Reference Point N08..... | 13 | +| 8.2.9 | Reference Point N09..... | 13 | +| 8.2.10 | Reference Point N10..... | 13 | +| 8.2.11 | Reference Point N11..... | 13 | +| 8.2.12 | Reference Point N12..... | 13 | +| 8.2.13 | Reference Point N13..... | 14 | + +| | Page | +|------------------------------------------------------------|-------------| +| 8.2.14 Reference Point N14..... | 14 | +| 8.2.15 Reference Point N15..... | 14 | +| 8.2.16 Reference Point N16..... | 14 | +| 8.2.17 Reference Point N17..... | 14 | +| 8.2.18 Reference Point N18..... | 14 | +| 8.2.19 Reference Point N19..... | 15 | +| 8.2.20 Reference Point N20..... | 15 | +| 8.2.21 Reference Point N21..... | 15 | +| 9 Protocol requirements for Mobility Management..... | 15 | +| 9.1 Service drivers ..... | 15 | +| 9.2 Service logic interaction modes ..... | 16 | +| 9.3 LMFv State Model..... | 16 | +| 9.3.1 State: v_Null ..... | 17 | +| 9.3.2 State: v_Initial Registration ..... | 18 | +| 9.3.3 State: V_Authentication Processing ..... | 18 | +| 9.3.4 State: V_Registration_pending..... | 19 | +| 9.3.5 State: V_Active_registered..... | 19 | +| 9.3.6 State: v_Inactive_registered..... | 20 | +| 9.3.7 State: v_Denied..... | 20 | +| 9.4 LMFh State Model..... | 20 | +| 9.4.1 State H_Location_Unknown ..... | 21 | +| 9.4.2 State H_Registering..... | 22 | +| 9.4.3 State H Registered ..... | 22 | +| 9.4.4 State H_Old_Location_Cancelling_and_Registered ..... | 23 | +| 9.4.5 State_H_Exception ..... | 23 | +| 9.5 AMF state model ..... | 23 | +| 9.5.1 State: A_Null ..... | 24 | +| 9.5.2 State: Authentication_Processing..... | 25 | +| 9.5.3 State: Awaiting_Challenge_Response..... | 25 | +| 9.6 Mobility Management Functional Communications ..... | 25 | +| 9.7 Choice of Protocol Suite ..... | 26 | +| 10 Protocol requirements for VHE Service Control ..... | 26 | +| 10.1 General requirements ..... | 26 | +| 10.2 Service Control Functional Communications..... | 27 | +| 10.3 Choice of Protocol Suite ..... | 28 | +| 11 Protocol requirements for Call and Bearer Control ..... | 28 | +| 11.1 General requirements ..... | 28 | +| 11.2 Choice of switching principles..... | 28 | + +| | Page | +|-------------------------------------------------------------|-------------| +| 11.3 Call and Bearer Control functional communications..... | 28 | +| 11.4 Choice of Protocol Suite ..... | 30 | +| 11.5 Multimedia calls ..... | 31 | +| 11.6 Multi-party calls..... | 31 | +| 12 Protocol requirements for Packet Service Control..... | 32 | +| 12.1 The PSCF to PSGCF Interface protocol ..... | 32 | +| 12.1.1 User plane requirements ..... | 33 | +| 12.1.2 Control plane requirements ..... | 33 | +| 12.2 The LMFp to LMFp Interface Protocol ..... | 33 | +| Appendix I – Guidance on trigger concepts and usage..... | 35 | +| I.1 Purpose..... | 35 | +| I.2 Introduction..... | 35 | +| I.3 Principles and concepts..... | 35 | +| I.4 Dynamic trigger arming ..... | 36 | +| I.5 Distribution of triggers..... | 36 | + + + +# **Internetwork signalling requirements for IMT-2000 capability set 1** + +# **1 Scope** + +The scope of this ITU-T Recommendation includes preparation of inter-networking signalling requirements to be used for development of a unique and common Network-to-Network Interface (NNI) protocol. With inputs from ITU-T Recommendations Q.1701 [1], Q.1711 [2] and Q.1721 [3], this ITU-T Recommendation provides signalling and protocol requirements, that are not of information flow nature. Specifically, this ITU-T Recommendation includes the following subjects: + +- Description of the signalling layers in accordance with the functional groupings for Call and Bearer Control (CBC), Mobility Management (MM), Packet Services Control (PSC), and VHE Service Control (VSC). +- NNI instances for Global Roaming and their Reference Points. +- State Models for various Functional Entities. +- Signalling Requirements for NNI Protocol(s). +- Choice of NNI Protocols. + +**The CN-CN interworking can also be realized by specifying an interworking function (IWF) for protocol (and billing) information conversion between different family members. But the detailed specification of the interworking function is outside the scope of ITU.** + +**Preparation of detailed description using "Specification and Description Language" (SDL), design of the protocol architecture and coding of the protocol are beyond the scope of this ITU-T Recommendation.** + +**Aspects of OAM between Family Member Systems are also beyond the scope of this ITU-T 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; 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 Q.1701 (1999), *Framework for IMT-2000 networks*. +- [2] ITU-T Recommendation Q.1711 (1999), *Network functional model for IMT-2000*. +- [3] ITU-T Recommendation Q.1721 (2000), *Information flows for IMT-2000 capability set 1*. +- [4] ITU-T Recommendation Q.1901 (2000), *Bearer independent call control protocol*. +- [5] ITU-T Recommendation Q.2630.1 (1999), *AAL type 2 signalling protocol (Capability Set 1)*. +- [6] ITU-T Recommendations Q.1238 series, *Interface Recommendation for intelligent network capability set 3*. +- [7] ITU-T Recommendation Q.1290 (1998), *Glossary of terms used in the definition of intelligent networks*. + +# 3 Definitions + +This ITU-T Recommendation defines the following terms: + +**3.1 anchor core network:** In a data session roaming environment, the anchor core network is the network where the data session is initiated and a packet service gateway is assigned to the mobile terminal. The anchor core network may be either the home or the visited network. + +**3.2 reference point:** In an inter- or intra-network functional model, the point of reference is referred to the relationship between two functional entities for exchanging signalling messages and operations transactions. + +**3.3 service application:** The provision of services by general purpose capabilities, such as Intelligent Network capabilities as applied at the home location or at a visited location as part of a Virtual Home Environment. + +**3.4 service control:** Functions that set or modify the context in which basic calls and bearers are established, modified and released. + +**3.5 state model:** The state model for a functional entity is a schematic representation of the states of a functional entity in relation to an inter-network signalling procedure. It includes identification of all entry and exit Detection Points (DPs) for each state. + +**3.6 subscriber:** The user of a mobile terminal who has subscribed to the service. + +**3.7 supplementary service application:** The provision of a specific supplementary service, typically through use of service specific capabilities, whether at the home location or at the visited location as part of a Virtual Home Environment. + +**3.8 user:** The user of a mobile terminal. The terms "user" and "subscriber" are used interchangeably in this ITU-T Recommendation. + +**3.9 virtual home environment:** The provision of a service experience to the visiting subscriber identical to, or as similar as possible to the service experience the subscriber has when served at his home location. + +This ITU-T Recommendation uses terms defined in ITU-T Recommendation Q.1701 [1]. + +- **core network** + +This ITU-T Recommendation uses terms defined in ITU-T Recommendation Q.1290 [7]. + +- **functional entity** +- **detection point** +- **service trigger** + +# 4 Abbreviations + +This ITU-T Recommendation uses the following abbreviations: + +| | | +|------|------------------------------------| +| AALx | ATM Application Layer x | +| AC | Authentication Centre | +| ADDS | Application Data Delivery Service | +| AINI | ATM InterNetwork Interface | +| AMF | Authentication Management Function | +| ATM | Asynchronous Transfer Mode | +| BICC | Bearer Independent Call Control | + +| | | +|----------|-----------------------------------------------------------------------------------------| +| B-ISUP | Broadband ISUP | +| CBC | Call and Bearer Control | +| CC | Call Control | +| CCAF' | Call Control Agent Function (enhanced, as described in ITU-T Recommendation Q.1711 [2]) | +| CCF | Call Control Function | +| CCF' | Call Control Function (enhanced, as described in ITU-T Recommendation Q.1711 [2]) | +| CLI | Calling Line ID | +| CN | Core Network | +| CNa | Core Network (anchored) | +| CnCAF | Connection Control Agent Function | +| CnCF | Connection Control Function | +| CNh | Core Network (home) | +| CNpv | Core Network (previous visited) | +| CNsn | Core Network (supporting) | +| CNv | Core Network (visited) | +| CS-X | Capability Set X | +| DFP | Distributed Functional Plane | +| DP | Detection Point | +| FE | Functional Entity | +| FT | Fixed Terminal | +| GPCF | Geographic Position Control Function | +| GPF | Geographic Position Function | +| GTT | Global Title Translation | +| ID | Identity | +| IF | Information Flow | +| IMDN | IMT-2000 International Mobile Directory Number | +| IMT-2000 | International Mobile Telecommunications-2000 | +| IMUI | IMT-2000 International Mobile User Identity | +| IN | Intelligent Network | +| INAP | Intelligent Network Application Protocol | +| IP | Internet Protocol | +| ISDN | Integrated Services Digital Network | +| ISP | Internet Service Provider | +| ISUP | ISDN User Part | +| IWF | InterWorking Function | + +| | | +|--------|----------------------------------------------| +| LAI | Location Area Identity | +| LMF | Location Management Function | +| MCF | Mobile Control Function | +| MGPF | Mobile Geographic Position Function | +| MM | Mobility Management | +| MRTR | Mobile Radio Transmission and Reception | +| MSC | Mobile Switching Centre | +| MT | Mobile Terminal | +| NAI | Network Access Identifier | +| N-ISUP | Narrow-band ISUP | +| NNI | Network-to-Network Interface | +| Nxx | Reference Point Nxx | +| PDN | Packet data Network | +| PIAM | Point in Authentication Management | +| PIN | Personal Identification Number | +| PNNI | Private Network-to-Network Interface | +| PSC | Packet Service Control | +| PSCAF | Packet Service Control Agent Function | +| PSCF | Packet Service Control Function | +| PSGCF | Packet Service Gateway Control Function | +| PSTN | Public Switched Telephone Network | +| QoS | Quality of Service | +| RACAF | Radio Access Control Agent Function | +| RAN | Radio Access Network | +| RF | Radio Frequency | +| RFTR | Radio Frequency Transmission and Reception | +| RNC | Radio Network Controller | +| SACF | Service Access Control Function | +| SCF | Service Control Function | +| SCP | Service Control Point | +| SDF | Service Data Function | +| SDP | Service Data Point | +| SIBF | System Access Information Broadcast Function | +| SLP | Service Logic Program | +| SMF | Service Management Function | +| SMS | Short Message Service | +| SRF | Specialized Resource Function | + +| | | +|------|-----------------------------------------| +| SSD | Shared Secret Data | +| TMUI | Temporary Mobile User Identifier | +| UDP | User Datagram Protocol | +| UIM | User Identity Module | +| UIMF | User Identification Management Function | +| UPT | Universal Personal Telecommunication | +| VHE | Virtual Home Environment | +| VSC | VHE Service Control | + +# 5 Introduction + +The NNI signalling requirements identified in this ITU-T Recommendation are to assist protocol designers to develop specific protocols that govern the interactions among core networks of the IMT-2000 Family of Systems. These requirements are divided into two parts, applications and protocols, and organized into 12 clauses as follows. Clauses 1 through 5 are general documentation requirements providing description of the scope of this ITU-T Recommendation, a short summary of the content of this ITU-T Recommendation, references, abbreviations, definitions and terminology, and this introduction. Clause 6 contains all general and application related requirements including service capabilities, data storage and subscriber profile requirements. It also covers all functional modelling aspects of the NNI. Clause 7 identifies and describes all the protocol-related FE-to-FE reference points. A total of 20 reference points are addressed in this clause. Clauses 8 through 12 are related to the protocol requirements for five categories of signalling for call and bearer control, mobility management, VHE and IN service control, packet and internet service control, and inter-core network exchange of security information and data. + +# 6 General requirements + +## 6.1 NNI requirements + +The NNI shall support the set of IMT-2000 CS-1 service/network capabilities and features that ensure backward compatibility with second generation systems. + +The following set of numbered NNI requirements provides as a starting point to build a complete set in subsequent sections. The requirements are intentionally kept single objective oriented to enable easy and efficient traceability. + +- 1) The NNI should provide for "look ahead" or optimum routing, e.g. to prevent the "tromboning" effect.1 +- 2) The NNI should support the transfer of Call Detail Record (CDR) such as call reference tags, charging related data, advice of charge, and other CDR information needed for regulatory issues. +- 3) NNI should support messaging services (e.g. voicemail notification and ADDS). + +--- + +1 In second generation systems, tromboning causes a mobile terminated call to be routed back to the called mobile subscriber's home system, even if the called party may actually be in the calling party's vicinity. Especially in a global roaming situation, avoiding tromboning would be very beneficial, preventing long-distance trunk resource wastage. + +## 6.2 VHE Service control requirements + +Virtual Home Environment must be provided according to the scenarios identified in Q.1711 [2]. Two scenarios are identified in this ITU-T Recommendation: + +**Direct home command:** This scenario calls for invocation of service logic to query for instruction/information to the SCFsn. In this scenario, the prearrangement between the supporting and the home networks or between the supporting and the visited networks may need screening capabilities of triggering invocation. + +**Relay service control:** This scenario calls for the invocation of the service logic via the SCFh or the SCFv to query for instruction/information to the SCFsn. In this scenario the prearrangement between the supporting and the home networks or between the supporting and the visited networks ranges from relaying, security/screening capabilities to shared service logic. + +### 6.2.1 Remote programming-based VHE + +Support of VHE by means of downloading of service logic and service related data from the home network to both the serving network and the UIM. + +### 6.2.2 Service capabilities + +**Charging:** The Charging procedures are used to provide Call Documentation and Call Duration. + +**Network management:** Network management procedures provide protection of the home network from overload. + +**Caller interaction and specialized resource handling:** The procedures allow for playing announcements, prompting and collecting post-dialling information from the user (e.g. PIN for Credit Card Calling). + +**Assist and handoff:** The procedures allow to request assistance to external equipment (e.g. IP) for playing announcement, prompting and collecting information. + +## 6.3 CN data storage requirements for subscriber (user) profile + +The following information items are stored in the subscriber home network and the subject of the subscriber information and profile management activities: + +- IMT-2000 Mobile Directory Number (IMDN), e.g. a diallable number; +- IMT-2000 Mobile User ID (IMUI); +- IMT-2000 Temporary Mobile User ID (TMUI); +- Terminal State; +- User/Terminal Location Information; +- Basic Service Data (e.g. subscribed bearer services); +- Teleservices (e.g. broadcast and/or group call subscription data); +- Supplementary Services data; +- Operator Determined features/services (e.g. Call Barring Data); +- Subscriber Determined features/services (e.g. Call Screening Data); +- Roaming Restriction Data; +- Regional Subscription Data; and +- VHE Subscription Data. + +## 6.4 Global roaming requirement + +The NNI is a common and unique CN-to-CN interface protocol that supports the global roaming capability of the IMT-2000 and provides home service environment to the users roaming through two or more IMT-2000 family member networks. Figure 6-1 shows the role that the common NNI can play, in conjunction with various family members' IWFs, to provide interoperability among the networks and support global roaming by providing a home service environment to the roaming users. The implementation of the interoperability and the global roaming configuration as shown in Figure 6-1 has the following distinct characteristics over the implementation of IWFs for every core network pair. + +- Open interface: There will be only one common and unique NNI (under development by ITU-T). +- Efficiency: One IWF (as opposed to N-1 bilateral IWFs) per family member for an IMT-2000 family of N members is needed. This is for every family member to interwork with all other family members. +- Transparency: Changes in one family member's network specifications will not affect other family members' IWFs. +- Future Proof: Can easily accommodate new members into the family. + +While the development of the NNI protocol lies with ITU-T, the development of the IWF is the responsibility of each family member. + +![Diagram of the IMT-2000 network interconnection model showing three family members (A, B, and C) connected via a central NNI node through their respective IWFs and CNs.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +The diagram illustrates the IMT-2000 network interconnection model. At the top, 'Family Member B' is shown as an oval containing 'CN B' and 'IWFb'. 'IWFb' is connected to a central hexagonal 'NNI' node. At the bottom left, 'Family Member A' is shown as an oval containing 'CN A' and 'IWFa'. 'IWFa' is connected to another hexagonal 'NNI' node, which is in turn connected to the central 'NNI' node. At the bottom right, 'Family Member C' is shown as an oval containing 'CN C' and 'IWFc'. 'IWFc' is connected to a third hexagonal 'NNI' node, which is also connected to the central 'NNI' node. The central 'NNI' node acts as a hub, connecting all three family members. A small label 'T11106580-00' is visible at the bottom right of the diagram. + +Diagram of the IMT-2000 network interconnection model showing three family members (A, B, and C) connected via a central NNI node through their respective IWFs and CNs. + +Figure 6-1/Q.1751 – IMT-2000 network interconnection model + +## 6.5 NNI communication grouping + +Four main and distinct communication groups are recognized in an IMT-2000 cross-CN operation. The distinction stems from the nature of the operations they support by constituting a unique and common NNI Application Protocol. These communications groups are as follows: + +- *Call and Bearer Control (CBC)* + +This communication group includes all cross-CN exchange of information related to controlling connection-oriented and connectionless services including basic services, standard supplementary services. + +- *Mobility Management (MM)* + +This communication group includes all cross-CN exchange of information related to mobility management (e.g. registration, authentication, and location information management). + +- *VHE Service Control (VSC)* + +This communication group includes all cross-CN exchange of information related to the control of the home network services accessible from the visited networks. + +- *Packet Service Control (PSC)* + +This communication group includes all cross-CN exchange of information related to the control of Packet services (e.g. voice, image and data). + +The requirements for inter-network security are described at a high level, and its functionality is incorporated into applicable communications group protocols. + +Within the context of a unique and common NNI protocol described in 6.4, this grouping is further illustrated in Figure 6-2 below: + +![Diagram illustrating NNI communications grouping between two core networks. Core Network I and Core Network II are shown as boxes containing four communication groups: CBC, MM, VSC, and PSC. Each group is connected to an IWF (Interworking Function) box. The IWF boxes are connected to a central NNI (Network-to-Network Interface) box, which is then connected to another NNI box, which is finally connected to another IWF box, which in turn connects to the communication groups in Core Network II. The text 'T11106590-00' is visible below the diagram.](b90144cfbb81a2d610d920240fda689d_img.jpg) + +Diagram illustrating NNI communications grouping between two core networks. Core Network I and Core Network II are shown as boxes containing four communication groups: CBC, MM, VSC, and PSC. Each group is connected to an IWF (Interworking Function) box. The IWF boxes are connected to a central NNI (Network-to-Network Interface) box, which is then connected to another NNI box, which is finally connected to another IWF box, which in turn connects to the communication groups in Core Network II. The text 'T11106590-00' is visible below the diagram. + +**Figure 6-2/Q.1751 – NNI communications grouping** + +To set up a call and/or to transport a service across a protocol interfacing two core networks, one or more of these communications groups are to be established either directly or indirectly between two or more core networks. The interconnections scheme to carry out the required communications follows the IMT-2000 network interconnectivity model of clause 7, as illustrated in Figure 7-1. + +## 6.6 Internet services + +- 1) The roaming packet data subscriber should be able to gain access to public Internet, to a home ISP, or to a private network from multiple IMT-2000 service providers while maintaining a formal customer-vendor relationship with only one IMT-2000 service provider. +- 2) The subscriber should explicitly indicate which access data service (i.e. access to public Internet, to a home ISP, or to a private network) is being requested. +- 3) The subscriber should be able to establish simultaneous data sessions to public Internet, a home ISP, or a private network and have different IP addresses and NAIs for the respective access services. The packet data network may use the destination IP address or the NAI that may be included in the session registration request to determine the destination of the packet data session. + +- 4) The NNI should be able to support QoS by assigning the user's traffic to a specific differentiated service class on a per packet basis for transport over the Internet. The NNI should be also able to assign all user's traffic to a specific service class on a per destination basis. + +## **6.7 Security Requirements** + +The NNI is the interface point of an IMT-2000 system's core network to other core networks. The NNI interacts with other networks to provide end-to-end communication between users (see Figure 6-1). The NNI will transport information about users (e.g. location, authorization, authentication and encryption keys) and networks (i.e. signalling and control); this information must be kept secured from intruders. This ITU-T Recommendation addresses the security aspects of the information transport. + +Security requirements for NNI can be separated into three parts. Authentication requirements (which includes privacy), Encryption requirements, and Key Management requirements for NNI. These parts are detailed below. + +### **6.7.1 Requirements for the support of user authentication** + +- The NNI standards should be designed to allow for the possible introduction of new authentication algorithms, key sizes and optional authentication methods during the expected lifetime of the standards. +- The NNI security mechanisms should minimize the impact to the network traffic (e.g. by optionally allowing sharing of secret data between the home entity and the serving entity). +- The NNI security mechanisms should support unique challenges of terminals on dedicated (bearer and signalling) channels. +- The NNI security mechanism should support a global challenge mechanism, broadcast on a global signalling channel, requiring a terminal to correctly respond to a network challenge before dedicated channels are allocated. +- The NNI security mechanisms should be able to detect and report security violations, and have recovery mechanisms to restore the system to a protected state. +- The provision or the generation of privacy and encryption keys may be part of the authentication procedure. +- The compromise of an individual mobile shall not compromise the overall network security. + +### **6.7.2 Encryption requirements for Network-to-Network Interface** + +- The NNI encryption mechanisms should satisfy legal requirements imposed by regulation agencies (for example, export controls, lawful interception). +- The NNI encryption mechanisms should be able to encrypt in multi-megabits per second, without any compromise to security. +- The NNI security should be able to provide for mutual authentication among the network elements. + +### **6.7.3 Key Management requirements for Network-to-Network Interface** + +- Compromise of a privacy key should not compromise authentication. +- Keys for data privacy may be based on the same authentication root key. +- The NNI encryption mechanisms should support call related key management, e.g. creation, distribution, modification, or revocation of cryptographic keys. +- The NNI shall not support modifications to the Authentication Root Key(s) stored in a UIM and the home authentication centre (AMFh). + +# 7 Interconnection model + +Figure 7-1 illustrates the relationships required to be supported by the NNI in support of IMT-2000 CS-1. All the FEs contained within each network are not necessarily shown here (e.g. Home network may contain SCF and SDF, Previously Visited network may contain PSGCF). Rather, the differentiation across NNI boundaries is intended to show which FEs are relevant to the particular network function for NNI interoperability. To avoid cluttering of the figure, no intra-network relationships are shown in the figure. + +![Figure 7-1/Q.1751 – IMT-2000 network interconnection model diagram showing functional element (FE) relationships across network boundaries.](dfe556fea00682b09a59427aaf72051c_img.jpg) + +The diagram illustrates the IMT-2000 network interconnection model across five network domains: **Interrogating Network**, **Supporting Network**, **Home Network**, **Destination Network**, **Serving Network**, and **Previous Visited Network**. A thick horizontal line separates the top three networks from the bottom three. + +Functional Elements (FEs) shown include: + +- Service Control**: Present in Interrogating, Supporting, and Home Networks. It connects across NNI boundaries. +- Mob Mgt**: Present in Interrogating, Home, and Previous Visited Networks. It connects across NNI boundaries. +- Call/Bearer Control**: Present in Interrogating, Destination, and Serving Networks. It connects across NNI boundaries. +- Packet Control**: Present in Interrogating, Home, and Previous Visited Networks. It connects across NNI boundaries. + +Connections between FEs are shown as lines crossing the vertical NNI boundaries. For example, Service Control in the Interrogating Network connects to Service Control in the Supporting Network, which in turn connects to Service Control in the Home Network. Similar connections exist for Mob Mgt, Call/Bearer Control, and Packet Control across the respective network boundaries. + +**Legend:** + +| | | +|-------------------------|---------------------| +| Service Control | SCF, SDF, SRF | +| Mobility Management | LMF, AMF, UIMF | +| Call and Bearer Control | CCF/SSF, CnCF, SACF | +| Packet Control | PSCF, PSGCF | + +T11106600-00 + +Figure 7-1/Q.1751 – IMT-2000 network interconnection model diagram showing functional element (FE) relationships across network boundaries. + +Figure 7-1/Q.1751 – IMT-2000 network interconnection model + +# 8 NNI functional interface + +## 8.1 Functional model + +Figure 8-1 shows the "NNI Functional Interface Model". Its purpose is to focus this ITU-T Recommendation on only those interfaces that pertain to the NNI on a functional level. Figure 7-1 "IMT-2000 Network Interconnection Model" (NIM) and Figure 8-1 "NNI Functional Interface Model" (FIM) together provide the framework for identifying the NNI signalling relationships and the basis for defining the protocol. + +![Figure 8-1/Q.1751 – NNI Functional Interface Model diagram showing connections between Family Member A and Family Member B through various reference points (N1-N21).](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +The diagram illustrates the NNI Functional Interface Model between Family Member A and Family Member B. A central vertical column of reference points (N1 through N21) acts as a bridge between the two family members. Family Member A on the left contains functional blocks: LMFv, LMFh, PSGCF, AMF, UIMF, SCF, SDF, SCF, CCF/SSF, SRF, and CnCF. Family Member B on the right contains functional blocks: LMFv, SCF, SACF, CCF/SSF, PSCF, SCF, LMFh, SRF, SACF, SDF, CCF/SSF, and CnCF. Lines connect specific functional blocks in A to specific reference points, which in turn connect to specific functional blocks in B. For example, LMFh in A connects to N2, N3, N4, N5, and N6, which then connect to SCF, SACF, CCF/SSF, and PSCF in B. An arrow labeled 'NNI' points down towards the reference points from the top. + +Figure 8-1/Q.1751 – NNI Functional Interface Model diagram showing connections between Family Member A and Family Member B through various reference points (N1-N21). + +T11106610-00 + +**Figure 8-1/Q.1751 – NNI Functional Interface Model** + +## **8.2 Reference Points** + +The Reference Points (Nxx), shown in Figure 8-1, are described below with illustrative examples of the NNI messaging (extracted from clause 5 "The IMT-2000 Functional Models" in ITU-T Recommendation Q.17112). + +2 Some of the relationships may not be covered in clause 7/Q.1711 [2]: "Global Roaming and Interworking Scenarios", perhaps because they were not meant to be comprehensive. + +Note that to support IMT-2000 service requirements, the means of identifying subscribers needs to be extended to include IMUI and others. This is a general requirement, which is applicable to existing IN interfaces. + +### **8.2.1 Reference Point N01** + +Reference Point N01 is the LMFv to LMFv functional interface. For example, NNI messaging over this functional interface enables: + +- the management of subscriber information (e.g. for IMUI retrieval based on TMUI). + +### **8.2.2 Reference Point N02** + +Reference Point N02 is the LMFh to LMFv functional interface. For example, NNI messaging over this functional interface enables: + +- registration; +- registration cancellation (home to previously visited); +- the transfer of service profile; +- the transfer of routing information for the establishment of calls; +- the management of subscriber information; +- the control of supplementary services. + +### **8.2.3 Reference Point N03** + +Reference Point N03 is the LMFh to SCF functional interface. For example, NNI messaging over this functional interface enables: + +- location management related IN services. + +### **8.2.4 Reference Point N04** + +Reference Point N04 is the LMFh to SACF functional interface. For example, NNI messaging over this functional interface enables: + +- the transfer of routing information for the establishment of calls; +- the transfer of authentication related requests; +- the management of basic mobility information, such as: + - MT location, status and identity; +- sharing of paging strategy information; +- the control of supplementary services; +- delivery of messages, such as: + - SMS messages, + - ADDS messages; +- managing global random challenge activities; +- managing unique authentication challenge activities. + +### **8.2.5 Reference Point N05** + +Reference Point N05 is the LMFh to CCF'/SSF functional interface. For example, NNI messaging over this functional interface enables: + +- the transfer of routing information for the establishment of calls; +- the transfer of profile information including service capability, such as: + - protocol information; + +- bearer information. + +### **8.2.6 Reference Point N06** + +Reference Point N06 is the LMFh to PSCF functional interface. For example, NNI messaging over this functional interface enables: + +- accessing and updating subscriber-related data; +- updating packet service information; +- updating packet routing information. + +### **8.2.7 Reference Point N07** + +Reference Point N07 is the PSGCF to PSCF functional interface. For example, NNI messaging over this functional interface enables: + +- the updating of MT packet data service information; +- the updating of MT routing context association; +- transfer of user data between an MT and a packet network. + +### **8.2.8 Reference Point N08** + +Reference Point N08 is the AMF to SCF functional interface. For example, NNI messaging over this functional interface enables: + +- user authentication related IN services. + +### **8.2.9 Reference Point N09** + +Reference Point N09 is the UIMF to SCF functional interface. For example, NNI messaging over this functional interface enables: + +- the transfer of service data/logic; +- the modification of service profile; +- the exchange of application information. + +### **8.2.10 Reference Point N10** + +Reference Point N10 is the SCF to SCF functional interface. For example, NNI messaging over this functional interface enables: + +- the acquisition and manipulation of secured data; +- distributed service control; +- unsolicited service notifications. + +### **8.2.11 Reference Point N11** + +Reference Point N11 is the SCF to LMFh functional interface. For example, NNI messaging over this functional interface enables: + +- the LMFh to provide MT location and subscriber status to the SCF. + +### **8.2.12 Reference Point N12** + +Reference Point N12 is the SCF to SRF functional interface. For example, NNI messaging over this functional interface enables: + +- the provision of specialized resources for IN services. + +### **8.2.13 Reference Point N13** + +Reference Point N13 is the SCF to SACF functional interface. For example, NNI messaging over this functional interface enables: + +- IN services based on mobility management events, such as: + - location management; + - user authentication; +- call unrelated IN services. + +### **8.2.14 Reference Point N14** + +Reference Point N14 is the SCF to SDF functional interface. For example, NNI messaging over this functional interface enables: + +- the SDF to provide the SCF with a logical view of subscriber data; +- the SCF and SDF to manage and update service data. + +### **8.2.15 Reference Point N15** + +Reference Point N15 is the SDF to SDF functional interface. For example, NNI messaging over this functional interface enables: + +- the exchange of service data. + +### **8.2.16 Reference Point N16** + +Reference Point N16 is the SCF to CCF'/SSF functional interface. For example, NNI messaging over this functional interface enables: + +- call related IN services. + +### **8.2.17 Reference Point N17** + +Reference Point N17 is the CCF'/SSF to CCF'/SSF functional interface. For example, NNI messaging over this functional interface enables: + +- the management of call instances with respect to: + - establishment; + - maintenance; + - release; +- the management of CCF'-based services including CCF'-CCF' interactions (e.g. redirection request). + +### **8.2.18 Reference Point N18** + +Reference Point N18 is the SRF to CCF'/SSF functional interface, when call and connection control are integrated. For example, NNI messaging over this functional interface enables: + +- the control of bearers to SRF for IN services, with respect to: + - establishment; + - maintenance; + - release. + +Note that as an option, BICC (Bearer Independent Call Control) protocol could also be used across this reference point. + +### 8.2.19 Reference Point N19 + +Reference Point N19 is the SRF to CnCF functional interface, when call and connection control are separated. For example, NNI messaging over this functional interface enables: + +- the control of bearers to SRF for IN services, with respect to: + - establishment; + - maintenance; + - release. + +### 8.2.20 Reference Point N20 + +Reference Point N20 is the CnCF to CnCF functional interface. For example, NNI messaging over this functional interface enables: + +- the management of connection instances, with respect to: + - establishment; + - maintenance; + - modification; + - release. +- the management of bearer control associations, with respect to: + - establishment; + - maintenance; + - release. + +### 8.2.21 Reference Point N21 + +Reference Point N21 is the LMFv to SCF functional interface. For example, NNI messaging over this functional interface enables: + +- location management related IN services. + +# 9 Protocol requirements for Mobility Management + +## 9.1 Service drivers + +The following IN service drivers are detailed further in this ITU-T Recommendation, and are used as example of IN services based on mobility events: + +- 1) **Credit Check:** The subscriber may be refused registration when roaming if he has no more credit. In a similar way, he may be notified when his account has reached a predetermined threshold. Eventually, he may be authorized to register only for a restricted set of services if a certain threshold has been reached. +- 2) **Authentication Location Control:** The subscriber may be refused registration if a fraud has been detected. Consistency between successive registration location is checked: for instance, the subscriber has registered in Berlin, and 15 minutes later in Chicago. Authentication location check helps detecting such fraud. +- 3) **UPT:** IMT-2000 is required to support UPT. It is assumed here that a UPT user is allowed to register on a mobile terminal from that terminal: UPT registration is based on an IMT-2000 number, i.e. a mobile subscriber must be registered on the terminal before a UPT user starts registering. For efficient routing, the UPT SCF needs to be notified when the terminal is switched off or on in order to route the call to the appropriate destination (e.g. to the UPT voicemail when the terminal is off). In a similar manner, the UPT service may include + +service restrictions when the mobile terminal is roaming: the UPT SCF must be notified when the terminal registers in a visited network in order to check roaming authorization for the UPT user and to apply specific charging for both incoming and outgoing calls. + +- 4) **Local Advertising:** When the mobile subscriber registers, some advertising may be displayed in order to give him some local information, e.g. weather forecast. It depends on the service elements to which the user has subscribed. +- 5) **Dynamic Filtering based on User Location:** When in roaming, the subscriber may wish to filter incoming calls, if split charging is used. Dynamic filtering is activated when the user registers in a foreign visited network (roaming user) and as long as the terminal is on. + +## 9.2 Service logic interaction modes + +Among the service features detailed in 9.1, IN service logic controlling mobility management processing can be classified in two types as follows: + +- **Notification:** The SCF is only notified by the LMF that a mobility event has occurred. UPT local advertising and filtering are considered of this type. The SCF does not influence the outcome of the mobility procedure, although the IN service is provided to the user. In the example, either a messaging service is provided, or another IN service, related or not to the subscriber, is notified. +- **Control:** The SCF is able to modify the outcome of the mobility procedure, for instance by denying or cancelling authentication or registration. The credit check and authentication location control are examples of such services. + +## 9.3 LMFv State Model + +Figure 9-1 is a schematic presentation of the LMFv state model showing various possible states of the mobile terminal in the visited network. It includes identification of all entry and exit Detection Points (DPs) for each state. These states and DPs are further described below. + +DPs with no identified service drivers are shown in grey. In the future, these DPs may be removed if no service justification is provided. The removal of these DPs will not impact the validity of the model (including states, event, state transitions, and actions). + +![State transition diagram for LMFv state model. States: V_Null (initial), V_Denied, V_Initial_registration, V_Authentication_processing, V_Registration_pending, V_Active_registered, V_Inactive_registered. Transitions include V_Deregistration DP, V_Initial_reg DP, V_Authenticate DP, V_Registration DP, V_Registered DP, V_Detach DP, V_Attach DP, V_Periodic_reg DP, V_Auth_denied DP, V_Reg_Failure DP.](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +``` + +stateDiagram-v2 + [*] --> V_Null + V_Null --> V_Initial_registration : V_Initial_reg DP + V_Initial_registration --> V_Authentication_processing : V_Authenticate DP + V_Authentication_processing --> V_Registration_pending : V_Registration DP + V_Registration_pending --> V_Active_registered : V_Registered DP + V_Active_registered --> V_Inactive_registered : V_Detach DP + V_Inactive_registered --> V_Active_registered : V_Attach DP + V_Active_registered --> [*] : V_Deregistration DP + V_Active_registered --> V_Initial_registration : V_Periodic_reg DP + V_Initial_registration --> V_Denied : V_Auth_denied DP + V_Registration_pending --> V_Denied : V_Reg_Failure DP + V_Denied --> V_Null + +``` + +State transition diagram for LMFv state model. States: V\_Null (initial), V\_Denied, V\_Initial\_registration, V\_Authentication\_processing, V\_Registration\_pending, V\_Active\_registered, V\_Inactive\_registered. Transitions include V\_Deregistration DP, V\_Initial\_reg DP, V\_Authenticate DP, V\_Registration DP, V\_Registered DP, V\_Detach DP, V\_Attach DP, V\_Periodic\_reg DP, V\_Auth\_denied DP, V\_Reg\_Failure DP. + +Figure 9-1/Q.1751 – LMFv state model + +### 9.3.1 State: v\_Null + +#### **Description** + +Initial state (the mobile user is not known in the LMFv) and LMFv awaits registration request. + +#### **Entry Events** + +- Receipt of location cancellation for the MT (DP: v\_Deregistration). +- Handling of authorization or registration denied for the MT is completed (Transition from v\_Denied). + +#### **Actions** + +- Removes the subscriber profile if present and releases any other resources allocated to the MT. + +#### **Exit Events** + +- A registration request is received for the MT (DP: v\_Initial\_reg). + +### 9.3.2 State: v\_Initial Registration + +#### Description + +The user registration is initiated and decision on authentication processing is made. + +#### Entry Events3 + +- A registration request is received for the MT (DP: v\_Initial\_reg). +- A registration request is received for the MT for a new location area (while in the Active state) (DP: v\_Initial\_reg). + +#### Actions + +- Initiates the user registration, and gathers information on the user (e.g. authentication information and user identity from the previous visited network). +- Decides whether authentication is to be performed or not. The way this decision is made is operator specific. + +#### Exit Events + +- Authentication is to be performed: authenticate (DP: v\_Authenticate). +- Authentication is not to be performed: do not authenticate (DP: v\_Registration). +- Registration fails (Transition to v\_Denied). + +### 9.3.3 State: V\_Authentication Processing + +#### Description + +Authentication is processed. + +#### Entry Events3 + +- Authentication is needed (DP: v\_Authenticate). + +#### Actions + +- Retrieves new authentication parameters if none available. +- Processes authentication. + +#### Exit Events + +- Authentication is successful (DP: v\_Registration). +- Authentication failed (DP: v\_Auth\_denied). + +--- + +3 Considering real-time requirements in the network, these DPs should be implemented for notification without suspending location management processing (equivalent to TDP-N). + +### 9.3.4 State: V\_Registration\_pending + +#### Description + +The registration for the MT is processed. + +#### Entry Events3 + +- The MT has been successfully authenticated (DP: v\_Registration). +- Authentication was not to be performed: do not authenticate (DP: v\_Registration). + +#### Actions + +- Registration processing for the MT. +- A subscriber record is filled or updated with MT location information, authorization period and other information. +- The subscriber profile is retrieved. + +#### Exit Events + +- Registration succeeds (DP: v\_Registered). +- Registration fails (DP: v\_Reg\_Failure). + +### 9.3.5 State: V\_Active\_registered + +#### Description + +The MT is registered and it is assumed to be reachable. + +#### Entry Events + +- Registration has been successfully performed (DP: v\_Registered). +- A registration request is received from a detached MT (DP: v\_Attach). +- A registration request is received for the MT in the same location area (DP: v\_Periodic\_reg). + +#### Actions + +- Maintains the MT location pointer and sets the MT status to active. +- If requested, provides a routing address for establishment of an information exchange path (e.g. call delivery, short message delivery). Requests paging before sending back a routing address [this is an option of the visited network]. +- If requested, provides notification that the MT is successfully registered and active. +- If requested, provides information based on the subscriber's service profile. + +#### Exit Events + +- A registration request is received for the MT in the same location area (DP: v\_Periodic\_reg). +- A detach request is received for the MT (DP: v\_Detach). +- A registration cancellation request is received for the MT (DP: v\_Deregistration). +- A registration request is received for the MT in a new location area. (DP: v\_Inital\_reg). + +### 9.3.6 State: v\_Inactive\_registered + +#### Description + +The MT is registered, but it is not reachable. The user data and service profile are still retained in the visited network. + +#### Entry Events + +- A detach request is received for the MT (DP: v\_Detach). + +#### Actions + +- Maintains the MT location pointer and sets the MT status to inactive. +- If requested, informs that the MT is inactive. + +#### Exit Events + +- A registration request is received from the detached MT (DP: v\_Attach). +- A registration cancellation request is received for the MT (DP: v\_Deregistration). + +### 9.3.7 State: v\_Denied + +#### Description + +Handling of failure and denial from authentication and registration. + +#### Entry Events + +- Registration is denied during authentication (DP: v\_Auth\_denied) or location registration (DP: v\_Reg\_failure). + +#### Actions + +- Provides information about registration or authentication denial for the MT. +- Sets the Exception Timer. + +#### Exit Events + +- The Exception Timer elapses (Transition to v\_Null). + +## 9.4 LMFh State Model + +This subclause provides a high-level description of the Location Management State Model for the LMFh (location management function), showing Points in Location Management (PILM) and Detection Points (DP). All of the possible DP-to-PILM and PILM-to-DP transitions are illustrated. + +In the future, these DPs may be removed if no service justification is provided. The removal of these DPs will not impact the validity of the model (including states, event, state transitions, and actions). + +![State transition diagram for LMFh Location Management. States: H_Location_Unknown, H_Exception, H_Registering, H Registered, H_Old_Location_Cancelling_and_Registered. Transitions include H_Location_Update_Nack DP, H_MS_Purged DP, H_Old_Location_Cancellation_Request, H_Location_Update DP, H_Location_Update_Ack DP, H_Old_Location_Cancellation_Result, and T11106630-00.](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg) + +``` + +stateDiagram-v2 + [*] --> H_Location_Unknown + H_Location_Unknown --> H_Exception + H_Exception --> H_Location_Unknown + H_Location_Unknown --> H_Registering : H_Location_Update DP + H_Registering --> H_Registered : H_Location_Update_Ack DP + H_Registering --> H_Registering : H_Location_Update_Nack DP + H_Registered --> H_Old_Location_Cancelling_and_Registered : H_Old_Location_Cancellation_Request + H_Old_Location_Cancelling_and_Registered --> H_Registered : H_Old_Location_Cancellation_Result + H_Registered --> H_Registered : H_MS_Purged DP + H_Registered --> H_Registered : H_Location_Update_Nack DP + H_Registered --> H_Registered : T11106630-00 + +``` + +State transition diagram for LMFh Location Management. States: H\_Location\_Unknown, H\_Exception, H\_Registering, H Registered, H\_Old\_Location\_Cancelling\_and\_Registered. Transitions include H\_Location\_Update\_Nack DP, H\_MS\_Purged DP, H\_Old\_Location\_Cancellation\_Request, H\_Location\_Update DP, H\_Location\_Update\_Ack DP, H\_Old\_Location\_Cancellation\_Result, and T11106630-00. + +Figure 9-2/Q.1751 – LMFh Location Management State Model + +### 9.4.1 State H\_Location\_Unknown + +#### Description + +The location of the Mobile Subscriber is unknown and terminating services (i.e. Mobile Call termination, SMS Termination, etc.) cannot be handled. + +#### Entry Events + +- Mobile Subscriber purged (DP: H\_MS\_Purged). +- Mobile Subscriber registration in visited domain cancelled by LMFh (DP: H\_present\_location\_cancelled). +- An exception occurs (PILM: H\_Exception). + +#### Actions + +None. + +#### Exit Events + +- Mobile Subscriber registered to the mobile network (DP: H\_Location\_Update, note restrictions as described in H\_Registering state). + +### 9.4.2 State H\_Registering + +#### Description + +The Mobile Subscriber that changed between or attached to service area within the mobile network needs to transfer its service profile to the service area and the location information of the subscriber needs to be updated. + +#### Entry Events4 + +- The Mobile Subscriber registered to the mobile network (DP: H\_Location\_Update). +- The Mobile Subscriber roamed between service areas (DP: H\_Location\_Update). + +#### Actions + +- Check if the subscriber is known within the database. +- Authorize the Mobile Subscriber network access. +- Transfer the Mobile Subscriber profile towards the new service area. +- Update the location information of the Mobile Subscriber within the database. + +#### Exit Events + +- Negative response to the location update request (i.e. such as subscriber unknown, subscriber rejected, etc.) (DP: H\_Location\_Update\_Nack). +- Positive response to the location update request (DP: Location\_Update\_Ack). +- An exception occurs (PILM: H\_Exception). + +### 9.4.3 State H Registered + +#### Description + +The location of the Mobile Subscriber is known and terminating services (i.e. Mobile Call termination, SMS Termination, etc.) can be handled. + +#### Entry Events + +- Successful location update (DP: H\_Location\_Update\_Ack). +- Successful or unsuccessful location cancellation in old LMFv (PILM: H\_old\_registration\_cancellation\_result). + +#### Actions + +- Handle location requests for terminating services. +- Handle service profile updates in visited LMF. These profile updates will not impact ongoing call or other ongoing services. + +#### Exit Events + +- Decision to cancel registration (DP: H\_present\_location\_cancelled). +- Decision to delete subscriber in old LMFv (PILM: H\_old\_location\_cancellation\_request). +- Indication from LMFv that the MS has been purged (DP: H\_MS\_Purged). +- The Mobile Subscriber roamed to another Service Area (DP: Location\_Update, note restrictions as described in the H\_Registering state). +- An exception occurs (PILM: Exception). + +--- + +4 Considering real-time requirements in the network, this DP should be implemented for notification without suspending location management processing (equivalent to TDP-N). + +### 9.4.4 State H\_Old\_Location\_Cancelling\_and Registered + +#### Description + +The subscriber record in the old LMFv is cancelled. + +#### Entry Events + +- Decision by LMFh to cancel location in old LMFv (PILM: H\_Old\_Location\_Cancellation\_Request). + +#### Actions + +- Interact with old LMFv to cancel location. +- Update management information of the Mobile Subscriber within the database. + +#### Exit Events + +- Successful or unsuccessful location cancellation (PILM: H\_Old\_Location\_Cancellation\_Result). + +### 9.4.5 State H\_Exception + +#### Description + +Handling of failure and exceptions + +#### Entry Events + +- HLR exceptions occurring during the H\_registered and H\_registering states processing. + +#### Actions + +- Exception handling for a specific mobile subscriber. + +#### Exit Events + +- Exception handling completed (transition to H\_Location\_Unknown). + +## 9.5 AMF state model + +This provides a high-level description of the Authentication Management Function (AMF) State Model (see Figure 9-3) showing Points in Authentication Management (PIAM) and Detection Points (DP). All of the possible DP-to-PIAM and PIAM-to-DP transitions are illustrated. This AMF SM applies to both the home and the visited situations. An authentication state model instance is created in the AMF where authentication is processed. This excludes the process where authentication parameters are generated. Depending on the implementation, it is located either in the home or the visited network. The use of the home AMF or the visited AMF is an operator decision. + +In the future, these DPs may be removed if no service justification is provided. The removal of these DPs will not impact the validity of the model (including states, event, state transitions, and actions). + +![State transition diagram for the AMF State Model. It shows three states: A_Null, A_Authentication_Processing, and A_Awaiting_Challenge_Response. Transitions are triggered by events (DP) or internal processing (PIAM).](692541e65db4dc852988ce77ebb60ce5_img.jpg) + +``` + +stateDiagram-v2 + [*] --> A_Null + A_Null --> A_Authentication_Processing : A_Authentication_Attempt DP + A_Authentication_Processing --> A_Awaiting_Challenge_Response : A_Challenge_Issued DP + A_Awaiting_Challenge_Response --> A_Authentication_Processing : A_Challenge_Response_Received + A_Authentication_Processing --> A_Null : A_Authentication_Processing_Failure + A_Authentication_Processing --> [*] : A_Authentication_Denied DP + A_Authentication_Processing --> [*] : A_Authenticated DP + +``` + +T11106640-00 + +State transition diagram for the AMF State Model. It shows three states: A\_Null, A\_Authentication\_Processing, and A\_Awaiting\_Challenge\_Response. Transitions are triggered by events (DP) or internal processing (PIAM). + +Figure 9-3/Q.1751 – AMF State Model + +### 9.5.1 State: A\_Null + +#### Description + +Initial state (the AMF awaits an authentication request from the mobile user). + +#### Entry Events + +- Authentication processing failure occurs (PIAM: A\_Authentication\_Processing\_Failure). +- Authentication is denied (DP: A\_Authentication\_Denied DP). +- Authentication is successful (DP: A\_Authenticated DP). + +#### Actions + +- None. + +#### Exit Events + +- An authentication request is received (DP: A\_Authentication\_Attempt). + +### 9.5.2 State: Authentication\_Processing + +#### Description + +The user authentication processing takes place. + +#### Entry Events + +- An authentication request is received (DP: A\_Authentication\_Attempt DP). +- The result of the Awaiting\_Challenge\_Response is received (PIAM: A\_Challenge\_Response\_Received). + +#### Actions + +- Call count is updated if necessary. +- Privacy keys are generated if necessary. +- Authentication processing is performed and depending on the outcome of the State: A\_Awaiting\_Challenge\_Response, either Authentication is successful or it is denied. + +#### Exit Events + +- Authentication processing failure occurs (PIAM: A\_Null). +- An authentication challenge is issued (SCF processing could occur at this point) (DP: A\_Challenge\_Issued DP). +- Authentication is successful (DP: A\_Authenticated). +- Authentication is denied (DP: A\_Authentication\_Denied). + +### 9.5.3 State: Awaiting\_Challenge\_Response + +#### Description + +The AMF waits for a response to the authentication challenge. + +#### Entry Events + +- An authentication challenge was issued (DP: A\_Challenge\_Issued DP). + +#### Actions + +- None. + +#### Exit Events + +- The AMF receives a response to the authentication challenge (PIAM: A\_Challenge\_Response\_Received). +- Authentication processing failure occurs (PIAM: A\_Null). + +## 9.6 Mobility Management Functional Communications + +Figure 9-4 has been reproduced from ITU-T Recommendation Q.1711, extended to show the CN-CN interface. + +The bold relationships fall – either fully or partially – within the scope of Mobility Management. + +![Figure 9-4/Q.1751 – The IMT-2000 Functional Model (Mobility Management). The diagram shows functional elements across four domains: UIM, MT, RAN, and CN. A dashed line separates the 'Communication and Service Control' layer (top) from the 'Radio Access Control' layer (bottom).](7ae836e598020d937ed1478c2ef13025_img.jpg) + +The diagram illustrates the IMT-2000 Functional Model for Mobility Management, organized into four vertical domains: UIM, MT, RAN, and CN. A horizontal dashed line divides the model into two layers: 'Communication and Service Control' (top) and 'Radio Access Control' (bottom). + +- UIM (User Identity Module):** Contains UIMF. +- MT (Mobile Terminal):** Contains MGPF, PSCAF, CCAF, CnCAF, MCF, RACAF, and MRTR. +- RAN (Radio Access Network):** Contains GPF, SNCF, SIBF, RACF, RFTR, and ARF. +- CN (Core Network):** Contains GPCF, PSGCF, PSCF, AMF, SDF, LMF, SCF, SRF, CCF/SSF, CnCF, and SACF. + +Key connections include: + + +- UIMF connects to MGPF, PSCAF, and MCF. +- MGPF connects to GPCF. +- PSCAF connects to PSCF. +- CCAF connects to CCF/SSF. +- CnCAF connects to CnCF. +- MCF connects to SACF. +- RACAF connects to RACF. +- MRTR connects to RFTR. +- GPF connects to SACF. +- SNCF, SIBF, and RACF are interconnected. +- ARF connects to RACF and SACF. +- PCF elements (PCAF, GPCF, PSCF) connect to AMF and LMF. +- AMF connects to SDF, LMF, and SCF. +- LMF connects to SCF and CCF/SSF. +- SCF connects to SRF and CCF/SSF. + +Figure 9-4/Q.1751 – The IMT-2000 Functional Model (Mobility Management). The diagram shows functional elements across four domains: UIM, MT, RAN, and CN. A dashed line separates the 'Communication and Service Control' layer (top) from the 'Radio Access Control' layer (bottom). + +Figure 9-4/Q.1751 – The IMT-2000 Functional Model (Mobility Management) + +## 9.7 Choice of Protocol Suite + +Various mobility protocols already exist for 2G systems, such as GSM MAP and IS-41. They have all been specifically designed and optimized for these 2G systems and service capabilities. However, the main drawback of these protocols is that they cannot easily support inter-family communication because of their specific nature and design (i.e. the syntax and semantics of arguments and results of these Mobility Management operations are heavily coupled with the related 2G services and architecture). + +The 2G protocols need enhancements to support the inter-family roaming between the different IMT-2000 members of systems. Therefore, the challenge of making the common NNI protocol for Mobility Management feasible for inter-family roaming relies mainly on creating protocol elements that should not be restricted to a particular mobile service and radio access technology. In other words, it should be generic enough to fit with the different members/systems of IMT-2000 from the NNI perspective. One way to proceed forward in that direction is to derive generic operations based on common parameters for IMT-2000 services that will be used by these different members. Attention should also be given to make the evolution path from the existing 2G systems towards the 3G common NNI as smooth as possible. + +# 10 Protocol requirements for VHE Service Control + +## 10.1 General requirements + +- 1) For the VHE Service Invocation information elements addition of the following to the relevant operation definitions in INAP are recommended: + - subscriber is a mobile subscriber; + +- mobile subscriber identity (e.g. IMUI); + - terminal capabilities (e.g. voice, data, etc.); + - location information (e.g. latitude and longitude, cell site, elevation, precision, etc.). +- 2) The trigger profile that is dynamically and geographically placed needs to include, in addition to the identification of the triggers, trigger criteria and service logic addresses associated with the triggers, protocol version information to be used to the indicated service logic program. The protocol version is required to ensure that the message sent to the SLP is of a version not higher than the SLP that is equipped to recognize and deal with. +- 3) For the VHE service Information flows involving the use of a specialized resource, the information flows should be aligned with the IN specifications. +- 4) For the VHE service provisioning, the SCF and SRF in the "supporting network" might be anywhere. As such, appropriate addressing mechanisms are required. The addressing capabilities of the INAP protocol for this aspect should be reviewed to ensure adequacy. + +## 10.2 Service Control Functional Communications + +Figure 10-1 has been reproduced from ITU-T Recommendation Q.1711. It is extended here to show the CN-CN interface for the service control capability. + +The bold relationships fall – either fully or partially – within the scope of Service Control Signalling. + +![Figure 10-1/Q.1751 – The IMT-2000 Functional Model (Service Control). This diagram illustrates the functional architecture of the IMT-2000 network, divided into four vertical domains: UIM, MT, RAN, and CN. A horizontal dashed line separates the 'Communication and Service Control' layer (top) from the 'Radio Access Control' layer (bottom). In the UIM domain, the UIMF is connected to the MT's MGPF, PSCAF, CCAF, CnCAF, and MCF. The MT domain includes MGPF, PSCAF, CCAF, CnCAF, MCF, RACAF, and MRTR. The RAN domain includes GPCF, PSGCF, PSCF, GPF, SNCF, SIBF, RACF, RFTR, and ARF. The CN domain includes AMF, SDF, LMF, SCF, SRF, CCF/SSF, CnCF, and SACF. Bold lines represent Service Control Signalling paths, notably between UIMF and SACF, and between various CAF/CF elements across domains. A reference code 'T11106660-00' is present in the bottom right of the diagram area.](9870bf462aa0d916a16d14b5a100c60a_img.jpg) + +Figure 10-1/Q.1751 – The IMT-2000 Functional Model (Service Control). This diagram illustrates the functional architecture of the IMT-2000 network, divided into four vertical domains: UIM, MT, RAN, and CN. A horizontal dashed line separates the 'Communication and Service Control' layer (top) from the 'Radio Access Control' layer (bottom). In the UIM domain, the UIMF is connected to the MT's MGPF, PSCAF, CCAF, CnCAF, and MCF. The MT domain includes MGPF, PSCAF, CCAF, CnCAF, MCF, RACAF, and MRTR. The RAN domain includes GPCF, PSGCF, PSCF, GPF, SNCF, SIBF, RACF, RFTR, and ARF. The CN domain includes AMF, SDF, LMF, SCF, SRF, CCF/SSF, CnCF, and SACF. Bold lines represent Service Control Signalling paths, notably between UIMF and SACF, and between various CAF/CF elements across domains. A reference code 'T11106660-00' is present in the bottom right of the diagram area. + +Figure 10-1/Q.1751 – The IMT-2000 Functional Model (Service Control) + +## 10.3 Choice of Protocol Suite + +| Relationship | Initial Protocol Proposal | +|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SCF-SDF | INAP + extensions for mobility. | +| SCF-SRF | INAP + extensions for mobility. | +| SCF-CCF/SSF | INAP + extensions for mobility. | +| SCF-AMF | INAP-like based on AMF state model. Refer to clause 9/Q.1721 for information flows. | +| SCF-LMF | INAP-like based on LMF state model to be defined. | +| SRF-CCF/SSF | Appropriate Bearer Control protocol. | +| SCF-UIMF (packet via PSCF, PSCAF) | Transport will be provided via IPv4 with potential evolution to IPv6. | +| SCF-UIMF (circuit, via SACF, MCF) | Options identified: | + +# 11 Protocol requirements for Call and Bearer Control + +## 11.1 General requirements + +**Call Detail Record (CDR):** This procedure allows to transfer CDR data from the serving network to the home network. Furthermore, real-time CDR transfer should be provided. However, in order to minimize data transfer only call reference tags and data necessary for call processing should be transferred. + +## 11.2 Choice of switching principles + +The switching technologies (circuit switched, ATM, AAL2, frame relay, ...) shall be selected by the operator or service provider. + +## 11.3 Call and Bearer Control functional communications + +Figures 11-1 and 11-2 have been reproduced from ITU-T Recommendation Q.1711, extended to show the CN-CN interface. + +The bold relationships fall – either fully or partially – within the scope of Call and Bearer Control Signalling. + +![Functional model diagram showing components across UIM, MT, RAN, and CN domains. It is divided into 'Communication and Service Control' and 'Radio Access Control' sections by a dashed line. Components include MGPF, PSCAF, CCAF'', UIMF, MCF, GPCF, PSGCF, PSCF, AMF, LMF, SDF, SCF, SRF, CCF/SSF, SACF, GPF, SNCF, SIBF, RACAF, RACF, ARF, MRTR, and RFTR.](f57c7b37d7a05a99618104f390089f03_img.jpg) + +The diagram illustrates the IMT-2000 functional model, organized into five vertical domains: UIM, MT, RAN, CN, and CN. A horizontal dashed line separates the top section, labeled 'Communication and Service Control', from the bottom section, labeled 'Radio Access Control'. + - In the UIM domain, UIMF is connected to MGPF and MCF. + - In the MT domain, MGPF connects to PSCAF and CCAF''; PSCAF connects to CCAF''; CCAF'' connects to MCF; MCF connects to RACAF; RACAF connects to MRTR. + - In the RAN domain, GPCF connects to PSGCF and PSCF; PSGCF connects to PSCF; PSCF connects to SACF; SACF connects to GPF; GPF connects to SNCF; SNCF connects to SIBF; SIBF connects to RACF; RACF connects to ARF; RACF connects to RFTR. + - In the CN domain, GPCF connects to AMF and LMF; AMF connects to SDF and LMF; LMF connects to SCF; SCF connects to SRF and CCF/SSF; CCF/SSF connects to the final CN domain. + - Cross-domain connections: MGPF (MT) to GPCF (CN); PSCAF (MT) to PSCF (CN); CCAF'' (MT) to CCF'' (RAN) to CCF/SSF (CN); UIMF (UIM) to SACF (CN); MCF (MT) to SACF (CN); RACAF (MT) to RACF (RAN); MRTR (MT) to RFTR (RAN). + - A label 'T11106670-00' is present near the dashed line on the right side. + +Functional model diagram showing components across UIM, MT, RAN, and CN domains. It is divided into 'Communication and Service Control' and 'Radio Access Control' sections by a dashed line. Components include MGPF, PSCAF, CCAF'', UIMF, MCF, GPCF, PSGCF, PSCF, AMF, LMF, SDF, SCF, SRF, CCF/SSF, SACF, GPF, SNCF, SIBF, RACAF, RACF, ARF, MRTR, and RFTR. + +NOTE – CCF'' is introduced to address protocol conversion functionality (related to Call and Bearer Control) between MT-RAN and RAN-CN interfaces. + +**Figure 11-1/Q.1751 – The IMT-2000 functional model + Alternative 1: Integrated Call Control and Connection Control FEs** + +![Figure 11-2/Q.1751 – The IMT-2000 functional model. This diagram illustrates the functional architecture of IMT-2000, divided into five vertical domains: UIM, MT, RAN, CN, and CN. A horizontal dashed line separates the 'Communication and Service Control' (top) from the 'Radio Access Control' (bottom). Key functional entities include MGPF, PSCAF, CCAF', CnCAF, UIMF, MCF, GPCF, PSGCF, PSCF, AMF, LMF, SCF, SDF, SRF, CCF'/SSF', SACF, GPF, SNCF, SIBF, RACAF, RACF, ARF, MRTR, and RFTR. Lines represent functional relationships between these entities across the domains.](e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg) + +Figure 11-2/Q.1751 – The IMT-2000 functional model. This diagram illustrates the functional architecture of IMT-2000, divided into five vertical domains: UIM, MT, RAN, CN, and CN. A horizontal dashed line separates the 'Communication and Service Control' (top) from the 'Radio Access Control' (bottom). Key functional entities include MGPF, PSCAF, CCAF', CnCAF, UIMF, MCF, GPCF, PSGCF, PSCF, AMF, LMF, SCF, SDF, SRF, CCF'/SSF', SACF, GPF, SNCF, SIBF, RACAF, RACF, ARF, MRTR, and RFTR. Lines represent functional relationships between these entities across the domains. + +**Figure 11-2/Q.1751 – The IMT-2000 functional model +Alternative 2: Separated Call Control and Connection Control FEs** + +## 11.4 Choice of Protocol Suite + +The usage of the following protocols for IMT-2000 CS-1 are applicable: + +| Functional relationship | Protocol proposal | +|-------------------------|-------------------------------------------------------------------------------------------------------------| +| CCF'-CCF' | BICC
N-ISUP for STM | +| CnCF-CnCF | Q.AAL2 for ATM AAL2
B-ISUP for ATM AAL1

NOTE – Others like PNNI/ATM or AINI/ATM are not excluded. | + +Due to timing constraints, the following functional relations have been assigned a lower priority within IMT-2000 CS-1 time-frame. + +| Functional relationship | Protocol proposal | +|-------------------------|----------------------------------------------------------------------| +| CCAF'-CCF' | Family member specific protocol within the IMT-2000 CS-1 time-frame. | +| CnCAF-CnCF | | +| CnCF-CnCF | | +| PSCAF-PSCF | | +| PSCF-PSGCF | | + +Two domains have to be distinguished, the PSTN/ISDN-domain and the packet data domain as they pertain to the following protocols: + +### 1) *ISDN/PSTN service domain* + +- a) Call control: BICC, N-ISUP for STM; +- b) Bearer control: B-ISUP for ATM AAL1; +Q.AAL2 for ATM AAL2. + +Flexibility is needed with respect to the IMT-2000 transport technology to meet the requirements of a deregulated, dynamic market. + +### 2) *Packet data service domain* + +- a) Call control: Not required. +- b) Bearer control: ATM AAL5 bearer. +- c) Network layer: Internet protocol (IP). + +Flexibility is needed with respect to the IMT-2000 transport technology to meet the requirements of a deregulated, dynamic market. Therefore different bearer types shall be allowed in IMT-2000 CS-1. + +## 11.5 Multimedia calls + +The IMT-2000 multimedia call requirements include the capability of merging the media streams on a single connection. The media are considered as different types of data streams (e.g. voice, data, image, etc.). These media can be multiplexed on a single connection and be controlled (e.g. adding, dropping media) by existing ITU-T Recommendations (e.g. H.323, H.245, H.248) operating "in-band" within the bearer connection. The requirement for AAL2 CS-2 is that the bandwidth of the AAL2 connection must be able to be modified. This requirement is addressed by AAL2 signalling CS-2. + +## 11.6 Multi-party calls + +The add/drop parties capabilities require only Point-To-Point communication configurations to a server or bridge (configuration 6), which can simulate the 2, 3, 4 and 5 configurations from a user's viewpoint. This Configuration Type 6 is a communication configuration that includes a server node (e.g. MultiPoint Communication Unit, MCU) within the network that can connect multiple Point-To-Point Connections. This will provide the end-user the possibility of MultiPoint-To-MultiPoint communications. The communication configuration Type 1 and 6 still allows for add/drop parties initiated by the root, leaf or third party (see TRQ 2001). + +Furthermore, the multi-party call capability includes only the add/drop party capability initiated by the root or leaf. No third Party Add/Drop Party Capability is required for IMT-2000 CS-1. In addition to this, it is required to include the root notification signalling, when a leave initiated add/drop Party event occurs. + +# 12 Protocol requirements for Packet Service Control + +The functional elements that will support packet data services and their relationships across CN boundaries are shown in Figure 12-1. This clause identifies a set of requirements that pertains to NNI that supports the packet data services. + +![Diagram of Packet Data Network-to-Network Interfaces (Figure 12-1/Q.1751).](e151d3468319b81f042ca232c4d82e4b_img.jpg) + +The diagram illustrates the network architecture for packet data services across two core networks, Core Network #1 and Core Network #2. In Core Network #1, the RACF is connected to the PSCFv, which is connected to the LMFv, which is connected to the AMFv. In Core Network #2, the PSGCFh is connected to the LMFh, which is connected to the AMFh. An NNI (Network-to-Network Interface) connects the PSCFv in Core Network #1 to the PSGCFh in Core Network #2. Another NNI connects the LMFv in Core Network #1 to the LMFh in Core Network #2. The PSGCFh in Core Network #2 is also connected to the INTERNET/RDP. + +Diagram of Packet Data Network-to-Network Interfaces (Figure 12-1/Q.1751). + +T11111810-01 + +Figure 12-1/Q.1751 – Packet Data Network-to-Network Interfaces + +## 12.1 The PSCF to PSGCF Interface protocol + +The two functional capabilities that the PSCF and PSGCF will provide are: + +- 1) transfer of user data between these two entities; and +- 2) interaction between these two entities for updates of packet service and routing contexts. + +These two functions and the associated information flow belong to two disjoint logical planes: the user plane and the control plane. The first function identified above belongs to the user plane, while the second function belongs to the control plane. + +The functional requirements listed below pertain to both the user plane and the control plane when the PSCF and PSGCF reside in two different Core Networks (CNs). + +- 1) When the PSCF and PSGCF reside in two different CNs, these two entities should be interconnected over an IP network. +- 2) When the PSCF and PSGCF are connected over the public Internet, there should be a security association between the PSCF and PSGCF. +- 3) When the home CN authorizes the Mobile Terminal (MT) for data services in a visited CN, the home CN should instruct the visited CN to select either a specific PSGCF or propose allocation of a local PSGCF in the visited CN to handle a data service session. +- 4) When the data service session is established the allocated PSGCF should be fixed during the entire duration of the data service session. The visited core network in which this PSGCF resides becomes the anchor core network, CNa, for the data session. +- 5) When the MT initiates a data service session, the PSCF should be allocated by the CN where the data service session was initiated. +- 6) When the MT roams into a visited CN during an established service session, the visited CN should dynamically allocate a new PSCF to handle the respective service session. A succession of PSCFs may be allocated to the MT as it roams inside the visited CN (during the intra-CN roaming). + +- 7) The IMSI or NAI may be used as a unique service-session identifier in all protocol transactions. If the MT supports several simultaneous service sessions, an associated Session Number identifier should be used to uniquely identify each individual service session. + +### **12.1.1 User plane requirements** + +- 1) The PSCF and PSGCF should transfer the users' information over an IP network by employing a two-way IP tunnel. +- 2) The user plane may incorporate a mechanism that will support the concurrent existence of a multiplicity of two-way tunnel-connections inside the IP tunnel that connects the PSCF and PSGCF. +- 3) The user plane should incorporate an optional mechanism (e.g. encapsulation scheme) that will prevent out-of-sequence deliveries of users' packet data units across the tunnel-connection. +- 4) At any given time, each tunnel-connection between the PSCF and PSGCF should have a specified lifetime. The lifetime of a tunnel-connection should be extendible. Whenever the lifetime of a given tunnel-connection expires, the respective tunnel-connection should be cleared. + +### **12.1.2 Control plane requirements** + +- 1) The control protocol between the PSCF and PSGCF should be able to establish individual tunnel-connections, extend the lifetime of the established tunnel-connections, and clear the established tunnel-connections. +- 2) The PSCF and PSGCF should employ the UDP to exchange control messages. These messages may be protected by an IP security tunnel. +- 3) A dedicated, well-known UDP port in the PSGCF should terminate a control channel over which control messages between the PSCF and PSGCF should be exchanged. +- 4) The PSCF and PSGCF should employ two-way (i.e. two-message) handshake protocol when establishing a tunnel-connection or extending the lifetime of an established tunnel-connection. The one-way protocol should be used to clear an established tunnel-connection. +- 5) The PSCF and PSGCF should be able to establish a security association with each other and perform encryption of data and authentication and integrity checking of control messages. + +## **12.2 The LMFp to LMFp Interface Protocol** + +To access packet data services, the roaming MT will register with the visiting IMT-2000 network by employing common authentication and terminal registration procedures, and request access to packet data facilities. An associated accounting record may be kept to register the usage of packet data resources. The CN architecture should allow for separation of LMF (and associated AMF) capabilities that pertain to access facilities and LMFp (and associated AMFp) capabilities that pertain to the packet data services. The requirements listed below refer to the interaction between visited and home LMFps that reside in two different CNs and incorporate only the packet data capabilities. + +- 1) When exchanging information that pertains to packet data services, the visiting LMFp and home LMFp should be able to convey the respective information over an IP network. +- 2) A security association between a visiting LMFp and a home LMFp should exist before information can be exchanged between these two entities. The security association may be automatically established, prearranged, or a visiting LMFp and a home LMFp can communicate through a trusted third party (e.g. broker) with whom they have, respectively, security association. + +- 3) The protocol between the visiting LMFp (and associated AMFp) and the home LMFp (and associated AMFp) should enable the visited CN to authenticate and authorize the visiting MT to use the packet data services in the visited CN. +- 4) If the home LMFp fails to authenticate the MT, the visited CN will not allow packet data service. The visited CN will assume agreement for charging if the home network authorizes service. +- 5) When using packet data services, the visited MT may identify itself to the packet data network only with its NAI. The visited LMFp should be able to identify and locate the home LMFp based on the NAI. +- 6) The visited LMFp should be able to request, and the home LMFp should be able to identify the PSGCF that the visited CN should use for the respective packet data session. +- 7) The visited LMFp should be able to request, and the home LMFp should be able to supply an IP address that will be used by the MT during the respective packet data session. +- 8) The protocol between the LMFp peers should provide a mechanism to convey accounting information across this interface. +- 9) The LMFp peers should use a unique Session Identifier (Session ID) for each packet data session they mutually handle. +- 10) The LMFp peers should employ a set of Response Codes that should be included in every response message. The Response Code will provide reply information concerning the request (e.g. service denied, error condition, and bad password) to the requesting peer. + +For packet data services, the IMT-2000 network will provide two levels of security – the access network security and the packet data network security. The access network security includes radio signal encryption and radio access key management for authentication of the MT. The packet data network security includes encryption and tunnelling of packets over the public Internet and authentication of the MT with the IMT-2000 network by using a secret key. The LMFp to LMFp interface requirements listed below pertain to the packet data network security. + +- 1) For purposes of authentication and service authorization, the home CN may be able to provide security information regarding the MT to the visited CN. +- 2) A mechanism should exist by which the visited LMFp will be able to convey to the home LMFp the Challenge and Challenge response values. The Challenge value will contain the value that the visited CN passed to the visiting MT. The Challenge response value will contain the value that the visiting MT has generated using the Challenge value and the secret that the visiting MT shares with its home CN. +- 3) A mechanism should exist by which the visited LMFp and home LMFp will be able to exchange security parameters (e.g. SPI and security keys). The security parameters that were received from home LMFp will enable the visited CN to establish a two-way security association with the visiting MT, and between the PSCF in visited CN and the PSGCF in home CN. + +# APPENDIX I + +## Guidance on trigger concepts and usage + +## I.1 Purpose + +The purpose of this informative appendix is to provide guidance on trigger usage through an informal discussion of some essential elements of trigger arming and processing within IMT-2000. It is expected that these basic guidelines will be further enhanced and optimized to fit the specific requirements (e.g. operational needs) of the different IMT-2000 family members. + +## I.2 Introduction + +This appendix begins with a discussion of some principles and concepts. It then develops trigger usage and application guidelines based on these principles and concepts. Note that the principles and concepts, while based on the call related BCSM, are also applicable to the Location Management and Authentication State Models. The remaining subclauses of this appendix which discuss Dynamic Trigger Arming and Distribution of Triggers, require further consideration to determine whether these guidelines are appropriate for triggering Location Management and Authentication Management services. + +Refer to IN ITU-T Recommendations Q.1231 and Q.1238 (Parts 1 and 2) for a further discussion on triggering and the BCSM call modelling principles on which the following subclauses are based. + +## I.3 Principles and concepts + +- 1) Triggers are service independent: + +A fundamental concept of triggering is that triggers are service independent. This means that when an armed trigger is encountered and its criteria satisfied, the MSC does not know which service or services will be invoked as a result of the message it sends to the Service Logic Program (SLP) at the SCF. + +- 2) Triggers include Service Logic Address Information: + +For the case of wireless subscribers, the service triggers, which implicitly indicates the SCF to be consulted, is located with the subscribers service profile located in the LMFh. + +- 3) The SLP will respond with an executable instruction: + +The MSC expects that the SCF (SLP) will respond with an appropriate instruction on how to process the call. The MSC must consider the received instruction for appropriateness considering its current view of the call. In some circumstances, call-related events may have occurred between the query to the SCF (SLP) and the response from the SCF that make the instruction received inappropriate. One example is caller abandon. + +- 4) Triggers are only acted upon when they are encountered in the BCSM: + +Some circumstances provide information earlier than when the BCSM looks for it. For example notification of Busy as a result of a mobility management procedure (e.g. location request). The O-BCSM model does not recognize this busy condition until call processing has progressed to a point where a T-BCSM is instantiated and the T-BCSM has progressed to the point where it encounters the T\_Busy DP. If the busy status is not consumed there, the T-BCSM propagates it back to the O-BCSM for potential use there. + +Note that the discussion here describes the IN modelling (Refer to the Q.1238 series of ITU-T Recommendations). An implementation is free to consider the busy information as soon as it is available in order to optimize its performance, but must remain aware of the possibility of other services being invoked between the time when the busy information is received, and when the modelling indicates it should be considered. + +- 5) Triggers take precedence in Order: Subscriber, Group, Office: + +This sequence enables service providers to offer selected subscribers the use of services that are not available to the general subscriber base. Examples include access to enhanced services such as conference calling, etc. Similarly, this trigger precedence order allows service providers to deny selected subscribers services available to the general subscriber based. Examples include restricting calling parties to certain area codes, etc. + +- 6) Each trigger is fully considered before the next trigger: + +Triggers are listed in precedence order. This principle indicates that a given trigger type is considered for subscriber, group and office applicability before proceeding to the next trigger type in the precedence order. + +It is possible to further refine items 5) and 6) to take into consideration precedence and sequencing of trigger criteria but this depends on the specific service and operational requirements of the particular IMT-2000 family member. For example, backwards compatibility with existing 2G systems may require specific handling of service triggers when operating in the context of 3G environment. + +## **I.4 Dynamic trigger arming** + +A subscriber's trigger profile is stored with other service related information in the LMFh. This trigger profile is considered to be "static" because it changes slowly, if at all. That is, it remains the same unless the subscriber adds or deletes a triggered service from the profile, or turns on or off or modifies one of the services that are subscribed to. It is this "static" profile that is dynamically geographically placed as the subscriber roams and is served by different MSCs. + +A subscriber's trigger profile may be modified for a given call instance without affecting the "static" profile. These modifications to the profile do not survive after the current call. On release of the call, all such modifications disappear. This is called "dynamic" trigger arming. + +Dynamic trigger arming is a powerful capability. A powerful capability which can also be readily misused. It is incumbent on service providers using this capability to understand and deal with the potential side-effects of the use of this capability. For example, with multiple SCPs providing services, inappropriate use of the dynamic trigger arming capability may cause undesired service interactions or failures from the end-user's point of view. If not well coordinated, a service logic program on one SCP may overwrite triggers armed for a service logic program on another SCP. This may cause the other service to fail, or to not run at all, or to run incorrectly. With multiple service providers involved, they are unlikely to be aware of the full suite of services subscribed to and the effects they may have on these other, unknown-to-them services. + +## **I.5 Distribution of triggers** + +Since wireless subscribers are inherently mobile, it is necessary to consider how the triggers for their services should be distributed. A mobile call origination or termination can occur anywhere and the roaming subscriber may be anywhere in the roaming areas available to the called mobile subscriber, it is necessary to distribute service processing in an optimal manner. It is assumed that when a service provider offers a set of services to a subscriber, the service provider should ensure that the services are an appropriate, coherent, and internally consistent set that will interact with each other in a manner desired by the subscriber. + +The options for the dynamic geographic placement of statically armed originating and terminating triggers are at the Originating, Terminating or Gateway MSC. If identical trigger profiles are placed at the Originating, Terminating and Gateway MSC, then some services may be executed twice leading to undesirable results. Given that identical trigger profiles should not be placed everywhere, criteria are needed for use in deciding where to place triggers. + +The following criteria is provided to assist the decision-making process to determine where to place the service triggers. + +For optimization of network resources, outgoing call originating triggers should be placed as close as practicable to the calling subscriber. In general, this means that the subscriber's originating triggers should be placed at the originating MSC when the MS registers. + +For calls to a subscriber, in order to ensure optimal use of network bearer connection resources, it is desirable to place triggers for services that may prevent call completion, as close to the originating point of the call as possible. Hence, a set of terminating triggers may be placed at the Originating or Gateway MSC for use in a BCSM being run as a proxy for the called subscriber. These triggers should be indicated in the information returned with the routeing (or location update) request. However, it should be noted that placing trigger profiles in the Local Exchanges (MSC) costs more and commits the network service providers to a higher cost deployment of the service before the market for the service is proven. Generally unless the Service requires high availability (high usage or low responses times) or requires deployment in the Local Exchanges (MSCs) for technical reasons the cost advantages to deployment in transit exchanges or interrogating gateways need to be considered. + +If the call may be deflected to another destination, this should be done as close to the source of the call as possible (e.g. Originating or Gateway MSC). Service example is call forwarding to a voicemail service. + +Security of Signalling may require that Triggers be deployed in a transit or a gateway node. Thus, if the SSF is in one network and the SCP is in a different network, STPs and GTT will be required at the signalling transport level. The use of STPs and GTT will reduce the speed of the signalling and will require extra security for the service providers to secure their protocol context. + +High usage of a service requires it to be deployed in the visited MSC, Originating or Terminating. + +The need for very short response times requires it to be deployed in the visited MSC, Originating or Terminating. + +Networks which employ Optimal Routing may require triggers to be deployed in the visited MSC, Originating or Terminating, As triggering at the Interrogating (transit) node may cause complex routing, e.g. tromboned legs. + +Signalling Timeouts may require that the originating triggers are placed in the Originating MSC and that the terminating triggers are placed in the Terminating MSC. Since, a number of specific conditions require the MSC to reset the ISDN short timeouts on the network access whilst the SCP is processing the application, this cannot be achieved at other exchanges. + +Access to Location Area information may require that the originating triggers are placed in the Originating MSC and that the terminating triggers are placed in the Terminating MSC. This requirement may be alleviated by future signalling systems, which allow the LAI information to be relayed in the call path as CLI may be today. However, the screening of such parameters at network boundaries may render the signalling ineffective. + +Home Network Applied Charging may require that Triggers be deployed in a transit or gateway node. Since if, the SSF is in one network and the SCP is in a different network. The Home network may never receive the call. Indeed it may be removed from the call path and so cannot secure the charging applied to the call. Other charging methods may require that service triggers are also deployed as close as possible to the called party. For example, services which require specific knowledge of radio interface parameters used such as, Cell ID, number of radio channels used etc., to ensure accurate calculation of charges. Other service examples include Mobile Terminating prepaid and Advice of Charge. + +Local Area services will require that the originating triggers are placed in the Originating MSC and that the terminating triggers are placed in the Terminating MSC. For example, user exclusion or privileges on a base station. This may be the equivalent to line-based services in the fixed network. + + + +# 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/Q/T-REC-Q.1763-200710-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1763-200710-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4af97f97be3110b490d92eca117356f79033801e --- /dev/null +++ b/marked/Q/T-REC-Q.1763-200710-I_PDF-E/raw.md @@ -0,0 +1,1177 @@ + + +**ITU-T** + +**Q.1763/Y.2803** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(10/2007) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for IMT-2000 + +SERIES Y: GLOBAL INFORMATION +INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS +AND NEXT-GENERATION NETWORKS + +Next Generation Networks – Generalized mobility + +--- + +**FMC service using legacy PSTN or ISDN as the +fixed access network for mobile network users** + +ITU-T Recommendation Q.1763/Y.2803 + +# ITU-T Q-SERIES RECOMMENDATIONS + +## SWITCHING AND SIGNALLING + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3999 | + +For further details, please refer to the list of ITU-T Recommendations. + +## **ITU-T Recommendation Q.1763/Y.2803** + +# **FMC service using legacy PSTN or ISDN as the fixed access network for mobile network users** + +## **Summary** + +In a fixed-mobile convergence (FMC) network environment, convergence between legacy PSTN and ISDN and mobile networks is a typical example of a pre-IMS FMC network environment. ITU-T Recommendation Q.1763/Y.2803 defines the service features, service architecture, and capability requirements of the convergence service between legacy PSTN and ISDN and mobile networks. An example of the implementation of the converged service is provided. + +## **Source** + +ITU-T Recommendation Q.1763/Y.2803 was approved on 29 October 2007 by ITU-T Study Group 19 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## **Keywords** + +Fixed-mobile convergence, Intelligent Network, ISDN, mobile network, PSTN. + +## 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 ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 4 | +| 6 Service features..... | 4 | +| 6.1 Service numbering..... | 4 | +| 6.2 Service subscription..... | 4 | +| 6.3 Registration and authentication for legacy fixed network access ..... | 5 | +| 6.4 Call handling ..... | 5 | +| 6.5 Extent of mobility provided by PAM service..... | 6 | +| 7 Architecture ..... | 7 | +| 7.1 Architecture alternatives..... | 7 | +| 7.2 Functional entities ..... | 8 | +| 7.3 Information flows overview ..... | 11 | +| 7.4 Allocation of functional entities to physical nodes ..... | 14 | +| 8 Capability requirements..... | 17 | +| 8.1 User authentication through PSTN/ISDN access ..... | 17 | +| 8.2 User identification and routing..... | 19 | +| 8.3 User profile treatment..... | 19 | +| 8.4 Emergency call handling ..... | 20 | +| 8.5 Video call handling..... | 20 | +| 9 Implementation of PAM service using IN approach ..... | 20 | +| 9.1 Network configuration..... | 20 | +| 9.2 Signalling requirements ..... | 23 | +| 9.3 Call flows..... | 23 | +| Bibliography..... | 30 | + + + +## **FMC service using legacy PSTN or ISDN as the fixed access network for mobile network users** + +# **1 Scope** + +This Recommendation describes the service features, service architecture and capability requirements for using the legacy PSTN or ISDN as a fixed access network for mobile network users (PAM service) and provides an example of the implementation of the PAM service. + +Mechanisms to support the basic voice and video telephony services are described. + +The mobile networks discussed in this Recommendation refer specifically to GSM/UTRAN [ITU-T Q.1741] networks and ANSI-41/cdma2000 [ITU-T Q.1742] 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 Q.1224] ITU-T Recommendation Q.1224 (1997), *Distributed functional plane for intelligent network Capability Set 2*. +- [ITU-T Q.1701] ITU-T Recommendation Q.1701 (1999), *Framework for IMT-2000 networks*. +- [ITU-T Q.1702] ITU-T Recommendation Q.1702 (2002), *Long-term vision of network aspects for systems beyond IMT-2000*. +- [ITU-T Q.1711] ITU-T Recommendation Q.1711 (1999), *Network functional model for IMT-2000*. +- [ITU-T Q.1741] ITU-T Recommendations Q.1741-series: + - Q.1741.1 (2002), *IMT-2000 references to release 1999 of GSM evolved UMTS core network with UTRAN access network*. + - Q.1741.2 (2002), *IMT-2000 references to release 4 of GSM evolved UMTS core network with UTRAN access network*. + - Q.1741.3 (2003), *IMT-2000 references to release 5 of GSM evolved UMTS core network*. + - Q.1741.4 (2005), *IMT-2000 references to release 6 of GSM evolved UMTS core network*. +- [ITU-T Q.1742] ITU-T Recommendations Q.1742-series: + - Q.1742.1 (2002), *IMT-2000 references to ANSI-41 evolved core network with cdma2000 access network*. + - Q.1742.2 (2003), *IMT-2000 references (approved as of 11 July 2002) to ANSI-41 evolved core network with cdma2000 access network*. + - Q.1742.3 (2004), *IMT-2000 references (approved as of 30 June 2003) to ANSI-41 evolved core network with cdma2000 access network*. + +- Q.1742.4 (2005), *IMT-2000 references (approved as of 30 June 2004) to ANSI-41 evolved core network with cdma2000 access network.* + - Q.1742.5 (2006), *IMT-2000 references (approved as of 31 December 2005) to ANSI-41 evolved core network with cdma2000 access network.* + - Q.1742.6 (2007), *IMT-2000 references (approved as of 31 December 2006) to ANSI-41 evolved core network with cdma2000 access network.* +- [ITU-T Q.1761] ITU-T Recommendation Q.1761 (2004), *Principles and requirements for convergence of fixed and existing IMT-2000 systems.* +- [ITU-T Q.1762] ITU-T Recommendation Q.1762/Y.2802 (2007), *Fixed-mobile convergence general requirements.* + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 fixed-mobile convergence** [ITU-T Q.1762]: In a given network configuration, the capabilities that provide service and application to the end-user regardless of the fixed or mobile access technologies being used and independent of user's location. In the NGN environment, it means to provide NGN services to end-users regardless of the fixed or mobile access technologies being used. + +**3.1.2 nomadism** [ITU-T Q.1761]: Ability of the user to change his network access point after moving; when changing the network access point, the user's service session is completely stopped and then started again, i.e., there is no handover possible. It is assumed that the normal usage pattern is that users shut down their service session before moving to another access point or changing terminal. This is the mobility alluded to in the case of fixed-mobile convergence. + +## 3.2 Terms defined in this Recommendation + +There are no terms defined in this Recommendation. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-----------------------------------------------------------| +| 2G | Second Generation | +| 3G | Third Generation | +| AP | Access Point | +| AuC | Authentication Centre | +| CAMEL | Customized Applications for Mobile network Enhanced Logic | +| CAP | CAMEL Application Protocol | +| CCF | Call Control Function | +| CDMA | Code Division Multiple Access | +| CLI | Calling Line Identity | +| CLIP | Calling Line Identification Presentation | +| CLIR | Calling Line Identification Restriction | +| CS | Circuit Switched | + +| | | +|----------|------------------------------------------------| +| CSI | CAMEL Subscription Information | +| DTMF | Dual Tone Multiple Frequency | +| FE | Functional Entity | +| FMC | Fixed-Mobile Convergence | +| FSK | Frequency Shift Keying | +| GMSC | Gateway Mobile Switching Centre | +| GSM | Global System for Mobile communications | +| HLR | Home Location Register | +| HSS | Home Subscriber Server | +| IMSI | International Mobile Station Identity | +| IMT-2000 | International Mobile Telecommunications – 2000 | +| IN | Intelligent Network | +| IP | Intelligent Peripheral | +| ISDN | Integrated Services Digital Network | +| ISUP | ISDN User Part | +| LE | Local Exchange | +| MAP | Mobile Application Protocol | +| MD5 | Message-Digest algorithm 5 | +| MS | Mobile Station | +| MSC | Mobile Switching Centre | +| MSISDN | Mobile Station International ISDN Number | +| MSN | Multiple Subscriber Number | +| N-CSI | Network CAMEL Subscription Information | +| PAM | PSTN Access for Mobile users | +| POTS | Plain Old Telephone Service | +| PSTN | Public Switched Telephone Network | +| RAN | Radio Access Network | +| RNS | Radio Network Subsystem | +| SAC | Service Access Code | +| SCF | Service Control Function | +| SCP | Service Control Point | +| SHA-1 | Secure Hash Algorithm 1 | +| SHA-256 | Secure Hash Algorithm 256 | +| SLA | Service Level Agreement | +| SRF | Specialized Resource Function | +| SSF | Service Switching Function | +| SSP | Service Switching Point | + +| | | +|-------|--------------------------------------------| +| T-CSI | Terminating CAMEL Subscription Information | +| UMTS | Universal Mobile Telecommunication System | +| UPT | Universal Personal Telecommunication | +| UTRAN | Universal Terrestrial Radio Access Network | +| VLR | Visitor Location Register | +| WIN | Wireless Intelligent Network | + +# 5 Conventions + +In this Recommendation, references to "mobile network" should be read as applying equally to GSM/UTRAN [ITU-T Q.1741] networks and ANSI-41/cdma2000 [ITU-T Q.1742] networks. + +In addition: + +- "he" should be read as gender neutral, that is referring to "he" or "she" as appropriate; and +- "his" should similarly be read as gender neutral. + +# 6 Service features + +The PAM service provides a mobile user with access to voice and video telephony services utilizing the PSTN/ISDN via an available access point (AP) with an appropriate dual mode mobile terminal. Whether the AP is connected to the legacy network via a PSTN analogue or an ISDN access interface does not affect the service from the PAM user's point of view. + +The dual mode dual radio mobile terminal provides the user the accesses to the legacy PSTN/ISDN and mobile networks using a single terminal. + +## 6.1 Service numbering + +The PAM service supports two types of numbering: + +- The user is identified by a discrete PAM service number (referred to as a "fixed PAM service number" which may be in the form of, e.g., an UPT number). The fixed PAM service number is used separately from the user's mobile number (MSISDN). The fixed PAM service number is used to make and receive calls when the user is being provided service by means of a PSTN/ISDN access, while the mobile number (MSISDN) is used when the user is being provided service by means of a mobile network access. +- The user is identified by his MSISDN, which is also his PAM service number, independent of whether he is being provided service by a PSTN access or a mobile network access. + +## 6.2 Service subscription + +The user needs to subscribe to the PAM service in advance. + +- When the fixed PAM service number is used, the subscription information is as follows: + - a fixed PAM service number assigned by the provider; + - a user identity assigned by the provider which links to the PAM service number of the user; + - the user's associated MSISDN for re-routing the terminating call to the mobile network in case the call is not possible to be completed through the PSTN/ISDN; + - the service access code (SAC) of PAM service which corresponds to the PAM service controlling point of the home network. + +- When a MSISDN is used as the PAM service number, the subscription information is as follows: + - the user's IMSI; + - a user identity assigned by the provider which links to the IMSI of the user terminal; + - the service access code (SAC) of PAM service which corresponds to the PAM service controlling point of the home network; + - the PAM service subscription to be registered in the user's service profile (in the HLR/AuC (HSS)). + +## 6.3 Registration and authentication for legacy fixed network access + +The mobile user needs to register at a fixed network access point before making and receiving calls. Authentication is mandatory when a mobile user requests legacy PSTN/ISDN access. + +Once the user is authenticated and registered, he is provided voice and video communication using the PSTN/ISDN via the fixed network access point at which he is registered consistent with the limitations related to the capabilities of the access point and the terminal device being used. + +The mobile user deregisters when he leaves the access point. + +## 6.4 Call handling + +The service supports two different treatments for incoming and outgoing calls according to the service number used. + +### 6.4.1 User assigned a discrete PAM service number + +When using a fixed PAM service number separately assigned from the MSISDN, the handling of the call is as follows: + +- *Originating call* + +If the user is currently registered at an AP, the originating call will be handled through the PSTN/ISDN when the fixed network access is available. The fixed PAM service number is presented as the calling party number to the called party, and the call is treated according to the service subscription associated with the fixed PAM service number. The call is charged against the fixed PAM service number. If the fixed network access is not available (i.e., the AP that the user is registered at encounters an all fixed access circuits busy situation), the call will be handled through the mobile network, if available, as a normal mobile originating call. The MSISDN is displayed as the calling party number and the call is treated according to the service subscription associated with the MSISDN in the mobile network. The call is charged against the MSISDN. + +If the user is currently not registered for fixed network access, the originating call will be handled through the mobile network, if available, as a normal mobile originating call. The MSISDN is displayed as the calling party number and the call is treated according to the service subscription associated with the MSISDN in the mobile network. The call is charged against the MSISDN. + +The user is provided with visibility of the selection of the radio access (PAM AP or mobile network) used for the originating call. + +- *Terminating call* + +When a call is placed to a fixed PAM service number, there will first be a check for whether the PAM user is registered at an AP. If so, the call will be delivered via the PSTN/ISDN to the AP at which the PAM user is currently registered, and the call is treated according to the service subscription associated with the fixed PAM service number. If call completion through the PSTN/ISDN fails (e.g., all the access circuits to the AP are busy), + +the call will be forwarded to the mobile network using the MSISDN and the call is treated according to the service subscription associated with the MSISDN. + +If the user is currently not registered at an AP, a call to a fixed PAM service number will be forwarded to the mobile network using the MSISDN as the forwarded-to number and the call is treated according to the service subscription associated with the MSISDN. + +Charging to the originating party will not be affected when a call is forwarded from the PSTN to the MSISDN of the terminating party. + +A call to the MSISDN associated with the PAM user is delivered to the mobile network as a normal mobile terminating call. + +### 6.4.2 MSISDN as the PAM service number + +When using the MSISDN as the PAM service number, the handling of the call is as follows: + +#### - *Originating call* + +If the user is currently registered at an AP, an originating call will be handled through the PSTN/ISDN when the fixed network access is available. If the fixed network access is not available (i.e., the AP the user is registered with is busy), the call will be handled through the mobile network, if available, as a normal mobile originating call. Whether the call is handled through the legacy PSTN/ISDN, or through the mobile network, the MSISDN is presented as the calling party number to the called party, and the call is treated according to the service subscription associated with the MSISDN. The call is charged against the MSISDN. + +If the user is currently not registered at an AP, the originating call will be handled through the mobile network, if available, as a normal mobile originating call. The MSISDN is displayed as the calling party number and the call is treated according to the service subscription associated with the MSISDN in the mobile network. The call is charged against the MSISDN. + +The user is provided with visibility of the selection of the radio access (PAM AP or mobile network) used for the originating call. + +#### - *Terminating call* + +When a call is placed to the MSISDN of a subscriber who subscribes to the PAM service, there will first be a check for whether the MSISDN is registered at an AP. If so, the call will be delivered via the PSTN/ISDN to the AP at which the MSISDN subscriber is currently registered. If call completion via the AP fails (e.g., the access lines to the AP are busy), the call will be forwarded through the mobile network using the MSISDN. Whether the call is handled through the legacy PSTN/ISDN or through the mobile network, the call is treated according to the service subscription associated with the MSISDN. Charging to the originating party will not be affected when a call is forwarded from the PSTN/ISDN to the MSISDN on the mobile network of the terminating party. + +If the user is currently not registered at an AP, a call to a MSISDN will be delivered through the mobile network directly and the call is treated according to the service subscription associated with the MSISDN. + +## 6.5 Extent of mobility provided by PAM service + +Only nomadism is supported. + +When the user is in an active call, the call is interrupted in the following cases: + +- the user moves to a different AP; or +- the user changes from an AP to using mobile network access or vice versa. + +# 7 Architecture + +## 7.1 Architecture alternatives + +The PAM service is realized by PAM-SCF, PAM access point (AP) function, and PAM terminal function for air interface selection and registration. The PAM-SCF is an intelligent network SCF containing PAM service logic and data, and provides PAM mobility management. The AP functionality manages the air interface connection between itself and the PAM functions in the terminal, and the control relationship between itself and the PAM-SCF. The PAM terminal function interacts with the AP function to manage the air interface selection process. + +Two architectures corresponding to the use of a discrete PAM service number or the use of a MSISDN as the PAM service number are described in the following subclauses. + +### 7.1.1 Architecture with a discrete PAM service number assigned + +Figure 1 illustrates the functional model of the PAM service when a fixed PAM service number is used. For simplicity, mobile station functions not specific to the PAM service are omitted. + +![Functional model of the PAM service using a discrete PAM service number](ddc7460821484f1ae2835c67955c554c_img.jpg) + +The diagram illustrates the functional model of the PAM service. It is divided into two main sections by a vertical line: 'PSTN or ISDN' on the left and 'Mobile network' on the right. In the PSTN or ISDN section, there is a vertical stack of components: 'PAM-SCF' at the top, connected to 'SSF' below it. 'SRF' is connected to both 'PAM-SCF' and 'SSF'. 'SSF' is connected to 'CCF' below it. 'CCF' is connected to 'AP function' below it. In the Mobile network section, there is a 'Mobile network' oval connected to a 'RAN' rectangle below it. At the bottom center, between the two sections, is the 'MS PAM function'. Arrows indicate connections: from 'AP function' to 'MS PAM function', and from 'MS PAM function' to 'RAN'. A small text label 'Q.1763/Y.2803(07)\_F01' is located near the bottom right of the diagram. + +Functional model of the PAM service using a discrete PAM service number + +**Figure 1 – The functional model of the PAM service using a discrete PAM service number** + +The functional model in Figure 1 follows the intelligent network functional model described in [ITU-T Q.1224]. The PAM-SCF is an SCF which supports PAM service logic and data. + +The functional model shown in Figure 1 can be applied in case of different operators for the legacy PSTN/ISDN and the mobile network and requires no special SLA between the fixed and mobile operators. + +### 7.1.2 Architecture using MSISDN as the PAM service number + +Figure 2 illustrates the functional model of the PAM service using a MSISDN as the PAM service number. The PAM-SCF interfaces with HLR/AuC (HSS) in the mobile network. For simplicity, mobile station functions not specific to the PAM service are omitted. + +![Figure 2: The functional model of the PAM service using a MSISDN as the PAM service number. The diagram shows a PSTN or ISDN network on the left and a Mobile network on the right. The PSTN or ISDN network contains a PSTN or ISDN node connected to an AP function. The Mobile network contains a PAM-SCF, HLR/AuC (HSS), SRF, SSF, CCF, (G)MSC/VLR, and RAN. The MS PAM function is shown at the bottom, connected to both the PSTN or ISDN network and the Mobile network via lightning bolt symbols. The diagram is labeled Q.1763/Y.2803(07)_F02.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +Figure 2: The functional model of the PAM service using a MSISDN as the PAM service number. The diagram shows a PSTN or ISDN network on the left and a Mobile network on the right. The PSTN or ISDN network contains a PSTN or ISDN node connected to an AP function. The Mobile network contains a PAM-SCF, HLR/AuC (HSS), SRF, SSF, CCF, (G)MSC/VLR, and RAN. The MS PAM function is shown at the bottom, connected to both the PSTN or ISDN network and the Mobile network via lightning bolt symbols. The diagram is labeled Q.1763/Y.2803(07)\_F02. + +**Figure 2 – The functional model of the PAM service using a MSISDN as the PAM service number** + +Figure 2 applies equally to the CAMEL functional entities defined for a GSM/UTRAN network in [ITU-T Q.1741] and to the equivalent WIN functional entities for an ANSI-41/cdma2000 network in [ITU-T Q.1742]. + +The PAM-SCF is an SCF which supports PAM service logic and data. + +The functional model shown in Figure 2 can be applied in the case of the same operator for both the legacy PSTN/ISDN and the mobile network as well as in the case of different operators cooperating by appropriate interconnection and SLAs. + +## 7.2 Functional entities + +### 7.2.1 Mobile station PAM function + +The mobile station PAM function provides dual mode radio access. It allows the user to access the public mobile network via a 3G/2G air interface and to access the fixed network via an alternative air interface to the AP. + +The MS PAM function automatically initiates a registration request to the AP function when it detects an appropriate AP to which it can connect. The MS PAM function initiates a deregistration request to the AP function when the user manually deregisters through the menu in the terminal. + +For a call origination, when both radio accesses (to the AP and to the mobile network) are available, the MS PAM function selects the radio access to the AP, in case the call set-up through the AP radio access fails, the MS PAM function sends the call request over the mobile network radio access. + +The MS PAM function provides the user with indications of: + +- whether the fixed network is available via the AP connection (reflecting the registration or deregistration status); +- the selected radio access for the originating call in the ringing and conversation phase. + +For authentication of a mobile user through fixed network access via an AP, the MS PAM function provides the same network security mechanism as used in the mobile network, i.e., the same as used in another (mobile radio access) mode of the terminal. The MS PAM function supports the + +GSM/UTRAN or ANSI-41/cdma2000 network access security mechanism to perform terminal/network authentication by interaction with the PAM-SCF via the AP function and the SRF. The PAM service access code (SAC) and the user identity are to be pre-set in the terminal. + +### 7.2.2 Access point function + +The access point (AP) appears to the legacy PSTN/ISDN as a user equipment of that network. The AP appears to the MS as if it were a mobile switching centre (MSC). + +The AP function supports the basic functions of a POTS terminal or an ISDN terminal appropriate to the interface to the legacy network, including support of calling line identification presentation. In addition, it supports the sending and receiving of in-band DTMF/FSK signal. + +The AP function provides conversion between the wireless protocol and the analog or digital line signalling used on the PSTN/ISDN access. + +The AP function provides media transcoding between the type of codec used in the terminal and the type of codec used on the PSTN/ISDN access. + +In addition, the AP function supports the following functions: + +#### - *Registration and deregistration* + +When an AP function receives a registration request from a MS PAM function, the AP function supports the following ways of identifying the terminal requesting attachment: + +- The AP function allocates a terminal identifier dynamically for that terminal in case a PSTN analogue line is used. +- The AP function allocates a subscriber number for that terminal dynamically from a set of pre-assigned multiple subscriber numbers when ISDN interface is used (the MSN service needs to be active for the ISDN line and multiple subscriber numbers are assigned to the same ISDN line). + +The AP function sends a registration request by initiating a call request to the fixed network. In the registration procedure, the AP function acts as a "proxy" for the MS PAM function and provides, together with the SRF, the means to transfer information related to authentication between the MS PAM function and the PAM-SCF. + +When an AP function receives a deregistration request from a MS PAM function or when it detects that a terminal is no longer accessible via the AP (e.g., has moved out of range, has been turned off, etc.), the AP function frees the terminal identifier or subscriber number allocated to the terminal and sends a deregistration request by initiating a call request to the fixed network. + +##### - *Originating call handling* + +When an AP function receives a call request from a MS PAM function via the air interface, it checks the PSTN/ISDN access line status. If a line is free, the AP function initiates a call request to the PSTN/ISDN containing the terminal identifier or the subscriber number corresponding to the terminal. If there is no line available, the AP function sends a rejection to the MS PAM function to allow the MS PAM function to automatically select and establish the call through the mobile network radio access if available. + +##### - *Terminating call handling* + +When an AP function receives a terminating call request from the PSTN/ISDN for a mobile terminal, the AP function recognizes the terminal to be connected by using the terminal identifier (in case a PSTN line is used) or the subscriber number (in case an ISDN line is used) and completes the call to the terminal with the CLI to be presented via the air interface to the MS PAM function. + +#### 7.2.3 CCF/SSF + +The CCF establishes, manipulates and releases calls/connections. The CCF provides trigger mechanisms to access IN functionality (e.g., passes events to the SSF). + +The SSF extends the logic of the CCF to include recognition of service control triggers and to interact with the PAM-SCF. The SSF manages signalling between the CCF and the SCF and it modifies call/connection processing functions (in the CCF) as required to process requests for IN provided service usage under the control of the PAM-SCF. The CCF/SSF interacts with the SRF for bearer channel establishment between the SRF and the AP function under the control of PAM-SCF. + +The PAM service trigger is handled in SSF as follows: + +- When a PAM user requests registration/deregistration/originating call at an AP, the AP initiates a call which invokes an IN trigger based on a prescribed number plan (the SAC of the PAM service) at the SSF so that interaction with a PAM-SCF is initiated. +- A terminating call to a PAM user served with a fixed PAM service number invokes an IN trigger at the SSF based on a prescribed number plan which comprises part of the digits of the fixed PAM service number. +- For a terminating call to a PAM user served with a MSISDN, the PAM-SSF invokes an IN trigger based on the terminating service subscription downloaded in CCF (MSC/VLR) from the HLR/AuC (HSS). + +The CCF/SSF sets up the bearer connection between the AP function and the SRF function under the control of the PAM-SCF to exchange the registration/deregistration/originating call parameters between the AP function and the SRF in-band. + +In originating and terminating call, the SSF executes the instruction from the PAM-SCF for the call processing with updated parameters including the CLI as follows: + +- In originating call, the SSF updates the CLI to represent the registered PAM user using fixed PAM service number or MSISDN as opposed to the CLI of the AP upon the instruction from the PAM-SCF. +- In terminating call, in case a PSTN analogue access line is used, the SSF updates the CLI to indicate the PAM user to be connected via updating the original CLI with additional terminal identifier information upon the instruction from the PAM-SCF. + +#### 7.2.4 PAM-SCF + +The PAM-SCF provides the following functions: + +- Authentication function to perform authentication when a mobile user requests fixed network access via an AP. An SRF may be needed to collect identification and authentication parameters. For both numbering types, the PAM-SCF provides the same network security mechanism as used in the mobile network corresponding to another (mobile radio access) mode of the terminal. + - When a fixed PAM service number is used, the PAM-SCF generates the authentication data on-demand as done in HLR/AuC (HSS). + - When a MSISDN is used as the PAM service number, the PAM-SCF requests the authentication data from the HLR/AuC (HSS). + +- Mobility management to handle the user moving between different APs or moving into or out of range of an AP. This is managed via registration and deregistration procedure. When the PAM-SCF receives the registration or deregistration requests from an AP function, the PAM-SCF updates the service information as follows: + - In case a fixed PAM service number is used, the PAM-SCF updates the PAM user's registration status and the information relevant to the user's fixed network access point in the database. + - In case a MSISDN is used as the PAM service number, the PAM-SCF updates the PAM user's registration status and the information relevant to the user's fixed network access point in the database and updates the mobile user's PAM service subscription status in HLR/AuC (HSS) when the HLR/AuC (HSS) supports this function. +- Call control function: + - When the PAM-SCF processes an originating call request, it modifies the CLI to the fixed PAM service number (when a separate PAM service number is used) or the MSISDN (when MSISDN is used as PAM service number) of the PAM user. + - When the PAM-SCF processes a terminating call for a PAM user, in case the user is currently registered at an AP, the PAM-SCF instructs the SSF to complete the call via PSTN/ISDN. In case a PSTN line is used, the PAM-SCF instructs the SSF to route the call to the specific AP at which the user is registered with the updated CLI carrying the terminal identifier. In case ISDN line is used, the PAM-SCF instructs the SSF to route the call to the specific subscriber number corresponding to the terminal. If the call cannot be completed to the AP function, the PAM-SCF provides instructions to forward the call to the MSISDN of the PAM user. In the latter case, when MSISDN is used as the PAM service number, the call must be appropriately labelled to prevent circular routing. Otherwise, if the mobile user is not connected to any AP, the call is directly routed to the terminal via the mobile network. +- Service treatment function: the PAM-SCF provides the services according to the service profile associated with the service number. The service profile associated with the fixed PAM service number is statically stored in the PAM-SCF. The service profile associated with the MSISDN is downloaded from the HLR/AuC (HSS) after registration and deleted after deregistration. + +### 7.2.5 SRF + +The SRF functional entity provides the AP function in-band DTMF/FSK interaction via the SSF/CCF for the purpose of obtaining user identification and authentication parameters. The SRF accepts instructions from the PAM-SCF concerning the user interaction to be conducted and the parameters to be collected and returned to the PAM-SCF. The SRF is connected to and is disconnected from the AP function by the SSF/CCF as directed by the PAM-SCF. + +An example of an implementation of the PAM service using the MSISDN as the PAM service number is provided in clause 9. + +## 7.3 Information flows overview + +This clause provides an overview of PAM service information flows. Detailed information flows are provided in clause 9.3. + +### 7.3.1 Overview of information flows when using the discrete PAM service number + +#### 7.3.1.1 Registration + +When an AP function receives a registration request from a MS PAM function containing the SAC and the user identity, the AP function assigns a dynamic terminal identifier (in case an analogue line + +is used) or a subscriber number (in case an ISDN line is used) to that terminal and initiates a call carrying the SAC, the request type (registration) and the terminal identifier or the subscriber number to the CCF/SSF. + +The CCF/SSF uses the CLI (subscriber number) received from the user (the AP function) if it is valid; otherwise, the CCF/SSF inserts the network provided CLI of the fixed access line to which the AP is connected, the CCF/SSF triggers and queries the PAM-SCF for instructions. + +The PAM-SCF instructs the SRF to establish a bearer connection between itself and the AP function by the CCF/SSF. + +During the registration, the following information is exchanged between the AP function and the SRF in-band under the control of the PAM-SCF: + +- The PAM-SCF instructs the SRF to request to collect the user identification information from the AP function. +- The AP function sends the user identity to the SRF which relays the information to the PAM-SCF. +- The PAM-SCF generates the authentication data and instructs the SRF to interact with the AP function which uses the data provided by the MS PAM function to perform the authentication. +- After finishing the registration processing, the PAM-SCF instructs the SRF to send the registration result to the AP function in-band. The AP function sends the registration response to the MS PAM function. + +#### 7.3.1.2 Deregistration + +When an AP function receives a deregistration request from a MS PAM function or when an AP function detects that a terminal is no longer accessible via the AP function, the AP function sends the deregistration request by initiating a call request to CCF/SSF containing the SAC, the request type (deregistration) and the terminal identifier (in case an analogue line is used) or the subscriber number (in case an ISDN line is used). + +The CCF/SSF uses the CLI (subscriber number) received from the user (the AP function) if it is valid; otherwise, the CCF/SSF inserts the network provided CLI of the fixed access line to which the AP is connected, and the CCF/SSF triggers and queries the PAM-SCF for instructions. + +The PAM-SCF processes the deregistration request and responses with the deregistration result to the AP function via the SRF in-band. The AP function sends the deregistration response to the terminal if the terminal is still accessible. + +#### 7.3.1.3 Originating call + +Upon receiving an originating call request from a MS PAM function, the AP function sends an outgoing call request to the CCF/SSF with the information containing the SAC, the request type (originating call) and the terminal identifier (in case an analogue line is used) or the subscriber number (in case an ISDN line is used). + +The CCF/SSF uses the CLI (subscriber number) received from the user (the AP function) if it is valid; otherwise, the CCF/SSF inserts the network provided CLI of the fixed access line to which the AP is connected, and the CCF/SSF triggers and queries the PAM-SCF for instructions. + +The PAM-SCF instructs the SRF to collect the dialled number from the AP function and the AP function returns the dialled number received from the MS PAM function to the SRF which relays the dialled number to the PAM-SCF. + +The PAM-SCF processes the originating call request accordingly and controls the modification of the CLI to the fixed PAM service number. + +#### 7.3.1.4 Terminating call + +A terminating call to a fixed PAM service number is routed to the "home switch" supporting the assigned PAM service number which treats the call as an IN call and queries the PAM-SCF for instructions. + +- If the user is currently registered at an AP, the PAM-SCF responds with routing instructions in the form of a specific AP to which to route the call for completion together with the updated CLI carrying the terminal identifier in case an analogue line is used, or in the form of a subscriber number corresponding to the terminal to which to route the call for completion in case an ISDN line is used. In case the call cannot be completed to the AP, the PAM-SCF provides the instructions to forward the call to the MSISDN associated with the subscriber. +- Otherwise, if the mobile user is not connected to any AP, the PAM-SCF forwards the call directly to the mobile network using the MSISDN associated with the subscriber. + +### 7.3.2 Overview of information flows when using MSISDN as the PAM service number + +#### 7.3.2.1 Registration + +When an AP function receives a registration request from a MS PAM function containing the SAC and the user identity, the AP function assigns a dynamic terminal identifier (in case an analogue line is used) or a subscriber number (in case an ISDN line is used) to that terminal and initiates a call carrying the SAC, the request type (registration) and the terminal identifier or the subscriber number to the CCF/SSF. + +The CCF/SSF uses the CLI (subscriber number) received from the user (the AP function) if it is valid; otherwise, the CCF/SSF inserts the network provided CLI of the fixed access line to which the AP is connected, and the CCF/SSF triggers and queries the PAM-SCF for instructions. + +The PAM-SCF instructs the SRF to establish a bearer connection between itself and the AP function by the CCF/SSF. + +During the registration, the following information is exchanged between the AP function and the SRF in-band under the control of the PAM-SCF: + +- The PAM-SCF instructs the SRF to collect the user identification information from the AP function. +- The AP function sends the user identity to the SRF which relays the information to the PAM-SCF. +- The PAM-SCF retrieves the authentication data of the terminal from HLR/AuC (HSS) and instructs the SRF to interact with the AP function which uses the data provided by the MS PAM function to perform the authentication. + +After authentication is successful, the PAM-SCF updates the mobile user's terminating subscription status in HLR/AuC (HSS) if the HLR/AuC (HSS) supports this function. + +After finishing the registration processing, the PAM-SCF instructs the SRF to send the registration result to the AP function in-band which relays the registration response to the MS PAM function. + +#### 7.3.2.2 Deregistration + +When an AP function receives a deregistration request from a MS PAM function or when an AP function detects that a terminal is no longer accessible via the AP, then the AP function sends the deregistration request by initiating a call request to CCF/SSF containing the SAC of the PAM service, the request type (deregistration) and the terminal identifier (in case an analogue line is used) or the subscriber number (in case an ISDN line is used). + +The CCF/SSF uses the CLI (subscriber number) received from the user (the AP function) if it is valid; otherwise, the CCF/SSF inserts the network provided CLI of the fixed access line to which the AP is connected and triggers and queries the PAM-SCF for instructions. + +The PAM-SCF processes the deregistration request and updates the mobile user's terminating subscription status in HLR/AuC (HSS) when the HLR/AuC (HSS) supports this function. + +After finishing the deregistration processing, the PAM-SCF responds with the deregistration result to the AP function via the SRF in-band. The AP function sends the deregistration response to the terminal if the terminal is still accessible. + +#### 7.3.2.3 Originating call + +Upon receiving an originating call request from a MS PAM function, the AP function sends an outgoing call request to the CCF/SSF with the information containing the SAC of the PAM service, the request type (originating call) and the terminal identifier (in case an analogue line is used) or the subscriber number (in case an ISDN line is used). + +The CCF/SSF uses the CLI (subscriber number) received from the user (the AP function) if it is valid; otherwise, the CCF/SSF inserts the network provided CLI of the fixed access line to which the AP is connected, the CCF/SSF triggers and queries the PAM-SCF for instructions. + +The PAM-SCF instructs the SRF to collect the dialled number from the AP function and the AP function returns the dialled number received from the MS PAM function to the SRF which relays the dialled number to the PAM-SCF. + +The PAM-SCF processes the originating call request accordingly and controls the modification of the CLI to the MSISDN. + +#### 7.3.2.4 Terminating call + +A terminating call to a MSISDN is routed to the "home switch" supporting the assigned PAM service number which treats the call as an IN call and queries the PAM-SCF for instructions. + +- If the user is currently registered at an AP, the PAM-SCF responds with routing instructions in the form of a specific AP to which to route the call for completion together with the updated CLI carrying the terminal identifier in case an analogue line is used, or in the form of a subscriber number corresponding to the terminal to which to route the call for completion in case an ISDN line is used. In case the call cannot be completed to the AP, the PAM-SCF provides the instructions to forward the call to the MSISDN associated with the subscriber. In the latter case, the call must be appropriately labelled to prevent circular routing. +- Otherwise, if the mobile user is not connected to any AP, the call is directly routed to the terminal via the mobile network. + +## 7.4 Allocation of functional entities to physical nodes + +For each functional model given in Figures 1 and 2, two scenarios are defined as follows: + +- The functional entities of IN are allocated to different physical nodes such as SSP, PAM-SCP and IP. +- The functional entities of IN are allocated to one platform referred to as PAM service platform. + +In each case, the functional architecture and information flows are the same. + +### 7.4.1 User assigned a discrete PAM service number + +Figure 3 illustrates the scenario of allocating the functional entities to different physical nodes when a fixed PAM service number is used. + +![Diagram illustrating the scenario for assigning Functional Entities (FEs) to different physical nodes when using a discrete PAM service number. The diagram is split into two main sections: PSTN or ISDN on the left and Mobile network on the right, connected by a central vertical line. On the left, from top to bottom: a box labeled 'PAM-SCP' containing an oval 'PAM-SCF'; a box labeled 'LE/SSP' containing ovals 'SSF' and 'CCF'; and a box labeled 'AP' containing an oval 'AP function'. An external box labeled 'IP' contains an oval 'SRF' and is connected to the 'PAM-SCP'. On the right, from top to bottom: an oval labeled 'Mobile network'; and a box labeled 'RAN'. At the bottom center, a box labeled 'Mobile station' contains an oval 'MS PAM function'. Arrows point from the 'PAM-SCP', 'LE/SSP', and 'Mobile station' towards the central vertical line. A small label 'Q.1763/Y.2803(07)_F03' is at the bottom right.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +Diagram illustrating the scenario for assigning Functional Entities (FEs) to different physical nodes when using a discrete PAM service number. The diagram is split into two main sections: PSTN or ISDN on the left and Mobile network on the right, connected by a central vertical line. On the left, from top to bottom: a box labeled 'PAM-SCP' containing an oval 'PAM-SCF'; a box labeled 'LE/SSP' containing ovals 'SSF' and 'CCF'; and a box labeled 'AP' containing an oval 'AP function'. An external box labeled 'IP' contains an oval 'SRF' and is connected to the 'PAM-SCP'. On the right, from top to bottom: an oval labeled 'Mobile network'; and a box labeled 'RAN'. At the bottom center, a box labeled 'Mobile station' contains an oval 'MS PAM function'. Arrows point from the 'PAM-SCP', 'LE/SSP', and 'Mobile station' towards the central vertical line. A small label 'Q.1763/Y.2803(07)\_F03' is at the bottom right. + +**Figure 3 – Scenario for assigning FEs to different physical nodes when using a discrete PAM service number** + +In this scenario, the relationship of the functional entities and the physical nodes is as follows: + +- the AP function maps to the AP; +- the mobile station PAM function maps to the mobile station (for simplicity, other MS functions are not shown); +- the CCF maps to the LE; +- the SSF maps to the SSP; +- the PAM-SCF maps to the PAM-SCP; +- the SRF functional entity maps to the IP. + +Figure 4 illustrates the scenario of allocating all the PAM-service functional entities to the same physical node when a fixed PAM service number is used. Note that the CCF and SSF have been mapped to different nodes. This separation of the CCF and SSF is described in further detail in later clauses. + +![Figure 4: Scenario for assigning functional entities to the same physical node when using a discrete PAM service number. The diagram shows a PSTN or ISDN side with a PAM service platform containing SRF, PAM-SCF, and SSF. Below it are LE (with CCF) and AP (with AP functions). A Mobile network side contains a Mobile network node connected to a RAN. At the bottom, a Mobile station contains PAM functions. Arrows indicate connections from the PSTN/ISDN side and the Mobile network side to the Mobile station.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +Q.1763/Y.2803(07)\_F04 + +Figure 4: Scenario for assigning functional entities to the same physical node when using a discrete PAM service number. The diagram shows a PSTN or ISDN side with a PAM service platform containing SRF, PAM-SCF, and SSF. Below it are LE (with CCF) and AP (with AP functions). A Mobile network side contains a Mobile network node connected to a RAN. At the bottom, a Mobile station contains PAM functions. Arrows indicate connections from the PSTN/ISDN side and the Mobile network side to the Mobile station. + +**Figure 4 – Scenario for assigning functional entities to the same physical node when using a discrete PAM service number** + +In this scenario, the PAM service functional entities are mapped to one physical node referred to as the PAM service platform which supports the SSF, SRF and PAM-SCF functionalities. + +### 7.4.2 MSISDN as the PAM service number + +Figure 5 illustrates the scenario of allocating functional entities to different physical nodes when a MSISDN is used as the PAM service number. For simplicity, HLR, etc., functions not specific to the PAM service are not expanded. + +![Figure 5: Scenario for assigning FEs to different physical nodes when using MSISDN as the PAM service number. The diagram shows a PSTN or ISDN side with a PSTN or ISDN node connected to an AP (with AP function). A Mobile network side includes a PAM-SCP (with PAM-SCF), a (G)MSC/VLR/SSP (with CCF and SSF), an IP node (with SRF), and two HLR/AuC (HSS) nodes. A RAN is connected to the (G)MSC/VLR/SSP. At the bottom, a Mobile station contains MS PAM function. Arrows indicate connections from the PSTN/ISDN side and the Mobile network side to the Mobile station.](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +Q.1763/Y.2803(07)\_F05 + +Figure 5: Scenario for assigning FEs to different physical nodes when using MSISDN as the PAM service number. The diagram shows a PSTN or ISDN side with a PSTN or ISDN node connected to an AP (with AP function). A Mobile network side includes a PAM-SCP (with PAM-SCF), a (G)MSC/VLR/SSP (with CCF and SSF), an IP node (with SRF), and two HLR/AuC (HSS) nodes. A RAN is connected to the (G)MSC/VLR/SSP. At the bottom, a Mobile station contains MS PAM function. Arrows indicate connections from the PSTN/ISDN side and the Mobile network side to the Mobile station. + +**Figure 5 – Scenario for assigning FEs to different physical nodes when using MSISDN as the PAM service number** + +In Figure 5, the relationship of the functional entities and the physical nodes is as follows: + +- the AP function maps to the AP; +- the mobile station PAM function maps to the Mobile Station (for simplicity, other MS functions are not shown); +- CCF/SSF maps to the (G)MSC/VLR/SSP; +- the PAM-SCF functional entity maps to the PAM-SCP; +- the SRF functional entity maps to the IP. + +Figure 6 illustrates the scenario of allocating all the PAM service functional entities to the same physical node when a MSISDN is used as the PAM service number. Note that the CCF and SSF have been mapped to different nodes. This separation of the CCF and SSF is described in further detail in later clauses. + +![Figure 6: Scenario for assigning FEs to the same physical node when using MSISDN as the PAM service number. The diagram shows a PSTN or ISDN network on the left and a Mobile network on the right. The PSTN or ISDN network includes a PSTN or ISDN node connected to an AP (AP functions) and a Mobile station (PAM functions). The Mobile network includes a PAM service platform (PAM-SCF, SRF, SSF), a (G)MSC/VLR (CCF), a RAN, and an HLR/AuC (HSS). The PAM service platform is connected to the (G)MSC/VLR and the HLR/AuC (HSS). The (G)MSC/VLR is connected to the RAN. The RAN is connected to the Mobile station. The Mobile station is connected to the AP. The AP is connected to the PSTN or ISDN node. The Mobile station is connected to the PSTN or ISDN node via a dashed line with lightning bolts.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Figure 6: Scenario for assigning FEs to the same physical node when using MSISDN as the PAM service number. The diagram shows a PSTN or ISDN network on the left and a Mobile network on the right. The PSTN or ISDN network includes a PSTN or ISDN node connected to an AP (AP functions) and a Mobile station (PAM functions). The Mobile network includes a PAM service platform (PAM-SCF, SRF, SSF), a (G)MSC/VLR (CCF), a RAN, and an HLR/AuC (HSS). The PAM service platform is connected to the (G)MSC/VLR and the HLR/AuC (HSS). The (G)MSC/VLR is connected to the RAN. The RAN is connected to the Mobile station. The Mobile station is connected to the AP. The AP is connected to the PSTN or ISDN node. The Mobile station is connected to the PSTN or ISDN node via a dashed line with lightning bolts. + +Q.1763/Y.2803(07)\_F06 + +**Figure 6 – Scenario for assigning FEs to the same physical node when using MSISDN as the PAM service number** + +In Figure 6, the PAM service functional entities are mapped to one physical node referred to as the PAM service platform which supports the SSF, SRF and PAM-SCF functionalities. + +# 8 Capability requirements + +When a mobile user requests to have legacy PSTN/ISDN access (i.e., the PAM service), the support of user registration and deregistration, authentication and call handling through the PSTN/ISDN access is required. + +## 8.1 User authentication through PSTN/ISDN access + +When a mobile user requests access to the PSTN/ISDN, mutual authentication between the MS PAM function and the AP function is required. + +During registration request processing, authentication needs to be performed. To accomplish user authentication through a fixed line access, a bearer channel between the AP function via which the MS PAM function is requesting service and the SRF needs to be set up to enable the PAM-SCF to exchange necessary identification and authentication information in-band with the AP function. + +The support of the same terminal authentication mechanism as used in the mobile network is required: the AP has to be able to receive the same authentication information from the mobile terminal that the mobile network RAN would receive as part of the registration procedure, and the AP must be able to relay this to the PAM-SCF so that the latter may interact with the HLR/AuC (HSS) to complete the registration. + +The normal authentication procedure is illustrated as follows: + +- When an AP function receives a registration request from a MS PAM function containing the SAC and the user identification information (a user identity), the AP function sends the registration request by initiating a call request to the fixed network. +- The call arrives in CCF/SSF which triggers and queries the PAM-SCF. +- The PAM-SCF instructs the SRF to establish a bearer channel between itself and the AP function. +- The PAM-SCF instructs the SRF to collect the user identification information from the AP function. +- The AP function sends the user identification information in-band to the SRF which relays the received information to the PAM-SCF. +- The PAM-SCF acquires the authentication data as follows: + - When a fixed PAM service number is used, the PAM-SCF generates the authentication data as it is done in HLR/AuC (HSS). + - When a MSISDN is used, the PAM-SCF requests the authentication data from the HLR/AuC (HSS) using the IMSI which is translated by the PAM-SCF using the user identity received from the AP function. +- The PAM-SCF instructs the SRF to send the authentication data to the AP function which relays the information to the MS PAM function. +- In case the terminal and network mutual authentication is required, the MS PAM function authenticates the network. If it is successful, the MS PAM function produces a response result which is sent back to the AP function. +- The AP function sends the response result to the SRF which relays the information to the PAM-SCF. +- The PAM-SCF compares the received result with the expected result. If they match, the PAM-SCF continues the registration procedure. Otherwise, the authentication is not successful and the PAM-SCF instructs the SRF to send a negative response to the AP function to end the registration. The AP relays the response to the MS PAM function and ends the registration procedure. + +The secure transfer of the user identification information is required on the radio interface between the MS PAM function and the AP function as well as on the interface between the AP function and the fixed network. + +The encryption of the user identification information sent over the radio access needs to be supported by the wireless technology used in the MS PAM function and the AP function. + +The encryption (e.g., using SHA-1 or SHA-256 or MD5 as specified in [b-IETF RFC 3174], [b-NIST SHA-256] and [b-IETF RFC 1321]) of the user identification information over the fixed network needs to be supported by the AP function and the PAM SCF. + +## 8.2 User identification and routing + +When a mobile user is connecting to an AP with PSTN access line, the mobile user needs to be correctly identified for routing the call and presentation of the user's PAM service number. The following information is needed: + +- The AP address: It is the CLI of the PSTN line to which the AP is connected. +- The terminal identifier: It is the number dynamically allocated by the AP to identify the terminals attached to it. + +The correlation of the user (either with a fixed PAM service number or a MSISDN) with the AP address and the terminal identifier needs to be set-up during registration. + +- When a fixed PAM service number is used: +The corresponding relationship among the user identity, the fixed PAM service number and the associated MSISDN is statically created when the user subscribes to the PAM service, while the AP address and terminal identifier need to be dynamically updated when the user registers or deregisters with an AP. +- When a MSISDN is used as the PAM service number: +The corresponding relationship between the user identity and the IMSI is statically created when the user subscribes to the PAM service, while the user's MSISDN, the AP address and the terminal identifier need to be dynamically updated when the user registers and deregisters. The user's MSISDN needs to be retrieved from the HLR/AuC (HSS) using IMSI which is translated by the PAM-SCF using the user identity. + +Once the correlation of the mobile user with the AP address and the terminal identifier is made: + +- originating calls of the mobile user through the AP function need to carry the AP address and terminal identifier and the PAM service number associated with the AP address and the terminal identifier is presented as CLI; +- terminating calls to the PAM service number need to be offered only to the mobile stations associated with the AP address and the terminal identifier. + +When a mobile user is connecting to an AP with ISDN line, an individual subscriber number is assigned to the mobile station and the PAM-SCF needs to set-up mobile station-subscriber number association. Once the mobile station-subscriber number association is made: + +- all calls originated by the terminal through the AP function need to carry the subscriber number of the terminal and the PAM service number associated with subscriber number is presented as CLI; +- terminating calls to the PAM service number shall be offered only to the mobile stations associated with the subscriber number. + +## 8.3 User profile treatment + +When a MSISDN is used as the PAM service number, the PAM-SCF needs to have the latest service profile of the mobile user in order to provide the set of services associated to the user when utilizing fixed access. This can be implemented in two ways at the discretion of the PAM-SCP implementer: + +- the PAM-SCF requests the service profile from the HLR/AuC (HSS) whenever the data is needed; or +- the platform acts like VLR: It stores the user profile during user registration and keeps the data HLR/AuC (HSS) as long as the user does not change the AP he is registered at. + +## 8.4 Emergency call handling + +When an AP function detects that an emergency short number has been sent, the call will be treated as an emergency call from the fixed access line to which the AP is connected, irrespective of successful registration or authentication. + +## 8.5 Video call handling + +The CS video telephony service needs to be supported and requires the AP function to support the ISDN interface. Hence, this service is not available when the AP is connected to a PSTN access line. + +The video phone call of the mobile user through the ISDN access is over a 64 kbit/s/56 kbit/s transparent data bearer. + +A video call between a mobile user utilizing an ISDN access point and other terminals supporting the same codec is handled in the same manner as a normal voice call and is transparent to the PAM-SCF and the AP. Codec negotiation may be required and is performed in-band between the terminals. + +A video phone call between a mobile user and other types of terminals supporting different codecs is possible when such kind of interworking is supported in either the underlying fixed or the underlying mobile network; otherwise, the video phone call may be downgraded to a voice call or the user may abandon the call. + +# 9 Implementation of PAM service using IN approach + +This clause provides an example of the implementation of the PAM service in convergence of PSTN and UMTS or ANSI-41/cdma2000 network. The implementation of the PAM service uses the intelligent network approach. The PAM service is realized by introducing the PAM-SCP with service logic and data to support the PAM service and with the support of the HLR/AuC (HSS). The advantage of this implementation is that there is no impact on the underlying fixed network and mobile core network. Some adaptations to the components at the application layer are required as described in clause 9.2. + +In the following figures, a suitable short range air interface such as [b-Bluetooth] or [b-IEEE 802.11g] is used between the AP and the mobile station. + +## 9.1 Network configuration + +Figure 7a illustrates the network configuration of the PAM service with PSTN access to a GSM/UTRAN network using MSISDN as the PAM service number. + +![Figure 7a: Network configuration of the PAM service using MSISDN as the PAM service number for a GSM/UTRAN mobile network. The diagram shows a PSTN network on the left connected to a UMTS network on the right. The PSTN network consists of three switches, with the bottom switch connected to an AP via analogue line signalling. The top switch connects to a GMSC/VLR/SSP via an ISUP link. The GMSC/VLR/SSP is connected to an IP node and an MSC/VLR/SSP via ISUP links. The IP node is connected to a PAM-SCP via a CAP link. The PAM-SCP is connected to the HLR/AuC (HSS) via a MAP link. The HLR/AuC (HSS) is connected to the MSC/VLR/SSP via a MAP link. The MSC/VLR/SSP is connected to a RAN. A mobile station is shown between the PSTN and UMTS networks. Signalling links (CAP, ISUP, MAP) are shown between the various network elements. A reference code Q.1763/Y.2803(07)_F07a is present in the bottom right.](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +Figure 7a: Network configuration of the PAM service using MSISDN as the PAM service number for a GSM/UTRAN mobile network. The diagram shows a PSTN network on the left connected to a UMTS network on the right. The PSTN network consists of three switches, with the bottom switch connected to an AP via analogue line signalling. The top switch connects to a GMSC/VLR/SSP via an ISUP link. The GMSC/VLR/SSP is connected to an IP node and an MSC/VLR/SSP via ISUP links. The IP node is connected to a PAM-SCP via a CAP link. The PAM-SCP is connected to the HLR/AuC (HSS) via a MAP link. The HLR/AuC (HSS) is connected to the MSC/VLR/SSP via a MAP link. The MSC/VLR/SSP is connected to a RAN. A mobile station is shown between the PSTN and UMTS networks. Signalling links (CAP, ISUP, MAP) are shown between the various network elements. A reference code Q.1763/Y.2803(07)\_F07a is present in the bottom right. + +**Figure 7a – The network configuration of the PAM service using MSISDN as the PAM service number for a GSM/UTRAN mobile network** + +Figure 7b illustrates the network configuration of the PAM service with PSTN access to an ANSI41/cdma2000 network using MSISDN as the PAM service number. + +![Figure 7b: Network configuration of the PAM service using MSISDN as the PAM service number for an ANSI-41/cdma2000 mobile network. The diagram shows a PSTN network on the left connected to an ANSI-41/cdma2000 network on the right. The PSTN network consists of three switches, with the bottom switch connected to an AP via analogue line signalling. The top switch connects to a GMSC/VLR/SSP via an ISUP link. The GMSC/VLR/SSP is connected to an IP node and an MSC/VLR/SSP via ISUP links. The IP node is connected to a PAM-SCP via a WIN link. The PAM-SCP is connected to the HLR/AuC (HSS) via a MAP link. The HLR/AuC (HSS) is connected to the MSC/VLR/SSP via a MAP link. The MSC/VLR/SSP is connected to a RAN. A mobile station is shown between the PSTN and ANSI-41/cdma2000 networks. Signalling links (WIN, ISUP, MAP) are shown between the various network elements. A reference code Q.1763/Y.2803(07)_F07b is present in the bottom right.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +Figure 7b: Network configuration of the PAM service using MSISDN as the PAM service number for an ANSI-41/cdma2000 mobile network. The diagram shows a PSTN network on the left connected to an ANSI-41/cdma2000 network on the right. The PSTN network consists of three switches, with the bottom switch connected to an AP via analogue line signalling. The top switch connects to a GMSC/VLR/SSP via an ISUP link. The GMSC/VLR/SSP is connected to an IP node and an MSC/VLR/SSP via ISUP links. The IP node is connected to a PAM-SCP via a WIN link. The PAM-SCP is connected to the HLR/AuC (HSS) via a MAP link. The HLR/AuC (HSS) is connected to the MSC/VLR/SSP via a MAP link. The MSC/VLR/SSP is connected to a RAN. A mobile station is shown between the PSTN and ANSI-41/cdma2000 networks. Signalling links (WIN, ISUP, MAP) are shown between the various network elements. A reference code Q.1763/Y.2803(07)\_F07b is present in the bottom right. + +**Figure 7b – The network configuration of the PAM service using MSISDN as the PAM service number for an ANSI-41/cdma2000 mobile network** + +The (MSC/VLR)/SSP supports the (MSC/VLR)/SSF functionalities. + +An originating call through the PSTN access uses N-CSI or WIN triggers in the GMSC/VLR/SSP. + +A terminating call of the PAM service uses T-CSI or WIN triggers in the MSC/VLR/SSP. (The terminating IN subscription is registered when the user subscribes to the PAM service, the initial terminating IN subscription status is set to inactive if the mobile network supports the dynamic update of the IN subscription status; otherwise, the initial IN subscription status is set to active.) + +The IP supports standard SRF functionalities. The IP provides for sending and receiving of in-band DTMF/FSK signals or announcements. Specifically, in-band FSK signalling is used during the registration (authentication), deregistration and originating call procedures for the exchange of necessary information between the AP which acts as a proxy for the terminal and the IP for relay to the PAM-SCP, and for the sending of the registration/deregistration responses to the AP which relays the response to the terminal. + +The PAM-SCP supports normal SCF functions per [ITU-T Q.1224]. In addition, the PAM-SCP supports: + +- The authentication function: The PAM-SCP acts as a VLR to perform terminal authentication. +- Registration and deregistration: The PAM-SCP acts as a VLR to update the location information for the user when the user registers and deregisters. + +During registration, the PAM-SCP updates the terminating IN subscription status to active in the HLR/AuC (HSS) (when the HLR/AuC (HSS) supports the dynamic modification of the subscription status). After registration, the call to the MSISDN will be triggered as an IN call and be handled by the PAM-SCP. + +During deregistration, the PAM-SCP updates the terminating IN subscription status to inactive in the HLR/AuC (HSS) (when the HLR/AuC (HSS) supports the dynamic modification of the subscription status). After deregistration, the call to the MSISDN will be handled as a normal mobile terminating call. + +- Originating call handling: The PAM-SCP gets the MSISDN of the user via the AP address and the terminal identifier received. The PAM-SCP handles the call connection to the called party and sets the calling party number as the user's MSISDN. The CLIR supplementary service is handled by the PAM-SCP according to the subscription of the mobile user. +- Terminating call handling: The PAM-SCP supports flexible call routing as described in the service features. When the mobile user is currently registered at an AP, the PAM-SCP gets the AP address and the terminal identifier via the MSISDN. The PAM-SCP reformats the calling line identity (CLI) received by adding the terminal identifier in predefined format and sends the newly formatted CLI in call set-up request to the AP. The PSTN will deliver the CLI to the AP during call establishment, during the first long silent interval of the ringing phase (the PSTN access line to which the AP is connected needs to have the CLIP active). The AP resolves the received CLI and establishes the call to the mobile user identified by the terminal identifier and sends the original calling party number to the mobile user in the call. + +Special treatment of the original calling party number is required when the calling party has CLIR and/or the called party (mobile user) does not have CLIP and/or the original calling party number is empty. In such cases, the PAM-SCP needs to set the original calling party number to a special number then adds the terminal identifier to it. When the AP receives the special calling party number carrying the terminal identifier, the AP only picks out the terminal identifier and will not send the calling party number to the mobile user. + +- Supplementary service supporting: In originating and terminating calls, part of the mobile user's supplementary services may be handled by the PAM-SCP. + +The PAM-SCP downloads the mobile subscriber's supplementary service data during registration. + +The CLIP/CLIR supplementary services of the mobile user are treated by the PAM-SCP as indicated in the preceding paragraphs. The other supplementary services provided by the PAM-SCP are limited by the capability of the access signalling system available to the AP and the capability of the call control signalling used in the PSTN/mobile network (like ISUP). + +## **9.2 Signalling requirements** + +### **9.2.1 Requirement on the interface between PAM-SCP and IP** + +The PAM-SCP controls the in-band FSK interaction between the IP and the AP in the scenario of user registration and deregistration through the PSTN access. + +The signalling between the PAM-SCP and the IP needs to support that the PAM-SCP could instruct the IP to conduct the sending and receiving of FSK signals. + +### **9.2.2 Requirement on the interface between PAM-SCP and HLR/AuC (HSS)** + +The interface between the PAM-SCP and the HLR/AuC (HSS) needs to support the following functions: + +- The PAM-SCP retrieves the authentication data from the HLR/AuC (HSS). +- The PAM-SCP retrieves the MSISDN and the user's service profile from the HLR/AuC (HSS). +- The PAM-SCP modifies the mobile user's IN service subscription status in the HLR/AuC (HSS) (optional). + +### **9.2.3 Requirement on the interface between PAM-SCP and SSP** + +The signalling between the PAM-SCP and the SSP needs to allow the PAM-SCP to instruct the SSP to overwrite the calling party number in call set-up request. + +The modification of the calling party number by PAM-SCP is used in the following cases: + +- In originating call, the PAM-SCP needs to set the PAM service number as CLI to be presented to the called party. +- In terminating call, the PAM-SCP needs to add the terminal identifier in the CLI which will be delivered to the AP during call establishment. + +## **9.3 Call flows** + +This clause provides the call flows for the PAM service. + +### 9.3.1 User registration call flow + +![Sequence diagram showing the user registration call flow between Mobile station, Access point, PSTN switch, (MSC/VLR)/SSP, PAM-SCP, IP, and HLR/AuC (HSS).](5414f65867392f05ba0063b208eeb5e1_img.jpg) + +``` + +sequenceDiagram + participant MS as Mobile station + participant AP as Access point + participant PS as PSTN switch + participant MV as (MSC/VLR)/SSP + participant PSR as PAM-SCP + participant IP as IP + participant HSS as HLR/AuC (HSS) + + Note left of MS: Service register request (user identity) + MS->>AP: + Note right of AP: 1. Automatic call set-up (SAC, request type, terminal identifier) + AP->>PS: + PS->>MV: 2. Set-up request + MV->>PSR: 3. Query (triggered by N-CSI) + PSR->>MV: 4. Prepare special resource + MV->>IP: 5. Establish connection with special resource + IP->>MV: 6. Special resource connected + MV->>PS: 7. Set-up response + PSR->>IP: 8. Special resource ready + PSR->>MV: 9. Send info request (IMSI), wait for result + MV-->>AP: 10. Send info request (user identification) in FSK + AP-->>IP: 11. Send user identity in FSK + PSR->>MV: 12. Result of info request + PSR->>HSS: 13. Retrieve authentication info + HSS->>PSR: 14. Authentication info ack + PSR->>IP: 15. Send authentication info + Note left of MS: Service authentication request + MS->>AP: + Note right of AP: 16. Send authentication info in FSK + AP-->>IP: 17. Authentication result calculated by terminal in FSK + PSR->>MV: 18. Result of authentication + PSR->>HSS: 19. Retrieve user profile + HSS->>PSR: 20. User profile data + PSR->>HSS: 21. Activate the PAM service + HSS->>PSR: 22. Activate ack + PSR->>IP: 23. Send registration response + Note left of MS: Service register response + MS->>AP: + Note right of AP: 24. Send registration response in FSK + AP-->>IP: + PSR->>MV: 25. Result of sending response + MV->>PSR: 26a. Release the special resource + PSR->>IP: 27a. Release + MV->>PSR: 28a. Release complete + Note right of AP: 26b. On hook + AP->>PS: + PS->>MV: 27b. Release + MV->>PS: 28b. Release complete + MV->>PSR: 29. Report release event + PSR->>MV: 30. End of query + +``` + +The sequence diagram illustrates the user registration call flow. It begins with a 'Service register request (user identity)' from the Mobile station to the Access point. The Access point initiates an 'Automatic call set-up' (SAC, request type, terminal identifier) to the PSTN switch, which sends a 'Set-up request' to the (MSC/VLR)/SSP. The (MSC/VLR)/SSP sends a 'Query (triggered by N-CSI)' to the PAM-SCP, which responds with 'Prepare special resource'. The (MSC/VLR)/SSP then establishes a connection with the IP, which confirms 'Special resource connected'. The PAM-SCP sends a 'Set-up response' to the (MSC/VLR)/SSP, which then sends it to the PSTN switch. The PAM-SCP also sends a 'Special resource ready' message to the IP. Next, the PAM-SCP sends an 'info request (IMSI), wait for result' to the (MSC/VLR)/SSP. The (MSC/VLR)/SSP sends an 'info request (user identification) in FSK' to the Access point, which in turn sends a 'Send user identity in FSK' to the IP. The IP returns the 'Result of info request' to the PAM-SCP, which then sends a 'Retrieve authentication info' request to the HLR/AuC (HSS). The HSS returns the 'Authentication info ack' to the PAM-SCP, which sends the 'Send authentication info' to the IP. The Mobile station sends a 'Service authentication request' to the Access point, which sends the 'Send authentication info in FSK' to the IP. The IP calculates the 'Authentication result' and sends it to the PAM-SCP. The PAM-SCP sends the 'Result of authentication' to the (MSC/VLR)/SSP, which sends it to the PSTN switch. The PAM-SCP then sends a 'Retrieve user profile' request to the HSS, which returns 'User profile data'. The PAM-SCP sends 'Activate the PAM service' to the HSS, which returns an 'Activate ack'. The PAM-SCP sends a 'Send registration response' to the IP. The Mobile station sends a 'Service register response' to the Access point, which sends the 'Send registration response in FSK' to the IP. The IP returns the 'Result of sending response' to the PAM-SCP, which sends a 'Release the special resource' request to the (MSC/VLR)/SSP. The (MSC/VLR)/SSP sends a 'Release' message to the IP, which returns 'Release complete'. The Access point sends an 'On hook' message to the PSTN switch, which sends a 'Release' message to the (MSC/VLR)/SSP, which returns 'Release complete'. The (MSC/VLR)/SSP sends a 'Report release event' to the PAM-SCP, which sends an 'End of query' message to the (MSC/VLR)/SSP. + +Sequence diagram showing the user registration call flow between Mobile station, Access point, PSTN switch, (MSC/VLR)/SSP, PAM-SCP, IP, and HLR/AuC (HSS). + +Q.1763/Y.2803(07)\_F08 + +Figure 8 – User registration call flow + +1. When the AP receives a user registration request, the AP automatically initiates a call to the PSTN network. The called number includes the service access code (SAC), request type (indicating the registration request) and the terminal identifier of the terminal. In this example, the user identity is sent afterwards during in-band FSK interaction to avoid the limitation of the length of the called number supported in the fixed network. + 2. The PSTN switch routes the call set-up request to the (MSC/VLR)/SSP according to the SAC. + 3. The (MSC/VLR)/SSP triggers and sends a query to the PAM-SCP. The node (MSC/VLR)/SSP is currently exercising IN SSP functionality only. MSC/VLR functions are not used in this scenario. + 4. The PAM-SCP instructs the (MSC/VLR)/SSP to establish a connection with the IP to prepare the special resource for FSK interaction. + 5. The (MSC/VLR)/SSP sets up the connection with IP via ISUP signalling. + 6. The IP acknowledges the (MSC/VLR)/SSP with a connection established response. + 7. The call set-up response is forwarded to the PSTN switch, and the bearer connection is established between the AP and the IP. + 8. The IP informs the PAM-SCP of its availability and capability. + 9. The PAM-SCP instructs the IP to send an "Info request (user identification)" (in FSK) to the AP. + 10. The "Info request (user identity)" message is sent from the IP to the AP (in FSK). + 11. The AP replies with the "user identity information" (in FSK). + 12. The IP sends the received user identity to the PAM-SCP. + 13. The PAM-SCP sends an authentication data request to the HLR/AuC (HSS) referenced by the IMSI corresponding to the user identity. + 14. The PAM-SCP receives and stores the authentication vector, including a random number, an expected response, a cipher key, an integrity key and an authentication token. + 15. The PAM-SCP instructs the IP to send the authentication data (random number, authentication token) to the AP. + 16. The authentication data is sent to the AP in FSK, the AP converts the message to wireless signalling and sends it to the terminal. + 17. The terminal verifies the authentication token and computes the result and sends the response with RES. + 18. The IP sends the received authentication result to the PAM-SCP. + 19. The PAM-SCP compares the received RES with the stored expected result. If equal, the authentication is successful and the PAM-SCP requests the user profile from the HLR/AuC (HSS). + 20. The HLR/AuC (HSS) provides the user profile to the PAM-SCP. + 21. The PAM-SCP stores the user's associated service data including MSISDN, the PSTN address of the AP and the terminal identifier in the database and sends a request to the HLR/AuC (HSS) to activate the PAM service status in T-CSI. +- NOTE – Subscription to the PAM service needs to be performed in advance, and the initial status of the PAM service is inactive. +22. The HLR/AuC (HSS) responds with a successful result for service activation. + 23. The PAM-SCP instructs the IP to send the AP the successful treatment of the user registration in FSK. + +24. The response is sent to the AP via FSK, the AP forwards the response to the terminal. +25. The IP sends the result to the PAM-SCP. +- 26a. The PAM-SCP indicates to the (MSC/VLR)/SSP to release the bearer connection with the IP. +- 27a. The MSC/VLR/SSP sends release to the IP. +- 28a. The IP responds with release complete confirmation. +- 26b. After the AP receives the registration response, the AP ends the registration process by releasing the call. +- 27b. A release call message is sent to the (MSC/VLR)/SSP. +- 28b. The (MSC/VLR)/SSP ends with the release complete confirmation. +29. The (MSC/VLR)/SSP reports the event to the PAM-SCP. +30. The PAM-SCP finishes the dialogue with the (MSC/VLR)/SSP. + +### 9.3.2 User deregistration call flow + +![Sequence diagram showing the user deregistration call flow between Mobile station, Access point, PSTN switch, (MSC/VLR)/SSP, PAM-SCP, IP, and HLR/AuC (HSS).](14252bcd35912bd656e98b16b2ee51c0_img.jpg) + +``` + +sequenceDiagram + participant MS as Mobile station + participant AP as Access point + participant PS as PSTN switch + participant MV as (MSC/VLR)/SSP + participant PS-SCP as PAM-SCP + participant IP as IP + participant HSS as HLR/AuC (HSS) + + Note left of MS: Service deregister request + MS->>AP: Service deregister request + AP->>PS: 1. Automatic call set-up (SAC request type, terminal identifier) + PS->>MV: 2. Set-up request + MV->>PS-SCP: 3. Query (triggered by N-CSI) + PS-SCP->>HSS: 4. Deactivate the PAM service + HSS->>PS-SCP: 5. Deactivate ack + PS-SCP->>MV: 6. Prepare special resource + MV->>IP: 7. Establish connection with special resource + PS->>MV: 9. Set-up response + MV->>PS-SCP: 8. Special resource connected + PS-SCP->>IP: 10. Special resource ready + PS-SCP->>MV: 11. Send deregistration response + MV-->>AP: 12. Send deregistration response in FSK + Note left of MS: Service deregister response + AP->>MS: Service deregister response + MV->>PS-SCP: 14a. Release the special resource + PS-SCP->>IP: 13. Result of sending response + MV->>IP: 15a. Release + IP->>MV: 16a. Release complete + MV->>PS: 15b. Release + PS->>MV: 16b. Release complete + MV->>PS-SCP: 17. Report release event + PS-SCP->>MV: 18. End of query + Note right of HSS: Q.1763/Y.2803(07)_F09 + +``` + +Sequence diagram showing the user deregistration call flow between Mobile station, Access point, PSTN switch, (MSC/VLR)/SSP, PAM-SCP, IP, and HLR/AuC (HSS). + +Figure 9 – User deregistration call flow + +1. When the terminal leaves the wireless coverage area of the AP, the AP sends a deregistration request to the network by means of a call set-up request containing the SAC, request type (indicating deregistration) and the terminal identifier of the terminal. +2. The PSTN switch routes the call set-up request to the (MSC/VLR)/SSP according to the SAC. +3. The (MSC/VLR)/SSP triggers and sends a query to the PAM-SCP. The node (MSC/VLR)/SSP is currently exercising IN SSP functionality only. MSC/VLR functions are not used in this scenario. +4. The PAM-SCP sends a request to the HLR/AuC (HSS) to deactivate the user's PAM service. + +5. The HLR/AuC (HSS) responds with the result of the deactivation and the PAM-SCP deletes the service data. +6. The PAM-SCP instructs the (MSC/VLR)/SSP to set-up a bearer connection to the IP to prepare the special resource for FSK interaction. +7. The (MSC/VLR)/SSP sets up a connection with the IP via ISUP signalling. +8. The IP acknowledges the (MSC/VLR)/SSP with a connection established response. +9. The connection set-up response is forwarded to the PSTN switch and the connection is set up between the AP and the IP. +10. The IP sends its availability and capability to the PAM-SCP. +11. The PAM-SCP instructs the IP to send a "Deregistration response" (in FSK) to the AP. +12. The "Deregistration response" message is sent from the IP to the AP, and the AP sends the deregistration response to the terminal in the wireless protocol if the terminal is still accessible. +13. After finishing the sending of information in-band to the AP, the IP sends to the PAM-SCP the result. +- 14a. The PAM-SCP indicates to the (MSC/VLR)/SSP to release the bearer connection with the IP. +- 15a. The (MSC/VLR)/SSP sends the release to the IP. +- 16a. The IP responds with release complete confirmation. +- 14b. When the AP receives the registration response, the AP ends the registration by releasing the call. +- 15b. The release call message is sent to the (MSC/VLR)/SSP. +- 16b. The (MSC/VLR)/SSP ends with the release complete confirmation. +17. The (MSC/VLR)/SSP reports the release event to the PAM-SCP. +18. The PAM-SCP finishes the dialogue with the (MSC/VLR)/SSP. + +### 9.3.3 Originating call flow + +![Sequence diagram of the originating call flow between Mobile station, Access point, PSTN switch, (MSC/VLR)/SSP, PAM-SCP, and IP.](399a5af4f606059626c92c92279d54b7_img.jpg) + +``` + +sequenceDiagram + participant MS as Mobile station + participant AP as Access point + participant PS as PSTN switch + participant MV as (MSC/VLR)/SSP + participant PSB as PAM-SCP + participant IP as IP + + Note right of MS: Originating call request + MS->>AP: 1. Call setup (SAC, request type, terminal identifier) + AP->>PS: 2. Call setup request + PS->>MV: 3. Query (triggered by N-CSI) + MV->>PSB: 4. Prepare special resource + MV->>IP: 5. Establish connection with special resource + IP->>MV: 6. Special resource connected + MV->>PS: 7. Setup response + PSB->>IP: 8. Special resource ready + PSB->>IP: 9. Send info request (called address) and wait for result + PSB-->>PS: 10. Send info request (called address) in FSK + PS-->>IP: 11. Send called address in DTMF/FSK + IP->>PSB: 12. Result of info request + PSB->>MV: 13. Release special resource + MV->>IP: 14. Release + MV->>MV: 15. Release complete + MV->>MV: 16. Connect called party + MV->>CP((called party)): 17. Set up connection + +``` + +Q.1763/Y.2803(07)\_F10 + +Sequence diagram of the originating call flow between Mobile station, Access point, PSTN switch, (MSC/VLR)/SSP, PAM-SCP, and IP. + +Figure 10 – Originating call flow + +1. When the terminal initiates a call, the AP automatically inserts the SAC, request type (originating call request) and the terminal identifier in the called number and sends the call set-up request to the network. In this example, the dialled called address is sent afterwards during in-band FSK interaction to avoid the limitation of the length of the called number supported in the fixed network. +2. The PSTN switch routes the call set-up request to the (MSC/VLR)/SSP according to the SAC. +3. The (MSC/VLR)/SSP triggers and initiates a query to the PAM-SCP. The node (MSC/VLR)/SSP is currently exercising IN SSP functionality only. MSC/VLR functions are not used in this scenario. +4. The PAM-SCP instructs the (MSC/VLR)/SSP to prepare the special resource for FSK interaction. +5. The (MSC/VLR)/SSP sets up a connection with the IP via ISUP signalling. +6. The IP acknowledges the (MSC/VLR)/SSP with a connection established response. +7. The call set-up response is forwarded to the PSTN switch, and the bearer connection is established between the AP and the IP. +8. The IP sends its availability and capability to the PAM-SCP. +9. The PAM-SCP instructs the IP to send "Info request (called address)" (in FSK) to the AP. +10. The "Info request (called address)" message is sent from the IP to the AP. +11. The AP replies with the "called address" (in FSK). + +12. The IP sends the received called address to the PAM-SCP. +13. The PAM-SCP indicates to the (MSC/VLR)/SSP to release the bearer connection with the IP. +14. The (MSC/VLR)/SSP sends the release to the IP. +15. The IP responds with a release complete confirmation. +16. The PAM-SCP processes the origination according to the user's service subscription (the user profile was stored on PAM-SCP during the registration phase) and sets up the connection with the called party. +17. The (MSC/VLR)/SSP sends the call set-up request to the called party, with the subsequent call handling being the same as normal IN service handling. + +### 9.3.4 Terminating call flow when PAM service is active + +![Sequence diagram showing the terminating call flow when PAM service is active. The diagram involves six lifelines: Mobile station, Access point, PSTN switch, (MSC/VLR)/SSP, PAM-SCP, and HLR/AuC (HSS). The sequence starts with an incoming call to the (MSC/VLR)/SSP, followed by a query to the HLR/AuC (HSS), a response with T-CSI, and a query triggered by T-CSI to the PAM-SCP. The PAM-SCP then instructs the (MSC/VLR)/SSP to connect via PSTN. The (MSC/VLR)/SSP sends a set-up request to the PSTN switch, which alerts the Access point, which in turn alerts the Mobile station. The Mobile station answers, and the PSTN switch sends an answer to the (MSC/VLR)/SSP, which reports the answer event to the PAM-SCP. A dashed line indicates the conversation between the Mobile station and the called party.](dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg) + +``` + +sequenceDiagram + participant MS as Mobile station + participant AP as Access point + participant PS as PSTN switch + participant MV as (MSC/VLR)/SSP + participant PSK as PAM-SCP + participant HSS as HLR/AuC (HSS) + + Note right of MV: 1. Incoming call + MV->>HSS: 2. Query the service and routing info + HSS-->>MV: 3. Response with the T-CSI + Note right of MV: 4. Query triggered by T-CSI + MV->>PSK: + PSK-->>MV: 5. Connect via PSTN + MV->>PS: 6. Set-up request + PS->>AP: 7. Alerting + AP->>MS: Alerting + MS->>AP: Answer + AP->>PS: Answer + PS->>MV: 8. Answer + MV->>PSK: 9. Report answer event + Note right of MV: In conversation + Note right of PSK: called party + +``` + +Q.1763/Y.2803(07)\_F11 + +Sequence diagram showing the terminating call flow when PAM service is active. The diagram involves six lifelines: Mobile station, Access point, PSTN switch, (MSC/VLR)/SSP, PAM-SCP, and HLR/AuC (HSS). The sequence starts with an incoming call to the (MSC/VLR)/SSP, followed by a query to the HLR/AuC (HSS), a response with T-CSI, and a query triggered by T-CSI to the PAM-SCP. The PAM-SCP then instructs the (MSC/VLR)/SSP to connect via PSTN. The (MSC/VLR)/SSP sends a set-up request to the PSTN switch, which alerts the Access point, which in turn alerts the Mobile station. The Mobile station answers, and the PSTN switch sends an answer to the (MSC/VLR)/SSP, which reports the answer event to the PAM-SCP. A dashed line indicates the conversation between the Mobile station and the called party. + +Figure 11 – Terminating call flow + +1. The (MSC/VLR)/SSP receives the incoming call request (in case the calling party is a PSTN user). +2. The GMSC/SSP queries the HLR/AuC (HSS) for the called user's service and routing info. +3. Because the PAM service is active, the HLR/AuC (HSS) returns the user's PAM service attribute instead of a routing number per normal procedures. +4. The GMSC/SSP triggers on the T-CSI and sends a query to the PAM-SCP. +5. The PAM-SCP obtains the AP address and terminal identifier corresponding to the MSISDN in the service database. The PAM-SCP instructs the GMSC/SSP to set-up the connection accordingly. In the connection message, the called number is the AP address and the original calling party number plus the terminal identifier of the terminal is sent to the SSP. + +NOTE – The format of the calling party number to carry the terminal identifier may be defined by the operator. For example, the SAC + terminal identifier + original calling party number. + +6. The GMSC/SSP sets up the call to the PSTN switch. +7. If the AP is idle, the AP receives the alerting signal, and the calling party number is sent to the AP during alerting. The AP subtracts the terminal identifier and sets up the call with the mobile terminal. +8. When the terminal answers, the event is sent from the PSTN switch to the GMSC/SSP. +9. The GMSC/SSP reports the answer event to the PAM-SCP, with the subsequent call handling being the same as normal IN service handling. + +# Bibliography + +- [b-ETSI TS 123 078] ETSI TS 123 078 (2006), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Customized Applications for Mobile network Enhanced Logic (CAMEL) Phase X; Stage 2 (3GPP TS 23.078 version 6.9.0 Release 6)*. +- [b-ETSI TS 129 002] ETSI TS 129 002 (2007), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Mobile Application Part (MAP) specification (3GPP TS 29.002 version 6.16.0 Release 6)*. +- [b-ETSI TS 133 102] ETSI TS 133 102 (2002), *Universal Mobile Telecommunications System (UMTS); 3G security; Security architecture (3GPP TS 33.102 version 4.5.0 Release 4)*. +- [b-Bluetooth] *Bluetooth specification Version 2.0 + EDR*, +- [b-IEEE 802.11g] IEEE Standard 802.11g-2003, *Information technology – Telecommunications and information exchange between systems – Local and metropolitan area networks – Specific requirements – Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications – Amendment 4: Further Higher-Data Rate Extension in the 2.4 GHz Band*. +- [b-IETF RFC 1321] IETF RFC 1321 (1992), *The MD5 Message-Digest Algorithm*. +- [b-IETF RFC 3174] IETF RFC 3174 (2001), *US Secure Hash Algorithm 1 (SHA1)*. +- [b-NIST SHA-256] NIST, Federal Information Processing Standards Publications (FIPS PUB) 180-2 (2002), *Secure Hash Standard (SHS)*. + +# ITU-T Y-SERIES RECOMMENDATIONS + +## GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS + +## GLOBAL INFORMATION INFRASTRUCTURE + +| | | +|-------------------------------------------|-------------| +| General | Y.100–Y.199 | +| Services, applications and middleware | Y.200–Y.299 | +| Network aspects | Y.300–Y.399 | +| Interfaces and protocols | Y.400–Y.499 | +| Numbering, addressing and naming | Y.500–Y.599 | +| Operation, administration and maintenance | Y.600–Y.699 | +| Security | Y.700–Y.799 | +| Performances | Y.800–Y.899 | + +### INTERNET PROTOCOL ASPECTS + +| | | +|--------------------------------------------------------------------|---------------| +| General | Y.1000–Y.1099 | +| Services and applications | Y.1100–Y.1199 | +| Architecture, access, network capabilities and resource management | Y.1200–Y.1299 | +| Transport | Y.1300–Y.1399 | +| Interworking | Y.1400–Y.1499 | +| Quality of service and network performance | Y.1500–Y.1599 | +| Signalling | Y.1600–Y.1699 | +| Operation, administration and maintenance | Y.1700–Y.1799 | +| Charging | Y.1800–Y.1899 | + +## NEXT GENERATION NETWORKS + +| | | +|-------------------------------------------------------------------|----------------------| +| Frameworks and functional architecture models | Y.2000–Y.2099 | +| Quality of Service and performance | Y.2100–Y.2199 | +| Service aspects: Service capabilities and service architecture | Y.2200–Y.2249 | +| Service aspects: Interoperability of services and networks in NGN | Y.2250–Y.2299 | +| Numbering, naming and addressing | Y.2300–Y.2399 | +| Network management | Y.2400–Y.2499 | +| Network control architectures and protocols | Y.2500–Y.2599 | +| Security | Y.2700–Y.2799 | +| Generalized mobility | Y.2800–Y.2899 | + +For further details, please refer to the list of ITU-T Recommendations. + +## 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/Q/T-REC-Q.2119-199607-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2119-199607-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7e5b66873e24fe57ad2736a8d7f16737bd51d70b --- /dev/null +++ b/marked/Q/T-REC-Q.2119-199607-I_PDF-E/raw.md @@ -0,0 +1,398 @@ + + +![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 + +**Q.2119** + +(07/96) + +SERIES Q: SWITCHING AND SIGNALLING + +Broadband ISDN – ATM adaptation layer + +--- + +**B-ISDN ATM adaptation layer – Convergence +function for SSCOP above the frame relay core +service** + +ITU-T Recommendation Q.2119 + +(Previously CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +## **SWITCHING AND SIGNALLING** + +| | | +|--------------------------------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATION OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| General aspects | Q.2000–Q.2099 | +| ATM adaptation layer | Q.2100–Q.2199 | +| Signalling network protocols | Q.2200–Q.2599 | +| Common aspects of B-ISDN application protocols for access signalling and network signalling and interworking | Q.2600–Q.2699 | +| B-ISDN application protocols of the network | Q.2700–Q.2899 | +| B-ISDN application protocols for access signalling | Q.2900–Q.2999 | + +For further details, please refer to ITU-T List of Recommendations. + +# **ITU-T RECOMMENDATION Q.2119** + +## **B-ISDN ATM ADAPTATION LAYER – CONVERGENCE FUNCTION FOR SSCOP ABOVE THE FRAME RELAY CORE SERVICE** + +## **Summary** + +This Recommendation specifies a mapping function that allows B-ISDN data communications applications utilizing protocol stacks which include SSCOP (Recommendation Q.2110) also to be deployed in an HDLC-based environment. The required mapping function is called "convergence function for SSCOP above the frame relay core service". + +This Recommendation makes use of the fact that the subset of services provided by AAL type 5 (Recommendation I.363.5) that SSCOP uses can also be provided by the services of the core service for the frame mode bearer services (Annex A/Q.922). + +This Recommendation also provides, in Annex A, suggested parameter values for use in support of SS No. 7 applications. Such an arrangement would allow one approach to a migration from N-ISDN to B-ISDN. + +This Recommendation is applicable to equipment to be attached to a frame relay network when protocol stacks developed for a B-ISDN environment are deployed in a narrow-band environment. + +## **Source** + +ITU-T Recommendation Q.2119 was prepared by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 9th of July 1996. + +## **Keywords** + +AAL, B-ISDN, frame relay, N-ISDN, SSCOP and SS No. 7 + +## 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 Normative references..... | 1 | +| 3 Definitions ..... | 2 | +| 4 Abbreviations..... | 2 | +| 5 General description..... | 2 | +| 6 Functions of the convergence function..... | 3 | +| 7 Specification of the convergence function..... | 3 | +| 7.1 The CPCS service of the AAL type 5 ..... | 3 | +| 7.2 The core service of the frame mode bearer service..... | 4 | +| 7.3 PDU format..... | 4 | +| 7.4 Mapping the AAL type 5 CPCS signal into the frame relay core service primitives (transmitter) ..... | 5 | +| 7.5 Mapping the frame relay core service primitives into the AAL type 5 CPCS signal (receiver)..... | 5 | +| 7.6 Layer management..... | 5 | +| Annex A – Use of the frame relay core service for SS No. 7 signalling links at the NNI..... | 6 | +| Appendix I – Impact of 32-bit alignment in SSCOP on the DL-CORE-DATA-PDU format. | 7 | + + + +## **B-ISDN ATM ADAPTATION LAYER – CONVERGENCE FUNCTION FOR SSCOP ABOVE THE FRAME RELAY CORE SERVICE** + +*(Geneva, 1996)* + +# **1 Scope** + +This Recommendation specifies a function that allows B-ISDN data communication applications utilizing protocol stacks which include SSCOP [3] also to be deployed in an HDLC-based environment. The required mapping function specified in this Recommendation is called "convergence function for SSCOP above the frame relay core service". + +This Recommendation makes use of the fact that SSCOP uses only a subset of the services offered by the preferred underlying (sub)layer, the AAL type 5 [1]. This particular service subset can also be derived as a subset from the service of the core service for the frame mode bearer service as specified in Annex A/Q.922 [2]. + +This Recommendation is applicable to equipment to be attached to a frame relay network when protocol stacks developed for a B-ISDN environment are deployed in a narrow-band environment. If this Recommendation is applied to signalling at a B-ISDN Network Node Interface (NNI), Annex A specifies further restrictions on the use of the frame relay core service. + +# **2 Normative 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 I.363 (1993), *B-ISDN ATM Adaptation Layer (AAL) specification*. +- [2] CCITT Recommendation Q.922 (1992), *ISDN data link layer specification for frame mode bearer services*. +- [3] ITU-T Recommendation Q.2110 (1994), *B-ISDN signalling ATM Adaptation – Service Specific Connection Oriented Protocol (SSCOP)*. +- [4] ITU-T Recommendation X.200 (1994), *Information technology – Open Systems Interconnection – Basic reference model: The basic model*. +- [5] ITU-T Recommendation X.210 (1993), *Information technology – Open Systems Interconnection – Basic reference model: Conventions for the definition of OSI Services*. +- [6] ITU-T Recommendation I.365.1 (1993), *B-ISDN ATM adaptation layer sublayers: Frame Relaying Service Specific Conversion Sublayer (FR-SSCS)*. +- [7] CCITT Recommendation I.233.1 (1991), *Frame mode bearer services: ISDN – Frame relaying bearer service*. +- [8] ITU-T Recommendation X.263 (1995) | ISO/IEC TR 9577: 1996, *Information technology – Protocol identification in the Network Layer*. + +[9] ITU-T Recommendation Q.704 (1996), *Signalling network functions and messages*. + +# 3 Definitions + +The term "frame relay core service" refers to the core aspects of the frame relaying bearer service (see Annex A/Q.922 [2]). Otherwise, this Recommendation introduces no new terms beyond the ones defined in Recommendations Q.2110 [3] and Q.922 [2]. As in those Recommendations, extensive use is made of the layering concepts defined in Recommendation X.200 [4] and the service primitive concepts defined in Recommendation X.210 [5]. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations. + +| | | +|----------|-----------------------------------------------| +| AAL | ATM Adaptation Layer | +| ATM | Asynchronous Transfer Mode | +| CP | Common Part | +| CPCS | Common Part Convergence Sublayer | +| CPCS-CI | CPCS-Congestion Indication | +| CPCS-LP | CPCS-Loss Priority | +| CPCS-UU | CPCS-User-to-User-Indication | +| DLCI | Data Link Connection Identifier | +| HDLC | High-level Data Link Control | +| IPI | Initial Protocol Identifier | +| PCI | Protocol Control Information | +| PDU | Protocol Data Unit | +| SAAL | AAL for Signalling | +| SAP | Service Access Point | +| SS No. 7 | Signalling System No. 7 | +| SSCOP | Service Specific Connection-Oriented Protocol | + +# 5 General description + +The convergence function for SSCOP above the frame relay core service provides for the possibility, to deploy SSCOP (Recommendation Q.2110 [3]) on top of the frame relay core service. The frame relay core service is implemented as frame relay services utilizing the protocol according to Annex A/Q.922 [2] (used on leased lines or narrow-band ISDN) or utilizing the protocol according to Recommendation I.365.1 [6] (as an AAL type 5 on B-ISDN). + +All protocol stacks that include SSCOP can, therefore, also be used in a frame relay environment (see Figure 1). For an intermediate period of time, a particular application of this Recommendation is in a protocol stack for SS No. 7 signalling. This option is defined further in Annex A. + +![Diagram illustrating the environment for the convergence function for SSCOP above the frame relay core service. It shows two parallel protocol stacks. The left stack is for B-ISDN, with 'Higher Layers' at the top, followed by 'SSCOP', then 'SSCOP Rec.Q.2110', then 'AAL type 5 CPCS service' (containing 'AAL type 5 Common Part' with 'CPCS' and 'SAR' sub-layers), and finally 'ATM Physical Layer'. The right stack is for 'FR or other', with 'Higher Layers' at the top, followed by 'Signals', then 'SSCOP Rec.Q.2110', then '(This Recommendation) Q.2119' (labeled as 'AAL type 5 CPCS service'), then 'Frame Relay Core Service', and finally 'Physical Layer'. Vertical double-headed arrows on both sides indicate that the 'Protocol Stacks' are 'identical' between the B-ISDN and FR or other environments. A vertical line separates the two stacks. A small label 'T1175410-95' is at the bottom right.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +Diagram illustrating the environment for the convergence function for SSCOP above the frame relay core service. It shows two parallel protocol stacks. The left stack is for B-ISDN, with 'Higher Layers' at the top, followed by 'SSCOP', then 'SSCOP Rec.Q.2110', then 'AAL type 5 CPCS service' (containing 'AAL type 5 Common Part' with 'CPCS' and 'SAR' sub-layers), and finally 'ATM Physical Layer'. The right stack is for 'FR or other', with 'Higher Layers' at the top, followed by 'Signals', then 'SSCOP Rec.Q.2110', then '(This Recommendation) Q.2119' (labeled as 'AAL type 5 CPCS service'), then 'Frame Relay Core Service', and finally 'Physical Layer'. Vertical double-headed arrows on both sides indicate that the 'Protocol Stacks' are 'identical' between the B-ISDN and FR or other environments. A vertical line separates the two stacks. A small label 'T1175410-95' is at the bottom right. + +**Figure 1/Q.2119 – Environment for the convergence function for SSCOP above the frame relay core service** + +# 6 Functions of the convergence function + +The purpose of the convergence function is to map SSCOP signals that use a subset of the AAL type 5 Common Part Convergence Sublayer (CPCS) service into a subset of the frame relay core service. In addition, a protocol identifier is added at the beginning of the frame relay core service PDU as is customarily done in the frame relay environment. + +# 7 Specification of the convergence function + +## 7.1 The CPCS service of the AAL type 5 + +The CPCS service of the AAL type 5 is defined in clause 6/I.363 [1]. Table 1 summarizes the primitives and parameters in the AAL type 5 CPCS service. Where there are differences between the definitions in this Recommendation and those in Recommendation I.363, the one in Recommendation I.363 is definitive. + +SSCOP (Recommendation Q.2110) defines the use of the parameters as follows: + +**Table 1/Q.2119 – AAL type 5 CPCS service primitives and parameters** + +| | CPCS-UNITDATA.invoke | CPCS-UNITDATA.signal | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------| +| Interface Data (ID) | X | X | +| More (M) (Note 1) | - | - | +| CPCS-Loss Priority (CPCS-LP) | X | X | +| CPCS-Congestion-Indication (CPCS-CI) | X | X | +| CPCS-User-to-User-Indication (CPCS-UU) | X | X | +| Reception Status (RS) (Note 2) | - | - | +| NOTE 1 – Not present in message mode.
NOTE 2 – Not present as the corrupted data delivery option is not utilized.
  • Only message mode is utilized.
  • The CPCS-LP parameter is set to "0" at the transmitter and ignored at the receiver.
  • The CPCS-CI parameter is set to "0" at the transmitter and its use by the receiver is for further study.
  • The CPCS-UU parameter is set to "0" at the transmitter and ignored at the receiver.
  • The corrupted data delivery option is not utilized.
| | | + +## 7.2 The core service of the frame mode bearer service + +The frame relay core service is defined in Annex A/Q.922 [2] and in Annex D/I.233.1 [7]. Table 2 summarizes the primitives and parameters in the frame relay core service. Where there are differences between the definitions in this Recommendation and those in Recommendation Q.922 or I.233.1, the one in Recommendation Q.922 is definitive. + +**Table 2/Q.2119 – Core service primitives and parameters** + +| | Core-DATA.request | Core-DATA.indication | +|------------------------------------------------|-------------------|----------------------| +| Core-user-data | X | X | +| Discard eligibility (optional) | X | - | +| Congestion encountered backward (optional) | - | X | +| Congestion encountered forward (optional) | - | X | +| Core service user protocol control information | X | X | + +## 7.3 PDU format + +SSCOP PDUs are prepended with two octets of PCI information. This is required to carry the protocol identifier; this situation is depicted in Figure 2. The coding of these two octets is as follows: + +### 1) *Octet 1: Unnumbered Information "UI"* + +This octet shall be coded as 0000-00112. + +### 2) *Octet 2: Protocol identifier* + +This octet contains an Initial Protocol Identifier (IPI) and shall be coded as 0000-10102 (this value is specified in ITU-T Rec. X.263 | ISO/IEC TR 9577 [8]). + +NOTE – Discussion of the impact of 32-bit alignment in SSCOP on the DL-CORE-DATA-PDU format can be found in Appendix I. + +| Octets | | | +|--------|---------------------|-----------| +| 1 | 2 | 3 to n | +| "UI" | Protocol Identifier | SSCOP PDU | + +T1175420-95 + +**Figure 2/Q.2119 – PDU format to embed an SSCOP PDU in a frame relay SDU** + +## **7.4 Mapping the AAL type 5 CPCS signal into the frame relay core service primitives (transmitter)** + +As shown in Figure 3, upon receipt of a CPCS-UNITDATA.invoke signal from SSCOP, a DL-CORE-DATA.request primitive is formed with the parameters noted below and submitted to the frame relay core service: + +- a) The "core-user-data" parameter is formed as specified in 7.3 using the "interface data" parameter of the CPCS-UNITDATA.invoke signal (SSCOP PDU). +- b) The "discard eligibility" parameter is set to "0". +- c) The "core service user protocol control information" parameter is set to "0". + +## **7.5 Mapping the frame relay core service primitives into the AAL type 5 CPCS signal (receiver)** + +As shown in Figure 3, upon receipt of a DL-CORE-DATA.indication primitive from the frame relay core service, a CPCS-UNITDATA.signal signal is formed with the parameters noted below and sent to SSCOP: + +- a) The "interface data" parameter is set to the value of the SSCOP PDU field of the "core-user-data" parameter of the DL-CORE-DATA.indication primitive (see 7.3). +- b) The "CPCS-loss priority" parameter is set to "0". +- c) The "CPCS-congestion indication" parameter is set to "0"; whether a mapping from the "congestion encountered forward" parameter of the DL-CORE-DATA.indication primitive is performed in some situations is for further study. +- d) The "CPCS-user-to-user-indication" parameter is set to "0". + +## **7.6 Layer management** + +There are no interactions with layer management defined. Interactions to report the values of the congestion management parameters of the frame relay core service are for further study. + +![Diagram showing the relationship of AAL type 5 CPCS signals and frame relay core service primitives. A central box labeled 'Rec. Q.2119' has two dashed vertical lines. The left dashed line is labeled 'As defined in 7.4' and has an arrow pointing down from 'CPCS-UNITDATA.invoke' and an arrow pointing up to 'Core-DATA.request'. The right dashed line is labeled 'As defined in 7.5' and has an arrow pointing down from 'CPCS-UNITDATA.signal' and an arrow pointing up to 'Core-DATA.indication'. The text 'T1175430-95' is at the bottom right.](d4af765160d04ecef538e5066006dc77_img.jpg) + +Diagram showing the relationship of AAL type 5 CPCS signals and frame relay core service primitives. A central box labeled 'Rec. Q.2119' has two dashed vertical lines. The left dashed line is labeled 'As defined in 7.4' and has an arrow pointing down from 'CPCS-UNITDATA.invoke' and an arrow pointing up to 'Core-DATA.request'. The right dashed line is labeled 'As defined in 7.5' and has an arrow pointing down from 'CPCS-UNITDATA.signal' and an arrow pointing up to 'Core-DATA.indication'. The text 'T1175430-95' is at the bottom right. + +**Figure 3/Q.2119 – Relationship of AAL type 5 CPCS signals and frame relay core service primitives** + +# **ANNEX A** + +## **Use of the frame relay core service for SS No. 7 signalling links at the NNI** + +This Annex specifies constraints on the values of frame relay and SSCOP parameters if this Recommendation is used for a signalling link at an NNI. The protocol stack applied in this use is shown in Figure A.1. + +![](7f17c430b9598e4d748a8041457810b3_img.jpg) + +| | | +|-------------------------------------------------------------------|-----------------| +| MTP Level 3 | e.g. Rec. Q.704 | +| SSCF at NNI | Rec. Q.2140 | +| SSCOP | Rec. Q.2110 | +| Convergence Function for SSCOP above the Frame Relay Core Service | Annex A/Q.2119 | +| Core Service of the Frame Mode Bearer Service | Annex A/Q.922 | +| Physical Layer | e.g. Rec. I.430 | + +T1175440-95 + +**Figure A.1/Q.2119 – Example C-plane protocol stack using Q.2119 to support SS No. 7 signalling applications** + +### **A.1 Configuration** + +SS No. 7 signalling links that utilize a protocol stack including Recommendations Q.2119, Q.2110 and Q.2140 are deployed on a single "physical layer" end-to-end connection. For this application of Q.2119, a constraint is placed on the configuration such that the functionality of a frame relay network with multiplexing at the layer 2 of traffic directed to different destinations is not used. + +### **A.2 Address field format** + +The default two-octet Data Link Connection Identifier (DLCI) format shall be used. By bilateral agreement, other DLCI formats may be used. + +### **A.3 DLCI value** + +The decimal value 256 is assigned to the Data Link Connection Identifier (DLCI). By bilateral agreement, other values may be used. + +### **A.4 Frame relay management procedures** + +Neither the consolidated link layer management procedures (Annex A/Q.922 [2]) nor the permanent virtual connection management procedures (Annex A/Q.933) shall be used. + +### **A.5 Congestion control** + +No frame mode bearer service congestion control procedures shall be used. + +### **A.6 Maximum PDU length** + +All networks shall support a default maximum length of the SSCOP information field (parameter "k" in Recommendation Q.2110) equal to 272 octets. Additional values for the maximum length of the SSCOP information field may be used upon bilateral agreement. + +NOTE – The default maximum length SSCOP PDU is composed of a 272 octet SSCOP SDU (sized to contain an MTP-3 peer-to-peer message defined in Recommendation Q.704 [9]) and 4 octets of SSCOP PCI. + +# **APPENDIX I** + +## **Impact of 32-bit alignment in SSCOP on the DL-CORE-DATA-PDU format** + +SSCOP is designed for a 32-bit environment; hence, its PDUs are designed to be aligned at 32-bit boundaries. If a default DLCI field length of two octets is used, the aligned structure is as shown in Figure I.1. With DLCI fields larger than two octets, i.e. three or four octets, the 32-bit alignment for the SSCOP PDUs can be achieved by putting the start of the DLCI other than at a 32-bit boundary as shown in Figures I.2 and I.3. As the HDLC environment of the frame relay core service of the frame mode bearer service is octet oriented, the beginning of the DLCI field need not be 32-bit aligned. + +![Diagram of a typical SSCOP PDU embedded in a frame relay PDU when a 2-octet DLCI is used. The diagram shows a frame structure with columns for Octets 1, 2, 3, and 4. Row 1 contains the header: Octet 1 is the first byte of the 2-octet DLCI, Octet 2 is the second byte of the DLCI, Octet 3 contains the 'UI' value, and Octet 4 contains the Protocol Identifier. Row 2 is the SSCOP SDU. Row 3 is a PAD (0..3 octets). Row N is the SSCOP PCI. Row N+1 is the FCS (CRC), with bits 8 through 1 shown below it. The identifier T1175450-95 is in the bottom right.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +Diagram of a typical SSCOP PDU embedded in a frame relay PDU when a 2-octet DLCI is used. The diagram shows a frame structure with columns for Octets 1, 2, 3, and 4. Row 1 contains the header: Octet 1 is the first byte of the 2-octet DLCI, Octet 2 is the second byte of the DLCI, Octet 3 contains the 'UI' value, and Octet 4 contains the Protocol Identifier. Row 2 is the SSCOP SDU. Row 3 is a PAD (0..3 octets). Row N is the SSCOP PCI. Row N+1 is the FCS (CRC), with bits 8 through 1 shown below it. The identifier T1175450-95 is in the bottom right. + +**Figure I.1/Q.2119 – Typical SSCOP PDU embedded in a frame relay PDU when a 2-octet DLCI is used** + +![Diagram of a typical SSCOP PDU embedded in a frame relay PDU when a 3-octet DLCI is used. The diagram shows a frame structure with columns for Octets 1, 2, 3, and 4. Row 1 contains the first byte of the 3-octet DLCI (DLCI octet 1). Row 2 contains the remaining two bytes of the DLCI (DLCI octet 2 and 3), the 'UI' value, and the Protocol Identifier. Row 3 is the SSCOP SDU. Row 4 is a PAD (0..3 octets). Row N is the SSCOP PCI. Row N+1 is the FCS (CRC), with bits 8 through 1 shown below it. The identifier T1175460-95 is in the bottom right.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) + +Diagram of a typical SSCOP PDU embedded in a frame relay PDU when a 3-octet DLCI is used. The diagram shows a frame structure with columns for Octets 1, 2, 3, and 4. Row 1 contains the first byte of the 3-octet DLCI (DLCI octet 1). Row 2 contains the remaining two bytes of the DLCI (DLCI octet 2 and 3), the 'UI' value, and the Protocol Identifier. Row 3 is the SSCOP SDU. Row 4 is a PAD (0..3 octets). Row N is the SSCOP PCI. Row N+1 is the FCS (CRC), with bits 8 through 1 shown below it. The identifier T1175460-95 is in the bottom right. + +**Figure I.2/Q.2119 – Typical SSCOP PDU embedded in a frame relay PDU when a 3-octet DLCI is used** + +![Diagram of a typical SSCOP PDU embedded in a frame relay PDU. The diagram shows a frame structure with fields: Header (DLCI octet 1 and 2, DLCI octet 3 and 4, 'UI', Protocol Identifier), SSCOP SDU (containing PAD), SSCOP PCI, and FCS (CRC).](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +The diagram illustrates the structure of a typical SSCOP PDU embedded in a frame relay PDU when a 4-octet DLCI is used. The frame is divided into several fields: + +- Header:** + - DLCI octet 1 and 2 (Octets 3 and 4) + - DLCI octet 3 and 4 (Octet 2) + - "UI" (Octet 3) + - Protocol Identifier (Octet 4) +- SSCOP SDU:** The main data payload, which may include a **PAD (0..3 octets)** at its end. +- SSCOP PCI:** Located at the end of the SSCOP SDU (Octet N). +- FCS (CRC):** The frame check sequence, consisting of 8 octets (8 7 6 5 4 3 2 1). + +Reference: T1175470-95 + +Diagram of a typical SSCOP PDU embedded in a frame relay PDU. The diagram shows a frame structure with fields: Header (DLCI octet 1 and 2, DLCI octet 3 and 4, 'UI', Protocol Identifier), SSCOP SDU (containing PAD), SSCOP PCI, and FCS (CRC). + +**Figure I.3/Q.2119 – Typical SSCOP PDU embedded in a frame relay PDU when a 4-octet DLCI is used** + +# 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/Q/T-REC-Q.2961B-200012-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2961B-200012-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..981435e1aeba4506a484c3add2ab2e8d642deb93 --- /dev/null +++ b/marked/Q/T-REC-Q.2961B-200012-I_PDF-E/raw.md @@ -0,0 +1,967 @@ + + +![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** + +**Q.2961 B** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(12/2000) + +SERIES Q: SWITCHING AND SIGNALLING + +Broadband ISDN – B-ISDN application protocols for +access signalling + +--- + +**Digital subscriber signalling system No. 2 +(DSS2) – Additional traffic parameters: +Protocol implementation conformance +statement (PICS) proforma** + +ITU-T Recommendation Q.2961 B + +(Formerly CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +# SWITCHING AND SIGNALLING + +| | | +|--------------------------------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| General aspects | Q.2000-Q.2099 | +| Signalling ATM adaptation layer (SAAL) | Q.2100-Q.2199 | +| Signalling network protocols | Q.2200-Q.2299 | +| Common aspects of B-ISDN application protocols for access signalling and network signalling and interworking | Q.2600-Q.2699 | +| B-ISDN application protocols for the network signalling | Q.2700-Q.2899 | +| B-ISDN application protocols for access signalling | Q.2900-Q.2999 | + +For further details, please refer to the list of ITU-T Recommendations. + +## **Digital subscriber signalling system No. 2 (DSS2) – Additional traffic parameters: Protocol implementation conformance statement (PICS) proforma** + +## **Summary** + +This Recommendation specifies the Protocol Implementation Conformance Statement (PICS) proforma for the $T_B$ reference point or coincident $S_B$ and $T_B$ reference point (as defined in ITU-T I.413 [7]) of implementations conforming to the procedures for the handling of additional traffic parameters that may be used for basic call and connection control of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the Broadband Integrated Services Digital Network (B-ISDN), ITU-T Recommendations of the Q.2961 series [1], [2], [3], [4], [5] and [6]. + +Other Recommendations of the Q.2961 family specify Test Suite Structure and Test Purposes (TSS & TP) and Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on this Recommendation. + +NOTE – This Recommendation related to protocol conformance is published only in English; it is based on an external SDO's standard published in English. + +###### **Source** + +ITU-T Recommendation Q.2961 B was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 6 December 2000. + +## 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 Endorsement..... | 2 | +| 4 Coverage ..... | 2 | +| 5 Modifications ..... | 2 | +| 5.1 General..... | 2 | +| 5.2 Abbreviations ..... | 3 | +| 5.3 Conventions ..... | 3 | +| 5.4 Additional capabilities ..... | 4 | +| 5.5 CDVT descriptor IE ..... | 8 | +| 5.6 Information elements contents for the user..... | 10 | +| 5.7 Information elements contents for the network ..... | 17 | +| Appendix I – Bibliography ..... | 25 | + + + +# **Digital subscriber signalling system No. 2 (DSS2) – Additional traffic parameters: Protocol implementation conformance statement (PICS) proforma** + +# 1 Scope + +This Recommendation specifies the Protocol Implementation Conformance Statement (PICS) proforma for the $T_B$ reference point or coincident $S_B$ and $T_B$ reference point (as defined in ITU-T I.413 [7]) of implementations conforming to the procedures for the handling of additional traffic parameters that may be used for basic call and connection control of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the Broadband Integrated Services Digital Network (B-ISDN), ITU-T Recommendations of the Q.2961 series [1], [2], [3], [4], [5] and [6]. + +Other Recommendations of the Q.2961 family specify Test Suite Structure and Test Purposes (TSS & TP) and Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on this Recommendation. + +This Recommendation is applicable to equipment, supporting capabilities for the indication of traffic parameters above of the peak cell rate at connection request time, to be attached at either side of a $T_B$ reference point or coincident $S_B$ and $T_B$ reference point when used as an access to the public B-ISDN. + +To evaluate conformance of a particular implementation, it is necessary to have a statement of which capabilities and options have been implemented for a given protocol. Such a statement is called an Implementation Conformance Statement (ICS). An ICS stating what capabilities and options have been implemented for a particular protocol is called a protocol ICS. This is commonly abbreviated to "PICS". + +The supplier of a protocol implementation that is claimed to conform to any of the Recommendations of the Q.2961 series [1], [2], [3], [4], [5] and [6], is required to complete a copy of the PICS proforma provided in Annex A of the endorsed document as modified by this Recommendation. + +NOTE – No PICS proforma is required to be completed for implementation capabilities not covered by this Recommendation. For coverage of capabilities, refer to clause 4. + +# 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; 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.2961.1 (1995), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Additional signalling capabilities to support traffic parameters for the tagging option and the sustainable cell rate parameter set.* +- [2] ITU-T Q.2961.2 (1997), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Support of ATM transfer capability in the broadband bearer capability information element.* +- [3] ITU-T Q.2961.3 (1997), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Signalling capabilities to support traffic parameters for the available bit rate (ABR) ATM transfer capability.* + +- [4] ITU-T Q.2961.4 (1997), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Signalling capabilities to support traffic parameters for the ATM block transfer (ABT) ATM transfer capability.* +- [5] ITU-T Q.2961.5 (1999), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Additional traffic parameters for cell delay variation tolerance indication.* +- [6] ITU-T Q.2961.6 (1998), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Additional signalling procedures for the support of the SBR2 and SBR3 ATM transfer capabilities.* +- [7] ITU-T I.413 (1993), *B-ISDN user-network interface.* +- [8] ETSI EN 301 068-2 V1.1.3 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; ATM transfer capability and traffic parameter indication; Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification.* + +# 3 Endorsement + +The text of ETSI EN 301 068-2 [8] was approved by ITU-T as Recommendation Q.2961 B with agreed modifications as given below. + +NOTE – Underlining and/or strike-out is used to highlight new or deleted text where detailed indication of modifications is necessary. + +# 4 Coverage + +This Recommendation covers ITU-T Q.2961.1 [1], Q.2961.2 [2] as modified by ITU-T Q.2961.2 Corrigendum 1 (03/99), Q.2961.3 [3], Q.2961.4 [4], Q.2961.5 [5] and Q.2961.6 [6]. + +# 5 Modifications + +## 5.1 General + +Throughout the text of ETSI EN 301 068-2 [8] replace references and text as shown in the following table: + +| Reference in ETSI EN 301 068-2 | Modified reference | +|--------------------------------|-------------------------------| +| EN 301 068-1 | Q.2961-series Recommendations | +| EN | Recommendation | +| Standard | Recommendation | + +### Page 4, Intellectual Property Rights + +Delete the whole section. + +### Page 4, Foreword + +Delete the whole Foreword. + +NOTE 1 – It is replaced by the Foreword of this Recommendation. + +### **Page 5, Clause 1 Scope** + +Replace the whole clause with the following: + +#### **"1 Scope** + +See clause 1 Scope of this Recommendation above." + +### **Page 5, Clause 2 References** + +Replace references [1] and [3] with the following below: + +[1] Void + +[3] Void + +NOTE 2 – These references are not used in the body of ETSI EN 301 068-2 but in its Scope, which is replaced by the Scope of this Recommendation. + +### **Page 21, History** + +Delete the whole clause "History". + +## **5.2 Abbreviations** + +In clause 3.2 "Abbreviations", add the following new abbreviations: + +CDVT Cell Delay Variation Tolerance + +FRBS Frame Relaying Bearer Service + +FRT Fixed Round-trip Time + +ICR Initial Cell Rate + +MBS Maximum Burst Size + +MCR Minimum Cell Rate + +PCR Peak Cell Rate + +RDF Rate Decrease Factor + +RIF Rate Increase Factor + +RM Resource Management (cell) + +SCR Sustainable Cell Rate + +TBE Transient Buffer Exposure + +## **5.3 Conventions** + +Modify the section "Reference column" of clause A.1.2 "Abbreviations and conventions" as below: + +#### **Reference column** + +"The reference column makes reference to EN 301 068-1 [4], except where explicitly stated otherwise. Whenever reference is made directly to ITU-T Q.2961.x, it means as endorsed by EN 301 068-1 [4]." + +## 5.4 Additional capabilities + +Modify Table A.1 "Roles" of clause A.5 "Roles" as below: + +| Item | Major role:
Does the implementation support ... | Conditions
for status | Status | Reference | Support | +|------------------------------------------------------------------------|--------------------------------------------------------------------------|--------------------------|------------|-----------|----------------------------------------------------------| +| R1.1 | the user role? | | O.1 | | Yes No | +| R1.2 | the network role? | | O.1 | | Yes No | +| R2.1 | support requirements for the coincident SB and TB reference point | | O.2 | | Yes No | +| R2.2 | support requirements for the TB reference point | | O.2 | | Yes No | +| O.1 It is mandatory to support exactly one of these items. | | | | | | +| O.2 Support of one, and only one, of these options is required. | | | | | | +| Comments: | | | | | | + +Modify Table A.2 "Major capabilities" of clause A.6.1 "Major capabilities": + +| Item | Major capability:
Does the implementation ... | Conditions
for status | Status | Reference | Support | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|--------------------------|--------------------|-----------------|------------------------------------------------------------------------------------------| +| MCu1 | support the DBR ATC? | | O.2 | Q.2961.2 | Yes No | +| MCu2 | support the SBR ATC? | | O.2 | Q.2961.2 | Yes No | +| MCu2.1 | support the SBR configuration 1 (SBR1) ATC? | MCu2
NOT Mcu2 | O.3
N/A | Q.2961.2 | Yes No
N/A | +| MCu2.2 | support the SBR configuration 2 or 3 like(SBR2/3-like) ATC (Note)? | MCu2
NOT Mcu2 | O.3
N/A | Q.2961.2 | Yes No
N/A | +| MCu2.3 | support the SBR configuration 2 (SBR2) ATC? | MCu2
NOT MCu2 | O.3
N/A | Q.2961.6 | Yes No
N/A | +| MCu2.4 | support the SBR configuration 3 (SBR3) ATC? | MCu2
NOT MCu2 | O.3
N/A | Q.2961.6 | Yes No
N/A | +| MCu3 | support the ABR ATC? | | O.2 | Q.2961.3 | Yes No | +| MCu4 | support the ABT ATC? | | O.2 | Q.2961.4 | Yes No | +| MCu4.1 | support the ABT with Immediate transmission (ABT-IT) ATC? | MCu4
NOT MCu4 | O.4
N/A | Q.2961.4 | Yes No
N/A | +| MCu4.2 | support the ABT with delayed transmission (ABT-DT) ATC? | MCu4
NOT MCu4 | O.4
N/A | Q.2961.4 | Yes No
N/A | +| MCu5 | support the CDVT indication? | | O.2 | Q.2961.5 | Yes No | +| O.2 The support of at least one of these items is mandatory. | | | | | | +| O.3 The support of at least one of these items is mandatory. | | | | | | +| O.4 The support of at least one of these items is mandatory. | | | | | | +| NOTE – The SBR2/3-like ATC identified in ITU-T Q.2961.2 are is different from SBR2 and SBR3 defined in ITU-T I.371 (see Note 14 to Table A.1/Q.2961.2, published in ITU-T Q.2961.2 Corrigendum 1), in that the Tagging traffic management option applies only locally and the request support applies separately to each direction of the connection. Further, the Broadband traffic capability field coding in the Broadband bearer capability information element are is different. A future version of the present standard will cover the SBR2 and SBR3 ATCs signalling support as specified in ITU-T Recommendation Q.2961.6. | | | | | | +| Comments: | | | | | | + +Modify Table A.3 "Subsidiary capabilities" of clause A.6.2 "Subsidiary capabilities": + +| Item | Subsidiary capability:
Does the implementation ... | Conditions
for status | Status | Reference | Support | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|--------------------------|----------|------------------------------|-------------------------| +| SCu1 | recognize additional Broadband bearer capability codepoints received, for backward compatibility with CBR (Note 1)? | MCu1
NOT MCu1 | O
N/A | 2.6.1
[Q.2961.2] | [ ]Yes [ ]No
[ ] N/A | +| SCu2 | recognize additional Broadband bearer capability codepoints received, for backward compatibility with VBR (Note 2)? | MCu2
NOT MCu1 | O
N/A | 2.6.1
[Q.2961.2] | [ ]Yes [ ]No
[ ] N/A | +| SCu3 | handle traffic management options for local support of tagging? | MCu2.2
NOT
MCu2.2 | O
N/A | 1.9.2
[Q.2961.1] | [ ]Yes [ ]No
[ ] N/A | +| SCu3.1 | send local tagging request in outgoing call request (Note 3)? | SCu3
NOT SCu3 | O
N/A | 1.9.2.1
[Q.2961.1] | [ ]Yes [ ]No
[ ] N/A | +| SCu3.2 | indicate local tagging not allowed (Note 4)? | SCu3
NOT SCu3 | O
N/A | 1.9.2.2
[Q.2961.1] | [ ]Yes [ ]No
[ ] N/A | +| NOTE 1 – Constant Bit Rate (with end-to-end timing required) information transfer capability as supported in the first edition of ITU-T Q.2931. | | | | | | +| NOTE 2 – Variable Bit Rate (with end-to-end timing required or not required) information transfer capability as supported in the first edition of ITU-T Q.2931. | | | | | | +| NOTE 3 – If local tagging is requested and indicated as being applied by the network, then an SBR configuration 3 (SBR3) is provided locally. Otherwise SBR configuration 2 (SBR2-like) service is provided with locally tagging. | | | | | | +| NOTE 4 – If local tagging is not allowed, then an SBR configuration 2 (SBR2-like) service is requested and shall apply locally. | | | | | | +| Comments: | | | | | | + +Modify Table A.8 "Major capabilities" of clause A.7.1 "Major capabilities": + +| Item | Major capability:
Does the implementation ... | Conditions
for status | Status | Reference | Support | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|--------------------------|--------------------|-----------------|------------------------------------------------------------------------------------------| +| MCn1 | support the DBR ATC? | | O.7 | Q.2961.2 | Yes No | +| MCn2 | support the SBR ATC? | | O.7 | Q.2961.2 | Yes No | +| MCn2.1 | support the SBR configuration 1 (SBR1) ATC? | MCn2
NOT MCn2 | O.8
N/A | Q.2961.2 | Yes No
N/A | +| MCn2.2 | support the SBR configuration 2 or 3 like (SBR2/3-like) ATC (Note)? | MCn2
NOT MCn2 | O.8
N/A | Q.2961.2 | Yes No
N/A | +| MCn2.3 | support the SBR configuration 2 (SBR2) ATC? | MCu2
NOT MCu2 | O.8
N/A | Q.2961.6 | Yes No
N/A | +| MCn2.4 | support the SBR configuration 3 (SBR3) ATC? | MCu2
NOT MCu2 | O.8
N/A | Q.2961.6 | Yes No
N/A | +| MCn3 | support the ABR ATC? | | O.7 | Q.2961.3 | Yes No | +| MCn4 | support the ABT ATC? | | O.7 | Q.2961.4 | Yes No | +| MCn4.1 | support the ABT with Immediate transmission (ABT-IT) ATC? | MCn4
NOT MCn4 | O.9
N/A | Q.2961.4 | Yes No
N/A | +| MCn4.2 | support the ABT with delayed transmission (ABT-DT) ATC? | MCn4
NOT MCn4 | O.9
N/A | Q.2961.4 | Yes No
N/A | +| MCn5 | support the CDVT indication? | | O.7 | Q.2961.5 | Yes No | +| O.7 The support of at least one of these items is mandatory. | | | | | | +| O.8 The support of at least one of these items is mandatory. | | | | | | +| O.9 The support of at least one of these items is mandatory. | | | | | | +| NOTE – The SBR2-like ATC identified in ITU-T Q.2961.2 are is different from SBR2 and SBR3 defined in ITU-T I.371 (see Note 14 to Table A.1/Q.2961.2, published in ITU-T Q.2961.2 Corrigendum 1), in that the Tagging traffic management option applies only locally and the request support applies separately to each direction of the connection. Further, the Broadband traffic capability field coding in the Broadband bearer capability information element are is different. A future version of the present standard will cover the SBR2 and SBR3 ATCs signalling support as specified in ITU-T Recommendation Q.2961.6. | | | | | | +| Comments: | | | | | | + +Modify Table A.9 "Subsidiary capabilities" of clause A.7.2 "Subsidiary capabilities": + +| Item | Subsidiary capability:
Does the implementation ... | Conditions
for status | Status | Reference | Support | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|--------------------------|----------|-----------------------|---------------------------| +| SCn1 | recognize additional Broadband bearer capability codepoints received, for backward compatibility with CBR (Note 1)? | MCn1
NOT MCn1 | O
N/A | 2.6.1
[Q.2961.2] | [ ] Yes [ ] No
[ ] N/A | +| SCn2 | recognize additional Broadband bearer capability codepoints received, for backward compatibility with VBR (Note 2)? | MCn2
NOT MCn1 | O
N/A | 2.6.1
[Q.2961.2] | [ ] Yes [ ] No
[ ] N/A | +| SCn3 | handle traffic management options for local support of tagging? | MCn2.2
NOT MCn2.2 | O
N/A | 1.9.2
[Q.2961.1] | [ ] Yes [ ] No
[ ] N/A | +| SCn3.1 | send local tagging supported in an incoming call indication (Note 3)? | SCn3
NOT SCn3 | O
N/A | 1.9.2.2
[Q.2961.1] | [ ] Yes [ ] No
[ ] N/A | +| SCn3.2 | indicate local tagging not supported (Note 4)? | SCn3
NOT SCn3 | O
N/A | 1.9.2.1
[Q.2961.1] | [ ] Yes [ ] No
[ ] N/A | +| NOTE 1 – Constant Bit Rate (with end-to-end timing required) information transfer capability as supported in the first edition of ITU-T Q.2931. | | | | | | +| NOTE 2 – Variable Bit Rate (with end-to-end timing required or not required) information transfer capability as supported in the first edition of ITU-T Q.2931. | | | | | | +| NOTE 3 – If local tagging is indicated as being supported by the network and the called user responds with tagging requested, then an SBR configuration 3 (SBR3) is provided locally. Otherwise SBR configuration 2 (SBR2-like) service is provided with shall apply locally tagging. | | | | | | +| NOTE 4 – If local tagging is indicated as not being supported, then an SBR configuration 2 (SBR2-like) service is provided locally. | | | | | | +| Comments: | | | | | | + +## 5.5 CDVT descriptor IE + +Add a new item to Table A.4 "Information elements in the CONNECT message received by the user" of clause A.6.4 "PDU parameters received by the user": + +| Item | CONNECT message received by the user:
Does the implementation support the ... | Conditions
for status | Status | Reference | Support | +|-------|----------------------------------------------------------------------------------|--------------------------|----------|---------------------|---------------------------| +| IERu6 | CDVT descriptor | MCu5
NOT MCu5 | M
N/A | 8.1.1
[Q.2961.5] | [ ] Yes [ ] No
[ ] N/A | + +Add a new item to Table A.5 "Information elements in the SETUP message received by the user" of clause A.6.4 "PDU parameters received by the user": + +| Item | SETUP message received by the user:
Does the implementation support the ... | Conditions for status | Status | Reference | Support | +|-------|--------------------------------------------------------------------------------|-----------------------|----------|---------------------|------------------------------------------------------------------------------------------| +| IERu7 | CDVT descriptor | MCu5
NOT MCu5 | M
N/A | 8.1.2
[Q.2961.5] | Yes No
N/A | + +Add a new item to Table A.6 "Information elements in the CONNECT message sent by the user" of clause A.6.5 "PDU parameters sent by the user": + +| Item | CONNECT message sent by the user:
Does the implementation support the ... | Conditions for status | Status | Reference | Support | +|-------|------------------------------------------------------------------------------|-----------------------|----------|---------------------|------------------------------------------------------------------------------------------| +| IETu6 | CDVT descriptor | MCu5
NOT MCu5 | O
N/A | 8.1.1
[Q.2961.5] | Yes No
N/A | + +Add a new item to Table A.7 "Information elements in the SETUP message sent by the user" of clause A.6.5 "PDU parameters sent by the user": + +| Item | SETUP message sent by the user:
Does the implementation support the ... | Conditions for status | Status | Reference | Support | +|-------|----------------------------------------------------------------------------|-----------------------|----------|---------------------|------------------------------------------------------------------------------------------| +| IETu7 | CDVT descriptor | MCu5
NOT MCu5 | O
N/A | 8.1.2
[Q.2961.5] | Yes No
N/A | + +Add a new item to Table A.10 "Information elements in the CONNECT message received by the network" of clause A.7.4 "PDU parameters received by the network": + +| Item | CONNECT message received by the network:
Does the implementation support the ... | Conditions for status | Status | Reference | Support | +|-------|-------------------------------------------------------------------------------------|-----------------------|----------|---------------------|------------------------------------------------------------------------------------------| +| IERn6 | CDVT descriptor | MCu5
NOT MCu5 | M
N/A | 8.1.1
[Q.2961.5] | Yes No
N/A | + +Add a new item to Table A.11 "Information elements in the SETUP message received by the network" of clause A.7.4 "PDU parameters received by the network": + +| Item | SETUP message received by the network:
Does the implementation support the ... | Conditions for status | Status | Reference | Support | +|-------|-----------------------------------------------------------------------------------|-----------------------|----------|---------------------|------------------------------------------------------------------------------------------| +| IERn7 | CDVT descriptor | MCu5
NOT MCu5 | M
N/A | 8.1.2
[Q.2961.5] | Yes No
N/A | + +Add a new item to Table A.12 "Information elements in the CONNECT message sent by the network" of clause A.7.5 "PDU parameters sent by the network": + +| Item | CONNECT message sent by the network:
Does the implementation support the ... | Conditions for status | Status | Reference | Support | +|-------|---------------------------------------------------------------------------------|-----------------------|----------|---------------------|------------------------------------------------------------------------------------------| +| IETn6 | CDVT descriptor | MCu5
NOT MCu5 | O
N/A | 8.1.1
[Q.2961.5] | Yes No
N/A | + +Add a new item to Table A.13 "Information elements in the SETUP message sent by the network" of clause A.7.5 "PDU parameters sent by the network": + +| Item | SETUP message sent by the network:
Does the implementation support the ... | Conditions for status | Status | Reference | Support | +|-------|-------------------------------------------------------------------------------|-----------------------|----------|---------------------|------------------------------------------------------------------------------------------| +| IETn7 | CDVT descriptor | MCu5
NOT MCu5 | O
N/A | 8.1.2
[Q.2961.5] | Yes No
N/A | + +## 5.6 Information elements contents for the user + +Add the following new clauses: + +### A.6.8 Structure of information elements received + +These tables are to be completed in order to evaluate the likelihood of successful interoperation of two implementations. + +#### A.6.8.1 ATM Traffic descriptor + +This clause defines a table containing additional codings to Table A.40 "ATM Traffic descriptor information element contents" of ITU-T Q.2931 B. If this PICS proforma is provided by the client together with Q.2931 B, items from IERu4.1 to IERu4.4 may be ignored in the table below. If they are filled in, it shall be identical to the content of Table A.40/Q.2931 B. + +**Table A.14/Q.2961 B – ATM Traffic descriptor information element contents** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|-----------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IERu 4.1 | Forward PCR (CLP = 0) | O | N/A | Yes No | +| IERu 4.2 | Backward PCR (CLP = 0) | O | N/A | Yes No | +| IERu 4.3 | Forward PCR (CLP = 0 + 1) | M | N/A | Yes No | +| IERu 4.4 | Backward PCR (CLP = 0 + 1) | M | N/A | Yes No | +| IERu 4.5 | Forward SCR (CLP = 0) (Note 1) | O | N/A | Yes No | +| IERu 4.6 | Backward SCR (CLP = 0) (Note 1) | O | N/A | Yes No | +| IERu 4.7 | Forward SCR (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IERu 4.8 | Backward SCR (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IERu 4.9 | Forward MBS (CLP = 0) (Note 1) | O | N/A | Yes No | +| IERu 4.10 | Backward MBS (CLP = 0) (Note 1) | O | N/A | Yes No | +| IERu 4.11 | Forward MBS (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IERu 4.12 | Backward MBS (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | + +**Table A.14/Q.2961 B – ATM Traffic descriptor information element contents (end)** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IERu 4.13 | Traffic management options (Note 2)
1. tagging not supported (tagging backward)
2. tagging supported (tagging backward)
3. tagging not applied (tagging forward)
4. tagging applied (tagging forward) | O
O
O
O
O |
0
1
0
1 | Yes No
Yes No
Yes No
Yes No
Yes No | +| IERu 4.14 | Forward ABR MCR (CLP = 0 + 1) (Note 3) | O | N/A | Yes No | +| IERu 4.15 | Backward ABR MCR (CLP = 0 + 1) (Note 3) | O | N/A | Yes No | +| IERu 4.16 | Forward RM PCR (Note 4) | O | N/A | Yes No | +| IERu 4.17 | Backward RM PCR (Note 4) | O | N/A | Yes No | +| NOTE 1 – Shall be supported if MCu2 is TRUE.
NOTE 2 – Shall be supported if SCu3 is TRUE.
NOTE 3 – Shall be supported if MCu3 is TRUE.
NOTE 4 – Shall be supported if MCu4 is TRUE. | | | | | +| Comments: | | | | | + +#### A.6.8.2 ABR setup parameters + +**Table A.15/Q.2961 B – ABR setup parameters information element contents** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|-----------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IERu 3.1 | Forward ABR ICR (CLP = 0 + 1) | M | N/A | Yes No | +| IERu 3.2 | Backward ABR ICR (CLP = 0 + 1) | M | N/A | Yes No | +| IERu 3.3 | Forward ABR TBE | M | N/A | Yes No | +| IERu 3.4 | Backward ABR TBE | M | N/A | Yes No | +| IERu 3.5 | Cumulative RM FRT | M | N/A | Yes No | +| IERu 3.6 | Forward RIF | M | N/A | Yes No | +| IERu 3.7 | Backward RIF | M | N/A | Yes No | +| IERu 3.8 | Forward RDF | M | N/A | Yes No | +| IERu 3.9 | Backward RDF | M | N/A | Yes No | +| Comments: | | | | | + +#### A.6.8.3 Broadband bearer capability + +**Table A.16/Q.2961 B – Broadband bearer capability information element contents** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|------------------------------------------------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IERu 16.1 | Bearer Class | M | | Yes No | +| | 1. BCOB-A | M | 1 | Yes No | +| | 2. BCOB-C | M | 3 | Yes No | +| | 3. FRBS | M | 5 | Yes No | +| | 4. BCOB-X | M | 16 | Yes No | +| IERu 16.2 | Broadband transfer capability | M | | Yes No | +| | 1. BTC5 | M | 5 | Yes No | +| | 2. DBR | M | 7 | Yes No | +| | 3. BTC9 | M | 9 | Yes No | +| | 4. BTC10 | M | 10 | Yes No | +| | 5. SBR1 with end-to-end timing not required | M | 11 | Yes No | +| | 6. SBR1 with end-to-end timing required | M | 19 | Yes No | +| | 7. BTC10 | M | 0 | Yes No | +| | 8. BTC9 | M | 1 | Yes No | +| | 10. BTC10 | M | 2 | Yes No | +| | 11. BTC5 | M | 4 | Yes No | +| | 12. BTC5 | M | 6 | Yes No | +| | 13. BTC10 | M | 8 | Yes No | +| | 14. ABT-DT (Note 1) | O | 16 | Yes No | +| | 15. ABT-IT (Note 1) | O | 17 | Yes No | +| | 16. SBR2 (Note 2) | O | 20 | Yes No | +| | 17. SBR3 (Note 3) | O | 21 | Yes No | +| IERu 16.3 | Susceptibility to clipping | M | | Yes No | +| | 1. not susceptible | M | 0 | Yes No | +| | 2. susceptible | M | 1 | Yes No | +| IERu 16.4 | User plane connection configuration | M | | Yes No | +| | 1. point-to-point | M | 0 | Yes No | +| | 2. point-to-multipoint | M | 1 | Yes No | +| IERu 16.5 | User information layer 2 protocol | M | | Yes No | +| | 1. Core aspects of Annex A/Q.922 | M | 15 | Yes No | +| NOTE 1 – Shall be supported if MCu4 is TRUE. | | | | | +| NOTE 2 – Shall be supported if MCu2.3 is TRUE. | | | | | +| NOTE 3 – Shall be supported if MCu2.4 is TRUE. | | | | | +| Comments: | | | | | + +#### A.6.8.4 CDVT descriptor + +**Table A.17/Q.2961 B – CDVT descriptor information element contents** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|-----------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IERu 6.1 | Forward $\tau_{PCR}$ (0 + 1) | M | N/A | Yes No | +| IERu 6.2 | Backward $\tau_{PCR}$ (0 + 1) | M | N/A | Yes No | +| IERu 6.1 | Forward $\tau_{SCR}$ (0) | M | N/A | Yes No | +| IERu 6.2 | Backward $\tau_{SCR}$ (0) | M | N/A | Yes No | +| IERu 6.1 | Forward $\tau_{SCR}$ (0 + 1) | M | N/A | Yes No | +| IERu 6.2 | Backward $\tau_{SCR}$ (0 + 1) | M | N/A | Yes No | +| IERu 6.1 | Forward $\tau_{PCR}$ (RM) | M | N/A | Yes No | +| IERu 6.2 | Backward $\tau_{PCR}$ (RM) | M | N/A | Yes No | +| Comments: | | | | | + +#### A.6.8.5 Minimum acceptable ABR traffic descriptor + +**Table A.18/Q.2961 B – Minimum acceptable ABR traffic descriptor information element contents** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|----------------------------------------------------------------------------------------------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IERu 5.1 | Forward ABR MCR (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IERu 5.2 | Backward ABR MCR (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IERu 5.3 | Forward SCR (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IERu 5.4 | Backward SCR (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IERu 5.5 | Forward MBS (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IERu 5.6 | Backward MBS (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IERu 5.7 | Forward RM PCR (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IERu 5.8 | Backward RM PCR (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| NOTE 1 – Shall be supported if MCu3 is TRUE.
NOTE 2 – Shall be supported if MCu4 is TRUE. | | | | | +| Comments: | | | | | + +### A.6.9 Structure of information elements sent + +These tables are to be completed in order to evaluate the likelihood of successful interoperation of two implementations. + +#### A.6.9.1 ATM Traffic descriptor + +This clause defines a table containing additional codings to Table A.40 "ATM Traffic descriptor information element contents" of ITU-T Q.2931 B. If this PICS proforma is provided by the client together with Q.2931 B, items from IETu4.1 to IETu4.4 may be ignored in the table below. If they are filled in, it shall be identical to the content of Table A.57/Q.2931 B. + +**Table A.19/Q.2961 B – ATM Traffic descriptor information element contents** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IETu 4.1 | Forward PCR (CLP = 0) | O | N/A | Yes No | +| IETu 4.2 | Backward PCR (CLP = 0) | O | N/A | Yes No | +| IETu 4.3 | Forward PCR (CLP = 0 + 1) | M | N/A | Yes No | +| IETu 4.4 | Backward PCR (CLP = 0 + 1) | M | N/A | Yes No | +| IETu 4.5 | Forward SCR (CLP = 0) (Note 1) | O | N/A | Yes No | +| IETu 4.6 | Backward SCR (CLP = 0) (Note 1) | O | N/A | Yes No | +| IETu 4.7 | Forward SCR (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IETu 4.8 | Backward SCR (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IETu 4.9 | Forward MBS (CLP = 0) (Note 1) | O | N/A | Yes No | +| IETu 4.10 | Backward MBS (CLP = 0) (Note 1) | O | N/A | Yes No | +| IETu 4.11 | Forward MBS (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IETu 4.12 | Backward MBS (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IETu 4.13 | Traffic management options (Note 2) | O | | Yes No | +| | 1. tagging not supported (tagging backward) | O | 0 | Yes No | +| | 2. tagging supported (tagging backward) | O | 1 | Yes No | +| | 3. tagging not applied (tagging forward) | O | 0 | Yes No | +| | 4. tagging applied (tagging forward) | O | 1 | Yes No | +| IETu 4.14 | Forward ABR MCR (CLP = 0 + 1) (Note 3) | O | N/A | Yes No | +| IETu 4.15 | Backward ABR MCR (CLP = 0 + 1) (Note 3) | O | N/A | Yes No | +| IETu 4.16 | Forward RM PCR (Note 4) | O | N/A | Yes No | +| IETu 4.17 | Backward RM PCR (Note 4) | O | N/A | Yes No | +| NOTE 1 – Shall be supported if MCu2 is TRUE.
NOTE 2 – Shall be supported if SCu3 is TRUE.
NOTE 3 – Shall be supported if MCu3 is TRUE.
NOTE 4 – Shall be supported if MCu4 is TRUE. | | | | | +| Comments: | | | | | + +#### A.6.9.2 ABR setup parameters + +**Table A.20/Q.2961 B – ABR setup parameters information element contents in the SETUP message** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|--------------------------------------------------------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IETu 3.1 | Forward ABR ICR (CLP = 0 + 1) (Note) | O | N/A | Yes No | +| IETu 3.2 | Backward ABR ICR (CLP = 0 + 1) (Note) | O | N/A | Yes No | +| IETu 3.3 | Forward ABR TBE (Note) | O | N/A | Yes No | +| IETu 3.4 | Backward ABR TBE (Note) | O | N/A | Yes No | +| IETu 3.5 | Cumulative RM FRT (Note) | O | N/A | Yes No | +| IETu 3.6 | Forward RIF (Note) | O | N/A | Yes No | +| IETu 3.7 | Backward RIF (Note) | O | N/A | Yes No | +| IETu 3.8 | Forward RDF (Note) | O | N/A | Yes No | +| IETu 3.9 | Backward RDF (Note) | O | N/A | Yes No | +| NOTE – This parameter is mandatory if R.1.1.2 is TRUE. | | | | | +| Comments: | | | | | + +**Table A.21/Q.2961 B – ABR setup parameters information element contents in the CONNECT message** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|-------------------------------------------------------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IETu 3.1 | Forward ABR ICR (CLP = 0 + 1) (Note) | M | N/A | Yes No | +| IETu 3.2 | Backward ABR ICR (CLP = 0 + 1) (Note) | M | N/A | Yes No | +| IETu 3.3 | Forward ABR TBE (Note) | M | N/A | Yes No | +| IETu 3.4 | Backward ABR TBE (Note) | M | N/A | Yes No | +| IETu 3.5 | Cumulative RM FRT (Note) | M | N/A | Yes No | +| IETu 3.6 | Forward RIF (Note) | M | N/A | Yes No | +| IETu 3.7 | Backward RIF (Note) | M | N/A | Yes No | +| IETu 3.8 | Forward RDF (Note) | M | N/A | Yes No | +| IETu 3.9 | Backward RDF (Note) | M | N/A | Yes No | +| NOTE – This parameter is mandatory when R2.2 is TRUE. | | | | | +| Comments: | | | | | + +#### A.6.9.3 Broadband bearer capability + +**Table A.22/Q.2961 B – Broadband bearer capability information element contents** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|------------------------------------------------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IETu 16.1 | Bearer Class | M | | Yes No | +| | 1. BCOB-A | O | 1 | Yes No | +| | 2. BCOB-C | O | 3 | Yes No | +| | 3. FRBS | O | 5 | Yes No | +| | 4. BCOB-X | O | 16 | Yes No | +| IETu 16.2 | Broadband transfer capability | O | | Yes No | +| | 1. BTC5 | O | 5 | Yes No | +| | 2. DBR | O | 7 | Yes No | +| | 3. BTC9 | O | 9 | Yes No | +| | 4. BTC10 | O | 10 | Yes No | +| | 5. SBR1 with end-to-end timing not required | O | 11 | Yes No | +| | 6. SBR1 with end-to-end timing required | O | 19 | Yes No | +| | 7. BTC10 | X | 0 | Yes No | +| | 8. BTC9 | X | 1 | Yes No | +| | 10. BTC10 | X | 2 | Yes No | +| | 11. BTC5 | X | 4 | Yes No | +| | 12. BTC5 | X | 6 | Yes No | +| | 13. BTC10 | X | 8 | Yes No | +| | 14. ABT-DT (Note 1) | O | 16 | Yes No | +| | 15. ABT-IT (Note 1) | O | 17 | Yes No | +| | 16. SBR2 (Note 2) | O | 20 | Yes No | +| | 17. SBR3 (Note 3) | O | 21 | Yes No | +| IETu 16.3 | Susceptibility to clipping | M | | Yes No | +| | 1. not susceptible | O | 0 | Yes No | +| | 2. susceptible | O | 1 | Yes No | +| IETu 16.4 | User plane connection configuration | M | | Yes No | +| | 1. point-to-point | O | 0 | Yes No | +| | 2. point-to-multipoint | O | 1 | Yes No | +| IETu 16.5 | User information layer 2 protocol | O | | Yes No | +| | 1. Core aspects of Annex A/Q.922 | M | 15 | Yes No | +| NOTE 1 – Shall be supported if MCu4 is TRUE. | | | | | +| NOTE 2 – Shall be supported if MCu2.3 is TRUE. | | | | | +| NOTE 3 – Shall be supported if MCu2.4 is TRUE. | | | | | +| Comments: | | | | | + +#### A.6.9.4 CDVT descriptor + +**Table A.23/Q.2961 B – CDVT descriptor information element contents** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|-----------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IETu 6.1 | Forward $\tau_{PCR}$ (0 + 1) | O | N/A | Yes No | +| IETu 6.2 | Backward $\tau_{PCR}$ (0 + 1) | O | N/A | Yes No | +| IETu 6.1 | Forward $\tau_{SCR}$ (0) | O | N/A | Yes No | +| IETu 6.2 | Backward $\tau_{SCR}$ (0) | O | N/A | Yes No | +| IETu 6.1 | Forward $\tau_{SCR}$ (0 + 1) | O | N/A | Yes No | +| IETu 6.2 | Backward $\tau_{SCR}$ (0 + 1) | O | N/A | Yes No | +| IETu 6.1 | Forward $\tau_{PCR}$ (RM) | O | N/A | Yes No | +| IETu 6.2 | Backward $\tau_{PCR}$ (RM) | O | N/A | Yes No | +| Comments: | | | | | + +#### A.6.9.5 Minimum acceptable ABR traffic descriptor + +**Table A.24/Q.2961 B – Minimum acceptable ABR traffic descriptor information element contents** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|----------------------------------------------------------------------------------------------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IETu 5.1 | Forward ABR MCR (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IETu 5.2 | Backward ABR MCR (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IETu 5.3 | Forward SCR (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IETu 5.4 | Backward SCR (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IETu 5.5 | Forward MBS (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IETu 5.6 | Backward MBS (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IETu 5.7 | Forward RM PCR (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IETu 5.8 | Backward RM PCR (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| NOTE 1 – This parameter is relevant to MCu3.
NOTE 2 – This parameter is relevant to MCu4. | | | | | +| Comments: | | | | | + +## 5.7 Information elements contents for the network + +Add the following new clauses: + +### A.7.8 Structure of information elements received + +These tables are to be completed in order to evaluate the likelihood of successful interoperation of two implementations. + +#### A.7.8.1 ATM Traffic descriptor + +This clause defines a table containing additional codings to Table A.110 "ATM Traffic descriptor information element contents" of ITU-T Q.2931 B. If this PICS proforma is provided by the client together with Q.2931 B, items from IERn4.1 to IERn4.4 may be ignored in the table below. If they are filled in, it shall be identical to the content of Table A.110/Q.2931 B. + +**Table A.25/Q.2961 B – ATM Traffic descriptor information element contents** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IERn 4.1 | Forward PCR (CLP = 0) | O | N/A | Yes No | +| IERn 4.2 | Backward PCR (CLP = 0) | O | N/A | Yes No | +| IERn 4.3 | Forward PCR (CLP = 0 + 1) | M | N/A | Yes No | +| IERn 4.4 | Backward PCR (CLP = 0 + 1) | M | N/A | Yes No | +| IERn 4.5 | Forward SCR (CLP = 0) (Note 1) | O | N/A | Yes No | +| IERn 4.6 | Backward SCR (CLP = 0) (Note 1) | O | N/A | Yes No | +| IERn 4.7 | Forward SCR (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IERn 4.8 | Backward SCR (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IERn 4.9 | Forward MBS (CLP = 0) (Note 1) | O | N/A | Yes No | +| IERn 4.10 | Backward MBS (CLP = 0) (Note 1) | O | N/A | Yes No | +| IERn 4.11 | Forward MBS (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IERn 4.12 | Backward MBS (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IERn 4.13 | Traffic management options (Note 2) | O | | Yes No | +| | 1. tagging not supported (tagging backward) | O | 0 | Yes No | +| | 2. tagging supported (tagging backward) | O | 1 | Yes No | +| | 3. tagging not applied (tagging forward) | O | 0 | Yes No | +| | 4. tagging applied (tagging forward) | O | 1 | Yes No | +| IERn 4.14 | Forward ABR MCR (CLP = 0 + 1) (Note 3) | O | N/A | Yes No | +| IERn 4.15 | Backward ABR MCR (CLP = 0 + 1) (Note 3) | O | N/A | Yes No | +| IERn 4.16 | Forward RM PCR (Note 4) | O | N/A | Yes No | +| IERn 4.17 | Backward RM PCR (Note 4) | O | N/A | Yes No | +| NOTE 1 – Shall be supported if MCn2 is TRUE.
NOTE 2 – Shall be supported if SCn3 is TRUE.
NOTE 3 – Shall be supported if MCn3 is TRUE.
NOTE 4 – Shall be supported if MCn4 is TRUE. | | | | | +| Comments: | | | | | + +#### A.7.8.2 ABR setup parameters + +**Table A.26/Q.2961 B – ABR setup parameters information element contents** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|-----------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IERn 3.1 | Forward ABR ICR (CLP = 0 + 1) | M | N/A | Yes No | +| IERn 3.2 | Backward ABR ICR (CLP = 0 + 1) | M | N/A | Yes No | +| IERn 3.3 | Forward ABR TBE | M | N/A | Yes No | +| IERn 3.4 | Backward ABR TBE | M | N/A | Yes No | +| IERn 3.5 | Cumulative RM FRT | M | N/A | Yes No | +| IERn 3.6 | Forward RIF | M | N/A | Yes No | +| IERn 3.7 | Backward RIF | M | N/A | Yes No | +| IERn 3.8 | Forward RDF | M | N/A | Yes No | +| IERn 3.9 | Backward RDF | M | N/A | Yes No | +| Comments: | | | | | + +#### A.7.8.3 Broadband bearer capability + +**Table A.27/Q.2961 B – Broadband bearer capability information element contents** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|-----------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IERn 16.1 | Bearer Class | M | | Yes No | +| | 1. BCOB-A | M | 1 | Yes No | +| | 2. BCOB-C | M | 3 | Yes No | +| | 3. FRBS | M | 5 | Yes No | +| | 4. BCOB-X | M | 16 | Yes No | +| IERn 16.2 | Broadband transfer capability | M | | Yes No | +| | 1. BTC5 | M | 5 | Yes No | +| | 2. DBR | M | 7 | Yes No | +| | 3. BTC9 | M | 9 | Yes No | +| | 4. BTC10 | M | 10 | Yes No | +| | 5. SBR1 with end-to-end timing not required | M | 11 | Yes No | +| | 6. SBR1 with end-to-end timing required | M | 19 | Yes No | +| | 7. BTC10 | M | 0 | Yes No | +| | 8. BTC9 | M | 1 | Yes No | +| | 10. BTC10 | M | 2 | Yes No | +| | 11. BTC5 | M | 4 | Yes No | +| | 12. BTC5 | M | 6 | Yes No | +| | 13. BTC10 | M | 8 | Yes No | +| | 14. ABT-DT (Note 1) | O | 16 | Yes No | +| | 15. ABT-IT (Note 1) | O | 17 | Yes No | +| | 16. SBR2 (Note 2) | O | 20 | Yes No | +| | 17. SBR3 (Note 3) | O | 21 | Yes No | + +**Table A.27/Q.2961 B – Broadband bearer capability information element contents (end)** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|--------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IERn 16.3 | Susceptibility to clipping | M | | Yes No | +| | 1. not susceptible | M | 0 | Yes No | +| | 2. susceptible | M | 1 | Yes No | +| IERn 16.4 | User plane connection configuration | M | | Yes No | +| | 1. point-to-point | M | 0 | Yes No | +| | 2. point-to-multipoint | M | 1 | Yes No | +| IERn 16.5 | User information layer 2 protocol | M | | Yes No | +| | 1. Core aspects of Annex A/Q.922 | M | 15 | Yes No | +| NOTE 1 – Shall be supported if MCn4 is TRUE.
NOTE 2 – Shall be supported if MCn2.3 is TRUE.
NOTE 3 – Shall be supported if MCn2.4 is TRUE. | | | | | +| Comments:

| | | | | + +#### A.7.8.4 CDVT descriptor + +**Table A.28/Q.2961 B – CDVT descriptor information element contents** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|-------------------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IERn 6.1 | Forward $\tau_{PCR}$ (0 + 1) | M | N/A | Yes No | +| IERn 6.2 | Backward $\tau_{PCR}$ (0 + 1) | M | N/A | Yes No | +| IERn 6.1 | Forward $\tau_{SCR}$ (0) | M | N/A | Yes No | +| IERn 6.2 | Backward $\tau_{SCR}$ (0) | M | N/A | Yes No | +| IERn 6.1 | Forward $\tau_{SCR}$ (0 + 1) | M | N/A | Yes No | +| IERn 6.2 | Backward $\tau_{SCR}$ (0 + 1) | M | N/A | Yes No | +| IERn 6.1 | Forward $\tau_{PCR}$ (RM) | M | N/A | Yes No | +| IERn 6.2 | Backward $\tau_{PCR}$ (RM) | M | N/A | Yes No | +| Comments:

| | | | | + +#### A.7.8.5 Minimum acceptable ABR traffic descriptor + +**Table A.29/Q.2961 B – Minimum acceptable ABR traffic descriptor information element contents** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|----------------------------------------------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IERn 5.1 | Forward ABR MCR (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IERn 5.2 | Backward ABR MCR (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IERn 5.3 | Forward SCR (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IERn 5.4 | Backward SCR (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IERn 5.5 | Forward MBS (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IERn 5.6 | Backward MBS (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IERn 5.7 | Forward RM PCR (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IERn 5.8 | Backward RM PCR (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| NOTE 1 – Shall be supported if MCn3 is TRUE. | | | | | +| NOTE 2 – Shall be supported if MCn4 is TRUE. | | | | | +| Comments: | | | | | + +### A.7.9 Structure of information elements sent + +These tables are to be completed in order to evaluate the likelihood of successful interoperation of two implementations. + +#### A.7.9.1 ATM Traffic descriptor + +This clause defines a table containing additional codings to Table A.128 "ATM Traffic descriptor information element contents" of ITU-T Q.2931 B. If this PICS proforma is provided by the client together with Q.2931 B, items from IETn4.1 to IETn4.4 may be ignored in the table below. If they are filled in, it shall be identical to the content of Table A.128/Q.2931 B. + +**Table A.30/Q.2961 B – ATM Traffic descriptor information element contents** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|-----------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IETn 4.1 | Forward PCR (CLP = 0) | O | N/A | Yes No | +| IETn 4.2 | Backward PCR (CLP = 0) | O | N/A | Yes No | +| IETn 4.3 | Forward PCR (CLP = 0 + 1) | M | N/A | Yes No | +| IETn 4.4 | Backward PCR (CLP = 0 + 1) | M | N/A | Yes No | +| IETn 4.5 | Forward SCR (CLP = 0) (Note 1) | O | N/A | Yes No | +| IETn 4.6 | Backward SCR (CLP = 0) (Note 1) | O | N/A | Yes No | +| IETn 4.7 | Forward SCR (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IETn 4.8 | Backward SCR (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IETn 4.9 | Forward MBS (CLP = 0) (Note 1) | O | N/A | Yes No | +| IETn 4.10 | Backward MBS (CLP = 0) (Note 1) | O | N/A | Yes No | + +**Table A.30/Q.2961 B – ATM Traffic descriptor information element contents (end)** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IETn 4.11 | Forward MBS (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IETn 4.12 | Backward MBS (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IETn 4.13 | Traffic management options (Note 2)
1. tagging not supported (tagging backward)
2. tagging supported (tagging backward)
3. tagging not applied (tagging forward)
4. tagging applied (tagging forward) | O
O
O
O
O |
0
1
0
1 | Yes No
Yes No
Yes No
Yes No
Yes No | +| IETn 4.14 | Forward ABR MCR (CLP = 0 + 1) (Note 3) | O | N/A | Yes No | +| IETn 4.15 | Backward ABR MCR (CLP = 0 + 1) (Note 3) | O | N/A | Yes No | +| IETn 4.16 | Forward RM PCR (Note 4) | O | N/A | Yes No | +| IETn 4.17 | Backward RM PCR (Note 4) | O | N/A | Yes No | +| NOTE 1 – Shall be supported if MCn2 is TRUE.
NOTE 2 – Shall be supported if SCn3 is TRUE.
NOTE 3 – Shall be supported if MCn3 is TRUE.
NOTE 4 – Shall be supported if MCn4 is TRUE. | | | | | +| Comments: | | | | | + +#### A.7.9.2 ABR setup parameters + +**Table A.31/Q.2961 B – ABR setup parameters information element contents in the CONNECT message** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|-----------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IETn 3.1 | Forward ABR ICR (CLP = 0 + 1) | M | N/A | Yes No | +| IETn 3.2 | Backward ABR ICR (CLP = 0 + 1) | M | N/A | Yes No | +| IETn 3.3 | Forward ABR TBE | M | N/A | Yes No | +| IETn 3.4 | Backward ABR TBE | M | N/A | Yes No | +| IETn 3.5 | Cumulative RM FRT | M | N/A | Yes No | +| IETn 3.6 | Forward RIF | M | N/A | Yes No | +| IETn 3.7 | Backward RIF | M | N/A | Yes No | +| IETn 3.8 | Forward RDF | M | N/A | Yes No | +| IETn 3.9 | Backward RDF | M | N/A | Yes No | +| Comments: | | | | | + +#### A.7.9.3 Broadband bearer capability + +**Table A.32/Q.2961 B – Broadband bearer capability information element contents** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|------------------------------------------------|----------------------------------------------------------------|--------|----------|----------------------------------| +| IETn 16.1 | Bearer Class | M | | [ ] Yes [ ] No | +| | 1. BCOB-A | O | 1 | [ ] Yes [ ] No | +| | 2. BCOB-C | O | 3 | [ ] Yes [ ] No | +| | 3. FRBS | O | 5 | [ ] Yes [ ] No | +| | 4. BCOB-X | O | 16 | [ ] Yes [ ] No | +| IETn 16.2 | Broadband transfer capability | O | | [ ] Yes [ ] No | +| | 1. BTC5 | O | 5 | [ ] Yes [ ] No | +| | 2. DBR | O | 7 | [ ] Yes [ ] No | +| | 3. BTC9 | O | 9 | [ ] Yes [ ] No | +| | 4. BTC10 | O | 10 | [ ] Yes [ ] No | +| | 5. SBR1 with end-to-end timing not required | O
O | 11
19 | [ ] Yes [ ] No
[ ] Yes [ ] No | +| | 6. SBR1 with end-to-end timing required | X | 0 | [ ] Yes [ ] No | +| | 7. BTC10 | X | 1 | [ ] Yes [ ] No | +| | 8. BTC9 | X | 2 | [ ] Yes [ ] No | +| | 10. BTC10 | X | 4 | [ ] Yes [ ] No | +| | 11. BTC5 | X | 6 | [ ] Yes [ ] No | +| | 12. BTC5 | X | 8 | [ ] Yes [ ] No | +| | 13. BTC10 | O | 16 | [ ] Yes [ ] No | +| | 14. ABT-DT (Note 1) | O | 17 | [ ] Yes [ ] No | +| | 15. ABT-IT (Note 1) | O | 20 | [ ] Yes [ ] No | +| | 16. SBR2 (Note 2) | O | 21 | [ ] Yes [ ] No | +| | 17. SBR3 (Note 3) | O | | [ ] Yes [ ] No | +| IETn 16.3 | Susceptibility to clipping | M | | [ ] Yes [ ] No | +| | 1. not susceptible | O | 0 | [ ] Yes [ ] No | +| | 2. susceptible | O | 1 | [ ] Yes [ ] No | +| IETn 16.4 | User plane connection configuration | M | | [ ] Yes [ ] No | +| | 1. point-to-point | O | 0 | [ ] Yes [ ] No | +| | 2. point-to-multipoint | O | 1 | [ ] Yes [ ] No | +| IETn 16.5 | User information layer 2 protocol | O | | [ ] Yes [ ] No | +| | 1. Core aspects of Annex A/Q.922 | M | 15 | [ ] Yes [ ] No | +| NOTE 1 – Shall be supported if MCn4 is TRUE. | | | | | +| NOTE 2 – Shall be supported if MCn2.3 is TRUE. | | | | | +| NOTE 3 – Shall be supported if MCn2.4 is TRUE. | | | | | +| Comments:

| | | | | + +#### A.7.9.4 CDVT descriptor + +**Table A.33/Q.2961 B – CDVT descriptor information element contents** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|-----------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IETn 6.1 | Forward $\tau_{PCR}$ (0 + 1) | O | N/A | Yes No | +| IETn 6.2 | Backward $\tau_{PCR}$ (0 + 1) | O | N/A | Yes No | +| IETn 6.1 | Forward $\tau_{SCR}$ (0) | O | N/A | Yes No | +| IETn 6.2 | Backward $\tau_{SCR}$ (0) | O | N/A | Yes No | +| IETn 6.1 | Forward $\tau_{SCR}$ (0 + 1) | O | N/A | Yes No | +| IETn 6.2 | Backward $\tau_{SCR}$ (0 + 1) | O | N/A | Yes No | +| IETn 6.1 | Forward $\tau_{PCR}$ (RM) | O | N/A | Yes No | +| IETn 6.2 | Backward $\tau_{PCR}$ (RM) | O | N/A | Yes No | +| Comments: | | | | | + +#### A.7.9.5 Minimum acceptable ABR traffic descriptor + +**Table A.34/Q.2961 B – Minimum acceptable ABR traffic descriptor information element contents** + +| Item | Does the implementation support the information element field: | Status | Value | Support | +|----------------------------------------------|----------------------------------------------------------------|--------|-------|----------------------------------------------------------| +| IETn 5.1 | Forward ABR MCR (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IETn 5.2 | Backward ABR MCR (CLP = 0 + 1) (Note 1) | O | N/A | Yes No | +| IETn 5.3 | Forward SCR (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IETn 5.4 | Backward SCR (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IETn 5.5 | Forward MBS (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IETn 5.6 | Backward MBS (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IETn 5.7 | Forward RM PCR (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| IETn 5.8 | Backward RM PCR (CLP = 0 + 1) (Note 2) | O | N/A | Yes No | +| NOTE 1 – This parameter is relevant to MCn3. | | | | | +| NOTE 2 – This parameter is relevant to MCn4. | | | | | +| Comments: | | | | | + +# APPENDIX I + +## Bibliography + +- [A] ETSI EN 300 443-1 V1.3.5 (1998), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; B-ISDN user-network interface layer 3 specification for basic call/bearer control; Part 1: Protocol specification.* +- [B] ETSI EN 301 068-1 V1.2.4 (1998), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; ATM transfer capability and traffic parameter indication; Part 1: Protocol specification.* +- [C] ETSI EN 301 068-3 V1.1.2 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; ATM transfer capability and traffic parameter indication; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user.* +- [D] ETSI EN 301 068-4 V1.1.1 (1999), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; ATM transfer capability and traffic parameter indication; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the user.* +- [E] ETSI EN 301 068-5 V1.1.2 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; ATM transfer capability and traffic parameter indication; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network.* +- [F] ETSI EN 301 068-6 V1.1.1 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; ATM transfer capability and traffic parameter indication; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network.* +- [G] ITU-T I.371 (2000), *Traffic control and congestion control in B-ISDN.* +- [H] ITU-T Q.2931 (1995), *Digital subscriber signalling system No. 2 (DSS2) – User-network interface (UNI) layer 3 specification for basic call/connection control.* +- [I] ITU-T Q.2931 B (2000), *Broadband Integrated Services Digital Network (B-ISDN) – Digital subscriber signalling system No. 2 (DSS2) – User-network interface (UNI) layer 3 specification for basic call/connection control: Protocol implementation conformance statement (PICS) proforma.* + +## **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/Q/T-REC-Q.2963.1C-200012-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2963.1C-200012-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..091554dd4717b90c91ea43f5448aeac12348b9f2 --- /dev/null +++ b/marked/Q/T-REC-Q.2963.1C-200012-I_PDF-E/raw.md @@ -0,0 +1,230 @@ + + +![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** + +**Q.2963.1 C** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(12/2000) + +SERIES Q: SWITCHING AND SIGNALLING + +Broadband ISDN – B-ISDN application protocols for +access signalling + +--- + +**Digital subscriber signalling system No. 2 – +Connection modification: Peak cell rate +modification by the connection owner: Test +suite structure and test purposes (TSS & TP) for +the user** + +ITU-T Recommendation Q.2963.1 C + +(Formerly CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +## SWITCHING AND SIGNALLING + +| | | +|-----------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| B-ISDN application protocols for access signalling | Q.2900-Q.2999 | + +For further details, please refer to the list of ITU-T Recommendations. + +## **Digital subscriber signalling system No. 2 – Connection modification: Peak cell rate modification by the connection owner: Test suite structure and test purposes (TSS & TP) for the user** + +## **Summary** + +This Recommendation specifies the Test Suite Structure and Test Purposes (TSS & TP) for the user attached to the TB reference point or coincident SB and TB reference point (as defined in ITU-T I.413 [1]) of implementations conforming to the procedures for the modification of the peak cell rate traffic parameter by the connection owner in the active phase of the call of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the Broadband Integrated Services Digital Network (B-ISDN), ITU-T Q.2963.1 [3]. + +Other Recommendations of the Q.2963.1 family specify the Protocol Implementation Conformance Statement (PICS) proforma and Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on this Recommendation. + +NOTE – This Recommendation related to protocol conformance is published only in English; it is based on an external SDO's standard published in English. + +###### **Source** + +ITU-T Recommendation Q.2963.1 C was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 6 December 2000. + +## 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 | Endorsement..... | 2 | +| 4 | Coverage ..... | 2 | +| 5 | Modifications ..... | 2 | +| | Appendix I – Bibliography ..... | 2 | + +## **Digital subscriber signalling system No. 2 – Connection modification: Peak cell rate modification by the connection owner: Test suite structure and test purposes (TSS & TP) for the user** + +## 1 Scope + +This Recommendation specifies the Test Suite Structure and Test Purposes (TSS & TP) for the user attached to the TB reference point or coincident SB and TB reference point (as defined in ITU-T I.413 [1]) of implementations conforming to the procedures for the modification of the peak cell rate traffic parameter by the connection owner in the active phase of the call of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the Broadband Integrated Services Digital Network (B-ISDN), ITU-T Q.2963.1 [3]. + +Other Recommendations of the Q.2963.1 family specify the Protocol Implementation Conformance Statement (PICS) proforma and Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on this Recommendation. + +This Recommendation is applicable to equipment, supporting the modification of the peak cell rate traffic parameters of the connection in the active phase of the call by the connection owner, to be attached at either side of a TB reference point or coincident SB and TB reference point when used as an access to the public B-ISDN. + +The test suite structure provides the grouping of tests in the test suite, the test purposes part is a list of test purposes realized in the ATS part of the Recommendation. Test purposes are generated from the protocol specification, refer to observable events only but give no guarantee that each test purpose defined is testable. Untestable test purposes are identified in the ATS part. + +## 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; 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 currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T I.413 (1993), *B-ISDN user-network interface*. +- [2] ITU-T Q.2931 (1995), *Digital subscriber signalling system No. 2 (DSS2) – User-network interface (UNI) layer 3 specification for basic call/connection control*. +- [3] ITU-T Q.2963.1 (1999), *Digital subscriber signalling system No. 2 – Connection modification: Peak cell rate modification by the connection owner*. +- [4] ITU-T Q.2963.1 B (2000), *Digital subscriber signalling system No. 2 – Connection modification: peak cell rate modification by the connection owner: Protocol implementation conformance statement (PICS) proforma*. +- [5] ETSI EN 301 003-3 V1.2.1 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Peak cell rate modification by the connection owner; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user*. + +## 3 Endorsement + +The text of ETSI EN 301 003-3 [5] was approved by ITU-T as Recommendation Q.2963.1 C with agreed modifications as given below. + +NOTE – Underlining and/or strike-out is used to highlight new or deleted text where detailed indication of modifications is necessary. + +## 4 Coverage + +This Recommendation covers ITU-T Q.2963.1 [3]. + +## 5 Modifications + +Throughout the text of ETSI EN 301 003-3 [5] replace references and text as shown in the following table: + +| Reference in ETSI EN 301 003-3 | Modified reference | +|--------------------------------|---------------------------------| +| EN 301 003 | Q.2963.1-series Recommendations | +| EN 301 003-1 | ITU-T Q.2963.1 | +| EN 300 443-1 | ITU-T Q.2931 | +| EN 301 003-2 | ITU-T Q.2963.1 B | +| Standard | Recommendation | + +### Page 4, Intellectual Property Rights + +Delete the whole section. + +### Page 4, Foreword + +Delete the whole Foreword. + +NOTE 1 – It is replaced by the Foreword of this Recommendation. + +### Page 5, Clause 1 Scope + +Replace the whole clause with the following: + +### "1 Scope + +See clause 1 Scope of this Recommendation above." + +### Page 18, Bibliography + +Delete the whole clause "Bibliography". + +NOTE 2 – It is replaced by Appendix I "Bibliography" of this Recommendation. + +### Page 19, History + +Delete the whole clause "History". + +## APPENDIX I + +### Bibliography + +- [A] ETSI EN 300 443-1 V1.3.5 (1998), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; B-ISDN user-* + +*network interface layer 3 specification for basic call/bearer control; Part 1: Protocol specification.* + +- [B] ETSI EN 301 003-1 V1.1.3 (1999), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Peak cell rate modification by the connection owner; Part 1: Protocol specification.* +- [C] ETSI EN 301 003-2 V1.1.3 (1999), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Peak cell rate modification by the connection owner; Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification.* +- [D] ETSI EN 301 003-4 V1.2.1 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Peak cell rate modification by the connection owner; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the user.* +- [E] ETSI EN 301 003-5 V1.2.1(2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Peak cell rate modification by the connection owner; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network.* +- [F] ETSI EN 301 003-6 V1.2.1 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Peak cell rate modification by the connection owner; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network.* +- [G] ISO/IEC 9646-3: 1998, *Information technology – Open Systems Interconnection – Conformance testing methodology and framework – Part 3: The Tree and Tabular Combined Notation (TTCN).* + +### 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/Q/T-REC-Q.3404-201608-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3404-201608-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..020d638fb3f6a2f0d231756215ee0cb6992bef63 --- /dev/null +++ b/marked/Q/T-REC-Q.3404-201608-I_PDF-E/raw.md @@ -0,0 +1,413 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3404** + +(08/2016) + +SERIES Q: SWITCHING AND SIGNALLING + +Signalling requirements and protocols for the NGN – +Service and session control protocols + +--- + +**Signalling requirements for NGN real-time +multimedia services supporting IPv6 transition** + +Recommendation ITU-T Q.3404 + +# ITU-T Q-SERIES RECOMMENDATIONS + +## **SWITCHING AND SIGNALLING** + +| | | +|---------------------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 | +| General | Q.3000–Q.3029 | +| Network signalling and control functional architecture | Q.3030–Q.3099 | +| Network data organization within the NGN | Q.3100–Q.3129 | +| Bearer control signalling | Q.3130–Q.3179 | +| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 | +| Resource control protocols | Q.3300–Q.3369 | +| Service and session control protocols | Q.3400–Q.3499 | +| Service and session control protocols – supplementary services | Q.3600–Q.3616 | +| Service and session control protocols – supplementary services based on SIP-IMS | Q.3617–Q.3639 | +| NGN applications | Q.3700–Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 | +| TESTING SPECIFICATIONS | Q.3900–Q.4099 | + +For further details, please refer to the list of ITU-T Recommendations. + +## Recommendation ITU-T Q.3404 + +## Signalling requirements for NGN real-time multimedia services supporting IPv6 transition + +## Summary + +Recommendation ITU-T Q.3404 describes the IPv6 transition technologies which could be applied in a next generation network (NGN) environment. The signalling requirements supporting NGN real-time multimedia services in Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6) mixed network are specified. Three mechanisms for IPv6 transition are introduced in this Recommendation including dual stack, translation and tunnelling. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.3404 | 2016-08-29 | 11 | 11.1002/1000/12987 | + +## Keywords + +IPv6, multimedia services, NGN. + +--- + +\* 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 2016 + +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 | Architecture for NGN multimedia services supporting IPv6 transition ..... | 2 | +| 7 | Signalling requirements for dual stack ..... | 3 | +| 8 | Signalling requirements for translation ..... | 3 | +| 8.1 | General requirements..... | 3 | +| 8.2 | Scenario 1: UE using IPv6 and NGN core using IPv4..... | 4 | +| 8.3 | Scenario 2: UE using IPv4 and NGN core using IPv6..... | 4 | +| 8.4 | Scenario 3: NGN core using IPv6 and other IP-based network using IPv4 ... | 5 | +| 8.5 | Scenario 4: NGN core using IPv4 and other IP-based networks using IPv6 . | 6 | +| 9 | Signalling requirements for tunnelling ..... | 7 | +| 9.1 | Overviews..... | 7 | +| 9.2 | Scenario1: 4over6 tunnel connecting IPv4 NGN core networks..... | 7 | +| 9.3 | Scenario 2: 6over4 tunnel connection IPv6 NGN core networks..... | 8 | + + + +## Recommendation ITU-T Q.3404 + +## Signalling requirements for NGN real-time multimedia services supporting IPv6 transition + +# 1 Scope + +This Recommendation describes the IPv6 transition technologies which could be applied in a next generation network (NGN) environment. The signalling requirements supporting NGN real-time multimedia services in Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6) mixed network are specified. Three mechanisms for IPv6 transition are described in this Recommendation including dual stack, translation and tunnelling. The security issues introduced by IPv6 transition is out of 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 Y.2011] Recommendation ITU-T Y.2011 (2004), *General principles and general reference model for Next Generation Networks*. +- [ITU-T Y.2012] Recommendation ITU-T Y.2012 (2010), *Functional requirements and architecture of next generation networks*. +- [ITU-T Y.2701] Recommendation ITU-T Y.2701 (2007), *Security requirements for NGN release 1*. +- [IETF RFC 5565] IETF RFC 5565 (2009), *Softwire Mesh Framework*. +- [IETF RFC 5747] IETF RFC 5747 (2010), *4over6 Transit Solution Using IP Encapsulation and MP-BGP Extensions*. +- [IETF RFC 5969] IETF RFC 5969 (2010), *IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 NGN service stratum** [ITU-T Y.2011]: That part of the NGN which provides the user functions that transfer service-related data and the functions that control and manage service resources and network services to enable user services and applications. + +**3.1.2 NGN transport stratum** [ITU-T Y.2011]: That part of the NGN which provides the user functions that transfer data and the functions that control and manage transport resources to carry such data between terminating entities. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|----------|----------------------------------------------------------| +| ABG-FE | Access Border Gateway Functional Entity | +| ALG | Application Level Gateway | +| IBC-FE | Interconnection Border Gateway Control Functional Entity | +| IBG-FE | Interconnection Border Gateway Functional Entity | +| IP | Internet Protocol | +| ISDN | Integrated Services Digital Network | +| NACF | Network Attachment Control Functions | +| NAT | Network Address Translation | +| NAT-PT | Network Address Translation Protocol Translation | +| NNI | Network to Network Interface | +| NSIW-FE | Network Signalling Interworking Functional Entity | +| P-CSC-FE | Proxy Call Session Control Functional Entity | +| PSTN | Public Switched Telephone Network | +| RACF | Resource and Admission Control Functions | +| S-CSC-FE | Serving Call Session Control Functional Entity | +| SCTP | Stream Control Transmission Protocol | +| SDP | Session Description Protocol | +| SIP | Session Initiation Protocol | +| TCP | Transmission Control Protocol | +| UDP | User Datagram Protocol | +| UE | User Equipment | +| UNI | User to Network Interface | + +# 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 may optionally provide the feature and still claim conformance with this Recommendation. + +# 6 Architecture for NGN multimedia services supporting IPv6 transition + +The architecture of NGN multimedia services supporting IPv6 transition is depicted in Figure 6-1. + +![Diagram of NGN core architecture showing Service and Transport strata connected to various networks via UNI and NNI interfaces.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +The diagram illustrates the architecture for NGN multimedia services supporting IPv6 transition. At the center is a box labeled 'NGN core', which contains two stacked rectangular blocks: a blue 'Service Stratum' on top and a yellow 'Transport Stratum' on the bottom. To the left of the NGN core, three red shapes represent external entities: 'Terminal Equipment' (a rectangle), 'User networks' (a cloud), and 'Corporate networks' (a cloud). These are connected to the NGN core through a vertical dashed line labeled 'UNI' (User Network Interface). To the right of the NGN core, two red cloud shapes represent 'Other IP-based Networks' and 'Other NGNs'. These are connected to the NGN core through a vertical dashed line labeled 'NNI' (Network Network Interface). The connections are as follows: 'Terminal Equipment' connects to the Service Stratum; 'User networks' and 'Corporate networks' connect to the Transport Stratum; 'Other IP-based Networks' connect to the Service Stratum; and 'Other NGNs' connect to the Transport Stratum. + +Diagram of NGN core architecture showing Service and Transport strata connected to various networks via UNI and NNI interfaces. + +**Figure 6-1 – Architecture for NGN multimedia services supporting IPv6 transition** + +In order to reduce the interworking complexity, all functional entities in the NGN core network (e.g., proxy call session control functional entity (P-CSC-FE), serving call session control functional entity (S-CSC-FE), access border gateway functional entity (ABG-FE)) should use the same version of internet protocol as far as possible. Accordingly, IP protocol transition is only required on user to network interface (UNI) and network to network interface (NNI) within both control plane and media plane in NGN service stratum and NGN transport stratum. Three IPv6 transition mechanisms are introduced in this Recommendation to support NGN real-time multimedia services, including dual stack, translation and tunnelling as specified in clause 7, clause 8 and clause 9 respectively. + +# 7 Signalling requirements for dual stack + +In order to support dual stack transition, all functional entities inside an NGN core network are required to support IPv4 and IPv6 simultaneously. At the edge of an NGN core network, the functional entities connected to user equipment (UEs) or other IP-based networks should have the capability to adapt the same IP version as that which is used by the connected entities (UEs and/or other IP-based networks) both at the signalling level and media level. + +# 8 Signalling requirements for translation + +## 8.1 General requirements + +Network address translation (NAT)/network address translation protocol translation (NAT-PT) functions are required to be processed in the border of the IPv4 and IPv6 network for translation transition. The IPv4 address of the traffic from the IPv4 network to the IPv6 network shall be translated into IPv6 address in the border gateway, and vice versa. As an interconnecting node, the border gateway shall support dual stack. + +The border gateway shall also implement application level gateway (ALG) function which provides the application level translation for specific protocols (e.g., session initiation protocol (SIP) and session description protocol (SDP)). + +The border gateway shall be located in the border of networks using different protocols. Referring to NGN architecture defined in [ITU-T Y.2012], the functions of border gateway could be implemented in ABG-FE, interconnection border gateway functional entity (IBG-FE), P-CSC-FE and interconnection border gateway control functional entity (IBC-FE). + +Considering IPv6 transition using translation mechanism, there are four specific scenarios: + +- 1) Scenario 1: UE using IPv6 and NGN core using IPv4; +- 2) Scenario 2: UE using IPv4 and NGN core using IPv6; +- 3) Scenario 3: NGN core using IPv6 and other IP-based network using IPv4; +- 4) Scenario 4: NGN core using IPv4 and other IP-based network using IPv6. + +### 8.2 Scenario 1: UE using IPv6 and NGN core using IPv4 + +![Diagram of Scenario 1: UE using IPv6 and NGN core using IPv4](e6df2733626a85205c1db682e6259c46_img.jpg) + +The diagram shows an IPv6-UE (pink box) connected to a Border gateway (dashed box). Inside the Border gateway, there are three stacked components: P-CSC-FE (green box), RACF/NACF (yellow box), and ABG-FE (yellow box). The Border gateway is connected to an IPv4-NGN core (cloud shape). The label 'Q.3404(16)\_F8-1' is at the bottom right. + +Diagram of Scenario 1: UE using IPv6 and NGN core using IPv4 + +**Figure 8-1 – Scenario 1: UE using IPv6 and NGN core using IPv4** + +In the scenario of "UE using IPv6 and NGN core using IPv4" shown in Figure 8-1, P-CSC-FE and ABG-FE act as a border gateway within the control plane and the user plane (media plane) respectively. + +P-CSC-FE implements ALG function which provides the application level translation for SIP and SDP. It requests address mapping information based on the address binding information provided by the resource and admission control functions (RACF), and then modifies the addresses and/or ports contained in the SIP and SDP message bodies. The function and procedure of RACF refers to [ITU-T Y.2701]. + +ABG-FE implements NAT/NAT-PT function under the control of the network attachment control functions (NACF) and RACF. A globally unique IPv4 address, dynamically allocated from an IPv4 address pool, is associated to an IPv6 node and vice versa. ABG-FE, using NAT function to bind IPv6 addresses with IPv4 addresses, implements interworking function between the IPv4 and IPv6 domains without any additional requirements to UEs. ABG-FE shall carry out NAT-PT translation to provide transport identifier translation (e.g., transmission control protocol (TCP), user datagram protocol (UDP) and stream control transmission protocol (SCTP)) on basis of network address translation. + +### 8.3 Scenario 2: UE using IPv4 and NGN core using IPv6 + +![Diagram of Scenario 2: UE using IPv4 and NGN core using IPv6](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) + +The diagram shows an IPv4-UE (pink box) connected to a Border gateway (dashed box). Inside the Border gateway, there are three stacked components: P-CSC-FE (green box), RACF/NACF (yellow box), and ABG-FE (yellow box). The Border gateway is connected to an IPv6-NGN core (cloud shape). The label 'Q.3404(16)\_F8-2' is at the bottom right. + +Diagram of Scenario 2: UE using IPv4 and NGN core using IPv6 + +**Figure 8-2 – Scenario 2: UE using IPv4 and NGN core using IPv6** + +In the scenario of "UE using IPv4 and NGN core using IPv6" shown in Figure 8-2, P-CSC-FE and ABG-FE act as a border gateway within the control plane and the user plane (media plane) respectively. + +The difference between scenario 1 and scenario 2 is that UE and NGN core network are using different IP versions. In scenario 2, the P-CSC-FE and ABG-FE implement the same functions as described in clause 8.2. + +### 8.4 Scenario 3: NGN core using IPv6 and other IP-based network using IPv4 + +The scenario of "NGN core using IPv6 and other IP-based network using IPv4" could be categorized by two sub-scenarios. + +In the scenario of "Interconnection between NGN core using IPv6 and other IP-based network using IPv4 (which could be a PSTN/ISDN emulation subsystem or another NGN core) via IBC-FE" shown in Figure 8-3, the IBC-FE and IBG-FE act as a border gateway within the control plane and the user plane (media plane) respectively. + +![Diagram of Scenario 3-1: Interconnection between NGN core using IPv6 and other IP-based networks using IPv4 via IBC-FE. The diagram shows an IPv6-NGN core cloud on the left connected to a 'Border gateway' box. Inside the box, from top to bottom, are IBC-FE (green), RACF (yellow), and IBG-FE (yellow). The IBC-FE is connected to an 'Other IPv4-based network' cloud on the right. The IBG-FE is also connected to the same cloud. The RACF is connected to both the IBC-FE and the IBG-FE. A label 'Q.3404(16)_F8-3' is at the bottom right.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +Diagram illustrating Scenario 3-1: Interconnection between NGN core using IPv6 and other IP-based networks using IPv4 via IBC-FE. The IPv6-NGN core is connected to a Border gateway containing IBC-FE, RACF, and IBG-FE. The IBC-FE connects to the Other IPv4-based network, while the IBG-FE also connects to it. The RACF is connected to both the IBC-FE and the IBG-FE. Reference label: Q.3404(16)\_F8-3. + +Diagram of Scenario 3-1: Interconnection between NGN core using IPv6 and other IP-based networks using IPv4 via IBC-FE. The diagram shows an IPv6-NGN core cloud on the left connected to a 'Border gateway' box. Inside the box, from top to bottom, are IBC-FE (green), RACF (yellow), and IBG-FE (yellow). The IBC-FE is connected to an 'Other IPv4-based network' cloud on the right. The IBG-FE is also connected to the same cloud. The RACF is connected to both the IBC-FE and the IBG-FE. A label 'Q.3404(16)\_F8-3' is at the bottom right. + +**Figure 8-3 – Scenario 3-1: Interconnection between NGN core using IPv6 and other IP-based networks using IPv4 via IBC-FE** + +In the scenario of "Interconnection between NGN core using IPv6 and other IP-based network using IPv4 (which is using other SIP profiles or other IP-based protocols such as ITU-T H.323) via NSIW-FE" shown in Figure 8-4, the network signalling interworking functional entity (NSIW-FE) and IBG-FE act as a border gateway within the control plane and the user plane (media plane) respectively. + +![Diagram of Scenario 3-2: Interconnection between NGN core using IPv6 and other IP-based networks using IPv4 via NSIW-FE. The diagram shows an IPv6-NGN core cloud on the left connected to a 'Border gateway' box. Inside the box, from top to bottom, are NSIW-FE (green), IBC-FE (green), RACF (yellow), and IBG-FE (yellow). The NSIW-FE is connected to an 'Other IPv4-based network' cloud on the right. The IBG-FE is also connected to the same cloud. The RACF is connected to both the IBC-FE and the IBG-FE. The IBC-FE is connected to the NSIW-FE. A label 'Q.3404(16)_F8-4' is at the bottom right.](c78c2eefd86269d1740ab85a916f24f2_img.jpg) + +Diagram illustrating Scenario 3-2: Interconnection between NGN core using IPv6 and other IP-based networks using IPv4 via NSIW-FE. The IPv6-NGN core is connected to a Border gateway containing NSIW-FE, IBC-FE, RACF, and IBG-FE. The NSIW-FE connects to the Other IPv4-based network, while the IBG-FE also connects to it. The RACF is connected to both the IBC-FE and the IBG-FE. The IBC-FE is connected to the NSIW-FE. Reference label: Q.3404(16)\_F8-4. + +Diagram of Scenario 3-2: Interconnection between NGN core using IPv6 and other IP-based networks using IPv4 via NSIW-FE. The diagram shows an IPv6-NGN core cloud on the left connected to a 'Border gateway' box. Inside the box, from top to bottom, are NSIW-FE (green), IBC-FE (green), RACF (yellow), and IBG-FE (yellow). The NSIW-FE is connected to an 'Other IPv4-based network' cloud on the right. The IBG-FE is also connected to the same cloud. The RACF is connected to both the IBC-FE and the IBG-FE. The IBC-FE is connected to the NSIW-FE. A label 'Q.3404(16)\_F8-4' is at the bottom right. + +**Figure 8-4 – Scenario 3-2: Interconnection between NGN core using IPv6 and other IP-based networks using IPv4 via NSIW-FE** + +In scenario 3-1, IBC-FE implements ALG function which provides the application level translation for SIP and SDP. It requests address mapping information based on the address binding information provided by the RACF, and then modifies the addresses and/or ports contained in the SIP and SDP message bodies. + +In scenario 3-2, NSIW-FE implements ALG function which provides the application level translation for SIP and SDP. It implements the same address and port translation function as that of IBC-FE described in scenario 3-1. + +In both scenarios, IBG-FE implements NAT/NAT-PT functions under the control of IBC-FE and RACF. A globally unique IPv4 address, dynamically allocated from an IPv4 address pool, is associated to an IPv6 node, and vice versa. IBG-FE, using NAT function to bind IPv6 addresses with IPv4 addresses, implements interworking function between IPv4 and IPv6 domains. IBG-FE shall carry out NAT-PT translation to provide transport identifier translation (e.g., TCP, UDP and SCTP) on basis of network address translation. + +### 8.5 Scenario 4: NGN core using IPv4 and other IP-based networks using IPv6 + +The scenario of "NGN core using IPv4 interconnecting with other IP-based networks using IPv6" could be categorized by 2 sub-scenarios. + +In the case of "NGN core using IPv4 and other IP-based network using IPv6 (which could be a PSTN/ISDN emulation subsystem or another NGN core) via IBC-FE" shown in Figure 8-5, the IBC-FE and IBG-FE act as border gateways within the control plane and the user plane (media plane) respectively. + +![Diagram of Scenario 4-1: Interconnection between NGN core using IPv4 and other IP-based network using IPv6 via IBC-FE. The diagram shows an IPv4-NGN core cloud on the left connected to a dashed 'Border gateway' box. Inside the box, IBC-FE (green), RACF (yellow), and IBG-FE (yellow) are stacked vertically. IBC-FE is connected to an 'Other IPv6-based network' cloud on the right. IBG-FE is also connected to the same cloud. A reference code Q.3404(16)_F8-5 is at the bottom right.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +Q.3404(16)\_F8-5 + +Diagram of Scenario 4-1: Interconnection between NGN core using IPv4 and other IP-based network using IPv6 via IBC-FE. The diagram shows an IPv4-NGN core cloud on the left connected to a dashed 'Border gateway' box. Inside the box, IBC-FE (green), RACF (yellow), and IBG-FE (yellow) are stacked vertically. IBC-FE is connected to an 'Other IPv6-based network' cloud on the right. IBG-FE is also connected to the same cloud. A reference code Q.3404(16)\_F8-5 is at the bottom right. + +**Figure 8-5 – Scenario 4-1: Interconnection between NGN core using IPv4 and other IP-based network using IPv6 via IBC-FE** + +In the scenario of "NGN core using IPv4 and other IP-based network using IPv6 (which is using other SIP profile or other IP-based protocols such as H.323) via NSIW-FE" shown in Figure 8-6, the NSIW-FE and IBG-FE act as border gateways within the control plane and the user plane (media plane) respectively. + +![Diagram of Scenario 4-2: Interconnection between NGN core using IPv6 and other IP-based networks using IPv4 via NSIW-FE. The diagram shows an IPv4-NGN core cloud on the left connected to a dashed 'Border gateway' box. Inside the box, NSIW-FE (green), IBC-FE (green), RACF (yellow), and IBG-FE (yellow) are stacked vertically. NSIW-FE is connected to an 'Other IPv6-based network' cloud on the right. IBG-FE is also connected to the same cloud. A reference code Q.3404(16)_F8-6 is at the bottom right.](78ffccd66df9bafd96e3e081110d09dd_img.jpg) + +Q.3404(16)\_F8-6 + +Diagram of Scenario 4-2: Interconnection between NGN core using IPv6 and other IP-based networks using IPv4 via NSIW-FE. The diagram shows an IPv4-NGN core cloud on the left connected to a dashed 'Border gateway' box. Inside the box, NSIW-FE (green), IBC-FE (green), RACF (yellow), and IBG-FE (yellow) are stacked vertically. NSIW-FE is connected to an 'Other IPv6-based network' cloud on the right. IBG-FE is also connected to the same cloud. A reference code Q.3404(16)\_F8-6 is at the bottom right. + +**Figure 8-6 – Scenario 4-2: Interconnection between NGN core using IPv6 and other IP-based networks using IPv4 via NSIW-FE** + +In scenario 4-1, IBC-FE implements ALG function which provides the application level translation for SIP and SDP. It requests address mapping information based on the address binding information + +provided by the RACF, and then modifies the addresses and/or ports contained in the SIP and SDP message bodies. + +In scenario 4-2, NSIW-FE implements ALG function which provides the application level translation for SIP and SDP. It implements the same address and port translation functions as that of IBC-FE described in scenario 4-1. + +In both scenarios, IBG-FE implements NAT/NAT-PT functions under the control of IBC-FE and RACF. A globally unique IPv6 address, dynamically allocated from an IPv6 address pool, is associated to an IPv4 node, and vice versa. IBG-FE, using NAT function to bind IPv4 addresses with IPv6 addresses, implements interworking function between IPv4 and IPv6 domains. IBG-FE shall carry out NAT-PT translation to provide transport identifier translation (e.g., TCP, UDP and SCTP) on basis of network address translation. + +# 9 Signalling requirements for tunnelling + +## 9.1 Overviews + +Tunnelling is a mechanism to transfer data by encapsulating an IP packet into another IP packet, where a point-to-point connection is established between two peers using different IP versions. For details of this tunneling mechanism refer to [IETF RFC 5565]. In the tunneling mechanism, packets are encapsulated at the start point of a tunnel and de-capsulated at the end point of a tunnel, while the intermediate nodes simply transfer the data without any modification. In an NGN environment, the tunnelling mechanism is applicable to connect two NGN core networks, each using the same IP version, via a carrier's network using a different IP version. The start point and the end point of the tunnel are located in the border of each NGN core network respectively. The tunneling mechanism is categorized by two scenarios: + +- 1) Scenario 1: 4over6 tunnel connecting IPv4 NGN core networks; +- 2) Scenario 2: 6over4 tunnel connecting IPv6 NGN core networks. + +## 9.2 Scenario1: 4over6 tunnel connecting IPv4 NGN core networks + +![Diagram of Scenario 1: 4over6 tunnel connecting IPv4 NGN core networks. Two IPv4-NGN core networks are connected via an IPv6 backbone through border gateways. Each border gateway contains IBC-FE, RACF, and IBG-FE components. Two 4over6 tunnels are shown: one between the IBC-FEs and another between the IBG-FEs.](4636adff5682a064f0ae5f13a1d464a6_img.jpg) + +The diagram illustrates two IPv4-NGN core networks (represented by clouds) connected via a central IPv6 backbone (also a cloud). Each IPv4-NGN core is connected to a 'Border gateway' (represented by a dashed box). Inside each border gateway, there are three stacked components: IBC-FE, RACF, and IBG-FE. Two tunnels, both labeled '4over6 tunnel', connect the border gateways. The upper tunnel connects the IBC-FE of the left border gateway to the IBC-FE of the right border gateway. The lower tunnel connects the IBG-FE of the left border gateway to the IBG-FE of the right border gateway. A small label 'Q.3404(16)\_F9-1' is in the bottom right corner. + +Diagram of Scenario 1: 4over6 tunnel connecting IPv4 NGN core networks. Two IPv4-NGN core networks are connected via an IPv6 backbone through border gateways. Each border gateway contains IBC-FE, RACF, and IBG-FE components. Two 4over6 tunnels are shown: one between the IBC-FEs and another between the IBG-FEs. + +**Figure 9-1 – Scenario 1: 4over6 tunnel connecting IPv4 NGN core networks** + +As shown in Figure 9-1, two IPv4 NGN core networks are connected via an IPv6 bearer network by establishing 4over6 tunnels. The border gateway acting as the start and the end point of the tunnel implements packet capsulation and de-capsulation. The border gateway is required to support IPv4 and IPv6 dual stack. As implemented, the signaling messages are transferred through the tunnel established between IBC-FEs located at the edge of two IPv4 NGN core networks, while media streams are transferred through the tunnel established between IBG-FEs at the edge of two IPv4 NGN core networks. + +There are three steps to transfer an IPv4 packet through the IPv6 transit core network: + +- 1) Encapsulate the incoming IPv4 packet with an IPv6 tunnel header at the start point of a tunnel; +- 2) Transmit the encapsulated packet over the IPv6 transit backbone; +- 3) De-capsulate the IPv6 header and forward the original IPv4 packet at the end point of a tunnel. + +The 4over6 tunnel protocol refers to [IETF RFC 5747]. + +## 9.3 Scenario 2: 6over4 tunnel connection IPv6 NGN core networks + +![Diagram of Scenario 2: 6over4 tunnel connecting IPv6 NGN core networks. Two IPv6-NGN core networks (represented by clouds) are connected via a central IPv4 backbone (represented by a cloud). Each IPv6-NGN core is connected to a Border gateway (represented by a dashed box). Inside each Border gateway, there are three components: IBC-FE, RACF, and IBG-FE. Two 6over4 tunnels are shown: one connecting the IBC-FEs of the two Border gateways, and another connecting the IBG-FEs of the two Border gateways, both passing through the IPv4 backbone. A small label 'Q.3404(16)_F9-2' is in the bottom right corner.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Diagram of Scenario 2: 6over4 tunnel connecting IPv6 NGN core networks. Two IPv6-NGN core networks (represented by clouds) are connected via a central IPv4 backbone (represented by a cloud). Each IPv6-NGN core is connected to a Border gateway (represented by a dashed box). Inside each Border gateway, there are three components: IBC-FE, RACF, and IBG-FE. Two 6over4 tunnels are shown: one connecting the IBC-FEs of the two Border gateways, and another connecting the IBG-FEs of the two Border gateways, both passing through the IPv4 backbone. A small label 'Q.3404(16)\_F9-2' is in the bottom right corner. + +**Figure 9-2 – Scenario 2: 6over4 tunnel connecting IPv6 NGN core networks** + +As shown in Figure 9-2, two IPv6 NGN core networks was connected via IPv4 bearer network by establishing 6over4 tunnel. The border gateway acting as the start and the end point of a tunnel implements packet capsulation and de-capsulation. The border gateway is required to support IPv4 and IPv6 dual stack. As implemented, the signal messages are transferred through the tunnel established between IBC-FEs located at the edge of two IPv6 NGN core networks, while media streams are transferred through the tunnel established between IBG-FEs located at the edge of two IPv6 NGN core networks. + +There are three steps to transfer an IPv6 packet through the IPv4 transit core network: + +- 1) Encapsulate the incoming IPv6 packet with an IPv4 tunnel header at the start point of a tunnel; +- 2) Transmit the encapsulated packet over the IPv4 transit backbone; +- 3) De-capsulate the IPv4 header and forward the original IPv6 packet at the end point of a tunnel. + +The 6over4 tunnel protocol refers to [IETF RFC 5969]. + + + +## **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 | 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 | 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, 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/Q/T-REC-Q.3717-201810-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3717-201810-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..86ea6d298c15cd92e13400ec941c723a21c9b0af --- /dev/null +++ b/marked/Q/T-REC-Q.3717-201810-I_PDF-E/raw.md @@ -0,0 +1,763 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3717** + +(10/2018) + +SERIES Q: SWITCHING AND SIGNALLING, AND +ASSOCIATED MEASUREMENTS AND TESTS + +Signalling requirements and protocols for SDN – Resource +control protocols + +--- + +**Signalling requirements for automatic +management of IP address pools by +software-defined networking technologies on a +broadband network gateway** + +Recommendation ITU-T Q.3717 + +# ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 | +| Resource control protocols | Q.3710–Q.3739 | +| Network signalling and signalling requirements for services | Q.3740–Q.3779 | +| TESTING SPECIFICATIONS | Q.3900–Q.4099 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000–Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050–Q.5069 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T Q.3717 + +# Signalling requirements for automatic management of IP address pools by software-defined networking technologies on a broadband network gateway + +## Summary + +Recommendation ITU-T Q.3717 describes the signalling requirements for the implementation of automatic management and efficient utilization of IP address resources using software-defined networking technologies on broadband network gateways. The signalling is used to automatically implement the allocation, monitoring and reclaiming of IP address resources. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.3717 | 2018-10-14 | 11 | 11.1002/1000/13698 | + +## Keywords + +Automatic management, IP address pool, software-defined networking. + +--- + +\* 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 ..... | 1 | +| 5 Conventions ..... | 2 | +| 6 Introduction of automatic management of IP address resources ..... | 2 | +| 7 Architecture of automatic management of IP address resources..... | 3 | +| 7.1 General architecture..... | 3 | +| 7.2 Functional entities ..... | 4 | +| 8 Signalling requirements of the automatic management of IP address resources..... | 5 | +| 8.1 Northbound interface message of the controller ..... | 5 | +| 8.2 Southbound interface message of the controller ..... | 11 | + + + +## Recommendation ITU-T Q.3717 + +## Signalling requirements for automatic management of IP address pools by software-defined networking technologies on a broadband network gateway + +# 1 Scope + +This Recommendation describes the signalling requirements for the implementation of automatic management and efficient utilization of IP address resources using software-defined networking technologies on broadband network gateways. + +# 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 Y.3300] Recommendation ITU-T Y.3300 (2014), *Framework of software-defined networking*. +- [ITU-T Y.3302] Recommendation ITU-T Y.3302 (2017), *Functional architecture of software-defined networking*. +- [ITU-T Q.3315] Recommendation ITU-T Q.3315 (2015), *Signalling requirements for flexible network service combination on broadband network gateway*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +None. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|---------|-----------------------------------| +| API | Application Programming Interface | +| BNG | Broadband Network Gateway | +| CGN | Carrier-Grade NAT | +| DNS | Domain Name System | +| DS-Lite | Dual Stack Lite | +| IP | Internet Protocol | +| IPv4 | Internet Protocol Version 4 | +| IPv6 | Internet Protocol Version 6 | + +| | | +|------|-----------------------------------------| +| NAT | Network Address Translation | +| NFV | Network Function Virtualization | +| SDN | Software Defined Networking | +| vBNG | Virtualized Broadband Network Gateway | +| vNAT | Virtualized Network Address Translation | + +# 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 keyword "should" indicates a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. + +The keyword "may" indicates 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 Introduction of automatic management of IP address resources + +As networks evolve towards software-defined networking/network function virtualization (SDN/NFV) enabled networks, intensive operations and resource pooling to improve resource use efficiency is the development trend of networks. It requires intensive resource management capabilities to manage network resources, such as IP address resources, session resources and forwarding resources. SDN/NFV technologies provide an effective means for intensive resource management. This Recommendation uses the intensive management of IP addresses resource as an example to describe the implementation. + +Generally, operators will face the following problems when they manage IP address resources in current networks: + +- Manually configuring IP address resources of network devices, such as a broadband network gateway / virtualized broadband network gateway (BNG/vBNG), is complicated and it has high maintenance costs. Moreover the IP address usage rate is low. +- For physical or virtual network functional units (e.g., carrier-grade NAT (CGN), Ds-Lite, etc.), insufficient sharing of IP addresses and port resources will lead to wasted resources. + +A method for the automatic management of IP address resources based on SDN/NFV technologies is proposed to solve the problems. In this method, an IP address resource management application interacts with the SDN controller to allocate and reclaim IP addresses. Using this method has the following advantages: + +- The centralized management of IPv4/IPv6 addresses enables automatic request, allocation, and reclaim of IPv4/IPv6 address resources, replacing the traditional manual configuration method, and improves IP address resources utilization. +- It enables IP address resources to be centrally controlled and highly shared on the physical interfaces, virtual interfaces and tunnel interfaces. +- Real-time dynamic adjustment and intelligent allocation of IP addresses through open programmable interfaces (APIs) is possible. + +The automatic management of IP address resources is based on a centralized control mode, which facilitates centralized/unified control and sharing, and helps achieve the efficient utilization IP address resources among the BNG/vBNG devices. Moreover, differentiated requirements also can be satisfied through open application programming interfaces (APIs). + +# 7 Architecture of automatic management of IP address resources + +## 7.1 General architecture + +The architecture of the automatic management of IP address resources, which is required to be kept aligned with the framework of a software-defined networking model defined in [ITU-T Y.3300], consists of three parts: an app for automatic management of IP address resources, SDN controller and forwarding devices. This is shown in Figure 7-1. + +Based on this architecture, unified IP address resource management can be implemented on the physical network elements interfaces, virtual network element interfaces and tunnel interfaces (such as tunnels for IPv4/IPv6 transition). In addition, this architecture implements the automatic management of IP address resources by a separate application, rather than adding a module to the SDN controller, which simplifies the complexity of the SDN controller. + +### 1) App for automatic management of IP address resources + +The app for the automatic management of IP address resources implements a unified configuration of the IP address resource pool and performs the main decision functions, e.g., IP address resource allocation and reclaiming. At the same time, it supports the query of the use status of the IP address resources, including current use status, historical use status and the usage log of the IP address resources, etc. + +### 2) SDN controller + +The SDN controller obtains the usage status of the IP address resources from the forwarding devices through the southbound interface, and then reports it to the app of automatic management of IP address resources through the northbound interface. Moreover, the SDN controller requests or reclaims an IP address block from the app, and supports the configuring of network devices. + +### 3) Device + +The device (e.g., BNG/CGN) supports the notification of the current IP address usage status and assigns an IP address from the configured IP address pool to the user terminal. + +![Diagram of the architecture of automatic management of IP address resources. A 'Management and orchestration' block on the left is connected to a central 'SDN controller' block. The 'SDN controller' is connected to two 'Device' blocks, 'vBNG/CGN' and 'BNG/CGN'. Above the 'SDN controller' is an 'App for automatic management of IP address resources' block, which is also connected to the 'SDN controller'. The 'SDN controller', 'App', 'vBNG/CGN', and 'BNG/CGN' are all enclosed in a dashed box labeled 'Device'.](0bf9346902e9a3bdabf05ceacc1947f5_img.jpg) + +``` +graph TD; MO[Management and orchestration] <--> SDN[SDN controller]; subgraph Device; SDN <--> App[App for automatic management of IP address resources]; SDN <--> vBNG[vBNG/CGN]; SDN <--> BNG[BNG/CGN]; end; +``` + +Q.3717(18)\_F7-1 + +Diagram of the architecture of automatic management of IP address resources. A 'Management and orchestration' block on the left is connected to a central 'SDN controller' block. The 'SDN controller' is connected to two 'Device' blocks, 'vBNG/CGN' and 'BNG/CGN'. Above the 'SDN controller' is an 'App for automatic management of IP address resources' block, which is also connected to the 'SDN controller'. The 'SDN controller', 'App', 'vBNG/CGN', and 'BNG/CGN' are all enclosed in a dashed box labeled 'Device'. + +**Figure 7-1 – Architecture of automatic management of IP address resources** + +## 7.2 Functional entities + +Figure 7-2 depicts the functional entities and interfaces of the architecture of automatic management of IP address resources. + +![Figure 7-2: Functional entities and interface of the architecture of automatic management of IP address resources. The diagram shows a hierarchical architecture with four layers. The top layer is the 'App for automatic management of IP address resources', which includes 'Device management', 'Database', 'Controller management', 'Address allocation processing unit', and 'Address query processing unit'. An 'Operator' is shown interacting with the app. The second layer is the 'SDN controller', which includes 'Device management', 'Address processing unit', 'IP address status information processing', and 'Controller management'. The third layer consists of 'Southbound REST interface' (with nodes NA1, NA3, NA2, NA4) and 'Northbound REST interface' (with nodes NC1, NC2, NC3, NC4, NC5). The bottom layer is the 'Device' layer, containing nodes DC1, DC2, DC5, DC3, CD1, DC4, and CD2. Arrows indicate the flow of information between entities across these interfaces.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg) + +Figure 7-2: Functional entities and interface of the architecture of automatic management of IP address resources. The diagram shows a hierarchical architecture with four layers. The top layer is the 'App for automatic management of IP address resources', which includes 'Device management', 'Database', 'Controller management', 'Address allocation processing unit', and 'Address query processing unit'. An 'Operator' is shown interacting with the app. The second layer is the 'SDN controller', which includes 'Device management', 'Address processing unit', 'IP address status information processing', and 'Controller management'. The third layer consists of 'Southbound REST interface' (with nodes NA1, NA3, NA2, NA4) and 'Northbound REST interface' (with nodes NC1, NC2, NC3, NC4, NC5). The bottom layer is the 'Device' layer, containing nodes DC1, DC2, DC5, DC3, CD1, DC4, and CD2. Arrows indicate the flow of information between entities across these interfaces. + +Figure 7-2 – Functional entities and interface of the architecture of automatic management of IP address resources + +### 7.2.1 Functional entities of app for automatic management of IP address resources + +#### – Device management + +This functional entity receives the online registration message, offline notification message, and heartbeat protection message of the device reported by the SDN controller, thereby maintaining the state of the associated devices. + +#### – Address allocation processing unit + +This functional entity is used to allocate or reclaim an IP address block to the device, and then receive an execution result from the device. + +#### – Address query processing unit + +This functional entity is used to query the IP address block usage status of the device, receive the query result and then update the usage status. + +- Controller management +This functional entity is used to configure and manage the SDN controller, make the SDN controller support the automatic management of the IP address resources. + +### 7.2.2 Functional entities of the SDN controller used to process IP address resources + +- Device management +This function implements online registration, offline notification, heartbeat protection of the device and maintains the state of associated devices. +- Address processing unit +This functional entity is used to receive the IP address block information allocated or reclaimed by the app for the automatic management of IP address resources and processing it. +- IP address status information processing +This functional entity is used to receive the message of the app for automatic management of IP address resources, query the IP address block usage status of the device and return the query result to the app. +- Controller management +This functional entity is used to receive the management and configuration parameters for the controller from the app. + +### 7.2.3 Interface message + +This clause describes the interface message shown in Figure 7-2. + +- Northbound interface message of the SDN controller +The northbound interface supports the delivery of various operation commands from the app to the SDN controller and the reporting of the IP address usage status in the device to the app. +- Southbound interface message of the SDN controller +The southbound interface connects the devices of different manufacturers and implements the allocation, reclaim and status query of the IP address block. + +# 8 Signalling requirements of the automatic management of IP address resources + +## 8.1 Northbound interface message of the controller + +### 8.1.1 Controller configuration message + +The controller configuration message, which is numbered NC1, sent from the app to the SDN controller is used to configure the controller id and devices which are managed by the SDN controller. Input parameters of the controller configuration message are described in Table 8-1. + +**Table 8-1 – Input parameters of the controller configuration message** + +| Parameter name | Type | Optional | Meanings and explanations | +|----------------|--------------|----------|-------------------------------------------------| +| controller_id | Int | N | The unique identifier of the SDN controller | +| device_list | List | N | A list of devices managed by the SDN controller | + +**Table 8-1 – Input parameters of the controller configuration message** + +| Parameter name | Type | Optional | Meanings and explanations | +|-----------------------------------|--------|----------|------------------------------------------------------------------------| +| device_keep_alive_interval | Int | N | Heartbeat interval of the device status required by the SDN controller | +| ipv4_address_pool_usage_threshold | Float | N | Threshold of applied for a new IPv4 address pool | +| ipv6_address_pool_usage_threshold | Float | N | Threshold of applied for a new IPv6 address pool | +| state_update_interval | Int | N | Time interval for refreshing device status to the SDN controller | +| device_sampling_interval | Int | N | Time interval of sampling status of IP address pool by the device | +| device_id | Int | N | The unique identifier of the device assigned by the app | +| device_type | String | N | Device type, including vBNG, CGN, etc. | +| device_ip | String | N | IP address of the device | +| device_port | Int | N | The port number range assigned to the device used in NAT | + +Output parameters of the controller configuration message is one of the following options. + +- Success, if the command is successfully executed; +- Failure, if the command fails to execute. + +### 8.1.2 Request reclaim message + +The request reclaim message, which is numbered NC2, sent from the app to the SDN controller is used to request the SDN controller to reclaim the specified IP address block from the specified device. The format of this message is similar to the text format of the Netconf protocol. When the value of the leasing time of the IP address block is set to 0, it should be reclaimed. + +Input parameters of the request reclaim message are described in Table 8-2. + +**Table 8-2 – Input parameters of the request reclaim message** + +| Parameter name | Type | Optional | Meanings and explanations | +|--------------------|--------|----------|------------------------------------------------------------------| +| device_id | Int | N | The unique identifier of the device assigned by the app | +| address_block_id | Int | N | The unique identifier of IP address block assigned by the app | +| protocol_type | Int | N | 0 indicates IPv6, 1 indicates IPv4 | +| address_block_name | String | N | The name of IP address block assigned by the app | +| address_pool_id | Int | N | The unique identifier of the IP address pool assigned by the app | +| address_pool_name | String | N | The name of the IP address pool assigned by the app | + +**Table 8-2 – Input parameters of the request reclaim message** + +| Parameter name | Type | Optional | Meanings and explanations | +|----------------|------|----------|----------------------------------------------------------------------------------------------------------------------| +| leasing_time | Int | N | The lease time of the IP address block.
Note: The IP address block should be reclaimed when leasing time set to 0 | + +Output parameters of the request reclaim message is one of the following options: + +- Success, if the specified IP address block from the specified device is successfully reclaimed; +- Failure, if the specified IP address block from the specified device is failed to reclaim. + +### **8.1.3 Send heartbeat message** + +The send heartbeat message, which is numbered NC3, sent from the app to the SDN controller is used to request the device's online status. This message may simultaneously confirm the online status of the SDN controller and devices which are managed by the SDN controller. + +The input parameter of the send heartbeat message is described in Table 8-3. + +**Table 8-3 – Input parameter of the send heartbeat message** + +| Parameter name | Type | Optional | Meanings and explanations | +|----------------|------|----------|---------------------------------------------| +| controller_id | Int | N | The unique identifier of the SDN controller | + +Output parameters of the send heartbeat message is described in the following Table 8-4. + +**Table 8-4 – Output parameters of the send heartbeat message** + +| Parameter name | Type | Optional | Meanings and explanations | +|----------------|--------------|----------|---------------------------------------------------------| +| controller_id | Int | N | The unique identifier of the SDN controller | +| device_list | List | N | A list of devices managed by the SDN controller | +| device_id | Int | N | The unique identifier of the device assigned by the app | +| Is_alive | String | N | Indicates whether the device is online | + +### **8.1.4 Manual allocation message** + +The manual allocation message, which is numbered NC4, sent from the app to the SDN controller is used to manually add a specific IP address block to a specified IP address pool in the specified device. + +Input parameters of the manual allocation message are described in Table 8-5. + +**Table 8-5 – Input parameters of the manual allocation message** + +| Parameter name | Type | Optional | Meanings and explanations | +|--------------------|--------|----------|------------------------------------------------------------------------------------------| +| device_id | Int | N | The unique identifier of the device assigned by the app | +| device_type | String | N | Device type, including vBNG, CGN, etc. | +| device_ip | String | N | IP address of the device | +| device_port | Int | N | The port number range assigned to the device used in t NAT | +| address_block_id | Int | N | The unique identifier of IP address block assigned by the app | +| protocol_type | Int | N | 0 indicates Ipv6, 1 indicates IPv4 | +| address_block_name | String | N | The name of IP address block assigned by the app | +| address_pool_id | Int | N | The unique identifier of the IP address pool assigned by the app | +| address_pool_name | String | N | The name of the address pool assigned by the app | +| domain_name | String | N | Domain name | +| ip_prefix | String | N | Represents a prefix of IPv4 address or IPv6 address | +| ip_prefix_length | Int | N | The length of IP address prefix | +| usergateway | String | N | IP address of the user gateway | +| gwnetmask | Int | N | The mask length of IP address of the user gateway | +| dns_server_list | String | N | Include at least one of primary domain name system (DNS) and secondary DNS | +| leasing_time | Int | N | The lease time of the IP address block.
Note: The default recommended value is 3days. | + +Output parameters of the manual allocation message is one of the following options: + +- Success, if the command is successfully executed; +- Failure, if the command fails to execute. + +### 8.1.5 Manual offline message + +The manual offline message, which is numbered NC5, sent from the app to the SDN controller is used to take the specified device offline. After receiving the command, the SDN controller delivers it to the device, and then the device should kick the online users offline and delete the configuration related to the IP address pool. The device responds the command execution result to the SDN controller, and the SDN controller delivers the result to the app. + +The input parameter of the manual offline message is described in Table 8-6. + +**Table 8-6 – Input parameter of the manual offline message** + +| Parameter name | Type | Optional | Meanings and explanations | +|----------------|------|----------|----------------------------------------------------------| +| device_id | Int | N | The unique identifier of the device assigned by the app. | + +Output parameters of the manual offline message is one of the following options: + +- Success, if the command is successfully executed; +- Failure, if the command fails to execute. + +### 8.1.6 Report a new device message + +The report a new device message, which is numbered NA1, sent from the SDN controller to the app is used to inform the app when a new device is registered to the SDN controller. + +The input parameter of the report a new device message is described in Table 8-7. + +**Table 8-7 – Input parameter of the report a new device message** + +| Parameter name | Type | Optional | Meanings and explanations | +|----------------|------|----------|---------------------------------------------------------| +| device_id | Int | N | The unique identifier of the device assigned by the app | + +Output parameters of report a new device message is one of the following options: + +- Success, if the command is successfully executed; +- Failure, if the command fails to execute. + +### 8.1.7 Report status message + +The report status message, which is numbered NA2, sent from the SDN controller to the app is used to report the IP address pool status to the app when the SDN controller receives it from the device. + +Input parameters of the report status message are described in Table 8-8. + +**Table 8-8 – Input parameters of the report status message** + +| Parameter name | Type | Optional | Meanings and explanations | +|-----------------------------|--------------------------|----------|------------------------------------------------------------------| +| device_id | Int | N | The unique identifier of the device assigned by the app | +| time | Double | N | The time of the SDN controller report status to the app | +| address_pool | List | N | List of all IP address pools | +| address_pool_id | Int | N | The unique identifier of the IP address pool assigned by the app | +| address_pool_name | String | N | The name of the address pool assigned by the app | +| protocol_type | Int | N | 0 indicates IPv6, 1 indicates IPv4 | +| address_pool_ranges | List | N | List of all IP address blocks in an IP address pool | +| address_block_id | Int | N | The unique identifier of the IP address block | +| address_block_name | String | N | The name of the IP address block | +| average_address_usage_ratio | Float | N | An IP address block usage rate in a period of time | + +Output parameters of the report status message is one of the following options: + +- Success, if the command is successfully executed. Moreover, the app will be triggered to allocate an IP address block to the device if the average IP address usage ratio is more than + +a threshold. Otherwise, the app will be triggered to reclaim an IP address block from the device if the parameter is less than a threshold. + +- Failure, if the command fails to execute. + +### 8.1.8 Report offline message + +The report offline message, which is numbered NA3, sent from the SDN controller to the app is used to report the device offline status when the SDN controller receives an offline message from the device or the SDN controller detects the device offline status by heartbeat message. + +Input parameters of the report offline message are described in Table 8-9. + +**Table 8-9 – Input parameters of the report offline message** + +| Parameter name | Type | Optional | Meanings and explanations | +|----------------|--------|----------|---------------------------------------------------------| +| device_id | Int | N | The unique identifier of the device assigned by the app | +| offline_reason | String | N | Description of the device offline reason | + +Output parameters of the report offline message is one of the following options: + +- Success, if the command is successfully executed; +- Failure, if the command fails to execute. + +### 8.1.9 Report result message + +The report result message, which is numbered NA4, sent from the SDN controller to the app is used to report the processing result for a single address block. + +Input parameters of the report result message are described in Table 8-10. + +**Table 8-10 – Input parameters of the report result message** + +| Parameter name | Type | Optional | Meanings and explanations | +|--------------------|--------|----------|------------------------------------------------------------------| +| device_id | Int | N | The unique identifier of the device assigned by the app | +| device_ip | String | N | IP address of the device | +| domain_name | String | N | Domain name | +| time | Double | N | The time of the SDN controller report result to the app | +| address_pool_id | Int | N | The unique identifier of the IP address pool assigned by the app | +| address_pool_name | String | N | The name of the IP address pool assigned by the app | +| protocol_type | Int | N | 0 indicates IPv6, 1 indicates IPv4 | +| address_block_id | Int | N | The unique identifier of IP address block | +| address_block_name | String | N | The name of IP address block | +| ip_prefix | String | N | Represents a prefix of IPv4 address or IPv6 address | +| ip_prefix_length | Int | N | The length of IP address prefix | +| result | Int | N | 0 means allocate successfully | + +**Table 8-10 – Input parameters of the report result message** + +| Parameter name | Type | Optional | Meanings and explanations | +|-----------------------|-------------|-----------------|------------------------------------------------------------------------------------------| +| | | | 1 means reclaim successfully
2 means failed to allocate
3 means failed to reclaim. | + +Output parameters of the report result message is one of the following options: + +- Success, if the command is successfully executed; +- Failure, if the command fails to execute. + +## **8.2 Southbound interface message of the controller** + +The design of the southbound interface in this section uses the Netconf protocol. Taking the YANG model implementation as an example, other southbound interface protocols, such as radius and openflow, can be easily adapted to the related parameters. The device serves as the server side of the Netconf protocol and the SDN controller serves as the client side of Netconf protocol. + +### **8.2.1 Register message** + +The register message, which is numbered DC1, sent from the device to the SDN controller is used to register and report the initial parameters of the device to the SDN controller. + +The input parameter of the register message is described in the following Table 8-11. + +**Table 8-11 – Input parameter of the register message** + +| Parameter name | Type | Optional | Meanings and explanations | +|-----------------------|-------------|-----------------|---------------------------------------------------------| +| device_id | Int | N | The unique identifier of the device assigned by the app | + +Output parameters of the register message is one of the following options: + +- Success, if the command is successfully executed; +- Failure, if the command fails to execute. + +### **8.2.2 Report state message** + +The report state message, which is numbered DC2, sent from the device to the SDN controller is used to report the device state. The device may report its state in one of the following cases: + +- app active inquiry; +- the local IP address pool reaches the usage threshold and the device actively applies for a new IP address block; +- the local address block reaches the reclamation threshold and the device actively applies for reclaiming the IP address block; +- the device periodically reports the state; +- the device report state after first successful registration. + +Input parameters of the report state message are described in Table 8-12. + +**Table 8-12 – Input parameters of the report state message** + +| Parameter name | Type | Optional | Meanings and explanations | +|-----------------------------|--------|----------|------------------------------------------------------------------| +| time | Double | N | The time of the device report state to the SDN controller | +| domain_name | String | N | Domain name | +| device_id | Int | N | The unique identifier of the device assigned by the app | +| address_pool_name | String | N | The name of the IP address pool assigned by the app | +| address_pool_id | Int | N | The unique identifier of the IP address pool assigned by the app | +| ipv4_address_block_name | String | N | The name of ipv4 address block | +| ipv4_address_block_id | Int | N | The unique identifier of ipv4 address block | +| ipv6_address_block_name | String | N | The name of ipv6 address block | +| ipv6_address_block_id | Int | N | The unique identifier of ipv6 address block | +| average_address_usage_ratio | Float | N | An IP address block usage rate in a period of time | + +Output parameters of the report state message is one of the following options: + +- Option 1 +- The SDN controller allocate a new IP address block to the device, either IPv4 address block or IPv6 address block. + - 1) Parameters of an IPv4 address block are described in Table 8-13. + +**Table 8-13 – Parameters of an IPv4 address block** + +| Parameter name | Type | Optional | Meanings and explanations | +|-------------------------|--------|----------|--------------------------------------------------------------------| +| time | Double | N | The time of the SDN controller allocating a new IPv4 address block | +| domain_name | String | N | Domain name | +| device_id | Int | N | The unique identifier of the device assigned by the app | +| address_pool_name | String | N | The name of the IPv4 address pool assigned by the app | +| address_pool_id | Int | N | The unique identifier of the IPv4 address pool assigned by the app | +| IPv4_address_block_id | Int | N | The unique identifier of IPv4 address block | +| IPv4_address_block_name | String | N | The name of ipv4 address block | +| IPv4_ip_prefix | String | N | Represents a prefix of IPv4 address | +| IPv4_prefix_length | Int | N | The length of IPv4 address prefix | +| usergateway | String | N | IP address of the user gateway | + +**Table 8-13 – Parameters of an IPv4 address block** + +| Parameter name | Type | Optional | Meanings and explanations | +|-----------------------|-------------|-----------------|------------------------------------------------------------------------------------------| +| gwnetmask | Int | N | The mask length of IP address of the user gateway | +| dns_list | String | N | Include at least one of primary DNS and secondary DNS | +| leasing_time | Int | N | The lease time of the IP address block.
Note: The default recommended value is 3days. | + +2) Parameters of an IPv6 address block are described in Table 8-14. + +**Table 8-14 – Parameters of an IPv6 address block** + +| Parameter name | Type | Optional | Meanings and explanations | +|-------------------------|-------------|-----------------|------------------------------------------------------------------------------------------| +| time | Double | N | The time of the SDN controller allocating a new IPv6 address block | +| domain_name | String | N | Domain name | +| device_id | Int | N | The unique identifier of the device assigned by the app | +| address_pool_name | String | N | The name of the IPv6 address pool assigned by the app | +| address_pool_id | Int | N | The unique identifier of the IPv6 address pool assigned by the app | +| IPv6_address_block_id | Int | N | The unique identifier of IPv6 address block | +| IPv6_address_block_name | String | N | The name of ipv6 address block | +| IPv6_ip_prefix | String | N | Represents a prefix of IPv6 address | +| IPv6_prefix_length | Int | N | The length of IPv6 address prefix | +| usergateway | String | N | IP address of the user gateway | +| gwnetmask | Int | N | The mask length of IP address of the user gateway | +| dns_list | String | N | Include at least one of primary DNS and secondary DNS | +| leasing_time | Int | N | The lease time of the IP address block.
Note: The default recommended value is 3days. | + +- Option 2 +- The SDN controller requires the device to reclaim the IP address block; input parameters are described in Table 8-15. + +**Table 8-15 – Input parameters of the SDN controller requiring the device to reclaim the IP address block** + +| Parameter name | Type | Optional | Meanings and explanations | +|-------------------------|--------|----------|------------------------------------------------------------------------------------------| +| device_id | Int | N | The unique identifier of the device assigned by the app | +| address_pool_name | String | N | The name of the IP address pool assigned by the app | +| address_pool_id | Int | N | The unique identifier of the IP address pool assigned by the app | +| IPv4_address_block_id | Int | N | The unique identifier of IPv4 address block | +| IPv4_address_block_name | String | N | The name of ipv4 address block | +| IPv6_address_block_id | Int | N | The unique identifier of IPv6 address block | +| IPv6_address_block_name | String | N | The name of ipv6 address block | +| leasing_time | Int | N | The lease time of the IP address block.
Note: The default recommended value is 3days. | + +- Option 3: Status report is successful, IP address allocation or reclaim has not been triggered. +- Option 4: Status report is failed, IP address allocation or reclaim has not been triggered. + +### 8.2.3 Report acquiring IP address message + +The report acquiring IP address message, which is numbered DC3, sent from the device to the SDN controller is used to report the information of acquiring the IP address block. The message is divided into two sub-messages: 1) The device reports the configuration confirmation message to the SDN controller when the configuration module completes the configuration and stores the configuration command or file in the database. 2) The device sends a service processing confirmation message to the SDN controller when the service module completes the service processing (such as user routes and uplink routes are successfully advertised) of the IP address. + +Input parameters of the report acquiring IP address message is described in Table 8-16. + +**Table 8-16 – Input parameters of the report acquiring IP address message** + +| Parameter name | Type | Optional | Meanings and explanations | +|-------------------------------|------|----------|--------------------------------------------------------------------------------------------------------------------------------| +| IP_address_block_allocate_ack | Int | N | 0 indicates that an IP address block is successfully allocated.
1 indicates that an IP address block fails to be allocated. | + +Output parameter is none. + +### 8.2.4 Report reclaiming IP address message + +The report reclaiming IP address message, which is numbered DC4, sent from the device to the SDN controller is used to report the information of reclaiming the IP address block. The message is divided into two sub-messages: 1) The device reports the reclaim confirmation message to the SDN controller when the configuration module deletes the database and recycles the IP address pool. 2) The device sends a service processing confirmation message to the SDN controller when the service module + +completes the service processing (such as user routes and uplink routes are withdrawn) of the IP address. + +The input parameter of the report reclaiming IP address message is described Table 8-17. + +**Table 8-17 – Input parameter of the report reclaiming IP address message** + +| Parameter name | Type | Optional | Meanings and explanations | +|------------------------------|------|----------|--------------------------------------------------------------------------------------------------------------------------------| +| IP_address_block_reclaim_ack | Int | N | 0 indicates that an IP address block is successfully reclaimed.
1 indicates that an IP address block fails to be reclaimed. | + +Output parameter is none. + +### 8.2.5 Report offline message + +The report offline message, which is numbered DC5, sent from the device to the SDN controller is used to report the device offline state. The offline message is divided into three cases: 1) The device is active offline. 2) The SDN controller requests the device offline. 3) The device is abnormal offline. The message is used to actively report the device offline status to the SDN controller. + +The input parameter of the report offline message is described in Table 8-18. + +**Table 8-18 – Input parameter of the report offline message** + +| Parameter name | Type | Optional | Meanings and explanations | +|----------------|------|----------|---------------------------------------------------------| +| device_id | Int | N | The unique identifier of the device assigned by the app | + +Output parameters of the report offline message is one of the following options: + +- Success, if the command is successfully executed; +- Failure, if the command fails to execute. + +### 8.2.6 Query state message + +The query state message, which is numbered CD1, sent from the SDN controller to the device is used to query the device status information according to the app request. + +Input parameters of the query state message are described in Table 8-19. + +**Table 8-19 – Input parameters of the query state message** + +| Parameter name | Type | Optional | Meanings and explanations | +|-------------------------|--------|----------|------------------------------------------------------------------| +| address_pool_name | String | N | The name of the IP address pool assigned by the app | +| address_pool_id | Int | N | The unique identifier of the IP address pool assigned by the app | +| device_id | Int | N | The unique identifier of the device assigned by the app. | +| ipv4_address_block_name | String | N | The name of ipv4 address block | + +**Table 8-19 – Input parameters of the query state message** + +| Parameter name | Type | Optional | Meanings and explanations | +|-----------------------------|-------------|-----------------|----------------------------------------------------| +| ipv4_address_block-id | Int | N | The unique identifier of IPv4 address block | +| ipv6_address_block_name | String | N | The name of ipv6 address block | +| ipv6_address_block-id | Int | N | The unique identifier of IPv6 address block | +| average_address_usage_ratio | Float | N | An IP address block usage rate in a period of time | + +When receiving the query message, the device will report the status to the SDN controller. Output parameters of the query state message are described in Table 8-20. + +**Table 8-20 – Output parameters of the query state message** + +| Parameter name | Type | Optional | Meanings and explanations | +|-----------------------------|-------------|-----------------|------------------------------------------------------------------| +| address_pool_name | String | N | The name of the IP address pool assigned by the app | +| address_pool_id | Int | N | The unique identifier of the IP address pool assigned by the app | +| device_id | Int | N | The unique identifier of the device assigned by the app. | +| ipv4_address_block_name | String | N | The name of ipv4 address block | +| ipv4_address_block-id | Int | N | The unique identifier of IPv4 address block | +| ipv6_address_block_name | String | N | The name of ipv6 address block | +| ipv6_address_block-id | Int | N | The unique identifier of IPv6 address block | +| average_address_usage_ratio | Float | N | An IP address block usage rate in a period of time | + +### 8.2.7 Manual offline message + +The manual offline message, which is numbered CD2, sent from the SDN controller to the device is used to request the device offline. The app issues the command of requesting the device offline, and then the SDN controller receives it and deliver it to the device. When receiving the message, the device kicks the online users offline, reclaims the IP address resources and then reports the execution result to the SDN controller. At the same time, the device stops the heartbeat message. + +The input parameter of the manual offline message is described in Table 8-21. + +**Table 8-21 – Input parameter of the manual offline message** + +| Parameter name | Type | Optional | Meanings and explanations | +|-----------------------|-------------|-----------------|---------------------------------------------------------| +| device_id | Int | N | The unique identifier of the device assigned by the app | + +Output parameters of the manual offline message is one of the following options: + +- Success, if the command is successfully executed; +- Failure, if the command fails to execute. + + + + + +## 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/Q/T-REC-Q.3718-201810-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3718-201810-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7bd6d8ade0352732aa5dcb2972a4a6bdf7483eaa --- /dev/null +++ b/marked/Q/T-REC-Q.3718-201810-I_PDF-E/raw.md @@ -0,0 +1,968 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3718** + +(10/2018) + +SERIES Q: SWITCHING AND SIGNALLING, AND +ASSOCIATED MEASUREMENTS AND TESTS + +Signalling requirements and protocols for SDN – Resource +control protocols + +--- + +**Signalling requirements of the Sew interface for +virtual data centres** + +Recommendation ITU-T Q.3718 + +# ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 | +| Resource control protocols | Q.3710–Q.3739 | +| Network signalling and signalling requirements for services | Q.3740–Q.3779 | +| TESTING SPECIFICATIONS | Q.3900–Q.4099 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000–Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050–Q.5069 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T Q.3718 + +## Signalling requirements of the Sew interface for virtual data centres + +## Summary + +Recommendation ITU-T Q.3718 focuses on the inter-domain Sew interface which is standardized to allow for multiple control entities within a virtual data centre (VDC). In VDCs, the SDN control entities exchange the control plane related information with each other through the Sew interface. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.3718 | 2018-10-14 | 11 | 11.1002/1000/13699 | + +## Keywords + +Sew, signalling requirement, software-defined networking; virtual data centre, VxLAN + +--- + +\* 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 ..... | 1 | +| 5 Conventions ..... | 2 | +| 6 The Sew interface in VDC..... | 3 | +| 7 The signalling requirements of the Sew interface ..... | 4 | +| 7.1 Overview of signalling requirements ..... | 4 | +| 7.2 Signalling requirements for handshaking..... | 5 | +| 7.3 Signalling requirements for information exchange ..... | 6 | +| 7.4 Signalling requirements for status query ..... | 9 | +| 7.5 Signalling requirements for failure notification ..... | 12 | +| 8 Security considerations ..... | 15 | +| Appendix I – Illustration of the Sew interface in VDC ..... | 16 | +| Bibliography..... | 18 | + + + +## Recommendation ITU-T Q.3718 + +## Signalling requirements of the Sew interface for virtual data centres + +# 1 Scope + +This Recommendation defines signalling requirements between multiple control entities within a virtual data centre. This Recommendation only focuses on the inter-domain Sew interface for multi-vendor interoperability. The signalling exchanged via the Sew interface is mainly related to the VxLAN protocol. + +# 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 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 term defined elsewhere: + +**3.1.1 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.2 Terms defined in this Recommendation + +This Recommendation defines the following term: + +**3.2.1 virtual data centre (VDC)**: A data centre in which the physical resources are abstracted and integrated by using virtualization technology. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|----------------------------------------------| +| CE | Control Entity | +| CO-FA | Control Entity Failure notification | +| CO-FAR | Control Entity Failure notification Response | +| CO-ST | Control Entity Status querying | +| CO-STR | Control Entity Status querying Response | +| ID | Identification | +| DC | Data Centre | +| IP | Internet Protocol | + +| | | +|--------|---------------------------------------| +| KE-AL | Keep Alive | +| KE-ALR | Keep Alive Response | +| MAC | Media Access Control | +| NE | Network Entity | +| NE-FA | NE Failure notification | +| NE-FAR | NE Failure notification Response | +| NE-IQ | NE Information Query | +| NE-IQR | NE Information Query Response | +| NE-EX | NE Information Exchange | +| NE-EXR | NE Information Exchange Response | +| OP-HA | Open Handshaking | +| OP-HAR | Open Handshaking Response | +| SDN | Software-Defined Networking | +| TCP | Transmission Control Protocol | +| TLS | Transport Layer Security | +| UDP | User Datagram Protocol | +| VDC | Virtual Data Centre | +| VM | Virtual Machine | +| VN-FA | VNI Failure notification | +| VN-FAR | VNI Failure notification Response | +| VNI | VXLAN Network Identifier | +| VN-IQ | VNI Information Query | +| VN-IQR | VNI Information Query Response | +| VN-EX | VNI Information Exchange | +| VN-EXR | VNI Information Exchange Response | +| VTEP | VXLAN Tunnel End Point | +| VT-FA | VTEP Failure notification | +| VT-FAR | VTEP Failure notification Response | +| VT-IQ | VTEP Information Query | +| VT-IQR | VTEP Information Query Response | +| VT-EX | VTEP information Exchange | +| VT-EXR | VTEP information Exchange Response | +| VXLAN | Virtual extensible Local Area Network | +| XML | Extensible Markup Language | + +# 5 Conventions + +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. + +In the body of this document and its annexes, the words shall, shall not, should and may sometimes appear, in which case they are to be interpreted, respectively, as is required to, is prohibited from, is recommended and can optionally. The appearance of such phrases or keywords in an appendix or in material explicitly marked as informative are to be interpreted as having no normative intent. + +{A} indicates that the parameter A is mandatory. + +\* indicates that the parameter may be multiple items. + +# 6 The Sew interface in VDC + +![Diagram illustrating the position of the Sew interface in a VDC. It shows two administrative domains, Administrative domain 1 and Administrative domain 2, separated by a dashed line representing the Sew interface. Each domain contains an SDN control entity (CE) connected to a Network entity (NE), which is further connected to multiple Network entities (NE). The Sew interface is shown as a dashed line between the SDN control entities of the two domains.](dbe553cf16dd14073b89a8263a428664_img.jpg) + +The diagram illustrates the hierarchy of network entities within two administrative domains. In Administrative domain 1, an SDN control entity (CE) is connected to a Network entity (NE), which in turn is connected to two Network entities (NE), which are further connected to four Network entities (NE). A similar hierarchy exists in Administrative domain 2. A dashed line labeled 'Sew' connects the SDN control entities of both domains, indicating the inter-domain interface. A small label 'Q.3718(18)\_F6-1' is present in the bottom right corner of the diagram area. + +Diagram illustrating the position of the Sew interface in a VDC. It shows two administrative domains, Administrative domain 1 and Administrative domain 2, separated by a dashed line representing the Sew interface. Each domain contains an SDN control entity (CE) connected to a Network entity (NE), which is further connected to multiple Network entities (NE). The Sew interface is shown as a dashed line between the SDN control entities of the two domains. + +**Figure 6-1 – The position of the Sew interface** + +The Sew interface permits the SDN control entities to interact, either within the same administrative domain (intra-domain), or between administrative domains (inter-domain): + +- The intra-domain Sew interface is typically a single-vendor interface contained within a single-carrier network. Since it is a single-vendor, this interface may contain proprietary elements specifically to that vendor. Therefore, the intra-domain Sew interface is out of the scope of this Recommendation. +- The inter-domain Sew interface is between multiple control entities that cross domain boundaries. The domain boundaries are defined by the carriers and can include administrative boundaries within a carrier's network, boundaries between different vendors within a carrier's network or boundaries between carriers. + +A VDC connects multiple physical DCs together to form a logical DC. However, different physical DCs could be controlled by different SDN control entities. From one DC network element to another DC network element, it is usually necessary to build a large layer 2 network, and VxLAN protocol [b-IETF RFC 7348] is a common solution. + +Therefore, the SDN control entities exchange control plane related information over the Sew interface in a VDC, such as the VXLAN network identifier (VNI) information of VxLAN and the MAC address of network entities (NEs). Also, the NE can be a router, a switch, a server or a virtual machine (VM). + +Through the Sew interface, the SDN control entities firstly establish connections with each other by handshake signalling, then the SDN control entities exchange information including the VXLAN tunnel end point (VTEP), VNI and MAC address of the NE. If there is lack of the information on VTEP, VNI or an NE's MAC address, the SDN control entities can trigger the inquiry process with + +information query signalling. When there is a failure, the SDN control entity will send failure notification signalling to the other SDN control entities in order to refresh the status information. + +# 7 The signalling requirements of the Sew interface + +## 7.1 Overview of signalling requirements + +Among different peer control entities, a handshake shall be made first before exchanging information. After confirming the identification of each other, the control entity should send its own information to each other. + +When any network entity fails, its SDN control entity should notify the peer control entities, for helping the peer control entities to refresh its information accordingly. + +#### Category 1: handshaking + +1-1 Open handshaking message and response message + +1-2 Keep alive message and response message + +### Category 2: information exchange + +2-1 VTEP information exchange message and response message + +2-2 VNI information exchange message and response message + +2-3 NE information exchange message and response message + +#### Category 3: status query + +3-1 VTEP status query message and response message + +3-2 VNI query message and response message + +3-3 NE status query message and response message + +### Category 4: failure notification + +4-1 Control entity failure notification message and response message + +4-2 VTEP failure notification message and response message + +4-3 VNI failure notification message and response message + +4-4 NE failure notification message and response message + +NOTE – No transport protocol for the signalling messages is specified here. No message content format is specified here either. + +The signalling messages may be XML-based messages over (or carried by) TCP, UDP, SCTP, TLS, etc. All of the messages consist of the message header and the message body. + +The message format is described in Figure 7-1 as follows: + +![Diagram of message composition showing a header with four fields: Message type, Message length, Transaction ID, and Message body. The first three fields are grouped as the 'Message header'.](e82162d92ae32bcb22effe6a2d9db4f0_img.jpg) + +| | | | | +|--------------|----------------|----------------|--------------| +| Message type | Message length | Transaction ID | Message body | +|--------------|----------------|----------------|--------------| + +Message header + +Q.3718(18)\_F7-1 + +Diagram of message composition showing a header with four fields: Message type, Message length, Transaction ID, and Message body. The first three fields are grouped as the 'Message header'. + +Figure 7-1 – Message composition + +The message header field contains the following information: + +- 1) Message type: uniquely specifies the type of the message; +- 2) Message length: specifies the length of the message body; + +- 3) Message transaction ID: generated by the sender of the message. If there is a response message for the request message, the transaction IDs of the request and response messages are the same. + +The message body field contains the message content. + +## 7.2 Signalling requirements for handshaking + +#### 7.2.1 Handshaking message and response message + +The handshaking message is defined as the HA-SH message. + +The HA-SH message, indicated by the message type in the message header field, is sent by the SDN control entity to start negotiation with each other and set up a connection for information exchange afterwards. + +Message format: + +``` +< HA-SH Message > ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Hold-time} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Hold-time` indicates the effective time of the HA-SH message. + +The response message to the HA-SH message is defined as the HA-SHR message. + +The HA-SHR message, indicated by the message type in the message header field, is sent by the destination SDN control entity to the source SDN control entity in response to the HA-SH message. + +Message format: + +``` +< HA-SHR Message > ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Result} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Result` shows the handshaking result between the SDN control entities. + +#### 7.2.2 Keep alive message and response message + +The keep alive message is defined as the KE-AL message. This message, indicated by the message type in the message header field, is sent by the SDN control entity after successful handshaking. This message is sent every certain time to keep the connection alive. + +Message format: + +``` + ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Hold-time} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Hold-time` indicates for the destination SDN control entity the maximum waiting time for a response message. + +The response message to the KE-AL message is defined as the KE-ALR message. + +The KE-ALR message, indicated by the message type in the message header field, is sent by the destination SDN control entity to the source SDN control entity in response to the KE-AL message. + +Message format: + +``` +< KE-ALR Message > ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Hold-time} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Hold-time` indicates for the source SDN control entity the maximum waiting time for another KE-AL message. + +## 7.3 Signalling requirements for information exchange + +#### 7.3.1 VTEP information exchange message and response message + +The VTEP information exchange message is defined as the VT-EX message. + +The VT-EX message, indicated by the message type in the message header field, is sent by the SDN control entity to exchange the information of the VTEP. + +Message format: + +``` +< VT-EX Message > ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Local-VTEP-Address} + {Local-VTEP-Information} + {Valid-time} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Local-VTEP-Address` uniquely specifies the VTEP controlled by the source SDN control entity. +- 4) `Local-VTEP-Information` uniquely specifies the information of the VTEP to be exchanged between SDN control entities, including type, capacity, etc. +- 5) `Valid-time` indicates the maximum valid time of the information contained in this message. + +The response message to the VT-EX message is defined as the VT-EXR message. + +The VT-EXR message, indicated by the message type in the message header field, is sent by the destination SDN control entity to the source SDN control entity in response to the VT-EX message. + +Message format: + +``` + ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Result} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Result` shows whether the information is successfully received by the destination SDN control entity. + +#### 7.3.2 VNI information exchange message and response message + +The VNI information exchange message is defined as the VN-EX message. + +The VN-EX message, indicated by the message type in the message header field, is sent by the SDN control entity to exchange the information of the VNI. + +Message format: + +``` +< VNI-EX Message > ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Local-VTEP-Address} + *{Local-VNI-Information} + {Valid-time} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. + +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Local-VTEP-Address` uniquely specifies the VTEP whose VNI information is to be exchanged. +- 4) `Local-VNI-Information` uniquely specifies the information of the local VNI in the local VTEP to be exchanged between SDN control entities, including the VNI and its extensions. There may be one or multiple VNIs in the same message. +- 5) `Valid-time` indicates the maximum valid time of the information contained in this message. + +The response message to the VN-EX message is defined as the VN-EXR message. + +The VN-EXR message, indicated by the message type in the message header field, is sent by the destination SDN control entity to the source SDN control entity in response to the VN-EX message. + +Message format: + +``` + ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Received-VTEP-Address} + {Result} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Received-VTEP-Address` uniquely specifies the VTEP controlled by the source SDN control entity. +- 4) `Result` shows whether the information is successfully received by the destination SDN control entity. + +#### 7.3.3 NE information exchange message and response message + +The NE information exchange message is defined as the NE-EX message. This message indicated by the message type in the message header field, is sent by the source SDN control entity to exchange the information of the local NEs. + +Message format: + +``` + ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Local-VNI} + *{Local-NE-Information} + {Valid-time} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. + +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Local-VNI` uniquely specifies the local VNI. +- 4) `Local-NE-Information` uniquely specifies the information of the NE associated with the local VNI, including MAC address, type of the NE, etc. There may be one or multiple values for an NE in the same message. +- 5) `Valid-time` indicates the maximum valid time of the information contained in this message. + +The response message to the NE-EX message is defined as the NE-EXR message. + +The NE-EXR message, indicated by the message type in the message header field, is sent by the destination SDN control entity to the source SDN control entity in response to the NE-EX message. + +Message format: + +``` +< NE-EXR Message > ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Received-VNI} + {Result} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Received-VNI` uniquely specifies the received VNI controlled by the source SDN control entity. +- 4) `Result` shows the results whether information is successfully received by the destination SDN control entity. + +## 7.4 Signalling requirements for status query + +#### 7.4.1 VTEP status query message and response message + +The VTEP status query message is defined as the VT-IQ message. This message indicated by the message type in the message header field, is sent by the source SDN control entity to query the VTEP status controlled by the destination SDN control entity. + +Message format: + +``` +< VT-IQ Message > ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Query-VTEP-Address} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. + +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Query-VTEP-Address` uniquely specifies the VTEP address which the source SDN control entity wants to query. + +The response message to the VT-IQ message is defined as the VT-IQR message. + +The VT-IQR message, indicated by the message type in the message header field, is sent by the destination SDN control entity to the source SDN control entity in response to the VT-IQ message. + +Message format: + +``` + ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Queried-VTEP-Address} + {Status} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Queried-VTEP-Address` uniquely specifies the VTEP which the source SDN control entity wants to query. +- 4) `Status` specifies the status of the VTEP. + +#### 7.4.2 VNI query message and response message + +The VNI query message is defined as the VN-IQ message. This message indicated by the message type in the message header field, is sent by the source SDN control entity to query the VNI which belongs to the destination SDN control entity. + +Message format: + +``` + ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Query-VNI} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Query-VNI` uniquely specifies the VNI which the source SDN control entity wants to query. + +The response message to the VN-IQ message is defined as the VN-IQR message. + +The VN-IQR message, indicated by the message type in the message header field, is sent by the destination SDN control entity to the source SDN control entity in response to the VN-IQ message. + +Message format: + +``` + ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Query-VNI} + {VNI-Information} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Query-VNI` uniquely specifies the VNI which the source SDN control entity wants to query. +- 4) `VNI-Information` defines the information of the VNI, including the VNI and its extensions. + +#### 7.4.3 NE status query message and response message + +The NE status query message is defined as the NE-IQT message. This message indicated by the message type in the message header field, is sent by the source SDN control entity to query the NE status controlled by the destination SDN control entity. + +Message format: + +``` + ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Query-VNI} + {Query-NE-Address} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Query-VNI` uniquely specifies the VNI associated with the NE which the source SDN control entity wants to query. +- 4) `Query-NE-Address` uniquely specifies the NE associated with the queried VNI. + +The response message to the NE-IQ message is defined as the NE-IQR message. + +The NE-IQR message, indicated by the message type in the message header field, is sent by the destination SDN control entity to the source SDN control entity in response to the NE-IQ message. + +Message format: + +``` + ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} +``` + +``` +{Queried-VNI} +{Queried-NE-Address} +{Status} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Queried-VNI` uniquely specifies the VNI with which the NE is associated is queried. +- 4) `Queried-NE-Address` uniquely specifies the NE which the source SDN control entity wants to query. +- 5) `Status` defines the status of the NE. + +## 7.5 Signalling requirements for failure notification + +#### 7.5.1 Control entity failure notification message and response message + +The control entity failure notification message is defined as the CO-FA message. + +The CO-FA message, indicated by the message type in the message header field, is sent by the source SDN control entity to notify the failure to the destination SDN control entity. + +Message format: + +``` + ::= < Message header > +{Destination-SDN-Control-Entity-Address} +{Source-SDN-Control-Entity-Address} +{Failure} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Failure` defines the failure event of the source SDN control entity. + +The response message to the CO-FA message is defined as the CO-FAR message. + +The CO-FAR message, indicated by the message type in the message header field, is sent by the destination SDN control entity to the source SDN control entity in response to the CO-FA message. + +Message format: + +``` + ::= < Message header > +{Destination-SDN-Control-Entity-Address} +{Source-SDN-Control-Entity-Address} +{Result} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. + +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Result` shows whether the failure notification is correctly received by the destination SDN control entity. + +#### 7.5.2 VTEP failure notification message and response message + +The VTEP failure notification message is defined as the VT-FA message. + +The VT-FA message, indicated by the message type in the message header field, is sent by the source SDN control entity to notify the failure of its VTEP to the destination SDN control entity. + +Message format: + +``` + ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Local-VTEP-Address} + {Failure} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Local-VTEP-Address` uniquely specifies the VTEP in error. +- 4) `Failure` defines the failure event of the VTEP. + +The response message to the VT-FA message is defined as the VT-FAR message. + +The VT-FAR message, indicated by the message type in the message header field, is sent by the destination SDN control entity to the source SDN control entity in response to the VT-FA message. + +Message format: + +``` + ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Received-VTEP-Address} + {Result} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Received-VTEP-Address` uniquely specifies the VTEP received through the ST-FA message. +- 4) `Result` shows whether the failure notification is correctly received by the destination SDN control entity. + +#### 7.5.3 VNI failure notification message and response message + +The VNI failure notification message is defined as the VN-FA message. + +The VN-FA message, indicated by the message type in the message header field, is sent by the source SDN control entity to notify the failure of its VNI to the destination SDN control entity. + +Message format: + +``` + ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Local-VNI} + {Failure} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Local-VNI` uniquely specifies the VNI in error. +- 4) `Failure` defines the failure event of the VNI. + +The response message to the VN-FA message is defined as the VN-FAR message. + +The VN-FAR message, indicated by the message type in the message header field, is sent by the destination SDN control entity to the source SDN control entity in response to the VN-FA message. + +Message format: + +``` + ::= < Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Received-VNI} + {Result} +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Received-VNI` uniquely specifies the VNI received through the VN-FA message. +- 4) `Result` shows whether the failure notification is correctly received by the destination SDN control entity. + +#### 7.5.4 NE failure notification message and response message + +The NE failure notification message is defined as the NE-FA message. + +The NE-FA message, indicated by the message type in the message header field, is sent by the source SDN control entity to notify the failure of the NE to the destination SDN control entity. + +Message format: + +``` + + ::=< Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Local-VNI} + {Local-NE-Address} + {Failure} + +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Local-VNI` uniquely specifies the VNI with which the NE is associated. +- 4) `Local-NE-Address` uniquely specifies the NE in error. +- 5) `Failure` defines the failure event of the NE. + +The response message to the NE-FA message is defined as the NE-FAR message. + +The NE-FAR message, indicated by the message type in the message header field, is sent by the destination SDN control entity to the source SDN control entity in response to the NE-FA message. + +Message format: + +``` + + ::=< Message header > + {Destination-SDN-Control-Entity-Address} + {Source-SDN-Control-Entity-Address} + {Received-VNI} + {Received-NE} + {Result} + +``` + +Meanings and explanations: + +- 1) `Destination-SDN-Control-Entity-Address` uniquely specifies the destination SDN control entity address. +- 2) `Source-SDN-Control-Entity-Address` uniquely specifies the source SDN control entity address. +- 3) `Received-VNI` uniquely specifies the VNI received through the NE-FA message. +- 4) `Received-NE` uniquely specifies the NE received through the NE-FA message. +- 5) `Result` shows whether the failure notification is correctly received by the destination SDN control entity. + +# 8 Security considerations + +The SDN control entities within the same administrative domain (intra-domain), or between administrative domains (inter-domain) exchange information via the Sew interface in VDCs. When the SDN control entities are in different administrative domains, it is necessary to confirm the peer's validation in a safe way, which is similar to other SDN scenarios defined in [ITU-T Y.3300]. This Recommendation does not introduce any new security issues. + +# Appendix I + +### Illustration of the Sew interface in VDC + +(This appendix does not form an integral part of this Recommendation.) + +To construct a VDC, VxLAN is a common solution. VxLAN is a network virtualization technology that attempts to improve the scalability problems associated with large cloud computing deployments. It uses a VLAN-like encapsulation technique to encapsulate MAC-based OSI layer 2 Ethernet frames within layer 4 UDP packets, using 4789 as the default IANA-assigned destination UDP port number. + +In VxLAN, the VNI is a 24-bit segment ID for identifying the different VxLAN segment. Only NEs within the same VxLAN segment can communicate with each other. Due to the VxLAN encapsulation, VxLAN uses stateless tunnels to build overlay layer 2 networks on top of layer 3 networks. The end point of the tunnel is a VTEP. + +VxLAN does not keep a long connection between the NEs, so the VxLAN needs a control plane to record whether the NEs are reachable. The control plane has a mapping table including a VTEP IP, VNI, NE MAC, etc. Like VLAN, VTEPs do not exchange their mapping tables periodically, so for the unknown MAC address, VxLAN must use a multicast or SDN control entity to get the path information. + +Therefore, in a VDC scenario, the SDN control entity should configure and maintain the mapping tables of all VTEPs for VxLAN. + +![Diagram of one SDN control entity in a VDC showing two VTEPs connected to a central SDN control entity, each with its own mapping table and connected NEs.](90ddf538ef276510e2b631f7b96654e6_img.jpg) + +The diagram illustrates a network architecture with a central 'SDN control entity' at the top. Below it are two 'VTEP' boxes, 'VTEP 1' and 'VTEP 2', connected by a horizontal line. Each VTEP is connected to three 'NE' (Network Element) boxes below it. To the left of 'VTEP 1' is a 'Mapping table' with three columns: 'VNI', 'NE MAC', and 'VTEP IP'. To the right of 'VTEP 2' is an identical 'Mapping table'. Dashed lines connect the 'SDN control entity' to both mapping tables. A label 'Q.3718(18)\_FI.1' is in the bottom right corner. + +Diagram of one SDN control entity in a VDC showing two VTEPs connected to a central SDN control entity, each with its own mapping table and connected NEs. + +Figure I.1 – One SDN control entity in a VDC + +![Sequence diagram showing the MAC address learning procedures involving an NE, VTEP 1, VTEP 2, and the SDN control entity.](627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg) + +The diagram shows a sequence of three messages between four entities: 'NE', 'VTEP 1', 'VTEP 2', and 'SDN control entity'. 1. An arrow labeled '①' goes from 'NE' to 'VTEP 1'. 2. An arrow labeled '②' goes from 'VTEP 1' to 'SDN control entity'. 3. An arrow labeled '③' goes from 'SDN control entity' to 'VTEP 2'. A label 'Q.3718(18)\_FI.2' is in the bottom right corner. + +Sequence diagram showing the MAC address learning procedures involving an NE, VTEP 1, VTEP 2, and the SDN control entity. + +Figure I.2 – The MAC address learning procedures of one SDN control entity in a VDC + +The detailed procedures are presented below: + +- ① The NE sends its MAC address to VTEP 1. +- ② VTEP 1 send the MAC address and the VNI information to the SDN control entity. +- ③ The SDN control entity sends the final mapping table to VTEP 2. + +But in a multiple control entities' scenario, for example, between administrative boundaries within a carrier's network, the different control entities must exchange their VTEPs' status, mapping tables, + +etc. The inter-domain Sew interface between the SDN control entities in different sites of a VDC is required. + +![Diagram of two SDN control entities in a VDC (Figure I.3).](365b54f616aff249b4e6c0edafdcb9b3_img.jpg) + +The diagram illustrates the architecture of two SDN control entities within a Virtual Data Center (VDC). SDN control entity 1 and SDN control entity 2 are connected via a dashed line labeled 'Sew'. SDN control entity 1 is connected to VTEP 1, which manages three Network Elements (NE). Similarly, SDN control entity 2 is connected to VTEP 2, which manages three NEs. VTEP 1 and VTEP 2 are interconnected. Each VTEP has an associated mapping table: + +| VNI | NE MAC | VTEP IP | +|-----|--------|---------| +| VNI | NE MAC | VTEP IP | +| VNI | NE MAC | VTEP IP | + +Diagram of two SDN control entities in a VDC (Figure I.3). + +Q.3718(18)\_FI.3 + +**Figure I.3 – Two SDN control entities in a VDC** + +![Sequence diagram of MAC address learning procedures (Figure I.4).](844077b3034f0030b404207db0ad76b4_img.jpg) + +``` + +sequenceDiagram + participant NE + participant VTEP 1 + participant VTEP 2 + participant SDN control entity 1 + participant SDN control entity 2 + Note over NE, VTEP 1: ① + NE->>VTEP 1: MAC address + Note over VTEP 1, SDN control entity 1: ② + VTEP 1->>SDN control entity 1: MAC address & VNI + Note over SDN control entity 1, SDN control entity 2: ③ + SDN control entity 1->>SDN control entity 2: Mapping table exchange + Note over SDN control entity 2, VTEP 2: ④ + SDN control entity 2->>VTEP 2: Final mapping table + +``` + +Sequence diagram of MAC address learning procedures (Figure I.4). + +Q.3718(18)\_FI.4 + +**Figure I.4 – The MAC address learning procedures of two SDN control entities in a VDC** + +The detailed procedures are presented below: + +- ① The VM sends its MAC address to VTEP1. +- ② VTEP1 sends the MAC address and the VNI information to SDN control entity 1. +- ③ SDN control entity 1 exchanges a mapping table with SDN control entity 2 through the inter-domain Sew interface. +- ④ SDN control entity 2 sends the final mapping table of VTEP 1 to VTEP 2. + +## Bibliography + +- [b-IETF RFC 7348] IETF RFC 7348 (2014), *Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks.* +- [b-ITU-T Q.Supp1.67] Supplement ITU-T Q.Supp1.67 (2015), *Framework of signalling for software-defined networking.* + + + +## 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/Q/T-REC-Q.3719-201912-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3719-201912-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6ccb62360c6191974b5e8bdcc241c1f9270ec98f --- /dev/null +++ b/marked/Q/T-REC-Q.3719-201912-I_PDF-E/raw.md @@ -0,0 +1,558 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3719** + +(12/2019) + +SERIES Q: SWITCHING AND SIGNALLING, AND +ASSOCIATED MEASUREMENTS AND TESTS + +Signalling requirements and protocols for SDN – Resource +control protocols + +--- + +**Signalling requirements for the separation of +control plane and user plane in a virtualized +broadband network gateway (vBNG)** + +Recommendation ITU-T Q.3719 + +# ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 | +| Resource control protocols | Q.3710–Q.3739 | +| Network signalling and signalling requirements for services | Q.3740–Q.3779 | +| TESTING SPECIFICATIONS | Q.3900–Q.4099 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000–Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050–Q.5069 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T Q.3719 + +# Signalling requirements for the separation of control plane and user plane in a virtualized broadband network gateway (vBNG) + +## Summary + +Recommendation ITU-T Q.3719 specifies architecture, signalling requirements and information flows for the separation of control plane and user plane in a virtualized broadband network gateway (vBNG). + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.3719 | 2019-12-14 | 11 | 11.1002/1000/14144 | + +## Keywords + +Control plane, user plane, vBNG. + +--- + +\* 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 Architecture for control plane and user plane separated vBNG | 3 | +| 7 Signalling requirements for the separation of control plane and user plane | 4 | +| 7.1 Interfaces between the vBNG-CP and the vBNG-UP | 4 | +| 7.2 General requirements | 5 | +| 7.3 Signalling requirement of service interface | 6 | +| 7.4 Signalling requirement of control interface | 6 | +| 7.5 Signalling requirement of management interface | 7 | +| 8 Information flows | 7 | +| 8.1 PPPoE process flow | 7 | +| 8.2 IPoE process flow | 8 | +| 8.3 User plane resource reporting | 9 | +| 8.4 CGN process flow | 9 | +| Appendix I – The deployment scenario of vBNG | 11 | + + + +## Recommendation ITU-T Q.3719 + +## Signalling requirements for the separation of control plane and user plane in a virtualized broadband network gateway (vBNG) + +# 1 Scope + +This Recommendation describes the architecture, signalling requirements and information flows for implementation of the separation of control plane and user plane in a virtualized broadband network gateway (vBNG). + +# 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 Y.3300] Recommendation ITU-T Y.3300 (2014), *Framework of software-defined networking*. +- [ITU-T Q.3315] Recommendation ITU-T Q.3315 (2015), *Signalling requirements for flexible network service combination on broadband network gateway*. +- [ITU-T Q.3715] Recommendation ITU-T Q.3715 (2018), *Signalling requirements for dynamic bandwidth adjustment on demand on broadband network gateway implemented by software-defined networking technologies*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 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.2 broadband network gateway (BNG)** [ITU-T Q.3315]: The access point to the provider's IP network for wireline broadband services. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 vBNG control plane (vBNG-CP)**: The virtualized broadband network gateway (vBNG) control plane is in charge of the control functions, including authentication, authorization and accounting (AAA) management function, IP address management function, user management function, access protocol processing function, and vBNG user plane management function, etc. The vBNG control plane is implemented using virtualization technologies and is deployed in the mode of centralization. + +**3.2.2 vBNG user plane (vBNG-UP):** The virtualized broadband network gateway (vBNG) user plane mainly provides user packets switching under the instruction of the vBNG control plane. The vBNG user plane can be implemented in different types of forwarding hardware, including NP-based dedicated equipment, ASIC-based dedicated equipment, or X86-based commercial equipment. + +**3.2.3 virtualized BNG (vBNG):** The virtualized BNG is the broadband network gateway of which all features or some features are directly implemented as virtualized network function(s) (VNF) running on the network function virtualization infrastructure (NFVI). It is used to either augment or replace the existing traditional BNG. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|------------------------------------------------| +| AAA | Authentication, Authorization and Accounting | +| ACL | Access Control List | +| ASIC | Application Specific Integrated Circuit | +| BNG | Broadband Network Gateway | +| CGN | Carrier Grade Network address translation | +| CHAP | Challenge Handshake Authentication Protocol | +| CP | Control Plane | +| DHCP | Dynamic Host Configuration Protocol | +| DPDK | Data Plane Development Kit | +| FPGA | Field Programmable Gate Array | +| GRE | Generic Routing Encapsulation | +| ID | Identifier | +| IPCP | Internet Protocol Control Protocol | +| IPoE | Internet Protocol over Ethernet | +| MAC | Media Access Control | +| MPLS | Multi-Protocol Label Switching | +| NAT | Network Address Translation | +| NFVI | Network Function Virtualization Infrastructure | +| NP | Network Process | +| NIC | Network Interface Controller | +| PADI | PPPoE Active Discovery Initiation | +| PADO | PPPoE Active Discovery Offer | +| PADR | PPPoE Active Discovery Request | +| PADS | PPPoE Active Discovery Session-confirmation | +| PPPoE | Point-to-Point Protocol over Ethernet | +| QoS | Quality of Service | +| SR-IOV | Single Root I/O Virtualization | + +| | | +|---------|-----------------------------------------------------| +| UP | User Plane | +| vBNG | Virtualized Broadband Network Gateway | +| vBNG-CP | Virtualized Broadband Network Gateway Control Plane | +| vBNG-UP | Virtualized Broadband Network Gateway User Plane | +| VLAN | Virtual Local Area Network | +| VNF | Virtualized Network Function | +| VxLAN | Virtual Extensible Local Area Network | + +# 5 Conventions + +None. + +# 6 Architecture for control plane and user plane separated vBNG + +There are two main functions in a traditional broadband network gateway (BNG), the user access management function, and the user data routing and forwarding function. While in a virtualized broadband network gateway (vBNG), it has been found that separating these two functions can make a difference. Actually, the user management function of traditional a BNG can be centrally deployed in the form of a concentrated virtualized network function (VNF) or modules or a device, which can be called a vBNG control plane (vBNG-CP). The reserved functions such as routing and forwarding function can be deployed in the form of a vBNG user plane (vBNG-UP). + +The architecture for a control plane and user plane separated vBNG is shown in Figure 6-1. + +![Figure 6-1: Architecture for control plane and user plane separated vBNG. The diagram shows a central vBNG-CP (Control Plane) and vBNG-UP (User Plane) block. The vBNG-CP contains five functional blocks: AAA management function, IP address management function, User management function, Access protocol processing function, and vBNG-U management function. The vBNG-UP contains three functional blocks: X86, NP, and ASIC. External components include AAA server, DHCP server, and OSS. The OSS is connected to a Management and orchestration block, which is also connected to the vBNG-CP and vBNG-UP. The AAA server and DHCP server are connected to the vBNG-CP. The vBNG-CP and vBNG-UP are connected to each other and to the Management and orchestration block.](dbe553cf16dd14073b89a8263a428664_img.jpg) + +Figure 6-1: Architecture for control plane and user plane separated vBNG. The diagram shows a central vBNG-CP (Control Plane) and vBNG-UP (User Plane) block. The vBNG-CP contains five functional blocks: AAA management function, IP address management function, User management function, Access protocol processing function, and vBNG-U management function. The vBNG-UP contains three functional blocks: X86, NP, and ASIC. External components include AAA server, DHCP server, and OSS. The OSS is connected to a Management and orchestration block, which is also connected to the vBNG-CP and vBNG-UP. The AAA server and DHCP server are connected to the vBNG-CP. The vBNG-CP and vBNG-UP are connected to each other and to the Management and orchestration block. + +Q.3719(19)\_F6-1 + +**Figure 6-1 – Architecture for control plane and user plane separated vBNG** + +The vBNG is separated into two main components, the control plane (CP) and the user plane (UP): + +- vBNG-CP, which is the control plane of the vBNG. + +The vBNG control plane could be implemented using virtualization technologies and deployed in the mode of centralization, which consists of main control functions, e.g., AAA management function, IP address management function, user management function, access protocol processing function, and vBNG-UP management function. The functional components of the vBNG control plane can be implemented in the form of VNFs and hosted in a network function virtualization infrastructure (NFVI). + +- vBNG-UP, which is the user plane of the vBNG + +The vBNG-UP mainly provides user packets switching under the instruction of the vBNG-CP. The vBNG-UP can be implemented in different types of forwarding hardware, including NP-based dedicated equipment, ASIC-based dedicated equipment, or X86-based commercial equipment, etc. For the X86-based vBNG-UP, in order to improve its forwarding performance, acceleration technologies can be used, e.g., DPDK, SR-IOV, ASIC or FPGA-based smart NIC, etc. + +The details of the vBNG functional components are described as follows: + +The vBNG control plane should support: + +- (1) IP address management function: managing the unified IP address pool. +- (2) AAA management function: implementing the AAA function for access users by cooperating with the AAA server. +- (3) User management function: managing user information and forwarding policy. +- (4) Access protocol processing function: handling protocol packets accessed by users via point-to-point protocol over Ethernet (PPPoE)/Internet protocol over Ethernet (IPoE) or PPPoE/IPoE. +- (5) vBNG-UP management function: managing the interface status of the vBNG-UP, and the setup, deletion, maintenance of channels between the vBNG-CP and the vBNG-UP. +- (6) the vBNG-CP should also support the unicast routing, multicast routing and multi-protocol label switching (MPLS) protocol, etc. + +The vBNG user plane should support traffic forwarding, quality of service (QoS) and traffic statistics collection. + +# 7 Signalling requirements for the separation of control plane and user plane + +## 7.1 Interfaces between the vBNG-CP and the vBNG-UP + +Several interfaces are defined to support the communication between the vBNG-CP and the vBNG-UP. Figure 7-1 illustrates the interfaces of the separation of control plane and user plane in vBNG. + +![Diagram showing the separation of control plane (vBNG-CP) and user plane (vBNG-UP) in vBNG. The vBNG-CP is a yellow rectangle at the top, and the vBNG-UP is an orange rectangle at the bottom. Three vertical lines connect them, labeled from left to right: 'Service interface', 'Control interface', and 'Manage interface'. Below the diagram is the text 'Q.3719(19)_F7-1'.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) + +Diagram showing the separation of control plane (vBNG-CP) and user plane (vBNG-UP) in vBNG. The vBNG-CP is a yellow rectangle at the top, and the vBNG-UP is an orange rectangle at the bottom. Three vertical lines connect them, labeled from left to right: 'Service interface', 'Control interface', and 'Manage interface'. Below the diagram is the text 'Q.3719(19)\_F7-1'. + +**Figure 7-1 – Interfaces of control plane and user plane separated vBNG** + +**Service interface:** The vBNG-CP and the vBNG-UP use this interface to establish tunnels with each other and transmit access protocol (PPPoE and IPoE) packets over the tunnels. This interface may run network virtualization technology protocols such as generic routing encapsulation (GRE) or virtual extensible local area network (VxLAN), etc. + +**Control interface:** The vBNG-CP uses this interface to deliver routing information and forwarding policies, and the vBNG-UP uses this interface to report user plane events to the vBNG-CP. + +**Management interface:** The vBNG-CP uses this interface to deliver configuration parameters to the vBNG-UP. This interface may run Netconf protocol. + +## 7.2 General requirements + +This clause specifies some of the general requirements that the protocol used for the separation of control plane and user plane should support. + +#### 7.2.1 CU separation protocol and flow table + +The control plane and user plane separation (CU separation) protocol must allow the vBNG-CP to send forwarding tables to each user plane device. The CU separation protocol should be lightweight to achieve high performance. The CU separation protocol should support batch processing capabilities to provide centralized session management, user management capabilities and high scalability, as well as cost-effective redundancy. The CU separation protocol should be able to deliver commands to the vBNG-UP devices in an ordered group of packets. Each set of commands should be sent to the vBNG-UP with as few messages as possible. In addition, the protocol must support the ability to specify whether the command group must have "all or nothing" semantics. The CU separation protocol should be able to support enough vBNG-UP devices and ports. For example, the size of protocol field corresponding to the vBNG-UP or port numbers shall be large enough to support the minimum required numbers. This requirement does not affect system performance when the number of vBNG-UPs or ports in the system increases. + +#### 7.2.2 Message priority + +In CU separation vBNG, the protocol between the vBNG-CP and the vBNG-UPs should provide a means of indicating the priority of the protocol message. + +#### 7.2.3 Keep alive + +In CU separation vBNG, the heartbeat is generated to indicate normal operation and to synchronize the vBNG-CP and vBNG-UPs, which is sent between the vBNG-CP and vBNG-UPs at a regular interval in the order of seconds. If the vBNG-CP or the vBNG-UP does not receive a heartbeat for a time, usually a few heartbeats intervals, it is assumed to have a fault. + +The CU separation protocol should support heartbeat monitor mechanism, and this mechanism should have ability to distinguish whether the interruption is an actual failure. For example, in some scenarios (i.e., the vBNG-CP and the vBNG-UP upgrade, etc.), the connection between the vBNG-UP and the vBNG-CP need to be interrupted. In this case, the interruption should not be notified. + +#### 7.2.4 Version compatibility + +The CU separated vBNG may include devices from different vendors when deployed in a carrier network. Since devices from different vendors may implement different versions of the protocol, the CU separation protocol should provide some mechanism to perform version compatibility. The version compatibility is the process by which the control plane of the CU separated vBNG is used to evaluate the protocol versions supported by the control plane and user plane devices. Then the CU separated vBNG selects the appropriate protocol version to communicate. This process is "negotiating" because it needs to identify the latest protocol version supported by both the control plane and the user plane device. + +#### 7.2.5 Capability exchange + +The CU separation vBNG should provide some mechanism to exchange the functionality of the vBNG-UP, for example, display device configuration files, service functions and other assigned functions in CU separated vBNG. + +#### **7.2.6 vBNG-UP event notification** + +The vBNG-UP should be able to report the events occurring on the vBNG-UP asynchronously to the vBNG-CP, such as faults and changes in available resources and functions. + +#### **7.2.7 High availability** + +vBNG-CP and vBNG-UP are key components, and some redundancy should be used for reliability. The vBNG-CP should support single instance reliability and multi-instance remote disaster recovery reliability. vBNG-DP should support 1 + 1/1:1 hot spare requirements and N:1 hot spare requirements. The channel between vBNG-CP and vBNG-DP should also support higher reliability. + +The CU separated vBNG network requires an alternate vBNG-CP for disaster recovery. And some mechanisms should be provided to implement the backup vBNG-CP: a) In some cases, there may be two vBNG-CPs that declare the primary vBNG-CP, which should be supported or associated to determine which vBNG-CP is the primary device. b) It shall support switching between the primary vBNG-CP and the standby vBNG-CP when the primary vBNG-CP is disconnected. + +#### **7.2.8 Security** + +The vBNG-CP can send some information tables to the vBNG-UP, which may be critical to network functions (e.g., user information, IPv4/IPv6 information), and can reflect business information (e.g., QoS, service level agreements, etc.). Therefore, it should be supported to ensure the integrity of all CU separation protocol messages and to prevent man-in-the-middle attacks. + +## **7.3 Signalling requirement of service interface** + +Service interface is used to transmitting PPPoE/IPoE dialup packets between user plane and control plane. For user access authentication, the vBNG-CP need to know which port of the vBNG-UP the user is connected to for the authentication at access location because a specific user is only permitted to access on specific port/location. The necessary information includes node ID, slot ID, sub-card ID, port ID and so on. The access port information should be carried in transmit tunnel encapsulated by vBNG-UP. + +## **7.4 Signalling requirement of control interface** + +The vBNG-CP uses this interface to deliver service entries, and the vBNG-UP uses this interface to report service events to the vBNG-CP. When users access to the broadband network, the control plane solicits these users' information (such as user's ID, user's MAC, user's access methods, for example via PPPoE/IPoE), associates them with available bandwidth which are reported by user planes, and based on the service requirement to generate a set of tables, which may include user's information, vBNG-UP's IP address pool, and QoS, etc. Then the control plane can transmit these tables to the user planes. User planes receive these tables, analyse them, match the corresponding rules, and then perform the corresponding actions. + +The following items should be included in the tables delivered from the vBNG-CP to the vBNG-UP, + +- a) Interface information accessed by the user, +- b) Virtual local area network (VLAN) information accessed by the user, +- c) user's MAC address, +- d) user's IP address, +- e) QoS information authorized to the user, +- f) some attributes of the user customized by the vendor, such as access control list (ACL), policy routing, and so on. + +## **7.5 Signalling requirement of management interface** + +The management interface between the vBNG-CP and the vBNG-UP is mainly used for service configuration and information query. The service configurations delivered from the vBNG-CP to the vBNG-UP mainly include: + +- 1) vBNG service interface configuration + - (1) BNG sub-interface and VLAN configuration; + - (2) BNG interface enable configuration; +- 2) vBNG business policy template configuration + - (1) QoS template configuration; + - (2) ACL template configuration; +- 3) vBNG service control channel configuration + - (1) Control channel configuration; + - (2) Service channel configuration. + +# **8 Information flows** + +## **8.1 PPPoE process flow** + +Figure 8-1 shows the PPPoE process flow. In the scenario where the vBNG control plane and the user plane are separated, the processes of a PPPoE home user accessing the Internet are according to the following flows: + +- (1) User dialup packets via PPPoE from a UP that will be send to the CP from the UP's service interface. +- (2) CP processes the dialup packet. Confirming with the AAA, CP makes the decision to permit or deny the dial by means of authentication. +- (3) After that, the CP tells the UP to do the corresponding forwarding actions with related policies. +- (4) If the user is authenticated and permitted, the UP forwards the traffic into the Internet with related policies such as limited bandwidth, etc. Otherwise, the user is denied to access the Internet. + +![Sequence diagram of PPPoE process flow between User, UP, CP, and AAA. The diagram shows the exchange of PPOE PADI, PADO, PADR, PADS, CHAP challenge/response/success, and IPCP messages, with some messages being tunneled between UP and CP. The CP interacts with the AAA for authentication and with the Internet for data forwarding.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +sequenceDiagram + participant User + participant UP + participant CP + participant AAA + Note right of CP: Internet + + User->>UP: PPOE PADI + UP->>CP: PPOE PADI in tunnel + CP->>AAA: Access request + AAA-->>CP: Access accept + CP->>UP: PPOE PADO in tunnel + UP-->>User: PPOE PADO + User->>UP: PPOE PADR + UP->>CP: PPOE PADR in tunnel + CP->>AAA: Access request + AAA-->>CP: Access accept + CP->>UP: PPOE PADS in tunnel + UP-->>User: PPOE PADS + User->>UP: CHAP challenge + UP->>CP: CHAP challenge in tunnel + CP->>AAA: Access request + AAA-->>CP: Access accept + CP->>UP: CHAP response in tunnel + UP-->>User: CHAP response + User->>UP: CHAP success + UP->>CP: CHAP success in tunnel + CP->>AAA: Access request + AAA-->>CP: Access accept + CP->>UP: IPCP in tunnel + UP-->>User: IPCP + CP->>UP: Set forwarding entries on UP + User->>UP: User data in PPPoE + UP->>Internet: User data + +``` + +Q.3719(19)\_F8-1 + +Sequence diagram of PPPoE process flow between User, UP, CP, and AAA. The diagram shows the exchange of PPOE PADI, PADO, PADR, PADS, CHAP challenge/response/success, and IPCP messages, with some messages being tunneled between UP and CP. The CP interacts with the AAA for authentication and with the Internet for data forwarding. + +**Figure 8-1 – PPPoE process flow** + +## 8.2 IPoE process flow + +Figure 8-2 shows the IPoE process flow. In the scenario where the vBNG control plane and the user plane are separated, the processes of an IPoE home user accessing the Internet are according to the following flows: + +- (1) User dialup packets via IPoE from UP that will be sent to the CP from a UP's service interface. +- (2) The CP processes the dialup packet. Confirming with the AAA, the CP makes the decision to permit or deny the dial by means of authentication. +- (3) After that, the CP tells the UP to do the corresponding forwarding actions with related policies. +- (4) If the user is authenticated and permitted, the UP forwards the traffic into the Internet with related policies. + +![Sequence diagram of the IPoE process flow involving User, UP, CP, and Radius entities.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +``` + +sequenceDiagram + participant User + participant UP + participant CP + participant Radius + + User->>UP: DHCP discovery + UP->>CP: DHCP discovery in VXLAN-GPE + CP->>Radius: Access request + Radius-->>CP: Access accept + CP-->>UP: DHCP offer in VXLAN-GPE + UP-->>User: DHCP offer + User->>UP: DHCP request + UP->>CP: DHCP request in VXLAN-GPE + CP-->>UP: DHCP ACK in VXLAN-GPE + UP-->>User: DHCP ACK + CP-->>UP: Set forwarding entries on UP + User->>UP: User data in IPoE + UP->>CP: User data + Note right of CP: Internet + +``` + +Q.3719(19)\_F8-2 + +Sequence diagram of the IPoE process flow involving User, UP, CP, and Radius entities. + +**Figure 8-2 – IPoE process flow** + +## 8.3 User plane resource reporting + +After the completion of the control plane and a user plane established in a session, the user plane reports the information of the boards and access side interfaces on this user plane to the control plane as shown in following Figure 8-3. + +![Sequence diagram of the forwarding plane resource reporting between UP and CP entities.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +``` + +sequenceDiagram + participant UP + participant CP + + UP->>CP: Report board resource to CP + CP-->>UP: ACK + UP->>CP: Report interface resource to CP + CP-->>UP: ACK + +``` + +Q.3719(19)\_F8-3 + +Sequence diagram of the forwarding plane resource reporting between UP and CP entities. + +**Figure 8-3 – Forwarding plane resource reporting** + +## 8.4 CGN process flow + +Figure 8-4 shows CGN process flow. In the scenario where the vBNG control plane and the user plane are separated, the processes of a user with carrier grade network address translation (CGN) mode accessing the Internet are according to the following flows: + +- (1) The first step is that the CP allocates one or more CGN address blocks to the UP +- (2) Next step is a user access process of the CGN mode; +- (3) The UP will report the network address translation (NAT) information to the CP when a CGN session is created. + +![Sequence diagram showing the CGN process flow between CPE, UP, CP, Radius, and Internet entities.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +``` + +sequenceDiagram + participant CPE + participant UP + participant CP + participant Radius + participant Internet + + Note right of UP: Public address block allocation request + UP-->CP: Public address block allocation request + CP-->UP: Public address block allocation response + CPE->>UP: Access request + UP->>CP: Access request + CP->>Radius: Access request + Radius-->>CP: Access accept + CP-->>UP: Access accept + UP-->>CPE: Access accept + UP-->>CP: User session request + CP-->>UP: User session response + UP-->>Internet: + Internet-->>CPE: + +``` + +The diagram illustrates the CGN process flow. It begins with the UP (User Plane) sending a 'Public address block allocation request' to the CP (Control Plane), which receives a 'Public address block allocation response'. Next, the CPE (Customer Premises Equipment) sends an 'Access request' to the UP, which is forwarded by the UP to the CP, and then by the CP to the Radius server. The Radius server returns an 'Access accept' to the CP, which is then passed back through the UP to the CPE. Following this, the UP sends a 'User session request' to the CP, which receives a 'User session response'. Finally, the UP establishes a connection to the Internet, which in turn connects back to the CPE. + +Q.3719(19)\_F8-4 + +Sequence diagram showing the CGN process flow between CPE, UP, CP, Radius, and Internet entities. + +**Figure 8-4 – CGN process flow** + +# Appendix I + +## The deployment scenario of vBNG + +(This appendix does not form an integral part of this Recommendation.) + +The vBNG with the control plane and user plane separated is composed of a control plane and multiple user planes. The control plane can be composed of VNFs and deployed centrally. As a component for user control and management, the control plane takes responsibility for managing user plane resources such as the user information and forwarding policy. The user plane is composed of a number of forwarding devices at the boundary of the broadband network, and can form a resource pool. The control plane interacts with different management systems to implement user access, authentication, and accounting. After the user is authenticated and permitted, the control plane tells the user plane to do the corresponding forwarding actions with related policies, and the user plane forwards the traffic into the Internet with related policies. + +The deployment scenario of vBNG is shown in Figure I.1: + +![Diagram of the deployment scenario of vBNG showing the separation of control and user planes.](33a8f3f01dfa8bce75d23017855a13c5_img.jpg) + +The diagram illustrates the deployment scenario of vBNG. At the top, a yellow box labeled 'vBNG-CP' (Control Plane) is connected to a central cloud labeled 'Network'. To the left of the 'Network' cloud is an orange box labeled 'AAA' (Authentication, Authorization, Accounting), and to the right is a green box labeled 'Internet'. Below the 'Network' cloud, there are two paths. The left path leads to a yellow box labeled 'vBNG-UP' (User Plane), which is connected to two 'Access network' boxes, each of which is connected to a 'Users' box. The right path leads to a cloud labeled 'Pool', which contains two yellow boxes labeled 'vBNG-UP'. This 'Pool' cloud is connected to two 'Access network' boxes, each of which is connected to a 'Users' box. The text 'Q.3719(19)\_FI.1' is visible in the bottom right corner of the diagram. + +Diagram of the deployment scenario of vBNG showing the separation of control and user planes. + +Figure I.1 – Deployment scenario of vBNG + + + + + +## 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/Q/T-REC-Q.3721-202209-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3721-202209-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d19d20aa5d4c800a16f4c31f1ac14ff34a854745 --- /dev/null +++ b/marked/Q/T-REC-Q.3721-202209-I_PDF-E/raw.md @@ -0,0 +1,985 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3721** + +(09/2022) + +SERIES Q: SWITCHING AND SIGNALLING, AND +ASSOCIATED MEASUREMENTS AND TESTS + +Signalling requirements and protocols for SDN – Resource +control protocols + +--- + +**Procedures for a programming protocol +independent packet processor switch-based +virtual border network gateway** + +Recommendation ITU-T Q.3721 + +# ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 | +| Resource control protocols | Q.3710–Q.3739 | +| Network signalling and signalling requirements for services | Q.3740–Q.3779 | +| TESTING SPECIFICATIONS | Q.3900–Q.4099 | +| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100–Q.4139 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000–Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050–Q.5069 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T Q.3721 + +## Procedures for a programming protocol independent packet processor switch-based virtual border network gateway + +# Summary + +Recommendation ITU-T Q.3721 specifies the architecture, interfaces and procedures for a programming protocol independent packet processor switch-based virtual border network gateway. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.3721 | 2022-09-29 | 11 | 11.1002/1000/15045 | + +## Keywords + +Procedures, programming protocol independent packet processor, switch-based. + +--- + +\* 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/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 ..... | 1 | +| 5 | Conventions ..... | 3 | +| 6 | Overview ..... | 3 | +| 7 | Architecture for a P4 switch-based vBNG ..... | 4 | +| 7.1 | General architecture..... | 4 | +| 8 | Interfaces for P4 switch-based vBNG ..... | 5 | +| 8.1 | Service interface ..... | 5 | +| 8.2 | Control interface..... | 5 | +| 8.3 | Management interface ..... | 6 | +| 8.4 | Maintenance interface ..... | 6 | +| 8.5 | Monitoring interface..... | 6 | +| 9 | Protocol requirement for P4 switch-based vBNG ..... | 6 | +| 9.1 | P4Runtime protocol..... | 6 | +| 9.2 | Netconf protocol..... | 8 | +| 9.3 | Telemetry report protocol..... | 8 | +| 9.4 | Tunnel protocol ..... | 8 | +| 10 | Procedures for P4 switch-based vBNG ..... | 8 | +| 10.1 | IPoE DHCPv4 access procedure ..... | 9 | +| 10.2 | IPoE DHCPv6 access procedure ..... | 9 | +| 10.3 | PPPoE access procedure..... | 10 | +| | Annex A – Telemetry report format specification ..... | 12 | +| A.1 | Outer encapsulation ..... | 12 | +| A.2 | Telemetry report group header (version 2.0) (8 octets)..... | 12 | +| A.3 | Individual report header (version 2.0) (4+ octets)..... | 13 | +| A.4 | Embedded telemetry metadata in stacked reports ..... | 18 | +| | Bibliography..... | 19 | + + + +## Recommendation ITU-T Q.3721 + +## Procedures for a programming protocol independent packet processor switch-based virtual border network gateway + +# 1 Scope + +This Recommendation specifies the architecture, interfaces and procedures for a programming protocol independent packet processor (P4) switch-based virtual border network gateway (vBNG). + +# 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 Q.3719] Recommendation ITU-T Q.3719 (2019), *Signalling requirements for the separation of control plane and user plane in a virtualized broadband network gateway (vBNG)*. + +[IETF RFC 6241] IETF RFC 6241 (2011), *Network configuration protocol (NETCONF)*. + +[IETF RFC 7348] IETF RFC 7348 (2014), *Virtual extensible local area network (VXLAN): A framework for overlaying virtualized layer 2 networks over layer 3 networks*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 broadband network gateway (BNG)** [b-ITU-T Q.3315]: The access point to the provider's IP network for wireline broadband services. + +**3.1.2 virtual BNG** [b-ITU-T Q.3715]: The virtual BNG is the broadband network gateway of which all features or some features are directly implemented as virtual network function(s) (VNF(s)) running on the network function virtualization infrastructure (NFVI). It is used to either augment or replace the existing traditional BNG. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-----------------------------------------| +| AAA | Authentication Authorization Accounting | +| ACL | Access Control List | +| AN | Access Node | +| ASIC | Application Specific Integrated Circuit | + +| | | +|--------|------------------------------------------------------------| +| BNG | Broadband Network Gateway | +| CFI | Control Forwarding Interface | +| CGN | Carrier-Grade Network address translation | +| CHAP | Challenge Handshake Authentication Protocol | +| D | Dropped | +| DHCP | Dynamic Host Configuration Protocol | +| DPDK | Data Plane Development Kit | +| DS | Domain Specific | +| F | Flow | +| FPGA | Field Programmable Gate Array | +| gMNI | gRPC Network Management Interface | +| gRPC | Google Remote Procedure Call | +| I | Intermediate | +| ID | Identifier | +| IDL | Interface Define Language | +| INT | In-band Network Telemetry | +| INT-MD | In-band Network Telemetry – embed Data | +| INT-MX | In-band Network Telemetry – embed instructions | +| INT-XD | In-band Network Telemetry – export Data | +| IOAM | In-situ Operations, Administration, and Maintenance | +| IP | Internet Protocol | +| LCP | Link Control Protocol | +| MD | Metadata | +| NFVI | Network Function Virtualization Infrastructure | +| P4 | Programming Protocol independent Packet Processor | +| PADI | PPPoE Active Discovery Initiation | +| PADO | PPPoE Active Discovery Offer | +| PADR | PPPoE Active Discovery Request | +| PADT | PPPoE Active Discovery Termination | +| PPP | Point-to-Point Protocol | +| PPPoE | Point-to-Point Protocol over Ethernet | +| Q | Queue | +| QoS | Quality of Service | +| Rsvd | Reserved | +| RG | Residential Gateway | +| SR-IOV | Single Root Input/Output Virtualization | +| TLV | Type Length Value | + +| | | +|-----------|------------------------------------------------------------------| +| vBNG | virtual Border Network Gateway | +| vBNG-CP | Virtual Border Network Gateway-Control Plane | +| vBNG-UP | Virtual Border Network Gateway-User Plane | +| VNF | Virtual Network Function | +| VNFM | Virtual Network Function Management | +| VxLAN-GPE | Virtual Extensible Local Area Network-Generic Protocol Extension | +| YANG | Yet Another Next Generation | + +# 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 conformity 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 need not be present to claim conformity. + +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 conformity with this Recommendation. + +# 6 Overview + +Network function virtualization has emerged as the leading transformative technology that will allow service providers to move to a truly virtualized infrastructure. A broadband network gateway (BNG) is deployed at the edge of the metro area network of an operator and aggregates user sessions from the access network, providing access control by interworking with an authentication authorization accounting (AAA) server. BNG is also evolving into vBNG, which can be implemented in different types of hardware including dedicated equipment based on a network processor, application specific integrated circuit (ASIC) or [b-ITU-T X.86]. In order to improve forwarding efficiency and maintain flexibility, acceleration technologies can be used, e.g., data plane development kit (DPDK), single root input/output virtualization (SR-IOV) and ASIC, field programmable gate array (FPGA) acceleration card or P4 switch. + +P4 is a high-level language for data-forwarding programming, whose design is based on protocol independence, object independence and re-configurability. P4 is a southbound protocol, although its scope is large. It can not only guide the data stream to be forwarded, but also program the data processing flow of the forwarding device such as switch through software programming to guide how to process packets. + +Traditional vBNG is suitable for low-traffic scenarios. Although it can decouple software and hardware, it enhances development flexibility greatly and achieves the desired performance with the support of acceleration technologies, e.g., DPDK, SR-IOV. However, in the scenario of high-throughput complex service, vBNG faces many challenges. It requires more hardware investment, but the performance does not increase linearly with the rise in hardware costs. + +In order to solve these problems, P4 switch-based vBNG is proposed. Through P4 programming, iterative development can be completed in a short time, and device independence can be realized, which avoids the long period of development and commissioning to physical hardware necessary in the traditional vBNG forwarding plane. + +P4 programming can be applied to vBNG forwarding plane devices of different manufacturers to control data-forwarding behaviour, completely solving the problem that the network device hardware is bundled by a few manufacturers. It can also support novel features of the new protocol or fix existing vulnerabilities through software upgrading only, and remove redundant forwarding plane functions according to the application scenario, reduce potential vulnerabilities and operation complexity, as well as improving performance. + +# 7 Architecture for a P4 switch-based vBNG + +## 7.1 General architecture + +With regard to P4 switch-based vBNG, the architecture design should follow the following guidelines. + +- The basic bit rate available to each user should meet current business requirements. +- The full virtualization of network functionalities should allow service providers to make a smooth transition to a cloud-based network, such as one with a fifth generation core. +- Carrier-grade network address translation (CGN) should be considered in the forwarding platform to deal with IPv4 address exhaustion. +- Some virtualized network functions (such as traffic detection function/deep packet inspection, CGN) should be implemented, so the signal gateway and BNG should be strengthened to achieve a unique virtualized platform, ensure ultra-low latency and improve performance. +- The implementation of network element equipment should be decoupled from hardware and software to eliminate dependence on proprietary hardware. +- The individual service requirements of each client should be required to have device-level granularity and in-depth analysis scalability. + +![Figure 7-1 – Architecture for P4 switch-based vBNG. The diagram shows a three-tier architecture. The top tier consists of four external management systems: DHCP, AAA, VNFM, and EMS. The middle tier is a management plane containing several functions: AAA management function, VNFM interface, IP address management function, User management function, Load balancer, Access protocol management, vBNG-UP management, CU tunnel interface function, and CU protocol interface. The bottom tier is the forwarding plane containing: CU tunnel interface function, CU protocol interface, VPN access, Routing protocol, MPLS protocol, and Forwarding engine. Three vertical double-headed arrows connect the middle and bottom tiers, labeled 'Protocol VxLAN-GPE', 'Control P4Runtime', and 'Configuration Netconf/gMNI'.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +Q.3721(22) + +Figure 7-1 – Architecture for P4 switch-based vBNG. The diagram shows a three-tier architecture. The top tier consists of four external management systems: DHCP, AAA, VNFM, and EMS. The middle tier is a management plane containing several functions: AAA management function, VNFM interface, IP address management function, User management function, Load balancer, Access protocol management, vBNG-UP management, CU tunnel interface function, and CU protocol interface. The bottom tier is the forwarding plane containing: CU tunnel interface function, CU protocol interface, VPN access, Routing protocol, MPLS protocol, and Forwarding engine. Three vertical double-headed arrows connect the middle and bottom tiers, labeled 'Protocol VxLAN-GPE', 'Control P4Runtime', and 'Configuration Netconf/gMNI'. + +gMNI: gRPC network management interface; VNFM: virtual network function management + +**Figure 7-1 – Architecture for P4 switch-based vBNG** + +This Recommendation focuses on the specification of the control and forwarding interface between the virtual border network gateway-control plane (vBNG-CP) and virtual border network gateway-user plane (vBNG-UP). The physical division of control and forwarding interfaces is the same as the separation of control plane and user plane in vBNG (specified in [ITU-T Q.3719]), which is divided into interfaces for service, control and management. Logically, it also can be divided into five interfaces, including ones for service, control, management, maintenance and monitoring. The maintenance interface is required to be one for physical control, which shares the P4Runtime channel. The monitoring interface should be an optional logical interface, which can be carried by the user datagram protocol (UDP) tunnelling protocol. + +- A *service interface* is used to transmit point-to-point protocol over Ethernet (PPPoE) and other protocol packets between the vBNG-CP and vBNG-UP by the virtual extensible local area network-generic protocol extension (VxLAN-GPE) tunnel. +- A *control interface* mainly includes two parts: one used by the vBNG-CP to deliver user forwarding entries (including user identification information and user policy information) to the vBNG-UP; and the other used by the vBNG-UP to report user-related information (e.g., statistics information) to the vBNG-CP. The control interface should be supported by P4Runtime. +- A *management interface* is used by the vBNG-CP to send configuration parameters to vBNG-UP, including quality of service (QoS) template, access control list (ACL) template, control channel and service channel configuration parameters, and other related parameters. The NETCONF protocol and the yet another next generation (YANG) model is used to deliver configuration parameters. +- A *maintenance interface* is used by the vBNG-CP to online edit and update the forwarding engine firmware in vBNG-UP, to real-time upgrade the control interface of the vBNG-UP and to implement the software defining the vBNG-UP. These should be implemented by P4Runtime. +- A *monitoring interface* is required to support visualization at the network packet-level, including data collection and reporting. + +# 8 Interfaces for P4 switch-based vBNG + +## 8.1 Service interface + +The service interface is carried by VxLAN-GPE. The extension field needs to carry information (such as device number, port or virtual local area network) to identify the user identity to which the internal protocol message belongs. The vBNG-UP supports dynamic configuration of the VxLAN-GPE tunnel destination address and internal parameters, etc. The configuration can be implemented by the management interface. The vBNG-UP supports the VxLAN-GPE tunnel function, encapsulates user protocol packets (such as PPPoE) into VxLAN-GPE tunnel packets, and decapsulates user protocol packets encapsulated in the original packets by VxLAN-GPE. + +## 8.2 Control interface + +P4Runtime defines a set of standard interface define language (IDL) (proto) files for a Google remote procedure call (gRPC). The IDL abstractly defines the interfaces for adding, deleting, modifying and checking hardware entries, counter reading, packet-in/out, address notification and online upgrading. According to the specification of the overall architecture of vBNG, basic switching functions should be implemented in vBNG-UP, and user-related flow tables should be managed by the vBNG-CP, so P4Runtime is mainly used to control the user-side flow table. + +Due to the diversification of P4 forwarding plane equipment, such as the coexistence of multiple vendors and multiple chips (FPGA, ASIC, etc.), a unified abstraction of the user-side forwarding table is required, so that the vBNG-CP can uniformly control different P4 forwarding planes. User + +table attributes include virtual routing and forwarding, Internet protocol (IP), media access control, Session identifier (ID) (PPPoE) and rate limit. The vBNG-UP should support dynamic configuration of a user-side flow table through P4Runtime. + +## **8.3 Management interface** + +The management interface is used by the vBNG-CP to manage the basic configuration attributes of vBNG-UP, such as templates for QoS and ACL. In addition, the specific parameters of the service and control channel are delivered to vBNG-UP through the management interface. Therefore, the management interface is necessary for the connection between the vBNG forwarding and control planes. It needs to be manually configured on the vBNG-UP; otherwise the vBNG-UP could actively detect the vBNG-CP. The channel is supported by the NETCONF protocol. + +The vBNG-UP supports the configuration or active detection of the management interface. vBNG-UP supports the NETCONF protocol and the delivery of the YANG model. The specification of the YANG model refers to the OpenConfig standard. + +The vBNG-UP supports the upgrade of the management interface. + +## **8.4 Maintenance interface** + +The vBNG-UP supports online upgrade of the pipeline through P4Runtime. The scope of the online upgrade includes at least the user-side flow table, which serves as the maintenance interface of the control forwarding interface (CFI). + +## **8.5 Monitoring interface** + +In-band network telemetry (INT) is a packet-level network monitoring method. It adds information to the message hop by hop through the switching devices the message passes through, so as to realize the collection of message-level path, delay and other information. The packet loss and congestion of the switching equipment are reported. The introduction of the P4 forwarding plane can support this feature through suitable P4 encoding. The P4 form of vBNG-UP supports the INT function that can send report messages to the monitoring server. The message format and content are determined by the telemetry report standard. The vBNG-UP based on the P4 switch supports dynamic configuration of the report message destination address and other parameters. The configuration can be implemented by the management interface. + +# **9 Protocol requirement for P4 switch-based vBNG** + +## **9.1 P4Runtime protocol** + +The P4Runtime protocol supports the control of the user-side flow table between the vBNG-CP and vBNG-UP, reporting the traffic statistics information by the vBNG-UP, and updating the forwarding engine firmware. + +The vBNG-CP manages the user information on the user side by controlling the user side flow table and distributes the access-related information in the form of the flow table after user authentication, as well as receiving the traffic statistics information reported by vBNG-UP. When the vBNG-CP delivers the user flow table, it carries user information, bandwidth limit information and billing information. The vBNG-CP periodically obtains the statistical value of the flow table through the read interface as the charging information after the user information is delivered. The user-side flow table model appears in Figure 9-1. + +![Figure 9-1: User-side flow table model diagram showing 'User Up' and 'User Down' flow tables with their respective match types and actions, and their corresponding 'Meter Up' and 'Meter Down' tables. Arrows labeled 'Hit' point from the User tables to the Meter tables. A small legend table on the left defines 'table name', 'key:match type', 'action', and 'value'.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +The diagram illustrates the User-side flow table model. It consists of four main components: a legend table, two User tables, and two Meter tables. + +- Legend Table:** + - table name + - \* key:match type + - \* action + - \* value +- User Up Table:** + - \* sip:Exact; + - \* drop; + - \* ipoe; + - \* meter idx + - \* counter idx + - \* ppp insert + - \* meter idx + - \* counter idx +- Meter Up Table:** + - \* up\_meter\_color:Exact; + - \* drop; + - \* do counter; +- User Down Table:** + - \* sip:Exact; + - \* drop; + - \* ipoe; + - \* meter idx + - \* counter idx + - \* ppp terminate + - \* meter idx + - \* counter idx + - \* session id + - \*MAC +- Meter Down Table:** + - \* down\_meter\_color:Exact; + - \* drop; + - \* do counter; + +Arrows labeled "Hit" point from the User Up table to the Meter Up table, and from the User Down table to the Meter Down table. The text Q.3721(22) is located in the bottom right corner. + +Figure 9-1: User-side flow table model diagram showing 'User Up' and 'User Down' flow tables with their respective match types and actions, and their corresponding 'Meter Up' and 'Meter Down' tables. Arrows labeled 'Hit' point from the User tables to the Meter tables. A small legend table on the left defines 'table name', 'key:match type', 'action', and 'value'. + +**Figure 9-1 –User-side flow table model** + +table name : The user-side flow table name + match type : user up or user down + action : drop or ipoe or ppp insert/terminate + value : user information and counter table ID + +The message format of vBNG-UP reporting traffic statistics appears in Figure 9-2. + +![Figure 9-2: Message format of vBNG-UP reporting traffic statistics diagram showing a 'counter' table with fields: counter_id, index, byte_count, and packet_count. The text Q.3721(22) is located in the bottom right corner.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +The diagram shows the message format for reporting traffic statistics. It consists of a single table: + +- counter Table:** + - \* counter\_id + - \* index + - \* byte\_count + - \* packet\_count + +The text Q.3721(22) is located in the bottom right corner. + +Figure 9-2: Message format of vBNG-UP reporting traffic statistics diagram showing a 'counter' table with fields: counter\_id, index, byte\_count, and packet\_count. The text Q.3721(22) is located in the bottom right corner. + +**Figure 9-2 –Message format of vBNG-UP reporting traffic statistics** + +counter\_id: counter table ID + index: the statistical index in the counter table + byte\_count: the number of bytes counted + packet\_count: the number of packets counted + +The update message format of the vBNG-CP to the vBNG-UP forwarding engine firmware appears in Figure 9-3. + +![](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +| ForwardingPipelineConfig | +|--------------------------| +| * device_id | +| * role_id | +| * election_id | +| * action | +| * p4info | +| * p4_device_config | +| * cookie | + +Q.3721(22) + +**Figure 9-3 – Update message format of the vBNG-CP to the vBNG-UP forwarding engine firmware** + +device\_id: Device (controller) ID + +role\_id: Controller role ID + +election\_id: number of elections, + +action: + +UNSPECIFIED = 0; + +VERIFY = 1; + +VERIFY\_AND\_SAVE = 2; + +VERIFY\_AND\_COMMIT = 3; + +COMMIT = 4; + +RECONCILE\_AND\_COMMIT = 5; + +p4info: description of firmware information + +p4\_device\_config: firmware bin + +## 9.2 Netconf protocol + +The Netconf protocol is used for the configuration of parameters between the vBNG-CP and the vBNG-UP, such as the configuration of the virtual extensible local area network channel, interface, address segment, as well as templates for QoS and ACL. The implementation of the Netconf protocol should conform to the specification in [IETF RFC 6241]. + +## 9.3 Telemetry report protocol + +It is recommended that the INT data collection between the vBNG-CP and vBNG-UP be carried by the telemetry report protocol, which is based on UDP and sends packet-level information collected by vBNG-UP to the vBNG-CP for visual analysis. + +## 9.4 Tunnel protocol + +The tunnel protocol should support VXLAN-GPE and its format should conform to the specification in [IETF RFC 7348]. + +# 10 Procedures for P4 switch-based vBNG + +Before starting the procedures, it is necessary to open the CFI configuration channel between the vBNG-CP and vBNG-UP. The configuration channel can be opened by directly configuring the vBNG-CP and vBNG-UP through an element management system. After opening, the configuration channel allows the vBNG-CP to configure the channels for protocol and control. The vBNG-CP can + +realize the unified configuration of all vBNG-UPs it manages, including the configuration of the vBNG interface and QoS template. + +## 10.1 IPoE DHCPv4 access procedure + +The IPoE dynamic host configuration protocol version 4 (DHCPv4) access procedure appears in Figure 10-1. + +![Sequence diagram of the IPoE DHCPv4 access procedure showing interactions between RG, AN, vBNG-UP, vBNG-CP, and AAA.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +The diagram illustrates the sequence of messages for the IPoE DHCPv4 access procedure. It features five lifelines: RG (Residential Gateway), AN (Access Node), vBNG-UP (vBNG User Plane), vBNG-CP (vBNG Control Plane), and AAA (Authentication, Authorization, Accounting). The process begins with a DHCP discover message from RG to AN, forwarded to vBNG-UP, and then to vBNG-CP. vBNG-CP then sends an Access request to AAA, which responds with an Access accept. Subsequently, a DHCP offer is sent from vBNG-CP back through vBNG-UP and AN to RG. This is followed by a DHCP request from RG through the same path to vBNG-CP. vBNG-CP then sends a DHCP ack back to RG. Finally, a session establishment request is sent from vBNG-CP to vBNG-UP, which responds with a session establishment response. The diagram labels the 'Service interface' as the interaction between RG and AN, and the 'Control interface' as the interaction between vBNG-UP and vBNG-CP. + +``` + +sequenceDiagram + participant RG + participant AN + participant vBNG-UP + participant vBNG-CP + participant AAA + + RG->>AN: DHCP discover + AN->>vBNG-UP: DHCP discover + vBNG-UP->>vBNG-CP: DHCP discover + vBNG-CP->>AAA: Access request + AAA-->>vBNG-CP: Access accept + vBNG-CP->>vBNG-UP: DHCP offer + vBNG-UP->>AN: DHCP offer + AN->>RG: DHCP offer + RG->>AN: DHCP request + AN->>vBNG-UP: DHCP request + vBNG-UP->>vBNG-CP: DHCP request + vBNG-CP->>vBNG-UP: DHCP ack + vBNG-UP->>AN: DHCP ack + AN->>RG: DHCP ack + vBNG-CP->>vBNG-UP: Session establishment request + vBNG-UP-->>vBNG-CP: Session establishment response + +``` + +Service interface +Control interface + +Q.3721(22) + +AN: access node + +Sequence diagram of the IPoE DHCPv4 access procedure showing interactions between RG, AN, vBNG-UP, vBNG-CP, and AAA. + +**Figure 10-1 – IPoE DHCPv4 access procedure** + +- (1) The vBNG-UP sends a DHCP discovery message to the vBNG-CP, which triggers access request to authenticate the residential gateway (RG). +- (2) The AAA successfully authenticates the RG and responds with an access accept message to the vBNG-CP. +- (3) The vBNG-CP sends a DHCP offer message to the vBNG-UP through the service interface, and finally to the RG. +- (4) The RG sends a DHCP request message that is forwarded to the vBNG-CP through the service interface through the vBNG-UP. +- (5) The vBNG-CP sends a DHCP acknowledgement message to the RG to complete IPoE user access. +- (6) The vBNG-CP obtains the IP address assigned to the RG, which can be assigned through a local address, AAA or DHCP server, and sends a session establishment request to the vBNG-UP. +- (7) The vBNG-UP sends the session establishment response information to the vBNG-CP and informs the vBNG-CP that it is ready to forward the user IP address information. + +## 10.2 IPoE DHCPv6 access procedure + +See Figure 10-2. + +![Sequence diagram of IPoE DHCPv6 access procedure showing interactions between RG, AN, vBNG-UP, vBNG-CP, and AAA. The diagram is divided into Service interface (RG-AN) and Control interface (AN-vBNG-UP-vBNG-CP-AAA).](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +``` + +sequenceDiagram + participant RG + participant AN + participant vBNG-UP + participant vBNG-CP + participant AAA + + Note left of RG: Service interface + Note right of vBNG-UP: Control interface + + RG->>AN: DHCPv6 sol. + AN->>vBNG-UP: DHCPv6 sol. + vBNG-UP->>vBNG-CP: DHCPv6 sol. + vBNG-CP->>AAA: Access request + AAA->>vBNG-CP: Access accept + vBNG-CP->>vBNG-UP: DHCPv6 adv. + vBNG-UP->>AN: DHCPv6 adv. + AN->>RG: DHCPv6 adv. + RG->>AN: DHCPv6 req. + AN->>vBNG-UP: DHCPv6 req. + vBNG-UP->>vBNG-CP: DHCPv6 req. + vBNG-CP->>vBNG-UP: DHCPv6 reply + vBNG-UP->>AN: DHCPv6 reply + AN->>RG: DHCPv6 reply + RG->>AN: DHCPv6 adv. + AN->>vBNG-UP: DHCPv6 adv. + vBNG-UP->>vBNG-CP: DHCPv6 adv. + vBNG-CP->>vBNG-UP: Session creation request + vBNG-UP->>vBNG-CP: Session creation response + +``` + +Q.3721(22) + +Sequence diagram of IPoE DHCPv6 access procedure showing interactions between RG, AN, vBNG-UP, vBNG-CP, and AAA. The diagram is divided into Service interface (RG-AN) and Control interface (AN-vBNG-UP-vBNG-CP-AAA). + +**Figure 10-2 – IPoE DHCPv6 access procedure** + +- (1) The vBNG-CP triggers an access request to the AAA for authentication of the RG. +- (2) The AAA successfully authenticates the RG and sends an access reply message to the vBNG-CP. +- (3) The vBNG-CP obtains the IP address assigned to the RG, which can be assigned through a server of the local address, AAA or DHCP type, and then sends a session request to the vBNG-UP. +- (4) The vBNG-UP sends the session response message to the vBNG-CP, informing the vBNG-CP that it is ready to forward the user IP address information. +- (5) The vBNG-CP sends a DHCPv6 advertisement message to the vBNG-UP through the service interface and finally to the RG. +- (6) The RG sends the DHCPv6 request message to the vBNG-UP through a customized session channel and to the vBNG-CP through a service interface. +- (7) The vBNG-CP sends a DHCPv6 reply message to the RG. +- (8) The vBNG-CP notifies the RG of the address information of the default gateway to complete IPoE user access. + +## 10.3 PPPoE access procedure + +See Figure 10-3. + +![Sequence diagram of PPPoE access procedure showing interactions between RG, AN, vBNG-UP, vBNG-CP, and AAA. The diagram is divided into Service interface (RG to AN) and Control interface (AN to vBNG-UP, vBNG-UP to vBNG-CP, vBNG-CP to AAA).](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +sequenceDiagram + participant RG + participant AN + participant vBNG-UP + participant vBNG-CP + participant AAA + + Note left of RG: Service interface + RG->>AN: PPPoE PADI + AN->>vBNG-UP: PPPoE PADI + vBNG-UP->>vBNG-CP: PPPoE PADI + vBNG-CP-->>vBNG-UP: PPPoE PADO + vBNG-UP-->>AN: PPPoE PADO + AN-->>RG: PPPoE PADO + RG->>AN: PPPoE PADR + AN->>vBNG-UP: PPPoE PADR + vBNG-UP->>vBNG-CP: PPPoE PADR + vBNG-CP-->>vBNG-UP: PPPoE PADT + vBNG-UP-->>AN: PPPoE PADT + AN-->>RG: PPPoE PADT + AN->>vBNG-UP: PPP LCP + vBNG-UP->>vBNG-CP: CHAP challenge + vBNG-CP-->>vBNG-UP: CHAP response + vBNG-UP-->>AN: CHAP response + AN-->>RG: CHAP response + vBNG-CP->>AAA: Access request + AAA-->>vBNG-CP: Access accept + vBNG-CP->>vBNG-UP: Address assignment request + vBNG-UP-->>AN: Address assignment request + AN-->>RG: Address assignment request + vBNG-CP->>vBNG-UP: Address assignment response + vBNG-UP-->>AN: Address assignment response + AN-->>RG: Address assignment response + Note right of vBNG-UP: Control interface + vBNG-CP->>vBNG-UP: Delivers the user data forwarding table + vBNG-CP->>vBNG-UP: Update the user data forwarding table + +``` + +Sequence diagram of PPPoE access procedure showing interactions between RG, AN, vBNG-UP, vBNG-CP, and AAA. The diagram is divided into Service interface (RG to AN) and Control interface (AN to vBNG-UP, vBNG-UP to vBNG-CP, vBNG-CP to AAA). + +Q.3721(22) + +CHAP: challenge handshake authentication protocol; LCP: Link Control Protocol; PADI: PPPoE active discovery initiation; PADO: PPPoE active discovery offer; PADR: PPPoE active discovery request; PADT: PPPoE active discovery termination; PPP: point-to-point protocol + +**Figure 10-3 – PPPoE access procedure** + +- (1) The vBNG-UP receives the subscriber's PPPoE access message, and vBNG-UP sends it to the vBNG-CP through the protocol channel. +- (2) The vBNG-CP processes the PPPoE state machine, triggers authentication by AAA and IP address allocation, and sends a response message to the vBNG-UP through the protocol channel. Then the vBNG-UP sends a response message back to the subscriber. +- (3) The vBNG-CP creates a user forwarding table and synchronizes it to the user table database. Through the control channel, the vBNG-CP sends the user forwarding table and user address routing information to the vBNG-UP. The vBNG-UP runs the routing protocol, generates network forwarding table entries, and publishes the user routing to the network side, so that the downlink traffic directly returns to the vBNG-UP. +- (4) The vBNG-UP collects user uplink and downlink traffic statistics, billing information and alarm information, and regularly sends them to the vBNG-CP through the control plane channel. + +# Annex A + +## Telemetry report format specification + +(This annex forms an integral part of this Recommendation.) + +This annex is derived from section 3 of [b-p4.org-TRF]. + +This annex specifies the packet format for telemetry reports. + +## A.1 Outer encapsulation + +Telemetry reports are defined using a UDP-based encapsulation. Various outer encapsulations may be used to transport the UDP packets. Typically, this would simply be an Ethernet header, followed by an IPv4 or IPv6 header, followed by the UDP header. This specification does not preclude the use of different transport encapsulations. + +The source IP address identifies the node that generates the telemetry report. + +The destination IP address identifies a location in the distributed telemetry monitoring system that will receive the telemetry report. + +In the case of IPv4, as is the case for any other IP packet, either the Don't Fragment (DF) bit must be set, or the IPv4 ID field must be set so that the value does not repeat within the maximum datagram lifetime for a given source address/destination address/protocol tuple. + +### A.1.1 UDP header (8 octets) + +See Figure A.1. + +![](aa9441a5971655a79987d70fc551b26a_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------|---|---|---|---|---|---|---|---|---|----|----|----|----|----|----|------------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| 0 | 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 | 29 | 30 | 31 | +| Source port | | | | | | | | | | | | | | | | Destination port | | | | | | | | | | | | | | | | +| Length | | | | | | | | | | | | | | | | Checksum | | | | | | | | | | | | | | | | + +Q.3721(22) + +Figure A.1 – UDP header + +The source port can optionally be used to carry flow entropy, e.g., based on a hash of the inner 5-tuple. Otherwise, it should be user configurable. + +The destination port is user configurable. The expectation is that the same destination port value will be used for all telemetry reports in a particular deployment. + +## A.2 Telemetry report group header (version 2.0) (8 octets) + +The telemetry report group header immediately follows the UDP header whose destination port identifies the contents as a telemetry report. This header contains the common fields in a telemetry report that optionally contains multiple coalesced individual reports, each corresponding to one data plane packet. There is at most one instance of the telemetry report group header in a packet. See Figure A.2. + +![](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------|---|---|---|-------|---|---|---|---|---|-----------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| 0 | 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 | 29 | 30 | 31 | +| Ver | | | | hw_id | | | | | | Sequence number | | | | | | | | | | | | | | | | | | | | | | +| Node ID | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +Q.3721(22) + +**Figure A.2 – Telemetry report group header (version 2.0)** + +#### **Ver (4 bits): Version** + +This specification defines **version 2**. + +#### **hw\_id (6 bits): Hardware ID** + +Identifies the hardware subsystem within the node that generated this report. For example, in a chassis with multiple linecards, this could identify a specific linecard or a subsystem within a linecard. The hw\_id is unique within the scope of a node ID. + +#### **Sequence number (22 bits): Sequence number** + +Reflects the sequence of reports from a specific combination of (node ID, hw\_id) to a particular telemetry report destination. This can be used to detect loss of telemetry reports before they reach their intended destination. + +#### **Node ID (32 bits): Node ID** + +The unique ID of a node. This is generally administratively assigned. Node IDs must be unique within a management domain. + +## **A.3 Individual report header (version 2.0) (4+ octets)** + +Each telemetry report packet contains one or more individual reports immediately following the telemetry report group header. Each report within the packet starts with the individual report header. The presence of multiple reports corresponding to multiple data plane packets, possibly from multiple flows, can be determined by comparing the report length in the individual report header with the length in the UDP header. See Figure A.3. + +![](cf4ac1058c52bc3ca37737740afb7f2c_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------|---|---|---|--------|---|---|---|---------------|---|----|----|----|----|----|----|-----------|----|----|----|----|----|----|----|----|----|----|----|------|----|----|----| +| 0 | 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 | 29 | 30 | 31 | +| RepType | | | | InType | | | | Report length | | | | | | | | MD length | | | | | | | | D | Q | F | I | Rsvd | | | | +| Individual report main contents
(Varies depending on RepType) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Individual report inner contents
(Truncated packet or additional DS extension data or TLV depending on InType) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +Report length + +Q.3721(22) + +**Figure A.3 – Individual report header (version 2.0)** + +#### **RepType (4 bits): Report type** + +Type of the individual report: + +- 0: Inner Only +- 1: INT +- 2: IOAM +- 3-15: Reserved. + +#### **InType (4 bits): Inner type** + +Type of data embedded after the *Individual Report Main Contents*: + +- 0: None +- 1: TLV +- 2: Domain Specific Extension Data +- 3: Ethernet +- 4: IPv4 +- 5: IPv6 +- 6-15: Reserved. + +#### **Report length (8 bits): Report length** + +Indicates the length of the individual report header in a multiple of 4-byte words, including the *Individual Report Main Contents* and *Individual Report Inner Contents*, but excluding the length of the first 4-byte word (RepType, InType, Report Length, MD Length, D, Q, F, I, Rsvd). + +For *RepType* codepoint 1 INT, the *Report Length* includes the lengths of *RepMdBits*, *Domain Specific ID*, *DSMdBits*, *DSMdstatus*, *Variable Optional Baseline Metadata* and *Variable Optional Domain Specific Metadata*. + +The *Report Length* value 0xFF is a special value that indicates a length greater than or equal to 0xFF, extending to the end of the UDP payload, i.e., there are no subsequent individual reports in this telemetry report. + +#### **MD length (8 bits): Metadata length** + +Indicates the length of metadata (MD) included in this report in a multiple of 4-byte words. This may help the telemetry monitoring system determine where the *Individual Report Inner Contents* begins. Note that this does not include the length of the fixed portion of the *Individual Report Main Contents*. + +For *RepType* codepoint 1 INT, this includes the length of the *Variable Optional Baseline Metadata* and *Variable Optional Domain Specific Metadata* in 4-byte words. + +#### **D (1 bit): Dropped** + +Indicates that at least one packet matching a watchlist was dropped. + +#### **Q (1 bit): Congested queue association** + +Indicates the presence of congestion on a monitored queue. + +#### **F (1 bit): Tracked flow association** + +Indicates that this telemetry report is for a tracked flow, i.e., the packet matched a watchlist somewhere (in the case of in-band network telemetry – embed data (INT-MD), in-band network telemetry – embed instructions (INT-MX) or *in-situ* operations, administration, and maintenance (IOAM)) or locally (in the case of in-band network telemetry – export data (INT-XD)). The report might include INT-MD or IOAM metadata in the truncated packet. Other telemetry reports are likely to be received for the same tracked flow, from the same node and (in case of drop reports, INT-MX, INT-XD or path changes) from other nodes. + +#### **I (1 bit): Intermediate report** + +Indicates that a transit node sent this intermediate report for INT-MD. + +#### **Rsvd (4 bit): Reserved** + +Should be set to zero upon transmission and ignored upon reception. + +#### Individual report main contents + +The metadata that comprises this report, along with associated fields that assist in processing the metadata. The format varies depending on *RepType*. + +When the *RepType* value is *Inner Only*, then the individual report main contents are empty. *MD Length* should be set to zero upon transmission and ignored upon reception. + +The *INT* individual report main contents format was derived with INT 2.0/2.1 in mind, but it may be used with other INT versions as well. It is possible that other *RepType* codepoints and corresponding individual report main contents formats may be defined for future versions of INT. + +The *IOAM* individual report main contents format is for further study. + +#### Truncated packet + +Layer 2/layer 3/ESP/layer 4 header of the IP packet for flow details. The presence of this field is indicated by *InType* codepoint 3, 4, or 5, which identifies the type of header at the beginning of the truncated packet. The length of the truncated packet can be determined as *Report Length* – ((fixed length of *Individual Report Main Contents*) + *MD Length*), unless the *Report Length* value is 0xFF. + +#### Additional DS extension data + +Additional domain specific (DS) extension data, whose format can be determined from the *Domain Specific ID* specified in the *Individual Report Main Contents*. For *RepType* codepoint 1 *INT*, this is additional domain specific data that is not associated with *DSMdBits*. The presence of this field is indicated by *InType* codepoint 2. + +#### TLV + +Type length value (TLV) format. Multiple TLV formatted data. The presence of this field is indicated by *InType* codepoint 1. + +### A.3.1 Individual Report Main Contents for RepType 1 (INT) (8+ octets) + +See Figure A.4. + +![Diagram of Individual report main contents for RepType 1 (INT). The diagram shows a 32-bit word structure with bits 0-31. Bits 0-15 are RepMdBits, and bits 16-31 are Domain specific ID. Below these are DSMdBits and DSMdstatus. The bottom two rows are Variable optional baseline metadata and Variable optional domain specific metadata, which are grouped by a bracket labeled MD length.](c0e369274e53b2e5364666be6f786c7a_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------|---|---|---|---|---|---|---|---|---|----|----|----|----|----|----|--------------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| 0 | 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 | 29 | 30 | 31 | +| RepMdBits | | | | | | | | | | | | | | | | Domain specific ID | | | | | | | | | | | | | | | | +| DSMdBits | | | | | | | | | | | | | | | | DSMdstatus | | | | | | | | | | | | | | | | +| Variable optional baseline metadata | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Variable optional domain specific metadata | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +Q.3721(22) + +Diagram of Individual report main contents for RepType 1 (INT). The diagram shows a 32-bit word structure with bits 0-31. Bits 0-15 are RepMdBits, and bits 16-31 are Domain specific ID. Below these are DSMdBits and DSMdstatus. The bottom two rows are Variable optional baseline metadata and Variable optional domain specific metadata, which are grouped by a bracket labeled MD length. + +Figure A.4 – Individual report main contents for RepType 1 (INT) + +##### RepMdBits (16 bit): Report metadata bits + +Bitmap that indicates which optional baseline metadata is present in the telemetry report header. Each bit represents 4 octets of optional metadata, except for bits 4, 5 and 6 which represent 8 octets of optional metadata. + +- bit 0 (MSB): Reserved +- bit 1: Level 1 Ingress Interface ID (16 bits) and Egress Interface ID (16 bit) +- bit 2: Hop Latency +- bit 3: Queue ID (8 bit) + Queue Occupancy (24 bit) +- bit 4: Ingress Timestamp (64 bit) + +- bit 5: Egress Timestamp (64 bit) +- bit 6: Level 2 Ingress Interface ID (32 bit) + Egress Interface ID (32 bit) +- bit 7: Egress Port TX Utilization +- bit 8: Buffer ID (8 bits) + Buffer Occupancy (24 bit) +- bit 9-14: Reserved +- bit 15: Queue ID (8 bit) + Drop Reason (8 bit) + Padding (16 bit). + +This specification defines the following metadata. + +##### Drop reason + +An enumeration that indicates the reason why a packet was dropped, e.g., as described in [b-GitHub]. See [b-p4.org-INT] for definitions of the remaining metadata. + +##### Domain specific ID (16 bit) + +The unique ID of the INT domain. + +The *Domain Specific ID* value 0x0000 is the default, known to all nodes. For this value, all *DSMdBits* are treated as reserved. Operators can assign values in the range 0x0001 to 0xFFFF. + +#### DSMdBits (16 bit): Domain specific Md bits + +Bitmap that indicates which optional domain specific metadata is present in the telemetry report header. Each bit represents 4 octets or a multiple of 4 octets of domain specific optional metadata. + +When using INT-MD or INT-MX, if the *Domain Specific ID* does not match any domain ID known to this node, then the node may either: + +- set the telemetry report *DSMdBits* field to zero and rederive the telemetry report *MD Length* from *RepMdBits*; or +- not send any of its own metadata to the monitoring systems, doing any of the following: + - not generating any Telemetry Report, + - clear *RepMdBits* and *MD Length* as well as *DSMdBits* (this only makes sense for INT-MD) or + - use *RepType* value *Inner Only* (this only makes sense for INT-MD). + +#### DSMdstatus (16 bit): Domain specific Md status + +Indicates the domain specific metadata status. + +##### Variable optional baseline metadata + +The metadata corresponding to *RepMdBits*, 4 octets for each bit, except 8 octets for bits 4, 5 and 6. + +If a node receives an INT-MX or INT-MD packet with an instruction bitmap that requests one or more metadata values that are not available or reserved, then the node must ensure that the corresponding bit(s) in the telemetry report *RepMdBits* that specify the unavailable metadata are not set. The telemetry report *MD Length* must be derived based on the adjusted *RepMdBits* (and *DSMdBits*) values. + +##### Variable optional domain specific metadata + +The metadata corresponding to *DSMdBits*, 4 octets or a multiple of 4 octets for each bit. + +If a node receives an INT-MX or INT-MD packet with a *DS Instruction* that requests one or more metadata values that are not available or reserved, then the node must ensure that the corresponding bit(s) in the telemetry report *DSMdBits* that specify the unavailable metadata are not set. The + +telemetry report *MD Length* must be derived based on the adjusted *DSMdBits* (and *RepMdBits*) values. + +### A.3.2 Individual report inner contents for InType 1 (TLV) (4+ octets) + +One or more TLVs, each following the format defined in this clause. The presence of multiple TLVs can be determined by comparing the *TLVLength* in the first TLV with the *Report Length* in the individual report header. See Figure A.5. + +![Diagram of TLV structure showing fields: TLVType (bits 0-3), Rsvd (bits 4-7), TLVLength (bits 8-15), and TLV data template (bits 16-31). The data template is variable length and may be repeated. The total length is indicated by TLV length and Q.3721(22).](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------|---|---|---|------|---|---|---|-----------|---|----|----|----|----|----|----|-------------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| 0 | 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 | 29 | 30 | 31 | +| TLVType | | | | Rsvd | | | | TLVLength | | | | | | | | TLV data template | | | | | | | | | | | | | | | | +| Variable TLV data as identified by TLVType
(Truncated packet or domain specific extension data) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +Annotations: 'May be repeated' (vertical arrow on the right), 'TLV length' (vertical arrow on the right), 'Q.3721(22)' (at the bottom right). + +Diagram of TLV structure showing fields: TLVType (bits 0-3), Rsvd (bits 4-7), TLVLength (bits 8-15), and TLV data template (bits 16-31). The data template is variable length and may be repeated. The total length is indicated by TLV length and Q.3721(22). + +Figure A.5 – Individual report inner contents for InType 1 (TLV) + +#### TLVType (4 bits): TLV data type + +- 0: Domain Specific Extension Data +- 1: Ethernet +- 2: IPv4 +- 3: IPv6 +- 4-15: Reserved + +#### Rsvd (4 bits) – Reserved + +Should be set to zero upon transmission and ignored upon reception. + +#### TLVLength (8 bits) + +Indicates the length, in 4-byte words, of variable *TLV Data* as identified by *TLVType*. Note that this does not include the length of the first 4-byte word (*TLVType*, *Rsvd*, *TLVLength*, *TLV Data Template*). + +##### TLV Data Template (16 bits) + +Specifies the format of the *Variable TLV Data*. A non-zero *TLV Data Template* value specifies the template for *TLVType* codepoint of *Domain Specific Extension Data*. For *TLVType* code-points *Ethernet*, *IPv4*, and *IPv6*, the *TLV Data Template* value should be zero upon transmission and ignored upon reception. + +##### Variable TLV data + +Variable length data based upon *TLVType*. The following two fields are defined in this version. + +##### Truncated packet + +Layer 2/layer 3/ESP/layer 4 header of the IP packet for flow details. The presence of this field is indicated by *TLVType* codepoint 1, 2, or 3, which identifies the type of header at the beginning of the truncated packet. + +##### Domain specific extension data + +Domain specific extension data, whose format can be determined from the *Domain Specific ID* specified in the *Individual Report Main Contents* and the *TLV Data Template*. The presence of this field is indicated by *TLVType* codepoint 0. + +For *RepType* codepoint 1 *INT*, this is additional domain specific data that is not associated with *DSMdBits*. + +## A.4 Embedded telemetry metadata in stacked reports + +There may still be further telemetry metadata embedded within a truncated packet fragment. For example, this is typically the case when there is stacked telemetry metadata from hops prior to the node generating the report. The telemetry metadata will typically be encoded using a defined data plane format such as INT-MD or IOAM. + +A node generating a telemetry report with stacked telemetry metadata may include its local telemetry metadata in any of the following: + +- the embedded telemetry metadata in a truncated packet fragment; +- the stacked telemetry metadata in domain specific extension data; +- the *Individual Report Main Contents* in the same individual report header that contains the stacked telemetry metadata from previous hops, in either a truncated packet fragment or in domain specific extension data; or +- the *Individual Report Main Contents* in a separate report from the stacked telemetry metadata from previous hops – note that in this case the ingress timestamp (if present) will be the same in both reports. + +If the *Tracked Flow Association (F)* bit is set to 0, then there will not be any embedded telemetry metadata in the report. + +If the *Tracked Flow Association (F)* bit is set to 1, there may or may not be any embedded telemetry metadata in the report. + +# Bibliography + +- [b-ITU-T Q.3315] Recommendation ITU-T Q.3315 (2015), *Signalling requirements for flexible network service combination on broadband network gateway*. +- [b-ITU-T Q.3715] Recommendation ITU-T Q.3715 (2018), *Signalling requirements for dynamic bandwidth adjustment on demand on broadband network gateway implemented by software-defined networking technologies*. +- [b-ITU-T X.86] Recommendation ITU-T X.86 (2001), *Ethernet over LAPS*. +- [b-GitHub] GitHub (2022). *p4lang/switch*. San Francisco, CA: Github. Available [2022-11-28] at: [github.com/p4lang/switch](https://github.com/p4lang/switch). +- [b-p4.org-INT] p4.org Applications Working Group (2020). *In-band network telemetry (INT) dataplane specification*, version 2.1. Available [viewed 2022-11-29] at: [https://p4.org/p4-spec/docs/INT\\_v2\\_1.pdf](https://p4.org/p4-spec/docs/INT_v2_1.pdf) +- [b-p4.org-TRF] p4.org Applications Working Group (2020). *Telemetry report format specification*, version 2.0. Available [viewed 2022-11-29] at: [https://p4.org/p4-spec/docs/telemetry\\_report\\_v2\\_0.pdf](https://p4.org/p4-spec/docs/telemetry_report_v2_0.pdf) + + + + + +# 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/Q/T-REC-Q.3741-201907-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3741-201907-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7caa1dedc9daaf6f9bd7ce2ab7a78c2fa4315b2a --- /dev/null +++ b/marked/Q/T-REC-Q.3741-201907-I_PDF-E/raw.md @@ -0,0 +1,710 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3741** + +(07/2019) + +SERIES Q: SWITCHING AND SIGNALLING, AND +ASSOCIATED MEASUREMENTS AND TESTS + +Signalling requirements and protocols for SDN – Network +signalling and signalling requirements for services + +# --- **Signalling requirements for SD-WAN service** + +Recommendation ITU-T Q.3741 + +## ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 | +| Resource control protocols | Q.3710–Q.3739 | +| Network signalling and signalling requirements for services | Q.3740–Q.3779 | +| TESTING SPECIFICATIONS | Q.3900–Q.4099 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000–Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050–Q.5069 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T Q.3741 + +# Signalling requirements for SD-WAN service + +## Summary + +Recommendation ITU-T Q.3741 specifies signalling requirements for software-defined wide area networking (SD-WAN) service launched by service providers. The signalling is to support the automated provision and management of the enterprise SD-WAN service. + +SD-WAN is an ecosystem of hardware, software and services that enable service providers to launch software-defined wide area network (WAN) services for enterprises. It provides high quality WAN performance, reliability and security in various ways. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.3741 | 2019-07-29 | 11 | 11.1002/1000/13978 | + +## Keywords + +SD-WAN, signalling requirements. + +--- + +\* 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 2019 + +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 Convention..... | 2 | +| 6 General description of SD-WAN service ..... | 2 | +| 7 Signalling architecture of SD-WAN service ..... | 3 | +| 8 The information flow of SFi ..... | 4 | +| 8.1 The information flow of registration and automatic installation..... | 4 | +| 8.2 The information flow of statistics collection..... | 4 | +| 8.3 The information flow of dynamic WAN path control..... | 5 | +| 9 The signalling requirements of SFi..... | 5 | +| 9.1 vCPE/CPE registration request and response message ..... | 5 | +| 9.2 WAN gateway registration request and response message ..... | 6 | +| 9.3 vCPE/CPE configuration request and response message ..... | 7 | +| 9.4 WAN gateway configuration request and response message..... | 9 | +| 9.5 Statistic collection message and response message..... | 10 | +| 9.6 Dynamic SD-WAN path control for vCPE /CPE request message and
response message..... | 11 | +| 9.7 Dynamic SD-WAN path control for WAN gateway request message and
response message..... | 12 | +| Bibliography..... | 13 | + + + +## Recommendation ITU-T Q.3741 + +# Signalling requirements for SD-WAN service + +# 1 Scope + +The Recommendation includes: + +- general description of software-defined wide area networking (SD-WAN) service launched by service providers; +- signalling architecture of SD-WAN service; +- information flow of interface SFi between SD-WAN controller and customer-premises equipment (CPE)/virtualized customer premises equipment (vCPE)/wide area network (WAN) gateway; +- signalling requirements of interface SFi. + +# 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. + +None. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 software-defined networking** [b-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.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 SD-WAN**: An ecosystem of hardware (including customer-premises equipment, such as edge devices), software (including controllers) and services that enable enterprise-grade performance, reliability and security of WAN services in various software-defined manners. + +**3.2.2 WAN gateway**: A gateway that provides WAN access for individuals and enterprises. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|------------------------------------| +| ADSL | Asymmetric Digital Subscriber Line | +| CPE | Customer-Premises Equipment | +| IPFPM | IP Flow-Performance Monitor | + +| | | +|--------|-----------------------------------------| +| LTE | Long Term Evolution | +| MOS | Mean Opinion Score | +| MPLS | Multiprotocol Label Switching | +| NQA | Network Quality Analyser | +| SDN | Software-Defined Networking | +| SD-WAN | Software-Defined Wide Area Networking | +| TWAMP | Two-Way Active Measurement Protocol | +| VPN | Virtual Private Network | +| vCPE | Virtualized Customer Premises Equipment | +| WAN | Wide Area Network | + +# 5 Convention + +None. + +# 6 General description of SD-WAN service + +Enterprise WAN has become increasingly complex and is costly to be managed and maintained. Service providers are facing difficulties in meeting enterprises' requirements. Some of these difficulties are listed below: + +- significant delays and cost in remote site deployment; +- heterogeneous network access results in complicated configuration, monitoring and management for virtual private network (VPN), multicast and link bundling; +- inefficient WAN bandwidth utilization for enterprises. + +SD-WAN service can be launched by service providers using software-defined networking (SDN) technologies and can satisfy the following key capabilities: + +- automated provisioning of services; +- creating scalable and redundant networks; +- dynamic multi-path optimization; +- automatic monitoring and capacity testing; +- application steering and link remediation. + +Figure 6-1 presents the framework of the SD-WAN service launched by service providers. + +![Figure 6-1: Framework of SD-WAN service. This diagram illustrates a network architecture. At the top is an 'SD-WAN controller'. Below it are three rows representing different sites. The top row is 'Headquarter vCPE/CPE' connected to a 'WAN gateway' via 'DSL' and 'Wireless' options. The middle and bottom rows are 'Branch vCPE/CPE' also connected to 'WAN gateways' via 'DSL' and 'Wireless'. The 'Service provider's access network' is on the left. In the center is the 'Service provider's backbone network' containing 'VPN' and 'Public Internet' clouds. On the right are destinations: 'Enterprise DC', 'Critical applications', and 'None-critical applications'. A red line traces a path from a Branch vCPE/CPE through DSL, a WAN gateway, and a VPN to the Enterprise DC. A blue line traces a path from a Branch vCPE/CPE through Wireless, a WAN gateway, and the Public Internet to None-critical applications. Dashed blue arrows connect the SD-WAN controller to the WAN gateways and vCPE/CPEs.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +Figure 6-1: Framework of SD-WAN service. This diagram illustrates a network architecture. At the top is an 'SD-WAN controller'. Below it are three rows representing different sites. The top row is 'Headquarter vCPE/CPE' connected to a 'WAN gateway' via 'DSL' and 'Wireless' options. The middle and bottom rows are 'Branch vCPE/CPE' also connected to 'WAN gateways' via 'DSL' and 'Wireless'. The 'Service provider's access network' is on the left. In the center is the 'Service provider's backbone network' containing 'VPN' and 'Public Internet' clouds. On the right are destinations: 'Enterprise DC', 'Critical applications', and 'None-critical applications'. A red line traces a path from a Branch vCPE/CPE through DSL, a WAN gateway, and a VPN to the Enterprise DC. A blue line traces a path from a Branch vCPE/CPE through Wireless, a WAN gateway, and the Public Internet to None-critical applications. Dashed blue arrows connect the SD-WAN controller to the WAN gateways and vCPE/CPEs. + +**Figure 6-1 – Framework of SD-WAN service** + +As shown in Figure 6-1, a service provider uses an SD-WAN controller dynamically to configure and manage all branch office WAN connections for an enterprise. A service provider's SD-WAN controller can monitor entire network traffic and choose appropriate connections for a specific enterprise. In an access network, a service provider can choose any network access technology, for example, asymmetric digital subscriber line (ADSL) [b- IETF RFC 2662] or wireless access technologies, to connect to the backbone-network. In a backbone-network, a service provider can choose a VPN [b-RFC 4346] to optimize bandwidth usage at a low cost. For example, in some scenarios (blue line), the SD-WAN controller chooses wireless technology and public Internet service which have a lower cost for non-critical applications. While in other scenarios (red line), when CPE/vCPE visits the enterprise data centre, the SD-WAN controller can choose ADSL and multiprotocol label switching (MPLS) channels for the purpose of security. + +# 7 Signalling architecture of SD-WAN service + +![Figure 7-1: Signalling architecture of SD-WAN service. The diagram is divided into two horizontal sections by dashed boxes. The top box is labeled 'Control plane' and contains a box for 'SD-WAN controller'. The bottom box is labeled 'Forwarding plane' and contains boxes for 'vCPE/CPE' and 'WAN gateway' connected by a solid line. Two double-headed arrows labeled 'SFi' connect the 'SD-WAN controller' to the 'vCPE/CPE' and the 'WAN gateway' respectively.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) + +Figure 7-1: Signalling architecture of SD-WAN service. The diagram is divided into two horizontal sections by dashed boxes. The top box is labeled 'Control plane' and contains a box for 'SD-WAN controller'. The bottom box is labeled 'Forwarding plane' and contains boxes for 'vCPE/CPE' and 'WAN gateway' connected by a solid line. Two double-headed arrows labeled 'SFi' connect the 'SD-WAN controller' to the 'vCPE/CPE' and the 'WAN gateway' respectively. + +**Figure 7-1 – Signalling architecture of SD-WAN service** + +Figure 7-1 presents the signalling architecture of the SD-WAN service. The SD-WAN controller in the control plane monitors the status of the forwarding plane, including vCPE/CPE and WAN gateway in the forwarding plane, and exchanges information with the forwarding plane to reveal the most appropriate forwarding solution based on a service provider's policy or business demands. The vCPE/CPE and WAN gateway provide an end-to-end connection for the enterprise. The interface SFi, between the SD-WAN controller and vCPE/CPE or WAN gateway, is responsible for monitoring and configuring information exchange. + +# 8 The information flow of SFi + +The SD-WAN service consists of three procedures: + +- 1) registration, +- 2) statistic collection, and +- 3) dynamic WAN path control. + +This clause provides the information flows of each procedure. + +## 8.1 The information flow of registration and automatic installation + +Figure 8-1 presents the information flow of registration and automatic installation. + +![Sequence diagram showing the information flow of registration and automatic installation between vCPE/CPE/WAN gateway and SD-WAN controller.](053f1077d592e6622cd21dc4bb4cb366_img.jpg) + +``` +sequenceDiagram + participant vCPE/CPE/WAN gateway + participant SD-WAN controller + Note left of vCPE/CPE/WAN gateway: Step 1 + vCPE/CPE/WAN gateway->>SD-WAN controller: Registration request + Note left of vCPE/CPE/WAN gateway: Step 2 + SD-WAN controller-->>vCPE/CPE/WAN gateway: Registration response + Note left of vCPE/CPE/WAN gateway: Step 3 + SD-WAN controller-->>vCPE/CPE/WAN gateway: Configuration request + Note left of vCPE/CPE/WAN gateway: Step 4 + vCPE/CPE/WAN gateway->>SD-WAN controller: Configuration response +``` + +Q.3741(19)\_F8-1 + +Sequence diagram showing the information flow of registration and automatic installation between vCPE/CPE/WAN gateway and SD-WAN controller. + +**Figure 8-1 – Information flow of registration and automatic installation** + +Step 1: vCPE/CPE/WAN gateway registers itself to the SD-WAN controller. + +Step 2: SD-WAN controller responds to the vCPE/CPE/WAN gateway's registration. + +Step 3: SD-WAN controller sends configuration scripts to the vCPE/CPE/WAN gateway. + +Step 4: vCPE/CPE/WAN gateway sends configuration response message to SD-WAN controller to inform the configuration results. + +NOTE 1 – How the vCPE/CPE automatically discovers the controller's IP address is out of scope of this Recommendation. + +NOTE 2 – How IP addresses are allocated to the vCPE/CPE/WAN gateway is out of scope of this Recommendation. + +NOTE 3 – How the SD-WAN controller gets the service requirement is out of scope of this Recommendation. + +NOTE 4 – The specific technologies for the SD-WAN service, such as VPN technologies used for establishing the enterprise virtual WAN network is out of scope of this Recommendation. + +## 8.2 The information flow of statistics collection + +Figure 8-2 presents the information flow of statistics collection. + +![Sequence diagram showing the information flow of statistics collection between vCPE/CPE/WAN gateway and SD-WAN controller.](fe61ee8618403cf584b2e28c4bada03a_img.jpg) + +``` +sequenceDiagram + participant vCPE/CPE/WAN gateway + participant SD-WAN controller + Note left of vCPE/CPE/WAN gateway: Step 1 + SD-WAN controller-->>vCPE/CPE/WAN gateway: Statistics request + Note left of vCPE/CPE/WAN gateway: Step 2 + vCPE/CPE/WAN gateway->>SD-WAN controller: Statistics report +``` + +Q.3741(19)\_F8-2 + +Sequence diagram showing the information flow of statistics collection between vCPE/CPE/WAN gateway and SD-WAN controller. + +**Figure 8-2 – Information flow of statistics collection** + +Step 1: For analysis and path control purpose, the SD-WAN controller sends the statistics request to the vCPE/CPE and WAN gateway at regular time. + +Step 2: The vCPE/CPE and WAN gateway responds with related statistics report to the SD-WAN controller. The statistics include data from the application and network layers. + +The data from the application layer include application type, which is by for the SD-WAN controller to differentiate different applications and application performance metrics, which is used for the SD-WAN controller to evaluate the application performance based on delay, jitter and loss of the protocol (e.g., HTTP, FTP, DNS). + +The data from the network layer includes network performance data, such as packet delay, jitter and loss. + +NOTE – There are lots of technologies used to collect statistics, such as IP flow-performance monitor (IPFPM) and netflow that detect and measure the applications, or two-way active measurement protocol (TWAMP) and network quality analyzer (NQA) that measures network performance. The specific technologies used to collect the statistics are out of scope of this Recommendation. + +## 8.3 The information flow of dynamic WAN path control + +Figure 8-3 presents the information flow of dynamic WAN path control. + +![Sequence diagram showing the information flow of dynamic WAN path control between a vCPE/CPE/WAN gateway and an SD-WAN controller. Step 1: SD-WAN controller sends a 'Link switch over request' to the gateway. Step 2: Gateway sends a 'Link switch over response' back to the controller. A note on the right indicates 'Switch over the links' after Step 2. The diagram is labeled Q.3741(19)_F8-3.](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +``` +sequenceDiagram + participant G as vCPE/CPE/ +WAN gateway + participant C as SD-WAN +controller + C->>G: Step 1 Link switch over request + G->>C: Step 2 Link switch over response + Note right of C: Switch over +the links +``` + +Sequence diagram showing the information flow of dynamic WAN path control between a vCPE/CPE/WAN gateway and an SD-WAN controller. Step 1: SD-WAN controller sends a 'Link switch over request' to the gateway. Step 2: Gateway sends a 'Link switch over response' back to the controller. A note on the right indicates 'Switch over the links' after Step 2. The diagram is labeled Q.3741(19)\_F8-3. + +**Figure 8-3 – Information flow of dynamic WAN path control** + +Step 1: When the SD-WAN controller detects the application or network performance degrading, it requests the vCPE/CPE/WAN gateway to change the links. For example, when a video service has bad performance, the SD-WAN controller will request the vCPE/CPE/WAN gateway to transfer the service to another link which has better network performance. + +Step 2: The vCPE/CPE/WAN gateway sends the link switchover response result to the SD-WAN controller. + +# 9 The signalling requirements of SFi + +## 9.1 vCPE/CPE registration request and response message + +The vCPE/CPE registration request message is defined as CPE-REG-RQ message. + +The CPE-REG-RQ message, indicated by the message type in the message header field, is sent by the vCPE/CPE to the SD-WAN controller to acknowledge itself. + +Message format: + +``` +::= < Message Header > + + * {CPE-Management-Protocol} + + {Software-Version} + + {Hardware-Version} + + {Mac-Address} + + * {Network-Access-Technology} +``` + +Meanings and explanations: + +- 1) `CPE-Management-Protocol`, uniquely specifies the available protocols installed in the vCPE/CPE in order to help the SD-WAN controller manage it, see for example [b-BBF TR069]. +- 2) `Software-Version`, uniquely specifies the software version of the vCPE/CPE. +- 3) `Hardware-Version`, uniquely specifies the hardware version of the vCPE/CPE. +- 4) `Mac-Address`, uniquely specifies the MAC address of the vCPE/CPE to help the SD-WAN controller to identify it. +- 5) `Network-Access-Technology`, uniquely specifies the network access technology. There may be multiple network access technologies. + +The vCPE/CPE registration response message is defined as CPE-REG-RP message. + +The CPE-REG-RP message, indicated by the message type in the message header field, is sent by the SD-WAN controller to the vCPE/CPE to respond to its request. + +Message format: + +``` + ::= < Message Header > + {Selected-CPE-Management-Protocol} + {Device-ID} +``` + +Meanings and explanations: + +- 1) `Selected-CPE-Management-Protocol`, uniquely specifies the protocols selected by the SD-WAN controller. +- 2) `Device-ID`: uniquely specifies the vCPE/CPE identification designated by the SD-WAN controller. + +## 9.2 WAN gateway registration request and response message + +The WAN gateway registration request message is defined as WG-REG-RQ message. + +The WG-REG-RQ message, indicated by the message type in the message header field, is sent by the WAN gateway to the SD-WAN controller to acknowledge itself. + +Message format: + +``` + ::= < Message Header > + {WG-Management-Protocol} + {Software-Version} + {Hardware-Version} + {Mac-Address} + * {Backbone-Network-Connection-Technology} +``` + +Meanings and explanations: + +- 1) `WG-Management-Protocol`, uniquely specifies the available protocols installed in the WAN gateway in order to help the SD-WAN controller to manage it. +- 2) `Software-Version`, uniquely specifies the software version of WAN gateway. + +- 3) `Hardware-Version`, uniquely specifies the hardware version of WAN gateway. +- 4) `Mac-Address`, uniquely specifies the MAC address of the WAN gateway to help the SD-WAN controller to identify it. +- 5) `Backbone-Network-Connection-Technology`, uniquely specifies the backbone-network connection technology. There may be multiple backbone-network connection technologies, e.g., MPLS VPN, IPSec VPN. + +The WAN gateway registration response message is defined as WG-REG-RP message. + +The WG-REG-RP message, indicated by the message type in the message header field, is sent by the SD-WAN controller to the WAN gateway to respond the request. + +Message format: + +``` + ::= < Message Header > + {Selected-WG-Management-Protocol} + {Device-ID} +``` + +Meanings and explanations: + +- 1) `Selected-WG-Management-Protocol`, uniquely specifies the protocols selected by the SD-WAN controller. +- 2) `Device-ID`: uniquely specifies the WAN gateway identification designated by the SD-WAN controller. + +## 9.3 vCPE/CPE configuration request and response message + +The vCPE/CPE configuration message is defined as CPE-CG message. + +The CPE-CG message, indicated by the message type in the message header field, is sent by the SD-WAN controller to the vCPE/CPE to transfer the configuration script. + +Message format: + +``` + ::= < Message Header > + * {SD-WAN-Service-Type-ID} + + {Software-Version} + + {Reboot} + + {Factory-Reset} + + {Upload-Download-Action} + + {Application-Layer-Performance-Detection} + + {Network-Layer-Performance-Detection} +``` + +Meanings and explanations: + +- 1) `SD-WAN-Service-Type-ID`, uniquely indicates the type of SD-WAN service. There may be multiple SD-WAN service types. + +NOTE 1 – The number of SD-WAN service type IDs is equal to the number of network access technologies times the number of backbone connection technologies. + +NOTE 2 – The first SD-WAN service type ID is chosen to be used by default, when the SD-WAN service is established. + +- 2) `Software-Version`, uniquely specifies the target software version for installation. +- 3) `Reboot`, uniquely specifies whether the reboot action is requested. +- 4) `Factory-Reset`, uniquely specifies the factory reset action requested by the SD-WAN controller. +- 5) `Upload-Download-Action`, uniquely specify the upload/download actions which aim to download the software with a specific version from the SD-WAN controller, and upload the real-time running information to the SD-WAN controller. +- 6) `Application-Layer-Performance-Detection`, uniquely specify the tool name and its version, which will be installed in the vCPE/CPE for application layer performance detection, such as IPFPM and netflow, and the related parameters, such as mean opinion score (MOS) value and HTTP response time. +- 7) `Network-Layer-Performance-Detection`, uniquely specify the tool name and its version, which will be installed in the vCPE/CPE for network layer performance detection, and the related parameters, such as TWAMP and NQA, and the related parameters, such as jitter, delay and loss. + +The vCPE/CPE configuration response message is defined as CPE-CGR message. + +The CPE-CGR message, indicated by the message type in the message header field, is sent by the vCPE/ CPE to SD-WAN controller to transfer the configuration response message. + +Message format: + +``` + ::= < Message Header > + {Device-ID-configuration-result} + * {SD-WAN-Service-Type-ID-configuration-result} + {Software-Version-configuration-result} + {Reboot-configuration-result} + {Factory-Reset-configuration-result} + {Upload-Download-Action-configuration-result} + {Application-Layer-Performance-Detection-configuration-result} + {Network-Layer-Performance-Detection-configuration-result} + } +``` + +Meanings and explanations: + +- 1) `Device-ID-configuration-result`, if successfully configured, equals `TRUE`, if not, equals `FALSE`. +- 2) `SD-WAN-Service-Type-ID-configuration-result`, if successfully configured, equals `TRUE`, if not, equals `FALSE`. +- 3) `Software-Version-configuration-result`, if successfully configured, equals `TRUE`, if not, equals `FALSE`. +- 4) `Reboot-configuration-result`, if reboot is configured, equals `TRUE`, if not, equals `FALSE`. +- 5) `Factory-Reset-configuration-result`, if `Factory-Reset` is configured, equals `TRUE`, if not, equals `FALSE`. + +- 6) Upload-Download-Action-configuration-result, if Upload-Download-Action is configured, equals TRUE, if not, equals FALSE. +- 7) Application-Layer-Performance-Detection-configuration-result, if successfully configured, equals TRUE, if not, equals FALSE. +- 8) Network-Layer-Performance-Detection-configuration-result, if successfully configured, equals TRUE, if not, equals FALSE. + +## 9.4 WAN gateway configuration request and response message + +The WAN gateway configuration message is defined as WG-CG message. + +The WG-CG message, indicated by the message type in the message header field, is sent by the SD-WAN controller to the WAN gateway to transfer the configuration script. + +Message format: + +``` + ::= < Message Header > + * {SD-WAN-Service-Type-ID} + {Software-Version} + {Reboot} + {Factory-Reset} + {Upload-Download-Action} + {Application-Layer-Performance-Detection} + {Network-Layer-Performance-Detection} +``` + +Meanings and explanations: + +- 1) SD-WAN-Service-Type-ID, uniquely indicates the type ID of the SD-WAN service. There may be multiple SD-WAN service type IDs. + +NOTE 1 – The number of SD-WAN service type IDs is equal to the number of network access technologies times the number of backbone connection technologies. + +NOTE 2 – The first SD-WAN service type ID is chosen to be used by default, when the SD-WAN service is established. + +- 2) Software-Version, uniquely specifies the target software version for installation. +- 3) Reboot, uniquely specifies whether a reboot action is requested. +- 4) Factory-Reset, uniquely specifies the factory reset action requested by the SD-WAN controller. +- 5) Upload-Download-Action, uniquely specify the upload/download actions which aim to download the software with a specific version from the SD-WAN controller, and upload the real-time running information to the SD-WAN controller. +- 6) Application-Layer-Performance-Detection, uniquely specify the tools, which will be installed in the WAN gateway for application-layer performance detection, such as IPFPM and netflow, and related parameters, such as MOS value and HTTP response time. +- 7) Network-Layer-Performance-Detection, uniquely specify the tools, which will be installed in the WAN gateway for network-layer performance detection, and related parameters, such as TWAMP and NQA, and related parameters, such as jitter, delay and loss. + +The WAN gateway configuration response message is defined as WG-CGR message. + +The WG-CGR message, indicated by the message type in the message header field, is sent by the WAN gateway to SD-WAN controller to transfer the configuration response message. + +Message format: + +``` +< WG-CGR -Message> ::= < Message Header > + {Device-ID-Configuration-result} + + * {SD-WAN-Service-Type-ID-configuration-result} + + {Software-Version-configuration-result} + + {Reboot-configuration-result} + + {Factory-Reset-configuration-result} + + {Upload-Download-Action-configuration-result} + + {Application-Layer-Performance-Detection-configuration-result} + + {Network-Layer-Performance-Detection-configuration-result} + +} +``` + +Meanings and explanations: + +- 1) Device-ID-configuration-result, if successfully configured, equals TRUE, if not, equals FALSE. +- 2) SD-WAN-Service-Type-ID-configuration-result, if successfully configured, equals TRUE, if not, equals FALSE. +- 3) Software-Version-configuration-result, if successfully configured, equals TRUE, if not, equals FALSE. +- 4) Reboot-configuration-result, if reboot is configured, it equals TRUE, if not, equals FALSE. +- 5) Factory-Reset-configuration-result, if Factory-Reset is configured, it equals TRUE, if not, equals FALSE. +- 6) Upload-Download-Action-configuration-result, if Upload-Download-Action is configured, it equals TRUE, if not, equals FALSE. +- 7) Application-Layer-Performance-Detection-configuration-result, if successfully configured, equals TRUE, if not, equals FALSE. +- 8) Network-Layer-Performance-Detection-configuration-result, if successfully configured, equals TRUE, if not, equals FALSE. + +## 9.5 Statistic collection message and response message + +The statistic request message is defined as ST-RQ message. + +The ST-RQ message, indicated by the message type in the message header field, is sent by the SD-WAN controller to the CPE/vCPE/WAN gateway to collect their real-time running information. + +Message format: + +``` + ::= < Message Header > + {SD-WAN-Service-Type-ID} +``` + +Meanings and explanations: + +- 1) `SD-WAN-Service-Type-ID`, uniquely indicates the type ID of the SD-WAN service. + +The statistic response message is defined as ST-RP message. + +The ST-RP message, indicated by the message type in the message header field, is sent by the CPE/vCPE/WAN gateway to the SD-WAN controller to notify their real-time running information. + +Message format: + +``` + ::= < Message Header > + {Delay} + {Jitter} + {Loss} + {MOS-value} + {Http-response-time} +``` + +Meanings and explanations: + +- 1) `Delay`, uniquely specifies the packet delay. +- 2) `Jitter`, uniquely specifies the packet jitter. +- 3) `Loss`, uniquely specifies the packet loss. +- 4) `MOS-value`, uniquely specifies the mean opinion score of video service. +- 5) `Http-response-time`, uniquely specifies the http response time for certain website. + +## 9.6 Dynamic SD-WAN path control for vCPE /CPE request message and response message + +The SD-WAN path change for vCPE/ CPE request configuration message is defined as CPE-Path-RQ message. + +The CPE-Path-RQ message, indicated by the message type in the message header field, is sent by the SD-WAN controller to the vCPE /CPE to switch over the SD-WAN service type. + +Message format: + +``` + ::= < Message Header > + {SD-WAN-Service-type-ID} +``` + +Meanings and explanations: + +- 1) `SD-WAN-Service-Type-ID`, uniquely indicates the target type ID of the SD-WAN service. + +The SD-WAN path change for the vCPE/ CPE response configuration message is defined as CPE-Path-RP message. + +The CPE-Path-RP message, indicated by the message type in the message header field, is sent by the CPE/vCPE to the SD-WAN controller. + +Message format: + +``` + ::= < Message Header > + {SD-WAN-Path-Change-Result} +``` + +Meanings and explanations: + +- 1) `SD-WAN-Path-Change-Result`, uniquely indicates the result of the SD-WAN path change. If the SD-WAN path is changed successfully, `SD-WAN-Path-Change-Result` is `TRUE`, if not, `SD-WAN-Path-Change-Result` is `FALSE` + +## 9.7 Dynamic SD-WAN path control for WAN gateway request message and response message + +The SD-WAN path change for the WAN gateway request configuration message is defined as `WG-Path-RQ` message. + +The `WG-Path-RQ` message, indicated by the message type in the message header field, is sent by the SD-WAN controller to the WAN gateway to switch over the SD-WAN service instance. + +Message format: + +$$\begin{aligned} \langle \text{WG-Path-RQ -Message} \rangle ::= & \langle \text{Message Header} \rangle \\ & \{ \text{SD-WAN-Service-Type-ID} \} \end{aligned}$$ + +Meanings and explanations: + +- 1) `SD-WAN-Service-Type-ID`, uniquely indicates the target type ID of SD-WAN service. + +The SD-WAN path change for the WAN gateway response configuration message is defined as `WG-Path-RP` message. + +The `WG-Path-RP` message, indicated by the message type in the message header field, is sent by the WAN gateway to the SD-WAN controller. + +Message format: + +$$\begin{aligned} \langle \text{WG-Path-RP-Message} \rangle ::= & \langle \text{Message Header} \rangle \\ & \{ \text{SD-WAN-Path-Change-Result} \} \end{aligned}$$ + +Meanings and explanations: + +- 1) `SD-WAN-Path-Change-Result`, uniquely indicates the result of the SD-WAN path change. If `SD-WAN-Path-Change-Result` is `FALSE`. + +## Bibliography + +- [b-ITU-T Y.3300] Recommendation ITU-T Y.3300 (2014), *Framework of software-defined networking*. +- [b-Broadband Forum TR-069] Broadband Forum TR-069 (2013), *CPE WAN Management Protocol*. +- [b-IETF RFC 4364] IETF RFC 4364 (2006), *BGP/MPLS IP Virtual Private Networks (VPNs)*. +- [b-IETF RFC 2662] IETF RFC 2662 (1999), *Definitions of Managed Objects for the ADSL Lines*. + + + + + +## 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/Q/T-REC-Q.3914-201801-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3914-201801-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..05587a651ba3abacde1d7472d7a338b481f5015c --- /dev/null +++ b/marked/Q/T-REC-Q.3914-201801-I_PDF-E/raw.md @@ -0,0 +1,762 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.3914** + +(01/2018) + +SERIES Q: SWITCHING AND SIGNALLING, AND +ASSOCIATED MEASUREMENTS AND TESTS + +Testing specifications – Testing specifications for next +generation networks + +# --- **Set of parameters of cloud computing for monitoring** + +Recommendation ITU-T Q.3914 + +## ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 | +| TESTING SPECIFICATIONS | Q.3900-Q.4099 | +| Testing specifications for next generation networks | Q.3900-Q.3999 | +| Testing specifications for SIP-IMS | Q.4000-Q.4039 | +| Testing specifications for Cloud computing | Q.4040-Q.4059 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T Q.3914 + +# Set of parameters of cloud computing for monitoring + +## Summary + +In accordance with the functional reference architecture of cloud computing that was defined in Recommendation ITU-T Y.3502, Recommendation ITU-T Q.3914 specifies the functional reference architecture of cloud computing according to Recommendation ITU-T Y.3500. This Recommendation provides a set of parameters that indicate the status and event of a cloud computing system, including resource layer, service layer and access layer. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.3914 | 2018-01-13 | 11 | 11.1002/1000/13487 | + +## Keywords + +Cloud computing, monitoring, parameter. + +--- + +\* 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..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Functional reference architecture of cloud computing ..... | 3 | +| 7 Monitoring parameters..... | 4 | +| 7.1 Resource layer parameters..... | 4 | +| 7.2 Service layer parameters..... | 12 | +| 7.3 Access layer parameters ..... | 15 | + + + +## Recommendation ITU-T Q.3914 + +# Set of parameters of cloud computing for monitoring + +# 1 Scope + +This Recommendation specifies the functional reference architecture of cloud computing according to [ITU-T Y.3500], in accordance with the functional reference architecture of cloud computing that was defined in [ITU-T Y.3502]. + +This Recommendation specifies parameters that should be monitored for the status identification of resource, service and management within a cloud system. + +The parameters specified in this Recommendation include: + +- monitoring parameters of the resource layer; +- monitoring parameters of the service layer; +- monitoring parameters of the access layer. + +# 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 Y.3500] Recommendation ITU-T Y.3500 (2014) | ISO/IEC 17788:2014, *Information technology – Cloud computing – Overview and Vocabulary*. + +[ITU-T Y.3502] Recommendation ITU-T Y.3502 (2014) | ISO/IEC 17789:2014, *Information technology – Cloud computing – Reference architecture*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 cloud computing** [ITU-T Y.3500]: Paradigm for enabling network access to a scalable and elastic pool of shareable physical or virtual resources with self-service provisioning and administration on-demand. + +**3.1.2 cloud service** [ITU-T Y.3500]: One or more capabilities offered via cloud computing invoked using a defined interface. + +**3.1.3 cloud service provider** [ITU-T Y.3500]: Party which makes cloud services available. + +**3.1.4 functional component** [ITU-T Y.3502]: A functional building block needed to engage in an activity, backed by an implementation. + +**3.1.5 product catalogue** [ITU-T Y.3502]: A listing of all the cloud service products which cloud service providers make available to cloud service customers. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following term: + +**3.2.1 cloud service user:** Natural person or entity acting on their behalf, associated with a cloud service customer that uses cloud services. + +NOTE – This definition is paraphrased from clause 8.2.1.1 of [ITU-T Y.3502]. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-------------------------------| +| CPU | Central Processing Unit | +| GPU | Graphics Processing Unit | +| IaaS | Infrastructure as a Service | +| I/O | Input/Output | +| IP | Internet Protocol | +| KPI | Key Performance Indicator | +| MDT | Mean Down Time | +| MTBF | Mean Time Between Failures | +| MTTR | Mean Time To Repair | +| NF | Network Function | +| NFS | Network Function Status | +| OSS | Operational Support System | +| PaaS | Platform as a Service | +| QoS | Quality of Service | +| RAM | Random Access Memory | +| SC | Service Chain | +| SDN | Software-Defined Networking | +| SLA | Service Level Agreement | +| TCP | Transmission Control Protocol | +| TBF | Time Between Failures | +| TTR | Time To Repair | +| UPS | Uninterruptible Power System | +| URL | Uniform Resource Locator | +| VIP | Virtual Internet Protocol | +| VM | Virtual Machine | + +# 5 Conventions + +None. + +# 6 Functional reference architecture of cloud computing + +The layering framework used in the cloud computing reference architecture has four layers, plus a set of functions that spans across the layers. The four layers are: + +- user layer; +- access layer; +- services layer; +- resources layer. + +The functions that span layers are called multilayer functions. + +The layering framework is shown schematically in Figure 6-1. + +![Figure 6-1: Cloud computing layering framework diagram. It shows four stacked layers on the left: User layer (white), Access layer (orange), Service layer (light blue), and Resource layer (teal). To the right of these layers is a tall green rectangle labeled 'Multilayer functions' at the top. The diagram is labeled Q.3914(18)_F6-1 at the bottom right.](367926125450c2bc3f4bdca9d59a62ba_img.jpg) + +Diagram illustrating the Cloud computing layering framework. The framework consists of four stacked layers on the left and a single tall green block on the right representing multilayer functions. The layers, from top to bottom, are: User layer (white), Access layer (orange), Service layer (light blue), and Resource layer (teal). The green block is labeled 'Multilayer functions' at the top. The diagram is labeled Q.3914(18)\_F6-1 at the bottom right. + +Figure 6-1: Cloud computing layering framework diagram. It shows four stacked layers on the left: User layer (white), Access layer (orange), Service layer (light blue), and Resource layer (teal). To the right of these layers is a tall green rectangle labeled 'Multilayer functions' at the top. The diagram is labeled Q.3914(18)\_F6-1 at the bottom right. + +**Figure 6-1 – Cloud computing layering framework** + +The function of each layer in the framework is described in clause 9.2.1 of [ITU-T Y.3502]. + +Figure 6-2 presents a high-level overview of the cloud computing reference architecture functional components organized by means of the layering framework. + +The relevant monitoring functional components are as follows. + +- Resource abstraction and control functional component: the resource abstraction and control functional component which resides in the resources layer enables control functionality, enabling monitoring and management capabilities implemented in the operational support systems functional component. + +Monitoring and reporting functional component: the monitoring and reporting functional component that is one of the multilayer operational support systems provides capabilities for the following. + +- Monitoring the activities of other functional components throughout the cloud provider's system. This includes the functional components that are involved in the direct use of cloud services by customer cloud service users such as service access and service implementation (e.g., the invocation of cloud service operation by a particular user). This also includes functional components involved in the support of cloud services, such as functional components in the operational support system (OSS) itself, like the service automation functional component (e.g., the provisioning of a service instance for a particular customer). +- Providing reports on the behaviour of the cloud service provider's system, which may take the form of alerts for behaviour that has a time-sensitive aspect (e.g., the occurrence of a fault, the completion of some task) or may take the form of aggregated forms of historical data (e.g., service usage data). +- Storage and retrieval of monitoring and event data as logging records. + +Service level management functional component: the service level management functional component, which also resides in the operational support systems, obtains monitoring information from the monitoring and reporting functional component in order to measure and record key performance indicators (KPIs) for the cloud service. Capacity is allocated or de-allocated based on the basis of these KPIs. + +The details of the functional components are described in clause 9.2 of [ITU-T Y.3502]. + +![Functional components of the cloud computing reference architecture diagram showing four layers (User, Access, Service, Resource) and five Multilayer functions (Integration, Security systems, Operational support systems, Business support systems, Development function).](cfda9df1319e04207eb28bcefd1dab7b_img.jpg) + +| User layer | | | Multilayer functions | | | | | +|---------------|-------------------|------------------------|--------------------------|---------------------------------------------|----------------------------------------|--------------------------|-----------------------| +| User function | Business function | Administrator function | Integration | Security systems | Operational support systems | Business support systems | Development function | +| | | | Security integration | Authentication and identity management | Service catalogue | Product catalogue | Developer environment | +| | | | Monitoring integration | Authorization and service policy management | Provisioning | Account management | | +| | | | Service integration | Encryption management | Monitoring and reporting | Subscription management | Build management | +| | | | Peer service integration | | Service policy management | Billing | | +| | | | | | Service automation | Accounts | Test management | +| | | | | | Service level management | | | +| | | | | | Incident and problem management | | | +| | | | | | Platform and virtualization management | | | +| | | | | | Peer service management | | | + + + +| Access layer | | | +|----------------|-----------------------|--| +| Access control | Connection management | | + + + +| Service layer | | | +|-----------------------|-----------------------|-----------------------------| +| Service capabilities | Business capabilities | Administration capabilities | +| Service orchestration | | | + + + +| Resource layer | | | +|----------------------------------|--|--| +| Resource abstraction and control | | | +| Physical resources | | | + +Functional components of the cloud computing reference architecture diagram showing four layers (User, Access, Service, Resource) and five Multilayer functions (Integration, Security systems, Operational support systems, Business support systems, Development function). + +Q.3914(18)\_F6-2 + +**Figure 6-2 – Functional components of the cloud computing reference architecture** + +# 7 Monitoring parameters + +Monitoring cloud resources and services is a key tool that helps cloud computing providers and consumers in designing, building and improving a cloud system, eliminating performance bottlenecks and identifying security flaws. Applications (e.g., streaming, web, indexing, compute and storage services) are distributed across cloud layers including platform as a service (PaaS) and infrastructure as a service (IaaS). In consequence, all parameters performed across all layers of the cloud stack need to be metered and monitored. These include not only cloud resource and network access, but also deployed services and applications. + +## 7.1 Resource layer parameters + +The resources layer is where the physical and virtual resources, as well as generic software, reside. This layer includes equipment typically used in a data centre such as servers, networking switches and routers, storage devices, in addition to the corresponding non-cloud specific software that runs on the servers and other equipment such as host operating systems, hypervisors, device drivers and generic systems management software. + +### 7.1.1 Physical computing resources + +Physical computing resources include any hardware within a computer system for running an operating system and software. An IaaS administrator can add physical computing resources to or remove physical computing resources from a virtual machine (VM). + +In order to ensure that the deployed software and hardware resources run at the required level to satisfy the service level agreement (SLA), a continuous physical resource monitoring process is desirable. + +Processors, memory and disks are basic computing and storage resources. Monitoring these resources can detect system failures or corruption before they become completely non-recoverable. So, monitoring functions and status of these resources to ensure system availability benefits users. + +See Table 7-1. + +**Table 7-1 – Parameters collected to monitor physical computing resources** + +| Metric name | Description | Unit | +|-------------------------------------------|-----------------------------------------|-----------| +| Central processing unit (CPU) frequency | CPU frequency | MHz | +| CPU util | Average CPU utilization | % | +| CPU idle time | Time of CPU is in idle status | ns | +| CPU load | CPUs have been loaded | process | +| CPU input/output (I/O) wait time | CPU I/O wait time | ns | +| CPU idle percent | Percent of CPU is in idle status | % | +| CPU user percent | Percent of CPU is in using status | % | +| CPU I/O wait percent | Percent of CPU I/O is in waiting status | % | +| memory | Volume of random access memory (RAM) | MB | +| memory util | Average RAM utilization | % | +| memory used | Used physical memory size | kB | +| disk size | Total size of disk | GB or TB | +| disk size used | Total size of disk used | GB or TB | +| disk random/sequential read requests | Volume of read requests | request | +| disk random/sequential read request rate | Average rate of read requests | request/s | +| disk random/sequential read delay | Average delay of read request | ms | +| disk random/sequential read error | Volume of read error | kB | +| disk random/sequential write requests | Volume of write requests | request | +| disk random/sequential write request rate | Average rate of write requests | request/s | +| disk random/sequential write delay | Average delay of write request | ms | +| disk random/sequential write error | Volume of write error | kB | +| disk random/sequential read bytes | Volume of reads | MB | +| disk random/sequential read byte rate | Average rate of reads | MB/s | +| disk random/sequential write bytes | Volume of writes | MB | +| disk random/sequential write byte rate | Average rate of writes | MB/s | +| Graphics processing unit (GPU) util | Average GPU utilization | % | +| GPU idle time | Time of GPU is in idle status | ns | +| GPU load | GPUs have been loaded | process | +| GPU I/O wait time | GPU I/O wait time | ns | +| GPU idle percent | Percent of GPU is in idle status | % | +| GPU user percent | Percent of GPU is in using status | % | +| GPU I/O wait percent | Percent of GPU I/O is in waiting status | % | + +**Table 7-1 – Parameters collected to monitor physical computing resources** + +| Metric name | Description | Unit | +|-------------------------------------------------------------------------------------------------------|-------------|------| +| NOTE – All metrics should be measured over different durations, e.g., 1 min, 5 min, 15 min or 30 min. | | | + +### **7.1.2 Virtual computing resources** + +Virtual computing resources include any virtual component within a virtual computer system for running an operating system, software and applications. Similarly to physical computing resources, running data and status of resources from VMs in which the applications are currently running require collection. These data provide a picture of how much of the VM is being utilized and helps in analysis and determination of the scaling requirement of applications. + +See Table 7-2. + +**Table 7-2 – Parameters collected to monitor virtual computing resources** + +| Metric name | Description | Unit | +|--------------------------------------------|--------------------------------------------------------------|-----------| +| vCPUs | Number of virtual CPUs allocated to the virtual machine (VM) | CPU | +| vCPU idle time | Time of virtual CPUs is in idle status | ns | +| vCPU idle percent | Percent of vCPU is in idle status | % | +| vCPU user percent | Percent of vCPU is in using status | % | +| vCPU load | Virtual CPUs have been loaded | process | +| vCPU I/O wait time | Time of virtual CPUs I/O is in waiting status | ns | +| vCPU I/O wait percent | Percent of virtual CPU is in using status | % | +| vMemory | Volume of virtual RAM allocated to the VM | MB | +| vMemory utilization | Average virtual RAM utilization | % | +| vMemory used | Used virtual memory size | MB | +| vDisk size | Total size of virtual disk allocated to the VM | GB | +| vDisk size used | Total size of virtual disk used | MB | +| vDisk random/sequential read requests | Number of read requests of virtual disk | request | +| vDisk random/sequential read request rate | Average rate of read requests of virtual disk | request/s | +| vDisk random/sequential write requests | Number of write requests of virtual disk | request | +| vDisk random/sequential write request rate | Average rate of write requests of virtual disk | request/s | +| vDisk random/sequential read bytes | Volume of reads of virtual disk | kB | +| vDisk random/sequential read byte rate | Average rate of reads of virtual disk | kB/s | +| vDisk random/sequential read delay | Average delay of read request | ms | +| vDisk random/sequential read error | Volume of read error | kB | +| vDisk random/sequential write bytes | Volume of writes of virtual disk | kB | + +**Table 7-2 – Parameters collected to monitor virtual computing resources** + +| Metric name | Description | Unit | +|------------------------------------------------------------------------------------------------------|------------------------------------------|---------| +| VDisk random/sequential write byte rate | Average rate of writes of virtual disk | kB/s | +| vDisk random/sequential write delay | Average delay of write request | ms | +| vDisk random/sequential write error | Volume of write error | kB | +| vGPU util | Average vGPU utilization | % | +| vGPU idle time | Time of vGPU is in idle status | ns | +| vGPU load | vGPUs have been loaded | process | +| vGPU I/O wait time | vGPU I/O wait time | ns | +| vGPU idle percent | Percent of vGPU is in idle status | % | +| vGPU user percent | Percent of vGPU is in using status | % | +| vGPU I/O wait percent | Percent of vGPU I/O is in waiting status | % | +| NOTE – All metrics should be measured over different duration, e.g., 1 min, 5 min, 15 min or 30 min. | | | + +### 7.1.3 Virtual machine operation and control + +VM operation and control are referred to the management of physical or virtual computing resources that allow users to create, edit, start and stop VMs. + +The impetus behind cloud computing is the ever-increasing demand to manage growth and increase computing flexibility by dynamic resource operation and control based on demand. An example of resource control operation could be to horizontally scale a database server by migrating it from a small CPU resource configuration to an extra-large CPU resource to improve throughput. This basic requirement of cloud computing is supported by the resource operation and control system. An inefficient resource operation and control system has a direct negative effect on performance. It can also indirectly affect system functionality. Some system functions provided might become ineffective due to poor performance. + +See Table 7-3. + +**Table 7-3 – Parameters collected to monitor VM operation and control** + +| Metric name | Description | Unit | +|-------------------------|---------------------------|------| +| CPU of VM start | Time of CPU start | s | +| CPU of VM stop | Time of CPU stop | s | +| CPU of VM restart | Time of CPU restart | s | +| CPU of VM select | Time of CPU select | s | +| CPU of VM scale down | Time of CPU scale down | s | +| CPU of VM scale up | Time of CPU scale up | s | +| VM start | Time of VM start | s | +| VM acquisition | Time of VM acquisition | s | +| VM release | Time of VM release | s | +| memory of VM scale down | Time of memory scale down | s | +| memory of VM scale up | Time of memory scale up | s | +| disk of VM scale down | Time of disk scale down | s | + +**Table 7-3 – Parameters collected to monitor VM operation and control** + +| Metric name | Description | Unit | +|----------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|------| +| disk of VM scale up | Time of disk scale up | s | +| upload file | Time of upload file | s | +| download file | Time of download file | s | +| allocation Internet protocol (IP) | Time of allocation IP | s | +| allocation ports | Time of allocation ports | s | +| allocation URL | Time of allocation uniform resource locator (URL) | s | +| VM live migration | Time that is needed to move a VM from two predefined resources | s | +| migration Interruption Time | Maximum time in which a customer has no access to migration to the resource | s | +| VM cloning | Time of VM cloning | s | +| VM backup | Time of VM backup | s | +| VM imaging | Time of VM imaging | s | +| recovery time | Time from the failure of a storage, to the successful restore from an existing backup | s | +| NOTE – VM backup time interval varies according to backup type, e.g., full backup or incremental backup. | | | + +### 7.1.4 Network + +High-performance computing requires large amounts of network bandwidth. Particularly for cloud computing, the network has a strong meaning, as all provided resources and services are available through a network. It has been found that poor network performance is caused by virtualization I/O overhead. A network monitoring system helps in realization of traffic, utilization and errors and then, based on accurate monitoring information, quality of service (QoS) policy validation, network outage resolution, performance problem troubleshooting, and in making important capacity planning decisions. + +See Table 7-4. + +**Table 7-4 – Parameters collected to monitor a network** + +| Metric name | Description | Unit | +|----------------------------|--------------------------------------------------------------------------------------|--------| +| incoming bytes | Number of bytes received by network interface | KB | +| incoming byte rate | Average rate of bytes received by network interface per second | KB/s | +| maximum incoming byte rate | Maximum incoming byte rate during a specific period (5 minute/15 minutes/60 minutes) | KB/s | +| outgoing bytes | Number of bytes sent by network interface | KB | +| outgoing byte rate | Average rate of bytes sent by network per second | KB/s | +| maximum outgoing byte rate | Maximum outgoing byte rate (5 minute/15 minutes/60 minutes) | KB/s | +| incoming packets | Number of incoming packets | packet | + +**Table 7-4 – Parameters collected to monitor a network** + +| Metric name | Description | Unit | +|-----------------------------------|----------------------------------------------------------------------------------|-------------| +| incoming packet rate | Average rate of incoming packets per second | packet/s | +| average packets size incoming | Average packets size incoming (1 minute/5 minutes/15 minutes) | byte | +| outgoing packets | Number of outgoing packets | packet | +| outgoing packet rate | Average rate of outgoing packets per second | packet /s | +| average packets size outgoing | Average packets size outgoing (1 minute/5 minutes/15 minutes) | byte | +| outgoing errors | Sending error of network interface | packet | +| bandwidth of incoming | Total capacity of the connection of the incoming | Mb | +| utilization of incoming interface | Percentage of incoming byte rate with respect to bandwidth of incoming. | % | +| bandwidth of outgoing | Total capacity of the connection of the outgoing | Mb/s | +| utilization of outgoing interface | Percentage of outgoing byte rate with respect to bandwidth of outgoing link. | % | +| average latency | Average of delay of data transition | ms | +| Minimum latency | Minimum time interval between submitting a packet and arrival at its destination | ms | +| Maximum latency | Maximum time interval between submitting a packet and arrival at its destination | ms | +| packet loss | Percentage of packets lost with respect to packets sent. | % | +| jitter | The difference in end-to-end one-way delay | ms | + +### **7.1.5 Software-defined networking** + +Software-defined networking (SDN) is a concept that enables network operators and data centres to flexibly manage their networking equipment using software. SDN introduces new levels of flexibility and automation without manual interaction for networking. + +#### **7.1.5.1 Software-defined networking-based network** + +Network setup in SDN is now separated from a network engineer's regular activities; network issue troubleshooting and diagnosis have become more complex. The availability, performance, utilization and capacity of SDN monitoring can enable a cloud computing provider more confidently to adopt SDN in cloud computing. + +See Table 7-5 + +**Table 7-5 – Parameters collected to monitor a software-defined networking controller** + +| Metric name | Description | Unit | +|----------------------------------------------------|-----------------------------------------------------------------------------|-------------| +| latency of topology discovery | Latency of topology discovery | ms | +| latency of connection from switch to controller | Latency of connection from switch to controller | ms | +| number of active switches | Number of active switches | switch | +| incoming packets of the same source addresses | Numbers of incoming packets with the same incoming source addresses | packet | +| incoming packets of the same destination addresses | Numbers of incoming packets with the same incoming destination addresses | packet | +| outgoing packets of the same source addresses | Numbers of outgoing packets with the same outgoing source addresses | packet | +| outgoing packets of destination addresses | Numbers of outgoing packets with the same outgoing destination addresses | packet | +| incoming packets of the same source port | Numbers of incoming packets with the same incoming source port numbers | packet | +| incoming packets of the same destination port | Numbers of incoming packets with the same incoming destination port number | packet | +| outgoing packets of the same source port | Numbers of outgoing packets with the same outgoing source port numbers | packet | +| outgoing packets of the same destination port | Numbers of outgoing packets with the same outgoing destination port numbers | packet | + +#### 7.1.5.2 Service chain + +Cloud computing provides not only computing and storage resources to consumers as a resource pool, but also as a network resource pool. According to appointed service logic, network traffic passes through several service points (generally reference is made to firewall, load balance or any other network functions (NFs)). A service chain (SC) links these service points together. A cloud computing provider should consider the performance and status of an SC when it provides service to consumers. + +See Table 7-6. + +**Table 7-6 – Parameters collected to monitor a service chain** + +| Metric name | Description | Unit | +|--------------------|----------------------------------------------------------------|-------------| +| NFS | Network function status | normal/fail | +| NF start | Time of network function start | s | +| NF stop | Time of network function stop | s | +| NF migration | Time that is needed to move a NF from two predefined resources | s | +| SC start | Time of a service chain established | s | +| SC stop | Time of a service chain destroy | s | + +### 7.1.6 Energy consumption + +Voltage or power use out of the permissible range can damage electrical components or cause system failure. If the fan stops working, the server overheats, is damaged and goes out of service. So, it is + +important to monitor the voltage or wattage, fan and temperature to ensure that they are within safe operating limits. + +In order to handle massive amounts of data generated by consumers and businesses, cloud computing typically needs a lot of power. A sharp increase in energy consumption can indicate server load unbalance that leads to performance degradation. Real-time monitoring is helpful for avoiding these consequences. Different states of the physical or VMs require different power levels. These states can normally be divided into six types: named as shutdown, work, idle, dormant, sleep and standby. + +See Table 7-7. + +**Table 7-7 – Parameters collected to monitor energy consumption in each state** + +| Metric name | Description | Unit | +|------------------------|-------------------------------------------|------| +| power of CPU | Current power of CPU consumption | w | +| power of GPU | Current power of GPU consumption | w | +| power of Memory | Current power of Memory consumption | w | +| power of storage | Current power of storage consumption | w | +| power of network | Current power of disk consumption | w | +| power of power Systems | Current power of power system consumption | w | +| temperature of CPU | Current temperature of CPU | °C | + +### 7.1.7 Environment + +The server room environment requires strict control processes for temperature, humidity and power supply. A fully automated monitoring system can help prevent overheating of servers and condensation on equipment. Keeping temperatures within range and carefully monitoring humidity to prevent corrosion or static electricity reduce energy consumption and keep servers running smoothly. Voltage use out of the permissible range can damage electrical components or cause system failure. If the fan stops working, the server overheats, is damaged and goes out of service. So, it is important to monitor the voltage or wattage, fan and temperature to ensure that they are within safe operating limits. + +See Table 7-8. + +**Table 7-8 – Parameters collected for the monitoring environment** + +| Metric name | Description | Unit | +|-------------------------------|-----------------------------------------------------------------|---------------| +| temperature | Current temperature of server room | °C | +| voltage | Current voltage of electricity supply | V | +| electric current | Electric current of electricity supply | A | +| UPS voltage | Output voltage of an uninterruptible power system (UPS) battery | V | +| UPS output electric current | Output electric current of UPS battery | A | +| UPS charging electric current | Electric current of charging | A | +| humidity | Relative humidity of server room | % | +| fan rotations | Fan rotations per minute | rotations/min | +| power of fan | Current power of fan consumption | W | + +## 7.2 Service layer parameters + +### 7.2.1 General + +One of the most important areas for provider and consumer is service performance and availability when it comes to cloud computing. Cloud service provider and consumer need to get an entire view of the health of service. A lot of decision making and SLA determination are driven by service performance and availability. The monitoring system should report the service performance and availability parameters to identify whether the QoS specified in the SLA is fulfilled. + +Different cloud services can be offered with different terminologies, specifications and features. Cloud services can achieve different levels of performance under various workloads generated by diverse applications. For example, unlike computation and communication-intensive applications, performance of data-intensive applications typically will be strongly affected by I/O performance and storage access in a cloud infrastructure. The monitoring parameters of typical services are included in this clause. Others are for further study. + +See Table 7-9. + +**Table 7-9 – Performance metrics for monitoring general cloud services** + +| Category | Metric name | Description | +|--------------|------------------|---------------------------------------------------------------------------------| +| Availability | MTBF | Mean time between failures | +| | MTTR | Mean time to repair | +| Performance | Response time | Response time for composite or atomic service | +| | Throughput | Number of transactions or requests processed per specified unit of time | +| Capacity | Bandwidth | Bandwidth of the connection that supports a service | +| | Storage capacity | Capacity of a temporary or persistent storage medium, such as RAM, disk or tape | + +### 7.2.2 Service availability + +Service availability is the property of being accessible and usable upon demand by an authorized entity. Continuity is the key feature used to measure service availability, which ensures the service is available for a certain amount of time without any interruption. Furthermore, if there is an incident, continuity enables the service to be restarted and access to data and functionality of the service regained within a particular period. All elements, including computing, storage, network and power supplement, can affect service continuity. For example, for a public-cloud end user, availability of the cloud not only refers to the services provided by the cloud service provider, but also to the possibility of accessing those services remotely. + +See Table 7-10. + +**Table 7-10 – Parameters collected for monitoring service availability** + +| Metric name | Description | Unit | +|-----------------------------------|-----------------------------------------------------------------------|------| +| mean time between failures (MTBF) | Time between inherent failures of element or service during operation | h | +| maximum TBF | Maximum time between failures | h | +| minimum TBF | Minimum time between failures | h | +| mean time to repair (MTTR) | The average time repair a failed element or service | h | + +**Table 7-10 – Parameters collected for monitoring service availability** + +| Metric name | Description | Unit | +|----------------------|-------------------------------------------------------------------------------------------------------------------|------| +| maximum TTR | Maximum time to repair | h | +| minimum TTR | Minimum time to repair | h | +| mean down time (MDT) | The average time that an element or service is non-operational. This includes all downtime associated with repair | h | +| maximum down time | Maximum time of down | h | +| minimum down time | Minimum time of down | h | + +### 7.2.3 Service performance + +#### 7.2.3.1 Transaction process + +Transaction process metrics can give a clear picture of the performance of an application in a cloud, such as response time to complete service requests and transaction rate at which service requests are executed. Latency for service requests, which calculates the time taken for the application to respond to user requests, is the key metric. + +See Table 7-11. + +**Table 7-11 – Parameters collected for monitoring the transaction process** + +| Metric name | Description | Unit | +|-------------------------|--------------------------------------------------------------------|---------------| +| transactions | Number of transactions during a period (1 min, 5 min, 15 min) | transaction | +| transaction rate | Transaction rate at which service requests are executed per second | transaction/s | +| errors | Number of error transactions | transaction | +| concurrent transactions | Average number of new transactions processed simultaneously | transaction | +| time per transactions | Average time necessary to process a single transactions item | ms | +| disk throughput rate | Throughput rate (input and output) for a specific service | kB/s | +| memory throughput rate | Throughput rate (input and output) for a specific service | kB/s | +| delay | Delay of message passing between processes | ms | +| time of task | Duration of specific predefined tasks | ms | + +#### 7.2.3.2 Load balance + +Load balancing of cloud computing is the process of distributing workloads across multiple computing resources, which provides an efficient solution to various issues residing in cloud computing environment usage. + +See Table 7-12. + +**Table 7-12 – Parameters collected for monitoring the efficiency and effectiveness of load balancing** + +| Metric name | Description | Unit | +|---------------------------------|-----------------------------------------------------|------------| +| load balance pool | Number of load balance pools | pool | +| load balance VIPs | Number of virtual internet protocol (VIP) addresses | member | +| load balance member | Number of load balance member | member | +| load balance health monitor | Number of Load balance health monitor | monitor | +| load balance connections | Volume of Load balance connections | connection | +| load balance active connections | Volume of Load balance active connections | connection | +| load balance incoming bytes | Volume of Load balance incoming bytes | MB | +| load balance outgoing bytes | Volume of Load balance outgoing bytes | MB | + +#### 7.2.3.3 Database + +A cloud database is a database that typically runs on a cloud computing platform. Poor database performance can dramatically degrade QoS. Cloud providers who offer database as a service, without physically launching a VM instance for the database, should have a clear picture of how a database is running and what is needed by consumers. + +A relational database is organized based on the relational model of the data. A non-relational database provides a mechanism for storage and retrieval of data that is modelled by means other than the tabular relations used in relational databases. Non-relational databases are increasingly used in big data and real-time web applications. The operation mechanisms of the two types of databases are entirely different. So relational and non-relational databases should be monitored separately. + +See Table 7-13. + +**Table 7-13 – Parameters collected for monitoring database efficiency** + +| Metric name | Description | Unit | +|-------------------------------------|----------------------------------------------------------------------|-----------| +| space | Total space of DB | kB | +| space used | Total space used of DB | kB | +| queries | Total number of DB queries (select, insert, update, delete, replace) | query | +| replace request | Volume of replace requests | request | +| replace request rate | Average rate of replace requests per second | request/s | +| response time of replace request | Average time of responding replace request | ms | +| insert/set request | Volume of insert/set requests | request | +| insert/set request rate | Average rate insert/set request of per second | request/s | +| response time of insert/set request | Average time of responding insert/set request | ms | +| update request | Volume of update requests | request | +| update request rate | Average rate of update requests per second | request/s | +| response time of update request | Average time of responding update request | ms | +| delete request | Volume of delete requests | request | +| delete request rate | Average rate of delete requests per second | request/s | +| response time of delete request | Average time of responding delete request | ms | + +**Table 7-13 – Parameters collected for monitoring database efficiency** + +| Metric name | Description | Unit | +|-------------------------------------|-------------------------------------------------|-------------| +| select/get request | Volume of select requests | request | +| select/get request rate | Average rate of select requests per second | request/s | +| response time of select/get request | Average time of responding select/get request | ms | +| connect | Connection number of concurrent clients | request | +| connect rate | Average rate of connections per second | request/s | +| slow/expired query | Volume of slow/expired queries | query | +| slow/expired query rate | Average rate of slow/expired queries per second | request/s | + +#### 7.2.3.4 Web service performance + +The main function of the web server is to provide an online information browsing service. There are three types of performance parameter for web service: throughput, concurrent transactions and response time. + +See Table 7-14. + +**Table 7-14 – Parameters collected for monitoring web service performance** + +| Metric name | Description | Unit | +|--------------------------|--------------------------------------------------------------------------------------------------------------|---------------| +| throughput | Number of service request that a web service can complete in a given period of time | request/s | +| users | Number of new connection users servicing per second | user/s | +| transactions per second | Average number of transactions processed per second | transaction/s | +| connection rate | Number of new transmission control protocol (TCP) connections setting up per second | link/s | +| response time | The time duration from receiving the request to the web service to sending the response from the web service | ms | +| round trip time | Time from sending SYN to receiving SYN ACK | ms | +| TCP setting up time | Average time of TCP link setting up | | +| simultaneous connections | Number of TCP connections setting up between client and server | link/s | +| cumulative transactions | Total number of transactions processing processed | transaction | + +## 7.3 Access layer parameters + +Principally, access control involves the authentication of a user through the presentation and validation of credentials, followed by the authorization of this authenticated user to use specific services. Associated with this is identity management. Access behaviour and management events should be monitored for the access layer. + +See Table 7-15. + +**Table 7-15 – Parameters collected for monitoring the access layer** + +| Metric name | Description | Unit | +|---------------------------------|----------------------------------------------------|-------------| +| account entries | Number of successful account logon events | event | +| unsuccessful account entries | Number of unsuccessful account logon events | event | +| account exits | Number of account logout events | event | +| create account | Number of successful account creation events | event | +| modify account | Number of successful account modification events | event | +| delete account | Number of successful account deletion events | event | +| unsuccessful account management | Number of unsuccessful account management events | event | +| policy change | Number of successful policy change events | event | +| unsuccessful policy change | Number of unsuccessful policy change events | event | +| data deletions | Number of successful data deletion events | event | +| unsuccessful data deletions | Number of unsuccessful data deletion events | event | +| data access | Number of successful data access events | event | +| unsuccessful data access | Number of unsuccessful data access events | event | +| data changes | Number of successful data changes events | event | +| unsuccessful data changes | Number of unsuccessful data change events | event | +| unauthorized access, | Number of unauthorized service access events | event | +| unauthorized modification | Number of unauthorized service modification events | event | +| unauthorized deletion | Number of unauthorized service deletion events | event | + + + +## 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/Q/T-REC-Q.3960-201607-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/Q/T-REC-Q.3960-201607-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc8e8b191ab1dc49f0485920692d0148a2eba8c7 --- /dev/null +++ b/marked/Q/T-REC-Q.3960-201607-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f60f8e74cb92f492328ad21c072588f0ea7e5c58e9aea9c1c003e37c775cebad +size 27799 diff --git a/marked/Q/T-REC-Q.3960-201607-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/Q/T-REC-Q.3960-201607-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22dc7ff0fb30f976cc1e576c45d2b7e65fa5ddc7 --- /dev/null +++ b/marked/Q/T-REC-Q.3960-201607-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa14933e776f7d0be8b2d60b81cbb6c1ee49deb5080e0281da05296f48189055 +size 6859 diff --git a/marked/Q/T-REC-Q.3960-201607-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/Q/T-REC-Q.3960-201607-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ea662276583b0727e515fe43515e142d8b6b5d1 --- /dev/null +++ b/marked/Q/T-REC-Q.3960-201607-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83b3c9ec283282c6317dbc8ceeeb4f9a862035e894c31ccb120885e6d98c1303 +size 27622 diff --git a/marked/Q/T-REC-Q.3960-201607-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/Q/T-REC-Q.3960-201607-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5aeb44eeb048ebe710c2d96bc6d5940bb162217e --- /dev/null +++ b/marked/Q/T-REC-Q.3960-201607-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd666911528155c9e57adec26f89d9e80e4c72c5cffe61eeb7b33eed27c9c6d7 +size 35270 diff --git a/marked/Q/T-REC-Q.3960-201607-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg b/marked/Q/T-REC-Q.3960-201607-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b358fb32442cb80625087afe98d496fc1ca5fe08 --- /dev/null +++ b/marked/Q/T-REC-Q.3960-201607-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:737fc192e1b84d1a1bf31410197d7fa0eb463d2d96da65ff4e1ffbfad404bb97 +size 34865 diff --git a/marked/Q/T-REC-Q.3960-201607-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.3960-201607-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4eff1c74166c4637da1da14a909e55135fd2b3d9 --- /dev/null +++ b/marked/Q/T-REC-Q.3960-201607-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9749668230bfa9d4eea73cd0fd14dcc945bef9b21f2c7cb2f6d292fb22afbad +size 61793 diff --git a/marked/Q/T-REC-Q.3960-201607-I_PDF-E/d17f75945bbb3feb84a153ecfedb9b81_img.jpg b/marked/Q/T-REC-Q.3960-201607-I_PDF-E/d17f75945bbb3feb84a153ecfedb9b81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2be85bbe74e61652d67be546bc5a5db639cdc51 --- /dev/null +++ b/marked/Q/T-REC-Q.3960-201607-I_PDF-E/d17f75945bbb3feb84a153ecfedb9b81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2278d798605f5e61947348ef821d82e565a051cb1d33baa58aa4b3cd4a5cd90 +size 23831 diff --git a/marked/Q/T-REC-Q.3960-201607-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Q/T-REC-Q.3960-201607-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7defcda7e9f9cf3ac08ed0229251564a925ba1d2 --- /dev/null +++ b/marked/Q/T-REC-Q.3960-201607-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f2a3a32002e882bf7f963906c535f21bf276ba51fcd783e0eeb6d9735ffd58d +size 43782 diff --git a/marked/Q/T-REC-Q.3960-201607-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/Q/T-REC-Q.3960-201607-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b7cb077a7445ad21189548bd246638258dd9e58 --- /dev/null +++ b/marked/Q/T-REC-Q.3960-201607-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51b3a2af352f4323bc8f2aecac63fea89a76861afc5e3a4979179d31c3ee20fe +size 31746 diff --git a/marked/Q/T-REC-Q.4003.3-201602-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4003.3-201602-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..53e1173cec150243258fd14cb84421017ce5ac10 --- /dev/null +++ b/marked/Q/T-REC-Q.4003.3-201602-I_PDF-E/raw.md @@ -0,0 +1,829 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.4003.3** + +(02/2016) + +SERIES Q: SWITCHING AND SIGNALLING + +Testing specifications – Testing specifications for SIP-IMS + +--- + +**Communication HOLD using IP multimedia core +network subsystem; Conformance testing – +Part 3: User side; Test suite structure and test +purposes** + +Recommendation ITU-T Q.4003.3 + +## ITU-T Q-SERIES RECOMMENDATIONS + +## SWITCHING AND SIGNALLING + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3899 | +| TESTING SPECIFICATIONS | Q.3900–Q.4099 | +| Testing specifications for next generation networks | Q.3900–Q.3999 | +| Testing specifications for SIP-IMS | Q.4000–Q.4039 | +| Testing specifications for Cloud computing | Q.4040–Q.4059 | + +For further details, please refer to the list of ITU-T Recommendations. + +## Recommendation ITU-T Q.4003.3 + +# Communication HOLD using IP multimedia core network subsystem; Conformance testing – Part 3: User side; Test suite structure and test purposes + +## Summary + +Recommendation ITU-T Q. 4003.3 v.1 (2016) is part 3 of the testing specifications for HOLD service implemented on IP multimedia subsystem (IMS) basis on the user side. The Recommendation specifies the test suite structure and test purposes (TSS&TP) which can be used for testing against the Recommendation ITU-T Q.3619 v.1, "*Communication HOLD using IP multimedia core network subsystem – Protocol specification*". + +The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.4003.3 and that it relates to Release 10 of the relevant 3GPP/ETSI standard. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|--------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.4003.3 v.1 | 2016-02-13 | 11 | 11.1002/1000/12735 | + +## Keywords + +HOLD, IP multimedia subsystem, IMS, network side, protocol implementation conformance statement, PICS, session description protocol, SDP, session initiation protocol, SIP, testing, user side. + +--- + +\* 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 2016 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Recommendation ITU-T Q.4003.3 + +## Communication HOLD using IP multimedia core network subsystem; Conformance testing – Part 3: User side, Test suite structure and test purposes + +## 1 Scope + +This Recommendation provides the test suite structure (TSS) and test purposes (TP) for the test specifications for the communication HOLD on the user side using IP multimedia (IM) core network (CN) subsystem as specified in [ITU-T Q.3619 v.1] and [IETF RFC 3264] in compliance with the relevant requirements and in accordance with the relevant guidance given in [ITU-T X.296]. + +This Recommendation can be used for compliance testing against [ITU-T Q.3619 v.1] "Communication HOLD using IP multimedia core network subsystem – Protocol specification" on the user side. + +The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.4003.3, and that it relates to Release 10 of the relevant 3GPP/ETSI standard. + +## 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 Q.3619 v.1] Recommendation ITU-T Q.3619 v.1 (2016), *Communication HOLD using IP multimedia core network subsystem – Protocol specification*. +- [ITU-T Q.4003.1 v.1] Recommendation ITU-T Q.4003.1 v.1 (2016), *Communication HOLD using IP multimedia core network subsystem; Conformance Testing – Part 1: Network side and user side; Protocol implementation conformance statement*. +- [ITU-T X.290] Recommendation ITU-T X.290 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – General concepts*. +- [ITU-T X.296] Recommendation ITU-T X.296 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – Implementation conformance statements*. +- [IETF RFC 3264] IETF RFC 3264 (2002), *An Offer/Answer Model with the Session Description Protocol (SDP)*. + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 **abstract test suite (ATS)**: Refer to [ITU-T X.290]. +- 3.1.2 **implementation under test (IUT)**: Refer to [ITU-T X.290]. + +- 3.1.3 **PICS proforma:** Refer to [ITU-T X.290]. +- 3.1.4 **point of control and observation:** Refer to [ITU-T X.290]. +- 3.1.5 **protocol implementation conformance statement (PICS):** Refer to [ITU-T X.290]. +- 3.1.6 **system under test (SUT):** Refer to [ITU-T X.290]. +- 3.1.7 **test purpose (TP):** Refer to [ITU-T X.290]. + +### 3.2 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +For the purposes of this Recommendation, the abbreviations given in [ITU-T Q.3619 v.1] and the following apply: + +| | | +|-----|---------------------------| +| IUT | Implementation Under Test | +| SUT | System Under Test | +| TSS | Test Suite Structure | +| UE | User Equipment | + +# 4 Test Suite Structure (TSS) + +| | | | +|------------|---------------|------------| +| ServedUser | WithUPDATE | CH_U01_xxx | +| | WithoutUPDATE | CH_U02_xxx | + +Figure 1 – Test suite structure + +## 4.1 Configuration + +The scope of this Recommendation is to test the signalling and procedural aspects of the stage 3 requirements as described in [ITU-T Q.3619 v.1]. Stage 3 describes the requirements for several network entities and also the requirements for terminal devices. Therefore several interfaces (reference points) are addressed to satisfy the test of the different entities. + +Therefore to test the appropriate entities the configurations below are applicable. + +### 4.1.2 Testing of the UE + +There are special clauses in the protocol standard describing the procedures that apply at the originating and terminating user equipment (UE). Therefore the test configuration below has been chosen. + +![Diagram showing a Test system connected to a User equipment (Implementation under test) via a Gm interface.](e23c9577e177bf077bac8951a775dd90_img.jpg) + +The diagram illustrates the test configuration for UE functionalities. On the left, a cyan box labeled 'Test system' is connected via a horizontal line to a green box on the right. The horizontal line is labeled 'Gm' and has a small vertical tick mark in the middle. The green box is labeled 'User equipment' at the top and 'Implementation under test' at the bottom. Below the green box, the text 'Q.4003.3v1(16)\_F02' is visible. + +Diagram showing a Test system connected to a User equipment (Implementation under test) via a Gm interface. + +Figure 2 – Applicable configuration to test UE functionalities + +## 5 Test purposes (TP) + +## 5.1 Introduction + +For each test requirement a test purpose (TP) is defined. + +#### 5.1.1 TP naming convention + +Test purposes (TPs) are numbered, starting at 001, within each group. Groups are organized according to the test suite structure (TSS). Additional references are added to identify the actual test suite and whether it applies to the network or the user (see Table 1). + +**Table 1 – TP identifier naming convention scheme** + +| | | | | | | +|-------------------------------------|----------------------------------------------------------------------------------------------------|---|------|---|---------| +| Identifier: __ | | | | | | +| = supplementary service: | e.g. "CH" | | | | | +| = type of IUT: |
UUser
NNetwork
| U | User | N | Network | +| U | User | | | | | +| N | Network | | | | | +| = group | 2 digit field representing group reference according to TSS | | | | | +| = sequential number | (001-999) | | | | | + +#### 5.1.2 Test strategy + +As the base standard [ITU-T Q.3619 v.1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the protocol implementation conformance statements (PICS) in [ITU-T Q.4003.1]. + +## 5.2 User TPs for HOLD + +All PICS items referred to in this clause are as specified in [ITU-T Q.4003.1 v.1] unless indicated otherwise by another numbered reference. + +#### 5.2.1 Served user + +#### 5.2.1.1 Communication Hold with support for UPDATE + +| TSS | TP | HOLD reference | Selection expression | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|--------------------------------------|------------------------------|-----------------------|--|-----------------------|--|--------------------------------------|--|-------------------------------|---|------------------|--|---|-------------------|--|--------------------------------|--| +| ServedUser/WithUPDATE | CH_U01_001 | Clause 4.5.2.1 of [ITU-T Q.3619 v.1] | PICS 5.1/1
AND PICS 5.2/2 | | | | | | | | | | | | | | | | +| Test purpose:
Session hold. UPDATE method is used. Individual media stream is affected. The media stream was previously set to sendrecv.
Ensure that the IUT to hold an individual media stream of the communication session, sends an UPDATE request containing a SDP body with an attribute line indicating 'a= sendonly'. | | | | | | | | | | | | | | | | | | | +| Precondition:
  • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • The media stream was previously set to 'sendrecv'
  • One individual media stream
| | | | | | | | | | | | | | | | | | | +| Comments:
User EquipmentTest Equipment
Establish a confirmed session
User invokes the HOLD service→UPDATE(sendonly)
←200 OK (recvonly)
Apply post test routine
| | | | User Equipment | | Test Equipment | | Establish a confirmed session | | User invokes the HOLD service | → | UPDATE(sendonly) | | ← | 200 OK (recvonly) | | Apply post test routine | | +| User Equipment | | Test Equipment | | | | | | | | | | | | | | | | | +| | Establish a confirmed session | | | | | | | | | | | | | | | | | | +| User invokes the HOLD service | → | UPDATE(sendonly) | | | | | | | | | | | | | | | | | +| | ← | 200 OK (recvonly) | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | + +| TSS | TP | HOLD reference | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|--------------------------------------|-----------------------------|-----------------------|--|-----------------------|--|--------------------------------------|--|---------------|---|------------------|--|---|----------------------------|-------------------|-------|----------------------|--|---|----------------------------|--|---|-----|--|--------------------------------|--| +| ServedUser/WithUPDATE | CH_U01_002 | Clause 4.5.2.1 of [ITU-T Q.3619 v.1] | PICS 5.1/1 AND PICS 5.2/2 | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose:
Session hold. UPDATE method is used. Individual media stream is affected. The media stream was previously set to sendrecv.
Ensure that the IUT responds to the hold request of an individual media stream of the communication session from the remote party, sends a 200 OK INVITE/UPDATE response containing a SDP body with an attribute line indicating 'a=recvonly'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Precondition:
  • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • The media stream was previously set to 'sendrecv'
  • One individual media stream
| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
User Equipment Test Equipment
Establish a confirmed session
CASE A ← UPDATE(sendonly)
→ 200 OK (recvonly)

CASE B
←
INVITE(sendonly)
→ 200 OK (recvonly)
← ACK
Apply post test routine
| | | | User Equipment | | Test Equipment | | Establish a confirmed session | | CASE A | ← | UPDATE(sendonly) | | → | 200 OK ( recvonly ) |
CASE B |
← |
INVITE(sendonly) | | → | 200 OK ( recvonly ) | | ← | ACK | | Apply post test routine | | +| User Equipment | | Test Equipment | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Establish a confirmed session | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE A | ← | UPDATE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | 200 OK ( recvonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CASE B |
← |
INVITE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | 200 OK ( recvonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS | TP | HOLD reference | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|--------------------------------------|-----------------------------|-----------------------|--|-----------------------|--|--------------------------------------|--|---------------|---|------------------|--|---|----------------------------|-------------------|-------|----------------------|--|---|----------------------------|--|---|-----|-----------------------------------|-------|-------------------------------|--|---|-------------------|--|--------------------------------|--| +| ServedUser/WithUPDATE | CH_U01_003 | Clause 4.5.2.1 of [ITU-T Q.3619 v.1] | PICS 5.1/1 AND PICS 5.2/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose:
Session hold. UPDATE method is used. Individual media stream is affected. The media stream was previously set to recvonly.
Ensure that the IUT to hold an individual media stream of the communication session, sends an UPDATE request containing a SDP body with an attribute line indicating 'a=inactive'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Precondition:
  • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • The media stream was previously set to 'recvonly'
  • One individual media stream
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
User Equipment Test Equipment
Establish a confirmed session
CASE A ← UPDATE(sendonly)
→ 200 OK (recvonly)

CASE B
←
INVITE(sendonly)
→ 200 OK (recvonly)
← ACK

User invokes the HOLD service
→
UPDATE(inactive)
← 200 OK (inactive)
Apply post test routine
| | | | User Equipment | | Test Equipment | | Establish a confirmed session | | CASE A | ← | UPDATE(sendonly) | | → | 200 OK ( recvonly ) |
CASE B |
← |
INVITE(sendonly) | | → | 200 OK ( recvonly ) | | ← | ACK |
User invokes the HOLD service |
→ |
UPDATE( inactive ) | | ← | 200 OK (inactive) | | Apply post test routine | | +| User Equipment | | Test Equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Establish a confirmed session | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE A | ← | UPDATE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | 200 OK ( recvonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CASE B |
← |
INVITE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | 200 OK ( recvonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
User invokes the HOLD service |
→ |
UPDATE( inactive ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | 200 OK (inactive) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS | TP | HOLD reference | Selection expression | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------|-----------------------------| +| ServedUser/WithUPDATE | CH_U01_004 | Clause 4.5.2.1 of [ITU-T Q.3619 v.1] | PICS 5.1/1 AND PICS 5.2/2 | +| Test purpose:
Session resume. UPDATE method is used. Individual media stream is affected. The media stream was previously set to sendonly. | | | | +| Ensure that the IUT to resume an individual media stream of the communication session, sends an UPDATE request containing a SDP body with an attribute line indicating 'a=sendrecv' or without attribute line. | | | | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|---------------------------------------------------------------------------| +| Precondition:
  • • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • • The media stream was previously set to 'sendonly'
  • • One individual media stream
| | | +| Comments:
User Equipment | | | +| | Establish a confirmed session | Test Equipment | +| User invokes the HOLD service | →
← | UPDATE( sendonly )
200 OK ( recvonly ) | +| User resumes the session | →
← | UPDATE( sendrecv or absent)
200 OK ( sendrecv or absent) | +| Apply post test routine | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|------------------------------------------------------------------|----------------------------------------------------------------| +| TSS
ServedUser/WithUPDATE | TP
CH_U01_005 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression
PICS 5.1/1
AND PICS 5.2/2 | +| Test purpose:
Session resume. UPDATE method is used. Individual media streams are affected. The media stream was previously set to inactive.
Ensure that the IUT to resume an individual media stream of the communication session, sends an UPDATE request containing a SDP body with an attribute line indicating 'a=recvonly'. | | | | +| Precondition:
  • • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • • The media stream was previously set to 'inactive'
  • • One individual media stream
| | | | +| Comments:
User Equipment | | | | +| | Establish a confirmed session | | Test Equipment | +| CASE A | ←
→ | | UPDATE( sendonly )
200 OK ( recvonly ) | +| CASE B | ←
→
← | | INVITE( sendonly )
200 OK ( recvonly )
ACK | +| User invokes the HOLD service | →
← | | UPDATE( inactive )
200 OK ( inactive ) | +| User resumes the media session | →
← | | UPDATE( recvonly )
200 OK ( sendonly ) | +| Apply post test routine | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------------------------------------------|-------------------------------------------------------------| +| TSS
ServedUser/WithUPDATE | TP
CH_U01_006 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression
PICS 5.1/1
AND PICS 5.2/2 | +| Test purpose:
Session hold. UPDATE method is used. Individual media stream is affected. The media stream was previously set to inactive.
Ensure that the IUT to resume an individual media stream of the communication session, sends an UPDATE request containing a SDP body with an attribute line indicating 'a=sendonly'. | | | | +| Precondition:
  • • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • • The media stream was previously set to 'inactive'
  • • One individual media stream
| | | | + +| | | | +|--------------------------------------|---|----------------------------| +| Comments: | | | +| User Equipment | | Test Equipment | +| Establish a confirmed session | | | +| User invokes the HOLD service | → | UPDATE( sendonly ) | +| | ← | 200 OK ( recvonly ) | +| CASE A | ← | UPDATE( inactive ) | +| | → | 200 OK ( inactive ) | +| CASE B | ← | INVITE( inactive ) | +| | → | 200 OK ( inactive ) | +| | ← | ACK | +| User resumes the media session | → | UPDATE( sendonly ) | +| | ← | 200 OK ( recvonly ) | +| Apply post test routine | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------|------------------------------| +| TSS | TP | HOLD reference | Selection expression | +| ServedUser/WithUPDATE | CH_U01_007 | Clause 4.5.2.1 of [ITU-T Q.3619 v.1] | PICS 5.1/1
AND PICS 5.2/1 | +| Test purpose: | | | | +| Session hold. UPDATE method is used. Individual media stream is affected. The media stream was previously set to sendrecv. | | | | +| Ensure that the IUT to hold an individual media stream of an early dialogue, sends an UPDATE request containing a SDP body with an attribute line indicating 'a= sendonly'. | | | | +| Precondition: | | | | +|
  • An early dialogue was established between the served user and a remote user according to the 'basic Call' procedures
  • The media stream was previously set to 'sendrecv'
  • One individual media stream
| | | | +| Comments: | | | | +| User Equipment | | Test Equipment | | +| Establish an early dialogue | | | | +| User invokes the HOLD service | → | UPDATE( sendonly ) | | +| | ← | 200 OK ( recvonly ) | | +| Apply post test routine | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------|------------------------------| +| TSS | TP | HOLD reference | Selection expression | +| ServedUser/WithUPDATE | CH_U01_008 | Clause 4.5.2.1 of [ITU-T Q.3619 v.1] | PICS 5.1/1
AND PICS 5.2/1 | +| Test purpose: | | | | +| Session hold. UPDATE method is used. Individual media stream is affected. The media stream was previously set to sendrecv. | | | | +| Ensure that the IUT responds to the hold request of an individual media stream from the remote party of an early dialogue, sends a 200 OK UPDATE response containing a SDP body with an attribute line indicating 'a=recvonly'. | | | | +| Precondition: | | | | +|
  • An early dialogue was established between the served user and a remote user according to the 'basic Call' procedures
  • The media stream was previously set to 'sendrecv'
  • One individual media stream
| | | | +| Comments: | | | | +| User Equipment | | Test Equipment | | +| Establish an early dialogue | | | | +| | ← | UPDATE( sendonly ) | | +| | → | 200 OK ( recvonly ) | | +| Apply post test routine | | | | + +| TSS | TP | HOLD reference | Selection expression | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|--------------------------------------|------------------------------|-----------------------|--|-----------------------|--|--------------------------------------|--|-------------------------------|---|------------------|--|---|-------------------|--|--------------------------------|--| +| ServedUser/WithUPDATE | CH_U01_009 | Clause 4.5.2.1 of [ITU-T Q.3619 v.1] | PICS 5.1/1
AND PICS 5.2/2 | | | | | | | | | | | | | | | | +| Test purpose:
Session hold. UPDATE method is used. All media streams are affected. The media streams were previously set to sendrecv.
Ensure that the IUT to hold all media streams of the communication session, sends an UPDATE request containing a SDP body with a session level direction attribute line indicating 'a=sendonly'. | | | | | | | | | | | | | | | | | | | +| Precondition:
  • • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • • All media streams were previously set to 'sendrecv'
  • • Individual media streams
| | | | | | | | | | | | | | | | | | | +| Comments:
User Equipment Test Equipment
Establish a confirmed session
User invokes the HOLD service → UPDATE(sendonly)
← 200 OK (recvonly)
Apply post test routine
| | | | User Equipment | | Test Equipment | | Establish a confirmed session | | User invokes the HOLD service | → | UPDATE(sendonly) | | ← | 200 OK (recvonly) | | Apply post test routine | | +| User Equipment | | Test Equipment | | | | | | | | | | | | | | | | | +| | Establish a confirmed session | | | | | | | | | | | | | | | | | | +| User invokes the HOLD service | → | UPDATE(sendonly) | | | | | | | | | | | | | | | | | +| | ← | 200 OK (recvonly) | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | + +| TSS | TP | HOLD reference | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|--------------------------------------|------------------------------|-----------------------|--|-----------------------|--|--------------------------------------|--|---------------|---|------------------|--|---|-------------------|-------------------|-------|----------------------|--|---|-------------------|--|---|-----|--|--------------------------------|--| +| ServedUser/WithUPDATE | CH_U01_010 | Clause 4.5.2.1 of [ITU-T Q.3619 v.1] | PICS 5.1/1
AND PICS 5.2/2 | | | | | | | | | | | | | | | | | | | | | | | | | +| Test purpose:
Session hold. UPDATE method is used. All media streams are affected. The media streams were previously set to sendrecv.
Ensure that the IUT responds to hold request of all media streams of the communication session from the remote party, sends a 200 OK INVITE/UPDATE response containing aSDP body with an attribute line indicating 'a=recvonly'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Precondition:
  • • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • • The media stream was previously set to 'sendrecv'
  • • One individual media stream
| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
User Equipment Test Equipment
Establish a confirmed session
CASE A ← UPDATE(sendonly)
→ 200 OK (recvonly)

CASE B
←
INVITE(sendonly)
→ 200 OK (recvonly)
← ACK
Apply post test routine
| | | | User Equipment | | Test Equipment | | Establish a confirmed session | | CASE A | ← | UPDATE(sendonly) | | → | 200 OK (recvonly) |
CASE B |
← |
INVITE(sendonly) | | → | 200 OK (recvonly) | | ← | ACK | | Apply post test routine | | +| User Equipment | | Test Equipment | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Establish a confirmed session | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE A | ← | UPDATE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | 200 OK (recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CASE B |
← |
INVITE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | 200 OK (recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS | TP | HOLD reference | Selection expression | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------|------------------------------| +| ServedUser/WithUPDATE | CH_U01_011 | Clause 4.5.2.1 of [ITU-T Q.3619 v.1] | PICS 5.1/1
AND PICS 5.2/2 | +| Test purpose:
Session hold. UPDATE method is used. All media streams are affected. The media streams were previously set to recvonly.
Ensure that the IUT to hold all media streams of the communication session, sends an UPDATE request containing a SDP body with a session level direction attribute line indicating 'a=inactive'. | | | | +| Precondition:
  • • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • • All media streams were previously set to 'recvonly'
  • • Individual media streams
| | | | + +| | | | +|--------------------------------------|---|----------------------------| +| Comments: | | | +| User Equipment | | Test Equipment | +| Establish a confirmed session | | | +| CASE A | ← | UPDATE( sendonly ) | +| | → | 200 OK ( recvonly ) | +| CASE B | ← | INVITE( sendonly ) | +| | → | 200 OK ( recvonly ) | +| | ← | ACK | +| User invokes the HOLD service | → | UPDATE( inactive ) | +| | ← | 200 OK ( inactive ) | +| Apply post test routine | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------|------------------------------| +| TSS | TP | HOLD reference | Selection expression | +| ServedUser/WithUPDATE | CH_U01_012 | Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | PICS 5.1/1
AND PICS 5.2/2 | +| Test purpose:
Session resume. UPDATE method is used. All media streams are affected. The media streams were previously set to sendonly.
Ensure that the IUT to resume all media streams of the communication session, sends an UPDATE request containing a SDP body with a session level direction attribute line indicating 'a=sendrecv' or without attribute line. | | | | +| Precondition:
  • • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • • All media streams were previously set to 'sendonly'
  • • Individual media streams
| | | | +| Comments: | | Test Equipment | | +| User Equipment | | | | +| Establish a confirmed session | | | | +| User invokes the HOLD service | → | UPDATE( sendonly ) | | +| | ← | 200 OK ( recvonly ) | | +| User resumes the session | → | UPDATE( sendrecv or absent) | | +| | ← | 200 OK ( sendrecv or absent) | | +| Apply post test routine | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------|------------------------------| +| TSS | TP | HOLD reference | Selection expression | +| ServedUser/WithUPDATE | CH_U01_013 | Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | PICS 5.1/1
AND PICS 5.2/2 | +| Test purpose:
Session resume. UPDATE method is used. All media streams are affected. The media streams were previously set to inactive.
Ensure that the IUT to resume all media streams of the communication session, sends an UPDATE request containing a SDP body with a session level direction attribute line indicating 'a=recvonly'. | | | | +| Precondition:
  • • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • • All media streams were previously set to 'inactive'
  • • Individual media streams
| | | | + +| | | | +|--------------------------------------|---|----------------------------| +| Comments: | | | +| User Equipment | | Test Equipment | +| Establish a confirmed session | | | +| CASE A | ← | UPDATE( sendonly ) | +| | → | 200 OK ( recvonly ) | +| CASE B | ← | INVITE( sendonly ) | +| | → | 200 OK ( recvonly ) | +| | ← | ACK | +| User invokes the HOLD service | → | UPDATE( inactive ) | +| | ← | 200 OK ( inactive ) | +| User resumes the media session | → | UPDATE( recvonly ) | +| | ← | 200 OK ( sendonly ) | +| Apply post test routine | | | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------|------------------------------| +| TSS | TP | HOLD reference | Selection expression | +| ServedUser/WithUPDATE | CH_U01_014 | Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | PICS 5.1/1
AND PICS 5.2/2 | +| Test purpose: | | | | +| Session hold. UPDATE method is used. All media streams are affected. The media streams were previously set to recvonly. | | | | +| Ensure that the IUT to hold an individual media stream of the communication session, sends an UPDATE request containing a SDP body with an attribute line indicating 'a=inactive'. | | | | +| Precondition: | | | | +|
  • • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • • The media stream was previously set to 'sendonly'
  • • Individual media streams
| | | | +| Comments: | | | | +| User Equipment | | | Test Equipment | +| Establish a confirmed session | | | | +| User invokes the HOLD service | → | UPDATE( sendonly ) | | +| | ← | 200 OK ( recvonly ) | | +| CASE A | ← | UPDATE( inactive ) | | +| | → | 200 OK ( inactive ) | | +| CASE B | ← | INVITE( inactive ) | | +| | → | 200 OK ( inactive ) | | +| | ← | ACK | | +| User resumes the media session | → | UPDATE( sendonly ) | | +| | ← | 200 OK ( recvonly ) | | +| Apply post test routine | | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------|------------------------------| +| TSS | TP | HOLD reference | Selection expression | +| ServedUser/WithUPDATE | CH_U01_015 | Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | PICS 5.1/1
AND PICS 5.2/1 | +| Test purpose: | | | | +| Session hold. UPDATE method is used. All media streams are affected. The media stream was previously set to sendrecv. | | | | +| Ensure that the IUT to hold all media streams of an early dialogue, sends an UPDATE request containing a SDP body with an attribute line indicating 'a= sendonly'. | | | | +| Precondition: | | | | +|
  • • An early dialogue was established between the served user and a remote user according to the 'basic Call' procedures
  • • The media stream was previously set to 'sendrecv'
  • • Individual media streams
| | | | + +| | | | +|------------------------------------|---|-----------------------| +| Comments: | | | +| User Equipment | | Test Equipment | +| Establish an early dialogue | | | +| User invokes the HOLD service | → | UPDATE(sendonly) | +| | ← | 200 OK (recvonly) | +| Apply post test routine | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------|------------------------------| +| TSS | TP | HOLD reference | Selection expression | +| ServedUser/WithUPDATE | CH_U01_016 | Clause 4.5.2.1 of [ITU-T Q.3619 v.1] | PICS 5.1/1
AND PICS 5.2/1 | +| Test purpose: | | | | +| Session hold. UPDATE method is used. All media streams are affected. The media streams were previously set to sendrecv. | | | | +| Ensure that the IUT responds to the hold request of all individual media streams from the remote party of an early dialogue, sends a 200 OK UPDATE response containing aSDP body with an attribute line indicating 'a=recvonly'. | | | | +| Precondition: | | | | +|
  • • An early dialogue was established between the served user and a remote user according to the 'basic Call' procedures
  • • The media stream was previously set to 'sendrecv'
  • • Individual media streams
| | | | +| Comments: | | | | +| User Equipment | | | Test Equipment | +| Establish an early dialogue | | | | +| | ← | | UPDATE(sendonly) | +| | → | | 200 OK (recvonly) | +| Apply post test routine | | | | + +#### 5.2.1.2 Communication Hold without support for UPDATE + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------|----------------------------------| +| TSS | TP | HOLD reference | Selection expression | +| ServedUser/WithoutUPDATE | CH_U02_001 | Clause 4.5.2.1 of [ITU-T Q.3619 v.1] | PICS 5.1/1
AND NOT PICS 5.2/2 | +| Test purpose: | | | | +| Session hold. UPDATE method is not used. Individual media stream is affected. The media stream was previously set to sendrecv. | | | | +| Ensure that the IUT to hold an individual media stream of the communication session, sends a ReINVITE request containing aSDP body with an attribute line indicating 'a=sendonly'. | | | | +| Precondition: | | | | +|
  • • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • • The media stream was previously set to 'sendrecv'
  • • Individual media streams
| | | | +| Comments: | | | | +| User Equipment | | | Test Equipment | +| Establish a confirmed session | | | | +| User invokes the HOLD service | → | | ReINVITE(sendonly) | +| | ← | | 200 OK (recvonly) | +| | → | | ACK | +| Apply post test routine | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------|----------------------------------| +| TSS | TP | HOLD reference | Selection expression | +| ServedUser/WithUPDATE | CH_U02_002 | Clause 4.5.2.1 of [ITU-T Q.3619 v.1] | PICS 5.1/1
AND NOT PICS 5.2/2 | +| Test purpose: | | | | +| Session hold. UPDATE method is not used. Individual media stream is affected. The media stream was previously set to sendrecv. | | | | +| Ensure that the IUT responds to the hold request of an individual media stream of the communication session from the remote party, sends a 200 OK INVITE/UPDATE response containing a SDP body with an attribute line indicating 'a=recvonly'. | | | | + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|-------------------------------------------------------| +| Precondition:
  • • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • • The media stream was previously set to 'sendrecv'
  • • Individual media streams
| | | +| Comments:
User Equipment Test Equipment | | | +| | Establish a confirmed session | | +| CASE A | ←
→ | UPDATE(sendonly)
200 OK ( recvonly ) | +| CASE B | ←
→
← | INVITE(sendonly)
200 OK ( recvonly )
ACK | +| Apply post test routine | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|------------------------------------------------------------------|-----------------------------------------------------------------| +| TSS
ServedUser/WithoutUPDATE | TP
CH_U02_003 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression
PICS 5.1/1
AND NOT PICS 5.2/2 | +| Test purpose:
Session hold. UPDATE method is not used. Individual media streams are affected. The media stream was previously set to recvonly.
Ensure that the IUT to hold an individual media streams of the communication session, sends a ReINVITE request containing a SDP body with an attribute line indicating 'a=inactive'. | | | | +| Precondition:
  • • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • • The media stream was previously set to 'recvonly'
  • • Individual media stream
| | | | +| Comments:
User Equipment Test Equipment | | | | +| | Establish a confirmed session | | | +| CASE A | ←
→ | | UPDATE(sendonly)
200 OK ( recvonly ) | +| CASE B | ←
→
← | | INVITE(sendonly)
200 OK ( recvonly )
ACK | +| User invokes the HOLD service | →
←
→ | | ReINVITE( inactive )
200 OK (inactive)
ACK | +| Apply post test routine | | | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------------------------------------------|-----------------------------------------------------------------| +| TSS
ServedUser/WithoutUPDATE | TP
CH_U02_004 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression
PICS 5.1/1
AND NOT PICS 5.2/2 | +| Test purpose:
Session resume. UPDATE method is not used. Individual media stream is affected. The media stream was previously set to sendonly.
Ensure that the IUT to resume an individual media stream of the communication session, sends a ReINVITE request containing a SDP body with an attribute line indicating 'a=sendrecv' or without attribute line. | | | | +| Precondition:
  • • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • • The media stream was previously set to 'sendonly'
  • • Individual media stream
| | | | + +| Comments: | | | +|--------------------------------------|---|--------------------------------------| +| User Equipment | | Test Equipment | +| Establish a confirmed session | | | +| User invokes the HOLD service | → | ReINVITE( sendonly ) | +| | ← | 200 OK ( recvonly ) | +| | → | ACK | +| User resumes the session | → | ReINVITE( sendrecv or absent) | +| | ← | 200 OK ( sendrecv or absent) | +| | → | ACK | +| Apply post test routine | | | + +| TSS | TP | HOLD reference | Selection expression | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------|----------------------------------| +| ServedUser/WithoutUPDATE | CH_U02_005 | Clause 4.5.2.1 of [ITU-T Q.3619 v.1] | PICS 5.1/1
AND NOT PICS 5.2/2 | +| Test purpose:
Session resume. UPDATE method is not used. Individual media stream is affected. The media stream was previously set to inactive. | | | | +| Ensure that the IUT to resume an individual media stream of the communication session, sends a ReINVITE request containing a SDP body with an attribute line indicating 'a=recvonly'. | | | | +| Precondition: | | | | +|
  • • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • • The media stream was previously set to 'inactive'
  • • Individual media streams
| | | | +| Comments: | | | | +| User Equipment | | | Test Equipment | +| Establish a confirmed session | | | | +| CASE A | ← | UPDATE( sendonly ) | | +| | → | 200 OK ( recvonly ) | | +| CASE B | ← | INVITE( sendonly ) | | +| | → | 200 OK ( recvonly ) | | +| | ← | ACK | | +| User invokes the HOLD service | → | ReINVITE( inactive ) | | +| | ← | 200 OK ( inactive ) | | +| | → | ACK | | +| User resumes the media session | → | ReINVITE( recvonly ) | | +| | ← | 200 OK ( sendonly ) | | +| | → | ACK | | +| Apply post test routine | | | | + +| TSS | TP | HOLD reference | Selection expression | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------|----------------------------------| +| ServedUser/WithUPDATE | CH_U02_006 | Clause 4.5.2.1 of [ITU-T Q.3619 v.1] | PICS 5.1/1
AND NOT PICS 5.2/2 | +| Test purpose:
Session hold. UPDATE method is not used. Individual media stream is affected. The media stream was previously set to inactive. | | | | +| Ensure that the IUT to resume an individual media stream of the communication session, sends a ReINVITE request containing a SDP body with an attribute line indicating 'a=sendonly'. | | | | +| Precondition: | | | | +|
  • • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • • The media stream was previously set to 'inactive'
  • • One individual media stream
| | | | + +| | | | +|--------------------------------------|-------|---------------------------------| +| Comments: | | | +| User Equipment | | Test Equipment | +| Establish a confirmed session | | | +| User invokes the HOLD service | → | ReINVITE( sendonly ) | +| | ← | 200 OK (recvonly) | +| | → | ACK | +|
CASE A |
← |
UPDATE( inactive ) | +| | → | 200 OK (inactive) | +|
CASE B |
← |
INVITE( inactive ) | +| | → | 200 OK (inactive) | +| | ← | ACK | +|
User resumes the media session |
→ |
ReINVITE( sendonly ) | +| | ← | 200 OK (recvonly) | +| | → | ACK | +| Apply post test routine | | | + +| | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------------------------------------------|-----------------------------------------------------------------------------------|------------------|--|--|-----------------------|--|-----------------------|------------------------------------|--|--|-------------------------------|---|---------------------------|--|---|-------------------|--------------------------------|--|--| +| TSS
ServedUser/WithUPDATE | TP
CH_U02_007 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression
PICS 5.1/1
AND PICS 5.2/1
AND NOT PICS 5.2/2 | | | | | | | | | | | | | | | | | | | +| Test purpose:
Session hold. UPDATE method is not used. Individual media stream is affected. The media stream was previously set to sendrecv.
Ensure that the IUT to hold an individual media stream of an early dialogue, sends an UPDATE request containing a SDP body with an attribute line indicating 'a= sendonly'. | | | | | | | | | | | | | | | | | | | | | | +| Precondition:
  • An early dialogue was established between the served user and a remote user according to the 'basic Call' procedures
  • The media stream was previously set to 'sendrecv'
  • One individual media stream
| | | | | | | | | | | | | | | | | | | | | | +|
Comments:
User Equipment Test Equipment
Establish an early dialogue
User invokes the HOLD service → UPDATE(sendonly)
← 200 OK (recvonly)
Apply post test routine
| | | | Comments: | | | User Equipment | | Test Equipment | Establish an early dialogue | | | User invokes the HOLD service | → | UPDATE( sendonly ) | | ← | 200 OK (recvonly) | Apply post test routine | | | +| Comments: | | | | | | | | | | | | | | | | | | | | | | +| User Equipment | | Test Equipment | | | | | | | | | | | | | | | | | | | | +| Establish an early dialogue | | | | | | | | | | | | | | | | | | | | | | +| User invokes the HOLD service | → | UPDATE( sendonly ) | | | | | | | | | | | | | | | | | | | | +| | ← | 200 OK (recvonly) | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------------------------------------------|-----------------------------------------------------------------------------------|------------------|--|--|-----------------------|--|-----------------------|------------------------------------|--|--|--|---|---------------------------|--|---|----------------------------|--------------------------------|--|--| +| TSS
ServedUser/WithUPDATE | TP
CH_U02_008 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression
PICS 5.1/1
AND PICS 5.2/1
AND NOT PICS 5.2/2 | | | | | | | | | | | | | | | | | | | +| Test purpose:
Session hold. UPDATE method is not used. Individual media stream is affected. The media stream was previously set to sendrecv.
Ensure that the IUT responds to the hold request of an individual media stream from the remote party of an early dialogue, sends a 200 OK UPDATE response containing a SDP body with an attribute line indicating 'a=recvonly'. | | | | | | | | | | | | | | | | | | | | | | +| Precondition:
  • An early dialogue was established between the served user and a remote user according to the 'basic Call' procedures
  • The media stream was previously set to 'sendrecv'
  • One individual media stream
| | | | | | | | | | | | | | | | | | | | | | +|
Comments:
User Equipment Test Equipment
Establish an early dialogue
← UPDATE(sendonly)
→ 200 OK (recvonly)
Apply post test routine
| | | | Comments: | | | User Equipment | | Test Equipment | Establish an early dialogue | | | | ← | UPDATE( sendonly ) | | → | 200 OK ( recvonly ) | Apply post test routine | | | +| Comments: | | | | | | | | | | | | | | | | | | | | | | +| User Equipment | | Test Equipment | | | | | | | | | | | | | | | | | | | | +| Establish an early dialogue | | | | | | | | | | | | | | | | | | | | | | +| | ← | UPDATE( sendonly ) | | | | | | | | | | | | | | | | | | | | +| | → | 200 OK ( recvonly ) | | | | | | | | | | | | | | | | | | | | +| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | + +| TSS
ServedUser/WithoutUPDATE | TP
CH_U02_009 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression
PICS 5.1/1
AND NOT PICS 5.2/2 | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|------------------------------------------------------------------|-----------------------------------------------------------------|-----------------------|--|-----------------------|--|--------------------------------------|--|-------------------------------|---|-----------------------------|--|---|----------------------------|--|---|-----|--|--------------------------------|--| +| Test purpose:
Session hold. UPDATE method is not used. All media streams are affected. The media streams were previously set to sendrecv.
Ensure that the IUT to hold all media streams of the communication session, sends a ReINVITE request containing a SDP body with a session level direction attribute line indicating 'a=sendonly'. | | | | | | | | | | | | | | | | | | | | | | +| Precondition:
  • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • All media streams were previously set to 'sendrecv'
  • Individual media streams
| | | | | | | | | | | | | | | | | | | | | | +| Comments:
User Equipment Test Equipment
Establish a confirmed session
User invokes the HOLD service → ReINVITE(sendonly)
← 200 OK (recvonly)
→ ACK
Apply post test routine
| | | | User Equipment | | Test Equipment | | Establish a confirmed session | | User invokes the HOLD service | → | ReINVITE( sendonly ) | | ← | 200 OK ( recvonly ) | | → | ACK | | Apply post test routine | | +| User Equipment | | Test Equipment | | | | | | | | | | | | | | | | | | | | +| | Establish a confirmed session | | | | | | | | | | | | | | | | | | | | | +| User invokes the HOLD service | → | ReINVITE( sendonly ) | | | | | | | | | | | | | | | | | | | | +| | ← | 200 OK ( recvonly ) | | | | | | | | | | | | | | | | | | | | +| | → | ACK | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | + +| TSS
ServedUser/WithUPDATE | TP
CH_U02_010 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression
PICS 5.1/1
AND NOT PICS 5.2/2 | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|------------------------------------------------------------------|-----------------------------------------------------------------|-----------------------|--|-----------------------|--|--------------------------------------|--|---------------|---|---------------------------|--|---|----------------------------|-------------------|-------|-------------------------------|--|---|----------------------------|--|---|-----|--|--------------------------------|--| +| Test purpose:
Session hold. UPDATE method is not used. All media streams are affected. The media streams were previously set to sendrecv.
Ensure that the IUT responds to hold request of all media streams of the communication session from the remote party, sends a 200 OK INVITE/UPDATE response containing aSDP body with an attribute line indicating 'a=recvonly'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Precondition:
  • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • The media stream was previously set to 'sendrecv'
  • One individual media stream
| | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Comments:
User Equipment Test Equipment
Establish a confirmed session
CASE A ← UPDATE(sendonly)
→ 200 OK (recvonly)

CASE B
←
INVITE(sendonly)
→ 200 OK (recvonly)
← ACK
Apply post test routine
| | | | User Equipment | | Test Equipment | | Establish a confirmed session | | CASE A | ← | UPDATE( sendonly ) | | → | 200 OK ( recvonly ) |
CASE B |
← |
INVITE( sendonly ) | | → | 200 OK ( recvonly ) | | ← | ACK | | Apply post test routine | | +| User Equipment | | Test Equipment | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Establish a confirmed session | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CASE A | ← | UPDATE( sendonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | 200 OK ( recvonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | +|
CASE B |
← |
INVITE( sendonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | +| | → | 200 OK ( recvonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | +| | ← | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| TSS
ServedUser/WithoutUPDATE | TP
CH_U02_011 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression
PICS 5.1/1
AND NOT PICS 5.2/2 | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------------------------------------------|-----------------------------------------------------------------| +| Test purpose:
Session hold. UPDATE method is not used. All media streams are affected. The media streams were previously set to recvonly.
Ensure that the IUT to hold all media streams of the communication session, sends a ReINVITE request containing a SDP body with a session level direction attribute line indicating 'a=inactive'. | | | | +| Precondition:
  • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • All media streams were previously set to 'recvonly'
  • Individual media streams
| | | | + +| | | | +|--------------------------------------|---|-----------------------| +| Comments: | | | +| User Equipment | | Test Equipment | +| Establish a confirmed session | | | +| CASE A | ← | UPDATE(sendonly) | +| | → | 200 OK (recvonly) | +| CASE B | ← | INVITE(sendonly) | +| | → | 200 OK (recvonly) | +| | ← | ACK | +| User invokes the HOLD service | → | ReINVITE(inactive) | +| | ← | 200 OK (inactive) | +| | → | ACK | +| Apply post test routine | | | + +| | | | | +|--------------------------|------------|--------------------------------------|----------------------------------| +| TSS | TP | HOLD reference | Selection expression | +| ServedUser/WithoutUPDATE | CH_U02_012 | Clause 4.5.2.1 of [ITU-T Q.3619 v.1] | PICS 5.1/1
AND NOT PICS 5.2/2 | + +**Test purpose:** +*Session resume. UPDATE method is not used. All media streams are affected. The media stream was previously set to sendonly.* + +Ensure that the IUT to resume all media streams of the communication session, sends a ReINVITE request containing a SDP body with a session level direction attribute line indicating 'a=sendrecv' or without attribute line. + +##### **Precondition:** + +- A session was established between the served user and a remote user according to the 'basic Call' procedures +- All media streams were previously set to 'sendonly' +- Individual media streams + +| | | | +|--------------------------------------|---|------------------------------| +| Comments: | | | +| User Equipment | | Test Equipment | +| Establish a confirmed session | | | +| User invokes the HOLD service | → | ReINVITE(sendonly) | +| | ← | 200 OK (recvonly) | +| | → | ACK | +| User resumes the session | → | ReINVITE(sendrecv or absent) | +| | ← | 200 OK (sendrecv or absent) | +| | → | ACK | +| Apply post test routine | | | + +| | | | | +|--------------------------|------------|--------------------------------------|----------------------------------| +| TSS | TP | HOLD reference | Selection expression | +| ServedUser/WithoutUPDATE | CH_U02_013 | Clause 4.5.2.1 of [ITU-T Q.3619 v.1] | PICS 5.1/1
AND NOT PICS 5.2/2 | + +**Test purpose:** +*Session resume. UPDATE method is not used. All media streams are affected. The media streams were previously set to inactive.* + +Ensure that the IUT to resume all media streams of the communication session, sends a ReINVITE request containing a SDP body with a session level direction attribute line indicating 'a=recvonly'. + +##### **Precondition:** + +- A session was established between the served user and a remote user according to the 'basic Call' procedures +- All media streams were previously set to 'inactive' +- Individual media streams + +| | | | +|--------------------------------------|---|-----------------------------| +| Comments: | | | +| User Equipment | | Test Equipment | +| Establish a confirmed session | | | +| CASE A | ← | UPDATE( sendonly ) | +| | → | 200 OK ( recvonly ) | +| CASE B | ← | INVITE( sendonly ) | +| | → | 200 OK ( recvonly ) | +| | ← | ACK | +| User invokes the HOLD service | → | ReINVITE( inactive ) | +| | ← | 200 OK ( inactive ) | +| | → | ACK | +| User resumes the media session | → | ReINVITE( recvonly ) | +| | ← | 200 OK ( sendonly ) | +| | → | ACK | +| Apply post test routine | | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------|----------------------------------| +| TSS | TP | HOLD reference | Selection expression | +| ServedUser/WithUPDATE | CH_U02_014 | Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | PICS 5.1/1
AND NOT PICS 5.2/2 | +| Test purpose:
Session hold. UPDATE method is not used. All media streams are affected. The media streams were previously set to recvonly.
Ensure that the IUT to hold an individual media stream of the communication session, sends a ReINVITE request containing a SDP body with an attribute line indicating 'a=inactive'. | | | | +| Precondition:
  • A session was established between the served user and a remote user according to the 'basic Call' procedures
  • The media stream was previously set to 'sendonly'
  • Individual media streams
| | | | +| Comments: | | | | +| User Equipment | | | Test Equipment | +| Establish a confirmed session | | | | +| User invokes the HOLD service | → | | ReINVITE( sendonly ) | +| | ← | | 200 OK ( recvonly ) | +| | → | | ACK | +| CASE A | ← | | UPDATE( inactive ) | +| | → | | 200 OK ( inactive ) | +| CASE B | ← | | INVITE( inactive ) | +| | → | | 200 OK ( inactive ) | +| | ← | | ACK | +| User resumes the media session | → | | ReINVITE( sendonly ) | +| | ← | | 200 OK ( recvonly ) | +| | → | | ACK | +| Apply post test routine | | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------|----------------------------------------------------| +| TSS | TP | HOLD reference | Selection expression | +| ServedUser/WithUPDATE | CH_U02_015 | Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | PICS 5.1/1
AND PICS 5.2/1
AND NOT PICS 5.2/2 | +| Test purpose:
Session hold. UPDATE method is used. All media streams are affected. The media stream was previously set to sendrecv.
Ensure that the IUT to hold all media streams of an early dialogue, sends an UPDATE request containing a SDP body with an attribute line indicating 'a= sendonly'. | | | | +| Precondition:
  • An early dialogue was established between the served user and a remote user according to the 'basic Call' procedures
  • The media stream was previously set to 'sendrecv'
  • Individual media streams
| | | | + +| | | | +|------------------------------------|---|-----------------------| +| Comments: | | | +| User Equipment | | Test Equipment | +| Establish an early dialogue | | | +| User invokes the HOLD service | → | UPDATE(sendonly) | +| | ← | 200 OK (recvonly) | +| Apply post test routine | | | + +| | | | | +|-----------------------|------------|-----------------------------------------|----------------------------------------------------| +| TSS | TP | HOLD reference | Selection expression | +| ServedUser/WithUPDATE | CH_U02_016 | Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | PICS 5.1/1
AND PICS 5.2/1
AND NOT PICS 5.2/2 | + +**Test purpose:** +*Session hold. UPDATE method is used. All media streams are affected. The media streams were previously set to sendrecv.* + +Ensure that the IUT responds to the hold request of all individual media streams from the remote party of an early dialogue, sends a 200 OK UPDATE response containing a SDP body with an attribute line indicating 'a=recvonly'. + +**Precondition:** + +- An early dialogue was established between the served user and a remote user according to the 'basic Call' procedures +- The media stream was previously set to 'sendrecv' +- Individual media streams + +| | | | +|------------------------------------|---|-----------------------| +| Comments: | | | +| User Equipment | | Test Equipment | +| Establish an early dialogue | | | +| | ← | UPDATE(sendonly) | +| | → | 200 OK (recvonly) | +| Apply post test routine | | | + + + + + +## 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 | 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 | 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, 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/Q/T-REC-Q.4006.1-201602-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4006.1-201602-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..fb76f59d5ba79752d211bb1ab2a6d5bc12ad79fe --- /dev/null +++ b/marked/Q/T-REC-Q.4006.1-201602-I_PDF-E/raw.md @@ -0,0 +1,418 @@ + + +# **ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +# **Q.4006.1** + +(02/2016) + +SERIES Q: SWITCHING AND SIGNALLING + +Testing specifications – Testing specifications for SIP-IMS + +--- + +**Communication waiting service using IP +multimedia core network subsystem; +Conformance testing – Part 1: Network side; +and user side; Protocol implementation +conformance statement** + +Recommendation ITU-T Q.4006.1 + +# ITU-T Q-SERIES RECOMMENDATIONS + +## **SWITCHING AND SIGNALLING** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3899 | +| TESTING SPECIFICATIONS | Q.3900–Q.4099 | +| Testing specifications for next generation networks | Q.3900–Q.3999 | +| Testing specifications for SIP-IMS | Q.4000–Q.4039 | +| Testing specifications for Cloud computing | Q.4040–Q.4059 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Recommendation ITU-T Q.4006.1** + +# Communication waiting service using IP multimedia core network subsystem; Conformance testing – Part 1: Network side and user side; Protocol implementation conformance statement + +## **Summary** + +Recommendation ITU-T Q.4006.1 v.1 (2016) is part 1 of the testing specifications for communication waiting service (CW) implemented on IP multimedia subsystem (IMS) basis on the user side and network side. The Recommendation specifies the protocol implementation conformance statement (PICS) which can be used for testing against Recommendation ITU-T Q.3622 v.1, Communication waiting using IP multimedia core network subsystem – Protocol specification. + +The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.4006.1 and that it relates to Release 10 of the relevant 3GPP/ETSI standard. + +## **History** + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|--------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.4006.1 v.1 | 2016-02-13 | 11 | 11.1002/1000/12741 | + +## **Keywords** + +Communication waiting, CW, IP multimedia subsystem, IMS, network side, protocol implementation conformance statement, PICS, session description protocol, SDP, session initiation protocol, SIP, testing, user side. + +--- + +\* 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 2016 + +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 | +| 4 Abbreviations and acronyms ..... | 1 | +| 5 Conformance to this PICS proforma specification..... | 2 | +| 5.1 Guidance for completing the PICS proforma..... | 2 | +| 5.2 Identification of the implementation ..... | 3 | +| 5.3 Identification of the ITU-T Q.3622 v.1 ..... | 5 | +| 5.4 Global statement of conformance..... | 5 | +| 5.5 Roles ..... | 6 | +| 5.6 User role ..... | 6 | +| 5.7 Network role ..... | 6 | + + + +## **Recommendation ITU-T Q.4006.1** + +## Communication waiting service using IP multimedia core network subsystem; Conformance testing – Part 1: Network side and user side; Protocol implementation conformance statement + +# **1 Scope** + +The present Recommendation provides the protocol implementation conformance statement (PICS) of the communication waiting (CW) service, based on stage three of the IMS simulation services specified in the protocol specification as specified in [ITU-T Q.3622 v.1] "Communication waiting using IP multimedia core network subsystem – Protocol specification". + +# **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 Q.3622 v.1] Recommendation ITU-T Q.3622 v.1 (2016), *Communication waiting using IP multimedia core network subsystem – Protocol specification*. +- [ITU-T X.290] Recommendation ITU-T X.290 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – General concepts*. +- [ITU-T X.296] Recommendation ITU-T X.296 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – Implementation conformance statements*. + +# **3 Definitions** + +For the purposes of this Recommendation, the terms and definitions given in [ITU-X.290] and [ITU-T X.296] apply: + +**3.1 implementation conformance statement (ICS):** A statement made by the supplier of an implementation or system claimed to conform to a given specification, stating which capabilities have been implemented. The ICS can take several forms: protocol ICS, profile ICS, profile specific ICS, information object ICS, etc. + +**3.2 ICS proforma:** A document, in the form of a questionnaire which, when completed for an implementation or system, becomes an ICS. + +**3.3 protocol ICS (PICS):** An ICS for an implementation or system claimed to conform to a given protocol specification. + +NOTE – This may contain additional information. + +## **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +CW Call Waiting + +| | | +|------|-----------------------------------------------| +| ICS | Implementation Conformance Statement | +| IP | Internet Protocol | +| IUT | Implementation Under Test | +| IMS | IP Multimedia Subsystem | +| PICS | Protocol Implementation Conformance Statement | +| SDP | Session Description Protocol | +| SIP | Session Initiation Protocol | +| SUT | Session Initiation Protocol | + +## 5 Conformance to this PICS proforma specification + +If it claims to conform to the present Recommendation, the actual protocol implementation conformance statement (PICS) proforma to be filled in by a supplier shall be technically equivalent to the text of the PICS proforma given in this clause, and shall preserve the numbering/naming and ordering of the proforma items. + +A PICS which conforms to the present Recommendation shall be a conforming PICS proforma completed in accordance with the guidance for completion given in clause 5.1. + +## 5.1 Guidance for completing the PICS proforma + +### 5.1.1 Purposes and structure + +The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in [ITU-T Q.3622 v.1] may provide information about the implementation in a standardized manner. + +The PICS proforma is subdivided into clauses for the following categories of information: + +- guidance for completing the PICS proforma; +- identification of the implementation; +- identification of the ; +- global statement of conformance; +- *roles*; +- *user role*; + - major capabilities; +- network role; + - major capabilities; +- Timers. + +### 5.1.2 Abbreviations and conventions + +The PICS proforma contained in this clause is comprised of information in tabular form in accordance with the guidelines presented in [ITU-T X.296]. + +#### **Item column** + +The item column contains a number which identifies the item in the table. + +#### **Item description column** + +The item description column describes in free text for each respective item (e.g., parameters, timers, etc.). It implicitly means "is supported by the implementation?". + +#### **Status column** + +The following notations, defined in [ITU-T X.296], are used for the status column: + +- m mandatory – the capability is required to be supported. +- o optional – the capability may be supported or not. +- n/a not applicable – in the given context, it is impossible to use the capability. + +##### **Reference column** + +The reference column makes reference to [ITU-T Q.3622 v.1], except where explicitly stated otherwise. + +##### **Support column** + +The support column shall be filled in by the supplier of the implementation. The following common notations, defined in [ITU-T X.296], are used for the support column: + +- Y or y supported by the implementation. +- N or n not supported by the implementation. +- N/A, n/a or – no answer required (allowed only if the status is n/a, directly or after evaluation of a conditional status). + +##### **Prerequisite line** + +A prerequisite line takes the form: Prerequisite: . + +A prerequisite line after a clause or table title indicates that the whole clause or the whole table is not required to be completed if the predicate is FALSE. + +### **5.1.3 Instructions for completing the PICS proforma** + +The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. In particular, an explicit answer shall be entered, in each of the support column boxes provided, using the notation described in clause 5.1.2. + +However, the tables containing in "user role" clause shall only be completed for user implementations, and the tables containing in "network role" clause shall only be completed for network implementations. + +If necessary, the supplier may provide additional comments in the space at the bottom of the tables or separately. + +More detailed instructions are given at the beginning of the different clauses of the PICS proforma. + +## **5.2 Identification of the implementation** + +Identification of the implementation under test (IUT) and the system in which it resides (the system under test (SUT)) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. + +The product supplier information and client information should both be filled in if they are different. + +A person who can answer queries regarding information supplied in the ICS should be named as the contact person. + +#### **5.2.1 Date of the statement** + +### **5.2.2 Implementation Under Test (IUT) identification** + +IUT name: + +IUT version: + +### **5.2.3 System Under Test (SUT) identification** + +SUT name: + +Hardware configuration: + +Operating system: + +#### **5.2.4 Product supplier** + +Name: + +Address: + +Telephone number: + +Facsimile number: + +E-mail address: + +Additional information: + +### **5.2.5 Client (if different from product supplier)** + +Name: + +Address: + +Telephone number: + +Facsimile number: + +E-mail address: + +Additional information: + +### **5.2.6 PICS contact person** + +(A person to contact if there are any queries concerning the content of the ICS) + +Name: + +Telephone number: + +Facsimile number: + +E-mail address: + +Additional information: + +## **5.3 Identification of the ITU-T Q.3622 v.1** + +This PICS proforma applies to [ITU-T Q.3622 v.1], "Communication waiting using IP multimedia core network subsystem – Protocol specification". + +## **5.4 Global statement of conformance** + +Are all mandatory capabilities implemented? (Yes/No) + +NOTE – Answering "No" to this question indicates non-conformance to the specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conforming, on pages attached to the PICS proforma. + +## 5.5 Roles + +**Table 5-1 – Roles** + +| Item | Item description | Reference | Status | Support | +|------|------------------|----------------------------------------------|--------|---------| +| 1 | User | Clauses 4.5.5, 4.5.5.3 of [ITU-T Q.3622 v.1] | o.1 | | +| 2 | Network | Clause 4.5.5.2 of [ITU-T Q.3622 v.1] | o.1 | | + +o.1: It is mandatory to support exactly one of these items. + +Comments: + +## 5.6 User role + +This clause contains the PICS proforma tables related to the user role. They need to be completed only for user implementations: + +Prerequisite: 5.0/1 -- user role + +### 5.6.1 Major capabilities + +**Table 5-2 – User related requirements and options** + +| Item | Item description | Reference | Status | Support | +|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|--------|---------| +| 1 | Does the user equipment of the user B indicate to the user that the outgoing communication is being treated as a waiting communication? | Clause 4.5.5.3.2 of [ITU-T Q.3622 v.1] | o | | +| 2 | Does the user equipment of the user C indicate to the user that the outgoing communication is being treated as a waiting communication? | Clause 4.5.5.3.4 of [ITU-T Q.3622 v.1] | o | | +| 3 | Is the user equipment of the user B able to send a communication waiting indication in a 180 Ringing and send the Alert-Info header with the value ? | Clause 4.5.5.3.2 of [ITU-T Q.3622 v.1] | o | | +| 4 | Does the user equipment of the user B accept and understand the XML CW MIME attachment and notify the user? | Clause 4.5.5.3.2 of [ITU-T Q.3622 v.1] | o | | +| 5 | Does the user equipment of the user B starts timer T UE-CW ? | Clause 4.5.5.3.2 of [ITU-T Q.3622 v.1] | o | | +| 6 | Does the user equipment of the user B use the value of the Expires header received in the INVITE request? | Clause 4.5.5.3.2 of [ITU-T Q.3622 v.1] | o | | + +Comments: + +## 5.7 Network role + +This clause contains the PICS proforma tables related to the network role. They need to be completed only for network implementations: + +Prerequisite: 5.0/2 -- network role + +### 5.7.1 Major capabilities + +**Table 5-3 – Network related requirements and options** + +| Item | Item description | Reference | Status | Support | +|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|--------|---------| +| 1 | Is the CW condition determined by the AS based on the receipt of a 180 (Ringing) response with an Alert-Info header field set to "urn:alert:service:call-waiting"? | Clause 4.5.5.2 of [ITU-T Q.3622 v.1] | o | | +| 2 | Is the CW condition determined by the AS based on validation of the "approaching NDUB" condition? | Clause 4.5.5.2 of [ITU-T Q.3622 v.1] | o | | +| 3 | Does the AS initiate the procedures for the provision of an announcement to the calling? | Clause 4.5.5.2 of [ITU-T Q.3622 v.1] | o | | +| 4 | Does the Application Server start the timer $T_{AS-CW}$ timer? | Clause 4.5.5.2 of [ITU-T Q.3622 v.1] | o | | +| 5 | Does the Application Server Supports the Call diversion service? | Clause 4.6.8 of [ITU-T Q.3622 v.1] | o | | +| 6 | Does the Application Server Supports the Service configuration via Ut interface? | Clause 4.8 of [ITU-T Q.3622 v.1] | o | | +| 7 | Does the Network include an Expires header set to the value of $T_{AS-CW}$ timer in the INVITE sent to user B | Clause 4.5.5.2 of [ITU-T Q.3622 v.1] | o | | + +Comments: + +### 5.7.2 Timers + +**Table 5-4 – Timer** + +| Item | Item description | Reference | Status | Support | Values | | +|------|-------------------|----------------------------------------|--------|---------|-------------------------|-----------------| +| | | | | | Allowed | Supported [sec] | +| 1 | Timer $T_{AS-CW}$ | Clause 4.7 of [ITU-T Q.3622 v.1] | o | | Service provider option | | +| 2 | Timer $T_{UE-CW}$ | Clause 4.5.5.3.2 of [ITU-T Q.3622 v.1] | o | | manufacturer option | | + +Comments: + + + + + +## **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 | 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 | Terminals and subjective and objective assessment methods | | +| Series Q Switching and signalling | 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, 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/Q/T-REC-Q.4102-202202-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4102-202202-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b0304c96038fefbe9d7d7a5b95acf468f740aec2 --- /dev/null +++ b/marked/Q/T-REC-Q.4102-202202-I_PDF-E/raw.md @@ -0,0 +1,1125 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.4102** + +(02/2022) + +SERIES Q: SWITCHING AND SIGNALLING, AND +ASSOCIATED MEASUREMENTS AND TESTS + +Protocols and signalling for peer-to-peer communications + +# --- **Hybrid peer-to-peer communications: Peer protocol** + +Recommendation ITU-T Q.4102 + +ITU-T + +![ITU logo](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 white grid pattern, overlaid by a stylized 'ITU' text in blue. + +ITU logo + +## ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 | +| TESTING SPECIFICATIONS | Q.3900–Q.4099 | +| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100–Q.4139 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000–Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050–Q.5069 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T Q.4102 + +# Hybrid peer-to-peer communications: Peer protocol + +## Summary + +Recommendation ITU-T Q.4102 describes the peer protocol for communication among peers. The peer protocol enables peers to organize a tree-based overlay network in a hybrid peer-to-peer network and distribute data over the overlay network. This Recommendation also specifies the connection types among peers, resource elements types used in the message header, protocol messages exchanged among peers and information flows for describing behaviours of peer. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.4102 | 2022-02-13 | 11 | 11.1002/1000/14923 | + +## Keywords + +Hybrid peer-to-peer, peer protocol, tree-based overlay network. + +--- + +\* 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/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 2022 + +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 Connection types ..... | 3 | +| 7 Resource element types and messages of peer protocol..... | 3 | +| 7.1 Resource elements ..... | 3 | +| 7.2 Messages..... | 4 | +| 8 Protocol behaviours ..... | 22 | +| 8.1 Joining phase ..... | 22 | +| 8.2 Service phase..... | 23 | +| 8.3 Leaving phase..... | 29 | +| Bibliography..... | 31 | + + + +## Recommendation ITU-T Q.4102 + +# Hybrid peer-to-peer communications: Peer protocol + +# 1 Scope + +This Recommendation describes peer protocol for tree-based overlay network in hybrid peer-to-peer (HP2P) communications as follows: + +- connection types between peers; +- resource elements of protocol messages; +- protocol messages and its parameters; +- information flows for describing behaviours of peer. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions that, 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 Q.4100] Recommendation ITU-T Q.4100 (2020), *Hybrid peer-to-peer communications: Functional architecture*. +- [ITU-T Q.4101] Recommendation ITU-T Q.4101 (2021), *Hybrid peer-to-peer communications: Tree and data recovery procedures*. +- [ITU-T Q.4103] Recommendation ITU-T Q.4103, *Hybrid peer-to-peer (communications: Overlay management protocol*. +- [IETF RFC 7159] IETF RFC 7159 (2014), *The JavaScript Object Notation (JSON) Data Interchange Format*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 buffermap** [b-ITU-T X.609]: A map showing the downloading status of fragments comprising a shared content. + +**3.1.2 corresponding peer** [b-ITU-T X.609.4]: A peer that performs an operation on the request received from the requesting peer. + +**3.1.3 hybrid overlay network** [ITU-T Q.4100]: A peer-to-peer overlay network in which participating peers exchange data using the pull and push method. The hybrid overlay network also provides a way to organize and maintain a tree-style path for pushing data to all peers without loops, as well as fetching data from other peers simultaneously. + +**3.1.4 overlay network** [b-ITU-T X.1162]: An overlay network is a virtual network that runs on top of another network. Like any other network, the overlay network comprises a set of nodes and links between them. Because the links are logical ones, they may correspond to many physical links of the underlying network. + +**3.1.5 peer** [b-ITU-T X.1161]: Communication node on P2P network that functions simultaneously as both "client" and "server" to the other nodes on the network. + +**3.1.6 peer-to-peer (P2P)** [b-ITU-T Y.2206]: A system is considered to be P2P if the nodes of the system share their resources in order to provide the service the system supports. The nodes in the system both provide services to other nodes and request services from other nodes. + +NOTE – Peer is the node in a P2P system. + +**3.1.7 requesting peer** [b-ITU-T X.609.4]: A peer that sends a request to the other corresponding peer. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|----------------------------------| +| HOMS | Hybrid Overlay Management Server | +| HP2P | Hybrid Peer-to-Peer | +| NTP | Network Time Protocol | +| P2P | Peer-to-Peer | + +# 5 Conventions + +In this Recommendation, message flows among peers to describe the operation of each message and behaviours of peer protocol are drawn with solid arrow lines or dashed arrow lines. The solid arrow line indicates a mandatory message and the dashed arrow line indicates an optional message. + +![Legend for message types solid arrow dashed arrow](1c94fd3cebf58af136144f14160d128e_img.jpg) + +Legend for message types: + +- Mandatory message +- Optional message + +Q.4102(22) + +Legend for message types solid arrow dashed arrow + +An interface with a user is drawn with a dot dashed line. + +![Legend for user interface dot dashed arrow](740442c999390734911677f01af0316d_img.jpg) + +Legend for user interface: + +- An interface with a user + +Q.4102(22) + +Legend for user interface dot dashed arrow + +The connection between peers is presented by solid lines or dashed lines. A solid line between peers is a primary connection and a dashed line between peers is a candidate connection. A dashed arrow line between peers indicates an outgoing or incoming candidate connection. + +![Legend for peer connections solid line with circles dashed line with circles dashed arrow line with circles](ef7a88e04d1939ee09bafd5c3072adf8_img.jpg) + +Legend for peer connections: + +- Primary connection between peer 1 and peer 2 +- Candidate connection between peer 1 and peer 2 +- Outgoing candidate connection from peer 1 to peer 2 + +Q.4102(22) + +Legend for peer connections solid line with circles dashed line with circles dashed arrow line with circles + +In the response message under clause 7.2, *rsp-code* is a combination of the request type for classifying the type of request and the response type for classifying the type of response. For example, *rsp-code* will be 2200 if the request type is "2" and the response type is "200". However, figures under clause 7.2 do not show the exact value of *rsp-code* for ease of understanding about the meaning of the response. + +Resource elements in clause 7.1 and fields of message header and extension under clause 7.2 are encoded in JavaScript object notation (JSON) [IETF RFC 7159], and the grammar used in representing objects defined in this Recommendation is as follows: + +- "NUMBER", "STRING", "BOOLEAN" and "LIST" are types used to indicate number, string, boolean and list respectively; +- An array of collective values are enclosed in brackets "[ ]" with values separated by commas " , ". + +# 6 Connection types + +This clause describes the connections between peers. The concept of a path (primary path / secondary path) described in [ITU-T Q.4100] is defined as a connection in this Recommendation. These connections between peers in a tree-based overlay network are classified as follows: + +- **Primary connection:** This connection is established for data broadcasting between peers. A peer in a tree-based overlay network has one or more primary connections for sending and receiving data from other peers. However, it maintains only one primary connection between two identical peers. +- **Candidate connection:** This connection is not used for data broadcasting between peers, but it is established in advance to restore fast in loss of primary connection. When a peer has a problem to send and receive data through the primary connection, it is necessary to replace the old primary connection with the new primary connection immediately. Therefore, when a peer detects a loss of a primary connection, it switches one of the candidate connections to a new primary connection. + +# 7 Resource element types and messages of peer protocol + +## 7.1 Resource elements + +This clause specifies the basic resource elements to be used in messages to convey information regarding the operations of peer. + +### 7.1.1 PEER\_BUFFERMAP + +All peers maintain a caching buffer list for data received from other peers, which consists of a set of caching buffers in the form of a circular queue for each data source. The PEER\_BUFFERMAP element includes detailed information about caching buffer list in Table 7-1. + +**Table 7-1 – PEER\_BUFFERMAP resource element** + +| Keyword | Type | Description | +|-------------|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| buffmaplist | LIST[BUFFERMAP] | buffmaplist includes the list of buffermap information such as source peer id and sequence of data packets described in [ITU-T Q.4101]. | + +### 7.1.2 BUFFERMAP + +The BUFFERMAP element includes detailed information on the caching buffer such as an identifier of source peer and a sequence list of data packets information received from source peer in Table 7-2. + +**Table 7-2 – BUFFERMAP resource element** + +| Keyword | Type | Description | +|----------------|--------------|-----------------------------------------------------------------------------------------------------------------------------------| +| source-peer-id | STRING | source-peer-id indicates the identifier of the peer who has sent the BROADCAST_DATA request message. | +| sequence-list | LIST[NUMBER] | Sequence-list includes the list of sequence values in the data packet received through the BROADCAST_DATA request message. | + +## 7.2 Messages + +This clause describes the messages exchanged between peers to be used in the reference point R2 that is specified in [ITU-T Q.4100] and the header of messages is represented as JavaScript object notation (JSON) [IETF RFC 7159]. + +Figure 7-1 shows the format and length of the message. + +| Version | Type | Length | Header | Content | Extension | +|---------|--------|---------|----------|----------|-----------| +| 1 byte | 1 byte | 2 bytes | Variable | Variable | Variable | + +Q.4102(22) + +**Figure 7-1 – Message format of peer protocol** + +- *version*: this field means the version of the protocol, and the current version is assigned as 0x01. +- *type*: this field means the encoding type of the header, and 0x01 and 0x10 are assigned as type values. The current version is assigned as 0x01. In this case, 0x01 is defined as a text type and 0x10 is defined as a binary encoding type. +- *length*: this field means the length of the header field. +- *header*: this field contains a code that distinguishes whether a message is a request or a response and the necessary parameters for the message code. +- *content*: this field contains content data. The length of the content can be checked through the length value of the *payload* field included in the header. +- *extension*: this field contains private purpose parameters. + +The following subclauses describe the message flow between peers, the peer operation related to the message, and the detailed format of the header part of each message. + +### 7.2.1 HELLO\_PEER + +A peer can initiate overlay network join by exchange of HELLO\_PEER request and response message with other peers belonging to the overlay network. Figure 7-2 shows the message flow of HELLO\_PEER. + +![Sequence diagram showing the message flow of HELLO_PEER between Peer A and Peer B. Step 1: Peer A sends HELLO_PEER to Peer B. Step 2: Peer B responds with 202 Accepted. Step 3: Peer B forwards HELLO_PEER to another peer (indicated by a dashed arrow). Reference Q.4102(22) is noted below step 3.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +``` + +sequenceDiagram + participant Peer A + participant Peer B + Note right of Peer B: Q.4102(22) + Peer A->>Peer B: 1. HELLO_PEER + Peer B-->>Peer A: 2. 202 Accepted + Peer B-->>Peer B: 3. HELLO_PEER + +``` + +Sequence diagram showing the message flow of HELLO\_PEER between Peer A and Peer B. Step 1: Peer A sends HELLO\_PEER to Peer B. Step 2: Peer B responds with 202 Accepted. Step 3: Peer B forwards HELLO\_PEER to another peer (indicated by a dashed arrow). Reference Q.4102(22) is noted below step 3. + +**Figure 7-2 – Message flow of HELLO\_PEER** + +- ① When a new peer A wants to join an overlay network, it sends a HELLO\_PEER request message to one of the peers (peer B in Figure 7-2) participating in the overlay network. + +The list of peers participating in the overlay network is obtained from a hybrid overlay management server (HOMS). At this time, the peer sending a HELLO\_PEER request message acts as a requesting peer and the responding peer that interacts with requesting peer acts as a corresponding peer. + +- ② Peer B receiving the HELLO\_PEER request message firstly checks whether it is acceptable and then processes it if possible. Peer B can then send a 202 (accepted) response which indicates it has received the HELLO\_PEER request message. + +- ③ Peer B transfers the received HELLO\_PEER request message to the acceptable peers connected to their primary connection. + +This is determined by considering the maximum number of requesting connections. The maximum number of requesting connections is the same as the value of the *conn\_num* field within the HELLO\_PEER request message, or 1 is reduced here. The latter is when peer B handles the HELLO\_PEER request message. + +Peer B forwards the HELLO\_PEER request message to the peers with a primary connection relationship if the maximum number of requesting connections is greater than 0. Peer B divides the maximum number of requesting connections by the number of peers in the primary connection relationship and then forwards the HELLO\_PEER request message to each peer in the primary connection relationship. + +Table 7-3 describes the syntax and semantics of each field in the header of a HELLO\_PEER request message. + +**Table 7-3 – Header format of HELLO\_PEER request** + +| Syntax | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 {   "req-code": NUMBER,   "req-params": {     "operation": {       "overlay-id": STRING,       "conn_num": NUMBER,       "ttl": NUMBER,       "recovery": BOOLEAN     },     "peer": {       "peer-id": STRING,     }   } }
|
  • – req-code indicates the type of the request message. In case of a HELLO_PEER request message, req-code value is set as 1.
  • – overlay-id indicates an identifier of the overlay network that the new peer wants to participate.
  • – conn_num indicates the number of connections that the new peer wants to establish with other peers.
  • – ttl indicates the number of steps of the message the peer wants to pass on to. The new participating peer specifies the initial ttl value, and the peer receiving the HELLO_PEER message reduces the ttl value by one when forwarding the message.
| + +**Table 7-3 – Header format of HELLO\_PEER request** + +| Syntax | Description | +|-----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
         "address": STRING,         "ticket-id": NUMBER       }     }   } }
|
  • – recovery is used when an emergency recovery is needed. If a new peer joins the overlay network for the first time, this field is not used.
  • – peer-id indicates the identifier of the new participating peer.
  • – address indicates network address information of new participating peer that can be accessed by other peers.
  • – ticket-id indicates the ticket-id value for the new participating peer. ticket-id, a value that indicates the order of peer joined to the hybrid overlay network, which is taken from the HOMS defined in [ITU-T Q.4100]. This means a peer with a low ticket-id value has first joined the corresponding overlay network. When recovering from an overlay network problem, a ticket ID plays an important role in preventing a loop by causing the peer with a large ticket ID value to attempt recovery of a broken connection.
| + +Table 7-4 describes the syntax and semantics of each field in the header of a HELLO\_PEER response message. + +**Table 7-4 – Header format of HELLO\_PEER response** + +| Syntax | Description | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 {   "rsp-code": NUMBER }
|
  • – rsp-code indicates which response message is for which request. The rsp-code is a combination of the request type in classifying the type of request and the response type for classifying the type of response. The request type is defined in the req-code in the request message. In case of a HELLO_PEER response message, rsp-code value is set as 1202 if the result of the request is successful.
    • • rsp-code value 1202 is a combination of the request type (1) and response type (202). Response type 202 means 'accepted'. Therefore, rsp-code value 1202 means an 'accepted' response to the HELLO_PEER request message.
| + +### 7.2.2 ESTAB\_PEER + +A candidate connection can be established by exchange of an ESTAB\_PEER request and response messages. An ESTAB\_PEER request message is used by a peer which received a HELLO\_PEER request message from a newly joining peer to directly connect to the new peer that wants to join. Figure 7-3 shows the message flows of ESTAB\_PEER messages. + +![Sequence diagram showing the message flow of ESTAB_PEER between Peer A and Peer B. Peer A sends a 1. ESTAB_PEER request to Peer B. Peer B responds with a 2. 200 OK / 603 Decline. The diagram is labeled Q.4102(22).](af7916c89a458fdab6c3f443217388ae_img.jpg) + +``` + +sequenceDiagram + participant Peer A + participant Peer B + Note right of Peer B: Q.4102(22) + Peer A->>Peer B: 1. ESTAB_PEER + Peer B-->>Peer A: 2. 200 OK / 603 Decline + +``` + +Sequence diagram showing the message flow of ESTAB\_PEER between Peer A and Peer B. Peer A sends a 1. ESTAB\_PEER request to Peer B. Peer B responds with a 2. 200 OK / 603 Decline. The diagram is labeled Q.4102(22). + +**Figure 7-3 – Message flow of ESTAB\_PEER** + +- ① Peer A sends an ESTAB\_PEER request message to peer B. + +When peer A receives the HELLO\_PEER request message, peer A firstly checks if it has room in its network connection capability. If peer A is available, an ESTAB\_PEER request message is used for establishing connection to the peer's address of HELLO\_PEER request message. At this time, peer A acts as a requesting peer and peer B acts as a corresponding peer for the ESTAB\_PEER request message. + +- ② Upon receipt of the ESTAB\_PEER request message, peer B can send a 200 (OK) or 603 (decline) response. + +The peer B sends a 200 response if peer B accepts a new connection through the ESTAB\_PEER request message, or 603 if it refuses. At this time, if peer A receives the 200 response on the ESTAB\_PEER request message, a candidate connection between the two peers is established. + +If peer B has received ESTAB\_PEER request messages beyond ESTAB\_PEER\_TIMEOUT, peer B sends a 603 response. ESTAB\_PEER\_TIMEOUT is the maximum waiting time for receiving ESTAB\_PEER request messages from other peers. + +Table 7-5 describes the syntax and semantics of each field in the header of an ESTAB\_PEER request message. + +**Table 7-5 – Header format of ESTAB\_PEER request** + +| Syntax | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 {   "req-code": NUMBER,   "req-params": {     "operation": {       "overlay-id": STRING     },     "peer": {       "peer-id": STRING,       "ticket-id": NUMBER     }   } }
|
  • – req-code indicates the type of the request message. In case of an ESTAB_PEER request message, req-code value is set as 2.
  • – overlay-id indicates the identifier of an overlay network.
  • – peer-id indicates the identifier of the peer sending an ESTAB_PEER request.
  • – ticket-id indicates the ticket-id value of the peer sending the ESTAB_PEER request message. ticket-id is assigned from the HOMS through the HybridOverlayJoin message defined in [ITU-T Q.4103].
| + +Table 7-6 describes the syntax and semantics of each field in the header of an ESTAB\_PEER response message. + +**Table 7-6 – Header format of ESTAB\_PEER response** + +| Syntax | Description | +|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
{   "rsp-code": NUMBER }
|
  • – rsp-code indicates which response message is for which request. In case of an ESTAB_PEER response message, it is possible to have the 2200 or 2603 as a rsp-code value.
    • • rsp-code value 2200 is a combination of the request type (2) and response type (200). Response type 200 means 'OK'. Therefore, rsp-code value 2200 means an 'OK' response to the ESTAB_PEER request message.
    • • rsp-code value 2603 is a combination of the request type (2) and the response type (603). Response type 603 means 'decline'. Therefore, rsp-code value 2603 is a 'decline' response to the ESTAB_PEER request message.
| + +### 7.2.3 PROBE\_PEER + +Network distance between two peers in a candidate connection relationship can be calculated by the exchange of the PROBE\_PEER request and response messages. When a new peer that wants to join the overlay can establish multiple candidate connections through HELLO\_PEER and ESTAB\_PEER request messages, a peer sends a PROBE\_PEER request message that initiates checking the network distance for selecting the primary connection. Figure 7-4 shows the message flow of a PROBE\_PEER. + +![Sequence diagram showing the message flow between Peer A and Peer B for PROBE_PEER. Peer A sends a '1. PROBE_PEER' request to Peer B, and Peer B responds with '2. 200 OK'. The diagram is labeled Q.4102(22) at the bottom right.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +``` + +sequenceDiagram + participant Peer A + participant Peer B + Note right of Peer B: Q.4102(22) + Peer A->>Peer B: 1. PROBE_PEER + Peer B-->>Peer A: 2. 200 OK + +``` + +Sequence diagram showing the message flow between Peer A and Peer B for PROBE\_PEER. Peer A sends a '1. PROBE\_PEER' request to Peer B, and Peer B responds with '2. 200 OK'. The diagram is labeled Q.4102(22) at the bottom right. + +**Figure 7-4 – Messages flow of PROBE\_PEER** + +- ① Peer A sends a PROBE\_PEER request message with a network time protocol (NTP) timestamp information to peer B, and peer B answers the 200 response message with a NTP timestamp information. +- ② Peer A who receives a 200 response message to the PROBE\_PEER request message uses the NTP timestamp information to calculate the network cost between corresponding peers. This process is repeated for each corresponding peer associated with the requesting peer. + +Table 7-7 describes the syntax and semantics of each field in the header of a PROBE\_PEER request message. + +**Table 7-7 – Header format of PROBE\_PEER request** + +| Syntax | Description | +|--------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
{   "req-code": NUMBER,   "req-params": {     "operation": {       "ntp-time": STRING     }   } }
|
  • – req-code indicates the type of the request message. In case of a PROBE_PEER request message, req-code value is set as 3.
  • – ntp-time indicates the NTP timestamp or local time of a peer.
| + +Table 7-8 describes the syntax and semantics of each field in the header of a PROBE\_PEER response message. + +**Table 7-8 – Header format of PROBE\_PEER response** + +| Syntax | Description | +|--------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
{   "rsp-code": NUMBER,   "rsp-params": {     "operation": {       "ntp-time": STRING     }   } }
|
  • – rsp-code indicates which response message is for which request. In case of a PROBE_PEER response message, rsp-code value is set as 3200.
    • • rsp-code value 3200 is a combination of the request type (3) and response type (200). Therefore, rsp-code value 3200 is an 'OK' response to the PROBE_PEER request message.
  • – Time value of this ntp-time is used as the same one as the ntp-time within the PROBE_PEER request message (Table 7-7). The peer receiving this response checks the network distance by comparing it with its own NTP timestamp or local timestamp value.
| + +### 7.2.4 SET\_PRIMARY + +A primary connection can be established by exchange of a SET\_PRIMARY request and response messages. A SET\_PRIMARY request message is used when the peer selects one of the candidate connections established through the ESTAB\_PEER message as the primary connection. Peers wishing to join the overlay network can send SET\_PRIMARY request messages to the peer with the best network distance through HELLO\_PEER, ESTAB\_PEER, and PROBE\_PEER messages. Figure 7-5 shows the message flow of a SET\_PRIMARY. + +![Sequence diagram showing the message flow of SET_PRIMARY between Peer A and Peer B. Peer A sends a '1. SET_PRIMARY' message to Peer B. Peer B responds with '2. 200 OK / 603 Decline'. The diagram is labeled Q.4102(22) at the bottom right.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +``` + +sequenceDiagram + participant Peer A + participant Peer B + Note right of Peer B: Q.4102(22) + Peer A->>Peer B: 1. SET_PRIMARY + Peer B-->>Peer A: 2. 200 OK / 603 Decline + +``` + +Sequence diagram showing the message flow of SET\_PRIMARY between Peer A and Peer B. Peer A sends a '1. SET\_PRIMARY' message to Peer B. Peer B responds with '2. 200 OK / 603 Decline'. The diagram is labeled Q.4102(22) at the bottom right. + +**Figure 7-5 – Message flow of SET\_PRIMARY** + +- ① Peer A sends a SET\_PRIMARY request message with its own PEER\_BUFFERMAP to peer B. PEER\_BUFFERMAP expresses its own caching buffer information. + Peer A can process as follows according to its response to the SET\_PRIMARY request message. + Firstly, if the requesting peer receives a 200 response to the SET\_PRIMARY request message, the primary connection is established, and data can be transmitted from the overlay network. + The requesting peer compares its own buffer map with the buffer map of the corresponding peer, and if there is data that the requesting peer does not have, the requesting peer can request the data from the corresponding peer. + Secondly, if the requesting peer receives a 603 response to the SET\_PRIMARY request message, the requesting peer selects one among the other peers and tries again. +- ② Upon receipt of the SET\_PRIMARY request message, the corresponding peer B can respond in two ways. + First, if the primary connection setting is possible, the corresponding peer answers a 200 response to the SET\_PRIMARY request message after internal processing with the primary connection setting. At this time, the 200 response to the SET\_PRIMARY request message includes PEER\_BUFFERMAP representing the state of its own caching buffer. The corresponding peer compares its own buffer map with the requesting peer (peer A in Figure 7-5)'s buffer map, and if there is data that the corresponding peer does not have, it can request data from the requesting peer. + Second, if the primary connection cannot be established due to an internal problem, the corresponding peer answers the 603 response message to the SET\_PRIMARY request message. + +Table 7-9 describes the syntax and semantics of each field in the header of a SET\_PRIMARY request message. + +**Table 7-9 – Header format of SET\_PRIMARY request** + +| Syntax | Description | +|--------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
{   "req-code": NUMBER,   "req-params": {     "buffermap": PEER_BUFFERMAP   } }
|
  • – req-code indicates the type of the request message. In case of a SET_PRIMARY request message, req-code value is set as 4.
  • – buffermap indicates the caching buffer status of requesting peer.
| + +Table 7-10 describes the syntax and semantics of each field in the header of a SET\_PRIMARY response message. + +**Table 7-10 – Header format of SET\_PRIMARY response** + +| Syntax | Description | +|--------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
{   "rsp-code": NUMBER,   "rsp-params": {     "buffermap": PEER_BUFFERMAP   } }
|
  • – rsp-code indicates which response message is for which request. In case of a SET_PRIMARY response message, it is possible to have the 4200 or 4603 as a rsp-code value.
  • – rsp-code value 4200 is a combination of the request type (4) and response type (200). Therefore, rsp-code value 4200 means an 'OK' response to the SET_PRIMARY request message.
  • – rsp-code value 4603 is a combination of the request type (4) and response type (603). Therefore, rsp-code value 4603 is a 'decline' response to the SET_PRIMARY request message. Response type 603 is set when the corresponding peer receiving the SET_PRIMARY request cannot establish a primary connection with the requesting peer due to internal problems.
  • – buffermap indicates the caching buffer status of the corresponding peer.
| + +### 7.2.5 SET\_CANDIDATE + +A candidate connection relationship can optionally be confirmed by exchange of SET\_CANDIDATE request and response messages. A SET\_CANDIDATE request message is optionally used by a peer willing to express a candidate connection relationship to other peers. After a new peer generates multiple candidate connections from different peers via ESTAB\_PEER messages and checks the network distance via PROBE\_PEER messages, the new peer sends SET\_PRIMARY request messages to the peer with the best network distance. The new peer can also send SET\_CANDIDATE request messages to the other peers to confirm the relationship among them. Maintaining the candidate connection is intended for quick switchover when the primary connection has a problem. Figure 7-6 shows the message flow of SET\_CANDIDATE. + +![Sequence diagram showing the message flow of SET_CANDIDATE between Peer A and Peer B. Peer A sends a '1. SET_CANDIDATE' message to Peer B, and Peer B responds with a '2. 200 OK' message. The diagram is labeled Q.4102(22).](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +sequenceDiagram + participant Peer A + participant Peer B + Note right of Peer B: Q.4102(22) + Peer A->>Peer B: 1. SET_CANDIDATE + Peer B-->>Peer A: 2. 200 OK + +``` + +Sequence diagram showing the message flow of SET\_CANDIDATE between Peer A and Peer B. Peer A sends a '1. SET\_CANDIDATE' message to Peer B, and Peer B responds with a '2. 200 OK' message. The diagram is labeled Q.4102(22). + +**Figure 7-6 – Message flow of SET\_CANDIDATE** + +- ① Peer A sends a SET\_CANDIDATE request message to peer B. In this case, a requesting peer sending the SET\_CANDIDATE request message considers the corresponding peer as 'outgoing candidate'. On the contrary, a corresponding peer considers the requesting peer as an 'incoming candidate'. +- ② Upon receipt of the SET\_CANDIDATE request message, the corresponding peer sends a 200 response to the SET\_CANDIDATE request message after internal processing with the candidate connection setting. + +Table 7-11 describes the syntax and semantics of each field in the header of a SET\_CANDIDATE request message. + +**Table 7-11 – Header format of SET\_CANDIDATE request** + +| Syntax | Description | +|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| {
"req-code": NUMBER
} | – req-code indicates the type of the request message. In case of a SET_CANDIDATE request message, req-code value is set as 5. | + +Table 7-12 describes the syntax and semantics of each field in the header of a SET\_CANDIDATE response message. + +**Table 7-12 – Header format of SET\_CANDIDATE response** + +| Syntax | Description | +|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| {
"rsp-code": NUMBER
} | – rsp-code indicates the code value of the response message. In case of a SET_CANDIDATE response message, rsp-code value is set as 5200.
  • • rsp-code value 5200 is a combination of the request type (5) and response type (200). Therefore, rsp-code value 5200 is an 'OK' response to the SET_CANDIDATE request message.
| + +### 7.2.6 BROADCAST\_DATA + +Data can be delivered by exchange of BROADCAST\_DATA request and response messages. A BROADCAST\_DATA message is used by a peer to broadcast data to other peers in a primary connection relationship. Both binary and text are possible for the data to be transmitted. The peer receiving this message forwards it to other peers that have a primary connection with it. Figure 7-7 shows the message flow of BROADCAST\_DATA. + +![Sequence diagram showing the message flow of BROADCAST_DATA between Peer A and Peer B. Step 1: Peer A sends a BROADCAST_DATA request to Peer B. Step 2: Peer B forwards the BROADCAST_DATA request to other peers. Step 3: Peer B sends a 200 OK response back to Peer A. The diagram is labeled Q.4102(22).](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +``` + +sequenceDiagram + participant Peer A + participant Peer B + Note right of Peer B: Q.4102(22) + Peer A->>Peer B: 1. BROADCAST_DATA + Peer B-->>Peer B: 2. BROADCAST_DATA + Peer B-->>Peer A: 3. 200 OK + +``` + +Sequence diagram showing the message flow of BROADCAST\_DATA between Peer A and Peer B. Step 1: Peer A sends a BROADCAST\_DATA request to Peer B. Step 2: Peer B forwards the BROADCAST\_DATA request to other peers. Step 3: Peer B sends a 200 OK response back to Peer A. The diagram is labeled Q.4102(22). + +**Figure 7-7 – Message flow of BROADCAST\_DATA** + +- ① In order to deliver data over an overlay network, peer A sends a BROADCAST\_DATA request message to peer B with the length of the content data, the type of content data in the *payload* field, and the data it wants to deliver to peer B (the peers associated with the primary connection). +- ② Peer B receiving the BROADCAST\_DATA request message delivers the received BROADCAST\_DATA request message to other peers in the primary connection except for the requesting peer of the BROADCAST\_DATA request message. This BROADCAST\_DATA request message is delivered until it reaches the leaf node of the tree. +- ③ Upon receipt of the BROADCAST\_DATA request message, peer B sends a 200 response when the *ack* field of the BROADCAST\_DATA request message is true. +Peer ID is included in this BROADCAST\_DATA request message to identify who created and sent this data for the first time. *Payload* field within the BROADCAST\_DATA request message is composed of length and content-type which contains the information about the data that will be transmitted. + +Table 7-13 describes the syntax and semantics of each field in the header of a BROADCAST\_DATA request message. + +**Table 7-13 – Header format of BROADCAST\_DATA request** + +| Syntax | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 {   "req-code": NUMBER,   "req-params": {     "operation": {       "ack": BOOLEAN     },     "peer": {       "peer-id": STRING,       "sequence": NUMBER     },     "payload": {       "length": NUMBER,       "content-type": STRING     }   } }
|
  • – req-code indicates the type of the request message. In case of the BROADCAST_DATA request message, req-code value is set as 6.
  • – ack has a TRUE value if requesting peer wants to receive a response message. Default value is FALSE.
  • – peer-id indicates the ID of the peer that initially generated this BROADCAST_DATA request message, and it is possible to identify who created and sent this data for the first time.
  • – Whenever self-generated data is sent through the BROADCAST_DATA message, the value of the sequence field is increased by 1 and allocated. When forwarding data is received from another peer, this value of the sequence field is not modified.
  • – length indicates the length of the data that is carried and is described in bytes.
| + +**Table 7-13 – Header format of BROADCAST\_DATA request** + +| Syntax | Description | +|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
  • – content-type indicates the kind of data that is carried. It is described as the MIME type such as application/JSON, application/XML, etc. The processing of content according to content-type depends on the application using the peer protocol.
| + +The BROADCAST\_DATA request message shall use the extension field to specify an application specific parameter. + +Table 7-14 describes the syntax and semantics of each field in the extension of the BROADCAST\_DATA request message. + +**Table 7-14 – Extension format of BROADCAST\_DATA request** + +| Syntax | Description | +|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| {
"app-id": STRING
} |
  • – app-id indicates the identifier of the application using the peer protocol
| + +Table 7-15 describes the syntax and semantics of each field in the header of the BROADCAST\_DATA response message. + +**Table 7-15 – Header format of BROADCAST\_DATA response** + +| Syntax | Description | +|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| {
"rsp-code": NUMBER
} |
  • – rsp-code indicates which response message is for which request. In case of a BROADCAST_DATA response message, rsp-code value is set as 6200.
    • • rsp-code value 6200 is a combination of the request type (6) and the response type (200). Therefore, rsp-code value 6200 is an 'OK' response to the BROADCAST_DATA request message.
| + +### 7.2.7 HEARTBEAT + +The status of a connection between two peers can be checked by exchange of HEARTBEAT request and response messages. The peer can check the connection status of each other between peers. HEARTBEAT request message is periodically used to inform whether two peers are connected to each other or not. Figure 7-8 shows the message flow of HEARTBEAT. + +![Sequence diagram showing the message flow of HEARTBEAT between Peer A and Peer B. Peer A sends a 1. HEARTBEAT request to Peer B, and Peer B responds with a 2. 200 OK message.](d79d33da852cb7bca3e87b400a15c3e8_img.jpg) + +``` + +sequenceDiagram + participant Peer A + participant Peer B + Note right of Peer B: Q.4102(22) + Peer A->>Peer B: 1. HEARTBEAT + Peer B-->>Peer A: 2. 200 OK + +``` + +Sequence diagram showing the message flow of HEARTBEAT between Peer A and Peer B. Peer A sends a 1. HEARTBEAT request to Peer B, and Peer B responds with a 2. 200 OK message. + +**Figure 7-8 – Message flow of HEARTBEAT** + +- ① Peer A generates a HEARTBEAT request message to inform that the connection with a specific peer is maintained, and sends it to peer B, which wants to notify that the connection is maintained. +- ② Upon receipt of the HEARTBEAT request message, peer B sends a 200 response to the HEARTBEAT request message after internal processing. + +Table 7-16 describes the syntax and semantics of each field in the header of the HEARTBEAT request message. + +**Table 7-16 – Header format of HEARTBEAT request** + +| Syntax | Description | +|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| {
"req-code": NUMBER
} | – req-code indicates the type of the request message. In case of a HEARTBEAT request message, req-code value is set as 7. | + +Table 7-17 describes the syntax and semantics of each field in the header of the HEARTBEAT response message. + +**Table 7-17 – Header format of HEARTBEAT response** + +| Syntax | Description | +|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| {
"rsp-code": NUMBER
} | – rsp-code indicates which response message is for which request. In case of the HEARTBEAT response message, rsp-code value is set as 7200.
  • • rsp-code value 7200 is a combination of the request type (7) and the response type (200). Therefore, rsp-code value 7200 is an 'OK' response to the HEARTBEAT request message.
| + +### 7.2.8 SCAN\_TREE + +The structure of an overlay network can be identified by the exchange of SCAN\_TREE request and response messages. The peer can scan connection features among peers with the primary connection relationship. The SCAN\_TREE request message is used to initiate the scan of the connection shape of peers connected to the primary connection. Figure 7-9 shows the message flow of SCAN\_TREE. + +![Sequence diagram showing the message flow of SCAN_TREE between Peer A and Peer B. The sequence is: 1. SCAN_TREE (solid arrow A to B), 2. 200 OK (solid arrow B to A), 3. 100 Trying (dashed arrow B to A), 4. SCAN_TREE (dashed arrow B to an external destination), 5. 100 Trying (dashed arrow from external destination to B), 6. 200 OK (dashed arrow from external destination to B), 7. 200 OK (dashed arrow B to A). The diagram is labeled Q.4102(22) in the bottom right.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +Sequence diagram showing the message flow of SCAN\_TREE between Peer A and Peer B. The sequence is: 1. SCAN\_TREE (solid arrow A to B), 2. 200 OK (solid arrow B to A), 3. 100 Trying (dashed arrow B to A), 4. SCAN\_TREE (dashed arrow B to an external destination), 5. 100 Trying (dashed arrow from external destination to B), 6. 200 OK (dashed arrow from external destination to B), 7. 200 OK (dashed arrow B to A). The diagram is labeled Q.4102(22) in the bottom right. + +**Figure 7-9 – Message flow of SCAN\_TREE** + +- ① Requesting peer A generates and sends a SCAN\_TREE request message to peer B. + At this time, a random digit number is added in the *cseq* field within the SCAN\_TREE message. Also, peer information (peer-id, address) on the requesting peer is added in the *via* field within the SCAN\_TREE message. *Via* field is a listed set of peer information that is composed of a peer-id and an address. New peer information is added in the first location of the listed set (i.e., start point of the list). +- ② If peer B is a leaf node of the tree, corresponding peer B sends a 200 response message to the requesting peer A. + The corresponding peer that has received the SCAN\_TREE request message can be an intermediate node or a leaf node of a tree. If the corresponding peer that receives the SCAN\_TREE request message has a peer relationship with another peer (except the requesting peer), that peer is an intermediate node of a tree. Otherwise, the corresponding peer is a leaf node of a tree. + At this time, peer information (peer-id, address) on the corresponding peer is added in the *path* field within the 200 response message. *Path* field is a listed set of peer information that is composed of a peer-id and an address. The information on the corresponding peer that has received the SCAN\_TREE request message is added in the last location of the listed set (i.e., the end point of the list). + The destination of the 200 response message is the first address of the *via* field within SCAN\_TREE (i.e., start point of the list). +- ③ If peer B is an intermediate node of a tree, corresponding peer B sends a 100 (trying) response message to the requesting peer A. +- ④ If peer B is an intermediate node of a tree, it sends the SCAN\_TREE message to the other peers with a primary connection relationship (except the requesting peer). + At this time, the transferred SCAN\_TREE request message includes its peer information in the *via* field. The forwarded SCAN\_TREE request message contains the addition of its own peer information in the first location *via* field within the received original SCAN\_TREE request message. A new generated SCAN\_TREE request message is sent to other peers with a primary connection relationship (except the requesting peer). The new generated SCAN\_TREE request message does not route to the requesting peer to prevent a loop. +- ⑤ If peer B has received a 100 response message from another peer with a primary connection relationship, the requesting peer B waits for the 200 response message after internal processing. + +- ⑥ If peer B has received a 200 response message from another peer with a primary connection relationship, peer B sends the 200 response message to the requesting peer A. + +At this time, peer B checks if the first (begin) address information *via* field matches its address information. If it matches, peer B is the original requesting peer, otherwise, peer B is the intermediate requesting peer + +If the requesting peer is the intermediate requesting peer (i.e., matching), the requesting peer moves the top address information *via* field to the top address of the *path* field within the 200 response, and then transfers the changed 200 response to the top address of the *via* field. Each peer should operate stateless so that they can be transferred up and down without managing the previous history or state of request and response message. + +- ⑦ Peer A, who has received the 200 response message, performs the internal processing to express the relationship of peers constituting the tree. + +If the requesting peer is the original requesting peer, the requesting peer can identify the composition and the order of the peers in the branch that make up the tree. This can be determined from a listed set of peer information contained in a *path* field of the 200 response. + +An original requesting peer that has created a SCAN\_TREE request message can receive multiple 200 responses. + +Table 7-18 describes the syntax and semantics of each field in the header of the SCAN\_TREE request message. + +**Table 7-18 – Header format of SCAN\_TREE request** + +| Syntax | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
{   "req-code": NUMBER,   "req-params": {     "cseq": NUMBER,     "overlay": {       "overlay-id": STRING,       "via": LIST[STRING]     },     "peer": {       "peer-id": STRING,       "address": STRING,       "ticket-id": NUMBER     }   } }
|
  • – req-code indicates the type of the request message. In case of a SCAN_TREE request message, the req-code value is set as 8.
  • – cseq is a command sequence number. This value is created at random by the peer that sends the SCAN_TREE message for the first time.
  • – overlay-id indicates the identifier of the overlay network.
  • – via indicates a listed set of peer information on the path from which the message has been delivered.
  • – peer-id indicates the identifier for the requesting peer of the SCAN_TREE message.
  • – address indicates the IP address information for the requesting peer of the SCAN_TREE message.
  • – ticket-id indicates the ticket-id value for the requesting peer of the SCAN_TREE message.
| + +Table 7-19 describes the syntax and semantics of each field in the header of the SCAN\_TREE response message. + +**Table 7-19 – Header format of SCAN\_TREE response** + +| Syntax | Description | +|------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
{   "rsp-code": NUMBER,   "rsp-params": {
|
  • – rsp-code indicates which response message is for which request. In case of a SCAN_TREE response message, it is possible to have the 8200 or 8100 as an rsp-code value.
| + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 "cseq": NUMBER, "overlay": {   "overlay-id": STRING,   "via": LIST[STRING],   "path": LIST[STRING] }, "peer": {   "peer-id": STRING,   "address": STRING,   "ticket-id": NUMBER } } } } }
|
  • • When the corresponding peer receiving the SCAN_TREE request message is a leaf node, 8200 is used. rsp-code value 8200 is a combination of the request type (8) and the response type (200). Therefore, rsp-code value 8200 is an 'OK' response to the SCAN_TREE request message.
  • • When the corresponding peer receiving the SCAN_TREE request message is not a leaf node, 8100 is used. rsp-code value 8100 is a combination of the request type (8) and the response type (100). Code value 100 means 'trying'. Therefore, rsp-code value 8100 is a 'trying' response to the SCAN_TREE request message.
  • – cseq is a command sequence number. The cseq value in the SCAN_TREE request message is copied as it is.
  • – overlay-id indicates the identifier of the overlay network. The overlay-id value in the SCAN_TREE request message is copied as it is.
  • – via indicates a listed set of peer information on the path from which the message has been delivered.
  • – path indicates a listed set of peer information on the path taken by the response message so far.
  • – peer-id indicates the identifier for the requesting peer of SCAN_TREE request message.
  • – address indicates the IP address information for the requesting peer of the SCAN_TREE request message.
  • – ticket-id indicates the ticket-id value for the requesting peer of a SCAN_TREE request message.
| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 7.2.9 RELEASE\_PEER + +A peer can gracefully exit from the overlay network currently participating by exchange of RELEASE\_PEER request and response messages. A RELEASE\_PEER request message is used when a peer no longer wants to participate in the overlay network currently participating. Requesting peer explicitly sends this message to the peer that wants to terminate the peer-to-peer connection. Figure 7-10 shows the message flows of RELEASE\_PEER. + +![Sequence diagram showing the message flow of RELEASE_PEER between Peer A and Peer B. Peer A sends a '1. RELEASE_PEER' request to Peer B. Peer B responds with a '2. 200 OK' response. The diagram is labeled Q.4102(22).](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` + +sequenceDiagram + participant Peer A + participant Peer B + Peer A->>Peer B: 1. RELEASE_PEER + Peer B-->>Peer A: 2. 200 OK + Note right of Peer B: Q.4102(22) + +``` + +Sequence diagram showing the message flow of RELEASE\_PEER between Peer A and Peer B. Peer A sends a '1. RELEASE\_PEER' request to Peer B. Peer B responds with a '2. 200 OK' response. The diagram is labeled Q.4102(22). + +**Figure 7-10 – Message flow of RELEASE\_PEER** + +- ① Peer A transmits a RELEASE\_PEER request message to peer B to terminate the connection. In order to prevent any peer from terminating the connection, peer A signs the entire RELEASE\_PEER request message with a private key and sends it including its own signature. +- ② Upon receipt of the RELEASE\_PEER request message, peer B sends a 200 response after internal processing when the *ack* field of the RELEASE\_PEER request message is set to *TRUE*. + +Table 7-20 describes the syntax and semantics of each field in the header of the RELEASE\_PEER request message. + +**Table 7-20 – Header format of RELEASE\_PEER request** + +| Syntax | Description | +|----------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
{   "req-code": NUMBER,   "req-params": {     "operation": {       "ack": BOOLEAN     }   } }
|
  • – req-code indicates the type of the request message. In case of a RELEASE_PEER request message, req-code value is set as 9.
  • – ack has a TRUE value if a receive a response message is needed. Default value is FALSE.
| + +Table 7-21 describes the syntax and semantics of each field in the header of the RELEASE\_PEER response message. + +**Table 7-21 – Header format of RELEASE\_PEER response** + +| Syntax | Description | +|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
{   "rsp-code": NUMBER }
|
  • – rsp-code indicates which response message is for which request. In case of the RELEASE_PEER response message, rsp-code value is set as 9200.
    • • rsp-code value 9200 is a combination of the request type (9) and the response type (200). Therefore, rsp-code value 9200 is an 'OK' response to the RELEASE_PEER request message.
| + +### 7.2.10 BUFFERMAP + +Peers can share their buffermap information with each other by exchanging BUFFERMAP request and response messages. A BUFFERMAP request message is used to initiate information sharing. Figure 7-11 shows the message flow of BUFFERMAP. + +![Sequence diagram showing the message flow of BUFFERMAP between Peer A and Peer B. Peer A sends a '1. BUFFERMAP' request to Peer B, and Peer B responds with a '2. 200 OK' message. The diagram is labeled Q.4102(22) at the bottom right.](e7c6a6e4c3047dac05a3b92e396e9794_img.jpg) + +``` + +sequenceDiagram + participant Peer A + participant Peer B + Note right of Peer B: Q.4102(22) + Peer A->>Peer B: 1. BUFFERMAP + Peer B-->>Peer A: 2. 200 OK + +``` + +Sequence diagram showing the message flow of BUFFERMAP between Peer A and Peer B. Peer A sends a '1. BUFFERMAP' request to Peer B, and Peer B responds with a '2. 200 OK' message. The diagram is labeled Q.4102(22) at the bottom right. + +**Figure 7-11 – Message flow of BUFFERMAP** + +- ① Peer A generates and sends a BUFFERMAP request message to peer B. + +- ② Peer B sends a 200 response message including its own buffer map to the requesting peer A. At this time, the 200 response includes the buffer map information representing its own caching state in the form of a PEER\_BUFFERMAP defined in clause 7.1.1. + +Table 7-22 describes the syntax and semantics of each field in the header of the BUFFERMAP request message. + +**Table 7-22 – Header format of BUFFERMAP request** + +| Syntax | Description | +|-------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
{   "req-code": NUMBER,   "req-params": {     "overlay-id": STRING   } }
|
  • – req-code indicates the type of the request message. In case of a BUFFERMAP request message, req-code value is set as 10.
  • – overlay-id indicates the identifier of the overlay network.
| + +Table 7-23 describes the syntax and semantics of each field in the header of a BUFFERMAP response message. + +**Table 7-23 – Header format of BUFFERMAP response** + +| Syntax | Description | +|----------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
{   "rsp-code": NUMBER,   "rsp-params": {     "overlay-id": STRING,     "buffermap": PEER_BUFFERMAP   } }
|
  • – rsp-code indicates which response message is for which request. In case of a BUFFERMAP response message, the rsp-code value is set as 10200.
    • • rsp-code value 10200 is a combination of the request type (10) and the response type (200). Therefore, rsp-code value 10200 is an 'OK' response to the BUFFERMAP request message.
  • – overlay-id indicates the identifier of the overlay network.
  • – buffermap expresses its own caching buffer state in the form of PEER_BUFFERMAP.
| + +### 7.2.11 GET\_DATA + +A peer can get specific data from other peers by exchange of GET\_DATA request and response messages. A GET\_DATA message is used to request the data with the specific sequence number held by another peer. Figure 7-12 shows the message flow of GET\_DATA. + +![Sequence diagram showing the message flow of GET_DATA between Peer A and Peer B. Peer A sends a GET_DATA request to Peer B, and Peer B responds with a 200 OK message. The diagram is labeled Q.4102(22).](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +``` + +sequenceDiagram + participant Peer A + participant Peer B + Note right of Peer B: Q.4102(22) + Peer A->>Peer B: 1. GET_DATA + Peer B-->>Peer A: 2. 200 OK + +``` + +Sequence diagram showing the message flow of GET\_DATA between Peer A and Peer B. Peer A sends a GET\_DATA request to Peer B, and Peer B responds with a 200 OK message. The diagram is labeled Q.4102(22). + +**Figure 7-12 – Message flow of GET\_DATA** + +- ① Requesting peer A generates and sends a GET\_DATA request message to peer B. +At this time, the GET\_DATA request message includes the sequence number that a requesting peer A wants to obtain. +- ② Peer B sends a 200 response message containing data of the requested sequence number to requesting peer A. +At this time, the 200 response includes the content data by the requesting peer's request in the *content* field, the length and the type of content data in the *payload* field in the *header* field, and the identifier of the application in the *extension* field. + +Table 7-24 describes the syntax and semantics of each field in the header in the GET\_DATA request message. + +**Table 7-24 – Header format of GET\_DATA request** + +| Syntax | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 {   "req-code": NUMBER,   "req-params": {     "overlay-id": STRING,     "source-id": STRING,     "sequence": NUMBER   } }
|
  • – req-code indicates the type of the request message. In case of GET_DATA request message, req-code value is set as 11.
  • – overlay-id indicates the identifier of the overlay network.
  • – source_id indicates the source ID of the desired data.
  • – sequence indicates the sequence number of the desired data.
| + +Table 7-25 describes the syntax and semantics of each field in the header in the GET\_DATA response message. + +**Table 7-25 – Header format of GET\_DATA response** + +| Syntax | Description | +|---------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 {   "rsp-code": NUMBER,   "rsp-params": {     "peer": {       "peer-id": STRING     }   }, }
|
  • – rsp-code indicates which response message is for which request. In case of a GET_DATA response message, the rsp-code value is set as 11200.
    • • rsp-code value 11200 is a combination of the request type (11) and the response type (200). Therefore, rsp-code
| + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
         "sequence": NUMBER,         "payload": {             "length": NUMBER,             "content-type": STRING         }     } }
|

value 11200 is an 'OK' response to the GET_DATA request message.

  • – peer-id indicates the peer ID of the data packet included in the content data, which matches the source-id of the GET_DATA request message.
  • – sequence indicates the sequence number of the data packet included in the content data, which matches the sequence of the GET_DATA request message.
  • – length indicates the length of the data that is carried and is described in bytes.
  • – content-type indicates the kind of data that is carried. It is described as the MIME type such as application/JSON, application/XML, etc. The processing of content according to content-type depends on the application using the peer protocol.
| +|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +The GET\_DATA response message shall use an extension field to specify application specific parameter. + +Table 7-26 describes the syntax and semantics of each field in the extension in the GET\_DATA response message. + +**Table 7-26 – Extension format of GET\_DATA response** + +| Syntax | Description | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| 
 {     "app-id": STRING }
|
  • – app-id indicates the identifier of an application using the peer protocol
| + +# 8 Protocol behaviours + +This clause describes the information flows of protocol operations such as joining and leaving an overlay network, broadcast of data, pruning of dead peer, tree and data recovery and tree scanning. + +## 8.1 Joining phase + +This clause describes the case of joining a new existing overlay network. The new peer chooses peers from a list of peers and sends a HELLO\_PEER request message with the maximum number of connections to the peers to which it wishes to connect. The receiving peer that can accept the new connection sends an ESTAB\_PEER request message so that the new peer makes the desired connection. + +Figure 8-1 shows the procedure for peer A to join an existing overlay network. In the existing overlay network, it is assumed that peer 1 has a primary connection with peer 2, and peer 2 with peer 3. + +![Sequence diagram showing the message flow for joining an overlay network. Peer A sends a HELLO_PEER request to Peer 1. Peer 1 responds with 202 Accepted and forwards the request to Peer 2. Peer 2 responds with 202 Accepted and forwards the request to Peer 3. Peer 3 responds with 202 Accepted. Peer 2 and Peer 3 then send ESTAB_PEER requests to Peer A. Peer A responds with 200 OK to both requests. A callout box shows the HELLO_PEER message structure: w.conn_num, address info., ... . A cloud diagram on the left shows Peer A joining a network of three peers (1, 2, 3).](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg) + +``` + +sequenceDiagram + participant Peer A + participant Peer 1 + participant Peer 2 + participant Peer 3 + + Note left of Peer A: Join overlay + Peer A->>Peer 1: 1. HELLO_PEER + Peer 1-->>Peer A: 2. 202 Accepted + Note right of Peer 1: w.conn_num, address info., ... + Peer 1->>Peer 2: 3. HELLO_PEER + Peer 2-->>Peer 1: 202 Accepted + Peer 2->>Peer 3: 3. HELLO_PEER + Peer 3-->>Peer 2: 202 Accepted + Peer 2->>Peer A: 4. ESTAB_PEER + Peer A-->>Peer 2: 5. 200 OK + Peer 3->>Peer A: 4. ESTAB_PEER + Peer A-->>Peer 3: 5. 200 OK + +``` + +Sequence diagram showing the message flow for joining an overlay network. Peer A sends a HELLO\_PEER request to Peer 1. Peer 1 responds with 202 Accepted and forwards the request to Peer 2. Peer 2 responds with 202 Accepted and forwards the request to Peer 3. Peer 3 responds with 202 Accepted. Peer 2 and Peer 3 then send ESTAB\_PEER requests to Peer A. Peer A responds with 200 OK to both requests. A callout box shows the HELLO\_PEER message structure: w.conn\_num, address info., ... . A cloud diagram on the left shows Peer A joining a network of three peers (1, 2, 3). + +**Figure 8-1 – Message flow for joining an overlay network** + +- ① When peer A wants to join an overlay network, it sends a HELLO\_PEER request message to one of the peers participating in the overlay network. Peer A sends a HELLO\_PEER request message to peer 1. +At this time, the list of peers participating in the overlay network is obtained from the HOMS through the HybridOverlayJoin message defined in [ITU-T Q.4103]. +The HELLO\_PEER request message must contain *conn\_num* and *address* information of peer A as specified in clause 7.2.1 of this Recommendation. *conn\_num* information is the number of requesting connections and address information is one that can be accessed by other peers. +- ② Peer 1 firstly checks whether the received HELLO\_PEER request message is acceptable, and if possible, sends a 202 response message to peer A. +- ③ Peer 1 checks whether the number of requesting connections in the HELLO\_PEER request message is satisfied according to the maximum number of requests specified in clause 7.2.1 of this Recommendation, and if not, delivers the received HELLO\_PEER request message to the peer connected through the primary connection. +At this time, it is assumed that peer A sets the number of requested connections to 1 or more. Therefore, peer 1 forwards the HELLO\_PEER request message to peer 2, and peer 2 forwards it to peer 3. +- ④ Peers receiving the HELLO\_PEER request message checks whether the resource is available and then sends an ESTAB\_PEER request message to peer A. In Figure 8-1, peer 2 and peer 3 send an ESTAB\_PEER request message to peer A. +- ⑤ Peer A receiving the ESTAB\_PEER message sends a 200 response if it wishes to accept the request. If peer A receives the ESTAB\_PEER message after ESTAB\_PEER\_TIMEOUT, it sends a 603 response as specified in clause 7.2.2 of this Recommendation. + +Thereafter, peer A calculates the network distance using PROBE\_PEER messages for the created connections as specified in clause 7.2.3 of this Recommendation. Peer A shall send a SET\_PRIMARY request message to one peer with the optimum network distance as specified in clause 7.2.4 of this Recommendation, and may send a SET\_CANDIDATE request message to the others as specified in clause 7.2.5 of this Recommendation. + +## 8.2 Service phase + +### 8.2.1 Broadcast of data + +This clause describes when a peer wants to send data to other peers participating in the same overlay network. Peer A sends a BROADCAST\_DATA request message to the peers in the primary connection relationship, and the peer receiving this message relays it to the other peers, and the BROADCAST\_DATA message is delivered to the leaf node through the intermediate nodes of the tree-based overlay network. + +Figure 8-2 shows the procedure for peer A to deliver data to peers in a primary connection. It is assumed that peer A has a primary connection with peer 2, peer 2 with peers 1 and 3, and peer 1 with peer 4. + +![Sequence diagram showing the message flow for broadcast of data. Peer A sends a BROADCAST_DATA message to Peer 2, which then relays it to Peers 1 and 3, and finally Peer 1 relays it to Peer 4. Each peer sends a 200 OK response back to the sender. A cloud diagram on the left shows the network topology: Peer A (orange circle) is connected to Peer 2 (blue circle); Peer 2 is connected to Peers 1 (blue circle) and 3 (blue circle); Peer 1 is connected to Peer 4 (blue circle).](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) + +The diagram illustrates the message flow for broadcasting data in a tree-based overlay network. The sequence of messages is as follows: + +- Peer A sends a **1. BROADCAST\_DATA** message to Peer 2. +- Peer 2 responds with a **200 OK** message to Peer A. +- Peer 2 then sends a **2. BROADCAST\_DATA** message to Peer 1. +- Peer 1 responds with a **200 OK** message to Peer 2. +- Peer 2 also sends a **2. BROADCAST\_DATA** message to Peer 3. +- Peer 3 responds with a **200 OK** message to Peer 2. +- Peer 1 then sends a **3. BROADCAST\_DATA** message to Peer 4. +- Peer 4 responds with a **200 OK** message to Peer 1. + +A cloud diagram on the left shows the network topology: Peer A (orange circle) is connected to Peer 2 (blue circle); Peer 2 is connected to Peers 1 (blue circle) and 3 (blue circle); Peer 1 is connected to Peer 4 (blue circle). The message flow follows this tree structure. + +Q.4102(22) + +Sequence diagram showing the message flow for broadcast of data. Peer A sends a BROADCAST\_DATA message to Peer 2, which then relays it to Peers 1 and 3, and finally Peer 1 relays it to Peer 4. Each peer sends a 200 OK response back to the sender. A cloud diagram on the left shows the network topology: Peer A (orange circle) is connected to Peer 2 (blue circle); Peer 2 is connected to Peers 1 (blue circle) and 3 (blue circle); Peer 1 is connected to Peer 4 (blue circle). + +**Figure 8-2 – Message flow for broadcast of data** + +- ① Peer A generates and sends a BROADCAST\_DATA request message to peer 2 with the primary connection relationship. + +Since this BROADCAST\_DATA request message was originated by peer A, peer A assigns values to the *peer-id* and *sequence* fields when it generates the BROADCAST\_DATA request message. The *Payload* field within the BROADCAST\_DATA request message is composed of *length* and *content-type* fields which contain information about the content data that will be transmitted. Peer A can also assign the identifier of an application using the peer protocol to the *app-id* field within an extension. + +Upon receipt of the BROADCAST\_DATA request message, peer 2 sends a 200 response when the *ack* field of the BROADCAST\_DATA request message is set to TRUE. + +- ② Peer 2, receiving the BROADCAST\_DATA message, delivers the received BROADCAST\_DATA request message to peer 1 and peer 3 in the primary connection. + +Peer ID is included in this BROADCAST\_DATA message to identify who created and sent this data for the first time. + +- ③ The BROADCAST\_DATA request message is delivered until it reaches the leaf node of the tree. Therefore, peer 1 forwards the BROADCAST\_DATA request message to peer 4. + +Upon receipt of the BROADCAST\_DATA request message, peer 1, peer 3, and peer 4 sends a 200 response when the *ack* field of the BROADCAST\_DATA request message is set to TRUE. + +### 8.2.2 Pruning of a dead peer + +If a peer leaves gracefully by explicitly sending a RELEASE\_PEER request message to its peers with a primary connection relationship. The corresponding peers can detect and initiate a tree recovery procedure if the leaving peer is peer in a primary connection relationship with a lower *ticket-id*. In the case of an ungraceful leaving, the peer with a higher *ticket-id* is responsible for detecting a dead peer by periodically sending a HEARTBEAT request message. The *heartbeat-interval* and *heartbeat-timeout* of the HEARTBEAT request message is provided from HOMS when the peer joins the overlay network. + +Figure 8-3 shows the procedures for detecting a dead peer leaving ungracefully. + +![Sequence diagram showing message flows for pruning a dead peer between Peer A and Peer 1.](4f148853ae68fdcf5e43f7604cab457d_img.jpg) + +The diagram illustrates the interaction between Peer A and Peer 1 for detecting a dead peer. Peer A sends a HEARTBEAT message (1) to Peer 1. Peer 1 responds with a 200 OK message (2). A dashed box next to Peer 1 indicates it has a lower *ticket-id*. After a *heartbeat-interval*, Peer A sends another HEARTBEAT message (3). Since Peer 1 is leaving ungracefully, it does not respond. After a *heartbeat-timeout*, Peer A detects the dead peer and initiates tree recovery, indicated by a dashed arrow pointing left. + +``` +sequenceDiagram + participant Peer A + participant Peer 1 + Note right of Peer 1: w.lower ticket-id + Peer A->>Peer 1: 1. HEARTBEAT + Peer 1-->>Peer A: 2. 200 OK + Note left of Peer A: Heartbeat-interval + Peer A->>Peer 1: 3. HEARTBEAT + Note left of Peer A: Heartbeat-timeout + Peer A-->>Left: Prune peer and initiate tree recovery + Note right of Peer 1: Ungraceful +``` + +Sequence diagram showing message flows for pruning a dead peer between Peer A and Peer 1. + +Figure 8-3 – Message flows for pruning of dead peer + +- ① Peer A with a higher *ticket-id* sends a HEARTBEAT request message to peer 1 in the primary connection relationship. +- ② Peer 1 with a lower *ticket-id* responds with a 200 response on receiving the HEARTBEAT request message. +- ③ After a specific time is set as *heartbeat-interval*, peer A sends a HEARTBEAT request message. If the corresponding peer does not respond to this request, the requesting peer waits until *heartbeat-timeout* passes. If there is no response after the *heartbeat-timeout* time, the requesting peer treats the nonresponsive peer as a dead peer and initiates a tree recovery procedure. + +### 8.2.3 Tree recovery + +When a peer detects an event regarding the leaving of a peer in a primary connection relationship with a higher *ticket-id*, it initiates a tree recovery procedure. It can detect the leave by using a periodic HEARTBEAT message or from an event fired from the underlying transport layer. The procedures for recovering the hybrid overlay network are specified in clause 7.2 of [ITU-T Q.4101] in detail. + +Figure 8-4 shows the procedures for tree recovery. It is assumed that peer A established a primary connection with peer 1, and it has a candidate connection with peer 2 and peer 3. It is assumed that + +the overlay network does not require data recovery. This is useful in the case where recovering timely old data is useless, such as live media streaming. + +![Sequence diagram illustrating the message flow for tree recovery. It shows four vertical lifelines: Peer A, Peer 1, Peer 2, and Peer 3. Peer 1 is labeled as 'Primary peer', while Peer 2 and Peer 3 are labeled as 'Candidate peer'. A dashed arrow from the left points to Peer A with the text 'Detect the leave of peer 1'. Peer A sends a '1. SET_PRIMARY' message to Peer 2. Peer 2 responds with '2. 200 OK' back to Peer A. The diagram is labeled 'Q.4102(22)' in the bottom right corner.](d9843ac5dfc4bbe9e4d21b8898723b5e_img.jpg) + +Sequence diagram illustrating the message flow for tree recovery. It shows four vertical lifelines: Peer A, Peer 1, Peer 2, and Peer 3. Peer 1 is labeled as 'Primary peer', while Peer 2 and Peer 3 are labeled as 'Candidate peer'. A dashed arrow from the left points to Peer A with the text 'Detect the leave of peer 1'. Peer A sends a '1. SET\_PRIMARY' message to Peer 2. Peer 2 responds with '2. 200 OK' back to Peer A. The diagram is labeled 'Q.4102(22)' in the bottom right corner. + +**Figure 8-4 – Message flow for tree recovery** + +- ① Peer A sends a SET\_PRIMARY request message to its outgoing candidate connection that is connected to peer 2. +- ② If peer 2 has enough resource, it responds with success (200). On sending and receiving the response, both peers regard a primary connection between them as established, and they can use the connection for data delivery immediately. + +If a peer receiving a SET\_PRIMARY request message does not have enough resources available, it responds with an error response. On receiving the error response, the requesting peer immediately sends a SET\_PRIMARY request message to another peer in the candidate connection relationship. If there no more exists a candidate connection, the requesting peer requests entry into the peer list to HOMS as soon as possible. On acquiring the entry peer list from HOMS, the requesting peer initiates an overlay joining procedures specified in clause 8.1 of this Recommendation with its own ticket-id that is issued at the initial joining phase. If there is no entry peer list from HOMS, it indicates that the requesting peer is the one that has the lowest *ticket-id*. In this case, it stops the initiation procedures to wait for the tree recovery procedure initiated by other peers with higher *ticket-id*. + +### 8.2.4 Data recovery + +When a hybrid overlay network requires data recovery that has been lost during the recovery of the tree, all peers keep their own cache for a pre-specified amount of time and quantity of messages. The amount and the number of messages to be cached are specified on creating the overlay network, and the policies are delivered to each peer on its joining by interacting with HOMS. The procedures for data recovery are specified in clause 8.2.2 of [ITU-T Q.4101] in detail. + +Figure 8-5 shows the information flow for recovering data lost during the tree recovery procedures. It is assumed that the peers are configured to recover the data using push mode. + +![Sequence diagram illustrating the message flow for data recovery between Peer A, Peer 1, and Peer 2. Peer A detects the leave of Peer 1 and sends a SET_PRIMARY request to Peer 2. Peer 2 responds with a 200 OK. Peer 2 then sends a BROADCAST_DATA request to Peer A, which in turn sends a BROADCAST_DATA request to Peer 1. Peer 1 sends a BROADCAST_DATA request to Peer 2. Callouts indicate Peer 1 is the 'Primary peer' and Peer 2 is a 'Candidate peer', with 'w. buffermap' (with buffermap) being included in the messages.](08dce7ad4c512fdf0c0cde60415fade6_img.jpg) + +``` + +sequenceDiagram + participant Peer A + participant Peer 1 + participant Peer 2 + Note left of Peer A: Detect the leave of peer 1 + Peer A->>Peer 2: 1. SET_PRIMARY (w. buffermap) + Peer 2-->>Peer A: 2. 200 OK (w. buffermap) + Peer 2->>Peer A: 3. BROADCAST_DATA + Peer A->>Peer 1: 4. BROADCAST_DATA + Peer 1->>Peer 2: BROADCAST_DATA + +``` + +Sequence diagram illustrating the message flow for data recovery between Peer A, Peer 1, and Peer 2. Peer A detects the leave of Peer 1 and sends a SET\_PRIMARY request to Peer 2. Peer 2 responds with a 200 OK. Peer 2 then sends a BROADCAST\_DATA request to Peer A, which in turn sends a BROADCAST\_DATA request to Peer 1. Peer 1 sends a BROADCAST\_DATA request to Peer 2. Callouts indicate Peer 1 is the 'Primary peer' and Peer 2 is a 'Candidate peer', with 'w. buffermap' (with buffermap) being included in the messages. + +**Figure 8-5 – Message flow for data recovery** + +- ① Peer A sends a SET\_PRIMARY request message to its outgoing candidate connection that is connected to peer 2. In this case, the peer embeds its buffermap in this message. +- ② If the corresponding peer 2 has enough resources, it responds with success (200). On sending the response message, peer 2 also embeds its buffermap. +- ③ Through step 2, peer 2 figures out what data packet needs to be pushed to peer A. Peer 2 sends a BROADCAST\_DATA request message to peer A for pushing data packets that peer A does not have. On receiving the BROADCAST\_DATA request message, peer A immediately sends it to its other primary connections. +- ④ On receiving a 200 response to the SET-PRIMARY request message from peer 2, peer 1 also sends data packets to peer 2 using a BROADCAST\_DATA request message. On receiving the BROADCAST\_DATA request message, peer 2 immediately sends it to its other primary connections. + +### 8.2.5 Scanning of tree + +This clause describes a case where a peer participating in an overlay network wants to obtain information about peers in a primary connection relationship with itself. Peer A sends a SCAN\_TREE request message to the peer in the primary connection relationship. The peer receiving the SCAN\_TREE request message sends a modified version of the SCAN\_TREE request message to other peers. Information on peers connected through the primary connection can be obtained through the *path* field of the 200 response message transmitted from the leaf node. + +Figure 8-6 shows the procedure for peer A to obtain information about peers in a primary connection relationship. It is assumed that peer A has a primary connection with peer 2, peer 2 with peers 1 and 3, and peer 1 with peer 4. + +![Sequence diagram showing message flow for network scanning between Peer A and Peers 1-4. The diagram includes a 'Scan Tree' icon on the left and message exchanges labeled 1 through 10. Callouts show the 'w.via' and 'path' fields in the messages.](7ae836e598020d937ed1478c2ef13025_img.jpg) + +The sequence diagram illustrates the message flow for network scanning. The participants are Peer A, Peer 1, Peer 2, Peer 3, and Peer 4. The process begins with Peer A sending a SCAN\_TREE request to Peer 2. Peer 2 responds with a 100 Trying message. Peer 2 then sends a revised SCAN\_TREE request to Peer 3, which includes the path [peer3]. Peer 3 responds with a 200 OK message. Peer 2 then sends a revised SCAN\_TREE request to Peer 1, which includes the path [peer3, peer2]. Peer 1 responds with a 200 OK message. Peer 2 then sends a revised SCAN\_TREE request to Peer 4, which includes the path [peer4, peer1]. Peer 4 responds with a 200 OK message. Peer 2 then sends a revised SCAN\_TREE request to Peer 1, which includes the path [peer4, peer1, peer2]. Peer 1 responds with a 200 OK message. The diagram also includes a 'Scan Tree' icon on the left, showing a cloud with nodes 1, 2, 3, and 4, and a dashed arrow pointing to Peer A. + +``` + +sequenceDiagram + participant Peer A + participant Peer 1 + participant Peer 2 + participant Peer 3 + participant Peer 4 + + Note left of Peer A: Scan Tree + Peer A->>Peer 2: 1. SCAN_TREE + Peer 2-->>Peer A: 2. 100 Trying + Peer 2->>Peer 3: 3. SCAN_TREE + Note right of Peer 3: w.via = [peer2, peerA] +path = [peer3] + Peer 3-->>Peer 2: 4. 200 OK + Peer 2->>Peer 1: 5. 200 OK + Note right of Peer 1: w.via = [peerA] +path = [peer3, peer2] + Peer 2->>Peer 1: 6. SCAN_TREE + Note right of Peer 1: w.via = [peer2, peerA] + Peer 1-->>Peer 2: 100 Trying + Peer 2->>Peer 4: 7. SCAN_TREE + Note right of Peer 4: w.via = [peer1, peer2, peerA] +path = [peer4] + Peer 4-->>Peer 2: 8. 200 OK + Peer 2->>Peer 1: 9. 200 OK + Note right of Peer 1: w.via = [peer2, peerA] +path = [peer4, peer1] + Peer 2->>Peer 1: 10. 200 OK + Note right of Peer 1: w.via = [peerA] +path = [peer4, peer1, peer2] + +``` + +Q.4102(22) + +Sequence diagram showing message flow for network scanning between Peer A and Peers 1-4. The diagram includes a 'Scan Tree' icon on the left and message exchanges labeled 1 through 10. Callouts show the 'w.via' and 'path' fields in the messages. + +**Figure 8-6 – Message flow for network scanning** + +- ① Requesting peer A generates and sends a SCAN\_TREE request message to peer 2. +At this time, a random digit number is added in the *CSEQ* field and the peer information (peer-id, address) on the requesting peer is added in the *via* field within the SCAN\_TREE request message. +- ② Since peer 2 is an intermediate node of tree, it sends a 100 response message to the requesting peer A. +- ③ Since peer 2 is an intermediate node of tree, it also sends a revised version of the SCAN\_TREE request message to peer 3 and peer 1 with a primary connection relationship (except the requesting peer for loop prevention). + +At this time, the new SCAN\_TREE request message includes peer 2's information in the *via* field. + +- ④ Since peer 3 is a leaf node of tree, peer 3 sends a 200 response message to peer 2. + +At this time, peer information (peer-id and address) on peer 3 is added in the *path* field within the 200 response message. *Path* field is a list of peer information. Information on peer 3 is added at the end of the *Path* field. + +The destination of the 200 response message is the origin of the SCAN\_TREE request message which is listed at the beginning of the *via* field within SCAN\_TREE. + +- ⑤ Peer 2, receives a 200 response message from peer 3, sends the 200 response message to peer A. + +Whenever a peer receives a response message, it checks whether its information is at the end of *via* field in the received response message. If the information is at the end of the *via* field, it indicates that the peer received as the response message is the origin of the SCAN\_TREE request message. Otherwise, the peer is an intermediate node in the overlay network. + +Since peer 2 is the intermediate requesting peer (i.e., matching), peer 2 moves its information at the beginning of *via* field within the received 200 response to the end of *path* field within the newly generated 200 response, and then transfers the newly generated 200 response to the peer at the beginning of the *via* field, which is peer A in Figure 8-6. + +- ⑥ Since peer 1, which is the received SCAN\_TREE request message from peer 2, is an intermediate node of tree, peer 1 sends a 100 response message to the requesting peer 2. +- ⑦ Since peer 1 is an intermediate node of tree, it transfers the SCAN\_TREE request message to peer 4. +- ⑧ Since peer 4 is a leaf node of tree, peer 4 sends a 200 response message to peer 1. +- ⑨ Peer 1, after receiving a 200 response message from peer 4, forwards the 200 response message to peer 2. +- ⑩ Peer 2, also sends the 200 response message to peer A. Peer A, who received the 200 response message performs the internal processing to express the relationship of peers constituting the tree. + +Peer A can identify the composition and order of the peers in the branch that make up the tree. The order can be determined from a listed set of peer information contained in a *path* field of a 200 response. + +## 8.3 Leaving phase + +This clause describes the case when a peer needs to leave a participating overlay network. Peer A, when leaving, sends a RELEASE\_PEER request message to peers in the primary connection relationship. Peers receiving the RELEASE\_PEER request message changes one of the candidate connections to a primary connection. In the case of a peer whose connection relationship has changed, it notifies HOMS of the changed status. + +Figure 8-7 shows the procedure for a peer A to leave a participating overlay network. It is assumed that peer A has a primary connection to peer 1 and peer 2. + +![Sequence diagram showing the message flow for leaving an overlay network. The participants are Peer A, HOMS, Peer 1, and Peer 2. Peer A sends RELEASE_PEER messages to Peer 1 and Peer 2, receiving 200 OK responses. Peer 2 then sends a SET_PRIMARY message to Peer 1, which responds with 200 OK. Finally, Peer 2 sends a HybridOverlayReport to HOMS, which responds with 200 OK. A callout 'w. higher ticket-id' is shown for Peer 2's SET_PRIMARY message. Below the diagram, two cloud icons represent the overlay network topology before and after Peer A leaves. In the first cloud, Peer A is connected to Peers 1, 2, and 3, and Peers 1, 2, 3, and 4 form a mesh. In the second cloud, Peer A has left, and Peer 2 is now connected to Peer 1 as its primary connection.](e451401f8fa77b466f401d5fce15b26c_img.jpg) + +Sequence diagram showing the message flow for leaving an overlay network. The participants are Peer A, HOMS, Peer 1, and Peer 2. Peer A sends RELEASE\_PEER messages to Peer 1 and Peer 2, receiving 200 OK responses. Peer 2 then sends a SET\_PRIMARY message to Peer 1, which responds with 200 OK. Finally, Peer 2 sends a HybridOverlayReport to HOMS, which responds with 200 OK. A callout 'w. higher ticket-id' is shown for Peer 2's SET\_PRIMARY message. Below the diagram, two cloud icons represent the overlay network topology before and after Peer A leaves. In the first cloud, Peer A is connected to Peers 1, 2, and 3, and Peers 1, 2, 3, and 4 form a mesh. In the second cloud, Peer A has left, and Peer 2 is now connected to Peer 1 as its primary connection. + +**Figure 8-7 – Message flow for leaving an overlay network** + +- ① Peer A, when leaving a participating overlay network, sends a RELEASE\_PEER request message to peer 1 and peer 2 in the primary connection relationship. At this time, to receive a response to the RELEASE\_PEER request message, the *ack* field of the RELEASE\_PEER request message is set to TRUE. +- ② Peer 1 and peer 2 receiving the RELEASE\_PEER request message checks whether the *ack* field of the RELEASE\_PEER request message is set to TRUE. After confirming that the *ack* field value is TRUE, peer1 and peer2 send a 200 response to peer A. +- ③ Peer 1 and peer 2 receiving the RELEASE\_PEER request message changes one of the candidate connections to the primary connection. At this time, peer 2 with a higher *ticket-id* sends a SET\_PRIMARY request message to peer 1 with a lower *ticket-id*. +- ④ Peer 2 is disconnected from peer A and has a new primary connection with peer 1. Thus peer 2 notifies HOMS of the changed status through the HybridOverlayReport message specified in clause 6.3 of [ITU-T Q.4103]. + +# Bibliography + +- [b-ITU-T X.609] Recommendation ITU-T X.609 (2015), *Managed peer-to-peer (P2P) communications: Functional architecture.* +- [b-ITU-T X.609.4] Recommendation ITU-T X.609.4 (2018), *Managed P2P communications: Multimedia streaming peer protocol.* +- [b-ITU-T X.1161] Recommendation ITU-T X.1161 (2008), *Framework for secure peer-to-peer communications.* +- [b-ITU-T X.1162] Recommendation ITU-T X.1162 (2008), *Security architecture and operations for peer-to-peer networks.* +- [b-ITU-T Y.2206] Recommendation ITU-T Y.2206 (2010), *Requirements for distributed service networking capabilities.* + + + + + +## 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/Q/T-REC-Q.4162-202312-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4162-202312-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2c72849f628da5b399c11e524d19c98948491a42 --- /dev/null +++ b/marked/Q/T-REC-Q.4162-202312-I_PDF-E/raw.md @@ -0,0 +1,476 @@ + + +# Recommendation + +## **ITU-T Q.4162 (12/2023)** + +SERIES Q: Switching and signalling, and associated measurements and tests + +Protocols and signalling for Quantum key distribution networks + +## --- **Protocols for Kq-1 interfaces for quantum key distribution networks** + +![ITU logo](84a1d09fb489061482111515543b60dc_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 Q-SERIES RECOMMENDATIONS + +## **Switching and signalling, and associated measurements and tests** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS NO. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM NO. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 | +| TESTING SPECIFICATIONS | Q.3900-Q.4099 | +| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100-Q.4139 | +| PROTOCOLS AND SIGNALLING FOR COMPUTING POWER NETWORKS | Q.4140-Q.4159 | +| PROTOCOLS AND SIGNALLING FOR QUANTUM KEY DISTRIBUTION NETWORKS | Q.4160-Q.4179 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000-Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050-Q.5069 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T Q.4162 + +## Protocols for Kq-1 interfaces for quantum key distribution networks + +## Summary + +Recommendation ITU-T Q.4162 specifies protocols for Kq-1 interfaces in quantum key distribution networks. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T Q.4162 | 2023-12-14 | 11 | 11.1002/1000/15726 | + +## Keywords + +Message parameters, protocol, QKD (quantum key distribution), QKDN (QKD network), signalling procedure. + +--- + +\* 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..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Kq-1 interface ..... | 2 | +| 7 Signalling procedure..... | 3 | +| 7.1 Signalling procedure for proactive key supply mode..... | 3 | +| 7.2 Signalling procedure for key supply upon request mode ..... | 3 | +| 8 Signalling messages and parameters ..... | 3 | +| 8.1 Messages and parameters for proactive key supply mode ..... | 4 | +| 8.2 Messages and parameters for key supply upon request mode..... | 5 | +| 9 Security considerations..... | 5 | +| Appendix I – Protocol implementation using the transmission control protocol ..... | 6 | +| Appendix II – Protocol implementation for key supply upon request mode using
hypertext transfer protocol secure ..... | 8 | +| II.1 Key request message ..... | 8 | +| II.2 Response to key request message..... | 8 | +| Bibliography..... | 9 | + + + +###### Recommendation ITU-T Q.4162 + +## Protocols for Kq-1 interfaces for quantum key distribution networks + +## 1 Scope + +This Recommendation specifies protocols for Kq-1 interfaces for quantum key distribution networks (QKDNs) especially in the following areas: + +- signalling procedures; +- signalling messages and parameters; +- security considerations. + +# 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 Q.4160] Recommendation ITU-T Q.4160 (2023), *Quantum key distribution networks – Protocol framework*. + +[ITU-T X.1712] Recommendation ITU-T X.1712 (2021), *Security requirements and measures for QKD networks – Key management*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 key management** [b-ITU-T Y.3800]: All activities performed on keys during their life cycle starting from their reception from the quantum layer, storage, formatting, relay, synchronization, authentication, to supply to cryptographic application and deletion or preservation depending on the key management policy. + +**3.1.2 key manager (KM)** [b-ITU-T Y.3800]: A functional module located in a quantum key distribution (QKD) node to perform key management in the key management layer. + +**3.1.3 key relay** [b-ITU-T Y.3800]: A method to share keys between arbitrary quantum key distribution (QKD) nodes via intermediate QKD node(s). + +**3.1.4 quantum key distribution** [b-ETSI GR QKD 007]: Procedure or method for generating and distributing symmetrical cryptographic keys with information theoretical security based on quantum information theory. + +**3.1.5 quantum key distribution key** [b-ITU-T Y.3802]: A pair of symmetric random bit strings generated by a pair of quantum key distribution (QKD) modules, particularly referring to random bit strings before being resized and formatted in a key manager. + +**3.1.6 quantum key distribution link** [b-ITU-T Y.3800]: A communication link between two quantum key distribution (QKD) modules to operate the QKD. + +NOTE – A QKD link consists of a quantum channel for the transmission of quantum signals, and a classical channel used to exchange information for synchronization and key distillation. + +**3.1.7 quantum key distribution module** [b-ITU-T Y.3800]: A set of hardware and software components that implements cryptographic functions and quantum optical processes, including quantum key distribution (QKD) protocols, synchronization, distillation for key generation, and is contained within a defined cryptographic boundary. + +NOTE – A QKD module is connected to a QKD link, acting as an endpoint module in which a key is generated. These are two types of QKD modules, namely, the transmitters (QKD-Tx) and the receivers (QKD-Rx). + +**3.1.8 quantum key distribution network (QKDN)** [b-ITU-T Y.3800]: A network comprised of two or more quantum key distribution (QKD) nodes connected through QKD links. + +NOTE – A QKDN allows sharing keys between the QKD nodes by key relay when they are not directly connected by a QKD link. + +**3.1.9 quantum key distribution network controller** [b-ITU-T Y.3800]: A functional module, which is located in a quantum key distribution (QKD) network control layer to control a QKD network. + +**3.1.10 quantum key distribution node** [b-ITU-T Y.3800]: A node that contains one or more quantum key distribution (QKD) modules protected against intrusion and attacks by unauthorized parties. + +NOTE – A QKD node can contain a key manager (KM). + +## 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|------------------------------------| +| HTTPS | Hypertext Transfer Protocol Secure | +| ID | Identifier | +| KM | Key Manager | +| QKD | Quantum Key Distribution | +| QKDN | Quantum Key Distribution Network | +| Rx | Receiver | +| TCP | Transmission Control Protocol | +| TLS | Transport Layer Security | +| Tx | Transmitter | + +# 5 Conventions + +None. + +# 6 Kq-1 interface + +A Kq-1 interface is established between a KM and a QKD module. The Kq-1 interface is used for key acquisition between the key storage function in the KM and the quantum key distribution key (QKD-key) supply function in the QKD module. + +# 7 Signalling procedure + +The following two modes are specified for key supply at the Kq-1 interface. + +- 1) Proactive key supply mode: QKD module initiates the supply of QKD-keys to KM. +- 2) Key supply upon request mode: KM initiates the procedure by requesting QKD module to supply QKD-keys and QKD module supplies QKD-keys to the KM in response to the request. + +The protocol suites applied for the signalling are specified in clause 7 of [ITU-T Q.4160]. + +## 7.1 Signalling procedure for proactive key supply mode + +This procedure is initiated when the QKD-keys are generated in the QKD module. The number of QKD-keys supplied mainly depends on the key generation request from the QKDN controller. + +Figure 1 shows signalling procedures for proactive key supply mode at the Kq-1 interface. + +![Sequence diagram for proactive key supply mode](0b87abe67b21a93777287649c33e755d_img.jpg) + +``` +sequenceDiagram + participant KM + participant QKD module + Note right of QKD module: Q.4162(23) + QKD module->>KM: Key supply + KM-->>QKD module: Response to key supply +``` + +The diagram illustrates the proactive key supply mode. It features two vertical lifelines: 'KM' on the left and 'QKD module' on the right. A solid arrow labeled 'Key supply' points from the QKD module to the KM. A return arrow labeled 'Response to key supply' points from the KM back to the QKD module. The diagram is labeled 'Q.4162(23)' at the bottom right. + +Sequence diagram for proactive key supply mode + +Figure 1 – Signalling procedures for proactive key supply mode at the Kq-1 interface + +## 7.2 Signalling procedure for key supply upon request mode + +In this procedure, the KM sends a key request to the QKD module when the KM needs QKD-keys. The QKD module supplies QKD-keys to the KM in response to the request. + +Figure 2 shows signalling procedures for key supply upon request mode at the Kq-1 interface. + +![Sequence diagram for key supply upon request mode](2ba086df3506f81bae3a9b53725dcfea_img.jpg) + +``` +sequenceDiagram + participant KM + participant QKD module + Note right of QKD module: Q.4162(23) + KM->>QKD module: Key request + QKD module-->>KM: Response to key request +``` + +The diagram illustrates the key supply upon request mode. It features two vertical lifelines: 'KM' on the left and 'QKD module' on the right. A solid arrow labeled 'Key request' points from the KM to the QKD module. A return arrow labeled 'Response to key request' points from the QKD module back to the KM. The diagram is labeled 'Q.4162(23)' at the bottom right. + +Sequence diagram for key supply upon request mode + +Figure 2 – Signalling procedures for key supply upon request mode at the Kq-1 interface + +# 8 Signalling messages and parameters + +This clause specifies messages and their parameters for the Kq-1 interface. + +The M/O columns of Tables 1 to 4 relate to signalling of the parameter in columns 1; M indicates mandatory and O indicates optional. + +The messages and parameters specified in this clause are independent of a specific protocol and can have different implementations. The recommended protocol implementations are described in Appendices I and II. + +NOTE – A message parameter described in Tables 1 to 4 is not necessarily mapped to a field in the message payload and might be a part of the control parameters of a specific protocol. The data type listed in columns 3 of Tables 1 to 4 may vary with specific protocols. + +## 8.1 Messages and parameters for proactive key supply mode + +### 8.1.1 Key supply message + +A key supply message is sent from the QKD module to the KM in the same QKD node. The QKD module supplies the QKD-key with a unique QKD-key identifier (ID) to the KM. + +Table 1 lists parameters of key supply message. + +**Table 1 – Parameters of key supply message** + +| Parameter | Description | Data type | M/O | Remarks | +|------------------------|-----------------------------------------------------------------------------------|------------------|-----|---------------------------------------| +| Key | QKD-key data supplied | String | M | | +| Key ID | ID of the QKD-key supplied | String | M | | +| QKD module ID | ID of the QKD module (Alice or Bob) that supplies the QKD-key | String | O | | +| Matching QKD module ID | ID to identify the matching QKD module that constitutes the pair of Alice and Bob | String | O | | +| Key length | Length of each QKD-key supplied | Integer | O | A default value is applied if omitted | +| Generation time stamp | Time stamp of QKD-key generation at the pair of QKD modules | String | O | | +| Hash value | Hash value of the QKD-key data. | String | O | | +| Extension | Array of extension parameters | Array of objects | O | For future use | + +### 8.1.2 Response to key supply message + +A response to a key supply message is sent from the KM to the QKD module in response to the key supply. The KM notifies the results of the receipt of the QKD-keys to the QKD module. + +Table 2 lists parameters of a response to key supply message. + +**Table 2 – Parameters of response to key supply message** + +| Parameter | Description | Data type | M/O | Remarks | +|------------------------|-----------------------------------------------------------------------------------|------------------|-----|-------------------------------| +| Key ID | ID of the QKD-key received. | String | M | | +| QKD module ID | ID of the QKD module (Alice or Bob) that supplies the QKD-key | String | O | | +| Matching QKD module ID | ID to identify the matching QKD module that constitutes the pair of Alice and Bob | String | O | | +| Response | Result of the receipt of the QKD-key | String | M | Reason for success or failure | +| Extension | Array of extension parameters | Array of objects | O | For future use | + +## 8.2 Messages and parameters for key supply upon request mode + +### 8.2.1 Key request message + +A key request message is sent from the KM to the QKD module to request QKD-keys. + +Table 3 lists parameters of a key request message. + +**Table 3 – Parameters of key request message** + +| Parameter | Description | Data type | M/O | Remarks | +|----------------|----------------------------------|------------------|-----|---------------------------------------| +| Number of keys | Number of QKD-keys requested | Integer | O | A default value is applied if omitted | +| Size of key | Length of each QKD-key requested | Integer | O | A default value is applied if omitted | +| Extension | Array of extension parameters | Array of objects | O | | + +### 8.2.2 Response to key request message + +A response to a key request message is sent from the QKD module to the KM in response to the key request from the cryptographic application. The QKD module supplies the requested QKD-keys to the cryptographic application. + +Table 4 lists parameters of a response to key request message. + +**Table 4 – Parameters of response to key request message** + +| Parameter | Description | Data type | M/O | Remarks | +|---------------|---------------------------------------------|------------------|-----|---------| +| Keys | Key file consists of key data and metadata. | Array of objects | M | | +| Key | QKD-key data provided for the request | String | M | | +| Key ID | ID of the QKD-key provided | String | M | | +| Key extension | Extensions to key file | Object | O | | +| Response | Result of key supply | String | M | | +| Extension | Array of extension parameters | Array of objects | O | | + +## 9 Security considerations + +Key data and associated metadata are transferred through a Kq-1 interface. Security requirements and measures to protect them are specified in [ITU-T X.1712]. + +## Appendix I + +### Protocol implementation using the transmission control protocol + +(This appendix does not form an integral part of this Recommendation.) + +This appendix describes an implementation using the transmission control protocol (TCP) for messages and parameters that are described in clause 8. + +NOTE 1 – Some parameters are mapped to a part of the control information of the protocol instead of being mapped to a field in the data payload. + +The QKD module can connect to the KM using the TCP protocol [b-IETF RFC 9293]. The corresponding message format over the TCP is shown in Figure I.1. + +| Version | MessageID | CommandCode | Length | Payload | +|---------|-----------|-------------|--------|---------| +|---------|-----------|-------------|--------|---------| + +Q.4162(23) + +**Figure I.1 – Message format over the transmission control protocol** + +In Figure I.1: + +Version: the current version of the message format adopted, 2 bytes; + +MessageID: the unique ID of each message, 4 bytes; + +CommandCode: a unique code that denotes different command/response messages transferred at the Kq-1 interface, 2 bytes; + +Length: the length of the message payload, 2 bytes; + +Payload: the message parameters of a specific command/response message, JavaScript object notation data format [b-IETF RFC 8259]. + +NOTE 2 – The transport layer security (TLS protocol) [b-IETF RFC 5246] can be implemented with the TCP for enhanced security. + +On establishment of the connection, mutual authentication between the QKD module and the KM is performed. After mutual authentication, a command/response message can be transferred via the Kq-1 interface for key supply from the QKD module to the KM. + +NOTE 3 – When applying the TLS protocol, the QKD module can verify the validity of a certificate the KM possesses and based on that confirm the ID of the KM it is connecting to. Similarly, the KM can verify the validity of a certificate the QKD module possesses and based on that confirm the ID of the connecting QKD module. + +Table I.1 lists CommandCode vs. command/response message name. + +**Table I.1 – CommandCode vs. command/response message name** + +| CommandCode | Command/response message name | +|-------------|-------------------------------| +| 0x3101 | Key supply | +| 0x1302 | Response to key supply | +| 0x1303 | Key request | +| 0x3104 | Response to key request | + +The first two digits "13" in a CommandCode indicate that the corresponding message is sent from the KM to the QKD module; "31" indicate that the corresponding message is sent from the QKD module to the KM. + +## Appendix II + +## Protocol implementation for key supply upon request mode using hypertext transfer protocol secure + +(This appendix does not form an integral part of this Recommendation.) + +The signalling messages and parameters for key supply upon request mode specified in clause 8.2 can be implemented using hypertext transfer protocol secure (HTTPS) according to the protocol and data format of the representational state transfer-based key delivery application programming interface specified in [b-ETSI GS QKD 014]. This appendix describes the mapping of the messages and parameters specified in clause 8.2 to the corresponding data format specified in [b-ETSI GS QKD 014]. + +NOTE – In this implementation, the KM and the QKD module play the roles of secure application entity and the key management entity defined in [b-ETSI GS QKD 014], respectively. + +### II.1 Key request message + +In this implementation, the key request message specified in clause 8.2.1 corresponds to the HTTPS request of the HTTPS transaction performed as the Get Key method specified in [b-ETSI GS QKD 014]. Table II.1 lists the mapping of the key request message to the Get Key method. + +**Table II.1 – Mapping of key request message to Get Key method** + +| Parameter | M/O | Data type | Implementation in Get Key method | +|----------------|-----|------------------|---------------------------------------------------------------------------------------| +| Number of keys | O | Integer | The "number" item in the key request data format | +| Size of key | O | Integer | The "size" item in the key request data format | +| Extension | O | Array of objects | The "extension_mandatory" or "extension_optional" item in the Key request data format | + +### II.2 Response to key request message + +In this implementation, the response to key request message specified in clause 8.2.2 corresponds to the HTTPS response of the HTTPS transaction performed as the Get Key method specified in [b-ETSI GS QKD 014]. Table II.2 lists the mapping of the response to a key request message to the Get Key method. + +**Table II.2 – Mapping of response to key request message to Get Key method** + +| Parameter | M/O | Data type | Implementation in Get Key method | +|---------------|-----|------------------|---------------------------------------------------------------------| +| Keys | M | Array of objects | The "keys" item in the key container data format | +| Key | M | String | The "key" item in the key container data format | +| Key ID | M | String | The 'key_ID' item in the key container data format | +| Key extension | O | Object | The "key_ID_extension" item in the key container data format | +| Response | M | String | The status code of HTTPS transaction performed as Get Key method | +| Extension | O | Array of objects | The "key_container_extension" item in the key container data format | + +## Bibliography + +- [b-ITU-T Y.3800] Recommendation ITU-T Y.3800 (2019)/Cor.1 (04/2020), *Overview on networks supporting quantum key distribution.* +- [b-ITU-T Y.3802] Recommendation ITU-T Y.3802 (2020)/Cor.1 (04/2021), *Quantum key distribution networks – Functional architecture.* +- [b-ETSI GR QKD 007] Group Report ETSI GR QKD 007 V1.1.1 (2018), *Quantum key distribution (QKD); Vocabulary.* +- [b-ETSI GS QKD 014] Group Specification ETSI GS QKD 014 V1.1.1 (2019), *Quantum key distribution (QKD); Protocol and data format of REST-based key delivery API.* +- [b-IETF RFC 5246] IETF RFC 5246 (2008), *The transport layer security (TLS) protocol – Version 1.2.* +- [b-IETF RFC 8259] IETF RFC 8259 (2017), *The JavaScript object notation (JSON) data interchange format.* +- [b-IETF RFC 9293] IETF RFC 9293 (2022), *Transmission control protocol (TCP).* + + + + + +## 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/Q/T-REC-Q.5004-202302-I_PDF-E/raw.md b/marked/Q/T-REC-Q.5004-202302-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3162f90fed543b04432671003b3b0e668240ea69 --- /dev/null +++ b/marked/Q/T-REC-Q.5004-202302-I_PDF-E/raw.md @@ -0,0 +1,506 @@ + + +# Recommendation**ITU-T Q.5004 (02/2023)** + +SERIES Q: Switching and signalling, and associated measurements and tests + +Signalling requirements and protocols for IMT-2020 – +Signalling requirements and architecture of IMT-2020 + +# --- **Signalling architecture of lite IMS for IMT-2020 networks and beyond** + +![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 Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 | +| TESTING SPECIFICATIONS | Q.3900-Q.4099 | +| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100-Q.4139 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000-Q.5049 | +| Signalling requirements and architecture of IMT-2020 | Q.5000-Q.5019 | +| Protocols for IMT-2020 | Q.5020-Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050-Q.5069 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T Q.5004 + +# Signalling architecture of lite IMS for IMT-2020 networks and beyond + +## Summary + +Recommendation ITU-T Q.5004 specifies the signalling architecture of lite IMS for IMT-2020 networks and beyond, designed for the Internet protocol multimedia system (IMS) domain with high efficiency, extensibility, intelligence and high value addition characteristics. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.5004 | 2023-02-13 | 11 | 11.1002/1000/15256 | + +## Keywords + +IMS, IMT-2020 network and beyond, signalling architecture. + +--- + +\* 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/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 ..... | 1 | +| 5 | Conventions ..... | 2 | +| 6 | Reference model of lite IMS..... | 2 | +| 7 | Signalling architecture of lite IMS ..... | 3 | +| 7.1 | Unified control function..... | 4 | +| 7.2 | Service enabler function..... | 5 | +| 7.3 | Service user profile function..... | 5 | +| 7.4 | End-user function ..... | 5 | +| 7.5 | Transport control function ..... | 5 | +| 7.6 | Service and application function ..... | 5 | +| 8 | Functional entities of lite IMS ..... | 6 | +| 8.1 | Functional entities in unified control function..... | 6 | +| 8.2 | Functional entities in a service user profile function ..... | 6 | +| 8.3 | Functional entities in a service enabler function ..... | 7 | +| 9 | Reference points of lite IMS ..... | 7 | +| 9.1 | Reference point U1..... | 7 | +| 9.2 | Reference point U2..... | 7 | +| 9.3 | Reference point L1 ..... | 8 | +| 9.4 | Reference point L2 ..... | 8 | +| 9.5 | Reference point L3 ..... | 9 | +| 9.6 | Reference point L4 ..... | 9 | +| 9.7 | Reference point L5 ..... | 9 | +| 10 | Relationship between lite IMS and IMS ..... | 10 | +| 11 | Security consideration..... | 11 | +| Appendix I | – Application programming interface format..... | 12 | +| I.1 | Examples of API format ..... | 12 | + + + +# Recommendation ITU-T Q.5004 + +## Signalling architecture of lite IMS for IMT-2020 networks and beyond + +# 1 Scope + +This Recommendation presents the signalling architecture of lite IMS for IMT-2020 networks and beyond. + +Lite IMS is an evolved version of IMS with the characteristics of high efficiency, extensibility, intelligence and high value addition, designed for application in IMT-2020 networks and beyond. This Recommendation specifies the reference model, signalling architecture, function entities, reference points, relationship between lite IMS and IMS, as well as security considerations for lite IMS. + +# 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 Y.2012] Recommendation ITU-T Y.2012 (2010), *Functional requirements and architecture of next generation networks*. + +[ITU-T Y.2701] Recommendation ITU-T Y.2701 (2007), *Security requirements for NGN release 1*. + +# 3 Definitions + +### 3.1 Terms defined elsewhere + +None. + +### 3.2 Terms defined in this Recommendation + +This Recommendation defines the following term: + +**3.2.1 lite IMS:** An evolved version of an Internet protocol multimedia system with the characteristics of high efficiency, extensibility, intelligence and high value addition, designed for application in IMT-2020 networks and beyond. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-----------------------------------| +| API | Application-Programming Interface | +| DNS | Domain Name Server | +| EF | End-user Function | +| FE | Functional Entity | +| HTTP | Hypertext Transfer Protocol | + +| | | +|----------|----------------------------------------------| +| IMT-2020 | International Mobile Telecommunications-2020 | +| I-CSCF | Interrogating Call Session Control Function | +| ID | Identifier | +| IMS | Internet Protocol Multimedia System | +| IP | Internet Protocol | +| IT | Information Technology | +| NE | Network Element | +| NFS | Network Function Service | +| NRF | Network Repository Function | +| P-CSCF | Proxy Call Session Control Function | +| SAF | Service and Application Function | +| SBI | Service-based Interface | +| S-CSCF | Serving Call Session Control Function | +| SDP | Session Description Protocol | +| SEF | Service Enabler Function | +| SIP | Session Initiation Protocol | +| SUPF | Service User Profile Function | +| TCF | Transport Control Function | +| UCF | Unified Control Function | +| UE | User Equipment | + +# 5 Conventions + +None. + +# 6 Reference model of lite IMS + +Figure 6-1 depicts the reference model of lite IMS. + +![Reference model of lite IMS diagram showing layers and interfaces.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +The diagram illustrates the reference model of lite IMS. At the top is the 'Service and application layer', which contains three sub-components: 'Telecommunications services', 'IT services', and 'Third-party applications'. Below this layer are two interfaces: 'Service invoking interface' and 'Capability exposure interface', both represented by double-headed blue arrows. The next layer is the 'Service enabler layer', which contains a 'Service enabler server'. Below this is the 'Service control layer', which contains a 'Unified control node'. The 'Service enabler layer' and 'Service control layer' are collectively labeled as 'Lite IMS'. Between the 'Service control layer' and the 'Transport layer' is the 'Transport control interface', also represented by a double-headed blue arrow. At the bottom is the 'Transport layer', which is connected to a 'UE' (User Equipment) via a double-headed blue arrow. The reference number 'Q.5004(23)' is located in the bottom right corner of the diagram. + +Reference model of lite IMS diagram showing layers and interfaces. + +**Figure 6-1 – Reference model of lite IMS** + +As illustrated in Figure 6-1, lite IMS mainly includes two layers: service enabler; and service control. In the service control layer, the unified control node performs functions including registration and authentication, service routing, service triggering and Internet protocol (IP) routing control. It interacts with the transport layer via a control interface to optimize routing selection. Moreover, it provides fundamental capabilities for service control to the service enabler server. + +In the service enabler layer, the server deployed provides the service (or capabilities for it) and application provision in two different ways. The service and application can directly invoke service capabilities via the applicable interface or capabilities can be exposed to the service and application layer via a service exposure interface so as to provide more complex service by means of service composition. + +Both service-based interface (SBI) and a restful interface can be used for the implementation of the interfaces mentioned in the preceding paragraph. + +# 7 Signalling architecture of lite IMS + +Figure 7-1 depicts the signalling architecture of lite IMS. + +![Diagram of the signalling architecture of lite IMS. The diagram shows two identical vertical stacks of functions connected by horizontal and diagonal interfaces. Each stack consists of SAF, SEF, UCF, and EF functions connected vertically by L5, L3, and L1 interfaces respectively. The UCF functions in both stacks are connected by a horizontal U1 interface. The top UCF in each stack is connected to a top-level SUPF function by a diagonal L4 interface. The two SUPF functions are connected to each other by a horizontal U2 interface. Both top-level UCF functions are connected to a central TCF function by diagonal L2 interfaces. A reference label 'Q.5004(23)' is present at the bottom right of the diagram.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +Diagram of the signalling architecture of lite IMS. The diagram shows two identical vertical stacks of functions connected by horizontal and diagonal interfaces. Each stack consists of SAF, SEF, UCF, and EF functions connected vertically by L5, L3, and L1 interfaces respectively. The UCF functions in both stacks are connected by a horizontal U1 interface. The top UCF in each stack is connected to a top-level SUPF function by a diagonal L4 interface. The two SUPF functions are connected to each other by a horizontal U2 interface. Both top-level UCF functions are connected to a central TCF function by diagonal L2 interfaces. A reference label 'Q.5004(23)' is present at the bottom right of the diagram. + +**Figure 7-1 – Signalling architecture of lite IMS** + +The signalling architecture of lite IMS consists of several functions that cooperate to provide the service control and service support functions and capabilities. These functions include: + +- unified control function (UCF); +- service enabler function (SEF); +- service user profile function (SUPF); +- end-user function (EF); +- transport control function (TCF); +- service and application function (SAF). + +### 7.1 Unified control function + +A UCF includes those service control functions performed by a session border controller and a serving-, interrogating- or proxy-call session control function (S/I/P-CSCF) in the lite IMS. + +A UCF mainly performs the following functions: + +- deals with the service registration and performs authentication and authorization functions; +- interacts with the SUPF to store, update, delete and query user profiles; +- processes signalling messages from EFs and determines the corresponding signalling routing based on different policies; +- performs service triggering according to user profiles fetched from SUPF; +- controls traffic optimization of media plane through interaction with the TCF, including the release of optimization policy to TCF, and interacts with TCF for the selection of optimized media routing path; +- cooperates with SEF to guarantee service and application provision; +- supports emergency call and legal interception – detailed implementation is for further study; +- deals with the interworking between different lite IMSs or different IMSs. + +### 7.2 Service enabler function + +With the introduction of service-based technology, SEF performs functions related to not only service and application support, but also network capability exposure. The service capabilities for calls provided by an SEF focus on a minimal set. Other service capabilities, such as those that are supplementary and intelligent, can also be implemented as plug-in elements in SEF as needed. + +A SEF mainly includes the following: + +- registration, authentication, authorization and other functions at the application level; +- responsibility for the management of service and application – the interaction between an SEF and SAF may be implemented as a publish-subscribe scheme to realize a two-way flexible mechanism; +- responsibility for the management, classification, encapsulation and provision of network capabilities; +- provision of service capabilities either directly via an invoking interface or via an exposure interface for service composition. + +### 7.3 Service user profile function + +A SUPF performs user profile maintenance and management functionalities, mainly including storage, update, deletion and query of user subscription information and other related data according to the requests of a UCF. With the interaction between UCF and SUPF, the user profile can be used for the registration, authentication and authorization process. With the interaction between SEF and SUPF, the user profile can be used for the registration, authentication, authorization and other functions at the application level. + +In the user profile, a new type of user identifier (ID) may be introduced based on vertical industry requirements. Furthermore, an access control policy may be introduced in an SUPF to handle the privacy or security perspective. For example, it is prohibited to provide a user profile related to call capability in the interaction with a UCF. + +### 7.4 End-user function + +EFs, as specified in [ITU-T Y.2012], support end-user access to lite IMS. + +### 7.5 Transport control function + +As a multimedia processing unit, a TCF performs media accessing and interworking, media resources management, policy control, content and context analysis and traffic scheduling functionalities. A TCF receives: network information from the transport layer; and application bandwidth and quality of service assignment requirements from the service control layer. A TCF makes decisions regarding network resource and admission control. For example, it receives the request messages including multimedia flow and transcoding directive from a UCF via an L2 interface, then performs the transcoding action, and finally returns the transcoded multimedia flow to the UCF. It supports a unified policy database and consistent policy specifications, as well as a variety of access and core networks within a general resource control framework. Furthermore, it supports the establishment of traffic-scheduling rules based on relevant information, such as traffic localization, selection of the traffic delivery network node, network status and intelligent routing policy. + +### 7.6 Service and application function + +An SAF provides services or applications to EFs, and should meet flexible requirements from not only the public network, but also vertical industry. The interaction between an SAF and SEF is based on a loose coupling mechanism. + +The detailed functionalities of an SAF and its interface with EFs lie outside the scope of this Recommendation. + +## 8 Functional entities of lite IMS + +### 8.1 Functional entities in unified control function + +As shown in Figure 8-1, the functional entities (FEs) in a UCF mainly include the following. + +- Authentication and authorization FE: Performs the authentication and authorization functions through the interaction with an SUPF. Different authorization mechanisms are provided for different trust level or service requirements. +- Registration FE: Performs registration-related functions. For different types of user equipment (UE), the registration process can be customized. For example, taking account of low-power wide-area Internet of things devices, periodic registration may be avoided to save energy. +- Routing control FE: Interacts with a TCF for the selection of optimized routing path media accessing and interworking, media resources management. Among the selection factors, a service level agreement should be included and be one of the most important factors. +- SEF selection FE: Selects a suitable SEF based on service requirements. The selection of SEF(s) is a dynamic procedure decoupled from registration, and flexible selection policies are taken into account, including security, cost and availability. During service provision, the SEF can be re-selected with a mechanism similar to that of re-invite in the session initiation protocol (SIP) process. +- Peer interaction FE: Interacts with other UCF(s) based on a loose-coupling mechanism. + +![Diagram of Functional entities in UCF](7f17c430b9598e4d748a8041457810b3_img.jpg) + +The diagram illustrates the internal functional entities of a Unified Control Function (UCF) and its external interfaces. The UCF is represented by a large rectangular box containing five smaller boxes: 'Authentication and authorization FE', 'Registration FE', 'Routing control FE', 'SEF selection FE', and 'Peer interaction FE'. External components include 'SUPF' (Service Profile Function) on the top left, 'TCF' (Traffic Control Function) on the bottom left, 'SEF' (Service Function) on the top right, and another 'UCF' on the bottom right. Double-headed arrows indicate bidirectional interactions: SUPF with the Authentication and authorization FE; TCF with the Routing control FE; SEF with the SEF selection FE; and the bottom UCF with the Peer interaction FE. + +Diagram of Functional entities in UCF + +Figure 8-1 – Functional entities in UCF + +### 8.2 Functional entities in a service user profile function + +As shown in Figure 8-2, the FEs in an SUPF mainly include the following. + +- Authentication and authorization FE: Performs user profile maintenance and management functionalities, mainly including storage, update, deletion and query of user subscription information plus other related data according to UCF requests. On interaction between a UCF and SUPF, the user profile can be used for the registration, authentication and authorization process. +- Addressing FE: A SUPF receives an addressing request from a calling UCF to the called user, queries the UCF address of the called user based on the independent self-organizing data network, and provides the query result to the calling UCF, so that it can send the call request to the called UCF. + +![Figure 8-2: Functional entities in an SUPF. The diagram shows two SUPF blocks, SUPF A and SUPF B. SUPF A contains 'Authentication and authorization FE' and 'Addressing FE'. SUPF B contains 'Authentication and authorization FE' and 'Addressing FE'. UCF A is connected to SUPF A, and UCF B is connected to SUPF B. There is a vertical double-headed arrow between the 'Addressing FE' of SUPF A and SUPF B. The label Q.5004(23) is at the bottom right.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Figure 8-2: Functional entities in an SUPF. The diagram shows two SUPF blocks, SUPF A and SUPF B. SUPF A contains 'Authentication and authorization FE' and 'Addressing FE'. SUPF B contains 'Authentication and authorization FE' and 'Addressing FE'. UCF A is connected to SUPF A, and UCF B is connected to SUPF B. There is a vertical double-headed arrow between the 'Addressing FE' of SUPF A and SUPF B. The label Q.5004(23) is at the bottom right. + +**Figure 8-2 – Functional entities in an SUPF** + +### 8.3 Functional entities in a service enabler function + +As shown in Figure 8-3, the FEs in an SEF mainly include the following. + +- SAF coordination FE: SAF informs its interested users and call events through the subscription mechanism. SEF provides an application-programming interface (API) for an SAF to collect and execute SAF call instructions, and cooperate with SAF to execute various new services. +- SIP signalling processing FE: an SEF receives the SIP signalling sent by the UCF and converts it into the corresponding call event; it also receives call instructions sent by the SAF and converts them into the corresponding SIP signalling. + +![Figure 8-3: Functional entities in an SEF. The diagram shows a central SEF block containing 'SIP signalling processing FE' and 'SAF coordination FE'. UCF is connected to the left side of the SEF, and SAF is connected to the right side. The label Q.5004(23) is at the bottom right.](410562339ce067fdc6fa41940c118658_img.jpg) + +Figure 8-3: Functional entities in an SEF. The diagram shows a central SEF block containing 'SIP signalling processing FE' and 'SAF coordination FE'. UCF is connected to the left side of the SEF, and SAF is connected to the right side. The label Q.5004(23) is at the bottom right. + +**Figure 8-3 – Functional entities in an SEF** + +## 9 Reference points of lite IMS + +### 9.1 Reference point U1 + +Reference point U1, for which SIP or hypertext transfer protocol (HTTP) can be used, exists between UCFs. + +As different vertical requirements are involved in service provision, different types of UCF(s) may exist. In order to realize interworking of different types of UCF(s), the following basic information is specified, but the transmission information between UCF(s) is not limited to the following contents: + +- information related to call participants: such as caller ID or called party ID, similar to the "from", "to" header fields in SIP; +- information about media intercommunication: such as the address of the called and called media, codec, similar to a session description protocol (SDP); +- call event information: such as call ringing, off-hook, release, similar to 18x, 200 of SIP. + +When the calling party and called party register on the same UCF, the call can be terminated within this UCF. In this case, information transmission on the U1 interface is not required. + +### 9.2 Reference point U2 + +Reference point U2 exists between different SUPFs that make up one independent, self-organized data network. + +Each SUPF has a unique domain name; and the self-organizing SUPF network is connected through a domain name server (DNS) protocol. + +The basic query flow shown in Figure 9-1 is used to interpret this reference point. + +Steps 1-8: During call establishment, the calling SUPF carries the called domain name and queries the IP address corresponding to the called SUPF with the DNS. + +Steps 9-10: A basic function of U2 is to address the UCF of the called user based on the DNS query results (the IP address corresponding to the called SUPF). The calling SUPF carries the called number and queries the called SUPF for the corresponding UCF address. + +For a specific user, the SUPF that accommodates its user data store is unique and does not change. However, the same user can register for different UCFs at different times, and the same SUPF can serve multiple different UCFs. Therefore, the calling SUPF must carry the number of the called user and query the called SUPF for the UCF registered by the called user. + +![Diagram illustrating the basic query flow for a call establishment. The diagram shows a DNS network containing three DNS servers: .com server, .y.a.com server, and .v.b.com server. A calling SUPF (x.y.a.com) sends a query (1) to the .y.a.com server. The .y.a.com server then queries the .com server (2), which queries the .b.com server (3), which queries the .v.b.com server (4). The .v.b.com server returns the result (5) to the .b.com server, which returns it (6) to the .com server, which returns it (7) to the .y.a.com server, which returns it (8) to the calling SUPF. The calling SUPF then sends a query (9) to the called SUPF (u.v.b.com), which returns the result (10) to the calling SUPF. The diagram also shows several EF (Edge Function) nodes connected to the SUPFs: A, B, C to x.y.a.com and D, E, F to u.v.b.com. A legend identifies the symbols for DNS server, SUPF, and EF. The reference number Q.5004(23) is shown in the bottom right.](a26e142d3df5bef41a84a9dd099d7825_img.jpg) + +Legend: + +- DNS server (server icon) +- SUPF (yellow circle) +- EF (red diamond) + +Q.5004(23) + +Diagram illustrating the basic query flow for a call establishment. The diagram shows a DNS network containing three DNS servers: .com server, .y.a.com server, and .v.b.com server. A calling SUPF (x.y.a.com) sends a query (1) to the .y.a.com server. The .y.a.com server then queries the .com server (2), which queries the .b.com server (3), which queries the .v.b.com server (4). The .v.b.com server returns the result (5) to the .b.com server, which returns it (6) to the .com server, which returns it (7) to the .y.a.com server, which returns it (8) to the calling SUPF. The calling SUPF then sends a query (9) to the called SUPF (u.v.b.com), which returns the result (10) to the calling SUPF. The diagram also shows several EF (Edge Function) nodes connected to the SUPFs: A, B, C to x.y.a.com and D, E, F to u.v.b.com. A legend identifies the symbols for DNS server, SUPF, and EF. The reference number Q.5004(23) is shown in the bottom right. + +Figure 9-1 – Basic query flow + +### 9.3 Reference point L1 + +Reference point L1 exists between a UCF and EF. It is mainly used for EF registration and session control. In order to maintain forward compatibility, use of an SIP is proposed for the L1 interface and related business processes. + +### 9.4 Reference point L2 + +Reference point L2 exists between a UCF and TCF. The UCF requests the TCF to provide media capability through this interface. This interface can be applied as an SBI by using a request-response mechanism: media plane capabilities of TCF are disassembled into different services, referred to as network function services (NFSs). Each NFS has the characteristics of independence and autonomy. For a media plane NFS, the network repository function (NRF) needs to be specified as responsible for the automatic management of all NFSs, including registration, discovery and status detection. After a network function is powered up, it will actively report its own NFS information to the NRF. When a UCF needs to use a certain media capability, it needs to query the NRF to obtain a specific NFS instance. + +This interface mainly realizes media access, media interworking, as well as media resource request and processing. + +**Media accessing:** each EF participating in the call has a corresponding media endpoint on the network side. This endpoint is used for the media access of this EF, including audio and video. When an EF initiates or receives a call, the UCF completes the application for a media endpoint to the TCF through the L2 interface. The TCF applies for a new endpoint for this user and returns the relevant information of the endpoint to the UCF. The UCF saves the application results and finally sends the information of this endpoint to the EF to realize the connection between the EF and this media endpoint. When the parameters of media access change, such as IP or port, encoding and decoding or code rate, the UCF updates these parameters through the L2 interface. + +**Media interworking:** Based on an L2 interface, a UCF controls interworking between media endpoints on the network side to realize the interworking with an EF corresponding to each endpoint. + +**Media resource management:** when media resources are needed during the session, such as playing tone, dual tone multi-frequency and voice conference, the UCF indicates the type of media resources, the parameters necessary for using media resources and the corresponding endpoint of using media resources through a L2 interface. After the TCF allocates the required media resources and completes media processing, it indicates the results through the L2 interface. + +### **9.5 Reference point L3** + +Reference point L3 exists between a UCF and SEF, and a SIP is suggested for L3 to ensure smooth evolution from existing IMS architecture including the following. + +When an UCF receives any signalling from an EF or other UCFs, it unconditionally forwards the message to a SEF through L3 interface, and the SEF controls the triggering of service. Call-related signalling includes EF registration signalling and various call event signalling, such as initial call event or off-hook event. + +Due to their close relationship, an SEF can also be deployed to a UCF as one of its components, which can avoid message transmission via the L3 interface and trigger service more efficiently. + +### **9.6 Reference point L4** + +Reference point L4, for which a diameter protocol or HTTPs are suggested, exists between an UCF and SUPF. + +Reference point L4 processes and delivers user profile and user profile management information to the UCF according to the storage, update and query user profile requests from it. With reference point L4, the user profile can be used for the registration, authentication and authorization process. Information related to authentication and authorization is transferred via L4. + +The SUPF receives the addressing request from the calling UCF to the called user through the L4 interface, completes the query of the UCF address of the called user based on the independent self-organizing data network, and provides the query result to the UCF through the L4 interface, so that the calling UCF can send the call request to the called UCF. + +### **9.7 Reference point L5** + +Reference point L5, for which HTTP is suggested, exists between an SEF and SAF. + +The publish or subscribe mechanism is suggested for L5 implementation and information about service capability invocation is transferred via L5. + +Based on L5, solutions to the following problems while triggering new services in the current IMS system are expected. + +- Low efficiency of third party development: SIP has high complexity, low awareness of third party developers and low efficiency of development and maintenance. +- Too long connection delay: multiple services in a single session are triggered serially and the connection delay increases significantly. + +With the increasing number of new services in the future, the negative impact of the above problems will be more prominent. + +An SEF provides an API for a SAF to call, receive and execute SAF call instructions, and cooperates with the SAF to finish various new services. + +Before the call starts, the SAF should inform its interested users and call events through the subscription mechanism. For the SAF, initial call event notification is required, and other events (such as ringing or off-hook) are optional, which can greatly reduce unnecessary message delivery and processing. + +During the call process, when an event occurs, an SEF sends the corresponding call event of a specific user to the SAF according to the subscription content of the SAF. After the SAF completes its own processing, it sends a call control instruction (not required) to the SEF according to its own business logic. The SEF executes the relevant processing according to the instruction to trigger a service. + +APIs are divided into those for call events and call control instructions. For examples, see Appendix I. + +When there are multiple SAFs, the calling order is changed from the original sequential mode to the parallel mode, as follows. + +- 1) Parallelization of call events sent by SEF: all call events, including initial call events and intra-session call events, can be sent to each SAF together instead of waiting for a SAF response message to be received before sending it to the next SAF. +- 2) Parallelization of SAF processing call events: each SAF processes call events in parallel immediately after receiving them, instead of only one SAF running at a certain time. +- 3) Execution by SEF of parallelization of instructions: after a SEF sends a call event to multiple SAFs in parallel, the SEF receives multiple call control instructions triggered by the call event from multiple SAFs, and then executes these instructions in parallel. + +The SEF judges whether the received multiple instructions are mutually exclusive, so as to determine the set of mutually exclusive instructions among the multiple call control instructions. Since multiple instructions in the set of mutually exclusive instructions cannot be executed in parallel, the SEF selects the instruction with the highest priority from the set of mutually exclusive instructions according to a certain priority order. + +## 10 Relationship between lite IMS and IMS + +Lite IMS simplifies the current IMS architecture and realizes its original basic functions. Some core differences between lite IMS and IMS are summarized in Table 1. + +**Table 1 – Core differences between lite IMS and IMS** + +| Comparison item | IMS | Lite IMS | +|----------------------|------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User data node | independent home subscriber server |
  • – self-organizing user data network composed of SUPFs
  • – enables independent operation and opening
| +| Service trigger mode | serially | in parallel, has more efficient third party development efficiency and | + +**Table 1 – Core differences between lite IMS and IMS** + +| Comparison item | IMS | Lite IMS | +|-----------------------------------|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | accelerates the process of call establishment | +| Media management | originating and terminating separation |
  • – originating and terminating unification
  • – lower media delay and more synchronous media experience
| +| Call control network element (NE) | multiple NEs: P-CSCF, S-CSCF, I-CSCF | unified NEs, accelerates the call establishment process. | + +## **11 Security consideration** + +The security requirements for signalling architecture of lite IMS for IMT-2020 network and beyond should be aligned with the requirements specified in [ITU-T Y.2701]. No specific consideration of security mechanisms is required in this Recommendation. + +# Appendix I + +## Application programming interface format + +(This appendix does not form an integral part of this Recommendation.) + +### I.1 Examples of API format + +Table I.1 lists examples of APIs for call events and call control instructions for the interface between an SEF and SAF, with their type, description and typical operation. + +**Table I.1 – Examples of APIs for call events and call control instructions** + +| Type | Description | Typical operation | +|------------------------------|----------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Call event API | SEF informs SAF of various events during an SAF decision-making session | Subscribe: subscribe
Unsubscribe: unsubscribe
Initcall: initial call notification
Ring: ring notification
Answer: off-hook notification
Release: release notification | +| Call control instruction API | After SAF makes a decision, it sends the instructions for execution by SEF, which acts accordingly | Callnewuser: call a new user
Releaseuser: release the user
Playvoice: play voice to user
SDP action: add, modify, or delete an SDP
Para action: add, modify or delete call parameters | + + + +## 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/Q/T-REC-Q.5029-202406-I_PDF-E/raw.md b/marked/Q/T-REC-Q.5029-202406-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..528c904d2aa7e2ae224c91882c48b5d96fd0ec5f --- /dev/null +++ b/marked/Q/T-REC-Q.5029-202406-I_PDF-E/raw.md @@ -0,0 +1,501 @@ + + +# Recommendation **ITU-T Q.5029 (06/2024)** + +SERIES Q: Switching and signalling, and associated measurements and tests + +Signalling requirements and protocols for IMT-2020 – +Protocols for IMT-2020 + +--- + +## **Data management interfaces in digital twin smart aquaculture system with intelligent edge computing** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features the letters "ITU" in a bold, blue, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. + +ITU logo + +## ITU-T Q-SERIES RECOMMENDATIONS + +# **Switching and signalling, and associated measurements and tests** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS NO. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM NO. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 | +| TESTING SPECIFICATIONS | Q.3900-Q.4099 | +| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100-Q.4139 | +| PROTOCOLS AND SIGNALLING FOR COMPUTING POWER NETWORKS | Q.4140-Q.4159 | +| PROTOCOLS AND SIGNALLING FOR QUANTUM KEY DISTRIBUTION NETWORKS | Q.4160-Q.4179 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000-Q.5049 | +| Signalling requirements and architecture of IMT-2020 | Q.5000-Q.5019 | +| Protocols for IMT-2020 | Q.5020-Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050-Q.5069 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T Q.5029 + +# Data management interfaces in digital twin smart aquaculture system with intelligent edge computing + +## Summary + +Recommendation ITU-T Q.5029 defines data management interfaces for intelligent edge computing-based digital twin smart aquaculture service. The data management interface includes data resources and interfaces for data processing. Data resources can be used to decide what data are for. A lot of data are needed to check environment and fish growth status. The interfaces for data processing define web-based application programming interfaces (APIs), including data creation, retrieving, update and deletion. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T Q.5029 | 2024-06-29 | 11 | 11.1002/1000/15979 | + +## Keywords + +Aquaculture, data management, digital twin, edge + +--- + +\* 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 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 ..... | 5 | +| 2 References..... | 5 | +| 3 Definitions ..... | 5 | +| 4 Abbreviations and acronyms ..... | 5 | +| 5 Conventions ..... | 6 | +| 6 Overview ..... | 6 | +| 7 Data management interfaces for IEC-based digital twin smart aquaculture system .... | 8 | +| 7.1 Interfaces for network functions..... | 8 | +| 7.2 Data resources ..... | 9 | +| 7.3 Interfaces for data processing..... | 13 | +| Bibliography..... | 18 | + + + +###### Recommendation ITU-T Q.5029 + +## Data management interfaces in digital twin smart aquaculture system with intelligent edge computing + +# 1 Scope + +This Recommendation addresses data management interfaces for intelligent edge computing (IEC)-based digital twin smart aquaculture service, including the following: + +- overview of IEC-based digital twin smart aquaculture system; +- data management interfaces for IEC-based digital twin smart aquaculture 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 Q.5001] Recommendation ITU-T Q.5001 (2018), *Signalling requirements and architecture of intelligent edge computing*. + +[IETF RFC 7159] IETF RFC 7159 (2014), *The JavaScript Object Notation (JSON) Data Interchange Format*. + +[IETF RFC 7231] IETF RFC 7231 (2014), *Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content*. + +# 3 Definitions + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----------------|------------------------------------------| +| AI | Artificial Intelligence | +| API | Application Programming Interface | +| CO 2 | Carbon dioxide | +| DO | Dissolved Oxygen | +| GRU | Gated Recurrent Unit | +| ICT | Information and Communication Technology | +| IEC | Intelligent Edge Computing | +| IoT | Internet of Things | +| JSON | JavaScript Object Notation | +| LSTM | Long Short-Term Memory | +| mV | millivolts | + +| | | +|------|---------------------------------| +| ORP | Oxidation Reduction Potential | +| pH | Potential of Hydrogen | +| REST | REpresentational State Transfer | +| TE | Terminal Entity | + +# 5 Conventions + +Resource elements in clause 7.2 and fields of message under clause 7.3 are encoded in JavaScript object notation (JSON) [IETF RFC 7159], and the grammar used in representing objects defined in this Recommendation is as follows: + +- "STRING" and "NUMBER" types are used to indicate string and number respectively; +- An array of collective values are enclosed in brackets "[ ]" with value separated by commas ", "; +- Selective options are separated by a vertical bar " | "; +- "MIN" means minimum value, while "MAX" means maximum value. + +# 6 Overview + +A digital twin is a digital representation fit to the purpose and roles of an observable object through synchronization between the object and its digital representation. An observable object can move across multiple industrial domains such as aquaculture, manufacturing, medical, farm, and city, and have different roles depending on the domain. Configuring an observable object into a digital twin involves creating digital twins with different characteristics, depending on their purposes and roles for each domain. A procedure for representing an observable object, also known as a physical asset or an object of interest, as a digital twin in a domain is as follows: + +- defining a purpose for expressing the observable object as a digital twin in the domain; +- organizing data based on the roles of the observable object in the domain; +- configuring the observable object into the digital twin based on the data for the purpose; +- interworking with a digital twin reflecting each of the other roles of the observable object; +- synchronizing the observable object and the digital twin; +- maintaining the digital twin for observable object between the plurality of domains in the same state. + +Digital twins, which started in manufacturing, are being used in all industries due to their operational efficiency and cost-saving effects, and are also beginning to be applied to land-based aquaculture. Land-based aquaculture is a fishery that uses seawater in an artificially built facility on land to raise aquatic life. This is divided into a method of farming in a tank and a method of farming in a cage. Land-based aquaculture uses water from the sea, and then discharges the water again. The used water discharged back into the ocean contains various residues and suspended solids. In this document, the scope of application is limited to land-based aquaculture. The smart aquaculture system in land-based aquaculture aims to increase the productivity of aquaculture products, while promoting environmentally friendly aquaculture technology by applying the Internet of Things (IoT), information and communication technology (ICT), big data, artificial intelligence (AI) technologies, etc., to the conventional land-based aquaculture system. Figure 6-1 illustrates the concept of digital twin smart aquaculture system. In order for such a smart aquaculture system to become a digital twin and provide services, an interface standard is required to transmit and receive big data and manage the data between the physical aquafarm and the virtual aquafarm. + +To provide smart aquaculture services using digital twins, data from (1) a physical aquaculture system (e.g., monitoring data and operation data), (2) a virtual aquaculture system (e.g., simulation + +configuration, input/output and analytics), (3) synchronization between two aquaculture systems and (4) smart aquaculture services should be considered, as shown in Figure 6-1. + +![Concept of digital twin smart aquaculture system diagram](acfc53eca625d62b38aa2563efa95c3e_img.jpg) + +The diagram illustrates the concept of a digital twin smart aquaculture system. It features a central 'Service cloud' represented by a stack of three blue cylinders. Above this cloud is a blue cloud icon containing a server rack and the text 'Aquafarm management system', with an arrow pointing to a computer monitor icon. Below the central cloud is a label 'Edge computing module (Sensor and actuator units)'. To the left, labeled '“REAL WORLD”', is a physical aquaculture system with a large circular tank containing a fish, connected to a water filtration and aeration unit. To the right, labeled '“DIGITAL WORLD”', is a virtual representation of the same system, shown in a lighter, semi-transparent style. Blue double-headed arrows connect the physical system to the central cloud and the central cloud to the virtual system, indicating bidirectional data flow. The text 'Q.5029(24)' is located in the bottom right corner of the diagram area. + +Concept of digital twin smart aquaculture system diagram + +**Figure 6-1 – Concept of digital twin smart aquaculture system** + +The IEC architecture defines a well-defined cloud infrastructure as a signal delivery architecture and reference point. Figure 6-2 shows the concept of a physical aquafarm and a virtual aquafarm based on IEC. This Recommendation defines a data management interface for IEC-based smart aquaculture systems. + +![Figure 6-2: Concept of IEC-based digital twin smart aquaculture system. The diagram shows a hierarchical structure. At the top is the 'Aquaculture service cloud'. Below it are multiple 'Edge computing module' blocks (labeled #1, #..., #n). Each module contains a 'Physical aquafarm' and a 'Virtual aquafarm' connected by a 'Synchronization between physical and virtual aquafarms' interface. The 'Physical aquafarm' contains 'Sensor units' (Water temperature, Dissolved oxygen, pH, etc.) and 'Actuator units' (Water pump, Heat pump, Oxygen injector, etc.). The 'Virtual aquafarm' contains 'Smart aquaculture services' and 'Sensor and actuator'. All modules are connected to the cloud via double-headed arrows. A small text 'Q.5029(24)' is in the bottom right corner.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +Figure 6-2: Concept of IEC-based digital twin smart aquaculture system. The diagram shows a hierarchical structure. At the top is the 'Aquaculture service cloud'. Below it are multiple 'Edge computing module' blocks (labeled #1, #..., #n). Each module contains a 'Physical aquafarm' and a 'Virtual aquafarm' connected by a 'Synchronization between physical and virtual aquafarms' interface. The 'Physical aquafarm' contains 'Sensor units' (Water temperature, Dissolved oxygen, pH, etc.) and 'Actuator units' (Water pump, Heat pump, Oxygen injector, etc.). The 'Virtual aquafarm' contains 'Smart aquaculture services' and 'Sensor and actuator'. All modules are connected to the cloud via double-headed arrows. A small text 'Q.5029(24)' is in the bottom right corner. + +**Figure 6-2 – Concept of IEC-based digital twin smart aquaculture system** + +As the well-defined edge-cloud infrastructure, IEC architecture [ITU-T Q.5001] defines signalling architecture and reference points. Figure 6-3 highlights the reference points which this Recommendation uses. This Recommendation defines data management application programming interfaces (APIs) for IEC-based digital twin smart aquaculture. + +![Figure 6-3: Reference points of IEC [ITU-T Q.5001] used in this Recommendation. The diagram shows the 'Intelligent edge computing' architecture. It includes a 'Terminal entity (TE)' on the left, an 'Edge networking entity', an 'Intelligent computing entity', an 'Edge gateway entity', 'Big data analytics in the cloud', and an 'IEC' entity on the right. The 'Edge networking entity' contains 'TE control and management functions' and 'Data collection functions'. The 'Intelligent computing entity' contains 'Data analysis functions', 'Data aggregation functions', 'Edge analytic model functions', and 'Storage management functions'. The 'Edge gateway entity' contains 'Forwarding management functions'. Reference points are labeled: Cb, Da, Ca, Db, Ub, Ua, Df, Dc, Dd, Dg, Dh, Di. A legend at the bottom defines Dx as Identifier for data flow reference points, Cx as Identifier for control flow reference points, and Ux as Identifier for model update reference points. A small text 'Q.5029(24)' is in the bottom right corner.](e6df2733626a85205c1db682e6259c46_img.jpg) + +Figure 6-3: Reference points of IEC [ITU-T Q.5001] used in this Recommendation. The diagram shows the 'Intelligent edge computing' architecture. It includes a 'Terminal entity (TE)' on the left, an 'Edge networking entity', an 'Intelligent computing entity', an 'Edge gateway entity', 'Big data analytics in the cloud', and an 'IEC' entity on the right. The 'Edge networking entity' contains 'TE control and management functions' and 'Data collection functions'. The 'Intelligent computing entity' contains 'Data analysis functions', 'Data aggregation functions', 'Edge analytic model functions', and 'Storage management functions'. The 'Edge gateway entity' contains 'Forwarding management functions'. Reference points are labeled: Cb, Da, Ca, Db, Ub, Ua, Df, Dc, Dd, Dg, Dh, Di. A legend at the bottom defines Dx as Identifier for data flow reference points, Cx as Identifier for control flow reference points, and Ux as Identifier for model update reference points. A small text 'Q.5029(24)' is in the bottom right corner. + +**Figure 6-3 – Reference points of IEC [ITU-T Q.5001] used in this Recommendation** + +# 7 Data management interfaces for IEC-based digital twin smart aquaculture system + +For extensibility, APIs follow representational state transfer (REST) architecture [b-REST] and payloads are encoded in JSON [IETF RFC 7159]. + +## 7.1 Interfaces for network functions + +The interfaces for network functions are conformed to [ITU-T Q.5001]. + +## 7.2 Data resources + +### 7.2.1 Environmental data of digital twins + +A digital twin-based aquafarm can be divided into environmental data collected from the actual farm and virtual data based on models. The collected environmental data are synchronized and utilized in real-time in the digital twin space, based on IEC. Model-based virtual data generates data according to the requirements of the farm based on historical and current data, which is provided to the virtual farm based on edge computing. + +#### 7.2.1.1 Water temperature + +The environmental factor that has the greatest impact on fish in aquaculture is the water environment. For fish farm operations, water temperature is the most important factor for water environment management and energy management. Table 7-1 shows the types of water temperature data and information collected in actual fish farms. + +**Table 7-1 – Water temperature data resource element** + +| Keyword | Type | Description | +|-----------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| water-temperature-value | NUMBER | water-temperature-value indicates the water temperature, measured by the water temperature sensor. | +| water-temperature-units | STRING | water-temperature-units indicates a unit of water temperature value. The unit may be represented by "C" indicating Celsius, "F" indicating Fahrenheit, and "K" indicating absolute water temperature. | +| water-temperature-range | NUMBER (MIN, MAX) | water-temperature-range indicates effective range of water temperature values. By specifying an effective range of water temperature, unnecessary data collection and transmission can be avoided. | +| water-temperature-precision | NUMBER | water-temperature-precision indicates precision of the temperature value. It can be used in conjunction with " water-temperature-range ". For example, if " water temperature-range " is (0, 10) and " water-temperature-precision " is 1, valid water temperature data can be expressed as an integer. | +| water-temperature-margin | NUMBER | water-temperature-margin indicates the error range of the water temperature value. It can be used in conjunction with " water-temperature-range ". For example, if " water-temperature-range " is (0, 10) and " water-temperature-margin " is 2, the range of valid measurements may be (-2, 12). | + +#### 7.2.1.2 Dissolved oxygen + +Dissolved oxygen (DO) is the amount of oxygen dissolved in water. It is one of the environmental factors that directly affects the production of aquaculture organisms and is an important environmental management factor for fish growth. Table 7-2 shows the types of DO data and information collected at actual fish farms. + +**Table 7-2 – DO data resource element** + +| Keyword | Type | Description | +|----------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dissolved-oxygen-value | NUMBER | dissolved-oxygen-value indicates the amount of oxygen dissolved in water as a value, and is a value measured by a DO sensor. | +| dissolved-oxygen-units | STRING | dissolved-oxygen-unit means a unit that expresses the amount of oxygen dissolved in water as a value. The unit can be expressed as mg/L. | +| dissolved-oxygen-range | NUMBER (MIN, MAX) | dissolved-oxygen-range indicates the effective range of the value of oxygen dissolved in water. By specifying a valid DO range, unnecessary data collection and transmission can be avoided. | +| dissolved-oxygen-precision | NUMBER | dissolved-oxygen-precision indicates the precision of the value of the amount of oxygen dissolved in water. This can be used in conjunction with the " dissolved-oxygen-range ". | +| dissolved-oxygen-margin | NUMBER | dissolved-oxygen-margin indicates the error range of the value of the amount of oxygen dissolved in water. This can be used in conjunction with the " dissolved-oxygen-range ". For example, if " dissolved oxygen range " is (0, 10) and " dissolved-oxygen-margin " is 2, the effective measurement range can be (-2, 12). | + +#### 7.2.1.3 Potential of hydrogen + +Potential of hydrogen (pH) is the hydrogen ion concentration, which is a logarithmic measure of how much hydrogen ions are contained in water. Aquaculture organisms are very sensitive to pH, making pH monitoring and management very important. Table 7-3 shows the types of pH data and information collected in actual fish farms. + +**Table 7-3 – pH data resource element** + +| Keyword | Type | Description | +|--------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| pH-value | NUMBER | pH-value indicates the amount of hydrogen ions present in water as a value, and is a value measured by a pH sensor. | +| pH-units | STRING | pH-units means a unit representing the amount of hydrogen ions present in water as a value. Units can be expressed as pH. | +| pH-range | NUMBER (MIN, MAX) | pH-range indicates the effective range of the amount of hydrogen ions present in water. By specifying valid pH ranges, unnecessary data collection and transmission can be avoided. | +| pH-precision | NUMBER | pH-precision indicates the precision of the value of the amount of hydrogen ions present in water. This can be used in conjunction with " pH-range ". For example, if " pH-range " is (0, 14) and " pH-precision " is 1, valid pH data can be expressed as integers. | +| pH-margin | NUMBER | pH-margin represents the error range of the value of the amount of hydrogen ions present in water. This can be used in conjunction with " pH-range ". For example, if the " pH-range " is (0, 14) and the " pH-margin " is 2, then the effective measurement range can be (-2, 16). | + +#### 7.2.1.4 Oxidation reduction potential + +Oxidation reduction potential (ORP) is a measure of a solution's ability to transfer electrons and is measured in millivolts (mV). It is the ability of water to purify or break down pollutants or waste. ORP can provide information about water quality and the extent of pollution. Table 7-4 shows the types of ORP data and information collected in real-world aquaculture. + +**Table 7-4 – ORP data resource element** + +| Keyword | Type | Description | +|---------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ORP-value | NUMBER | ORP-value is the oxidation reduction potential, which is an indicator of the degree of oxidation and reduction of metals. ORP-value is used to measure the redox reaction of wastewater. | +| ORP-units | STRING | ORP-units is the movement of electrons, which is measured in mV. | +| ORP-range | NUMBER (MIN, MAX) | ORP-range is 1000 mV to –1000 mV. Above 1100 mV is acidic and has a strong disinfectant effect; 500 to 750 mV is the level of tap water sterilized with chlorine; 400 to 500 mV is a well-purified water tank; 100 to 200 mV is natural fresh water; –50 to –200 mV is the level of nitric acid reduction; –200 to –500 mV is the level at which sulfuric acid reduction begins; and below –500 mV is the level of methane production due to carbonic oxidation of hydrogen. | +| ORP-precision | NUMBER | ORP-precision indicates the precision of the ORP value in the water. This can be used in conjunction with " ORP-range ". For example, if " ORP-range " is (–1000, 1000) and " ORP-precision " is 1, valid ORP data can be expressed as integers. | +| ORP-margin | NUMBER | ORP-margin represents the error range of the value of the amount of ORP in the water. This can be used in conjunction with " ORP-range ". For example, if the " ORP-range " is (–1000, 1000) and the " ORP-margin " is 2, then the effective measurement range can be (–1002, 1002). | + +### 7.2.2 Data generated by the model for digital twins + +In a digital twin-based aqua farm, model-based data can be utilized in a digital twin, based on edge computing to generate predictive data for areas where data are missing or difficult to measure, or to generate virtual sensor data to obtain information that cannot be measured by sensors in real time. For example, DO levels and water temperature have the greatest impact on fish growth, so these environmental data can be modelled, secured, and utilized in digital twins. In addition, growth prediction to predict and manage the growth of farmed fish can also be used to collect and utilize data using AI models. There are various types of AI models such as long short-term memory (LSTM), gated recurrent unit (GRU), transformer, and random forest; the appropriate model can be selected according to the development environment and purpose of utilization, and the trained model used for digital twins. Table 7-5 provides example information on models and generated data that can be utilized for edge computing-based digital twins. + +**Table 7-5 – AI model for aquafarm of edge-computing digital twins** + +| Data types | Available models | Description | +|------------------------------|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DO prediction | LSTM, GRU, etc. | It is a model that predicts future changes in DO based on environmental data, feeding, and weight data measured over a period of time. Environmental variables include DO, water temperature, pH, and carbon dioxide (CO 2 ). | +| Water temperature prediction | Transformer, LSTM, random forest, etc. | It is a model that predicts future changes in water temperature based on environmental data measured over a period. Environmental variables include dissolved oxygen, fish farm environmental data, pH, and CO 2 . | + +#### 7.2.2.1 DO prediction model for digital twins + +DO levels are an important factor in the growth of aquaculture organisms and water quality management. In the edge computing-based digital twin environment, DO prediction models can be used to generate and use DO data by utilizing the data collected. The specification and type of input data required for training are highly flexible but, in terms of data utilization, the data generated by the prediction model follows the DO data type and description in clause 7.2.1.2. See Table 7-6. + +**Table 7-6 – Predicted DO data resource element based on digital twin AI model** + +| Keyword | Type | Description | +|--------------------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| predicted-dissolved-oxygen-value | NUMBER | predicted-dissolved-oxygen-value indicates the amount of oxygen dissolved in water as a value, and is a value predicted by the AI model of digital twins. | +| predicted-dissolved-oxygen-units | STRING | predicted-dissolved-oxygen-units means a unit that expresses the amount of predicted oxygen dissolved in water as a value. The unit can be expressed as mg/L. | +| predicted-dissolved-oxygen-range | NUMBER (MIN, MAX) | predicted-dissolved-oxygen-range indicates the effective range of the value of predicted oxygen dissolved in water. By specifying a valid DO range, unnecessary data collection and transmission can be avoided. | +| predicted-dissolved-oxygen-precision | NUMBER | predicted-dissolved-oxygen-precision indicates the precision of the value of the amount of predicted oxygen dissolved in water. This can be used in conjunction with the " predicted-dissolved-oxygen-range ". | +| predicted-dissolved-oxygen-margin | NUMBER | predicted-dissolved-oxygen-margin indicates the error range of the value of the amount of predicted oxygen dissolved in water. This can be used in conjunction with the " predicted-dissolved-oxygen-range ". For example, if " predicted-dissolved-oxygen-range " is (0, 10) and " predicted-dissolved-oxygen-margin " is 2, the effective measurement range can be (-2, 12). | + +#### 7.2.2.2 Water temperature prediction model for digital twins + +As the number of high temperature periods increases due to persistent heat waves and extreme weather events, the water temperature can change the amount of DO in the water, which affects the respiration of fish and shellfish, resulting in large-scale mortality. To this end, models that predict changes and trends in water temperature can be utilized in edge computing digital twin aquaculture. The specification and type of input data required for training is highly flexible but, in terms of data + +utilization, the data generated by the prediction model follows the water temperature data type and description in clause 7.2.1.1. See Table 7-7. + +**Table 7-7 – Predicted water temperature data resource element based on the digital twin AI model** + +| Keyword | Type | Description | +|---------------------------------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| predicted-water-temperature-value | NUMBER | predicted-water-temperature-value indicates the water temperature, predicted by the AI model of digital twins. | +| predicted-water-temperature-units | STRING | predicted-water-temperature-units indicates a unit of predicted water temperature value. The unit may be represented by "C" indicating Celsius, "F" indicating Fahrenheit, and "K" indicating absolute water temperature. | +| predicted-water-temperature-range | NUMBER (MIN, MAX) | predicted-water-temperature-range indicates effective range of predicted water temperature values. By specifying an effective range of water temperature, unnecessary data collection and transmission can be avoided. | +| predicted-water-temperature-precision | NUMBER | predicted-water-temperature-precision indicates precision of the temperature value. It can be used in conjunction with " predicted-water-temperature-range ". For example, if " predicted-water-temperature-range " is (0, 10) and " predicted-water-temperature-precision " is 1, valid predicted water temperature data can be expressed as an integer. | +| predicted-water-temperature-margin | NUMBER | predicted-water-temperature-margin indicates the error range of predicted water temperature value. It can be used in conjunction with " predicted-water-temperature-range ". For example, if " predicted-water-temperature-range " is (0, 10) and " predicted-water-temperature-margin " is 2, the range of valid measurements may be (-2, 12). | + +## 7.3 Interfaces for data processing + +This clause describes the APIs for data processing, including creating, retrieving, updating, and deleting data to be used in the reference point Da specified in [ITU-T Q.5001]. In the body of HTTP request/response message, the following notation is used for representing the requirements on the specific parameter: + +- m: mandatory; +- o: optional; +- c: conditional, meaning that the use of the parameter depends on the context of the message usages. + +### 7.3.1 DataCreation + +DataCreation is used for posting data at the edge networking entity. Table 7-8 describes the syntax of the request message. + +**Table 7-8 – Request message syntax for DataCreation** + +| | | +|--------------------|--------------------------------------------------------------------------------------------------------------------------| +| HTTP Method | POST | +| HTTP URI | http://[address of edge networking entity]:[port]/[digital twin smart aquaculture service]/[version]/[type of event]/c | +| BODY | "timestamp": NUMBER,
"device-id": STRING,
"data-id": NUMBER,
"data-type": STRING,
"data-value": DATA ELEMENT | + +- *timestamp* field indicates the time when the value is measured. The time when the value measured by the device reaches the system is mainly utilized. +- *device-id* field indicates identifiers of the sensor device that measures the value. Through the device identifier, it is possible to check with which sensor the value was measured. That means the location of the value can be estimated. +- *data-id* field indicates identifiers which are identifying each measurement value. +- *data-type* field indicates what kinds of data, which are defined in clause 7.2. +- *data-value* field indicates data element, which is defined in clauses 7.2.1 to 7.2.2, corresponding to data type. + +Table 7-9 describes the syntax of the response for DataCreation. + +**Table 7-9 – Response message syntax for DataCreation** + +| | | +|---------------------------|-----------------| +| HTTP Response code | rsp_code | +| BODY | None | + +- *rsp\_code* indicates the result of the request. If successful, this is 200, and it uses appropriate HTTP response code if it fails. + +### 7.3.2 DataRetrieval + +DataRetrieval is used for retrieving data at the edge networking entity. Table 7-10 describes the syntax of the request message for getting entire data resources. + +**Table 7-10 – Request message syntax for DataRetrieval for getting entire data resources** + +| | | +|--------------------|------------------------------------------------------------------------------------------------------------------------------------| +| HTTP Method | GET | +| HTTP URI | http://[address of edge networking entity]:[port]/[digital twin smart aquaculture service]/[version]/[type of event]/r/[data-type] | +| PARAMETERS | "data-type": STRING | + +- *data-type* field indicates what kinds of data, which are defined in clause 7.2. + +Table 7-11 describes the syntax of the request message for DataRetrieval for getting specific data resources. + +**Table 7-11 – Request message syntax for DataRetrieval for getting specific data resources** + +| | | +|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| HTTP Method | GET | +| HTTP URI | http:// [address of edge networking entity]: [port]/ [digital twin smart aquaculture service]/ [version]/ [type of event]/r/ [data-type]/ [device-id] | +| PARAMETERS | "device-id": STRING,
"data-type": STRING | + +- *device-id* field indicates identifiers of the sensor device that measures data value. Through the device identifier, it is possible to check with which sensor the data value was measured. That means the location of the data value can be estimated. +- *data-type* field indicates what kinds of data, which are defined in clause 7.2. + +Table 7-12 describes the syntax of the response for DataRetrieval. + +**Table 7-12 – Response message syntax for DataRetrieval** + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------| +| HTTP Response code | rsp_code | +| BODY | "timestamp": NUMBER,
"device-id": STRING,
"data-id": NUMBER,
"data-type": STRING,
"data-value": DATA ELEMENT | + +- *rsp\_code* indicates the result of the request. If successful, this is 200, and it uses appropriate HTTP response code if it fails. +- *timestamp* field indicates the time when the data value is measured. The time when the data value measured by the device reaches the system is mainly utilized. +- *device-id* field indicates identifiers of the sensor device that measures data value. Through the device identifier, it is possible to check with which sensor the data value was measured. That means the location of the data value can be estimated. +- *data-id* field indicates identifiers which are identifying each data value. +- *data-type* field indicates what kinds of data, which are defined in clause 7.2. +- *data-value* field indicates data element, which is defined in clauses 7.2.1 to 7.2.2, corresponding to data type. + +### 7.3.3 DataUpdate + +DataUpdate is used for updating data at the edge networking entity. Table 7-13 describes the syntax of the request message. + +NOTE – DataUpdate is only supported for configuration data, which is defined in clauses 7.2.1 to 7.2.2. + +**Table 7-13 – Request message syntax for DataUpdate** + +| | | +|--------------------|----------------------------------------------------------------------------------------------------------------------------------| +| HTTP Method | PUT | +| HTTP URI | http://[address of edge networking entity]:[port]/[digital twin smart aquaculture service]/[version]/[type of event]/u/[data-id] | +| PARAMETERS | "data-id": NUMBER | +| BODY | "timestamp": NUMBER,
"data-value": DATA ELEMENT | + +- *data-id* field indicates identifiers which are identifying each data value. +- *timestamp* field indicates the time when the data value is measured. The time when the data value measured by the device reaches the system is mainly utilized. +- *data-value* field indicates data element, which is defined in clauses 7.2.1 to 7.2.2, corresponding to data type. + +Table 7-14 describes the syntax of the response for DataUpdate. + +**Table 7-14 – Response message syntax for DataUpdate** + +| | | +|---------------------------|-----------------| +| HTTP Response code | rsp_code | +| BODY | None | + +- *rsp\_code* indicates the result of the request. If successful, this is 200, and it uses appropriate HTTP response code if it fails. + +### 7.3.4 DataDeletion + +DataDeletion is used for deleting data at the edge networking entity. Table 7-15 describes the syntax of the request message. + +**Table 7-15 – Request message syntax for DataDeletion** + +| | | +|--------------------|----------------------------------------------------------------------------------------------------------------------------------| +| HTTP Method | POST | +| HTTP URI | http://[address of edge networking entity]:[port]/[digital twin smart aquaculture service]/[version]/[type of event]/d/[data-id] | +| BODY | "data-id": NUMBER | + +- *data-id* field indicates identifiers which is identifying each data value. + +Table 7-16 describes the syntax of the response for DataDeletion. + +**Table 7-16 – Response message syntax for DataDeletion** + +| | | +|-------------------------------|-----------------| +| HTTP
Response code | rsp_code | +| BODY | None | + +- *rsp\_code* indicates the result of the request. If successful, this is 200, and it uses appropriate HTTP response code if it fails. + +# Bibliography + +[b-REST] + +Fielding, R. (2000), *Architectural Styles and the Design of Network-based Software Architectures*, Doctoral Dissertation, University of California, Irvine. + + + +## 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/Q/T-REC-Q.5034-202601-I_PDF-E/raw.md b/marked/Q/T-REC-Q.5034-202601-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..912360d810feebc2b593973b376dc779ffe70a1b --- /dev/null +++ b/marked/Q/T-REC-Q.5034-202601-I_PDF-E/raw.md @@ -0,0 +1,1353 @@ + + +# Recommendation + +## **ITU-T Q.5034 (01/2026)** + +SERIES Q: Switching and signalling, and associated measurements and tests + +Signalling requirements and protocols for IMT-2020 – +Protocols for IMT-2020 + +--- + +**Protocol for supporting integrated resource scheduling and orchestration for future networks including IMT-2020 networks** + +![ITU logo](84a1d09fb489061482111515543b60dc_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 Q-SERIES RECOMMENDATIONS + +## **Switching and signalling, and associated measurements and tests** + +| | | +|--------------------------------------------------------------------------------|----------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS NO. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM NO. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 | +| TESTING SPECIFICATIONS | Q.3900-Q.4099 | +| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100-Q.4139 | +| PROTOCOLS AND SIGNALLING FOR COMPUTING POWER NETWORKS | Q.4140-Q.4159 | +| PROTOCOLS AND SIGNALLING FOR QUANTUM KEY DISTRIBUTION NETWORKS | Q.4160-Q.4179 | +| ARTIFICIAL INTELLIGENCE-ENABLED SIGNALLING, TESTING AND MONITORING | Q.4180-Q.4279 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000-Q.5049 | +| Signalling requirements and architecture of IMT-2020 | Q.5000-Q.5019 | +| Protocols for IMT-2020 | Q.5020-Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050-Q.5069 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T Q.5034 + +## Protocol for supporting integrated resource scheduling and orchestration for future networks including IMT-2020 networks + +## Summary + +Recommendation ITU-T Q.5034 specifies a protocol for supporting integrated resource scheduling and orchestration for future networks including IMT-2020 networks. Integrated resource scheduling and orchestration can sense, analyse and measure multi-type resources including network, computing, and storage, to realize the most suitable scheduling solution for customers. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T Q.5034 | 2026-01-13 | 11 | 11.1002/1000/16696 | + +## Keywords + +Cloud management, integrated resource scheduling, network management, service exposure. + +--- + +\* 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 2026 + +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 Overview..... | 2 | +| 7 Interfaces for supporting integrated resource scheduling and orchestration ..... | 4 | +| 7.1 Northbound interfaces ..... | 4 | +| 7.2 Southbound interfaces ..... | 4 | +| 8 Signalling flow for supporting integrated resource scheduling and orchestration ..... | 5 | +| 8.1 Signalling flow of task scheduling ..... | 5 | +| 8.2 Signalling flow of service exposure for supporting integrated scheduling .... | 6 | +| 8.3 Signalling flow of southbound interfaces for supporting integrated
scheduling..... | 12 | +| 9 Message format for supporting integrated resource scheduling and orchestration ..... | 15 | +| 9.1 Task scheduling ..... | 15 | +| 9.2 Integrated scheduling service exposure..... | 16 | +| 9.3 Southbound interfaces ..... | 21 | +| Bibliography..... | 33 | + + + +# Recommendation ITU-T Q.5034 + +## Protocol for supporting integrated resource scheduling and orchestration for future networks including IMT-2020 networks + +# 1 Scope + +This Recommendation specifies a protocol for supporting integrated resource scheduling and orchestration for future network including IMT-2020 networks. This Recommendation covers the following aspects: + +- Overview of signalling architecture for supporting integrated resource scheduling and orchestration; +- Interfaces for supporting integrated resource scheduling and orchestration; +- Signalling flow for supporting integrated resource scheduling and orchestration; +- Message format for supporting integrated resource scheduling and orchestration. + +# 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 Q.5020\]](#) Recommendation ITU-T Q.5020 (2019), *Protocol requirements and procedures for network slice lifecycle management*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following term defined elsewhere: + +**3.1.1 communication resource scheduling** [b-ITU-T F.743.16]: A module that is used for dynamically scheduling communication resources. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following term: + +**3.2.1 integrated resource scheduling**: A capability of dynamically scheduling more than one type of resources considering a set of factors to satisfy the service requirements. + +NOTE – Factors include network factors (e.g., bandwidth, latency, reliability and connection type), storage factors (e.g., storage type, storage capacity and storage write/read rate), computing factors (e.g., computing type, computing capability and utilization), energy consumption factors (e.g., power usage effectiveness and energy efficiency), cost factors (e.g., monthly or yearly cost), and security factors (e.g., encrypted transmission, secure storage). + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +AI Artificial Intelligence + +| | | +|------|--------------------------------------------------| +| API | Application Programming Interface | +| CMS | Cloud Management System | +| CPU | Central Processing Unit | +| GPU | Graphics Processing Unit | +| HDD | Hard Disk Drive | +| ID | Identifier | +| IF | Interface | +| IP | Internet Protocol | +| IRSO | Integrated Resource Scheduling and Orchestration | +| ML | Machine Learning | +| NMS | Network Management System | +| NVMe | Non-Volatile Memory express | +| OS | operating system | +| QoS | Quality of Service | +| SLA | Service Level Agreement | +| SSD | Solid-State Drive | +| VLAN | Virtual Local Area Network | +| VM | Virtual Machine | + +# 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 Overview + +In the era of IMT-2020 and beyond, with the continuous enrichment of business scenarios such as interactive live broadcasting, video surveillance, cloud conferencing, smart industry and artificial intelligence (AI) applications, the requirements of large video traffic delivery guarantee, ultra-latency guarantee as well as large data storage and processing are becoming more and more common and urgent, which causes high demand of infrastructure resources. + +To meet the multi-scenario and personalized needs of customers, integrated scheduling of multi-type resources has become necessary. Integrated scheduling of multi-type resources determines the optimal scheduling strategy based on quality of service (QoS) goals, resource status and business load trends, improving scheduling efficiency and resource utilization, as well as improving customers' experience. + +[ITU-T Q.5020] specifies network slices management and only addresses network resources scheduling in IMT-2020. To address the integrated resources provision issues for the new business scenarios, enhanced interfaces and protocol aspect for supporting integrated scheduling and orchestration of multi-type resources are specified in this Recommendation. + +Figure 6-1 illustrates the general signalling architecture for supporting integrated resource scheduling and orchestration (IRSO) for future networks. The IRSO system mainly includes cloud and network + +resource sensing and adaptation capabilities, integrated scheduling capabilities of cloud and network resources, application-oriented service scheduling capabilities, and visualization capabilities. + +NOTE – Network resource scheduling is identical to communication resource scheduling [b-ITU-T F.743.16]. + +IRSO receives the application service requirements, generates and responds with integrated resource scheduling solutions, as well as issues the notification of scheduling directly through the northbound reference point IF3, which is the service interface between it and the capability invokers, such as third-party applications, self-operation applications and developers. + +IRSO can also indirectly receive the application service requirements and expose the corresponding capabilities to capability invokers through northbound reference point IF4 (the service interface between IRSO and capability exposure platform) and northbound reference point IF5 (the service interface between capability exposure platform and capability invokers), by invoking northbound application programming interfaces (APIs). + +IRSO system collects network and cloud resources status information from the network management system (NMS) and cloud management system (CMS) through southbound reference points IF1 and IF2, respectively, and distributes integrated resource scheduling and orchestration policies to NMS and CMS by invoking southbound APIs. + +![Diagram of the general signalling architecture for supporting integrated resource scheduling and orchestration for future networks. The diagram shows a layered structure. At the top are 'Capability invokers/Customers' (Third-party applications, Self-operation applications, Developers). Below them is the 'Capability exposure' layer. Between the top layer and the next is the 'Northbound API' with reference point IF-5. Below the Northbound API is the 'IRSO' layer, which contains four capabilities: 'Resource awareness capability', 'Integrated resource scheduling capability', 'Service scheduling capability', and 'Visualization capability'. Below the IRSO layer is the 'Southbound API' with reference points IF-1 and IF-2. At the bottom are the 'Network management system' and 'Cloud management system'. Reference point IF-3 is shown on the left between the Capability invokers and the IRSO layer.](367926125450c2bc3f4bdca9d59a62ba_img.jpg) + +Diagram of the general signalling architecture for supporting integrated resource scheduling and orchestration for future networks. The diagram shows a layered structure. At the top are 'Capability invokers/Customers' (Third-party applications, Self-operation applications, Developers). Below them is the 'Capability exposure' layer. Between the top layer and the next is the 'Northbound API' with reference point IF-5. Below the Northbound API is the 'IRSO' layer, which contains four capabilities: 'Resource awareness capability', 'Integrated resource scheduling capability', 'Service scheduling capability', and 'Visualization capability'. Below the IRSO layer is the 'Southbound API' with reference points IF-1 and IF-2. At the bottom are the 'Network management system' and 'Cloud management system'. Reference point IF-3 is shown on the left between the Capability invokers and the IRSO layer. + +**Figure 6-1 – General signalling architecture for supporting integrated resource scheduling and orchestration for future networks** + +The IRSO system supports different applications, and is required to satisfy the following requirements: + +- For data storage applications, which include data (e.g., video, voice, pictures, etc.), backup storage and real-time video data scheduling and storage, it requires cloud resources and network transmission resources that meet storage needs. +- For AI/machine learning (ML) computing applications (e.g., centralized AI training services and rendering services, local AI training/inference services, etc.), it requires centralized cloud resources and network transmission resources to meet large-scale AI training/inference requirements and selects edge cloud resources to meet low latency requirements. +- For supercomputing applications (e.g., basic scientific research, engineering simulation, weather forecast, bioinformatics and biomedicine, etc.), it requires high-performance computing resources and data transmission links to meet supercomputing requirements. + +- For applications, dynamic migration scenarios (e.g., application recovery backup, application migration due to demand changes, etc.), it requires to select new cloud resources and data transmission resources for application migration, which includes image deployment and data synchronization. + +To achieve the integrated scheduling and orchestration of multi-type resources as described above, and effectively meet the diverse requirements of different application scenarios, the northbound and southbound interfaces supporting integrated resource scheduling and orchestration are specified in clause 7; the signalling flows for task scheduling, service exposure and southbound resource operations are detailed in clause 8; and the message formats for various interactions are specified in clause 9. Therefore, a complete protocol framework for the IRSO system is formed, laying a foundation for the practical application of integrated resource scheduling and orchestration in future networks including IMT-2020. + +# 7 Interfaces for supporting integrated resource scheduling and orchestration + +## 7.1 Northbound interfaces + +IRSO system provides the capabilities of integrated resource scheduling and orchestration to capability invokers (e.g., third-party applications, self-operation applications and developers) by northbound reference points IF3 and IF4. + +It is required to provide the service exposure capabilities for supporting integrated resource scheduling by the following northbound interfaces: + +- Service consultation interface: consultation of service-oriented resource availability according to the service level agreement (SLA) requirements of the application service; +- Service session creation interface: service session creation and alternative policies calculation according to the SLA requirements of the application service; +- Service policy deployment interface: service policy selection and activation to deploy resources according to alternative policies returned by service session creation interface; +- Service session modification interface: adjustment of service requirements includes modification of the service description information and the resource requirement parameters; +- Service session release interface: deletion of service session according to the service deletion request; +- Service subscription query interface: query of service subscription and resources information; +- Service quality assurance query interface: detection of connectivity, bandwidth and latency according to customer service quality detection requests. + +In addition, task scheduling capability is undertaken by IF3, with invokers comprising third-party applications and customers. + +## 7.2 Southbound interfaces + +IRSO invokes the sensing capabilities and configuration capabilities of cloud and network resources from CMS and NMS by southbound interfaces. Sensing capabilities refer to obtaining status information of underlying network and cloud resources by southbound reference points IF1 and IF2, providing the IRSO system with the capability to query the availability of cloud and network resources. These data serve as crucial input for calculating scheduling strategies, ensuring the accuracy and real-time performance of scheduling strategies. Configuration capabilities enable creation, query, update, and deletion operations of cloud and network resources based on the scheduling strategies, by reference points IF1 and IF2, supporting dynamic resource allocation and management to meet the changing needs of different services. + +It is required to invoke the sensing capabilities for supporting integrated resource scheduling by the following southbound interfaces: + +- Network resource data sensing interface: perception of resource information between network sensing nodes, including bandwidth, delay, jitter, and packet loss rate; +- Cloud resource data sensing interface: perception of resource information of cloud resource nodes, including total and used central processing unit (CPU), total and used graphics processing unit (GPU), total and used memory, total and used storage resources, as well as total and used bandwidth in incoming/outgoing directions. + +It is required to invoke the configuration capabilities for supporting integrated resource scheduling by the following southbound interfaces: + +- Network resource creation interface: configuration of parameters such as composed virtual private network resource configuration, QoS policies, and link types (dedicated/public network) from access node to destination node based on the selected service scheduling policy; +- Cloud resource creation interface: configuration of cloud resources such as CPU, GPU, memory and storage based on the selected service scheduling policy; +- Network resource query interface: query of the status of network resources corresponding to the customer-selected policies, including key performance indicators such as bandwidth, latency, jitter, and packet loss rate according to the service identifier (ID); +- Cloud resource query interface: query of the utilization rate of CPU, GPU, memory and storage resources according to the service ID; +- Network resource update interface: adjustment of network resource according to the customer's updated policies choice, such as modifying bandwidth, adjusting QoS levels, and switching link types and network availability level; +- Cloud resource update interface: adjustment of cloud resource according to the customer's updated policy choice, such as increasing CPU cores, expanding memory, and upgrading image versions; +- Network resource delete interface: releasing corresponding network resources according to customer service deletion requests; +- Network resource delete interface: releasing corresponding cloud resources according to customer service deletion requests. + +# **8 Signalling flow for supporting integrated resource scheduling and orchestration** + +## **8.1 Signalling flow of task scheduling** + +The signalling flow of task scheduling is shown in Figure 8-1 and described in the text that follows it. + +![Sequence diagram showing the signalling flow of task scheduling between Third-party applications and IRSO. The flow consists of five steps: 1. TaskScheduling_Request from Third-party applications to IRSO; 2. Parse the task scheduling request to obtain task attribute data (internal to IRSO); 3. Obtain the task scheduling policy for the task scheduling request (internal to IRSO); 4. Distribute the task scheduling policy (internal to IRSO); 5. TaskScheduling_Response from IRSO to Third-party applications. The diagram is labeled Q.5034(26).](d4af765160d04ecef538e5066006dc77_img.jpg) + +``` + +sequenceDiagram + participant Third-party applications + participant IRSO + Note right of IRSO: 2. Parse the task scheduling request to obtain task attribute data + Note right of IRSO: 3. Obtain the task scheduling policy for the task scheduling request + Note right of IRSO: 4. Distribute the task scheduling policy + Third-party applications->>IRSO: 1. TaskScheduling_Request + IRSO-->>Third-party applications: 5. TaskScheduling_Response + +``` + +Sequence diagram showing the signalling flow of task scheduling between Third-party applications and IRSO. The flow consists of five steps: 1. TaskScheduling\_Request from Third-party applications to IRSO; 2. Parse the task scheduling request to obtain task attribute data (internal to IRSO); 3. Obtain the task scheduling policy for the task scheduling request (internal to IRSO); 4. Distribute the task scheduling policy (internal to IRSO); 5. TaskScheduling\_Response from IRSO to Third-party applications. The diagram is labeled Q.5034(26). + +**Figure 8-1 – Signalling flow of task scheduling** + +1. IRSO receives a task scheduling request from the third-party applications. +2. IRSO obtains task attribute data, including the task basic information and the task effect target data, by parsing the task scheduling request, extracting the task basic information corresponding to the task scheduling request, obtaining the SLA corresponding to the task scheduling request, and determining the task effect target data based on the SLA. The task basic information includes: task request type and task data volume; the task effect target data includes at least one or more targets of task time-consuming target, task energy consumption target, and task cost target. +3. The task attribute data is input into the trained task scheduling model to obtain the task scheduling policy for the task scheduling request. The task scheduling policy includes the computing resource scheduling information of the target cloud resource pool (e.g., cloud resource pool type, target cloud resource pool ID, computing resource scheduling information, storage resource scheduling information, etc.) and the network bandwidth scheduling information to the target cloud resource pool. +4. The task scheduling policy is distributed to the corresponding target computing and network resources control nodes to control the target cloud resource pool to execute the data processing task corresponding to the task scheduling request, after verifying the feasibility of the task scheduling policy. IRSO obtains the current running status information of the target cloud resource pool corresponding to the task scheduling policy and compares the current running status information with the scheduling information of the target cloud resource pool to verify the feasibility of the task scheduling policy, in order to distribute the task scheduling policy to the corresponding target cloud resource pool after will verify the feasibility of the task scheduling policy. +5. IRSO sends the task scheduling response to the third-party applications to indicate the task scheduling result for the task scheduling request. + +## **8.2 Signalling flow of service exposure for supporting integrated scheduling** + +### **8.2.1 General** + +The service handling method for supporting integrated scheduling is applied to the capability exposure platform. The capability exposure platform is used to provide multiple service capabilities and service interfaces, where different service interfaces correspond to different service capabilities in the cloud-network integrated scheduling scenarios, and the cloud-network integrated scheduling scenario is used for scheduling basic cloud-network infrastructure resources, as specified in clauses 8.2.2 to 8.2.7. The service handling method supported by these interfaces includes: + +- The capability exposure platform receives a cloud-network integrated service invocation request sent by a capability invoker through calling a specific service interface. This cloud-network integrated service invocation request is used to invoke a specific service capability associated with the specific service interface. +- The capability exposure platform forwards the cloud-network integrated service invocation request to the capability provider. The capability provider is responsible for processing the cloud-network integrated service invocation request and generating the corresponding response result for the request. +- Upon receiving the response result from the capability provider, the response result for the request is returned to the capability invoker. + +### 8.2.2 Service resource consultation + +The described service capabilities include service resource consultation capability, and the specific service interfaces, as described in clause 8.2.1, include the service resource consultation interface. The cloud-network integrated service invocation requests include the service resource consultation request. The response results for the requests include the service resource consultation response. + +The signalling flow for service resource consultation is shown in Figure 8-2 and described in the text that follows it. + +![Sequence diagram showing the signalling flow of service resource consultation between a Capability invoker, Capability exposure platform, and IRSO.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +``` + +sequenceDiagram + participant CI as Capability invoker + participant CEP as Capability exposure platform + participant IRSO as IRSO + + CI->>CEP: 1. ServiceResourceConsultation_Request + Note over CEP: 2. Authenticates the invokers' identity + CEP->>IRSO: 3. Forwards the service resource consultation request + Note over IRSO: 4. Checks the resource availability, calculate scheduling strategy + IRSO-->>CI: 5. ServiceResourceConsultation_Response + +``` + +The diagram illustrates the interaction between three entities: Capability invoker, Capability exposure platform, and IRSO. The sequence of messages is as follows: + +- The Capability invoker sends a **ServiceResourceConsultation\_Request** to the Capability exposure platform. +- The Capability exposure platform performs an internal step: **Authenticates the invokers' identity**. +- The Capability exposure platform then sends a message to the IRSO: **Forwards the service resource consultation request**. +- The IRSO performs an internal step: **Checks the resource availability, calculate scheduling strategy**. +- Finally, a response is sent back to the Capability invoker: **ServiceResourceConsultation\_Response**. + +Sequence diagram showing the signalling flow of service resource consultation between a Capability invoker, Capability exposure platform, and IRSO. + +**Figure 8-2 – Signalling flow of service resource consultation** + +The steps are as follows: + +- The capability exposure platform receives the cloud-network integrated service invocation request sent by the capability invoker through the specific service interface, namely service resource consultation interface. +- Then the capability exposure platform performs identity and security authentication on the capability invoker and forwards the service resource consultation request to the capability provider (IRSO system) after the identity and security authentication is passed. The service resource consultation request contains the service description information and service requirement information of the service to be invoked. The service requirement information includes resource requirement information and/or endpoint address requirement information, and the endpoint address requirement information includes one or more specified endpoint address information. +- The service resource consultation request is forwarded to the capability provider (IRSO system). + +4. The capability provider (IRSO system) determines whether real-time invocation of the service to be invoked is supported based on the resource availability corresponding to the service: + - When real-time invocation of the service to be invoked is supported, IRSO calculates a resource configuration strategy for the service to be invoked based on the service requirement information, and generates the service resource consultation response based on the service description information, the resource configuration strategy, and the cost information associated with the resource configuration strategy. IRSO can calculate multiple optional resource configuration strategies for the service to be invoked based on the service requirement information, and different optional resource configuration strategies use different system effectiveness metrics as key considerations; + - When real-time invocation of the service to be invoked is not supported, IRSO generates the service resource consultation response based on the service description information combined with resource usage trends. IRSO can also determine the expected waiting time based on resource usage trends and estimate the expected resource configuration strategy for the service to be invoked using the service requirement information and resource usage trends. The service resource consultation response includes service ID, service description information, the expected resource configuration strategy, the expected waiting time, etc. +5. Upon receiving the service resource consultation response returned by the capability provider (IRSO system), the capability exposure platform forwards the service resource consultation response to the capability invoker. + +### 8.2.3 Service session creation + +The described service capabilities include the service session creation capability. The specific service interfaces, as described in clause 8.2.1, include the service session creation interface. The cloud-network integrated service invocation requests include the service session creation request, which contains service description information of the service to be created, and the resource configuration strategy information selected for the service to be created. The response results for the requests include the service session creation response. The signalling flow for service session creation is shown in Figure 8-3 and described in the text that follows it. + +![Sequence diagram showing the signalling flow of service session creation between Capability invoker, Capability exposure platform, and IRSO.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +sequenceDiagram + participant CI as Capability invoker + participant CEP as Capability exposure platform + participant IRSO as IRSO + CI->>CEP: 1. ServiceSessionCreation_Request + CEP->>IRSO: + Note right of IRSO: 2. Performs corresponding integrated resource configuration according to the selected strategy + IRSO->>CEP: + CEP->>CI: 3. ServiceSessionCreation_Response + +``` + +Sequence diagram showing the signalling flow of service session creation between Capability invoker, Capability exposure platform, and IRSO. + +**Figure 8-3 – Signalling flow of service session creation** + +The steps are as follows: + +1. The capability exposure platform receives the cloud-network integrated service invocation request sent by the capability invoker through the specific service interface, namely the service session creation interface, then it forwards the service session creation request to the capability provider (IRSO system). The service session creation contains the service ID and the selected strategy ID. + +2. The capability provider (IRSO system) configures the basic cloud and network infrastructure resources according to the resource configuration strategy information and generates the service session creation response based on the resource configuration results. +3. Upon receiving the service session creation response returned by the capability provider (IRSO system), the capability exposure platform forwards the service session creation response to the capability invoker. + +### 8.2.4 Service session modification + +The described service capabilities include the service session modification capability. The specific service interfaces, as described in clause 8.2.1, include the service session modification interface. The cloud-network integrated service invocation requests include the service session modification request, which contains service description information to be modified and the updated resource requirement parameters. The response results for the requests include the service session modification response. The signalling flow for service session modification is shown in Figure 8-4 and described in the text that follows it. + +![Figure 8-4: Signalling flow of service session modification. The diagram shows three participants: Capability invoker, Capability exposure platform, and IRSO. The flow consists of three steps: 1. ServiceSessionModification_Request from Capability invoker to IRSO via Capability exposure platform; 2. Determine a new scheduling strategy and reconfigure resources (internal to IRSO); 3. ServiceSessionModification_Response from IRSO to Capability invoker via Capability exposure platform.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +sequenceDiagram + participant CI as Capability invoker + participant CEP as Capability exposure platform + participant IRSO as IRSO + Note right of IRSO: 2. Determine a new scheduling strategy and reconfigure resources + CI->>IRSO: 1. ServiceSessionModification_Request + IRSO-->>CI: 3. ServiceSessionModification_Response + +``` + +Q.5034(26) + +Figure 8-4: Signalling flow of service session modification. The diagram shows three participants: Capability invoker, Capability exposure platform, and IRSO. The flow consists of three steps: 1. ServiceSessionModification\_Request from Capability invoker to IRSO via Capability exposure platform; 2. Determine a new scheduling strategy and reconfigure resources (internal to IRSO); 3. ServiceSessionModification\_Response from IRSO to Capability invoker via Capability exposure platform. + +**Figure 8-4 – Signalling flow of service session modification** + +The steps are as follows: + +1. The capability exposure platform receives the cloud-network integrated service invocation request sent by the capability invoker through the specific service interface, namely the service session modification interface, then it forwards the service session modification request to the capability provider (IRSO system). The service session modification request contains the service ID, the updated resource requirements (such as the modified access bandwidth, cloud host requirements, memory requirements, storage requirements), the modified guaranteed time, etc. +2. The capability provider (IRSO system) re-determines a new resource configuration strategy based on the modified resource requirement parameters, re-configures the basic cloud and network infrastructure resources according to the new resource configuration strategy, and generates the service session modification response based on the resource reconfiguration results. +3. Upon receiving the service session modification response returned by the capability provider (IRSO system), the capability exposure platform forwards the service session modification response to the capability invoker. + +### 8.2.5 Service session deletion + +The described service capabilities include the service session deletion capability. The specific service interfaces, as described in clause 8.2.1, include the service session deletion interface. The cloud-network integrated service invocation requests include a service session deletion request, which contains the service description information of the service to be deleted. The response results for the + +requests include the service session deletion response. The signalling flow for service session deletion is shown in Figure 8-5 and described in the text that follows it. + +![Sequence diagram for service session deletion](5cab96b2d23174c25919840ecd50aa48_img.jpg) + +``` +sequenceDiagram + participant CI as Capability invoker + participant CEP as Capability exposure platform + participant IRSO as IRSO + Note right of IRSO: 2. Delete the resource configuration corresponding to the service ID and release the resources + CI->>IRSO: 1. ServiceSessionDeletion_Request + IRSO-->>CEP: 3. ServiceSessionDeletion_Response + CEP-->>CI: 3. ServiceSessionDeletion_Response +``` + +The diagram illustrates the signalling flow for service session deletion. It features three lifelines: Capability invoker, Capability exposure platform, and IRSO. The process begins with the Capability invoker sending a '1. ServiceSessionDeletion\_Request' to the IRSO via the Capability exposure platform. The IRSO then performs an internal action: '2. Delete the resource configuration corresponding to the service ID and release the resources'. Finally, the IRSO sends a '3. ServiceSessionDeletion\_Response' back to the Capability invoker via the Capability exposure platform. The reference 'Q.5034(26)' is noted in the bottom right corner. + +Sequence diagram for service session deletion + +**Figure 8-5 – Signalling flow of service session deletion** + +The steps are as follows: + +1. The capability exposure platform receives the service invocation request sent by the capability invoker through the specific service interface, namely the service session deletion interface, then it forwards the service session deletion request to the capability provider (IRSO system). +2. The capability provider (IRSO system) deletes the resource configuration results associated with the service to be deleted, releases the basic cloud and network infrastructure resources occupied by the service to be deleted, and generates the service session deletion response based on the resource release results. +3. Upon receiving the service session deletion response returned by the capability provider (IRSO system), the capability exposure platform forwards the service session deletion response to the capability invoker. + +### 8.2.6 Service subscription query + +The described service capabilities include the service subscription query capability. The specific service interfaces, as described in clause 8.2.1, include the service subscription query interface. The cloud-network integrated service invocation requests include the service subscription query request, which contains the service description information of the service to be queried. The response results for the requests include the service subscription query response. The signalling flow for service subscription query is shown in Figure 8-6 and described in the text that follows it. + +![Sequence diagram for service subscription query](cb4cfa42ce34febde7bdb882f3fc3094_img.jpg) + +``` +sequenceDiagram + participant CI as Capability invoker + participant CEP as Capability exposure platform + participant IRSO as IRSO + Note right of IRSO: 2. Query the resource subscription information corresponding to the service ID + CI->>IRSO: 1. ServiceSubscriptionQuery_Request + IRSO-->>CEP: 3. ServiceSubscriptionQuery_Response + CEP-->>CI: 3. ServiceSubscriptionQuery_Response +``` + +The diagram illustrates the signalling flow for service subscription query. It features three lifelines: Capability invoker, Capability exposure platform, and IRSO. The process begins with the Capability invoker sending a '1. ServiceSubscriptionQuery\_Request' to the IRSO via the Capability exposure platform. The IRSO then performs an internal action: '2. Query the resource subscription information corresponding to the service ID'. Finally, the IRSO sends a '3. ServiceSubscriptionQuery\_Response' back to the Capability invoker via the Capability exposure platform. The reference 'Q.5034(26)' is noted in the bottom right corner. + +Sequence diagram for service subscription query + +**Figure 8-6 – Signalling flow of service subscription query** + +The steps are as follows: + +1. The capability exposure platform receives the cloud-network integrated service invocation request sent by the capability invoker through the specific service interface, namely the service subscription query interface, then it forwards the service subscription query request to the capability provider (IRSO system). +2. The capability provider (IRSO system) queries the resource subscription information associated with the service to be queried based on the service description information of the service to be queried, and generates the service subscription query response based on the resource subscription information. +3. Upon receiving the service subscription query response returned by the capability provider (IRSO system), the capability exposure platform forwards the service subscription query response to the capability invoker. The service subscription query response includes purchased cloud resources, network bandwidth, guaranteed time duration, etc. + +### 8.2.7 Service quality assurance query + +The described service capabilities include the service quality assurance query capability. The specific service interfaces, as described in clause 8.2.1, include the service quality assurance query interface. The cloud-network integrated service invocation requests include the service quality assurance query request, which contains the QoS requirement metrics for the subscribed service. The response results for the requests include the service quality assurance query response. The signalling flow for service quality assurance query is shown in Figure 8-7 and described in the text that follows it. + +![Sequence diagram showing the signalling flow of service quality assurance query between Capability invoker, Capability exposure platform, and IRSO.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +``` +sequenceDiagram + participant CI as Capability invoker + participant CEP as Capability exposure platform + participant IRSO as IRSO + Note right of IRSO: 2. Conducts resource guarantee detection and prediction for the subscribed service + CI->>CEP: 1. ServiceQualityAssuranceQuery_Request + CEP->>IRSO: + IRSO-->>CEP: + CEP->>CI: 3. ServiceQualityAssuranceQuery_Response +``` + +The diagram illustrates the signalling flow for a service quality assurance query. It involves three main components: Capability invoker, Capability exposure platform, and IRSO. The sequence of messages is as follows: 1. The Capability invoker sends a 'ServiceQualityAssuranceQuery\_Request' to the Capability exposure platform. 2. The Capability exposure platform forwards this request to the IRSO. 3. The IRSO performs resource guarantee detection and prediction for the subscribed service. 4. The IRSO returns a 'ServiceQualityAssuranceQuery\_Response' to the Capability exposure platform, which then forwards it to the Capability invoker. The diagram is labeled Q.5034(26). + +Sequence diagram showing the signalling flow of service quality assurance query between Capability invoker, Capability exposure platform, and IRSO. + +**Figure 8-7 – Signalling flow of service quality assurance query** + +The steps are as follows: + +1. The capability exposure platform receives the service invocation request sent by the capability invoker through the specific service interface, namely the service quality assurance query interface, then it forwards the service quality assurance query request to the capability provider (IRSO system). +2. The capability provider (IRSO system) conducts quality of service analysis on the subscribed service, including detection and prediction of network performance indicators (such as connectivity/bandwidth/delay/jitter), as well as detection and prediction of cloud resource availability and utilization rate. Based on the comparison between the service quality analysis results and the QoS requirement metrics, the capability provider generates the service quality assurance query response. +3. Upon receiving the service quality assurance query response returned by the capability provider (IRSO system), the capability exposure platform forwards the service quality assurance query response to the capability invoker. The service quality assurance query result includes service ID, quality guarantee detection and prediction, etc. + +## 8.3 Signalling flow of southbound interfaces for supporting integrated scheduling + +### 8.3.1 Data sensing of cloud and network resources + +Data sensing is mainly initiated by IRSO to the NMS and CMS by using network data subscription operation and cloud data subscription operation through the southbound sensing interfaces. The signalling flow of data sensing of cloud and network resources is shown in Figure 8-8 and described in the text that follows it. + +![Sequence diagram showing the signalling flow of data sensing of cloud and network resources between IRSO, NMS, and CMS.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` +sequenceDiagram + participant IRSO + participant NMS + participant CMS + IRSO->>NMS: 1.1 NetworkDataSubscription_Request + IRSO->>CMS: 1.2 CloudDataSubscription_Request + Note over NMS: 2.1 Formats and packages the +collected network resource data +based on the data request + Note over CMS: 2.2 Formats and packages the +collected cloud resource data +based on the data request + NMS->>IRSO: 3.1 NetworkDataSubscription_Response + CMS->>IRSO: 3.2 CloudDataSubscription_Response + Note over IRSO: 4. Processes the perceived data +``` + +The diagram illustrates the signalling flow for data sensing. It involves three main entities: IRSO, NMS, and CMS. The sequence of interactions is as follows: 1. IRSO sends a 'NetworkDataSubscription\_Request' (1.1) to NMS and a 'CloudDataSubscription\_Request' (1.2) to CMS. 2. NMS and CMS perform internal processing: '2.1 Formats and packages the collected network resource data based on the data request' and '2.2 Formats and packages the collected cloud resource data based on the data request' respectively. 3. NMS sends a 'NetworkDataSubscription\_Response' (3.1) back to IRSO, and CMS sends a 'CloudDataSubscription\_Response' (3.2) back to IRSO. 4. IRSO then 'Processes the perceived data'. + +Sequence diagram showing the signalling flow of data sensing of cloud and network resources between IRSO, NMS, and CMS. + +Figure 8-8 – Signalling flow of data sensing of cloud and network resources + +The steps are as follows: + +1. The IRSO system initiates resource data subscription requests to the NMS and CMS through the network resource data sensing interface and cloud resource data sensing interface, respectively, according to current task requirements by invoking NetworkDataSubscription\_Request (step 1.1) and CloudDataSubscription\_Request (step 1.2). +2. After receiving the request, the NMS and CMS perform resource status collection operations, and format and package the collected resource data. +3. NMS and CMS return the resource data subscription response to IRSO system, the response includes network resource data, such as network bandwidth, latency, jitter, packet loss rate; as well as cloud resource data, such as CPU, GPU, memory, storage and network usage of cloud resources, by invoking NetworkDataSubscription\_Response (step 3.1) and CloudDataSubscription\_Response (step 3.2) +4. After receiving the resource data, the IRSO system parses, cleans and caches the data. Then, the perceived data can be input into the scheduling algorithm. At the same time, the data can be saved in the database for subsequent trend analysis, capacity planning, performance optimization, etc. + +### 8.3.2 Integrated creation of cloud and network resources + +The integrated creation of cloud and network resources is used to deploy the required resources for services as needed in the underlying network and cloud infrastructure. The signalling flow of integrated creation of cloud and network resources is shown in Figure 8-9 and described in the text that follows it. + +![Sequence diagram showing the signalling flow for integrated creation of cloud and network resources between IRSO, NMS, and CMS.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +``` + +sequenceDiagram + participant IRSO + participant NMS + participant CMS + Note right of CMS: Q.5034(26) + + IRSO->>NMS: 1.1 NetworkResourceCreation_Request + IRSO->>CMS: 1.2 CloudResourceCreation_Request + Note right of NMS: 2.1 Perform network resource quota verification and allocate and initialize network resources + Note right of CMS: 2.2 Perform cloud resource quota verification and allocate and initialize cloud resources + NMS->>IRSO: 3.1 NetworkResourceCreation_Response + CMS->>IRSO: 3.2 CloudResourceCreation_Response + Note left of NMS: 4. Updates the task status + +``` + +The diagram illustrates the interaction between three entities: IRSO, NMS, and CMS. The sequence of messages is as follows: + + +- IRSO sends a **1.1 NetworkResourceCreation\_Request** to NMS. +- IRSO sends a **1.2 CloudResourceCreation\_Request** to CMS. +- Simultaneously, NMS performs **2.1 Perform network resource quota verification and allocate and initialize network resources** and CMS performs **2.2 Perform cloud resource quota verification and allocate and initialize cloud resources**. +- NMS returns a **3.1 NetworkResourceCreation\_Response** to IRSO. +- CMS returns a **3.2 CloudResourceCreation\_Response** to IRSO. +- Finally, IRSO performs **4. Updates the task status**. + +Sequence diagram showing the signalling flow for integrated creation of cloud and network resources between IRSO, NMS, and CMS. + +**Figure 8-9 – Signalling flow of integrated creation of cloud and network resources** + +The steps are as follows: + +1. IRSO initiates resource creation requests to the NMS and CMS through the network resource creation interface and cloud resource creation interface, respectively, by invoking **NetworkResourceCreation\_Request** (step 1.1) and **CloudResourceCreation\_Request** (step 1.2). +2. After receiving the request, the NMS and CMS perform resource quota verification to determine whether the creation conditions are met; +If the conditions are met, the NMS and CMS allocate and initialize resources in the underlying infrastructure; +In case of exceptions during the creation process (such as insufficient resources, permission issues, etc.), the NMS and CMS will return a clear error code. +3. Once the resource creation is completed, the NMS and CMS return the result to the IRSO system by invoking **NetworkResourceCreation\_Response** (step 3.1) and **CloudResourceCreation\_Response** (step 3.2). +4. IRSO configures the task status accordingly and can monitor, optimize or release the resource of the task according to the requests. + +### 8.3.3 Integrated query of cloud and network resources + +The integrated query of cloud and network resources is used to obtain the status and attribute information of deployed resources, facilitating the IRSO system to manage resources and optimize scheduling. The signalling flow of the integrated query of cloud and network resources is shown in Figure 8-10 and described in the text that follows it. + +![Sequence diagram showing the signalling flow of integrated query of cloud and network resources between IRSO, NMS, and CMS.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +``` + +sequenceDiagram + participant IRSO + participant NMS + participant CMS + Note right of CMS: Q.5034(26) + IRSO->>NMS: 1.1 NetworkResourceQuery_Request + IRSO->>CMS: 1.2 CloudResourceQuery_Request + Note right of NMS: 2.1 Retrieve the corresponding network resource information + Note right of CMS: 2.2 Retrieve the corresponding cloud resource information + NMS->>IRSO: 3.1 NetworkResourceQuery_Response + CMS->>IRSO: 3.2 CloudResourceQuery_Response + +``` + +Sequence diagram showing the signalling flow of integrated query of cloud and network resources between IRSO, NMS, and CMS. + +**Figure 8-10 – Signalling flow of integrated query of cloud and network resources** + +The steps are as follows: + +1. The IRSO system initiates query requests to the NMS and CMS through the network resource query interface and cloud resource query interface respectively according to the parameters such as task ID, resource type and resource ID to be queried, by invoking `NetworkResourceQuery_Request` (step 1.1) and `CloudResourceQuery_Request` (step 1.2). +2. After receiving the query request, the NMS and CMS retrieve the corresponding resource information of the task to be queried, which includes resource configuration details, operating status, performance indicators, associated resources, etc. +3. NMS and CMS send the query response to the IRSO system in a standardized format. The IRSO system can use the query results for resource status display, performance analysis and scheduling strategy adjustment by invoking `NetworkResourceQuery_Response` (step 3.1) and `CloudResourceQuery_Response` (step 3.2). + +### 8.3.4 Integrated update of cloud and network resources + +The integrated update of cloud and network resources is used to dynamically adjust resource configurations when service requirements change, achieving flexible resource scheduling. The signalling flow of the integrated update of cloud and network resources is shown in Figure 8-11 and described in the text that follows it. + +![Sequence diagram showing the signalling flow of integrated update of cloud and network resources between IRSO, NMS, and CMS.](2eb23c2210154279f8013a1594fbcc5a_img.jpg) + +``` + +sequenceDiagram + participant IRSO + participant NMS + participant CMS + Note right of CMS: Q.5034(26) + IRSO->>NMS: 1.1 NetworkResourceUpdate_Request + IRSO->>CMS: 1.2 CloudResourceUpdate_Request + Note right of NMS: 2.1 Update network resources + Note right of CMS: 2.2 Update cloud resources + NMS->>IRSO: 3.1 NetworkResourceUpdate_Response + CMS->>IRSO: 3.2 CloudResourceUpdate_Response + IRSO->>NMS: 4. Updates the task status + +``` + +Sequence diagram showing the signalling flow of integrated update of cloud and network resources between IRSO, NMS, and CMS. + +**Figure 8-11 – Signalling flow of integrated update of cloud and network resources** + +The steps are as follows: + +1. The IRSO system sends resource update requests to the NMS and CMS through the network resource update interface and cloud resource update interface, respectively, by invoking `NetworkResourceUpdate_Request` (step 1.1) and `CloudResourceUpdate_Request` (step 1.2). + +2. The NMS and CMS verify whether the resources exist and can be updated; after the verification, the NMS and CMS update the resource parameters according to the update requests, such as adjusting bandwidth, expanding memory, CPU cores, etc. +3. After the update is completed, the NMS and CMS return the resource update response to the IRSO system by invoking `NetworkResourceUpdate_Response` (step 3.1) and `CloudResourceUpdate_Response` (step 3.2). +4. IRSO system updates the task status accordingly. + +### 8.3.5 Integrated deletion of cloud and network resources + +The resource deletion process is used to release unused resources for a finished task, improve resource utilization, and prevent resource waste. The signalling flow of integrated deletion of cloud and network resources is shown in Figure 8-12 and described in the text that follows it. + +![Sequence diagram showing the signalling flow of integrated deletion of cloud and network resources between IRSO, NMS, and CMS.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +``` + +sequenceDiagram + participant IRSO + participant NMS + participant CMS + Note right of CMS: Q.5034(26) + + IRSO->>NMS: 1.1 NetworkResourceDelete_Request + IRSO->>CMS: 1.2 CloudResourceDelete_Request + Note right of NMS: 2.1 Execute the deletion operation of network resource + Note right of CMS: 2.2 Execute the deletion operation of cloud resource + NMS->>IRSO: 3.1 NetworkResourceDelete_Response + CMS->>IRSO: 3.2 CloudResourceDelete_Response + +``` + +The diagram illustrates the interaction between the IRSO, NMS, and CMS for resource deletion. The IRSO sends two requests: 1.1 `NetworkResourceDelete_Request` to the NMS and 1.2 `CloudResourceDelete_Request` to the CMS. The NMS and CMS then execute their respective deletion operations (2.1 and 2.2). Finally, they return responses: 3.1 `NetworkResourceDelete_Response` from the NMS and 3.2 `CloudResourceDelete_Response` from the CMS back to the IRSO. A label 'Q.5034(26)' is present in the bottom right corner of the diagram area. + +Sequence diagram showing the signalling flow of integrated deletion of cloud and network resources between IRSO, NMS, and CMS. + +**Figure 8-12 – Signalling flow of integrated deletion of cloud and network resources** + +The steps are as follows: + +1. The IRSO system sends resource delete requests to the NMS and CMS through the network resource deletion interface and cloud resource deletion interface, respectively, by invoking `NetworkResourceDelete_Request` (step 1.1) and `CloudResourceDelete_Request` (step 1.2). +2. After receiving the request, the NMS and CMS check whether the resources exist and have dependency relationships; if there is no conflict, the NMS and CMS execute the deletion operation and recycle resources quota occupied by the task. +3. Once the deletion is completed, the NMS and CMS return the resource delete response to the IRSO system by invoking `NetworkResourceDelete_Response` (step 3.1) and `CloudResourceDelete_Response` (step 3.2). + +NOTE 1 –A soft deletion mechanism is supported. which supports logical deletion rather than physical deletion, to facilitate subsequent recovery. + +NOTE 2 – The deletion process should not affect other running resources. + +# 9 Message format for supporting integrated resource scheduling and orchestration + +## 9.1 Task scheduling + +This message is sent to IRSO to request task scheduling. + +Table 9-1 describes the detailed information of `task_scheduling_Request`. + +**Table 9-1 – Task scheduling\_ Request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|----------------------------------------| +| TaskRequestType | M | string | 1..N | Type of task | +| TaskDataVolume | M | string | 1..N | Data volume of the task | +| SLA | M | string | 1 | SLA requirements indicate task targets | + +Table 9-2 describes the detailed information of task scheduling\_ Response. + +**Table 9-2 – Task scheduling\_ Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|-------------------|-------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 201
400
500 | Indicates the success or failure of task scheduling:
201: Created
400: Invalid input
500: Internal error | + +## 9.2 Integrated scheduling service exposure + +### 9.2.1 Service resource consultation + +This message is sent to IRSO to request a service resource consultation. + +Table 9-3 describes the detailed information of ServiceResourceConsultation\_ Request. + +**Table 9-3 – ServiceResourceConsultation\_ Request** + +| Information element | Status | Data type | Cardinality | Description | +|----------------------|--------|-----------|-------------|------------------------------------------------------------------------------------------| +| InvokerID | M | string | 1 | Indicate the unique identifier of the capability invoker | +| ServiceDescription | M | string | 1 | Description of the service to be invoked. | +| ResourceRequirements | O | array | 1..N | Resource needs (CPU/memory/storage). Required if no endpoint specified. | +| EndpointAddresses | O | string | 1..N | List of specified endpoint addresses. Required if no resource requirements are provided. | +| ServiceTypeIndicator | M | string | 1 | Category of requested service (e.g., "real-time", "batch") | + +Table 9-4 describes the detailed information of ServiceResourceConsultation\_ Response. + +**Table 9-4 – ServiceResourceConsultation\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|--------------------------|--------|-----------|-------------|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 200
202
400
500 | Indicates the success or failure of the service resource consultation.
200 Real-time supported
202 Async (non-real-time)
400 Input Parameter Error
500 Server Internal Error | +| ServiceID | C | string | 0..1 | N/A | Service identifier. Present when the result is 200 or 202. | +| RealTimeSupported | C | boolean | 0..1 | N/A | true/false. It's true when the result is 200, and false when the result is 202. | +| ResourceConfigStrategies | C | array | 0..N | N/A | Resource configuration strategies. Present when RealTimeSupported is true. | +| ExpectedWaitingTime | C | number | 0..1 | N/A | Minutes. Present when RealTimeSupported is false. | +| ExpectedResourceConfig | C | object | 0..1 | N/A | Estimated resource plan. Present when RealTimeSupported is false. | +| UsageTrendAnalysis | C | string | 0..1 | N/A | Resource trend insights. Present when the result is 202. | + +### 9.2.2 Service session creation + +This message is sent to IRSO to request a service session creation. + +Table 9-5 describes the detailed information of ServiceSessionCreation\_Request. + +**Table 9-5 – ServiceSessionCreation\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|------------------------------------------------------------------| +| InvokerID | M | string | 1 | Indicate the unique identifier of the capability invoker. | +| ServiceID | M | string | 1 | Identifier of the service to be created | +| StrategyID | M | string | 1 | Identifier of the pre-negotiated resource configuration strategy | + +Table 9-6 describes the detailed information of ServiceSessionCreation\_Response. + +**Table 9-6 – ServiceSessionCreation\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 201
400
409
500 | Indicates the success or failure of the service session creation.
201: Created
400: Invalid input
409: Strategy conflict
500: Internal error | +| SessionID | C | string | 0..1 | N/A | Unique session identifier. Present when the result is 201 | +| ActivationDeadline | C | datetime | 0..1 | N/A | Timestamp by which resources will be active. Present when the result is 201 | +| ConflictDetails | C | string | 0..1 | N/A | Description of strategy conflict. Present when the result is 409 | + +### **9.2.3 Service session modification** + +This message is sent to IRSO to request a service session modification. + +Table 9-7 describes the detailed information of ServiceSessionModification\_Request. + +**Table 9-7 – ServiceSessionModification\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|------------------------|--------|-----------|-------------|----------------------------------------------------| +| SessionID | M | string | 1 | Identifier of the active service session to modify | +| ModifiedGuaranteedTime | M | datetime | 1 | Updated service guarantee timeframe | +| AccessBandwidth | O | number | 0..1 | Updated bandwidth requirement | +| ComputeRequirements | O | object | 0..1 | Updated cloud resource requirement | +| StorageRequirements | O | object | 0..1 | Updated storage requirement | +| MemoryRequirements | O | object | 0..1 | Updated memory requirement | + +Table 9-8 describes the detailed information of ServiceSessionModification\_Response. + +**Table 9-8 – ServiceSessionModification\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 200
400
409
500 | Indicates the success or failure of the service session modification.
200: Success
400: Invalid input
409: Resource conflict
500: Internal error | + +**Table 9-8 – ServiceSessionModification\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|------------|---------------------------------------------------------------------| +| NewStrategyID | C | string | 0..1 | N/A | Identifier of new resource strategy. Present when the result is 200 | +| ReconfigurationTime | C | datetime | 0..1 | N/A | Timestamp when changes take effect | +| ImpactAnalysis | C | object | 0..1 | N/A | Service disruption estimates. Present when the result is 200 | +| ConflictDetails | C | string | 0..1 | N/A | Resource limitation details. Present when the result is 409 | + +### **9.2.4 Service session deletion** + +This message is sent to IRSO to request a service session deletion. + +Table 9-9 describes the detailed information of ServiceSessionDeletion\_Request. + +**Table 9-9 – ServiceSessionDeletion\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|--------------------------------------------------------------------| +| SessionID | M | string | 1 | Identifier of the service session to delete | +| DeletionMode | O | enum | 0..1 | graceful (default): phased release
immediate: force termination | +| DataHandling | O | object | 0..1 | Instructions for residual data processing | + +Table 9-10 describes the detailed information of ServiceSessionDeletion\_Response. + +**Table 9-10 – ServiceSessionDeletion\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 200
400
404
500 | Indicates the success or failure of the service session deletion.
200: Success
400: Invalid request
404: Session not found
500: Internal error | +| ReleaseSummary | C | object | 0..1 | N/A | Resource release report. Present when the result is 200 | +| CompletionTime | C | datetime | 0..1 | N/A | When resources were fully released. Present when the result is 200 | + +### 9.2.5 Service subscription query + +This message is sent to IRSO to request a service subscription query. + +Table 9-11 describes the detailed information of ServiceSubscriptionQuery\_Request. + +**Table 9-11 – ServiceSubscriptionQuery\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|-------------------------------------------------------------------------------------| +| QueryType | M | enum | 1 | Summary (basic info)
detailed (full resource specs)
historical (usage trends) | +| ServiceID | M | string | 1 | Identifier of the service subscription to query | +| TimeRange | O | object | 0..1 | Required for historical queries | + +Table 9-12 describes the detailed information of ServiceSubscriptionQuery\_Response. + +**Table 9-12 – ServiceSubscriptionQuery\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 200
400
404
500 | Indicates the success or failure of the service subscription query.
200: Success
400: Invalid query
404: Subscription not found
500: Internal error | +| SubscriptionDetails | C | object | 0..1 | N/A | Present when the result is 200 | +| UsageTrends | C | object | 0..1 | N/A | Present for historical queries | + +### 9.2.6 Service quality assurance query + +This message is sent to IRSO to request a service quality assurance query. + +Table 9-13 describes the detailed information of ServiceQualityAssuranceQuery\_Request. + +**Table 9-13 – ServiceQualityAssuranceQuery\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|------------------------------------------| +| ServiceID | M | string | 1 | Identifier of the subscribed service | +| QoSMetrics | M | object | 1 | Required quality metrics with thresholds | +| Timestamp | O | enum | 0..1 | Realtime (default) | + +Table 9-14 describes the detailed information of ServiceQualityAssuranceQuery\_Response. + +**Table 9-14 – ServiceQualityAssuranceQuery\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 200
400
404
500 | Indicates the success or failure of the service quality assurance query.
200: Success
400: Invalid query
404: Service not found
500: Internal error | +| QualityReport | C | object | 0..1 | N/A | Present when the result is 200 | +| SLAComplianceScore | C | number | 0..1 | N/A | 0-100% SLA compliance. Present when the result is 200 | + +## 9.3 Southbound interfaces + +### 9.3.1 Network data subscription + +This message is sent from IRSO to NMS to request network data. + +Table 9-15 describes the detailed information of NetworkDataSubscription\_Request. + +**Table 9-15 – NetworkDataSubscription\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|---------------------------------------| +| Network category | M | varchar | 1 | Indicate network category | +| Network_bandwidth | M | int | 1 | Bandwidth (Unit: Mbit/s) | +| Network_latency | M | int | 1 | Latency (Unit: ms) | +| Network_jitter | M | int | 1 | Jitter (Unit: ms) | +| Network_loss | M | number | 1 | Packet Loss Rate (%) | +| Time range | M | string | 1 | Indicate data subscription time range | + +This message is sent from NMS to IRSO to return the response with the network data subscription result. + +Table 9-16 describes the detailed information of NetworkDataSubscription\_Response. + +**Table 9-16 – NetworkDataSubscription\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 200
400
404
500 | Indicates the success or failure of the network data subscription.
200: Success
400: Invalid query
404: Service not found
500: Internal error | +| Subscription_id | M | varchar | 1 | N/A | Unique identifier for the subscription | +| Update_frequency | O | int | 1 | N/A | Data update frequency in seconds | + +**Table 9-16 – NetworkDataSubscription\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|------------|--------------------------------| +| Start_time | M | string | 1 | N/A | Start time of the subscription | +| End_time | M | string | 1 | N/A | End time of the subscription | +| Network category | M | varchar | 1 | N/A | Network category | +| Network_bandwidth | M | int | 1 | N/A | Bandwidth (Unit: Mbit/s) | +| Network_latency | M | int | 1 | N/A | Latency (Unit: ms) | +| Network_jitter | M | int | 1 | N/A | Jitter (Unit: ms) | +| Network_loss | M | number | 1 | N/A | Packet Loss Rate (%) | + +### 9.3.2 Cloud data subscription + +This message is sent from IRSO to CMS to request cloud data. + +Table 9-17 describes the detailed information of CloudDataSubscription\_Request. + +**Table 9-17 – CloudDataSubscription\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|-------------------------|--------|-------------|-------------|---------------------------------------| +| cloud_id | M | varchar(64) | 1 | Cloud pool ID | +| category | M | varchar(20) | 1 | Resource category | +| available_cpu_amount | M | int4 | 1 | Available CPU quantity | +| available_gpu_amount | M | int4 | 1 | Available GPU quantity | +| available_memory | M | int4 | 1 | Available memory size (Unit: GB) | +| pue | O | float8 | 1 | Power usage effectiveness | +| cloud_use_status | M | varchar(32) | 1 | Usage status | +| cloud_allot_status | M | varchar(32) | 1 | Allocation status | +| physical_server_amount | O | int4 | 1 | Quantity of physical servers | +| virtual_machine_amount | O | int4 | 1 | Quantity of virtual machines | +| container_amount | O | int4 | 1 | Quantity of containers | +| total_in_bandwidth | O | int8 | 1 | Total incoming bandwidth (bit/s) | +| total_out_bandwidth | O | int8 | 1 | Total outgoing bandwidth (bit/s) | +| available_in_bandwidth | O | int8 | 1 | Available incoming bandwidth (bit/s) | +| available_out_bandwidth | O | int8 | 1 | Available outgoing bandwidth (bit/s) | +| Time range | M | string | 1 | Indicate data subscription time range | + +This message is sent from CMS to IRSO to return the response with the cloud data subscription result. + +Table 9-18 describes the detailed information of CloudDataSubscription\_Response. + +**Table 9-18 – CloudDataSubscription\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|-------------------------|--------|-------------|-------------|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 200
400
404
500 | Indicates the success or failure of the cloud data subscription.
200: Success
400: Invalid query
404: Service not found
500: Internal error | +| Subscription_id | M | varchar | 1 | N/A | Unique identifier for the subscription | +| Update_frequency | O | int | 1 | N/A | Data update frequency in seconds | +| Start_time | M | string | 1 | N/A | Start time of the subscription | +| End_time | M | string | 1 | N/A | End time of the subscription | +| cloud_id | M | varchar(64) | 1 | N/A | Cloud pool ID | +| category | M | varchar(20) | 1 | N/A | Resource category | +| available_cpu_amount | M | int4 | 1 | N/A | Available CPU quantity | +| available_gpu_amount | M | int4 | 1 | N/A | Available GPU quantity | +| available_memory | M | int4 | 1 | N/A | Available memory size (GB) | +| pue | O | float8 | 1 | N/A | Power usage effectiveness | +| cloud_use_status | M | varchar(32) | 1 | N/A | Usage status | +| cloud_allot_status | M | varchar(32) | 1 | N/A | Allocation status | +| physical_server_amount | O | int4 | 1 | N/A | Quantity of physical servers | +| virtual_machine_amount | O | int4 | 1 | N/A | Quantity of virtual machines | +| container_amount | O | int4 | 1 | N/A | Quantity Of Containers | +| total_in_bandwidth | O | int8 | 1 | N/A | Total incoming bandwidth (bit/s) | +| total_out_bandwidth | O | int8 | 1 | N/A | Total outgoing bandwidth (bit/s) | +| available_in_bandwidth | O | int8 | 1 | N/A | Available incoming bandwidth (bit/s) | +| available_out_bandwidth | O | int8 | 1 | N/A | Available outgoing bandwidth (bit/s) | + +### 9.3.3 Network resource creation + +This message is sent from IRSO to NMS to request a network resource creation. + +Table 9-19 describes the detailed information of NetworkResourceCreation\_Request. + +**Table 9-19 – NetworkResourceCreation\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|------------------------------------------------------| +| Task ID | M | int | 1 | Indicate a unique task identifier | +| Network category | M | varchar | 1 | Indicate network category configuration for the task | +| Network_bandwidth | M | int | 1 | Bandwidth configuration for the task | +| Network_latency | M | int | 1 | Latency configuration for the task | +| Network_jitter | M | int | 1 | Jitter configuration for the task | +| Network_loss | M | number | 1 | Packet loss rate configuration for the task | + +This message is sent from NMS to IRSO to return the response with the network resource creation result. + +Table 9-20 describes the detailed information of NetworkResourceCreation\_Response. + +**Table 9-20 – NetworkResourceCreation\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|----------------------|--------|-----------|-------------|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 201
400
404
500
507 | Indicates the success or failure of the network resource creation.
201: Created
400: Invalid request
404: Service not found
500: Internal error
507: Insufficient resources | +| Task ID | M | int | 1 | N/A | Corresponding to the unique task identifier in the request, used to associate the request with the response. | +| Network resource ID | M | varchar | 1 | N/A | The unique identifier of the newly created network resource (such as link ID, slice ID). | +| Network category | M | varchar | 1 | N/A | Consistent with the network category configuration in the request. | +| Network bandwidth | M | int | 1 | N/A | The actually allocated bandwidth (unit: Mbit/s), which may be consistent with the requested value or adjusted due to resource limitations. | +| Network latency | M | int | 1 | N/A | The actually guaranteed latency (unit: ms). | +| Network jitter | M | int | 1 | N/A | The actually guaranteed jitter (unit: ms). | +| Network loss | M | number | 1 | N/A | The actually guaranteed packet loss rate (%). | +| Creation time | M | string | 1 | N/A | The timestamp when the resource was created | +| Associated resources | O | array | 0..N | N/A | List of associated underlying resources (such as physical link ID, switch port number). | +| Quota usage | O | object | 1 | N/A | Resource quota usage (such as the percentage of used bandwidth in the total quota). | + +### 9.3.4 Cloud resource creation + +This message is sent from IRSO to CMS to request a cloud resource creation. + +Table 9-21 describes the detailed information of CloudResourceCreation\_Request. + +**Table 9-21 – CloudResourceCreation\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|--------------------------------------------------------------------------------------------------| +| Task ID | M | int | 1 | Indicate unique task identifier | +| Cloud service type | M | varchar | 1 | Cloud service type (e.g., virtual machine (VM)/container/bare metal) | +| vCPU cores | M | int | 1 | Number of vCPU cores requested | +| GPU type | O | varchar | 0..1 | GPU accelerator model | +| GPU count | O | int | 0..1 | Number of GPUs | +| Memory (GB) | M | int | 1 | Requested memory capacity (GB) | +| Storage type | M | varchar | 1 | Storage type (solid-state drive (SSD)/hard disk drive (HDD)/ non-volatile memory express (NVMe)) | +| Storage size (GB) | M | int | 1 | Storage space size (GB) | +| OS image | M | varchar | 1 | Operating system image identifier | +| Availability zone | O | varchar | 0..1 | Availability zone for resource deployment | +| Elastic IP | O | boolean | 0..1 | Whether to allocate an Elastic Public IP | + +This message is sent from CMS to IRSO to return the response with the cloud resource creation result. + +Table 9-22 describes the detailed information of CloudResourceCreation\_Response. + +**Table 9-22 – CloudResourceCreation\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 201
400
404
500
507 | Indicates the success or failure of the cloud resource creation.
201: Created
400: Invalid request
404: Service not found
500: Internal error
507: Insufficient resources | +| Task ID | M | int | 1 | N/A | Corresponding to the unique task identifier in the request, used to associate the request with the response. | +| Cloud resource ID | M | varchar | 1 | N/A | Cloud resource instance ID (e.g., VM ID/Container ID) | +| vCPU allocated | M | int | 1 | N/A | Actually allocated vCPU cores (may be adjusted due to resource constraints) | +| GPU allocated | C | varchar | 0..1 | N/A | Actually allocated GPU model and count (mandatory if GPU requested) | +| Memory allocated | M | int | 1 | N/A | Actually allocated memory capacity (GB) | + +**Table 9-22 – CloudResourceCreation\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|----------------------|--------|-----------|-------------|------------|--------------------------------------------------------------------| +| Storage allocated | M | object | 1 | N/A | Actually allocated storage: {type, size (GB)} | +| IP address | M | string | 1 | N/A | Private IP address of the resource | +| Elastic IP | O | string | 0..1 | N/A | Elastic Public IP address (if requested) | +| Creation time | M | string | 1 | N/A | Resource creation timestamp | +| Associated resources | O | array | 0..N | N/A | Associated underlying resources (e.g., cloud disk ID, vSwitch ID) | +| Quota usage | O | object | 1 | N/A | Resource quota usage details (e.g., {vCPU: "15/100", GPU: "2/10"}) | + +### 9.3.5 Network resource query + +This message is sent from IRSO to NMS to request a network resource status. + +Table 9-23 describes the detailed information of NetworkResourceQuery\_Request. + +**Table 9-23 – NetworkResourceQuery\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|------------------------|--------|-----------|-------------|-------------------------------------------------------------------------------| +| Query ID | M | int | 1 | Unique query identifier | +| Tenant ID | O | varchar | 0..1 | Tenant affiliation filter | +| Resource type | O | varchar | 0..1 | Type of network resource (e.g., link/slice/virtual local area network (VLAN)) | +| Min bandwidth (Mbit/s) | O | int | 0..1 | Minimum bandwidth requirement | +| Max latency (ms) | O | int | 0..1 | Maximum acceptable latency | +| Max jitter (ms) | O | int | 0..1 | Maximum acceptable jitter | +| Max loss (%) | O | number | 0..1 | Maximum acceptable packet loss rate | +| Task ID | O | int | 0..1 | Associated task identifier filter | +| Resource status | O | enum | 0..1 | Active/Pending/Released | + +This message is sent from NMS to IRSO to return the response with the queried network resource status. + +Table 9-24 describes the detailed information of NetworkResourceQuery\_Response. + +**Table 9-24 – NetworkResourceQuery\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 200
400
404
500 | Indicates the success or failure of the network resource query.
200: Success
400: Invalid query
404: No matching resources
500: Internal error | +| Query ID | M | int | 1 | N/A | Echoes the Query ID from the request | +| Total resources | M | int | 1 | N/A | Total matching resources count | +| Network resources | M | array | 0..N | N/A | List of matching resources | +| Resource ID | M | varchar | 1 | N/A | Unique network resource identifier | +| Tenant ID | M | varchar | 1 | N/A | Affiliated tenant | +| Resource type | M | varchar | 1 | N/A | Link/Slice/VLAN/etc. | +| Network category | M | varchar | 1 | N/A | Service category (e.g., GOLD/SILVER) | +| Bandwidth (Mbit/s) | M | int | 1 | N/A | Allocated bandwidth | +| Latency (ms) | M | int | 1 | N/A | Guaranteed latency | +| Jitter (ms) | M | int | 1 | N/A | Guaranteed jitter | +| Loss (%) | M | number | 1 | N/A | Guaranteed packet loss rate | +| Creation time | M | string | 1 | N/A | creation timestamp | +| Status | M | enum | 1 | N/A | Active/Pending/Released | +| Associated task ID | M | int | 1 | N/A | Task ID linked to resource | + +### 9.3.6 Cloud resource query + +This message is sent from IRSO to CMS to request a cloud resource status. + +Table 9-25 describes the detailed information of CloudResourceQuery\_Request. + +**Table 9-25 – CloudResourceQuery\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|---------------------------------| +| Query ID | M | int | 1 | Unique query identifier | +| Tenant ID | O | varchar | 0..1 | Tenant affiliation filter | +| Cloud service type | O | enum | 0..1 | VM/Container/Bare metal | +| Min vCPU cores | O | int | 0..1 | Minimum required vCPU cores | +| Min memory (GB) | O | int | 0..1 | Minimum required memory | +| GPU type | O | varchar | 0..1 | Specific GPU model (e.g., A100) | +| Min GPU count | O | int | 0..1 | Minimum required GPUs | +| Storage type | O | enum | 0..1 | SSD/HDD/NVMe | +| Min storage (GB) | O | int | 0..1 | Minimum storage capacity | +| OS image | O | varchar | 0..1 | OS image identifier filter | + +**Table 9-25 – CloudResourceQuery\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|----------------------------| +| Availability zone | O | varchar | 0..1 | Target deployment zone | +| resource status | O | enum | 0..1 | Running/Terminated | +| Task ID | O | int | 0..1 | Associated task identifier | + +This message is sent from CMS to IRSO to return the response with the queried cloud resource status. + +Table 9-26 describes the detailed information of CloudResourceQuery\_Response. + +**Table 9-26 – CloudResourceQuery\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 200
400
404
500 | Indicates the success or failure of the cloud resource query.
200: Success
400: Invalid query
404: No matching resources
500: Internal error | +| Query ID | M | int | 1 | N/A | Echoes request's Query ID | +| Total resources | M | int | 1 | N/A | Total matching resources count | +| Current page | M | int | 1 | N/A | Current page index | +| Page size | M | int | 1 | N/A | Resources per page | +| Cloud resources | M | array | 0..N | N/A | List of matching resources | +| Cloud resource ID | M | varchar | 1 | N/A | Instance ID | +| Tenant ID | M | varchar | 1 | N/A | Resource owner | +| Cloud service type | M | enum | 1 | N/A | VM/Container/Bare Metal | +| vCPU allocated | M | int | 1 | N/A | Actual vCPU cores allocated | +| GPU allocated | M | object | 1 | N/A | {type count} (if applicable) | +| Memory allocated | M | int | 1 | N/A | Actual memory allocated | +| Storage allocated | M | object | 1 | N/A | {type, size} (if applicable) | +| OS image | M | varchar | 1 | N/A | Deployed OS image | +| Availability zone | M | varchar | 1 | N/A | Deployment zone | +| IP address | M | string | 1 | N/A | Private IP address | +| Elastic IP | M | string | 1 | N/A | Public IP (if assigned) | +| Creation time | M | string | 1 | N/A | Creation timestamp | +| Status | M | enum | 1 | N/A | Running/Terminated | +| Associated task ID | M | int | 1 | N/A | Task ID linked to creation | + +### 9.3.7 Network resource update + +This message is sent from IRSO to NMS to request a network resource update. + +Table 9-27 describes the detailed information of NetworkResourceUpdate\_Request. + +**Table 9-27 – NetworkResourceUpdate\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|---------------------------------------------------------| +| Task ID | M | int | 1 | Unique identifier for this update task | +| Network resource ID | M | varchar | 1 | Unique ID of the network resource to update | +| Network bandwidth | O | int | 0..1 | New desired bandwidth (Mbit/s). Omitted if unchanged. | +| Network latency | O | int | 0..1 | New desired latency (ms). Omitted if unchanged. | +| Network jitter | O | int | 0..1 | New desired jitter (ms). Omitted if unchanged. | +| Network loss | O | number | 0..1 | New desired packet loss rate (%). Omitted if unchanged. | + +This message is sent from NMS to IRSO to return the response for the network resource update. + +Table 9-28 describes the detailed information of NetworkResourceUpdate\_Response. + +**Table 9-28 – NetworkResourceUpdate\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 200
400
404
500 | Indicates the success or failure of the network resource update.
200: Success
400: Invalid request
404: Resource not found
500: Internal error | +| Task ID | M | int | 1 | N/A | Echoes the update Task ID from the request | +| Network resource ID | M | varchar | 1 | N/A | Updated resource ID | +| Updated bandwidth | M | int | 1 | N/A | Actually allocated bandwidth after update (Mbit/s) | +| Updated latency | M | int | 1 | N/A | Actually guaranteed latency (ms) | +| Updated jitter | M | int | 1 | N/A | Actually guaranteed jitter (ms) | +| Updated loss | M | number | 1 | N/A | Actually guaranteed packet loss rate (%) | +| Updated time | M | string | 1 | N/A | Timestamp when the update took effect | + +### 9.3.8 Cloud resource update + +This message is sent from IRSO to CMS to request a cloud resource update. + +Table 9-29 describes the detailed information of CloudResourceUpdate\_Request. + +**Table 9-29 – CloudResourceUpdate\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|-----------------------------------------------------| +| Task ID | M | int | 1 | Unique identifier for this update task | +| Cloud resource ID | M | varchar | 1 | ID of the cloud resource to update | +| vCPU cores | O | int | 0..1 | New vCPU requirement (omit to keep current) | +| Memory | O | int | 0..1 | New memory requirement (GB) | +| GPU count | O | int | 0..1 | New GPU count requirement | +| Storage size | O | int | 0..1 | Storage expansion size (GB) – only increase allowed | +| Elastic IP action | O | enum | 0..1 | Attach/Detach/Replace | + +This message is sent from CMS to IRSO to return the response for the cloud resource update. + +Table 9-30 describes the detailed information of CloudResourceUpdate\_Response. + +**Table 9-30 – CloudResourceUpdate\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 200
400
404
500 | Indicates the success or failure of the cloud resource update.
200: Success
400: Invalid request
404: Resource not found
500: Internal error | +| Task ID | M | int | 1 | N/A | Echoes request task ID | +| Cloud resource ID | M | varchar | 1 | N/A | Updated resource ID | +| vCPU allocated | M | int | 1 | N/A | Updated vCPU cores | +| Memory allocated | M | int | 1 | N/A | Updated memory capacity | +| GPU allocated | C | object | 0..1 | N/A | Updated GPU: {type, count} (if present) | +| Storage allocated | M | object | 1 | N/A | Updated storage: {type, size (GB)} | +| Elastic IP | O | string | 0..1 | N/A | Updated public IP (if attached) | +| Current state | M | enum | 1 | N/A | Running/Terminated | +| Update time | M | string | 1 | N/A | Timestamp when update completed | +| Modified attributes | M | array | 1..N | N/A | List of changed parameters (e.g., ["vCPU", "Memory"]) | + +### 9.3.9 Network resource deletion + +This message is sent from IRSO to NMS to request a network resource release. + +Table 9-31 describes the detailed information of NetworkResourceDelete\_Request. + +**Table 9-31 – NetworkResourceDelete\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|----------------------|--------|-----------|-------------|--------------------------------------------------------------------------------------| +| Task ID | M | int | 1 | Unique identifier for this deletion task | +| Network resource ID | M | varchar | 1 | Target resource ID to delete | +| Deletion mode | O | enum | 0..1 | Graceful (default): Wait for active sessions
Forced: Immediate termination | +| Release dependencies | O | boolean | 0..1 | true: Release associated resources (e.g., IPs)
false: Keep dependencies (default) | + +This message is sent from NMS to IRSO to return the response for network resource release. + +Table 9-32 describes the detailed information of NetworkResourceDelete\_Response. + +**Table 9-32 – NetworkResourceDelete\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 200
400
404
500
423 | Indicates the success or failure of the network resource deletion.
200: Success
400: Invalid request
404: Resource not found
500: Internal error
423: Resource locked | +| Task ID | M | int | 1 | N/A | Unique identifier for this deletion task | +| Network resource ID | M | varchar | 1 | N/A | Deleted resource ID | +| Deletion time | M | string | 1 | N/A | Timestamp when deletion is completed | +| Released resources | O | array | 0..N | N/A | List of freed dependent resources (e.g., IPs, ports) | + +### 9.3.10 Cloud resource deletion + +This message is sent from IRSO to CMS to request a cloud resource release. + +Table 9-33 describes the detailed information of CloudResourceDelete\_Request. + +**Table 9-33 – CloudResourceDelete\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|------------------------------------------| +| Task ID | M | int | 1 | Unique identifier for this deletion task | +| Cloud resource ID | M | varchar | 1 | Target cloud resource ID to delete | + +**Table 9-33 – CloudResourceDelete\_Request** + +| Information element | Status | Data type | Cardinality | Description | +|---------------------|--------|-----------|-------------|-----------------------------------------------------------------------------| +| Deletion mode | O | enum | 0..1 | Graceful (default): Safe shutdown
Forced: Immediate termination | +| Storage handling | O | enum | 0..1 | Retain (default): Keep attached storage
Delete: Destroy associated disks | +| IP retention | O | enum | 0..1 | Keep (default): Retain Elastic IP
Released: Return to IP pool | +| Snapshot policy | O | boolean | 0..1 | true: Create final snapshot before deletion
false: No snapshot (default) | + +This message is sent from CMS to IRSO to return the response for cloud resource release. + +Table 9-34 describes the detailed information of CloudResourceDelete\_Response. + +**Table 9-34 – CloudResourceDelete\_Response** + +| Information element | Status | Data type | Cardinality | Code value | Description | +|---------------------|--------|-----------|-------------|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | num | 1 | 200
400
404
500
423
424 | Indicates the success or failure of the cloud resource deletion.
200: Success
400: Invalid request
404: Resource not found
500: Internal error
423: Resource locked
424: Dependency exists | +| Task ID | M | int | 1 | N/A | Echoes request Task ID | +| Cloud resource ID | M | varchar | 1 | N/A | Deleted resource ID | +| Deletion time | M | string | 1 | N/A | Timestamp when deletion is completed | +| Released resources | O | array | 0..N | N/A | Freed resources (e.g., IPs, security groups) | +| Retained resources | O | array | 0..N | N/A | Preserved resources (e.g., disk IDs, snapshots) | +| Snapshot ID | C | varchar | 0..1 | N/A | Final snapshot ID (if created) | + +# Bibliography + +[\[b-ITU-T F.743.16\]](#) + +Recommendation ITU-T F.743.16 (2022), *Requirements for communication resource management in intelligent visual surveillance systems.* + + + + + +## 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/Q/T-REC-Q.626-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.626-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..73366024a9d823e5eeda3ce5a0bbded0ab3ac10e --- /dev/null +++ b/marked/Q/T-REC-Q.626-198811-I_PDF-E/raw.md @@ -0,0 +1,358 @@ + + +![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 + +**Q.626** + +**INTERWORKING OF SIGNALLING SYSTEMS** + +--- + +**LOGIC PROCEDURES FOR OUTGOING +SIGNALLING SYSTEM R2** + +**ITU-T Recommendation Q.626** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.626 was published in Fascicle VI.6 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. + +# LOGIC PROCEDURES FOR OUTGOING SIGNALLING SYSTEM R2 + +![State overview diagram for outgoing Signalling System R2 showing states 00 through 10 and their transitions.](7055f51feb10ea4ea48b27c36f085286_img.jpg) + +``` + + graph LR + 00((00)) --> 01((01)) + 01 --> 02((02)) + 02 --> 03((03)) + 03 --> 04((04)) + 04 --> 05((05)) + 05 --> 06((06)) + 06 --> 07((07)) + 07 --> 08((08)) + 08 --> 09((09)) + 09 --> 10((10)) + 10 --> 00 + 00 --> 04 + 02 --> 04 + 03 --> 04 + 04 --> 07 + 05 --> 07 + 06 --> 07 + 07 --> 04 + 08 --> 04 + 09 --> 04 + 10 --> 04 + +``` + +CCITT-48630 + +State overview diagram for outgoing Signalling System R2 showing states 00 through 10 and their transitions. + +| State number | State description | Sheet reference | Timers running | +|--------------|------------------------------------------|-----------------|----------------| +| 00 | Idle | 1, 4 | | +| 01 | Wait for calling party's category (CPCI) | 1 | | +| 02 | Wait for country code indicator (CCI) | 1 | | +| 03 | Wait for echo suppressor indicator (ECI) | 1 | | +| 04 | Wait for backward signal | 2 | $t_1$ | +| 05 | Wait for address information | 3 | $t_2$ | +| 06 | Wait for Type B signal | 3 | $t_1$ | +| 07 | Wait for answer | 4 | | +| 08 | Answered | 4 | | +| 09 | Clear-back | 4 | | +| 10 | Clear-forward | 4 | | + +FIGURE 1/Q.626 +State overview diagram for outgoing Signalling System R2 + +## *Supervisory timers for outgoing Signalling System R2* + +$t_1 = 12-18$ s      Recommendation Q.476, § 5.5.1.1 + +$t_2 > 24$ s            Recommendation Q.476, § 5.5.1.2 + +### *Procedures not shown* + +The following procedures, not directly relevant to interworking, are not shown in the logic procedures: + +- Interrupt control procedures (analogue version). +- Seizing acknowledgement (digital version). +- Transmission fault procedures (digital version). +- $T_1$ time-out and abnormal release sequence (analogue version). +- Optional forward transfer. +- Blocking and unblocking sequences. + +FIGURE 2/Q.626 +Notes to outgoing Signalling System R2 + +Connector reference + +![Flowchart for Outgoing Signalling System R2. The process starts at 'Idle' (00), branches to 'Activate outgoing R2' or 'Activate outgoing R2 end-to-end signalling'. The latter leads to 'Seizing' and connector 1. The former leads to 'Wait for CPCI-FITE' (01), then to FITEs 9-19 or FITE 22. FITE 22 leads to 'Idle' (00). FITEs 9-19 lead to 'Wait for country code indicator' (02), then to FITE 2, 7, 8, 6, or 22. FITE 22 leads to 'Idle' (00). FITEs 7, 8, and 6 lead to 'Seizing', then to I-12, I-14, and I-11 respectively, all leading to connector 2. FITE 2 leads to 'Wait for echo-suppressor indicator' (03), then to FITE 4, 5, or 22. FITE 22 leads to 'Idle' (00). FITE 4 leads to 'Seizing', then to connector 3. FITE 5 leads to 'Idle' (00). Connector 3 leads to 'Which CPCI-FITE' decision. The decision branches to Language digits 1-5 (FITEs 9-13) or Discriminating digit 0 (FITEs 15, 16, 18, 19), all leading to connector 2.](2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg) + +``` + +graph TD + Idle00_1([00 Idle]) --> ActR2[Activate outgoing R2] + Idle00_1 --> ActR2E2S[Activate outgoing R2 end-to-end signalling] + ActR2E2S --> Seiz1[Seizing] + Seiz1 --> C1((1)) + ActR2 --> WaitCPCI([01 Wait for CPCI-FITE]) + WaitCPCI --> FITE9_19{FITEs 9, 10, 11, 12, 13, 15, 16, 18, 19} + WaitCPCI --> FITE22_1{FITE 22} + FITE22_1 --> Idle00_2([00 Idle]) + FITE9_19 --> WaitCC([02 Wait for country code indicator]) + WaitCC --> FITE2{FITE 2} + WaitCC --> FITE7{FITE 7} + WaitCC --> FITE8{FITE 8} + WaitCC --> FITE6{FITE 6} + WaitCC --> FITE22_2{FITE 22} + FITE22_2 --> Idle00_3([00 Idle]) + FITE7 --> Seiz7[Seizing] + Seiz7 --> I12[I-12] + FITE8 --> Seiz8[Seizing] + Seiz8 --> I14[I-14] + FITE6 --> Seiz6[Seizing] + Seiz6 --> I11[I-11] + I12 --> C2((2)) + I14 --> C2 + I11 --> C2 + FITE2 --> WaitEcho([03 Wait for echo-suppressor indicator]) + WaitEcho --> FITE4{FITE 4} + WaitEcho --> FITE5{FITE 5} + WaitEcho --> FITE22_3{FITE 22} + FITE22_3 --> Idle00_4([00 Idle]) + FITE4 --> Seiz4[Seizing] + Seiz4 --> C3((3)) + FITE5 --> Idle00_5([00 Idle]) + C3 --> WhichCPCI{Which CPCI-FITE} + WhichCPCI --> LD1{Language digit 1} + WhichCPCI --> LD2{Language digit 2} + WhichCPCI --> LD3{Language digit 3} + WhichCPCI --> LD4{Language digit 4} + WhichCPCI --> LD5{Language digit 5} + WhichCPCI --> DD0{Discriminating digit 0} + LD1 --> C2 + LD2 --> C2 + LD3 --> C2 + LD4 --> C2 + LD5 --> C2 + DD0 --> C2 + +``` + +Flowchart for Outgoing Signalling System R2. The process starts at 'Idle' (00), branches to 'Activate outgoing R2' or 'Activate outgoing R2 end-to-end signalling'. The latter leads to 'Seizing' and connector 1. The former leads to 'Wait for CPCI-FITE' (01), then to FITEs 9-19 or FITE 22. FITE 22 leads to 'Idle' (00). FITEs 9-19 lead to 'Wait for country code indicator' (02), then to FITE 2, 7, 8, 6, or 22. FITE 22 leads to 'Idle' (00). FITEs 7, 8, and 6 lead to 'Seizing', then to I-12, I-14, and I-11 respectively, all leading to connector 2. FITE 2 leads to 'Wait for echo-suppressor indicator' (03), then to FITE 4, 5, or 22. FITE 22 leads to 'Idle' (00). FITE 4 leads to 'Seizing', then to connector 3. FITE 5 leads to 'Idle' (00). Connector 3 leads to 'Which CPCI-FITE' decision. The decision branches to Language digits 1-5 (FITEs 9-13) or Discriminating digit 0 (FITEs 15, 16, 18, 19), all leading to connector 2. + +CCITT-50050 + +FIGURE 3/Q.626 (Sheet 1 of 4) +Outgoing Signalling System R2 + +Connector +reference + + +2 + +5 + +A + +10, 9 +5 + +3 +7, 8, 7 +10, 2 + +2 + +2 + +6 +2 + +4 + +Fascicle VI.6 - Rec. Q.626 + +3 + +Image: Flowchart of Outgoing Signalling System R2, Sheet 2 of 4 + +``` + + graph TD + Start2((2)) --> StopT2[Stop t2] + StopT2 --> StartT1[Start t1] + StartT1 -- "t1 = 12-18 s" --> WaitBackward{Wait for backward signal} + WaitBackward --> A1[A-1] + WaitBackward --> FITE1[FITE 1] + WaitBackward --> A3A5[A-3, A-5] + WaitBackward --> A4[A-4] + WaitBackward --> A8[A-8] + WaitBackward --> A15[A-15] + WaitBackward --> A14[A-14] + WaitBackward --> A9A10[A-9, A-10] + WaitBackward --> A_out((A))3 + + A1 --> ZDigit{Z-digit next} + ZDigit -- Yes --> Conn3_1((3))1 + ZDigit -- No --> ReqFITE1{Required FITE 1 stored} + ReqFITE1 -- Yes --> AddressSignal[Address signal] + ReqFITE1 -- No --> StopT1_2[Stop t1] + StopT1_2 --> StartT2_2[Start t2] + StartT2_2 -- "t2 > 24 s" --> Conn2_2((2))2 + StartT2_2 --> Conn6_3((6))3 + + FITE1 --> Conn5_2((5))2 + + A3A5 --> WhichCPCIFITE{Which CPCI-FITE} + WhichCPCIFITE -- "9-13, 15, 16" --> II7[II-7] + II7 --> WhichSignal{Which signal} + WhichSignal -- "A-3" --> StopT2_3[Stop t2] + StopT2_3 --> StartT1_3[Start t1] + StartT1_3 -- "t1 = 12-18 s" --> Conn4_3((4))3 + WhichSignal -- "A-5" --> Conn2_2_alt((2))2 + + A4 --> BITE12[BITE 12] + BITE12 --> Conn7_4((7))4 + Conn7_4 --> II9[II-9] + II9 --> WhichSignal + + A8 --> BITE2[BITE 2] + BITE2 --> Conn8_4((8))4 + Conn8_4 --> II8[II-8] + II8 --> WhichSignal + + A15 --> BITE11[BITE 11] + BITE11 --> Conn7_4_alt((7))4 + + A14 --> WhichESIFITE{Which ESI-FITE} + WhichESIFITE -- "5, 6, 8" --> I14[I-14] + I14 --> Conn2_2_alt2((2))2 + WhichESIFITE -- "4, 7" --> Conn10_2((10))2 + + A9A10 --> I12[I-12] + I12 --> Conn2_2_alt3((2))2 + +``` + +CCITT-50060 + +**FIGURE 3/Q.626 (Sheet 2 of 4)** +**Outgoing Signalling System R2** + +![Flowchart for Outgoing Signalling System R2, showing various signal paths and decision points.](191a4a245a7d36d03be9a990d0f758f5_img.jpg) + +The flowchart illustrates the Outgoing Signalling System R2. It begins at connector reference A, marked with a circled 'A' and subscript '2'. The main horizontal bus contains several signal paths: + + +- A-2**: 'Continue sending from digit (N-1)' leads to connector **10**2. +- A-7**: 'Continue sending from digit (N-2)' leads to connector **10**2. +- A-8**: 'Continue sending from digit (N-3)' leads to connector **10**2. +- A-11**: 'Continue sending from CCI' leads to a decision diamond 'Which CCI-FITE'. + - Path 7 leads to signal **I-12**. + - Paths 6 and 8 lead to signal **I-14**. +- A-12**: 'Continue sending from Z-digit' leads to connector **3**1. +- A-13**: Leads to a decision diamond 'Which response'. + - The 'Satellite' path leads to signal **I-14**. + - The 'Terrestrial or unknown' path leads to signal **I-13**. +- A-14**: Leads to a delay element $\bar{t}_1$ , then to signal **BITE 12**, which leads to connector **7**4. +- FITE 22**: Leads to signal **BITE 12**. + + Signals **I-12**, **I-14**, and **I-13** converge at connector **2**2. From here, the flow proceeds to connector reference 05 ('Wait for address information'). + + +- FITE 1**: 'Address signal' leads to connector **2**2. +- A-3**: Leads to connector **9**2. +- A-4**: Leads to signal **BITE 12**. +- A-6**: Leads to signal **BITE 2**, which leads to connector **8**4. +- A-15**: Leads to signal **BITE 11**. +- A-16**: Leads to a delay element $\bar{t}_2$ , then to signal **BITE 12**. +- FITE 22**: Leads to signal **BITE 12**. + + Signals **BITE 12**, **BITE 11**, and **BITE 2** converge at connector **7**4. From connector **2**2, the flow proceeds to connector reference 06 ('Wait for B-signal'). + + +- B-1** and **B-6**: Lead to signal **BITE 5**, which leads to connector **8**4. +- B-7**: Leads to signal **BITE 6**. +- B-2**, **B-9**, and **B-10**: Lead to signal **BITE 20**, which leads to connector **7**4. +- B-3**: Leads to signal **BITE 16**. +- B-4**, **B-11** to **B-15**: Lead to signal **BITE 13**. +- B-5**: Leads to signal **BITE 15**. +- B-8**: Leads to signal **BITE 17**. +- B-9**: Leads to a delay element $\bar{t}_1$ , then to signal **BITE 12**. +- FITE 22**: Leads to signal **BITE 12**. + + Signals **BITE 5**, **BITE 6**, **BITE 16**, **BITE 13**, **BITE 15**, **BITE 17**, and **BITE 12** all converge at connector **7**4. The diagram is signed 'CCITT - 50071' at the bottom right. + +Flowchart for Outgoing Signalling System R2, showing various signal paths and decision points. + +FIGURE 3/Q.626 (Sheet 3 of 4) + +## Outgoing Signalling System R2 + +Connector reference + +![State transition diagram for Outgoing Signalling System R2. The diagram shows a sequence of states and transitions with connector references on the left. States include Stop t1, Stop t2, Wait for answer (07), Answer, FITE 22, BITE 21, Answered (08), Clear-back, BITE 25, Clear-back (09), Stop t1, Stop t2, Clear-forward, Clear-forward (10), Release-guard, and Idle (00). Transitions are labeled with connector numbers and counts.](1956f44611abd5c3c41049836aa78ad8_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Stop_t1: 8 + Stop_t1 --> Stop_t2: 2, 3(2x) + Stop_t2 --> Wait_for_answer: 1 + state "07 Wait for answer" as Wait_for_answer + Wait_for_answer --> Answer + Wait_for_answer --> FITE_22_1: FITE 22 + FITE_22_1 --> [*]: 7, 4 + Answer --> BITE_21_1: BITE 21 + BITE_21_1 --> Answered: 11, 4 + state "08 Answered" as Answered + Answered --> Clear_back + Answered --> FITE_22_2: FITE 22 + FITE_22_2 --> [*]: 7, 4 + Clear_back --> BITE_25: BITE 25 + BITE_25 --> Clear_back_09: 09 Clear-back + state "09 Clear-back" as Clear_back_09 + Clear_back_09 --> Answer_2 + Clear_back_09 --> FITE_22_3: FITE 22 + FITE_22_3 --> Stop_t1_2: 7, 2(2x), 3(3x), 4(2x) + Stop_t1_2 --> Stop_t2_2: Stop t1 + Stop_t2_2 --> Clear_forward + Clear_forward --> Clear_forward_10: 10 Clear-forward + state "10 Clear-forward" as Clear_forward_10 + Clear_forward_10 --> Release_guard + Release_guard --> Idle: 00 Idle + Idle --> [*]: 11, 4 + +``` + +State transition diagram for Outgoing Signalling System R2. The diagram shows a sequence of states and transitions with connector references on the left. States include Stop t1, Stop t2, Wait for answer (07), Answer, FITE 22, BITE 21, Answered (08), Clear-back, BITE 25, Clear-back (09), Stop t1, Stop t2, Clear-forward, Clear-forward (10), Release-guard, and Idle (00). Transitions are labeled with connector numbers and counts. + +CCITT-50080 + +FIGURE 3/Q.626 (Sheet 4 of 4) +Outgoing Signalling System R2 \ No newline at end of file diff --git a/marked/Q/T-REC-Q.642-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.642-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9ae1397e2548e4f9627332abec8e4d4ccc54f181 --- /dev/null +++ b/marked/Q/T-REC-Q.642-198811-I_PDF-E/raw.md @@ -0,0 +1,243 @@ + + +![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** + +**Q.642** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**INTERWORKING OF SIGNALLING SYSTEMS** + +--- + +**LOGIC PROCEDURES FOR INTERWORKING +OF SIGNALLING SYSTEM No. 5 TO No. 6** + +**ITU-T Recommendation Q.642** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation Q.642 was published in Fascicle VI.6 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. + +# LOGIC PROCEDURES FOR INTERWORKING OF SIGNALLING SYSTEM No. 5 TO No. 6 + +![State overview diagram for interworking of Signalling System No. 5 to No. 6. The diagram shows seven states (00 to 06) in a sequence. State 00 is Idle, 01 is Wait for CPCI-FITE, 02 is Wait for ST, 03 is Wait for address-complete, 04 is Wait for answer, 05 is Answered, and 06 is Clear-back. Transitions are shown between 00-01, 01-02, 02-03, 03-04, 04-05, 05-06, and 06-00. There are also transitions from 01 to 03, 02 to 03, and 03 to 04. A feedback loop is shown from 06 back to 00.](7055f51feb10ea4ea48b27c36f085286_img.jpg) + +State overview diagram for interworking of Signalling System No. 5 to No. 6. The diagram shows seven states (00 to 06) in a sequence. State 00 is Idle, 01 is Wait for CPCI-FITE, 02 is Wait for ST, 03 is Wait for address-complete, 04 is Wait for answer, 05 is Answered, and 06 is Clear-back. Transitions are shown between 00-01, 01-02, 02-03, 03-04, 04-05, 05-06, and 06-00. There are also transitions from 01 to 03, 02 to 03, and 03 to 04. A feedback loop is shown from 06 back to 00. + +CCITT-48650 + +| State number | State description | Sheet reference | +|---------------------|---------------------------|------------------------| +| 00 | Idle | 1, 2, 3 | +| 01 | Wait for CPCI-FITE | 1 | +| 02 | Wait for ST | 2 | +| 03 | Wait for address-complete | 2 | +| 04 | Wait for answer | 3 | +| 05 | Answered | 3 | +| 06 | Clear-back | 3 | + +FIGURE 1/Q.642 +State overview diagram for interworking of Signalling System No. 5 to No. 6 + +*Procedure not shown* + +P1 - Procedure for repeat attempt. + +FIGURE 2/Q.642 +Notes to interworking of Signalling System No. 5 to No. 6 + +Connector reference + +![Flowchart for interworking of Signalling System No. 5 to No. 6. The process starts with 'Idle' (00), followed by 'Activate interworking No. 5/No. 6', then 'Wait for CPCI-FITE' (01). It then branches into FITE 1, FITEs 9-13, 17, and FITE 22. FITE 22 leads to 'Idle' (00). FITEs 9-13, 17 leads to 'Activate outgoing No. 6', then FITE 24. FITE 24 leads to a decision 'SPITE 22'. If 'No', it goes to FITE 2. If 'Yes', it goes to FITE 3. FITE 3 leads to a decision 'SPITE 20'. If 'No', it goes to FITE 20. If 'Yes', it goes to FITE 21. FITE 21 leads to a decision 'SPITE 21'. If 'No', it goes to FITE 4. If 'Yes', it goes to FITE 5. FITE 5 leads to a decision 'Which CPCI-FITE'. If '9-13', it goes to FITE 9-13. If '17', it goes to FITE 17. Both FITE 9-13 and FITE 17 lead to connector reference 1.](2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg) + +``` +graph TD; Idle00_1([00 Idle]) --> ActIntw[Activate interworking No. 5/No. 6]; ActIntw --> Wait01([01 Wait for CPCI-FITE]); Wait01 --> FITE1[/FITE 1/]; Wait01 --> FITEs91317[/FITEs 9-13, 17/]; Wait01 --> FITE22[/FITE 22/]; FITE22 --> Idle00_2([00 Idle]); FITEs91317 --> ActOutg[Activate outgoing No. 6]; ActOutg --> FITE24[/FITE 24/]; FITE24 --> SPITE22{SPITE 22}; SPITE22 -- No --> FITE2[/FITE 2/]; SPITE22 -- Yes --> FITE3[/FITE 3/]; FITE3 --> SPITE20{SPITE 20}; SPITE20 -- No --> FITE20[/FITE 20/]; SPITE20 -- Yes --> FITE21[/FITE 21/]; FITE21 --> SPITE21{SPITE 21}; SPITE21 -- No --> FITE4[/FITE 4/]; SPITE21 -- Yes --> FITE5[/FITE 5/]; FITE5 --> WhichCPCI{Which CPCI-FITE}; WhichCPCI -- 9-13 --> FITE913[/FITE 9-13/]; WhichCPCI -- 17 --> FITE17[/FITE 17/]; FITE913 --> Ref1((1)); FITE17 --> Ref1; Ref1 --> Ref2((2)); +``` + +Flowchart for interworking of Signalling System No. 5 to No. 6. The process starts with 'Idle' (00), followed by 'Activate interworking No. 5/No. 6', then 'Wait for CPCI-FITE' (01). It then branches into FITE 1, FITEs 9-13, 17, and FITE 22. FITE 22 leads to 'Idle' (00). FITEs 9-13, 17 leads to 'Activate outgoing No. 6', then FITE 24. FITE 24 leads to a decision 'SPITE 22'. If 'No', it goes to FITE 2. If 'Yes', it goes to FITE 3. FITE 3 leads to a decision 'SPITE 20'. If 'No', it goes to FITE 20. If 'Yes', it goes to FITE 21. FITE 21 leads to a decision 'SPITE 21'. If 'No', it goes to FITE 4. If 'Yes', it goes to FITE 5. FITE 5 leads to a decision 'Which CPCI-FITE'. If '9-13', it goes to FITE 9-13. If '17', it goes to FITE 17. Both FITE 9-13 and FITE 17 lead to connector reference 1. + +1 + +2 + +CCITT-50110 + +FIGURE 3/Q.642 (Sheet 1 of 3) +Interworking of Signalling System No. 5 to No. 6 + +![Flowchart for interworking of Signalling System No. 5 to No. 6. The process starts at connector 1, checks for more FITE 1 messages. If none, it waits for ST and then sends FITE 1, BITE 12, FITE 22, BITEs 2, 3, and BITE 15. FITE 22, BITEs 2, 3, and BITE 15 lead to connectors 2, 3, and 4 respectively. BITE 12 leads to BITE 8 and then to an Idle state. If more FITE 1 messages exist, it checks the country code. If present, it sends FITE 1 and checks ST-FITE. If not present, it omits the country code and returns to connector 1. If ST-FITE is not present, it returns to connector 1. If present, it waits for address-complete and then sends BITEs 2, 7, BITE 12, BITEs 14-17, 20, BITEs 9, 10, 19, and FITE 22. BITEs 2, 7 leads to BITE 27 and connector 5. BITE 12 leads to BITE 8. BITEs 14-17, 20 leads to BITE 28 and connector 4. BITEs 9, 10, 19 leads to a repeat attempt decision. If yes, it goes to P1. If no, it sends BITE 8. FITE 22 leads to connector 2. All BITE 8 messages lead to an Idle state.](f9a14fbfecbd7d059226cc93677d721b_img.jpg) + +Connector reference + +``` + +graph TD + C1((1)) -- "1, 2" --> D1{Any more FITE 1} + D1 -- No --> W02([02 Wait for ST]) + W02 --> FITE1_1[FITE 1] + W02 --> BITE12_1[BITE 12] + W02 --> FITE22_1[FITE 22] + W02 --> BITEs23_1[BITEs 2, 3] + W02 --> BITE15_1[BITE 15] + FITE22_1 --> C2((2) 3) + BITEs23_1 --> C3((3) 2) + BITE15_1 --> C4((4) 2) + BITE12_1 --> BITE8_1[BITE 8] + BITE8_1 --> Idle1([00 Idle]) + D1 -- Yes --> DCC{Country code FITE} + DCC -- Yes --> FITE1_2[FITE 1] + DCC -- No --> DSC{SPITE 22} + DSC -- Yes --> OCF[Omit country code FITE] + OCF --> C1_2((1) 2) + DSC -- No --> FITE1_2 + FITE1_2 --> DST{ST-FITE} + DST -- No --> C1_2 + DST -- Yes --> W03([03 Wait for address-complete]) + W03 --> BITEs27_2[BITEs 2, 7] + W03 --> BITE12_2[BITE 12] + W03 --> BITEs141720_2[BITEs 14-17, 20] + W03 --> BITEs91019_2[BITEs 9, 10, 19] + W03 --> FITE22_2[FITE 22] + BITEs27_2 --> BITE27_2[BITE 27] + BITE27_2 --> C5((5) 3) + BITE12_2 --> BITE8_2[BITE 8] + BITEs141720_2 --> BITE28_2[BITE 28] + BITE28_2 --> C4_2((4) 2) + BITEs91019_2 --> RA1{Repeat attempt} + RA1 -- Yes --> P1_1((P1)) + RA1 -- No --> BITE8_3[BITE 8] + FITE22_2 --> C2_2((2) 3) + BITE8_2 --> Idle2([00 Idle]) + BITE8_3 --> Idle3([00 Idle]) + BITE28_2 --> SPITE6[SPITE 6 Return appropriate tone] + SPITE6 --> Idle2 + +``` + +1 + +2, 3, 4 + +1 + +3, 4 + +2 + +5 + +CCITT - 50121 + +Flowchart for interworking of Signalling System No. 5 to No. 6. The process starts at connector 1, checks for more FITE 1 messages. If none, it waits for ST and then sends FITE 1, BITE 12, FITE 22, BITEs 2, 3, and BITE 15. FITE 22, BITEs 2, 3, and BITE 15 lead to connectors 2, 3, and 4 respectively. BITE 12 leads to BITE 8 and then to an Idle state. If more FITE 1 messages exist, it checks the country code. If present, it sends FITE 1 and checks ST-FITE. If not present, it omits the country code and returns to connector 1. If ST-FITE is not present, it returns to connector 1. If present, it waits for address-complete and then sends BITEs 2, 7, BITE 12, BITEs 14-17, 20, BITEs 9, 10, 19, and FITE 22. BITEs 2, 7 leads to BITE 27 and connector 5. BITE 12 leads to BITE 8. BITEs 14-17, 20 leads to BITE 28 and connector 4. BITEs 9, 10, 19 leads to a repeat attempt decision. If yes, it goes to P1. If no, it sends BITE 8. FITE 22 leads to connector 2. All BITE 8 messages lead to an Idle state. + +FIGURE 3/Q.642 (Sheet 2 of 3) +**Interworking of Signalling System No. 5 to No. 6** + +![SDL state transition diagram for interworking of Signalling System No. 5 to No. 6. It shows transitions between states 'Wait for answer', 'Answered', 'Clear-back', and 'Idle' based on BITE and FITE signals.](547f726730e589392f239257a833ede3_img.jpg) + +Connector +reference +5 + + + + +2 + +6 +5 + + + + + +2 + +7 +6 + + + + + +2 + + +7, 6 + +``` + +stateDiagram-v2 + direction TB + C5: (5) + S04: 04 Wait for answer + S05: 05 Answered + S06: 06 Clear-back + S00: 00 Idle + + [*] --> C5 + C5 --> S04: 2, 3 + + S04 --> BITE22_23 + BITE22_23 --> BITE22_Task + BITE22_Task --> S05 + + S04 --> BITEs10_12_19 + BITEs10_12_19 --> BITE8_Task + BITE8_Task --> S00 + + S04 --> FITE23_Input1 + FITE23_Input1 --> FITE23_Task1 + FITE23_Task1 --> C5_3: (5) 3 + + S04 --> FITE22_Input1 + FITE22_Input1 --> C2_3: (2) 3 + + S05 --> BITE25_Input + BITE25_Input --> BITE25_Task + BITE25_Task --> S06 + + S05 --> FITE23_Input2 + FITE23_Input2 --> FITE23_Task2 + FITE23_Task2 --> C6_3: (6) 3 + + S05 --> FITE22_Input2 + FITE22_Input2 --> C2_3 + + S06 --> FITE22_Input3 + FITE22_Input3 --> FITE22_Task3 + FITE22_Task3 --> S00 + + S06 --> FITE23_Input3 + FITE23_Input3 --> FITE23_Task3 + FITE23_Task3 --> C7_3: (7) 3 + + S06 --> BITE24_Input + BITE24_Input --> BITE22_Task4 + BITE22_Task4 --> C6_3_2: (6) 3 + +``` + +CCITT-50130 + +SDL state transition diagram for interworking of Signalling System No. 5 to No. 6. It shows transitions between states 'Wait for answer', 'Answered', 'Clear-back', and 'Idle' based on BITE and FITE signals. + +FIGURE 3/Q.642 (Sheet 3 of 3) +**Interworking of Signalling System No. 5 to No. 6** \ No newline at end of file diff --git a/marked/Q/T-REC-Q.694-199303-I_PDF-E/raw.md b/marked/Q/T-REC-Q.694-199303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..80dcc014420e2788ec80dcfe81a43b66682256d1 --- /dev/null +++ b/marked/Q/T-REC-Q.694-199303-I_PDF-E/raw.md @@ -0,0 +1,251 @@ + + +![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** + +**Q.694** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(03/93) + +# **INTERWORKING OF SIGNALLING SYSTEMS** --- + +**INTERWORKING OF SIGNALLING SYSTEMS – +LOGIC PROCEDURES FOR INTERWORKING +OF SIGNALLING SYSTEM No. 7 (ISUP) +TO R1** + +**ITU-T Recommendation Q.694** + +(Previously “CCITT Recommendation”) + +--- + +## FOREWORD + +The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecommunication Union. 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, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +ITU-T Recommendation Q.694 was prepared by the ITU-T Study Group XI (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993). + +## --- NOTES + +1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector. + +In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms "CCITT, CCIR or IFRB" or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure. + +2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## **INTERWORKING OF SIGNALLING SYSTEM – LOGIC PROCEDURES FOR INTERWORKING OF SIGNALLING SYSTEM No. 7 (ISUP) TO R1** + +*(Helsinki, 1993)* + +![State overview diagram showing states 00 through 07 with transitions. State 00 is Idle, 01 is Wait for call, 02 is Set up information/Wait for COT, 03 is Wait for address-complete, 04 is Wait for register deactivation, 05 is Wait for answer, 06 is Answered, and 07 is Clear-back. Transitions are shown as arrows between states, with a return path from 07 to 00.](69edc2887e907309499ac95b47ab6905_img.jpg) + +``` + + graph LR + 00((00)) --> 01((01)) + 01 --> 02((02)) + 02 --> 03((03)) + 03 --> 04((04)) + 04 --> 05((05)) + 05 --> 06((06)) + 06 --> 07((07)) + 07 --> 00 + +``` + +T1141640-92/d01 + +State overview diagram showing states 00 through 07 with transitions. State 00 is Idle, 01 is Wait for call, 02 is Set up information/Wait for COT, 03 is Wait for address-complete, 04 is Wait for register deactivation, 05 is Wait for answer, 06 is Answered, and 07 is Clear-back. Transitions are shown as arrows between states, with a return path from 07 to 00. + +| State number | State description | Sheet reference | +|---------------------|------------------------------------|------------------------| +| 00 | Idle | 1, 4 | +| 01 | Wait for call | 1 | +| 02 | Set up information
Wait for COT | 1 | +| 03 | Wait for address-complete | 2 | +| 04 | Wait for register deactivation | 3 | +| 05 | Wait for answer | 3 | +| 06 | Answered | 4 | +| 07 | Clear-back | 4 | + +FIGURE 1 /Q.694 +State overview diagram for interworking of Signalling System No. 7 (ISUP) to R1 + +### **Procedures not shown** + +P1 – No transit working is defined for R1 + +FIGURE 2/Q.694 +Note to the interworking of Signalling System No. 7 (ISUP) to R1 + +Connector reference + +![Flowchart for Interworking of Signalling System No. 7 (ISUP) to R1. The process starts at state '00 Idle', followed by 'Activate SS No. 7 (ISUP)/R1', state '01 Wait for call set up info', and 'FITE A Call set up info'. It then enters state '02 Wait for COT', which branches into 'FITE 1', 'FITE 25', 'FITE 24', and 'FITE Z'. 'FITE Z' leads to state '00 Idle'. The main path continues to 'SPITE 53 Analyse info received and generate appropriate BITE and FITE', 'Activate outgoing R1', and decision 'SPITE 22'. If 'Yes', it goes to connector 'P1' with a note 'No transit working is specified for Signalling System R1'. The main path continues to connector 'A'.](2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg) + +``` +graph TD; Idle00_1([00 Idle]) --> ActSS7[Activate SS No. 7 (ISUP)/R1]; ActSS7 --> Wait01([01 Wait for call set up info]); Wait01 --> FITEA[FITE A Call set up info]; FITEA --> Wait02([02 Wait for COT]); Wait02 --> FITE1[FITE 1]; Wait02 --> FITE25[FITE 25]; Wait02 --> FITE24[FITE 24]; Wait02 --> FITEZ[FITE Z]; FITEZ --> Idle00_2([00 Idle]); FITE1 --> SPITE53[SPITE 53 Analyse info received and generate appropriate BITE and FITE]; FITE25 --> SPITE53; FITE24 --> SPITE53; SPITE53 --> ActOutR1[Activate outgoing R1]; ActOutR1 --> SPITE22{SPITE 22}; SPITE22 -- Yes --> P1((P1)); P1 -.-> Note1[No transit working is specified for Signalling System R1]; SPITE22 --> A((A)); +``` + +T1 130780-91/d02 + +Flowchart for Interworking of Signalling System No. 7 (ISUP) to R1. The process starts at state '00 Idle', followed by 'Activate SS No. 7 (ISUP)/R1', state '01 Wait for call set up info', and 'FITE A Call set up info'. It then enters state '02 Wait for COT', which branches into 'FITE 1', 'FITE 25', 'FITE 24', and 'FITE Z'. 'FITE Z' leads to state '00 Idle'. The main path continues to 'SPITE 53 Analyse info received and generate appropriate BITE and FITE', 'Activate outgoing R1', and decision 'SPITE 22'. If 'Yes', it goes to connector 'P1' with a note 'No transit working is specified for Signalling System R1'. The main path continues to connector 'A'. + +A + +FIGURE 3/Q.694 (sheet 1 of 4) +Interworking of Signalling System No. 7 (ISUP) to R1 + +![Flowchart for interworking of ISUP to R1. It starts at connector A (1), goes to a decision 'Any more FITE 1?'. If 'No', it goes to 'Wait for address complete' (03). If 'Yes', it goes to 'Country code FITE?'. If 'Yes' to 'Country code FITE?', it goes to 'Omit country code FITE'. If 'No', it goes to 'FITE 1'. Both 'FITE 1' and 'Omit country code FITE' lead to connector 1, 2. The 'Wait for address complete' block leads to 'FITE 1' (connector 1, 2), 'BITE 26' (which leads to 'SPITE 53 (Table 1)' then 'BITE X' to connector 7, 3), and 'FITE Z' (connector 2, 4). A bracket labeled 'Artificial' is next to the 'Wait for address complete' block. A reference T1130790-91/d03 is at the bottom right.](f9a14fbfecbd7d059226cc93677d721b_img.jpg) + +Connector reference + +``` + +graph TD + A((A 1)) --> D{Any more FITE 1?} + D -- No --> W[03 Wait for address complete] + D -- Yes --> C{Country code FITE?} + C -- Yes --> O[Omit country code FITE] + C -- No --> F1[> FITE 1 <] + O --> C1((1 2)) + F1 --> C1 + W --> F1_out[> FITE 1 <] + W --> B26[> BITE 26 <] + W --> FZ[> FITE Z <] + F1_out --> C1 + B26 --> S53[SPITE 53 Table 1] + S53 --> BX[> BITE X <] + BX --> C7((7 3)) + FZ --> C2((2 4)) + T1130790-91/d03 + +``` + +Connector reference + +A + +1 + +1, 2 + +7 + +Flowchart for interworking of ISUP to R1. It starts at connector A (1), goes to a decision 'Any more FITE 1?'. If 'No', it goes to 'Wait for address complete' (03). If 'Yes', it goes to 'Country code FITE?'. If 'Yes' to 'Country code FITE?', it goes to 'Omit country code FITE'. If 'No', it goes to 'FITE 1'. Both 'FITE 1' and 'Omit country code FITE' lead to connector 1, 2. The 'Wait for address complete' block leads to 'FITE 1' (connector 1, 2), 'BITE 26' (which leads to 'SPITE 53 (Table 1)' then 'BITE X' to connector 7, 3), and 'FITE Z' (connector 2, 4). A bracket labeled 'Artificial' is next to the 'Wait for address complete' block. A reference T1130790-91/d03 is at the bottom right. + +FIGURE 3/Q.694 (sheet 2 of 4) + Interworking of Signalling System No. 7 (ISUP) to R1 + +![Flowchart showing the interworking of Signalling System No. 7 (ISUP) to R1. The flow starts at connector 7, goes through 'Wait for register deactivation' (04), then branches into 'BITE 27' and 'FITE Z'. 'FITE Z' leads to connector 2. 'BITE 27' leads to connector 3. From connector 3, it goes through 'Wait for answer' (05), then branches into 'BITE 22', 'FITE 23', and 'FITE Z'. 'FITE Z' leads to connector 2. 'BITE 22' leads to 'SPITE 53 (Table 2)', which then leads to 'BITE Y', which leads to connector 4. 'FITE 23' leads to connector 3. Connector 2 is labeled with reference 4. Connector 3 is labeled with reference 3. Connector 4 is labeled with reference 4. A code T1130810-91/d04 is present near connector 2.](547f726730e589392f239257a833ede3_img.jpg) + +Connector reference + +``` + +graph TD + 7((7)) --> 04[04 Wait for register deactivation] + 04 --> B27_1[BITE 27] + 04 --> FZ_1[FITE Z] + FZ_1 --> 2_1((2)) + B27_1 --> B27_2[BITE 27] + B27_2 --> 3_1((3)) + 3_1 --> 05[05 Wait for answer] + 05 --> B22[BITE 22] + 05 --> F23_1[FITE 23] + 05 --> FZ_2[FITE Z] + FZ_2 --> 2_2((2)) + B22 --> S53[SPITE 53 (Table 2)] + S53 --> BY[BITE Y] + BY --> 4((4)) + F23_1 --> F23_2[FITE 23] + F23_2 --> 3_2((3)) + 2_1 -.-> 4 + 3_1 -.-> 3 + 4 -.-> 4 + T1130810-91/d04 + +``` + +Flowchart showing the interworking of Signalling System No. 7 (ISUP) to R1. The flow starts at connector 7, goes through 'Wait for register deactivation' (04), then branches into 'BITE 27' and 'FITE Z'. 'FITE Z' leads to connector 2. 'BITE 27' leads to connector 3. From connector 3, it goes through 'Wait for answer' (05), then branches into 'BITE 22', 'FITE 23', and 'FITE Z'. 'FITE Z' leads to connector 2. 'BITE 22' leads to 'SPITE 53 (Table 2)', which then leads to 'BITE Y', which leads to connector 4. 'FITE 23' leads to connector 3. Connector 2 is labeled with reference 4. Connector 3 is labeled with reference 3. Connector 4 is labeled with reference 4. A code T1130810-91/d04 is present near connector 2. + +FIGURE 3/Q.694 (sheet 3 of 4) +**Interworking of Signalling System No. 7 (ISUP) to R1** + +![State transition diagram for the interworking of Signalling System No. 7 (ISUP) to R1. The diagram shows two main sections: 'Answered' and 'Clear-back'. The 'Answered' section starts with a circle containing '4' and '2 x 4', leading to a state '06 Answered'. From 'Answered', three transitions lead to 'BITE 25', 'FITE 23', and 'FITE Z'. 'BITE 25' leads to a state 'BITE 25' which then leads to state '07 Clear-back'. 'FITE 23' leads to a circle containing '4' and '4'. 'FITE Z' leads to a circle containing '2' and '4'. The 'Clear-back' section starts with state '07 Clear-back', which has three transitions leading to 'BITE 22', 'FITE 23', and 'FITE Z'. 'BITE 22' leads to a state 'BITE 24' which then leads to a circle containing '4' and '4'. 'FITE 23' leads to a circle containing '5' and '4'. 'FITE Z' leads to a state 'FITE 22' which then leads to state 'Idle'. There is also a circle containing '2' pointing to the 'FITE Z' transition in the 'Clear-back' section. Connector references are listed on the left: '4' at the top, '2' and '5' in the middle, and '4, 5' at the bottom.](fc46871d72c65d3381d9201646d23439_img.jpg) + +Connector reference + +``` + +stateDiagram-v2 + [*] --> Answered : 4, 2 x 4 + state "06 Answered" as Answered + Answered --> BITE_25_1 : BITE 25 + Answered --> FITE_23_1 : FITE 23 + Answered --> FITE_Z_1 : FITE Z + BITE_25_1 --> BITE_25_2 : BITE 25 + FITE_23_1 --> FITE_23_2 : FITE 23 + FITE_Z_1 --> FITE_Z_2 : FITE Z + BITE_25_2 --> Clear_back : 07 Clear-back + FITE_23_2 --> FITE_23_3 : FITE 23 + FITE_Z_2 --> FITE_Z_3 : FITE Z + Clear_back --> BITE_22 : BITE 22 + Clear_back --> FITE_23_4 : FITE 23 + Clear_back --> FITE_Z_4 : FITE Z + BITE_22 --> BITE_24 : BITE 24 + FITE_23_4 --> FITE_23_5 : FITE 23 + FITE_Z_4 --> FITE_22 : FITE 22 + BITE_24 --> BITE_24_out : 4 + FITE_23_5 --> FITE_23_6 : 5 + FITE_22 --> Idle : Idle + +``` + +Connector reference + +4 + +2 + +5 + +4 + +2 + +4, 5 + +T1130800-91/d05 + +State transition diagram for the interworking of Signalling System No. 7 (ISUP) to R1. The diagram shows two main sections: 'Answered' and 'Clear-back'. The 'Answered' section starts with a circle containing '4' and '2 x 4', leading to a state '06 Answered'. From 'Answered', three transitions lead to 'BITE 25', 'FITE 23', and 'FITE Z'. 'BITE 25' leads to a state 'BITE 25' which then leads to state '07 Clear-back'. 'FITE 23' leads to a circle containing '4' and '4'. 'FITE Z' leads to a circle containing '2' and '4'. The 'Clear-back' section starts with state '07 Clear-back', which has three transitions leading to 'BITE 22', 'FITE 23', and 'FITE Z'. 'BITE 22' leads to a state 'BITE 24' which then leads to a circle containing '4' and '4'. 'FITE 23' leads to a circle containing '5' and '4'. 'FITE Z' leads to a state 'FITE 22' which then leads to state 'Idle'. There is also a circle containing '2' pointing to the 'FITE Z' transition in the 'Clear-back' section. Connector references are listed on the left: '4' at the top, '2' and '5' in the middle, and '4, 5' at the bottom. + +FIGURE 3/Q.694 (sheet 4 of 4) +**Interworking of Signalling System No. 7 (ISUP) to R1** + +TABLE 1/Q.694 + +| Received BITE | | +|---------------------------------|----| +| Backward call indicators in ACM | 26 | +| Charging indicator | 10 | +| Called party's status | 00 | +| Called party's category | 00 | +| Interworking indicator | 1 | + +TABLE 1/Q.694 + +| Backward call indicators in ANM | +|----------------------------------------------------| +| ANM without backward call indicators is to be sent | \ No newline at end of file diff --git a/marked/Q/T-REC-Q.751.4-199805-I_PDF-E/raw.md b/marked/Q/T-REC-Q.751.4-199805-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2048a1827df8a8cdd2aff851fe5582795352af8c --- /dev/null +++ b/marked/Q/T-REC-Q.751.4-199805-I_PDF-E/raw.md @@ -0,0 +1,1178 @@ + + +![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** + +**Q.751.4** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(05/98) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of Signalling System No. 7 – Signalling +System No. 7 management + +--- + +**Network element information model for SCCP +accounting and accounting verification** + +ITU-T Recommendation Q.751.4 + +(Previously CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +# **SWITCHING AND SIGNALLING** + +| | | +|----------------------------------------------------------|--------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.849 | +| General | Q.700 | +| Message transfer part (MTP) | Q.701-Q.709 | +| Signalling connection control part (SCCP) | Q.711-Q.719 | +| Telephone user part (TUP) | Q.720-Q.729 | +| ISDN supplementary services | Q.730-Q.739 | +| Data user part | Q.740-Q.749 | +| Signalling System No. 7 management | Q.750-Q.759 | +| ISDN user part | Q.760-Q.769 | +| Transaction capabilities application part | Q.770-Q.779 | +| Test specification | Q.780-Q.799 | +| Q3 interface | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +# **ITU-T RECOMMENDATION Q.751.4** + +# **NETWORK ELEMENT INFORMATION MODEL FOR SCCP ACCOUNTING AND ACCOUNTING VERIFICATION** + +## **Summary** + +Measurements for SCCP accounting and accounting verification have been defined in Recommendation Q.752. The network element information model – based on Recommendations X.742 and Q.751.2 – for these measurements is contained in this Recommendation. + +### **Source** + +ITU-T Recommendation Q.751.4 was prepared by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 15th of May 1998. + +### **Keywords** + +Accounting, Measurements, network element information model, object model, OMAP, SCCP, TMN, Verification. + +## 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 | +| 4 | Abbreviations ..... | 2 | +| 5 | Conventions..... | 3 | +| 6 | Informal description of managed object classes ..... | 3 | +| 6.1 | Reused Managed Objects..... | 3 | +| 6.2 | Relation Notification/LogRecord/File..... | 3 | +| 6.3 | Diagrams ..... | 4 | +| 6.3.1 | Inheritance diagram..... | 4 | +| 6.3.2 | ER-Diagram for SCCP accounting and verification..... | 4 | +| 6.4 | Textual description..... | 5 | +| 6.5 | Tables ..... | 6 | +| 6.5.1 | Managed Objects classes common for SS7 accounting ..... | 7 | +| 6.5.2 | Managed Objects Classes for SCCP accounting ..... | 7 | +| 7 | Formal definitions..... | 10 | +| 7.1 | Formal definitions common for SS7 accounting..... | 10 | +| 7.2 | Formal definitions for SCCP accounting ..... | 10 | +| 7.2.1 | Managed Object Class Definitions..... | 10 | +| 7.2.2 | Package definitions ..... | 10 | +| 7.2.3 | Attribute definitions ..... | 12 | +| 7.2.4 | Name binding definitions ..... | 13 | +| 7.2.5 | Notification Definitions..... | 14 | +| 7.2.6 | Parameter Definitions..... | 15 | +| 7.2.7 | ASN.1 Definitions..... | 15 | + + + +# NETWORK ELEMENT INFORMATION MODEL FOR SCCP ACCOUNTING AND ACCOUNTING VERIFICATION + +(Geneva, 1998) + +## 1 Scope + +This Recommendation contains the network element information model which is necessary to manage network elements for accounting and accounting verification of SS7 SCCP traffic according to Recommendation Q.752. The model is based on the models defined in Recommendations Q.751.2 and X.742. SCCP Accounting options which are marked "f.f.s." in Recommendation Q.752 are not included. + +## 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 I.751 (1996), *Asynchronous transfer mode management of the network element view*. +- ITU-T Recommendation M.3100 (1995), *Generic network information model*. +- 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.751.2 (1997), *Network element management information model for the Signalling Connection Control Part*. +- ITU-T Recommendation Q.751.3 (1997), *Network element information model for MTP accounting*. +- CCITT Recommendation X.208 (1988), *Specification of Abstract Syntax Notation One (ASN.1)*. +- ITU-T Recommendation X.680 (1997) | ISO/IEC 8824-1:1998, *Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation*. +- ITU-T Recommendation X.711 (1997) | ISO/IEC 9596-1:1998, *Information technology – Open Systems Interconnection – Common Management Information Protocol: Specification*. +- CCITT Recommendation X.720 (1992) | ISO/IEC 10165-1:1993, *Information technology – Open Systems Interconnection – Structure of management information: Management information model*. +- 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.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 Recommendation X.722/Amd.1 (1995) | ISO/IEC 10165-4/Amd.1:1996, *Set by create and components registration*. +- ITU-T Recommendation X.723 (1993) | ISO/IEC 10165-5:1994, *Information technology – Open Systems Interconnection – Structure of management information: Generic management information*. +- CCITT Recommendation X.731 (1992) | ISO/IEC 10164-2:1992, *Information technology – Open Systems Interconnection – State management function*. + +- CCITT Recommendation X.733 (1992) | ISO/IEC 10164-4:1992, *Information technology – Open Systems Interconnection – Systems management: Alarm reporting function.* +- ITU-T Recommendation X.742 (1995) | ISO/IEC 10164-10:1995, *Information technology – Open Systems Interconnection – Systems management: Usage metering function for accounting purposes.* + +## 3 Terms and definitions + +For the purpose of this Recommendation, the following definitions apply. + +This Recommendation makes use of the following terms defined in Recommendation M.3010: + +- a) performance management; +- b) configuration management; +- c) fault management; +- d) Telecommunications Management Network (TMN). + +This Recommendation makes use of the following term defined in Recommendation X.700: + +- object instance. + +This Recommendation makes use of the following terms defined in Recommendation X.701: + +- a) managed object class; +- b) management information; +- c) notification. + +This Recommendation makes use of the following term defined in Recommendation X.710: + +- attribute. + +This Recommendation makes use of the following terms defined in Recommendation X.720: + +- a) inheritance; +- b) name binding; +- c) package; +- d) parameter; +- e) action; +- f) actual class; +- g) attribute group; +- h) behaviour; +- i) conditional package; +- j) instantiation; +- k) superclass. + +This Recommendation makes use of the following terms defined in ITU-T Rec. X.701 | ISO/IEC 10040: + +- a) managed object class; +- b) notification. + +## 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-------|--------------------------------------------------| +| ASN.1 | Abstract Syntax Notation One | +| ERD | Entity Relationship Diagram | +| GDMO | Guidelines for the Definition of Managed Objects | +| max | Maximum | +| MO | Managed Object | + +| | | +|------|-------------------------------------------------| +| MOC | Managed Object Class | +| MSU | Message Signal Unit | +| MTP | Message Transfer Part | +| NE | Network Element | +| OMAP | Operations, Maintenance and Administration Part | + +## 5 Conventions + +The Guidelines for the Definition of Managed Objects (GDMO), defined in Recommendation X.722, are used. In case of differences between the formal part (clause 7) and the informal parts of this Recommendation, the formal part is to be regarded as leading. + +If there are inconsistencies between the informal description, the formal definitions or conformance statements proformas, the formal definitions shall prevail. + +Throughout this Recommendation, the wording "The managed object class x ..." refers to a particular managed object class while the wording "An x ..." refers to an instance of the managed object class "x". + +Modelling of redundancy is avoided (e.g. relationships between managed objects are described in one MOC only; information which is obtainable via referenced instances of other information models are not repeated here). However, for some implementations, it may be useful or necessary to add some additional information to some managed object classes. + +# 6 Informal description of managed object classes + +This clause gives informal descriptions of the object model for SS7 SCCP accounting and accounting verification. + +### 6.1 Reused Managed Objects + +The following Table 1 gives an overview of all the Q.751.1, Q.751.2 and Q.751.3 object classes which are referenced by object classes of this information model. + +**Table 1/Q.751.4 – Reuse of Q.751.1, Q.751.2 and Q.751.3** + +| Referenced object class | Q.751.1/
Q.751.2/
Q.751.3 | +|-------------------------------------|---------------------------------| +| managedSwitchingElement | Q.751.1 | +| sccp | Q.751.2 | +| scrc | Q.751.2 | +| sccpLinkage | Q.751.2 | +| gtTranslator | Q.751.2 | +| gtRule | Q.751.2 | +| ss7AccountingAndVerificationControl | Q.751.3 | + +### 6.2 Relation Notification/LogRecord/File + +See Recommendation Q.751.3 + +### 6.3 Diagrams + +#### 6.3.1 Inheritance diagram + +![Inheritance diagram showing a hierarchy of object classes starting from 'X.721: top' branching into 'logRecord', 'sccpAccount', 'verification Translator', and 'terminatingAccount ClassForAccounting'. Further sub-classifications include 'eventLogRecord' under 'logRecord', 'verificationRule' under 'verification Translator', and 'terminatingAccount ClassForVerification' under 'terminatingAccount ClassForAccounting'. 'sccpAccountingLog Record' is shown as a sub-class of 'eventLogRecord'.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg) + +``` +graph TD; top["X.721: top"] --> logRecord["logRecord"]; top --> sccpAccount["sccpAccount"]; top --> vTranslator["verification Translator"]; top --> tAccount["terminatingAccount ClassForAccounting"]; logRecord --> eLogRecord["eventLogRecord"]; eLogRecord --> sccpAccountingLogRecord["sccpAccountingLog Record"]; vTranslator --> vRule["verificationRule"]; tAccount --> tAccountV["terminatingAccount ClassForVerification"]; +``` + +T1197290-97/d01 + +Inheritance diagram showing a hierarchy of object classes starting from 'X.721: top' branching into 'logRecord', 'sccpAccount', 'verification Translator', and 'terminatingAccount ClassForAccounting'. Further sub-classifications include 'eventLogRecord' under 'logRecord', 'verificationRule' under 'verification Translator', and 'terminatingAccount ClassForVerification' under 'terminatingAccount ClassForAccounting'. 'sccpAccountingLog Record' is shown as a sub-class of 'eventLogRecord'. + +Figure 1/Q.751.4 – Inheritance diagram + +#### 6.3.2 ER-Diagram for SCCP accounting and verification + +##### Explanation of arrows in the ERD + +Containment (full line): + +- Double arrows at the subordinate object class signify that several instances of it can be contained in one instance of the superior object class. + +Relation (dashed line): + +- A single arrow at the "targeted" object means that the "pointing" object references exactly one instance of the "target" object. +- Double arrows at the "targeted" object mean that the "pointing" object can reference several instances of the "target" object. A single arrow at the "pointing" object means that the "targeted" object is referenced by exactly one instance of the "pointing" object. +- Double arrows at the "pointing" object mean that the "targeted" object can be referenced by several instances of the "pointing" object. + +NOTE – SCCP Accounting options (selection based on SSN or SCCP Protocol Class) which are marked "f.f.s." in Recommendation Q.752 are not included. Extension for these options could be modelled as follows: Object classes defining the registration items must be defined, if it is not already existing in Recommendation Q.751.2. The attributes `selectionGroupSetForAccounting` and `selectionGroupSetForVerification` then point optionally to the corresponding object class. The attribute type for these attributes has to be extended for an additional optional pointer to the corresponding object class. + +![ER-Diagram for SCCP accounting and verification. The diagram shows a hierarchy of managed elements. At the top is 'managedElementR1', which branches into three boxes: 'Q.751.3: ss7AccountingAndVerificationControl', 'Q.751.2: sccp', and 'log'. 'Q.751.2: sccp' leads to 'Q.751.2: srcc'. 'log' leads to 'sccpAccountingLogRecord'. 'Q.751.2: srcc' branches into four boxes: 'sccpAccount', 'Q.751.2: sccpLinkage', 'terminatingAccountClassForAccounting', and 'Q.751.2: gtTranslator'. 'sccpAccount' has a bidirectional dashed arrow to 'Q.751.2: sccpLinkage' and two solid arrows pointing down to 'verificationTranslator' and 'terminatingAccountClassForVerification'. 'Q.751.2: gtTranslator' has a solid arrow pointing down to 'Q.751.2: gtRule'. 'terminatingAccountClassForAccounting' has a dashed arrow pointing to 'Q.751.2: gtRule'. 'verificationTranslator' has a solid arrow pointing down to 'verificationRule'. 'terminatingAccountClassForVerification' has a dashed arrow pointing to 'verificationRule'. At the bottom, a box contains 'sccpAccounting and/or sccpAccountingVerification', with a double-lined arrow pointing to it from the text 'sccpAccount generates (triggered by control) if corresponding selectionGroup-Set is not empty:'. Two dashed arrows labeled 'selectionGroupSet ForAccounting' and 'selectionGroupSet ForVerification' point from 'terminatingAccountClassForAccounting' and 'terminatingAccountClassForVerification' respectively to this text. A small code 'T1197300-97/d02' is in the bottom right of the diagram area.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +``` + +graph TD + managedElementR1[managedElementR1] --> Q7513[Q.751.3: +ss7AccountingAnd +VerificationControl] + managedElementR1 --> Q7512_scp[Q.751.2: +sccp] + managedElementR1 --> log[log] + Q7512_scp --> Q7512_src[Q.751.2: +srcc] + log --> sccpAccountingLogRecord[sccpAccounting +LogRecord] + Q7512_src --> sccpAccount[sccpAccount] + Q7512_src --> Q7512_scpLinkage[Q.751.2: +sccpLinkage] + Q7512_src --> terminatingAccountClassForAccounting[terminatingAccountClass +ClassForAccounting] + Q7512_src --> Q7512_gtTranslator[Q.751.2: +gtTranslator] + sccpAccount <--> Q7512_scpLinkage + sccpAccount --> verificationTranslator[verificationTranslator] + sccpAccount --> terminatingAccountClassForVerification[terminatingAccountClass +ClassForVerification] + Q7512_gtTranslator --> Q7512_gtRule[Q.751.2: +gtRule] + terminatingAccountClassForAccounting -.-> Q7512_gtRule + verificationTranslator --> verificationRule[verificationRule] + terminatingAccountClassForVerification -.-> verificationRule + sccpAccountingLogRecord --- T1197300_97_d02[T1197300-97/d02] + sccpAccountingLogRecord -.-> selectionGroupSetForAccounting[selectionGroupSet +ForAccounting] + selectionGroupSetForAccounting -.-> sccpAccountingAndOrVerification[sccpAccounting +and/or +sccpAccountingVerification] + terminatingAccountClassForAccounting -.-> selectionGroupSetForVerification[selectionGroupSet +ForVerification] + selectionGroupSetForVerification -.-> sccpAccountingAndOrVerification + sccpAccountingAndOrVerification -.-> sccpAccountingAndOrVerification_text[sccpAccount generates +(triggered by control) if +corresponding selectionGroup- +Set is not empty:] + +``` + +ER-Diagram for SCCP accounting and verification. The diagram shows a hierarchy of managed elements. At the top is 'managedElementR1', which branches into three boxes: 'Q.751.3: ss7AccountingAndVerificationControl', 'Q.751.2: sccp', and 'log'. 'Q.751.2: sccp' leads to 'Q.751.2: srcc'. 'log' leads to 'sccpAccountingLogRecord'. 'Q.751.2: srcc' branches into four boxes: 'sccpAccount', 'Q.751.2: sccpLinkage', 'terminatingAccountClassForAccounting', and 'Q.751.2: gtTranslator'. 'sccpAccount' has a bidirectional dashed arrow to 'Q.751.2: sccpLinkage' and two solid arrows pointing down to 'verificationTranslator' and 'terminatingAccountClassForVerification'. 'Q.751.2: gtTranslator' has a solid arrow pointing down to 'Q.751.2: gtRule'. 'terminatingAccountClassForAccounting' has a dashed arrow pointing to 'Q.751.2: gtRule'. 'verificationTranslator' has a solid arrow pointing down to 'verificationRule'. 'terminatingAccountClassForVerification' has a dashed arrow pointing to 'verificationRule'. At the bottom, a box contains 'sccpAccounting and/or sccpAccountingVerification', with a double-lined arrow pointing to it from the text 'sccpAccount generates (triggered by control) if corresponding selectionGroup-Set is not empty:'. Two dashed arrows labeled 'selectionGroupSet ForAccounting' and 'selectionGroupSet ForVerification' point from 'terminatingAccountClassForAccounting' and 'terminatingAccountClassForVerification' respectively to this text. A small code 'T1197300-97/d02' is in the bottom right of the diagram area. + +Figure 2/Q.751.4 – ER-Diagram for SCCP accounting and verification + +### 6.4 Textual description + +The information model presented in Figure 1 contains four SCCP accounting and accounting verification specific objects: + +*sccpAccount, verificationTranslator, verificationRule, terminatingAccountClassForAccounting and terminatingAccountClassForVerification (ss7AccountingAndVerificationControl)* + +is common for MTP and SCCP Accounting and Accounting Verification and is defined in Recommendation Q.751.3). + +An *sccpAccount* represents a set of remote sccp nodes (represented by sccpLinkages) belonging to one operator for which accounting/accounting verification may be done collectively. For each sccpAccount, the accountable traffic may be recorded into different counters according to certain selection criteria that are different for accounting/accounting verification. The counters are represented by a set of references to *terminatingAccountClass (ForAccounting/Verification)* instances. + +A **terminatingAccountClassForAccounting** contained in *scrc* groups a number of *gtRules* for which the same tariff applies for accounting purposes. A reference to an instance of this class in *sccpAccount* represents an accounting counter with a specific tariff valid for the affected operator. + +- This containment in *scrc* means that the grouping that applies for accounting is identical for all remote operators SCCP Accounting bills are sent to. Prices associated with the accountclasses are however not restricted by this rule. +- The fact that the groupings apply for all *sccpAccounts* also means that the *gtRules* belong to only one *terminatingAccountClassForAccounting*. Otherwise, a unique selection of a tariff/counter would not be possible. + +A **terminatingAccountClassForVerification** contained in an *sccpAccount* groups a number of *verificationRules* for which the same tariff applies for accounting verification purposes. A reference to an instance of this class in *sccpAccount* represents a verification counter with a specific tariff valid for the affected operator. + +- This containment in *sccpAccount* means that the grouping only applies for the operator specified by the *sccpAccount*. The *verificationRules* belonging to this tariff (*terminatingAccountClassForVerification*) shall also belong to this operator, i.e. the superior *verificationTranslator* shall be contained in the same *sccpAccount*. +- Within the scope of an *sccpAccount*, the *verificationTranslators* also belong to only one *terminatingAccountClassForVerification*. + +A *gtTranslator* is used during the global title translation process for routing purposes. The **verificationTranslator** has the same purpose during the global title analysis process for accounting verification purposes. For each *sccpAccount*, a set of *verificationTranslator* are to be defined. + +A *gtRule* is used during the global title translation process for routing purposes. The **verificationRule** has the same purpose during the global title analysis process for accounting verification purposes. For each *sccpAccount*, a set of *verificationRules* are to be defined. These rules are assigned to a *terminatingAccountClassForVerification* representing a verification counter for the affected operator. + +### 6.5 Tables + +In these tables, (I), (M) and (C) are used with the following meaning: + +- (I) This element is inherited from a superclass. +- (M) This element is mandatory. +- (Cn) Conditional, n specifies the number of the condition; explanation of it below the tables. +- (O) Optional (condition "if the instance supports it" or similar). + +This signification is only done at the package level. + +The possible operations on objects and attributes are specified by: + +- (Cr) CREATE +- (WrOI) WITH REFERENCE OBJECT INSTANCE +- (Del) DELETE +- (oinco) ONLY-IF-NO-CONTAINED-OBJECTS +- (G) GET +- (SBC) SET BY CREATE +- (R) REPLACE +- (A-Rm) ADD-REMOVE +- (d) DEFAULT VALUE is defined for the attribute +- (dr) DEFAULT VALUE DERIVATION RULE is defined for the attributes + +#### 6.5.1 Managed Objects classes common for SS7 accounting + +For the explanations of the object class and the attributes defined in this Recommendation, see their behaviour descriptions in the formal definition section. + +For objectClass ss7AccountingAndVerificationControl, see Recommendation Q.751.3. + +#### 6.5.2 Managed Objects Classes for SCCP accounting + +##### 6.5.2.1 sccpAccount + +Table 2/Q.751.4 – sccpAccount + +| sccpAccount (Cr, Del oinco) | | | +|----------------------------------------------------------------------------|------------------------------------------------|---------| +| Attributes | Notifications | Actions | +| sccpAccountPackage (M) | | | +| sccpAccountId (G, SBC) | | | +| sccpLinkageSet (G, SBC, A-Rm) | | | +| operatorName (G, SBC) | | | +| selectionGroupSetForAccounting (G, R, A-Rm, i) | | | +| selectionGroupSetForVerification (G, R, A-Rm, i) | | | +| "ITU-T Rec. M.3100 (1995)":objectManagementNotificationsPackage (M) | | | +| | "ITU-T Rec. X.721 (1992)":attributeValueChange | | +| | "ITU-T Rec. X.721 (1992)":objectCreation | | +| | "ITU-T Rec. X.721 (1992)":objectDeletion | | +| "ITU-T Rec. Q.751.3 (1997)":controlPointerPackage (O) | | | +| "ITU-T Rec. Q.751.3 (1997)":controlPointer (G, SBC) | | | +| "ITU-T Rec. Q.751.3 (1997)":measurementControlStatusPackage (O) | | | +| "ITU-T Rec. Q.751.3 (1997)":measurementControlStatus (G, SBC) | | | +| sccpAccountingNotificationsPackage (O) | | | +| | sccpAccounting | | +| | sccpAccountingVerification | | +| "ITU-T Rec. X.721 (1992)":topPackage (M,I) | | | +| objectClass (G) | | | +| nameBinding (G) | | | +| "ITU-T Rec. X.721 (1992)":packagesPackage (C1,I) | | | +| packages (G) | | | +| "ITU-T Rec. X.721 (1992)":allomorphicPackage (C2,I) | | | +| allomorphs (G) | | | +| C1 Present if any registered package has been instantiated. | | | +| C2 Present if allomorphism is supported. | | | + +##### 6.5.2.2 sccpAccountingLogRecord + +This non-instantiable object class is defined to formally supply the possibility to write the sccpAccounting and/or sccpAccountingVerification notifications into a log. + +##### 6.5.2.3 terminatingAccountClassForAccounting + +Table 3/Q.751.4 – terminatingAccountClassForAccounting + +| terminatingAccountClassForAccounting (Cr WrOI, Del) | | | +|---------------------------------------------------------------------------------------------------------|------------------------------------------------|----------------| +| Attributes | Notifications | Actions | +| terminatingAccountClassForAccountingPackage (M) | | | +| terminatingAccountClassForAccountingId
(G, SBC) | | | +| ruleSet (G, SBC, A-Rm) | | | +| "ITU-T Rec. M.3100 (1995)":objectManagementNotificationsPackage (M) | | | +| | "ITU-T Rec. X.721 (1992)":attributeValueChange | | +| | "ITU-T Rec. X.721 (1992)":objectCreation | | +| | "ITU-T Rec. X.721 (1992)":objectDeletion | | +| "ITU-T Rec. X.721 (1992)":topPackage (M,I) | | | +| objectClass (G) | | | +| nameBinding (G) | | | +| "ITU-T Rec. X.721 (1992)":packagesPackage (C1,I) | | | +| packages (G) | | | +| "ITU-T Rec. X.721 (1992)":allomorphicPackage (C2,I) | | | +| allomorphs (G) | | | +| C1 Present if any registered package has been instantiated.
C2 Present if allomorphism is supported. | | | + +##### 6.5.2.4 terminatingAccountClassForVerification + +Table 4/Q.751.4 – terminatingAccountClassForVerification + +| terminatingAccountClassForVerification (Cr WrOI, Del) | | | +|---------------------------------------------------------------------------------------------------------|------------------------------------------------|----------------| +| Attributes | Notifications | Actions | +| terminatingAccountClassForVerificationPackage (M) | | | +| terminatingAccountClassForVerificationId
(G, SBC) | | | +| ruleSet (G, SBC, A-Rm) | | | +| "ITU-T Rec. M.3100 (1995)":objectManagementNotificationsPackage (M) | | | +| | "ITU-T Rec. X.721 (1992)":attributeValueChange | | +| | "ITU-T Rec. X.721 (1992)":objectCreation | | +| | "ITU-T Rec. X.721 (1992)":objectDeletion | | +| "ITU-T Rec. X.721 (1992)":topPackage (M,I) | | | +| objectClass (G) | | | +| nameBinding (G) | | | +| "ITU-T Rec. X.721 (1992)":packagesPackage (C1,I) | | | +| packages (G) | | | +| "ITU-T Rec. X.721 (1992)":allomorphicPackage (C2,I) | | | +| allomorphs (G) | | | +| C1 Present if any registered package has been instantiated.
C2 Present if allomorphism is supported. | | | + +##### 6.5.2.5 verificationRule + +Table 5/Q.751.4 – verificationRule + +| verificationRule (Cr WrOI, Del) | | | +|----------------------------------------------------------------------------|------------------------------------------------|---------| +| Attributes | Notifications | Actions | +| verificationRulePackage (M) | | | +| verificationRuleId (G, SBC) | | | +| ITU-T Rec. Q.751.2 (1997):gtAddressInformation (G, R) | | | +| ITU-T Rec. Q.751.2 (1997):gtEncodingScheme (G, SBC) | | | +| "ITU-T Rec. M.3100 (1995)":objectManagementNotificationsPackage (M) | | | +| | "ITU-T Rec. X.721 (1992)":attributeValueChange | | +| | "ITU-T Rec. X.721 (1992)":objectCreation | | +| | "ITU-T Rec. X.721 (1992)":objectDeletion | | +| "ITU-T Rec. X.721 (1992)":topPackage (M,I) | | | +| objectClass (G) | | | +| nameBinding (G) | | | +| "ITU-T Rec. X.721 (1992)":packagesPackage (C1,I) | | | +| packages (G) | | | +| "ITU-T Rec. X.721 (1992)":allomorphicPackage (C2,I) | | | +| allomorphs (G) | | | +| C1 Present if any registered package has been instantiated. | | | +| C2 Present if allomorphism is supported. | | | + +##### 6.5.2.6 verificationTranslator + +Table 6/Q.751.4 – verificationTranslator + +| verificationTranslator (Cr WrOI, Del) | | | +|----------------------------------------------------------------------------|------------------------------------------------|---------| +| Attributes | Notifications | Actions | +| verificationTranslatorPackage (M) | | | +| verificationTranslatorId (G, SBC) | | | +| ITU-T Rec. Q.751.2 (1997):gtIndicator (G, SBC) | | | +| gtNatureOfAddressSet (G, R, A-Rm) | | | +| gtNumberingPlanSet (G, R, A-Rm) | | | +| gtTranslationTypeSet (G, R, A-Rm) | | | +| "ITU-T Rec. M.3100 (1995)":objectManagementNotificationsPackage (M) | | | +| | "ITU-T Rec. X.721 (1992)":attributeValueChange | | +| | "ITU-T Rec. X.721 (1992)":objectCreation | | +| | "ITU-T Rec. X.721 (1992)":objectDeletion | | +| "ITU-T Rec. X.721 (1992)":topPackage (M,I) | | | +| objectClass (G) | | | +| nameBinding (G) | | | +| "ITU-T Rec. X.721 (1992)":packagesPackage (C1,I) | | | +| packages (G) | | | +| "ITU-T Rec. X.721 (1992)":allomorphicPackage (C2,I) | | | +| allomorphs (G) | | | +| C1 Present if any registered package has been instantiated. | | | +| C2 Present if allomorphism is supported. | | | + +## 7 Formal definitions + +### 7.1 Formal definitions common for SS7 accounting + +These definitions are defined in Recommendation Q.751.3 and are reused. + +### 7.2 Formal definitions for SCCP accounting + +#### 7.2.1 Managed Object Class Definitions + +sccpAccount MANAGED OBJECT CLASS +DERIVED FROM "ITU-T Rec. X.721 (1992) | ISO/IEC 10165-2:1992":top; +CHARACTERIZED BY +"ITU-T Rec. M.3100 (1995)":objectManagementNotificationsPackage, +sccpAccountPackage ; +CONDITIONAL PACKAGES +"ITU-T Rec. Q.751.3 (1997)":controlPointerPackage PRESENT IF "the instance supports it", +"ITU-T Rec. Q.751.3 (1997)":measurementControlStatusPackage PRESENT IF "the instance +supports it", +sccpAccountingNotificationsPackage PRESENT IF "the instance supports it"; +REGISTERED AS {sccpAccount-OOi}; + +sccpAccountingLogRecord MANAGED OBJECT CLASS +DERIVED FROM "ITU-T Rec. X.735 (1991)":eventLogRecord; +CHARACTERIZED BY +sccpAccountingLogRecordPackage; +REGISTERED AS {sccpAccountingLogRecord-OOi}; + +terminatingAccountClassForAccounting MANAGED OBJECT CLASS +DERIVED FROM "ITU-T Rec. X.721 (1992) | ISO/IEC 10165-2:1992":top; +CHARACTERIZED BY +terminatingAccountClassForAccountingPackage, +"ITU-T Rec. M.3100 (1995)":objectManagementNotificationsPackage ; +REGISTERED AS {terminatingAccountClassForAccounting-OOi}; + +terminatingAccountClassForVerification MANAGED OBJECT CLASS +DERIVED FROM "ITU-T Rec. X.721 (1992) | ISO/IEC 10165-2:1992":top; +CHARACTERIZED BY +terminatingAccountClassForVerificationPackage, +"ITU-T Rec. M.3100 (1995)":objectManagementNotificationsPackage ; +REGISTERED AS {terminatingAccountClassForVerification-OOi}; + +verificationRule MANAGED OBJECT CLASS +DERIVED FROM "ITU-T Rec. X.721 (1992) | ISO/IEC 10165-2:1992":top; +CHARACTERIZED BY +verificationRulePackage, +"ITU-T Rec. M.3100 (1995)":objectManagementNotificationsPackage ; +REGISTERED AS {verificationRule-OOi}; + +verificationTranslator MANAGED OBJECT CLASS +DERIVED FROM "ITU-T Rec. X.721 (1992) | ISO/IEC 10165-2:1992":top; +CHARACTERIZED BY +verificationTranslatorPackage, +"ITU-T Rec. M.3100 (1995)":objectManagementNotificationsPackage ; +REGISTERED AS {verificationRule-OOi}; + +#### 7.2.2 Package definitions + +sccpAccountPackage PACKAGE +BEHAVIOUR sccpAccountPackageBehaviour BEHAVIOUR DEFINED AS +"The sccpAccount managed object allows by means of the attribute sccpLinkageSet to define a set (at least one) of remote nodes for which SCCP accounting/verification can be done collectively, because they are belonging to the same operator. All sccpLinkageSets defined by sccpAccounts shall be disjunct. + +The selectionGroupSetForAccounting refers to terminatingAccountClassForAccounting instances contained in scrc, i.e. the accounting is independent of the operator (Other selection items for SCCP accounting are for further study). The selectionGroupSetForVerification refers to terminatingAccountClassForVerification instances contained in the same sccpAccount that the selectionGroupSetForVerification attribute belongs to, i.e. the verification is operator dependent. Each selectionGroup entry shall be unique in these attributes. For each selectionGroup it is counted separately. Each counter information contains the number of GTs, the number of octets, an eventual data problem and the selectionGroup for which was counted. The counters are not readable but only available in the notification data. + +If all counters for verification or accounting should still be zero at the end of the measurement, the corresponding notification should be generated regardless of that in order to provide a measure against notification loss. + +Two different notifications, one for accounting, one for accounting verification containing the measurement results might be generated by this one object. If a selectionGroupSet is empty, then this means, that accounting resp. verification is not performed for the adjacent operator. In this case there is no notification for accounting resp. verification. + +The following rules apply for set requests on the sccpLinkageSet, selectionGroupSetForAccounting and selectionGroupSetForVerification attributes: The addressed sccpLinkages in the sccpLinkageSet attribute may only appear in one sccpAccount. The selectionGroups in the selectionGroupSetForVerification shall refer to terminatingAccountClassForVerification instances contained in this sccpAccount instance. The selectionGroups in the selectionGroupSetForAccounting shall refer to terminatingAccountClass instancesForAccounting.";; + +##### ATTRIBUTES + +sccpAccountId GET SET-BY-CREATE, +sccpLinkageSet GET SET-BY-CREATE ADD-REMOVE, +operatorName GET SET-BY-CREATE, +selectionGroupSetForAccounting INITIAL VALUE selectionGroupSetInitial GET REPLACE, +selectionGroupSetForVerification INITIAL VALUE selectionGroupSetInitial GET REPLACE; + +REGISTERED AS {sccpAccountPackage-POi}; + +##### sccpAccountingLogRecordPackage PACKAGE + +###### BEHAVIOUR sccpAccountingLogRecordPackageBehaviour BEHAVIOUR DEFINED AS + +"The sccpAccountingLogRecord managed object is used to represent logged information that resulted from the sccpAccounting or sccpAccountingVerification notifications.";; + +##### ATTRIBUTES + +endOfMeasurementTime GET, +sccpLinkageSet GET, +sccpAccCounterDataSequence GET; + +REGISTERED AS {sccpAccountingLogRecordPackage-POi}; + +##### sccpAccountingNotificationsPackage PACKAGE + +###### BEHAVIOUR sccpAccountingNotificationsPackageBehaviour BEHAVIOUR DEFINED AS + +"The sccpAccountingLogRecord managed object is used to represent logged information that resulted from the sccpAccounting or sccpAccountingVerification notifications.";; + +##### NOTIFICATIONS + +sccpAccounting, +sccpAccountingVerification; + +REGISTERED AS {sccpAccountingNotificationsPackage-POi}; + +##### terminatingAccountClassForAccountingPackage PACKAGE + +###### BEHAVIOUR terminatingAccountClassForAccountingBehaviour BEHAVIOUR DEFINED AS + +"The terminatingAccountClassForAccounting instances contain a set of gtRules with the same tariff. The terminating account class for accounting is identified by the terminatingAccountClassForAccountingId. An instance of this class represents the destination information item involved in accounting. + +The following restrictions apply for set requests on the ruleSet attribute: A rule may be contained in only one ruleSet within the scope of the superior scrc.";; + +##### ATTRIBUTES + +terminatingAccountClassForAccountingId GET SET-BY-CREATE, +ruleSet GET SET-BY-CREATE ADD-REMOVE; + +REGISTERED AS {terminatingAccountClassForAccountingPackage-POi}; + +##### terminatingAccountClassForVerificationPackage PACKAGE + +###### BEHAVIOUR terminatingAccountClassForVerificationBehaviour BEHAVIOUR DEFINED AS + +"The terminatingAccountClassForVerification instances contain a set of verificationRules with the same tariff. The terminating account class for verification is identified by the terminatingAccountClassForAccountingId. An instance of this class represents the destination information item involved in accounting verification. + +The following restrictions apply for set requests on the ruleSet attribute: A rule may be contained in only one ruleSet within the scope of a superior sccpAccount.";; + +##### ATTRIBUTES + +terminatingAccountClassForVerificationId GET SET-BY-CREATE, +ruleSet GET SET-BY-CREATE ADD-REMOVE; + +REGISTERED AS {terminatingAccountClassForVerificationPackage-POi}; + +##### verificationRulePackage PACKAGE + +###### BEHAVIOUR verificationRuleBehaviour BEHAVIOUR DEFINED AS + +"The verificationRules are selected during the translation of outgoing global titles for accounting verification purposes. As the translation mechanism is the same as the translation for routing purposes, the same selection attributes are applicable: gtAddressInformation and possibly the encodingScheme. If there is no matching verificationRule found, no terminatingAccountClassForVerification can be selected. In this case, no accounting verification counter is to be incremented.";; + +##### ATTRIBUTES + +verificationRuleId GET SET-BY-CREATE, +ITU-T Rec. Q.751.2 (1997):gtAddressInformation GET-REPLACE, +ITU-T Rec. Q.751.2 (1997):gtEncodingScheme GET SET-BY-CREATE; + +REGISTERED AS {verificationRulePackage-POi}; + +##### verificationTranslatorPackage PACKAGE + +###### BEHAVIOUR verificationTranslatorBehaviour BEHAVIOUR DEFINED AS + +"The verificationTranslators are selected during the translation of outgoing global titles for accounting verification purposes. As the translation mechanism is the same as the translation for routing purposes, the same selection attributes are applicable: gtIndicator, gtNatureOfAddress, gtNumberingPlan and gtTranslationType. No single-valued address attributes are chosen however. This is to avoid that identical sets of verificationRule-sets have to be created in case of identical routing for a set of address parameter values. A verification translator, if selected, specifies a set of contained verificationRules that apply for a certain outgoing global title.";; + +##### ATTRIBUTES + +verificationTranslatorId GET SET-BY-CREATE, +ITU-T Rec. Q.751.2 (1997):gtIndicator GET SET-BY-CREATE, +gtNatureOfAddressSet GET-REPLACE ADD-REMOVE, +gtNumberingPlanSet GET-REPLACE ADD-REMOVE, +gtTranslationTypeSet GET-REPLACE ADD-REMOVE; + +REGISTERED AS {verificationTranslatorPackage-POi}; + +#### 7.2.3 Attribute definitions + +##### ruleSet ATTRIBUTE + +WITH ATTRIBUTE SYNTAX SccpAccountingDefinedTypesModule.RuleSet; + +MATCHES FOR EQUALITY, SET-COMPARISON, SET-INTERSECTION; + +###### BEHAVIOUR gtRuleSetBehaviour BEHAVIOUR DEFINED AS + +"The ruleSet attribute refers to a set (at least one) of gtRules or verificationRules, all belonging to the same terminating account class. + +A set request is rejected if + +a rule would be referenced which is already referenced by another + +terminatingAccountClass(ForAccounting/Verification) contained in the same superior object class instance.";; + +REGISTERED AS {ruleSet-AOi}; + +##### sccpAccountId ATTRIBUTE + +WITH ATTRIBUTE SYNTAX SccpAccountingDefinedTypesModule.SimpleNameType; + +MATCHES FOR EQUALITY; + +###### BEHAVIOUR sccpAccountIdBehaviour BEHAVIOUR DEFINED AS + +"The sccpAccountId is the naming attribute of the sccpAccount managed object.";; + +REGISTERED AS {sccpAccountId-AOi}; + +##### sccpLinkageSet ATTRIBUTE + +WITH ATTRIBUTE SYNTAX SccpAccountingDefinedTypesModule.SccpLinkageSet; + +MATCHES FOR EQUALITY, SET-COMPARISON, SET-INTERSECTION; + +###### BEHAVIOUR sccpLinkageSetBehaviour BEHAVIOUR DEFINED AS + +"The sccpLinkageSet refers to a set (at least one) of sccpLinkages, identifying an operator.";; + +REGISTERED AS {sccpLinkageSet-AOi}; + +##### terminatingAccountClassForAccountingId ATTRIBUTE + +WITH ATTRIBUTE SYNTAX SccpAccountingDefinedTypesModule.SimpleNameType; + +MATCHES FOR EQUALITY; + +###### BEHAVIOUR terminatingAccountClassForAccountingIdBehaviour BEHAVIOUR DEFINED AS + +"The terminatingAccountClassForAccountingId is the naming attribute of the terminatingAccountClassForAccounting managed object.";; + +REGISTERED AS {terminatingAccountClassForAccountingId-AOi}; + +terminatingAccountClassForVerificationId ATTRIBUTE +WITH ATTRIBUTE SYNTAX SccpAccountingDefinedTypesModule.SimpleNameType; +MATCHES FOR EQUALITY; +BEHAVIOUR terminatingAccountClassForVerificationIdBehaviour BEHAVIOUR DEFINED AS +"The terminatingAccountClassForVerificationId is the naming attribute of the terminatingAccountClassForVerification +managed object. ";; +REGISTERED AS {terminatingAccountClassForVerificationId-AOi}; + +verificationTranslatorId ATTRIBUTE +WITH ATTRIBUTE SYNTAX SccpAccountingDefinedTypesModule.SimpleNameType; +MATCHES FOR EQUALITY; +BEHAVIOUR verificationTranslatorIdBehaviour BEHAVIOUR DEFINED AS +"The verificationTranslatorId is the naming attribute of the verificationTranslator managed object. ";; +REGISTERED AS {verificationTranslatorId-AOi}; + +verificationRuleId ATTRIBUTE +WITH ATTRIBUTE SYNTAX SccpAccountingDefinedTypesModule.SimpleNameType; +MATCHES FOR EQUALITY; +BEHAVIOUR verificationRuleIdBehaviour BEHAVIOUR DEFINED AS +"The verificationRuleId is the naming attribute of the verificationRule managed object. ";; +REGISTERED AS {verificationRuleId-AOi}; + +gtNatureOfAddressSet ATTRIBUTE +WITH ATTRIBUTE SYNTAX SccpAccountingDefinedTypesModule.GtNatureOfAddressSet; +MATCHES FOR EQUALITY, SET-COMPARISON, SET-INTERSECTION; +BEHAVIOUR gtNatureOfAddressSetBehaviour BEHAVIOUR DEFINED AS +"The gtNatureOfAddressSet attribute defines a set of gtNatureOfAddress values. ";; +REGISTERED AS {gtNatureOfAddressSet-AOi} + +gtNumberingPlanSet ATTRIBUTE +WITH ATTRIBUTE SYNTAX SccpAccountingDefinedTypesModule.GtNumberingPlanSet; +MATCHES FOR EQUALITY, SET-COMPARISON, SET-INTERSECTION; +BEHAVIOUR gtNumberingPlanSetBehaviour BEHAVIOUR DEFINED AS +"The gtNumberingPlanSet attribute defines a set of gtNumberingPlan values. ";; +REGISTERED AS {gtNumberingPlanSet-AOi} + +gtTranslationTypeSet ATTRIBUTE +WITH ATTRIBUTE SYNTAX SccpAccountingDefinedTypesModule.GtTranslationTypeSet; +MATCHES FOR EQUALITY, SET-COMPARISON, SET-INTERSECTION; +BEHAVIOUR gtTranslationTypeSetBehaviour BEHAVIOUR DEFINED AS +"The gtTranslationTypeSet attribute defines a set of gtTranslationType values. ";; +REGISTERED AS {gtTranslationType-AOi} + +#### 7.2.4 Name binding definitions + +sccpAccount-srcc NAME BINDING +SUBORDINATE OBJECT CLASS sccpAccount AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS "ITU-T Rec. Q.751.2 (1996)":srcc AND SUBCLASSES; +WITH ATTRIBUTE sccpAccountId; +BEHAVIOUR sccpAccount-srccBehaviour BEHAVIOUR DEFINED AS +"This name binding is used when the sccpAccount instance is created by management operations. +A create request is rejected if +at least one of the instances which would be referenced by the attribute sccpLinkageSet is not existing +OR +at least one of the instances which would be referenced by the attributes selectionGroupSetForAccounting or +selectionGroupSetForVerification is not existing. ";; +CREATE; +DELETE ONLY-IF-NO-CONTAINED-OBJECTS; +REGISTERED AS {sccpAccount-srcc-NBOI}; + +terminatingAccountClassForAccounting-srcc NAME BINDING +SUBORDINATE OBJECT CLASS terminatingAccountClassForAccounting AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS "ITU-T Rec. Q.751.2 (1996)":srcc AND SUBCLASSES; +WITH ATTRIBUTE terminatingAccountClassForAccountingId; +BEHAVIOUR terminatingAccountClassForAccounting-srccBehaviour BEHAVIOUR DEFINED AS +"This name binding is used when a terminatingAccountClassForAccounting instance for SCCP accounting is created by +management operations. +A create request is rejected if +a gtRule would be referenced via the attribute ruleSet which is already referenced by another +terminatingAccountClassForAccounting contained in the same superior object class instance. + +A delete request is rejected if +the instance is still referenced by an instance of object class sccpAccount via attribute +selectionGroupSetForAccounting.";; + +CREATE WITH REFERENCE OBJECT INSTANCE; + +DELETE; + +REGISTERED AS {terminatingAccountClassForAccounting-src-NBOI}; + +terminatingAccountClassForVerification-scpAccount NAME BINDING + +SUBORDINATE OBJECT CLASS terminatingAccountClassForVerification AND SUBCLASSES; + +NAMED BY SUPERIOR OBJECT CLASS sccpAccount AND SUBCLASSES; + +WITH ATTRIBUTE terminatingAccountClassForVerificationId; + +BEHAVIOUR terminatingAccountClassForVerification-scpAccountBehaviour BEHAVIOUR DEFINED AS + +"This name binding is used when a terminatingAccountClassForVerification instance for SCCP accounting verification is created by management operations. + +A create request is rejected if + +a verificationRule would be referenced via the attribute ruleSet which is already referenced by another +terminatingAccountClassForVerification contained in the same superior object class instance, + +or if + +a verificationRule would be referenced via the attribute ruleSet which is contained in another sccpAccount instance than +the terminatingAccountClassForVerification + +A delete request is rejected if + +the instance is still referenced by an instance of object class sccpAccount via attribute +selectionGroupSetForVerification.";; + +CREATE WITH REFERENCE OBJECT INSTANCE; + +DELETE; + +REGISTERED AS {terminatingAccountClassForVerification-scpAccount-NBOI}; + +verificationTranslator-scpAccount NAME BINDING + +SUBORDINATE OBJECT CLASS verificationTranslator AND SUBCLASSES; + +NAMED BY SUPERIOR OBJECT CLASS sccpAccount AND SUBCLASSES; + +WITH ATTRIBUTE verificationTranslatorId; + +BEHAVIOUR verificationTranslator-scpAccount-Bhv BEHAVIOUR DEFINED AS + +"This name binding is used when a verificationTranslator instance for SCCP accounting is created by management operations.";; + +CREATE WITH REFERENCE OBJECT INSTANCE; + +DELETE ONLY-IF-NO-CONTAINED-OBJECTS; + +REGISTERED AS {verificationTranslator-scpAccount-NBOI}; + +verificationRule-verificationTranslator NAME BINDING + +SUBORDINATE OBJECT CLASS verificationRule AND SUBCLASSES; + +NAMED BY SUPERIOR OBJECT CLASS verificationTranslator AND SUBCLASSES; + +WITH ATTRIBUTE verificationRuleId; + +BEHAVIOUR verificationRule-verificationTranslator-Bhv BEHAVIOUR DEFINED AS + +"This name binding is used when a verificationRule instance for SCCP accounting is created by management operations.";; + +CREATE WITH REFERENCE OBJECT INSTANCE; + +DELETE; + +REGISTERED AS {verificationRule-verificationTranslator-NBOI}; + +#### 7.2.5 Notification Definitions + +sccpAccounting NOTIFICATION + +BEHAVIOUR sccpAccountingBehaviour BEHAVIOUR DEFINED AS + +"This notification is generated on occurrence of the event specified in the reporting triggers attribute of the ss7AccountingAndVerificationControl object controlling the sccpAccount, except if the attribute selectionGroupSetForAccounting of the instance has size zero. The notification shall also be sent, if all counters have the value zero. + +If accounting is done for all accounts in the same way, then it is possible to include the ruleSet only in one notification (e.g. the first) of the interval and omit it in all others. In this case the sequence of the given counters must be identical, i.e. refer to the same gtRules, for all notifications of the interval.";; + +WITH INFORMATION SYNTAX + +SccpAccountingDefinedTypesModule.SccpAccountingNotificationData + +AND ATTRIBUTE IDS + +| | | +|----------------------------|-----------------------------| +| endOfMeasurementTime | endOfMeasurementTime, | +| sccpLinkageSet | sccpLinkageSet, | +| sccpAccCounterDataSequence | sccpAccCounterDataSequence; | + +REGISTERED AS {sccpAccounting-NOI} + +sccpAccountingVerification NOTIFICATION + +BEHAVIOUR sccpAccountingVerificationBehaviour BEHAVIOUR DEFINED AS + +"This notification is generated on occurrence of the event specified in the reporting triggers attribute of the ss7AccountingAndVerificationControl object controlling the sccpAccount, except if the attribute selectionGroupSetForVerification of the instance has size zero. The notification shall also be sent, if all counters have the value zero. + +If verification is done for all accounts in the same way, then it is possible to include the ruleSet only in one notification (e.g. the first) of the interval and omit it in all others. In this case the sequence of the given counters must be identical, i.e. refer to the same gtRules, for all notifications of the interval.";; + +WITH INFORMATION SYNTAX + +SccpAccountingDefinedTypesModule.SccpAccountingNotificationData + +AND ATTRIBUTE IDS + +| | | +|----------------------------|-----------------------------| +| endOfMeasurementTime | endOfMeasurementTime, | +| sccpLinkageSet | sccpLinkageSet, | +| sccpAccCounterDataSequence | sccpAccCounterDataSequence; | + +REGISTERED AS {sccpAccountingVerification-NOI} + +#### 7.2.6 Parameter Definitions + +Currently none defined. + +#### 7.2.7 ASN.1 Definitions + +SccpAccountingDefinedTypesModule + +{itu-t(0) recommendation(0) q(17) omap(751) sccpAccounting(4) informationModel(0) asn1Modules(2) + +sccpAccountingDefinedTypesModule(0)} + +DEFINITIONS IMPLICIT TAGS ::= BEGIN + +IMPORTS + +ObjectInstance, SimpleNameType + +FROM Attribute-ASN1Module {joint-iso-itu-t ms(9) smi(3) part2(2) asn1Module(2) 1} + +Counter, DataProblem, accountingInformationModel, accountingAction, accountingAttribute, accountingAttributeGroup, accountingNameBinding, accountingNotification, accountingObjectClass, accountingPackage, accountingParameter, SelectionGroupSequence, SelectionGroup + +FROM AccountingDefinedTypesModule {itu-t(0) recommendation(0) q(17) omap(751) accounting(3) informationModel(0) asn1Modules(2) accountingDefinedTypesModule(0)} + +GtNatureOfAddress, GtNumberingPlan, GtTranslationType + +FROM SCCPDefinedTypesModule {itu-t(0) recommendation q(17) omap(751) sccp(2) informationModel(0) asn1Modules(2) sccpDefinedTypesModule(0)} + +Ss7SpecificErrorInformation + +FROM {itu(0) recommendation(0) q(17) omap2(2751) part1(1) informationModel(0) asn1Modules(2) q2751DefinedTypesModule(0)} + +EXPORTS EVERYTHING + +-- ASN.1 TYPE DEFINITIONS + +RuleSet ::= SET SIZE (1..maxNumberReferencesInRuleSet) OF ObjectInstance + +maxNumberReferencesInRuleSet INTEGER ::= i -- *this number is only for compilability* + +maxNumberReferencesInSccpLinkageSet INTEGER ::= j -- *this number is only for compilability* + +maxNumberReferencesInSccpSelectionGroupSet INTEGER ::= q -- *this number is only for compilability* + +SccpLinkageSet ::= SET SIZE (1..maxNumberReferencesInSccpLinkageSet) OF ObjectInstance + +SccpAccCounterData ::= SEQUENCE + +| | | +|-------------|-----------------------| +| {gts | [0] INTEGER, | +| octets | [1] INTEGER, | +| dataProblem | [2] DataProblem, | +| ruleSet | [3] RuleSet OPTIONAL} | + +SccpAccCounterDataSequence ::= SEQUENCE SIZE + +(1..maxNumberReferencesInSccpSelectionGroupSet) OF SccpAccCounterData + +-- *maximum size = q* + +``` + +SccpAccountingNotificationData ::= SEQUENCE { + endOfMeasurementTime EndOfMeasurementTime, + sccpLinkageSet SccpLinkageSet, + sccpAccCounterDataSequence SccpAccCounterDataSequence} + +selectionGroupSetInitial SelectionGroupSet ::= {} + +GtNatureOfAddressSet ::= SET OF GtNatureOfAddress + +GtNumberingPlanSet ::= SET OF GtNumberingPlan + +GtTranslationTypeSet ::= SET OF GtTranslationType +-- the following values of Ss7SpecificErrorInformation defined in Q.2751.1 are used: +gtRuleAlreadyUsedByAnotherTAC Ss7SpecificErrorInformation ::= 4000 +-- One of the gtRules specified in attribute ruleSet is already +-- used by another terminatingAccountClassForAccounting. + +invalidTACForAccountingReference Ss7SpecificErrorInformation ::= 4001 +-- at least one of the references in selectionGroupSetForAccounting is not +-- referring to a terminatingAccountClassForAccounting + +invalidTACForVerificationReference Ss7SpecificErrorInformation ::= 4002 +-- at least one of the references in selectionGroupSetForVerification is not +-- referring to a terminatingAccountClassForVerification contained in the +-- same sccpAccount. + +ruleOverlapError Ss7SpecificErrorInformation ::= 4003 +-- the ruleSet of the-terminatingAccountClassForAccounting/Verification +-- is not disjunct ! No unambiguous identification of a +-- terminatingAccountClass would be possible. + +sccpLinkageAlreadyInOtherAccount Ss7SpecificErrorInformation ::= 4004 +-- at least one of the sccpLinkages referred to by the sccpLinkageSet is +-- already -referred to by another sccpLinkageSet in another sccpAccount +-- instance + +selectionGroupOverlapError Ss7SpecificErrorInformation ::= 4005 +-- the manipulated selectionGroupSetForAccounting/Verification would +-- not allow an unambiguous identification of a the counter to be +-- incremented + +-- ASN.1 OBJECT IDENTIFIER definitions + +ruleSet-AOi OBJECT IDENTIFIER ::= {accountingAttribute gtRuleSet(22)} +sccpAccCounterDataSequence-AOi OBJECT IDENTIFIER ::= {accountingAttribute sccpAccCounterDataSequence(26)} +sccpAccountId-AOi OBJECT IDENTIFIER ::= {accountingAttribute sccpAccountId(23)} +sccpAccounting-NOI OBJECT IDENTIFIER ::= {accountingNotification sccpAccounting(3)} +sccpAccountingVerification-NOI OBJECT IDENTIFIER ::= {accountingNotification sccpAccountingVerification(4)} +sccpAccountPackage-POi OBJECT IDENTIFIER ::= {accountingPackage sccpAccountPackage(12)} +sccpAccount-OOi OBJECT IDENTIFIER ::= {accountingObjectClass sccpAccount(11)} +sccpAccountingLogRecord-OOi OBJECT IDENTIFIER ::= {accountingObjectClass sccpAccountingLogRecord(7)} +sccpAccountingLogRecordPackage-POi OBJECT IDENTIFIER ::= {accountingPackage sccpAccountingLogRecordPackage(13)} +sccpAccountingNotificationsPackage-POi OBJECT IDENTIFIER ::= {accountingPackage sccpAccountingNotificationsPackage(11)} +sccpLinkageSet-AOi OBJECT IDENTIFIER ::= {accountingAttribute sccpLinkageSet(24)} +sccpAccount-scr-NBOI OBJECT IDENTIFIER ::= {accountingNameBinding sccpAccount-scr(6)} +terminatingAccountClassForVerification-scpAccount-NBOI OBJECT IDENTIFIER ::= {accountingNameBinding terminatingAccountClassForVerification-scpAccount(7)} + +``` + +``` + +terminatingAccountClassForAccounting-scre-NBOi OBJECT IDENTIFIER ::= {accountingNameBinding +terminatingAccountClassForAccounting-scre(8)} + +terminatingAccountClassForAccountingId-AOi OBJECT IDENTIFIER ::= {accountingAttribute +terminatingAccountClassForAccountingId(25)} + +terminatingAccountClassForVerificationId-AOi OBJECT IDENTIFIER ::= {accountingAttribute +terminatingAccountClassForVerificationId(21)} + +terminatingAccountClassForAccountingPackage-POi OBJECT IDENTIFIER ::= {accountingPackage +terminatingAccountClassForAccountingPackage(7)} + +terminatingAccountClassForVerificationPackage-POi OBJECT IDENTIFIER ::= {accountingPackage +terminatingAccountClassForVerificationPackage(10)} + +terminatingAccountClassForAccounting-OOi OBJECT IDENTIFIER ::= {accountingObjectClass +terminatingAccountClassForAccounting(6)} + +terminatingAccountClassForVerification-OOi OBJECT IDENTIFIER ::= {accountingObjectClass +terminatingAccountClassForVerification(9)} + +verificationRule-OOi OBJECT IDENTIFIER ::= {accountingObjectClass verificationRule(10)} + +verificationTranslator-OOi OBJECT IDENTIFIER ::= {accountingObjectClass verificationTranslator(8)} + +verificationRulePackage-POi OBJECT IDENTIFIER ::= {accountingPackage +verificationRulePackage(8)} + +verificationTranslatorPackage-POi OBJECT IDENTIFIER ::= {accountingPackage +verificationTranslatorPackage(9)} + +verificationTranslatorId-AOi OBJECT IDENTIFIER ::= {accountingAttribute +verificationTranslatorId(16)} + +verificationRuleId-AOi OBJECT IDENTIFIER ::= {accountingAttribute +verificationRuleId(17)} + +gtNatureOfAddressSet-AOi OBJECT IDENTIFIER ::= {accountingAttribute +gtNatureOfAddressSet(18)} + +gtNumberingPlanSet-AOi OBJECT IDENTIFIER ::= {accountingAttribute +gtNumberingPlanSet(19)} + +gtTranslationTypeSet-AOi OBJECT IDENTIFIER ::= {accountingAttribute +gtTranslationTypeSet(20)} + +verificationTranslator-sccpAccount-NBOi OBJECT IDENTIFIER ::= {accountingNameBinding +verificationTranslator-sccpAccount(9)} + +verificationRule-verificationTranslator-NBOi OBJECT IDENTIFIER ::= +{accountingNameBinding verificationRule-verificationTranslator(10)} + +END + +``` + + + +# 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/Q/T-REC-Q.765-200006-I_PDF-E/raw.md b/marked/Q/T-REC-Q.765-200006-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4bf901017f2133e5eb047d3b6f4b5beb2c768f6c --- /dev/null +++ b/marked/Q/T-REC-Q.765-200006-I_PDF-E/raw.md @@ -0,0 +1,1380 @@ + + +![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 + +**Q.765** + +(06/2000) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of Signalling System No. 7 – ISDN user part + +--- + +**Signalling System No. 7 – Application transport +mechanism** + +ITU-T Recommendation Q.765 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +# SWITCHING AND SIGNALLING + +| | | +|----------------------------------------------------------|--------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 | +| General | Q.700 | +| Message transfer part (MTP) | Q.701-Q.709 | +| Signalling connection control part (SCCP) | Q.711-Q.719 | +| Telephone user part (TUP) | Q.720-Q.729 | +| ISDN supplementary services | Q.730-Q.739 | +| Data user part | Q.740-Q.749 | +| Signalling System No. 7 management | Q.750-Q.759 | +| ISDN user part | Q.760-Q.769 | +| Transaction capabilities application part | Q.770-Q.779 | +| Test specification | Q.780-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| BROADBAND ISDN | Q.2000-Q.2999 | + +For further details, please refer to the list of ITU-T Recommendations. + +# **Signalling System No. 7 – Application transport mechanism** + +## **Summary** + +This Recommendation describes the additions to the ISDN User Part (ISUP) for providing a transport mechanism used by applications requiring a bearer in conjunction with the support of the application's signalling information flow. This transport mechanism shall provide the same capabilities as the Transaction Capabilities Application Part (TCAP) provides to its users. + +## **Source** + +ITU-T Recommendation Q.765 was revised by ITU-T Study Group 11 (1997-2000) and approved under the WTSC Resolution 1 procedure on 15 June 2000. + +## **Keywords** + +APM, ISUP. + +## 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..... | 2 | +| 3 | Definitions ..... | 2 | +| 4 | Abbreviations..... | 3 | +| 5 | Recommendation structure ..... | 4 | +| 6 | Modelling..... | 4 | +| 6.1 | Network model ..... | 5 | +| 6.2 | Specification model ..... | 6 | +| 6.2.1 | Introduction..... | 6 | +| 6.2.2 | General model..... | 6 | +| 6.2.3 | Dynamic primitive flows ..... | 8 | +| 7 | Application Process functions ..... | 11 | +| 7.1 | General..... | 11 | +| 7.2 | APM Application Process (AP) functions ..... | 12 | +| 7.2.1 | Introduction..... | 12 | +| 7.2.2 | Primitive interface (AP-SACF) ..... | 13 | +| 7.2.3 | Procedures ..... | 13 | +| 7.2.4 | Primitive contents ..... | 14 | +| 8 | Single Association Control Function (SACF) ..... | 15 | +| 8.1 | Introduction..... | 15 | +| 8.2 | Information flows related to messages sent by the node..... | 15 | +| 8.3 | Information flows related to messages received by the node..... | 16 | +| 9 | ISDN user part ASE (ISUP ASE) ..... | 17 | +| 9.1 | Primitive interface..... | 17 | +| 9.2 | Procedures..... | 17 | +| 9.3 | Primitive contents ..... | 18 | +| 10 | Application transport mechanism ASE (APM ASE)..... | 18 | +| 10.1 | Primitive interface..... | 18 | +| 10.2 | Procedures..... | 19 | +| 10.2.1 | Normal procedures – Sending ..... | 19 | +| 10.2.2 | Normal procedures – Receiving ..... | 19 | +| 10.2.3 | Sending of acknowledgement..... | 21 | +| 10.2.4 | Segmentation ..... | 21 | +| 10.3 | Primitive contents ..... | 24 | + +| | Page | +|-------------|----------------------------------------------------------------------------------------| +| 11 | Application Transport Mechanism User ASE (APM-user ASE) ..... 24 | +| 11.1 | Primitive interface..... 24 | +| 11.2 | Procedures..... 25 | +| 11.2.1 | General..... 25 | +| 11.2.2 | Signalling congestion..... 25 | +| 11.2.3 | Handling of unrecognized signalling information..... 25 | +| 11.3 | Primitive contents ..... 25 | +| 12 | Network Interface function ..... 26 | +| 12.1 | Introduction..... 26 | +| 12.2 | Primitive interfaces ..... 26 | +| 12.2.1 | MTP interface ..... 26 | +| 12.2.2 | AEI interface..... 26 | +| 12.3 | Procedures..... 26 | +| 12.3.1 | Formats and codes ..... 26 | +| 12.3.2 | Distribution..... 26 | +| 12.3.3 | Primitive mapping ..... 27 | +| 13 | Errors Handling ASE (EH ASE)..... 27 | +| 13.1 | Introduction of unidentified context and addressing errors handling mechanism ..... 27 | +| 13.1.1 | Unidentified context and addressing errors handling – Local error handling ..... 28 | +| 13.1.2 | Unidentified context and addressing errors handling – Remote error handling ..... 28 | +| 13.2 | Reassembly error handling..... 29 | +| 13.3 | Primitive interface..... 29 | +| 13.4 | Procedures..... 29 | +| 13.4.1 | Normal procedures – Remote error handling ..... 29 | +| 13.4.2 | Normal procedures – Local error handling..... 30 | +| 13.4.3 | Exceptional procedures – Context identifier error..... 31 | +| 13.4.4 | Exceptional procedures – Unrecognized reason value ..... 31 | +| 13.5 | Primitive contents ..... 31 | +| 14 | Application transport notification information ..... 31 | +| 15 | Timers ..... 32 | +| Appendix I | – Example sequence diagrams of APM segmentation..... 33 | +| Appendix II | – Setting of parameter and message instruction indicators..... 34 | + +# **Signalling System No. 7 – Application transport mechanism** + +# **1 Scope** + +This Recommendation describes the additions to the ISDN User Part (ISUP) for providing a transport mechanism used by applications requiring a bearer in conjunction with the support of the application's signalling information flow. This transport mechanism shall provide the same capabilities as the Transaction Capabilities Application Part (TCAP) provides to its users. The definition of the applications that use this mechanism are documented in their own Recommendation and are therefore outside the scope of this Recommendation. + +The Application Transport Mechanism (APM) is capable of creating signalling associations between APM-user application logic located at a Public Initiating Node (PIN) and its peer APM-user application logic located at the Public Addressed Node (PAN). (The PIN/PAN concept is described in clause 6.) The ability to create different PIN/PAN relationships is only limited by the addressing mechanism used. At call setup, the ISUP basic call mechanism is used to route the call through the network towards the PAN in the same manner as it normally establishes a call. The APM addressing mechanism is used to determine the node in the call path where the Application Information has to be handled but has no influence on the routing of the call. + +This transport mechanism provides the APM-user applications (APM "2000"-user applications) with both an implicit and an explicit APM addressing capability. The applications originally designed to use the APM "98" [6] (APM "98"-user applications) can be supported without alterations by the mechanism described in this Recommendation. APM "98"-user and APM "2000"-user applications are differentiated by their application context identifiers. + +The coexistence along a call path of nodes with the APM "98" capability and nodes supporting the APM "2000" functionality may cause in two very specific configurations, an inappropriate handling of application transport parameters sent by an APM "2000"-user application. + +- 1) The first scenario is the following: + - a) An APM "2000"-user application sends information at call set-up towards a remote application. + - b) An intermediate node supporting the previous APM version [6] is encountered in the call path before the node where the application information has to be delivered. + - c) This intermediate node is addressed by the called party number. + +In this specific case, the intermediate APM "98" node will reject the application information associated to the APM "2000"-user application according to the procedures defined in [6]. + +- 2) The second scenario is the case where an error notification has to be generated by an APM "98" node on receipt of application information associated to an APM "2000"-user application. This notification may not be delivered to the initiating application if the explicit addressing mechanism was used by this application. An APM "98" node does indeed not support the EH ASE (see clause 13) and cannot therefore use the explicit addressing mechanism for the sending of a notification. Apart from the case explained above (intermediate APM "98" node addressed by the called party number), such a problem can only possibly occur if application information generated by an application using the explicit addressing mechanism is received by an end node with APM "98" capability. + +Because of the above reasons future standardized applications shall not be defined as APM "98"-user applications. + +At any time of the call, it is possible to create the following PIN/PAN relationships: + +- PIN and PAN at end exchanges; +- PIN at transit exchange and PAN at end exchange; +- PIN at end exchange and PAN at transit exchange; +- PIN and PAN at transit exchanges. + +It means that a PIN located anywhere in the call path has the capability to create a PIN/PAN relationship with any exchange in the call path having the APM-user capability. The intermediate exchanges having the APM capability but not the APM-user capability will transit the APM information. + +It is, of course, possible to communicate in both directions once a PIN/PAN relationship has been created. It should be noted that only one PIN/PAN relationship may exist over the same segment of the call path for a given application (Context identity value) which does not use the explicit addressing mechanism. For example, if a PIN/PAN relationship has been established (PIN) between the Originating Local Exchange (OLE) and an intermediate exchange in the call path (PAN), it is not possible to later establish a PIN/PAN relationship from the destination local exchange to the originating local exchange for the same application since its corresponding PAN would be located at the OLE and would therefore result in two PIN/PAN relationships overlapping at the call leg between the OLE and the intermediate exchange. However, it is possible to establish overlapping PIN/PAN relationships for a given application using the explicit addressing mechanism. + +# 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 Q.761 (1999), *Signalling System No. 7 – ISDN User Part functional description.* +- [2] ITU-T Q.762 (1999), *Signalling System No. 7 – ISDN User Part general functions of messages and signal.* +- [3] ITU-T Q.763 (1999), *Signalling System No. 7 – ISDN User Part formats and codes.* +- [4] ITU-T Q.764 (1999), *Signalling System No. 7 – ISDN User Part signalling procedures.* +- [5] ITU-T Q.1400 (1993), *Architecture framework for the development of signalling and OA&M protocols using OSI concepts.* +- [6] ITU-T Q.765 (1998), *Signalling System No. 7 – Application transport mechanism.* + +# 3 Definitions + +This Recommendation defines the following terms: + +- 3.1 context:** A set of rules by which to interpret the contents of the Encapsulated Application Information field as identified by a context identifier which uniquely represents an application to which data are associated. +- 3.2 APM "98"-user application:** An APM-user application which was originally designed to be supported by the application transport mechanism defined in ITU-T Q.765 [6]. + +**3.3 APM "2000"-user application:** An APM-user application which is defined to be supported by the application transport mechanism specified in this Recommendation. + +**3.4 APM end node:** A node which determines that the APM application information cannot be passed on beyond that node. The way a node determines that it is the APM end node is beyond the scope of this Recommendation. + +# **4 Abbreviations** + +This Recommendation uses the following abbreviations. + +| | | +|----------|--------------------------------------------------| +| ACM | Address Complete Message | +| AE | Application Entity | +| AEI | Application Entity Invocation | +| ALS | Application Layer Structure | +| AP | Application Process | +| APM | Application Transport Mechanism | +| APM-user | Application Transport Mechanism User | +| APP | Application Transport Parameter | +| ASE | Application Service Element | +| CPG | Call Progress message | +| EH | Errors Handling | +| EUCEH | Enhanced Unidentified Context and Error Handling | +| IAM | Initial Address Message | +| ISDN | Integrated Services Digital Network | +| ISUP | ISDN User Part | +| LE | Local Exchange | +| M/O | Mandatory/Optional | +| MTP-3 | Message Transfer Part | +| NI | Network Interface | +| NNI | Network Node Interface | +| OSI | Open Systems Interconnection | +| PAN | Public Addressed Node | +| PIN | Public Initiating Node | +| PRI | Pre-Release Information Message | +| SACF | Single Association Control Function | +| SAO | Single Association Object | +| SDL | Specification and Description Language | +| SID | Signalling Identifier | +| SIO | Service Indicator Octet | +| SLS | Signalling Link Set | + +| | | +|------|-----------------------------------------| +| TE | Transit Exchange | +| UCEH | Unidentified Context and Error Handling | + +# 5 Recommendation structure + +The description of the ISDN User Part procedures in this Recommendation are structured according to the model described in 6.2. The description is thus divided into two main parts: + +- Protocol functions. +- Non-protocol functions, i.e. exchange nodal functions; this is referred to as the "Application Process". + +This Recommendation describes only the part of the total Application Process and Protocol functions in the exchange, that relates to NNI enhancements for the support of the Application Transport Mechanism. + +The protocol functions relate only to signalling associations with a bearer (ISUP) and describe the additional information and procedures to that defined for ISUP Basic Call [4] and its associated formats and codes [3] required to support the Application Transport Mechanism. + +The signalling association with a bearer is subdivided into three parts: APM-user Protocol Control (APM-user ASE), Application Transport Mechanism protocol control (APM ASE), and the ISUP Basic Call (ISUP ASE). These are coordinated by the Single Association Control Function (SACF). + +The Application Entity (AE) can contain more than one APM-user application. It may contain APM "98"-user applications and APM "2000"-user applications. It also contains Errors Handling (EH ASE) for taking the appropriate actions in the case when either the addressed node (PAN) does not support the APM-user application or for the handling of APM error cases. + +The Application Process (AP) contains all Call Control functions; however, this Recommendation will only describe the enhancements required to support the Application Transport Mechanism (APM). The AP relevant to the public ISUP basic call can be found in [4], whereas the APM-user functionality can be found in the suitable Recommendations that define the given application. + +The service primitive technique, used to define the ISUP ASEs and the SACF specific to the Application Transport Mechanism's signalling needs, is a way of describing how the services offered by: + +- an ASE or SACF can be accessed by the user of the services; or +- the provider of a (set of) service(s) can be accessed by the SACF or the AP, respectively. + +The service primitive interface is a conceptual interface and is not a testable or accessible interface. It is a descriptive tool. The use of service primitives at an interface does not imply any particular implementation of that interface, nor does it imply that an implementation must conform to that particular service primitive interface to provide the stated service. All conformance to the ISUP specification is based on the external behaviour of a node, i.e. on the generation of the correct message structure and in the proper sequence (as specified in [3] and [4], and in this Recommendation). + +The structure and examples of its usage are illustrated in 6.2. + +Examples of primitive flow sequence diagrams for APM segmentation can be found in Appendix I. + +# 6 Modelling + +The models described in this clause introduce concepts and terminology used in this specification of the Application Transport Mechanism. + +## 6.1 Network model + +![Figure 1/Q.765 – Network model diagram showing the relationship between two APM-user applications connected via a TE (Terminal Equipment) through a public network. The diagram shows two APM-user boxes, each containing an LE/TE PIN or PAN component. A dashed line represents the logical peer-to-peer path of APM-user information, connecting the two APM-user boxes. A solid line represents the actual path of APM-user information, connecting the LE/TE PIN/PAN components through the TE box. The diagram is labeled T1197830-97.](5b4e774d63e0e0ed73801a9247755e5f_img.jpg) + +----- Logical peer-to-peer path of APM-user information +——— Actual path of APM-user information + +Figure 1/Q.765 – Network model diagram showing the relationship between two APM-user applications connected via a TE (Terminal Equipment) through a public network. The diagram shows two APM-user boxes, each containing an LE/TE PIN or PAN component. A dashed line represents the logical peer-to-peer path of APM-user information, connecting the two APM-user boxes. A solid line represents the actual path of APM-user information, connecting the LE/TE PIN/PAN components through the TE box. The diagram is labeled T1197830-97. + +**Figure 1/Q.765 – Network model** + +This clause illustrates the relationship between the APM-user Application and the APM implemented across a public network. Figure 1 provides an example of a call from an initiating application to an addressed application via a public transit network. The APM provides the APM-user application with the service of providing both a signalling association as well as a bearer between remote applications. + +The Public Initiating Node (PIN) and Public Addressed Node (PAN) concept is introduced here to assist in the description of the APM. The PIN represents the point in the network that wishes to initiate communications towards a peer APM-user application located at an addressed location (PAN). An APM-user application may result in the establishment of a signalling and bearer association, in which case it will use the services of the public basic call. + +A PIN/PAN signalling relationship may be established: + +- 1) at any time in association with an already established public basic call; +- 2) at call set-up by utilizing the received IAM; or +- 3) by the application establishing a new call. + +In the third case, the initiating APM-user's Application Process supplies a normal public E.164 number which is used to route through the public network, thus establishing an association between the Public Initiating Node (PIN) and the Public Addressed Node (PAN). At any phase of the call, the APM addressing mechanism is used to specify the location of the PAN. Either the initiating APM-user supplies the address of the node where the Application Information shall be delivered (explicit addressing), or no address is provided by the initiating application, in which case: + +- 1) if the application information is associated to an APM "2000"-user application, the PAN is the next node supporting the APM-user application (implicit addressing); or +- 2) if the application information is associated to an APM "98"-user application, the PAN is determined as specified in 10.2.2. + +The APM destination address does not influence the routing of the call through the public network but is only used to determine whether a node in the call path is the PAN. The PAN identifies the particular APM-user application by the Context Identifier value carried within the Application Transport Parameter (APP). + +The public basic call mechanism is employed to provide an association between the PIN and the PAN. In routing through the public network the call may pass through intermediate public nodes with or without the ability to support the particular APM-user functionality. However, if the application is not addressed towards that node, it will behave as a normal intermediate public node. + +As a number of APM-user applications may be independently active on the same basic call, it is possible to have a number of PIN/PAN relationships established in either the forward or backward direction and at different phases with respect to the ISUP basic call. + +## 6.2 Specification model + +### 6.2.1 Introduction + +The model used to structure the description of ISUP procedures herein are based on the OSI Application Layer Structure (ALS) model, see [5]. This clause presents the model, gives a general description of its operation and shows the generalized model for the "Exchange Application Process" for the support of applications making use of the Application Transport Mechanism over the Network Node Interface (NNI). + +### 6.2.2 General model + +The generalized model for the bearer related (ISUP) Application Transport Mechanism Application Process is shown in Figure 2. This figure does not represent the situation at any specific point during ISUP procedures, but instead it shows the full picture of the architecture. The specific application of this model is discussed in 6.1. Figure 2 shows the primitive interfaces between the functional blocks, as used in the body of this Recommendation for calls with bearer (ISUP). + +![Figure 2/Q.765 – ISUP specification model diagram showing the hierarchy of functional blocks and their interfaces.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +The diagram illustrates the ISUP specification model architecture. At the top, the 'Exchange Application Process' contains 'ISUP Nodal functions'. Below this, the 'ISUP AEI' (Application Environment Interface) block contains several functional blocks: 'ISUP SAO', 'SACF', 'APM user ASE', 'EH ASE', 'APM ASE', and 'ISUP ASE'. The 'SACF' block is central and connected to the 'ISUP SAO' block on its left. It has primitive interfaces labeled 'a' (upwards to ISUP Nodal functions), 'b' (to APM user ASE), 'c' (to EH ASE), 'd' (to APM ASE), 'e' (to ISUP ASE), and 'f' (downwards to the NI block). The 'NI' (Network Interface) block is at the bottom of the Exchange Application Process, connected to the 'MTP-3' layer via interface 'g'. The reference 'T11108460-00' is located in the bottom right corner of the diagram area. + +Figure 2/Q.765 – ISUP specification model diagram showing the hierarchy of functional blocks and their interfaces. + +Figure 2/Q.765 – ISUP specification model + +The definitions of the interfaces a) to g) are: + +- a) Interface between the Application Process nodal functions (AP) and the SACF for the support of the APM over the NNI – see 7.2.2. +- b) Interface between SACF and APM-user ASE representing the application being supported by the APM. (Interface is out of the scope of this Recommendation, except for the primitive interface part used to access the services of the APM ASE.) – see 11.1. +- c) Interface between SACF and EH ASE representing the handling of unidentified context identifier values and error cases – see 13.1. +- d) Interface between SACF and APM ASE representing enhancements of the public functionality (ISUP) for providing a transportation mechanism for the support of various applications (APM-user) over the NNI – see 10.1. +- e) Interface to public ISUP basic call signalling ASE (interface is out of the scope of this Recommendation, except for the primitive interface part used by the APM ASE to access the services of the ISUP ASE) – see clause 9. +- f) Interface between SACF and NI function – see 12.2.2. +- g) Interface to MTP-3. + +With respect to Figure 2, all functions also have an interface to a "Management application", this is not defined as a formal primitive interface. + +The term "Exchange Application Process" is used to describe all the Application functionality in an exchange. ISUP is a part of the Exchange Application Process. Thus the ISUP Nodal functions shown on the model are referred to as the ISUP Application Process functions in the body of this Recommendation. + +The ISUP AEI provides all the bearer-related communication capabilities required by the ISUP Nodal functions. For simplicity an ISUP AEI is defined as containing just one SAO; this avoids the need to specify a Multiple Association Control Function (MACF). Thus all coordination of ISUP signalling associations are performed via the ISUP Nodal functions. + +The SACF has the responsibility of coordinating the flow of primitives between its interfaces in the appropriate manner. + +The ISUP ASE is defined by [4]. Its main responsibilities are basic call procedures and the handling of protocol errors and unrecognized information handling [4]. The monolithic nature of these Recommendations means that both Public Call Control and Protocol Control functionality are defined together. It is not the intention of this Recommendation to redefine [4] in ALS format, therefore it is referenced *en bloc* within this Recommendation as the ISUP ASE. Conceptually, this should be considered to represent a logical division between the protocol control functionality within the ISUP ASE and its associated call control functionality within the application process. The modelling and interfaces with respect to this are outside the scope of this Recommendation. + +The APM ASE provides the means for the transfer of information (including addressing) between nodes for signalling requiring a bearer, and to provide generic services to applications, while being independent of any of these. It is responsible for the enhancements to the NNI (ISUP) for the support of a mechanism which allows various applications to transport their information flows via the NNI. Its main responsibilities are: + +- 1) to provide message segmentation in order to provide the APM-user the ability to transport up to 2048 octets of application information; +- 2) to provide the means to identify the PAN. + +The APM ASE is able to support multiple APM-users where each is treated independently and provided with the same level of service. + +The EH ASE handles the Application Transport Instruction Indicators (ATII), thereby providing a compatibility mechanism for the case where various levels of application (context) support exist within network nodes. It also handles APM reassembly error cases according to the ATII. For the compatibility mechanism it consists of two distinct sets of functions; one set used as the Public Addressed Node (PAN), and one set used as the Public Initiating Node (PIN) (supporting the signalling association to a subsequent exchange). The PIN/PAN concept is explained in 6.1. + +The APM-user ASE is responsible for preparing the application specific signalling in a form that can be transported by the public Application Transport Mechanism. It is also responsible for providing any required addresses for the APM addressing mechanism. + +To handle any particular ISUP function, the Exchange Application Process creates an instance of the required ISUP Nodal functions. ISUP will create instances, as required, of the ISUP AEI. The Network Interface (NI) function exists to distribute messages received from the MTP-3 to the appropriate instance of the ISUP AEI. There is only one instance of the NI in an exchange. The NI also fulfils the presentation layer function according to the formats and codes of [3]. + +The MTP-3 interface is defined in [1]. + +The SAO contained in the ISUP AE is one of the following types: + +a) Public Initiating Node (PIN). + +This contains: + +- ISUP, Initiating APM, Initiating EH ASE, Initiating APM-user and ISUP SACF. + +b) Public Addressed Node (PAN). + +This contains: + +- ISUP, Addressed APM, Addressed EH ASE, Addressed APM-user and ISUP SACF. + +The ISUP may be incoming or outgoing depending on the direction of the PIN/PAN relationship with respect to the ISUP call. + +### 6.2.3 Dynamic primitive flows + +Figures 3 and 4 illustrate the dynamic primitive flows for an APM-user call with a bearer being supported over the NNI (ISUP) for the case that a call control message is coincident with the application information flow. Figure 3 shows the case when a message is being sent; Figure 4 shows the case when a message is being received. + +![Diagram of Figure 3/Q.765 showing an Application Process connected to APM-user ASE, APM ASE, and ISUP ASE. A large downward arrow is shown below the ISUP ASE box.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +This diagram illustrates the static primitive flows for the NNI support of the APM-user information flow. At the top, a box labeled "Application Process" is connected by three curved arrows to three stacked boxes: "APM-user ASE", "APM ASE", and "ISUP ASE". Below the "ISUP ASE" box is the text "T1197850-97". A large, curved arrow points downwards from the bottom of the "ISUP ASE" box, indicating a flow to the next figure. + +Diagram of Figure 3/Q.765 showing an Application Process connected to APM-user ASE, APM ASE, and ISUP ASE. A large downward arrow is shown below the ISUP ASE box. + +**Figure 3/Q.765** + +![Diagram of Figure 4/Q.765 showing an Application Process connected to APM-user ASE, APM ASE, and ISUP ASE. A large upward arrow is shown above the Application Process box.](724c7777b608e53be38b12b6fb3c43bc_img.jpg) + +This diagram illustrates the dynamic primitive flows for the NNI support of the APM-user information flow. At the top, a box labeled "Application Process" is connected by three curved arrows from three stacked boxes: "APM-user ASE", "APM ASE", and "ISUP ASE". Below the "ISUP ASE" box is the text "T1197860-97". A large, curved arrow points upwards from the bottom of the "ISUP ASE" box, through the "Application Process" box, indicating a flow from the previous figure. + +Diagram of Figure 4/Q.765 showing an Application Process connected to APM-user ASE, APM ASE, and ISUP ASE. A large upward arrow is shown above the Application Process box. + +**Figure 4/Q.765** + +Figures 5 and 6 illustrate the dynamic primitive flows for the NNI support of the APM-user information flow via a call with a bearer where no call control messages are sent coincidentally. That is, the APM ASE initiates a primitive towards the ISUP ASE which in turn sends an APM message which will provide a mechanism for supporting the information flow. + +![Diagram of Figure 5/Q.765 showing an Application Process connected to a large rectangular box. Inside the box, three smaller boxes are stacked vertically: APM-user ASE, APM ASE, and ISUP ASE. Arrows point from the Application Process to each of these three boxes. A reference code 'T1197870-97' is located below the ISUP ASE box. An arrow points downwards from the bottom of the large rectangular box.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +Diagram of Figure 5/Q.765 showing an Application Process connected to a large rectangular box. Inside the box, three smaller boxes are stacked vertically: APM-user ASE, APM ASE, and ISUP ASE. Arrows point from the Application Process to each of these three boxes. A reference code 'T1197870-97' is located below the ISUP ASE box. An arrow points downwards from the bottom of the large rectangular box. + +**Figure 5/Q.765** + +![Diagram of Figure 6/Q.765 showing an Application Process connected to a large rectangular box. Inside the box, three smaller boxes are stacked vertically: APM-user ASE, APM ASE, and ISUP ASE. Arrows point from the Application Process to each of these three boxes. A reference code 'T1197880-97' is located below the ISUP ASE box. An arrow points upwards from the bottom of the large rectangular box towards the Application Process.](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) + +Diagram of Figure 6/Q.765 showing an Application Process connected to a large rectangular box. Inside the box, three smaller boxes are stacked vertically: APM-user ASE, APM ASE, and ISUP ASE. Arrows point from the Application Process to each of these three boxes. A reference code 'T1197880-97' is located below the ISUP ASE box. An arrow points upwards from the bottom of the large rectangular box towards the Application Process. + +**Figure 6/Q.765** + +When the APM ASE and associated AP logic must communicate, primitives are passed between them. Figure 7 illustrates the case when the AP requests a service directly from the APM ASE. Figure 8 illustrates an indication being sent directly from the APM ASE to the AP. + +![Diagram of Figure 7/Q.765 showing an Application Process connected to a large central box, which in turn connects to three stacked boxes: APM-user ASE, APM ASE, and ISUP ASE. A reference code T1197890-97 is present below the ISUP ASE box.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +The diagram shows an 'Application Process' box at the top. A line descends from it to a large vertical rectangular box. From the right side of this large box, three curved arrows point to three smaller rectangular boxes stacked vertically: 'APM-user ASE', 'APM ASE', and 'ISUP ASE'. Below the 'ISUP ASE' box is the text 'T1197890-97'. A long curved arrow originates from the bottom of the large central box and points downwards. + +Diagram of Figure 7/Q.765 showing an Application Process connected to a large central box, which in turn connects to three stacked boxes: APM-user ASE, APM ASE, and ISUP ASE. A reference code T1197890-97 is present below the ISUP ASE box. + +**Figure 7/Q.765** + +![Diagram of Figure 8/Q.765 showing three stacked boxes (APM-user ASE, APM ASE, ISUP ASE) connected to a large central box, which then connects to an Application Process box. A reference code T1197900-97 is present below the ISUP ASE box.](2cde062fd82833415971a8bd1a2cafab_img.jpg) + +The diagram shows three stacked rectangular boxes on the right: 'APM-user ASE', 'APM ASE', and 'ISUP ASE'. Below the 'ISUP ASE' box is the text 'T1197900-97'. A line connects the 'ISUP ASE' box to a large vertical rectangular box on the left. From the top of this large box, a curved arrow points upwards to an 'Application Process' box at the top. + +Diagram of Figure 8/Q.765 showing three stacked boxes (APM-user ASE, APM ASE, ISUP ASE) connected to a large central box, which then connects to an Application Process box. A reference code T1197900-97 is present below the ISUP ASE box. + +**Figure 8/Q.765** + +# 7 Application Process functions + +## 7.1 General + +The modelling of the Application Process (AP) is outside the scope of this Recommendation; however, in order to appreciate the role of the AP for the purposes of this Recommendation, it can be considered to consist of three different functional groups that are relevant to the support of an application over the public Network Node Interface (NNI). These are the APM-user application processes (out of the scope of this Recommendation), the public network ISUP basic call functionality, where the application process and protocol control functions are defined together in + +the monolithic Recommendations of the ISUP [4], and the APM specific application process logic which is defined in this Recommendation. + +It is the responsibility of the APM-user aspect of the application process to coordinate between the APM-user application process and the public basic call application process functionality. It must ensure that the basic call states are aligned between the public basic call and the APM-user application processes. + +When the APM-user application requires the establishment of a PIN/PAN signalling association and the related ISUP call already exists, then the application makes use of the APM services in conjunction with the existing call. When no call already exists, it passes the routing information to the public application process such that it can route the call from the Public Initiating Node (PIN) to the appropriate node in the public network, Public Addressed Node (PAN), which contains the adjacent APM-user functionality. The PIN/PAN concept is described in 6.1. Details of the Public basic call routing information requirements can be found in [4]. + +The definition of the primitive interface (interface a) in Figure 2) between the AP and the SACF for both the specific public basic call primitives and those of the APM-user application are outside the scope of this Recommendation. + +## 7.2 APM Application Process (AP) functions + +### 7.2.1 Introduction + +The following functions are fulfilled by the APM application process: + +#### 1) Transit node operation + +The public network may contain a number of transit exchanges between the PIN and the PAN. Some or all of these exchanges may support the APM; however, they are not the addressed node (PAN) for the application using the APM. In this case, these nodes must pass the APM information transparently with the behaviour of a transit exchange. + +#### 2) Support of APM signalling association acknowledgement mechanism (sent from the PAN in conjunction with the APM segmentation/reassembly procedures) + +When sending information in subsequent messages after an IAM but before the reception of a first backwards message, there is no guarantee that the information will successfully arrive at its destination. Since APM-user applications may wish to send a greater amount of information during the establishment phase than can be carried in an ISUP IAM message, it is necessary to send the information in subsequent messages. To ensure the reliable delivery of this information, the application process located at the PAN initiates the sending of an appropriate first backwards message (such as, an ACM with "no indication" or APM) towards the PIN on reception of an IAM indicating segmentation of APM information, has occurred. This provides an acknowledgement to the IAM, thereby confirming the establishment of a signalling association. + +NOTE – In the case that such an acknowledgement for an APM signalling association initiated by the PIN at call set-up has not yet been received before reception of either: + +- an ACM indicating "subscriber free"; or +- a CPG indicating "alerting"; or +- an ANM or CON + +without the appropriate acknowledgement, then if the application association for the call was essential, the call shall be released and the maintenance function shall be notified. + +#### 3) The coordination of segmented APM-user information with public call control messages + +When application data is segmented by the APM, the result is that the information is sent over the ISUP via a number of messages. It is therefore the responsibility of the APM to + +ensure that the information is reassembled correctly and that the application data is associated with the correct call control message, where applicable. This is achieved by the APM ASE informing the AP that the complete information has not been made available to the AP (i.e. reassembly procedure under way). Similarly the AP is informed once the complete information has been passed to it, thus allowing it to complete its processing. It is the responsibility of the AP to coordinate all the application processes related to the call. + +In the case of the receipt of segmented application data relating to a Release message the application data segments start with a Pre-release Information message, and the End\_APP\_Info indication primitive indicates to the application process that all the application information relating to the yet to be received Release message has been received. + +- 4) The handling of instructions received from the SACF resulting from the handling of Application Transport Instruction Indicators. + +The Application Transport Instruction Indicator (ATII) mechanism allows for an APM-user application to instruct a receiving node how to respond to error cases, for example it may wish to release the call in the case that the application is not supported at the PAN. This instruction is fulfilled when the AP receives the UCEH\_Release indication primitive. + +- 5) Use of Pre-release Information message + +This capability allows information to be transported at Release in a manner which is compatible with the 1992 and subsequent versions of the ISUP protocol. Any APM-user application requiring the transport of application data in the release phase of a call must make use of the pre-release mechanism (PRI message) described in ITU-T Q.761 [1], Q.762 [2], Q.763 [3] and Q.764 [4]. + +### 7.2.2 Primitive interface (AP-SACF) + +The primitives in Table 1 have been introduced by the functionality specified in this Recommendation. All other primitives at this interface (public basic call or APM-user application) are outside the scope of this Recommendation. + +**Table 1/Q.765 – Primitives between AP and SACF** + +| Primitive name | Types | Direction (Note) | +|-------------------------------------------------------------------------------|--------------------|------------------| +| APM_Transit | Indication/Request | ➔ / ➔ | +| APM_Acknowledgement | Request | ➔ | +| More_APP_Info | Indication | ➔ | +| End_APP_Info | Indication | ➔ | +| UCEH_Release | Indication | ➔ | +| NOTE – Primitive flow from SACF to AP: ➔
Primitive flow from AP to SACF: ➔ | | | + +### 7.2.3 Procedures + +This clause describes the additional procedures required in the application process for the support of the APM. + +#### 7.2.3.1 Transit Node + +On receipt of an APM\_Transit Indication primitive, the contents are passed transparently through the transit exchange and sent to SACF in the APM\_Transit Request primitive. + +#### 7.2.3.2 Public Initiating Node (PIN) + +##### 7.2.3.2.1 APM signalling association acknowledgement mechanism + +No specific procedures for the PIN. + +##### 7.2.3.2.2 Segmentation coordination + +The coordination of segmentation must be performed by the receiving node. To achieve this coordination, the AP must not complete the processing of information received (basic call control primitive) in conjunction with the reception of the More\_APP\_Info indication primitive. + +On reception of the End\_APP\_Info indication primitive, the AP may complete the processing of the received information. + +#### 7.2.3.3 Public Addressed Node (PAN) + +##### 7.2.3.3.1 APM signalling association acknowledgement mechanism + +The reception of the More\_APP\_Info primitive indicates that APP segmentation/reassembly procedures are underway. If the More\_APP\_Info indication primitive is received in conjunction with the receipt of an IAM, the signalling association must be acknowledged by sending the primitive corresponding to the appropriate first backwards message (e.g. ACM "no indication", CPG or APM) together with the APM\_Acknowledgement request primitive to SACF. + +##### 7.2.3.3.2 Segmentation coordination + +See 7.2.3.2.2. + +##### 7.2.3.3.3 UCEH\_Release indication + +On reception of the UCEH\_Release indication primitive, a release procedure is initiated with cause dependent on the received Reason parameter value as shown below: + +Unidentified context/Addressing Error 79 – Service or option not implemented, unspecified. + +Reassembly error 111 – Protocol error, unspecified. + +The release of an ISUP public basic call is described in [4]. + +### 7.2.4 Primitive contents + +Table 2 describes the contents of the primitives passed across interface (a). + +The More\_APP\_Info indication primitive, the APM\_Acknowledgement request primitive and the End\_APP\_Info indication primitives are empty. + +**Table 2/Q.765 – Contents of the UCEH\_Release Ind primitive** + +| Parameter | Mandatory/Optional | +|-----------|--------------------| +| Reason | M | + +**Table 3/Q.765 – Contents of the APM\_Transit Ind/Req primitive** + +| Parameter | Mandatory/Optional | +|--------------|--------------------| +| Transit_Data | M | + +# 8 Single Association Control Function (SACF) + +## 8.1 Introduction + +The main objective of SACF is to receive/deliver primitives from/to the appropriate entity and to perform a distribution function where appropriate. The flow of information is from the AP (interface a) in Figure 2) towards NI (interface f) in Figure 2) or vice versa. Therefore the SACF is also responsible to ensure that when multiple primitives are generated by the ASEs towards the AP, that they are delivered across the interface together to ensure that correct associations are maintained. The SACF described here only defines the mapping and functions related to the Application Transport Mechanism. The SACF functionality related specifically to the public basic call functionality or the APM-user application functionality is outside the scope of this Recommendation. + +The interfaces referenced herein are illustrated in 6.2, Figure 2. Clause 6.2.3 also provides examples of the "Dynamic primitive flows". + +The primitives on the interface between the AP and SACF, interface a), that are not specifically for the definition of the APM (i.e. public basic call and APM user applications) are outside the scope of this Recommendation. + +The application specific primitives on the interface between SACF and APM-user ASE, interface b), is outside the scope of this Recommendation. + +The primitives used on the interface between SACF and EH ASE, interface c), are defined in 13.3. + +The parameters in these primitives are listed in Tables 27 to 29. + +The primitives used on the interface between SACF and APM ASE, interface d), are defined in 10.1. + +The parameters in these primitives are listed in Table 18. + +The primitives related to ISUP basic call on the interface between SACF and ISUP ASE, interface e), are outside the scope of this Recommendation. Primitives associated with the APM's use of the ISUP ASE's services are defined in 9.1. Their associated contents are defined in 9.3. + +## 8.2 Information flows related to messages sent by the node + +On receipt of a primitive (request or response) from the Application Process (AP), via interface a), the SACF issues appropriate primitive(s) to the ASEs, populating the parameters in the generated primitives from the appropriate subset of the parameters received from the AP. The SACF also performs a distribution function of the responding primitives received from the ASEs prior to sending the resulting primitive to NI via interface f). + +The APM-user ASE will send application data to the APM ASE, via SACF, using an APM\_U\_Data request primitive via interface b). Note that a number of APM-user ASEs may generate the APM\_U\_Data primitive. A parameter received by the APM ASE within the APM\_Data primitive is identifiable through its unique relationship with an application context, and hence the appropriate APM-user ASE. Other APM related primitives on interface b) are defined in 11.1. Their associated contents are defined in 11.3. Each APM\_U\_Data primitive sent by one APM-user ASE shall be handled independently from the APM\_U\_Data primitives generated by other APM-user ASEs or even the same APM-user ASE. + +Tables 4 to 8 show the mapping of primitives performed by the SACF. + +**Table 4/Q.765 – Mapping from APM-user ASE to APM ASE primitives** + +| Interface b), APM-user ASE | Interface d), APM ASE | +|----------------------------|-----------------------| +| APM_U_Data | APM_Data | + +**Table 5/Q.765 – Mapping from EH ASE to APM ASE primitives** + +| Interface c), EH ASE | Interface d), APM ASE | +|-----------------------------|------------------------------| +| APM_U_Data | APM_Data | +| Send_APM_Transit | Send_APM_Transit | + +**Table 6/Q.765 – Mapping from APM ASE to ISUP ASE primitives** + +| Interface d), APM ASE | Interface e), ISUP ASE | +|------------------------------|-------------------------------| +| APM_Transfer | APM_Transfer | + +**Table 7/Q.765 – Mapping from AP to APM ASE primitives** + +| Interface a), AP ASE | Interface d), APM ASE | +|-----------------------------|------------------------------| +| APM_Acknowledgement | APM_Acknowledgement | +| APM_Transit | APM_Transit | + +**Table 8/Q.765 – Mapping from ISUP ASE to NI primitives** + +| Interface e), ISUP ASE | Interface f), NI | +|-------------------------------|-------------------------| +| Transfer | Transfer | + +## 8.3 Information flows related to messages received by the node + +On receipt of a Transfer Indication primitive (see Table 22) from the NI, the SACF distributes the contents of the primitive to the ISUP ASE. In the case that an Application Transport Parameter (APP) is present, the ISUP ASE will then pass it to the APM ASE via the APM\_Transfer indication primitive (see Table 16). More than one APP may be present in the ISUP message, hence multiple APPs may be passed to the APM ASE. When the APM ASE is ready to pass the received information to the APM-user ASE, then it sends the APM\_Data indication primitive to SACF. The SACF will distribute the primitive(s) to the appropriate APM-user ASE(s) in the APM\_U\_Data indication primitive according to the context identifier value which is used to uniquely identify the APM-users. + +Tables 9 to 13 show the mapping of primitives performed by the SACF. For received messages, the mapping of APM\_U\_Data and APM\_Transfer (Tables 4, 5 and 6) primitives is the reverse to that described in the tables for messages sent by the node in 8.2. + +**Table 9/Q.765 – Mapping from EH ASE to APM-user ASE primitives** + +| Interface c), EH ASE | Interface b), APM-user ASE | +|-----------------------------|-----------------------------------| +| APM_Error | APM_U_Error | + +**Table 10/Q.765 – Mapping from EH ASE to AP primitives** + +| Interface c), EH ASE | Interface a), AP | +|-----------------------------|-------------------------| +| UCEH_Release | UCEH_Release | + +**Table 11/Q.765 – Mapping from APM ASE to AP primitives** + +| Interface d), APM ASE | Interface a), AP | +|------------------------------|-------------------------| +| APM_Transit | APM_Transit | +| More_APP_Info | More_APP_Info | +| End_APP_Info | End_APP_Info | + +**Table 12/Q.765 – Mapping from APM ASE to EH ASE primitives** + +| Interface d), APM ASE | Interface c), EH ASE | +|------------------------------|-----------------------------| +| APM_UCEH_Error | APM_UCEH_Error | + +**Table 13/Q.765 – Mapping from NI to ISUP ASE primitives** + +| Interface f), NI | Interface e), ISUP ASE | +|-------------------------|-------------------------------| +| Transfer | Transfer | + +# 9 ISDN user part ASE (ISUP ASE) + +The ISUP ASE is defined in [4]. Its main responsibilities are basic call procedures and the handling of protocol errors and unrecognized information handling [4]. The monolithic nature of this Recommendation means that both Public Call Control and Protocol Control functionality are defined together. It is not the intention of this Recommendation to redefine [4] in ALS format, therefore they are referenced *en bloc* as the ISUP ASE. Conceptually, this should be considered to represent a logical division between the protocol control functionality within the ISUP ASE and its associated call control functionality within the application process. The modelling and interfaces with respect to this are outside the scope of this Recommendation. + +## 9.1 Primitive interface + +The SACF uses the services provided by the ISUP ASE primitive interface (interface e) in Figure 2) as listed in Table 14. + +**Table 14/Q.765 – Primitives between ISUP ASE and SACF** + +| Primitive name | Types | Direction (Note) | +|-------------------------------------------------------------------------------------------|--------------------|-------------------------| +| APM_Transfer | Indication/Request | ➔/ ➔ | +| NOTE – Primitive flow from SACF to ISUP ASE: ➔
Primitive flow from ISUP ASE to SACF: ➔ | | | + +ISUP ASE uses the SACF service primitives: Transfer request/indication. + +It is also a receiver of the indications: Remote\_Status, Destination\_Available, Destination\_Unavailable. + +## 9.2 Procedures + +The procedures of the ISUP ASE are defined in [4]. With respect to the Application Transport Mechanism, on reception of APM\_Transfer request primitive(s), it is the responsibility of the ISUP + +ASE to include the APP(s) within a suitable call control message, when available, or alternatively to generate an Application Transport Mechanism message (APM message; see [3]). Similarly it must handle the reception of the APP parameter(s) and the transfer of the received data in the APM\_Transfer indication primitive(s). The APM message can only be sent/received on a non-idle circuit and does not cause a state change. The ISUP parameter compatibility instruction indicators should have the same settings as the ATII. In the case that a message contains more than one APP, then the ATII settings for each APP will be according to the needs of each APM-user application. However, the ISUP parameter compatibility settings must be according to the most stringent case with regard to the ATIIIs. + +## 9.3 Primitive contents + +Primitive contents is shown in Table 15. + +**Table 15/Q.765 – Contents of the APM\_Transfer Ind/Req primitive** + +| Parameter | Mandatory/Optional | Reference | +|-----------------------------|--------------------|-------------------------------------| +| Application Transport (APP) | M | ITU-T Q.761, Q.762, Q.763 and Q.764 | + +# 10 Application transport mechanism ASE (APM ASE) + +The APM ASE specifies the extensions to ISUP in order to provide the underlying services to the APM-user ASE(s) and support the application's (APM-user's) information flows. The APM ASE is responsible for the signalling procedures and the parameters specific to the Application Transport Mechanism. + +The APM ASE provides a segmentation mechanism to the APM-user(s) such that the ISUP message length limitation does not restrict the APM-user information flows. The maximum supported size of APM-user information is 2048 octets in length, per Application Information field. The APM ASE may serve many APM-users which are differentiated by their Context Identifiers. + +## 10.1 Primitive interface + +The ISUP SACF uses the services provided by the APM ASE primitive interface (interface d) in Figure 2) as listed in Table 16. + +**Table 16/Q.765 – Primitives between APM ASE and ISUP SACF** + +| Primitive name | Types | Direction (Note) | +|-----------------------------------------------------------------------------------------|--------------------|------------------| +| More_APP_Info | Indication | ➔ | +| End_APP_Info | Indication | ➔ | +| APM_Transit | Indication/Request | ➔ / ➜ | +| APM_Acknowledgement | Request | ➜ | +| APM_UCEH_Error | Indication | ➔ | +| APM_Data | Indication/Request | ➔ / ➜ | +| Send_APM_Transit | Request | ➔ | +| NOTE – Primitive flow from APM ASE to SACF: ➔
Primitive flow from SACF to APM ASE: ➜ | | | + +The APM ASE uses the services provided by the ISUP SACF primitive interface (interface d) in Figure 2) as listed in Table 17. + +**Table 17/Q.765 – Primitives between ISUP SACF and APM ASE** + +| Primitive name | Types | Direction (Note) | +|-----------------------------------------------------------------------------------------|--------------------|-------------------------| +| APM_Transfer | Indication/Request | ➔ / ➔ | +| NOTE – Primitive flow from SACF to APM ASE: ➔
Primitive flow from APM ASE to SACF: ➔ | | | + +## 10.2 Procedures + +### 10.2.1 Normal procedures – Sending + +On receipt of an APM\_Data request primitive, the APM ASE constructs the Application Transport Parameter (APP) according to the definition in ITU-T Q.761, Q.762, Q.763 and Q.764. The context identifier is set based on the APM-user. The Application Transport Instruction indicators are supplied by the APM-user. + +For APM "2000"-user applications using explicit addressing, the APM-user shall supply the address of the PAN and should supply the address of the PIN. + +NOTE – If the address of the PIN is not supplied in the case of explicit addressing, then the PAN may be unable to address error notifications or other application information towards the PIN. Problems are also likely to arise with the segmentation and reassembly procedures. + +If no originating (destination) address is supplied by the APM-user, then the originating (destination) address field in the APP parameter will be of zero length. When provided by the APM-user, the originating and destination addresses shall uniquely identify the PIN and the PAN respectively. + +For APM "98"-user applications, neither address length fields nor address fields are included in the APP. + +The APM Segmentation indicator is set to zero (0), the Sequence Indicator field is coded "new sequence" and the Segmentation Local Reference is absent, unless segmentation procedures apply (see 10.2.4). APM segmentation procedures shall only apply if it is not possible to transfer all parameters in the IAM, ACM, CON, ANM or PRI message and SGM, if simple segmentation procedures are used, because the 272 octet MTP limit would be exceeded. + +NOTE – The threshold for the initiation of the APM segmentation procedure may alternatively depend on network characteristics. The value of this threshold may vary per traffic relation depending on the typical network configuration and interconnection arrangements. Based on the set of services supported (e.g. ISDN end-to-end information, Call Diversion, User-to-user, etc.) and the set of APM applications (VPN, BICC, GAT, etc.), the exchange performing the segmentation is able to calculate the maximum length of the first segment to leave enough space in a message for use by any subsequent exchange. This maximum length may vary per traffic relation depending on the typical network configuration and interconnection arrangements. + +The Application Data received from the APM-user is encapsulated and the whole APP is transferred in the APM\_Transfer request primitive. + +On receipt of an APM\_Transit request primitive, the APM ASE transfers the received information transparently in an APM\_Transfer request primitive. + +### 10.2.2 Normal procedures – Receiving + +On receipt of an APM\_Transfer indication primitive, the subsequent action depends on the Application Context Identifier associated to the received APP. + +If the APP is associated to an APM "98"-user application, the action depends on whether it was received at call setup or at another time. + +If the APP is associated to an APM "2000"-user application, the procedures are the same at any phase of the call. + +#### **10.2.2.1 Procedures at call establishment (IAM message) for APM "98"-user applications** + +On receipt of an APM\_Transfer indication at call setup, if the received APP is associated to an APM "98"-user application, the action depends on whether this node is addressed by the called party number. If not, the APM ASE notes that this node is a "pass-on" node for this context and transfers the APP parameter unchanged in an APM\_Transit indication primitive. A pass-on node does not verify the contents of the Transit\_Data parameter. + +If this is the addressed node, the action depends on whether the context in question is supported at this node: + +- 1) If the context is supported, the parameter is checked to see if segmentation has occurred. If so the segmentation reassembly procedure applies (see 10.2.4) and the completely reassembled Application Information is sent in the APM\_Data indication primitive. +- 2) If the context is not supported, then an APM\_UCEH\_Error indication primitive is sent. The Application Context and Application Transport Instruction Indicators are set as received in the APM\_Transfer primitive and the Reason is set to "Unidentified Context". If the parameter had been segmented, the APM ASE notes that the reassembly procedure for this sequence has been abandoned. + +#### **10.2.2.2 Procedures at other times for APM "98"-user applications and any time of the call for APM "2000"-user applications** + +On receipt of an APM\_Transfer indication, the APM ASE checks whether this is a "pass-on" node for this context. If so, the APP parameter is passed on unchanged within an APM\_Transit indication primitive. A pass-on node does not verify the contents of the Transit\_Data parameter. + +If not, the action depends on whether the context in question is supported at this node: + +- 1) If the context is supported: + - If the node is addressed by the destination address field contained in the APP (in case of explicit addressing), or if no destination address field is contained in the APP, the APM ASE checks whether it is expecting for the received context an acknowledgement to an initial segment sent at call setup according to the segmentation procedure of 10.2.4: + - If so, the segmentation procedures apply. + - If the APM ASE is not expecting such an acknowledgement, the parameter is checked to see if segmentation has occurred. If so, the segmentation reassembly procedure applies (see 10.2.4) and the completely reassembled Application Information is sent in the APM\_Data indication primitive. + - If the node is not addressed by the destination address field contained in the APP parameter in case of explicit addressing then: + - If the node is not an APM end node, the APP parameter is passed on unchanged within an APM\_Transit indication primitive. + - If the node is an APM end node, then an APM\_UCEH\_Error indication primitive is sent. The Originating Address, the Application Context and the Application Transport Instruction Indicators are set as received in the APM\_Transfer primitive, the Reason is set to "Unidentified Context/Addressing Error". + +- 2) If the context is not supported: +- If the node is not an APM end node, then the APM ASE notes that this node is a "pass-on" node for this context and transfers the APP parameter unchanged in an APM\_Transit indication primitive. + - If the node is an APM end node, then if this is the first or only segment of a sequence, an APM\_UCEH\_Error indication primitive is sent. The Originating Address (if received), the Application Context and Application Transport Instruction Indicators are set as received in the APM\_Transfer primitive. The Reason is set to "Unidentified Context/Addressing Error". If the parameter had been segmented, the APM ASE notes that the reassembly procedure for this sequence has been abandoned. Subsequent segments in this case are discarded. + +#### 10.2.2.3 Reception of the Send\_APM\_Transit primitive + +On receipt of the Send\_APM\_Transit primitive, the contents shall be passed unchanged in the APM\_Transit primitive. + +### 10.2.3 Sending of acknowledgement + +On receipt of an APM\_Acknowledgement request primitive, an APP will be constructed for each sequence currently under reassembly (Note). The ATII will be set to "release call" and "do not send notification" and the Application Information field shall be empty. + +If the Context is associated to an APM "2000"-user application, the originating address field and the destination address field will contain the destination address and the originating address, respectively, received in the segments currently under reassembly. The address fields will be of zero length if no addresses are contained in the segments currently under reassembly. + +If the Context is associated to an APM "98"-user application, neither address length fields nor address fields are included in the APP. + +This APP will then be sent in an APM\_Transfer request primitive. + +NOTE – One acknowledgement only is sent for sequences associated with the same application context identifier, originating address and destination address. + +### 10.2.4 Segmentation + +Segmentation procedures may be separately and simultaneously applied to multiple application data fields generated by one or several APM-user applications. The procedures in 10.2.4.1 describe the handling of segmentation and reassembly for application information sent in one APM\_Data request primitive. It should be noted that when multiple APM-users are utilizing the services of the APM for a single call, that the procedures may be applied concurrently and independently with respect to each APM-user and that each application data field sent by one APM-user shall be handled independently from any other application data field generated by the same or any other APM-user. + +The initial segment of each sequence must be transported in the first message and this initial segment size may be of zero length. In case that segmentation is applied on different application data fields simultaneously, it must start in the same message. The first message may be an IAM, ACM, CPG, CON, ANM or PRI message (when available) and this procedure ensures that the reassembling node is able to associate the APM information with the first ISUP message. A maximum of one such message can be associated with the transport of segmented application data. Any additional segments will be included in the APP within subsequent APM message(s). In order to associate all the reassembled application data with the first ISUP message, the AP is informed when reassembly procedures are invoked by sending the More\_APP\_Info indication primitive. On completion of reassembly for all sequences for which initial segments were received in the first message, the End\_APP\_Info indication primitive is sent. + +NOTE – In the case of the first message being a PRI message the End\_APP\_Info indication primitive indicates to the AP that all the APP information relating to the subsequent REL message has been received. + +There would be a possibility that user information segments could be lost when sent forward during call setup if sent before the receipt of a first backwards message. To avoid this situation occurring, the PIN shall not send subsequent segments to an IAM message until a backward message is received containing an empty APP, which implicitly indicates that a path has been successfully routed through the network to the PAN. The PAN initiates the backwards acknowledgement indication only in the case that an IAM is received containing an APP which indicates that segmentation has occurred. + +For segmented application data associated with an ACM, CPG, CON, ANM or PRI message, this message shall be sent first, followed by the SGM message (when ISUP Simple segmentation applies to remaining information in the ISUP message), and then followed by the APM messages containing subsequent segments. In case a PRI message is sent, the REL message shall be sent following the APM message containing the last segment. + +#### 10.2.4.1 Procedures for segmentation + +The following rules apply when Application Information in an APM\_Data request primitive has to be segmented: + +- a) The maximum number of segments is 10 (one initial, possibly empty, segment plus up to 9 segments). The maximum size of Application Information that can be supported is 2048 octets. If the Application Information is too long to be segmented, then the local maintenance function shall be notified, and the APM\_Data request primitive is discarded. +- b) The Encapsulated Application Information field in the first segment shall begin with the first octet of the application Information and sequentially fill the Encapsulated Application Information field. (Alternatively the first segment may contain zero octets of Application Information, and the second segment is filled as described.) The Sequence Indicator field will be set to indicate "new sequence", the APM segmentation indicator field will indicate the number of segments that remain to be sent and a Segmentation Local Reference value included that is unique to the call. +- c) The encapsulated information field in each subsequent segment shall begin with the first octet following the last octet transmitted in the previous segment, thus continuing segmentation until no further encapsulated application data octets remain. The Sequence indicator field shall indicate "subsequent segment to first segment" and the APM segmentation indicator field shall be decremented to indicate the number of segments that remain to be sent and the Segmentation Local Reference shall have the same values as sent in the first segment. +- d) Once the first segment has been transmitted, then all remaining segments of that Application Information shall be sent except in the case that the first segment is sent in an IAM, in which case the reception of an empty APP is awaited prior to the sending of subsequent segments. This APP acknowledgement must originate from the PAN for the segmentation sequence. +- e) Only failure conditions shall cause the transmission of a segmented message to be aborted. In this case the maintenance function is to be notified. +- f) The ATII, the originating address and the destination address should be set as provided by the APM-user in the APM\_Data request primitive for the first and all subsequent segments (see Note). + +NOTE – The address fields will be of zero length if they are not provided by the APM-user and if this APM-user is an APM "2000"-user application. If the Application Information is associated to an APM "98"-user application, neither address length fields nor address fields are included in the APPs. + +#### 10.2.4.2 Procedures for reassembly + +Reassembly procedures may be simultaneously applied to multiple sequences related to the same or different contexts. Each sequence characterized by its Application Context Identifier, its originating address (possibly absent) and its Segmentation Local Reference is handled by one reassembly function. Each segment is therefore directed towards a specific reassembly function according to the Application Context Identifier, the originating address and the Segmentation Local reference it contains. + +The following rules apply to the receipt and reassembly of segmented Application Information: + +- a) A reassembly function, on receiving an APM\_Transfer indication primitive containing an APP with the Sequence indicator field indicating "new sequence" and the APM segmentation indicator field set to a value greater than zero (0), and not exceeding nine (9), shall treat that Encapsulated Application Information as a valid first segment and save the segment contents, the Application Context Identifier, the originating address (if received – see 10.2.1) and the received Segmentation Local Reference value. (The first segment may have zero octets of Encapsulated Application Information.) Timer Treass shall be started on receipt of a valid first segment. +- b) A reassembly function, on receiving a subsequent segment with the Sequence Indicator field indicating "subsequent segment to first segment" and the APM segmentation indicator field set to a value one less than the value in the previously received segment, the same Application Context Identifier, the same originating address (if received – see 10.2.1) and the same Segmentation Local Reference value as received in the first segment shall treat the segment as a valid next segment. +- c) A reassembly function, on receiving a valid next segment in which the APM segmentation indicator field has a value greater than zero, shall save the segment contents along with the saved contents of the previous segment or segments. +- d) A reassembly function, on receiving a valid next segment in which the APM segmentation indicator field has a value equal to zero, final segment, shall deliver the accumulated segments, including the last segment, as the complete Application Information to the APM-user with the APM\_Data indication primitive. Timer Treass shall be stopped on receipt of the final segment of the sequence. +- e) A reassembly function in which no reassembly process is active shall discard any received segment which is not a valid first segment and send the APM\_UCEH\_Error Indication primitive indicating "reassembly error". +This applies to: + - Segments with a Sequence Indicator coded "Subsequent segment to first segment". + - Segments in which the APM segmentation indicator field has a value exceeding 9. +- f) A reassembly function shall discard the received and any saved segments on receipt of any subsequent segment which is not a valid next segment and send the APM\_UCEH\_Error Indication primitive indicating "reassembly error" for both reassembly sequences. +This applies to: + - Segments with a segmentation indicator field value that is not decremented from the value of the previous segment. +- g) A reassembly function shall discard any saved segments on receipt of any subsequent segment which is not a valid next segment and send the APM\_UCEH\_Error Indication primitive indicating "reassembly error". +This applies to: + - Segments with a Sequence Indicator coded "New sequence". + +- h) On expiry of timer $T_{reass}$ , the reassembly function shall discard all segments received for the current sequence and send the APM\_UCEH\_Error indication primitive indicating "reassembly error". +- i) In the case that an APM\_UCEH\_Error indication primitive indicating "reassembly error" is sent, the ATII settings shall reflect those applicable to the sequence undergoing the reassembly procedure. + +## 10.3 Primitive contents + +The following primitives are already defined elsewhere: + +APM\_Transfer primitive is defined in Table 15. + +More\_APP\_Info primitive is defined in 7.2.4. + +End\_APP\_Info primitive is defined in 7.2.4. + +APM\_Acknowledgement primitive is defined in 7.2.4. + +APM\_Transit primitive is defined in Table 3. + +APM\_UCEH\_Error primitive is defined in Table 28. + +Send\_APM\_Transit primitive is defined in Table 29. + +Table 18 defines the primitive used across the SACF/APM ASE interface d). + +**Table 18/Q.765 – Contents of the APM\_Data Ind/Req primitive** + +| Parameter | Mandatory/Optional | +|----------------------------------------------|--------------------| +| Application Context Identifier | M | +| Application Transport Instruction Indicators | M | +| Originating Address | O | +| Destination Address | O | +| Application Information | M | + +# 11 Application Transport Mechanism User ASE (APM-user ASE) + +The APM-user ASE is responsible for the detailed protocol control signalling aspects specific to the application it represents. The definition of the application is outside the scope of this Recommendation. The APM-user ASE utilises a specific interface towards SACF in order to access the services of the APM ASE. + +An APM-user is uniquely identified by the SACF through its "context identifier value". This represents the application that it supports and defines the "context" in which this APM-user operates. + +## 11.1 Primitive interface + +The SACF/APM-user ASE interface (interface b) in Figure 2), is application specific and therefore outside the scope of this Recommendation, except for the primitive interface part used to access the services of the APM ASE. The Application Transport Mechanism specific primitives are listed in Table 19. + +**Table 19/Q.765 – Primitives between APM-user ASE and SACF** + +| Primitive name | Types | Direction (Note) | +|-------------------------------------------------------------------------------------------|--------------------|-------------------------| +| APM_U_Data | Indication/Request | ➔ / ➔ | +| APM_U_Error | Indication | ➔ | +| NOTE – Primitive flow from SACF to APM-user: ➔
Primitive flow from APM-user to SACF: ➔ | | | + +APM-user ASE may be a receiver of the SACF service primitive indications: Remote\_Status, Destination\_Available, Destination\_Unavailable dependent on the needs of the given application. + +Multiple APM\_U\_Data request primitives may be sent from the APM-user ASE to the SACF. The procedures are applied concurrently and independently with respect to each primitive. + +## 11.2 Procedures + +### 11.2.1 General + +The procedures for the APM-user ASE are application specific and therefore outside the scope of this Recommendation. + +### 11.2.2 Signalling congestion + +In order to avoid congestion in the No. 7 signalling network, it is necessary that applications that contribute signalling load towards a congested destination limit their signalling traffic in a controlled manner. As the AP makes use of the ISUP ASE, the ISDN User Part signalling congestion control procedure [4] may reduce traffic towards an affected destination. As such, new call attempts may temporarily be rejected. + +Since this mechanism does not restrict the signalling load being generated by already established calls, APM-users should consider the inclusion of procedures to restrict the application's request for generating signalling load. For this purpose, the APM-user ASE would subscribe to the "Remote\_Status" primitive. + +### 11.2.3 Handling of unrecognized signalling information + +APM-users should consider the inclusion of procedures for the handling of unrecognized signalling information carried in the Encapsulated Application Information field of the Application Transport Parameter (APP). + +## 11.3 Primitive contents + +**Table 20/Q.765 – Contents of the APM\_U\_Data Ind/Req primitive** + +| Parameter | Mandatory/Optional | +|----------------------------------------------|---------------------------| +| Application Context Identifier | M | +| Application Transport Instruction Indicators | M | +| Originating Address | O | +| Destination Address | O | +| Application Data | M | + +**Table 21/Q.765 – Contents of the APM\_U\_Error Ind primitive** + +| Parameter | Mandatory/Optional | +|--------------|--------------------| +| Notification | M | + +# 12 Network Interface function + +## 12.1 Introduction + +The Network Interface (NI) function is the part of ISUP that provides a transport interface for instances of the ISUP AEI. The MTP-3 Service Primitive interface is a single interface within an exchange, but multiple instances of signalling associations exist within one exchange. NI associates the signalling instance representation (session layer [5]) of the external interface to the internal instances. NI also represents the presentation layer [5] for ISUP. + +## 12.2 Primitive interfaces + +### 12.2.1 MTP interface + +The interface (interface g) in Figure 2) to the MTP-3 is the Service Primitive interface defined in reference [1]. + +### 12.2.2 AEI interface + +The primitives listed in Table 22 are present on the interface between the NI and the SACF in the ISUP AEI (interface f) in Figure 2). + +**Table 22/Q.765 – Primitive between NI and SACF** + +| Primitive name | Types | Direction (Note) | +|-------------------------------------------------------------------------------|--------------------|------------------| +| Transfer | Request/Indication | ➔ / ⬅ | +| Remote_Status | Indication | ⬅ | +| Destination_Unavailable | Indication | ⬅ | +| Destination_Available | Indication | ⬅ | +| NOTE – Primitive flow from SACF to NI: ➔
Primitive flow from NI to SACF: ⬅ | | | + +## 12.3 Procedures + +### 12.3.1 Formats and codes + +The NI performs the presentation layer [5] function for the ISUP. The details of ISUP formats and codes can be found in [3]. + +MTP\_Transfer indication primitives received from the MTP, (interface g) in Figure 2) are decoded according to the formatting rules defined in [3] and procedures defined in reference [4]. + +### 12.3.2 Distribution + +MTP\_Transfer indication primitives received from the MTP are distributed to AEIs. Before this distribution can be performed, the circuit to which the incoming message is addressed must be tied to an AEI. Through the use of the CIC, NI, OPC and DPC values of the circuit, AEI identity, mapping is performed according to the following rules: + +- If the circuit value corresponds to an existing ISUP AEI, the message is distributed to that AEI. +- If the circuit value does not correspond to an existing ISUP AEI, a new instance of ISUP AEI is created. + +When a Transfer request primitive is received from an ISUP AEI, it is mapped into a MTP\_Transfer request primitive. The AEI identity to which the message is associated is used to identify the CIC, NI, OPC and DPC values to use when sending the message. The SIO and SLS fields are completed as specified in [3]. + +### 12.3.3 Primitive mapping + +Tables 23 and 24 show the primitive mapping performed by the NI. + +**Table 23/Q.765 – NI primitive mappings from MTP to SACF** + +| Interface g) from MTP | Interface f) to SACF | +|-------------------------|------------------------------------| +| MTP_Transfer indication | Transfer indication | +| MTP_Status indication | Remote_Status indication | +| MTP_Pause indication | Destination_Unavailable indication | +| MTP_Resume indication | Destination_Available indication | + +**Table 24/Q.765 – NI primitive mappings from SACF to MTP** + +| Interface f) from SACF | Interface g) to MTP | +|------------------------|----------------------| +| Transfer request | MTP_Transfer request | + +# 13 Errors Handling ASE (EH ASE) + +The EH ASE handles error cases such as unidentified context values, addressing errors and reassembly errors. The EH ASE takes action according to the Application Transport Instruction Indicators (ATII) received together with the application information in the APP. Based on the Release Call Indicator, the call may be released or allowed to proceed. The Send Notification Indicator determines if a notification is sent. On reception of such a notification at the node which sent the original application information, the EH ASE is responsible for informing the appropriate APM-user application that the error has occurred. For example, to notify the application located at the PIN that the desired context identifier value was not supported at the PAN. The EH ASE is a mandatory ASE in the AEI that supports the APM ASE. + +## 13.1 Introduction of unidentified context and addressing errors handling mechanism + +The unidentified context and Addressing Errors handling mechanism describes the cases when: + +- 1) an APM "98"-user application initiates a signalling association with a remote exchange (PAN) which has the APM capability but does not support the application; or +- 2) Application Information generated by an exchange (PIN), supporting an application identified by a specific context identifier, is received by an APM end node which has the APM capability but does not support the application indicated by the context identifier or which is not the node addressed by the Destination Address received in the APP parameter (in case of explicit addressing). + +The unidentified context and addressing errors handling mechanism ensures these situations are handled according to the specific needs of the initiating application. + +### 13.1.1 Unidentified context and addressing errors handling – Local error handling + +- When an exchange is the addressed node for an APP associated to an APM "98"-user application but does not support the specified context; or +- when an APM end node receives an unidentified context identifier value or a destination address which is not its own, + +the EH ASE takes action according to the Application Transport Instruction Indicators (ATII). Based on the Release Call Indicator, the call may be released or allowed to proceed. The Send Notification Indicator determines if a notification is sent back from these exchanges towards the PIN. + +Figure 9 illustrates the dynamic flow of information from the point where the APM ASE identifies that the APM-user is not supported or that the node is not addressed (in case of explicit addressing). In the case that there is no APM-user supporting the context identifier of a received APP or that the node is not addressed by the Destination Address contained in the APP, then the APM ASE sends an APM\_UCEH\_Error indication primitive indicating the context identifier received and supplies the received Originating Address (if available) and Application Transport Instruction Indicators (ATII). This initiates the unidentified context and addressing errors handling procedures. These procedures can be seen as a user of the APM mechanism by the manner in which the notification is transported. + +![Figure 9/Q.765 – Dynamic flow in an exchange when an unidentified context or addressing error is detected. The diagram shows a stack of four boxes: Application Process, EH ASE, APM ASE, and ISUP ASE. Arrows indicate the flow of primitives between them. A dashed arrow points from the Application Process to the EH ASE. Solid arrows point from the EH ASE to the APM ASE, from the APM ASE to the ISUP ASE, and from the ISUP ASE to the Application Process. A legend on the right lists the primitive names: UCEH_Release.Ind (when 'release' is indicated), APM_UCEH_Error.Ind, APM_U_Data.Req (when 'send notification' indicated), APM_Data.Req, APM_Transfer.Req, and Transfer.Req. A note on the left states: 'Error: APM ASE detects that APM user is not present or node not addressed: sends APM_UCEH_Error.Ind primitive'. A small code 'T11108470-00' is at the bottom right of the stack.](a4b963a07cc368283154762c4b156fe7_img.jpg) + +Primitive names: + UCEH\_Release.Ind + (when 'release' is indicated) + +APM\_UCEH\_Error.Ind + +APM\_U\_Data.Req + (when 'send notification' indicated) + +APM\_Data.Req + +APM\_Transfer.Req + +APM\_Transfer.Req + +Transfer.Req + +T11108470-00 + +Error: APM ASE detects that APM user is not present or node not addressed: sends APM\_UCEH\_Error.Ind primitive + +Figure 9/Q.765 – Dynamic flow in an exchange when an unidentified context or addressing error is detected. The diagram shows a stack of four boxes: Application Process, EH ASE, APM ASE, and ISUP ASE. Arrows indicate the flow of primitives between them. A dashed arrow points from the Application Process to the EH ASE. Solid arrows point from the EH ASE to the APM ASE, from the APM ASE to the ISUP ASE, and from the ISUP ASE to the Application Process. A legend on the right lists the primitive names: UCEH\_Release.Ind (when 'release' is indicated), APM\_UCEH\_Error.Ind, APM\_U\_Data.Req (when 'send notification' indicated), APM\_Data.Req, APM\_Transfer.Req, and Transfer.Req. A note on the left states: 'Error: APM ASE detects that APM user is not present or node not addressed: sends APM\_UCEH\_Error.Ind primitive'. A small code 'T11108470-00' is at the bottom right of the stack. + +**Figure 9/Q.765 – Dynamic flow in an exchange when an unidentified context or addressing error is detected** + +### 13.1.2 Unidentified context and addressing errors handling – Remote error handling + +When an APP is received with Context Identifier "Unidentified Context and Error Handling ASE", the contents are passed to the EH ASE in the same manner as any other APM-user. The procedures described in 13.4.1 are then applied. + +When an APP is received with Context Identifier "Enhanced Unidentified Context and error Handling ASE", the procedures described in 10.2.2.2 are applied. If the node is addressed by the destination address received in the APP, the contents are passed to the EH ASE and the procedures described in 13.4.1 are then applied. + +## 13.2 Reassembly error handling + +When a reassembly error occurs in the APM ASE, the APM\_UCEH\_Error primitive is sent, via SACF, to the EH ASE indicating "reassembly error". The application context identifier and the originating address (if available) are supplied as received by the APM ASE. Actions taken by the EH ASE are according to the ATII. If a notification is to be sent, the reason given indicates "reassembly error". A reassembly error may occur for any segmented message in either a PIN or a PAN, therefore the procedures are equally applicable to both. + +## 13.3 Primitive interface + +The SACF uses the services provided by the EH ASE primitive interface (interface c) in Figure 2) as listed in Table 25. + +**Table 25/Q.765 – Primitives between EH ASE and SACF** + +| Primitive name | Types | Direction (Note) | +|----------------------------------------------|------------|------------------| +| APM_Error | Indication | ➔ | +| UCEH_Release | Indication | ➔ | +| NOTE – Primitive flow from EH ASE to SACF: ➔ | | | + +The EH ASE uses the services provided by the SACF primitive interface (interface c) in Figure 2) as listed in Table 26. + +**Table 26/Q.765 – Primitives between SACF and EH ASE** + +| Primitive name | Types | Direction (Note) | +|---------------------------------------------------------------------------------------|--------------------|------------------| +| APM_UCEH_Error | Indication | ➔ | +| APM_U_Data | Indication/Request | ➔ / ➜ | +| Send_APM_Transit | Request | ➜ | +| NOTE – Primitive flow from SACF to EH ASE: ➔
Primitive flow from EH ASE to SACF: ➜ | | | + +## 13.4 Procedures + +### 13.4.1 Normal procedures – Remote error handling + +When the EH ASE receives an APM\_U\_Data indication primitive with Context Identifier "UCEH ASE", the ASE checks whether this is a "pass-on" node for each context indicated in the "APM-user Context Identifier" field within the Application Transport Notification information. If this is so, for any of the received Context Ids, then a new Application Transport Notification information field is constructed containing the received Context and Reason information for only those contexts for which this is a "pass-on" node. This information is then passed on within the Send\_APM\_Transit indication primitive. + +For those contexts where this node is not to behave as a "pass-on" node then the Context Identifier(s) within the received Notification parameter (clause 14) are used to determine the APM-user(s) which should be notified. If the APM-user indicated by the Context Identifier does not exist, then the associated Notification parameter within the Application Transport Notification Information will be discarded. If the APM-user indicated by the Context Identifier does exist, an APM\_Error indication + +primitive is sent to each APM-user via SACF indicating the Reason for the error. The maintenance function will be notified. + +When the EH ASE receives an APM\_U\_Data indication primitive with Context Identifier "EUCEH ASE", the ASE checks whether each context indicated in the "APM-user Context Identifier" field within the Application Transport Notification Information is supported by the node. If the APM-user indicated by the Context Identifier does not exist, then the associated Notification parameter within the Application Transport Notification Information will be discarded. For the received contexts which are supported by the node, the associated APM-users are notified: an APM\_Error indication primitive is sent to each APM-user via SACF indicating the Reason for the error. The maintenance function will be notified. + +Figure 10 illustrates the dynamic flow of information when the notification is sent to the APM-user. + +![Diagram showing the dynamic flow of information in the PIN to handle reception of APM notification. It shows an Application Process connected to a vertical stack of four ASEs: APM-user ASE, EH ASE, APM ASE, and ISUP ASE. Arrows indicate the flow of primitives from the ASEs up to the Application Process. To the right of each ASE, specific primitive names are listed.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +``` + +graph TD + AP[Application Process] + AUASE[APM-user ASE] + EHASE[EH ASE] + APMASE[APM ASE] + ISUPASE[ISUP ASE] + + ISUPASE --> APMASE + APMASE --> EHASE + EHASE --> AUASE + AUASE --> AP + + subgraph Primitives + direction LR + P1[Primitive names: +(application specific)] + P2[APM_U_Error.Ind +APM_Error.Ind] + P3[APM_U_Data.Ind +APM_Data.Ind] + P4[APM_Transfer.Ind +APM_Transfer.Ind] + P5[Transfer.Ind] + end + +``` + +Primitive names: +(application specific) + +APM\_U\_Error.Ind +APM\_Error.Ind + +APM\_U\_Data.Ind +APM\_Data.Ind + +APM\_Transfer.Ind +APM\_Transfer.Ind + +Transfer.Ind + +T11108480-00 + +Diagram showing the dynamic flow of information in the PIN to handle reception of APM notification. It shows an Application Process connected to a vertical stack of four ASEs: APM-user ASE, EH ASE, APM ASE, and ISUP ASE. Arrows indicate the flow of primitives from the ASEs up to the Application Process. To the right of each ASE, specific primitive names are listed. + +**Figure 10/Q.765 – Dynamic flow in the PIN to handle reception of APM notification** + +### 13.4.2 Normal procedures – Local error handling + +When one or more APM\_UCEH\_Error indication primitive(s) are received by the EH ASE, the Application Transport Instruction Indicators of each are checked to determine the appropriate actions. If any "send notification" bit is set, then a single Notification (clause 14) is constructed indicating the context and associated reason for each APM\_UCEH\_Error indication whose ATII indicated "send notification". The following procedures for the sending of a notification depend on the presence of the originating address (address of the PIN) in the received APM\_UCEH\_Error indication primitives: + +The Notification parameters associated to APM\_UCEH\_Error indication primitives which did not contain any originating address are concatenated to construct an Application Transport Notification information field which is then sent to the APM ASE via the APM\_U\_Data request primitive for transport. The ATII is set to "release call" and "do not send notification". The application context identifier is set to "Unidentified Context and Error Handling ASE". + +Each Notification parameter associated to APM\_UCEH\_Error indication primitives containing the same originating address are concatenated to construct an Application Transport Notification information field which is then sent to the APM ASE via the APM\_U\_Data request primitive for + +transport. The destination address sent by the EH ASE in the APM\_U\_Data request primitive is the originating address previously received in the APM\_UCEH\_Error indication primitive. The address of the node is supplied by the EH ASE in the originating address field of the APM\_U\_Data request primitive. The ATII is set to "release call" and "do not send notification" and the application context identifier is set to "Enhanced Unidentified Context and Error Handling ASE". + +For each of the received APM\_UCEH\_Error indications indicating "release call", a UCEH\_Release indication primitive is sent to the AP via SACF. The maintenance function will be notified. + +### 13.4.3 Exceptional procedures – Context identifier error + +If a context identifier is received as "no information", then the information is discarded and the maintenance function will be notified. + +### 13.4.4 Exceptional procedures – Unrecognized reason value + +If an Unrecognized Reason value is received in the Application Transport Notification Information parameter, then the information is discarded and the maintenance function will be notified. + +## 13.5 Primitive contents + +Tables 27 to 29 define the primitives used across the SACF/EH ASE interface (interface c) in Figure 2). The APM\_U\_Data primitive is described in Table 20. The UCEH\_Release primitive is described in Table 2. + +**Table 27/Q.765 – Contents of the APM\_Error Ind primitive** + +| Parameter | Mandatory/Optional | +|--------------|--------------------| +| Notification | M | + +**Table 28/Q.765 – Contents of the APM\_UCEH\_Error Ind primitive** + +| Parameter | Mandatory/Optional | +|----------------------------------------------|--------------------| +| Reason | M | +| Application Context Identifier | M | +| Application Transport Instruction Indicators | M | +| Originating Address | O | + +**Table 29/Q.765 – Contents of the Send\_APM\_Transit Request primitive** + +| Parameter | Mandatory/Optional | +|----------------------------------------------|--------------------| +| Application Context Identifier | M | +| Application Transport Instruction Indicators | M | +| Application Data | M | + +# 14 Application transport notification information + +The Application Transport Notification information is carried within the Encapsulated Application Information field of the Application Transport Parameter (APP), when the context identifier value is set to "UCEH ASE" or "EUCHEH ASE" (see Figure 11). + +Each Notification parameter within the Application Transport Notification Information field consists of the APM-user Context Identifier and the Reason of the error. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | +|-----------|-----------------------------|---|---|---|---|---|---|--------| +| ext.
1 | APM-user Context Identifier | | | | | | | 1 | +| ext.
1 | Reason | | | | | | | 2 | +| ext.
1 | APM-user Context Identifier | | | | | | | 3 | +| ext.
1 | Reason | | | | | | | 4 | +| ext.
1 | APM-user Context Identifier | | | | | | | n-1 | +| ext.
1 | Reason | | | | | | | n | + +NOTE – n is even and greater than or equal to 2. + +**Figure 11/Q.765 – Application Transport Notification Information** + +- a) *Extension indicators* + - 0 Further octet exists + - 1 Last octet +- b) *APM-user Context Identifier* + - 0 No Information + - 1-16383 Refer to "Application Context Identifier" field in the Application Transport Parameter [3]. +- c) *Reason* + - 0 No Information + - 1 Unidentified Context/Addressing Error + - 2 Reassembly Error + - 3-127 Spare + +# 15 Timers + +See Table 30. + +**Table 30/Q.765 – Timers** + +| Symbol | Time-out value | Cause for initiation | Normal termination | At expiry | Reference | +|--------------------|----------------|---------------------------------------------------------|-------------------------|-----------------------------------|-----------| +| T reass | 10-18 sec | Receipt of APP indicating "new sequence" for reassembly | Receipt of last segment | Apply "reassembly error handling" | 10.2.4.2 | + +# APPENDIX I + +## Example sequence diagrams of APM segmentation + +![Sequence diagram Figure I.1/Q.765 showing the sending of an IAM containing initial APM segments for 2 applications. It details the flow between AP components (APM User 2, APM User 1, ISUP BC, APM) and AE components (APM User 2 ASE, APM User 1 ASE, APM ASE, ISUP ASE).](47a7beddcb8a1b7abdca746967e32bb4_img.jpg) + +| AP | | | | AE | | | | +|------------|------------|---------|-----|----------------|----------------|---------|----------| +| APM User 2 | APM User 1 | ISUP BC | APM | APM User 2 ASE | APM User 1 ASE | APM ASE | ISUP ASE | + +The sequence diagram illustrates the interaction for APM segmentation. On the AP side, there are lifelines for APM User 2, APM User 1, ISUP BC, and APM. On the AE side, there are lifelines for APM User 2 ASE, APM User 1 ASE, APM ASE, and ISUP ASE. A shaded region labeled 'AP COORDINATION' covers the first part of the diagram. A dashed line labeled 'ISUP BASIC CALL SETUP' connects the ISUP BC lifeline to the ISUP ASE lifeline. Within the coordination phase, 'application-specific' messages are sent from APM User 2 and APM User 1 to the APM ASE lifeline. Subsequent messages include 'APM\_Data' from the ASEs to the APM ASE, followed by a series of 'APM\_Transfer' messages. These are followed by 'IAM' and 'APM' messages on the ISUP ASE lifeline, with 'Note 1' and 'Note 4' respectively. Further 'APM\_Transfer' and 'APM' messages follow, with 'Note 2' and 'Note 3' respectively. The final 'APM' message is sent from the ISUP ASE lifeline to the APM lifeline on the AP side. + +Sequence diagram Figure I.1/Q.765 showing the sending of an IAM containing initial APM segments for 2 applications. It details the flow between AP components (APM User 2, APM User 1, ISUP BC, APM) and AE components (APM User 2 ASE, APM User 1 ASE, APM ASE, ISUP ASE). + +T1197930-97 + +- NOTE 1 – IAM includes initial APP for each APM User, these may be "empty". +- NOTE 2 – APM includes last APP segment for APM User 1. +- NOTE 3 – APM includes last APP segment for APM User 2. +- NOTE 4 – Will be repeated for each context that is being segmented. + +**Figure I.1/Q.765 – Sending of an IAM containing initial APM segments for 2 applications** + +![Sequence diagram showing the receipt of an IAM containing initial APM segments for 2 applications. The diagram illustrates the interaction between an AE (ISUP ASE), two APM Users (1 ASE and 2 ASE), and an AP (APM). The sequence starts with an IAM message from the AE. The AE sends APM_Transfer, APM_Transfer (Note 1), More_APP_Info, APP_Acknowledgement, APM_Transfer (Note 5), and APM (Note 4) to the AP. The AP then sends APM_Transfer (Note 2) to User 1 and APM_Transfer (Note 3) to User 2. User 1 sends APM_Data and End_APP_Info to the AP. User 2 sends application-specific data to the AP. The AP sends APM to the AE. The diagram is labeled 'ISUP BASIC CALL SETUP' and 'AP COORDINATION'. A large arrow on the right points to the right, indicating the flow of the sequence. The text 'T1197940-97' is in the bottom right corner.](5eb69662cc4fa7d0d49b4eb22951c204_img.jpg) + +Sequence diagram showing the receipt of an IAM containing initial APM segments for 2 applications. The diagram illustrates the interaction between an AE (ISUP ASE), two APM Users (1 ASE and 2 ASE), and an AP (APM). The sequence starts with an IAM message from the AE. The AE sends APM\_Transfer, APM\_Transfer (Note 1), More\_APP\_Info, APP\_Acknowledgement, APM\_Transfer (Note 5), and APM (Note 4) to the AP. The AP then sends APM\_Transfer (Note 2) to User 1 and APM\_Transfer (Note 3) to User 2. User 1 sends APM\_Data and End\_APP\_Info to the AP. User 2 sends application-specific data to the AP. The AP sends APM to the AE. The diagram is labeled 'ISUP BASIC CALL SETUP' and 'AP COORDINATION'. A large arrow on the right points to the right, indicating the flow of the sequence. The text 'T1197940-97' is in the bottom right corner. + +NOTE 1 – Contains initial APPs for each APM User. + +NOTE 2 – Contains last segment for APM User 1. + +NOTE 3 – Contains last segment for APM User 2. + +NOTE 4 – An APM message is used if there is no concurrent call control message being sent. + +NOTE 5 – Will be repeated for each context that is being segmented. + +**Figure I.2/Q.765 – Receipt of an IAM containing initial APM segments for 2 applications** + +# APPENDIX II + +## Setting of parameter and message instruction indicators + +Tables II.1 and II.2 for PCII and MCII show recommended mappings from the ATII value provided by an application. These tables do not define a definitive coding but should be read as a guide to derive compatibility information from the ATII. + +**Table II.1/Q.765** + +| ATII provided by application | | PCII sent for APP parameter | | | | | | | | +|------------------------------|--------|-----------------------------|-----------------|--------|-----------------|-------------------|-------------------|------------|-------------| +| A | B | A | B | C | D | E | GF | H (Note 1) | JI (Note 1) | +| Release | Notify | Transit | Release | Notify | Discard message | Discard parameter | PONP | EXT | B/N I/W | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 10 | 1 or 0 | 00 | +| 0 | 1 | 0 | 0 | 1 | 0 | 0 | 10 | 1 or 0 | 00 | +| 1 | 0 | 0 | 0 or 1 (Note 2) | 0 | 0 | 0 | 00 or 10 (Note 2) | 1 or 0 | 00 | +| 1 | 1 | 0 | 0 or 1 (Note 2) | 1 | 0 | 0 | 00 or 10 (Note 2) | 1 or 0 | 00 | + +**Table II.1/Q.765 (concluded)** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1 – If bits JI are sent then they should be set as shown, and bit H is set accordingly. | +| NOTE 2 – Two options are identified for the settings of B and GF: | +| a) B=1 and GF=10, i.e. release call at any type A exchange (setting of GF is arbitrary, but proposed value is simplest). | +| b) B=0 and GF=00, i.e. release call at type A exchange only if pass on is not possible. | +| The choice between a) and b) may depend on the types of application deployed in the network, e.g. if a network specific context value is being used, or if only the internationally standardized context values are being used. In the absence of any network specific consideration option b) is proposed to be employed. | + +**Table II.2/Q.765** + +| ATII provided by application | | MCII sent for APM or PRI containing an APP (Note 2) | | | | | | | +|------------------------------|--------|-----------------------------------------------------|--------------------|--------|-----------------|--------------------|---------|-----| +| A | B | A | B | C | D | E | GF | H | +| Release | Notify | Transit | Release | Notify | Discard message | PONP | B/N i/w | EXT | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 00 | 1 | +| 0 | 1 | 0 | 0 | 1 | 0 | 1 | 00 | 1 | +| 1 | 0 | 0 | 0 or 1
(Note 1) | 0 | 0 | 0 or 1
(Note 1) | 00 | 1 | +| 1 | 1 | 0 | 0 or 1
(Note 1) | 1 | 0 | 0 or 1
(Note 1) | 00 | 1 | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1 – Two options are identified for the settings of B and E: | +| a) B=1 and E=1, i.e. release call at any type A exchange (setting of E is arbitrary, but proposed value is simplest.) | +| b) B=0 and E=0, i.e. release call at type A exchange only if pass on is not possible. | +| The choice between a) and b) may depend on the types of application deployed in the network, e.g. if a network specific context value is being used, or if only the internationally standardized context values are being used. In the absence of any network specific consideration option b) is proposed to be employed. | +| NOTE 2 – If the message is also being used to carry other parameters with a more stringent compatibility requirement the MCII setting shown may be overridden. | + +# 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/Q/T-REC-Q.769.1-199912-I_PDF-E/raw.md b/marked/Q/T-REC-Q.769.1-199912-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3d9b4e8347d239370206191241e1799e0b7601db --- /dev/null +++ b/marked/Q/T-REC-Q.769.1-199912-I_PDF-E/raw.md @@ -0,0 +1,751 @@ + + +![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' to the right. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.769.1** + +(12/99) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of Signalling System No. 7 – ISDN user part + +--- + +**Signalling system No. 7 – ISDN user part +enhancements for the support of number +portability** + +ITU-T Recommendation Q.769.1 + +(Previously CCITT Recommendation) + +--- + +# ITU-T Q-SERIES RECOMMENDATIONS + +## **SWITCHING AND SIGNALLING** + +| | | +|----------------------------------------------------------|--------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 | +| General | Q.700 | +| Message transfer part (MTP) | Q.701–Q.709 | +| Signalling connection control part (SCCP) | Q.711–Q.719 | +| Telephone user part (TUP) | Q.720–Q.729 | +| ISDN supplementary services | Q.730–Q.739 | +| Data user part | Q.740–Q.749 | +| Signalling System No. 7 management | Q.750–Q.759 | +| ISDN user part | Q.760–Q.769 | +| Transaction capabilities application part | Q.770–Q.779 | +| Test specification | Q.780–Q.799 | +| Q3 interface | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| BROADBAND ISDN | Q.2000–Q.2999 | + +For further details, please refer to ITU-T List of Recommendations. + +## **ITU-T RECOMMENDATION Q.769.1** + +# **SIGNALLING SYSTEM No. 7 – ISDN USER PART ENHANCEMENTS FOR THE SUPPORT OF NUMBER PORTABILITY** + +## **Summary** + +This Recommendation specifies the relevant ISDN user part enhancements for the support of number portability in a national environment. + +## **Source** + +ITU-T Recommendation Q.769.1 was prepared by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on 3 December 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 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..... | 2 | +| 3 | Definitions ..... | 2 | +| 4 | Abbreviations..... | 3 | +| 5 | Conventions ..... | 3 | +| 6 | Call control and signalling procedures ..... | 3 | +| 6.1 | Separate Directory Number Addressing method ..... | 4 | +| 6.1.1 | Handling of network routing number and directory number ..... | 4 | +| 6.1.2 | Handling of an incomplete directory number ..... | 4 | +| 6.2 | Other addressing methods..... | 4 | +| 6.3 | Actions required in the originating network ..... | 4 | +| 6.3.1 | Onward Routing ..... | 4 | +| 6.3.2 | All Call Query..... | 5 | +| 6.4 | Actions required in the donor network ..... | 5 | +| 6.4.1 | Onward Routing ..... | 5 | +| 6.4.2 | All Call Query..... | 5 | +| 6.5 | Actions required in a transit network..... | 5 | +| 6.5.1 | Onward Routing ..... | 5 | +| 6.5.2 | All Call Query..... | 5 | +| 6.6 | Actions required in the recipient network..... | 5 | +| | Annex A – Procedures for the Concatenated Addressing method ..... | 6 | +| A.1 | General..... | 6 | +| A.2 | Exceptions to clause 6 of this Recommendation ..... | 6 | +| | Annex B – Procedures for the Separate Network Routing Number Addressing method ..... | 7 | +| B.1 | General..... | 7 | +| B.2 | Exceptions to clause 6 of this Recommendation ..... | 7 | +| | Annex C – Procedures to support Query on Release ..... | 8 | +| C.1 | General..... | 8 | +| C.2 | Procedures for QoR with the forward and the backward indications ..... | 8 | +| C.2.1 | Normal procedures..... | 8 | +| C.2.2 | Exceptional procedures..... | 9 | + +| | Page | +|------------------------------------------------------------------------------------------|-------------| +| C.3    Procedures for QoR with the backward indication only ..... | 10 | +| C.3.1    Normal procedures..... | 10 | +| C.3.2    Exceptional procedures..... | 11 | +| Annex D – Procedures to support Dropback..... | 11 | +| D.1    General..... | 11 | +| D.2    Actions required in the networks involved in the first leg..... | 11 | +| D.2.1    Actions required in the originating network..... | 11 | +| D.2.2    Actions required in the transit network ..... | 11 | +| D.2.3    Actions required in the donor network ..... | 11 | +| D.3    Actions required in the networks involved in the second leg ..... | 12 | +| D.3.1    Actions required in the transit network ..... | 12 | +| D.3.2    Actions required in the rerouting network..... | 12 | +| D.4    Actions required in the networks involved in the third leg..... | 12 | +| D.4.1    Actions required in a transit network..... | 12 | +| D.4.2    Actions required in the recipient network ..... | 12 | +| Annex E – Procedures for forward transfer of number portability status information ..... | 13 | +| E.1    General..... | 13 | +| E.2    Normal procedures..... | 13 | +| E.2.1    Actions required at an initiating exchange ..... | 13 | +| E.3    Exceptional procedures..... | 13 | + +## **Recommendation Q.769.1** + +# **SIGNALLING SYSTEM No. 7 – ISDN USER PART ENHANCEMENTS FOR THE SUPPORT OF NUMBER PORTABILITY** + +*(Geneva, 1999)* + +# **1 Scope** + +In a national environment with support of number portability, the existing ISUP procedures as specified in Recommendation Q.764 [1] apply with the modifications as specified in this Recommendation. + +NOTE – ISUP formats and codes are described in Recommendation Q.763 [2]. + +The addressing method for number portability in a network will have an impact on existing functions and services. The impact is network and implementation dependent and outside the scope of this Recommendation. + +With the introduction of the procedures for number portability as defined in this Recommendation, backwards compatibility with the ISUP according to Recommendation Q.767 is not possible. + +In addition to the main text, the following annexes are part of this Recommendation: + +- Annex A describes an alternative addressing method making use of a concatenated addressing format. This addressing method may typically be useful as an intermediate solution in some networks as it may limit the impact on existing functions and services. +- Annex B describes another addressing method making use of the Separate Network Routing Number Addressing method. It may be used within the network of a service provider. This addressing method may typically be useful in some networks as it may limit the impact on existing network functions and service handling. +- Annex C describes the additional network capabilities for Query on Release that may be used within the network of a service provider. These additional capabilities may typically be useful in some networks for network efficiency reasons. +- Annex D describes the additional network capabilities for Dropback that may be used within the network of a service provider. These capabilities make use of the procedures for Pivot Routing or Redirection as specified in Recommendation Q.730 [3]. These additional capabilities may typically be useful in some networks for network efficiency reasons. +- Annex E describes the procedures for forward transfer of number portability status information that may be used within the network of a service provider. This service logic may be used in some networks in order to minimize the number of number portability data base queries and reduce the risk of looping due to number portability data base mismatches. + +The use of these annexes is up to network operator decisions, bilateral agreement, regulatory demands and/or implementation reasons. These considerations and possible pre-conditions are outside the scope of this Recommendation. + +Number portability introduces new requirements to retain full service transparency of ISDN supplementary services like Completion of Calls to Busy Subscriber (CCBS), which use non-circuit related signalling. The identified relay functions to meet these requirements are elaborated in Recommendation Q.730 [3], subclause "Relay methods for non-circuit related signalling". + +# 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 Q.764 (1999), *Signalling System No. 7 – ISDN User Part signalling procedures*. +- [2] ITU-T Recommendation Q.763 (1999), *Signalling System No. 7 – ISDN User Part formats and codes*. +- [3] ITU-T Recommendation Q.730 (1999), *ISDN User Part supplementary services*. + +# 3 Definitions + +This Recommendation defines the following terms: + +- 3.1 Directory number:** A number in the national numbering scheme that is allocated to a customer for a telephony service. Allocation of the directory number is made directly by the numbering plan authority to the customer, or indirectly when blocks of numbers are managed by service providers. +- 3.2 Donor exchange:** The initial exchange where a number was located before ever being ported. +- 3.3 Donor network:** The initial network where a number was located before ever being ported. +- 3.4 Initiating exchange:** An exchange that requires and obtains the routing information for number portability. +- 3.5 Initiating network:** A network that requires and obtains the routing information for number portability. +- 3.6 Network routing number:** A number that is derived and used by the network to route the call towards a ported number. +- 3.7 Originating exchange:** The exchange serving a calling end user. For most incoming international calls, the originating exchange is effectively the international gateway. For carrier selection, the first exchange of the selected carrier effectively becomes the entry to the originating network for routing purposes. +- 3.8 Originating network:** The network serving a calling end user. For most incoming international calls, the originating network is effectively the network containing the international gateway. For carrier selection, the first exchange of the selected carrier effectively becomes the entry to the originating network for routing purposes. +- 3.9 Recipient exchange:** The exchange where a number is located after being ported. +- 3.10 Recipient network:** The network where a number is located after being ported. +- 3.11 Transit exchange:** An exchange between two exchanges, e.g. between the initiating exchange and the recipient exchange. +- 3.12 Transit network:** A network between two networks, e.g. between the initiating network and the recipient network. +- 3.13 Rerouting:** Pivot routing or redirection as specified in [3]. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|------|-------------------------------------| +| ACM | Address Complete message | +| ANM | Answer message | +| CON | Connect message | +| CPG | Call Progress message | +| DN | Directory number | +| IAM | Initial Address message | +| ISUP | ISDN User Part | +| NoA | Nature of Address indicator | +| NRN | Network routing number | +| QoR | Query on Release | +| SAM | Subsequent Address message | +| SDM | Subsequent Directory Number message | + +# 5 Conventions + +1) The name of each element of the following classes of terms is capitalized: + +- indicators; +- parameters; +- messages; +- methods/functions. + +Examples: Called Party Number parameter, Initial Address message, All Call Query, Query on Release, Separate Directory Number Addressing method, Separate Network Routing Number Addressing method. + +2) The definition of a parameter value is written in *italics* and is put between quotation marks. + +Example: NoA value 0000011 – "*national (significant) number*". + +# 6 Call control and signalling procedures + +This clause describes the call control and signalling procedures for the methods All Call Query and Onward Routing (see [4] and [5], Bibliography). + +In a number portability environment, the directory number (DN) is not sufficient to route the call. There is a need to derive a network routing number (NRN) (see [4] and [5], Bibliography). Once the NRN has been determined, the routing in the network will be based on this NRN. As the NRN is always a complete address, sending of additional digits in overlap operation applies only to the directory number (DN) information. The DN is transferred along with the call to identify the called ported subscriber. The following subclauses describe the handling of the NRN and DN. + +## 6.1 Separate Directory Number Addressing method + +#### 6.1.1 Handling of network routing number and directory number + +The network routing number and the directory number are transferred in the Initial Address message (IAM) as follows. + +The network routing number (NRN) is transferred in the Called Party Number parameter and the directory number (DN) is transferred in the Called Directory Number parameter. + +The Called Party Number parameter is coded with NoA value 0000110 – "*network routing number in national (significant) number format*", and the Called Directory Number parameter is coded with NoA value 0000011 – "*national (significant) number*". + +NOTE – For specific applications, the NoA values 0000011 – "*national (significant) number*" and 0000111 – "*network routing number in network specific number format*" may alternatively be chosen by certain operators for the coding of the Called Party Number parameter, possibly with additional information to maintain the number portability routing efficiency. + +#### 6.1.2 Handling of an incomplete directory number + +If the complete directory number is not available, the following procedures are required: + +##### a) *Actions at the initiating exchange* + +Called directory number digits received after the Initial Address message (IAM) has been sent shall be sent in Subsequent Directory Number message(s) (SDM) instead of Subsequent Address message(s) (SAM). + +##### b) *Actions at the intermediate exchange* + +An intermediate exchange shall transit the SDM message and shall preserve the received additional digits related to the directory number information as part of the stored IAM information. SDMs received during the circuit selection process may be included in the IAM. + +NOTE – The storage of additional digits is required to avoid loss of digits in case an automatic repeat attempt is required, see 2.8.1/Q.764 [1]. + +##### c) *Actions at the recipient exchange* + +The exchange that is addressed by the NRN, i.e. the node that completes the call with the directory number, shall accept additional digits received in a SDM as part of the directory number. + +## 6.2 Other addressing methods + +Instead of the addressing method according to 6.1, network operators may alternatively decide to apply the Concatenated Addressing method (see Annex A) or the Separate Network Routing Number Addressing method (see Annex B). + +NOTE – Existing ISUP procedures may be applied on the interconnection interface between networks. In this case, the DN is contained in the Called Party Number parameter with NoA value 0000011 – "*national (significant) number*", although in that case no additional routing information is transferred. + +## 6.3 Actions required in the originating network + +### 6.3.1 Onward Routing + +The originating network will apply the procedures as defined in Recommendation Q.764 [1]. + +#### **6.3.2 All Call Query** + +When the initiating exchange is located in the originating network, it has to determine whether the DN is ported or not. + +If the DN is not ported, the existing ISUP procedures apply without modification. + +If the DN is ported, the initiating exchange shall derive the network routing number and shall route the call towards the recipient network. The transfer of the NRN and DN shall be made according to 6.1. + +## **6.4 Actions required in the donor network** + +### **6.4.1 Onward Routing** + +Since the donor network acts as the initiating network in this case, it shall determine whether the DN is ported or not. + +If the DN is not ported, the existing ISUP procedures apply without modification. + +If the DN is ported, the initiating exchange shall derive the network routing number and shall route the call towards the recipient network. The transfer of the NRN and DN shall be made according to 6.1. + +### **6.4.2 All Call Query** + +When the initiating exchange is located in the donor network, the same procedures apply as specified in 6.3.2. + +## **6.5 Actions required in a transit network** + +#### **6.5.1 Onward Routing** + +With the Onward Routing method, there is no impact on a transit network between the originating and the donor networks. + +For a transit network between the donor network and the recipient network, the NRN and the DN are handled according to 6.1. + +#### **6.5.2 All Call Query** + +When the initiating exchange is located in a transit network, the same procedures apply as specified in 6.3.2. + +For a transit network between the initiating network and the recipient network, the NRN and the DN are handled according to 6.1. + +## **6.6 Actions required in the recipient network** + +This subclause applies independently of the method used for number portability, e.g. Onward Routing or All Call Query. + +The recipient network handles the received NRN and DN according to 6.1. + +Depending on the agreement, the recipient network may find and use its own NRN, or use the NRN received. The NRN is used to reach the recipient exchange of the called ported subscriber. The recipient exchange uses the DN to identify the called ported subscriber and completes the call. + +# ANNEX A + +## Procedures for the Concatenated Addressing method + +### A.1 General + +This annex describes the procedures for the Concatenated Addressing method. It specifies the exceptions to clause 6 which are needed for the support of the Concatenated Addressing method. + +### A.2 Exceptions to clause 6 of this Recommendation + +#### To clause 6 Call control and signalling procedures: + +No exception. + +#### To 6.1.1 Handling of network routing number and directory number: + +The text is replaced by the following: + +The network routing number and directory number are transferred in the Initial Address message as follows. + +The DN is contained in the Called Party Number parameter and is prefixed by some digits used as a NRN. Two alternatives for the coding of the NoA parameter field are possible: + +NoA value 0000011 – *"national (significant) number"*; + +NoA value 0001000 – *"network routing number concatenated with called directory number"*. + +##### To 6.1.2 Handling of an incomplete directory number: + +Not applicable. Overlap procedures as described in 2.1.2/Q.764 [1] apply. + +#### To 6.2 Other addressing methods: + +In this case, the Concatenated Addressing method is applied. + +#### To 6.3 Actions required in the originating network: + +##### To 6.3.1 Onward Routing: + +No exception. + +#### To 6.3.2 All Call Query: + +No exception. + +#### To 6.4 Actions required in the donor network: + +#### To 6.4.1 Onward Routing: + +No exception. + +#### To 6.4.2 All Call Query: + +No exception. + +#### To 6.5 Actions required in a transit network: + +#### To 6.5.1 Onward Routing: + +No exception. + +#### To 6.5.2 All Call Query: + +No exception. + +#### To 6.6 Actions required in the recipient network: + +No exception. + +## ANNEX B + +## **Procedures for the Separate Network Routing Number Addressing method** + +### **B.1 General** + +This annex describes the procedures for the Separate Network Routing Number Addressing method. It specifies the exceptions to clause 6 which are needed for the support of the Separate Network Routing Number Addressing method. + +### **B.2 Exceptions to clause 6 of this Recommendation** + +#### **To clause 6 Call control and signalling procedures:** + +No exception. + +##### **To 6.1.1 Handling of network routing number and directory number:** + +The text is replaced by the following: + +The network routing number and directory number are transferred in the Initial Address message as follows. + +The NRN is transferred in the Network Routing Number parameter. The DN is transferred in the Called Party Number parameter with NoA value 0000011 – "*national (significant) number*". + +##### **To 6.1.2 Handling of an incomplete directory number:** + +Not applicable, the text is replaced by the following: + +Overlap procedures as described in 2.1.2/Q.764 [1] apply with the following exception. + +The routing is performed based on the contents of the Network Routing Number parameter. The digits in the SAMs are not relevant for routing the call, but relate only to the DN. The SAMs have to be processed accordingly. + +#### **To 6.2 Other addressing methods:** + +In this case, the Separate Network Routing Number Addressing method is applied. + +#### **To 6.3 Actions required in the originating network:** + +#### **To 6.3.1 Onward Routing:** + +No exception. + +#### **To 6.3.2 All Call Query:** + +No exception. + +#### **To 6.4 Actions required in the donor network:** + +#### **To 6.4.1 Onward Routing:** + +No exception. + +#### **To 6.4.2 All Call Query:** + +No exception. + +#### **To 6.5 Actions required in a transit network:** + +#### **To 6.5.1 Onward Routing:** + +No exception. + +#### **To 6.5.2 All Call Query:** + +No exception. + +#### **To 6.6 Actions required in the recipient network:** + +No exception. + +# **ANNEX C** + +## **Procedures to support Query on Release** + +### **C.1 General** + +This annex describes the procedures for the support of Query on Release. + +NOTE – Since this number portability method may result in an increased number of Release messages from specific destinations (and in particular Release messages before answer), measures may be necessary to avoid possible blocking of circuits and possible faulty generation of alarms as a result of the deployed network management functionality. + +### **C.2 Procedures for QoR with the forward and the backward indications** + +This procedure requires the use of optional forward information. The procedure provides a general mechanism that can be used by an exchange that decides that the call should be released because the called number is ported out. If the QoR Capability parameter is present in the IAM, such an exchange can invoke the QoR mechanism to request a preceding exchange, involved in the call, to route that call to the recipient network. If none of the preceding nodes support QoR (i.e. the QoR Capability parameter is not received), then this exchange shall forward the call on to the new called number (e.g. using Onward Routing as a fallback method). + +General interactions with supplementary services are for further study. + +#### **C.2.1 Normal procedures** + +##### **C.2.1.1 Originating exchange** + +An originating exchange that wishes to offer to perform the QoR function shall store the sent IAM information (and the SAM information, if any) and shall send the QoR Capability parameter in the IAM with a parameter compatibility information. The IAM information (and the SAM information, if any) must be retained until: + +- the ACM message with a Called Party's Status indicator (Backward Call Indicators parameter) set to "*subscriber free*"; or +- the CPG message with a Called Party's Status indicator (Backward Call Indicators parameter) set to "*subscriber free*"; or +- the CPG message with a Event indicator (Event Information parameter) set to "*alerting*"; or +- the CON message; or +- the ANM message, + +is received. + +##### **C.2.1.2 Intermediate exchange** + +The intermediate exchange with QoR capability (capable to perform the query) shall store the received IAM (and the SAM information, if any) and shall pass unchanged the QoR Capability parameter along with parameter compatibility information to the subsequent exchange. + +An intermediate exchange may also be the first exchange to indicate that QoR is possible, in which case it performs the actions described for the originating exchange in C.2.1.1. + +The IAM information (and the SAM information, if any) must be retained until: + +- the ACM message with a Called Party's Status indicator (Backward Call Indicators parameter) set to "*subscriber free*"; or +- the CPG message with a Called Party's Status indicator (Backward Call Indicators parameter) set to "*subscriber free*"; or +- the CPG message with a Event indicator (Event Information parameter) set to "*alerting*"; or +- the CON message; or +- the ANM message, + +is received. + +The intermediate exchange with no QoR capability (it is not capable to perform the query but it may know about the QoR Capability parameter) shall pass the QoR Capability parameter unchanged along with parameter compatibility information to the subsequent exchange either because it has the knowledge of the QoR Capability parameter or through the normal compatibility procedures. + +##### C.2.1.3 Gateway exchange + +A gateway exchange shall discard the QoR Capability parameter either because it has the knowledge of this parameter or through the normal compatibility procedures. + +##### C.2.1.4 Donor exchange + +An exchange which determines that a called number is ported out and which wishes to invoke the QoR procedure shall check the presence of the QoR Capability parameter to determine whether QoR is possible for the current call. If QoR is possible, it shall release the call, using the cause value #14 (QoR: ported number). + +##### C.2.1.5 Exchange receiving a Release message with the QoR cause value + +The actions at an exchange having the QoR capability and receiving a Release message with the cause value #14 (QoR: ported number) will depend on whether the IAM received from the prior exchange, if any, had included a QoR Capability parameter and on the service logic at that exchange as follows: + +- 1) If a prior exchange had the QoR capability and the service logic determines that a prior exchange should perform the query, then the Release message is passed back unchanged. +- 2) If + - the service logic determines that this exchange should perform the query; or + - there is no exchange with the QoR capability; or + - there is no prior exchange,then the exchange (having the QoR capability) should perform the query to the database and progress the call. + +#### C.2.2 Exceptional procedures + +If a Release message with the cause value #14 (QoR: ported number) is received in the originating exchange and that exchange had not sent the QoR Capability parameter in the IAM, the call shall be released with cause value #31 (normal, unspecified). + +### **C.3 Procedures for QoR with the backward indication only** + +These procedures apply within networks where at least one exchange always exists with QoR capability. They provide a general mechanism that can be used by an exchange that decides that the call should be released because the called number is ported out. Such an exchange can invoke the QoR mechanism to request a preceding exchange involved in the call to route that call to the recipient network. + +General interactions with supplementary services are for further study. + +#### **C.3.1 Normal procedures** + +##### **C.3.1.1 Originating exchange** + +An originating exchange that wishes to offer to perform the QoR function shall store the sent IAM information (and the SAM information, if any). + +The IAM information (and the SAM information, if any) must be retained until: + +- the ACM message with a Called Party's Status indicator (Backward Call Indicators parameter) set to "*subscriber free*"; or +- the CPG message with a Called Party's Status indicator (Backward Call Indicators parameter) set to "*subscriber free*"; or +- the CPG message with a Event indicator (Event Information parameter) set to "*alerting*"; or +- the CON message; or +- the ANM message, + +is received. + +##### **C.3.1.2 Intermediate exchange** + +The intermediate exchange that wishes to offer to perform the QoR function shall store the received IAM (and the SAM information, if any). + +The IAM information (and the SAM information, if any) must be retained until: + +- the ACM message with a Called Party's Status indicator (Backward Call Indicators parameter) set to "*subscriber free*"; or +- the CPG message with a Called Party's Status indicator (Backward Call Indicators parameter) set to "*subscriber free*"; or +- the CPG message with a Event indicator (Event Information parameter) set to "*alerting*"; or +- the CON message; or +- the ANM message, + +is received. + +##### **C.3.1.3 Donor exchange** + +An exchange which determines that a called number is ported out and wishes to invoke the QoR procedure shall release the call, using the cause value #14 (QoR: ported number). + +##### **C.3.1.4 Exchange receiving a Release message with the QoR cause value** + +The actions at an exchange receiving a Release message with the cause value #14 (QoR: ported number) will depend on the service logic at that exchange as follows: + +- 1) If the service logic determines that a prior exchange should perform the query, then the Release message is passed back unchanged. + +2) If: + +- the service logic determines that this exchange should perform the query; or +- there is no prior exchange, + +then the exchange should perform the query to the database and progress the call. + +#### C.3.2 Exceptional procedures + +If a Release message with cause value #14 (QoR: ported number) is received in an exchange which is not capable to perform the query, and there is no prior exchange, then the call shall be released with cause value #31 (normal, unspecified). + +# ANNEX D + +## Procedures to support Dropback + +### D.1 General + +This annex describes the procedures for the support of the Dropback method. + +These procedures make use of the Pivot Routing mechanism or Redirection mechanism as specified in Recommendation Q.730 [3]. Which mechanism is used is left to the network operator. + +NOTE – Since this number portability method may result in an increased number of Release messages from specific destinations (and in particular Release messages before answer), measures may be necessary to avoid possible blocking of circuits and possible faulty generation of alarms as a result of the deployed network management functionality. + +### D.2 Actions required in the networks involved in the first leg + +This subclause describes the behaviour of the networks involved in the first leg, i.e. the leg from the originating network to and including the donor network. + +#### D.2.1 Actions required in the originating network + +The originating network will apply the procedures as in Recommendation Q.764 [1]. + +An originating network that offers to perform the rerouting function (i.e. Pivot Routing or Redirection function) shall send the appropriate parameter(s) in the IAM according to Recommendation Q.730 [3]. The originating network shall include in the IAM the Pivot Routing (or Redirect) Forward Information parameter with Performing Pivot (or Redirect) indicator with the appropriate Performing Pivot (or Redirect) Reason value(s) (e.g. "*service provider portability*") and Pivot (or Redirect) Possible indicator value(s). + +#### D.2.2 Actions required in the transit network + +The transit network in the first leg will apply the procedures as in Recommendation Q.764 [1]. + +A transit network may also be the first network to indicate that a rerouting function is possible (or is possible for a particular reason), in which case it performs the actions described for the originating network in D.2.1. + +#### D.2.3 Actions required in the donor network + +Since the donor network acts as the initiating network for Dropback, it shall determine whether the directory number (DN) is ported or not. + +If the result is that the DN is not ported, the existing ISUP procedures apply without modification. + +If the result is that the DN has been ported, the initiating network shall derive the network routing number and invoke the Dropback procedure. + +The network routing number (NRN) shall be sent back to the preceding network by using the Facility message (Pivot Routing method) or the Release message (Redirection method). The invoking reason for rerouting information (with value indicating the reason for the Dropback, e.g. "*service provider portability*") shall be returned within the backward message. + +The network routing number (NRN) is transferred backward in the Redirection Number parameter. + +The Redirection Number parameter is coded with NoA value 0000110 – "*network routing number in national (significant) number format*". + +NOTE – For specific applications the NoA values 0000011 – "*national (significant) number*" and 0000111 – "*network routing number in network specific number format*" may be chosen by certain operators for the coding of the Redirection Number parameter, possibly with additional information to maintain the number portability routing efficiency. + +If the preceding network(s) have not offered to perform the rerouting function, the action required in the donor network is the same as described in 6.4.1. + +### **D.3 Actions required in the networks involved in the second leg** + +This subclause describes the behaviour of the networks involved in the second leg, i.e. the leg from the donor network to and including the rerouting network (i.e. the network which performs the Pivot Routing or redirects the call as specified in Recommendation Q.730 [3]). + +#### **D.3.1 Actions required in the transit network** + +If the transit network is not the rerouting network, it will apply the actions as described for intermediate exchanges in Recommendation Q.730 [3]. + +#### **D.3.2 Actions required in the rerouting network** + +The rerouting network will apply a rerouting procedure as specified in Recommendation Q.730 [3]. The IAM toward the recipient network will contain the NRN as received from the donor network and the DN as stored in rerouting network. + +### **D.4 Actions required in the networks involved in the third leg** + +This subclause describes the behaviour of the networks involved in the third leg, i.e. the leg from the rerouting network to and including the recipient network. + +#### **D.4.1 Actions required in a transit network** + +For a transit network between the rerouting network and the recipient network, the NRN and DN are handled according to clause 6. + +#### **D.4.2 Actions required in the recipient network** + +The actions required in the recipient network are specified in 6.6. + +## Procedures for forward transfer of number portability status information + +### E.1 General + +This annex describes the procedures for the support of forward transfer of number portability status information in addition to the call control and signalling procedures as defined in clause 6. These procedures provide a mechanism that may be used to signal an indication as to whether the number portability status of the called number has been determined. This indication may be included for both ported and non-ported numbers. + +NOTE – Support of all or part of these procedures for the support of forward transfer of number portability status information depends on the service logic of each exchange in the network. + +### E.2 Normal procedures + +#### E.2.1 Actions required at an initiating exchange + +The following procedures support the handling of number portability status information on determination by an initiating exchange as to whether a call is ported or not: + +- 1) If the DN is determined not to be ported, a Number Portability Forward Information parameter shall be sent in the IAM with the Number Portability Status indicator set to "*number portability query done for called number, non-ported called subscriber*". +- 2) If the DN is determined to be ported, a Number Portability Forward Information parameter shall be sent in the IAM with the Number Portability Status indicator set to "*number portability query done for called number, ported called subscriber*". + +The following procedures support the handling of the Number Portability Status indicator on receipt of a Number Portability Forward Information parameter by a subsequent initiating exchange: + +- 1) If the value carried in the Number Portability Status indicator is either "*no indication*" or "*number portability query not done for called number*", then the exchange shall determine whether the DN is ported or not. +- 2) If the value carried in the Number Portability Status indicator is either "*number portability query done for called number, non-ported called subscriber*" or "*number portability query done for called number, ported called subscriber*", then the exchange may determine again whether the DN is ported or not, depending on the service logic of the exchange. + +### E.3 Exceptional procedures + +If an IAM is received in an initiating exchange with a Number Portability Status indicator with the value "*number portability query done for called number, ported called subscriber*" but without a network routing number, then the exchange shall determine whether the DN is ported or not. + +# Bibliography + +The following documents contain background information. + +- [4] ITU-T Supplement 4 to the Q-series Recommendations (1998), *Number portability – Call control for capability set 1 service provider portability (All Call Query and Onward Routing)*. +- [5] ITU-T Supplement 3 to the Q-series Recommendations (1998), *Number portability – Scope and capability set 1 architecture*. + + + + + +# 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 | + +\*17787\* \ No newline at end of file diff --git a/marked/Q/T-REC-Q.818-201205-I_PDF-E/raw.md b/marked/Q/T-REC-Q.818-201205-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..55946f77144f51af35bd96a6b6a1ca252f7d8ff7 --- /dev/null +++ b/marked/Q/T-REC-Q.818-201205-I_PDF-E/raw.md @@ -0,0 +1,2241 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.818** + +(05/2012) + +SERIES Q: SWITCHING AND SIGNALLING + +Q3 interface + +--- + +**Web services-based management services** + +Recommendation ITU-T Q.818 + +![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 Q-SERIES RECOMMENDATIONS + +## SWITCHING AND SIGNALLING + +| | | +|--------------------------------------------------------------------------------|--------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120-Q.499 | +| DIGITAL EXCHANGES | Q.500-Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 | +| Q3 INTERFACE | Q.800-Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 | +| INTELLIGENT NETWORK | Q.1200-Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 | +| BROADBAND ISDN | Q.2000-Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T Q.818 + +# Web services-based management services + +## Summary + +Recommendation ITU-T Q.818 defines a set of services required to support service-oriented web services-based interfaces and along with Recommendation ITU-T X.782 composes a framework for web services-based network management interfaces. It specifies protocol requirements, how some well-known web services should be used in network management interfaces and defines some network management-specific support services. The WSDL interface definitions for the network management-specific support services are also provided. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T Q.818 | 2012-05-14 | 2 | + +## Keywords + +Distributed processing, extensible markup language (XML), managed objects, network management interfaces, service-oriented, universal description discovery and integration (UDDI), web services (WS), web services description language (WSDL), XML schema. + +## 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 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Web services-based network management services goal and requirements ..... | 3 | +| 6.1 Goals..... | 3 | +| 6.2 Information modelling dependencies ..... | 4 | +| 6.3 Scoping..... | 5 | +| 6.4 Notifications ..... | 5 | +| 7 Framework overview and protocol requirements ..... | 6 | +| 7.1 Framework overview..... | 6 | +| 7.2 Protocol, languages and services requirements ..... | 7 | +| 8 Usage of well-known web services ..... | 7 | +| 8.1 Web services base notification ..... | 7 | +| 8.2 UDDI service registration..... | 16 | +| 9 Framework support services ..... | 21 | +| 9.1 Heartbeat service ..... | 21 | +| 9.2 Multiple object operation service ..... | 23 | +| 9.3 Containment service ..... | 29 | +| 10 Compliance and conformance ..... | 31 | +| 10.1 System conformance points..... | 31 | +| 10.2 Basic conformance profile..... | 31 | +| Annex A – WSDL definition of framework support services ..... | 33 | +| A.1 ITU notification service WSDL and XML schema definition ..... | 33 | +| A.2 ITU heartbeat service WSDL and XML schema definition..... | 44 | +| A.3 ITU MOO service WSDL and XML schema definition ..... | 46 | +| A.4 ITU containment service WSDL and XML schema definition..... | 51 | +| Bibliography..... | 55 | + + + +## Web services-based management services + +# 1 Scope + +The network management architecture defined in [ITU-T M.3010] introduces the use of multiple management protocols. So far, the GDMO/CMIP and CORBA GIOP/IIOP are possible choices at the application layer. Based on the management interface specification methodology defined in [ITU-T M.3020], more technology-based paradigms can be introduced into network management interfaces, and web services/XML is now an additional paradigm for network management. + +This Recommendation, together with [ITU-T X.782], sets out to define a framework for defining how interfaces supported by management systems and network elements should be modelled using web services/XML schema. It is the scope of this Recommendation to provide the following guidelines or instructions: + +- protocol requirements for using web services in network management; +- how a web services-based notification service is used in network management interfaces; +- how a new service is registered and accessed using UDDI; +- how to monitor the availability of a web services notification forwarding mechanism; +- how to access multiple managed objects in one operation; +- compliance and conformance requirements. + +# 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 X.701] Recommendation ITU-T X.701 (1997), *Information technology – Open Systems Interconnection – Systems management overview*. +- [ITU-T X.703] Recommendation ITU-T X.703 (1997), *Information technology – Open Distributed Management Architecture*. +- [ITU-T X.782] Recommendation ITU-T X.782 (2012), *Guidelines for defining web services for managed objects and management interfaces*. +- [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.3702] Recommendation ITU-T M.3702 (2010), *Common management services – Notification management – Protocol neutral requirements and analysis*. +- [OASIS UDDI] OASIS Specification (2004), *Universal Description, Discovery and Integration (UDDI) v3.0.2*. +- [OASIS WSN] OASIS Specification (2006), *Web Services Base Notification v1.3*. + +- [W3C SOAP] W3C Recommendation (2007), *SOAP Version 1.2 Part 1: Messaging Framework (Second Edition)*. +- [W3C XML] W3C Recommendation (2000), *Extensible Markup Language (XML) 1.0 Second Edition*. +- [W3C XS-P1] W3C Recommendation (2004), *XML Schema Part 1: Structures Second Edition*. +- [W3C XS-P2] W3C Recommendation (2004), *XML Schema Part 2: Datatypes Second Edition*. +- [W3C WSDL] W3C Recommendation (2001), *Web Services Description Language (WSDL) 1.1*. + +# 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 **managed object class** [ITU-T X.701] +- 3.1.3 **manager** [ITU-T M.3020] +- 3.1.4 **notification** [ITU-T X.703] + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +- CMIP Common Management Information Protocol +- CORBA Common Object Request Broker Architecture +- GDMO Guidelines for the Definition of Managed Objects +- GIOP General Inter-ORB Protocol +- IIOP Internet Inter-ORB Protocol +- MO Managed Object +- MOC Managed Object Class +- MOO Multiple Object Operation +- SOAP Simple Object Access Protocol +- TMN Telecommunications Management Network +- UDDI Universal Description Discovery and Integration +- WS Web Services +- WSDL Web Services Description Language + +| | | +|-----|----------------------------| +| WSN | Web Services Notification | +| XML | extensible Markup Language | +| XSD | XML Schema Definition | + +# 5 Conventions + +A few conventions are followed in this Recommendation to make the reader aware of the purpose of the text. While most of the Recommendation is normative, paragraphs succinctly stating mandatory requirements to be met by a management system (managing and/or managed) are preceded by a boldface "R" enclosed in parentheses, followed by a short name indicating the subject of the requirement, and a number. For example: + +**(R) EXAMPLE-1:** An example mandatory requirement. + +Requirements that may be optionally implemented by a management system are preceded by an "O" instead of an "R" For example: + +**(O) OPTION-1:** An example optional requirement. + +The requirement statements are used to create compliance and conformance profiles. + +Many examples of WSDL and XML schema are included in this Recommendation, and WSDL specifying management specific services and supporting data types are included in a normative annex. The WSDL and XML schema are written in a 10 point courier typeface: + +``` + + + + +``` + +# 6 Web services-based network management services goal and requirements + +This clause describes the key goals of the services framework and the requirements that help the web services-based network management services support these goals. Clause 6.1 introduces the goals of the web services framework. Clause 6.2 then provides terminology and requirements. The requirements in this clause are requirements that the framework must satisfy and which are based on telecommunications management needs. Clauses 7, 8, 9 then describe a framework that meets these needs and defines how to achieve the requirements of this clause by using web services in a certain way. + +## 6.1 Goals + +This Recommendation sets out to define a framework for defining how interfaces supported by management systems and network elements should be modelled. Some key goals of the framework are identified here: + +- application interoperability +- common usage of well-known web services. + +This clause elaborates on these two goals. + +### 6.1.1 Application interoperability + +A key goal of the network management architecture and in particular the information architecture, is to promote a standard framework for providing interoperability and information exchange between systems from a diverse set of network management system suppliers. Interoperability between systems involves many aspects of development. At its lowest layer, a common communication mechanism must be in place to support a common syntax, the establishment of + +connectivity and the exchange of operation requests/replies between systems. This aspect of interoperability is inherently supported by the web services specifications. + +For network management, there is the need to provide application interoperability. That is, management systems from diverse suppliers will be utilized within a single administration's TMN to support different functions necessary to support the management of its networks. To simplify integration of these various suppliers' systems, they must agree on the semantics of the information being exchanged. This is accomplished with the specification of an information model. Guidelines for the definition of web services-based information models are specified in [ITU-T X.782], but the services defined here should support those guidelines. + +### **6.1.2 Common usage of well-known web services** + +A second aspect of this framework is the definition of common usage and profiling of the distributed processing environment of choice. This aspect of the framework should indicate the reasonable expectations network management system suppliers may have for one another. Rather than redefining the interface capabilities needed to support common network management functions such as notification filtering with each information model, the modelling guidelines in [ITU-T X.782] rely upon a set of support services. These support services enable the information models to be simpler, and also enhance interoperability. + +In defining these services, special effort will be taken to make use of some of the well-known web services. Specifically, this Recommendation will address the use of the web services notification as defined in [OASIS WSN] and web services UDDI service registration as defined in [OASIS UDDI] which will impact system interoperability (i.e., issues involving the use of web services within a single system are outside the scope of this Recommendation). Where network management needs cannot be met by the above mentioned well known web services, additional services will be defined. + +## **6.2 Information modelling dependencies** + +As described in the previous clause, the explicit modelling of resources that are manageable across an interface is central to application interoperability. The guidelines for defining web services-based managed objects detailed in [ITU-T X.782] describe the rules for modelling manageable resources. They also embody several decisions that must be supported by the network management web services-based services framework. This clause summarizes those points. + +### **6.2.1 Access granularity** + +Web services interface granularity refers to the relationship between the resources that are modelled on an interface and the means by which they are accessed using web services. [ITU-T X.782] uses a service-grain modelling approach which means each modelled resource is only accessible through a specific web service. The objects that represent manageable resources are called managed objects. + +### **6.2.2 Representation of containment and naming** + +Containment is a logical representation of how modelled resources contain other modelled resources. Containment has traditionally been a very important relationship in network management applications because it is a convenient means of identifying the large number of resources that typically must be managed. [ITU-T X.782] guidelines require that a unique name be assigned to each managed object, based in part on the name of the object that contains it. The web services-based management services must provide the means to store these names (and hence the containment relationships they represent). + +### 6.2.3 Object creation and deletion + +The web services platforms do not provide clients with the means to create or delete objects on remote systems. Instead, these functionalities are provided by remote systems for clients to create or delete objects on the remote system. [ITU-T X.782] provides a common object accessing service, so object creation and deletion will be model-independent. When deleting an object that contains other objects, the containment relationship shall be kept, so that there will not be any orphan objects existing in the remote systems. The containment information should be stored in the remote system and be maintained when creation and deletion happen. + +## 6.3 Scoping + +The ability to perform complex queries (i.e., GET operations), updates (i.e., SET operations) and delete operations on a group of entities with a single operation request is a valuable component of TMN. Management systems may have to manage up to $10^7$ instances of managed objects. Due to the size of the management information base, a managing system cannot efficiently perform ad hoc queries on individual instances of managed objects (i.e., entities). Rather, the managing system expects a level of intelligence to be supported by the managed system. + +The intelligence in the managed system allows the managing system to select a group of managed entities on which an operation will be performed. Managed entity selection involves two phases: scoping. This managed entity selection process is supported by a service defined later in this Recommendation. This service allows a managing system to select a scope of objects to act on (scope is defined through containment relationships; see clause 6.2.2). Once the scope of entities is determined, the operation (specified by the scope request) is performed only on those entities. + +The use of scoping in this framework supports: + +- Scoped get: Returns the values (for a list of attributes) from each of the entities that meet the scope. +- Scoped update: Replaces an attribute value or adds/removes values to/from set-valued attributes, in the group of entities meeting the scope, to the values specified in the scoped request. May be used to update one or multiple attributes in a single object or multiple objects. +- Scoped deletion: Deletes all entities that meet the scope. + +Scoping entails the identification of the entities to which a filter is to be applied. Scoping is applied based on the containment hierarchy as defined in clause 6.2.2. The scope is applied from a base managed entity down to a particular depth in the containment tree. + +The base entity for the scope is defined as the root of the containment tree from which the search is to commence. A scoped request must specify the base managed entity of the scope. The depth of the scoping level can then be specified in one of four manners within the scoped request: + +- 1) the base entity +- 2) the n-th level subordinates of the base entity +- 3) the base entity and all of its subordinates down to and including the n-th level +- 4) the base entity and all of its subordinates (i.e., the whole subtree). + +## 6.4 Notifications + +The framework needs to support the ability to: + +- deliver notifications +- subscribe for notification types +- forward notifications to multiple destinations + +- filter notifications +- uniquely identify the resource that emits the notification. + +# 7 Framework overview and protocol requirements + +## 7.1 Framework overview + +This framework for web services-based management interfaces is a collection of capabilities. One part of the framework is a set of well-known web services. This framework defines their role in network management interfaces and defines conventions for their use. The framework also defines support services that have not been standardized in industry yet, but are expected to be standards on network management interfaces conforming to this framework. WSDL interfaces for these services are defined in Annex A. + +To support the software objects representing manageable resources, the framework requires that they implement some common basic capabilities. Therefore, one base class is defined in [ITU-T X.782] for use in modelling network management resources. Managed object classes in information models must inherit and implement a basic set of capabilities from the base class in order to operate within this framework. Finally, some rules and conventions are defined for information modellers developing models for use with this framework. These consist of modelling guidelines and XML style idioms. All of these are depicted graphically in Figure 1. + +![Figure 1 – Overview of a framework. The diagram illustrates the framework structure. At the top, four boxes represent design principles: 'Principle for Service-oriented WSDL interface design', 'Standard data types', 'Notification Specifications', and 'Style conventions for WSDL and XML Schema specification'. Below these, a 'super class: Managed Object (XML element)' is shown. An arrow labeled 'inherits' points from 'Application-specific Objects: Other specific Managed Object' to the super class. An arrow labeled 'accesses' points from 'Basic MO Access' to the super class. Another arrow labeled 'manages' points from 'Other extended services' to the 'Other specific Managed Object'. A box on the right lists 'Other Conventions: (Naming, inheritance)'. The bottom section, 'Support Services:', includes 'UDDI Service Registration', 'WS-Notification', 'Heartbeat Service', 'MOO Service', and 'Containment Service'. At the very bottom, a box represents the communication protocol 'SOAP 1.2'.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +Figure 1 – Overview of a framework. The diagram illustrates the framework structure. At the top, four boxes represent design principles: 'Principle for Service-oriented WSDL interface design', 'Standard data types', 'Notification Specifications', and 'Style conventions for WSDL and XML Schema specification'. Below these, a 'super class: Managed Object (XML element)' is shown. An arrow labeled 'inherits' points from 'Application-specific Objects: Other specific Managed Object' to the super class. An arrow labeled 'accesses' points from 'Basic MO Access' to the super class. Another arrow labeled 'manages' points from 'Other extended services' to the 'Other specific Managed Object'. A box on the right lists 'Other Conventions: (Naming, inheritance)'. The bottom section, 'Support Services:', includes 'UDDI Service Registration', 'WS-Notification', 'Heartbeat Service', 'MOO Service', and 'Containment Service'. At the very bottom, a box represents the communication protocol 'SOAP 1.2'. + +**Figure 1 – Overview of a framework** + +Figure 1 shows the framework in grey. In the middle are the application-specific objects that are supported by the framework. Along the bottom is a box representing the communication protocol: SOAP. Above that are a number of boxes with names in them representing the services that compose the framework (some also have icons depicting the databases they would have to maintain + +to perform their functions). Along the top of the figure are icons representing the super class managed object, and the basic MO accessing service. Each managed object supported by this framework must ultimately inherit from the super class. Also shown on Figure 1 are icons of pages with up-turned corners representing standard object modelling conventions. + +The framework services, represented as boxes with square corners, are defined in this Recommendation. The super class, notifications, and object modelling conventions are defined in [ITU-T X.782]. + +## 7.2 Protocol, languages and services requirements + +This clause defines the versions of the languages, protocol, and services that are required to support this framework. Web services basic technology and protocol specifications are defined by W3C, and two well-known services used in this framework are defined by OASIS. Table 1 shows which version (including subsequent versions released up until the date of this Recommendation) of the applicable specifications must be supported to comply with this framework. + +**Table 1 – Web services language, protocol and services versions** + +| Service | Version | +|----------------------------------------------|-----------------------| +| WSDL Recommendation (W3C) | 1.1 (March, 2001) | +| XML schema Recommendation (W3C) | 1.1 (October, 2004) | +| Web services base notification ([OASIS WSN]) | 1.3 (October, 2006) | +| UDDI specification ([OASIS UDDI]) | 3.0.2 (October, 2004) | +| SOAP (W3C) | 1.2 (April 2007) | + +# 8 Usage of well-known web services + +## 8.1 Web services base notification + +This framework uses the OASIS web services base notification specification for transferring notifications needed in network management interfaces. + +### 8.1.1 Web services base notification overview + +Web services base notification (WSN) is a specification that define a standard web services approach to notification using a topic-based publish/subscribe pattern. The contents of WSN include standard message exchanges to be implemented by notification providers, operational requirements expected of service providers and requestors that participate in notifications, and an XML model that describes topics. + +The web services base notification (WSN) supports the asynchronous exchange of event messages between clients using a subscribe-and-publish paradigm, as described in [OASIS WSN]. It also supports the filtering of notifications which are also needed in network management interfaces. + +### 8.1.2 Mapping of operations from Recommendation ITU-T M.3702 and to WSN + +The mechanisms and WSDL interfaces of the [OASIS WSN] specification will be used in this framework, but it is used as an internal functionality, which is not disposed to notification consumers directly. [ITU-T M.3702] provides protocol neutral requirements and analysis for generic notification management services, which define the generic functions that are to be implemented by a protocol-specific management paradigm. In this framework, the generic notification management model is mapped to WSDL/XML definitions and some of the WSDL operation are then mapped to [OASIS WSN] operations. + +The following table indicates the mapping from [ITU-T M.3702] to the web services notification. + +**Table 2 – Mappings from [ITU-T M.3702] to this Recommendation and [OASIS WSN]** + +| No. | [ITU-T M.3702] | | ITU-T Q.818 | | [OASIS WSN] | | +|-----|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Operation name | | Operation name | | Operation | | +| | Request/
response | Parameters | Request/
response | Parameters | Request/
response | Parameters | +| 1 | subscribeNotification | | subscribeNotification | | Subscribe | | +| | Input
parameter |
  • – managerId
  • – notificationTypes
  • – filteringCriteria
  • – destination
| Request |
  • – managerId: type="nts:IdType"
  • – notificationTypes: type="nts:NotificationTypeListType"
  • – filteringCriteria type="nts:FilterType"
  • – destination: type="wsa:EndpointReferenceType"
| Request |
  • – consumerReference,
  • – filter,
  • – subscriptionPolicy,
  • – initialTerminationTime
| +| | Output
parameter |
  • – subscriptionId
  • – status
| Response |
  • – subscriptionId: type="nts:IdType"
  • – status: type="nts:StatusType"
| Response | subscriptionReference | +| 2 | unsubscribeNotification | | unsubscribeNotification | | Unsubscribe | | +| | Input
parameter |
  • – managerId
  • – subscriptionId
| Request |
  • – managerId type="nts:IdType"
  • – subscriptionId type="nts:IdType"
| Request | – subscriptionReference | +| | Output
parameter | – status | Response | – status: type="nts:StatusType" | Response | NULL | +| 3 | suspendSubscription | | suspendSubscription | | PauseSubscription | | +| | Input
parameter |
  • – managerId
  • – subscriptionId
| Request |
  • – managerId: type="nts:IdType"
  • – subscriptionId: type="nts:IdType"
| Request | – subscriptionReference | +| | Output
parameter | – status | Response | – status type="nts:StatusType" | Response | NULL | +| 4 | resumeSubscription | | resumeSubscriptions | | ResumeSubscription | | +| | Input
parameter |
  • – managerId
  • – subscriptionId
| Request |
  • – managerId: type="nts:IdType"
  • – subscriptionId: type="nts:IdType"
| Request | – subscriptionReference | +| | Output
parameter | – status | Response | – status: type="nts:StatusType" | Response | NULL | +| 5 | getNotificationTypes | | getNotificationTypes | | -- | | +| | Input
parameter | – notificationIRPId | Request | – notificationIRPId: type="x782:NameType" | | | +| | Output
parameter |
  • – status
  • – notificationType List
| Response |
  • – notificationTypeList: type="nts:NotificationTypeListType"
  • – status type="nts:StatusType"
| | | + +**Table 2 – Mappings from [ITU-T M.3702] to this Recommendation and [OASIS WSN]** + +| No. | [ITU-T M.3702] | | ITU-T Q.818 | | [OASIS WSN] | | +|-----|------------------------|--------------------------------------------------------------------------------------------------------------|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------------------------------------------| +| | Operation name | | Operation name | | Operation | | +| | Request/
response | Parameters | Request/
response | Parameters | Request/
response | Parameters | +| 6 | querySubscription | | querySubscription | | – | | +| | Input
parameter | – subscriptionId | Request | – subscriptionId:
type="nts:IdType" | | | +| | Output
parameter | – subscribed
NotificationType
– subscriptionStatus
– destination
– filteringCriteria
– status | Response | – notificationTypes:
type="nts:Notification
TypeListType"
– subscriptionStatus:
type="nts:Subscription
StatusType"
– destination: type="wsa:
EndpointReference
Type"
– filteringCriteria: type=
"nts:FilterType"
– status
type="nts:StatusType" | | | +| 7 | modifySubscription | | modifySubscription | | -- | | +| | Input
parameter | – subscriptionId
– filteringCriteria
– destination
– notificationTypes | Request | – subscriptionId:
type="nts:IdType"
– filteringCriteria:
type="nts:FilterType"
– destination: type="wsa:
EndpointReference
Type"
– notificationTypes:
type="nts:Notification
TypeListType" | | | +| | Output
parameter | – status | Response | – status
type="nts:StatusType" | | | +| 8 | listAllSubscriptionIds | | listAllSubscriptionIds | | -- | | +| | Input
parameter | – managerId | Request | – managerId:
type="nts:IdType" | | | +| | Output
parameter | – subscriptionIdSet
– status | Response | – subscriptionIdSet:
type="nts:IdSetType"
– status
type="nts:StatusType" | | | +| 9 | report notification: | | – (Use WSN notify directly) | | Notify: | | +| | | | | | notification
Message | – SubscriptionReference
– Topic
– ProducerURL
– Message | +| | | | | | Response | NULL | + +Table 3 gives additional descriptions for the mapping from the operations defined in this Recommendation to the ones defined in WS-Notification. + +**Table 3 – Additional descriptions for the mappings from the operations in [ITU-T M.3702]** + +| Operation name | Request/
response | ITU-T Q.818 | [OASIS WSN] | +|---------------------|----------------------|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| subscribe | Request | managerId | There is no such managerId parameter in WS-Notification and this parameter will only be processed and stored by an agent, not by WS-Notification. | +| | | filterCriteria | Filter | +| | | destination | ConsumerReference | +| | | NotificationTypes | There is no direct mapping in WSN corresponding to this NotificationTypes, but the filter parameter in WSN can support the function of filtering supported notification types. | +| | | – | subscriptionPolicy
This parameter is optional in WSN, which can be raw or any value in Notify message. Notify message can provide more information in a message according to the WSN definition. In the mapping of such an operation, the value of subscriptionPolicy should always use the Notify message in this Recommendation. | +| | | – | initialTerminationTime
initialTerminationTime indicates the termination time of a subscription. When the value of attribute xsi:nil is true, there is no limit for the subscription. In this Recommendation, the default value for this parameter in WSN will be xsi:nil= true. | +| | Response | subscriptionId | subscriptionReference | +| unsubscribe | Request | managerId | There is no such concept as managerId in WSN which will be processed and stored in the agent itself. The type is a string at this moment. | +| | | subscriptionId | subscriptionReference | +| suspendSubscription | Request | managerId | There is no such concept as managerId in WSN which will be processed and stored in the agent itself. The type is a string at this moment. | +| | | subscriptionId | subscriptionReference | +| resumeSubscription | Request | managerId | There is no such concept as managerId in WSN which will be processed and stored in the agent itself. The type is a string at this moment. | +| | | subscriptionId | subscriptionReference | + +**Table 3 – Additional descriptions for the mappings from the operations in [ITU-T M.3702]** + +| Operation name | Request/
response | ITU-T Q.818 | [OASIS WSN] | +|------------------------|----------------------------------------------------------------------------------------------------------|-------------|-------------| +| getNotificationTypes | There are no corresponding operations defined in WSN, and they should be implemented by an agent itself. | | | +| querySubscription | | | | +| modifySubscription | | | | +| listAllSubscriptionIds | | | | +| notify | In this Recommendation, the notify operation from WSN is used directly in an agent. | | | + +A detailed interface definition can be found in clause A.1. + +### 8.1.3 Notification format definitions + +#### 8.1.3.1 Notification format to be used in this Recommendation + +The following table provides the notify operations defined in [OASIS WSN] which will be used in this Recommendation when sending notifications. + +**Table 4 – Notify operations from [OASIS WSN]** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 <wsnt:Notify>   <wsnt:NotificationMessage>     <wsnt:SubscriptionReference>       wsa:EndpointReferenceType     </wsnt:SubscriptionReference> ?     <wsnt:Topic Dialect="xsd:anyURI">       {any} ?     </wsnt:Topic>?     <wsnt:ProducerReference>       wsa:EndpointReferenceType     </wsnt:ProducerReference> ?     <wsnt:Message>       {any}     </wsnt:Message>   </wsnt:NotificationMessage> +   {any} * </wsnt:Notify>
| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +In this Recommendation not all the above components will be used. More detailed descriptions of the above components which can or cannot be used in this Recommendation are shown below: + +- The WS-Addressing [action] Message Addressing Property MUST contain the URI . + +The components of the notify message are described as follows: + +/wsnt:Notify + +contains a collection of one or more NotificationMessages: + +/wsnt:Notify/wsnt:NotificationMessage + +This contains: + +— a notification payload: + +`/wsnt:Notify/wsnt:NotificationMessage/wsnt:SubscriptionReference` + +This is an `EndpointReference` to the subscription that is associated with the notify message. This component is optional. + +`/wsnt:Notify/wsnt:NotificationMessage/wsnt:ProducerReference` + +This is an `EndpointReference` to the `NotificationProducer` that produced the notification artefact. This component is optional: + +`/wsnt:Notify/wsnt:NotificationMessage/wsnt:Topic` + +This is a `TopicExpression` describing exactly one topic, which **MUST** be the topic that is associated with the notification. This element describes the topic that matched to a subscription, causing the `NotificationProducer` to send the notify message to the `NotificationConsumer`. This component is also optional. + +`/wsnt:Notify/wsnt:NotificationMessage/wsnt:Topic/@Dialect` + +This is the dialect used in the `TopicExpression`. This **MUST** be the same dialect used by the subscriber when it created the subscription that yielded this notify message. + +`/wsnt:Notify/wsnt:NotificationMessage/wsnt:Message` + +This is a copy of the actual notification payload. This component is of any type, and will be replaced by predefined notification types, which are defined in clause A.5 and will be explained later. + +and any metadata components: + +`/wsnt:Notify/{any}` + +The raw data shall not be used in this Recommendation. + +The most simplified notification message format that can be used in this Recommendation is shown in Table 5. + +**Table 5 – Most simplified notification format in this Recommendation** + +``` + + + + {any} + + + + +``` + +#### 8.1.3.2 Common notification header definition + +This clause provides the detailed common notification header described in [ITU-T M.3702]. + +The following table provides the definition of the parameters of the common notification header. + +**Table 6 – Common notification header definition** + +| Parameter name | Qualifiers | XSD data type | Descriptions | +|------------------|------------|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| objectClass | M | xsd:string | It is the class name of the MO which sends out this notification. See clause 7.3.5 of [ITU-T M.3702] | +| objectInstance | M | x782:NameType | It is the DN of the MO which sends out this notification. See clause 7.3.5 of [ITU-T M.3702] | +| notificationId | M | 782:NotificationIdType | It is the Identifier of the notification for the purpose of notification correlation. See clause 7.3.5 of [ITU-T M.3702] | +| eventTime | M | xsd:dateTime | It is the time when this event happened. See clause 7.3.5 of [ITU-T M.3702] | +| systemDN | M | x782:NameType | It is the DN of the system which sends out this notification. See clause 7.3.5 of [ITU-T M.3702] | +| notificationType | M | nts:NotificationTypeType |

It indicates the type of notification. See clause 7.3.5 of [ITU-T M.3702].

The possible common notification types defined in this Recommendation can be the following:

  • – attributeValueChange
  • – objectCreation
  • – objectDeletion
  • – stateChange
  • – communicationsAlarm
  • – environmentalAlarm
  • – equipmentAlarm
  • – processingErrorAlarm
  • – qualityOfServiceAlarm
  • – integrityViolation
  • – operationalViolation
  • – physicalViolation
  • – securityViolation
  • – timeDomainViolation
  • – relationshipChange
  • – heartbeat

This list can be extended to include new notification types as and when they are defined.

| + +#### 8.1.3.3 Common notification contents definition + +- 1) Notification contents for the objectCreation and objectDeletion notifications. + +**Table 7 – Notification contents for objectCreation and objectDeletion** + +| Notification parameter | Qualifiers | Data type | Descriptions | +|-------------------------|------------|------------------------------------|--------------------------------------------| +| correlatedNotifications | O | x782:Correlated NotificationType | List of correlated notifications. | +| additionalText | O | xsd:string | Text message. | +| additionalInfo | O | x782:Additional InformationSetType | Additional information not in text format. | +| sourceIndicator | O | x782:SourceIndicatorType | Cause of event. | +| attributeList | O | x782:AttributeNameAnd ValueType | Attribute values. | + +- 2) Notification contents for the attributeValueChange notification. + +**Table 8 – Notification contents for attributeValueChange** + +| Notification parameter | Qualifiers | Data type | Descriptions | +|-------------------------|------------|------------------------------------|--------------------------------------------| +| correlatedNotifications | O | x782:Correlated NotificationType | List of correlated notifications. | +| additionalText | O | xsd:string | Text message. | +| additionalInfo | O | x782:Additional InformationSetType | Additional information not in text format. | +| sourceIndicator | O | x782:SourceIndicatorType | Cause of event. | +| attributeChanges | M | x782:AttributeValueChange SetType | Changed attributes. | + +- 3) Notification contents for the stateChange notification. + +**Table 9 – Notification contents for stateChange** + +| Notification parameter | Qualifiers | Data type | Descriptions | +|-------------------------|------------|------------------------------------|--------------------------------------------| +| correlatedNotifications | O | x782:Correlated NotificationType | List of correlated notifications. | +| additionalText | O | xsd:string | Text message. | +| additionalInfo | O | x782:Additional InformationSetType | Additional information not in text format. | +| sourceIndicator | O | x782:SourceIndicatorType | Cause of event. | +| stateChanges | M | x782:AttributeValueChange SetType | Changed states. | + +- 4) Notification contents for the communicationAlarm, environmentalAlarm, equipmentAlarm, processingErrorAlarm, qualityOfServiceAlarm notifications. + +**Table 10 – Notification contents for alarms** + +| Notification parameter | Qualifiers | Data type | Descriptions | +|-------------------------|------------|------------------------------------|------------------------------------------------------------------------------------| +| correlatedNotifications | O | x782:CorrelatedNotificationSetType | List of correlated notifications. | +| additionalText | O | xsd:string | Text message. | +| additionalInfo | O | x782:AdditionalInformationSetType | Additional information not in text format. | +| probableCause | M | x782:ProbableCauseType | The probable cause of the alarm. | +| specificProblems | O | x782:SpecificProblemSetType | Non standardized problems. | +| perceivedSeverity | M | x782:PerceivedSeverityType | It indicates the perceived severity of the alarm. See type definition for details. | +| backedUpStatus | O | xsd:boolean | "True" if backed up. | +| backUpObject | O | X782:NameType | It indicates the DN of the backup object if the backUpStatus is "false". | +| trendIndication | O | x782:TrendIndicationType | See type for details. | +| thresholdInfo | O | x782:ThresholdInfoType | See type for details. | +| stateChangeDefinition | O | x782:AttributeChangeSetType | It indicates the state changes in this alarm. | +| monitoredAttributes | O | x782:AttributeNameAndValueType | See type for details. | +| proposedRepairActions | O | x782:ProposedRepairActionSetType | It indicates the proposed actions to repair this fault. | +| alarmEffectOnService | O | xsd:boolean | True if alarm is service effecting. | +| alarmingResumed | O | xsd:boolean | True if alarming was just resumed, possibly resulting in delayed reporting. | +| suspectObjectList | O | x782:SuspectObjectSetType | Objects possibly involved in failure. | + +- 5) Notification contents for the integrityViolation, operationalViolation, physicalViolation, securityViolation, timeDomainViolation notifications. + +**Table 11 – Notification contents for violations** + +| Notification parameter | Qualifiers | Data type | Descriptions | +|-------------------------|------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------| +| correlatedNotifications | O | x782:Correlated NotificationSetType | List of correlated notifications. | +| additionalText | O | xsd:string | Text message. | +| additionalInfo | O | x782:AdditionalInformation SetType | Additional information not in text format. | +| securityAlarmCause | M | x782:SecurityAlarmCause Type | The cause of the security alarm. | +| securityAlarmSeverity | M | x782:PerceivedSeverityType | Clears allowed?
ITU-T X.721 appears to restrict the cleared value on this alarm, but clears should be allowed. | +| securityAlarmDetector | M | x782:SecurityAlarmDetector Type | See type for details. | +| serviceUser | M | x782:ServiceUserType | The user of the service which is violated. | +| serviceProvider | M | x782:ServiceProviderType | The service provider of the service which is violated. | + +- 6) Notification contents for the relationshipChange notification. + +**Table 12 – Notification contents for relationshipChange** + +| Notification parameter | Qualifiers | Data type | Descriptions | +|-------------------------|------------|------------------------------------|--------------------------------------------| +| correlatedNotifications | O | x782:Correlated NotificationType | List of correlated notifications. | +| additionalText | O | xsd:string | Text message. | +| additionalInfo | O | x782:AdditionalInformation SetType | Additional information not in text format. | +| sourceIndicator | O | x782:SourceIndicatorType | Cause of event. | +| relationshipChanges | M | x782:AttributeChangeSet Type | Changed relationship attributes. | + +The detailed data type definitions for notification contents can be found in clause A.1. + +## 8.2 UDDI service registration + +The OASIS UDDI registry is a web services-based directory service. + +The focus of universal description discovery and integration (UDDI) is the definition of a set of services supporting the description and discovery of the following: + +- businesses, organizations, and other web services providers + +- the web services they make available and +- the technical interfaces which may be used to access those services. + +UDDI provides an interoperable, foundational infrastructure for a web services-based software environment for both publicly available services and services that are exposed only internally within an organization. + +UDDI registry allows a client to find web services registered within it. This framework uses the well-known service UDDI for service registration and it provide the means for a managing system to discover the services provided by a managed system. + +As UDDI is not designed specifically for network management there are many properties which are not needed when used in network management. + +The following clauses provide a simplified UDDI information model and listed are some of the related operations which are expected to be used in a network management domain. + +### 8.2.1 UDDI information model used in network management + +![UML Class Diagram showing the simplified information model of UDDI. It consists of three classes: BusinessEntity, BusinessService, and BindingTemplate. BusinessEntity has attributes +businessKey, +name, +description, and +businessServices. BusinessService has attributes +businessKey, +servicesKey, +name, and +description. BindingTemplate has attributes +bindingKey, +serviceKey, +description, and +accessPoint. BusinessEntity has a 1 to 0..* aggregation relationship with BusinessService. BusinessService has a 1 to 0..* aggregation relationship with BindingTemplate.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg) + +``` + +classDiagram + class BusinessEntity { + +businessKey + +name + +description + +businessServices + } + class BusinessService { + +businessKey + +servicesKey + +name + +description + } + class BindingTemplate { + +bindingKey + +serviceKey + +description + +accessPoint + } + BusinessEntity "1" o-- "0..*" BusinessService + BusinessService "1" o-- "0..*" BindingTemplate + +``` + +UML Class Diagram showing the simplified information model of UDDI. It consists of three classes: BusinessEntity, BusinessService, and BindingTemplate. BusinessEntity has attributes +businessKey, +name, +description, and +businessServices. BusinessService has attributes +businessKey, +servicesKey, +name, and +description. BindingTemplate has attributes +bindingKey, +serviceKey, +description, and +accessPoint. BusinessEntity has a 1 to 0..\* aggregation relationship with BusinessService. BusinessService has a 1 to 0..\* aggregation relationship with BindingTemplate. + +**The simplified information model of UDDI** + +A UDDI information model which is used in network management is composed of instances of the following entity types: + +- **businessEntity**: Describes a system entity which provides some management services. It is usually a managed system (e.g., EMS or agent) provided by a vendor and sometimes it can also be a third party system which provides standalone services to be shared by multiple managed systems (e.g., WSN services). Within a network management domain it is usually a managing system that uses services provided by multiple managed systems. A given instance of the businessEntity structure is uniquely identified by its attribute businessKey in the UDDI registry. It is assigned by the UDDI registry at the time of registration. The name attribute gives a nickname to the managed system. Both a managed system and a third party + +can be registered as an instance of businessEntity. Simple textual information about the managed system could be provided in the optional attribute description. The list of services provided by this managed system is described in the attribute businessServices. Other properties of the businessEntity in the original UDDI model are not used in this framework. + +- **businessService:** Represents a logical web service which provides a management functionality (e.g., configuration management, performance management) by the managed system. businessService is the unit for collecting management operations which are closely related (e.g., retrieve or modify attribute values of managed objects). A given businessService instance is uniquely identified by its attribute serviceKey in the UDDI registry. The businessKey attribute uniquely identifies the containing businessEntity which is the provider of this service. The name attribute gives the nickname of a service. Simple textual information about the management service could be provided in the optional attribute description, indicating the functionalities, usage and other descriptive information of the web services. Other properties of businessService in the original UDDI model are not used in this framework. +- **bindingTemplate:** Describes the technical information necessary for a managing system to use a particular web service. Usually a businessService in a network management domain only has one accessPoint, thus there should be a one-to-one relationship between businessService and its bindingTemplate, except when load balance or backup is turned on, where more than one service implementations are provided. In this case, the information of each accessPoint is contained in a bindingTemplate. A given bindingTemplate entity is uniquely identified by its attribute bindingKey. It is not allowed for more than one implementation to perform different functionalities for a network management service as this confuses the managing system when it attempts to select the appropriate service accessPoint. The serviceKey attribute uniquely identifies the containing businessService. Simple textual information about the bindingTemplate could be given in the optional attribute description. The accessPoint attribute is a string used to convey the network address that suitable for invoking the web services. + +### 8.2.2 Register a new service and access it using UDDI + +[OASIS UDDI] provide several APIs for both web services providers and web services clients to use, either to register a service or find a service. The following subclauses describe some related APIs that are expected to be used in a network domain. + +#### 8.2.2.1 Using publication APIs to publish a new web service in UDDI registry + +There are three operation APIs for a managed system (or a third party) to register its provided web services into the UDDI registry which are listed in the following table. + +**Table 13 – Operation APIs in the UDDI to register a web service** + +| Operation APIs | Parameter direction | Parameter name | Descriptions | +|-----------------------|----------------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| get_authToken | arguments | userId | This required attribute argument is the user identifier that an individual authorized user was assigned by a UDDI node. Nodes should provide a means for individuals to obtain a userID and password credentials that will be valid at the given node. | +| | | cred | This required attribute argument is the password or credential that is associated with the user. | +| | return | authToken | Upon successful completion this API call returns an authToken structure that contains a valid authInfo element that can be used in subsequent calls to API calls that require an authInfo value. | +| save_business: | arguments | authInfo | This argument is an element that contains an authentication token. Authentication tokens are obtained using the get_authToken API call. Registries that serve multiple publishers and registries that restrict who can publish in them typically require authInfo for this call. | +| | | businessEntity | Required repeating element containing one or more businessEntity structures. | +| | return | businessKey | This is assigned as a result of processing the save_business API. | +| save_service | arguments | authInfo | This argument is an element that contains an authentication token. Authentication tokens are obtained using the get_authToken API call. Registries that serve multiple publishers and registries that restrict who can publish in them typically require authInfo for this call. | +| | | businessService | Required repeating element containing one or more complete businessService elements. | +| | return | serviceKey | The serviceKey and the bindingKey values that were assigned as a result of processing the save_service API are included in the businessService data. | +| | | bindingKey | | + +#### 8.2.2.2 Using inquiry APIs to find web services in the UDDI registry + +**Table 14 – Operation APIs in the UDDI to find a web service** + +| Operation APIs | Parameter direction | Parameter name | Descriptions | +|----------------|---------------------|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| find_business | arguments | name | This optional collection of string values represents one or more names potentially qualified with xml:lang attributes. Since exactMatch is the default behaviour, the value supplied for the name argument must be an exact match. | +| | | findQualifiers | This collection of findQualifier elements can be used to alter the default behaviour exactMatch of the search functionality. | +| | | maxRows | This optional integer value allows the requesting program to limit the number of results returned. This argument can be used in conjunction with the listHead argument. | +| | return | businessList | Returns a businessList that matches the criteria specified in the arguments. BusinessList: this structure is a sequence of businesses. | +| find_service | arguments | name | This optional collection of string values represents one or more names potentially qualified with xml:lang attributes. Since exactMatch is the default behaviour, the value supplied for the name argument must be an exact match. | +| | | findQualifiers | This collection of findQualifier elements can be used to alter the default behaviour exactMatch of the search functionality. | +| | | businessKey | This uddi_key is used to specify a particular businessEntity instance to search for. This argument is used to specify an existing businessEntity within which services should be found. | +| | | maxRows | This optional integer value allows the requesting program to limit the number of results returned. This argument can be used in conjunction with the listHead argument. | +| | return | serviceList | Returns a serviceList that matches the criteria specified in the arguments. ServiceList : this structure is a sequence of businesses. | + +**Table 14 – Operation APIs in the UDDI to find a web service** + +| Operation APIs | Parameter direction | Parameter name | Descriptions | +|-----------------------|----------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| find_binding | arguments | serviceKey | This optional uddi_key is used to specify a particular instance of a businessService element in the registered data. Only bindings in the specific businessService data identified by the serviceKey are searched. | +| | | findQualifier | This collection of findQualifier elements can be used to alter the default behaviour exactMatch of the search functionality. | +| | | maxRows | This optional integer value allows the requesting program to limit the number of results returned. This argument can be used in conjunction with the listHead argument. | +| | return | bindingDetail | Returns a bindingDetail that contains zero or more bindingTemplate structures matching the criteria specified in the argument list. Each bindingTemplate structure contains the description and accessPoint. | + +# **9 Framework support services** + +This clause defines common support services included in the framework which are not well known web services. This clause defines services that will be broadly used by network management applications. These services also provide functionality required to enable the reuse of existing information models without significant changes in semantics. The WSDL describing the interfaces to these services can be found in Annex A. + +## **9.1 Heartbeat service** + +The heartbeat service is used to verify the operation of the notification forwarding mechanism (i.e., WSN in this framework) in a managed system, as well as the communications network between the managed system and managing system. + +It periodically sends a small notification to a managing system interested in receiving it and that notification identifies the system that emitted the heartbeat. After configuring this service a managing system can ensure the WSN is functioning. Since these notifications flow through the same software and networks as notifications from other resources, they periodically verify the operation of these resources. + +The heartbeat service has two internal attributes, each of which has a pair of accessing methods, one for value get and one for value set, as presented in the following table: + +**Table 15 – Attributes and accessing operations in a heartbeat service** + +| Internal attributes of heartbeat services | Operations | Message for requests and responses | +|-------------------------------------------|----------------|-------------------------------------------------------------------------------| +| systemLabel | systemLabelGet | Request: NULL
Response:
name="systemLabel"
type="hs:SystemLabelType" | +| | systemLabelSet | Request:
name="systemLabel"
type="hs:SystemLabelType"
Response: NULL | +| period | periodGet | Request: NULL
Response:
name="period" type="hs:HeartbeatPeriodType" | +| | periodSet | Request:
name="period" type="hs:HeartbeatPeriodType"
Response: NULL | + +The following table contains the contents to be included in a heartbeat notification. + +**Table 16 – Notification contents for heartbeat** + +| Heartbeat notification contents | Data type | Descriptions | +|---------------------------------|------------------|--------------------------------------------------------------------------| +| systemLabel | xsd:string | Identifies the managed system which sent out the heartbeat notification. | +| period | xsd:unsignedLong | Indicates the time period between two heartbeats. | +| timeStamp | xsd:dateTime | Indicates the time stamp when the heartbeat notification is generated. | + +The attribute systemLabel and period are two attributes of a heartbeat service. systemLabel is a user-supplied identifier. The intended use is to allow a managing system to insert a label to identify the system providing the heartbeat. The value of systemLabel can be modified using the systemLabelSet operation. period is the period between heartbeats. The value of period can be controlled using the periodSet operation. The value submitted to this operation is the period, in seconds, that the heartbeat service waits between emitting notifications. + +Each notification includes the value of the systemLabel, the current value for the period, and a timestamp. + +**(R) HEARTBEAT-1:** If the heartbeat service is supported by a managed system it shall support the heartbeat interface described above and defined in the WSDL in clause A.2. The functionality described above shall be supported. + +**(R) HEARTBEAT-2:** Updating of the period shall cause the service to deliver a notification to the WSN with the new period value and then begin a new period. Setting the period to zero shall cause the service to emit one final notification with a period value of zero, then no more (until the period is reset). + +**(R) HEARTBEAT-3:** Until the period is changed, the heartbeat notifications shall be sent to the WSN service once within each period. The time between heartbeat notifications being sent to a WSN service shall never be greater than twice the period. + +## 9.2 Multiple object operation service + +The multiple object operation (MOO) service's interface is defined in clause A.3 and in programming terms it is weakly typed. It provides a set of generic capabilities that may be invoked on any kinds of sets of managed objects (of any kind). The operations supported are listed below. + +- Scoped get: Returns the values from each of the objects for a list of attributes. +- Scoped update: Used to replace an attribute value or to add or remove values to/from set-valued attributes. May be used to update one or multiple attributes in a single object or multiple objects. +- Scoped delete: Deletes multiple objects. + +A basic service only needs to implement the scoped get operation. The other two operations are optional. + +### 9.2.1 Common parameters in MOO service operations + +Each of the scoped operations requires four parameters to define the set of objects on which the operation will be performed. + +- Base object name: The name of the object at the root of a tree of objects on which the operation will potentially be performed. +- Scope: A *complexType* identifying the objects contained under the base object on which the operation will potentially be performed. The *complexType* contains two elements, one element *scope* indicating four scope cases. Two of the cases include an integer specifying a level of objects contained below the base object, which is presented by the other element *level* in the *complexType*. The four cases are: + - Base object only. If the scope is *baseObjectOnly*, then only the named target (base) object is included in the scope. In this case, the *level* is not used. + - Whole subtree. If the scope is *wholeSubtree*, the scope is all of the objects contained below the base object, along with the base object. + - Individual level. If the scope is *individualLevel*, the positive integer-valued *level* will also be used. All of the objects contained at a level below the base object equal to this value are in the scope. The objects directly contained by the base object are level one. + - Base to level. If the scope is *baseToLevel*, the positive integer-valued *level* will also be used. The scope will be all of the objects down to the given level, including the base object and the object at the given level. + +The XSD signature for the scopeType is the following: + +**Table 17 – ScopeType definition** + +| | | +|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ScopeEnumType | 
<xsd:simpleType name="ScopeEnumType">   <xsd:restriction base="xsd:string">     <xsd:enumeration value="BasicObjectOnly"/>     <xsd:enumeration value="WholeSubtree"/>     <xsd:enumeration value="IndividualLevel"/>     <xsd:enumeration value="BaseToLevel"/>   </xsd:restriction> </xsd:simpleType>
| +| ScopeType | 
<xsd:complexType name="ScopeType">   <xsd:sequence>     <xsd:element name="scopeInd" type="moos:ScopeEnumType"/>     <xsd:element name="level" type="xsd:short"/>   </xsd:sequence> </xsd:complexType>
| + +The object names are the NameType (DN) format as describe in the [ITU-T X.782]. The scope is a complexType with values as described above. + +The following clauses give additional details on each of the scoped operations. + +### 9.2.2 Scoped get + +The WSDL signature for the scoped get operation on the basic MOO service is: + +**Table 18 – Request and response for ScopedGet operation** + +| | | +|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ScopedGet Request | 
<xsd:complexType name="ScopedGetRequestType">   <xsd:sequence>     <xsd:element name="baseName" type="x782:NameType"/>     <xsd:element name="scope" type="moos:ScopeType"/>     <xsd:element name="moClassList"       type="x782:MOClassListType" minOccurs="0" maxOccurs="1"/>     <xsd:element name="attributes" type="x782:StringSetType"/>   </xsd:sequence> </xsd:complexType>
| +| ScopedGet Response | 
<xsd:complexType name="ScopedGetResponseType">   <xsd:sequence>     <xsd:element name="moInfo" type="moos:GetResultsType"       minOccurs="0" maxOccurs="unbounded"/>   </xsd:sequence> </xsd:complexType>
| + +As described above, the first two parameters baseName and scope in the scopedGet request are used to select a set of objects on which to perform the get operation. The optional parameter moClassList in the scopedGet request can be used to select the objects of a certain MOC(s). For each of the objects, the MOO service will try to return a value for each of the attributes named in the attributes parameter, which is just a list of strings. A submitted null attribute list, however, has the special meaning that all attribute values for the selected objects should be returned. The data types involved in the return value are listed in the following table: + +**Table 19 – Data types for ScopedGet** + +| | | +|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| X782:AttributeNameAndValueType | 
<xsd:complexType name="AttributeNameAndValueType">   <xsd:sequence>     <xsd:element name="attributeName" type="xsd:string"/>     <xsd:element name="attributeType" type="xsd:string"/>     <xsd:element name="attributeValue" type="x782:AttributeValueType"/>   </xsd:sequence> </xsd:complexType>
| +| X782:AttributeNameAndValueSetType | 
<xsd:complexType name="AttributeNameAndValueSetType">   <xsd:sequence>     <xsd:element name="attributeNameAndValue" type="x782:AttributeNameAndValueType" minOccurs="0" maxOccurs="unbounded"/>   </xsd:sequence> </xsd:complexType>
| +| GetResultsType | 
<xsd:complexType name="GetResultsType">   <xsd:sequence>     <xsd:element name="name" type="x782:NameType"/>     <xsd:element name="attributes" type="x782:AttributeNameAndValueSetType"/>     <xsd:element name="failedAttributes" type="x782:StringSetType"/>   </xsd:sequence> </xsd:complexType>
| +| X782:StringSetType | 
<xsd:complexType name="StringSetType">   <xsd:sequence>     <xsd:element name="value" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>   </xsd:sequence> </xsd:complexType>
| + +The first two types *x782:AttributeNameAndValueType* and *x782:AttributeNameAndValueSetType* form a name-value pair list. The return type is a *complexType* which contains a sequence of structures, one for each selected managed object. In each structure, there is an MO's name, the list of attribute values from that object, and the names of any attributes that could not be retrieved from that object. If an attribute value of an MO could not be retrieved either because the object did not have a matching attribute or an exception was raised on access, that attribute's name should be put on the failed attribute list for that object. + +### 9.2.3 Scoped update + +The WSDL signature for the scoped update operation on the MOO service is: + +**Table 20 – Request and response for ScopedUpdate operation** + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ScopedUpdate Request |
type="moos:ScopedUpdateRequestType"/>





type="x782:MOClassListType" minOccurs="0" maxOccurs="1"/>
type="moas:AttributeNVMLISTType"/>


 | +| ScopedUpdate Response |
type="moos:ScopedUpdateResponseType"/>



type="moos:UpdateResultType" minOccurs="0"
maxOccurs="unbounded"/>

 | + +Again, the first two parameters are used to select the set of objects on which the update is performed. The optional parameter moClassList can be used to select the objects of a certain MOC(s). The modifications is a sequence of structures, each with the name of an attribute, the type of the attribute, a value for that attribute, and an enumerated value indicating if the value should replace the attribute's current value, be added to the attribute's current value, or be removed from it. The ADDValues and REMOVEValues options are valid only if the attribute's type is an XSD complex type of a sequence, and the values of the attribute can be added or removed. The values in the modifications sequence of structures are passed across as XML anyTypes. The XSD signature for the modification related data types are shown as the following: + +**Table 21 – Modification related data types for ScopedUpdate operation** + +| | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| moas:ModifyOptionType | 
<xsd:simpleType name="ModifyOptionType">   <xsd:restriction base="xsd:string">     <xsd:enumeration value="REPLACE"/>     <xsd:enumeration value="ADDValues"/>     <xsd:enumeration value="REMOVEValues"/>     <xsd:enumeration value="SETToefault"/>   </xsd:restriction> </xsd:simpleType>
| +| moas:AttributeNVMTType | 
<xsd:complexType name="AttributeNVMTType">   <xsd:sequence>     <xsd:element name="attributeName" type="xsd:string"/>     <xsd:element name="attributeType" type="xsd:string"/>     <xsd:element name="attributeValue" type="x782:AttributeValueType"/>     <xsd:element name="modifyOption" type="moas:ModificationOpType"/>   </xsd:sequence> </xsd:complexType>
| +| moas:AttributeNVMLISTType | 
<xsd:complexType name="AttributeNVMLISTType">   <xsd:sequence>     <xsd:element name="attributeNVM" type="moas: AttributeNVMTType" minOccurs="1" maxOccurs="unbounded"/>   </xsd:sequence> </xsd:complexType>
| + +The *failuresOnly* flag is used to indicate if the client wants the service to return results for all objects meeting the scope, or just those objects for which at least one of the modifications could not be performed even though the scope has been satisfied. + +The return value is a sequence of structures, each containing an object's name and a list of any attributes that could not be modified. The service will try to perform all the modifications in the list, in order, continuing to try the rest even if one modification fails. If any operation fails on an attribute, that attribute's name is added to the list of failures. If the *failedAttributes* data member is empty, the client will know all updates were performed on that object. The new types involved in the return value are shown in the following table: + +**Table 22 – Return data types for ScopedUpdate operation** + +| | | +|--------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UpdateResults Type | 
<xsd:complexType name="UpdateResultsType">   <xsd:sequence>     <xsd:element name="name" type="x782:NameType" minOccurs="1" maxOccurs="unbounded"/>     <xsd:element name="failedAttributes" type="x782:StringSetType" minOccurs="0" maxOccurs="unbounded"/>   </xsd:sequence> </xsd:complexType>
| +|--------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 9.2.4 Scope delete + +The WSDL signature for the scoped delete operation on the advanced MOO service is: + +**Table 23 – Request and response for ScopedDelete operation** + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ScopedDelete Request | 
<wsdl:message name="scopedDeleteRequest">   <wsdl:part name="scopedDeleteInput" type="nts:ScopedDeleteRequestType"/> </wsdl:message> <xsd:complexType name="ScopedDeleteRequestType">   <xsd:sequence>     <xsd:element name="baseName" type="x782:NameType"/>     <xsd:element name="scope" type="moos:ScopeType"/>     <xsd:element name="moClassList" type="x782:MOClassListType" minOccurs="0" maxOccurs="1"/>     <xsd:element name="failuresOnly" type="xsd:boolean"/>   </xsd:sequence> </xsd:complexType>
| +| ScopedDelete Response | 
<wsdl:message name="scopedDeleteResponse">   <wsdl:part name="scopedDeleteOutput" type="moos:ScopedDeleteResponseType"/> </wsdl:message> <xsd:complexType name="ScopedDeleteResponseType">   <xsd:sequence>     <xsd:element name="deleteResult" type="moos: DeleteResultType" minOccurs="0" maxOccurs="unbounded"/>   </xsd:sequence> </xsd:complexType>
| + +This operation simply attempts to delete each object selected by the scope parameter. The optional parameter moClassList can be used to select the objects of a certain MOC(s). + +The failuresOnly flag is used to indicate if the client wants the service to return results for all objects meeting the scope, or just those objects that could not be deleted. Because object deletion notifications are typically sent, clients may often want to choose to receive results for only those objects that could not be deleted. + +The return value lists the name of each object along with a flag, the notDeletable flag shall be true if the selected object could not be deleted, either due to its delete policy, or because it raised an exception. + +The data types involved in the return value are listed in the following table: + +**Table 24 – Data types for ScopedDelete operation** + +| | | +|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DeleteResults Type | 
<xsd:complexType name="DeleteResultType">   <xsd:sequence>     <xsd:element name="name" type="x782:NameType" minOccurs="1" maxOccurs="unbounded"/>     <xsd:element name="notDeletable" type="xsd:boolean" minOccurs="0" maxOccurs="1"/>   </xsd:sequence> </xsd:complexType>
| +|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +Because many objects cannot be deleted if they contain other objects, for scopes based on containment relationships the service must begin deleting the leaf objects that are within scope and work towards the root object. When deleting objects, the MOO service must follow the rules for + +deleting an object based on the object's delete policy. Because the rules are being applied to each of the objects in the scope, starting from the bottom up, however, the effect will be different than simply trying to delete the object at the root of a subtree. Also, the MOO service is best-effort. Therefore, it is possible for some of the objects in a scoped subtree to be deleted while others are not. These are the rules that must be applied to scoped delete operations: + +- 1) No objects may be orphaned. That is, an object may not be deleted without deleting all of its contained (child) objects. +- 2) Performing a scoped delete on an entire subtree results in all of the objects in that subtree being deleted unless an object is not deletable, or an object has a subordinate that is not deletable. +- 3) Performing a scoped delete on part of a subtree requires evaluating each of the objects at the lowest scoped layer. If an object at the lowest layer of the scope may be deleted, it and any subordinates are deleted. If a lowest layer object cannot be deleted, it is not deleted nor are any of its superior objects. Other objects in the scope may be deleted, however, if the delete rules allow it. The service then moves up to the next layer, and so on. + +### 9.2.5 MOO service requirements + +This clause summarizes the multiple object operation service requirements. + +**(R) MOO-1:** An implementation of the MOO service shall support the scopedGet operation described above and whose WSDL is defined in clause A.3. + +**(O) MOO-2:** Optionally, an implementation of the MOO service may support the scopedUpdate and ScopeDelete Operation described above and whose WSDL is defined in clause A.3. + +## 9.3 Containment service + +In the network management field a function is needed to be able to report which objects are contained by a superior object, to verify that a superior object exists before a subordinate is created, to make sure two objects with the same name are not created, etc. The framework will be extended to support this function by adding a new service, the containment service. + +### 9.3.1 Containment service description + +The main function to be supported by the containment service is to enable a managing system to query a managed system with the name of an object, and receive back the names of the objects contained by that object. In addition, a means of getting names added to and removed from the service will be defined. These are not for use by managing systems but internally by managed objects, factories, and other parts of a managed system. They are provided to promote the development of reusable components, possibly by third parties, and are defined on an interface separate from that used by managing systems. + +### 9.3.2 The containment service definition + +The containment service provides three operations to retrieve containment information. The WSDL describing the containment service interface and the corresponding XML schema can be found in clause A.4. + +A short description of the semantics of the containment service is illustrated in the following table: + +**Table 25 – Operations in containment service** + +| Operation | Parameter direction | Parameter name | Descriptions | +|-------------------------|---------------------|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| exists | request | name:
x782:NameType | This is the DN of a managed object to be checked whether it exists in the containment service or not. | +| | response | existsOutput :
xsd:boolean | Returns true if the specified MO exists in the containment service, otherwise the result will be false. | +| getContained | request | base:
x782:NameType | It indicates the base MO instance for a specified tree for retrieving containment information. | +| | | scope: ScopeType | It indicates the scope information for retrieving containment information. See clause 9.2.1 for the semantics of the scope. | +| | response | moList:
x782:NameSet
Type | Returns a list of MO names that is specified by the base and scope parameters. | +| getContainedBy
Class | request | base :
x782:NameType | It indicates the base MO instance for a specified tree for retrieving containment information. | +| | | moClass:
xsd:string | It indicates the managed object class for retrieving containment information. | +| | | scope:
moos:ScopeType | It indicates the scope information for retrieving containment information. See clause 9.2.1 for the semantics of the scope. | +| | response | moList:
x782:NameSet
Type | Returns a list of MO names that is specified by the base and scope parameters and they are all instances of class specified by the moClass parameter. | + +The 'exists' operation takes a name and returns true if it is registered with the containment service. The other two operations return the names of objects contained by the object named in the base parameter. The scope parameter on both of these operations can be used to specify which part of the tree of objects contained below the base object is to be retrieved. The third operation, getContainedByClass, takes an moClass parameter to instruct the containment service to return the names for objects of a certain MOC. + +**(R) CONTAINMENT-1:** The interface supported by the containment service shall be the containment interface described above and defined in clause A.4. + +**(R) CONTAINMENT-2:** In response to an invocation of the 'exists' operation, the containment service shall return true if the name is currently registered with the service and false otherwise. If some error on the server prevents this determination an appropriate application error exception response shall be returned to the managing system. + +**(R) CONTAINMENT-3:** In response to an invocation of the getContained operation, the containment service shall return a list of the names of the objects contained by the object named in the base parameter. The list of contained objects shall be determined according to the scope parameter. If an empty base name is submitted, the first level of contained names shall be the names of the registered root MO. If some error prevents the list from being returned, an appropriate application error exception response shall be returned, for example, the base name is not registered. + +**(R) CONTAINMENT-4:** The containment service shall respond to the invocation of the *getContainedByClass* operation as described in requirement CONTAINMENT-3, except only those names that match the *moClass* parameter are returned. + +The registration of MO names in the containment service is a function that should be implemented by managed systems which is outside the scope of this Recommendation. + +# 10 Compliance and conformance + +This clause defines the criteria that must be met by other standards documents claiming compliance to this framework and the functions that must be implemented by systems claiming conformance to this Recommendation. + +## 10.1 System conformance points + +This clause summarizes the individual functions described earlier in this Recommendation. These conformance points are then combined in profiles that must be supported by systems claiming conformance to this Recommendation. + +- 1) An implementation claiming conformance to the notifications requirements must: + - support the OASIS web services base Notification [OASIS WSN] version specified in clause 7.2; + - support the notification interface described in clause 8.1 and defined in the WSDL and XML schema in clause A.1; + - support the notification format described in clause 8.1.3 and defined in the XML schema in clause A.5. +- 2) An implementation claiming conformance to the services registry requirements must: + - support the OASIS UDDI service registration [OASIS UDDI] version specified in clause 7.2; + - support the usage of UDDI service registration as specified in clause 8.2. +- 3) An implementation claiming conformance to the heartbeat service must: + - support the heartbeat service interface described in clause 9.1 and defined in the WSDL and XML schema in clause A.2; + - support the heartbeat service requirements specified in clause 9.1. +- 4) An implementation claiming conformance to the multiple object operations (MOO) service must: + - support the MOO service interface described in clause 9.2 and defined in the WSDL and XML schema in clause A.3; + - support all of the mandatory MOO service requirements specified in clause 9.2.5. +- 5) An implementation claiming conformance to the containment service must: + - support the containment service interface described in clause 9.3 and defined in the WSDL and XML schema in clause A.4; + - support the containment service requirements specified in clause 9.2. + +## 10.2 Basic conformance profile + +A system claiming conformance to the ITU-T.Q.818 basic profile shall support: + +- 1) the version of WSDL, XML schema and SOAP as specified in clause 7.2 +- 2) the WSN (see conformance point 1) +- 3) the UDDI service registration (see conformance point 2) + +- 4) the heartbeat service (see conformance point 3) +- 5) the MOO service (see conformance point 5) +- 6) the containment service (see conformance point 4). + +# Annex A + +## WSDL definition of framework support services + +(This annex forms an integral part of this Recommendation.) + +## A.1 ITU notification service WSDL and XML schema definition + +#### 1) ITU notification service XML schema definition + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + + + +``` + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + +``` + + + +``` + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +#### 2) ITU notification service WSDL + +``` + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +## A.2 ITU heartbeat service WSDL and XML schema definition + +#### 1) ITU heartbeat service XML schema definition + +``` + + + + + + + + + + + + + + + +``` + +``` + + + + + +``` + +#### 2) ITU heartbeat service WSDL definition + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +## A.3 ITU MOO service WSDL and XML schema definition + +#### 1) ITU MOO service XML schema definition + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + +``` + +#### 2) ITU MOO service WSDL definition + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + +``` + +## A.4 ITU containment service WSDL and XML schema definition + +#### 1) ITU containment service XML schema definition + +``` + + + +--> + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + +``` + +#### 2) ITU containment service WSDL definition + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + +``` + +# Bibliography + +- [b-ITU-T Q.816] Recommendation ITU-T Q.816 (2001), *CORBA-based TMN services*. +- [b-ITU-T Q.816.1] Recommendation ITU-T Q.816.1 (2001), *CORBA-based TMN services: Extensions to support coarse-grained interfaces*. +- [b-ITU-T Q.816.2] Recommendation ITU-T Q.816.2 (2007), *CORBA-based TMN services: Extensions to support service-oriented 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/Q/T-REC-Q.819-202201-I_PDF-E/raw.md b/marked/Q/T-REC-Q.819-202201-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ec4fd2067db4d70d583301149cab74f2be3691a0 --- /dev/null +++ b/marked/Q/T-REC-Q.819-202201-I_PDF-E/raw.md @@ -0,0 +1,2213 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**Q.819** + +(01/2022) + +SERIES Q: SWITCHING AND SIGNALLING, AND +ASSOCIATED MEASUREMENTS AND TESTS + +Q3 interface + +--- + +**REST-based management services** + +Recommendation ITU-T Q.819 + +ITU-T + +![ITU logo](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 white grid pattern, and the letters 'ITU' in white, bold, sans-serif font, superimposed on the globe. + +ITU logo + +# ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS** + +| | | +|--------------------------------------------------------------------------------|--------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 | +| Q3 INTERFACE | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 | +| TESTING SPECIFICATIONS | Q.3900–Q.4099 | +| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100–Q.4139 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000–Q.5049 | +| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050–Q.5069 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T Q.819 + +## REST-based management services + +## Summary + +Recommendation ITU-T Q.819 defines a set of services required to support REST-based interfaces and, with Recommendation ITU-T X.785, composes a framework for REST-based network management interfaces. It specifies protocol requirements and defines some network management-specific support services, which are notification service, heartbeat service and containment service. The JSON/YAML interface definitions for the network management-specific support services are also provided. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T Q.819 | 2022-01-13 | 2 | 11.1002/1000/14835 | + +## Keywords + +5G, AI, energy saving, telecom operation management. + +--- + +\* 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/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 2022 + +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 ..... | 3 | +| 6 REST-based network management services – goals and requirements..... | 4 | +| 6.1 Goals..... | 4 | +| 6.2 Information modelling dependencies ..... | 4 | +| 6.3 Notifications ..... | 5 | +| 7 Framework overview and protocol requirements ..... | 5 | +| 7.1 Framework overview ..... | 5 | +| 7.2 Protocol, languages and services requirements ..... | 6 | +| 8 REST-based notification service and notification format ..... | 7 | +| 8.1 REST-based notification service overview ..... | 7 | +| 8.2 Mapping of operations from [ITU-T M.3702] ..... | 7 | +| 8.3 Notification format definitions ..... | 9 | +| 9 REST-based heartbeat service ..... | 15 | +| 10 REST-based containment service ..... | 17 | +| 11 Compliance and conformance ..... | 20 | +| 11.1 System conformance points..... | 20 | +| 11.2 Basic conformance profile..... | 20 | +| Annex A – YAML/JSON scheme definition of framework support services ..... | 21 | +| A.1 REST-based notification service interface ..... | 21 | +| A.2 REST-based heartbeat service interface ..... | 36 | +| A.3 REST-based containment service interface ..... | 41 | +| Bibliography..... | 46 | + + + +# Recommendation ITU-T Q.819 + +## REST-based management services + +# 1 Scope + +The network management architecture defined in [ITU-T M.3010] introduces the use of multiple management protocols. So far, GDMO/CMIP, CORBA GIOP/IIOP, SMI/SNMP and Web Service/SOAP are possible choices at the application layer. Based on the management interface specification methodology defined in [ITU-T M.3020], more technology-based paradigms can be introduced into network management interfaces, and representational state transfer/hyper text transfer protocol (REST/HTTP) is now an additional paradigm for network management. + +This Recommendation, together with [ITU-T X.785], sets out to define a framework for defining how interfaces supported by management systems and network elements should be modelled using the REST / JavaScript object notation (JSON) schema. It is within the scope of this Recommendation to provide the following guidelines or instructions: + +- protocol requirements for using REST in network management; +- how a REST-based notification service is used in network management interfaces; +- how to monitor the availability of a REST notification forwarding mechanism; +- how to access containment information through a REST containment service; +- compliance and conformance requirements. + +# 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 (2017), *Management interface specification methodology*. +- [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), *Information technology – Open Systems Interconnection – Systems management overview*. +- [ITU-T X.703] Recommendation ITU-T X.703 (1997), *Information technology – Open Distributed Management Architecture*. +- [ITU-T X.721] Recommendation ITU-T X.721 (1992), *Information technology – Open Systems Interconnection – Structure of management information: Definition of management information*. +- [ITU-T X.785] Recommendation ITU-T X.785 (2021), *Guidelines for defining REST-based managed objects and management interfaces*. +- [IETF RFC 3986] IETF RFC 3986 (2005), *Uniform Resource Identifier (URI): Generic Syntax*. + +- [IETF RFC 6585] IETF RFC 6585 (2012), *Additional HTTP Status Codes*. +- [IETF RFC 7230] IETF RFC 7230 (2014), *Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing*. +- [IETF RFC 7231] IETF RFC 7231 (2014), *Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content*. +- [IETF RFC 7232] IETF RFC 7232 (2014), *Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests*. +- [IETF RFC 7540] IETF RFC 7540 (2015), *Hypertext Transfer Protocol Version 2 (HTTP/2)*. +- [IETF RFC 8259] IETF RFC 8259 (2017), *The JavaScript Object Notation (JSON) Data Interchange Format (JSON)*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 agent** [ITU-T M.3020]: 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. + +**3.1.2 managed object class** [ITU-T X.701]: A named set of managed objects sharing the same (named) sets of attributes, notifications, management operations (packages), and which share the same conditions for presence of those packages. + +**3.1.3 manager** [ITU-T M.3020]: 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. + +**3.1.4 notification** [ITU-T X.703]: An interaction for which the contract between the invoking object (client) and the receiving object (server) is restricted to the ability of the server to receive the contents of information sent by the client. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|--------------------------------------------------| +| CMIP | Common Management Information Protocol | +| CORBA | Common Object Request Broker Architecture | +| CRUD | Create, Read, Update and Delete | +| DN | Distinguished Name | +| GDMO | Guidelines for the Definition of Managed Objects | +| GIOP | General Inter-ORB Protocol | +| HTTP | Hyper Text Transfer Protocol | +| IIOP | Internet Inter-ORB Protocol | +| JSON | JavaScript Object Notation | + +| | | +|------|---------------------------------------| +| MO | Managed Object | +| REST | Representational State Transfer | +| SMI | Structure of Management Information | +| SNMP | Simple Network Management Protocol | +| SOAP | Simple Object Access Protocol | +| TMN | Telecommunications Management Network | +| URI | Uniform Resource Identifier | +| URL | Unified Resource Location | +| XML | extensible Markup 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 REST-based network management services – goals and requirements + +This clause describes the key goals of the services framework and the requirements that help the REST-based network management services support these goals. Clause 6.1 introduces the goals of the REST-based services framework. Clause 6.2 then provides terminology and requirements. The requirements in this clause are requirements that the framework must satisfy and that are based on telecommunications management needs. Clauses 7, 8 and 9 then describe a framework that meets these needs and defines how to achieve the requirements of this clause by using REST-based services in a certain way. + +## 6.1 Goals + +This Recommendation sets out a framework for defining how interfaces supported by management systems and network elements should be modelled. Some key goals of the framework are identified here: + +- application interoperability; +- common REST-based support services. + +This clause elaborates on these two goals. + +### 6.1.1 Application interoperability + +A key goal of the network management architecture, and in particular the information architecture, is to promote a standard framework for providing interoperability and information exchange between systems from a diverse set of network management system suppliers. Interoperability between systems involves many aspects of development. At its lowest layer, a common communication mechanism must be in place to support a common syntax, the establishment of connectivity and the exchange of operation requests/replies between systems. This aspect of interoperability is inherently supported by the REST/HTTP specifications. + +For network management, there is a need to provide application interoperability. That is, management systems from diverse suppliers will be utilized within a single administration's telecommunications management network (TMN) to support the different functions necessary to support the management of its networks. To simplify the integration of these various suppliers' systems, they must agree on the semantics of the information being exchanged. This is accomplished with the specification of an information model. Guidelines for the definition of REST-based information models are specified in [ITU-T X.785], but the services defined here should also support those guidelines. + +### 6.1.2 Common REST-based support services + +A second aspect of this framework is the definition of the common usage and profiling of the distributed processing environment of choice. This aspect of the framework should indicate the reasonable expectations network management system suppliers may have of one another. Rather than redefining the interface capabilities needed to support common network management functions such as a notification service with each information model, the modelling guidelines in [ITU-T X.785] rely upon a set of support services. These support services enable the information models to be simpler, and also enhance interoperability. + +## 6.2 Information modelling dependencies + +As described in the previous clause, the explicit modelling of resources that are manageable across an interface is central to application interoperability. The guidelines for defining REST-based managed objects (MOs) detailed in [ITU-T X.785] describe the rules for modelling manageable resources. They also embody several decisions that must be supported by the network management REST-based services framework. This clause summarizes those points. + +### 6.2.1 Access granularity + +REST-based service interface granularity refers to the relationship between the resources that are modelled on an interface and the means by which they are accessed using REST-based services. The objects that represent manageable resources are called MOs. Recommendation [ITU-T X.785] uses a service-grain modelling approach which means each modelled resource is only accessible through either the generic MO access service, or a user defined REST service specific for various MO classes. + +### 6.2.2 Representation of containment and naming + +Containment is a logical representation of how modelled resources contain other modelled resources. Containment has traditionally been a very important relationship in network management applications because it is a convenient means of identifying the large number of resources that typically must be managed. The [ITU-T X.785] guidelines require that a unique name be assigned to each MO, based in part on the name of the object that contains it. The REST-based management services must provide the means to store these names (and hence the containment relationships they represent). + +### 6.2.3 Object creation and deletion + +The REST-based platforms do not provide clients with the particular means to create or delete objects on remote systems. Instead, these functionalities are provided by remote systems for clients to create or delete objects on the remote system. Recommendation [ITU-T X.785] provides a common object accessing service, so object creation and deletion can be model independent. When deleting an object that contains other objects, the containment relationship shall be retained, so that there will be no orphan objects existing in the remote systems. The containment information should be stored in the remote system and be maintained when creation and deletion take place. + +## 6.3 Notifications + +The framework needs to support the ability to: + +- deliver notifications; +- subscribe for notification types; +- forward notifications to multiple destinations; +- uniquely identify the resource that emits the notification. + +# 7 Framework overview and protocol requirements + +## 7.1 Framework overview + +This framework for REST-based management interfaces is a collection of capabilities. The framework defines the support services to be standards on network management interfaces conforming to this framework. The REST interfaces for these services will be defined in Annex A. + +To support the software objects representing manageable resources, the framework requires that they implement some common basic capabilities. Therefore, one base class (YAML/JSON-based) is defined in [ITU-T X.785] for use in modelling network management resources. MO classes in information models must inherit and implement a basic set of capabilities from the base class in order to operate within this framework. Finally, some rules and conventions are defined for information modellers developing models for use with this framework. These consist of modelling guidelines and YAML/JSON style idioms. All of these are depicted graphically in Figure 1. + +![Figure 1 – Framework overview diagram showing the hierarchy of managed objects, services, and conventions.](d4af765160d04ecef538e5066006dc77_img.jpg) + +The diagram illustrates the framework overview. At the top, three boxes represent conventions: 'Principle for REST-based interface design', 'Style conventions for JSON/YAML schema specification', and 'Other conventions: (Containment, inheritance, association)'. Below these, a dashed oval labeled 'Managed object (a JSON/YAML schema object)' is identified as the 'Super class:'. To its right, a box labeled 'Generic MO accessing methods' has a dashed arrow pointing to it from a dashed oval labeled 'Other specific managed object'. This oval is part of a large box labeled 'Application-specific objects'. An arrow labeled 'Inherits' points from the 'Other specific managed object' oval to the 'Managed object' oval. Another arrow labeled 'Accesses' points from the 'Generic MO accessing methods' box to the 'Other specific managed object' oval. Below the application-specific objects box, a section labeled 'Support services:' contains three boxes: 'Notification service', 'Heartbeat service', and 'Containment service'. At the very bottom, a box represents the communication protocol 'HTTP 1.1/2.0'. The entire diagram is enclosed in a grey border. A small label 'Q.819(22)' is in the bottom right corner. + +Figure 1 – Framework overview diagram showing the hierarchy of managed objects, services, and conventions. + +Q.819(22) + +**Figure 1 – Framework overview** + +Figure 1 shows the framework in grey. In the middle are the application-specific objects that are supported by the framework. Along the bottom is a box representing the communication protocol, HTTP 1.1 or 2.0. Above that are a number of boxes with names in them representing the services that compose this framework. Along the top of the figure are icons representing the super class ManagedObject, and the generic MO accessing methods. Each MO supported by this framework must ultimately inherit from the super class. Also shown in Figure 1 are squares with downturned corners representing standard object modelling conventions. + +The framework services, represented as boxes with square corners, are defined in this Recommendation. The super class, object modelling conventions and other conversions are defined in [ITU-T X.785]. + +## 7.2 Protocol, languages and services requirements + +This clause defines the versions of the languages and protocols that are required to support this framework. REST-based technology and protocol specifications are defined by IETF and OAI. Table 1 shows which version (including subsequent versions released up until the publication date of this Recommendation) of the applicable specifications must be supported to comply with this framework. + +**Table 1 – REST-based language, protocol and versions** + +| Language and protocol | Version | References | +|-------------------------|--------------------------------------------------|--------------------------------------------------------------------| +| YAML Schema (OAI) | 3.0 | [b-OAI-OAS3] | +| JSON Schema Core (IETF) | Draft 2020-12 (Draft-08-patch-1, December, 2020) | [IETF RFC 8259] | +| HTTP protocol (IETF) | 1.1 (2014)
2.0 (August, 2017) | [IETF RFC 7230], [IETF RFC 7231], [IETF RFC 7232], [IETF RFC 7540] | + +# 8 REST-based notification service and notification format + +## 8.1 REST-based notification service overview + +REST-base notification service provides a standard approach for notification consumers and providers to transfer notification information using a topic-based publish/subscribe pattern. The contents of the notification service include standard message exchanges to be implemented by notification providers, operational requirements expected of service providers and requesters that participate in notifications and an JSON model that describes topics. + +The REST-based notification service supports the asynchronous exchange of event messages between clients using a subscribe-and-publish paradigm. + +## 8.2 Mapping of operations from [ITU-T M.3702] + +Recommendation [ITU-T M.3702] provides protocol neutral requirements and analysis for the generic notification management service, which defines the generic functions that are to be implemented by a protocol-specific management paradigm. In this framework, the generic notification management model is mapped to the JSON/HTTP definition. + +Table 2 indicates the mapping from [ITU-T M.3702] to the REST-based notification service. + +**Table 2 – Notification operations mapping from [ITU-T M.3702] to this Recommendation** + +| No. | [ITU-T M.3702] | | [ITU-T Q.819] | | +|-----|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Operation name | | Operation name | | +| | Request/
response | Parameters | Request/
response | Parameters | +| 1 | subscribeNotification | | HTTP POST | | +| | Input
parameter |
  • – managerId
  • – notificationTypes
  • – filteringCriteria
  • – destination
| Request | "POST" {notificationServiceURI}/"subscriptions"
{HTTPVersion}
request body schema:
\$ref: "notificationApiDataSchema.json#/definitions/SubscribeNotificationRequest" | +| | Output
parameter |
  • – subscriptionId
  • – status
| Response | {HTTPVersion} {statusCode} {reasonPhrase}
Location: {notificationServiceURI}/"subscriptions"/
{subscriptionId} {response body} | +| 2 | unsubscribeNotification | | HTTP DELETE | | +| | Input
parameter |
  • – managerId
  • – subscriptionId
| Request | "DELETE" {notificationServiceURI}/"subscriptions"/
{subscriptionId} {HTTPVersion} | +| | Output
parameter |
  • – status
| Response | {HTTPVersion} {statusCode} {reasonPhrase}
{response body} | +| 3 | suspendSubscription | | HTTP POST | | +| | Input
parameter |
  • – managerId
  • – subscriptionId
| Request | "POST" {notificationServiceURI}/"subscriptions"/
{subscriptionId}/"suspendSubscription"
{HTTPVersion} | +| | Output
parameter |
  • – status
| Response | {HTTPVersion} {statusCode} {reasonPhrase}
{response body}
Response body schema:
\$ref: "notificationApiDataSchema.json#/definitions/NotificationInfo" | + +**Table 2 – Notification operations mapping from [ITU-T M.3702] to this Recommendation** + +| No. | [ITU-T M.3702] | | [ITU-T Q.819] | | +|-----|------------------------|--------------------------------------------------------------------------------------------------------------|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Operation name | | Operation name | | +| | Request/
response | Parameters | Request/
response | Parameters | +| 4 | resumeSubscription | | HTTP POST | | +| | Input
parameter | – managerId
– subscriptionId | Request | "POST" {notificationServiceURI}/"subscriptions"/{subscriptionId}/"resumeSubscriptions" {HTTPVersion} | +| | Output
parameter | – status | Response | {HTTPVersion} {statusCode} {reasonPhrase} {response body} | +| 5 | getNotificationTypes | | HTTP GET | | +| | Input
parameter | – notificationIRPIId | Request | "GET" {notificationServiceURI}/NotificationTypes {HTTPVersion} | +| | Output
parameter | – status
– notificationType
List | Response | {HTTPVersion} {statusCode} {reasonPhrase} {response body}
Response body schema:
\$ref:"notificationApiDataSchema.json#/definitions/GetNotificationTypesResponse" | +| 6 | querySubscription | | HTTP GET | | +| | Input
parameter | – subscriptionId | Request | "GET" {notificationServiceURI}/"subscriptions"/{subscriptionId} {HTTPVersion} | +| | Output
parameter | – subscribed
NotificationType
– subscriptionStatus
– destination
– filteringCriteria
– status | Response | {HTTPVersion} {statusCode} {reasonPhrase} {response body}
Response body schema:
\$ref: "notificationApiDataSchema.json#/definitions/QuerySubscriptionResponse" | +| 7 | modifySubscription | | HTTP PATCH | | +| | Input
parameter | – subscriptionId
– filteringCriteria
– destination
– notificationTypes | Request | "PATCH" {notificationServiceURI}/"subscriptions"/{subscriptionId} {HTTPVersion} {request body}
Request body schema:
\$ref:"notificationApiDataSchema.json#/definitions/ModifySubscriptionRequest" | +| | Output
parameter | – status | Response | {HTTPVersion} {statusCode} {reasonPhrase} {response body}
Response body schema:
\$ref: "notificationApiDataSchema.json#/definitions/NotificationInfo" | +| 8 | listAllSubscriptionIds | | HTTP GET | | +| | Input
parameter | – managerId | Request | "GET" {notificationServiceURI}/"subscriptions"/listAllSubscriptionIds {HTTPVersion} {request body}
Request body schema:
\$ref: "notificationApiDataSchema.json#/definitions/ListAllSubscriptionIdsRequest" | +| | Output
parameter | – subscriptionIdSet
– status | Response | {HTTPVersion} {statusCode} {reasonPhrase} {response body}
Response body schema:
\$ref:"notificationApiDataSchema.json#/definitions/ListAllSubscriptionIdsResponse" | + +**Table 2 – Notification operations mapping from [ITU-T M.3702] to this Recommendation** + +| No. | [ITU-T M.3702] | | [ITU-T Q.819] | | +|-----|----------------------|------------|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Operation name | | Operation name | | +| | Request/
response | Parameters | Request/
response | Parameters | +| 9 | report notification: | | HTTP POST (from provider to consumer) | | +| | | | Request | "POST" {destinationURI} {HTTPVersion}
{request body}
Request body schema:
\$ref: "notificationApiDataSchema.json#
/definitions/NotifyRequest" | +| | | | Response | {HTTPVersion} {statusCode} {reasonPhrase}
{response body} | + +A detailed interface definition using YAML can be found in clause A.1. + +## 8.3 Notification format definitions + +### 8.3.1 Notification format to be used in this Recommendation + +This clause will provide a description for the notification format to be used in this Recommendation. + +### 8.3.2 Common notification header definition + +This clause provides the detailed common notification header described in [ITU-T M.3702]. +Table 3 provides the definition of the parameters of the common notification header. + +**Table 3 – Common notification header definition** + +| Parameter name | Qualifiers | JSON/YAML-schema type | Descriptions | +|----------------|------------|---------------------------|-----------------------------------------------------------------------------------------------------------------------------| +| objectClass | M | string | It is the class name of the MO which sends out this notification.
See clause 7.3.5 of [ITU-T M.3702] | +| objectInstance | M | uri | It is the distinguished name (DN) of the MO which sends out this notification.
See clause 7.3.5 of [ITU-T M.3702] | +| notificationId | M | string | It is the identifier of the notification for the purpose of notification correlation.
See clause 7.3.5 of [ITU-T M.3702] | +| eventTime | M | string | It is the time when this event happened.
See clause 7.3.5 of [ITU-T M.3702] | +| systemDN | M | type:string
format:uri | It is the DN of the system which sends out this notification.
See clause 7.3.5 of [ITU-T M.3702] | + +**Table 3 – Common notification header definition** + +| Parameter name | Qualifiers | JSON/YAML-schema type | Descriptions | +|------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| notificationType | M | NotificationType:
type: string
enum:
- objectCreation
- objectDeletion
-
attributeValueChange
- stateChange
-
communicationAlarm
-
environmentalAlarm
- equipmentAlarm
-
processingErrorAlarm
-
qualityOfServiceAlarm
-
integrityViolation
-
operationalViolation
-
physicalViolation
-
securityViolation
-
timeDomainViolation
-
relationshipChange
- heartbeat | It indicates the type of notification. See clause 7.3.5 of [ITU-T M.3702].
The possible common notification types defined in this Recommendation can be found in the list in the left column.
This list can be extended to include new notification types when they are defined. | + +### **8.3.3 Common notification contents definition** + +- 1) Notification contents for the objectCreation and objectDeletion notifications are shown in Table 4. + +**Table 4 – Notification contents for objectCreation and objectDeletion** + +| Notification parameter | Qualifiers | Data type | Descriptions | +|-------------------------|------------|------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------| +| correlatedNotifications | O | CorrelatedNotifications
type: array
items:
type: string | List of correlated notifications | +| additionalText | O | string | Text message | +| additionalInfo | O | string | Additional information not in text format. (The information will be provided in JSON strings. Below is the same.) | + +**Table 4 – Notification contents for objectCreation and objectDeletion** + +| Notification parameter | Qualifiers | Data type | Descriptions | +|------------------------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------| +| sourceIndicator | O | SourceIndicator:
type: string
format: enum
- resourceOperation
- managementOperation
- unknown | Cause of event | +| attributeList | O | NVPairList:
type: object
properties:
attributeList:
type: array
items:
\$ref:
'#/.../NVPair'
NVPair:
type: object
properties:
name:
type: string
value:
type: string
type:
type: string | Attribute values | + +2) Notification contents for the attributeValueChange notification are shown in Table 5. + +**Table 5 – Notification contents for attributeValueChange** + +| Notification parameter | Qualifiers | Data type | Descriptions | +|-------------------------|------------|-------------------------|-------------------------------------------| +| correlatedNotifications | O | CorrelatedNotifications | List of correlated notifications | +| additionalText | O | string | Text message | +| additionalInfo | O | string | Additional information not in text format | +| sourceIndicator | O | SourceIndicator | Cause of event | +| attributeChanges | M | NVPairList | Changed attributes | + +- 3) Notification contents for the stateChange notification are shown in Table 6. + +**Table 6 – Notification contents for stateChange** + +| Notification parameter | Qualifiers | Data type | Descriptions | +|-------------------------|------------|-------------------------|-------------------------------------------| +| correlatedNotifications | O | CorrelatedNotifications | List of correlated notifications | +| additionalText | O | string | Text message | +| additionalInfo | O | string | Additional information not in text format | +| sourceIndicator | O | SourceIndicator | Cause of event | +| stateChanges | M | NVPairList | Changed states | + +- 4) Notification contents for the communicationAlarm, environmentalAlarm, equipmentAlarm, processingErrorAlarm and qualityOfServiceAlarm notifications are shown in Table 7. + +**Table 7 – Notification contents for alarms** + +| Notification parameter | Qualifiers | Data type | Descriptions | +|-------------------------|------------|---------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| correlatedNotifications | O | CorrelatedNotifications | List of correlated notifications | +| additionalText | O | string | Text message | +| additionalInfo | O | string | Additional information not in text format | +| probableCause | M | string | The probable cause of the alarm | +| specificProblems | O | SpecificProblems:
type: array
items:
type: string | Non-standardized problems | +| perceivedSeverity | M | AlarmSeverity:
type: string
format: enum
- indeterminate
- critical
- major
- minor
- warning
- cleared | It indicates the perceived severity of the alarm. See type definition for details. | +| backedUpStatus | O | boolean | "True" if backed up | +| backUpObject | O | type: string
format: uri | It indicates the DN of the backup object if the backUpStatus is "false". | + +**Table 7 – Notification contents for alarms** + +| Notification parameter | Qualifiers | Data type | Descriptions | +|------------------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------| +| trendIndication | O | TrendIndication:
type: string
format: enum
- lessSevere
- noChange
- moreSevere | See type for details | +| thresholdInfo | O | ThresholdInfo:
type: object
properties:
attributeID:
type: string
observedValue:
type: number
format: float
thresholdLevel:
\$ref:
'#/.../ThresholdLevelInd'
armTime:
type: string
format: date-time

ThresholdLevelInd:
type: object
properties:
indication:
\$ref:
'#/.../ThresholdIndication'
low:
type: number
format: float
high:
type: number
format: float

ThresholdIndication:
type: string
format: enum
- up
- down | See type for details | +| stateChangeDefinition | O | NVPairList | It indicates the state changes in this alarm. | +| monitoredAttributes | O | type: array
items:
type: string | See type for details. | +| proposedRepairActions | O | type: array
items:
type: string | It indicates the proposed actions to repair this fault. | + +**Table 7 – Notification contents for alarms** + +| Notification parameter | Qualifiers | Data type | Descriptions | +|------------------------|------------|------------------------------------------------------|----------------------------------------------------------------------------| +| alarmEffectOnService | O | boolean | True if alarm is service effecting | +| alarmingResumed | O | boolean | True if alarming was just resumed, possibly resulting in delayed reporting | +| suspectObjectList | O | type: array
items:
type: string
format: uri | Objects possibly involved in failure | + +5) Notification contents for the integrityViolation, operationalViolation, physicalViolation, securityViolation and timeDomainViolation notifications are shown in Table 8. + +**Table 8 – Notification contents for violations** + +| Notification parameter | Qualifiers | Data type | Descriptions | +|-------------------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| +| correlatedNotifications | O | CorrelatedNotifications | List of correlated notifications | +| additionalText | O | string | Text message | +| additionalInfo | O | string | Additional information not in text format | +| securityAlarmCause | M | string | The cause of the security alarm | +| securityAlarmSeverity | M | AlarmSeverity | Clears allowed? [ITU-T X.721] appears to restrict the cleared value on this alarm, but clears should be allowed. | +| securityAlarmDetector | M | SecurityAlarmDetector:
type: object
properties:
mechanism:
\$ref: '#/.../UID'
obj:
type: string
format: uri
UID:
type: object
properties:
uri:
type: string
format: uri
value:
type: integer
format: unsignedLong | See type for details | + +**Table 8 – Notification contents for violations** + +| Notification parameter | Qualifiers | Data type | Descriptions | +|------------------------|------------|-----------|-------------------------------------------------------| +| serviceUser | M | string | The user of the service which is violated | +| serviceProvider | M | string | The service provider of the service which is violated | + +6) Notification contents for the relationshipChange notification are shown in Table 9. + +**Table 9 – Notification contents for relationshipChange** + +| Notification parameter | Qualifiers | Data type | Descriptions | +|-------------------------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| +| correlatedNotifications | O | CorrelatedNotifications | List of correlated notifications | +| additionalText | O | string | Text message | +| additionalInfo | O | string | Additional information not in text format | +| sourceIndicator | O | SourceIndicator | Cause of event | +| relationshipChanges | M | AttributeChangeSet:
type: array
items:
\$ref: '#/.../AttributeChange'
AttributeChange:
type: object
properties:
attributeName:
type: string
attributeType:
type: string
oldValue:
type: string
newValue:
type: string | Changed relationship attributes | + +The detailed data type definitions for notification contents can be found in clause A.1. + +## 9 REST-based heartbeat service + +The heartbeat service is used to verify the operation of the notification forwarding mechanism in a managed system as well as that of the communications network between the managed system and managing system. + +It periodically sends a small notification to a managing system interested in receiving it and that notification identifies the system that emitted the heartbeat. After configuring this service, a managing system can ensure the notification service is functioning. Since these notifications flow through the same software and networks as notifications from other resources, they periodically verify the operation of these resources. + +The heartbeat service contains the following operations: + +### (1) Heartbeat operation: + +The "heartbeat" operation is used by the managed system to send a brief heartbeat notification to the management system. The heartbeat notification information type is HeartbeatMessageType. The operation is completed by the notify operation of the notification service defined. The corresponding REST interface definition is shown in Table 10. + +**Table 10 – Interface definition of heartbeat operation** + +| Name | Schema | +|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| REQUEST | "POST" {destinationURI}/"notifications" {HTTPVersion}
{RequestBody} | +| RequestBody | HeartbeatMessageType : : = {
Allof: [
{ NotificationBaseType },
{
systemLabel: string
period: string
timeStamp: string
}]
} | +| RESPONSE | {HTTPVersion} {StatusCode} {ReasonPhrase}
Location:
{destinationURI}/"notifications"/{notificationId}
{ResponseBody} | +| ResponseBody | HeartbeatMessageType | + +### (2) getHeartbeatAttributes operation: + +The getHeartbeatAttributes operation is used to get the value of the systemLabel and period attributes in the heartbeat notification. The REST interface definition for this operation contains the following: + +- a) The HTTP method: the operation of the query attribute should be mapped to the "GET" request method. +- b) The request URI: In the heartbeat service, the subscribed heartbeat notification is placed in the heartbeats collection resource of the heartbeat service for management, and is identified by the subscriptionId. The query parameter attributes are optional. If no query condition is added, it means that both systemLabel and period attribute values are obtained. If you want to query a specified attribute value, the attribute name to be queried is placed in the attributes query parameter of the request URI. + +Based on the above analysis, the REST interface definition of the getHeartbeatAttributes operation can be found in Table 11. + +**Table 11 – Interface definition of getHeartbeatAttributes operation** + +| Name | Schema | +|--------------|----------------------------------------------------------------------------------------------------------------------------| +| REQUEST | "GET" heartbeatServiceURI "/"
heartbeats/"subscriptionId
[ "?attributes="("systemLabel" "period") ]
HTTPVersion | +| RESPONSE | {HTTPVersion} {StatusCode} {ReasonPhrase}
{ResponseBody} | +| ResponseBody | HeartBeatAttributes : : = {
systemLabel: string
period: string
} | + +### (3) setHeartbeatAttributes operation: + +The setHeartbeatAttributes operation is used to set the value of the systemLabel and period attributes in the heartbeat notification. The REST interface definition for this operation contains the following: + +- a) The HTTP method: this operation is an operation to modify the attribute, and supports modification of some attributes, so it should be mapped to the 'PATCH' request method. +- b) The content of the request body: the setHeartbeatAttributes operation needs to give the attribute name and attribute value to be modified in the request body. The manager can modify the systemLabel and period attribute values at the same time, or modify only one of the attribute values. + +Based on the above analysis, the REST interface definition of the setHeartbeatAttributes operation can be found in Table 12. + +**Table 12 – Interface definition of setHeartBeatAttribute operation** + +| Name | Schema | +|-------------|------------------------------------------------------------------------------------------------------| +| REQUEST | "PATCH" { heartbeatServiceURI }/" heartbeats
"/{subscriptionId}
{HTTPVersion}
{RequestBody} | +| RequestBody | HeartbeatAttributes : : = {
systemLabel: string
period: string
} | +| RESPONSE | {HTTPVersion} {StatusCode} {ReasonPhrase} | + +The detailed JSON/YAML Schema and REST interface definitions can be found in clause A.2. + +## 10 REST-based containment service + +In the network management field, a function is needed to be able to report which objects are contained by a superior object, to verify that a superior object exists before a subordinate is created, to make sure two objects with the same name are not created, etc. The containment service is defined in this framework to support this function. + +The main functions to be supported by the containment service are to enable a managing system to query a managed system with the name of an MO, and receive back the names of the objects contained by this object. In addition, a means of getting names added to and removed from the service will be defined. These are not for use by managing systems but internally by MOs, factories and other parts of a managed system. They are provided to promote the development of reusable components, possibly by third parties, and are defined on an interface separate from that used by managing systems. + +The containment service provides three operations to retrieve containment information. A short description of the operation semantics in the containment service is described as follows: + +### (1) exists operation: + +The exists operation is used to check whether a specified MO is registered in the containment service or not. The REST interface definition for this operation contains the following: + +- a) The HTTP method: the operation of the query attribute should be mapped to the "GET" request method. +- b) The request URI: In the containment service, the "ContainmentService/exists" is used as the collection resource for this operation, and the moInstance parameter in the path will provide the DN of the specified MO instance to be checked. + +Based on the above analysis, the REST interface definition of the exists operation can be found in Table 13. + +**Table 13 – Interface definition of exists operation** + +| Name | Schema | +|--------------|----------------------------------------------------------------------------------------------| +| REQUEST | "GET" {ContainmentServiceURI}
"/ContainmentService/exists/" {moInstance}
{HTTPVersion} | +| RESPONSE | {HTTPVersion} {StatusCode} {ReasonPhrase}
{ResponseBody} | +| ResponseBody | boolean | + +### (2) getContained operation: + +The "getContained" operation is used to retrieve the names of all the resources contained in the specified MO. It uses DN (URI1) to identify the target MO and then return the list of the URIs of the MOs that are contained under this MO instance. The REST interface definition for this operation contains the following: + +- a) The request URI: Since the operation cannot be mapped to the basic create, read, update and delete (CRUD) operations, it is represented by a Task Resource URI, and the actionName is used to indicate the operation to be performed after the resource object URI to be operated. The actionName of the operation is represented by 'getContained'. +- b) The HTTP method: this operation is a query operation, so the 'GET' request method is used. + +1 URI is defined in [IETF RFC 3986]. Based on the descriptions provided in [IETF RFC 3986]: URL refers to the subset of URIs that, in addition to identifying a resource, provide a means of locating the resource by describing its primary access mechanism (e.g., its network "location"). Within this Recommendation, only URI is used. + +- c) There are two input parameters for this operation. The first one is the baseMO, which indicates the root MO instance of a subtree to be queried. The other parameter is scope, which indicates the scope of the subtree to be queried for containment: BasicObjectOnly, WholeSubTree, IndividualLevel and BaseToLevel (the semantic explanation of the above four choices can be found in clause 6.3 of [b-ITU-T Q.818]); when the choices are IndividualLevel or BaseToLevel, an extra optional parameter *level* is provided, which is a positive integer. +- d) Possible response codes and corresponding response body contents: The possible status codes of the method are 200, 400, 404, 405 and 500. When the status code is 200, the contained object instance URI list information in the scope is returned in the response body. The type is defined as MOList, which is an array type of string. Each element in the list is a string type in URI format. + +Based on the above analysis, the REST interface definition of the getContainment operation can be found in Table 14. + +**Table 14 – Interface definition of getContained operation** + +| Name | Schema | +|--------------|------------------------------------------------------------------------------------------------------------| +| REQUEST | "GET" {ContainmentServiceURI}
"/ContainmentService/getContained/"
{moInstance}/{scope} {HTTPVersion} | +| actionName | "getContained" | +| RESPONSE | {HTTPVersion} {StatusCode} {ReasonPhrase}
{ResponseBody} | +| ResponseBody | list of string | + +### (3) getContainedByClass operation: + +The "getContainedByClass" operation is used to retrieve the names of all the resources contained in the specified MO, whose MO class should be the same value as the input parameter. The semantic of this operation is very similar to the operation "getContained", the only difference is that the returned MO name list is filtered by the input parameter *class*. The REST interface definition for this operation contains the following: + +- a) The request URI: The operation is represented by a Task Resource URI and the actionName is 'getContainedByClass'. +- b) The HTTP method: This operation is a query operation, so the 'GET' request method is used. +- c) There are three input parameters, baseMO, scope and class. The first two have the same semantic as defined in the "getContained" operation. The last parameter class is a string, which indicates the MO class for filtering. +- d) Possible response codes and corresponding response body contents: The possible status codes of the method are 200, 400, 404, 405 and 500. When the status code is 200, the contained object instance URI list information in the scope with the specified class is returned in the response body. + +Based on the above analysis, the REST interface definition of the getContainmentByClass operation can be found in Table 15. + +**Table 15 – Interface definition of getContainedByClass operation** + +| Name | Schema | +|--------------|---------------------------------------------------------------------------------------------------------------------------| +| REQUEST | "GET" {ContainmentServiceURI}
"/ContainmentService/getContainedByClass/"
{moInstance}/{scope}/{class} {HTTPVersion} | +| actionName | "getContainedByClass" | +| RESPONSE | {HTTPVersion} {StatusCode} {ReasonPhrase}
{ResponseBody} | +| ResponseBody | list of string | + +The detailed JSON/YAML Schema and REST interface definitions can be found in Annex A.3. + +[IETF RFC 7231] and [IETF RFC 6585] provide dozens of definitions for status code, which will likely be referenced in implementations of this Recommendation. The list of status codes can be found in Table A.2 of [ITU-T X.785]. + +# 11 Compliance and conformance + +This clause defines the criteria that must be met by other standards documents claiming compliance to this framework and the functions that must be implemented by systems claiming conformance to this Recommendation. + +## 11.1 System conformance points + +This clause summarizes the individual functions described earlier in this Recommendation. These conformance points are then combined in profiles that must be supported by systems claiming conformance to this Recommendation. + +- 1) An implementation claiming conformance to the notification service must: + - support the notification service requirements and interface described in clause 8 and defined in the YAML/JSON schema in clause A.1; + - support the notification format described in clause 8.3 and defined in the YAML/JSON schema in clause A.1. +- 2) An implementation claiming conformance to the heartbeat service must: + - support the heartbeat service requirements and interface described in clause 9 and defined in the YAML/JSON schema in clause A.2. +- 3) An implementation claiming conformance to the containment service must: + - support the containment service requirements and interface described in clause 10 and defined in the YAML/JSON schema in clause A.3. + +## 11.2 Basic conformance profile + +A system claiming conformance to this Recommendation's basic profile shall support: + +- 1) the version of JSON/YAML schema and HTTP protocol as specified in clause 7.2; +- 2) the notification service (see conformance point 1); +- 3) the heartbeat service (see conformance point 2); +- 4) the containment service (see conformance point 3). + +## Annex A + +## YAML/JSON scheme definition of framework support services + +(This annex forms an integral part of this Recommendation.) + +## A.1 REST-based notification service interface + +#### A.1.1 JSON-schema definitions for REST-based notification service interface + +The following provides the HTTP requests and responses for REST-based notification service interface. + +##### 1) subscribeNotification + +###### REQUEST: + +"POST" {notificationServiceURI}/"subscriptions" {HTTPVersion} + +response body schema: + +\$ref: "notificationApiDataSchema.json#/definitions/SubscribeNotificationRequest" + +###### RESPONSE: + +{HTTPVersion} {statusCode} {reasonPhrase} + +Location: { notificationServiceURI }/"subscriptions"/{subscriptionId} + +{response body} + +| statusCode | reasonPhrase | response body schema | +|------------|-----------------------|------------------------------------------------------------------------------| +| 201 | Created | null or \$ref:"notificationApiDataSchema.json#/definitions/NotificationInfo" | +| 400 | Bad Request | \$ref:"commonApiDataSchema.json#/definitions/ErrorInformation" | +| 404 | Not Found | null | +| 409 | Conflict | null | +| 500 | Internal Server Error | null | + +##### 2) unsubscribeNotification + +###### REQUEST: + +"DELETE" {notificationServiceURI}/"subscriptions"/{subscriptionId} {HTTPVersion} + +###### RESPONSE: + +{HTTPVersion} {statusCode} {reasonPhrase} + +{response body} + +| statusCode | reasonPhrase | response body schema | +|------------|-----------------------|----------------------| +| 200 | OK | null | +| 404 | Not Found | null | +| 405 | Method Not Allowed | null | +| 500 | Internal Server Error | null | + +##### 3) suspendNotification + +###### REQUEST: + +"POST" { notificationServiceURI } /"subscriptions"/{subscriptionId}/ +"suspendSubscription" {HTTPVersion} + +###### RESPONSE: + +{HTTPVersion} {statusCode} {reasonPhrase} +{response body} + +| statusCode | reasonPhrase | response body schema | +|-------------------|-----------------------|-----------------------------| +| 200 | OK | null | +| 404 | Not Found | null | +| 405 | Method Not Allowed | null | +| 409 | Conflict | null (Already suspended) | +| 500 | Internal Server Error | null | + +##### 4) resumeSubscriptions + +###### REQUEST: + +"POST" { notificationServiceURI } /"subscriptions"/{subscriptionId}/ +"resumeSubscriptions" {HTTPVersion} + +###### RESPONSE: + +{HTTPVersion} {statusCode} {reasonPhrase} +{response body} + +| statusCode | reasonPhrase | response body schema | +|-------------------|-----------------------|-----------------------------| +| 200 | OK | null | +| 404 | Not Found | null | +| 405 | Method Not Allowed | null | +| 409 | Conflict | null (Already resumed) | +| 500 | Internal Server Error | null | + +##### 5) getNotificationTypes + +###### REQUEST: + +"GET" { notificationServiceURI } /"subscriptions"/{subscriptionId}/"getTypes" +{HTTPVersion} + +###### RESPONSE: + +{HTTPVersion} {statusCode} {reasonPhrase} +{response body} + +| statusCode | reasonPhrase | response body schema | +|-------------------|-----------------------|-----------------------------------------------------------------------------------| +| 200 | OK | \$ref: "notificationApiDataSchema.json#/definitions/GetNotificationTypesResponse" | +| 404 | Not Found | null | +| 500 | Internal Server Error | null | + +##### 6) querySubscription + +###### REQUEST: + +"GET" {notificationServiceURI}/"subscriptions"/{subscriptionId} {HTTPVersion} + +###### RESPONSE: + +{HTTPVersion} {statusCode} {reasonPhrase} +{response body} + +| statusCode | reasonPhrase | response body schema | +|------------|-----------------------|--------------------------------------------------------------------------------| +| 200 | OK | \$ref: "notificationApiDataSchema.json#/definitions/QuerySubscriptionResponse" | +| 404 | Not Found | null | +| 500 | Internal Server Error | null | + +##### 7) modifySubscription + +###### REQUEST: + +"PATCH" {notificationServiceURI}/"subscriptions"/{subscriptionId} +{HTTPVersion} +{request body} + +###### Request body schema: + +\$ref:"notificationApiDataSchema.json#/definitions/ModifySubscriptionRequest" + +###### RESPONSE: + +{HTTPVersion} {statusCode} {reasonPhrase} +{response body} + +| statusCode | reasonPhrase | response body schema | +|------------|-----------------------|----------------------------------------------------------------------------------| +| 200 | OK | null or
\$ref: "notificationApiDataSchema.json#/definitions/NotificationInfo" | +| 400 | Bad Request | \$ref: "commonApiDataSchema.json#/definitions/ErrorInformation" | +| 404 | Not Found | null | +| 405 | Method Not Allowed | null | +| 500 | Internal Server Error | null | + +##### 8) listAllSubscriptionIds + +###### REQUEST: + +"POST" {notificationServiceURI}/"subscriptions"/listAllSubscriptionIds +{HTTPVersion} +{request body} + +###### Request body schema: + +\$ref: +"notificationApiDataSchema.json#/definitions/ListAllSubscriptionsIdsRequest" + +###### RESPONSE: + +{HTTPVersion} {statusCode} {reasonPhrase} +{response body} + +| statusCode | reasonPhrase | response body schema | +|-------------------|-----------------------|-------------------------------------------------------------------------------------| +| 200 | OK | \$ref:"notificationApiDataSchema.json#/definitions/ListAllSubscriptionsIdsResponse" | +| 400 | Bad Request | \$ref:"commonApiDataSchema.json#/definitions/ErrorInformation" | +| 404 | Not Found | null | +| 500 | Internal Server Error | null | + +##### 9) notify + +###### **REQUEST:** + +"POST" {destinationURI} {HTTPVersion} +{request body} + +###### **Request body schema:** + +\$ref: "notificationApiDataSchema.json#/definitions/NotifyRequest" + +###### **RESPONSE:** + +{HTTPVersion} {statusCode} {reasonPhrase} +{response body} +response body schema: + +| statusCode | reasonPhrase | response body schema | +|-------------------|-----------------------|---------------------------------------------------------------| +| 200 | OK | null | +| 400 | Bad Request | \$ref:"commonApiDataSchema.json#/definition/ErrorInformation" | +| 404 | Not Found | null | +| 405 | Method Not Allowed | null | +| 500 | Internal Server Error | null | + +#### **A.1.2 YAML-schema definitions for REST-based notification service** + +Figure A.1 provides the YAML-schema definitions for REST-based notification service interface. + +NOTE – The "notify" operation in clause A.1.1 (9) is mapped to a callback in the YAML-schema interface definitions for the subscribeNotification operation of path /Subscription. + +``` + +openapi: 3.0.0 +info: + title: ITU-T_NotificationService + description: 'This is the formal definition of the ITU-T Notification Service.' + termsOfService: https://www.itu.int/en/ITU-T/about/Pages/default.aspx + contact: + email: zlwang@bupt.edu.cn + license: + name: Apache 2.0 + url: http://www.apache.org/licenses/LICENSE-2.0.html + version: 1.0.0 +externalDocs: + description: See Recommendation ITU-T Q.819 + url: https://www.itu.int/itu-t/recommendations/index.aspx?ser=X +servers: +- url: http://www.itu.int/sg2/rest/NotificationService/v1.0.0 + +``` + +``` + +- url: https://www.itu.int/sg2/rest/NotificationService/v1.0.0 +tags: +- name: NotificationService + description: All APIs related to the ITU-T Notification Service + externalDocs: + description: Find out more + url: https://www.itu.int/itu-t/recommendations/index.aspx?ser=X + +paths: + /Subscription: + post: + tags: + - NotificationService + summary: "subscribe notification" + description: "create an subscription in the notification services with the + specified parameters list" + operationId: "subscribeNotification" + requestBody: + description: "The input parameters of the subscribeNotification + operation" + content: + application/json: + schema: + $ref: '#/components/schemas/SubscribeNotificationRequest' + required: true + responses: + 201: + description: "Subscription is successfully created, and the new + Subscription ID value will be returned." + content: + application/json: + schema: + $ref: '#/components/schemas/subscriptionId' + 400: + description: "Parameter Error occurred in the subscribeNotification + operation" + content: + application/json: + schema: + $ref: '#/components/schemas/ErrorInfo' + 404: + description: "The URI does not exist" + content: {} + 409: + description: "Subscription Conflict" + content: {} + 500: + description: "Internal Server Error" + content: {} + callbacks: + notification: + '{$request.query.requestBody.destination}': + '{$request.query.requestBody.destination}?event={$request.query.requestBody.eventTypes}': + post: + requestBody: + content: + application/json: + schema: + +``` + +``` + + $ref: '#/components/schemas/NotificationInfo' + #example: + #messageasdfsdf: Some event + responses: + '200': + description: OK + +get: + tags: + - NotificationService + summary: "Get Subscription Information" + description: "get the list of Identifiers of all the existing Notification +Subscriptions" + operationId: "listAllSubscriptionIds" + responses: + 200: + description: "The attribute value list of the specified MO is +retrieved successfully" + content: + application/json: + schema: + type: array + items: + $ref: "#/components/schemas/subscriptionId" + 404: + description: "Specified Subscription Not found" + content: {} + 500: + description: "Internal Server Error" + content: {} + +/Subscription={subscriptionId}: + parameters: + - name: subscriptionId + in: path + description: "The unique Identifier of the notification Subscription" + required: true + schema: + type: string + +get: + tags: + - NotificationService + summary: "Query Subscription Information" + description: "query the attributes information of a specific Notification +Subscription" + operationId: "querySubscription" + responses: + 200: + description: "The attribute value list of the specified MO is +retrieved successfully" + content: + application/json: + schema: + $ref: "#/components/schemas/SubscriptionInfo" + 404: + description: "Specified Subscription Not found" + content: {} + 500: + description: "Internal Server Error" + +``` + +``` + +content: {} + +delete: + tags: + - NotificationService + summary: "Unsubscribe Notification" + description: "delete a specific Notification Subscription" + operationId: "unsubscribeNotification" + responses: + 200: + description: "The specified Subscription is deleted successfully" + content: {} + 404: + description: "Specified Subscription does not exist" + content: {} + 405: + description: "Method Not Allowed, the specified Subscription cannot be +deleted" + content: {} + 500: + description: "Internal Server Error" + content: {} + +patch: + tags: + - NotificationService + summary: "Modify Subscription" + description: "modify a specific Notification Subscription" + operationId: "modifySubscription" + requestBody: + description: "The input parameters of the modifySubscription operation" + content: + application/json: + schema: + $ref: '#/components/schemas/ModifySubscriptionRequest' + required: true + responses: + 200: + description: "The specified Subscription is modified successfully, and +the modified Subscription information is returned" + content: + application/json: + schema: + $ref: '#/components/schemas/SubscriptionInfo' + 400: + description: "Parameter Error occurred in the modifySubscription +operation" + content: + application/json: + schema: + $ref: '#/components/schemas/ErrorInfo' + 404: + description: "Specified Subscription does not exist" + content: {} + 405: + description: "Method Not Allowed, the specified Subscription cannot be +modified" + content: {} + 500: + description: "Internal Server Error" + +``` + +``` + +content: {} + +/Subscription={subscriptionId}/suspend: +parameters: +- name: subscriptionId + in: path + description: "The unique Identifier of the notification Subscription" + required: true + schema: + type: string + +post: +tags: +- NotificationService +summary: "Suspend Subscription " +description: "Suspend the specific Notification Subscription" +operationId: "suspendSubscription" +responses: +200: + description: "The specified Subscription is suspended successfully" + content: {} +404: + description: "Specified Subscription Not found" + content: {} +405: + description: "Method Not Allowed" + content: {} +409: + description: "Subscription already Suspended" + content: {} +500: + description: "Internal Server Error" + content: {} + +/Subscription={subscriptionId}/resume: +parameters: +- name: subscriptionId + in: path + description: "The unique Identifier of the notification Subscription" + required: true + schema: + type: string + +post: +tags: +- NotificationService +summary: "Resume Subscription " +description: "Resume the specific suspended Notification Subscription" +operationId: "resumeSubscription" +responses: +200: + description: "The specified Subscription is resumed successfully" + content: {} +400: + description: "Subscription already Resumed" + content: {} +404: + description: "Specified Subscription Not found" + content: {} +405: + +``` + +``` + + description: "Method Not Allowed" + content: {} + 500: + description: "Internal Server Error" + content: {} + +/NotificationTypes: + get: + tags: + - NotificationService + summary: "Get Notification Types" + description: "get the supported Notification Types." + operationId: "getNotificationTypes" + responses: + 200: + description: "The attribute value list of the specified MO is +retrieved successfully" + content: + application/json: + schema: + type: array + items: + $ref: "#/components/schemas/NotificationType" + 404: + description: "Specified Subscription Not found" + content: {} + 500: + description: "Internal Server Error" + content: {} + +components: + schemas: + + NVPair: + type: object + required: + - name + - value + properties: + name: + type: string + value: + type: string + type: + type: string + + NVPairList: + type: object + properties: + attributeList: + type: array + items: + $ref: '#/components/schemas/NVPair' + + SubscribeNotificationRequest: + type: object + properties: + managerId: + type: string + +``` + +``` + +notificationTypeList: + #empty list means subscribing all notification types. + type: array + items: + $ref: '#/components/schemas/NotificationType' +filteringCriteria: + #optional + type: string +destination: + #URI of the notification subscriber + type: string + format: uri +required: + - managerId + - destination + +NotificationType: + type: string + enum: + - objectCreation + - objectDeletion + - attributeValueChange + - stateChange + - communicationAlarm + - environmentalAlarm + - equipmentAlarm + - processingErrorAlarm + - qualityOfServiceAlarm + - integrityViolation + - operationalViolation + - physicalViolation + - securityViolation + - timeDomainViolation + - relationshipChange + - heartbeat + +subscriptionId: + type: string + +ErrorInfo: + type: object + properties: + code: + type: string + enum: + - invalidObjectInstance + - noSuchObjectClass + - noSuchAttribute + - invalidAttributeValue + - missingAttributeValue + - notFound + - cannotBeDeleted + message: + type: string + required: + - code + +SubscriptionInfo: + type: object + properties: + +``` + +``` + +subscriptionId: + type: string +managerId: + #the identifier of manager of this notification subscription + type: string +notificationTypeList: + #empty list means subscribing all notification types. + type: array + items: + $ref: '#/components/schemas/NotificationType' +filteringCriteria: + #optional + type: string +destination: + #URI of the notification subscriber + type: string + format: uri +subscriptionStatus: + #Whether the subscription is suspended or resumed + type: string + enum: + - suspended + - resumed +required: + - subscriptionId + - managerId + - destination + - subscriptionState + +ModifySubscriptionRequest: + type: object + properties: + notificationTypeList: + #empty list means subscribing all notification types. + type: array + items: + $ref: '#/components/schemas/NotificationType' + filteringCriteria: + #optional + type: string + destination: + #URI of the notification subscriber + type: string + format: uri + +NotificationInfo: + type: object + properties: + notificationHeader: + $ref: '#/components/schemas/NotificationHeader' + notificationBody: + $ref: '#/components/schemas/NotificationBody' + required: + - notificationHeader + - notificationBody + +NotificationHeader: + type: object + properties: + objectClass: + +``` + +``` + +type: string +objectInstance: + type: string + format: uri +notificationId: + type: string +eventTime: + type: string + # to be confirmed. + format: date-time +systemDN: + type: string +notificationType: + $ref: '#/components/schemas/NotificationType' +required: +- objectClass +- objectInstance +- notificationId +- eventTime +- systemDN +- notificationType + +``` + +##### NotificationBody: + +``` + +type: object +#One of the following will be used in a concrete notification +properties: + objectCreationBody: + $ref: '#/components/schemas/ObjectCreationDeletionBody' + objectDeletionBody: + $ref: '#/components/schemas/ObjectCreationDeletionBody' + attributeValueChangeBody: + $ref: '#/components/schemas/AttributeValueChangeBody' + stateChangeBody: + $ref: '#/components/schemas/StateChangeBody' + alarmNotificationBody: + #for communicationsAlarm, environmentalAlarm, equipmentAlarm, +processingErrorAlarm, qualityOfServiceAlarm + $ref: '#/components/schemas/AlarmNotificationBody' + violationsNotificationBody: + $ref: '#/components/schemas/ViolationsNotificationBody' + relationshipChangeNotificationBody: + $ref: '#/components/schemas/RelationshipChangeNotificationBody' + heartbeatNotificationBody: + $ref: '#/components/schemas/HeartbeatNotificationBody' + +``` + +##### ObjectCreationDeletionBody: + +``` + +type: object +properties: + commonAttributes: + $ref: '#/components/schemas/CMNotificationCommonAttrs' + attributeList: + $ref: '#/components/schemas/NVPairList' + +``` + +##### AttributeValueChangeBody: + +``` + +type: object +properties: + commonAttributes: + $ref: '#/components/schemas/CMNotificationCommonAttrs' + attributeChanges: + $ref: '#/components/schemas/NVPairList' + +``` + +``` + +required: + - attributeChanges + +StateChangeBody: + type: object + properties: + commonAttributes: + $ref: '#/components/schemas/CMNotificationCommonAttrs' + stateChanges: + $ref: '#/components/schemas/NVPairList' + required: + - stateChanges + +CMNotificationCommonAttrs: + type: object + properties: + correlatedNotifications: + type: array + items: + type: string + additionalText: + type: string + additionalInfo: + type: string + sourceIndicator: + $ref: '#/components/schemas/SourceIndicator' + +SourceIndicator: + type: string + format: enum + - resourceOperation + - managementOperation + - unknown + +AlarmNotificationBody: + type: object + properties: + correlatedNotifications: + type: array + items: + type: string + additionalText: + type: string + additionalInfo: + type: string + probableCause: + type: string + specificProblems: + type: array + items: + type: string + perceivedSeverity: + $ref: '#/components/schemas/AlarmSeverity' + backedUpStatus: + type: boolean + backUpObject: + type: string + format: uri + trendIndication: + $ref: '#/components/schemas/TrendIndication' + +``` + +``` + +thresholdInfo: + $ref: '#/components/schemas/ThresholdInfo' +stateChangeDefinition: + $ref: '#/components/schemas/StateChangeDefinition' +monitoredAttributes: + type: array + items: + type: string +proposedRepairActions: + type: array + items: + type: string +alarmEffectOnService: + type: boolean +alarmingResumed: + type: boolean +suspectObjectList: + type: array + items: + type: string + format: uri +required: + - probableCause + - perceivedSeverity + +AlarmSeverity: + type: string + format: enum + - cleared + - warning + - indetermined + - minor + - major + - critical + +TrendIndication: + type: string + format: enum + - lessSevere + - noChange + - moreSevere + +ThresholdInfo: + type: object + properties: + attributeID: + type: string + observedValue: + type: number + format: float + thresholdLevel: + $ref: '#/components/schemas/ThresholdLevelInd' + armTime: + type: string + format: date-time + +ThresholdLevelInd: + type: object + properties: + +``` + +``` + +indication: + $ref: '#/components/schemas/ThresholdIndication' +low: + type: number + format: float +high: + type: number + format: float + +ThresholdIndication: + type: string + format: enum + - up + - down + +StateChangeDefinition: + $ref: '#/components/schemas/NVPairList' + +ViolationsNotificationBody: + type: object + properties: + correlatedNotifications: + type: array + items: + type: string + additionalText: + type: string + additionalInfo: + type: string + securityAlarmCause: + type: string + securityAlarmSeverity: + $ref: '#/components/schemas/AlarmSeverity' + securityAlarmDetector: + $ref: '#/components/schemas/SecurityAlarmDetector' + serviceUser: + type: string + serviceProvider: + type: string + required: + - securityAlarmCause + - securityAlarmSeverity + - securityAlarmDetector + - serviceUser + - serviceProvider + +SecurityAlarmDetector: + type: object + properties: + mechanism: + $ref: '#/components/schemas/UID' + obj: + type: string + format: uri + +UID: + type: object + properties: + uri: + +``` + +``` + + type: string + format: uri + value: + type: integer + format: unsignedLong + +RelationshipChangeNotificationBody: + type: object + properties: + commonAttributes: + $ref: '#/components/schemas/CMNotificationCommonAttrs' + relationshipChanges: + $ref: '#/components/schemas/AttributeChangeSet' + required: + - relationshipChanges + +AttributeChangeSet: + type: array + items: + $ref: '#/components/schemas/AttributeChange' + +AttributeChange: + type: object + properties: + attributeName: + type: string + attributeType: + type: string + oldValue: + type: string + newValue: + type: string + +HeartbeatNotificationBody: + type: object + properties: + systemLabel: + type: string + format: uri + period: + type: integer + format: unitsInSeconds + timeStamp: + type: string + format: date-time + +``` + +**Figure A.1 – YAML-schema definitions for REST-based notification service** + +### **A.2 REST-based heartbeat service interface** + +#### **A.2.1 JSON-schema definitions for REST-based heartbeat service** + +The following provides the HTTP requests and responses for REST-based heartbeat service interface. + +- (1) Table A.1 shows the heartbeat operation. + +**Table A.1 – Interface definition of heartbeat operation** + +| Name | Schema | +|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| REQUEST | "POST" { destinationURI } / " notifications " {HTTPVersion} {RequestBody} | +| RequestBody | HeartbeatMessageType : : = {
AllOf: [
{ NotificationBaseType },
{
systemLabel: string
period: string
timeStamp: string
}]
} | +| RESPONSE | {HTTPVersion} {StatusCode} {ReasonPhrase}
Location: { destinationURI } / " notifications " / { notificationId } {ResponseBody} | +| ResponseBody | HeartbeatMessageType | + +(2) Table A.2 shows the getHeartbeatAttributes operation. + +**Table A.2 – Interface definition of getHeartbeatAttributes operation** + +| Name | Schema | +|--------------|----------------------------------------------------------------------------------------------------------------------------| +| REQUEST | "GET" heartbeatServiceURI / " heartbeats / "subscriptionId
[ "?attributes=" ("systemLabel" "period") ]
HTTPVersion | +| RESPONSE | {HTTPVersion} {StatusCode} {ReasonPhrase}
{ResponseBody} | +| ResponseBody | HeartBeatAttributes : : = {
systemLabel: string
period: string'
} | + +(3) Table A.3 shows the setHeartbeatAttributes operation. + +**Table A.3 – Interface definition of setHeartbeatAttribute operation** + +| Name | Schema | +|-------------|-------------------------------------------------------------------------------------------------| +| REQUEST | "PATCH" { heartbeatServiceURI } / " heartbeats " / {subscriptionId} {HTTPVersion} {RequestBody} | +| RequestBody | HeartbeatAttributes : : = {
systemLabel: string
period: string
} | +| RESPONSE | {HTTPVersion} {StatusCode} {ReasonPhrase} | + +#### A.2.2 YAML-schema definitions for REST-based heartbeat service + +Table A.4 provides the YAML-schema definitions for the REST-based heartbeat service interface. + +**Table A.4 – YAML-schema definitions for REST-based heartbeat service** + +``` +openapi: 3.0.0 +info: + title: ITU-T_HeartbeatService + description: 'This is the formal definition of the ITU-T Heartbeat Service.' + termsOfService: https://www.itu.int/en/ITU-T/about/Pages/default.aspx + contact: + email: zlwang@bupt.edu.cn + license: + name: Apache 2.0 + url: http://www.apache.org/licenses/LICENSE-2.0.html + version: 1.0.0 +externalDocs: + description: See Recommendation ITU-T Q.819 + url: https://www.itu.int/itu-t/recommendations/index.aspx?ser=X +servers: +- url: https://www.itu.int/sg2/rest/HeartbeatService/v1.0.0 +- url: http://www.itu.int/sg2/rest/HeartbeatService/v1.0.0 +tags: +- name: HeartbeatService + description: All APIs related to the ITU-T Heartbeat Service + externalDocs: + description: Find out more + url: https://www.itu.int/itu-t/recommendations/index.aspx?ser=X +paths: +/HeartbeatService/{subscriptionId}: + parameters: + - name: subscriptionId + in: path + description: "The unique Identifier of the notification Subscription" + required: true + schema: + type: string + + get: + tags: + - HeartbeatService + summary: "Get Heartbeat Service Information" + description: "get the list of Identifiers of all the existing +Notification Subscriptions" + operationId: "getHeartbeatAttributes" + responses: + 200: + description: "The attribute value list of the specified MO is +retrieved successfully" + content: + application/json: + schema: + $ref: "#/components/schemas/HeartbeatInfo" + 404: + description: "Specified Subscription Not found" + content: {} + 500: + description: "Internal Server Error" + content: {} + + patch: + tags: +``` + +``` + +- HeartbeatService +summary: "Modify Heartbeat service attributes" +description: "modify the attribute of a heartbeat service attributes." +operationId: "modifyHeartbeatService" +requestBody: + description: "The input parameters of the modifySubscription +operation" + content: + application/json: + schema: + $ref: '#/components/schemas/ModifyHeartbeatServiceRequest' + required: true +responses: + 200: + description: "The specified Subscription is modified successfully, +and the modified Subscription information is returned" + content: + application/json: + schema: + $ref: '#/components/schemas/SubscriptionInfo' + 400: + description: "Parameter Error occurred in the modifyHeartbeatService +operation" + content: + application/json: + schema: + $ref: '#/components/schemas/ErrorInfo' + 404: + description: "Specified Subscription does not exist" + content: {} + 405: + description: "Method Not Allowed, the specified Subscription cannot +be modified" + content: {} + 500: + description: "Internal Server Error" + content: {} + +components: + schemas: + NotificationType: + type: string + enum: + - objectCreation + - objectDeletion + - attributeValueChange + - stateChange + - communicationAlarm + - environmentalAlarm + - equipmentAlarm + - processingErrorAlarm + - qualityOfServiceAlarm + - integrityViolation + - operationalViolation + - physicalViolation + - securityViolation + - timeDomainViolation + - relationshipChange + - heartbeat + +``` + +``` + +ErrorInfo: + type: object + properties: + code: + type: string + enum: + - invalidObjectInstance + - noSuchObjectClass + - noSuchAttribute + - invalidAttributeValue + - missingAttributeValue + - notFound + - cannotBeDeleted + message: + type: string + required: + - code + +SubscriptionInfo: + type: object + properties: + subscriptionId: + type: string + managerId: + #the identifier of manager of this notification subscription + type: string + notificationTypeList: + #empty list means subscribing all notification types. + type: array + items: + $ref: '#/components/schemas/NotificationType' + filteringCriteria: + #optional + type: string + destination: + #URI of the notification subscriber + type: string + format: uri + subscriptionStatus: + #Whether the subscription is suspended or resumed + type: string + enum: + - suspended + - resumed + required: + - subscriptionId + - managerId + - destination + - subscriptionState + +HeartbeatInfo: + type: object + properties: + systemLabel: + type: string + format: uri + period: + type: integer + format: unitsInSeconds + required: + +``` + +``` + +- systemLabel +- period + +ModifyHeartbeatServiceRequest: + type: object + properties: + systemLabel: + type: string + format: uri + period: + type: integer + format: unitsInSeconds + +HeartbeatNotificationBody: + type: object + properties: + systemLabel: + type: string + format: uri + period: + type: integer + format: unitsInSeconds + timeStamp: + type: string + format: date-time + +``` + +### A.3 REST-based containment service interface + +#### A.3.1 JSON-schema definitions for REST-based containment service + +The JSON schema definitions for the REST-base containment service interface include the following information, as show in Tables A.5, A.6 and A.7: + +- (1) Table A.5 shows the exists operation. + +**Table A.5 – Interface definition of exists operation** + +| Name | Schema | +|--------------|----------------------------------------------------------------------------------------------| +| REQUEST | "GET" {ContainmentServiceURI}
"/ContainmentService/exists/" {moInstance}
{HTTPVersion} | +| RESPONSE | {HTTPVersion} {StatusCode} {ReasonPhrase}
{ResponseBody} | +| ResponseBody | boolean | + +- (2) Table A.6 shows the getContained operation. + +**Table A.6 – Interface definition of getContained operation** + +| Name | Schema | +|--------------|------------------------------------------------------------------------------------------------------------| +| REQUEST | "GET" {ContainmentServiceURI}
"/ContainmentService/getContained/"
{moInstance}/{scope} {HTTPVersion} | +| actionName | "getContained" | +| RESPONSE | {HTTPVersion} {StatusCode} {ReasonPhrase}
{ResponseBody} | +| ResponseBody | list of string | + +(3) Table A.7 shows the getContainedByClass operation. + +**Table A.7 – Interface definition of getContainedByClass operation** + +| Name | Schema | +|--------------|---------------------------------------------------------------------------------------------------------------------------| +| REQUEST | "GET" {ContainmentServiceURI}
"/ContainmentService/getContainedByClass/"
{moInstance}/{scope}/{class} {HTTPVersion} | +| actionName | "getContainedByClass" | +| RESPONSE | {HTTPVersion} {StatusCode} {ReasonPhrase}
{ResponseBody} | +| ResponseBody | list of string | + +#### A.3.2 YAML-schema definitions for REST-based containment service + +Table A.8 provides the YAML-schema definitions for REST-based containment service interface. + +**Table A.8 – YAML-schema definitions for REST-based containment service** + +``` + +openapi: 3.0.0 +info: + title: ITU-T_ContainmentService + description: 'This is the formal definition of the ITU-T Containment Service.' + termsOfService: https://www.itu.int/en/ITU-T/about/Pages/default.aspx + contact: + email: zlwang@bupt.edu.cn + license: + name: Apache 2.0 + url: http://www.apache.org/licenses/LICENSE-2.0.html + version: 1.0.0 +externalDocs: + description: See Recommendation ITU-T Q.819 + url: https://www.itu.int/itu-t/recommendations/index.aspx?ser=X +servers: +- url: http://www.itu.int/sg2/rest/ContainmentService/v1.0.0 +- url: https://www.itu.int/sg2/rest/ContainmentService/v1.0.0 +tags: +- name: ContainmentService + description: All APIs related to the ITU-T Containment Service + externalDocs: + description: Find out more + url: https://www.itu.int/itu-t/recommendations/index.aspx?ser=X + +``` + +``` + +paths: + /ContainmentService/exists/{moInstance}: + parameters: + - name: moInstance + in: path + description: "The DN(URI) of the specified MO" + required: true + schema: + type: string + format: uri + + get: + tags: + - ContainmentService + summary: "check whether the specified MO instance is registered in the containment service or not." + description: "returns true if the specified MO instance exists in the containment service, otherwise it returns false" + operationId: "exists" + responses: + 200: + description: "The specified MO is found in the containment services." + content: {} + 404: + description: "The specified MO is not found in the containment services." + content: {} + 500: + description: "Internal Server Error" + content: {} + + /ContainmentService/getContained/{baseMO}/{scope}: + parameters: + - name: baseMO + in: path + description: "The DN of the specified base MO which is the root of a subtree" + required: true + schema: + type: string + format: uri + - name: scope + in: path + description: "The scope of the containment information to be returned associated with the root MO" + required: true + schema: + $ref: '#/components/schemas/ScopeType' + + get: + tags: + - ContainmentService + summary: "returns the MO instance list which are contained by the specified base MO instance." + description: "returns the list of MO instance that are contained by the base MO instance. the scope parameter can be of 4 possible values: BaseObjectOnly, WholeSubTree, IndividualLevel, IndividualLevel" + operationId: "getContained" + +``` + +``` + +responses: + 200: + description: "The operation is executed successfully, and the list +of contained MO instances are returned" + content: + application/json: + schema: + $ref: '#/components/schemas/MOList' + 404: + description: "The specified MO is not found in the containment +services." + content: {} + 500: + description: "Internal Server Error" + content: {} + +/ContainmentService/getContainedByClass/{baseMO}/{scope}/{class}: + parameters: + - name: baseMO + in: path + description: "The DN of the specified base MO which is the root of a +subtree" + required: true + schema: + type: string + format: uri + - name: scope + in: path + description: "The scope of the containment information to be returned +associated with the root MO" + required: true + schema: + $ref: '#/components/schemas/ScopeType' + - name: class + in: path + description: "The class of the contained information to be returned +associated with the root MO" + required: true + schema: + type: string + + get: + tags: + - ContainmentService + summary: "returns the MO instance list which are contained by the +specified base MO instance." + description: "returns the list of MO instance that are contained by the +base MO instance. the scope parameter can be of 4 possible values: +BaseObjectOnly, WholeSubTree, IndividualLevel, IndividualLevel, and the +returned MO list is filtered by the class specified in the input parameter" + operationId: "getContainedByClass" + responses: + 200: + description: "The operation is executed successfully, and the list +of contained MO instances are returned" + content: + application/json: + schema: + $ref: '#/components/schemas/MOList' + 404: + +``` + +``` + description: "The specified MO is not found in the containment +services." + content: {} +500: + description: "Internal Server Error" + content: {} + +components: + schemas: + + ScopeEnumType: + type: string + format: enum + - BasicObjectOnly + - WholeSubtree + - IndividualLevel + - BaseToLevel + + ScopeType: + type: object + properties: + scopeInd: + $ref: '#/components/schemas/ScopeEnumType' + level: + type: integer + + MOList: + type: array + items: + type: string + format: uri +``` + +# Bibliography + +- [b-ITU-T Q.818] Recommendation ITU-T Q.818 (2012), *Web service-based management services*. +- [b-OAI-OAS3] OpenAPI Initiative (2017), *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/Q/T-REC-Q.823.1-199710-I_PDF-E/raw.md b/marked/Q/T-REC-Q.823.1-199710-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e1e0d23a3ea5ead402e10e2be7abd18d5006955d --- /dev/null +++ b/marked/Q/T-REC-Q.823.1-199710-I_PDF-E/raw.md @@ -0,0 +1,9363 @@ + + +![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 + +**Q.823.1** + +(10/97) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of Signalling System No. 7 – Q3 interface + +--- + +# **Management Conformance Statement Proformas** + +ITU-T Recommendation Q.823.1 + +(Previously CCITT Recommendation) + +--- + +## ITU-T Q-SERIES RECOMMENDATIONS + +## **SWITCHING AND SIGNALLING** + +| | | +|------------------------------------------------------------|--------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 | +| General | Q.700 | +| Message transfer part (MTP) | Q.701–Q.709 | +| Signalling connection control part (SCCP) | Q.711–Q.719 | +| Telephone user part (TUP) | Q.720–Q.729 | +| ISDN supplementary services | Q.730–Q.739 | +| Data user part | Q.740–Q.749 | +| Signalling System No. 7 management | Q.750–Q.759 | +| ISDN user part | Q.760–Q.769 | +| Transaction capabilities application part | Q.770–Q.779 | +| Test specification | Q.780–Q.799 | +| Q3 interface | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| General | Q.850–Q.919 | +| Data link layer | Q.920–Q.929 | +| Network layer | Q.930–Q.939 | +| User-network management | Q.940–Q.949 | +| Stage 3 description for supplementary services using DSS 1 | Q.950–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1999 | +| BROADBAND ISDN | Q.2000–Q.2999 | + +For further details, please refer to ITU-T List of Recommendations. + +## **ITU-T RECOMMENDATION Q.823.1** + +# **MANAGEMENT CONFORMANCE STATEMENT PROFORMAS** + +## **Source** + +ITU-T Recommendation Q.823.1 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 | Introduction ..... | 1 | +| 1.1 | Purpose and structure ..... | 1 | +| 1.2 | Instructions for completing the MCS proforma to produce an MCS ..... | 1 | +| 2 | Identification of the implementation ..... | 1 | +| 2.1 | Date of statement..... | 1 | +| 2.2 | Identification of the implementation ..... | 1 | +| 2.3 | Contact ..... | 1 | +| 3 | Identification of the document in which the management information is defined..... | 2 | +| 3.1 | Technical corrigenda implemented ..... | 2 | +| 3.2 | Amendments implemented..... | 2 | +| 4 | Management conformance summary..... | 2 | +| 5 | MOCS proformas ..... | 3 | +| 5.1 | Introduction ..... | 3 | +| 5.2 | Instructions for completing the MOCS proforma to produce a MOCS ..... | 3 | +| 5.3 | Statement of conformance to the managed object class..... | 3 | +| 6 | acc ["Q.823"]..... | 4 | +| 7 | accAffectedTraffic ["Q.823"]..... | 11 | +| 8 | accTrigger ["Q.823"]..... | 17 | +| 9 | adc ["Q.823"]..... | 20 | +| 10 | adcTrigger ["Q.823"]..... | 28 | +| 11 | cancelFrom ["Q.823"] ..... | 36 | +| 12 | cancelRerouted ["Q.823"] ..... | 42 | +| 13 | cancelTo ["Q.823"]..... | 48 | +| 14 | circuitEndPointSubgroupCurrentData ["Q.823"]..... | 54 | +| 15 | circuitEndPointSubgroupHistoryData ["Q.823"]..... | 70 | +| 16 | congestionLevelIndication ["Q.823"]..... | 76 | +| 17 | destinationCodeControl ["Q.823"] ..... | 79 | +| 18 | dccGroup ["Q.823"] ..... | 87 | +| 19 | exchangeCurrentData ["Q.823"] ..... | 93 | +| 20 | exchangeHistoryData ["Q.823"]..... | 109 | + +| | | Page | +|----|-----------------------------------------------------|-------------| +| 21 | htrDestination ["Q.823"] ..... | 114 | +| 22 | observedDestination ["Q.823"] ..... | 121 | +| 23 | observedDestinationCurrentData ["Q.823"]..... | 127 | +| 24 | observedDestinationHistoryData ["Q.823"]..... | 143 | +| 25 | scr ["Q.823"] ..... | 148 | +| 26 | scrAffectedTraffic ["Q.823"]..... | 156 | +| 27 | skip ["Q.823"] ..... | 162 | +| 28 | stateIndicator ["Q.823"] ..... | 168 | +| 29 | tarFrom ["Q.823"] ..... | 177 | +| 30 | tarTo ["Q.823"] ..... | 183 | +| 31 | tmCircuitEndPointSubgroup ["Q.823"] ..... | 190 | +| 32 | tmCircuitEndPointSubgroupCurrentData ["Q.823"]..... | 196 | +| 33 | tmExchangeCurrentData ["Q.823"] ..... | 212 | +| 34 | tmObservedDestinationCurrentData ["Q.823"] ..... | 228 | +| 35 | tmTrafficControlCurrentData ["Q.823"]..... | 244 | +| 36 | trafficControl ["Q.823"] ..... | 260 | +| 37 | trafficControlCurrentData ["Q.823"] ..... | 266 | +| 38 | trafficControlHistoryData ["Q.823"]..... | 281 | + +## Recommendation Q.823.1 + +# MANAGEMENT CONFORMANCE STATEMENT PROFORMAS + +*(Geneva, 1997)* + +## 1 Introduction + +### 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. + +### 1.2 Instructions for completing the MCS proforma to produce an MCS + +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. + +## 2 Identification of the implementation + +### 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 | +|-------------------| + +### 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. + +| | +|--| +| | +|--| + +### 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. + +| | +|--| +| | +|--| + +## **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 | +|------------------------------------------| + +### **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. + +| | +|--| +| | +|--| + +### **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. + +| | +|--| +| | +|--| + +## **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 Rec. X.291 | ISO/IEC 9646-2 and ITU-T Rec. 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 Rec. X.291 | ISO/IEC 9646-2 and ITU-T Rec. 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. + +## **5 MOCS proformas** + +### **5.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. + +### **5.2 Instructions for completing the MOCS proforma to produce a MOCS** + +The supplier of the implementation shall state which items are supported in the tables below and if necessary provide additional information. + +### **5.3 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. + +Tables are numbered consistently for all classes, that is Table A.x.1 for Managed object class support, A.x.3 for Package support, etc. To preserve this numbering scheme, table numbers are allocated, even if a particular class does not have any of the corresponding properties. + +## 6 acc ["Q.823"] + +**Table 6.1/Q.823.1 – acc 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 | acc | {0 0 17 823 0 3 1} | | | + +**Table 6.2/Q.823.1 – acc 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 6.3/Q.823.1 – acc Packages support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|---------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | accPackage | | Mandatory | m | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 3 | creatorPackage | {0 0 17 823 0 4 14} | "an instance supports it" | o | | | +| 4 | "Rec. M.3100 : 1992":
objectManagementNotificationsPackage | {0 0 13 3100 0 4 20} | Mandatory | m | | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c1 | | | +| 6 | "Rec. M.3100 : 1992":
stateChangeNotificationPackage | {0 0 13 3100 0 4 28} | Mandatory | m | | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
topPackage | | Mandatory | m | | | +| 8 | trafficControlPackage | | Mandatory | m | | | + +**Table 6.4/Q.823.1 – acc Attributes 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": administrativeState | {2 9 3 2 7 31} | ENUMERATED | m | | m | | m | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 3 | assocAccAffectedTraffic | {0 0 17 823 0 6 66} | CHOICE | m | | m | | m | | +| 4 | autoActivated | {0 0 17 823 0 6 13} | BOOLEAN | m? | | m | | – | | +| 5 | controlTmCircuitEndPointSubgroup | {0 0 17 823 0 6 58} | CHOICE | m? | | m | | – | | +| 6 | creatorIdentity | {0 0 17 823 0 6 24} | CHOICE | o? | | o | | – | | +| 7 | dispositionOfCalls | {0 0 17 823 0 6 29} | CHOICE | m | | m | | m | | +| 8 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 10 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | cl | | – | | +| 11 | tmSurveillance | {0 0 17 823 0 6 60} | BOOLEAN | m | | m | | m | | +| 12 | trafficControlId | {0 0 17 823 0 6 61} | CHOICE | m? | | m | | – | | + +**Table 6.4/Q.823.1 – acc Attributes 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 | – | | – | | – | | | + +**Table 6.5/Q.823.1 – acc Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 6.6/Q.823.1 – acc Action support** + +There are no actions specified for this managed object class. + +**Table 6.7/Q.823.1 – acc 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | m | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | m | | | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stateChange | {2 9 3 2 10 14} | | m | | | | + +**Table 6.7/Q.823.1 – acc Notification support (continued)** + +| 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 | | | + +**Table 6.7/Q.823.1 – acc Notification support (continued)** + +| 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | | | + +**Table 6.7/Q.823.1 – acc Notification support (continued)** + +| 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.4.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.5 | | | +| | 2.1.4.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 3.1.4.2.2 | nonSpecificForm | – | OCTET STRING | c:o.7 | | | + +**Table 6.7/Q.823.1 – acc Notification support (continued)** + +| 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.4.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.7 | | | +| | 3.1.4.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | 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 | | | +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | +| 4 | 4.1 | StateChangeInfo | | Information Syntax
SEQUENCE | m | | | +| | 4.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | o | | | +| | 4.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | o | | | +| | 4.1.2.1 | globalForm | – | OBJECT IDENTIFIER | c:o.8 | | | +| | 4.1.2.2 | localForm | – | INTEGER | c:o.8 | | | +| | 4.1.3 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | m | | | +| | 4.1.3.1 | attributeID | – | CHOICE | m | | | +| | 4.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | o.9 | | | +| | 4.1.3.1.2 | localForm | – | INTEGER | o.9 | | | +| | 4.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | o | | | +| | 4.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | m | | | +| | 4.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | o | | | +| | 4.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | o | | | +| | 4.1.5.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 4.1.5.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 4.1.5.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.5.2.2 | nonSpecificForm | – | OCTET STRING | c:o.10 | | | + +**Table 6.7/Q.823.1 – acc 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.5.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | o | | | +| | 4.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | o | | | +| | 4.1.7.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.7.2 | significance | – | BOOLEAN | c:o | | | +| | 4.1.7.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 6.8/Q.823.1 – acc Parameter support** + +There are no parameters specified for this managed object class. + +**Table 6.9/Q.823.1 – acc Conditions** + +| Condition number | Condition | Reference | +|------------------|------------------------|-------------------------------------------------------------------------| +| c1 | IF 1.3/5 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table 6.10/Q.823.1 – acc Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------|---------------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | trafficControl-managedElement | {0 0 17 823 0 5 20} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | + +**Table 6.10/Q.823.1 – acc 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 | | | + +## 7 accAffectedTraffic ["Q.823"] + +**Table 7.1/Q.823.1 – accAffectedTraffic 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 | accAffectedTraffic | {0 0 17 823 0 3 2} | | | + +**Table 7.2/Q.823.1 – accAffectedTraffic 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 7.3/Q.823.1 – accAffectedTraffic Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | accAffectedTrafficPackage | | Mandatory | m | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 3 | "Rec. M.3100 : 1992": objectManagementNotificationsPackage | {0 0 13 3100 0 4 20} | Mandatory | m | | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c1 | | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | + +**Table 7.4/Q.823.1 – accAffectedTraffic 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 | accAffectedTrafficId | {0 0 17 823 0 6 1} | CHOICE | m? | | m | | – | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 3 | cl1ResponseCategories | {0 0 17 823 0 6 19} | SET OF SEQUENCE | m | | m | | m | | +| 4 | cl2ResponseCategories | {0 0 17 823 0 6 20} | SET OF SEQUENCE | m | | m | | m | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | cl | | – | | + +**Table 7.4/Q.823.1 – accAffectedTraffic Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | – | | | +| 5 | – | | – | | – | | | +| 6 | – | | – | | – | | | +| 7 | – | | – | | – | | | + +**Table 7.5/Q.823.1 – accAffectedTraffic Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 7.6/Q.823.1 – accAffectedTraffic Action support** + +There are no actions specified for this managed object class. + +**Table 7.7/Q.823.1 – accAffectedTraffic 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | m | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | m | | | | + +**Table 7.7/Q.823.1 – accAffectedTraffic Notification support (continued)** + +| 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | + +**Table 7.7/Q.823.1 – accAffectedTraffic Notification support (continued)** + +| 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.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | | | + +**Table 7.7/Q.823.1 – accAffectedTraffic Notification support (continued)** + +| 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.4.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | 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 | | | + +**Table 7.7/Q.823.1 – accAffectedTraffic 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.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 7.8/Q.823.1 – accAffectedTraffic Parameter support** + +There are no parameters specified for this managed object class. + +**Table 7.9/Q.823.1 – accAffectedTraffic Conditions** + +| Condition number | Condition | Reference | +|------------------|------------------------|-------------------------------------------------------------------------| +| c1 | IF 2.3/4 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table 7.10/Q.823.1 – accAffectedTraffic Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-----------------------------------|---------------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | accAffectedTraffic-managedElement | {0 0 17 823 0 5 1} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | + +**Table 7.10/Q.823.1 – accAffectedTraffic 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:m | | | +| | 1.6 | Delete contained objects | | c:x | | | + +## 8 accTrigger ["Q.823"] + +**Table 8.1/Q.823.1 – accTrigger 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 | accTrigger | {0 0 17 823 0 3 3} | | | + +**Table 8.2/Q.823.1 – accTrigger 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 8.3/Q.823.1 – accTrigger Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|-----------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | accTriggerPackage | | Mandatory | m | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c1 | | | +| 4 | "Rec. M.3100 : 1992": stateChangeNotificationPackage | {0 0 13 3100 0 4 28} | Mandatory | m | | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | + +**Table 8.4/Q.823.1 – accTrigger 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 | accTriggerId | {0 0 17 823 0 6 4} | CHOICE | m? | | m | | – | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": administrativeState | {2 9 3 2 7 31} | ENUMERATED | m | | m | | m | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | + +**Table 8.4/Q.823.1 – accTrigger 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 | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c1 | | – | | + +**Table 8.4/Q.823.1 – accTrigger Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | – | | | +| 5 | – | | – | | – | | | +| 6 | – | | – | | – | | | + +**Table 8.5/Q.823.1 – accTrigger Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 8.6/Q.823.1 – accTrigger Action support** + +There are no actions specified for this managed object class. + +**Table 8.7/Q.823.1 – accTrigger 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stateChange | {2 9 3 2 10 14} | | m | | | | + +**Table 8.7/Q.823.1 – accTrigger 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 | StateChangeInfo | | 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 28} | 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 | stateChangeDefinition | {2 9 3 2 7 28} | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | | | + +**Table 8.8/Q.823.1 – accTrigger Parameter support** + +There are no parameters specified for this managed object class. + +**Table 8.9/Q.823.1 – accTrigger Conditions** + +| Condition number | Condition | Reference | +|------------------|------------------------|-------------------------------------------------------------------------| +| c1 | IF 3 3/3 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table 8.10/Q.823.1 – accTrigger Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-----------------------------|---------------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | accTrigger-managedElement | {0 0 17 823 0 5 2} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | + +**Table 8.10/Q.823.1 – accTrigger 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 | | – | | | +| | 1.5 | Delete only if no contained objects | | – | | | +| | 1.6 | Delete contained objects | | – | | | + +## 9 adc ["Q.823"] + +**Table 9.1/Q.823.1 – adc 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 | adc | {0 0 17 823 0 3 4} | | | + +**Table 9.2/Q.823.1 – adc 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 9.3/Q.823.1 – adc Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------|----------------------------------------|----------------------------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | adcAsynchronousTimerPackage | {0 0 17 823 0 4 1} | "adcPercentagePackage and adcContinuousTimerPackage and adcLeakyBucketPackage are not present, and NE supports it." | c1 | | | +| 2 | adcContinuousTimerPackage | {0 0 17 823 0 4 2} | "adcPercentagePackage and adcAsynchronousTimerPackage and adcLeakyBucketPackage are not present, and NE supports it." | c2 | | | +| 3 | adcLeakyBucketPackage | {0 0 17 823 0 4 3} | "adcPercentagePackage and adcContinuousTimerPackage and adcAsynchronousTimerPackage are not present, and NE supports it." | c3 | | | +| 4 | adcPackage | | Mandatory | m | | | +| 5 | adcPercentagePackage | {0 0 17 823 0 4 4} | "adcContinuousTimerPackage and adcAsynchronousTimerPackage and adcLeakyBucketPackage are not present, and NE supports it." | c4 | | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 7 | creatorPackage | {0 0 17 823 0 4 14} | "an instance supports it" | o | | | +| 8 | destinationTypePackage | {0 0 17 823 0 4 16} | "destination type is required to unambiguously identify the destinationCode" | c5 | | | +| 9 | "Rec. M.3100 : 1992": objectManagementNotificationsPackage | {0 0 13 3100 0 4 20} | Mandatory | m | | | +| 10 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c6 | | | +| 11 | "Rec. M.3100 : 1992": stateChangeNotificationPackage | {0 0 13 3100 0 4 28} | Mandatory | m | | | +| 12 | "Rec. X.721 ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | +| 13 | trafficControlPackage | | Mandatory | m | | | + +**Table 9.4/Q.823.1 – adc 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 | adcType | {0 0 17 823 0 6 7} | ENUMERATED | m? | | m | | – | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": administrativeState | {2 9 3 2 7 31} | ENUMERATED | m | | m | | m | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 4 | asynchronousTimer | {0 0 17 823 0 6 12} | CHOICE | c1? | | c1 | | – | | +| 5 | autoActivated | {0 0 17 823 0 6 13} | BOOLEAN | m? | | m | | – | | +| 6 | continuousTimer | {0 0 17 823 0 6 23} | SEQUENCE | c2? | | c2 | | – | | +| 7 | creatorIdentity | {0 0 17 823 0 6 24} | CHOICE | o? | | o | | – | | +| 8 | destinationCode | {0 0 17 823 0 6 27} | GraphicString | m? | | m | | – | | +| 9 | destinationType | {0 0 17 823 0 6 28} | CHOICE | c5? | | c5 | | – | | +| 10 | leakyBucket | {0 0 17 823 0 6 35} | SEQUENCE | c3? | | c3 | | – | | +| 11 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 12 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 13 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c6 | | – | | +| 14 | percentage | {0 0 17 823 0 6 49} | CHOICE | c4? | | c4 | | – | | +| 15 | timeExpiration | {0 0 17 823 0 6 57} | CHOICE | m? | | m | | – | | +| 16 | tmSurveillance | {0 0 17 823 0 6 60} | BOOLEAN | m | | m | | m | | +| 17 | trafficControlId | {0 0 17 823 0 6 61} | CHOICE | m? | | m | | – | | +| 18 | treatment | {0 0 17 823 0 6 64} | CHOICE | m? | | m | | – | | + +**Table 9.4/Q.823.1 – adc Attribute support (continued)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | – | | | +| 5 | – | | – | | – | | | +| 6 | – | | – | | – | | | +| 7 | – | | – | | – | | | +| 8 | – | | – | | – | | | + +**Table 9.4/Q.823.1 – adc 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 | – | | – | | – | | | + +**Table 9.5/Q.823.1 – adc Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 9.6/Q.823.1 – adc Action support** + +There are no actions specified for this managed object class. + +**Table 9.7/Q.823.1 – adc 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | m | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | m | | | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stateChange | {2 9 3 2 10 14} | | m | | | | + +**Table 9.7/Q.823.1 – adc Notification support (continued)** + +| 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | | | + +**Table 9.7/Q.823.1 – adc Notification support (continued)** + +| Index | Subindex | Notification field name label | Value of object identifier of attribute type associated with field | Constraints and values | Status | Support | Additional information | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|---------------------------------------|--------|---------|------------------------| +| 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 | attributeType | – | OBJECT
IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT
IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 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 | | | + +**Table 9.7/Q.823.1 – adc Notification support (continued)** + +| 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | 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 | | | +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | +| 4 | 4.1 | StateChangeInfo | | Information Syntax
SEQUENCE | m | | | +| | 4.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | o | | | +| | 4.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | o | | | +| | 4.1.2.1 | globalForm | – | OBJECT IDENTIFIER | c:o.8 | | | +| | 4.1.2.2 | localForm | – | INTEGER | c:o.8 | | | +| | 4.1.3 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | m | | | +| | 4.1.3.1 | attributeID | – | CHOICE | m | | | +| | 4.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | o.9 | | | +| | 4.1.3.1.2 | localForm | – | INTEGER | o.9 | | | + +**Table 9.7/Q.823.1 – adc 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.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | o | | | +| | 4.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | m | | | +| | 4.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | o | | | +| | 4.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | o | | | +| | 4.1.5.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 4.1.5.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 4.1.5.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.5.2.2 | nonSpecificForm | – | OCTET STRING | c:o.10 | | | +| | 4.1.5.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | o | | | +| | 4.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | o | | | +| | 4.1.7.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.7.2 | significance | – | BOOLEAN | c:o | | | +| | 4.1.7.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 9.8/Q.823.1 – adc Parameter support** + +There are no parameters specified for this managed object class. + +**Table 9.9/Q.823.1 – adc Conditions** + +| Condition number | Condition | Reference | +|------------------|-------------------------|----------------------------------------------------------------------------------------------------------------------------| +| c1 | IF 4.3/1 THEN m ELSE – | "adcPercentagePackage and adcContinuousTimerPackage and adcLeakyBucketPackage are not present, and NE supports it." | +| c2 | IF 4.3/2 THEN m ELSE – | "adcPercentagePackage and adcAsynchronousTimerPackage and adcLeakyBucketPackage are not present, and NE supports it." | +| c3 | IF 4.3/3 THEN m ELSE – | "adcPercentagePackage and adcContinuousTimerPackage and adcAsynchronousTimerPackage are not present, and NE supports it." | +| c4 | IF 4.3/5 THEN m ELSE – | "adcContinuousTimerPackage and adcaSynchronousTimerPackage and adcLeakyBucketPackage are not present, and NE supports it." | +| c5 | IF 4.3/8 THEN m ELSE – | "destination type is required to unambiguously identify the destinationCode" | +| c6 | IF 4.3/10 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table 9.10/Q.823.1 – adc Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------|---------------------------------------------|----------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | trafficControl-managedElement | {0 0 17 823 0 5 20} | Superior class:
"Recommendation M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | + +**Table 9.10/Q.823.1 – adc 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 | | | + +## 10 adcTrigger ["Q.823"] + +**Table 10.1/Q.823.1 – adcTrigger 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 | adcTrigger | {0 0 17 823 0 3 5} | | | + +**Table 10.2/Q.823.1 – adcTrigger 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 10.3/Q.823.1 – adcTrigger Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | adcTriggerPackage | | Mandatory | m | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 3 | asynchronousTimerPackage | {0 0 17 823 0 4 8} | "percentagePackage and continuousTimerPackage and leakyBucketPackage are not present, and NE supports it." | c1 | | | +| 4 | continuousTimerPackage | {0 0 17 823 0 4 13} | "percentagePackage and asynchronousTimerPackage and leakyBucketPackage are not present, and NE supports it." | c2 | | | +| 5 | destinationCodePackage | {0 0 17 823 0 4 15} | "if the triggering of the adc control is restricted to a predetermined destination." | c3 | | | +| 6 | destinationTypePackage | {0 0 17 823 0 4 16} | "destinationCodePackage is present and destination type is required to unambiguously identify the destinationCode." | c4 | | | +| 7 | leakyBucketPackage | {0 0 17 823 0 4 17} | "percentagePackage and continuousTimerPackage and asynchronousTimerPackage Are not present, and NE supports it." | c5 | | | +| 8 | "Rec. M.3100 : 1992": objectManagementNotificationsPackage | {0 0 13 3100 0 4 20} | Mandatory | m | | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c6 | | | +| 10 | percentagePackage | {0 0 17 823 0 4 19} | "continuousTimerPackage and asynchronousTimerPackage and leakyBucketPackage are not present, and NE supports it." | c7 | | | +| 11 | "Rec. M.3100 : 1992": stateChangeNotificationPackage | {0 0 13 3100 0 4 28} | Mandatory | m | | | +| 12 | "Rec. X.721 ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | +| 13 | triggerThresholdPackage | {0 0 17 823 0 4 23} | "a threshold is to be defined by the manager for adcTrigger to activate" | c8 | | | + +**Table 10.4/Q.823.1 – adcTrigger 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 | adcTriggerId | {0 0 17 823 0 6 5} | CHOICE | m? | | m | | – | | +| 2 | adcTriggerType | {0 0 17 823 0 6 6} | ENUMERATED | m | | m | | m | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": administrativeState | {2 9 3 2 7 31} | ENUMERATED | m | | m | | m | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 5 | asynchronousTimer | {0 0 17 823 0 6 12} | CHOICE | c1 | | c1 | | c1 | | +| 6 | continuousTimer | {0 0 17 823 0 6 23} | SEQUENCE | c2 | | c2 | | c2 | | +| 7 | destinationCode | {0 0 17 823 0 6 27} | GraphicString | c3? | | c3 | | – | | +| 8 | destinationType | {0 0 17 823 0 6 28} | CHOICE | c4? | | c4 | | – | | +| 9 | leakyBucket | {0 0 17 823 0 6 35} | SEQUENCE | c5 | | c5 | | c5 | | +| 10 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 11 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 12 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c6 | | – | | +| 13 | percentage | {0 0 17 823 0 6 49} | CHOICE | c7 | | c7 | | c7 | | +| 14 | timeExpiration | {0 0 17 823 0 6 57} | CHOICE | m | | m | | m | | +| 15 | triggerThreshold | {0 0 17 823 0 6 65} | INTEGER | c8? | | c8 | | – | | + +**Table 10.4/Q.823.1 – adcTrigger Attribute support (continued)** + +| 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 | – | | – | | – | | | + +**Table 10.4/Q.823.1 – adcTrigger Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 12 | – | | – | | – | | | +| 13 | – | | – | | – | | | +| 14 | – | | – | | – | | | +| 15 | – | | – | | – | | | + +**Table 10.5/Q.823.1 – adcTrigger Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 10.6/Q.823.1 – adcTrigger Action support** + +There are no actions specified for this managed object class. + +**Table 10.7/Q.823.1 – adcTrigger 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | m | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | m | | | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stateChange | {2 9 3 2 10 14} | | m | | | | + +**Table 10.7/Q.823.1 – adcTrigger Notification support (continued)** + +| 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 | | | + +**Table 10.7/Q.823.1 – adcTrigger Notification support (continued)** + +| 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | | | + +**Table 10.7/Q.823.1 – adcTrigger Notification support (continued)** + +| 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 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 | | | + +**Table 10.7/Q.823.1 – adcTrigger Notification support (continued)** + +| 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | 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 | | | +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | +| 4 | 4.1 | StateChangeInfo | | Information Syntax SEQUENCE | m | | | +| | 4.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | o | | | +| | 4.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | o | | | +| | 4.1.2.1 | globalForm | – | OBJECT IDENTIFIER | c:o.8 | | | +| | 4.1.2.2 | localForm | – | INTEGER | c:o.8 | | | +| | 4.1.3 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | m | | | +| | 4.1.3.1 | attributeID | – | CHOICE | m | | | +| | 4.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | o.9 | | | +| | 4.1.3.1.2 | localForm | – | INTEGER | o.9 | | | +| | 4.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | o | | | +| | 4.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | m | | | +| | 4.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | o | | | + +**Table 10.7/Q.823.1 – adcTrigger 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.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | o | | | +| | 4.1.5.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 4.1.5.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 4.1.5.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.5.2.2 | nonSpecificForm | – | OCTET STRING | c:o.10 | | | +| | 4.1.5.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | o | | | +| | 4.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | o | | | +| | 4.1.7.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.7.2 | significance | – | BOOLEAN | c:o | | | +| | 4.1.7.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 10.8/Q.823.1 – adcTrigger Parameter support** + +There are no parameters specified for this managed object class. + +**Table 10.9/Q.823.1 – adcTrigger Conditions** + +| Condition number | Condition | Reference | +|------------------|------------------------|---------------------------------------------------------------------------------------------------------------------| +| c1 | IF 5.3/3 THEN m ELSE – | "percentagePackage and continuousTimerPackage and leakyBucketPackage are not present, and NE supports it." | +| c2 | IF 5.3/4 THEN m ELSE – | "percentagePackage and asynchronousTimerPackage and leakyBucketPackage are not present, and NE supports it." | +| c3 | IF 5.3/5 THEN m ELSE – | "if the triggering of the adc control is restricted to a predetermined destination." | +| c4 | IF 5.3/6 THEN m ELSE – | "destinationCodePackage is present and destination type is required to unambiguously identify the destinationCode." | +| c5 | IF 5.3/7 THEN m ELSE – | "percentagePackage and continuousTimerPackage and asynchronousTimerPackage Are not present, and NE supports it." | + +**Table 10.9/Q.823.1 – adcTrigger Conditions (concluded)** + +| Condition number | Condition | Reference | +|------------------|-------------------------|-------------------------------------------------------------------------------------------------------------------| +| c6 | IF 5.3/9 THEN m ELSE – | "any registered package, other than this package has been instantiated" | +| c7 | IF 5.3/10 THEN m ELSE – | "continuousTimerPackage and asynchronousTimerPackage and leakyBucketPackage are not present, and NE supports it." | +| c8 | IF 5.3/13 THEN m ELSE – | "a threshold is to be defined by the manager for adcTrigger to activate" | + +**Table 10.10/Q.823.1 – adcTrigger Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-----------------------------|---------------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | adcTrigger-managedElement | {0 0 17 823 0 5 3} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | + +**Table 10.10/Q.823.1 – adcTrigger 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:m | | | +| | 1.6 | Delete contained objects | | c:x | | | + +## 11 cancelFrom ["Q.823"] + +**Table 11.1/Q.823.1 – cancelFrom 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 | cancelFrom | {0 0 17 823 0 3 6} | | | + +**Table 11.2/Q.823.1 – cancelFrom 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 11.3/Q.823.1 – cancelFrom Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | cancelFromPackage | | Mandatory | m | | | +| 3 | creatorPackage | {0 0 17 823 0 4 14} | "an instance supports it" | o | | | +| 4 | "Rec. M.3100 : 1992": objectManagementNotificationsPackage | {0 0 13 3100 0 4 20} | Mandatory | m | | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | cl | | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | +| 7 | trafficControlPackage | | Mandatory | m | | | + +**Table 11.4/Q.823.1 – cancelFrom 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 2 | controlTmCircuitEndPointSubgroup | {0 0 17 823 0 6 58} | CHOICE | m? | | m | | – | | +| 3 | creatorIdentity | {0 0 17 823 0 6 24} | CHOICE | o? | | o | | – | | +| 4 | destinationAspect | {0 0 17 823 0 6 26} | CHOICE | m | | m | | m | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 7 | originationAspect | {0 0 17 823 0 6 42} | SEQUENCE | m | | m | | m | | +| 8 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | cl | | – | | +| 9 | percentage | {0 0 17 823 0 6 49} | CHOICE | m | | m | | m | | +| 10 | routingAspect | {0 0 17 823 0 6 51} | ENUMERATED | m | | m | | m | | +| 11 | tmSurveillance | {0 0 17 823 0 6 60} | BOOLEAN | m | | m | | m | | +| 12 | trafficControlId | {0 0 17 823 0 6 61} | CHOICE | m? | | m | | – | | +| 13 | treatment | {0 0 17 823 0 6 64} | CHOICE | m | | m | | m | | + +**Table 11.4/Q.823.1 – cancelFrom Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | m | | | +| 5 | – | | – | | – | | | +| 6 | – | | – | | – | | | +| 7 | – | | – | | m | | | +| 8 | – | | – | | – | | | +| 9 | – | | – | | – | | | +| 10 | – | | – | | m | | | +| 11 | – | | – | | – | | | +| 12 | – | | – | | – | | | +| 13 | – | | – | | – | | | + +**Table 11.5/Q.823.1 – cancelFrom Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 11.6/Q.823.1 – cancelFrom Action support** + +There are no actions specified for this managed object class. + +**Table 11.7/Q.823.1 – cancelFrom 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | m | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | m | | | | + +**Table 11.7/Q.823.1 – cancelFrom Notification support (continued)** + +| 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | | | + +**Table 11.7/Q.823.1 – cancelFrom Notification support (continued)** + +| Index | Subindex | Notification field name label | Value of object identifier of attribute type associated with field | Constraints and values | Status | Support | Additional information | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|---------------------------------------|--------|---------|------------------------| +| 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 | attributeType | – | OBJECT
IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT
IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 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 | | | + +**Table 11.7/Q.823.1 – cancelFrom 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | 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 | | | +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 11.8/Q.823.1 – cancelFrom Parameter support** + +There are no parameters specified for this managed object class. + +**Table 11.9/Q.823.1 – cancelFrom Conditions** + +| Condition number | Condition | Reference | +|------------------|------------------------|-------------------------------------------------------------------------| +| c1 | IF 6.3/5 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table 11.10/Q.823.1 – cancelFrom Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------|---------------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | trafficControl-managedElement | {0 0 17 823 0 5 20} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | + +**Table 11.10/Q.823.1 – cancelFrom 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 | | | + +## 12 cancelRerouted ["Q.823"] + +**Table 12.1/Q.823.1 – cancelRerouted 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 | cancelRerouted | {0 0 17 823 0 3 7} | | | + +**Table 12.2/Q.823.1 – cancelRerouted 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 12.3/Q.823.1 – cancelRerouted Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|---------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | cancelReroutedPackage | | Mandatory | m | | | +| 3 | creatorPackage | {0 0 17 823 0 4 14} | "an instance supports it" | o | | | +| 4 | "Rec. M.3100 : 1992":
objectManagementNotificationsPackage | {0 0 13 3100 0 4 20} | Mandatory | m | | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c1 | | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
topPackage | | Mandatory | m | | | +| 7 | trafficControlPackage | | Mandatory | m | | | + +**Table 12.4/Q.823.1 – cancelRerouted 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 2 | controlTmCircuitEndPointSubgroup | {0 0 17 823 0 6 58} | CHOICE | m? | | m | | – | | +| 3 | creatorIdentity | {0 0 17 823 0 6 24} | CHOICE | o? | | o | | – | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c1 | | – | | +| 7 | tmSurveillance | {0 0 17 823 0 6 60} | BOOLEAN | m | | m | | m | | +| 8 | trafficControlId | {0 0 17 823 0 6 61} | CHOICE | m? | | m | | – | | +| 9 | treatment | {0 0 17 823 0 6 64} | CHOICE | m | | m | | m | | + +**Table 12.4/Q.823.1 – cancelRerouted 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 | – | | – | | – | | | + +**Table 12.5/Q.823.1 – cancelRerouted Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 12.6/Q.823.1 – cancelRerouted Action support** + +There are no actions specified for this managed object class. + +**Table 12.7/Q.823.1 – cancelRerouted 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | m | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | m | | | | + +**Table 12.7/Q.823.1 – cancelRerouted Notification support (continued)** + +| 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | | | + +**Table 12.7/Q.823.1 – cancelRerouted Notification support (continued)** + +| Index | Subindex | Notification field name label | Value of object identifier of attribute type associated with field | Constraints and values | Status | Support | Additional information | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|---------------------------------------|--------|---------|------------------------| +| 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 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 | | | + +**Table 12.7/Q.823.1 – cancelRerouted 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | 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 | | | +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 12.8/Q.823.1 – cancelRerouted Parameter support** + +There are no parameters specified for this managed object class. + +**Table 12.9/Q.823.1 – cancelRerouted Conditions** + +| Condition number | Condition | Reference | +|------------------|------------------------|-------------------------------------------------------------------------| +| c1 | IF 7.3/5 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table 12.10/Q.823.1 – cancelRerouted Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------|---------------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | trafficControl-managedElement | {0 0 17 823 0 5 20} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | + +**Table 12.10/Q.823.1 – cancelRerouted 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 | | | + +## 13 cancelTo ["Q.823"] + +**Table 13.1/Q.823.1 – cancelTo 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 | cancelTo | {0 0 17 823 0 3 8} | | | + +**Table 13.2/Q.823.1 – cancelTo 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 13.3/Q.823.1 – cancelTo Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | cancelToPackage | | Mandatory | m | | | +| 3 | creatorPackage | {0 0 17 823 0 4 14} | "an instance supports it" | o | | | +| 4 | "Rec. M.3100 : 1992": objectManagementNotificationsPackage | {0 0 13 3100 0 4 20} | Mandatory | m | | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | cl | | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | +| 7 | trafficControlPackage | | Mandatory | m | | | + +**Table 13.4/Q.823.1 – cancelTo 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 2 | controlTmCircuitEndPointSubgroup | {0 0 17 823 0 6 58} | CHOICE | m? | | m | | – | | +| 3 | creatorIdentity | {0 0 17 823 0 6 24} | CHOICE | o? | | o | | – | | +| 4 | destinationAspect | {0 0 17 823 0 6 26} | CHOICE | m | | m | | m | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 7 | originationAspect | {0 0 17 823 0 6 42} | SEQUENCE | m | | m | | m | | +| 8 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | cl | | – | | +| 9 | percentage | {0 0 17 823 0 6 49} | CHOICE | m | | m | | m | | +| 10 | routingAspect | {0 0 17 823 0 6 51} | ENUMERATED | m | | m | | m | | +| 11 | tmSurveillance | {0 0 17 823 0 6 60} | BOOLEAN | m | | m | | m | | +| 12 | trafficControlId | {0 0 17 823 0 6 61} | CHOICE | m? | | m | | – | | +| 13 | treatment | {0 0 17 823 0 6 64} | CHOICE | m | | m | | m | | + +**Table 13.4/Q.823.1 – cancelTo Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | m | | | +| 5 | – | | – | | – | | | +| 6 | – | | – | | – | | | +| 7 | – | | – | | m | | | +| 8 | – | | – | | – | | | +| 9 | – | | – | | – | | | +| 10 | – | | – | | m | | | +| 11 | – | | – | | – | | | +| 12 | – | | – | | – | | | +| 13 | – | | – | | – | | | + +**Table 13.5/Q.823.1 – cancelTo Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 13.6/Q.823.1 – cancelTo Action support** + +There are no actions specified for this managed object class. + +**Table 13.7/Q.823.1 – cancelTo 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | m | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | m | | | | + +**Table 13.7/Q.823.1 – cancelTo Notification support (continued)** + +| 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | | | + +**Table 13.7/Q.823.1 – cancelTo Notification support (continued)** + +| Index | Subindex | Notification field name label | Value of object identifier of attribute type associated with field | Constraints and values | Status | Support | Additional information | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|---------------------------------------|--------|---------|------------------------| +| 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 | – | INTEGER | o | | | +| | 2.1.4 | correlatedNotifications | – | 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 | attributeType | – | OBJECT
IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT
IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 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 | | | + +**Table 13.7/Q.823.1 – cancelTo 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | 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 | | | +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 13.8/Q.823.1 – cancelTo Parameter support** + +There are no parameters specified for this managed object class. + +**Table 13.9/Q.823.1 – cancelTo Conditions** + +| Condition number | Condition | Reference | +|------------------|------------------------|-------------------------------------------------------------------------| +| c1 | IF 8.3/5 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table 13.10/Q.823.1 – cancelTo Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------|---------------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | trafficControl-managedElement | {0 0 17 823 0 5 20} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | + +**Table 13.10/Q.823.1 – cancelTo 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 | | | + +## **14 circuitEndPointSubgroupCurrentData ["Q.823"]** + +**Table 14.1/Q.823.1 – circuitEndPointSubgroupCurrentData 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 | circuitEndPointSubgroupCurrentData | {0 0 17 823 0 3 9} | | | + +**Table 14.2/Q.823.1 – circuitEndPointSubgroupCurrentData 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 14.3/Q.823.1 – circuitEndPointSubgroupCurrentData Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|---------------------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | answeredIncomingSeizuresPackage | {0 0 17 823 0 4 5} | "this performance measurement is supported by the NE" | c1 | | | +| 3 | "Rec. M.3100 : 1992":
attributeValueChangeNotificationPackage | {0 0 13 3100 0 4 4} | "notification of attribute value change events is required" | c2 | | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
availabilityStatusPackage | {2 9 3 2 4 22} | "the managed object can be scheduled" | c3 | | | +| 5 | circuitEndPointSubgroupCurrentDataPackage | | Mandatory | m | | | +| 6 | "Rec. M.3100 : 1992":
createDeleteNotificationsPackage | {0 0 13 3100 0 4 10} | "notification of object creation and object deletion events is required" | c4 | | | +| 7 | "ITU-T Rec. Q.822 : 1994":
currentDataPkg | | Mandatory | m | | | +| 8 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
dailyScheduling | {2 9 3 2 4 25} | "daily scheduling is required and the weekly or external scheduling package is not present" | c5 | | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
duration | {2 9 3 2 4 26} | "the scanning function is to be enabled between specified start and stop times" | c6 | | | +| 10 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
externalScheduler | {2 9 3 2 4 27} | "reference to external scheduler is required and the daily or weekly scheduling package is not present" | c7 | | | +| 11 | "ITU-T Rec. Q.822 : 1994":
filterSuppressionPkg | {0 0 17 822 0 4 2} | "an instance supports it and the zeroSuppressionPkg is not present" | c8 | | | +| 12 | "ITU-T Rec. Q.822 : 1994":
historyRetentionPkg | {0 0 17 822 0 4 6} | "historyData objects are to be created at the end of an interval." | c9 | | | +| 13 | "ITU-T Rec. Q.822 : 1994":
maxSuppressedIntervalsPkg | {0 0 17 822 0 4 7} | "an instance supports it and at least one of zeroSuppressionPkg or filterSuppressionPkg is present." | c10 | | | +| 14 | "ITU-T Rec. Q.822 : 1994":
measurementListPkg | {0 0 17 822 0 4 8} | "an instance supports it or the object class is currentData" | c11 | | | +| 15 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervalsPkg | {0 0 17 822 0 4 9} | "suppression counts are required and the filterSuppressionPkg or the zeroSuppressionPkg is present." | c12 | | | +| 16 | "ITU-T Rec. Q.822 : 1994":
observedManagedObjectPkg | {0 0 17 822 0 4 11} | "an instance supports it." | o | | | + +**Table 14.3/Q.823.1 – circuitEndPointSubgroupCurrentData Package support (concluded)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 17 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c13 | | | +| 18 | "ITU-T Rec. X.739":
periodSynchronizationPackage | {2 9 2 11 4 10} | "configurable agent internal synchronization of repeating time periods is required" | c14 | | | +| 19 | "ITU-T Rec. X.739":
scannerPackage | | Mandatory | m | | | +| 20 | "ITU-T Rec. Q.822 : 1994":
scheduledPMReportPkg | {0 0 17 822 0 4 12} | "scheduled notifications are to be emitted." | c15 | | | +| 21 | "Rec. M.3100 : 1992":
stateChangeNotificationPackage | {0 0 13 3100 0 4 28} | "notification of state change event is required" | c16 | | | +| 22 | "ITU-T Rec. Q.822 : 1994":
thresholdPkg | {0 0 17 822 0 4 13} | "a Quality of Service Alarm Notification is to be emitted for threshold crossing." | c17 | | | +| 23 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
topPackage | | Mandatory | m | | | +| 24 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
weeklyScheduling | {2 9 3 2 4 29} | "weekly scheduling is required and the daily or external scheduling package is not present" | c18 | | | +| 25 | "ITU-T Rec. Q.822 : 1994":
zeroSuppressionPkg | {0 0 17 822 0 4 15} | "an instance supports it and the filterSuppressionPkg is not present." | c19 | | | + +**Table 14.4/Q.823.1 – circuitEndPointSubgroupCurrentData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
administrativeState | {2 9 3 2 7 31} | ENUMERATED | m | | m | | m | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 3 | answeredIncomingSeizures | {0 0 17 823 0 6 9} | INTEGER | c1? | | – | | – | | +| 4 | answeredOutgoingSeizures | {0 0 17 823 0 6 10} | INTEGER | m? | | – | | – | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
availabilityStatus | {2 9 3 2 7 33} | SET OF INTEGER | c3? | | c3 | | – | | + +**Table 14.4/Q.823.1 – circuitEndPointSubgroupCurrentData 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 | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": discriminatorConstruct | {2 9 3 2 7 56} | CHOICE | c8 | | c8 | | c8 | | +| 7 | "ITU-T Rec. Q.822 : 1994": elapsedTime | {0 0 17 822 0 7 2} | CHOICE | m? | | m | | – | | +| 8 | "ITU-T Rec. X.739": granularityPeriod | {2 9 2 11 7 23} | CHOICE | m | | m | | m | | +| 9 | "ITU-T Rec. Q.822 : 1994": historyRetention | {0 0 17 822 0 7 5} | INTEGER | c9 | | c9 | | c9 | | +| 10 | incomingSeizures | {0 0 17 823 0 6 31} | INTEGER | m? | | – | | – | | +| 11 | incomingTrafficUsage | {0 0 17 823 0 6 33} | INTEGER | m? | | – | | – | | +| 12 | "Rec. X.721 ISO/IEC 10165-2 : 1992": intervalsOfDay | {2 9 3 2 7 57} | SET OF SEQUENCE | c5 | | c5 | | c5 | | +| 13 | "ITU-T Rec. Q.822 : 1994": maxSuppressedIntervals | {0 0 17 822 0 7 6} | INTEGER | c10 | | c10 | | c10 | | +| 14 | "ITU-T Rec. Q.822 : 1994": measurementList | {0 0 17 822 0 7 7} | SET OF SEQUENCE | c11 | | c11 | | c11 | | +| 15 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 16 | "ITU-T Rec. Q.822 : 1994": numSuppressedIntervals | {0 0 17 822 0 7 9} | INTEGER | c12? | | c12 | | – | | +| 17 | numberOfAvailCircuits | {0 0 17 823 0 6 40} | CHOICE | m? | | – | | – | | +| 18 | "ITU-T Rec. X.738": numericAttributeIdArray | {2 9 2 13 7 10} | SEQUENCE OF CHOICE | c15 | | c15 | | c15 | | +| 19 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 20 | "ITU-T Rec. Q.822 : 1994": observedObjectClass | {0 0 17 822 0 7 10} | CHOICE | o? | | o | | – | | +| 21 | "ITU-T Rec. X.739": observedObjectInstance | {2 9 2 11 7 16} | CHOICE | o? | | o | | – | | +| 22 | "ITU-T Rec. X.738": onceReportAttributeIdList | {2 9 2 13 7 16} | SET OF CHOICE | c15 | | c15 | | c15 | | +| 23 | "Rec. X.721 ISO/IEC 10165-2 : 1992": operationalState | {2 9 3 2 7 35} | ENUMERATED | – | | m | | – | | +| 24 | outgoingBids | {0 0 17 823 0 6 44} | INTEGER | m? | | – | | – | | +| 25 | outgoingSeizures | {0 0 17 823 0 6 45} | INTEGER | m? | | – | | – | | + +**Table 14.4/Q.823.1 – circuitEndPointSubgroupCurrentData 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 | +| 26 | outgoingTrafficUsage | {0 0 17 823 0 6 47} | INTEGER | m? | | – | | – | | +| 27 | overflow | {0 0 17 823 0 6 48} | INTEGER | m? | | – | | – | | +| 28 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c13 | | – | | +| 29 | "ITU-T Rec. X.739": periodSynchronizationTime | {2 9 2 11 7 24} | GeneralizedTime | c14 | | c14 | | c14 | | +| 30 | "ITU-T Rec. Q.822 : 1994": reportAllAttributes | {0 0 17 822 0 7 11} | BOOLEAN | c17 | | c17 | | c17 | | +| 31 | "ITU-T Rec. X.738": scanAttributeList | {2 9 2 13 7 21} | SET OF CHOICE | c15 | | c15 | | c15 | | +| 32 | "ITU-T Rec. X.739": scannerId | {2 9 2 11 7 25} | CHOICE | m? | | m | | – | | +| 33 | "Rec. X.721 ISO/IEC 10165-2 : 1992": schedulerName | {2 9 3 2 7 67} | CHOICE | c7? | | c7 | | – | | +| 34 | "Rec. X.721 ISO/IEC 10165-2 : 1992": startTime | {2 9 3 2 7 68} | GeneralizedTime | c6 | | c6 | | c6 | | +| 35 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stopTime | {2 9 3 2 7 69} | CHOICE | c6 | | c6 | | c6 | | +| 36 | "ITU-T Rec. Q.822 : 1994": suppressAdditionalThresholds | {0 0 17 822 0 7 13} | BOOLEAN | c17 | | c17 | | c17 | | +| 37 | "ITU-T Rec. Q.822 : 1994": suspectIntervalFlag | {0 0 17 822 0 7 14} | BOOLEAN | m? | | m | | – | | +| 38 | "ITU-T Rec. Q.822 : 1994": thresholdDataInstance | {0 0 17 822 0 7 16} | SET OF CHOICE | c17 | | c17 | | c17 | | +| 39 | "Rec. X.721 ISO/IEC 10165-2 : 1992": weekMask | {2 9 3 2 7 71} | SET OF SEQUENCE | c18 | | c18 | | c18 | | + +**Table 14.4/Q.823.1 – circuitEndPointSubgroupCurrentData 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 | c5 | | c5 | | c5 | | | +| 13 | – | | – | | – | | | +| 14 | – | | – | | – | | | +| 15 | – | | – | | – | | | +| 16 | – | | – | | – | | | +| 17 | – | | – | | – | | | +| 18 | – | | – | | – | | | +| 19 | – | | – | | – | | | +| 20 | – | | – | | – | | | +| 21 | – | | – | | – | | | +| 22 | c15 | | c15 | | – | | | +| 23 | – | | – | | – | | | +| 24 | – | | – | | – | | | +| 25 | – | | – | | – | | | +| 26 | – | | – | | – | | | +| 27 | – | | – | | – | | | +| 28 | – | | – | | – | | | +| 29 | – | | – | | – | | | +| 30 | – | | – | | – | | | +| 31 | c15 | | c15 | | – | | | +| 32 | – | | – | | – | | | +| 33 | – | | – | | – | | | +| 34 | – | | – | | – | | | +| 35 | – | | – | | c6 | | | +| 36 | – | | – | | – | | | +| 37 | – | | – | | m | | | +| 38 | c17 | | c17 | | – | | | +| 39 | c18 | | c18 | | c18 | | | + +**Table 14.5/Q.823.1 – circuitEndPointSubgroupCurrentData Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 14.6/Q.823.1 – circuitEndPointSubgroupCurrentData Action support** + +There are no actions specified for this managed object class. + +**Table 14.7/Q.823.1 – circuitEndPointSubgroupCurrentData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | c2 | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | c4 | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | c4 | | | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": qualityOfServiceAlarm | {2 9 3 2 10 11} | | c17 | | | "Rec. Q.821 : 1992":
correlatedRecordNameParameter

"Rec. Q.821 : 1992":
logRecordIdParameter

"Rec. Q.821 : 1992":
suspectObjectListParameter | +| 5 | "ITU-T Rec. X.738": scanReport | {2 9 2 13 10 2} | | c15 | | | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stateChange | {2 9 3 2 10 14} | | c16 | | | | + +**Table 14.7/Q.823.1 – circuitEndPointSubgroupCurrentData Notification support (continued)** + +| 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 | c2 | | | +| | 1.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 1.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | c: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 | c:m | | | +| | 1.1.3.1 | attributeID | – | CHOICE | c:m | | | +| | 1.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.2 | | | +| | 1.1.3.1.2 | localForm | – | INTEGER | c:o.2 | | | +| | 1.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | c:o | | | +| | 1.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | c:m | | | +| | 1.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 1.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 1.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 1.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | | | + +**Table 14.7/Q.823.1 – circuitEndPointSubgroupCurrentData Notification support (continued)** + +| Index | Subindex | Notification field name label | Value of object identifier of attribute type associated with field | Constraints and values | Status | Support | Additional information | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|---------------------------------------|--------|---------|------------------------| +| 2 | 2.1 | ObjectInfo | | Information Syntax
SEQUENCE | c4 | | | +| | 2.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 2.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c: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 | c:o | | | +| | 2.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 2.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 2.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | c4 | | | +| | 3.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 3.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c:o | | | +| | 3.1.2.1 | attributeId | – | CHOICE | c:m | | | + +**Table 14.7/Q.823.1 – circuitEndPointSubgroupCurrentData Notification support (continued)** + +| 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.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 | c:o | | | +| | 3.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 3.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 3.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 3.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 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 | c17 | | | +| | 4.1.1 | probableCause | {2 9 3 2 7 18} | CHOICE | c:m | | | +| | 4.1.1.1 | globalValue | – | OBJECT IDENTIFIER | c:o.8 | | | +| | 4.1.1.2 | localValue | – | INTEGER | c:o.8 | | | +| | 4.1.2 | specificProblems | {2 9 3 2 7 27} | SET OF CHOICE | c:o | | | +| | 4.1.2.1 | OBJECT IDENTIFIER | – | OBJECT IDENTIFIER | c:o.9 | | | +| | 4.1.2.2 | INTEGER | – | INTEGER | c:o.9 | | | +| | 4.1.3 | perceivedSeverity | {2 9 3 2 7 17} | ENUMERATED | c:m | | | +| | 4.1.4 | backedUpStatus | {2 9 3 2 7 11} | BOOLEAN | c:o | | | + +**Table 14.7/Q.823.1 – circuitEndPointSubgroupCurrentData Notification support (continued)** + +| 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.5 | backUpObject | {2 9 3 2 7 40} | CHOICE | c:o | | | +| | 4.1.5.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.5.2 | nonSpecificForm | – | OCTET STRING | c:o.10 | | | +| | 4.1.5.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.6 | trendIndication | {2 9 3 2 7 30} | ENUMERATED | c:o | | | +| | 4.1.7 | thresholdInfo | {2 9 3 2 7 29} | SEQUENCE | c:o | | | +| | 4.1.7.1 | triggeredThreshold | – | CHOICE | c:m | | | +| | 4.1.7.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.11 | | | +| | 4.1.7.1.2 | localForm | – | INTEGER | c:o.11 | | | +| | 4.1.7.2 | observedValue | – | CHOICE | c:m | | | +| | 4.1.7.2.1 | integer | – | INTEGER | c:o.12 | | | +| | 4.1.7.2.2 | real | – | REAL | c:o.12 | | | +| | 4.1.7.3 | thresholdLevel | – | CHOICE | c:o | | | +| | 4.1.7.3.1 | up | – | SEQUENCE | c:o.13 | | | +| | 4.1.7.3.1.1 | high | – | CHOICE | c:m | | | +| | 4.1.7.3.1.1.1 | integer | – | INTEGER | c:o.14 | | | +| | 4.1.7.3.1.1.2 | real | – | REAL | c:o.14 | | | +| | 4.1.7.3.1.2 | low | – | CHOICE | c:o | | | +| | 4.1.7.3.1.2.1 | integer | – | INTEGER | c:o.15 | | | +| | 4.1.7.3.1.2.2 | real | – | REAL | c:o.15 | | | +| | 4.1.7.3.2 | down | – | SEQUENCE | c:o.13 | | | +| | 4.1.7.3.2.1 | high | – | CHOICE | c:m | | | +| | 4.1.7.3.2.1.1 | integer | – | INTEGER | c:o.16 | | | +| | 4.1.7.3.2.1.2 | real | – | REAL | c:o.16 | | | +| | 4.1.7.3.2.2 | low | – | CHOICE | c:m | | | +| | 4.1.7.3.2.2.1 | integer | – | INTEGER | c:o.17 | | | +| | 4.1.7.3.2.2.2 | real | – | REAL | c:o.17 | | | +| | 4.1.7.4 | armTime | – | GeneralizedTime | c:o | | | +| | 4.1.8 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 4.1.9 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c:o | | | + +**Table 14.7/Q.823.1 – circuitEndPointSubgroupCurrentData Notification support (continued)** + +| 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.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.18 | | | +| | 4.1.9.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.9.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.9.2.2 | nonSpecificForm | – | OCTET STRING | c:o.18 | | | +| | 4.1.9.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.18 | | | +| | 4.1.9.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.9.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.10 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | c:o | | | +| | 4.1.10.1 | attributeID | – | CHOICE | c:m | | | +| | 4.1.10.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.19 | | | +| | 4.1.10.1.2 | localForm | – | INTEGER | c:o.19 | | | +| | 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 | c:o | | | +| | 4.1.11.1 | attributeId | – | CHOICE | c:m | | | +| | 4.1.11.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.20 | | | +| | 4.1.11.1.2 | localForm | – | INTEGER | c:o.20 | | | +| | 4.1.11.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 4.1.12 | proposedRepairActions | {2 9 3 2 7 19} | SET OF CHOICE | c:o | | | +| | 4.1.12.1 | OBJECT IDENTIFIER | – | OBJECT IDENTIFIER | c:o.21 | | | +| | 4.1.12.2 | INTEGER | – | INTEGER | c:o.21 | | | +| | 4.1.13 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 4.1.14 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | | | + +**Table 14.7/Q.823.1 – circuitEndPointSubgroupCurrentData Notification support (continued)** + +| Index | Subindex | Notification field name label | Value of object identifier of attribute type associated with field | Constraints and values | Status | Support | Additional information | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|---------------------------------------|--------|---------|------------------------| +| 5 | 5.1 | ScanReportInformation | | Information Syntax
SEQUENCE | c:15 | | | +| | 5.1.1 | scanInitiationTime | {2 9 2 13 7 22} | GeneralizedTime | c:o | | | +| | 5.1.2 | onceReportAttributeList | {2 9 2 13 7 17} | SET OF
SEQUENCE | c:o | | | +| | 5.1.2.1 | attributeId | – | CHOICE | c:m | | | +| | 5.1.2.1.1 | globalForm | – | OBJECT
IDENTIFIER | c:o:22 | | | +| | 5.1.2.1.2 | localForm | – | INTEGER | c:o:22 | | | +| | 5.1.2.2 | attributeValue | – | ANY DEFINED
BY attributeId | c:m | | | +| | 5.1.3 | observationScanList | {2 9 2 13 7 15} | SET OF
SEQUENCE | c:m | | | +| | 5.1.3.1 | observedObjectInstance | – | CHOICE | c:o | | | +| | 5.1.3.1.1 | distinguishedName | – | SEQUENCE OF
SET OF
SEQUENCE | c:o:23 | | | +| | 5.1.3.1.1.1 | attributeType | – | OBJECT
IDENTIFIER | c:m | | | +| | 5.1.3.1.1.2 | attributeValue | – | ANY | c:m | | | +| | 5.1.3.1.2 | nonSpecificForm | – | OCTET STRING | c:o:23 | | | +| | 5.1.3.1.3 | localDistinguishedName | – | SEQUENCE OF
SET OF
SEQUENCE | c:o:23 | | | +| | 5.1.3.1.3.1 | attributeType | – | OBJECT
IDENTIFIER | c:m | | | +| | 5.1.3.1.3.2 | attributeValue | – | ANY | c:m | | | +| | 5.1.3.2 | attributeMeasureList | – | SET OF
SEQUENCE | c:o | | | +| | 5.1.3.2.1 | attributeId | – | CHOICE | c:m | | | +| | 5.1.3.2.1.1 | globalForm | – | OBJECT
IDENTIFIER | c:o:24 | | | +| | 5.1.3.2.1.2 | localForm | – | INTEGER | c:o:24 | | | +| | 5.1.3.2.2 | attributeValue | – | ANY DEFINED
BY attributeId | c:o | | | +| | 5.1.3.2.3 | timeStamp | – | CHOICE | c:o | | | +| | 5.1.3.2.3.1 | days | – | INTEGER | c:o:25 | | | +| | 5.1.3.2.3.2 | hours | – | INTEGER | c:o:25 | | | +| | 5.1.3.2.3.3 | minutes | – | INTEGER | c:o:25 | | | +| | 5.1.3.2.3.4 | seconds | – | INTEGER | c:o:25 | | | +| | 5.1.3.2.3.5 | milliSeconds | – | INTEGER | c:o:25 | | | +| | 5.1.3.2.3.6 | microSeconds | – | INTEGER | c:o:25 | | | +| | 5.1.3.2.3.7 | nanoSeconds | – | INTEGER | c:o:25 | | | + +**Table 14.7/Q.823.1 – circuitEndPointSubgroupCurrentData Notification support (continued)** + +| 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.3.2.3.8 | picoSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.4 | suspectFlag | – | BOOLEAN | c:o | | | +| | 5.1.3.3 | numericValueArray | – | SEQUENCE OF CHOICE | c:o | | | +| | 5.1.3.3.1 | missingData | – | NULL | c:o.26 | | | +| | 5.1.3.3.2 | valueOnly | – | CHOICE | c:o.26 | | | +| | 5.1.3.3.2.1 | integer | – | INTEGER | c:o.27 | | | +| | 5.1.3.3.2.2 | real | – | REAL | c:o.27 | | | +| | 5.1.3.3.3 | qualifiedValue | – | SEQUENCE | c:o.26 | | | +| | 5.1.3.3.3.1 | value | – | CHOICE | c:m | | | +| | 5.1.3.3.3.1.1 | integer | – | INTEGER | c:o.28 | | | +| | 5.1.3.3.3.1.2 | real | – | REAL | c:o.28 | | | +| | 5.1.3.3.3.2 | timeStamp | – | CHOICE | c:o | | | +| | 5.1.3.3.3.2.1 | days | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.2 | hours | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.3 | minutes | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.4 | seconds | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.5 | milliSeconds | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.6 | microSeconds | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.7 | nanoSeconds | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.8 | picoSeconds | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.3 | suspectFlag | – | BOOLEAN | c:o | | | +| | 5.1.4 | incompleteScan | {2 9 2 13 7 30} | INTEGER | c:o | | | +| | 5.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 5.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 5.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 5.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | +| 6 | 6.1 | StateChangeInfo | | Information Syntax
SEQUENCE | c!6 | | | +| | 6.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 6.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | c:o | | | +| | 6.1.2.1 | globalForm | – | OBJECT IDENTIFIER | c:o.30 | | | +| | 6.1.2.2 | localForm | – | INTEGER | c:o.30 | | | +| | 6.1.3 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | c:m | | | +| | 6.1.3.1 | attributeID | – | CHOICE | c:m | | | + +**Table 14.7/Q.823.1 – circuitEndPointSubgroupCurrentData 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 | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|-----------------------------|--------|---------|------------------------| +| | 6.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.31 | | | +| | 6.1.3.1.2 | localForm | – | INTEGER | c:o.31 | | | +| | 6.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | c:o | | | +| | 6.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | c:m | | | +| | 6.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 6.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c:o | | | +| | 6.1.5.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 6.1.5.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 6.1.5.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.32 | | | +| | 6.1.5.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 6.1.5.2.2 | nonSpecificForm | – | OCTET STRING | c:o.32 | | | +| | 6.1.5.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.32 | | | +| | 6.1.5.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 6.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 6.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 6.1.7.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.7.2 | significance | – | BOOLEAN | c:o | | | +| | 6.1.7.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 14.8/Q.823.1 – circuitEndPointSubgroupCurrentData Parameter support** + +| Index | Parameter template label | Value of object identifier for parameter | Constraints and values | Status | Support | Additional information | +|-------|--------------------------------------------------|------------------------------------------|----------------------------------|--------|---------|------------------------| +| 1 | "Rec. Q.821:1992": correlatedRecordNameParameter | {0 0 17 821 0 5 2} | EVENT-INFO qualityofServiceAlarm | c17 | | | +| 2 | "Rec. Q.821:1992": logRecordIdParameter | {0 0 17 821 0 5 1} | EVENT-INFO qualityofServiceAlarm | c17 | | | +| 3 | "Rec. Q.821:1992": suspectObjectListParameter | {0 0 17 821 0 5 3} | EVENT-INFO qualityofServiceAlarm | c17 | | | + +**Table 14.9/Q.823.1 – circuitEndPointSubgroupCurrentData Conditions** + +| Condition number | Condition | Reference | +|------------------|-------------------------|---------------------------------------------------------------------------------------------------------| +| c1 | IF 9.3/2 THEN m ELSE – | "this performance measurement is supported by the NE" | +| c2 | IF 9.3/3 THEN m ELSE – | "notification of attribute value change events is required" | +| c3 | IF 9.3/4 THEN m ELSE – | "the managed object can be scheduled" | +| c4 | IF 9.3/6 THEN m ELSE – | "notification of object creation and object deletion events is required" | +| c5 | IF 9.3/8 THEN m ELSE – | "daily scheduling is required and the weekly or external scheduling package is not present" | +| c6 | IF 9.3/9 THEN m ELSE – | "the scanning function is to be enabled between specified start and stop times" | +| c7 | IF 9.3/10 THEN m ELSE – | "reference to external scheduler is required and the daily or weekly scheduling package is not present" | +| c8 | IF 9.3/11 THEN m ELSE – | "an instance supports it and the zeroSuppressionPkg is not present" | +| c9 | IF 9.3/12 THEN m ELSE – | "historyData objects are to be created at the end of an interval." | +| c10 | IF 9.3/13 THEN m ELSE – | "an instance supports it and at least one of zeroSuppressionPkg or filterSuppressionPkg is present." | +| c11 | IF 9.3/14 THEN m ELSE – | "an instance supports it or the object class is currentData" | +| c12 | IF 9.3/15 THEN m ELSE – | "suppression counts are required and the filterSuppressionPkg or the zeroSuppressionPkg is present." | +| c13 | IF 9.3/17 THEN m ELSE – | "any registered package, other than this package has been instantiated" | +| c14 | IF 9.3/18 THEN m ELSE – | "configurable agent internal synchronization of repeating time periods is required" | +| c15 | IF 9.3/20 THEN m ELSE – | "scheduled notifications are to be emitted." | +| c16 | IF 9.3/21 THEN m ELSE – | "notification of state change event is required" | +| c17 | IF 9.3/22 THEN m ELSE – | "a Quality of Service Alarm Notification is to be emitted for threshold crossing." | +| c18 | IF 9.3/24 THEN m ELSE – | "weekly scheduling is required and the daily or external scheduling package is not present" | +| c19 | IF 9.3/25 THEN m ELSE – | "an instance supports it and the filterSuppressionPkg is not present." | + +**Table 14.10/Q.823.1 – circuitEndPointSubgroupCurrentData Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|----------------------------------------------------------|---------------------------------------------|---------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "ITU-T Rec. X.738":
conflictingPackagesScanner-system | {2 9 2 13 6 9} | Superior class:
"Rec. X.721 ISO/IEC 10165-2 : 1992":
system
AND SUBCLASSES | o | | | + +**Table 14.10/Q.823.1 – circuitEndPointSubgroupCurrentData 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:m | | | +| | 1.6 | Delete contained objects | | c:x | | | + +## 15 circuitEndPointSubgroupHistoryData ["Q.823"] + +**Table 15.1/Q.823.1 – circuitEndPointSubgroupHistoryData 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 | circuitEndPointSubgroupHistoryData | {0 0 17 823 0 3 10} | | | + +**Table 15.2/Q.823.1 – circuitEndPointSubgroupHistoryData 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 15.3/Q.823.1 – circuitEndPointSubgroupHistoryData Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|-----------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | answeredIncomingSeizureHistoryPackage | {0 0 17 823 0 4 6} | "this package is present in the corresponding currentData" | c1 | | | +| 3 | circuitEndPointSubgroupHistoryDataPackage | | Mandatory | m | | | +| 4 | "ITU-T Rec. Q.822 : 1994":
historyDataMeasurementListPkg | {0 0 17 822 0 4 4} | "the measurementListPkg is present in the corresponding currentData instance" | c2 | | | +| 5 | "ITU-T Rec. Q.822 : 1994":
historyDataPkg | | Mandatory | m | | | +| 6 | "ITU-T Rec. Q.822 : 1994":
historyDataSuspectIntervalFlagPkg | {0 0 17 822 0 4 5} | "an instance supports it." | o | | | +| 7 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervalsPkg | {0 0 17 822 0 4 9} | "this package is present in the corresponding currentData instance." | c3 | | | +| 8 | "ITU-T Rec. Q.822 : 1994":
objectDeleteNotificationPkg | {0 0 17 822 0 4 10} | "an instance supports it." | o | | | +| 9 | "ITU-T Rec. Q.822 : 1994":
observedManagedObjectPkg | {0 0 17 822 0 4 11} | "this package is present in the corresponding currentData instance." | c3 | | | +| 10 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c4 | | | +| 11 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
topPackage | | Mandatory | m | | | + +**Table 15.4/Q.823.1 – circuitEndPointSubgroupHistoryData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 2 | answeredIncomingSeizures | {0 0 17 823 0 6 9} | INTEGER | c1? | | c1 | | – | | +| 3 | answeredOutgoingSeizures | {0 0 17 823 0 6 10} | INTEGER | m? | | m | | – | | +| 4 | "ITU-T Rec. X.739": granularityPeriod | {2 9 2 11 7 23} | CHOICE | m? | | m | | – | | +| 5 | "ITU-T Rec. Q.822 : 1994": historyDataId | {0 0 17 822 0 7 4} | CHOICE | m? | | m | | – | | +| 6 | incomingSeizures | {0 0 17 823 0 6 31} | INTEGER | m? | | m | | – | | +| 7 | incomingTrafficUsage | {0 0 17 823 0 6 33} | INTEGER | m? | | m | | – | | +| 8 | "ITU-T Rec. Q.822 : 1994": measurementList | {0 0 17 822 0 7 7} | SET OF SEQUENCE | c2? | | c2 | | – | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 10 | "ITU-T Rec. Q.822 : 1994": numSuppressedIntervals | {0 0 17 822 0 7 9} | INTEGER | c3? | | c3 | | – | | +| 11 | numberOfAvailCircuits | {0 0 17 823 0 6 40} | CHOICE | m? | | m | | – | | +| 12 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 13 | "ITU-T Rec. Q.822 : 1994": observedObjectClass | {0 0 17 822 0 7 10} | CHOICE | c3? | | c3 | | – | | +| 14 | "ITU-T Rec. X.739": observedObjectInstance | {2 9 2 11 7 16} | CHOICE | c3? | | c3 | | – | | +| 15 | outgoingBids | {0 0 17 823 0 6 44} | INTEGER | m? | | m | | – | | +| 16 | outgoingSeizures | {0 0 17 823 0 6 45} | INTEGER | m? | | m | | – | | +| 17 | outgoingTrafficUsage | {0 0 17 823 0 6 47} | INTEGER | m? | | m | | – | | +| 18 | overflow | {0 0 17 823 0 6 48} | INTEGER | m? | | m | | – | | +| 19 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c4 | | – | | +| 20 | "ITU-T Rec. Q.822 : 1994": periodEndTime | {0 0 17 822 0 7 12} | GeneralizedTime | m? | | m | | – | | +| 21 | "ITU-T Rec. Q.822 : 1994": suspectIntervalFlag | {0 0 17 822 0 7 14} | BOOLEAN | o? | | o | | – | | + +**Table 15.4/Q.823.1 – circuitEndPointSubgroupHistoryData 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 | – | | – | | – | | | + +**Table 15.5/Q.823.1 – circuitEndPointSubgroupHistoryData Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 15.6/Q.823.1 – circuitEndPointSubgroupHistoryData Action support** + +There are no actions specified for this managed object class. + +**Table 15.7/Q.823.1 – circuitEndPointSubgroupHistoryData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | o | | | | + +**Table 15.7/Q.823.1 – circuitEndPointSubgroupHistoryData 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 | ObjectInfo | | Information Syntax
SEQUENCE | o | | | +| | 1.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 1.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c:o | | | +| | 1.1.2.1 | attributeId | – | CHOICE | c:m | | | +| | 1.1.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.1 | | | +| | 1.1.2.1.2 | localForm | – | INTEGER | c:o.1 | | | +| | 1.1.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 1.1.3 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 1.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c:o | | | +| | 1.1.4.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 1.1.4.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 1.1.4.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.2 | | | +| | 1.1.4.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.4.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 1.1.4.2.2 | nonSpecificForm | – | OCTET STRING | c:o.2 | | | +| | 1.1.4.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.2 | | | +| | 1.1.4.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 1.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 1.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 1.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 1.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 15.8/Q.823.1 – circuitEndPointSubgroupHistoryData Parameter support** + +There are no parameters specified for this managed object class. + +**Table 15.9/Q.823.1 – circuitEndPointSubgroupHistoryData Conditions** + +| Condition number | Condition | Reference | +|------------------|--------------------------|-------------------------------------------------------------------------------| +| c1 | IF 10.3/2 THEN m ELSE – | "this package is present in the corresponding currentData" | +| c2 | IF 10.3/4 THEN m ELSE – | "the measurementListPkg is present in the corresponding currentData instance" | +| c3 | IF 10.3/7 THEN m ELSE – | "this package is present in the corresponding currentData instance." | +| c4 | IF 10.3/10 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table 15.10/Q.823.1 – circuitEndPointSubgroupHistoryData Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|--------------------------------------------------------------|---------------------------------------------|--------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | circuitEndPointSubgroupHistoryData-tmCircuitEndPointSubgroup | {0 0 17 823 0 5 4} | Superior class:
tmCircuitEndPointSubgroup
AND SUBCLASSES | o | | | +| 2 | "ITU-T Rec. Q.822 : 1994":
historyData-currentData | {0 0 17 822 0 6 1} | Superior class:
"ITU-T Rec. Q.822 : 1994":
currentData
AND SUBCLASSES | o | | | + +**Table 15.10/Q.823.1 – circuitEndPointSubgroupHistoryData 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:x | | | +| | 1.6 | Delete contained objects | | c:m | | | +| 2 | 2.1 | Create support | | – | | | +| | 2.2 | Create with reference object | | – | | | +| | 2.3 | Create with automatic instance naming | | – | | | +| | 2.4 | Delete support | | c:m | | | +| | 2.5 | Delete only if no contained objects | | c:x | | | +| | 2.6 | Delete contained objects | | c:m | | | + +### 16 congestionLevelIndication ["Q.823"] + +**Table 16.1/Q.823.1 – congestionLevelIndication 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 | congestionLevelIndication | {0 0 17 823 0 3 11} | | | + +**Table 16.2/Q.823.1 – congestionLevelIndication 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 16.3/Q.823.1 – congestionLevelIndication Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|----------------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | "Rec. M.3100 : 1992":
attributeValueChangeNot
ificationPackage | {0 0 13 3100 0 4 4} | Mandatory | m | | | +| 3 | congestionLevelIndicationPackage | | Mandatory | m | | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c1 | | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
topPackage | | Mandatory | m | | | + +**Table 16.4/Q.823.1 – congestionLevelIndication 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 2 | congestionLevel | {0 0 17 823 0 6 21} | ENUMERATED | m? | | m | | – | | +| 3 | congestionLevelIndicationId | {0 0 17 823 0 6 22} | CHOICE | m? | | m | | – | | + +**Table 16.4/Q.823.1 – congestionLevelIndication 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 | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c1 | | – | | + +**Table 16.4/Q.823.1 – congestionLevelIndication Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | – | | | +| 5 | – | | – | | – | | | +| 6 | – | | – | | – | | | + +**Table 16.5/Q.823.1 – congestionLevelIndication Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 16.6/Q.823.1 – congestionLevelIndication Action support** + +There are no actions specified for this managed object class. + +**Table 16.7/Q.823.1 – congestionLevelIndication 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | + +**Table 16.7/Q.823.1 – congestionLevelIndication 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | | | + +**Table 16.8/Q.823.1 – congestionLevelIndication Parameter support** + +There are no parameters specified for this managed object class. + +**Table 16.9/Q.823.1 – congestionLevelIndication Conditions** + +| Condition number | Condition | Reference | +|------------------|------------------------|-------------------------------------------------------------------------| +| c1 | IF 1.3/4 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table 16.10/Q.823.1 – congestionLevelIndication Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------|---------------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | congestionLevelIndication-managedElement | {0 0 17 823 0 5 5} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | + +**Table 16.10/Q.823.1 – congestionLevelIndication 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 | | – | | | +| | 1.5 | Delete only if no contained objects | | – | | | +| | 1.6 | Delete contained objects | | – | | | + +## 17 destinationCodeControl ["Q.823"] + +**Table 17.1/Q.823.1 – destinationCodeControl 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 | destinationCodeControl | {0 0 17 823 0 3 12} | | | + +**Table 17.2/Q.823.1 – destinationCodeControl 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 17.3/Q.823.1 – destinationCodeControl Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|---------------------------------------------------------------|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | assocOwnerDccGroupPackage | {0 0 17 823 0 4 7} | "percentagePackage and continuousTimerPackage and asynchronousTimerPackage and leakyBucketPackage are not present, and the NE supports it." | c1 | | | +| 3 | asynchronousTimerPackage | {0 0 17 823 0 4 8} | "percentagePackage and continuousTimerPackage and leakyBucketPackage and assocOwnerDccGroupPackage are not present, and the NE supports it." | c2 | | | +| 4 | continuousTimerPackage | {0 0 17 823 0 4 13} | "percentagePackage and asynchronousTimerPackage and leakyBucketPackage and assocOwnerDccGroupPackage are not present, and the NE supports it." | c3 | | | +| 5 | creatorPackage | {0 0 17 823 0 4 14} | "an instance supports it" | o | | | +| 6 | destinationCodeControlPackage | | Mandatory | m | | | +| 7 | destinationTypePackage | {0 0 17 823 0 4 16} | "destination type is required to unambiguously identify the destinationCode." | c4 | | | +| 8 | leakyBucketPackage | {0 0 17 823 0 4 17} | "percentagePackage and continuousTimerPackage and asynchronousTimerPackage and assocOwnerDccGroupPackage are not present, and the NE supports it." | c5 | | | +| 9 | "Rec. M.3100 : 1992":
objectManagementNotificationsPackage | {0 0 13 3100 0 4 20} | Mandatory | m | | | +| 10 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c6 | | | +| 11 | percentagePackage | {0 0 17 823 0 4 19} | "continuousTimerPackage and asynchronousTimerPackage and leakyBucketPackage and assocOwnerDccGroupPackage are not present, and the NE supports it." | c7 | | | +| 12 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
topPackage | | Mandatory | m | | | +| 13 | trafficControlPackage | | Mandatory | m | | | + +**Table 17.4/Q.823.1 – destinationCodeControl 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 2 | assocOwnerDccGroup | {0 0 17 823 0 6 11} | CHOICE | c1 | | c1 | | c1 | | +| 3 | asynchronousTimer | {0 0 17 823 0 6 12} | CHOICE | c2 | | c2 | | c2 | | +| 4 | continuousTimer | {0 0 17 823 0 6 23} | SEQUENCE | c3 | | c3 | | c3 | | +| 5 | creatorIdentity | {0 0 17 823 0 6 24} | CHOICE | o? | | o | | – | | +| 6 | destinationCode | {0 0 17 823 0 6 27} | GraphicString | m? | | m | | – | | +| 7 | destinationType | {0 0 17 823 0 6 28} | CHOICE | c4? | | c4 | | – | | +| 8 | leakyBucket | {0 0 17 823 0 6 35} | SEQUENCE | c5 | | c5 | | c5 | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 10 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 11 | originationAspect | {0 0 17 823 0 6 42} | SEQUENCE | m | | m | | m | | +| 12 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c6 | | – | | +| 13 | percentage | {0 0 17 823 0 6 49} | CHOICE | c7 | | c7 | | c7 | | +| 14 | tmSurveillance | {0 0 17 823 0 6 60} | BOOLEAN | m | | m | | m | | +| 15 | trafficControlId | {0 0 17 823 0 6 61} | CHOICE | m? | | m | | – | | +| 16 | treatment | {0 0 17 823 0 6 64} | CHOICE | m | | m | | m | | + +**Table 17.4/Q.823.1 – destinationCodeControl Attribute support (continued)** + +| 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 | – | | – | | m | | | +| 12 | – | | – | | – | | | + +**Table 17.4/Q.823.1 – destinationCodeControl Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 13 | – | | – | | – | | | +| 14 | – | | – | | – | | | +| 15 | – | | – | | – | | | +| 16 | – | | – | | – | | | + +**Table 17.5/Q.823.1 – destinationCodeControl Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 17.6/Q.823.1 – destinationCodeControl Action support** + +There are no actions specified for this managed object class. + +**Table 17.7/Q.823.1 – destinationCodeControl 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | m | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | m | | | | + +**Table 17.7/Q.823.1 – destinationCodeControl Notification support (continued)** + +| 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 | | | + +**Table 17.7/Q.823.1 – destinationCodeControl Notification support (continued)** + +| 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | | | + +**Table 17.7/Q.823.1 – destinationCodeControl Notification support (continued)** + +| 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 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 | | | + +**Table 17.7/Q.823.1 – destinationCodeControl 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | 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 | | | +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 17.8/Q.823.1 – destinationCodeControl Parameter support** + +There are no parameters specified for this managed object class. + +**Table 17.9/Q.823.1 – destinationCodeControl Conditions** + +| Condition number | Condition | Reference | +|------------------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| c1 | IF 2.3/2 THEN m ELSE – | "percentagePackage and continuousTimerPackage and asynchronousTimerPackage and leakyBucketPackage are not present, and the NE supports it." | +| c2 | IF 2.3/3 THEN m ELSE – | "percentagePackage and continuousTimerPackage and leakyBucketPackage and assocOwnerDccGroupPackage are not present, and the NE supports it." | +| c3 | IF 2.3/4 THEN m ELSE – | "percentagePackage and asynchronousTimerPackage and leakyBucketPackage and assocOwnerDccGroupPackage are not present, and the NE supports it." | +| c4 | IF 2.3/7 THEN m ELSE – | "destination type is required to unambiguously identify the destinationCode." | +| c5 | IF 2.3/8 THEN m ELSE – | "percentagePackage and continuousTimerPackage and asynchronousTimerPackage and assocOwnerDccGroupPackage are not present, and the NE supports it." | +| c6 | IF 2.3/10 THEN m ELSE – | "any registered package, other than this package has been instantiated" | +| c7 | IF 2.3/11 THEN m ELSE – | "continuousTimerPackage and asynchronousTimerPackage and leakyBucketPackage and assocOwnerDccGroupPackage are not present, and the NE supports it." | + +**Table 17.10/Q.823.1 – destinationCodeControl Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------|---------------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | trafficControl-managedElement | {0 0 17 823 0 5 20} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | + +**Table 17.10/Q.823.1 – destinationCodeControl 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 | | | + +## 18 dccGroup ["Q.823"] + +**Table 18.1/Q.823.1 – dccGroup 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 | dccGroup | {0 0 17 823 0 3 13} | | | + +**Table 18.2/Q.823.1 – dccGroup 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 18.3/Q.823.1 – dccGroup Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | asynchronousTimerPackage | {0 0 17 823 0 4 8} | "percentagePackage and continuousTimerPackage and leakyBucketPackage and are not present, and the NE supports it." | c1 | | | +| 3 | continuousTimerPackage | {0 0 17 823 0 4 13} | "percentagePackage and asynchronousTimerPackage and leakyBucketPackage and are not present, and the NE supports it." | c2 | | | +| 4 | dccGroupPackage | | Mandatory | m | | | +| 5 | leakyBucketPackage | {0 0 17 823 0 4 17} | "percentagePackage and continuousTimerPackage and asynchronousTimerPackage and are not present, and the NE supports it." | c3 | | | +| 6 | "Rec. M.3100 : 1992": objectManagementNotificationsPackage | {0 0 13 3100 0 4 20} | Mandatory | m | | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c4 | | | +| 8 | percentagePackage | {0 0 17 823 0 4 19} | "continuousTimerPackage and asynchronousTimerPackage and leakyBucketPackage and are not present, and the NE supports it." | c5 | | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | + +**Table 18.4/Q.823.1 – dccGroup 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 2 | asynchronousTimer | {0 0 17 823 0 6 12} | CHOICE | c1 | | c1 | | c1 | | +| 3 | continuousTimer | {0 0 17 823 0 6 23} | SEQUENCE | c2 | | c2 | | c2 | | +| 4 | dccGroupId | {0 0 17 823 0 6 25} | CHOICE | m? | | m | | – | | +| 5 | leakyBucket | {0 0 17 823 0 6 35} | SEQUENCE | c3 | | c3 | | c3 | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 8 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c4 | | – | | +| 9 | percentage | {0 0 17 823 0 6 49} | CHOICE | c5 | | c5 | | c5 | | + +**Table 18.4/Q.823.1 – dccGroup 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 | – | | – | | – | | | + +**Table 18.5/Q.823.1 – dccGroup Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 18.6/Q.823.1 – dccGroup Action support** + +There are no actions specified for this managed object class. + +**Table 18.7/Q.823.1 – dccGroup 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | m | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | m | | | | + +**Table 18.7/Q.823.1 – dccGroup Notification support (continued)** + +| 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | + +**Table 18.7/Q.823.1 – dccGroup Notification support (continued)** + +| 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.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | | | + +**Table 18.7/Q.823.1 – dccGroup Notification support (continued)** + +| 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.4.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | 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 | | | + +**Table 18.7/Q.823.1 – dccGroup 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.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 18.8/Q.823.1 – dccGroup Parameter support** + +There are no parameters specified for this managed object class. + +**Table 18.9/Q.823.1 – dccGroup Conditions** + +| Condition number | Condition | Reference | +|------------------|------------------------|---------------------------------------------------------------------------------------------------------------------------| +| c1 | IF 3.3/2 THEN m ELSE – | "percentagePackage and continuousTimerPackage and leakyBucketPackage and are not present, and the NE supports it." | +| c2 | IF 3.3/3 THEN m ELSE – | "percentagePackage and asynchronousTimerPackage and leakyBucketPackage and are not present, and the NE supports it." | +| c3 | IF 3.3/5 THEN m ELSE – | "percentagePackage and continuousTimerPackage and asynchronousTimerPackage and are not present, and the NE supports it." | +| c4 | IF 3.3/7 THEN m ELSE – | "any registered package, other than this package has been instantiated" | +| c5 | IF 3.3/8 THEN m ELSE – | "continuousTimerPackage and asynchronousTimerPackage and leakyBucketPackage and are not present, and the NE supports it." | + +**Table 18.10/Q.823.1 – dccGroup Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-----------------------------|---------------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | dccGroup-managedElement | {0 0 17 823 0 5 6} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | + +**Table 18.10/Q.823.1 – dccGroup 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:m | | | +| | 1.6 | Delete contained objects | | c:x | | | + +## 19 exchangeCurrentData ["Q.823"] + +**Table 19.1/Q.823.1 – exchangeCurrentData 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 | exchangeCurrentData | {0 0 17 823 0 3 14} | | | + +**Table 19.2/Q.823.1 – exchangeCurrentData 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 19.3/Q.823.1 – exchangeCurrentData Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|---------------------------------------------------------------------|----------------------------------------|--------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | "Rec. M.3100 : 1992":
attributeValueChangeNotificationPackage | {0 0 13 3100 0 4 4} | "notification of attribute value change events is required" | c1 | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
availabilityStatusPackage | {2 9 3 2 4 22} | "the managed object can be scheduled" | c2 | | | +| 4 | "Rec. M.3100 : 1992":
createDeleteNotificationsPackage | {0 0 13 3100 0 4 10} | "notification of object creation and object deletion events is required" | c3 | | | +| 5 | "ITU-T Rec. Q.822 : 1994":
currentDataPkg | | Mandatory | m | | | + +**Table 19.3/Q.823.1 – exchangeCurrentData Package support (continued)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
dailyScheduling | {2 9 3 2 4 25} | "daily scheduling is required and the weekly or external scheduling package is not present" | c4 | | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
duration | {2 9 3 2 4 26} | "the scanning function is to be enabled between specified start and stop times" | c5 | | | +| 8 | exchangeCurrentDataPackage | | Mandatory | m | | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
externalScheduler | {2 9 3 2 4 27} | "reference to external scheduler is required and the daily or weekly scheduling package is not present" | c6 | | | +| 10 | "ITU-T Rec. Q.822 : 1994":
filterSuppressionPkg | {0 0 17 822 0 4 2} | "an instance supports it and the zeroSuppressionPkg is not present" | c7 | | | +| 11 | "ITU-T Rec. Q.822 : 1994":
historyRetentionPkg | {0 0 17 822 0 4 6} | "historyData objects are to be created at the end of an interval." | c8 | | | +| 12 | "ITU-T Rec. Q.822 : 1994":
maxSuppressedIntervalsPkg | {0 0 17 822 0 4 7} | "an instance supports it and at least one of zeroSuppressionPkg or filterSuppressionPkg is present." | c9 | | | +| 13 | "ITU-T Rec. Q.822 : 1994":
measurementListPkg | {0 0 17 822 0 4 8} | "an instance supports it or the object class is currentData" | c10 | | | +| 14 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervalsPkg | {0 0 17 822 0 4 9} | "suppression counts are required and the filterSuppressionPkg or the zeroSuppressionPkg is present." | c11 | | | +| 15 | "ITU-T Rec. Q.822 : 1994":
observedManagedObjectPkg | {0 0 17 822 0 4 11} | "an instance supports it." | o | | | +| 16 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c12 | | | +| 17 | "ITU-T Rec. X.739":
periodSynchronizationPackage | {2 9 2 11 4 10} | "configurable agent internal synchronization of repeating time periods is required" | c13 | | | +| 18 | "ITU-T Rec. X.739":
scannerPackage | | Mandatory | m | | | +| 19 | "ITU-T Rec. Q.822 : 1994":
scheduledPMReportPkg | {0 0 17 822 0 4 12} | "scheduled notifications are to be emitted." | c14 | | | +| 20 | "Rec. M.3100 : 1992":
stateChangeNotificationPackage | {0 0 13 3100 0 4 28} | "notification of state change event is required" | c15 | | | +| 21 | "ITU-T Rec. Q.822 : 1994":
thresholdPkg | {0 0 17 822 0 4 13} | "a Quality of Service Alarm Notification is to be emitted for threshold crossing." | c16 | | | + +**Table 19.3/Q.823.1 – exchangeCurrentData Package support (concluded)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 22 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
topPackage | | Mandatory | m | | | +| 23 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
weeklyScheduling | {2 9 3 2 4 29} | "weekly scheduling is required and the daily or external scheduling package is not present" | c17 | | | +| 24 | "ITU-T Rec. Q.822 : 1994":
zeroSuppressionPkg | {0 0 17 822 0 4 15} | "an instance supports it and the filterSuppressionPkg is not present." | c18 | | | + +**Table 19.4/Q.823.1 – exchangeCurrentData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
administrativeState | {2 9 3 2 7 31} | ENUMERATED | m | | m | | m | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
availabilityStatus | {2 9 3 2 7 33} | SET OF INTEGER | c2? | | c2 | | – | | +| 4 | callsBlockedByLoadShedding | {0 0 17 823 0 6 17} | INTEGER | m? | | – | | – | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
discriminatorConstruct | {2 9 3 2 7 56} | CHOICE | c7 | | c7 | | c7 | | +| 6 | "ITU-T Rec. Q.822 : 1994":
elapsedTime | {0 0 17 822 0 7 2} | CHOICE | m? | | m | | – | | +| 7 | "ITU-T Rec. X.739":
granularityPeriod | {2 9 2 11 7 23} | CHOICE | m | | m | | m | | +| 8 | "ITU-T Rec. Q.822 : 1994":
historyRetention | {0 0 17 822 0 7 5} | INTEGER | c8 | | c8 | | c8 | | +| 9 | incomingTraffic | {0 0 17 823 0 6 32} | INTEGER | m? | | – | | – | | +| 10 | internalTraffic | {0 0 17 823 0 6 34} | INTEGER | m? | | – | | – | | +| 11 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
intervalsOfDay | {2 9 3 2 7 57} | SET OF SEQUENCE | c4 | | c4 | | c4 | | +| 12 | "ITU-T Rec. Q.822 : 1994":
maxSuppressedIntervals | {0 0 17 822 0 7 6} | INTEGER | c9 | | c9 | | c9 | | + +**Table 19.4/Q.823.1 – exchangeCurrentData 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 | "ITU-T Rec. Q.822 : 1994":
measurementList | {0 0 17 822 0 7 7} | SET OF SEQUENCE | c10 | | c10 | | c10 | | +| 14 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 15 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervals | {0 0 17 822 0 7 9} | INTEGER | c11? | | c11 | | – | | +| 16 | "ITU-T Rec. X.738":
numericAttributeIdArray | {2 9 2 13 7 10} | SEQUENCE OF CHOICE | c14 | | c14 | | c14 | | +| 17 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 18 | "ITU-T Rec. Q.822 : 1994":
observedObjectClass | {0 0 17 822 0 7 10} | CHOICE | o? | | o | | – | | +| 19 | "ITU-T Rec. X.739":
observedObjectInstance | {2 9 2 11 7 16} | CHOICE | o? | | o | | – | | +| 20 | "ITU-T Rec. X.738":
onceReportAttributeIdList | {2 9 2 13 7 16} | SET OF CHOICE | c14 | | c14 | | c14 | | +| 21 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
operationalState | {2 9 3 2 7 35} | ENUMERATED | – | | m | | – | | +| 22 | originatingTraffic | {0 0 17 823 0 6 43} | INTEGER | m? | | – | | – | | +| 23 | outgoingTraffic | {0 0 17 823 0 6 46} | INTEGER | m? | | – | | – | | +| 24 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c12 | | – | | +| 25 | "ITU-T Rec. X.739":
periodSynchronizationTime | {2 9 2 11 7 24} | GeneralizedTime | c13 | | c13 | | c13 | | +| 26 | "ITU-T Rec. Q.822 : 1994":
reportAllAttributes | {0 0 17 822 0 7 11} | BOOLEAN | c16 | | c16 | | c16 | | +| 27 | "ITU-T Rec. X.738":
scanAttributeIdList | {2 9 2 13 7 21} | SET OF CHOICE | c14 | | c14 | | c14 | | +| 28 | "ITU-T Rec. X.739":
scannerId | {2 9 2 11 7 25} | CHOICE | m? | | m | | – | | +| 29 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
schedulerName | {2 9 3 2 7 67} | CHOICE | c6? | | c6 | | – | | +| 30 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
startTime | {2 9 3 2 7 68} | GeneralizedTime | c5 | | c5 | | c5 | | + +**Table 19.4/Q.823.1 – exchangeCurrentData 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 | +| 31 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stopTime | {2 9 3 2 7 69} | CHOICE | c5 | | c5 | | c5 | | +| 32 | "ITU-T Rec. Q.822 : 1994": suppressAdditionalThresholds | {0 0 17 822 0 7 13} | BOOLEAN | c16 | | c16 | | c16 | | +| 33 | "ITU-T Rec. Q.822 : 1994": suspectIntervalFlag | {0 0 17 822 0 7 14} | BOOLEAN | m? | | m | | – | | +| 34 | terminatingTraffic | {0 0 17 823 0 6 56} | INTEGER | m? | | – | | – | | +| 35 | "ITU-T Rec. Q.822 : 1994": thresholdDataInstance | {0 0 17 822 0 7 16} | SET OF CHOICE | c16 | | c16 | | c16 | | +| 36 | transitTraffic | {0 0 17 823 0 6 63} | INTEGER | m? | | – | | – | | +| 37 | "Rec. X.721 ISO/IEC 10165-2 : 1992": weekMask | {2 9 3 2 7 71} | SET OF SEQUENCE | c17 | | c17 | | c17 | | + +**Table 19.4/Q.823.1 – exchangeCurrentData Attribute support (continued)** + +| 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 | c4 | | c4 | | c4 | | | +| 12 | – | | – | | – | | | +| 13 | – | | – | | – | | | +| 14 | – | | – | | – | | | +| 15 | – | | – | | – | | | +| 16 | – | | – | | – | | | +| 17 | – | | – | | – | | | +| 18 | – | | – | | – | | | +| 19 | – | | – | | – | | | + +**Table 19.4/Q.823.1 – exchangeCurrentData Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 20 | c14 | | c14 | | – | | | +| 21 | – | | – | | – | | | +| 22 | – | | – | | – | | | +| 23 | – | | – | | – | | | +| 24 | – | | – | | – | | | +| 25 | – | | – | | – | | | +| 26 | – | | – | | – | | | +| 27 | c14 | | c14 | | – | | | +| 28 | – | | – | | – | | | +| 29 | – | | – | | – | | | +| 30 | – | | – | | – | | | +| 31 | – | | – | | c5 | | | +| 32 | – | | – | | – | | | +| 33 | – | | – | | m | | | +| 34 | – | | – | | – | | | +| 35 | c16 | | c16 | | – | | | +| 36 | – | | – | | – | | | +| 37 | c17 | | c17 | | c17 | | | + +**Table 19.5/Q.823.1 – exchangeCurrentData Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 19.6/Q.823.1 – exchangeCurrentData Action support** + +There are no actions specified for this managed object class. + +**Table 19.7/Q.823.1 – exchangeCurrentData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | c1 | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | c3 | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | c3 | | | | + +**Table 19.7/Q.823.1 – exchangeCurrentData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": qualityofServiceAlarm | {2 9 3 2 10 11} | | c16 | | | "Rec. Q.821: 1992":
correlatedRecordNameParameter
"Rec. Q.821: 1992":
logRecordIdParameter
"Rec. Q.821: 1992":
suspectObjectListParameter | +| 5 | "ITU-T Rec. X.738": scanReport | {2 9 2 13 10 2} | | c14 | | | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stateChange | {2 9 3 2 10 14} | | c15 | | | | + +**Table 19.7/Q.823.1 – exchangeCurrentData Notification support (continued)** + +| 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 | c1 | | | +| | 1.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 1.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | c: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 | c:m | | | +| | 1.1.3.1 | attributeID | – | CHOICE | c:m | | | +| | 1.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.2 | | | +| | 1.1.3.1.2 | localForm | – | INTEGER | c:o.2 | | | +| | 1.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | c:o | | | +| | 1.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | c:m | | | +| | 1.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | + +**Table 19.7/Q.823.1 – exchangeCurrentData Notification support (continued)** + +| 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 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 1.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 1.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | c3 | | | +| | 2.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 2.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c: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 | c:o | | | +| | 2.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | | | + +**Table 19.7/Q.823.1 – exchangeCurrentData Notification support (continued)** + +| 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.4.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 2.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 2.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | c3 | | | +| | 3.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 3.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c: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 | c:o | | | +| | 3.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | | | + +**Table 19.7/Q.823.1 – exchangeCurrentData Notification support (continued)** + +| 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.4.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 3.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 3.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 3.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 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 | c!6 | | | +| | 4.1.1 | probableCause | {2 9 3 2 7 18} | CHOICE | c:m | | | +| | 4.1.1.1 | globalValue | – | OBJECT IDENTIFIER | c:o.8 | | | +| | 4.1.1.2 | localValue | – | INTEGER | c:o.8 | | | +| | 4.1.2 | specificProblems | {2 9 3 2 7 27} | SET OF CHOICE | c:o | | | +| | 4.1.2.1 | OBJECT IDENTIFIER | – | OBJECT IDENTIFIER | c:o.9 | | | +| | 4.1.2.2 | INTEGER | – | INTEGER | c:o.9 | | | +| | 4.1.3 | perceivedSeverity | {2 9 3 2 7 17} | ENUMERATED | c:m | | | +| | 4.1.4 | backedUpStatus | {2 9 3 2 7 11} | BOOLEAN | c:o | | | +| | 4.1.5 | backUpObject | {2 9 3 2 7 40} | CHOICE | c:o | | | +| | 4.1.5.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.5.2 | nonSpecificForm | – | OCTET STRING | c:o.10 | | | +| | 4.1.5.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.6 | trendIndication | {2 9 3 2 7 30} | ENUMERATED | c:o | | | +| | 4.1.7 | thresholdInfo | {2 9 3 2 7 29} | SEQUENCE | c:o | | | +| | 4.1.7.1 | triggeredThreshold | – | CHOICE | c:m | | | +| | 4.1.7.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.11 | | | +| | 4.1.7.1.2 | localForm | – | INTEGER | c:o.11 | | | + +**Table 19.7/Q.823.1 – exchangeCurrentData Notification support (continued)** + +| 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.2 | observedValue | – | CHOICE | c:m | | | +| | 4.1.7.2.1 | integer | – | INTEGER | c:o.12 | | | +| | 4.1.7.2.2 | real | – | REAL | c:o.12 | | | +| | 4.1.7.3 | thresholdLevel | – | CHOICE | c:o | | | +| | 4.1.7.3.1 | up | – | SEQUENCE | c:o.13 | | | +| | 4.1.7.3.1.1 | high | – | CHOICE | c:m | | | +| | 4.1.7.3.1.1.1 | integer | – | INTEGER | c:o.14 | | | +| | 4.1.7.3.1.1.2 | real | – | REAL | c:o.14 | | | +| | 4.1.7.3.1.2 | low | – | CHOICE | c:o | | | +| | 4.1.7.3.1.2.1 | integer | – | INTEGER | c:o.15 | | | +| | 4.1.7.3.1.2.2 | real | – | REAL | c:o.15 | | | +| | 4.1.7.3.2 | down | – | SEQUENCE | c:o.13 | | | +| | 4.1.7.3.2.1 | high | – | CHOICE | c:m | | | +| | 4.1.7.3.2.1.1 | integer | – | INTEGER | c:o.16 | | | +| | 4.1.7.3.2.1.2 | real | – | REAL | c:o.16 | | | +| | 4.1.7.3.2.2 | low | – | CHOICE | c:m | | | +| | 4.1.7.3.2.2.1 | integer | – | INTEGER | c:o.17 | | | +| | 4.1.7.3.2.2.2 | real | – | REAL | c:o.17 | | | +| | 4.1.7.4 | armTime | – | GeneralizedTime | c:o | | | +| | 4.1.8 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 4.1.9 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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.18 | | | +| | 4.1.9.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.9.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.9.2.2 | nonSpecificForm | – | OCTET STRING | c:o.18 | | | +| | 4.1.9.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.18 | | | +| | 4.1.9.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.9.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.10 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | c:o | | | +| | 4.1.10.1 | attributeID | – | CHOICE | c:m | | | +| | 4.1.10.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.19 | | | + +**Table 19.7/Q.823.1 – exchangeCurrentData Notification support (continued)** + +| 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.10.1.2 | localForm | – | INTEGER | c:o.19 | | | +| | 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 | c:o | | | +| | 4.1.11.1 | attributeId | – | CHOICE | c:m | | | +| | 4.1.11.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.20 | | | +| | 4.1.11.1.2 | localForm | – | INTEGER | c:o.20 | | | +| | 4.1.11.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 4.1.12 | proposedRepairActions | {2 9 3 2 7 19} | SET OF CHOICE | c:o | | | +| | 4.1.12.1 | OBJECT IDENTIFIER | – | OBJECT IDENTIFIER | c:o.21 | | | +| | 4.1.12.2 | INTEGER | – | INTEGER | c:o.21 | | | +| | 4.1.13 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 4.1.14 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | ScanReportInformation | | Information Syntax SEQUENCE | c14 | | | +| | 5.1.1 | scanInitiationTime | {2 9 2 13 7 22} | GeneralizedTime | c:o | | | +| | 5.1.2 | onceReportAttributeList | {2 9 2 13 7 17} | SET OF SEQUENCE | c:o | | | +| | 5.1.2.1 | attributeId | – | CHOICE | c:m | | | +| | 5.1.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.22 | | | +| | 5.1.2.1.2 | localForm | – | INTEGER | c:o.22 | | | +| | 5.1.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 5.1.3 | observationScanList | {2 9 2 13 7 15} | SET OF SEQUENCE | c:m | | | +| | 5.1.3.1 | observedObjectInstance | – | CHOICE | c:o | | | +| | 5.1.3.1.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.23 | | | +| | 5.1.3.1.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | + +**Table 19.7/Q.823.1 – exchangeCurrentData Notification support (continued)** + +| 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.3.1.1.2 | attributeValue | – | ANY | c:m | | | +| | 5.1.3.1.2 | nonSpecificForm | – | OCTET STRING | c:o.23 | | | +| | 5.1.3.1.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.23 | | | +| | 5.1.3.1.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.3.1.3.2 | attributeValue | – | ANY | c:m | | | +| | 5.1.3.2 | attributeMeasureList | – | SET OF SEQUENCE | c:o | | | +| | 5.1.3.2.1 | attributeId | – | CHOICE | c:m | | | +| | 5.1.3.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.24 | | | +| | 5.1.3.2.1.2 | localForm | – | INTEGER | c:o.24 | | | +| | 5.1.3.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:o | | | +| | 5.1.3.2.3 | timeStamp | – | CHOICE | c:o | | | +| | 5.1.3.2.3.1 | days | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.2 | hours | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.3 | minutes | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.4 | seconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.5 | milliSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.6 | microSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.7 | nanoSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.8 | picoSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.4 | suspectFlag | – | BOOLEAN | c:o | | | +| | 5.1.3.3 | numericValueArray | – | SEQUENCE OF CHOICE | c:o | | | +| | 5.1.3.3.1 | missingData | – | NULL | c:o.26 | | | +| | 5.1.3.3.2 | valueOnly | – | CHOICE | c:o.26 | | | +| | 5.1.3.3.2.1 | integer | – | INTEGER | c:o.27 | | | +| | 5.1.3.3.2.2 | real | – | REAL | c:o.27 | | | +| | 5.1.3.3.3 | qualifiedValue | – | SEQUENCE | c:o.26 | | | +| | 5.1.3.3.3.1 | value | – | CHOICE | c:m | | | +| | 5.1.3.3.3.1.1 | integer | – | INTEGER | c:o.28 | | | +| | 5.1.3.3.3.1.2 | real | – | REAL | c:o.28 | | | +| | 5.1.3.3.3.2 | timeStamp | – | CHOICE | c:o | | | +| | 5.1.3.3.3.2.1 | days | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.2 | hours | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.3 | minutes | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.4 | seconds | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.5 | milliSeconds | – | INTEGER | c:o.29 | | | + +**Table 19.7/Q.823.1 – exchangeCurrentData Notification support (continued)** + +| 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.3.3.3.2.6 | microSeconds | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.7 | nanoSeconds | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.8 | picoSeconds | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.3 | suspectFlag | – | BOOLEAN | c:o | | | +| | 5.1.4 | incompleteScan | {2 9 2 13 7 30} | INTEGER | c:o | | | +| | 5.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 5.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 5.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 5.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | +| 6 | 6.1 | StateChangeInfo | | Information Syntax
SEQUENCE | c!5 | | | +| | 6.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 6.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | c:o | | | +| | 6.1.2.1 | globalForm | – | OBJECT IDENTIFIER | c:o.30 | | | +| | 6.1.2.2 | localForm | – | INTEGER | c:o.30 | | | +| | 6.1.3 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | c:m | | | +| | 6.1.3.1 | attributeID | – | CHOICE | c:m | | | +| | 6.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.31 | | | +| | 6.1.3.1.2 | localForm | – | INTEGER | c:o.31 | | | +| | 6.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | c:o | | | +| | 6.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | c:m | | | +| | 6.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 6.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c:o | | | +| | 6.1.5.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 6.1.5.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 6.1.5.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.32 | | | +| | 6.1.5.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 6.1.5.2.2 | nonSpecificForm | – | OCTET STRING | c:o.32 | | | + +**Table 19.7/Q.823.1 – exchangeCurrentData 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 | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|-----------------------------|--------|---------|------------------------| +| | 6.1.5.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.32 | | | +| | 6.1.5.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 6.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 6.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 6.1.7.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.7.2 | significance | – | BOOLEAN | c:o | | | +| | 6.1.7.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 19.8/Q.823.1 – exchangeCurrentData Parameter support** + +| Index | Parameter template label | Value of object identifier for parameter | Constraints and values | Status | Support | Additional information | +|-------|--------------------------------------------------|------------------------------------------|----------------------------------|--------|---------|------------------------| +| 1 | "Rec. Q.821:1992": correlatedRecordNameParameter | {0 0 17 821 0 5 2} | EVENT-INFO qualityofServiceAlarm | c16 | | | +| 2 | "Rec. Q.821:1992": logRecordIdParameter | {0 0 17 821 0 5 1} | EVENT-INFO qualityofServiceAlarm | c16 | | | +| 3 | "Rec. Q.821:1992": suspectObjectListParameter | {0 0 17 821 0 5 3} | EVENT-INFO qualityofServiceAlarm | c16 | | | + +**Table 19.9/Q.823.1 – exchangeCurrentData Conditions** + +| Condition number | Condition | Reference | +|------------------|-------------------------|---------------------------------------------------------------------------------------------------------| +| c1 | IF 4.3/2 THEN m ELSE – | "notification of attribute value change events is required" | +| c2 | IF 4.3/3 THEN m ELSE – | "the managed object can be scheduled" | +| c3 | IF 4.3/4 THEN m ELSE – | "notification of object creation and object deletion events is required" | +| c4 | IF 4.3/6 THEN m ELSE – | "daily scheduling is required and the weekly or external scheduling package is not present" | +| c5 | IF 4.3/7 THEN m ELSE – | "the scanning function is to be enabled between specified start and stop times" | +| c6 | IF 4.3/9 THEN m ELSE – | "reference to external scheduler is required and the daily or weekly scheduling package is not present" | +| c7 | IF 4.3/10 THEN m ELSE – | "an instance supports it and the zeroSuppressionPkg is not present" | +| c8 | IF 4.3/11 THEN m ELSE – | "historyData objects are to be created at the end of an interval." | + +**Table 19.9/Q.823.1 – exchangeCurrentData Conditions (concluded)** + +| Condition number | Condition | Reference | +|------------------|-------------------------|------------------------------------------------------------------------------------------------------| +| c9 | IF 4.3/12 THEN m ELSE – | "an instance supports it and at least one of zeroSuppressionPkg or filterSuppressionPkg is present." | +| c10 | IF 4.3/13 THEN m ELSE – | "an instance supports it or the object class is currentData" | +| c11 | IF 4.3/14 THEN m ELSE – | "suppression counts are required and the filterSuppressionPkg or the zeroSuppressionPkg is present." | +| c12 | IF 4.3/16 THEN m ELSE – | "any registered package, other than this package has been instantiated" | +| c13 | IF 4.3/17 THEN m ELSE – | "configurable agent internal synchronization of repeating time periods is required" | +| c14 | IF 4.3/19 THEN m ELSE – | "scheduled notifications are to be emitted." | +| c15 | IF 4.3/20 THEN m ELSE – | "notification of state change event is required" | +| c16 | IF 4.3/21 THEN m ELSE – | "a Quality of Service Alarm Notification is to be emitted for threshold crossing." | +| c17 | IF 4.3/23 THEN m ELSE – | "weekly scheduling is required and the daily or external scheduling package is not present" | +| c18 | IF 4.3/24 THEN m ELSE – | "an instance supports it and the filterSuppressionPkg is not present." | + +**Table 19.10/Q.823.1 – exchangeCurrentData Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|----------------------------------------------------------|---------------------------------------------|---------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "ITU-T Rec. X.738":
conflictingPackagesScanner-system | {2 9 2 13 6 9} | Superior class:
"Rec. X.721 ISO/IEC 10165-2 : 1992":
system
AND SUBCLASSES | o | | | + +**Table 19.10/Q.823.1 – exchangeCurrentData 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:m | | | +| | 1.6 | Delete contained objects | | c:x | | | + +## **20 exchangeHistoryData ["Q.823"]** + +**Table 20.1/Q.823.1 – exchangeHistoryData 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 | exchangeHistoryData | {0 0 17 823 0 3 15} | | | + +**Table 20.2/Q.823.1 – exchangeHistoryData 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 20.3/Q.823.1 – exchangeHistoryData Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|-----------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | exchangeHistoryDataPackage | | Mandatory | m | | | +| 3 | "ITU-T Rec. Q.822 : 1994":
historyDataMeasurementListPkg | {0 0 17 822 0 4 4} | "the measurementListPkg is present in the corresponding currentData instance" | c1 | | | +| 4 | "ITU-T Rec. Q.822 : 1994":
historyDataPkg | | Mandatory | m | | | +| 5 | "ITU-T Rec. Q.822 : 1994":
historyDataSuspectIntervalFlagPkg | {0 0 17 822 0 4 5} | "an instance supports it." | o | | | +| 6 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervalsPkg | {0 0 17 822 0 4 9} | "this package is present in the corresponding currentData instance." | c2 | | | +| 7 | "ITU-T Rec. Q.822 : 1994":
objectDeleteNotificationPkg | {0 0 17 822 0 4 10} | "an instance supports it." | o | | | + +**Table 20.3/Q.823.1 – exchangeHistoryData Package support (concluded)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|-----------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------|--------|---------|------------------------| +| 8 | "ITU-T Rec. Q.822 : 1994":
observedManagedObject Pkg | {0 0 17 822 0 4 11} | "this package is present in the corresponding currentData instance." | c2 | | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c3 | | | +| 10 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
topPackage | | Mandatory | m | | | + +**Table 20.4/Q.823.1 – exchangeHistoryData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 2 | callsBlockedByLoadShedding | {0 0 17 823 0 6 17} | INTEGER | m? | | m | | – | | +| 3 | "ITU-T Rec. X.739":
granularityPeriod | {2 9 2 11 7 23} | CHOICE | m? | | m | | – | | +| 4 | "ITU-T Rec. Q.822 : 1994":
historyDataId | {0 0 17 822 0 7 4} | CHOICE | m? | | m | | – | | +| 5 | incomingTraffic | {0 0 17 823 0 6 32} | INTEGER | m? | | m | | – | | +| 6 | internalTraffic | {0 0 17 823 0 6 34} | INTEGER | m? | | m | | – | | +| 7 | "ITU-T Rec. Q.822 : 1994":
measurementList | {0 0 17 822 0 7 7} | SET OF SEQUENCE | c1? | | c1 | | – | | +| 8 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 9 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervals | {0 0 17 822 0 7 9} | INTEGER | c2? | | c2 | | – | | +| 10 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 11 | "ITU-T Rec. Q.822 : 1994":
observedObjectClass | {0 0 17 822 0 7 10} | CHOICE | c2? | | c2 | | – | | +| 12 | "ITU-T Rec. X.739":
observedObjectInstance | {2 9 2 11 7 16} | CHOICE | c2? | | c2 | | – | | +| 13 | originatingTraffic | {0 0 17 823 0 6 43} | INTEGER | m? | | m | | – | | + +**Table 20.4/Q.823.1 – exchangeHistoryData 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 | outgoingTraffic | {0 0 17 823 0 6 46} | INTEGER | m? | | m | | – | | +| 15 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c3 | | – | | +| 16 | "ITU-T Rec. Q.822 : 1994": periodEndTime | {0 0 17 822 0 7 12} | GeneralizedTime | m? | | m | | – | | +| 17 | "ITU-T Rec. Q.822 : 1994": suspectIntervalFlag | {0 0 17 822 0 7 14} | BOOLEAN | o? | | o | | – | | +| 18 | terminatingTraffic | {0 0 17 823 0 6 56} | INTEGER | m? | | m | | – | | +| 19 | transitTraffic | {0 0 17 823 0 6 63} | INTEGER | m? | | m | | – | | + +**Table 20.4/Q.823.1 – exchangeHistoryData 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 | – | | – | | – | | | + +**Table 20.5/Q.823.1 – exchangeHistoryData Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 20.6/Q.823.1 – exchangeHistoryData Action support** + +There are no actions specified for this managed object class. + +**Table 20.7/Q.823.1 – exchangeHistoryData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | o | | | | + +**Table 20.7/Q.823.1 – exchangeHistoryData Notification support (continued)** + +| 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 | ObjectInfo | | Information Syntax SEQUENCE | o | | | +| | 1.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 1.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c:o | | | +| | 1.1.2.1 | attributeId | – | CHOICE | c:m | | | +| | 1.1.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.1 | | | +| | 1.1.2.1.2 | localForm | – | INTEGER | c:o.1 | | | +| | 1.1.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 1.1.3 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 1.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c:o | | | +| | 1.1.4.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 1.1.4.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 1.1.4.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.2 | | | +| | 1.1.4.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.4.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 1.1.4.2.2 | nonSpecificForm | – | OCTET STRING | c:o.2 | | | +| | 1.1.4.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.2 | | | +| | 1.1.4.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 1.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | + +**Table 20.7/Q.823.1 – exchangeHistoryData 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.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 1.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 1.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 20.8/Q.823.1 – exchangeHistoryData Parameter support** + +There are no parameters specified for this managed object class. + +**Table 20.9/Q.823.1 – exchangeHistoryData Conditions** + +| Condition number | Condition | Reference | +|------------------|------------------------|-------------------------------------------------------------------------------| +| c1 | IF 5.3/3 THEN m ELSE – | "the measurementListPkg is present in the corresponding currentData instance" | +| c2 | IF 5.3/6 THEN m ELSE – | "this package is present in the corresponding currentData instance." | +| c3 | IF 5.3/9 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table 20.10/Q.823.1 – exchangeHistoryData Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------------------------------|---------------------------------------------|-----------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | exchangeHistoryData-managedElement | {0 0 17 823 0 5 8} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | +| 2 | "ITU-T Rec. Q.822 : 1994":
historyData-currentData | {0 0 17 822 0 6 1} | Superior class:
"ITU-T Rec. Q.822 :
1994":
currentData
AND SUBCLASSES | o | | | + +**Table 20.10/Q.823.1 – exchangeHistoryData 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:x | | | +| | 1.6 | Delete contained objects | | c:m | | | +| 2 | 2.1 | Create support | | – | | | +| | 2.2 | Create with reference object | | – | | | +| | 2.3 | Create with automatic instance naming | | – | | | +| | 2.4 | Delete support | | c:m | | | +| | 2.5 | Delete only if no contained objects | | c:x | | | +| | 2.6 | Delete contained objects | | c:m | | | + +## 21 htrDestination ["Q.823"] + +**Table 21.1/Q.823.1 – htrDestination 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 | htrDestination | {0 0 17 823 0 3 16} | | | + +**Table 21.2/Q.823.1 – htrDestination 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 21.3/Q.823.1 – htrDestination Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|-----------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | creatorPackage | {0 0 17 823 0 4 14} | Mandatory | m | | | +| 3 | destinationTypePackage | {0 0 17 823 0 4 16} | "destination type is required to unambiguously identify the destination code" | c1 | | | +| 4 | htrDestinationPackage | | Mandatory | m | | | + +**Table 21.3/Q.823.1 – htrDestination Package support (concluded)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------|--------|---------|------------------------| +| 5 | "Rec. M.3100 : 1992": objectManagementNotificationsPackage | {0 0 13 3100 0 4 20} | Mandatory | m | | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c2 | | | +| 7 | "Rec. M.3100 : 1992": stateChangeNotificationPackage | {0 0 13 3100 0 4 28} | Mandatory | m | | | +| 8 | tmCircuitEndPointSubgroupListPackage | {0 0 17 823 0 4 22} | "the htrDestination is correlated with tmCircuitEndPointSubgroups" | c3 | | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | + +**Table 21.4/Q.823.1 – htrDestination 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": administrativeState | {2 9 3 2 7 31} | ENUMERATED | m | | m | | m | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 3 | creatorIdentity | {0 0 17 823 0 6 24} | CHOICE | m? | | m | | – | | +| 4 | destinationCode | {0 0 17 823 0 6 27} | GraphicString | m? | | m | | – | | +| 5 | destinationType | {0 0 17 823 0 6 28} | CHOICE | c1? | | c1 | | – | | +| 6 | htrDestinationId | {0 0 17 823 0 6 30} | CHOICE | m? | | m | | – | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 8 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c2 | | – | | +| 10 | tmCircuitEndPointSubgroupList | {0 0 17 823 0 6 59} | SET OF CHOICE | c3 | | c3 | | c3 | | + +**Table 21.4/Q.823.1 – htrDestination 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 | c3 | | c3 | | – | | | + +**Table 21.5/Q.823.1 – htrDestination Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 21.6/Q.823.1 – htrDestination Action support** + +There are no actions specified for this managed object class. + +**Table 21.7/Q.823.1 – htrDestination 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | m | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | m | | | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stateChange | {2 9 3 2 10 14} | | m | | | | + +**Table 21.7/Q.823.1 – htrDestination Notification support (continued)** + +| 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | | | + +**Table 21.7/Q.823.1 – htrDestination Notification support (continued)** + +| Index | Subindex | Notification field name label | Value of object identifier of attribute type associated with field | Constraints and values | Status | Support | Additional information | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|---------------------------------------|--------|---------|------------------------| +| 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 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 | | | + +**Table 21.7/Q.823.1 – htrDestination Notification support (continued)** + +| 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | 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 | | | +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | +| 4 | 4.1 | StateChangeInfo | | Information Syntax
SEQUENCE | m | | | +| | 4.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | o | | | +| | 4.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | o | | | +| | 4.1.2.1 | globalForm | – | OBJECT IDENTIFIER | c:o.8 | | | +| | 4.1.2.2 | localForm | – | INTEGER | c:o.8 | | | +| | 4.1.3 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | m | | | +| | 4.1.3.1 | attributeID | – | CHOICE | m | | | +| | 4.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | o.9 | | | +| | 4.1.3.1.2 | localForm | – | INTEGER | o.9 | | | + +**Table 21.7/Q.823.1 – htrDestination 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.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | o | | | +| | 4.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | m | | | +| | 4.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | o | | | +| | 4.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | o | | | +| | 4.1.5.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 4.1.5.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 4.1.5.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.5.2.2 | nonSpecificForm | – | OCTET STRING | c:o.10 | | | +| | 4.1.5.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | o | | | +| | 4.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | o | | | +| | 4.1.7.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.7.2 | significance | – | BOOLEAN | c:o | | | +| | 4.1.7.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 21.8/Q.823.1 – htrDestination Parameter support** + +There are no parameters specified for this managed object class. + +**Table 21.9/Q.823.1 – htrDestination Conditions** + +| Condition number | Condition | Reference | +|------------------|------------------------|-------------------------------------------------------------------------------| +| c1 | IF 6.3/3 THEN m ELSE – | "destination type is required to unambiguously identify the destination code" | +| c2 | IF 6.3/6 THEN m ELSE – | "any registered package, other than this package has been instantiated" | +| c3 | IF 6.3/8 THEN m ELSE – | "the htrDestination is correlated with tmCircuitEndPointSubgroups" | + +**Table 21.10/Q.823.1 – htrDestination Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-----------------------------------|---------------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | autoHTRDestination-managedElement | {0 0 17 823 0 5 10} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | +| 2 | htrDestination-managedElement | {0 0 17 823 0 5 9} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | + +**Table 21.10/Q.823.1 – htrDestination 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 | | – | | | +| | 1.5 | Delete only if no contained objects | | – | | | +| | 1.6 | Delete contained objects | | – | | | +| 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 | | | + +## 22 observedDestination ["Q.823"] + +**Table 22.1/Q.823.1 – observedDestination 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 | observedDestination | {0 0 17 823 0 3 17} | | | + +**Table 22.2/Q.823.1 – observedDestination 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 22.3/Q.823.1 – observedDestination Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------|----------------------------------------|----------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | creatorPackage | {0 0 17 823 0 4 14} | "if an instance supports it" | c1 | | | +| 3 | destinationTypePackage | {0 0 17 823 0 4 16} | "destination type is required to unambiguously identify the destination code" | c2 | | | +| 4 | "Rec. M.3100 : 1992": objectManagementNotificationsPackage | {0 0 13 3100 0 4 20} | Mandatory | m | | | +| 5 | observedDestinationPackage | | Mandatory | m | | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c3 | | | +| 7 | tmCircuitEndPointSubgroupListPackage | {0 0 17 823 0 4 22} | "a destinations performances should be monitored in correlation with certain tmCircuitEndPointSubgroups" | c4 | | | +| 8 | "Rec. X.721 ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | + +**Table 22.4/Q.823.1 – observedDestination 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 2 | creatorIdentity | {0 0 17 823 0 6 24} | CHOICE | c1? | | c1 | | – | | +| 3 | destinationCode | {0 0 17 823 0 6 27} | GraphicString | m? | | m | | – | | +| 4 | destinationType | {0 0 17 823 0 6 28} | CHOICE | c2? | | c2 | | – | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 7 | observedDestinationId | {0 0 17 823 0 6 41} | CHOICE | m? | | m | | – | | +| 8 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c3 | | – | | +| 9 | tmCircuitEndPointSubgroupList | {0 0 17 823 0 6 59} | SET OF CHOICE | c4 | | c4 | | c4 | | +| 10 | tmSurveillance | {0 0 17 823 0 6 60} | BOOLEAN | m | | m | | m | | + +**Table 22.4/Q.823.1 – observedDestination 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 | c4 | | c4 | | – | | | +| 10 | – | | – | | – | | | + +**Table 22.5/Q.823.1 – observedDestination Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 22.6/Q.823.1 – observedDestination Action support** + +There are no actions specified for this managed object class. + +**Table 22.7/Q.823.1 – observedDestination 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | m | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | m | | | | + +**Table 22.7/Q.823.1 – observedDestination Notification support (continued)** + +| 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | | | + +**Table 22.7/Q.823.1 – observedDestination Notification support (continued)** + +| Index | Subindex | Notification field name label | Value of object identifier of attribute type associated with field | Constraints and values | Status | Support | Additional information | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|---------------------------------------|--------|---------|------------------------| +| 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 | attributeType | – | OBJECT
IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT
IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 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 | | | + +**Table 22.7/Q.823.1 – observedDestination 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | 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 | | | +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 22.8/Q.823.1 – observedDestination Parameter support** + +There are no parameters specified for this managed object class. + +**Table 22.9/Q.823.1 – observedDestination Conditions** + +| Condition number | Condition | Reference | +|------------------|------------------------|-------------------------------------------------------------------------------------------------| +| c1 | IF 7.3/2 THEN m ELSE – | "if an instance supports it" | +| c2 | IF 7.3/3 THEN m ELSE – | "destination type is required to unambiguously identify the destination code" | +| c3 | IF 7.3/6 THEN m ELSE – | "any registered package, other than this package has been instantiated" | +| c4 | IF 7.3/7 THEN m ELSE – | "a destinationsperformanceshouldbemonitoredincorrelationwithcertaintmCircuit EndPointSubgroups" | + +**Table 22.10/Q.823.1 – observedDestination Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------|---------------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | observedDestination-managedElement | {0 0 17 823 0 5 11} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | + +**Table 22.10/Q.823.1 – observedDestination 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 | | | + +## 23 observedDestinationCurrentData ["Q.823"] + +**Table 23.1/Q.823.1 – observedDestinationCurrentData 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 | observedDestinationCurrent Data | {0 0 17 823 0 3 18} | | | + +**Table 23.2/Q.823.1 – observedDestinationCurrentData 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 23.3/Q.823.1 – observedDestinationCurrentData Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|---------------------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | "Rec. M.3100 : 1992":
attributeValueChangeNotificationPackage | {0 0 13 3100 0 4 4} | "notification of attribute value change events is required" | c1 | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
availabilityStatusPackage | {2 9 3 2 4 22} | "the managed object can be scheduled" | c2 | | | +| 4 | callsAffectedByDccPackage | {0 0 17 823 0 4 9} | "an instance supports it" | o | | | +| 5 | "Rec. M.3100 : 1992":
createDeleteNotificationsPackage | {0 0 13 3100 0 4 10} | "notification of object creation and object deletion events is required" | c3 | | | +| 6 | "ITU-T Rec. Q.822 : 1994":
currentDataPkg | | Mandatory | m | | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
dailyScheduling | {2 9 3 2 4 25} | "daily scheduling is required and the weekly or external scheduling package is not present" | c4 | | | +| 8 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
duration | {2 9 3 2 4 26} | "the scanning function is to be enabled between specified start and stop times" | c5 | | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
externalScheduler | {2 9 3 2 4 27} | "reference to external scheduler is required and the daily or weekly scheduling package is not present" | c6 | | | +| 10 | "ITU-T Rec. Q.822 : 1994":
filterSuppressionPkg | {0 0 17 822 0 4 2} | "an instance supports it and the zeroSuppressionPkg is not present" | c7 | | | +| 11 | "ITU-T Rec. Q.822 : 1994":
historyRetentionPkg | {0 0 17 822 0 4 6} | "historyData objects are to be created at the end of an interval." | c8 | | | +| 12 | "ITU-T Rec. Q.822 : 1994":
maxSuppressedIntervalsPkg | {0 0 17 822 0 4 7} | "an instance supports it and at least one of zeroSuppressionPkg or filterSuppressionPkg is present." | c9 | | | +| 13 | "ITU-T Rec. Q.822 : 1994":
measurementListPkg | {0 0 17 822 0 4 8} | "an instance supports it or the object class is currentData" | c10 | | | +| 14 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervalsPkg | {0 0 17 822 0 4 9} | "suppression counts are required and the filterSuppressionPkg or the zeroSuppressionPkg is present." | c11 | | | +| 15 | observedDestinationCurrentDataPackage | | Mandatory | m | | | +| 16 | "ITU-T Rec. Q.822 : 1994":
observedManagedObjectPkg | {0 0 17 822 0 4 11} | "an instance supports it." | o | | | + +**Table 23.3/Q.823.1 – observedDestinationCurrentData Package support (concluded)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 17 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c12 | | | +| 18 | "ITU-T Rec. X.739":
periodSynchronizationPackage | {2 9 2 11 4 10} | "configurable agent internal synchronization of repeating time periods is required" | c13 | | | +| 19 | "ITU-T Rec. X.739":
scannerPackage | | Mandatory | m | | | +| 20 | "ITU-T Rec. Q.822 : 1994":
scheduledPMReportPkg | {0 0 17 822 0 4 12} | "scheduled notifications are to be emitted." | c14 | | | +| 21 | "Rec. M.3100 : 1992":
stateChangeNotificationPackage | {0 0 13 3100 0 4 28} | "notification of state change event is required" | c15 | | | +| 22 | "ITU-T Rec. Q.822 : 1994":
thresholdPkg | {0 0 17 822 0 4 13} | "a Quality of Service Alarm Notification is to be emitted for threshold crossing." | c16 | | | +| 23 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
topPackage | | Mandatory | m | | | +| 24 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
weeklyScheduling | {2 9 3 2 4 29} | "weekly scheduling is required and the daily or external scheduling package is not present" | c17 | | | +| 25 | "ITU-T Rec. Q.822 : 1994":
zeroSuppressionPkg | {0 0 17 822 0 4 15} | "an instance supports it and the filterSuppressionPkg is not present." | c18 | | | + +**Table 23.4/Q.823.1 – observedDestinationCurrentData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
administrativeState | {2 9 3 2 7 31} | ENUMERATED | m | | m | | m | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 3 | answeredOutgoingSeizures | {0 0 17 823 0 6 10} | INTEGER | m? | | – | | – | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
availabilityStatus | {2 9 3 2 7 33} | SET OF INTEGER | c2? | | c2 | | – | | +| 5 | bids | {0 0 17 823 0 6 14} | INTEGER | m? | | – | | – | | +| 6 | callsAffectedByDcc | {0 0 17 823 0 6 15} | INTEGER | o? | | – | | – | | + +**Table 23.4/Q.823.1 – observedDestinationCurrentData 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 | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992": discriminatorConstruct | {2 9 3 2 7 56} | CHOICE | c7 | | c7 | | c7 | | +| 8 | "ITU-T Rec. Q.822 : 1994": elapsedTime | {0 0 17 822 0 7 2} | CHOICE | m? | | m | | – | | +| 9 | "ITU-T Rec. X.739": granularityPeriod | {2 9 2 11 7 23} | CHOICE | m | | m | | m | | +| 10 | "ITU-T Rec. Q.822 : 1994": historyRetention | {0 0 17 822 0 7 5} | INTEGER | c8 | | c8 | | c8 | | +| 11 | "Rec. X.721 ISO/IEC 10165-2 : 1992": intervalsOfDay | {2 9 3 2 7 57} | SET OF SEQUENCE | c4 | | c4 | | c4 | | +| 12 | "ITU-T Rec. Q.822 : 1994": maxSuppressedIntervals | {0 0 17 822 0 7 6} | INTEGER | c9 | | c9 | | c9 | | +| 13 | "ITU-T Rec. Q.822 : 1994": measurementList | {0 0 17 822 0 7 7} | SET OF SEQUENCE | c10 | | c10 | | c10 | | +| 14 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 15 | noCircuitsAvailable | {0 0 17 823 0 6 39} | INTEGER | m? | | – | | – | | +| 16 | "ITU-T Rec. Q.822 : 1994": numSuppressedIntervals | {0 0 17 822 0 7 9} | INTEGER | c11? | | c11 | | – | | +| 17 | "ITU-T Rec. X.738": numericAttributeIdArray | {2 9 2 13 7 10} | SEQUENCE OF CHOICE | c14 | | c14 | | c14 | | +| 18 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 19 | "ITU-T Rec. Q.822 : 1994": observedObjectClass | {0 0 17 822 0 7 10} | CHOICE | o? | | o | | – | | +| 20 | "ITU-T Rec. X.739": observedObjectInstance | {2 9 2 11 7 16} | CHOICE | o? | | o | | – | | +| 21 | "ITU-T Rec. X.738": onceReportAttributeIdList | {2 9 2 13 7 16} | SET OF CHOICE | c14 | | c14 | | c14 | | +| 22 | "Rec. X.721 ISO/IEC 10165-2 : 1992": operationalState | {2 9 3 2 7 35} | ENUMERATED | – | | m | | – | | +| 23 | outgoingSeizures | {0 0 17 823 0 6 45} | INTEGER | m? | | – | | – | | +| 24 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c12 | | – | | + +**Table 23.4/Q.823.1 – observedDestinationCurrentData 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 | +| 25 | "ITU-T Rec. X.739": periodSynchronizationTime | {2 9 2 11 7 24} | GeneralizedTime | c13 | | c13 | | c13 | | +| 26 | "ITU-T Rec. Q.822 : 1994": reportAllAttributes | {0 0 17 822 0 7 11} | BOOLEAN | c16 | | c16 | | c16 | | +| 27 | "ITU-T Rec. X.738": scanAttributeList | {2 9 2 13 7 21} | SET OF CHOICE | c14 | | c14 | | c14 | | +| 28 | "ITU-T Rec. X.739": scannerId | {2 9 2 11 7 25} | CHOICE | m? | | m | | – | | +| 29 | "Rec. X.721 ISO/IEC 10165-2 : 1992": schedulerName | {2 9 3 2 7 67} | CHOICE | c6? | | c6 | | – | | +| 30 | "Rec. X.721 ISO/IEC 10165-2 : 1992": startTime | {2 9 3 2 7 68} | GeneralizedTime | c5 | | c5 | | c5 | | +| 31 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stopTime | {2 9 3 2 7 69} | CHOICE | c5 | | c5 | | c5 | | +| 32 | "ITU-T Rec. Q.822 : 1994": suppressAdditionalThresholds | {0 0 17 822 0 7 13} | BOOLEAN | c16 | | c16 | | c16 | | +| 33 | "ITU-T Rec. Q.822 : 1994": suspectIntervalFlag | {0 0 17 822 0 7 14} | BOOLEAN | m? | | m | | – | | +| 34 | "ITU-T Rec. Q.822 : 1994": thresholdDataInstance | {0 0 17 822 0 7 16} | SET OF CHOICE | c16 | | c16 | | c16 | | +| 35 | "Rec. X.721 ISO/IEC 10165-2 : 1992": weekMask | {2 9 3 2 7 71} | SET OF SEQUENCE | c17 | | c17 | | c17 | | + +**Table 23.4/Q.823.1 – observedDestinationCurrentData Attribute support (continued)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | – | | | +| 5 | – | | – | | – | | | +| 6 | – | | – | | – | | | +| 7 | – | | – | | – | | | + +**Table 23.4/Q.823.1 – observedDestinationCurrentData Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 8 | – | | – | | – | | | +| 9 | – | | – | | – | | | +| 10 | – | | – | | – | | | +| 11 | c4 | | c4 | | c4 | | | +| 12 | – | | – | | – | | | +| 13 | – | | – | | – | | | +| 14 | – | | – | | – | | | +| 15 | – | | – | | – | | | +| 16 | – | | – | | – | | | +| 17 | – | | – | | – | | | +| 18 | – | | – | | – | | | +| 19 | – | | – | | – | | | +| 20 | – | | – | | – | | | +| 21 | c14 | | c14 | | – | | | +| 22 | – | | – | | – | | | +| 23 | – | | – | | – | | | +| 24 | – | | – | | – | | | +| 25 | – | | – | | – | | | +| 26 | – | | – | | – | | | +| 27 | c14 | | c14 | | – | | | +| 28 | – | | – | | – | | | +| 29 | – | | – | | – | | | +| 30 | – | | – | | – | | | +| 31 | – | | – | | c5 | | | +| 32 | – | | – | | – | | | +| 33 | – | | – | | m | | | +| 34 | c16 | | c16 | | – | | | +| 35 | c17 | | c17 | | c17 | | | + +**Table 23.5/Q.823.1 – observedDestinationCurrentData Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 23.6/Q.823.1 – observedDestinationCurrentData Action support** + +There are no actions specified for this managed object class. + +**Table 23.7/Q.823.1 – observedDestinationCurrentData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | c1 | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | c3 | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | c3 | | | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": qualityOfServiceAlarm | {2 9 3 2 10 11} | | c16 | | | "Rec. Q.821: 1992": correlatedRecordNameParameter
"Rec. Q.821: 1992": logRecordIdParameter
"Rec. Q.821: 1992": suspectObjectListParameter | +| 5 | "ITU-T Rec. X.738": scanReport | {2 9 2 13 10 2} | | c14 | | | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stateChange | {2 9 3 2 10 14} | | c15 | | | | + +**Table 23.7/Q.823.1 – observedDestinationCurrentData Notification support (continued)** + +| 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 | c1 | | | +| | 1.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 1.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | c: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 | c:m | | | +| | 1.1.3.1 | attributeID | – | CHOICE | c:m | | | + +**Table 23.7/Q.823.1 – observedDestinationCurrentData Notification support (continued)** + +| 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.3.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.2 | | | +| | 1.1.3.1.2 | localForm | – | INTEGER | c:o.2 | | | +| | 1.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | c:o | | | +| | 1.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | c:m | | | +| | 1.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 1.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 1.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 1.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | c3 | | | +| | 2.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 2.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c: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 | | | + +**Table 23.7/Q.823.1 – observedDestinationCurrentData Notification support (continued)** + +| 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.3 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 2.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 2.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 2.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | c3 | | | +| | 3.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 3.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c: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 | c:o | | | +| | 3.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | | | + +**Table 23.7/Q.823.1 – observedDestinationCurrentData Notification support (continued)** + +| 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.4.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.7 | | | +| | 3.1.4.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 3.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 3.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 3.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 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 | c!6 | | | +| | 4.1.1 | probableCause | {2 9 3 2 7 18} | CHOICE | c:m | | | +| | 4.1.1.1 | globalValue | – | OBJECT IDENTIFIER | c:o.8 | | | +| | 4.1.1.2 | localValue | – | INTEGER | c:o.8 | | | +| | 4.1.2 | specificProblems | {2 9 3 2 7 27} | SET OF CHOICE | c:o | | | +| | 4.1.2.1 | OBJECT IDENTIFIER | – | OBJECT IDENTIFIER | c:o.9 | | | +| | 4.1.2.2 | INTEGER | – | INTEGER | c:o.9 | | | +| | 4.1.3 | perceivedSeverity | {2 9 3 2 7 17} | ENUMERATED | c:m | | | +| | 4.1.4 | backedUpStatus | {2 9 3 2 7 11} | BOOLEAN | c:o | | | +| | 4.1.5 | backUpObject | {2 9 3 2 7 40} | CHOICE | c:o | | | +| | 4.1.5.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.5.2 | nonSpecificForm | – | OCTET STRING | c:o.10 | | | +| | 4.1.5.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | + +**Table 23.7/Q.823.1 – observedDestinationCurrentData Notification support (continued)** + +| 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.5.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.6 | trendIndication | {2 9 3 2 7 30} | ENUMERATED | c:o | | | +| | 4.1.7 | thresholdInfo | {2 9 3 2 7 29} | SEQUENCE | c:o | | | +| | 4.1.7.1 | triggeredThreshold | – | CHOICE | c:m | | | +| | 4.1.7.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.11 | | | +| | 4.1.7.1.2 | localForm | – | INTEGER | c:o.11 | | | +| | 4.1.7.2 | observedValue | – | CHOICE | c:m | | | +| | 4.1.7.2.1 | integer | – | INTEGER | c:o.12 | | | +| | 4.1.7.2.2 | real | – | REAL | c:o.12 | | | +| | 4.1.7.3 | thresholdLevel | – | CHOICE | c:o | | | +| | 4.1.7.3.1 | up | – | SEQUENCE | c:o.13 | | | +| | 4.1.7.3.1.1 | high | – | CHOICE | c:m | | | +| | 4.1.7.3.1.1.1 | integer | – | INTEGER | c:o.14 | | | +| | 4.1.7.3.1.1.2 | real | – | REAL | c:o.14 | | | +| | 4.1.7.3.1.2 | low | – | CHOICE | c:o | | | +| | 4.1.7.3.1.2.1 | integer | – | INTEGER | c:o.15 | | | +| | 4.1.7.3.1.2.2 | real | – | REAL | c:o.15 | | | +| | 4.1.7.3.2 | down | – | SEQUENCE | c:o.13 | | | +| | 4.1.7.3.2.1 | high | – | CHOICE | c:m | | | +| | 4.1.7.3.2.1.1 | integer | – | INTEGER | c:o.16 | | | +| | 4.1.7.3.2.1.2 | real | – | REAL | c:o.16 | | | +| | 4.1.7.3.2.2 | low | – | CHOICE | c:m | | | +| | 4.1.7.3.2.2.1 | integer | – | INTEGER | c:o.17 | | | +| | 4.1.7.3.2.2.2 | real | – | REAL | c:o.17 | | | +| | 4.1.7.4 | armTime | – | GeneralizedTime | c:o | | | +| | 4.1.8 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 4.1.9 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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.18 | | | +| | 4.1.9.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.9.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.9.2.2 | nonSpecificForm | – | OCTET STRING | c:o.18 | | | + +**Table 23.7/Q.823.1 – observedDestinationCurrentData Notification support (continued)** + +| 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.9.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.18 | | | +| | 4.1.9.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.9.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.10 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | c:o | | | +| | 4.1.10.1 | attributeID | – | CHOICE | c:m | | | +| | 4.1.10.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.19 | | | +| | 4.1.10.1.2 | localForm | – | INTEGER | c:o.19 | | | +| | 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 | c:o | | | +| | 4.1.11.1 | attributeId | – | CHOICE | c:m | | | +| | 4.1.11.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.20 | | | +| | 4.1.11.1.2 | localForm | – | INTEGER | c:o.20 | | | +| | 4.1.11.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 4.1.12 | proposedRepairActions | {2 9 3 2 7 19} | SET OF CHOICE | c:o | | | +| | 4.1.12.1 | OBJECT IDENTIFIER | – | OBJECT IDENTIFIER | c:o.21 | | | +| | 4.1.12.2 | INTEGER | – | INTEGER | c:o.21 | | | +| | 4.1.13 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 4.1.14 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | ScanReportInformation | | Information Syntax
SEQUENCE | c14 | | | +| | 5.1.1 | scanInitiationTime | {2 9 2 13 7 22} | GeneralizedTime | c:o | | | +| | 5.1.2 | onceReportAttributeList | {2 9 2 13 7 17} | SET OF SEQUENCE | c:o | | | +| | 5.1.2.1 | attributeId | – | CHOICE | c:m | | | +| | 5.1.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.22 | | | + +**Table 23.7/Q.823.1 – observedDestinationCurrentData Notification support (continued)** + +| 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.2.1.2 | localForm | – | INTEGER | c:o.22 | | | +| | 5.1.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 5.1.3 | observationScanList | {2 9 2 13 7 15} | SET OF SEQUENCE | c:m | | | +| | 5.1.3.1 | observedObjectInstance | – | CHOICE | c:o | | | +| | 5.1.3.1.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.23 | | | +| | 5.1.3.1.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.3.1.1.2 | attributeValue | – | ANY | c:m | | | +| | 5.1.3.1.2 | nonSpecificForm | – | OCTET STRING | c:o.23 | | | +| | 5.1.3.1.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.23 | | | +| | 5.1.3.1.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.3.1.3.2 | attributeValue | – | ANY | c:m | | | +| | 5.1.3.2 | attributeMeasureList | – | SET OF SEQUENCE | c:o | | | +| | 5.1.3.2.1 | attributeId | – | CHOICE | c:m | | | +| | 5.1.3.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.24 | | | +| | 5.1.3.2.1.2 | localForm | – | INTEGER | c:o.24 | | | +| | 5.1.3.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:o | | | +| | 5.1.3.2.3 | timeStamp | – | CHOICE | c:o | | | +| | 5.1.3.2.3.1 | days | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.2 | hours | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.3 | minutes | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.4 | seconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.5 | milliSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.6 | microSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.7 | nanoSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.8 | picoSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.4 | suspectFlag | – | BOOLEAN | c:o | | | +| | 5.1.3.3 | numericValueArray | – | SEQUENCE OF CHOICE | c:o | | | +| | 5.1.3.3.1 | missingData | – | NULL | c:o.26 | | | +| | 5.1.3.3.2 | valueOnly | – | CHOICE | c:o.26 | | | +| | 5.1.3.3.2.1 | integer | – | INTEGER | c:o.27 | | | +| | 5.1.3.3.2.2 | real | – | REAL | c:o.27 | | | + +**Table 23.7/Q.823.1 – observedDestinationCurrentData Notification support (continued)** + +| 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.3.3.3 | qualifiedValue | – | SEQUENCE | c:o:26 | | | +| | 5.1.3.3.3.1 | value | – | CHOICE | c:m | | | +| | 5.1.3.3.3.1.1 | integer | – | INTEGER | c:o:28 | | | +| | 5.1.3.3.3.1.2 | real | – | REAL | c:o:28 | | | +| | 5.1.3.3.3.2 | timeStamp | – | CHOICE | c:o | | | +| | 5.1.3.3.3.2.1 | days | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.2 | hours | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.3 | minutes | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.4 | seconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.5 | milliSeconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.6 | microSeconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.7 | nanoSeconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.8 | picoSeconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.3 | suspectFlag | – | BOOLEAN | c:o | | | +| | 5.1.4 | incompleteScan | {2 9 2 13 7 30} | INTEGER | c:o | | | +| | 5.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 5.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 5.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 5.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | +| 6 | 6.1 | StateChangeInfo | | Information Syntax
SEQUENCE | c15 | | | +| | 6.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 6.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | c:o | | | +| | 6.1.2.1 | globalForm | – | OBJECT IDENTIFIER | c:o:30 | | | +| | 6.1.2.2 | localForm | – | INTEGER | c:o:30 | | | +| | 6.1.3 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | c:m | | | +| | 6.1.3.1 | attributeID | – | CHOICE | c:m | | | +| | 6.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o:31 | | | +| | 6.1.3.1.2 | localForm | – | INTEGER | c:o:31 | | | +| | 6.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | c:o | | | +| | 6.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | c:m | | | +| | 6.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | + +**Table 23.7/Q.823.1 – observedDestinationCurrentData 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 | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|-----------------------------|--------|---------|------------------------| +| | 6.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c:o | | | +| | 6.1.5.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 6.1.5.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 6.1.5.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o:32 | | | +| | 6.1.5.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 6.1.5.2.2 | nonSpecificForm | – | OCTET STRING | c:o:32 | | | +| | 6.1.5.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o:32 | | | +| | 6.1.5.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 6.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 6.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 6.1.7.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.7.2 | significance | – | BOOLEAN | c:o | | | +| | 6.1.7.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 23.8/Q.823.1 – observedDestinationCurrentData Parameter support** + +| Index | Parameter template label | Value of object identifier for parameter | Constraints and values | Status | Support | Additional information | +|-------|--------------------------------------------------|------------------------------------------|----------------------------------|--------|---------|------------------------| +| 1 | "Rec. Q.821:1992": correlatedRecordNameParameter | {0 0 17 821 0 5 2} | EVENT-INFO qualityofServiceAlarm | c16 | | | +| 2 | "Rec. Q.821:1992": logRecordIdParameter | {0 0 17 821 0 5 1} | EVENT-INFO qualityofServiceAlarm | c16 | | | +| 3 | "Rec. Q.821:1992": suspectObjectListParameter | {0 0 17 821 0 5 3} | EVENT-INFO qualityofServiceAlarm | c16 | | | + +**Table 23.9/Q.823.1 – observedDestinationCurrentData Conditions** + +| Condition number | Condition | Reference | +|------------------|-------------------------|---------------------------------------------------------------------------------------------------------| +| c1 | IF 8.3/2 THEN m ELSE – | "notification of attribute value change events is required" | +| c2 | IF 8.3/3 THEN m ELSE – | "the managed object can be scheduled" | +| c3 | IF 8.3/5 THEN m ELSE – | "notification of object creation and object deletion events is required" | +| c4 | IF 8.3/7 THEN m ELSE – | "daily scheduling is required and the weekly or external scheduling package is not present" | +| c5 | IF 8.3/8 THEN m ELSE – | "the scanning function is to be enabled between specified start and stop times" | +| c6 | IF 8.3/9 THEN m ELSE – | "reference to external scheduler is required and the daily or weekly scheduling package is not present" | +| c7 | IF 8.3/10 THEN m ELS – | "an instance supports it and the zeroSuppressionPkg is not present" | +| c8 | IF 8.3/11 THEN m EL – | "historyData objects are to be created at the end of an interval." | +| c9 | IF 8.3/12 THEN m ELSE – | "an instance supports it and at least one of zeroSuppressionPkg or filterSuppressionPkg is present." | +| c10 | IF 8.3/13 THEN m ELS – | "an instance supports it or the object class is currentData" | +| c11 | IF 8.3/14 THEN m EL – | "suppression counts are required and the filterSuppressionPkg or the zeroSuppressionPkg is present." | +| c12 | IF 8.3/17 THEN m E-E – | "any registered package, other than this package has been instantiated" | +| c13 | IF 8.3/18 THEN m ELSE – | "configurable agent internal synchronization of repeating time periods is required" | +| c14 | IF 8.3/20 THEN m ELSE – | "scheduled notifications are to be emitted." | +| c15 | IF 8.3/21 THEN m ELSE – | "notification of state change event is required" | +| c16 | IF 8.3/22 THEN m ELSE – | "a Quality of Service Alarm Notification is to be emitted for threshold crossing." | +| c17 | IF 8.3/24 THEN m ELSE – | "weekly scheduling is required and the daily or external scheduling package is not present" | +| c18 | IF 8.3/25 THEN m ELSE – | "an instance supports it and the filterSuppressionPkg is not present." | + +**Table 23.10/Q.823.1 – observedDestinationCurrentData Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|----------------------------------------------------------|---------------------------------------------|---------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "ITU-T Rec. X.738":
conflictingPackagesScanner-system | {2 9 2 13 6 9} | Superior class:
"Rec. X.721 ISO/IEC 10165-2 : 1992":
system
AND SUBCLASSES | o | | | + +**Table 23.10/Q.823.1 – observedDestinationCurrentData 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:m | | | +| | 1.6 | Delete contained objects | | c:x | | | + +## 24 observedDestinationHistoryData ["Q.823"] + +**Table 24.1/Q.823.1 – observedDestinationHistoryData 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 | observedDestinationHistoryData | {0 0 17 823 0 3 19} | | | + +**Table 24.2/Q.823.1 – observedDestinationHistoryData 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 24.3/Q.823.1 – observedDestinationHistoryData Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|-----------------------------------------------------------------|----------------------------------------|-----------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | callsAffectedByDecHistoryPackage | {0 0 17 823 0 4 10} | "this package is present if it is present in the corresponding instance of currentData" | c1 | | | +| 3 | "ITU-T Rec. Q.822 : 1994":
historyDataMeasurementListPkg | {0 0 17 822 0 4 4} | "the measurementListPkg is present in the corresponding currentData instance" | c2 | | | +| 4 | "ITU-T Rec. Q.822 : 1994":
historyDataPkg | | Mandatory | m | | | +| 5 | "ITU-T Rec. Q.822 : 1994":
historyDataSuspectIntervalFlagPkg | {0 0 17 822 0 4 5} | "an instance supports it." | o | | | + +**Table 24.3/Q.823.1 – observedDestinationHistoryData Package support (concluded)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|---------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------|--------|---------|------------------------| +| 6 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervals
Pkg | {0 0 17 822 0 4 9} | "this package is present in the corresponding currentData instance." | c3 | | | +| 7 | "ITU-T Rec. Q.822 : 1994":
objectDeleteNotification
Pkg | {0 0 17 822 0 4 10} | "an instance supports it." | o | | | +| 8 | observedDestinationHistoryDataPackage | | Mandatory | m | | | +| 9 | "ITU-T Rec. Q.822 : 1994":
observedManagedObject
Pkg | {0 0 17 822 0 4 11} | "this package is present in the corresponding currentData instance." | c3 | | | +| 10 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c4 | | | +| 11 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
topPackage | | Mandatory | m | | | + +**Table 24.4/Q.823.1 – observedDestinationHistoryData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 2 | answeredOutgoingSeizures | {0 0 17 823 0 6 10} | INTEGER | m? | | m | | – | | +| 3 | bids | {0 0 17 823 0 6 14} | INTEGER | m? | | m | | – | | +| 4 | callsAffectedByDcc | {0 0 17 823 0 6 15} | INTEGER | c1? | | c1 | | – | | +| 5 | "ITU-T Rec. X.739":
granularityPeriod | {2 9 2 11 7 23} | CHOICE | m? | | m | | – | | +| 6 | "ITU-T Rec. Q.822 : 1994":
historyDataId | {0 0 17 822 0 7 4} | CHOICE | m? | | m | | – | | +| 7 | "ITU-T Rec. Q.822 : 1994":
measurementList | {0 0 17 822 0 7 7} | SET OF SEQUENCE | c2? | | c2 | | – | | +| 8 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 9 | noCircuitsAvailable | {0 0 17 823 0 6 39} | INTEGER | m? | | m | | – | | + +**Table 24.4/Q.823.1 – observedDestinationHistoryData 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 | +| 10 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervals | {0 0 17 822 0 7 9} | INTEGER | c3? | | c3 | | – | | +| 11 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 12 | "ITU-T Rec. Q.822 : 1994":
observedObjectClass | {0 0 17 822 0 7 10} | CHOICE | c3? | | c3 | | – | | +| 13 | "ITU-T Rec. X.739":
observedObjectInstance | {2 9 2 11 7 16} | CHOICE | c3? | | c3 | | – | | +| 14 | outgoingSeizures | {0 0 17 823 0 6 45} | INTEGER | m? | | m | | – | | +| 15 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c4 | | – | | +| 16 | "ITU-T Rec. Q.822 : 1994":
periodEndTime | {0 0 17 822 0 7 12} | GeneralizedTime | m? | | m | | – | | +| 17 | "ITU-T Rec. Q.822 : 1994":
suspectIntervalFlag | {0 0 17 822 0 7 14} | BOOLEAN | o? | | o | | – | | + +**Table 24.4/Q.823.1 – observedDestinationHistoryData Attribute support (continued)** + +| 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 | – | | – | | – | | | + +**Table 24.4/Q.823.1 – observedDestinationHistoryData Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 14 | – | | – | | – | | | +| 15 | – | | – | | – | | | +| 16 | – | | – | | – | | | +| 17 | – | | – | | – | | | + +**Table 24.5/Q.823.1 – observedDestinationHistoryData Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 24.6/Q.823.1 – observedDestinationHistoryData Action support** + +There are no actions specified for this managed object class. + +**Table 24.7/Q.823.1 – observedDestinationHistoryData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | o | | | | + +**Table 24.7/Q.823.1 – observedDestinationHistoryData Notification support (continued)** + +| 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 | ObjectInfo | | Information Syntax SEQUENCE | o | | | +| | 1.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 1.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c:o | | | +| | 1.1.2.1 | attributeId | – | CHOICE | c:m | | | +| | 1.1.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.1 | | | +| | 1.1.2.1.2 | localForm | – | INTEGER | c:o.1 | | | +| | 1.1.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 1.1.3 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | + +**Table 24.7/Q.823.1 – observedDestinationHistoryData 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.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c:o | | | +| | 1.1.4.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 1.1.4.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 1.1.4.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.2 | | | +| | 1.1.4.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.4.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 1.1.4.2.2 | nonSpecificForm | – | OCTET STRING | c:o.2 | | | +| | 1.1.4.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.2 | | | +| | 1.1.4.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 1.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 1.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 1.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 1.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 24.8/Q.823.1 – observedDestinationHistoryData Parameter support** + +There are no parameters specified for this managed object class. + +**Table 24.9/Q.823.1 – observedDestinationHistoryData Conditions** + +| Condition number | Condition | Reference | +|------------------|------------------------|-----------------------------------------------------------------------------------------| +| c1 | IF 9.3/2 THEN m ELSE – | "this package is present if it is present in the corresponding instance of currentData" | +| c2 | IF 9.3/3 THEN m ELSE – | "the measurementListPkg is present in the corresponding currentData instance" | +| c3 | IF 9.3/6 THEN m ELSE – | "this package is present in the corresponding currentData instance." | +| c4 | IF 9.3/10 THEN m ELS – | "any registered package, other than this package has been instantiated" | + +**Table 24.10/Q.823.1 – observedDestinationHistoryData Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------------------------------|---------------------------------------------|-----------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | observedDestinationHistoryData-observedDestination | {0 0 17 823 0 5 12} | Superior class:
observedDestination
AND SUBCLASSES | o | | | +| 2 | "ITU-T Rec. Q.822 : 1994":
historyData-currentData | {0 0 17 822 0 6 1} | Superior class:
"ITU-T Rec. Q.822 :
1994":
currentData
AND SUBCLASSES | o | | | + +**Table 24.10/Q.823.1 – observedDestinationHistoryData 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:x | | | +| | 1.6 | Delete contained objects | | c:m | | | +| 2 | 2.1 | Create support | | – | | | +| | 2.2 | Create with reference object | | – | | | +| | 2.3 | Create with automatic instance naming | | – | | | +| | 2.4 | Delete support | | c:m | | | +| | 2.5 | Delete only if no contained objects | | c:x | | | +| | 2.6 | Delete contained objects | | c:m | | | + +25 scr ["Q.823"] + +**Table 25.1/Q.823.1 – scr 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 | scr | {0 0 17 823 0 3 20} | | | + +**Table 25.2/Q.823.1 – scr 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 25.3/Q.823.1 – scr Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|---------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | creatorPackage | {0 0 17 823 0 4 14} | "an instance supports it" | o | | | +| 3 | "Rec. M.3100 : 1992":
objectManagementNotificationsPackage | {0 0 13 3100 0 4 20} | Mandatory | m | | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c1 | | | +| 5 | scrPackage | | Mandatory | m | | | +| 6 | "Rec. M.3100 : 1992":
stateChangeNotificationPackage | {0 0 13 3100 0 4 28} | Mandatory | m | | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
topPackage | | Mandatory | m | | | +| 8 | trafficControlPackage | | Mandatory | m | | | + +**Table 25.4/Q.823.1 – scr 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 | activationThresholds | {0 0 17 823 0 6 3} | SEQUENCE | m | | m | | m | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
administrativeState | {2 9 3 2 7 31} | ENUMERATED | m | | m | | m | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 4 | assocScrAffectedTraffic | {0 0 17 823 0 6 53} | CHOICE | m | | m | | m | | +| 5 | autoActivated | {0 0 17 823 0 6 13} | BOOLEAN | m? | | m | | – | | +| 6 | controlTmCircuitEndPointSubgroup | {0 0 17 823 0 6 58} | CHOICE | m? | | m | | – | | +| 7 | creatorIdentity | {0 0 17 823 0 6 24} | CHOICE | o? | | o | | – | | +| 8 | dispositionOfCalls | {0 0 17 823 0 6 29} | CHOICE | m | | m | | m | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | + +**Table 25.4/Q.823.1 – scr 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 | +| 10 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 11 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | cl | | – | | +| 12 | tmSurveillance | {0 0 17 823 0 6 60} | BOOLEAN | m | | m | | m | | +| 13 | trafficControlId | {0 0 17 823 0 6 61} | CHOICE | m? | | m | | – | | + +**Table 25.4/Q.823.1 – scr 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 | – | | – | | – | | | + +**Table 25.5/Q.823.1 – scr Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 25.6/Q.823.1 – scr Action support** + +There are no actions specified for this managed object class. + +**Table 25.7/Q.823.1 – scr 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | m | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | m | | | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stateChange | {2 9 3 2 10 14} | | m | | | | + +**Table 25.7/Q.823.1 – scr Notification support (continued)** + +| 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 | | | + +**Table 25.7/Q.823.1 – scr Notification support (continued)** + +| 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.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.3 | | | +| | 1.1.5.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 2.1.4.2.2 | nonSpecificForm | – | OCTET STRING | c:o.5 | | | + +**Table 25.7/Q.823.1 – scr Notification support (continued)** + +| 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.4.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.5 | | | +| | 2.1.4.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 3.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | o | | | + +**Table 25.7/Q.823.1 – scr Notification support (continued)** + +| 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 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | o | | | +| | 3.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | +| 4 | 4.1 | StateChangeInfo | | Information Syntax
SEQUENCE | m | | | +| | 4.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | o | | | +| | 4.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | o | | | +| | 4.1.2.1 | globalForm | – | OBJECT IDENTIFIER | c:o.8 | | | +| | 4.1.2.2 | localForm | – | INTEGER | c:o.8 | | | +| | 4.1.3 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | m | | | +| | 4.1.3.1 | attributeID | – | CHOICE | m | | | +| | 4.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | o.9 | | | +| | 4.1.3.1.2 | localForm | – | INTEGER | o.9 | | | +| | 4.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | o | | | +| | 4.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | m | | | +| | 4.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | o | | | +| | 4.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | o | | | +| | 4.1.5.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 4.1.5.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 4.1.5.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.5.2.2 | nonSpecificForm | – | OCTET STRING | c:o.10 | | | +| | 4.1.5.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | o | | | + +**Table 25.7/Q.823.1 – scr 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 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | o | | | +| | 4.1.7.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.7.2 | significance | – | BOOLEAN | c:o | | | +| | 4.1.7.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 25.8/Q.823.1 – scr Parameter support** + +There are no parameters specified for this managed object class. + +**Table 25.9/Q.823.1 – scr Conditions** + +| Condition number | Condition | Reference | +|------------------|-------------------------|-------------------------------------------------------------------------| +| c1 | IF 10.3/4 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table 25.10/Q.823.1 – scr Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------|---------------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | trafficControl-managedElement | {0 0 17 823 0 5 20} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | + +**Table 25.10/Q.823.1 – scr 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 | | | + +## 26 scrAffectedTraffic ["Q.823"] + +Table 26.1/Q.823.1 – scrAffectedTraffic 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 | scrAffectedTraffic | {0 0 17 823 0 3 21} | | | + +Table 26.2/Q.823.1 – scrAffectedTraffic 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 26.3/Q.823.1 – scrAffectedTraffic Package support + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | level2ResponseCategoriesPackage | {0 0 17 823 0 4 18} | "instance supports multi threshold selective circuit reservation" | c1 | | | +| 3 | "Rec. M.3100 : 1992": objectManagementNotificationsPackage | {0 0 13 3100 0 4 20} | Mandatory | m | | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c2 | | | +| 5 | scrAffectedTrafficPackage | | Mandatory | m | | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | + +Table 26.4/Q.823.1 – scrAffectedTraffic 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 2 | level1ResponseCategories | {0 0 17 823 0 6 36} | SET OF SEQUENCE | m | | m | | m | | +| 3 | level2ResponseCategories | {0 0 17 823 0 6 37} | SET OF SEQUENCE | c1 | | c1 | | c1 | | + +**Table 26.4/Q.823.1 – scrAffectedTraffic 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 | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c2 | | – | | +| 7 | scrAffectedTrafficId | {0 0 17 823 0 6 52} | CHOICE | m? | | m | | – | | + +**Table 26.4/Q.823.1 – scrAffectedTraffic Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | – | | | +| 5 | – | | – | | – | | | +| 6 | – | | – | | – | | | +| 7 | – | | – | | – | | | + +**Table 26.5/Q.823.1 – scrAffectedTraffic Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 26.6/Q.823.1 – scrAffectedTraffic Action support** + +There are no actions specified for this managed object class. + +**Table 26.7/Q.823.1 – scrAffectedTraffic 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | m | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | m | | | | + +**Table 26.7/Q.823.1 – scrAffectedTraffic Notification support (continued)** + +| 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 | | | + +**Table 26.7/Q.823.1 – scrAffectedTraffic Notification support (continued)** + +| 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.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 2.1.4.2.2 | nonSpecificForm | – | OCTET STRING | c:o.5 | | | + +**Table 26.7/Q.823.1 – scrAffectedTraffic Notification support (continued)** + +| 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.4.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.5 | | | +| | 2.1.4.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | + +**Table 26.7/Q.823.1 – scrAffectedTraffic 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.4.2.3.2 | attributeValue | – | 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 | | | +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 26.8/Q.823.1 – scrAffectedTraffic Parameter support** + +There are no parameters specified for this managed object class. + +**Table 26.9/Q.823.1 – scrAffectedTraffic Conditions** + +| Condition number | Condition | Reference | +|------------------|-------------------------|-------------------------------------------------------------------------| +| c1 | IF 11.3/2 THEN m ELSE – | "instance supports multi threshold selective circuit reservation" | +| c2 | IF 11.3/4 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table 26.10/823.1 – scrAffectedTraffic Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-----------------------------------|---------------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | scrAffectedTraffic-managedElement | {0 0 17 823 0 5 13} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | + +**Table 26.10/823.1 – scrAffectedTraffic 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 | | | + +27 skip ["Q.823"] + +**Table 27.1/Q.823.1 – skip 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 | skip | {0 0 17 823 0 3 22} | | | + +**Table 27.2 skip/Q.823.1 – 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 27.3/Q.823.1 – skip Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | creatorPackage | {0 0 17 823 0 4 14} | "an instance supports it" | o | | | +| 3 | "Rec. M.3100 : 1992": objectManagementNotificationsPackage | {0 0 13 3100 0 4 20} | Mandatory | m | | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c1 | | | +| 5 | skipPackage | | Mandatory | m | | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | +| 7 | trafficControlPackage | | Mandatory | m | | | + +**Table 27.4/Q.823.1 – skip 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 2 | controlTmCircuitEndPointSubgroup | {0 0 17 823 0 6 58} | CHOICE | m? | | m | | – | | +| 3 | creatorIdentity | {0 0 17 823 0 6 24} | CHOICE | o? | | o | | – | | +| 4 | destinationAspect | {0 0 17 823 0 6 26} | CHOICE | m | | m | | m | | + +**Table 27.4/Q.823.1 – skip 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 | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 7 | originationAspect | {0 0 17 823 0 6 42} | SEQUENCE | m | | m | | m | | +| 8 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | cl | | – | | +| 9 | percentage | {0 0 17 823 0 6 49} | CHOICE | m | | m | | m | | +| 10 | routingAspect | {0 0 17 823 0 6 51} | ENUMERATED | m | | m | | m | | +| 11 | tmSurveillance | {0 0 17 823 0 6 60} | BOOLEAN | m | | m | | m | | +| 12 | trafficControlId | {0 0 17 823 0 6 61} | CHOICE | m? | | m | | – | | + +**Table 27.4/Q.823.1 – skip Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | m | | | +| 5 | – | | – | | – | | | +| 6 | – | | – | | – | | | +| 7 | – | | – | | m | | | +| 8 | – | | – | | – | | | +| 9 | – | | – | | – | | | +| 10 | – | | – | | m | | | +| 11 | – | | – | | – | | | +| 12 | – | | – | | – | | | + +**Table 27.5/Q.823.1 – skip Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 27.6/Q.823.1 – skip Action support** + +There are no actions specified for this managed object class. + +**Table 27.7/Q.823.1 – skip 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | m | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | m | | | | + +**Table 27.7/Q.823.1 – skip Notification support (continued)** + +| 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 | | | + +**Table 27.7/Q.823.1 – skip Notification support (continued)** + +| 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.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 2.1.4.2.2 | nonSpecificForm | – | OCTET STRING | c:o.5 | | | + +**Table 27.7/Q.823.1 – skip Notification support (continued)** + +| 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.4.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.5 | | | +| | 2.1.4.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | + +**Table 27.7/Q.823.1 – skip 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.4.2.3.2 | attributeValue | – | 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 | | | +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 27.8/Q.823.1 – skip Parameter support** + +There are no parameters specified for this managed object class. + +**Table 27.9/Q.823.1 – skip Conditions** + +| Condition number | Condition | Reference | +|------------------|-------------------------|-------------------------------------------------------------------------| +| c1 | IF 12.3/4 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table 27.10/Q.823.1 – skip Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------|---------------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | trafficControl-managedElement | {0 0 17 823 0 5 20} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | + +**Table 27.10/Q.823.1 – skip 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 | | | + +## **28 stateIndicator ["Q.823"]** + +**Table 28.1/Q.823.1 – stateIndicator 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 | stateIndicator | {0 0 17 823 0 3 23} | | | + +**Table 28.2/Q.823.1 – stateIndicator 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 28.3/Q.823.1 – stateIndicator Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | "Rec M.3100 : 1992": attributeValueChangeNotificationPackage | {0 0 13 3100 0 4 4} | "notification of attribute value change events is required" | c1 | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": availabilityStatusPackage | {2 9 3 2 4 22} | "the managed object can be scheduled" | c2 | | | +| 4 | "Rec. M.3100 : 1992": createDeleteNotificationsPackage | {0 0 13 3100 0 4 10} | "notification of object creation and object deletion events is required" | c3 | | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992": dailyScheduling | {2 9 3 2 4 25} | "daily scheduling is required and the weekly or external scheduling package is not present" | c4 | | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": duration | {2 9 3 2 4 26} | "the scanning function is to be enabled between specified start and stop times" | c5 | | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992": externalScheduler | {2 9 3 2 4 27} | "reference to external scheduler is required and the daily or weekly scheduling package is not present" | c6 | | | +| 8 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c7 | | | +| 9 | "ITU-T Rec. X.739": periodSynchronizationPackage | {2 9 2 11 4 10} | "configurable agent internal synchronization of repeating time periods is required" | c8 | | | +| 10 | "ITU-T Rec. X.739": scannerPackage | | Mandatory | m | | | +| 11 | "Rec. M.3100 : 1992": stateChangeNotificationPackage | {0 0 13 3100 0 4 28} | "notification of state change event is required" | c9 | | | + +**Table 28.3/Q.823.1 – stateIndicator Package support (concluded)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 12 | stateIndicatorActionPackage | {0 0 17 823 0 4 20} | "stateIndicatorNotificationPackage is not present" | c10 | | | +| 13 | stateIndicatorNotificationPackage | {0 0 17 823 0 4 21} | "stateIndicatorActionPackage is not present" | c11 | | | +| 14 | stateIndicatorPackage | | Mandatory | m | | | +| 15 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
topPackage | | Mandatory | m | | | +| 16 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
weeklyScheduling | {2 9 3 2 4 29} | "weekly scheduling is required and the daily or external scheduling package is not present" | c12 | | | + +**Table 28.4/Q.823.1 – stateIndicator 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
administrativeState | {2 9 3 2 7 31} | ENUMERATED | m | | m | | m | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
availabilityStatus | {2 9 3 2 7 33} | SET OF INTEGER | c2? | | c2 | | – | | +| 4 | "ITU-T Rec. X.739":
granularityPeriod | {2 9 2 11 7 23} | CHOICE | m | | m | | m | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
intervalsOfDay | {2 9 3 2 7 57} | SET OF SEQUENCE | c4 | | c4 | | c4 | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 8 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
operationalState | {2 9 3 2 7 35} | ENUMERATED | – | | m | | – | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c7 | | – | | +| 10 | "ITU-T Rec. X.739":
periodSynchronizationTime | {2 9 2 11 7 24} | GeneralizedTime | c8 | | c8 | | c8 | | + +**Table 28.4/Q.823.1 – stateIndicator 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 | "ITU-T Rec. X.739": scannerId | {2 9 2 11 7 25} | CHOICE | m? | | m | | – | | +| 12 | "Rec. X.721 ISO/IEC 10165-2 : 1992": schedulerName | {2 9 3 2 7 67} | CHOICE | c6? | | c6 | | – | | +| 13 | "Rec. X.721 ISO/IEC 10165-2 : 1992": startTime | {2 9 3 2 7 68} | GeneralizedTime | c5 | | c5 | | c5 | | +| 14 | stateIndicatorId | {0 0 17 823 0 6 55} | CHOICE | m? | | m | | – | | +| 15 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stopTime | {2 9 3 2 7 69} | CHOICE | c5 | | c5 | | c5 | | +| 16 | "Rec. X.721 ISO/IEC 10165-2 : 1992": weekMask | {2 9 3 2 7 71} | SET OF SEQUENCE | c12 | | c12 | | c12 | | + +**Table 28.4/Q.823.1 – stateIndicator Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | – | | | +| 5 | c4 | | c4 | | c4 | | | +| 6 | – | | – | | – | | | +| 7 | – | | – | | – | | | +| 8 | – | | – | | – | | | +| 9 | – | | – | | – | | | +| 10 | – | | – | | – | | | +| 11 | – | | – | | – | | | +| 12 | – | | – | | – | | | +| 13 | – | | – | | – | | | +| 14 | – | | – | | – | | | +| 15 | – | | – | | c5 | | | +| 16 | c12 | | c12 | | c12 | | | + +**Table 28.5/Q.823.1 – stateIndicator Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 28.6/Q.823.1 – stateIndicator Action support** + +| Index | Action type template label | Value of object identifier for action type | Constraints and values | Status | Support | Additional information | +|-------|----------------------------|--------------------------------------------|------------------------|--------|---------|------------------------| +| 1 | stateIndicatorAction | {0 0 17 823 0 7 1} | | c10 | | | + +**Table 28.6/Q.823.1 – stateIndicator Action support (concluded)** + +| Index | Subindex | Action field name label | Constraints and values | Status | Support | Additional information | +|-------|----------|-------------------------|----------------------------|--------|---------|------------------------| +| 1 | 1.1 | StateIndicatorBitMap | Reply Syntax
BIT STRING | c10 | | | + +**Table 28.7/Q.823.1 – stateIndicator 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
attributeValueChange | {2 9 3 2 10 1} | | c1 | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
objectCreation | {2 9 3 2 10 6} | | c3 | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
objectDeletion | {2 9 3 2 10 7} | | c3 | | | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
stateChange | {2 9 3 2 10 14} | | c9 | | | | +| 5 | stateIndicatorNotification | {0 0 17 823 0 8 1} | | c11 | | | | + +**Table 28.7/Q.823.1 – stateIndicator Notification support (continued)** + +| 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 | c1 | | | +| | 1.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 1.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | c:o | | | +| | 1.1.2.1 | globalForm | – | OBJECT IDENTIFIER | c:o.1 | | | +| | 1.1.2.2 | localForm | – | INTEGER | c:o.1 | | | + +**Table 28.7/Q.823.1 – stateIndicator Notification support (continued)** + +| 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.3 | attributeValueChangeDefinition | {2 9 3 2 7 10} | SET OF SEQUENCE | c:m | | | +| | 1.1.3.1 | attributeID | – | CHOICE | c:m | | | +| | 1.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.2 | | | +| | 1.1.3.1.2 | localForm | – | INTEGER | c:o.2 | | | +| | 1.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | c:o | | | +| | 1.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | c:m | | | +| | 1.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 1.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 1.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 1.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | c3 | | | +| | 2.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 2.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c:o | | | +| | 2.1.2.1 | attributeId | – | CHOICE | c:m | | | +| | 2.1.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.4 | | | + +**Table 28.7/Q.823.1 – stateIndicator Notification support (continued)** + +| 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.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 | c:o | | | +| | 2.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 2.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 2.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | c3 | | | +| | 3.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 3.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c: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 | c:o | | | +| | 3.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c:o | | | +| | 3.1.4.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | + +**Table 28.7/Q.823.1 – stateIndicator Notification support (continued)** + +| 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 3.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 3.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 3.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | +| 4 | 4.1 | StateChangeInfo | | Information Syntax
SEQUENCE | c9 | | | +| | 4.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 4.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | c:o | | | +| | 4.1.2.1 | globalForm | – | OBJECT IDENTIFIER | c:o.8 | | | +| | 4.1.2.2 | localForm | – | INTEGER | c:o.8 | | | +| | 4.1.3 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | c:m | | | +| | 4.1.3.1 | attributeID | – | CHOICE | c:m | | | +| | 4.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.9 | | | +| | 4.1.3.1.2 | localForm | – | INTEGER | c:o.9 | | | +| | 4.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | c:o | | | +| | 4.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | c:m | | | +| | 4.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 4.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c:o | | | +| | 4.1.5.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 4.1.5.2 | sourceObjectInst | – | CHOICE | c:o | | | + +**Table 28.7/Q.823.1 – stateIndicator 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.5.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.5.2.2 | nonSpecificForm | – | OCTET STRING | c:o.10 | | | +| | 4.1.5.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 4.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 4.1.7.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.7.2 | significance | – | BOOLEAN | c:o | | | +| | 4.1.7.3 | information | – | ANY DEFINED BY identifier | c:m | | | +| 5 | 5.1 | StateIndicatorBitMap | | Information Syntax
BIT STRING | c:l | | | + +**Table 28.8/Q.823.1 – stateIndicator Parameter support** + +There are no parameters specified for this managed object class. + +**Table 28.9/Q.823.1 – stateIndicator Conditions** + +| Condition number | Condition | Reference | +|------------------|------------------------|---------------------------------------------------------------------------------------------------------| +| c1 | IF 1.3/2 THEN m ELSE – | "notification of attribute value change events is required" | +| c2 | IF 1.3/3 THEN m ELSE – | "the managed object can be scheduled" | +| c3 | IF 1.3/4 THEN m ELSE – | "notification of object creation and object deletion events is required" | +| c4 | IF 1.3/5 THEN m ELSE – | "daily scheduling is required and the weekly or external scheduling package is not present" | +| c5 | IF 1.3/6 THEN m ELSE – | "the scanning function is to be enabled between specified start and stop times" | +| c6 | IF 1.3/7 THEN m ELSE – | "reference to external scheduler is required and the daily or weekly scheduling package is not present" | +| c7 | IF 1.3/8 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table 28.9/Q.823.1 – stateIndicator Conditions (concluded)** + +| Condition number | Condition | Reference | +|------------------|-------------------------|---------------------------------------------------------------------------------------------| +| c8 | IF 1.3/9 THEN m ELSE – | "configurable agent internal synchronization of repeating time periods is required" | +| c9 | IF 1.3/11 THEN m ELSE – | "notification of state change event is required" | +| c10 | IF 1.3/12 THEN m ELSE – | "stateIndicatorNotificationPackage is not present" | +| c11 | IF 1.3/13 THEN m ELSE – | "stateIndicatorActionPackage is not present" | +| c12 | IF 1.3/16 THEN m ELSE – | "weekly scheduling is required and the daily or external scheduling package is not present" | + +**Table 28.10/Q.823.1 – stateIndicator Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|----------------------------------------------------------|---------------------------------------------|------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | stateIndicator-managedElement | {0 0 17 823 0 5 15} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | +| 2 | "ITU-T Rec. X.738":
conflictingPackagesScanner-system | {2 9 2 13 6 9} | Superior class:
"Rec. X.721 ISO/IEC
10165-2 : 1992":
system
AND SUBCLASSES | o | | | + +**Table 28.10/Q.823.1 – stateIndicator 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 | | – | | | +| | 1.5 | Delete only if no contained objects | | – | | | +| | 1.6 | Delete contained objects | | – | | | +| 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 | | | + +## **29 tarFrom ["Q.823"]** + +**Table 29.1/Q.823.1 – tarFrom 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 | tarFrom | {0 0 17 823 0 3 24} | | | + +**Table 29.2/Q.823.1 – tarFrom 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 29.3/Q.823.1 – tarFrom Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------|----------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | creatorPackage | {0 0 17 823 0 4 14} | "an instance supports it" | o | | | +| 3 | destinationTypePackage | {0 0 17 823 0 4 16} | "destination type is required to unambiguously identify the destinationCode" | c1 | | | +| 4 | "Rec. M.3100 : 1992": objectManagementNotificationsPackage | {0 0 13 3100 0 4 20} | Mandatory | m | | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c2 | | | +| 6 | tarFromPackage | | Mandatory | m | | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | +| 8 | trafficControlPackage | | Mandatory | m | | | + +**Table 29.4/Q.823.1 – tarFrom 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 2 | controlTmCircuitEndPointSubgroup | {0 0 17 823 0 6 58} | CHOICE | m? | | m | | – | | +| 3 | creatorIdentity | {0 0 17 823 0 6 24} | CHOICE | o? | | o | | – | | +| 4 | destinationAspect | {0 0 17 823 0 6 26} | CHOICE | m | | m | | m | | +| 5 | destinationCode | {0 0 17 823 0 6 27} | GraphicString | m? | | m | | – | | +| 6 | destinationType | {0 0 17 823 0 6 28} | CHOICE | c1? | | c1 | | – | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 8 | newTmCircuitEndPointSubgroups | {0 0 17 823 0 6 38} | SEQUENCE OF CHOICE | m | | m | | m | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 10 | originationAspect | {0 0 17 823 0 6 42} | SEQUENCE | m | | m | | m | | +| 11 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c2 | | – | | +| 12 | percentage | {0 0 17 823 0 6 49} | CHOICE | m | | m | | m | | +| 13 | returnAction | {0 0 17 823 0 6 50} | CHOICE | m? | | m | | – | | +| 14 | routingAspect | {0 0 17 823 0 6 51} | ENUMERATED | m | | m | | m | | +| 15 | tmSurveillance | {0 0 17 823 0 6 60} | BOOLEAN | m | | m | | m | | +| 16 | trafficControlId | {0 0 17 823 0 6 61} | CHOICE | m? | | m | | – | | + +**Table 29.4/Q.823.1 – tarFrom Attribute support (continued)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | m | | | +| 5 | – | | – | | – | | | +| 6 | – | | – | | – | | | +| 7 | – | | – | | – | | | +| 8 | – | | – | | – | | | +| 9 | – | | – | | – | | | +| 10 | – | | – | | m | | | + +**Table 29.4/Q.823.1 – tarFrom Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 11 | – | | – | | – | | | +| 12 | – | | – | | – | | | +| 13 | – | | – | | – | | | +| 14 | – | | – | | m | | | +| 15 | – | | – | | – | | | +| 16 | – | | – | | – | | | + +**Table 29.5/Q.823.1 – tarFrom Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 29.6/Q.823.1 – tarFrom Action support** + +There are no actions specified for this managed object class. + +**Table 29.7/Q.823.1 – tarFrom 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | m | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | m | | | | + +**Table 29.7/Q.823.1 – tarFrom Notification support (continued)** + +| 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 | | | + +**Table 29.7/Q.823.1 – tarFrom Notification support (continued)** + +| 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | | | + +**Table 29.7/Q.823.1 – tarFrom Notification support (continued)** + +| 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 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 | | | + +**Table 29.7/Q.823.1 – tarFrom 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | 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 | | | +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 29.8/Q.823.1 – tarFrom Parameter support** + +There are no parameters specified for this managed object class. + +**Table 29.9/Q.823.1 – tarFrom Conditions** + +| Condition number | Condition | Reference | +|------------------|------------------------|------------------------------------------------------------------------------| +| c1 | IF 2.3/3 THEN m ELSE – | "destination type is required to unambiguously identify the destinationCode" | +| c2 | IF 2.3/5 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table 29.10/Q.823.1 – tarFrom Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------|---------------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | trafficControl-managedElement | {0 0 17 823 0 5 20} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | + +**Table 29.10/Q.823.1 – tarFrom 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 | | | + +## 30 tarTo ["Q.823"] + +**Table 30.1/Q.823.1 – tarTo 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 | tarTo | {0 0 17 823 0 3 25} | | | + +**Table 30.2/Q.823.1 – tarTo 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 30.3/Q.823.1 – tarTo Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|---------------------------------------------------------------|----------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | creatorPackage | {0 0 17 823 0 4 14} | "an instance supports it" | o | | | +| 3 | destinationTypePackage | {0 0 17 823 0 4 16} | "destination type is required to unambiguously identify the destinationCode" | c1 | | | +| 4 | "Rec. M.3100 : 1992":
objectManagementNotificationsPackage | {0 0 13 3100 0 4 20} | Mandatory | m | | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c2 | | | +| 6 | tarToPackage | | Mandatory | m | | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
topPackage | | Mandatory | m | | | +| 8 | trafficControlPackage | | Mandatory | m | | | + +**Table 30.4/Q.823.1 – tarTo 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 2 | controlTmCircuitEndPointSubgroup | {0 0 17 823 0 6 58} | CHOICE | m? | | m | | – | | +| 3 | creatorIdentity | {0 0 17 823 0 6 24} | CHOICE | o? | | o | | – | | +| 4 | destinationAspect | {0 0 17 823 0 6 26} | CHOICE | m | | m | | m | | +| 5 | destinationCode | {0 0 17 823 0 6 27} | GraphicString | m? | | m | | – | | +| 6 | destinationType | {0 0 17 823 0 6 28} | CHOICE | c1? | | c1 | | – | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 8 | newTmCircuitEndPointSubgroups | {0 0 17 823 0 6 38} | SEQUENCE OF CHOICE | m | | m | | m | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | + +**Table 30.4/Q.823.1 – tarTo 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 | +| 10 | originationAspect | {0 0 17 823 0 6 42} | SEQUENCE | m | | m | | m | | +| 11 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c2 | | – | | +| 12 | percentage | {0 0 17 823 0 6 49} | CHOICE | m | | m | | m | | +| 13 | returnAction | {0 0 17 823 0 6 50} | CHOICE | m? | | m | | – | | +| 14 | routingAspect | {0 0 17 823 0 6 51} | ENUMERATED | m | | m | | m | | +| 15 | tmSurveillance | {0 0 17 823 0 6 60} | BOOLEAN | m | | m | | m | | +| 16 | trafficControlId | {0 0 17 823 0 6 61} | CHOICE | m? | | m | | – | | + +**Table 30.4/Q.823.1 – tarTo Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | m | | | +| 5 | – | | – | | – | | | +| 6 | – | | – | | – | | | +| 7 | – | | – | | – | | | +| 8 | – | | – | | – | | | +| 9 | – | | – | | – | | | +| 10 | – | | – | | m | | | +| 11 | – | | – | | – | | | +| 12 | – | | – | | – | | | +| 13 | – | | – | | – | | | +| 14 | – | | – | | m | | | +| 15 | – | | – | | – | | | +| 16 | – | | – | | – | | | + +**Table 30.5/Q.823.1 – tarTo Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 30.6/Q.823.1 – tarTo Action support** + +There are no actions specified for this managed object class. + +**Table 30.7/Q.823.1 – tarTo 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | m | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | m | | | | + +**Table 30.7/Q.823.1 – tarTo Notification support (continued)** + +| 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 | | | + +**Table 30.7/Q.823.1 – tarTo Notification support (continued)** + +| 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.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.3 | | | +| | 1.1.5.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | | | + +**Table 30.7/Q.823.1 – tarTo Notification support (continued)** + +| 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.4.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | ANY | c:m | | | + +**Table 30.7/Q.823.1 – tarTo 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | 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 | | | +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 30.8/Q.823.1 – tarTo Parameter support** + +There are no parameters specified for this managed object class. + +**Table 30.9/Q.823.1 – tarTo Conditions** + +| Condition number | Condition | Reference | +|------------------|------------------------|------------------------------------------------------------------------------| +| c1 | IF 3.3/3 THEN m ELSE – | "destination type is required to unambiguously identify the destinationCode" | +| c2 | IF 3.3/5 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table 30.10/Q.823.1 – tarTo Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------|---------------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | trafficControl-managedElement | {0 0 17 823 0 5 20} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | + +**Table 30.10/Q.823.1 – tarTo 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 | | | + +## 31 tmCircuitEndPointSubgroup ["Q.823"] + +**Table 31.1/Q.823.1 – tmCircuitEndPointSubgroup 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 | tmCircuitEndPointSubgroup | {0 0 17 823 0 3 26} | | | + +**Table 31.2/Q.823.1 – tmCircuitEndPointSubgroup 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 31.3/Q.823.1 – tmCircuitEndPointSubgroup Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|-----------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | "Rec. M.3100 : 1992": circuitEndPointSubgroup Package | | Mandatory | m | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c1 | | | +| 4 | tmCircuitEndPointSubgroupPackage | | Mandatory | m | | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | + +**Table 31.4/Q.823.1 – tmCircuitEndPointSubgroup 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 2 | "Rec. M.3100 : 1992": circuitDirectionality | {0 0 13 3100 0 7 66} | ENUMERATED | m? | | m | | – | | +| 3 | "Rec. M.3100 : 1992": circuitEndPointSubgroup Id | {0 0 13 3100 0 7 61} | CHOICE | m? | | m | | – | | +| 4 | "Rec. M.3100 : 1992": informationTransferCapabilities | {0 0 13 3100 0 7 65} | ENUMERATED | m? | | m | | – | | +| 5 | "Rec. M.3100 : 1992": labelOfFarEndExchange | {0 0 13 3100 0 7 63} | GraphicString | m? | | m | | – | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 7 | "Rec. M.3100 : 1992": numberOfCircuits | {0 0 13 3100 0 7 62} | INTEGER | m? | | m | | – | | +| 8 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | cl | | – | | +| 10 | "Rec. M.3100 : 1992": signallingCapabilities | {0 0 13 3100 0 7 64} | ENUMERATED | m? | | m | | – | | +| 11 | tmSurveillance | {0 0 17 823 0 6 60} | BOOLEAN | m | | m | | m | | +| 12 | "Rec. M.3100 : 1992": transmissionCharacteristics | {0 0 13 3100 0 7 67} | BIT STRING | m? | | m | | – | | +| 13 | "Rec. M.3100 : 1992": userLabel | {0 0 13 3100 0 7 50} | GraphicString | m | | m | | m | | + +**Table 31.4/Q.823.1 – tmCircuitEndPointSubgroup Attribute support (continued)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | – | | | +| 5 | – | | – | | – | | | +| 6 | – | | – | | – | | | +| 7 | – | | – | | – | | | + +**Table 31.4/Q.823.1 – tmCircuitEndPointSubgroup Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 8 | – | | – | | – | | | +| 9 | – | | – | | – | | | +| 10 | – | | – | | – | | | +| 11 | – | | – | | – | | | +| 12 | – | | – | | – | | | +| 13 | – | | – | | – | | | + +**Table 31.5/Q.823.1 – tmCircuitEndPointSubgroup Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 31.6/Q.823.1 – tmCircuitEndPointSubgroup Action support** + +There are no actions specified for this managed object class. + +**Table 31.7/Q.823.1 – tmCircuitEndPointSubgroup 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | m | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | m | | | | + +**Table 31.7/Q.823.1 – tmCircuitEndPointSubgroup Notification support (continued)** + +| 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 | | | + +**Table 31.7/Q.823.1 – tmCircuitEndPointSubgroup Notification support (continued)** + +| 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | | | + +**Table 31.7/Q.823.1 – tmCircuitEndPointSubgroup Notification support (continued)** + +| 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 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 | | | + +**Table 31.7/Q.823.1 – tmCircuitEndPointSubgroup 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.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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | 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 | | | +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 31.8/Q.823.1 – tmCircuitEndPointSubgroup Parameter support** + +There are no parameters specified for this managed object class. + +**Table 31.9/Q.823.1 – tmCircuitEndPointSubgroup Conditions** + +| Condition number | Condition | Reference | +|------------------|------------------------|-------------------------------------------------------------------------| +| c1 | IF 4.3/3 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table 31.10/Q.823.1 – tmCircuitEndPointSubgroup Name Binding support** + +There are no name bindings specified for this managed object class. + +**Table 32.1/Q.823.1 – tmCircuitEndPointSubgroupCurrentData +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 | tmCircuitEndPointSubgroupCurrentData | {0 0 17 823 0 3 27} | | | + +**Table 32.2/Q.823.1 – tmCircuitEndPointSubgroupCurrentData 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 32.3/Q.823.1 – tmCircuitEndPointSubgroupCurrentData Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | answeredIncomingSeizuresPackage | {0 0 17 823 0 4 5} | "this performance measurement is supported by the NE" | c1 | | | +| 3 | "Rec. M.3100 : 1992": attributeValueChangeNotificationPackage | {0 0 13 3100 0 4 4} | "notification of attribute value change events is required" | c2 | | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": availabilityStatusPackage | {2 9 3 2 4 22} | "the managed object can be scheduled" | c3 | | | +| 5 | circuitEndPointSubgroupCurrentDataPackage | | Mandatory | m | | | +| 6 | "Rec. M.3100 : 1992": createDeleteNotificationsPackage | {0 0 13 3100 0 4 10} | "notification of object creation and object deletion events is required" | c4 | | | +| 7 | "ITU-T Rec. Q.822 : 1994": currentDataPkg | | Mandatory | m | | | +| 8 | "Rec. X.721 ISO/IEC 10165-2 : 1992": dailyScheduling | {2 9 3 2 4 25} | "daily scheduling is required and the weekly or external scheduling package is not present" | c5 | | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992": duration | {2 9 3 2 4 26} | "the scanning function is to be enabled between specified start and stop times" | c6 | | | +| 10 | "Rec. X.721 ISO/IEC 10165-2 : 1992": externalScheduler | {2 9 3 2 4 27} | "reference to external scheduler is required and the daily or weekly scheduling package is not present" | c7 | | | + +**Table 32.3/Q.823.1 – tmCircuitEndPointSubgroupCurrentData Package support (concluded)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------|----------------------------------------|------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 11 | "ITU-T Rec. Q.822 : 1994":
filterSuppressionPkg | {0 0 17 822 0 4 2} | "an instance supports it and the zeroSuppressionPkg is not present" | c8 | | | +| 12 | "ITU-T Rec. Q.822 : 1994":
historyRetentionPkg | {0 0 17 822 0 4 6} | "historyData objects are to be created at the end of an interval." | c9 | | | +| 13 | "ITU-T Rec. Q.822 : 1994":
maxSuppressedIntervalsPkg | {0 0 17 822 0 4 7} | "an instance supports it and at least one of zeroSuppressionPkg or filterSuppressionPkg is present." | c10 | | | +| 14 | "ITU-T Rec. Q.822 : 1994":
measurementListPkg | {0 0 17 822 0 4 8} | "an instance supports it or the object class is currentData" | c11 | | | +| 15 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervalsPkg | {0 0 17 822 0 4 9} | "suppression counts are required and the filterSuppressionPkg or the zeroSuppressionPkg is present." | c12 | | | +| 16 | "ITU-T Rec. Q.822 : 1994":
observedManagedObjectPkg | {0 0 17 822 0 4 11} | "an instance supports it." | o | | | +| 17 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c13 | | | +| 18 | "ITU-T Rec. X.739":
periodSynchronizationPackage | {2 9 2 11 4 10} | Mandatory | m | | | +| 19 | "ITU-T Rec. X.739":
scannerPackage | | Mandatory | m | | | +| 20 | "ITU-T Rec. Q.822 : 1994":
scheduledPMReportPkg | {0 0 17 822 0 4 12} | "scheduled notifications are to be emitted." | c14 | | | +| 21 | "Rec. M.3100 : 1992":
stateChangeNotificationPackage | {0 0 13 3100 0 4 28} | "notification of state change event is required" | c15 | | | +| 22 | "ITU-T Rec. Q.822 : 1994":
thresholdPkg | {0 0 17 822 0 4 13} | "a Quality of Service Alarm Notification is to be emitted for threshold crossing." | c16 | | | +| 23 | tmCircuitEndPointSubgroupCurrentDataPackage | | Mandatory | m | | | +| 24 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
topPackage | | Mandatory | m | | | +| 25 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
weeklyScheduling | {2 9 3 2 4 29} | "weekly scheduling is required and the daily or external scheduling package is not present" | c17 | | | +| 26 | "ITU-T Rec. Q.822 : 1994":
zeroSuppressionPkg | {0 0 17 822 0 4 15} | "an instance supports it and the filterSuppressionPkg is not present." | c18 | | | + +**Table 32.4/Q.823.1 – tmCircuitEndPointSubgroupCurrentData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
administrativeState | {2 9 3 2 7 31} | ENUMERATED | m | | m | | m | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 3 | answeredIncomingSeizures | {0 0 17 823 0 6 9} | INTEGER | c1? | | – | | – | | +| 4 | answeredOutgoingSeizures | {0 0 17 823 0 6 10} | INTEGER | m? | | – | | – | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
availabilityStatus | {2 9 3 2 7 33} | SET OF INTEGER | c3? | | c3 | | – | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
discriminatorConstruct | {2 9 3 2 7 56} | CHOICE | c8 | | c8 | | c8 | | +| 7 | "ITU-T Rec. Q.822 : 1994":
elapsedTime | {0 0 17 822 0 7 2} | CHOICE | m? | | m | | – | | +| 8 | "ITU-T Rec. X.739":
granularityPeriod | {2 9 2 11 7 23} | CHOICE | m | | m | | m | | +| 9 | "ITU-T Rec. Q.822 : 1994":
historyRetention | {0 0 17 822 0 7 5} | INTEGER | m? | | m | | – | | +| 10 | incomingSeizures | {0 0 17 823 0 6 31} | INTEGER | m? | | – | | – | | +| 11 | incomingTrafficUsage | {0 0 17 823 0 6 33} | INTEGER | m? | | – | | – | | +| 12 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
intervalsOfDay | {2 9 3 2 7 57} | SET OF SEQUENCE | c5 | | c5 | | c5 | | +| 13 | "ITU-T Rec. Q.822 : 1994":
maxSuppressedIntervals | {0 0 17 822 0 7 6} | INTEGER | c10 | | c10 | | c10 | | +| 14 | "ITU-T Rec. Q.822 : 1994":
measurementList | {0 0 17 822 0 7 7} | SET OF SEQUENCE | c11 | | c11 | | c11 | | +| 15 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 16 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervals | {0 0 17 822 0 7 9} | INTEGER | c12? | | c12 | | – | | +| 17 | numberOfAvailCircuits | {0 0 17 823 0 6 40} | CHOICE | m? | | – | | – | | +| 18 | "ITU-T Rec. X.738":
numericAttributeIdArray | {2 9 2 13 7 10} | SEQUENCE OF CHOICE | c14 | | c14 | | c14 | | + +**Table 32.4/Q.823.1 – tmCircuitEndPointSubgroupCurrentData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 20 | "ITU-T Rec. Q.822 : 1994":
observedObjectClass | {0 0 17 822 0 7 10} | CHOICE | o? | | o | | – | | +| 21 | "ITU-T Rec. X.739":
observedObjectInstance | {2 9 2 11 7 16} | CHOICE | o? | | o | | – | | +| 22 | "ITU-T Rec. X.738":
onceReportAttributeIdList | {2 9 2 13 7 16} | SET OF CHOICE | c14 | | c14 | | c14 | | +| 23 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
operationalState | {2 9 3 2 7 35} | ENUMERATED | – | | m | | – | | +| 24 | outgoingBids | {0 0 17 823 0 6 44} | INTEGER | m? | | – | | – | | +| 25 | outgoingSeizures | {0 0 17 823 0 6 45} | INTEGER | m? | | – | | – | | +| 26 | outgoingTrafficUsage | {0 0 17 823 0 6 47} | INTEGER | m? | | – | | – | | +| 27 | overflow | {0 0 17 823 0 6 48} | INTEGER | m? | | – | | – | | +| 28 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c13 | | – | | +| 29 | "ITU-T Rec. X.739":
periodSynchronizationTime | {2 9 2 11 7 24} | GeneralizedTime | m | | m | | m | | +| 30 | "ITU-T Rec. Q.822 : 1994":
reportAllAttributes | {0 0 17 822 0 7 11} | BOOLEAN | c16 | | c16 | | c16 | | +| 31 | "ITU-T Rec. X.738":
scanAttributeIdList | {2 9 2 13 7 21} | SET OF CHOICE | c14 | | c14 | | c14 | | +| 32 | "ITU-T Rec. X.739":
scannerId | {2 9 2 11 7 25} | CHOICE | m? | | m | | – | | +| 33 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
schedulerName | {2 9 3 2 7 67} | CHOICE | c7? | | c7 | | – | | +| 34 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
startTime | {2 9 3 2 7 68} | GeneralizedTime | c6 | | c6 | | c6 | | +| 35 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
stopTime | {2 9 3 2 7 69} | CHOICE | c6 | | c6 | | c6 | | +| 36 | "ITU-T Rec. Q.822 : 1994":
suppressAdditionalThresholds | {0 0 17 822 0 7 13} | BOOLEAN | c16 | | c16 | | c16 | | + +**Table 32.4/Q.823.1 – tmCircuitEndPointSubgroupCurrentData 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 | +| 37 | "ITU-T Rec. Q.822 : 1994":
suspectIntervalFlag | {0 0 17 822 0 7 14} | BOOLEAN | m? | | m | | – | | +| 38 | "ITU-T Rec. Q.822 : 1994":
thresholdDataInstance | {0 0 17 822 0 7 16} | SET OF CHOICE | c16 | | c16 | | c16 | | +| 39 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
weekMask | {2 9 3 2 7 71} | SET OF SEQUENCE | c17 | | c17 | | c17 | | + +**Table 32.4/Q.823.1 – tmCircuitEndPointSubgroupCurrentData Attribute support (continued)** + +| 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 | c5 | | c5 | | c5 | | | +| 13 | – | | – | | – | | | +| 14 | – | | – | | – | | | +| 15 | – | | – | | – | | | +| 16 | – | | – | | – | | | +| 17 | – | | – | | – | | | +| 18 | – | | – | | – | | | +| 19 | – | | – | | – | | | +| 20 | – | | – | | – | | | +| 21 | – | | – | | – | | | +| 22 | c14 | | c14 | | – | | | +| 23 | – | | – | | – | | | +| 24 | – | | – | | – | | | +| 25 | – | | – | | – | | | +| 26 | – | | – | | – | | | + +**Table 32.4/Q.823.1 – tmCircuitEndPointSubgroupCurrentData Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 27 | – | | – | | – | | | +| 28 | – | | – | | – | | | +| 29 | – | | – | | – | | | +| 30 | – | | – | | – | | | +| 31 | c14 | | c14 | | – | | | +| 32 | – | | – | | – | | | +| 33 | – | | – | | – | | | +| 34 | – | | – | | – | | | +| 35 | – | | – | | c6 | | | +| 36 | – | | – | | – | | | +| 37 | – | | – | | m | | | +| 38 | c16 | | c16 | | – | | | +| 39 | c17 | | c17 | | c17 | | | + +**Table 32.5/Q.823.1 – tmCircuitEndPointSubgroupCurrentData Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 32.6/Q.823.1 – tmCircuitEndPointSubgroupCurrentData Action support** + +There are no actions specified for this managed object class. + +**Table 32.7/Q.823.1 – tmCircuitEndPointSubgroupCurrentData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | c2 | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | c4 | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | c4 | | | | + +**Table 32.7/Q.823.1 – tmCircuitEndPointSubgroupCurrentData +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 | "Rec. X.721 ISO/IEC
10165-2 : 1992":
qualityofServiceAlarm | {2 9 3 2 10 11} | | c16 | | | "Rec. Q.821:
1992":
correlatedRecor
dNameParamete
r

"Rec. Q.821:
1992":
logRecordIdPar
ameter

"Rec. Q.821:
1992":
suspectObjectLi
stParameter | +| 5 | "ITU-T Rec. X.738":
scanReport | {2 9 2 13 10 2} | | c14 | | | | +| 6 | "Rec. X.721 ISO/IEC
10165-2 : 1992":
stateChange | {2 9 3 2 10 14} | | c15 | | | | + +**Table 32.7/Q.823.1 – tmCircuitEndPointSubgroupCurrentData +Notification support (continued)** + +| 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 | c2 | | | +| | 1.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 1.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | c: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 | c:m | | | +| | 1.1.3.1 | attributeID | – | CHOICE | c:m | | | +| | 1.1.3.1.1 | globalForm | – | OBJECT
IDENTIFIER | c:o.2 | | | +| | 1.1.3.1.2 | localForm | – | INTEGER | c:o.2 | | | +| | 1.1.3.2 | oldAttributeValue | – | ANY DEFINED
BY attributeID | c:o | | | +| | 1.1.3.3 | newAttributeValue | – | ANY DEFINED
BY attributeID | c:m | | | + +**Table 32.7/Q.823.1 – tmCircuitEndPointSubgroupCurrentData +Notification support (continued)** + +| 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.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 1.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 1.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 1.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | c4 | | | +| | 2.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 2.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c: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 | c:o | | | +| | 2.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | | | + +**Table 32.7/Q.823.1 – tmCircuitEndPointSubgroupCurrentData +Notification support (continued)** + +| 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.4.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.5 | | | +| | 2.1.4.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 2.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 2.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | c4 | | | +| | 3.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 3.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c: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 | c:o | | | +| | 3.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | + +**Table 32.7/Q.823.1 – tmCircuitEndPointSubgroupCurrentData +Notification support (continued)** + +| 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.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 3.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 3.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 3.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 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 | c16 | | | +| | 4.1.1 | probableCause | {2 9 3 2 7 18} | CHOICE | c:m | | | +| | 4.1.1.1 | globalValue | – | OBJECT IDENTIFIER | c:o.8 | | | +| | 4.1.1.2 | localValue | – | INTEGER | c:o.8 | | | +| | 4.1.2 | specificProblems | {2 9 3 2 7 27} | SET OF CHOICE | c:o | | | +| | 4.1.2.1 | OBJECT IDENTIFIER | – | OBJECT IDENTIFIER | c:o.9 | | | +| | 4.1.2.2 | INTEGER | – | INTEGER | c:o.9 | | | +| | 4.1.3 | perceivedSeverity | {2 9 3 2 7 17} | ENUMERATED | c:m | | | +| | 4.1.4 | backedUpStatus | {2 9 3 2 7 11} | BOOLEAN | c:o | | | +| | 4.1.5 | backUpObject | {2 9 3 2 7 40} | CHOICE | c:o | | | +| | 4.1.5.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.5.2 | nonSpecificForm | – | OCTET STRING | c:o.10 | | | +| | 4.1.5.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | + +**Table 32.7/Q.823.1 – tmCircuitEndPointSubgroupCurrentData +Notification support (continued)** + +| 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.5.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.6 | trendIndication | {2 9 3 2 7 30} | ENUMERATED | c:o | | | +| | 4.1.7 | thresholdInfo | {2 9 3 2 7 29} | SEQUENCE | c:o | | | +| | 4.1.7.1 | triggeredThreshold | – | CHOICE | c:m | | | +| | 4.1.7.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.11 | | | +| | 4.1.7.1.2 | localForm | – | INTEGER | c:o.11 | | | +| | 4.1.7.2 | observedValue | – | CHOICE | c:m | | | +| | 4.1.7.2.1 | integer | – | INTEGER | c:o.12 | | | +| | 4.1.7.2.2 | real | – | REAL | c:o.12 | | | +| | 4.1.7.3 | thresholdLevel | – | CHOICE | c:o | | | +| | 4.1.7.3.1 | up | – | SEQUENCE | c:o.13 | | | +| | 4.1.7.3.1.1 | high | – | CHOICE | c:m | | | +| | 4.1.7.3.1.1.1 | integer | – | INTEGER | c:o.14 | | | +| | 4.1.7.3.1.1.2 | real | – | REAL | c:o.14 | | | +| | 4.1.7.3.1.2 | low | – | CHOICE | c:o | | | +| | 4.1.7.3.1.2.1 | integer | – | INTEGER | c:o.15 | | | +| | 4.1.7.3.1.2.2 | real | – | REAL | c:o.15 | | | +| | 4.1.7.3.2 | down | – | SEQUENCE | c:o.13 | | | +| | 4.1.7.3.2.1 | high | – | CHOICE | c:m | | | +| | 4.1.7.3.2.1.1 | integer | – | INTEGER | c:o.16 | | | +| | 4.1.7.3.2.1.2 | real | – | REAL | c:o.16 | | | +| | 4.1.7.3.2.2 | low | – | CHOICE | c:m | | | +| | 4.1.7.3.2.2.1 | integer | – | INTEGER | c:o.17 | | | +| | 4.1.7.3.2.2.2 | real | – | REAL | c:o.17 | | | +| | 4.1.7.4 | armTime | – | GeneralizedTime | c:o | | | +| | 4.1.8 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 4.1.9 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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.18 | | | +| | 4.1.9.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.9.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.9.2.2 | nonSpecificForm | – | OCTET STRING | c:o.18 | | | + +**Table 32.7/Q.823.1 – tmCircuitEndPointSubgroupCurrentData +Notification support (continued)** + +| 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.9.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.18 | | | +| | 4.1.9.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.9.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.10 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | c:o | | | +| | 4.1.10.1 | attributeID | – | CHOICE | c:m | | | +| | 4.1.10.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.19 | | | +| | 4.1.10.1.2 | localForm | – | INTEGER | c:o.19 | | | +| | 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 | c:o | | | +| | 4.1.11.1 | attributeId | – | CHOICE | c:m | | | +| | 4.1.11.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.20 | | | +| | 4.1.11.1.2 | localForm | – | INTEGER | c:o.20 | | | +| | 4.1.11.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 4.1.12 | proposedRepairActions | {2 9 3 2 7 19} | SET OF CHOICE | c:o | | | +| | 4.1.12.1 | OBJECT IDENTIFIER | – | OBJECT IDENTIFIER | c:o.21 | | | +| | 4.1.12.2 | INTEGER | – | INTEGER | c:o.21 | | | +| | 4.1.13 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 4.1.14 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | ScanReportInformation | | Information Syntax
SEQUENCE | c14 | | | +| | 5.1.1 | scanInitiationTime | {2 9 2 13 7 22} | GeneralizedTime | c:o | | | +| | 5.1.2 | onceReportAttributeList | {2 9 2 13 7 17} | SET OF SEQUENCE | c:o | | | +| | 5.1.2.1 | attributeId | – | CHOICE | c:m | | | + +**Table 32.7/Q.823.1 – tmCircuitEndPointSubgroupCurrentData +Notification support (continued)** + +| 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.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.22 | | | +| | 5.1.2.1.2 | localForm | – | INTEGER | c:o.22 | | | +| | 5.1.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 5.1.3 | observationScanList | {2 9 2 13 7 15} | SET OF SEQUENCE | c:m | | | +| | 5.1.3.1 | observedObjectInstance | – | CHOICE | c:o | | | +| | 5.1.3.1.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.23 | | | +| | 5.1.3.1.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.3.1.1.2 | attributeValue | – | ANY | c:m | | | +| | 5.1.3.1.2 | nonSpecificForm | – | OCTET STRING | c:o.23 | | | +| | 5.1.3.1.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.23 | | | +| | 5.1.3.1.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.3.1.3.2 | attributeValue | – | ANY | c:m | | | +| | 5.1.3.2 | attributeMeasureList | – | SET OF SEQUENCE | c:o | | | +| | 5.1.3.2.1 | attributeId | – | CHOICE | c:m | | | +| | 5.1.3.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.24 | | | +| | 5.1.3.2.1.2 | localForm | – | INTEGER | c:o.24 | | | +| | 5.1.3.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:o | | | +| | 5.1.3.2.3 | timeStamp | – | CHOICE | c:o | | | +| | 5.1.3.2.3.1 | days | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.2 | hours | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.3 | minutes | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.4 | seconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.5 | milliSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.6 | microSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.7 | nanoSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.8 | picoSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.4 | suspectFlag | – | BOOLEAN | c:o | | | +| | 5.1.3.3 | numericValueArray | – | SEQUENCE OF CHOICE | c:o | | | + +**Table 32.7/Q.823.1 – tmCircuitEndPointSubgroupCurrentData +Notification support (continued)** + +| 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.3.3.1 | missingData | – | NULL | c:o.26 | | | +| | 5.1.3.3.2 | valueOnly | – | CHOICE | c:o.26 | | | +| | 5.1.3.3.2.1 | integer | – | INTEGER | c:o.27 | | | +| | 5.1.3.3.2.2 | real | – | REAL | c:o.27 | | | +| | 5.1.3.3.3 | qualifiedValue | – | SEQUENCE | c:o.26 | | | +| | 5.1.3.3.3.1 | value | – | CHOICE | c:m | | | +| | 5.1.3.3.3.1.1 | integer | – | INTEGER | c:o.28 | | | +| | 5.1.3.3.3.1.2 | real | – | REAL | c:o.28 | | | +| | 5.1.3.3.3.2 | timeStamp | – | CHOICE | c:o | | | +| | 5.1.3.3.3.2.1 | days | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.2 | hours | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.3 | minutes | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.4 | seconds | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.5 | milliSeconds | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.6 | microSeconds | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.7 | nanoSeconds | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.8 | picoSeconds | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.3 | suspectFlag | – | BOOLEAN | c:o | | | +| | 5.1.4 | incompleteScan | {2 9 2 13 7 30} | INTEGER | c:o | | | +| | 5.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 5.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 5.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 5.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | +| 6 | 6.1 | StateChangeInfo | | Information Syntax
SEQUENCE | c!5 | | | +| | 6.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 6.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | c:o | | | +| | 6.1.2.1 | globalForm | – | OBJECT IDENTIFIER | c:o.30 | | | +| | 6.1.2.2 | localForm | – | INTEGER | c:o.30 | | | +| | 6.1.3 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | c:m | | | +| | 6.1.3.1 | attributeID | – | CHOICE | c:m | | | +| | 6.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.31 | | | + +**Table 32.7/Q.823.1 – tmCircuitEndPointSubgroupCurrentData +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 | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|-----------------------------|--------|---------|------------------------| +| | 6.1.3.1.2 | localForm | – | INTEGER | c:o.31 | | | +| | 6.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | c:o | | | +| | 6.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | c:m | | | +| | 6.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 6.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c:o | | | +| | 6.1.5.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 6.1.5.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 6.1.5.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.32 | | | +| | 6.1.5.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 6.1.5.2.2 | nonSpecificForm | – | OCTET STRING | c:o.32 | | | +| | 6.1.5.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.32 | | | +| | 6.1.5.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 6.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 6.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 6.1.7.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.7.2 | significance | – | BOOLEAN | c:o | | | +| | 6.1.7.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 32.8/Q.823.1 – tmCircuitEndPointSubgroupCurrentData Parameter support** + +| Index | Parameter template label | Value of object identifier for parameter | Constraints and values | Status | Support | Additional information | +|-------|--------------------------------------------------|------------------------------------------|----------------------------------|--------|---------|------------------------| +| 1 | "Rec. Q.821:1992": correlatedRecordNameParameter | {0 0 17 821 0 5 2} | EVENT-INFO qualityofServiceAlarm | c16 | | | +| 2 | "Rec. Q.821:1992": logRecordIdParameter | {0 0 17 821 0 5 1} | EVENT-INFO qualityofServiceAlarm | c16 | | | +| 3 | "Rec. Q.821:1992": suspectObjectListParameter | {0 0 17 821 0 5 3} | EVENT-INFO qualityofServiceAlarm | c16 | | | + +**Table 32.9/Q.823.1 – tmCircuitEndPointSubgroupCurrentData Conditions** + +| Condition number | Condition | Reference | +|------------------|-------------------------|---------------------------------------------------------------------------------------------------------| +| c1 | IF 5.3/2 THEN m ELSE – | "this performance measurement is supported by the NE" | +| c2 | IF 5.3/3 THEN m ELSE – | "notification of attribute value change events is required" | +| c3 | IF 5.3/4 THEN m ELSE – | "the managed object can be scheduled" | +| c4 | IF 5.3/6 THEN m ELSE – | "notification of object creation and object deletion events is required" | +| c5 | IF 5.3/8 THEN m ELSE – | "daily scheduling is required and the weekly or external scheduling package is not present" | +| c6 | IF 5.3/9 THEN m ELSE – | "the scanning function is to be enabled between specified start and stop times" | +| c7 | IF 5.3/10 THEN m ELSE – | "reference to external scheduler is required and the daily or weekly scheduling package is not present" | +| c8 | IF 5.3/11 THEN m ELSE – | "an instance supports it and the zeroSuppressionPkg is not present" | +| c9 | IF 5.3/12 THEN m ELSE – | "historyData objects are to be created at the end of an interval." | +| c10 | IF 5.3/13 THEN m ELSE – | "an instance supports it and at least one of zeroSuppressionPkg or filterSuppressionPkg is present." | +| c11 | IF 5.3/14 THEN m ELSE – | "an instance supports it or the object class is currentData" | +| c12 | IF 5.3/15 THEN m ELSE – | "suppression counts are required and the filterSuppressionPkg or the zeroSuppressionPkg is present." | +| c13 | IF 5.3/17 THEN m ELSE – | "any registered package, other than this package has been instantiated" | +| c14 | IF 5.3/20 THEN m ELSE – | "scheduled notifications are to be emitted." | +| c15 | IF 5.3/21 THEN m ELSE – | "notification of state change event is required" | +| c16 | IF 5.3/22 THEN m ELSE – | "a Quality of Service Alarm Notification is to be emitted for threshold crossing." | +| c17 | IF 5.3/25 THEN m ELSE – | "weekly scheduling is required and the daily or external scheduling package is not present" | +| c18 | IF 5.3/26 THEN m ELSE – | "an instance supports it and the filterSuppressionPkg is not present." | + +**Table 32.10/Q.823.1 – tmCircuitEndPointSubgroupCurrentData Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|----------------------------------------------------------------|---------------------------------------------|---------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | tmCircuitEndPointSubgroupCurrentData-tmCircuitEndPointSubgroup | {0 0 17 823 0 5 16} | Superior class:
tmCircuitEndPointSubgroup
AND SUBCLASSES | o | | | +| 2 | "ITU-T Rec. X.738":
conflictingPackagesScanner-system | {2 9 2 13 6 9} | Superior class:
"Rec. X.721 ISO/IEC 10165-2 : 1992":
system
AND SUBCLASSES | o | | | + +**Table 32.10/Q.823.1 – tmCircuitEndPointSubgroupCurrentData +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 | | – | | | +| | 1.5 | Delete only if no contained objects | | – | | | +| | 1.6 | Delete contained objects | | – | | | +| 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 | | | + +### 33 tmExchangeCurrentData ["Q.823"] + +**Table 33.1/Q.823.1 – tmExchangeCurrentData 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 | tmExchangeCurrentData | {0 0 17 823 0 3 28} | | | + +**Table 33.2/Q.823.1 – tmExchangeCurrentData 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 33.3/Q.823.1 – tmExchangeCurrentData Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | "Rec. M.3100 : 1992": attributeValueChangeNotificationPackage | {0 0 13 3100 0 4 4} | "notification of attribute value change events is required" | c1 | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": availabilityStatusPackage | {2 9 3 2 4 22} | "the managed object can be scheduled" | c2 | | | + +**Table 33.3/Q.823.1 – tmExchangeCurrentData Package support (continued)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|---------------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 4 | "Rec. M.3100 : 1992":
createDeleteNotifications
Package | {0 0 13 3100 0 4 10} | "notification of object creation and object deletion events is required" | c3 | | | +| 5 | "ITU-T Rec. Q.822 : 1994":
currentDataPkg | | Mandatory | m | | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
dailyScheduling | {2 9 3 2 4 25} | "daily scheduling is required and the weekly or external scheduling package is not present" | c4 | | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
duration | {2 9 3 2 4 26} | "the scanning function is to be enabled between specified start and stop times" | c5 | | | +| 8 | exchangeCurrentDataPackage | | Mandatory | m | | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
externalScheduler | {2 9 3 2 4 27} | "reference to external scheduler is required and the daily or weekly scheduling package is not present" | c6 | | | +| 10 | "ITU-T Rec. Q.822 : 1994":
filterSuppressionPkg | {0 0 17 822 0 4 2} | "an instance supports it and the zeroSuppressionPkg is not present" | c7 | | | +| 11 | "ITU-T Rec. Q.822 : 1994":
historyRetentionPkg | {0 0 17 822 0 4 6} | "historyData objects are to be created at the end of an interval." | c8 | | | +| 12 | "ITU-T Rec. Q.822 : 1994":
maxSuppressedIntervalsPkg | {0 0 17 822 0 4 7} | "an instance supports it and at least one of zeroSuppressionPkg or filterSuppressionPkg is present." | c9 | | | +| 13 | "ITU-T Rec. Q.822 : 1994":
measurementListPkg | {0 0 17 822 0 4 8} | "an instance supports it or the object class is currentData" | c10 | | | +| 14 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervalsPkg | {0 0 17 822 0 4 9} | "suppression counts are required and the filterSuppressionPkg or the zeroSuppressionPkg is present." | c11 | | | +| 15 | "ITU-T Rec. Q.822 : 1994":
observedManagedObjectPkg | {0 0 17 822 0 4 11} | "an instance supports it." | o | | | +| 16 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c12 | | | +| 17 | "ITU-T Rec. X.739":
periodSynchronizationPackage | {2 9 2 11 4 10} | Mandatory | m | | | +| 18 | "ITU-T Rec. X.739":
scannerPackage | | Mandatory | m | | | +| 19 | "ITU-T Rec. Q.822 : 1994":
scheduledPMReportPkg | {0 0 17 822 0 4 12} | "scheduled notifications are to be emitted." | c13 | | | + +**Table 33.3/Q.823.1 – tmExchangeCurrentData Package support (concluded)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|---------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 20 | "Rec. M.3100 : 1992": stateChangeNotificationPackage | {0 0 13 3100 0 4 28} | "notification of state change event is required" | c14 | | | +| 21 | "ITU-T Rec. Q.822 : 1994": thresholdPkg | {0 0 17 822 0 4 13} | "a Quality of Service Alarm Notification is to be emitted for threshold crossing." | c15 | | | +| 22 | tmExchangeCurrentDataPackage | | Mandatory | m | | | +| 23 | "Rec. X.721 ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | +| 24 | "Rec. X.721 ISO/IEC 10165-2 : 1992": weeklyScheduling | {2 9 3 2 4 29} | "weekly scheduling is required and the daily or external scheduling package is not present" | c16 | | | +| 25 | "ITU-T Rec. Q.822 : 1994": zeroSuppressionPkg | {0 0 17 822 0 4 15} | "an instance supports it and the filterSuppressionPkg is not present." | c17 | | | + +**Table 33.4/Q.823.1 – tmExchangeCurrentData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": administrativeState | {2 9 3 2 7 31} | ENUMERATED | m | | m | | m | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": availabilityStatus | {2 9 3 2 7 33} | SET OF INTEGER | c2? | | c2 | | – | | +| 4 | callsBlockedByLoadShedding | {0 0 17 823 0 6 17} | INTEGER | m? | | – | | – | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992": discriminatorConstruct | {2 9 3 2 7 56} | CHOICE | c7 | | c7 | | c7 | | +| 6 | "ITU-T Rec. Q.822 : 1994": elapsedTime | {0 0 17 822 0 7 2} | CHOICE | m? | | m | | – | | +| 7 | "ITU-T Rec. X.739": granularityPeriod | {2 9 2 11 7 23} | CHOICE | m | | m | | m | | +| 8 | "ITU-T Rec. Q.822 : 1994": historyRetention | {0 0 17 822 0 7 5} | INTEGER | m? | | m | | – | | +| 9 | incomingTraffic | {0 0 17 823 0 6 32} | INTEGER | m? | | – | | – | | + +**Table 33.4/Q.823.1 – tmExchangeCurrentData 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 | +| 10 | internalTraffic | {0 0 17 823 0 6 34} | INTEGER | m? | | – | | – | | +| 11 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
intervalsOfDay | {2 9 3 2 7 57} | SET OF SEQUENCE | c4 | | c4 | | c4 | | +| 12 | "ITU-T Rec. Q.822 : 1994":
maxSuppressedIntervals | {0 0 17 822 0 7 6} | INTEGER | c9 | | c9 | | c9 | | +| 13 | "ITU-T Rec. Q.822 : 1994":
measurementList | {0 0 17 822 0 7 7} | SET OF SEQUENCE | c10 | | c10 | | c10 | | +| 14 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 15 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervals | {0 0 17 822 0 7 9} | INTEGER | c11? | | c11 | | – | | +| 16 | "ITU-T Rec. X.738":
numericAttributeIdArray | {2 9 2 13 7 10} | SEQUENCE OF CHOICE | c13 | | c13 | | c13 | | +| 17 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 18 | "ITU-T Rec. Q.822 : 1994":
observedObjectClass | {0 0 17 822 0 7 10} | CHOICE | o? | | o | | – | | +| 19 | "ITU-T Rec. X.739":
observedObjectInstance | {2 9 2 11 7 16} | CHOICE | o? | | o | | – | | +| 20 | "ITU-T Rec. X.738":
onceReportAttributeIdList | {2 9 2 13 7 16} | SET OF CHOICE | c13 | | c13 | | c13 | | +| 21 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
operationalState | {2 9 3 2 7 35} | ENUMERATED | – | | m | | – | | +| 22 | originatingTraffic | {0 0 17 823 0 6 43} | INTEGER | m? | | – | | – | | +| 23 | outgoingTraffic | {0 0 17 823 0 6 46} | INTEGER | m? | | – | | – | | +| 24 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c12 | | – | | +| 25 | "ITU-T Rec. X.739":
periodSynchronizationTime | {2 9 2 11 7 24} | GeneralizedTime | m | | m | | m | | +| 26 | "ITU-T Rec. Q.822 : 1994":
reportAllAttributes | {0 0 17 822 0 7 11} | BOOLEAN | c15 | | c15 | | c15 | | +| 27 | "ITU-T Rec. X.738":
scanAttributeIdList | {2 9 2 13 7 21} | SET OF CHOICE | c13 | | c13 | | c13 | | +| 28 | "ITU-T Rec. X.739":
scannerId | {2 9 2 11 7 25} | CHOICE | m? | | m | | – | | + +**Table 33.4/Q.823.1 – tmExchangeCurrentData 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 | +| 29 | "Rec. X.721 ISO/IEC 10165-2 : 1992": schedulerName | {2 9 3 2 7 67} | CHOICE | c6? | | c6 | | – | | +| 30 | "Rec. X.721 ISO/IEC 10165-2 : 1992": startTime | {2 9 3 2 7 68} | GeneralizedTime | c5 | | c5 | | c5 | | +| 31 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stopTime | {2 9 3 2 7 69} | CHOICE | c5 | | c5 | | c5 | | +| 32 | "ITU-T Rec. Q.822 : 1994": suppressAdditionalThresholds | {0 0 17 822 0 7 13} | BOOLEAN | c15 | | c15 | | c15 | | +| 33 | "ITU-T Rec. Q.822 : 1994": suspectIntervalFlag | {0 0 17 822 0 7 14} | BOOLEAN | m? | | m | | – | | +| 34 | terminatingTraffic | {0 0 17 823 0 6 56} | INTEGER | m? | | – | | – | | +| 35 | "ITU-T Rec. Q.822 : 1994": thresholdDataInstance | {0 0 17 822 0 7 16} | SET OF CHOICE | c15 | | c15 | | c15 | | +| 36 | transitTraffic | {0 0 17 823 0 6 63} | INTEGER | m? | | – | | – | | +| 37 | "Rec. X.721 ISO/IEC 10165-2 : 1992": weekMask | {2 9 3 2 7 71} | SET OF SEQUENCE | c16 | | c16 | | c16 | | + +**Table 33.4/Q.823.1 – tmExchangeCurrentData Attribute support (continued)** + +| 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 | c4 | | c4 | | c4 | | | +| 12 | – | | – | | – | | | +| 13 | – | | – | | – | | | +| 14 | – | | – | | – | | | + +**Table 33.4/Q.823.1 – tmExchangeCurrentData Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 15 | – | | – | | – | | | +| 16 | – | | – | | – | | | +| 17 | – | | – | | – | | | +| 18 | – | | – | | – | | | +| 19 | – | | – | | – | | | +| 20 | c13 | | c13 | | – | | | +| 21 | – | | – | | – | | | +| 22 | – | | – | | – | | | +| 23 | – | | – | | – | | | +| 24 | – | | – | | – | | | +| 25 | – | | – | | – | | | +| 26 | – | | – | | – | | | +| 27 | c13 | | c13 | | – | | | +| 28 | – | | – | | – | | | +| 29 | – | | – | | – | | | +| 30 | – | | – | | – | | | +| 31 | – | | – | | c5 | | | +| 32 | – | | – | | – | | | +| 33 | – | | – | | m | | | +| 34 | – | | – | | – | | | +| 35 | c15 | | c15 | | – | | | +| 36 | – | | – | | – | | | +| 37 | c16 | | c16 | | c16 | | | + +**Table 33.5/Q.823.1 – tmExchangeCurrentData Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 33.6/Q.823.1 – tmExchangeCurrentData Action support** + +There are no actions specified for this managed object class. + +**Table 33.7/Q.823.1 – tmExchangeCurrentData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | c1 | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | c3 | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | c3 | | | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": qualityofServiceAlarm | {2 9 3 2 10 11} | | c15 | | | "Rec. Q.821: 1992": correlatedRecordNameParameter
"Rec. Q.821: 1992": logRecordIdParameter
"Rec. Q.821: 1992": suspectObjectListParameter | +| 5 | "ITU-T Rec. X.738": scanReport | {2 9 2 13 10 2} | | c13 | | | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stateChange | {2 9 3 2 10 14} | | c14 | | | | + +**Table 33.7/Q.823.1 – tmExchangeCurrentData Notification support (continued)** + +| 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 | c1 | | | +| | 1.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 1.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | c: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 | c:m | | | +| | 1.1.3.1 | attributeID | – | CHOICE | c:m | | | + +**Table 33.7/Q.823.1 – tmExchangeCurrentData Notification support (continued)** + +| 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.3.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.2 | | | +| | 1.1.3.1.2 | localForm | – | INTEGER | c:o.2 | | | +| | 1.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | c:o | | | +| | 1.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | c:m | | | +| | 1.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 1.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 1.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 1.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | c3 | | | +| | 2.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 2.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c: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 | | | + +**Table 33.7/Q.823.1 – tmExchangeCurrentData Notification support (continued)** + +| 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.3 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 2.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 2.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 2.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | c3 | | | +| | 3.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 3.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c: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 | c:o | | | +| | 3.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | | | + +**Table 33.7/Q.823.1 – tmExchangeCurrentData Notification support (continued)** + +| 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.4.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.7 | | | +| | 3.1.4.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 3.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 3.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 3.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 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 | c15 | | | +| | 4.1.1 | probableCause | {2 9 3 2 7 18} | CHOICE | c:m | | | +| | 4.1.1.1 | globalValue | – | OBJECT IDENTIFIER | c:o.8 | | | +| | 4.1.1.2 | localValue | – | INTEGER | c:o.8 | | | +| | 4.1.2 | specificProblems | {2 9 3 2 7 27} | SET OF CHOICE | c:o | | | +| | 4.1.2.1 | OBJECT IDENTIFIER | – | OBJECT IDENTIFIER | c:o.9 | | | +| | 4.1.2.2 | INTEGER | – | INTEGER | c:o.9 | | | +| | 4.1.3 | perceivedSeverity | {2 9 3 2 7 17} | ENUMERATED | c:m | | | +| | 4.1.4 | backedUpStatus | {2 9 3 2 7 11} | BOOLEAN | c:o | | | +| | 4.1.5 | backUpObject | {2 9 3 2 7 40} | CHOICE | c:o | | | +| | 4.1.5.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.5.2 | nonSpecificForm | – | OCTET STRING | c:o.10 | | | +| | 4.1.5.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | + +**Table 33.7/Q.823.1 – tmExchangeCurrentData Notification support (continued)** + +| 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.5.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.6 | trendIndication | {2 9 3 2 7 30} | ENUMERATED | c:o | | | +| | 4.1.7 | thresholdInfo | {2 9 3 2 7 29} | SEQUENCE | c:o | | | +| | 4.1.7.1 | triggeredThreshold | – | CHOICE | c:m | | | +| | 4.1.7.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.11 | | | +| | 4.1.7.1.2 | localForm | – | INTEGER | c:o.11 | | | +| | 4.1.7.2 | observedValue | – | CHOICE | c:m | | | +| | 4.1.7.2.1 | integer | – | INTEGER | c:o.12 | | | +| | 4.1.7.2.2 | real | – | REAL | c:o.12 | | | +| | 4.1.7.3 | thresholdLevel | – | CHOICE | c:o | | | +| | 4.1.7.3.1 | up | – | SEQUENCE | c:o.13 | | | +| | 4.1.7.3.1.1 | high | – | CHOICE | c:m | | | +| | 4.1.7.3.1.1.1 | integer | – | INTEGER | c:o.14 | | | +| | 4.1.7.3.1.1.2 | real | – | REAL | c:o.14 | | | +| | 4.1.7.3.1.2 | low | – | CHOICE | c:o | | | +| | 4.1.7.3.1.2.1 | integer | – | INTEGER | c:o.15 | | | +| | 4.1.7.3.1.2.2 | real | – | REAL | c:o.15 | | | +| | 4.1.7.3.2 | down | – | SEQUENCE | c:o.13 | | | +| | 4.1.7.3.2.1 | high | – | CHOICE | c:m | | | +| | 4.1.7.3.2.1.1 | integer | – | INTEGER | c:o.16 | | | +| | 4.1.7.3.2.1.2 | real | – | REAL | c:o.16 | | | +| | 4.1.7.3.2.2 | low | – | CHOICE | c:m | | | +| | 4.1.7.3.2.2.1 | integer | – | INTEGER | c:o.17 | | | +| | 4.1.7.3.2.2.2 | real | – | REAL | c:o.17 | | | +| | 4.1.7.4 | armTime | – | GeneralizedTime | c:o | | | +| | 4.1.8 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 4.1.9 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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.18 | | | +| | 4.1.9.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.9.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.9.2.2 | nonSpecificForm | – | OCTET STRING | c:o.18 | | | + +**Table 33.7/Q.823.1 – tmExchangeCurrentData Notification support (continued)** + +| 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.9.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.18 | | | +| | 4.1.9.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.9.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.10 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | c:o | | | +| | 4.1.10.1 | attributeID | – | CHOICE | c:m | | | +| | 4.1.10.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.19 | | | +| | 4.1.10.1.2 | localForm | – | INTEGER | c:o.19 | | | +| | 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 | c:o | | | +| | 4.1.11.1 | attributeId | – | CHOICE | c:m | | | +| | 4.1.11.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.20 | | | +| | 4.1.11.1.2 | localForm | – | INTEGER | c:o.20 | | | +| | 4.1.11.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 4.1.12 | proposedRepairActions | {2 9 3 2 7 19} | SET OF CHOICE | c:o | | | +| | 4.1.12.1 | OBJECT IDENTIFIER | – | OBJECT IDENTIFIER | c:o.21 | | | +| | 4.1.12.2 | INTEGER | – | INTEGER | c:o.21 | | | +| | 4.1.13 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 4.1.14 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | ScanReportInformation | | Information Syntax
SEQUENCE | c:l3 | | | +| | 5.1.1 | scanInitiationTime | {2 9 2 13 7 22} | GeneralizedTime | c:o | | | +| | 5.1.2 | onceReportAttributeList | {2 9 2 13 7 17} | SET OF SEQUENCE | c:o | | | +| | 5.1.2.1 | attributeId | – | CHOICE | c:m | | | +| | 5.1.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.22 | | | + +**Table 33.7/Q.823.1 – tmExchangeCurrentData Notification support (continued)** + +| 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.2.1.2 | localForm | – | INTEGER | c:o.22 | | | +| | 5.1.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 5.1.3 | observationScanList | {2 9 2 13 7 15} | SET OF SEQUENCE | c:m | | | +| | 5.1.3.1 | observedObjectInstance | – | CHOICE | c:o | | | +| | 5.1.3.1.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.23 | | | +| | 5.1.3.1.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.3.1.1.2 | attributeValue | – | ANY | c:m | | | +| | 5.1.3.1.2 | nonSpecificForm | – | OCTET STRING | c:o.23 | | | +| | 5.1.3.1.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.23 | | | +| | 5.1.3.1.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.3.1.3.2 | attributeValue | – | ANY | c:m | | | +| | 5.1.3.2 | attributeMeasureList | – | SET OF SEQUENCE | c:o | | | +| | 5.1.3.2.1 | attributeId | – | CHOICE | c:m | | | +| | 5.1.3.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.24 | | | +| | 5.1.3.2.1.2 | localForm | – | INTEGER | c:o.24 | | | +| | 5.1.3.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:o | | | +| | 5.1.3.2.3 | timeStamp | – | CHOICE | c:o | | | +| | 5.1.3.2.3.1 | days | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.2 | hours | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.3 | minutes | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.4 | seconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.5 | milliSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.6 | microSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.7 | nanoSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.8 | picoSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.4 | suspectFlag | – | BOOLEAN | c:o | | | +| | 5.1.3.3 | numericValueArray | – | SEQUENCE OF CHOICE | c:o | | | +| | 5.1.3.3.1 | missingData | – | NULL | c:o.26 | | | +| | 5.1.3.3.2 | valueOnly | – | CHOICE | c:o.26 | | | +| | 5.1.3.3.2.1 | integer | – | INTEGER | c:o.27 | | | +| | 5.1.3.3.2.2 | real | – | REAL | c:o.27 | | | + +**Table 33.7/Q.823.1 – tmExchangeCurrentData Notification support (continued)** + +| 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.3.3.3 | qualifiedValue | – | SEQUENCE | c:o:26 | | | +| | 5.1.3.3.3.1 | value | – | CHOICE | c:m | | | +| | 5.1.3.3.3.1.1 | integer | – | INTEGER | c:o:28 | | | +| | 5.1.3.3.3.1.2 | real | – | REAL | c:o:28 | | | +| | 5.1.3.3.3.2 | timeStamp | – | CHOICE | c:o | | | +| | 5.1.3.3.3.2.1 | days | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.2 | hours | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.3 | minutes | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.4 | seconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.5 | milliSeconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.6 | microSeconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.7 | nanoSeconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.8 | picoSeconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.3 | suspectFlag | – | BOOLEAN | c:o | | | +| | 5.1.4 | incompleteScan | {2 9 2 13 7 30} | INTEGER | c:o | | | +| | 5.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 5.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 5.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 5.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | +| 6 | 6.1 | StateChangeInfo | | Information Syntax
SEQUENCE | c14 | | | +| | 6.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 6.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | c:o | | | +| | 6.1.2.1 | globalForm | – | OBJECT IDENTIFIER | c:o:30 | | | +| | 6.1.2.2 | localForm | – | INTEGER | c:o:30 | | | +| | 6.1.3 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | c:m | | | +| | 6.1.3.1 | attributeID | – | CHOICE | c:m | | | +| | 6.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o:31 | | | +| | 6.1.3.1.2 | localForm | – | INTEGER | c:o:31 | | | +| | 6.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | c:o | | | +| | 6.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | c:m | | | +| | 6.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | + +**Table 33.7/Q.823.1 – tmExchangeCurrentData 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 | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|-----------------------------|--------|---------|------------------------| +| | 6.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c:o | | | +| | 6.1.5.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 6.1.5.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 6.1.5.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o:32 | | | +| | 6.1.5.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 6.1.5.2.2 | nonSpecificForm | – | OCTET STRING | c:o:32 | | | +| | 6.1.5.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o:32 | | | +| | 6.1.5.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 6.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 6.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 6.1.7.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.7.2 | significance | – | BOOLEAN | c:o | | | +| | 6.1.7.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 33.8/Q.823.1 – tmExchangeCurrentData Parameter support** + +| Index | Parameter template label | Value of object identifier for parameter | Constraints and values | Status | Support | Additional information | +|-------|---------------------------------------------------------------|------------------------------------------|-------------------------------------|--------|---------|------------------------| +| 1 | "Recommendation Q.821:1992":
correlatedRecordNameParameter | {0 0 17 821 0 5 2} | EVENT-INFO
qualityofServiceAlarm | c15 | | | +| 2 | "Recommendation Q.821:1992":
logRecordIdParameter | {0 0 17 821 0 5 1} | EVENT-INFO
qualityofServiceAlarm | c15 | | | +| 3 | "Recommendation Q.821:1992":
suspectObjectListParameter | {0 0 17 821 0 5 3} | EVENT-INFO
qualityofServiceAlarm | c15 | | | + +**Table 33.9/Q.823.1 – tmExchangeCurrentData Conditions** + +| Condition number | Condition | Reference | +|------------------|-------------------------|---------------------------------------------------------------------------------------------------------| +| c1 | IF 6.3/2 THEN m ELSE – | "notification of attribute value change events is required" | +| c2 | IF 6.3/3 THEN m ELSE – | "the managed object can be scheduled" | +| c3 | IF 6.3/4 THEN m ELSE – | "notification of object creation and object deletion events is required" | +| c4 | IF 6.3/6 THEN m ELSE – | "daily scheduling is required and the weekly or external scheduling package is not present" | +| c5 | IF 6.3/7 THEN m ELSE – | "the scanning function is to be enabled between specified start and stop times" | +| c6 | IF 6.3/9 THEN m ELSE – | "reference to external scheduler is required and the daily or weekly scheduling package is not present" | +| c7 | IF 6.3/10 THEN m ELSE – | "an instance supports it and the zeroSuppressionPkg is not present" | +| c8 | IF 6.3/11 THEN m ELSE – | "historyData objects are to be created at the end of an interval." | +| c9 | IF 6.3/12 THEN m ELSE – | "an instance supports it and at least one of zeroSuppressionPkg or filterSuppressionPkg is present." | +| c10 | IF 6.3/13 THEN m ELSE – | "an instance supports it or the object class is currentData" | +| c11 | IF 6.3/14 THEN m ELSE – | "suppression counts are required and the filterSuppressionPkg or the zeroSuppressionPkg is present." | +| c12 | IF 6.3/16 THEN m ELSE – | "any registered package, other than this package has been instantiated" | +| c13 | IF 6.3/19 THEN m ELSE – | "scheduled notifications are to be emitted." | +| c14 | IF 6.3/20 THEN m ELSE – | "notification of state change event is required" | +| c15 | IF 6.3/21 THEN m ELSE – | "a Quality of Service Alarm Notification is to be emitted for threshold crossing." | +| c16 | IF 6.3/24 THEN m ELSE – | "weekly scheduling is required and the daily or external scheduling package is not present" | +| c17 | IF 6.3/25 THEN m ELSE – | "an instance supports it and the filterSuppressionPkg is not present." | + +**Table 33.10/Q.823.1 – tmExchangeCurrentData Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|----------------------------------------------------------|---------------------------------------------|------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | tmExchangeCurrentData-managedElement | {0 0 17 823 0 5 17} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | +| 2 | "ITU-T Rec. X.738":
conflictingPackagesScanner-system | {2 9 2 13 6 9} | Superior class:
"Rec. X.721 ISO/IEC
10165-2 : 1992":
system
AND SUBCLASSES | o | | | + +**Table 33.10/Q.823.1 – tmExchangeCurrentData 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 | | – | | | +| | 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 | | | + +### 34 tmObservedDestinationCurrentData ["Q.823"] + +**Table 34.1/Q.823.1 – tmObservedDestinationCurrentData 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 | tmObservedDestinationCurrentData | {0 0 17 823 0 3 29} | | | + +**Table 34.2/Q.823.1 – tmObservedDestinationCurrentData 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 34.3/Q.823.1 – tmObservedDestinationCurrentData Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | "Rec. M.3100 : 1992": attributeValueChangeNotificationPackage | {0 0 13 3100 0 4 4} | "notification of attribute value change events is required" | c1 | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": availabilityStatusPackage | {2 9 3 2 4 22} | "the managed object can be scheduled" | c2 | | | + +**Table 34.3/Q.823.1 – tmObservedDestinationCurrentData Package support (continued)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 4 | callsAffectedByDccPackage | {0 0 17 823 0 4 9} | "an instance supports it" | o | | | +| 5 | "Rec. M.3100 : 1992":
createDeleteNotificationsPackage | {0 0 13 3100 0 4 10} | "notification of object creation and object deletion events is required" | c3 | | | +| 6 | "ITU-T Rec. Q.822 : 1994":
currentDataPkg | | Mandatory | m | | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
dailyScheduling | {2 9 3 2 4 25} | "daily scheduling is required and the weekly or external scheduling package is not present" | c4 | | | +| 8 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
duration | {2 9 3 2 4 26} | "the scanning function is to be enabled between specified start and stop times" | c5 | | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
externalScheduler | {2 9 3 2 4 27} | "reference to external scheduler is required and the daily or weekly scheduling package is not present" | c6 | | | +| 10 | "ITU-T Rec. Q.822 : 1994":
filterSuppressionPkg | {0 0 17 822 0 4 2} | "an instance supports it and the zeroSuppressionPkg is not present" | c7 | | | +| 11 | "ITU-T Rec. Q.822 : 1994":
historyRetentionPkg | {0 0 17 822 0 4 6} | "historyData objects are to be created at the end of an interval." | c8 | | | +| 12 | "ITU-T Rec. Q.822 : 1994":
maxSuppressedIntervalsPkg | {0 0 17 822 0 4 7} | "an instance supports it and at least one of zeroSuppressionPkg or filterSuppressionPkg is present." | c9 | | | +| 13 | "ITU-T Rec. Q.822 : 1994":
measurementListPkg | {0 0 17 822 0 4 8} | "an instance supports it or the object class is currentData" | c10 | | | +| 14 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervalsPkg | {0 0 17 822 0 4 9} | "suppression counts are required and the filterSuppressionPkg or the zeroSuppressionPkg is present." | c11 | | | +| 15 | observedDestinationCurrentDataPackage | | Mandatory | m | | | +| 16 | "ITU-T Rec. Q.822 : 1994":
observedManagedObjectPkg | {0 0 17 822 0 4 11} | "an instance supports it." | o | | | +| 17 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c12 | | | +| 18 | "ITU-T Rec. X.739":
periodSynchronizationPackage | {2 9 2 11 4 10} | Mandatory | m | | | +| 19 | "ITU-T Rec. X.739":
scannerPackage | | Mandatory | m | | | +| 20 | "ITU-T Rec. Q.822 : 1994":
scheduledPMReportPkg | {0 0 17 822 0 4 12} | "scheduled notifications are to be emitted." | c13 | | | + +**Table 34.3/Q.823.1 – tmObservedDestinationCurrentData Package support (concluded)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|---------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 21 | "Rec. M.3100 : 1992": stateChangeNotificationPackage | {0 0 13 3100 0 4 28} | "notification of state change event is required" | c14 | | | +| 22 | "ITU-T Rec. Q.822 : 1994": thresholdPkg | {0 0 17 822 0 4 13} | "a Quality of Service Alarm Notification is to be emitted for threshold crossing." | c15 | | | +| 23 | tmObservedDestinationCurrentDataPackage | | Mandatory | m | | | +| 24 | "Rec. X.721 ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | +| 25 | "Rec. X.721 ISO/IEC 10165-2 : 1992": weeklyScheduling | {2 9 3 2 4 29} | "weekly scheduling is required and the daily or external scheduling package is not present" | c16 | | | +| 26 | "ITU-T Rec. Q.822 : 1994": zeroSuppressionPkg | {0 0 17 822 0 4 15} | "an instance supports it and the filterSuppressionPkg is not present." | c17 | | | + +**Table 34.4/Q.823.1 – tmObservedDestinationCurrentData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": administrativeState | {2 9 3 2 7 31} | ENUMERATED | m | | m | | m | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 3 | answeredOutgoingSeizures | {0 0 17 823 0 6 10} | INTEGER | m? | | – | | – | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": availabilityStatus | {2 9 3 2 7 33} | SET OF INTEGER | c2? | | c2 | | – | | +| 5 | bids | {0 0 17 823 0 6 14} | INTEGER | m? | | – | | – | | +| 6 | callsAffectedByDcc | {0 0 17 823 0 6 15} | INTEGER | o? | | – | | – | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992": discriminatorConstruct | {2 9 3 2 7 56} | CHOICE | c7 | | c7 | | c7 | | +| 8 | "ITU-T Rec. Q.822 : 1994": elapsedTime | {0 0 17 822 0 7 2} | CHOICE | m? | | m | | – | | +| 9 | "ITU-T Rec. X.739": granularityPeriod | {2 9 2 11 7 23} | CHOICE | m | | m | | m | | + +**Table 34.4/Q.823.1 – tmObservedDestinationCurrentData 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 | +| 10 | "ITU-T Rec. Q.822 : 1994": historyRetention | {0 0 17 822 0 7 5} | INTEGER | m? | | m | | – | | +| 11 | "Rec. X.721 ISO/IEC 10165-2 : 1992": intervalsOfDay | {2 9 3 2 7 57} | SET OF SEQUENCE | c4 | | c4 | | c4 | | +| 12 | "ITU-T Rec. Q.822 : 1994": maxSuppressedIntervals | {0 0 17 822 0 7 6} | INTEGER | c9 | | c9 | | c9 | | +| 13 | "ITU-T Rec. Q.822 : 1994": measurementList | {0 0 17 822 0 7 7} | SET OF SEQUENCE | c10 | | c10 | | c10 | | +| 14 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 15 | noCircuitsAvailable | {0 0 17 823 0 6 39} | INTEGER | m? | | – | | – | | +| 16 | "ITU-T Rec. Q.822 : 1994": numSuppressedIntervals | {0 0 17 822 0 7 9} | INTEGER | c11? | | c11 | | – | | +| 17 | "ITU-T Rec. X.738": numericAttributeIdArray | {2 9 2 13 7 10} | SEQUENCE OF CHOICE | c13 | | c13 | | c13 | | +| 18 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 19 | "ITU-T Rec. Q.822 : 1994": observedObjectClass | {0 0 17 822 0 7 10} | CHOICE | o? | | o | | – | | +| 20 | "ITU-T Rec. X.739": observedObjectInstance | {2 9 2 11 7 16} | CHOICE | o? | | o | | – | | +| 21 | "ITU-T Rec. X.738": onceReportAttributeIdList | {2 9 2 13 7 16} | SET OF CHOICE | c13 | | c13 | | c13 | | +| 22 | "Rec. X.721 ISO/IEC 10165-2 : 1992": operationalState | {2 9 3 2 7 35} | ENUMERATED | – | | m | | – | | +| 23 | outgoingSeizures | {0 0 17 823 0 6 45} | INTEGER | m? | | – | | – | | +| 24 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c12 | | – | | +| 25 | "ITU-T Rec. X.739": periodSynchronizationTime | {2 9 2 11 7 24} | GeneralizedTime | m | | m | | m | | +| 26 | "ITU-T Rec. Q.822 : 1994": reportAllAttributes | {0 0 17 822 0 7 11} | BOOLEAN | c15 | | c15 | | c15 | | +| 27 | "ITU-T Rec. X.738": scanAttributeIdList | {2 9 2 13 7 21} | SET OF CHOICE | c13 | | c13 | | c13 | | + +**Table 34.4/Q.823.1 – tmObservedDestinationCurrentData 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 | +| 28 | "ITU-T Rec. X.739": scannerId | {2 9 2 11 7 25} | CHOICE | m? | | m | | – | | +| 29 | "Rec. X.721 ISO/IEC 10165-2 : 1992": schedulerName | {2 9 3 2 7 67} | CHOICE | c6? | | c6 | | – | | +| 30 | "Rec. X.721 ISO/IEC 10165-2 : 1992": startTime | {2 9 3 2 7 68} | GeneralizedTime | c5 | | c5 | | c5 | | +| 31 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stopTime | {2 9 3 2 7 69} | CHOICE | c5 | | c5 | | c5 | | +| 32 | "ITU-T Rec. Q.822 : 1994": suppressAdditionalThresh holds | {0 0 17 822 0 7 13} | BOOLEAN | c15 | | c15 | | c15 | | +| 33 | "ITU-T Rec. Q.822 : 1994": suspectIntervalFlag | {0 0 17 822 0 7 14} | BOOLEAN | m? | | m | | – | | +| 34 | "ITU-T Rec. Q.822 : 1994": thresholdDataInstance | {0 0 17 822 0 7 16} | SET OF CHOICE | c15 | | c15 | | c15 | | +| 35 | "Rec. X.721 ISO/IEC 10165-2 : 1992": weekMask | {2 9 3 2 7 71} | SET OF SEQUENCE | c16 | | c16 | | c16 | | + +**Table 34.4/Q.823.1 – tmObservedDestinationCurrentData Attribute support (continued)** + +| 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 | c4 | | c4 | | c4 | | | +| 12 | – | | – | | – | | | +| 13 | – | | – | | – | | | +| 14 | – | | – | | – | | | + +**Table 34.4/Q.823.1 – tmObservedDestinationCurrentData Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 15 | – | | – | | – | | | +| 16 | – | | – | | – | | | +| 17 | – | | – | | – | | | +| 18 | – | | – | | – | | | +| 19 | – | | – | | – | | | +| 20 | – | | – | | – | | | +| 21 | c13 | | c13 | | – | | | +| 22 | – | | – | | – | | | +| 23 | – | | – | | – | | | +| 24 | – | | – | | – | | | +| 25 | – | | – | | – | | | +| 26 | – | | – | | – | | | +| 27 | c13 | | c13 | | – | | | +| 28 | – | | – | | – | | | +| 29 | – | | – | | – | | | +| 30 | – | | – | | – | | | +| 31 | – | | – | | c5 | | | +| 32 | – | | – | | – | | | +| 33 | – | | – | | m | | | +| 34 | c15 | | c15 | | – | | | +| 35 | c16 | | c16 | | c16 | | | + +**Table 34.5/Q.823.1 – tmObservedDestinationCurrentData Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 34.6/Q.823.1 – tmObservedDestinationCurrentData Action support** + +There are no actions specified for this managed object class. + +**Table 34.7/Q.823.1 – tmObservedDestinationCurrentData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | c1 | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | c3 | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | c3 | | | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": qualityOfServiceAlarm | {2 9 3 2 10 11} | | c15 | | | "Rec. Q.821: 1992": correlatedRecordNameParameter
"Rec. Q.821: 1992": logRecordIdParameter
"Rec. Q.821: 1992": suspectObjectListParameter | +| 5 | "ITU-T Rec. X.738": scanReport | {2 9 2 13 10 2} | | c13 | | | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stateChange | {2 9 3 2 10 14} | | c14 | | | | + +**Table 34.7/Q.823.1 – tmObservedDestinationCurrentData Notification support (continued)** + +| 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 | c1 | | | +| | 1.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 1.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | c: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 | c:m | | | +| | 1.1.3.1 | attributeID | – | CHOICE | c:m | | | + +**Table 34.7/Q.823.1 – tmObservedDestinationCurrentData Notification support (continued)** + +| 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.3.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.2 | | | +| | 1.1.3.1.2 | localForm | – | INTEGER | c:o.2 | | | +| | 1.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | c:o | | | +| | 1.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | c:m | | | +| | 1.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 1.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 1.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 1.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | c3 | | | +| | 2.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 2.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c: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 | | | + +**Table 34.7/Q.823.1 – tmObservedDestinationCurrentData Notification support (continued)** + +| 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.3 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 2.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 2.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 2.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | c3 | | | +| | 3.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 3.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c: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 | c:o | | | +| | 3.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | | | + +**Table 34.7/Q.823.1 – tmObservedDestinationCurrentData Notification support (continued)** + +| 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.4.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.7 | | | +| | 3.1.4.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 3.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 3.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 3.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 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 | c15 | | | +| | 4.1.1 | probableCause | {2 9 3 2 7 18} | CHOICE | c:m | | | +| | 4.1.1.1 | globalValue | – | OBJECT IDENTIFIER | c:o.8 | | | +| | 4.1.1.2 | localValue | – | INTEGER | c:o.8 | | | +| | 4.1.2 | specificProblems | {2 9 3 2 7 27} | SET OF CHOICE | c:o | | | +| | 4.1.2.1 | OBJECT IDENTIFIER | – | OBJECT IDENTIFIER | c:o.9 | | | +| | 4.1.2.2 | INTEGER | – | INTEGER | c:o.9 | | | +| | 4.1.3 | perceivedSeverity | {2 9 3 2 7 17} | ENUMERATED | c:m | | | +| | 4.1.4 | backedUpStatus | {2 9 3 2 7 11} | BOOLEAN | c:o | | | +| | 4.1.5 | backUpObject | {2 9 3 2 7 40} | CHOICE | c:o | | | +| | 4.1.5.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.5.2 | nonSpecificForm | – | OCTET STRING | c:o.10 | | | +| | 4.1.5.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | + +**Table 34.7/Q.823.1 – tmObservedDestinationCurrentData Notification support (continued)** + +| 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.5.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.6 | trendIndication | {2 9 3 2 7 30} | ENUMERATED | c:o | | | +| | 4.1.7 | thresholdInfo | {2 9 3 2 7 29} | SEQUENCE | c:o | | | +| | 4.1.7.1 | triggeredThreshold | – | CHOICE | c:m | | | +| | 4.1.7.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.11 | | | +| | 4.1.7.1.2 | localForm | – | INTEGER | c:o.11 | | | +| | 4.1.7.2 | observedValue | – | CHOICE | c:m | | | +| | 4.1.7.2.1 | integer | – | INTEGER | c:o.12 | | | +| | 4.1.7.2.2 | real | – | REAL | c:o.12 | | | +| | 4.1.7.3 | thresholdLevel | – | CHOICE | c:o | | | +| | 4.1.7.3.1 | up | – | SEQUENCE | c:o.13 | | | +| | 4.1.7.3.1.1 | high | – | CHOICE | c:m | | | +| | 4.1.7.3.1.1.1 | integer | – | INTEGER | c:o.14 | | | +| | 4.1.7.3.1.1.2 | real | – | REAL | c:o.14 | | | +| | 4.1.7.3.1.2 | low | – | CHOICE | c:o | | | +| | 4.1.7.3.1.2.1 | integer | – | INTEGER | c:o.15 | | | +| | 4.1.7.3.1.2.2 | real | – | REAL | c:o.15 | | | +| | 4.1.7.3.2 | down | – | SEQUENCE | c:o.13 | | | +| | 4.1.7.3.2.1 | high | – | CHOICE | c:m | | | +| | 4.1.7.3.2.1.1 | integer | – | INTEGER | c:o.16 | | | +| | 4.1.7.3.2.1.2 | real | – | REAL | c:o.16 | | | +| | 4.1.7.3.2.2 | low | – | CHOICE | c:m | | | +| | 4.1.7.3.2.2.1 | integer | – | INTEGER | c:o.17 | | | +| | 4.1.7.3.2.2.2 | real | – | REAL | c:o.17 | | | +| | 4.1.7.4 | armTime | – | GeneralizedTime | c:o | | | +| | 4.1.8 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 4.1.9 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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.18 | | | +| | 4.1.9.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.9.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.9.2.2 | nonSpecificForm | – | OCTET STRING | c:o.18 | | | + +**Table 34.7/Q.823.1 – tmObservedDestinationCurrentData Notification support (continued)** + +| 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.9.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.18 | | | +| | 4.1.9.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.9.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.10 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | c:o | | | +| | 4.1.10.1 | attributeID | – | CHOICE | c:m | | | +| | 4.1.10.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.19 | | | +| | 4.1.10.1.2 | localForm | – | INTEGER | c:o.19 | | | +| | 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 | c:o | | | +| | 4.1.11.1 | attributeId | – | CHOICE | c:m | | | +| | 4.1.11.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.20 | | | +| | 4.1.11.1.2 | localForm | – | INTEGER | c:o.20 | | | +| | 4.1.11.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 4.1.12 | proposedRepairActions | {2 9 3 2 7 19} | SET OF CHOICE | c:o | | | +| | 4.1.12.1 | OBJECT IDENTIFIER | – | OBJECT IDENTIFIER | c:o.21 | | | +| | 4.1.12.2 | INTEGER | – | INTEGER | c:o.21 | | | +| | 4.1.13 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 4.1.14 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | ScanReportInformation | | Information Syntax
SEQUENCE | c!3 | | | +| | 5.1.1 | scanInitiationTime | {2 9 2 13 7 22} | GeneralizedTime | c:o | | | +| | 5.1.2 | onceReportAttributeList | {2 9 2 13 7 17} | SET OF SEQUENCE | c:o | | | +| | 5.1.2.1 | attributeId | – | CHOICE | c:m | | | +| | 5.1.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.22 | | | + +**Table 34.7/Q.823.1 – tmObservedDestinationCurrentData Notification support (continued)** + +| 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.2.1.2 | localForm | – | INTEGER | c:o.22 | | | +| | 5.1.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 5.1.3 | observationScanList | {2 9 2 13 7 15} | SET OF SEQUENCE | c:m | | | +| | 5.1.3.1 | observedObjectInstance | – | CHOICE | c:o | | | +| | 5.1.3.1.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.23 | | | +| | 5.1.3.1.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.3.1.1.2 | attributeValue | – | ANY | c:m | | | +| | 5.1.3.1.2 | nonSpecificForm | – | OCTET STRING | c:o.23 | | | +| | 5.1.3.1.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.23 | | | +| | 5.1.3.1.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.3.1.3.2 | attributeValue | – | ANY | c:m | | | +| | 5.1.3.2 | attributeMeasureList | – | SET OF SEQUENCE | c:o | | | +| | 5.1.3.2.1 | attributeId | – | CHOICE | c:m | | | +| | 5.1.3.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.24 | | | +| | 5.1.3.2.1.2 | localForm | – | INTEGER | c:o.24 | | | +| | 5.1.3.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:o | | | +| | 5.1.3.2.3 | timeStamp | – | CHOICE | c:o | | | +| | 5.1.3.2.3.1 | days | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.2 | hours | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.3 | minutes | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.4 | seconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.5 | milliSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.6 | microSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.7 | nanoSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.8 | picoSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.4 | suspectFlag | – | BOOLEAN | c:o | | | +| | 5.1.3.3 | numericValueArray | – | SEQUENCE OF CHOICE | c:o | | | +| | 5.1.3.3.1 | missingData | – | NULL | c:o.26 | | | +| | 5.1.3.3.2 | valueOnly | – | CHOICE | c:o.26 | | | +| | 5.1.3.3.2.1 | integer | – | INTEGER | c:o.27 | | | +| | 5.1.3.3.2.2 | real | – | REAL | c:o.27 | | | + +**Table 34.7/Q.823.1 – tmObservedDestinationCurrentData Notification support (continued)** + +| 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.3.3.3 | qualifiedValue | – | SEQUENCE | c:o:26 | | | +| | 5.1.3.3.3.1 | value | – | CHOICE | c:m | | | +| | 5.1.3.3.3.1.1 | integer | – | INTEGER | c:o:28 | | | +| | 5.1.3.3.3.1.2 | real | – | REAL | c:o:28 | | | +| | 5.1.3.3.3.2 | timeStamp | – | CHOICE | c:o | | | +| | 5.1.3.3.3.2.1 | days | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.2 | hours | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.3 | minutes | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.4 | seconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.5 | milliSeconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.6 | microSeconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.7 | nanoSeconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.8 | picoSeconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.3 | suspectFlag | – | BOOLEAN | c:o | | | +| | 5.1.4 | incompleteScan | {2 9 2 13 7 30} | INTEGER | c:o | | | +| | 5.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 5.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 5.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 5.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | +| 6 | 6.1 | StateChangeInfo | | Information Syntax
SEQUENCE | c14 | | | +| | 6.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 6.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | c:o | | | +| | 6.1.2.1 | globalForm | – | OBJECT IDENTIFIER | c:o:30 | | | +| | 6.1.2.2 | localForm | – | INTEGER | c:o:30 | | | +| | 6.1.3 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | c:m | | | +| | 6.1.3.1 | attributeID | – | CHOICE | c:m | | | +| | 6.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o:31 | | | +| | 6.1.3.1.2 | localForm | – | INTEGER | c:o:31 | | | +| | 6.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | c:o | | | +| | 6.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | c:m | | | +| | 6.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | + +**Table 34.7/Q.823.1 – tmObservedDestinationCurrentData 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 | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|-----------------------------|--------|---------|------------------------| +| | 6.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c:o | | | +| | 6.1.5.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 6.1.5.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 6.1.5.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o:32 | | | +| | 6.1.5.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 6.1.5.2.2 | nonSpecificForm | – | OCTET STRING | c:o:32 | | | +| | 6.1.5.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o:32 | | | +| | 6.1.5.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 6.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 6.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 6.1.7.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.7.2 | significance | – | BOOLEAN | c:o | | | +| | 6.1.7.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 34.8/Q.823.1 – tmObservedDestinationCurrentData Parameter support** + +| Index | Parameter template label | Value of object identifier for parameter | Constraints and values | Status | Support | Additional information | +|-------|--------------------------------------------------|------------------------------------------|----------------------------------|--------|---------|------------------------| +| 1 | "Rec. Q.821:1992": correlatedRecordNameParameter | {0 0 17 821 0 5 2} | EVENT-INFO qualityofServiceAlarm | c15 | | | +| 2 | "Rec. Q.821:1992": logRecordIdParameter | {0 0 17 821 0 5 1} | EVENT-INFO qualityofServiceAlarm | c15 | | | +| 3 | "Rec. Q.821:1992": suspectObjectListParameter | {0 0 17 821 0 5 3} | EVENT-INFO qualityofServiceAlarm | c15 | | | + +**Table 34.9/Q.823.1 – tmObservedDestinationCurrentData Conditions** + +| Condition number | Condition | Reference | +|------------------|-------------------------|---------------------------------------------------------------------------------------------------------| +| c1 | IF 7.3/2 THEN m ELSE – | "notification of attribute value change events is required" | +| c2 | IF 7.3/3 THEN m ELSE – | "the managed object can be scheduled" | +| c3 | IF 7.3/5 THEN m ELSE – | "notification of object creation and object deletion events is required" | +| c4 | IF 7.3/7 THEN m ELSE – | "daily scheduling is required and the weekly or external scheduling package is not present" | +| c5 | IF 7.3/8 THEN m ELSE – | "the scanning function is to be enabled between specified start and stop times" | +| c6 | IF 7.3/9 THEN m ELSE – | "reference to external scheduler is required and the daily or weekly scheduling package is not present" | +| c7 | IF 7.3/10 THEN m ELSE – | "an instance supports it and the zeroSuppressionPkg is not present" | +| c8 | IF 7.3/11 THEN m ELSE – | "historyData objects are to be created at the end of an interval." | +| c9 | IF 7.3/12 THEN m ELSE – | "an instance supports it and at least one of zeroSuppressionPkg or filterSuppressionPkg is present." | +| c10 | IF 7.3/13 THEN m ELSE – | "an instance supports it or the object class is currentData" | +| c11 | IF 7.3/14 THEN m ELSE – | "suppression counts are required and the filterSuppressionPkg or the zeroSuppressionPkg is present." | +| c12 | IF 7.3/17 THEN m ELSE – | "any registered package, other than this package has been instantiated" | +| c13 | IF 7.3/20 THEN m ELSE – | "scheduled notifications are to be emitted." | +| c14 | IF 7.3/21 THEN m ELSE – | "notification of state change event is required" | +| c15 | IF 7.3/22 THEN m ELSE – | "a Quality of Service Alarm Notification is to be emitted for threshold crossing." | +| c16 | IF 7.3/25 THEN m ELSE – | "weekly scheduling is required and the daily or external scheduling package is not present" | +| c17 | IF 7.3/26 THEN m ELSE – | "an instance supports it and the filterSuppressionPkg is not present." | + +**Table 34.10/Q.823.1 – tmObservedDestinationCurrentData Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|----------------------------------------------------------|---------------------------------------------|------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | tmObservedDestinationCurrentData-observedDestination | {0 0 17 823 0 5 18} | Superior class:
observedDestination
AND SUBCLASSES | o | | | +| 2 | "ITU-T Rec. X.738":
conflictingPackagesScanner-system | {2 9 2 13 6 9} | Superior class:
"Rec. X.721 ISO/IEC
10165-2 : 1992":
system
AND SUBCLASSES | o | | | + +**Table 34.10/Q.823.1 – tmObservedDestinationCurrentData +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 | | – | | | +| | 1.5 | Delete only if no contained objects | | – | | | +| | 1.6 | Delete contained objects | | – | | | +| 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 | | | + +### 35 tmTrafficControlCurrentData ["Q.823"] + +**Table 35.1/Q.823.1 – tmTrafficControlCurrentData 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 | tmTrafficControlCurrentData | {0 0 17 823 0 3 30} | | | + +**Table 35.2/Q.823.1 – tmTrafficControlCurrentData 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 35.3/Q.823.1 – tmTrafficControlCurrentData Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | "Rec. M.3100 : 1992": attributeValueChangeNotificationPackage | {0 0 13 3100 0 4 4} | "notification of attribute value change events is required" | c1 | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": availabilityStatusPackage | {2 9 3 2 4 22} | "the managed object can be scheduled" | c2 | | | + +**Table 35.3/Q.823.1 – tmTrafficControlCurrentData Package support (continued)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|---------------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 4 | callsOfferedPackage | {0 0 17 823 0 4 11} | "an instance supports it" | o | | | +| 5 | "Rec. M.3100 : 1992":
createDeleteNotifications
Package | {0 0 13 3100 0 4 10} | "notification of object creation and object deletion events is required" | c3 | | | +| 6 | "ITU-T Rec. Q.822 : 1994":
currentDataPkg | | Mandatory | m | | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
dailyScheduling | {2 9 3 2 4 25} | "daily scheduling is required and the weekly or external scheduling package is not present" | c4 | | | +| 8 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
duration | {2 9 3 2 4 26} | "the scanning function is to be enabled between specified start and stop times" | c5 | | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
externalScheduler | {2 9 3 2 4 27} | "reference to external scheduler is required and the daily or weekly scheduling package is not present" | c6 | | | +| 10 | "ITU-T Rec. Q.822 : 1994":
filterSuppressionPkg | {0 0 17 822 0 4 2} | "an instance supports it and the zeroSuppressionPkg is not present" | c7 | | | +| 11 | "ITU-T Rec. Q.822 : 1994":
historyRetentionPkg | {0 0 17 822 0 4 6} | "historyData objects are to be created at the end of an interval." | c8 | | | +| 12 | "ITU-T Rec. Q.822 : 1994":
maxSuppressedIntervalsPkg | {0 0 17 822 0 4 7} | "an instance supports it and at least one of zeroSuppressionPkg or filterSuppressionPkg is present." | c9 | | | +| 13 | "ITU-T Rec. Q.822 : 1994":
measurementListPkg | {0 0 17 822 0 4 8} | "an instance supports it or the object class is currentData" | c10 | | | +| 14 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervalsPkg | {0 0 17 822 0 4 9} | "suppression counts are required and the filterSuppressionPkg or the zeroSuppressionPkg is present." | c11 | | | +| 15 | "ITU-T Rec. Q.822 : 1994":
observedManagedObjectPkg | {0 0 17 822 0 4 11} | "an instance supports it." | o | | | +| 16 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c12 | | | +| 17 | "ITU-T Rec. X.739":
periodSynchronizationPackage | {2 9 2 11 4 10} | Mandatory | m | | | +| 18 | "ITU-T Rec. X.739":
scannerPackage | | Mandatory | m | | | +| 19 | "ITU-T Rec. Q.822 : 1994":
scheduledPMReportPkg | {0 0 17 822 0 4 12} | "scheduled notifications are to be emitted." | c13 | | | + +**Table 35.3/Q.823.1 – tmTrafficControlCurrentData Package support (concluded)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|---------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 20 | "Rec. M.3100 : 1992": stateChangeNotificationPackage | {0 0 13 3100 0 4 28} | "notification of state change event is required" | c14 | | | +| 21 | "ITU-T Rec. Q.822 : 1994": thresholdPkg | {0 0 17 822 0 4 13} | "a Quality of Service Alarm Notification is to be emitted for threshold crossing." | c15 | | | +| 22 | tmTrafficControlCurrentDataPackage | | Mandatory | m | | | +| 23 | "Rec. X.721 ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | +| 24 | trafficControlCurrentDataPackage | | Mandatory | m | | | +| 25 | "Rec. X.721 ISO/IEC 10165-2 : 1992": weeklyScheduling | {2 9 3 2 4 29} | "weekly scheduling is required and the daily or external scheduling package is not present" | c16 | | | +| 26 | "ITU-T Rec. Q.822 : 1994": zeroSuppressionPkg | {0 0 17 822 0 4 15} | "an instance supports it and the filterSuppressionPkg is not present." | c17 | | | + +**Table 35.4/Q.823.1 – tmTrafficControlCurrentData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": administrativeState | {2 9 3 2 7 31} | ENUMERATED | m | | m | | m | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": availabilityStatus | {2 9 3 2 7 33} | SET OF INTEGER | c2? | | c2 | | – | | +| 4 | callsAffectedByTrafficControl | {0 0 17 823 0 6 16} | INTEGER | m? | | – | | – | | +| 5 | callsOfferedToTrafficControl | {0 0 17 823 0 6 18} | INTEGER | o? | | – | | – | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": discriminatorConstruct | {2 9 3 2 7 56} | CHOICE | c7 | | c7 | | c7 | | +| 7 | "ITU-T Rec. Q.822 : 1994": elapsedTime | {0 0 17 822 0 7 2} | CHOICE | m? | | m | | – | | +| 8 | "ITU-T Rec. X.739": granularityPeriod | {2 9 2 11 7 23} | CHOICE | m | | m | | m | | + +**Table 35.4/Q.823.1 – tmTrafficControlCurrentData 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 | +| 9 | "ITU-T Rec. Q.822 : 1994":
historyRetention | {0 0 17 822 0 7 5} | INTEGER | m? | | m | | – | | +| 10 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
intervalsOfDay | {2 9 3 2 7 57} | SET OF SEQUENCE | c4 | | c4 | | c4 | | +| 11 | "ITU-T Rec. Q.822 : 1994":
maxSuppressedIntervals | {0 0 17 822 0 7 6} | INTEGER | c9 | | c9 | | c9 | | +| 12 | "ITU-T Rec. Q.822 : 1994":
measurementList | {0 0 17 822 0 7 7} | SET OF SEQUENCE | c10 | | c10 | | c10 | | +| 13 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 14 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervals | {0 0 17 822 0 7 9} | INTEGER | c11? | | c11 | | – | | +| 15 | "ITU-T Rec. X.738":
numericAttributeIdArray | {2 9 2 13 7 10} | SEQUENCE OF CHOICE | c13 | | c13 | | c13 | | +| 16 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 17 | "ITU-T Rec. Q.822 : 1994":
observedObjectClass | {0 0 17 822 0 7 10} | CHOICE | o? | | o | | – | | +| 18 | "ITU-T Rec. X.739":
observedObjectInstance | {2 9 2 11 7 16} | CHOICE | o? | | o | | – | | +| 19 | "ITU-T Rec. X.738":
onceReportAttributeIdList | {2 9 2 13 7 16} | SET OF CHOICE | c13 | | c13 | | c13 | | +| 20 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
operationalState | {2 9 3 2 7 35} | ENUMERATED | – | | m | | – | | +| 21 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c12 | | – | | +| 22 | "ITU-T Rec. X.739":
periodSynchronizationTime | {2 9 2 11 7 24} | GeneralizedTime | m | | m | | m | | +| 23 | "ITU-T Rec. Q.822 : 1994":
reportAllAttributes | {0 0 17 822 0 7 11} | BOOLEAN | c15 | | c15 | | c15 | | +| 24 | "ITU-T Rec. X.738":
scanAttributeIdList | {2 9 2 13 7 21} | SET OF CHOICE | c13 | | c13 | | c13 | | +| 25 | "ITU-T Rec. X.739":
scannerId | {2 9 2 11 7 25} | CHOICE | m? | | m | | – | | + +**Table 35.4/Q.823.1 – tmTrafficControlCurrentData 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 | +| 26 | "Rec. X.721 ISO/IEC 10165-2 : 1992": schedulerName | {2 9 3 2 7 67} | CHOICE | c6? | | c6 | | – | | +| 27 | "Rec. X.721 ISO/IEC 10165-2 : 1992": startTime | {2 9 3 2 7 68} | GeneralizedTime | c5 | | c5 | | c5 | | +| 28 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stopTime | {2 9 3 2 7 69} | CHOICE | c5 | | c5 | | c5 | | +| 29 | "ITU-T Rec. Q.822 : 1994": suppressAdditionalThresholds | {0 0 17 822 0 7 13} | BOOLEAN | c15 | | c15 | | c15 | | +| 30 | "ITU-T Rec. Q.822 : 1994": suspectIntervalFlag | {0 0 17 822 0 7 14} | BOOLEAN | m? | | m | | – | | +| 31 | "ITU-T Rec. Q.822 : 1994": thresholdDataInstance | {0 0 17 822 0 7 16} | SET OF CHOICE | c15 | | c15 | | c15 | | +| 32 | "Rec. X.721 ISO/IEC 10165-2 : 1992": weekMask | {2 9 3 2 7 71} | SET OF SEQUENCE | c16 | | c16 | | c16 | | + +**Table 35.4/Q.823.1 – tmTrafficControlCurrentData Attribute support (continued)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | – | | | +| 5 | – | | – | | – | | | +| 6 | – | | – | | – | | | +| 7 | – | | – | | – | | | +| 8 | – | | – | | – | | | +| 9 | – | | – | | – | | | +| 10 | c4 | | c4 | | c4 | | | +| 11 | – | | – | | – | | | +| 12 | – | | – | | – | | | +| 13 | – | | – | | – | | | +| 14 | – | | – | | – | | | +| 15 | – | | – | | – | | | +| 16 | – | | – | | – | | | + +**Table 35.4/Q.823.1 – tmTrafficControlCurrentData Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 17 | – | | – | | – | | | +| 18 | – | | – | | – | | | +| 19 | c13 | | c13 | | – | | | +| 20 | – | | – | | – | | | +| 21 | – | | – | | – | | | +| 22 | – | | – | | – | | | +| 23 | – | | – | | – | | | +| 24 | c13 | | c13 | | – | | | +| 25 | – | | – | | – | | | +| 26 | – | | – | | – | | | +| 27 | – | | – | | – | | | +| 28 | – | | – | | c5 | | | +| 29 | – | | – | | – | | | +| 30 | – | | – | | m | | | +| 31 | c15 | | c15 | | – | | | +| 32 | c16 | | c16 | | c16 | | | + +**Table 35.5/Q.823.1 – tmTrafficControlCurrentData Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 35.6/Q.823.1 – tmTrafficControlCurrentData Action support** + +There are no actions specified for this managed object class. + +**Table 35.7/Q.823.1 – tmTrafficControlCurrentData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | c1 | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | c3 | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | c3 | | | | + +**Table 35.7/Q.823.1 – tmTrafficControlCurrentData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": qualityofServiceAlarm | {2 9 3 2 10 11} | | c15 | | | "Rec. Q.821: 1992":
correlatedRecordNameParameter
"Rec. Q.821: 1992":
logRecordIdParameter
"Rec. Q.821: 1992":
suspectObjectListParameter | +| 5 | "ITU-T Rec. X.738": scanReport | {2 9 2 13 10 2} | | c13 | | | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stateChange | {2 9 3 2 10 14} | | c14 | | | | + +**Table 35.7/Q.823.1 – tmTrafficControlCurrentData Notification support (continued)** + +| 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 | c1 | | | +| | 1.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 1.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | c: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 | c:m | | | +| | 1.1.3.1 | attributeID | – | CHOICE | c:m | | | +| | 1.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.2 | | | +| | 1.1.3.1.2 | localForm | – | INTEGER | c:o.2 | | | +| | 1.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | c:o | | | +| | 1.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | c:m | | | +| | 1.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | + +**Table 35.7/Q.823.1 – tm TrafficControlCurrentData Notification support (continued)** + +| 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 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 1.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 1.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | c3 | | | +| | 2.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 2.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c: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 | c:o | | | +| | 2.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | | | + +**Table 35.7/Q.823.1 – tmTrafficControlCurrentData Notification support (continued)** + +| 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.4.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 2.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 2.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | c3 | | | +| | 3.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 3.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c: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 | c:o | | | +| | 3.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | | | + +**Table 35.7/Q.823.1 – tm TrafficControlCurrentData Notification support (continued)** + +| 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.4.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 3.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 3.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 3.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 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 | c!5 | | | +| | 4.1.1 | probableCause | {2 9 3 2 7 18} | CHOICE | c:m | | | +| | 4.1.1.1 | globalValue | – | OBJECT IDENTIFIER | c:o.8 | | | +| | 4.1.1.2 | localValue | – | INTEGER | c:o.8 | | | +| | 4.1.2 | specificProblems | {2 9 3 2 7 27} | SET OF CHOICE | c:o | | | +| | 4.1.2.1 | OBJECT IDENTIFIER | – | OBJECT IDENTIFIER | c:o.9 | | | +| | 4.1.2.2 | INTEGER | – | INTEGER | c:o.9 | | | +| | 4.1.3 | perceivedSeverity | {2 9 3 2 7 17} | ENUMERATED | c:m | | | +| | 4.1.4 | backedUpStatus | {2 9 3 2 7 11} | BOOLEAN | c:o | | | +| | 4.1.5 | backUpObject | {2 9 3 2 7 40} | CHOICE | c:o | | | +| | 4.1.5.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.5.2 | nonSpecificForm | – | OCTET STRING | c:o.10 | | | +| | 4.1.5.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.6 | trendIndication | {2 9 3 2 7 30} | ENUMERATED | c:o | | | +| | 4.1.7 | thresholdInfo | {2 9 3 2 7 29} | SEQUENCE | c:o | | | +| | 4.1.7.1 | triggeredThreshold | – | CHOICE | c:m | | | +| | 4.1.7.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.11 | | | +| | 4.1.7.1.2 | localForm | – | INTEGER | c:o.11 | | | + +**Table 35.7/Q.823.1 – tm TrafficControlCurrentData Notification support (continued)** + +| 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.2 | observedValue | – | CHOICE | c:m | | | +| | 4.1.7.2.1 | integer | – | INTEGER | c:o.12 | | | +| | 4.1.7.2.2 | real | – | REAL | c:o.12 | | | +| | 4.1.7.3 | thresholdLevel | – | CHOICE | c:o | | | +| | 4.1.7.3.1 | up | – | SEQUENCE | c:o.13 | | | +| | 4.1.7.3.1.1 | high | – | CHOICE | c:m | | | +| | 4.1.7.3.1.1.1 | integer | – | INTEGER | c:o.14 | | | +| | 4.1.7.3.1.1.2 | real | – | REAL | c:o.14 | | | +| | 4.1.7.3.1.2 | low | – | CHOICE | c:o | | | +| | 4.1.7.3.1.2.1 | integer | – | INTEGER | c:o.15 | | | +| | 4.1.7.3.1.2.2 | real | – | REAL | c:o.15 | | | +| | 4.1.7.3.2 | down | – | SEQUENCE | c:o.13 | | | +| | 4.1.7.3.2.1 | high | – | CHOICE | c:m | | | +| | 4.1.7.3.2.1.1 | integer | – | INTEGER | c:o.16 | | | +| | 4.1.7.3.2.1.2 | real | – | REAL | c:o.16 | | | +| | 4.1.7.3.2.2 | low | – | CHOICE | c:m | | | +| | 4.1.7.3.2.2.1 | integer | – | INTEGER | c:o.17 | | | +| | 4.1.7.3.2.2.2 | real | – | REAL | c:o.17 | | | +| | 4.1.7.4 | armTime | – | GeneralizedTime | c:o | | | +| | 4.1.8 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 4.1.9 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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.18 | | | +| | 4.1.9.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.9.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.9.2.2 | nonSpecificForm | – | OCTET STRING | c:o.18 | | | +| | 4.1.9.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.18 | | | +| | 4.1.9.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.9.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.10 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | c:o | | | +| | 4.1.10.1 | attributeID | – | CHOICE | c:m | | | +| | 4.1.10.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.19 | | | + +**Table 35.7/Q.823.1 – tm TrafficControlCurrentData Notification support (continued)** + +| 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.10.1.2 | localForm | – | INTEGER | c:o.19 | | | +| | 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 | c:o | | | +| | 4.1.11.1 | attributeId | – | CHOICE | c:m | | | +| | 4.1.11.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.20 | | | +| | 4.1.11.1.2 | localForm | – | INTEGER | c:o.20 | | | +| | 4.1.11.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 4.1.12 | proposedRepairActions | {2 9 3 2 7 19} | SET OF CHOICE | c:o | | | +| | 4.1.12.1 | OBJECT IDENTIFIER | – | OBJECT IDENTIFIER | c:o.21 | | | +| | 4.1.12.2 | INTEGER | – | INTEGER | c:o.21 | | | +| | 4.1.13 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 4.1.14 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | ScanReportInformation | | Information Syntax
SEQUENCE | c!3 | | | +| | 5.1.1 | scanInitiationTime | {2 9 2 13 7 22} | GeneralizedTime | c:o | | | +| | 5.1.2 | onceReportAttributeList | {2 9 2 13 7 17} | SET OF SEQUENCE | c:o | | | +| | 5.1.2.1 | attributeId | – | CHOICE | c:m | | | +| | 5.1.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.22 | | | +| | 5.1.2.1.2 | localForm | – | INTEGER | c:o.22 | | | +| | 5.1.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 5.1.3 | observationScanList | {2 9 2 13 7 15} | SET OF SEQUENCE | c:m | | | +| | 5.1.3.1 | observedObjectInstance | – | CHOICE | c:o | | | +| | 5.1.3.1.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.23 | | | +| | 5.1.3.1.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | + +**Table 35.7/Q.823.1 – tm TrafficControlCurrentData Notification support (continued)** + +| 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.3.1.1.2 | attributeValue | – | ANY | c:m | | | +| | 5.1.3.1.2 | nonSpecificForm | – | OCTET STRING | c:o.23 | | | +| | 5.1.3.1.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.23 | | | +| | 5.1.3.1.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.3.1.3.2 | attributeValue | – | ANY | c:m | | | +| | 5.1.3.2 | attributeMeasureList | – | SET OF SEQUENCE | c:o | | | +| | 5.1.3.2.1 | attributeId | – | CHOICE | c:m | | | +| | 5.1.3.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.24 | | | +| | 5.1.3.2.1.2 | localForm | – | INTEGER | c:o.24 | | | +| | 5.1.3.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:o | | | +| | 5.1.3.2.3 | timeStamp | – | CHOICE | c:o | | | +| | 5.1.3.2.3.1 | days | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.2 | hours | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.3 | minutes | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.4 | seconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.5 | milliSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.6 | microSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.7 | nanoSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.8 | picoSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.4 | suspectFlag | – | BOOLEAN | c:o | | | +| | 5.1.3.3 | numericValueArray | – | SEQUENCE OF CHOICE | c:o | | | +| | 5.1.3.3.1 | missingData | – | NULL | c:o.26 | | | +| | 5.1.3.3.2 | valueOnly | – | CHOICE | c:o.26 | | | +| | 5.1.3.3.2.1 | integer | – | INTEGER | c:o.27 | | | +| | 5.1.3.3.2.2 | real | – | REAL | c:o.27 | | | +| | 5.1.3.3.3 | qualifiedValue | – | SEQUENCE | c:o.26 | | | +| | 5.1.3.3.3.1 | value | – | CHOICE | c:m | | | +| | 5.1.3.3.3.1.1 | integer | – | INTEGER | c:o.28 | | | +| | 5.1.3.3.3.1.2 | real | – | REAL | c:o.28 | | | +| | 5.1.3.3.3.2 | timeStamp | – | CHOICE | c:o | | | +| | 5.1.3.3.3.2.1 | days | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.2 | hours | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.3 | minutes | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.4 | seconds | – | INTEGER | c:o.29 | | | + +**Table 35.7/Q.823.1 – tm TrafficControlCurrentData Notification support (continued)** + +| 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.3.3.3.2.5 | milliSeconds | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.6 | microSeconds | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.7 | nanoSeconds | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.2.8 | picoSeconds | – | INTEGER | c:o.29 | | | +| | 5.1.3.3.3.3 | suspectFlag | – | BOOLEAN | c:o | | | +| | 5.1.4 | incompleteScan | {2 9 2 13 7 30} | INTEGER | c:o | | | +| | 5.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 5.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 5.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 5.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | +| 6 | 6.1 | StateChangeInfo | | Information Syntax
SEQUENCE | c14 | | | +| | 6.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 6.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | c:o | | | +| | 6.1.2.1 | globalForm | – | OBJECT IDENTIFIER | c:o.30 | | | +| | 6.1.2.2 | localForm | – | INTEGER | c:o.30 | | | +| | 6.1.3 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | c:m | | | +| | 6.1.3.1 | attributeID | – | CHOICE | c:m | | | +| | 6.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.31 | | | +| | 6.1.3.1.2 | localForm | – | INTEGER | c:o.31 | | | +| | 6.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | c:o | | | +| | 6.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | c:m | | | +| | 6.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 6.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c:o | | | +| | 6.1.5.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 6.1.5.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 6.1.5.2.1 | distinguishedName | – | SEQUENCE OF
SET OF
SEQUENCE | c:o.32 | | | +| | 6.1.5.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | + +**Table 35.7/Q.823.1 – tmTrafficControlCurrentData 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 | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|-----------------------------|--------|---------|------------------------| +| | 6.1.5.2.2 | nonSpecificForm | – | OCTET STRING | c:o.32 | | | +| | 6.1.5.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.32 | | | +| | 6.1.5.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 6.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 6.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 6.1.7.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.7.2 | significance | – | BOOLEAN | c:o | | | +| | 6.1.7.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 35.8/Q.823.1 – tmTrafficControlCurrentData Parameter support** + +| Index | Parameter template label | Value of object identifier for parameter | Constraints and values | Status | Support | Additional information | +|-------|--------------------------------------------------|------------------------------------------|----------------------------------|--------|---------|------------------------| +| 1 | "Rec. Q.821:1992": correlatedRecordNameParameter | {0 0 17 821 0 5 2} | EVENT-INFO qualityofServiceAlarm | c15 | | | +| 2 | "Rec. Q.821:1992": logRecordIdParameter | {0 0 17 821 0 5 1} | EVENT-INFO qualityofServiceAlarm | c15 | | | +| 3 | "Rec. Q.821:1992": suspectObjectListParameter | {0 0 17 821 0 5 3} | EVENT-INFO qualityofServiceAlarm | c15 | | | + +**Table 35.9/Q.823.1 – tmTrafficControlCurrentData Conditions** + +| Condition number | Condition | Reference | +|------------------|-------------------------|---------------------------------------------------------------------------------------------------------| +| c1 | IF 8.3/2 THEN m ELSE – | "notification of attribute value change events is required" | +| c2 | IF 8.3/3 THEN m ELSE – | "the managed object can be scheduled" | +| c3 | IF 8.3/5 THEN m ELSE – | "notification of object creation and object deletion events is required" | +| c4 | IF 8.3/7 THEN m ELSE – | "daily scheduling is required and the weekly or external scheduling package is not present" | +| c5 | IF 8.3/8 THEN m ELSE – | "the scanning function is to be enabled between specified start and stop times" | +| c6 | IF 8.3/9 THEN m ELSE – | "reference to external scheduler is required and the daily or weekly scheduling package is not present" | +| c7 | IF 8.3/10 THEN m ELSE – | "an instance supports it and the zeroSuppressionPkg is not present" | +| c8 | IF 8.3/11 THEN m ELSE – | "historyData objects are to be created at the end of an interval." | + +**Table 35.9/Q.823.1 – tmTrafficControlCurrentData Conditions (concluded)** + +| Condition number | Condition | Reference | +|------------------|-------------------------|------------------------------------------------------------------------------------------------------| +| c9 | IF 8.3/12 THEN m ELSE – | "an instance supports it and at least one of zeroSuppressionPkg or filterSuppressionPkg is present." | +| c10 | IF 8.3/13 THEN m ELSE – | "an instance supports it or the object class is currentData" | +| c11 | IF 8.3/14 THEN m ELSE – | "suppression counts are required and the filterSuppressionPkg or the zeroSuppressionPkg is present." | +| c12 | IF 8.3/16 THEN m ELSE – | "any registered package, other than this package has been instantiated" | +| c13 | IF 8.3/19 THEN m ELSE – | "scheduled notifications are to be emitted." | +| c14 | IF 8.3/20 THEN m ELSE – | "notification of state change event is required" | +| c15 | IF 8.3/21 THEN m ELSE – | "a Quality of Service Alarm Notification is to be emitted for threshold crossing." | +| c16 | IF 8.3/25 THEN m ELSE – | "weekly scheduling is required and the daily or external scheduling package is not present" | +| c17 | IF 8.3/26 THEN m ELSE – | "an instance supports it and the filterSuppressionPkg is not present." | + +**Table 35.10/Q.823.1 – tmTrafficControlCurrentData Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|----------------------------------------------------------|---------------------------------------------|------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | tmTrafficControlCurrentData-trafficControl | {0 0 17 823 0 5 19} | Superior class:
trafficControl
AND SUBCLASSES | o | | | +| 2 | "ITU-T Rec. X.738":
conflictingPackagesScanner-system | {2 9 2 13 6 9} | Superior class:
"Rec. X.721 ISO/IEC
10165-2 : 1992":
system
AND SUBCLASSES | o | | | + +**Table 35.10/Q.823.1 – tmTrafficControlCurrentData 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 | | – | | | +| | 1.5 | Delete only if no contained objects | | – | | | +| | 1.6 | Delete contained objects | | – | | | +| 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 | | | + +Table 36.1/Q.823.1 – trafficControl 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 | trafficControl | {0 0 17 823 0 3 31} | | | + +Table 36.2/Q.823.1 – trafficControl 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 36.3/Q.823.1 – trafficControl Package support + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | creatorPackage | {0 0 17 823 0 4 14} | "an instance supports it" | o | | | +| 3 | "Rec. M.3100 : 1992": objectManagementNotificationsPackage | {0 0 13 3100 0 4 20} | Mandatory | m | | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c1 | | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | +| 6 | trafficControlPackage | | Mandatory | m | | | + +Table 36.4/Q.823.1 – trafficControl 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 2 | creatorIdentity | {0 0 17 823 0 6 24} | CHOICE | o? | | o | | – | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | + +**Table 36.4/Q.823.1 – trafficControl 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 | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 5 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | cl | | – | | +| 6 | tmSurveillance | {0 0 17 823 0 6 60} | BOOLEAN | m | | m | | m | | +| 7 | trafficControlId | {0 0 17 823 0 6 61} | CHOICE | m? | | m | | – | | + +**Table 36.4/Q.823.1 – trafficControl Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | – | | | +| 5 | – | | – | | – | | | +| 6 | – | | – | | – | | | +| 7 | – | | – | | – | | | + +**Table 36.5/Q.823.1 – trafficControl Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 36.6/Q.823.1 – trafficControl Action support** + +There are no actions specified for this managed object class. + +**Table 36.7/Q.823.1 – trafficControl 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | m | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | m | | | | + +**Table 36.7/Q.823.1 – trafficControl Notification support (continued)** + +| 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 | | | + +**Table 36.7/Q.823.1 – trafficControl Notification support (continued)** + +| 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.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 2.1.4.2.2 | nonSpecificForm | – | OCTET STRING | c:o.5 | | | + +**Table 36.7/Q.823.1 – trafficControl Notification support (continued)** + +| 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.4.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.5 | | | +| | 2.1.4.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | + +**Table 36.7/Q.823.1 – trafficControl 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.4.2.3.2 | attributeValue | – | 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 | | | +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 36.8/Q.823.1 – trafficControl Parameter support** + +There are no parameters specified for this managed object class. + +**Table 36.9/Q.823.1 – trafficControl Conditions** + +| Condition number | Condition | Reference | +|------------------|------------------------|-------------------------------------------------------------------------| +| c1 | IF 9.3/4 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table 36.10/Q.823.1 – trafficControl Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------|---------------------------------------------|------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | trafficControl-managedElement | {0 0 17 823 0 5 20} | Superior class:
"Rec. M.3100 : 1992":
managedElement
AND SUBCLASSES | o | | | + +**Table 36.10/Q.823.1 – trafficControl 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 | | | + +### 37 trafficControlCurrentData ["Q.823"] + +**Table 37.1/Q.823.1 – trafficControlCurrentData 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 | trafficControlCurrentData | {0 0 17 823 0 3 32} | | | + +**Table 37.2/Q.823.1 – trafficControlCurrentData 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 37.3/Q.823.1 – trafficControlCurrentData Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|---------------------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | "Rec. M.3100 : 1992":
attributeValueChangeNotificationPackage | {0 0 13 3100 0 4 4} | "notification of attribute value change events is required" | c1 | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
availabilityStatusPackage | {2 9 3 2 4 22} | "the managed object can be scheduled" | c2 | | | +| 4 | callsOfferedPackage | {0 0 17 823 0 4 11} | "an instance supports it" | o | | | +| 5 | "Rec. M.3100 : 1992":
createDeleteNotificationsPackage | {0 0 13 3100 0 4 10} | "notification of object creation and object deletion events is required" | c3 | | | +| 6 | "ITU-T Rec. Q.822 : 1994":
currentDataPkg | | Mandatory | m | | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
dailyScheduling | {2 9 3 2 4 25} | "daily scheduling is required and the weekly or external scheduling package is not present" | c4 | | | +| 8 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
duration | {2 9 3 2 4 26} | "the scanning function is to be enabled between specified start and stop times" | c5 | | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
externalScheduler | {2 9 3 2 4 27} | "reference to external scheduler is required and the daily or weekly scheduling package is not present" | c6 | | | +| 10 | "ITU-T Rec. Q.822 : 1994":
filterSuppressionPkg | {0 0 17 822 0 4 2} | "an instance supports it and the zeroSuppressionPkg is not present" | c7 | | | +| 11 | "ITU-T Rec. Q.822 : 1994":
historyRetentionPkg | {0 0 17 822 0 4 6} | "historyData objects are to be created at the end of an interval." | c8 | | | + +**Table 37.3/Q.823.1 – trafficControlCurrentData Package support (concluded)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------|----------------------------------------|------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 12 | "ITU-T Rec. Q.822 : 1994":
maxSuppressedIntervalsPkg | {0 0 17 822 0 4 7} | "an instance supports it and at least one of zeroSuppressionPkg or filterSuppressionPkg is present." | c9 | | | +| 13 | "ITU-T Rec. Q.822 : 1994":
measurementListPkg | {0 0 17 822 0 4 8} | "an instance supports it or the object class is currentData" | c10 | | | +| 14 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervalsPkg | {0 0 17 822 0 4 9} | "suppression counts are required and the filterSuppressionPkg or the zeroSuppressionPkg is present." | c11 | | | +| 15 | "ITU-T Rec. Q.822 : 1994":
observedManagedObjectPkg | {0 0 17 822 0 4 11} | "an instance supports it." | o | | | +| 16 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c12 | | | +| 17 | "ITU-T Rec. X.739":
periodSynchronizationPackage | {2 9 2 11 4 10} | "configurable agent internal synchronization of repeating time periods is required" | c13 | | | +| 18 | "ITU-T Rec. X.739":
scannerPackage | | Mandatory | m | | | +| 19 | "ITU-T Rec. Q.822 : 1994":
scheduledPMReportPkg | {0 0 17 822 0 4 12} | "scheduled notifications are to be emitted." | c14 | | | +| 20 | "Rec. M.3100 : 1992":
stateChangeNotificationPackage | {0 0 13 3100 0 4 28} | "notification of state change event is required" | c15 | | | +| 21 | "ITU-T Rec. Q.822 : 1994":
thresholdPkg | {0 0 17 822 0 4 13} | "a Quality of Service Alarm Notification is to be emitted for threshold crossing." | c16 | | | +| 22 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
topPackage | | Mandatory | m | | | +| 23 | trafficControlCurrentDataPackage | | Mandatory | m | | | +| 24 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
weeklyScheduling | {2 9 3 2 4 29} | "weekly scheduling is required and the daily or external scheduling package is not present" | c17 | | | +| 25 | "ITU-T Rec. Q.822 : 1994":
zeroSuppressionPkg | {0 0 17 822 0 4 15} | "an instance supports it and the filterSuppressionPkg is not present." | c18 | | | + +**Table 37.4/Q.823.1 – trafficControlCurrentData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
administrativeState | {2 9 3 2 7 31} | ENUMERATED | m | | m | | m | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
availabilityStatus | {2 9 3 2 7 33} | SET OF INTEGER | c2? | | c2 | | – | | +| 4 | callsAffectedByTrafficControl | {0 0 17 823 0 6 16} | INTEGER | m? | | – | | – | | +| 5 | callsOfferedToTrafficControl | {0 0 17 823 0 6 18} | INTEGER | o? | | – | | – | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
discriminatorConstruct | {2 9 3 2 7 56} | CHOICE | c7 | | c7 | | c7 | | +| 7 | "ITU-T Rec. Q.822 : 1994":
elapsedTime | {0 0 17 822 0 7 2} | CHOICE | m? | | m | | – | | +| 8 | "ITU-T Rec. X.739":
granularityPeriod | {2 9 2 11 7 23} | CHOICE | m | | m | | m | | +| 9 | "ITU-T Rec. Q.822 : 1994":
historyRetention | {0 0 17 822 0 7 5} | INTEGER | c8 | | c8 | | c8 | | +| 10 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
intervalsOfDay | {2 9 3 2 7 57} | SET OF SEQUENCE | c4 | | c4 | | c4 | | +| 11 | "ITU-T Rec. Q.822 : 1994":
maxSuppressedIntervals | {0 0 17 822 0 7 6} | INTEGER | c9 | | c9 | | c9 | | +| 12 | "ITU-T Rec. Q.822 : 1994":
measurementList | {0 0 17 822 0 7 7} | SET OF SEQUENCE | c10 | | c10 | | c10 | | +| 13 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 14 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervals | {0 0 17 822 0 7 9} | INTEGER | c11? | | c11 | | – | | +| 15 | "ITU-T Rec. X.738":
numericAttributeIdArray | {2 9 2 13 7 10} | SEQUENCE OF CHOICE | c14 | | c14 | | c14 | | +| 16 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 17 | "ITU-T Rec. Q.822 : 1994":
observedObjectClass | {0 0 17 822 0 7 10} | CHOICE | o? | | o | | – | | + +**Table 37.4/Q.823.1 – trafficControlCurrentData 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 | +| 18 | "ITU-T Rec. X.739": observedObjectInstance | {2 9 2 11 7 16} | CHOICE | o? | | o | | – | | +| 19 | "ITU-T Rec. X.738": onceReportAttributeIdList | {2 9 2 13 7 16} | SET OF CHOICE | c14 | | c14 | | c14 | | +| 20 | "Rec. X.721 ISO/IEC 10165-2 : 1992": operationalState | {2 9 3 2 7 35} | ENUMERATED | – | | m | | – | | +| 21 | "Rec. X.721 ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c12 | | – | | +| 22 | "ITU-T Rec. X.739": periodSynchronizationTime | {2 9 2 11 7 24} | GeneralizedTime | c13 | | c13 | | c13 | | +| 23 | "ITU-T Rec. Q.822 : 1994": reportAllAttributes | {0 0 17 822 0 7 11} | BOOLEAN | c16 | | c16 | | c16 | | +| 24 | "ITU-T Rec. X.738": scanAttributeIdList | {2 9 2 13 7 21} | SET OF CHOICE | c14 | | c14 | | c14 | | +| 25 | "ITU-T Rec. X.739": scannerId | {2 9 2 11 7 25} | CHOICE | m? | | m | | – | | +| 26 | "Rec. X.721 ISO/IEC 10165-2 : 1992": schedulerName | {2 9 3 2 7 67} | CHOICE | c6? | | c6 | | – | | +| 27 | "Rec. X.721 ISO/IEC 10165-2 : 1992": startTime | {2 9 3 2 7 68} | GeneralizedTime | c5 | | c5 | | c5 | | +| 28 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stopTime | {2 9 3 2 7 69} | CHOICE | c5 | | c5 | | c5 | | +| 29 | "ITU-T Rec. Q.822 : 1994": suppressAdditionalThresholds | {0 0 17 822 0 7 13} | BOOLEAN | c16 | | c16 | | c16 | | +| 30 | "ITU-T Rec. Q.822 : 1994": suspectIntervalFlag | {0 0 17 822 0 7 14} | BOOLEAN | m? | | m | | – | | +| 31 | "ITU-T Rec. Q.822 : 1994": thresholdDataInstance | {0 0 17 822 0 7 16} | SET OF CHOICE | c16 | | c16 | | c16 | | +| 32 | "Rec. X.721 ISO/IEC 10165-2 : 1992": weekMask | {2 9 3 2 7 71} | SET OF SEQUENCE | c17 | | c17 | | c17 | | + +**Table 37.4/Q.823.1 – trafficControlCurrentData 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 | c4 | | c4 | | c4 | | | +| 11 | – | | – | | – | | | +| 12 | – | | – | | – | | | +| 13 | – | | – | | – | | | +| 14 | – | | – | | – | | | +| 15 | – | | – | | – | | | +| 16 | – | | – | | – | | | +| 17 | – | | – | | – | | | +| 18 | – | | – | | – | | | +| 19 | c14 | | c14 | | – | | | +| 20 | – | | – | | – | | | +| 21 | – | | – | | – | | | +| 22 | – | | – | | – | | | +| 23 | – | | – | | – | | | +| 24 | c14 | | c14 | | – | | | +| 25 | – | | – | | – | | | +| 26 | – | | – | | – | | | +| 27 | – | | – | | – | | | +| 28 | – | | – | | c5 | | | +| 29 | – | | – | | – | | | +| 30 | – | | – | | m | | | +| 31 | c16 | | c16 | | – | | | +| 32 | c17 | | c17 | | c17 | | | + +**Table 37.5/Q.823.1 – trafficControlCurrentData Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 37.6/Q.823.1 – trafficControlCurrentData Action support** + +There are no actions specified for this managed object class. + +**Table 37.7/Q.823.1 – trafficControlCurrentData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | c1 | | | | +| 2 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | c3 | | | | +| 3 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | c3 | | | | +| 4 | "Rec. X.721 ISO/IEC 10165-2 : 1992": qualityOfServiceAlarm | {2 9 3 2 10 11} | | c16 | | | "Rec. Q.821: 1992": correlatedRecordNameParameter
"Rec. Q.821: 1992": logRecordIdParameter
"Rec. Q.821: 1992": suspectObjectListParameter | +| 5 | "ITU-T Rec. X.738": scanReport | {2 9 2 13 10 2} | | c14 | | | | +| 6 | "Rec. X.721 ISO/IEC 10165-2 : 1992": stateChange | {2 9 3 2 10 14} | | c15 | | | | + +**Table 37.7/Q.823.1 – trafficControlCurrentData Notification support** + +| 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 | c1 | | | +| | 1.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 1.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | c: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 | c:m | | | +| | 1.1.3.1 | attributeID | – | CHOICE | c:m | | | + +**Table 37.7/Q.823.1 – trafficControlCurrentData Notification support (continued)** + +| 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.3.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.2 | | | +| | 1.1.3.1.2 | localForm | – | INTEGER | c:o.2 | | | +| | 1.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | c:o | | | +| | 1.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | c:m | | | +| | 1.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 1.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 1.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 1.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | c3 | | | +| | 2.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 2.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c: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 | | | + +**Table 37.7/Q.823.1 – trafficControlCurrentData Notification support (continued)** + +| 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.3 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 2.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 2.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 2.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | c3 | | | +| | 3.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 3.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c: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 | c:o | | | +| | 3.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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 | | | + +**Table 37.7/Q.823.1 – trafficControlCurrentData Notification support (continued)** + +| 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.4.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.7 | | | +| | 3.1.4.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | attributeValue | – | 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 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 3.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 3.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 3.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 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 | c!6 | | | +| | 4.1.1 | probableCause | {2 9 3 2 7 18} | CHOICE | c:m | | | +| | 4.1.1.1 | globalValue | – | OBJECT IDENTIFIER | c:o.8 | | | +| | 4.1.1.2 | localValue | – | INTEGER | c:o.8 | | | +| | 4.1.2 | specificProblems | {2 9 3 2 7 27} | SET OF CHOICE | c:o | | | +| | 4.1.2.1 | OBJECT IDENTIFIER | – | OBJECT IDENTIFIER | c:o.9 | | | +| | 4.1.2.2 | INTEGER | – | INTEGER | c:o.9 | | | +| | 4.1.3 | perceivedSeverity | {2 9 3 2 7 17} | ENUMERATED | c:m | | | +| | 4.1.4 | backedUpStatus | {2 9 3 2 7 11} | BOOLEAN | c:o | | | +| | 4.1.5 | backUpObject | {2 9 3 2 7 40} | CHOICE | c:o | | | +| | 4.1.5.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | +| | 4.1.5.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.5.2 | nonSpecificForm | – | OCTET STRING | c:o.10 | | | +| | 4.1.5.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.10 | | | + +**Table 37.7/Q.823.1 – trafficControlCurrentData Notification support (continued)** + +| 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.5.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.6 | trendIndication | {2 9 3 2 7 30} | ENUMERATED | c:o | | | +| | 4.1.7 | thresholdInfo | {2 9 3 2 7 29} | SEQUENCE | c:o | | | +| | 4.1.7.1 | triggeredThreshold | – | CHOICE | c:m | | | +| | 4.1.7.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.11 | | | +| | 4.1.7.1.2 | localForm | – | INTEGER | c:o.11 | | | +| | 4.1.7.2 | observedValue | – | CHOICE | c:m | | | +| | 4.1.7.2.1 | integer | – | INTEGER | c:o.12 | | | +| | 4.1.7.2.2 | real | – | REAL | c:o.12 | | | +| | 4.1.7.3 | thresholdLevel | – | CHOICE | c:o | | | +| | 4.1.7.3.1 | up | – | SEQUENCE | c:o.13 | | | +| | 4.1.7.3.1.1 | high | – | CHOICE | c:m | | | +| | 4.1.7.3.1.1.1 | integer | – | INTEGER | c:o.14 | | | +| | 4.1.7.3.1.1.2 | real | – | REAL | c:o.14 | | | +| | 4.1.7.3.1.2 | low | – | CHOICE | c:o | | | +| | 4.1.7.3.1.2.1 | integer | – | INTEGER | c:o.15 | | | +| | 4.1.7.3.1.2.2 | real | – | REAL | c:o.15 | | | +| | 4.1.7.3.2 | down | – | SEQUENCE | c:o.13 | | | +| | 4.1.7.3.2.1 | high | – | CHOICE | c:m | | | +| | 4.1.7.3.2.1.1 | integer | – | INTEGER | c:o.16 | | | +| | 4.1.7.3.2.1.2 | real | – | REAL | c:o.16 | | | +| | 4.1.7.3.2.2 | low | – | CHOICE | c:m | | | +| | 4.1.7.3.2.2.1 | integer | – | INTEGER | c:o.17 | | | +| | 4.1.7.3.2.2.2 | real | – | REAL | c:o.17 | | | +| | 4.1.7.4 | armTime | – | GeneralizedTime | c:o | | | +| | 4.1.8 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 4.1.9 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c: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.18 | | | +| | 4.1.9.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.9.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.9.2.2 | nonSpecificForm | – | OCTET STRING | c:o.18 | | | + +**Table 37.7/Q.823.1 – trafficControlCurrentData Notification support (continued)** + +| 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.9.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.18 | | | +| | 4.1.9.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.9.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 4.1.10 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | c:o | | | +| | 4.1.10.1 | attributeID | – | CHOICE | c:m | | | +| | 4.1.10.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.19 | | | +| | 4.1.10.1.2 | localForm | – | INTEGER | c:o.19 | | | +| | 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 | c:o | | | +| | 4.1.11.1 | attributeId | – | CHOICE | c:m | | | +| | 4.1.11.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.20 | | | +| | 4.1.11.1.2 | localForm | – | INTEGER | c:o.20 | | | +| | 4.1.11.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 4.1.12 | proposedRepairActions | {2 9 3 2 7 19} | SET OF CHOICE | c:o | | | +| | 4.1.12.1 | OBJECT IDENTIFIER | – | OBJECT IDENTIFIER | c:o.21 | | | +| | 4.1.12.2 | INTEGER | – | INTEGER | c:o.21 | | | +| | 4.1.13 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 4.1.14 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c: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 | ScanReportInformation | | Information Syntax
SEQUENCE | c14 | | | +| | 5.1.1 | scanInitiationTime | {2 9 2 13 7 22} | GeneralizedTime | c:o | | | +| | 5.1.2 | onceReportAttributeList | {2 9 2 13 7 17} | SET OF SEQUENCE | c:o | | | +| | 5.1.2.1 | attributeId | – | CHOICE | c:m | | | +| | 5.1.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.22 | | | + +**Table 37.7/Q.823.1 – trafficControlCurrentData Notification support (continued)** + +| 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.2.1.2 | localForm | – | INTEGER | c:o.22 | | | +| | 5.1.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 5.1.3 | observationScanList | {2 9 2 13 7 15} | SET OF SEQUENCE | c:m | | | +| | 5.1.3.1 | observedObjectInstance | – | CHOICE | c:o | | | +| | 5.1.3.1.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.23 | | | +| | 5.1.3.1.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.3.1.1.2 | attributeValue | – | ANY | c:m | | | +| | 5.1.3.1.2 | nonSpecificForm | – | OCTET STRING | c:o.23 | | | +| | 5.1.3.1.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.23 | | | +| | 5.1.3.1.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.3.1.3.2 | attributeValue | – | ANY | c:m | | | +| | 5.1.3.2 | attributeMeasureList | – | SET OF SEQUENCE | c:o | | | +| | 5.1.3.2.1 | attributeId | – | CHOICE | c:m | | | +| | 5.1.3.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.24 | | | +| | 5.1.3.2.1.2 | localForm | – | INTEGER | c:o.24 | | | +| | 5.1.3.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:o | | | +| | 5.1.3.2.3 | timeStamp | – | CHOICE | c:o | | | +| | 5.1.3.2.3.1 | days | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.2 | hours | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.3 | minutes | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.4 | seconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.5 | milliSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.6 | microSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.7 | nanoSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.3.8 | picoSeconds | – | INTEGER | c:o.25 | | | +| | 5.1.3.2.4 | suspectFlag | – | BOOLEAN | c:o | | | +| | 5.1.3.3 | numericValueArray | – | SEQUENCE OF CHOICE | c:o | | | +| | 5.1.3.3.1 | missingData | – | NULL | c:o.26 | | | +| | 5.1.3.3.2 | valueOnly | – | CHOICE | c:o.26 | | | +| | 5.1.3.3.2.1 | integer | – | INTEGER | c:o.27 | | | +| | 5.1.3.3.2.2 | real | – | REAL | c:o.27 | | | + +**Table 37.7/Q.823.1 – trafficControlCurrentData Notification support (continued)** + +| 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.3.3.3 | qualifiedValue | – | SEQUENCE | c:o:26 | | | +| | 5.1.3.3.3.1 | value | – | CHOICE | c:m | | | +| | 5.1.3.3.3.1.1 | integer | – | INTEGER | c:o:28 | | | +| | 5.1.3.3.3.1.2 | real | – | REAL | c:o:28 | | | +| | 5.1.3.3.3.2 | timeStamp | – | CHOICE | c:o | | | +| | 5.1.3.3.3.2.1 | days | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.2 | hours | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.3 | minutes | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.4 | seconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.5 | milliSeconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.6 | microSeconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.7 | nanoSeconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.2.8 | picoSeconds | – | INTEGER | c:o:29 | | | +| | 5.1.3.3.3.3 | suspectFlag | – | BOOLEAN | c:o | | | +| | 5.1.4 | incompleteScan | {2 9 2 13 7 30} | INTEGER | c:o | | | +| | 5.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 5.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 5.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 5.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | +| 6 | 6.1 | StateChangeInfo | | Information Syntax
SEQUENCE | c15 | | | +| | 6.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 6.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | c:o | | | +| | 6.1.2.1 | globalForm | – | OBJECT IDENTIFIER | c:o:30 | | | +| | 6.1.2.2 | localForm | – | INTEGER | c:o:30 | | | +| | 6.1.3 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | c:m | | | +| | 6.1.3.1 | attributeID | – | CHOICE | c:m | | | +| | 6.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o:31 | | | +| | 6.1.3.1.2 | localForm | – | INTEGER | c:o:31 | | | +| | 6.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | c:o | | | +| | 6.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | c:m | | | +| | 6.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | + +**Table 37.7/Q.823.1 – trafficControlCurrentData 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 | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|-----------------------------|--------|---------|------------------------| +| | 6.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c:o | | | +| | 6.1.5.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 6.1.5.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 6.1.5.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o:32 | | | +| | 6.1.5.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.5.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 6.1.5.2.2 | nonSpecificForm | – | OCTET STRING | c:o:32 | | | +| | 6.1.5.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o:32 | | | +| | 6.1.5.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.5.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 6.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 6.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 6.1.7.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 6.1.7.2 | significance | – | BOOLEAN | c:o | | | +| | 6.1.7.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 37.8/Q.823.1 – trafficControlCurrentData Parameter support** + +| Index | Parameter template label | Value of object identifier for parameter | Constraints and values | Status | Support | Additional information | +|-------|--------------------------------------------------|------------------------------------------|----------------------------------|--------|---------|------------------------| +| 1 | "Rec. Q.821:1992": correlatedRecordNameParameter | {0 0 17 821 0 5 2} | EVENT-INFO qualityofServiceAlarm | c16 | | | +| 2 | "Rec. Q.821:1992": logRecordIdParameter | {0 0 17 821 0 5 1} | EVENT-INFO qualityofServiceAlarm | c16 | | | +| 3 | "Rec. Q.821:1992": suspectObjectListParameter | {0 0 17 821 0 5 3} | EVENT-INFO qualityofServiceAlarm | c16 | | | + +**Table 37.9/Q.823.1 – trafficControlCurrentData Conditions** + +| Condition number | Condition | Reference | +|------------------|--------------------------|---------------------------------------------------------------------------------------------------------| +| c1 | IF 10.3/2 THEN m ELSE – | "notification of attribute value change events is required" | +| c2 | IF 10.3/3 THEN m ELSE – | "the managed object can be scheduled" | +| c3 | IF 10.3/5 THEN m ELSE – | "notification of object creation and object deletion events is required" | +| c4 | IF 10.3/7 THEN m ELSE – | "daily scheduling is required and the weekly or external scheduling package is not present" | +| c5 | IF 10.3/8 THEN m ELSE – | "the scanning function is to be enabled between specified start and stop times" | +| c6 | IF 10.3/9 THEN m ELSE – | "reference to external scheduler is required and the daily or weekly scheduling package is not present" | +| c7 | IF 10.3/10 THEN m ELSE – | "an instance supports it and the zeroSuppressionPkg is not present" | +| c8 | IF 10.3/11 THEN m ELSE – | "historyData objects are to be created at the end of an interval." | +| c9 | IF 10.3/12 THEN m ELSE – | "an instance supports it and at least one of zeroSuppressionPkg or filterSuppressionPkg is present." | +| c10 | IF 10.3/13 THEN m ELSE – | "an instance supports it or the object class is currentData" | +| c11 | IF 10.3/14 THEN m ELSE – | "suppression counts are required and the filterSuppressionPkg or the zeroSuppressionPkg is present." | +| c12 | IF 10.3/16 THEN m ELSE – | "any registered package, other than this package has been instantiated" | +| c13 | IF 10.3/17 THEN m ELSE – | "configurable agent internal synchronization of repeating time periods is required" | +| c14 | IF 10.3/19 THEN m ELSE – | "scheduled notifications are to be emitted." | +| c15 | IF 10.3/20 THEN m ELSE – | "notification of state change event is required" | +| c16 | IF 10.3/21 THEN m ELSE – | "a Quality of Service Alarm Notification is to be emitted for threshold crossing." | +| c17 | IF 10.3/24 THEN m ELSE – | "weekly scheduling is required and the daily or external scheduling package is not present" | +| c18 | IF 10.3/25 THEN m ELSE – | "an instance supports it and the filterSuppressionPkg is not present." | + +**Table 37.10/Q.823.1 – trafficControlCurrentData Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|----------------------------------------------------------|---------------------------------------------|---------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "ITU-T Rec. X.738":
conflictingPackagesScanner-system | {2 9 2 13 6 9} | Superior class:
"Rec. X.721 ISO/IEC 10165-2 : 1992":
system
AND SUBCLASSES | o | | | + +**Table 37.10/Q.823.1 – trafficControlCurrentData 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:m | | | +| | 1.6 | Delete contained objects | | c:x | | | + +### 38 trafficControlHistoryData ["Q.823"] + +**Table 38.1/Q.823.1 – trafficControlHistoryData 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 | trafficControlHistoryData | {0 0 17 823 0 3 33} | | | + +**Table 38.2/Q.823.1 – trafficControlHistoryData 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 38.3/Q.823.1 – trafficControlHistoryData Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|-----------------------------------------------------------------|----------------------------------------|-----------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | callsOfferedHistoryPackage | {0 0 17 823 0 4 12} | "this package is present if it is present in the corresponding instance of currentData" | c1 | | | +| 3 | "ITU-T Rec. Q.822 : 1994":
historyDataMeasurementListPkg | {0 0 17 822 0 4 4} | "the measurementListPkg is present in the corresponding currentData instance" | c2 | | | +| 4 | "ITU-T Rec. Q.822 : 1994":
historyDataPkg | | Mandatory | m | | | +| 5 | "ITU-T Rec. Q.822 : 1994":
historyDataSuspectIntervalFlagPkg | {0 0 17 822 0 4 5} | "an instance supports it." | o | | | + +**Table 38.3/Q.823.1 – trafficControlHistoryData Package support (concluded)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------|--------|---------|------------------------| +| 6 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervals Pkg | {0 0 17 822 0 4 9} | "this package is present in the corresponding currentData instance." | c3 | | | +| 7 | "ITU-T Rec. Q.822 : 1994":
objectDeleteNotification Pkg | {0 0 17 822 0 4 10} | "an instance supports it." | o | | | +| 8 | "ITU-T Rec. Q.822 : 1994":
observedManagedObject Pkg | {0 0 17 822 0 4 11} | "this package is present in the corresponding currentData instance." | c3 | | | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c4 | | | +| 10 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
topPackage | | Mandatory | m | | | +| 11 | trafficControlHistoryData Package | | Mandatory | m | | | + +**Table 38.4/Q.823.1 – trafficControlHistoryData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 2 | callsAffectedByTrafficControl | {0 0 17 823 0 6 16} | INTEGER | m? | | m | | – | | +| 3 | callsOfferedToTrafficControl | {0 0 17 823 0 6 18} | INTEGER | c1? | | c1 | | – | | +| 4 | "ITU-T Rec. X.739":
granularityPeriod | {2 9 2 11 7 23} | CHOICE | m? | | m | | – | | +| 5 | "ITU-T Rec. Q.822 : 1994":
historyDataId | {0 0 17 822 0 7 4} | CHOICE | m? | | m | | – | | +| 6 | "ITU-T Rec. Q.822 : 1994":
measurementList | {0 0 17 822 0 7 7} | SET OF SEQUENCE | c2? | | c2 | | – | | +| 7 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 8 | "ITU-T Rec. Q.822 : 1994":
numSuppressedIntervals | {0 0 17 822 0 7 9} | INTEGER | c3? | | c3 | | – | | + +**Table 38.4/Q.823.1 – trafficControlHistoryData 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 | +| 9 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 10 | "ITU-T Rec. Q.822 : 1994":
observedObjectClass | {0 0 17 822 0 7 10} | CHOICE | c3? | | c3 | | – | | +| 11 | "ITU-T Rec. X.739":
observedObjectInstance | {2 9 2 11 7 16} | CHOICE | c3? | | c3 | | – | | +| 12 | "Rec. X.721 ISO/IEC 10165-2 : 1992":
packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c4 | | – | | +| 13 | "ITU-T Rec. Q.822 : 1994":
periodEndTime | {0 0 17 822 0 7 12} | GeneralizedTime | m? | | m | | – | | +| 14 | "ITU-T Rec. Q.822 : 1994":
suspectIntervalFlag | {0 0 17 822 0 7 14} | BOOLEAN | o? | | o | | – | | + +**Table 38.4/Q.823.1 – trafficControlHistoryData 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 | – | | – | | – | | | + +**Table 38.5/Q.823.1 – trafficControlHistoryData Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table 38.6/Q.823.1 – trafficControlHistoryData Action support** + +There are no actions specified for this managed object class. + +**Table 38.7/Q.823.1 – trafficControlHistoryData 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 | "Rec. X.721 ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | o | | | | + +**Table 38.7/Q.823.1 – trafficControlHistoryData Notification support (continued)** + +| 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 | ObjectInfo | | Information Syntax SEQUENCE | o | | | +| | 1.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | c:o | | | +| | 1.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | c:o | | | +| | 1.1.2.1 | attributeId | – | CHOICE | c:m | | | +| | 1.1.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.1 | | | +| | 1.1.2.1.2 | localForm | – | INTEGER | c:o.1 | | | +| | 1.1.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 1.1.3 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | c:o | | | +| | 1.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | c:o | | | +| | 1.1.4.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 1.1.4.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 1.1.4.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.2 | | | +| | 1.1.4.2.1.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.4.2.1.2 | attributeValue | – | ANY | c:m | | | +| | 1.1.4.2.2 | nonSpecificForm | – | OCTET STRING | c:o.2 | | | +| | 1.1.4.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.2 | | | +| | 1.1.4.2.3.1 | attributeType | – | OBJECT IDENTIFIER | c:m | | | + +**Table 38.7/Q.823.1 – trafficControlHistoryData 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.4.2.3.2 | attributeValue | – | ANY | c:m | | | +| | 1.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | c:o | | | +| | 1.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | c:o | | | +| | 1.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 1.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table 38.8/Q.823.1 – trafficControlHistoryData Parameter support** + +There are no parameters specified for this managed object class. + +**Table 38.9/Q.823.1 – trafficControlHistoryData Conditions** + +| Condition number | Condition | Reference | +|------------------|-------------------------|-----------------------------------------------------------------------------------------| +| c1 | IF 11.3/2 THEN m ELSE – | "this package is present if it is present in the corresponding instance of currentData" | +| c2 | IF 11.3/3 THEN m ELSE – | "the measurementListPkg is present in the corresponding currentData instance" | +| c3 | IF 11.3/6 THEN m ELSE – | "this package is present in the corresponding currentData instance." | +| c4 | IF 11.3/9 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table 38.10/Q.823.1 – trafficControlHistoryData Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------------------------------|---------------------------------------------|-----------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | trafficControlHistoryData-trafficControl | {0 0 17 823 0 5 21} | Superior class:
trafficControl
AND SUBCLASSES | o | | | +| 2 | "ITU-T Rec. Q.822 : 1994":
historyData-currentData | {0 0 17 822 0 6 1} | Superior class:
"ITU-T Rec. Q.822 :
1994":
currentData
AND SUBCLASSES | o | | | + +**Table 38.10/Q.823.1 – trafficControlHistoryData 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:x | | | +| | 1.6 | Delete contained objects | | c:m | | | +| 2 | 2.1 | Create support | | – | | | +| | 2.2 | Create with reference object | | – | | | +| | 2.3 | Create with automatic instance naming | | – | | | +| | 2.4 | Delete support | | c:m | | | +| | 2.5 | Delete only if no contained objects | | c:x | | | +| | 2.6 | Delete contained objects | | c:m | | | + +## 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/Q/T-REC-Q.824.4-199510-I_PDF-E/raw.md b/marked/Q/T-REC-Q.824.4-199510-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..cddf28171999e26e32d3882aadda33591fa779f7 --- /dev/null +++ b/marked/Q/T-REC-Q.824.4-199510-I_PDF-E/raw.md @@ -0,0 +1,399 @@ + + +![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** + +**Q.824.4** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(10/95) + +# **SPECIFICATIONS OF SIGNALLING SYSTEM No. 7** --- + +**STAGES 2 AND 3 DESCRIPTION FOR +THE Q3 INTERFACE – CUSTOMER +ADMINISTRATION – INTEGRATED SERVICES +DIGITAL NETWORK (ISDN) – TELESERVICES** + +**ITU-T Recommendation Q.824.4** + +(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 Q.824.4 was prepared by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 17th of October 1995. + +--- + +## 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 | +| 1.1 Purpose and scope ..... | 1 | +| 1.2 Cross-reference ..... | 1 | +| 1.3 Application ..... | 1 | +| 1.4 General Overview ..... | 1 | +| 2 References ..... | 3 | +| 3 Teleservices..... | 4 | +| 3.1 Telefax 4 ..... | 4 | +| 3.2 Telephony ..... | 4 | +| 3.3 Teletex ..... | 5 | +| 4 Attribute templates ..... | 5 | +| 4.1 Max Number Of Info Channels ..... | 5 | +| 4.2 Max Number Of Total Calls ..... | 5 | +| 4.3 Telefax Class ..... | 6 | +| 4.4 Teletex Mode ..... | 6 | +| 5 Name bindings ..... | 6 | +| 6 Type definitions ..... | 6 | + +## Summary + +The purpose of this Recommendation is to provide the Stages 2 and 3 description 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 of ISDN Teleservices. 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. This Recommendation supports the administration of the customer configuration in the local exchange by the TMN. This Recommendation is part of a series of Recommendations. In this Recommendation the ISDN Teleservices specific managed objects are defined. + +## **STAGES 2 AND 3 DESCRIPTION FOR THE Q3 INTERFACE – CUSTOMER ADMINISTRATION – INTEGRATED SERVICES DIGITAL NETWORK (ISDN) – TELESERVICES** + +*(Geneva, 1995)* + +# **1 Introduction** + +## **1.1 Purpose and scope** + +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. + +The purpose of this Recommendation is to provide the common Stage 2 and 3 description of the Q3 interface between a local exchange and the Telecommunications Management Network (TMN) for the support of configuration management functions. + +The Q3 interface is the TMN interface between network elements or Q-adapters which interface to Operations Systems (OSs) without mediation and between OSs and mediation devices as described in Recommendation M.3100. + +## **1.2 Cross-reference** + +This Recommendation is based on the Stage 1 management service description given in the M.3000-Series Recommendations including Recommendation M.3400. This Recommendation provides the Stage 2 and 3 descriptions for handling customer administration services based on the service description provided in the I.240-Series Recommendations, and based on the common Stage 2 and 3 descriptions given in Recommendation Q.824.0. The information model provided by this Recommendation may be used for the customer administration purposes either over a Q3 interface or over the ISDN UNI as described in Recommendation Q.942. + +## **1.3 Application** + +The management information included in this Recommendation may be exchanged by implementations of the Common Management Information Service Element (CMISE). The Transaction-Oriented class of OAM&P applications is supported in this Recommendation by defining object classes, their attributes, and their relationships. The protocol suites are given in Recommendations Q.811 and Q.812. No special requirements are identified. + +## **1.4 General Overview** + +### **1.4.1 Information model diagrams** + +The following information model diagrams have been drawn for the purpose of clarifying the relations between the different object classes of customer administration. There are three different types of diagrams: + +- 1) Entity-Relationship Model showing the relations of the different managed objects. +- 2) Inheritance Hierarchy showing how managed objects are derived from each other (i.e. the different paths of inherited characteristics of the different managed objects). +- 3) Naming Hierarchy showing the derivation of names for managed objects (i.e. the different naming paths for instances of managed objects). + +These three different diagrams are only for clarification. The formal specification in terms of GDMO templates and ASN.1 type definitions are the relevant information for the implementation of this Recommendation. See Figures 1 to 3. + +![Entity-Relationship diagram showing Managed Element, Customer Profile, Teleservice, Telefax 4, Telephony, and Teletex with relationships C and Is a.](547f726730e589392f239257a833ede3_img.jpg) + +This Entity-Relationship diagram illustrates the relationships between several entities. At the top is a rectangular box labeled "Managed Element". To its right is an empty rectangular box with the text "Defined in other Recommendations". Below "Managed Element" is a diamond-shaped relationship box containing the letter "C", with a downward-pointing arrow leading to a rectangular box labeled "Customer Profile". Below "Customer Profile" is another diamond-shaped relationship box containing the letter "C", with a downward-pointing arrow leading to a rectangular box labeled "Teleservice". Below "Teleservice" is a diamond-shaped relationship box containing the text "Is a", with an upward-pointing arrow. A horizontal line extends from the bottom of the "Is a" diamond, connecting to three separate rectangular boxes labeled "Telefax 4", "Telephony", and "Teletex". The reference code "T1173970-95/d01" is located at the bottom right of the diagram. + +Entity-Relationship diagram showing Managed Element, Customer Profile, Teleservice, Telefax 4, Telephony, and Teletex with relationships C and Is a. + +FIGURE 1/Q.824.4 +Entity-Relationship diagram + +![Inheritance hierarchy diagram showing X.721: top, ITU-T Rec. 824.0: teleservice, Telefax 4, Telephony, and Teletex.](a7d78d22e465dea388b31d0739f9d0cd_img.jpg) + +This Inheritance hierarchy diagram shows a chain of inheritance. It starts with a rectangular box labeled "X.721": top, which is connected by a horizontal line to another rectangular box labeled "ITU-T Rec. 824.0": teleservice. From the right side of the "ITU-T Rec. 824.0": teleservice box, a vertical line descends, with three horizontal branches extending to three separate rectangular boxes labeled "Telefax 4", "Telephony", and "Teletex". The reference code "T1173980-95/d02" is located at the bottom right of the diagram. + +Inheritance hierarchy diagram showing X.721: top, ITU-T Rec. 824.0: teleservice, Telefax 4, Telephony, and Teletex. + +FIGURE 2/Q.824.4 +Inheritance hierarchy + +![Diagram showing the naming hierarchy for ITU-T Rec. Q.824.0: customerProfile. The hierarchy starts with 'M.3100: managedElement' connected to 'ITU-T Rec. Q.824.0: customerProfile', which then branches into three sub-elements: 'Telefax 4', 'Telephony', and 'Teletex'. Below the diagram is the code T1173990-95/d03.](fc46871d72c65d3381d9201646d23439_img.jpg) + +``` + +graph LR + A["\"M.3100\": +managedElement"] --- B["\"ITU-T +Rec. Q.824.0\": +customerProfile"] + B --- C["Telefax 4"] + B --- D["Telephony"] + B --- E["Teletex"] + +``` + +T1173990-95/d03 + +Diagram showing the naming hierarchy for ITU-T Rec. Q.824.0: customerProfile. The hierarchy starts with 'M.3100: managedElement' connected to 'ITU-T Rec. Q.824.0: customerProfile', which then branches into three sub-elements: 'Telefax 4', 'Telephony', and 'Teletex'. Below the diagram is the code T1173990-95/d03. + +NOTE – The indicated naming hierarchy includes reusable name bindings defined in other Recommendations. + +FIGURE 3/Q.824.4 +**Naming hierarchy** + +## 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. + +- ITU-T Recommendation F.184 (1993), *Operational provisions for the international public facsimile service between subscriber stations with group 4 facsimile machines (telefax 4)*. +- CCITT Recommendation F.200 (1992), *Teletex service*. +- CCITT Recommendation I.240 (1988), *Definition of teleservices*. +- CCITT Recommendation I.241.1 (1988), *Telephony*. +- CCITT Recommendation I.241.2 (1988), *Teletex*. +- CCITT Recommendation I.241.3 (1988), *Telefax 4*. +- CCITT Recommendation M.3010 (1992), *Principles for a telecommunications management network*. +- CCITT Recommendation M.3020 (1992), *TMN interface specification methodology*. +- ITU-T Recommendation M.3100 (1995), *Generic network information model*. +- CCITT Recommendation M.3400 (1992), *TMN management functions*. +- ITU-T Recommendation Q.811 (1993), *Lower layer protocol profiles for the Q3 interface*. +- ITU-T Recommendation Q.812 (1993), *Upper layer protocol profiles for the Q3 interface*. +- ITU-T Recommendation Q.824.0 (1995), *Stages 2 and 3 description for the Q3 interface – Customer administration – Common information*. + +- CCITT Recommendation X.700 (1992), *Management framework for Open Systems Interconnection (OSI) for CCITT applications.* +- CCITT Recommendation X.701 (1992), *Information technology – Open Systems Interconnection – System management overview.* +- CCITT Recommendation X.710 (1991), *Common management information service definition for CCITT applications.* +- CCITT Recommendation X.711 (1991), *Common management information protocol specification for CCITT applications.* +- CCITT Recommendation X.720 (1992), *Information technology – Open Systems Interconnection – Structure of management information: Management information model.* +- CCITT Recommendation X.721 (1992), *Information technology – Open Systems Interconnection – Structure of management information: Definition of management information.* +- CCITT Recommendation X.722 (1992), *Information technology – Open Systems Interconnection – Structure of management information: Guidelines for the definition of managed objects.* +- ITU-T Recommendation X.723 (1993), *Information technology – Open Systems Interconnection – Structure of management information: Generic management information.* + +# 3 Teleservices + +## 3.1 Telefax 4 + +telefax4 **MANAGED OBJECT CLASS** + +**DERIVED FROM** "ITU-T Rec. Q.824.0":teleservice; + +**CHARACTERIZED BY** + +telefax4Pkg **PACKAGE** + +**BEHAVIOUR** + +telefax4Bhv **BEHAVIOUR** + +**DEFINED AS** "Telefax 4, as defined in F.184 and I.241.3, is an international service enabling subscribers to exchange office correspondence in the form of documents containing facsimile coded information automatically via the ISDN. The Telefax 4 service provides a basic level of compatibility between all terminals participating in the service. It offers bidirectional communication between two users via the ISDN using 64 kbit/s digital signals over the B-channel. The basic element of the correspondence between users is the page which is the smallest unit of text treated as an entity. No restrictions shall exist concerning the operator procedures for generation of the text or the position of the text within the reproducible area.";; + +**ATTRIBUTES** + +telefaxClass + +**GET-REPLACE**;; + +**REGISTERED AS** {cAISDNTSOObjectClass 1}; + +## 3.2 Telephony + +telephony **MANAGED OBJECT CLASS** + +**DERIVED FROM** "ITU-T Rec. Q.824.0":teleservice; + +**CHARACTERIZED BY** + +telephonyPkg **PACKAGE** + +**BEHAVIOUR** + +telephonyBhv **BEHAVIOUR** + +**DEFINED AS** "The telephony service provides speech transmission at an audio bandwidth of 3.1 kHz as defined in I.241.1. The communication is bidirectional, with both directions continuously and simultaneously active during the speech phase. The network may use processing techniques appropriate for speech such as analogue transmission, echo cancellation and low bit rate encoding.";; + +### ATTRIBUTES + +maxNumOfInfoChannels +maxNumOfTotalCalls + +GET SET-BY-CREATE, +GET;;; + +REGISTERED AS {cAISDNTSObjectClass 2}; + +## 3.3 Teletex + +teletex MANAGED OBJECT CLASS + +DERIVED FROM "ITU-T Rec. Q.824.0":teleservice; + +### CHARACTERIZED BY + +teletexPkg PACKAGE + +### BEHAVIOUR + +teletexBhv BEHAVIOUR + +DEFINED AS "The basic Teletex service, as defined in F.200 and I.241.2, provides communication between equipment, which is used for the preparation, editing and printing of correspondence. A basic level of compatibility is provided between any two Teletex terminal equipments both nationally and internationally so that they may communicate formatted documents composed of character-coded information to each other.";; + +### ATTRIBUTES + +teletexMode + +GET SET-BY-CREATE;;; + +REGISTERED AS {cAISDNTSObjectClass 3}; + +## 4 Attribute templates + +This clause contains the ASN.1 definitions for all attributes in the described object classes. These definitions identify the function of the attributes and their valid characteristics, such as their valid values, interdependencies, read/write constraints, etc. The attributes are identified by their ASN.1 descriptors. + +## 4.1 Max Number Of Info Channels + +maxNumOfInfoChannels ATTRIBUTE + +#### WITH ATTRIBUTE SYNTAX + +CATeleserviceAttributeModule.MaxNumber; +MATCHES FOR EQUALITY; + +### BEHAVIOUR + +maxNumOfInfoChannelsBhv BEHAVIOUR + +DEFINED AS "This attribute determines the maximum number of Information channels to be used by the Telephone teleservice as defined in I.241.1.";; + +REGISTERED AS {cAISDNTSAttribute 1}; + +### 4.2 Max Number Of Total Calls + +maxNumOfTotalCalls ATTRIBUTE + +#### WITH ATTRIBUTE SYNTAX + +CATeleserviceAttributeModule.MaxNumber; +MATCHES FOR EQUALITY; + +#### BEHAVIOUR + +maxNumOfTotalCallsBhv BEHAVIOUR + +DEFINED AS "This attribute determines the maximum number of simultaneous calls to be used by the Telephone teleservice as defined in I.241.1.";; + +REGISTERED AS {cAISDNTSAttribute 2}; + +### 4.3 Telefax Class + +telefaxClass ATTRIBUTE + +#### WITH ATTRIBUTE SYNTAX + +CATeleserviceAttributeModule.TelefaxClass; +MATCHES FOR EQUALITY; +BEHAVIOUR +telefaxClassBhv BEHAVIOUR +DEFINED AS "The Telefax Class attribute defines the class of telefax teleservice as described in F.184 +and I.241.3.";; +REGISTERED AS {cAISDNTSAttribute 3}; + +## 4.4 Teletex Mode + +teletexMode ATTRIBUTE + +#### WITH ATTRIBUTE SYNTAX + +CATeleserviceAttributeModule.TeletexMode; +MATCHES FOR EQUALITY; +BEHAVIOUR +teletexModeBhv BEHAVIOUR +DEFINED AS "The teletex mode attribute defines the mode of teletex teleservice as described in F.200 +and I.241.2.";; +REGISTERED AS {cAISDNTSAttribute 4}; + +## 5 Name bindings + +No new name bindings are defined in this Recommendation. All teleservices currently defined use the name binding defined in Recommendation Q.824.0 for the teleservice super-class. The teleservice class is named in terms of Customer Profile. This name binding is defined for teleservices and its subclasses. + +# 6 Type definitions + +CAISDNTSModule {itu-t(0) recommendation(0) q(17) ca(824) dot(127) isdnts(4) informationModel(0) ans1Modules(2) +cAISDNTSModule(0)} + +DEFINITIONS IMPLICIT TAGS ::= BEGIN + +-- EXPORTS Everything; + +### IMPORTS + +ObjectInstance, ObjectClass + +FROM CMIP-1 {joint-iso-ccitt ms(9) cmip(1) modules(0) protocol(3)} + +AlarmStatus, Boolean, NameType, ObjectList, Pointer, PointerOrNull + +FROM ASN1DefinedTypesModule {ccitt recommendation m(13) gnm(3100) +informationModel(0) ans1Modules(2) asn1DefinedTypesModule(0)} + +q824-4InformationModel OBJECT IDENTIFIER ::= {itu-t(0) recommendation(0) q(17) ca(824) +dot(127) isdnts(4) informationModel(0)} + +cAISDNTSObjectClass OBJECT IDENTIFIER ::= {q824-4InformationModel +managedObjectClass(3)} + +cAISDNTPackage OBJECT IDENTIFIER ::= {q824-4InformationModel package(4)} + +cAISDNSTAttribute OBJECT IDENTIFIER ::= {q824-4InformationModel attribute(7)} + +cAISDNTSNameBinding OBJECT IDENTIFIER ::= {q824-4InformationModel nameBinding(6)} + +cAISDNSTAction OBJECT IDENTIFIER ::= {q824-4InformationModel action(9)} + +-- default value definitions -- + +false Boolean ::= FALSE + +true Boolean ::= TRUE + +null NULL ::= NULL + +one INTEGER ::= 1 + +zero INTEGER ::= 0 + +minusOne INTEGER ::= -1 + +emptySet NULL ::= NULL + +-- supporting productions -- + +DetailedNumber ::= SEQUENCE { + +    incoming INTEGER, +    outgoing INTEGER, +    bothWay INTEGER } + +MaxNumber ::= CHOICE { + +    detailed [1] DetailedNumber, +    total [2] INTEGER } + +TelefaxClass ::= + +    ENUMERATED { +        telefaxClassI (1), +        telefaxClassII (2), +        telefaxClassIII (3) } + +TeletexMode ::= + +    BIT STRING {virtualDialogueMode (1), +        processableMode (2), +        mixedMode (3) } + +END -- Type definitions -- \ No newline at end of file diff --git a/marked/Q/T-REC-Q.836.1-200002-I_PDF-E/raw.md b/marked/Q/T-REC-Q.836.1-200002-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..80af32b98bcf5b1cc8286190d90f0f791bc5091a --- /dev/null +++ b/marked/Q/T-REC-Q.836.1-200002-I_PDF-E/raw.md @@ -0,0 +1,3585 @@ + + +![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 + +# Q.836.1 + +(02/2000) + +SERIES Q: SWITCHING AND SIGNALLING + +Specifications of Signalling System No. 7 – Q3 interface + +# --- **SSF management information model** + +ITU-T Recommendation Q.836.1 + +(Previously CCITT Recommendation) + +--- + +## ITU-T Q-SERIES RECOMMENDATIONS + +# **SWITCHING AND SIGNALLING** + +| | | +|------------------------------------------------------------|--------------------| +| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 | +| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 | +| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 | +| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 | +| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 | +| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 | +| DIGITAL EXCHANGES | Q.500–Q.599 | +| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 | +| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 | +| General | Q.700 | +| Message transfer part (MTP) | Q.701–Q.709 | +| Signalling connection control part (SCCP) | Q.711–Q.719 | +| Telephone user part (TUP) | Q.720–Q.729 | +| ISDN supplementary services | Q.730–Q.739 | +| Data user part | Q.740–Q.749 | +| Signalling System No. 7 management | Q.750–Q.759 | +| ISDN user part | Q.760–Q.769 | +| Transaction capabilities application part | Q.770–Q.779 | +| Test specification | Q.780–Q.799 | +| Q3 interface | Q.800–Q.849 | +| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 | +| General | Q.850–Q.919 | +| Data link layer | Q.920–Q.929 | +| Network layer | Q.930–Q.939 | +| User-network management | Q.940–Q.949 | +| Stage 3 description for supplementary services using DSS 1 | Q.950–Q.999 | +| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 | +| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 | +| INTELLIGENT NETWORK | Q.1200–Q.1699 | +| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 | +| BROADBAND ISDN | Q.2000–Q.2999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +# **SSF MANAGEMENT INFORMATION MODEL** + +## **Summary** + +This Recommendation is one in a series of Recommendations that deals with the management of IN functional entities. There will be one Recommendation for each functional entity. This Recommendation specifies the Management Information Model for the Service Switching Function (SSF). + +## **Source** + +ITU-T Recommendation Q.836.1 was prepared by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution 1 procedure on 4 February 2000. + +## 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 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 | Normative references ..... | 1 | +| 2.1 | Informative reference ..... | 1 | +| 3 | Definitions ..... | 1 | +| 4 | Abbreviations..... | 2 | +| 5 | Requirements met ..... | 3 | +| 5.1 | Management functional areas ..... | 3 | +| 5.1.1 | Fault management..... | 3 | +| 5.1.2 | Configuration Management..... | 3 | +| 5.1.3 | Accounting management ..... | 3 | +| 5.1.4 | Performance management ..... | 3 | +| 5.1.5 | Security management..... | 3 | +| 5.2 | Operational requirements..... | 4 | +| 5.2.1 | Introduction..... | 4 | +| 6 | Information Model – Overview ..... | 4 | +| 6.1 | Managed Object Class Relationship Model..... | 4 | +| 6.1.1 | "Configure SRF/SCF relaying capabilities" and "Configure SRF assisting" Relationships ..... | 4 | +| 6.1.2 | Managed Object descriptions ..... | 5 | +| 6.2 | Inheritance Hierarchy..... | 6 | +| 6.3 | Naming Hierarchy..... | 7 | +| 7 | Managed Object Class Definitions ..... | 8 | +| 7.1 | IN Authorization ..... | 8 | +| 7.2 | Basic Call State Model (BCSM)..... | 9 | +| 7.3 | Trigger Detection Point (TDP) ..... | 9 | +| 7.4 | Originating Attempt Authorized Trigger ..... | 10 | +| 7.5 | Collected Information Trigger ..... | 10 | +| 7.6 | Analysed Information Trigger..... | 11 | +| 7.7 | Route Select Failure Trigger ..... | 11 | +| 7.8 | Originating Called Party Busy Trigger ..... | 12 | +| 7.9 | Originating No Answer Trigger ..... | 12 | +| 7.10 | Originating Answer Trigger..... | 12 | +| 7.11 | Originating Mid Call Trigger ..... | 13 | +| 7.12 | Originating Disconnect Trigger ..... | 13 | +| 7.13 | Originating Abandon Trigger..... | 14 | + +| | Page | +|---------------------------------------------------|-------------| +| 7.14 Terminating Attempt Authorized Trigger ..... | 14 | +| 7.15 Terminating Called Party Busy Trigger ..... | 14 | +| 7.16 Terminating No Answer Trigger ..... | 15 | +| 7.17 Terminating Answer Trigger ..... | 15 | +| 7.18 Terminating Mid Call Trigger ..... | 16 | +| 7.19 Terminating Disconnect Trigger ..... | 16 | +| 7.20 Terminating Abandon Trigger ..... | 17 | +| 7.21 Trigger Base ..... | 17 | +| 7.22 Originating Line Trigger Base ..... | 18 | +| 7.23 Originating Trunk Trigger Base ..... | 18 | +| 7.24 Terminating Line Trigger Base ..... | 18 | +| 7.25 Terminating Trunk Trigger Base ..... | 18 | +| 7.26 Private Facility Trigger Base ..... | 19 | +| 7.27 Office Trigger Base ..... | 19 | +| 7.28 IN Call Gap ..... | 19 | +| 7.29 Service Filtering ..... | 20 | +| 7.30 Service Filtering Counter ..... | 21 | +| 7.31 Service Filtering Duration Default ..... | 22 | +| 7.32 Initiate Call Default Information ..... | 22 | +| 7.33 INAP Counter ..... | 22 | +| 7.34 Service Feature Control ..... | 23 | +| 7.35 SCF Access ..... | 24 | +| 7.36 SCF Access Point Code Based ..... | 24 | +| 7.37 SCF Global Title Based ..... | 25 | +| 7.38 IP Configuration ..... | 25 | +| 7.39 Assist Treatment Configuration ..... | 26 | +| 7.40 Ported Number Trigger ..... | 26 | +| 7.41 Ported Number List ..... | 27 | +| 7.42 INAP Current Data ..... | 27 | +| 7.43 INAP History Data ..... | 27 | +| 7.44 Default Charging ..... | 28 | +| 7.45 Exception Handler ..... | 28 | +| 7.46 SSF Timer ..... | 29 | +| 7.47 SCF Application Entity ..... | 29 | +| 7.48 SSF Application Entity ..... | 29 | +| 8 Package definitions ..... | 29 | + +| | Page | +|---------------------------------------------|-------------| +| 9 Attribute definitions ..... | 30 | +| 9.1 bcsmId Attribute ..... | 30 | +| 9.2 tdpId Attribute ..... | 30 | +| 9.3 tdpMode Attribute ..... | 30 | +| 9.4 tdp1Criteria Attribute ..... | 30 | +| 9.5 tdp2Criteria Attribute ..... | 30 | +| 9.6 tdp3Criteria Attribute ..... | 31 | +| 9.7 tdp4Criteria Attribute ..... | 31 | +| 9.8 tdp5Criteria Attribute ..... | 31 | +| 9.9 tdp6Criteria Attribute ..... | 31 | +| 9.10 tdp7Criteria Attribute ..... | 32 | +| 9.11 tdp8Criteria Attribute ..... | 32 | +| 9.12 tdp9Criteria Attribute ..... | 32 | +| 9.13 tdp10Criteria Attribute ..... | 32 | +| 9.14 tdp12Criteria Attribute ..... | 33 | +| 9.15 tdp13Criteria Attribute ..... | 33 | +| 9.16 tdp14Criteria Attribute ..... | 33 | +| 9.17 tdp15Criteria Attribute ..... | 33 | +| 9.18 tdp16Criteria Attribute ..... | 34 | +| 9.19 tdp17Criteria Attribute ..... | 34 | +| 9.20 tdp18Criteria Attribute ..... | 34 | +| 9.21 triggerAssociation Attribute ..... | 34 | +| 9.22 inEscape Attribute ..... | 34 | +| 9.23 congestionAction Attribute ..... | 35 | +| 9.24 serviceKey Attribute ..... | 35 | +| 9.25 inCallGapId Attribute ..... | 35 | +| 9.26 gapDuration Attribute ..... | 35 | +| 9.27 gapInterval Attribute ..... | 35 | +| 9.28 gapTreatment Attribute ..... | 36 | +| 9.29 digitString Attribute ..... | 36 | +| 9.30 authenticationCode Attribute ..... | 36 | +| 9.31 calledPartyNumberList Attribute ..... | 36 | +| 9.32 callingPartyNumberList Attribute ..... | 36 | +| 9.33 version Attribute ..... | 37 | +| 9.34 observedEventId Attribute ..... | 37 | +| 9.35 observedSCFAccessList Attribute ..... | 37 | + +| | Page | +|-------------------------------------------------------------------------|-------------| +| 9.36 count Attribute ..... | 37 | +| 9.37 defaultCharging Attribute ..... | 37 | +| 9.38 chargingProfile Attribute ..... | 38 | +| 9.39 iNAPASE Attribute ..... | 38 | +| 9.40 iNEscape Attribute..... | 38 | +| 9.41 exceptionHandling Attribute..... | 38 | +| 9.42 sCFAccessPointer Attribute..... | 38 | +| 9.43 triggerList Attribute ..... | 39 | +| 9.44 basePriority Attribute..... | 39 | +| 9.45 gapCriteria Attribute ..... | 39 | +| 9.46 gapDuration Attribute ..... | 39 | +| 9.47 gapInterval Attribute ..... | 39 | +| 9.48 gapTreatment Attribute..... | 40 | +| 9.49 controlType Attribute..... | 40 | +| 9.50 iPCapabilityList Attribute ..... | 40 | +| 9.51 dialledDigitLength ..... | 40 | +| 9.52 terminatingDialDigitsList Attribute..... | 40 | +| 9.53 defaultChargingAction Attribute ..... | 41 | +| 9.54 timerValue Attribute ..... | 41 | +| 9.55 missingCustomerRecordException Attribute ..... | 41 | +| 10 Name Bindings..... | 41 | +| 10.1 TDP to BCSM..... | 41 | +| 10.2 Originating Trunk Trigger Base to Configured End Point Group ..... | 42 | +| 10.3 Terminating Trunk Trigger Base to Configured End Point Group ..... | 42 | +| 10.4 Originating Line Trigger Base to Customer Profile..... | 42 | +| 10.5 Terminating Line Trigger Base to Customer Profile ..... | 42 | +| 10.6 SCF Access to Managed Element..... | 43 | +| 10.7 BCSM to Managed Element ..... | 43 | +| 10.8 IN Call Gap to SSF-SCF Application Entity ..... | 43 | +| 10.9 Service Filtering to Service Feature Control..... | 43 | +| 10.10 IP Configuration to Managed Element ..... | 44 | +| 10.11 Dialled Digit Length to Managed Element ..... | 44 | +| 10.12 Terminating Dialled Digit List to Dialled Digit Length ..... | 44 | +| 10.13 inAuthorization to tdp..... | 45 | +| 10.14 Initiate Call Default Information to Managed Element ..... | 45 | +| 10.15 Assist Treatment Configuration to Managed Element..... | 45 | + +| | Page | +|----------------------------------------------------------------------|-------------| +| 10.16 Ported Number Trigger to Managed Element..... | 45 | +| 10.17 Ported Number List to Managed Element..... | 46 | +| 10.18 Default Charging to Service Feature Control ..... | 46 | +| 10.19 Exception Handler to Service Feature Control ..... | 46 | +| 10.20 SSF Timer to SCF Access ..... | 46 | +| 10.21 INAP Counter to SSF Application Entity..... | 47 | +| 10.22 INAP Current Data to SSF Application Entity ..... | 47 | +| 10.23 INAP History Data to SSF Application Entity ..... | 47 | +| 10.24 Assist Treatment Configuration to SSF Application Entity ..... | 48 | +| 10.25 Service Feature Control to SSF Application Entity..... | 48 | +| 11 ASN.1 Module ..... | 48 | +| Appendix I – Productions Imported From Q.1218 ..... | 53 | + + + +## Recommendation Q.836.1 + +# SSF MANAGEMENT INFORMATION MODEL + +# 1 Scope + +This Recommendation specifies the information model for the management of IN functionality provided in the Service Switching Function (SSF). In the physical functional plane the data structures implied by this model may reside in any physical system (Network Element (NE)), e.g. Service Switching Point (SSP) or Service Switching Control Point (SSCP), that implements the SSF functionality. + +This Recommendation defines: + +- the managed objects and associated attributes, actions, notifications and behaviour; +- the name bindings; +- the GDMO templates and associated ASN.1 syntax used in specifying the information model; and +- the representation of the management information at the Q3 interface between the system supporting the SSF functionality and the management system. + +This Recommendation does not define: + +- the internal implementation of the data structures used to represent the information model in the physical system. + +# 2 Normative 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 Q.1236 (1999), *Intelligent Network Capability Set 3 – Management Information Model Requirements and Methodology*. + +## 2.1 Informative reference + +- ETSI ES 201 386 Ver.1.1.1 (1999), *Telecommunications Management Network (TMN); Service Switching Function (SSF) management information model*. + +# 3 Definitions + +This Recommendation defines the following terms: + +**3.1 assisting:** If SRF functionality is required but no appropriate SRP is available at the SSP, the call is forwarded to a second SSP, the "assisting SSP", having a suitable SRF. Signalling to this SRP is relayed via the assisting SSP. + +**3.2 IN-based Service Feature Control:** This is the control of the feature processing of a specified IN service. It uses signalling addresses to invoke associations with SCPs. + +**3.3 IN trigger:** A mechanism for deciding under which conditions normal call processing has to be suspended and IN-based Service Feature Control has to be activated. + +**3.4 service key:** An abstract identification of service logic. Within this Recommendation, only the concept of a 'logical' service key is used. + +Other terms used in this Recommendation are defined in the Q.12xx series of Recommendations (IN CS-1). + +# **4 Abbreviations** + +This Recommendation uses the following abbreviations: + +| | | +|-------|----------------------------------------------------------------------------------| +| ACSE | Association Control Service Element | +| AE | Application Entity | +| AP | Application Process | +| ASN.1 | Abstract Syntax Notation One | +| BCSM | Basic Call State Model | +| CMIP | Common Management Information Protocol | +| CMISE | Common Management Information Service Element | +| INAP | Intelligent Network Application Protocol | +| ISUP | ISDN User Part | +| ITU | International Telecommunication Union | +| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector | +| MOC | Managed Object Class | +| NE | Network Element | +| OS | Operations System | +| OSI | Open Systems Interconnection | +| SCF | Switching Control Function | +| SCP | Switching Control Point | +| SE | application-service-element | +| SMASE | Systems Management Application Service Element | +| SRF | Special Resource Function | +| SRP | Special Resource Point | +| SSF | Service Switching Function | +| SSP | Service Switching Point | +| TDP | Trigger Detection Point | +| TMN | Telecommunications Management Network | + +# **5 Requirements met** + +## **5.1 Management functional areas** + +This Recommendation meets the following SSF management: + +### **5.1.1 Fault management** + +- Report automatic restoration. + +### **5.1.2 Configuration Management** + +- Download trigger data. + +The following trigger data is configurable for each trigger: + +- trigger type; +- routing to SCF; +- service key; +- congestion control (action to be taken in case of SCF overload); + - a) terminate call; + - b) play announcement; + - c) alternate route. +- Modify trigger data. +- Delete trigger data. +- Block and unblock trigger tables. + +### **5.1.3 Accounting management** + +For further study. + +### **5.1.4 Performance management** + +- Monitor call gapping, e.g.: + - number of calls blocked per call gap; + - number of calls blocked per call gap type. +- Manage call gap parameters: + - type of call gapping (manual, SCF overload, destination overload, etc.); + - status of call gap; + - call gapping criteria (e.g. calling region, called region, calling party, called party); + - gapping duration interval; + - call treatment for gapped calls (e.g. play announcement, busy tone). +- Traffic measurements, e.g.: + - number of failed calls due to caller abandon, SSF failure or SCF failure; + - number of successful calls; + - number of queries sent to SCF; + - average waiting time per call. + +### **5.1.5 Security management** + +For further study. + +## **5.2 Operational requirements** + +The operational requirements to be met by this specification are specified in Recommendation Q.1236. That Recommendation provides detailed requirements for the functionality identified in the overview below. The information model specified in this Recommendation is being released in phases and presently the requirement identified as OR9 in Recommendation Q.1236 is not met by this information model. OR9 would require access to charging information while a call was in progress. Support of this capability would result in introducing complexity that is currently not supported. + +### **5.2.1 Introduction** + +The following operational requirements are defined: + +- Configure triggering of IN-based service feature control; +- Start call gapping; +- Stop call gapping; +- Read current gapping criteria; +- Configure default values (call gapping); +- Configure SRF/SCF relaying capabilities of the SSF; +- Configure SRF assisting; +- Configure default parameters (service filtering); +- Read service filtering; +- Configure a set of originating call set-up data for SCF initiated call; +- Read current defined originating call set-up data for SCF initiated call; +- Configure IN charging; +- Configure error handling; +- Start INAP Measurements counters; +- Stop INAP Measurements counters; +- Read current INAP Measurement counters. + +# **6 Information Model – Overview** + +## **6.1 Managed Object Class Relationship Model** + +### **6.1.1 "Configure SRF/SCF relaying capabilities" and "Configure SRF assisting" Relationships** + +See Figure 1. + +![UML Class Diagram showing relationships between SSF AP, SSF/SCF AE, SSF/SRF AE, SSF/SSF AE, Assist Treatment, Timer, and TDP.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +``` + +classDiagram + class SSF_AP["SSF AP"] + class SSF_SCF_AE["SSF/SCF AE"] + class SSF_SRF_AE["SSF/SRF AE"] + class SSF_SSF_AE["SSF/SSF AE"] + class Assist_Treatment["Assist Treatment"] + class Timer + class TDP + + SSF_AP o-- SSF_SCF_AE + SSF_AP o-- SSF_SRF_AE + SSF_AP o-- SSF_SSF_AE + SSF_SCF_AE "1..*" -- "1" Assist_Treatment + SSF_SRF_AE "1..*" -- "1" Assist_Treatment + SSF_SRF_AE "1..*" -- "1" Assist_Treatment + SSF_SSF_AE "1..*" -- "1..*" Timer + Assist_Treatment "1" -- "1" TDP + class SSF_SRF_AE { + IP_Capabilities + } + class Assist_Treatment { + IP_cAvailable + Scfld_Mapping + Correlation_Id_mapping + } + class TDP { + Trigger_Criteria + } + +``` + +The diagram illustrates the relationships between various Managed Objects (MOCs) in the SSF system. At the top is the **SSF AP** class. It has three aggregation relationships (indicated by hollow diamonds) with **SSF/SCF AE**, **SSF/SRF AE**, and **SSF/SSF AE**. **SSF/SCF AE** has a one-to-many relationship (1 to 1..\*) with **Assist Treatment**. **SSF/SRF AE** has a one-to-many relationship (1 to 1..\*) with **Assist Treatment** and a one-to-many relationship (1 to 1..\*) with **Assist Treatment**. **SSF/SSF AE** has a one-to-many relationship (1 to 1..\*) with **Timer**. **Assist Treatment** has a one-to-one relationship (1 to 1) with **TDP**. The **Assist Treatment** class contains three attributes: **IP cAvailable**, **Scfld Mapping**, and **Correlation Id mapping**. The **SSF/SRF AE** class contains one attribute: **IP Capabilities**. The **TDP** class contains one attribute: **Trigger Criteria**. + +UML Class Diagram showing relationships between SSF AP, SSF/SCF AE, SSF/SRF AE, SSF/SSF AE, Assist Treatment, Timer, and TDP. + +T0413100-99 + +**Figure 1/Q.836.1 – "Configure SRF/SCF relaying capabilities" and "Configure SRF assisting" Relationships** + +### 6.1.2 Managed Object descriptions + +#### 6.1.2.1 SSF AP + +##### General description + +The SSF Application Process MOC represents all of the possible SSF processes associated with the SSF-SCF, SSF-SRF and SSF-SSF interface. Contained within this class are all the Application Entities, i.e. the set of INAP messages. + +#### 6.1.2.2 SSF/SRF AE + +##### General description + +The "SSF/SRF AE" MOC represents the set of INAP messages defined for the SSF-SRF interface. It has a many-to-one relationship with the Assist Treatment MOC. + +##### Attributes + +- IP Capabilities: describes which type of feature interactions are possible by the SRF. + +#### **6.1.2.3 SSF/SCF AE** + +##### **General description** + +The SSF/SCF Application Entity MOC represents the set of INAP messages defined for the SSF-SCF interface. It has a many-to-one relationship with the Assist Treatment MOC. + +#### **6.1.2.4 SSF/SSF AE** + +##### **General description** + +The SSF/SSF Application Entity MOC represents the set of INAP messages defined for the SSF-SSF interface. These messages will be enveloped in ISUP. + +#### **6.1.2.5 Assist Treatment** + +##### **General description** + +The "Assist Treatment" MOC represents the set of operations contained within the SSF/SRF and SSF/SCF Application Entities. The Assist Treatment MOC has a one-to-one relationship with the TDP MOC. + +##### **Attributes** + +- IP Available specifies which SRF is available and what features it can support. +- SCF Id mapping is used to identify which SCF the Assist treatment is to be sent to. +- Correlation Id is used to identify which call is related to the SRF association. + +#### **6.1.2.6 TDP** + +##### **General description** + +The TDP MOC is used to describe at which conditions normal call processing has to be suspended and IN-based service feature control is activated. It has a one-to-one relationship with the Assist Treatment MOC. + +##### **Attributes** + +- Trigger Criteria represents the conditions upon which the trigger is initiated. + +#### **6.1.2.7 Timer** + +##### **General description** + +The Timer MOC represents the timer that is set at association time between the SSF control and assisting. The timer is controlled and reset if necessary by the controlling SSF. + +## **6.2 Inheritance Hierarchy** + +See Figure 2. + +![Inheritance Hierarchy diagram showing a 'top' node branching into several categories: M.3100 Managed Element, bcs, tdp, triggerBase, inCallGap, sfAccess, and event Configuration. Further sub-nodes include Ported Number Trigger, tdp subclasses, triggerBase subclasses, and iNapCounter.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +graph TD + top[top] --- M3100[M.3100 Managed Element] + top --- bcs[bcs] + top --- tdp[tdp] + top --- triggerBase[triggerBase] + top --- inCallGap[inCallGap] + top --- sfAccess[sfAccess] + top --- eventConfig[event Configuration] + + M3100 --- PNTP[Ported Number Trigger] + tdp --- tdpSub[tdp subclasses] + triggerBase --- triggerBaseSub[triggerBase subclasses] + inCallGap --- iNapCounter[iNapCounter] + +``` + +T0413110-99 + +Inheritance Hierarchy diagram showing a 'top' node branching into several categories: M.3100 Managed Element, bcs, tdp, triggerBase, inCallGap, sfAccess, and event Configuration. Further sub-nodes include Ported Number Trigger, tdp subclasses, triggerBase subclasses, and iNapCounter. + +**Figure 2/Q.836.1 – Inheritance Hierarchy** + +## 6.3 Naming Hierarchy + +See Figure 3. + +![Naming Hierarchy diagram showing a 'root' node leading to 'M.3100 Managed Element', which then branches into bcs, customer Profile, cTP/tTP and subclasses, Routing Information, and scfAccess. Further sub-nodes include event Configuration, tdp (and subclasses), and inCallGap.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +``` + +graph TD + root[root] --- M3100[M.3100 Managed Element] + M3100 --- bcs[bcs] + M3100 --- customerProfile[customer Profile] + M3100 --- cTPtTP[cTP/tTP and subclasses] + M3100 --- RoutingInformation[Routing Information] + M3100 --- scfAccess[scfAccess] + + bcs --- eventConfig[event Configuration] + cTPtTP --- tdpSub[tdp (and subclasses)] + scfAccess --- inCallGap[inCallGap] + +``` + +T0413120-99 + +Naming Hierarchy diagram showing a 'root' node leading to 'M.3100 Managed Element', which then branches into bcs, customer Profile, cTP/tTP and subclasses, Routing Information, and scfAccess. Further sub-nodes include event Configuration, tdp (and subclasses), and inCallGap. + +**Figure 3/Q.836.1 – Naming Hierarchy** + +# 7 Managed Object Class Definitions + +## 7.1 IN Authorization + +inAuthorization MANAGED OBJECT CLASS + +**DERIVED FROM** "Recommendation X.721 : 1992": top; + +**CHARACTERIZED BY** + +inAuthorizationPackage **PACKAGE** + +**BEHAVIOUR** + +inAuthorizationBehaviour BEHAVIOUR + +DEFINED AS "This object class is used to support IN features offered to customers from remote exchanges. The inAuthorization managed object is associated with trunk- or office-based triggers to identify the customers who have access to the IN capabilities.";; + +**ATTRIBUTES** + +inAuthorizationId GET;;; + +**REGISTERED AS** {inSSFManagedObjectClass 101}; + +inAuthorizationOriginating MANAGED OBJECT CLASS + +**DERIVED FROM** inAuthorization; + +**CHARACTERIZED BY** + +inAuthorizationOriginatingPackage **PACKAGE** + +**BEHAVIOUR** + +inAuthorizationOriginatingBehaviour BEHAVIOUR + +DEFINED AS "This object class is used to authorize the use of originating triggers or trigger bases by individual customers. This managed object class may only be associated with originating side triggers or trigger bases. + +This object is only used to associate triggers to customers in remote exchanges. For line based (customer profile based) triggers the association to a particular directory number is established via the trigger criteria in the appropriate trigger object.";; + +**ATTRIBUTES** + +authenticationCode SET-BY-CREATE, -- Replaceable but not readable. +callingPartyNumberList GET-REPLACE ADD-REMOVE;; + +**REGISTERED AS** {inSSFManagedObjectClass 102}; + +inAuthorizationTerminating MANAGED OBJECT CLASS + +**DERIVED FROM** inAuthorization; + +**CHARACTERIZED BY** + +inAuthorizationTerminatingPackage **PACKAGE** + +**BEHAVIOUR** + +inAuthorizationTerminatingBehaviour BEHAVIOUR + +DEFINED AS "This object class is used to authorize the use of terminating triggers or trigger bases by individual customers. This managed object class may only be associated with terminating side triggers or trigger bases. + +This object is only used to associate triggers to customers in remote exchanges. For line-based (customer profile based) triggers the association to a particular directory number is established via the trigger criteria in the appropriate trigger object.";; + +### ATTRIBUTES + +calledPartyNumberList + +**GET-REPLACE ADD-REMOVE;;;** + +**REGISTERED AS** {inSSFManagedObjectClass 61}; + +## 7.2 Basic Call State Model (BCSM) + +bcsm **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation X.721 : 1992": top; + +### CHARACTERIZED BY + +bcsmPackage **PACKAGE** + +### BEHAVIOUR + +bcsmBehaviour **BEHAVIOUR** + +**DEFINED AS** "This object class represents the basic call processing capability.";; + +### ATTRIBUTES + +bcsmId **GET,** + +version **GET SET-BY-CREATE;;;** + +**REGISTERED AS** {inSSFManagedObjectClass 62}; + +## 7.3 Trigger Detection Point (TDP) + +tdp **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation X.721 : 1992": top; + +### CHARACTERIZED BY + +tdpPackage **PACKAGE** + +### BEHAVIOUR + +tdpBehaviour **BEHAVIOUR** + +**DEFINED AS** "This object class is a non-instantiable superclass for trigger point objects. Trigger point objects serve as launch points for the invocation of IN features. + +The tdpId attribute is used as the RDN for naming. + +TDPs may be of one of two types: "request" (which request that a control relation be established between the SCF and SSF and an operation may need to be performed at the SCF, the SSF may need to wait before continuing call processing) and a "notification" (which does not result in the establishment of a control relation). + +The triggerAssociation attribute identifies the trigger base associated with that trigger. + +The inEscape attribute defines a set of conditions that will cause escape from IN feature invocation and result in normal call processing. + +The congestionAction attribute defines the action to be taken when the SCF is overloaded and IN service requests cannot be processed in a timely manner. Possible actions are termination of the call, playing of an announcement with subsequent termination or playing announcement with user option of continuing the call. + +The serviceKey attribute defines which IN service will be activated in response to this trigger. + +The administrative attribute may be used to administratively lock a trigger; this results in the trigger becoming inactive. Only the locked and unlocked state values are used (shutting-down is not meaningful in this context).";; + +### ATTRIBUTES + +| | | +|----------------------------------------|----------------| +| tdpId | GET, | +| tdpMode | GET-REPLACE, | +| triggerAssociation | GET-REPLACE, | +| inEscape | GET-REPLACE, | +| congestionAction | GET-REPLACE, | +| serviceKey | GET-REPLACE, | +| "ITU-T Rec. X.735":administrativeState | GET-REPLACE;;; | + +**REGISTERED AS** {inSSFManagedObjectClass 63}; + +## 7.4 Originating Attempt Authorized Trigger + +**o\_Attempt\_Authorized MANAGED OBJECT CLASS** + +**DERIVED FROM** tdp; + +**CHARACTERIZED BY** + +o\_Attempt\_AuthorizedPackage **PACKAGE** + +**BEHAVIOUR** + +o\_Attempt\_AuthorizedBehaviour **BEHAVIOUR** + +DEFINED AS "This object class is a subclass of tdp. It is used to trigger IN control at point in call O\_NULL & Authorize\_Origination\_Attempt when a seizure event was accepted. Triggering may be unconditional or dependent on trigger criteria. + +The attribute tdp1Criteria indicates whether the trigger is conditional or unconditional. If the trigger is conditional, the tdp1Criteria attribute contains the logical expression that specifies the applicable criteria. + +For trunk-based triggers only callingPartyNumber and bearerCapability are allowed. + +For subscriber- (customer profile) based triggers only classOfService is allowed.";; + +### ATTRIBUTES + +| | | +|--------------|----------------| +| tdp1Criteria | GET-REPLACE;;; | +|--------------|----------------| + +**REGISTERED AS** {inSSFManagedObjectClass 1}; + +## 7.5 Collected Information Trigger + +**collected\_InfoTrigger MANAGED OBJECT CLASS** + +**DERIVED FROM** tdp; + +**CHARACTERIZED BY** + +collected\_InfoPackage **PACKAGE** + +**BEHAVIOUR** + +collected\_InfoBehaviour **BEHAVIOUR** + +DEFINED AS "This object class is a subclass of tdp. It is used to trigger IN control at point in call collect Information as dialled digits are received. Triggering might be unconditional or dependent on trigger criteria. + +The attribute tdp2Criteria indicates whether the trigger is conditional or unconditional. If the trigger is conditional, the tdp2Criteria attribute contains the logical expression that specifies the applicable criteria. + +Valid parameters in the tdp2Criteria construct include: calledPartyNumber, callingPartyNumber, digitString and stringLength.";; + +**ATTRIBUTES** +tdp2Criteria + +GET-REPLACE;;; + +**REGISTERED AS** {inSSFManagedObjectClass 2}; + +## 7.6 Analysed Information Trigger + +analysed\_InfoTrigger **MANAGED OBJECT CLASS** + +**DERIVED FROM** tdp; + +**CHARACTERIZED BY** + +analysed\_InfoPackage **PACKAGE** + +**BEHAVIOUR** + +analysed\_InfoBehaviour **BEHAVIOUR** + +DEFINED AS "This object class is a subclass of tdp. It is used to trigger IN control at point in call Analyse Information when the exchange analyses the received digits. Triggering may be unconditional or dependent on trigger criteria. + +The attribute tdp3Criteria indicates whether the trigger is conditional or unconditional. If the trigger is conditional, the tdp3Criteria attribute contains the logical expression that specifies the applicable criteria. + +Valid parameters in the tdp3Criteria construct include: calledPartyNumber, callingPartyNumber, natureOfAddress, digitString, stringLength, facilityInformation and featureActivation.";; + +**ATTRIBUTES** +tdp3Criteria + +GET-REPLACE;;; + +**REGISTERED AS** {inSSFManagedObjectClass 3}; + +## 7.7 Route Select Failure Trigger + +route\_Select\_FailureTrigger **MANAGED OBJECT CLASS** + +**DERIVED FROM** tdp; + +**CHARACTERIZED BY** + +route\_Select\_FailurePackage **PACKAGE** + +**BEHAVIOUR** + +route\_Select\_FailureBehaviour **BEHAVIOUR** + +DEFINED AS "This object class is a subclass of tdp. It is used to trigger IN control at point in call Routing\_ & \_Alerting when the call fails due to a route select failure. Triggering may be unconditional or dependent on trigger criteria. + +The attribute tdp4Criteria indicates whether the trigger is conditional or unconditional. If the trigger is conditional, the tdp4Criteria attribute contains the logical expression that specifies the applicable criteria. + +Valid parameters in the tdp4Criteria construct include: cause, callingPartyNumber, and featureActivation.";; + +**ATTRIBUTES** +tdp4Criteria + +GET-REPLACE;;; + +**REGISTERED AS** {inSSFManagedObjectClass 4}; + +## 7.8 Originating Called Party Busy Trigger + +**o\_Called\_Party\_BusyTrigger MANAGED OBJECT CLASS** + +**DERIVED FROM** tdp; + +**CHARACTERIZED BY** + +o\_Called\_Party\_BusyPackage      **PACKAGE** + +**BEHAVIOUR** + +o\_Called\_Party\_BusyBehaviour BEHAVIOUR + +DEFINED AS "This object class is a subclass of tdp. It is used to trigger IN control at point in call Routing\_ &\_ Alerting when the call encounters a busy condition. Triggering may be unconditional or dependent on trigger criteria. + +The attribute tdp5Criteria indicates whether the trigger is conditional or unconditional. If the trigger is conditional, the tdp5Criteria attribute contains the logical expression that specifies the applicable criteria. + +Valid parameters in the tdp5Criteria construct include: cause and featureActivation.";; + +**ATTRIBUTES** + +tdp5Criteria + +GET-REPLACE;;; + +**REGISTERED AS** {inSSFManagedObjectClass 5}; + +## 7.9 Originating No Answer Trigger + +**o\_No\_AnswerTrigger MANAGED OBJECT CLASS** + +**DERIVED FROM** tdp; + +**CHARACTERIZED BY** + +o\_No\_AnswerPackage      **PACKAGE** + +**BEHAVIOUR** + +o\_No\_AnswerBehaviour BEHAVIOUR + +DEFINED AS "This object class is a subclass of tdp. It is used to trigger IN control at point in call Routing\_ &\_ Alerting when the call encounters a no-answer condition. Triggering may be unconditional or dependent on trigger criteria. + +The attribute tdp6Criteria indicates whether the trigger is conditional or unconditional. If the trigger is conditional, the tdp6Criteria attribute contains the logical expression that specifies the applicable criteria. + +Valid parameters in the tdp6Criteria construct include: cause and featureActivation.";; + +**ATTRIBUTES** + +tdp6Criteria + +GET-REPLACE;;; + +**REGISTERED AS** {inSSFManagedObjectClass 6}; + +## 7.10 Originating Answer Trigger + +**o\_AnswerTrigger MANAGED OBJECT CLASS** + +**DERIVED FROM** tdp; + +**CHARACTERIZED BY** + +o\_AnswerPackage      **PACKAGE** + +**BEHAVIOUR** + +o\_AnswerBehaviour BEHAVIOUR + +DEFINED AS "This object class is a subclass of tdp. It is used to trigger IN control at point in call O\_Active when the call is answered. Triggering may be unconditional or dependent on trigger criteria. + +The attribute tdp7Criteria indicates whether the trigger is conditional or unconditional. If the trigger is conditional, the tdp7Criteria attribute contains the logical expression that specifies the applicable criteria. + +Valid parameters in the tdp7Criteria construct include: facilityInformation and featureActivation.";; + +### ATTRIBUTES + +tdp7Criteria + +GET-REPLACE;;; + +REGISTERED AS {inSSFManagedObjectClass 7}; + +## 7.11 Originating Mid Call Trigger + +o\_Mid\_CallTrigger **MANAGED OBJECT CLASS** + +**DERIVED FROM** tdp; + +**CHARACTERIZED BY** + +o\_Mid\_CallPackage **PACKAGE** + +**BEHAVIOUR** + +o\_Mid\_CallBehaviour **BEHAVIOUR** + +DEFINED AS "This object class is a subclass of tdp. It is used to trigger IN control at point in call O\_Active when feature activation is invoked in the active state of the call. Triggering may be unconditional or dependent on trigger criteria. + +The attribute tdp8Criteria indicates whether the trigger is conditional or unconditional. If the trigger is conditional, the tdp8Criteria attribute contains the logical expression that specifies the applicable criteria. + +Valid parameters in the tdp8Criteria construct include: facilityInformation and featureActivation.";; + +### ATTRIBUTES + +tdp8Criteria + +GET-REPLACE;;; + +REGISTERED AS {inSSFManagedObjectClass 8}; + +## 7.12 Originating Disconnect Trigger + +o\_DisconnectTrigger **MANAGED OBJECT CLASS** + +**DERIVED FROM** tdp; + +**CHARACTERIZED BY** + +o\_DisconnectPackage **PACKAGE** + +**BEHAVIOUR** + +o\_DisconnectBehaviour **BEHAVIOUR** + +DEFINED AS "This object class is a subclass of tdp. It is used to trigger IN control at point in call O\_Active when a disconnect occurs. Triggering may be unconditional or dependent on trigger criteria. + +The attribute tdp9Criteria indicates whether the trigger is conditional or unconditional. If the trigger is conditional, the tdp9Criteria attribute contains the logical expression that specifies the applicable criteria. + +Valid parameters in the tdp9Criteria construct include: cause and featureActivation.";; + +### ATTRIBUTES + +tdp9Criteria + +GET-REPLACE;;; + +**REGISTERED AS** {inSSFManagedObjectClass 9}; + +## 7.13 Originating Abandon Trigger + +**o\_AbandonTrigger** **MANAGED OBJECT CLASS** + +**DERIVED FROM** tdp; + +**CHARACTERIZED BY** + +o\_AbandonPackage **PACKAGE** + +**BEHAVIOUR** + +o\_AbandonBehaviour **BEHAVIOUR** + +**DEFINED AS** "This object class is a subclass of tdp. It is used to trigger IN control at points in call when a call abandon occurs. Triggering may be unconditional or dependent on trigger criteria. + +The attribute tdp10Criteria indicates whether the trigger is conditional or unconditional. If the trigger is conditional, the tdp10Criteria attribute contains the logical expression that specifies the applicable criteria. + +Valid parameters in the tdp10Criteria construct include: cause and featureActivation.";; + +**ATTRIBUTES** + +tdp10Criteria + +GET-REPLACE;;; + +**REGISTERED AS** {inSSFManagedObjectClass 10}; + +## 7.14 Terminating Attempt Authorized Trigger + +**t\_Attempt\_Authorized** **MANAGED OBJECT CLASS** + +**DERIVED FROM** tdp; + +**CHARACTERIZED BY** + +t\_Attempt\_AuthorizedPackage **PACKAGE** + +**BEHAVIOUR** + +t\_Attempt\_AuthorizedBehaviour **BEHAVIOUR** + +**DEFINED AS** "This object class is a subclass of tdp. It is used to trigger IN control at point in call T\_NULL & Authorize\_Termination\_Attempt when a seizure event was accepted. Triggering may be unconditional or dependent on trigger criteria. + +The attribute tdp12Criteria indicates whether the trigger is conditional or unconditional. If the trigger is conditional, the tdp12Criteria attribute contains the logical expression that specifies the applicable criteria. + +Valid parameters in the tdp12Criteria construct include: callingPartyNumber and featureActivation.";; + +**ATTRIBUTES** + +tdp12Criteria + +GET-REPLACE;;; + +**REGISTERED AS** {inSSFManagedObjectClass 12}; + +## 7.15 Terminating Called Party Busy Trigger + +**t\_Called\_Party\_BusyTrigger** **MANAGED OBJECT CLASS** + +**DERIVED FROM** tdp; + +**CHARACTERIZED BY** + +t\_Called\_Party\_BusyPackage **PACKAGE** + +### BEHAVIOUR + +t\_Called\_Party\_BusyBehaviour BEHAVIOUR + +DEFINED AS "This object class is a subclass of tdp. It is used to trigger IN control at point in call Select\_Facility\_&\_Present\_Call when the call encounters a busy condition. Triggering may be unconditional or dependent on trigger criteria. + +The attribute tdp13Criteria indicates whether the trigger is conditional or unconditional. If the trigger is conditional, the tdp13Criteria attribute contains the logical expression that specifies the applicable criteria. + +Valid parameters in the tdp13Criteria construct include: cause, callingPartyNumber and featureActivation.";; + +### ATTRIBUTES + +tdp13Criteria + +GET-REPLACE;;; + +REGISTERED AS {inSSFManagedObjectClass 13}; + +## 7.16 Terminating No Answer Trigger + +t\_No\_AnswerTrigger MANAGED OBJECT CLASS + +DERIVED FROM tdp; + +CHARACTERIZED BY + +t\_No\_AnswerPackage PACKAGE + +### BEHAVIOUR + +t\_No\_AnswerBehaviour BEHAVIOUR + +DEFINED AS "This object class is a subclass of tdp. It is used to trigger IN control at point in call Select\_Facility\_&\_Present\_Call when the call encounters a no-answer condition. Triggering may be unconditional or dependent on trigger criteria. + +The attribute tdp14Criteria indicates whether the trigger is conditional or unconditional. If the trigger is conditional, the tdp14Criteria attribute contains the logical expression that specifies the applicable criteria. + +Valid parameters in the tdp14Criteria construct include: cause, callingPartyNumber and featureActivation.";; + +### ATTRIBUTES + +tdp14Criteria + +GET-REPLACE;;; + +REGISTERED AS {inSSFManagedObjectClass 14}; + +## 7.17 Terminating Answer Trigger + +t\_AnswerTrigger MANAGED OBJECT CLASS + +DERIVED FROM tdp; + +CHARACTERIZED BY + +t\_AnswerPackage PACKAGE + +### BEHAVIOUR + +t\_AnswerBehaviour BEHAVIOUR + +DEFINED AS "This object class is a subclass of tdp. It is used to trigger IN control at point in call T\_Active when the call is answered. Triggering may be unconditional or dependent on trigger criteria. + +The attribute tdp15Criteria indicates whether the trigger is conditional or unconditional. If the trigger is conditional, the tdp15Criteria attribute contains the logical expression that specifies the applicable criteria. + +Valid parameters in the tdp15Criteria construct include: facilityInformation and featureActivation.";; + +### **ATTRIBUTES** + +tdp15Criteria + +GET-REPLACE;;; + +**REGISTERED AS** {inSSFManagedObjectClass 15}; + +## **7.18 Terminating Mid Call Trigger** + +t\_Mid\_CallTrigger **MANAGED OBJECT CLASS** + +**DERIVED FROM** tdp; + +**CHARACTERIZED BY** + +o\_Mid\_CallPackage **PACKAGE** + +**BEHAVIOUR** + +t\_Mid\_CallBehaviour **BEHAVIOUR** + +DEFINED AS "This object class is a subclass of tdp. It is used to trigger IN control at point in call T\_Active when feature activation is invoked in the active state of the call. Triggering may be unconditional or dependent on trigger criteria. + +The attribute tdp16Criteria indicates whether the trigger is conditional or unconditional. If the trigger is conditional, the tdp16Criteria attribute contains the logical expression that specifies the applicable criteria. + +Valid parameters in the tdp16Criteria construct include: facilityInformation and featureActivation.";; + +### **ATTRIBUTES** + +tdp16Criteria + +GET-REPLACE;;; + +**REGISTERED AS** {inSSFManagedObjectClass 16}; + +## **7.19 Terminating Disconnect Trigger** + +t\_DisconnectTrigger **MANAGED OBJECT CLASS** + +**DERIVED FROM** tdp; + +**CHARACTERIZED BY** + +t\_DisconnectPackage **PACKAGE** + +**BEHAVIOUR** + +t\_DisconnectBehaviour **BEHAVIOUR** + +DEFINED AS "This object class is a subclass of tdp. It is used to trigger IN control at point in call T\_Active when a disconnect occurs. Triggering may be unconditional or dependent on trigger criteria. + +The attribute tdp17Criteria indicates whether the trigger is conditional or unconditional. If the trigger is conditional, the tdp17Criteria attribute contains the logical expression that specifies the applicable criteria. + +Valid parameters in the tdp17Criteria construct include: cause and featureActivation.";; + +### **ATTRIBUTES** + +tdp17Criteria + +GET-REPLACE;;; + +**REGISTERED AS** {inSSFManagedObjectClass 17}; + +## 7.20 Terminating Abandon Trigger + +t\_AbandonTrigger **MANAGED OBJECT CLASS** + +**DERIVED FROM** tdp; + +**CHARACTERIZED BY** + +t\_AbandonPackage **PACKAGE** + +**BEHAVIOUR** + +t\_AbandonBehaviour **BEHAVIOUR** + +DEFINED AS "This object class is a subclass of tdp. It is used to trigger IN control at points in call when a call abandon occurs. Triggering may be unconditional or dependent on trigger criteria. + +The attribute tdp18Criteria indicates whether the trigger is conditional or unconditional. If the trigger is conditional, the tdp18Criteria attribute contains the logical expression that specifies the applicable criteria. + +Valid parameters in the tdp18Criteria construct include: cause and featureActivation.";; + +**ATTRIBUTES** + +tdp18Criteria + +GET-REPLACE;;; + +**REGISTERED AS** {inSSFManagedObjectClass 18}; + +## 7.21 Trigger Base + +triggerBase **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation X.721 : 1992": top; + +**CHARACTERIZED BY** + +triggerBasePackage **PACKAGE** + +**BEHAVIOUR** + +triggerBaseBehaviour **BEHAVIOUR** + +DEFINED AS "This object class is used to define an association between a set of triggers and the scope of these triggers, e.g. Originating Line, Terminating Line, Originating Trunk, Terminating Trunk, Private Facility, Office (Analysed Info Base). + +The triggerBaseId attribute is used for naming. + +The associatedObject attribute is a pointer to the object instance with which the trigger base is associated. + +The basePriority attribute allows specification of which triggerList will be active when several would apply simultaneously to a call. + +The trigger list is a prioritized list of trigger objects that will apply to a call. The triggers that may be contained in this list will be constrained by the behaviour of subclasses of this object class. + +The administrative attribute may be used to administratively lock a trigger-base; this results in the trigger-base becoming inactive, thereby deactivating all triggers associated with that base. Only the locked and unlocked state values are used (shutting-down is not meaningful in this context).";; + +**ATTRIBUTES** + +triggerBaseId + +associatedObject + +basePriority + +triggerList + +"ITU-T Rec. X.735":administrativeState + +GET, + +GET SET-BY-CREATE, + +GET-REPLACE, + +GET-REPLACE ADD-REMOVE, + +GET-REPLACE;;; + +**REGISTERED AS** {inSSFManagedObjectClass 21}; + +## 7.22 Originating Line Trigger Base + +**o\_lineTriggerBase MANAGED OBJECT CLASS** + +**DERIVED FROM** triggerBase; + +**CHARACTERIZED BY** + +o\_lineTriggerBasePackage **PACKAGE** + +**BEHAVIOUR** + +o\_lineTriggerBaseBehaviour **BEHAVIOUR** + +DEFINED AS "The triggerList attribute of this object class is constrained to triggers of type (see Rec. Q.1241) 1,2,3,4,5,6 and 8.";;;; + +**REGISTERED AS** {inSSFManagedObjectClass 22}; + +## 7.23 Originating Trunk Trigger Base + +**o\_trunkTriggerBase MANAGED OBJECT CLASS** + +**DERIVED FROM** triggerBase; + +**CHARACTERIZED BY** + +o\_trunkTriggerBasePackage **PACKAGE** + +**BEHAVIOUR** + +o\_trunkTriggerBehaviour **BEHAVIOUR** + +DEFINED AS "The triggerList attribute of this object class is constrained to triggers of type (see Rec. Q.1241) 1,2,3,4,5,6 and 8.";;;; + +**REGISTERED AS** {inSSFManagedObjectClass 23}; + +## 7.24 Terminating Line Trigger Base + +**t\_lineTriggerBase MANAGED OBJECT CLASS** + +**DERIVED FROM** triggerBase; + +**CHARACTERIZED BY** + +t\_lineTriggerBasePackage **PACKAGE** + +**BEHAVIOUR** + +t\_lineTriggerBaseBehaviour **BEHAVIOUR** + +DEFINED AS "The triggerList attribute of this object class is constrained to triggers of type (see Rec. Q.1241) 12,13,14 and 16.";;;; + +**REGISTERED AS** {inSSFManagedObjectClass 24}; + +## 7.25 Terminating Trunk Trigger Base + +**t\_trunkTriggerBase MANAGED OBJECT CLASS** + +**DERIVED FROM** triggerBase; + +**CHARACTERIZED BY** + +t\_trunkTriggerBasePackage **PACKAGE** + +**BEHAVIOUR** + +t\_trunkTriggerBaseBehaviour **BEHAVIOUR** + +DEFINED AS "The triggerList attribute of this object class is constrained to triggers of type (see Rec. Q.1241) 12,13,14 and 16.";;;; + +**REGISTERED AS** {inSSFManagedObjectClass 25}; + +## **7.26 Private Facility Trigger Base** + +privateFacilityTriggerBase **MANAGED OBJECT CLASS** + +**DERIVED FROM** triggerBase; + +**CHARACTERIZED BY** + +privateFacilityBasePackage **PACKAGE** + +**BEHAVIOUR** + +privateFacilityBaseBehaviour **BEHAVIOUR** + +DEFINED AS "The triggerList attribute of this object class may contain triggers of any type (see Rec. Q.1241).";; + +**REGISTERED AS** {inSSFManagedObjectClass 26}; + +## **7.27 Office Trigger Base** + +officeTriggerBase **MANAGED OBJECT CLASS** + +**DERIVED FROM** triggerBase; + +**CHARACTERIZED BY** + +officeTriggerBasePackage **PACKAGE** + +**BEHAVIOUR** + +officeTriggerBaseBehaviour **BEHAVIOUR** + +DEFINED AS "The triggerList attribute of this object class may contain triggers of type (see Rec. Q.1241) 3-18.";; + +**REGISTERED AS** {inSSFManagedObjectClass 27}; + +## **7.28 IN Call Gap** + +inCallGap **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation X.721 : 1992": top; + +**CHARACTERIZED BY** + +inCallGapPackage **PACKAGE** + +**BEHAVIOUR** + +inCallGapBehaviour **BEHAVIOUR** + +DEFINED AS "This object class defines the OSF defined call gapping criteria. + +The inCallGapId attribute is used as the RDN for naming. + +The gapCriteria attribute allows configuring criteria for the calls to be gapped. Calls may be gapped for particular destinations, particular services or both. + +The gapDuration attribute specifies the time interval for which gapping is active. + +The gapInterval attribute specifies the minimum inter-arrival time between calls that will be passed. + +The controlType attribute indicates how call gapping was activated. Call gapping may be activated by the SCP or the OSF. + +The gapTreatment attribute specifies the treatment to be given to calls that have been gapped. + +The administrative attribute may be used to administratively lock a inCallGap object.";; + +### ATTRIBUTES + +| | | +|----------------------------------------|----------------| +| inCallGapId | GET, | +| gapCriteria | GET-REPLACE, | +| gapDuration | GET-REPLACE, | +| gapInterval | GET-REPLACE, | +| controlType | GET-REPLACE, | +| gapTreatment | GET-REPLACE, | +| "ITU-T Rec. X.735":administrativeState | GET-REPLACE;;; | + +**REGISTERED AS** {inSSFManagedObjectClass 28}; + +## 7.29 Service Filtering + +serviceFiltering **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation X.721 : 1992": top; + +### CHARACTERIZED BY + +serviceFilteringPackage **PACKAGE** + +### BEHAVIOUR + +serviceFilteringBehaviour **BEHAVIOUR** + +**DEFINED AS** "This object class is used to specify how IN calls are to be filtered. It contains the criteria for filtering and specifies the treatment of filtered calls. + +The object is created by the SSF as a result of the receipt of an activateServiceFiltering operation from the SCF. + +- If the filteringCriteria attribute in the received operation has the value serviceKey, the filtering will be activated for that particular service and the serviceFiltering object will be associated with that particular service. +- If the filteringCriteria attribute in the received operation has the value dialledNumber or callingPartyNumber, the filtering will be activated for the particular services associated with the calling party or dialled number. + +The SCF specifies that the network-dependent default duration is to be used by setting the attribute *duration* to "-2". + +This object instance is automatically deleted when the stopTime is reached or when duration expires. Prior to deletion, the objectId, filteringCriteria and the countersValues are passed to the INAP ASE to be used in the INAP *serviceFilteringResponse* operation. + +The serviceFilterId attribute is used as the RDN for naming. + +The startTime attribute specifies the time at which service filtering will be or is started. + +The stopTime attribute specifies the time at which service filtering will be stopped. If the incoming message specified a duration, the stop time is derived by adding the duration to the start time. If default timing was specified in the incoming request the stopTime will be set at the time this object instance is created by adding the default duration (specified in the serviceFilteringDefaultDuration object) to the specified start time. + +**NOTE** – This implies that changes to the default duration made subsequent to creation of this object instance will have no effect on the stopTime. + +The releaseCause specifies the release cause to be used for filtered calls. + +The billingChargingCharacteristics attribute specifies the charging to be applied to filtered calls. + +The filteredCallTreatment attribute specifies the treatment to be given to calls that have been filtered, e.g. inBandInfo, tone, etc.;; + +### ATTRIBUTES + +| | | +|--------------------------------|--------| +| serviceFilterId | GET, | +| startTime | GET, | +| stopTime | GET, | +| releaseCause | GET, | +| billingChargingCharacteristics | GET, | +| filteredCallTreatment | GET;;; | + +### CONDITIONAL PACKAGES + +TimeBasedFilteringPackage**PACKAGE** + +timeBasedFilteringPackageBhvr **BEHAVIOUR** + +"This package specifies that all calls an interval of at least "interval" must pass between calls that invoke SCF service logic";; + +### ATTRIBUTES + +| | | +|----------|--------------| +| interval | GET-REPLACE; | +|----------|--------------| + +REGISTERED AS { inSSFPackage 1}; PRESENT IF "the incoming activateServiceFiltering message specified time based filtering", + +countBasedFilteringPackage**PACKAGE** + +countBasedFilteringPackageBhvr **BEHAVIOUR** + +"This package specifies that only every nth call will be sent to the SFC where N is numberOfCalls + 1";; + +### ATTRIBUTES + +| | | +|---------------|--------------| +| numberOfCalls | GET-REPLACE; | +|---------------|--------------| + +REGISTERED AS { inSSFPackage 2}; PRESENT IF "the incoming activateServiceFiltering message specified time based filtering", + +countersPackage **PACKAGE** + +countersPackageBhvr **BEHAVIOUR** + +"This package specifies the maximum number of counters to be used and provides pointers to the counters used";; + +### ATTRIBUTES + +| | | +|-------------------------|------| +| maximumNumberOfCounters | GET, | +| counterPointerList | GET; | + +REGISTERED AS { inSSFPackage 3}; PRESENT IF "the incoming activateServiceFiltering message specified the use of counters", + +:: + +REGISTERED AS {inSSFManagedObjectClass 29}; + +## 7.30 Service Filtering Counter + +serviceFilteringCounter **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation X.721 : 1992": top; + +**CHARACTERIZED BY** + +serviceFilteringCounterPackage **PACKAGE** + +**BEHAVIOUR** + +serviceFilteringCounterBehaviour **BEHAVIOUR** + +DEFINED AS "This object counts calls that have been subjected to service filtering. The counterValue attribute contains the count and is automatically reset whenever the SSF sends a serviceFilteringResponse for that service filter. + +The associatedServiceFilter attribute points to the serviceFilter for which this counter is active.";; + +### ATTRIBUTES + +| | | +|---------------------------|--------| +| serviceFilteringCounterId | GET, | +| counterValue | GET, | +| associatedServiceFilter | GET;;; | + +REGISTERED AS {inSSFManagedObjectClass 30}; + +**NOTE – Do we need to model how counters are used. I.e. what causes one or another counter to be incremented.** + +## 7.31 Service Filtering Duration Default + +serviceFilteringDurationDefault **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation X.721 : 1992": top; + +**CHARACTERIZED BY** + +serviceFilteringDurationDefaultPackage **PACKAGE** + +**BEHAVIOUR** + +serviceFilteringDurationDefaultBehaviour **BEHAVIOUR** + +**DEFINED AS** "This object class stores the default duration to be used for service filtering. This value is stored in the interval attribute.";; + +**ATTRIBUTES** + +| | | +|-----------------------------------|----------------| +| serviceFilteringDurationDefaultId | GET, | +| interval | GET-REPLACE;;; | + +**REGISTERED AS** {inSSFManagedObjectClass 31}; + +## 7.32 Initiate Call Default Information + +initiateCallDefaultInformation **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation X.721 : 1992": top; + +**CHARACTERIZED BY** + +initiateCallDefaultInformationPackage **PACKAGE** + +**BEHAVIOUR** + +initiateCallDefaultInformationBehaviour **BEHAVIOUR** + +**DEFINED AS** "This object class stores the default information to be used in setting up a call when the SCF provides incomplete call-setup information in the initiateCallAttempt operation.";; + +**ATTRIBUTES** + +| | | +|----------------------------------|----------------| +| initiateCallDefaultInformationId | GET, | +| callingPartyNumber | GET-REPLACE, | +| callingPartyCategory | GET- REPLACE, | +| forwardCallIndicators | GET- REPLACE, | +| natureOfConnectionIndicator | GET- REPLACE, | +| bearerService | GET-REPLACE;;; | + +**REGISTERED AS** {inSSFManagedObjectClass 32}; + +## 7.33 INAP Counter + +iNAPCounter **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation X.721 : 1992": top; + +**CHARACTERIZED BY** + +iNAPCounterPackage **PACKAGE** + +**BEHAVIOUR** + +iNAPCounterBehaviour **BEHAVIOUR** + +**DEFINED AS** "This object class provides the capability for counting particular events that occur in association with the use of INAP. + +The attribute observedEventId specifies the semantics of the events counted by this particular counter. This value cannot be changed after the counter has been instantiated. + +The attribute observedSCFAccessList identifies the SCF accesses that are being observed by this counter. + +The attribute count contains the number of times the event has occurred since the last time the counter was zeroed." + +**NOTE – Do we want to allow resets?;;** + +### ATTRIBUTES + +| | | +|-----------------------|----------------------| +| iNAPCounterId | GET, | +| observedEventId | GET SET-BY-CREATE, | +| observedSCFAccessList | GET SET-BY-CREATE, | +| administrativeState | GET-REPLACE, | +| count | GET SET-BY-CREATE;;; | + +**REGISTERED AS** {inSSFManagedObjectClass 33}; + +## 7.34 Service Feature Control + +serviceFeatureControl **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation X.721 : 1992": top; + +### CHARACTERIZED BY + +servicefeatureControl Package **PACKAGE** + +### BEHAVIOUR + +servicefeatureControl Behaviour **BEHAVIOUR** + +**DEFINED AS** "The serviceFeatureControl managed object represents the capability of controlling an IN service. + +The serviceFeatureControlId Attribute is used as the RDN. + +The serviceKey attribute identifies the service to be invoked. + +The administrativeState indicates whether the IN service has been administratively disabled. + +The defaultCharging attribute specifies how charging is to be applied if no instructions are received from the SCF. + +The chargingProfile attribute specifies the type of record to be generated if this is not clear from the context of the call or from the instructions received from the SCF. + +The iNAPASE attribute identifies the INAP ASE to be associated with that service. + +The sCFAccessPointer attribute identifies the sCFAccess to which INAP messages for this service are to be sent. + +The processingInstructions attribute specifies the default values for feature control, e.g. that IN-IN interworking is not allowed. + +The exceptionHandling attribute specifies the actions to be taken by the SSF if invocation of the IN service logic fails.";; + +### ATTRIBUTES + +| | | +|-------------------------|----------------| +| serviceFeatureControlId | GET, | +| serviceKey | GET-REPLACE, | +| administrativeState | GET-REPLACE, | +| defaultCharging | GET-REPLACE, | +| chargingProfile | GET-REPLACE, | +| iNAPASE | GET-REPLACE, | +| sCFAccessPointer | GET-REPLACE, | +| processingInstructions | GET-REPLACE, | +| routeListMapping | GET-REPLACE, | +| exceptionHandling | GET-REPLACE;;; | + +**REGISTERED AS** {inSSFManagedObjectClass 34}; + +## 7.35 SCF Access + +scfAccess **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation X.721 : 1992": top; + +**CHARACTERIZED BY** + +scfAccessPackage **PACKAGE** + +**BEHAVIOUR** + +scfAccessBehaviour **BEHAVIOUR** + +DEFINED AS "The scfAccess managed object identifies the SCF access to be used for particular services and is used as a single point of reference for data items used for IN service control. + +The scfAccessId Attribute is used as the RDN.";; + +**ATTRIBUTES** + +scfAccessId GET;;; + +**REGISTERED AS** {inSSFManagedObjectClass 35}; + +## 7.36 SCF Access Point Code Based + +scfAccessPointCodeBased **MANAGED OBJECT CLASS** + +**DERIVED FROM** scfAccess; + +**CHARACTERIZED BY** + +scfAccessPointCodeBasedPackage **PACKAGE** + +**BEHAVIOUR** + +scfAccessPointCodeBased Behaviour **BEHAVIOUR** + +DEFINED AS "The scfAccessPointCodeBased managed object identifies the SCF access by means of point codes. + +The dPCPointer attribute points to an object of class mtpSignPoint that identifies the destination point code to be used. + +The oPCPointer attribute points to an object of class mtpSignPoint that identifies the origination point code to be used. + +The sSIDPointer attribute points to an object of class sscpAccessPoint that identifies the subsystem id to be used.";; + +**ATTRIBUTES** + +dPCPointer GET-REPLACE, +oPCPointer GET-REPLACE, +sSIDPointer GET-REPLACE;;; + +**REGISTERED AS** {inSSFManagedObjectClass 36}; + +## 7.37 SCF Global Title Based + +scfAccessGlobalTitleBased      **MANAGED OBJECT CLASS** + +**DERIVED FROM**      scfAccess; + +**CHARACTERIZED BY** + +scfAccessGlobalTitleBasedPackage      **PACKAGE** + +**BEHAVIOUR** + +scfAccessGlobalTitleBased Behaviour BEHAVIOUR + +DEFINED AS "The scfAccessPointCodeBased managed object identifies the SCF access by means of point codes. + +The globalTitleRulePtr attribute points to an object of class gtRule. + +The sCPAddress attribute + +The sSIDPointer attribute points to an object of class sccpAccessPoint that identifies the subsystem id to be used.";; + +**ATTRIBUTES** + +| | | +|--------------------|----------------| +| globalTitleRulePtr | GET-REPLACE, | +| sCPAddress | GET-REPLACE, | +| sSIDPointer | GET-REPLACE;;; | + +**REGISTERED AS** {inSSFManagedObjectClass 37}; + +## 7.38 IP Configuration + +iPConfiguration      **MANAGED OBJECT CLASS** + +**DERIVED FROM**      "Recommendation X.721 : 1992": top; + +**CHARACTERIZED BY** + +iPConfigurationPackage      **PACKAGE** + +**BEHAVIOUR** + +scfAccessGlobalTitleBased Behaviour BEHAVIOUR + +DEFINED AS "The iPConfigurationId managed object specifies the capabilities of an IP and its availability. + +The iPConfigurationId is used in forming the RDN. + +The operationalState attribute specifies whether the IP is enabled. + +The administrativeState specifies whether the IP is locked or unlocked. + +The iPCapabilityList attribute describes the functional capabilities of the IP; e.g. tone generation, speech synthesis, etc.";; + +**ATTRIBUTES** + +| | | +|---------------------------------------------------|----------------| +| iPConfigurationId | GET, | +| "Recommendation X.721 : 1992":administrativeState | GET-REPLACE, | +| "Recommendation X.721 : 1992":operationalState | GET-REPLACE, | +| iPCapabilityList | GET-REPLACE;;; | + +**REGISTERED AS** {inSSFManagedObjectClass 38}; + +## 7.39 Assist Treatment Configuration + +assistTreatmentConfiguration **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation X.721 : 1992": top; + +### **CHARACTERIZED BY** + +assistTreatmentConfigurationPackage **PACKAGE** + +### **BEHAVIOUR** + +assistTreatmentConfigurationBehaviour **BEHAVIOUR** + +DEFINED AS "The assistTreatmentConfiguration managed object the way in which the assisting SSF should determine how to manipulate information to be sent in the assistRequestInstruction (ARI) message and the SCF access to which the ARI is to be sent. + +The assistTreatmentConfigurationId is used in forming the RDN. + +The digitStringToCorrelationIdMapping attribute specifies how to map the received digit string to the correlationId to be used in the ARI message so that the SCF can correlate the ARI with its ETC (establishTemporaryConnection) message. + +The digitStringToScfIdMapping specifies the mapping from the received digitString to the sCFId so that the SSF can identify the SCP with which it has to communicate in order to receive assist instructions. + +The sCFAccessPtr attribute identifies the sCFAccess to be used for communicating with the previously identified SCP.";; + +### **ATTRIBUTES** + +| | | +|-----------------------------------|----------------| +| assistTreatmentConfigurationId | GET, | +| digitStringToCorrelationIdMapping | GET-REPLACE, | +| digitStringToScfIdMapping | GET-REPLACE, | +| sCFAccessPtr | GET-REPLACE;;; | + +**REGISTERED AS** {inSSFManagedObjectClass 39}; + +## 7.40 Ported Number Trigger + +portedNumberTrigger **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation X.721 : 1992": top; + +### **CHARACTERIZED BY** + +portedNumberTriggerPackage **PACKAGE** + +### **BEHAVIOUR** + +portedNumberTriggerBehaviour **BEHAVIOUR** + +DEFINED AS "The portedNumberTrigger managed object specifies the length of the dialled digits string on which the decision to check for a ported number is made.";; + +### **ATTRIBUTES** + +| | | +|-----------------------|--------------------| +| portedNumberTriggerId | GET SET-BY-CREATE, | +| serviceKey | GET SET-REPLACE, | +| dialledDigitLength | GET-REPLACE;;; | + +**REGISTERED AS** {inSSFManagedObjectClass 40}; + +## 7.41 Ported Number List + +portedNumberList **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation X.721 : 1992": top; + +**CHARACTERIZED BY** + +portedNumberListPackage **PACKAGE** + +**BEHAVIOUR** + +portedNumberListBehaviour **BEHAVIOUR** + +DEFINED AS "The portedNumberList managed object specifies the list of dialled digits of the terminating address for which the exchange has to check for additional routing information.";; + +**ATTRIBUTES** + +| | | +|---------------------------|--------------------| +| portedNumberListId | GET SET-BY-CREATE, | +| terminatingDialDigitsList | GET-REPLACE;;; | + +**REGISTERED AS** {inSSFManagedObjectClass 41}; + +## 7.42 INAP Current Data + +iNAPCurrentData **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation Q.822": currentData; + +**CHARACTERIZED BY** + +iNAPCurrentDataPackage **PACKAGE** + +**BEHAVIOUR** + +iNAPCurrentDataBehaviour **BEHAVIOUR** + +DEFINED AS "This object class provides the capability for counting particular events that occur in a given time period in association with the use of INAP. Also, the threshold attribute allows thresholding of the count during the time interval. If the threshold is exceeded, a notification is emitted. Detailed behavioural description is found in the superclass definition. + +The attribute observedEventId specifies the semantics of the events counted by this particular object. + +The attribute observedSCFAccessList identifies the SCF accesses that are being observed by this object. + +The attribute count contains the number of times the event has occurred during the time interval.";; + +**ATTRIBUTES** + +| | | +|-----------------------|--------------------| +| observedEventId | GET SET-BY-CREATE, | +| observedSCFAccessList | GET SET-BY-CREATE, | +| count | GET;;; | + +**REGISTERED AS** {inSSFManagedObjectClass 42}; + +## 7.43 INAP History Data + +iNAPHistoryData **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation Q.822": historyData; + +**CHARACTERIZED BY** + +iNAPHistoryDataPackage **PACKAGE** + +**BEHAVIOUR** + +iNAPHistoryDataBehaviour **BEHAVIOUR** + +DEFINED AS "This object class provides the capability for storing the content of previous iNAPCurrentData. objectsDetailed behavioural description is found in the superclass definition. + +The attribute observedEventId specifies the semantics of the events counted by this particular object. +The attribute observedSCFAccessList identifies the SCF accesses that are being observed by this object. +The attribute count contains the number of times the event has occurred during the time interval." + +### ATTRIBUTES + +| | | +|-----------------------|--------------------| +| observedEventId | GET SET-BY-CREATE, | +| observedSCFAccessList | GET SET-BY-CREATE, | +| count | GET;;; | + +**REGISTERED AS** {inSSFManagedObjectClass 43}; + +## 7.44 Default Charging + +defaultCharging **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation X.721": top; + +### CHARACTERIZED BY + +defaultChargingPackage **PACKAGE** + +### BEHAVIOUR + +defaultChargingBehaviour **BEHAVIOUR** + +**DEFINED AS** "This object class defines the default action to be taken if no specific charging information is supplied for the IN call. The default action may be service dependent." + +### ATTRIBUTES + +| | | +|-----------------------|--------------------| +| defaultChargingId | GET SET-BY-CREATE, | +| defaultChargingAction | GET-REPLACE;;; | + +**REGISTERED AS** {inSSFManagedObjectClass 44}; + +## 7.45 Exception Handler + +exceptionHandler **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation X.721": top; + +### CHARACTERIZED BY + +exceptionHandlerPackage **PACKAGE** + +### BEHAVIOUR + +exceptionHandlerBehaviour **BEHAVIOUR** + +**DEFINED AS** "This object class defines the action to be taken by the SSF as default treatment when an error occurs in call processing." + +### ATTRIBUTES + +| | | +|--------------------------------------|--------------------| +| exceptionHandlerId | GET SET-BY-CREATE, | +| missingCustomerRecordException | GET-REPLACE, | +| missingParameterException | GET-REPLACE, | +| systemFailureException | GET-REPLACE, | +| taskRefusedException | GET-REPLACE, | +| unexpectedValueException | GET-REPLACE, | +| unexpectedparameterException | GET-REPLACE, | +| unexpectedValueException | GET-REPLACE, | +| unexpectedComponentSequenceException | GET-REPLACE; | + +### NOTIFICATIONS + +callProcessingException;;; + +**REGISTERED AS** {inSSFManagedObjectClass 45}; + +[NOTE – Do we want OA&M alarms generated by this] + +## 7.46 SSF Timer + +sSFTimer **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation X.721": top; + +**CHARACTERIZED BY** + +defaultChargingPackage **PACKAGE** + +**BEHAVIOUR** + +sSFTimerBehaviour **BEHAVIOUR** + +**DEFINED AS** "This object class defines the value of the timer TSSF" + +**ATTRIBUTES** + +sSFTimerId + +timerValue + +GET SET-BY-CREATE, + +GET-REPLACE;;; + +**REGISTERED AS** {inSSFManagedObjectClass 46}; + +## 7.47 SCF Application Entity + +scfApplicationEntity **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation M.3100": software; + +**CHARACTERIZED BY** + +scfApplicationEntityPackage **PACKAGE** + +**BEHAVIOUR** + +scfApplicationEntityBehaviour **BEHAVIOUR** + +**DEFINED AS** "This object class represents the SCF application process.";;; + +**REGISTERED AS** {inSSFManagedObjectClass 47}; + +## 7.48 SSF Application Entity + +ssfApplicationEntity **MANAGED OBJECT CLASS** + +**DERIVED FROM** "Recommendation M.3100": software; + +**CHARACTERIZED BY** + +ssfApplicationEntityPackage **PACKAGE** + +**BEHAVIOUR** + +ssfApplicationEntityBehaviour **BEHAVIOUR** + +**DEFINED AS** "This object class represents the SSF application process.";;; + +**REGISTERED AS** {inSSFManagedObjectClass 48}; + +# 8 Package definitions + +No external conditional packages defined. + +# **9 Attribute definitions** + +## **9.1 bcsmId Attribute** + +bcsmId ATTRIBUTE +WITH ATTRIBUTE SYNTAX NameType; +MATCHES FOR EQUALITY; +BEHAVIOUR +bcsmIdBhvr BEHAVIOUR +DEFINED AS "This attribute is used as the RDN attribute for naming.";; +REGISTERED AS {inSSFattribute 1}; + +## **9.2 tdpId Attribute** + +tdpId ATTRIBUTE +WITH ATTRIBUTE SYNTAX NameType; +MATCHES FOR EQUALITY; +BEHAVIOUR +tdpIdBhvr BEHAVIOUR +DEFINED AS "This attribute is used as the RDN attribute for naming.";; +REGISTERED AS {inSSFattribute 2}; + +## **9.3 tdpMode Attribute** + +tdpMode ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN1Module.TdpMode; +MATCHES FOR EQUALITY; +BEHAVIOUR +tdpModeBhvr BEHAVIOUR +DEFINED AS "This attribute specifies whether the TDP is configured as a request or notification TDP. +NOTE – In some cases only one particular mode may be valid for a TDP. This will be specified in the appropriate subclass.";; +REGISTERED AS {inSSFattribute 3}; + +## **9.4 tdp1Criteria Attribute** + +tdp1Criteria ATTRIBUTE +WITH ATTRIBUTE SYNTAX TDP1Filter; +MATCHES FOR EQUALITY; +BEHAVIOUR +tdp1CriteriaBhvr BEHAVIOUR +DEFINED AS "This attribute specifies criteria that will cause a triggering of an IN service. It is structured syntactically as a filter in order to allow formulation of complex trigger conditions based on the combination of various predicates. The criteria may include calling party number, bearer capability and class of service.";; +REGISTERED AS {inSSFattribute 4}; + +## **9.5 tdp2Criteria Attribute** + +tdp2Criteria ATTRIBUTE +WITH ATTRIBUTE SYNTAX TDP2Filter; +MATCHES FOR EQUALITY; +BEHAVIOUR +tdp2CriteriaBhvr BEHAVIOUR +DEFINED AS "This attribute specifies criteria that will cause a triggering of an IN service. It is structured syntactically as a filter in order to allow formulation of complex trigger conditions based on the combination of various predicates. The criteria may include calledPartyNumber, callingPartyNumber, digitString and stringLength.";; + +REGISTERED AS {inSSFAttribute 5}; + +## 9.6 tdp3Criteria Attribute + +tdp3Criteria ATTRIBUTE + +WITH ATTRIBUTE SYNTAX TDP3Filter; + +MATCHES FOR EQUALITY; + +BEHAVIOUR + +tdp3CriteriaBhvr BEHAVIOUR + +DEFINED AS "This attribute specifies criteria that will cause a triggering of an IN service. It is structured syntactically as a filter in order to allow formulation of complex trigger conditions based on the combination of various predicates. The criteria may include calledPartyNumber, callingPartyNumber, natureOfAddress, digitString, stringLength, facilityInformation and featureActivation.";; + +REGISTERED AS {inSSFAttribute 6}; + +## 9.7 tdp4Criteria Attribute + +tdp4Criteria ATTRIBUTE + +WITH ATTRIBUTE SYNTAX TDP4Filter; + +MATCHES FOR EQUALITY; + +BEHAVIOUR + +tdp4CriteriaBhvr BEHAVIOUR + +DEFINED AS "This attribute specifies criteria that will cause a triggering of an IN service. It is structured syntactically as a filter in order to allow formulation of complex trigger conditions based on the combination of various predicates. The criteria may include cause, callingPartyNumber, and featureActivation.";; + +REGISTERED AS {inSSFAttribute 7}; + +## 9.8 tdp5Criteria Attribute + +tdp5Criteria ATTRIBUTE + +WITH ATTRIBUTE SYNTAX TDP5Filter; + +MATCHES FOR EQUALITY; + +BEHAVIOUR + +tdp5CriteriaBhvr BEHAVIOUR + +DEFINED AS "This attribute specifies criteria that will cause a triggering of an IN service. It is structured syntactically as a filter in order to allow formulation of complex trigger conditions based on the combination of various predicates. The criteria may include cause and featureActivation.";; + +REGISTERED AS {inSSFAttribute 8}; + +## 9.9 tdp6Criteria Attribute + +tdp6Criteria ATTRIBUTE + +WITH ATTRIBUTE SYNTAX TDP6Filter; + +MATCHES FOR EQUALITY; + +BEHAVIOUR + +tdp6CriteriaBhvr BEHAVIOUR + +DEFINED AS "This attribute specifies criteria that will cause a triggering of an IN service. It is structured syntactically as a filter in order to allow formulation of complex trigger conditions based on the combination of various predicates. The criteria may include cause and featureActivation.";; + +REGISTERED AS {inSSFAttribute 9}; + +## 9.10 tdp7Criteria Attribute + +tdp7Criteria ATTRIBUTE +WITH ATTRIBUTE SYNTAX TDP7Filter; +MATCHES FOR EQUALITY; +BEHAVIOUR +tdp7CriteriaBhvr BEHAVIOUR +DEFINED AS "This attribute specifies criteria that will cause a triggering of an IN service. It is structured syntactically as a filter in order to allow formulation of complex trigger conditions based on the combination of various predicates. The criteria may include facilityInformation and featureActivation.";; + +REGISTERED AS {inSSFattribute 10}; + +## 9.11 tdp8Criteria Attribute + +tdp8Criteria ATTRIBUTE +WITH ATTRIBUTE SYNTAX TDP8Filter; +MATCHES FOR EQUALITY; +BEHAVIOUR +tdp8CriteriaBhvr BEHAVIOUR +DEFINED AS "This attribute specifies criteria that will cause a triggering of an IN service. It is structured syntactically as a filter in order to allow formulation of complex trigger conditions based on the combination of various predicates. The criteria may include facilityInformation and featureActivation.";; + +REGISTERED AS {inSSFattribute 11}; + +## 9.12 tdp9Criteria Attribute + +tdp9Criteria ATTRIBUTE +WITH ATTRIBUTE SYNTAX TDP9Filter; +MATCHES FOR EQUALITY; +BEHAVIOUR +tdp9CriteriaBhvr BEHAVIOUR +DEFINED AS "This attribute specifies criteria that will cause a triggering of an IN service. It is structured syntactically as a filter in order to allow formulation of complex trigger conditions based on the combination of various predicates. The criteria may include cause and featureActivation.";; + +REGISTERED AS {inSSFattribute 12}; + +## 9.13 tdp10Criteria Attribute + +tdp10Criteria ATTRIBUTE +WITH ATTRIBUTE SYNTAX TDP10Filter; +MATCHES FOR EQUALITY; +BEHAVIOUR +tdp10CriteriaBhvr BEHAVIOUR +DEFINED AS "This attribute specifies criteria that will cause a triggering of an IN service. It is structured syntactically as a filter in order to allow formulation of complex trigger conditions based on the combination of various predicates. The criteria may include cause and featureActivation.";; + +REGISTERED AS {inSSFattribute 13}; + +## 9.14 tdp12Criteria Attribute + +tdp12Criteria ATTRIBUTE +WITH ATTRIBUTE SYNTAX TDP12Filter; +MATCHES FOR EQUALITY; +BEHAVIOUR +tdp12CriteriaBhvr BEHAVIOUR +DEFINED AS "This attribute specifies criteria that will cause a triggering of an IN service. It is structured syntactically as a filter in order to allow formulation of complex trigger conditions based on the combination of various predicates. The criteria may include classOfService and callingPartyNumber.";; +REGISTERED AS {inSSFattribute 14}; + +## 9.15 tdp13Criteria Attribute + +tdp13Criteria ATTRIBUTE +WITH ATTRIBUTE SYNTAX TDP13Filter; +MATCHES FOR EQUALITY; +BEHAVIOUR +tdp13CriteriaBhvr BEHAVIOUR +DEFINED AS "This attribute specifies criteria that will cause a triggering of an IN service. It is structured syntactically as a filter in order to allow formulation of complex trigger conditions based on the combination of various predicates. The criteria may include featureActivation and callingPartyNumber.";; +REGISTERED AS {inSSFattribute 15}; + +## 9.16 tdp14Criteria Attribute + +tdp14Criteria ATTRIBUTE +WITH ATTRIBUTE SYNTAX TDP14Filter; +MATCHES FOR EQUALITY; +BEHAVIOUR +tdp14CriteriaBhvr BEHAVIOUR +DEFINED AS "This attribute specifies criteria that will cause a triggering of an IN service. It is structured syntactically as a filter in order to allow formulation of complex trigger conditions based on the combination of various predicates. The criteria may include featureActivation and callingPartyNumber.";; +REGISTERED AS {inSSFattribute 16}; + +## 9.17 tdp15Criteria Attribute + +tdp15Criteria ATTRIBUTE +WITH ATTRIBUTE SYNTAX TDP15Filter; +MATCHES FOR EQUALITY; +BEHAVIOUR +tdp15CriteriaBhvr BEHAVIOUR +DEFINED AS "This attribute specifies criteria that will cause a triggering of an IN service. It is structured syntactically as a filter in order to allow formulation of complex trigger conditions based on the combination of various predicates. The criteria may include facilityInformation and featureActivation.";; +REGISTERED AS {inSSFattribute 17}; + +## 9.18 tdp16Criteria Attribute + +tdp16Criteria ATTRIBUTE +WITH ATTRIBUTE SYNTAX TDP16Filter; +MATCHES FOR EQUALITY; +BEHAVIOUR +tdp15CriteriaBhvr BEHAVIOUR +DEFINED AS "This attribute specifies criteria that will cause a triggering of an IN service. It is structured syntactically as a filter in order to allow formulation of complex trigger conditions based on the combination of various predicates. The criteria may include facilityInformation and featureActivation.";; +REGISTERED AS {inSSFattribute 18}; + +## 9.19 tdp17Criteria Attribute + +tdp17Criteria ATTRIBUTE +WITH ATTRIBUTE SYNTAX TDP17Filter; +MATCHES FOR EQUALITY; +BEHAVIOUR +tdp17CriteriaBhvr BEHAVIOUR +DEFINED AS "This attribute specifies criteria that will cause a triggering of an IN service. It is structured syntactically as a filter in order to allow formulation of complex trigger conditions based on the combination of various predicates. The criteria may include cause and featureActivation.";; +REGISTERED AS {inSSFattribute 19}; + +## 9.20 tdp18Criteria Attribute + +tdp18Criteria ATTRIBUTE +WITH ATTRIBUTE SYNTAX TDP18Filter; +MATCHES FOR EQUALITY; +BEHAVIOUR +tdp18CriteriaBhvr BEHAVIOUR +DEFINED AS "This attribute specifies criteria that will cause a triggering of an IN service. It is structured syntactically as a filter in order to allow formulation of complex trigger conditions based on the combination of various predicates. The criteria may include cause and featureActivation.";; +REGISTERED AS {inSSFattribute 20}; + +## 9.21 triggerAssociation Attribute + +triggerAssociation ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN.Module.TriggerAssociation; +MATCHES FOR EQUALITY; +BEHAVIOUR +triggerAssociationBhvr BEHAVIOUR +DEFINED AS "This attribute specifies the basis on which the trigger is to be applied.";; +REGISTERED AS {inSSFattribute 21}; + +*Editor's Note:* Should this attribute be set-valued? + +## 9.22 inEscape Attribute + +inEscape ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN.Module.INEscapes; +MATCHES FOR EQUALITY; +BEHAVIOUR +inEscapeBhvr BEHAVIOUR +DEFINED AS "This set valued attribute specifies the call related information on the basis of which escape from IN processing would occur.";; + +REGISTERED AS {inSSFattribute 22}; + +## 9.23 congestionAction Attribute + +congestionAction ATTRIBUTE + +WITH ATTRIBUTE SYNTAX SSFASN.Module.CongestionAction; + +MATCHES FOR EQUALITY; + +BEHAVIOUR + +congestionActionBhvr BEHAVIOUR + +DEFINED AS "This attribute specifies the action to be taken if the SCF cannot be reached or does not respond in time. Valid actions are terminate call, play announcement, play announcement and terminate call.";; + +REGISTERED AS {inSSFattribute 23}; + +## 9.24 serviceKey Attribute + +serviceKey ATTRIBUTE + +WITH ATTRIBUTE SYNTAX SSFASN.Module.ServiceKey; + +MATCHES FOR EQUALITY; + +BEHAVIOUR + +serviceKeyBhvr BEHAVIOUR + +DEFINED AS "This attribute specifies the logical service key for the IN service to be invoked.";; + +REGISTERED AS {inSSFattribute 24}; + +## 9.25 inCallGapId Attribute + +inCallGapId ATTRIBUTE + +WITH ATTRIBUTE SYNTAX SSFASN.Module.NameType; + +MATCHES FOR EQUALITY; + +BEHAVIOUR + +inCallGapIdBhvr BEHAVIOUR + +DEFINED AS "This attribute is used for the RDN of the inCallGap object.";; + +REGISTERED AS {inSSFattribute 25}; + +## 9.26 gapDuration Attribute + +gapDuration ATTRIBUTE + +WITH ATTRIBUTE SYNTAX SSFASN.Module.GapDuration; + +MATCHES FOR EQUALITY; + +BEHAVIOUR + +gapDurationBhvr BEHAVIOUR + +DEFINED AS "This attribute is used to specify the length of time for which gapping is to be applied.";; + +REGISTERED AS {inSSFattribute 26}; + +## 9.27 gapInterval Attribute + +gapInterval ATTRIBUTE + +WITH ATTRIBUTE SYNTAX SSFASN.Module.GapInterval; + +MATCHES FOR EQUALITY; + +BEHAVIOUR + +gapIntervalBhvr BEHAVIOUR + +DEFINED AS "This attribute is used to specify the fraction of calls to be gapped. No gapping when the attribute is zero and gap all calls gapInterval is one.";; + +REGISTERED AS {inSSFattribute 27}; + +## 9.28 gapTreatment Attribute + +gapTreatment ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN.Module.CallTreatment; +MATCHES FOR EQUALITY; +BEHAVIOUR +gapTreatmentBhvr BEHAVIOUR +DEFINED AS "This attribute is used to specify the treatment to be applied to a gapped call. It may specify information to be sent to the calling party, release of the call with a cause value or information to be sent and subsequent release of the call.";; + +REGISTERED AS {inSSFAttribute 28}; + +## 9.29 digitString Attribute + +digitString ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN.Module.DigitString; +MATCHES FOR EQUALITY; +BEHAVIOUR +digitStringBhvr BEHAVIOUR +DEFINED AS "This attribute is used to identify a digit string. In trigger point objects this digit string may be used as criterion or a part of a logical expression for invoking IN service logic.";; + +REGISTERED AS {inSSFAttribute 29}; + +## 9.30 authenticationCode Attribute + +authenticationCode ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN.Module.AuthenticationCode; +MATCHES FOR EQUALITY; +BEHAVIOUR +authenticationCodeBhvr BEHAVIOUR +DEFINED AS "This attribute contains a parameter used in authenticating a user for access to data or services.";; + +REGISTERED AS {inSSFAttribute 30}; + +## 9.31 calledPartyNumberList Attribute + +calledPartyNumberList ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN.Module.CalledPartyNumberList; +MATCHES FOR EQUALITY SET-COMPARISON SET-INTERSECTION; +BEHAVIOUR +calledPartyNumberListBhvr BEHAVIOUR +DEFINED AS "This attribute is a list of called party directory numbers. The list may be used as screening list.";; + +REGISTERED AS {inSSFAttribute 31}; + +## 9.32 callingPartyNumberList Attribute + +callingPartyNumberList ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN.Module.CallingPartyNumberList; +MATCHES FOR EQUALITY SET-COMPARISON SET-INTERSECTION; +BEHAVIOUR +callingPartyNumberListBhvr BEHAVIOUR +DEFINED AS "This attribute is a list of calling party directory numbers. The list may be used as screening list.";; + +REGISTERED AS {inSSFAttribute 32}; + +## 9.33 version Attribute + +version ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN.Module.Version; +MATCHES FOR EQUALITY ORDERING; +BEHAVIOUR +versionBhvr BEHAVIOUR +DEFINED AS "This attribute specifies the version of an entity. The data-type used to encode the version value must support ordering.";; +REGISTERED AS {inSSFattribute 33}; + +## 9.34 observedEventId Attribute + +observedEventId ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN.Module.ObservedEventId; +MATCHES FOR EQUALITY ORDERING; +BEHAVIOUR +observedEventIdBhvr BEHAVIOUR +DEFINED AS "This attribute identifies the event that is being observed by the object in which it is installed. If this object is a counter, the count will change every time one of these events occurs.";; +REGISTERED AS {inSSFattribute 34}; + +## 9.35 observedSCFAccessList Attribute + +observedSCFAccessList ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN.Module.ObservedSCFAccessList; +MATCHES FOR EQUALITY ORDERING SET-INTERSECTION SET-COMPARISON; +BEHAVIOUR +observedSCFAccessListBhvr BEHAVIOUR +DEFINED AS "This attribute identifies the set of SCF access to which the object is related or with which it is associated.";; +REGISTERED AS {inSSFattribute 35}; + +## 9.36 count Attribute + +count ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN.Module.Count; +MATCHES FOR EQUALITY ORDERING; +BEHAVIOUR +countBhvr BEHAVIOUR +DEFINED AS "This is an integer count of the specified event.";; +REGISTERED AS {inSSFattribute 36}; + +## 9.37 defaultCharging Attribute + +defaultCharging ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN.Module.DefaultCharging; +MATCHES FOR EQUALITY; +BEHAVIOUR +defaultChargingBhvr BEHAVIOUR +DEFINED AS "Services do not necessarily require that charging information be sent from the SCF to the SSF. The SSF, therefore, needs to be able to refer to a choice of default charging options. This attribute specifies the following options: +– indication that same charging level has to be used as that determined by PSTN before (single value); +– indication for setting the call to "free of charge" (single value); + +- indication to reject the call (single value); +- specific charge level (set of values).";; + +REGISTERED AS {inSSFattribute 37}; + +## 9.38 chargingProfile Attribute + +chargingProfile ATTRIBUTE + +WITH ATTRIBUTE SYNTAX SSFASN.Module.ChargingProfile; +MATCHES FOR EQUALITY; +BEHAVIOUR +chargingProfileBhvr BEHAVIOUR + +DEFINED AS "IN triggering may occur before the SSP specific usage metering control function determines the kind of usage metering. In this cases the 'charging profile' of the IN service determines the kind of usage metering recording. This attribute is defined network operator specific.";; + +REGISTERED AS {inSSFattribute 38}; + +## 9.39 iNAPASE Attribute + +iNAPASE ATTRIBUTE + +WITH ATTRIBUTE SYNTAX SSFASN.Module.ObjectInstance; +MATCHES FOR EQUALITY; +BEHAVIOUR +iNAPASEBhvr BEHAVIOUR + +DEFINED AS "Associates an INAP ASE with the object that has this attribute.";; + +REGISTERED AS {inSSFattribute 39}; + +## 9.40 iNEscape Attribute + +iNEscape ATTRIBUTE + +WITH ATTRIBUTE SYNTAX SSFASN.Module.iNEscape; +MATCHES FOR EQUALITY; +BEHAVIOUR +iNEscapeBhvr BEHAVIOUR + +DEFINED AS "This attribute defines a set of conditions that will cause escape from IN call processing and result in normal call processing.";; + +REGISTERED AS {inSSFattribute 40}; + +## 9.41 exceptionHandling Attribute + +exceptionHandling ATTRIBUTE + +WITH ATTRIBUTE SYNTAX SSFASN.Module.ExceptionHandling; +MATCHES FOR EQUALITY; +BEHAVIOUR +exceptionHandlingBhvr BEHAVIOUR + +DEFINED AS "This attributes contains continuation information for the call processing (e.g. intercept treatment, announcements, etc.). Includes pointers to customizable resources.";; + +REGISTERED AS {inSSFattribute 41}; + +## 9.42 sCFAccessPointer Attribute + +sCFAccessPointer ATTRIBUTE + +WITH ATTRIBUTE SYNTAX SSFASN.Module.ObjectInstance; +MATCHES FOR EQUALITY; +BEHAVIOUR +sCFAccessPointerBhvr BEHAVIOUR + +DEFINED AS "This attributes identifies the SCP to which INAP messages for this service are to be sent.";; +REGISTERED AS {inSSFattribute 42}; + +## 9.43 triggerList Attribute + +triggerList ATTRIBUTE +WITH ATTRIBUTE SYNTAX SET OF ObjectInstance; +MATCHES FOR EQUALITY SET-INTERSECTION SET-COMPARISON; +BEHAVIOUR +triggerListBhvr BEHAVIOUR + +DEFINED AS "This attribute associates a set of triggers to the object that has this attribute.";; +REGISTERED AS {inSSFattribute 43}; + +## 9.44 basePriority Attribute + +basePriority ATTRIBUTE +WITH ATTRIBUTE SYNTAX INTEGER; +MATCHES FOR EQUALITY ORDERING; +BEHAVIOUR +basePriorityBhvr BEHAVIOUR + +DEFINED AS "The basePriority attribute allows specification of which triggerList will be active when several would apply simultaneously to a call. The larger number indicates lower priority.";; +REGISTERED AS {inSSFattribute 44}; + +## 9.45 gapCriteria Attribute + +gapCriteria ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN.Module.GapCriteria; +MATCHES FOR EQUALITY ORDERING; +BEHAVIOUR +gapCriteriaBhvr BEHAVIOUR + +DEFINED AS "The gapCriteria attribute allows configuring criteria for the calls to be gapped. Calls may be gapped for particular destinations, particular services or both.";; +REGISTERED AS {inSSFattribute 45}; + +## 9.46 gapDuration Attribute + +gapDuration ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN.Module.GapDuration; +MATCHES FOR EQUALITY ORDERING; +BEHAVIOUR +gapDurationBhvr BEHAVIOUR + +DEFINED AS "The gapDuration attribute specifies the time interval for which gapping is active.";; +REGISTERED AS {inSSFattribute 46}; + +## 9.47 gapInterval Attribute + +gapInterval ATTRIBUTE +WITH ATTRIBUTE SYNTAX INTEGER; +MATCHES FOR EQUALITY ORDERING; +BEHAVIOUR +gapInterval Bhvr BEHAVIOUR + +DEFINED AS "The gapInterval attribute specifies the minimum inter-arrival time between calls that will be passed. The time is specified in milliseconds.";; +REGISTERED AS {inSSFattribute 47}; + +## 9.48 gapTreatment Attribute + +gapTreatment ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN.Module.CallTreatment; +MATCHES FOR EQUALITY ORDERING; +BEHAVIOUR +gapTreatmentBhvr BEHAVIOUR +DEFINED AS "The gapTreatment attribute specifies the treatment to be given to calls that have been gapped.";; +REGISTERED AS {inSSFAttribute 48}; + +## 9.49 controlType Attribute + +controlType ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN.Module.ControlType; +MATCHES FOR EQUALITY ORDERING; +BEHAVIOUR +controlTypeBhvr BEHAVIOUR +DEFINED AS "The controlType attribute indicates how call gapping was activated. Call gapping may be activated by the SCP or the OSF.";; +REGISTERED AS {inSSFAttribute 49}; + +## 9.50 iPCapabilityList Attribute + +iPCapabilityList ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN.Module.ControlType; +MATCHES FOR EQUALITY; +BEHAVIOUR +iPCapabilityListBhvr BEHAVIOUR +DEFINED AS "The iPCapabilityList attribute describes the functional capabilities of the IP, e.g. tone generation, speech synthesis, etc.";; +REGISTERED AS {inSSFAttribute 50}; + +## 9.51 dialledDigitLength + +dialledDigitLength ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN.Module.DialledDigitLength; +MATCHES FOR EQUALITY ORDERING; +BEHAVIOUR +dialledDigitLengthBhvr BEHAVIOUR +DEFINED AS "The dialledDigitLength specifies the number of digits on which the decision to check the portedNumberList is made.";; +REGISTERED AS {inSSFAttribute 51}; + +## 9.52 terminatingDialDigitsList Attribute + +terminatingDialDigitsList ATTRIBUTE +WITH ATTRIBUTE SYNTAX SSFASN.Module.TerminatingDialDigitsList; +MATCHES FOR EQUALITY; +BEHAVIOUR +terminatingDialDigitsListBhvr BEHAVIOUR +DEFINED AS "The terminatingDialDigitsList attribute is a list of entries that specifies the dialled digits for which the exchange needs to obtain instructions on how to route the call due to possible porting of that number. The list consists of digit strings that if matched will cause triggering of an LNP (Local Number Portability) query.";; + +REGISTERED AS {inSSFAttribute 52}; + +## 9.53 defaultChargingAction Attribute + +defaultChargingAction ATTRIBUTE + +WITH ATTRIBUTE SYNTAX SSFASN.Module.DefaultChargingAction; +MATCHES FOR EQUALITY; +BEHAVIOUR +defaultChargingActionBhvr BEHAVIOUR + +DEFINED AS "The defaultChargingAction attribute defines the default action to be taken if no specific charging information is supplied for the IN call. The default action may be service dependent.";; + +REGISTERED AS {inSSFAttribute 53}; + +## 9.54 timerValue Attribute + +timerValue ATTRIBUTE + +WITH ATTRIBUTE SYNTAX SSFASN.Module.TimerValue; +MATCHES FOR EQUALITY ORDERING; +BEHAVIOUR +timerValueBhvr BEHAVIOUR + +DEFINED AS "The timerValue attribute specifies the amount of time that is to elapse after a particular event has occurred prior to the occurrence of another event. The values is specified in milliseconds.";; + +REGISTERED AS {inSSFAttribute 54}; + +## 9.55 missingCustomerRecordException Attribute + +missingCustomerRecordException ATTRIBUTE + +WITH ATTRIBUTE SYNTAX SSFASN.Module.INAPEException; +MATCHES FOR EQUALITY ORDERING; +BEHAVIOUR +missingCustomerRecordExceptionBhvr BEHAVIOUR + +DEFINED AS "The missingCustomerRecordException attribute specifies the action to be taken if the customer record for a particular call cannot be located.";; + +REGISTERED AS {inSSFAttribute 55}; + +NOTE – Similar templates will be provided in the final edit for the following exceptions: missingParameterException, systemFailureException, taskRefusedException, unexpectedValueException, unexpectedparameterException, unexpectedValueException, unexpectedComponentSequenceException. + +# 10 Name Bindings + +## 10.1 TDP to BCSM + +tdp-bcsm      **NAME BINDING** +**SUBORDINATE OBJECT CLASS**              tdp      **AND SUBCLASSES;** +**NAMED BY** +**SUPERIOR OBJECT CLASS** bcsm **AND SUBCLASSES ;** +WITH ATTRIBUTE              tdpId; +CREATE WITH-REFERENCE-OBJECT , +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE +ONLY-IF-NO-CONTAINED-OBJECTS; + +REGISTERED AS {inSSFNameBinding 1}; + +## 10.2 Originating Trunk Trigger Base to Configured End Point Group + +``` +o_trunkTriggerBase-cepsg NAME BINDING + SUBORDINATE OBJECT CLASS o_trunkTriggerBase AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS cepsg AND SUBCLASSES ; + WITH ATTRIBUTE triggerBaseId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + ONLY-IF-NO-CONTAINED-OBJECTS; + +REGISTERED AS {inSSFNameBinding 2}; +``` + +## 10.3 Terminating Trunk Trigger Base to Configured End Point Group + +``` +t_trunkTriggerBase-cepsg NAME BINDING + SUBORDINATE OBJECT CLASS t_trunkTriggerBase AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS cepsg AND SUBCLASSES ; + WITH ATTRIBUTE triggerBaseId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + ONLY-IF-NO-CONTAINED-OBJECTS; + +REGISTERED AS {inSSFNameBinding 3}; +``` + +## 10.4 Originating Line Trigger Base to Customer Profile + +``` +o_lineTriggerBase-customerProfile NAME BINDING + SUBORDINATE OBJECT CLASS o_lineTriggerBase AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation Q.824.1": customerProfile + AND SUBCLASSES ; + WITH ATTRIBUTE triggerBaseId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + ONLY-IF-NO-CONTAINED-OBJECTS; + +REGISTERED AS {inSSFNameBinding 4}; +``` + +## 10.5 Terminating Line Trigger Base to Customer Profile + +``` +t_trunkTriggerBase-customerProfile NAME BINDING + SUBORDINATE OBJECT CLASS t_lineTriggerBase AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation Q.824.1": customerProfile + AND SUBCLASSES ; + WITH ATTRIBUTE triggerBaseId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE +``` + +ONLY-IF-NO-CONTAINED-OBJECTS; + +REGISTERED AS {inSSFNameBinding 5}; + +## 10.6 SCF Access to Managed Element + +sCFAccess-managedElement      **NAME BINDING** +    **SUBORDINATE OBJECT CLASS**      sCFAccess      **AND SUBCLASSES;** +    **NAMED BY** +    **SUPERIOR OBJECT CLASS** "Recommendation M.3100": managedElement +        **AND SUBCLASSES ;** +    WITH ATTRIBUTE      sCFAccessId; +    CREATE +    WITH-REFERENCE-OBJECT , +    WITH-AUTOMATIC-INSTANCE-NAMING; +    DELETE +    ONLY-IF-NO-CONTAINED-OBJECTS; + +REGISTERED AS {inSSFNameBinding 6}; + +## 10.7 BCSM to Managed Element + +bcsm-managedElement      **NAME BINDING** +    **SUBORDINATE OBJECT CLASS**      bcsm      **AND SUBCLASSES;** +    **NAMED BY** +    **SUPERIOR OBJECT CLASS** "Recommendation M.3100": managedElement +        **AND SUBCLASSES ;** +    WITH ATTRIBUTE      sCFAccessId; +    CREATE +    WITH-REFERENCE-OBJECT , +    WITH-AUTOMATIC-INSTANCE-NAMING; +    DELETE +    ONLY-IF-NO-CONTAINED-OBJECTS; + +REGISTERED AS {inSSFNameBinding 7}; + +## 10.8 IN Call Gap to SSF-SCF Application Entity + +inCallGap-ssfScfAE      **NAME BINDING** +    **SUBORDINATE OBJECT CLASS**      inCallGap      **AND SUBCLASSES;** +    **NAMED BY** +    **SUPERIOR OBJECT CLASS** ssfScfAE +        **AND SUBCLASSES ;** +    WITH ATTRIBUTE      inCallGapId; +    CREATE +    WITH-REFERENCE-OBJECT , +    WITH-AUTOMATIC-INSTANCE-NAMING; +    DELETE +    ONLY-IF-NO-CONTAINED-OBJECTS; + +REGISTERED AS {inSSFNameBinding 8}; + +## 10.9 Service Filtering to Service Feature Control + +serviceFiltering-serviceFeatureControl      **NAME BINDING** +    **SUBORDINATE OBJECT CLASS**      serviceFiltering      **AND SUBCLASSES;** +    **NAMED BY** + +**SUPERIOR OBJECT CLASS** serviceFeatureControl **AND SUBCLASSES** ; + WITH ATTRIBUTE serviceFilteringId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + ONLY-IF-NO-CONTAINED-OBJECTS; + +REGISTERED AS {inSSFNameBinding 9}; + +## 10.10 IP Configuration to Managed Element + +ipConfiguration-managedElement **NAME BINDING** +**SUBORDINATE OBJECT CLASS** ipConfiguration **AND SUBCLASSES**; +**NAMED BY** +**SUPERIOR OBJECT CLASS** "Recommendation M.3100": managedElement +**AND SUBCLASSES** ; + WITH ATTRIBUTE ipConfigurationId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + ONLY-IF-NO-CONTAINED-OBJECTS; + +REGISTERED AS {inSSFNameBinding 10}; + +## 10.11 Dialed Digit Length to Managed Element + +dialledDigitLength-managedElement **NAME BINDING** +**SUBORDINATE OBJECT CLASS** dialledDigitLength **AND SUBCLASSES**; +**NAMED BY** +**SUPERIOR OBJECT CLASS** "Recommendation M.3100": managedElement +**AND SUBCLASSES** ; + WITH ATTRIBUTE portedNumberTriggerId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + ONLY-IF-NO-CONTAINED-OBJECTS; + +REGISTERED AS {inSSFNameBinding 11}; + +## 10.12 Terminating Dialed Digit List to Dialed Digit Length + +terminatingDialedDigitList-dialledDigitLength **NAME BINDING** +**SUBORDINATE OBJECT CLASS** terminatingDialedDigitList **AND SUBCLASSES**; +**NAMED BY** +**SUPERIOR OBJECT CLASS** dialledDigitLength +**AND SUBCLASSES** ; + WITH ATTRIBUTE portedNumberListId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + ONLY-IF-NO-CONTAINED-OBJECTS; + +REGISTERED AS {inSSFNameBinding 12}; + +## 10.13 inAuthorization to tdp + +``` +inAuthorization-tdp NAME BINDING + SUBORDINATE OBJECT CLASS inAuthorization AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS tdp + AND SUBCLASSES ; + WITH ATTRIBUTE inAuthorizationId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + ONLY-IF-NO-CONTAINED-OBJECTS; +``` + +REGISTERED AS {inSSFNameBinding 13}; + +## 10.14 Initiate Call Default Information to Managed Element + +``` +initiateCallDefaultInformation-managedElement NAME BINDING + SUBORDINATE OBJECT CLASS initiateCallDefaultInformation AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation M.3100": managedElement + AND SUBCLASSES ; + WITH ATTRIBUTE initiateCallDefaultInformationId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + ONLY-IF-NO-CONTAINED-OBJECTS; +``` + +REGISTERED AS {inSSFNameBinding 14}; + +## 10.15 Assist Treatment Configuration to Managed Element + +``` +assistTreatmentConfiguration-managedElement NAME BINDING + SUBORDINATE OBJECT CLASS assistTreatmentConfiguration AND + SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation M.3100": managedElement + AND SUBCLASSES ; + WITH ATTRIBUTE assistTreatmentConfigurationId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + ONLY-IF-NO-CONTAINED-OBJECTS; +``` + +REGISTERED AS {inSSFNameBinding 15}; + +## 10.16 Ported Number Trigger to Managed Element + +``` +portedNumberTrigger-managedElement NAME BINDING + SUBORDINATE OBJECT CLASS portedNumberTrigger AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS "Recommendation M.3100": managedElement + AND SUBCLASSES ; + WITH ATTRIBUTE portedNumberTriggerId; + CREATE + WITH-REFERENCE-OBJECT , +``` + +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE +ONLY-IF-NO-CONTAINED-OBJECTS; + +REGISTERED AS {inSSFNameBinding 16}; + +## 10.17 Ported Number List to Managed Element + +portedNumberList-managedElement      **NAME BINDING** +    **SUBORDINATE OBJECT CLASS**      portedNumberList      **AND SUBCLASSES;** +    **NAMED BY** +    **SUPERIOR OBJECT CLASS** portedNumberTrigger +        **AND SUBCLASSES ;** +    WITH ATTRIBUTE      portedNumberListId; +    CREATE +    WITH-REFERENCE-OBJECT , +    WITH-AUTOMATIC-INSTANCE-NAMING; +    DELETE +    ONLY-IF-NO-CONTAINED-OBJECTS; + +REGISTERED AS {inSSFNameBinding 17}; + +## 10.18 Default Charging to Service Feature Control + +defaultCharging-serviceFeatureControl      **NAME BINDING** +    **SUBORDINATE OBJECT CLASS**      defaultCharging      **AND SUBCLASSES;** +    **NAMED BY** +    **SUPERIOR OBJECT CLASS** serviceFeatureControl +        **AND SUBCLASSES ;** +    WITH ATTRIBUTE      defaultChargingId; +    CREATE +    WITH-REFERENCE-OBJECT , +    WITH-AUTOMATIC-INSTANCE-NAMING; +    DELETE +    ONLY-IF-NO-CONTAINED-OBJECTS; + +REGISTERED AS {inSSFNameBinding 18}; + +## 10.19 Exception Handler to Service Feature Control + +exceptionHandler-serviceFeatureControl      **NAME BINDING** +    **SUBORDINATE OBJECT CLASS**      exceptionHandler **AND SUBCLASSES;** +    **NAMED BY** +    **SUPERIOR OBJECT CLASS** serviceFeatureControl +        **AND SUBCLASSES ;** +    WITH ATTRIBUTE      exceptionHandlerId; +    CREATE +    WITH-REFERENCE-OBJECT , +    WITH-AUTOMATIC-INSTANCE-NAMING; +    DELETE +    ONLY-IF-NO-CONTAINED-OBJECTS; + +REGISTERED AS {inSSFNameBinding 19}; + +## 10.20 SSF Timer to SCF Access + +sSFTimer-sCFAccess      **NAME BINDING** +    **SUBORDINATE OBJECT CLASS**      sSFTimer      **AND SUBCLASSES;** + +**NAMED BY** +**SUPERIOR OBJECT CLASS** sCFAccess +**AND SUBCLASSES ;** +**WITH ATTRIBUTE** sSFTimerId; +**CREATE** +**WITH-REFERENCE-OBJECT ,** +**WITH-AUTOMATIC-INSTANCE-NAMING;** +**DELETE** +**ONLY-IF-NO-CONTAINED-OBJECTS;** + +REGISTERED AS {inSSFNameBinding 20}; + +## **10.21 INAP Counter to SSF Application Entity** + +iNAPCounter-ssfApplicationEntity **NAME BINDING** +**SUBORDINATE OBJECT CLASS** iNAPCounter **AND SUBCLASSES;** +**NAMED BY** +**SUPERIOR OBJECT CLASS** ssfApplicationEntity +**AND SUBCLASSES ;** +**WITH ATTRIBUTE** iNAPCounterId; +**CREATE** +**WITH-REFERENCE-OBJECT ,** +**WITH-AUTOMATIC-INSTANCE-NAMING;** +**DELETE** +**ONLY-IF-NO-CONTAINED-OBJECTS;** + +REGISTERED AS {inSSFNameBinding 21}; + +## **10.22 INAP Current Data to SSF Application Entity** + +iNAPCurrentData-ssfApplicationEntity **NAME BINDING** +**SUBORDINATE OBJECT CLASS** iNAPCurrentData **AND SUBCLASSES;** +**NAMED BY** +**SUPERIOR OBJECT CLASS** ssfApplicationEntity +**AND SUBCLASSES ;** +**WITH ATTRIBUTE** "ITU-T Recommendation Q.822":currentDataId; +**CREATE** +**WITH-REFERENCE-OBJECT ,** +**WITH-AUTOMATIC-INSTANCE-NAMING;** +**DELETE** +**ONLY-IF-NO-CONTAINED-OBJECTS;** + +REGISTERED AS {inSSFNameBinding 22}; + +## **10.23 INAP History Data to SSF Application Entity** + +iNAPHistoryData-ssfApplicationEntity **NAME BINDING** +**SUBORDINATE OBJECT CLASS** iNAPHistoryData **AND SUBCLASSES;** +**NAMED BY** +**SUPERIOR OBJECT CLASS** ssfApplicationEntity +**AND SUBCLASSES ;** +**WITH ATTRIBUTE** "ITU-T Recommendation Q.822":HistoryDataId; +**CREATE** +**WITH-REFERENCE-OBJECT ,** +**WITH-AUTOMATIC-INSTANCE-NAMING;** +**DELETE** +**ONLY-IF-NO-CONTAINED-OBJECTS;** + +REGISTERED AS {inSSFNameBinding 23}; + +## 10.24 Assist Treatment Configuration to SSF Application Entity + +``` +assistTreatmentConfiguration-ssfApplicationEntity NAME BINDING + SUBORDINATE OBJECT CLASS assistTreatmentConfiguration AND + SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS ssfApplicationEntity + AND SUBCLASSES ; + WITH ATTRIBUTE assistTreatmentConfigurationId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + ONLY-IF-NO-CONTAINED-OBJECTS; +``` + +REGISTERED AS {inSSFNameBinding 24}; + +## 10.25 Service Feature Control to SSF Application Entity + +``` +serviceFeatureControl-ssfApplicationEntity NAME BINDING + SUBORDINATE OBJECT CLASS serviceFeatureControl AND SUBCLASSES; + NAMED BY + SUPERIOR OBJECT CLASS ssfApplicationEntity + AND SUBCLASSES ; + WITH ATTRIBUTE serviceFeatureControlId; + CREATE + WITH-REFERENCE-OBJECT , + WITH-AUTOMATIC-INSTANCE-NAMING; + DELETE + ONLY-IF-NO-CONTAINED-OBJECTS; +``` + +REGISTERED AS {inSSFNameBinding 25}; + +# 11 ASN.1 Module + +ASN1DefinedTypesModule { itu-t(0) recommendation(0) q(17) inmod(1831) informationModel(0) asn1Modules(2) asn1DefinedTypesModule(0)} + +DEFINITION IMPLICIT TAGS ::= + +BEGIN + +-- *EXPORTS everything* + +IMPORTS + +ObjectClass, ObjectInstance, Attribute FROM CMIP-1 { joint-iso-ccitt ms (9) cmip (1) modules (0) protocol (3) } + +--- *see X.711* + +AdministrativeState, OperationalState, Management Extension FROM Attribute-ASN1Module { joint-iso-ccitt ms(9) smi (3) part2 (2) asn1Module(1) 1} + +--- *see X.721* + +BillingCharacteristics, CallTreatment, DefaultCharging, FilteredCallTreatment, FilteringCharacteristics, FilteringCriteria, FilteringTimeOut, GapTreatment, GapInterval, GapDuration, GapCriteria, InbandInfo, InformationToSend, Integer4, MessageID + +FROM IN-CS-1-Operations {ccitt recommendations q 1218 modules(0) cs-1-operations(0) version1(0)} + +--- *see Q.1218* + +``` + +-- OBJECT IDENTIFIERS +managedObjectClass OBJECT IDENTIFIER ::= {informationModel managedObjectClass(3)} +package OBJECT IDENTIFIER ::= {informationModel package(4)} +nameBinding OBJECT IDENTIFIER ::= {informationModel nameBinding(6)} +attribute OBJECT IDENTIFIER ::= {informationModel attribute(7)} +action OBJECT IDENTIFIER ::= {informationModel action(9)} +notification OBJECT IDENTIFIER ::= {informationModel notification(10)} +behaviour OBJECT IDENTIFIER ::= {informationModel behaviour(11)} +notification OBJECT IDENTIFIER ::= {informationModel notification(10)} + +``` + +``` + +-- ASN.1 Types + +``` + +``` + +AuthenticationCode ::= OCTET STRING + +``` + +``` + +BearerCapability ::= CHOICE { + bearerCap [0] OCTET STRING, + tmr [1] OCTET STRING} + +``` + +``` + +-- bearerCap is encoded according to Q.763 or Q.931 and +-- tmr (transmission medium requirement parameter) is encoded according to ITU-T Q.763 + +``` + +``` + +CalledPartyNumber ::= OCTET STRING -- Encoded according to ITU-T Q.763 + +``` + +``` + +CalledPartyNumberList ::= SET OF CalledPartyNumber + +``` + +``` + +CallingPartyNumber ::= OCTET STRING -- Encoded according to ITU-T Q.763 + +``` + +``` + +CallingPartyNumberList ::= SET OF CallingPartyNumber + +``` + +``` + +Cause ::= OCTET STRING + +``` + +``` + +-- Cause values encoded according to ITU-T Q.763. +-- Cause and Location values encoded according to ITU-T Q.850. + +``` + +``` + +ChargeProfile ::= OCTET STRING -- Operator Specific + +``` + +``` + +CongestionAction ::= ENUMERATED { + terminateCall (0), + playAnnouncement (1), + playAnnouncementAndTerminate (2)} + +``` + +``` + +ControlType ::= ENUMERATED { + sCPInitiated (0), + oSInitiated (1) } + +``` + +``` + +Count ::= INTEGER + +``` + +``` + +DialledDigitLength ::= INTEGER -- Specifies the length of a dialled digit string + +``` + +``` + +DigitString ::= OCTET STRING -- Encoded in accordance with ITU-T Q.763 + +``` + +``` + +DefaultChargingAction ::= CHOICE { + specificAction [1]ENUMERATED { + continueWithNormalCharging (0), + freeCall (1), + releaseCall (2)} + tariffReference [2]NameType } + +``` + +``` + +DisplayInformation ::= IA5String (SIZE (minDisplayInformationLength ..maxDisplayInformationLength)) + +``` + + + +| | | | +|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | classOfService
cause
digitString
facilityInformation
featureActivation
natureOfAddress
stringLength | [3] ClassOfService,
[4] Cause,
[5] DigitString,
[6] FacilityInformation,
[7] FeatureActivation,
[8] NatureOfAddress,
[9] StringLength } | +| Tdp1Criteria ::= CHOICE { | callingPartyNumber
calledPartyNumber
classOfService | [1] CallingPartyNumber,
[2] CalledPartyNumber,
[3] ClassOfService} | +| Tdp2Criteria ::= CHOICE { | callingPartyNumber
calledPartyNumber
digitString
stringLength | [1] CallingPartyNumber,
[2] CalledPartyNumber,
[5] DigitString,
[9] StringLength } | +| Tdp3Criteria ::= CHOICE { | callingPartyNumber
calledPartyNumber
digitString
facilityInformation
featureActivation
natureOfAddress
stringLength | [1] CallingPartyNumber,
[2] CalledPartyNumber,
[5] DigitString,
[6] FacilityInformation,
[7] FeatureActivation,
[8] NatureOfAddress,
[9] StringLength } | +| Tdp4Criteria ::= CHOICE { | callingPartyNumber
cause
featureActivation | [1] CallingPartyNumber,
[4] Cause,
[7] FeatureActivation} | +| Tdp5Criteria ::= CHOICE { | cause
featureActivation | [4] Cause,
[7] FeatureActivation} | +| Tdp6Criteria ::= CHOICE { | cause
featureActivation | [4] Cause,
[7] FeatureActivation} | +| Tdp7Criteria ::= CHOICE { | facilityInformation
featureActivation | [6] FacilityInformation,
[7] FeatureActivation} | +| Tdp8Criteria ::= CHOICE { | facilityInformation
featureActivation | [6] FacilityInformation,
[7] FeatureActivation} | +| Tdp9Criteria ::= CHOICE { | cause
featureActivation | [4] Cause,
[7] FeatureActivation} | +| Tdp10Criteria ::= CHOICE { | cause
featureActivation | [4] Cause,
[7] FeatureActivation} | +| Tdp11Criteria ::= CHOICE { | cause
featureActivation | [4] Cause,
[7] FeatureActivation} | +| Tdp12Criteria ::= CHOICE { | callingPartyNumber
classOfService | [1] CallingPartyNumber,
[3] ClassOfService} | +| Tdp13Criteria ::= CHOICE { | callingPartyNumber
cause
featureActivation | [1] CallingPartyNumber,
[4] Cause,
[7] FeatureActivation} | +| Tdp14Criteria ::= CHOICE { | callingPartyNumber
cause
featureActivation | [1] CallingPartyNumber,
[4] Cause,
[7] FeatureActivation} | + +``` + +Tdp15Criteria ::= CHOICE { + facilityInformation [6] FacilityInformation, + featureActivation [7] FeatureActivation} + +Tdp16Criteria ::= CHOICE { + facilityInformation [6] FacilityInformation, + featureActivation [7] FeatureActivation} + +Tdp17Criteria ::= CHOICE { + cause [4] Cause, + featureActivation [7] FeatureActivation} + +Tdp18Criteria ::= CHOICE { + cause [4] Cause, + featureActivation [7] FeatureActivation} + +TDP1Filter ::= CMISFilter -- restricted to using TDP1Criteria +TDP2Filter ::= CMISFilter -- restricted to using TDP2Criteria +TDP3Filter ::= CMISFilter -- restricted to using TDP3Criteria +TDP4Filter ::= CMISFilter -- restricted to using TDP4Criteria +TDP5Filter ::= CMISFilter -- restricted to using TDP5Criteria +TDP6Filter ::= CMISFilter -- restricted to using TDP6Criteria +TDP7Filter ::= CMISFilter -- restricted to using TDP7Criteria +TDP8Filter ::= CMISFilter -- restricted to using TDP8Criteria +TDP9Filter ::= CMISFilter -- restricted to using TDP9Criteria +TDP10Filter ::= CMISFilter -- restricted to using TDP10Criteria +TDP11Filter ::= CMISFilter -- restricted to using TDP11Criteria +TDP12Filter ::= CMISFilter -- restricted to using TDP12Criteria +TDP13Filter ::= CMISFilter -- restricted to using TDP13Criteria +TDP14Filter ::= CMISFilter -- restricted to using TDP14Criteria +TDP15Filter ::= CMISFilter -- restricted to using TDP15Criteria +TDP16Filter ::= CMISFilter -- restricted to using TDP16Criteria +TDP17Filter ::= CMISFilter -- restricted to using TDP17Criteria +TDP18Filter ::= CMISFilter -- restricted to using TDP18Criteria + +TdpMode ::= ENUMERATED { + notification (1), + request (2) } + +TimerValue ::= INTEGER -- time specified in milliseconds + +Tone ::= SEQUENCE { + toneID [0] Integer4, + duration [1] Integer4 OPTIONAL +} +-- The duration specifies the length of the tone in seconds; value 0 indicates infinite duration. + +TerminatingDialledDigitList ::= SEQUENCE OF DigitString + +``` + +TriggerAssociation ::= SET OF ObjectInstance +Version ::= GraphicString + +END -- end of ASN1 DefinedTypesModule + +# APPENDIX I + +## Productions Imported From Q.1218 + +BillingChargingCharacteristics ::= OCTET STRING + +CallTreatment ::= CHOICE { +    informationToSend [0] InformationToSend, +    releaseCause [1] Cause, +    both [2] SEQUENCE { +        informationToSend [0] InformationToSend, +        releaseCause [1] Cause +    } +} + +-- The default value for Cause is the same as in ISUP. + +DefaultCharging ::= CHOICE { +    pSTNChargingLevel [0] BOOLEAN, +    freeOfCharge [1] BOOLEAN, +    callReject [2] BOOLEAN, +    inChargeLevels [3] SET OF OCTET STRING -- Operator Specific + +FilteredCallTreatment ::= SEQUENCE { +    sFBillingChargingCharacteristics [0] SFBillingChargingCharacteristics, +    informationToSend [1] InformationToSend OPTIONAL, +    maximumNumberOfCounters [2] MaximumNumberOfCounters OPTIONAL, +    releaseCause [3] Cause OPTIONAL +} + +-- If releaseCause is not present, the default value is the same as the ISUP cause value decimal 31. + +-- If informationToSend is present, the call will be released after the end of the announcement with the +-- indicated or default releaseCause. If maximumNumberOfCounters is not present, ServiceFilteringResponse +-- will be sent with CountersValue ::= SEQUENCE SIZE (0) OF CounterAndValue + +FilteringCharacteristics ::= CHOICE { +    interval [0] INTEGER (-1..32000), +    numberOfCalls [1] Integer4 +} + +-- Indicates the severity of the filtering and the point in time when the ServiceFilteringResponse is to be +-- sent. If = interval, every interval of time the next call leads to an InitialDP and a +-- ServiceFilteringResponse is sent to the SCF. The interval is specified in seconds. If = NumberOfCalls, +-- every N calls the Nth call leads to an InitialDP and a ServiceFilteringResponse is sent to the SCF. If +-- ActivateServiceFiltering implies several counters (filtering on several dialled numbers), the +-- numberOfCalls would include calls to all the dialled numbers. + +FilteringCriteria ::= CHOICE { +    serviceKey [2] ServiceKey, +    addressAndService [30] SEQUENCE { +        calledAddressValue [0] Digits, +        serviceKey [1] ServiceKey, +        callingAddressValue [2] Digits OPTIONAL, +    } + +``` + + locationNumber [3] LocationNumber OPTIONAL + } +} +-- In case calledAddressValue is specified, the numbers to be filtered are from calledAddressValue up to +-- and including calledAddressValue +maximumNumberOfCounters-1. The last two digits of calledAddressValue +-- cannot exceed 100-maximumNumberOfCounters. +``` + +``` + +FilteringTimeOut ::= CHOICE { + Duration [0] Duration, + StopTime [1] DateAndTime +} +-- Indicates the maximum duration of the filtering. When the timer expires, a ServiceFilteringResponse is +-- sent to the SCF. +``` + +``` + +GapCriteria ::= CHOICE { + calledAddressValue [0] Digits, + gapOnService [2] GapOnService, + calledAddressAndService [29] SEQUENCE { + calledAddressValue [0] Digits, + serviceKey [1] ServiceKey + } + + callingAddressAndService [30] SEQUENCE { + callingAddressValue [0] Digits, + serviceKey [1] ServiceKey, + locationNumber [2] LocationNumber OPTIONAL + } +} +``` + +*-- Both calledAddressValue and callingAddressValue can be incomplete numbers, in the sense that a limited +-- amount of digits can be given. For the handling of numbers starting with the same digit string refer to +-- the detailed procedure of the CallGap operation in Clause 9.* + +``` + +InbandInfo ::= SEQUENCE { + messageID [0] MessageID, + numberOfRepetitions [1] INTEGER (1..127) OPTIONAL, + duration [2] INTEGER (0..32767) OPTIONAL, + interval [3] INTEGER (0..32767) OPTIONAL +} +-- interval is the time in seconds between each repeated announcement. Duration is the total amount of time +-- in seconds, including repetitions and intervals. The end of announcement is either the end of duration +-- or numberOfRepetitions, whatever comes first. Duration with value 0 indicates infinite duration. +``` + +``` + +InformationToSend ::= CHOICE { + inbandinfo [0] InbandInfo, + tone [1] Tone, + displayInformation [2] DisplayInformation} +``` + +``` + +Integer4 ::= INTEGER (0..2147483647) +``` + +``` + +MessageID ::= CHOICE { + elementaryMessageID [0] Integer4, + text [1] SEQUENCE { + messageContent [0] IA5String (SIZE(minMessageContentLength .. + maxMessageContentLength)), + attributes [1] OCTET STRING (SIZE (minAttributesLength .. + maxAttributesLength)) OPTIONAL + }, + elementaryMessageIDs [29] SEQUENCE SIZE (1..numOfMessageIDs) OF Integer4, + variableMessage [30] SEQUENCE { + elementaryMessageID [0] Integer4, + variableParts [1] SEQUENCE SIZE(1..5) OF VariablePart + } +} + +END + +``` + + + + + +# 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/Q/T-REC-Q.84.2-199510-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cef5eb4611113d7c5b634363fe18cee218cb1764 --- /dev/null +++ b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f57064fcb55ea53607f19cac2e208f6c38d46cc654d98131785a6372fb2a438 +size 55123 diff --git a/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c128762c9d28d8368b771a7c198387aefa27375 --- /dev/null +++ b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8dfe802b4b4fb878d25dd0462b754daa24134bc782ec37f032d5c1286226d8b0 +size 161966 diff --git a/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43b37456a3d0a9d1386723de2ec11adeefaeec4d --- /dev/null +++ b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c61586c8dfe924a9c4465f316915130f2c736af58cef5359d090f82852e94044 +size 25436 diff --git a/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53e518f5ad27ad8f8727b0fc7bdb1b406536293a --- /dev/null +++ b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:046a5a653bb27822cb78abe81e1e8a317a1d3cfd0a47be1d7f15bf3fcf24dd1f +size 114931 diff --git a/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c9103a04f0b280aefac58dd7409d41be53ebff7 --- /dev/null +++ b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c8fa872f062e3f1d54cb1f6a44a41b6bd5fb56442c9b7ba43bb73e539074498 +size 60144 diff --git a/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/a738993919a50143787084ee7ce6e2f2_img.jpg b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/a738993919a50143787084ee7ce6e2f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24856b0e793c36b765972147a97e5ec9e7f2fd5d --- /dev/null +++ b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/a738993919a50143787084ee7ce6e2f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c02a387657ae309adc06df65cfa9020fd696f68ea761b08e7db2392cc0fac6d6 +size 32965 diff --git a/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0e337280512835035b2e9fe10f799351b80377d --- /dev/null +++ b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f20480a6f5e5d73c89de08a3e0fda8c55b61fa6e5708f7e4fa0f5f007f3c7485 +size 207897 diff --git a/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3243ac1dd98f3e2d30e76a24732fc92a871451ff --- /dev/null +++ b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:324d061f064210f712d99a9601cb93b52e33beb5ba0b84bc5afc03a545ae1c03 +size 51170 diff --git a/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f816544f23c6223498d7640f036c369d97d567ea --- /dev/null +++ b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cab578c9f73508b788495bed5a47f8127d00122078165dc106296db4e55f5d0 +size 121055 diff --git a/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79b09066f574a9fb11198bf6676c4b2b7acb458e --- /dev/null +++ b/marked/Q/T-REC-Q.84.2-199510-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:548d6ad649685bc13a95a27d703f9bc4f0498545d5efc44d62b9b5b6cc36bc9e +size 106821 diff --git a/marked/Q/T-REC-Q.85.1-199202-I_PDF-E/raw.md b/marked/Q/T-REC-Q.85.1-199202-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c2404911f5d7e68788a2e0edb95b0eaf50c82267 --- /dev/null +++ b/marked/Q/T-REC-Q.85.1-199202-I_PDF-E/raw.md @@ -0,0 +1,2370 @@ + + +![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 + +# CCITT + +## Q.85 + +THE INTERNATIONAL +TELEGRAPH AND TELEPHONE +CONSULTATIVE COMMITTEE + +# **FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN** --- + +## **STAGE 2 DESCRIPTION FOR COMMUNITY OF INTEREST SUPPLEMENTARY SERVICES** + +**SECTION 1 – CLOSED USER GROUP (CUG)** + +**SECTION 3 – MULTI-LEVEL PRECEDENCE AND +PREEMPTION (MLPP) (rev.1)** + +**Modifications and addenda to: +Recommendation Q.85** + +--- + +![CCITT logo: A stylized globe with the letters CCITT inside a circle.](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +CCITT logo: A stylized globe with the letters CCITT inside a circle. + +Geneva, 1992 + +## 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 Q.85, §§ 1 and 3 was prepared by Study Group XI and was approved under the Resolution No. 2 procedure on the 4th of February 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. + +© ITU 1992 + +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. + +### Recommendation Q.85 + +## STAGE 2 DESCRIPTION FOR COMMUNITY OF INTEREST SUPPLEMENTARY SERVICES + +## 1 Closed User Group (CUG) + +### 1.1 *Scope* + +This Recommendation defines the stage 2 of the integrated services digital network (ISDN) as provided by telecommunications operators for the Closed User Group (CUG) supplementary service. Stage 2 identifies the functional capabilities and the information flows needed to support the service description. The Stage 2 description also identifies user operations not directly associated with a call (see Recommendation I.130 [1]). + +This Recommendation is specified according to the methodology specified in Recommendation Q.65 [2]. + +This Recommendation does not formally describe the relationship between this supplementary service and the basic call, but where possible, this information is included for guidance. + +In addition, this Recommendation does not specify the requirements where the service is provided to the user via a private ISDN. This Recommendation does not specify the requirements for the allocation of defined functional entities within a private ISDN, it does however, define which functional entities may be allocated to a private ISDN. + +This Recommendation does not specify the additional requirements where the service is provided to the user via a telecommunications network that is not an ISDN. + +The CUG supplementary service enables users to form groups to and from which access is restricted. A specific user may be a member of one or more closed user groups. Members of a specific Closed User Group can communicate among themselves but not, in general, with users outside the group. + +The CUG supplementary service is applicable to all telecommunication services. + +This Recommendation is applicable to the stage 3 Recommendations for the ISDN CUG supplementary service. The term "stage 3" is also defined in Recommendation I.130 [1]. + +### 1.2 *References* + +This Recommendation incorporates by dated or undated reference, provisions from other publications. These references are cited at the appropriate places in the text and the publications are listed hereafter. For dated references, subsequent amendments to, or revisions of any of these publications apply to this Recommendation only when incorporated in it by amendment or revision. For undated references the latest edition of the publication referred to applies. + +- [1] CCITT Rec. I.130 — *Methods for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN*, 1988. +- [2] CCITT Rec. Q.65 — *Stage 2 of the method for the characterization of services supported by an ISDN*, 1988. +- [3] CCITT Rec. I.112 — *Vocabulary of terms for ISDNs*, 1988. +- [4] CCITT Rec. Q.711) — *ISDN 64 kbit/s circuit mode switched bearer services*, 1988. +- [5] CCITT Rec. I.255.1 — *Closed User Group*. + +--- + +1) Recommendation Q.71 will be submitted for approval at the CCITT Plenary Assembly in March, 1993. + +- [6] CCITT Rec. I.210 — *Principles of telecommunication services supported by an ISDN and the means used to describe them*, 1988. +- [7] CCITT Rec. Q.950 — *Supplementary services protocols — Structure and general principles*. +- [8] CCITT Rec. Q.931.— *ISDN user-network interface layer 3 specification for basic call control*. +- [9] CCITT Rec. Q.763.— *Specifications of Signalling System No. 7 — Formats and codes*. + +### 1.3 Definitions + +For the purposes of this Recommendation, the following definitions apply: + +*Integrated services digital network (ISDN)* + +See Recommendation I.112 [3], § 2.3, definition 308. + +*Service, telecommunications service* + +See Recommendation I.112 [3], § 2.2, definition 201. + +*Supplementary service* + +See Recommendation I.210 [6], § 2.4. + +#### **Closed User Group** + +Grouping of users with common availability requirements. + +#### **preferential CUG** + +A preferential Closed User Group is the nominated default group to be used when no Closed User Group or explicit outgoing access request is received by the network. + +#### **incoming access** + +An arrangement which allows a member of a Closed User Group to receive calls from outside the Closed User Group. + +#### **outgoing access** + +An arrangement which allows a member of a Closed User Group to place calls outside the Closed User Group. + +#### **incoming calls barred within a Closed User Group** + +An access restriction that prevents a Closed User Group member from receiving calls from other members of that group. + +#### **outgoing calls barred within a Closed User Group** + +An access restriction that prevents a Closed User Group member from placing calls to other members of that group. + +#### **Closed User Group call** + +A call is a call which is restricted to a pre-defined group of users. + +#### **CUG domain** + +An area of common CUG interlock codes. + +The domain internal CUG interlock codes need not be released via the boundary of the domain. + +A Closed User Group application may span over several domains. Both domains shall treat the other domain's Closed User Group as a single member of its own Closed User Group. + +### 1.4 *Symbols and abbreviations* + +| | | +|------|-------------------------------------| +| CC | Call Control | +| CCA | Call control agent | +| CUG | Closed User Group | +| DB | Data base | +| FE | Functional entity | +| FEA | Functional entity actions | +| IA | Incoming access | +| ICB | Incoming calls barred | +| IIC | Incoming international centre | +| ISDN | Integrated services digital network | +| LE | Local exchange | +| OA | Outgoing access | +| OCB | Outgoing calls barred | +| OIC | Outgoing international centre | +| PCUG | Preferential CUG | +| PN | Private network | +| TE | Terminal equipment | + +### 1.5 *Description* + +The general description of the CUG supplementary service is specified in Recommendation I.255.1 [5]. + +### 1.6 *Derivation of the functional model* + +#### 1.6.1 *Functional model description* + +The functional model for the CUG supplementary service shall be as shown in Figures 1-1/Q.85 and 1-2/Q.85. + +The functional model for the application of the CUG supplementary service within a single CUG domain shall be as shown in Figure 1-1/Q.85. + +The expanded functional model used for interworking between CUG domains shall be as shown in Figure 1-2/Q.85. + +![Figure 1-1/Q.85: A functional model diagram showing a sequence of functional elements (FE1, FE2, FE4, FE6) connected by relationships r_a, r_b, and r_c. FE3 is connected to FE2 by relationship r_d, and FE5 is connected to FE4 by relationship r_e.](547f726730e589392f239257a833ede3_img.jpg) + +``` + +graph LR + FE1[FE1] -- r_a --> FE2[FE2] + FE2 -- r_b --> FE4[FE4] + FE4 -- r_c --> FE6[FE6] + FE3[FE3] -- r_d --> FE2 + FE5[FE5] -- r_e --> FE4 + +``` + +Figure 1-1/Q.85: A functional model diagram showing a sequence of functional elements (FE1, FE2, FE4, FE6) connected by relationships r\_a, r\_b, and r\_c. FE3 is connected to FE2 by relationship r\_d, and FE5 is connected to FE4 by relationship r\_e. + +T1125690-90 + +FIGURE 1-1/Q.85 + +![Figure 1-2/Q.85: An expanded functional model diagram showing three domains (Domain A, Domain B, Domain C) stacked vertically. Each domain contains a copy of the functional model from Figure 1-1/Q.85. Domain A has an additional relationship r_y from FE4 to a point below it. Domain B has an additional relationship r_y from FE4 to a point below it. Domain C has an additional relationship r_c from FE4 to FE6. The domains are connected by vertical lines with arrows indicating flow.](88b0f3f4393228e9ea4d6542aef7c399_img.jpg) + +``` + +graph TD + subgraph Domain_A [Domain A] + FE1A[FE1] -- r_a --> FE2A[FE2] + FE2A -- r_b --> FE4A[FE4] + FE4A -- r_y --> P1(( )) + FE3A[FE3] -- r_d --> FE2A + FE5A[FE5] -- r_e --> FE4A + end + subgraph Domain_B [Domain B] + FE1B[FE1] -- r_a --> FE2B[FE2] + FE2B -- r_b --> FE4B[FE4] + FE4B -- r_y --> P2(( )) + FE3B[FE3] -- r_d --> FE2B + FE5B[FE5] -- r_e --> FE4B + end + subgraph Domain_C [Domain C] + FE1C[FE1] -- r_a --> FE2C[FE2] + FE2C -- r_b --> FE4C[FE4] + FE4C -- r_c --> FE6C[FE6] + FE3C[FE3] -- r_d --> FE2C + FE5C[FE5] -- r_e --> FE4C + end + P1 --- P2 + P2 --- FE1C + +``` + +Figure 1-2/Q.85: An expanded functional model diagram showing three domains (Domain A, Domain B, Domain C) stacked vertically. Each domain contains a copy of the functional model from Figure 1-1/Q.85. Domain A has an additional relationship r\_y from FE4 to a point below it. Domain B has an additional relationship r\_y from FE4 to a point below it. Domain C has an additional relationship r\_c from FE4 to FE6. The domains are connected by vertical lines with arrows indicating flow. + +T1125700-90 + +FIGURE 1-2/Q.85 + +##### **Expanded functional model** + + + +![Sequence diagram showing successful CUG calls own domain across six functional entities (FE1 to FE6).](990567efebf979be51f56d1150012c9d_img.jpg) + +The diagram illustrates a sequence of events across six functional entities (FE1 to FE6) during a successful CUG call. The sequence is as follows: + +- FE1** receives an external **INFORM 1 req.** (211 >>>>). It sends **INFORM 1 req. ind.** (211 >>>> |---> | >>>>) to **FE2** and **INFORM 1 req. ind.** (910) to **FE2**. +- FE2** sends **ENQUIRY 1 req. ind.** (920) to **FE3** and **ENQUIRY 1 resp. conf.** (921) to **FE3**. +- FE3** sends **241 >>>> | SETUP req. ind.** (241 >>>> |---> | >>>>) to **FE4** and **INFORM 2 req. ind.** (922) to **FE4**. +- FE4** sends **ENQUIRY 2 req. ind.** (940) to **FE5** and **ENQUIRY 2 resp. conf.** (941) to **FE5**. +- FE5** sends **251 >>>> | SETUP req. ind.** (251 >>>> |---> | >>>>) to **FE6** and **INFORM 1 req. ind.** (942) to **FE6**. +- FE6** sends **251 >>>> | INFORM ind.** (251 >>>> |---> | >>>>) to **FE6** and **INFORM ind.** (960) to **FE6**. + +Relationships between entities are indicated by dashed lines: $r_a$ (FE1 to FE2), $r_b$ (FE2 to FE3), $r_c$ (FE4 to FE5), $r_d$ (FE2 to FE3), and $r_e$ (FE4 to FE5). + +T1131390-91 + +Sequence diagram showing successful CUG calls own domain across six functional entities (FE1 to FE6). + +FIGURE 1-4/Q.85 + +Successful CUG calls own domain + +![Sequence diagram Figure 1-5/Q.85: Chaining of CUG domains. Shows message exchange between FE4 and FE2. FE4 sends SETUP req. ind. (231) to FE2. FE4 also sends INFORM 1 req. ind. to FE2. Labels 940, 941, 942 are associated with FE4, and 920 with FE2. Relationship r_y is indicated between them.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +``` + +sequenceDiagram + participant FE4 + participant FE2 + Note over FE4, FE2: r_y + Note left of FE4: (Note) 940, 941, 942 + FE4->>FE2: 231 SETUP req. ind. 231 + FE4->>FE2: INFORM 1 req. ind. + Note right of FE2: 920 + +``` + +T1131400-91 + +Sequence diagram Figure 1-5/Q.85: Chaining of CUG domains. Shows message exchange between FE4 and FE2. FE4 sends SETUP req. ind. (231) to FE2. FE4 also sends INFORM 1 req. ind. to FE2. Labels 940, 941, 942 are associated with FE4, and 920 with FE2. Relationship r\_y is indicated between them. + +*Note* – Call to this point is covered in Figure 1-4/Q.85. + +FIGURE 1-5/Q.85 + +#### Chaining of CUG domains + +(Successful CUG calls between different CUG domains showing information flows across relationship *r* according to the functional model in Figure 1-2/Q.85.) + +![Sequence diagram Figure 1-6/Q.85: Unsuccessful CUG calls – Case 1 own CUG domains. Shows message exchange between FE1, FE2, and FE3. FE1 sends SETUP req. ind. (211) to FE2. FE2 sends ENQUIRY 1 req. ind. (920) to FE3. FE3 responds with ENQUIRY 1 resp. conf. (930). FE2 sends SETUP REJECT req. ind. (921, 923) to FE1. FE1 sends INFORM 1 REJECT req. ind. (911) to FE2. Relationships r_a and r_d are shown.](367926125450c2bc3f4bdca9d59a62ba_img.jpg) + +``` + +sequenceDiagram + participant FE1 + participant FE2 + participant FE3 + Note over FE1, FE2: r_a + Note over FE2, FE3: r_d + Note left of FE1: 211 >>>> + Note left of FE1: INFORM 1 req. + Note right of FE1: 910 + FE1->>FE2: 211 SETUP req. ind. 221 + Note left of FE2: (Note) + FE1->>FE2: INFORM 1 req. ind. + Note right of FE2: 920 + FE2->>FE3: ENQUIRY 1 req. ind. + Note right of FE3: 930 + FE3-->>FE2: ENQUIRY 1 resp. conf. + Note right of FE2: 921, 923 + FE2-->>FE1: SETUP REJECT req. ind. + Note right of FE2: 924 + FE1->>FE2: INFORM 1 REJECT req. ind. + Note right of FE1: 911 + +``` + +T1131410-91 + +Sequence diagram Figure 1-6/Q.85: Unsuccessful CUG calls – Case 1 own CUG domains. Shows message exchange between FE1, FE2, and FE3. FE1 sends SETUP req. ind. (211) to FE2. FE2 sends ENQUIRY 1 req. ind. (920) to FE3. FE3 responds with ENQUIRY 1 resp. conf. (930). FE2 sends SETUP REJECT req. ind. (921, 923) to FE1. FE1 sends INFORM 1 REJECT req. ind. (911) to FE2. Relationships r\_a and r\_d are shown. + +*Note* – Depending on the progress of the basic call INFORM 1 REJECT will be sent simultaneously with the appropriate basic call clearing information flow. + +FIGURE 1-6/Q.85 + +##### Unsuccessful CUG calls – Case 1 own CUG domains + + + +![Sequence diagram showing information flows between FE4 and FE2. FE4 sends SETUP req. ind. (231) to FE2. FE2 sends INFORM 1 req. ind. to FE4. FE4 sends SETUP REJECT req. ind. to FE2. FE2 sends INFORM 1 REJECT req. ind. to FE4. FE4 also sends 944 to FE2. FE2 sends 920, 921, 923, and 924 to FE4. A dashed line r_y connects FE4 and FE2. Notes 1 and 2 are present.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +Sequence diagram showing information flows between FE4 and FE2. FE4 sends SETUP req. ind. (231) to FE2. FE2 sends INFORM 1 req. ind. to FE4. FE4 sends SETUP REJECT req. ind. to FE2. FE2 sends INFORM 1 REJECT req. ind. to FE4. FE4 also sends 944 to FE2. FE2 sends 920, 921, 923, and 924 to FE4. A dashed line $r_y$ connects FE4 and FE2. Note 1 is at FE2 and Note 2 is at FE4. + +Sequence diagram showing information flows between FE4 and FE2. FE4 sends SETUP req. ind. (231) to FE2. FE2 sends INFORM 1 req. ind. to FE4. FE4 sends SETUP REJECT req. ind. to FE2. FE2 sends INFORM 1 REJECT req. ind. to FE4. FE4 also sends 944 to FE2. FE2 sends 920, 921, 923, and 924 to FE4. A dashed line r\_y connects FE4 and FE2. Notes 1 and 2 are present. + +*Note 1* – Call to this point is covered in Figure 1-4/Q.85. +*Note 2* – Depending on the progress of the basic call INFORM 1 REJECT will be sent simultaneously with the appropriate basic call clearing information flow. + +FIGURE 1-8/Q.85 +**Chaining of CUG domains** + +(Unsuccessful CUG calls between different CUG domains showing information flows across relationship $r$ according to the functional model in Figure 1-2/Q.85.) + +#### 1.7.2 Definition of individual information flows + +##### 1.7.2.1 Relationship $r_a$ + +###### 1.7.2.1.1 Contents of INFORM 1 + +The contents of INFORM 1 shall be as in Table 1-1/Q.85. INFORM 1 is an optional information flow. + +TABLE 1-1/Q.85 +**INFORM 1 contents** + +| Name | req. ind. | Allowed value | +|----------------------------|----------------------|---------------| +| CUG index
OA indication | optional
optional | ON
OFF | + +###### 1.7.2.1.2 Contents of INFORM 1 REJECT + +The contents of INFORM 1 REJECT shall be as in Table 1-2/Q.85. + +TABLE 1-2/Q.85 + +###### **INFORM 1 REJECT contents** + +| Name | req. ind. | Allowed value | +|---------------------|-----------|---------------| +| CUG specific reason | Mandatory | (Note) | + +*Note* – For allowed values, see Recommendation Q.950 [7]. + +##### 1.7.2.2 *Relationship $r_b$* + +###### 1.7.2.2.1 *Contents of INFORM 2* + +The contents of INFORM 2 shall be as in Table 1-3/Q.85. INFORM 2 at $r_b$ is an optional information flow. + +TABLE 1-3/Q.85 + +###### **INFORM 2 contents** + +| Name | req. ind. | Allowed value | +|--------------------|--------------------|---------------| +| CUG interlock code | Mandatory (Note 1) | (Note 2) | +| OA indication | Optional | ON
OFF | + +*Note 1* – Where the INFORM 2 information flow crosses an international gateway, the CUG interlock code shall be an international CUG interlock code. + +*Note 2* – As specified in § 3.13 of Recommendation Q.763 [9]. + +###### 1.7.2.2.2 *Contents of INFORM 2 REJECT* + +The contents of INFORM 2 REJECT shall be as in Table 1-4/Q.85. + +TABLE 1-4/Q.85 + +###### **INFORM 2 REJECT contents** + +| Name | req. ind. | Allowed value | +|---------------------|-----------|---------------| +| CUG specific reason | Mandatory | (Note) | + +*Note* – For allowed values, see Recommendation Q.950 [7]. + +##### 1.7.2.3 *Relationship $r_c$* + +INFORM 1, see § 1.7.2.1.1. + +INFORM 1 REJ, see § 1.7.2.1.2. + +##### 1.7.2.4 Relationship $r_d$ + +###### 1.7.2.4.1 Contents of ENQUIRY 1 + +The contents of ENQUIRY 1 shall be as in Tables 1-5/Q.85 and 1-6/Q.85. + +TABLE 1-5/Q.85 +ENQUIRY 1 contents + +| Name | req. ind. | Allowed value | +|-------------------------------|-----------|---------------| +| Calling party number (Note 1) | Mandatory | (Note 2) | +| Basic service | Mandatory | (Note 2) | +| CUG index | Optional | | +| OA indication | Optional | ON
OFF | + +*Note 1* – FE2 may send the ENQUIRY to FE3 as soon as sufficient addressing information to identify the access can be included. + +*Note 2* – The values are derived from the original call set-up request. For allowed values see Recommendation Q.931 [8]. + +The result shall be one of the following values: + +TABLE 1-6/Q.85 + +| Name | resp. conf. | Allowed value | +|-----------------------------------------|-------------|-----------------| +| Non-CUG | Optional | | +| CUG interlock code | Optional | (Note 3) | +| Reject reason | Optional | (Note 2) | +| CUG interlock code and
OA indication | Optional | (Notes 3 and 4) | + +*Note 1* – The information elements above shall be mutually exclusive. + +*Note 2* – For allowed values see Recommendation Q.950 [7]. + +*Note 3* – As specified in § 3.13 of Recommendation Q.763 [9]. + +*Note 4* – National option. + +##### 1.7.2.5 Relationship $r_e$ + +###### 1.7.2.5.1 Contents of ENQUIRY 2 + +The contents of ENQUIRY 2 shall be as in Tables 1-7/Q.85 and 1-8/Q.85. + +TABLE 1-7/Q.85 + +###### **ENQUIRY 2 contents** + +| Name | req. ind | Allowed value | +|------------------------------|-----------|---------------| +| Called party number (Note 2) | Mandatory | (Note 3) | +| Basic service | Mandatory | (Note 3) | +| CUG interlock code (Note 1) | Optional | (Note 4) | +| Non-CUG | Optional | | +| OA indication (Note 1) | Optional | (Note 4) | + +*Note 1* — A combination CUG interlock code with OA indication shall be supported. + +*Note 2* — FE4 may send the ENQUIRY to FE5 as soon as sufficient addressing information to identify the access can be included + +*Note 3* — The values are derived from the received call set-up request. For allowed values see Recommendation Q.931 [8]. + +*Note 4* — As specified in § 3.13 of Recommendation Q.763 [9]. + +The result shall be one of the following values: + +TABLE 1-8/Q.85 + +| Name | resp. conf. | Allowed value | +|---------------|-------------|---------------| +| Non-CUG | Optional | | +| CUG index | Optional | | +| OA indication | Optional | | +| Reject reason | Optional | (Note 2) | + +*Note 1* – *resp. conf.* conveying the combination CUG index with OA indication may be supported as a national option. + +*Note 2* – For allowed values, see Recommendation Q.950 [7]. + +##### 1.7.2.6 Relationship $r_y$ + +This relationship appears to be an $r_c$ relationship to FE4 and an $r_a$ relationship to FE2. + +INFORM 1, see § 1.7.2.1.1. + +INFORM 1 REJECT, see § 1.7.2.1.2. + +At this relationship the CUG index is mandatory. + +![Sequence diagram showing CUG1 sending an INFORM 1 req. ind. to CUG2, and CUG3 sending an INFORM 1 REJECT req. ind. to CUG4, with associated reject reasons and connector labels.](bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg) + +``` + +sequenceDiagram + participant CUG1 + participant CUG2 + participant CUG3 + participant CUG4 + + CUG1->>CUG2: INFORM 1 req. ind. (Note 1) + Note over CUG1, CUG2: 910 r_a, FE2 + CUG3->>CUG4: INFORM 1 REJECT req. ind. + Note over CUG3, CUG4: 911 r_a, FE2 + Note over CUG4: Reject reason (Note 2) + Note over CUG4: 911 + +``` + +The diagram illustrates two separate call flows. In the first flow, CUG1 sends an 'INFORM 1 req. ind. (Note 1)' to CUG2. This message is associated with connector label '910' and 'r\_a, FE2'. In the second flow, CUG3 sends an 'INFORM 1 REJECT req. ind.' to CUG4. This message is associated with connector label '911' and 'r\_a, FE2'. Following this, CUG4 sends a 'Reject reason (Note 2)' message, which is associated with connector label '911'. + +Sequence diagram showing CUG1 sending an INFORM 1 req. ind. to CUG2, and CUG3 sending an INFORM 1 REJECT req. ind. to CUG4, with associated reject reasons and connector labels. + +T1125770-90 + +*Note 1* – This INFORM 1 req. ind. shall be sent simultaneously with the basic call SETUP req. ind. + +*Note 2* – The INFORM 1 REJECT will be processed together with the basic call clearing information flows. + +*Note 3* – CUG1 and CUG2 break the base call between connector S1/1 and S1/2 of Recommendation Q.71 [4]. + +*Note 4* – CUG3 and CUG4 break the basic call transition during the CCA state “Call sent” or “Wait for further digits” or “Wait for SETUP resp. conf.” prior to the accept of SETUP resp. conf. after the receipt of SETUP REJECT req. ind., DISCONNECT req. ind. (FE411), RELEASE req. ind. (see Figure A-1/Q.71 of Recommendation Q.71 [4]). + +FIGURE 1-9/Q.85 + +**CUG, FE1** + +![Flowchart for CUG, FE2. The process starts with CUG6 leading to 'INFORM 1 req. ind. (Note 1)'. This leads to a decision 'Does the calling user have the CUG facility?'. If 'No', it goes to 'CUG or CUG OA requested?'. If 'Yes', it goes to 'ENQUIRY 1 req. ind.', then 'SET (NOW + WAITING TIME, TIMER TCUG 1) (Note 4)', then 'WAIT ENQUIRY'. From 'WAIT ENQUIRY', it branches to 'TIMER TCUG1', 'ENQUIRY 1 resp. conf. (REJECT REASON)', or 'ENQUIRY 1 conf. resp. "OK"'. 'TIMER TCUG1' leads to 'SET REJECT REASON = SERVICE NOT AVAILABLE'. 'ENQUIRY 1 resp. conf. (REJECT REASON)' leads to 'RESET (TIMER TCUG1)'. 'ENQUIRY 1 conf. resp. "OK"' leads to 'RESET (TIMER TCUG1)'. Both 'SET REJECT REASON = SERVICE NOT AVAILABLE' and 'RESET (TIMER TCUG1)' lead to a decision 'CUG supplementary service explicitly requested by the user?'. If 'Yes', it goes to 'INFORM 1 REJECT req. ind.', then 'CUG8'. If 'No', it goes to 'INSERT REJECT REASON into basic call clearing information flow', then 'CUG8'. 'INFORM 1 REJECT req. ind.' also leads to 'CUG8'. 'ENQUIRY 1 conf. resp. "OK"' leads to a decision 'Ordinary call?'. If 'Yes', it goes to 'INFORM 2 req. ind. (Note 2)', then 'CUG7'. If 'No', it goes to 'INFORM 1 REJECT req. ind.', then 'CUG8'. Notes 920, 921, 922, 923, 924, and 925 provide additional context for various steps and decisions.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +``` + +graph TD + CUG6((CUG6)) --> INFORM1reqind1[INFORM 1 req. ind. + (Note 1)] + INFORM1reqind1 --> CUG5((CUG5)) + CUG5 --> DoescallinguserhaveCUGfacility{Does + the calling user + have the CUG + facility?} + DoescallinguserhaveCUGfacility -- No --> CUGorCUGOArequested{CUG + or CUG OA + requested?} + DoescallinguserhaveCUGfacility -- Yes --> ENQUIRY1reqind[ENQUIRY 1 + req. ind.] + ENQUIRY1reqind --> SETNOWWAITINGTIME[SET (NOW + + WAITING TIME, + TIMER TCUG 1) + (Note 4)] + SETNOWWAITINGTIME --> WAITENQUIRY([WAIT + ENQUIRY]) + WAITENQUIRY --> TIMERTCUG1[/TIMER + TCUG1/] + WAITENQUIRY --> ENQUIRY1respconf[ENQUIRY 1 + resp. conf. + (REJECT + REASON)] + WAITENQUIRY --> ENQUIRY1confrespOK[/ENQUIRY 1 + conf. resp. + "OK"/] + TIMERTCUG1 --> SETREJECTREASON[SET REJECT + REASON = SERVICE + NOT AVAILABLE] + ENQUIRY1respconf --> RESETTIMERTCUG1[RESET (TIMER + TCUG1)] + ENQUIRY1confrespOK --> RESETTIMERTCUG1_2[RESET (TIMER + TCUG1)] + SETREJECTREASON --> CUGsupplementaryserviceexplicitlyrequested{CUG + supplementary + service explicitly + requested by + the user?} + RESETTIMERTCUG1 --> CUGsupplementaryserviceexplicitlyrequested + CUGsupplementaryserviceexplicitlyrequested -- Yes --> INFORM1REJECTreqind[INFORM 1 + REJECT + req. ind.] + CUGsupplementaryserviceexplicitlyrequested -- No --> INSERTREJECTREASON[INSERT REJECT + REASON into basic + call clearing + information flow] + INFORM1REJECTreqind --> CUG8((CUG8)) + INSERTREJECTREASON --> CUG8 + RESETTIMERTCUG1_2 --> Ordinarycall{Ordinary + call?} + Ordinarycall -- Yes --> INFORM2reqind[INFORM 2 + req. ind. + (Note 2)] + Ordinarycall -- No --> INFORM1REJECTreqind_2[INFORM 1 + REJECT + req. ind.] + INFORM2reqind --> CUG7((CUG7)) + INFORM1REJECTreqind_2 --> CUG8_2((CUG8)) + CUGorCUGOArequested -- Yes --> INFORM1REJECTreqind_3[INFORM 1 + REJECT + req. ind.] + CUGorCUGOArequested -- No --> CUG7_2((CUG7)) + INFORM1REJECTreqind_3 --> CUG8_3((CUG8)) + +``` + +920: Does the calling user have the CUG facility? + +921: FE3, $r_d$ + +922: $r_b$ , FE4 + +923: INSERT REJECT REASON into basic call clearing information flow + +924 (Note 5): This information flow is sent simultaneously with the basic call clearing information flow + +924 (Note 5): This information flow shall be sent simultaneously with the basic call clearing information flow + +FE3, $r_d$ : There are three cases -IC, non CUG, as a national option: IC + OA + +(Note 6): Ordinary call? + +Flowchart for CUG, FE2. The process starts with CUG6 leading to 'INFORM 1 req. ind. (Note 1)'. This leads to a decision 'Does the calling user have the CUG facility?'. If 'No', it goes to 'CUG or CUG OA requested?'. If 'Yes', it goes to 'ENQUIRY 1 req. ind.', then 'SET (NOW + WAITING TIME, TIMER TCUG 1) (Note 4)', then 'WAIT ENQUIRY'. From 'WAIT ENQUIRY', it branches to 'TIMER TCUG1', 'ENQUIRY 1 resp. conf. (REJECT REASON)', or 'ENQUIRY 1 conf. resp. "OK"'. 'TIMER TCUG1' leads to 'SET REJECT REASON = SERVICE NOT AVAILABLE'. 'ENQUIRY 1 resp. conf. (REJECT REASON)' leads to 'RESET (TIMER TCUG1)'. 'ENQUIRY 1 conf. resp. "OK"' leads to 'RESET (TIMER TCUG1)'. Both 'SET REJECT REASON = SERVICE NOT AVAILABLE' and 'RESET (TIMER TCUG1)' lead to a decision 'CUG supplementary service explicitly requested by the user?'. If 'Yes', it goes to 'INFORM 1 REJECT req. ind.', then 'CUG8'. If 'No', it goes to 'INSERT REJECT REASON into basic call clearing information flow', then 'CUG8'. 'INFORM 1 REJECT req. ind.' also leads to 'CUG8'. 'ENQUIRY 1 conf. resp. "OK"' leads to a decision 'Ordinary call?'. If 'Yes', it goes to 'INFORM 2 req. ind. (Note 2)', then 'CUG7'. If 'No', it goes to 'INFORM 1 REJECT req. ind.', then 'CUG8'. Notes 920, 921, 922, 923, 924, and 925 provide additional context for various steps and decisions. + +T1131440-91 + +FIGURE 1-10/Q.85 (sheet 1 of 2) + +**CUG, FE2** + +Notes relative to Figure 1-10/Q.85 (sheet 1 of 2): + +Note 1 – $r_a$ , FE1 from a user end equipment – $r_y$ from another CUG domain. + +Note 2 – This INFORM 2 req. ind. shall be sent simultaneously with the basic call SETUP req. ind. + +Note 3 – On a call received from an end user equipment CUG5, CUG6, CUG7 and CUG8 break the basic call between connector S2/1 and S2/2 of Recommendation Q.71 [4]. + +On a call received from another CUG domain of a private ISDN, CUG5, CUG6, CUG7 and CUG8 break the basic call during CC state "IDLE" during FEA 261 [see Figure 2-18/Q.71 [4] (sheet 1 of 7)] by following the YES branch of the decision "successful" and prior to sending "SETUP ind.". The analysis of MSN or DDI shall be performed prior to the invocation of CUG. CUG7 is the exit to proceed with the call and CUG8 is the exit where the call shall be cleared, this is the same exit as the NO-branch of the preceding decision "successful" of Recommendation Q.71 [4]. + +Note 4 – Timer TCUG1 shall be implemented in the case of the remote data base. TCUG1 shall be automatically reset by basic call at any event resulting in clearing the call relation. + +Note 5 – $r_a$ , FE1 towards an end user equipment; $r_y$ , FE4 towards another CUG domain. + +Note 6 – The primary decision whether the call is to be set-up as a normal call or not, can be made either by FE3 or by FE2. + +![Flowchart for CUG, FE2. The process starts with CUG9, leading to an 'INFORM 2 REJECT req. ind.' block. A dashed line labeled '924 FE4, r_b (Note 1)' connects this block to a decision diamond: 'CUG supplementary service explicitly requested by the user?'. If 'Yes', the flow goes to 'INFORM 1 REJECT req. ind.'. If 'No', it goes to 'Insert reject reason into basic call clearing information flows'. A dashed line labeled '923' connects this block to 'INFORM 1 REJECT req. ind.'. Another dashed line labeled '924 (Note 2)' connects 'INFORM 1 REJECT req. ind.' back to 'Insert reject reason...'. Both paths eventually lead to CUG10. The reference T1125790-90 is at the bottom right.](43837b056625d3d6ce615e4c02f163bb_img.jpg) + +``` + +graph TD + CUG9((CUG9)) --> Inform2[INFORM 2 +REJECT +req. ind.] + Inform2 -.-> Label1["924 +FE4, r_b +(Note 1)"] + Label1 -.-> Decision{CUG +supplementary +service explicitly +requested by the +user?} + Decision -- Yes --> Inform1[INFORM 1 +REJECT +req. ind.] + Decision -- No --> Insert[Insert reject reason +into basic call +clearing information +flows] + Insert -.-> Label2["923"] + Label2 -.-> Inform1 + Inform1 -.-> Label3["924 +(Note 2)"] + Label3 -.-> Insert + Inform1 --> CUG10((CUG10)) + Insert --> CUG10 + +``` + +T1125790-90 + +Flowchart for CUG, FE2. The process starts with CUG9, leading to an 'INFORM 2 REJECT req. ind.' block. A dashed line labeled '924 FE4, r\_b (Note 1)' connects this block to a decision diamond: 'CUG supplementary service explicitly requested by the user?'. If 'Yes', the flow goes to 'INFORM 1 REJECT req. ind.'. If 'No', it goes to 'Insert reject reason into basic call clearing information flows'. A dashed line labeled '923' connects this block to 'INFORM 1 REJECT req. ind.'. Another dashed line labeled '924 (Note 2)' connects 'INFORM 1 REJECT req. ind.' back to 'Insert reject reason...'. Both paths eventually lead to CUG10. The reference T1125790-90 is at the bottom right. + +Note 1 – Information processed simultaneously with the basic call clearing information flows. + +Note 2 – FE1, $r_a$ towards a user end equipment FE4, $r_y$ towards another CUG domain. This information flow shall be sent simultaneously with the basic call clearing information flow. + +Note 3 – CUG9 and CUG10 are hooks at the receipt of basic call clearing information flows at outgoing calls prior to the receipt of SETUP resp. conf., they break the basic call between connectors S2/35 and S2/36, S2/37 and S2/38 of Recommendation Q.71 [4]. CUG9 and CUG10 additionally are hooks in CC FE2 call state $r_1$ - $r_2$ CALL SENT following the receipt of RELEASE req. ind. (see Recommendation Q.71 [4], Figure A-2/Q.71). On a call received from an other CUG domain of a private ISDN, CUG9 and CUG10 break accordingly (see Figures 2-18 CC FE6, sheet 2 of 7, sheet 3 of 7, sheet 7 of 7 of Recommendation Q.71 [4]). + +**FIGURE 1-10/Q.85 (sheet 2 of 2)** + +**CUG, FE2** + +![Flowchart for CUG, FE3 showing the process from IDLE to ENQUIRY 1 req. ind., Perform outgoing CUG control, Results? decision, and two possible responses: REJECT REASON or OK, both leading back to IDLE.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +graph TD + IDLE1([IDLE]) --> ENQUIRY1[ENQUIRY 1 +req. ind.] + rd_FE2_1["rd, FE2"] -.-> ENQUIRY1 + ENQUIRY1 --> CUG[Perform outgoing +CUG control] + CUG -.-> 930 + CUG --> RESULTS{Results?} + RESULTS -- OK --> ENQUIRY1_OK[ENQUIRY 1 +resp. conf. +("OK")] + RESULTS -- Reject --> ENQUIRY1_REJECT[ENQUIRY 1 +resp. conf. +(REJECT +REASON)] + rd_FE2_2["rd, FE2"] -.-> ENQUIRY1_REJECT + rd_FE2_3["rd, FE2"] -.-> ENQUIRY1_OK + ENQUIRY1_REJECT --> IDLE2([IDLE]) + ENQUIRY1_OK --> IDLE3([IDLE]) + +``` + +The flowchart illustrates the process for CUG, FE3. It begins with an IDLE state, leading to an ENQUIRY 1 req. ind. process. A dashed arrow labeled $r_d, FE2$ points to this process. The process then leads to Perform outgoing CUG control, which has a dashed arrow labeled 930 pointing to it. From Perform outgoing CUG control, the flow goes to a decision diamond labeled Results?. If the result is OK, the flow goes to an ENQUIRY 1 resp. conf. ("OK") process. If the result is Reject, the flow goes to an ENQUIRY 1 resp. conf. (REJECT REASON) process. Both of these response processes have a dashed arrow labeled $r_d, FE2$ pointing to them. Finally, both response processes lead back to an IDLE state. + +Flowchart for CUG, FE3 showing the process from IDLE to ENQUIRY 1 req. ind., Perform outgoing CUG control, Results? decision, and two possible responses: REJECT REASON or OK, both leading back to IDLE. + +T11255800-90 + +FIGURE 1-11/Q.85 +CUG, FE3 + +![Flowchart for CUG, FE4. The process starts with CUG11 and CUG12. A decision diamond asks 'Does the called user have the CUG facility?'. If 'No', it goes to CUG13. If 'Yes', it goes to 'INFORM 2 req. ind.' (receiving r_b, FE2 940). This leads to 'ENQUIRY 2 req. ind.' (receiving FE5, r_e), then 'SET (NOW + WAITING TIME, TIMER TCUG1) (Note 1)', and 'WAIT ENQUIRY'. From 'WAIT ENQUIRY', three paths emerge: 1) 'TIMER TCUG1' leading to 'SET REJECT REASON = SERVICE NOT AVAILABLE', which then leads to 'INFORM 2 REJECT req. ind.' (receiving r_b, FE2 943) and finally CUG14. 2) 'ENQUIRY 2 resp. conf. (REJECT REASON)' (receiving FE5, r_e 941) leading to 'Reset (Timer TCUG1)', which then leads to 'INFORM 2 REJECT req. ind.' and CUG14. 3) 'ENQUIRY 2 conf. resp. (OK)' (receiving FE5, r_e 941) leading to 'Reset (Timer TCUG1)', which then leads to 'INFORM 1 req. ind. (Note 2)' (receiving r_y, FE2 towards another CUG domain and r_c, FE6 towards an end user equipment) and finally CUG13. A note on the right explains the three cases for FE5, r_e 941: non IC - CUG index, or as a national option: CUG index + OA indication.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +``` + +graph TD + CUG11((CUG11)) --> D1{Does the called user have the CUG facility?} + CUG12((CUG12)) --> I2req[INFORM 2 req. ind.] + I2req -.->|r_b, FE2 940| I2req + I2req --> D1 + D1 -- No --> CUG13((CUG13)) + D1 -- Yes --> E2req[/ENQUIRY 2 req. ind./] + E2req -.->|FE5, r_e| E2req + E2req --> S1[SET (NOW + WAITING TIME, TIMER TCUG1) (Note 1)] + S1 --> W1[/WAIT ENQUIRY/] + W1 --> T1[/TIMER TCUG1/] + T1 --> S2[SET REJECT REASON = SERVICE NOT AVAILABLE] + S2 --> I2rej[/INFORM 2 REJECT req. ind./] + I2rej -.->|r_b, FE2 943| I2rej + I2rej --> CUG14((CUG14)) + W1 --> E2resp[/ENQUIRY 2 resp. conf. (REJECT REASON)/] + E2resp -.->|FE5, r_e 941| E2resp + E2resp --> R1[Reset (Timer TCUG1)] + R1 --> I2rej + W1 --> E2ok[/ENQUIRY 2 conf. resp. ("OK")/] + E2ok -.->|FE5, r_e 941| E2ok + E2ok --> R2[Reset (Timer TCUG1)] + R2 --> I1req[/INFORM 1 req. ind. (Note 2)/] + I1req -.->|942 r_y, FE2 towards another CUG domain; r_c, FE6 towards an end user equipment| I1req + I1req --> CUG13 + +``` + +FE5, re 941 +There are three cases – non IC – CUG index, – as a national option: CUG index + OA indication + +942 +ry, FE2 towards another CUG domain +rc, FE6 towards an end user equipment + +Flowchart for CUG, FE4. The process starts with CUG11 and CUG12. A decision diamond asks 'Does the called user have the CUG facility?'. If 'No', it goes to CUG13. If 'Yes', it goes to 'INFORM 2 req. ind.' (receiving r\_b, FE2 940). This leads to 'ENQUIRY 2 req. ind.' (receiving FE5, r\_e), then 'SET (NOW + WAITING TIME, TIMER TCUG1) (Note 1)', and 'WAIT ENQUIRY'. From 'WAIT ENQUIRY', three paths emerge: 1) 'TIMER TCUG1' leading to 'SET REJECT REASON = SERVICE NOT AVAILABLE', which then leads to 'INFORM 2 REJECT req. ind.' (receiving r\_b, FE2 943) and finally CUG14. 2) 'ENQUIRY 2 resp. conf. (REJECT REASON)' (receiving FE5, r\_e 941) leading to 'Reset (Timer TCUG1)', which then leads to 'INFORM 2 REJECT req. ind.' and CUG14. 3) 'ENQUIRY 2 conf. resp. (OK)' (receiving FE5, r\_e 941) leading to 'Reset (Timer TCUG1)', which then leads to 'INFORM 1 req. ind. (Note 2)' (receiving r\_y, FE2 towards another CUG domain and r\_c, FE6 towards an end user equipment) and finally CUG13. A note on the right explains the three cases for FE5, r\_e 941: non IC - CUG index, or as a national option: CUG index + OA indication. + +T1131450-90 + +FIGURE 1-12/Q.85 (sheet 1 of 2) + +CUG, FE4 + +Notes relative to Figure 1-12/Q.85 (sheet 1 of 2): + +*Note 1* – Timer TCUG1 shall be implemented in the case of the remote data base. TCUG1 shall be automatically reset by basic call at any event resulting in clearing the call relation. + +*Note 2* – This INFORM 1 req. ind. shall be sent simultaneously with the basic call SETUP req. ind. + +*Note 3* – CUG11, CUG12, CUG13 and CUG14 break the basic call on a call towards a user end equipment between connector S4/31 and S4/32 of Recommendation Q.71 [4]. On a call towards another CUG domain of a private ISDN, CUG11, CUG12, CUG13 and CUG14 break the basic call during CC state “IDLE” during FEA271 (see Figure 2-19/Q.71 [4]). “Terminating screening, process attempt” prior to sending SETUP req. ind. (FEA271). + +The analysis of MSN and DDI shall be performed prior to invocation of CUG. The CUG specific checks shall be performed prior to the determination of network determined user busy. + +CUG13 is the exit to proceed with the call CUG14 is the exit where the call shall be cleared: this is the same exit as the NO-branch of the preceding decision “successful” of Recommendation Q.71 [4]. + +![Flowchart for CUG15 and CUG16 showing information flow and rejection signals.](2eb23c2210154279f8013a1594fbcc5a_img.jpg) + +``` +graph TD; CUG15((CUG15)) --> INFORM1[INFORM 1 +REJECT +req. ind.]; INFORM1 -.-> FE2rY[944 +FE2, ry]; INFORM1 --> INFORM2[INFORM 2 +REJECT +req. ind.]; FE2rB[FE2, rb] -.-> INFORM2; INFORM2 --> CUG16((CUG16)); +``` + +The diagram is a flowchart illustrating the information flow between CUG15 and CUG16. It starts with a circle labeled 'CUG15' at the top. An arrow points down to a rectangular box labeled 'INFORM 1 REJECT req. ind.'. From this box, a dashed arrow points to the right towards a bracketed label '944 FE2, ry'. Another arrow points down from the 'INFORM 1' box to a second rectangular box labeled 'INFORM 2 REJECT req. ind.'. A dashed arrow points from the left towards the 'INFORM 2' box, originating from a bracketed label 'FE2, rb'. Finally, an arrow points down from the 'INFORM 2' box to a circle labeled 'CUG16' at the bottom. The identifier 'T1125820-90' is located at the bottom right of the diagram. + +Flowchart for CUG15 and CUG16 showing information flow and rejection signals. + +*Note* – This information flow is processed simultaneously with the basic call clearing information flow. On a call towards another CUG domain of a private ISDN CUG15 and CUG16 break the basic call transition during any call state after sending of SETUP req. ind. and prior to receipt of REPORT (ALERTING) or SETUP resp. conf. (if no alerting occurs). See Figure 2-19/Q.71 of Recommendation Q.71 [4]. + +FIGURE 1-12/Q.85 (sheet 2 of 2) + +**CUG, FE4** + +![Flowchart for CUG, FE5 showing the process from IDLE to ENQUIRY 2 req. ind., then to Perform incoming CUG control, a decision diamond 'Results?', and two possible paths: 'Reject' leading to ENQUIRY 2 (REJECT REASON) resp. conf. and 'OK' leading to ENQUIRY 2 resp. conf. 'OK'. Both paths lead back to IDLE. External inputs FE4, r_e and 950 are shown.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +``` + +graph TD + IDLE1([IDLE]) --> ENQUIRY2[ENQUIRY 2 +req. ind.] + FE4_re[FE4, r_e] -.-> ENQUIRY2 + ENQUIRY2 --> CUG[Perform +incoming CUG +control] + 950 -.-> CUG + CUG --> Results{Results?} + Results -- OK --> ENQUIRY2_OK[ENQUIRY 2 +resp. conf. +"OK"] + Results -- Reject --> ENQUIRY2_REJECT[ENQUIRY 2 +(REJECT +REASON) +resp. conf.] + FE4_re -.-> ENQUIRY2_REJECT + FE4_re -.-> ENQUIRY2_OK + ENQUIRY2_REJECT --> IDLE2([IDLE]) + ENQUIRY2_OK --> IDLE3([IDLE]) + +``` + +Flowchart for CUG, FE5 showing the process from IDLE to ENQUIRY 2 req. ind., then to Perform incoming CUG control, a decision diamond 'Results?', and two possible paths: 'Reject' leading to ENQUIRY 2 (REJECT REASON) resp. conf. and 'OK' leading to ENQUIRY 2 resp. conf. 'OK'. Both paths lead back to IDLE. External inputs FE4, r\_e and 950 are shown. + +T1125830-90 + +FIGURE 1-13/Q.85 +CUG, FE5 + +### 1.9 Functional entity actions (FEAs) + +#### 1.9.1 FEAs of FE1 + +910: The functional entity shall receive CUG request from the user and transfer the request simultaneously with the call setup request. + +911: The functional entity shall recognize CUG specific reject reasons and indicate the reason to its user. + +#### 1.9.2 FEAs of FE2 + +920: The functional entity shall: + +- identify a CUG call; +- check the CUG subscription of the calling user; +- access the outgoing CUG control entity (FE3). + +- 921: The functional entity shall receive the results of the CUG specific checks from the outgoing CUG control entity (FE3). +- 922: The functional entity shall: +- store the CUG characteristics as received from FE3; + - transfer the CUG request simultaneously with the basic call setup request as received from FE3. +- 923: The functional entity shall insert the reject reason into basic call clearing information flow element “cause”. +- 924: The functional entity shall transfer simultaneously with basic call control clearing information flow INFORM 1 REJECT with CUG specific reasons. + +![Sequence diagram for CUG, FE6. It shows a flow from CUG17 to a process block 'INFORM 1 req. ind. (Note 1)'. A dashed arrow from a box labeled '960 FE4, r_c (Notes 1 and 2)' also points to this block. The flow then goes to another process block 'INFORM 1 ind. (Notes 1 and 2)', which has a dashed arrow pointing to a box labeled 'User'. Finally, the flow ends at CUG18. The diagram is labeled T1125840-90.](08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg) + +``` + +sequenceDiagram + participant CUG17 + participant FE4 as 960 FE4, r_c (Notes 1 and 2) + participant P1 as INFORM 1 req. ind. (Note 1) + participant P2 as INFORM 1 ind. (Notes 1 and 2) + participant User + participant CUG18 + + CUG17 --> P1 + FE4 -.-> P1 + P1 --> P2 + P2 -.-> User + P2 --> CUG18 + +``` + +T1125840-90 + +Sequence diagram for CUG, FE6. It shows a flow from CUG17 to a process block 'INFORM 1 req. ind. (Note 1)'. A dashed arrow from a box labeled '960 FE4, r\_c (Notes 1 and 2)' also points to this block. The flow then goes to another process block 'INFORM 1 ind. (Notes 1 and 2)', which has a dashed arrow pointing to a box labeled 'User'. Finally, the flow ends at CUG18. The diagram is labeled T1125840-90. + +*Note 1* – This is received/sent simultaneously with the basic call SETUP req. ind. + +*Note 2* – CUG17 and CUG18 break the basic call between connector S5/1 and S5/2 (see Recommendation Q.71 [4]). + +FIGURE 1-14/Q.85 + +##### CUG, FE6 + +#### 1.9.3 FEAs of FE3 + +- 930: The functional entity shall: +- perform validation checks of CUG information of a calling user according to Table 1-9/Q.85; + - convert the CUG index to an interlock code. + +TABLE 1-9/Q.85 + +CUG interpretation table (outgoing side) + +| SETUP presentation | | | | CUG with index
OA = OFF | CUG with index
OA = ON | CUG without index
OA = OFF | CUG without index
OA = ON | Non-CUG information | +|-------------------------|--------------|--------------|------|----------------------------|---------------------------|-------------------------------|------------------------------|---------------------| +| Calling user class | | | | | | | | | +| CUG | CUG + OA (E) | CUG + OA (I) | PCUG | | | | | | +| Yes | | | | Specified CUG a) | Specified CUG a) | Rejected | Rejected | Rejected | +| | Yes | | | Specified CUG a) | Specified CUG b) | Rejected | Ordinary call | Ordinary call | +| | | Yes | | Specified CUG b) | Specified CUG b) | Ordinary call | Ordinary call | Ordinary call | +| Yes | | | Yes | Specified CUG a) | Specified CUG a) | PCUG a) | Rejected | PCUG a) | +| | Yes | | Yes | Specified CUG a) | Specified CUG b) | PCUG a) | Ordinary call | PCUG a) | +| | | Yes | Yes | Specified CUG b) | Specified CUG b) | c) a) | Ordinary call c) a) | c) a) | +| | | | | | | | | | +| Calling user is NOT CUG | | | | REJECT | | | | Ordinary call | + +FE3 + +FE2 + +a) In case of OCB (CUG), a call is rejected. + +The combination of PCUG and OCB with the PCUG is barred in the option data. + +b) In case of OCB (CUG), a call is interpreted as an ordinary call. + +c) Both “preferential CUG” and “implicit” outgoing access options imply that no subscriber procedures are needed to invoke either of the options when placing a call. When a user subscribes to both options, the network does not know which option the user is invoking, if no additional subscriber procedures are used when placing the call. + +Three ways of operating are recommended: + +- 1) the user has to indicate if a call is intended to be an outgoing access call. If no information (CUG request or outgoing call request) is given, the preferential CUG is assumed; +- 2) the combination is not allowed, i.e. a user cannot have both options allocated at the same time; +- 3) the caller may make a call and the network will route the call with the preferential CUG and an outgoing access request. The call will therefore be connected if the called number is a member of the preferential CUG or is a member of a different CUG and has incoming access, or is a non-CUG user. + +In the case of the first way of operating, CUG interpretation is “PCUG”. In the case of OCB, Note a) is applicable. + +In the case of the second way of operating, the combination of the options is not allowed. + +In the case of the third way of operating, CUG interpretation is “PCUG with OA”. In the case of OCB, Note a) is applicable. + +The choice from the above cases is a national option. + +OA(E) Outgoing access explicit + +If the “allowed per call (explicit OA)” outgoing access option is assigned then the CUG user can determine the OA status by means of the OA request on a call by call basis, but if the “allowed per call” outgoing access option is not assigned then the OA request shall be ignored by the network and the OA status shall be determined according to the OA subscription option. + +OA(I) Outgoing access implicit + +OA Outgoing access allowed + +OCB Outgoing access barred within the CUG + +PCUG Preferential CUG + +*Note 1* — When an illegal index code is received, the outgoing call is rejected. + +*Note 2* — All the user classes are not necessarily supported by all the networks. User classes to be supported are network dependent. + +#### 1.9.4 *FEAs of FE4* + +- 940: The functional entity shall: +- identify a call for a user with CUG service; + - access the incoming CUG control entity (FE5). +- 941: The functional entity shall receive the results of the CUG specific checks from the incoming CUG control entity. +- 942: The functional entity shall: +- store the CUG characteristics as received from FE5; + - transfer the CUG request as received from FE5 simultaneously with the basic call setup request. +- 943: The functional entity shall transfer simultaneously with basic call clearing information flow INFORM 2 REJECT with CUG specific reasons. +- 944: The functional entity shall, in the case of a call towards a PN FE2, provide the capability to receive a CUG-specific rejection of the call from the PN. In this case the requirement is to receive and transfer simultaneously with basic call control information flow CUG specific INFORM 1 REJECT with CUG specific reason. + +#### 1.9.5 *FEAs of FE5* + +- 950: The functional entity shall, according to Table 1-10/Q.85: +- converse the interlock code to CUG index; + - perform validation checks of CUG information of a called user (including the compatibility with the called user class — CUG IA — in case of ordinary incoming call). + +#### 1.9.6 *FEAs of FE6* + +- 960: The functional entity shall receive CUG indication simultaneously with the call SETUP req. ind. and indicating this to the user. + +![A large empty rectangular box, likely a placeholder for a diagram or figure.](a95bbb7c401e0f3ee7e6c1a870f4917c_img.jpg) + +A large empty rectangular box with a thin black border, oriented vertically. It appears to be a placeholder for a diagram or figure related to the technical specification. + +A large empty rectangular box, likely a placeholder for a diagram or figure. + +TABLE 1-10/Q.85 + +#### **CUG checking in incoming side** + +| Called user's class

SEPUP Presentation | Called user is CUG | | | | Called user is not CUG | | +|-----------------------------------------------|--------------------------|-----|-----------------------------|-----|------------------------|--| +| | CUG with or without PCUG | | CUG IA with or without PCUG | | | | +| | No ICB | ICB | No ICB | ICB | | | +| CUG | M (1) | REJ | M (1) | REJ | REJ | | +| | NM REJ | | NM REJ | | | | +| CUG and OA (Note 8) | M (1) | REJ | M (2) | 3 | (3) | | +| | NM REJ | | NM (3) | | | | +| Ordinary | REJ | | (3) | | (3) a) | | + +a) Covered by SDLs + +IA Incoming access + +OA Outgoing access + +*Note 1* — Since CUG OA user class is not concerned in the incoming case, it is not shown in the above list. It shall be regarded that CUG OA user class is the same as user class CUG, and CUG OA/IA is the same as user class CUG IA in this table. + +Most of the table is performed in FE5. + +*Note 2* — (1)-(3) shows CUG parameter to be used in the SETUP to the called user. + +- (1) CUG index; +- (2) CUG + OA (index + OA mark), this is a national option; +- (3) No CUG (ordinary call). + +*Note 3* — ICB means incoming calls barred within the CUG. The interpretation logic is changed in this case as shown in each column in the table. For example: + +| | | +|--------|-----| +| No ICB | ICB | +| M (1) | REJ | + +This means that when the interlock codes are matched and no ICB is applied for the CUG, then (1) is used. However, when ICB is applied for the CUG, the incoming call is rejected even if interlock codes are matched. + +*Note 4* — M means that the interlock code is matched with the CUG of the called user. + +*Note 5* — NM means “not matched”. + +*Note 6* — REJ means that an incoming call is rejected. + +*Note 7* — Interpretation logic, e.g.: + +| | +|-----| +| M | +| (3) | + +means that when matched with CUG, no CUG selection facility field is set in the SETUP to the called user. + +*Note 8* — This may be supported as a national option. + +TABLE 1-11/Q.85 + +| Scenarios | FE1 | FE2 | FE3 | FE4 | FE5 | FE6 | +|------------|-----|---------------------------------------------------------------------------------|-------------------------------|---------------------------|-------------------------------|-----| +| Scenario 1 | TE | LE1 | LE1 | LE2 | LE2 | TE | +| Scenario 2 | TE | LE1 | DB1 | LE2 | DB1 | TE | +| Scenario 3 | TE | LE1 | DB1 | LE2 | DB2 | TE | +| Scenario 4 | TE | <— — — — PN — —
— —>
&
LE1 LE1 LE2 LE2 | | | | TE | +| Scenario 5 | TE | LE1 LE1 LE2 LE2
&
<— — — — PN — —
— —> | | | | TE | +| Scenario 6 | TE | <— — — — PN — —
— —>
&
LE1 LE1 LE2 LE2
&
<— — — — PN — —
— —> | | | | TE | +| Scenario 7 | TE | LE1
&
OIC | LE1/DB1

OIC | OIC

LE2 | OIC

LE2/DB2 | TE | +| Scenario 8 | TE | LE1
&
OIC
&
IIC | LE1/DB1

OIC

IIC | OIC

IIC

LE2 | OIC

IIC

LE2/DB2 | TE | + +DB Data base. + +IIC Incoming international centre. + +LE Local exchange. + +OIC Outgoing international centre. + +TE Terminal equipment. + +*Note* — The symbol “&” represents the chaining of CUG domains of the public and private ISDN or two public ISDNs + +The network scenarios 1, 4, 5 and 6 represent the decentralized approach of the CUG service implementation. + +The network scenario 2 describes the fully centralized approach with a unique data base. + +The network scenario 3 describes a centralized approach with two data bases (DB1 and DB2). + +Network scenarios 7 and 8 — The translation between national and international CUG interlock codes is the responsibility of the country not accepting international CUG codes in its network. + +## 3 Multi-Level Precedence and Preemption (MLPP) (revised 1992) + +### 3.1 *Scope* + +This Recommendation defines the stage 2 for the Multi-Level Precedence and Preemption (MLPP) supplementary service of the integrated service digital network (ISDN) as provided by public telecommunications operators. Stage 2 identifies the functional capabilities and the information flows needed to support the service description. The stage 2 description also identifies user operations not directly associated with a call (see Recommendation I.130 [1]). + +This Recommendation is defined according to the methodology specified in Recommendation Q.65 [2]. + +This Recommendation does not formally describe the relationship between this supplementary service and the basic call but, where possible, this information is included for guidance. + +In addition, this Recommendation does not specify the requirements where the service is provided to the user via a private ISDN. This Recommendation does not specify the allocation of defined functional entities within a private ISDN; however, it does define which functional entities may be allocated to a private ISDN. + +This Recommendation does not specify the additional requirements where the service is provided to the user via a telecommunication network that is not an ISDN. + +This Recommendation is applicable to the stage 3 Recommendations for the ISDN MLPP supplementary service. The term “stage 3” is defined in Recommendation I.130 [1]. + +### 3.2 *References* + +These following references are applicable: + +- [1] CCITT Rec. I.130 *Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN*, 1988 +- [2] CCITT Rec. Q.65 *Stage 2 of the method for the characterization of services supported by an ISDN*, 1988. +- [3] CCITT Rec. Q.711) *ISDN 64 kbit/s circuit mode switched bearer services*, 1993. +- [4] CCITT Rec. I.210 *Principles of telecommunication services supported by an ISDN and the means to describe them*, 1988. +- [5] CCITT Rec. I.255.3 *Multi-Level Precedence and Preemption service (MLPP)*, 1990. + +### 3.3 *Definitions* + +For the purpose of this Recommendation, the following definitions apply: + +#### **MLPP call** + +A call that has a precedence level established and is either being setup or is setup. Only MLPP subscribers can generate MLPP calls, which are identified by a precedence level. Calls from non-MLPP subscribers will not carry a precedence level and shall not be preempted. + +#### **preemptable circuit** + +A circuit that is active with or reserved for an MLPP call: + +- 1) within the same domain as the preempting call; and +- 2) with a lower precedence than the preempting call. A busy or reserved circuit for which a precedence level has not been specified is not a preemptable circuit. + +--- + +1) Recommendation Q.71 will be submitted for approval at the CCITT Plenary Assembly in March, 1993. + +#### **precedence call** + +A call with precedence level higher than the lowest level of precedence. + +#### **users A and B** + +Parties of the MLPP call A-B for scenarios involving preemption in the network. User A is also a party of the MLPP call A-D for scenarios depicting preemption in the user access area. + +#### **user C** + +Calling party of the preempting higher precedence call. + +#### **user D** + +Called party of the preempting higher precedence call from user C. User D is also a party of the MLPP call A-D for preemption in the user access area scenarios. + +#### **LFB req. ind.** + +An optional information flow used to find out whether network resources are available to support the higher precedence call. Available resources include ideal circuits and circuits used for lower precedence calls. This information flow will provide call path reservation. + +#### **LFB resp. conf.** + +The response information flow used to indicate the status of the called party and network resources. Possible responses are: available and unavailable. Available means that network and called party resources are available to support the higher precedence call. The called party is available if it is either: + +- 1) not busy; +- 2) busy with a call of lower precedence with preemptable access resources; +- 3) busy with a call of equal or higher precedence with call completion or call offering services (i.e. Call Waiting or Call Forwarding Busy) or an alternate party, or +- 4) busy with access resources non-preemptable with call completion services or an alternate party. + +Unavailable means that: + +- 1) network resources are not available to support the higher precedence call; +- 2) the called party is busy with a call of equal or higher precedence and no call completion or call offering services or an alternate party are available, or +- 3) the called party is busy with non-preemptable resources and no call completion services or an alternate party are available. + +#### **response timer $T_K$** + +This is started when the service provider notifies the called user of a precedence call (for example, this would be the preemption notification if preemption occurs at the user interface). This timer establishes the time that the called party of the precedence call has to accept the precedence call from the calling party of the precedence call. The length of this timer is in the range of 4 to 30 seconds. + +#### **timer $T_L$** + +A timer that is started when a functional entity sends an LFB information flow. This timer establishes the amount of time the network has to complete and LFB search for network and access resources before preemption is initiated (if the functional entity initiated the search) or an LFB resp. conf. "available" is returned from the previous FE. The expected value of this timer is in the range of 5 to 20 seconds. + +#### **preempted** + +Notification sent to the parties of the preempted calls. + +#### **preempt notification** + +Notification of preemption at the user interface sent to the preempted user (e.g. user D) to release the existing call and to reserve the interface for the preempting call. + +### 3.4 *Symbols and abbreviations* + +| | | +|------|--------------------------------------------------| +| CC | Call control | +| CCA | Call control agent | +| FE | Functional entity | +| FEA | Functional entity action | +| ISDN | Integrated services digital network | +| LE | Local exchange | +| LFB | Look-ahead-for-busy | +| MLPP | Multi-level precedence and preemption | +| PNX | Private network exchange | +| TE | Terminal equipment | +| TR | Transit exchange (same as Intermediate exchange) | + +### 3.5 *Description* + +The description for this service can be found in Recommendation I.255.3 [5]. + +The MLPP service provides a prioritized call handling service. The service has two parts: precedence and preemption. Precedence involves assigning a priority level to a call. Preemption involves the seizing of busy resources, which are in use by call(s) of lower precedence, by a higher precedence call in the absence of idle resources. + +Precedence provides preferred handling of MLPP services requests. It involves assigning and validating priority levels to calls and prioritized treatment of MLPP service requests (e.g. with respect to interactions with other supplementary services such as Call Waiting). + +Preemption may take one of two forms. First, the called party may be busy with a lower precedence call that must be preempted in favour of completing the higher precedence call from the calling party. Second, the network resources may be busy with calls, some of which are of lower precedence than the call requested by the calling party. One or more of these lower precedence calls must be preempted to complete the higher precedence call. + +The MLPP service, as described in this document, only applies within a domain of the MLPP service. An MLPP domain consists of the network and access resources that are in use by a set of MLPP subscribers at any given time. These resources are marked by a precedence level and a domain identification during establishment of an MLPP call. Connections and resources that are in use by MLPP subscribers may only be preempted by calls from MLPP users belonging to the same domain that carry a higher precedence levels. + +MLPP users may receive calls from non-MLPP users. These non-MLPP calls will not carry a precedence level and, as a result, cannot be preempted. Calls from MLPP subscribers to non-MLPP users may not be preempted after receipt of the REPORT req. ind. from the destination. The destination will determine the status of the called party (MLPP or non-MLPP) and should insert an indication in the REPORT req. ind. Upon receipt of the REPORT req. ind. the originating and intermediate MLPP functional entities should reclassify the call as non-MLPP if the called party is a non-MLPP user. + +As a service provider option, before preemption of a lower precedence call, a network may provide a search and reservation of network resources. This procedure utilizes a look-ahead-for-busy (LFB) function to ensure that network and called user resources are available to complete the call prior to preemption. + +### 3.6 Derivation of the functional model + +#### 3.6.1 Functional model description + +The functional model for the MLPP supplementary service is shown in Figure 3-1/Q.85. For clarity, both user A (FE2) and user C (FE1) have a relationship with the same FE. + +Note that all the users shown in this description are MLPP users that may generate MLPP calls and may be preempted. + +The functionalities in the model are described in the following sections with emphasis on functions required for the MLPP service. Relationships $r_a$ to $r_f$ , etc., between the functional entities characterize the information flows required to process calls (establish, manipulate, and release) and MLPP service requests. + +![Functional model for the MLPP service diagram showing functional entities FE1 through FE7 and their relationships.](6470d350326789d5306eabcb76533951_img.jpg) + +``` + +graph LR + UserC["(User C)"] --- FE1[FE1] + UserA["(User A)"] --- FE2[FE2] + FE1 --- ra((ra)) --- FE3[FE3] + FE2 --- rb((rb)) --- FE3 + FE3 --- rc((rc)) --- FE4[FE4] + FE4 --- re((re)) --- FE6[FE6] + FE4 --- rd((rd)) --- FE5[FE5] + FE6 --- rf((rf)) --- FE7[FE7] + FE5 --- UserB["(User B)"] + FE7 --- UserD["(User D)"] + FE7 --- T1131460-91[T1131460-91] + +``` + +FE Functional entity + +Functional model for the MLPP service diagram showing functional entities FE1 through FE7 and their relationships. + +FIGURE 3-1/Q.85 + +##### Functional model for the MLPP service + +The expanded functional model in Figure 3-1a/Q.85 is a concatenation of the functional model shown in Figure 3-1/Q.85. This model is used to show that multiple lower precedence calls may be preempted to complete the higher precedence call (C-D). In this case, the two lower precedence calls are the calls A1-B1 and A2-B2. + +#### 3.6.2 Description of the functional entities + +The functional entities required by the MLPP supplementary service in addition to those of the basic call, are described in the following sections. + +##### 3.6.2.1 FE1 + +FE1 serves user C by initiating service requests, relaying MLPP indicators, and maintaining the call state information. + +##### 3.6.2.2 FE2 + +FE2 serves user A, who is on an MLPP call with user B or with user D. FE2 relays MLPP indicators and maintains the call state information. + +![Expanded functional model diagram showing a sequence of Functional Elements (FE1 to FE7) and their connections. FE1 and FE2 (User A1) connect to FE3 via links r_a and r_b. FE3 connects to FE4 via link r_c. FE4 connects to FE3 via link r_c, and to FE5 (User B1) via link r_d. FE3 connects to FE4 via link r_c, and to FE5 (User B2) via link r_d. FE4 connects to FE6 via link r_e. FE6 connects to FE7 (User D) via link r_f. FE7 is labeled T1131470-91.](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +``` + +graph LR + UserA1[User A1] --- FE1[FE1] + UserA1 --- FE2[FE2] + FE1 -- r_a --> FE3[FE3] + FE2 -- r_b --> FE3 + FE3 -- r_c --> FE4_1[FE4] + FE4_1 -- r_c --> FE3 + FE4_1 -- r_d --> UserB1[User B1] + FE3 -- r_c --> FE4_2[FE4] + FE4_2 -- r_d --> UserB2[User B2] + FE4_2 -- r_e --> FE6[FE6] + FE6 -- r_f --> FE7[FE7] + FE7 --- T1131470_91[T1131470-91] + UserA2[User A2] --- FE2_2[FE2] + FE2_2 -- r_b --> FE3 + +``` + +Expanded functional model diagram showing a sequence of Functional Elements (FE1 to FE7) and their connections. FE1 and FE2 (User A1) connect to FE3 via links r\_a and r\_b. FE3 connects to FE4 via link r\_c. FE4 connects to FE3 via link r\_c, and to FE5 (User B1) via link r\_d. FE3 connects to FE4 via link r\_c, and to FE5 (User B2) via link r\_d. FE4 connects to FE6 via link r\_e. FE6 connects to FE7 (User D) via link r\_f. FE7 is labeled T1131470-91. + +FIGURE 3-1a/Q.85 + +##### Expanded functional model + +##### 3.6.2.3 FE3 + +FE3 provides validation of the user C requested precedence level and prioritized treatment of MLPP service requests based on the precedence levels. FE3 also initiates preemption of network resources, when path congestion is encountered, in order to connect a higher precedence call. When LFB is utilized as a network provider option, FE3 initiates the LFB search, prior to preemption, and provides the appropriate response to the result of this search. + +##### 3.6.2.4 FE4 + +FE4 may preempt network resources, when it receives a SETUP request from FE3, in order to connect the higher precedence call. When LFB is utilized as a network provider option, FE4 can perform search and reservation functions as requested by FE3. In addition, if no LFB search was conducted by FE3 for this call, FE4 may initiate an LFB search (if preemption is required). + +##### 3.6.2.5 FE5 + +FE5 serves user B, who may be on an MLPP call with user A. FE5 relays MLPP indicators and maintains the call state information. + +##### 3.6.2.6 FE6 + +FE6 supports preemption of the access resources to FE7, when required. When LFB is supported, FE6 supports reservation of network resources when requested by FE4 and relays user status information to FE4 during LFB search and reservation procedures. + +##### 3.6.2.7 FE7 + +FE7 serves user D, who receives an MLPP call from user C. FE7 relays MLPP indicators, supports preemption of access resources to FE6, and maintains the call state information. + +#### 3.6.3 Relationship with a basic service + +The relationship with a basic service is shown in Figure 3-2/Q.85. + +![Figure 3-2/Q.85: Relationship with a basic service. This diagram illustrates the information flow between various functional entities (FE) and call control agents (CCA) for four users (A, B, C, D). User C (FE1, CCA) and User A (FE2, CCA) are on the left. User D (FE7, CCA) and User B (FE5, CCA) are on the right. Intermediate nodes include FE3, FE4, FE6, and a standalone CC. Information flows are labeled with 'r' followed by a subscript (r_a, r_b, r_1, r_c, r_e, r_f, r_d, r_2, r_3). A legend defines FE as Functional entity, CC as Call control, and CCA as Call control agent.](692541e65db4dc852988ce77ebb60ce5_img.jpg) + +(User C) + FE1 + CCA + (User A) + FE2 + CCA + FE3 + CC + FE4 + CC + FE6 + CC + FE7 + CCA + (User D) + FE5 + CCA + (User B) + +FE Functional entity + CC Call control + CCA Call control agent + +Figure 3-2/Q.85: Relationship with a basic service. This diagram illustrates the information flow between various functional entities (FE) and call control agents (CCA) for four users (A, B, C, D). User C (FE1, CCA) and User A (FE2, CCA) are on the left. User D (FE7, CCA) and User B (FE5, CCA) are on the right. Intermediate nodes include FE3, FE4, FE6, and a standalone CC. Information flows are labeled with 'r' followed by a subscript (r\_a, r\_b, r\_1, r\_c, r\_e, r\_f, r\_d, r\_2, r\_3). A legend defines FE as Functional entity, CC as Call control, and CCA as Call control agent. + +FIGURE 3-2/Q.85 + +T1131480-91 + +##### Relationship with a basic service + +### 3.7 Information flows + +#### 3.7.1 Information flow diagrams + +This section contains the information flow diagrams of successful sequences for the MLPP service. Note that the basic call procedures are shown only when necessary for the description of the MLPP service (e.g. “SETUP resp. conf.” is not shown in the information flow diagrams). The complete basic call SETUP and RELEASE procedures can be found in Recommendation Q.71 [3]. + +Figure 3-3/Q.85 shows the information flow for successful preemption in the network utilizing the search and reservation (LFB) option. The called party (user D) of the preempting call may or may not be busy with a call of lower precedence than that of the preempting call (from user C to user D). + +Note that if the LFB search and reservation information flow encounters a network that does not support LFB procedures, the LFB gateway exchange will send back an LFB “available” response (since the LFB was capable of reaching the interworking point, it was able to reserve available circuits to that point) to the preemption initiating exchange (FE3). Upon receiving the response, the preemption initiating exchange will invoke preemption and begin call setup. + +The resources that are marked as “path reserved” during the course of the LFB procedures are subject to preemption by higher precedence calls. If reserved resources are preempted, the call must initiate a normal search for ideal or preemptable resources when the SETUP (prec) req. ind. reaches the FE where the reserved resources were preempted. + +Figure 3-4/Q.85 shows the information flow for successful preemption in the network without the search and reservation (LFB) option. Again, the called party (user D) of the preempting call may or may not be busy with a call of lower precedence than that of the preempting call (from user C to user D). + +Figure 3-5/Q.85 shows the information flow for successful preemption in the access area. The called party (user D) of the preempting call is busy with a call of lower precedence (with user A) than that of the preempting call. + +![Sequence diagram showing the information flow for preemption in a network with the LFB option. The diagram involves seven Functional Entities (FE1 to FE7) representing User C, User A, User B, and User D. It details the setup, preemption, and release of calls A-B and C-D, including LFB (Local Forwarding Block) and PREEMPT NOTIFICATION messages.](08dce7ad4c512fdf0c0cde60415fade6_img.jpg) + +**C-D PREEMPTING HIGHER PRECEDENCE LEVEL CALL** + +The diagram illustrates the sequence of events for a call C-D preempting a higher precedence call A-B. The participants are User C (FE1), User A (FE2), User B (FE5), and User D (FE7), with intermediate Functional Entities FE3, FE4, FE6, and FE7. The sequence includes: + +- Setup of Call A-B:** User C sends a **SETUP (prec.) req.** (911) to FE1. FE1 sends a **SETUP (prec.) req. ind.** (911) to FE2. FE2 sends an **LFB** (931) to FE3. FE3 sends an **LFB req. ind.** (941) to FE4. FE4 sends an **LFB req. ind.** (942) to FE6. FE6 sends an **LFB resp. conf.** (961) to FE4. FE4 sends an **LFB** (943) to FE3. FE3 sends a **resp. conf. RELEASE (Note 1)** (933) to FE2. FE2 sends a **req. ind.** (934) to FE3. FE3 sends a **RELEASE resp. conf.** (944) to FE4. FE4 sends a **RELEASE (cause = preempted)** (951) to FE5. FE5 sends a **PREEMPTED ind.** (921) to FE1. FE1 sends a **DISCONNECT (Note 2)** (921) to FE2. FE2 sends a **PREEMPTED ind.** (921) to FE3. FE3 sends a **RELEASE resp. conf.** (945) to FE4. FE4 sends a **RELEASE** (963) to FE6. FE6 sends a **PREEMPT NOTIFICATION** (964) to FE5. FE5 sends a **PREEMPT NOTIFICATION** (971) to FE7. FE7 sends a **PREEMPT NOTIFICATION** (972) to FE5. FE5 sends a **resp. conf. SETUP (prec.)** (967) to FE4. FE4 sends a **req. ind.** (968) to FE6. FE6 sends a **REPORT** (968) to FE4. FE4 sends a **REPORT** (946) to FE3. FE3 sends a **REPORT** (935) to FE2. FE2 sends a **REPORT** (935) to FE1. FE1 sends a **REPORT ind.** (935) to the network. + +T1131490-91 + +Sequence diagram showing the information flow for preemption in a network with the LFB option. The diagram involves seven Functional Entities (FE1 to FE7) representing User C, User A, User B, and User D. It details the setup, preemption, and release of calls A-B and C-D, including LFB (Local Forwarding Block) and PREEMPT NOTIFICATION messages. + +*Note 1* – Cause = Preempted, circuit reserved for re-use. + +*Note 2* – Cause = Preempted, circuit released not for re-use because it was used for the call A-B and not used for the preempting call (call C-D). + +FIGURE 3-3/Q.85 + +**Information flow for preemption in the network with the LFB option** + +![Sequence diagram showing call preemption between User C (FE1), User A (FE2), User B (FE5), and User D (FE7) through intermediate functional entities FE3, FE4, and FE6. It shows the transition from an existing A-B MLPP call to a new C-D call via preemption signaling including SETUP (prec.), RELEASE, DISCONNECT, PREEMPTED, PREEMPT NOTIF., and REPORT messages.](7ae836e598020d937ed1478c2ef13025_img.jpg) + +**C-D PREEMPTING HIGHER PRECEDENCE LEVEL CALL** + +``` + +sequenceDiagram + participant C as User C FE1 + participant A as User A FE2 + participant FE3 as FE3 + participant FE4 as FE4 + participant FE6 as FE6 + participant B as User B FE5 + participant D as User D FE7 + + Note over A, B: A-B MLPP CALL + C->>FE3: SETUP (prec.) req. (911) + FE3->>A: SETUP (prec.) req. ind. (931) + FE3->>FE4: RELEASE (Note 1) req. ind. (934) + A->>FE3: DISCONNECT (Note 2) req. ind. + FE3->>A: PREEMPTED ind. (921) + FE4->>FE6: RELEASE (cause = preempted) req. ind. (944) + FE6->>B: RELEASE (cause = preempted) req. ind. (951) + B->>FE6: RELEASE resp. conf. + FE6->>FE4: RELEASE resp. conf. + FE4->>FE3: RELEASE resp. conf. + FE3->>FE4: SETUP (prec.) req. ind. (945) + FE4->>FE6: SETUP (prec.) req. ind. (963) + FE6->>B: PREEMPT NOTIF. req. ind. (964) + FE6->>D: PREEMPT NOTIFICATION ind. (971) + D->>FE6: PREEMPT NOTIFICATION resp. + B->>FE6: PREEMPT NOTIF. resp. conf. + FE6->>FE4: REPORT req. ind. (968) + FE6->>D: SETUP (prec.) req. ind. (969) + D->>FE6: SETUP (prec.) ind. (972) + FE4->>FE3: REPORT req. ind. (946) + FE3->>C: REPORT req. ind. (935) + C->>FE3: REPORT ind. + +``` + +T1131500-91 + +Sequence diagram showing call preemption between User C (FE1), User A (FE2), User B (FE5), and User D (FE7) through intermediate functional entities FE3, FE4, and FE6. It shows the transition from an existing A-B MLPP call to a new C-D call via preemption signaling including SETUP (prec.), RELEASE, DISCONNECT, PREEMPTED, PREEMPT NOTIF., and REPORT messages. + +*Note 1* – Cause = Preempted, circuit reserved for re-use. + +*Note 2* – Cause = Preempted, circuit released not for re-used because it was used for the call A-B and not used for the preempting call (call C-D). + +FIGURE 3-4/Q.85 + +##### **Information flow for preemption in the network without the LFB option** + +If the called user (user D) is not busy and does not respond to the precedence call setup indication within timer $T_K$ and an alternate party is subscribed to by the called party, the service provider will initiate alternate party diversion. In addition, if the called party (user D) is busy on a call of equal or higher precedence or is busy with non-preemptable access resources, an alternate party is subscribed to by the called party, and no call completion or call offering services (i.e. Call Waiting or Call Forwarding Busy) are available, the service provider will initiate alternate party diversion. + +#### **3.7.2 Definition of individual information flows** + +##### **3.7.2.1 Relationship $r_a$** + +In addition to the basic call requirements, the contents of the SETUP (prec) information flow shall contain the information as shown in Table 3-1/Q.85. + +![Sequence diagram FIGURE 3-5/Q.85 showing information flow for preemption in the user access area. The diagram involves User C (FE1), User A (FE2, FE3), and User D (FE4, FE6, FE7). It shows an existing 'A-D MLPP CALL' being preempted by a new 'SETUP (prec.)' request from User C. Key messages include SETUP (prec.) req. (911), SETUP (prec.) req. ind. (931), SETUP (prec.) req. ind. (963, 965, 966), RELEASE req. ind. (964), DISCONNECT (cause = preempted) (921), PREEMPT NOTIFICATION req. ind. (971), PREEMPT NOTIFICATION resp. conf. (969), RELEASE resp. conf., SETUP (prec.) req. ind. (972), REPORT req. ind. (968, 946, 935), and REPORT ind.](f9c64800d9bace9b4315646d1057be3c_img.jpg) + +C-D PREEMPTING HIGHER PRECEDENCE LEVEL CALL + +T1131510-91 + +Sequence diagram FIGURE 3-5/Q.85 showing information flow for preemption in the user access area. The diagram involves User C (FE1), User A (FE2, FE3), and User D (FE4, FE6, FE7). It shows an existing 'A-D MLPP CALL' being preempted by a new 'SETUP (prec.)' request from User C. Key messages include SETUP (prec.) req. (911), SETUP (prec.) req. ind. (931), SETUP (prec.) req. ind. (963, 965, 966), RELEASE req. ind. (964), DISCONNECT (cause = preempted) (921), PREEMPT NOTIFICATION req. ind. (971), PREEMPT NOTIFICATION resp. conf. (969), RELEASE resp. conf., SETUP (prec.) req. ind. (972), REPORT req. ind. (968, 946, 935), and REPORT ind. + +FIGURE 3-5/Q.85 + +##### **Information flow for preemption in the user access area** + +TABLE 3-1/Q.85 + +##### **Relationship $r_a$ SETUP (prec)** + +| Parameter | Allowed value | req. ind. | +|------------------|---------------------------------------------------------------------------------|--------------------| +| Precedence level | 4 (routine)
3 (priority)
2 (immediate)
1 (flash)
0 (flash override) | Optional
(Note) | + +*Note* – If the user does not specify a precedence level, the network will assign precedence level 4 (routine) for this call. + +Relationship $r_a$ shall also support the REPORT information flow which is defined in Table 3-5/Q.85. + +##### 3.7.2.2 Relationship $r_b$ + +In addition to the basic call requirements, the contents of the DISCONNECT information flow shall contain the information as shown in Table 3-2/Q.85. + +TABLE 3-2/Q.85 + +###### DISCONNECT contents + +| Parameter | Allowed value | req. ind. | +|-----------|--------------------------------------|-----------| +| Cause | Preempted
Precedence call blocked | Mandatory | + +##### 3.7.2.3 Relationship $r_c$ + +Relationship $r_c$ shall support the LFB, SETUP (prec), REPORT, and RELEASE information flows. The LFB, SETUP (prec), REPORT and RELEASE information flows are defined in Tables 3-3/Q.85 to 3-6/Q.85. + +###### 3.7.2.3.1 Contents of LFB + +In addition to the basic call setup information flow requirements, the contents of the LFB information shall contain the information as defined in Table 3-3/Q.85. + +TABLE 3-3/Q.85 + +###### LFB contents + +| Parameter | Allowed value | req. ind. | resp. conf. | +|-----------------------------|---------------------------------------------------------------------------------|-----------|-------------| +| Precedence level | 4 (routine)
3 (priority)
2 (immediate)
1 (flash)
0 (flash override) | Mandatory | Mandatory | +| MLPP domain | | Mandatory | | +| Network/Called party status | Available
Unavailable | | | + +###### 3.7.2.3.2 Contents of SETUP (prec) req. ind. + +In addition to the basic call requirements, the contents of the SETUP (prec) information flow shall contain the information as defined in Table 3-4/Q.85. + +###### 3.7.2.3.3 Contents of REPORT + +In addition to the basic call requirements, the contents of the REPORT information flow shall contain the information contained in Table 3-5/Q.85. + +TABLE 3-4/Q.85 + +###### **SETUP (prec) contents** + +| Parameter | Allowed value | req. ind. | +|------------------|---------------------------------------------------------------------------------|-----------| +| Precedence level | 4 (routine)
3 (priority)
2 (immediate)
1 (flash)
0 (flash override) | Mandatory | +| MLPP domain | | Mandatory | +| LFB indicator | LFB Allowed
LFB Not Allowed
Path reserved | Mandatory | + +TABLE 3-5/Q.85 + +###### **REPORT contents** + +| Parameter | Allowed value | req. ind. | +|----------------|----------------------------|---------------------| +| MLPP indicator | MLPP user
Non-MLPP user | Mandatory
(Note) | + +*Note* – The MLPP indicator is not required for $r_f$ . + +###### 3.7.2.3.4 *Contents of RELEASE* + +TABLE 3-6/Q.85 + +###### **RELEASE contents** + +| Parameter | Allowed value | req. ind. | +|-----------|--------------------------------------|-----------| +| Cause | Preempted
Precedence call blocked | Mandatory | + +##### 3.7.2.4 *Relationship $r_d$* + +Relationship $r_d$ shall support the RELEASE information flow as defined in Table 3-6/Q.85. + +##### 3.7.2.5 *Relationship $r_e$* + +Relationship $r_e$ shall support the LFB, SETUP (prec), REPORT, and RELEASE information flows as defined in Tables 3-3/Q.85, 3-4/Q.85, 3-5/Q.85, and 3-6/Q.85 respectively. + +##### 3.7.2.6 *Relationship rf* + +Relationship rf shall support the SETUP (prec), REPORT, and PREEMPT NOTIFICATION information flows. The SETUP (prec) information flow is defined in Table 3-4/Q.85. The PREEMPT NOTIFICATION is as defined in § 3.3. Note that there is no parameter included in this PREEMPT NOTIFICATION. The REPORT information flow is defined in Table 3-5/Q.85. + +### 3.8 *SDL diagrams for functional entities* + +The following contains the SDLs for the functional entities as defined in Figures 3-1/Q.85 and 3-2/Q.85. These SDLs reflect preemption in the network and at the user-network interface for networks with and without the LFB option. + +#### 3.8.1 *SDLs for FE1* + +Figure 3-6/Q.85 contains the SDL for MLPP call setup procedures for FE1. + +#### 3.8.2 *SDLs for FE2* + +Figure 3-7/Q.85 contains the SDL for MLPP call preempted notification procedures for FE2. + +#### 3.8.3 *SDLs for FE3* + +Figure 3-8/Q.85 contains the SDL for MLPP call setup, preemption, and LFB procedures, for FE3. It should be noted that the LFB procedures are only initiated once per call, since multiple LFB procedures could greatly delay call setup. In addition, the release (preemption) procedures for the call A-B are only shown for this FE, since normal call release procedures are used to release the call once preemption is initiated by FE3. The only exception to this is preemption indications from the FEs that directly serve the users (i.e. FE1, FE2, FE5, and FE7). + +#### 3.8.4 *SDLs for FE4* + +The SDL for MLPP call setup, preemption, LFB initiation, and LFB continuation procedures for FE4 is given in Figure 3-9/Q.85. It should be noted that the LFB initiation procedures will only apply if no LFB operation has been performed at FE3. + +#### 3.8.5 *SDLs for FE5* + +Figure 3-11/Q.85 contains the SDL for MLPP call preempted notification procedures for FE5. + +#### 3.8.6 *SDLs for FE6* + +The SDL diagram for MLPP call setup, preemption, and LFB procedures at FE6 are shown in Figure 3-10/Q.85. + +#### 3.8.7 *SDLs for FE7* + +Figure 3-12/Q.85 contains the SDL for MLPP call preemption and precedence call setup procedures for FE7. + +### 3.9 *Functional entity actions (FEAs)* + +Functional entities are assumed to have the basic capabilities required to properly perform their assigned functions in the ISDN (e.g. synchronism, signalling capabilities, etc.). In addition, the actions that occur at the functional entities during call processing stages for providing the MLPP service described in this Recommendation, have been given reference numbers and brief descriptions. The reference numbers are shown on the information flow diagrams (Figures 3-2/Q.85 to 3-4/Q.85). + +![Flowchart for FE1 – Incoming MLPP call from user. It shows a sequence: MLPP 1 (circle) points to a rectangle 'Insert precedence level into call setup'. A bracket labeled '911' points to this rectangle. The rectangle points to MLPP 2 (circle). Below MLPP 2 is the text 'T1131520-91'.](77959075c823bb5169480d7b8ff82a63_img.jpg) + +``` + +graph TD + MLPP1((MLPP 1)) --> Box[Insert precedence level into call setup] + 911[911] -.-> Box + Box --> MLPP2((MLPP 2)) + MLPP2 --- T1131520_91[T1131520-91] + +``` + +Flowchart for FE1 – Incoming MLPP call from user. It shows a sequence: MLPP 1 (circle) points to a rectangle 'Insert precedence level into call setup'. A bracket labeled '911' points to this rectangle. The rectangle points to MLPP 2 (circle). Below MLPP 2 is the text 'T1131520-91'. + +*Note* – MLPP 1 and MLPP 2 break the basic call between connectors S1/1 and S1/2 (see Recommendation Q.71 [3]). + +FIGURE 3-6/Q.85 + +#### **FE1 – Incoming MLPP call from user** + +![Flowchart for FE2 – Preempted notification to user. It starts with MLPP 3 (circle) pointing to a diamond 'Preempted indicator?'. A bracket labeled '921' points to the diamond. The 'No' path leads to MLPP 4 (circle). The 'Yes' path leads to a hexagon 'PREEMPTED ind.'. A bracket labeled '921' points to this hexagon. The hexagon points to MLPP 5 (circle). Below MLPP 5 is the text 'T1131530-91'.](b58cedaf15ad4f0edee5621820865ccc_img.jpg) + +``` + +graph TD + MLPP3((MLPP 3)) --> Diamond{Preempted indicator?} + 921[921] -.-> Diamond + Diamond -- No --> MLPP4((MLPP 4)) + Diamond -- Yes --> Hexagon{{PREEMPTED ind.}} + 921[921] -.-> Hexagon + Hexagon --> MLPP5((MLPP 5)) + MLPP5 --- T1131530_91[T1131530-91] + +``` + +Flowchart for FE2 – Preempted notification to user. It starts with MLPP 3 (circle) pointing to a diamond 'Preempted indicator?'. A bracket labeled '921' points to the diamond. The 'No' path leads to MLPP 4 (circle). The 'Yes' path leads to a hexagon 'PREEMPTED ind.'. A bracket labeled '921' points to this hexagon. The hexagon points to MLPP 5 (circle). Below MLPP 5 is the text 'T1131530-91'. + +*Note* – MLPP 3, MLPP 4 and MLPP 5 break the basic call between connectors S1/15, S1/16 and S1/MLPP 5 or S5/14, S5/15 and S5/16 (see Recommendation Q.71 [3]). + +FIGURE 3-7/Q.85 + +#### **FE2 – Preempted notification to user** + +![Flowchart for FE3 - Incoming MLPP call from FE1](5eb69662cc4fa7d0d49b4eb22951c204_img.jpg) + +``` + +graph TD + Start((MLPP 6a)) --> D1{MLPP call?} + D1 -- No --> C1((MLPP 6b)) + D1 -- Yes --> D2{Is precedence level valid?} + D2 -- No --> C1 + D2 -- Yes --> B((B)) + B --> D3{Is idle circuit available?} + D3 -- Yes --> A((A)) + A --> P1[Mark circuit to FE4 busy at selected precedence level] + P1 --> P2[Insert precedence level in SETUP] + P2 --> C2((MLPP 8b)) + D3 -- No --> D4{Is call a precedence call?} + D4 -- No --> C3((MLPP 7)) + D4 -- Yes --> P3[Search for lowest precedence pre-emptable circuit to FE4] + P3 --> D5{Preemptable circuit to FE4 found?} + D5 -- No --> D((D)) + D --> P4[DISCONNECT req. ind. precedence call blocked] + P4 --> C2 + D5 -- Yes --> D6{LFB allowed?} + D6 -- No --> C((C)) + D6 -- Yes --> F((F)) + +``` + +Flowchart for FE3 - Incoming MLPP call from FE1 + +931 + +3 + +931 + +931 + +931 + +931 + +LFB allowed if +(1) network supports LFB, +(2) LFB not utilized previously for this call, and +(3) service provider allows LFB for this call + +3 + +931 + +3 + +931 +If FE3 is a TR, a RELEASE req. ind. shall be sent instead of a DISCONNECT req. ind. + +2 + +3 + +T1131540-91 + +*Note* – MLPP 6 and MLPP 7 enter the basic call at connector S2/6 (see Recommendation Q.71 [3]). +MLPP 6a and MLPP 6b break the basic call between connectors S2/17 and S2/18 (see Recommendation Q.71 [3]). +MLPP 8b enters the basic call at connector S2/10 (see Recommendation Q.71 [3]). + +FIGURE 3-8/Q.85 (sheet 1 of 3) + +**FE3 – Incoming MLPP call from FE1** + +38 + +**Recommendation Q.85** + +![Flowchart for FE3 - Release and preemption of call A-B. The process starts with a 'Release circuit to FE4' action leading to connector C. From C, the flow goes to 'Reserve circuit to FE4 at selected precedence level' (934). This leads to a decision diamond: 'DISCONNECT req. ind. (with cause = preempted, not for re-use to FE2)'. A note indicates that if FE3 is a TR, a RELEASE req. ind. shall be sent instead of a DISCONNECT req. ind. Connector 9 leads to this diamond. The diamond leads to 'RELEASE req. ind. (reserved for re-use circuit to FE4)' (934), which then leads to 'Normal call release' (934) with a note 'With indication of preemption'. This leads to 'RELEASE resp. conf. (from FE4)' (934), then 'Circuit to FE4 marked busy at precedence level' (934), and finally 'Insert precedence level in SETUP'. This sequence leads to connector MLPP 9b. A side path from connector 9 leads to a decision diamond: 'Called party MLPP user?'. If 'Yes', it leads to connector MLPP 9a. If 'No', it leads to 'Reclassify resources as normal call' (935), which then leads to connector MLPP 9a. Reference T1131550-91 is noted near the 'Reclassify' step.](9a5927586a691c4908aa2cf98bd47ebb_img.jpg) + +``` + +graph TD + C((C)) -- "Release circuit to FE4" --> R1[Reserve circuit to FE4 at selected precedence level] + R1 -- 934 --> D1{DISCONNECT req. ind. (with cause = preempted, not for re-use to FE2)} + Note1["If FE3 is a TR, a RELEASE req. ind. shall be sent instead of a DISCONNECT req. ind."] + 9((9)) -- 3 --> D1 + D1 -- 934 --> R2[RELEASE req. ind. (reserved for re-use circuit to FE4)] + Note2["FE3 begins to release switched path to FE4"] + R2 -- 934 --> R3([Normal call release]) + Note3["With indication of preemption"] + R3 -- 934 --> R4[/RELEASE resp. conf. (from FE4)/] + R4 -- 934 --> R5[Circuit to FE4 marked busy at precedence level] + R5 -- 934 --> R6[Insert precedence level in SETUP] + R6 --> MLPP9b((MLPP 9b)) + + 9 --> D2{Called party MLPP user?} + D2 -- Yes --> MLPP9a((MLPP 9a)) + D2 -- No --> R7[Reclassify resources as normal call] + Note4["T1131550-91"] + R7 -- 935 --> MLPP9a + +``` + +Flowchart for FE3 - Release and preemption of call A-B. The process starts with a 'Release circuit to FE4' action leading to connector C. From C, the flow goes to 'Reserve circuit to FE4 at selected precedence level' (934). This leads to a decision diamond: 'DISCONNECT req. ind. (with cause = preempted, not for re-use to FE2)'. A note indicates that if FE3 is a TR, a RELEASE req. ind. shall be sent instead of a DISCONNECT req. ind. Connector 9 leads to this diamond. The diamond leads to 'RELEASE req. ind. (reserved for re-use circuit to FE4)' (934), which then leads to 'Normal call release' (934) with a note 'With indication of preemption'. This leads to 'RELEASE resp. conf. (from FE4)' (934), then 'Circuit to FE4 marked busy at precedence level' (934), and finally 'Insert precedence level in SETUP'. This sequence leads to connector MLPP 9b. A side path from connector 9 leads to a decision diamond: 'Called party MLPP user?'. If 'Yes', it leads to connector MLPP 9a. If 'No', it leads to 'Reclassify resources as normal call' (935), which then leads to connector MLPP 9a. Reference T1131550-91 is noted near the 'Reclassify' step. + +*Note* – MLPP 9 and MLPP 9a break the basic call between connectors S2/19 and S2/20 (see Recommendation Q.71 [3]). +MLPP 9b enters the basic call at connector S2/10 (see Recommendation Q.71 [3]). + +FIGURE 3-8/Q.85 (sheet 2 of 3) + +#### FE3 – Release and preemption of call A-B + + + +![Flowchart for incoming MLPP call from FE3. The process starts with MLPP 9c, leading to a decision 'MLPP call?'. If 'No', it goes to MLPP 9d. If 'Yes', it asks 'Is outgoing circuit reserved?'. If 'No', it goes to MLPP 9d. If 'Yes', it searches for a reserved outgoing circuit. If found, it checks if the reserved circuit is idle. If 'No', it goes to connector G (3). If 'Yes', it checks if an idle circuit is available. If 'No', it goes to connector 1 (2). If 'Yes', it marks the circuit busy at the selected precedence level and inserts the precedence level in the SETUP, leading to MLPP 9e. There are also connectors J (4) and H (4) in the flow.](798679874d1c29f8343506a156c79d7e_img.jpg) + +``` + +graph TD + MLPP9c((MLPP 9c)) --> D1{MLPP call?} + D1 -- No --> MLPP9d((MLPP 9d)) + D1 -- Yes --> D2{Is outgoing circuit reserved?} + D2 -- No --> MLPP9d + D2 -- Yes --> S1[Search for reserved outgoing circuit] + S1 --> D3{Reserved circuit found?} + D3 -- No --> J((J 4)) + J --> D4{Is idle circuit available?} + D4 -- No --> 1((1 2)) + D4 -- Yes --> H((H 4)) + H --> D5{Is reserved circuit idle?} + D5 -- No --> G((G 3)) + D5 -- Yes --> S2[Mark circuit busy at selected precedence level] + S2 --> S3[Insert precedence level in SETUP] + S3 --> MLPP9e((MLPP 9e)) + +``` + +T1131570-91 + +Flowchart for incoming MLPP call from FE3. The process starts with MLPP 9c, leading to a decision 'MLPP call?'. If 'No', it goes to MLPP 9d. If 'Yes', it asks 'Is outgoing circuit reserved?'. If 'No', it goes to MLPP 9d. If 'Yes', it searches for a reserved outgoing circuit. If found, it checks if the reserved circuit is idle. If 'No', it goes to connector G (3). If 'Yes', it checks if an idle circuit is available. If 'No', it goes to connector 1 (2). If 'Yes', it marks the circuit busy at the selected precedence level and inserts the precedence level in the SETUP, leading to MLPP 9e. There are also connectors J (4) and H (4) in the flow. + +*Note* – MLPP 9c and MLPP 9d break the basic call between connectors S3/3 and S3/4 (see Recommendation Q.71 [3]). +MLPP 9e enters the basic call at connector S3/6 (see Recommendation Q.71 [3]). + +FIGURE 3-9/Q.85 (sheet 1 of 6) + +#### **FE4 – Incoming MLPP call from FE3** + +![Flowchart for FE4 – Incoming MLPP call from FE3. The process starts with connector 1, leading to a decision 'Is call a precedence call?'. If 'No', it goes to MLPP 10. If 'Yes', it searches for the lowest precedence preemptable circuit to FE6. If found, it checks if LFB is allowed. If 'No', it goes to connector I. If 'Yes', it goes to connector L. If not found, it goes to connector K, then to a decision 'RELEASE req. ind. to FE3 (precedence call blocked)'. If 'Yes', it goes to MLPP 11. If 'No', it goes to connector 3. The flowchart includes several 945 connector points and a note about LFB conditions.](cbb2d311b20781a595488445ded48d0a_img.jpg) + +``` + +graph TD + 1((1)) --> D1{Is call a precedence call?} + D1 -- No --> MLPP10((MLPP 10)) + D1 -- Yes --> S1[Search for lowest precedence preemptable circuit to FE6] + S1 --> D2{Preemptable circuit found?} + D2 -- No --> K((K)) + D2 -- Yes --> D3{LFB allowed?} + D3 -- No --> I((I)) + D3 -- Yes --> L((L)) + K --> D4{RELEASE req. ind. to FE3 (precedence call blocked)} + D4 -- No --> 3((3)) + D4 -- Yes --> MLPP11((MLPP 11)) + +``` + +945 --- [Is call a precedence call?] + +945 --- [Search for lowest precedence preemptable circuit to FE6] + +945 --- [Preemptable circuit found?] + +945 --- [LFB allowed?] + +LFB allowed if + (1) network supports LFB, + (2) LFB not utilized previously for this call, and + (3) service provider allows LFB for this call + +945 --- [RELEASE req. ind. to FE3 (precedence call blocked)] + +T1131580-91 + +Flowchart for FE4 – Incoming MLPP call from FE3. The process starts with connector 1, leading to a decision 'Is call a precedence call?'. If 'No', it goes to MLPP 10. If 'Yes', it searches for the lowest precedence preemptable circuit to FE6. If found, it checks if LFB is allowed. If 'No', it goes to connector I. If 'Yes', it goes to connector L. If not found, it goes to connector K, then to a decision 'RELEASE req. ind. to FE3 (precedence call blocked)'. If 'Yes', it goes to MLPP 11. If 'No', it goes to connector 3. The flowchart includes several 945 connector points and a note about LFB conditions. + +Note – MLPP 10 and MLPP 11 enter the basic call at connector S4/2 (see Recommendation Q.71 [3]). + +FIGURE 3-9/Q.85 (sheet 2 of 6) +**FE4 – Incoming MLPP call from FE3** + +![Flowchart for FE4 - Release and preemption of an existing call. The process starts with a call to connector I, which releases the circuit to FE5. A circuit is then reserved to FE6 at a selected precedence level. A decision point G (connector 1, 4) leads to a RELEASE request indicator to FE5 (reserved not for re-use). This is followed by a Normal call release process, which includes releasing the preempted call in the backward direction with an indication of preemption. A RELEASE response confirmation is received from FE5. The circuit to FE6 is then marked busy at the selected precedence level, and the precedence level is inserted into the SETUP message. The process then moves to connector MLPP 12b. A side process starting at MLPP 12 checks if the called party is an MLPP user. If Yes, it proceeds to MLPP 12a. If No, it reclassifies resources as a normal call and then proceeds to MLPP 12a. Connector 946 is shown as a reference point for the MLPP 12 and Reclassify steps.](e8e818455bb0d1a6153299a388b94868_img.jpg) + +``` + +graph TD + I((I)) -- "Release circuit to FE5" --> Reserve[Reserve circuit to FE6 at selected precedence level] + Reserve --> G((G)) + G -- "1, 4" --> ReleaseReq{RELEASE req. ind. to FE5 (reserved not for re-use)} + ReleaseReq --> NormalCallRelease([Normal call release]) + NormalCallRelease --> ReleaseResp[/RELEASE resp. conf. from FE5/] + ReleaseResp --> MarkBusy[Circuit to FE6 marked busy at selected precedence level] + MarkBusy --> InsertSetup[Insert precedence level in SETUP] + InsertSetup --> MLPP12b((MLPP 12b)) + + MLPP12((MLPP 12)) --> CalledParty{Called party MLPP user?} + CalledParty -- No --> Reclassify[Reclassify resources as normal call] + Reclassify --> MLPP12a((MLPP 12a)) + CalledParty -- Yes --> MLPP12a + + I -.-> 946a[946] + Reclassify -.-> 946b[946] + +``` + +Including release of the preempted call in the backward direction with indication of preemption to the users on the preempted call + +T1131590-91 + +Flowchart for FE4 - Release and preemption of an existing call. The process starts with a call to connector I, which releases the circuit to FE5. A circuit is then reserved to FE6 at a selected precedence level. A decision point G (connector 1, 4) leads to a RELEASE request indicator to FE5 (reserved not for re-use). This is followed by a Normal call release process, which includes releasing the preempted call in the backward direction with an indication of preemption. A RELEASE response confirmation is received from FE5. The circuit to FE6 is then marked busy at the selected precedence level, and the precedence level is inserted into the SETUP message. The process then moves to connector MLPP 12b. A side process starting at MLPP 12 checks if the called party is an MLPP user. If Yes, it proceeds to MLPP 12a. If No, it reclassifies resources as a normal call and then proceeds to MLPP 12a. Connector 946 is shown as a reference point for the MLPP 12 and Reclassify steps. + +*Note* – MLPP 12 and MLPP 12a break the basic call between connectors S4/5 and S4/6 (see Recommendation Q.71 [3]). +MLPP 12b enters the basic call at connector S3/6 (see Recommendation Q.71 [3]). + +FIGURE 3-9/Q.85 (sheet 3 of 6) +**FE4 – Release and preemption of an existing call** + +![Flowchart of FE4 – LFB initiation procedures. The process starts at node L (2), goes through circuit reservation, sending an LFB request, setting a timer T_L, and waiting for a response. Three outcomes from waiting: unavailable response (leads to reset and unreserve, ending at K), timer expiry, or available response (leads to reset). Both expiry and available response lead to a check if the reserved circuit is available, then if it is idle, leading to exit nodes J, G, or H.](0a42e05c07941450f34e4f7117725834_img.jpg) + +``` + +graph TD + L((L +2)) --> Reserve[Reserve outgoing +circuit to FE6] + Reserve --> LFBReq[/LFB req. ind. +to FE6/] + LFBReq --> SET[SET (Now + +TL – Max., TL)] + SET --> Waiting{{Waiting for +response}} + Waiting --> LFBUnavail[/LFB resp. conf. from +FE6 (with network/ +called user status +of “unavailable”)/] + Waiting --> TLExp[/TL (expires)/] + Waiting --> LFBAvail[/LFB resp. conf. from +FE6 (with network/ +called user status +of “available”)/] + LFBUnavail --> Reset1[Reset (TL)] + Reset1 --> Unreserve[Unreserve incoming +(to FE3) and outgoing +(to FE6) circuits] + Unreserve --> K((K +2)) + TLExp --> Reserved{Reserved +circuit +available?} + LFBAvail --> Reset2[Reset (TL)] + Reset2 --> Reserved + Reserved -- No --> J((J +1)) + Reserved -- Yes --> Idle{Is circuit +idle?} + Idle -- No --> G((G +3)) + Idle -- Yes --> H((H +1)) + Note[Available if not preempted +by a higher precedence +call during the course +of the LFB procedures] -.- Reserved + +``` + +T1131600-91 + +Flowchart of FE4 – LFB initiation procedures. The process starts at node L (2), goes through circuit reservation, sending an LFB request, setting a timer T\_L, and waiting for a response. Three outcomes from waiting: unavailable response (leads to reset and unreserve, ending at K), timer expiry, or available response (leads to reset). Both expiry and available response lead to a check if the reserved circuit is available, then if it is idle, leading to exit nodes J, G, or H. + +FIGURE 3-9/Q.85 (sheet 4 of 6) + +#### **FE4 – LFB initiation procedures** + + + +![Flowchart for FE4 – LFB continuation procedures. The process starts in an 'Idle (waiting for LFB)' state. It receives an 'LFB req. ind. from FE3' (941) and reserves an incoming circuit from FE3 (941). It then searches for a suitable circuit to FE6 (idle or preemptable) (942). A decision is made: 'Suitable circuit found?'. If 'Yes', it reserves an outgoing circuit to FE6 (942), sends an 'LFB req. ind. to FE6' (942), sets a timer (Now + T_L - Max., T_L) (942), and enters a 'Waiting for response' state (942). If 'No', it sends an 'LFB resp. conf. to FE3 (with network/called user status of unavailable)' (942) and unreserves the incoming circuit from FE3 (942), returning to the 'Idle' state. The process ends at connector 2.](38cbce07f83fba6d5a7c46605bd5743f_img.jpg) + +``` + +graph TD + Start([Idle +(waiting for LFB)]) --> InReq[/LFB req. ind. +from FE3/] + InReq --> ReserveIn[Reserve incoming +circuit from FE3] + ReserveIn --> Search[Search for suitable +circuit to FE6 (idle +or preemptable)] + Search --> Found{Suitable +circuit found?} + Found -- Yes --> ReserveOut[Reserve outgoing +circuit to FE6] + ReserveOut --> SendReq[/LFB req. ind. +to FE6/] + SendReq --> SetTimer[Set (Now + +TL - Max., TL)] + SetTimer --> WaitResp([Waiting for +response]) + WaitResp --> Conn2((2)) + Found -- No --> SendConf[/LFB resp. conf. to +FE3 (with network/ +called user status +of "unavailable")/] + SendConf --> UnreserveIn[Unreserve incoming +circuit from FE3] + UnreserveIn --> End([Idle]) + +``` + +6 + +T1131610-91 + +Flowchart for FE4 – LFB continuation procedures. The process starts in an 'Idle (waiting for LFB)' state. It receives an 'LFB req. ind. from FE3' (941) and reserves an incoming circuit from FE3 (941). It then searches for a suitable circuit to FE6 (idle or preemptable) (942). A decision is made: 'Suitable circuit found?'. If 'Yes', it reserves an outgoing circuit to FE6 (942), sends an 'LFB req. ind. to FE6' (942), sets a timer (Now + T\_L - Max., T\_L) (942), and enters a 'Waiting for response' state (942). If 'No', it sends an 'LFB resp. conf. to FE3 (with network/called user status of unavailable)' (942) and unreserves the incoming circuit from FE3 (942), returning to the 'Idle' state. The process ends at connector 2. + +**FE4 – LFB continuation procedures** + +![Flowchart for incoming MLPP call from FE4. The process starts with MLPP 13a, leading to a decision 'MLPP call?'. If 'No', it goes to MLPP 13b. If 'Yes', it goes to a decision 'Called party MLPP user?'. If 'No', it goes to MLPP 13. If 'Yes', it goes to a decision 'Is outgoing circuit idle?'. If 'Yes', it goes to 'Mark circuit to FE7 busy at selected precedence level', then to connector A (2). If 'No', it goes to a decision 'Is call a precedence call?'. If 'No', it goes to MLPP 14. If 'Yes', it goes to a decision 'Is circuit preemptable?'. If 'No', it goes to connector R (3). If 'Yes', it goes to connector S (4). Callouts 963, 964, and 964 are associated with the 'Called party MLPP user?', 'Is outgoing circuit idle?', and 'Is call a precedence call?' decisions respectively. A callout 'Including preemptable access resources' is associated with the 'Is circuit preemptable?' decision.](12c19090355e19922e23044633b9d1ea_img.jpg) + +``` + +graph TD + MLPP13a((MLPP 13a)) --> D1{MLPP call?} + D1 -- No --> MLPP13b((MLPP 13b)) + D1 -- Yes --> D2{Called party MLPP user?} + D2 -- No --> MLPP13((MLPP 13)) + D2 -- Yes --> D3{Is outgoing circuit idle?} + D3 -- Yes --> B1[Mark circuit to FE7 busy at selected precedence level] + B1 --> A2((A 2)) + D3 -- No --> D4{Is call a precedence call?} + D4 -- No --> MLPP14((MLPP 14)) + D4 -- Yes --> D5{Is circuit preemptable?} + D5 -- No --> R3((R 3)) + D5 -- Yes --> S4((S 4)) + +``` + +963 --- D2 + +964 --- D3 + +964 --- D4 + +964 --- D5 + +Including preemptable access resources --- D5 + +T1131630-91 + +Flowchart for incoming MLPP call from FE4. The process starts with MLPP 13a, leading to a decision 'MLPP call?'. If 'No', it goes to MLPP 13b. If 'Yes', it goes to a decision 'Called party MLPP user?'. If 'No', it goes to MLPP 13. If 'Yes', it goes to a decision 'Is outgoing circuit idle?'. If 'Yes', it goes to 'Mark circuit to FE7 busy at selected precedence level', then to connector A (2). If 'No', it goes to a decision 'Is call a precedence call?'. If 'No', it goes to MLPP 14. If 'Yes', it goes to a decision 'Is circuit preemptable?'. If 'No', it goes to connector R (3). If 'Yes', it goes to connector S (4). Callouts 963, 964, and 964 are associated with the 'Called party MLPP user?', 'Is outgoing circuit idle?', and 'Is call a precedence call?' decisions respectively. A callout 'Including preemptable access resources' is associated with the 'Is circuit preemptable?' decision. + +*Note* – MLPP 13 enters the basic call at connector S4/30 (see Recommendation Q.71 [3]). + MLPP 14 enters the basic call at connector S4/2 (see Recommendation Q.71 [3]). + MLPP 13a and MLPP 13b break the basic call between connectors S4/31 and S4/32 (see Recommendation Q.71 [3]). + +FIGURE 3-10/Q.85 (sheet 1 of 5) + +#### **FE6 – Incoming MLPP call from FE4** + +![Flowchart for FE6 – Incoming MLPP call from FE4. The process starts at connector 1, 4 (A), leading to a 'SETUP (prec.) req. ind. to FE7' block (967). A decision 'Is call a precedence call?' (967) follows. If 'No', it goes to 'Waiting for response from FE7' (967). If 'Yes', a second decision 'Alternate party subscribed to?' (967) is made. If 'No', it also goes to 'Waiting for response from FE7'. If 'Yes', a block 'Set (Now + T_K - Max., T_K)' (967) is executed, followed by 'Waiting for response from FE7'. From 'Waiting for response from FE7', the flow splits into two paths. The left path is triggered by 'T_K expires' (964), leading to 'Divert call to alternate party' (964) and then 'MLPP call setup to alternate party' (964). The right path is triggered by 'REPORT req. ind. from FE7' (968), leading to 'RESET T_K', then 'Insert MLPP indicator in REPORT req. ind.' (968), and finally to connector 'MLPP 15'. The diagram is labeled T1131640-91.](5ee1bbbf85b473f78af9ec8368a4159a_img.jpg) + +``` + +graph TD + Start((1, 4 +A)) --> Setup[/SETUP (prec.) +req. ind. to FE7/] + Setup --> IsPrecedence{Is call +a precedence +call?} + IsPrecedence -- No --> Waiting1([Waiting for +response from FE7]) + IsPrecedence -- Yes --> Alternate{Alternate +party subscribed +to?} + Alternate -- No --> Waiting1 + Alternate -- Yes --> Set["Set (Now + +TK - Max., TK)"] + Set --> Waiting1 + Waiting1 --> Split(( )) + Split --> TKE[TK expires] + TKE --> Divert[Divert call to +alternate party] + Divert --> SetupAlt([MLPP call setup +to alternate party]) + Split --> Report[/REPORT +req. ind. +from FE7/] + Report --> ResetT[RESET TK] + ResetT --> InsertMLPP[Insert MLPP indi- +cator in REPORT +req. ind.] + InsertMLPP --> End((MLPP +15)) + +``` + +T1131640-91 + +Flowchart for FE6 – Incoming MLPP call from FE4. The process starts at connector 1, 4 (A), leading to a 'SETUP (prec.) req. ind. to FE7' block (967). A decision 'Is call a precedence call?' (967) follows. If 'No', it goes to 'Waiting for response from FE7' (967). If 'Yes', a second decision 'Alternate party subscribed to?' (967) is made. If 'No', it also goes to 'Waiting for response from FE7'. If 'Yes', a block 'Set (Now + T\_K - Max., T\_K)' (967) is executed, followed by 'Waiting for response from FE7'. From 'Waiting for response from FE7', the flow splits into two paths. The left path is triggered by 'T\_K expires' (964), leading to 'Divert call to alternate party' (964) and then 'MLPP call setup to alternate party' (964). The right path is triggered by 'REPORT req. ind. from FE7' (968), leading to 'RESET T\_K', then 'Insert MLPP indicator in REPORT req. ind.' (968), and finally to connector 'MLPP 15'. The diagram is labeled T1131640-91. + +*Note* – MLPP 15 enters the basic call at connector S4/6 (see Recommendation Q.71 [3]). + +FIGURE 3-10/Q.85 (sheet 2 of 5) + +#### **FE6 – Incoming MLPP call from FE4** + +![Flowchart for incoming MLPP call from FE6. It starts with a connector 'R' (labeled 1) leading to a decision diamond 'Is alternate party subscribed to?'. A dashed line from a box 'Interaction with other supplementary services expected but not yet specified' points to the connector. If 'Yes', the flow goes to a process box 'Divert call to alternate party' and then to an output oval 'MLPP call setup to alternate party'. If 'No', the flow goes to a process box 'RELEASE req. ind. to FE4 (precedence call blocked)' and then to a connector 'MLPP 16' (labeled T1131650-91).](dbd074feb5cce1300f42f91da8f673d1_img.jpg) + +``` + +graph TD + Start((R)) -- 1 --> D{Is alternate party subscribed to?} + D -- Yes --> P1[Divert call to alternate party] + P1 --> O1([MLPP call setup to alternate party]) + D -- No --> P2[RELEASE req. ind. to FE4 +(precedence call blocked)] + P2 --> C1((MLPP 16)) + + subgraph SideBox [ ] + SB[Interaction with other supplementary services expected but not yet specified] + end + SB -.- Start + + style SideBox fill:none,stroke:none + +``` + +T1131650-91 + +Flowchart for incoming MLPP call from FE6. It starts with a connector 'R' (labeled 1) leading to a decision diamond 'Is alternate party subscribed to?'. A dashed line from a box 'Interaction with other supplementary services expected but not yet specified' points to the connector. If 'Yes', the flow goes to a process box 'Divert call to alternate party' and then to an output oval 'MLPP call setup to alternate party'. If 'No', the flow goes to a process box 'RELEASE req. ind. to FE4 (precedence call blocked)' and then to a connector 'MLPP 16' (labeled T1131650-91). + +*Note* – MLPP 16 enters the basic call at connector S4/34 (see Recommendation Q.71 [3]). + +FIGURE 3-10/Q.85 (sheet 3 of 5) +**FE6 – Incoming MLPP call from FE4** + +![Flowchart for FE6 - Release and preemption of an existing call. The process starts at state S (1), releases user D call, and maintains connection to user D. It then receives a PREEMPTION NOTIFICATION (req. ind. to FE7) [964], sets a timer (Now + T_K - Max., T_K) [964], and waits for a response from FE7 [964]. Two paths emerge: 1) T_K expires [969], leading to a decision 'Is alternate party subscribed to?'. If 'No', it goes to state A (2). If 'Yes', it diverts the call to the alternate party [969] and sets up MLPP call [969]. 2) PREEMPT NOTIFICATION (resp. conf. from FE7) [967/969], leading to RESET T_K and then state A (2).](2580688a4de0a29692805cc6ba4822d7_img.jpg) + +``` + +graph TD + S((S 1)) --> Release[Release user D call and connection to other party of user D call (with preempt notification), while maintaining connection to user D] + Release --> PreemptReq{PREEMPTION NOTIFICATION req. ind. (to FE7)} + PreemptReq -- 964 --> SetTimer[Set (Now + T_K - Max., T_K)] + SetTimer -- 964 --> WaitResp([Waiting for response from FE7]) + WaitResp --> TimerExpires{} + WaitResp --> PreemptResp{PREEMPT NOTIFICATION resp. conf. (from FE7)} + + TimerExpires -- 969 --> IsSubscribed{Is alternate party subscribed to?} + IsSubscribed -- No --> A1((A 2)) + IsSubscribed -- Yes --> Divert[Divert call to alternate party] + Divert -- 969 --> MLPP([MLPP call setup to alternate party]) + MLPP -- 969 --> A1 + + PreemptResp -- 967/969 --> ResetTimer[RESET T_K] + ResetTimer --> A2((A 2)) + +``` + +Flowchart for FE6 - Release and preemption of an existing call. The process starts at state S (1), releases user D call, and maintains connection to user D. It then receives a PREEMPTION NOTIFICATION (req. ind. to FE7) [964], sets a timer (Now + T\_K - Max., T\_K) [964], and waits for a response from FE7 [964]. Two paths emerge: 1) T\_K expires [969], leading to a decision 'Is alternate party subscribed to?'. If 'No', it goes to state A (2). If 'Yes', it diverts the call to the alternate party [969] and sets up MLPP call [969]. 2) PREEMPT NOTIFICATION (resp. conf. from FE7) [967/969], leading to RESET T\_K and then state A (2). + +T1131660-91 + +FIGURE 3-10/Q.85 (sheet 4 of 5) + +#### **FE6 – Release and preemption of an existing call** + +![Flowchart for FE6 - LFB procedures. The process starts with an 'Idle (waiting for LFB)' state. An 'LFB req. ind. (from FE4)' event (961) triggers a 'Reserve incoming circuit' action (961). A decision 'Is user interface accessible?' follows. If 'Yes', an 'LFB resp. conf. (with network/called user status of "available")' event (962) leads to 'Idle (waiting for SETUP)'. If 'No', an 'Unreserve incoming circuit to FE4' action (961) is performed, followed by an 'LFB resp. conf. to FE4 (with network/called user status of "unavailable")' event (962), leading to an 'Idle' state. A note on the left specifies conditions for the 'Yes' path: 'Accessible if idle, preemptable, alternate party subscribed to, or call completion services available'.](4162c218fc7881cd90fc9574e07d2327_img.jpg) + +``` + +graph TD + Start([Idle +(waiting for LFB)]) --> Event1[/LFB req. ind. +(from FE4)/] + Event1 --> Action1[Reserve incoming circuit] + Action1 --> Decision1{Is user interface +accessible?} + Decision1 -- Yes --> Event2[/LFB resp. conf. +(with network/ +called user status +of "available")/] + Decision1 -- No --> Action2[Unreserve incoming +circuit to FE4] + Event2 --> End1([Idle (waiting +for SETUP)]) + Action2 --> Event3[/LFB resp. conf. to +FE4 (with network/ +called user status +of "unavailable")/] + Event3 --> End2([Idle]) + +``` + +961 + +961 + +962 + +Accessible if idle, preemptable, alternate party subscribed to, or call completion services available + +962 + +962 + +962 + +T1131670-91 + +Flowchart for FE6 - LFB procedures. The process starts with an 'Idle (waiting for LFB)' state. An 'LFB req. ind. (from FE4)' event (961) triggers a 'Reserve incoming circuit' action (961). A decision 'Is user interface accessible?' follows. If 'Yes', an 'LFB resp. conf. (with network/called user status of "available")' event (962) leads to 'Idle (waiting for SETUP)'. If 'No', an 'Unreserve incoming circuit to FE4' action (961) is performed, followed by an 'LFB resp. conf. to FE4 (with network/called user status of "unavailable")' event (962), leading to an 'Idle' state. A note on the left specifies conditions for the 'Yes' path: 'Accessible if idle, preemptable, alternate party subscribed to, or call completion services available'. + +FIGURE 3-10/Q.85 (sheet 5 of 5) + +#### **FE6 – LFB procedures** + +![Flowchart for FE5 – Preempted notification to user. The flow starts at a circle 'MLPP 17', leading to a diamond decision 'Preempted indicator?'. A 'No' branch leads to circle 'MLPP 18'. A 'Yes' branch leads to a process box 'PREEMPTED ind.', which then leads to circle 'MLPP 19'. Brackets labeled '951' are next to the decision and process boxes.](701bc79e78b382bcfd3ba85597dbb9c3_img.jpg) + +``` + +graph TD + MLPP17((MLPP 17)) --> Decision{Preempted indicator?} + Decision -- No --> MLPP18((MLPP 18)) + Decision -- Yes --> Process[/PREEMPTED ind./] + Process --> MLPP19((MLPP 19)) + +``` + +T1131680-91 + +Flowchart for FE5 – Preempted notification to user. The flow starts at a circle 'MLPP 17', leading to a diamond decision 'Preempted indicator?'. A 'No' branch leads to circle 'MLPP 18'. A 'Yes' branch leads to a process box 'PREEMPTED ind.', which then leads to circle 'MLPP 19'. Brackets labeled '951' are next to the decision and process boxes. + +*Note* – MLPP 17, MLPP 18 and MLPP 19 break the basic call between connectors S1/15, S1/16 and S1/MLPP 19 or S5/14, S5/15 and S5/16 (see Recommendation Q.71 [3]). + +FIGURE 3-11/Q.85 + +#### **FE5 – Preempted notification to user** + +#### 3.9.1 *FEAs of FE1* + +911: Insert the precedence level in the call set-up information. + +#### 3.9.2 *FEAs of FE2* + +921: Check for the cause preempted in the DISCONNECT req. ind. and if it is present, send a PREEMPTED ind. to the user. + +#### 3.9.3 *FEAs of FE3* + +931: Receive a higher precedence call request from user [via SETUP (prec) req. ind.]. + +Check and validate subscription option. + +Validate the precedence level of the call (assign the lowest precedence level if the user does not specify the precedence level for the call). + +Record successful invocation by precedence level. + +Queue the call request if all outgoing network resources to the called user are busy — that is, if congestion is encountered (if idle resources are available, mark the circuits with appropriate precedence level and MLPP domain information, and continue normal call set-up). + +If no idle resources are available, search for the lowest precedence preemptable circuits within the same MLPP domain, provided that the call is a precedence call (a call with precedence level higher than the lowest level of precedence). If no preemptable circuits are available, release the call with a cause of “precedence call blocked” to the user C. + +932: A preemptable circuit is available. Identify and mark the circuit as “path reserved” along with the precedence level and MLPP domain of the higher precedence call. (This happens to be the circuit of MLPP call A-B between FE3 and FE4.) + +Send LFB req. ind. to the next FE on the route (FE4). + +Start timer $T_L$ (if the LFB resp. conf. is not received before timer $T_L$ expires, preemption is initiated as given in FEA 934). + +![Flowchart for incoming MLPP call to user. The left side shows a sequence of events: Idle state, followed by a PREEMPT NOTIFICATION req. ind. (connector 971), then a PREEMPT NOTIFICATION ind. (connector 971), then a Waiting for response state (connector 971), then a PREEMPT NOTIFICATION resp. (connector 971), then a PREEMPT NOTIFICATION resp. conf. (connector 971), and finally back to Idle. The right side shows a decision diamond: 'Precedence level indicator in SETUP?'. If 'No', it goes to MLPP 21. If 'Yes', it goes to a 'SETUP (prec.) ind.' (connector 972), which then leads to MLPP 22. A reference T1131690-91 is noted.](89f8aefc01866631793087542316cef2_img.jpg) + +``` + +graph TD + Idle1([Idle]) --> Preq[PREEMPT NOTIFICATION req. ind.] + Preq -- 971 --> Pind{PREEMPT NOTIFICATION ind.} + Pind -- 971 --> Wait([Waiting for response]) + Wait -- 971 --> Presp[PREEMPT NOTIFICATION resp.] + Presp -- 971 --> Pconf{PREEMPT NOTIFICATION resp. conf.} + Pconf --> Idle2([Idle]) + + MLPP20((MLPP 20)) --> D{Precedence level indicator in SETUP?} + D -- No --> MLPP21((MLPP 21)) + D -- Yes --> Sprec[SETUP (prec.) ind.] + Sprec -- 972 --> MLPP22((MLPP 22)) + +``` + +T1131690-91 + +Flowchart for incoming MLPP call to user. The left side shows a sequence of events: Idle state, followed by a PREEMPT NOTIFICATION req. ind. (connector 971), then a PREEMPT NOTIFICATION ind. (connector 971), then a Waiting for response state (connector 971), then a PREEMPT NOTIFICATION resp. (connector 971), then a PREEMPT NOTIFICATION resp. conf. (connector 971), and finally back to Idle. The right side shows a decision diamond: 'Precedence level indicator in SETUP?'. If 'No', it goes to MLPP 21. If 'Yes', it goes to a 'SETUP (prec.) ind.' (connector 972), which then leads to MLPP 22. A reference T1131690-91 is noted. + +*Note* – MLPP 20, MLPP 21 and MLPP 22 break the basic call between connectors S5/1, S5/2 and S5/18 (see Recommendation Q.71 [3]). + +FIGURE 3-12/Q.85 +**FE7 – Incoming MLPP call to user** + +933: Receive LFB resp. conf. + +Determine the status of the called user and network resources (circuits). If the network/called party status is “unavailable”, a RELEASE req. ind. is sent to user C with a “precedence call blocked” indication, and the call A-B is not preempted. + +If the network/called party status is “available”, and if the reserved circuit is not preempted by another higher precedence call during the course of the LFB procedure, then proceed as shown in FEA 934. + +934: A DISCONNECT req. ind. is sent to the preceding FE (FE2) and a RELEASE req. ind. is sent to the next FE to preempt the lower precedence call A-B. + +A SETUP (prec) req. ind. is initiated and sent to the next FE (in this case it is FE4). The SETUP (prec) req. ind. includes the LFB indicator, MLPP domain, and the precedence level required to setup the higher precedence call C-D. + +935: Receive REPORT req. ind. + +Examine the MLPP indicator. If the called party is not an MLPP user, reclassify the call as a normal call. + +Relay the REPORT req. ind. to the preceding FE. + +Continue normal call setup. + +#### 3.9.4 *FEAs of FE4* + +941: Receive LFB req. ind. + +Mark the preemptable incoming circuit as “path reserved” along with the precedence level and MLPP domain of the higher precedence call. + +942: Search for the lowest precedence preemptable outgoing circuits within the same MLPP domain. (If no preemptable circuits are available, unreserve the incoming circuit and send LFB resp. conf. to the preceding FE with the network/called user status of “unavailable”.) + +A preemptable circuit is available. Mark the preemptable outgoing circuit as “path reserved” along with the precedence level and MLPP domain of the higher precedence call. + +Send LFB req. ind. to the next FE on the route. + +Start timer $T_L$ (if the LFB resp. conf. is not received before timer $T_L$ expires, the outgoing circuit is unreserved and an LFB resp. conf. “available” indication is returned to the preceding FE). + +943: Receive LFB resp.conf. + +Determine the status of the called user and network resources (circuits). If the network/called party status is “unavailable”, unreserve the incoming and outgoing circuits. + +Relay LFB resp. conf. to the preceding FE. + +944: Receive RELEASE req. ind. from the preceding FE. + +Release the network resources of the lower precedence call A-B. + +Send RELEASE resp. conf. to the preceding FE. + +945: Receive SETUP (prec) req. ind. from the preceding FE. + +Search for the reserved outgoing circuit. If the reserved outgoing circuit was preempted by another higher precedence call, initiate a normal search for an idle or preemptable circuit to reserve without using the LFB option (the procedure is similar to the procedure as described in FEA 931). + +If the reserved outgoing circuit is found and is idle, mark circuit as “busy” at selected precedence level and MLPP domain. If the reserved circuit is found and is busy with lower precedence, preempt the reserved outgoing circuit before marking circuit as “busy” at selected precedence level and MLPP domain. + +Send SETUP (prec) req. ind. to the next FE. The SETUP (prec) req. ind. includes MLPP domain, LFB indicator, calling party number, and the precedence level required to setup the higher precedence call C-D. + +946: Receive REPORT req. ind. + +Examine the MLPP indicator. If the called party is not an MLPP user, reclassify the call a normal call. + +Relay the REPORT to req. ind. to the preceding FE. + +#### 3.9.5 *FEAs of FE5* + +951: Check for the cause preempted in the RELEASE req. ind. and if it is present send a PREEMPTED ind. to the user. + +#### 3.9.6 *FEAs of FE6* + +961: Receive LFB req. ind. + +Mark the preemptable incoming circuit as “path reserved” along with the precedence level and MLPP domain of the higher precedence call. + +962: Determine the status of the called party. If the called party is available (the circuit is idle, preemptable, or the called party is subscribed to call completion service or has an alternate party) then send LFB resp. conf. to the preceding FE with network/called user status of “available”. Otherwise, an LFB resp. conf. is sent to the preceding FE with network/called user status of “unavailable”. + +963: Receive SETUP (prec) req. ind. from the preceding FE. + +Identify MLPP subscription status (MLPP or non-MLPP user) of called party. If the called party is a non-MLPP user, continue setup using basic call setup procedures and, once a SETUP resp. conf. is received from FE7, proceed as shown in FEA 968. If the called party is an MLPP subscriber, continue MLPP call setup as shown in FEA 964. + +964: Search for an idle outgoing circuit. (If there is an idle outgoing circuit, mark the outgoing circuit as “busy” at selected precedence level and MLPP domain, and send SETUP (prec) req. ind. to the user D). + +If no idle resources are available, search for the lowest precedence preemptable circuits within the same MLPP domain, provided that the call is a precedence call (a call with precedence level higher than the lowest level of precedence). + +If the called user is busy with a lower precedence call, an “intended preemption” indicator is sent to the called user D via PREEMPT NOTIFICATION req. ind. + +Start timer $T_K$ (If no acceptance of intended preemption is received before the expiry of timer $T_K$ , call diversion is initiated to the alternate party). + +965: Determine the status of the called user D (busy with lower precedence level call in this case). + +966: Initiate preemption of current call between user A and user D by sending RELEASE req. ind. to FE4. + +967: Receive called user acceptance of intended preemption (via PREEMPT NOTIFICATION resp. conf.) + +Mark circuit as “busy” at selected precedence level and MLPP domain. + +Initiate call setup by sending SETUP (prec) req. ind. to user D. + +968: Insert MLPP indicator in REPORT req. ind. to indicate the status of the called party (MLPP or non-MLPP user). + +Relay REPORT req. ind. to FE4. + +969: Receive called user acceptance of intended preemption (via PREEMPT NOTIFICATION resp. conf.). (If no acceptance of intended preemption is received before the expiry of timer $T_K$ , initiate alternate party diversion). + +Reserve user access channel for preempting call. + +#### 3.9.7 *FEAs of FE7* + +971: Receive PREEMPT NOTIFICATION req. ind. from the preceding FE. + +Send a PREEMPT NOTIFICATION ind. to the user and wait for a response. + +Receive PREEMPT NOTIFICATION resp. from the user. + +Send a PREEMPT NOTIFICATION resp. conf. to the preceding FE. + +972: Receive SETUP (prec) req. ind. for the preceding FE. + +Check for the precedence level in SETUP req. ind. and if it is present, send SETUP (prec) ind. to user. If it is not present, it will be treated as a non-compatible call in accordance with basic call procedures. + +### 3.10 Allocation of functional entities to physical locations + +The functional model relates to preemption of call(s) in the network to connect a higher precedence call. The following matrix contains additional, non-exhaustive scenarios. + +**Functional entities** + +| Functional entities
Scenarios | FE1 | FE2 | FE3 | FE4 | FE6 | FE5 | FE7 | +|----------------------------------|-----|-----|-----|-----|-----|-----|-----| +| Scenario 1 | TE | TE | LE | LE | LE | TE | TE | +| Scenario 2 | TE | TE | PNX | LE | PNX | TE | TE | +| Scenario 3 | TE | TE | PNX | TR | LE | TE | TE | +| Scenario 4 | TE | TE | LE | TR | PNX | TE | TE | +| Scenario 5 | TE | TE | TR | LE | LE | TE | TE | +| Scenario 6 | TE | TE | TR | LE | PNX | TE | TE | +| Scenario 7 | TE | TE | TR | TR | LE | TE | TE | +| Scenario 8 | TE | TE | TR | TR | PNX | TE | TE | + +LE Local exchange + +TE Terminal equipment + +TR Transit exchange + +PNX Private network exchange \ No newline at end of file diff --git a/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82956eeb8b256a993157d3a50f7cf1fdd199044b --- /dev/null +++ b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba7060e512a1cdeb8aef6d7a607803fb9728ccae98da1b9b80a1fd115d800494 +size 116788 diff --git a/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b182aac7417b6dce21317c734ab92de4f791fe27 --- /dev/null +++ b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fca8b7c30651b56735dad33d516a879c46095cb8231fb5a4705db42ad06bb8cf +size 177936 diff --git a/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6b4e308697b9f919aca433c67898d5f02cc623a --- /dev/null +++ b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abbd48f34d965c7d90ddc456f5ed289f754cf62e596b911e162e41539b7d5258 +size 73341 diff --git a/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..448d4e77391b41dd44ab92ab382a3ec414edc059 --- /dev/null +++ b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c58a3d78f02973e7ca20ba625332f91d5a1e7876ba72e5709082af5c7ba3f0f +size 110571 diff --git a/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59b129a0232810dbb8dbd4f4ec4bfb210f3a02d5 --- /dev/null +++ b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07f4b8bd070d80be7de5725b868477ae78c65582e331fb9b364ca1e12ed13bef +size 74466 diff --git a/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95a93b39b2b2ff4c3060c7cf0afa392b3bf55136 --- /dev/null +++ b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64d0016037d61afd9aae6b06436c27541d9e191bd2af5f079ee649863c97ab21 +size 51499 diff --git a/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/145d00f59802048185303f15937ea65c_img.jpg b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/145d00f59802048185303f15937ea65c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92958976823573a213e54ba98f657c618a7cacd8 --- /dev/null +++ b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/145d00f59802048185303f15937ea65c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94af21d547da250d5867232f2e69fb5734655f7c1eea8e4c24bb33a616065862 +size 123871 diff --git a/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..641cd352896c0914ff30da909ec4393664322402 --- /dev/null +++ b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:763402b6946678cfd2168e89131e96699c27fff06182b9163d8de75a6b16998b +size 8209 diff --git a/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91ada5de3fbe19323b060e75cdba1c4fda60d1c3 --- /dev/null +++ b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a39db3b47461200cdb6ea4d095e445e7795e1d3587a186878a9b3d17f66d54d1 +size 134570 diff --git a/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82a59c86bd372ba1e5feea5c010f0e8564be1ca8 --- /dev/null +++ b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae050783695acb68639286cb9df9495d50e28c3cb2bbc57d7a763830bf064909 +size 78768 diff --git a/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6905b1f123a2dfffe2eb096174eb5e57a2a90c27 --- /dev/null +++ b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ce5a43c764c3eca15740bd9bffbad72d5b36f0d456c051a17a3302e0f200d69 +size 60709 diff --git a/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d78377de4b93d47c1a1cc9486665fcefa301a7a --- /dev/null +++ b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43d435baabdc367a9ae61e9a72c0994c9eeb3a1613e250c2f0e74e201101e04b +size 54188 diff --git a/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a07a09d7712a9f081d7951b3ff20b1c41f424b7 --- /dev/null +++ b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7a9a3566c37b9a70c0f6d92c78e2765d445195673ffea1eb5d1c1a1f67ed7fb +size 204765 diff --git a/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/cfb98c691c1af5befe32ff9442eea511_img.jpg b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/cfb98c691c1af5befe32ff9442eea511_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16c55aeca2a0bb7ef392d5afb8b83152ee27a051 --- /dev/null +++ b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/cfb98c691c1af5befe32ff9442eea511_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:830f3dd163bacd60e754297654750e77b37c4e7145ecd7c8aee3814562cc7d92 +size 108996 diff --git a/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fa2e6697b1bfb97e7d5c23af21694b30e05a605 --- /dev/null +++ b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e398bf4c278e7cd7ff70ce41c114926e112da542038fabb9611185abcf79968 +size 52352 diff --git a/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/e151d3468319b81f042ca232c4d82e4b_img.jpg b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/e151d3468319b81f042ca232c4d82e4b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b01effe693f8ed9b340b494fd427ece092c7060 --- /dev/null +++ b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/e151d3468319b81f042ca232c4d82e4b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99180aa1d5207914ffcc0484e64abcf9d343ee96f2894b85e9473b00f46751f5 +size 94255 diff --git a/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d58f3902a48b43a261c4f79e92af99926c8bf048 --- /dev/null +++ b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f7a3eb2f8feb80e0e4d5c79dce51c62824a777aeaabce1b5811cd14a342603a +size 67381 diff --git a/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e524ee075ea43edcccb0bae78765c9ae5e4ed9e5 --- /dev/null +++ b/marked/Q/T-REC-Q.956.2-199510-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee34c07cde24ca0341f05830ad34c4b2d5cde8f1173b91f2868ee2d5375d7833 +size 182322