Add files using upload-large-folder tool

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                                                                                                                                                                                                              |
+|------------|---------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <i>a</i> ) | A subscriber (automatic)                                                                                                  | 1. International prefix <sup>a</sup> )<br>2. Country code <sup>b</sup> )<br>3. National (significant) number <sup>c</sup> )                                                                                                                       |
+| <i>b</i> ) | A subscriber (semi-automatic)                                                                                             | 1. Country code <sup>b</sup> ), <sup>d</sup> )<br>2. National (significant) number <sup>c</sup> )<br>3. Sending-finished                                                                                                                          |
+| <i>c</i> ) | Any incoming or delay operator's position (semi-automatic)                                                                | 1. Country code <sup>b</sup> ), <sup>d</sup> )<br>2. Extra digit designating the incoming international exchange <sup>e</sup> )<br>3. Code 11 or code 12 <sup>f</sup> )<br>4. Sending-finished                                                    |
+| <i>d</i> ) | An particular delay operator, or one of those operating a particular group of delay operator's positions (semi-automatic) | 1. Country code <sup>b</sup> ), <sup>d</sup> )<br>2. Extra digit designating the incoming international exchange <sup>e</sup> )<br>3. Code 12 <sup>f</sup> )<br>4. Number of a particular position or a group of positions<br>5. Sending-finished |
+| <i>e</i> ) | An information operator or a special service operator                                                                     | 1. Special numbers                                                                                                                                                                                                                                |
+
+<sup>a</sup>) The recommended international prefix is 00, see Recommendation Q. 11 *bis*, § 4.1.
+
+<sup>b</sup>) The country code consists of one these digit combinations: I<sub>1</sub>, I<sub>1</sub> I<sub>2</sub>, I<sub>1</sub> I<sub>2</sub> I<sub>3</sub>.
+
+<sup>c</sup>) The national (significant) number consists of the subscriber number and the trunk code: N<sub>1</sub>, N<sub>2</sub>, N<sub>3</sub>.... 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<br>on the international link              |
+|-----------|---------------------|---------------------|-------------------------------------------------------------|
+|           | from                | to                  |                                                             |
+| <i>a)</i> | Originating country | Designation country | Terminal-call indicator or discriminating or language digit |
+| <i>b)</i> | Originating country | Transit country     | Transit-call indicator                                      |
+| <i>c)</i> | Transit country     | Transit country     | Transit-call indicator                                      |
+| <i>d)</i> | 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 <sup>a)</sup> |
+|--------------------------------------------|------------------------------------|---------------------------------------------------------------------------------------------------------|-------|------------------------------------------|------------------|
+| sending sequence                           | International transit call         | Transit seizing <sup>b)</sup>                                                                           | KP 2  | I-12 or<br>I-14 or<br>I-11 <sup>c)</sup> | —                |
+|                                            | Echo-suppressor indicator          | — <sup>d)</sup>                                                                                         | —     |                                          | —                |
+|                                            | Nature-of-circuit indicator        | —                                                                                                       | —     | I-13 or I-14 <sup>e)</sup>               | —                |
+|                                            | Country code                       | I <sub>1</sub> I <sub>1</sub> I <sub>2</sub> I <sub>1</sub> I <sub>2</sub> I <sub>3</sub> <sup>f)</sup> |       |                                          | —                |
+|                                            | Calling-party's-category indicator | D = 0 or L = 1, 2, 3, ...                                                                               |       |                                          | —                |
+|                                            | National (significant) number      | N <sub>1</sub> N <sub>2</sub> N <sub>3</sub> ...                                                        |       |                                          | ���                |
+|                                            | Sending-finished                   | Code 15                                                                                                 | ST    | Code 15                                  | —                |
+| International terminal call                | Terminal-call indicator            | Terminal seizing <sup>b)</sup>                                                                          | KP 1  |                                          | KP <sup>h)</sup> |
+|                                            | Calling-party's-category indicator | D = 0 or L = 1, 2, 3 ... <sup>g)</sup>                                                                  |       |                                          | —                |
+|                                            | Echo-suppressor indicator          | — <sup>d)</sup>                                                                                         | —     | 1-14 <sup>e)</sup>                       | —                |
+|                                            | Nature-of-circuit indicator        | —                                                                                                       | —     | 1-13 or 1-14 <sup>e)</sup>               | —                |
+|                                            | National (significant) number      | N <sub>1</sub> N <sub>2</sub> N <sub>3</sub> ...                                                        |       |                                          | —                |
+|                                            | Sending-finished                   | Code 15                                                                                                 | ST    | Code 15                                  | —                |
+
+<sup>a)</sup> Signalling system R1 is not used for international transit calls.
+
+<sup>b)</sup> 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.
+
+<sup>c)</sup> The use of signal I-11 in international working is subject to bilateral agreements.
+
+<sup>d)</sup> Code 14 can be used for echo-suppressor control to bilateral or multilateral agreements.
+
+<sup>e)</sup> These signals are sent on request.
+
+<sup>f)</sup> See Recommendation Q.101.
+
+<sup>g)</sup> For Signalling System R2, the L digit is also used as terminal-call indicator.
+
+<sup>h)</sup> 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 <sup>a)</sup>    |
+|--------------------------------------------|-----------------------------------------------|-----------------------------------------------------------------------------------------------|-------|------------------------------------------|---------------------|
+| Sending sequence                           | International transit call                    | Transit seizing <sup>b)</sup>                                                                 | KP 2  | I-12 or<br>I-14 or<br>I-11 <sup>c)</sup> | —                   |
+|                                            | Echo-suppressor indicator                     | — <sup>d)</sup>                                                                               | —     |                                          | —                   |
+|                                            | Nature-of-circuit indicator                   | —                                                                                             | —     | I-13 or I-14 <sup>e)</sup>               | —                   |
+|                                            | Country code                                  | I <sub>1</sub> , I <sub>1</sub> I <sub>2</sub> , I <sub>1</sub> I <sub>2</sub> I <sub>3</sub> |       |                                          | —                   |
+|                                            | Language digit                                | L = 1, 2, 3, ...                                                                              |       |                                          | —                   |
+|                                            | Extra digit designating the incoming exchange | N <sub>1</sub>                                                                                |       |                                          | —                   |
+|                                            | Access to operator's position                 | Code 11 or code 12 <sup>f)</sup>                                                              |       |                                          | —                   |
+|                                            | Sending-finished                              | Code 15                                                                                       | ST    | Code 15                                  | —                   |
+| International terminal call                | Terminal-call indicator                       | Terminal seizing <sup>b)</sup>                                                                | KP 1  |                                          | KP <sup>h)</sup>    |
+|                                            | Language digit                                | L = 1, 2, 3, ... <sup>g)</sup>                                                                |       |                                          | —                   |
+|                                            | Echo-suppressor indicator                     | — <sup>d)</sup>                                                                               | —     | 1-14 <sup>e)</sup>                       | —                   |
+|                                            | Nature-of-circuit indicator                   | —                                                                                             | —     | 1-13 or 1-14 <sup>e)</sup>               | —                   |
+|                                            | Extra digit designating the incoming exchange | N <sub>1</sub>                                                                                |       |                                          | —                   |
+|                                            | Access to operator's position                 | Code 11 or code 12 <sup>f)</sup>                                                              |       |                                          | e.g. 121<br>or 1150 |
+|                                            | Sending-finished                              | Code 15                                                                                       | ST    | Code 15                                  | ST                  |
+
+<sup>a)</sup> Signalling System R1 is not used for international transit calls.
+
+<sup>b)</sup> 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.
+
+<sup>c)</sup> The use of signal I-11 in international working is subject to bilateral agreements.
+
+<sup>d)</sup> Code 14 can be used for echo-suppressor control subject to bilateral or multilateral agreements.
+
+<sup>e)</sup> These signals are sent on request.
+
+<sup>f)</sup> See Recommendation Q.101.
+
+<sup>g)</sup> For Signalling System R2, The L digit is also used as terminal-call indicator.
+
+<sup>h)</sup> 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 <sup>a)</sup>                     |
+|------------------------------------------------|-----------------------------------------|-----------------------------------------------------------------------------------------------|-------|------------------------------------------|--------------------------------------|
+| Sending sequence<br>International transit call | Transit-call indicator                  | Transit seizing <sup>b)</sup>                                                                 | KP 2  | I-12 or<br>I-14 or<br>I-11 <sup>c)</sup> | —                                    |
+|                                                | Echo-suppressor indicator               | — <sup>d)</sup>                                                                               | —     |                                          | —                                    |
+|                                                | Nature-of-circuit indicator             | —                                                                                             | —     | I-13 or I-14 <sup>e)</sup>               | —                                    |
+|                                                | Country code                            | I <sub>1</sub> , I <sub>1</sub> I <sub>2</sub> , I <sub>1</sub> I <sub>2</sub> I <sub>3</sub> |       |                                          | —                                    |
+|                                                | Language digit                          | L = 1, 2, 3, ...                                                                              |       |                                          | —                                    |
+|                                                | Extra digit designating the incoming CT | N <sub>1</sub>                                                                                |       |                                          | —                                    |
+|                                                | Access to operator's position           | Code 12                                                                                       |       |                                          | —                                    |
+|                                                | Number of a particular position         | x <sub>1</sub> (x <sub>2</sub> x <sub>3</sub> ...)                                            |       |                                          | —                                    |
+|                                                | Sending-finished                        | Code 15                                                                                       | ST    | Code 15                                  | —                                    |
+| International terminal call                    | Terminal-call indicator                 | Terminal seizing <sup>b)</sup>                                                                | KP 1  |                                          | KP <sup>g)</sup>                     |
+|                                                | Language digit                          | L = 1, 2, 3, ... <sup>f)</sup>                                                                |       |                                          | —                                    |
+|                                                | Echo-suppressor indicator               | — <sup>d)</sup>                                                                               | —     | 1-14 <sup>e)</sup>                       | —                                    |
+|                                                | Nature-of-circuit indicator             | —                                                                                             | —     | 1-13 or 1-14 <sup>e)</sup>               | —                                    |
+|                                                | Extra digit designating the incoming CT | N <sub>1</sub>                                                                                |       |                                          | —                                    |
+|                                                | Access to operator's position           | Code 12                                                                                       |       |                                          | e.g. 1150                            |
+|                                                | Number of a particular position         | x <sub>1</sub> (x <sub>2</sub> x <sub>3</sub> ...)                                            |       |                                          | e.g. 11x <sub>1</sub> x <sub>2</sub> |
+|                                                | Sending-finished                        | Code 15                                                                                       | ST    | Code 15                                  | ST                                   |
+
+<sup>a)</sup> Signalling System R1 is not used for international transit calls.
+
+<sup>b)</sup> 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.
+
+<sup>c)</sup> The use of signal I-11 in international working is subject to bilateral agreements.
+
+<sup>d)</sup> Code 14 can be used for echo-suppressor control subject to bilateral or multilateral agreements.
+
+<sup>e)</sup> These signals are sent on request.
+
+<sup>f)</sup> For Signalling System R2, the L digit is also used as terminal-call indicator.
+
+<sup>g)</sup> 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 <sup>a)</sup> | —                                        |
+| 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                                       |
+
+<sup>a)</sup> 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<br>7<br>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.

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.

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
+
+|                                     | <i>Page</i> |
+|-------------------------------------|-------------|
+| 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.

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.

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        |
+| <b>INTELLIGENT NETWORK</b>                               | <b>Q.1200–Q.1999</b> |
+| 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
+
+|                                                      | <i>Page</i> |
+|------------------------------------------------------|-------------|
+| 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                                                   |
+| <b>Series Q</b> | <b>Switching and signalling</b>                                                                                                |
+| 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                                                                                                          |

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        |
+| <b>ATM adaptation layer</b>                                                                                  | <b>Q.2100–Q.2199</b> |
+| 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.<br>NOTE 2 – Not present as the corrupted data delivery option is not utilized.<br><ul style="list-style-type: none"> <li>Only message mode is utilized.</li> <li>The CPCS-LP parameter is set to "0" at the transmitter and ignored at the receiver.</li> <li>The CPCS-CI parameter is set to "0" at the transmitter and its use by the receiver is for further study.</li> <li>The CPCS-UU parameter is set to "0" at the transmitter and ignored at the receiver.</li> <li>The corrupted data delivery option is not utilized.</li> </ul> |                      |                      |
+
+## 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-0011<sub>2</sub>.
+
+### 2) *Octet 2: Protocol identifier*
+
+This octet contains an Initial Protocol Identifier (IPI) and shall be coded as 0000-1010<sub>2</sub> (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

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>B-ISDN application protocols for access signalling</b> | <b>Q.2900-Q.2999</b> |
+
+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 T<sub>B</sub> reference point or coincident S<sub>B</sub> and T<sub>B</sub> 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
+
+|   |                                 | <b>Page</b> |
+|---|---------------------------------|-------------|
+| 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 T<sub>B</sub> reference point or coincident S<sub>B</sub> and T<sub>B</sub> 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 T<sub>B</sub> reference point or coincident S<sub>B</sub> and T<sub>B</sub> 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                                                   |
+| <b>Series Q</b> | <b>Switching and signalling</b>                                                                                                |
+| 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                                                           |

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        |
+| <b>Service and session control protocols</b>                                                | <b>Q.3400–Q.3499</b> |
+| 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          | <a href="http://handle.itu.int/11.1002/1000/12987">11.1002/1000/12987</a> |
+
+## Keywords
+
+IPv6, multimedia services, NGN.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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                                                                                                 |
+| <b>Series Q</b> | <b>Switching and signalling</b>                                                                                                                           |
+| 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                                                                                      |

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        |
+| <b>Resource control protocols</b>                                              | <b>Q.3710–Q.3739</b> |
+| 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          | <a href="http://handle.itu.int/11.1002/1000/13698">11.1002/1000/13698</a> |
+
+## Keywords
+
+Automatic management, IP address pool, software-defined networking.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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<Device> | 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.<br>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<Device> | 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.<br>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<Address_Pool>       | 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<Address_pool_range> | 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**
+
+| <b>Parameter name</b> | <b>Type</b> | <b>Optional</b> | <b>Meanings and explanations</b>                                                         |
+|-----------------------|-------------|-----------------|------------------------------------------------------------------------------------------|
+|                       |             |                 | 1 means reclaim successfully<br>2 means failed to allocate<br>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**
+
+| <b>Parameter name</b> | <b>Type</b> | <b>Optional</b> | <b>Meanings and explanations</b>                        |
+|-----------------------|-------------|-----------------|---------------------------------------------------------|
+| 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**
+
+| <b>Parameter name</b> | <b>Type</b> | <b>Optional</b> | <b>Meanings and explanations</b>                                                         |
+|-----------------------|-------------|-----------------|------------------------------------------------------------------------------------------|
+| 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.<br>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**
+
+| <b>Parameter name</b>   | <b>Type</b> | <b>Optional</b> | <b>Meanings and explanations</b>                                                         |
+|-------------------------|-------------|-----------------|------------------------------------------------------------------------------------------|
+| 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.<br>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.<br>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.<br>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.<br>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**
+
+| <b>Parameter name</b>       | <b>Type</b> | <b>Optional</b> | <b>Meanings and explanations</b>                   |
+|-----------------------------|-------------|-----------------|----------------------------------------------------|
+| 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**
+
+| <b>Parameter name</b>       | <b>Type</b> | <b>Optional</b> | <b>Meanings and explanations</b>                                 |
+|-----------------------------|-------------|-----------------|------------------------------------------------------------------|
+| 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**
+
+| <b>Parameter name</b> | <b>Type</b> | <b>Optional</b> | <b>Meanings and explanations</b>                        |
+|-----------------------|-------------|-----------------|---------------------------------------------------------|
+| 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                                                                              |
+| <b>Series Q</b> | <b>Switching and signalling, and associated measurements and tests</b>                                                                                    |
+| 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                                                                                      |

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        |
+| <b>Resource control protocols</b>                                              | <b>Q.3710–Q.3739</b> |
+| 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          | <a href="http://handle.itu.int/11.1002/1000/13699">11.1002/1000/13699</a> |
+
+## Keywords
+
+Sew, signalling requirement, software-defined networking; virtual data centre, VxLAN
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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:
+
+```
+<KE-AL 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 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:
+
+```
+<VT-EXR 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 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:
+
+```
+<VN-EXR Message > ::= < 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:
+
+```
+<NE-EX Message > ::= < 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:
+
+```
+<VT-IQR Message > ::= < 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:
+
+```
+<VN-IQ Message > ::= < 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:
+
+```
+<VN-IQR Message > ::= < 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:
+
+```
+<NE-IQ Message > ::= < 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:
+
+```
+<NE-IQR Message > ::= < 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:
+
+```
+<CO-FA Message > ::= < 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:
+
+```
+<CO-FAR 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 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:
+
+```
+<VT-FA Message > ::= < 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:
+
+```
+<VT-FAR Message > ::= < 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:
+
+```
+<VN-FA Message > ::= < 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:
+
+```
+<VN-FAR 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 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:
+
+```
+
+<NE-FA Message > ::=< 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:
+
+```
+
+<NE-FAR Message > ::=< 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                                                                              |
+| <b>Series Q</b> | <b>Switching and signalling, and associated measurements and tests</b>                                                                                    |
+| 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                                                                                      |

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        |
+| <b>Resource control protocols</b>                                              | <b>Q.3710–Q.3739</b> |
+| 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          | <a href="http://handle.itu.int/11.1002/1000/14144">11.1002/1000/14144</a> |
+
+## Keywords
+
+Control plane, user plane, vBNG.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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
+
+|                                                                              | <b>Page</b> |
+|------------------------------------------------------------------------------|-------------|
+| 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                                                                              |
+| <b>Series Q</b> | <b>Switching and signalling, and associated measurements and tests</b>                                                                                    |
+| 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                                                                                      |

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        |
+| <b>Resource control protocols</b>                                              | <b>Q.3710–Q.3739</b> |
+| 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          | <a href="http://handle.itu.int/11.1002/1000/15045">11.1002/1000/15045</a> |
+
+## Keywords
+
+Procedures, programming protocol independent packet processor, switch-based.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+# 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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   | <i>In-situ</i> 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<br>(Varies depending on RepType)                                                  |   |   |   |        |   |   |   |               |   |    |    |    |    |    |    |           |    |    |    |    |    |    |    |    |    |    |    |      |    |    |    |
+| Individual report inner contents<br>(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<br>(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                                                                              |
+| <b>Series Q</b> | <b>Switching and signalling, and associated measurements and tests</b>                                                                                    |
+| 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                                                                                      |

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        |
+| <b>Network signalling and signalling requirements for services</b>             | <b>Q.3740–Q.3779</b> |
+| 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          | <a href="http://handle.itu.int/11.1002/1000/13978">11.1002/1000/13978</a> |
+
+## Keywords
+
+SD-WAN, signalling requirements.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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<br>response message.....   | 11   |
+| 9.7 Dynamic SD-WAN path control for WAN gateway request message and<br>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:
+
+```
+<CPE-REG -RQ-Message>::= < 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:
+
+```
+<CPE-REG -RP-Message> ::= < 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:
+
+```
+<WG -RES-RQ-Message> ::= < 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:
+
+```
+<WG-REG-RP-Message> ::= < 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:
+
+```
+<CPE-CG-Message> ::= < 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:
+
+```
+<CPE-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, 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:
+
+```
+<WG-CG-Message> ::= < 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:
+
+```
+<ST-RQ-Message> ::= < 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:
+
+```
+<ST-RP-Message> ::= < 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:
+
+```
+<CPE-Path-RQ -Message> ::= < 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:
+
+```
+<CPE-Path-RP -Message> ::= < 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                                                                              |
+| <b>Series Q</b> | <b>Switching and signalling, and associated measurements and tests</b>                                                                                    |
+| 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                                                                                      |

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        |
+| <b>Testing specifications for next generation networks</b>                     | <b>Q.3900-Q.3999</b> |
+| 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          | <a href="http://handle.itu.int/11.1002/1000/13487">11.1002/1000/13487</a> |
+
+## Keywords
+
+Cloud computing, monitoring, parameter.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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**
+
+| <b>Metric name</b>                | <b>Description</b>                                                               | <b>Unit</b> |
+|-----------------------------------|----------------------------------------------------------------------------------|-------------|
+| 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**
+
+| <b>Metric name</b>                                 | <b>Description</b>                                                          | <b>Unit</b> |
+|----------------------------------------------------|-----------------------------------------------------------------------------|-------------|
+| 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**
+
+| <b>Metric name</b> | <b>Description</b>                                             | <b>Unit</b> |
+|--------------------|----------------------------------------------------------------|-------------|
+| 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**
+
+| <b>Metric name</b>                  | <b>Description</b>                              | <b>Unit</b> |
+|-------------------------------------|-------------------------------------------------|-------------|
+| 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**
+
+| <b>Metric name</b>       | <b>Description</b>                                                                                           | <b>Unit</b>   |
+|--------------------------|--------------------------------------------------------------------------------------------------------------|---------------|
+| 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**
+
+| <b>Metric name</b>              | <b>Description</b>                                 | <b>Unit</b> |
+|---------------------------------|----------------------------------------------------|-------------|
+| 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                                                                              |
+| <b>Series Q</b> | <b>Switching and signalling, and associated measurements and tests</b>                                                                                    |
+| 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                                                                                      |

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        |
+| <b>Testing specifications for SIP-IMS</b>                                      | <b>Q.4000–Q.4039</b> |
+| 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          | <a href="http://handle.itu.int/11.1002/1000/12741">11.1002/1000/12741</a> |
+
+## **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 <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 <reference specification type>;
+- 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 <item description> 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: <predicate>.
+
+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 <reference specification type> 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 <urn:alert:service:call-waiting>? | 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 <sub>UE-CW</sub> ?                                                                                                              | 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                                                                                                 |                                 |
+| <td><b>Series Q</b></td> <td><b>Switching and signalling</b></td> | <b>Series Q</b>                                                                                                                                           | <b>Switching and signalling</b> |
+| 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                                                                                      |                                 |

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        |
+| <b>PROTOCOLS AND SIGNALLING FOR QUANTUM KEY DISTRIBUTION NETWORKS</b>          | <b>Q.4160-Q.4179</b> |
+| 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 <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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<br>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                                                                              |
+| <b>Series Q</b> | <b>Switching and signalling, and associated measurements and tests</b>                                                                                    |
+| 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                                                                                      |

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        |
+| <b>Signalling requirements and architecture of IMT-2020</b>                    | <b>Q.5000-Q.5019</b> |
+| 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          | <a href="http://handle.itu.int/11.1002/1000/15256">11.1002/1000/15256</a> |
+
+## Keywords
+
+IMS, IMT-2020 network and beyond, signalling architecture.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 | <ul style="list-style-type: none"> <li>– self-organizing user data network composed of SUPFs</li> <li>– enables independent operation and opening</li> </ul> |
+| 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 | <ul style="list-style-type: none"><li>– originating and terminating unification</li><li>– lower media delay and more synchronous media experience</li></ul> |
+| 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<br>Unsubscribe: unsubscribe<br>Initcall: initial call notification<br>Ring: ring notification<br>Answer: off-hook notification<br>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<br>Releaseuser: release the user<br>Playvoice: play voice to user<br>SDP action: add, modify, or delete an SDP<br>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                                                                              |
+| <b>Series Q</b> | <b>Switching and signalling, and associated measurements and tests</b>                                                                                    |
+| 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                                                                                      |

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        |
+| <b>Protocols for IMT-2020</b>                                                  | <b>Q.5020-Q.5049</b> |
+| 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 <https://handle.itu.int/> 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 <http://www.itu.int/ITU-T/ipr/>.
+
+© 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 <sub>2</sub> | 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            | <i>water-temperature-value</i> indicates the water temperature, measured by the water temperature sensor.                                                                                                                                                                                                                           |
+| water-temperature-units     | STRING            | <i>water-temperature-units</i> 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) | <i>water-temperature-range</i> 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            | <i>water-temperature-precision</i> indicates precision of the temperature value. It can be used in conjunction with " <i>water-temperature-range</i> ". For example, if " <i>water temperature-range</i> " is (0, 10) and " <i>water-temperature-precision</i> " is 1, valid water temperature data can be expressed as an integer. |
+| water-temperature-margin    | NUMBER            | <i>water-temperature-margin</i> indicates the error range of the water temperature value. It can be used in conjunction with " <i>water-temperature-range</i> ". For example, if " <i>water-temperature-range</i> " is (0, 10) and " <i>water-temperature-margin</i> " 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            | <i>dissolved-oxygen-value</i> indicates the amount of oxygen dissolved in water as a value, and is a value measured by a DO sensor.                                                                                                                                                                                                                      |
+| dissolved-oxygen-units     | STRING            | <i>dissolved-oxygen-unit</i> 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) | <i>dissolved-oxygen-range</i> 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            | <i>dissolved-oxygen-precision</i> indicates the precision of the value of the amount of oxygen dissolved in water. This can be used in conjunction with the " <i>dissolved-oxygen-range</i> ".                                                                                                                                                           |
+| dissolved-oxygen-margin    | NUMBER            | <i>dissolved-oxygen-margin</i> indicates the error range of the value of the amount of oxygen dissolved in water. This can be used in conjunction with the " <i>dissolved-oxygen-range</i> ". For example, if " <i>dissolved oxygen range</i> " is (0, 10) and " <i>dissolved-oxygen-margin</i> " 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            | <i>pH-value</i> indicates the amount of hydrogen ions present in water as a value, and is a value measured by a pH sensor.                                                                                                                                                                                      |
+| pH-units     | STRING            | <i>pH-units</i> 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) | <i>pH-range</i> 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            | <i>pH-precision</i> indicates the precision of the value of the amount of hydrogen ions present in water. This can be used in conjunction with " <i>pH-range</i> ". For example, if " <i>pH-range</i> " is (0, 14) and " <i>pH-precision</i> " is 1, valid pH data can be expressed as integers.                |
+| pH-margin    | NUMBER            | <i>pH-margin</i> represents the error range of the value of the amount of hydrogen ions present in water. This can be used in conjunction with " <i>pH-range</i> ". For example, if the " <i>pH-range</i> " is (0, 14) and the " <i>pH-margin</i> " 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            | <i>ORP-value</i> is the oxidation reduction potential, which is an indicator of the degree of oxidation and reduction of metals. <i>ORP-value</i> is used to measure the redox reaction of wastewater.                                                                                                                                                                                                                                                                              |
+| ORP-units     | STRING            | <i>ORP-units</i> is the movement of electrons, which is measured in mV.                                                                                                                                                                                                                                                                                                                                                                                                             |
+| ORP-range     | NUMBER (MIN, MAX) | <i>ORP-range</i> 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            | <i>ORP-precision</i> indicates the precision of the ORP value in the water. This can be used in conjunction with " <i>ORP-range</i> ". For example, if " <i>ORP-range</i> " is (–1000, 1000) and " <i>ORP-precision</i> " is 1, valid ORP data can be expressed as integers.                                                                                                                                                                                                        |
+| ORP-margin    | NUMBER            | <i>ORP-margin</i> represents the error range of the value of the amount of ORP in the water. This can be used in conjunction with " <i>ORP-range</i> ". For example, if the " <i>ORP-range</i> " is (–1000, 1000) and the " <i>ORP-margin</i> " 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**
+
+| <b>Data types</b>            | <b>Available models</b>                | <b>Description</b>                                                                                                                                                                                                                       |
+|------------------------------|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 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 <sub>2</sub> ). |
+| 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 <sub>2</sub> .            |
+
+#### 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**
+
+| <b>Keyword</b>                       | <b>Type</b>       | <b>Description</b>                                                                                                                                                                                                                                                                                                                                                                                         |
+|--------------------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| predicted-dissolved-oxygen-value     | NUMBER            | <i>predicted-dissolved-oxygen-value</i> 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            | <i>predicted-dissolved-oxygen-units</i> 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) | <i>predicted-dissolved-oxygen-range</i> 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            | <i>predicted-dissolved-oxygen-precision</i> indicates the precision of the value of the amount of predicted oxygen dissolved in water. This can be used in conjunction with the " <i>predicted-dissolved-oxygen-range</i> ".                                                                                                                                                                               |
+| predicted-dissolved-oxygen-margin    | NUMBER            | <i>predicted-dissolved-oxygen-margin</i> indicates the error range of the value of the amount of predicted oxygen dissolved in water. This can be used in conjunction with the " <i>predicted-dissolved-oxygen-range</i> ". For example, if " <i>predicted-dissolved-oxygen-range</i> " is (0, 10) and " <i>predicted-dissolved-oxygen-margin</i> " 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            | <i>predicted-water-temperature-value</i> indicates the water temperature, predicted by the AI model of digital twins.                                                                                                                                                                                                                                                                 |
+| predicted-water-temperature-units     | STRING            | <i>predicted-water-temperature-units</i> 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) | <i>predicted-water-temperature-range</i> 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            | <i>predicted-water-temperature-precision</i> indicates precision of the temperature value. It can be used in conjunction with " <i>predicted-water-temperature-range</i> ". For example, if " <i>predicted-water-temperature-range</i> " is (0, 10) and " <i>predicted-water-temperature-precision</i> " is 1, valid predicted water temperature data can be expressed as an integer. |
+| predicted-water-temperature-margin    | NUMBER            | <i>predicted-water-temperature-margin</i> indicates the error range of predicted water temperature value. It can be used in conjunction with " <i>predicted-water-temperature-range</i> ". For example, if " <i>predicted-water-temperature-range</i> " is (0, 10) and " <i>predicted-water-temperature-margin</i> " 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**
+
+|                    |                                                                                                                          |
+|--------------------|--------------------------------------------------------------------------------------------------------------------------|
+| <b>HTTP Method</b> | POST                                                                                                                     |
+| <b>HTTP URI</b>    | http://[address of edge networking entity]:[port]/[digital twin smart aquaculture service]/[version]/[type of event]/c   |
+| <b>BODY</b>        | "timestamp": NUMBER,<br>"device-id": STRING,<br>"data-id": NUMBER,<br>"data-type": STRING,<br>"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**
+
+|                           |                 |
+|---------------------------|-----------------|
+| <b>HTTP Response code</b> | <i>rsp_code</i> |
+| <b>BODY</b>               | 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**
+
+|                    |                                                                                                                                    |
+|--------------------|------------------------------------------------------------------------------------------------------------------------------------|
+| <b>HTTP Method</b> | GET                                                                                                                                |
+| <b>HTTP URI</b>    | http://[address of edge networking entity]:[port]/[digital twin smart aquaculture service]/[version]/[type of event]/r/[data-type] |
+| <b>PARAMETERS</b>  | "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**
+
+|                    |                                                                                                                                                       |
+|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>HTTP Method</b> | GET                                                                                                                                                   |
+| <b>HTTP URI</b>    | http:// [address of edge networking entity]: [port]/ [digital twin smart aquaculture service]/ [version]/ [type of event]/r/ [data-type]/ [device-id] |
+| <b>PARAMETERS</b>  | "device-id": STRING,<br>"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**
+
+|                           |                                                                                                                          |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------|
+| <b>HTTP Response code</b> | <i>rsp_code</i>                                                                                                          |
+| <b>BODY</b>               | "timestamp": NUMBER,<br>"device-id": STRING,<br>"data-id": NUMBER,<br>"data-type": STRING,<br>"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**
+
+|                    |                                                                                                                                  |
+|--------------------|----------------------------------------------------------------------------------------------------------------------------------|
+| <b>HTTP Method</b> | PUT                                                                                                                              |
+| <b>HTTP URI</b>    | http://[address of edge networking entity]:[port]/[digital twin smart aquaculture service]/[version]/[type of event]/u/[data-id] |
+| <b>PARAMETERS</b>  | "data-id": NUMBER                                                                                                                |
+| <b>BODY</b>        | "timestamp": NUMBER,<br>"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**
+
+|                           |                 |
+|---------------------------|-----------------|
+| <b>HTTP Response code</b> | <i>rsp_code</i> |
+| <b>BODY</b>               | 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**
+
+|                    |                                                                                                                                  |
+|--------------------|----------------------------------------------------------------------------------------------------------------------------------|
+| <b>HTTP Method</b> | POST                                                                                                                             |
+| <b>HTTP URI</b>    | http://[address of edge networking entity]:[port]/[digital twin smart aquaculture service]/[version]/[type of event]/d/[data-id] |
+| <b>BODY</b>        | "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**
+
+|                               |                 |
+|-------------------------------|-----------------|
+| <b>HTTP<br/>Response code</b> | <i>rsp_code</i> |
+| <b>BODY</b>                   | 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                                                                              |
+| <b>Series Q</b> | <b>Switching and signalling, and associated measurements and tests</b>                                                                                    |
+| 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                                                                                      |

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**<sub>2</sub>.
+- A-7**: 'Continue sending from digit (N-2)' leads to connector **10**<sub>2</sub>.
+- A-8**: 'Continue sending from digit (N-3)' leads to connector **10**<sub>2</sub>.
+- 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**<sub>1</sub>.
+- 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**<sub>4</sub>.
+- FITE 22**: Leads to signal **BITE 12**.
+
+ Signals **I-12**, **I-14**, and **I-13** converge at connector **2**<sub>2</sub>. From here, the flow proceeds to connector reference 05 ('Wait for address information').
+ 
+
+- FITE 1**: 'Address signal' leads to connector **2**<sub>2</sub>.
+- A-3**: Leads to connector **9**<sub>2</sub>.
+- A-4**: Leads to signal **BITE 12**.
+- A-6**: Leads to signal **BITE 2**, which leads to connector **8**<sub>4</sub>.
+- 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**<sub>4</sub>. From connector **2**<sub>2</sub>, 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**<sub>4</sub>.
+- B-7**: Leads to signal **BITE 6**.
+- B-2**, **B-9**, and **B-10**: Lead to signal **BITE 20**, which leads to connector **7**<sub>4</sub>.
+- 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**<sub>4</sub>. 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

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
+
+| <i>State number</i> | <i>State description</i>  | <i>Sheet reference</i> |
+|---------------------|---------------------------|------------------------|
+| 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*
+
+P<sub>1</sub> - 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**

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.
+
+| <i>State number</i> | <i>State description</i>           | <i>Sheet reference</i> |
+|---------------------|------------------------------------|------------------------|
+| 00                  | Idle                               | 1, 4                   |
+| 01                  | Wait for call                      | 1                      |
+| 02                  | Set up information<br>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 |

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        |
+| <b>Signalling System No. 7 management</b>                | <b>Q.750-Q.759</b> |
+| 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/<br>Q.751.2/<br>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 |
+| <b>sccpAccountPackage (M)</b>                                              |                                                |         |
+| sccpAccountId (G, SBC)                                                     |                                                |         |
+| sccpLinkageSet (G, SBC, A-Rm)                                              |                                                |         |
+| operatorName (G, SBC)                                                      |                                                |         |
+| selectionGroupSetForAccounting (G, R, A-Rm, i)                             |                                                |         |
+| selectionGroupSetForVerification (G, R, A-Rm, i)                           |                                                |         |
+| <b>"ITU-T Rec. M.3100 (1995)":objectManagementNotificationsPackage (M)</b> |                                                |         |
+|                                                                            | "ITU-T Rec. X.721 (1992)":attributeValueChange |         |
+|                                                                            | "ITU-T Rec. X.721 (1992)":objectCreation       |         |
+|                                                                            | "ITU-T Rec. X.721 (1992)":objectDeletion       |         |
+| <b>"ITU-T Rec. Q.751.3 (1997)":controlPointerPackage (O)</b>               |                                                |         |
+| "ITU-T Rec. Q.751.3 (1997)":controlPointer (G, SBC)                        |                                                |         |
+| <b>"ITU-T Rec. Q.751.3 (1997)":measurementControlStatusPackage (O)</b>     |                                                |         |
+| "ITU-T Rec. Q.751.3 (1997)":measurementControlStatus (G, SBC)              |                                                |         |
+| <b>sccpAccountingNotificationsPackage (O)</b>                              |                                                |         |
+|                                                                            | sccpAccounting                                 |         |
+|                                                                            | sccpAccountingVerification                     |         |
+| <b>"ITU-T Rec. X.721 (1992)":topPackage (M,I)</b>                          |                                                |         |
+| objectClass (G)                                                            |                                                |         |
+| nameBinding (G)                                                            |                                                |         |
+| <b>"ITU-T Rec. X.721 (1992)":packagesPackage (C1,I)</b>                    |                                                |         |
+| packages (G)                                                               |                                                |         |
+| <b>"ITU-T Rec. X.721 (1992)":allomorphicPackage (C2,I)</b>                 |                                                |         |
+| 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
+
+| <b>terminatingAccountClassForAccounting (Cr WrOI, Del)</b>                                              |                                                |                |
+|---------------------------------------------------------------------------------------------------------|------------------------------------------------|----------------|
+| <b>Attributes</b>                                                                                       | <b>Notifications</b>                           | <b>Actions</b> |
+| <b>terminatingAccountClassForAccountingPackage (M)</b>                                                  |                                                |                |
+| terminatingAccountClassForAccountingId<br>(G, SBC)                                                      |                                                |                |
+| ruleSet (G, SBC, A-Rm)                                                                                  |                                                |                |
+| <b>"ITU-T Rec. M.3100 (1995)":objectManagementNotificationsPackage (M)</b>                              |                                                |                |
+|                                                                                                         | "ITU-T Rec. X.721 (1992)":attributeValueChange |                |
+|                                                                                                         | "ITU-T Rec. X.721 (1992)":objectCreation       |                |
+|                                                                                                         | "ITU-T Rec. X.721 (1992)":objectDeletion       |                |
+| <b>"ITU-T Rec. X.721 (1992)":topPackage (M,I)</b>                                                       |                                                |                |
+| objectClass (G)                                                                                         |                                                |                |
+| nameBinding (G)                                                                                         |                                                |                |
+| <b>"ITU-T Rec. X.721 (1992)":packagesPackage (C1,I)</b>                                                 |                                                |                |
+| packages (G)                                                                                            |                                                |                |
+| <b>"ITU-T Rec. X.721 (1992)":allomorphicPackage (C2,I)</b>                                              |                                                |                |
+| allomorphs (G)                                                                                          |                                                |                |
+| C1 Present if any registered package has been instantiated.<br>C2 Present if allomorphism is supported. |                                                |                |
+
+##### 6.5.2.4 terminatingAccountClassForVerification
+
+Table 4/Q.751.4 – terminatingAccountClassForVerification
+
+| <b>terminatingAccountClassForVerification (Cr WrOI, Del)</b>                                            |                                                |                |
+|---------------------------------------------------------------------------------------------------------|------------------------------------------------|----------------|
+| <b>Attributes</b>                                                                                       | <b>Notifications</b>                           | <b>Actions</b> |
+| <b>terminatingAccountClassForVerificationPackage (M)</b>                                                |                                                |                |
+| terminatingAccountClassForVerificationId<br>(G, SBC)                                                    |                                                |                |
+| ruleSet (G, SBC, A-Rm)                                                                                  |                                                |                |
+| <b>"ITU-T Rec. M.3100 (1995)":objectManagementNotificationsPackage (M)</b>                              |                                                |                |
+|                                                                                                         | "ITU-T Rec. X.721 (1992)":attributeValueChange |                |
+|                                                                                                         | "ITU-T Rec. X.721 (1992)":objectCreation       |                |
+|                                                                                                         | "ITU-T Rec. X.721 (1992)":objectDeletion       |                |
+| <b>"ITU-T Rec. X.721 (1992)":topPackage (M,I)</b>                                                       |                                                |                |
+| objectClass (G)                                                                                         |                                                |                |
+| nameBinding (G)                                                                                         |                                                |                |
+| <b>"ITU-T Rec. X.721 (1992)":packagesPackage (C1,I)</b>                                                 |                                                |                |
+| packages (G)                                                                                            |                                                |                |
+| <b>"ITU-T Rec. X.721 (1992)":allomorphicPackage (C2,I)</b>                                              |                                                |                |
+| allomorphs (G)                                                                                          |                                                |                |
+| C1 Present if any registered package has been instantiated.<br>C2 Present if allomorphism is supported. |                                                |                |
+
+##### 6.5.2.5 verificationRule
+
+Table 5/Q.751.4 – verificationRule
+
+| verificationRule (Cr WrOI, Del)                                            |                                                |         |
+|----------------------------------------------------------------------------|------------------------------------------------|---------|
+| Attributes                                                                 | Notifications                                  | Actions |
+| <b>verificationRulePackage (M)</b>                                         |                                                |         |
+| verificationRuleId (G, SBC)                                                |                                                |         |
+| ITU-T Rec. Q.751.2 (1997):gtAddressInformation (G, R)                      |                                                |         |
+| ITU-T Rec. Q.751.2 (1997):gtEncodingScheme (G, SBC)                        |                                                |         |
+| <b>"ITU-T Rec. M.3100 (1995)":objectManagementNotificationsPackage (M)</b> |                                                |         |
+|                                                                            | "ITU-T Rec. X.721 (1992)":attributeValueChange |         |
+|                                                                            | "ITU-T Rec. X.721 (1992)":objectCreation       |         |
+|                                                                            | "ITU-T Rec. X.721 (1992)":objectDeletion       |         |
+| <b>"ITU-T Rec. X.721 (1992)":topPackage (M,I)</b>                          |                                                |         |
+| objectClass (G)                                                            |                                                |         |
+| nameBinding (G)                                                            |                                                |         |
+| <b>"ITU-T Rec. X.721 (1992)":packagesPackage (C1,I)</b>                    |                                                |         |
+| packages (G)                                                               |                                                |         |
+| <b>"ITU-T Rec. X.721 (1992)":allomorphicPackage (C2,I)</b>                 |                                                |         |
+| 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 |
+| <b>verificationTranslatorPackage (M)</b>                                   |                                                |         |
+| 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)                                          |                                                |         |
+| <b>"ITU-T Rec. M.3100 (1995)":objectManagementNotificationsPackage (M)</b> |                                                |         |
+|                                                                            | "ITU-T Rec. X.721 (1992)":attributeValueChange |         |
+|                                                                            | "ITU-T Rec. X.721 (1992)":objectCreation       |         |
+|                                                                            | "ITU-T Rec. X.721 (1992)":objectDeletion       |         |
+| <b>"ITU-T Rec. X.721 (1992)":topPackage (M,I)</b>                          |                                                |         |
+| objectClass (G)                                                            |                                                |         |
+| nameBinding (G)                                                            |                                                |         |
+| <b>"ITU-T Rec. X.721 (1992)":packagesPackage (C1,I)</b>                    |                                                |         |
+| packages (G)                                                               |                                                |         |
+| <b>"ITU-T Rec. X.721 (1992)":allomorphicPackage (C2,I)</b>                 |                                                |         |
+| 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                                                   |
+| <b>Series Q</b> | <b>Switching and signalling</b>                                                                                                |
+| 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                                                                                                          |

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        |
+| <b>ISDN user part</b>                                    | <b>Q.760–Q.769</b> |
+| 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 |
+
+|                                                                                          | <b>Page</b> |
+|------------------------------------------------------------------------------------------|-------------|
+| 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                                                   |
+| <b>Series Q</b> | <b>Switching and signalling</b>                                                                                                |
+| 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\*

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
+
+|                                       | <i>Page</i> |
+|---------------------------------------|-------------|
+| 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 --