diff --git a/marked/Q/T-REC-Q.101-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.101-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..d55d34330c527d171e0e58c5bfdb5aeab81636ff
--- /dev/null
+++ b/marked/Q/T-REC-Q.101-198811-I_PDF-E/raw.md
@@ -0,0 +1,105 @@
+
+
+
+
+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.101**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**GENERAL RECOMMENDATIONS ON TELEPHONE
+SWITCHING AND SIGNALLING**
+
+**CLAUSES APPLICABLE TO ITU-T STANDARD
+SYSTEMS**
+
+---
+
+**FACILITIES PROVIDED IN INTERNATIONAL
+SEMI-AUTOMATIC WORKING**
+
+**ITU-T Recommendation Q.101**
+
+(Extract from the *Blue Book*)
+
+---
+
+# NOTES
+
+1 ITU-T Recommendation Q.101 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.1 FACILITIES PROVIDED IN INTERNATIONAL SEMI-AUTOMATIC WORKING**
+
+1.1.1 The operating methods used in the semi-automatic international service are described in the *Instructions for the International Telephone Service*. These operating methods assume the existence of equipment (operator's positions and automatic switching equipment) involving the following categories of operators:
+
+- a) *outgoing* operators;
+- b) *incoming* operators;
+- c) *delay* operators;
+- d) *assistance* operators;
+- e) *information* or *special service* operators.
+
+1.1.2 The *outgoing operator* controls the setting up of calls at the outgoing exchange. (From the operating point of view she is, in general, the controlling operator and is sometimes so referred to in the *Instructions*.)
+
+She must be able to set up calls to any one of the following points in the called country:
+
+- a) subscribers;
+- b) incoming operators at the incoming international exchange;
+- c) delay operators, especially a particular delay operator at the incoming international exchange;
+- d) incoming operators at a local manual exchange in the called country;
+- e) information or special service operators.
+
+The outgoing operator should be able to recall incoming and delay operators on calls set up via these operators, by sending a forward-transfer signal as defined in the relevant system specifications.
+
+1.1.3 The *incoming operator*1) at the incoming international exchange is obtained by using a special code 11 signal or a special number. The code 11 signal is a particular combination provided by the signal code. This operator performs the functions of an incoming operator in ordinary manual service for those calls which cannot be routed automatically at the incoming international exchange.
+
+1.1.4 The *delay operator* is obtained by using a special code 12 signal, or a special number. The code 12 signal is a particular combination provided by the signal code. The delay operator may be:
+
+- any of the operators of this category;
+- or a particular operator, or one of those operating a particular group of positions; her position or her group of positions is then indicated by a number which follows the code 12 signal or is indicated by the special number.
+
+With respect to the direction in which a required call is set up, the delay operator may be at the outgoing international exchange and may be called by an operator at the incoming international exchange. From the technical point of view and as far as signalling is concerned, however, the delay operator at the outgoing international exchange called back by an operator at an incoming international exchange must be regarded as being at the incoming end of the international circuit over which she has been called back.
+
+1.1.5 *Notes on incoming and delay operators*
+
+a) Incoming and delay operators must be able to speak the *service language* used for the route concerned, and hence may have to belong to a particular language group. A *language (or information) digit*, from 1 to 8, sent on all
+
+---
+
+1) Called alternatively in French "opératrice translatrice", see *Instructions for the International Telephone Service* (art. 125).
+
+semi-automatic calls, is used to obtain operators of a particular language group [see Recommendation Q.104]2).
+
+- b) It may be the same operator who acts as an incoming and as a delay operator, and even as an assistance operator. She enters a circuit in any of these capacities in response to the appropriate signal.
+- c) While an incoming or delay operator is being called, the national ringing tone of the incoming country must be sent back over the international circuit.
+
+1.1.6 The *assistance operator* at the incoming international exchange enters a semi-automatic circuit on a call already set up, when requested by the outgoing operator, because of language difficulties or, for instance, when she is required to interpret a national tone. Access to an assistance operator at an international transit exchange is not possible.
+
+The assistance operator is called by a forward-transfer signal, sent by the outgoing operator when, for example, she operates a key on the outgoing position. An assistance operator in a required language group is obtained in conjunction with the forward-transfer signal by the language digit (or information) sent previously during the setting up of the call. Hence the incoming relay set must store the language digit (or information).
+
+The outgoing operator receives no indication to show that the assistance operator is being called, or to show when she answers or withdraws from the circuit, but if necessary the outgoing operator can send the forward-transfer signal several times on the same call.
+
+The assistance operator must be able:
+
+- a) to break into the call as a third party (this she would do, for example, when the language spoken in the country of arrival is other than the service language used in that relation, and the operator intervenes as an interpreter);
+- b) to enter a circuit on one side only after having isolated the other. She does this, in particular, when she translates a verbal announcement or interprets an audible tone returned from the incoming end.
+
+In no circumstances will the assistance operator be able to block the international circuit.
+
+*Note* - It should be noted that the term "assistance operator" has a very definite meaning in CCITT documents. It stands for an operator who breaks in, as required, as a third party in a circuit already set up. Hence this operator must not be confused with any other operator in the incoming country who may help to *set up* the call in conjunction with the international outgoing operator. Assistance operators may not be available on intraregional circuits.
+
+1.1.7 The *information or special service operator* of the country of destination is obtained by using a special number. This operator is responsible for giving details concerning subscriber number and miscellaneous inquiries.
+
+---
+
+2) The language digit may not be used on some intraregional circuits.
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.106-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.106-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7
--- /dev/null
+++ b/marked/Q/T-REC-Q.106-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e
+size 7392
diff --git a/marked/Q/T-REC-Q.106-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.106-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..902d231b8a2d1a66539842ffb78738de5b322f7f
--- /dev/null
+++ b/marked/Q/T-REC-Q.106-198811-I_PDF-E/raw.md
@@ -0,0 +1,49 @@
+
+
+
+
+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.106**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**GENERAL RECOMMENDATIONS ON TELEPHONE
+SWITCHING AND SIGNALLING**
+
+**CLAUSES APPLICABLE TO ITU-T STANDARD
+SYSTEMS**
+
+---
+
+**THE SENDING - FINISHED SIGNAL**
+
+**ITU-T Recommendation Q.106**
+
+(Extract from the *Blue Book*)
+
+---
+
+## NOTES
+
+1 ITU-T Recommendation Q.106 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.6 THE SENDING-FINISHED SIGNAL**
+
+In semi-automatic working, when the international outgoing operator has finished keying or dialling, she operates a special button on her keyboard or a key so that, after the number, a local signal which is called a *sending-finished* signal is sent to the outgoing equipment to show that there are no more digits to follow. In automatic working, subscribers cannot show when they have finished dialling the number, and so this signal does not apply.
+
+*Note* - In semi-automatic working, local sending of the sending-finished signal will cause an *end-of-pulsing* signal to be sent on the international circuit 1) or signalling channel. This has the same function and shows the incoming equipment that there are no more digits to be received. In some cases also in automatic working, when the outgoing equipment decides that there are no more digits to follow, an end-of-pulsing signal is sent on the international circuit or signalling channel, for example in the ST condition of System No. 5 (see Recommendation Q.152).
+
+---
+
+1) In System R2 the sending of end-of-pulsing signal (code 15) may not occur if a *number-received* indication has already been received.
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.109-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.109-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..0498f884283128f1b30a626ba85dc6b8e724c9cc
--- /dev/null
+++ b/marked/Q/T-REC-Q.109-198811-I_PDF-E/raw.md
@@ -0,0 +1,49 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. A lightning bolt symbol is positioned to the right of the letters.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**Q.109**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**GENERAL RECOMMENDATIONS ON TELEPHONE
+SWITCHING AND SIGNALLING**
+
+**CLAUSES APPLICABLE TO ITU-T STANDARD
+SYSTEMS**
+
+---
+
+**TRANSMISSION OF THE ANSWER SIGNAL IN
+INTERNATIONAL EXCHANGES**
+
+**ITU-T Recommendation Q.109**
+
+(Extract from the *Blue Book*)
+
+---
+
+# NOTES
+
+1 ITU-T Recommendation Q.109 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.9 TRANSMISSION OF THE ANSWER SIGNAL IN INTERNATIONAL EXCHANGES**
+
+For the reasons given in Recommendation Q.27, it is necessary to reduce to a minimum the delays resulting from:
+
+- the conversion of the national answer signal into the international answer signal and vice versa; and
+- the transmission of the international answer signal over the international part of the connection,
+
+these delays being additional to any delays due to conversions and repetitions of the answer signal within the national systems of the incoming and outgoing countries.
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.113-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.113-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7
--- /dev/null
+++ b/marked/Q/T-REC-Q.113-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e
+size 7392
diff --git a/marked/Q/T-REC-Q.113-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.113-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..0335cbb0395b502aa78475f0cdda2fc5480014f9
--- /dev/null
+++ b/marked/Q/T-REC-Q.113-198811-I_PDF-E/raw.md
@@ -0,0 +1,63 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**Q.113**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**GENERAL RECOMMENDATIONS ON TELEPHONE
+SWITCHING AND SIGNALLING**
+
+**CLAUSES APPLICABLE TO ITU-T STANDARD
+SYSTEMS**
+
+---
+
+**CONNECTION OF SIGNAL RECEIVERS IN
+THE CIRCUIT**
+
+**ITU-T Recommendation Q.113**
+
+(Extract from the *Blue Book*)
+
+---
+
+# NOTES
+
+1 ITU-T Recommendation Q.113 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.2 CONNECTION OF SIGNAL RECEIVERS IN THE CIRCUIT**
+
+2.2.1 The line signal receivers are permanently connected to the 4-wire side of the circuit. The register signal receivers in System No. 5 are connected to the 4-wire side of the circuit when the register is associated with the circuit for the setting up of the call; the same is valid (in the international exchanges) for the register signal receivers in Systems R1 and R2.
+
+2.2.2 An in-band line signal receiver should be protected against disturbing currents (voice currents or possibly noise), coming from the near end of the circuit, by a buffer amplifier or other arrangement. The arrangement used should introduce an appropriate supplementary attenuation in such a manner that, at the point where the line signal receiver is connected, these disturbing currents are of such a level that they cannot:
+
+- operate the line signal receiver;
+- interfere with the reception of signals by operating the guard circuit of the line signal receiver.
+
+The additional attenuation introduced should in consequence take account of:
+
+- a) the relative level $n$ at the point where the signal receiver is connected (this relative level is obtained by assuming a zero relative level at the distant origin of the circuit);
+- b) the minimum permissible signal level at the input to the signal receiver, for example:
+ - $-18 + n$ dBm in the case of System No. 4 (see Recommendation Q.123 § 3.2.1),
+ - $-16 + n$ dBm in the case of System No. 5 (see Recommendation Q. 144 § 2.4.1);
+- c) the maximum permissible level for disturbing currents (voice currents and switching noise) coming from the near end of the circuit. The maximum level of voice current might be assumed to be, for example, $+10$ dBm0 in the direction *opposite* to that of the signals. The nature of the switching noises depends on the national systems used;
+- d) any attenuation (terminating set and possibly pads) between the point where the signal receiver is connected and the point where the near-end disturbing currents are considered;
+- e) a safety margin to give an appreciable reduction of the level of disturbing currents coming from the near end [as defined in c)] compared to the minimum level of the signal as defined in b).
+
+2.2.3 When a register-signal receiver is connected to the circuit, the exchange side of the circuit is disconnected and hence the receiver is not subject to near-end disturbances.
+
+2.2.4 The Recommendations of Volume III concerning international circuits must still be met after the connection of a signal sender and a signal receiver and of the switching equipment. In consequence, it is necessary to fix the limits of input and output impedance, insertion loss, attenuation distortion, non-linear distortion, balance, and crosstalk of line signal senders and receivers; an example of specification clauses concerning these conditions is given in Recommendation Q.114.
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.114-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.114-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..6849b99c00a66e0ff7bae7e9e6b8c0f45c13994a
--- /dev/null
+++ b/marked/Q/T-REC-Q.114-198811-I_PDF-E/raw.md
@@ -0,0 +1,104 @@
+
+
+
+
+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.114**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**GENERAL RECOMMENDATIONS ON TELEPHONE
+SWITCHING AND SIGNALLING**
+
+**CLAUSES APPLICABLE TO ITU-T STANDARD
+SYSTEMS**
+
+---
+
+**TYPICAL TRANSMISSION REQUIREMENTS
+FOR SIGNAL SENDERS AND RECEIVERS**
+
+**ITU-T Recommendation Q.114**
+
+(Extract from the *Blue Book*)
+
+---
+
+# NOTES
+
+1 ITU-T Recommendation Q.114 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.3 TYPICAL TRANSMISSION REQUIREMENTS FOR SIGNAL SENDERS AND RECEIVERS
+
+2.3.1 In-band line signal receivers (including the buffer amplifier or equivalent device), in §§ 2.3.2 to 2.3.7 below, apply only in the case where the signal receiver is a 4-terminal device ("quadrupole") and where the nominal circuit impedance is 600 ohms.
+
+### 2.3.2 *Input and output impedance*
+
+The nominal value of the input and output impedances of the signal receiver is 600 ohms.
+
+$Z_E$ and $Z_S$ , which are respectively the measured values of the input and output impedance of the signal receiver, should meet the following condition throughout the 300 to 3400 Hz frequency band:
+
+$$\left| \frac{Z_E - 600}{Z_E + 600} \right| \leq 0.35 \text{ and } \left| \frac{Z_S - 600}{Z_S + 600} \right| \leq 0.35.$$
+
+In making these measurements the free terminals should be looped by a resistance of 600 ohms and the voltage applied must not overload the equipment.
+
+### 2.3.3 *Attenuation*
+
+At 800 Hz, the insertion loss of the signal receiver, measured with a generator and a receiver of internal resistance of 600 ohms, must be between the limits:
+
+$$A \pm 0.5 \text{ decibel}$$
+
+The value $A$ is to be determined from the level diagram of the circuit according to the point of the circuit at which the signal receiver should be connected.
+
+The measurement is made with a 1 mW generator having an internal impedance equal to a pure resistance of 600 ohms and having an e.m.f. of $2 \times 0.775$ volt (so-called "standard generator"). The e.m.f. of the generator will be adjusted to take into account the relative level of the point of the circuit at which the signal receiver is connected.
+
+If $n$ is the relative level at the signal receiver input, the e.m.f. of the generator will therefore be:
+
+$$1.55 \cdot 10^{\frac{n}{20}} \text{ volts, if } n \text{ is expressed in decibels.}$$
+
+### 2.3.4 *Attenuation distortion*
+
+The variation in insertion loss of the signal receiver in the 300-3400 Hz frequency band, measured under the conditions of § 2.3.3 above, should not exceed the limits shown in Figure 1/Q.114.
+
+As in certain cases Systems No. 5, and R1 may be applied to circuits in transmission systems with a channel spacing of less than 4 kHz, the 300 Hz lower limit shown above may be replaced by 200 Hz for System No. 5.
+
+### 2.3.5 *Nonlinear distortion*
+
+The curve representing the variation (as a function of power) of the output level of the signal receiver, with reference to the nominal value of the output level, should be within the limits shown in Figure 2/Q.114 over the relevant frequency range.
+
+### 2.3.6 *Balance*
+
+The input and output of the signal receiver should have a high degree of balance to earth, the admittance of each terminal to earth being very low.
+
+The same clause should apply to the signal sender.
+
+
+
+Figure 1/Q.114: Attenuation distortion of the signal receiver. A graph showing attenuation in dB versus frequency in Hz. The y-axis ranges from -0.2 to +0.5 dB. The x-axis has markers at 300, 600, 800, 2400, and 3400 Hz. The graph shows a shaded region between +0.2 dB and +0.5 dB from 300 Hz to 2400 Hz, and another shaded region between -0.2 dB and +0.5 dB from 2400 Hz to 3400 Hz. The text 'CCITT - 48 501' is at the bottom right.
+
+FIGURE 1/Q.114
+Attenuation distortion of the signal receiver
+
+
+
+Figure 2/Q.114: Limits for nonlinear distortion due to the insertion of the signal receiver. A graph showing the variation of the output level in dB versus the power level applied to the input in dBm0. The y-axis ranges from -0.2 to +0.2 dB. The x-axis has a marker at 3.5 dBm0. The graph shows a shaded region between -0.2 dB and +0.2 dB up to 3.5 dBm0. The text 'CCITT - 48 511' is at the bottom right. A note indicates: 'Power level applied to the input of the signal receiver and referred to zero relative level'.
+
+FIGURE 2/Q.114
+Limits for nonlinear distortion due to the insertion of the signal receiver
+
+### 2.3.7 *Crosstalk between adjacent signal receivers*
+
+The crosstalk ratio between two adjacent signal receivers should not be less than 74 dB in the relevant frequency band.
+
+2.3.8 During the register signalling period no speech transmission takes place. It is not essential therefore for the register signalling equipment of systems having separate equipment for that purpose to take account of §§ 2.3.2 to 2.3.7 above but it is desirable to adopt appropriate clauses for efficient signalling performance.
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.118bis-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.118bis-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7
--- /dev/null
+++ b/marked/Q/T-REC-Q.118bis-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e
+size 7392
diff --git a/marked/Q/T-REC-Q.1200-199709-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1200-199709-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..51b5ec8c2bb45138f684cb022794b43c6b85e609
--- /dev/null
+++ b/marked/Q/T-REC-Q.1200-199709-I_PDF-E/raw.md
@@ -0,0 +1,364 @@
+
+
+
+
+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.1200**
+
+(09/97)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Intelligent Network
+
+# --- **General series Intelligent Network Recommendation structure**
+
+ITU-T Recommendation Q.1200
+
+(Previously CCITT Recommendation)
+
+---
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## **SWITCHING AND SIGNALLING**
+
+| | |
+|----------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 |
+| DIGITAL EXCHANGES | Q.500-Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 |
+| INTELLIGENT NETWORK | Q.1200-Q.1999 |
+| BROADBAND ISDN | Q.2000-Q.2999 |
+
+*For further details, please refer to ITU-T List of Recommendations.*
+
+## **ITU-T RECOMMENDATION Q.1200**
+
+# **GENERAL SERIES INTELLIGENT NETWORK RECOMMENDATION STRUCTURE**
+
+## **Summary**
+
+This Recommendation explains the structure of the Q.1200-series Intelligent Network (IN) Recommendations and provides the outline of all general (i.e. Q.120x-series) Recommendations.
+
+## **Source**
+
+ITU-T Recommendation Q.1200 was revised by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 12th of September 1997.
+
+# FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
+
+The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+# NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+# INTELLECTUAL PROPERTY RIGHTS
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 1999
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+# CONTENTS
+
+*Page*
+
+| | | |
+|---|-----------------------------------------------------------|---|
+| 0 | Introduction ..... | 1 |
+| 1 | General structure ..... | 1 |
+| 2 | Q-series Intelligent Network Recommendation overview..... | 1 |
+
+
+
+# **GENERAL SERIES INTELLIGENT NETWORK RECOMMENDATION STRUCTURE**
+
+*(revised in 1997)*
+
+# **0 Introduction**
+
+A block of one hundred numbers has been set aside in the Q series for the development of Intelligent Network (IN) Recommendations. This Recommendation, the first in that series, has been developed to organize the Recommendations in a meaningful way in order to assist users in locating topics of interest. It defines the structure of the Q.1200-series Recommendations and assigns blocks of numbers to the groupings of IN capabilities known as Capability Sets (CSs) and blocks of numbers for general and vocabulary sections. In addition, this Recommendation provides a structural overview of the content of each Recommendation.
+
+This Recommendation has been developed with a long range view in mind. By assigning blocks of numbers to each capability set (CS-1, CS-2, CS-n), an organized, parallel structure across capability sets can be maintained; for example, CS-1 has been assigned the Q.121x block of numbers and CS-2 the Q.122x block of numbers.
+
+Associated work has been documented in the I-series Recommendations. For the sake of consistency, Recommendations Q.1201, Q.1202 and Q.1203 have been assigned numbers in the I-series Recommendations (I.312, I.328 and I.329, respectively).
+
+## **1 General structure**
+
+Table 1 shows the overall Q.1200-series Intelligent Network Recommendation structural distribution through the "ten" digits (1201, 1211, 1221, etc.) and the "one" digits (i.e. 1201, 1211, 1221, etc.).
+
+**Table 1/Q.1200 – Recommendation framework structure**
+
+| | |
+|-----------------------------------------------------------------------------|-------------------------------------------|
+| 00 – General | |
+| 10 – CS-1 | 1 – Principles introduction |
+| 20 – CS-2 | 2 – Service plane (not included for CS-1) |
+| 30 – CS-3 | 3 – Global functional plane |
+| 40 – CS-4 | 4 – Distributed functional plane |
+| 50 – CS-5 | 5 – Physical plane |
+| 60 – CS-6 | 6 – For future use |
+| 70 – CS-7 | 7 – For future use |
+| 80 – CS-8 | 8 – Interface Recommendation |
+| 90 – Glossary | 9 – Intelligent Network user's guide |
+| NOTE 1 – 1200 is assigned as for the IN Recommendation framework structure. | |
+| NOTE 2 – 1290-series has been set aside for the glossary. | |
+
+## **2 Q-series Intelligent Network Recommendation overview**
+
+### **Q.1200 – General series Intelligent Network Recommendation structure**
+
+- 0 Introduction
+- 1 General structure
+- 2 Q-series Intelligent Network Recommendation overview
+
+### **I.312/Q.1201 – Principles of Intelligent Network architecture**
+
+- 1 Objectives, overall description
+ - 1.1 Motivation, objectives, scope of Intelligent Network
+ - 1.1.1 Motivation
+ - 1.1.2 Objectives of Intelligent Network
+ - 1.1.3 Scope of Intelligent Network
+ - 1.2 Definition of Intelligent Network
+ - 1.3 Evolution of Intelligent Network Recommendations
+ - 1.3.1 General considerations on the standardization process
+ - 1.3.2 Recommendation areas
+ - 1.3.3 Phased standardization and definition of capability sets
+- 2 IN functional requirements
+ - 2.0 Introduction
+ - 2.1 Service requirements
+ - 2.1.1 Overall requirements
+ - 2.1.2 Service creation
+ - 2.1.3 Service management
+ - 2.1.4 Service processing
+ - 2.1.5 Service interworking
+ - 2.2 Network requirements
+ - 2.2.1 Overall requirements
+ - 2.2.2 Service creation
+ - 2.2.3 Service management
+ - 2.2.4 Network management
+ - 2.2.5 Service processing
+ - 2.2.6 Network interworking
+- 3 IN architectural concept
+ - 3.1 IN Conceptual Model (INCM)
+ - 3.1.1 Service plane
+ - 3.1.2 Global functional plane
+ - 3.1.3 Distributed functional plane
+ - 3.1.4 Physical plane
+ - 3.1.5 Relationship with the 3-stage method
+ - 3.1.6 Service logic
+ - 3.1.7 Application Programming Interface (API)
+ - 3.1.8 Relationships among different planes
+ - 3.1.9 Service interaction
+ - 3.1.10 Service and network interworking
+ - 3.1.11 Management functionality
+- 4 Intelligent Network (IN) long-term architecture framework
+ - 4.1 Introduction
+ - 4.2 Intelligent Network Conceptual Model
+ - 4.3 Architecture structure
+ - 4.3.1 Logical architecture
+ - 4.3.2 Physical architecture
+ - 4.3.3 Open distributed processing view
+ - 4.4 Service considerations
+ - 4.4.1 Service/service feature interaction
+ - 4.5 Technology basis
+ - 4.5.1 Broadband capabilities
+ - 4.5.2 Distributed processing
+ - 4.5.3 Open Systems Interconnection (OSI)
+ - 4.5.4 Object-oriented modelling
+ - 4.5.5 Information technology
+ - 4.5.6 Cooperative processing
+ - 4.5.7 Distributed control
+ - 4.5.8 Management of services and networks
+ - 4.5.9 Verification/validation
+ - 4.5.10 Artificial intelligence
+
+### **I.328/Q.1202 – Intelligent Network Service plane architecture**
+
+- 1 General
+- 2 Service plane architecture
+ - 2.0 General
+ - 2.1 Characterization of services and service capability requirements
+ - 2.2 Service plane modelling
+ - 2.3 Service and service feature interaction
+ - 2.3.1 The service and feature interaction problem
+ - 2.3.2 A solution: Which one?
+ - 2.3.3 A solution: When?
+ - 2.3.4 A solution: How?
+
+Annex A – Alphabetical list of abbreviations used in this Recommendation
+
+Annex B – A thesaurus of examples
+
+- B.1 General
+- B.2 Call Forwarding Unconditional and Terminating Key Code Screening
+ - B.2.1 First case
+ - B.2.2 Second case
+- B.3 Call Forwarding Unconditional and Automatic Call Back
+ - B.3.1 First case
+ - B.3.2 Second case
+- B.4 Call Forwarding Unconditional and Terminating Call Screening
+
+### **I.329/Q.1203 – Intelligent Network global functional plane architecture**
+
+- 1 General
+- 2 Scope of IN global functional plane architecture
+- 3 References
+- 4 Global functional plane modelling
+- 5 Service independent building blocks
+ - 5.1 Definition of an SIB
+ - 5.2 Characteristics of an SIB
+ - 5.3 Data parameters for SIBs
+ - 5.4 Method to describe SIBs
+ - 5.5 Flowchart analysis
+ - 5.6 Interaction management
+ - 5.6.1 Interaction between SIBs
+- 6 Basic call process
+ - 6.1 General
+ - 6.2 Basic call process functionality
+- 7 Global service logic
+ - 7.1 General
+
+Annex A – Alphabetical list of abbreviations used in this Recommendation
+
+### **Q.1204 – Intelligent Network distributed functional plane architecture**
+
+- 1 General
+- 2 Distributed functional plane model
+ - 2.1 Explanation of diagram
+ - 2.1.1 Functional entities
+ - 2.1.2 Relationships
+ - 2.3 Definition of functional entities related to IN service execution
+ - 2.4 Definition of IN service creation/management related functional entities
+
+- 3 Functional entity call/service logic processing models
+ - 3.1 General
+ - 3.2 Modelling objectives/criteria
+ - 3.2.1 Call modelling objectives/criteria
+ - 3.2.2 Modelling of service logic processing objectives/criteria
+ - 3.3 General assumptions
+ - 3.3.1 Scope of functional entity call/service logic processing models
+ - 3.3.2 Relation to IN conceptual model
+ - 3.3.3 Use of functional entity call/service logic processing models
+ - 3.3.4 Other considerations
+ - 3.4 Overview of call/service logic processing related functional entities
+ - 3.5 Call/service logic processing functional entity models
+ - 4 Relationship between functional entities
+ - 4.1 General
+ - 4.2 Relationships
+ - 4.3 Information flows between functional entities
+ - 5 Mapping the global functional plane to the distributed functional plane
+ - 5.1 Mapping requirements
+ - 5.2 Relationship to IN conceptual model
+ - 5.3 An example of mapping some selected SIBs to functional entities
+- Annex A – Example basic call state model (BCSM)
+- Annex B – Object-oriented finite state machine modelling
+- Annex C – Call segment model
+
+### **Q.1205 – Intelligent Network physical plane architecture**
+
+- 1 General
+- 2 Requirements and assumptions
+ - 2.1 Requirements
+ - 2.2 Assumptions
+- 3 Physical entities (PEs)
+- 4 Mapping the distributed functional plane to the physical plane
+ - 4.1 Mapping of functional entities to physical entities
+ - 4.2 Selection of underlying protocol platforms
+- 5 User interfaces
+
+### **Q.1208 – General aspects of the Intelligent Network application protocol**
+
+- 1 Introduction
+- 2 Background
+- 3 Definition methodology
+- 4 Evolutionary requirements
+
+### **Q.1210 – Q.1210-series Intelligent Network Recommendation structure**
+
+- 1 General Q.1200-series structure
+- 2 Q.121x-series Intelligent Network Recommendation overview
+
+### **Q.1220 – Q.1220-series Intelligent Network Capability Set 2 Recommendation structure**
+
+- 0 Introduction
+- 1 General Q.1200-series structure
+- 2 Q.121x-series Intelligent Network Recommendation overview
+
+### **Q.1230 – Q.1230-series Intelligent Network Capability Set 3**
+
+- 1 General Q.1200-series structure
+- 2 Q.123x-series Intelligent Network Recommendation overview
+
+### **Q.1290 – Glossary of terms used in the definition of Intelligent Networks**
+
+- 1 General
+ - 1.1 Introduction
+ - 1.2 Conventions
+- 2 Terms and definitions (listed alphabetically)
+
+Annex A – Acronyms
+
+
+
+# ITU-T RECOMMENDATIONS SERIES
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of the ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure |
+| Series Z | Programming languages |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.1208-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1208-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36a32fb27730598abaef54b051cf1fffedc17599
--- /dev/null
+++ b/marked/Q/T-REC-Q.1208-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c315972c25456ec61dce423cf7bdb17e9326e1a8465e66d166c5dfadaf26aa35
+size 8270
diff --git a/marked/Q/T-REC-Q.1208-199709-I_PDF-E/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Q/T-REC-Q.1208-199709-I_PDF-E/d0abac95583b52a3b35f74a215567334_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fee4b1be1f7e76baf5dc6ec8b4e27f5b5a0ea80b
--- /dev/null
+++ b/marked/Q/T-REC-Q.1208-199709-I_PDF-E/d0abac95583b52a3b35f74a215567334_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:03f9d45627b625858f20174dae594354465ab0cf5f00d1560e2de415f24ba258
+size 21628
diff --git a/marked/Q/T-REC-Q.1208-199709-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1208-199709-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..fd6710e953b462a8878650effccb7f8b7901b0b4
--- /dev/null
+++ b/marked/Q/T-REC-Q.1208-199709-I_PDF-E/raw.md
@@ -0,0 +1,196 @@
+
+
+
+
+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.1208**
+
+(09/97)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Intelligent Network
+
+# --- **General aspects of the Intelligent Network Application protocol**
+
+ITU-T Recommendation Q.1208
+
+(Previously CCITT Recommendation)
+
+---
+
+## ITU-T Q-SERIES RECOMMENDATIONS
+
+## **SWITCHING AND SIGNALLING**
+
+| | |
+|----------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+
+*For further details, please refer to ITU-T List of Recommendations.*
+
+## **ITU-T RECOMMENDATION Q.1208**
+
+# **GENERAL ASPECTS OF THE INTELLIGENT NETWORK APPLICATION PROTOCOL**
+
+## **Summary**
+
+The objective of this Recommendation is to specify the definition methodology to be applied to the Intelligent Network application protocol Recommendations defined in specific capability sets. This Recommendation is not expected to change greatly in future versions with the possible exception of additional specification mechanisms.
+
+Associated standardization work is contained in all of the Q.12xx IN Recommendations and more particularly in the Q.12x8 INAP Recommendations.
+
+### **Source**
+
+ITU-T Recommendation Q.1208 was revised by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 12th of September 1997.
+
+## FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
+
+The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 1998
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+## CONTENTS
+
+| | Page |
+|----------------------------------------------------------------------|-------------|
+| 1 Introduction ..... | 1 |
+| 2 Background..... | 1 |
+| 3 Definition methodology..... | 1 |
+| 4 Evolutionary requirements ..... | 1 |
+| 4.1 Rules for adding new parameters to INAP..... | 2 |
+| 4.2 Rules/guidelines for development of IN call party handling ..... | 2 |
+
+
+
+# **GENERAL ASPECTS OF THE INTELLIGENT NETWORK APPLICATION PROTOCOL**
+
+*(revised in 1997)*
+
+## **1 Introduction**
+
+This Recommendation defines the general aspects of the interfaces and protocols. For the detailed protocols and interfaces supported in each capability set, refer to the Q.12x8 Recommendation for that capability set.
+
+## **2 Background**
+
+All the work on interface specifications is based on the IN Functional Model (INFM). Each capability set will support a number of the interfaces defined in that model appropriate to the requirements placed upon that capability set.
+
+## **3 Definition methodology**
+
+The definition of the protocol can be split into three sections:
+
+- the definition of the service which the protocol provides (primitives etc.);
+- the definition of the operations transferred between entities;
+- the definition of the actions taken at each entity as a result of performing the operations.
+
+The primitives are defined in a tabular notation and may be omitted. The operation definitions are in Abstract Syntax Notation 1 (ASN.1, see Recommendation X.680). The actions are defined in terms of state transition diagrams. Other definition techniques may be used in future capability sets to supplement or replace these if this seems appropriate.
+
+The INAP is a ROSE user protocol (see Recommendation X.219/X.229). The ROSE protocol is contained within the component sublayer of TCAP (see Recommendations Q.771 to Q.775) and DSS 1 (Recommendation Q.932). At present the ROSE APDUs are conveyed in transaction sublayer messages in SS No. 7 and in the Q.931 REGISTER, FACILITY and call control messages in DSS 1. Other supporting protocols may be added at a later date.
+
+The INAP (as a ROSE user) and the ROSE protocol have been specified using ASN.1. At present, the only standardized way to encode the resulting PDUs is the basic encoding rules (see Recommendation X.690). The protocols should be defined in such a way that the functional entities defined in the INFM may be mapped into physical entities in any way that operators and manufacturers desire.
+
+## **4 Evolutionary requirements**
+
+The use of the application context negotiation mechanism (as defined in the Q.77x-Series Recommendations) allows the two communicating entities to identify exactly what their capabilities (and therefore the capabilities required on the interface) are. Where possible, this should be used to allow evolution through capability sets.
+
+Capability sets should always be defined as supersets of previous capability sets to ensure successful interworking with previous capability sets is possible. This may not apply where errors are found in previous capability sets.
+
+### 4.1 Rules for adding new parameters to INAP
+
+The objective of the rules is to achieve alignment and to avoid clashes between ITU-T CS-x and implementations based upon the regional standards that emanated from earlier versions of CS-x Recommendations. For network-specific parameters which are included in the Recommendations, context specific tags will be used. Rules for context specific tagging are:
+
+- 1) Originally defined Q.12x8 tag values shall be maintained in subsequent capability sets.
+- 2) In case parameters are removed from a defined Q.12x8, the corresponding tag values remain reserved.
+- 3) In case a regional defined parameter is adopted by the ITU-T, the regional defined tag values are also considered.
+- 4) The following structure for tag value allocation shall be used:
+
+
+
+| | | | | | | | | | |
+|-------------------|---|---|-----|-----------------------------------------|-----|----|---------------------------|-----------|--|
+| Q.1218 parameters | | | | Regional standard
adopted parameters | | | Future Capability Set use | | |
+| → | | | | ← | | | → | | |
+| 0 | 1 | 2 | ... | x | ... | 30 | 31 | ... n ... | |
+
+Diagram showing tag value allocation for INAP parameters. It is divided into three sections: 'Q.1218 parameters' (tags 0, 1, 2, ..., x), 'Regional standard adopted parameters' (tags ..., 30), and 'Future Capability Set use' (tags 31, ..., n ...). Arrows indicate the flow and scope of each section.
+
+When a new data type is to be added to an existing sequence of data types with an extension marker (...) and the new data type can be ignored when the receiving system is an implementation of an older INAP version, the new data type shall be added at the end of the sequence, after the extension marker. When the new data type cannot be ignored, the new data type shall be positioned before the extension marker, before the last mandatory parameter. The ITU-T shall allocate tag values starting from 0 upwards (as shown above). Regional bodies may then use tag values from 30 downwards for their additions to the Q.12x8 Recommendation. If the ITU-T adopts a parameter for INAP from such a regional standard, the tag value will also be adopted, in order to ensure compatibility. When all tag values from 0 to 30 have been allocated between Q.12x8 and regional standards, tag allocation by the ITU-T will continue from 31 upwards.
+
+### 4.2 Rules/guidelines for development of IN call party handling
+
+The information used to synchronize the SSF and SCF with the Connection View State should be as generic as possible, to allow flexibility. Allowing different operators to support differing transitions and priorities for feature interactions, thereby enabling competition. The IFs and IEs should specify the modified use of Legs and Call Segments by LegID and Call Segment ID. This also applies to commands initiated by the SCF, both bidirectional (class 1) and unidirectional (class 2) messages.
+
+These requirements also provide a flexible view to evolve to the IN/B-ISDN requirements being developed by the ITU-T, where the addition and removal of parties and bearers should be completely flexible.
+
+## ITU-T RECOMMENDATIONS SERIES
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of the ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure |
+| Series Z | Programming languages |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/042af54276c75e7b7b48a3af1f0a84e5_img.jpg b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/042af54276c75e7b7b48a3af1f0a84e5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f7ccff2fd08eff9f29c82cce7efbfadd82006db0
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/042af54276c75e7b7b48a3af1f0a84e5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4115e66089ed2b8eb64ed2a08f3d2b358a51f5ecaa02f3a5bdf48b9bf8331030
+size 9550
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6adb8452e0839d3b3e7395397bf7ac19666a2432
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a0b8de0bde776fa456c77cb46fc61863ecc70eb4f52969ac2390c080064b52f5
+size 144185
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5ffff7a1054d8765600972a4077a58367f301767
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d7680f255e63a44b5b55843947e08228e3e97ed2ecf159c9451f139edaa3ee07
+size 9866
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/212c50c4e3d043c989037a01e13c1a98_img.jpg b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/212c50c4e3d043c989037a01e13c1a98_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b950efb09a36cce84b5201e7cb6572fcb79b18f8
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/212c50c4e3d043c989037a01e13c1a98_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a99f5b2c7f3efb5e307723014026cd5c0418d127fdf93ff3753cf2dba7e6ee9f
+size 149857
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0367bcedb79fde112f337643bf62686bcf476670
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ed50eb7b97340444a3bbc7ca6dc0235ad3b1554fa6a6707292697e99b9a1b144
+size 10065
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4774b3a190fdc9f65b8ae6259a55d3a725a7dd4a
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e646b535623af01c7c140e1a16eb3827d9384182b9f72383794dfee880e853f
+size 8208
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/329c96049bb432e9c2cbda4e224a0c9c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..df5dedc23dab2c478aa3dd0ed8c240057ecd8b6f
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/329c96049bb432e9c2cbda4e224a0c9c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2fd6518b07322bb6a6aedb90052ca4297230c2632d986126a939a1ee76738259
+size 155741
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/3337af75dfee8af7687b4f49914d6c93_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0f9f641418cf2eba8bd6927962ba243033e1199d
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/3337af75dfee8af7687b4f49914d6c93_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:633a65ba795b6e76cab2845f75263ea43323f139ad7a8b22f2fb99a04fbe8ea8
+size 158303
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/40ebe9179df298f1b6d76822f28d90aa_img.jpg b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/40ebe9179df298f1b6d76822f28d90aa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b64787d9adc2ce854b072a32c8fd60dacccefee8
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/40ebe9179df298f1b6d76822f28d90aa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:511a2d92b566d26680a510de39a97bf222f98128c7641463f8a7d409dbb6239b
+size 12321
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/575d7d345b3ec04393bb2ec720ebabca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0ce8f062d8f5df83af3d5c738d163d90d5eee087
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/575d7d345b3ec04393bb2ec720ebabca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d8c0222e9213502415019f8de96927feeeef10f6963e863654c803334560a329
+size 181043
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/838c31609fac483fa2c01c7896a2fd6d_img.jpg b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/838c31609fac483fa2c01c7896a2fd6d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0d21666821b5fd4245735bff1ae901cb1eb4263c
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/838c31609fac483fa2c01c7896a2fd6d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f87e20f1bfc4ced0238cb692d7e219e0d8a2f3f2d59c5d478681a4906240d7df
+size 206975
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..18a868c97f9f790c127dcc60197852aaeae1effe
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4b64bfb9ab1f23394a626534a123ccd2eba93dbad18e76e876003a0b08cfc6b0
+size 9508
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fd2ce837accecfc59f26e6d8c459e31385bfcece
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1fa684100eb062630d216e4a49a9da8d7c572fb6236722f73535e856d9b6b96e
+size 71287
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/9cd85f266cdb1fb3ad544eb3dd3bd5e4_img.jpg b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/9cd85f266cdb1fb3ad544eb3dd3bd5e4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..578327a02b3e0a8e95540e55039c1a9f4d5aa973
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/9cd85f266cdb1fb3ad544eb3dd3bd5e4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e46eb9b1020fabaaeeac6725e8bdd8d800afc672fe5b7f8f34c8bf3d7b3e4d3c
+size 172864
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..86f8f6ba5ade8a5161ec030afda8be6acadc4c03
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:53a3399cc93beae4ff5c873d0d8de3c75efec362fad8ca9aa2654ab5b2b3b9ad
+size 216164
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e08b9f6e03634de0442d673b0dc26d34ed894650
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3258a1f81ccb7e389f3b77bca4af9d4aed0cca2b25a945971f14da4799ac4486
+size 162388
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/fcbc3c31776721edc98ceb1944ec438f_img.jpg b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/fcbc3c31776721edc98ceb1944ec438f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a5e1cf6cd0335b9ffc85f8f7a8e7baba172f601b
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/fcbc3c31776721edc98ceb1944ec438f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c1c5655515fb197f85c96a57d2b6227dbc2f4d3daad5d4c7edf56e7f4271cfc
+size 232340
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d6ccdb5073410755359afca9e49ad567c1658943
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5f964f3e15c4bbf6534f862f8a3f4ed2635a25cc0f3906545e0ab2d6ae599578
+size 9800
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/feae5a5b6e128162dbced0860fd97b9b_img.jpg b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/feae5a5b6e128162dbced0860fd97b9b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c4283ab3e740a4d8a78c51b39f809e82202db859
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/feae5a5b6e128162dbced0860fd97b9b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cdc434f97f6d49a9f31105466540b8825a14a9b18e2c7d2db08e092e98464437
+size 152481
diff --git a/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..343181f7d689f1478cf3ad01a29209f6c95c2758
--- /dev/null
+++ b/marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/raw.md
@@ -0,0 +1,1850 @@
+
+
+
+
+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.140-Q.180**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(11/1988)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+# --- **Specifications of Signalling System No. 5**
+
+ITU-T Recommendations Q.140-Q.180
+
+(Formerly CCITT Recommendations)
+
+---
+
+## 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 SYSTEM No. 4 | Q.120–Q.139 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 5 | Q.140–Q.199 |
+| 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 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# **Specifications of Signalling System No. 5**
+
+## **Source**
+
+ITU-T Recommendations Q.140-Q.180 were prepared by CCITT Study Group XI (1985-1988) and approved by WTSC in Melbourne on 25 November 1988. Those texts include the amendments to ITU-T Recs. Q.141 and Q.144 by WTSC on 12 March 1993. Those texts were originally published in Blue Book, Fascicle VI.2.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSC Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2002
+
+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
+
+# Specifications of Signalling System No. 5
+
+| Rec. No. | | Page |
+|----------|----------------------------------------------------------------------------------------------|------|
+| Q.140 | Definition and function of signals..... | 3 |
+| Q.141 | Signal code for line signalling..... | 6 |
+| Q.142 | Double seizing with both-way operation..... | 11 |
+| Q.143 | Line signal sender ..... | 12 |
+| Q.144 | Line signal receiver ..... | 13 |
+| Q.145 | Splitting arrangements ..... | 15 |
+| Q.146 | Speed of switching in international exchanges ..... | 16 |
+| Q.151 | Signal code for register signalling..... | 17 |
+| Q.152 | End-of-Pulsing conditions – Register arrangements concerning ST (end-of-pulsing) signal .... | 18 |
+| Q.153 | Multifrequency signal sender..... | 19 |
+| Q.154 | Multifrequency signal receiver..... | 20 |
+| Q.155 | Analysis of digital information for routing ..... | 21 |
+| Q.156 | Release of international registers ..... | 21 |
+| Q.157 | Switching to the speech position..... | 22 |
+| Q.161 | General arrangements for manual testing..... | 23 |
+| Q.162 | Routine testing of equipment (local maintenance)..... | 23 |
+| Q.163 | Manual testing..... | 24 |
+| Q.164 | Testing equipment for checking equipment and signals ..... | 27 |
+| Q.180 | Interworking of systems No. 4 and No. 5 ..... | 43 |
+
+
+
+# SPECIFICATIONS OF SIGNALLING SYSTEM No. 5
+
+## INTRODUCTION
+
+## PRINCIPLES OF No. 5 SIGNALLING SYSTEM
+
+### General
+
+System No. 5 is compatible with both TASI1) and non-TASI-equipped circuits and may be applied for automatic and semi-automatic operation and both-way working. It requires four-wire signalling and automatic access to the outgoing circuits.
+
+The signalling equipment is in two parts:
+
+- a) line signalling – for the so-called supervisory signals; and
+- b) register signalling – for the numerical signals.
+
+#### a) *Line signalling*
+
+This is a link-by-link system using two in-band signalling frequencies 2400 Hz and 2600 Hz, two frequencies, instead of one frequency, being adopted for the following reasons:
+
+- i) Automatic detection of double seizing on both-way working;
+- ii) Frequency discrimination between signals, no time discrimination being incorporated.
+
+Automatic detection of double seizing requires that the frequency of the proceed-to-send signal (2600 Hz) be different from that of the seizing signal (2400 Hz). The detection is achieved when one end transmits the outgoing seizing signal (2400 Hz) and at the same time receives the seizing signal (2400 Hz) from the other end and not the 2600 Hz proceed-to-send signal expected.
+
+All signal recognition times are the same (125 ms) except for the seizing and proceed-to-send signals (40 ms). These two signals are not subject to signal imitation by speech and fast signalling is desired in particular to minimize double seizings.
+
+To avoid, with this signalling system, relatively slow signalling in non-TASI applications and in lightly loaded conditions (the more usual) of TASI applications, all signals are the continuous compelled2) type except the forward transfer signal. Continuous signals ensure TASI trunk/channel association during the actual time this function requires. (The alternative of TASI-prefix pulse type signals would, due to the 500-ms TASI prefix, introduce a slight risk of failure to associate a trunk with a channel, and would slow the signalling in terms of restoration of the transmission path after the signalling line splits under the more usual conditions of TASI loading and in non-TASI applications.) Only the forward-transfer signal is a TASI-prefixed pulse since for this signal a slight risk of failure can be accepted because it is operator-controlled and may be repeated at will.
+
+---
+
+1) See Supplement No. 2 in Orange Book, Volume VI.1 (1976).
+
+2) See for this term Recommendation Q.141, § 2.1.6
+
+Except for the answer signal, all the compelled signals are normal compelled3) type. For reasons of fast speed, the answer signal is overlap-compelled4) at transit points. Fast answer signalling is desirable to minimize the risk of an abandoned call by either the called or calling party, should the verbal answer be lost due to the line splitting on answer signalling.
+
+#### b) *Register signalling*
+
+This is a link-by-link 2/6 multifrequency (m.f.) in-band en bloc4) pulse signalling system, forward signalling only. The alternative, continuous compelled signalling, would be slow due to the long circuit propagation times in certain applications. The frequencies (700 Hz . . . 1700 Hz) are outside of the line signalling frequencies. The numerical information signalling is preceded by a KP signal (start-of-pulsing) and terminated by an ST signal (end-of-pulsing). En bloc non-overlap sending4) applies at the outgoing international register, the seizing signal being sent, and thus the international circuit being taken as late as possible, namely when the ST condition is available in the outgoing international register. When sending, the outgoing register pulses out in a continuous sequence. The prior GO trunk/channel association due to the seizing signal is maintained by the TASI speech detector hangover during the interval between cessation of the seizing signal (on receipt of the proceed-to-send signal) and the start of the register pulse out, and during the intervals between successive m.f. signals.
+
+En bloc overlap register signalling4) applies at the international transit registers and at the incoming international register to minimize the post-dialling delay.
+
+Compandors affect signalling, particularly short-pulse compound signalling (e.g. register signalling), due to distortion and the production of intermodulation frequencies. By virtue of the lin-by-link signalling and the adopted duration of the m.f. pulses, system No. 5 functions correctly in the presence of compandors.
+
+---
+
+3) See for these terms Recommendation Q.141, § 2.1.7.
+
+4) See for these terms footnote to Recommendation Q.151, § 3.1.1
+
+## CHAPTER I
+
+## DEFINITION AND FUNCTION OF SIGNALS
+
+#### Recommendation Q.140
+
+### 1. DEFINITION AND FUNCTION OF SIGNALS
+
+#### 1.1 **seizing signal (sent in the forward direction)**
+
+This signal is transmitted at the beginning of a call to initiate circuit operation at the incoming end of an international circuit and to seize equipment for switching the call either to the national network of the incoming country or to another international exchange.
+
+#### 1.2 **proceed-to-send signal (sent in the backward direction)**
+
+This signal is sent from the incoming end of an international circuit, following the receipt of a seizing signal, to indicate that the equipment is ready to receive the numerical signals.
+
+#### 1.3 **start-of-pulsing signal, also called for system No. 5 "KP signal" (sent in the forward direction)**
+
+This numerical type signal is sent on receipt of a proceed-to-send signal and may be used to prepare the incoming international register for the receipt of the subsequent numerical signals.
+
+Two different KP signals are provided to discriminate between terminal and transit calls:
+
+- a) KP1, terminal; and
+- b) KP2, transit.
+
+#### 1.4 **numerical signal (sent in the forward direction)**
+
+This signal provides an element of information necessary to effect the switching of the call in the desired direction. There is always a succession of numerical signals sent.
+
+#### 1.5 **end-of-pulsing signal, also called for system No. 5 "ST signal" (sent in the forward direction)**
+
+This numerical type signal is sent to show that there are no more numerical signals to follow. The signal is always sent in semi-automatic as well as in automatic working.
+
+#### 1.6 **busy-flash signal (sent in the backward direction)**
+
+This signal, which is sent only after the proceed-to-send signal, is sent to the outgoing international exchange to show that either the route, or the called subscriber, is busy. The conditions of use of this signal are as follows:
+
+- a) An international transit exchange *must* send this signal after register association, to indicate that there is congestion at that exchange or on the appropriate outgoing routes.
+
+- b) An incoming international exchange *must* send this signal, after register association, if there is congestion at that exchange or on the outgoing routes directly connected to it, but sending the signal *is optional* when there is congestion beyond that exchange (when there is congestion at a point in the national network of the incoming country or when the called subscriber's line is busy). This signal is optional because there are several countries that do not send it from their national networks.
+
+*Note* – The receipt of the busy-flash signal at the outgoing exchange will cause:
+
+- an appropriate indication to be given to the outgoing operator or to the calling subscriber; and
+- the sending of the clear-forward by the outgoing exchange to release the international connection (except when otherwise arranged, for example, in this case of observations on circuits).
+
+#### 1.7 **answer signal (sent in the backward direction)**
+
+This signal is sent to the outgoing international exchange to show that the called party has answered the call1).
+
+In semi-automatic working, the signal has a supervisory function.
+
+In automatic working, it is used:
+
+- to start metering the charge to the calling subscriber;
+- to start the measurement of call duration for international accounting purposes.
+
+#### 1.8 **clear-back signal (sent in the backward direction)**
+
+This signal is sent to the outgoing international exchange to indicate that the called party has cleared. In the semi-automatic service, it performs a supervisory function. It must not permanently open the speech path at the outgoing international exchange.
+
+In automatic working, arrangements must be made to clear the international connection, stop the charging and stop the measurement of call duration if, between 1 and 2 minutes after receipt of the clear-back signal, the calling subscriber has not cleared. Clearing of the international connection should preferably be controlled from the point where the charging of the calling subscriber is carried out.
+
+*Notes on the answer and clear-back signals.* – See the corresponding Notes in Recommendation Q.120.
+
+#### 1.9 **clear-forward signal (sent in the forward direction)**
+
+This signal is sent in the forward direction at the end of a call when:
+
+- a) in semi-automatic working, the operator at the outgoing international exchange withdraws her plug from the jack, or when an equivalent operation is performed;
+- b) in automatic working, when the calling subscriber hangs up or otherwise clears (as in the case of a subscriber's installation with extension telephones).
+
+This signal is also sent after receipt of a busy-flash signal by the outgoing international exchange, and when there is forced release of the connection (see Recommendation Q.118, §§ 4.3.1 and 4.3.2 for automatic working and § 4.3.1 for semi-automatic working). This signal may also be sent after an abnormal release of an outgoing register in the case indicated in Recommendation Q.156 under § 3.6.2 a) 1.
+
+#### 1.10 **release-guard signal (sent in the backward direction)**
+
+This signal is sent in the backward direction in response to the clear-forward signal. It serves to protect an international circuit against subsequent seizure as long as the disconnection operations controlled by reception of the clear-forward signal have not been completed at its incoming end.
+
+---
+
+1) See Recommendation Q.27 for the action to be taken to ensure that answer signals, both national and international, are transmitted as quickly as possible.
+
+#### 1.11 **forward-transfer signal (sent the forward direction)**
+
+This signal is sent to the incoming international exchange when the outgoing international exchange operator wants the help of an operator at the incoming international exchange.
+
+The signal will normally serve to bring an assistance operator2) into the circuit if the call is automatically set up at that exchange. When a call is completed via an operator (incoming or delay operator) at the incoming international exchange, the signal should preferably cause this operator to be recalled.
+
+#### 1.12 *Diagrams showing signal sequence*
+
+The sequence of signals in semi-automatic and automatic working is shown in Tables 1 and 2 of Annex 1 to Signalling System No. 5 specifications.
+
+A description of the various operations corresponding to the various normal and abnormal conditions which may arise in setting up a call are given in the tables of Annex 2 to Signalling System No. 5 specifications.
+
+---
+
+2) See the definition of assistance operator in § 1.1.6 of Recommendation Q.101.
+
+## CHAPTER II
+
+### LINE SIGNALLING
+
+#### Recommendation Q.141\*)
+
+### 2.1 SIGNAL CODE FOR LINE SIGNALLING
+
+*(Geneva, 1964; modified at Helsinki, 1993)*
+
+##### 2.1.1 General
+
+The line-signal coding arrangement is based on the use of two frequencies $f_1$ (2400 Hz) and $f_2$ (2600 Hz) transmitted individually or in combination as shown in Table 1. The use of compound signalling for the clear-forward/release-guard sequence increases the immunity to false release by signal imitation.
+
+By taking advantage of the fixed order of occurrence of specific signals, signals of the same frequency content are used to characterize different functions. For example, in the backward direction $f_2$ is used to indicate proceed-to-send, busy-flash and clear-back without conflict. The signalling equipment must operate in a sequential manner retaining memory of the preceding signalling states and the direction of signalling in order to differentiate between signals of the same frequency content. All signals except the forward-transfer signal are acknowledged in the compelled-type manner as indicated in Table 1. The order of transmission of backward signals is subject to the following restrictions:
+
+- a) busy-flash signal: never after an answer signal and only after a proceed-to-send signal;
+- b) answer signal: never after a busy-flash signal;
+- c) clear-back signal: only after an answer signal.
+
+NOTE – The receipt of the answer signal ( $f_1$ ) permits discrimination between the busy-flash and the clear-back signals (both $f_2$ ).
+
+A clear-forward signal, which must be acknowledged by a release-guard signal under all conditions of the equipment including the idle condition, may be sent from an outgoing end at any time to initiate the release of the circuit. The clear-forward signal is completely overriding and may break into any other signal sequence.
+
+##### 2.1.2 Transit working
+
+In transit operation, the line equipment at the transit exchange shall be informed (e.g. by the register) that the condition is transit. This will facilitate the link-by-link transmission of line signals through the transit exchange without bringing about consequences appropriate to the terminal exchanges.
+
+##### 2.1.3 Sending duration of line signalling
+
+2.1.3.1 The sending durations of the line signals are shown in Table 1. Additional requirements are:
+
+- a) In the event of double seizing (due to both-way operation), the seizing signal transmitted from the end having detected double seizing should persist for at least $850 \pm 200$ ms to permit the other end to detect the double seizing.
+- b) Should the called party flash his switch-hook at a faster rate than the equipment can transmit a succession of clear-back and answer signals, the correct indication of the final position of the switch-hook must always be given by the appropriate signal.
+
+---
+
+\*) The text of ITU-T Rec. Q.141 is as amended by WTSC in March 1993.
+
+- c) Once the sending of a signal (pulse or compelled) has begun it should be completed (but see 2.1.1 in regard to the clear-forward signal releasing the circuit at any stage and in 2.1.7 in regard to the overlap answer signal at transit points). If two signals have to be sent one immediately after the other in the same direction, a silent interval of not less than 100 ms should separate the two successive signals. The silent interval should not be so long as to cause unreasonable delay in signalling.
+
+##### *Exceptionally*
+
+- 1) the intervals between successive signals may be less than 100 ms. However, the technique of complete signals with intervals of at least 100 ms is the preferred arrangement;
+ - 2) the forward-transfer signal may be ceased immediately if a backward signal is received. The acknowledgement of the backward signal is then sent.
+- d) When sending a compound signal, the interval of time between the moments when each of the two frequencies is sent must not exceed 5 ms. The interval of time between the moments when each of the two frequencies ceases must not exceed 5 ms.
+- e) *Time-out and alarm procedures*
+ - i) Should the transmission of any size, busy-flash, answer, clear-back or clear-forward signal persist beyond a maximum of 10 to 20 seconds, the signal shall be terminated.
+NOTE 1 – 10 to 20 seconds time-out for the seizing signal allows reasonable time for association of a register in a distant centre.
+ - ii) Should the transmission of any proceed-to-send, release-guard or other acknowledgement signal persist beyond a maximum of 4 to 9 seconds, the signal shall be terminated.
+NOTE 2 – The shorter time-out periods for secondary signals enable, under many conditions, detection of a fault at both ends of a circuit on a single call.
+NOTE 3 – Time-out of the answer acknowledgement signal may cause charging without a satisfactory transmission path to the called party. If the occurrence of such time-outs should reach unacceptable levels, a delay in the transfer of the answer signal into the national network until the compelled answer signalling cycle is complete, may be justified.
+ - iii) Upon the occurrence of a time-out under the two above conditions, the attention of the maintenance personnel should be drawn to the fact that time-out has occurred.
+NOTE 4 – An Administration may decide that on the time-out of an acknowledgement signal at the incoming end of the connection, when an automatic repeat clear-forward sequence is known to be provided at the outgoing end, no indication is given to the maintenance personnel, neither is the circuit taken out of service.
+ - iv) Upon the occurrence of a time-out, the circuit should automatically be removed from service after clearance by the subscriber and blocked to outgoing calls. However, time-out of a seize signal may be excluded from this provision if time-out of that signal is followed by a clear-forward attempt.
+ - v) As a test procedure, Administrations may make repeated signalling attempts and restore the circuit to service if it is found to perform in a normal manner.
+ - vi) Each Administration shall make appropriate arrangements to ensure that a single fault will not cause removal from service of more than one circuit or of more than one register.
+
+**2.1.3.2** The duration of the forward-transfer signal is based on the possibility that TASI may clip a signal by up to 500 ms on rare occasions during heavy traffic periods, and on the need for establishing a recognition time that minimizes signal imitation.
+
+##### **2.1.4 Recognition times of line signals**
+
+Recognition time is defined as the minimum duration a direct-current signal, at the output of the signal receiver, must have in order to be recognized as a valid condition by the switching equipment. The recognition times are given in Table 1.
+
+For equal immunity against signal imitation, the recognition time of compound signals such as the clear-forward/release-guard sequence could be less than that of the single-frequency signals liable to signal imitation. However, for convenient design arrangements, and to improve the immunity of the clear-forward/release-guard sequence, the recognition time of the compound signals is the same ( $125 \pm 25$ ms) as that of the single-frequency signals liable to signal imitation.
+
+After signal recognition, interruptions of up to 15 ms in the primary or acknowledgement signals shall be ignored in the compelled signalling sequences. Interruptions of more than 40 ms must be recognized as the end of the appropriate signal in the compelled signalling sequences.
+
+##### 2.1.5 Line signal code of System No. 5
+
+The line signal code is given in Table 1.
+
+TABLE 1/Q.141
+
+##### **Line signal code**
+
+| Signal | Direction a) | Frequency b) | Sending duration | Recognition time |
+|-------------------------------------------------------------|-------------------------|-------------------------------------|------------------|------------------|
+| Seizing – Prise . . . . . | ————→ | f1 | Continuous | 40 ± 10 ms |
+| Proceed-to-send – Invitation à transmettre . . . . . | ←———— | f2 | Continuous | 40 ± 10 ms |
+| Busy-flash – Occupation . . . . . | ←———— | f2 | Continuous | 125 ± 25 ms |
+| Acknowledgement – Accusé de réception . . . . . | ————→ | f1 | Continuous | 125 ± 25 ms |
+| Answer – Réponse . . . . . | ←———— | f1 | Continuous | 125 ± 25 ms |
+| Acknowledgement – Accusé de réception . . . . . | ————→ | f1 | Continuous | 125 ± 25 ms |
+| Clear-back – Raccrochage du demandé . . . . . | ←———— | f2 | Continuous | 125 ± 25 ms |
+| Acknowledgement – Accusé de réception . . . . . | ————→ | f1 | Continuous | 125 ± 25 ms |
+| Forward-transfer – Signal d'intervention . . . . . | ————→ | f2 | 850 ± 200 ms | 125 ± 25 ms |
+| Clear-forward – Signal de fin . . . . . | ————→ | f1 + f2
(compound) | Continuous | 125 ± 25 ms |
+| Release-guard – Libération de garde . . . . . | ←———— | f1 + f2
(compound) | Continuous | 125 ± 25 ms |
+
+a) —————→ forward signals ←———— backward signals
+
+b) *f1* = 2400 Hz *f2* = 2600 Hz
+
+##### 2.1.6 Further specification clauses relative to the signalling code
+
+- a) The seizing signal continues until acknowledged by the proceed-to-send signal. The proceed-to-send signal is transmitted when an incoming register is associated and continues until acknowledged by the stopping of the seizing signal1).
+- b) The clear-forward signal continues until acknowledged by the release-guard signal, which may be sent as described under 1) or 2) below:
+ - 1) The release-guard signal is sent on recognition of the clear-forward signal and continues until acknowledged by the cessation of the clear-forward signal or until the relevant incoming equipment at the international exchange is released, whichever occurs later1).
+ - 2) The release-guard signal is sent in response to the clear-forward signal to indicate that the latter has brought about the release of the relevant incoming equipment at the international exchange. The release-guard signal continues until cessation of the clear-forward signal is recognized1).
+
+1) This type of signalling is called “continuous compelled”.
+
+The outgoing access of the incoming end of the both-way circuit shall be maintained busy for 200 to 300 ms after the end of the transmission of the release-guard signal.
+
+- c) With respect to the busy-flash, answer and clear-back signals the acknowledgement signal shall not be transmitted before the signal recognition time ( $125 \pm 25$ ms) of the primary signal has elapsed. The primary signal shall not be ceased until the signal recognition time ( $125 \pm 25$ ms) of the acknowledgement signal has elapsed2) (see 2.1.7 with respect to the transmission of the answer signal at a transit point).
+- d) The busy-flash will be transmitted if the call cannot be completed for any of the following reasons:
+ - 1) congestion at an incoming international exchange;
+ - 2) congestion at a transit international exchange;
+ - 3) error detected in the receipt of the register signals;
+ - 4) busy-flash (if received) from a subsequent international system (e.g. system No. 4) or from the national network;
+ - 5) time-out of an incoming international register.
+- e) Receipt of busy-flash at the outgoing international exchange will cause:
+ - after signal recognition time ( $125 \pm 25$ ):
+ - 1) the acknowledgement signal to be sent; and
+ - 2) an appropriate audible indication to be transmitted to the operator or to the subscriber. When the preceding circuit provides for the transmission of busy-flash, this signal should be transmitted to that preceding circuit;
+ - after the end of the compelled sequence, i.e. 100 ms after termination of the acknowledgement signal [see 2.1.3 c)]:
+ - 3) a clear-forward signal to be transmitted from that exchange and the international circuit or chain of circuits to be released by the clear-forward/release-guard sequence.
+- f) Receipt of busy-flash at a transit exchange will cause after signal recognition time:
+ - 1) the acknowledgement signal to be sent; and
+ - 2) the busy-flash signal to be sent on the preceding incoming circuit;
+ - 3) the transit exchange and forward connection to be cleared.
+NOTE 1– Where existing equipment is designed to allow clearing only from the outgoing international exchange, this need not be modified retrospectively.
+- g) Upon receipt of the answer signal in the answer state or the clear-back signal in the clear-back state, the international exchange should, nevertheless, respond by sending the acknowledgement signal.
+NOTE 2 – This procedure will be helpful to avoid unnecessary discontinuity of the compelled sequence when the international exchange receives answer (*f* 1) or clear-back (*f* 2) signal twice within a short interval.
+- h) In order to prevent irregularities, Administrations should ensure that the sending time of the release guard signal has a minimum duration of 200 ms. The recognition of the release guard signal without prior sending of a clear forward signal should be regarded as an irregularity. Administrations should decide to react on detection of that irregularity by sending a clear forward signal and release through-connection in the international exchange. Depending on the capability of the signalling system on the preceding link, the international switching centre should initiate the release of this link.
+
+##### 2.1.7 Backward signals on multilink connections (consider as an example a connection A-T-B)
+
+- a) *Normal compelled signalling for busy-flash and clear-back signals*
+
+With *normal compelled signalling* [see 2.1.6 c) above] at a transit point T, the transmission of the primary signal from T to A does not commence until the signal recognition time of the primary signal sent from B to T has elapsed. This technique is applied for the transmission of busy-flash and clear-back signals.
+
+---
+
+2) This type of signalling is called “continuous compelled”.
+
+##### b) *Overlap compelled signalling for the answer signal*
+
+With *overlap compelled signalling* at a transit point T, the process of transmitting the primary signal from T to A is initiated as soon as the signal receiver response has caused at T the receiving end line split of BT. The normal signal recognition of the primary signal is still required at each transit point. The acknowledgement signal on a particular link should not be transmitted until signal recognition time of the primary signal has elapsed. To speed up the transmission of the answer signal, the overlap compelled technique is applied for this signal at a transit exchange when two No. 5 circuits are switched in tandem.
+
+More details of the overlap compelled technique are given below:
+
+If the primary signal from B to T lasts less than the signal recognition time, transmission of a primary signal already initiated at a transit point T from T to A will be stopped.
+
+After the recognition time at T of a primary signal from B to T has elapsed, there shall be no control at T of the primary signal sent from T to A by the primary signal sent from B to T. In this case the primary signal on each link is ceased by its acknowledgement signal on that link [as in 2.1.6 c) above].
+
+Figure 1 illustrates a typical arrangement and is included to illustrate the principle of overlap compelled signalling at transit points. Other design arrangements may be adopted as preferred by Administrations.
+
+Transmission of the primary signal from T to A is initiated (by a “start to send” control condition *X* through the switch block at the transit point) as soon as the signal receiver response on the primary signal from B to T has caused the receiving-end line split ( $t_1$ of $T_1$ ). The primary signal is transmitted from T to A after the sending-end line split ( $t_3$ of $T_3$ ). Signal recognition of the primary signal is required at the transit point and the acknowledgement signal on a particular link should not be transmitted until the signal recognition time ( $t_2$ of $T_1$ , $t_2$ of $T_4$ ) has elapsed. The primary signal is ceased after the signal recognition time ( $t_2$ of $T_2$ , $t_2$ of $T_5$ ) of the relevant acknowledgement signal.
+
+To prevent imitations of the primary signal on link BT lasting less than the signal recognition time from giving rise to an effective compelled signalling sequence on link TA, transmission of the primary signal on link TA is first under the “start to send” control *X* of a time base $T_3$ followed, without break at the termination of the time base (at time *Z*), by the continuous signal control required for compelled signalling. Should the duration of the primary signal on link BT be less than the signal recognition time ( $t_2$ of $T_1$ ), the “start to send” control (*X* control) is interrupted. This stops transmission of a primary signal on link TA (should this have commenced) within the period *X-Z* of $T_3$ and hence before the continuous signal control can be applied.
+
+After the signal recognition time of the primary signal on link BT has elapsed, there shall be no control of the transmission of the primary signal on link TA by the primary signal on link BT at the transit point. To achieve this, a condition is applied to the *Y* control to inhibit the *X* control, which should ensure that transmission of the primary signal on link TA cannot be stopped during the period *X-Y* of $T_3$ and that the continuous signal control of the primary signal is applied without break at time *Y* (or at time *Z* depending upon the particular design). In these circumstances the primary signal on each link is ceased by its relevant acknowledgement signal.
+
+
+
+The diagram illustrates the timing of signals in a network with two links and three exchanges (A, T, and B).
+
+- **Exchange A** sends an **Outgoing** **Primary signal** into the first **LINK**.
+
+- At the far end of the first link, **Exchange (Transit) T** receives an **Incoming** signal.
+
+- **Exchange (Transit) T** then sends an **Outgoing** **Primary signal** into the second **LINK**.
+
+- At **Exchange B**, an **Incoming** signal is received.
+
+- **Acknowledgement** signals are shown propagating back from **Exchange B** through the links.
+
+- A **Switch block** in **Exchange (Transit) T** is shown with **D.C. control** lines.
+
+- Time intervals are defined:
+
+ - $t_1$ : Receiving end line split (35 ms max.)
+
+ - $t_2$ : Signal recognition time ( $125 \pm 25$ ms)
+
+ - $t_3$ : Sending end line split ( $40 \pm 10$ ms)
+
+ - $t_4$ : $125 \pm 25$ ms typically
+
+ - $t_5$ : Continuous signal control for primary signal
+
+- Vertical dashed lines indicate key timing points:
+
+ - **T4**: Start of outgoing primary signal at Exchange A.
+
+ - **T5**: Start of incoming primary signal at Exchange T.
+
+ - **T3**: Start of outgoing primary signal at Exchange T.
+
+ - **T1**: Start of outgoing primary signal into the second link.
+
+ - **T2**: Start of incoming primary signal at Exchange B.
+
+- Brackets indicate durations:
+
+ - $t_1$ at T4 and T1.
+
+ - $t_2$ at T4, T1, and T2.
+
+ - $t_3$ at T4.
+
+ - $t_4$ between T5 and T3.
+
+ - $t_1$ and $t_2$ at T2.
+
+- Text labels indicate that the start of the acknowledgement signal at T5 'Causes the cessation of the primary signal' at T4, and similarly at Exchange B.
+
+Timing diagram for overlap compelled signalling. It shows signal propagation between Exchange A, a Link, Exchange (Transit) T, another Link, and Exchange B. Key signals include Primary signal, Acknowledgement, and D.C. control. Time intervals t1 through t5 are marked to show the timing relationships between signal sending, splitting, and recognition at various points in the network.
+
+$T_1$ , etc. = Time base
+
+$t_1$ = Receiving end line split (35 ms max.)
+
+$t_2$ = Signal recognition time ( $125 \pm 25$ ms)
+
+$t_3$ = Sending end line split ( $40 \pm 10$ ms)
+
+$t_4$ = $125 \pm 25$ ms typically
+
+FIGURE 1/Q.141
+
+**Typical arrangement to illustrate the principle of overlap compelled signalling for the answer signal at transit points**
+
+#### **Recommendation Q.142**
+
+### **2.2 DOUBLE SEIZING WITH BOTH-WAY OPERATION**
+
+#### **2.2.1 Unguarded interval**
+
+Considering that on long international (intercontinental) circuits:
+
+- a) the sending end splitting time may be 50 ms prior to signal transmission;
+- b) TASI may occasionally clip the initial 500 ms of seizing signals;
+- c) circuit propagation time may be relatively long;
+- d) the signal receiver response time must be taken into account;
+- e) the recognition time of seizing signals is $40 \pm 10$ ms;
+
+the unguarded interval relative to double seizing in the extreme case approaches 600 ms plus the circuit propagation time and the signal receiver response time. The signalling system should therefore detect double seizing and take action as defined in § 2.2.2.
+
+#### 2.2.2 Detection of double seizing
+
+In the event of double seizing, the same frequency ( $f1$ ) is received as is being transmitted at each terminal. This condition shall be detected by the signalling equipment and shall cause stoppage of the outgoing seizing signal at each end. An end having detected double seizing, and terminated the outgoing seizing signal $850 \pm 200$ ms after this signal has been transmitted, will maintain the circuit in the busy condition until the stoppage of the incoming seizing signal from the distant end. Each outgoing seizing signal maintained for at least $850 \pm 200$ ms will ensure that both ends of the circuit will detect the double seizing.
+
+The signalling equipment will be released on termination of both the outgoing and incoming seizing signals and a clear-forward shall not be sent.
+
+Either of the following arrangements may apply on detection of double seizing:
+
+- a) an automatic repeat attempt to set up the call; or
+- b) a re-order indication is given to the operator or to the subscriber and no automatic repeat attempt is made.
+
+Method a) is the preferred arrangement (see Recommendation Q.108).
+
+Method a) does not require the repeat attempt to be limited to the circuit used at the first attempt, but should the first circuit be seized again at the second attempt on the second search over the circuits, a minimum time of 100 ms shall elapse between the termination of the first attempt outgoing seizing signal (or the recognition of the cessation of the incoming seizing signal, whichever occurs later) and the commencement of the second attempt seizing signal.
+
+To minimize the probability of double seizing, the circuit selection at the two ends should be such that, as far as possible, double seizing can occur only when a single circuit remains (e.g. by selection of circuits in opposite order at the two ends).
+
+#### Recommendation Q.143
+
+### 2.3 LINE SIGNAL SENDER1)
+
+#### 2.3.1 Signalling frequencies
+
+$2400 \pm 6$ Hz ( $f1$ ) and $2600 \pm 6$ Hz ( $f2$ ).
+
+These frequencies are applied separately or in combination.
+
+#### 2.3.2 Transmitted signal level
+
+$-9 \pm 1$ dBm0 per frequency.
+
+For compound signals the difference in transmitted level between $f1$ and $f2$ shall not exceed 1 dB.
+
+*Note 1* – The noise as measured at the output of the line signal sender shall be as low as practicable but in any event, at least 40 dB below signal level. This noise includes all extraneous power in the frequency band between 300 Hz and 3400 Hz including power resulting from non-linear distortion of the signal.
+
+*Note 2* – The level of the leak current transmitted to line should be at least 50 dB below signal level per frequency.
+
+---
+
+1) See also Recommendation Q.112.
+
+### 2.4 LINE SIGNAL RECEIVER1)
+
+(Geneva, 1964; modified at Helsinki, 1993)
+
+#### 2.4.1 Operating limits
+
+The line signal receiver shall operate in the conditions specified under 2.4.5 for the distortion of received signals that meet the following conditions:
+
+- $f1: 2400 \pm 15$ Hz; $f2: 2600 \pm 15$ Hz.
+- The absolute power level $N$ of each unmodulated signal received shall be within the limits:
+
+$$(-16 + n) \leq N \leq (-2 + n) \text{ dBm}$$
+
+where $n$ is the relative power level at the signal received input.
+
+These limits give a margin of $\pm 7$ dB on the nominal absolute level of each received signal at the input to the signal receiver.
+
+- The absolute level of the two unmodulated signal frequencies in a compound signal may differ from each other by not more than 5 dB.
+
+The tolerances given in a), b) and c) are to allow for variations at the sending end and for variations in line transmission.
+
+#### 2.4.2 Non-operate conditions of line signal receiver
+
+- Selectivity*
+
+The signal receiver shall not operate on a signal having an absolute power level at the receiving end within the limits specified in 2.4.1 when the frequency is outside:
+
+| | | |
+|------|-------|-----------------------------------|
+| | + 100 | |
+| 2400 | | Hz for the $f1$ signal circuit or |
+| | - 150 | |
+| 2600 | | Hz for the $f2$ signal circuit |
+| | - 100 | |
+
+- Maximum sensitivity of line signal receiver*
+
+The signal receiver shall not operate on a signal of $2400 \pm 15$ Hz or $2600 \pm 15$ Hz whose absolute power level at the point of connection of the receiver is $(-17 - 9 + n)$ dBm, $n$ being the relative power level at this point. This limit is 17 dB below the nominal absolute level of the signal current at the input to the signal receiver.
+
+#### 2.4.3 Efficiency of the guard circuit
+
+The signal receiver must be protected by a guard circuit against false operation due to speech currents, circuit noise, or other currents of miscellaneous origin circulating in the line.
+
+The purpose of the guard circuit is to prevent:
+
+- signal imitation. (Signals are imitated if the duration of the resulting direct-current pulses at the output of the signal receiver is long enough to be recognized as signals by the switching equipment);
+- operation of the splitting device from interfering with speech.
+
+To minimize signal imitation by speech currents it is advisable that the guard circuit be tuned.
+
+To minimize signal interference by low-frequency noise it is advisable that the response of the guard circuit falls off towards the lower frequencies and that the sensitivity of the guard circuit at 200 Hz be at least 10 dB less than that at 1000 Hz.
+
+\*) The text of ITU-T Rec. Q.144 is as amended by WTSC in March 1993.
+
+1) See also Recommendation Q.112.
+
+An indication of the efficiency of the guard circuit is given by the following:
+
+- a) during 10 hours of speech, normal speech currents should not, on the average, cause more than one false operation of the $f1$ or the $f2$ signal circuit lasting more than 90 ms (the minimum recognition time of a signal liable to imitation is 100 ms);
+- b) the number of false splits of the speech path caused by speech currents should not cause an appreciable reduction in the transmission quality of the circuit.
+
+Since Signalling System No. 5 and V.22 modem are using the same frequency, the following conditions should be verified when testing new receivers, so that the connection is not released during data transmission:
+
+When the 2400 Hz or 2600 Hz frequencies are present at level from $-2$ dBm0 to $-26$ dBm0, the addition of one of the following should guard the receiver from recognizing them as line signalling frequencies:
+
+- a) a tone of 1800 Hz at 10 dB below the line frequency signal level;
+- b) any tone in the area of 1000 Hz to 1900 Hz at 7 dB below the line frequency signal level.
+
+#### 2.4.4 Guard circuit limits
+
+##### A Steady noise
+
+*Considering:*
+
+- (a) that when there is noise on a telephone circuit an over-sensitive guard circuit might give rise to signalling difficulties and, in particular, inhibit the response of the signal receiver;
+- (b) that unweighted noise of a level $-40$ dBm0 (100 000 pW) and uniform spectrum energy may arise on the longest international, i.e. intercontinental, circuit,
+
+it is recommended that, for either one or two signalling currents (each being within the limits specified in 2.4.1), the signal receiver should satisfy the conditions indicated in 2.4.5 for the distortion of signals in the presence of noise of a level of $-40$ dBm0 and uniform spectrum energy over the frequency range 300 to 3400 Hz.
+
+##### B Surges
+
+A guard circuit with an excessive hand-over time may cause difficulties in receiving a signal, for example, when it has been immediately preceded by surges, and it is therefore recommended that the following condition should be fulfilled:
+
+If a disturbing current of a frequency corresponding to the maximum sensitivity of the guard circuit and having an absolute power level of $(-10 + n)$ dBm at the relative level point $n$ where the receiver is connected ceases 30 ms before the application of a signal satisfying the limits defined in 2.4.1, the lengths of the received signals must remain within the limits specified in 2.4.5.
+
+#### 2.4.5 Distortion of received signals
+
+When the signal frequencies and levels are within the limits specified in 2.4.1, the change in signal length in the presence of noise as defined in 2.4.4, A should not exceed:
+
+- a) 15 ms when the signal receiver receives a pulse of one frequency $f1$ or $f2$ with a minimum duration of 150 ms;
+- b) 25 ms when the signal receiver receives a compound pulse of the two frequencies $f1$ and $f2$ with a minimum duration of 150 ms, the change being defined as the difference between the simultaneous reception of the two frequencies at the input to the receiver and the simultaneous production of the two components as a direct-current signal at the output of the signal receiver.
+
+In general, the response time of the signal receiver should be as short as practicable to minimize the time required for signalling purposes.
+
+Except for the forward transfer pulse signal the above pulse distortion requirements are of minor importance for the remaining line signals, which are all of the continuous compelled type2). Nevertheless the limits are specified for receiver design and test purposes.
+
+---
+
+2) See 2.1.6/Q.141 explaining the term "continuous compelled".
+
+### **2.5 SPLITTING ARRANGEMENTS**
+
+#### *Sending line split*
+
+- 2.5.1 According to Recommendation Q.25, § 2, sending split arrangements have to be provided.
+- 2.5.2 The exchange side of the international circuit shall be disconnected 30 to 50 ms before a voice-frequency signal is sent over the circuit.
+- 2.5.3 The exchange side of the international circuit will not be reconnected for 30 to 50 ms following the end of the sending of a voice-frequency signal over the circuit.
+- 2.5.4 Exceptionally, the values quoted in §§ 2.5.2 and 2.5.3 above may be 0 to 50 ms as the values are of minor importance with respect to compelled-type signals.
+
+#### *Receiving line split*
+
+- 2.5.5 The international circuit should be split at the international exchange when either a single-frequency or a compound-frequency signal is received, to ensure that no fraction of the signal exceeding 35 ms duration may pass out of the international circuit.
+
+The splitting time of 35 ms may be reduced by each Administration concerned in order to help to protect its national network against the effect of signals coming from the international circuit. It should be noted, however, that a shorter splitting time can lead to an increase in the number of false operations of the splitting device by speech currents and impair speech transmission.
+
+- 2.5.6 The split must be maintained for the duration of the signal but must cease within 25 ms of the end of the direct-current signal which caused the splitting device to operate.
+- 2.5.7 The splitting of the line must not give rise to surges which might cause interference with signalling over the international circuit or with other signalling systems associated with it for setting up an international call.
+- 2.5.8 The splitting device may be any suitable arrangement – for example, physical line disconnection, high impedance electronic device, insertion of signalling frequency band stop filter, etc. The level of leak current transmitted to the subsequent circuit from the splitting device in the split condition should be at least 40 dB below the received signal level. Exceptionally, the level of the leak current may be 25 dB below the received signal level if this causes no interference with the relevant networks.
+
+### **2.6 SPEED OF SWITCHING IN INTERNATIONAL EXCHANGES**
+
+2.6.1 It is recommended that the equipment in the international exchanges shall have a high switching speed so that the switching time may be as short as possible.
+
+2.6.2 At the outgoing international exchange the seizing of the circuit and the setting up of the connection should take place as soon as the ST end-of-pulsing condition is available (see Recommendation Q.152). In automatic operation advantage should be taken of all cases in which the ST condition can be reasonably determined at once, i.e. with avoidance of the 4-6 seconds time-out.
+
+At an international transit exchange the setting up of the connection on the outgoing circuit should take place as soon as the digits necessary to determine the routing, are received and analyzed.
+
+At the incoming international exchange the setting up of the national part of the connection should start as soon as the register has received a sufficient number of digits.
+
+2.6.3 At international exchanges the return of a proceed-to-send signal should be as fast as possible but in any case the return should normally be guaranteed before the time-out (minimum 10 seconds) of the seizing signal.
+
+Furthermore, in the case of congestion on the circuits outgoing from a transit or an incoming exchange, a busy-flash signal should be returned as soon as practicable, but in any case within a maximum delay of 10 seconds following the receipt of the information necessary to determine the routing.
+
+## CHAPTER III
+
+## REGISTER SIGNALLING
+
+#### Recommendation Q.151
+
+### 3.1 SIGNAL CODE FOR REGISTER SIGNALLING
+
+#### 3.1.1 General
+
+- 1) Automatic access to the international circuits must be used for outgoing traffic and the numerical signals from the operator or subscriber are stored in an outgoing international register before an international circuit is seized. As soon as the ST (end-of-pulsing) condition is available to the outgoing register, a free international circuit is selected and a seizing line signal transmitted. On receipt of a proceed-to-send line signal the seizing signal is terminated and a KP ("start of pulsing") pulse, followed by the numerical signals, is transmitted by the register. The final register signal transmitted is an end-of-pulsing (ST) pulse. The register signalling is not required to be TASI-prefixed.
+- 2) Link-by-link register signalling applies. The register signals are always sent en bloc1). En bloc non-overlap1) applies at the outgoing international register. En bloc overlap1) applies at the transit and incoming international registers.
+- 3) On a particular link, the KP signal sent by the international register (outgoing or transit register) on receipt of a proceed-to-send signal may be used to prepare the distant international register on this link for the receipt of the subsequent numerical signals. This signal may also serve to discriminate between terminal and transit traffic:
+ - a) Terminal KP (KP1). Used to create conditions at the next exchange so that equipment (or techniques) used exclusively for switching the call to the national network of the incoming country is brought into circuit.
+ - b) Transit KP (KP2). Used to bring into circuit, at the next exchange, equipment (or techniques) required to switch to call to another international exchange.
+- 4) The register signalling is a 2-out-of-6 multifrequency code, forward signalling only, as shown in Table 2.
+
+---
+
+1) *En bloc register signalling* is the transmission, by a register, of all the call information as a whole in a regular timed sequence of signals.
+
+The technique requires that, in one register on the connection, all the relevant call information from a subscriber or operator shall be completely stored before output en bloc signal transmission takes place from that register.
+
+At registers subsequent to the one where all the call information from a subscriber or operator is completely stored, the output signal transmission may commence before the complete reception of the input information; thus overlap to any desired degree of the output signal transmission with the input signal reception may occur and this may be understood as being *en bloc overlap*. Alternatively, the output signal transmission may be delayed until all the call information is received and stored. This may be understood as being *en bloc non-overlap*.
+
+TABLE 2
+**Register signal code of system No. 5**
+
+| Signal | Frequencies
(compound)
Hz | Remarks |
+|---------|---------------------------------|------------------|
+| KP1 | 1100 + 1700 | Terminal traffic |
+| KP2 | 1300 + 1700 | Transit traffic |
+| Digit 1 | 700 + 900 | |
+| " 2 | 700 + 1100 | |
+| " 3 | 900 + 1100 | |
+| " 4 | 700 + 1300 | |
+| " 5 | 900 + 1300 | |
+| " 6 | 1100 + 1300 | |
+| " 7 | 700 + 1500 | |
+| " 8 | 900 + 1500 | |
+| " 9 | 1100 + 1500 | |
+| " 0 | 1300 + 1500 | |
+| Code 11 | 700 + 1700 | Code 11 operator |
+| Code 12 | 900 + 1700 | Code 12 operator |
+| ST | 1500 + 1700 | End-of-pulsing |
+
+#### 3.1.2 *Sending sequence of register signals*
+
+The sequence of the register signals shall conform to the sequence indicated in Recommendation Q.107, noting the following:
+
+- a) a KP start-of-pulsing signal shall precede the sequence of numerical signals in all the cases indicated;
+- b) the ST end-of-pulsing signal will be transmitted from the register in automatic as well as in semi-automatic operation;
+- c) exceptionally, special numbers for giving access to incoming operators or delay operators may be dialled by outgoing operators and submitted by outgoing international registers instead of code 11 and code 12 signals.
+
+#### **Recommendation Q.152**
+
+### **3.2 END-OF-PULSING CONDITIONS – REGISTER ARRANGEMENTS CONCERNING ST (END-OF-PULSING) SIGNAL**
+
+3.2.1 The register signalling arrangements provide for the sending of a ST signal for both semi-automatic and automatic operation; the arrangements in the outgoing international register for recognizing the ST end-of-pulsing condition will vary as follows:
+
+#### a) *Semi-automatic operation*
+
+The ST condition is determined by the receipt of the "sending-finished" signal from the operator (see Recommendation Q.106).
+
+#### b) *Automatic operation*
+
+- 1) Where the ST condition is determined by the originating national network and an ST signal is produced and transmitted to the outgoing international register, no further arrangements are necessary in that register for this purpose.
+- 2) Where the ST condition is not received from the originating national network, the outgoing international register will be required to determine the ST condition. This ST condition is determined when the cessation of numerical information input to the register exceeds a period of 4 seconds ( $5 \pm 1$ seconds) in either of the following two circumstances, as preferred by the Administration:
+ - i) after the minimum number of digits in the world numbering plan; or
+
+- ii) after the minimum number of digits of the destination country numbering plan.
+
+In i) and ii), prolonged cessation of the numerical information input before the minimum number of digits should result in time-out of the register without the production of the ST condition.
+
+An immediate ST condition may be produced by a digit count to avoid the 4-second delay ST condition in the following circumstances:
+
+- i) when the destination country numbering plan has a fixed number of digits;
+- ii) when the maximum number of digits in the numbering plan of the destination country has been received.
+
+3.2.2 Under all conditions, the outgoing international circuit should not be seized until the ST end-of-pulsing condition is available in the outgoing international register.
+
+#### **Recommendation Q.153**
+
+### **3.3 MULTIFREQUENCY SIGNAL SENDER**
+
+#### **3.3.1 *Signalling frequencies***
+
+700, 900, 1100, 1300, 1500 and 1700 Hz.
+
+A signal shall consist of a combination of any two of these six frequencies. The frequency variation shall not exceed $\pm 6$ Hz of each nominal frequency.
+
+#### **3.3.2 *Transmitted signal level***
+
+$-7 \pm 1$ dBm0 per frequency.
+
+The difference in transmitted level between the two frequencies comprising a signal shall not exceed 1 dB.
+
+*Note* – The level of the leak current transmitted to line should be at least:
+
+- a) 50 dB below the single-frequency level when a multifrequency signal is not being transmitted;
+- b) 30 dB below the transmitted signal level of either of the two frequencies when a multifrequency signal is being transmitted.
+
+#### **3.3.3 *Signal duration***
+
+KP1 and KP2 signals: $100 \pm 10$ ms
+
+All other signals: $55 \pm 5$ ms
+
+Interval between all signals: $55 \pm 5$ ms
+
+Interval between cessation of the seizing line signal and transmission of the register KP signal: $80 \pm 20$ ms.
+
+##### **3.3.4 *Compound signal tolerance***
+
+The interval of time between the moments when each of the two frequencies comprising a signal is sent must not exceed 1 ms. The interval of time between the moments when each of the two frequencies ceases must not exceed 1 ms.
+
+### **3.4 MULTIFREQUENCY SIGNAL RECEIVER**
+
+#### **3.4.1 Operating limits**
+
+The signal receiver must ensure a separate output signal for each of the six voice-frequency signals received, and must operate satisfactorily for any combination of two of the frequencies, received as a single pulse or in a train of pulses, satisfying the following conditions:
+
+- a) the frequency of the received signal is within $\pm 15$ Hz of the nominal signalling frequency;
+- b) the absolute power level $N$ of each unmodulated signal shall be within the limits $(-14 + n \leq N \leq n)$ dBm where $n$ is the relative power level at the signal receiver input. These limits give a margin of $\pm 7$ dB on the nominal absolute level of each received signal at the input to the signal receiver;
+- c) the absolute levels of the two unmodulated frequencies comprising a signal must not differ from each other by more than 4 dB;
+- d) when the signal frequencies and levels are within the limits specified in a), b) and c) above, and in the presence of noise as defined in § 3.4.3:
+ - 1) at the input of a signal receiver, the minimum duration of an MF signal necessary to ensure correct registration of the digit shall not exceed 30 ms; this includes the operate time of the signal receiver and the two-and-two only check feature;
+ - 2) furthermore, at the input of the signal receiver, the minimum duration of an interval necessary to ensure the correct functioning of the registration device shall not exceed 30 ms; this includes the release time of the signal receiver and the restoration time of the two-and-two only check feature.
+
+*Note 1* – The tolerances given in a), b) and c) are to allow for variations at the sending end and in line transmission.
+
+*Note 2* – The test values indicated in d) are less than the working values. The difference between the test and working values will allow for pulse distortion, difference in time of the receipt of the two frequencies comprising a signal, etc.
+
+#### **3.4.2 Non-operating conditions**
+
+##### **a) Maximum sensitivity**
+
+The signal receiver shall not operate under the effect of a signal as indicated in § 3.4.1 a) whose absolute power level at the point of connection of the receiver is $(-17 - 7 + n)$ dBm, $n$ being the relative power level at this point.
+
+This limit is 17 dB below the nominal absolute power level of the signal current at the input to the signal receiver.
+
+##### **b) Transient response**
+
+Operation of the signal receiver shall be delayed for a minimum period necessary to guard against false operation due to spurious signals generated within the receiver on reception of any signal.
+
+##### **c) Short signal response**
+
+The signal receiver should not operate to a pulse signal of 10 ms or less. This signal may be of single frequency or two frequencies received simultaneously.
+
+Likewise the signal receiver should ignore short intervals.
+
+#### 3.4.3 *Steady noise*
+
+Considering that unweighted noise of a level $-40$ dBm0 (100 000 pW) and uniform spectrum energy may arise on the longest international circuit, the multifrequency receiver should satisfy the condition indicated in § 3.4.1 d) for minimum signal and interval durations in the presence of noise of level $-40$ dBm0 and uniform spectrum energy over the frequency range 300 to 3400 Hz.
+
+#### 3.4.4 *Input impedance*
+
+The input impedance should be such that the return loss over a frequency range 300 to 3400 Hz against a 600 ohm non-inductive resistor is greater than 20 dB.
+
+#### **Recommendation Q.155**
+
+### **3.5 ANALYSIS OF DIGITAL INFORMATION FOR ROUTING**
+
+(see Recommendation Q.107 *bis*)
+
+#### **Recommendation Q.156**
+
+### **3.6 RELEASE OF INTERNATIONAL REGISTERS**
+
+#### 3.6.1 *Normal release conditions*
+
+- a) An outgoing international register shall be released when it has transmitted the ST signal.
+- b) An incoming international register shall be released in either one of the following two cases:
+ - 1) Depending on the arrangements adopted by the Administration concerned at the incoming international exchange.
+
+*For example:* release on transmission of the ST signal, release on receipt of a number-received condition from the national network, etc.
+
+- 2) When the busy-flash signal is returned. The return of the busy-flash signal in the case of congestion at the incoming exchange should take place as soon as practicable, but in any case within a maximum delay of 10 seconds following the receipt, at the incoming exchange, of the digits necessary to determine the routing.
+- c) A transit international register shall be released in either one of the following two cases:
+ 1. When it has transmitted the ST signal.
+ 2. When the busy-flash signal is returned. The return of the busy-flash signal in the case of congestion at the transit exchange should take place as soon as possible, but in any case within a maximum delay of 10 seconds following the receipt, at the transit exchange, of the digits necessary to determine the routing.
+
+#### 3.6.2 *Abnormal release conditions*
+
+- a) An outgoing international register shall be released in either one of the following two cases:
+
+1. Proceed-to-send signal not received.
+
+To release after the maximum delay of 10 to 20 seconds indicated by the time-out of the seizing signal. Register release after this delay will depend upon the arrangements preferred by the Administrations concerned, but release should preferably take place as quickly as possible after the time-out of the seizing line signal. On the affected incoming circuit, the preferred action is to return a congestion signal.
+
+2. Proceed-to-send signal received.
+
+This case assumes that the proceed-to-send signal has ceased at the incoming end in the normal way but owing to a fault condition the outgoing register has not pulsed out. The outgoing register will be released by the clear-forward/release-guard sequence prompted by the busy-flash signal sent from the incoming end on non-receipt of register signals within the appropriate time. This assumes that the busy-flash signal is received at the outgoing end before the termination of any forced release delay that Administrations may wish to incorporate in the outgoing register.
+
+- b) An incoming international register shall be released in either one of the following two cases:
+ 1. The ST signal not received within a certain time after commencement of the transmission of the proceed-to-send signal from the incoming end.
+ 2. On return of the busy-flash signal, transmitted from the incoming end when an error is detected in the receipt of the register multifrequency signals.
+- c) A transit international register shall be released in any one of the cases stated for the release of the outgoing and incoming registers in §§ a) and b) above.
+
+#### **Recommendation Q.157**
+
+### **3.7 SWITCHING TO THE SPEECH POSITION**
+
+At the outgoing and transit international exchanges, the circuit shall be switched to the speech position when the register (outgoing or transit) is released after sending the ST signal.
+
+At the incoming international exchange, the circuit will be switched to the speech position when the register is released (see § 3.6.1 of Recommendation Q.156).
+
+## CHAPTER IV
+
+## MANUAL TESTING ARRANGEMENTS FOR SIGNALLING SYSTEM No. 5
+
+#### Recommendation Q.161
+
+### 4.1 GENERAL ARRANGEMENTS FOR MANUAL TESTING1)
+
+(see Recommendation Q.107 *bis*)
+
+#### Recommendation Q.162
+
+### 4.2 ROUTINE TESTING OF EQUIPMENT (LOCAL MAINTENANCE)
+
+4.2.1 Routine tests for testing individual items of equipment such as circuit equipment, connecting circuits, operator's line calling equipment, selectors, registers, etc., must be provided for in every international exchange equipped for automatic switching. These routine tests will be made in accordance with the practice followed in each country for the local maintenance of the switching equipment.
+
+4.2.2 The testing equipment must conform to the following principles:
+
+- a) an item of equipment must not be taken for test until it is free;
+- b) an item of equipment taken for test will be marked "engaged" for the duration of the test. Before a circuit equipment is taken for test, the circuit will be withdrawn from service at both international exchanges;
+- c) as an alternative to b), a like item of equipment, known to be properly adjusted, may be switched in, and the item of equipment to be tested is switched out during the test.
+
+4.2.3 Testing of the circuit and signalling equipment should include a check that the specifications of System No. 5 are met in regard to the following:
+
+- a) *Line signalling system*
+Signalling frequencies
+Transmitted signal levels
+Signal frequency leak
+Receiver operate and non-operate limits
+Receiving-end line split
+Sending-end line split
+Line signal codes
+Sending duration of signals
+Recognition time of signals
+Overlap transmission of answer signal on transit calls
+Double seizing
+Time-out and alarm features
+
+---
+
+1) See Recommendation Q.49/O.22: "Specifications for the CCITT automatic transmission measuring and signalling testing equipment ATME No. 2."
+
+#### b) *Register signalling system*
+
+- Signalling frequencies
+- Transmitted signal levels
+- Signal frequency leak
+- Sending duration of signals
+- Receiver operate and non-operate limits
+- Operation of the receiver to a series of pulses
+- Error-checking features
+
+#### 4.2.4 *Simulated end-to-end tests*
+
+It is desirable that a means be provided whereby end-to-end testing can be simulated on a local basis. A local loop-around arrangement permitting an outgoing test call to be routed directly on a four-wire basis into incoming equipment should be provided. The loop-around arrangement replaces the international line and is connected to the circuit equipment under test on the one side and on the other side to similar working spare both-way circuit equipment and signalling equipment having access to the switching system.
+
+#### **Recommendation Q.163**
+
+### **4.3 MANUAL TESTING**
+
+#### 4.3.1 *Functional testing of signalling arrangements*
+
+Functional tests from one end of the circuit to the other can be made in the following three ways:
+
+- a) The first method consists of a rapid verification of satisfactory signal transmission by ensuring that a seizing signal is followed by the return of a proceed-to-end signal, that a clear-forward signal is followed by the return of a release-guard signal.
+- b) The second method consists of verification of satisfactory signal transmission by initiating a test call:
+ - 1. to technical personnel at the distant-end international exchange; or
+ - 2. to a test call signal testing and answering device, if such equipment is available at the distant-end international exchange.
+- c) The third method consists of complete verification of satisfactory line and register signal transmission. The verification consists of a check of ability to:
+ - 1. generate and receive line and register signals;
+ - 2. transmit the appropriate acknowledgement signals;
+ - 3. provide required duration and spacing of MF signals;
+ - 4. complete terminal and transit1) calls.
+
+#### 4.3.2 *First method: rapid test*
+
+- 1. Verification of satisfactory signal transmission:
+ - a) Initiate a seizing signal and verify the receipt and recognition of the proceed-to-send signal from the distant end.
+*Note – Absence of numerical information following termination of the seizing signal may result in receipt of a busy-flash signal provided by some Administrations from the distant-end equipment.*
+ - b) Initiate a clear-forward signal and verify the receipt and recognition of the release-guard signal from the distant end.
+
+---
+
+1) See the note to § 4.3.4.3.
+
+2. Failure to complete the seizing/proceed-to-end signalling sequence or the clear-forward/release-guard signalling sequence should result in the automatic termination of the frequencies being transmitted within 10-20 seconds/4-9 seconds (see Recommendation Q.141, § 2.1.3.1 e).
+3. In the event of a failure, appropriate steps should be taken to locate and correct the trouble.
+4. The above tests are short, simple, and should be performed at least monthly from each end of the circuit as appropriate. This minimum periodicity should be increased to as often as daily if the incidence of trouble encountered is unsatisfactory.
+
+#### 4.3.3 *Second method: test calls*
+
+1. Verification of satisfactory transmission of signals involved in completion of test calls (manual method):
+ - a) Place a call to the technical personnel at the distant international exchange.
+ - b) On completion of connection:
+ - i) the audible ringing tone should be heard;
+ - ii) the answer signal should be received when the call is answered at the distant end.
+ - c) Request distant end to initiate a clear-back signal, followed by an answer signal.
+ - d) A clear-back signal should be received and recognized when the distant end hangs up and a second answer signal should be received and recognized when the distant end re-answers the call.
+ - e) Initiate a forward-transfer signal which should result in bringing in the assistance operator at the distant end.
+ - f) Terminate the call and observe that the circuit restores to the idle condition.
+2. Verification of satisfactory transmission of signals involved in completion of test calls (semi-automatic method).
+
+If test call signal testing and answering devices are available at the distant international exchange, the signal verification tests should be made using this equipment to the extent that the applicable features indicated in 1 above are available.
+
+3. The above tests should be made from each end of the circuit. They should be made monthly when the manual testing methods prescribed in 1 are used.
+
+They may be made daily when semi-automatic test arrangements are available.
+
+#### 4.3.4 *Third method: comprehensive tests; terminal and transit test calls*
+
+1. Verification of satisfactory signal transmission (frequency, level, duration, etc.) involved in terminal and transit calls.
+ - a) These tests are made in conjunction with:
+ - verification and location of faults;
+ - ensuring that new circuits are satisfactory in operation before being brought into service.
+ - b) When establishing new circuits all of the tests outlined in 4.2.3 should have been completed at both terminals. New circuits assigned to Time Assignment Speech Interpolation (TASI) equipment should be patched as non-TASI for the duration of these tests.
+
+##### 2. Terminal calls
+
+Initiate a call to the distant end test centre. Coordinate this test with the distant end so that appropriate test equipment is connected prior to establishing the call. Check the following:
+
+- a) At the originating end check that a seizing signal is following by the receipt and recognition of the proceed-to-send signal from the distant end. Check that the proceed-to-send signal persists until the seizing signal ceases.
+- b) At the distant end check the following:
+
+| | Duration of transmitted signal |
+|-------------------------------------------------------------------------------|---------------------------------------|
+| 1. Interval between termination of seizing signal and start of KP signal..... | 80 ± 20 ms |
+| 2. KP signal duration..... | 100 ± 10 ms |
+| 3. Digital and ST signal duration..... | 55 ± 5 ms |
+| 4. Interval between all signals..... | 55 ± 5 ms |
+
+- c) Check that the audible ringing tone is heard at the originating end.
+- d) At the originating end check that the answer signal is received, recognized and acknowledged. Check that the acknowledgement signal persists until the clear-back signal ceases.
+- e) At the distant end initiate a clear-back signal.
+- f) At the originating end check that a clear-back signal is received, recognized and acknowledged. Check that the acknowledgement signal persists until the clear-back signal ceases.
+- g) At the originating end initiate a forward-transfer signal.
+- h) At the distant end check the receipt of the forward-transfer signal. The transmitted duration of this signal should be $850 \pm 200$ ms. This signal may be subject to TASI clipping.
+- i) At the distant end arrange to transmit a succession of clear-back and answer signals; first at a slow rate, then at a rate which is faster than the system is capable of following.
+- j) At the originating end check during the slow transmission of the switch-hook flashes that each clear-back and answer signal is received and properly recognized. Verify that after the fast transmission of switch-hook flashes the equipment indicates the final position of the switch-hook.
+- k) At the originating end release the circuit and check that the clear-forward signal is followed by the receipt and recognition of the release-guard signal from the distant end. Check that the release-guard signal ceases after the clear-forward signal ceases. Check that the circuit restores to the idle condition.
+- l) At the originating end check that the clear-forward signal sent to the incoming equipment in the idle condition results in the return of the release-guard signal and that the equipment restores to the idle condition.
+- m) At the originating end check that the busy-flash signal is received, recognized and acknowledged. Check that the acknowledgement ceases after the busy-flash signal ceases. (Some Administrations at the incoming end may find it convenient to provide a test call device which prompts the return of a busy-flash signal.)
+
+In normal service the receipt of a busy-flash signal causes (after the acknowledgement) a clear-forward signal to be sent automatically from the international exchange originating the call. On a test call procedure some Administrations may prefer to avoid this process. In this case, the release of the connection is controlled by the personnel at the terminal originating the test call.
+
+*Note on items a) to m)* – As part of the comprehensive tests it may, in certain circumstances such as fault localization, be desirable to test the frequency, level, and duration of received signals. Normally, however, it may be assumed that each Administration has verified the accuracy of its signal transmission locally as covered in § 4.2.3.
+
+##### 3. Transit calls2)
+
+- a) After securing the cooperation of a third international exchange initiate a transit call to this exchange through the international exchange covered in 2 above.
+- b) With the assistance of technical personnel at the third international exchange repeat steps 2 c) to 2 k) except that in step 2 h) measurement of the duration of the forward-transfer signal need not be made.
+
+*Note* – Detailed tests of certain transit features such as that of the transmission of the answer signal on an overlap basis at the transit point should be performed locally.
+
+---
+
+2) When making transit test calls it is not the intention to check the performance or the quality of the circuit beyond the transit exchange, this being completely the responsibility of the Administration concerned. However, it is important that in principle the transit operations can be checked.
+
+#### Recommendation Q.164
+
+### 4.4 TEST EQUIPMENT FOR CHECKING EQUIPMENT AND SIGNALS
+
+#### 4.4.1 General
+
+For local checks of correct equipment operation and for readjusting the equipment, international exchanges should have test equipment available which includes:
+
+- a) Line and register signal generators.
+- b) Signal-measuring apparatus.
+- c) Loop-around equipment (see 4.4.4).
+
+#### 4.4.2 Signal generators
+
+The signal generators should be able to simulate all line and register signals. The generators may be part of test equipment which cycles the equipment to be tested through actual signalling sequences, in a manner which enables rapid complete testing to determine whether the equipment meets the system specifications. The generators should have the following characteristics:
+
+- a) *Line signal generator*
+ - 1) Signal frequencies should be within $\pm 5$ Hz of the nominal signalling frequency or frequencies and shall not vary during the time required for testing.
+ - 2) Signal levels should be variable between the limit given in the specification and be able to be set within $\pm 0.2$ dB.
+ - 3) Signal duration should be long enough so that the signals can be recognized and long enough in the case of compelled signals to complete the acknowledgement process.
+- b) *Register signal generator*
+ - 1. Signal frequencies should be within $\pm 5$ Hz of the nominal signalling frequency or frequencies and shall not vary during the time required for testing.
+ - 2. Signal levels should be variable between the limits given in the specification and be able to be set within $\pm 0.2$ dB.
+ - 3. Signal durations and intervals between signals shall be within the limits given in the specification in Recommendation Q.153, § 3.3.3, for normal operate values and in Recommendation Q.154, § 3.4.1 d), for test operate values.
+
+#### 4.4.3 Signal-measuring equipment
+
+Equipment capable of measuring signal frequencies, signal levels, signal durations and other significant signal time intervals may be part of the test equipment referred to in § 4.4.2, or separate instruments. In either case the characteristics of the measuring equipment should be as follows:
+
+- a) *Line signal-measuring equipment*
+ - 1. Signal frequency or frequencies to be measured to be between the extreme limits given in the specification, the reading being made with an accuracy of $\pm 1$ Hz.
+ - 2. Level of the signal frequency or frequencies measured over the range given in the specification to be measured with an accuracy of $\pm 0.2$ dB.
+ - 3. Signal durations, signal recognition times and other significant time intervals as given in the specification should be measured within an accuracy of 1 ms or $\pm 1\%$ of the nominal duration, whichever yields the higher value. The range of time intervals to be measured is approximately 5 to 1050 ms. Time-out intervals of 10 to 20 seconds and of 4 to 9 seconds should be determinable within an accuracy of $\pm 1$ second.
+
+##### b) *Register signal-measuring equipment*
+
+1. Signal frequency or frequencies to be measured to be between the extreme limits given in the specification, the reading being made with an accuracy of $\pm 1$ Hz.
+ 2. Level of the signal frequency or frequencies measured over the range given in the specification to be measured within an accuracy of $\pm 0.2$ dB.
+ 3. Signal duration and intervals between signals as given in the specification should be measured with an accuracy within 1 ms.
+- c) In regard to measuring time intervals a recorder having a minimum of two input channels may be useful. The recorded characteristic should conform with the accuracy quoted in a) and b) above and be easily connected to the circuit under test. The recorder input characteristic should be such as to have a negligible effect on circuit performance.
+
+#### 4.4.4 *Loop-around equipment*
+
+Local four-wire loop-around equipment should simulate line facilities without introducing signalling degradation. The gain of the loop-around equipment should be set to provide proper transmission levels. Alternatively, if the testing of the individual items of equipment is on a limit test basis it would not be essential to set the gain of the loop to provide the exact transmission levels. In this event a straight patch would be adequate.
+
+# ANNEXES TO SIGNALLING SYSTEM No. 5 SPECIFICATIONS
+
+## ANNEX 1
+
+### Signalling sequences
+
+*Table 1* – Semi-automatic (SA) and automatic (A) terminal traffic.
+
+*Table 2* – Semi-automatic (SA) and automatic (A) transit traffic.
+
+*In these tables the arrows have the following meanings:*
+
+- ▶ transmission of signalling frequency (permanent or pulse emission).
+- ▶ end of transmission of the signalling frequency in the case of its permanent transmission.
+- .....▶ transmission of an audible tone.
+
+## ANNEX 2
+
+### **Description of the operations corresponding to the various normal and abnormal conditions which may arise in setting up a call**
+
+*Table 1* – Outgoing exchange – Normal conditions
+
+*Table 2* – Outgoing exchange – Abnormal conditions
+
+*Table 3* – Incoming exchange – Normal conditions
+
+*Table 4* – Incoming exchange – Abnormal conditions
+
+*Table 5* – Transit exchange – Normal conditions
+
+*Table 6* – Transit exchange – Abnormal conditions
+
+## ANNEX 1
+
+TABLE 1
+
+### Semi-automatic (SA) and automatic (A) terminal traffic
+
+
+
+| Outgoing international exchange | Incoming international exchange |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CALL TO A FREE SUBSCRIBER | |
+| The seizing signal is sent forward when the ST end-of-pulsing condition is recognized in the outgoing register (the speech path is open as long as the register is connected). | Receipt of the seizing signal causes a register at the incoming exchange to be connected; when the latter is ready to receive the digital information a proceed-to-send signal is sent back (the speech path is open as long as the incoming register is connected). |
+| Receipt of the proceed-to-send signal causes the seizing signal to cease. | |
+| It is followed by the sending en bloc in multifrequency code of:
the KP1 signal,
the language or the discriminating digit,
the national (significant) number,
the ST signal. | The end of reception of the seizing signal causes the proceed-to-send signal to cease. |
+| The outgoing register releases after the ST signal has been sent. The speech path through the outgoing exchange is established. | The numerical signals are received in the incoming register. This register starts the setting up of the call in the incoming country when enough digits have been received to determine the routing. The incoming register carries out the appropriate operations according to the language (or discriminating) digit. In SA operation for code 11 or 12 calls, the register directs the call to the operators' positions. The incoming register releases, and sets up the speech path in the incoming exchange as soon as it has sent forward all the information received. |
+| SA: The operator or
A: the calling subscriber
hears the ringing tone. } | The ringing tone of the country of destination is sent back. |
+| SA: An "answer" indication is given to the controlling operator.
A: Charging and measurement of the call duration begin. | The called subscriber answers.
An answer signal is sent back. |
+| Receipt of the answer signal causes an acknowledgement signal to be sent. | Receipt of the acknowledgement ceases the answer signal. |
+| The end of reception of the answer signal ceases the acknowledgement signal. | |
+| SA: A clearing supervisory signal is given to the controlling operator.
A: After 1-2 min., if there is no clear-forward signal, the international connection is released and charging and measurement of the call duration are ceased. | The called subscriber clears.
The clear-back signal is sent back. |
+
+### ANNEX 1
+
+TABLE 1 (continued)
+
+| Outgoing international exchange | Incoming international exchange |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| The clear-back signal causes acknowledgement to be sent. | Receipt of the acknowledgement ceases the clear-back signal. |
+| The end of reception of the clear-back signal ceases the acknowledgement signal. | |
+| The outgoing operator (SA) or the calling subscriber (A) clears.
A clear-forward signal is sent. | The clear-forward signal causes a release-guard signal to be sent back:
a) on receipt of the clear-forward signal, or
b) when the incoming equipment has been released. |
+| The receipt of the release-guard signal ceases the clear-forward signal. | The clear-forward signal is sent in the country of destination. |
+| The end of the release-guard signal terminates the guard condition at the outgoing end. | The release-guard signal is ceased:
a) subject to the two conditions that the incoming equipment has been released and that the clear-forward signal is no longer received;
or
b) subject to the single condition that the clear-forward signal is no longer received. |
+| | The outgoing access of the incoming end is maintained busy for 200 to 300 ms after the cessation of the release-guard signal. |
+| CALL TO A BUSY SUBSCRIBER (OR CONGESTION) | |
+| The signal sequence is the same as for a call to a free subscriber, up to the point where the incoming register releases. | |
+| SA: A "busy" indication is given to the operator. | 2600 |
+| A: The calling subscriber hears the busy tone of the outgoing (national or international) exchange. | 2400 |
+| The busy-flash signal causes the acknowledgement signal to be sent. | 2600 |
+| The end of reception of the busy-flash signal ceases the acknowledgement signal. | 2400 |
+| The cessation of the acknowledgement signal is followed automatically by the sending of the clear-forward signal which releases the international connection. | |
+| SA: The operator, or
A: the calling subscriber
hears the busy tone and clears and the clear-forward signal is sent | 2400 |
+
+#### *1st case*
+
+The national network of the incoming country can give a busy-flash signal. This signal is detected by the incoming international equipment, which sends a busy-flash signal back. The acknowledgement signal ceases the busy-flash signal.
+
+#### *2nd case*
+
+The national network of the incoming country cannot give the busy-flash signal. The busy tone of the incoming country is sent back.
+
+### ANNEX 1
+
+TABLE 1 (concluded)
+
+| Outgoing international exchange | Incoming international exchange |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| SPECIAL CONDITIONS | |
+| 1. FORWARD TRANSFER
1st Case
SA: Following a call switched automatically to a subscriber, or following a call established via a special number or an incoming, or delay operator, the controlling operator wishes to call in an assistance operator at the incoming international exchange. A forward-transfer signal is sent.
2600
2nd Case
SA: Following a call via code 11 or 12, the controlling operator wishes to recall the incoming operator at the incoming international exchange. A forward-transfer signal is sent.
2600
| →
The forward-transfer signal causes an assistance operator to intervene at the incoming international exchange.
→
Recalls the incoming operator on calls completed via the operator positions of this exchange.
|
+| 2. DOUBLE SEIZING
The outgoing end sends the seizing signal.
2400
| →
2400
The incoming end also sends the seizing signal.
|
+| The two ends of the circuit send and receive the seizing signal for a sufficiently long time to ensure that the signal can be recognized at both ends.
The two ends recognize the double seizing by this condition.
| |
+| The equipment is cleared at each end without the sending of a clear-forward signal; then:
| |
+| a) either a second automatic attempt to set up the connection takes place, or
b) { SA: a re-order indication is given to the operator;
A: a busy tone is sent to the subscriber.
| |
+
+### ANNEX 1
+
+#### TABLE 2
+
+#### **Semi-automatic (SA) and automatic (A) transit traffic**
+
+
+
+| Outgoing international exchange | International transit exchange | Incoming international exchange |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CALL TO A FREE SUBSCRIBER | | |
+| A seizing signal is sent forward when the ST end-of-pulsing condition is recognized in the outgoing register (the speech path is open as long as the outgoing register is connected). | 2400 → | Receipt of the seizing signal causes a register at the transit exchange to be connected. The proceed-to-send signal is sent back when the register is connected. (The speech path is open as long as the register is connected.) |
+| Receipt of the proceed-to-send signal ceases the seizing signal. | ← 2600 | |
+| It is followed by the sending en bloc in multi-frequency code of: | 2400 - - - - - → | The end of reception of the seizing signal ceases the proceed-to-send signal. |
+| - – the KP2 signal
- – the country code
- – the language or the discriminating digit
- – the national (significant) number
- – the ST signal.
| ← 2600 - - - - - | |
+| The outgoing register releases after the ST signal has been sent. The speech path through the outgoing exchange is established. | MF 2/6 code → | The numerical signals are received in the register at the transit exchange. |
+| | | When enough digits have been received to determine the routing, a circuit is taken. A seizing signal is sent forward. |
+| | 2400 → | Receipt of the seizing signal causes a register to be connected at the incoming exchange and, when this register is connected, the proceed-to-send signal is sent back (the speech path is open as long as the register is connected). |
+| | ← 2600 | |
+| | 2400 - - - - - → | Receipt of the proceed-to-send signal ceases the seizing signal. |
+| | | The end of reception of the seizing signal ceases the proceed-to-send signal. |
+| | ← 2600 - - - - - | |
+| | MF 2/6 code → | The numerical signals are received in the incoming register. This register starts the setting up of the call in the incoming country when enough digits have been received to determine the routing. |
+| | | The transit register releases after the ST signal has been sent. The speech path through the transit exchange is established. |
+
+ANNEX 1
+TABLE 2 (continued)
+
+
+
+| Outgoing international exchange | International transit exchange | Incoming international exchange |
+|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | The incoming register carries out the appropriate operations according to the language (or dis-criminating) digit. In SA operation for code 11 or 12 calls, the register routes the call to the operator's positions. The incoming register releases and establishes the speech path at the incoming exchange as soon as it has sent forward all the information received. |
+| SA: The operator.
A: The calling subscriber hears the ringing tone. } | | The ringing tone of the incoming country is sent back. |
+| | | The called subscriber answers.
An answer signal is sent back. |
+| | Receipt of the answer signal:
– causes an answer signal to be sent back in "overlap compelled" manner. | 2400 ← |
+| SA: An answer indication is given to the controlling operator. | | 2400 → |
+| Receipt of the answer signal causes an acknowledgement signal to be sent forward. | Receipt of the acknowledgement signal ceases the answer signal. | 2400 ← |
+| | The end of reception of the answer signal ceases the acknowledgement signal. | Receipt of the acknowledgement signal ceases the answer signal. |
+| A: Charging and measurement of the call duration begin. | | 2400 → |
+| The end of reception of the answer signal ceases the acknowledgement signal. | | |
+
+### ANNEX 1
+
+TABLE 2 (continued)
+
+| Outgoing international exchange | International transit exchange | Incoming international exchange |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|
+| | | 2600
The called subscriber clears.
The clear-back signal is sent back. |
+| | Receipt of the clear-back signal:
- causes a clear-back signal to be sent back.
- causes an acknowledgement signal to be sent forward. | 2400
Receipt of the acknowledgement signal ceases the clear-back signal. |
+| SA: A clearing supervisory signal is given to the controlling operator.
Receipt of the clear-back signal causes an acknowledgement signal to be sent forward. | | 2600
----- |
+| A: After 1-2 min. if there is no clear-forward signal, the international connection is released and charging and measurement of the call duration are ceased.
The end of reception of the clear-back signal ceases the acknowledgement signal. | Receipt of the acknowledgement signal ceases the clear-back signal.
The end of reception of the clear-back signal ceases the acknowledgement signal. | 2400
----- |
+| SA: The controlling operator, or
A: The calling subscriber clears.
The clear-forward signal is sent. | | |
+| 2400 + 2600
-----> | Receipt of the clear-forward signal causes:
- a release-guard signal to be sent back:
- a clear-forward signal to be sent forward. | 2400 + 2600
-----> |
+| | a) on receipt of the clear-forward signal, or
b) when the incoming equipment has been released. | 2400 + 2600
-----> |
+| Receipt of the release-guard ceases the clear-forward signal. | Receipt of the release-guard signal ceases the clear-forward signal. | 2400 + 2600
-----> |
+| 2400 + 2600
-----> | | |
+| | | The clear-forward signal is sent in the country of destination. |
+
+### ANNEX 1
+
+TABLE 2 (continued)
+
+
+
+| Outgoing international exchange | International transit exchange | Incoming international exchange |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|
+| The release-guard signal is ceased:
a) subject to the two conditions that the incoming equipment has been released and the clear-forward signal is no longer received, or
b) subject to the single condition that the clear-forward signal is no longer received.
| | |
+| The end of the release-guard signal terminates the guard condition at the outgoing end.
| The end of the release-guard signal terminates the guard conditions at the outgoing end in the transit exchange.
| The outgoing access of the incoming end is maintained busy for 200 to 300 ms after the cessation of the release-guard signal.
|
+| CALL TO A BUSY SUBSCRIBER (OR CONGESTION)
The signal is the same as for a call to a free subscriber up to the point where the incoming register releases
| | |
+| SA: A busy indication is given to the operator
| Receipt of the busy-flash signal:
- – causes the busy-flash signal to be sent back.
- – causes the acknowledgement signal to be sent forward.
| 1st case: The national incoming network gives the busy-flash signal. The busy-flash signal is sent back.
|
+| A: The calling subscriber hears the busy tone sent by the outgoing (national or international) exchange.
| Receipt of the acknowledgement signal ceases the busy-flash signal.
| Receipt of the acknowledgement signal ceases the busy-flash signal.
|
+| Receipt of the busy-flash signal causes an acknowledgement signal to be sent.
| The end of reception of the busy-flash signal ceases the acknowledgement signal.
| |
+
+Sequence diagrams for call signaling between Outgoing, Transit, and Incoming exchanges. The top part shows the release-guard signal sequence with arrows indicating signal flow and text describing conditions for signal cessation. The bottom part shows the busy subscriber signaling sequence, including busy-flash and acknowledgement signals, with a note about the '1st case' for the busy-flash signal origin.
+
+### ANNEX 1
+
+TABLE 2 (concluded)
+
+| Outgoing international exchange | International transit exchange | Incoming international exchange |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| The cessation of the acknowledgement signal is followed automatically by the sending of the clear-forward signal to release the international circuit, clearance being effected from the outgoing exchange.
SA: The operator, or
A: the calling subscriber hears the busy tone and clears. The clear-forward signal is sent.
| | 2nd Case: The national incoming network does not give the busy-flash signal. The busy tone of the incoming country is sent back.
|
+| SPECIAL CONDITIONS
| | |
+| FORWARD-TRANSFER
1st Case
SA: Following a call switched automatically to a subscriber, or following a call established via a special number incoming or delay operator, the controlling operator wishes to call in an assistance operator at the incoming international exchange. A forward-transfer signal is sent.
| 2600 → The forward-transfer signal causes a forward-transfer signal to be sent over the following circuit.
| 2600 → The forward-transfer signal causes an assistance operator to intervene at the incoming international exchange on an established connection completed automatically.
|
+| 2nd Case
SA: Following a call via code 11 or 12, the controlling operator wishes to recall the incoming operator at the incoming international exchange. The forward-transfer signal is sent.
| 2600 → The forward-transfer signal causes a forward-transfer signal to be sent over the following circuit.
| 2600 → Recalls the incoming operator on calls completed via the operators' positions of this exchange.
|
+
+## ANNEX 2
+
+TABLE 1
+
+#### **Outgoing exchange – Normal conditions**
+
+| Conditions | | Subscriber free | Subscriber busy or national congestion | | Congestion at a transit or an incoming exchange or on circuits immediately outgoing from that exchange (after register association) |
+|-----------------------------------------------------|-------------------------------------------------------------------------|-----------------------------|----------------------------------------|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|
+| | | | The busy-flash signal: | | |
+| | | | is not provided | is provided | |
+| Operations effected | Release of register | After sending the ST signal | | | |
+| | Speech position | After release of register | | | |
+| | Action on the international circuit | | | Release of the circuit after reception of a busy-flash signal | |
+| | SA – Local signals given to the operator | | | Busy | |
+| | A – Transmission of an appropriate indication to the calling subscriber | | | Busy tone | |
+| Information received from the international circuit | Signals received | | | | Busy-flash signal |
+| | Audible indication received | Ringing tone | Busy tone | | |
+| References | | 3.6.1 | 3.7 | | 3.6.1, 3.7, 1.6 |
+
+SA = Semi-automatic service
+A = Automatic service
+
+} When there is no specific indication the clause is applicable to both services
+
+## ANNEX 2
+
+TABLE 2
+
+#### **Outgoing exchange – Abnormal conditions**
+
+| Conditions | | The outgoing register receives no more digits | Registration of unused numerical information | Non-receipt of a proceed-to-send signal after sending the seizing signal | The outgoing register not having detected an abnormality, the incoming register receives an incomplete number or a non-existing number and it detects the abnormality |
+|-------------------------------------------------|------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|--------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Operations effected | Release of register | SA – (local sending-finished signal not received):
10-20 seconds a) after seizure or receipt of last digit.
A – 15-30 seconds a) after seizure of no, or less than the minimum number of digits received.
(When enough digits received, 4-6 seconds after the receipt of the last digit, normal ST condition is assumed) | Immediately the abnormality is recognized | 10-20 seconds after the start of sending the seizing signal | After sending the ST signal |
+| | Speech position | (A – After release of the register should ST condition be assumed) | | | After release of the register |
+| | Action on the international circuit | (A – Seized in normal manner should ST condition be assumed) | | Released by clear-forward signal | |
+| | SA – Local signals given to the operator | Determined by each Administration, as this a national matter | | | |
+| | A – Indications given to the subscriber | Appropriate audible indication | | | |
+| Signals received from the international circuit | | | | | Busy-flash |
+| References | | 3.2 | | 3.6.2,
1.9 | 2.1.6 d,
3.6.1 |
+
+a) Typical value.
+
+ANNEX 2
+
+TABLE 3
+
+**Incoming exchange – Normal conditions**
+
+| Conditions
Operations
effected | Called
subscriber free | Subscriber busy or national congestion | | Congestion at the
incoming exchange
or on circuits
immediately
outgoing from that
exchange (after
register association) |
+|--------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|
+| | | The busy-flash signal: | | |
+| | | is not provided | is provided | |
+| Release
of
register | After:
a) sending the numerical information to,
or b) sending an ST signal to,
or c) receipt of and end-of-selection signal from, the national network
equipment | | | After sending
the busy-flash
signal |
+| Speech
position | After release of the register | | | |
+| Sending of
busy-flash signal
on the international
circuit | | | After receipt
of the national
busy-flash
signal | 0-10 seconds after
receipt of the information
necessary for
determining the route |
+| Sending of
an audible
indication | National
ringing
tone | National
busy tone | National
busy tone
(if present) | |
+| References | 3.6.1 b) 1. | 3.6.1 b) 1. | 2.1.6 d) 4.
3.6.1 b) 2. | 1.6
2.1.6 d) 1.
3.6.1 b) 2. |
+
+40
+
+**Signalling System N° 5 (1988)**
+
+### ANNEX 2
+
+TABLE 4
+
+#### **Incoming exchange – Abnormal conditions**
+
+| Conditions
Operations effected | Non-receipt of numerical signals | Error detected in receipt of the numerical signals | ST signal not received | Receipt of an incomplete number or a non-existing number (ST signal received) |
+|------------------------------------------------|---------------------------------------------------------------------|----------------------------------------------------|-----------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Release of register | 10-20 seconds after the start of sending the proceed-to-send signal | immediately the error is recognized | 20-40 seconds a) after the start of sending the proceed-to-send signal | After:
a) sending the numerical information to,
or b) sending an ST signal to,
or c) receipt of an end-of-selection signal from,
or d) receipt of a busy-flash b) signal from, the national network equipment
or e) recognition of the abnormality by the incoming international register |
+| Speech position | After release of the register | | | |
+| Signals sent back on the international circuit | Busy-flash | | | d) Busy-flash
e) Busy-flash |
+| References | 2.1.6 d) | 2.1.6 d) | 2.1.6 d)
3.6.2 b) 1. | 2.1.6 d)
3.6.2 b) 2. |
+
+a) Typical value.
+
+b) For new equipment Administrations may feel it more appropriate to send “special information tone” instead of the Busy Flash.
+
+## ANNEX 2
+
+TABLE 5
+
+### **Transit exchange – Normal conditions**
+
+| Conditions
Operations effected | Successful attempt (as far as transit exchange is concerned) | Congestion at the transit exchange or on international circuits immediately outgoing from that exchange (after register association) |
+|-----------------------------------|--------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|
+| Release of register | After sending the ST signal | After sending the busy-flash signal |
+| Speech position | After release of the register | |
+| Sending of busy-flash signal back | | 0-10 seconds after the receipt of the information necessary for determining the routing |
+| References | 3.6.1 c) 1. | 3.6.1 c) 2. |
+
+## ANNEX 2
+
+TABLE 6
+
+#### **Transit exchange – Abnormal conditions**
+
+| Conditions
Operations effected | Non-receipt of numerical signals | Error detected in the receipt of the numerical signals | ST signal not received | Receipt of unused numerical information | Non-receipt of the proceed-to-send signal after sending the seizing signal |
+|---------------------------------------------------------|---------------------------------------------------------------------|--------------------------------------------------------|-----------------------------------------------------------------------------------|-----------------------------------------|----------------------------------------------------------------------------|
+| Release of register | 10-20 seconds after the start of sending the proceed-to-send signal | Immediately the error is recognized | 20-40 seconds a) after the start of sending the proceed-to-send signal | After recognition of the abnormality | 10-20 seconds after the start of sending the seizing signal |
+| Speech position | After release of the register | | | | |
+| Signals sent back on the incoming international circuit | Busy-flash | | | | |
+| Action on the outgoing international circuit | | | | | Released by clear-forward signal |
+| References | 2.1.6 d) | 2.1.6 d) | 2.1.6 d)
3.6.2 c) | 2.1.6 d) | 2.1.3.1 e)
2.1.6 d)
3.6.2 c) |
+
+a) Typical value.
+
+# INTERWORKING OF SYSTEMS No. 4 AND No. 5
+
+## 1. General
+
+It is possible to ensure normal operation for both semi-automatic and automatic service when interworking takes place between Signalling Systems No. 4 and No. 5, in either the "4 to 5" or "5 to 4" direction.
+
+The interworking is possible because:
+
+- the line signals (i.e. the supervisory signals) generally have the same meaning and the same function in both systems;
+- the numerical (address) information is sent in the same sequence in both systems;
+- all conditions for the use of the language digit in the semi-automatic service and the discriminating digit in the automatic service are the same in both systems.
+
+In general, the interworking of the two systems merely requires that a signal received in the code of one of the systems be converted into the corresponding signal of the code used by the other system. Nevertheless, in a transit exchange where there is interworking of Systems No. 4 and No. 5, special precautions are necessary with regard to signals which are used differently in the two systems. These differences are as follows:
+
+- a) System No. 5 always uses a forward end-of-pulsing signal (the ST signal), whereas the end-of-pulsing signal (code 15) is not always given in System No. 4;
+- b) System No. 4 uses a backward number-received signal which is not provided in System No. 5.
+
+## 2. Calls from System No. 4 to System No. 5
+
+### 2.1 Semi-automatic calls from System No. 4 to System No. 5
+
+
+
+```
+graph LR; A((A)) --- T((T)); T --- B((B)); subgraph System No. 4; A --- T; end; subgraph System No. 5; T --- B; end; CCITT-28480
+```
+
+Diagram showing the interworking of System No. 4 and System No. 5. System No. 4 is represented by a circle labeled 'A'. System No. 5 is represented by a circle labeled 'B'. A transit exchange 'T' is shown between them. The link between A and T is labeled 'System No. 4'. The link between T and B is labeled 'System No. 5'. The diagram is labeled 'CCITT-28480'.
+
+1. In semi-automatic operation, the outgoing exchange A of System No. 4 sends an end-of-pulsing signal over link AT and the outgoing register at A is released.
+2. The end-of-pulsing signal of System No. 4, which is a numerical type signal (code 15), is acknowledged.
+3. On receipt of an end-of-pulsing signal from A, the incoming part of System No. 4 at transit exchange T sends to A an acknowledgement of the end-of-pulsing signal and then sends to A a number-received signal.
+4. At T, an end-of-pulsing signal ST is sent over link TB on System No. 5; this ST signal is obtained by converting the end-of-pulsing signal (code 15) of System No. 4.
+5. At T, the outgoing register1) of System No. 5 is released as soon as the signal ST has been sent over link TB on System No. 5. At T, the incoming register1) of System No. 4 is released after the number-received signal of System No. 4 has been sent back to A.
+
+1) These register functions may be combined in a single register.
+
+*Note* – The number-received signal is sent from T over link TA in order to conform to the specifications of System No. 4. Since the outgoing register at A will be released as soon as A has sent the end-of-pulsing signal (in accordance with the specifications of System No. 4), the only possible role of the number-received signal at A is to indicate to the operator that the selection procedure has been effected. However, since the number-received signal relates only to operations on the link AT on System No. 4, this signal provides no information about the entire selection process from A to B; the indication to the operator is hence of little value.
+
+### 2.2 Automatic calls from System No. 4 to System No. 5
+
+
+
+```
+
+graph LR
+ A((A)) --- T((T))
+ T --- B((B))
+ subgraph System No. 4
+ A
+ T
+ end
+ subgraph System No. 5
+ B
+ end
+ B --- CCITT-28480
+
+```
+
+Diagram of automatic calls from System No. 4 to System No. 5. It shows a line connecting node A (System No. 4) to node T (transit exchange), which is then connected to node B (System No. 5). Node B is labeled CCITT-28480.
+
+1. The System No. 4 link AT does not provide for an end-of-pulsing signal from exchange A in automatic operation; the transit exchange T will therefore have to recognize that all the digits have been received in order to:
+ - a) send a forward ST signal to B in System No. 5; and
+ - b) send a backward number-received signal to A in System No. 4.
+
+In this situation, the System No. 5 register signalling at T will be *en bloc* non-overlap2). (See Recommendation Q.152, § 3.2.1 b) (2) for the action to be taken by the System No. 5 register at T to recognize that all digits have been received.)
+
+2. At A, release of the outgoing register of System No. 4 depends upon reception of the number-received signal.
+
+At the incoming end of System No. 4 at T, the incoming register3) of System No. 4 is released as soon as the number-received signal is sent backward and all the numerical information necessary for setting up the call is sent to B.
+
+At T, an ST end-of-pulsing signal is sent to B by System No. 5 after the numerical information has been sent, and the outgoing register3) of System No. 5 at T is then released.
+
+## 3. Calls from System No. 5 to System No. 4
+
+### 3.1 Semi-automatic calls from System No. 5 to System No. 4
+
+
+
+```
+
+graph LR
+ A((A)) --- T((T))
+ T --- B((B))
+ subgraph System No. 5
+ A
+ T
+ end
+ subgraph System No. 4
+ B
+ end
+ B --- CCITT-28480
+
+```
+
+Diagram of semi-automatic calls from System No. 5 to System No. 4. It shows a line connecting node A (System No. 5) to node T (transit exchange), which is then connected to node B (System No. 4). Node B is labeled CCITT-28480.
+
+1. In semi-automatic operation at transit exchange T the incoming register3) part of System No. 5 receives an ST end-of-pulsing signal 55 ms after reception of the last numerical signal.
+2. At T, the ST end-of-pulsing signal of System No. 5 is converted into an end-of-pulsing signal of System No. 4, which is sent to the incoming end B of this system.
+3. The end-of-pulsing signal of System No. 4, which is a numerical type signal (code 15), is acknowledged.
+4. At A, the outgoing register of System No. 5 is released after the ST signal has been sent.
+
+2) See for this term the footnote to Recommendation Q.151.
+
+3) These register functions may be combined in a single register.
+
+5. At T, the outgoing register3) of System No. 4 is released when the end-of-pulsing signal is sent.
+6. At B, the incoming register of System No. 4 is released as soon as the number-received signal is sent backward to T on System No. 4 and all the numerical information necessary for setting up the call in the incoming country has been sent forward.
+7. The number-received signal is sent over link BT upon reception at B of the end-of-pulsing signal. It will be noted that number-received signal is sent over link BT solely in order to conform to the specifications of System No. 4, even though this signal is superfluous in this case as:
+ - a) the number-received signal is not needed to release the outgoing register of System No. 4 at T since it is released when it sends the end-of-pulsing signal;
+ - b) this signal cannot be used to give any information to the operator at A since it cannot be passed by System No. 5 on link AT.
+
+### 3.2 Automatic calls from System No. 5 to System No. 4
+
+
+
+```
+
+graph LR
+ A((A)) --- T((T))
+ T --- B((B))
+ subgraph SystemNo5 [System No. 5]
+ A
+ end
+ subgraph SystemNo4 [System No. 4]
+ B
+ end
+ style SystemNo5 fill:none,stroke:none
+ style SystemNo4 fill:none,stroke:none
+
+```
+
+Diagram showing the network configuration for automatic calls from System No. 5 to System No. 4. It consists of three nodes: A (System No. 5), T (transit exchange), and B (System No. 4). Node A is connected to node T, and node T is connected to node B. The label 'CCITT-28480' is placed below node B.
+
+1. This situation raises no difficulties since System No. 5 possesses the ST signal which, by determining the end-of-pulsing at T, places the outgoing register of System No. 4 at T in conditions that are comparable to those existing with semi-automatic operation in System No. 4.
+2. At T, the ST signal of System No. 5 is converted into the end-of-pulsing signal (code 15) of System No. 4.
+3. The specifications of System No. 4 require that the incoming exchange B of System No. 4 must send the number-received signal as soon as:
+ - a) an end-of-pulsing signal has been received, or
+ - b) it has recognized that all the digits have been received.
+
+In this case of interworking, condition a) is generally fulfilled first. It may happen, however, that a complete national number is recognized before the end-of-pulsing signal is received (for example, when the number of digits in the national number of the incoming country is constant). The transit exchange T must hence be capable of receiving the number-received signal not only after emission of the end-of-pulsing signal but also when the last digit preceding that signal has been sent.
+
+4. Exchange B must be capable of receiving the end-of-pulsing signal (code 15) on automatic calls.
+
+## 4. Overflow from System No. 5 to System No. 4
+
+4.1 In an exchange equipped with System No. 4 and System No. 5, it may be desirable to provide for overflow from a group of circuits operated by System No. 5 to a group operated by System No. 4. This may be the case for a call outgoing from an exchange A (Figure 1/Q.180) or for a call from an outgoing exchange K (Figure 2/Q.180) and arriving via a group of circuits in System No. 4 at transit exchange T where a choice must be made between a first-choice route operated by System No. 5 and an overflow route operated by System No. 4.
+
+4.2 There are two possible ways of arranging for the overflow, in particular with respect to the moment at which the decision is taken to use the overflow route:
+
+- Single exploration;
+- Double exploration.
+
+3) These register functions may be combined in a single register.
+
+
+
+Diagram of Figure 1/Q.180 showing a network topology. A node A is connected to a node L via a link labeled '4'. Node A is also connected to a node labeled '5', which is part of a link labeled 'CCITT-46960'. Node L is connected to another node labeled '5', which is also part of a link labeled 'CCITT-46960'. Arrows indicate signal flow from A to L and from the node '5' at A to the node '5' at L.
+
+FIGURE 1/Q.180
+
+
+
+Diagram of Figure 2/Q.180 showing a network topology. A node K is connected to a node T via a link labeled '4'. Node T is connected to a node L via a link labeled '4'. Node T is also connected to a node labeled '5', which is part of a link labeled 'CCITT-46970'. Node L is connected to another node labeled '5', which is also part of a link labeled 'CCITT-46970'. Arrows indicate signal flow from K to T, from T to L, and from the node '5' at T to the node '5' at L.
+
+FIGURE 2/Q.180
+
+#### 4.2.1 Single exploration
+
+With single exploration, the state of occupation, or availability, of the System No. 5 group at exchange A or exchange T is considered only when the condition ST is determined at this exchange in the System No. 5 outgoing register.
+
+- If the exploration at A or at T shows that no free circuit in the System No. 5 group is available, overflow to the System No. 4 group takes place.
+
+For this overflow the register has all the numerical information (even in the case of a transit register like that of the T exchange mentioned above), and the end-of-pulsing indication ST. The register at the transit exchange T will be regarded, for successive selection operations, as an outgoing System No. 4 register. Thus, in this case, signalling between the three System No. 4 registers involved will be link-by-link and not end-to-end.
+
+In the case of Figure 2, as soon as the ST condition is available (at the latest immediately after the $5 \pm 1$ seconds delay provided for in the specifications for System No. 5) the number-received signal will be sent back from T to K in System No. 4.
+
+The ST condition will also be used to cause the end-of-pulsing signal (code 15) to be sent forward from T to L, even in automatic working. The code 15 signal will cause the number-received signal to be sent back from L to T, so that there will be no need to wait for five or ten seconds at L before it is known that a complete number has been received.
+
+The number-received signal sent by T will be received at K and will, in the case of an automatic call, release the outgoing register at that exchange. The second number-received signal, which will be sent by L, will be received at T to release the register at that exchange, despite the fact that the register has transmitted an end-of-pulsing signal which could have been used for releasing the register. The establishment of the speech path at T takes place immediately after the release of the register.
+
+If in the case of Figure 1/Q.180 the ST condition is recognized in the outgoing exchange A, even in automatic operation. This end-of-pulsing signal will in the same way cause the number-received signal to be sent back from L to A.
+
+- b) If the exploration at A or at T shows that a free circuit in the System No. 5 group is available, the *en bloc* numerical information has to be transmitted over this circuit, followed by the end-of-pulsing signal ST, in accordance with the specifications for System No. 5.
+
+In the case of Figure 2/Q.180, the conditions for the number-received signal and the release of the outgoing register are the same as under 4.2.1 a).
+
+#### 4.2.2 *Double exploration*
+
+With double exploration the state of availability of the System No. 5 circuit group is examined twice, namely:
+
+- as soon as the direction to be chosen is determined;
+- after receipt of the complete numerical information.
+
+With the double exploration, advantage is taken of the fact that, without awaiting condition ST, exchange A or exchange T can know that the direct route by System No. 5 is occupied as soon as the direction to be chosen is determined.
+
+- a) If the first exploration at A or at T shows that no free circuit in the System No. 5 group is available, overflow to the System No. 4 group should take place immediately; the use of the signals on the System No. 4 circuit(s) must be in accordance with the normal procedure of that system:
+ - in the case of Figure 2, end-to-end working (K-T-L) for the numerical signals and the number-received signal;
+ - the end-of-pulsing signal (code 15) only for semi-automatic calls.
+
+The procedure of overflow at this first exploration reduces post-dialling delay in automatic working since there is no need to wait until all the digital information is assembled *en bloc* before proceeding with the setting up of the connection. On the other hand, there is a slight reduction in the efficiency of the first choice System No. 5 group.
+
+- b) After the first exploration has shown no congestion of the System No. 5 group, it may happen, during or after reception in the outgoing register at A (or transit register, in the case of T) of the digits following the digits necessary to determine the routing, that the System No. 5 group gets busy, more particularly because such a circuit group is a first-choice high-usage route with consequently a high probability of loss. When this happens, after noting by this second exploration that all circuits in the System No. 5 group are busy, overflow to the System No. 4 group takes place.
+
+For this case of overflow, the conditions can be considered to be the same as in 4.2.1 a).
+
+- c) If also the second exploration shows no congestion of System No. 5 group, the conditions mentioned in 4.2.1 b) fully apply.
+
+4.3 Line signalling for calls set up in overflow through two successive No. 4 systems will be done normally, that is, end-to-end. The number-received signal, however, will be sent as stated in 4.2.1 a), 4.2.2 a) or 4.2.2 b).
+
+## 5. *Interworking line signalling conditions*
+
+### 5.1 *Forward-transfer signal*
+
+The forward-transfer signal, in the event of a transit call going from System No. 4 to System No. 5, or from System No. 5 to System No. 4, should cause the assistance operator to intervene in the country of arrival, and not at the transit exchange.
+
+The incoming line relay set of the first system at the transit exchange is informed, e.g. by the transit register, that the call is a transit call. Hence, when a forward-transfer signal arrives on the first system, it causes the forward-transfer signal to be transferred to the outgoing line relay set of the second system without intervention by the operator at the transit exchange.
+
+### 5.2 Answer signal
+
+#### 5.2.1 System No. 4 to System No. 5 (traffic direction)
+
+The answer signal on the System No. 4 link should be sent only after complete recognition of the answer signal received from the System No. 5 link, i.e. overlap transmission should not be used.
+
+The considerations for this requirement are:
+
+- the overlap technique could give rise to troubles in signalling system No. 4 in case of imitation of the P signal;
+- in the transfer of the answer signal from System No. 5 to System No. 4 the sending end line split (silent period) before starting P is a necessity due to the pulse type signals of System No. 4. The requirement for this sending-end line split period ( $40 \pm 10$ ms) would have meant little speed advantage of overlap operation in transferring the answer signal from System No. 5 to System No. 4 (about 40 ms);
+- overlap operation would be contrary to the design characteristic of System No. 4 in that once the sending of a signal has begun it must be sent completely.
+
+#### 5.2.2 System No. 5 to System No. 4 (traffic direction)
+
+In the interworking arrangements in a transit centre for transferring the answer signal backward from System No. 4 to System No. 5, overlap transmission should not be used.
+
+In System No. 4, overlap operation is incompatible with the use of time measurement for recognition of the suffix signal (short suffix or long suffix). The overlap operation would not permit waiting for the end of a signal PY (answer signal), to determine that it is not a PYY signal release-guard signal).
+
+### 5.3 Busy-flash signal
+
+In the case of interworking at a transit point from System No. 4 to System No. 5 or vice versa, a busy-flash signal received at that transit point from the outgoing circuit is to be converted to a busy-flash signal on the incoming circuit.
+
+In the case of interworking from System No. 5 to System No. 4, the busy-flash signal will cause the release of the international connection initiated from the outgoing exchange.
+
+In the case of interworking from System No. 4 to System No. 5, the System No. 5 equipment at this transit exchange should function as an outgoing System No. 5 equipment on the receipt of a busy-flash signal and release the System No. 5 circuit from the transit point. It should be noted that the System No. 4 circuit is also released in the case of automatic calls.
+
+*Note* – In the case of interworking from System No. 5 to System No. 4 it has been determined that no advantage is to be gained by the release of the international connection being initiated only by the outgoing exchange. Therefore in both cases of interworking, the transit exchange and the forward connection may be released immediately on receipt of the busy-flash signal. However, there is no need to modify existing equipment.
+
+#### 5.4 Time-out delays to clear a connection in the event of signal failures
+
+#### 5.4.1 Non-reception of a clear-forward signal after a clear-back signal has been sent
+
+In the event of transit working System No. 4 to System No. 5 at an exchange T, this latter represents the terminal for System No. 4.
+
+The action to be taken at an international incoming exchange for System No. 4 holds good for the exchange T. After a time-out of 2 to 3 minutes, the System No. 4 incoming equipment at T should produce an effect forward on the circuit of System No. 5, so as to release the international circuit (for example, should there be some interruption in the System No. 4 circuit). This release should proceed in the same way as the release of the national part of the connection, when the incoming exchange is indeed the incoming international exchange of the international connection.
+
+For symmetry's sake, the action at T to release the connection should also be undertaken when there is transit working from System No. 5 to System No. 4, since a time-out of 2 to 3 minutes exists in System No. 5 to release the connection forward.
+
+##### 5.4.2 *Delay in clearing by the calling subscriber in automatic working*
+
+In the case of automatic calls with interworking from System No. 4 to System No. 5, or from System No. 5 to System No. 4, release of the international connection as brought about by the time-out of 1 to 2 minutes must take place *at the outgoing exchange only*, and not at the exchange T, the point of connection of the two systems. In exchange T, the outgoing line relay sets of the second system in the connection must accordingly be marked that they are acting, not as relay sets for the terminal outgoing end of the system in question, but as transit exchange relay sets.
+
+##### 5.4.3 *Non-reception of an answer-signal at the outgoing exchange after reception of a number-received signal or generation of the ST condition*
+
+When a connection passes through System No. 4 towards System No. 5, or vice versa, release must be undertaken *at the outgoing exchange only*. Hence nothing must be done at the transit exchange T, the point at which Systems Nos. 4 and 5 are connected.
+
+In the case of System No. 4 towards System No. 5, exchange T represents the connection transit exchange for both systems. Non-reception at T of an answer-signal within 2 to 4 minutes after condition ST has been determined must produce *no* effect at exchange T. It will be for the outgoing exchange to cause release (by sending the clear-forward signal) on the 2 to 4 minutes' time-out after reception of the number-received signal from exchange T.
+
+In the case of System No. 5 towards System No. 4 exchange T represents the connecting transit exchange for both systems. Non-reception at T of an answer-signal within 2 to 4 minutes after reception of the number received-signal from the incoming exchange must *not* affect exchange T. It will be for the outgoing exchange to cause release of the connection (by sending the clear-forward signal) after the delay of 2 to 4 minutes following the generation of the ST condition at that exchange.
+
+# **ANNEXES TO INTERWORKING SPECIFICATIONS OF SYSTEMS No. 4 AND No. 5**
+
+## ANNEX 1
+
+### **Signalling sequences in interworking from System No. 4 to System No. 5**
+
+## ANNEX 2
+
+### **Signalling sequences in interworking from System No. 5 to System No. 4**
+
+*In these tables the arrows have the following meanings:*
+
+- ▶ transmission of a signalling frequency (permanent or pulse emission).
+- - - -▶ end of transmission of the signalling frequency in the case of its permanent transmission.
+- .....▶ transmission of an audible tone.
+
+## ANNEX 1
+
+### Signalling sequences in interworking from system No. 4 to system No. 5
+
+
+
+| Outgoing international exchange
system No. 4 | International transit exchange
system No. 4 to system No. 5 | Incoming international exchange
system No. 5 |
+|-------------------------------------------------------------------------------------------------|----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CALL TO A FREE SUBSCRIBER | | |
+| Transit seizing signal sent forward (speech path open while register associated). | PY → | Causes transit register to be connected (speech path open while register associated). |
+| | ← Y | Transit proceed-to-send signal returned. |
+| Causes the first digit of the country code to be sent forward. | Binary code → | Received in transit register. |
+| | ← y | Digit acknowledgement and request for next digit required. |
+| Causes the next digit and all the other digits of the numerical information to be sent forward. | Binary code → | Received in transit register. Each digit acknowledged. |
+| Received in outgoing register. | ← y | A: Acknowledgement of last digit of national (significant) number.
SA: the last numerical signal to be acknowledged is code 15 (end-of-pulsing) and is acknowledged by x or y. |
+| Received in outgoing register. | ← x or y | |
+| Release of the outgoing register and speech path established: | ← P | The ST condition is now established. A number-received signal is sent back to the outgoing exchange. |
+| SA: after an end-of-pulsing signal is sent. | | |
+| A: after the receipt of the number-received signal. | | |
+
+### ANNEX 1 (continued)
+
+
+
+| Outgoing international exchange system No. 4 | International transit exchange system No. 4 to system No. 5 | Incoming international exchange system n° 5 |
+|------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | A seizing signal is sent to the incoming exchange. 2400 → | Causes a proceed-to-send signal to be returned when a register is connected (speech path open while register associated). ← 2600 |
+| | Causes the cessation of the seizing signal followed by:
- – the sending of KP1
- – the language (or the discriminating) digit
- – the national (significant) number
- – the ST signal.
2400 →
2600 ←
MF 2/6 code → | Causes the cessation of the proceed-to-send signal. ← 2600
Register takes appropriate action on the language (or the discriminating) digit, passes forward the national (significant) number and releases (speech path established). |
+| | Releases of the transit register (speech path established). | |
+| The operator (SA) or the calling subscriber (A) { hears the ringing tone ← | | The ringing tone the incoming country is sent back. |
+| | Receipt of the answer signal, causes:
- – return of an answer signal. ← 2400
- – acknowledgement signal to be sent forward. → 2400
| Called subscriber answers. Answer signal returned. |
+| SA: answer supervisory signal to operator. ← PY | | Causes cessation of the answer signal. ← 2400 |
+| A: both the charging of the subscriber and the measurement of call duration start. | | Causes cessation of the acknowledgement signal. ← 2400 |
+
+### ANNEX 1 (continued)
+
+
+
+| Outgoing international exchange system No. 4 | International transit exchange system No. 4 to system No. 5 | Incoming international exchange system No. 5 |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | Called subscriber clears. |
+| | | 2600 ← Clear-back signal returned. |
+| SA: clearing supervisory signal to the operator. ← PX | Receipt of the clear-back signal, causes:
- - return of a clear-back signal.
- - acknowledgement signal to be sent forward.
| 2400 → Causes cessation of the clear-back signal. |
+| A: after 1-2 min, in the absence of a clear-forward signal, the international connection will be released, and both the charging of the subscriber and the measurement of call duration are ceased. | | 2600 - - - - - → |
+| SA: operator or | | 2400 - - - - - → Causes cessation of the acknowledgement signal. |
+| A: calling subscriber clears. | | |
+| PXX → Clear-forward sent. | Receipt of the clear-forward signal:
- - releases the incoming part of the No. 4 circuit and when fully released sends back a release-guard signal.
- - causes a clear-forward signal to be sent forward.
| 2400 + 2600 → Causes release-guard signal to be returned (see Recommendation Q.141, paragraph 2.1.6). Clear-forward signal sent to national network of incoming country. |
+| PYY ← Causes removal of guard from the outgoing circuit. | | 2400 + 2600 ← |
+| | Causes cessation of clear-forward signal. - - - - - → | 2400 + 2600 → Causes cessation of the release-guard signal (see Recommendation Q.141). |
+| | Causes removal of guard from outgoing circuit. - - - - - → | 2400 + 2600 ← The outgoing access of the incoming end is maintained busy for 200 to 300 ms after the cessation of the release-guard signal. |
+
+### ANNEX 1 (continued)
+
+
+
+| Outgoing international exchange system No. 4 | International transit exchange system No. 4 to system No. 5 | Incoming international exchange system No. 5 |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|----------------------------------------------|
+| CALL TO A BUSY SUBSCRIBER (OR CONGESTION) | | |
+| The sequence of signals is the same as for a call to a free subscriber up to the point at which the incoming register releases. | | |
+| SA: the operator is given a busy indication, the operator then releases the connection.
A: the clear-forward signal is sent forward to automatically release the system No. 4 circuit.
The calling subscriber hears the busy tone from the outgoing (national or international) exchange.
sequenceDiagram participant OIE as Outgoing international exchange system No. 4 participant ITE as International transit exchange system No. 4 to system No. 5 participant IE as Incoming international exchange system No. 5 Note right of IE: 1st Case IE->>ITE: 2600 (busy-flash) Note left of IE: Receipt of the busy-flash signal, causes:
- the sending back of a busy-flash signal.
- the sending of the acknowledgement signal. ITE->>OIE: PX Note right of IE: 2400 IE->>ITE: 2600 Note left of IE: Causes the cessation of the busy-flash signal. ITE-->>IE: 2400 Note right of IE: The cessation of the busy-flash acknowledgement signal is followed by the sending forward of the clear-forward signal to the incoming international exchange to automatically release the system No. 5 circuit. Note right of IE: 2nd Case Note left of IE: The national network of the incoming country cannot give a busy-flash signal. The busy tone of the incoming country is sent back. Note left of OIE: The operator and/or the calling subscriber hears the busy tone and releases the connection.
1st Case
The national network of the incoming country can give a busy-flash signal. This is detected by the incoming international exchange which returns the busy-flash signal.
Causes the cessation of the busy-flash signal.
2nd Case
The national network of the incoming country cannot give a busy-flash signal. The busy tone of the incoming country is sent back.
| | |
+
+Sequence diagram for 'Call to a Busy Subscriber' showing signal exchanges between three exchanges. The diagram includes signal types like PX, 2600, and 2400, and two cases for the busy signal handling.
+
+### ANNEX 1 (concluded)
+
+| Outgoing international exchange system No. 4 | International transit exchange system No. 4 to system No. 5 | Incoming international exchange system No. 5 |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|
+| SPECIAL CONDITIONS | | |
+| 1st Case: | | |
+| SA: Following a call switched automatically to a subscriber, or following a call established via a special number incoming or delay operator, the controlling operator wishes to call in an assistance operator at the incoming international exchange. A forward-transfer signal is sent.
| PYY → Causes the sending of a forward-transfer signal on the next circuit.
| 2600 → Causes an assistance operator to intervene at the incoming international exchange.
|
+| 2nd Case: | | |
+| SA: Following a call via code 11 or 12, the controlling operator wishes to recall the incoming operator at the incoming international exchange. A forward-transfer signal is sent.
| PYY → Causes the sending of a forward-transfer signal on the next circuit.
| 2600 → Recalls the incoming operator on calls completed via the operator positions of this incoming international exchange.
|
+
+## ANNEX 2
+
+### Signalling sequences in interworking from System No. 5 to System No. 4
+
+
+
+| Outgoing international exchange
system No. 5 | International transit exchange
system No. 5 to system No. 4 | Incoming international exchange
system No. 4 |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|
+| SETTING UP OF THE CONNECTION | | |
+| A seizing signal is sent when the ST-condition is recognized. | 2400 → | |
+| | ← 2600 | Causes the connection of a register. When a register is connected a proceed-to-send signal is returned. |
+| Causes cessation of the seizing signal, followed by the sending en bloc of | 2400 → | |
+| - – KP2 signal
- – country code
- – language or discriminating digit
- – national (significant) number
- – ST signal.
| ← 2600 | Causes cessation of the proceed-to-send signal. |
+| Release of the register (speech path established). | MF 2/6 code → | |
+| | | PX → |
+| | | ← X |
+| | | Causes the sending of the language or discriminating digit, national (significant) number + code 15. |
+| | | Binary code → |
+| | | ← x |
+| | | Digit-acknowledgement signals. |
+| | | Release of the register (speech path established). |
+| | | Setting up of the call in the incoming country. |
+| | | P → |
+| | | ← |
+| | | After the determination of a "complete number" a number-received signal is sent. Release of the register (speech path established). |
+
+## ANNEX 2 (continued)
+
+
+
+| Outgoing international exchange system No. 5 | International transit exchange system No. 5 to system No. 4 | Incoming international exchange system No. 4 |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|--------------------------------------------------------|
+| CALL TO A FREE SUBSCRIBER | | |
+| The operator (SA) or the calling subscriber (A) } hears the ringing tone.
| | The ringing tone of the incoming country is sent back. |
+| | 2400 ← | PY → |
+| SA: Answer supervisory signal to the operator
| Receipt of the answer signal causes return of an answer signal.
| Called party answers.
|
+| Causes an acknowledgement signal to be sent.
| 2400 → | Answer signal returned.
|
+| A: Both charging of the subscriber and measurement of call duration start.
| Causes the cessation of the answer signal.
| |
+| | 2400 ← | |
+| Causes the cessation of the acknowledgement signal.
| 2400 → | |
+| | | Called party clears.
|
+| | 2600 ← | PX → |
+| SA: Clearing supervisory signal to the operator.
| Receipt of the clear-back signal causes return of a clear-back signal.
| Clear-back signal returned.
|
+| Causes an acknowledgement signal to be sent.
| 2400 → | |
+| A: After 1 to 2 minutes, if there is no clear-forward signal, the international connection is released and charging of the subscriber and measurement of call duration are then ceased.
| Causes the cessation of the clear-back signal.
| |
+| | 2600 ← | |
+| Causes the cessation of the acknowledgement signal.
| 2400 → | |
+
+## ANNEX 2 (continued)
+
+
+
+| Outgoing international exchange system No. 5 | International transit exchange system No. 5 to system No. 4 | Incoming international exchange system No. 4 |
+|---------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| The operator (SA) or the calling subscriber (A) clears.
Clear-forward signal sent.
| | |
+| | Causes the sending of: | |
+| | - – a release-guard signal backward (see Q.141, para 2.1.6).
- – a clear-forward signal forward.
| |
+| Causes cessation of the clear-forward signal. | | PXX → |
+| | Causes cessation of the release-guard signal (see Q.141). | |
+| Causes removal of guard from the outgoing circuit. | | PYY ← |
+| | The outgoing access of the incoming end is maintained busy for 200 to 300 ms after the cessation of the release-guard signal. | Releases the connection and when the release is fully effective a release-guard signal is returned. |
+| CALL TO A BUSY SUBSCRIBER (OR CONGESTION) | | |
+| The sequence of signals is the same as for a call to a free subscriber up to the point at which the incoming register releases. | | |
+| | | 1st Case:
The national network of the incoming country can give a busy-flash signal. This signal is detected by the incoming international equipment, which sends the busy-flash signal back. |
+| | | PX ← |
+| SA: A busy indication is given to the operator. | Receipt of the busy-flash signal causes a busy-flash signal to be sent back. | |
+| Causes an acknowledgement signal to be sent. | 2600 ← | |
+| | 2400 → | |
+| A: The calling subscriber hears the busy tone of the outgoing (national or international) exchange. | Causes the cessation of the acknowledgement signal, followed by the automatic release of the connection (see above). | |
+| | 2600 ← | |
+| | 2400 → | |
+
+### ANNEX 2 (concluded)
+
+| Outgoing international exchange system No. 5 | International transit exchange system No. 5 to system No. 4 | Incoming international exchange system No. 4 |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| The operator and/or the calling subscriber hears the busy tone and releases the connection (see above).
| | 2nd Case:
The national network of the incoming country cannot give a busy-flash signal. The busy tone of the incoming country is sent back.
|
+| SPECIAL CONDITIONS
| | |
+| 1st Case:
SA: Following a call switched automatically to a subscriber, or following a call established via a special number incoming or delay operator, the controlling operator wishes to call in an assistance operator at the incoming international exchange. A forward-transfer signal is sent.
| 2600 → Causes the sending of a forward-transfer signal on the next circuit.
| PYY → Causes an assistance operator to intervene at the incoming international exchange.
|
+| 2nd Case:
SA: Following a call via code 11 or 12, the controlling operator wishes to recall the incoming operator at the incoming international exchange. A forward-transfer signal is sent.
| 2600 → Causes the sending of a forward-transfer signal on the next circuit.
| PYY → Recalls the incoming operator on calls completed via the operator positions of this exchange.
|
+
+
+
+
+
+# SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure and Internet protocol aspects |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.1702-200206-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1702-200206-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..57ec23fda09e262f977bf0e5cffbe2f1bdfcb45c
--- /dev/null
+++ b/marked/Q/T-REC-Q.1702-200206-I_PDF-E/raw.md
@@ -0,0 +1,376 @@
+
+
+
+
+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.1702**
+
+(06/2002)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Signalling requirements and protocols for IMT-2000
+
+---
+
+**Long-term vision of network aspects for
+systems beyond IMT-2000**
+
+ITU-T Recommendation Q.1702
+
+---
+
+# 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 SYSTEM No. 4 | Q.120–Q.139 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 5 | Q.140–Q.199 |
+| 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 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# **ITU-T Recommendation Q.1702**
+
+# **Long-term vision of network aspects for systems beyond IMT-2000**
+
+## **Summary**
+
+This Recommendation addresses the envisaged network environment, network design objectives, and architecture concepts of Systems Beyond IMT-2000. This Recommendation, together with a draft ITU-R Recommendation which covers the radio aspects, form the ITU long-term vision for Systems Beyond IMT-2000.
+
+## **Source**
+
+ITU-T Recommendation Q.1702 was prepared by ITU-T SSG (2001-2004) and approved under the WTSA Resolution 1 procedure on 29 June 2002.
+
+## **Keywords**
+
+Long-Term Vision, Network Aspects, Systems Beyond IMT-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 2002
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## CONTENTS
+
+###### Page
+
+| | | |
+|-----|-------------------------------------------------------------|---|
+| 1 | Scope ..... | 1 |
+| 2 | References..... | 1 |
+| 3 | Definitions ..... | 1 |
+| 4 | Abbreviations..... | 2 |
+| 5 | Envisaged network environment around the year 2010 ..... | 2 |
+| 5.1 | Market trends..... | 2 |
+| 5.2 | Technology trends ..... | 3 |
+| 6 | Key long-term network design objectives ..... | 3 |
+| 6.1 | Broadband and multiple bearer service capability ..... | 3 |
+| 6.2 | Service expandability and application service support ..... | 4 |
+| 6.3 | Security support..... | 4 |
+| 6.4 | User platform support..... | 4 |
+| 6.5 | High performance and system efficiency ..... | 4 |
+| 6.6 | System flexibility..... | 4 |
+| 6.7 | System scalability..... | 6 |
+| 6.8 | System interoperability..... | 6 |
+| 6.9 | System robustness ..... | 6 |
+| 7 | Long-term network architecture concepts ..... | 6 |
+
+# **Introduction**
+
+The ITU-T and ITU-R have collaborated to develop a single ITU vision of Systems Beyond IMT-2000 targeted for initial deployment around the year 2010, subject to market considerations. This common ITU Vision is the nucleus and foundation for the development of related Recommendations in both the Telecommunication Standardization Sector and the Radiocommunication Sector. This relationship is responsive to ITU-T Resolution 38 and ITU-R Resolution 50 which require the development of roadmaps on IMT-2000 in an independent, but well-coordinated manner.
+
+There is a definite trend towards integration of access networks (e.g., cellular, wireless local area network, personal area wireless network, satellite systems, and Internet.) Based on this trend, it is envisioned that the network environment of Systems Beyond IMT-2000 will consist of packet-based network infrastructure offering a plethora of converged services.
+
+# Long-term vision of network aspects for systems beyond IMT-2000
+
+# 1 Scope
+
+The scope of this Recommendation is to provide a long-term vision (around the year 2010) for the network aspects of Systems Beyond IMT-2000. The further development of existing IMT-2000 systems is not addressed by 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.
+
+- [1] ITU-T Recommendation X.233 (1997) *Information technology – Protocol for providing the connectionless-mode network service: Protocol specification.*
+- [2] ITU-T Recommendation I.113 (1997) *Vocabulary of terms for broadband aspects of ISDN.*
+- [3] ITU-T Recommendation H.323 (2000) *Packet-based multimedia communications systems.*
+- [4] ITU-R Recommendation M.687-2 (1997) *International Mobile Telecommunications-2000 (IMT-2000).*
+- [5] ITU-R Recommendation M.1311 (1997) *Framework for modularity and radio commonality within IMT-2000.*
+
+# 3 Definitions
+
+This Recommendation defines the following terms:
+
+**3.1 converged services:** The integration of Internet, multimedia, e-mail, presence, instant messaging, m-commerce, etc., services with voice service.
+
+**3.2 mobility:** The ability to provide services irrespective of changes that may occur by user/terminal's activities.
+
+**3.3 multicast:** Data transmission to one or more destinations in a selected group in a single service invocation. [1]
+
+**3.4 multimedia:** The combination of multiple forms of media such as audio, video, text, graphics, fax, and telephony in the communication of information.
+
+**3.5 multimedia service:** A service in which the interchanged information consists of more than one type, such as text, graphics, sound, image and video. [2]
+
+**3.6 seamless service:** Seamless Service will prevent users from experiencing any service disruptions while maintaining mobility or portability.
+
+**3.7 session continuity:** The ability of the user to maintain continuity of ongoing sessions while changing between terminal devices and across various access and core networks. For example, the user of a mobile terminal may wish to switch from his mobile equipment attached to a wireless network to a laptop connected to a wire-line or Digital Subscriber Line connection. This should be
+
+supported without any session discontinuity.
+
+**3.8 unicast:** A process of transmitting messages from one source to one destination. [3]
+
+**3.9 virtual reality services:** The ability for users to access the sights and sounds of remotely located complex systems in real-time.
+
+# 4 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|-------|----------------------------------------------------------|
+| API | Application Programming Interface |
+| ASP | Application Service Provider |
+| IMT | International Mobile Telecommunications |
+| IP | Internet Protocol |
+| Mbps | Mega bits per second |
+| OAM&P | Operations, Administration, Maintenance and Provisioning |
+| PAN | Personal Access Network |
+| QoS | Quality of Service |
+| WLAN | Wireless Local Area Network |
+
+# 5 Envisaged network environment around the year 2010
+
+The following network environment around the year 2010 is envisaged to facilitate the identification of future needs of users, service capabilities, and network capabilities at that time.
+
+## 5.1 Market trends
+
+- High-speed data connection is a norm in accessing multimedia services and Internet services, even in the wireless environment, due to additional spectrum, efficient spectrum utilization, and advanced radio technologies. Because of these advancements, "Virtual Reality Services" becomes widely available.
+- The core network is fully Internet Protocol (IP)-based and service provisioning is distributed around the core network. Wireless access is just one of the access methods to the IP-based core network, services, and applications.
+- There exist many complementary wireless networks for voice and data applications in addition to International Mobile Telecommunications-2000 (IMT-2000) terrestrial and satellite-based systems. Some examples are Bluetooth and Wireless Local Area Network (WLAN). A limited integration among these wireless networks and IMT-2000 systems exists.
+- Digital TV with data service capability is ubiquitous.
+- The number of users around the year 2010 could grow to more than 1700 million wireless subscribers with a great number of them having several different terminals for communications. A majority of the user populations is computer proficient and quick to adopt of advanced technologies to enhance quality of life and productivity.
+- There exist Application Service Providers (ASPs) utilizing mobile networks as a means to offer unique services taking advantage of mobile terminal capabilities and location information.
+- Large numbers of users move internationally wanting to use their services anytime anywhere with their personal terminals.
+
+- Services are the driver: the role of technology is to enable provision of services (and capacities) that the users are willing to pay for.
+
+## 5.2 Technology trends
+
+- Software-defined radio technology has become a main element in the wireless infrastructure and handset implementations. Because of this technology, new and advanced radio technologies are easily introduced and deployed by the Network operators and Service providers to differentiate their services.
+- Mobile terminals may form a closed network, or an *ad hoc* network, which enables direct communications between them. Transmission speed could be independent between an uplink and a downlink. Systems Beyond IMT-2000 are expected to act as platforms to effectively deliver traffic within and between the *ad hoc* networks and to offer additional values to them, such as advanced mobility management techniques.
+- Mobility management will be more than supporting higher speed objects such as vehicles. It will be needed to support applications with very large IP multimedia traffic needs, and with diversified communications including person-to-person, machine-to-machine, machine-to-person and vice versa.
+- The concept of seamless services will be extended beyond handover and roaming services.
+- Diverse end-users' individual needs will require flexibility to deal with their preferences or contexts.
+- The following network security environment around the year 2010 is envisaged:
+ - Highly efficient security mechanisms are available in a multimedia environment to process high-speed and high volume information flows.
+ - There exist user transparent access authentication and authorization mechanisms to provide protection in different access environments.
+ - The security infrastructure is supported across service providers.
+ - The capacity of security servers is scaled to provide service for massive network usage.
+ - Seamless security is available to maintain the same security strength with unreduced performance in handover procedures.
+
+# 6 Key long-term network design objectives
+
+The set of network capabilities existing for current IMT-2000 Family Member Systems should be included for Systems Beyond IMT-2000, as needed. The key long-term network design objectives for Systems Beyond IMT-2000 are listed in the following subclauses.
+
+## 6.1 Broadband and multiple bearer service capability
+
+- Access is based on advanced radio access technologies that can enable transmission speeds well beyond the current IMT-2000 radio access target speeds of 2 Mega bits per second (Mbps).
+- Access support includes the ability to handle the diverse Quality of Service (QoS) needs of future applications, including considerations for:
+ - non-real-time / best effort service,
+ - quasi-real-time (such as streaming) service, and
+ - real-time service (such as voice and video telephony)
+- Cooperation with broadcast networks (hybrid networks) is included to open up new applications (e.g., navigation, traffic information, interactive multimedia services.)
+
+## 6.2 Service expandability and application service support
+
+- Encourages appearances of diversified ASPs by supporting their services and offering additional values to them.
+- Provides multiple service combination capabilities with appropriate mechanisms to handle service interaction and service invocation.
+ - Traditional telecommunications service invoking methods are mostly based on service Application Programming Interface (API) and its capabilities. In service provisioning components, the objective is changed to provide flexible service provisioning based on trigger objects, which will enable automatic interaction and invoking of a series of service logic instances that might be fully distributed in different elements.
+ - Service interactions will support variable exchange of information element types.
+ - Service combinations may be created dynamically, based on a user's profile/situation selections that best fit the user's present usage environment. Users can also build a situation profile in a real-time fashion.
+ - The service combination capability should support backward compatibility with existing service platforms.
+- Supports modularized service control and open service architecture.
+- Simplifies service expansion and dynamic creation of multi-facet services at session level.
+- Supports flexibility for adoption of new services.
+- Provides seamless service capabilities across networks.
+
+## 6.3 Security support
+
+Provides seamless security protection in Systems Beyond IMT-2000 networks.
+
+## 6.4 User platform support
+
+- Mobile users may form a closed *ad hoc* network and communicate directly with each other within that *ad hoc* network. In addition, these users may also wish to communicate normally for conventional communication. Such access requirements must be supported.
+- A group of users may move collectively with respect to a core network (e.g., users in a train, aeroplane, ship, etc.) Such a group may be open or closed. Systems beyond IMT-2000 should accommodate the access requirements of such users. [4]
+- User platforms should provide a natural communication-oriented man-machine interface.
+
+## 6.5 High performance and system efficiency
+
+- Efficient handling of very large IP multimedia traffic with various predefined service parameters.
+- Support of a wide range of traffic ratios within the network, including unicast, multicast, broadcast and bursty traffic.
+- Distributing service provisioning according to provider's resource control policy.
+
+## 6.6 System flexibility
+
+- Support Moving Networks:
+ - A Moving Network is a network that can move in the same manner as a terminal in mobile systems. For example, a Moving Network could be in a train, ship or aeroplane, etc.
+- Accommodate diverse access technologies/schemes.
+
+- A key long-term network design objective for Systems Beyond IMT-2000 should be its flexibility to accommodate diverse access technologies/schemes.
+- Future mobile devices are expected to support numerous access technologies (including a variety of wireless and/or wire-line choices.) A key network design goal should be to facilitate a judicious choice of appropriate access technology for a particular usage environment. The choice should be based on:
+ - a) availability of access technologies at the mobile user location,
+ - b) speed and QoS requirements of the user application,
+ - c) cost of using the access technology, etc.
+- Separate control and transport functions.
+ - Control functions in the IP-based network platform should be open to support various existing and future evolution signalling systems, and its function will be more focused on signalling processing.
+ - Transport functions should fully utilize IP transport capability to direct user traffic flows to their proper destinations.
+ - The interface between control and transport functions should be open and standardized.
+ - When the control and transport functions are implemented in the same physical equipment, the interface(s) between them still should be opened.
+- Facilitate support of multiple switching control methods, signalling at different layers and their combinations.
+ - Switching components in the IP-based network platform may provide multiple switching control methods, and may also provide interoperation among these methods.
+ - Switching control methods may be implemented according to their service support requirements, and thus, may be functioning at different internetworking layers.
+ - The usage of IP transport for various switching control signalling should be used according to service requirements.
+- Support open interface for roaming and handover among various networks.
+- Automatically manage the access means (including both wired access and wireless access) based on user defined criteria such as cost, speed, QoS, privacy, applications, etc.
+- Have flexible, efficient, and integrated mobility management, i.e., flexibility to support advanced mobility management schemes including:
+ - Location Management:
+ - Location Registration;
+ - Paging.
+ - Routing Management:
+ - Handover.
+ - Session Continuity:
+ - Seamless Session Transfer;
+ - Diversity Handover across access and core networks;
+ - Having a flexible, efficient, and integrated mobility management, i.e., flexibility to support advanced mobility management.
+ - Support an efficient and adaptive combination of location registration and IP paging functions.
+ - Support dynamic network capacity changes.
+
+## 6.7 System scalability
+
+Systems Beyond IMT-2000 are expected to handle very large amounts of multimedia traffic to/from a large number of mobile users. The multimedia applications run by the mobile users will have diverse traffic and performance/QoS requirements. Advanced mobility management techniques are needed to handle the QoS requirements (e.g., satisfying QoS requirements of a mobile application during a sequence of handovers.) The system must also take into consideration all the access technology choices the user may have in a particular network environment. Advanced mobility management schemes are needed to handle multicast and broadcast requirements of geographically dispersed mobile multimedia users.
+
+## 6.8 System interoperability
+
+- Support global standards, e.g., standardized interfaces between networks.
+- Effective and user-friendly Operations, Administration, Maintenance and Provisioning (OAM&P) facilities.
+- Interoperability with existing third generation mobile networks. Interoperability in this case means the availability of well-defined gateway points and functions between both networks.
+- Integration/inter-operation with alternative networks, e.g., a Personal Access Network (PAN), a WLAN.
+
+## 6.9 System robustness
+
+Provide network security among heterogeneous inter-connected networks. The security objectives shall include the following aspects:
+
+- Comprehensive and cross-provider security infrastructure support.
+- Well-defined and conducted routine system risk analysis.
+- Robust system intrusion monitoring and response system to control damage.
+- Low overhead security protocols to accommodate wireless bandwidth limitation.
+- Provide seamless security across heterogeneous access technologies.
+
+# 7 Long-term network architecture concepts
+
+The network part of Systems Beyond IMT-2000 will be flexible, versatile and new services will be easy-to-deploy. Systems Beyond IMT-2000 are likely to be realized according to the following general principles:
+
+- Network architecture based on IP technology;
+- Modular construction using expandable components; and
+- Open interfaces between various systems.
+
+An IP-based network concept is likely to be used for future development and standardization efforts.
+
+The high-level architecture of Systems Beyond IMT-2000 may be envisaged to include user platform, IP-based network platform, and service provisioning platform. The IP-based network platform includes two types of components: access network components and core network components.
+
+The user platform allows a user to gain access to services in conjunction with the access and core networks. User platform can be subdivided into a number of components.
+
+Access network components are access technology dependent. They include multiple wireless and wire-line access technologies. Core network components are access technology independent. They
+
+include functional components such as control functions and transport functions.
+
+It is anticipated that radio access components of Systems Beyond IMT-2000 can dynamically support various radio transmission requirements. In addition to these radio access components, other access components to provide interconnection with other fixed networks are also needed in the IP-based network platform. [5]
+
+Core network components will provide control functions and transport functions.
+
+It is envisaged that a service provisioning mechanism that can dynamically provide user-defined combined multiple media services at a session level is needed. The service provisioning platform supports such a multiple service combination capability.
+
+Service provisioning mechanisms in Systems Beyond IMT-2000 are envisaged to become more flexible in a multi-stage distributed manner. Such a distributed service provisioning platform is expected to help explore the network service potential of Systems Beyond IMT-2000.
+
+
+
+
+
+## **SERIES OF ITU-T RECOMMENDATIONS**
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure and Internet protocol aspects |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.1721-200006-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1721-200006-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..b4af5f7b663ecc925df04edb76934a62591ac90c
--- /dev/null
+++ b/marked/Q/T-REC-Q.1721-200006-I_PDF-E/raw.md
@@ -0,0 +1,7604 @@
+
+
+
+
+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.1721**
+
+(06/2000)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Signalling requirements and protocols for IMT-2000
+
+---
+
+**Information flows for imt-2000 capability set 1**
+
+ITU-T Recommendation Q.1721
+
+(Formerly CCITT Recommendation)
+
+---
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+# **SWITCHING AND SIGNALLING**
+
+| | |
+|-----------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# **INFORMATION FLOWS FOR IMT-2000 CAPABILITY SET 1**
+
+## **Summary**
+
+This Recommendation specifies Stage 2 information flow procedures for the support of end-to-end inter-family and inter-system IMT-2000 Capability Set 1 (CS-1) services and network capabilities. The areas covered are mobility management, call and bearer control, services control, and over-the-air authorization services.
+
+## **Source**
+
+ITU-T Recommendation Q.1721 was prepared by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution 1 procedure on 15 June 2000.
+
+### **Keywords**
+
+CN, CS-1, IMT-2000, LMFh, LMFv, MT, NNI, RAN, UIM, VHE.
+
+## FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
+
+The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+### NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 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 ..... | 3 |
+| 4 | Abbreviations and acronyms..... | 3 |
+| 5 | Introduction..... | 6 |
+| 5.1 | Description of information flow modelling techniques ..... | 7 |
+| 5.1.1 | Functional models..... | 7 |
+| 5.1.2 | End-to-end subsystem relationship model..... | 9 |
+| 5.1.3 | Information flow sequence type..... | 10 |
+| 5.2 | Information flow template ..... | 11 |
+| 6 | Mobility management ..... | 13 |
+| 6.1 | Authentication management ..... | 14 |
+| 6.1.1 | UIM holder authorization ..... | 14 |
+| 6.1.2 | User authentication ..... | 15 |
+| 6.2 | Location management ..... | 35 |
+| 6.2.1 | Subscriber data management ..... | 35 |
+| 6.2.2 | Identity retrieval – user ..... | 41 |
+| 6.2.3 | Registration management ..... | 46 |
+| 6.2.4 | Location data fault recovery ..... | 54 |
+| 7 | Basic call and bearer control..... | 57 |
+| 7.1 | Mobile outgoing call ..... | 57 |
+| 7.1.1 | Initial mobile outgoing call..... | 58 |
+| 7.1.2 | Additional mobile outgoing call ..... | 60 |
+| 7.2 | Terminal paging..... | 60 |
+| 7.3 | Network call routing ..... | 61 |
+| 7.4 | Mobile incoming call ..... | 64 |
+| 7.4.1 | Initial mobile incoming call..... | 64 |
+| 7.4.2 | Additional mobile incoming call ..... | 66 |
+| 7.5 | Mobile call release ..... | 66 |
+| 7.5.1 | Normal release: mobile initiated..... | 66 |
+| 7.5.2 | Normal release: network initiated..... | 68 |
+| 7.6 | Emergency calls ..... | 69 |
+| 7.6.1 | Emergency call origination..... | 69 |
+| 7.6.2 | Emergency call release: network initiated ..... | 69 |
+| 7.6.3 | Emergency call release: mobile initiated ..... | 69 |
+
+| | Page | |
+|--------|----------------------------------------------------------|-----|
+| 7.7 | Priority calls ..... | 70 |
+| 8 | Multimedia call and bearer control ..... | 70 |
+| 8.1 | Teleservice change ..... | 70 |
+| 8.2 | Add media during a call (mobile user originating) ..... | 72 |
+| 8.3 | Drop media from an active call ..... | 74 |
+| 8.4 | Point-to-multipoint call ..... | 75 |
+| 8.4.1 | Party addition (mobile-to-mobile) ..... | 75 |
+| 8.4.2 | Party dropping ..... | 79 |
+| 8.5 | Access to Internet services ..... | 82 |
+| 8.5.1 | Packet data service session establishment ..... | 82 |
+| 8.5.2 | Roaming during an established packet data session ..... | 86 |
+| 8.5.3 | Packet data service session termination ..... | 92 |
+| 9 | Virtual Home Environment ..... | 96 |
+| 9.1 | "Direct Home Command" ..... | 96 |
+| 9.1.1 | High level "Direct Home Command" service procedure ..... | 96 |
+| 9.1.2 | "Direct Home Command" – Call related services ..... | 98 |
+| 9.1.3 | "Direct Home Command" – LMF invoked services ..... | 100 |
+| 9.1.4 | "Direct Home Command" – AMF invoked services ..... | 101 |
+| 9.2 | "Relay Service Control" ..... | 102 |
+| 9.2.1 | "Relay Service Control" service procedure ..... | 103 |
+| 10 | Messaging services applications ..... | 105 |
+| 10.1 | Short message service (SMS) ..... | 105 |
+| 10.1.1 | SMS notification transfer ..... | 105 |
+| 10.1.2 | Mobile originated short message ..... | 108 |
+| 10.1.3 | Mobile terminated short message ..... | 112 |
+| 10.2 | Teleservice message broadcast (TMB) ..... | 117 |
+| 10.3 | Message waiting notification (MWN) ..... | 120 |
+| 10.3.1 | MWN information flows ..... | 120 |
+| 11 | Supplementary service procedures ..... | 121 |
+| 11.1 | Get password ..... | 122 |
+| 11.2 | Register password ..... | 123 |
+| 11.3 | Register SS ..... | 124 |
+| 11.4 | Erase SS ..... | 126 |
+| 11.5 | Activate SS ..... | 127 |
+| 11.6 | Deactivate SS ..... | 128 |
+| 11.7 | Interrogate SS ..... | 130 |
+
+| | Page |
+|-------------------------------------------------------------------------------------|-------------|
+| 11.8 Invoke SS ..... | 132 |
+| 11.9 Process unstructured SS request ..... | 133 |
+| 11.10 Unstructured SS request..... | 134 |
+| 11.11 Unstructured SS notify..... | 136 |
+| 11.12 SS invocation notification..... | 138 |
+| 12 Over-the-air services..... | 139 |
+| 12.1 Over-the-air service provisioning (OTASP) ..... | 139 |
+| 12.2 Overview..... | 139 |
+| 12.3 Description..... | 140 |
+| 12.4 Over-the-air service provisioning information flows..... | 140 |
+| 12.4.1 Invocation of activation with desired service provider..... | 140 |
+| 12.4.2 A-key generation..... | 144 |
+| 12.4.3 Re-authentication for voice and signalling ciphering..... | 148 |
+| 12.4.4 Transfer of OTASP data ..... | 151 |
+| 13 Definitions of information elements ..... | 153 |
+| Annex A – List of common procedure modules used in this Recommendation..... | 161 |
+| Appendix I – Q.1721 Coverage of Table 1/Q.1701, Capability Set 1 Requirements ..... | 162 |
+| Appendix II – A-key generation..... | 171 |
+| II.1 Introduction..... | 171 |
+| II.2 A-key Generation using the Diffie-Hellman Algorithm ..... | 171 |
+| Appendix III – Bibliography ..... | 171 |
+
+# **INFORMATION FLOWS FOR IMT-2000 CAPABILITY SET 1**
+
+## **1 Scope**
+
+This Recommendation provides the Stage 2 end-to-end inter-family information flows for IMT-2000 Capability Set 1 (CS-1) services and network capabilities. It is specified according to the Stage 2 methodology described in ITU-T Recommendation Q.65 [1]. Companion ITU-T Recommendations, Q.1701 [2] and Q.1711 [3], form the basis for this Recommendation. Used together, these Recommendations form a Stage 2 description that identifies the functional capability and information flows needed to support the Stage 1 IMT-2000 services and network capabilities.
+
+This Recommendation covers information flows for the UIM to MT interface, the MT to RAN+CN interface, and the CN to CN interface (also known as the NNI.) The information flows described cover the successful cases only. The unsuccessful cases are outside the scope of this Recommendation and are best handled as part of the Stage 3 development. Companion Q-series Recommendations Q.1731, Q.1741 and Q.1751 complement the end-to-end view of Recommendation Q.1721 by addressing interface specific aspects of these interfaces.
+
+This Recommendation does not include Radio Resource Management (RRM), Base Station Management (BSM) or RAN-CN information flows. RRM is covered elsewhere. BSM and RAN-CN information flows are outside the scope of IMT-2000 CS-1 per section 8.1/Q.1701.
+
+The following paragraphs provide a brief overview of the contents of each of the clauses of this Recommendation.
+
+Clauses 2, 3 and 4 provide references, definitions and a list of abbreviations and acronyms relevant to the content of this Recommendation.
+
+Clause 5, "Introduction", provides context for the remainder of this Recommendation. It includes the overall protocol architecture, identification of the functional models used from Recommendation Q.1711, an end-to-end network model, information flow sequence types and the information flow template.
+
+Clause 6, "Mobility Management", describes the information flows for managing authentication, including UIM holder verification, user and network authentication and terminal identification. It then addresses location management, including geographic positioning, subscriber data management, user profile interrogation, identity retrieval, registration management and location data fault recovery.
+
+Clause 7, "Call and Bearer Control", describes basic incoming and outgoing mobile calls, including terminal paging, routing, emergency calls and priority calls.
+
+Clause 8, "Multimedia Call and Bearer Control", describes information flows and procedures for changing a teleservice during a call (switching between voice and data communications), adding and dropping a medium within an existing call, and changing communication configurations by adding and dropping a party in a data call. Access to the Internet is also covered in this clause.
+
+Clause 9, "Virtual Home Environment", provides the information flows for the Direct Home Command (DHC) and Relay Service Control (RSC) methods. (The use of IN to support supplementary services within a network is outside the scope of this Recommendation.)
+
+Clause 10, "Messaging Service Applications", describes short message services, teleservice message broadcast and message waiting notification information flows and procedures.
+
+Clause 11, "Generic Supplementary Service Procedures", provides information flows for a suite of general purpose procedures that may be used by various supplementary services.
+
+Clause 12, "Over-the-Air Service Provisioning", describes information flows for over-the-air service provisioning procedures.
+
+Clause 13, "Definitions of Information Elements", defines what the various information elements used in this Recommendation mean.
+
+Annex A provides a listing of all the common procedure modules used within this Recommendation and the clause number where they are described.
+
+Appendix I, "Q.1721 Coverage of Table 1/Q.1701, Capability Set 1 Requirements", provides linkage between Table 1/Q.1701, the capabilities required of IMT-2000 Capability Set 1 and the contents of this Recommendation.
+
+Appendix II, "A-Key Generation", provides a brief overview of this topic, including the Diffie-Hellman algorithm.
+
+Appendix III, "Bibliography", provides a list of additional references to supplement the specific references listed in clause 2.
+
+# 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 available ITU-T Recommendations is regularly published.
+
+- [1] ITU-T Recommendation Q.65 (2000), *The unified functional methodology for the characterization of services and network capabilities including alternative Object Oriented Techniques*.
+- [2] ITU-T Recommendation Q.1701 (1999), *Framework for IMT-2000 networks*.
+- [3] ITU-T Recommendation Q.1711 (1999), *Network functional model for IMT-2000*.
+- [4] ITU-T Recommendation A.3 (1996), *Elaboration and presentation of texts and development of terminology and other means of expression for Recommendations of the ITU Telecommunication Standardization Sector*.
+- [5] ITU-T Q.1200-series Recommendations, *Intelligent networks*.
+- [6] ITU-T Recommendation E.164 (1997), *The international public telecommunication numbering plan*.
+- [7] ITU-T Recommendation E.212 (1988), *Identification Plan for Land Mobile Stations*.
+- [8] ITU-T Recommendation E.213 (1988), *Telephone and ISDN numbering plan for land mobile stations in public land mobile networks*.
+- [9] ITU-T Recommendation X.121 (1996), *International numbering plan for public data networks*.
+- [10] ITU-T Recommendation Q.931 (1998), *ISDN user-network interface layer 3 specification for basic call control*.
+- [11] ITU-T Recommendation Q.762 (1997), *Signalling System No. 7 – ISDN User Part general functions of messages and signals*.
+
+# 3 Definitions
+
+This Recommendation defines the following terms:
+
+- 3.1 anchor core network:** In a data session roaming environment, the anchor core network is the network where the data session is initiated and a packet service gateway is assigned to the mobile terminal. The anchor core network may be either the home or the visited network.
+- 3.2 man machine interface:** The interaction of the user and network via a subscriber device.
+- 3.3 request indication:** The information flow sent from one functional entity to another requesting a specific action. This is referred to as req.ind.
+- 3.4 response confirmation:** The information flow sent by the requested functional confirming that the requested action has been successfully completed. This is referred to as resp.conf.
+- 3.5 service application:** The provision of services by general purpose capabilities, such as Intelligent Network capabilities as applied at the home location or at a visited location as part of a Virtual Home Environment.
+- 3.6 service control:** Functions that set or modify the context, in which basic calls and bearers are established, modified and released.
+- 3.7 subscriber:** The user of a mobile terminal who has subscribed to the service.
+- 3.8 supplementary service application:** The provision of a specific supplementary service, typically through use of service specific capabilities, whether at the home location or at the visited location as part of a Virtual Home Environment.
+- 3.9 user:** The user of a mobile terminal.
+- 3.10 virtual home environment:** The provision of a service experience to the subscriber identical to, or as similar as possible to the service environment the subscriber experiences when served at his/her home location.
+
+NOTE 1 – The terms "user" and "subscriber" are used interchangeably in this Recommendation.
+
+NOTE 2 – The home network is synonymous with home core network (CNh).
+
+NOTE 3 – The visited network is synonymous with visited core network (CNv).
+
+Clause 13, "Definitions of Information Elements", defines what the various information elements used in this Recommendation mean.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|-------|---------------------------------------|
+| A-key | Authentication Key |
+| AC | Authentication Centre |
+| ACSM | Authentication Control State Model |
+| ADDS | Application Data Delivery Service |
+| AMF | Authentication Management Function |
+| AMSC | Anchor Mobile Switching Centre |
+| AMSM | Authentication Management State Model |
+| ARF | Access link Relay Function |
+| AUTH | Authentication Response |
+| BCSM | Basic Call State Model |
+
+| | |
+|----------|----------------------------------------------|
+| BS | Base Station |
+| CC | Call Control |
+| CCAF' | Call Control Agent Function (enhanced) |
+| CCF | Call Control Function |
+| CCF' | Call Control Function (enhanced) |
+| CHCNT | Call History Count |
+| CN | Core Network |
+| CNa | Core Network (anchored) |
+| CnCAF | Connection Control Agent Function |
+| CnCF | Connection Control Function |
+| CNdest | Core Network (destination) |
+| CNh | Core Network (home) |
+| CNpv | Core Network (previous visited) |
+| CNs | Core Network (supporting) |
+| CNv | Core Network (visited) |
+| conf. | confirmation |
+| CS | Capability Set |
+| DFP | Distributed Functional Plane |
+| DHC | Direct Home Command |
+| FE | Functional Entity |
+| FEA | Functional Entity Action |
+| FT | Fixed Terminal |
+| GC | Global Challenge/response mechanism |
+| GPCF | Geographic Position Control Function |
+| GPF | Geographic Position Function |
+| ID | Identity |
+| IF | Information Flow |
+| IMT-2000 | International Mobile Telecommunications-2000 |
+| IMUI | International Mobile User Identity |
+| IN | Intelligent Network |
+| ind. | indication |
+| IP | Internet Protocol |
+| ISP | Internet Service Provider |
+| ITDN | International Temporary Directory Number |
+| LMF | Location Management Function |
+| LMFh | Location Management Function (home) |
+| LMFp | Location Management Function (packet) |
+
+| | |
+|-------|----------------------------------------------|
+| LMFv | Location Management Function (visited) |
+| LMSM | Location Management State Model |
+| MCF | Mobile Control Function |
+| MGPF | Mobile Geographic Position Function |
+| MMI | Man Machine Interface |
+| MRTR | Mobile Radio Transmission and Reception |
+| MSC | Mobile Switching Centre |
+| MT | Mobile Terminal |
+| MWN | Message Waiting Notification |
+| NAI | Network Access Identifier |
+| NNI | Network-to-Network Interface |
+| OTASP | Over-the-Air Service Provisioning |
+| PDGN | Packet Data Gateway Node |
+| PDN | Public Data Network |
+| PDSN | Packet Data Serving Node |
+| PIN | Personal Identification Number |
+| PSCAF | Packet Service Control Agent Function |
+| PSCF | Packet Service Control Function |
+| PSGCF | Packet Service Gateway Control Function |
+| QoS | Quality of Service |
+| RACAF | Radio Access Control Agent Function |
+| RAN | Radio Access Network |
+| RAND | Random Number |
+| RANDC | Random Number (Challenge) |
+| RANDG | Random Number (Global) |
+| req. | request |
+| resp. | response |
+| RF | Radio Frequency |
+| RFTR | Radio Frequency Transmission and Reception |
+| RNC | Radio Network Controller |
+| RSC | Relay Service Control |
+| SACF | Service Access Control Function |
+| SCF | Service Control Function |
+| SCP | Service Control Point |
+| SDF | Service Data Function |
+| SDP | Service Data Point |
+| SIBF | System access Information Broadcast Function |
+
+| | |
+|------|-----------------------------------------|
+| SLP | Service Logic Program |
+| SMF | Service Management Function |
+| SMS | Short Message Service |
+| SNCF | Satellite Network Control Function |
+| SPI | Security Parameter Index |
+| SRES | Signature Result |
+| SRF | Specialized Resource Function |
+| SSD | Shared Secret Data |
+| SSF | Service Switching Function |
+| TMB | Teleservice Message Broadcast |
+| TMUI | Temporary Mobile User Identifier |
+| UC | Unique Challenge/response mechanism |
+| UIM | User Identity Module |
+| UIMF | User Identification Management Function |
+| UPT | Universal Personal Telecommunication |
+| USSD | Unstructured Supplementary Service Data |
+| VHE | Virtual Home Environment |
+
+# 5 Introduction
+
+This Recommendation describes the information flows for end-to-end inter-family IMT-2000 procedures, which are necessary for the support of IMT-2000 CS-1 services and network capabilities. The description of information flows contains the list of information elements that are exchanged between the interacting functional entities. In addition, the functional entity actions (FEAs) performed by the receiving entity are also described.
+
+The modelling techniques used in describing the information flows for IMT-2000 procedures are outlined below.
+
+The information flows specified in this Recommendation for the various IMT-2000 services and network capabilities control many aspects of the IMT-2000 network for which signalling and protocol requirements need to be specified. These are as follows:
+
+- Service control, including:
+ - multimedia services;
+ - Virtual Home Environment (VHE);
+ - messaging services; and
+ - supplementary services.
+- Mobility management and Authentication control.
+- Call control.
+- Bearer control.
+
+This Recommendation does not address radio resource management.
+
+Common procedure modules are listed in Annex A. These basic modules are reused in a variety of tasks which are composites of these basic procedures and other procedures specific to those tasks.
+
+A fundamental principle that has been applied throughout this Recommendation is "separation of concerns". Strict separation enables both functional and protocol independence for each of the areas addressed, thereby ensuring that each may evolve and provide greater capabilities without requiring that other areas be reworked simultaneously.
+
+Within the framework of IMT-2000 networks, as specified in Recommendation Q.1701, Figure 5.1 captures the boundaries where these separations have been applied to guide the development of IMT-2000 signalling and protocol requirements.
+
+
+
+The diagram illustrates the overall information flows architecture across five main components: UIM, MT, RAN, CN, and Other CN. It is organized into several horizontal layers and functional blocks:
+
+- Service Application (Home):** Two horizontal arrows at the top spanning from UIM to Other CN.
+- Control Plane:**
+ - A block on the right side contains: Mobility Management, Service Control, Call Control, and Bearer Control. A note below indicates: "Mobility Management, Service Control, Call Control and Bearer Control may be routed to different destinations".
+ - The MT (Mobile Terminal) contains an L3 block with: Mobility Management, Service Control, Call Control, and Bearer Control.
+ - The RAN (Radio Access Network) contains sub-blocks for L3 RRM (Radio Resource Management) and L3 BSM (Base Station Management).
+ - Vertical layers are labeled: L3 (across MT and RAN), L2 (across MT, RAN, and CN), and L1 (across all components).
+ - An arrow labeled "L3 - L7" spans from UIM to MT.
+- Data Plane:**
+ - A block on the far right contains: Data Packets, and a note "Call and Bearer Control may use IP/ATM".
+ - Horizontal arrows for data flow are shown at the L2 and L1 layers across the CN and Other CN components.
+
+T11105250-00
+
+Figure 5-1/Q.1721 – Overall information flows architecture diagram showing layers and components across UIM, MT, RAN, CN, and Other CN.
+
+Figure 5-1/Q.1721 – Overall information flows architecture
+
+## 5.1 Description of information flow modelling techniques
+
+This subclause provides two functional models specified in ITU-T Recommendation Q.1711 [3], namely, "Integrated call control and connection control model" and "Separated call control and connection control model". In addition, this subclause defines an end-to-end subsystem relationship model.
+
+### 5.1.1 Functional models
+
+Figure 5.1.1-1 is the same as Figure 5-1a/Q.1711 and is an IMT-2000 functional model illustrating an integrated call control and connection control FE. Refer to clause 6/Q.1711 for details.
+
+
+
+The diagram illustrates the functional model for IMT-2000, organized into four vertical domains: UIM, MT, RAN, and CN. A horizontal dashed line separates the 'Communication and Service Control' (top) from the 'Radio Access Control' (bottom).
+
+- UIM (User Interface Management):** Contains UIMF.
+- MT (Mobile Terminal):** Contains MGPF, PSCAF, CCAF', MCF, and RACAF.
+- RAN (Radio Access Network):** Contains GPF, SNCF, SIBF, RACF, RFTR, and two ARF units.
+- CN (Core Network):** Contains GPCF, PSGCF, PSCF, LMF, AMF, SDF, SCF, SRF, CCF'/SSF, and SACF.
+
+Key connections include:
+
+
+- UIMF connects to MGPF, PSCAF, and SACF.
+- MGPF connects to GPCF and RACAF.
+- PSCAF connects to PSCF and RACAF.
+- CCAF' connects to CCF'/SSF.
+- MCF connects to SACF.
+- RACAF connects to RACF and MRTR.
+- GPF connects to GPCF and RACF.
+- SNCF connects to RACF.
+- SIBF connects to RACF.
+- RACF connects to RFTR and ARF.
+- MRTR connects to RFTR.
+- GPCF connects to AMF and LMF.
+- PSGCF connects to LMF.
+- PSCF connects to LMF.
+- LMF connects to AMF, SDF, SCF, and CCF'/SSF.
+- AMF connects to SDF.
+- SDF connects to SCF.
+- SCF connects to SRF.
+- CCF'/SSF connects to SACF.
+
+T11105260-00
+
+Functional model diagram for IMT-2000 (integrated call control and connection control) showing components across four domains: UIM, MT, RAN, and CN. The diagram is divided into two horizontal sections: 'Communication and Service Control' (top) and 'Radio Access Control' (bottom).
+
+**Figure 5.1.1-1/Q.1721 – IMT-2000 functional model (integrated call control and connection control)**
+
+Figure 5.1.1-2 is the same as Figure 5-1b/Q.1711 and is an IMT-2000 functional model illustrating separated call control and connection control FEs. Refer to clause 6/Q.1711 for details.
+
+
+
+Figure 5.1.1-2/Q.1721 – IMT-2000 functional model (separated call control and connection control). The diagram shows functional elements (FEs) organized into four vertical columns: UIM, MT, RAN, and CN. A horizontal dashed line separates the 'Communication and Service Control' (top) from the 'Radio Access Control' (bottom). FEs include MGPF, PSCAF, CCAF', CnCAF, UIMF, MCF, GPF, SNCF, SIBF, RACAF, MRTR, RACF, RFTR, GPCF, PSGCF, PSCF, AMF, LMF, SDF, SCF, SRF, CCF'/SSF, CnCF, and ARF. Lines represent functional relationships between these elements across the subsystems.
+
+T11105270-00
+
+**Figure 5.1.1-2/Q.1721 – IMT-2000 functional model (separated call control and connection control)**
+
+It should be noted that a mapping of the FEs to the subsystems UIM, MT, RAN and CN, as defined in Q.1701, is also shown in the models to reflect the applicability of the IMT-2000 Family of Systems concept. It should also be noted that the allocation of FEs to the RAN and CN subsystems is preliminary (refer to Q.1711 for more details).
+
+### 5.1.2 End-to-end subsystem relationship model
+
+The end-to-end functional network relationship model illustrates the network perspective via Functional Subsystems (FS) defined in Q.1701 and Q.1711 (i.e. UIM, MT, RAN and CN) and their associations with multiple users. As illustrated in Figure 5.1.2-1, the end-to-end network model contains three user end points. This is used to illustrate more advanced services such as conference calling, simultaneous establishment of point-to-multipoint bearer services.
+
+
+
+**Possible Relationships**
+
+Diagram illustrating the IMT-2000 end-to-end subsystem relationship model. It shows three parties (A, B, and C) and their network components. Party A consists of a UIM, MT, RAN+CNv, CNs A, and CNh A. Party B consists of CNh B, CNs B, RAN+CNv, MT, and UIM. Party C consists of CNh C, CNs C, RAN+CNv a), FT, and UIM. Arrows indicate relationships: 'Supporting Network for Party A' to CNs A; 'Home Network for Party A' to CNh A; 'Home Network for Party B' to CNh B; 'Supporting Network for Party B' to CNs B; 'Previous Visited Network' to CNpv; 'Home Network for Party C' to CNh C; and 'Supporting Network for Party C' to CNs C. Lines connect CNh A to CNh B, CNh B to CNh C, CNh C to CNh A, and CNh A to CNpv. RAN+CNv blocks are interconnected with lines.
+
+**RAN+CN** Visited Radio Access Network + Core Network
+**UIM** User Identity Module
+**MT** Mobile Terminal
+**CNpv** Previous visited Core Network
+**CNh** Home Core Network
+**CNs** Supporting Core Network
+**FT** Fixed Terminal
+
+T11105280-00
+
+a) This Functional Subsystem could be replaced by other network subsystems to illustrate internetworking with other networks such as PSTN, ISDN, etc.
+
+**Figure 5.1.2-1/Q.1721 – The IMT-2000 end-to-end subsystem relationship model**
+
+The Core Network may serve in several different roles:
+
+- CNpv = Core Network (previous visited): The network entity that previously was associated with the visited mobile terminal.
+- CNh = Core Network (home): where the home Location Management Function (LMFh) and the home Authentication Management Function (AMFh) are located.
+- CNs = Core Network (supporting network): where the home Service Control Function (SCFh), home Service Data Function (SDFh) and the home Specialized Resource Function (SRFh) are located.
+
+### 5.1.3 Information flow sequence type
+
+An information flow consists of two parts: Information Flow Function Name and Flow Sequence Type. Figure 5.1.3-1 illustrates the possible action types.
+
+
+
+| Flow Sequence Type I
(Confirmed Success: Failure is not reported) | Flow Sequence Type II
(Confirmed Failure: Success is not reported) | Flow Sequence Type III
(Confirmed Success or Failure: whichever applies is reported) | Flow Sequence Type IV
(Unconfirmed: neither Success nor Failure is reported) |
+|----------------------------------------------------------------------|-----------------------------------------------------------------------|-----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|
+| Success
| Success
| Success
| Success
|
+| Failure
| Failure
| Failure
| Failure
|
+
+NOTE – "X" represents Information Flow Function Name, while req.ind. is an example of a type that could be associated with the Information Flow Function Name.
+
+T11105290-00
+
+Sequence diagram for Type I Success: Client sends X req.ind. to Server, Server responds with X resp.conf. Success is confirmed. Sequence diagram for Type II Success: Client sends X req.ind. to Server, Server does not respond. Success is not confirmed. Sequence diagram for Type III Success: Client sends X req.ind. to Server, Server responds with X resp.conf. Success is confirmed. Sequence diagram for Type IV Success: Client sends X req.ind. to Server, Server does not respond. Success is not confirmed. Sequence diagram for Type I Failure: Client sends X req.ind. to Server, Server does not respond. Failure is not confirmed. Sequence diagram for Type II Failure: Client sends X req.ind. to Server, Server responds with X resp.conf. Failure is confirmed. Sequence diagram for Type III Failure: Client sends X req.ind. to Server, Server responds with X resp.conf. Failure is confirmed. Sequence diagram for Type IV Failure: Client sends X req.ind. to Server, Server does not respond. Failure is not confirmed.
+
+**Figure 5.1.3-1/Q.1721 – Information flow sequence type**
+
+The above figure illustrates four types of information flow sequences. Each type describes the specific information flows that constitute that type. The first type is client-server information flow sequence, and the result is a confirmed success, with failure not confirmed. The second type is also client-server information flow sequence, but the result is a confirmed failure, with success not confirmed. The third type is a confirmed notification of either success or failure as applicable. The fourth type is an unconfirmed notification.
+
+The "resp.conf." flow is in response to a previous "req.ind." flow, and as such it carries a unique "Transaction ID" associated with it. This "Transaction ID" is used to tie each pair of "req.ind." and "resp.conf." flows. Therefore, there is no need to repeat any user identification such as IMT-2000 International Mobile User Identity (IMUI) or IMT-2000 International Mobile Directory Number (IMDN) within the "resp.conf." flow.
+
+## 5.2 Information flow template
+
+This subclause describes the template used in developing the information flow (IF) procedures.
+
+### X.Y.Z "Name of procedure (e.g. Terminal location registration)"
+
+*In this clause, provide a brief prose description of the service or network capability. "X.Y.Z" is the subclause heading number in Q.1721. This subclause contains a detailed information flow diagram for the service or network capability using the template provided below. See Figure 5.2-1.*
+
+
+
+The diagram is a sequence diagram with five lifelines: UIM, MT, RAN+CNv, CNh, and CNpv. Each lifeline has a corresponding entity name below it: UIMF, MCF, SACF, LMF, LMF, and LMF. The diagram is divided into six horizontal time steps, numbered 0 to 5.
+ - At time 0, an 'Initiating stimulus' is shown as an arrow from UIMF to MCF.
+ - At time 1, an 'Info flow name req.ind.' message is shown as an arrow from MCF to SACF.
+ - At time 2, an 'Info flow name resp.conf.' message is shown as an arrow from SACF back to MCF.
+ - At time 3, a dashed box labeled 'Info flow name req.ind.' is shown, with an arrow pointing from the box to the LMF under CNh.
+ - At time 4, a solid box labeled 'Procedure name' spans across the lifelines of UIMF, MCF, SACF, and LMF (under CNh).
+ - At time 5, a dashed box labeled 'Procedure name' spans across the lifelines of MCF, SACF, and LMF (under CNh).
+ The diagram is labeled 'T11105300-00' at the bottom right.
+
+Sequence diagram showing information flow between UIM, MT, RAN+CNv, CNh, and CNpv. The diagram includes an initiating stimulus, info flow name req.ind., info flow name resp.conf., and procedure name elements across six time steps (0-5).
+
+Figure 5.2-1/Q.1721 – The IMT-2000 information flow diagram template
+
+This subclause consists of paragraphs each dedicated to one information flow of the IF diagram. For each information flow, a detailed description is provided on the information flow name, type (e.g. req.ind. or resp.conf.), the information elements within the information flow, whether each IE is mandatory or optional (M/O), in the sequence as shown in the IF diagram. FE actions (FEA) are also provided in this clause. Common actions such as "receiving and analysing a flow" and "generating the next flow" are assumed for each entity that receives a flow and, therefore, not included in the description of FEAs. This subclause format is proposed as follows:
+
+0. **Initial information flow:** Describe initiating FE Action (FEA) leading to the first IF (Flow #1).
+
+| | |
+|------|--------------------------------------------------------------------|
+| FEA0 | – Describe the action of the FE at the receiving end of this flow. |
+|------|--------------------------------------------------------------------|
+
+1. **Information flow #1, flow name, flow sequence type:** A brief description of the flow and its start and end FEs to be followed by the content of the flow's information elements, as shown in the table below. When an IE is "O", conditions for its inclusion must be specified and response to its presence when received must also be specified, e.g.: include IE #2 when condition xyz occurs. For IFs that are of req.ind. type, indicate whether a response is required based on successful outcome to the received IF, failed outcome, both or neither, e.g. "Response: Success or Failure".
+
+| IF name (Response: Success/Failure/Success or Failure/None) | req.ind. |
+|-------------------------------------------------------------|----------|
+| IE #1 (e.g. Called user identity) | M/O |
+| IE #2 | M/O |
+| IE #3 | M/O |
+
+| | |
+|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|
+| FEA1 | – Description of functional entity action(s) at receiving end of this flow. |
+| NOTE – Describe the conditions of optionality for IEs that are optional. | |
+
+2. **Information flow #2, flow name, flow type:** *A brief description of the flow and its start and end FEs to be followed by the content of the flow's information elements as follows. When an IE is "O", conditions for its inclusion must be specified and response to its presence when received must also be specified, e.g.: when IE #6 is received, do wxy. For resp.conf., indication of Response is not applicable.*
+
+| IF name | resp.conf. |
+|---------|------------|
+| IE #4 | M/O |
+| IE #5 | M/O |
+| IE #6 | M/O |
+
+| | |
+|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|
+| FEA2 | – Description of functional entity action(s) at receiving end of this flow. |
+| NOTE – Describe the conditions of optionality for IEs that are optional. | |
+
+3. **Information flow #3, flow name, flow sequence type:** *A brief description of the flow and its start and end FEs to be followed by the content of the flow's information elements, as shown below. When an IE is "O", conditions for its inclusion must be specified and response to its presence when received must also be specified, e.g.: include IE #2 when condition xyz occurs. For IFs that are of req.ind. type, indicate whether a response is required based on successful outcome to the received IF, failed outcome, both or neither, e.g. "Response: Success or Failure".*
+
+| IF name (Response: Success/Failure/Success or Failure/None) | req.ind. |
+|-------------------------------------------------------------|----------|
+| IE #1 | M/O |
+| IE #2 | M/O |
+| IE #3 | M/O |
+
+| | |
+|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|
+| FEA3 | – Description of functional entity action(s) at receiving end of this flow. |
+| NOTE – Describe the conditions of optionality for IEs that are optional. | |
+
+4. **Information flow #4, Procedure name:** *A brief statement about the common procedure that is carried out at this point in the sequence.*
+
+| | |
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA4 | - – Description of functional entity action(s) at end of this procedure at the FE defined by the specifics of the procedure itself.
- – If the next procedure is optional as in this template, then include the conditions on when it should or should not be carried out.
|
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+5. **Information flow #5, Procedure name:** *A brief statement about the optional common procedure that is carried out at this point in the sequence.*
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA5 | - – Description of functional entity action(s) at end of this procedure at the FE defined by the specifics of the procedure itself.
- – As this completes the procedure illustrated in the template, "No further action" may be indicated.
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+# 6 Mobility management
+
+This clause provides the information flows for mobility management related IMT-2000 services and network capabilities.
+
+## 6.1 Authentication management
+
+### 6.1.1 UIM holder authorization
+
+This is a feature by which the removable user of the UIM is authorized. This feature only applies when the UIM is used for user association with the IMT-2000 mobile terminals. This is distinct from the "lockout" feature that may be provided by some MT vendors. See Figure 6.1.1-1.
+
+
+
+Sequence diagram showing UIM holder authorization between UIM (UIMF) and MT (MCF). The sequence starts with 'UIM inserted into MT' at time 0. At time 1, MT sends 'Select req.ind.' to UIM. At time 2, UIM sends 'Select resp.conf.' to MT. A dashed box between time 2 and 3 contains 'PIN request' from MT and 'PIN' from UIM. At time 3, MT sends 'Verify PIN req.ind.' to UIM. At time 4, UIM sends 'Verify PIN resp.conf.' to MT. The diagram is labeled T11105310-00.
+
+Figure 6.1.1-1/Q.1721 – UIM holder authorization
+
+0. **UIM inserted into MT:** the MT with the UIM inserted is powered-up.
+
+| | |
+|------|-----------------------------------------------|
+| FEA0 | – Initiate UIM holder verification procedure. |
+|------|-----------------------------------------------|
+
+1. **Select req.ind.:** is used to select the appropriate file(s) in a UIMF.
+
+| Select (Response: Success or Failure) | req.ind. |
+|---------------------------------------|----------|
+| File ID | M |
+
+| | |
+|------|-------------------------------------------|
+| FEA1 | – Select appropriate file(s) in the UIMF. |
+|------|-------------------------------------------|
+
+2. **Select resp.conf.:** is the response to the request.
+
+| Select | resp.conf. |
+|------------|------------|
+| File ID | M (Note) |
+| PIN Format | M |
+
+| | |
+|-----------------------------------------------------------------------|-------------------------------------|
+| FEA2 | – Interact with user to obtain PIN. |
+| NOTE – Either confirming system or requesting alternate if different. | |
+
+3. **Verify PIN req.ind.:** is used to verify PIN.
+
+| Verify PIN (Response: Success or Failure) | req.ind. |
+|--------------------------------------------------|-----------------|
+| PIN | M |
+
+| | |
+|------|----------------------------------------------------------------|
+| FEA3 | – Compare the user entered PIN with the PIN stored in the UIM. |
+|------|----------------------------------------------------------------|
+
+4. **Verify PIN resp.conf.:** is the response to the request.
+
+| Verify PIN | resp.conf. |
+|-------------------|-------------------|
+| Result | M |
+
+| | |
+|------|---------------------------------------------------------------------------------------------------|
+| FEA4 | – If a successful response is returned then the UIM user is valid and the terminal is authorized. |
+|------|---------------------------------------------------------------------------------------------------|
+
+### 6.1.2 User authentication
+
+The international mobile user identity (IMUI) authentication process is the verification by the core network that the IMT-2000 MT/UIM identity (IMUI or TMUI) is the one claimed. The authentication is composed of a challenge/response protocol showing knowledge of a secret key, called the Authentication Key (A-key), which is shared between and available only to the IMT-2000 MT/UIM and the Authentication Centre (AC) in the user's home network. The purpose of this authentication security procedure is to protect the network against unauthorized use.
+
+The network may trigger the authentication IMT-2000 process when:
+
+- the subscriber registers in a serving system (including location updates, attached/detached directives); or
+- the subscriber originates a call; or
+- the subscriber is responding to a page; or
+- the subscriber is responding to an SMS page; or
+- based on an operator's policies, including management of supplementary services, testing, periodic challenging of a user authentication, Shared Secret Data updates, etc.
+
+If an MT authentication procedure fails then the access to the IMT-2000 network shall be denied, except in case of emergency calls. It should be noted that a service provider may optionally allow this MT access to the network in case the authentication cannot be performed by the serving system and the home LMFh/AMF cannot be reached due to a network overload or failure.
+
+Three different authentication procedures are defined for an IMT-2000 network: two "Unique challenge/response mechanisms (UC)" and the "Global challenge mechanism (GC)" as described below. In the case of inter-system operation between different IMT-2000 family members, the visited system initiates the authentication mechanism according to its capabilities. This implies that a home system shall support the authentication request from the visited system in order to support roaming across IMT-2000 family members.
+
+Two additional security-related procedures are performed after the successful completion of user authentication procedures. The first is the procedure to "start ciphering" and the second is the "TMUI assignment" procedure.
+
+#### 6.1.2.1 Authentication Key
+
+The subscriber's authentication key (A-key) shall be known and stored only in the MT and in the home Authentication Centre (AC). The A-key shall never be transmitted over the air or over the network, and its integrity is essential for an effective authentication process.
+
+#### 6.1.2.2 Unique challenge/response user authentication mechanism based on Triplets Authentication Vectors
+
+The Unique challenge/response user authentication mechanism consists of the following exchange between the visited network and the UIM.
+
+- The visited network transmits a non-predictable random number RAND to the UIM.
+- The UIM computes the signature based on the received RAND, using the user authentication algorithm and the user secret authentication key, and transmits the signature result (SRES) to the visited network.
+- The visited network checks the signature result.
+
+See Figure 6.1.2.2-1.
+
+
+
+The diagram illustrates the interaction between four entities: UIM, MT, RAN+CNv, and CNh. The RAN+CNv entity is further divided into SACF, LMF, and AMF components. The sequence of messages is as follows:
+
+- Initiate challenge:** A message from the LMF (part of RAN+CNv) to the SACF (part of RAN+CNv).
+- Authentication challenge req.ind.:** A message from the SACF to the MT.
+- Authentication calculation:** A process performed by the UIM upon receiving the challenge.
+- Authentication challenge resp.conf.:** A message from the UIM to the MT.
+- Security status report req.ind.:** A message from the MT to the LMF (part of RAN+CNv).
+
+Timeline markers 0 through 4 are shown on the left and right sides of the diagram. The text "T11105320-00" is located at the bottom right.
+
+Sequence diagram showing the unique challenge/response user authentication process between UIM, MT, RAN+CNv, and CNh. The diagram includes steps for initiating a challenge, sending an authentication challenge request, performing an authentication calculation, and sending a response and security status report.
+
+Figure 6.1.2.2-1/Q.1721 – Unique challenge/response user authentication
+
+0. **Initiate challenge request:** the SACF receives an Initiate challenge request. This happens when the LMFv finds that user authentication is needed.
+
+| | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|
+| FEA0 | – Initiate authentication challenge. |
+| NOTE – The optional Authentication key management procedure is executed to obtain authentication triplets if they are not available. Refer to the Authentication key management procedure for details. | |
+
+1. **Authentication challenge req.ind.:** is used to verify the identity of the user.
+
+| Authentication challenge (Response: Success or Failure) | req.ind. |
+|---------------------------------------------------------|----------|
+| Challenge | M |
+
+| | |
+|------|----------------------------------------|
+| FEA1 | – Initiate Authentication calculation. |
+|------|----------------------------------------|
+
+2. **Authentication:** procedure is performed.
+
+3. **Authentication challenge resp.conf.:** is sent by the MCF to the SACF to convey the result of the authentication calculation.
+
+| Authentication challenge | resp.conf. |
+|--------------------------|------------|
+| Challenge Response | M |
+
+| | |
+|------|----------------------------------------------------|
+| FEA3 | – Determine if a Security status report is needed. |
+|------|----------------------------------------------------|
+
+4. **Security status report req.ind.:** is used to send a security status report to the home network (optional).
+
+| Security status report (Response: None) | req.ind. |
+|-----------------------------------------|----------|
+| Result | M |
+| IMUI | O (Note) |
+
+| | |
+|---------------------------------------------|-----------------------------------|
+| FEA4 | – Analyse security status report. |
+| NOTE – IMUI must be included, if available. | |
+
+##### 6.1.2.2.1 Authentication key management
+
+The subscriber authentication key, A-key, is allocated, together with the IMUI, at subscription time.
+
+The A-key is stored on the network side in the Home Network (AMFh), in an Authentication Centre (AC.)
+
+An IMT-2000 network may contain one or more ACs. An AC can be physically integrated with other functions, e.g. with a home Location Register (LMFh.) A subscriber shall be associated with only one AC.
+
+When needed for each MT, the LMFv requests security related information from the AMFh corresponding to the MT. This includes an array of pairs of corresponding RAND and SRES. These pairs are obtained by applying the user authentication algorithm to each RAND and A-key. The pairs are stored in the LMFv as part of the security related information.
+
+For the unique challenge mechanism, authentication triplets may be generated in batches by the AMFh in the Authentication Centre and sent via the LMFh to the LMFv.
+
+See Figure 6.1.2.2-2.
+
+
+
+```
+
+sequenceDiagram
+ participant User
+ participant RAN+CNv as RAN+CNv (LMF)
+ participant CNh as CNh (LMF/AMF)
+ Note left of User: 0
+ User->>RAN+CNv: User auth. or service request
+ Note right of RAN+CNv: 1
+ RAN+CNv->>CNh: Auth. info retrieval req.ind.
+ Note right of CNh: 2
+ CNh-->>RAN+CNv: Auth. info retrieval resp.conf.
+ Note right of RAN+CNv: T11105330-00
+
+```
+
+Sequence diagram for Authentication key management. It shows three lifelines: RAN+CNv (LMF), CNh (LMF/AMF), and a User. The sequence starts at time 0 with a 'User auth. or service request' from the User to the LMF. At time 1, the LMF sends an 'Auth. info retrieval req.ind.' to the CNh. At time 2, the CNh sends an 'Auth. info retrieval resp.conf.' back to the LMF. The diagram is labeled T11105330-00.
+
+Figure 6.1.2.2-2/Q.1721 – Authentication key management
+
+0. **User authorization or service request:** the subscriber identity is received, the LMFv checks whether a user authentication is necessary.
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | – If there is not enough authentication information in the LMFv to perform the authentication, an authentication information retrieval request is sent to the LMFh. |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **Authentication information retrieval req.ind.:** is used to request security information from the LMFh for user authentication.
+
+| Authentication information retrieval (Response: Success or Failure) | req.ind. |
+|---------------------------------------------------------------------|----------|
+| IMUI | M |
+
+| | |
+|------|-------------------------------------------------------------------------------------------------------|
+| FEA1 | – Retrieve security information.
– Retrieve challenge and response information for authentication. |
+|------|-------------------------------------------------------------------------------------------------------|
+
+2. **Authentication information retrieval resp.conf.:** contains the result of Authentication information retrieval req.ind.
+
+| Authentication information | resp.conf. |
+|----------------------------|------------|
+| Challenge(s) | M |
+| Challenge Response(s) | M |
+| Result | M |
+| Ciphering Key | O (Note) |
+
+| | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|
+| FEA2 | – Store authentication information. |
+| NOTE – For the triplet-based authentication mechanism, the Ciphering key must be available for some network accesses, e.g. location updates, paging responses, call initiation, etc. | |
+
+##### 6.1.2.2.2 Transfer of unused authentication triplets during location update
+
+When a user moves into another LMFv, unused triplets from the previous LMFv may be transferred to the new LMFv. This capability is used only when the authentication is done using TMUI (see Figure 6.2.2).
+
+##### 6.1.2.2.3 Authentication calculation
+
+This procedure is initiated by the MT towards the UIM requesting execution of the authentication calculation algorithm for the purpose of authenticating a user signature.
+
+NOTE – The UIMF holds the authentication key which is used to calculate authentication result. From the security point of view, the authentication key must not be retrieved from outside this functional entity. Therefore, a procedure to request the UIMF to execute an authentication calculation is necessary. This procedure is a common procedure for Unique challenge/response and Global challenge user authentication mechanisms.
+
+See Figure 6.1.2.2-3.
+
+
+
+Sequence diagram showing authentication calculation between UIMF and MCF. The diagram has two vertical lifelines: UIM (top) with UIMF (bottom) and MT (top) with MCF (bottom). The sequence of messages is: 0. Authentication request (from MT to MCF), 1. Authentication req.ind. (from MCF to UIMF), 2. Authentication resp.conf. (from UIMF to MCF). Horizontal dashed lines mark the sequence points 0, 1, and 2. A small note 'T11105340-00' is at the bottom right.
+
+**Figure 6.1.2.2-3/Q.1721 – Authentication calculation**
+
+0. **Authentication request:** the MCF receives an Authentication request.
+
+| | |
+|------|----------------------------------------|
+| FEA0 | – Initiate authentication calculation. |
+|------|----------------------------------------|
+
+1. **Authentication req.ind.:** is used to request the authentication calculation be carried out using the random number and authentication key.
+
+| Authentication (Response: Success or Failure) | req.ind. |
+|-----------------------------------------------|----------|
+| RAND | M |
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | – The UIMF calculates the authentication signature using the random number supplied by the MCF and the user authentication key stored in the UIMF. |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------|
+
+2. **Authentication resp.conf.:** is used to return the authentication calculation result.
+
+| Authentication | resp.conf. |
+|------------------|------------|
+| Signature result | M |
+| Ciphering key(s) | M |
+
+| | |
+|------|------------------------------------------------|
+| FEA2 | – Receive authentication calculation response. |
+|------|------------------------------------------------|
+
+#### 6.1.2.3 Global challenge
+
+A global challenge is the radio interfaces message (RAND) that is broadcast on a common system-wide information channel. Its generation and update frequency are under the control of the network operator, and should be in accordance with good authentication practices.
+
+When attempting a network access or a response to an SMS page, the mobile station has to include its authentication signature. The calculated authentication signature is based on secrets that were distributed during the subscription process. The global challenge response information elements include, but are not limited to, a subscription identifier, a confirmation of the received global challenge (RANDC), an authentication response (AUTH), a value for the parameter CHCNT. The information elements that comprise the response to the network challenge are generally embedded in network access request messages, such as registrations, call originations, call terminations or SMS page responses. Thus, the global challenge mechanism is not utilized as a stand-alone mechanism, but accompanies other network access protocols in order to minimize message traffic on air interface channels. The global challenge procedure also triggers the calculation of the ciphering keys that are then used for encrypting user traffic. See Figure 6.1.2.3-1.
+
+
+
+Sequence diagram for Global challenge user authentication. Lifelines: UIM (UIMF), MT (MCF), RAN+CNv (SACF, LMF/AMF), CNh (LMF, AMF). The sequence starts at 0 with a 'Broadcast req.' from UIMF to MCF. At 1, 'Authentication calculation' occurs in UIMF. At 2, 'Auth\_R0 req.ind.' is sent from MCF to SACF. At 3, 'Auth\_R2 req.ind.' is sent from LMF/AMF to LMF. At 4, 'Auth\_R2 resp.conf.' is sent from LMF to LMF/AMF. At 5, 'Auth\_R0 resp.conf.' is sent from SACF to MCF. The diagram is labeled T11105350-00.
+
+**Figure 6.1.2.3-1/Q.1721 – Global challenge user authentication**
+
+0. **Broadcast request:** during a system access attempt by the MT, the "global challenge" is read from the system information broadcast channel.
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | - – Broadcast "global challenge" is obtained by the mobile station from a common signalling channel, then applied to the authentication algorithm in the UIMF, along with secret user information, to calculate the UIMF's authentication signature (AUTH_R).
- – Initiate authentication calculation.
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **Authentication calculation:** is performed.
+2. **Auth\_R0 req.ind.:** is used as a component of a registration or a service request procedure.
+
+| Auth_R0 | req.ind. |
+|------------------------------|----------|
+| TMUI | M |
+| Confirmation of RAND (RANDC) | M |
+| AUTH_R | M |
+| CHCNT | M |
+
+| | |
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA2 | - – Verify that Confirmation of RAND (i.e. RANDC) is consistent with global RAND received over the system information channel.
- – Get user SSD from the serving system LMFv.
- – If SSD is not available in visited network forward the user authentication response to LMFh, including the full global RAND instead of RANDC.
- – Perform user authentication procedure.
- – Calculate applicable ciphering keys.
|
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+NOTE – The LMFv supports the global challenge mechanism by participating in the generation and distribution of the global RAND that is broadcast by the serving network on a system-wide information channel. Updates of global RAND are controlled by the serving system.
+
+3. **Auth\_R2 req.ind.:** is used to pass the authentication request to the home network.
+
+| Auth_R2 (Response: Success or Failure) | req.ind. |
+|-----------------------------------------------|-----------------|
+| IMUI | M |
+| RANDG | M |
+| AUTH_R | M |
+| CHCNT | M |
+
+| | |
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA3 | - – Calculate applicable ciphering key(s).
- – Perform user authentication procedure.
- – Forward confirmation of user validity, along with applicable ciphering key(s), and, under some circumstances, SSD, to LMFv.
|
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+4. **Auth\_R2 resp.conf.:** is the response providing the security information requested.
+
+| Auth_R2 | resp.conf. |
+|------------------|-------------------|
+| Result | M |
+| SSD | O (Note 1) |
+| Ciphering Key(s) | O (Note 2) |
+
+| | |
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA4 | - – Forward confirmation of user validity, along with applicable ciphering key(s), and, under some circumstances, SSD, to MCF.
|
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+NOTE 1 – If SSD sharing is turned on by the LMFh/AMF, the SSD parameter may be included in this message.
+
+NOTE 2 – Returned if available.
+
+5. **Auth\_R0 resp.conf.:** conveys the response to Auth\_R0 req.ind. to the MCF.
+
+| Auth_R0 | resp.conf. |
+|----------------|-------------------|
+| Result | M |
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA5 | - – Receive a status confirmation from the network as a component of system access attempt.
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------|
+
+#### 6.1.2.4 SSD management
+
+##### 6.1.2.4.1 Update of user's shared secret data (SSD update)
+
+In order to minimize network traffic between the serving system and the home AMF, while providing additional protection to the A-key, a secondary authentication key, called Shared Secret Data (SSD), is derived from the subscriber's A-key. The SSD update procedure, by which the MT's SSD is shared with a serving system, may be executed any time at the discretion of the "home" service provider. The SSD update process shall be initiated only after a successful MT authentication. See Figure 6.1.2.4.1-1.
+
+
+
+```
+
+sequenceDiagram
+ participant UIMF
+ participant MCF
+ participant SACF
+ participant LMF
+ participant CNh
+
+ Note right of CNh: Decide to do SSD update
+ CNh->>LMF: SSD update req.ind.
+ LMF->>SACF: SSD update req.ind.
+ SACF->>MCF: SSD update req.ind.
+ MCF->>UIMF: Network verify req.ind.
+ UIMF->>MCF: Network verify req.ind.
+ MCF->>SACF: Network verify req.ind.
+ SACF->>LMF: Network verify req.ind.
+ LMF->>CNh: Network verify resp.conf.
+ CNh->>LMF: Network verify resp.conf.
+ LMF->>SACF: Network verify resp.conf.
+ SACF->>MCF: Network verify resp.conf.
+ MCF->>UIMF: Network verify resp.conf.
+ UIMF->>MCF: SSD update resp.conf.
+ MCF->>SACF: SSD update resp.conf.
+ SACF->>LMF: SSD update resp.conf.
+ LMF->>CNh: Unique challenge req.ind.
+ CNh->>LMF: Unique challenge req.ind.
+ LMF->>SACF: Unique challenge req.ind.
+ SACF->>MCF: Unique challenge req.ind.
+ MCF->>UIMF: Unique challenge resp.conf.
+ UIMF->>MCF: Unique challenge resp.conf.
+ MCF->>SACF: Unique challenge resp.conf.
+ SACF->>LMF: Unique challenge resp.conf.
+ LMF->>CNh: Unique challenge resp.conf.
+
+```
+
+Sequence diagram for SSD update (SSD is not shared) involving UIMF, MCF, SACF, LMF, and CNh entities. The diagram shows 18 steps of message exchanges between these components.
+
+T11105360-00
+
+Figure 6.1.2.4.1-1/Q.1721 – SSD update (SSD is not shared)
+
+0. **Decide to do SSD update:** initiates the execution of the SSD update procedure for a selected mobile user in the visited network.
+
+| | |
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | - – Generate a random number RANDSSD.
- – Calculate new SSD for mobile user.
- – Generate RANDU and calculate AUTH_U, using new SSD.
- – Send SSD update req.ind. to LMFv requesting that the selected mobile user perform an immediate update of his/her SSD.
|
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **SSD update req.ind.:** directs the UIMF to update its value of SSD. It is sent from the home system towards the visited system where the mobile user is located. For this procedure to be executed, it is required that the UIM (removable or permanent) be present in the mobile terminal.
+
+| SSD update (Response: Success or Failure) | req.ind. |
+|-------------------------------------------|----------|
+| IMUI | M |
+| RANDSSD | M |
+| RANDU | M |
+| AUTH_U | M |
+| Ciphering Key(s) | O (Note) |
+
+| | |
+|----------------------------------------------|----------------------------------------------------------------------------------------------------|
+| FEA1 | – Receive SSD update req.ind. from LMFh, perform IMUI/TMUI translation, and forward it to the MCF. |
+| NOTE – Ciphering Keys are sent if available. | |
+
+2. **SSD update req.ind.:** directs the mobile user to update its value of SSD. It is sent from the home system towards the visited system where the mobile user is located. For this procedure to be executed, it is required that the UIM (removable or permanent) be present in the mobile terminal in order to interact with the network.
+
+| SSD update (Response: Success or Failure) | req.ind. |
+|-------------------------------------------|----------|
+| IMUI | M |
+| RANDSSD | M |
+
+| | |
+|------|---------------------------------------------------|
+| FEA2 | – Relay SSD update req.ind. from visited network. |
+|------|---------------------------------------------------|
+
+3. **SSD update req.ind.:** directs the mobile user to update its value of SSD. It is relayed by the visited system.
+
+| SSD update (Response: Success or Failure) | req.ind. |
+|-------------------------------------------|----------|
+| IMUI | M |
+| RANDSSD | M |
+
+| | |
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA3 | - – Calculate a new (tentative) SSD.
- – Generate a random number RANDBS for use in the Network verify IF.
- – Calculate the expected AUTHBS using the new (tentative) SSD.
- – Send the Network verify req.ind. to the MCF (to authenticate and verify the network).
|
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+4. **Network verify req.ind.:** causes the network to authenticate and verify itself to the mobile. It comes from the UIM.
+
+| Network verify (Response: Success or Failure) | req.ind. |
+|-----------------------------------------------|----------|
+| TMUI | M |
+| RANDBS | M |
+
+| | |
+|------|--------------------------------------------|
+| FEA4 | – Relay Network verify req.ind. from UIMF. |
+|------|--------------------------------------------|
+
+5. **Network verify req.ind.:** is relayed to the visited system by the MCF.
+
+| Network verify (Response: Success or Failure) | req.ind. |
+|-----------------------------------------------|----------|
+| TMUI | M |
+| RANDBS | M |
+
+| | |
+|------|----------------------------------|
+| FEA5 | – Perform IMUI/TMUI translation. |
+|------|----------------------------------|
+
+6. **Network verify req.ind.:** is relayed by the visited system to the home system for purposes of authenticating the network.
+
+| Network verify (Response: Success or Failure) | req.ind. |
+|-----------------------------------------------|----------|
+| IMUI | M |
+| RANDBS | M |
+
+| | |
+|------|----------------------------------|
+| FEA6 | – Generate AUTHBS using new SSD. |
+|------|----------------------------------|
+
+7. **Network verify resp.conf.:** is the response from the home network to the Network verify req.ind. information flow.
+
+| Network verify | resp.conf. |
+|----------------|------------|
+| AUTHBS | M |
+
+| | |
+|------|----------------------------------|
+| FEA7 | – Perform IMUI/TMUI translation. |
+|------|----------------------------------|
+
+8. **Network verify resp.conf.:** is relayed by the visited system.
+
+| Network verify | resp.conf. |
+|----------------|------------|
+| AUTHBS | M |
+
+| | |
+|------|-----------------------------------|
+| FEA8 | – Relay Network verify resp.conf. |
+|------|-----------------------------------|
+
+9. **Network verify resp.conf.:** is relayed by the mobile system to the UIM.
+
+| Network verify | resp.conf. |
+|-----------------------|-------------------|
+| AUTHBS | M |
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA9 | - – Compare received AUTHBS to expected AUTHBS.
- – Prepare a pass/fail confirmation.
- – Update memory with new SSD if procedure has been successful.
|
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+10. **SSD update resp.conf.:** is the response from the UIM to SSD update req.ind.
+
+| SSD update | resp.conf. |
+|-------------------|-------------------|
+| Result | M |
+
+| | |
+|-------|-------------------------------|
+| FEA10 | – Relay SSD update resp.conf. |
+|-------|-------------------------------|
+
+11. **SSD update resp.conf.:** is the response to the SSD update req.ind. information flow.
+
+| SSD update | resp.conf. |
+|-------------------|-------------------|
+| Result | M |
+
+| | |
+|-------|------------------------|
+| FEA11 | – Process confirmation |
+|-------|------------------------|
+
+12. **SSD update resp.conf.:** is the response to the SSD update req.ind. information flow.
+
+| SSD update | resp.conf. |
+|-------------------|-------------------|
+| Result | M |
+
+| | |
+|-------|----------------------------------------------------------------------------------------|
+| FEA12 | – Prepare to send Unique challenge req.ind. to the mobile user in the visited network. |
+|-------|----------------------------------------------------------------------------------------|
+
+13. **Unique challenge req.ind.:** enables the network to determine whether (or not) the selected mobile has been able to successfully update its SSD.
+
+| Unique challenge (Response: Success or Failure) | req.ind. |
+|--------------------------------------------------------|-----------------|
+| IMUI | M |
+| RANDU | M |
+| AUTH_U | M |
+
+| | |
+|-------|----------------------------------|
+| FEA13 | – Perform IMUI/TMUI translation. |
+|-------|----------------------------------|
+
+14. **Unique challenge req.ind.:** is forwarded from UIMF to MT.
+
+| Unique challenge (Response: Success or Failure) | req.ind. |
+|--------------------------------------------------------|-----------------|
+| TMUI | M |
+| RANDU | M |
+| AUTH_U | M |
+
+| | |
+|-------|-----------------------------------|
+| FEA14 | – Relay Unique challenge req.ind. |
+|-------|-----------------------------------|
+
+15. **Unique challenge req.ind.:** is forwarded to the UIMF.
+
+| Unique challenge (Response: Success or Failure) | req.ind. |
+|--------------------------------------------------------|-----------------|
+| TMUI | M |
+| RANDU | M |
+| AUTH_U | M |
+
+| | |
+|-------|-----------------------------------------------------------|
+| FEA15 | – Calculate authentication response AUTH_U using new SSD. |
+|-------|-----------------------------------------------------------|
+
+16. **Unique challenge resp.conf.:** is the response to **Unique challenge req.ind.** and contains the authentication response.
+
+| Unique challenge | resp.conf. |
+|-------------------------|-------------------|
+| AUTH_U | M |
+
+| | |
+|-------|-------------------------------------|
+| FEA16 | – Relay Unique challenge resp.conf. |
+|-------|-------------------------------------|
+
+17. **Unique challenge resp.conf.:** is forwarded to RAN+CNv.
+
+| Unique challenge | resp.conf. |
+|-------------------------|-------------------|
+| AUTH_U | M |
+
+| | |
+|-------|----------------------------------|
+| FEA17 | – Perform IMUI/TMUI translation. |
+|-------|----------------------------------|
+
+18. **Unique challenge resp.conf.:** is forwarded to the home network.
+
+| Unique challenge | resp.conf. |
+|-------------------------|-------------------|
+| AUTH_U | M |
+
+| | |
+|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA18 | - – Update mobile user's data based on status information received.
- – If status is successful, store the new SSD value for use in future executions of the authentication procedure and allow mobile user to continue with call origination and call termination. Optionally, the SSD can be shared with an LMFv, if permitted by service provider agreements.
|
+|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+NOTE – The LMFh updates the mobile user's data based on status information received. If authentication did not fail, then allow the mobile user to continue with call origination and call termination. In addition, transfer SSD to LMFv if permitted by service provider agreements. If the status is unsuccessful, maintain the current SSD and reattempt to update the SSD of the mobile user in a subsequent transaction.
+
+##### 6.1.2.4.2 Invoke security sharing
+
+Invoke security sharing is used to invoke the sharing of security information associated with a particular IMT-2000 user.
+
+Scenario:
+
+- a) The home system of a subscriber determines that security sharing should be enabled and extends (shares) security information to the visited system.
+- b) The visited system enables security sharing and responds to the home system indicating success or failure.
+
+See Figure 6.1.2.4.2-1.
+
+
+
+Sequence diagram showing the interaction between RAN+CNv (LMF) and CNh (LMF) for Invoke security sharing. The sequence starts at point 0 with 'Decide to enable SSD' in CNh. At point 1, 'Invoke SSD req.ind.' is sent from CNh to RAN+CNv. At point 2, 'Invoke SSD resp.conf.' is sent from RAN+CNv to CNh. The diagram is labeled T11105370-00.
+
+Figure 6.1.2.4.2-1/Q.1721 – Invoke security sharing information flow diagram
+
+0. **Decide to enable SSD:** decide to enable sharing of secret data between home and visited system.
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | – LMFh determines that security sharing should be enabled and sends an Invoke_security_sharing request to the LMFv with the security information to be shared. |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **Invoke\_security\_sharing req.ind.:** is used to invoke the sharing of the security information at the visited system.
+
+| Invoke_security_sharing (Response: Success or Failure) | req.ind. |
+|--------------------------------------------------------|----------|
+| IMUI | M |
+| SSD | M |
+
+| | |
+|------|------------------------------------------------------------------------------------------|
+| FEA1 | – LMFv receives the request, enables security sharing, and returns a success or failure. |
+|------|------------------------------------------------------------------------------------------|
+
+2. **Invoke\_security\_sharing resp.conf.:** is the response to the Invoke\_security\_sharing req.ind. information flow.
+
+| Invoke_security_sharing | resp.conf. |
+|-------------------------|------------|
+| Result | M |
+
+##### 6.1.2.4.3 Revoke security sharing
+
+Revoke security sharing is used to revoke the sharing of security information at the visited system.
+
+Scenario:
+
+- a) The home system of a subscriber determines that security sharing should be disabled and informs the visited system.
+- b) The visited system disables security sharing and responds to the home system, with the call history count if available, indicating success or failure.
+
+See Figure 6.1.2.4.3-1.
+
+
+
+Sequence diagram showing the information flow for revoking security sharing between RAN+CNv (LMF) and CNh (LMF). The sequence starts at 0 with 'Decide to revoke SSD' from CNh to RAN+CNv. At 1, 'Revoke SSD req.ind.' is sent from RAN+CNv to CNh. At 2, 'Revoke SSD resp.conf.' is sent from CNh to RAN+CNv. The diagram is labeled T11105380-00.
+
+Figure 6.1.2.4.3-1/Q.1721 – Revoke security sharing information flow diagram
+
+0. **Decide to revoke SSD:** decide to enable sharing of secret data between home and visited system.
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------|
+| FEA0 | – LMFh determines that security sharing should be disabled and sends a Revoke_security_sharing request to the LMFv. |
+|------|---------------------------------------------------------------------------------------------------------------------|
+
+1. **Revoke\_security\_sharing req.ind.:** is used to revoke the sharing of the security information at the visited system.
+
+| Revoke_security_sharing (Response: Success or Failure) | req.ind. |
+|--------------------------------------------------------|----------|
+| IMUI | M |
+
+| | |
+|------|------------------------------------------------------------------------------------------|
+| FEA1 | – LMFv receives the request, disables security sharing and returns a success or failure. |
+|------|------------------------------------------------------------------------------------------|
+
+2. **Revoke\_security\_sharing resp.conf.:** is the response to the Revoke\_security\_sharing req.ind. information flow.
+
+| Revoke_security_sharing | resp.conf. |
+|-----------------------------------------|------------|
+| Result | M |
+| CHCNT | O (Note) |
+| NOTE – CHCNT is returned, if available. | |
+
+#### 6.1.2.5 Start ciphering
+
+This procedure provides encryption of the data stream on the radio interface to prevent unauthorized access to the information. Ciphering is initiated in the MT (and LMFv) only after a successful authentication process. See Figure 6.1.2.5-1.
+
+
+
+Sequence diagram showing the start ciphering information flow between MT and RAN+CNv. The diagram has two vertical lifelines: MT (left) and RAN+CNv (right). Above the MT lifeline is the label 'MCF' and above the RAN+CNv lifeline is the label 'SACF'. There are two horizontal dashed lines representing sequence points 0 and 1. At sequence 0, an arrow labeled 'Start ciphering req.' points from MT to RAN+CNv. At sequence 1, an arrow labeled 'Start ciphering req.ind.' points from RAN+CNv to MT. The diagram is labeled 'T11105390-00' at the bottom right.
+
+Figure 6.1.2.5-1/Q.1721 – Start ciphering information flow diagram
+
+- 0. **Start ciphering request:** start ciphering request is received.
+- 1. **Start\_ciphering req.ind.:** is used to activate ciphering control over the radio interface.
+
+| Start ciphering (Response: None) | req.ind. |
+|----------------------------------|----------|
+| None | N/A |
+
+| | |
+|------|--------------------------------------------------------|
+| FEA1 | – Activate ciphering control over the radio interface. |
+|------|--------------------------------------------------------|
+
+#### 6.1.2.6 TMUI assignment
+
+A TMUI has local significance only in the location area in which the user is registered. Outside that area, it should be accompanied by an appropriate Location Area Identification (LAI) in order to avoid ambiguities. The association between the permanent and temporary user identities is kept by the LMFv in which the user is registered.
+
+The TMUI, when available, is normally used to identify the user on the radio access path, for instance in paging requests, location update requests, attach requests, service requests, connection re-establishment requests and detach requests.
+
+This procedure is used to assign and convey the TMUI to the UIM after the network has verified the identity of the user and should be performed after the initiation of ciphering. See Figure 6.1.2.6-1.
+
+
+
+Sequence diagram showing TMUI assignment information flow between UIM (UIMF), MT (MCF), and RAN+CNv (SACF). The sequence starts at 0 with TMUI assignment req. from SACF to MCF. At 1, TMUI assignment req.ind. is sent from MCF to UIMF. At 2, a TMUI update is performed within UIMF. At 3, TMUI assignment resp.conf. is sent from UIMF to SACF. Reference T11105400-00 is shown at the bottom right.
+
+Figure 6.1.2.6-1/Q.1721 – TMUI assignment information flow diagram
+
+0. **TMUI assignment request:** is received.
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | - – Retrieve TMUI and TMUI assignment source ID, and optionally TMUI expiration timer.
- – Send TMUI assignment req.ind.
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **TMUI\_assignment req.ind.:** is used to assign and convey the TMUI to the user after the network has verified the identify of the user.
+
+| TMUI_assignment (Response: Success or Failure) | req.ind. |
+|------------------------------------------------|----------|
+| TMUI | M |
+| TMUI assignment source ID | M |
+| TMUI expiration timer | O (Note) |
+
+| | |
+|----------------------------------------------------------------------------------------------------|------------------------------------------|
+| FEA1 | – Initiate TMUI update procedure module. |
+| NOTE – Include if other than a default expiration timer value as set by the network is to be used. | |
+
+2. **TMUI\_assignment resp.conf.:** indicates the TMUI update procedure was executed.
+
+| | |
+|------|---------------------------------------------------------------------------|
+| FEA2 | – Analyse the result of TMUI update and report it to the visited network. |
+|------|---------------------------------------------------------------------------|
+
+3. **TMUI\_assignment resp.conf.:** is the response to TMUI\_assignment req.ind.
+
+| TMUI_assignment | resp.conf. |
+|-----------------|------------|
+| Result | M |
+
+| | |
+|------|------------------------------------------------|
+| FEA3 | Note the response. No further action required. |
+|------|------------------------------------------------|
+
+#### 6.1.2.7 Call history count
+
+##### 6.1.2.7.1 Update call history count
+
+The Update call history count procedure is used to update the call history count (CHCNT) in the visited system, mobile terminal and UIM. See Figure 6.1.2.7.1-1.
+
+
+
+```
+
+sequenceDiagram
+ participant CNh as CNh (LMF)
+ participant RAN+CNv as RAN+CNv (LMF)
+ participant MT as MT (MCF)
+ participant UIM as UIM (UIMF)
+
+ Note right of CNh: 0 Decide to update CH count
+ CNh->>RAN+CNv: 1 Update CH count req.ind.
+ RAN+CNv->>MT: 2 Update CH count req.ind.
+ MT->>UIM: 3 Update CH count req.ind.
+ UIM->>MT: 4 Update CH count resp.conf.
+ MT->>RAN+CNv: 5 Update CH count resp.conf.
+ RAN+CNv->>CNh: 6 Update CH count resp.conf.
+
+```
+
+T11105410-00
+
+Sequence diagram showing the update call history count information flow between UIM, MT, RAN+CNv, and CNh. The sequence starts with a decision to update the CH count at the CNh LMF, followed by a request to the RAN+CNv LMF, then to the MT MCF, then to the UIM UIMF, and finally responses are sent back from UIM to MT, MT to RAN+CNv, and RAN+CNv to CNh.
+
+Figure 6.1.2.7.1-1/Q.1721 – Update call history count information flow diagram
+
+0. **Decide to update call history count:** the home system detects the need to update the call history count and sends a request to the visited system to update the call history count.
+
+| | |
+|------|-------------------------------------------------------------------------------------|
+| FEA0 | – Retrieve appropriate parameters and initiate Update call history count procedure. |
+|------|-------------------------------------------------------------------------------------|
+
+1. **Update\_CH\_count req.ind.:** is used to request the call history count to be updated in the visited system.
+
+| Update_CH_count (Response: Success or Failure) | req.ind. |
+|------------------------------------------------|----------|
+| IMUI | M |
+| Update_CH_count | M |
+
+| | |
+|------|---------------------------------------------------------|
+| FEA1 | – Update call history count data in the visited system. |
+|------|---------------------------------------------------------|
+
+2. **Update\_CH\_count req.ind.:** is sent to MCF.
+
+| Update_CH_count (Response: Success or Failure) | req.ind. |
+|------------------------------------------------|----------|
+| IMUI | M |
+| Update_CH_count | M |
+
+| | |
+|------|----------------------------------------------------------|
+| FEA2 | – Update call history count data in the mobile terminal. |
+|------|----------------------------------------------------------|
+
+3. **Update\_CH\_count req.ind.:** is sent to UIMF.
+
+| Update_CH_count (Response: Success or Failure) | req.ind. |
+|-------------------------------------------------------|-----------------|
+| IMUI | M |
+| Update_CH_count | M |
+
+| | |
+|------|----------------------------------------------|
+| FEA3 | – Update call history count data in the UIM. |
+|------|----------------------------------------------|
+
+4. **Update\_CH\_count resp.conf.:** is the response to the request from UIMF.
+
+| Update_CH_count | resp.conf. |
+|------------------------|-------------------|
+| CHCNT | M |
+| Result | M |
+
+| | |
+|------|------------------------|
+| FEA4 | – Relay result to MCF. |
+|------|------------------------|
+
+5. **Update\_CH\_count resp.conf.:** is the response to the request from MCF.
+
+| Update_CH_count | resp.conf. |
+|------------------------|-------------------|
+| CHCNT | M |
+| Result | M |
+
+| | |
+|------|-------------------------------------------|
+| FEA5 | – Relay result to SACF in visited system. |
+|------|-------------------------------------------|
+
+6. **Update\_CH\_count resp.conf.:** is the response to the request from visited system.
+
+| Update_CH_count | resp.conf. |
+|------------------------|-------------------|
+| CHCNT | O (Note) |
+| Result | M |
+
+| | |
+|---------------------------------------------|--------------------------------|
+| FEA6 | – Relay result to home system. |
+| NOTE – Send CHCNT to home system if needed. | |
+
+##### 6.1.2.7.2 Call history count request procedure
+
+When the CHCNT parameter is used, the "home" network needs to query the previously visited network to obtain the current value of CHCNT in order that the current serving network may use it. The current serving network may be the "home" network or another "visited" network. See Figure 6.1.2.7.2-1.
+
+
+
+Sequence diagram showing the call history count request information flow between RAN+CNv (LMF/AMF) and CNh (LMF/AMF). The sequence starts at 0 with 'Decide to request CH count' (internal to CNh). At 1, 'Request CH count req.ind.' is sent from CNh to RAN+CNv. At 2, 'Request CH count resp.conf.' is sent from RAN+CNv to CNh. The diagram is labeled T11105420-00.
+
+Figure 6.1.2.7.2-1/Q.1721 – Call history count request information flow diagram
+
+0. **Decide to request call history count:** the home system detects the need to query the previously visited network to obtain the current value of CHCNT in order that the current serving network may use it.
+
+| | |
+|------|--------------------------------------------------|
+| FEA0 | – Initiate Call history CHCNT request procedure. |
+|------|--------------------------------------------------|
+
+1. **Request\_CH\_count req.ind.:** is used to request the current value of CHCNT from previously visited network.
+
+| Request_CH_count (Response: Success or Failure) | req.ind. |
+|-------------------------------------------------|----------|
+| IMUI | M |
+
+| | |
+|------|---------------------------------------------------------------------------|
+| FEA1 | – Access the current value of CHCNT for the user and send to home system. |
+|------|---------------------------------------------------------------------------|
+
+2. **Request\_CH\_count resp.conf.:** is the response to the request.
+
+| Request_CH_count | resp.conf. |
+|------------------|------------|
+| CHCNT | M |
+
+| | |
+|------|-----------------------------------------------------------------------------------------|
+| FEA2 | – Receive CHCNT for the user from previously visited system and store it for later use. |
+|------|-----------------------------------------------------------------------------------------|
+
+#### 6.1.2.8 Unique Challenge Authentication – RANDU based
+
+The Home HLR/AC as well as the serving system can trigger this type of UC process (if the SSD is shared). A random number is selected by the serving system (RANDU) and an expected authentication response, based on the mobile's SSD, is produced by the authentication algorithm. Upon receiving the challenged (i.e. RANDU), the MT in turn is calculating its own authentication signature using its SSD and the same authentication algorithm. The authentication signature is returned to the serving system (or the AC) where it is checked against the expected one. If they match, the authentication is successful.
+
+The UC process can be optionally used to (re)authenticate an MT, to authenticate supplementary services or as part of the SSD update process. See Figure 6.1.2.8-1.
+
+
+
+```
+
+sequenceDiagram
+ participant UIM as UIM (UIMF)
+ participant MT as MT (MCF)
+ participant RAN+CNv as RAN+CNv (SACF, LMF)
+ participant CNh as CNh (LMF)
+
+ Note right of CNh: 0 Initiate challenge req.
+ CNh->>RAN+CNv: Initiate challenge req.
+ Note left of RAN+CNv: 1 Authentication challenge req.ind.
+ RAN+CNv->>MT: Authentication challenge req.ind.
+ Note left of UIM: 2 Authentication calculation
+ UIM->>UIM: Authentication calculation
+ Note left of UIM: 3 Authentication challenge resp.conf.
+ UIM->>RAN+CNv: Authentication challenge resp.conf.
+ Note left of RAN+CNv: 4 Security status report
+ RAN+CNv->>CNh: Security status report
+
+```
+
+T11105430-00
+
+Sequence diagram for Unique challenge/response user authentication (SSD shared). The diagram shows four lifelines: UIM (UIMF), MT (MCF), RAN+CNv (SACF, LMF), and CNh (LMF). The sequence of messages is: 0. Initiate challenge req. (from CNh LMF to RAN+CNv LMF); 1. Authentication challenge req.ind. (from RAN+CNv SACF to MT MCF); 2. Authentication calculation (internal to UIM UIMF); 3. Authentication challenge resp.conf. (from UIM UIMF to RAN+CNv SACF); 4. Security status report (from RAN+CNv LMF to CNh LMF).
+
+**Figure 6.1.2.8-1/Q.1721 – Unique challenge/response user authentication (SSD shared)**
+
+0. **Initiate challenge request:** the SACF receives an Initiate challenge request after the LMFv is triggered to initiate a UC authentication process.
+
+| | |
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | - – Initiate authentication challenge.
- – Generate the challenge – RANDU and send it to the user.
|
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **Authentication challenge req.ind.:** is sent to verify the identity of the user.
+
+| Authentication challenge (Response: Success or Failure) | req.ind. |
+|---------------------------------------------------------|----------|
+| RANDU | M |
+
+| | |
+|------|----------------------------------------------------------|
+| FEA1 | – Calculate the expected authentication signature AUTHU. |
+|------|----------------------------------------------------------|
+
+2. **Authentication calculation:** is executed.
+
+3. **Authentication challenge resp.conf.:** sends the authentication signature based on RANDU.
+
+| | |
+|------|-------------------------------------------------------------------------------------------------------------------|
+| FEA2 | - – Receive AUTHU.
- – Verify the received AUTHU validity.
|
+|------|-------------------------------------------------------------------------------------------------------------------|
+
+4. **Security status report req.ind.:** is used to send a security status report to the home network (optional).
+
+| Security status report (Response: None) | req.ind. |
+|-----------------------------------------|----------|
+| Result | M |
+| IMUI | O (Note) |
+
+| | |
+|---------------------------------------------|-----------------------------------|
+| FEA5 | – Analyse security status report. |
+| NOTE – IMUI must be included, if available. | |
+
+## 6.2 Location management
+
+### 6.2.1 Subscriber data management
+
+The subscriber data management procedures are used by the LMFh to change or remove certain subscriber data from the subscriber profile in the LMFv if the subscription of one or more basic or supplementary services have been changed or withdrawn. Hence, this can be seen as "stand alone" modification of the subscriber profile in the visited system, i.e. not in conjunction with a location update.
+
+NOTE – The terms "user" and "subscriber" used in this subclause are interchangeable.
+
+Throughout this subclause, it is assumed that the following information items are stored in the subscriber home network/supporting network and are the subject of the subscriber information and profile management activities:
+
+- IMT-2000 mobile directory number (IMDN), e.g. a dialable number;
+- IMT-2000 mobile user ID (IMUI);
+- international mobile equipment ID (IMEI);
+- user/terminal location information;
+- basic service data (e.g. subscribed bearer services);
+- teleservices (e.g. broadcast and/or group call subscription data);
+- security data;
+- supplementary services data;
+- operator determined features/services (e.g. call barring data);
+- subscriber determined features/services (e.g. call screening data);
+- roaming restriction data;
+- regional subscription data; and
+- VHE subscription data.
+
+#### 6.2.1.1 Subscriber profile modification
+
+##### 6.2.1.1.1 Subscriber profile modification, Case 1: Subscriber profile copy
+
+Subscriber profile data have been modified and the modifications have to be reflected in the LMFv. In this case, the "Subscriber profile copy" procedure can be used. This procedure overwrites all existing values of the parameters by their corresponding new values. See Figure 6.2.1.1-1.
+
+
+
+```
+sequenceDiagram
+ participant RAN+CNv as RAN+CNv (LMF)
+ participant CNh as CNh (LMF)
+ Note right of CNh: User profile modified
+ CNh->>RAN+CNv: Subscriber profile copy req.ind.
+ RAN+CNv-->>CNh: Subscriber profile copy resp.conf.
+```
+
+Sequence diagram for Subscriber profile modification, Case 1: Subscriber profile copy. The diagram shows two lifelines: RAN+CNv (LMF) and CNh (LMF). The sequence of messages is: 1. An external arrow labeled 'User profile modified' points to the CNh (LMF) lifeline at time 0. 2. A dashed arrow labeled 'Subscriber profile copy req.ind.' points from the CNh (LMF) lifeline to the RAN+CNv (LMF) lifeline at time 1. 3. A solid arrow labeled 'Subscriber profile copy resp.conf.' points from the RAN+CNv (LMF) lifeline to the CNh (LMF) lifeline at time 2. The diagram is labeled T11105440-00 at the bottom right.
+
+Figure 6.2.1.1-1/Q.1721 – Subscriber profile modification, Case 1: Subscriber profile copy
+
+0. **User profile modified:** initiates the Subscriber profile copy to the LMFv.
+
+| | |
+|------|---------------------------------------------------------------------------------------------|
+| FEA0 | – Determine the need to update the user profile residing in the LMF of the visited network. |
+|------|---------------------------------------------------------------------------------------------|
+
+1. **Subscriber profile copy req.ind.:** is sent from the LMFh to LMFv in the serving network indicating requirements to update one or more elements of the subscriber profile.
+
+| Subscriber profile copy (Response: Success) | req.ind. |
+|---------------------------------------------|----------|
+| IMUI | M |
+| User profile | M |
+
+| | |
+|------|----------------------------------------------------------------------------|
+| FEA1 | – Identifies the IMT-2000 user in question.
– Updates the user profile. |
+|------|----------------------------------------------------------------------------|
+
+2. **Subscriber profile copy resp.conf.:** is sent from the LMFv in the serving network to the LMFh in the user's home network. It is to inform the LMFh of the profile update results.
+
+| Subscriber profile copy | resp.conf. |
+|-------------------------|------------|
+| Result | M |
+
+| | |
+|------|-------------------------------------------------------------------|
+| FEA2 | – Note the completion of the Subscriber profile update procedure. |
+|------|-------------------------------------------------------------------|
+
+##### 6.2.1.1.2 Subscriber profile modification, Case 2: Delete user data
+
+The subscription of one or more basic or supplementary services has been withdrawn. This procedure is used to indicate the specific services that have been withdrawn and the specific data to be deleted. See Figure 6.2.1.1-2.
+
+
+
+```
+
+sequenceDiagram
+ participant RAN+CNv
+ participant CNh
+ Note left of RAN+CNv: LMF
+ Note right of CNh: LMF
+ Note over RAN+CNv, CNh: Service subscription withdrawn
+ RAN+CNv->>CNh: Delete user data req.ind.
+ CNh-->>RAN+CNv: Delete user data resp.conf.
+ Note right of CNh: T111105450-00
+
+```
+
+Sequence diagram for 'Subscriber profile modification, Case 2: Delete user data'. It shows interactions between RAN+CNv, CNh, and their respective LMFs. The sequence starts with 'Service subscription withdrawn' (0), followed by 'Delete user data req.ind.' (1) from CNh LMF to RAN+CNv LMF, and 'Delete user data resp.conf.' (2) from RAN+CNv LMF to CNh LMF. A small note 'T111105450-00' is at the bottom right.
+
+Figure 6.2.1.1-2/Q.1721 – Subscriber profile modification, Case 2: Delete user data
+
+0. **Service subscription withdrawn:** is a request to delete a specific service subscription from the list of subscribed services.
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | – Determine the need to delete one or more basic or supplementary services from the user profile residing in the LMF of the visited network. |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **Delete user data req.ind.:** is used to delete specific user data.
+
+| Delete user data (Response: Success) | req.ind. |
+|---------------------------------------------|-----------------|
+| IMUI | M |
+| Deleted user data | M |
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | - – Identify the concerned IMT-2000 user.
- – Delete the user data indicated in the Delete user data req.ind.
|
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+2. **Delete user data resp.conf.:** confirms the request.
+
+| Delete user data | resp.conf. |
+|-------------------------|-------------------|
+| Result | M |
+
+| | |
+|------|----------------------------------------------------------|
+| FEA2 | – Note the completion of the Delete user data procedure. |
+|------|----------------------------------------------------------|
+
+##### 6.2.1.1.3 Subscriber profile modification, Case 3: Subscriber profile removal
+
+The authentication algorithm or authentication key of the subscriber has been changed or the modification of the subscriber profile affects the subscriber's permission to roam in its current area. In this case, the subscriber profile should be removed entirely from the visited network and, therefore, the "Subscriber profile removal" procedure is used. See Figure 6.2.1.1-3.
+
+
+
+```
+
+sequenceDiagram
+ participant RAN+CNv as RAN+CNv (LMFv)
+ participant CNh as CNh (LMFh)
+ Note right of CNh: Algorithm/Key/Roaming changed
+ CNh->>RAN+CNv: User profile remove req.ind.
+ RAN+CNv->>CNh: User profile remove resp.conf.
+
+```
+
+Sequence diagram for Subscriber profile removal. It shows interactions between RAN+CNv (LMFv) and CNh (LMFh). Step 0: Algorithm/Key/Roaming changed (indicated by a dashed line from CNh to RAN+CNv). Step 1: User profile remove req.ind. (solid arrow from CNh to RAN+CNv). Step 2: User profile remove resp.conf. (solid arrow from RAN+CNv to CNh).
+
+Figure 6.2.1.1-3/Q.1721 – Subscriber profile modification, Case 3: Subscriber profile removal
+
+0. **Algorithm/Key/Roaming changed:** initiates removal of the subscriber profile from the LMFv.
+
+| | |
+|------|----------------------------------|
+| FEA0 | – Initiate User profile removal. |
+|------|----------------------------------|
+
+1. **User profile remove req.ind.:** is used to request removal of the user profile.
+
+| User profile remove (Response: Success) | req.ind. |
+|------------------------------------------------|-----------------|
+| IMUI | M |
+
+| | |
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | - – Identify the concerned IMT-2000 user.
- – Remove the user profile of the identified user.
|
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+2. **User profile remove resp.conf.:** is returned to confirm the actions taken by the LMFv.
+
+| User profile remove | resp.conf. |
+|----------------------------|-------------------|
+| Result | M |
+
+| | |
+|------|--------------------------------------------------------------|
+| FEA2 | – Note the completion of the user profile removal procedure. |
+|------|--------------------------------------------------------------|
+
+#### 6.2.1.2 Location information interrogation
+
+The location information interrogation procedure may be invoked in the following cases:
+
+Case 1: the most current version of the user location information residing in the LMFv is the subject of interrogation by the LMFh; and
+
+Case 2: a supporting network interrogates the home network for location information. Case 1 may be implemented independently or as a nested procedure within Case 2.
+
+##### 6.2.1.2.1 Location information interrogation by LMF
+
+This procedure is for the LMFh to interrogate the LMFv for the user information. Upon receiving a request for the user location information, the LMFh may request for the latest/most current location information (e.g. the status and location of the user) from the serving network. See Figure 6.2.1.2-1.
+
+
+
+```
+
+sequenceDiagram
+ participant RAN+CNv as RAN+CNv (LMF)
+ participant CNh as CNh (LMF)
+ Note right of CNh: 0
+ CNh->>RAN+CNv: Location info needed
+ Note left of RAN+CNv: 1
+ RAN+CNv->>CNh: Provide user location information req.ind.
+ Note right of CNh: 2
+ CNh->>RAN+CNv: Provide user location information resp.conf.
+ Note right of CNh: T11105470-00
+
+```
+
+Sequence diagram showing the interaction between RAN+CNv (LMF) and CNh (LMF) for user information interrogation. The sequence starts at 0 with 'Location info needed' from CNh LMF to RAN+CNv LMF. At 1, 'Provide user location information req.ind.' is sent from RAN+CNv LMF to CNh LMF. At 2, 'Provide user location information resp.conf.' is sent from CNh LMF to RAN+CNv LMF. The diagram is labeled T11105470-00.
+
+Figure 6.2.1.2-1/Q.1721 – User information interrogation by LMFh
+
+0. **Location info needed:** initiates the request for user location information interrogation.
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | – Determine the need to acquire current user information in order to perform a mobility management procedure (e.g. Terminal registration), or simply in an updating/relaying mode, to respond to a request for the information. |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **Provide user location information req.ind.:** is sent from the LMFh to the LMFv to request that user information (e.g. state and location information) be given.
+
+| Provide user location information (Response: Success or Failure) | req.ind. |
+|-------------------------------------------------------------------------|-----------------|
+| Requested information | M |
+| IMUI | O (Note) |
+| IMDN | O (Note) |
+
+| | |
+|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | - – Identifies the concerned IMT-2000 user.
- – Retrieves the requested user information.
|
+| NOTE – Either IMUI or IMDN must be provided. | |
+
+2. **Provide user location information resp.conf.:** is sent from the LMFv to the LMFh providing the requested user information (e.g. state and location information).
+
+| Provide user information | resp.conf. |
+|--------------------------|------------|
+| Location information | O (Note) |
+| User state | O (Note) |
+
+| | |
+|---------------------------------------------------------------------|------------------------------------------------------------------|
+| FEA2 | – Note the completion of the Provide User Information procedure. |
+| NOTE – This IE should be provided if it is requested and available. | |
+
+##### 6.2.1.2.2 User information interrogation by SCF
+
+This procedure enables the SCF to obtain the user information (e.g. state of the terminal and its location information) residing in the LMFh. The information is used in support of the IN based services to the user. See Figure 6.2.1.2-2.
+
+
+
+```
+
+sequenceDiagram
+ participant RAN+CNv as RAN+CNv (LMF)
+ participant CNh as CNh (LMF)
+ participant CNs as CNs (SCF)
+ Note right of CNs: User info needed
+ CNs->>CNh: Provide user info req.ind.
+ Note over RAN+CNv, CNh: User info interrogation
+ CNh->>CNs: Provide user info resp.conf.
+
+```
+
+T11105480-00
+
+Sequence diagram for User location information interrogation by SCF. Lifelines: RAN+CNv (LMF), CNh (LMF), and CNs (SCF). The sequence starts at 0 with 'User info needed' from SCF. At 1, SCF sends 'Provide user info req.ind.' to LMFh. At 2, a dashed box labeled 'User info interrogation' spans between LMFv and LMFh. At 3, LMFh sends 'Provide user info resp.conf.' to SCF. Reference T11105480-00 is shown at the bottom right.
+
+Figure 6.2.1.2-2/Q.1721 – User location information interrogation by SCF
+
+0. **User info needed:** initiates the request for user information interrogation.
+
+| | |
+|------|-------------------------------------------------------------------------------------------|
+| FEA0 | – Determine the need to acquire user information in order to provide an IN based service. |
+|------|-------------------------------------------------------------------------------------------|
+
+1. **Provide user information req.ind.:** is sent from the SCF in the supporting network to LMFh to request the user information.
+
+| Provide user information (Response: Success or Failure) | req.ind. |
+|---------------------------------------------------------|----------|
+| Requested information | M |
+| IMUI | O (Note) |
+| IMDN | O (Note) |
+
+| | |
+|------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | - – Identifies the concerned IMT-2000 user.
- – Retrieves the requested user information. If the user information is not available, it requests the information from the LMFv by performing the User info interrogation procedure.
|
+| NOTE – Either the IMUI or the IMDN must be provided. | |
+
+2. **User info interrogation:** is performed if required.
+3. **Provide user information resp.conf.:** is the response from the LMFh to the SCF providing the requested user information.
+
+| Provide user information | resp.conf. |
+|---------------------------------|-------------------|
+| Location information | M |
+| Terminal status | M |
+
+| | |
+|------|-----------------------------------------------------------------------|
+| FEA3 | – Utilize the information received in the SLP that has been executed. |
+|------|-----------------------------------------------------------------------|
+
+#### 6.2.1.3 Subscriber profile transfer
+
+This procedure is invoked when an IMT-2000 user attempts to register in a visited network. This procedure is required as a common module for transferring the subscriber profile from the LMFh to the LMFv when a user roams into a serving network outside its home network. See Figure 6.2.1.3-1.
+
+
+
+```
+
+sequenceDiagram
+ participant RAN+CNv as RAN+CNv (LMF)
+ participant CNh as CNh (LMF)
+ Note left of RAN+CNv: 0
+ CNh->>RAN+CNv: User registration stimulus
+ Note left of RAN+CNv: 1
+ RAN+CNv->>CNh: Profile transfer req.ind.
+ Note left of RAN+CNv: 2
+ CNh->>RAN+CNv: Profile transfer resp.conf.
+ Note right of CNh: T11105490-00
+
+```
+
+Sequence diagram for Subscriber profile transfer. It shows two lifelines: RAN+CNv (LMF) and CNh (LMF). The sequence starts at 0 with a 'User registration stimulus' from CNh to RAN+CNv. At 1, a 'Profile transfer req.ind.' is sent from RAN+CNv to CNh. At 2, a 'Profile transfer resp.conf.' is sent from CNh to RAN+CNv. The diagram is labeled T11105490-00.
+
+Figure 6.2.1.3-1/Q.1721 – Subscriber profile transfer
+
+0. **User registration stimulus:** initiates this procedure.
+
+| | |
+|------|-----------------------------------------------------------------------------------|
+| FEA0 | – Determine that the user profile is needed to support a user in a visiting user. |
+|------|-----------------------------------------------------------------------------------|
+
+1. **Profile transfer req.ind.:** is sent from the LMFh to the LMFv to provide the profile for the roaming user.
+
+| Profile transfer (Response: Success) | req.ind. |
+|---------------------------------------------|-----------------|
+| IMUI | M |
+| Subscriber profile | M |
+
+| | |
+|------|--------------------------------------------------------------------|
+| FEA1 | – Identifies the IMT-2000 user in question and stores the profile. |
+|------|--------------------------------------------------------------------|
+
+2. **Profile transfer resp.conf.:** is the response from the LMFv to the LMFh confirming the update of the user service profile with data provided by the LMFh.
+
+| Profile transfer | resp.conf. |
+|------------------|------------|
+| Result | M |
+
+| | |
+|------|-------------------------------------|
+| FEA2 | – Note successful profile transfer. |
+|------|-------------------------------------|
+
+### 6.2.2 Identity retrieval – user
+
+#### 6.2.2.1 Identity retrieval and update
+
+The UIMF retains TMUI, LAI and the IMT-2000 user's IMUI. For call origination, call termination, terminal location update, etc., the mobile terminal needs to retrieve IMUI, TMUI and the LAI information. For terminal location update, the mobile terminal needs to update TMUI and LAI.
+
+Five information flow diagrams for identity retrieval and update are described, namely:
+
+- IMUI inquiry;
+- TMUI inquiry;
+- LAI inquiry;
+- TMUI update;
+- LAI update.
+
+##### 6.2.2.1.1 IMUI inquiry
+
+See Figure 6.2.2.1-1.
+
+
+
+```
+
+sequenceDiagram
+ participant UIM as UIM (UIMF)
+ participant MT as MT (MCF)
+ Note right of MT: 0 Process request
+ MT->>UIM: 1 IMUI inquiry req.ind.
+ UIM->>MT: 2 IMUI inquiry resp.conf.
+ Note right of MT: T11105500-00
+
+```
+
+Sequence diagram for IMUI inquiry. Lifelines: UIM (UIMF) and MT (MCF). The sequence starts at 0 with a 'Process request' stimulus to the MT. At 1, the MT sends an 'IMUI inquiry req.ind.' message to the UIM. At 2, the UIM sends an 'IMUI inquiry resp.conf.' message back to the MT. The diagram is labeled T11105500-00.
+
+Figure 6.2.2.1-1/Q.1721 – IMUI inquiry
+
+0. **Process request:** is the stimulus for the IMUI inquiry received by the MCF.
+
+| | |
+|------|----------------------------------------|
+| FEA0 | – Initiate the IMUI inquiry procedure. |
+|------|----------------------------------------|
+
+1. **IMUI inquiry req.ind.:** is sent from the MCF to the UIMF to retrieve the IMUI of the subscriber.
+
+| IMUI inquiry (Response: Success or Failure) | req.ind. |
+|---------------------------------------------|----------|
+| None | N/A |
+
+| | |
+|------|----------------------------------------|
+| FEA1 | – Retrieve the IMUI of the subscriber. |
+|------|----------------------------------------|
+
+2. **IMUI inquiry resp.conf.:** is the response to the request.
+
+| IMUI inquiry | resp.conf. |
+|--------------|------------|
+| IMUI | M |
+
+| | |
+|------|--------------------|
+| FEA2 | – Record the IMUI. |
+|------|--------------------|
+
+##### 6.2.2.1.2 TMUI inquiry
+
+See Figure 6.2.2.1-2.
+
+
+
+```
+
+sequenceDiagram
+ participant UIM as UIM
+UIMF
+ participant MT as MT
+MCF
+ Note right of MT: Process request
+ MT->>UIM: TMUI inquiry req.ind.
+ UIM->>MT: TMUI inquiry resp.conf.
+
+```
+
+T11105510-00
+
+Sequence diagram for TMUI inquiry between UIM (UIMF) and MT (MCF). The diagram shows three steps: 0. Process request (external to MT), 1. TMUI inquiry req.ind. (MT to UIM), 2. TMUI inquiry resp.conf. (UIM to MT).
+
+Figure 6.2.2.1-2/Q.1721 – TMUI inquiry
+
+0. **Process request:** received by the MCF initiates the TMUI inquiry.
+
+| | |
+|------|----------------------------------------|
+| FEA0 | – Initiate the TMUI inquiry procedure. |
+|------|----------------------------------------|
+
+1. **TMUI inquiry req.ind.:** is sent from the MCF to the UIMF to retrieve the TMUI of the subscriber.
+
+| TMUI inquiry (Response: Success or Failure) | req.ind. |
+|---------------------------------------------|----------|
+| None | N/A |
+
+| | |
+|------|----------------------------------------|
+| FEA1 | – Retrieve the TMUI of the subscriber. |
+|------|----------------------------------------|
+
+2. **TMUI inquiry resp.conf.:** is the response to the request.
+
+| IMUI inquiry | resp.conf. |
+|---------------------------|------------|
+| TMUI | M |
+| TMUI assignment source ID | M |
+
+| | |
+|------|------------------------------------------------------|
+| FEA2 | – Record the TMUI and the TMUI assignment source ID. |
+|------|------------------------------------------------------|
+
+##### 6.2.2.1.3 LAI inquiry
+
+See Figure 6.2.2.1-3.
+
+
+
+Sequence diagram for LAI inquiry between UIM (UIMF) and MT (MCF). The sequence starts at time 0 with a 'Process request' stimulus to the MCF. At time 1, the MCF sends a 'LAI inquiry req.ind.' message to the UIMF. At time 2, the UIMF sends a 'LAI inquiry resp.conf.' message back to the MCF. The diagram is labeled T11105520-00.
+
+Figure 6.2.2.1-3/Q.1721 – LAI inquiry
+
+0. **Process request:** received by the MCF, is the stimulus for the LAI inquiry.
+
+| | |
+|------|---------------------------------------|
+| FEA0 | – Initiate the LAI inquiry procedure. |
+|------|---------------------------------------|
+
+1. **LAI inquiry req.ind.:** is sent from the MCF to the UIMF to retrieve the LAI of the subscriber.
+
+| LAI inquiry (Response: Success or Failure) | req.ind. |
+|--------------------------------------------|----------|
+| None | N/A |
+
+| | |
+|------|---------------------------------------|
+| FEA1 | – Retrieve the LAI of the subscriber. |
+|------|---------------------------------------|
+
+2. **LAI inquiry resp.conf.:** is the response to the request.
+
+| LAI inquiry | resp.conf. |
+|-------------|------------|
+| LAI | M |
+
+| | |
+|------|-------------------|
+| FEA2 | – Record the LAI. |
+|------|-------------------|
+
+##### 6.2.2.1.4 TMUI update
+
+See Figure 6.2.2.1-4.
+
+
+
+Sequence diagram for TMUI update between UIM (UIMF) and MT (MCF). The sequence starts at time 0 with a 'Process request' stimulus to the MCF. At time 1, the MCF sends a 'TMUI update req.ind.' message to the UIMF. At time 2, the UIMF sends a 'TMUI update resp.conf.' message back to the MCF. The diagram is labeled T11105530-00.
+
+Figure 6.2.2.1-4/Q.1721 – TMUI update
+
+0. **Process request:** stimulus for the TMUI update is received by MCF.
+
+| | |
+|------|---------------------------------------|
+| FEA0 | – Initiate the TMUI update procedure. |
+|------|---------------------------------------|
+
+1. **TMUI update req.ind.:** is sent from the MCF to the UIMF to update the TMUI for the subscriber.
+
+| TMUI update (Response: Success or Failure) | req.ind. |
+|--------------------------------------------|----------|
+| TMUI | M |
+| TMUI assignment source ID | M |
+
+| | |
+|------|----------------------------------------------------------------------------|
+| FEA1 | – Update TMUI for the subscriber and record the TMUI assignment source ID. |
+|------|----------------------------------------------------------------------------|
+
+2. **TMUI update resp.conf.:** is the response to the request.
+
+| TMUI update | resp.conf. |
+|-------------|------------|
+| None | N/A |
+
+| | |
+|------|-------------------------------|
+| FEA2 | – Note successful completion. |
+|------|-------------------------------|
+
+##### 6.2.2.1.5 LAI update
+
+See Figure 6.2.2.1-5.
+
+
+
+```
+
+sequenceDiagram
+ participant UIMF
+ participant MCF
+ Note right of MCF: Process request
+ MCF->>UIMF: LAI update req.ind.
+ UIMF->>MCF: LAI update resp.conf.
+
+```
+
+T11105540-00
+
+Sequence diagram for LAI update between UIMF and MCF. The diagram shows three steps: 0. Process request (stimulus to MCF), 1. LAI update req.ind. (MCF to UIMF), and 2. LAI update resp.conf. (UIMF to MCF).
+
+Figure 6.2.2.1-5/Q.1721 – LAI update
+
+0. **Process request:** stimulus for the LAI update is received by MCF.
+
+| | |
+|------|---------------------------------------|
+| FEA0 | – Send request to UIMF to update LAI. |
+|------|---------------------------------------|
+
+1. **LAI update req.ind.:** is sent from the MCF to the UIMF to update LAI of the subscriber.
+
+| LAI update (Response: Success or Failure) | req.ind. |
+|-------------------------------------------|----------|
+| LAI | M |
+
+| | |
+|------|-------------------------------------|
+| FEA1 | – Update the LAI of the subscriber. |
+|------|-------------------------------------|
+
+2. **LAI update resp.conf.:** is the response to the request.
+
+| LAI update | resp.conf. |
+|-------------------|-------------------|
+| None | N/A |
+
+| | |
+|------|-------------------------------|
+| FEA2 | – Note successful completion. |
+|------|-------------------------------|
+
+#### **6.2.2.2 User ID retrieval**
+
+This procedure is used to convert the TMUI to the IMUI of the user. The newly visited network initiates this procedure when the network receives the TMUI, or a set of TMUI, and the TMUI assignment source ID as user ID from the mobile side.
+
+For Terminal location registration and update, there are two cases:
+
+- Case 1: TMUI has been assigned by newly visited LMF (see 6.2.2.1.2).
+- Case 2: TMUI has been assigned by another LMF different from newly visited LMF (this subclause).
+
+If the newly visited network cannot retrieve the IMUI successfully (e.g. loses the TMUI), then the newly visited network attempts to retrieve the IMT-2000 user's IMUI from the UIMF (see 6.2.2.1.1). See Figure 6.2.2.2-1.
+
+
+
+Sequence diagram showing IMUI and Authentication info retrieval information flow between a new RAN+CNv LMF and a previous RAN+CNv LMF. The sequence starts at 0 with 'UserID received' at the new LMF. At 1, 'IMUI and auth info retrieval req.ind.' is sent from the new LMF to the previous LMF. At 2, 'IMUI and auth info retrieval resp.conf.' is sent from the previous LMF back to the new LMF. The diagram is labeled T11105550-00.
+
+**Figure 6.2.2.2-1/Q.1721 – IMUI and Authentication info retrieval information flow diagram**
+
+0. **UserID received:** received by the newly visited LMF initiates this procedure.
+
+| | |
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | For Case 1:
– Retrieve the IMUI of the requesting IMT-2000 user with the TMUI.
For Case 2:
– Identify the LMF by which the TMUI is assigned with the TMUI assignment source ID. |
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **IMUI and authentication info retrieval req.ind.:** is used to retrieve the IMUI with the TMUI. This information flow is sent to the LMF in the previous visited network.
+
+| IMUI and authentication info retrieval (Response: Success or Failure) | req.ind. |
+|------------------------------------------------------------------------------|-----------------|
+| TMUI | M |
+| TMUI assignment source ID | M |
+
+| | |
+|------|-------------------------------------------------------------------------------------------------------|
+| FEA1 | – Retrieve the IMUI and unused authentication triplets of the requesting IMT-2000 user with the TMUI. |
+|------|-------------------------------------------------------------------------------------------------------|
+
+2. **IMUI retrieval resp.conf.:** is the response to the request.
+
+| IMUI and authentication info retrieval | resp.conf. |
+|-----------------------------------------------|-------------------|
+| IMUI | M |
+| Result | M |
+| Challenge(s) | O (Note 1) |
+| Challenge Response(s) | O (Note 1) |
+| Ciphering Key(s) | O (Note 2) |
+
+| | |
+|-----------------------------------------------------------|-----------------------------------------|
+| FEA2 | – Confirm completion of IMUI retrieval. |
+| NOTE 1 – Included if authentication is to be carried out. | |
+| NOTE 2 – Returned if available. | |
+
+### 6.2.3 Registration management
+
+#### 6.2.3.1 Terminal location registration
+
+This feature is used when an IMT-2000 user notifies the system on his location. This procedure enables the location area information of the IMT-2000 user to be registered in the visited network. A Terminal location registration procedure is carried out when no previous location details are known about the user when he first appears in a network domain. During this procedure, all the information on the user is erased in the previously visited network. Updating of the location area information may occur after network or terminal failure. See Figure 6.2.3.1-1.
+
+
+
+```
+
+sequenceDiagram
+ participant UIM as UIM (UIMF)
+ participant MT as MT (MCF)
+ participant RAN as RAN+CNv (SACF, LMF)
+ participant CNh as CNh (LMF)
+ participant CNpv as CNpv (LMF)
+
+ Note left of UIM: 0
+ UIM->>MT: Terminal location registration request
+ Note left of UIM: 1
+ UIM->>UIM: IMUI or TMUI Inquiry
+ Note left of UIM: 2
+ UIM->>RAN: Terminal location registration req.ind.
+ Note left of UIM: 3
+ UIM->>CNpv: User ID retrieval
+ Note left of UIM: 4
+ UIM->>CNh: User authentication
+ Note left of UIM: 5
+ CNh->>RAN: Roaming registration req.ind.
+ Note left of UIM: 6
+ RAN->>CNpv: Subscriber profile transfer
+ Note left of UIM: 7
+ CNh->>RAN: Roaming registration resp.conf.
+ Note left of UIM: 8
+ RAN->>MT: Start ciphering
+ Note left of UIM: 9
+ UIM->>CNh: TMUI assignment
+ Note left of UIM: 10
+ CNh->>RAN: Terminal location registration resp.conf.
+ Note left of UIM: 11
+ UIM->>MT: LAI update
+ Note left of UIM: 12
+ CNh->>CNpv: De-registration req.ind.
+ Note left of UIM: 13
+ CNpv->>CNh: De-registration resp.conf.
+
+```
+
+T11105560-00
+
+Sequence diagram for Terminal location registration. Lifelines: UIM (UIMF), MT (MCF), RAN+CNv (SACF, LMF), CNh (LMF), CNpv (LMF). The sequence shows steps from Terminal location registration request to De-registration resp.conf. with a note that steps 12 and 13 are optional and can occur after step 5.
+
+NOTE – IFs 12 and 13 may occur any time after IF 5 and are independent of IFs 8 through 11 inclusive.
+
+Figure 6.2.3.1-1/Q.1721 – Terminal location registration
+
+0. **Terminal location registration request:** is initiated when the MT is powered-up and attempts to register in the network using the information broadcast by that network.
+
+| | |
+|------|-----------------------------|
+| FEA0 | – Obtain the user identity. |
+|------|-----------------------------|
+
+1. **IMUI or TMUI inquiry:** is used to obtain the IMUI or TMUI as appropriate.
+
+2. **Terminal location registration req.ind.:** is used to register the location area information of the mobile terminal to the network.
+
+| Terminal location registration (Response: Success or Failure) | req.ind. |
+|---------------------------------------------------------------|------------|
+| UserID | M (Note 1) |
+| TC Info | O (Note 2) |
+| AUTH_R | O (Note 3) |
+| Confirmation of RANDG | O (Note 3) |
+| CHCNT | O (Note 3) |
+
+| | |
+|------|-----------------------------------------------------------------------------------|
+| FEA2 | – Initiate User ID retrieval procedure to retrieve the IMUI, if the TMUI is used. |
+|------|-----------------------------------------------------------------------------------|
+
+NOTE 1 – Either IMUI or TMUI as available.
+
+NOTE 2 – If available, sent to indicate the services that the terminal can support.
+
+NOTE 3 – If the global challenge (random number) is used in the broadcast information for authentication purposes, authentication data is sent.
+
+3. **User ID retrieval:** is executed if required.
+
+4. **User authentication:** is executed.
+
+5. **Roaming registration req.ind.:** is used to update the LMFv address in the home network.
+
+| Roaming registration (Response: Success or Failure) | req.ind. |
+|-----------------------------------------------------|----------|
+| IMUI | M |
+| LMFv address | M |
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA5 | - – Identify the requesting IMT-2000 user.
- – Update the LMFv address.
- – Identify the LMFv address of the previously visited network, if applicable.
- – Initiate User Profile Update if required.
|
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+6. **Subscriber profile transfer:** is executed if required.
+
+7. **Roaming registration resp.conf.:** is the confirmation to Roaming Registration req.ind.
+
+| Roaming registration | resp.conf. |
+|----------------------|------------|
+| Result | M |
+
+| | |
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA7 | - – Confirm completion of roaming registration for the IMT-2000 user.
- – Identify Location area and TC info.
- – Store Location area and TC info for the IMT-2000 user.
- – Invoke TMUI update procedure for the IMT-2000 user.
|
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+8. **Start ciphering:** is executed if appropriate.
+
+9. **TMUI assignment:** is executed.
+
+| | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
+| FEA9 | – Analyse the result of TMUI update procedure. |
+| NOTE – TMUI update procedure module is separated from user authentication procedure module in order to assign TMUI after user profile is created in the newly visited network. | |
+
+10. **Terminal location registration resp.conf.:** is the confirmation of Terminal location registration req.ind.
+
+| Terminal location registration | resp.conf. |
+|--------------------------------|------------|
+| Result | M |
+
+| | |
+|-------|--------------------------------------------------------------------|
+| FEA10 | – Memorize Location area identifier of current location in the MT. |
+|-------|--------------------------------------------------------------------|
+
+11. **LAI update:** is executed to update the Location Area Identifier in the UIM.
+
+12. **De-registration req.ind.:** is optionally used to de-register the user from the previously visited network.
+
+| De-registration (Response: Success or Failure) | req.ind. |
+|------------------------------------------------|----------|
+| IMUI | M |
+
+| | |
+|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA12 | - – Identify the requesting IMT-2000 user.
- – Remove user profile of the requesting IMT-2000 user.
- – Formulate and send De-registration resp.conf.
|
+|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+13. **De-registration resp.conf.:** is the confirmation of De-registration req.ind.
+
+| De-registration | resp.conf. |
+|-----------------|------------|
+| Result | M |
+
+| | |
+|------|---------------------------------------|
+| FEA8 | – Identify the newly visited network. |
+|------|---------------------------------------|
+
+#### 6.2.3.2 Terminal location updating
+
+This feature is used when an IMT-2000 user who roams within the same network domain notifies the system on his new location area. This new location area information is then registered in the visited network. Updating of such location area information may also occur after a network or terminal failure. See Figure 6.2.3.2-1.
+
+
+
+```
+
+sequenceDiagram
+ participant UIMF as UIM (UIMF)
+ participant MCF as MT (MCF)
+ participant RAN_CNv as RAN+CNv (SACF, LMF)
+ participant CNh as CNh (LMF)
+
+ Note over UIMF, CNh: 0 Terminal location update request
+ UIMF->>MCF: Terminal location update request
+ Note over UIMF, MCF: 1 TMUI inquiry
+ UIMF-->>MCF: TMUI inquiry
+ Note over MCF, RAN_CNv: 2 Terminal location update req.ind.
+ MCF->>RAN_CNv: Terminal location update req.ind.
+ Note over UIMF, RAN_CNv: 3 User ID retrieval
+ RAN_CNv-->>UIMF: User ID retrieval
+ Note over UIMF, CNh: 4 User authentication
+ UIMF-->>CNh: User authentication
+ Note over MCF, RAN_CNv: 5 Start ciphering
+ RAN_CNv-->>MCF: Start ciphering
+ Note over UIMF, RAN_CNv: 6 TMUI update
+ MCF-->>UIMF: TMUI update
+ Note over MCF, RAN_CNv: 7 Terminal location update resp.conf.
+ RAN_CNv->>MCF: Terminal location update resp.conf.
+ Note over UIMF, MCF: 8 LAI update
+ MCF-->>UIMF: LAI update
+
+```
+
+Sequence diagram for Terminal location updating. Lifelines: UIM (UIMF), MT (MCF), RAN+CNv (SACF, LMF), CNh (LMF). The sequence starts with a 'Terminal location update request' from UIMF to MCF. Step 1: 'TMUI inquiry' from UIMF to MCF. Step 2: 'Terminal location update req.ind.' from MCF to LMF. Step 3: 'User ID retrieval' from LMF to UIMF. Step 4: 'User authentication' from UIMF to LMF. Step 5: 'Start ciphering' from LMF to MCF. Step 6: 'TMUI update' from MCF to UIMF. Step 7: 'Terminal location update resp.conf.' from LMF to MCF. Step 8: 'LAI update' from MCF to UIMF. The diagram is labeled T11105570-00.
+
+Figure 6.2.3.2-1/Q.1721 – Terminal location updating
+
+0. **Terminal location update request:** request is initiated by the visited network.
+
+| | |
+|------|---------------------------------------------------------|
+| FEA0 | – Initiate TMUI inquiry procedure to retrieve the TMUI. |
+|------|---------------------------------------------------------|
+
+1. **TMUI inquiry:** is executed.
+2. **Terminal location update req.ind.:** is sent from the MCF to the LMFv.
+
+| Terminal location update (Response: Success or Failure) | req.ind. |
+|---------------------------------------------------------|------------|
+| TMUI | M |
+| TMUI sourceID | M |
+| AUTH_R | O (Note 1) |
+| Confirmation of RANDG | O (Note 1) |
+| CHCNT | O (Note 2) |
+| Terminal Status | O (Note 3) |
+| TC info | O (Note 3) |
+
+| | |
+|-----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA2 | – Initiate User ID retrieval procedure, if TMUI and TMUI assignment source ID are used as the IMT-2000 user ID in the Terminal location update request. |
+| NOTE 1 – Included if authentication is to be carried out. | |
+| NOTE 2 – Included if Call History Count is available. | |
+| NOTE 3 – Provided if available. | |
+
+3. **User ID retrieval:** is executed to identify the requesting IMT-2000 user, if needed.
+4. **User authentication:** is executed if the User ID retrieval procedure was executed.
+5. **Start ciphering:** is executed if the user authentication procedure was executed.
+6. **TMUI update:** is executed following the above two procedures if they were executed.
+7. **Terminal location update resp.conf.:** is the confirmation to Terminal location update req.ind.
+
+| Terminal location update | resp.conf. |
+|--------------------------|------------|
+| Result | M |
+
+| | |
+|------|-----------------------------------------------------------|
+| FEA7 | – Record the LAI.
– Initiate the LAI update procedure. |
+|------|-----------------------------------------------------------|
+
+8. **LAI update:** procedure is executed.
+
+#### 6.2.3.3 Detach
+
+The terminal explicitly notifies the serving network that it will not be reachable (e.g. switching off or do not disturb), using this procedure.
+
+In certain situations (e.g. following a period of inactivity) the visited network may decide to notify the LMFh that the user is not reachable, so that for example any request for routing information for mobile terminating calls will be treated accordingly.
+
+This capability may also be used in other implicit cases (e.g. battery discharge or radio signal deterioration). See Figure 6.2.3.3-1.
+
+
+
+Sequence diagram for the Detach procedure. Lifelines: UIM (UIMF), MT (MCF), RAN+CNv (SACF, LMF), and CNh (LMF). The sequence starts with a Detach request from UIMF to MCF. Step 1: TMUI inquiry from UIMF to MCF. Step 2: Detach req.ind. from MCF to SACF. Step 3: User ID retrieval from SACF to LMF. Step 4: User authentication (dashed box) between SACF and LMF. Step 5: Detach resp.conf. from SACF to MCF. Step 6: Purge req.ind. from LMF to CNh. Step 7: Purge resp.conf. from CNh to LMF. The diagram is numbered 0 to 7 on both sides.
+
+T11105580-00
+
+Figure 6.2.3.3-1/Q.1721 – Detach
+
+0. **Detach request:** is the stimulus, initiates the Detach procedure.
+
+| | |
+|------|---------------------------------------------------------|
+| FEA0 | – Initiate TMUI inquiry procedure to retrieve the TMUI. |
+|------|---------------------------------------------------------|
+
+1. **TMUI inquiry:** procedure is executed.
+
+2. **Detach req.ind.:** is used by the terminal to notify the serving network that it is going to be unreachable.
+
+| Detach (Response: Success or Failure) | req.ind. |
+|---------------------------------------|----------|
+| UserID | M (Note) |
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------|
+| FEA2 | – Initiate User ID retrieval procedure, if TMUI and TMUI assignment source ID are used as the IMT-2000 User ID in the Detach request. |
+|------|---------------------------------------------------------------------------------------------------------------------------------------|
+
+NOTE – TMUI should be used instead of IMUI as the IMT-2000 User ID to keep the identity of the user confidential.
+
+3. **User ID retrieval:** procedure is executed.
+
+4. **User authentication procedure:** is executed, if necessary.
+
+5. **Detach resp.conf.:** is the confirmation of the Detach req.ind.
+
+| Detach | resp.conf. |
+|--------|------------|
+| Result | M |
+
+| | |
+|------|-----------------------------------------------|
+| FEA5 | – Note that the Detach procedure is complete. |
+|------|-----------------------------------------------|
+
+6. **Purge req.ind.:** is used by the serving network to notify the home network that the terminal is unreachable.
+
+| Purge (Response: Success or Failure) | req.ind. |
+|--------------------------------------|----------|
+| IMUI | M |
+| LMFv address | O |
+
+| | |
+|------|---------------------------------------------------------------------|
+| FEA6 | – Mark the IMT-2000 user as not reachable in the notifying network. |
+|------|---------------------------------------------------------------------|
+
+7. **Purge resp.conf.:** is the confirmation to Purge req.ind.
+
+| Purge | resp.conf. |
+|--------|------------|
+| Result | M |
+
+| | |
+|------|-------------------------------------------------------------------------|
+| FEA7 | – Decide whether the subscriber record has to be deleted from the LMFv. |
+|------|-------------------------------------------------------------------------|
+
+#### 6.2.3.4 Attach
+
+See Figure 6.2.3.4-1.
+
+
+
+Sequence diagram for the Attach procedure. Lifelines: UIM (UIMF), MT (MCF), RAN+CNv (SACF, LMF), and CNh (LMF). The sequence starts at 0 with an 'Attach request' from UIMF to MCF. At 1, UIMF sends a 'TMUI inquiry' to MCF. At 2, MCF sends an 'Attach req.ind.' to SACF. At 3, SACF and LMF perform 'User ID retrieval'. At 4, a 'User authentication' block occurs between UIMF, MCF, and LMF. At 5, LMF sends an 'Attach resp.conf.' to MCF. The diagram is labeled T11105590-00.
+
+NOTE – If the Attach procedure fails, the MT should interpret this as a need to do the Terminal Location Registration procedure.
+
+Figure 6.2.3.4-1/Q.1721 – Attach
+
+0. **Attach request:** initiates the Attach procedure.
+
+| | |
+|------|---------------------------------------------------------|
+| FEA0 | – Initiate TMUI inquiry procedure to retrieve the TMUI. |
+|------|---------------------------------------------------------|
+
+1. **TMUI inquiry:** is executed.
+2. **Attach req.ind.:** is used by the terminal to notify the serving network that the MT is reachable.
+
+| Attach (Response: Success or Failure) | req.ind. |
+|----------------------------------------------|-----------------|
+| TMUI | M |
+
+| | |
+|------|-----------------------------------------|
+| FEA0 | – Initiate User ID retrieval procedure. |
+|------|-----------------------------------------|
+
+3. **User ID retrieval:** is executed.
+4. **User authentication:** is executed, if necessary as a result of the above procedure.
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA4 | - – Based on a short message state info in the LMFv (e.g. short message transfer failure because terminal is unreachable), the short message notification procedure will start (not shown in the figure).
- – If LMFv has the flag set to show that the home system's roaming data is unreliable, the location update will be executed (not shown in the figure).
- – Acknowledge the Attach req.ind.
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+5. **Attach resp.conf.:** is the confirmation of the Attach req.ind.
+
+| Attach | resp.conf. |
+|---------------|-------------------|
+| Result | M |
+
+| | |
+|-------|----------------------------------|
+| FEA 5 | – MT continues normal operation. |
+|-------|----------------------------------|
+
+### 6.2.4 Location data fault recovery
+
+This category of procedures deals with recovery after fault situation. The purpose is to make sure that data stored in different nodes is consistent. In this category three procedures apply:
+
+- Unreliable roamer data.
+- Check supplementary service data indication.
+- Restore LMF data.
+
+#### 6.2.4.1 Unreliable roamer data
+
+Unreliable roamer data is used to inform a Visited System that the Home System's roaming mobile terminal data is unreliable (e.g. due to a system failure). See Figure 6.2.4.1-1.
+
+
+
+Sequence diagram showing the interaction between RAN+CNv (LMF) and CNh (LMF) for unreliable roamer data. The sequence starts at 0 with 'Roaming data unreliable' from CNh to RAN+CNv. At 1, 'Unreliable roamer data req.ind.' is sent from RAN+CNv to CNh. At 2, 'Unreliable roamer data resp.conf.' is sent from CNh to RAN+CNv. The diagram is labeled T11105600-00.
+
+**Figure 6.2.4.1-1/Q.1721 – Unreliable roamer data**
+
+0. **Roaming data unreliable:** indicates that roamer data is unreliable and initiates notification of other systems.
+
+| | |
+|------|------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | – LMFh prepares to inform other system(s) that it has experienced a failure which renders its roaming data unreliable. |
+|------|------------------------------------------------------------------------------------------------------------------------|
+
+1. **Unreliable roamer data req.ind.:** is sent from LMFh to LMF(s) in other system(s).
+
+| Unreliable roamer data (Response: Success or Failure) | req.ind. |
+|-------------------------------------------------------|----------|
+| Home network ID | M |
+
+| | |
+|------|-------------------------------------------------------------------------------------------------|
+| FEA1 | – The LMFv removes all records of the subscribers associated with the LMFh sending the message. |
+|------|-------------------------------------------------------------------------------------------------|
+
+2. **Unreliable roamer data resp.conf.:** is the response to the request.
+
+| Unreliable roamer | resp.conf. |
+|-------------------|------------|
+| Result | M |
+
+| | |
+|------|-----------------------------|
+| FEA2 | – Note the acknowledgement. |
+|------|-----------------------------|
+
+#### 6.2.4.2 Check supplementary service data indication
+
+The Check supplementary service data feature is used by the LMFh to indicate to the mobile user that supplementary service data might be altered due to the restart. On receipt from the LMFh, the LMFv forwards this indication to SACF which in turn forwards this indication to the MCF. See Figure 6.2.4.2-1.
+
+
+
+Sequence diagram showing the 'Check supplementary service data indication' procedure. Lifelines: MT (MCF), RAN+CNv (SACF, LMF), and CNh (LMF). The sequence starts with a 'Restart' stimulus at time 0. At time 1, the LMF in CNh sends a 'Check SS data req.ind.' message to the LMF in RAN+CNv. At time 2, the SACF in RAN+CNv sends a 'Check SS data req.ind.' message to the MCF in MT. The diagram is labeled T11105610-00.
+
+Figure 6.2.4.2-1/Q.1721 – Check supplementary service data indication
+
+0. **Restart:** is the stimulus, initiates the Check SS data procedure.
+
+| | |
+|------|--------------------------------------------------------------------------------------------------------------------|
+| FEA0 | – Determine that a restart has occurred and that the mobile should be informed of possible changes to the SS data. |
+|------|--------------------------------------------------------------------------------------------------------------------|
+
+1. **Check SS data req.ind.:** is sent from LMFh to LMFv.
+
+| Check SS data (Response: None) | req.ind. |
+|--------------------------------|----------|
+| None | N/A |
+
+| | |
+|------|----------------------------------|
+| FEA1 | – Forward Check SS data req.ind. |
+|------|----------------------------------|
+
+2. **Check SS data req.ind.:** is sent from SACF to MCF.
+
+| Check SS data (Response: None) | req.ind. |
+|--------------------------------|----------|
+| None | N/A |
+
+| | |
+|------|-----------------------------------------------------------------------------|
+| FEA2 | – The terminal should indicate to the user that SS info should be verified. |
+|------|-----------------------------------------------------------------------------|
+
+#### 6.2.4.3 Restore LMF data
+
+The Restore LMF data feature is used to indicate to the LMFh that it has received a Provide roaming number operation for an unknown IMUI or for a known IMUI with the indicator "Confirmed by HLR" set to "Not confirmed". The service is used to update the Location number (i.e. LAI and LMFv address) in the LMFh, if provided, and to request the LMFh to send all subscriber profile data to the LMFv. See Figure 6.2.4.3-1.
+
+
+
+```
+
+sequenceDiagram
+ participant RAN+CNv
+ participant CNh
+ Note left of RAN+CNv: LMF
+ Note right of CNh: LMF
+ Note left of RAN+CNv: 0
+ Note right of CNh: 0
+ RAN+CNv->>RAN+CNv: Request for unknown or unconfirmed IMUI
+ Note left of RAN+CNv: 1
+ Note right of CNh: 1
+ RAN+CNv->>CNh: Restore LMF data req.ind.
+ Note left of RAN+CNv: 2
+ Note right of CNh: 2
+ RAN+CNv->>CNh: Subscriber profile transfer
+
+```
+
+Sequence diagram showing the Restore LMF data procedure between RAN+CNv and CNh. The diagram includes three steps: 0. Request for unknown or unconfirmed IMUI, 1. Restore LMF data req.ind., and 2. Subscriber profile transfer. The diagram is labeled T11105620-00.
+
+**Figure 6.2.4.3-1/Q.1721 – Restore LMF data**
+
+0. **Request for unknown or unconfirmed IMUI:** initiates the Restore LMF data procedure.
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | – Determine that a roaming number was requested for an unknown IMUI or for an IMUI that needs confirmation from the LMFh. |
+|------|---------------------------------------------------------------------------------------------------------------------------|
+
+1. **Restore LMF data req.ind.:** is sent from the LMFv to the LMFh.
+
+| Restore LMF data (Response: Success or Failure) | req.ind. |
+|-------------------------------------------------|----------|
+| IMUI | M |
+| LAI | M |
+
+| | |
+|------|------------------------------------------------------|
+| FEA1 | – Execute the subscriber profile transfer procedure. |
+|------|------------------------------------------------------|
+
+2. **Subscriber profile transfer:** is executed to complete the restoration process.
+
+# 7 Basic call and bearer control
+
+This clause provides the information flows for Basic call and bearer control for IMT-2000 systems, for setting up and tearing down voice calls using circuit switched or packet based bearers.
+
+Basic call and bearer control encompasses IFs for:
+
+- Mobile outgoing call;
+- Terminal paging;
+- Call routing;
+- Mobile incoming call;
+- Mobile call release;
+- Emergency call; and
+- Priority Call.
+
+## 7.1 Mobile outgoing call
+
+The Mobile outgoing call procedure involves a mobile subscriber originating a call in the idle state (initial call) or in the busy state (additional call). Before the call is established, the visited network validates the calling party and may invoke services based on the origination attempt. This procedure is either local to the serving network or uses the VHE network capability.
+
+### 7.1.1 Initial mobile outgoing call
+
+The Initial mobile outgoing call procedure is used when the user originates a call in the idle state. See Figure 7.1.1-1.
+
+
+
+The sequence diagram illustrates the interaction for an initial mobile outgoing call. The lifelines are UIM (with UIMF), MT (with MCF), RAN+CNv (with SACF and LMF), CNh (with LMF), and CNs (with SCF/SDF). The sequence of messages is as follows:
+
+
+- 0: **outgoing call request** from MT to UIMF.
+- 1: **User info req.ind.** from MCF to UIMF.
+- 2: **User info resp.conf.** from UIMF to MCF.
+- 3: **Setup req.ind.** from MCF to SACF.
+- 4: **User authentication** (sequence block between SACF and LMF).
+- 5: **Terminal location registration** (sequence block between SACF and LMF).
+- 6: **Start ciphering** (sequence block between SACF and LMF).
+- 7: **TMUI assignment** (sequence block between SACF and LMF).
+- 8: **VHE service invocation** (sequence block between SACF and SCF/SDF).
+- 9: **Setup resp.conf.** from SACF to MCF.
+
+Sequence diagram showing the initial mobile outgoing call information flow between UIM, MT, RAN+CNv, CNh, and CNs. The diagram includes steps for outgoing call request, user info req.ind., user info resp.conf., setup req.ind., user authentication, terminal location registration, start ciphering, TMUI assignment, VHE service invocation, and setup resp.conf. The diagram is labeled T11105630-00.
+
+Figure 7.1.1-1/Q.1721 – Initial mobile outgoing call information flow diagram
+
+0. **Outgoing call request:** the mobile subscriber initiates an outgoing (mobile originated) call in the idle state.
+
+| | |
+|------|------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | – The MT may interact with the subscriber to accumulate information. It may invoke service logic (e.g. speed dialling list). |
+|------|------------------------------------------------------------------------------------------------------------------------------|
+
+1. **User info req.ind.:** the MCF optionally queries the UIMF for further information/instructions.
+
+| User info (Response: Success or Failure) | req.ind. |
+|------------------------------------------|----------|
+| UIM information request | M |
+
+| | |
+|------|------------------------------------------------------------------------------------------------|
+| FEA1 | – Optionally, invoke local (e.g. UIM based) service logic.
– Collect requested information. |
+|------|------------------------------------------------------------------------------------------------|
+
+2. **User info resp.conf.:** the UIMF returns the requested user information to the MCF.
+
+| User info | resp.conf. |
+|--------------------------|------------|
+| UIM information response | M |
+
+| | |
+|------|-----------------------------------------|
+| FEA2 | Initiate call setup and bearer request. |
+|------|-----------------------------------------|
+
+3. **Setup req.ind.:** the MCF proceeds to set up the call, and requests the SACF in the serving network to allocate a bearer channel.
+
+| Setup (Response: Success or Failure) | req.ind. |
+|--------------------------------------|------------|
+| UserID | M (Note 1) |
+| Called Number | M |
+| Calling Number | M |
+| Service Identifier | M |
+| Billing ID | O (Note 2) |
+| Bearer Capability | O (Note 3) |
+| QoS | O (Note 4) |
+| AUTH_R | O (Note 5) |
+| RANDC | O (Note 5) |
+| CHCNT | O (Note 5) |
+| IMEI | O (Note 5) |
+| AUTHKEYS | O (Note 6) |
+| SRES | O (Note 7) |
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA3 | - – Optionally, invoke and await completion of User authentication.
- – Optionally, invoke and await completion of Terminal location registration.
- – Optionally, invoke and await completion of Start ciphering.
- – Set up the call and bearer channel.
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+NOTE 1 – Include either IMUI or TMUI as available. TMUI is recommended for over-the-air security.
+
+NOTE 2 – Include if required by the home service provider.
+
+NOTE 3 – Include to indicate the capability of the bearer channel.
+
+NOTE 4 – Include to indicate desired quality of service.
+
+NOTE 5 – Include to provide authentication related information only for SSD based systems.
+
+NOTE 6 – Include to provide authentication related information only for non-SSD based systems.
+
+NOTE 7 – Include to provide the signature result.
+
+4. **User authentication:** if authentication is required for this call attempt, it is performed.
+
+5. **Terminal location registration:** if the MT is not registered in the visited network, terminal location registration is performed.
+
+6. **Start ciphering:** if ciphering is required for this call attempt, it is initiated.
+
+7. **TMUI assignment:** if a TMUI needs to be assigned, it can be done any time after ciphering has been initiated.
+
+8. **VHE service invocation:** based on the subscriber profile, the visited network may invoke IN service logic. This may occur at any defined and active trigger detection point.
+
+9. **Setup resp.conf.:** the SACF in the visited network reports the successful completion of call and bearer channel setup.
+
+| Setup | resp.conf. |
+|-----------|------------|
+| Bearer ID | M |
+
+| | |
+|------|-----------------------------------------|
+| FEA9 | Complete call setup on selected bearer. |
+|------|-----------------------------------------|
+
+### 7.1.2 Additional mobile outgoing call
+
+The mobile outgoing additional call involves a mobile subscriber originating a second call while already on a call, i.e. a three-way call. The procedure is performed similarly to mobile outgoing calls.
+
+## 7.2 Terminal paging
+
+The Terminal paging procedure is used to page a mobile terminal. See Figure 7.2-1.
+
+
+
+Sequence diagram for Terminal paging showing interactions between UIM (UIMF), MT (MCF), and RAN+CNv (SACF). The sequence starts with a 'Paging request' from RAN+CNv to SACF at time 0. At time 1, SACF sends 'Paging req.ind.' to MCF. At time 2, MCF sends 'TMUI inquiry' to UIMF. At time 3, UIMF sends 'User info req.ind.' to MCF. At time 4, MCF sends 'User info resp.conf.' to UIMF. At time 5, MCF sends 'Paging resp.conf.' to SACF. The diagram is labeled T11105640-00.
+
+Figure 7.2-1/Q.1721 – Terminal paging
+
+0. **Paging request:** a mobile incoming call results in a page request at the visited network.
+
+| | |
+|------|-------------------------------------------------------------|
+| FEA0 | – The visited network forwards the page request to the MCF. |
+|------|-------------------------------------------------------------|
+
+1. **Paging req.ind.:** the visited network attempts to page the mobile terminal.
+
+| Paging (Response: Success or Failure) | req.ind. |
+|---------------------------------------|----------|
+| TMUI | M |
+
+| | |
+|------|------------------------------------|
+| FEA1 | – Prepare to perform TMUI inquiry. |
+|------|------------------------------------|
+
+2. **TMUI inquiry:** the MCF retrieves the TMUI from the UIMF, compares it to the received TMUI from the visited network and determines that the page request is meant for this mobile terminal.
+3. **User info req.ind.:** optionally the MCF queries the UIMF for further information/instructions.
+
+| User info (Response: Success or Failure) | req.ind. |
+|-------------------------------------------------|-----------------|
+| Termination treatment request | O (Note) |
+
+| | |
+|-----------------------------------------------------------------|------------------------------------------|
+| FEA3 | Instruct the MCF to respond to the page. |
+| NOTE – Include to request page response instructions from UIMF. | |
+
+4. **User info resp.conf.:** the UIMF returns the requested information to the MCF.
+
+| User info | resp.conf. |
+|----------------------------|-------------------|
+| Termination treatment info | O (Note) |
+
+| | |
+|------------------------------------------------------------------------------|-----------------------------------|
+| FEA4 | – Prepare to respond to the page. |
+| NOTE – Include to indicate type of call termination treatment to be applied. | |
+
+5. **Paging resp.conf.:** the MCF responds to the page.
+
+| Paging | resp.conf. |
+|---------------|-------------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|--------|
+| FEA5 | – None |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+## 7.3 Network call routing
+
+This subclause addresses end-to-end information flows for inter-family (or inter-network) IMT-2000 call routing operations. Routing a call within an IMT-2000 family member system is considered an intra-family operation and is not addressed here.
+
+The Call routing procedure is used to get an address (e.g. roaming number) from the network element of the visited network where the user is located in order to route a terminating call. The address is dynamically linked to the identity of the user.
+
+Routing information data is needed by the interrogating networks for requesting a "Call Setup" to the visited network of the called party. The term "Routing Information" is used here to represent all the information data that is needed to identify the visited network and the user's terminal location.
+
+Routing Information query can be executed directly between networks. When either the originating network or the intermediate network is the interrogating network, the query for routing information is sent directly to the home network without routing the call (Call setup request) to the home network. However, the execution depends on the bilateral agreement between networks. When neither the originating network nor the intermediate network are capable of interrogation, the call is routed to the home network and the first query is invoked there. In all these cases, there is only one "interrogating network", either the originating, the intermediate or the home network.
+
+The call routing procedure uses a chain interrogation scheme by which the interrogating network obtains updated routing information (e.g. DN, IP Address) directly from the called party's home network. Furthermore, the chain query scheme is defined as the procedure by which the interrogating network queries for routing information to the called party's home network, and then the home network queries the visited network for the updated called party's routing information.
+
+The following assumptions are made related to this Call routing information flow:
+
+- The "Interrogating Network" could either be the originating, an intermediate, or a supporting network.
+- Query for "Routing Information" is sent in a chain scheme from the interrogating network to the called party's home network, and after receiving the information, the call setup request is sent to the called party's visited network.
+- The Paging execution in the called party's visited network may be carried out any time after receiving a request for routing information.
+
+See Figure 7.3.1.
+
+
+
+The diagram illustrates the call routing procedure across four network entities: Interrogating Network (RAN+CNv), Home Network (CNh), Supporting Network (RAN+CNv), and Serving Network (RAN+CNv). The sequence of messages is as follows:
+
+- 0. Outgoing call request:** Received by the Interrogating Network.
+- 1. Routing info query req.ind.:** Sent from the Interrogating Network to the Home Network.
+- 2. Routing info query resp.conf.:** Sent from the Home Network to the Interrogating Network.
+- 3. Service invocation:** A dashed box indicating a service control relationship between the Interrogating Network and the Supporting Network.
+- 4. Routing info query req.ind.:** Sent from the Interrogating Network to the Home Network.
+- 5. Routing info query req.ind.:** Sent from the Home Network to the Serving Network.
+- 6. Terminal paging:** Executed in the Serving Network.
+- 7. Routing info query resp.conf.:** Sent from the Serving Network to the Home Network.
+- 8. Routing info query resp.conf.:** Sent from the Home Network to the Interrogating Network.
+
+Notes: (Note 1) indicates the service control relationship could be invoked multiple times. (Note 2) indicates that these interfaces may not be required if the LMFn already has routing information.
+
+Sequence diagram of call routing procedure between Interrogating Network, Home Network, Supporting Network, and Serving Network. The diagram shows the flow of routing information queries and responses, including service invocation and terminal paging steps.
+
+NOTE 1 – This service control relationship could be invoked multiple times.
+
+NOTE 2 – These IFs may not be required if the LMFn already has routing information.
+
+**Figure 7.3-1/Q.1721 – Call routing**
+
+0. **Outgoing call request:** a mobile outgoing call request is received.
+
+| | |
+|------|-----------------------------------------------------------------|
+| FEA0 | – The interrogating network initiates routing query procedures. |
+|------|-----------------------------------------------------------------|
+
+1. **Routing info query req.ind.:** optionally invoked by the CCF'/SSF of the interrogating network, this flow is used to obtain from the LMFh the routing address of the supporting network if service control is to be performed.
+
+| Routing info query (Response: Success or Failure) | req.ind. |
+|----------------------------------------------------------|-----------------|
+| Called number | M |
+
+| | |
+|------|-----------------------------------------------------------------|
+| FEA1 | – Retrieve called party's supporting network's routing address. |
+|------|-----------------------------------------------------------------|
+
+2. **Routing info query resp.conf.:** this flow is used to inform the interrogating network of the called party's supporting network's routing address. The supporting network's routing address may (optionally) be used to invoke the called party's IN service features (e.g. Call Screening, Call Barring).
+
+| Routing info query | resp.conf. |
+|---------------------------------------------------------|-------------------|
+| Routing address (for called party's supporting network) | M |
+
+| | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------|
+| FEA2 | Optionally perform IN service invocation procedure. |
+| NOTE 1 – There may be additional service control interactions within the "Service Control Relationship" (schematically shown by the shaded square) encompassing the "Service Logic Invocation" information flows. The Service Control Relationship may end after the first service logic interaction or it may continue until the call is routed.
NOTE 2 – Service invocation can be from SSF in the interrogating network to SCF in the home network (possibly relayed via SCF in the interrogating network), or from the LMF in the home network.
NOTE 3 – In case service invocation is invoked from the interrogating network, information obtained from the home network in response to the routing information query will contain instruction to the serving network for the service invocation.
NOTE 4 – Service invocation can result in different scenarios, like call diversion to, for example, a fixed line, user interaction with an SRF, or other scenarios. This figure depicts only the simple call termination towards the mobile subscriber.
| |
+
+3. **IN service invocation:** this procedure may be optionally invoked.
+
+4. **Routing info query req.ind.1:** invoked by the CCF'/SSF of the interrogating network this flow is used to inquire the routing information (e.g. ITDN for the called party) from the LMF of the called party's home network.
+
+| Routing info query (Response: Success or Failure) | req.ind. |
+|----------------------------------------------------------|-----------------|
+| Called number | M |
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA4 | - – Identify called user.
- – Forward the query to the serving/visited network in order to obtain a routing number (e.g. ITDN).
|
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+---
+
+1 Conditional, if service invocation from the interrogating network.
+
+5. **Routing info query req.ind.:** this flow is used to forward the query to the LMF in the serving network to obtain the routing number (e.g. ITDN) of the user. It may (optionally) be used to invoke the service logic to page the terminal.
+
+| Routing info query (Response: Success or Failure) | req.ind. |
+|----------------------------------------------------------|-----------------|
+| IMUI | M |
+| Called number | O |
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA5 | - – Identify Called user.
- – Paging procedure (Optional Flows).
- – Assign a routing number (e.g. ITDN) for the called user.
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+6. **Terminal paging.:** this procedure is optionally performed, if necessary.
+
+7. **Routing info query resp.conf.:** this flow is used to transfer the routing number (e.g. ITDN) of the called user to the user's home network LMF.
+
+| Routing info query | resp.conf. |
+|--------------------------------------------|-------------------|
+| Routing number of called party (e.g. ITDN) | M |
+
+| | |
+|------|---------------------------------------|
+| FEA7 | – Forward routing number (e.g. ITDN). |
+|------|---------------------------------------|
+
+8. **Routing info query resp.conf.:** this flow is used to transfer the routing address/number of the called user and may also be used to transfer the result of paging (if executed).
+
+| Routing info query | resp.conf. |
+|--------------------------------------------|-------------------|
+| Routing number of called party (e.g. ITDN) | M |
+
+| | |
+|------|-----------------------------------------------------------------------------------------------------|
+| FEA8 | – Uses the routing number (e.g. ITDN) to route the call (e.g. via the PSTN) to the serving network. |
+|------|-----------------------------------------------------------------------------------------------------|
+
+## 7.4 Mobile incoming call
+
+The mobile incoming call procedure is used to terminate a call to a mobile terminal in the idle state.
+
+Assuming that the call is optimally routed (the interrogating network is not the home network):
+
+- for basic services the call is routed from the serving network to the destination through call control signalling, using the roaming number previously retrieved;
+- for advanced services the VHE applies.
+
+### 7.4.1 Initial mobile incoming call
+
+See Figure 7.4.1-1.
+
+
+
+Sequence diagram for Mobile incoming call (Figure 7.4.1-1/Q.1721). The diagram shows interactions between UIM (UIMF), MT (MCF, CCAF'), RAN+CNv (CCF', LMF), CNh (LMF), and CNs (CCF'). The sequence starts with 'Terminating call setup' from CNh to RAN+CNv at step 0. Subsequent steps include 'Terminal paging' (1), 'User authentication' (2), 'Start ciphering' (3), and 'TMUI assignment' (4). At step 5, 'VHE service invocation' occurs. At step 6, 'Setup req.ind.' is sent from RAN+CNv to MT. At step 7, 'User info req.ind.' is sent from MT to UIM. At step 8, 'User info resp.conf.' is sent from UIM to MT. At step 9, 'Setup resp.conf.' is sent from MT to RAN+CNv. Vertical dashed lines represent lifelines, and horizontal dashed lines represent time steps 0 through 9. A small note 'T11105660-00' is at the bottom right.
+
+**Figure 7.4.1-1/Q.1721 – Mobile incoming call**
+
+0. **Terminating call setup:** a call arrives at the serving system for a mobile subscriber in the idle state.
+
+| | |
+|------|------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | – Before establishing the call, the visited network validates the called party and may invoke services based on the termination attempt. |
+|------|------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **Terminal paging:** the serving system may attempt to page the MT at this time. Paging may have occurred earlier during the routing stage or may not be necessary if the MT is already on another call.
+2. **User authentication:** if authentication is required for this call attempt, it is performed.
+3. **Start ciphering:** if ciphering is required for this call attempt, it is initiated.
+4. **TMUI assignment:** if a TMUI needs to be assigned, it can be done any time after ciphering has been initiated.
+5. **VHE service invocation:** based on the subscriber profile, the visited network may invoke IN service logic. This may occur at any defined and active trigger detection point.
+
+6. **Setup req.ind.:** the CCF' proceeds to set up the call.
+
+| Setup (Response: Success or Failure) | req.ind. |
+|---------------------------------------------|-----------------|
+| UserID | M (Note) |
+| Calling Number (IMDN) | M |
+
+| | |
+|-------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA6 | - – Optionally, invoke and await completion of User info procedure.
- – Set up the call and bearer channel.
|
+| NOTE – Include either IMUI or TMUI as available. TMUI is recommended for over-the-air security. | |
+
+7. **User info req.ind.:** optionally, the MCF queries the UIMF for further information/instructions.
+
+| User info (Response: Success or Failure) | req.ind. |
+|-------------------------------------------------|-----------------|
+| Termination treatment request | O (Note) |
+
+| | |
+|------------------------------------------------------------------|----------------------------------------|
+| FEA7 | – Instruct the MCF to accept the call. |
+| NOTE – Include to request call treatment instructions from UIMF. | |
+
+8. **User info resp.conf.:** the UIMF returns the requested information to the MCF.
+
+| User info | resp.conf. |
+|----------------------------|-------------------|
+| Termination treatment info | O (Note) |
+
+| | |
+|------------------------------------------------------------------------------|---------------------------------------------------|
+| FEA8 | – Apply the indicated call termination treatment. |
+| NOTE – Include to indicate type of call termination treatment to be applied. | |
+
+9. **Setup resp.conf.:** the CCAF' reports the successful completion of call and bearer channel setup.
+
+| Setup | resp.conf. |
+|--------------|-------------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|---------|
+| FEA9 | – None. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+### 7.4.2 Additional mobile incoming call
+
+The mobile incoming additional call involves a mobile subscriber receiving a second call while already on a call, i.e. a three-way call. The procedure is performed similarly to mobile incoming calls, with the exception that paging will not be needed when adding the third party.
+
+## 7.5 Mobile call release
+
+### 7.5.1 Normal release: mobile initiated
+
+See Figure 7.5.1-1.
+
+
+
+Sequence diagram for Mobile initiated normal release. Lifelines: MT (MCF), RAN+CN (SACF, SSF/CCF'), CN, PSTN, etc. (CCF). The sequence starts at 0 with 'User initiates release'. At 1, 'Release req.ind.' is sent from MCF to SACF. At 2, 'Release req.ind.' is sent from SSF/CCF' to CCF. At 3, 'Release resp.conf.' is sent from CCF to SSF/CCF'. At 4, 'Release resp.conf.' is sent from SACF to MCF. The diagram is labeled T11105670-00.
+
+Figure 7.5.1-1/Q.1721 – Mobile initiated normal release
+
+0. **User initiates release:** the mobile subscriber releases the call.
+
+| | |
+|------|-----------------------------------|
+| FEA0 | – The MT makes a release request. |
+|------|-----------------------------------|
+
+1. **Release req.ind.:** MCF sends a release request to the SACF.
+
+| Release (Response: Success or Failure) | req.ind. |
+|----------------------------------------|----------|
+| TMUI | M |
+
+| | |
+|------|----------------------------------------------------------------------|
+| FEA1 | – Prepare to forward the release request to the originating network. |
+|------|----------------------------------------------------------------------|
+
+2. **Release req.ind.:** the SSF/CCF' in the visited network forwards the release request to the CCF in the originating network.
+
+| Release (Response: Success or Failure) | req.ind. |
+|----------------------------------------|----------|
+| TMUI | M |
+
+| | |
+|------|------------------------------------------------|
+| FEA2 | – Release resources associated with this call. |
+|------|------------------------------------------------|
+
+3. **Release resp.conf.:** the CCF in the originating network returns an acknowledgement of successful call release to the SSF/CCF' in the visited network.
+
+| Release | resp.conf. |
+|---------|------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|
+| FEA3 | – Prepare to forward the release response to the visited network. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+4. **Release resp.conf.:** the SACF in the visited network forwards the acknowledgement of successful call release to the MCF.
+
+| Release | resp.conf. |
+|---------|------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|------------------------------------------------|
+| FEA4 | – Release resources associated with this call. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+### 7.5.2 Normal release: network initiated
+
+See Figure 7.5.2-1.
+
+
+
+Sequence diagram showing network initiated normal release. Lifelines: MT (MCF), RAN+CN (SACF, SSF/CCF'), CN, PSTN, etc. (CCF). The sequence starts at step 0 with 'Release initiated' from the right. Step 1: 'Release req.ind.' from CCF to SSF/CCF'. Step 2: 'Release req.ind.' from SSF/CCF' to MCF. Step 3: 'Release resp.conf.' from MCF to SSF/CCF'. Step 4: 'Release resp.conf.' from SSF/CCF' to CCF. The diagram is labeled T11105680-00.
+
+Figure 7.5.2-1/Q.1721 – Network initiated normal release: call information flow diagram
+
+0. **Release initiated:** either the network autonomously initiates release or it receives a release request from a user in the network (e.g. wireline/non-mobile subscriber).
+
+| | |
+|------|--------------------------------------------------------------------------|
+| FEA0 | – The network prepares to make a release request to the visited network. |
+|------|--------------------------------------------------------------------------|
+
+1. **Release req.ind.:** CCF sends a release request to the SSF/CCF'.
+
+| Release (Response: Success or Failure) | req.ind. |
+|----------------------------------------|----------|
+| TMUI | M |
+
+| | |
+|------|------------------------------------------------------------------|
+| FEA1 | – Prepare to forward the release request to the mobile terminal. |
+|------|------------------------------------------------------------------|
+
+2. **Release req.ind.:** the SACF in the visited network forwards the release request to the MCF.
+
+| Release (Response: Success or Failure) | req.ind. |
+|----------------------------------------|----------|
+| TMUI | M |
+
+| | |
+|------|------------------------------------------------|
+| FEA2 | – Release resources associated with this call. |
+|------|------------------------------------------------|
+
+3. **Release resp.conf.:** the MCF returns an acknowledgement of successful call release to the SACF in the visited network.
+
+| Release | resp.conf. |
+|---------|------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|
+| FEA3 | – Prepare to forward the release response to the originating network. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+4. **Release resp.conf.:** the SACF in the visited network forwards the acknowledgement of successful call release to the originating network.
+
+| Release | resp.conf. |
+|---------|------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|------------------------------------------------|
+| FEA4 | – Release resources associated with this call. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+## 7.6 Emergency calls
+
+### 7.6.1 Emergency call origination
+
+Emergency calls should bypass normal authentication and location registration processing. Emergency calls may not require the presence of a UIM in the MT.
+
+The emergency call origination procedure is performed similarly to a mobile outgoing call with the exception that the procedures for User Authentication, Terminal Location Registration, Start Ciphering, TMUI Assignment will not need to be performed. Additionally the serving network receives the call request and attempts to set up the call once a routing number is available. The serving network may invoke VHE service at any defined and active trigger detection point. For an emergency call, this may include a translation of an emergency number into a local or regional number. Also, the geographic position of the MT may be determined at any time after the serving network receives the Setup request. Geographic position determination may occur before any VHE services are invoked.
+
+### 7.6.2 Emergency call release: network initiated
+
+The emergency call release – network initiated – procedure is performed similarly to call release – network initiated. In an emergency call, when the Public Safety Answering Point (PSAP) releases the call, the complete path to the user will be released.
+
+### 7.6.3 Emergency call release: mobile initiated
+
+The emergency call release – mobile initiated – procedure is performed similarly to call release – mobile initiated. The resources may be held when the calling user requests the call release and communication of the emergency call is suspended. This procedure is optional and the normal call release procedure (i.e. release of the complete path to the user) may also be applied. If the resources are held and the user originates the call setup afterwards, the suspended emergency call is resumed.
+
+## 7.7 Priority calls
+
+Priority calling allows a subscriber to have priority access to voice or traffic channels on call origination. This feature permits a subscriber to obtain priority access to voice or traffic channels by queueing these subscribers' originating calls when channels are not available. When a channel becomes available, the queued subscriber is served on a first come first served and a priority basis. The subscriber is assigned one of $n$ priority levels at subscription time (where $n$ has a minimum and a maximum). Priority levels are defined as 1, 2, 3, ..., $n$ , with 1 being the highest priority level and $n$ being the lowest priority level. The priority level is carried in the Subscriber Profile and is used within the RAN+CN to assign radio channels.
+
+# 8 Multimedia call and bearer control
+
+This clause covers the information flows for establishing and controlling of multimedia calls, multi-party calls, and packet data services calls including establishing access to Internet services. This clause contains two groups of services: teleservices and access to Internet services.
+
+## 8.1 Teleservice change
+
+Teleservice change procedure enables an IMT-2000 user to change the service during a call (e.g. switching from voice to data communication and vice versa) which may lead to a change of the access link to be used. From the network-to-network interface perspective, the teleservice change is to modify the bearer to allow for the bearer capability to support the change in the service type. Changes in teleservices may be initiated by either the originating user or the terminating user. However, an end-to-end (mobile-to-mobile) information flow for the teleservice change will cover both cases as shown in Figure 8.1-1.
+
+
+
+```
+
+sequenceDiagram
+ participant MT_A as MT (CCAF')
+ participant RAN_A as RAN+CN (Party A) (CCF'/SSF)
+ participant RAN_B as RAN+CN (Party B) (CCF'/SSF)
+ participant MT_B as MT (CCAF')
+
+ Note left of MT_A: 0 User requests teleservice change
+ MT_A->>RAN_A: 1 Teleservice change req.ind.
+ RAN_A->>RAN_B: 2 Teleservice change req.ind.
+ RAN_B->>MT_B: 3 Teleservice change req.ind.
+ MT_B->>RAN_B: 4 Teleservice change resp.conf.
+ RAN_B->>RAN_A: 5 Teleservice change resp.conf.
+ RAN_A->>MT_A: 6 Teleservice change resp.conf.
+
+```
+
+T11105690-00
+
+Sequence diagram for Teleservice change procedure showing message flow between MT (CCAF'), RAN+CN (Party A) (CCF'/SSF), RAN+CN (Party B) (CCF'/SSF), and MT (CCAF').
+
+Figure 8.1-1/Q.1721 – Teleservice change
+
+0. **User requests teleservice change:** the user requests teleservice (access link) change.
+
+| | |
+|------|-----------------------------------------|
+| FEA0 | – Request for change in the connection. |
+|------|-----------------------------------------|
+
+1. **Teleservice change req.ind.:** is used to request establishment of a connection.
+
+| Teleservice change (Report: Success/Failure) | req.ind. |
+|-----------------------------------------------------|-----------------|
+| Call ID | M |
+| Teleservice type | M |
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | - – Interact with radio resource management to adjust the access link as requested.
- – Send request for teleservice change to inform other call party(ies).
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+2. **Teleservice change req.ind.:** is issued by the CCF/SSF to make the teleservice change request.
+
+| Teleservice change (Report: Success/Failure) | req.ind. |
+|-----------------------------------------------------|-----------------|
+| Call ID | M |
+| Teleservice type | M |
+
+| | |
+|------|------------------------------------|
+| FEA2 | – Send teleservice change request. |
+|------|------------------------------------|
+
+3. **Teleservice change req.ind.:** is to request Party B network for teleservice change.
+
+| Teleservice change (Response: Success or Failure) | req.ind. |
+|----------------------------------------------------------|-----------------|
+| Call ID | M |
+| Teleservice type | M |
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA3 | - – Interact with radio resource management for the access link adjustment.
- – Respond to confirm teleservice (access link) change.
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+4. **Teleservice change resp.conf.:** is issued by the CCAF to respond to the teleservice change request.
+
+| Teleservice change | resp.conf. |
+|---------------------------|-------------------|
+| Result | M |
+
+| | |
+|------|--------------------------------------------------------------------------------------------|
+| FEA4 | Respond to Party A network to confirm connection establishment for the teleservice change. |
+|------|--------------------------------------------------------------------------------------------|
+
+5. **Teleservice change resp.conf.:** is used to confirm that the connection has been established.
+
+| Teleservice change | resp.conf. |
+|---------------------------|-------------------|
+| Result | M |
+
+| | |
+|------|-----------------------------------|
+| FEA5 | Connect with the new access link. |
+|------|-----------------------------------|
+
+6. **Teleservice change resp.conf.:** is used to confirm that the connection has been established.
+
+| Teleservice change | resp.conf. |
+|--------------------|------------|
+| Result | M |
+
+| | |
+|------|-------|
+| FEA6 | None. |
+|------|-------|
+
+## 8.2 Add media during a call (mobile user originating)
+
+The purpose of this procedure is to add a media component to an active call. It is supposed that the adding of the media component is related to an allocation into the call of a new bearer dedicated to support it. See Figure 8.2-1.
+
+
+
+```
+
+sequenceDiagram
+ participant MT as MT (CCAF')
+ participant RAN_A as RAN+CN (Party A) (SSF/CCF')
+ participant RAN_B as RAN+CN (Party B) (SSF/CCF')
+ participant MT_end as MT (CCAF')
+
+ Note left of MT: User requests additional media
+ MT->>RAN_A: Add media req.ind.
+ RAN_A->>RAN_B: Add media req.ind.
+ RAN_B->>MT_end: Add media req.ind.
+ MT_end->>RAN_B: Add media resp.conf.
+ RAN_B->>RAN_A: Add media resp.conf.
+ RAN_A->>MT: Add media resp.conf.
+
+```
+
+T11105700-00
+
+Sequence diagram for adding media to a call (mobile originating). The diagram shows four lifelines: MT (CCAF'), RAN+CN (Party A) (SSF/CCF'), RAN+CN (Party B) (SSF/CCF'), and MT (CCAF'). The sequence of messages is: 0. User requests additional media (external to MT); 1. Add media req.ind. (MT to RAN+CN Party A); 2. Add media req.ind. (RAN+CN Party A to RAN+CN Party B); 3. Add media req.ind. (RAN+CN Party B to MT); 4. Add media resp.conf. (MT to RAN+CN Party B); 5. Add media resp.conf. (RAN+CN Party B to RAN+CN Party A); 6. Add media resp.conf. (RAN+CN Party A to MT).
+
+Figure 8.2-1/Q.1721 – Add media to a call (mobile originating)
+
+0. **User requests additional media:** the mobile user wishes to add a media component. It specifies which supplementary service is wanted.
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | - – Request for an additional medium.
- – Send request for connection of access link.
|
+|------|----------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **Add media req.ind.:** is to transport the information that the user wishes to add a media component to the active call. It specifies which supplementary teleservice is wanted.
+
+| Add media (Response: Success or Failure) | req.ind. |
+|------------------------------------------|----------|
+| Call ID | M |
+| Medium type | M |
+
+| | |
+|------|--------------------------------------------------------------------------------------------------------|
+| FEA1 | – Check for service authorization of Party A (internal operation). Request downstream for "Add media". |
+|------|--------------------------------------------------------------------------------------------------------|
+
+2. **Add media req.ind.:** is to request for an additional media component to the active call.
+
+| Add media (Response: Success or Failure) | req.ind. |
+|-------------------------------------------------|-----------------|
+| Call ID | M |
+| Medium type | M |
+
+| | |
+|------|-----------------------------------------------------------------------------------------------------------|
+| FEA2 | – Check for service authorization of Party B (internal).
– Send request for connection of access link. |
+|------|-----------------------------------------------------------------------------------------------------------|
+
+3. **Add media req.ind.:** is to transport the information that the user wishes to add a media component to the active call. It specifies which supplementary teleservice is wanted.
+
+| Add media (Response: Success or Failure) | req.ind. |
+|-------------------------------------------------|-----------------|
+| Call ID | M |
+| Medium type | M |
+
+| | |
+|------|-------------------------------------------------------------------------------------|
+| FEA3 | – Check for service authorization.
– Send request for connection of access link. |
+|------|-------------------------------------------------------------------------------------|
+
+4. **Add media resp.conf.:** is to inform that actions are being taken for add media request.
+
+| Add media | resp.conf. |
+|------------------|-------------------|
+| Result | M |
+
+| | |
+|------|-------------------|
+| FEA4 | – Relay response. |
+|------|-------------------|
+
+5. **Add media resp.conf.:** is to inform that actions are being taken for add media request.
+
+| Add media | resp.conf. |
+|------------------|-------------------|
+| Result | M |
+
+| | |
+|------|-------------------|
+| FEA5 | – Relay response. |
+|------|-------------------|
+
+6. **Add media resp.conf.:** is to inform that actions are being taken for add media request.
+
+| Add media | resp.conf. |
+|------------------|-------------------|
+| Result | M |
+
+| | |
+|------|----------------------------------------------------|
+| FEA6 | – Request for the establishment of bearer channel. |
+|------|----------------------------------------------------|
+
+## 8.3 Drop media from an active call
+
+This procedure aims to remove a media component from an active call. It can either be user decided or network decided (if needed resources are no more available and if it concerns a "low class" call). First case is shown here. See Figure 8.3-1.
+
+
+
+Sequence diagram showing the interaction for dropping media from a multimedia call. Lifelines: MT (CCAF'), RAN+CN (Party A) (CCF/SSF), RAN+CN (Party B) (CCF/SSF), and MT (CCAF'). The sequence starts with 'User requests drop media' at time 0. At time 1, 'Drop media req.ind.' is sent from MT to RAN+CN (Party A). At time 2, 'Drop media req.ind.' is forwarded from RAN+CN (Party A) to RAN+CN (Party B). At time 3, 'Drop media req.ind.' is sent from RAN+CN (Party B) to MT. At time 4, 'Drop media resp.conf.' is sent from MT to RAN+CN (Party B). At time 5, 'Drop media resp.conf.' is forwarded from RAN+CN (Party B) to RAN+CN (Party A). At time 6, 'Drop media resp.conf.' is sent from RAN+CN (Party A) to MT. The diagram is labeled T11105710-00.
+
+Figure 8.3-1/Q.1721 – Drop media from a multimedia call (mobile originating)
+
+0. **User requests drop media:** is the request from the user to remove a media component.
+
+| | |
+|------|--------------------------------------------------------------------------------------------------------------|
+| FEA0 | – Send a request for dropping the media component from the corresponding call control entity in the network. |
+|------|--------------------------------------------------------------------------------------------------------------|
+
+1. **Drop media req.ind.:** is used to request the "drop media" operation.
+
+| Drop media (Response: Success or Failure) | req.ind. |
+|-------------------------------------------|----------|
+| Call ID | M |
+| Media ID | M |
+
+| | |
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | – Identifies the call and the corresponding medium to be dropped.
– Forward the "drop media" request to the distant call control entity, Party B's serving network. |
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+2. **Drop media req.ind.:** is to forward the "drop media" request to the core network of other call party to modify the call (removing the concerned bearer) in the part under their responsibility.
+
+| Drop media (Response: Success or Failure) | req.ind. |
+|-------------------------------------------|----------|
+| Call ID | M |
+| Media ID | M |
+
+| | |
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA2 | - – Identifies the call and the corresponding medium to be dropped.
- – Send a request to drop the medium to the access network.
- – Drop the corresponding media component.
|
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+3. **Drop media req.ind.:** is to forward the "drop media" request to the access network to modify the call by removing the medium under its control.
+
+| Drop media (Response: Success or Failure) | req.ind. |
+|--------------------------------------------------|-----------------|
+| Call ID | M |
+| Media ID | M |
+
+| | |
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA3 | - – Identifies the call and the corresponding medium to be dropped.
- – Interact with the radio resource management elements.
- – Drop the corresponding media component.
|
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+4. **Drop media resp.conf.:** is to confirm that both the remote access network and the core network have correctly removed the media component and its related bearer(s).
+
+| Drop media | resp.conf. |
+|-------------------|-------------------|
+| Result | M |
+
+| | |
+|------|---------------------------------------------------|
+| FEA4 | – Drop media component and its associated bearer. |
+|------|---------------------------------------------------|
+
+5. **Drop media resp.conf.:** is to confirm that both the remote access network and the core network have correctly removed the media component and its related bearer(s).
+
+| Drop media | resp.conf. |
+|-------------------|-------------------|
+| Result | M |
+
+| | |
+|------|---------------------------------------------------|
+| FEA5 | – Drop media component and its associated bearer. |
+|------|---------------------------------------------------|
+
+6. **Drop media resp.conf.:** is to forward the result to the originating call control FE.
+
+| Drop media | resp.conf. |
+|-------------------|-------------------|
+| Result | M |
+
+| | |
+|------|----------------------------------------------------|
+| FEA6 | – Request release of the media associated bearers. |
+|------|----------------------------------------------------|
+
+## 8.4 Point-to-multipoint call
+
+### 8.4.1 Party addition (mobile-to-mobile)
+
+In a two-party call, each party can request the addition of another party to the call. Party A will become the root of the type 1 network connection (i.e. point-to-point connection) requesting that a new mobile Party C be added to the call. The old type 1 network connection will become a type 2 network connection (i.e. point-to-multipoint connection) with both root and leaf parties being present in the configuration. The request for the "add\_party" operation also requires that a "teleservice change" or "notification" procedure be carried out for the call in progress between parties on the call. This subclause addresses both root and leaf initiated party addition procedures.
+
+#### 8.4.1.1 Party addition (root initiated)
+
+Figure 8.4.1-1 shows the information flow diagram for a root initiated party addition. Party C is added to the call already under way between Party A and Party B. For the new party, Party C, in the destination visited network, a mobile incoming call procedure is applied as part of the "connection establishment" common procedure.
+
+
+
+The diagram illustrates the information flow for a root initiated party addition. It features six vertical lifelines representing different entities: MT (Party A), RAN+CN (Party A), RAN+CN (Party B), MT (Party B), RAN+CN (Party C), and MT (Party C). The interactions are numbered 0 to 4:
+
+- 0 Add party:** Initiated by the user at MT (Party A).
+- 1 Add party req.ind.:** A request is sent from MT (Party A) to RAN+CN (Party A).
+- 2 Teleservice change/Notification:** A message is sent from RAN+CN (Party A) to MT (Party B).
+- 3 Call routing:** A message is sent from RAN+CN (Party B) to RAN+CN (Party C).
+- 4 Add party resp.conf.:** A response is sent from RAN+CN (Party A) to MT (Party A).
+
+T11105720-00
+
+Sequence diagram for Party addition (root initiated) showing interactions between MT (Party A), RAN+CN (Party A), RAN+CN (Party B), MT (Party B), RAN+CN (Party C), and MT (Party C). The sequence includes steps: Add party, Add party req.ind., Teleservice change/Notification, Call routing, and Add party resp.conf.
+
+Figure 8.4.1-1/Q.1721 – Party addition (root initiated)
+
+0. **Add party:** is initiated by the user Party A to add another party, Party C, to an ongoing call with Party B.
+
+| | |
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | - – Send add party request.
- – A teleservice change request is made for the parties involved in the call.
|
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **Add party req.ind.:** is to initiate the addition of a party to an existing connection.
+
+| Add party (Report: Success or Failure) | req.ind. |
+|----------------------------------------|----------|
+| Call ID | M |
+| Called number | M |
+| End point reference | M |
+
+| | |
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | - – Identify the user to be added.
- – Select and reserve outgoing resources.
- – Send setup request to initiate call and connection establishment.
|
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+2. **Teleservice change/Notification:** is to request change of the service (e.g. from point-to-point to point-to-multipoint) and process addition of access link (if needed).
+
+| | |
+|------|--------------------------------------------------------------------------------|
+| FEA2 | – Request change of service (e.g. from point-to-multipoint to point-to-point). |
+|------|--------------------------------------------------------------------------------|
+
+3. **Call routing:** is used to request establishment of a call to be followed by a bearer connection.
+
+4. **Add party resp.conf.:** is used to acknowledge that the add party request was successful.
+
+| Add party | resp.conf. |
+|---------------------|-------------------|
+| Call ID | M |
+| End point reference | M |
+
+| | |
+|------|-----------------------------------------------------------------------------------------------------------------------------------------|
+| FEA4 | - – Send add party confirmation.
- – Request establishment of bearer channel(s).
|
+|------|-----------------------------------------------------------------------------------------------------------------------------------------|
+
+#### **8.4.1.2 Party addition (leaf initiated)**
+
+Figure 8.4.1-2 shows the information flow diagram for a leaf initiated party addition. Party D is to be added by Party C to the call that is already under way between Party A, Party B and Party C. Party C notifies the root party, Party A, for adding Party D to the call. From this point on, the root party CN takes over and performs a "party addition (root initiated)" procedure.
+
+
+
+```
+
+sequenceDiagram
+ participant MT_A as MT (Party A) CCAF'
+ participant RAN_A as RAN+CNv (Party A) CCF'/SSF
+ participant MT_B as MT (Party B) CCAF'
+ participant RAN_B as RAN+CNv (Party B) CCF'/SSF
+ participant MT_C as MT (Party C) CCAF'
+ participant RAN_C as RAN+CNv (Party C) CCF'/SSF
+ participant MT_D as MT (Party D) CCAF'
+ participant RAN_D as RAN+CNv (Party D) CCF'/SSF
+
+ Note over MT_C, RAN_C: 0 Add party request
+ MT_C->>RAN_C:
+ Note over RAN_C, RAN_A: 1 Add party req.ind.
+ RAN_C->>RAN_A:
+ Note over RAN_A, MT_B: 2 Add party req.ind.
+ RAN_A->>MT_B:
+ Note over MT_B, MT_A: 3 Add party req.ind.
+ MT_B->>MT_A:
+ Note over MT_A, MT_B: 4 Add party resp.conf.
+ MT_A->>MT_B:
+ rect rgb(255, 255, 255)
+ Note over MT_A, RAN_D: 5 Add party (root initiated)
+ end
+ Note over MT_B, RAN_C: 6 Add party resp.conf.
+ MT_B->>RAN_C:
+
+```
+
+Sequence diagram for 'Party addition (leaf initiated)'. The diagram shows interactions between MTs (Party A, B, C, D) and RAN+CNv (Party A, B, C, D) via CCAF' and CCF'/SSF entities. The sequence starts at step 0 with Party C sending an 'Add party request' to Party D. At step 1, Party C sends an 'Add party req.ind.' to Party A. At step 2, Party A sends an 'Add party req.ind.' to Party B. At step 3, Party B sends an 'Add party req.ind.' to Party A. At step 4, Party A sends an 'Add party resp.conf.' to Party B. At step 5, a box labeled 'Add party (root initiated)' spans across all parties. At step 6, Party B sends an 'Add party resp.conf.' to Party C. The diagram is labeled T11105730-00 at the bottom right.
+
+**Figure 8.4.1-2/Q.1721 – Party addition (leaf initiated)**
+
+The information flows, information elements and functional entity actions related to this procedure are described below in the same order as the flows are shown in Figure 8.4.1-2.
+
+0. **Add party request:** is initiated by the user Party C to add another party, Party D, to an active call with Parties A and B.
+
+1. **Add party req.ind.:** is to initiate the addition of a party to an existing connection.
+
+| Add party (Report: Success or Failure) | req.ind. |
+|-----------------------------------------------|-----------------|
+| Call ID | M |
+| Called number | M |
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | - – Send an add party request to the root party.
- – Select and reserve outgoing resources.
|
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------|
+
+2. **Add party req.ind.:** is to initiate the addition of a party to an existing connection.
+
+| Add party (Report: Success or Failure) | req.ind. |
+|-----------------------------------------------|-----------------|
+| Call ID | M |
+| Called number | M |
+| End point reference | M |
+
+| | |
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA2 | - – Identify the new party to be added.
- – Notify all call parties (except the requesting party) of the party addition.
- – Select and reserve outgoing resources.
- – Send setup request to initiate call and connection establishment.
- – Provide end point reference.
|
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+3. **Add party req.ind.:** (optional) is to initiate the addition of a party to an existing connection.
+
+| Add party (Response: Neither Success nor Failure) | req.ind. |
+|----------------------------------------------------------|-----------------|
+| Call ID | M |
+| Called number | M |
+| End point reference | M |
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA3 | - – Identify the new party to be added.
- – Acknowledge the request to add party.
- – Initiate the add party procedure.
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+4. **Add party resp.conf.:** is used to acknowledge the add party request.
+
+| Add party | resp.conf. |
+|------------------|-------------------|
+| Result | M |
+
+| | |
+|------|-----------------------------------------------------------|
+| FEA4 | |
+|------|-----------------------------------------------------------|
+
+5. **Party Addition (root initiated):** is used to request addition of a party by the root party of an ongoing call.
+
+6. **Add party resp.conf.:** is used to acknowledge that the add party request was successful.
+
+| Add party | resp.conf. |
+|-----------|------------|
+| Result | M |
+
+| | |
+|------|---------|
+| FEA6 | – None. |
+|------|---------|
+
+### 8.4.2 Party dropping
+
+A leaf party may be dropped from an existing point-to-multipoint connection by a request from either the root party or the leaf party itself.
+
+#### 8.4.2.1 Party dropping (root party initiated)
+
+The root party (Party A) may request that a leaf party (Party C) be dropped from the connection. In this procedure, the resources between Party C and the core network are released normally by trigger of the core network. See Figure 8.4.2-1.
+
+
+
+```
+
+sequenceDiagram
+ participant MT_A as MT (Party A)
+ participant RAN_A as RAN+CNv (Party A)
+ participant RAN_B as RAN+CNv (Party B)
+ participant MT_B as MT (Party B)
+ participant RAN_C as RAN+CNv (Party C)
+ participant MT_C as MT (Party C)
+
+ Note left of MT_A: 0
+ MT_A->>RAN_A: Drop party request
+ Note left of RAN_A: 1
+ RAN_A->>RAN_C: Drop party req.ind.
+ Note left of RAN_C: 2
+ RAN_C->>MT_C: Call release
+ Note left of MT_C: 3
+ RAN_C->>RAN_A: Drop party resp.conf.
+ Note left of RAN_A: 4
+ RAN_A->>MT_A: Drop party resp.conf.
+ Note left of MT_A: 5
+ Note right of MT_A: Teleservice change
+ Note left of MT_A: 6
+
+```
+
+T111105740-00
+
+Sequence diagram for Party dropping (root party initiated). The diagram shows the interaction between MT (Party A), RAN+CNv (Party A), RAN+CNv (Party B), MT (Party B), RAN+CNv (Party C), and MT (Party C). The sequence starts with a 'Drop party request' from MT (Party A) to RAN+CNv (Party A). RAN+CNv (Party A) sends a 'Drop party req.ind.' to RAN+CNv (Party C). RAN+CNv (Party C) sends a 'Call release' to MT (Party C). RAN+CNv (Party C) sends a 'Drop party resp.conf.' to RAN+CNv (Party A). RAN+CNv (Party A) sends a 'Drop party resp.conf.' to MT (Party A). Finally, a 'Teleservice change' is indicated between MT (Party A) and RAN+CNv (Party A).
+
+**Figure 8.4.2-1/Q.1721 – Party dropping (root party initiated)**
+
+0. **Drop party request:** is the user's request to drop a call party.
+
+| | |
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | - – Identify the party to be dropped.
- – Verify the states of all other leaf parties associated with the connection, if necessary.
|
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **Drop party req.ind.:** is to initiate the detachment of a party from an existing connection.
+
+| Drop party (Response: Success or Failure) | req.ind. |
+|--------------------------------------------------|-----------------|
+| Call ID | M |
+| End point reference | M |
+| Cause | M |
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | - – Identify the requesting user.
- – Acknowledge that the requesting user is root.
- – Identify the party to be dropped.
- – Verify the states of all other leaf parties associated with this connection.
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+2. **Drop party req.ind.:** is to initiate the detachment of a party from an existing connection.
+
+| Drop party (Response: Success or Failure) | req.ind. |
+|--------------------------------------------------|-----------------|
+| Call ID | M |
+| End point reference | M |
+| Cause | M |
+
+| | |
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | - – Identify the requesting user.
- – Acknowledge that the requesting user is root.
- – Identify the party to be dropped.
- – Verify the states of all other leaf parties associated with this connection.
- – Initiate Release call procedure.
|
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+3. **Release call:** (network initiated) procedure is used to request the drop of a party from the call.
+
+| | |
+|------|------------------------------------------|
+| FEA3 | – Send drop party/release call response. |
+|------|------------------------------------------|
+
+4. **Drop party resp.conf.:** is used to notify that the drop party request was successful.
+
+| Drop party | resp.conf. |
+|-------------------|-------------------|
+| Cause | O (Note) |
+
+| | |
+|----------------------------------------------------------------------------|-------------------------------------------|
+| FEA4 | – Relay drop party confirmation response. |
+| NOTE – Send information on the cause of release of the party if available. | |
+
+5. **Drop party resp.conf.:** is used to notify that the drop party request was successful.
+
+| Drop party | resp.conf. |
+|-------------------|-------------------|
+| Cause | O (Note) |
+
+| | |
+|----------------------------------------------------------------------------|---------------------------------|
+| FEA5 | – Send drop party confirmation. |
+| NOTE – Send information on the cause of release of the party if available. | |
+
+6. **Teleservice change:** procedure is a request for the possible change of teleservice for Party A and Party B, changing from point-to-multipoint to point-to-point.
+
+| | |
+|------|--------------------------------------------------------------------------------|
+| FEA6 | – Request change of service (e.g. from point-to-multipoint to point-to-point). |
+|------|--------------------------------------------------------------------------------|
+
+#### **8.4.2.2 Party dropping (a leaf party initiated)**
+
+On receipt of release request from a leaf party to be dropped (Party C), core network notifies the root party (Party A) that the leaf party has dropped by sending drop party request. See Figure 8.4.2-2.
+
+
+
+Sequence diagram for Party dropping (a leaf party initiated). The diagram shows interactions between MT (Party A), RAN+CNv (Party A), RAN+CNv (Party B), MT (Party B), RAN+CNv (Party C), and MT (Party C). The sequence starts with a 'Release call' from RAN+CNv (Party C) to MT (Party C) at time 0. At time 1, a 'Call release' message is sent from RAN+CNv (Party C) to RAN+CNv (Party B). At time 2, a 'Drop leaf party req.ind.' message is sent from RAN+CNv (Party B) to RAN+CNv (Party A). At time 3, another 'Drop leaf party req.ind.' message is sent from RAN+CNv (Party A) to MT (Party A). At time 4, a 'Teleservice change' message is sent from MT (Party A) to MT (Party B). The diagram is labeled T11105750-00.
+
+**Figure 8.4.2-2/Q.1721 – Party dropping (a leaf party initiated)**
+
+0. **Call release:** is initiated from a leaf party requesting to be dropped from the call/connection.
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | - – Start mobile call release procedure.
- – Identify the leaf party (requesting party) to be dropped.
- – Send a drop party request to the root party's network.
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **Call release:** procedure is to release the call between the dropping leaf party and the remaining parties in the call.
+
+| | |
+|------|------------------------------------------------------------------|
+| FEA1 | – Send a drop party request to the root party's mobile terminal. |
+|------|------------------------------------------------------------------|
+
+2. **Drop party req.ind.:** is sent to notify the detachment of a leaf party from an existing connection.
+
+| Drop party (Response: Neither Success nor Failure) | req.ind. |
+|----------------------------------------------------|----------|
+| Call ID | M |
+| End point reference | M |
+| Cause | M |
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA2 | - – Identify the detached leaf party based on end point reference.
- – Verify the states of all other leaf parties associated with the connection, if necessary.
- – Send drop party indication.
|
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+3. **Drop party req.ind.:** is sent to notify the detachment of a leaf party from an existing connection.
+
+| Drop party (Response: Neither Success nor Failure) | req.ind. |
+|-----------------------------------------------------------|-----------------|
+| Call ID | M |
+| End point reference | M |
+| Cause | M |
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA3 | - – Identify the detached leaf party based on end point reference.
- – Verify the states of all other leaf parties associated with the connection, if necessary.
- – Send drop party indication.
|
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+4. **Teleservice change:** (optional) is to process a change of teleservices for the remaining parties in the call.
+
+| | |
+|------|--------------------------------------------------------------------------------|
+| FEA4 | – Request change of service (e.g. from point-to-multipoint to point to-point). |
+|------|--------------------------------------------------------------------------------|
+
+## 8.5 Access to Internet services
+
+The access to Internet services enables a roaming IMT-2000 subscriber to initiate a data service session in a visited Core Network (CN). Once the data service session has been established, the subscriber will be able to roam into the next visited CN without any interruption in the data service session. When starting a data service session, the subscriber's mobile terminal may have one or several public IP addresses, that was permanently allocated to it by the home CN, or a public IP address (one or several) may be dynamically allocated to it by the home CN or by the visited CN. The routing context in the IMT-2000 network will be established when the session is initiated and it will be updated whenever the mobile terminal roams into the next visited CN.
+
+The procedures described in this subclause are mandatory when roaming between IMT-2000 networks with different core network architectures (i.e. from different IMT-2000 family members). Roaming between networks implemented using the same family member may use family-member specific procedures.
+
+### 8.5.1 Packet data service session establishment
+
+To access packet data services, the roaming mobile terminal will register with the visiting IMT-2000 network by employing common authentication and terminal registration procedures, and requesting access to packet data facilities. The mobile terminal will register for use of packet data resources upon gaining access to packet data facilities. The IMT-2000 architecture will allow for separation of LMF (and associated AMF) capabilities that pertain to access facilities and LMFp (and associated AMFp) capabilities that pertain to the packet data services.
+
+Figure 8.5.1-1 shows the information flow diagram for this procedure. Steps 4-7 may be repeated in order to support multiple data sessions from the same mobile terminal.
+
+
+
+Sequence diagram showing packet data session establishment between MT (MCF, PSCAF), RAN+CNv (PSCF, LMFp), and CNh (LMF, LMFp). The sequence includes: 0. Data service request (MT to PSCAF), 1. Terminal registration and authentication (dashed box), 2. Data service req.ind. (PSCAF to PSCF), 3. Advertisement req.ind. (PSCF to PSCAF), 4. Data session req.ind. (PSCAF to PSCF), 5. Tunnel-connection req.ind. (PSCF to LMFp), 6. Tunnel-connection resp.conf. (LMFp to PSCF), 7. Data session resp.conf. (PSCF to PSCAF).
+
+Figure 8.5.1-1/Q.1721 – Packet data session establishment
+
+0. **Data service request:** the user initiates a packet data service session.
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------|
+| FEA0 | – Request establishment of a data service session, preceded by terminal registration and authentication. |
+|------|----------------------------------------------------------------------------------------------------------|
+
+1. **Terminal registration and authentication:** is required if not already done.
+
+2. **Data service req.ind.:** is to initiate a data service session in the visited network by requesting the service.
+
+| Data service (Response: Neither Success nor Failure) | req.ind. |
+|------------------------------------------------------|----------|
+| User ID | M |
+| Service type (data) | M |
+
+| | |
+|------|-----------------------------------------------------------------------------------------------------------|
+| FEA2 | – Employs the link layer procedure to establish an access link to be followed by "advertisement" request. |
+|------|-----------------------------------------------------------------------------------------------------------|
+
+3. **Advertisement req.ind.:** is for the flow to the terminal to request establishment of a data session when a new network access identifier (NAI) is detected.
+
+| Advertisement (Response: Neither Success nor Failure) | req.ind. |
+|-------------------------------------------------------|----------|
+| IP address (PSCF) | M |
+| IP address (PSCF-Public) | M (Note) |
+| Challenge value | M |
+| NAI (PSCF) | M |
+
+| | |
+|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA3 | - – Respond to the advertisement with a Data Session request if it detects a new PSCF NAI.
- – Specify a well-known UDP port and the IP address of the PSCF as a destination for this information.
|
+| NOTE – This IP address is the address of the foreign agent (e.g. it is used as the tunnel termination point seen from the PSGCF). | |
+
+4. **Data session req.ind.:** is sent from the PSCAF to the PSCF in the visited network over the established access link to request the establishment of a new data session2.
+
+| Data session (Response: Success or Failure) | req.ind. |
+|----------------------------------------------------|-----------------|
+| Session ID | O (Note 1) |
+| NAI (MT) | M |
+| NAI (PSCFpv) | M |
+| IP address (MT) | O (Note 2) |
+| IP address (PSCF Public) | M |
+| Service discriminator | O (Note 3) |
+| Challenge value (from PSCF) | M |
+| Challenge response | M |
+| Encapsulation method | M |
+| Data session lifetime | M |
+
+| | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA4 | - – Determine address of LMFp based on service discriminator.
- – Request the establishment of a tunnel-connection for this data session.
- – May reduce the proposed data session lifetime before forwarding this information to the LMFp.
|
+| NOTE 1 – If it is a case of multiple session.
NOTE 2 – Static assignment if the IP address is static and permanent, else dynamic assignment.
NOTE 3 – The LMFp may need the service discriminator for authorization purposes. | |
+
+5. **Tunnel-connection req.ind.:** is from the visited LMFp to the mobile terminal's home LMFp to authenticate and authorize the visiting mobile terminal to use the packet data services in the visited network.
+
+| Tunnel-connection (Response: Success or Failure) | req.ind. |
+|---------------------------------------------------------|-----------------|
+| NAI (MT) | M |
+| NAI (PSCFpv) | M |
+| NAI (PSCFv) | M |
+| IP address (MT) | O (Note 1) |
+| IP address (PSCF Public) | M |
+| Service discriminator | O (Note 2) |
+| Challenge value (from PSCF) | M |
+
+2 Not to confuse the mobile terminal "Registration" procedure with the registration to establish data session, the name "Data Session" was chosen to this flow.
+
+| Tunnel-connection (Response: Success or Failure) | req.ind. |
+|---------------------------------------------------------|-----------------|
+| Challenge response | M |
+| Encapsulation method | M |
+| Data session lifetime | M |
+
+| | |
+|-----------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA5 | - – Determine PSGCF based on service discriminator.
- – Authenticate the mobile terminal by using the challenge value, challenge response and the secret that it shares with its mobile terminal.
- – May allocate an IP address to the mobile terminal or it may decide that the PSGCF should allocate this address. As requested by the tunnel-connection req.ind., the PSGCF may be dynamically allocated, or it may have been already statically pre-allocated to the mobile terminal.
- – If the PSGCF is dynamically allocated, then the home LMFp may either allocate it in the home network or the home LMFp may decide that the visited network should allocate the PSGCF.
- – May also generate a set of security keys and security parameter indices (SPIs) that will be distributed to the mobile terminal, visited PSCF, and PSGCF to support encryption and security associations between these entities.
- – Employ the shared secrets it shares with the PSCAF, home PSGCF and the visited LMFp.
- – May also reduce the proposed data session lifetime before forwarding this information to its PSGCF or the visited LMFp.
- – Return the tunnel-connection response to the visited LMFp indicating that the PSGCF in the visited network should be allocated.
|
+| NOTE 1 – Static IP address assignment if the IP address is static and permanent, else dynamic assignment. | |
+| NOTE 2 – The LMFp may need the service discriminator for authorization purpose. | |
+
+6. **Tunnel-connection resp.conf.:** is sent from the mobile terminal's home LMFp to the visited LMFp to authorize the packet data service for the mobile terminal in the visited network.
+
+| Information elements | resp.conf. |
+|------------------------------------------------------|-------------------|
+| Result (PSGCF allocation indication) | M |
+| IP address (PSGCF public) | M |
+| IP address (MT) included if assigned by home network | O (Note) |
+| Data session lifetime | M |
+| Security information | M |
+
+| | |
+|-------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA6 | - – Respond to confirm the establishment of the tunnel connection.
- – Send result for establishment of the data session.
|
+| NOTE – IP address may not be required if no new assignment by the home network has taken place. | |
+
+7. **Data session resp.conf.:** is a response to a request for establishment of a new data session.
+
+| Registration | resp.conf. |
+|---------------------------|-------------------|
+| Session ID | O (Note) |
+| Result (success or fail) | M |
+| IP address (PSGCF public) | M |
+| IP address (MT) | M |
+| Security information | M |
+| Session lifetime | M |
+
+| | |
+|----------------------------------------|------------------------------------------------------------|
+| FEA7 | Continues with the data session, no further action needed. |
+| NOTE – If supplied by PSCAF in flow 4. | |
+
+### 8.5.2 Roaming during an established packet data session
+
+When roaming into the next visited network, a PSGCF in the anchor network has already been assigned to the mobile terminal. The anchor network may be either the home network or the visited network where the data session was initiated. The mobile terminal may register with the next visiting network by employing common authentication and terminal registration procedures. By invoking the radio resource management (RRM) procedure, the mobile terminal will establish an access link with the PSCF in the next visited network. Since the advertised PSCF NAI address is different than the current one, the PSCAF will start a new "packet data service session establishment" procedure as shown in Figure 8.5.2-1.
+
+
+
+```
+
+sequenceDiagram
+ participant MT as MT (MCF, PSCAF)
+ participant RAN_CNv as RAN+CNv (PSCF, LMFp)
+ participant CNpv as CNpv (LMFp)
+ participant CNh as CNh (LMF, LMFp)
+ participant CNa as CNa (LMFp)
+
+ Note over MT, RAN_CNv: 0 Data service request
+ MT->>RAN_CNv:
+ rect rgb(255, 255, 255)
+ Note over MT, CNh: 1 Terminal registration and authentication
+ end
+ Note over MT, RAN_CNv: 2 Data service req.ind.
+ MT->>RAN_CNv:
+ Note over MT, RAN_CNv: 3 Advertisement req.ind.
+ RAN_CNv->>MT:
+ Note over MT, RAN_CNv: 4 Data session req.ind.
+ MT->>RAN_CNv:
+ Note over RAN_CNv, CNh: 5 Tunnel-connection req.ind.
+ RAN_CNv->>CNh:
+ Note over CNh, CNa: 6 Tunnel-connection req.ind.
+ CNh->>CNa:
+ Note over CNh, CNa: 7 Tunnel-connection resp.conf.
+ CNa->>CNh:
+ Note over RAN_CNv, CNh: 8 Tunnel-connection resp.conf.
+ CNh->>RAN_CNv:
+ Note over MT, RAN_CNv: 9 Data session resp.conf.
+ RAN_CNv->>MT:
+ rect rgb(255, 255, 255)
+ Note over RAN_CNv, CNpv: 10 Clear old connection req.ind.
+ RAN_CNv->>CNpv:
+ Note over RAN_CNv, CNpv: 11 Clear old connection resp.conf.
+ CNpv->>RAN_CNv:
+ end
+
+```
+
+Sequence diagram showing roaming during an established data session. Lifelines: MT (MCF, PSCAF), RAN+CNv (PSCF, LMFp), CNpv (LMFp), CNh (LMF, LMFp), CNa (LMFp).
+
+**Figure 8.5.2-1/Q.1721 – Roaming during an established data session**
+
+This information flow diagram is similar to the information flow diagram of 8.5.1 up to the "tunnel connection" operation where the flow is forwarded (from the home network) to the anchor network. In addition, the "clear old connection" operation must be performed once the new connection is established.
+
+0. **Data service request:** is the trigger to register for the mobile terminal during an established packet data session.
+
+| | |
+|------|------------------------------------------------------------------|
+| FEA0 | – Initiate terminal authentication and registration if required. |
+|------|------------------------------------------------------------------|
+
+1. **Terminal registration and authentication:** is for the mobile terminal to register with the visited network before requesting packet data service.
+
+| | |
+|------|-------------------------------------------------|
+| FEA1 | – Request a data service session establishment. |
+|------|-------------------------------------------------|
+
+2. **Data service req.ind.:** the mobile terminal initiates a data service session in the visited network.
+
+| Data service (Response: Neither Success nor Failure) | req.ind. |
+|-------------------------------------------------------------|-----------------|
+| User ID | M |
+| Service type (data) | M |
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------|
+| FEA2 | – Request for access link setup to be followed by the "Advertisement" operation request to the terminal. |
+|------|----------------------------------------------------------------------------------------------------------|
+
+3 **Advertisement req.ind.:** is sent to the terminal to request establishment of a data session when a new NAI is detected.
+
+| Advertisement (Report: Neither Success nor Failure) | req.ind. |
+|------------------------------------------------------------|-----------------|
+| IP address (PSCFv) | M |
+| IP address (PSCFv – Public) | M |
+| Challenge value (PSCFv) | M |
+| NAI (PSCFv) | M |
+
+| | |
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA3 | - – Respond to the advertisement with a registration if it detects a new PSCF NAI.
- – Specify a well-known UDP port and the IP address of the visited PSCF as a destination for this information.
- – Specify a UDP port that should be used by the visited PSCF when returning the reply information to the PSCAF.
|
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+4. **Data session req.ind.:** is sent from the PSCAF to the PSCF in the visited network over the established access link to request the establishment of a new tunnel-connection for the existing data session.
+
+| Registration (Response: Success or Failure) | req.ind. |
+|----------------------------------------------------|-----------------|
+| Session ID | O (Note 1) |
+| NAI (MT) | M |
+| NAI (PSCFpv) | M |
+| IP address (MT) | M |
+| IP address (PSCFv Public) | M |
+| Service discriminator | M (Note 2) |
+| IP address (PSGCF Public) | M |
+| Challenge value (PSCFv) | M |
+| Challenge response | M |
+| Encapsulation method | M |
+| Data session lifetime | M |
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA4 | - – Communicate with its LMFp to request the establishment of a new tunnel-connection with the anchor PSGCF for the existing data session.
- – Store locally all information that has been supplied to it by the PSCAF in the Registration req.ind. and bind this information to the access link and the IMSI if it was supplied during the access link establishment.
- – May reduce the proposed data session lifetime before forwarding this information to its LMFp.
- – Assign a transaction identifier to this transaction. Subsequently, it will forward the information obtained from the Registration req.ind. to its LMFp. A security association between the next visiting PSCF and its LMFp will have been previously arranged.
- – Store the session ID.
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+NOTE 1 – If supplied by PSCAF in flow 4.
+
+NOTE 2 – The service discriminator, as it is used in 8.4.1, is not used here as the session is already active in the PSGCF. Consequently, the LMFp does not select the PSGCF. However, the LMFp may need the service discriminator for authorization purposes.
+
+5. **Tunnel-connection req.ind.:** is sent from the Visited LMFp to the mobile terminal's home LMFp to authenticate and authorize the visiting mobile terminal and establish a new tunnel-connection between the Visited PSCF and the PSGCF. Based on the previous NAI information, the visited LMFp will determine that the previous PSCF is in a different network. The mobile terminal's NAI will be used to locate its home LMFp. A security association between the visited LMFp and the home LMFp should exist before any information can be exchanged between these two entities. The visited LMFp forwards this information with the information that was included in the original registration req.ind. to the home LMFp.
+
+| Tunnel connection (Report: Success or Failure) | req.ind. |
+|-------------------------------------------------------|-----------------|
+| NAI (MT) | M |
+| NAI (PSCFpv) | M |
+| NAI (PSCFv) | M |
+| IP address (MT) | M |
+| IP address (PSCFv Public) | M |
+| Service discriminator | M |
+| IP address (PSGCF Public) | M |
+| Challenge value (from PSCFv) | M |
+| Challenge response | M |
+| Encapsulation Method | M |
+| Data session lifetime | M |
+
+| | |
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA5 | - – Authenticate the mobile terminal by using the Challenge Value, Challenge Response and the secret it shares with its mobile terminal.
- – Detect that this is an established packet data session and it will know whether the anchor network is the home network or the visited network where the session was initiated.
- – May decide to use the existing security keys and Security Parameter Indices (SPIs) that were allocated to the previous PSCF or it may generate new values for these parameters.
- – When passing the security keys and SPIs to the PSCAF, anchor PSGCF, anchor LMFp, and the Visited LMFp, the home LMFp will employ the shared secrets it shares with these entities.
- – When the anchor network is not the home network, the home LMFp will forward the tunnel-connection req.ind. to the anchor LMFp in the visited network where the session was initiated.
- – For the case where the PSGCF is in the home network, a request is sent from the home LMFp to its PSGCF in the home network to request the establishment of a new tunnel-connection between the visited PSCF and the home PSGCF.
|
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+6. **Tunnel-connection req.ind.:** is sent from the home LMFp to the anchor LMFp to request the establishment of a new tunnel-connection between the anchor PSGCF and the visited PSCF. The home LMFp has recorded the NAI of anchor LMFp when the data session was initiated.
+
+| Tunnel connection (Response: Success or Failure) | req.ind. |
+|---------------------------------------------------------|-----------------|
+| NAI (MT) | M |
+| IP address (MT) | M |
+| IP address (PSCFv Public) | M |
+| IP address (PSGCF Public) | M |
+| Encapsulation method | M |
+| Remaining data session lifetime | M |
+| Security keys and SPI | M |
+| Data session lifetime | M |
+
+| | |
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA6 | - – Detect that this is an established data session.
- – Forward a request to its PSGCF to request the establishment of a new tunnel-connection between the visited PSCF and the anchor PSGCF.
|
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+7. **Tunnel-connection resp.conf.:** is sent from the anchor LMFp to the home LMFp to indicate whether the request to establish a new tunnel-connection between the visited PSCF and the anchor PSGCF has been accepted or rejected.
+
+| Tunnel connection | resp.conf. |
+|--------------------------------------|-------------------|
+| Result (PSGCF allocation indication) | M |
+| IP address (PSGCF public) | M |
+| IP address (MT) | M |
+| Data session lifetime | M |
+
+| | |
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA7 | - – Respond to confirm authorization of establishing the new data session.
- – Optionally, request previously visited network to remove the old connection, "clear old connection" operation.
|
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+8. **Tunnel-connection resp.conf.:** is sent from the mobile terminal's home LMFp to the visited LMFp to authorize the packet data service for the mobile terminal in the visited network and indicate whether a new tunnel-connection with the anchor PSGCF has been established.
+
+| Tunnel connection | resp.conf. |
+|--------------------------------------|-------------------|
+| Result (PSGCF allocation indication) | M |
+| IP address (PSGCF public) | M |
+| IP address (MT) | M |
+| Data session lifetime | M |
+| Security keys and SPI | M |
+
+| | |
+|------|----------------------------------------------------------------------------------|
+| FEA8 | – Informs the Visited PSCF whether a new tunnel-connection has been established. |
+|------|----------------------------------------------------------------------------------|
+
+9. **Data session resp.conf.:** is sent from the Visited PSCF to the PSCAF in response to the Registration req.ind. requesting the establishment of a new tunnel-connection. This information is sent over the established access link.
+
+| Data session | resp.conf. |
+|--------------------------------------|-------------------|
+| Result (PSGCF allocation indication) | M |
+| IP address (PSGCF public) | M |
+| IP address (MT) | M |
+| Security keys and SPI | M |
+| Data session lifetime | M |
+| Session ID | O (Note) |
+
+| | |
+|------------------------------|-----------------------|
+| FEA9 | – No action required. |
+| NOTE – If supplied by PSCAF. | |
+
+10. **Clear old connection req.ind.:** (optional) is for the home LMFp to inform the previously visited LMFp to clear all local information that pertains to the old tunnel-connection with the anchor PSGCF. This IF is independent of IF 9.
+
+| Clear old connection (Response: Neither Success nor Failure) | req.ind. |
+|---------------------------------------------------------------------|-----------------|
+| NAI (MT) | M |
+| IP address (MT) | M |
+| NAI (PSCFpv) | M |
+| IP address (PSGCF-Public) | M |
+
+| | |
+|-------|-----------------------------------------------------|
+| FEA11 | – Respond to confirm removal of the old connection. |
+|-------|-----------------------------------------------------|
+
+11. **Clear old connection resp.conf.:** (optional) is for the previously visited LMFp to send confirmation information to the home LMFp indicating that the old tunnel-connection has been cleared.
+
+| Clear old connection | resp.conf. |
+|----------------------|------------|
+| Result | M |
+
+| | |
+|-------|-----------------------|
+| FEA11 | – No action required. |
+|-------|-----------------------|
+
+### 8.5.3 Packet data service session termination
+
+#### 8.5.3.1 Mobile terminal initiated session termination
+
+Either the terminal or the network may decide to terminate an active packet data session. This subclause describes the terminal initiated de-registration information flow procedure. Figure 8.5.3-1 shows the information flow diagram for this procedure. Steps 2-4 may be repeated in order to support multiple data sessions from the same mobile terminal.
+
+
+
+```
+
+sequenceDiagram
+ participant MT
+ participant RAN+CNv as RAN+CNv (PSCF, LMFp)
+ participant CNpv as CNpv (LMFp)
+ participant CNa as CNa (LMFp, PSGCF)
+
+ Note left of MT: 0
+ MT->>PSCAF: De-registration request
+ Note right of CNa: 0
+
+ Note left of MT: 1
+ PSCAF->>RAN+CNv: De-registration req.ind.
+ Note right of CNa: 1
+
+ Note left of MT: 2
+ RAN+CNv->>CNpv: De-registration req.ind.
+ Note right of CNa: 2
+
+ Note left of MT: 3
+ CNpv->>RAN+CNv: De-registration resp.conf.
+ Note right of CNa: 3
+
+ Note left of MT: 4
+ RAN+CNv->>CNa: Tunnel release req.ind.
+ Note right of CNa: 4
+
+```
+
+T11105780-00
+
+Sequence diagram for terminal initiated packet data session termination. Lifelines: MT, RAN+CNv (PSCF, LMFp), CNpv (LMFp), and CNa (LMFp, PSGCF). The sequence shows: 0. De-registration request from MT to PSCAF; 1. De-registration req.ind. from PSCAF to RAN+CNv; 2. De-registration req.ind. from RAN+CNv to CNpv; 3. De-registration resp.conf. from CNpv to RAN+CNv; 4. Tunnel release req.ind. from RAN+CNv to CNa.
+
+Figure 8.5.3-1/Q.1721 – Terminal initiated packet data session termination
+
+0. **De-registration request:** is to initiate a packet data service de-registration.
+
+| | |
+|------|----------------------------------------------------------|
+| FEA0 | – Request termination of the active packet data session. |
+|------|----------------------------------------------------------|
+
+1. **De-registration req.ind.:** is from the mobile terminal to inform the IMT-2000 network of its request to de-register from the active packet data service session.
+
+| De-registration (no response expected) | req.ind. |
+|-----------------------------------------------|-----------------|
+| User identification (IMUI or TMUI) | M |
+| IP address (PSGCF – Public) | M |
+| IP address (PSCFv – Public) | M |
+| NAI (PSCFv) | M |
+| IP address (MT) | M |
+| NAI (MT) | M |
+| Data session lifetime | M |
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | - – The visited LMFp updates its database as appropriate.
- – The visited LMFp notifies the home LMFp.
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+2. **De-registration req.ind.:** is from the visited LMFp sending the de-registration req.ind. to the home LMFp to indicate that the terminal is no longer reachable in the visited system.
+
+| De-registration (Response: Success/Failure) | req.ind. |
+|----------------------------------------------------|-----------------|
+| IP address (PSGCF – Public) | M |
+| IP address (PSCFv – Public) | M |
+| NAI (PSCFv) | M |
+| IP address (MT) | M |
+| NAI (MT) | M |
+| Data session lifetime | M |
+| Session source address | O (Note) |
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA2 | - – The home LMFp updates its database as appropriate.
- – The home LMFp responds to the visited LMFp.
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+NOTE – In the case of multiple sessions, the PSCFv must associate the resp.conf. signal with the corresponding req.ind. signal using source address information.
+
+3. **De-registration resp.conf.:** is from the home LMFp acknowledging the request to de-register the terminal.
+
+| De-registration | resp.conf. |
+|------------------------|-------------------|
+| IP address (MT) | M |
+| NAI (MT) | M |
+| Session source address | O (Note) |
+
+| | |
+|------|------------------------------------------------------------------|
+| FEA3 | The visited system initiates tunnel release to the gateway PSCF. |
+|------|------------------------------------------------------------------|
+
+NOTE – In the case of multiple sessions, the PSCFv must associate the resp.conf. signal with the corresponding req.ind. signal using source address information.
+
+4. **Tunnel release req.ind.:** is from the serving PSCF notifying the anchor PSGCF to release the tunnel to the visited network.
+
+| Tunnel release (Response: Neither Success nor Failure) | req.ind. |
+|---------------------------------------------------------------|-----------------|
+| IP address (PSGCF – Public) | M |
+| IP address (PSCFv – Public) | M |
+| NAI (PSCFv) | M |
+| IP address (MT) | M |
+| NAI (MT) | M |
+| Data session lifetime | M |
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA4 | - – The PSGCF in the anchor network notifies its local LMFp that it is no longer serving as gateway to the de-registered terminal.
- – The anchor LMFp updates its database as appropriate.
|
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+#### **8.5.3.2 Network initiated session termination**
+
+Either the terminal or the network may decide to terminate an active packet data session. This subclause describes the network initiated de-registration information flow procedure. Figure 8.5.3-2 shows the information flow diagram for this procedure. Steps 2-4 may be repeated in order to support multiple data sessions from the same mobile terminal.
+
+
+
+```
+
+sequenceDiagram
+ participant MT as MT (PSCAF)
+ participant RAN+CNv as RAN+CNv (PSCF, LMFp)
+ participant CNpv as CNpv (LMFp)
+ participant CNa as CNa (LMFp, PSGCF)
+
+ Note left of MT: 0
+ MT->>RAN+CNv: De-registration request
+ Note right of RAN+CNv: 1
+ RAN+CNv->>MT: De-registration req.ind.
+ Note right of RAN+CNv: 2
+ RAN+CNv->>CNpv: De-registration req.ind.
+ Note right of CNpv: 3
+ CNpv->>RAN+CNv: De-registration resp.conf.
+ Note right of RAN+CNv: 4
+ RAN+CNv->>CNa: Tunnel release req.ind.
+ Note right of CNa: 4
+
+```
+
+T11105790-00
+
+Sequence diagram for network initiated packet data session termination. Lifelines: MT (PSCAF), RAN+CNv (PSCF, LMFp), CNpv (LMFp), CNa (LMFp, PSGCF). Steps: 0. De-registration request (MT to RAN+CNv); 1. De-registration req.ind. (RAN+CNv to MT); 2. De-registration req.ind. (RAN+CNv to CNpv); 3. De-registration resp.conf. (CNpv to RAN+CNv); 4. Tunnel release req.ind. (RAN+CNv to CNa).
+
+**Figure 8.5.3-2/Q.1721 – Network initiated packet data session termination**
+
+0. **De-registration request:** the network initiates a packet data service de-registration.
+
+| | |
+|------|------------------------------------------------|
+| FEA0 | – Notify terminal (PSCAF) for de-registration. |
+|------|------------------------------------------------|
+
+1. **De-registration req.ind.:** is to inform the terminal of the network's intent to de-register the terminal from the active packet data service session.
+
+| De-registration (Response: Neither Success nor Failure) | req.ind. |
+|----------------------------------------------------------------|-----------------|
+| User identification (IMUI or TMUI) | M |
+
+| | |
+|------|-----------------------------------------------------|
+| FEA1 | – The terminal prepares to release the access link. |
+|------|-----------------------------------------------------|
+
+2. **De-registration req.ind.:** sends the de-registration request to the home LMFp to indicate that the terminal is no longer reachable in the visited system.
+
+| De-registration (Report Success/Failure) | req.ind. |
+|-------------------------------------------------|-----------------|
+| IP address (PSGCFv – Public) | M |
+| IP address (PSCFv – Public) | M |
+| NAI (PSCFv) | M |
+| IP address (MT) | M |
+| NAI (MT) | M |
+| Data session lifetime | M |
+| Session source address | O (Note) |
+
+| | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA2 | - – The home LMFp updates its database as appropriate.
- – The home LMFp responds to the visited LMFp.
|
+| NOTE – For multiple sessions, the PSCFv must associate the response signal with the corresponding req.ind. signal using source address information. | |
+
+3. **De-registration resp.conf.:** is for the home LMFp to acknowledge the request to de-register the terminal.
+
+| De-registration | resp.conf. |
+|------------------------|-------------------|
+| IP address (MT) | M |
+| NAI (MT) | M |
+| Session source address | O (Note) |
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|
+| FEA3 | - – The visited system initiates tunnel release to the gateway PSCF.
|
+| NOTE – For multiple sessions, the PSCFv must associate the response signal with the corresponding request signal using source address information. | |
+
+4. **Tunnel release req.ind.:** the serving PSCF notifies the anchor PSGCF to release the tunnel to the visited network.
+
+| Tunnel release (no response expected) | req.ind. |
+|----------------------------------------------|-----------------|
+| IP address (PSGCFv – Public) | M |
+| IP address (PSCFv – Public) | M |
+| NAI (PSCFv) | M |
+| IP address (MT) | M |
+| NAI (MT) | M |
+| Data session lifetime | M |
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA4 | - – The PSGCF in the anchor network notifies its local LMFp that it is no longer serving as gateway to the de-registered terminal.
- – The anchor LMFp updates its database as appropriate.
|
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+# 9 Virtual Home Environment
+
+Service invocation in the IMT-2000 system may occur at any time during call processing. It may also occur, either in conjunction with or independent of a call, in relation to mobility management processing, or for authentication processing. Services are offered according to information contained in the subscriber service profile. The subscriber service profile lists subscribed standard basic and supplementary services as well as triggers and associated information (e.g. trigger criteria, associated service logic address, etc.) for VHE-based customized services. Visited IMT-2000 networks are not expected to offer customized services (i.e. customized services offered by home network operators/service providers.) However, the VHE capability and procedures enable the serving network to make these services available to visiting users.
+
+In the VHE concept, service provisioning and network operation may be separated, allowing services to be offered by networks other than those providing the home network's call processing capabilities. In some cases, service logic may be accessed in a separate supporting network. In other cases, the home network provides the service logic and therefore acts as the supporting network.
+
+In the following description (subclauses 9.1 and 9.2), the supporting network is the network where the service logic is located and executed (marked as CNs). The serving or visited network is the network where the user is roaming when the service execution is requested (marked as CNv). The home network (marked as CNh) is where the home Location Management Function (LMFh) and the home Authentication Management Function (AMFh) are located. The CNs and the CNh may be the same network.
+
+Recommendations Q.1701 and Q.1711 identify two VHE realization scenarios for IMT-2000 CS-1. They are the "Direct Home Command" scenario addressed in 9.1 and the "Relay Service Control" scenario addressed in 9.2.
+
+## 9.1 "Direct Home Command"
+
+In the "Direct Home Command" VHE scenario, the supporting network provides service logic to a visited network serving the roaming subscriber to support that subscriber's VHE-based services. Service logic in the supporting network is invoked via the IN triggering capability of the visited network. Pre-arrangement between the supporting and the visited networks may be needed for screening trigger invocations.
+
+### 9.1.1 High level "Direct Home Command" service procedure
+
+In an end-to-end IF scheme, this procedure consists of four components: call origination, VHE service logic invocation, call routing, and call connect (in the case of call-related services; similar VHE service procedures apply to call-unrelated scenarios). This subclause addresses the information flows for the VHE service logic invocation part, and treats the information flows for the other three parts as common procedures within the context of the end-to-end information flows.
+
+The following assumptions are made related to VHE service logic invocation information flows:
+
+- In this scenario, pre-arrangement between the supporting and the home networks, or between the supporting and the visited networks, is needed for screening trigger invocations.
+- The serving/visited network has IN capability for triggering the required service logic.
+
+Figure 9.1.1-1 presents a high-level overview information flow (IF) diagram for the "Direct Home Command" VHE scenario. The following points should be noted with respect to this figure:
+
+- for call-related services, it includes only the call origination side of the flows from a calling party; similar interaction could occur from a terminating call to a called party;
+- other means of initiating service logic not related to calls, such as from mobility management or authentication management, behave in the same way, although the messaging is from a different FE in the "RAN+CNh or v" (see 9.1.3 and 9.1.4);
+
+- the case of a notification to service logic is a subset of Figure 9.1.1-1 (i.e. flow 2 would not be required); and
+- the figure is greatly simplified in that it does not illustrate the full range of service logic interaction supported by IN, e.g. it does not reflect an extended interaction with service logic (which may continue until the call is released), user interaction controlled by service logic, etc.
+
+
+
+The diagram illustrates a sequence of interactions between three entities: RAN+CNh or v (SSR/CCF'), CNs or h (SCF), and CNdest (CCF'). The sequence is numbered 0 to 3.
+ 0. Call origination: An arrow points from the left (RAN+CNh or v) to the right (CNdest).
+ 1. Service logic invoke req.ind.: An arrow points from the RAN+CNh or v entity to the CNs or h entity.
+ 2. Service logic invoke resp.conf.: An arrow points from the CNs or h entity back to the RAN+CNh or v entity.
+ 3. Call routing: A horizontal bar labeled 'Call routing' spans across the bottom of the diagram, indicating a transition or a common processing step.
+
+Sequence diagram showing call flow between RAN+CNh or v, CNs or h, and CNdest. The diagram includes steps for call origination, service logic invoke request, and service logic invoke response. The diagram is labeled T11105800-00.
+
+Figure 9.1.1-1/Q.1721 – High-level call related "Direct Home Command"
+
+0. **Call origination:** a subscriber originates a call. The information obtained from the home network at registration will contain information for the serving network to support VHE service invocation3.
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | – Continue call processing until an armed trigger is encountered at a TDP, and the criteria for the armed trigger are met. |
+|------|----------------------------------------------------------------------------------------------------------------------------|
+
+1. **Service logic invoke req.ind.:** is used to invoke service logic at the SCF associated with the trigger whose criteria were met. It conveys information about the subscriber, the state of the call and the trigger condition encountered.
+
+| Service logic invoke (Response: Success or Failure) | req.ind. |
+|-------------------------------------------------------|----------|
+| Information elements in a service logic initiating IF | Per [5] |
+| IMUI | M |
+
+| | |
+|------|--------------------------|
+| FEA1 | – Execute service logic. |
+|------|--------------------------|
+
+2. **Service logic invoke resp.conf.:** provides the call processing instruction which service logic wishes the invoking entity to perform.
+
+| Service logic invoke | resp.conf. |
+|-------------------------------------------------------|------------|
+| Information elements in a service logic responding IF | Per [5] |
+
+| | |
+|------|----------------------------------------------------|
+| FEA2 | – Execute call processing instruction if possible. |
+|------|----------------------------------------------------|
+
+3 This information is included in user profile information obtained during MT registration. This avoids the need to obtain this information as part of call origination.
+
+3. **Call routing:** is employed to continue call processing and to connect the call to the destination network, if that is the appropriate action based on the information in the Service Logic Invoke resp.conf.
+
+Service logic for VHE-based customized services using the "Direct Home Command" is provided by the user's home network or a supporting network (which may be the home network). For the generalized VHE scenario, it is assumed services are provided by a supporting network.
+
+This subclause above provides a high-level simplified end-to-end IF for the "Direct Home Command" (DHC) procedure. The invocation of the VHE-based service triggering capability may occur for two classes of services:
+
+- **Call-related service invocation** occurs during call processing (e.g. call origination, call termination or mid-call). At the FE level, this scenario invokes service logic in the SCF of the supporting network via the triggering capability of the CCF/SSF in the visited network.
+- **Call-unrelated service invocation** occurs for mobility management events4, or authentication events. At the FE level, this scenario invokes service logic in the SCF of the supporting network by a query from the LMF or a query from the AMF.
+
+### 9.1.2 "Direct Home Command" – Call related services
+
+This subclause expands upon the "VHE service invocation" component for the NNI and addresses the signalling requirements for the DHC scenario for services invoked by an SSF/CCF in the visited network. It is assumed that the SSF/CCF has the capability to trigger the required SCF service logic residing in the supporting network.
+
+Subclause 7.2.2.5/Q.1711 describes an IMT-2000 functional model for interconnections across the NNI between a home network, a supporting network and a visited network. These interconnections are required for invocation of service logic in the supporting network.
+
+Figure 9.1.2-1 presents the DHC scenario of the VHE information flow diagram. The figure is simplified in that it does not illustrate the full range of service logic interaction supported by IN as noted in 9.1.1 above. The "VHE service invocation" procedure may end after the first "Specialized Resource Assist" or it may continue until the call-related service is complete.
+
+This subclause describes triggering in relation to call origination. Triggers may also occur during call termination or mid-call.
+
+---
+
+4 Mobility management processing may occur in conjunction with a call or separate from any call event.
+
+
+
+```
+
+sequenceDiagram
+ participant RAN+CNh or v as RAN+CNh or v
+SSF/CCF'
+ participant CNs or h as CNs or h
+SCF SRF
+ participant CNh as CNh
+LMF
+ Note left of RAN+CNh or v: 0 Call origination
+ RAN+CNh or v->>CNs or h: 1 VHE service invocation req.ind.
+ CNs or h->>CNh: 2 Location information interrogation
+ CNs or h->>RAN+CNh or v: 3 Specialized resource assist
+ CNs or h->>RAN+CNh or v: 4 VHE service invocation resp.conf.
+
+```
+
+Sequence diagram for 'Direct Home Command' showing interactions between RAN+CNh or v (SSF/CCF'), CNs or h (SCF, SRF), and CNh (LMF). The sequence starts with 'Call origination' at step 0, followed by 'VHE service invocation req.ind.' at step 1, 'Location information interrogation' at step 2, 'Specialized resource assist' at step 3, and 'VHE service invocation resp.conf.' at step 4.
+
+Figure 9.1.2-1/Q.1721 – Detailed call related "Direct Home Command"
+
+0. **Call origination:** the calling party originates a call in a visited network. The information obtained from the home network at registration includes triggers and associated criteria and other parameters for visited network support of VHE-based services.
+
+| | |
+|------|----------------------------------------------------------------------------------|
+| FEA0 | – An armed trigger in the SSF/CCF' BCSM is encountered and its criteria are met. |
+|------|----------------------------------------------------------------------------------|
+
+1. **VHE service invocation req.ind.:** is used to invoke the VHE-based service logic of the supporting SCF.
+
+| VHE service invocation (Response: Success or Failure) | req.ind. |
+|-------------------------------------------------------|------------|
+| Information elements in a service logic initiating IF | Per [5] |
+| IMUI | M |
+| MS capability | O (Note 1) |
+| MS Location information | O (Note 2) |
+
+| | |
+|-----------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | - – Identify the user.
- – Retrieve user service data from the subscriber VHE service profile (e.g. SDF).
- – If required, formulate and send a request for MS location and state information to the LMF in the home network.
|
+| NOTE 1 – MS capability is included based on trigger criteria.
NOTE 2 – MS location information is included if it is available. | |
+
+2. **Location information interrogation:** is used to request information on the called user's location if it is required by service logic and it was not included in the first information flow.
+
+3. **Specialized resource assist:** if needed, is initiated by service logic at the SCF to obtain access to the SRF's specialized resources (e.g. play announcement and/or digit collection) in conjunction with the SSF/CCF'. This procedure uses INAP procedures as defined in Recommendation Q.1238.
+
+4. **VHE service invocation resp.conf.:** transfers VHE-based service instructions to the VHE-based service invocation initiating entity.
+
+| VHE service invocation | resp.conf. |
+|-------------------------------------------------------|------------|
+| Information elements in a service logic responding IF | Per [5] |
+
+| | |
+|------|----------------------------------------------------------------------------------------|
+| FEA4 | – Continue processing the call per the instruction received from the SCF, if possible. |
+|------|----------------------------------------------------------------------------------------|
+
+### 9.1.3 "Direct Home Command" – LMF invoked services
+
+Subclause 7.2.2.5/Q.1711 describes an IMT-2000 functional model for interconnections across the NNI between a home or a visited network and a supporting network. These interconnections are required for invocation of service logic in the supporting network triggered from the LMF.
+
+Figure 9.1.3-1 provides the LMF invoked VHE DHC scenario information flow diagram.
+
+
+
+The diagram is a sequence diagram with three lifelines: **RAN+CNh or v** (labeled LMF), **CNs** (labeled SCF), and **CNh** (labeled LMF). The sequence of messages is as follows:
+
+- 0**: A **Call unrelated event** occurs within the **RAN+CNh or v** lifeline.
+- 1**: A **VHE service invocation req.ind.** message is sent from **RAN+CNh or v** to **CNs**.
+- 2**: A **Location information interrogation** message is sent from **CNs** to **CNh**.
+- 3**: A **VHE service invocation resp.conf.** message is sent from **CNh** back to **RAN+CNh or v**.
+
+Reference code: T11105820-00
+
+Sequence diagram for LMF 'Direct Home Command' showing interactions between RAN+CNh or v (LMF), CNs (SCF), and CNh (LMF).
+
+Figure 9.1.3-1/Q.1721 – LMF "Direct Home Command"
+
+0. **Call unrelated event:** the mobility management process utilizes information obtained from the home network at registration. This information includes triggers and associated criteria and other parameters for visited network support of LMF invoked VHE-based services.
+
+| | |
+|------|--------------------------------------------------------------------------------------------------------------------|
+| FEA0 | – An armed trigger is encountered at a TDP in the LMF state model, and the criteria for the armed trigger are met. |
+|------|--------------------------------------------------------------------------------------------------------------------|
+
+1. **VHE service invocation req.ind.:** is used to invoke VHE-based service logic at the supporting SCF.
+
+| VHE service invocation (Response: Success or Failure) | req.ind. |
+|-------------------------------------------------------|------------|
+| Service key | M |
+| Event type | M |
+| IMUI | M |
+| MS capability | O (Note 1) |
+| MS location information | O (Note 2) |
+
+| | |
+|------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | - – Identify user.
- – Retrieve user data from the subscriber VHE service profile (e.g. SDF).
- – If required, formulate and send a request for MS location and state information to the LMF in the home network.
|
+| NOTE 1 – MS capability is included based on trigger criteria. | |
+| NOTE 2 – MS location information is included if it is available. | |
+
+2. **Location information interrogation:** is used to request information on the called user's location if it is required by service logic and it was not included in the first information flow.
+3. **VHE service invocation resp.conf.:** transfers VHE-based service instruction to the VHE-based service invocation initiating entity.
+
+| VHE service invocation | resp.conf. |
+|-------------------------|------------|
+| VHE service instruction | M |
+
+| | |
+|------|------------------------------------------------------------------------------------------------------|
+| FEA2 | – Continue processing the location registration procedure per the instruction received from the SCF. |
+|------|------------------------------------------------------------------------------------------------------|
+
+### 9.1.4 "Direct Home Command" – AMF invoked services
+
+Subclause 7.2.2.5/Q.1711 describes an IMT-2000 functional model for interconnections across the NNI between a home or a visited network and a supporting network. These interconnections are required for invocation of the service logic in the supporting network triggered from the AMF.
+
+Figure 9.1.4-1 presents the AMF invoked VHE DHC scenario information flow diagram.
+
+
+
+```
+
+sequenceDiagram
+ participant RAN+CNh or v as RAN+CNh or v
+AMF
+ participant CNs as CNs
+SCF
+ participant CNh as CNh
+LMF
+
+ Note left of RAN+CNh or v: Call unrelated event
+ RAN+CNh or v->>CNs: VHE service invocation req.ind.
+ Note right of CNs: Location information interrogation
+ CNs->>RAN+CNh or v: VHE service invocation resp.conf.
+
+```
+
+The diagram illustrates the information flow for the AMF invoked VHE DHC scenario. It features three vertical lifelines: RAN+CNh or v (AMF), CNs (SCF), and CNh (LMF). The sequence of events is as follows:
+
+
+- 0: A 'Call unrelated event' is indicated by a diagonal arrow pointing to the AMF lifeline.
+- 1: The AMF sends a 'VHE service invocation req.ind.' message to the SCF.
+- 2: A dashed box labeled 'Location information interrogation' spans between the SCF and LMF lifelines, indicating an interaction between them.
+- 3: The SCF sends a 'VHE service invocation resp.conf.' message back to the AMF.
+
+ The diagram is labeled with 'T11105830-00' at the bottom right.
+
+Sequence diagram for AMF 'Direct Home Command' showing interactions between RAN+CNh or v (AMF), CNs (SCF), and CNh (LMF).
+
+Figure 9.1.4-1/Q.1721 – AMF "Direct Home Command"
+
+0. **Authentication management event:** initiates the authentication management process. The information available includes triggers and associated criteria and other parameters for support of AMF invoked VHE-based services.
+
+| | |
+|------|--------------------------------------------------------------------------------------------------------------------|
+| FEA0 | – An armed trigger is encountered at a TDP in the AMF state model, and the criteria for the armed trigger are met. |
+|------|--------------------------------------------------------------------------------------------------------------------|
+
+1. **VHE service invocation req.ind.:** is used to invoke VHE service logic at the supporting SCF.
+
+| VHE service invocation (Response: Success or Failure) | req.ind. |
+|-------------------------------------------------------|----------|
+| IMUI | M |
+| Service key | M |
+| Event type | M |
+| MS location information | O (Note) |
+
+| | |
+|----------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | - – Identify user.
- – Retrieve user data from the subscriber VHE service profile (e.g. SDF).
- – If required, formulate and send a request for MS location and state information to the LMF in the home network.
|
+| NOTE – MS location information is included if it is available. | |
+
+2. **Location information interrogation:** is used to request information on the called user's location if it is required by service logic and it was not included in the first information flow.
+
+3. **VHE service invocation resp.conf.:** is used to send VHE service instructions from the SCF in the supporting network to the requesting AMF.
+
+| VHE service invocation | Resp.conf. |
+|-------------------------|------------|
+| VHE service instruction | M |
+
+| | |
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA2 | - – Continue processing the authentication procedure per the instruction received from the SCF.
|
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------|
+
+## 9.2 "Relay Service Control"
+
+The VHE "Relay Service Control" (RSC) scenario is the invocation of service logic that resides in the SCF of a supporting (or home) network by the SCF of a serving network (either a home or visited network).
+
+In VHE RSC, service logic is distributed between the supporting network and the visited network to support a roaming subscriber's VHE-based services.
+
+When the serving network is the same as the supporting network, VHE RSC is IN-based service invocation for which well-established procedures exist. When the serving network is not a supporting network, then VHE RSC can apply. For VHE RSC, it is always assumed that the serving and the supporting networks are two different networks interworking through an NNI protocol.
+
+In the serving network, events of interest may be reported by the CCF/SSF, LMF or AMF to the SCF. The triggers in the invoking FEs may be armed by information from the subscriber's profile or by a concurrent service provisioning process. The invoked SCFv (of the serving network) will query the SCF (of the supporting network) for service control support5.
+
+5 Figures 7-7/Q.1711 and 7-8/Q.1711 show the interconnections across the NNI that can be used for this event reporting.
+
+Service logic for VHE-based services using RSC is provided by the user's home network or a supporting network. For the generalized VHE scenario, it is assumed services are provided by a supporting network.
+
+It is assumed that pre-arrangements are made for cooperation and coordination between the serving and supporting networks for VHE RSC. The extent of the cooperation may vary from a partial (shared) to a full relay of service control program6.
+
+Similar to VHE "Direct Home Command," services for the RSC scenario may be call-related or call unrelated.
+
+### 9.2.1 "Relay Service Control" service procedure
+
+This procedure calls for the invocation of service logic via the SCFv to the SCFs for service control support. Pre-arrangement between the supporting and the visited networks may consist of the relay of security/screening capabilities, service logic execution program subroutines, or wholly executable programs.
+
+Subclause 7.2.2.5/Q.1711 describes an IMT-2000 functional model for interconnections across the NNI between a home network, a supporting network and a visited network. These interconnections are required for invocation of the service command/logic in the supporting network.
+
+In an end-to-end IF scheme, this procedure consists of four components: initial stimulus, VHE service invocation, VHE handling information and completion of initial procedure. This subclause addresses the information flows for the VHE service logic invocation and VHE handling information parts and treats the information flows for the other three parts as common procedures within the context of the end-to-end information flows.
+
+Figure 9.2.1-1 is the information flow diagram for the VHE "Relay Service Control" scenario. It is assumed that the SSF/CCF, LMF or AMF, upon matching trigger criteria, has the capability to send a message to the required SCF within the serving network, and that the serving SCF has the capability to request assistance from the supporting SCF. The following points should be noted with respect to this figure:
+
+- the case of a notification to service logic is a subset of Figure 9.2.1-1 (i.e. flows 2 and 3 would not be required); and
+- the figure is greatly simplified in that it does not illustrate the full range of service logic interaction supported by IN, e.g. it does not reflect an extended interaction with service logic (which may continue until the call is released), user interaction controlled by service logic, etc.
+
+---
+
+6 Relay of Security or Screening Capability for Fraud/Abuse control procedures may also be executed by a Service Logic Program (SLP) at an SCF.
+
+
+
+Sequence diagram for 'Relay Service Control' high level. Lifelines: RAN+CNh or v (SCF), CNs or h (SCF), CNh (LMF). The sequence starts with 'Initial service logic invocation' at step 0. At step 1, 'Relay service control request req.ind.' is sent from the first SCF to the second SCF. At step 2, a dashed box labeled 'Location information interrogation' is shown between the second SCF and the LMF. At step 3, 'Relay service control request resp.conf.' is sent from the second SCF back to the first SCF. The diagram is labeled T111105840-00.
+
+**Figure 9.2.1-1/Q.1721 – "Relay Service Control" high level**
+
+0. **Initial service logic invocation:** invokes service logic at the SCF associated with the trigger whose criteria were met. It conveys information about the subscriber, the state of the call process (invoked from SSF/CCF'), or the state of mobility management (invoked from the LMF) or the state of the authentication process (invoked from AMF) and the trigger condition encountered.
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | - – Identify user's supporting network.
- – Check bilateral agreement for the RSC scheme.
- – Invoke the SCFs (of the supporting network) for the user's VHE service logic program (SLP).
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **Relay service control req.ind.:** is used by the controlling SCF to send a request to the supporting SCF, or for requesting the supporting SCF to perform predefined actions.
+
+| Relay service control (Response: Success or Failure) | req.ind. |
+|------------------------------------------------------|------------|
+| Service key | M |
+| Event type | M |
+| IMUI | M |
+| MS Capability | O (Note 1) |
+| MS Location Information | O (Note 2) |
+
+| | |
+|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | - – Identify User and its Service ID.
- – Identify requested SLP.
- – If required, formulate and send a request for MS location and state information to the LMF in the home network.
- – Check restrictions (using IMUI, MS Location, etc.)
|
+| NOTE 1 – MS capability is included based on trigger criteria. | |
+| NOTE 2 – MT location information is sent if available. | |
+
+2. **Location information interrogation:** is used to request information on the called user's location if it is required by service logic and it was not included in the first information flow.
+
+3. **Relay service control resp.conf.:** is used to forward to the controlling SCF the requested information to enable the call to proceed.
+
+| Relay service control | req.ind. |
+|------------------------------|-----------------|
+| Relayed service logic | M |
+
+| | |
+|------|----------------------------------|
+| FEA2 | – Execute relayed service logic. |
+|------|----------------------------------|
+
+# 10 Messaging services applications
+
+The point-to-point short message service (SMS) provides a means of sending text messages to and from IMT-2000 mobile terminals. The provision of SMS makes use of a message centre (MC), which acts as a store and forward centre for short messages.
+
+Two different point-to-point services have been defined: mobile originated and mobile terminated. Mobile originated messages will be transported from an MT to a message centre. These may be destined for other mobile users, or for subscribers in the fixed network. Mobile terminated messages will be transported from a message centre to an MT. These may be input to the message centre by other mobile users (via a mobile originated short message) or by a variety of other sources, e.g. speech, telex or facsimile.
+
+The point-to-multipoint teleservice message broadcast (TMB) provides a method to manage and deliver teleservice messages for broadcast over the radio interface to IMT-2000 mobile terminals. TMB messages are broadcast to defined geographical areas known as cell broadcast areas. These areas may comprise one or more cells, or may comprise the whole network for a certain service provider. Individual TMB messages will be assigned their own geographical coverage areas by mutual agreement between the information provider and the network operator.
+
+## 10.1 Short message service (SMS)
+
+### 10.1.1 SMS notification transfer
+
+The SMS notification procedure is used for alerting the message centre. The procedure starts when the mobile terminal is active (after a short message transfer has failed because the mobile terminal was previously not reachable), or when the mobile terminal has indicated that it now has memory capacity to accept a short message.
+
+#### 10.1.1.1 MT is active
+
+See Figure 10.1.1.1-1.
+
+
+
+```
+
+sequenceDiagram
+ participant MT
+ participant RAN+CNv
+ participant CNh
+ Note left of MT: MT is active
+ MT->>RAN+CNv:
+ RAN+CNv->>CNh: Ready for SM req.ind.
+ CNh->>RAN+CNv: Ready for SM resp.conf.
+
+```
+
+T11105850-00
+
+Sequence diagram for SMS notification transfer (MT is active). The diagram shows three entities: MT, RAN+CNv, and CNh. The MT sends a message 'MT is active' to the RAN+CNv. The RAN+CNv then sends 'Ready for SM req.ind.' to the CNh. Finally, the CNh sends 'Ready for SM resp.conf.' back to the RAN+CNv. The diagram is numbered 0, 1, 2 on the left and right sides. A small code 'T11105850-00' is at the bottom right.
+
+Figure 10.1.1.1-1/Q.1721 – SMS notification transfer (MT is active)
+
+0. **MT is active:** when the MT is active, e.g. the MT made a service request, had a call origination or paging response. Optionally, user authentication may have occurred.
+
+| | |
+|------|---------------------------------------------------------------------------------------|
+| FEA0 | – When the MT is present, LMFv will change the relevant database and inform the LMFh. |
+|------|---------------------------------------------------------------------------------------|
+
+1. **Ready for SM req.ind.:** informs the LMFh that the MT is ready to accept short messages.
+
+| Ready for SM (Response: Success) | req.ind. |
+|----------------------------------|----------|
+| IMUI | M |
+| Alert reason | M |
+
+| | |
+|------|---------------------------------------------------------------------------|
+| FEA1 | – Inform the visited network that the SM ready request has been received. |
+|------|---------------------------------------------------------------------------|
+
+2. **Ready for SM resp.conf.:** acknowledges the receipt of the short message request.
+
+| Ready for SM | resp.conf. |
+|----------------|------------|
+| User error | O (Note) |
+| Provider error | O (Note) |
+
+| | |
+|----------------------------------------------------------|--------------------------------------------|
+| FEA2 | – Concludes the SMS notification transfer. |
+| NOTE – Only required if an error situation has occurred. | |
+
+#### 10.1.1.2 Memory capacity available
+
+See Figure 10.1.1.2-1.
+
+
+
+```
+
+sequenceDiagram
+ participant UIMF as UIMF
+ participant MCF as MCF
+ participant SACF as SACF
+ participant LMF as LMF
+ participant SCF_SMS as SCF_SMS
+
+ Note left of UIMF: Ready for short message (crossed out)
+ UIMF->>MCF: SM mem cap avail req.ind. (1)
+ MCF->>SACF: SM mem cap avail req.ind. (2)
+ SACF->>LMF: Ready for SM req.ind. (3)
+ LMF->>SACF: Ready for SM resp.conf. (4)
+ SACF->>MCF: SM mem cap avail resp.conf. (5)
+ MCF->>UIMF: SM mem cap avail resp.conf. (6)
+
+```
+
+Sequence diagram showing SMS notification transfer for memory capacity available. Lifelines: UIM (UIMF), MT (MCF), RAN+CNv (SACF, LMF), CNh (LMF, SCF\_SMS). The sequence starts at time 0 with a 'Ready for short message' message from MT to UIM (crossed out). At time 1, UIMF sends 'SM mem cap avail req.ind.' to MCF. At time 2, MCF sends 'SM mem cap avail req.ind.' to SACF. At time 3, SACF sends 'Ready for SM req.ind.' to LMF. At time 4, LMF sends 'Ready for SM resp.conf.' to SACF. At time 5, SACF sends 'SM mem cap avail resp.conf.' to MCF. At time 6, MCF sends 'SM mem cap avail resp.conf.' to UIMF.
+
+T11105860-00
+
+Figure 10.1.1.2-1/Q.1721 – SMS notification transfer (memory capacity available)
+
+0. **Ready for short message:** is the initial stimulus where the mobile terminal has made a service request. Optionally, user authentication may have occurred.
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------|
+| FEA0 | – When the UIMF has the possibility to handle short messages and has made available memory capacity, it informs MCF. |
+|------|----------------------------------------------------------------------------------------------------------------------|
+
+1. **SM memory capacity available req.ind.:** informs the MCF in the MT that it has memory available to accept short messages.
+
+| SM memory capacity available (Response: Success) | req.ind. |
+|--------------------------------------------------|----------|
+| TMUI or IMUI | M (Note) |
+
+| | |
+|------------------------------------------------|-----------------------------------------|
+| FEA1 | – Relay the request to serving network. |
+| NOTE – TMUI should be used if it is available. | |
+
+2. **SM memory capacity available req.ind.:** informs the visited network that the MT is ready to accept short messages.
+
+| SM memory capacity available (Response: Success) | req.ind. |
+|--------------------------------------------------|----------|
+| TMUI or IMUI | M (Note) |
+
+| | |
+|------------------------------------------------|--------------------------------------------------------------------------------------------------------|
+| FEA2 | – Prepare to inform the home network that the requesting subscriber is ready to accept short messages. |
+| NOTE – TMUI should be used if it is available. | |
+
+3. **Ready for SM req.ind.:** informs the LMFh that the MT is ready to accept short messages.
+
+| Ready for SM (Response: Success) | req.ind. |
+|----------------------------------|----------|
+| IMUI | M |
+| Alert reason | M |
+
+| | |
+|------|---------------------------------------------------------------------------|
+| FEA3 | – Inform the visited network that the SM ready request has been received. |
+|------|---------------------------------------------------------------------------|
+
+4. **Ready for SM resp.conf.:** acknowledges the receipt of the short message request.
+
+| Ready for SM | resp.conf. |
+|----------------|------------|
+| User error | O (Note) |
+| Provider error | O (Note) |
+
+| | |
+|----------------------------------------------------------|---------------------------------|
+| FEA4 | – Relay acknowledgement to MCF. |
+| NOTE – Only required if an error situation has occurred. | |
+
+5. **SM memory capacity available resp.conf.:** sends from visited network to confirmed.
+
+| SM memory capacity available | resp.conf. |
+|------------------------------|------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|----------------------------------|
+| FEA5 | – Relay acknowledgement to UIMF. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+6. **SM memory capacity available resp.conf.:** sends a confirmation to UIMF.
+
+| SM memory capacity available | resp.conf. |
+|------------------------------|------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|-----------------------|
+| FEA6 | – No action required. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+### 10.1.2 Mobile originated short message
+
+The mobile terminal sends the short message to the CCF'/SACF in the visiting network. The CCF'/SACF interrogates the LMFv to retrieve the MS ISDN address and forward the message to the interworking CCF'/SSF node in the destination network. The CCF'/SSF nodes sends the short message to the message centre. An E.164 number in the destination network numbering plan to which the message centre is connected addresses the message centre from the mobile. The E.164 number is stored in the UIM.
+
+#### 10.1.2.1 Mobile originated short message (on a traffic channel)
+
+This procedure is invoked when an IMT-2000 user sends a point-to-point short message and a call is already in progress. See Figure 10.1.2.1-1.
+
+
+
+The sequence diagram illustrates the interaction for a mobile originated short message (on a traffic channel). The lifelines are UIM (UIMF), MT (MCF, CCAF), RAN+CNv (SACF, CCF), and CNh (SCFSMS). The sequence of messages is as follows:
+
+- 0: Short message to send (from UIM to UIMF)
+- 1: User authentication (between UIMF and SACF)
+- 2: Start ciphering (between UIMF and SACF)
+- 3: SMS transfer req.ind. (from UIMF to MCF)
+- 4: SMS transfer req.ind. (from MCF to CCF)
+- 5: Forward SMS req.ind. (from CCF to SCFSMS)
+- 6: Forward SMS resp.conf. (from SCFSMS to CCF)
+- 7: SMS transfer resp.conf. (from CCF to MCF)
+- 8: SMS transfer resp.conf. (from MCF to UIMF)
+
+T11105870-00
+
+Sequence diagram for mobile originated short message (on a traffic channel).
+
+Figure 10.1.2.1-1/Q.1721 – Mobile originated short message (on a traffic channel)
+
+0. **Short message to send:** is the initial stimulus where the subscriber submits a short message to the MT to send to a recipient.
+
+| | |
+|------|------------------------------------------------------|
+| FEA0 | – The mobile terminal makes a short message request. |
+|------|------------------------------------------------------|
+
+1. **User authentication:** optionally, user authentication procedure may be invoked.
+2. **Start ciphering:** optionally, ciphering procedure may be initiated.
+3. **SMS transfer req.ind.:** transfer short message to MCF.
+
+| SMS transfer (Response: Success) | req.ind. |
+|----------------------------------|----------|
+| TMUI or IMUI | M (Note) |
+| Called number | M |
+| Message centre address | M |
+| Message | M |
+
+| | |
+|------------------------------------------------|----------------------------------------|
+| FEA3 | – Forward the information to the CCAF. |
+| NOTE – TMUI should be used if it is available. | |
+
+4. **SMS transfer req.ind.:** is used to send the message to CNv.
+
+| SMS transfer (Response: Success) | req.ind. |
+|--------------------------------------------------------|--------------|
+| < Same information elements as in information flow 3 > | < See IF 3 > |
+
+| | |
+|------|-------------------------------------------------------------------|
+| FEA4 | – Forward the information to the short message centre in the CNh. |
+|------|-------------------------------------------------------------------|
+
+5. **Forward SMS req.ind.:** transfer the message to short message centre in CNh.
+
+| Forward SMS (Response: Success) | req.ind. |
+|--------------------------------------------------------|--------------|
+| < Same information elements as in information flow 3 > | < See IF 3 > |
+
+| | |
+|------|---------------------------------------------------------|
+| FEA5 | – Formulates a delivery report to send back to the CNv. |
+|------|---------------------------------------------------------|
+
+6. **Forward SMS resp.conf.:** acknowledgement received to the message.
+
+| Forward SMS | resp.conf. |
+|-------------|------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|---------------------------------------------|
+| FEA6 | – Forwards the delivery report to the CCAF. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+7. **SMS transfer resp.conf.:** acknowledgement received to the message.
+
+| SMS transfer | resp.conf. |
+|--------------|------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|--------------------------------------------|
+| FEA7 | – Forwards the delivery report to the MCF. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+8. **SMS transfer resp.conf.:** acknowledgement received to the message.
+
+| SMS transfer | resp.conf. |
+|--------------|------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|
+| FEA8 | – Informs the subscriber whether or not the message was successfully delivered. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+#### 10.1.2.2 Mobile originated short message (on a control channel)
+
+See Figure 10.1.2.2-1.
+
+
+
+Sequence diagram for mobile originated short message (on a control channel). The diagram shows interactions between UIM (UIMF), MT (MCF, CCAF), RAN+CNv (SACF), and CNh (SCF\_SMS). The sequence starts with 'Short message to send' from UIMF to MCF. Steps 1-2 involve 'User authentication' and 'Start ciphering' between UIMF and SACF. Step 3: 'SMS transfer req.ind.' from UIMF to MCF. Step 4: 'SMS transfer req.ind.' from MCF to SACF. Step 5: 'Forward SMS req.ind.' from SACF to SCF\_SMS. Step 6: 'Forward SMS resp.conf.' from SCF\_SMS to SACF. Step 7: 'SMS transfer resp.conf.' from SACF to CCAF. Step 8: 'SMS transfer resp.conf.' from CCAF to UIMF. The diagram is labeled T11105880-00.
+
+Figure 10.1.2.2-1/Q.1721 – Mobile originated short message (on a control channel)
+
+0. **Short message to send:** is the initial stimulus where the subscriber submits a short message to the MT to send to a recipient.
+
+| | |
+|------|------------------------------------------------------|
+| FEA0 | – The mobile terminal makes a short message request. |
+|------|------------------------------------------------------|
+
+1. **User authentication:** optionally, the User authentication procedure may be invoked.
+
+2. **Start ciphering:** optionally, the ciphering procedure may be initiated.
+3. **SMS transfer req.ind.:** transfers a short message to the MCF.
+
+| SMS transfer (Response: Success) | req.ind. |
+|-----------------------------------------|-----------------|
+| TMUI or IMUI | M (Note) |
+| Called number | M |
+| Message centre address | M |
+| Message | M |
+
+| | |
+|------------------------------------------------|-----------------------------------------|
+| FEA3 | – Forwards the information to the CCAF. |
+| NOTE – TMUI should be used if it is available. | |
+
+4. **SMS transfer req.ind.:** is used to send the message to the CNv.
+
+| SMS transfer (Response: Success) | req.ind. |
+|--------------------------------------------------------|-----------------|
+| < Same information elements as in information flow 3 > | < See IF 3 > |
+
+| | |
+|------|--------------------------------------------------------------------|
+| FEA4 | – Forwards the information to the short message centre in the CNh. |
+|------|--------------------------------------------------------------------|
+
+5. **Forward SMS req.ind.:** transfers the message to SCF in CNh.
+
+| Forward SMS (Response: Success) | req.ind. |
+|--------------------------------------------------------|-----------------|
+| < Same information elements as in information flow 3 > | < See IF 3 > |
+
+| | |
+|------|---------------------------------------------------------|
+| FEA5 | – Formulates a delivery report to send back to the CNv. |
+|------|---------------------------------------------------------|
+
+6. **Forward SMS resp.conf.:** acknowledges receipt of the message.
+
+| Forward SMS | resp.conf. |
+|--------------------|-------------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|---------------------------------------------|
+| FEA6 | – Forwards the delivery report to the CCAF. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+7. **SMS transfer resp.conf.:** acknowledgement received to the message.
+
+| SMS transfer | resp.conf. |
+|---------------------|-------------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|--------------------------------------------|
+| FEA7 | – Forwards the delivery report to the MCF. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+8. **SMS transfer resp.conf.:** acknowledgement received to the message.
+
+| SMS transfer | resp.conf. |
+|--------------|------------|
+| None | (Note) |
+
+| | |
+|------|---------------------------------------------------------------------------------|
+| FEA8 | – Informs the subscriber whether or not the message was successfully delivered. |
+|------|---------------------------------------------------------------------------------|
+
+NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success.
+
+### 10.1.3 Mobile terminated short message
+
+The message centre sends the short message to the CCF'/SACF in the subscriber's home network. The CCF'/SACF interrogates the LMFh to retrieve routing information necessary to forward the short message, and then sends the message to the relevant CCF'/SACF in the visiting network, transiting other networks if necessary. The CCF'/SACF then sends the short message to the MT.
+
+#### 10.1.3.1 Mobile terminated short message on a traffic channel
+
+See Figure 10.1.3.1-1.
+
+
+
+```
+
+sequenceDiagram
+ participant External
+ participant CNh as CNh (LMF, SCF_SMS)
+ participant RAN_CNv as RAN+CNv (SACF, CCF, LMF)
+ participant MT as MT (MCF, CCAF)
+ participant UIM as UIM (UIMF)
+
+ Note right of CNh: Short message for MT (Note)
+ External->>CNh: Short message for MT
+ Note right of CNh: User info interrogation
+ CNh->>RAN_CNv: Forward SMS req.ind.
+ Note right of RAN_CNv: User authentication
+ RAN_CNv->>MT: Start ciphering
+ Note right of MT: SMS transfer req.ind.
+ MT->>UIM: SMS transfer req.ind.
+ UIM->>MT: SMS transfer resp.conf.
+ MT->>RAN_CNv: SMS transfer resp.conf.
+ RAN_CNv->>CNh: Forward SMS resp.conf.
+
+```
+
+Sequence diagram for Mobile terminated short message on a traffic channel. Lifelines: UIM (UIMF), MT (MCF, CCAF), RAN+CNv (SACF, CCF, LMF), CNh (LMF, SCF\_SMS). The sequence shows the flow of a short message from an external source through the CNh, LMFh, CCF/SACF, and finally to the MT, with authentication and ciphering steps in between.
+
+NOTE – The SCFSMS may optionally query the LMFh for location information if the mobile is known to be reachable and has available memory capacity. "User info interrogation" being optional leads to the subsequent information flows being optional.
+
+**Figure 10.1.3.1-1/Q.1721 – Mobile terminated short message (on a traffic channel)**
+
+0. **Short message for MT:** a short message is submitted at the subscriber's home system message centre for delivery to the subscriber's MT.
+
+| | |
+|------|--------------------------------------------------------------------------------------------------------|
+| FEA0 | – Initiate the user info interrogations procedure to obtain information needed to deliver the message. |
+|------|--------------------------------------------------------------------------------------------------------|
+
+1. **User information interrogation:** the LMFh queries the LMFv for the current location and state of the subscriber to whom the short message is destined. The LMFv determines the current location and state of the MT and responds to the LMFh with this information.
+
+2. **Forward SMS req.ind.:** transfers the short message to CCF identified in step 1.
+
+| Forward SMS (Response: Success) | req.ind. |
+|---------------------------------|----------|
+| IMUI | M |
+| Calling number | M |
+| Message centre address | M |
+| Message | M |
+
+| | |
+|------|------------------------------------------------|
+| FEA2 | – Transfers the message to the CCAF in the MT. |
+|------|------------------------------------------------|
+
+3. **User authentication:** optionally, the User authentication procedure may be invoked.
+
+4. **Start ciphering:** optionally, the Ciphering procedure may be initiated.
+
+5. **SMS transfer req.ind.:** transfers the message to the mobile terminal.
+
+| SMS transfer (Response: Success) | req.ind. |
+|--------------------------------------------------------|--------------|
+| < Same information elements as in information flow 2 > | < See IF 2 > |
+
+| | |
+|------|----------------------------------------|
+| FEA5 | – Forwards the information to the MCF. |
+|------|----------------------------------------|
+
+6. **SMS transfer req.ind.:** transfers the message to UIM.
+
+| SMS transfer (Response: Success) | req.ind. |
+|--------------------------------------------------------|--------------|
+| < Same information elements as in information flow 2 > | < See IF 2 > |
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------|
+| FEA6 | – Displays the short message to the user or notifies user of SM.
– Initiates a delivery report to send back to the CNh. |
+|------|----------------------------------------------------------------------------------------------------------------------------|
+
+7. **SMS transfer resp.conf.:** acknowledges receipt of the message.
+
+| SMS transfer | resp.conf. |
+|--------------|------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|---------------------------------------------|
+| FEA7 | – Forwards the acknowledgement to the CCAF. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+8. **SMS transfer resp.conf.:** acknowledgement received to the message.
+
+| SMS transfer | resp.conf. |
+|---------------------|-------------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|--------------------------------------------------------|
+| FEA8 | – Transfers the acknowledgement to the SCF in the CNh. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+9. **Forward SMS resp.conf.:** acknowledges receipt of the message.
+
+| Forward SMS | resp.conf. |
+|--------------------|-------------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|------------------------------------------------|
+| FEA9 | – Marks the message as successfully delivered. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+#### **10.1.3.2 Mobile terminated short message on a control channel**
+
+See Figure 10.1.3.2-1.
+
+
+
+The diagram is a sequence diagram illustrating the interaction for a mobile terminated short message. The lifelines are UIM (UIMF), MT (MCF, CCAF), RAN+CNv (SACF, CCF, LMF), and CNh (LMF, SCFSMS). The sequence of messages is as follows:
+
+- 0: Short message for MT (from CNh to UIMF). (Note: This step is optional.)
+- 1: User info interrogation (from LMF to UIMF). (Note: This step is optional.)
+- 2: Terminal paging (from UIMF to SACF).
+- 3: Forward SMS req.ind. (from SACF to LMF).
+- 4: User authentication (from LMF to UIMF).
+- 5: Start ciphering (from UIMF to SACF).
+- 6: SMS transfer req.ind. (from SACF to MCF).
+- 7: SMS transfer req.ind. (from MCF to UIMF).
+- 8: SMS transfer resp.conf. (from UIMF to MCF).
+- 9: SMS transfer resp.conf. (from MCF to SACF).
+- 10: Forward SMS resp.conf. (from SACF to LMF).
+
+T11105900-00
+
+Sequence diagram for Mobile terminated short message (on a control channel). The diagram shows interactions between UIM (UIMF), MT (MCF, CCAF), RAN+CNv (SACF, CCF, LMF), and CNh (LMF, SCF\_SMS). The sequence starts with a 'Short message for MT' at step 0, followed by optional 'User info interrogation' (step 1), 'Terminal paging' (step 2), 'Forward SMS req.ind.' (step 3), 'User authentication' (step 4), 'Start ciphering' (step 5), 'SMS transfer req.ind.' (step 6), 'SMS transfer req.ind.' (step 7), 'SMS transfer resp.conf.' (step 8), 'SMS transfer resp.conf.' (step 9), and 'Forward SMS resp.conf.' (step 10). A note indicates that step 0 is optional and step 1 is optional.
+
+NOTE – The SCFSMS may optionally query the LMFh for location information if the mobile is known to be reachable and has available memory capacity. "User info interrogation" being optional leads to the subsequent information flows being optional.
+
+Figure 10.1.3.2-1/Q.1721 – Mobile terminated short message (on a control channel)
+
+0. **Short message for MT:** a short message is submitted at the subscriber's home system message centre for delivery to the subscriber's MT.
+
+| | |
+|------|--------------------------------------------------------------------------------------------------------|
+| FEA0 | – Initiate the user info interrogations procedure to obtain information needed to deliver the message. |
+|------|--------------------------------------------------------------------------------------------------------|
+
+1. **User information interrogation:** the LMFh queries the LMFv for the current location and state of the subscriber to whom the short message is destined. The LMFv determines the current location and state of the MT and responds to the LMFh with this information.
+2. **Terminal paging:** optionally, paging procedure may be done to further pinpoint the location of the mobile terminal.
+
+3. **Forward SMS req.ind.:** transfers the short message to the SACF in the CNv.
+
+| Forward SMS (Response: Success) | req.ind. |
+|----------------------------------------|-----------------|
+| IMUI | M |
+| Calling number | M |
+| Message centre address | M |
+| Message | M |
+
+| | |
+|------|-----------------------------------------------|
+| FEA3 | – Transfers the message to the MCF in the MT. |
+|------|-----------------------------------------------|
+
+4. **User authentication:** optionally, the User authentication procedure may be invoked.
+
+5. **Start ciphering:** optionally, the Ciphering procedure may be initiated.
+
+6. **SMS transfer req.ind.:** transfer the message to the mobile terminal.
+
+| SMS transfer (Response: Success) | req.ind. |
+|--------------------------------------------------------|-----------------|
+| < Same information elements as in information flow 3 > | < See IF 3 > |
+
+| | |
+|------|--------------------------------------|
+| FEA6 | – Transfers the message to the UIMF. |
+|------|--------------------------------------|
+
+7. **SMS transfer req.ind.:** transfers the message to UIM.
+
+| SMS transfer (Response: Success) | req.ind. |
+|--------------------------------------------------------|-----------------|
+| < Same information elements as in information flow 3 > | < See IF 3 > |
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------|
+| FEA7 | – Displays the short message to the user or notifies user of SM.
– Initiates a delivery report to send back to the CNh. |
+|------|----------------------------------------------------------------------------------------------------------------------------|
+
+8. **SMS transfer resp.conf.:** acknowledges receipt of the message.
+
+| SMS transfer | resp.conf. |
+|---------------------|-------------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|---------------------------------------------|
+| FEA8 | – Forwards the acknowledgement to the SACF. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+9. **SMS transfer resp.conf.:** acknowledges receipt of the message.
+
+| SMS transfer | resp.conf. |
+|---------------------|-------------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|--------------------------------------------------------|
+| FEA9 | – Transfers the acknowledgement to the SCF in the CNh. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+10. **Forward SMS resp.conf.:** acknowledges receipt of the message.
+
+| Forward SMS | resp.conf. |
+|--------------------|-------------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|------------------------------------------------|
+| FEA10 | – Marks the message as successfully delivered. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+## 10.2 Teleservice message broadcast (TMB)
+
+This subclause provides information flows for Teleservice Message Broadcast (TMB) which provides a method to manage and deliver teleservice text messages for broadcast over the radio interface to IMT-2000 mobile terminals. Examples of areas where teleservice text messages can be used are pertaining to emergencies, administrative announcements, advertisements, subscribed-to services, etc. The broadcast may be done over a prescribed zone (i.e. over a whole or partial SACF in a CN). The broadcast may be done under home-system based periodicity control or under visited-system based periodicity control. Other attributes such as broadcast language, priority, etc., also characterize the broadcast. Teleservice message broadcasts are unacknowledged (i.e. the mobile is not expected to respond when it receives a broadcast message).
+
+TMB happens periodically in the following ways:
+
+NOTE – The **periodicity** consists of a **start time**, a **repetition rate** and a **duration**.
+
+**Option A: Visited-System Based Periodicity Control** – The periodicity of the broadcast of teleservice messages is under the control of the visited system. The teleservice message to be broadcast is deposited by a "client" at the message centre (the SCFSMS in the home system) which then transfers it to one or more CNvs. The SACFs in the CNvs then store and begin the broadcast of the message at regular intervals and for the prescribed duration, in accordance with the periodicity that is specified. The SACFs in the CNvs store the message until the completion of the broadcast (i.e. until the end of the broadcast period). The SACFs may prematurely curtail broadcasting the message when and if directed by the SCFSMS.
+
+**Option B: Home-System Based Periodicity Control** – The periodicity of the broadcast of teleservice messages is under the control of the home system. The teleservice message to be broadcast is deposited by a "client" at the message centre (the SCF in the home system) which then transfers it to one or more CNvs. The SACFs in the CNvs then immediately broadcast the message. Here, the SACFs do not need to store the message. However, if the client had desired rebroadcast at regular intervals and for some duration, the home (SCFSMS) can re-send the message to the CNvs for rebroadcast. In this scenario, the SCFSMS in the CNh has the responsibility of retaining the message until the completion of the broadcast (i.e. until the end of the broadcast period).
+
+Both options are illustrated in the Figure 10.2-1.
+
+Also, the SCF sends the teleservice message broadcast payload and associated IEs to all the SACFs in the CNvs that are part of the prescribed broadcast zone. However, for simplicity only one SACF is shown in the Figure 10.2-1.
+
+Typically, Option A is used for high repetition rate broadcasts (e.g. every two minutes,) over a short duration (e.g. for three hours).
+
+Typically, Option B is used for low repetition rate broadcasts (e.g. every six hours) over a long duration (e.g. for seven days).
+
+It is an operator's decision: Option A tends to utilize greater system resources (memory) while Option B tends to utilize greater signalling link resources (higher occupancy).
+
+
+
+The sequence diagram shows the following steps:
+
+- 0:** TMB message submitted (from external source to CNh).
+- 1:** Application data delivery req.ind. (from CNh to RAN+CNv).
+- 2:** Application data delivery resp.conf. (from RAN+CNv to CNh).
+- 3:** Teleservice message broadcast req.ind. (from UIMF to RAN+CNv).
+- Option A:** A dashed box labeled "Option A" contains a "Time lapse" between steps 3 and 4.
+- 4:** Teleservice message broadcast req.ind. (from UIMF to RAN+CNv).
+- Option B:** A dashed box labeled "Option B" contains a "Time lapse" between steps 4 and 5.
+- 5:** Application data delivery req.ind. (from RAN+CNv to CNh).
+- 6:** Application data delivery resp.conf. (from CNh to RAN+CNv).
+- 7:** Teleservice message broadcast req.ind. (from UIMF to RAN+CNv).
+
+T11105910-00
+
+Sequence diagram for Teleservice message broadcast showing interactions between UIM, MT, RAN+CNv, and CNh. The diagram illustrates two options for message delivery. Option A involves a direct broadcast request from UIMF to SACF after a time lapse. Option B involves a response from SACF to SCF\_SMS, followed by a broadcast request from SACF to UIMF after another time lapse.
+
+Figure 10.2-1/Q.1721 – Teleservice message broadcast
+
+0. **TMB message submitted:** this is the initial stimulus where a "client" submits a message to be broadcast using teleservice message broadcast. The request includes the actual broadcast payload, the originator's address, the broadcast category, broadcast message type, broadcast message status, broadcast message priority, broadcast periodicity, broadcast service group, broadcast zone identifier and the preferred language for broadcast.
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | – Initiates Option A (Visited-System Based Periodicity Control) or Option B (Home-System Periodicity Control) in accordance with the TMB requests. |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **Application data delivery req.ind.:** is from the SCF in the home network to all the SACFs which control the prescribed broadcast zone.
+
+| Application data delivery (Response: Success) | req.ind. |
+|-----------------------------------------------|------------|
+| Originator address | M |
+| Payload | M |
+| Category | M |
+| Message type | M |
+| Message status | M |
+| Zone identifier | O (Note 1) |
+
+| Application data delivery (Response: Success) | req.ind. |
+|------------------------------------------------------|-----------------|
+| Periodicity | O (Note 2) |
+| Message priority | O (Note 3) |
+| Service group | O (Note 4) |
+| Preferred language | O (Note 5) |
+
+| | |
+|------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | - – Acknowledge the application data delivery request.
- – Initiates to send teleservice message broadcast in the visiting network.
|
+| NOTE 1 – Include to specify broadcast zones. Absence of IE means broadcast over whole SACF. | |
+| NOTE 2 – Include for Visited-System Based Periodicity control if absent, send the message once only. | |
+| NOTE 3 – Include to indicate normal (default), interactive, urgent or emergency broadcast. | |
+| NOTE 4 – Include to indicate target MT audience (operator defined). | |
+| NOTE 5 – Include to indicate the language that the message is written in. Used for filtering. | |
+
+2. **Application data delivery resp.conf.:** acknowledges receipt of the application data delivery requests.
+
+| Application data delivery | resp.conf. |
+|----------------------------------|-------------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA2 | - – No action required if Option A is selected.
- – Wait for timer expiry if Option B is selected.
|
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+3. **Teleservice message broadcast req.ind.:** passes the message to UIMF.
+
+| Teleservice message broadcast (Response: None) | req.ind. |
+|-------------------------------------------------------|-----------------|
+| Originator address | M |
+| Payload | M |
+| Category | M |
+| Message type | M |
+| Message status | M |
+| Message priority | O (Note 1) |
+| Service group | O (Note 2) |
+| Preferred language | O (Note 3) |
+
+| | |
+|-----------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|
+| FEA3 | - – Display the message to the user in accordance with the parameters as received.
|
+| NOTE 1 – Include to indicate normal (default), interactive, urgent or emergency broadcast. | |
+| NOTE 2 – Include to indicate target MT audience (operator defined). | |
+| NOTE 3 – Include to indicate the language that the message is written in. Used for filtering. | |
+
+Step 4 is a repeat of information flow 3, and applies only in the case of Option A, where the visited system controls the periodicity. The IEs and the FEA are the same as in information flow 3. This step is repeated in accordance with the prescribed periodicity.
+
+Steps 5, 6 and 7 are the same as information flows 1, 2 and 3 except the Periodicity is not included in information flow 5. They apply only in the case of Option B where the home system controls the periodicity. These steps are repeated in accordance with the prescribed periodicity.
+
+## 10.3 Message waiting notification (MWN)
+
+### 10.3.1 MWN information flows
+
+This scenario shows the information flow related to message waiting notification (MWN) for IMT-2000 systems in a global roaming situation. Message waiting notification is a feature whereby enrolled subscribers are notified when pending voice, fax, e-mail and other types of messages have been deposited in their messaging systems and are available for retrieval. See Figure 10.3.1-1.
+
+
+
+```
+
+sequenceDiagram
+ participant UIM as UIM (UIMF)
+ participant MT as MT (MCF)
+ participant RAN as RAN+CNv (SACF, LMF)
+ participant CNh as CNh (LMF)
+
+ Note right of CNh: 0 Change in message waiting status
+ CNh->>RAN: 1 Message waiting req.ind.
+ RAN->>MT: 2 Message waiting req.ind.
+ MT->>UIM: 3 Message waiting req.ind.
+ RAN->>CNh: 4 Message waiting resp.conf.
+
+```
+
+Sequence diagram for Message waiting notification (MWN) showing interactions between UIM (UIMF), MT (MCF), RAN+CNv (SACF, LMF), and CNh (LMF).
+
+**Figure 10.3.1-1/Q.1721 – Message waiting notification**
+
+0. **Change in message waiting status:** this is the initial stimulus where a messaging system, fax or e-mail server or similar entity reports a change in the MT's voice, fax, e-mail or other message status to the LMFh.
+
+| | |
+|------|--------------------------------------|
+| FEA0 | – Change the message waiting status. |
+|------|--------------------------------------|
+
+1. **Message waiting req.ind.:** for each type of message (voice, fax, e-mail, etc.) a separate req.ind. may be sent. Alternatively, using constructor parameters, information on more than one type of message may be bundled and sent in one req.ind. This scenario illustrates the former mechanism.
+
+| Message waiting (Response: Success) | req.ind. |
+|-------------------------------------|------------|
+| IMUI | M |
+| Message waiting indicator | M (Note 1) |
+| Message waiting type | O (Note 2) |
+| Message priority | O (Note 3) |
+| Messages pending count | O (Note 4) |
+| Preferred language | O (Note 5) |
+
+| | |
+|--------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|
+| FEA1 | – Relay the contents to the SACF so that they can be sent to the MCF. |
+| NOTE 1 – Can have two values "Yes" or "No". | |
+| NOTE 2 – Indicates whether the messages are voice, fax, e-mail or other. | |
+| NOTE 3 – Include to indicate normal (default), interactive, urgent or emergency broadcast. | |
+| NOTE 4 – Indicates the number of pending messages. | |
+| NOTE 5 – Indicates the language to be used if a notification announcement is made. | |
+
+2. **Message waiting req.ind.:** transfers information about the messages waiting to the MCF.
+
+| | |
+|--------------------------------------------------------|-----------------|
+| Message waiting (Response: Success) | req.ind. |
+| < Same information elements as in information flow 1 > | < See IF 1 > |
+
+| | |
+|------|-----------------------------------|
+| FEA2 | – Relay the contents to the UIMF. |
+|------|-----------------------------------|
+
+3. **Message waiting req.ind.:** transfers the message waiting notification to UIMF.
+
+| | |
+|---------------------------------------------------------|-----------------|
+| Message waiting notification (Response: Success) | req.ind. |
+| < Same information elements as in information flow 1 > | < See IF 1 > |
+
+| | |
+|------|-------------------------------------------------------------------------------------------|
+| FEA3 | – Use the received information to provide the specified type of notification to the user. |
+|------|-------------------------------------------------------------------------------------------|
+
+4. **Message waiting resp.conf.:** acknowledgement for message waiting notification.
+
+| | |
+|-------------------------------------|-------------------|
+| Message waiting notification | resp.conf. |
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|--------------------------|
+| FEA6 | – No action is required. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+# 11 Supplementary service procedures
+
+*The following features may not be applicable to all IMT-2000 family members.*
+
+These stand-alone procedures are used to control the supplementary services (SS) of a user. They are initiated by the user7, normally by pressing keys on the mobile terminal.
+
+The following supplementary service procedures are described:
+
+- Get password.
+- Register password.
+- Register SS.
+- Erase SS.
+
+7 The "get password" and "unstructured supplementary service notify" procedures are initiated by the HLR (LMFh), but they are triggered by other supplementary service control procedures previously initiated by the user.
+
+- Activate SS.
+- Deactivate SS.
+- Interrogate SS.
+- Invoke SS.
+- Process unstructured SS request.
+- Unstructured SS request.
+- Unstructured SS notify.
+- SS invocation notification.
+
+## 11.1 Get password
+
+This procedure is initiated by the home network to request a password from the user, when the home network receives a request from the user for a supplementary service control operation that requires a password. This procedure can be used in combination with any of the other supplementary service control procedures, but it will not be shown explicitly in all of them. See Figure 11.1-1.
+
+
+
+Sequence diagram for 'Get password' procedure. Lifelines: MT (MCF), RAN+CNv (SACF, LMF/ACF), CNh (LMF). The sequence starts with 'User initiates SS requiring password' at step 0. Step 1: CNh sends 'Get password req.ind.' to RAN+CNv. Step 2: RAN+CNv sends 'Get password req.ind.' to MT. Step 3: MT sends 'Get password resp.conf.' to RAN+CNv. Step 4: RAN+CNv sends 'Get password resp.conf.' to CNh. Reference T11105930-00.
+
+Figure 11.1-1/Q.1721 – Get password
+
+0. **User initiates SS requiring password:** the LMFh receives a user initiated SS requiring password.
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | - – Detect the need to request a password from the user in response to an initiated SS procedure.
- – Prepare and send a Get password req.ind. to LMF in the visiting network.
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **Get password req.ind.:** is used to request the user to provide a password.
+
+| Get password (Response: Success or Failure) | req.ind. |
+|---------------------------------------------|----------|
+| Guidance information | M |
+
+| | |
+|------|----------------------------------------------------------------------------------------------|
+| FEA1 | - – Relay the Get password req.ind. to SACF.
|
+|------|----------------------------------------------------------------------------------------------|
+
+2. **Get password req.ind.:** is used to request the user to provide a password via the MMI.
+
+| Get password (Response: Success or Failure) | req.ind. |
+|----------------------------------------------------|-----------------|
+| Guidance information | M |
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA2 | - – Interpret the guidance information element and display the relevant information to the user via the MMI.
- – Receive the password from the user via the MMI.
- – Prepare and send a Get Password resp.conf. to SACF, possibly using multiple messages, e.g. for DTMF emulation.
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+3. **Get password resp.conf.:** send the current password and result to the SACF.
+
+| Get password | resp.conf. |
+|---------------------|-------------------|
+| Current password | M |
+| Result | M |
+
+| | |
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA3 | - – Relay the Get password resp.conf. to LMFv.
- – Prepare and send a Get password resp.conf. to the LMFh, possibly using multiple messages, e.g. for DTMF emulation.
|
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+4. **Get password resp.conf.:** send the current password and result to the LMFh.
+
+| Get password | resp.conf. |
+|---------------------|-------------------|
+| Current password | M |
+| Result | M |
+
+| | |
+|------|----------------------------------------------------------------------------------|
+| FEA4 | - – Confirmed password reviewed.
|
+|------|----------------------------------------------------------------------------------|
+
+## 11.2 Register password
+
+This procedure is initiated by the home network to request the old password from the user. When the home network receives the old password, a request will be sent to the user to request the new password. The home network will request one additional time the user to confirm the new password. See Figure 11.2-1
+
+
+
+```
+
+sequenceDiagram
+ participant MT as MT (MCF)
+ participant RAN+CNv as RAN+CNv (SACF, LMF)
+ participant CNh as CNh (LMF)
+
+ Note left of MT: 0
+ Note right of CNh: 0
+ Note right of CNh: Register password request
+ Note left of MT: 1
+ Note right of CNh: 1
+ Note right of CNh: Get password
+ Note left of MT: 2
+ Note right of CNh: 2
+ Note right of CNh: Get password
+ Note left of MT: 3
+ Note right of CNh: 3
+ Note right of CNh: Get password
+ Note right of CNh: T11105940-00
+
+```
+
+Sequence diagram for Figure 11.2-1/Q.1721 – Register password. Lifelines: MT (MCF), RAN+CNv (SACF, LMF), and CNh (LMF). The sequence starts with an external 'Register password request' at step 0. Steps 1, 2, and 3 involve the LMFh in CNh sending 'Get password' messages to the MT via the RAN+CNv.
+
+Figure 11.2-1/Q.1721 – Register password
+
+0. **Register password request:** the user requests to change the password for a supplementary service.
+1. **Get password:** the LMFh requests the old password from the user.
+2. **Get password:** the LMFh requests the user to give the new password.
+3. **Get password:** the LMFh requests the user to give the new password one more time for confirmation.
+
+## 11.3 Register SS
+
+This procedure is used to register data related to a supplementary service in the home network. See Figure 11.3-1.
+
+
+
+```
+
+sequenceDiagram
+ participant MT as MT (MCF)
+ participant RAN+CNv as RAN+CNv (SACF, LMF/ACF)
+ participant CNh as CNh (LMF)
+
+ Note left of MT: 0
+ Note right of MT: User initiates SS registration
+ Note left of MT: 1
+ Note right of RAN+CNv: 1
+ Note right of RAN+CNv: MT register SS req.ind.
+ Note left of RAN+CNv: 2
+ Note right of CNh: 2
+ Note right of CNh: Register SS req.ind.
+ Note left of CNh: 3
+ Note right of CNh: 3
+ Note right of CNh: Register SS resp.conf.
+ Note left of MT: 4
+ Note right of RAN+CNv: 4
+ Note right of RAN+CNv: MT register SS resp.conf.
+ Note right of CNh: T11105950-00
+
+```
+
+Sequence diagram for Figure 11.3-1/Q.1721 – Register SS. Lifelines: MT (MCF), RAN+CNv (SACF, LMF/ACF), and CNh (LMF). The sequence starts with 'User initiates SS registration' at step 0. Step 1: MT sends 'MT register SS req.ind.' to RAN+CNv. Step 2: RAN+CNv sends 'Register SS req.ind.' to CNh. Step 3: CNh sends 'Register SS resp.conf.' to RAN+CNv. Step 4: RAN+CNv sends 'MT register SS resp.conf.' to MT.
+
+Figure 11.3-1/Q.1721 – Register SS
+
+0. **User initiates SS registration:** the MCF receives a user initiated SS registration.
+
+| | |
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | - – Detect user initiated SS control procedure via the MMI to request a registration of a supplementary service.
- – Prepare and send the received information to SACF.
|
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **MT register SS req.ind.:** is used to request to register a supplementary service.
+
+| MT register SS (Response: Success or Failure) | req.ind. |
+|-----------------------------------------------|----------|
+| SS code | M |
+| SS data | M |
+
+| | |
+|------|--------------------------------------------------|
+| FEA1 | – Prepare and send Register SS req.ind. to LMFv. |
+|------|--------------------------------------------------|
+
+2. **Register SS req.ind.:** is used to request the LMFh to register a supplementary service.
+
+| Register SS (Response: Success or Failure) | req.ind. |
+|--------------------------------------------|----------|
+| SS code | M |
+| SS data | M |
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA2 | - – Identify the concerned supplementary service.
- – Store the received SS data according to the command.
- – Prepare and send a Register SS resp.conf. to LMFv.
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+3. **Register SS resp.conf.:** is used to send a response back to the user to inform about the result of the registration.
+
+| Register SS (Response: Success or Failure) | resp.conf. |
+|--------------------------------------------|------------|
+| Result | M |
+
+| | |
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA3 | - – Relay the information to SACF.
- – Prepare and send an MT register SS resp.conf. from SACF.
|
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+4. **MT register SS resp.conf.:** sends the result of the registration of supplementary service to the user.
+
+| MT register SS | resp.conf. |
+|----------------|------------|
+| Result | M |
+
+| | |
+|------|--------------------------------------------------------------------------------------------------------|
+| FEA4 | – Acknowledge to the user that the related data for the supplementary service has been stored in LMFh. |
+|------|--------------------------------------------------------------------------------------------------------|
+
+## 11.4 Erase SS
+
+This procedure is initiated by the user to delete information stored against a particular service by a previous registration in the home network. See Figure 11.4-1.
+
+
+
+Sequence diagram for Erase SS procedure. Lifelines: MT (MCF), RAN+CNv (SACF, LMF/ACF), CNh (LMF). The sequence starts with 'User initiates SS erasure' at time 0. At time 1, MT sends 'MT erase SS req.ind.' to SACF. At time 2, SACF sends 'Erase SS req.ind.' to LMF. At time 3, LMF sends 'Erase SS resp.conf.' back to SACF. At time 4, SACF sends 'MT erase SS resp.conf.' back to MT. The diagram is labeled T11105960-00.
+
+Figure 11.4-1/Q.1721 – Erasure of SS
+
+0. **User initiates SS erasure:** the MCF receives a user initiated SS Erasure.
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | - – Detect user initiated SS control procedure via the MMI to request an erasure of a supplementary service.
- – Prepare and send the received information to SACF.
|
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **MT erase SS req.ind.:** is used to request to erase a supplementary service.
+
+| MT erase SS (Response: Success or Failure) | req.ind. |
+|--------------------------------------------|----------|
+| SS code | M |
+| SS data | O (Note) |
+
+| | |
+|------------------------------------------------------------------------|-----------------------------|
+| FEA1 | – Request to erase SS data. |
+| NOTE – Only requested for such supplementary services which have data. | |
+
+2. **Erase SS req.ind.:** is used to request the LMFh to erase a supplementary service.
+
+| Erase SS (Response: Success or Failure) | req.ind. |
+|-----------------------------------------|----------|
+| SS code | M |
+| SS data | O (Note) |
+
+| | |
+|------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA2 | - – Identify the concerned supplementary service.
- – Erase SS data according to the command.
|
+| NOTE – Only requested for such supplementary services which have data. | |
+
+3. **Erase SS resp.conf.:** is used to send a response back to the user to inform about the result of the erasure.
+
+| Erase SS (Response: Success or Failure) | resp.conf. |
+|-----------------------------------------|------------|
+| Result | M |
+
+| | |
+|------|----------------------------------|
+| FEA3 | – Relay the information to SACF. |
+|------|----------------------------------|
+
+4. **MT erase SS resp.conf.:** sends the result of the erasure of supplementary service to the user.
+
+| MT Erase SS | resp.conf. |
+|-------------|------------|
+| Result | M |
+
+| | |
+|------|-----------------------|
+| FEA4 | – No action required. |
+|------|-----------------------|
+
+## 11.5 Activate SS
+
+This procedure is used to enable a process to run as and when required by the service concerned, resulting in the active phase. Some services can be either "operative" or "quiescent" (not operative) during the active phase according to whether or not the system would be able to invoke or use the service. The information is stored in the home network and for some relevant services is stored in the serving network as well. See Figure 11.5-1.
+
+
+
+```
+
+sequenceDiagram
+ participant MT as MT (MCF)
+ participant RAN as RAN+CNv (SACF, LMF/ACF)
+ participant CNh as CNh (LMF)
+
+ Note left of MT: User initiates SS activation
+ MT->>RAN: MT activate SS req.ind.
+ RAN->>CNh: Activate SS req.ind.
+ CNh-->>RAN: Activate SS resp.conf.
+ RAN-->>MT: MT activate SS resp.conf.
+
+```
+
+The diagram illustrates the sequence of messages for SS activation. It starts with the user initiating activation at the MT (MCF). The MT sends an 'MT activate SS req.ind.' message to the RAN+CNv (SACF). The RAN+CNv then sends an 'Activate SS req.ind.' message to the CNh (LMF). The CNh responds with an 'Activate SS resp.conf.' message back to the RAN+CNv. Finally, the RAN+CNv sends an 'MT activate SS resp.conf.' message back to the MT. The sequence is numbered 0 to 4 on both sides.
+
+Sequence diagram for Activation of SS showing interactions between MT (MCF), RAN+CNv (SACF, LMF/ACF), and CNh (LMF).
+
+Figure 11.5-1/Q.1721 – Activation of SS
+
+0. **User initiates SS activation:** the MCF receives a user initiated SS Activation.
+
+| | |
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | – Detect user initiated SS control procedure via the MMI to request an activation of a supplementary service.
– Prepare and send the received information to SACF. |
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **MT activate SS req.ind.:** is used to request to activate a supplementary service.
+
+| MT activate SS (Response: Success or Failure) | req.ind. |
+|------------------------------------------------------|-----------------|
+| SS code | M |
+| SS data | O (Note) |
+
+| | |
+|------------------------------------------------------------------------|-------------------------|
+| FEA1 | Request to activate SS. |
+| NOTE – Only requested for such supplementary services which have data. | |
+
+2. **Activate SS req.ind.:** is used to request the LMFh to activate a supplementary service.
+
+| Activate SS (Response: Success or Failure) | req.ind. |
+|---------------------------------------------------|-----------------|
+| SS code | M |
+| SS data | O (Note) |
+
+| | |
+|----------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA2 | - – Identify the concerned supplementary service.
- – Activate SS data according to the command.
|
+| NOTE – Only request for such supplementary services which have data. | |
+
+3. **Activate SS resp.conf.:** is used to send a response back to the user to inform about the result of the activation.
+
+| Activate SS (Response: Success or Failure) | resp.conf. |
+|---------------------------------------------------|-------------------|
+| Result | M |
+
+| | |
+|------|----------------------------------|
+| FEA3 | – Relay the information to SACF. |
+|------|----------------------------------|
+
+4. **MT activate SS resp.conf.:** sends the result of the activation of supplementary service to the user.
+
+| MT activate SS | resp.conf. |
+|-----------------------|-------------------|
+| Result | M |
+
+| | |
+|------|-----------------------|
+| FEA4 | – No action required. |
+|------|-----------------------|
+
+## 11.6 Deactivate SS
+
+This procedure is initiated by the user, to terminate the process started at the activation. The information will be stored in the home network and for some relevant services it will be stored in the serving network as well. See Figure 11.6-1.
+
+
+
+```
+
+sequenceDiagram
+ participant MT as MT (MCF)
+ participant RAN_CNv as RAN+CNv (SACF, LMF/ACF)
+ participant CNh as CNh (LMF)
+ Note over MT, RAN_CNv: 0 User initiates SS deactivation
+ MT->>RAN_CNv: 1 MT deactivate SS req.ind.
+ RAN_CNv->>CNh: 2 Deactivate SS req.ind.
+ CNh-->>RAN_CNv: 3 Deactivate SS resp.conf.
+ RAN_CNv-->>MT: 4 MT deactivate SS resp.conf.
+
+```
+
+Sequence diagram showing the deactivation of a supplementary service (SS) between MT, RAN+CNv, and CNh. The sequence starts with the user initiating SS deactivation at the MT (MCF). The MT sends an 'MT deactivate SS req.ind.' to the RAN+CNv (SACF). The SACF then sends a 'Deactivate SS req.ind.' to the CNh (LMF). The LMF responds with 'Deactivate SS resp.conf.' to the SACF, which in turn sends 'MT deactivate SS resp.conf.' back to the MT. The sequence is numbered 0 to 4.
+
+**Figure 11.6-1/Q.1721 – Deactivation of SS**
+
+0. **User initiates SS deactivation:** the MCF receives a user initiated SS deactivation.
+
+| | |
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | - – Detect user initiated SS control procedure via the MMI to request a deactivation of a supplementary service.
- – Prepare and send the received information to SACF.
|
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **MT deactivate SS req.ind.:** is used to request to deactivate a supplementary service.
+
+| MT deactivate SS (Response: Success or Failure) | req.ind. |
+|-------------------------------------------------|----------|
+| SS code | M |
+| SS data | O (Note) |
+
+| | |
+|------------------------------------------------------------------------|---------------------------|
+| FEA1 | Request to deactivate SS. |
+| NOTE – Only requested for such supplementary services which have data. | |
+
+2. **Deactivate SS req.ind.:** is used to request the LMFh to deactivate a supplementary service.
+
+| Deactivate SS (Response: Success or Failure) | req.ind. |
+|----------------------------------------------|----------|
+| SS code | M |
+| SS data | O (Note) |
+
+| | |
+|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA2 | - – Identify the concerned supplementary service.
- – Deactivate SS data according to the command.
|
+| NOTE – Only requested for such supplementary services which have data. | |
+
+3. **Deactivate SS resp.conf.:** is used to send a response back to the user to inform about the result of the deactivation.
+
+| Deactivate SS (Response: Success or Failure) | resp.conf. |
+|----------------------------------------------|------------|
+| Result | M |
+
+| | |
+|------|----------------------------------|
+| FEA3 | – Relay the information to SACF. |
+|------|----------------------------------|
+
+4. **MT deactivate SS resp.conf.:** sends the result of the deactivation of supplementary service to the user.
+
+| MT deactivate SS | resp.conf. |
+|------------------|------------|
+| Result | M |
+
+| | |
+|------|-----------------------|
+| FEA4 | – No action required. |
+|------|-----------------------|
+
+## 11.7 Interrogate SS
+
+This procedure is initiated by the user to provide information about a specific supplementary service. The information is fetched from the home network. See Figure 11.7-1.
+
+
+
+```
+
+sequenceDiagram
+ participant User
+ participant MT as MT (MCF)
+ participant RAN as RAN+CNv (SACF, LMF/ACF)
+ participant CNh as CNh (LMF)
+
+ Note left of MT: 0 User initiates SS interrogation
+ MT->>RAN: 1 MT interrogate SS req.ind.
+ RAN->>CNh: 2 Interrogate SS req.ind.
+ CNh-->>RAN: 3 Interrogate SS resp.conf.
+ RAN-->>MT: 4 MT interrogate SS resp.conf.
+
+```
+
+T11105990-00
+
+Sequence diagram for Interrogation of SS. Lifelines: MT (MCF), RAN+CNv (SACF, LMF/ACF), CNh (LMF). The sequence shows: 0. User initiates SS interrogation to MCF; 1. MT interrogate SS req.ind. from MCF to SACF; 2. Interrogate SS req.ind. from SACF to LMF; 3. Interrogate SS resp.conf. from LMF to SACF; 4. MT interrogate SS resp.conf. from SACF to MCF.
+
+Figure 11.7-1/Q.1721 – Interrogation of SS
+
+0. **User initiates SS interrogation:** the MCF receives a user initiated SS interrogation.
+
+| | |
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | – Detect user initiated SS control procedure via the MMI to request an interrogation of a supplementary service.
– Prepare and send the received information to SACF. |
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **MT interrogate SS req.ind.:** is used to request to retrieve information related to a supplementary service.
+
+| MT interrogate SS (Response: Success or Failure) | req.ind. |
+|---------------------------------------------------------|-----------------|
+| SS code | M |
+| SS data | O (Note) |
+
+| | |
+|------------------------------------------------------------------------|-----------------------------------|
+| FEA1 | – Request to interrogate SS data. |
+| NOTE – Only requested for such supplementary services which have data. | |
+
+2. **Interrogate SS req.ind.:** is used to request the LMFh if necessary to retrieve information related to a supplementary service.
+
+| Interrogate SS (Response: Success or Failure) | req.ind. |
+|------------------------------------------------------|-----------------|
+| SS code | M |
+| SS data | O (Note) |
+
+| | |
+|------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|
+| FEA2 | – Identify the concerned supplementary service.
– Interrogate SS data according to the command. |
+| NOTE – Only requested for such supplementary services which have data. | |
+
+3. **Interrogate SS resp.conf.:** is used to send a response back to the user to inform about the result of the interrogation.
+
+| Interrogate SS (Response: Success or Failure) | resp.conf. |
+|------------------------------------------------------|-------------------|
+| Result | M |
+
+| | |
+|------|----------------------------------|
+| FEA3 | – Relay the information to SACF. |
+|------|----------------------------------|
+
+4. **MT interrogate SS resp.conf.:** sends the result of the retrieved information of supplementary service to the user.
+
+| MT interrogate SS | resp.conf. |
+|--------------------------|-------------------|
+| Result | M |
+
+| | |
+|------|-----------------------|
+| FEA4 | – No action required. |
+|------|-----------------------|
+
+## 11.8 Invoke SS
+
+This procedure is initiated by the user. The procedure is used to check the subscriber's subscription to a given supplementary service in the serving network. See Figure 11.8-1.
+
+
+
+Sequence diagram showing the interaction between MT (Mobile Terminal) and RAN+CNv (Radio Access Network + Core Network). The diagram is divided into three horizontal sections labeled 0, 1, and 2. Section 0 shows 'User initiates SS invocation' pointing to the MT's MCF (Mobile Communication Function). Section 1 shows 'MT invoke SS req.ind.' (request indication) being sent from the MT's MCF to the RAN+CNv's SACF (Service Access Control Function). Section 2 shows 'MT invoke SS resp.conf.' (response confirmation) being sent from the RAN+CNv's SACF back to the MT's MCF. The diagram is labeled T11106000-00 at the bottom right.
+
+Figure 11.8-1/Q.1721 – Invocation of SS
+
+0. **User initiates SS invocation:** the MCF receives a user initiated SS Invocation.
+
+| | |
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | - – Detect user initiated SS control procedure via the MMI to request an invocation of a supplementary service.
- – Prepare and send the received information to SACF.
|
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **MT invoke SS req.ind.:** is used to request to check the subscriber's subscription to a given supplementary service (e.g. call hold or multi-party) in LMFv, in connection with in-call invocation of that supplementary service, i.e. after the call setup phase is finished.
+
+| MT invoke SS (Response: Success or Failure) | req.ind. |
+|---------------------------------------------|----------|
+| SS code | M |
+| SS data | O (Note) |
+
+| | |
+|------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | - – Identify the concerned supplementary service.
- – Checked the subscriber's subscription according to the received information.
- – Prepare and send information to SACF.
|
+| NOTE – Only requested for such supplementary services which have data. | |
+
+2. **MT invoke SS resp.conf.:** sends the result of the checked subscriber's subscription information of supplementary service to the user.
+
+| MT interrogate SS | resp.conf. |
+|-------------------|------------|
+| Result | M |
+
+| | |
+|------|--------------------------------------------------------------------------------------|
+| FEA2 | - – Present the result for the user.
|
+|------|--------------------------------------------------------------------------------------|
+
+## 11.9 Process unstructured SS request
+
+This procedure is used to relay information in order to allow unstructured supplementary service operation. The received network entity passes the data received in the request to the application handling unstructured supplementary service application and waits for response from the application. See Figure 11.9-1.
+
+
+
+Sequence diagram for Process unstructured SS request. Lifelines: MT (MCF), RAN+CNv (SACF, LMF/ACF), CNh (LMF). The sequence starts at 0 with 'User initiates process unstructured SS interrogation'. At 1, MT sends 'MT process unstructured SS req.ind.' to RAN+CNv. At 2, RAN+CNv sends 'Process unstructured SS req.ind.' to CNh. At 3, CNh sends 'Process unstructured SS resp.conf.' back to RAN+CNv. At 4, RAN+CNv sends 'MT process unstructured SS resp.conf.' back to MT. The diagram is labeled T11106010-00.
+
+Figure 11.9-1/Q.1721 – Process unstructured SS request
+
+0. **User initiates process unstructured SS request:** the MCF receives a user initiated process unstructured SS request.
+
+| | |
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | - – Detect user initiated SS control procedure via the MMI to request a process unstructured request of a supplementary service.
- – Prepare and send the received information to SACF.
|
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **MT process unstructured SS req.ind.:** is used to request to allow unstructured supplementary service operation.
+
+| MT process unstructured SS (Response: Success or Failure) | req.ind. |
+|-----------------------------------------------------------|----------|
+| USSD data coding scheme | M |
+| USSD string | M |
+
+| | |
+|------|--------------------------------------------|
+| FEA1 | – Request to Process unstructured SS data. |
+|------|--------------------------------------------|
+
+2. **Process unstructured SS req.ind.:** is used to request the LMFh to process the USSD request.
+
+| Process unstructured SS (Response: Success or Failure) | req.ind. |
+|--------------------------------------------------------|----------|
+| USSD data coding scheme | M |
+| USSD string | M |
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA2 | - – Perform one or more of the following functions as required by service logic.
- – Set up or release speech channels.
- – Pass the request to another network entity (unchanged or changed).
- – Pass a different USSD request to another network entity.
- – Request further information from the user.
|
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+3. **Process unstructured SS resp.conf.**: is used to send a response back to the user to inform about the result of the process unstructured SS request.
+
+| Process unstructured SS (Response: Success or Failure) | resp.conf. |
+|---------------------------------------------------------------|-------------------|
+| USSD data coding scheme | O (Note 1) |
+| USSD string | O (Note 2) |
+| Result | O (Note 3) |
+
+| | |
+|----------------------------------------------------------------------------------------|--------------------------------|
+| FEA3 | Relay the information to SACF. |
+| NOTE 1 – If this IE is present, then the USSD String IE has to be present. | |
+| NOTE 2 – If this IE is present, then the USSD Data Coding Scheme IE has to be present. | |
+| NOTE 3 – Only used if an error situation has occurred. | |
+
+4. **MT process unstructured SS resp.conf.**: sends the result of the retrieved information of supplementary service to the user.
+
+| MT process unstructured SS | resp.conf. |
+|-----------------------------------|-------------------|
+| USSD data coding scheme | O (Note 1) |
+| USSD string | O (Note 2) |
+| Result | O (Note 3) |
+
+| | |
+|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|
+| FEA4 | – Confirmation about allowing unstructured supplementary service operation to be used. |
+| NOTE 1 – If this IE is present, then the USSD String IE has to be present. | |
+| NOTE 2 – If this IE is present, then the USSD Data Coding Scheme IE has to be present. | |
+| NOTE 3 – Only used if an error situation has occurred. | |
+
+## 11.10 Unstructured SS request
+
+This procedure is used by the invoking entity, when information is required from the mobile user, in connection with unstructured supplementary service handling.
+
+In some circumstances the SCFh may generate (or receive) an unstructured SS request towards (or from) the LMFh. This is likely to occur when an operator specific service, which is provided by the home SCF, requires a dialogue with the mobile user. This dialogue may be user initiated or SCF service initiated. The unstructured supplementary service data provides a transparent transport mechanism which enables this mobile user/service dialogue to take place. See Figure 11.10-1.
+
+
+
+Sequence diagram for Unstructured SS request. Lifelines: MT (MCF), RAN+CNv (SACF, LMF/ACF), and CNh (LMF). The sequence starts at time 0 with an 'Unstructured SS request' from CNh. At time 1, 'Unstructured SS request req.ind.' is sent from CNh to LMF/ACF. At time 2, 'MT unstructured SS request req.ind.' is sent from LMF/ACF to MCF. At time 3, 'MT unstructured SS request resp.conf.' is sent from MCF to LMF/ACF. At time 4, 'Unstructured SS request resp.conf.' is sent from LMF/ACF to CNh. The diagram is labeled T11106020-00.
+
+Figure 11.10-1/Q.1721 – Unstructured SS request
+
+0. **Unstructured SS request:** the invoking entity requires information from the mobile user.
+
+| | |
+|------|--------------------------------------------------------------|
+| FEA0 | – Prepare and send Unstructured SS Request req.ind. to LMFv. |
+|------|--------------------------------------------------------------|
+
+1. **Unstructured SS request req.ind.:** is used to request information from the mobile user.
+
+| Unstructured SS request (Response: Success or Failure) | req.ind. |
+|--------------------------------------------------------|----------|
+| USSD data coding scheme | M |
+| USSD string | M |
+| Alerting pattern | O (Note) |
+
+| | |
+|----------------------------------------------------------------------------------------------|--------------------------------------------------------------|
+| FEA1 | – Prepare and send Unstructured SS request req.ind. to SACF. |
+| NOTE – Will be present if received in connect operation from SCFh, otherwise will be absent. | |
+
+2. **MT unstructured SS request req.ind.:** is used to request the mobile user.
+
+| MT unstructured SS request (Response: Success or Failure) | req.ind. |
+|-----------------------------------------------------------|----------|
+| USSD data coding scheme | M |
+| USSD string | M |
+| Alerting pattern | O (Note) |
+
+| | |
+|----------------------------------------------------------------------------------------------|----------------------------------------------------------------------|
+| FEA2 | – Prepare and send an MT unstructured SS request resp.conf. to SACF. |
+| NOTE – Will be present if received in connect operation from SCFh, otherwise will be absent. | |
+
+3. **MT unstructured SS request resp.conf.:** is used to send a response back to the LMFh via SACF and LMFv about the result of the request.
+
+| MT unstructured SS request (Response: Success or Failure) | resp.conf. |
+|------------------------------------------------------------------|-------------------|
+| USSD data coding scheme | O (Note 1) |
+| USSD string | O (Note 2) |
+| Result | O (Note 3) |
+
+| | |
+|----------------------------------------------------------------------------------------|----------------------------------------------------------------------|
+| FEA3 | – Prepare and send an MT unstructured SS request resp.conf. to LMFv. |
+| NOTE 1 – If this IE is present, then the USSD string IE has to be present. | |
+| NOTE 2 – If this IE is present, then the USSD data coding scheme IE has to be present. | |
+| NOTE 3 – Only used if an error situation has occurred. | |
+
+4. **Unstructured SS request resp.conf.:** sends the result of the retrieved information from the mobile user.
+
+| Unstructured SS request | resp.conf. |
+|--------------------------------|-------------------|
+| USSD data coding scheme | O (Note 1) |
+| USSD string | O (Note 2) |
+| Result | O (Note 3) |
+
+| | |
+|----------------------------------------------------------------------------------------|------------------------------------------------------------|
+| FEA4 | – The required information has been fetched from the user. |
+| NOTE 1 – If this IE is present, then the USSD string IE has to be present. | |
+| NOTE 2 – If this IE is present, then the USSD data coding scheme IE has to be present. | |
+| NOTE 3 – Only used if an error situation has occurred. | |
+
+## 11.11 Unstructured SS notify
+
+This procedure is used by the invoking entity, when required a notification to be sent to the mobile user, in connection with unstructured supplementary service handling.
+
+In some circumstances the SCFh may generate (or receive) an unstructured SS notification request towards (or from) the LMFh. This is likely to occur when an operator specific service, which is provided by the home SCF, requires a dialogue with the mobile user. This dialogue may be user initiated or SCF service initiated. The unstructured supplementary service data provides a transparent transport mechanism which enables this mobile user/service dialogue to take place. See Figure 11.11-1.
+
+
+
+Sequence diagram for Unstructured SS notification showing interactions between MT (MCF), RAN+CNv (SACF, LMF/ACF), and CNh (LMF). The sequence starts with an 'Unstructured SS notification' from CNh to MT at step 0. At step 1, CNh sends 'Unstructured SS notify req.ind.' to RAN+CNv. At step 2, RAN+CNv sends 'MT unstructured SS notify req.ind.' to MT. At step 3, MT sends 'MT unstructured SS notify resp.conf.' to RAN+CNv. At step 4, RAN+CNv sends 'Unstructured SS notify resp.conf.' to CNh. The diagram is labeled T11106030-00.
+
+**Figure 11.11-1/Q.1721 – Unstructured SS notification**
+
+0. **Unstructured SS notification:** indicates that a notification is to be sent to the mobile user.
+
+| | |
+|------|-------------------------------------------------------|
+| FEA0 | – Send an unstructured SS notify request to the LMFv. |
+|------|-------------------------------------------------------|
+
+1. **Unstructured SS notify req.ind.:** is used to send information to the mobile user.
+
+| Unstructured SS notify (Response: Success or Failure) | req.ind. |
+|--------------------------------------------------------------|-----------------|
+| USSD data coding scheme | M |
+| USSD string | M |
+| Alerting pattern | O (Note) |
+
+| | |
+|----------------------------------------------------------------------------------------------|-------------------------------------------------------|
+| FEA1 | – Send an unstructured SS notify request to the SACF. |
+| NOTE – Will be present if received in connect operation from SCFh, otherwise will be absent. | |
+
+2. **MT unstructured SS notify req.ind.:** is used to send information to the mobile user.
+
+| MT unstructured SS notify (Response: Success or Failure) | req.ind. |
+|-----------------------------------------------------------------|-----------------|
+| USSD data coding scheme | M |
+| USSD string | M |
+| Alerting pattern | O (Note) |
+
+| | |
+|----------------------------------------------------------------------------------------------|-----------------------------------------------------------|
+| FEA2 | – Send an MT Unstructured SS Notify response to the SACF. |
+| NOTE – Will be present if received in connect operation from SCFh, otherwise will be absent. | |
+
+3. **MT unstructured SS notify resp.conf.:** is used to send a response back to the LMFh via SACF and LMFv about the result of the request.
+
+| MT unstructured SS notify (Response: Success or Failure) | resp.conf. |
+|----------------------------------------------------------|------------|
+| Result | O (Note) |
+
+| | |
+|------------------------------------------------------|-----------------------------------------------------------|
+| FEA3 | – Send an MT Unstructured SS Notify response to the SACF. |
+| NOTE – Only used if an error situation has occurred. | |
+
+4. **Unstructured SS notify resp.conf.:** sends the result of the retrieved information from the mobile user.
+
+| Unstructured SS notify | resp.conf. |
+|------------------------|------------|
+| Result | O (Note) |
+
+| | |
+|------------------------------------------------------|-------------------------------------------------------------|
+| FEA4 | – Confirm that the retrieved information has been received. |
+| NOTE – Only used if an error situation has occurred. | |
+
+## 11.12 SS invocation notification
+
+This procedure is used between the SACF and the SCF at invocation of certain supplementary services by the user. The services are explicit call transfer, call deflection and multi-party service. The SACF checks whether the criteria for sending a notification is fulfilled. If this is the case a notification is sent to the home SCF. If the notification criteria is not fulfilled, the processing of the particular supplementary service continues unchanged and no notification is sent. See Figure 11.12-1.
+
+
+
+```
+
+sequenceDiagram
+ participant RAN+CNv as RAN+CNv (SACF)
+ participant CNh as CNh (SCF)
+ Note left of RAN+CNv: 0 SS invoked by user
+ Note right of CNh: 0
+ Note left of RAN+CNv: 1
+ Note right of CNh: 1
+ RAN+CNv->>CNh: SS invocation notification req.ind.
+ Note right of CNh: 2
+ Note left of RAN+CNv: 2
+ CNh->>RAN+CNv: SS invocation notification resp.conf.
+ Note right of CNh: T11106040-00
+
+```
+
+Sequence diagram showing the interaction between RAN+CNv (SACF) and CNh (SCF) for SS invocation notification. The sequence starts at 0 with 'SS invoked by user' at the SACF. At 1, 'SS invocation notification req.ind.' is sent from SACF to SCF. At 2, 'SS invocation notification resp.conf.' is sent from SCF back to SACF. The diagram is labeled T11106040-00.
+
+Figure 11.12-1/Q.1721 – Invocation notification
+
+0. **SS invoked by user:** the SACF receives a user initiated SS invocation.
+
+| | |
+|------|------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | – Detect invocation of a certain supplementary service.
– Prepare and send an SS Invocation Notification req.ind. to SCF. |
+|------|------------------------------------------------------------------------------------------------------------------------------|
+
+1. **SS invocation notification req.ind.:** is used when a subscriber invokes a certain supplementary service.
+
+| SS invocation notification (Response: Success or Failure) | req.ind. |
+|------------------------------------------------------------------|-----------------|
+| MS ISDN | M |
+| IMUI | M |
+| SS-Event | M |
+| SS-Data | O (Note) |
+
+| | |
+|-----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | - – If the information received is understood, prepare and send a positive acknowledgement SS invocation notification resp.conf.
- – If the information received is not understood, prepare and send a negative acknowledgement SS invocation notification resp.conf.
|
+| NOTE – Not all supplementary services contain data. | |
+
+2. **SS invocation notification resp.conf.:** sends the result of the invocation notification back to SACF.
+
+| SS invocation notification | resp.conf. |
+|-----------------------------------|-------------------|
+| Result | M |
+
+| | |
+|------|-----------------------------------------------------------------------|
+| FEA2 | – Confirm the completion of the SS invocation notification procedure. |
+|------|-----------------------------------------------------------------------|
+
+# 12 Over-the-air services
+
+*The following feature may not be applicable to all IMT-2000 family members.*
+
+## 12.1 Over-the-air service provisioning (OTASP)
+
+This clause provides information flow diagrams for one of the Over-the-Air (OTA) services called Over-the-Air Service Provisioning (OTASP) for IMT-2000 systems.
+
+## 12.2 Overview
+
+The OTASP feature meets a need of the IMT-2000 based wireless industry to enable and expedite, in a secure manner, the process by which potential IMT-2000 service subscribers can activate (i.e. become authorized for) new wireless service(s). In addition, current subscribers can request changes in their existing service without third party intervention. An integral component of this process is the over-the-air functionality in the CNh.
+
+One of the primary objectives of OTASP is the ability to provide a secure authentication key to a UIM to facilitate authentication. Authentication is the process by which information is exchanged between a UIM and the network for the purpose of confirming and validating the identity of the UIM.
+
+The OTASP feature incorporates a cryptographic Authentication Key Generation procedure. This procedure allows the network to exchange Authentication Key parameters with a UIM. These parameters are used to generate the A-key. The Authentication Key Generation procedure enhances security for the subscriber (i.e. voice and data ciphering can be enabled to allow for the secure transfer of a new subscriber's credit/financial and IMUI information). It reduces the potential for fraudulent use of the IMT-2000 telecommunication service.
+
+## 12.3 Description
+
+OTASP information flows illustrate the following logical progression of events:
+
+- **Invocation of activation with desired service provider:** Where an "attachment" occurs between the serving CNv and the over-the-air functionality (modelled in the SCF and depicted in the information flows as SCFOTA) in the desired service provider's CN, and a correlation between the voice path (user to Customer Representative (CR), or a Voice Response Unit (VRU), at the Customer Service Centre (CSC)) and the data path (between the UIM and the over-the-air functionality) is established. The mobile terminal performs the initial system access based on a preferred system selection list that is pre-loaded within the UIMF. The user dials the prescribed OTASP digits to initiate the activation process. The visited network will need to be able to recognize and process the received digits from the mobile terminal in order to initiate the OTASP session. Based on the digits, the visited network will need to recognize that this is an OTASP origination and route the call appropriately to the CSC. This special handling of the received digits will require a bilateral business agreement between the home and visited systems, which is outside the scope of this Recommendation.
+- **A-key generation:** Where the Authentication Key is separately generated in the AMF and the UIMF. The A-key is then used for ciphering and security during the OTASP process.
+- **Re-authentication for voice and signalling ciphering:** This process computes and transfers ciphering information to the CNv to invoke ciphering of user plane (voice) and control plane (signalling messages) data prior to the exchange over the air of sensitive financial and provisioning information.
+- **Transfer of OTASP data:** Where the actual provisioning information is transferred between the home network and the UIM.
+
+## 12.4 Over-the-air service provisioning information flows
+
+### 12.4.1 Invocation of activation with desired service provider
+
+A potential subscriber ("user") wants to have an IMT-2000 mobile terminal activated in a desired service provider's network (the "home" network), while in another network (the "visited" network). This information flow shows the first step in OTASP called the "attachment" process whereby the user's voice call is correlated with the data path and the necessary information is downloaded to the UIM. The user's voice call origination is redirected from the visited network to a Customer Representative (CR – a human) or a Voice Response Unit (VRU – a machine), at the Customer Service Centre (CSC) in the home network. The visited network assigns a Temporary Reference Number (TRN) for voice and data path correlation. The TRN pool is administered via bilateral agreements between partnering service providers in order to maintain uniqueness of TRNs used in each visited network. The home network assigns an "activation" IMUI that is used during the activation process. See Figure 12.4-1.
+
+
+
+```
+
+sequenceDiagram
+ participant UIM as UIMF
+ participant MT as MCF
+ participant RAN+CNv as SACF, CCF/SSF
+ participant CNh as SCF_OTA, CCF/SSF
+
+ Note left of UIM: User requests activation
+ MT->>RAN+CNv: Setup req.ind.
+ RAN+CNv-->>MT: Setup resp.conf.
+ Note right of MT: Call delivery to initial CSC
+ Note right of MT: User dialog
+ Note right of RAN+CNv: Call extended to desired CSC
+ Note right of MT: User dialog
+ RAN+CNv->>CNh: Forward activation IMUI req.ind.
+ CNh-->>RAN+CNv: Forward activation IMUI resp.conf.
+ RAN+CNv->>CNh: Release TRN req.ind.
+ CNh-->>RAN+CNv: Release TRN resp.conf.
+
+```
+
+Sequence diagram showing the invocation of activation with desired service provider information flow. Lifelines: UIM (UIMF), MT (MCF), RAN+CNv (SACF, CCF/SSF), CNh (SCF\_OTA, CCF/SSF). The sequence starts with 'User requests activation' at step 0, followed by 'Setup req.ind.' at step 1, 'Setup resp.conf.' at step 2, 'Call delivery to initial CSC' at step 3, 'User dialog' at step 4, 'Call extended to desired CSC' at step 5, 'User dialog' at step 6, 'Forward activation IMUI req.ind.' at step 7, 'Forward activation IMUI resp.conf.' at step 8, 'Release TRN req.ind.' at step 9, and 'Release TRN resp.conf.' at step 10.
+
+**Figure 12.4-1/Q.1721 – Invocation of activation with desired service provider information flow diagram**
+
+0. **User requests activation:** is the initial stimulus where the user desires activation but happens to be on a system other than the system of choice.
+
+| | |
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | - – The user initiates the process by making an OTASP call origination, i.e. by dialling the appropriate digits for activation (for e.g. a local Feature Service Code and directory number, as advertised or per the package instructions with the mobile terminal).
- – The MCF requests a bearer channel to establish the call to the local CSC.
|
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **Setup req.ind.:** is from the MCF to the CCF/SSF in the CNv. Upon receiving the OTASP call origination digits that the user had entered, the MCF sends the dialled digits to the CCF/SSF in the CNv.
+
+| Setup (Response: Success) | req.ind. |
+|---------------------------|----------|
+| Initial IMUI (INIT_IMUI) | M (Note) |
+
+| | |
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | - – Upon receiving the digits string and recognizing the local Feature Service Code as an OTASP attempt, the CNv may bypass or may perform normal network access authorization or subscriber validation and authentication prior to proceeding. Irrespective of the outcome of this procedure, the CNv connects the voice call to a local CSC (Customer Service Centre).
- – The CCF/SSF allocates a unique TRN (Temporary Reference Number) for this OTASP session.
- – The CNv transfers the TRN to the CSC during call setup. Note that the TRN may be sent as a Calling Number or a Called Number based on the signalling schemes used.
- – The CCF/SSF grants a bearer channel to carry the call.
|
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+NOTE – INIT\_IMUI is the IMUI placed in the UIM at manufacture time. It is short-lived and is replaced by the Newly Assigned IMUI (NEW\_IMUI) that is granted by the CNh, prior to the conclusion of the OTASP session.
+
+2. **Setup resp.conf.:** is from the CCF/SSF to the MCF.
+
+| Setup | resp.conf. |
+|-----------|------------|
+| Bearer ID | M |
+
+| | |
+|------|--------------------------------------------------------------------------------------|
+| FEA2 | – The MCF acquires the granted bearer channel and proceeds with completing the call. |
+|------|--------------------------------------------------------------------------------------|
+
+3. **Call delivery to initial CSC:** the call connection between the user and the CSC associated with the CNv is made.
+
+4. **Dialogue between user and initial CSC's CR or VRU:** a customer representative or a voice response unit at the CNv's CSC begins a dialogue with the user.
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA4 | - – The customer representative or a voice response unit at the CSC determines that the user desires to have the MT activated on another CN, which would then become the user's home CN (CNh).
- – Since a business agreement exists between the operator of the CNv and the CNh, the CSC initiates a call re-route to the CSC in the desired CNh.
- – The initial CSC may make use of an internal look-up table to obtain the address of the desired CSC to re-route the call. No dialling number will be allowed from the user to avoid fraud.
|
+|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+5. **Call extended to desired CSC:** the customer representative or a voice response unit at the CSC obtains information from the user regarding the system that he/she desires to be connected to.
+
+| | |
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA5 | - – The CSC customer representative or a voice response unit then extends the voice call to another CSC (assuming that business agreements for such a transfer exist) that is associated with the desired service provider (operator).
- – Forwards the TRN to the new CSC.
|
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+6. **Dialogue between user and desired CSC's CR or VRU:** a customer representative or a voice response unit at the desired CSC begins a dialogue with the user.
+
+| | |
+|------|------------------------------------------------------------------------------------------------------------------------------|
+| FEA6 | – The CSC then contacts the desired over-the-air functionality to activate service provisioning via the SCF OTA . |
+|------|------------------------------------------------------------------------------------------------------------------------------|
+
+7. **Forward activation IMUI req.ind.:** is from the SCFOTA in the home network to the SACF in the visited network. The CSC representative causes the SCFOTA to initiate this flow. The CNh is able to determine the routing address of the CNv from the TRN previously provided. This flow requests the SACF to attach to the CNh for this OTASP session. The CNh also assigns an "activation" IMUI to be used only during this OTASP session.
+
+| Forward activation IMUI (Response: Success) | req.ind. |
+|----------------------------------------------------|-----------------|
+| Activation IMUI (ACT_IMUI) | M (Note 1) |
+| Temporary reference number (TRN) | M (Note 2) |
+| Action code (ACTCODE) | M (Note 3) |
+
+| | |
+|------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA7 | – The CNv associates the call in question with the CNh, and thus a correlation between the voice path and the signalling path is established. |
+| NOTE 1 – The ACT_IMUI is only used for this OTASP session. | |
+| NOTE 2 – The TRN is used to associate the CNh with this OTASP call. | |
+| NOTE 3 – The ACTCODE instructs the SACF to attach to this CNh for this call. | |
+
+8. **Forward activation IMUI resp.conf.:** is from the SACF in the visited network to the SCFOTA in the home network.
+
+| Forward activation IMUI | resp.conf. |
+|-----------------------------------------------|-------------------|
+| INIT_IMUI | M (Note 1) |
+| CNv identity (CNv ID) | M (Note 2) |
+| CNv authentication capabilities (CNv_AUTHCAP) | M (Note 3) |
+| Authorization denied (AUTHDEN) | O (Note 4) |
+
+| | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA8 | – The CNh informs the CSC that the attachment with the CNv has been accomplished.
– The CSC informs the CNh that it should direct the CNv to release the TRN. |
+| NOTE 1 – The INIT_IMUI is received from the UIM at call setup and used for A-key Generation. | |
+| NOTE 2 – The CNv ID is needed to route messages back to the CNv later in the OTASP process. | |
+| NOTE 3 – The CNv_AUTHCAP informs the CNh about the CNv's authentication capabilities, used for Re-Authentication. | |
+| NOTE 4 – Include the AUTHDEN if this UIM had previously (in Step 2) been denied network access authorization or failed subscriber validation and authentication. | |
+
+9. **Release TRN req.ind.:** is from the SCFOTA in the home network to the SACF in the visited network. The CSC representative causes the SCFOTA to initiate this flow. Since the attachment of the mobile terminal to the desired system (CSC and CNh) has completed successfully, the TRN is no longer needed, and the CNh decides to release the TRN (a potentially limited resource) so that it can be reused.
+
+| Release TRN (Response: Success) | req.ind. |
+|----------------------------------------|-----------------|
+| ACT_IMUI | M |
+| ACTCODE | M (Note) |
+
+| | |
+|-----------------------------------------------------------|----------------------------------------------------------------------------------------------------|
+| FEA9 | – The SACF in the CNv releases the TRN, thus permitting it to be reused for another OTASP session. |
+| NOTE – The ACTCODE instructs the SACF to release the TRN. | |
+
+10. **Release TRN resp.conf.:** is from the SACF in the visited network to the SCFOTA in the home network.
+
+| Release TRN | resp.conf. |
+|--------------------|-------------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|
+| FEA10 | – The SACF acknowledges the instruction after having released the TRN.
– This concludes the attachment process. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+### 12.4.2 A-key generation
+
+Prior to activating the user's IMT-2000 mobile terminal, secure voice and data paths have to be established. This is done by generating identical authentication keys (A-key) separately in the network (LMF) and the UIM (UIMF), using a public encryption method (such as the Diffie-Hellman algorithm; see Appendix II for a description). The A-key (never sent over the air) is then used to produce the necessary masks needed to establish voice and data ciphering. This information flow shows how the A-key is generated for IMT-2000 OTASP. See Figure 12.4-2.
+
+
+
+```
+
+sequenceDiagram
+ participant UIM as UIM (UIMF)
+ participant MT as MT (MCF)
+ participant RAN_CNv as RAN+CNv (SACF)
+ participant CNh as CNh (SCF_OTA, LMF/AMF)
+ Note right of CNh: 0 Initiate A-key generation
+ CNh->>RAN_CNv: 1 UIM key request req.ind.
+ RAN_CNv->>UIM: 2 UIM key request req.ind.
+ UIM->>RAN_CNv: 3 UIM key request resp.conf.
+ RAN_CNv->>CNh: 4 UIM key request resp.conf.
+ CNh->>RAN_CNv: 5 Generate A-key req.ind.
+ RAN_CNv->>UIM: 6 Generate A-key req.ind.
+ UIM->>RAN_CNv: 7 Generate A-key resp.conf.
+ RAN_CNv->>CNh: 8 Generate A-key resp.conf.
+
+```
+
+The diagram illustrates the information flow for A-key generation. It features four lifelines: UIM (UIMF), MT (MCF), RAN+CNv (SACF), and CNh (SCFOTA and LMF/AMF). The sequence starts at step 0 with an external stimulus 'Initiate A-key generation' to the CNh. Step 1 shows a 'UIM key request req.ind.' message from CNh to RAN+CNv. Step 2 shows the same message being forwarded from RAN+CNv to UIM. Step 3 shows a 'UIM key request resp.conf.' message from UIM to RAN+CNv. Step 4 shows this response being forwarded from RAN+CNv to CNh. Step 5 shows a 'Generate A-key req.ind.' message from CNh to RAN+CNv. Step 6 shows this request being forwarded from RAN+CNv to UIM. Step 7 shows a 'Generate A-key resp.conf.' message from UIM to RAN+CNv. Step 8 shows this response being forwarded from RAN+CNv to CNh. The diagram is labeled with 'T11106060-00' at the bottom right.
+
+Sequence diagram showing A-key generation information flow between UIM, MT, RAN+CNv, and CNh. The diagram includes 9 steps (0-8) showing the initiation and response of the A-key generation process.
+
+**Figure 12.4-2/Q.1721 – A-key generation information flow diagram**
+
+0. **Initiate A-key generation process:** is the initial stimulus where the CSC initiates the authentication key generation procedure.
+
+| | |
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | - – The CSC initiates the A-key Generation process.
- – The over-the-air functionality sends the LMFh a request, which includes the authentication key protocol version, corresponding to the UIM's A-key generation capabilities8, the UIM's IMUI, and the activation IMUI.
- – The LMFh responds by returning the authentication key protocol version it will use, and public keys called Modulus Value (N*) and Primitive Value (g*). It also includes the CN Key Value (Y*), which the over the air functionality stores.
|
+|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **UIM key request req.ind.:** is from the SCFOTA in the home network to the SACF in the visited network. The CSC representative causes the SCFOTA to initiate this flow. It includes the authentication key protocol version and the public keys. The over-the-air functionality stores the CN Key Value, and does not send it to the SACF.
+
+8 The Diffie-Hellman algorithm is modelled here, since it is publicly available for use, and is scalable, allowing for various combinations of exponents and public encryption values (modulus and primitive) to be used to meet the degree of security desired by the operator.
+
+| UIM key request (Response: Success) | req.ind. |
+|----------------------------------------------|-----------------|
+| Authentication key protocol version (AKEYPV) | M (Note) |
+| Modulus value (MODVAL) | M |
+| Primitive value (PRIMVAL) | M |
+
+| | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|
+| FEA1 | – The SACF in the CNv relays the contents so that they can be sent over the radio interface. |
+| NOTE – The AKEYPV provides the authentication key protocol version corresponding to the specific combination of the Modulus Value ( $N^*$ ), the Primitive Value ( $g^*$ ) and the Exponent ( $y^*$ ), which the CNh (and the UIM) will use, as desired by the operator. | |
+
+2. **UIM key request req.ind.:** is from the SACF in the visited network to the UIMF via the MCF. The SACF merely forwards the contents it had received in Step 1 from the over-the-air functionality, to the UIMF.
+
+| UIM key request (Response: Success) | req.ind. |
+|----------------------------------------------|-----------------|
+| Authentication key protocol version (AKEYPV) | M |
+| Modulus value (MODVAL) | M |
+| Primitive value (PRIMVAL) | M |
+
+| | |
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA2 | – The UIMF successfully computes the UIM Key value ( $X^*$ ) based on the received public key values: MODVAL and PRIMVAL, and the Exponent, as specified by the authentication key protocol version. |
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+3. **UIM key request resp.conf.:** This flow is from the UIMF (via the MCF) to the SACF in the visited network. The UIMF successfully computes the UIM Key Value and indicates this fact to the SACF in the CNv.
+
+| UIM key request | resp.conf. |
+|------------------------|-------------------|
+| Result | M (Note) |
+
+| | |
+|----------------------------------------------------------------------------------------|------------------------------------------------------------------------------|
+| FEA3 | – The SACF in the CNv relays the contents to the over-the-air functionality. |
+| NOTE – The Result indicates that the UIMF has successfully computed the UIM Key Value. | |
+
+4. **UIM key request resp.conf.:** is from the SACF in the visited network to the SCFOTA in the home network. The SACF merely forwards the contents it had received in Step 3 from the UIMF, to the over-the-air functionality.
+
+| UIM key request | resp.conf. |
+|------------------------|-------------------|
+| Result | M |
+
+| | |
+|------|------------------------------------------------------------------------|
+| FEA4 | – The over-the-air functionality in the CNh computes the CN Key Value. |
+|------|------------------------------------------------------------------------|
+
+5. **Generate A-key req.ind.:** is from the SCFOTA in the home network to the SACF in the visited network. The CSC representative causes the SCFOTA to initiate this flow. The over-the-air functionality includes the CN Key Value (Y\*) that the over-the-air functionality had stored in Step 1.
+
+| Generate A-key (Response: Success) | req.ind. |
+|------------------------------------|----------|
+| CN key value (CNKEY) | M |
+
+| | |
+|------|----------------------------------------------------------------------------------------------|
+| FEA5 | – The SACF in the CNv relays the contents so that they can be sent over the radio interface. |
+|------|----------------------------------------------------------------------------------------------|
+
+6. **Generate A-key req.ind.:** is from the SACF in the visited network to the UIMF (via the MCF). The SACF merely forwards the contents it had received in Step 5 from the over-the-air functionality, to the UIMF.
+
+| Generate A-key (Response: Success) | req.ind. |
+|------------------------------------|----------|
+| CNKEY | M |
+
+| | |
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA6 | – The UIMF successfully computes the Authentication Key using the CNKEY, MODVAL and the same Exponent it had used when computing the UIM Key Value. |
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+
+7. **Generate A-key resp.conf.:** is from the UIMF (via the MCF) to the SACF in the visited network. The UIMF has successfully computed the A-key Value and indicates this fact to the SACF in the CNv. It sends the computed UIM Key Value to the SACF, but not the A-key Value (which is never sent over the air).
+
+| Generate A-key | resp.conf. |
+|------------------------|------------|
+| Result | M (Note) |
+| UIM key value (UIMKEY) | M |
+
+| | |
+|--------------------------------------------------------------------------------------|-------------------------------------------------------------------|
+| FEA7 | – The SACF relays the contents to the over-the-air functionality. |
+| NOTE – The Result indicates that the UIMF has successfully computed the A-key Value. | |
+
+8. **Generate A-key resp.conf.:** this flow is from the SACF in the visited network to the SCFOTA in the home network. The SACF merely forwards the contents it had received in Step 7 from the UIMF, to the over-the-air functionality.
+
+| Generate A-key | resp.conf. |
+|----------------|------------|
+| Result | M |
+| UIMKEY | M |
+
+| | |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA8 | – The over-the-air functionality directs the LMFh to generate the A-key also, using the received UIMKEY, the MODVAL and the same Exponent used in Step 1 to compute the CNKEY.
– Thus both the UIM and the CNh generate identical A-keys.
|
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+### 12.4.3 Re-authentication for voice and signalling ciphering
+
+This scenario describes UIM re-authentication for the purpose of computing and sending encryption parameters to the CNv. These parameters are used to invoke signalling message encryption and voice privacy, respectively, over the air interface. See Figure 12.4-3.
+
+
+
+```
+
+sequenceDiagram
+ participant UIMF as UIMF
+ participant MCF as MCF
+ participant SACF as SACF
+ participant SCF_OTA as SCF_OTA
+ participant LMF_AMF as LMF/AMF
+
+ Note right of SACF: Re-authentication
+ SACF->>SCF_OTA: Re-authenticate req.ind.
+ SCF_OTA->>SACF: Re-authenticate req.ind.
+ SACF->>MCF: Re-authenticate resp.conf.
+ MCF->>SCF_OTA: Re-authenticate resp.conf.
+ SCF_OTA->>SACF: Ciphering values req.ind.
+ SACF->>SCF_OTA: Ciphering values resp.conf.
+ SCF_OTA->>SACF: Ciphering status req.ind.
+ SACF->>SCF_OTA: Ciphering status resp.conf.
+
+```
+
+T11106070-00
+
+Sequence diagram showing the information flow for re-authentication and ciphering. Lifelines: UIM (UIMF), MT (MCF), RAN+CNv (SACF), CNh (SCF\_OTA, LMF/AMF). The sequence starts with a 'Re-authentication' stimulus to SCF\_OTA, followed by 'Re-authenticate req.ind.' from SCF\_OTA to SACF, then to UIMF. Responses 'Re-authenticate resp.conf.' are sent back from UIMF to SACF, then to SCF\_OTA. Finally, 'Ciphering values req.ind.', 'Ciphering values resp.conf.', 'Ciphering status req.ind.', and 'Ciphering status resp.conf.' are exchanged between SCF\_OTA and SACF.
+
+Figure 12.4-3/Q.1721 – Re-Authentication for voice and signalling ciphering information flow diagram
+
+0. **Re-authentication:** is the initial stimulus where the CSC initiates the re-authentication procedure.
+
+| | |
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | - – The CSC initiates the re-authentication process.
- – It determines that ciphering is needed over the radio interface.
- – The over-the-air functionality generates a Random challenge value (RAND) and sends it to the SACF.
|
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **Re-authenticate req.ind.:** is from the SCFOTA in the home network to the SACF in the visited network. The CSC representative causes the SCFOTA to initiate this flow. The over-the-air functionality generates a Random Challenge Value (RAND) and sends it to the SACF. The purpose is to authenticate the UIM (again, as it were) following A-key generation, to ensure that the correct UIM is still involved in the OTASP process, prior to turning on ciphering.
+
+| Re-authenticate (Response: Success) | req.ind. |
+|--------------------------------------------|-----------------|
+| Random challenge value (RAND) | M (Note) |
+
+| | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|
+| FEA1 | – The SACF in the CNv relays the contents to the UIMF via the MCF. |
+| NOTE – The RAND is used by the UIMF to respond with a corresponding result that will allow the CNh to determine that the UIM has re-authenticated correctly. | |
+
+2. **Re-authenticate req.ind.:** is from the SACF in the visited network to the UIMF (via the MCF). The SACF merely forwards the contents it had received in Step 1 from the over-the-air functionality, to the UIMF.
+
+| Re-authenticate (Response: Success) | req.ind. |
+|--------------------------------------------|-----------------|
+| RAND | M |
+
+| | |
+|------|-------------------------------------------------------------------------------------------------------------|
+| FEA2 | – The UIMF successfully computes a corresponding response that indicates it has re-authenticated correctly. |
+|------|-------------------------------------------------------------------------------------------------------------|
+
+3. **Re-authenticate resp.conf.:** is from the UIMF (via the MCF) to the SACF in the visited network. The UIMF performs re-authentication and computes a corresponding Random Challenge Response (RANDC) value based on the received RAND, its own IMUI and other attributes. The computation may be based on an algorithm understood exclusively by the UIMF and the CNh.
+
+| Re-authenticate | resp.conf. |
+|-----------------------------------|-------------------|
+| Random challenge response (RANDC) | M |
+
+| | |
+|------|----------------------------------------------------------------------------------------------------------|
+| FEA3 | – The SACF in the CNv relays the contents to the over-the-air functionality via the SCF OTA . |
+|------|----------------------------------------------------------------------------------------------------------|
+
+4. **Re-authenticate resp.conf.:** is from the SACF to the SCFOTA in the visited network.
+
+| Re-authenticate | resp.conf. |
+|------------------------|-------------------|
+| RANDC | M |
+
+| | |
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA4 | - – The over-the-air functionality forwards the information to the LMFh, along with the RAND value.
- – The LMFh independently computes a RANDC using the algorithm as in Step 3.
- – The LMFh compares it with the received RANDC.
- – The LMFh determines that the UIM has been re-authenticated correctly.
- – The LMFh then initiates the generation of ciphering related values.
|
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+5. **Ciphering values req.ind.:** is from the LMFh in the home network to the SACF in the visited network. Having determined that the UIM has been correctly re-authenticated, the LMFh computes the ciphering values and sends them to the SACF.
+
+| Ciphering values (Response: Success) | req.ind. |
+|---------------------------------------------|-----------------|
+| CNv identity (CNv ID) | M (Note 1) |
+| Control plane cipher key (CPCKEY) | M (Note 2) |
+| User plane cipher key (UPCKEY) | M (Note 3) |
+
+| | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|
+| FEA5 | – The SACF in the CNv uses the CPCKEY and UPCKEY to turn on ciphering. |
+| NOTE 1 – The CNv ID is used to route the Ciphering Values req.ind. to the correct SACF.
NOTE 2 – This is used to turn on ciphering of control plane information such as signalling messages.
NOTE 3 – This is used to turn on ciphering of user plane information such as voice. | |
+
+6. **Ciphering values resp.conf.:** is from the SACF in the visited network to the LMFh in the home network.
+
+| Ciphering values | resp.conf. |
+|-------------------------|-------------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|
+| FEA6 | The LMFh in the CNh has indication that the ciphering values have successfully reached the SACF. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+7. **Ciphering status req.ind.:** this flow is from the SACF in the visited network to the LMFh in the home network. User plane ciphering (voice) or control plane ciphering (signalling messages) or both get turned on over the radio interface.
+
+| Ciphering status (Response: Success) | req.ind. |
+|---------------------------------------------|-----------------|
+| Control plane ciphering report (CPCRPT) | M (Note 1) |
+| User plane ciphering report (UPCRPT) | M (Note 2) |
+
+| | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|
+| FEA7 | – The LMFh in the CNh has information regarding the current status of ciphering over the radio interface. |
+| NOTE 1 – This informs whether or not control plane ciphering has turned on.
NOTE 2 – This informs whether or not user plane ciphering has turned on. | |
+
+8. **Ciphering status resp.conf.:** this flow is from the SACF in the visited network to the LMFh in the home network. The LMFh forwards this information to the over-the-air functionality which then provides an indication to the CSC representative in the CNh if it is now safe to exchange sensitive user data over the air.
+
+| Ciphering status | resp.conf. |
+|------------------|------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA8 | - – The LMFh in the CNh forwards this information to the over-the-air functionality.
- – This indicates to the CSC if it is now safe to exchange data over the air.
- – Hence, the CSC and the subscriber exchange sensitive (financial, etc.) information.
- – This concludes the re-authentication process.
|
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+### 12.4.4 Transfer of OTASP data
+
+This scenario describes the exchange of OTASP Data Messages which carry the actual activation related information, between the over-the-air functionality in the CNh, and the UIMF via the MCF and the SACF in the CNv. This is typically done after ciphering has been turned on. See Figure 12.4-4.
+
+
+
+```
+
+sequenceDiagram
+ participant CSC as CSC
+ participant CNh as CNh (SCF_OTA)
+ participant CNv as CNv (SACF)
+ participant MT as MT (MCF)
+ participant UIM as UIM (UIMF)
+
+ Note right of CNh: 0 Initiate OTASP data exchange process
+ CNh->>CNv: 1 OTASP data exchange req.ind.
+ CNv->>MT: 2 OTASP data exchange req.ind.
+ MT->>CNv: 3 OTASP data exchange resp.conf.
+ CNv->>CNh: 4 OTASP data exchange resp.conf.
+
+```
+
+Sequence diagram showing OTASP data exchange flow between UIM, MT, RAN+CNv, and CNh. The diagram shows four steps: 0. Initiate OTASP data exchange process (from CSC to SCF\_OTA), 1. OTASP data exchange req.ind. (from SCF\_OTA to SACF), 2. OTASP data exchange req.ind. (from SACF to MCF), 3. OTASP data exchange resp.conf. (from MCF to SACF), 4. OTASP data exchange resp.conf. (from SACF to SCF\_OTA).
+
+Figure 12.4-4/Q.1721 – OTASP data exchange information flow diagram
+
+0. **Initiate OTASP data exchange process:** is the initial stimulus where the CSC representative causes the SCFOTA to initiate the OTASP Data Exchange procedure.
+
+| | |
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA0 | - – The CSC initiates the OTASP Data Exchange process.
- – Having confirmed that ciphering is present over the radio interface, it prompts the over-the-air functionality to send OTASP related data to the SACF in the CNv.
- – This includes the Newly Assigned IMUI for downloading into the UIMF and other supplementary service related information.
|
+|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+1. **OTASP data exchange req.ind.:** is from the SCFOTA in the home network to the SACF in the visited network.
+
+| OTASP data exchange (Response: Success) | req.ind. |
+|------------------------------------------------|-----------------|
+| Newly assigned IMUI (NEW_IMUI) | M (Note 1) |
+| ACTCODE | M (Note 2) |
+
+| | |
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA1 | - – The SACF in the CNv relays the contents to the UIMF via the MCF.
- – The SACF also releases any resources when the OTASP session is completed.
|
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+NOTE 1 – The NEW\_IMUI is the permanent identity assigned and committed into the user's UIM.
+
+NOTE 2 – Depending on the data exchange case, the ACTCODE can variously instruct the:
+
+- SACF to send the NEW\_IMUI to the UIMF;
+- UIMF to commit the NEW\_IMUI to its permanent memory;
+- UIM to re-register the user after the NEW\_IMUI has been committed to its permanent memory;
+- SACF and UIMF to release resources after completing the OTASP tasks.
+
+2. **OTASP data exchange req.ind.:** this flow is from the SACF in the visited network to the UIMF (via the MCF).
+
+| OTASP data exchange (Response: Success) | req.ind. |
+|------------------------------------------------|-----------------|
+| Newly assigned IMUI (NEW_IMUI) | M |
+
+| | |
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA2 | - – The UIMF replaces the ACT_IMUI with the NEW_IMUI.
- – It commits the NEW_IMUI to permanent memory.
- – It uses the Terminal Registration Procedure to re-register the user.
|
+|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+3. **OTASP data exchange resp.conf.:** this flow is from the UIMF (via the MCF) to the SACF in the visited network.
+
+| OTASP data exchange | resp.conf. |
+|----------------------------|-------------------|
+| None | (Note) |
+
+| | |
+|---------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|
+| FEA3 | - – The SACF forwards the OTASP Data Exchange resp.conf. on to the over-the-air functionality.
|
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. | |
+
+4. **OTASP data exchange resp.conf.:** this flow is from the SACF in the visited network to the SCFOTA in the home network.
+
+| OTASP data exchange | resp.conf. |
+|----------------------------|-------------------|
+| None | (Note) |
+
+| | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|
+| FEA4 | – The over-the-air functionality informs the CSC that the OTASP Data Exchange concluded successfully. |
+| NOTE – The response confirmation is empty. Merely its presence is sufficient to indicate success. This successfully completes the OTASP session. At this point the MT and UIM are activated and the subscriber can receive service. | |
+
+# 13 Definitions of information elements
+
+**13.1 action code (ACTCODE):** Specifies the nature of the action to be performed by the designated functional entity. For example, in OTASP, the action code is used by the SCF in the home network to instruct the SACF in the serving network to:
+
+- Attach to the home network during a particular OTASP session.
+- Release a TRN, thus permitting the TRN to be reused for another OTASP session.
+- Send the newly assigned IMUI to the UIM.
+- Commit the new IMUI to the UIM's permanent memory.
+- Re-register the user after the new IMUI has been committed within the UIM.
+- Release resources at the CNv at the conclusion of the OTASP session.
+
+**13.2 activation IMUI (ACT\_IMUI):** Is a temporary IMUI assigned by the SCF in the home network, that is used only for the duration of a particular OTASP session. It is eventually replaced by the newly assigned IMUI.
+
+**13.3 alert reason:** Indicates the reason why the message service centre is alerted. It can take one of the following values:
+
+- MT present.
+- Memory available.
+
+**13.4 alerting pattern:** An indication that can be used by the MT to alert the user in a specific manner in case of mobile terminating traffic (switched call or unstructured supplementary data). This indication can be an alerting level or an alerting category.
+
+**13.5 authorization denied (AUTHDEN):** Indicates that a UIM had previously been denied network access authorization or failed subscriber validation and authentication.
+
+**13.6 authentication key (A-key):** Is a security related value used in voice/data and signalling message ciphering. It is never sent over the radio interface. It may be established at both the CNh and UIM by OTASP procedures, or it may be programmed into the UIM by service provider specified methods.
+
+**13.7 authentication key protocol version (AKEYPV):** Indicates the specific combination (as desired by the home operator) of modulus value "N", the primitive value "g" and the exponent "y", which the CNh and the UIM will be using during an OTASP authentication key generation process. (See Appendix II.)
+
+**13.8 AUTHBS:** An authentication response generated by the network in response to a random challenge sent by the UIM during an "Update SSD" procedure.
+
+- 13.9 AUTH\_R:** An authentication response to SSD-based global challenge.
+- 13.10 AUTH\_U:** An authentication response to an SSD-based unique challenge.
+- 13.11 bearer capability:** Indicates a requested ISDN bearer service to be provided by the network. (See ITU-T Recommendation Q.931 [10].)
+- 13.12 bearer ID:** Is used to specify the bearer (e.g. channel number).
+- 13.13 billing ID:** Is used to identify the billing plan (tariff, account owner, etc.) associated with the call.
+- 13.14 called number:** Identifies the called party of a call. (See ITU-T Recommendation Q.931 [10].)
+- 13.15 call history count (CHCNT):** A counter held and maintained in the network and the UIM. This counter may be updated by either the home or visited network, and serves as a detector of possible "cloned" UIMs.
+- 13.16 call ID:** Indicates the identity of a call in a signalling transfer point.
+- 13.17 calling number:** Identifies the origin of a call. (See ITU-T Recommendation Q.931 [10].)
+- 13.18 calling user ID:** Identifies the calling party of a call.
+- 13.19 category:** Provides an indication of the specific subject matter (e.g. emergency, system operator announcement, news, advertisement, sports, etc.) carried in the payload being sent to a user or users (e.g. SMS or teleservice broadcast messaging).
+- 13.20 challenge (or RANDU):** A random unique challenge generated by the network to authenticate the UIM.
+- 13.21 challenge response:** A UIM-computed authentication response to the network-initiated random unique challenge. Also, known as SRES (Signature result) in some systems.
+- 13.22 challenge response value:** It is a value generated by the mobile terminal (PSCAF) using the challenge value and the secret data that it shares with its home network (LMFp/AMFp).
+- 13.23 challenge value:** It is a random value generated by the visited network to be used for authentication of the visited mobile terminal.
+- 13.24 ciphering key(s):** Secret key(s) used for encipherment of radio interface traffic.
+- 13.25 CNv authentication capabilities (CNv\_AUTHCAP):** Provides information regarding a visited/serving network's authentication capabilities; for example used in re-authentication during an OTASP session.
+- 13.26 CNv identity (CNvID):** Provides the identity of the visited/serving network for routing purposes. For example, in OTASP, it is provided by a CNv to the CNh, so that the CNh may use it later during an OTASP session to route messages to the CNv.
+- 13.27 CN key value (CNKEY):** Is a number "Y" generated by the home network (i.e. in the LMFh) which is sent to the visited network and on to the UIM, for the generation of the authentication key during an OTASP session. It is computed as:
+- $$Y = g^Y \text{ Mod } N$$
+- 13.28 confirmation of RANDG:** A form of RAND sent by the MCF, consistent with specific radio interfaces.
+- 13.29 connected line ID:** Identifies the connected party of a call.
+
+**13.30 control plane cipher key (CPCKEY):** Contains the key to be used for ciphering of appropriate data fields within signalling messages sent in both directions over the radio interface. It is computed at the CNh. Its presence also instructs the serving/visited network to turn on control plane ciphering.
+
+**13.31 control plane ciphering report (CPCRPT):** Is sent by a visited/serving network to the home network to indicate whether or not control plane ciphering has been turned on.
+
+**13.32 current password:** The password used by a user for supplementary service control.
+
+**13.33 data session lifetime:** It is the duration of time allocated to the tunnel-connection of a data session. It is determined and/or extended by the PSCAF when requesting establishment of a new data session. A tunnel-connection is cleared when its lifetime expires.
+
+**13.34 deleted user data:** Describes the user profile data to be deleted in the subscriber data management procedures. It may include:
+
+- a list of basic services;
+- a list of supplementary services (in the form of supplementary codes);
+- supplementary services data;
+- VHE subscription data;
+- broadcast and/or group call subscription data.
+
+**13.35 encapsulation method:** It is a user plane scheme to prevent out-of-sequence delivery of users' packet data units across the tunnel-connection. The choice of encapsulation method is suggested by PSACF when sending a request for establishment/re-establishment of a data session to the LMFP of the visited network.
+
+**13.36 end point reference (point):** It is the routing address/number of the user (i.e. ITDN), the party, to be added to or dropped from a multi-party call.
+
+**13.37 expected quality:** This information element is used to report the expected quality of a radio bearer, which the network may allocate to the mobile terminal, based on the measurement result.
+
+**13.38 feature information:** Feature code, visited system capabilities, current visited system action.
+
+**13.39 guidance information:** Refers to the guidance information given to a user who is requested to provide a password supplementary service control. The following information may be given:
+
+- "Enter password": This is used to prompt the user for his/her current password.
+- "Enter new password": This is used to prompt the user for a new password during registration of a new password.
+- "Enter new password again": This is used to prompt the user to re-enter the new password during registration of a new password.
+
+**13.40 high layer compatibility:** Provides a means for the remote user to check compatibility. (See ITU-T Recommendation Q.931 [10].)
+
+**13.41 LMFh address:** A routable address to a home location management function, e.g. the ISDN number of the HLR.
+
+**13.42 IMT-2000 mobile directory number (IMDN):** A dialable number that uniquely identifies an IMT-2000 user and is used to place, or forward, a call to that user, or to identify a user upon call origination.
+
+NOTE – E.164 MS ISDN Number may be applied for this.
+
+**13.43 international mobile user identity (IMUI):** Is used to address a mobile terminal and identify the mobile user uniquely to a service provision function.
+
+- 13.44 information transfer capability:** Indicates the type of the bearer capability requested by the calling party (e.g. speech). (See ITU-T Recommendation Q.931 [10].)
+- 13.45 international temporary directory number (ITDN):** An E.164 number which carries a dialable, routable number that a called party is assigned in and by a visited system for a short duration to facilitate call routing, while roaming globally.
+- 13.46 initial IMUI (INIT\_IMUI):** Is the original IMUI that is placed in the UIM at time of manufacture and is used during the OTASP authentication key generation process. It is short-lived and is replaced by the newly assigned IMUI that is granted by the home network, prior to the conclusion of an OTASP session.
+- 13.47 interference level:** This information element is used to report the interference level as a part of a measurement report.
+- 13.48 IP address (X):** IP address of the entity X (e.g. PSCAF, PSCF and PSGCF). It is used as the tunnel termination point.
+- 13.49 location area identity (LAI):** Identifies the area in which the mobile terminal is located in the visited network.
+- 13.50 LMFv address:** A routable address to a visited location management function, e.g. the ISDN number of the VLR.
+- 13.51 location information:** Indicates the location of the mobile user as accurately as possible with the available information. This could be, for example, cell ID, location area ID, VLR address, or some kind of geographical information.
+- 13.52 low layer compatibility:** Provides a means which should be used for compatibility checking by an addressed entity (e.g. a remote user or an interworking unit or a high-layer function network node addressed by the calling user). (See ITU-T Recommendation Q.931 [10].)
+- 13.53 media ID:** It is used to identify/select a media type.
+- 13.54 media type:** Is referred to a specific service transport medium. The word media is referred to a set of bearers allocated to support a variety of generic services such as voice, data, image and video.
+- 13.55 measurement condition:** This information element is used to instruct the mobile terminal on the condition on which the measurement is performed. Information such as repetition interval is included.
+- 13.56 message:** This parameter contains the SMS message.
+- 13.57 message centre address:** Represents the E.164 address of a SMS message centre.
+- 13.58 message notification type:** Indicates the manner in which to notify the user (e.g. audible, visual, vibratory, combinations of these, or other).
+- 13.59 messages pending count:** Indicates the number of messages that are awaiting retrieval by the user.
+- 13.60 message priority:** Provides in increasing order, an indication of the level of priority (e.g. normal, interactive, urgent, emergency) of a message (e.g. SMS or teleservice broadcast).
+- 13.61 message status:** Provides an indication of whether a message is new, a replacement, or a deletion of an existing message (e.g. SMS or teleservice broadcast) with the same identification (see Message type).
+- 13.62 message type:** Provides an identification for a message (e.g. SMS or teleservice broadcast) within a serving network.
+- 13.63 message waiting indicator:** Indicates if it is a message that is waiting or not.
+
+- 13.64 message waiting type:** Indicates whether the pending messages are voice, fax, e-mail or other.
+- 13.65 modulus value (MODVAL):** Is a number "N" generated by the home network (i.e. in the LMFh) which is sent to the visited network and on to the UIM, for the generation of the authentication key during an OTASP session. Its length is set by the operator (e.g. 512 bits, 768 bits, etc.) and the larger the number the greater the security provided during the authentication key generation process.
+- 13.66 MS ISDN:** Refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with ITU-T Recommendation E.213 [8].
+- 13.67 network access identifier (NAI):** A string that uniquely identifies the FE, in this case the PSCF.
+- 13.68 newly assigned IMUI (New\_IMUI):** Is the permanent identity assigned by the home network (LMFh) to the UIM of a new subscriber, and is committed within the UIM at the conclusion of an OTASP session where it replaces the Activation IMUI.
+- 13.69 number of measured calls:** This information element is used to instruct the mobile terminal on the maximum number of surrounding cells of which measurement should be performed if radio condition allows.
+- 13.70 operation result:** Provides the outcome of the operation such as operation rejected (e.g. invalid operation), operation accepted and completed, or operation accepted and not completed (e.g. error).
+- 13.71 originator address:** Is the address of the original message sender (e.g. in SMS or teleservice broadcast). Typical formats include BCD Digits, IA5 encoding and IP address variants.
+- 13.72 payload:** Is any text carried (e.g. by SMS or teleservice broadcast) for display or other use by a recipient entity. It is meaningful only to the protocol end points, and is interpreted by a teleservice identifier.
+- 13.73 periodicity:** Provides an indication of the start time, duration and repetition rate with which a message (e.g. SMS or teleservice broadcast) needs to be delivered to recipient(s).
+- 13.74 pilot channel reception level:** This information element is used to report the reception level of a pilot channel as a part of a measurement report.
+- 13.75 personal identification number (PIN):** A number used in the verification of a user's claimed identity, used here to unlock the UIM. Assigned by the service provider at time of service provisioning.
+- 13.76 preferred language indicator:** Indicates the language of choice of a recipient of a voice announcement or a text message (e.g. when notifying a user of pending messages that require retrieval, providing a roamer greeting, displaying a short message).
+- 13.77 primitive value (PRIMVAL):** Is a number "g" set by the home network (i.e. in the LMFh) which is sent to the visited network and on to the UIM, for the generation of the authentication key during an OTASP session. Its length is set by the operator and the larger the number the greater the security provided during the authentication key generation process.
+- 13.78 power control info.:** Is used to instruct the mobile terminal on the initial power level it should set for the allocated radio bearer.
+- 13.79 provider error:** Indicates a protocol related type of error:
+- duplicated invoke ID;
+ - not supported service;
+ - mistyped parameter;
+
+- resource limitation;
+- initiating release, i.e. the peer has already initiated release of the dialogue and the service has to be released;
+- unexpected response from the peer;
+- service completion failure;
+- no response from the peer;
+- invalid response received.
+
+**13.80 quality of service (QoS):** Is used to specify the required quality of service such as bit error rate.
+
+**13.81 RANDBS:** A random challenge sent by the MCF to validate the network in SSD-based systems.
+
+**13.82 RANDG:** A global random challenge (random number) broadcast over the system information channel. It is used in SSD-based systems in conjunction with SSD and other parameters, as appropriate, to authenticate the user.
+
+**13.83 RANDSSD:** A random number sent to the UIM, for use in the SSD update process.
+
+**13.84 RANDU:** A random unique challenge used to authenticate the user of the terminal in SSD-based systems. (May be generated by the visited network when SSD is shared.)
+
+**13.85 remaining session lifetime:** Computed by the home LMFp using the original session lifetime, it is sent to the anchor LMFp during an established data session.
+
+**13.86 remote action:** Tone or announcement to play.
+
+**13.87 requested information:** Indicates type of information requested, e.g. location information, user state, or both.
+
+**13.88 radio frequency info.:** Is used to specify the information of the radio frequency which is allocated to the mobile terminal.
+
+**13.89 reverse link info.:** Is used to specify the information of the reverse radio link which is allocated to the mobile terminal.
+
+**13.90 result:** Is used to indicate success or failure of a requested procedure.
+
+**13.91 routing address:** Is used for routing to the terminating visited/serving/supporting network.
+
+**13.92 security key:** Generated by LMFp, it is sent to the mobile terminal, visited PSCF, and PSGCF for support of encryption and security association between these entities.
+
+**13.93 security parameter index:** Generated by LMFp, it is sent to the mobile terminal, visited PSCF, and PSGCF for support of encryption and security association between these entities.
+
+**13.94 selection:** Specifies the data that is to be retrieved from the SDF.
+
+**13.95 service address information:** Is used by the SCF to select the correct application.
+
+**13.96 service discriminator:** It is an indicator used by the home LMFp to determine the PSGCF and to indicate to the mobile terminal which network to connect to (e.g. specific ISP, specific corporate network, generic internet access). It also indicates whether or not access is preferred to be through a PSGCF in the visited or in the home network.
+
+**13.97 service ID:** Identifies the service type for which the user wants to register (possible service types are: telephone, fax, videotex, data, etc.).
+
+**13.98 service group:** Provides information that identifies the target mobile station audience intended for receiving SMS or teleservice broadcast service. It is "free form", in that its format is
+
+determined and understood only by the protocol end points (e.g. for teleservice broadcast, the end points would be the message centre and the mobiles).
+
+**13.99 service type:** It is referred to the types of service when the establishment of a packet data session is requested (e.g. voice and data).
+
+**13.100 session ID:** Supplied by PSCAF (when an "advertisement" request is received), it is to remove ambiguity from the response to the MT in a later stage of a "data session establishment/re-establishment" procedure. It is a unique identifier of each packet data session in a multiple sessions environment.
+
+**13.101 session source address:** In a multiple sessions case, it is the address information of a session (i.e. Session ID), used to associate the "de-registration" response signal with the session to be terminated.
+
+**13.102 SS-data:** Contains additional information related to supplementary service invocation. Depending on the service invoked it can contain the following information:
+
+- A list with all called party numbers involved.
+- The called party number involved.
+
+**13.103 shared secret data (SSD):** A quantity derived from the A-key for use in authenticating the subscriber in both the "home" and "roaming" environments, in SSD-systems. The SSD is partitioned into two distinct subsets, SSD-A and SSD-B, used for authentication response and encryption key generation, respectively.
+
+**13.104 SS-event:** Indicates the supplementary service for which an invocation notification is sent towards the SCF. It can indicate one of the following services:
+
+- Explicit call transfer.
+- Call deflection.
+- Multi-party call.
+
+**13.105 SS code:** Indicates one supplementary service or a set of supplementary services.
+
+**13.106 SS data:** A general information element including data used by different supplementary services, e.g. call forwarding information or call barring information.
+
+**13.107 target CCF ID:** Is used to indicate the CCF in which the access bearer is to be established.
+
+**13.108 TC Info.:** Is the terminal capability information which determines the services that the terminal can support.
+
+**13.109 teleservice type:** Refers to services such as messaging, speech, facsimile, paging, etc.
+
+**13.110 temporary reference number (TRN):** Is assigned by the SCF in the home network and is used to correlate the voice connection (between the user's mobile and the Customer Service Centre) with the data connection (between the serving network and home network), during an OTASP session.
+
+**13.111 terminal status:** Identifies the status of the mobile terminal and its user (i.e. MT active or inactive, service granted, operator determined barring, etc.).
+
+**13.112 termination treatment info:** Is used to provide information regarding how a particular termination attempt should be dealt with (e.g. respond to a page).
+
+**13.113 termination treatment request:** Is used to query about how a particular termination attempt should be dealt with (e.g. whether or not a page be responded to).
+
+**13.114 temporary mobile user ID (TMUI):** Is used both to address a mobile terminal and to identify an IMT-2000 user. It is allocated and used by the visited network temporarily to preserve anonymity.
+
+**13.115 TMUI assignment source ID:** Is used to identify an LMFv which assigned the TMUI.
+
+**13.116 TMUI expiration timer:** Is used together with TMUI in order to provide enhanced user confidentiality.
+
+**13.117 transit network selection:** Indicates the transit network(s) requested to be used in the call. (See ITU-T Recommendation Q.762 [11].)
+
+**13.118 UIM info request:** Refers to the information requested from the UIM to provide the following:
+
+- called number associated with speed (abbreviated) dialling number;
+- specific authentication related information;
+- specific subscriber related information;
+- specific address related information.
+
+**13.119 UIM info response:** Contains the UIM information requested.
+
+**13.120 UIM key value (UIMKEY):** Is a number "X" generated by UIM and sent to the home network (i.e. in the LMFh), via the visited network, during an OTASP authentication key generation process. It is computed as:
+
+$$X = g^x \text{ Mod } N$$
+
+**13.121 user error:** Indicates that an error has occurred during handling with short message service.
+
+**13.122 user information rate:** Is used to indicate the actual user information rate which is transmitted over the radio bearer and the terrestrial channel. It may also indicate the rate adaptation in the case the user information rate and the bearer capability of the radio bearer are not the same.
+
+**13.123 user plane cipher key (UPCKEY):** Contains the key to be used for ciphering of voice/data sent in both directions over the radio interface. Its presence also instructs the serving/visited network to turn on user plane ciphering.
+
+**13.124 user plane ciphering report (UPCRPT):** Is sent by a visited/serving network to the home network to indicate whether or not user plane ciphering has been turned on.
+
+**13.125 user profile:** Is the data that specifies the subscribed services, and authentication related data for the IMT-2000 user. In addition, it may include the following attributes:
+
+- Broadcast and/or group call subscription data (if applicable);
+- IMT-2000 Mobile directory number (IMDN), e.g. a dialable number;
+- IMT-2000 Mobile user ID (IMUI);
+- IMT-2000 Temporary mobile user ID (TMUI);
+- terminal state;
+- user/terminal location information;
+- basic service data (e.g. subscribed bearer services);
+- teleservices (e.g. broadcast and/or group call subscription data);
+- supplementary services data;
+- operator determined features/services (e.g. Call barring data);
+- subscriber determined features/services (e.g. Call screening data);
+- roaming restriction data;
+- regional subscription data; and
+- VHE Subscription Data.
+
+**13.126 USSD data coding scheme:** Contains the information of the alphabet and the language used for the unstructured information in an unstructured supplementary service data operation.
+
+**13.127 USSD string:** Contains a string of unstructured information in an unstructured supplementary service data operation. The mobile user or the network either sends the string.
+
+**13.128 zone identifier:** Provides an indication of the geographical area (e.g. whole RANs or portions of a RAN within a serving network, or to the whole serving network) over which a message should be broadcast, as in the case of teleservice broadcast messaging. It is "free form", in that its format is determined and understood only by the protocol end points (e.g. for teleservice broadcast, the end points would be the message centre and the serving network).
+
+# ANNEX A
+
+## List of common procedure modules used in this Recommendation
+
+| Name of common procedure | Clause No. | Procedure used in |
+|--------------------------------|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Authentication calculation | 6.1.2.2.3 | User authentication |
+| Call Release | 7.5 | Party dropping (root party initiated and leaf initiated) |
+| Call routing | 7.3 | VHE "Direct Home Command", Party addition (root party initiated) |
+| Get password | 11.1 | Register password |
+| IMT-2000 user ID retrieval | 6.2.2 | Terminal location update |
+| LAI update | 6.2.2.1.5 | Terminal location registration, Terminal location update |
+| Location update | | Terminal location registration |
+| Mobile call release | 7.5 | Party dropping |
+| Mobile incoming call | 7.4 | Party addition |
+| Specialized resource assist | IN procedure | VHE "Direct Home Command" |
+| Start ciphering | 6.1.2.5 | Terminal location registration, Terminal location update, Initial mobile outgoing call, Initial mobile incoming call, Mobile originated short message, Mobile terminated short message |
+| Subscriber profile transfer | 6.2.1.3 | Restore LMF data |
+| Terminal location registration | 6.2.3.1 | Initial mobile outgoing call, Packet data session |
+| Terminal paging | 7.2 | Initial mobile incoming call, Mobile terminating short message |
+| TMUI assignment | 6.1.2.6 | Terminal location registration, Terminal location update, Initial mobile outgoing call, Initial mobile incoming call |
+| TMUI inquiry | 6.2.2.1.1 | Terminal location update, Detach, Terminal paging, Attach |
+| TMUI update | 6.2.2.1.4 | TMUI assignment |
+| User authentication | 6.1.2 | Terminal location registration, Terminal location update, Detach, Initial mobile outgoing call, Initial mobile incoming call, Mobile originated short message, Mobile terminated short message, Attach |
+
+| Name of common procedure | Clause No. | Procedure used in |
+|--------------------------|------------|--------------------------------------------------------------------------|
+| User ID retrieval | 6.2.2.2 | Terminal location registration, Detach, Attach |
+| User info interrogation | 6.2.1.2 | User information interrogation, Mobile terminated short message |
+| VHE service invocation | 9 | Initial mobile outgoing call, Call routing, Initial mobile incoming call |
+
+# APPENDIX I
+
+## Q.1721 Coverage of Table 1/Q.1701, Capability Set 1 Requirements
+
+This appendix uses Table 1/Q.1701 copied verbatim from Q.1701. A third column is added to indicate whether Q.1721 covers the identified capability.
+
+The entries in the third column should be interpreted as follows:
+
+| Entry | Interpretation |
+|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Not Applicable | This capability is of a type that specific information flows are not associated with it. |
+| Yes | This capability is supported by the information flows described in the indicated clause. |
+| No | This capability is not supported by information flows in Q.1721. Reasons are given. |
+| Partial | This capability is partially supported by the information flows described in the indicated clause. Those aspects not supported are indicated together with reasons. |
+
+**Table I.1/Q.1721 – Capability Set 1 for IMT-2000**
+
+| Category | Capabilities | Coverage |
+|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|
+| A) Existing Capability | 1 Widely used existing 2nd generation core fixed and mobile services and capabilities, possibly enhanced | 1 Not Applicable |
+| B) Long-Term Objectives | 1 Support network capabilities that are a distinct improvement over widely used 2G (second generation) wireless networks system capabilities in the areas of voice, data, messaging, image and multimedia, including:
1.1 Enhanced roaming
1.2 Increased data rates
1.3 Multimedia and Internet wireless services | 1 Not Applicable. The capabilities needed to support these enhancements are further addressed later in the table. |
+| C) Bearer Capability | 1 For terrestrial access:
1.1 At least 144 kbit/s in vehicular radio environment, $BER \le 10^{-6}$ , both for circuit and packet services
1.2 At least 384 kbit/s in outdoor to indoor and pedestrian radio environments, $BER \le 10^{-6}$ , both for circuit and packet services | 1 Yes. Subclause 7.1 |
+
+**Table I.1/Q.1721 – Capability Set 1 for IMT-2000 (continued)**
+
+| Category | Capabilities | Coverage |
+|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|
+| | 1.3 At least 2048 kbit/s in indoor office radio environment, $BER \leq 10^{-6}$ , both for circuit and packet services | |
+| 2 | Range of QoS with independent negotiation:
2.1 Real time/non-real time
2.2 Delay characteristics
2.3 Maximum acceptable Bit Error Rate
2.4 Bit rate/throughput | 2 Yes. Subclause 7.1 |
+| 3 | Support of packet services (both on the radio interface and on the fixed interfaces) | 3 Yes. Subclause 8.4 |
+| 4 | For the satellite access interface:
4.1 The data rates from any one user of the satellite component of IMT-2000 may be expected to range from 9.6 kbit/s up to 144 kbit/s, depending on operating environment and type of terminal | 4 Yes. Subclause 7.1 |
+| 5 | Communication configurations:
5.1 PTP: Point-to-point service bidirectional (Connection Type 1)
5.2 PTM: Point-to-multipoint service (Connection Type 2)
5.2.1 Broadcast
5.2.2 Multicast Capabilities
5.2.2.1 Pre-assigned, i.e. root selected at call setup | 5 Yes. Clauses 7 and 8 |
+| 6 | Communication types:
6.1 CLNS: Connectionless network service
6.2 CONS: Connection-oriented network service | 6 Yes. Bearer Capability |
+| 7 | Symmetry of access links:
7.1 Symmetric (equal bit rates upstream and downstream)
7.2 Asymmetric (unequal bit rates upstream and downstream) | 7 Yes. Bearer Capability |
+| 8 | Fixed and variable bit rate traffic | 8 Yes. Bearer Capability |
+| 9 | Bearer interworking procedures:
9.1 Bearer connection adaptation/conversion
9.2 Bearer, Service component and Teleservice
9.2.1 Mapping
9.2.2 Negotiation
9.2.3 Fallback procedures | 9 Not explicitly addressed |
+
+**Table I.1/Q.1721 – Capability Set 1 for IMT-2000 (continued)**
+
+| Category | Capabilities | Coverage |
+|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|
+| D) Access Network Capability – General | 1 Support for packet services including:
1.1 Negotiable bit rate of delivery (peak and mean throughput)
1.2 Negotiable delay tolerance
1.3 Negotiable reliability classes (determines the probability of data loss, out of sequence delivery, duplicate delivery and corrupted data)
2 Support of:
2.1 Constant bit rate with timing: connection-oriented
2.2 Variable bit rate with timing: connection-oriented
2.3 Variable bit rate without timing: connectionless
2.4 Variable bit rate without timing: connection-oriented
2.5 Efficient link layer recovery
3 Radio Resource Control Capabilities:
3.1 Radio channel and Radio environment monitoring and supervision
3.1.1 Radio channel quality monitoring
3.1.2 Macro diversity monitoring
3.2 Radio resources allocation, deallocation
3.3 Radio-Frequency power Control and setting
4 Support of FWA applications with ISDN-like functionality | 1 Yes. Clause 8
2 Yes, Clauses 7, 8; QoS
3 No. Radio resource management
4 Not specifically addressed |
+| E) Core Network Capability – General | 1 Support of:
1.1 Constant bit rate with timing: connection-oriented
1.2 Variable bit rate with timing: connection-oriented
1.3 Variable bit rate without timing: connectionless
1.4 Variable bit rate without timing: connection-oriented
2 Support of both circuit and packet communications for handling voice, data and video simultaneously | 1 Yes. Clauses 7, 8. QoS and Bearer Capability
2 Yes. Clauses 7 and 8 |
+
+**Table I.1/Q.1721 – Capability Set 1 for IMT-2000 (continued)**
+
+| Category | Capabilities | Coverage |
+|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 3 Interworking:
3.1 With ISDN: support of ISDN "like" services at 56 kbit/s, 64 kbit/s, 128 kbit/s, and 144 kbit/s (including D-Channel)
3.2 With B-ISDN CS-2.1
3.3 With X.25 PDN: support PAD access bearer at rates of 300, 1200, 2400, 4800, and 9600 bit/s. Support X.25 packet mode bearer at rates of 2400, 4800, and 9600 bit/s
3.4 With IP networks for user-initiated and network-initiated contexts
3.5 With PSTN (voice, fax, and data via modem)
4 Mobility:
4.1 Terminal Mobility
4.2 Personal Mobility
4.3 Service Mobility (e.g. Virtual Home Environment)
5 Internet and Data Applications:
5.1 IMT-2000 shall provide interworking with IP networks (including intranet, IPv4 and IPv6)
5.2 IMT-2000 may provide stand-alone Internet-type services
6 Global (worldwide) roaming and service interoperability between IMT-2000 Family Members
7 Core Network Transport Capabilities:
7.1 Support of packet-switched and circuit-switched operation
7.2 Support of evolved family member network architecture (PDH/SDH/ATM)
7.3 Support of open interfaces to IN Servers, Dedicated Service Providers Servers
| 3 Not explicitly addressed
4 Yes. Clause 6
5 Yes. Subclause 8.5
6 Yes. Clause 6 for roaming and Clause 9 for VHE services
7 Yes. Clauses 7 and 8
|
+| F) Network Capabilities – Call Control | 1 Separation of call and bearer channel/connection control
2 Single address/name/directory for a user, to facilitate service transportability. This does not preclude multiple subscriber numbers
3 Support of IN CS-1/2 to enable access to IN based services
4 Provision of mobility-enhanced BCSM functionality
| 1 Yes. Clause 7
2 Not explicitly addressed
3 Yes. Clause 9
4 Yes. Clause 9
|
+
+**Table I.1/Q.1721 – Capability Set 1 for IMT-2000 (continued)**
+
+| Category | Capabilities | Coverage |
+|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|
+| | 5 Multiple simultaneous calls per terminal or directory number | 5 Not explicitly addressed |
+| | 6 Multimedia mail store and forward | 6 No. Function of an MM FE. |
+| | 7 Multimedia Calls (see Broadband Signalling Capability Sets 1 and 2.1, including add/drop connection for point-to-point communication configurations, and add/drop party) | 7 Yes. Clause 8 |
+| | 8 Call internetworking procedures:
8.1 Belonging to different IMT-2000 Networks (IMT-2000 Family Members internetworking)
8.2 Belonging to IMT-2000 Networks and to Fixed Networks (PSTN, PSDN, (IP)INTERNET, (B)ISDN) | 8 Not explicitly addressed |
+| | 9 Emergency Call:
9.1 Identification of emergency call
9.2 Emergency call handling
9.3 Emergency caller location | 9 Yes. Section 7.6 |
+| | 10 Priority Call:
10.1 Identification of priority call
10.2 Priority call handling | 10 Yes. Section 7.7 |
+| | 11 Geographic positioning of a terminal/user:
11.1 Geographic position determination
11.2 Geographic position notification
11.3 User control over subscribed location service information, including the capability to prevent inadvertent disabling of mandatory service location functionality | 11 Yes. Subclause 6.2 |
+| | 12 Independence of connection characteristics for multi-connection calls | 12 Yes. Subclause 8.4 |
+| G) Network Capabilities – Security Procedures | 1 User authentication and ciphering for both circuit and packet modes | 1 Yes. Subclause 6.1.2 |
+| | 2 Terminal identification including the ability to detect stolen and non-type approved terminals | 2 Not explicitly addressed |
+| | 3 User-network mutual authentication | 3 Yes. Subclause 6.1.2 |
+| | 4 Support of service dependent authentication and ciphering mechanisms | 4 Not explicitly addressed |
+| | 5 Control of misuse of a network, i.e. prevent fraudulent use by an unauthorized user or by an authorized user exceeding his authority | 5 Not explicitly addressed |
+| | 6 Ciphering on the radio interface (user and control information) | 6 No. Radio interface matter |
+| | 7 Lawful interception (as applicable per national regulatory requirements) | 7 Not explicitly addressed |
+
+**Table I.1/Q.1721 – Capability Set 1 for IMT-2000 (continued)**
+
+| Category | Capabilities | Coverage |
+|----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|
+| | 8 Privacy of user and subscriber related data (including user identity)
9 Privacy of billing data
10 Privacy of user messages
11 Authentication mechanism negotiation between user, serving and home networks
12 Event reporting and event limitation to support fraud prevention | 8 Management topic
9 Management topic
10 Management topic
11 Not explicitly addressed
12 AMF internal function |
+| H) Network Capabilities – Resource Allocation | 1 Allocation based on negotiated QoS
2 Overload controls
3 Spectrum-efficient support for mixed services configurations (e.g. low bit rate/high bit rate, real-time/non-real-time services)
4 Route optimization at call setup and during a call | 1 Not explicitly addressed
2 Not explicitly addressed
3 Radio interface matter
4 Not explicitly addressed |
+| I) Network Capabilities – Numbering and Addressing | 1 Support of numbering and addressing portability
2 Identification, Addressing and Numbering Plan:
2.1 Identity Management
2.1.1 Terminal
2.1.2 International Mobile User
2.1.3 Subscriber ISDN
2.1.4 Multicast Group
2.2 Support of existing and advanced Addressing and Numbering Plans, including:
2.2.1 Recommendation E.164
2.2.2 Recommendation E.212
2.2.3 Recommendation E.213
2.2.4 Recommendation X.121
2.2.5 NSAP (Network Service Access Point)
2.2.6 IPv4/v6
2.2.7 E-mail and Internet type addresses
2.2.8 Other mechanisms, e.g. calling by name
2.3 Address encapsulation and mapping
2.4 Support of Recommendation E.214 (Land Mobile Global Title) addressing | 1 Not explicitly addressed
2 Not explicitly addressed |
+| J) Network Capabilities – Charging and Accounting | These items reflect the choices identified for IMT-2000 charging and accounting.
1 Standardized billing and charging user profiles
2 Standardized event reporting and usage detail recording:
2.1 Call detail recording | 1 See M.3210
2 See M.3210 |
+
+**Table I.1/Q.1721 – Capability Set 1 for IMT-2000 (continued)**
+
+| Category | Capabilities | Coverage |
+|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 2.2 Charging information generation for:
2.2.1 Circuit-switched calls
2.2.2 Packet data transmission sessions
2.2.3 Services realized exclusively by exchanging signalling information
2.2.4 Data transmission on the transparent UIM-Home Network channel
3 New charging mechanisms (e.g. volume (number of packets or bytes including by source/destination address pair), QoS, time, etc.)
4 Real-time charging
5 Flexible charging/billing mechanisms:
5.1 User notification of charges before, during and after significant events
5.2 Quasi-real time transmission of usage data records
6 Third-party charging (e.g. charging to other parties during multi-party calls)
7 Prepaid billing
8 Location-dependent billing and charging
9 Real-time access to billing information | 3 See M.3210
4 See M.3210
5 No. Significant unresolved issues in internetwork business arrangements, tariff sharing, currency conversion, accuracy, etc.
6 See M.3210
7 No: serving network matter
8 See M.3210
9 See M.3210 |
+| K) Network Capabilities – Roaming | 1 Interoperability and roaming among IMT-2000 family of systems using a single subscription
2 Ability to supplement mobility management with IN-type service logic
3 Ability to supplement authentication control with IN-type service logic. This capability does not include generation of authentication parameters (e.g. triplets)
4 Mobility and global roaming:
4.1 Location management, including automatic update
4.2 User Registration, Update and Cancellation
4.3 Service Monitoring Registration, Update, Activation, Deactivation and Cancellation
4.4 User Profile Database management and control
4.5 Security and Authentication Database management and control | 1 Yes. Clause 6
2 Yes. Clause 9
3 Yes. Clause 9
4 Yes. Clause 6 |
+
+**Table I.1/Q.1721 – Capability Set 1 for IMT-2000 (continued)**
+
+| Category | Capabilities | Coverage |
+|------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|
+| L) Network Capabilities – Service Portability | 1 The serving system should be able to enable support of a roaming user's services based on the user profile information | 1 Yes. Clause 9 |
+| | 2 Seamless (i.e. transparent to users) service portability with other IMT-2000 networks independent of environment technologies (e.g. cellular, cordless, satellite) | 2 Yes. Clause 9 |
+| | 3 Support of Virtual Home Environment to enable a user to be offered the same service experience when roaming as when in the home network, for operator specific services:
3.1 Direct home command
3.2 Relay service control | 3 Yes. Clause 9 |
+| | 4 Support of UPT | 4 Not explicitly addressed |
+| | 5 Support of Service profile management | 5 Yes. Clause 12 |
+| | 6 Support of standardized supplementary services | 6 Yes. Clause 11 |
+| M) Network Services/ Features – Handover | 1 Intra-Family Member handover is supported
1.1 Support for Hierarchical Cell Structure
1.1.1 Call transfer and handover across cell layers
1.1.2 Location management within multiple cell layers | 1 Intra-family matter |
+| | | |
+| | | |
+| | | |
+| N) Network Services/ Features – Service Provisioning | 1 Over-the-air service provisioning:
1.1 Support for both voice and data services
1.2 Uploadable and downloadable (e.g. service parameters)
1.3 Support for security and authentication | 1 Yes. Clause 12 |
+| | | |
+| | | |
+| | | |
+| O) Network Services/ Features – Quality of Service | 1 Based on subscription | 1 Yes |
+| | 2 QoS negotiation during service invocation | 2 Yes. Clause 7 |
+| | 3 QoS re-negotiation during a service session (e.g. call) | 3 Yes. Subclause 8.1 |
+| | 4 QoS of multimedia services as good as on wired access (depending on bearer service classes) | 4 Radio interface matter |
+| | 5 Speech quality equivalent to wireline | 5 Radio interface matter |
+| | 6 Meet minimum delay requirements (affects signalling timers, etc.) | 6 Not explicitly addressed |
+| P) Network Services/ Features – Supplemental Support | 1 Cordless Telephone Access | 1 Not explicitly addressed |
+| | 2 Virtual private networks | 2 Not explicitly addressed |
+| | 3 Operator support services | 3 Not explicitly addressed |
+| | 4 IP-based services | 4 Yes. Clause 8 |
+| | 5 Satellite access: considerations for long link delay, limited power, and bandwidth management | 5 Not explicitly addressed |
+| | 6 Media transparency (i.e. user data delivered unchanged) | 6 Not explicitly addressed |
+
+**Table I.1/Q.1721 – Capability Set 1 for IMT-2000 (concluded)**
+
+| Category | Capabilities | Coverage |
+|---------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Q) Network Services/ Features – Terminals and User Identity Modules (UIM) | 1 Network model to support:
1.1 Network with uploading and downloading of user profiles, data information, etc., to support UIM functionality via functional communication channels
1.2 Software configurable terminals, for operational flexibility (e.g. to support pro-active applications)
1.3 Flexible enough to support future enhancements in software-defined radios, for operational flexibility
2 Mobiles and UIM with downloading capabilities over the air for data and applications. Appropriate procedures should set in place to protect sensitive and confidential information transferred over the air
3 Multiple calls on a single terminal
4 Support terminal roaming with removable or integrated UIM and provide information needed from UIM to associate a subscriber with the MT and to personalize the MT
5 Personal mobility based on a UIM separate from the terminal (IC card)
6 Multiple registration of one user on several terminals for different services | 1 Yes. Clause 12
2 Yes. Clause 12
3 Not explicitly addressed
4 Yes. Clause 6
5 Not explicitly addressed
6 Not explicitly addressed |
+| R) Network Capabilities – Packet Transfer Control | 1 Registration/Authentication
2 Address Assignment:
2.1 Static
2.2 Dynamic
3 Sleep mode to support battery power conservation
4 Optimal packet routing
5 Multi-protocol support
6 Data compression
7 Internetworking (e.g. tunnelling, mobile-IP support)
8 Location Identification
9 Load Balancing across RF channels
10 Multiple simultaneous address registrations (e.g. IP addresses) on a single terminal
11 Priority access (for registration and data transfer)
12 Multimedia sessions | 1 Yes. Clause 6
2 Not explicitly addressed
3 Radio interface matter
4 Not explicitly addressed
5 Not explicitly addressed
6 Not explicitly addressed
7 Yes. Clause 8
8 Yes. Clause 6
9 Radio interface matter
10 Not explicitly addressed
11 Yes. Subclause 7.7
12 Yes. Clause 8 |
+
+# APPENDIX II
+
+## A-key generation
+
+## II.1 Introduction
+
+Generation of the A-key is supported in OTASP using the public key encryption method. An example of such a method is the Diffie-Hellman public key encryption method, described here. Diffie-Hellman offers certain advantages in that it is publicly available and also scalable, i.e. the various values used in this algorithm may be set by the operator for achieving the desired level of security. The MS and the network establish which set of values is supported for A-key generation, prior to the actual A-key generation process.
+
+## II.2 A-key Generation using the Diffie-Hellman Algorithm
+
+In the Diffie-Hellman scheme, the A-key is generated in both the UIMF and the LMFh/AMF using information that is shared between both entities. The LMFh/AMF generates values for a public modulus $N$ and primitive $g$ . The LMFh/AMF generates a secret key, $y$ , which is at least a 160-bit random number. The LMFh/AMF sends to the UIMF: $N$ , $g$ , and $Y$ , where:
+
+$$Y = g^y \text{ Mod } N$$
+
+The UIMF, upon receipt of $N$ , $g$ , and $Y$ , generates a secret key, $x$ , which is at least a 160-bit random number, computes and sends $X$ to the LMFh/AMF, where:
+
+$$X = g^x \text{ Mod } N$$
+
+The A-key in the UIMF is computed as the least significant 64 bits of:
+
+$$Y^x \text{ mod } N = (g^y)^x \text{ mod } N$$
+
+The LMFh/AMF computes the same A-key value as the least significant 64 bits of:
+
+$$X^y \text{ mod } N = (g^x)^y \text{ mod } N$$
+
+After the successful generation of the A-key, the LMFh/AMF and the UIMF exchange confirmations. UIMF generation of $x$ , and LMFh/AMF generation of $N$ , $g$ and $y$ are beyond the scope of this Recommendation. Requirements and properties for generation of these numbers may be obtained from current, publicly available cryptographic literature.
+
+# APPENDIX III
+
+## Bibliography
+
+The following references are not explicitly used in the body of this Recommendation but provide additional useful background and related information.
+
+- [1] ITU-T Recommendation M.3100 (1995), *Generic network information model*.
+- [2] ITU-R Recommendation M.687-2 (1997), *International Mobile Telecommunications-2000 (IMT-2000)*.
+- [3] ITU-R Recommendation M.816-1 (1997), *Framework for services supported on International Mobile Telecommunications-2000 (IMT-2000)*.
+- [4] ITU-R Recommendation M.817 (1992), *International Mobile Telecommunications-2000. Network architectures*.
+- [5] ITU-R Recommendation M.818-1 (1993), *Satellite operation within International Mobile Telecommunications-2000 (IMT-2000)*.
+
+- [6] ITU-R Recommendation M.819-2 (1997), *International Mobile Telecommunications-2000 (IMT-2000) for developing countries.*
+- [7] ITU-R Recommendation M.1034-1 (1997), *Requirements for the radio interface(s) for International Mobile Telecommunications-2000 (IMT-2000).*
+- [8] ITU-R Recommendation M.1035 (1993), *Framework for the radio interface(s) and radio sub-system functionality for International Mobile Telecommunications-2000 (IMT-2000).*
+- [9] ITU-R Recommendation M.1078 (1993), *Security principles for International Mobile Telecommunications-2000 (IMT-2000).*
+- [10] ITU-R Recommendation M.1167 (1995), *Framework for the satellite component of International Mobile Telecommunications-2000 (IMT-2000).*
+- [11] ITU-R Recommendation M.1168 (1995), *Framework of International Mobile Telecommunications-2000 (IMT-2000).*
+- [12] ITU-R Recommendation M.1223 (1997), *Evaluation of security mechanisms for IMT-2000.*
+- [13] ITU-R Recommendation ITU-R M.1224 (1997), *Vocabulary of terms for International Mobile Telecommunications-2000 (IMT-2000).*
+- [14] ITU-T Recommendation F.115 (1995), *Service objectives and principles for future public land mobile telecommunication systems.*
+- [15] ITU-T Recommendation F.116 (2000), *Service features and operational provisions in IMT-2000.*
+- [16] ITU-T Recommendation F.700 (2000), *Framework Recommendation for multimedia services.*
+- [17] ITU-T Recommendation I.211 (1993), *B-ISDN service aspects.*
+- [18] ITU-T Recommendation I.374 (1993), *Framework Recommendation on "Network capabilities to support multimedia services". (Withdrawn in 1998 – replaced by I.375.1 and I.375.2.)*
+- [19] ITU-T Recommendation Q.1001 (1988), *General aspects of public land mobile networks.*
+- [20] ITU-T Recommendation Q.1290 (1998), *Glossary of terms used in the definition of intelligent networks.*
+- [21] ITU-R Recommendation M.1311 (1997), *Framework for modularity and radiocommonality within IMT-2000.*
+- [22] ITU-T Recommendation E.214 (1988), *Structure of the land mobile global title for the signalling connection control part (SCCP).*
+- [23] ITU-R Recommendation M.1457 (2000), *Detailed specifications of the radio interfaces of International Mobile Telecommunications-2000 (IMT-2000).*
+
+# **SERIES OF ITU-T RECOMMENDATIONS**
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure and Internet protocol aspects |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/0073ee258067e591778333101c5d2edb_img.jpg b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/0073ee258067e591778333101c5d2edb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..21712f0032908e3942e83ec317f80479a2ca0993
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/0073ee258067e591778333101c5d2edb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fb669f2b7ad73d57990a8077e1fe720b310a7153d9f6d3fffcf9ec73db26e37e
+size 38349
diff --git a/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/18e519d1f91133e080347562f681dfb5_img.jpg b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/18e519d1f91133e080347562f681dfb5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..86c36d75b7ad197af52e174bedb782f97125a7e9
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/18e519d1f91133e080347562f681dfb5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2f9d0287d19eeec3486c43af3672b0e5126abba32155c13ac90d5802e1b4f82
+size 29441
diff --git a/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/200e768e8ed91aadff59c651287d1009_img.jpg b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/200e768e8ed91aadff59c651287d1009_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2db895c95615f7e37509d13ae160b3fbd1dfa88e
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/200e768e8ed91aadff59c651287d1009_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:07826ea36565fb78f9706b36d08aa3f1b8d5358b847b3d73df4901d4caeaa51f
+size 23145
diff --git a/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/2b88ad19a498bc8973acfafdd639c1cd_img.jpg b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/2b88ad19a498bc8973acfafdd639c1cd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e0ce9ee81d29cba0ae3a2b9ca0905c6883885631
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/2b88ad19a498bc8973acfafdd639c1cd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4c566632d4db82720667c4ba0dff1ef819f3cd12ee60bd78b15c0c3a0d9b5a00
+size 40499
diff --git a/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359
+size 8245
diff --git a/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/3922e505954d53f8864a44dc9ea664c6_img.jpg b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/3922e505954d53f8864a44dc9ea664c6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1008b4114f2859e8ce2fb3942b1326f91b00e5f4
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/3922e505954d53f8864a44dc9ea664c6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:939259eb532e2f309c5ff8a133ed5d3658e1f4c7ee6c17391a06f62b7cca79fb
+size 43578
diff --git a/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/438622ea89762ed550a4ef3c13fa71a6_img.jpg b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/438622ea89762ed550a4ef3c13fa71a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c0e9663869f739e6ae7de24cea9c0fb946f02643
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/438622ea89762ed550a4ef3c13fa71a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6c09f6b6219bc0ac97d291056e1d80ce699d364c506668676c967d4f22e2e6ce
+size 42753
diff --git a/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..593be893b4c7c6e50fe49e2d378f58914fde5fd7
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1778f188806963b9235c6a435fa9e8e4c803c0d028bbd9eaa2cb1a8a5db54529
+size 51755
diff --git a/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3be8dc30a5b8912496e5daf93744876858769690
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:277b3eeeeabac8a1cc4358ad7c5da0645516936ed9d597951aa809b72945952c
+size 17696
diff --git a/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/5ee80a63ec53c60d7306b5a44984afcf_img.jpg b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/5ee80a63ec53c60d7306b5a44984afcf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ab3734c2b4d66cbf6364a825e5117ffbaa4d5b95
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/5ee80a63ec53c60d7306b5a44984afcf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:62dd1fdfd7f4e44ff5b7cdf079ac8c31722f0b72f203d754b7c8f114aebef703
+size 23700
diff --git a/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d33b3bbadd4ec71cc3a682fa47e46f73a216d101
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d59a0157ce4a9085e68fdadb191f54e835bb7eacf42c686fa6eb7d04ef7392cf
+size 49254
diff --git a/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e2f8d8daa17e021ccf3a601d74313101bfeb90a2
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bfbc8062742e8fae952daed619b91f5ab37290a35c25cb6f0a028666eff65ad8
+size 120159
diff --git a/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..136ec061e63f32da47d2842d98f86daee48fd859
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:49b64e66f97fd1ab5b6e86c2d8b620af091a89de7345fa44a5934af2ac84da87
+size 25284
diff --git a/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/a76fa39f5daf6a026e032495262ed0f6_img.jpg b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/a76fa39f5daf6a026e032495262ed0f6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7705e37dfe9f4e8c8b20cd2d417d33d5c8eb1506
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/a76fa39f5daf6a026e032495262ed0f6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:659305c0ef4f07931376c979b36657ca7550dd78d97c64c4f23f8d9a5e9c5332
+size 38482
diff --git a/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cabffdcb6ae60254ad1be7507002013e48b5c671
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aac2675191bb415e1ee679f4dc0622e44b590d6f8c7fd7423c28d689a7789e64
+size 47211
diff --git a/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..29a0d049c1b4fef7e669fd35e68a14f4b451cb53
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:23f0d93c6441befadb0404529f25eb602f742ae9c9fbfc40a327aed37df4b6ac
+size 56035
diff --git a/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/dfd09f348b50c9255f3cfe67985db9bc_img.jpg b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/dfd09f348b50c9255f3cfe67985db9bc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5b47091fd0a388be62fb496c4bb405df1f888aaf
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/dfd09f348b50c9255f3cfe67985db9bc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:905fcdb08a1a2461969e0f4993a357f01823c8237fe25e61a49c0479f3c4122d
+size 41138
diff --git a/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/f21295f56ab9da5a7ea269beb8cf4afe_img.jpg b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/f21295f56ab9da5a7ea269beb8cf4afe_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64e310e6356947b65720f36df11c5ebde89bdf49
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/f21295f56ab9da5a7ea269beb8cf4afe_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3eb452efc4c686bd72474455cc227c8db193364366f98d66f8d4c66416818153
+size 36542
diff --git a/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..af584e51290f19a614272b92a3fe3f71e18ede20
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e9944303ba385cf206f8139bec5327ac50162d904b6883f90b303a709af564da
+size 64131
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6955ce461b96d54ee579accd7c867ec88d41d78d
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a32fd2fac85163c57480befc39871ce28ac93743cc244c16a89cdafe994d7cb5
+size 134273
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359
+size 8245
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/2f108a589e99e93fd7aa8fac626398c7_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/2f108a589e99e93fd7aa8fac626398c7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..045d8089c23716a99eb4e253396e407e9a374852
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/2f108a589e99e93fd7aa8fac626398c7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:49f2b4ac178b46c1ced627215e49e3ca0786191af11e0fdac71b57078c91357e
+size 59607
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cffdb29f98751dac4d5242b7642cb028eac70ec5
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f4bc8766524d50235fdf798e1dd15eb71aa5fe315dc55a83d5dba7898f131ee7
+size 28787
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/39729be7ec83c3de8e480061966e4505_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/39729be7ec83c3de8e480061966e4505_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f47b1fca41a62a32887f75f3d4458d7064c5562f
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/39729be7ec83c3de8e480061966e4505_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ab4efdc7f8b086004f01575dc56e0ad22dccb35457f30fc35a06431c9153385c
+size 38042
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/3d46409f8d0190e611a910ff27f8ec07_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/3d46409f8d0190e611a910ff27f8ec07_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a0bf7777e854cbe2c95501e4e4c4865ef223e633
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/3d46409f8d0190e611a910ff27f8ec07_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9c5ef3281ba0152afabf087c81a3084b34df4bcb4a62aa09e75aba853bacd9e5
+size 73485
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/55a415876cf7b7c2509c0318bb857efa_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/55a415876cf7b7c2509c0318bb857efa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b81e0de7e5641c4511fd4356af09715474c44665
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/55a415876cf7b7c2509c0318bb857efa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e79a4241f96069e21d87332d1499b807b17de442bace9ccf98d93399de722d93
+size 43249
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/623feecbd1d66ea35a128030719ad30c_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/623feecbd1d66ea35a128030719ad30c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6901cde09f686f6e0f220aa6cfe8a8823f43a11d
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/623feecbd1d66ea35a128030719ad30c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9497ea73d060709c69dcd1e61647af6c248e738342d58a881c94a6f1158dde16
+size 25306
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/64c76a4fd6b7918cd8a2704de0265e8d_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/64c76a4fd6b7918cd8a2704de0265e8d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d63ac8967ac42aed8f1bef4407bab9e82ae55c46
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/64c76a4fd6b7918cd8a2704de0265e8d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:438c08e62da29d425cb39f73f3028915c0c36d54e23eb40e5f664263c5c2d582
+size 37632
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/710b805054943193bd9fd7674b0759f6_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/710b805054943193bd9fd7674b0759f6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a45d8fec7ab769e0ddaa816098f6af5afae6ad59
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/710b805054943193bd9fd7674b0759f6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:503779308437b49ad9c21facc1a0ce754a8c730be0adcb4c83568317b1af6c71
+size 36244
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/773bb1698c96c3aea54d138ddcc7cfd5_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/773bb1698c96c3aea54d138ddcc7cfd5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7960eb15368b761ecb769f89473d248a1d1a8b02
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/773bb1698c96c3aea54d138ddcc7cfd5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a6cd084a44ff4add5565bb4b823191351bfcfd0c8466eb6f2c28b691e2ca2b4a
+size 37789
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/853ef5420f0432e626e83987e3f38a0b_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/853ef5420f0432e626e83987e3f38a0b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..88d148d262a8a0b31a5b6523c1b1ea8fc3ddf385
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/853ef5420f0432e626e83987e3f38a0b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bd9d888a1433759ee8458e1e430ab09550994efaf500c8babda649f3f1d5bf8c
+size 39251
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..24aac5b7441150b7dee2c53bcbf8a0a17286d23f
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d1c0ce0af86a6e21524379312ef5485cbe3ea353fd0c45bdfeafe1e318da753
+size 111394
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2bf9e9cf2c618312d0d35711f8070eca5fb2a0df
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d15a5b3d94412056d9fdfdf5d3b7b7dd55740f91b5fd19be899f69f00628fe39
+size 21126
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/b3459be722bb1ef785aa859e6f4ec7e4_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/b3459be722bb1ef785aa859e6f4ec7e4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..10a6ee71e23793ac5cde8beb1a9b65ed1049878b
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/b3459be722bb1ef785aa859e6f4ec7e4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eaad92c4e08223aa3be0a808b06a778c1d992639b090fca555e5274f4460a52b
+size 37551
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/b5335262987c819d7f71ce40f99cb71b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..29295a808227bc5d97c1a439186333e3b9dac92f
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/b5335262987c819d7f71ce40f99cb71b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c9ec6c90a1bcd469855f8bdd90aa234fd39c08409031d74ddde72743c6b5549
+size 81101
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/bdee2715697a4142d16a360549fa7c7f_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/bdee2715697a4142d16a360549fa7c7f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..df69291ab5a6ebf4cbfa6e0a40d580de519c325a
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/bdee2715697a4142d16a360549fa7c7f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9406378ea38efd0a8f2d96986ba78b53ba715a9b629363b79ed66508b35ba2c8
+size 21519
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/c19f37cdfc7768db716bfc0cc5934cfb_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/c19f37cdfc7768db716bfc0cc5934cfb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fea25a8e48cc00f5c93e99e5fa85c49d7d5ed0dc
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/c19f37cdfc7768db716bfc0cc5934cfb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ca89c2fa877e036ede4d2d6e5d75199d065f70855785ee0ec11dba945a05ddf2
+size 47457
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6436051a9006c766144e48c482745d308bb1b049
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:84aa0ec0a8aa4533c477b232a8e64630eca0e75baa1811eb5c8b78195d6a0926
+size 80031
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/dbbc0baac7341cda76cc4f8355dce23f_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/dbbc0baac7341cda76cc4f8355dce23f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1d7e188d1024252cb0f929903f1d2bf73b4b5759
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/dbbc0baac7341cda76cc4f8355dce23f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5a6cb2e4177a00868a56ea72a402a04383b4b41349eb6ab5471a5a3233fb868d
+size 68114
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e2dbc56135ff8c9f640b660da498b58250d503d4
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6f2abcaffb971cd448121259f67d39d2507d6c7533e0803f0822bd554624053c
+size 69641
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/dfafe39c233a62ec8ebd71e42992c14d_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/dfafe39c233a62ec8ebd71e42992c14d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0ba60577eab1ebc648a1d19154e2c244c80a6dc3
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/dfafe39c233a62ec8ebd71e42992c14d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a96900461405ede1d617517601b4aaff7cd5be7133910911e03448c601ce4d2d
+size 14379
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/e38206fcefa2045af01d494b2956775a_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/e38206fcefa2045af01d494b2956775a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6d76e8fca81bc86b9a90ce05e63583fd9daed6cb
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/e38206fcefa2045af01d494b2956775a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fa2f9f2019aa24f283b9a9351a85ae3aedbc9c45793e3bb06b3a250c4b863bf7
+size 33964
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a2a48a82e1d7764a41532e145abc68a8ab94c365
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:86800683c917e737da55a7fc033865935d01a14957ea900c3d96b5fd25d77674
+size 56811
diff --git a/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/fda85db2e355bb8e3edcd5a74bf3d673_img.jpg b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/fda85db2e355bb8e3edcd5a74bf3d673_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2da6c99e88fffbbba6d55d138870dc2ff7946d41
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.3-200309-I_PDF-E/fda85db2e355bb8e3edcd5a74bf3d673_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cd789adf9a95e9d4ade8c6eb96744e221d28d674bfc934655d797dccc890df1f
+size 53340
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7102eff7d1655bc6bf70f4208c05bc910f56d31e
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:11c68377051c4351582fb1d24fc83bb8f4c4f642cad738a42184d99ac0f2e388
+size 124467
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8df067bcb7fcdb1b6fc746a62b285a5abf20c932
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8df004e7ab7c861612586d7f3289ed28b2c8f0f744ba35e4370c65ad183c30a7
+size 30151
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2d042f813f55b9d3da5aa697d65b670d964fdecb
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:32173c3ca8d7ac88b015bb06ded05f35603e29734e6310226a9df90223ecb023
+size 72759
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/1316d63eca7b84e13c27f55f0027b7b5_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/1316d63eca7b84e13c27f55f0027b7b5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..746e05e1c92d37c757850105960c167ffd3a07d4
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/1316d63eca7b84e13c27f55f0027b7b5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dcea1cc1c86fe52393a39029cdeaa21ac2a1e637ffb45cca4dd4b266c690c1ff
+size 18897
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8f24b214263bab4142643453a604fb5196f9397e2500c675cde79d53ce5e5d8e
+size 3645
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/1e8c50ad4fca7f315a407347dd5091cc_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/1e8c50ad4fca7f315a407347dd5091cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0abaef893ba389bec1b970ac877b871defafc7ad
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/1e8c50ad4fca7f315a407347dd5091cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:00b79235ec8c9e95bd3d2e5ab0737d4c2e292067b4a99d67159fba9f08c2de63
+size 68350
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/3f4a2dc3fd8cdbf151b1ce1a2d2f5864_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/3f4a2dc3fd8cdbf151b1ce1a2d2f5864_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bf933caf44778f92d9be4e059a32c1e9aa3ae01f
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/3f4a2dc3fd8cdbf151b1ce1a2d2f5864_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:633bc88c9c14dfe6224508616a3f87a7f881ce6e88b87e49bd3bc8fe20aee63a
+size 60863
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/48f209b7c0c1f91af40cfc3466dbd534_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/48f209b7c0c1f91af40cfc3466dbd534_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c578f5e74920819d0f9235082d64d19c0f26cddd
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/48f209b7c0c1f91af40cfc3466dbd534_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e0544c6f7719575e766b07b46b829d61f617517e14a9be06542145c44e540ad6
+size 35739
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0c7307b23df91394ee11c20c648008b76a972b5f
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7074703118ee1e5cb18d6786c5834c7cad9716fef0562f32bb31d5a6f095a870
+size 36141
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dbdfdc84800daf3df799d5e332761bfdc69ca705
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a4d6cbbaab6dee314752962e1123823d2d79be08d027044c93fae6c7a1658243
+size 14803
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4dd2e40d1d5f30c58304eb87e42df5bcb1ad667a
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1d2242bd6812c76090d36237a55d3073012281fbc8a0575a6f31ba9f23c90eeb
+size 51036
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/683f755e8456c884716de4fce48c7e63_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/683f755e8456c884716de4fce48c7e63_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..308ebe4a8a6945d10f231821b63941bf8e47feb5
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/683f755e8456c884716de4fce48c7e63_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e8a3c322f13a374b8342dab05720ee7863f7481151e92fb096bd1e90c3a8e1c9
+size 42836
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/763d1eea110547543c01572972391ef1_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/763d1eea110547543c01572972391ef1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5e530f8313901860c44219c46d521fe97977a805
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/763d1eea110547543c01572972391ef1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8e788e637c0f6e37dcdff2a6ab8aca2b2c7ffb6baeb499e7e6ae4dfb19f13d57
+size 20727
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/9832c14a1af451896d75b69abc97654f_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/9832c14a1af451896d75b69abc97654f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fe898d0408bed506a9ed5de1fc11816e12e12209
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/9832c14a1af451896d75b69abc97654f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d5e4441cb7a5570cb3d2c5d79232b7daf735f996d9eb7e83633395cc1a3903e6
+size 44162
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..88c30bd68e69c50d46a1c1fde9bb466d09947251
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:01aae0489ca77823879c42951ea5c3bad7c2b8359a2535b726e8a9bafc3c290c
+size 17211
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/a548c5381cebd2650c5edb725b19f795_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/a548c5381cebd2650c5edb725b19f795_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..55af8a9729ee2ce4e875f863404e47097b0c8f88
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/a548c5381cebd2650c5edb725b19f795_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dcfe6663be4345329fe081c3c38d7d3b7aa8bc53d99a59f45a22108814201a7f
+size 36997
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/b791cfc87b743b82b2791e40a02966a3_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/b791cfc87b743b82b2791e40a02966a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d1c61a2066bf5fb46dfbeef388eea13e2ae4dbea
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/b791cfc87b743b82b2791e40a02966a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3a245afc4a14e0289dc35185adc9989e940283ac4dd1a8267d760184ef9bdcd4
+size 27406
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f59e6c56372ce33684e2c8588a91b424e6286c32
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1acf74a7db63e6b69e019f69f712256d01819b5d6b279250cb4e02c29a5b6609
+size 76645
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3ad35c57bb7860ae0a2abb356dfb94dbfdd8baef
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7a7ef53bb971decf824200697b4a4513455a4c5786538ad2795d6df7f9bfaa1b
+size 149523
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/cccf3125a7354e1865653731de1ca03d_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/cccf3125a7354e1865653731de1ca03d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9154f1dcff5a33510fc93704371e561a5505d101
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/cccf3125a7354e1865653731de1ca03d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b4ab8cd974a7800d897a8a6d6c54ece1c93db63f78de80e983abf90ab5c0f6d5
+size 80688
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/cef981f48160da6ca248560bbf31eb7f_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/cef981f48160da6ca248560bbf31eb7f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a67eea9ed17d97b83df29b02ee6b45f98e359f2e
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/cef981f48160da6ca248560bbf31eb7f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:049a870abe38eb08bf1344c8cb58a781ce8abb80682ea158e59f4f1691a7d4a3
+size 44869
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/d6e4b74a3ccc1bf6e1bb4bad1ff72f55_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/d6e4b74a3ccc1bf6e1bb4bad1ff72f55_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d6bfd8af13630f1a9655f26327721c7ea4032d01
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/d6e4b74a3ccc1bf6e1bb4bad1ff72f55_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:26a9c8df9118b7e7fbdaa071beddb2155bcc51541da8c79b6e333eb6180bc938
+size 102996
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/e3026761f1da20ee91832039701984dd_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/e3026761f1da20ee91832039701984dd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..76b72d7d7863af17d7c85c301fb0a7d915d01ab0
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/e3026761f1da20ee91832039701984dd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:136166975b8ecf862949e7a49c4c7971a338e0ef1a8857188addc1a61d7e14dd
+size 55507
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c067a37f6f01a27b0be7d8a00c88823973d6d166
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:95f82956367639a86a6029e25f2d4cac438eb5892acb8eaa539797ece9ce2d75
+size 77483
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/fd6100880c96880a39d994338c9d5f36_img.jpg b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/fd6100880c96880a39d994338c9d5f36_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2654f012f89d3aed5979ee97ea610075b854175d
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/fd6100880c96880a39d994338c9d5f36_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:83ffbd0ca87a667247582a3f2e05326fda49d54d88d438e4c2bd2aa534ccc5d2
+size 72987
diff --git a/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..da9b31a891e20cb1dd95489fb3a80b30e45a9f04
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.5-200810-I_PDF-E/raw.md
@@ -0,0 +1,12449 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.1741.5**
+
+(10/2008)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Signalling requirements and protocols for IMT-2000
+
+---
+
+**IMT-2000 references to Release 7 of
+GSM-evolved UMTS core network**
+
+Recommendation ITU-T Q.1741.5
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120-Q.499 |
+| DIGITAL EXCHANGES | Q.500-Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 |
+| Q3 INTERFACE | Q.800-Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 |
+| INTELLIGENT NETWORK | Q.1200-Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 |
+| BROADBAND ISDN | Q.2000-Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## **Recommendation ITU-T Q.1741.5**
+
+# **IMT-2000 references to Release 7 of GSM-evolved UMTS core network**
+
+## **Summary**
+
+Recommendation ITU-T Q.1741.5 identifies a release of the IMT-2000 Family Member, "GSM evolved UMTS Core Network". This release of the Family Member is known to the Standards Development Organizations (i.e., ARIB, CCSA, ETSI, ATIS, TTA, TTC) as the "3GPP Release 7". Earlier releases, known as "3GPP Release 99", "3GPP Release 4", "3GPP Release 5", and "3GPP Release 6", of this Family Member are specified in Recommendations ITU-T Q.1741.1, Q.1741.2, Q.1741.3, and Q.1741.4, respectively, while other IMT-2000 Family Members are specified in other ITU-T Recommendations in the Q.174x series.
+
+This Recommendation combines and associates the relevant standards from a number of Standards Development Organizations for the core network for this IMT-2000 Family Member into a global Recommendation.
+
+## **Source**
+
+Recommendation ITU-T Q.1741.5 was approved on 14 October 2008 by ITU-T Study Group 19 (2005-2008) under Recommendation ITU-T A.8 procedure.
+
+## **Keywords**
+
+Core Network, GSM, IMT-2000, Release 7, third generation system, UMTS.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2009
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## CONTENTS
+
+###### Page
+
+| | | |
+|------|-----------------------------------------------------------------------------------------------------------------|----|
+| 1 | Scope ..... | 1 |
+| 2 | References..... | 1 |
+| 2.1 | Normative references..... | 1 |
+| 2.2 | Informative references..... | 6 |
+| 3 | Definitions ..... | 6 |
+| 4 | Abbreviations and acronyms ..... | 25 |
+| 5 | Introduction ..... | 33 |
+| 6 | Basic architecture for the UMTS IMT-2000 Family Member ..... | 35 |
+| 7 | Network entities..... | 42 |
+| 7.1 | Gateway mobile switching centre (GMSC) ..... | 42 |
+| 7.2 | Mobile switching centre and visitor location register (MSC/VLR) ..... | 42 |
+| 7.3 | Home subscriber server (HSS) ..... | 44 |
+| 7.4 | Equipment identity register (EIR) ..... | 47 |
+| 7.5 | SMS gateway MSC (SMS-GMSC)..... | 47 |
+| 7.6 | SMS interworking MSC ..... | 47 |
+| 7.7 | Gateway GPRS support node (GGSN)..... | 48 |
+| 7.8 | Serving GPRS support node (SGSN)..... | 48 |
+| 7.9 | Circuit switched – Media gateway function (CS-MGW)..... | 48 |
+| 7.10 | IP multimedia (IM) core network (CN) subsystem entities ..... | 49 |
+| 7.11 | Signalling gateway function (SGW) ..... | 51 |
+| 7.12 | Global text telephony specific entities ..... | 51 |
+| 7.13 | Security gateway (SEG) ..... | 52 |
+| 7.14 | Gateway mobile location centre (GMLC)..... | 52 |
+| 7.15 | GPRS service switching function (gprsSSF)..... | 52 |
+| 7.16 | GSM service control function (gsmSCF)..... | 52 |
+| 7.17 | GSM service switching function (gsmSSF) ..... | 52 |
+| 7.18 | GSM specialized resource function (gsmSRF) ..... | 53 |
+| 7.19 | Gateway location register (GLR) ..... | 53 |
+| 7.20 | Intermediate GPRS serving node (IM-GSN) ..... | 53 |
+| 7.21 | Intermediate mobile-service switching centre (IM-MSC) ..... | 53 |
+| 8 | Interfaces and reference points ..... | 53 |
+| 8.1 | C interface (Gateway mobile switching centre server (GMSC server) –
Home location register (HLR)) ..... | 53 |
+| 8.2 | D interface (Visitor location register (VLR) – Home location register
(HLR)) ..... | 53 |
+| 8.3 | E interface (Mobile switching centre server (MSC server) – Mobile
switching centre server (MSC server))..... | 54 |
+| 8.4 | F interface (Mobile switching centre server (MSC server) – Equipment
identity register (EIR)) ..... | 54 |
+
+| | Page | |
+|------|------------------------------------------------------------------------------------------------------------------------------------------------|----|
+| 8.5 | G interface (Visitor location register (VLR) – Visitor location register (VLR)) ..... | 54 |
+| 8.6 | Gc interface (Home location register (HLR) – Gateway GPRS support node (GGSN)) ..... | 55 |
+| 8.7 | Gf interface (Equipment identity register (EIR) – Serving GPRS support node (SGSN)) ..... | 55 |
+| 8.8 | Reference point GGSN – Packet data networks (Gi reference point) ..... | 55 |
+| 8.9 | GLa interface (Gateway location register (GLR) – Home location register (HLR)) ..... | 55 |
+| 8.10 | GLb interface (Gateway location register (GLR) – Visitor location register (VLR)) ..... | 55 |
+| 8.11 | GLc interface (Gateway location register (GLR) – Serving GPRS support node (SGSN)) ..... | 56 |
+| 8.12 | GLd interface (Gateway location register (GLR) – Intermediate mobile-services switching centre (IM-MSC)) ..... | 56 |
+| 8.13 | GLe interface (Gateway location register (GLR) – Intermediate GPRS serving node (IM-GSN)) ..... | 56 |
+| 8.14 | GLf interface (Gateway location register (GLR) – Short message service-gateway mobile switching centre (SMS-GMSC)) ..... | 56 |
+| 8.15 | GLg interface (Intermediate mobile-services switching centre (IM-MSC)– Short message service-gateway mobile switching centre (SMS-GMSC)) ..... | 56 |
+| 8.16 | GLh interface (Intermediate mobile-services switching centre (IM-MSC)– Mobile switching centre (MSC)) ..... | 57 |
+| 8.17 | GLi interface (Intermediate mobile-services switching centre (IM-MSC)– Gateway mobile location centre (GMLC)) ..... | 57 |
+| 8.18 | GLj interface (Intermediate GPRS serving node (IM-GSN) – Gateway GPRS support node (GGSN)) ..... | 57 |
+| 8.19 | GLk interface (Intermediate GPRS serving node (IM-GSN) – Serving GPRS support node (SGSN)) ..... | 57 |
+| 8.20 | Gn interface (Gateway GPRS support node (GGSN) – Serving GPRS support node (SGSN)) ..... | 57 |
+| 8.21 | Gp interface (Serving GPRS support node (SGSN) – External data network) ..... | 57 |
+| 8.22 | Gr interface (Home location register (HLR) – Serving GPRS support node (SGSN)) ..... | 58 |
+| 8.23 | Gs interface (Mobile switching centre (MSC)/Visitor location register (VLR) – Serving GPRS support node (SGSN)) ..... | 58 |
+| 8.24 | gsmSCF – HLR interface ..... | 58 |
+| 8.25 | gsmSCF – gsmSRF interface ..... | 58 |
+| 8.26 | gsmSSF – gsmSCF interface ..... | 58 |
+| 8.27 | gprsSSF – gsmSCF interface ..... | 59 |
+| 8.28 | H interface (Home location register (HLR) – Authentication centre (AuC)) ..... | 59 |
+
+| | | |
+|-------|-------------------------------------------------------------------------------------------------------------------------------|-----|
+| 8.29 | IuBC interface (Cell broadcast centre (CBC) – Radio network subsystem (RNS)) ..... | 59 |
+| 8.30 | IuCS interface (Mobile switching centre (MSC) – RNS or BSS) ..... | 59 |
+| 8.31 | IuPS interface (Serving GPRS support node (SGSN) – RNS or BSS)) ..... | 59 |
+| 8.32 | A interface (Mobile switching centre (MSC) – Base station system (BSS)) ..... | 60 |
+| 8.33 | Gb interface (Serving GPRS support node (SGSN) – Base station system (BSS)) ..... | 60 |
+| 8.34 | Reference point GMLC – external LCS client (Le reference point) ..... | 60 |
+| 8.35 | LCS interfaces using MAP ..... | 60 |
+| 8.36 | Mc reference point (Mobile switching centre server (MSC Server) – Circuit switched media gateway (CS-MGW)) ..... | 61 |
+| 8.37 | Mobile switching centre (MSC) – gsmSCF interface ..... | 61 |
+| 8.38 | Nb reference point (Circuit switched media gateway (CS-MGW) –Circuit switched media gateway (CS-MGW)) ..... | 61 |
+| 8.39 | Nc reference point (Mobile switching centre server (MSC server) – Gateway mobile switching centre server (GMSC server)) ..... | 61 |
+| 8.40 | Reference point fixed networks – MSC ..... | 62 |
+| 8.41 | IM subsystem reference points ..... | 62 |
+| 8.42 | Reference point CSCF – Multimedia IP networks (Mm reference point) ..... | 65 |
+| 8.43 | Reference point PDG – Packet data networks (Wi reference point) ..... | 65 |
+| 8.44 | Reference point WAG – WLAN access network (Wn reference point) ..... | 65 |
+| 9 | Technical specifications structure ..... | 65 |
+| 10 | Technical specifications ..... | 66 |
+| 10.1 | 21-series, Requirements specifications ..... | 66 |
+| 10.2 | 22-series, Service aspects ..... | 67 |
+| 10.3 | 23-Series, Technical realization ..... | 117 |
+| 10.4 | 24-series, Signalling protocols (User equipment – core network) ..... | 169 |
+| 10.5 | 26-series, Codecs (speech, video, etc.) ..... | 196 |
+| 10.6 | 27-series, Data ..... | 235 |
+| 10.7 | 28-series, Signalling protocols (RSS-CN) ..... | 241 |
+| 10.8 | 29-series, Signalling protocols (NSS) ..... | 241 |
+| 10.9 | 31-series, UIM user identity module ..... | 294 |
+| 10.10 | 32-series, operation and maintenance ..... | 304 |
+| 10.11 | 33-series, Security aspects ..... | 410 |
+| 10.12 | 35-series, Algorithm specifications ..... | 423 |
+
+
+
+## Recommendation ITU-T Q.1741.5
+
+# IMT-2000 references to Release 7 of GSM-evolved UMTS core network
+
+# 1 Scope
+
+This Recommendation identifies the IMT-2000 Family Member, "GSM evolved UMTS Core Network". This release of the Family Member is known to the Standards Development Organizations (i.e., ARIB, CCSA, ETSI, ATIS, TTA, TTC) as the "3GPP Release 7".
+
+The core network interfaces identified in this Recommendation and the radio interfaces and radio access interfaces which are identified in [ITU-R M.1457-7] constitute a complete system specification for the 3rd generation mobile system for terrestrial usage of this IMT-2000 Family Member.
+
+It is the intent of the ITU-T that the references in this Recommendation are only to specifications that specify the network aspects of this IMT-2000 Family Member. In the event that a referenced specification also includes material that specifies any of the radio aspects of this IMT-2000 family member, [ITU-R M.1457-7] shall take precedence.
+
+NOTE – The structure and content of this Recommendation have been organized for ease of use by those familiar with the original source material; as such, the usual style of ITU-T Recommendations has not been applied.
+
+# 2 References1
+
+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.
+
+## 2.1 Normative references
+
+- | | |
+|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [ITU-R M.1457-7] | Recommendation ITU-R M.1457-7 (2007), Detailed specifications of the radio interfaces of International Mobile Telecommunications-2000 (IMT-2000) . |
+| [ETSI TS 123 002] | ETSI TS 123 002 (2007), Network architecture (Release 7) . |
+
+---
+
+1 Technical documents of Standards Development Organizations recognized under the provisions of Recommendation ITU-T A.5 can be found under:
+
+- ARIB at
+- CCSA at
+- ETSI at
+- ATIS at
+- TTA at
+- TTC at
+- IETF at
+
+| | |
+|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [TTC TS-3GA-23.002] | TTC TS-3GA-23.002 (2007), Network architecture (Release 7) . |
+| [ATIS 3GPP 23.002] | ATIS 3GPP 23.002 (2007), Network architecture (Release 7) . |
+| [TTA TTAT.3G-23.002] | TTA TTAT.3G-23.002 (2007), Network architecture (Release 7) . |
+| [CCSA-TSD-123 002] | CCSA-TSD-123 002 (2007), Network architecture (Release 7) . |
+| [TTC TS-3GA-23.271] | TTC TS-3GA-23.271 (2007), Functional stage 2 description of location services . |
+| [ETSI TS 123 271] | ETSI TS 123 271 (2007), Functional stage 2 description of location services . |
+| [ATIS 3GPP 23.271] | ATIS 3GPP 23.271 (2007), Functional stage 2 description of location services in UMTS . |
+| [TTA TTAT.3G-23.271] | TTA TTAT.3G-23.271 (2007), IMT-2000 3GPP-Location Services (LCS); Functional description; Stage 2 (R7) . |
+| [CCSA-TSD-123 271] | CCSA-TSD-123 271 (2007), Functional stage 2 description of location services in UMTS . |
+| [ETSI EN 301 140-1] | ETSI EN 301 140-1 (1999), Intelligent Network (IN); Intelligent network Application Protocol (INAP); Capability Set 2 (CS2); Part 1: Protocol Specification . |
+| [ETSI ETS 300 356-18] | ETSI ETS 300 356-18 (1995), ISDN User Part (ISUP) version 2 for the international interface; Part 18: Completion of Calls to Busy Subscriber (CCBS) supplementary service . |
+| [ISO/IEC 3309] | ISO/IEC 3309:1993, Information technology – Telecommunication and information exchange between systems – High-level data link control (HDLC) procedures – Frame structure . |
+| [ISO/IEC 4335] | ISO/IEC 4335:1993, Information technology – Telecommunications and information exchange between systems – High-level data link control (HDLC) procedures – Elements of procedures . |
+| [ISO/IEC 7498-1] | ISO/IEC 7498-1:1994, Information processing systems – Open Systems Interconnection – Basic Reference Model: The Basic Model . |
+| [ISO/IEC 7809] | ISO/IEC 7809:1993, Information technology – Telecommunication and information exchange between systems – High-level data link control (HDLC) procedures – Classes of procedures . |
+| [ISO/IEC 8886] | ISO/IEC 8886:1996, Information technology – Open Systems Interconnection – Data link service definition . |
+| [ITU-T E.164] | Recommendation ITU-T E.164 (2005), The international public telecommunication numbering plan . |
+| [ITU-T G.711] | Recommendation ITU-T G.711 (1988), Pulse code modulation (PCM) of voice frequencies . |
+
+| | |
+|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [ITU-T H.245] | Recommendation ITU-T H.245 (2005), Control protocol for multimedia communication. |
+| [ITU-T H.248.1] | Recommendation ITU-T H.248.1 (2005), Gateway control protocol: Version 3. |
+| [ITU-T H.323] | Recommendation ITU-T H.323 (2003), Packet-based multimedia communications systems. |
+| [ITU-T H.324] | Recommendation ITU-T H.324 (2005), Terminal for low bit-rate multimedia communication. |
+| [ITU-T I.112] | Recommendation ITU-T I.112 (1993), Vocabulary of terms for ISDNs. |
+| [ITU-T I.113] | Recommendation ITU-T I.113 (1997), Vocabulary of terms for broadband aspects of ISDN. |
+| [ITU-T I.130] | Recommendation ITU-T I.130 (1988), Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN. |
+| [ITU-T I.210] | Recommendation ITU-T I.210 (1993), Principles of telecommunication services supported by an ISDN and the means to describe them. |
+| [ITU-T I.420] | Recommendation ITU-T I.420 (1988), Basic user-network interface. |
+| [ITU-T I.460] | Recommendation ITU-T I.460 (1999), Multiplexing, rate adaption and support of existing interfaces. |
+| [ITU-T I.461] | Recommendation ITU-T I.461/X.30 (1993), Support of X.21, X.21 bis and X.20 bis based Data Terminal Equipments (DTEs) by an Integrated Services Digital Network (ISDN). |
+| [ITU-T I.462] | Recommendation ITU-T I.462/X.31 (1995), Support of packet mode terminal equipment by an ISDN. |
+| [ITU-T I.463] | Recommendation ITU-T I.463/V.110 (2000), Support by an ISDN of data terminal equipments with V-series type interfaces. |
+| [ITU-T Q.65] | Recommendation ITU-T Q.65 (2000), The unified functional methodology for the characterization of services and network capabilities including alternative object oriented techniques. |
+| [ITU-T Q.920] | Recommendation ITU-T Q.920/I.440 (1993), ISDN user-network interface data link layer – General aspects. |
+| [ITU-T Q.921] | Recommendation ITU-T Q.921/I.441 (1997), ISDN user-network interface – Data link layer specification. |
+| [ITU-T Q.921 bis] | Recommendation ITU-T Q.921 bis (1993), Abstract test suite for LAPD conformance testing. |
+| [ITU-T Q.922] | Recommendation ITU-T Q.922 (1992), ISDN data link layer specification for frame mode bearer services. |
+| [ITU-T Q.1001] | Recommendation ITU-T Q.1001 (1988), General aspects of public land mobile networks. |
+
+| | |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [ITU-T Q.1214] | Recommendation ITU-T Q.1214 (1995), Distributed functional plane for intelligent network CS-1 . |
+| [ITU-T Q.1902.1] | Recommendation ITU-T Q.1902.1 (2001), Bearer Independent Call Control Protocol (Capability Set 2): Functional description . |
+| [ITU-T Q.1902.2] | Recommendation ITU-T Q.1902.2 (2001), Bearer Independent Call Control Protocol (Capability Set 2) and Signalling System No. 7 ISDN user part: General functions of messages and parameters . |
+| [ITU-T Q.1902.3] | Recommendation ITU-T Q.1902.3 (2001), Bearer Independent Call Control Protocol (Capability Set 2) and Signalling System No. 7 ISDN user part: Formats and codes . |
+| [ITU-T Q.1902.4] | Recommendation ITU-T Q.1902.4 (2001), Bearer Independent Call Control Protocol (Capability Set 2): Basic call procedures . |
+| [ITU-T Q.1902.5] | Recommendation ITU-T Q.1902.5 (2001), Bearer Independent Call Control Protocol (Capability Set 2): Exceptions to the Application transport mechanism in the context of BICC . |
+| [ITU-T Q.1902.6] | Recommendation ITU-T Q.1902.6 (2001), Bearer Independent Call Control protocol (Capability Set 2): Generic signalling procedures for the support of the ISDN user part supplementary services and for bearer redirection . |
+| [ITU-T T.31] | Recommendation ITU-T T.31 (1995), Asynchronous facsimile DCE control – Service Class 1 . |
+| [ITU-T T.32] | Recommendation ITU-T T.32 (1995), Asynchronous facsimile DCE control – Service Class 2 . |
+| [ITU-T V.14] | Recommendation ITU-T V.14 (1993), Transmission of start-stop characters over synchronous bearer channels . |
+| [ITU-T V.21] | Recommendation ITU-T V.21 (1988), 300 bits per second duplex modem standardized for use in the general switched telephone network . |
+| [ITU-T V.22] | Recommendation ITU-T V.22 (1988), 1200 bits per second duplex modem standardized for use in the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits . |
+| [ITU-T V.22 bis] | Recommendation ITU-T V.22 bis (1988), 2400 bits per second duplex modem using the frequency division technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits . |
+| [ITU-T V.24] | Recommendation ITU-T V.24 (2000), List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE) . |
+
+| | |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [ITU-T V.25 bis ] | Recommendation ITU-T V.25 bis (1996), Synchronous and asynchronous automatic dialling procedures on switched networks. |
+| [ITU-T V.25 ter ] | Recommendation ITU-T V.25 ter (1997), Serial asynchronous automatic dialling and control. |
+| [ITU-T V.26 ter ] | Recommendation ITU-T V.26 ter (1988), 2400 bits per second duplex modem using the echo cancellation technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits. |
+| [ITU-T V.32] | Recommendation ITU-T V.32 (1993), A family of 2-wire, duplex modems operating at data signalling rates of up to 9600 bit/s for use on the general switched telephone network and on leased telephone-type circuits. |
+| [ITU-T V.80] | Recommendation ITU-T V.80 (1996), In-band DCE control and synchronous data modes for asynchronous DTE. |
+| [ITU-T V.250 Sup.1] | Recommendation ITU-T V.250 Supplement 1 (2001), Various extensions to V.250 basic command set. |
+| [ITU-T X.21 bis ] | Recommendation ITU-T X.21 bis (1988), Use on public data networks of Data Terminal Equipment (DTE) which is designed for interfacing to synchronous V-Series modems. |
+| [ITU-T X.25] | Recommendation ITU-T X.25 (1996), Interface between Data Terminal Equipment (DTE) and Data Circuit-Terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit. |
+| [ITU-T X.32] | Recommendation ITU-T X.32 (1996), Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and accessing a Packet-Switched Public Data Network through a public switched telephone network or an Integrated Services Digital Network or a Circuit-Switched Public Data Network. |
+| [IETF RFC 3261] | IETF RFC 3261 (2002), SIP: Session Initiation Protocol. |
+| [ITU-T F.703] | Recommendation ITU-T F.703 (2000), Multimedia conversational services. |
+| [ITU-T I.363.2] | Recommendation ITU-T I.363.2 (2000), B-ISDN ATM Adaptation Layer specification: Type 2 AAL. |
+| [IETF RFC 768] | IETF RFC 768 (1980), User Datagram Protocol. |
+| [IETF RFC 1889] | IETF RFC 1889 (1996), RTP: A Transport Protocol for Real-Time Applications. |
+| [ETSI TS 102 241] | ETSI TS 102 241 (2008), Smart Cards; UICC Application Programming Interface (UICC API) for Java Card™, Release 7. |
+| [ETSI TS 102 484] | ETSI TS 102 484 V7.0.0 (2007), Smart Cards: Secure channel between a UICC and an end-point terminal (Release 7). |
+
+## 2.2 Informative references
+
+- [ARIB TR-T12-21.905] ARIB TR-T12-21.905 (2007), *Vocabulary for 3GPP Specifications*.
+- [CCSA-TSD-121 905] CCSA-TSD-121 905 (2007), *Vocabulary for 3GPP Specifications*.
+- [ETSI TR 121 905] ETSI TR 121 905 (2007), *Vocabulary for 3GPP Specifications*.
+- [ATIS 3GPP TR 21.905] ATIS 3GPP TR 21.905 (2007), *Vocabulary for 3GPP Specifications*.
+- [TTC TR-3GA-21.905] TTC TR-3GA-21.905 (2007), *Vocabulary for 3GPP Specifications*.
+
+# 3 Definitions
+
+The text is based on references in clause 2.2.
+
+This Recommendation defines the following terms:
+
+**3.1 A/Gb mode:** Mode of operation of the MS when connected to the core network via GERAN and the A and/or Gb interfaces.
+
+**3.2 applet:** A small program that is intended not to be run on its own, but rather to be embedded inside another application
+
+**3.3 application:** An application is a service enabler deployed by service providers, manufacturers or users. Individual applications will often be enablers for a wide range of services.
+
+**3.4 application interface:** Standardized interface used by application/clients to access service capability features.
+
+**3.5 application protocol:** The set of procedures required by the application.
+
+**3.6 authentication:** A property by which the correct identity of an entity or party is established with a required assurance. The party being authenticated could be a user, subscriber, home environment or serving network.
+
+**3.7 base station:** A base station is a network element in radio access network responsible for radio transmission and reception in one or more cells to or from the user equipment. A base station can have an integrated antenna or be connected to an antenna by feeder cables. In UTRAN, it terminates the Iub interface towards the RNC. In GERAN, it terminates the Abis interface towards the BSC.
+
+**3.8 base station subsystem:** Either a full network or only the access part of a GERAN offering the allocation, release and management of specific radio resources to establish means of connection between an MS and the GERAN. A base station subsystem is responsible for the resources and transmission/reception in a set of cells.
+
+**3.9 basic telecommunication service:** This term is used as a common reference to both bearer services and teleservices.
+
+**3.10 bearer:** An information transmission path of defined capacity, delay and bit error rate, etc.
+
+**3.11 bearer capability:** A transmission function, which the UE requests to the network.
+
+**3.12 bearer independent protocol:** (UICC) Mechanism by which the ME provides the (U)SIM applications on the UICC with access to the data bearers supported by the ME and the network.
+
+- 3.13 bearer service:** A type of telecommunication service that provides the capability of transmission of signals between access points.
+- 3.14 billing:** A function whereby CDRs generated by the charging function are transformed into bills requiring payment.
+- 3.15 broadcast:** A value of the service attribute "communication configuration", which denotes unidirectional distribution to all users (source: [ITU-T I.113]).
+- 3.16 byte code:** (UICC) A hardware machine-independent representation of a primitive computer operation that serves as an instruction to a software program called an interpreter or a virtual machine that simulates the hypothetical computer's central processing unit. Code generated by a Java compiler and executed by the Java interpreter.
+- 3.17 call:** A logical association between several users (this could be connection-oriented or connectionless).
+- 3.18 charging data record (CDR):** A formatted collection of information about a chargeable event (e.g., time of call set-up, duration of the call, amount of data transferred, etc.) for use in billing and accounting. For each party to be charged for parts of or all charges of a chargeable event, a separate CDR shall be generated, i.e., more than one CDR may be generated for a single chargeable event, e.g., because of its long duration, or because more than one charged party is to be charged.
+- 3.19 cell:** Radio network object that can be uniquely identified by a user equipment from a (cell) identification that is broadcasted over a geographical area from one UTRAN or GERAN access point. A Cell in UTRAN is either FDD or TDD mode.
+- 3.20 cellular text telephone modem (CTM):** A modulation and coding method intended for transmission of text in voice channels for the application of real-time text conversation.
+- 3.21 charging:** A function whereby information related to a chargeable event is formatted and transferred in order to make it possible to determine usage for which the charged party may be billed.
+- 3.22 cipher key:** A code used in conjunction with a security algorithm to encode and decode user and/or signalling data.
+- 3.23 closed user group:** A group with a predefined set of members. Only defined members may participate in a closed group.
+- 3.24 confidentiality:** The avoidance of disclosure of information without the permission of its owner.
+- 3.25 connection:** A communication channel between two or more end-points (e.g., terminal, server, etc.).
+- 3.26 connectionless (for a bearer service):** In a connectionless bearer, no connection is established beforehand between the source and the destination entities; the source and destination network addresses need to be specified in each message. Transferred information cannot be guaranteed of ordered delivery. Connectionless bearer services lifetime is reduced to the transport of one message.
+- 3.27 connectionless service:** A service, which allows the transfer of information among service users without the need for end-to-end call establishment procedures (source: [ITU-T I.113]).
+- 3.28 control channel:** A logical channel that carries system control information.
+- 3.29 core network:** An architectural term relating to the part of a 3G system, which is independent of the connection technology of the terminal (e.g., radio, wired).
+- 3.30 core network operator:** Operator that offers core network services.
+
+- 3.31 corporate code:** Code which, when combined with the network and SP codes, refers to a unique corporate. The code is provided in the GID2 file on the (U)SIM (see clause A.1) and is correspondingly stored on the ME.
+- 3.32 corporate code group:** Combination of the Corporate code and the associated SP and network codes.
+- 3.33 corporate personalization:** Allows a corporate customer to personalize MEs that he provides for his employees or customers use so that they can only be used with the company's own (U)SIMs.
+- 3.34 coverage area (of a mobile cellular system):** An area where mobile cellular services are provided by that mobile cellular system to the level required of that system.
+- 3.35 coverage area:** Area over which a 3G system service is provided with the service probability above a certain threshold.
+- 3.36 current directory:** The latest MF or DF selected on the UICC.
+- 3.37 current EF:** The latest EF selected.
+- 3.38 current serving cell:** This is the cell on which the MS is camped.
+- 3.39 data object:** Information coded as TLV objects, i.e., consisting of a tag, a length and a value part.
+- 3.40 dedicated channel:** A channel dedicated to a specific UE.
+- 3.41 de-personalization:** The process of deactivating the personalization so that the ME ceases to carry out the verification checks.
+- 3.42 dedicated file (DF):** A file containing access conditions and, optionally, elementary files (EFs) or other dedicated files (DFs).
+- 3.43 delivered QoS:** Actual QoS parameter values with which the content was delivered over the lifetime of a QoS session.
+- 3.44 demand service:** A type of telecommunication service in which the communication path is established almost immediately, in response to a user request effected by means of user-network signalling (source: [ITU-T I.112]).
+- 3.45 dependability:** A performance criterion that describes the degree of certainty (or surety) with which a function is performed regardless of speed or accuracy, but within a given observational interval (source: Recommendation ITU-T I.350).
+- 3.46 destination user:** Entity to which calls to the general packet radio service (GPRS) are directed.
+- 3.47 directory:** General term for the MF and/or a DF on the UICC.
+- 3.48 directory number:** A string consisting of one or more of the characters from the set {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, \*, #, a, b, c} associated with a nature of address indicator and number plan indicator. When using the public MMI for the control of supplementary services however, \* and # cannot be part of any SC or SI field.
+- NOTE 1 – No such restriction on the SC and SI fields exists when using other (e.g., menu-driven) MMI for the control of supplementary services.
+- NOTE 2 – When using the public MMI, certain limitations on the use of one- and two-digit directory numbers may apply. The use of other MMI can remove these restrictions.
+- NOTE 3 – This definition is not intended to require the support of all these characters in the MMI itself.
+- 3.49 distribution service:** Service characterized by the unidirectional flow of information from a given point in the network to other (multiple) locations (source: [ITU-T I.113]).
+
+- 3.50 domain:** The highest-level group of physical entities. Reference points are defined between domains.
+- 3.51 donor network:** The subscription network from which a number is ported in the porting process. This may or may not be the number range owner network.
+- 3.52 downlink:** Unidirectional radio link for the transmission of signals from a UTRAN access point to a UE. Also in general the direction from network to UE.
+- 3.53 drift RNS:** The role an RNS can take with respect to a specific connection between a UE and UTRAN. An RNS that supports the serving RNS with radio resources when the connection between the UTRAN and the user equipment needs to use cell(s) controlled by this RNS is referred to as "Drift RNS".
+- 3.54 element manager:** Provides a package of end-user functions for management of a set of closely related types of network elements. These functions can be divided into two main categories.
+- 3.55 elementary file (EF):** A file containing access conditions and data and no other files on the UICC.
+- 3.56 essential UE requirement (conditional):** Requirement which has to be implemented under certain service conditions, e.g., AMR codec in UE which supports speech service.
+- 3.57 essential UE requirement (unconditional):** Requirement which has to be implemented in any 3G UE in order to exist in and communicate with the 3G network (e.g., chip rate of 3.84 Mcps).
+- 3.58 explicit diversity gain (dB):** The effective gain achieved using diversity techniques.
+- 3.59 extra SDU delivery probability:** The ratio of total (unrequested) extra service data units (SDUs) to total service data units received by a destination user in a specified sample (source: Recommendation ITU-T X.140).
+- 3.60 file:** A named and hierarchically-classified data set on the UICC.
+- 3.61 file identifier (FID):** The 2-byte name of a file or a directory on the UICC.
+- 3.62 fixed network user rate:** The user rate between IWF and the fixed network.
+- 3.63 flow control (FC):** A set of mechanisms used to prevent the network from becoming overloaded by regulating the input rate transmissions.
+- 3.64 flexible layer one (FLO):** GERAN feature that allows the channel coding of the layer one to be configured at call set-up.
+- 3.65 framework:** A framework defines a set of application programming interface (API) classes for developing applications and for providing system services to those applications.
+- 3.66 functional group:** A set of functions that may be performed by a single equipment (source: [ITU-T I.112]).
+- 3.67 geographical routing:** The conversion of the PDU's geographical area definition, which specifies the area in which the PDU will be broadcast, into an equivalent radio coverage map.
+- 3.68 GERAN radio network temporary identifier (G-RNTI):** An MS identifier which is allocated by the serving BSC and is unique within this SBSC. It is allocated for all MSs having an RRC connection. The G-RNTI is always reallocated when the Serving BSC for the RRC connection is changed and deallocated when the RRC connection is released. The G-RNTI is also used at RLC/MAC during contention resolution.
+- 3.69 GPRS MS:** An MS capable of GPRS services.
+
+- 3.70 group:** A set of members allowed to participate in the group call service. The group is defined by a set of rules that identifies a collection of members implicitly or explicitly. These rules may associate members for the purpose of participating in a group call, or may associate members who do not participate in data transfer but do participate in management, security, control, or accounting for the group.
+- 3.71 group call:** The relationship that exists between the members of a group for the purpose of transferring data. More than one group call may exist in a group. A group call establishes an active group.
+- 3.72 group call initiator:** A member (or third party) authorized to initiate a group call. More than one member may initiate group calls.
+- 3.73 group call participant:** A member of a group participating in a particular group call at a given time.
+- 3.74 group call server:** A logical entity that provides the group call service to the members.
+- 3.75 group call service:** A PTM service in which a relationship exists between participants of the group, and in which a single data unit transmitted by a source participant is received by multiple destination participants; it is a one-in, many-out service.
+- 3.76 group controller:** The member (or third party) responsible for the group creation and membership control.
+- 3.77 GSM/EDGE radio access network (GERAN):** A conceptual term identifying that part of the network which consists of BSCs and BTSs between A/Gb or Iu and Um interfaces.
+- 3.78 GSM BSS:** Refers in this Recommendation to the GSM/GPRS access network.
+- 3.79 GSM core network:** Refers in this Recommendation to the GSM NSS and GPRS backbone infrastructure.
+- 3.80 GSM coverage:** An area where mobile cellular services are provided in accordance with GSM standards.
+- 3.81 GSM session:** That part of the card session dedicated to the GSM operation.
+- 3.82 guaranteed service:** A service model which provides highly reliable performance, with little or no variance in the measured performance criteria.
+- 3.83 handoff gain/loss (dB):** This is the gain/loss factor (+ or –) brought by handoff to maintain specified reliability at the cell boundary.
+- 3.84 handover:** The transfer of a user's connection from one radio channel to another (can be the same or different cell).
+- 3.85 handover:** The process in which the radio access network changes the radio transmitters or radio access mode or radio system used to provide the bearer services, while maintaining a defined bearer service QoS.
+- 3.86 hard handover:** A category of handover procedures where all the old radio links in the UE are abandoned before the new radio links are established.
+- 3.87 home environment value-added service provider (HE-VASP):** This is a VASP that has an agreement with the home environment to provide services. The home environment provides services to the user in a managed way, possibly by collaborating with HE-VASPs, but this is transparent to the user. The same service could be provided by more than one HE-VASP and each HE-VASP can provide more than one service.
+- 3.88 home environment:** Responsible for overall provision and control of the personal service environment of its subscribers.
+
+- 3.89 home PLMN:** PLMN where the mobile country code (MCC) and mobile network code (MNC) of the PLMN identity are the same as the MCC and MNC of the IMSI.
+- 3.90 IC card:** A card holding an integrated circuit containing subscriber, end-user, authentication and/or application data for one or more applications.
+- 3.91 idle mode:** The state of UE switched on but which does not have any established RRC connection.
+- 3.92 implementation capability:** A capability that relates to a particular technical domain. Examples: a spreading factor of 128 (in the domain of the physical layer); the A5 algorithm; a 64-bit key length (in the domain of security); a power output of 21 dBm (in the domain of transmitter performance); support of AMR codec (in the domain of the codec); support of CHV1 (in the domain of the USIM).
+- 3.93 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.94 information data rate:** Rate of the user information, which must be transmitted over the air interface. For example, output rate of the voice codec.
+- 3.95 initial paging information:** This information indicates if the UE needs to continue to read more paging information and eventually receive a page message.
+- 3.96 initial paging occasion:** The paging occasion the UE uses as starting point for its paging DRX cycle.
+- 3.97 integrity:** (in the context of security) The avoidance of unauthorized modification of information.
+- 3.98 inter-cell handover:** A handover between different cells. An inter-cell handover requires network connections to be altered.
+- 3.99 inter-PLMN handover:** Handover between different PLMNs, i.e., having different MCC-MNC.
+- 3.100 inter-system handover:** Handover between networks using different radiosystems, e.g., UMTS – GSM.
+- 3.101 interactive service:** A service which provides the means for bidirectional exchange of information between users. Interactive services are divided into three classes of services: conversational services, messaging services and retrieval services (source: [ITU-T I.113]).
+- 3.102 interface:** The common boundary between two associated systems (source: [ITU-T I.112]).
+- 3.103 international mobile station equipment identity (IMEI):** An "International Mobile Station Equipment Identity" is a unique number, which shall be allocated to each individual mobile station equipment in the PLMN and shall be unconditionally implemented by the MS manufacturer.
+- 3.104 international mobile user number (IMUN):** The international mobile user number is a diallable number allocated to a 3GPP system user.
+- 3.105 interpreter:** A software program that simulates a hypothetical computer by performing the operations defined by the instructions of this computer. (See also "byte code" and "virtual machine").
+- 3.106 interworking WLAN (I-WLAN):** A WLAN that interworks with a 3GPP system.
+- 3.107 intra-cell handover:** A handover within one sector or between different sectors of the same cell. An intra-cell handover does not require network connections to be altered.
+
+**3.108 intra-PLMN handover:** Handover within the same network, i.e., having the same MCC-MNC regardless of radio access system.
+
+NOTE – This includes the case of UMTS $\leftrightarrow$ GSM handover where MCC-MNC are the same in both cases.
+
+**3.109 IP-connectivity access network (IP-CAN):** The collection of network entities and interfaces that provides the underlying IP transport connectivity between the UE and the IMS entities. An example of an "IP-Connectivity Access Network" is GPRS.
+
+**3.110 IP-connectivity access network bearer (IP-CAN bearer):** The data communications bearer provided by the IP-connectivity access network. When using GPRS, the IP-connectivity access network bearers are provided by PDP Contexts.
+
+**3.111 IRP information model:** An IRP information model consists of an IRP information service and a network resource model (see below for definitions of "IRP Information Service" and "Network Resource Model").
+
+**3.112 IRP information service:** An IRP information service describes the information flow and support objects for a certain functional area, e.g., the alarm information service in the fault management area. As an example of support objects, for the alarm IRP there is the alarm record and alarm list.
+
+**3.113 IRP solution set:** An IRP solution set is a mapping of the IRP information service to one of several technologies (CORBA/IDL, SNMP/SMI, CMIP/GDMO, etc.). An IRP information service can be mapped to several different IRP solution sets. Different technology selections may be done for different IRPs.
+
+**3.114 inter-system change:** A change of radio access between different radio access technologies such as GSM and UMTS.
+
+**3.115 IMS SIM (ISIM):** An application residing on the UICC that provides access to IP multimedia services.
+
+**3.116 Iu:** Interconnection point between an RNC and a core network. It is also considered as a reference point.
+
+**3.117 Iu-flex:** Routing functionality for intradomain connection of RAN nodes to multiple CN nodes.
+
+**3.118 Iub:** Interface between an RNC and a Node B.
+
+**3.119 Iur:** A logical interface between two RNC. Whilst logically representing a point-to-point link between RNC, the physical realization may not be a point-to-point link.
+
+**3.120 key pair:** Key pairs are matching private and public keys. If a block of data is encrypted using the private key, the public key from the pair can be used to decrypt it. The private key is never divulged to any other party, but the public key is available, e.g., in a certificate.
+
+**3.121 local service:** Services, which are provided by current roamed to network that are not HE services. The same service can be provided by a network as a local service to inbound roamers and as a HE service to the subscribers of this network.
+
+**3.122 localized service area (LSA):** An operator-defined group of cells, for which specific access conditions apply. This may correspond to an area in which the core network offers specific services. A LSA may be defined within a PLMN or globally. Therefore, a LSA may offer a non-contiguous radio coverage.
+
+**3.123 location registration (LR):** The UE registers its presence in a registration area, for instance regularly or when entering a new registration area.
+
+**3.124 logical channel:** A logical channel is an information stream dedicated to the transfer of a specific type of information over the radio interface. Logical channels are provided on top of the MAC layer.
+
+**3.125 logical channel (UICC):** A command/response communication context multiplexed on the physical channel between the ME and the UICC.
+
+**3.126 logical model:** A logical model defines an abstract view of a network or network element by means of information objects representing network element, aggregations of network elements, the topological relationship between the elements, endpoints of connections (termination points), and transport entities (such as connections) that transport information between two or more termination points.
+
+The information objects defined in the logical model are used, among others, by connection management functions. In this way, a physical implementation independent management is achieved.
+
+**3.127 logical O&M:** The signalling associated with the control of logical resources (channels, cells) owned by the RNC but physically implemented in the Node B. The RNC controls these logical resources. A number of O&M procedures physically implemented in Node B impact on the logical resources and therefore require an information exchange between RNC and Node B. All messages needed to support this information exchange are classified as Logical O&M forming an integral part of NBAP.
+
+**3.128 LSA exclusive access cell:** A UE may only camp on this cell if the cell belongs to the LSAs to which the user has subscribed. Nevertheless, if no other cells are available, the UE of non-LSA users may originate emergency calls from this cell.
+
+**3.129 LSA only access:** When LSA only access applies to the user, the UE can only access cells that belong to the LSAs to which the user has subscribed. Outside the coverage area of the subscribed LSAs, the UE may camp on other cells and limited services apply.
+
+**3.130 LSA preferential access cell:** A LSA preferential access cell is a cell which is part of the LSA. UEs of users that have subscribed to a LSA of a LSA-preferential-access cell have higher priority to resources than non-LSA users in the same cell.
+
+**3.131 macro cells:** "Macro cells" are outdoor cells with a large cell radius.
+
+**3.132 macro diversity handover:** "Macro diversity" is an operation state in which a user equipment simultaneously has radio links with two or more UTRAN access points for the sole aim of improving quality of the radio connection or providing seamless.
+
+**3.133 management infrastructure:** The collection of systems (computers and telecommunications) a 3GPP System Organization has in order to manage a 3GPP System.
+
+**3.134 mandatory UE requirement:** Regulatory requirement which is applicable to 3G UEs. It is determined by each country/region and beyond the scope of 3GPP specification (e.g., spurious emission in UK).
+
+**3.135 master file (MF):** The root directory of the file system hierarchy on the UICC.
+
+**3.136 maximum output power:** For UE, this is a measure of the maximum power supported by the UE (i.e., the actual power as would be measured assuming no measurement error) (TS 25.101). For FDD BS, the mean power level per carrier of the base station measured at the antenna connector in a specified reference condition (TS 25.104). For TDD BS, this refers to the measure of power when averaged over the transmit timeslot at the maximum power setting (TS 25.105).
+
+**3.137 maximum possible AIUR:** The highest possible AIUR that the multiple TCH/F can provide, e.g., 2 TCH/F using TCH/F9.6 provides a maximum possible AIUR of 19.2 kbit/s.
+
+- 3.138 maximum transmitter power per traffic channel (dBm):** The maximum power at the transmitter output for a single traffic channel.
+- 3.139 mean bit rate:** A measure of throughput. The average (mean) bit rate available to the user for the given period of time (source: [ITU-T I.210]).
+- 3.140 mean transit delay:** The average transit delay experienced by a (typically) large sample of PDUs within the same service category.
+- 3.141 medium access control:** A sub-layer of radio interface layer 2 providing unacknowledged data transfer service on logical channels and access to transport channels.
+- 3.142 messaging service:** An interactive service, which offers user-to-user communication between individual users via storage units with store-and-forward, mailbox and/or message handling (e.g., information editing, processing and conversion) functions (source: [ITU-T I.113]).
+- 3.143 MExE classmark:** A MExE classmark identifies a category of MExE UE supporting MExE functionality with a minimum level of processing, memory, display, and interactive capabilities. Several MExE classmarks may be defined to differentiate between the functionalities offered by different MExE UEs. A MExE application or applet defined as being of a specific MExE classmark indicates that it is supportable by a MExE UE of that classmark.
+- 3.144 MExE executable:** An executable is an applet, application, or executable content, which conforms to the MExE specification and may execute on the ME.
+- 3.145 MExE server:** A node supporting MExE services in the MExE service environment.
+- 3.146 MExE service:** A service enhanced (or made possible) by MExE technology.
+- 3.147 MExE service environment:** Depending on the configuration of the PLMN, the operator may be able to offer support to MExE services in various ways. Examples of possible sources are from traditional GSM nodes, IN nodes, operator-specific nodes, operator franchised nodes and services provider nodes, together with access to nodes external (i.e., vendor-specific) to the PLMN depending on the nature of the MExE service. These nodes are considered to constitute the MExE service environment. The MExE service environment shall support direct MExE UE to MExE UE interaction of MExE services.
+- 3.148 MExE SIM:** A (U)SIM application that is capable of storing a security certificate that is accessible using standard mechanisms.
+- 3.149 MExE subscriber:** The owner of a subscription who has entered into an agreement with a MExE service provider for MExE services.
+- 3.150 micro cells:** "Micro cells" are small cells.
+- 3.151 minimum transmit power:** The minimum controlled output power of the TDD BS is when the power control setting is set to a minimum value. This is when the power control indicates a minimum transmit output power is required (TS 25.105).
+- 3.152 mobile evaluated handover (MEHO):** A type of handover triggered by an evaluation made in the mobile. The mobile evaluates the necessity of handover based on the measured radio environment and based on criteria, defined by the network. When the evaluation meets the hand-off criteria the necessary information is sent from the mobile to the network. The network then decides on the necessity of the handover based on the reported evaluation result and other conditions, e.g., uplink radio environment and/or availability of network resources; the network may then execute the handover.
+- 3.153 mobile number portability:** The ability for a mobile subscriber to change subscription network within the same country whilst retaining their original MSISDN(s).
+
+- 3.154 mobile termination:** The mobile termination is the component of the mobile station which supports functions specific to management of the radio interface (Um).
+- 3.155 mobility:** The ability for the user to communicate whilst moving independent of location.
+- 3.156 mobility management:** A relation between the mobile station and the UTRAN that is used to set up, maintain and release the various physical channels.
+- 3.157 multi-mode terminal:** UE that can obtain service from at least one UTRA radio access mode, and one or more different systems such as GSM bands or possibly other radio systems such as IMT-2000 Family Members.
+- 3.158 multicast service:** A unidirectional PTM service in which a message is transmitted from a single source entity to all subscribers currently located within a geographical area. The message contains a group identifier indicating whether the message is of interest to all subscribers or to only the subset of subscribers belonging to a specific multicast group.
+- 3.159 multipoint:** A value of the service attribute "communication configuration", which denotes that the communication involves more than two network terminations (source: [ITU-T I.113]).
+- 3.160 multimedia service:** Services that handle several types of media such as audio and video in a synchronized way from the user's point of view. A multimedia service may involve multiple parties, multiple connections, and the addition or deletion of resources and users within a single communication session.
+- 3.161 name:** A name is an alphanumeric label used for identification of end users and may be portable.
+- 3.162 negotiated QoS:** In response to a QoS request, the network shall negotiate each QoS attribute to a level that is in accordance with the available network resources. After QoS negotiation, the bearer network shall always attempt to provide adequate resources to support all of the negotiated QoS profiles.
+- 3.163 network code:** MCC and MNC.
+- 3.164 network code group:** Same as "network code".
+- 3.165 network connection:** An association established by a network layer between two users for the transfer of data, which provides explicit identification of a set of network data transmissions and agreement concerning the services to be provided by the set (source: Rec. ITU-T X.213 | ISO/IEC 8348).
+- 3.166 network element:** A discrete telecommunications entity, which can be managed over a specific interface, e.g., the RNC.
+- 3.167 network manager:** Provides a package of end-user functions with the responsibility for the management of a network, mainly as supported by the EM(s) but it may also involve direct access to the network elements. All communication with the network is based on open and well-standardized interfaces supporting management of multi-vendor and multi-technology network elements.
+- 3.168 network operator:** See "PLMN operator".
+- 3.169 network personalization:** Allows the network operator to personalize a ME so that it can only be used with that particular network operator's (U)SIMs.
+- 3.170 network resource model:** A protocol-independent model describing managed objects representing network resources, e.g., an RNC or Node B.
+- 3.171 network service data unit (NSDU):** A unit of data passed between the user and the GPRS network across a network service access point (NSAP).
+
+- 3.172 network subset code:** Digits 6 and 7 of the IMSI.
+- 3.173 network subset personalization:** A refinement of network personalization, which allows network operators to limit the usage of a ME to a subset of (U)SIMs.
+- 3.174 network termination:** A functional group on the network side of a user-network interface (source: [ITU-T I.112]).
+- 3.175 nomadic operating mode:** Mode of operation where the terminal is transportable but being operated while stationary and may in addition require user cooperation (e.g., close to open spaces, antenna set-up, etc.).
+- 3.176 nominal maximum output power:** This is the nominal power defined by the UE power class.
+- 3.177 non-access stratum:** Protocols between UE and the core network that are not terminated in the UTRAN.
+- 3.178 normal GSM operation:** Relating to general, CHV-related, GSM security-related and subscription-related procedures.
+- 3.179 normal mode of operation:** The mode of operation into which the ME would have gone if it had no personalization checks to process.
+- 3.180 narrow TDD (NTDD):** The 1.28 Mcps chip rate UTRA-TDD option.
+- 3.181 number:** A string of decimal digits that uniquely indicates the public network termination point. The number contains the information necessary to route the call to this termination point.
+- A number can be in a format determined nationally or in an international format. The international format is known as the international public telecommunication number which includes the country code and subsequent digits, but not the international prefix.
+- 3.182 number portability:** Where the provision of diallable numbers is independent of home environment and/or serving network.
+- 3.183 open service architecture:** Concept for introducing a vendor-independent means for introduction of new services.
+- 3.184 operations system:** This term indicates a generic management system, independent of its location level within the management hierarchy.
+- 3.185 OSA interface:** Standardized interface used by application/clients to access service capability features.
+- 3.186 packet:** An information unit identified by a label at layer 3 of the OSI reference model (source: [ITU-T I.113]). A network protocol data unit (NPDU).
+- 3.187 packet data protocol (PDP):** Any protocol, which transmits data as discrete units known as packets, e.g., IP, or [ITU-T X.25].
+- 3.188 packet transfer mode:** Also known as "packet mode". A transfer mode in which the transmission and switching functions are achieved by packet-oriented techniques, so as to dynamically share network transmission and switching resources between a multiplicity of connections (source: [ITU-T I.113]).
+- 3.189 padding:** One or more bits appended to a message in order to cause the message to contain the required number of bits or bytes.
+- 3.190 paging:** The act of seeking a user equipment.
+- 3.191 paging occasion:** The frame where the UE monitors in FDD or the paging block, which consists of several frames, for TDD. For paging blocks, the value of paging occasion is equal to the first frame of the paging block.
+
+**3.192 peak bit rate:** A measure of throughput. The maximum bit rate offered to the user for a given time period (to be defined) for the transfer of a bursty signal (source: [ITU-T I.210]). (The maximum user information transfer rate achievable by a user for a single service data unit transfer.)
+
+**3.193 performance:** The ability to track service and resource usage levels and to provide feedback on the responsiveness and reliability of the network.
+
+**3.194 personal service environment:** Contains personalized information defining how subscribed services are provided and presented towards the user. Each subscriber of the home environment has her own personal service environment. The personal service environment is defined in terms of one or more user profiles.
+
+**3.195 personalization:** The process of storing information in the ME and activating the procedures, which verify this information against the corresponding information stored in the SIM whenever the ME is powered up or a SIM is inserted, in order to limit the SIMs with which the ME will operate.
+
+**3.196 personalization entity:** Network, network subset, SP, Corporate or (U)SIM to which the ME is personalized.
+
+**3.197 phonebook:** A dataset of personal or entity attributes. The simplest form is a set of name-subscriber phone number pairs as supported by GSM (U)SIMs.
+
+**3.198 physical channel data stream:** In the uplink, a data stream that is transmitted on one physical channel. In the downlink, a data stream that is transmitted on one physical channel in each cell of the active set.
+
+**3.199 physical channel:** In FDD mode, a physical channel is defined by code, frequency and, in the uplink, relative phase (I/Q). In TDD mode, a physical channel is defined by code, frequency, and time-slot.
+
+**3.200 pico cells:** "Pico cells" are cells, mainly indoor cells, with a radius typically less than 50 metres.
+
+**3.201 PICH monitoring occasion:** The time instance where the UE monitors PICH within paging occasion.
+
+**3.202 PLMN area:** The geographical area in which a PLMN provides communication services according to the specifications to mobile users. In the PLMN area, the mobile user can set up calls to a user of a terminating network. The terminating network may be a fixed network, the same PLMN, another PLMN or other types of PLMN. Terminating network users can also set up calls to the PLMN. The PLMN area is allocated to a PLMN. It is determined by the service and network provider in accordance with any provisions laid down under national law. In general, the PLMN area is restricted to one country. It can also be determined differently, depending on the different telecommunication services, or type of MS. If there are several PLMNs in one country, their PLMN areas may overlap. In border areas, the PLMN areas of different countries may overlap. Administrations will have to take precautions to ensure that cross border coverage is minimized in adjacent countries unless otherwise agreed.
+
+**3.203 public land mobile network operator (PLMN operator):** The entity which offers telecommunications services over an air interface.
+
+**3.204 point-to-multipoint service:** A service type in which data is sent to "all service subscribers or a predefined subset of all subscribers" within an area defined by the service requester.
+
+**3.205 point-to-point:** A value of the service attribute "communication configuration", which denotes that the communication involves only two network terminations.
+
+**3.206 point-to-point service:** A service type in which data is sent from a single network termination to another network termination.
+
+- 3.207** **ported number:** A MSISDN that has undergone the porting process.
+- 3.208** **ported subscriber:** The subscriber of a ported number.
+- 3.209** **porting process:** A description of the transfer of a number between network operators.
+- 3.210** **power control dynamic range:** The difference between the maximum and the minimum total transmit output power for a specified reference condition (TS 25.104).
+- 3.211** **predictive service:** A service model which provides reliable performance, but allowing a specified variance in the measured performance criteria.
+- 3.212** **prepay billing:** Billing arrangement between customer and operator/service provider where the customer deposits an amount of money in advance, which is subsequently used to pay for service usage.
+- 3.213** **postpay billing:** Billing arrangement between customer and operator/service provider where the customer periodically receives a bill for service usage in the past period.
+- 3.214** **proactive SIM:** A SIM which is capable of issuing commands to the terminal. Part of SIM application toolkit.
+- 3.215** **protocol:** A formal set of procedures that are adopted to ensure communication between two or more functions within the same layer of a hierarchy of functions (source: [ITU-T I.112]).
+- 3.216** **public land mobile network:** A telecommunications network providing mobile cellular services.
+- 3.217** **QoS profile:** A QoS profile comprises a number of QoS parameters. A QoS profile is associated with each QoS session. The QoS profile defines the performance expectations placed on the bearer network.
+- 3.218** **QoS session:** Lifetime of PDP context. The period between the opening and closing of a network connection whose characteristics are defined by a QoS profile. Multiple QoS sessions may exist, each with a different QoS profile.
+- 3.219** **quality of service:** The collective effect of service performances, which determine the degree of satisfaction of a user of a service. It is characterized by the combined aspects of performance factors applicable to all services, such as:
+- service operability performance;
+ - service accessibility performance;
+ - service retainability performance;
+ - service integrity performance; and
+ - other factors specific to each service.
+- 3.220** **radio access bearer:** The service that the access stratum provides to the non-access stratum for transfer of user data between user equipment and CN.
+- 3.221** **radio access mode:** Mode of the cell, FDD or TDD.
+- 3.222** **RAN sharing:** Two or more CN operators share the same RAN, i.e., a RAN node (RNC or BSC) is connected to multiple CN nodes (SGSNs and MSC/VLRs) belonging to different CN operators.
+- 3.223** **radio access network application part:** Radio network signalling over the Iu.
+- 3.224** **radio access network operator:** Operator that offers radio access to one or more core network operators.
+- 3.225** **radio access network technology:** UTRAN, GERAN, etc.
+
+- 3.226 radio interface:** The "radio interface" is the tetherless interface between user equipment and a UTRAN access point. This term encompasses all the functionality required to maintain such interfaces.
+- 3.227 radio link:** A "radio link" is a logical association between single user equipment and a single UTRAN access point. Its physical realization comprises one or more radio bearer transmissions.
+- 3.228 radio link control:** A sublayer of radio interface layer 2 providing transparent, unacknowledged and acknowledged data transfer service.
+- 3.229 radio network controller:** This equipment in the RNS is in charge of controlling the use and the integrity of the radio resources.
+- 3.230 radio network subsystem:** Either a full network or only the access part of a UTRAN offering the allocation and the release of specific radio resources to establish means of connection in between an UE and the UTRAN. A radio network subsystem is responsible for the resources and transmission/reception in a set of cells.
+- 3.231 radio system:** The selected 2nd or 3rd generation radio access technology.
+- 3.232 real time:** Time, typically in number of seconds, to perform the online mechanism used for fraud control and cost control.
+- 3.233 received signal code power:** Given only signal power is received, the average power of the received signal after despreading and combining.
+- 3.234 receiver antenna gain (dBi):** The maximum gain of the receiver antenna in the horizontal plane (specified as dB relative to an isotropic radiator).
+- 3.235 receiver noise figure (dB):** The noise figure of the receiving system referenced to the receiver input.
+- 3.236 receiver sensitivity (dBm):** This is the signal level needed at the receiver input that just satisfies the required $E_b/(N_0+I_0)$ .
+- 3.237 recipient network:** The network which receives the number in the porting process. This network becomes the subscription network when the porting process is complete.
+- 3.238 record:** A string of bytes within an EF handled as a single entity (see clause 6).
+- 3.239 record number:** The number which identifies a record within an EF.
+- 3.240 record pointer:** The pointer which addresses one record in an EF.
+- 3.241 reference configuration:** A combination of functional groups and reference points that shows possible network arrangements (source: [ITU-T I.112]).
+- 3.242 reference point:** A conceptual point at the conjunction of two non-overlapping functional groups (source: [ITU-T I.112]).
+- 3.243 regionally provided service:** A service entitlement to only certain geographical part(s) of a PLMN, as controlled by the network operator.
+- 3.244 registration:** This is the process of camping on a cell of the PLMN and doing any necessary LRs.
+- 3.245 registered PLMN (RPLMN):** This is the PLMN on which the UE has performed a location registration successfully.
+- 3.246 registration area:** A (NAS) registration area is an area in which the UE may roam without a need to perform location registration, which is a NAS procedure.
+- 3.247 relay:** Terminal devices capable of ODMA relay communications.
+
+- 3.248 relay/seed gateway:** Relay or seed that communicates with the UTRAN, in either TDD or FDD mode.
+- 3.249 relaylink:** Relaylink is a communications link between two ODMA relay nodes.
+- 3.250 release 99:** A particular version of the 3G System standards produced by the 3GPP project. Also: Release 4, Release 5, Release 6, Release 7, etc.
+- 3.251 repeater:** A radio transceiver used to extend the transmission of a base station beyond its normal range.
+- 3.252 requested QoS:** A QoS profile is requested at the beginning of a QoS session. QoS modification requests are also possible during the lifetime of a QoS session.
+- 3.253 required Eb/(No+Io) (dB):** The ratio between the received energy per information bit to the total effective noise and interference power density needed to satisfy the quality objectives.
+- 3.254 residual error rate:** A parameter describing service accuracy. The frequency of lost SDUs and of corrupted or duplicated network SDUs delivered at the user-network interface.
+- 3.255 retrieval service:** An interactive service which provides the capability of accessing information stored in database centres. The information will be sent to the user on demand only. The information is retrieved on an individual basis, i.e., the time at which an information sequence is to start is under the control of the user (source [ITU-T I.113]).
+- 3.256 roaming:** The ability for a user to function in a serving network different from the home network.
+- 3.257 RRC connection:** A point-to-point bidirectional connection between RRC peer entities on the UE and the UTRAN sides, respectively. An UE has either zero or one RRC connection.
+- 3.258 SDU error probability:** The ratio of total incorrect service data units (SDUs) to total successfully transferred service data units plus incorrect service data units in a specified sample (source: Rec. ITU-T X.140).
+- NOTE – The source document term "user information unit" has been replaced by the term "service data unit".
+- 3.259 SDU loss probability:** The ratio of total lost service data units (SDUs) to total transmitted service data units in a specified sample (source: Rec. ITU-T X.140).
+- NOTE – The source document term "user information unit" has been replaced by the term "service data unit".
+- 3.260 SDU misdelivery probability:** The ratio of total misdelivered service data units (SDUs) to total service data units transferred between a specified source and destination user in a specified sample (source: Rec. ITU-T X.140).
+- NOTE – The source document term "user information unit" has been replaced by the term "service data unit".
+- 3.261 SDU transfer delay:** The value of elapsed time between the start of transfer and successful transfer of a specified service data unit (SDU) (source: Rec. ITU-T X.140).
+- NOTE – The source document term "user information unit" has been replaced by the term "service data unit".
+- 3.262 SDU transfer rate:** The total number of successfully transferred service data units (SDUs) in a transfer sample divided by the input/output time for that sample. The input/output time is the larger of the input time or the output time for the sample (source: Rec. ITU-T X.140).
+- NOTE – The source document term "user information unit" has been replaced by the term "service data unit".
+- 3.263 seamless handover:** A handover without perceptible interruption of the radio connection.
+
+- 3.264 sector:** A sub-area of a cell. All sectors within one cell are served by the same base station. A radio link within a sector can be identified by a single logical identification belonging to that sector.
+- 3.265 secured packet:** The information flow on top of which the level of required security has been applied. An application message is transformed with respect to a chosen transport layer and chosen level of security into one or more secured packets.
+- 3.266 security:** The ability to prevent fraud as well as the protection of information availability, integrity and confidentiality.
+- 3.267 service area:** The service area is defined in the same way as the service area according to [ITU-T Q.1001]. In contrast to the PLMN area, it is not based on the coverage of a PLMN. Instead, it is based on the area in which a fixed network user can call a mobile user without knowing his location. The service area can therefore change when the signalling system is being extended, for example.
+- 3.268 service capabilities:** Bearers defined by parameters, and/or mechanisms needed to realize services. These are within networks and under network control.
+- 3.269 service capability feature:** Functionality offered by service capabilities that are accessible via the standardized application interface.
+- 3.270 service capability server:** Network functionality providing open interfaces towards the functionality offered by 3G System service capabilities.
+- 3.271 service control:** The ability of the user, home environment or serving environment to determine what a particular service does, for a specific invocation of that service, within the limitations of that service.
+- 3.272 service enabler:** A capability which may be used, either by itself or in conjunction with other service enablers, to provide a service to the end user.
+- 3.273 service request:** This is defined as being one invocation of the service through a service request primitive.
+- 3.274 service requester:** The entity which requests the initiation of a GPRS operation, through a service request.
+- 3.275 service subscriber:** The entity which subscribes to the general packet radio service (GPRS) service.
+- 3.276 services (of a mobile cellular system):** The set of functions that the mobile cellular system can make available to the user.
+- 3.277 serving network:** The serving network provides the user with access to the services of home environment.
+- 3.278 settlement:** Payment of amounts resulting from the accounting process.
+- 3.279 shared network:** When two or more network operators share network elements.
+- 3.280 SIM personalization:** Enables a user to personalize a ME so that it may only be used with particular SIM(s).
+- 3.281 speed:** A performance criterion that describes the time interval required to perform a function or the rate at which the function is performed. (The function may or may not be performed with the desired accuracy.) (source: Rec. ITU-T I.350).
+
+- 3.282 SRNC radio network temporary identifier (S-RNTI):** A UE identifier which is allocated by the serving RNC and unique within this SRNC. It is allocated for all UEs having a RRC connection. S-RNTI is reallocated always when the serving RNC for the RRC connection is changed and deallocated when the RRC connection is released.
+- 3.283 SRNS relocation:** The change of Iu instance and transfer of the SRNS role to another RNS.
+- 3.284 stratum:** Grouping of protocols related to one aspect of the services provided by one or several domains.
+- 3.285 sub-network management functions:** Set of functions that are related to a network model for a set of network elements constituting a clearly defined sub-network, which may include relations between the network elements. This model enables additional functions on the sub-network level (typically in the areas of network topology presentation, alarm correlation, service impact analysis and circuit provisioning).
+- 3.286 subscribed QoS:** The network will not grant a QoS greater than the subscribed QoS. The QoS profile subscription parameters are held in the HLR. An end user may have several QoS subscriptions. For security and the prevention of damage to the network, the end user cannot directly modify the QoS subscription profile data.
+- 3.287 subscriber:** An entity (associated with one or more users) that is engaged in a subscription with a service provider. The subscriber is allowed to subscribe and unsubscribe services, to register a user or a list of users authorized to enjoy these services, and also to set the limits relative to the use that associated users make of these services.
+- 3.288 subscription:** A subscription describes the commercial relationship between the subscriber and the service provider.
+- 3.289 subscription management (SuM):** Set of capabilities that allow operators, service providers, and indirectly subscribers, to provision, control, monitor the subscription profile.
+- 3.290 suitable cell:** This is a cell on which an UE may camp. It must satisfy certain conditions.
+- 3.291 supplementary service:** A service which modifies or supplements a basic telecommunication service. Consequently, it cannot be offered to a user as a stand-alone service. It must be offered together with or in association with a basic telecommunication service. The same supplementary service may be common to a number of basic telecommunication services.
+- 3.292 system area:** The group of PLMN areas accessible by MSs. Interworking of several PLMNs and interworking between PLMNs and fixed network(s) permit public land mobile communication services at international level.
+- 3.293 telecommunication service:** What is offered by a PLMN operator or service provider to its customers in order to satisfy a specific telecommunication requirement. (source: [ITU-T I.112]). Telecommunication services are divided into two broad families: bearer services and teleservices (source: [ITU-T I.210]).
+- 3.294 teleservice:** A type of telecommunication service that provides the complete capability, including terminal equipment functions, for communication between users according to standardized protocols and transmission capabilities established by agreement between operators.
+- 3.295 text conversation:** Real-time transfer of text between users in at least two locations.
+- 3.296 text telephony:** An audiovisual conversation service providing bidirectional real-time transfer of text and optionally audio between users in two locations. Audio may be transmitted alternating with text or simultaneously with text (source: [ITU-T F.703]).
+- 3.297 throughput:** A parameter describing service speed. The number of data bits successfully transferred in one direction between specified reference points per unit time (source: [ITU-T I.113]).
+
+- 3.298 toolkit applet:** An application on the UICC that generates proactive commands to the ME.
+- 3.299 total conversation:** An audiovisual conversation service providing bidirectional symmetric real-time transfer of motion video, text and voice between users in two or more locations (source: [ITU-T F.703]).
+- 3.300 total power dynamic range:** The difference between the maximum and the minimum total transmit output power for a specified reference condition (TS 25.104).
+- 3.301 traffic channel:** A logical channel, which carries user information.
+- 3.302 transit delay:** A parameter describing service speed. The time difference between the instant at which the first bit of a protocol data unit (PDU) crosses one designated boundary (reference point), and the instant at which the last bit of the PDU crosses a second designated boundary (source: [ITU-T I.113]).
+- 3.303 transmission time interval:** The inter-arrival time of transport block sets, i.e., the time it shall take to transmit a transport block set.
+- 3.304 transmitter antenna gain (dBi):** The maximum gain of the transmitter antenna in the horizontal plane (specified as dB relative to an isotropic radiator).
+- 3.305 transport block:** The basic data unit exchanged between L1 and MAC. An equivalent term for transport block is "MAC PDU".
+- 3.306 transport block set:** A set of transport blocks that is exchanged between L1 and MAC at the same time instance using the same transport channel. An equivalent term for transport block set is "MAC PDU Set".
+- 3.307 transport block set size:** The number of bits in a transport block set.
+- 3.308 transport block size:** The size (number of bits) of a transport block.
+- 3.309 transport channel:** The channels offered by the physical layer to Layer 2 for data transport between peer L1 entities are denoted as transport channels. Different types of transport channels are defined by how and with which characteristics data is transferred on the physical layer, e.g., whether using dedicated or common physical channels.
+- 3.310 transport format:** A format offered by L1 to MAC for the delivery of a transport block set during a transmission time interval on a transport channel. The transport format constitutes of two parts – one dynamic part and one semi-static part.
+- 3.311 transport format combination:** The combination of currently valid transport formats on all transport channels of an UE, i.e., containing one transport format from each transport channel.
+- 3.312 transport format combination set:** A set of transport format combinations to be used by an UE.
+- 3.313 transport format combination indicator (TFCI):** A representation of the current transport format combination.
+- 3.314 transport format identification (TFI in UTRAN, TFIN in GERAN):** A label for a specific transport format within a transport format set.
+- 3.315 transport format set:** A set of transport formats. For example, a variable rate DCH has a transport format set (one transport format for each rate), whereas a fixed rate DCH has a single transport format.
+
+**3.316 UE service capabilities:** Capabilities that can be used either singly or in combination to deliver services to the user. The characteristic of UE service capabilities is that their logical function can be defined in a way that is independent of the implementation of the 3GPP System (although all UE service capabilities are of course constrained by the implementation of the 3GPP System). Examples: a data bearer of 144 kbit/s; a high-quality speech teleservice; an IP teleservice; a capability to forward a speech call.
+
+**3.317 universal IC card (UICC):** A physically secure device, an IC card (or 'smart card'), that can be inserted and removed from the terminal equipment. It may contain one or more applications. One of the applications may be a USIM.
+
+**3.318 universal subscriber identity module (USIM):** An application residing on the UICC used for accessing services provided by mobile networks, which the application is able to register on with the appropriate security.
+
+**3.319 uplink:** A unidirectional radio link for the transmission of signals from a UE to a base station, from a mobile station to a mobile base station or from a mobile base station to a base station.
+
+**3.320 URA updating:** A family of procedures that updates the UTRAN registration area of a UE when a RRC connection exists and the position of the UE is known on URA level in the UTRAN.
+
+**3.321 user:** An entity, not part of the 3G System, which uses 3G System services. Example: a person using a 3G System mobile station as a portable telephone.
+
+**3.322 user access or user network access:** The means by which a user is connected to a telecommunication network in order to use the services and/or facilities of that network (source: [ITU-T I.112]).
+
+**3.323 user equipment:** A device allowing a user access to network services. For the purpose of 3G specifications, the interface between the UE and the network is the radio interface. A user equipment can be subdivided into a number of domains, the domains being separated by reference points. Currently defined domains are the USIM and ME Domains. The ME Domain can further be subdivided into several components showing the connectivity between multiple functional groups. These groups can be implemented in one or more hardware devices. An example of such a connectivity is the TE-MT interface. Further, an occurrence of a user equipment is an MS for GSM.
+
+**3.324 UTRA radio access mode:** The selected UTRA radio access mode, i.e., UTRA-FDD; UTRA-TDD.
+
+**3.325 UTRA-TDD:** Time division duplex UTRA radio access mode.
+
+**3.326 UTRA-WTDD:** Time division duplex UTRA access mode 3.84 Mcps option.
+
+**3.327 UTRAN access point:** A conceptual point within the UTRAN performing radio transmission and reception. A UTRAN access point is associated with one specific cell, i.e., there exists one UTRAN access point for each cell. It is the UTRAN-side endpoint of a radio link.
+
+**3.328 UTRAN registration area:** An area covered by a number of cells. The URA is only internally known in the UTRAN.
+
+**3.329 UTRAN radio network temporary identifier:** The U-RNTI is a unique UE identifier that consists of two parts, an SRNC identifier and a C-RNTI. U-RNTI is allocated to an UE having a RRC connection. It identifies the UE within UTRAN and is used as an UE identifier in cell update, URA update, RRC connection reestablishment and (UTRAN originated) paging messages and associated responses on the radio interface.
+
+**3.330 user profile:** The set of information necessary to provide a user with a consistent, personalized service environment, irrespective of the user's location or the terminal used (within the limitations of the terminal and the serving network).
+
+- 3.331 Uu:** The Radio interface between UTRAN and the user equipment.
+- 3.332 value-added service provider:** Provides services other than basic telecommunications service for which additional charges may be incurred.
+- 3.333 variable bit rate service:** A type of telecommunication service characterized by a service bit rate specified by statistically expressed parameters which allow the bit rate to vary within defined limits (source: [ITU-T I.113]).
+- 3.334 virtual home environment:** A concept for personal service environment portability across network boundaries and between terminals.
+- 3.335 virtual machine:** A software program that simulates a hypothetical computer central processing unit. The programs executed by a virtual machine are represented as byte codes, which are primitive operations for this hypothetical computer.
+- 3.336 visited PLMN of home country:** This is a PLMN, different from the home PLMN, where the MCC part of the PLMN identity is the same as the MCC of the IMSI.
+- 3.337 wide TDD (WTDD):** The 3.84 Mcps chip rate UTRA-TDD option.
+- 3.338 WLAN user equipment (WLAN UE):** A UE (equipped with UICC card including (U)SIM) utilized by a subscriber capable of accessing a WLAN network. A WLAN UE may include entities whose configuration, operation and software environment are not under the exclusive control of the 3GPP system operator, such as a laptop computer or PDA with a WLAN card, UICC card reader and suitable software applications.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|--------|-------------------------------------------------------------|
+| 2G | Second Generation |
+| 3G | Third Generation |
+| 3GMS | Third Generation Mobile Communication System |
+| 3GPP | Third Generation Partnership Project |
+| AAL 2 | ATM Adaptation Layer type 2 |
+| AC | Access Class, Access Condition, Application Context |
+| ACC | Automatic Congestion Control |
+| ACELP | Algebraic Code-Excited Linear Prediction |
+| AES | Advanced Encryption Standard |
+| A-GNSS | Advanced Global Navigation Satellite System |
+| AID | Application Identifier |
+| AKA | Authentication and Key Agreement |
+| AKI | Asymmetric Key Index |
+| AMF | Authentication Management Field |
+| AMR | Adaptive Multi Rate (also appears as "Adaptive Multi-Rate") |
+| AMR-WB | Adaptive Multi Rate WideBand |
+| ANP | Access Network Provider |
+| AoC | Advice of Charge |
+
+| | |
+|------------|----------------------------------------------------------------------------------------------------|
+| AoCC | Advice of Charge Charging (also appears as "Advice of Charge (Charging)") |
+| AoCI | Advice of Charge Information (also appears as "Advice of Charge (Information)") |
+| API | Application Programming Interface |
+| AS | Application Server |
+| ASE | Application Service Element |
+| ASQ | Automatic Repeat ReQuest |
+| AT-command | ATtention Command |
+| ATM | Asynchronous Transfer Mode |
+| AuC | Authentication Centre |
+| BAIC | Barring of All Incoming Calls supplementary service (also appears without "supplementary service") |
+| BAOC | Barring of All Outgoing Calls supplementary service (also appears without "supplementary service") |
+| BER | Bit Error Rate; Basic Encoding Rules (of ASN.1) |
+| BGCF | Breakout Gateway Control Function |
+| BICC | Bearer Independent Call Control |
+| BIC-Roam | Barring of Incoming Calls when Roaming outside the home PLMN country |
+| BOIC | Barring of Outgoing International Calls |
+| BOIC-exHC | Barring of Outgoing International Calls except those directed to the Home PLMN Country |
+| BS | Base Station |
+| BS | Bearer Service |
+| BSC | Base Station Controller |
+| BSS | Base Station Subsystem |
+| BSSMAP | Base Station Subsystem Management Application Part |
+| BTS | Base Transceiver Station |
+| CAI | Charge Advise Information |
+| CAMEL | Customized Applications for Mobile network Enhanced Logic |
+| CAP | CAMEL Application Part |
+| CB | Call Barring |
+| CBC | Cell Broadcast Centre |
+| CBS | Cell Broadcast Service |
+| CC | Call Control |
+| CCBS | Completion of Calls to Busy Subscriber (also appears as "Call Completion to Busy Subscriber") |
+| CD | Call Deflection |
+| CDR | Charging Data Record |
+| CF | Call Forwarding |
+
+| | |
+|--------|-------------------------------------------------------------------------------------------------------------------------|
+| CFB | Call Forwarding on mobile subscriber Busy |
+| CFNRc | Call Forwarding on mobile subscriber Not Reachable supplementary service (also appears without "supplementary service") |
+| CFNRy | Call Forwarding on No Reply supplementary service (also appears without "supplementary service") |
+| CFU | Call Forwarding Unconditional |
+| CGF | Charging Gateway Function |
+| CLI | Calling Line Identity |
+| CLIP | Calling Line Identification Presentation |
+| CLIR | Calling Line Identification Restriction |
+| CM | Configuration Management |
+| CMIP | Common Management Information Protocol |
+| CN | Core Network |
+| CNAP | Calling Name Presentation |
+| COLP | Connected Line identification Presentation |
+| COLR | Connected Line identification Restriction |
+| CORBA | Common Object Request Broker Architecture |
+| CS | Circuit Switched |
+| CSCF | Call Session Control Function |
+| CSE | CAMEL Service Environment |
+| CSICS | Circuit Switched IMS Combinational Service |
+| CS-MGW | Circuit Switched Media GateWay |
+| CTM | Cellular Text telephone Modem |
+| CUG | Closed User Group |
+| CW | Call Waiting |
+| DCE | Data Circuit-terminating Equipment |
+| DTE | Data Terminal Equipment |
+| DTMF | Dual Tone Multiple Frequency |
+| DTX | Discontinuous Transmission |
+| ECT | Explicit Call Transfer supplementary service |
+| EDGE | Enhanced Data rates for GSM Evolution |
+| EF | Elementary File |
+| EFR | Enhanced Full Rate |
+| EGPRS | Enhanced GPRS |
+| EIR | Equipment Identity Register |
+| EM | Element Manager |
+
+| | |
+|---------|-----------------------------------------------------------------------------------------------------------------------------|
+| eMLPP | Enhanced Multi-Level Precedence and Pre-emption (also appears as "enhanced Multi-Level Precedence and Pre-emption service") |
+| EP | Elementary Procedure |
+| EP | Entry Point |
+| FDD | Frequency Division Duplex |
+| FM | Fault Management |
+| GAD | Geographical Area Description |
+| GBS | General Bearer Services |
+| GERAN | GSM/EDGE Radio Access Network |
+| GGSN | Gateway GPRS Support Node |
+| GLR | Gateway Location Register |
+| GMLC | Gateway Mobile Location Centre |
+| GMSC | Gateway Mobile Switching Centre |
+| GPRS | General Packet Radio Service |
+| gprsSSF | GPRS Service Switching Function |
+| GPS | Global Positioning System |
+| GSM | Global System for Mobile communications |
+| GSM-EFR | GSM Enhanced Full Rate speech Codec |
+| gsmSCF | GSM Service Control Function |
+| gsmSRF | GSM Specialized Resource Function |
+| gsmSSF | GSM Service Switching Function |
+| GSN | GPRS Support Nodes |
+| GT | Global Title |
+| GTP | GPRS Tunnelling Protocol |
+| GTT | Global Text Telephony |
+| HDLC | High Level Data Link Control |
+| HE | Home Environment |
+| HLR | Home Location Register |
+| HPLMN | Home Public Land Mobile Network |
+| HSCSD | High Speed Circuit Switched Data |
+| IC | Integrated Circuit (also appears as "Integrated Circuits") |
+| ICC | Integrated Circuit Card |
+| IDL | Interface Definition Language |
+| IM | IP Multimedia |
+| IMEI | International Mobile Equipment Identity |
+| IM-GSN | Intermediate GPRS Serving Node |
+| IM-MGW | Intermediate Media GateWay |
+
+| | |
+|--------|----------------------------------------------------------------------------------------------------|
+| IM-MSC | Intermediate Mobile-services Switching Centre |
+| IMS | IP Multimedia Subsystem |
+| IMSI | International Mobile Subscriber Identity (also appears as "International Mobile Station Identity") |
+| IN | Intelligent Network |
+| INAP | Intelligent Network Application Protocol |
+| IP | Internet Protocol |
+| IP-CAN | IP-Connectivity Access Network |
+| IPDL | Idle Period Downlink |
+| IPLMN | Interrogating PLMN |
+| IrDA | Infrared Data Association |
+| IRP | Integration Reference Point |
+| IS | Information Service |
+| ISDN | Integrated Services Digital Network |
+| ISUP | ISDN User Part |
+| Itf-N | Interface N |
+| IWF | InterWorking Function |
+| K | Subscriber key |
+| LAN | Local Area Network |
+| LCS | Location Services |
+| LMSI | Local Mobile Station Identity |
+| LMU | Location Measurement Unit |
+| LR | Location Registration |
+| MAC | Media Access Control |
+| MAC | Message Authentication Code |
+| MAP | Mobile Application Part |
+| MC | Multicall |
+| ME | Mobile Equipment |
+| MExE | Mobile station application Execution Environment, aka Mobile Execution Environment |
+| MGC | Media Gateway Controller |
+| MGCF | Media Gateway Control Function |
+| MGW | Media GateWay |
+| MIM | Management Information Model |
+| MIME | Multipurpose Internet Mail Extensions |
+| MLC | Mobile Location Centre |
+| MM | Mobility Management |
+
+| | |
+|---------|-----------------------------------------------------------------------------------------------|
+| MMI | Man-Machine Interface |
+| MMS | Multimedia Messaging Service |
+| MNP | Mobile Number Portability |
+| MO | Mobile Originated |
+| MO-LR | Mobile Originating Location Request |
+| MPTY | MultiParty |
+| MR | Multi Rate |
+| MRFC | Multimedia Resource Function Controller |
+| MRFP | Multimedia Resource Function Processor |
+| MS | Mobile Station |
+| MSC | Mobile Switching Centre (also appears as "Mobile-services Switching Centre") |
+| MSISDN | Mobile Subscriber ISDN number (also appears as "Mobile Station International ISDN Number(s)") |
+| MSP | Multiple Subscriber Profile |
+| MSRN | Mobile Station Roaming Number |
+| MT | Mobile Terminal |
+| MT | Mobile Termination |
+| MTP | Message Transfer Part |
+| NE | Network Element |
+| NITZ | Network Identity and Time Zone |
+| NM | Network Manager |
+| NRM | Network Resource Model |
+| NSS | Network Subsystem |
+| NW | Network |
+| OACSU | Off-Air Call Set-Up |
+| ODB | Operator Determined Barring |
+| OoBTC | Out of Band Transcoder Control |
+| OP | OPerator |
+| OS | Operations System |
+| OSA | Open Service Architecture |
+| OSI | Open Systems Interconnection |
+| OTDOA | Observed Time Difference Of Arrival |
+| PBX | Private Branch eXchange |
+| PCM | Pulse Code Modulation |
+| PDC | Personal Digital Communication |
+| PDC-EFR | ARIB PDC-EFR 6.7 kbit/s speech Codec |
+| PDN | Public Data Network |
+
+| | |
+|---------|-------------------------------------------------------------------------------------|
+| PDP | Packet Data Protocol |
+| PDU | Protocol Data Unit |
+| PI | Presentation Indicator |
+| PIX | Proprietary application Identifier eXtension |
+| PLMN | Public Land Mobile Network |
+| PM | Performance Management |
+| PNM | Personal Network Management |
+| PP | Point-to-Point |
+| PS | Packet Switched |
+| PSAP | Public Service Access Point |
+| PSE | Personal Service Environment |
+| PSS | Packet-switched Streaming Service |
+| PSTN | Public Switched Telephone Network |
+| QoS | Quality of Service |
+| RANAP | Radio Access Network Application Part |
+| RAND | RANDom number (used for authentication) |
+| RID | Registered application provider Identifier |
+| RLC/MAC | Radio Link Control/Media Access Control |
+| RLP | Radio Link Protocol |
+| RNC | Radio Network Controller |
+| RNS | Radio Network Subsystem (also appears as "Radio Network System") |
+| RR | Radio Resources |
+| RTP | Real Time Protocol |
+| SAGE | Security Algorithms Group of Experts |
+| SAT | SIM Application Toolkit |
+| SC | Service Centre (used for SMS) |
+| SCCP | Signalling Connection Control Part |
+| SCF | Service Control Function (IN context), Service Capability Feature (VHE/OSA context) |
+| SCIM | Service Capability Interaction Manager |
+| SCR | Source Controlled Rate |
+| SCTP | Stream Control Transmission Protocol |
+| SDL | Specification Description Language |
+| SGSN | Serving GPRS Support Node |
+| SGW | Signalling GateWay |
+| SID | Silence Descriptor |
+| SIM | GSM Subscriber Identity Module |
+
+| | |
+|----------|--------------------------------------------------------------------------------------------|
+| SIWFS | Shared InterWorking Function Server |
+| SLF | Subscription Locator Function |
+| SM | Session Management |
+| SM | Short Message |
+| SMC | Short Message Control |
+| SMIL | Synchronized Multimedia Integration Language |
+| SMLC | Serving Mobile Location Centre |
+| SM-RL | Short Message Relay Layer |
+| SMS | Short Message Service |
+| SMTP | Simple Mail Transfer Protocol |
+| SOR | Support of Optimal Routing |
+| SP | Service Provider |
+| SP | Switching Point |
+| SQN | Sequence Number |
+| SRNC | Serving Radio Network Controller |
+| SRNS | Serving RNS |
+| SS | Solution Set |
+| SS | Supplementary Service |
+| SS7 | Signalling System No. 7 |
+| SSAP | Supplementary Service Application Part |
+| SSF | Service Switching Function |
+| TA | Terminal Adaptation |
+| TA | Terminal Adapter |
+| TAF | Terminal Adaptation Function |
+| T-BCSM | Terminating Basic Call State Model |
+| TCAP | Transaction Capabilities |
+| TCH/F | A full rate Traffic CHannel |
+| TDD | Time Division Duplex |
+| TDMA | Time Division Multiple Access |
+| TDMA_EFR | TIA IS-641 Enhanced speech Codec |
+| TDMA_USI | TIA TDMA-US1 (12.2 kbit/s Codec, similar to GSM-EFR) |
+| TE | Terminal Equipment |
+| TFO | Tandem Free Operation |
+| TMSI | Temporary Mobile Subscriber Identity (also appears as "Temporary Mobile Station Identity") |
+| TrFO | Transcoder Free Operation |
+| TUP | Telephone User Part (SS7) |
+
+| | |
+|----------|----------------------------------------------------------------|
+| UDP | User Datagram Protocol |
+| UE | User Equipment |
+| UI | User Interaction |
+| UI | User Interface |
+| UICC | Universal IC Card |
+| UIM | User Identity Module |
+| UMTS | Universal Mobile Telecommunications System |
+| USAT | USIM Application Toolkit |
+| USIM | Universal Subscriber Identity Module |
+| USSD | Unstructured Supplementary Service Data |
+| UTRA | Universal Terrestrial Radio Access |
+| UTRA-FDD | Universal Terrestrial Radio Access – Frequency Division Duplex |
+| UTRAN | Universal Terrestrial Radio Access Network |
+| UTRA-TDD | Universal Terrestrial Radio Access – Time Division Duplex |
+| UUS | User-to-User Signalling |
+| VAD | Voice Activity Detector |
+| VBS | Voice Broadcast Service |
+| VGCS | Voice Group Call Service |
+| VHE | Virtual Home Environment |
+| VLR | Visitor Location Register |
+| VMSC | Visited Mobile Switching Centre |
+| VPLMN | Visited Public Land Mobile Network |
+| WAP | Wireless Application Protocol |
+| XML | eXtensible Markup Language |
+
+# 5 Introduction
+
+The core network for this IMT-2000 Family Member, referred to as "3GPP Release 7", is based on an evolved core network from the 3rd generation releases 1999 through to Release 6. The Technical Specifications have been developed in a partnership project and transposed to the involved Standards Development Organizations (SDOs). The system will support different applications ranging from narrow-band to wideband communications capability with integrated personal and terminal mobility to meet the user and service requirements.
+
+Release 7 is the fifth release of this 3rd generation of mobile communications technology. The core network interfaces identified in this Recommendation constitute a complete mobile core network system for this IMT-2000 Family Member. The core network of 3GPP Release 7 supports both 2nd and 3rd generation radio access networks as options.
+
+Refer to clause 10.2.40, Service principles, for more information.
+
+The descriptions of the Technical Specifications listed in clause 10 are for informative purposes only. Normative information is in the table for the respective specification.
+
+3GPP Release 7 introduces a range of new features under control of the 3GPP Workplan. At the September 2007 plenary of 3GPP, the following feature set was approved:
+
+- IMS-related new features:
+ - Identification of communication services in IMS
+ - Supporting globally routable user agent URIs in IMS
+ - IMS support of conferencing and messaging group management
+ - Multimedia telephony service for IMS
+ - Performance characterization of VoIMS over HSDPA/EUL channels
+- Location-related new features:
+ - Advanced global navigation satellite system (A-GNSS) concept
+ - A-GPS minimum performance
+ - UE positioning Rel-7
+ - Velocity
+- Combinational services
+- System enhancements for fixed broadband access to IMS
+- Access class barring and overload protection
+- USSD message delivery and transfer to USIM
+- Protocol-related new features:
+ - IMS Stage 3 IETF Protocol alignment
+ - DIAMETER on the GGSN Gi interface
+ - DIAMETER on the PDG Wi interface
+- Mp (MRFC-MRFP) interface
+- Support of SMS over generic 3GPP IP access
+- Dynamic and interactive multimedia scenes
+- Security-related new features:
+ - Liberty Alliance and 3GPP Security Interworking
+ - Trust requirements for open platforms in 3GPP
+ - Development of UEA2 and UIA2
+ - Lawful interception in the 3GPP Rel-7 architecture
+ - Access security enhancements
+- One tunnel solution for optimization of packet data traffic
+- End-to-end multimedia services performance metrics
+- ISIM API for Java Card
+- Network composition
+- Key establishment between a UICC and a terminal
+- Selective disabling of UE capabilities
+- Personal network management (PNM)
+- CSI terminating session handling
+- Interoperability between VGCS/VBS and A/Gb flexibility
+
+# 6 Basic architecture for the UMTS IMT-2000 Family Member
+
+This text is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 5.1.
+
+The basic configuration of a public land mobile network (PLMN) supporting GPRS and the interconnection to the PSTN/ISDN and PDN is presented in Figure 6-1. This configuration presents signalling and user traffic interfaces which can be found in a PLMN. Implementations may be different: some particular functions may be gathered in the same equipment and then some interfaces may become internal interfaces.
+
+In the basic configuration presented in Figure 6-1, all the functions are considered implemented in different equipments. Therefore, all the interfaces within PLMN are external. This Recommendation will only describe the internal interfaces in the core network (CN) and the external interfaces to and from CN. Interfaces Iu, Iur and Iub are defined in the 25.7xx-series of Technical Specifications, which are outside the scope of this Recommendation. Interfaces A and Abis are defined in the 48-series of Technical Specifications, which are also outside the scope of this Recommendation. Interfaces C, D, E, F and G need the support of the mobile application part of Signalling System No. 7 to exchange the data necessary to provide the mobile service. No protocols for the H-interface and for the I-interface are standardized. All the GPRS-specific interfaces (G-series) are defined in the 23-series and 24-series of Technical Specifications. Interfaces Mc, Nb, and Nc are defined in 23.705 and in the 29-series of Technical Specifications.
+
+From this configuration, all the possible PLMN organizations can be deduced. In the case when some functions are contained in the same equipment, the relevant interfaces become internal to that equipment.
+
+
+
+The diagram illustrates the basic configuration of a PLMN supporting CS and PS services. It shows the following components and interfaces:
+
+- CN (Core Network):** Includes PSTN, CS-MGW, GMSC server, HSS (HLR, AuC), PDF, CRF, GGSN, SGSN, VLR, and MSC server. Interfaces include PSTN, Mc, Nb, G, E, Nc, D, F, Gs, Gf, Gr, Gn, Gx, Go, Go\*, Gi, Gp, Rx, Gq.
+- BSS (Base Station System):** Includes BSC and BTS. Interfaces include A, IuCS, IuPS, Gb, Abis, Um.
+- RNS (Radio Network System):** Includes RNC and Node B (Cell). Interfaces include Iur, Iub, IuCS, IuPS.
+- MS (Mobile Station):** Includes ME, SIM, and USIM. Interfaces include Um, Uu, SIM-ME i/f, Cu.
+
+Legend:
+
+- Interfaces supporting user traffic
+- - - Interfaces supporting signalling
+
+Q.1741.5(08)\_F6-1
+
+Figure 6-1: Basic configuration of a PLMN supporting CS and PS services and interfaces. The diagram shows the interconnections between various network elements including CN (Core Network), BSS (Base Station System), RNS (Radio Network System), and MS (Mobile Station).
+
+NOTE 1 – The figure shows direct interconnections between the entities. The actual links may be provided by an underlying network (e.g., SS7 or IP): this needs further studies.
+
+NOTE 2 – When the MSC and the SGSN are integrated in a single physical entity, this entity is called UMTS MSC (UMSC).
+
+NOTE 3 – A (G)MSC server and associated CS-MGW can be implemented as a single node: the (G)MSC.
+
+NOTE 4 – The Gn interface (between two SGSNs) is also part of the reference architecture, but is not shown for layout purposes only.
+
+NOTE 5 – The Go interface marked with a '\*' has been included to this figure for backwards compatibility only, in order to support connecting to Release-5 IM CN subsystem configurations.
+
+**Figure 6-1 – Basic configuration of a PLMN supporting CS and PS services and interfaces**
+
+The following text is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 5.2.1.
+
+The configuration of LCS entities for GSM GERAN is presented in Figure 6-2. In the figure, all the functions are considered implemented in different logical nodes. If two logical nodes are implemented in the same physical equipment, the relevant interfaces may become internal to that equipment.
+
+
+
+Figure 6-2: Configuration of LCS entities for a GERAN PLMN. The diagram shows a GERAN BSS containing a BTS (Type B LMU) and a BSC. The BSC is connected to a 3G MSC/MSC server (Iu-cs), a 3G SGSN (Iu-ps), a 2G MSC (A), and a 2G SGSN (Gb). The BSC also contains an SMLC and a CBC. The BSS is connected to an MS via Um interfaces. The BSC is also connected to an external SMLC and CBC via Lb and Lp interfaces. The 3G MSC/MSC server, 3G SGSN, 2G MSC, and 2G SGSN are connected to a GMLC via Lg interfaces. The GMLC is connected to an HSS (Lh) and an External LCS client (Le). The External LCS client is connected to an OSA SCS (OSA API) and a gsmSCF (Proprietary). The OSA SCS is connected to the gsmSCF (Proprietary). The gsmSCF is connected to the External LCS client (Proprietary).
+
+a) HSS includes both 2G-HLR and 3G-HLR functionality.
+
+b) As one alternative, the LCS client may get location information directly from GMLC, which may contain OSA mobility SCS with support for the OSA user location interfaces.
+
+**Figure 6-2 – Configuration of LCS entities for a GERAN PLMN**
+
+The following text is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 5.2.2.
+
+The basic configuration of UTRAN LCS is presented in Figure 6-3. The SMLC functionality is integrated in SRNC or, in case a stand-alone SMLC (SAS) entity is present, split between SRNC and SMLC.
+
+
+
+Figure 6-3: Configuration of LCS entities for a UTRAN PLMN. The diagram shows a UTRAN RNS containing a Stand-alone SMLC (SAS), an SRNC (SMLC functionality), a Node B (Associated LMU), and a Cell. The RNS is connected to an RNC via Iur. The RNS is also connected to a 3G MSC/MSC server (Iu-cs) and a 3G SGSN (Iu-ps). The RNS is also connected to a UE via Uu interfaces. The 3G MSC/MSC server, 3G SGSN, and Stand-alone LMU are connected to a GMLC via Lg interfaces. The GMLC is connected to an HSS (Lh) and an External LCS client (Le). The External LCS client is connected to an OSA SCS (OSA API) and a gsmSCF (Proprietary). The OSA SCS is connected to the gsmSCF (Proprietary). The gsmSCF is connected to the External LCS client (Proprietary).
+
+a) The HSS includes both 2G-HLR and 3G-HLR functionality.
+
+b) As one alternative, the LCS client may get location information directly from GMLC, which may contain OSA mobility SCS with support for the OSA user location interfaces.
+
+c) The SMLC may be either a stand-alone network element (SAS) or an internal function of the RNC.
+
+**Figure 6-3 – Configuration of LCS entities for a UTRAN PLMN**
+
+The following text is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clauses 4a.4 and 5.3.
+
+Figure 6-4 shows the interconnection of the CAMEL-specific entities with the rest of the network. Only the interfaces specifically involved in CAMEL provisioning are shown, i.e., all the GMSC, MSC, SGSN and HLR interfaces depicted in Figure 6-4 are still supported by these entities even if not shown.
+
+NOTE 1 – Most CAMEL-specific interfaces have no particular name. They are designated by the name of the two entities they link together, e.g., "the gsmSSF-gsmSCF interfaces".
+
+
+
+Figure 6-4: Configuration of CAMEL entities. This diagram shows the network architecture for CAMEL. At the top, a GMSC is connected to a gsmSSF. The gsmSSF is connected to a gsmSCF via a dashed line (signalling). The gsmSCF is connected to an HLR via a dashed line (signalling). The gsmSCF is also connected to a gsmSRF via a bold line (user data). The gsmSRF is connected to an MSC via a bold line (user data). The MSC is connected to a gsmSSF and a VLR. The gsmSSF is connected to the MSC via a bold line (user data). The VLR is connected to the MSC via a bold line (user data). The HLR is connected to the gsmSCF via a dashed line (signalling). The HLR is also connected to a gprsSSF via a dashed line (signalling). The gprsSSF is connected to an SGSN via a bold line (user data). The SGSN is connected to the gprsSSF via a bold line (user data). The diagram is labeled Q.1741.5(08)\_F6-4.
+
+**Figure 6-4 – Configuration of CAMEL entities**
+
+The bold lines are used for interfaces supporting user data only; the dashed lines are used for interfaces supporting signalling only.
+
+The following text is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clauses 4a.5 and 5.4.
+
+The cell broadcast service (CBS) is a teleservice, which enables an Information Provider to submit short messages for broadcasting to a specified area within the PLMN.
+
+
+
+Figure 6-5: Configuration of a PLMN supporting Cell Broadcast Service entities. This diagram shows the network architecture for CBS. At the top, a CN (Core Network) contains a CBC (Cell Broadcast Center). The CBC is connected to a BSS (Base Station System) via a dashed line (signalling) labeled (Note). The CBC is also connected to an RNS (Radio Network Subsystem) via a dashed line (signalling) labeled IuBC. The BSS contains a BSC (Base Station Controller) which is connected to two BTS (Base Transceiver Station) units via Abis interfaces. The RNS contains an RNC (Radio Network Controller) which is connected to two Node B units via Iub interfaces. One of the Node B units is connected to a UE (User Equipment). The diagram is labeled Q.1741.5(08)\_F6-5.
+
+NOTE – Interface outside the scope of 3GPP/GSM.
+
+**Figure 6-5 – Configuration of a PLMN supporting Cell Broadcast Service entities**
+
+The following text is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 5.5.
+
+The configuration of IM CN subsystem entities is presented in Figure 6-6. In the figure, all the functions are considered implemented in different logical nodes. If two logical nodes are implemented in the same physical equipment, the relevant interfaces may become internal to that equipment.
+
+Only the interfaces specifically linked to the IM subsystem are shown, i.e., all the SGSN, GGSN and HSS interfaces depicted in Figure 6-6 are still supported by these entities even if not shown.
+
+
+
+Figure 6-6: Configuration of IM subsystem entities. This diagram shows the interconnections between various network elements. On the left, 'IP multimedia networks' are connected to an 'IMS-MGW'. The 'IMS-MGW' is connected to a 'MRFP' (Media Resource Function) via an 'Mb' interface. The 'MRFP' is connected to an 'MRFC' (Media Resource Controller) via an 'Mp' interface. The 'MRFC' is connected to a 'CSCF' (Call Session Control Function) via an 'Mg' interface. The 'CSCF' is connected to an 'HSS' (Home Subscriber Server) via a 'Cx' interface, to an 'SLF' (Subscription Locator Function) via a 'Dx' interface, and to a 'P-CSCF' (PDN Connection Network) via a 'Mw' interface. The 'P-CSCF' is connected to a 'UE' (User Equipment) via a 'Gm' interface. The 'CSCF' is also connected to a 'BGCF' (Breakout Gateway Control Function) via a 'Mk' interface. The 'BGCF' is connected to a 'PSTN' (Packet Switched Network) via a 'PSTN' interface. The 'PSTN' is connected to an 'IMS-MGW' via an 'Mb' interface. The 'IMS-MGW' is also connected to a 'Legacy mobile signalling networks' via a 'C, D, Ge, Gr' interface. The 'IM subsystem' is indicated by a dashed box containing the 'IMS-MGW', 'MRFP', 'MRFC', 'CSCF', 'HSS', 'SLF', 'P-CSCF', and 'UE'.
+
+Figure 6-6 – Configuration of IM subsystem entities
+
+Figure 6-7 depicts an overall view of the functional architecture for services.
+
+
+
+Figure 6-7: Functional architecture for the provision of service in the IMS. This diagram shows the functional architecture for services. At the top, a 'SIP application server' contains 'AS' (Application Server) and 'SCIM' (Service Capability Interaction Manager) components. It is connected to an 'HSS' via an 'Sh' interface. The 'HSS' is connected to an 'S-CSCF' (Serving CSCF) via a 'Cx' interface. The 'S-CSCF' is connected to an 'OSA service capability server (SCS)' via an 'ISC' interface. The 'SCS' is connected to an 'OSA application server' via an 'OSA API' interface. The 'S-CSCF' is also connected to an 'IM-SSF' (IM Service Switching Function) via a 'Si' interface. The 'IM-SSF' is connected to a 'Camel service environment' via a 'CAP' interface. The 'HSS' is also connected to the 'Camel service environment' via a 'MAP' interface.
+
+Figure 6-7 – Functional architecture for the provision of service in the IMS
+
+The purpose of the IM SSF is to host the CAMEL network features (i.e., trigger detection points, CAMEL service switching finite state machine, etc.) and to interwork with CAP.
+
+The IM SSF and the CAP interface support legacy services only.
+
+The application server may contain "service capability interaction manager" (SCIM) functionality and other application servers. The SCIM functionality is an application which performs the role of interaction management. The internal components are represented by the "dotted boxes" inside the SIP application server. The internal structure of the application server is outside the standards. The Sh interface shall have sufficient functionality to enable this scenario.
+
+Figure 6-7a depicts an overall view of the functional architecture for enabling the management of the user's service related information via the Ut interface.
+
+
+
+Figure 6-7a: Functional architecture for the management of the user's service related information. The diagram shows a SIP application server connected to a UE via the Ut interface, to an HSS via the Sh interface, and to an S-CSCF via the ISC interface. The HSS is connected to the S-CSCF via the Cx interface. The SIP application server, HSS, and S-CSCF are represented by dotted boxes. The reference point Q.1741.5(08)\_F6-7a is indicated.
+
+**Figure 6-7a – Functional architecture for the management of the user's service related information**
+
+The following text is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 5.6.
+
+The signalling gateway function is used to interconnect different signalling networks, i.e., SCTP/IP-based signalling networks and SS7 signalling networks. The application layer (e.g., ISUP, BICC, MAP or CAP) is not affected. The signalling gateway function may be implemented as a stand-alone entity or inside another entity.
+
+
+
+Figure 6-8: Configuration of a Signalling Gateway function. The diagram shows an IP signalling transport NW connected to an SGW via the SCTP/IP interface, and the SGW connected to an SS7 signalling transport NW via the MTP interface. The reference point Q.1741.5(08)\_F6-8 is indicated.
+
+**Figure 6-8 – Configuration of a Signalling Gateway function**
+
+NOTE 2 – SS7 application transport and SCTP/IP adaptation protocols are not shown.
+
+The following text is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 5.7 "Configuration of 3GPP/WLAN Interworking".
+
+The configuration of the 3GPP/WLAN interworking function is presented in Figure 6-8a. The figure shows all network entities and reference points for the roaming scenario when a WLAN UE accesses PS-based services in the home network. PS-based services in the visited network are accessed via a packet data gateway in the visited 3GPP network. Reference point Ww between WLAN UE and WLAN is outside the scope of 3GPP and is only shown for completeness.
+
+
+
+```
+
+graph LR
+ UE[WLAN UE] -- Ww --> WAN[WLAN access network]
+ WAN -- Wn --> WAG[WAG]
+ WAG -- Wg --> AAA_Proxy[3GPP AAA proxy]
+ AAA_Proxy -- Wd --> AAA_Server[3GPP AAA server]
+ AAA_Server -- Wx --> HSS[HSS]
+ AAA_Server -- D/Gr' --> HLR[HLR]
+ AAA_Server -- Wo --> OCS[OCS]
+ AAA_Server -- Wf --> CGW_CCF1[CGW/CCF]
+ AAA_Server -- Wm --> PDG[Packet data gateway]
+ PDG -- Wi --> Intranet[Intranet/Internet]
+ PDG -- Wu --> UE
+ PDG -- Wp --> WAG
+ AAA_Proxy -- Wa --> Intranet
+ AAA_Proxy -- Wf --> CGW_CCF2[CGW/CCF]
+
+```
+
+Figure 6-8a: Configuration of a 3GPP/WLAN interworking function. The diagram shows a WLAN UE connected to a WLAN access network, which is connected to a WAG. The WAG is connected to a 3GPP AAA proxy in the 3GPP visited network. The 3GPP AAA proxy is connected to a 3GPP AAA server in the 3GPP home network. The 3GPP AAA server is connected to an HSS, an HLR, and a CGW/CCF. The 3GPP AAA server is also connected to an OCS. The 3GPP AAA server is connected to a Packet data gateway, which is connected to the Intranet/Internet. The Packet data gateway is also connected to the WAG. The Packet data gateway is connected to the 3GPP AAA server. The Packet data gateway is connected to the Intranet/Internet. The Packet data gateway is connected to the WAG. The Packet data gateway is connected to the 3GPP AAA server. The Packet data gateway is connected to the Intranet/Internet.
+
+**Figure 6-8a – Configuration of a 3GPP/WLAN interworking function**
+
+The following text is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 5.8 "Configuration of Presence service".
+
+The reference architecture model, the reference points and the functional entities to support the Presence Service are described in 3G TS 23.141.
+
+The following text is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], Annex A.
+
+Gateway location register (GLR) is an optional functional entity to optimize signalling traffic between PLMNs. This entity handles location management of a roaming subscriber in the visited network without involving HLR. The location register function in the GLR stores subscription information and routing information for both CS services and PS services. This entity can be only located in a visited PLMN.
+
+In the basic configuration with GLR introduction presented in Figure 6-9, all the functions related to GLR introduction are considered implemented in different equipments. Therefore, all the interfaces within PLMN are external. Interfaces GLa, GLb, GLc, GLd, GLf, GLg, GLh, and GLi need the support of the mobile application part of Signalling System No. 7 to exchange the data necessary to provide the mobile service. No protocols for the GLe interface are standardized. GLj and GLk need the support of the GPRS tunnelling protocol control to provide the packet domain services.
+
+
+
+----- Signalling interface
+ — User traffic interface. User traffic includes short message.
+
+Q.1741.5(08)\_F6-9
+
+Diagram showing the configuration of a PLMN and interfaces with GLR. The diagram includes various network entities: SGSN, VLR/MSC, IM-GSN, GLR, IM-MSC, GGSN, HLR, SMS-GMSC, and GMLC. Interfaces are labeled GLk, GLc, GLb, GLh, GLe, GLd, GLj, GLa, GLf, GLg, and GLi. A legend indicates that dashed lines represent signalling interfaces and solid lines represent user traffic interfaces, which include short messages. The entities GGSN, HLR, SMS-GMSC, and GMLC are grouped under 'Other PLMN'.
+
+**Figure 6-9 – Configuration of a PLMN and interfaces with GLR**
+
+# 7 Network entities
+
+## 7.1 Gateway mobile switching centre (GMSC)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4.1.2.2.
+
+The mobile switching centre (MSC), which performs the routing function to the actual location of the mobile station (MS), is called the gateway MSC (GMSC).
+
+If a network delivering a call to the PLMN cannot interrogate the home location register (HLR), the call is routed to an MSC. This MSC will interrogate the appropriate HLR and then route the call to the MSC where the mobile station is located.
+
+The acceptance of an interrogation to an HLR is the decision of the operator.
+
+The choice of which MSCs can act as gateway MSCs is for the operator to decide (i.e., all MSCs or some designated MSCs).
+
+When needed, the GMSC can be implemented in two different entities: the GMSC server, handling only signalling, as defined below, and the CS-MGW, defined below. A GMSC server and a CS-MGW make up the full functionality of a GMSC.
+
+### 7.1.1 Gateway MSC server (GMSC server)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4.1.2.2.1.
+
+The GMSC server mainly comprises the call control and mobility control parts of a GMSC.
+
+## 7.2 Mobile switching centre and visitor location register (MSC/VLR)
+
+### 7.2.1 Mobile switching centre (MSC)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4.1.2.1.
+
+The mobile-services switching centre (MSC) constitutes the interface between the radio system and the fixed networks. The MSC performs all necessary functions in order to handle the circuit-switched services to and from the mobile stations.
+
+In order to obtain radio coverage of a given geographical area, a number of BSS and/or RNS are normally required; i.e., each MSC would thus have to interface to one or more BSS(s) and/or RNS(s). In addition, several MSCs may be required to cover a country.
+
+When intra-domain connection of RAN nodes to multiple CN nodes is applied, all the MSCs serving a pool-area share the responsibility to serve the MSs located in the pool-area. All these MSCs interface to all the BSS(s) and/or RNS(s) forming the pool-area.
+
+The mobile-services switching centre is an exchange that performs all the switching and signalling functions for mobile stations located in a geographical area designated as the MSC area. When intra-domain connection of RAN nodes to multiple CN nodes is applied, one or more MSCs serve a pool-area, but each individual MS is served by only one out of these MSCs, as described in 3G TS 23.236. The main difference between a MSC and an exchange in a fixed network is that the MSC has to take into account the impact of the allocation of radio resources and the mobile nature of the subscribers and has to perform in addition, at least the following procedures:
+
+- procedures required for the location registration;
+- procedures required for handover.
+
+When needed, the MSC can be implemented in two different entities: the MSC server, handling only signalling, and the CS-MGW, handling user's data. A MSC server and a CS-MGW make up the full functionality of a MSC.
+
+### **7.2.2 Mobile switching centre server (MSC server)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4.1.2.1.1.
+
+The MSC server mainly comprises the call control (CC) and mobility control parts of a MSC.
+
+The MSC server is responsible for the control of mobile originated and mobile terminated CC CS domain calls. It terminates the user-network signalling and translates it into the relevant network-network signalling. The MSC server also contains a VLR to hold the mobile subscriber's service data and CAMEL related data.
+
+The MSC server controls the parts of the call state that pertain to connection control for media channels in a CS-MGW.
+
+### **7.2.3 Visitor location register (VLR)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4.1.1.2.
+
+A mobile station roaming in an MSC area is controlled by the visitor location register (VLR) in charge of this area. When a mobile station (MS) enters a new location area, it starts a registration procedure. The MSC in charge of that area notices this registration and transfers to the visitor location register the identity of the location area where the MS is situated. If this MS is not yet registered, the VLR and the HLR exchange information to allow the proper handling of calls involving the MS.
+
+A VLR may be in charge of one or several MSC areas.
+
+The VLR contains also the information needed to handle the calls set up or received by the MSs registered in its database (for some supplementary services the VLR may have to obtain additional information from the HLR). The following elements are included:
+
+- the international mobile subscriber identity (IMSI);
+- the mobile station international ISDN number (MSISDN);
+- the mobile station roaming number (MSRN);
+- the temporary mobile station identity (TMSI), if applicable;
+
+- the local mobile station identity (LMSI), if used;
+- the location area where the mobile station has been registered;
+- the identity of the SGSN where the MS has been registered. Only applicable to PLMNs supporting GPRS and which have a Gs interface between MSC/VLR and SGSN;
+- the last known location and the initial location of the MS.
+
+The VLR also contains supplementary service parameters attached to the mobile subscriber and received from the HLR.
+
+## 7.3 Home subscriber server (HSS)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4.1.1.1.
+
+The HSS is the master database for a given user. It is the entity containing the subscription-related information to support the network entities actually handling calls/sessions.
+
+A home network may contain one or several HSSs: it depends on the number of mobile subscribers, on the capacity of the equipment and on the organization of the network.
+
+As an example, the HSS provides support to the call control servers in order to complete the routing/roaming procedures by solving authentication, authorization, naming/addressing resolution, location dependencies, etc.
+
+The HSS is responsible for holding the following user-related information:
+
+- user identification, numbering and addressing information;
+- user security information: Network access control information for authentication and authorization;
+- user location information at inter-system level: The HSS supports the user registration, and stores inter-system location information, etc.;
+- user profile information.
+
+The HSS also generates user security information for mutual authentication, communication integrity check and ciphering.
+
+Based on this information, the HSS also is responsible for supporting the call control and session management entities of the different domains and subsystems (defined in clause 3) of the operator as shown in Figure 7.3-1.
+
+
+
+The diagram illustrates the HSS (Home Subscriber Server) as a central oval containing three boxes: 'Subscription information', 'Location information', and '...'. Below the HSS, six rectangular boxes represent different network entities: 'MSC server', 'GMSC server', 'SGSN', 'GGSN', 'CSCF', and 'GUP server'. Lines connect the HSS to each of these entities, labeled with interface names: 'D' (to MSC server), 'C' (to GMSC server), 'Gr' (to SGSN), 'Gc' (to GGSN), 'Cx' (to CSCF), and 'Rp' (to GUP server). A small text 'Q.1741.5(08)\_F7.3-1' is located at the bottom right of the diagram.
+
+Diagram of a generic HSS structure showing the HSS connected to various network entities via specific interfaces.
+
+Figure 7.3-1 – Example of a generic HSS structure and basic interfaces
+
+The HSS may integrate heterogeneous information, and enable enhanced features in the core network to be offered to the application and services domain, at the same time hiding the heterogeneity.
+
+The HSS consists of the following functionalities:
+
+- IP multimedia functionality to provide support to control functions of the IM subsystem such as the CSCF. It is needed to enable subscriber usage of the IM CN subsystem services. This IP multimedia functionality is independent of the access network used to access the IM CN subsystem.
+- The subset of the HLR/AUC functionality required by the PS domain.
+- The subset of the HLR/AUC functionality required by the CS domain, if it is desired to enable subscriber access to the CS domain or to support roaming to legacy GSM/UMTS CS domain networks.
+
+The organization of the subscriber data is outlined in 3GPP TS 23.008. It also indicates which numbers, addresses and identifiers specified in 3G TS 23.003 are stored in HSS.
+
+### 7.3.1 Home location register (HLR)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4.1.1.1.1.
+
+The HLR can be considered a subset of the HSS that holds the following functionalities:
+
+- The functionality required to provide support to PS domain entities such as the SGSN and GGSN, through the Gr and Gc interfaces. It is needed to enable subscriber access to the PS domain services.
+- The functionality required to provide support to CS domain entities such as the MSC/MSC server and GMSC/GMSC server, through the C and D interfaces. It is needed to enable subscriber access to the CS domain services and to support roaming to legacy GSM/UMTS CS domain networks.
+
+### 7.3.2 Authentication centre (AuC)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4.1.1.1.2.
+
+The AuC can be considered a subset of the HSS that holds the following functionalities for the CS domain and PS domain:
+
+- The AuC is associated with an HLR and stores an identity key for each mobile subscriber registered with the associated HLR. This key is used to generate security data for each mobile subscriber:
+ - data which are used for mutual authentication of the international mobile subscriber identity (IMSI) and the network;
+ - a key used to check the integrity of the communication over the radio path between the mobile station and the network;
+ - a key used to cipher communication over the radio path between the mobile station and the network.
+- The AuC communicates only with its associated HLR over a non-standardized interface denoted the H interface. The HLR requests the data needed for authentication and ciphering from the AuC via the H interface, stores them and delivers them to the VLR and SGSN which need them to perform the security functions for a mobile station.
+
+### 7.3.3 HSS logical functions
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4.1.1.1.3.
+
+This clause provides a high level and not exhaustive description of HSS functionality.
+
+
+
+The diagram illustrates the logical functions of the HSS and its interfaces. The HSS is shown as a large box containing several functional blocks. Below the HSS, the network is divided into three domains: CS domain, PS domain, and IM CN subsystem. The CS domain includes GMSC, MSC/VLR, and gsmSCF. The PS domain includes SGSN and GGSN. The IM CN subsystem includes SIP application server, OSA SCS, IM-SSF, and CSCF. Interfaces are labeled with letters: Wx, C, D, Gr, Gc, Rp, Sh, Si, and Cx. Other components shown include 3GPP AAA server, Applications, and GUP server.
+
+| HSS | |
+|--------------------------------------|-------------------------------|
+| Mobility management | Identification handling |
+| User security information generation | Service authorization support |
+| User security support | Access authorization |
+| Service provisioning support | Application services support |
+| Call/session establishment support | CAMEL services support |
+| GUP data repository | |
+
+Diagram of HSS logical functions showing the internal structure of the HSS and its interfaces with the CS domain, PS domain, and IM CN subsystem.
+
+Q.1741.5(08)\_F7.3.3-1
+
+Figure 7.3.3-1 – HSS logical functions
+
+- *Mobility management*
+This function supports the user mobility through CS domain, PS domain and IM CN subsystem.
+- *Call and/or session establishment support*
+The HSS supports the call and/or session establishment procedures in CS domain, PS domain and IM CN subsystem. For terminating traffic, it provides information on which call and/or session control entity currently hosts the user.
+- *User security information generation*
+The HSS generates user authentication, integrity and ciphering data for the CS and PS domains and for the IM CN subsystem.
+- *User security support*
+The HSS supports the authentication procedures to access CS domain, PS domain and IM CN subsystem services by storing the generated data for authentication, integrity and ciphering and by providing these data to the appropriate entity in the CN (i.e., MSC/VLR, SGSN or CSCF).
+- *User identification handling*
+The HSS provides the appropriate relations among all the identifiers uniquely determining the user in the system: CS domain, PS domain and IM CN subsystem (e.g., IMSI and MSISDNs for CS domain; IMSI, MSISDNs and IP addresses for PS domain, private identity and public identities for IM CN subsystem).
+
+- *Access authorization*
+
+The HSS authorizes the user for mobile access when requested by the MSC/VLR, SGSN or CSCF, by checking that the user is allowed to roam to that visited network.
+
+- *Service authorization support*
+
+The HSS provides basic authorization for MT call/session establishment and service invocation. Besides, the HSS updates the appropriate serving entities (i.e., MSC/VLR, SGSN, CSCF) with the relevant information related to the services to be provided to the user.
+
+- *Service provisioning support*
+
+The HSS provides access to the service profile data for use within the CS domain, PS domain and/or IM CN subsystem.
+
+- *Application services and CAMEL services support*
+
+The HSS communicates with the SIP application server and the OSA-SCS to support application services in the IM CN subsystem. It communicates with the IM-SSF to support the CAMEL services related to the IM CN subsystem. It communicates with the gsmSCF to support CAMEL services in the CS domain and PS domain.
+
+## 7.4 Equipment identity register (EIR)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4.1.1.4.
+
+The equipment identity register (EIR) is the logical entity, which is responsible for storing in the network the international mobile equipment identities (IMEIs) used.
+
+The equipment is classified as "white listed", "grey listed", "black listed", or it may be unknown.
+
+This functional entity contains one or several databases which store(s) the IMEIs used.
+
+The mobile equipment may be classified as "white listed", "grey listed" and "black listed" and therefore may be stored in three separate lists.
+
+An IMEI may also be unknown to the EIR.
+
+An EIR shall as a minimum contain a "white list" (Equipment classified as "white listed").
+
+## 7.5 SMS gateway MSC (SMS-GMSC)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4.1.1.5.
+
+The SMS gateway MSC (SMS-GMSC) acts as an interface between a short message service centre and the PLMN, to allow short messages to be delivered to mobile stations from the service centre (SC).
+
+The choice of which MSCs can act as SMS gateway MSCs is a network operator matter (e.g., all MSCs or some designated MSCs).
+
+## 7.6 SMS interworking MSC
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4.1.1.6.
+
+The SMS Interworking MSC acts as an interface between the PLMN and a short message service centre (SC) to allow short messages to be submitted from mobile stations to the SC.
+
+The choice of which MSCs can act as SMS interworking MSCs is a network operator matter (e.g., all MSCs or some designated MSCs).
+
+## 7.7 Gateway GPRS support node (GGSN)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clauses 4.1.3 and 4.1.3.2.
+
+The UMTS GPRS support nodes (GSN) is the gateway GSN (GGSN) and the serving GSN (SGSN). They constitute the interface between the radio system and the fixed networks for packet-switched services. The GSN performs all necessary functions in order to handle the packet transmission to and from the mobile stations.
+
+Gateway GPRS support node (GGSN): The location register function in the GGSN stores subscriber data received from the HLR and the SGSN. There are two types of subscriber data needed to handle originating and terminating packet data transfer:
+
+- Subscription information:
+ - the IMSI;
+ - zero or more PDP addresses.
+- Location information:
+ - the SGSN address for the SGSN where the MS is registered.
+
+## 7.8 Serving GPRS support node (SGSN)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clauses 4.1.3 and 4.1.3.1.
+
+The UMTS GPRS support nodes (GSN) is the gateway GSN (GGSN) and the serving GSN (SGSN). They constitute the interface between the radio system and the fixed networks for packet-switched services. The GSN performs all necessary functions in order to handle the packet transmission to and from the mobile stations.
+
+Serving GPRS support node (SGSN): The location register function in the SGSN stores two types of subscriber data needed to handle originating and terminating packet data transfer:
+
+- Subscription information:
+ - the IMSI;
+ - one or more temporary identities;
+ - zero or more PDP addresses.
+- Location information:
+ - depending on the operating mode of the MS, the cell or the routeing area where the MS is registered;
+ - the VLR number of the associated VLR (if the Gs interface is implemented);
+ - the GGSN address of each GGSN for which an active PDP context exists.
+
+## 7.9 Circuit switched – Media gateway function (CS-MGW)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4.1.2.1.2.
+
+NOTE – In this Recommendation, the term "Media Gateway Function (MGW)" is used when there is no need to differentiate between the CS domain entity and the IP multimedia CN subsystem entity. When referring specifically to the CS domain entity, the term "CS-MGW" is used. When referring specifically to the IP multimedia CN subsystem entity, the term "IM-MGW" is used.
+
+This component is PSTN/PLMN transport termination point for a defined network and interfaces UTRAN with the core network over Iu.
+
+A CS-MGW may terminate bearer channels from a switched-circuit network and media streams from a packet network (e.g., RTP streams in an IP network). Over Iu, the CS-MGW may support media conversion, bearer control and payload processing (e.g., codec, echo canceller, conference bridge) for support of different Iu options for CS services (AAL 2/ATM-based as well as RTP/UDP/IP-based).
+
+The CS-MGW:
+
+- interacts with MGCF, MSC server and GMSC server for resource control;
+- owns and handles resources such as echo cancellers, etc.;
+- may need to have codecs.
+
+The CS-MGW will be provisioned with the necessary resources for supporting UMTS/GSM transport media. Further tailoring (i.e., packages) of the H.248.1 may be required to support additional codecs and framing protocols, etc.
+
+The CS-MGW bearer control and payload processing capabilities will also need to support mobile specific functions such as SRNS relocation/handover and anchoring. It is expected that current H.248.1 standard mechanisms can be applied to enable this.
+
+## **7.10 IP multimedia (IM) core network (CN) subsystem entities**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4a.7.
+
+### **7.10.1 Call session control function (CSCF)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4a.7.1.
+
+The CSCF can act as proxy CSCF (P-CSCF), serving CSCF (S-CSCF) or interrogating CSCF (I-CSCF). The P-CSCF is the first contact point for the UE within the IM subsystem (IMS); the S-CSCF actually handles the session states in the network; the I-CSCF is mainly the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. Further definitions of the P-, S- and I-CSCF are provided in 3G TS 23.228.
+
+### **7.10.2 Media gateway control function (MGCF)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4a.7.2.
+
+The MGCF:
+
+- controls the parts of the call state that pertain to connection control for media channels in an IMS-MGW;
+- communicates with CSCF;
+- selects the CSCF depending on the routing number for incoming calls from legacy networks;
+- performs protocol conversion between ISUP and the IM subsystem call control protocols;
+- out-of-band information assumed to be received in MGCF and may be forwarded to CSCF/IMS-MGW.
+
+### **7.10.3 IP multimedia subsystem – Media gateway function (IMS-MGW)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4a.7.3.
+
+NOTE – In this Recommendation, the term "Media Gateway Function (MGW)" is used when there is no need to differentiate between the CS domain entity and the IP multimedia CN subsystem entity. When referring specifically to the CS domain entity, the term "CS-MGW" is used. When referring specifically to the IP multimedia CN subsystem entity, the term "IMS-MGW" is used.
+
+An IMS-MGW may terminate bearer channels from a switched-circuit network and media streams from a packet network (e.g., RTP streams in an IP network). The IMS-MGW may support media conversion, bearer control and payload processing (e.g., codec, echo canceller, conference bridge), it:
+
+- interacts with the MGCF for resource control;
+- owns and handles resources such as echo cancellers, etc.;
+- may need to have codecs.
+
+The IMS-MGW will be provisioned with the necessary resources for supporting UMTS/GSM transport media. Further tailoring (i.e., packages) of the H.248.1 may be required to support additional codecs and framing protocols, etc.
+
+#### **7.10.4 Multimedia resource function controller (MRFC)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4a.7.4.
+
+The MRFC:
+
+- controls the media stream resources in the MRFP;
+- interprets information coming from an AS and S-CSCF (e.g., session identifier) and controls MRFP accordingly;
+- generates CDRs.
+
+### **7.10.5 Multimedia resource function processor (MRFP)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4a.7.4a.
+
+The MRFP:
+
+- controls bearers on the Mb reference point;
+- provides resources to be controlled by the MRFC;
+- mixes incoming media streams (e.g., for multiple parties);
+- sources media streams (for multimedia announcements);
+- processes media streams (e.g., audio transcoding, media analysis).
+
+#### **7.10.6 Subscription locator function (SLF)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4a.7.5.
+
+The SLF:
+
+- is queried by the I-CSCF during the registration and session setup to get the name of the HSS containing the required subscriber specific data. Furthermore, the SLF is also queried by the S-CSCF during the registration;
+- is accessed via the Dx interface.
+
+The SLF is not required in a single HSS environment. An example for a single HSS environment is a server farm architecture.
+
+### **7.10.7 Breakout gateway control function (BGCF)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4a.7.6.
+
+The breakout gateway control function (BGCF) selects the network in which PSTN breakout is to occur and – within the network where the breakout is to occur – selects the MGCF.
+
+### **7.10.8 Application server (AS)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4a.7.7.
+
+An application server (AS) i.e., SIP application server, OSA application server, or CAMEL IM-SSF, offers value-added IM services and resides either in the user's home network or in a third-party location. The third party could be a network or simply a stand-alone AS.
+
+NOTE – The OSA application server does not directly interact with the IMS network entities but through the OSA service capability servers (OSA SCSs). Further information on OSA is provided in 3G TS 22.127.
+
+The AS (SIP application server and/or the OSA service capability server and/or IM-SSF) can communicate with the HSS. The Sh and Si interfaces are used for this purpose.
+
+The serving-CSCF to AS interface is used to provide services residing in an AS. Two cases were identified:
+
+- Serving-CSCF to an AS in home network;
+- Serving-CSCF to an AS in a trusted external network (e.g., third party or visited). The S-CSCF does not provide authentication and security functionality for secure direct third party access to the IM subsystem. The OSA framework provides a standardized way for third party access to the IM subsystem.
+
+An Application Server may influence and impact the SIP session on behalf of the services supported by the operator's network. An AS may host and execute services.
+
+## **7.11 Signalling gateway function (SGW)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4a.8.
+
+The SGW performs the signalling conversion (both ways) at transport level between the SS7-based transport and the IP-based transport of signalling (i.e., between Sigtran SCTP/IP and SS7 MTP). The SGW does not interpret the application layer (e.g., MAP, CAP, BICC, ISUP) messages but may have to interpret the underlying SCCP or SCTP layer to ensure proper routing of the signalling.
+
+## **7.12 Global text telephony specific entities**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4a.9.
+
+Interworking between cellular text modem (CTM) and text telephony standards (e.g., V.18) used in external networks can be supported by three methods:
+
+- Routing calls through a CTM special resource function (CTM-SRF) in the core network. The CTM-SRF is linked into the call path via CAMEL procedures. Depending on operator configuration, the CTM-SRF may also be linked into the call path for emergency calls.
+- A CTM/text telephone converting function included along the speech call path selected by the network after an indication from the terminal that CTM is required.
+
+– A CTM/text telephone converting function included in all speech call paths.
+
+Further information of the support for text telephony is found in 3G TS 23.226.
+
+For further details of CTM, see 3G TS 26.226.
+
+## **7.13 Security gateway (SEG)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4a.10.
+
+The UMTS network domain shall be logically and physically divided into security domains in order to protect IP-based control plane signalling. These security domains typically coincide with operator borders.
+
+The interface between different security domains is protected by security gateways (SEGs). The SEGs are responsible for enforcing the security policy of an IP security domain towards other SEGs in the destination IP security domain. All NDS/IP traffic shall pass through a SEG before entering or leaving a security domain. The security policy between security domains is subject to inter-domain agreements. This may differ from the security policy within the same security domain, which is optional to implementation and unilaterally decided by the security domain operator. For further details of SEG, see 3G TS 33.210.
+
+## **7.14 Gateway mobile location centre (GMLC)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4a.3.2.
+
+The gateway mobile location centre (GMLC) is the first node an external location application accesses in the PLMN. The GMLC performs registration authorization and requests routing information from the HLR. There may be more than one GMLC in a PLMN.
+
+## **7.15 GPRS service switching function (gprsSSF)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4a.4.4.
+
+GPRS service switching function (gprsSSF) is a functional entity that interfaces the SGSN to the gsmSCF. The concept of the gprsSSF is derived from the IN SSF, but uses different triggering mechanisms because of the nature of the mobile network.
+
+## **7.16 GSM service control function (gsmSCF)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4a.4.1.
+
+GSM service control function (gsmSCF) is a functional entity that contains the CAMEL service logic to implement operator specific service. It interfaces with the gsmSSF, the gsmSRF and the HLR.
+
+## **7.17 GSM service switching function (gsmSSF)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4a.4.2.
+
+GSM service switching function (gsmSSF) is a functional entity that interfaces the MSC/GMSC to the gsmSCF. The concept of the gsmSSF is derived from the IN SSF, but uses different triggering mechanisms because of the nature of the mobile network.
+
+## **7.18 GSM specialized resource function (gsmSRF)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 4a.4.3.
+
+GSM specialized resource function (gsmSRF) is a functional entity, which provides various specialized resources. It interfaces with the gsmSCF and with the MSC. This entity is defined in [ITU-T Q.1214] with variations defined in 3G TS 23.078.
+
+## **7.19 Gateway location register (GLR)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause A.2.1.
+
+The gateway location register (GLR) handles location management of roaming subscriber in visited network without involving HLR. The location register function in the GLR stores subscription information and routeing information for both CS services and PS services. This entity can be located only in a visited PLMN. The GLR is an optional function entity to optimize signalling traffic between PLMNs.
+
+## **7.20 Intermediate GPRS serving node (IM-GSN)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause A.2.3.
+
+The intermediate GPRS serving node (IM-GSN) is used as serving GSN towards home network and relay some PDU notification messages between serving GSN and gateway GSN. This entity can be located only in a visited PLMN.
+
+## **7.21 Intermediate mobile-service switching centre (IM-MSC)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause A.2.2.
+
+The intermediate mobile-services switching centre (IM-MSC) is used as serving MSC towards home network and relays some messages between home network and serving MSC. This entity can be located only in a visited PLMN.
+
+# **8 Interfaces and reference points**
+
+## **8.1 C interface (Gateway mobile switching centre server (GMSC server) – Home location register (HLR))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6.4.1.2.
+
+The gateway MSC server must interrogate the HLR of the required subscriber to obtain routeing information for a call or a short message directed to that subscriber.
+
+Signalling on this interface uses the mobile application part (MAP), which in turn uses the services of transaction capabilities.
+
+For customized application for mobile network enhanced logic (CAMEL) purposes, this interface is used, e.g., at terminating calls to exchange routeing information, subscriber status, location information, subscription information, etc.
+
+## **8.2 D interface (Visitor location register (VLR) – Home location register (HLR))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6.4.1.3.
+
+This interface is used to exchange the data related to the location of the mobile station and to the management of the subscriber. The main service provided to the mobile subscriber is the capability to set up or to receive calls within the whole service area. To support this, the location registers have to exchange data. The VLR informs the HLR of the location of a mobile station managed by the latter and provides it (either at location updating or at call set-up) with the roaming number of that station. The HLR sends to the VLR all the data needed to support the service to the mobile subscriber. The HLR then instructs the previous VLR to cancel the location registration of this subscriber. Exchanges of data may occur when the mobile subscriber requires a particular service, when he wants to change some data attached to his subscription or when some parameters of the subscription are modified by administrative means.
+
+Signalling on this interface uses the mobile application part (MAP), which in turn uses the services of transaction capabilities.
+
+For customized application for mobile network enhanced logic (CAMEL) purposes, this interface is used to send the CAMEL related subscriber data to the visited PLMN and for provision of mobile station roaming number (MSRN). The interface is also used for the other purposes, e.g., to retrieve subscriber status and location information of the mobile subscriber or to indicate suppression of announcement for a CAMEL service.
+
+## **8.3 E interface (Mobile switching centre server (MSC server) – Mobile switching centre server (MSC server))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6.4.1.4.
+
+When a mobile station moves from one MSC area to another during a call, a handover procedure has to be performed in order to continue the communication. For that purpose, the MSC servers have to exchange data to initiate and then to realize the operation.
+
+After the handover operation has been completed, the MSC servers will exchange information to transfer A-interface or Iu-interface signalling as defined in 3G TS 23.009.
+
+When a short message is to be transferred between a mobile station and short message service centre (SC), in either direction, this interface is used to transfer the message between the MSC server serving the mobile station and the MSC server, which acts as the interface to the SC.
+
+Signalling on this interface uses the mobile application part (MAP), which in turn uses the services of transaction capabilities (see 3G TS 29.002).
+
+## **8.4 F interface (Mobile switching centre server (MSC server) – Equipment identity register (EIR))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6.4.1.5.
+
+This interface is used between MSC server and EIR to exchange data, in order that the EIR can verify the status of the IMEI retrieved from the mobile station.
+
+Signalling on this interface uses the mobile application part (MAP), which in turn uses the services of transaction capabilities.
+
+## **8.5 G interface (Visitor location register (VLR) – Visitor location register (VLR))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6.4.1.6.
+
+When a mobile subscriber moves from a VLR area to another location registration procedure will happen. This procedure may include the retrieval of the IMSI and authentication parameters from the old VLR.
+
+Signalling on this interface uses the mobile application part (MAP), which in turn uses the services of transaction capabilities.
+
+## **8.6 Gc interface (Home location register (HLR) – Gateway GPRS support node (GGSN))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6.4.2.3.
+
+This optional signalling path may be used by the GGSN to retrieve information about the location and supported services for the mobile subscriber, to be able to activate a packet data network address.
+
+There are two alternative ways to implement this signalling path:
+
+- If an SS7 interface is implemented in the GGSN, signalling between the GGSN and the HLR uses the mobile application part (MAP), which in turn uses the services of transaction capabilities (TCAP);
+- If there is *no* SS7 interface in the GGSN, any GSN in the same PLMN and which has an SS7 interface installed can be used as a GTP to MAP protocol converter, thus forming a signalling path between the GGSN and the HLR.
+
+## **8.7 Gf interface (Equipment identity register (EIR) – Serving GPRS support node (SGSN))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6.4.2.4.
+
+This interface is used between SGSN and EIR to exchange data, in order that the EIR can verify the status of the IMEI retrieved from the mobile station.
+
+Signalling on this interface uses the mobile application part (MAP), which in turn uses the services of transaction capabilities (TCAP).
+
+## **8.8 Reference point GGSN – Packet data networks (Gi reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 7.2.
+
+This is the reference point between the GGSN and a packet data network. It may be an operator external public or private packet data network or an intra operator packet data network, e.g., for provision of IMS services.
+
+## **8.9 GLa interface (Gateway location register (GLR) – Home location register (HLR))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause A.5.1.
+
+In circuit switched domain, this interface is the same as that between the VLR and the HLR. The HLR regards the GLR as the VLR via this interface. On the other hand, in packet switched domain, this interface is the same as that between the SGSN and the HLR. The HLR regards the GLR as the SGSN via this interface.
+
+## **8.10 GLb interface (Gateway location register (GLR) – Visitor location register (VLR))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause A.5.2.
+
+This interface is the same as those between the VLR and the HLR. The VLR regards the GLR as the HLR via this interface.
+
+## **8.11 GLc interface (Gateway location register (GLR) – Serving GPRS support node (SGSN))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause A.5.3.
+
+This interface is the same as those between the SGSN and the HLR. The SGSN regards the GLR as the HLR via this interface.
+
+## **8.12 GLd interface (Gateway location register (GLR) – Intermediate mobile-services switching centre (IM-MSC))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause A.5.4.
+
+In the network with the GLR, when the IM-MSC receives a message, it interrogates the GLR for the routing information of the MSC. However, this interface is internal because GLR and IM-MSC are implemented in the same physical node and the protocol on this interface is not specified.
+
+## **8.13 GLe interface (Gateway location register (GLR) – Intermediate GPRS serving node (IM-GSN))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause A.5.5.
+
+In the network with the GLR when the IM-GSN receiving a PDU notification from the GGSN, the IM-GSN relays the notification to the SGSN by interrogating via the interface the routing information to the GLR. The interrogation uses the same operation on the interface between the SGSN and the HLR.
+
+## **8.14 GLf interface (Gateway location register (GLR) – Short message service-gateway mobile switching centre (SMS-GMSC))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause A.5.6.
+
+This interface is used to forward mobile-terminated short messages in the network with the GLR in case of SMS transfer over GPRS. Signalling on this interface uses the mobile application part (MAP).
+
+The SMS-GMSC regards the GLR as the SGSN via this interface.
+
+## **8.15 GLg interface (Intermediate mobile-services switching centre (IM-MSC) – Short message service-gateway mobile switching centre (SMS-GMSC))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause A.5.7.
+
+This interface is used to forward short messages in the network with the GLR in case of SMS transfer over non-GPRS. Signalling on this interface uses the mobile application part (MAP).
+
+The SMS-GMSC regards the IM-MSC as the MSC via this interface.
+
+## **8.16 GLh interface (Intermediate mobile-services switching centre (IM-MSC) – Mobile switching centre (MSC))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause A.5.8.
+
+This interface is used to forward short messages in the network with the GLR in case of SMS transfer over non-GPRS. Also this interface is used to exchange data needed by the MSC to perform subscriber authorization and allocate network resources. Signalling on this interface uses the mobile application part (MAP).
+
+## **8.17 GLi interface (Intermediate mobile-services switching centre (IM-MSC) – Gateway mobile location centre (GMLC))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause A.5.9.
+
+Also this interface is used to exchange data needed by the MSC to perform subscriber authorization and allocate network resources. Signalling on this interface uses the mobile application part (MAP).
+
+The GMLC regards the IM-MSC as the MSC via this interface.
+
+## **8.18 GLj interface (Intermediate GPRS serving node (IM-GSN) – Gateway GPRS support node (GGSN))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause A.5.10.
+
+In the network with the GLR when receiving a PDP PDU from the external network, the GGSN sends a notification to the IM-GSN by the routing information from the HLR. The GGSN regards the IM-GSN as the SGSN via this interface.
+
+## **8.19 GLk interface (Intermediate GPRS serving node (IM-GSN) – Serving GPRS support node (SGSN))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause A.5.11.
+
+In the network with the GLR when receiving a PDP notification from the GGSN, the IM-GSN relays the notification to the SGSN by the routing information from the GLR. The SGSN regards the IM-GSN as the GGSN via this interface.
+
+## **8.20 Gn interface (Gateway GPRS support node (GGSN) – Serving GPRS support node (SGSN))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6.4.2.2.
+
+This interface is used to support mobility between the SGSN and GGSN. The Gn interface is used when GGSN and SGSN are located inside one PLMN. The Gn interface also includes a part which allows SGSNs to communicate subscriber and user data, when changing SGSN.
+
+Signalling on this interface uses the user datagram protocol, UDP/IP.
+
+## **8.21 Gp interface (Serving GPRS support node (SGSN) – External data network)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6.4.2.2.
+
+The Gp interface is used if GGSN and SGSN are located in different PLMNs. The Gp interface also includes a part that allows SGSNs to communicate subscriber and user data, when changing SGSN.
+
+Signalling on this interface uses the user datagram protocol, UDP/IP.
+
+## **8.22 Gr interface (Home location register (HLR) – Serving GPRS support node (SGSN))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6.4.2.1.
+
+This interface is used to exchange the data related to the location of the mobile station and to the management of the subscriber. The main service provided to the mobile subscriber is the capability to transfer packet data within the whole service area. The SGSN informs the HLR of the location of a mobile station managed by the latter. The HLR sends to the SGSN all the data needed to support the service to the mobile subscriber. Exchanges of data may occur when the mobile subscriber requires a particular service, when he wants to change some data attached to his subscription or when some parameters of the subscription are modified by administrative means.
+
+Signalling on this interface uses the mobile application part (MAP), which in turn uses the services of transaction capabilities (TCAP).
+
+## **8.23 Gs interface (Mobile switching centre (MSC)/Visitor location register (VLR) – Serving GPRS support node (SGSN))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6.4.3.1.
+
+The SGSN may send location information to the MSC/VLR via the optional Gs interface. The SGSN may receive paging requests from the MSC/VLR via the Gs interface. The MSC/VLR may indicate to an SGSN, via the Gs interface, that an MS is engaged in a service handled by the MSC.
+
+Signalling on this interface uses connectionless SCCP (without TCAP). SCCP global title (GT) is used for addressing.
+
+## **8.24 gsmSCF – HLR interface**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.4.4.
+
+This interface is used by the gsmSCF to request information from the HLR. As a network operator option, the HLR may refuse to provide the information requested by the gsmSCF.
+
+This interface is also used for USSD operations, both for gsmSCF-initiated dialogues and MS-initiated dialogues (relayed via HLR). It is a network operator option whether to support or not USSD operations on this interface.
+
+## **8.25 gsmSCF – gsmSRF interface**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.4.5.
+
+This interface is used by the gsmSCF to instruct the gsmSRF to play tones/announcements to the users.
+
+## **8.26 gsmSSF – gsmSCF interface**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.4.2.
+
+This interface is used by the gsmSCF to control a call in a certain gsmSSF and to request the gsmSSF to establish a connection with a gsmSRF. Relationships on this interface are opened as a result of the gsmSSF sending a request for instructions to the gsmSCF.
+
+## **8.27 gprsSSF – gsmSCF interface**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.4.8.
+
+This interface is used by the gsmSCF to control a GPRS session or individual PDP Context in a certain gprsSSF. Relationships between the gprsSSF and the gsmSCF (GPRS dialogues) on this interface are opened as a result of the gprsSSF sending a request for instructions to the gsmSCF.
+
+## **8.28 H interface (Home location register (HLR) – Authentication centre (AuC))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6.4.3.2.
+
+When an HLR receives a request for authentication and ciphering data for a mobile subscriber and it does not hold the requested data, the HLR requests the data from the AuC. The protocol used to transfer the data over this interface is not standardized.
+
+## **8.29 IuBC interface (Cell broadcast centre (CBC) – Radio network subsystem (RNS))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.5.1.
+
+The IuBC interface between the CBC and the RNS is specified in the 25.41x-series of 3G Technical Specifications.
+
+The CBC-RNS interface is used to carry information concerning:
+
+- the CBS messages itself; and
+- CBS delivery parameter.
+
+## **8.30 IuCS interface (Mobile switching centre (MSC) – RNS or BSS)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clauses 6.2.1.2 and 6.2.1.3.
+
+The IuCS interface between the MSC and its RNS or BSS is specified in the 25.41x-series of UMTS Technical Specifications.
+
+The RNS-MSC interface is used to carry information concerning:
+
+- RNS management;
+- call handling;
+- mobility management.
+
+## **8.31 IuPS interface (Serving GPRS support node (SGSN) – RNS or BSS)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clauses 6.2.2.2 and 6.2.2.3.
+
+The IuPS interface between SGSN and RNS/BSS is used to carry information concerning:
+
+- packet data transmission;
+- mobility management.
+
+The IuPS interface is defined in the 25.41x-series of 3G Technical Specifications.
+
+## **8.32 A interface (Mobile switching centre (MSC) – Base station system (BSS))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6.2.1.1.
+
+The A interface between the MSC and its BSS is specified in the 48-series of Technical Specifications.
+
+The BSS-MSC interface is used to carry information concerning:
+
+- BSS management;
+- call handling;
+- mobility management.
+
+## **8.33 Gb interface (Serving GPRS support node (SGSN) – Base station system (BSS))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6.2.2.1.
+
+The BSS-SGSN interface is used to carry information concerning:
+
+- packet data transmission;
+- mobility management.
+
+The Gb interface is defined in 3G TS 48.014, 3G TS 48.016 and 3G TS 48.018.
+
+## **8.34 Reference point GMLC – external LCS client (Le reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 7.3.
+
+At this reference point, external LCS clients request services from the PLMN.
+
+## **8.35 LCS interfaces using MAP**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.3.1.
+
+The following interfaces are based on MAP in LCS.
+
+### **8.35.1 Lh interface (interface between GMLC and HLR)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.3.1.
+
+This interface is used by the GMLC to request the address of the visited MSC or SGSN for a particular target UE whose location has been requested (see 3G TS 29.002).
+
+### **8.35.2 Lg interface (interface between GMLC – MSC and GMLC – SGSN)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.3.1.
+
+This interface is used by the GMLC to convey a location request to the MSC or SGSN currently serving a particular target UE whose location was requested. The interface is used by the MSC or SGSN to return location results to the GMLC (see 3G TS 29.002).
+
+### **8.35.3 Lc interface (between GMLC and gsmSCF, CAMEL)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.3.1.
+
+This interface is used to get location information for CAMEL-based services GMLC (see 3G TS 29.002).
+
+## **8.36 Mc reference point (Mobile switching centre server (MSC Server) – Circuit switched media gateway (CS-MGW))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6.4.1.7.
+
+The Mc reference point describes the interfaces between the MGCF and IMS-MGW, between the MSC server and CS-MGW, and between the GMSC Server and CS-MGW. It has the following properties:
+
+- Full compliance with [ITU-T H.248.1].
+- Flexible connection handling that allows support of different call models and different media processing purposes not restricted to H.323 usage.
+- Open architecture where extensions/packages definition work on the interface may be carried out.
+- Dynamic sharing of MGW physical node resources. A physical MGW can be partitioned into logically separate virtual MGWs/domains consisting of a set of statically allocated terminations.
+- Dynamic sharing of transmission resources between the domains as the MGW controls bearers and manage resources according to the H.248.1 protocols.
+
+The functionality across the Mc reference point will need to support mobile specific functions such as SRNS relocation/handover and anchoring. It is expected that current H.248.1/IETF Megaco standard mechanisms can be applied to enable this.
+
+## **8.37 Mobile switching centre (MSC) – gsmSCF interface**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.4.6.
+
+This interface is used by the MSC to send supplementary service invocation notifications to the gsmSCF.
+
+## **8.38 Nb reference point (Circuit switched media gateway (CS-MGW) – Circuit switched media gateway (CS-MGW))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6.4.1.9.
+
+Over the Nb reference point the bearer control and transport are performed. The transport may be RTP/UDP/IP [IETF RFC 1889] and [IETF RFC 768] or AAL 2 [ITU-T I.363.2] for transport of user data. In the R00 architecture, different options for user data transport and bearer control shall be possible on Nb, for example: AAL 2/Q.AAL 2, STM/none, RTP/H.245, IPBC.
+
+## **8.39 Nc reference point (Mobile switching centre server (MSC server) – Gateway mobile switching centre server (GMSC server))**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6.4.1.8.
+
+Over the Nc reference point, the network-network-based call control is performed. Examples of this are ISUP or an evolution of ISUP for bearer independent call control (BICC). Different options for signalling transport on Nc shall be possible including IP.
+
+## **8.40 Reference point fixed networks – MSC**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 7.1.
+
+The MSC is based on a normal ISDN exchange. It has, for call control, the same reference points as the fixed network exchanges. The signalling reference point considered in the Technical Specifications is related to the Signalling System No. 7 user parts TUP and ISUP associated to the circuits used for incoming and outgoing calls.
+
+## **8.41 IM subsystem reference points**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.7.
+
+### **8.41.1 Reference point HSS – CSCF (Cx reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.7.1.
+
+The Cx reference point supports information transfer between CSCF and HSS.
+
+The main procedures that require information transfer between CSCF and HSS are:
+
+- 1) Procedures related to serving CSCF assignment.
+- 2) Procedures related to routing information retrieval from HSS to CSCF.
+- 3) Procedures related to authorization (e.g., checking of roaming agreement).
+- 4) Procedures related to authentication: transfer of security parameters of the subscriber between HSS and CSCF.
+- 5) Procedures related to filter control: transfer of filter parameters of the subscriber from HSS to CSCF.
+
+Further information on the Cx reference point is provided in 3G TS 23.228.
+
+### **8.41.2 Reference point CSCF – UE (Gm reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.7.2.
+
+The Gm reference point supports the communication between UE and IM CN subsystem, e.g., related to registration and session control.
+
+The protocol used for the Gm reference point is SIP (as defined by IETF RFC 3261], other relevant RFCs, and additional enhancements introduced to support 3GPP's needs).
+
+### **8.41.3 Reference point MGCF – IMS-MGW (Mn reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.7.3.
+
+The Mn reference point describes the interfaces between the MGCF and IMS-MGW in the IMS. It has the following properties:
+
+- Full compliance with the H.248.1 standard functions for IMS-PSTN/PLMN interworking.
+- Flexible connection handling which allows support of different call models and different media processing purposes not restricted to [ITU-T H.323] usage.
+- Open architecture where extensions/Packages definition work on the interface may be carried out.
+
+- Dynamic sharing of IMS-MGW physical node resources. A physical IMS-MGW can be partitioned into logically separate virtual MGWs/domains consisting of a set of statically allocated Terminations.
+- Dynamic sharing of transmission resources between the domains as the IMS-MGW controls bearers and manage resources according to the H.248.1 protocols and functions for IMS.
+
+### **8.41.4 Reference point MGCF – CSCF (Mg reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.7.4.
+
+The Mg reference point allows the MGCF to forward incoming session signalling (from the PSTN) to the CSCF for the purpose of interworking with PSTN networks.
+
+The protocol used for the Mg reference point is SIP (as defined by [IETF RFC 3261], other relevant RFCs, and additional enhancements introduced to support 3GPP's needs).
+
+#### **8.41.5 Reference point CSCF – MRFC (Mr reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.7.6.
+
+The Mr reference point allows interaction between an S-CSCF and an MRFC.
+
+The protocol used for the Mr reference point is SIP (as defined by [IETF RFC 3261], other relevant RFCs, and additional enhancements introduced to support 3GPP's needs).
+
+#### **8.41.6 Reference point MRFC – MRFP (Mp reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.7.6a.
+
+The Mp reference point has the following properties:
+
+- Full compliance with [ITU-T H.248.1].
+- Open architecture where extensions (packages) definition work on the interface may be carried out.
+
+#### **8.41.7 Reference point CSCF – CSCF (Mw reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.7.7.
+
+The Mw reference point allows the communication and forwarding of signalling messaging between CSCFs, e.g., during registration and session control.
+
+#### **8.41.8 Reference point GGSN – PDF (Go reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.7.9.
+
+This interface allows the policy decision function (PDF) to apply policy to the bearer usage in the GGSN.
+
+The policy decision function (PDF) is a logical entity of the P-CSCF. If the PDF is implemented in a separate physical node, the interface between the PDF and the P-CSCF is not standardized.
+
+#### **8.41.9 Reference point CSCF – BGCF (Mi reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.7.10.
+
+This reference point allows the serving CSCF to forward the session signalling to the breakout gateway control function for the purpose of interworking to the PSTN networks.
+
+The Mi reference point is based on external specifications, i.e., SIP [IETF RFC 3261].
+
+#### **8.41.10 Reference point BGCF – MGCF (Mj reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.7.11.
+
+This reference point allows the breakout gateway control function to forward the session signalling to the media gateway control function for the purpose of interworking to the PSTN networks.
+
+The Mj reference point is based on external specifications, i.e., SIP [IETF RFC 3261].
+
+#### **8.41.11 Reference point BGCF – BGCF (Mk reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.7.12.
+
+This reference point allows the breakout gateway control function to forward the session signalling to another breakout gateway control function.
+
+The Mk reference point is based on external specifications, i.e., SIP [IETF RFC 3261].
+
+#### **8.41.12 Reference point CSCF – SLF (Dx reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.7.13.
+
+This interface between CSCF and SLF is used to retrieve the address of the HSS which holds the subscription for a given user.
+
+This interface is not required in a single HSS environment. An example for a single HSS environment is a server farm architecture.
+
+Details are described in 3G TS 23.228, subclause 5.8.1.
+
+#### **8.41.13 Reference point to IPv6 network services (Mb reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.7.14.
+
+Via the Mb reference point, IPv6 network services are accessed. These IPv6 network services are used for user data transport. Note that GPRS provides IPv6 network services to the UE, i.e., the GPRS Gi reference point and the IMS Mb reference point may be the same.
+
+#### **8.41.14 Reference point CSCF – AS (ISC reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.7.15.
+
+This interface between CSCF and the application servers (i.e., SIP application server, OSA service capability server, or CAMEL IM-SSF) is used to provide services for the IMS.
+
+Details are described in 3G TS 23.228, subclause 4.2.4.
+
+### **8.41.15 Reference point HSS – SIP AS or OSA SCS (Sh reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.7.16.
+
+The application server (SIP application server and/or the OSA service capability server) may communicate the HSS. The Sh interface is used for this purpose. Details are described in 3G TS 23.228, subclause 4.2.4.
+
+### **8.41.16 Reference point HSS – CAMEL IM-SSF (Si reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 6a.7.17.
+
+The CAMEL application server (IM-SSF) may communicate to the HSS. The Si interface is used for this purpose. Details are described in 3G TS 23.228, subclause 4.2.4.
+
+## **8.42 Reference point CSCF – Multimedia IP networks (Mm reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 7.4.
+
+This is an IP interface between CSCF and IP networks. This interface is used, for example, to receive a session request from another SIP server or terminal.
+
+## **8.43 Reference point PDG – Packet data networks (Wi reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 7.6.
+
+This is the reference point between the PDG and a packet data network. It may be an operator external public or private packet data network or an intra operator packet data network, e.g., for provision of IMS services.
+
+## **8.44 Reference point WAG – WLAN access network (Wn reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002], [TTA TTAT.3G-23.002] and [CCSA-TSD-123 002], clause 7.7.
+
+This is the reference point between the WAG and the WLAN access network. It is used to force traffic between a WLAN UE and PDG to go through the WAG.
+
+# **9 Technical specifications structure**
+
+This clause provides an overview of the specifications for this IMT-2000 Family Member based on GSM evolved UMTS core network. Details for these specifications may be found in clause 10.
+
+The following text describes the numbering scheme for the specifications and reports for the 3GPP 3rd generation mobile system.
+
+Specifications for Release 7 of the 3rd generation mobile system are identified by the "ab.cde" numbering scheme.
+
+The following series titles and descriptions are used for guidance only and may be further developed with experience.
+
+The specification series are:
+
+| | |
+|-----------|----------------------------------------|
+| 21-series | Requirements specifications |
+| 22-series | Service aspects |
+| 23-series | Technical realization |
+| 24-series | Signalling protocols (UE – CN network) |
+| 25-series | UTRA aspects (Note 1) |
+| 26-series | Codecs (speech, video, etc.) |
+| 27-series | Data |
+| 28-series | Signalling protocols (RSS – CN) |
+| 29-series | Signalling protocols |
+
+| | |
+|-----------|-------------------------------|
+| 30-series | Programme management (Note 2) |
+| 31-series | User identity module (UIM) |
+| 32-series | Operation and maintenance |
+| 33-series | Security aspects |
+| 34-series | Test specifications (Note 2) |
+| 35-series | Algorithm specifications |
+| 48-series | GERAN aspects (Note 1) |
+
+NOTE 1 – Technical Specifications in this series are not included in the scope for this Recommendation. They are described in [ITU-R M.1457-7].
+
+NOTE 2 – Technical Specifications in these series are not included in the scope for this Recommendation.
+
+# 10 Technical specifications
+
+The working procedures within the 3GPP allow a continuous improvement of their specifications by means of a change request procedure. The Change Requests are reviewed by each 3GPP working group and provided for approval to the quarterly 3GPP TSG plenary meetings. Therefore, the SDO standards/specifications can be updated after each 3GPP TSG plenary meetings. In this context, it is recommended to the reader to retrieve the latest version of the SDO Standards/Specifications from the location indicated within the template.
+
+NOTE – The format of the "issued date" column in clause 10 is **yyyy-mm-dd** (for year-month-day) or Month-yyyy, respectively, in case the day of month has not been specified.
+
+## 10.1 21-series, Requirements specifications
+
+### 10.1.1 TS 21.101 technical specifications and technical reports for a UTRAN-based 3GPP system (Release 7)
+
+The document identifies the 3rd generation mobile system specifications for Release 7. The specifications and reports of 3G Release 7 have a major version number 7 (e.g., 7.x.y).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-21.101V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/21/A21101-700.pdf |
+| CCSA | CCSA-TSD-121101 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 121 101 | 7.0.0 | Published | 2007-10-16 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0021101v700 |
+| ATIS | ATIS.3GPP.21.101V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/seaarch.aspx |
+| TTA | TTAT.3G-21.101(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-21.101(R7-7.0.0).zip |
+| TTC | TS-3GA-21.101(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts21101rel7v700.pdf |
+
+### 10.1.2 TS 21.111 USIM and IC card requirements
+
+This document defines the requirements of the USIM (universal subscriber identity module) and the IC card for 3G (UICC). These are derived from the service and security requirements defined in 3G TS 22.100 and 3G TS 22.101. The USIM is a 3G application on an IC card. It inter-operates with a 3G terminal and provides access to 3G services. This document is intended to serve as a basis for the detailed specification of the USIM and the UICC, and the interface to the 3G terminal.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-21.111V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/21/A21111-700.pdf |
+| CCSA | CCSA-TSD-121 111 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 121 111 | 7.0.0 | Published | 2007-04-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0621111v700 |
+| ATIS | ATIS.3GPP.21.111V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-21.111(R7-7.0.0) | 7.0.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-21.111(R7-7.0.0).zip |
+
+## 10.2 22-series, Service aspects
+
+### 10.2.1 TS 22.001 Principles of circuit telecommunication services supported by a public land mobile network (PLMN)
+
+The document covers the definition of the circuit telecommunication services supported by a PLMN. The purpose of the document is to provide a method for the characterization and the description of these telecommunication services.
+
+TS 22.101 describes overall service principles of a PLMN.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.001V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22001-700.pdf |
+| CCSA | CCSA-TSD-122 001 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 001 | 7.0.0 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122001v700 |
+| ATIS | ATIS.3GPP.22.001V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.001(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.001(R7-7.0.0).zip |
+
+### 10.2.2 TS 22.002 Circuit bearer services (BS) supported by a public land mobile network (PLMN)
+
+The document defines a set of circuit bearer services to be provided to PLMN subscribers by a PLMN itself and in connection with other networks. This Technical Specification should also be used as a reference for defining the corresponding required mobile network capabilities.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.002V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22002-700.pdf |
+| CCSA | CCSA-TSD-122 002 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 002 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122002v700 |
+| ATIS | ATIS.3GPP.22.002 V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/seaarch.aspx |
+| TTA | TTAT.3G-22.002(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.002(R7-7.0.0).zip |
+
+### 10.2.3 TS 22.003 Circuit teleservices supported by a public land mobile network (PLMN)
+
+This Technical Specification (TS) describes and defines a recommended set of circuit teleservices to be supported by a PLMN in connection with other networks as a basis for defining the network capabilities required.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.003V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22003-700.pdf |
+| CCSA | CCSA-TSD-122 003 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 003 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122003v700 |
+| ATIS | ATIS.3GPP.22.003V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/seaarch.aspx |
+| TTA | TTAT.3G-22.003(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.003(R7-7.0.0).zip |
+
+### 10.2.4 TS 22.004 General on supplementary services
+
+The purpose of the document is to define a recommended set of supplementary services to the teleservices and bearer services, which will be supported by a PLMN in connection with other networks as a basis for the definition of the network capabilities, required.
+
+Supplementary services not covered in TS 22.004 cannot be introduced unilaterally in any PLMN if they require modification of the signalling specifications.
+
+Technical realization of supplementary services is described in TS 23.011 and 24.010.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 004 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 004 | 7.0.0 | Published | 2007-04-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122004v700 |
+| ATIS | ATIS.3GPP.22.004V 700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.004(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/sfnfile/TTAT.3G-22.004(R7-7.0.0).zip |
+| TTC | TS-3GA-22.004(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22004rel7v700.pdf |
+
+### 10.2.5 TS 22.011 Service accessibility
+
+The purpose of this Technical Specification is to describe the service access procedures as presented to the user.
+
+Definitions and procedures are provided in this Technical Specification for international roaming, national roaming and regionally provided service. These are mandatory in relation to the technical realization of the mobile station (UE).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 011 | 7.7.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 011 | 7.7.0 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122011v770 |
+| ATIS | ATIS.3GPP.22.011V 770-2007 | 7.7.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.011(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/sfnfile/TTAT.3G-22.011(R7-7.2.0).zip |
+| TTC | TS-3GA-22.011(Rel7)v7.7.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22011rel7v770.pdf |
+
+### 10.2.6 TS 22.016 International mobile station equipment identities (IMEI)
+
+The document defines the principal purpose and use of international mobile station equipment identities (IMEI).
+
+TS 23.003 describes the technical manner of numbering, addressing and identification.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.016V7.0.1 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22016-701.pdf |
+| CCSA | CCSA-TSD-122 016 | 7.0.1 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 016 | 7.0.1 | Published | 2007-06-21 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122016v701 |
+| ATIS | ATIS.3GPP.22.016V701-2007 | 7.0.1 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.016(R7-7.0.1) | 7.0.1 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/sntfile/TTAT.3G-22.016(R7-7.0.1).zip |
+
+### 10.2.7 TS 22.022 Personalization of mobile equipment (ME); Mobile functionality specification
+
+The document provides functional specifications of five features to personalize mobile equipment (ME) for GSM and 3G systems. These features are called:
+
+- Network personalization;
+- Network subset personalization;
+- Service provider (SP) personalization;
+- Corporate personalization;
+- SIM/USIM personalization (SIM for GSM systems or USIM for 3G systems).
+
+The document specifies requirements for MEs that provide these personalization features.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.022V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22022-700.pdf |
+| CCSA | CCSA-TSD-122 022 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 022 | 7.0.0 | Published | 2007-06-22 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0322022v700 |
+| ATIS | ATIS.3GPP.22.022V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.022(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/sntfile/TTAT.3G-22.022(R7-7.0.0).zip |
+
+### 10.2.8 TS 22.024 Description of charge advice information (CAI)
+
+The charging supplementary service is described in TS 22.086. These services are designed to supply to a mobile user sufficient information to allow a real-time estimate to be made of the bill that will eventually be levied in the home PLMN on the mobile station (MS) subscriber.
+
+In the case of certain MS uses, for example a mobile payphone, this estimate could be subject to further processing (e.g., to present the charges in currency, rather than units, this may include an additional mark up). This additional processing is not described in this document in order to avoid constraining the evolution of the MS product in this area.
+
+This document gives an overall view of how this supplementary service shall operate both in the PLMN and within the MS. Text given in this document is required to define functionality and is not intended to constrain implementation.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 024 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 024 | 7.0.0 | Published | 2007-07-05 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122024v700 |
+| ATIS | ATIS.3GPP.22.024V 700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.024(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/snf/TTAT.3G-22.024(R7-7.0.0).zip |
+| TTC | TS-3GA-22.024(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22024rel7v700.pdf |
+
+### 10.2.9 TS 22.030 Man-machine interface (MMI) of the user equipment (UE)
+
+The document defines the requirements for and gives guidelines on the MMI on the user equipment (UE). This includes the requirements of the user procedures for call control and supplementary service control, the requirements on the physical input media and the output, such as indications and displayed information.
+
+This document includes requirements only to UE connected to CS Domain. See TS 22.101 for overall service principles and TS 22.001 for circuit telecommunication services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.030V7.0.1 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22030-701.pdf |
+| CCSA | CCSA-TSD-122 030 | 7.0.1 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 030 | 7.0.1 | Published | 2006-01-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122030v701 |
+| ATIS | ATIS.3GPP.22.030V701-2007 | 7.0.1 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.030(R7-7.0.1) | 7.0.1 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/sfnfile/TTAT.3G-22.030(R7-7.0.1).zip |
+
+### 10.2.10 TS 22.031 Fraud information gathering system (FIGS); Service description; Stage 1
+
+This Technical Specification specifies the stage 1 description of the fraud information gathering system (FIGS) feature which provides the means for the HPLMN to monitor the activities of its subscribers in a VPLMN.
+
+The purpose of this network feature is to enable the HPLMN to monitor the activities of its subscribers while they are roaming. The VPLMN collects information about a defined set of activities on monitored subscribers and sends this information back to the HPLMN. This enables the HPLMN to clear certain types of calls and so stop fraudulent use of the GSM system.
+
+This specification enables service providers/network operators to use FIGS, and service limitation controls such as operator determined barring (ODB) and immediate service termination (IST), to limit their financial exposure to subscribers producing large unpaid bills.
+
+HPLMNs may also choose to monitor the activities of its subscribers within the HPLMN.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.031V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22031-700.pdf |
+| CCSA | CCSA-TSD-122 031 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 031 | 7.0.0 | Published | 2007-06-25 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0322031v700 |
+| ATIS | ATIS.3GPP.22.031V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.031(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/sfnfile/TTAT.3G-22.031(R7-7.0.0).zip |
+
+### 10.2.11 TS 22.032 Immediate service termination (IST); Service description; Stage 1
+
+The document specifies the Stage 1 description of the immediate service termination (IST) service which provides the means for the HPLMN to terminate all the activities of an HPLMN subscriber in a VPLMN.
+
+The purpose of this network feature is to enable the HPLMN to control the activities of its subscribers, particularly while they are roaming. If the HPLMN decides (based upon information received via fraud information gathering system (FIGS) or other systems) that a roaming subscriber is behaving in a fraudulent or suspicious manner, the HPLMN can terminate all activities of the subscriber, including calls (including transferred and diverted calls) that are in progress.
+
+This procedure can also be used to terminate all the activities of a subscriber when the subscription has ended.
+
+The primary aim is to enable service providers/network operators to use IST to reduce the amount of money that they lose because of roaming fraud.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.032V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22032-700.pdf |
+| CCSA | CCSA-TSD-122 032 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 032 | 7.0.0 | Published | 2007-06-22 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0322032v700 |
+| ATIS | ATIS.3GPP.22.032V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.032(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/sfnfile/TTAT.3G-22.032(R7-7.0.0).zip |
+
+### 10.2.12 TS 22.034 High speed circuit switched data (HSCSD); Stage 1
+
+The document specifies the Stage 1 description of high speed circuit switched data (HSCSD). HSCSD is a feature that introduces general bearer services and a multislot mechanism is used for user rates that can be achieved with one or more TCH/F. Multislot also defines a flexible use of air interface resources that makes efficient and flexible use of higher user rates feasible.
+
+The multislot mechanism is only applicable to GERAN.
+
+At UTRAN radio access parameters used for GBS user data are specified at TS 23.107.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.034V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22034-700.pdf |
+| CCSA | CCSA-TSD-122 034 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 034 | 7.0.0 | Published | 2007-07-05 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122034v700 |
+| ATIS | ATIS.3GPP.22.034V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.034(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/snf/file/TTAT.3G-22.034(R7-7.0.0).zip |
+
+### 10.2.13 TS 22.038 USIM application toolkit (USAT); Service description; Stage 1
+
+This technical specification defines the Stage 1 description of the USIM application toolkit (USAT). Stage 1 is an overall service description, primarily from the subscriber's and serving environment's points of view, and does not deal with the details of the human interface itself.
+
+This Technical Specification includes information applicable to network operators, serving environments and terminal, switch and database manufacturers.
+
+This technical specification contains the core requirements for a USIM application toolkit (USAT) that are sufficient to provide a complete service.
+
+It is highly desirable, however, that technical solutions for a USIM application toolkit (USAT) are sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in this technical specification may implement requirements that are considered outside the scope of this technical specification. This additional functionality may be on a network-wide basis, nationwide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service.
+
+As indicated in Figure 10.2.13-1, the scope of this technical specification encompasses the USAT functionality in the UE (comprising USIM and ME) and the interaction with the PLMN environment. The USAT server is not necessarily a separate entity as shown in the figure; nodes providing USAT services may also exist within the PLMN. The functionalities of the USAT servers (such as charging aspects, security level classification, etc.) are not covered by this specification.
+
+
+
+Q.1741.5(08)\_F10.2.13-1
+
+Diagram illustrating the scope of Technical Specification 22.038. It shows an ME (Mobile Equipment) connected to a PLMN (Packet Switched Network). The ME contains GSM/UMTS and SAT/USAT components, which are connected to a SIM/USIM. The PLMN is connected to SAT/USAT server(s). A dashed line indicates the 'Scope of this TS' covering the ME and the PLMN.
+
+**Figure 10.2.13-1 – Scope of Technical Specification 22.038**
+
+The requirements are considered to be applicable to both GSM and UMTS systems.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.038V7.5.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22038-750.pdf |
+| CCSA | CCSA-TSD-122 038 | 7.5.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 038 | 7.5.0 | Published | 2006-01-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122038v750 |
+| ATIS | ATIS.3GPP.22.038V750-2007 | 7.5.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.038(R7-7.5.0) | 7.5.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/sfnfile/TTAT.3G-22.038(R7-7.5.0).zip |
+
+### 10.2.14 TS 22.041 Operator determined barring (ODB)
+
+The document describes the network feature operator determined barring (ODB).
+
+This allows the network operator or service provider to regulate, by means of an exceptional procedure, access by the subscribers to services (both circuit and packet oriented), by the barring of certain categories of outgoing or incoming calls/packet oriented services or of roaming. ODB shall take effect immediately and shall terminate ongoing calls and bar future calls/packet oriented services.
+
+The purpose of this network feature is to be able to limit the service provider's financial exposure to new subscribers, or to those who have not promptly paid their bills. It may only be applied to the service provider's own subscribers.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 041 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 041 | 7.0.0 | Published | 2007-04-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122041v700 |
+| ATIS | ATIS.3GPP.22.041V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.041(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/sfnfile/TTAT.3G-22.041(R7-7.0.0).zip |
+| TTC | TS-3GA-22.041(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22041rel7v700.pdf |
+
+### 10.2.15 TS 22.042 Network identity and time zone (NITZ); Service description; Stage 1
+
+The document describes the feature network identity and time zone (NITZ).
+
+This feature provides the means for serving PLMNs to transfer current identity, time, daylight saving time and the local time zone to mobile stations (MS)s, and for the MSs to store and use this information. This enhances roaming by permitting accurate indication of PLMN identities that are either newer than the mobile equipment (ME) or have changed their name since the ME was sold. Additionally, time, daylight saving time, and time zone information can be utilized by MEs as desired.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 042 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 042 | 7.0.0 | Published | 2007-07-05 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122042v700 |
+| ATIS | ATIS.3GPP.22.042V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.042(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/sfnfile/TTAT.3G-22.042(R7-7.0.0).zip |
+| TTC | TS-3GA-22.042(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22042rel7v700.pdf |
+
+### 10.2.16 TS 22.053 Tandem free operation (TFO); Service description; Stage 1
+
+The document specifies the stage 1 description for the tandem free operation (TFO) feature that provides the capability to avoid tandeming speech codecs in mobile-to-mobile speech calls. The primary aim is to realize improvements in speech quality. The TFO mode of operation could also be used to reduce inter-mobile service switching centre (MSC) transmission bandwidth requirements.
+
+In analogy with [ITU-T I.130], Stage 1 is an overall service description, from the service subscriber's and user's standpoints, that views the network as a single entity which provides services to the user.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.053V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22053-700.pdf |
+| CCSA | CCSA-TSD-122 053 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 053 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0422053v700 |
+| ATIS | ATIS.3GPP.22.053V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.053(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/sntfile/TTAT.3G-22.053(R7-7.0.0).zip |
+
+### 10.2.17 TS 22.057 Mobile execution environment (MExE); Service description; Stage 1
+
+MExE provides a standardized execution environment in an UE, and an ability to negotiate its supported capabilities with a MExE service provider, allowing applications to be developed independently of any UE platform. The UE (consisting of the ME and SIM/USIM) can then be targeted at a range of implementations for MExE from small devices with low bandwidth, limited displays, low processor speeds, limited memory, MMI, etc., to sophisticated devices with a complete MExE execution environment.
+
+This Technical Specification defines the Stage 1 description of the mobile execution environment (MExE). Stage 1 is an overall service description, primarily from the subscriber's and service providers' points of view, and does not deal with the details of the human interface itself.
+
+This Technical Specification includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
+
+This Technical Specification contains the core requirements for a mobile execution environment (MExE) that is sufficient to provide a complete service.
+
+It is highly desirable, however, that technical solutions for a mobile execution environment (MExE) be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in this Technical Specification may implement requirements that are considered outside the scope of this Technical Specification. This additional functionality may be on a network-wide basis, nationwide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service.
+
+As indicated in Figure 10.2.17-1, the scope of this Technical Specification encompasses the MExE functionality in the UE, interaction with the MExE service environment. The MExE service environment is not necessarily restricted to the PLMN, and nodes providing MExE services (i.e., MExE servers) may also exist outside the PLMN. Aspects of the support provided by MExE servers within the MExE service environment (such as charging aspects, security level classification, etc.) are covered by this specification, but not the MExE servers themselves.
+
+
+
+Diagram showing the scope of Technical Specification 22.057. A User Equipment (UE) box is connected to a cloud labeled 'MExE service environment'. An arrow labeled 'Scope of this TS' points from the cloud to the UE box. Below the diagram is the text 'Q.1741.5(08)\_F10.2.17-1'.
+
+**Figure 10.2.17-1 – Scope of Technical Specification 22.057**
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.057V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22057-700.pdf |
+| CCSA | CCSA-TSD-122 057 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 057 | 7.0.0 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122057v700 |
+| ATIS | ATIS.3GPP.22.057V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.057(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/tnfile/TTAT.3G-22.057(R7-7.0.0).zip |
+
+### **10.2.18 TS 22.060 General packet radio service (GPRS); Service description; Stage 1**
+
+This Technical Specification defines the Stage 1 description of the general packet radio service (GPRS). Stage 1 is an overall service description, primarily from the service subscriber's and user's points of view, but does not deal with the details of the human interface itself. This Technical Specification includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
+
+This Technical Specification contains the core requirements for the packet-switched 3G networks that are sufficient to provide a complete service. It defines a set of bearer services that provide packet mode transmission within the PLMN and interwork with external networks.
+
+The term "GPRS" shall be used in this document to refer the GPRS service offered via GERAN and UTRAN and the PS Domain of the 3G PLMN.
+
+The GPRS shall not prevent the user's operation of other 3GPP services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 060 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 060 | 7.0.0 | Published | 2007-07-05 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122060v700 |
+| ATIS | ATIS.3GPP.22.060V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.060(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/sfnfile/TTAT.3G-22.060(R7-7.0.0).zip |
+| TTC | TS-3GA-22.060(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22060rel7v700.pdf |
+
+### 10.2.19 TS 22.066 Support of mobile number portability (MNP); Service description; Stage 1
+
+This Technical Specification defines the Stage 1 description of the support of mobile number portability between networks in the same country as well as North America cross-sector portability (i.e., number portability between fixed and 3GPP system). Stage 1 is an overall service description, primarily from the service subscriber's and user's points of view, but does not deal with the details of the human interface itself.
+
+Mobile number portability (MNP) is applicable only to those telecommunication services identified by an MSISDN.
+
+This specification includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
+
+This specification contains the core requirements for the support of mobile number portability between network operators in the same country as well as North America cross-sector portability that are sufficient to provide a complete service.
+
+Other cross-sector portability options (e.g., number portability between fixed and mobile networks outside the North American region) are outside the scope of this Technical Specification. It is highly desirable, however, that technical solutions for MNP should be sufficiently flexible to allow for possible enhancements, e.g., cross-sector number portability, and MNP between analogue and digital mobile networks. Additional functionalities not documented in this specification may implement requirements that are considered outside the scope of this specification. This additional functionality may be on a network-wide basis, nationwide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service.
+
+Porting between service providers (i.e., service provider portability) that does not involve a change of network operator is outside the scope of this specification.
+
+The relationship between service providers and network operators is outside the scope of this specification.
+
+The relationship between a service provider and subscriber is outside the scope of this specification. The interface between the user equipment (UE) and any external applications are outside the scope of this specification. Charging principles are outside the scope of this specification, except where explicitly stated in the text.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 066 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 066 | 7.0.0 | Published | 2007-07-05 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122066v700 |
+| ATIS | ATIS.3GPP.22.066V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.066(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.066(R7-7.0.0).zip |
+| TTC | TS-3GA-22.066(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22066rel7v700.pdf |
+
+### 10.2.20 TS 22.067 Enhanced multi-level precedence and pre-emption service (eMLPP); Stage 1
+
+The document specifies the Stage 1 description of the enhanced multi-level precedence and pre-emption service (eMLPP). This service has two parts: precedence and pre-emption. Precedence involves assigning a priority level to a call in combination with fast call set-up. Pre-emption involves the seizing of resources, which are in use by a call of a lower precedence, by a higher-level precedence call in the absence of idle resources. Pre-emption can also involve the disconnection of an ongoing call of lower precedence to accept an incoming call of higher precedence.
+
+The eMLPP service is provided as a network operator's option to a domain of a network. The domain can be the whole network or a subset of the network. The eMLPP service applies to all network resources in the domain that is in common use. The eMLPP service is applicable to all mobile stations in the domain with all or some mobile stations having a respective subscription assigning precedence according to the eMLPP service.
+
+eMLPP is a supplementary service and shall be provided to a subscriber for all basic services subscribed to and for which eMLPP applies.
+
+The service is described from the service subscriber's and user's point of view, in particular:
+
+- the procedure for normal operation with successful outcome;
+- the action to be taken in exceptional circumstances;
+- the interaction with other services and features.
+
+The document does not deal with the man-machine interface (MMI) requirements, but makes reference to the appropriate specifications.
+
+The document is applicable to teleservices 1x and 6x and to all bearer services used in a mobile network if eMLPP is provided.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.067V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22067-700.pdf |
+| CCSA | CCSA-TSD-122 067 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 067 | 7.0.0 | Published | 2007-04-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122067v700 |
+| ATIS | ATIS.3GPP.22.067V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.067(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.067(R7-7.0.0).zip |
+
+### 10.2.21 TS 22.071 Location services (LCS); Service description; Stage 1
+
+This document provides the Stage 1 description of location services (LCS). A Stage 1 description provides an overall service description, primarily from the service subscriber's and user's points of view, but not dealing with the details of the man-machine interface (MMI). This Technical Specification includes information applicable to network operators, service providers and terminal, base station system, switch, and database manufacturers.
+
+NOTE – Location services may be considered as a network-provided enabling technology consisting of standardized service capabilities that enable the provision of location-based applications. These applications may be service provider specific. The description of the numerous and varied possible location applications which are enabled by this technology are outside the scope of this specification. However, clarifying examples of how the functionality being specified may be used to provide specific location services is included in various clauses of the specification.
+
+This document provides core requirements to an extent sufficient to derive a complete definition of location services at the service level. However, this document also provides additional requirements that may suggest in a non-normative manner certain ways the system may be implemented to support location services.
+
+LCS can be offered without subscription to basic telecommunication services. LCS is available to the following categories of LCS clients:
+
+- Value-added services LCS clients – Use LCS to support various value-added services. These clients can include UE subscribers as well as non-subscribers to other services.
+- PLMN operator LCS clients – Use LCS to enhance or support certain O&M related tasks, supplementary services, IN-related services and bearer services and teleservices.
+- Emergency services LCS clients – Use LCS to enhance support for emergency calls from subscribers.
+- Lawful intercept LCS clients – Use LCS to support various legally required or sanctioned services.
+
+LCS is applicable to any target UE whether or not the UE supports LCS, but with restrictions on the choice of the positioning method or notification of a location request to the UE user when the LCS or the individual positioning methods, respectively, are not supported by the UE.
+
+LCS is being developed in phases with enhancements added in yearly releases.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.071V7.4.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22071-740.pdf |
+| CCSA | CCSA-TSD-122 071 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 071 | 7.4.0 | Published | 2006-01-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122071v740 |
+| ATIS | ATIS.3GPP.22.071V740-2007 | 7.4.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.071(R7-7.3.0) | 7.3.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-22.071(R7-7.3.0).zip |
+
+### 10.2.22 TS 22.072 Call deflection service description; Stage 1
+
+Call deflection (CD) enables the served mobile subscriber to respond to an incoming call offered by the network by requesting redirection of this call to another number specified in the response. The CD supplementary service can only be invoked before the connection is established by the served mobile subscriber, i.e., in response to the offered call, or during the period that the served subscriber is being informed of the call. The served subscriber's ability to originate calls is unaffected by the CD supplementary service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 072 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 072 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122072v700 |
+| ATIS | ATIS.3GPP.22.072V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.072(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-22.072(R7-7.0.0).zip |
+| TTC | TS-3GA-22.072(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22072rel7v700.pdf |
+
+### 10.2.23 TS 22.076 Noise suppression for the AMR codec; Service description; Stage 1
+
+This document specifies the Stage 1 description for the noise suppression feature for the AMR codec that enhances the input speech signal corrupted by acoustic noise. In analogy with [ITU-T I.130], Stage 1 is an overall service description, from the service subscriber's and user's standpoints, that views the network as a single entity which provides services to the user.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.076V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22076-700.pdf |
+| CCSA | CCSA-TSD-122 076 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 076 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0422076v700 |
+| ATIS | ATIS.3GPP.22.076V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.076(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-22.076(R7-7.0.0).zip |
+
+### 10.2.24 TS 22.078 Customized applications for mobile network enhanced logic (CAMEL); Service description; Stage 1
+
+This standard specifies the Stage 1 description for the CAMEL feature (customized applications for mobile network enhanced logic) that provides the mechanisms to support services consistently independently of the serving network. The CAMEL features shall facilitate service control of operator specific services external from the serving PLMN. The CAMEL feature is a network feature and not a supplementary service. It is a tool to help the network operator to provide the subscribers with the operator specific services even when roaming outside the HPLMN.
+
+If an IPLMN or VPLMN supports CAMEL Phase 4, it shall also provide the functionality of all previous CAMEL phases.
+
+Phase 4 network signalling shall support interworking with CAMEL Phases 3 and 2.
+
+The CAMEL feature is applicable:
+
+- to mobile originated and mobile terminated call related activities;
+- to supplementary service invocations;
+- to SMS MO, to GPRS sessions and PDP contexts, to the control of HLR subscriber data, to the control of network signalling load.
+
+The mechanism described addresses especially the need for information exchange among the VPLMN, HPLMN and the CAMEL service environment (CSE) for support of such operator specific services. Any user procedures for operator specific services are outside the scope of this standard.
+
+This specification describes the interactions between the functions of the VPLMN, HPLMN, IPLMN and the CSE.
+
+The second phase of CAMEL enhances the capabilities of phase 1 where the following capabilities have been added:
+
+- Additional event detection points.
+- Interaction between a user and a service using announcements, voice prompting and information collection via in-band interaction or USSD interaction.
+- Control of call duration and transfer of advice of charge information to the mobile station.
+- The CSE can be informed about the invocation of the supplementary services ECT, CD and MPTY.
+
+- For easier post-processing, charging information from a serving node can be integrated in normal call records.
+
+The third phase of CAMEL enhances the capabilities of phase 2. The following capabilities are added:
+
+- Support of facilities to avoid overload.
+- Capabilities to support dialled services.
+- Capabilities to handle mobility events, such as (Not-)reachability and roaming.
+- Control of GPRS sessions and PDP contexts.
+- Control of mobile originating SMS through both circuit-switched and packet-switched serving network entities.
+- Interworking with SoLSA (support of localized service area). Support for this interworking is optional.
+- The CSE can be informed about the invocation of the supplementary service CCBS.
+
+Detailed information is given in the respective clauses.
+
+The fourth phase of CAMEL enhances the capabilities of phase 3. The following capabilities are added:
+
+- CAMEL support for optimal routing of circuit-switched mobile-to-mobile calls.
+- The capability for the CSE to create additional parties in an existing call.
+- The capability for the CSE to create a new call unrelated to any other existing call.
+- Capabilities for the enhanced handling of call party connections.
+- The capability for the CSE to control sessions in the IP multimedia subsystem.
+- Enhanced CSE capability for dialled services.
+- The capability to report basic service changes during ongoing call.
+
+With CAMEL Phase 4, it is possible that only a limited subset of the new functionalities is supported, in addition to the complete support of CAMEL Phase 3.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 078 | 7.6.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 078 | 7.6.0 | Published | 2006-01-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122078v760 |
+| ATIS | ATIS.3GPP.22.078V760-2007 | 7.6.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.078(R7-7.5.0) | 7.5.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.078(R7-7.5.0).zip |
+| TTC | TS-3GA-22.078(Rel7)v7.6.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22078rel7v760.pdf |
+
+### 10.2.25 TS 22.079 Support of optimal routing (SOR); Stage 1
+
+This Stage 1 description of the first phase of support of optimal routing (SOR):
+
+- compiles the basic service requirements for SOR;
+
+- describes the interactions for supplementary services (SS) in order to cater for SOR;
+- refers to modifications to network features required by SOR.
+
+This specification does not address the following:
+
+- There is no need for optimization of the routing of calls originally directed to a fixed network subscriber, because the physical address of a fixed network terminating line cannot differ from its logical address.
+- SOR in non-PLMNs is not a subject of this Technical Specification, but might be possible by bilateral arrangement between PLMN operators and those non-PLMN operators.
+
+The purpose of SOR is to reduce the number of unnecessary inter-PLMN call legs.
+
+The first phase of SOR applies to:
+
+- Optimal routing for the benefit of the B party, i.e., mobile terminated calls with late call forwarding to the home or visited country (scenarios 1 and 2),
+
+and optionally:
+
+- Optimal routing for the benefit of the A party, e.g., mobile-to-mobile calls where both mobile subscribers are in the same country (scenarios 3 to 10).
+
+The complete set of scenarios included in the phase 1 of optimal routing is presented in the paragraph for normal procedures. All other scenarios are excluded from Phase 1 of optimal routing.
+
+Note that optimal routing is applicable to national roaming situations, that is to calls directed to a mobile subscriber roaming in his or her home country, but registered in a PLMN different from his or her HPLMN.
+
+All further call scenarios, including multiple call forwarding, are left to subsequent phases of SOR. Subsequent phases of SOR shall be backwards compatible with this first phase.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 079 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 079 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122079v700 |
+| ATIS | ATIS.3GPP.22.079V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.079(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.079(R7-7.0.0).zip |
+| TTC | TS-3GA-22.079(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22079rel7v700.pdf |
+
+### 10.2.26 TS 22.081 Line identification supplementary services; Stage 1
+
+The document describes the supplementary services belonging to the group line identification supplementary services.
+
+The general aspects, including definitions and recommended provision, of the description of the supplementary services are given in TS 22.004.
+
+The group of line identification supplementary services is divided into the following four supplementary services:
+
+- CLIP Calling line identification presentation;
+- CLIR Calling line identification restriction;
+- COLP Connected line identification presentation;
+- COLR Connected line identification restriction.
+
+**Definition of line identity:** The line identity is made up of a number of information units:
+
+- The subscriber's national ISDN/MSISDN number (MSISDN number is the number stored in the VLR).
+- The country code.
+- Optionally, subaddress information. The PLMN cannot be responsible for the content of this subaddress. (For definition of the subaddress, see [ITU-T E.164]).
+- In a full ISDN environment, the line identity shall include all the address information necessary to unambiguously identify a subscriber.
+- The calling line identity is the line identity of the calling party.
+- The connected line identity is the line identity of the connected party.
+
+If for the line identity of the calling party or the connected party, additional line identification is received (additional calling party/connected party number) in a PLMN this additional line identification shall be used for the presentation purpose of the line identification presentation services.
+
+**Definition of presentation and screening indicators:** In addition to or instead of the line identity, the network may give a presentation indicator (PI) and/or a screening indicator (SI) to the served subscriber. The following information may be given:
+
+- Presentation indicator showing:
+ - a) presentation allowed; or
+ - b) presentation restricted; or
+ - c) number not available due to interworking.
+
+If presentation indicator is set to "Presentation Restricted", then the MS can get additional information on the cause of no CLI, if provided by the network.
+
+The cause of no CLI value may be one of the following:
+
+- unavailable;
+- reject by user;
+- interaction with other services;
+- coin line/pay phone;
+- Screening indicator showing:
+ - a) user provided, verified and passed; or
+ - b) user provided, not screened; or
+ - c) network provided.
+
+If the line identity is that of a PLMN subscriber, then:
+
+- the national number and the country code shall always be provided by the network;
+- the subaddress shall only be included if it is provided by the user (or user equipment);
+- the screening indicator shall indicate "network provided".
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 081 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 081 | 7.0.0 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122081v700 |
+| ATIS | ATIS.3GPP.22.081V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.081(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-22.081(R7-7.0.0).zip |
+| TTC | TS-3GA-22.081(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22081rel7v700.pdf |
+
+### 10.2.27 TS 22.082 Call forwarding (CF) supplementary services; Stage 1
+
+This specification describes the supplementary services belonging to the group CALL OFFERING SUPPLEMENTARY SERVICES.
+
+The general aspects, including definitions and recommended provision, of the description of the supplementary services are given in Specification TS 22.004.
+
+The group of supplementary services CALL OFFERING SUPPLEMENTARY SERVICES is divided into four different supplementary services:
+
+- call forwarding unconditional;
+- call forwarding on mobile subscriber busy;
+- call forwarding on no reply;
+- call forwarding on mobile subscriber not reachable.
+
+##### Indication of active call forwarding supplementary service
+
+An indication that a call forwarding service is currently active and operative on a number will be given to the forwarding party each time an outgoing call is made. There will be one indication for unconditional call forwarding and another common indication for the conditional call forwarding services.
+
+##### Note on the use of the forwarded-to number at registration
+
+If the forwarded-to number is a number in the HPLMN country, it may be entered by the served mobile subscriber in three different formats, independent of his or her actual location, according to the schemes:
+
+- 1) National (significant) number.
+- 2) National (trunk) prefix plus national (significant) number.
+- 3) International prefix\*, country code, national (significant) number.
+
+Scheme 3) Storage of numbers in this format is mandatory for all PLMN operators.
+
+If the forwarded-to number is a number in a country other than the HPLMN country, it shall be entered by the served mobile subscriber, independent of his or her actual location, according to the following scheme:
+
+- International prefix (Note), country code, national (significant) number.
+
+NOTE – The MMI for entering of international prefix is defined in TS 22.030.
+
+The maximum forwarded-to number length is 28 digits.
+
+##### **Principles for interaction with the barring of outgoing calls supplementary services**
+
+Numbers allowed to call according to the barring of outgoing call service condition are allowed as forwarded-to numbers for the served mobile subscriber.
+
+Numbers not allowed to call according to the barring of outgoing call service condition are not allowed as forwarded-to numbers for the served mobile subscriber.
+
+For unconditional call forwarding, the forwarded leg is treated as an outgoing call from the HPLMN country.
+
+For the conditional call forwarding services, the forwarded leg is treated as an outgoing call from the LPLMN (HPLMN or VPLMN) country.
+
+##### **Principles for interaction with the barring of incoming calls supplementary services**
+
+When barring of all incoming calls is active for the served mobile subscriber – no call forwarding services are allowed.
+
+When barring of all incoming calls when roaming outside the HPLMN country is active and operative – i.e., the served mobile subscriber is roaming outside the HPLMN country, the conditional call forwarding services are not allowed.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|-----------------------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 082 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 082 | 7.0.0 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TS/SGS-0122082v700 |
+| ATIS | ATIS.3GPP.22.082V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.082(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdnfile/TTAT.3G-22.082(R7-7.0.0).zip |
+| TTC | TS-3GA-22.082(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22082rel7v700.pdf |
+
+### **10.2.28 TS 22.083 Call waiting (CW) and call hold (HOLD) supplementary services; Stage 1**
+
+The document describes the supplementary services belonging to the group call completion supplementary services.
+
+The general aspects, including definitions and recommended provision, of the description of supplementary services are given in TS 22.004.
+
+The group of call completion supplementary services is divided into the following two supplementary services:
+
+- Call waiting;
+- Call hold.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 083 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 083 | 7.0.0 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TS/SGS-0122083v700 |
+| ATIS | ATIS.3GPP.22.083V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.083(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.083(R7-7.0.0).zip |
+| TTC | TS-3GA-22.083(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22083rel7v700.pdf |
+
+### 10.2.29 TS 22.084 Multi-party (MPTY) supplementary service; Stage 1
+
+The document describes the supplementary services belonging to the group multi-party supplementary services.
+
+The general aspects, including definitions and recommended provision, of the description of the supplementary services are given in TS 22.004.
+
+The group of multi-party supplementary services consists of one supplementary service:
+
+- Multi-party service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 084 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 084 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TS/SGS-0122084v700 |
+| ATIS | ATIS.3GPP.22.084V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.084(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.084(R7-7.0.0).zip |
+| TTC | TS-3GA-22.084(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22084rel7v700.pdf |
+
+### 10.2.30 TS 22.085 Closed user group (CUG) supplementary services; Stage 1
+
+The document describes the supplementary services belonging to the group community of interest supplementary services.
+
+The general aspects, including definitions and recommended provision, of the description of the supplementary services are given in TS 22.004.
+
+The group of community of interest supplementary services includes one supplementary service:
+
+- Closed user group.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 085 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 085 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122085v700 |
+| ATIS | ATIS.3GPP.22.085V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.085(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.085(R7-7.0.0).zip |
+| TTC | TS-3GA-22.085(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22085rel7v700.pdf |
+
+### 10.2.31 TS 22.086 Advice of charge (AoC) supplementary services; Stage 1
+
+The document describes the supplementary services belonging to the group charging supplementary services.
+
+The general aspects, including definitions and recommended provision, of the description of the supplementary services are given in TS 22.004.
+
+Charging services are the supplementary services associated with charging aspects. The group of supplementary services charging supplementary services comprises two services:
+
+- Advice of charge (Information);
+- Advice of charge (Charging).
+
+Advice of charge (AoC) supplementary services will use the charge advice information described in TS 22.024.
+
+In principle, the same type of mobile station (MS) can be used for both services of advice of charge (AoC), except where the application demands special features – e.g., the payment mechanism in a payphone.
+
+Only one of these services may be subscribed to at any one time.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 086 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 086 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122086v700 |
+| ATIS | ATIS.3GPP.22.086V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.086(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.086(R7-7.0.0).zip |
+| TTC | TS-3GA-22.086(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22086rel7v700.pdf |
+
+### 10.2.32 TS 22.087 User-to-user signalling (UUS); Stage 1
+
+The user-to-user signalling (UUS) supplementary service allows a mobile subscriber to send/receive a limited amount of information to/from another PLMN or ISDN subscriber over the signalling channel in association with a call to the other subscriber.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 087 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 087 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122087v700 |
+| ATIS | ATIS.3GPP.22.087V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.087(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.087(R7-7.0.0).zip |
+| TTC | TS-3GA-22.087(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22087rel7v700.pdf |
+
+### 10.2.33 TS 22.088 Call barring (CB) supplementary services; Stage 1
+
+The document describes the supplementary services belonging to the group call restriction supplementary services.
+
+The general aspects – including definitions and recommended provision – of the description of the supplementary services are given in TS 22.004.
+
+The call restriction supplementary services allow the possibility for a mobile subscriber to have barring of certain categories of outgoing or incoming calls at the mobile subscribers access.
+
+The group of call restriction services includes two supplementary services:
+
+- barring of outgoing calls;
+- barring of incoming calls.
+
+By use of subscription options, the mobile subscriber can at provision time select a set of one or more barring programs to determine the categories of calls to be barred. The following categories are defined:
+
+- all outgoing calls;
+- outgoing international calls;
+- outgoing international calls except those directed to the home PLMN country;
+- all incoming calls;
+- incoming calls when roaming outside the home PLMN country.
+
+NOTE 1 – Each category (barring program) is handled as a single supplementary service.
+
+NOTE 2 – The call barring program "incoming calls when roaming outside the home PLMN country" is only relevant if, as a general rule, the called mobile subscriber pays the charges for the forwarded part of the call from his home PLMN country to any other country.
+
+The barring services can be offered to a mobile subscriber with a password option allowing the activation and deactivation by the subscriber. One password per mobile subscriber is supported by the network for all barring services. For the definition of the password, the description of its use and its management, see TS 22.004.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 088 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 088 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122088v700 |
+| ATIS | ATIS.3GPP.22.088V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.088(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.088(R7-7.0.0).zip |
+| TTC | TS-3GA-22.088(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22088rel7v700.pdf |
+
+### 10.2.34 TS 22.090 Unstructured supplementary service data (USSD); Stage 1
+
+The document defines the Stage 1 description of unstructured supplementary service data (USSD) for use in one or a number of public land mobile networks (PLMNs).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 090 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 090 | 7.0.0 | Published | 2006-09-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122090v700 |
+| ATIS | ATIS.3GPP.22.090V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.090(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.090(R7-7.0.0).zip |
+| TTC | TS-3GA-22.090(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22090rel7v700.pdf |
+
+### 10.2.35 TS 22.091 Explicit call transfer (ECT); Stage 1
+
+The document specifies the Stage 1 description of explicit call transfer (ECT) from the service subscriber's and user's points of view, in particular:
+
+- the procedures for normal operation with successful outcome;
+- the action to be taken in exceptional circumstances;
+- the interaction with other supplementary services.
+
+The document does not deal with the man-machine interface (MMI) requirements, but makes reference to the appropriate Technical Specifications.
+
+The charging principles applied to ECT are established in the document in terms of the charging information required to be collected. Any subsequent charging implications are outside of the scope of the document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 091 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 091 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122091v700 |
+| ATIS | ATIS.3GPP.22.091V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.091(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.091(R7-7.0.0).zip |
+| TTC | TS-3GA-22.091(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22091rel7v700.pdf |
+
+### 10.2.36 TS 22.093 Completion of calls to busy subscriber (CCBS); Service description; Stage 1
+
+The document specifies the Stage 1 description of completion of calls to busy subscriber (CCBS) from the subscriber's and user's points of view; in particular:
+
+- the procedures for normal operation with successful outcome;
+- the action to be taken in exceptional circumstances;
+- the interaction with other supplementary services;
+
+The document does not deal with the man-machine interface (MMI) requirements, but makes reference to the appropriate specifications.
+
+The charging principles applied to CCBS are outside of the scope of this specification.
+
+Any interactions with other networks not dealt with in the document are outside the scope of the document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 093 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 093 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122093v700 |
+| ATIS | ATIS.3GPP.22.093V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.093(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.093(R7-7.0.0).zip |
+| TTC | TS-3GA-22.093(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22093rel7v700.pdf |
+
+### 10.2.37 TS 22.094 Follow me service description; Stage 1
+
+The document specifies the Stage 1 description for the follow me feature.
+
+The follow me feature enables a mobile subscriber A to manipulate the follow me data of a party B in such a way that – under certain conditions – subsequent calls directed to party B will be forwarded to subscriber A.
+
+The feature is described from the service subscriber's and user's point of view, in particular:
+
+- the procedure for normal operation with successful outcome;
+- the action to be taken in exceptional circumstances;
+- the interaction with other GSM services and features.
+
+This Technical Specification does not deal with the man-machine interface (MMI) requirements, but makes reference to the appropriate specifications.
+
+Any interaction with other services and/or networks not dealt with in this specification is outside the scope of this Technical Specification.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 094 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 094 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122094v700 |
+| ATIS | ATIS.3GPP.22.094V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.094(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-22.094(R7-7.0.0).zip |
+| TTC | TS-3GA-22.094(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22094rel7v700.pdf |
+
+### 10.2.38 TS 22.096 Name identification supplementary service; Stage 1
+
+The document describes the supplementary services belonging to the group name identification supplementary services.
+
+The general aspects, including definitions and recommended provision, of the description of the supplementary services are given in TS 22.004.
+
+The group of name identification supplementary services is divided into the following supplementary services:
+
+- Calling name presentation (CNAP).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 096 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 096 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122096v700 |
+| ATIS | ATIS.3GPP.22.096V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.096(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-22.096(R7-7.0.0).zip |
+| TTC | TS-3GA-22.096(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22096rel7v700.pdf |
+
+### 10.2.39 TS 22.097 Multiple subscriber profile (MSP) Phase 1; Service description; Stage 1
+
+The document gives an overall view of how this service shall operate both in the PLMN and within the mobile station (MS). This Technical Specification defines functionality and is not intended to constrain implementation.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 097 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 097 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122097v700 |
+| ATIS | ATIS.3GPP.22.097V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.097(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.097(R7-7.0.0).zip |
+| TTC | TS-3GA-22.097(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22097rel7v700.pdf |
+
+### 10.2.40 TS 22.101 Service aspects; Service principles
+
+This Technical Specification (TS) describes the service principles for PLMNs. Principles and requirements for interworking with WLAN are covered in TS 22.234.
+
+3G specifications define integrated personal communications services. The system will support different applications ranging from narrow-band to wideband communications capability with integrated personal and terminal mobility to meet the user and service requirements of the 21st century.
+
+The specifications allow the realization of a new generation of mobile communications technology for a world in which personal communications services should allow person-to-person calling, independent of location, the terminal used, the means of transmission (wired or wireless) and the choice of technology. Personal communication services should be based on a combination of fixed and wireless/mobile services to form a seamless end-to-end service for the user.
+
+The specifications should be in compliance with the following objectives:
+
+- to provide a single integrated system in which the user can access services in an easy and uniform way to use in all environments;
+- to allow differentiation between service offerings of various serving networks and home environments;
+- to provide a wide range of telecommunication services including those provided by fixed networks and requiring user bit rates of up to 2 Mbit/s as well as services special to mobile communications. These services should be supported in residential, public and office environments and in areas of diverse population densities. These services are provided with a quality comparable with that provided by fixed networks such as ISDN;
+- to provide services via handheld, portable, vehicular-mounted, movable and fixed terminals (including those which normally operate connected to fixed networks), in all environments (in different service environments – residential, private domestic and different radio environments) provided that the terminal has the necessary capabilities;
+- to provide support of roaming users by enabling users to access services provided by their home environment in the same way even when roaming;
+
+- f) to provide audio, data, video and particularly multimedia services;
+- g) to provide for the flexible introduction of telecommunication services;
+- h) to provide within the residential environment the capability to enable a pedestrian user to access all services normally provided by fixed networks;
+- i) to provide within the office environment the capability to enable a pedestrian user to access all services normally provided by PBXs and LANs;
+- j) to provide a substitute for fixed networks in areas of diverse population densities, under conditions approved by the appropriate national or regional regulatory authority;
+- k) to provide support for interfaces which allow the use of terminals normally connected to fixed networks.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.101V7.9.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22101-790.pdf |
+| CCSA | CCSA-TSD-122 101 | 7.9.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 101 | 7.9.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122101v790 |
+| ATIS | ATIS.3GPP.22.101V790-2007 | 7.9.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.101(R7-7.3.0) | 7.3.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.101(R7-7.3.0).zip |
+
+### 10.2.41 TS 22.105 Services and service capabilities
+
+Existing systems have largely standardized the complete sets of bearer services, teleservices and supplementary services that they provide. 3G specifications specify service capabilities rather than services, allowing service differentiation and system continuity. This Technical Specification (TS) describes how and what kind of services the user has access to.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.105V7.1.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22105-710.pdf |
+| CCSA | CCSA-TSD-122 105 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 105 | 7.1.0 | Published | 2007-04-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122105v710 |
+| ATIS | ATIS.3GPP.22.105V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.105(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.105(R7-7.1.0).zip |
+
+### 10.2.42 TS 22.112 USAT interpreter; Stage 1
+
+This document specifies a system to make mobile operator services, based on USIM application toolkit (USAT) functionality and USIM-based security functionality, available to an Internet environment. This is achieved by specifying the necessary components and protocols for a secure narrow-band channel between the Internet application and an USAT interpreter on the USIM. The actual application could be developed using the application language of choice. Two types of applications interfaces are used as examples, i.e., mark-up language based on XML and remote procedure call (RPC).
+
+The interpreter and the secure narrow-band channel form a core platform to enable services like:
+
+- advanced security functionality, e.g., digital signatures in m-commerce applications;
+- value-added services based on position and roaming;
+- controlled activation and management of other applications, e.g., multimedia and payment type of applications.
+
+The secure narrow-band channel is achieved by specifying the following:
+
+- specific application and content-related functionalities of the interface between the application system and the USAT gateway;
+- specific functionalities and protocols of the interface between the USAT gateway and the USAT interpreter associated with a USIM, achieved by defining a low-level command set for interpretation by the USAT interpreter;
+- defined level of functionality available to the application server for the implementation of USIM-based services such as PKI, location services, push and broadcast services, event-based services, etc.
+
+This document does not specify any elements of the protocol stack between the application server and the USAT gateway, the mark-up language definition, and the transport protocols between the USAT gateway and the USAT interpreter.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.112V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22112-700.pdf |
+| CCSA | CCSA-TSD-122 112 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 112 | 7.0.0 | Published | 2007-06-22 | http://webapp.etsi.org/workprogram/Report_WorkItem.asp?WKI_ID=26515 |
+| ATIS | ATIS.3GPP.22.112V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.112V700-2007 | 7.0.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-22.112(R7-7.0.0).zip |
+
+### 10.2.43 TS 22.115 Service aspects; Charging and billing
+
+The document describes the service aspects of charging and billing of the 3GPP system.
+
+The document is not intended to duplicate existing standards or standards being developed by other groups on these topics, and will reference these where appropriate. The document will elaborate on
+
+the charging requirements described in the charging principles in TS 22.001 service principles. It will allow the generation of accurate charging information to be used in the commercial and contractual relationships between the parties concerned.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 115 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 115 | 7.1.0 | Published | 2007-10-12 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122115v710 |
+| ATIS | ATIS.3GPP.22.115V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.115(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.115(R7-7.1.0).zip |
+| TTC | TS-3GA-22.115(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22115rel7v710.pdf |
+
+### 10.2.44 TS 22.127 Service requirement for the open services access (OSA); Stage 1
+
+This document specifies the Stage 1 requirements for realization of an open service access (OSA).
+
+OSA enables applications to make use of network functionality through an open standardized interface (the OSA API). OSA provides the glue between applications and network functionality. In this way applications implementing the services become independent from the underlying network technology.
+
+Applications that make use of network functionality offered through the OSA interface are not standardized.
+
+OSA is one toolkit, amongst others, that enables certain aspects of the requirements of the virtual home environment (VHE) concept to be realized.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 127 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 127 | 7.1.0 | Published | 2006-04-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122127v710 |
+| ATIS | ATIS.3GPP.22.127V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.127(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.127(R7-7.1.0).zip |
+| TTC | TS-3GA-22.127(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22127rel7v710.pdf |
+
+### 10.2.45 TS 22.129 Handover requirements between UTRAN and GERAN or other radio systems
+
+The scope of this document includes service requirements for handover maintaining continuity of service to a wireless terminal as it moves between the radio coverage area, or "cells", associated with different base station sites. This functionality is called "handover". Handover can also occur due to change of radio resource providing a service without necessarily any change of the base stations involved. In particular, when the radio resources providing a service change from one of the UTRA radio access modes to the other (UTRA-FDD and UTRA-TDD), this is regarded as handover. Particular emphasis has been placed on the description of requirements for service continuity within UTRAN and between UTRAN and GERAN, but requirements specific to other systems are incorporated as required.
+
+It is a key requirement to allow for dual or multimode terminals to hand over traffic from UTRAN to other radio systems such as GERAN and vice versa. This document describes the service requirements for intra- and inter-system handover.
+
+The following subject areas are within the scope of these service requirements:
+
+- User perceived performance that may be influenced by handover;
+- Operational requirements relating to handover;
+- Security requirements.
+
+The requirements set forth in this document are service requirements, in that they fulfil the following:
+
+- The requirements are independent of the implementation of the UTRAN.
+- The extent to which the requirements are met are in principle verifiable using observable that are not internal to the UTRAN.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 129 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 129 | 7.0.0 | Published | 2007-04-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122129v700 |
+| ATIS | ATIS.3GPP.22.129V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.129(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.129(R7-7.0.0).zip |
+| TTC | TS-3GA-22.129(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22129rel7v700.pdf |
+
+### 10.2.46 TS 22.135 Multicall; Service description; Stage 1
+
+The document describes multicall supplementary service.
+
+The general aspects, including definitions and recommended provision, of the description of supplementary services are given in TS 22.004.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 135 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 135 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122135v700 |
+| ATIS | ATIS.3GPP.22.135V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.135(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.135(R7-7.0.0).zip |
+| TTC | TS-3GA-22.135(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22135rel7v700.pdf |
+
+### 10.2.47 TS 22.140 Multimedia messaging service (MMS); Stage 1
+
+This Technical Specification defines the Stage 1 description of the non real-time multimedia messaging service (MMS). Stage 1 is the set of requirements which shall be supported for the provision of non real-time multimedia messaging service, seen primarily from the subscriber's and service providers' points of view.
+
+This Technical Specification includes information applicable to network operators, service providers, terminal and network manufacturers.
+
+This Technical Specification contains the core requirements for the multimedia messaging service, which is sufficient to provide a complete service.
+
+This TS defines the requirements for MMS to be understood as a framework to enable non real-time transmissions for different types of media including such functionality as:
+
+- multiple media elements per single message;
+- individual handling of message elements;
+- different delivery methods for each message element;
+- negotiating different terminal and network MM capabilities;
+- notification and acknowledgement of MM related events (e.g., delivery, deletion, etc.);
+- handling of undeliverable MM;
+- personalized MMS configuration;
+- flexible charging.
+
+The above list is not exhaustive.
+
+Thus, the MMS enables a unified application that integrates the composition, storage, access, and delivery of different kinds of media, e.g., text, voice, image or video in combination with additional mobile requirements.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.140V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22140-700.pdf |
+| CCSA | CCSA-TSD-122 140 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 140 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122140v700 |
+| ATIS | ATIS.3GPP.22.140V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.140(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.140(R7-7.0.0).zip |
+
+### 10.2.48 TS 22.141 Presence service; Stage 1
+
+This TS defines the Stage 1 description for the presence service. Stage 1 is the set of requirements which shall be supported to enable the exploitation of the presence service, seen primarily from the users' and home environments' points of view.
+
+This TS includes information applicable to the home environment, device and network manufacturers which are sufficient to provide complete support of the presence service.
+
+Additional functionalities not documented in this TS are considered outside the scope of this TS. Such additional functionality may be on a network-wide basis, nationwide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the requirements of the presence service defined in this specification.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.141V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22141-700.pdf |
+| CCSA | CCSA-TSD-122 141 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 141 | 7.0.0 | Published | 2006-01-06 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122141v700 |
+| ATIS | ATIS.3GPP.22.141V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.141(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.141(R7-7.0.0).zip |
+
+### 10.2.49 TS 22.146 Multimedia broadcast/multicast service; Stage 1
+
+This Technical Specification defines the Stage 1 description of the broadcast and multicast services for the 3GPP System (UTRAN and GERAN). Stage 1 is the set of requirements which shall be supported for the provision of broadcast and multicast services, seen primarily from the subscriber's and service providers' points of view.
+
+This TS includes information applicable to network operators, content providers, and terminal and network manufacturers.
+
+This TS contains the core requirements for multicast and broadcast services, which are sufficient to provide a complete service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.146V7.2.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22146-720.pdf |
+| CCSA | CCSA-TSD-122 146 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 146 | 7.2.0 | Published | 2007-04-23 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122146v720 |
+| ATIS | ATIS.3GPP.22.146V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.146(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.146(R7-7.2.0).zip |
+
+### 10.2.50 TS 22.173 IP Multimedia core network subsystem (IMS) multimedia telephony service and supplementary services; Stage 1
+
+This Technical Specification defines the Stage 1 description of the IMS multimedia telephony service and the minimum set of capabilities required to secure multi-vendor and multi-operator inter-operability for multimedia telephony and related supplementary services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 173 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 173 | 7.4.0 | Published | 2007-10-16 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122173v740 |
+| ATIS | ATIS.3GPP.22.173V740-2007 | 7.4.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.173(R7-7.3.0) | 7.3.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.173(R7-7.3.0).zip |
+| TTC | TS-3GA-22.173(Rel7)v7.4.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22173rel7v740.pdf |
+
+### 10.2.51 TS 22.174 Push service; Service aspects; Stage 1
+
+This Technical Specification defines the Stage 1 description of the push service and is the set of requirements that shall be supported for the provision of push, seen primarily from the subscriber's, service providers' and delivery network points of view.
+
+This TS includes information applicable to network operators, service providers, terminal and network manufacturers. It is of use to manufacturers and organizations which have devices or machines benefiting by availability of push service.
+
+This TS contains the core requirements for the push service, for operator and external push initiators, which are sufficient to provide a complete service capability and service capability feature.
+
+This TS defines the requirements for the push service to enable delivery of push data, including such functionality as:
+
+- transfer of push data from a push initiator to a push recipient;
+- latency and priority classes;
+- definition of handling of undeliverable push data.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.174V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22174-700.pdf |
+| CCSA | CCSA-TSD-122 174 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 174 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122174v700 |
+| ATIS | ATIS.3GPP.22.174V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.174(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-22.174(R7-7.0.0).zip |
+
+### 10.2.52 TS 22.226 Global text telephony (GTT); Stage 1
+
+This Technical Specification defines the Stage 1 description of the global text telephone feature, (GTT). Stage 1 is the set of requirements which shall be supported for the provision of the real-time text conversation feature, seen primarily from the subscriber's and service providers' points of view.
+
+This TS includes information applicable to network operators, service providers, terminal and network manufacturers.
+
+This TS contains the core requirements for the global text telephony feature, which are sufficient to provide a complete feature to incorporate in conversational services.
+
+This TS defines the requirements for GTT to be understood as a framework to enable real-time transmission of text, for the purpose of a text-based or text-supported conversation between users. Text may be transported alone or in combination with other media in the session, especially video and voice.
+
+Thus, the GTT enables text conversation to be included in any mobile conversational service.
+
+Interworking with existing text telephony in PSTN, as well as emerging forms of standardized text conversation in all networks, is within the scope of this document. Interoperation with multimedia messaging services is also within scope of this feature.
+
+NOTE – The global text telephony feature may be enhanced due to, e.g., operator's or regulator's requirements; however, such additional functionality shall not compromise conformance to the core requirements documented in this TS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 226 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 226 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122226v700 |
+| ATIS | ATIS.3GPP.22.226V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.226(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.226(R7-7.0.0).zip |
+| TTC | TS-3GA-22.226(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22226rel7v700.pdf |
+
+### 10.2.53 TS 22.228 Service requirements for the Internet protocol (IP) multimedia core network subsystem; Stage 1
+
+This TS defines the service requirements from users' and operators' perspective for the support of IP multimedia applications.
+
+IP multimedia applications are supported by IP multimedia sessions in the IM CN subsystem. IP multimedia sessions use IP connectivity bearers (e.g., GPRS as a bearer). Examples of IP multimedia applications include speech communication, real-time multimedia applications, shared online whiteboards, etc.
+
+This TS, in general, does not standardize usage of IP multimedia applications, but instead identifies the requirements to enable their support.
+
+In order to align IP multimedia applications wherever possible with non-3GPP IP applications, the general approach is to adopt non-3GPP IP-based solutions.
+
+The existing legacy tele- and supplementary services shall not be re-standardized as IP multimedia applications, and multimedia equivalent applications may be created with toolkits.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.228V7.6.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22228-760.pdf |
+| CCSA | CCSA-TSD-122 228 | 7.6.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 228 | 7.6.0 | Published | 2007-10-16 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122228v760 |
+| ATIS | ATIS.3GPP.22.228V760-2007 | 7.6.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.228(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.228(R7-7.2.0).zip |
+
+### **10.2.54 TS 22.233 Transparent end-to-end packet-switched streaming service; Stage 1**
+
+This Technical Specification defines the Stage 1 description of the packet-switched streaming service (PSS). Stage 1 is the set of requirements that shall be supported for the provision of a streaming service, seen primarily from the user's and service providers' points of view but also includes the service capabilities of the PSS itself.
+
+This TS includes information applicable to network operators, service providers, terminal and network manufacturers.
+
+This TS contains the core requirements for the packet-switched streaming service (PSS), which are sufficient to enable a range of services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|-----------------------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.233V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22233-700.pdf |
+| CCSA | CCSA-TSD-122 233 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 233 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122233v700 |
+| ATIS | ATIS.3GPP.22.233V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.233(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.233(R7-7.0.0).zip |
+
+### **10.2.55 TS 22.234 Requirements on 3GPP system to wireless local area network (WLAN) interworking**
+
+The present document specifies the functional requirements placed on the 3GPP system for interworking WLAN with the 3GPP system. Guidance is given for WLAN operators intending to provide the interworked WLAN capability.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|-----------------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 234 | 7.6.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 234 | 7.6.0 | Published | 2007-10-16 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122234v760 |
+| ATIS | ATIS.3GPP.22.234V760-2007 | 7.6.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.234(R7-7.3.0) | 7.3.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.234(R7-7.3.0).zip |
+| TTC | TS-3GA-22.234(Rel7)v7.6.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22234rel7v760.pdf |
+
+### 10.2.56 TS 22.242 Digital rights management (DRM); Stage 1
+
+The text in this specification has been removed. DRM specifications are elaborated in the open mobile alliance (OMA) according to an agreement between 3GPP and OMA.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.242V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22242-700.pdf |
+| CCSA | CCSA-TSD-122 242 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 242 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122242v700 |
+| ATIS | ATIS.3GPP.22.242V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.242(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.242(R7-7.0.0).zip |
+
+#### 10.2.57 TS 22.243 Speech recognition framework for automated voice services; Stage 1
+
+The present document defines the Stage 1 description of the speech recognition framework (SRF) for automated voice services. Stage 1 is the set of requirements for data seen primarily from the user's and service providers' points of view.
+
+This Technical Specification includes information applicable to network operators, service providers, terminal and network manufacturers.
+
+This Technical Specification contains the core requirements for the speech recognition framework for automated voice services.
+
+The scope of this Stage 1 is to identify the requirements for 3G networks to support the deployments of a speech recognition framework-based automated voice services, and therefore to introduce a 3GPP speech recognition framework as part of speech-enabled services. The speech recognition framework for automated voice services is an optional feature in a 3GPP system.
+
+Figure 1 positions the speech recognition framework (SRF) with respect to other speech-enabled services. As illustrated, SRF is designed to support server-side speech recognition over packet switched network (e.g., IMS). As such, SRF also enables configurations of multimodal and multi-device services that include distributing the speech engines.
+
+Note that it is possible to design speech-enabled services that alternate or combine the use of client-side only engines and SRF.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 243 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 243 | 7.0.0 | Published | 2007-07-25 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122243v700 |
+| ATIS | ATIS.3GPP.22.243V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.243(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.243(R7-7.0.0).zip |
+| TTC | TS-3GA-22.243(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22243rel7v700.pdf |
+
+### 10.2.58 TS 22.246 Multimedia broadcast/multicast service (MBMS) user services; Stage 1
+
+The present document describes MBMS user services that use the capabilities of MBMS. Application scenarios including charging, QoS aspects and related service requirements derived from them are described. These scenarios and service requirements can be used as guidance for the design of codecs and bearers for both UTRAN and GERAN.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.246V7.3.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/22/A22246-730.pdf |
+| CCSA | CCSA-TSD-122 246 | 7.3.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 246 | 7.3.0 | Published | 2007-07-05 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122246v730 |
+| ATIS | ATIS.3GPP.22.246V730-2007 | 7.3.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.246(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.246(R7-7.0.0).zip |
+
+### 10.2.59 TS 22.250 IP multimedia subsystem (IMS) group management; Stage 1
+
+The present document defines the Stage 1 description of the IMS group management. Stage 1 is the set of requirements which shall be supported for the provision of IMS group management, seen primarily from the subscribers' and service providers' points of view.
+
+The TS includes information applicable to network operator, service provider, terminal and network manufacturer.
+
+Additional functionalities not documented in the TS are considered outside the scope of this TS. Such additional functionality may be on a network-wide basis, nationwide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the requirements of the IMS group management defined in this specification.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 250 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 250 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0122250v700 |
+| ATIS | ATIS.3GPP.22.250V 700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.250(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.250(R7-7.0.0).zip |
+| TTC | TS-3GA-22.250(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22250rel7v700.pdf |
+
+### 10.2.60 TS 22.279 Combined circuit switched (CS) and IP multimedia subsystem (IMS) sessions; Stage 1
+
+This Technical Specification defines service requirements for combining CS and IMS services using a CS speech or CS multimedia call in association with an IMS session. The IMS session may consist of one or more IMS services.
+
+Requirements for the following capabilities are included:
+
+- Radio capability exchange.
+- Terminal capability exchange.
+- E.164 number exchange.
+- Adding IMS session to an ongoing CS call.
+- Adding a CS call to an ongoing IMS session.
+- Supplementary services as they relate to CSICS.
+
+It is intended that the capabilities defined herein for CSICS shall support interoperability between different operator networks, and roaming.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 279 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 279 | 7.1.0 | Published | 2006-01-26 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0122279v710 |
+| ATIS | ATIS.3GPP.22.279V 710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.279(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.279(R7-7.0.0).zip |
+| TTC | TS-3GA-22.279(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22279rel7v710.pdf |
+
+### 10.2.61 TS 22.340 IP multimedia system (IMS) messaging; Stage 1
+
+The present document specifies the Stage 1 description of the IMS messaging services. Stage 1 is an overall service description and defines service requirements, primarily from the subscriber's and service providers' points of view, and does not deal with the details of the human interface itself.
+
+The present TS includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
+
+The present TS contains the requirements for IMS messaging services, which are sufficient to provide a complete service. The messaging types identified in this document are: immediate messaging, session-based messaging and deferred delivery messaging.
+
+However, the requirements for the "deferred delivery messaging" type of IMS messaging are considered to be the same as for the multimedia messaging service (MMS) as described in 3G TS 22.140. Therefore, the present TS references TS 22.140 for a description of requirements of the "deferred delivery messaging" type of IMS messaging.
+
+It is highly desirable that technical solutions for IMS messaging services should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in this 3GPP TS may implement requirements which are considered outside the scope of this 3GPP TS. Such additional functionality shall not compromise conformance to the core requirements of the service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 340 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 122 340 | 7.0.0 | Published | 2006-01-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TS/SGS-0122340v700 |
+| ATIS | ATIS.3GPP.22.340V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-22.340(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-22.340(R7-7.0.0).zip |
+| TTC | TS-3GA-22.340(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts22340rel7v700.pdf |
+
+### 10.2.62 TR 22.903 Study on videotelephony teleservice
+
+This document analyses the introduction of additional functionalities for the videotelephony service in addition to what is provided in the 3GPP specifications up to Release 6. The functionalities will include but are not limited to codec negotiation, charging principles, supplementary services support. The approach followed is to evaluate how functionalities which are applicable to existing teleservices can be replicated for videotelephony.
+
+The document will analyse how the new functionalities will impact the backwards compatibility with the existing CS multimedia service, and will analyse whether it is beneficial to create a videotelephony teleservice.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 903 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 122 903 | 7.0.0 | Published | 2006-01-16 | http://pda.etsi.org/pda/home.asp?wkr=DTR/TSGS-0122903v700 |
+| ATIS | ATIS.3GPP.22.903V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TR-3GA-22.903(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr22903rel7v700.pdf |
+
+### 10.2.63 TR 22.934 Feasibility study on 3GPP system to wireless local area network (WLAN) interworking
+
+This document studies the feasibility of interworking between 3GPP systems and wireless local area networks (WLANs). This document identifies and describes:
+
+- scenarios for 3GPP – WLAN interworking;
+- 3GPP-WLAN interworking service requirements;
+- guidelines for standardization of 3GPP-WLAN interworking.
+
+The document includes a number of different scenarios of 3GPP-WLAN interworking ranging from common billing to the provision of services seamlessly between the WLAN and the 3GPP system. In addition, 3GPP-WLAN interworking feasibility study includes the analysis of a number of environments where both the 3GPP system and WLAN may be deployed. Finally, this report outlines some of the different WLAN technologies that may be interworked with 3GPP systems.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 934 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 122 934 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0122934v700 |
+| ATIS | ATIS.3GPP.22.934V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.2.64 TR 22.936 Multi-system terminals
+
+This document studies the behaviour of a multi-system terminal that supports both 3GPP and non-3GPP systems. Particular issues handled include, but are not restricted to:
+
+- Whether the system selection or PLMN selection should take higher priority in a multi-system terminal.
+- Criteria for system change.
+- Interaction between the user's and the operator's preferences.
+- Support of automatic and manual system selection mode.
+- Different methods of system selection and their impact on 3GPP specifications.
+- Some areas for possible standardization, to ensure 3GPP compliance and protection of 3GPP networks.
+
+The document treats non-3GPP networks in a generic way but it applies mainly to the case of 3GPP2/3GPP compliant terminals.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.936V7.1.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/22/A22936-710.pdf |
+| CCSA | CCSA-TSD-122 936 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 122 936 | 7.1.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=DTR/TSGS-0122936v710 |
+| ATIS | ATIS.3GPP.22.936V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.2.65 TR 22.940 IP multimedia subsystem (IMS) messaging
+
+The objective of this Technical Report is to:
+
+- describe use cases that illustrate the service requirements for IMS messaging;
+- derive the broad 3GPP requirements for IMS messaging services;
+- investigate the possible requirements for interworking with networks outside the 3GPP domain;
+- develop an analysis of the possible interaction between IMS messaging services and existing 3GPP messaging services (SMS, EMS and MMS) as well as other relevant 3GPP services such as presence IMS group management, etc.;
+- identify possible routes to standardization by:
+ - adopting existing and emerging standards, e.g., OMA, IETF;
+ - modifying and enhancing existing and emerging standards;
+ - developing of new standards.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 940 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 122 940 | 7.0.0 | Published | 2006-01-24 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0122940v700 |
+| ATIS | ATIS.3GPP.22.940V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TR-3GA-22.940(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr22940rel7v700.pdf |
+
+### 10.2.66 TR 22.944 Report on service requirements for UE functionality split
+
+This report identifies scenarios and requirements for UEs with functionality split over multiple devices. Scenarios that are required to be supported in the standard are defined in detail. The requirements in this report should enable interoperability between user equipment components from different vendors. This report is not intended to identify all possible or permitted functionality
+
+splits. Certain splits of functionality may be prohibited for security or other reasons. This report does not identify all prohibited scenarios.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.944V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/22/A22944-700.pdf |
+| CCSA | CCSA-TSD-122 944 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 122 944 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0122944v700 |
+| ATIS | ATIS.3GPP.22.944V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.2.67 TR 22.949 Study on a generalized privacy capability
+
+The present document aims to investigate and summarize the existing service requirements on privacy for 3GPP services. In order to ensure that these services and future 3GPP services will have a consistent set of rules that control the availability and usage of confidential information, it is the intention to identify a common way to handle privacy-related information in the network.
+
+Generic privacy requirements for the mobile industry are also being defined by the Open Mobile Alliance, and it is the intention of this document to present the existing requirements and any alternatives to achieving the required functionality within 3GPP networks.
+
+The scope of this study is to:
+
+- identify privacy-related information that is used in the 3GPP system;
+- identify the existing 3GPP services that handle privacy-related information;
+- identify the various stakeholders that handle, control or consume personal data, and to define their relationships;
+- document the definitions of the various functions, stakeholders and functions involved in a privacy capability;
+- identify the work being done by other organizations and the additional work to be done by 3GPP.
+
+The types of data subject to privacy rules within the scope of this study include:
+
+- privacy-related information specific to an individual user;
+- privacy-related information relating to entities such as corporations;
+- network data such as serving cell and broadcast area, e.g., data that relates to the user's location or presence in the network, and which could be used by applications to track the user.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.949V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/22/A22949-700.pdf |
+| CCSA | CCSA-TSD-122 949 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 122 949 | 7.0.0 | Published | 2007-07-05 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0122949v700 |
+| ATIS | ATIS.3GPP.22.949V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.2.68 TR 22.950 Priority service feasibility study
+
+This Technical Report (TR) presents the results of the feasibility study on priority service. The intent of this feasibility study is to assess the ability of 3GPP specifications to meet high-level requirements identified for priority service. This feasibility study consisted of a multi-step process, namely:
+
+- 1) Identify high-level requirements for priority service.
+- 2) Determine existing relevant 3GPP specifications for priority service.
+- 3) Perform a gap analysis to assess the ability of existing 3GPP specifications to meet the high-level priority service requirements.
+
+Additional functionalities not documented in this TR are considered outside the scope of this TR. Such additional functionality may be on a network-wide basis, nationwide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the requirements of the priority service defined in this specification.
+
+The priority service is intended to be utilized for both voice and data and therefore both elements are considered within the scope of this document. While priority service is meant for both voice and data services, the initial set of requirements address circuit-switched services (voice as well as data). Multimedia and non-circuit-switched aspects of priority service have not been addressed in this feasibility study and are for further study.
+
+The priority service is intended to interwork with external networks to provide an end-to-end service. Therefore, service interactions with external networks are considered within the scope of this document, although the specification of these interactions may be in other standards. If this occurs, a reference to that specification shall be made.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.950V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/22/A22950-700.pdf |
+| CCSA | CCSA-TSD- 122 950 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 122 950 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0122950v700 |
+| ATIS | ATIS.3GPP.22.950V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.2.69 TR 22.951 Service aspects and requirements for network sharing
+
+In the current dynamic market place, as a result of partnerships, acquisitions, creative agreements among operators, etc., the need for tools that enable various degrees of network sharing is becoming increasingly important.
+
+When GSM and then UMTS were specified, the possibility of sharing part or all of the network by two or more separated commercial entities was not considered, and as a result the standards lack some functionalities that enable the realization of such commercial agreements.
+
+GSM was designed under the principle "one operator, one radio access network". The GSM network has some possibilities of infrastructure sharing, but it does not support true radio access network sharing. The initial design of 3GPP system has followed the same principle.
+
+This technical report is aimed to capture the service and user requirements that must be fulfilled by the 3GPP system in order to enable network sharing in a standardized way. Section 5 describes various network sharing and includes various scenarios, e.g., spanning from common radio access network connected to multiple core networks, or multiple radio access networks sharing one core network. Section 6 contains a summary of the user classification and network identities. In section 7 the user requirements are described, while section 8 deals with the network operator requirements. Section 9 describes the mobility requirements in a shared network. The rest of the document covers security (section 10) and charging (section 11). Some conclusions can be found in section 12 and an annex with examples of practical realization of network sharing is provided.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD- 122 951 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 122 951 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0122951v700 |
+| ATIS | ATIS.3GPP.22.951V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TR-3GA-22.951(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr22951rel7v700.pdf |
+
+### 10.2.70 TR 22.952 Priority service guide
+
+This document addresses the service aspects (service description), network aspects (call flows), and management aspects (operations, administration, maintenance, and provisioning) of priority service, based on existing 3GPP specifications.
+
+The priority service is intended to be used for both voice and data. However, this document only addresses circuit-switched voice service. Data, multimedia and non-circuit-switched aspects of priority service have not been addressed and are for further study.
+
+The priority service is intended to interwork with external networks to provide an end-to-end service. Therefore, service interactions with external networks are considered within the scope of this document, although the specification of these interactions may be in another standard. If this occurs, a reference to that specification is made.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.952V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/22/A22952-700.pdf |
+| CCSA | CCSA-TSD- 122 952 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 122 952 | 7.0.0 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0122952v700 |
+| ATIS | ATIS.3GPP.22.952V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.2.71 TR 22.953 Multimedia priority service feasibility study
+
+This Technical Report (TR) presents the results of the feasibility study on multimedia priority service. The intent of this feasibility study is to assess the ability of 3GPP specifications to meet high-level requirements identified for multimedia priority service. This feasibility study consisted of a multi-step process, namely:
+
+- Identify high-level requirements for multimedia priority service.
+- Determine relevant 3GPP specifications for multimedia priority service.
+- Perform a gap analysis to assess the ability of existing 3GPP specifications to meet the high-level multimedia priority service requirements.
+
+Additional functionalities not documented in this TR are considered outside the scope of this TR. Such additional functionality may be on a network-wide basis, nationwide basis or particular to a group of users.
+
+The multimedia priority service is intended to be utilized for both voice and data in the packet-switched (PS) domain and the IP multimedia subsystem (IMS).
+
+The multimedia priority service is intended to interwork with external networks to provide an end-to-end service. Therefore, service interactions with external networks are considered within the scope of this document, although the specification of these interactions may be in other standards. If this occurs, a reference to that specification is made.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.953V7.1.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/22/A22953-710.pdf |
+| CCSA | CCSA-TSD-122 953 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 122 953 | 7.1.0 | Published | 2007-04-23 | http://pda.etsi.org/pda/home.asp?wkr=DTR/TSGS-0122953v710 |
+| ATIS | ATIS.3GPP.22.953V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.2.72 TR 22.967 Transferring of emergency call data
+
+This document examines the issues associated with the transmission of emergency call data from a vehicle to a public service access point (PSAP).
+
+Issues associated with the content of the emergency call data or the triggers of the emergency calls are outside the scope of this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.967V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/22/A22967-700.pdf |
+| CCSA | CCSA-TSD-122 967 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 122 967 | 7.0.0 | Published | 2006-09-21 | http://pda.etsi.org/pda/home.asp?wkr=DTR/TSGS-0122967v700 |
+| ATIS | ATIS.3GPP.22.967V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.2.73 TR 22.973 IMS multimedia telephony service and supplementary services
+
+This Technical Report defines the IMS multimedia telephony service and associated supplementary services for IMS. It aims to take account and build on the IMS capabilities already provided in 3GPP Release 5 and Release 6.
+
+The objective is to define the minimum set of capabilities required in the IP multimedia subsystem to secure multi-vendor and multi-operator inter-operability for the IMS multimedia telephony service and related supplementary services.
+
+While the user experience for the IMS multimedia telephony service is expected to have some similarity to existing telephony services, the richer capabilities of IMS will be exploited.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 973 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 122 973 | 7.0.0 | Published | 2007-04-23 | http://pda.etsi.org/pda/home.asp?wkr=DTR/TSGS-0122973v700 |
+| ATIS | ATIS.3GPP.22.973V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TR-3GA-22.973(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr22973rel7v700.pdf |
+
+### 10.2.74 TR 22.977 Feasibility study for speech-enabled services
+
+The advancement in the automatic speech recognition (ASR) technology, coupled with the rapid growth in the wireless telephony market has created a compelling need for speech-enabled services. Voice-activated dialling has become a *de facto* standard in many of the mobile phones in the market today. The speech recognition technology has also been applied more recently to voice messaging and personal access services. A voice eXtensible markup language (voice XML) has been designed to bring the full power of web development and content delivery to voice response applications. Voice portals that provide voice access to conventional graphically oriented services over the Internet are now becoming popular. Forecasts show that speech-driven services will play an important role on the 3G market. Users of mobile terminals want the ability to access information while on the move and the small portable mobile devices that will be used to access this information need improved user interfaces using speech input.
+
+A brief overview of the speech-enabled services is presented. The different ways of enabling speech recognition for the speech-enabled services are described. Section 6 discusses multimodal services and options to enable multimodal and multi-device services. The scope of the report, references, definitions and abbreviations are detailed in the first few sections.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-122 977 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 122 977 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0122977v700 |
+| ATIS | ATIS.3GPP.22.977V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+## 10.3 23-Series, Technical realization
+
+### 10.3.1 TS 23.002 Network architecture
+
+This document offers an overview of the PLMN and its architectures and configuration. The configuration and the functional entities of the PLMN and the interfaces between them are described on a general level in order to cope with possible implementations. These descriptions include interfaces between and within the core networks, the access networks, the user equipment, different service platforms, different domains and subsystems, and functional entities within domains and subsystems.
+
+This document covers different architectural aspects with varying level of detail. In general, other specifications shall be referred to for further details; these specifications enable the reader to acquire the full understanding of a system or service feature.
+
+Note that this document does not cover, or even list, all features of PLMNs.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 002 | 7.3.1 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 002 | 7.3.1 | Published | 2007-10-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223002v731 |
+| ATIS | ATIS.3GPP.23.002V731-2007 | 7.3.1 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.002(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.002(R7-7.2.0).zip |
+| TTC | TS-3GA-23.002(Rel7)v7.3.1 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23002rel7v730.pdf |
+
+### 10.3.2 TS 23.003 Numbering, addressing and identification
+
+The document defines the principal purpose and use of international mobile station equipment identities (IMEI) within the digital cellular telecommunications system and the 3G system.
+
+The document defines:
+
+- a) an identification plan for mobile subscribers in the GSM system;
+- b) principles of assigning telephone and ISDN numbers to MSs in the country of registration of the MS;
+- c) principles of assigning mobile station (MS) roaming numbers to visiting MSs;
+- d) an identification plan for location areas, routing areas, and base stations in the GSM system;
+- e) an identification plan for MSCs, SGSNs, GGSNs, and location registers in the GSM system;
+- f) principles of assigning international mobile equipment identities;
+- g) principles of assigning zones for regional subscription;
+- h) an identification plan for groups of subscribers to the voice group call service (VGCS) and to the voice broadcast service (VBS); and identification plan for voice group calls and voice broadcast calls; an identification plan for group call areas;
+- i) principles for assigning packet data protocol (PDP) addresses to mobile stations;
+- j) an identification plan for point-to-multipoint data transmission groups;
+- k) an identification plan for CN domain, RNC and service area in the UTRAN system;
+- l) an identification plan for mobile subscribers in the WLAN system.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 003 | 7.5.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 003 | 7.5.0 | Published | 2007-10-11 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423003v750 |
+| ATIS | ATIS.3GPP.23.003V750-2007 | 7.5.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.003(R7-7.5.0) | 7.5.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.003(R7-7.5.0).zip |
+| TTC | TS-3GA-23.003(Rel7)v7.5.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23003rel7v750.pdf |
+
+### 10.3.3 TS 23.007 Restoration procedures
+
+The data stored in location registers are automatically updated in normal operation; the main information stored in a location register defines the location of each mobile station and the subscriber data required to handle traffic for each mobile subscriber. The loss or corruption of these data will seriously degrade the service offered to mobile subscribers; it is therefore necessary to define procedures to limit the effects of failure of a location register, and to restore the location register data automatically. This document defines the necessary procedures.
+
+The basic principle is that restoration should be based on radio contact to avoid faulty data being spread in the system.
+
+Subscriber data for supplementary services must also be correctly restored, although the impact on service of corruption of supplementary service data is less severe.
+
+Procedures for supporting these functions are defined in 3G Technical Specifications 29.002 and 29.060.
+
+The MAP operation "IMSI Attach" is used only in MAP version 1; in MAP version 2 the same function is performed by the MAP operation "Update Location Area". References in this specification to IMSI attach apply only to MAP version 1 network entities.
+
+If the restoration of subscriber data in the VLR is triggered by Location Updating or IMSI Attach, the VLR retrieves subscriber data from the HLR by sending an "Update Location" request, which triggers one or more "Insert Subscriber Data" operations from the HLR. The "Update Location" request may also be used to send the LMSI to the HLR.
+
+If the restoration of subscriber data in the VLR is triggered by a "Provide Roaming Number" request, the behaviour of the VLR depends on whether it is implemented according to MAP version 1 or MAP version 2. For MAP version 2, the VLR retrieves subscriber data from the HLR by sending a "Restore Data" request, which triggers one or more "Insert Subscriber Data" operations from the HLR. The "Restore Data" request is also used to send the LMSI to the HLR. For MAP version 1, the VLR retrieves subscriber data from the HLR by sending a "Send Parameters" request with parameter type "Subscriber Data", which cannot be used to send the LMSI to the HLR.
+
+The VLR number and MSC number in the subscriber data in the HLR are updated by the "Update Location" procedure.
+
+The GGSN (gateway GPRS support node) is the point of PDN interconnection with the GSM PLMN supporting GPRS. The GGSN contains routing information for GPRS users with a PDP context active. The necessary procedures needed to restore GGSN data information after a restart is described in this document.
+
+The SGSN (serving GPRS support node) is the node that is serving the MS. The SGSN stores information regarding, e.g., mobility management, routing and security. The necessary procedures needed to restore this SGSN information after a restart are described in this document.
+
+A Type A LMU (location measurement unit) is a network node, accessed over the GSM air interface that is functionally similar to an MS. All requirements associated with a non-GPRS MS in this specification apply also to a Type A LMU, except where specified otherwise.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 007 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 007 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423007v700 |
+| ATIS | ATIS.3GPP.23.007V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.007(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.007(R7-7.0.0).zip |
+| TTC | TS-3GA-23.007(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23007rel7v700.pdf |
+
+### 10.3.4 TS 23.008 Organization of subscriber data
+
+The document provides details concerning information to be stored in home subscriber servers, visitor location registers, GPRS support nodes and call session control function (CSCF) concerning mobile subscriber.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 008 | 7.7.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 008 | 7.7.0 | Published | 2007-10-11 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423008v770 |
+| ATIS | ATIS.3GPP.23.008V770-2007 | 7.7.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.008(R7-7.6.0) | 7.6.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.008(R7-7.6.0).zip |
+| TTC | TS-3GA-23.008(Rel7)v7.7.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23008rel7v770.pdf |
+
+### 10.3.5 TS 23.009 Handover procedures
+
+The document contains a detailed description of the handover procedures to be used in PLMNs. The purpose of the handover procedures, as described in the document, are to ensure that the connection to the mobile station (MS) or user equipment (UE) is maintained as it moves from one cell or radio network to another. The document defines the circuit-switched handover functionality based on the service requirements in TS 22.129.
+
+The document considers the following four cases:
+
+- i) Handover between base stations connected to the same MSC: this is termed an "Intra-MSC handover";
+- ii) Handover between radio network subsystems connected to the same 3G\_MSC: this is termed an "Intra-3G\_MSC handover/relocation". This case also includes inter-system handover between RNS and BSS if the 3G\_MSC supports the A interface. In the context of this specification, the term "RNS" refers also to a BSS when serving a mobile station in Iu mode;
+- iii) Handover between base stations connected to different MSCs: this is termed an "Inter-MSC handover". This category can be sub-divided into three further procedures:
+ - a) the basic inter-MSC handover procedure, where the MS is handed over from a controlling MSC (MSC-A) to another MSC (MSC-B);
+ - b) the subsequent inter-MSC handover procedure, where the MS is handed over from MSC-B to a third MSC (MSC-B');
+ - c) the subsequent inter-MSC hand back, where the MS is handed back from MSC-B to MSC-A;
+- iv) Handover between radio network subsystems connected to different 3G\_MSCs: this is termed an "Inter-3G\_MSC handover/relocation". In the context of this specification, the term "RNS" also refers to a BSS when serving a mobile station in Iu mode. This category can be divided into three further sub-procedures:
+ - a) the inter-3G\_MSC handover procedure from UMTS to GSM, where the UE/MS is handed over from a controlling 3G\_MSC (3G\_MSC-A) to an MSC (MSC-B);
+ - b) the inter-3G\_MSC handover procedure from GSM to UMTS, where the UE/MS is handed over from a controlling MSC (MSC-A) to a 3G\_MSC (3G\_MSC-B);
+ - c) the inter-3G\_MSC relocation procedure, where the UE is relocated from 3G\_MSC-A to 3G\_MSC-B. This procedure can also be combined with a hard change of radio resources (hard handover with switch in the core network).
+
+The MSC in this category can optionally be a 3G\_MSC supporting the A interface. The three sub-procedures do also cover subsequent handover/relocation to a third MSC-B' or 3G\_MSC-B' and subsequent handover/relocation back to MSC-A or 3G\_MSC-A.
+
+In both cases i) and iii), the same procedures as defined in TS 48.008 and in TS 24.008 shall be used on the A interface and on the radio interface, respectively.
+
+In case ii), the same procedures as defined in TS 25.413 and in TS 24.008 shall be used on the Iu interface. If the 3G\_MSC in case ii) also supports the A interface, TS 08.08 and TS 24.008 shall be used on the A interface.
+
+In case iii), the handover procedures shall transport the A-interface messages between MSC-A and MSC-B described in the mobile application part (MAP), TS 29.002.
+
+In case iv), the handover procedures shall transport the A-interface messages between 3G\_MSC and MSC described in the mobile application part (MAP), TS 29.002.
+
+In case iv), the relocation procedure shall transport the Iu-interface messages between 3G\_MSC-A and 3G\_MSC-B described in the mobile application part (MAP), TS 29.002.
+
+The interworking between the TS 29.002 protocol and the TS 48.008 protocol is described in TS 29.010.
+
+Multicall supplementary service is not applicable in GERAN Iu mode, and relocation of multicalls is therefore only possible within UTRAN.
+
+Handovers which take place on the same MSC are termed "Intra-MSC handovers"; this includes both inter-BSS and intra-BSS handovers.
+
+Handovers which take place on the same 3G\_MSC are termed "Intra-3G\_MSC handovers"; this includes inter-RNS handovers and optionally RNS to BSS and BSS to RNS handovers.
+
+In the context of this specification, the term "InterSystem handover" can also refer to a handover which takes place between a base station serving a mobile station in Iu mode and a base station serving a mobile in A/Gb mode.
+
+*"Flexible Iu interface for handover/relocation" Option:* Up to release 99, an RNS can be connected only to one 3G\_MSC. From release 4 onwards, as a network option, an RNS can have Iu interfaces to more than one MSC. Such an additional Iu interface may be selected by an MSC during an intra-PLMN relocation or intra-PLMN BSS to RNS handover procedure. This allows the MSC to use an Intra-3G\_MSC handover procedure according to case ii) instead of an Inter-3G\_MSC handover procedure according to case iv). The decision whether to use the Intra-3G\_MSC handover procedure is implementation and configuration dependent. In a network implementing this option, a global title based on the global RNC-Id may optionally be used for the addressing of the Iu interface messages.
+
+*"Intra-domain connection of RAN nodes to multiple CN nodes" Option:* When applied, a BSS or an RNS can be connected to more than one MSC.
+
+The document also covers the requirements for handover in ongoing GSM voice group calls, directed retry and handover without a circuit connection between (U)MSCs. This document does not consider the case of handovers between radio channels on the same BSS (Intra-BSS handover) or the handover of packet radio services. The Inter-RNS handover case that results in a relocation is covered by this document but not other Inter-RNS or Intra-RNS handover cases.
+
+For voice broadcast calls in GSM, the speaker uses normal point-to-point handover procedures, whilst the listeners use idle mode cell reselection procedures for the voice group call listeners.
+
+Voice group calls are only applicable to GSM, and handover of voice group calls is therefore only possible in GSM.
+
+Inter-MSC handover imposes a few limitations on the system. After inter-MSC handover:
+
+- call re-establishment is not supported.
+
+The list of TS 48.008 features supported during and after Inter-MSC handover is given in TS 49.008.
+
+In the Inter-MSC handover case, the interworking between a Phase 1 BSSMAP protocol possibly used by one MSC and the Phase 2 BSSMAP protocol used in the Phase 2 MAP protocol on the E interface is performed by this MSC.
+
+This document also includes SDL diagrams and message flows.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 009 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 009 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0123009v700 |
+| ATIS | ATIS.3GPP.23.009V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.009(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.009(R7-7.0.0).zip |
+| TTC | TS-3GA-23.009(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23009rel7v700.pdf |
+
+### 10.3.6 TS 23.011 Technical realization of supplementary services – General aspects
+
+The document describes the general aspects on how supplementary services in the 3GPP system are realized from a technical point of view.
+
+Description of technical realization for specific supplementary services can be found in 3GPP TS 23.072, 230.8x and in the 230.9x-series Technical Specifications.
+
+All supplementary services may require signalling on the radio path. Signalling procedures and messages used are defined in the 3GPP TS 24.072 and in the 24.08x and 24.09x-series Technical Specifications.
+
+For some supplementary services, information needs to be transferred between the home location register (HLR), the visitor location register (VLR), the mobile services switching centre (MSC) and the serving GPRS support node (SGSN). Signalling procedures for such information transfer are defined in 3GPP TS 29.002.
+
+Definitions and descriptions of supplementary services are given in 3GPP TS 22.072 and in the 22.08x and 22.09x-series Technical Specifications.
+
+Definitions are given in 3G TS 22.004.
+
+NOTE – The Technical Specifications on the technical realization of supplementary services do not distinguish between subscriber, user and customer, since all three do not fully cover the textual needs. Generally, the term "subscriber" is used, even if this person does not have the subscription.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 011 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 011 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423011v700 |
+| ATIS | ATIS.3GPP.23.011V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.011(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.011(R7-7.0.0).zip |
+| TTC | TS-3GA-23.011(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23011rel7v700.pdf |
+
+### 10.3.7 TS 23.012 Location management procedures
+
+The document describes the location management procedures for the circuit-switched domain, with respect to the application level functional behaviour. This is to be distinguished from the corresponding protocol handling behaviour, which is specified in 3G TS 29.002. The following location management procedures are included:
+
+- Location updating;
+- Location cancellation;
+- MS purging;
+- IMSI attach/detach.
+
+The procedures in the mobile station (MS) are described in GSM 03.22. The procedures between MSC, VLR and HLR utilize the Mobile Application Part (MAP) and details concerning the protocol handling are contained in 3G TS 29.002.
+
+The document excludes location management procedures for the packet-switched domain, which are covered in 3G TS 23.060.
+
+The descriptions herein depict a logical separation between the MSC and VLR. This logical separation, as well as the messages transferred between the two logical entities are the basis of a model used to define the externally visible behaviour of the MSC/VLR, which may be a single physical entity. They do not impose any requirement except the definition of the externally visible behaviour.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 012 | 7.3.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 012 | 7.3.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423012v730 |
+| ATIS | ATIS.3GPP.23.012V730-2007 | 7.3.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.012(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.012(R7-7.1.0).zip |
+| TTC | TS-3GA-23.012(Rel7)v7.3.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23012rel7v730.pdf |
+
+### 10.3.8 TS 23.014 Support of dual tone multi frequency (DTMF) signalling
+
+The document describes how dual tone multi frequency (DTMF) signals are supported in the 3GPP system.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 014 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 014 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0123014v700 |
+| ATIS | ATIS.3GPP.23.014V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.014(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.014(R7-7.0.0).zip |
+| TTC | TS-3GA-23.014(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23014rel7v700.pdf |
+
+### 10.3.9 TS 23.015 Technical realization of operator determined barring (ODB)
+
+The network feature operator determined barring (ODB) allows a network operator or service provider to regulate access by subscribers to services (both circuit and packet oriented), by the barring of certain categories of incoming or outgoing calls/packet oriented services or of roaming. Operator determined barring applies to all bearer services and teleservices except the emergency call teleservice; the teleservice short message point-to-point is therefore subject to operator determined barring in the same way as circuit-switched calls.
+
+The application of specific categories of operator determined barring to a subscription is controlled by the network operator or service provider, using administrative interaction at the HLR; this interface is not standardized.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 015 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 015 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423015v700 |
+| ATIS | ATIS.3GPP.23.015V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.015(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-23.015(R7-7.0.0).zip |
+| TTC | TS-3GA-23.015(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23015rel7v700.pdf |
+
+### 10.3.10 TS 23.016 Subscriber data management; Stage 2
+
+This specification gives the Stage 2 description of the subscriber data management handling between:
+
+- the home location register (HLR) and the visitor location register (VLR);
+- the home location register (HLR) and the serving GPRS support node (SGSN).
+
+A number of procedures require updating of subscriber information:
+
+- Location updating;
+- Restoration;
+- Modification of data by the operator;
+- Modification of data by the subscriber via the mobile station (MS).
+
+Updating of subscriber information from HLR to SGSN is required in the following situations:
+
+- GPRS location updating;
+- Modification of data by the operator.
+
+Only the rules for the updating of subscriber data from the HLR to the VLR and from the HLR to the SGSN are described in this specification. Public land mobile network (PLMN) specific and unstructured supplementary service data (USSD) subscriber data are out of the scope of this specification. The GPRS context update from the SGSN to the GGSN is out of the scope of this specification.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 016 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 016 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423016v700 |
+| ATIS | ATIS.3GPP.23.016V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.016(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.016(R7-7.0.0).zip |
+| TTC | TS-3GA-23.016(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23016rel7v700.pdf |
+
+###### 10.3.11 TS 23.018 Basic call handling – Technical realization
+
+This Technical Specification (TS) specifies the technical realization of the handling of calls originated by a UMTS or GSM mobile subscriber and calls directed to a UMTS or GSM mobile subscriber, up to the point where the call is established. Normal release of the call after establishment is also specified.
+
+In this specification, the term "MS" is used to denote a UMTS or GSM MS, as appropriate.
+
+The handling of DTMF signalling and off-air call set-up (OACSU) is not described in this specification.
+
+The details of the effects of UMTS or GSM supplementary services on the handling of a call are described in the relevant 23.07x, 23.08x and 23.09x series of specifications.
+
+The specification of the handling of a request from the HLR for subscriber information is not part of basic call handling, but is required for both CAMEL (TS 23.078) and optimal routeing (TS 23.079). The use of the provide subscriber information message flow is shown in TS 23.078 and TS 23.079.
+
+The logical separation of the MSC and VLR, and the messages transferred between them are the basis of a model used to define the externally visible behaviour of the MSC/VLR, which is a single physical entity. They do not impose any requirement except the definition of the externally visible behaviour.
+
+If there is any conflict between this specification and the corresponding Stage 3 specifications (TS 24.008, TS 25.413, GSM 48.008 and TS 29.002), the Stage 3 specifications shall prevail.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 018 | 7.6.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 018 | 7.6.0 | Published | 2007-10-08 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423018v760 |
+| ATIS | ATIS.3GPP.23.018V760-2007 | 7.6.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.018(R7-7.5.0) | 7.5.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.018(R7-7.5.0).zip |
+| TTC | TS-3GA-23.018(Rel7)v7.6.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23018rel7v760.pdf |
+
+### 10.3.12 TS 23.031 3G security; Fraud information gathering system (FIGS); Technical realization; Stage 2
+
+This Technical Specification specifies the Stage 2 description of the fraud information gathering system (FIGS) feature which provides the means for the HPLMN to monitor the activities of its subscribers in a VPLMN.
+
+Three levels of FIGS service are defined, levels 1 to 3.
+
+Level 1 will use the facilities provided by transferred account procedure (TAP).
+
+Levels 2 and 3 will use facilities provided by customized applications for mobile network enhanced logic (CAMEL), in particular, the information flows between the GSM service switching function (gsmSSF) and GSM service control function (gsmSCF). Phase 1 and Phase 2 CAMEL facilities will be used.
+
+Connection-orientated services only are covered.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 031 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 031 | 7.0.0 | Published | 2007-10-11 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0323031v700 |
+| ATIS | ATIS.3GPP.23.031V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.031(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.031(R7-7.0.0).zip |
+| TTC | TS-3GA-23.031(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23031rel7v700.pdf |
+
+### 10.3.13 TS 23.032 Universal geographical area description (GAD)
+
+The present document defines an intermediate universal geographical area description which subscriber applications, GSM or UMTS services, can use and the network can convert into an equivalent radio coverage map.
+
+For GSM or UMTS services which involve the use of an "area", it can be assumed that in the majority of cases the service requester will be forbidden access to data on the radio coverage map of a particular PLMN and that the service requester will not have direct access to network entities (e.g., BSC/BTS or RNC/Node B).
+
+The interpretation by the PLMN operator of the geographical area in terms of cells actually used, cells that are partly within the given area and all other technical and quality of service aspects are out of the scope of the present document.
+
+This specification also provides a description of velocity that may be associated with a universal geographical area description when both are applied to a common entity at a common time.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 032 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 032 | 7.0.0 | Published | 2007-06-22 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223032v700 |
+| ATIS | ATIS.3GPP.23.032V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.032(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.032(R7-7.0.0).zip |
+| TTC | TS-3GA-23.032(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23032rel7v700.pdf |
+
+### 10.3.14 TS 23.034 High speed circuit switched data (HSCSD); Stage 2
+
+The document contains the Stage 2 service description for a high speed circuit switched data (HSCSD) on GSM/GERAN in A/Gb mode and Iu mode. HSCSD utilizes the multislots mechanism, i.e., using multiple traffic channels (/bearers) for the communication.
+
+Additionally, the present document specifies some HSCSD related requirements for multi-system mobile stations operating in UTRAN Iu mode. In UTRAN Iu mode, one bearer can provide all needed data rates, and the multislots mechanism is therefore not needed. However, for inter-system handover to GERAN, certain information has to be provided by the mobile station during the service negotiation. The UTRAN Iu mode aspects concerning HSCSD are described exclusively in clause 4.2 of the Technical Specification.
+
+In analogy with [ITU-T I.130] (refer to Annex A) and with reference to [ITU-T Q.65], the second stage of the HSCSD is defined as follows.
+
+Stage 2 identifies the functional capabilities and information flows needed to support the service as described in high speed circuit switched data (HSCSD) – Stage 1, TS 22.034. Furthermore, it identifies various possible physical locations for the functional capabilities. The output of Stage 2, which is signalling system independent, is used as an input to Stage 3, the design of signalling system and switching Recommendations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 034 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 034 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0123034v700 |
+| ATIS | ATIS.3GPP.23.034V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.034(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-23.034(R7-7.0.0).zip |
+| TTC | TS-3GA-23.034(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23034rel7v700.pdf |
+
+### 10.3.15 TS 23.035 Immediate service termination (IST); Stage 2
+
+This document specifies the Stage 2 description of the immediate service termination (IST) service which provides the means for the HPLMN to terminate all the activities of an HPLMN subscriber in a VPLMN.
+
+Two implementations of IST are described: an implementation based on CAMEL, and an implementation based on a new MAP message.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.035V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/23/A23035-700.pdf |
+| CCSA | CCSA-TSD-123 035 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 035 | 7.0.0 | Published | 2007-06-22 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0323035v700 |
+| ATIS | ATIS.3GPP.23.035V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.035(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-23.035(R7-7.0.0).zip |
+
+### 10.3.16 TS 23.038 Alphabets and language-specific information
+
+This Technical Specification defines the alphabets, languages and message handling requirements for SMS, CBS and USSD and may additionally be used for man-machine interface (MMI) (TS 22.030).
+
+The specification for the data circuit-terminating equipment/data terminal equipment (DCE/DTE) interface (TS 27.005) will also use the codes specified herein for the transfer of SMS data to an external terminal.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.038V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/23/A23038-700.pdf |
+| CCSA | CCSA-TSD-123 038 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 038 | 7.0.0 | Published | 2007-04-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0123038v700 |
+| ATIS | ATIS.3GPP.23.038V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.038(R7-7.0.0) | 7.0.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-23.038(R7-7.0.0).zip |
+
+### 10.3.17 TS 23.040 Technical realization of the short message service (SMS)
+
+The document describes the short message service (SMS) for GSM/UMTS networks. It defines:
+
+- the services and service elements;
+- the network architecture;
+- the service centre functionality;
+- the MSC functionality (with regard to the SMS);
+- the SGSN functionality (with regard to the SMS);
+- the routing requirements;
+- the protocols and protocol layering,
+
+for the teleservice short message service, as specified in the GSM TS 02.03 and 3G TS 22.105.
+
+The use of radio resources for the transfer of short messages between the MS and the MSC or the SGSN is described in 3G TS 24.011 "Short Message Service Support on Mobile Radio Interface", and is dealt with in that specification.
+
+The network aspects of short message service provision are outside the scope of the document (i.e., the provision of network connectivity between the PLMN subsystems). There is no technical restriction within the document for the transfer of short messages between different PLMNs. Any such restriction is likely to be subject to commercial arrangements, and PLMN operators must make their own provision for interworking or for preventing interworking with other PLMNs as they see fit.
+
+The required and assumed network service offered to the higher layers is defined in this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.040V7.0.1 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/23/A23040-701.pdf |
+| CCSA | CCSA-TSD-123 040 | 7.0.1 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 040 | 7.0.1 | Published | 2007-04-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0123040v701 |
+| ATIS | ATIS.3GPP.23.040V701-2007 | 7.0.1 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.040(R7-7.0.1) | 7.0.1 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.040(R7-7.0.1).zip |
+
+### 10.3.18 TS 23.041 Technical realization of cell broadcast service (CBS)
+
+The document describes the cell broadcast short message service (CBS) for GSM and UMTS.
+
+For GSM, it defines the primitives over the cell broadcast centre – base station system (CBC-BSS) interface and the message formats over the base station system – mobile station (BSS-MS) interface for teleservice 23 as specified in 3G TS 22.003.
+
+For UMTS it defines the interface requirements for the cell broadcast centre – UMTS radio network system (RNS) interface and the radio interface requirements for UMTS radio access networks to support CBS as specified in TS 22.003.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.041V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/23/A23041-700.pdf |
+| CCSA | CCSA-TSD-123 041 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 041 | 7.0.0 | Published | 2007-04-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0123041v700 |
+| ATIS | ATIS.3GPP.23.041V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.041(R7-7.0.0) | 7.0.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.041(R7-7.0.0).zip |
+
+### 10.3.19 TS 23.042 Compression algorithm for text messaging services
+
+The document introduces the concepts and mechanisms involved in the compression and decompression of a stream of data.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.042V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/23/A23042-700.pdf |
+| CCSA | CCSA-TSD-123 042 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 042 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0123042v700 |
+| ATIS | ATIS.3GPP.23.042V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.042(R7-7.0.0) | 7.0.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.042(R7-7.0.0).zip |
+
+### 10.3.20 TS 23.053 Tandem free operation (TFO); Service description; Stage 2
+
+The document defines the Stage 2 service description for tandem free operation (TFO) in and between GSM and UMTS. Tandem free operation applies only to speech calls.
+
+NOTE – The TFO principles are built so that they could be used as well by other systems other than GSM and UMTS.
+
+In analogy with [ITU-T I.130] and with reference to [ITU-T Q.65], the second stage of the following three-level structure is derived from a stage 1 service description.
+
+- Stage 1 is an overall service description, from the service subscriber's and user's standpoints, that views the network as a single entity which provides services to the user.
+- Stage 2 identifies the functional capabilities and information flows needed to support the service described in Stage 1. Furthermore, it identifies various possible physical locations for the functional capabilities. The output of Stage 2, which is signalling system independent, is used as an input to Stage 3, the design of signalling system and switching Recommendations.
+- Stage 3 defines the signalling system protocols and switching functions needed to implement the service described in Stage 2.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.053V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/23/A23053-700.pdf |
+| CCSA | CCSA-TSD-123 053 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 053 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0423053v700 |
+| ATIS | ATIS.3GPP.23.053V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.053(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.053(R7-7.0.0).zip |
+
+### 10.3.21 TS 23.057 Mobile execution environment (MExE); Functional description; Stage 2
+
+The document defines the Stage 2 and Stage 3 description of the mobile execution environment (MExE). Stage 2 identifies the functional capabilities and information flows needed to support the service described in Stage 1.
+
+The document includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
+
+The document contains the core functions for a mobile execution environment (MExE) that are sufficient to provide a complete service.
+
+MExE uses a number of technologies to realize the requirements of the Stage 1 description (TS 22.057). The document describes how the service requirements are realized with the selected technologies. The TS is divided into sections each covering the aspects relating to particular MExE technologies; it is intended that this specification will evolve along with the MExE technologies. A generic section of the specification covers areas of MExE common to all technologies.
+
+Implementation of this specification outside the UE (user equipment) is outside the scope of this specification.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.057V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/23/A23057-700.pdf |
+| CCSA | CCSA-TSD-123 057 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 057 | 7.0.0 | Published | 2007-06-22 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223057v700 |
+| ATIS | ATIS.3GPP.23.057V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.057(R7-7.0.0) | 7.0.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.057(R7-7.0.0).zip |
+
+### 10.3.22 TS 23.060 General packet radio service (GPRS) Service description; Stage 2
+
+The document defines the Stage 2 service description for the general packet radio service (GPRS) which is a packet bearer service and a main part of the packet domain. [ITU-T I.130] describes a three-stage method for characterization of telecommunication services, and [ITU-T Q.65] defines Stage 2 of the method.
+
+The document does not cover the radio access network functionality. TS 23.064 contains an overall description of the GSM GPRS access network. 3G TS 25.301 contains an overall description of the UMTS terrestrial radio access network. 3G TS 43.051 contains an overall description of GSM/EDGE radio access network.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 060 | 7.5.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 060 | 7.5.0 | Published | 2007-10-08 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223060v750 |
+| ATIS | ATIS.3GPP.23.060V750-2007 | 7.5.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.060(R7-7.4.0) | 7.4.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.060(R7-7.4.0).zip |
+| TTC | TS-3GA-23.060(Rel7)v7.5.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23060rel7v750.pdf |
+
+### 10.3.23 TS 23.066 Support of mobile number portability (MNP); Technical realization; Stage 2
+
+The document describes several alternatives for the realization of mobile number portability.
+
+The document includes information applicable to network operators, service providers, switch and database manufacturers and national regulators.
+
+It is left to operator and implementation decisions which option, or combination of options, is used, taking into account the regulatory and architectural constraints that may prevail. The possible implications of these options on internal node functions and on signalling performance are not covered in the document.
+
+Normative Annex A of the document describes the technical realization of the handling of calls to ported UMTS or GSM mobile subscribers using IN technology.
+
+Normative Annex C of the document describes the technical realization of the handling of calls to ported UMTS or GSM mobile subscribers using signalling relay technology.
+
+Normative Annexes A and C describe alternative solutions. The network operator may choose the solution to be used in his network.
+
+Normative Annex B of the document describes the technical realization of the handling of non-call related SCCP signalling for ported UMTS or GSM mobile subscribers using signalling relay technology.
+
+The document does not specify the porting process.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 066 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 066 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423066v700 |
+| ATIS | ATIS.3GPP.23.066V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.066(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.066(R7-7.0.0).zip |
+| TTC | TS-3GA-23.066(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23066rel7v700.pdf |
+
+### 10.3.24 TS 23.067 Enhanced multi-level precedence and pre-emption service (eMLPP); Stage 2
+
+The document specifies the Stage 2 description of the enhanced multi-level precedence and pre-emption service (eMLPP) which provides different call priorities in combination with fast call set-up and pre-emption for different applications according to 3G TS 22.067.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 067 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 067 | 7.1.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423067v710 |
+| ATIS | ATIS.3GPP.23.067V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.067(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.067(R7-7.1.0).zip |
+| TTC | TS-3GA-23.067(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23067rel7v710.pdf |
+
+### 10.3.25 TS 23.072 Call deflection (CD) supplementary service; Stage 2
+
+This Technical Specification gives the Stage 2 description of the call deflection supplementary service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 072 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 072 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423072v700 |
+| ATIS | ATIS.3GPP.23.072V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.072(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.072(R7-7.0.0).zip |
+| TTC | TS-3GA-23.072(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23072rel7v700.pdf |
+
+### 10.3.26 TS 23.078 Customized applications for mobile network enhanced logic (CAMEL) Phase 4; Stage 2
+
+The document specifies the Stage 2 description for the fourth phase (see TS 22.078) of the customized applications for mobile network enhanced logic (CAMEL) feature which provides the mechanisms to support services of operators which are not covered by standardized services even when roaming outside the HPLMN.
+
+The CAMEL feature is a network feature and not a supplementary service. It is a tool to help the network operator to provide the subscribers with the operator specific services even when roaming outside the HPLMN.
+
+In this document, the GSM service control function (gsmSCF) is treated as being part of the HPLMN. The regulatory environment in some countries may require the possibility that the gsmSCF and the HPLMN are controlled by different operators, and the gsmSCF and the HPLMN are therefore distinct entities.
+
+The fourth phase of the CAMEL feature supports, in addition to the third phase of the CAMEL:
+
+- interactions with optimal routing;
+- call party handling;
+- DTMF mid call procedure for mobile originated and mobile terminating calls;
+- inclusion of flexible tone injection;
+- provision of location information of called subscriber;
+- provide location information during ongoing call;
+- CAMEL control over MT SMS;
+- notification of GPRS mobility management to CSE;
+- inclusion of ODB data in any time modification;
+- enhancement of any time interrogation and provide subscriber information for PS domain;
+- mobile number portability database interrogation;
+- criteria for the provision of location information during ongoing call;
+- enhanced dialled services;
+- enhancement to establish temporary connection.
+
+CAMEL applicability to IP-based multimedia services is introduced in the fourth phase of the CAMEL. It is specified in TS 23.278.
+
+CAMEL is not applicable to emergency set-up (TS 12), i.e., if an emergency call is requested, then the gsmSSF shall not be invoked.
+
+The mechanism described in this document addresses especially the need for information exchange between the VPLMN or IPLMN and the HPLMN for support of operator-specific services. Any user procedures for the control of operator-specific services are outside the scope of this document. Subscribers who have subscribed to operator specific services and therefore need the functional support of the CAMEL feature shall be marked in the HPLMN and VPLMN. In case a subscriber is marked to need CAMEL support, the appropriate procedures which provide the necessary information to the VPLMN or the HPLMN are invoked. It is possible for the HPLMN to instruct the VPLMN or IPLMN to interact with a gsmSCF which is controlled by the HPLMN.
+
+The specification of operator specific services is outside the scope of this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 078 | 7.9.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 078 | 7.9.0 | Published | 2007-10-08 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423078v790 |
+| ATIS | ATIS.3GPP.23.078V790-2007 | 7.9.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.078(R7-7.8.0) | 7.8.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.078(R7-7.8.0).zip |
+| TTC | TS-3GA-23.078(Rel7)v7.9.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23078rel7v790.pdf |
+
+### 10.3.27 TS 23.079 Support of optimal routing (SOR); Technical realization; Stage 2
+
+The document specifies the technical realization of the first phase of the network feature support of optimal routing (SOR). The first phase of SOR provides:
+
+- as a network operator option, a method to route a call from one mobile subscriber directly to another mobile subscriber who is in the same country as the calling mobile subscriber or in the called mobile subscriber's home country, without needing to connect the call via the HPLMN of the called subscriber, even though the called mobile subscriber has roamed outside his HPLMN;
+- a method to forward calls when a called mobile subscriber who has roamed outside his home country is busy, or is not reachable, or does not reply, to a forwarded-to destination in the HPLMN country of the called subscriber or the VPLMN country of the called subscriber, without needing to connect the forwarded call via the VPLMN of the called subscriber;
+- a method to combine the optimal routing described in the first bullet point above with the optimal routing described in the second bullet point above.
+
+Optimal routing of a call is permitted only if all entities involved in handling the call support optimal routing.
+
+Other cases of optimal routing (e.g., calls where the calling and called subscribers are in different countries, forwarding to a mobile subscriber or multiple forwarding) will be considered for inclusion in later phases.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 079 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 079 | 7.0.0 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423079v700 |
+| ATIS | ATIS.3GPP.23.079V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.079(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.079(R7-7.0.0).zip |
+| TTC | TS-3GA-23.079(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23079rel7v700.pdf |
+
+### 10.3.28 TS 23.081 Line identification supplementary services; Stage 2
+
+This document gives the Stage 2 description of the call identification supplementary services.
+
+The group line identification supplementary services are divided into the following four supplementary services:
+
+- Calling line identification presentation (CLIP);
+- Calling line identification restriction (CLIR);
+- Connected line identification presentation (COLP);
+- Connected line identification restriction (COLR).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 081 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 081 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423081v700 |
+| ATIS | ATIS.3GPP.23.081V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.081(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.081(R7-7.0.0).zip |
+| TTC | TS-3GA-23.081(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23081rel7v700.pdf |
+
+### 10.3.29 TS 23.082 Call forwarding (CF) supplementary services; Stage 2
+
+The document gives the Stage 2 description of the call forwarding supplementary services.
+
+The group of supplementary services call offering supplementary services is divided into 4 different supplementary services:
+
+- Call forwarding unconditional (CFU);
+- Call forwarding on mobile subscriber busy (CFB);
+- Call forwarding on no reply (CFNRy);
+- Call forwarding on mobile subscriber not reachable (CFNRc).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 082 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 082 | 7.1.0 | Published | 2007-10-08 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423082v710 |
+| ATIS | ATIS.3GPP.23.082V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.082(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.082(R7-7.0.0).zip |
+| TTC | TS-3GA-23.082(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23082rel7v710.pdf |
+
+### 10.3.30 TS 23.083 Call waiting (CW) and call hold (HOLD) supplementary service; Stage 2
+
+This document gives the Stage 2 description of the call completion supplementary services.
+
+The group of call completion supplementary services is divided into the following two supplementary services:
+
+- Call waiting (CW);
+- Call hold (HOLD).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 083 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 083 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423083v700 |
+| ATIS | ATIS.3GPP.23.083V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.083(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.083(R7-7.0.0).zip |
+| TTC | TS-3GA-23.083(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23083rel7v700.pdf |
+
+### 10.3.31 TS 23.084 Multi-party (MPTY) supplementary service; Stage 2
+
+The document gives the Stage 2 description of the multi-party supplementary services.
+
+Only one multi-party supplementary service has been defined: this is the multi-party (MPTY) service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 084 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 084 | 7.0.0 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423084v700 |
+| ATIS | ATIS.3GPP.23.084V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.084(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.084(R7-7.0.0).zip |
+| TTC | TS-3GA-23.084(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23084rel7v700.pdf |
+
+### 10.3.32 TS 23.085 Closed user group (CUG) supplementary service; Stage 2
+
+The document gives the Stage 2 description of the closed user group supplementary service.
+
+The community of interest supplementary service defined is:
+
+- Closed user group (CUG)
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 085 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 085 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423085v700 |
+| ATIS | ATIS.3GPP.23.085V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.085(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.085(R7-7.0.0).zip |
+| TTC | TS-3GA-23.085(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23085rel7v700.pdf |
+
+### 10.3.33 TS 23.086 Advice of charge (AoC) supplementary service; Stage 2
+
+The document gives the Stage 2 description of the advice of charge (AoC) supplementary services.
+
+The charging supplementary services currently defined are:
+
+- Advice of charge (Information) (AoCI);
+- Advice of charge (Charging) (AoCC).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 086 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 086 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423086v700 |
+| ATIS | ATIS.3GPP.23.086V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.086(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.086(R7-7.0.0).zip |
+| TTC | TS-3GA-23.086(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23086rel7v700.pdf |
+
+### 10.3.34 TS 23.087 User-to-user signalling (UUS) supplementary service; Stage 2
+
+The document gives the Stage 2 description of the user-to-user signalling supplementary services.
+
+The user-to-user supplementary service is divided into 3 different services:
+
+- Service 1 (UUS1);
+- Service 2 (UUS2);
+- Service 3 (UUS3).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 087 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 087 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423087v700 |
+| ATIS | ATIS.3GPP.23.087V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.087(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.087(R7-7.0.0).zip |
+| TTC | TS-3GA-23.087(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23087rel7v700.pdf |
+
+### 10.3.35 TS 23.088 Call barring (CB) supplementary services; Stage 2
+
+The document gives the Stage 2 description of the call barring services.
+
+The possibility for a mobile subscriber to have certain categories of calls barred originated from or terminated at his access.
+
+Barring of outgoing calls:
+
+- Barring of all outgoing calls (BAOC) (Barring program 1);
+- Barring of outgoing international calls (BOIC) (Barring program 2);
+- Barring of outgoing international calls EXCEPT those directed to the home PLMN country (BOIC-exHC) (Barring program 3).
+
+Barring of incoming calls:
+
+- Barring of all incoming calls (BAIC) (Barring program 1);
+- Barring of incoming calls when roaming outside the home PLMN country (BIC-Roam) (Barring program 2).
+
+NOTE – The call barring program "incoming calls when roaming outside the home PLMN country" is only relevant if, as a general rule, the called mobile subscriber pays the charges for the forwarded part of the call from his home PLMN country to any other country.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 088 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 088 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423088v700 |
+| ATIS | ATIS.3GPP.23.088V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.088(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.088(R7-7.0.0).zip |
+| TTC | TS-3GA-23.088(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23088rel7v700.pdf |
+
+### 10.3.36 TS 23.090 Unstructured supplementary service data (USSD); Stage 2
+
+The document gives the Stage 2 description of unstructured supplementary service data (USSD).
+
+The unstructured supplementary service data (USSD) mechanism allows the mobile station (MS) user and a PLMN operator defined application to communicate in a way which is transparent to the MS and to intermediate network entities. The mechanism allows development of PLMN specific supplementary services. Figure 10.3.36-1 shows how handling of USSD is carried out, independently of the applications.
+
+
+
+```
+
+graph LR
+ subgraph MS [MS]
+ MMI[MMI]
+ USSD_H[USSD handler]
+ end
+ subgraph MSC [MSC]
+ Apps1[Applications]
+ USSD_H1[USSD handler]
+ end
+ subgraph VLR [VLR]
+ Apps2[Applications]
+ USSD_H2[USSD handler]
+ end
+ subgraph HLR [HLR]
+ Apps3[Applications]
+ USSD_H3[USSD handler]
+ end
+ USER((USER)) --- MMI
+ MMI --- USSD_H
+ USSD_H --- USSD_H1
+ USSD_H1 --- USSD_H2
+ USSD_H2 --- USSD_H3
+
+```
+
+Diagram illustrating the handling of USSD across network entities: MS, MSC, VLR, and HLR. Each entity contains an 'Applications' block and a 'USSD handler' block. The MS also contains an 'MMI' block. Arrows show the flow of USSD messages from the user through the MS's MMI and USSD handler, then through the MSC, VLR, and HLR's USSD handlers.
+
+Q.1741.5(08)\_F10.3.36-1
+
+**Figure 10.3.36-1 – Handling of USSD**
+
+The document defines the requirements for handling USSD at the MS and network entities. It does not include specification of particular applications, nor does it specify how a particular application is selected. Where more than one application exists at a network entity, routing of messages to the correct application is carried out by the USSD handler. The MMI for USSD is specified in
+
+TS 22.030 and TS 22.090. The alphabet indicator and the data-coding scheme are defined in TS 23.038.
+
+USSD may be initiated by the MS user, or by the network in the following ways:
+
+- Network initiated USSD;
+- Mobile initiated USSD.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 090 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 090 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423090v700 |
+| ATIS | ATIS.3GPP.23.090V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.090(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.090(R7-7.0.0).zip |
+| TTC | TS-3GA-23.090(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23090rel7v700.pdf |
+
+### 10.3.37 TS 23.091 Explicit call transfer (ECT) supplementary service; Stage 2
+
+The document gives the Stage 2 description of the call transfer supplementary services.
+
+Only one call transfer supplementary service has been defined, this is the explicit call transfer (ECT) supplementary service, and is described in this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 091 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 091 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423091v700 |
+| ATIS | ATIS.3GPP.23.091V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.091(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.091(R7-7.0.0).zip |
+| TTC | TS-3GA-23.091(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23091rel7v700.pdf |
+
+### 10.3.38 TS 23.093 Technical realization of completion of calls to busy subscriber (CCBS); Stage 2
+
+This Technical Specification gives the Stage 2 description of the completion of calls to busy subscriber (CCBS) supplementary service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 093 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 093 | 7.1.0 | Published | 2007-10-08 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423093v710 |
+| ATIS | ATIS.3GPP.23.093V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.093(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.093(R7-7.0.0).zip |
+| TTC | TS-3GA-23.093(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23093rel7v710.pdf |
+
+### 10.3.39 TS 23.094 Follow Me; Stage 2
+
+The document specifies the Stage 2 description for the Follow Me feature.
+
+The Follow Me feature enables a mobile subscriber A to manipulate the Follow Me data of a remote party B in such a way that subsequent calls directed to remote party B will be forwarded to subscriber A.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 094 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 094 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423094v700 |
+| ATIS | ATIS.3GPP.23.094V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.094(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.094(R7-7.0.0).zip |
+| TTC | TS-3GA-23.094(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23094rel7v700.pdf |
+
+### 10.3.40 TS 23.096 Name identification supplementary service; Stage 2
+
+The document gives the Stage 2 description of the name identification supplementary services.
+
+The group of name identification supplementary services contains the following supplementary service:
+
+CNAP – Calling name presentation.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 096 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 096 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423096v700 |
+| ATIS | ATIS.3GPP.23.096V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.096(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.096(R7-7.0.0).zip |
+| TTC | TS-3GA-23.096(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23096rel7v700.pdf |
+
+### 10.3.41 TS 23.097 Multiple subscriber profile (MSP) Phase 2; Stage 2
+
+The document specifies the Stage 2 description of the multiple subscriber profile (MSP) supplementary service Phase 2. MSP Phase 2 is implemented using CAMEL Phase 3.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 097 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 097 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423097v700 |
+| ATIS | ATIS.3GPP.23.097V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.097(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.097(R7-7.0.0).zip |
+| TTC | TS-3GA-23.097(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23097rel7v700.pdf |
+
+### 10.3.42 TS 23.101 General UMTS architecture
+
+This document defines the basic physical and functional separation of UMTS. The contents of this specification is limited to those features that are common to all UMTS networks independent of their origin. It identifies and names the reference points and functional groupings appearing at this level.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 101 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 101 | 7.0.0 | Published | 2007-06-22 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223101v700 |
+| ATIS | ATIS.3GPP.23.101V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.101(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdnfile/TTAT.3G-23.101(R7-7.0.0).zip |
+| TTC | TS-3GA-23.101(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23101rel7v700.pdf |
+
+### 10.3.43 TS 23.107 Quality of service (QoS) concept and architecture
+
+The document provides the framework for quality of service within UMTS. The main purpose is to specify the list of attributes applicable to UMTS bearer service and radio access bearer service, as well as describe the quality of service architecture to be used in UMTS networks.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.107V7.1.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/23/A23107-710.pdf |
+| CCSA | CCSA-TSD-123 107 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 107 | 7.1.0 | Published | 2007-10-08 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223107v710 |
+| ATIS | ATIS.3GPP.23.107V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.107(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdnfile/TTAT.3G-23.107(R7-7.0.0).zip |
+
+### 10.3.44 TS 23.108 Mobile radio interface layer 3 specification, core network protocols; Stage 2
+
+This document specifies the procedures used at the radio interface (Reference Point Um, see TS 24.002) for call control (CC), mobility management (MM), and session management (SM).
+
+When the notations for "further study" or "FS" or "FFS" are present in this document, they mean that the indicated text is not a normative portion of this standard.
+
+These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The control channels are described in TS 44.003.
+
+The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in TS 24.007.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 108 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 108 | 7.0.0 | Published | 2007-07-05 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0123108v700 |
+| ATIS | ATIS.3GPP.23.108V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.108(R7-7.0.0) | 7.0.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.108(R7-7.0.0).zip |
+| TTC | TS-3GA-23.108(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23108rel7v700.pdf |
+
+### 10.3.45 TS 23.110 Universal mobile telecommunications system (UMTS) access stratum; services and functions
+
+The present document specifies the services provided by the access stratum to the rest of the system. The adopted architecture is given by 3GPP TS 23.101.
+
+The present document describes the main functions visible at the boundary between the access stratum and the rest of the system; it describes in general terms the information flows, both control and user data, over this boundary and relevant for the access stratum.
+
+The present document is the basis of the detailed specifications of the protocols which rule the information flows, both control and user data, between the access stratum and the parts of UMTS outside the access stratum, and of the detailed specifications of the UTRAN. These detailed specifications are to be found in other Technical Specifications.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 110 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 110 | 7.0.0 | Published | 2007-06-22 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223110v700 |
+| ATIS | ATIS.3GPP.23.110V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.110(R7-7.0.0) | 7.0.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.110(R7-7.0.0).zip |
+| TTC | TS-3GA-23.110(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23110rel7v700.pdf |
+
+### 10.3.46 TS 23.116 Super-charger technical realization; Stage 2
+
+The document specifies the Stage 2 description of the super-charger that provides a mechanism to reduce the signalling traffic associated with mobility.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 116 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 116 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423116v700 |
+| ATIS | ATIS.3GPP.23.116V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.116(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-23.116(R7-7.0.0).zip |
+| TTC | TS-3GA-23.116(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23116rel7v700.pdf |
+
+### 10.3.47 TS 23.119 Gateway location register (GLR); Stage2
+
+The document gives the Stage 2 description of the gateway location register (GLR) within the UMTS core network as a means of reducing the amount of MAP signalling traffic associated with location management carried over inter-PLMN links for roaming users.
+
+The document will be restricted of the case where the GLR supports one VPLMN only.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 119 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 119 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423119v700 |
+| ATIS | ATIS.3GPP.23.119V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.119(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-23.119(R7-7.0.0).zip |
+| TTC | TS-3GA-23.119(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23119rel7v700.pdf |
+
+### 10.3.48 TS 23.122 Non-access-stratum (NAS) functions related to mobile station (MS) in idle mode
+
+This Technical Specification gives an overview of the tasks undertaken by the core network protocols of a mobile station (MS) when in idle mode, that is, switched on but not having a dedicated channel allocated. It also describes the corresponding network functions. The idle mode functions are also performed by a GPRS MS as long as no dedicated channel is allocated to the MS. The conditions when the idle mode functions are performed by an MS in the UTRA RRC connected mode states are specified in 3G TS 25.331.
+
+This Technical Specification outlines how the requirements of the 22-series Technical Specifications (especially 3G TS 22.011) on idle mode operation shall be implemented. Further details are given in 3G TS 24.008.
+
+This Technical Specification gives a general description of the idle mode process. The main requirements and technical solutions of those requirements are included. The processes used in idle mode are described.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 122 | 7.10.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 122 | 7.10.0 | Published | 2007-10-08 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0123122v7a0 |
+| ATIS | ATIS.3GPP.23.122V7100-2007 | 7.10.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.122(R7-7.9.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.122(R7-7.9.0).zip |
+| TTC | TS-3GA-23.122(Rel7)v7.10.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23122rel7v7100.pdf |
+
+### 10.3.49 TS 23.125 Overall high-level functionality and architecture impacts of flow-based charging; Stage 2
+
+The present document specifies the overall high-level functionality and architecture impacts of flow-based charging.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 125 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 125 | 7.0.0 | Published | 2007-06-25 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223125v700 |
+| ATIS | ATIS.3GPP.23.125V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.125(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.125(R7-7.0.0).zip |
+| TTC | TS-3GA-23.125(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23125rel7v700.pdf |
+
+### 10.3.50 TS 23.135 Multicall supplementary service; Stage 2
+
+The document gives the Stage 2 description of the multicall supplementary service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 135 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 135 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423135v700 |
+| ATIS | ATIS.3GPP.23.135V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.135(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.135(R7-7.0.0).zip |
+| TTC | TS-3GA-23.135(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23135rel7v700.pdf |
+
+### 10.3.51 TS 23.141 Presence service; architecture and functional description
+
+The present document describes the Stage 2 description (architectural solution and functionalities) for the presence service, which includes the elements necessary to realize the Stage 1 requirements in 3GPP TS 22.141.
+
+The present document includes information applicable to network operators, service providers and manufacturers.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 141 | 7.3.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 141 | 7.3.0 | Published | 2007-10-08 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223141v730 |
+| ATIS | ATIS.3GPP.23.141V730-2007 | 7.3.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.141(R7-7.3.0) | 7.3.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.141(R7-7.3.0).zip |
+| TTC | TS-3GA-23.141(Rel7)v7.3.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23141rel7v730.pdf |
+
+### 10.3.52 TS 23.146 Technical realization of facsimile Group 3 service – Non-transparent
+
+The document describes the procedures allowing the technical realization of the real-time end-to-end facsimile group 3 service within the UMTS PLMN using non-transparent network support according to the definition of the teleservices 61 and 62 specified in TS 22.003. Within the document, particular attention is given to teleservice "Alternate speech/facsimile group 3" (Teleservice 61). However, the definitions apply also to teleservice "Automatic facsimile group 3" (Teleservice 62) with the exception of all actions concerned with the speech phase. Consequently, in the following descriptions, the term "Teleservice" denotes both teleservice 61 and teleservice 62 as appropriate.
+
+NOTE – [ITU-T V.25 *bis*] is outdated. References to V.25 *bis* procedures need to be replaced by corresponding procedures based on Rec. ITU-T V.250 and on TS 27.007.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 146 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 146 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0323146v700 |
+| ATIS | ATIS.3GPP.23.146V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.146(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.146(R7-7.0.0).zip |
+| TTC | TS-3GA-23.146(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23146rel7v700.pdf |
+
+### 10.3.53 TS 23.153 Out-of-band transcoder control; Stage 2
+
+This Technical Specification specifies the Stage 2 description of the out-of-band transcoder control for speech services. It describes the principles and procedures to support transcoder free operation, tandem free operation and the interworking between TrFO and TFO. Transcoder at the edge is also part of this specification.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 153 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 153 | 7.2.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423153v720 |
+| ATIS | ATIS.3GPP.23.153V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.153(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.153(R7-7.2.0).zip |
+| TTC | TS-3GA-23.153(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23153rel7v720.pdf |
+
+### 10.3.54 TS 23.167 IP multimedia subsystem (IMS) emergency sessions
+
+This document defines the stage-2 service description for emergency services in the IP multimedia core network subsystem (IMS), including the elements necessary to support IP multimedia (IM) emergency services. [ITU-T I.130] describes a three-stage method for the characterization of telecommunication services, and [ITU-T Q.65] defines stage 2 of the method.
+
+This document covers also the access network aspects that are crucial for the provisioning of IMS emergency services. Other 3GPP specifications that are related to the IMS emergency services are TS 23.228 on IMS in general, including fixed broadband access aspects, TS 23.060 and TS 23.234 describing GPRS and 3GPP/WLAN interworking respectively and TS 23.271 that covers location services. TS 25.301 contains an overall description of the UMTS terrestrial radio access network.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 167 | 7.6.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 167 | 7.6.0 | Published | 2007-10-08 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223167v760 |
+| ATIS | ATIS.3GPP.23.167V760-2007 | 7.6.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.167(R7-7.4.0) | 7.4.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.167(R7-7.4.0).zip |
+| TTC | TS-3GA-23.167(Rel7)v7.6.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23167rel7v760.pdf |
+
+### 10.3.55 TS 23.172 Technical realization of circuit switched (CS) multimedia service; UDI/RDI fallback and service modification; Stage 2
+
+This specification describes the service change and UDI fallback (SCUDIF) feature. This service is available to UDI/RDI multimedia calls and allows users to achieve successful call establishment when end-to-end circuit-switched (CS) multimedia is not possible (fallback to speech) or when signalling of the feature is not possible in the network (fallback to preferred service or speech). Furthermore, it allows the users to swap between a multimedia service and basic speech during an established call.
+
+NOTE – In this document, the term "multimedia" refers to UDI/RDI multimedia unless specifically stated.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 172 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 172 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0323172v700 |
+| ATIS | ATIS.3GPP.23.172V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.172(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.172(R7-7.0.0).zip |
+| TTC | TS-3GA-23.172(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23172rel7v700.pdf |
+
+### 10.3.56 TS 23.198 Open service access (OSA); Stage 2
+
+This document specifies the stage 2 of the open service access (OSA).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 198 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 198 | 7.2.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0523198v720 |
+| ATIS | ATIS.3GPP.23.198V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.198(R7-7.3.0) | 7.3.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-23.198(R7-7.3.0).zip |
+| TTC | TS-3GA-23.198(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23198rel7v720.pdf |
+
+### 10.3.57 TS 23.202 Circuit switched data bearer services
+
+The present document provides an overview of the architecture and issues related to the provision of circuit switched bearer services in a 3G mobile network (UMTS) operating in UTRAN or GERAN Iu mode. Handover to GERAN A/Gb mode is also considered.
+
+NOTE – The Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 202 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 202 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0323202v700 |
+| ATIS | ATIS.3GPP.23.202V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.202(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-23.202(R7-7.0.0).zip |
+| TTC | TS-3GA-23.202(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23202rel7v700.pdf |
+
+### 10.3.58 TS 23.203 Policy and charging control architecture
+
+The present document specifies the overall stage 2 level functionality for policy and charging control that encompasses the following high level functions for IP-CANs (e.g., GPRS, I-WLAN, fixed broadband, etc.):
+
+- Flow based charging, including charging control and online credit control;
+- Policy control (e.g., gating control, QoS control, etc.).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.203V7.4.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/23/A23203-740.pdf |
+| CCSA | CCSA-TSD-123 203 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 203 | 7.4.0 | Published | 2007-10-08 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223203v740 |
+| ATIS | ATIS.3GPP.23.203V740-2007 | 7.4.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.203(R7-7.3.0) | 7,3,0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.203(R7-7.3.0).zip |
+
+### 10.3.59 TS 23.205 Bearer-independent circuit-switched core network; Stage 2
+
+The document defines the Stage 2 description for the bearer independent CS core network. The Stage 2 shall cover the information flow between the GMSC server, MSC server and media gateways. Note that nothing in this document shall preclude an implementation of a combined MSC Server and MGW. This document shall show the CS core network termination of the Iu interface in order to cover the information flow stimulus to the core network and describe the interaction with the supplementary and value-added services and capabilities.
+
+For the purposes of this specification, the protocol used over the Nc interface is an enhanced call control protocol supporting call bearer separation such as BICC (which is specified in 3G TS 29.205). The protocol used over the Mc interface is [ITU-T H.248.1]. Existing specifications and Recommendations shall not be repeated as such, the relevant specification shall be referred to.
+
+This Technical Specification is applicable only for ATM or IP transport in the CS core network.
+
+
+
+Figure 10.3.59-1 – CS core network logical architecture diagram. The diagram shows the logical architecture of a CS core network. On the left, UTRAN and GERAN are connected to an MGW via Iu and A/Iu interfaces respectively. The MGW is connected to an MSC server via a Mc interface. The MSC server is connected to a GMSC server via an Nc interface. The GMSC server is connected to another MGW via a Mc interface. This second MGW is connected to a PSTN/Legacy/External network. Below the MSC server and GMSC server, there are interfaces for Applications and services (CAP) and an HLR (D and C interfaces). A legend at the bottom indicates that dashed lines represent signalling interfaces and solid lines represent signalling and data transfer interfaces. The diagram is labeled Q.1741.5(08)\_F10.3.59-1.
+
+**Figure 10.3.59-1 – CS core network logical architecture**
+
+The CAP interfaces and the interfaces towards the HLR are outside the scope of this Technical Specification.
+
+Details of transcoder-free operation are outside the scope of this Technical Specification. Please see TS 23.153 for more information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 205 | 7.6.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 205 | 7.6.0 | Published | 2007-10-11 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423205v760 |
+| ATIS | ATIS.3GPP.23.205V760-2007 | 7.6.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.205(R7-7.5.0) | 7.5.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-23.205(R7-7.5.0).zip |
+| TTC | TS-3GA-23.205(Rel7)v7.6.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23205rel7v760.pdf |
+
+### 10.3.60 TS 23.206 Voice call continuity (VCC) between circuit switched (CS) and IP multimedia subsystem (IMS); Stage 2
+
+The present document specifies the functional architecture and information flows of the voice call continuity feature which provides the capability to transfer the path of an existing voice call between a 3GPP CS system (GSM/UMTS) and IMS, and vice versa.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.206V7.4.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/23/A23206-740.pdf |
+| CCSA | CCSA-TSD-123 206 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 206 | 7.4.0 | Published | 2007-10-08 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223206v740 |
+| ATIS | ATIS.3GPP.23.206V740-2007 | 7.4.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.206(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-23.206(R7-7.2.0).zip |
+
+### 10.3.61 TS 23.207 End-to-end quality of service (QoS) concept and architecture
+
+This document provides the framework for end-to-end quality of service involving GPRS and complements TS 23.107 which describes the framework for quality of service within UMTS. The end-to-end QoS architecture is provided in Figure 10.3.61-1. The document describes the interaction between the TE/MT local bearer service, the GPRS bearer service, and the external bearer service, and how these together provide quality of service for the end-to-end service. The document also describes IP level mechanisms necessary in providing end-to-end quality of service involving GPRS networks, including possible interaction between the IP level and the GPRS level, as well as the application level and the IP level.
+
+In contrast to the TS 23.107, this specification is only applicable to GPRS packet-switched access services, and includes aspects of interworking to the IM subsystem as well as PSTN and other networks. The document does not cover the circuit-switched access services.
+
+
+
+Figure 10.3.61-1 – End-to-end QoS architecture diagram. The diagram shows a layered architecture for GPRS. At the top, a 'GPRS' bracket spans over 'MT', 'UTRAN/GERAN', 'CN Iu EDGE NODE', and 'CN gateway'. Below this, an 'End-to-end service' layer spans from 'TE' to 'TE'. Below that, 'TE/MT local bearer service', 'GPRS bearer service', and 'External bearer service' are shown. The 'GPRS bearer service' is supported by 'Radio access bearer service' and 'CN bearer service'. These are further supported by 'Radio bearer service', 'Iu bearer service', and 'Backbone bearer service'. At the bottom, 'Physical radio service' and 'Physical bearer service' are shown. A small text 'Q.1741.5(08)\_F10.3.61-1' is at the bottom right.
+
+Figure 10.3.61-1 – End-to-end QoS architecture
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.207V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/23/A23207-700.pdf |
+| CCSA | CCSA-TSD-123 207 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 207 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TS/SGS-0223207v700 |
+| ATIS | ATIS.3GPP.23.207V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.207(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-23.207(R7-7.0.0).zip |
+
+### 10.3.62 TS 23.218 IP multimedia (IM) session handling; IM call model; Stage 2
+
+This document specifies the IP multimedia (IM) call model for handling of an IP multimedia session origination and termination for an IP multimedia subscriber.
+
+This document includes interactions between an application server and IP multimedia sessions.
+
+The IP multimedia (IM) subsystem Stage 2 is specified in TS 23.228, and the signalling flows for the IP multimedia call control based on SIP and SDP are specified in TS 24.228.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 218 | 7.7.1 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 218 | 7.7.1 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0123218v771 |
+| ATIS | ATIS.3GPP.23.218V771-2007 | 7.7.1 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.218(R7-7.6.0) | 7.6.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.218(R7-7.6.0).zip |
+| TTC | TS-3GA-23.218(Rel7)v7.7.1 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23218rel7v771.pdf |
+
+### 10.3.63 TS 23.221 Architectural requirements
+
+This document covers details the architectural requirements for the GSM in Iu mode and UMTS systems. In particular, it details the high-level requirements for the circuit-switched (CS) domain and the Stage 2 procedures that span more than one domain/subsystem within UMTS and GSM. The reference model to which these procedures apply can be found within 3G TS 23.002. In addition, A mode-to-Iu mode handover for CS services is addressed. Detailed architectural requirements within the subsystems are contained within the remainder of the 23 series of specifications; e.g., the requirements for the packet-switched (PS) domain are contained within 3G TS 23.060 and the requirements for the bearer independent CS core network are contained in 3G TS 23.205.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 221 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 221 | 7.1.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223221v710 |
+| ATIS | ATIS.3GPP.23.221V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.221(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.221(R7-7.2.0).zip |
+| TTC | TS-3GA-23.221(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23221rel7v710.pdf |
+
+### 10.3.64 TS 23.226 Global text telephony (GTT); Stage 2
+
+This Technical Specification defines the Stage 2 description of the real-time text conversation feature called global text telephony (GTT). GTT Stage 2 identifies the functional capabilities needed to support the service described in GTT Stage 1.
+
+This document contains the core functions for a real-time text conversation feature GTT, to be used in combination with other media in conversational services.
+
+GTT offers real-time conversation in text, to be used alone or in combination with other conversational media, and interworking with current and emerging text conversation features in the fixed networks and other mobile networks.
+
+GTT uses a number of functional entities to realize the requirements of the Stage 1 description (TS 22.226). This document describes how the service requirements are realized with these functional entities. As far as possible, existing protocols shall be used for the realization of the global text telephony feature. This may include, e.g., SIP, 3G.324, or circuit-switched voice service as protocol environments, and CTM, AL1 and RTP/text as transmission protocols. It also means usage of existing text presentation format Rec. ITU-T T.140, common to all GTT text conversation environments.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 226 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 226 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223226v700 |
+| ATIS | ATIS.3GPP.23.226V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.226(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.226(R7-7.0.0).zip |
+| TTC | TS-3GA-23.226(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23226rel7v700.pdf |
+
+### 10.3.65 TS 23.228 IP multimedia subsystem (IMS); Stage 2
+
+This document defines the Stage 2 service description for the IP multimedia core network subsystem (IMS), which includes the elements necessary to support IP multimedia (IM) services in UMTS. [ITU-T I.130] describes a three-stage method for characterization of telecommunication services, and [ITU-T Q.65] defines Stage 2 of the method.
+
+This document does not cover the access network functionality except as they relate to provision of IM services. The TS 23.060 describes GPRS. GSM 03.64 contains an overall description of the GSM GPRS radio interface. TS 25.301 contains an overall description of the UMTS terrestrial radio access network.
+
+This document identifies the mechanisms to enable support for IP multimedia applications. In order to align IP multimedia applications wherever possible with non-3GPP IP applications, the general approach is to adopt non-3GPP-specific IP-based solutions.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.228V7.9.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/23/A23228-790.pdf |
+| CCSA | CCSA-TSD-123 228 | 7.9.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 228 | 7.9.0 | Published | 2007-10-12 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223228v790 |
+| ATIS | ATIS.3GPP.23.228V790-2007 | 7.9.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.228(R7-7.7.0) | 7.7.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.228(R7-7.7.0).zip |
+
+### 10.3.66 TS 23.234 3GPP system to wireless local area network (WLAN) interworking; system description
+
+This document specifies system description for interworking between 3GPP systems and wireless local area networks (WLANs). The intent of 3GPP-WLAN interworking is to extend 3GPP services and functionality to the WLAN access environment. The 3GPP-WLAN interworking system provides bearer services allowing a 3GPP subscriber to use a WLAN to access 3GPP PS-based services.
+
+This specification defines a 3GPP system architecture and procedures to do the following:
+
+- Provide access, authentication and authorization (AAA) services to the 3GPP-WLAN interworking system based on subscription.
+- Provide access to the locally connected IP network (e.g., the Internet) if allowed by subscription.
+- Provide WLAN UEs with IP bearer capability to the operator's network and PS services, if allowed by subscription.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 234 | 7.5.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 234 | 7.5.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223234v750 |
+| ATIS | ATIS.3GPP.23.234V750-2007 | 7.5.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.234(R7-7.6.0) | 7.6.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.234(R7-7.6.0).zip |
+| TTC | TS-3GA-23.234(Rel7)v7.5.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23234rel7v750.pdf |
+
+### 10.3.67 TS 23.236 Intra-domain connection of radio access network (RAN) nodes to multiple core network (CN) nodes
+
+This document covers the details for the intra-domain connection of RAN nodes to multiple CN nodes for GSM and UMTS systems. In particular, it details the impacts to GSM and UMTS systems and the Stage 2 procedures for the support of connecting a RNC or BSC to multiple MSC servers or SGSNs. The overall solution is described, and the detailed impacts on the existing specifications are identified.
+
+The reference model to which these procedures apply can be found within TS 23.002. Detailed architectural requirements within the subsystems are contained within the remainder of the 23 series of specifications, e.g., the requirements for the packet-switched (PS) domain are contained within TS 23.060, and the requirements for the bearer independent CS core network are contained in TS 23.205.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.236V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/23/A23236-700.pdf |
+| CCSA | CCSA-TSD-123 236 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 236 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223236v700 |
+| ATIS | ATIS.3GPP.23.236V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.236(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-23.236(R7-7.0.0).zip |
+
+### 10.3.68 TS 23.240 3GPP generic user profile (GUP); architecture (Stage 2)
+
+The objective of specifying the 3GPP generic user profile is to provide a conceptual description to enable harmonized usage of the user-related information located in different entities. Technically, the 3GPP generic user profile provides an architecture, data description and interface with mechanisms to handle the data.
+
+The present document defines the Stage 2 architecture description to the 3GPP generic user profile (GUP), which includes the elements necessary to realize the Stage 1 requirements in 3G TS 22.240.
+
+The present document includes the GUP reference architecture with descriptions of functional entities, and their interfaces and procedures, as well as the high-level information model for the GUP data.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 240 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 240 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223240v700 |
+| ATIS | ATIS.3GPP.23.240V 700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.240(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.240(R7-7.0.0).zip |
+| TTC | TS-3GA-23.240(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23240rel7v700.pdf |
+
+### 10.3.69 TS 23.246 Multimedia broadcast/multicast service (MBMS); architecture and functional description
+
+The present document describes the Stage 2 description (architectural solution and functionalities) for the MBMS bearer service, which includes, together with MBMS user services defined in 3G TS 26.346, all the elements necessary to realize the Stage 1 requirements in 3G TS 22.146 and 3G TS 22.246.
+
+The present document also includes considerations on the manner in which user services should make use of the MBMS bearer service described herein.
+
+The present document includes information applicable to network operators, service providers and manufacturers.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 246 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 246 | 7.4.0 | Published | 2007-10-11 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223246v740 |
+| ATIS | ATIS.3GPP.23.246V 740-2007 | 7.4.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.246(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.246(R7-7.2.0).zip |
+| TTC | TS-3GA-23.246(Rel7)v7.4.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23246rel7v740.pdf |
+
+### 10.3.70 TS 23.251 Network sharing; architecture and functional description
+
+Network sharing is a way for operators to share the heavy deployment costs for mobile networks, especially in the roll-out phase. In the current mobile telephony marketplace, functionality that enables various forms of network sharing is becoming more and more important.
+
+Scenarios and user requirements are described in 3G TR 22.951, while the current document presents the Stage 2 details and descriptions of how these requirements are supported in a 3GPP network.
+
+The present document covers the details of network sharing. It shows how several core network operators can share one radio access network and details the impacts on the network architecture. All UEs shall comply with existing requirements, among them PLMN selection and system information reception. The present document defines additional requirements for network-sharing supporting UEs.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 251 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 251 | 7.0.0 | Published | 2007-06-25 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223251v700 |
+| ATIS | ATIS.3GPP.23.251V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.251(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.251(R7-7.0.0).zip |
+| TTC | TS-3GA-23.251(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23251rel7v700.pdf |
+
+### 10.3.71 TS 23.271 Functional stage 2 description of LCS
+
+The document specifies Stage 2 of the location services (LCS) feature in UMTS and GSM, which provides the mechanisms to support mobile location services for operators, subscribers and third party service providers.
+
+Location services may be considered as a network-provided enabling technology consisting of standardized service capabilities, which enable the provision of location applications. The application(s) may be service-provider specific. The description of the numerous and varied possible location applications which are enabled by this technology are outside the scope of this document. However, clarifying examples of how the functionality being described may be used to provide specific location services may be included.
+
+This Stage 2 service description covers the LCS system functional model for the whole system, the LCS system architecture, state descriptions, message flows, etc.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 271 | 7.9.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 271 | 7.9.0 | Published | 2007-10-11 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223271v790 |
+| ATIS | ATIS.3GPP.23.271V790-2007 | 7.9.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.271(R7-7.8.0) | 7.8.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.271(R7-7.8.0).zip |
+| TTC | TS-3GA-23.271(Rel7)v7.9.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23271rel7v790.pdf |
+
+### 10.3.72 TS 23.278 Customized applications for mobile network enhanced logic (CAMEL) Phase 4 – Stage 2; IM CN interworking
+
+This document specifies the Stage 2 description for the customized applications for mobile network enhanced logic (CAMEL) feature which provides the mechanisms to support services for the IP multimedia core network (IM CN) subsystem.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 278 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 278 | 7.1.0 | Published | 2006-05-31 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423278v710 |
+| ATIS | ATIS.3GPP.23.278V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.278(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.278(R7-7.1.0).zip |
+| TTC | TS-3GA-23.278(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23278rel7v710.pdf |
+
+### 10.3.73 TS 23.279 Combining circuit switched (CS) and IP multimedia subsystem (IMS) services; Stage 2
+
+The document provides architectural details to combine CS services and IMS services for using them in parallel between the same two users in a peer-to-peer context. The document provides a detailed description of how capabilities and identities are exchanged to enable the combination of CS and IMS services between the same two UEs.
+
+The present document includes the following capabilities that enable the combination of CS and IMS services:
+
+- Radio capability exchange.
+- SIP based UE terminal capability exchange.
+- MSISDN number exchange in SIP.
+
+- Establishing an IMS session in parallel to an ongoing CS call between the same two UEs.
+- Establishing a CS call in parallel to an ongoing IMS session between the same two users UEs.
+- Network support for establishing multimedia sessions between a UE that uses IMS origination and a UE that uses CS termination
+
+The individual CS call or IMS service that are combined are described in their respective specifications.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 279 | 7.7.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 279 | 7.7.0 | Published | 2007-10-12 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0223279v770 |
+| ATIS | ATIS.3GPP.23.279V770-2007 | 7.7.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.279(R7-7.6.0) | 7.6.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.279(R7-7.6.0).zip |
+| TTC | TS-3GA-23.279(Rel7)v7.7.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23279rel7v770.pdf |
+
+### 10.3.74 TS 23.333 Multimedia resource function controller (MRFC) – Multimedia resource function processor (MRFP) Mp interface: Procedures descriptions
+
+This specification describes the functional requirements and information flows that generate procedures between the multimedia resource function controller (MRFC) and the multimedia resource function processor (MRFP), the Mp interface.
+
+This specification is limited to information flows relevant to the Mp interface; in order to define these procedures and make the functional requirements clear some triggers from an external interface may be described; these may be specified within the Mr interface, for example, or within an AS in which the MRFC function resides. However, for the overall stage 2 procedures of IMS, see 3GPP TS 23.228.
+
+The protocol on the Mp interface is defined to comply with ITU-T H.248.1 gateway control protocol; see [ITU-T H.248.1]. The goal of this specification is to provide the input to defining a formal Profile within the H.248 protocol toolbox specifically for the Mp application.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 333 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 123 333 | 7.2.0 | Published | 2007-10-11 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0423333v720 |
+| ATIS | ATIS.3GPP.23.333V720-2007 | 7.2.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-23.333(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-23.333(R7-7.1.0).zip |
+| TTC | TS-3GA-23.333(Rel7)v7.2.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts23333rel7v720.pdf |
+
+### 10.3.75 TR 23.903 Redial solution for voice-video switching
+
+Many 3GPP operators regard circuit switched video services as a key part of UMTS. However, there is a strong desire to have an effective and user-friendly method of switching between voice and video services when the user desires and/or when radio conditions change and video mode is no longer available.
+
+Following a study of alternative mechanisms, this Technical Report describes the idle mode redial mechanism which 3GPP-based systems can use to enhance switching between voice and video services.
+
+The present document describes the idle mode redial mechanism which 3GPP-based systems can use to enhance switching between circuit-switched voice and video services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 903 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 123 903 | 7.0.0 | Published | 2007-06-25 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0223903v700 |
+| ATIS | ATIS.3GPP.23.903V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TR-3GA-23.903(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr23903rel7v700.pdf |
+
+### 10.3.76 TR 23.919 Direct tunnel deployment guideline
+
+The present document contains deployment guidelines for the use of direct tunnelling of user plane data between the RNC and the GGSN (earlier known as the one tunnel approach).
+
+This report highlights the impacts of the 3GPP Release 7 direct tunnel solution to the current UMTS system in order to guide equipment development and network deployment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 919 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 123 919 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=DTR/TSGS-0223919v700 |
+| ATIS | ATIS.3GPP.23.919V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TR-3GA-23.919(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr23919rel7v700.pdf |
+
+### 10.3.77 TR 23.976 Push architecture
+
+The purpose of this technical report is to analyse the service requirements for push services as defined in 3GPP TS 22.174 "Push service; Stage 1".
+
+This technical report describes methods for supporting push services by 3GPP delivery networks. The mechanisms described apply to existing delivery networks for the 3GPP packet-switched (PS) domain, circuit-switched (CS) domain, IP multimedia core network subsystem (IMS), multimedia broadcast/multicast service (MBMS), and wireless local area network (WLAN). Any necessary changes identified during this work will be introduced by means of change requests to the appropriate specifications.
+
+The definition of push functionality that applies to push application servers is outside the scope of this work. The definition of push functionality that is best implemented in push application servers such as a push proxy and push initiator will be undertaken by other standards bodies and industry forums.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 976 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 123 976 | 7.0.0 | Published | 2007-06-25 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0223976v700 |
+| ATIS | ATIS.3GPP.23.976V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TR-3GA-23.976(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr23976rel7v700.pdf |
+
+### 10.3.78 TR 23.977 Bandwidth and resource savings and speech enhancements for circuit-switched (CS) networks (BARS)
+
+The objective of this technical report is to identify the full set of requirements for bandwidth and resource savings and improved speech quality, with specific consideration to networks supporting A/Gb mode and the bearer independent circuit-switched core network (BICN). The different architectural solutions to meet these requirements will be assessed.
+
+Consideration shall be made to existing architectures and solutions to provide harmony between 2G nodes, UMTS nodes and external networks (PSTN/ISDN). Backward compatibility to existing solutions and ease of network introduction/upgrade shall be given high importance.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-23.977V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/23/A23977-700.pdf |
+| CCSA | CCSA-TSD-123 977 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 123 977 | 7.0.0 | Published | 2007-06-25 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0223977v700 |
+| ATIS | ATIS.3GPP.23.977V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.3.79 TR 23.979 3GPP enablers for open mobile alliance (OMA) push-to-talk over cellular (PoC) services; Stage 2
+
+The present document studies the architectural requirements in order to enable services like PoC over 3GPP systems. The report looks into aspects of using 3GPP PS domain and radio access technologies (GERAN, UTRAN) for bearer services and IMS for reachability and connectivity for applications like PoC.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 979 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 123 979 | 7.0.0 | Published | 2007-06-25 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0223979v700 |
+| ATIS | ATIS.3GPP.23.979V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TR-3GA-23.979(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr23979rel7v700.pdf |
+
+### 10.3.80 TR 23.981 Interworking aspects and migration scenarios for IPv4-based IMS implementations
+
+3GPP specifications design the IMS to use exclusively IPv6; however, early IMS implementations and deployments may use IPv4, as specified in clause 5.1 of 3G TS 23.221. Therefore, it is understood that there will exist IPv4-based IMS implementations, namely initial IMS implementations and IMS implementations based on 3GPP2 specifications. This is the motivation to study interworking and migration scenarios related to IPv4-based IMS implementations.
+
+The present document studies interworking and migration scenarios related to IPv4-based IMS implementations. The study provides guidelines for operators and vendors on interworking aspects of IPv4-based IMS implementations, and provides guidelines on migrating to 3GPP IMS using IPv6.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-123 981 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 123 981 | 7.0.0 | Published | 2007-06-25 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0223981v700 |
+| ATIS | ATIS.3GPP.23.981V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TR-3GA-23.981(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr23981rel7v700.pdf |
+
+## 10.4 24-series, Signalling protocols (User equipment – core network)
+
+### 10.4.1 TS 24.002 GSM-UMTS public land mobile network (PLMN) access reference configuration
+
+The document describes the reference configuration for access to a PLMN.
+
+A user accesses a PLMN via a number of interfaces, including the MS-BS (in A/Gb mode and GERAN Iu mode) and UE-UTRAN (in UTRAN Iu mode) interface. The purpose of this Technical Specification is to indicate the possible access arrangements that may be used in conjunction with the MS-BS (in A/Gb mode and GERAN Iu mode) and UE-UTRAN (in UTRAN Iu mode) interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 002 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 002 | 7.0.0 | Published | 2007-07-05 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0124002v700 |
+| ATIS | ATIS.3GPP.24.002V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.002(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-24.002(R7-7.0.0).zip |
+| TTC | TS-3GA-24.002(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24002rel7v700.pdf |
+
+### 10.4.2 TS 24.007 Mobile radio interface signalling layer 3 – General aspects
+
+The document defines the principal architecture of layer 3 and its sublayers on the GSM Um interface, i.e., the interface between mobile station (MS) and network; for the CM sublayer, the description is restricted to paradigmatic examples, call control, supplementary services, and short message services for non-GPRS services. It also defines the basic message format and error handling applied by the layer 3 protocols.
+
+For non-GPRS services, the communication between sublayers and adjacent layers and the services provided by the sublayers are distributed by use of abstract service primitives. But only externally observable behaviour resulting from the description is normatively prescribed by this document.
+
+For GPRS services, in addition, the local information transfer and stimuli sent between sublayers is informatively included within Annex C of the document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 007 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 007 | 7.0.0 | Published | 2006-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0124007v700 |
+| ATIS | ATIS.3GPP.24.007V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.007(R7-7.0.0) | 7.0.0 | Approved | 2006-04-19 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.007(R7-7.0.0).zip |
+| TTC | TS-3GA-24.007(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24007rel7v700.pdf |
+
+### 10.4.3 TS 24.008 Mobile radio interface layer 3 specification; Core network protocols; Stage 3
+
+The document specifies the procedures used at the radio interface core network protocols within the 3rd generation mobile telecommunications system and the digital cellular telecommunications system.
+
+It specifies the procedures used at the radio interface (reference point Um or Uu, see TS 24.002 or TS 23.002) for Call Control (CC), mobility management (MM), and session management (SM).
+
+These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The control channels are described in TS 44.003 and TS 25.301.
+
+The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in TS 24.007.
+
+The procedures currently described in this TS are for the call control of circuit-switched connections, session management for GPRS services, mobility management and radio resource management for circuit-switched and GPRS services.
+
+TS 24.010 contains functional procedures for support of supplementary services.
+
+TS 24.011 contains functional procedures for support of point-to-point short message services.
+
+TS 24.012 contains functional description of short message – cell broadcast.
+
+TS 44.060 contains procedures for radio link control and medium access control (RLC/MAC) of packet data physical channels.
+
+TS 24.071 contains functional descriptions and procedures for support of location services.
+
+NOTE – "layer 3" includes the functions and protocols described in this Technical Specification. The terms "data link layer" and "layer 2" are used interchangeably to refer to the layer immediately below layer 3.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 008 | 7.9.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 008 | 7.9.0 | Published | 2007-10-16 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0124008v790 |
+| ATIS | ATIS.3GPP.24.008V790-2007 | 7.9.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.008(R7-7.7.0) | 7.7.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.008(R7-7.7.0).zip |
+| TTC | TS-3GA-24.008(Rel7)v7.9.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24008rel7v790.pdf |
+
+#### 10.4.4 TS 24.010 Mobile radio interface layer 3 – Supplementary services specification – General aspects
+
+The document gives the general aspects of the specification of supplementary services at the layer 3 radio interface.
+
+TS 24.08x and 24.09x-series specify the procedures used at the radio interface (reference point Um as defined in TS 24.002) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
+
+TS 44.008 and TS 24.080 specify the formats and coding for the supplementary services.
+
+Definitions and descriptions of supplementary services are given in TS 22.004 and TS 22.08x and 22.09x-series.
+
+Technical realization of supplementary services is described in TS 23.011 and GSM 23.08x and 23.09x-series.
+
+The procedures for call control, mobility management and radio resource management at the layer 3 radio interface are defined in TS 24.007 and TS 44.008.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 010 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 010 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0424010v700 |
+| ATIS | ATIS.3GPP.24.010V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.010(R7-7.0.0) | 7.0.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.010(R7-7.0.0).zip |
+| TTC | TS-3GA-24.010(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24010rel7v700.pdf |
+
+#### 10.4.5 TS 24.011 Point-to-point (PP) short message service (SMS) support on mobile radio interface
+
+The document specifies the procedures used across the mobile radio interface by the signalling layer 3 function short message control (SMC) and short message relay function (SM-RL) for both circuit switched in A/Gb mode and GPRS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 011 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 011 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0124011v700 |
+| ATIS | ATIS.3GPP.24.011V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.011(R7-7.0.0) | 7.0.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.030(R7-7.2.0).zip |
+| TTC | TS-3GA-24.011(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24011rel7v700.pdf |
+
+#### 10.4.6 TS 24.022 Radio link protocol (RLP) for circuit-switched bearer and teleservices
+
+The document specifies the radio link protocol (RLP) for circuit-switched data transmission within the GSM and UMTS PLMN. RLP covers the Layer 2 functionality of the ISO OSI reference model [ISO/IEC 7498-1]. It is based on ideas contained in [ISO/IEC 3309], [ISO/IEC 4335] and [ISO/IEC 7809] (HDLC of ISO) as well as [ITU-T X.25] and [ITU-T Q.92x] (LAP-B and LAP-D of ITU, respectively). RLP has been tailored to the special needs of digital radio transmission. RLP provides to its users the OSI data link service [ISO/IEC 8886].
+
+RLP is intended for use with non-transparent data-transfer. Protocol conversion may be provided for a variety of protocol configurations. Those foreseen immediately are:
+
+- Character-mode protocols using start-stop transmission (IA5);
+- X.25 LAP-B.
+
+For reasons of better presentation, material about protocol conversion has been placed within those Specifications concerned with the relevant Terminal Adapters, i.e., TS 27.002 for the asynchronous case and TS 27.003 for the synchronous case. Care must be taken that that material also applies to interworking functions; see TS 29.007.
+
+The present document is valid for a PLMN in A/Gb mode as well as in Iu mode. If text applies only for one of these systems, it is explicitly mentioned by using the terms "A/Gb mode" and "Iu mode". Please note that the Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 022 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 022 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0324022v700 |
+| ATIS | ATIS.3GPP.24.022V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.022(R7-7.0.0) | 7.0.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.022(R7-7.0.0).zip |
+| TTC | TS-3GA-24.022(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24022rel7v700.pdf |
+
+#### 10.4.7 TS 24.030 Location services LCS; Supplementary service operations; Stage 3
+
+The document gives the Stage 3 description of the location service (LCS) operations for mobile station. These operations shall apply to both CS and PS domain.
+
+The group of location services operations is divided into two different classes:
+
+- Network-initiated location services operations;
+- Mobile-initiated location services operations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 030 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 030 | 7.2.0 | Published | 2007-07-05 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0424030v720 |
+| ATIS | ATIS.3GPP.24.030V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.030(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.030(R7-7.2.0).zip |
+| TTC | TS-3GA-24.030(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24030rel7v720.pdf |
+
+#### 10.4.8 TS 24.067 Enhanced multi-level precedence and pre-emption service (eMLPP); Stage 3
+
+The document specifies the procedures used at the radio interface (reference point Um for GSM and reference point Uu for UMTS as defined in TS 24.002) for normal operation, invocation, registration and interrogation of the enhanced multi-level precedence and pre-emption Service (eMLPP) supplementary service. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
+
+In TS 24.010, the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
+
+TS 24.080 specifies the formats and coding for the supplementary services.
+
+Definitions and descriptions of supplementary services are given in TS 22.004 and TS 22.08x and in the 22.09x-series. TS 22.067 is related specially to eMLPP.
+
+Technical realization of supplementary services is described in TS 23.011 and TS 23.08x and in the 23.09x-series.
+
+TS 23.067 is related specially to eMLPP.
+
+The procedures for call control, mobility management at the layer 3 radio interface are defined in TS 24.007 and TS 24.008.
+
+The procedures for radio resource management at layer 3 radio interface are defined in TS 44.018 and TS 25.331.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 067 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 067 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0424067v700 |
+| ATIS | ATIS.3GPP.24.067V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.067(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.067(R7-7.0.0).zip |
+| TTC | TS-3GA-24.067(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24067rel7v700.pdf |
+
+#### 10.4.9 TS 24.072 Call deflection (CD) supplementary service; Stage 3
+
+This global system for mobile communications Technical Specification specifies the procedures used at the radio interface (reference point Um as defined in TS 44.002) for normal operation of call deflection (CD) supplementary service. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 072 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 072 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0424072v700 |
+| ATIS | ATIS.3GPP.24.072V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.072(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.072(R7-7.0.0).zip |
+| TTC | TS-3GA-24.072(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24072rel7v700.pdf |
+
+#### 10.4.10 TS 24.080 Mobile radio interface Layer 3 supplementary service specification – Formats and coding
+
+The document contains the coding of information necessary for the support of supplementary service operation on the mobile radio interface layer 3.
+
+This document gives the functional definitions and contents of messages for call-independent supplementary service operations. Messages necessary for the support of call-related supplementary service operations are defined in TS 24.008.
+
+This document gives the general format and coding for messages used for call-independent supplementary service and the format and coding of information elements used for both call-related and call-independent supplementary service operations.
+
+This document gives the specification of the call-related and call-independent supplementary service operations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 080 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 080 | 7.4.0 | Published | 2007-10-11 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0424080v740 |
+| ATIS | ATIS.3GPP.24.080V740-2007 | 7.4.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.080(R7-7.3.0) | 7.3.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.080(R7-7.3.0).zip |
+| TTC | TS-3GA-24.080(Rel7)v7.4.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24080rel7v740.pdf |
+
+#### 10.4.11 TS 24.081 Line identification supplementary services; Stage 3
+
+The document specifies the procedures used at the radio interface for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of line identification supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
+
+In 3G TS 24.010, the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
+
+3G TS 24.080 specifies the formats and coding for the supplementary services.
+
+Definitions and descriptions of supplementary services are given in 3G TS 22.004 and 3G TS 22.08x and in the 3G TS 22.09x-series. 3G TS 22.081 is related specially to line identification supplementary services.
+
+Technical realization of supplementary services is described in 3G TS 23.011 and in the 3G TS 23.08x and in the 3G TS 23.09x-series. 3G TS 23.081 is related specially to line identification supplementary services.
+
+The procedures for call control, mobility management and radio resource management at the layer 3 radio interface are defined in 3G TS 24.007 and 3G TS 24.008.
+
+The following supplementary services belong to the line identification supplementary services and are described in this document:
+
+- Calling line identification presentation (CLIP);
+- Calling line identification restriction (CLIR);
+- Connected line identification presentation (COLP);
+- Connected line identification restriction (COLR).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 081 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 081 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0424081v700 |
+| ATIS | ATIS.3GPP.24.081V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.081(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-24.081(R7-7.0.0).zip |
+| TTC | TS-3GA-24.081(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24081rel7v700.pdf |
+
+#### 10.4.12 TS 24.082 Call forwarding (CF) supplementary service; Stage 3
+
+This document specifies the procedures used at the radio interface (reference point Um as defined in TS 24.002) for normal operation, registration, erasure, activation, deactivation, interrogation and network invocation of call offering supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
+
+In TS 24.010, the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
+
+TS 24.080 specifies the formats and coding for the supplementary services.
+
+Definitions and descriptions of supplementary services are given in TS 22.004 and TS 22.08x and in the TS 22.09x-series. TS 22.082 is related specially to call offering supplementary services.
+
+Technical realization of supplementary services is described in TS 23.011 and TS 23.08x and in the TS 23.09x-series. TS 23.082 is related specially to call offering supplementary services.
+
+The procedures for call control, mobility management and radio resource management at the layer 3 radio interface are defined in TS 24.007 and TS 24.008.
+
+The following supplementary services belong to the call offering supplementary services and are described in this document:
+
+- Call forwarding unconditional (CFU);
+- Call forwarding on mobile subscriber busy (CFB);
+- Call forwarding on no reply (CFNRy);
+- Call forwarding on mobile subscriber not reachable(CFNRc).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 082 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 082 | 7.1.0 | Published | 2007-10-11 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0424082v710 |
+| ATIS | ATIS.3GPP.24.082V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.082(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.082(R7-7.0.0).zip |
+| TTC | TS-3GA-24.082(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24082rel7v710.pdf |
+
+#### **10.4.13 TS 24.083 Call waiting (CW) and call hold (HOLD) supplementary service; Stage 3**
+
+The document specifies the procedures used at the radio interface (reference point Um as defined in TS 24.002) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of call completion supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
+
+In TS 24.010, the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
+
+TS 24.080 specifies the formats and coding for the supplementary services.
+
+Definitions and descriptions of supplementary services are given in TS 22.004 and TS 22.08x and in the TS 22.09x-series. TS 22.083 is related specially to call completion supplementary services.
+
+Technical realization of supplementary services is described in TS 23.011 and TS 23.08x and in the TS 23.09x-series.
+
+TS 23.083 is related specially to call completion supplementary services.
+
+The procedures for call control, mobility management and radio resource management at the layer 3 radio interface are defined in TS 24.007 and TS 24.008.
+
+The following supplementary services belong to the call completion supplementary services and are described in this document:
+
+- Call waiting (CW);
+- Call hold (HOLD).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 083 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 083 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0424083v700 |
+| ATIS | ATIS.3GPP.24.083V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.083(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.083(R7-7.0.0).zip |
+| TTC | TS-3GA-24.083(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24083rel7v700.pdf |
+
+#### 10.4.14 TS 24.084 Multi-party (MPTY) supplementary service; Stage 3
+
+The document specifies the procedures used at the radio interface (reference point Um as defined in TS 24.002) for normal operation and invocation of multi-party supplementary services.
+
+In TS 24.010, the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
+
+TS 24.080 specifies the formats and coding for the supplementary services.
+
+Definitions and descriptions of supplementary services are given in TS 22.004 and the TS 22.08x and in the TS 22.09x-series.
+
+TS 22.084 is related specially to multi-party supplementary services.
+
+Technical realization of supplementary services is described in TS 23.011 and the TS 23.08x and in the TS 23.09x-series.
+
+TS 23.084 is related specially to multi-party supplementary services.
+
+The procedures for call control, mobility management and radio resource management at the layer 3 radio interface are defined in TS 24.007 and TS 24.008.
+
+The following supplementary service belongs to the multi-party supplementary services and is described in this document:
+
+- Multi-party service (MPTY).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 084 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 084 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0424084v700 |
+| ATIS | ATIS.3GPP.24.084V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.084(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.084(R7-7.0.0).zip |
+| TTC | TS-3GA-24.084(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24084rel7v700.pdf |
+
+#### 10.4.15 TS 24.085 Closed user group (CUG) supplementary service; Stage 3
+
+This Technical Specification (TS) for mobile communications specifies the procedures used at the radio interface (reference point Um as defined in TS 24.002) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of community of interest supplementary services. The provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and causes no signalling on the radio interface.
+
+In TS 24.010, the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
+
+TS 24.080 specifies the formats coding for the supplementary services.
+
+Definitions and descriptions of supplementary services are given in TS 22.004 and TS 22.08x and TS 22.09x-series. TS 22.085 is related to the community of interest supplementary services.
+
+Technical realization of supplementary services is described in technical specifications TS 23.011 and TS 23.08x and 23.09x-series. TS 23.085 is related to the community of interest supplementary services.
+
+The procedures for call control, mobility management and radio resource management at the layer 3 radio interface are defined in TS 24.007 and TS 24.008.
+
+Signalling interworking for supplementary services between GSM 09.02 and TS 24.008 and between GSM 09.02 and TS 24.080 is defined in GSM 09.11.
+
+The following supplementary services belong to the community of interest supplementary services and are described in this Technical Specification:
+
+- Closed user group (CUG).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 085 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 085 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0424085v700 |
+| ATIS | ATIS.3GPP.24.085V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.085(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.085(R7-7.0.0).zip |
+| TTC | TS-3GA-24.085(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24085rel7v700.pdf |
+
+#### 10.4.16 TS 24.086 Advice of charge (AoC) supplementary service; Stage 3
+
+The document specifies the procedures used at the radio interface (reference point Um as defined in TS 24.002) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of charging supplementary services. The provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and causes no signalling on the radio interface.
+
+In TS 24.010, the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
+
+TS 24.080 specifies the formats and coding for the supplementary services.
+
+Definitions and descriptions of supplementary services are given in TS 22.004 and TS 22.08x and TS 22.09x-series. TS 22.024 and 02.86 are related to the charging supplementary services.
+
+Technical realization of supplementary services is described in TS 23.011 and TS 23.08x and TS 23.09x-series. TS 23.086 is related to the charging supplementary services.
+
+The procedures for call control, mobility management and radio resource management at the layer 3 radio interface are defined in TS 24.007 and TS 24.008.
+
+The following supplementary services belong to the charging supplementary services and are described in this document:
+
+- Advice of charge (Information) (AoCI);
+- Advice of charge (Charging) (AoCC).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 086 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 086 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0424086v700 |
+| ATIS | ATIS.3GPP.24.086V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.086(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.086(R7-7.0.0).zip |
+| TTC | TS-3GA-24.086(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24086rel7v700.pdf |
+
+#### 10.4.17 TS 24.087 User-to-user signalling (UUS) supplementary service; Stage 3
+
+This Technical Specification gives the Stage 3 description of the user-to-user signalling supplementary services.
+
+The user-to-user supplementary service is divided into 3 different services:
+
+- Service 1 (UUS1);
+- Service 2 (UUS2);
+- Service 3 (UUS3).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 087 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 087 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0424087v700 |
+| ATIS | ATIS.3GPP.24.087V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.087(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.087(R7-7.0.0).zip |
+| TTC | TS-3GA-24.087(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24087rel7v700.pdf |
+
+#### 10.4.18 TS 24.088 Call barring (CB) supplementary service; Stage 3
+
+This Technical Specification (TS) specifies the procedures used at the radio interface (reference point Um as defined in TS 24.002) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of call barring supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
+
+In TS 24.010, the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
+
+TS 24.080 specifies the formats and coding for the supplementary services.
+
+Definitions and descriptions of supplementary services are given in TS 22.004, TS 22.08x and TS 22.09x-series.
+
+Technical realization of supplementary services is described in TS 23.011, TS 23.08x and TS 23.09x-series.
+
+The procedures for call control, mobility management and radio resource management at the layer 3 radio interface are defined in TS 24.007 and TS 24.008.
+
+The following supplementary services belong to the call restriction supplementary services and are described in this specification:
+
+- Barring of outgoing calls:
+ - Barring of all outgoing calls (BAOC) (Barring program 1);
+ - Barring of outgoing international calls (BOIC) (Barring program 2);
+ - Barring of outgoing international calls EXCEPT those directed to the home PLMN country (BOIC-exHC) (Barring program 3).
+- Barring of incoming calls:
+ - Barring of all incoming calls (BAIC) (Barring program 1);
+ - Barring of incoming calls when roaming outside the home PLMN country (BIC-Roam) (Barring program 2).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 088 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 088 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0424088v700 |
+| ATIS | ATIS.3GPP.24.088V 700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.088(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.088(R7-7.0.0).zip |
+| TTC | TS-3GA-24.088(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24088rel7v700.pdf |
+
+#### 10.4.19 TS 24.090 Unstructured supplementary service data (USSD); Stage 3
+
+The document gives the Stage 3 description of the unstructured supplementary service data (USSD) operations.
+
+The group of unstructured supplementary service data operations is divided into two different classes:
+
+- Network-initiated unstructured supplementary service data operations;
+- Mobile-initiated unstructured supplementary service data operations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 090 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 090 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0424090v700 |
+| ATIS | ATIS.3GPP.24.090V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.090(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.090(R7-7.0.0).zip |
+| TTC | TS-3GA-24.090(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24090rel7v700.pdf |
+
+#### 10.4.20 TS 24.091 Explicit call transfer (ECT) supplementary service; Stage 3
+
+The document gives the Stage 3 description of the call transfer supplementary services.
+
+The document specifies the procedures used at the radio interface (reference point Um as defined in TS 24.002) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of call transfer supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
+
+In TS 24.010, the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
+
+TS 24.080 specifies the formats and coding for the supplementary services.
+
+Definitions and descriptions of supplementary services are given in TS 22.004, TS 22.08x and TS 22.09x-series. TS 22.091 is related specifically to call transfer supplementary services.
+
+The technical realization of supplementary services is described in TS 23.011, TS 23.08x and TS 23.09x-series. TS 23.091 is related specifically to call transfer supplementary services.
+
+The procedures for call control, mobility management and radio resource management at the layer 3 radio interface are defined in TS 24.007 and TS 24.008.
+
+The following supplementary services belong to the call transfer supplementary services and are described in this document:
+
+- Explicit call transfer (ECT).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 091 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 091 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0424091v700 |
+| ATIS | ATIS.3GPP.24.091V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.091(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.091(R7-7.0.0).zip |
+| TTC | TS-3GA-24.091(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24091rel7v700.pdf |
+
+#### 10.4.21 TS 24.093 Completion of calls to busy subscriber (CCBS); Stage 3
+
+The document gives the Stage 3 description of the completion of calls to busy subscriber (CCBS) supplementary service. The document specifies the procedures used at the radio interface (reference point Um as defined in TS 24.002) for normal operation, activation, deactivation, invocation and interrogation of the completion of calls to busy subscriber supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
+
+In TS 24.010, the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
+
+TS 24.080 specifies the formats and coding for the supplementary services.
+
+Definitions and descriptions of supplementary services are given in TS 22.004, TS 22.08x and TS 22.09x-series. Technical specification TS 22.093 is related specifically to the completion of calls to busy subscriber supplementary service.
+
+The technical realization of supplementary services is described in technical specifications TS 23.011, TS 23.08x and 23.09x-series. TS 23.093 is related specifically to Completion of Calls to busy subscriber supplementary service.
+
+The procedures for call control, mobility management and radio resource management at the layer 3 radio interface are defined in TS 24.007 and TS 24.008.
+
+The following supplementary services belong to the call completion supplementary services and are described in this document:
+
+- Completion of calls to busy subscriber (CCBS).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 093 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 093 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0424093v700 |
+| ATIS | ATIS.3GPP.24.093V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.093(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.093(R7-7.0.0).zip |
+| TTC | TS-3GA-24.093(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24093rel7v700.pdf |
+
+#### 10.4.22 TS 24.096 Name identification supplementary service; Stage 3
+
+This Technical Specification (TS) specifies the procedures used at the radio interface for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of name identification supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
+
+In TS 24.010, the general aspects of the specification of supplementary services at the layer 3 radio interface are given. TS 24.080 specifies the formats and coding for the supplementary services.
+
+Definitions and descriptions of supplementary services are given in TS 22.004 and TS 22.08x and 22.09x-series. TS 22.096 is related specially to name identification supplementary services.
+
+Technical realization of supplementary services is described in TS 23.011 and TS 23.08x and 23.09x-series. Technical specification TS 23.096 is related specially to name identification supplementary services.
+
+The procedures for call control, mobility management and radio resource management at the layer 3 radio interface are defined in TS 24.007 and TS 24.008.
+
+The following supplementary services belong to the name identification supplementary services and are described in this Technical Specification:
+
+- Calling name presentation (CNAP).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 096 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 096 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0424096v700 |
+| ATIS | ATIS.3GPP.24.096V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.096(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.096(R7-7.0.0).zip |
+| TTC | TS-3GA-24.096(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24096rel7v700.pdf |
+
+#### 10.4.23 TS 24.109 Bootstrapping interface (Ub) and network application function interface (Ua); Protocol details
+
+The present document defines Stage 3 for the HTTP Digest AKA [IETF RFC 3310: "*Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)*".] based implementation of Ub interface (UE-BSF) and the HTTP Digest [IETF RFC 2617: "*HTTP Authentication: Basic and Digest Access Authentication*"] and the PSK TLS [IETF RFC 4279: "*Pre-Shared Key Ciphersuites for Transport Layer Security (TLS)*"] based implementation of bootstrapped security association usage over Ua interface (UE-NAF) in generic authentication architecture (GAA) as specified in 3G TS 33.220. The purpose of the Ub interface is to create a security association between UE and BSF for further usage in GAA applications. The purpose of the Ua interface is to use the so created bootstrapped security association between UE and NAF for secure communication.
+
+The present document also defines Stage 3 for the authentication proxy usage as specified in 3G TS 33.222.
+
+The present document also defines Stage 3 for the subscriber certificate enrolment, as specified in 3G TS 33.221, which is one realization of the Ua interface. The subscriber certificate enrolment uses the HTTP Digest-based implementation of bootstrapped security association usage to enrol a subscriber certificate and the delivery of a CA certificate.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 109 | 7.5.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 109 | 7.5.0 | Published | 2007-01-12 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0124109v750 |
+| ATIS | ATIS.3GPP.24.109V750-2007 | 7.5.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.109(R7-7.6.0) | | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.109(R7-7.6.0).zip |
+| TTC | TS-3GA-24.109(Rel7)v7.5.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24109rel7v750.pdf |
+
+#### 10.4.24 TS 24.135 Multicall supplementary service; Stage 3
+
+The document gives the Stage 3 description of the multicall (MC) supplementary service. The document specifies the procedures used by the radio interface for normal operation, registration and interrogation of the multicall supplementary service. Provision, withdrawal, erasure, activation and deactivation of supplementary services is an administrative matter between the mobile subscriber and the service provider and causes no signalling on the radio interface.
+
+3G TS 24.010 describes the general aspects of the specification of supplementary services at the layer 3 radio interface.
+
+3G TS 24.080 specifies the formats and coding for the supplementary services.
+
+Definitions and descriptions of supplementary services are given in 3G TS 22.004, 3G TS 22.072, 3G TS 22.08x, 3G TS 22.09x-series and 3G TS 22.135. 3G TS 22.135 is related specifically to the Multicall supplementary service.
+
+The technical realization of supplementary services are described in 3G TS 23.011, 3G TS 23.072, 3G TS 23.08x, 23.09x-series and 3G TS 23.135. 3G TS 23.135 is related specifically to the Multicall supplementary service.
+
+The procedures for call control and mobility management at the layer 3 radio interface are defined in 3G TS 24.007 and 3G TS 24.008.
+
+The following supplementary services are described in this document:
+
+- Multicall (MC).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 135 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 135 | 7.0.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0424135v700 |
+| ATIS | ATIS.3GPP.24.135V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.135(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.135(R7-7.0.0).zip |
+| TTC | TS-3GA-24.135(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24135rel7v700.pdf |
+
+#### 10.4.25 TS 24.141 Presence service using the IP multimedia (IM) core network (CN) subsystem; Stage 3
+
+The present document provides the protocol details for the presence service within the IP multimedia (IM) core network (CN) subsystem based on the session initiation protocol (SIP) and SIP events as defined in 3G TS 24.229.
+
+Where possible, the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP and SIP events, either directly, or as modified by 3G TS 24.229.
+
+Requirements for manipulation of presence data are defined by use of a protocol at the Ut reference point based on XML configuration access protocol (XCAP) [IETF RFC 4825: "*The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)*"].
+
+The present document is applicable to application servers (ASs) and user equipment (UE) providing presence functionality.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 141 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 141 | 7.4.0 | Published | 2007-10-15 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0124141v740 |
+| ATIS | ATIS.3GPP.24.141V740-2007 | 7.4.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.141(R7-7.4.0) | 7.4.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.141(R7-7.4.0).zip |
+| TTC | TS-3GA-24.141(Rel7)v7.4.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24141rel7v740.pdf |
+
+#### 10.4.26 TS 24.147 Conferencing using the IP multimedia (IM) core network (CN) subsystem; Stage 3
+
+The present document provides the protocol details for conferencing within the IP multimedia core network subsystem (IMS) based on the session initiation protocol (SIP), SIP events, the session description protocol (SDP), the conference policy control protocol (CPCP) and the binary floor control protocol (BFCP).
+
+The present document does not cover the signalling between a MRFC and a MRFP.
+
+Where possible, the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP, SIP events, SDP, CPCP and BFCP, either directly, or as modified by 3G TS 24.229. Where this is not possible, extensions to SIP are defined within the present document. The document has therefore been structured in order to allow both forms of specification.
+
+The present document is applicable to application servers (ASs), multimedia resource function controllers (MRFCs), multimedia resource function processors (MRFP), media gateway control functions (MGCFs) and to user equipment (UE) providing conferencing capabilities.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 147 | 7.6.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 147 | 7.6.0 | Published | 2007-10-12 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0124147v760 |
+| ATIS | ATIS.3GPP.24.147V760-2007 | 7.6.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.147(R7-7.5.0) | 7.5.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.147(R7-7.5.0).zip |
+| TTC | TS-3GA-24.147(Rel7)v7.6.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24147rel7v760.pdf |
+
+#### 10.4.27 TS 24.167 3GPP IMS management object (MO); Stage 3
+
+This document defines a mobile device 3GPP IMS management object. The management object is compatible with open mobile alliance (OMA) device management protocol specifications, version 1.2 and upwards, and is defined using the OMA DM device description framework.
+
+The 3GPP IMS management object consists of relevant parameters that can be managed for the IM CN subsystem. This includes the basic framework defined in 3GPP TS 23.228 and 3GPP TS 24.229, and early IMS as defined in 3GPP TS 23.221.
+
+The IMS management object defines a repository of data into the ME including parameters that are provisioned from the ISIM application (i.e., 3GPP TS 31.103) or, after derivation, from the USIM application (i.e., 3GPP TS 31.102).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 167 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 167 | 7.2.0 | Published | 2007-10-11 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0124167v720 |
+| ATIS | ATIS.3GPP.24.167V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.167(R7-7.3.0) | 7.3.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.167(R7-7.3.0).zip |
+| TTC | TS-3GA-24.167(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24167rel7v720.pdf |
+
+#### 10.4.28 TS 24.173 IMS multimedia telephony communication service and supplementary services; Stage 3
+
+The present document provides the protocol details for multimedia telephony communication service and associated supplementary services in the IP multimedia (IM) core network (CN) subsystem based on the requirements from 3GPP TS 22.173.
+
+Multimedia telephony and supplementary services allow users to establish communications between them and enrich that by enabling supplementary services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 173 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 173 | 7.2.0 | Published | 2007-10-15 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0124173v720 |
+| ATIS | ATIS.3GPP.24.173V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.173(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.173(R7-7.0.0).zip |
+| TTC | TS-3GA-24.173(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24173rel7v720.pdf |
+
+#### **10.4.29 TS 24.206 Voice call continuity between the circuit-switched (CS) domain and the IP multimedia core network (CN) (IMS) subsystem; Stage 3**
+
+Voice call continuity allows users to move between the CS domain and the IP connectivity access network (e.g., WLAN interworking) with home IM CN subsystem functionality.
+
+The present document provides the protocol details for voice call continuity between the IP multimedia (IM) core network (CN) subsystem based on the session initiation protocol (SIP) and the session description protocol (SDP) and the protocols of the 3GPP circuit-switched (CS) domain (CAP, MAP, ISUP, BICC and the NAS call control protocol for the CS access).
+
+This document makes no VCC specific enhancements to SIP, SIP events or SDP, beyond those specified in 3GPP TS 24.229.
+
+The present document is applicable to user equipments (UEs), application servers (ASs) and media gateway control functions (MGCFs) providing voice call continuity capabilities.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|-----------------------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 206 | 7.3.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 206 | 7.3.0 | Published | 2007-10-15 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0124206v730 |
+| ATIS | ATIS.3GPP.24.206V730-2007 | 7.3.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.206(R7-7.4.0) | 7.4.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.206(R7-7.4.0).zip |
+| TTC | TS-3GA-24.206(Rel7)v7.3.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24206rel7v730.pdf |
+
+#### **10.4.30 TS 24.216 Communication continuity management object (MO)**
+
+This document defines the communication continuity management object. The management object is compatible with OMA device management protocol specifications, version 1.2 and upwards, and is defined using the OMA DM device description framework.
+
+The communication continuity management object consists of relevant parameters that can be managed for communication continuity capabilities.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 216 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 216 | 7.2.0 | Published | 2007-10-08 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0124216v720 |
+| ATIS | ATIS.3GPP.24.216V720-2007 | 7.2.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.216(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.216(R7-7.1.0).zip |
+| TTC | TS-3GA-24.216(Rel7)v7.2.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24216rel7v720.pdf |
+
+### 10.4.31 TS 24.229 IP multimedia call control protocol based on SIP and SDP; Stage 3
+
+This document defines a call control protocol for use in the IP multimedia (IM) core network (CN) subsystem based on the session initiation protocol (SIP), and the associated session description protocol (SDP).
+
+This document is applicable to:
+
+- the interface between the user equipment (UE) and the call session control function (CSCF);
+- the interface between the CSCF and any other CSCF;
+- the interface between the CSCF and an application server (AS);
+- the interface between the CSCF and the media gateway control function (MGCF);
+- the interface between the S-CSCF and the media resource function controller (MRFC)
+- the interface between the CSCF and the breakout gateway control function (BGCF);
+- the interface between the BGCF and the MGCF;
+- the interface between the BGCF and any other BGCF; and
+- the interface between the CSCF and an external multimedia IP network.
+
+Where possible, this document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP and SDP. Where this is not possible, extensions to SIP and SDP are defined within this document. The document has therefore been structured in order to allow both forms of specification.
+
+As the IM CN subsystem is designed to interwork with different IP-connectivity access networks (IP-CANs), the IP-CAN independent aspects of the IM CN subsystem are described in the main body and Annex A of this specification. Aspects for connecting a UE to the IM CN subsystem through specific types of IP-CANs are documented separately in the annexes or in separate documents.
+
+NOTE – This document covers only the usage of SIP and SDP to communicate with the entities of the IM CN subsystem. It is possible, and not precluded, to use the capabilities of GPRS to allow a terminal containing a SIP UA to communicate with SIP servers or SIP UAs outside the IM CN subsystem, and therefore utilize the services provided by those SIP servers. The usage of SIP and SDP for communicating with SIP servers or SIP UAs outside the IM CN subsystem is outside the scope of this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 229 | 7.9.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 229 | 7.9.0 | Published | 2007-10-15 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0124229v790 |
+| ATIS | ATIS.3GPP.24.229V790-2007 | 7.9.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.229(R7-7.8.0) | 7.8.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.229(R7-7.8.0).zip |
+| TTC | TS-3GA-24.229(Rel7)v7.9.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24229rel7v790.pdf |
+
+#### 10.4.32 TS 24.234 3GPP system to wireless local area network (WLAN) interworking; User equipment (UE) to network protocols; Stage 3
+
+The present document specifies the network selection, including authentication and access authorization procedures used for the interworking of the 3GPP system and WLANs. In addition to these, the present document also specifies the tunnel management procedures used for establishing an end-to-end tunnel from the WLAN UE to the 3GPP network via the Wu reference point.
+
+The present document is applicable to the WLAN user equipment (UE) and the network. In this technical specification, the network includes the WLAN and 3GPP network.
+
+Tunnel management signalling is carried between WLAN-UE and WLAN by WLAN access technology-specific protocols; however, this signalling is transparent to the WLAN.
+
+Details of the security framework for the end-to-end tunnel establishment are covered in 3G TS 33.234. The transport of the tunnel management signalling between WLAN and 3GPP network and within the 3GPP network (i.e., PDG, 3GPP AAA server and WAG) are covered in 3G TS 29.234.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 234 | 7.5.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 234 | 7.5.0 | Published | 2007-03-23 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0124234v750 |
+| ATIS | ATIS.3GPP.24.234V750-2007 | 7.5.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.234(R7-7.5.0) | 7.5.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.234(R7-7.5.0).zip |
+| TTC | TS-3GA-24.234(Rel7)v7.5.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24234rel7v750.pdf |
+
+#### **10.4.33 TS 24.247 Messaging service using the IP multimedia (IM) core network (CN) subsystem; Stage 3**
+
+This document provides the protocol details for the messaging service within the IP multimedia CN subsystem (IMS) based on the session initiation protocol (SIP), the session description protocol (SDP), the message session relay protocol (MSRP) and the conference policy control protocol (CPCP). The document covers immediate messaging, session-based messaging and session-based messaging conferences, as described in 3G TS 22.340.
+
+Where possible, the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP, SDP, MSRP and other protocols, either directly, or as modified by 3G TS 24.229.
+
+The present document is applicable to application servers (ASs), media resource function controllers (MRFCs), media resource function processors (MRFPs) and to user equipment (UE) providing messaging capabilities.
+
+This document does not cover the signalling between a MRFC and a MRFP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|-----------------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 247 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 247 | 7.2.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0124247v720 |
+| ATIS | ATIS.3GPP.24.247V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.247(R7-7.2.0) | 7.2.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.247(R7-7.2.0).zip |
+| TTC | TS-3GA-24.247(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24247rel7v720.pdf |
+
+#### **10.4.34 TS 24.279 Combining circuit switched (CS) and IP multimedia subsystem (IMS) services; Stage 3**
+
+This document provides the technical realization for the combination of circuit switched calls and IM sessions when using them simultaneously between the same two users.
+
+The present document describes the use of CS and IM services in combination, using the existing procedures that have been defined for CS and IMS. It includes the necessary function as adding an IM session to an ongoing CS call, adding a CS call to an ongoing IM session, supplementary services as they relate to CSICS and supporting capability exchange.
+
+The present document is applicable to UE and application servers providing for the combination of circuit switched calls and IM sessions.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 279 | 7.6.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 279 | 7.6.0 | Published | 2007-10-15 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0124279v760 |
+| ATIS | ATIS.3GPP.24.279V760-2007 | 7.6.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.279(R7-7.4.0) | 7.4.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.279(R7-7.4.0).zip |
+| TTC | TS-3GA-24.279(Rel7)v7.6.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24279rel7v760.pdf |
+
+#### 10.4.35 TS 24.305 Selective disabling of 3GPP user equipment capabilities (SDoUE) management object (MO)
+
+This present document specifies a mobile device selective disabling of 3GPP UE capabilities (SDoUE) management object (MO) and the rules and corresponding behaviour of the UE with regard to the selective disabling of 3GPP UE capabilities, for example, when services or functions are disabled/enabled.
+
+The SDoUE MO is compatible with the OMA device management (DM) protocol specifications, version 1.2 and upwards, and is defined using the OMA DM device description framework (DDF).
+
+The SDoUE MO consists of the relevant parameters that can be managed for selective disabling of 3GPP UE capabilities.
+
+The SDoUE MO defines a repository of data into the ME.
+
+The service requirements for selective disabling of 3GPP UE capabilities are defined in 3GPP TS 22.011.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 305 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 305 | 7.2.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0124305v720 |
+| ATIS | ATIS.3GPP.24.305V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.305(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.305(R7-7.2.0).zip |
+| TTC | TS-3GA-24.305(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24305rel7v720.pdf |
+
+#### 10.4.36 TS 24.341 Support of SMS over IP networks; Stage 3
+
+This document provides the protocol details for SMS over IP within the IP multimedia (IM) core network (CN) subsystem based on the session initiation protocol (SIP) and SIP events as defined in 3GPP TS 24.229.
+
+Where possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP and SIP events, either directly, or as modified by 3GPP TS 24.229.
+
+The present document is applicable to application servers (ASs) and user equipment (UE) providing SMS over IP functionality.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 341 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 124 341 | 7.1.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0124341v710 |
+| ATIS | ATIS.3GPP.24.341V 710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-24.341(R7-7.1.0) | 7.1.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-24.341(R7-7.1.0).zip |
+| TTC | TS-3GA-24.341(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts24341rel7v710.pdf |
+
+#### 10.4.37 TR 24.930 Signalling flows for the session set-up in the IP multimedia core network subsystem (IMS) based on session initiation protocol (SIP) and session description protocol (SDP); Stage 3
+
+The present document gives examples of the session set-up in the IM CN subsystem based on SIP and SDP.
+
+These signalling flows provide detailed signalling flows, which expand on the overview information flows provided in 3GPP TS 23.228. The flows focus on a basic session set-up, i.e., no flows will be provided for topology hiding, for sessions with IBCF involved or for sessions having certain features.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-124 930 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 124 930 | 7.2.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=DTR/TSGC-0124930v720 |
+| ATIS | ATIS.3GPP.24.930V 720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TR-3GA-24.930(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr24930rel7v720.pdf |
+
+## 10.5 26-series, Codecs (speech, video, etc.)
+
+### 10.5.1 TS 26.071 AMR speech codec; General description
+
+The document is an introduction to the speech processing parts of the narrow-band telephony speech service employing the adaptive multi-rate (AMR) speech coder. A general overview of the speech processing functions is given, with reference to the documents where each function is specified in detail.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.071V7.0.1 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26071-700.pdf |
+| CCSA | CCSA-TSD-126 071 | 7.0.1 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 071 | 7.0.1 | Published | 2007-07-25 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426071v701 |
+| ATIS | ATIS.3GPP.26.071V701-2007 | 7.0.1 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.071(R7-7.0.1) | 7.0.1 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.071(R7-7.0.1).zip |
+
+### 10.5.2 TS 26.073 ANSI-C code for the adaptive multi-rate (AMR) speech codec
+
+The document contains an electronic copy of the ANSI-C code for the adaptive multi-rate codec. The ANSI-C code is necessary for a bit-exact implementation of the adaptive multi-rate speech transcoder (TS 26.090), voice activity detection (TS 26.094), comfort noise (TS 26.092), source controlled rate operation (TS 26.093) and example solutions for substituting and muting of lost frames (TS 26.091).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.073V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26073-700.pdf |
+| CCSA | CCSA-TSD-126 073 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 073 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426073v700 |
+| ATIS | ATIS.3GPP.26.073V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.073(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.073(R7-7.0.0).zip |
+
+### 10.5.3 TS 26.074 Mandatory speech codec speech processing functions; Adaptive multi-rate (AMR) speech codec test sequences
+
+The present document specifies the digital test sequences for the adaptive multi-rate (AMR) speech codec. These sequences test for a bit-exact implementation of the adaptive multi-rate speech transcoder (3G TS 26.090), voice activity detection (3G TS 26.094), comfort noise (3G TS 26.092), and source controlled rate operation (3G TS 26.093).
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|--------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-26.074(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.074(R7-7.0.0).zip |
+
+### 10.5.4 TS 26.077 Minimum performance requirements for noise suppresser; Application to the AMR speech encoder
+
+The document specifies recommended minimum performance requirements for noise suppression algorithms intended for application in conjunction with the AMR speech encoder. This specification is for guidance purposes. Noise suppression is intended to enhance the speech signal corrupted by acoustic noise at the input to the AMR speech encoder.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.077V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26077-700.pdf |
+| CCSA | CCSA-TSD-126 077 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TTAT.3G-26.077(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.077(R7-7.0.0).zip |
+| ATIS | ATIS.3GPP.26.077V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.077(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.077(R7-7.0.0).zip |
+
+### 10.5.5 TS 26.090 AMR speech codec; Transcoding functions
+
+The document describes the detailed mapping from input blocks of 160 speech samples in 13-bit uniform PCM format to encoded blocks of 95, 103, 118, 134, 148, 159, 204, and 244 bits and from encoded blocks of 95, 103, 118, 134, 148, 159, 204, and 244 bits to output blocks of 160 reconstructed speech samples. The sampling rate is 8000 samples/s leading to a bit rate for the encoded bit stream of 4.75, 5.15, 5.90, 6.70, 7.40, 7.95, 10.2 or 12.2 kbit/s. The coding scheme for the multi-rate coding modes is the so-called algebraic code-excited linear prediction coder, hereafter referred to as ACELP. The multi-rate ACELP coder is referred to as MR-ACELP.
+
+In the case of discrepancy between the requirements described in the document and the fixed point computational description (ANSI-C code) of these requirements contained in 3G TS 26.073, the description in 3G TS 26.073 will prevail. The ANSI-C code is not described in this document; see 3G TS 26.073 for a description of the ANSI-C code.
+
+The transcoding procedure specified in the document is mandatory for systems using the AMR speech codec.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.090V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26090-700.pdf |
+| CCSA | CCSA-TSD-126 090 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 090 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426090v700 |
+| ATIS | ATIS.3GPP.26.090V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.090(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.090(R7-7.0.0).zip |
+
+### 10.5.6 TS 26.091 AMR speech codec; Error concealment of lost frames
+
+The document defines an error concealment procedure, also termed "frame substitution and muting" procedure, which shall be used by the AMR speech codec receiving end when one or more lost speech or lost silence descriptor (SID) frames are received.
+
+The requirements of this document are mandatory for implementation in all networks and user equipments (UE)s capable of supporting the AMR speech codec. It is not mandatory to follow the bit-exact implementation outlined in this document and the corresponding C source code.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.091V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26091-700.pdf |
+| CCSA | CCSA-TSD-126 091 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 091 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426091v700 |
+| ATIS | ATIS.3GPP.26.091V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.091(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.091(R7-7.0.0).zip |
+
+### 10.5.7 TS 26.092 AMR speech codec; Comfort noise aspects
+
+The document gives the detailed requirements for the correct operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation for the AMR speech codec during source controlled rate (SCR) operation.
+
+The requirements described in this document are mandatory for implementation in all UEs capable of supporting the AMR speech codec.
+
+The receiver requirements are mandatory for implementation in all networks capable of supporting the AMR speech codec, the transmitter requirements only for those where downlink SCR will be used.
+
+In case of discrepancy between the requirements described in this document and the fixed point computational description of these requirements contained in 3G TS 26.073, the description in 3G TS 26.073 will prevail.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.092V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26092-700.pdf |
+| CCSA | CCSA-TSD-126 092 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 092 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426092v700 |
+| ATIS | ATIS.3GPP.26.092V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.092(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-26.092(R7-7.0.0).zip |
+
+#### 10.5.8 TS 26.093 AMR speech codec; Source controlled rate operation
+
+This document describes the source controlled rate (SCR) operation of the adaptive multi-rate speech codec in codec types UMTS\_AMR and GSM\_AMR for the UMTS system. The implementation of this SCR operation is mandatory in all UMTS equipment.
+
+This structure of distributing the various functions between system entities is not mandatory for implementation, as long as the operation on the speech decoder output remains the same.
+
+Annex A describes the discontinuous transmission (DTX) operation of the adaptive multi-rate speech codec in codec types FR\_AMR, HR\_AMR and OHR\_AMR for GERAN. This annex is the former GSM 06.93 (release 98).
+
+Annexes B to E describe the SCR operation of the adaptive multi-rate speech codec in codec types GSM\_EFR, TDMA\_EFR, TDMA\_US1 and PDC\_EFR for the UMTS system.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.093V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26093-700.pdf |
+| CCSA | CCSA-TSD-126 093 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 093 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TS/SGS-0426093v700 |
+| ATIS | ATIS.3GPP.26.093V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.093(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.093(R7-7.0.0).zip |
+
+### 10.5.9 TS 26.094 AMR speech codec; Voice activity detector
+
+The document specifies two alternatives for the voice activity detector (VAD) to be used in the discontinuous transmission (DTX) as described in 3G TS 26.093. Implementers of mobile station and infrastructure equipment conforming to the AMR specifications can choose which of the two VAD options to implement. There are no interoperability factors associated with this choice.
+
+The requirements are mandatory on any VAD to be used either in user equipment (UE) or base station systems (BSS)s that utilize the AMR speech codec.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.094V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26094-700.pdf |
+| CCSA | CCSA-TSD-126 094 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 094 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TS/SGS-0426094v700 |
+| ATIS | ATIS.3GPP.26.094V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.094(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.094(R7-7.0.0).zip |
+
+### 10.5.10 TS 26.101 Mandatory speech codec speech processing functions; Adaptive multi-rate (AMR) speech codec frame structure
+
+The document describes a generic frame format for the adaptive multi-rate (AMR) speech codec. This format shall be used as a common reference point when interfacing speech frames between different elements of the 3G system and between different systems. Appropriate mappings to and from this generic frame format will be used within and between each system element.
+
+Annex A describes a second frame format, which shall be used when octet alignment of AMR frames is required.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.101V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26101-700.pdf |
+| CCSA | CCSA-TSD-126 101 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 101 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426101v700 |
+| ATIS | ATIS.3GPP.26.101V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.101(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.101(R7-7.0.0).zip |
+
+### 10.5.11 TS 26.102 AMR speech codec; Interface to Iu, Uu and Nb
+
+The document specifies the mapping of the AMR generic frame format (TS 26.101) to the Iu Interface (TS 25.415), the Uu interface and the Nb interface (TS 29.415). It further specifies the mapping of enhanced full rate (GSM\_EFR) coded speech and of PCM 64 kbit/s [ITU-T G.711] coded speech to the Nb Interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.102V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26102-710.pdf |
+| CCSA | CCSA-TSD-126 102 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 102 | 7.1.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426102v710 |
+| ATIS | ATIS.3GPP.26.102V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.102(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.102(R7-7.1.0).zip |
+
+### 10.5.12 TS 26.103 Speech codec list for GSM and UMTS
+
+The Technical Specification outlines the codec lists in 3G including both systems, GSM and UMTS, to be used by the out of band transcoder control (OoBTC) protocol to set up a call or modify a call in transcoder free operation (TrFO) and in "transcoder at the edge" scenarios.
+
+The TS further specifies the coding of the supported codec list information elements for the UMTS radio access technology.
+
+The supported codec list IE includes Codec\_Types from the TDMA and PDC systems, to support TFO or TrFO between UMTS and TDMA, or UMTS and PDC.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.103V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26103-700.pdf |
+| CCSA | CCSA-TSD-126 103 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 103 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426103v700 |
+| ATIS | ATIS.3GPP.26.103V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.103(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.103(R7-7.0.0).zip |
+
+### 10.5.13 TS 26.104 ANSI-C code for the floating-point adaptive multi-rate (AMR) speech codec
+
+This Technical Standard (TS) contains an electronic copy of the ANSI-C code for a floating-point implementation of the adaptive multi-rate codec. This floating-point codec specification is mainly targeted to be used in multimedia applications such as the 3G-324M terminal specified in TS 26.110, or in packet-based (e.g., H.323) applications. The bit-exact fixed-point ANSI-C code in TS 26.073 remains the preferred implementation for all applications, but the floating-point codec may be used instead of the fixed-point codec when the implementation platform is better suited for a floating-point implementation. It has been verified that the fixed-point and floating-point codecs interoperate with each other without any artifacts.
+
+The floating-point ANSI-C code in this specification is the only standard conforming non-bit-exact implementation of the adaptive multi-rate speech transcoder (TS 26.090), voice activity detection (TS 26.094), comfort noise generation (TS 26.092), and source controlled rate operation (TS 26.093). The floating-point code also contains example solutions for substituting and muting of lost frames (TS 26.091).
+
+The fixed-point specification in 26.073 shall remain the only allowed implementation for the 3G mandatory speech services and the use of the floating-point codec is strictly limited to other services.
+
+The floating-point encoder in this specification is a non-bit-exact implementation of the fixed-point encoder producing quality indistinguishable from that of the fixed-point encoder. The decoder in this specification is functionally a bit-exact implementation of the fixed-point decoder, but the code has been optimized for speed and the standard fixed-point libraries are not used as such.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.104V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26104-700.pdf |
+| CCSA | CCSA-TSD-126 104 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 104 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426104v700 |
+| ATIS | ATIS.3GPP.26.104V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.104(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.104(R7-7.0.0).zip |
+
+#### 10.5.14 TS 26.110 Codec for circuit-switched multimedia telephony service; General description
+
+This specification introduces the set of specifications that apply to 3G-324M multimedia terminals.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.110V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26110-700.pdf |
+| CCSA | CCSA-TSD-126 110 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 110 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426110v700 |
+| ATIS | ATIS.3GPP.26.110V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.110(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.110(R7-7.0.0).zip |
+
+#### 10.5.15 TS 26.111 Codec for circuit-switched multimedia telephony service; Modifications to H.324
+
+[ITU-T H.324] with Annex C describes a generic multimedia codec for use in error-prone, wireless networks. The scope of the document is the changes, deletions, and additions to those texts necessary to fully specify a multimedia codec for use in 3G networks. Note that this implicitly excludes the network interface and call set-up procedures. Also excluded are any general introductions to the system components.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.111V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26111-700.pdf |
+| CCSA | CCSA-TSD-126 111 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 111 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426111v700 |
+| ATIS | ATIS.3GPP.26.111V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.111(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.111(R7-7.0.0).zip |
+
+### **10.5.16 TS 26.114 IP multimedia subsystem (IMS); Multimedia telephony; Media handling and interaction**
+
+The present document specifies a client for the multimedia telephony service for IMS (MTSI) supporting conversational speech (including DTMF), video and text transported over RTP with the scope to deliver a user experience equivalent to or better than that of circuit switched (CS) conversational services using the same amount of network resources. It defines media handling (e.g., signalling, transport, jitter buffer management, packet-loss handling, adaptation), as well as interactivity (e.g., adding or dropping media during a call). The focus is to ensure a reliable and interoperable service with a predictable media quality, while allowing for flexibility in the service offerings.
+
+The scope includes maintaining backward compatibility in order to ensure seamless interworking with existing services available in the CS domain, such as CS speech and video telephony, as well as with terminals of earlier 3GPP releases. In addition, inter-working with traditional PSTN and emerging TISPAN network is covered.
+
+The specification is written in a forward-compatible way in order to allow additions of media components and functionality in releases after Release 7.
+
+NOTE 1 – MTSI clients can support more than conversational speech, video and text, which is the scope of the present document. See 3GPP TS 22.173 for the definition of the multimedia telephony service for IMS.
+
+NOTE 2 – 3GPP TS 26.235 and 3GPP TS 26.236 do not include the specification of an MTSI client, although they include conversational multimedia applications. Only those parts of 3GPP TS 26.235 and 3GPP TS 26.236 that are specifically referenced by the present document apply to multimedia telephony service for IMS.
+
+NOTE 3 – The present document was started as a conclusion from the study in 3GPP TR 26.914 on optimization opportunities in multimedia telephony for IMS (3GPP TR 22.973).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.114V7.2.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26114-720.pdf |
+| CCSA | CCSA-TSD-126 114 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 114 | 7.2.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426114v720 |
+| ATIS | ATIS.3GPP.26.114V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.114(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.114(R7-7.1.0).zip |
+
+### 10.5.17 TS 26.115 Echo control for speech and multimedia services
+
+The document specifies minimum performance requirements for the gateway echo control of 3G speech and multimedia services. The document is applicable to any narrow-band speech telephony or multimedia service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.115V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26115-700.pdf |
+| CCSA | CCSA-TSD-126 115 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 115 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426115v700 |
+| ATIS | ATIS.3GPP.26.115V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.115(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.115(R7-7.0.0).zip |
+
+### 10.5.18 TS 26.131 Terminal acoustic characteristics for telephony; Requirements
+
+The document is applicable to any terminal capable of supporting narrow-band or wideband telephony, either as a stand-alone service or as the telephony component of a multimedia service. The document specifies minimum performance requirements for the acoustic characteristics of 3G terminals when used to provide narrow-band or wideband telephony.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.131V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26131-700.pdf |
+| CCSA | CCSA-TSD-126 131 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 131 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426131v700 |
+| ATIS | ATIS.3GPP.26.131V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.131(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.131(R7-7.0.0).zip |
+
+#### 10.5.19 TS 26.132 Speech and video telephony terminal acoustic test specification
+
+The present document specifies test methods to allow the minimum performance requirements for the acoustic characteristics of 3G terminals when used to provide narrow-band or wideband telephony to be assessed.
+
+The performance requirements are specified in 3G TS 26.131; the test methods and considerations are specified in the main body of the text.
+
+The present document is applicable to any terminal capable of supporting narrow-band or wideband telephony, either as a stand-alone service or as the telephony component of a multimedia service. The present document specifies test methods to allow the minimum performance requirements for the acoustic characteristics of 3G terminals when used to provide narrow-band or wideband telephony to be assessed.
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|--------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-26.132(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.132(R7-7.0.0).zip |
+
+#### 10.5.20 TS 26.140 Multimedia messaging service (MMS); Media formats and codes
+
+This document specifies the media types, formats and codecs for the MMS within the 3GPP system. The scope of this document extends to codecs for speech, audio, video, still images, bitmap graphics, and other media in general, as well as scene description, multimedia integration and synchronization schemes.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.140V7.1.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26140-710.pdf |
+| CCSA | CCSA-TSD-126 140 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 140 | 7.1.0 | Published | 2007-07-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426140v710 |
+| ATIS | ATIS.3GPP.26.140V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.140(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.140(R7-7.1.0).zip |
+
+### 10.5.21 TS 26.141 IP multimedia system (IMS) messaging and presence; Media formats and codecs
+
+The 3GPP Technical Specifications 3G TS 22.340 and 3G TS 22.141 define the requirements for the 3GPP IP multimedia subsystem (IMS)-based messaging and presence services. This Technical Specification takes the requirements into account when defining the minimal baseline and optional media codecs and message container format to be used by IMS messaging and associated presence service, when supported.
+
+IMS messaging services incorporate one or more of the following messaging types: immediate messaging, deferred delivery messaging, and session-based messaging. With immediate messaging the sender expects immediate message delivery in what is perceived as real time compared with deferred messaging, where the sender expects the network to deliver the message as soon as the recipient becomes available. With session-based messaging, a communications association is established between two or more users before communication can take place. In the simplest form, session-based messaging may be a direct communication between two users. This specification defines the media types and container formats for both the immediate message type and the session-based message type.
+
+The specification provides the ability to have an interoperable baseline set of media types for messaging and presence services, that will simultaneously maximize the technology reuse of the already existing 3GPP services with media types, defined in 3G TS 26.140 and 3G TS 26.234. Simultaneously, the specification will provide the ability to indicate the IMS system about the complete set of UE media and storage capabilities relevant for the IMS messaging and presence services.
+
+The present document specifies the basic media formats and codecs to be used in the IMS messaging and presence services. It defines the mandatory "baseline" set of media types for the services. Additionally, it also targets to allow possible message content type enhancements, either 3GPP-standardized or other generally used media types, in a flexible way.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.141V7.1.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26141-710.pdf |
+| CCSA | CCSA-TSD-126 141 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 141 | 7.1.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426141v710 |
+| ATIS | ATIS.3GPP.26.141V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.141(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.141(R7-7.1.0).zip |
+
+### 10.5.22 TS 26.142 Dynamic and interactive multimedia scenes
+
+DIMS defines a dynamic rich-media system, including a media type, its packaging, delivery, and interaction with the local terminal, user, and other local and remote sub-systems. Enhanced end-user experiences are provided by the coordinated management and synchronization of media and events, combined with end-user interaction.
+
+The DIMS media type can be used as a generic media type, allowing creating dynamic interactive rich-media services and can also benefit, or be used in association with other media types (e.g., audio codecs, video codecs, XHTML browser, etc.).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.142V7.1.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26142-710.pdf |
+| CCSA | CCSA-TSD-126 142 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 142 | 7.1.0 | Published | 2007-10-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426142v710 |
+| ATIS | ATIS.3GPP.26.142V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.142(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.142(R7-7.0.0).zip |
+
+### 10.5.23 TS 26.171 Adaptive multi-rate – wideband (AMR-WB) speech codec; General description
+
+This document is an introduction to the speech processing parts of the wideband telephony speech service employing the adaptive multi-rate wideband (AMR-WB) speech coder. A general overview of the speech processing functions is given, with reference to the documents where each function is specified in detail.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.171V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26171-700.pdf |
+| CCSA | CCSA-TSD-126 171 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 171 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426171v700 |
+| ATIS | ATIS.3GPP.26.171V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.171(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.171(R7-7.0.0).zip |
+
+#### 10.5.24 TS 26.173 ANSI-C code for the adaptive multi-rate – wideband (AMR-WB) speech codec
+
+This document contains an electronic copy of the ANSI-C code for the adaptive multi-rate wideband codec. The ANSI-C code is necessary for a bit-exact implementation of the adaptive multi-rate wideband speech transcoder (3G TS 26.190), voice activity detection (3G TS 26.194), comfort noise (3G TS 26.192), source controlled rate operation (3G TS 26.193) and example solutions for substituting and muting of lost frames (3G TS 26.191).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.173V7.1.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26173-710.pdf |
+| CCSA | CCSA-TSD-126 173 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 173 | 7.1.0 | Published | 2007-10-15 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426173v710 |
+| ATIS | ATIS.3GPP.26.173V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.173(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.173(R7-7.1.0).zip |
+
+#### 10.5.25 TS 26.174 Speech codec speech processing functions; Adaptive multi-rate – wideband (AMR-WB) speech codec test sequences
+
+The present document specifies the digital test sequences for the adaptive multi-rate wideband (AMR-WB) speech codec. These sequences test for a bit-exact implementation of the adaptive multi-rate wideband (AMR-WB) speech transcoder (3G TS 26.190), voice activity detection (3G TS 26.194), comfort noise (3G TS 26.192), and source controlled rate operation (3G TS 26.193).
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|--------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-26.174(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.174(R7-7.0.0).zip |
+
+#### **10.5.26 TS 26.177 Speech enabled services (SES); DSR extended advanced front-end test sequences**
+
+The present document specifies the digital test sequences for the DSR extended advanced front-end speech codec. These sequences can be used to test for a bit-exact implementation of the DSR advanced front-end codec and quantization (3G TS 26.243).
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|--------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-26.177(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.177(R7-7.0.0).zip |
+
+#### **10.5.27 TS 26.190 Speech codec speech processing functions; Adaptive multi-rate – wideband (AMR-WB) speech codec; Transcoding functions**
+
+This Telecommunication Standard (TS) describes the detailed mapping from input blocks of 320 speech samples in 16-bit uniform PCM format to encoded blocks of 132, 177, 253, 285, 317, 365, 397, 461 and 477 bits and from encoded blocks of 132, 177, 253, 285, 317, 365, 397, 461 and 477 bits to output blocks of 320 reconstructed speech samples. The sampling rate is 16 000 samples/s leading to a bit rate for the encoded bit stream of 6.60, 8.85, 12.65, 14.25, 15.85, 18.25, 19.85, 23.05 or 23.85 kbit/s. The coding scheme for the multi-rate coding modes is the so-called algebraic code-excited linear prediction coder, hereafter referred to as ACELP. The multi-rate wideband ACELP coder is referred to as MRWB-ACELP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.190V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26190-700.pdf |
+| CCSA | CCSA-TSD-126 190 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 190 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426190v700 |
+| ATIS | ATIS.3GPP.26.190V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.190(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.190(R7-7.0.0).zip |
+
+#### **10.5.28 TS 26.191 Adaptive multi-rate – wideband (AMR-WB) speech codec; Error concealment of erroneous or lost frames**
+
+This specification defines an error concealment procedure, also termed frame substitution and muting procedure, which shall be used by the AMR-WB speech codec receiving end when one or more erroneous/lost speech or lost silence descriptor (SID) frames are received.
+
+The requirements of this document are mandatory for implementation in all networks and user equipments (UE)s capable of supporting the AMR-WB speech codec. It is not mandatory to follow the bit-exact implementation outlined in this document and the corresponding C source code.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.191V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26191-700.pdf |
+| CCSA | CCSA-TSD-126 191 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 191 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426191v700 |
+| ATIS | ATIS.3GPP.26.191V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.191(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.191(R7-7.0.0).zip |
+
+### **10.5.29 TS 26.192 Speech codec speech processing functions; Adaptive multi-rate – wideband (AMR-WB) speech codec; Comfort noise aspects**
+
+This document gives the detailed requirements for the correct operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation for the AMR wideband (AMR-WB) speech codec during source controlled rate (SCR) operation.
+
+The requirements described in this document are mandatory for implementation in all UEs capable of supporting the AMR-WB speech codec.
+
+The receiver requirements are mandatory for implementation in all networks capable of supporting the AMR-WB speech codec, the transmitter requirements only for those where downlink SCR will be used.
+
+In case of discrepancy between the requirements described in this document and the fixed point computational description of these requirements contained in 3G TS 26.173, the description in 3G TS 26.173 will prevail.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.192V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26192-700.pdf |
+| CCSA | CCSA-TSD-126 192 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 192 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426192v700 |
+| ATIS | ATIS.3GPP.26.192V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.192(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.192(R7-7.0.0).zip |
+
+### 10.5.30 TS 26.193 Adaptive multi-rate – wideband (AMR-WB) speech codec; Source controlled rate operation
+
+This document describes the source controlled rate (SCR) operation of the adaptive multi-rate wideband speech codec. The implementation of this SCR operation is mandatory in all UMTS equipment implementing the adaptive multi-rate wideband speech codec.
+
+The description is structured according to the block diagram in Figure 10.5.30-1. This structure of distributing the various functions between system entities is not mandatory for implementation, as long as the operation on the speech decoder output remains the same.
+
+Annex A describes the discontinuous transmission (DTX) operation of the adaptive multi-rate wideband speech codec in codec type FR\_AMR-WB for the GSM system.
+
+An overall description of the speech processing parts can be found in 3G TS 26.171. An overview of one link SCR operation is shown in Figure 10.5.30-1.
+
+
+
+```
+
+graph LR
+ subgraph TX_SCR_handler [TX SCR handler]
+ SE[Speech encoder]
+ VAD[Voice activity detector]
+ CNPC[Comfort noise parameter computation]
+ end
+ subgraph Network ["Network"]
+ IPC[Information packeting, transport and classification]
+ end
+ subgraph RX_SCR_handler [RX SCR handler]
+ SD[Speech decoder]
+ EC[Error concealment]
+ CNG[Comfort noise generation]
+ end
+ SE -.-> IPC
+ VAD --> IPC
+ CNPC --> IPC
+ IPC -.-> SD
+ IPC --> EC
+ IPC --> CNG
+
+```
+
+The diagram illustrates the flow of data in a source controlled rate (SCR) operation. On the left, the TX SCR handler contains three components: Speech encoder, Voice activity detector, and Comfort noise parameter computation. The Speech encoder sends 'Information bits' (dashed line) to the Network. The Voice activity detector sends 'Mode indication' (solid line) to the Network. The Comfort noise parameter computation sends 'TX\_TYPE' (solid line) to the Network. The Network contains a component for 'Information packeting, transport and classification'. From this component, 'Information bits' (dashed line) are sent to the RX SCR handler. 'Mode indication' (solid line) and 'RX\_TYPE' (solid line) are also sent to the RX SCR handler. The RX SCR handler contains three components: Speech decoder, Error concealment, and Comfort noise generation. The Speech decoder receives the 'Information bits'. The Error concealment receives the 'Mode indication'. The Comfort noise generation receives the 'RX\_TYPE'.
+
+Block diagram of one link SCR operation showing TX SCR handler, Network, and RX SCR handler components and their interactions.
+
+Q.1741.5(08)\_F10.5.30-1
+
+Figure 10.5.30-1 – Block diagram of one link SCR operation
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.193V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26193-700.pdf |
+| CCSA | CCSA-TSD-126 193 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 193 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426193v700 |
+| ATIS | ATIS.3GPP.26.193V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.193(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.193(R7-7.0.0).zip |
+
+### 10.5.31 TS 26.194 Adaptive multi-rate – wideband (AMR-WB) speech codec; Voice activity detector (VAD)
+
+This document specifies the voice activity detector (VAD) to be used in the discontinuous transmission (DTX) as described in 3GPP TS 26.193.
+
+The requirements are mandatory on any VAD to be used either in user equipment (UE) or base station systems (BSS)s that utilize the AMR wideband speech codec.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.194V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26194-700.pdf |
+| CCSA | CCSA-TSD-126 194 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 194 | 7.0.0 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426194v700 |
+| ATIS | ATIS.3GPP.26.194V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.194(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.194(R7-7.0.0).zip |
+
+### 10.5.32 TS 26.201 Adaptive multi-rate – wideband (AMR-WB) speech codec; Frame structure
+
+This document describes a generic frame format for the adaptive multi-rate wideband (AMR-WB) speech codec. This format shall be used as a common reference point when interfacing speech frames between different elements of the 3G system and between different systems. Appropriate mappings to and from this generic frame format will be used within and between each system element.
+
+Annex A of this Technical Specification describes a second frame format which shall be used when octet alignment of AMR-WB frames is required.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.201V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26201-700.pdf |
+| CCSA | CCSA-TSD-126 201 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 201 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426201v700 |
+| ATIS | ATIS.3GPP.26.201V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.201(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.201(R7-7.0.0).zip |
+
+### 10.5.33 TS 26.202 Adaptive multi-rate – wideband (AMR-WB) speech codec; Interface to Iu, Uu, and Nb
+
+This document specifies the mapping of the AMR wideband generic frame format (3G TS 26.201) to the Iu interface (3G TS 25.415), the Uu interface and the Nb interface (3G TS 29.415). It further specifies the mapping of PCM 64 kbit/s [ITU-T G.711] coded speech to the Nb interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.202V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26202-700.pdf |
+| CCSA | CCSA-TSD-126 202 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 202 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426202v700 |
+| ATIS | ATIS.3GPP.26.202V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.202(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.202(R7-7.0.0).zip |
+
+### 10.5.34 TS 26.204 Adaptive multi-rate – wideband (AMR-WB) speech codec; ANSI-C code
+
+This document contains an electronic copy of the ANSI-C code for the floating-point adaptive multi-rate wideband codec. This floating-point codec specification is mainly targeted to be used in multimedia applications or in packet-based applications. The bit-exact fixed-point ANSI-C code in 3G TS 26.173 remains the preferred implementation for all applications, but the floating-point codec may be used instead of the fixed-point codec when the implementation platform is better suited for a floating-point implementation. It has been verified that the fixed-point and floating-point codecs interoperate with each other without any artifacts.
+
+The floating-point ANSI-C code in this document is the only standard conforming non-bit-exact implementation of the adaptive multi-rate wideband speech transcoder (3G TS 26.190), voice activity detection (3G TS 26.194), comfort noise generation (3G TS 26.192), and source controlled rate operation (3G TS 26.193). The floating-point code also contains example solutions for substituting and muting of lost frames (3G TS 26.191).
+
+The fixed-point specification in 3G TS 26.173 shall remain the only allowed implementation for the 3G AMR-WB speech service and the use of the floating-point codec is strictly limited to other services.
+
+The floating-point encoder in this document is a non-bit-exact implementation of the fixed-point encoder producing quality indistinguishable from that of the fixed-point encoder. The decoder in this document is functionally a bit-exact implementation of the fixed-point decoder, but the code has been optimized for speed and the standard fixed-point libraries are not used as such.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.204V7.1.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26204-710.pdf |
+| CCSA | CCSA-TSD-126 204 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 204 | 7.1.0 | Published | 2007-10-15 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426204v710 |
+| ATIS | ATIS.3GPP.26.204V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.204(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-26.204(R7-7.1.0).zip |
+
+### 10.5.35 TS 26.226 Cellular text telephone modem; General description
+
+This Technical Specification (TS) concerns the cellular text telephone modem (CTM). CTM allows reliable transmission of a text telephone conversation alternating with a speech conversation through the existing speech communication paths in cellular mobile phone systems. This reliability is achieved by an improved modulation technique, including error protection, interleaving and synchronization. Together with Recs ITU-T V.18 and T.140, CTM may serve for worldwide applications in text telephony.
+
+A general overview and explanations of possible implementation architectures is provided. CTM is intended for use in end terminals (on the mobile or fixed side) and within the network for the adaptation between CTM and existing traditional text telephone standards.
+
+The CTM transmitter is fully specified and a bit exact C-code reference is provided. An implementation of an example CTM receiver is also described.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.226V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26226-700.pdf |
+| CCSA | CCSA-TSD-126 226 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 226 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426226v700 |
+| ATIS | ATIS.3GPP.26.226V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.226(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.226(R7-7.0.0).zip |
+
+### 10.5.36 TS 26.230 Cellular text telephone modem; transmitter bit exact C-code
+
+This Technical Standard (TS) contains an electronic copy of the ANSI-C code for the cellular text telephone modem (CTM) for reliable transmission of text telephone text via the speech channel of cellular networks. While CTM is generally usable with text in UCS coding, the example application linked to CTM in this document is limited to use the signals and character set of the Baudot type.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.230V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26230-700.pdf |
+| CCSA | CCSA-TSD-126 230 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 230 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426230v700 |
+| ATIS | ATIS.3GPP.26.230V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.230(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.230(R7-7.0.0).zip |
+
+### 10.5.37 TS 26.231 Cellular text telephone modem; minimum performance requirements
+
+This Technical Standard (TS) describes the minimum performance requirements for the cellular text telephone modem (CTM) for reliable transmission of text telephone text via the speech channel of cellular or PSTN networks. The transmitting parts of the cellular text telephone modem are specified in 3G TS 26.226.
+
+CTM is a general technology, independent of text telephone types. The tests are made only for one specific type of text telephone, the Baudot type. The tests are applicable only to a combination of a Baudot codec and CTM and tests the combined performance. A bit-exact implementation of the CTM transmitter as well as an example implementation of the remaining functions of such a combination are provided in 3G TS 26.230.
+
+The test scripts and test vectors required to perform this testing are included in a supplement, which is located in the zip archive ctm\_testing.zip. The path and file names given in this specification refer to the file structures associated with this supplement. A second supplement (zip archive ctm\_score.zip) provides the scoring program that is described in clause 6 of 3G TS 26.231.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.231V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26231-700.pdf |
+| CCSA | CCSA-TSD-126 231 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 231 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426231v700 |
+| ATIS | ATIS.3GPP.26.231V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.231(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.231(R7-7.0.0).zip |
+
+### 10.5.38 TS 26.233 Transparent end-to-end packet-switched streaming service (PSS); General description
+
+The document contains a general description of a transparent packet-switched streaming service in 3G networks. In particular, it defines the usage scenarios, overall high-level end-to-end service concept, and lists terminal-related functional components. It also lists any identified service interworking requirements. PSS protocols and codecs are defined in 3G TS 26.234.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.233V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26233-700.pdf |
+| CCSA | CCSA-TSD-126 233 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 233 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426233v700 |
+| ATIS | ATIS.3GPP.26.233V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.233(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.233(R7-7.0.0).zip |
+
+### 10.5.39 TS 26.234 Transparent end-to-end packet-switched streaming service (PSS); Protocols and codecs
+
+The document specifies the protocols and codecs for the PSS within the 3G system. Protocols for control signalling, capability exchange, scene description, media transport and media encapsulations are specified. Codecs for speech, natural and synthetic audio, video, still images, bitmap graphics, vector graphics, timed text, and text are specified.
+
+The document is applicable to IP-based packet-switched networks.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.234V7.4.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26234-740.pdf |
+| CCSA | CCSA-TSD-126 234 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 234 | 7.4.0 | Published | 2007-10-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426234v740 |
+| ATIS | ATIS.3GPP.26.234V740-2007 | 7.4.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.234(R7-7.3.0) | 7.3.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.234(R7-7.3.0).zip |
+
+### 10.5.40 TS 26.235 Packet-switched conversational multimedia applications; Default codecs
+
+This document introduces the set of default codecs for packet-switched conversational multimedia applications within the 3G IP multimedia subsystem. Visual and sound communication are specifically addressed. The intended applications are assumed to require low-delay, real-time functionality.
+
+This document is applicable, but not limited, to PS video telephony.
+
+The applicability of this specification to GERAN is FFS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.235V7.2.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26235-720.pdf |
+| CCSA | CCSA-TSD-126 235 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 235 | 7.2.0 | Published | 2007-10-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426235v720 |
+| ATIS | ATIS.3GPP.26.235V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.235(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.235(R7-7.2.0).zip |
+
+#### **10.5.41 TS 26.236 Packet-switched conversational multimedia applications; Transport protocols**
+
+This document introduces the required protocols for packet-switched conversational multimedia applications within 3GPP IP multimedia subsystem. Visual and sound communications are specifically addressed. The intended applications are assumed to require low-delay, real-time functionality.
+
+This document describes the required protocol-related elements for 3G PS multimedia terminal:
+
+- required SDP signalling regarding the media type bit rate, packet size, packet transport frequency;
+- usage of RTP payload for media types;
+- bandwidth adaptation;
+- QoS negotiation.
+
+This document is applicable, but not limited, to packet-switched video telephony.
+
+The applicability of this document to GERAN is FFS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|-----------------------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.236V7.2.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26236-720.pdf |
+| CCSA | CCSA-TSD-126 236 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 236 | 7.2.0 | Published | 2007-10-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426236v720 |
+| ATIS | ATIS.3GPP.26.236V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.236(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-26.236(R7-7.1.0).zip |
+
+#### **10.5.42 TS 26.243 ANSI-C code for the fixed-point distributed speech recognition extended advanced front-end**
+
+The present document contains an electronic copy of the ANSI-C code for DSR extended advanced front-end. The ANSI-C code is necessary for a bit-exact implementation of DSR extended advanced front-end.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.243V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26243-700.pdf |
+| CCSA | CCSA-TSD-126 243 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 243 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426243v700 |
+| ATIS | ATIS.3GPP.26.243V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.243(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.243(R7-7.0.0).zip |
+
+#### 10.5.43 TS 26.244 Transparent end-to-end packet-switched streaming service (PSS); 3GPP file format (3GP)
+
+This document defines the 3GPP file format (3GP) as an instance of the ISO base media file format. The definition addresses 3GPP specific features such as codec registration and conformance within the MMS and PSS services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.244V7.2.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26244-720.pdf |
+| CCSA | CCSA-TSD-126 244 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 244 | 7.2.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426244v720 |
+| ATIS | ATIS.3GPP.26.244V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.244(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.244(R7-7.2.0).zip |
+
+#### 10.5.44 TS 26.245 Transparent end-to-end packet-switched streaming service (PSS); Timed text format
+
+The 3GPP transparent end-to-end packet-switched streaming service (PSS) specification consists of six 3GPP TSs: 3G TS 22.233, 3G TS 26.233, 3G TS 26.234, 3G TS 26.244, 3G TS 26.245 and 3G TS 26.246.
+
+The 3G TS 22.233 contains the service requirements for the PSS. The 3G TS 26.233 provides an overview of the PSS. The 3G TS 26.234 provides the details of protocol and codecs used by the PSS. The 3G TS 26.244 defines the 3GPP file format (3GP) used by the PSS and MMS services. The 3G TS 26.246 defines the 3GPP SMIL language profile. The present document defines the timed text format used by the PSS.
+
+The 3G TS 26.244, 3G TS 26.245 and 3G TS 26.246 start with Release 6. Earlier releases of the 3GPP file format, the timed text format and the 3GPP SMIL language profile can be found in 3G TS 26.234.
+
+Timed text is text that is rendered at the terminal, in synchronization with other timed media such as video or audio. Timed text is used for such applications as closed captioning, titling, and other visual annotation of timed media.
+
+This document defines the timed text format relative to the 3GPP file format. This specification defines the format of timed text in downloaded files.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.245V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26245-700.pdf |
+| CCSA | CCSA-TSD-126 245 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 245 | 7.0.0 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426245v700 |
+| ATIS | ATIS.3GPP.26.245V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.245(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.245(R7-7.0.0).zip |
+
+#### **10.5.45 TS 26.246 Transparent end-to-end packet-switched streaming service (PSS); 3GPP SMIL language profile**
+
+The present document includes the specification of the 3GPP SMIL language profile. The 3GPP SMIL language profile is also referred to as "3GPP PSS SMIL Language Profile" (3G TS 26.234) and also just "3GPP SMIL".
+
+The 3GPP SMIL language profile is based on SMIL 2.0 basic and SMIL scalability framework. It is a clean subset of SMIL 2.0 full profile, and a clear superset of SMIL 2.0 basic.
+
+The 3GPP SMIL language profile is used by the PSS and MMS services.
+
+The 3GPP SMIL language profile is in no way restricted to be used with only these services, but can also be used for other services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.246V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26246-700.pdf |
+| CCSA | CCSA-TSD-126 246 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 246 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426246v700 |
+| ATIS | ATIS.3GPP.26.246V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.246(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.246(R7-7.0.0).zip |
+
+#### 10.5.46 TS 26.273 ANSI-C code for the fixed-point extended AMR – wideband (AMR-WB+) codec
+
+This document contains an electronic copy of the ANSI-C code for the fixed-point extended adaptive multi-rate wideband codec. Alternatively, floating-point ANSI-C code is specified in TS 26.304. The floating-point codec/encoder/decoder specified in the present document or the floating-point codec/encoder/decoder specified in TS 26.304 may be used depending on if the implementation platform is better suited for a floating-point or a fixed-point implementation. It has been verified that the fixed-point and floating-point codecs interoperate with each other without any artifacts.
+
+The fixed-point ANSI-C code in the present document defines, besides the floating-point c-code specified in TS 26.304, one valid reference implementation of the extended adaptive multi-rate wideband transcoder (TS 26.290). Standard conformance is enforced by meeting the conformance criteria defined in TS 26.274.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.273V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26273-700.pdf |
+| CCSA | CCSA-TSD-126 273 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 273 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426273v700 |
+| ATIS | ATIS.3GPP.26.273V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.273(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.273(R7-7.0.0).zip |
+
+#### **10.5.47 TS 26.274 Audio codec processing functions; Extended adaptive multi-rate – wideband (AMR-WB+) codec; Conformance testing**
+
+This document specifies test procedures and digital test sequences to be used for conformance testing of implementations of the extended adaptive multi-rate wideband (AMR-WB+) codec.
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|--------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-26.274(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.274(R7-7.0.0).zip |
+
+#### **10.5.48 TS 26.290 Audio codec processing functions; Extended adaptive multi-rate – wideband (AMR-WB+) codec; Transcoding functions**
+
+This Telecommunication Standard describes the detailed mapping from input blocks of monophonic or stereophonic audio samples in 16-bit uniform PCM format to encoded blocks and from encoded blocks to output blocks of reconstructed monophonic or stereophonic audio samples. The coding scheme is an extension of the AMR-WB coding scheme (3G TS 26.194) and is referred to as extended AMR-WB or AMR-WB+ codec. It comprises all AMR-WB speech codec modes including VAD/DTX (TS 26.190) as well as extended functionality for encoding general audio signals such as music, speech, mixed, and other signals.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|-----------------------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.290V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26290-700.pdf |
+| CCSA | CCSA-TSD-126 290 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 290 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426290v700 |
+| ATIS | ATIS.3GPP.26.290V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.290(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.290(R7-7.0.0).zip |
+
+#### **10.5.49 TS 26.304 Extended adaptive multi-rate – wideband (AMR-WB+) codec; floating-point ANSI-C code**
+
+The present document contains an electronic copy of the ANSI-C code for the floating-point extended adaptive multi-rate wideband codec. Alternatively, fixed-point ANSI-C code is specified in 3G TS 26.273. The floating-point codec/encoder/decoder specified in this document or the fixed-point codec/encoder/decoder may be used depending on if the implementation platform is better suited for a floating-point or a fixed-point implementation. It has been verified that the fixed-point and floating-point codecs interoperate with each other without any artifacts.
+
+The floating-point ANSI-C code in the present document defines, besides the fixed-point c-code specified in 3G TS 26.273, one valid reference implementation of the extended adaptive multi-rate wideband transcoder (3G TS 26.290). Standard conformance is enforced by meeting the conformance criteria defined in 3G TS 26.290.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.304V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26304-700.pdf |
+| CCSA | CCSA-TSD-126 304 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 304 | 7.0.0 | Published | 2007-04-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426304v700 |
+| ATIS | ATIS.3GPP.26.304V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.304(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.304(R7-7.0.0).zip |
+
+### 10.5.50 TS 26.346 Multimedia broadcast/multicast service (MBMS); Protocols and codecs
+
+This document defines a set of media codecs, formats and transport/application protocols to enable the deployment of MBMS user services either over the MBMS bearer service or other UMTS bearer services within the 3GPP system.
+
+In this version of the specification, only MBMS download and streaming delivery methods are specified. The present document does not preclude the use of other delivery methods.
+
+The present document includes information applicable to network operators, service providers and manufacturers.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.346V7.5.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26346-750.pdf |
+| CCSA | CCSA-TSD-126 346 | 7.5.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 346 | 7.5.0 | Published | 2007-10-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426346v750 |
+| ATIS | ATIS.3GPP.26.346V750-2007 | 7.5.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.346(R7-7.4.0) | 7.4.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.346(R7-7.4.0).zip |
+
+### 10.5.51 TS 26.401 General audio codec audio processing functions; Enhanced aacPlus general audio codec; General description
+
+This Telecommunication Standard (TS) describes the detailed mapping from an MPEG-4 bitstream containing enhanced aacPlus coded audio to PCM sample output. The enhanced aacPlus audio codec is based on the AAC, SBR and parametric stereo coding tools defined in the MPEG-4 audio standard. In addition, it includes further tools such as error concealment, spline resampler, and stereo-to-mono downmix.
+
+This Telecommunication Standard (TS) also describes the detailed mapping from a PCM sample input to an MPEG-4 bitstream containing enhanced aacPlus coded audio.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.401V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26401-700.pdf |
+| CCSA | CCSA-TSD-126 401 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 401 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426401v700 |
+| ATIS | ATIS.3GPP.26.401V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.401(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.401(R7-7.0.0).zip |
+
+#### **10.5.52 TS 26.402 General audio codec audio processing functions; Enhanced aacPlus general audio codec; Additional decoder tools**
+
+This Telecommunication Standard (TS) describes the error concealment algorithm, SBR parameter downmix and output resampling for the enhanced aacPlus general audio codec (3G TS 26.401).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.402V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26402-700.pdf |
+| CCSA | CCSA-TSD-126 402 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 402 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426402v700 |
+| ATIS | ATIS.3GPP.26.402V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.402(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.402(R7-7.0.0).zip |
+
+#### **10.5.53 TS 26.403 General audio codec audio processing functions; Enhanced aacPlus general audio codec; Encoder specification AAC part**
+
+This Telecommunication Standard (TS) describes the AAC encoder part of the enhanced aacPlus general audio codec (3G TS 26.401).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.403V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26403-700.pdf |
+| CCSA | CCSA-TSD-126 403 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 403 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426403v700 |
+| ATIS | ATIS.3GPP.26.403V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.403(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.403(R7-7.0.0).zip |
+
+#### **10.5.54 TS 26.404 General audio codec audio processing functions; Enhanced aacPlus general audio codec; Enhanced aacPlus encoder SBR part**
+
+This Telecommunication Standard (TS) describes the SBR encoder part of the enhanced aacPlus general audio codec (3G TS 26.401).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.404V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26404-700.pdf |
+| CCSA | CCSA-TSD-126 404 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 404 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426404v700 |
+| ATIS | ATIS.3GPP.26.404V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.404(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.404(R7-7.0.0).zip |
+
+#### **10.5.55 TS 26.405 General audio codec audio processing functions; Enhanced aacPlus general audio codec; Encoder specification parametric stereo part**
+
+This Telecommunication Standard (TS) describes the parametric stereo encoder part of the enhanced aacPlus general audio codec (3G TS 26.401).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.405V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26405-700.pdf |
+| CCSA | CCSA-TSD-126 405 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 405 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426405v700 |
+| ATIS | ATIS.3GPP.26.405V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.405(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.405(R7-7.0.0).zip |
+
+#### **10.5.56 TS 26.410 General audio codec audio processing functions; Enhanced aacPlus general audio codec; Floating-point ANSI-C code**
+
+The present document contains an electronic copy of the ANSI-C code for the floating-point enhanced aacPlus codec (3G TS 26.401).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.410V7.2.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26410-720.pdf |
+| CCSA | CCSA-TSD-126 410 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 410 | 7.2.0 | Published | 2007-10-12 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426410v720 |
+| ATIS | ATIS.3GPP.26.410V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.410(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.410(R7-7.2.0).zip |
+
+#### **10.5.57 TS 26.411 General audio codec audio processing functions; Enhanced aacPlus general audio codec; Fixed-point ANSI-C code**
+
+This document contains an electronic copy of the ANSI-C code for the fixed-point enhanced aacPlus codec as specified in TS 26.401.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.411V7.3.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26411-730.pdf |
+| CCSA | CCSA-TSD-126 411 | 7.3.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 411 | 7.3.0 | Published | 2007-10-12 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426411v730 |
+| ATIS | ATIS.3GPP.26.411V730-2007 | 7.3.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.411(R7-7.3.0) | 7.3.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.411(R7-7.3.0).zip |
+
+### 10.5.58 TS 26.412 Source code for 3GP file format
+
+This document contains the source code of the 3GPP file format as specified in TS 26.244.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.412V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/26/A26412-700.pdf |
+| CCSA | CCSA-TSD-126 412 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 126 412 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0426412v700 |
+| ATIS | ATIS.3GPP.26.412V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-26.412(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-26.412(R7-7.0.0).zip |
+
+### 10.5.59 TR 26.902 Video codec performance
+
+This document comprises a technical report on video codec performance, for packet-switched video-capable multimedia services standardized by 3GPP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.902V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/26/A26902-700.pdf |
+| CCSA | CCSA-TSD-126 902 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 126 902 | 7.0.0 | Published | 2007-07-17 | http://pda.etsi.org/pda/home.asp?wkr=DTR/TSGS-0426902v700 |
+| ATIS | ATIS.3GPP.26.902V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.5.60 TR 26.911 Codec(s) for circuit-switched multimedia telephony service; Terminal Implementor's Guide
+
+This document provides non-mandatory recommendations for the use of the different codec implementation options for the circuit-switched multimedia telephony service which is based on [ITU-T H.324], and in Annex C of [ITU-T H.324] in particular. These Recommendations address issues specific to the 3G operating environment, including guaranteeing sufficient error resilience and interworking between terminals.
+
+The contents of this document are provided for information to assist in high-quality implementation of multimedia telephony terminals. All references to "terminals" in this report are to terminals supporting the Circuit-Switched Multimedia Telephony Service as described in [ITU-T H.324], Recs ITU-T G.723.1, and H.263.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.911V7.1.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/26/A26911-710.pdf |
+| CCSA | CCSA-TSD-126 911 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 126 911 | 7.1.0 | Published | 2006-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0426911v710 |
+| ATIS | ATIS.3GPP.26.911V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.5.61 TR 26.214 Multimedia telephony over IP multimedia subsystem (IMS); Optimization opportunities
+
+This document:
+
+- identifies opportunities for optimization of service quality and efficiency of multimedia telephony over IP in a qualitative sense;
+- provides the basis for developing a set of optional backward-compatible tools implementing such optimizations.
+
+The optimized multimedia telephony targets many different system configurations and operating conditions, e.g., GERAN, UTRAN, interworking between GERAN, UTRAN, GAN, and different PLMNs. Of the various use cases for multimedia telephony, the main focus of the present document is on voice calls, but the focus also includes other core media components, such as video. In particular, areas with optimization opportunities include handling of degraded channels, delay jitter, packet losses, efficiency, interworking with other voice systems, etc.
+
+The scope includes proposing solutions that maintain backward compatibility in order to ensure seamless interworking with existing services available in the CS domain, such as CS voice telephony and 3G-324M, as well as with terminals of earlier 3GPP releases. Alignment with legacy media formats avoids transcoding and even allows realizing at least parts of the optimization gains. All optimizations are hence based on the default codecs specified in TS 26.235 and TS 26.141.
+
+The optimizations identified in this document address mainly media transport and signalling. Most of the SIP signalling is out of scope. Issues regarding registration to the network and/or to IMS at power-on or at other occurrences are not included either.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.914V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/26/A26914-700.pdf |
+| CCSA | CCSA-TSD-126 914 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 126 914 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=DTR/TS/SGS-0426914v700 |
+| ATIS | ATIS.3GPP.26.914V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+#### **10.5.62 TR 26.935 Packet-switched conversational multimedia applications; Performance characterization of default codecs**
+
+The present document provides information on the performances of default speech codecs in packet-switched conversational multimedia applications. The codecs under test are AMR-NB (adaptive multi-rate narrowband) and AMR-WB (adaptive multi-rate wideband). In addition, several ITU-T codecs (G.723.1, G.729, G.722 and G.711) are included in the testing. Experimental test results from the speech quality testing are reported to illustrate the behaviour of these codecs.
+
+The results give information of the performance of PS conversational multimedia applications under various operating and transmission conditions (e.g., considering radio transmission errors, IP packet losses, end-to-end delays, and several types of background noise). The performance results can be used, e.g., as guidance for network planning and to appropriately adjust the radio network parameters.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.935V7.1.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/26/A26935-710.pdf |
+| CCSA | CCSA-TSD-126 935 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 126 935 | 7.1.0 | Published | 2007-10-26 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0426935v710 |
+| ATIS | ATIS.3GPP.26.935V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.5.63 TR 26.936 Performance characterization of 3GPP audio codecs
+
+This document comprises the Technical Report for the characterization of the 3GPP audio codecs, enhanced aacPlus (*Eaac+*) and extended AMR-WB (*AMR-WB+*), standardized by 3GPP in release 6 for packet-switched streaming service (PSS), multimedia messaging service (MMS), multimedia broadcast and multicast service (MBMS), and IMS messaging service and presence service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.936V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/26/A26936-700.pdf |
+| CCSA | CCSA-TSD-126 936 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 126 936 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0426936v700 |
+| ATIS | ATIS.3GPP.26.936V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.5.64 TR 26.937 Transparent end-to-end packet-switched streaming service (PSS); RTP usage model
+
+The objective of this document is to characterize the 3GPP packet-switched streaming service (PSS). In doing so, the document considers the impacts of the underlying network configurations and how the streaming mechanism itself could be optimized.
+
+The scope of this document includes consideration of (non-exhaustive):
+
+- trade-off between radio usage efficiency and streaming QoS;
+- feedback of network conditions and adaptation of stream and/or the transmission of the stream;
+- optimal packetization of the media stream in line with the segmentation within the transport mechanism;
+- error robustness mechanisms (such as retransmission).
+
+Client buffering to ease the QoS requirements on the network and enable more flexibility in how the network transport resources are applied.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.937V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/26/A26937-700.pdf |
+| CCSA | CCSA-TSD-126 937 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 126 937 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0426937v700 |
+| ATIS | ATIS.3GPP.26.937V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.5.65 TR 26.943 Recognition performance evaluations of codecs for speech-enabled services (SES)
+
+This technical report provides information on the recognition performance of the DSR extended advanced front end conducted by speech recognition vendors IBM and scansoft for the selection of a codec for speech-enabled services. The performance results are provided both as absolute word error rates for DSR and AMR-NB/AMR-WB on a range of extensive evaluation databases and as relative word error rate reductions when compared to both the AMR-NB and AMR-WB codecs.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.943V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/26/A26943-700.pdf |
+| CCSA | CCSA-TSD-126 943 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 126 943 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0426943v700 |
+| ATIS | ATIS.3GPP.26.943V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.5.66 TR 26.944 End-to-end multimedia services performance metrics
+
+The present document describes and defines performance metrics for popular multimedia services in 3G networks, including packed-switched streaming service (PSS), multimedia broadcast multicast service (MBMS), video telephony (VT), and IP multimedia subsystem service (IMS). The present document has a top-down approach, which starts with the quality of experience (QoE) parameters and metrics, and then provides end-to-end service QoS (ESQoS) and system quality of service (SQoS) parameters and metrics and mapping between these different layers.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.944V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/26/A26944-700.pdf |
+| CCSA | CCSA-TSD-126 944 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 126 944 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=DTR/TSGS-0426944v700 |
+| ATIS | ATIS.3GPP.26.944V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.5.67 TR 26.946 Multimedia broadcast/multicast service (MBMS) user service guidelines
+
+MBMS user services can be built on top of the MBMS bearer service. This document describes the usage of the two delivery methods, which are defined in TS 26.346. The two delivery methods are streaming and download. Examples of applications using the download delivery method are news and software upgrades. Delivery of live music is an example of an application using the streaming delivery method.
+
+The objective of the document is to provide an overview of the MBMS system, and describes how the MBMS user services use the MBMS bearer services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.946V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/26/A26946-700.pdf |
+| CCSA | CCSA-TSD-126 946 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 126 946 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0426946v700 |
+| ATIS | ATIS.3GPP.26.946V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.5.68 TR 26.975 Performance characterization of the adaptive multi-rate (AMR) speech codec
+
+This document provides background information on the performances of the adaptive multi-rate (AMR) speech codec. Experimental test results from the verification and characterization phases of testing are reported to illustrate the behaviour of AMR in multiple operational conditions.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.975V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/26/A26975-700.pdf |
+| CCSA | CCSA-TSD-126 975 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 126 975 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0426975v700 |
+| ATIS | ATIS.3GPP.26.975V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.5.69 TR 26.976 Performance characterization of the adaptive multi-rate wideband (AMR-WB) speech codec
+
+This document provides information of the AMR wideband (AMR-WB) characterization, verification and selection phases. Experimental test results from the speech quality-related testing are reported to illustrate the behaviour of the AMR-WB codec. Additional information is provided, e.g., on implementation complexity of the AMR-WB codec. Also the verification results for the floating-point version of the AMR-WB codec (3G TS 26.204) are presented.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.976V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/26/A26976-700.pdf |
+| CCSA | CCSA-TSD-126 976 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 126 976 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0426976v700 |
+| ATIS | ATIS.3GPP.26.976V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.5.70 TR 26.978 Results of the adaptive multi-rate (AMR) noise suppression selection phase
+
+The present document provides background information on the performance of the six candidates which were proposed as solutions for publication of an example noise suppression solution for application to the GSM adaptive multi-rate (AMR) speech codec. Experimental test results from the speech quality-related testing are reported to illustrate the behaviour of the candidate algorithms in multiple operational conditions. Additional information is also provided covering data not necessarily directly associated with speech quality (such as complexity, delay, effect on voice activity factor).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.978V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/26/A26978-700.pdf |
+| CCSA | CCSA-TSD-126 978 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 126 978 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0426978v700 |
+| ATIS | ATIS.3GPP.26.978V7 00-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+## 10.6 27-series, Data
+
+### 10.6.1 TS 27.001 General on terminal adaptation functions (TAF) for mobile stations (MS)
+
+The present document is based on the principles of terminal adaptor functions presented in the ITU-T I-series of Recommendations (I.460 to I.463).
+
+The PLMN supports a wide range of voice and non-voice services in the same network. In order to enable non-voice traffic in the PLMN, there is a need to connect various kinds of terminal equipment to the mobile termination (MT). The target of the present document is to outline the functions needed for the terminal adaptation.
+
+The bearer services are described in 3GPP TS 22.002 and the general network configuration is described in 3GPP TS 23.002. The PLMN access reference configuration is defined in 3GPP TS 23.002. The various connection types used in the A/Gb mode or GERAN Iu mode PLMN are presented in 3GPP TR 21.905 and 3GPP TS 29.990. For support of data services between a PLMN and other networks, see 3GPP TS 29.007.
+
+The present document is valid for a 2nd generation PLMN (A/Gb mode) as well as for a 3rd generation PLMN (Iu mode). If text applies only for one of these systems, it is explicitly mentioned by using the terms "A/Gb mode" and "Iu mode". If text applies to both of the systems, but a distinction between the ISDN/PSTN and the PLMN is necessary, the term "PLMN" is used.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-127 001 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 127 001 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0327001v700 |
+| ATIS | ATIS.3GPP.27.001V 700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-27.001(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-27.001(R7-7.0.0).zip |
+| TTC | TS-3GA-27.001(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts27001rel7v700.pdf |
+
+### 10.6.2 TS 27.002 Terminal adaptation functions (TAF) for services using asynchronous bearer capabilities
+
+The document defines the interfaces and terminal adaptation functions (TAFs) integral to a mobile termination (MT) which enable the use of asynchronous bearer services in the PLMN and the attachment of asynchronous terminals to a MT (see TS 44.002 and TS 23.101).
+
+The general aspects of terminal adaptation functions are contained in TS 27.001.
+
+This document covers support of these services for the following interfaces and procedures:
+
+- [ITU-T V.14] procedures;
+- [ITU-T V.21] DTE/DCE interface;
+- [ITU-T V.22 *bis*] DTE/DCE interface;
+- [ITU-T V.32] DTE/DCE procedures;
+- [ITU-T I.420] S interface;
+- [ITU-T V.250] signalling procedures.
+
+The asynchronous data rates between the MT and the IWF are defined in TS 22.002.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-127 002 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 127 002 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0327002v700 |
+| ATIS | ATIS.3GPP.27.002V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-27.002(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-27.002(R7-7.0.0).zip |
+| TTC | TS-3GA-27.002(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts27002rel7v700.pdf |
+
+### 10.6.3 TS 27.003 Terminal adaptation functions (TAFs) for services using synchronous bearer capabilities
+
+The document defines terminal adaptation functions (TAFs) which are integrated in a mobile termination (MT) and which enable the use of synchronous bearer services in the PLMN and the attachment of synchronous terminals to an MT (see TS 24.002). For the case where asynchronous terminals are attached to the TAF when using synchronous bearer services in the PLMN, the reader is referred to TS 27.002 for the asynchronous MT-TAF interface specifics and to this document for synchronous bearer service specifics on the TAF-IWF interface. The general aspects of terminal adaptation functions are contained in specification TS 27.001. This document covers support of synchronous data services (see TS 22.002) for the following interfaces and procedures:
+
+- [ITU-T V.22] DTE/DCE interface;
+- [ITU-T V.22 *bis*] DTE/DCE interface;
+- [ITU-T V.26 *ter*] DTE/DCE interface;
+- [ITU-T X.21 *bis*] DTE/DCE interface;
+
+- [ITU-T X.32] procedure;
+- [ITU-T V.25 *bis*] procedure.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-127 003 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 127 003 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0327003v700 |
+| ATIS | ATIS.3GPP.27.003V 700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-27.003(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-27.003(R7-7.0.0).zip |
+| TTC | TS-3GA-27.003(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts27003rel7v700.pdf |
+
+#### 10.6.4 TS 27.005 Use of data terminal equipment – data circuit-terminating equipment (DTE – DCE) interface for short message service (SMS) and cell broadcast service (CBS)
+
+This Technical Specification (TS) defines three interface protocols for control of SMS functions within a GSM/UMTS mobile telephone from a remote terminal via an asynchronous interface.
+
+This document defines a binary protocol ("Block Mode"). The protocol includes error protection and is suitable for use where the link may not be completely reliable. It will be of particular use where control of remote devices is required. Efficient transfer of binary encoded user data is possible.
+
+This document defines a character-based interface based on "AT" commands ("Text Mode"). This mode is suitable for unintelligent terminals or terminal emulators, and for application software built on command structures like those defined in [ITU-T V.25 *ter*]. Some of the commands defined in clause 3 will also be useful for implementations of clause 2 and/or clause 4, for example enabling an indication of incoming SMS messages.
+
+This document defines a character-based interface with hex-encoded binary transfer of message blocks ("PDU Mode"). This mode is suitable for software drivers based on AT command structures which do not understand the content of the message blocks and can only pass them between the MT and "upper level" software resident in the TE.
+
+In all three modes, the terminal is considered to be in control for SMS/CBS transactions.
+
+This specification considers the mobile termination to be a single entity. Other 3G/GSM Technical Specifications describe the split of functionality between the mobile equipment and (U)SIM.
+
+The three "modes" referred to above are represented in Figure 10.6.4-1.
+
+The "Block mode" is a self-contained mode in its own right, and when entered, control will remain within that mode until the procedures to exit the mode are executed, after which control is returned to the V.25 *ter* "command" state or "on-line command" state.
+
+The "Text" and "PDU" modes are not in themselves V.25 *ter* states but are simply sets of commands that will operate in either the V.25 *ter* "command" state or "on-line command" state. The "Text" and "PDU" modes are transitory states and after each operation, control is automatically
+
+returned to the V.25 *ter* "command" state or "on-line command" state. Whilst in the V.25 *ter* command state, the MS is available to handle incoming and outgoing calls such as data or facsimile.
+
+
+
+Q.1741.5(08)\_F10.6.4-1
+
+Diagram showing the relationship between V.25 ter states and SMS modes. A large circle contains 'V.25 ter "command" state and "on-line command" state'. Inside this circle are two smaller circles labeled 'SMS text mode' and 'SMS PDU mode'. Below the large circle, a rectangle labeled 'SMS block mode' is connected by a line.
+
+**Figure 10.6.4-1 – Block, text and PDU modes**
+
+In the "Block mode" and "PDU" mode, a mobile is not permitted to modify any component of an SMS/CBS message received from the air interface or an SMS message received from a TE, before passing it on, except where TS 23.040 or TS 23.041 defines a "component modification facility" and where this "component modification facility" is supported by the mobile. In the text mode, the mobile may be unable to display characters coded in particular coding schemes. In this case, the mobile shall behave as described in TS 23.038 and assume the coding scheme to be the GSM 7-bit default alphabet.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-27.005V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/27/A27005-700.pdf |
+| CCSA | CCSA-TSD-127 005 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 127 005 | 7.0.0 | Published | 2007-04-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0127005v700 |
+| ATIS | ATIS.3GPP.27.005V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-27.005(R7-7.0.0) | 7.0.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-27.005(R7-7.0.0).zip |
+
+### 10.6.5 TS 27.007 AT command set for user equipment (UE)
+
+The document specifies a profile of AT commands and recommends that this profile be used for controlling mobile termination (MT) functions and GSM/UMTS network services from a terminal equipment (TE) through terminal adaptor (TA). The command prefix +C is reserved for digital cellular in [ITU-T V.25 *ter*]. This document has also the syntax details used to construct these extended GSM/UMTS commands. Commands from [ITU-T V.25 *ter*] and existing digital cellular
+
+standards (TIA IS-99 and TIA IS-135) are used whenever applicable. Some of the new commands are defined in such way that they can be easily applied to MT of networks other than GSM/UMTS. [ITU-T T.31] and [ITU-T T.32] fax AT commands may be used for GSM/UMTS fax transmission from TE. GSM/UMTS short message service AT commands are defined in 3G TS 27.005. GPRS AT commands are defined in clause 10 of this specification. This document assumes an abstract architecture comprising a TE (e.g., a computer) and a MT interfaced by a TA (see Figure 10.6.5-1). The span of control of the defined commands should allow handling any physical implementation that this abstract architecture may lead to:
+
+- TA, MT and TE as three separate entities;
+- TA integrated under the MT cover, and the TE implemented as a separate entity;
+- TA integrated under the TE cover, and the MT implemented as a separate entity;
+- TA and MT integrated under the TE cover as a single entity.
+
+
+
+```
+
+graph LR
+ subgraph USER_APPLICATIONS [USER & APPLICATIONS]
+ TE[TE]
+ end
+ subgraph NETWORK [NETWORK]
+ MT[MT]
+ end
+ TE -- "AT cmds" --> TA[TA]
+ TA -- "responses" --> TE
+ TA -- "MT control" --> MT
+ MT -- "MT status" --> TA
+ MT <--> "Network messages" --> NETWORK
+
+```
+
+Diagram of the abstract architecture showing the interaction between TE, TA, and MT. The TE is connected to USER & APPLICATIONS. The TE sends 'AT cmds' to the TA and receives 'responses' from it. The TA sends 'MT control' to the MT and receives 'MT status' from it. The MT is connected to the NETWORK via 'Network messages'.
+
+Q.1741.5(08)\_F10.6.5-1
+
+**Figure 10.6.5-1 – Set-up**
+
+The commands described in this document may be observed on the link between the TE and the TA. However, most of the commands retrieve information about the MT, not about the TA.
+
+Interface between TE and TA is intended to operate over existing serial [ITU-T V.24] cables, infrared link, and all link types with similar behaviour. For correct operation, many of the defined commands require eight-bit data, and therefore it is recommended that TE-TA link is set to eight bits/byte mode. (For infrared operation implementation, refer to informative references IrDA. For embedding AT commands and data during on-line data state, refer to TIA IS-617 [ITU-T V.80]). Interface between TA and MT is dependent on the interface in the MT.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-27.007V7.4.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/27/A27007-740.pdf |
+| CCSA | CCSA-TSD-127 007 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 127 007 | 7.4.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0127007v740 |
+| ATIS | ATIS.3GPP.27.007V740-2007 | 7.4.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-27.007(R7-7.4.0) | 7.4.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-27.007(R7-7.4.0).zip |
+
+### 10.6.6 TS 27.010 Terminal equipment to user equipment (TE-UE) multiplexer protocol
+
+The document is to define a multiplexing protocol between a UE and a TE. The multiplexing protocol can be used to send any data, for instance, voice, SMS, USSD, fax, etc.
+
+The document describes the protocol, but not the commands or data transported with it.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-27.010V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/27/A27010-700.pdf |
+| CCSA | CCSA-TSD-127 010 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 127 010 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0327010v700 |
+| ATIS | ATIS.3GPP.27.010V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-27.010(R7-7.0.0) | 7.0.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-27.010(R7-7.0.0).zip |
+
+### 10.6.7 TS 27.060 Packet domain; Mobile station (MS) supporting packet-switched services
+
+The document defines the requirements for TE-MT interworking over the R-reference point for the packet domain, within the GSM and 3G systems. It is up to the manufacturer how to implement the various functions but this document and existing Technical Specifications 27.001, 27.002, and 27.003 shall be followed where applicable.
+
+It is the intention that this document shall remain as the specification to develop a MS for the support of packet-switched services and its text includes references to UMTS/GSM standards.
+
+The UMTS/GSM PLMN supports a wide range of voice and non-voice services in the same network. In order to enable non-voice traffic in the PLMN, there is a need to connect various kinds of terminal equipments to the mobile station (MS). This document defines the requirements for TE-MT interworking over the R-reference point for the packet domain, including the protocols and signalling needed to support packet-switched services, as defined in TS 22.060 and TS 23.060.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-127 060 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 127 060 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0327060v700 |
+| ATIS | ATIS.3GPP.27.060V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-27.060(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-27.060(R7-7.0.0).zip |
+| TTC | TS-3GA-27.060(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts27060rel7v700.pdf |
+
+## 10.7 28-series, Signalling protocols (RSS-CN)
+
+### 10.7.1 TS 28.062 In-band tandem free operation (TFO) of speech codecs; Service description; Stage 3
+
+The document contains the service description for the in-band signalling protocol for the support of tandem free operation of speech codecs in GSM and GSM-evolved 3G systems.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-28.062V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/28/A28062-700.pdf |
+| CCSA | CCSA-TSD-128 062 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 128 062 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0428062v700 |
+| ATIS | ATIS.3GPP.28.062V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-28.062(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-28.062(R7-7.0.0).zip |
+
+## 10.8 29-series, Signalling protocols (NSS)
+
+### 10.8.1 TS 29.002 Mobile application part (MAP) specification
+
+It is necessary to transfer between entities of a public land mobile network (PLMN) information specific to the PLMN in order to deal with the specific behaviour of roaming mobile stations (MS)s. The Signalling System No. 7 specified by ITU-T is used to transfer this information.
+
+This document describes the requirements for the signalling system and the procedures needed at the application level in order to fulfil these signalling needs.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 002 | 7.9.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 002 | 7.9.0 | Published | 2007-10-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429002v790 |
+| ATIS | ATIS.3GPP.29.002V790-2007 | 7.9.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.002(R7-7.7.0) | 7.7.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.002(R7-7.7.0).zip |
+| TTC | TS-3GA-29.002(Rel7)v7.9.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29002rel7v790.pdf |
+
+### 10.8.2 TS 29.007 General requirements on interworking between the public land mobile network (PLMN) and the integrated services digital network (ISDN) or public switched telephone network (PSTN)
+
+The document identifies the mobile-services switching centre/interworking functions (MSC/IWFs) and requirements to support interworking between:
+
+- a) PLMN and PSTN;
+- b) PLMN and ISDN;
+
+for circuit-switched services in the PLMN. It is not possible to treat ISDN and PSTN as one type of network, even when both ISDN and PSTN subscribers are served by the same exchange because of the limitations of the PSTN subscriber's access, i.e., analogue connection without D-channel signalling.
+
+Within this document, the requirements for voice and non-voice (data) calls are considered separately.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 007 | 7.3.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 007 | 7.3.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0329007v730 |
+| ATIS | ATIS.3GPP.29.007V730-2007 | 7.3.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.007(R7-7.3.0) | 7.3.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.007(R7-7.3.0).zip |
+| TTC | TS-3GA-29.007(Rel7)v7.3.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29007rel7v730.pdf |
+
+### 10.8.3 TS 29.010 Information element mapping between mobile station – base station system (MS – BSS) and base station system – mobile-services switching centre (BSS – MSC) signalling procedures and the mobile application part (MAP)
+
+The scope of the document is:
+
+- i) to provide a detailed specification for the interworking between information elements contained in layer 3 messages sent on the MS-MSC interface (call control and mobility management parts of GSM 04.08) and parameters contained in MAP services sent over the MSC-VLR interface (GSM 09.02) where the MSC acts as a transparent relay of information;
+- ii) to provide a detailed specification for the interworking between information elements contained in BSSMAP messages sent on the BSC-MSC interface (GSM 08.08) and parameters contained in MAP services sent over the MSC-VLR interface (GSM 09.02) where the MSC acts as a transparent relay of information;
+- iii) to provide a detailed specification for the interworking between information elements contained in BSSMAP messages (TS 48.008) and RANAP (TS 25.413);
+- iv) to provide a detailed specification for the interworking as in i) and ii) above when the MSC also processes the information.
+
+Interworking for supplementary services is given in GSM 09.11. Interworking for the short message service is given in GSM 03.40 and GSM 04.11. Interworking between the call control signalling of GSM 04.08 and the PSTN/ISDN is given in GSM 09.03, GSM 09.07 and TS 49.008. Interworking between the 'A' and 'E' interfaces for inter-MSC handover signalling is given in GSM 09.07 and 09.08.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 010 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 010 | 7.1.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429010v710 |
+| ATIS | ATIS.3GPP.29.010V710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.010(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.010(R7-7.1.0).zip |
+| TTC | TS-3GA-29.010(Rel7)v7.1.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29010rel7v710.pdf |
+
+#### 10.8.4 TS 29.011 Signalling interworking for supplementary services
+
+This Technical Specification is to provide a detailed specification for interworking between the A interface protocol and the mobile application part for handling of supplementary services. The MAP interfaces of interest are the B, C, D and E interfaces.
+
+The A, C, D and E interfaces are physical interfaces while the B interface is an internal interface defined for modelling purposes. Information relating to the modelling interface is not normative in this specification.
+
+Supplementary service signalling may be passed by the MSC/VLR between the A and E interfaces after inter-MSC handover. This procedure is transparent as far as supplementary services are concerned therefore interworking concerning this process is not described in this specification.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 011 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 011 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429011v700 |
+| ATIS | ATIS.3GPP.29.011V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.011(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.011(R7-7.0.0).zip |
+| TTC | TS-3GA-29.011(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29011rel7v700.pdf |
+
+### **10.8.5 TS 29.013 Signalling interworking between ISDN supplementary services application service element (ASE) and mobile application part (MAP) protocols**
+
+This document is to provide a specification for interworking between the ISDN application service element (ASE) protocol for supplementary services and the mobile application part (MAP) protocol on MAP D-interface protocol for handling of supplementary services within the digital cellular telecommunications system (Phase 2+). This version of the specification includes the interworking for the call completion to busy subscriber (CCBS) service between the ISDN CCBS-ASE and MAP.
+
+The MAP protocol for CCBS service is specified in GSM 09.02. The ISDN CCBS-ASE protocol is specified in [ETSI ETS 300 356-18]. The ISDN CCBS-ASE protocol is also commonly referred to as the SSAP protocol in GSM 03.93. This specification clarifies the interworking within the HLR between these protocols for the call completion to busy subscriber (CCBS) service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|-----------------------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 013 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 013 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429013v700 |
+| ATIS | ATIS.3GPP.29.013V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.013(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.013(R7-7.0.0).zip |
+| TTC | TS-3GA-29.013(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29013rel7v700.pdf |
+
+### **10.8.6 TS 29.016 Serving GPRS support node (SGSN) – visitor location register (VLR); Gs interface network service specification**
+
+This document specifies or references the subset of MTP and SCCP that is used for the reliable transport of BSSAP+ messages in the Gs interface. This document references the TS 29.202 that specifies alternative transport layers that can be applied instead of the MTP. This document also specifies the SCCP addressing capabilities to be provided in the Gs interface.
+
+The SCCP is used to provide message routing between the SGSN and the VLR. The SCCP routing principles specified in this Technical Specification allow connecting one SGSN to several VLR. No segmentation at SCCP level is needed on the Gs interface. Only SCCP class 0 is used on the Gs interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 016 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 016 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0129016v700 |
+| ATIS | ATIS.3GPP.29.016V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.016(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.016(R7-7.0.0).zip |
+| TTC | TS-3GA-29.016(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29016rel7v700.pdf |
+
+### 10.8.7 TS 29.018 Serving GPRS support node (SGSN) – visitor location register (VLR); Gs interface layer 3 specification
+
+The document specifies or references procedures used on the serving GPRS support node (SGSN) to visitor location register (VLR) interface for interoperability between GSM circuit-switched services and GSM packet data services.
+
+The document specifies the layer 3 messages and procedures on the Gs interface to allow coordination between databases and to relay certain messages related to GSM circuit-switched services over the GPRS subsystem.
+
+The functional split between VLR and SGSN is defined in TS 23.060. The required procedures between VLR and SGSN are defined in detail in the document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 018 | 7.3.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 018 | 7.3.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0129018v730 |
+| ATIS | ATIS.3GPP.29.018V730-2007 | 7.3.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.018(R7-7.3.0) | 7.3.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.018(R7-7.3.0).zip |
+| TTC | TS-3GA-29.018(Rel7)v7.3.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29018rel7v730.pdf |
+
+### 10.8.8 TS 29.060 GPRS tunnelling protocol (GTP) across the Gn and Gp interface
+
+The document defines the second version of GTP used on:
+
+- the Gn and Gp interfaces of the general packet radio service (GPRS);
+- the Iu, Gn and Gp interfaces of the UMTS system.
+
+NOTE – The version number used in the message headers is 0 for the first version of GTP described in GSM 09.60, and 1 for the second version in TS 29.060.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 060 | 7.7.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 060 | 7.7.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429060v770 |
+| ATIS | ATIS.3GPP.29.060V770-2007 | 7.7.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.060(R7-7.6.0) | 7.6.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.060(R7-7.6.0).zip |
+| TTC | TS-3GA-29.060(Rel7)v7.7.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29060rel7v770.pdf |
+
+#### 10.8.9 TS 29.061 Interworking between the public land mobile network (PLMN) supporting packet-based services and packet data networks (PDNs)
+
+The document defines the requirements for packet domain interworking between a:
+
+- PLMN and PDN;
+- PLMN and PLMN.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 061 | 7.5.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 061 | 7.5.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0329061v750 |
+| ATIS | ATIS.3GPP.29.061V750-2007 | 7.5.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.061(R7-7.4.0) | 7.4.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.061(R7-7.4.0).zip |
+| TTC | TS-3GA-29.061(Rel7)v7.5.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29061rel7v750.pdf |
+
+#### 10.8.10 TS 29.078 Customized application for mobile network enhanced logic (CAMEL) Phase 3; CAMEL application part (CAP) specification
+
+The document specifies the CAMEL application part (CAP) supporting the third phase of the network feature customized applications for mobile network enhanced logic. CAP is based on a sub-set of the ETSI core INAP CS-2 as specified by [ETSI EN 301 140-1]. Descriptions and definitions provided by [ETSI EN 301 140-1] are directly referenced by this standard in case no additions or clarifications are needed for the use in the CAP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 078 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 078 | 7.4.0 | Published | 2007-10-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429078v740 |
+| ATIS | ATIS.3GPP.29.078V740-2007 | 7.4.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.078(R7-7.4.0) | 7.4.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.078(R7-7.4.0).zip |
+| TTC | TS-3GA-29.078(Rel7)v7.4.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29078rel7v740.pdf |
+
+### 10.8.11 TS 29.108 Application of the radio access network application part (RANAP) on the E interface
+
+The document describes the subset of radio access network application part (RANAP) messages and procedures, defined in TS 25.413, which is used on the E interface. A general description can be found in TS 23.002 and TS 23.009.
+
+For the initiation and execution of relocation of SRNS ("relocation" for short, throughout the whole document) between MSCs, a subset of RANAP procedures are used. For the subsequent control of resources allocated to the user equipment (UE), RANAP procedures are used. The direct transfer elementary procedure (EP) of RANAP is used for the transfer of connection management and mobility management messages between the UE and the controlling 3G\_MSC.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 108 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 108 | 7.1.0 | Published | 2006-07-21 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGR-0329108v710 |
+| ATIS | ATIS.3GPP.29.108V710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.108(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.108(R7-7.1.0).zip |
+| TTC | TS-3GA-29.108(Rel7)v7.1.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29108rel7v710.pdf |
+
+### 10.8.12 TS 29.109 Generic authentication architecture (GAA); Zh and Zn interfaces based on the diameter protocol; Stage 3
+
+The present Stage 3 specification defines the Diameter-based implementation for bootstrapping Z interface (BSF-HSS) and GAA application Zn interface (BSF-NAF) in generic authentication architecture (GAA). The definition contains procedures, message contents and coding. The procedures for bootstrapping and usage of bootstrapped security association are defined in 3G TS 33.220.
+
+This specification is a part of the generic authentication architecture (GAA) specification series.
+
+The diameter-based implementation is based on re-usage of Cx interface Multimedia-Auth-Request/Answer messages originally between CSCF and HSS. These messages are defined in 3GPP TS 29.229. The 3GPP IMS mobility management uses the same definitions between CSCF and HSS. The present document defines how the defined messages are used with the bootstrapping and GAA application procedures (e.g., subscriber certificates) and the application logic that is needed in GAA network elements (BSF, HSS, and NAF).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 109 | 7.7.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 109 | 7.7.0 | Published | 2007-10-15 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429109v770 |
+| ATIS | ATIS.3GPP.29.109V770-2007 | 7.7.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.109(R7-7.0.0) | 7.6.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.109_R7-7.6.0.zip |
+| TTC | TS-3GA-29.109(Rel7)v7.7.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29109rel7v770.pdf |
+
+### 10.8.13 TS 29.119 GPRS tunnelling protocol (GTP) specification for gateway location register (GLR)
+
+The document describes the signalling requirements and procedures used at network elements related to the GLR for GTP within the 3G system at the application level.
+
+The document gives the description of the systems needed only in the network utilizing GLR as the delta document against TS 29.060.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 119 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 119 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429119v700 |
+| ATIS | ATIS.3GPP.29.119V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | ATIS.3GPP.29.119V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TS-3GA-29.119(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29119rel7v700.pdf |
+
+### 10.8.14 TS 29.120 Mobile application part (MAP) specification for gateway location register (GLR)
+
+The document describes the signalling requirements and procedures used at network elements related to the GLR for MAP within the 3G system at the application level.
+
+The document gives the description of the systems needed only in the network utilizing GLR as the delta document against TS 29.002.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 120 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 120 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429120v700 |
+| ATIS | ATIS.3GPP.29.120V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.120(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.120(R7-7.0.0).zip |
+| TTC | TS-3GA-29.120(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29120rel7v700.pdf |
+
+### 10.8.15 TS 29.140 Multimedia messaging service (MMS); MM10 interface based on diameter protocol; Stage 3
+
+The present document defines the procedures and the transport protocol for use in the multimedia messaging service (MMS) based on diameter.
+
+The present document is applicable to:
+
+- the MM10 interface between an MMS relay/server and the MSCF.
+
+Whenever it is possible, this document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of diameter. Where this is not possible, extensions to Diameter are defined within this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-29.140V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/29/A29140-700.pdf |
+| CCSA | CCSA-TSD-129 140 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 140 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429140v700 |
+| ATIS | ATIS.3GPP.29.140V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.140(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.140(R7-7.0.0).zip |
+
+### **10.8.16 TS 29.161 Interworking between the public land mobile network (PLMN) supporting packet-based services with wireless local area network (WLAN) access and packet data networks (PDNs)**
+
+The present document describes the network interworking for the packet domain. Interworking to various external networks is defined together with the interworking for data forwarding while subscribers roam within the 3GPP system.
+
+The present document defines the requirements for packet domain interworking between a:
+
+- a) PLMN with WLAN access and PDN;
+- b) PLMN with WLAN access and PLMN.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|-----------------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 161 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 161 | 7.2.0 | Published | 2007-04-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0329161v720 |
+| ATIS | ATIS.3GPP.29.161V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.161(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.161(R7-7.2.0).zip |
+| TTC | TS-3GA-29.161(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29161rel7v720.pdf |
+
+### **10.8.17 TS 29.162 Interworking between the IM CN subsystem and IP networks**
+
+The IM CN subsystem interworks with the external IP networks through the Mb reference point.
+
+This document details the interworking between the IM CN subsystem and external IP networks for IM service support. It addresses the issues of control plane interworking, user plane interworking and IP version interworking.
+
+The IP version interworking, between IP version 4 IETF RFC 791: "*Internet Protocol*" and IP version 6 IETF RFC 1883 (IETF RFC 2460: "*Internet Protocol, Version 6 (IPv6) Specification*") detailed in terms of the processes and protocol mappings required in order to support both mobile originated and terminated calls.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 162 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 162 | 7.1.0 | Published | 2006-06-08 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0329162v710 |
+| ATIS | ATIS.3GPP.29.162V 710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.162(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.162(R7-7.1.0).zip |
+| TTC | TS-3GA-29.162(Rel7)v7.1.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29162rel7v710.pdf |
+
+### 10.8.18 TS 29.163 Interworking between the IP multimedia (IM) core network (CN) subsystem and circuit-switched (CS) networks
+
+The present document specifies the principles of interworking between the 3GPP IM CN subsystem and BICC/ISUP based legacy CS networks, in order to support IM basic voice calls.
+
+The present document addresses the areas of control and user plane interworking between the IM CN subsystem and CS networks through the network functions, which include the MGCF and IM-MGW. For the specification of control plane interworking, areas such as the interworking between SIP and BICC or ISUP are detailed in terms of the processes and protocol mappings required for the support of both IM originated and terminated voice calls.
+
+Other areas addressed encompass the transport protocol and signalling issues for negotiation and mapping of bearer capabilities and QoS information.
+
+The present document specifies the interworking between 3GPP profile of SIP (as detailed according to 3GPP TS 24.229) and BICC or ISUP, as specified in [ITU-T Q.1902.1] to [ITU-T Q.1902.6]: "*Bearer Independent Call Control*" and ITU-T Recs Q.761 to Q.764: "*Signalling System No. 7 – ISDN User Part Signalling procedures*" respectively.
+
+The present document addresses two interworking scenarios with respect to the properties of the CS network:
+
+- The CS network does not use any 3GPP specific additions.
+- The CS network uses 3GPP-specific additions.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 163 | 7.9.0 | Approved | 2008-01-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 163 | 7.9.0 | Published | 2008-01-31 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0329163v790 |
+| ATIS | ATIS.3GPP.29.163V780-2007 | 7.8.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.163(R7-7.6.0) | | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-29.163(R7-7.6.0).zip |
+| TTC | TS-3GA-29.163(Rel7)v7.8.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29163rel7v780.pdf |
+
+#### **10.8.19 TS 29.164 Interworking between the 3GPP CS domain with BICC or ISUP as signalling protocol and external SIP-I networks**
+
+The present document defines interworking procedures between a 3GPP CS domain (see TS 23.205) which applies either BICC or ISUP as signalling protocol, and external networks that use SIP-I (see ITU-T Q.1912.5, Profile C) as signalling protocol. The document also describes the related interworking architecture. The control plane interworking is performed by an interworking unit at the interconnection between the 3GPP CS domain and an external SIP-I network. The user plane interworking is performed by an MGW. The present document defines stage 2 procedures for the control of the MGW.
+
+The present specification reuses existing interworking procedures of TS 29.163 and ITU-T Q.1912.5, Profile C, as far as possible.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 164 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 164 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0329164v700 |
+| ATIS | ATIS.3GPP.29.164V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.164(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-29.164(R7-7.0.0).zip |
+| TTC | TS-3GA-29.164(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29164rel7v700.pdf |
+
+#### **10.8.20 TS 29.198-01 Open service access (OSA) application programming interface (API); Part 1: Overview**
+
+The document is the first part of the Specification defining the application programming interface (API) for open service access (OSA), and provides an overview of the content and structure of the various parts of this specification, and of the relation to other standards documents.
+
+The OSA specifications define an architecture that enables service application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in TS 23.127. The requirements for OSA are contained in TS 22.127.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 198-1 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 198-1 | 7.0.0 | Published | 2007-03-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529198-01v700 |
+| ATIS | ATIS.3GPP.29.198-01V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.198-01(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.198-01(R7-7.0.0).zip |
+| TTC | TS-3GA-29.198-01(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29198-01rel7v700.pdf |
+
+#### 10.8.21 TS 29.198-02 Open service access (OSA) application programming interface (API); Part 2: Common data definitions
+
+The document is Part 2 of the Stage 3 specification for an application programming interface (API) for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in TS 23.127. The requirements for OSA are contained in TS 22.127.
+
+The document specifies the common data definitions of the OSA. The common data definitions contain data-types that are common across the rest of the OSA API.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 198-2 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 198-2 | 7.0.0 | Published | 2007-03-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529198-02v700 |
+| ATIS | ATIS.3GPP.29.198-02V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.198-02(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.198-02(R7-7.0.0).zip |
+| TTC | TS-3GA-29.198-02(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29198-02rel7v700.pdf |
+
+### **10.8.22 TS 29.198-03 Open service access (OSA) application programming interface (API); Part 3: Framework**
+
+The document is Part 3 of the Stage 3 specification for an application programming interface (API) for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in TS 23.127. The requirements for OSA are contained in TS 22.127.
+
+The document specifies the framework aspects of the interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|----------------|-----------------------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 198-3 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 198-3 | 7.1.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529198-03v710 |
+| ATIS | ATIS.3GPP.29.198-03V710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.198-03(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.198-03(R7-7.1.0).zip |
+| TTC | TS-3GA-29.198-03(Rel7)v7.1.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29198-03rel7v710.pdf |
+
+### **10.8.23 TS 29.198-04-1 Open service access (OSA) application programming interface (API); Part 4: Call control; Sub-part 1: Call control common definitions**
+
+This document is Part 4, sub-part 1 of the Stage 3 specification for an application programming interface (API) for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3G TS 23.127. The requirements for OSA are contained in 3G TS 22.127.
+
+This document specifies the common definitions used by the call control service capability features (SCF).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 198-4-1 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 198-4-1 | 7.0.0 | Published | 2007-03-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529198-04-1v700 |
+| ATIS | ATIS.3GPP.29.198-04-1V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.198-04-1(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.198-04-1(R7-7.0.0).zip |
+| TTC | TS-3GA-29.198-04-1(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29198-04-1rel7v700.pdf |
+
+#### **10.8.24 TS 29.198-04-2 Open service access (OSA) application programming interface (API); Part 4: Call control; Sub-part 2: Generic call control SCF**
+
+The document is Part 4, sub-part 2 of the Stage 3 specification for an application programming interface (API) for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3G TS 23.127. The requirements for OSA are contained in 3G TS 22.127.
+
+This document specifies the generic call control service capability feature (SCF) aspects of the interface. All aspects of the generic call control SCF are defined here, these being:
+
+- sequence diagrams;
+- class diagrams;
+- interface specification plus detailed method descriptions;
+- state transition diagrams;
+- data definitions;
+- IDL description of the interfaces;
+- WSDL description of the interfaces;
+- reference to the Java API description of the interfaces.
+
+The process by which this task is accomplished is through the use of object modelling techniques described by the unified modelling language (UML).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 198-4-2 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 198-4-2 | 7.0.0 | Published | 2007-03-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529198-04-2v700 |
+| ATIS | ATIS.3GPP.29.198-04-2V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.198-04-2(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-29.198-04-2(R7-7.0.0).zip |
+| TTC | TS-3GA-29.198-04-2(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29198-04-2rel7v700.pdf |
+
+#### **10.8.25 TS 29.198-04-3 Open service access (OSA) application programming interface (API); Part 4: Call control; Sub-part 3: Multi-party call control SCF**
+
+The document is Part 4, sub-part 3 of the Stage 3 specification for an application programming interface (API) for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3G TS 23.127. The requirements for OSA are contained in 3G TS 22.127.
+
+This document specifies the multi-party call control service capability feature (SCF) aspects of the interface. All aspects of the multi-party call control SCF are defined here, these being:
+
+- sequence diagrams;
+- class diagrams;
+- interface specification plus detailed method descriptions;
+- state transition diagrams;
+- data definitions;
+- IDL description of the interfaces;
+- WSDL description of the interfaces;
+- reference to the Java API description of the interfaces.
+
+The process by which this task is accomplished is through the use of object modelling techniques described by the unified modelling language (UML).
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|--------------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-29.198-04-3(R7-7.0.1) | 7.0.1 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-29.198-04-3(R7-7.0.1).zip |
+| TTC | TS-3GA-29.198-04-3(Rel7)v7.0.1 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29198-04-3rel7v701.pdf |
+
+### **10.8.26 TS 29.198-04-4 Open service access (OSA) application programming interface (API); Part 4: Call control; Sub-part 4: Multi-media call control SCF**
+
+The document is Part 4, sub-part 4 of the Stage 3 specification for an application programming interface (API) for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3G TS 23.127. The requirements for OSA are contained in 3G TS 22.127.
+
+This document specifies the multi-party call control service capability feature (SCF) aspects of the interface. All aspects of the multi-party call control SCF are defined here, these being:
+
+- sequence diagrams;
+- class diagrams;
+- interface specification plus detailed method descriptions;
+- state transition diagrams;
+- data definitions;
+- IDL description of the interfaces;
+- WSDL description of the interfaces;
+- reference to the Java API description of the interfaces.
+
+The process by which this task is accomplished is through the use of object modelling techniques described by the unified modelling language (UML).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|----------------|-----------------------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 198-4-4 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 198-4-4 | 7.0.0 | Published | 2007-04-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529198-04-4v700 |
+| ATIS | ATIS.3GPP.29.198-04-4V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.198-04-4(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.198-04-4(R7-7.0.0).zip |
+| TTC | TS-3GA-29.198-04-4(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29198-04-4rel7v700.pdf |
+
+### **10.8.27 TS 29.198-04-5 Open service access (OSA) application programming interface (API); Part 4: Call control; Sub-part 5: Conference call control service capability feature (SCF)**
+
+This document is Part 4, sub-part 5 of the Stage 3 specification for an application programming interface (API) for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198. The requirements for OSA are contained in 3GPP TS 22.127.
+
+The present document specifies the conference call control service capability feature (SCF) aspects of the interface. All aspects of the conference call control SCF are defined here, these being:
+
+- sequence diagrams
+- class diagrams
+- interface specification plus detailed method descriptions
+- state transition diagrams
+- data definitions
+- IDL description of the interfaces
+- WSDL description of the interfaces
+- reference to the Java™ API description of the interfaces
+
+The process by which this task is accomplished is through the use of object modelling techniques described by the unified modelling language (UML).
+
+This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 198-4-5 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 198-4-5 | 7.0.0 | Published | 2007-03-27 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGC-0529198-04-5v700 |
+| ATIS | ATIS.3GPP.29.198-04-5V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.198-04-5(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.198-04-5(R7-7.0.0).zip |
+| TTC | TS-3GA-29.198-04-5(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29198-04-5rel7v700.pdf |
+
+### **10.8.28 TS 29.198-05 Open service access (OSA); application programming interface (API); Part 5: User interaction service capability feature (SCF)**
+
+This document is Part 5 of the Stage 3 specification for an application programming interface (API) for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in TS 23.127. The requirements for OSA are contained in TS 22.127.
+
+The document specifies the user interaction (UI) service capability feature (SCF) aspects of the interface.
+
+The process by which this task is accomplished is through the use of object modelling techniques described by the unified modelling language (UML).
+
+This specification has been defined jointly between 3GPP TSG CN WG5, ETSI TISPAN and the Parlay Group, in cooperation with a number of JAIN™ Community member companies.
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|------------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-29.198-05(R7-7.1.1) | 7.1.1 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.198-05(R7-7.1.1).zip |
+| TTC | TS-3GA-29.198-05(Rel7)v7.1.1 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29198-05rel7v711.pdf |
+
+### **10.8.29 TS 29.198-06 Open service access (OSA) application programming interface (API); Part 6: Mobility SCF**
+
+The document is Part 6 of the Stage 3 specification for an application programming interface (API) for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in TS 23.127. The requirements for OSA are contained in TS 22.127.
+
+The document specifies the mobility service capability feature (SCF) aspects of the interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 198-6 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 198-6 | 7.0.0 | Published | 2007-03-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529198-06v700 |
+| ATIS | ATIS.3GPP.29.198-06V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.198-06(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.198-06(R7-7.0.0).zip |
+| TTC | TS-3GA-29.198-06(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29198-06rel7v700.pdf |
+
+### **10.8.30 TS 29.198-07 Open service access (OSA) application programming interface (API); Part 7: Terminal capabilities SCF**
+
+The document is part 7 of the Stage 3 specification for an application programming interface (API) for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in TS 23.127. The requirements for OSA are contained in TS 22.127.
+
+The document specifies the terminal capabilities service capability feature (SCF) aspects of the interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 198-7 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 198-7 | 7.0.0 | Published | 2007-03-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529198-07v700 |
+| ATIS | ATIS.3GPP.29.198-07V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.198-07(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.198-07(R7-7.0.0).zip |
+| TTC | TS-3GA-29.198-07(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29198-07rel7v700.pdf |
+
+### **10.8.31 TS 29.198-08 Open service access (OSA) application programming interface (API); Part 8: Data session control SCF**
+
+The document is Part 8 of the Stage 3 specification for an application programming interface (API) for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in TS 23.127. The requirements for OSA are contained in TS 22.127.
+
+The document specifies the data session control service capability feature (SCF) aspects of the interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|------------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-29.198-08(R7-7.0.1) | 7.0.1 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.198-08(R7-7.0.1).zip |
+| TTC | TS-3GA-29.198-08(Rel7)v7.0.1 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29198-08rel7v701.pdf |
+
+### **10.8.32 TS 29.198-11 Open service access (OSA) application programming interface (API); Part 11: Account management SCF**
+
+The document is Part 11 of the Stage 3 specification for an application programming interface (API) for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in TS 23.127. The requirements for OSA are contained in TS 22.127.
+
+The document specifies the account management service capability feature (SCF) aspects of the interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 198-11 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 198-11 | 7.0.0 | Published | 2007-03-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529198-11v700 |
+| ATIS | ATIS.3GPP.29.198-11V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.198-11(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.198-11(R7-7.0.0).zip |
+| TTC | TS-3GA-29.198-11(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29198-11rel7v700.pdf |
+
+### 10.8.33 TS 29.198-12 Open service access (OSA) application programming interface (API); Part 12: Charging SCF
+
+The document is Part 12 of the Stage 3 specification for an application programming interface (API) for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in TS 23.127. The requirements for OSA are contained in TS 22.127.
+
+The document specifies the charging service capability feature (SCF) aspects of the interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 198-12 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 198-12 | 7.0.0 | Published | 2007-03-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529198-12v700 |
+| ATIS | ATIS.3GPP.29.198-12V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.198-12(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.198-12(R7-7.0.0).zip |
+| TTC | TS-3GA-29.198-12(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29198-12rel7v700.pdf |
+
+### 10.8.34 TS 29.198-13 Open service access (OSA) application programming interface (API); Part 13: Policy management SCF
+
+The document is part 13 of the Stage 3 specification for an application programming interface (API) for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3G TS 23.127. The requirements for OSA are contained in 3G TS 22.127.
+
+This document specifies the policy management service capability feature (SCF) aspects of the interface. All aspects of the policy management SCF are defined here, these being:
+
+- sequence diagrams;
+- class diagrams;
+- interface specification plus detailed method descriptions;
+- state transition diagrams;
+- data definitions;
+- IDL description of the interfaces.
+
+The process by which this task is accomplished is through the use of object modelling techniques described by the unified modelling language (UML).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 198-13 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 198-13 | 7.0.0 | Published | 2007-03-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529198-13v700 |
+| ATIS | ATIS.3GPP.29.198-13V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.198-13(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.198-13(R7-7.0.0).zip |
+| TTC | TS-3GA-29.198-13(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29198-13rel7v700.pdf |
+
+### **10.8.35 TS 29.198-14 Open service access (OSA) application programming interface (API); Part 14: Presence and availability management (PAM) SCF**
+
+The document is part 14 of the Stage 3 specification for an application programming interface (API) for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3G TS 23.127. The requirements for OSA are contained in 3G TS 22.127.
+
+This document specifies the presence and availability management service capability feature (SCF) aspects of the interface. All aspects of the presence and availability management SCF are defined here, these being:
+
+- sequence diagrams;
+- class diagrams;
+- interface specification plus detailed method descriptions;
+- state transition diagrams;
+- data definitions;
+
+- IDL description of the interfaces.
+
+The process by which this task is accomplished is through the use of object modelling techniques described by the unified modelling language (UML).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 198-14 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 198-14 | 7.0.0 | Published | 2007-03-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529198-14v700 |
+| ATIS | ATIS.3GPP.29.198-14V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.198-14(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.198-14(R7-7.0.0).zip |
+| TTC | TS-3GA-29.198-14(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29198-14rel7v700.pdf |
+
+### **10.8.36 TS 29.198-15 Open service access (OSA); application programming interface (API); Part 15: Multimedia messaging (MM) SCF**
+
+The present document is Part 15 of the Stage 3 specification for an application programming interface (API) for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198. The requirements for OSA are contained in 3GPP TS 22.127.
+
+The present document specifies the multimedia messaging service capability feature (SCF) aspects of the interface. All aspects of the multimedia messaging SCF are defined here, these being:
+
+- sequence diagrams;
+- class diagrams;
+- interface specification plus detailed method descriptions;
+- state transition diagrams;
+- data definitions;
+- IDL description of the interfaces;
+- WSDL description of the interfaces.
+
+The process by which this task is accomplished is through the use of object modelling techniques described by the unified modelling language (UML).
+
+The present document has been defined jointly between 3GPP TSG CN WG5, ETSI TISPAN and the Parlay Group, in cooperation with a number of JAIN™ Community member companies.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 198-15 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 198-15 | 7.1.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529198-15v710 |
+| ATIS | ATIS.3GPP.29.198-15V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.198-15(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.198-15(R7-7.0.0).zip |
+| TTC | TS-3GA-29.198-15(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29198-15rel7v710.pdf |
+
+### **10.8.37 TS 29.198-16 Open service access (OSA); Application programming interface (API); Part 16: Service broker service capability feature (SCF)**
+
+The present document is Part 16 of the Stage 3 specification for an application programming interface (API) for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198. The requirements for OSA are contained in 3GPP TS 22.127.
+
+The present document specifies the service broker service capability feature (SCF) aspects of the interface. All aspects of the service broker SCF are defined here, these being:
+
+- sequence diagrams
+- class diagrams
+- interface specification plus detailed method descriptions
+- state transition diagrams
+- data definitions
+- IDL description of the interfaces
+- WSDL description of the interfaces
+
+The process by which this task is accomplished is through the use of object modelling techniques described by the unified modelling language (UML).
+
+This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 198-16 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 198-16 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529198-16v700 |
+| ATIS | ATIS.3GPP.29.198-16V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.198-16(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.198-16(R7-7.0.0).zip |
+| TTC | TS-3GA-29.198-16(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29198-16rel7v700.pdf |
+
+### 10.8.38 TS 29.199-01 Open service access (OSA); Parlay X web services; Part 1: Common
+
+The present document is Part 1 of the Stage 3 Parlay X web services specification for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3G TS 23.127. The requirements for OSA are contained in 3G TS 22.127.
+
+The present document specifies the common aspects of the Parlay X web services. The following are defined here:
+
+- name spaces;
+- data definitions;
+- fault definitions;
+- WSDL description of the interfaces.
+
+The present document has been defined jointly between 3GPP TSG CN WG5, ETSI TISPAN and The Parlay Group.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-1 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-1 | 7.2.0 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529199-01v720 |
+| ATIS | ATIS.3GPP.29.199-01V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-01(R7-7.1.1) | 7.1.1 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-01(R7-7.1.1).zip |
+| TTC | TS-3GA-29.199-01(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-01rel7v720.pdf |
+
+### **10.8.39 TS 29.199-02 Open service access (OSA); Parlay X web services; Part 2: Third-party call**
+
+The present document is Part 2 of the Stage 3 Parlay X web services specification for open service access (OSA).
+
+The present document specifies the third-party call web service aspects of the interface. All aspects of the third-party call web service are defined here, these being:
+
+- name spaces;
+- sequence diagrams;
+- data definitions;
+- interface specification plus detailed method descriptions;
+- fault definitions;
+- service policies;
+- WSDL description of the interfaces.
+
+The present document has been defined jointly between 3GPP TSG CN WG5, ETSI TISPAN and The Parlay Group.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|----------------|-----------------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-2 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-2 | 7.4.0 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529199-02v740 |
+| ATIS | ATIS.3GPP.29.199-02V740-2007 | 7.4.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-02(R7-7.3.0) | 7.3.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-02(R7-7.3.0).zip |
+| TTC | TS-3GA-29.199-02(Rel7)v7.4.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-02rel7v740.pdf |
+
+### **10.8.40 TS 29.199-03 Open service access (OSA); Parlay X web services; Part 3: Call notification**
+
+The present document is Part 3 of the Stage 3 Parlay X web services specification for open service access (OSA).
+
+The present document specifies the call notification web service aspects of the interface. All aspects of the call notification web service are defined here, these being:
+
+- name spaces;
+- sequence diagrams;
+- data definitions;
+- interface specification plus detailed method descriptions;
+- fault definitions;
+- service policies;
+- WSDL description of the interfaces.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-3 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-3 | 7.2.0 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529199-03v720 |
+| ATIS | ATIS.3GPP.29.199-03V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-03(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-03(R7-7.1.0).zip |
+| TTC | TS-3GA-29.199-03(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-03rel7v720.pdf |
+
+#### 10.8.41 TS 29.199-04 Open service access (OSA); Parlay X web services; Part 4: Short messaging
+
+The present document specifies the short messaging web service aspects of the interface. All aspects of the short messaging web service are defined here, these being:
+
+- name spaces;
+- sequence diagrams;
+- data definitions;
+- interface specification plus detailed method descriptions;
+- fault definitions;
+- service policies;
+- WSDL description of the interfaces.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-4 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-4 | 7.2.0 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529199-04v720 |
+| ATIS | ATIS.3GPP.29.199-04V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-04(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-04(R7-7.1.0).zip |
+| TTC | TS-3GA-29.199-04(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-04rel7v720.pdf |
+
+#### 10.8.42 TS 29.199-05 Open service access (OSA); Parlay X web services; Part 5: Multimedia messaging
+
+The present document specifies the multimedia messaging web service aspects of the interface. All aspects of the multimedia messaging web service are defined here, these being:
+
+- name spaces;
+
+- sequence diagrams;
+- data definitions;
+- interface specification plus detailed method descriptions;
+- fault definitions;
+- service policies;
+- WSDL description of the interfaces.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-5 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-5 | 7.2.0 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529199-05v720 |
+| ATIS | ATIS.3GPP.29.199-05V720-2007 | 7.2.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-05(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-05(R7-7.1.0).zip |
+| TTC | TS-3GA-29.199-05(Rel7)v7.2.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-05rel7v720.pdf |
+
+#### **10.8.43 TS 29.199-06 Open service access (OSA); Parlay X web services; Part 6: Payment**
+
+The present document specifies the payment web service aspects of the interface. All aspects of the payment web service are defined here, these being:
+
+- name spaces;
+- sequence diagrams;
+- data definitions;
+- interface specification plus detailed method descriptions;
+- fault definitions;
+- service policies;
+- WSDL description of the interfaces.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-6 | 7.2.2 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-6 | 7.2.2 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529199-06v722 |
+| ATIS | ATIS.3GPP.29.199-06V722-2007 | 7.2.2 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-06(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-06(R7-7.2.0).zip |
+| TTC | TS-3GA-29.199-06(Rel7)v7.2.2 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-06rel7v722.pdf |
+
+#### **10.8.44 TS 29.199-07 Open service access (OSA); Parlay X web services; Part 7: Account management**
+
+The present document specifies the account management web service aspects of the interface. All aspects of the account management web service are defined here.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-7 | 7.2.2 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-7 | 7.2.2 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529199-07v722 |
+| ATIS | ATIS.3GPP.29.199-07V722-2007 | 7.2.2 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-07(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-07(R7-7.2.0).zip |
+| TTC | TS-3GA-29.199-07(Rel7)v7.2.2 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-07rel7v722.pdf |
+
+#### **10.8.45 TS 29.199-08 Open service access (OSA); Parlay X web services; Part 8: Terminal status**
+
+The present document specifies the terminal status web service aspects of the interface. All aspects of the terminal status web service are defined here.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-8 | 7.0.2 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-8 | 7.0.2 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529199-08v702 |
+| ATIS | ATIS.3GPP.29.199-08V702-2007 | 7.0.2 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-08(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-08(R7-7.0.0).zip |
+| TTC | TS-3GA-29.199-08(Rel7)v7.0.2 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-08rel7v702.pdf |
+
+#### **10.8.46 TS 29.199-09 Open service access (OSA); Parlay X web services; Part 9: Terminal location**
+
+The present document specifies the terminal location web service aspects of the interface. All aspects of the terminal location web service are defined here.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-9 | 7.2.2 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-9 | 7.2.2 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529199-09v722 |
+| ATIS | ATIS.3GPP.29.199-09V722-2007 | 7.2.2 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-09(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-09(R7-7.2.0).zip |
+| TTC | TS-3GA-29.199-09(Rel7)v7.2.2 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-09rel7v722.pdf |
+
+#### **10.8.47 TS 29.199-10 Open service access (OSA); Parlay X web services; Part 10: Call handling**
+
+The present document specifies the call handling web service aspects of the interface. All aspects of the call handling web service are defined here.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-10 | 7.0.2 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-10 | 7.0.2 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529199-10v702 |
+| ATIS | ATIS.3GPP.29.199-10V702-2007 | 7.0.2 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-10(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-10(R7-7.0.0).zip |
+| TTC | TS-3GA-29.199-10(Rel7)v7.0.2 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-10rel7v702.pdf |
+
+#### **10.8.48 TS 29.199-11 Open service access (OSA); Parlay X web services; Part 11: Audio call**
+
+The present document specifies the audio call web service aspects of the interface. All aspects of the audio call web service are defined here.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-11 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-11 | 7.2.0 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529199-11v720 |
+| ATIS | ATIS.3GPP.29.199-11V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-11(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-11(R7-7.1.0).zip |
+| TTC | TS-3GA-29.199-11(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-11rel7v720.pdf |
+
+#### **10.8.49 TS 29.199-12 Open service access (OSA); Parlay X web services; Part 12: Multimedia conference**
+
+The present document specifies the multimedia conference web service aspects of the interface. All aspects of the multimedia conference web service are defined here.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-12 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-12 | 7.1.0 | Published | 2007-10-16 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529199-12v710 |
+| ATIS | ATIS.3GPP.29.199-12V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-12(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-12(R7-7.0.0).zip |
+| TTC | TS-3GA-29.199-12(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-12rel7v710.pdf |
+
+#### **10.8.50 TS 29.199-13 Open service access (OSA); Parlay X web services; Part 13: Address list management**
+
+The present document specifies the address list management web service aspects of the interface. All aspects of the address list management web service are defined here.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-13 | 7.0.2 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-13 | 7.0.2 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529199-13v702 |
+| ATIS | ATIS.3GPP.29.199-13V702-2007 | 7.0.2 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-13(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-13(R7-7.0.0).zip |
+| TTC | TS-3GA-29.199-13(Rel7)v7.0.2 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-13rel7v702.pdf |
+
+#### **10.8.51 TS 29.199-14 Open service access (OSA); Parlay X web services; Part 14: Presence**
+
+The present document specifies the presence web service aspects of the interface. All aspects of the presence web service are defined here.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-14 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-14 | 7.4.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529199-14v740 |
+| ATIS | ATIS.3GPP.29.199-14V740-2007 | 7.4.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-14(R7-7.3.0) | 7.3.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-14(R7-7.3.0).zip |
+| TTC | TS-3GA-29.199-14(Rel7)v7.4.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-14rel7v740.pdf |
+
+### **10.8.52 TS 29.199-15 Open service access (OSA); Parlay X web services; Part 15: Message broadcast**
+
+The present document is Part 15 of the Stage 3 Parlay X web services specification for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198. The requirements for OSA are contained in 3GPP TS 22.127.
+
+The present document specifies the message broadcast web service aspects of the interface. All aspects of the message broadcast web service are defined here, these being:
+
+- Name spaces.
+- Sequence diagrams.
+- Data definitions.
+- Interface specification plus detailed method descriptions.
+- Fault definitions.
+- Service policies.
+- WSDL description of the interfaces.
+
+The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-15 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-15 | 7.2.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529199-15v720 |
+| ATIS | ATIS.3GPP.29.199-15V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-15(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-15(R7-7.1.0).zip |
+| TTC | TS-3GA-29.199-15(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-15rel7v720.pdf |
+
+### **10.8.53 TS 29.199-16 Open service access (OSA); Parlay X web services; Part 16: Geocoding**
+
+This document is Part 16 of the Stage 3 Parlay X web services specification for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198. The requirements for OSA are contained in 3GPP TS 22.127.
+
+The document specifies the geocoding web service aspects of the interface. All aspects of the geocoding web service are defined here, these being:
+
+- Name spaces
+- Sequence diagrams
+- Data definitions
+- Interface specification plus detailed method descriptions
+- Fault definitions
+- Service policies
+- WSDL Description of the interfaces
+
+This document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-16 | 7.1.2 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-16 | 7.1.2 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529199-16v712 |
+| ATIS | ATIS.3GPP.29.199-16V712-2007 | 7.1.2 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-16(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-16(R7-7.1.0).zip |
+| TTC | TS-3GA-29.199-16(Rel7)v7.1.2 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-16rel7v712.pdf |
+
+#### **10.8.54 TS 29.199-17 Open service access (OSA); Parlay X web services; Part 17: Application-driven quality of service (QoS)**
+
+This document is Part 17 of the Stage 3 Parlay X web services specification for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198. The requirements for OSA are contained in 3GPP TS 22.127.
+
+The document specifies the application-driven quality of service (QoS) web service aspects of the interface. All aspects of the application-driven QoS web service are defined here, these being:
+
+- Name spaces.
+- Sequence diagrams.
+- Data definitions.
+- Interface specification plus detailed method descriptions.
+- Fault definitions.
+- Service policies.
+- WSDL Description of the interfaces.
+
+This document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Consortium.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-17 | 7.0.2 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-17 | 7.0.2 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529199-17v702 |
+| ATIS | ATIS.3GPP.29.199-17V702-2007 | 7.0.2 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-17(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-17(R7-7.0.0).zip |
+| TTC | TS-3GA-29.199-17(Rel7)v7.0.2 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-17rel7v702.pdf |
+
+### **10.8.55 TS 29.199-18 Open Service Access (OSA); Parlay X web services; Part 18: Device capabilities and configuration**
+
+This document is Part 18 of the Stage 3 Parlay X web services specification for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198. The requirements for OSA are contained in 3GPP TS 22.127.
+
+The document specifies the device capabilities and configuration web service aspects of the interface. All aspects of the device capabilities and configuration web service are defined here, these being:
+
+- Name spaces.
+- Sequence diagrams.
+- Data definitions.
+- Interface specification plus detailed method descriptions.
+- Fault definitions.
+- Service policies.
+- WSDL description of the interfaces.
+
+This document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Consortium.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-18 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-18 | 7.0.0 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGC-0529199-18v700 |
+| ATIS | ATIS.3GPP.29.199-18V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-18(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-18(R7-7.0.0).zip |
+| TTC | TS-3GA-29.199-18(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-18rel7v700.pdf |
+
+### **10.8.56 TS 29.199-19 Open service access (OSA); Parlay X web services; Part 19: Multimedia streaming control**
+
+This document is Part 19 of the Stage 3 Parlay X web services specification for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198. The requirements for OSA are contained in 3GPP TS 22.127.
+
+The document specifies the Multimedia streaming control web service aspects of the interface. All aspects of the multimedia streaming control web service are defined here, these being:
+
+- Name spaces.
+- Sequence diagrams.
+- Data definitions.
+- Interface specification plus detailed method descriptions.
+- Fault definitions.
+- Service policies.
+- WSDL description of the interfaces.
+
+This document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Consortium.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-19 | 7.0.2 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-19 | 7.0.2 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529199-19v702 |
+| ATIS | ATIS.3GPP.29.199-19V702-2007 | 7.0.2 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-19(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-19(R7-7.0.0).zip |
+| TTC | TS-3GA-29.199-19(Rel7)v7.0.2 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-19rel7v702.pdf |
+
+### **10.8.57 TS 29.199-20 Open service access (OSA); Parlay X web services; Part 20: Multimedia multicast session management**
+
+This document is Part 20 of the Stage 3 Parlay X web services specification for open service access (OSA).
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198. The requirements for OSA are contained in 3GPP TS 22.127.
+
+The document specifies the multimedia multicast session management web service aspects of the interface. All aspects of the multimedia multicast session management web service are defined here, these being:
+
+- Name spaces.
+- Sequence diagrams.
+- Data definitions.
+- Interface specification plus detailed method descriptions.
+- Fault definitions.
+- Service policies.
+- WSDL description of the interfaces.
+
+This document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Consortium.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 199-20 | 7.0.2 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 199-20 | 7.0.2 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0529199-20v702 |
+| ATIS | ATIS.3GPP.29.199-20V702-2007 | 7.0.2 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.199-20(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.199-20(R7-7.0.0).zip |
+| TTC | TS-3GA-29.199-20(Rel7)v7.0.2 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29199-20rel7v702.pdf |
+
+### 10.8.58 TS 29.202 Signalling System No. 7 (SS7) signalling transport in core network; Stage 3
+
+The document defines the possible protocol architectures for transport of SS7 signalling protocols in core network.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 202 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 202 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429202v700 |
+| ATIS | ATIS.3GPP.29.202V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.202(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.202(R7-7.0.0).zip |
+| TTC | TS-3GA-29.202(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29202rel7v700.pdf |
+
+### 10.8.59 TS 29.204 Signalling System No. 7 (SS7) security gateway; Architecture, functional description and protocol details
+
+This document provides functional description of the SS7 security gateway. The document covers also network architecture, routeing considerations, and protocol details.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 204 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 204 | 7.1.0 | Published | 2007-04-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGC-0429204v710 |
+| ATIS | ATIS.3GPP.29.204V710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.204(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.204(R7-7.1.0).zip |
+| TTC | TS-3GA-29.204(Rel7)v7.1.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29204rel7v710.pdf |
+
+### 10.8.60 TS 29.205 Application of Q.1900-series to bearer-independent circuit-switched core network architecture; Stage 3
+
+The document describes the protocols to be used when [ITU-T Q.1902.x] "*Bearer Independent Call Control*" are used as call control protocol in a 3G bearer independent CS core network 3G TS 23.205. [ITU-T Q.1902.x], operate between (G)MSC servers. The BICC architecture, as described in [ITU-T Q.1902.x] consists of a number of protocols. The following types of protocols are described: call control protocol, bearer control protocols and a resource control protocol for this architecture. The architecture complies with the requirements imposed by 3G TS 23.205 and 3G TS 23.153.
+
+NOTE – [ITU-T Q.1902.x] can be used in other network architectures than the one defined in TS 23.205.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 205 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 205 | 7.0.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429205v700 |
+| ATIS | ATIS.3GPP.29.205V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.205(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.205(R7-7.0.0).zip |
+| TTC | TS-3GA-29.205(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29205rel7v700.pdf |
+
+### 10.8.61 TS 29.212 Policy and charging control over Gx reference point
+
+This document provides the stage 3 specification of the Gx reference point for the present release. The functional requirements and the stage 2 specifications of the Gx reference point are contained in TS 23.203. The Gx reference point lies between the policy and charging rule function and the policy and charging enforcement function.
+
+Whenever it is possible, the present document specifies the requirements for the protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 212 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 212 | 7.2.0 | Published | 2007-10-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0329212v720 |
+| ATIS | ATIS.3GPP.29.212V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.212(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.212(R7-7.1.0).zip |
+| TTC | TS-3GA-29.212(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29212rel7v720.pdf |
+
+### 10.8.62 TS 29.213 Policy and charging control signalling flows and QoS parameter mapping
+
+The specification adds detailed flows of policy and charging control (PCC) over the Rx and Gx reference points and their relationship with the bearer level signalling flows over the Gn interface.
+
+The calls flows depicted in this Technical Specification represent usual cases, i.e., not all situations are covered. Detailed information provided in TS 29.212 and TS 29.214 shall be taken into consideration.
+
+The present specification also describes the binding and the mapping of QoS parameters among SDP, UMTS QoS parameters, and QoS authorization parameters.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 213 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 213 | 7.2.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0329213v720 |
+| ATIS | ATIS.3GPP.29.213V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.213(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.213(R7-7.1.0).zip |
+| TTC | TS-3GA-29.213(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29213rel7v720.pdf |
+
+### 10.8.63 TS 29.214 Policy and charging control over Rx reference point
+
+The present document provides the stage 3 specification of the Rx reference point for the present release. The functional requirements and the stage 2 specifications of the Rx reference point are contained in TS 23.203. The Rx reference point lies between the application function and the policy and charging rule function.
+
+Whenever it is possible, the present document specifies the requirements for the protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 214 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 214 | 7.2.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0329214v720 |
+| ATIS | ATIS.3GPP.29.214V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.214(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.214(R7-7.1.0).zip |
+| TTC | TS-3GA-29.214(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29214rel7v720.pdf |
+
+#### 10.8.64 TS 29.228 IP multimedia (IM) subsystem Cx and Dx interfaces; Signalling flows and message contents
+
+This Technical Specification (TS) specifies:
+
+- 1) the interactions between the HSS (home subscriber server) and the CSCF (call session control functions), referred to as the Cx interface;
+- 2) the interactions between the CSCF and the SLF (server locator function), referred to as the Dx interface.
+
+The IP multimedia (IM) subsystem Stage 2 is specified in 3G TS 23.228 and the signalling flows for the IP multimedia call control based on SIP and SDP are specified in 3G TS 24.228.
+
+This document addresses the signalling flows for Cx and Dx interfaces.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 228 | 7.7.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 228 | 7.7.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429228v770 |
+| ATIS | ATIS.3GPP.29.228V770-2007 | 7.7.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.228(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.228(R7-7.2.0).zip |
+| TTC | TS-3GA-29.228(Rel7)v7.7.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29228rel7v770.pdf |
+
+#### 10.8.65 TS 29.229 Cx and Dx interfaces based on the diameter protocol; Protocol details
+
+The document defines a transport protocol for use in the IP multimedia (IM) core network (CN) subsystem based on Diameter.
+
+This document is applicable to:
+
+- the Cx interface between the I-CSCF/S-CSCF and the HSS;
+- the Dx interface between the I-CSCF/S-CSCF and the SLF.
+
+Whenever it is possible, this document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 229 | 7.6.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 229 | 7.6.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429229v760 |
+| ATIS | ATIS.3GPP.29.229V760-2007 | 7.6.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.229(R7-7.6.0) | 7.6.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.229(R7-7.6.0).zip |
+| TTC | TS-3GA-29.229(Rel7)v7.6.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29229rel7v760.pdf |
+
+#### 10.8.66 TS 29.230 Diameter applications; 3GPP specific codes and identifiers
+
+The present document lists the 3GPP-specific Diameter protocol codes, including the AVP codes and experimental result codes.
+
+This document lists also the application identifiers assigned to 3GPP-specific Diameter applications by IANA and the Diameter command code range which is assigned to 3GPP by IANA.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 230 | 7.8.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 230 | 7.8.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429230v780 |
+| ATIS | ATIS.3GPP.29.230V780-2007 | 7.8.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.230(R7-7.7.0) | 7.7.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.230(R7-7.7.0).zip |
+| TTC | TS-3GA-29.230(Rel7)v7.8.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29230rel7v780.pdf |
+
+#### 10.8.67 TS 29.232 Media gateway controller (MGC) – Media gateway (MGW) interface; Stage 3
+
+The document describes the protocol to be used on the media gateway controller (MGC) – media gateway (MGW) interface. The media gateway controllers covered in this specification are the MSC server and the GMSC server. The basis for this protocol is the H.248.1 MEGACO protocol as
+
+specified in ITU-T and IETF. The BICC architecture, as described in TS 23.205 and 29.205, defines the usage of this protocol.
+
+This specification describes the changes to H.248.1/MEGACO which are needed to handle 3G specific traffic cases. This is done by using the H.248.1/MEGACO standard extension mechanism.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 232 | 7.7.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 232 | 7.7.0 | Published | 2007-10-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429232v770 |
+| ATIS | ATIS.3GPP.29.232V770-2007 | 7.7.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.232(R7-7.6.0) | 7.6.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.232(R7-7.6.0).zip |
+| TTC | TS-3GA-29.232(Rel7)v7.7.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29232rel7v770.pdf |
+
+### 10.8.68 TS 29.234 3GPP system to wireless local area network (WLAN) interworking; Stage 3
+
+The present document defines the Stage 3 protocol description for several reference points in the WLAN-3GPP interworking system.
+
+The present document is applicable to:
+
+- the Dw reference point between the 3GPP AAA server and an SLF;
+- the Wa reference point between the WLAN AN and the 3GPP AAA proxy;
+- the Wd reference point between the 3GPP AAA proxy and 3GPP AAA server;
+- the Wx reference point between the 3GPP AAA server and the HSS;
+- the Wm reference point between the 3GPP AAA server and the PDG;
+- the Wn reference point between the WLAN AN and the 3GPP WAG;
+- the Wg reference point between the 3GPP AAA server/proxy and the WAG.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 234 | 7.7.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 234 | 7.7.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429234v770 |
+| ATIS | ATIS.3GPP.29.234V770-2007 | 7.7.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.234(R7-7.6.0) | 7.6.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.234(R7-7.6.0).zip |
+| TTC | TS-3GA-29.234(Rel7)v7.7.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29234rel7v770.pdf |
+
+### **10.8.69 TS 29.240 3GPP generic user profile (GUP); Stage 3; Network**
+
+This document defines the stage 3 network protocol description to the 3GPP generic user profile (GUP), which includes the elements necessary to realise the stage 2 requirements in TS 23.240.
+
+The fact of having several domains within the 3GPP mobile system (e.g., circuit-switched, packet-switched, IP multimedia subsystem) and access technologies (e.g., GERAN, UTRAN and WLAN) introduces a wide distribution of data associated with the user. Further, the new functions both in terminals and networks mean that the data related to users, services and user equipment will be increased greatly. This causes difficulties for users, subscribers, network operators and value-added service providers to create, access and manage the user-related data located in different entities.
+
+The objective of specifying the 3GPP generic user profile is to provide a conceptual description to enable harmonized usage of the user-related information located in different entities. Technically, the 3GPP generic user profile provides an architecture, data description and interface with mechanisms to handle the data.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|----------------|-----------------------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 240 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 240 | 7.0.0 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429240v700 |
+| ATIS | ATIS.3GPP.29.240V 700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.240(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-29.240(R7-7.0.0).zip |
+| TTC | TS-3GA-29.240(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29240rel7v700.pdf |
+
+### **10.8.70 TS 29.278 Customized applications for mobile network enhanced logic (CAMEL) Phase 4; CAMEL application part (CAP) specification for IP multimedia subsystems (IMS)**
+
+The document specifies the CAMEL application part (CAP) supporting the fourth phase of the network feature customized applications for mobile network enhanced logic for IP multimedia CN subsystems. CAP is based on a sub-set of the ETSI core INAP CS-2 as specified by [ETSI EN 301 140-1]. Descriptions and definitions provided by [ETSI EN 301 140-1] are directly referenced by this standard in case no additions or clarifications are needed for the use in the CAP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 278 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 278 | 7.0.0 | Published | 2006-01-10 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429278v700 |
+| ATIS | ATIS.3GPP.29.278V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.278(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.278(R7-7.0.0).zip |
+| TTC | TS-3GA-29.278(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29278rel7v700.pdf |
+
+#### 10.8.71 TS 29.328 IP multimedia (IM) subsystem Sh interface; signalling flows and message contents
+
+This Technical Specification (TS) specifies the interactions between the HSS (home subscriber server) and the SIP AS (application server) and between the HSS and the OSA SCS (service capability server). This interface is referred to as the Sh reference point.
+
+The IP multimedia (IM) core network subsystem Stage 2 is specified in 3G TS 23.228 and the signalling flows for the IP multimedia call control based on SIP and SDP are specified in 3G TS 24.228.
+
+The IP multimedia (IM) session handling with the IP multimedia (IM) call model is specified in 3G TS 23.218.
+
+This document addresses the signalling flows and message contents for the protocol at the Sh interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 328 | 7.7.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 328 | 7.7.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429328v770 |
+| ATIS | ATIS.3GPP.29.328V770-2007 | 7.7.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.328(R7-7.6.0) | 7.6.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.328(R7-7.6.0).zip |
+| TTC | TS-3GA-29.328(Rel7)v7.7.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29328rel7v770.pdf |
+
+#### 10.8.72 TS 29.329 Sh interface based on the Diameter protocol; Protocol details
+
+The document defines a transport protocol for use in the IP multimedia (IM) core network (CN) subsystem based on diameter.
+
+This document is applicable to:
+
+- the Sh interface between an AS and the HSS;
+- the Sh interface between an SCS and the HSS.
+
+Whenever it is possible, this document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of diameter. Where this is not possible, extensions to diameter are defined within this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 329 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 329 | 7.4.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429329v740 |
+| ATIS | ATIS.3GPP.29.329V740-2007 | 7.4.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.329(R7-7.4.0) | 7.4.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-29.329(R7-7.4.0).zip |
+| TTC | TS-3GA-29.329(Rel7)v7.4.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29329rel7v740.pdf |
+
+### 10.8.73 TS 29.332 Media gateway control function (MGCF) – IM media gateway; Mn interface
+
+The present document describes the protocol to be used on the media gateway control function (MGCF) – IM media gateway (IM-MGW) interface. The basis for this protocol is the H.248.1/MEGACO protocol as specified in ITU-T and IETF. The IMS architecture is described in 3G TS 23.228. The interaction of the MGCF-IM MGW interface signalling procedures in relation to the SIP, and BICC/ISUP signalling at the MGCF are described in 3G TS 29.163.
+
+This specification describes the application of H.248.1/MEGACO on the Mn interface. Required extensions use the H.248.1/MEGACO standard extension mechanism.
+
+The present document is valid for a 3rd generation PLMN (UMTS) complying with Release 6 and later.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 332 | 7.8.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 332 | 7.8.0 | Published | 2007-10-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429332v780 |
+| ATIS | ATIS.3GPP.29.332V780-2007 | 7.8.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.332(R7-7.7.0) | 7.7.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-29.332(R7-7.7.0).zip |
+| TTC | TS-3GA-29.332(Rel7)v7.8.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29332rel7v780.pdf |
+
+### 10.8.74 TS 29.333 Multimedia resource function controller (MRFC) – Multimedia resource function processor (MRFP) Mp interface; Stage 3
+
+This document describes the protocol to be used on the multimedia resource function controller (MRFC) – multimedia resource function processor (MRFP) interface (Mp interface). The IMS architecture is described in TS 23.228, the functional requirements are described in 3G TS 23.333.
+
+This specification defines a profile of the gateway control protocol [ITU-T H.248.1], for controlling multimedia resource function processor supporting in-band user interaction, conferencing and transcoding for multimedia-services.
+
+The document is valid for a 3rd generation PLMN (UMTS) complying with Release 7 and later.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 333 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 333 | 7.1.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0429333v710 |
+| ATIS | ATIS.3GPP.29.333V 710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.333(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.333(R7-7.0.0).zip |
+| TTC | TS-3GA-29.333(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29333rel7v710.pdf |
+
+### 10.8.75 TS 29.414 Core network Nb data transport and transport signalling
+
+The document specifies the bearer data transport and bearer control protocols used between MGWs within the CS core network across the Nb Interface. This document assumes the implementation of the split of the call control and the bearer transport and control, as specified in TS 23.205; see Figure 10.8.75-1. The user plane protocol that uses this bearer data transport (Nb UP) is described in TS 29.415. Note that the document does not preclude an implementation of a combined MSC server and MGW.
+
+
+
+Q.1741.5(08)\_F10.8.75-1
+
+----- Signalling interface
+ ————— Signalling and data transfer interface
+
+Figure 10.8.75-1 – CS core network logical architecture diagram. The diagram shows the logical architecture of a CS core network. On the left, UTRAN \ GERAN Iu mode and GERAN A/Gb mode are connected to an MGW via Iu and A interfaces respectively. The MGW is connected to a PSTN/ Legacy/External network via an Nb interface. The MGW is also connected to an MSC server via an Mc interface. The MSC server is connected to a GMSC server via an Nc interface. The GMSC server is connected to the PSTN/ Legacy/External network via an Nb interface. The legend indicates that dashed lines represent signalling interfaces and solid lines represent signalling and data transfer interfaces.
+
+Figure 10.8.75-1 – CS core network logical architecture
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 414 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 414 | 7.2.0 | Published | 2007-04-05 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0329414v720 |
+| ATIS | ATIS.3GPP.29.414V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.414(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.414(R7-7.2.0).zip |
+| TTC | TS-3GA-29.414(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29414rel7v720.pdf |
+
+### 10.8.76 TS 29.415 Core network Nb user plane protocols
+
+The document specifies the user plane protocol of the bearer used between two MGWs within the CS core network, called the Nb UP protocol. This document assumes the implementation of the split between call control and the bearer transport and control, as specified in TS 23.205. Note that the document does not preclude an implementation of a combined MSC server and MGW.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 415 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 129 415 | 7.0.0 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0329415v700 |
+| ATIS | ATIS.3GPP.29.415V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-29.415(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-29.415(R7-7.0.0).zip |
+| TTC | TS-3GA-29.415(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts29415rel7v700.pdf |
+
+### 10.8.77 TR 29.994 Recommended infrastructure measures to overcome specific mobile station (MS) faults
+
+The present document clarifies recommended measures which may be adopted by 3GPP infrastructure utilizing GSM or GERAN as access network to enable interworking to be obtained between network and various user equipment (UE) implementations of the 3GPP specification. The objective is to obtain compatibility without changing the consolidated set of specifications. The present document describes the recommended changes to the infrastructure to cater for specific faults within some types of UE.
+
+The lifetime of the herein-described measures together with their potential impact on optimal network performance is out of the scope of the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 994 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 129 994 | 7.0.0 | Published | 2007-07-25 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGC-0129994v700 |
+| ATIS | ATIS.3GPP.29.994V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TR-3GA-29.994(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr29994rel7v700.pdf |
+
+### **10.8.78 TR 29.998-01 Open service access (OSA) application programming interface (API) mapping for open service access; Part 1: General issues on API mapping**
+
+The document is suggesting a mapping of the application programming interface (API) for open service access (OSA) onto CAMEL application part (CAP) operations and mobile application part (MAP) operations, and provides an overview of the content and structure of the various parts of this document. The mapping of the OSA API to the CAP and relevant MAP operations is considered informative and not normative.
+
+The API specification is contained in the 3G TS 29.198 series of specifications. An overview of these is available in the introduction of this document as well as in 3G TS 29.198-1. The concepts and the functional architecture for the open service access (OSA) are described by 3G TS 23.127. The requirements for OSA are defined in 3G TS 22.127.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 998-1 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 129 998-1 | 7.0.0 | Published | 2007-03-30 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGC-0529998-01v700 |
+| ATIS | ATIS.3GPP.29.998-01V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TR-3GA-29.998-01(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr29998-01rel7v700.pdf |
+
+### **10.8.79 TR 29.998-04-1 Open service access (OSA) application programming interface (API) mapping for open service access; Part 4: Call control service mapping; Sub-part 1: API to CAP mapping**
+
+This document investigates how the OSA call control interface class methods defined in 3G TS 29.198-4 can be mapped onto CAMEL application part (CAP) operations and mobile application part (MAP) operations.
+
+The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of this document as well as in 3G TR 29.998-1.
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The API specification is contained in the 3G TS 29.198 series of specifications. An overview of these is
+
+available in the introduction of this document as well as in 3G TS 29.198-1. The concepts and the functional architecture for the open service access (OSA) are described by 3G TS 23.127. The requirements for OSA are defined in 3G TS 22.127.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 998-4-1 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 129 998-4-1 | 7.0.0 | Published | 2007-03-30 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGC-0529998-04-1v700 |
+| TTC | TR-3GA-29.998-04-1(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr29998-04-1rel7v700.pdf |
+
+#### **10.8.80 TR 29.998-04-4 Open service access (OSA) application programming interface (API) mapping for open service access; Part 4: Call control service mapping; Sub-part 4: Multi-party call control internal service control (ISC)**
+
+This document investigates how the OSA call control interface Class methods defined in 3G TS 29.198-4 can be mapped onto SIP methods.
+
+The mapping of the OSA API to the SIP is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of this document as well as in 3G TR 29.998-1.
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The API specification is contained in the 3G TS 29.198 series of specifications. An overview of these is available in the introduction of this document as well as in 3G TS 29.198-1. The concepts and the functional architecture for the open service access (OSA) are described by 3G TS 22.121. The requirements for OSA are defined in 3G TS 22.127.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 998-4-4 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 129 998-4-4 | 7.0.0 | Published | 2007-03-30 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGC-0529998-04-4v700 |
+| ATIS | ATIS.3GPP.29.998-04-4V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TR-3GA-29.998-04-4(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr29998-04-4rel7v700.pdf |
+
+#### **10.8.81 TR 29.998-05-1 Open service access (OSA) application programming interface (API) mapping for open service access; Part 5: User interaction service mapping; Sub-part 1: API to CAP mapping**
+
+This document investigates how the OSA user interaction interface Class methods defined in 3G TS 29.198-5 can be mapped onto CAMEL application part operations and mobile application part operations.
+
+The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of this document as well as in 3G TR 29.998-1.
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The API specification is contained in the 3G TS 29.198 series of specifications. An overview of these is available in the introduction of this document as well as in 3G TS 29.198-1. The concepts and the functional architecture for the open service access (OSA) are described by 3G TS 23.127. The requirements for OSA are defined in 3G TS 22.127.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 998-5-1 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 129 998-5-1 | 7.0.0 | Published | 2007-03-30 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGC-0529998-05-1v700 |
+| ATIS | ATIS.3GPP.29.998-05-1V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TR-3GA-29.998-05-1(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr29998-05-1rel7v700.pdf |
+
+#### **10.8.82 TR 29.998-05-4 Open service access (OSA) application programming interface (API) mapping for open service access; Part 5: User interaction service mapping; Sub-part 4: API to SMS mapping**
+
+This document investigates how the OSA user interaction interface class methods defined in 3G TS 29.198-5 can be mapped onto CAMEL application part operations and mobile application part operations, within the context of SMS. The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of this document as well as in 3G TR 29.998-1.
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The API specification is contained in the 3G TS 29.198 series of specifications. An overview of these is available in the introduction of this document as well as in 3G TS 29.198-1. The concepts and the functional architecture for the open service access (OSA) are described by 3G TS 23.127. The requirements for OSA are defined in 3G TS 22.127.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 998-5-4 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 129 998-5-4 | 7.0.0 | Published | 2007-03-30 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGC-0529998-05-4v700 |
+| ATIS | ATIS.3GPP.29.998-05-4V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TR-3GA-29.998-05-4(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr29998-05-4rel7v700.pdf |
+
+### **10.8.83 TR 29.988-06-1 Open service access (OSA) application programming interface (API) mapping for open service access; Part 6: User location – user status service mapping; Sub-part 1: Mapping to mobile application part (MAP)**
+
+This document investigates how the OSA mobility interface class methods defined in TS 29.198-6 can be mapped onto CAMEL application part (CAP) operations and mobile application part (MAP) operations.
+
+The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in TR 29.998-1.
+
+The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e., the OSA APIs. The API specification is contained in the TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in TS 29.198-1. The concepts and the functional architecture for the open service access (OSA) are described by TS 23.198. The requirements for OSA are defined in TS 22.127.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|----------------|-----------------------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 998-6-1 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 129 998-6-1 | 7.0.0 | Published | 2007-03-30 | http://pda.etsi.org/pda/home.asp?wkr=DTR/TSGC-0529998-06-1v700 |
+| ATIS | ATIS.3GPP.29.998-06-1V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TR-3GA-29.998-06-1(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr29998-06-1rel7v700.pdf |
+
+### **10.8.84 TR 29.988-06-2 Open service access (OSA) application programming interface (API) mapping for open service access; Part 6: User location – user status service mapping; Sub-part 2: Mapping to session initiation protocol (SIP)**
+
+This document investigates how the OSA mobility interface class methods defined in TS 29.198-6 can be mapped onto IMS ISC interface (SIP) operations.
+
+The mapping of the OSA API to the SIP is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in TR 29.998-1.
+
+The OSA specifications define an architecture that enables application developers to make use of the network functionality through an open standardized interface, i.e., the OSA APIs. The API specification is contained in the TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in TS 29.198-1. The concepts and the functional architecture for the open service access (OSA) are described by TS 23.198. The requirements for OSA are defined in TS 22.127.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 998-6-2 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 129 998-6-2 | 7.0.0 | Published | 2007-03-30 | http://pda.etsi.org/pda/home.asp?wkr=DTR/TSGC-0529998-06-2v700 |
+| ATIS | ATIS.3GPP.29.998-06-2V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TR-3GA-29.998-06-2(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr29998-06-2rel7v700.pdf |
+
+### **10.8.85 TR 29.998-08 Open service access (OSA) application programming interface (API) mapping for open service access; Part 8: Data session control service mapping to CAP**
+
+This document investigates how the OSA data session control interface class methods defined in 3G TS 29.198-8 can be mapped onto CAMEL application part operations and mobile application part operations.
+
+The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of this document as well as in 3G TR 29.998-1.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-129 998-8 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 129 998-8 | 7.0.0 | Published | 2007-03-30 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGC-0529998-08v700 |
+| ATIS | ATIS.3GPP.29.998-08V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TR-3GA-29.998-06-2(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr29998-06-2rel7v700.pdf |
+
+## **10.9 31-series, UIM user identity module**
+
+### **10.9.1 TS 31.101 UICC-terminal interface; Physical and logical characteristics**
+
+The document specifies the interface between the UICC and the terminal for 3G-telecom network operation.
+
+The document specifies:
+
+- the requirements for the physical characteristics of the UICC;
+- the electrical interface between the UICC and the terminal;
+- the initial communication establishment and the transport protocols;
+- the model which serves as a basis for the logical structure of the UICC;
+- the communication commands and the procedures;
+- the application independent files and protocols.
+
+The administrative procedures and initial card management are not part of the document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.101V7.0.1 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/31/A31101-701.pdf |
+| CCSA | CCSA-TSD-131 101 | 7.0.1 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 131 101 | 7.0.1 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0631101v701 |
+| ATIS | ATIS.3GPP.31.101V701-2007 | 7.0.1 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-31.101(R7-7.0.1) | 7.0.1 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-31.101(R7-7.0.1).zip |
+
+## 10.9.2 TS 31.102 Characteristics of the USIM application
+
+The document defines the USIM application for 3G-telecom network operation.
+
+The document specifies:
+
+- specific command parameters;
+- file structures;
+- contents of EFs (elementary files);
+- security functions;
+- application protocol to be used on the interface between UICC (USIM) and ME.
+
+This is to ensure interoperability between a USIM and an ME independently of the respective manufacturer, card issuer or operator.
+
+The document does not define any aspects related to the administrative management phase of the USIM. Any internal technical realization of either the USIM or the ME is only specified where these are reflected over the interface. The document does not specify any of the security algorithms that may be used.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.102V7.10.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/31/A31102-7a0.pdf |
+| CCSA | CCSA-TSD-131 102 | 7.10.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 131 102 | 7.10.0 | Published | 2007-10-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0631102v7a0 |
+| ATIS | ATIS.3GPP.31.102V7100-2007 | 7.10.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-31.102(R7-7.8.0) | 7.8.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-31.102(R7-7.8.0).zip |
+
+### 10.9.3 TS 31.103 Characteristics of the IP multimedia services identity module (ISIM) application
+
+This document defines the ISIM application for access to IMS services.
+
+This document specifies:
+
+- specific command parameters;
+- file structures;
+- contents of EFs (elementary files);
+- security functions;
+- application protocol to be used on the interface between UICC (ISIM) and terminal.
+
+This is to ensure interoperability between an ISIM and terminal independently of the respective manufacturer, card issuer or operator.
+
+This document does not define any aspects related to the administrative management phase of the ISIM. Any internal technical realization of either the ISIM or the terminal is only specified where these are reflected over the interface. This document does not specify any of the security algorithms that may be used.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.103V7.3.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/31/A31103-730.pdf |
+| CCSA | CCSA-TSD-131 103 | 7.3.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 131 103 | 7.3.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0631103v730 |
+| ATIS | ATIS.3GPP.31.103V730-2007 | 7.3.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-31.103(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-31.103(R7-7.2.0).zip |
+
+### 10.9.4 TS 31.111 USIM application toolkit (USAT)
+
+The document defines the interface between the universal ICC (UICC) and the mobile equipment (ME), and mandatory ME procedures, specifically for "USIM application toolkit".
+
+USAT is a set of commands and procedures for use during the network operation phase of 3G, in addition to those defined in TS 31.101.
+
+Specifying the interface is to ensure interoperability between a UICC and an ME independently of the respective manufacturers and operators.
+
+The document defines:
+
+- the commands;
+- the application protocol;
+- the mandatory requirements on the UICC and ME for each procedure.
+
+This document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the UICC or the ME is only specified where these reflect over the interface. The document does not specify any of the security algorithms that may be used.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.111V7.8.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/31/A31111-780.pdf |
+| CCSA | CCSA-TSD-131 111 | 7.8.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 131 111 | 7.8.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0631111v780 |
+| ATIS | ATIS.3GPP.31.111V780-2007 | 7.8.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-31.111(R7-7.3.0) | 7.3.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-31.111(R7-7.3.0).zip |
+
+### 10.9.5 TS 31.112 USAT interpreter architecture description; Stage 2
+
+This document defines the Stage 2 description for the USAT interpreter system. As the second stage of a three-level structure, it is derived from the Stage 1 service description.
+
+This document defines the overall architecture for the USAT interpreter system:
+
+- role models;
+- system architecture;
+- function and information flow.
+
+The Stage 3 documents shall conform to this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.112V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/31/A31112-700.pdf |
+| CCSA | CCSA-TSD-131 112 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 131 112 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0631112v700 |
+| ATIS | ATIS.3GPP.31.112V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-31.112(R7-7.0.0) | 7.0.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-31.112(R7-7.0.0).zip |
+
+### 10.9.6 TS 31.113 USAT interpreter byte codes
+
+This document specifies the byte codes that are recognized by an USAT interpreter. The byte codes primary purpose is to provide efficient programmatic access to the SIM application toolkit commands.
+
+The design objectives of the byte code set are:
+
+- compact representation for efficient transmission over the air interface;
+- minimization of USAT interpreter complexity to minimize SIM footprint and ease compliance testing;
+- easily configured and extended;
+- source language independent although XML-style mark-up languages are explicitly envisioned;
+- transport bearer independent (e.g., SMS, GPRS, etc.);
+- transport protocol independent;
+- independent from design of external entities.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.113V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/31/A31113-700.pdf |
+| CCSA | CCSA-TSD-131 113 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 131 113 | 7.0.0 | Published | 2007-06-25 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0631113v700 |
+| ATIS | ATIS.3GPP.31.113V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-31.113(R7-7.0.0) | 7.0.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-31.113(R7-7.0.0).zip |
+
+### 10.9.7 TS 31.114 USAT interpreter protocol and administration
+
+This document specifies the transmission protocol to be used to communicate with the USAT interpreter and the administrative structures and procedures to administer the USAT interpreter.
+
+This document does not specify any USAT interpreter byte code commands.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.114V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/31/A31114-700.pdf |
+| CCSA | CCSA-TSD-131 114 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 131 114 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0631114v700 |
+| ATIS | ATIS.3GPP.31.114V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-31.114(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-31.114(R7-7.0.0).zip |
+
+### 10.9.8 TS 31.115 Secured packet structure for (U)SIM toolkit applications
+
+This document specifies the structure of the secured packets in implementations using short message service point-to-point (SMS-PP), short message service cell broadcast (SMS-CB), and unstructured supplementary service data (USSD) based on TS 102 225.
+
+The structure of the secured packets shall comply with the one defined in TS 102 225. The present document only contains additional requirements or explicit limitations for SIM/USIM applications.
+
+It is applicable to the exchange of secured packets between an entity in a 3G or GSM PLMN and an entity in the (U)SIM.
+
+Secured packets contain application messages to which certain mechanisms according to TS 102 224 have been applied. Application messages are commands or data exchanged between an application resident in or behind the 3G or GSM PLMN and on the (U)SIM. The sending/receiving entity in the 3G or GSM PLMN and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into secured packets.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.115V7.1.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/31/A31115-710.pdf |
+| CCSA | CCSA-TSD-131 115 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 131 115 | 7.1.0 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0631115v710 |
+| ATIS | ATIS.3GPP.31.115V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-31.115(R7-7.1.0) | 7.1.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-31.115(R7-7.1.0).zip |
+
+### 10.9.9 TS 31.116 Remote APDU structure for (U)SIM toolkit applications
+
+The present document defines the remote management of files and applets on the SIM/USIM.
+
+It describes the APDU format for remote management.
+
+Furthermore, the document specifies:
+
+- a set of commands coded according to this APDU structure and used in the remote file management on the SIM/USIM specified in 3G TS 51.011, 3G TS 31.101 and 3G TS 31.102;
+- a set of commands coded according to this APDU structure and used in the remote applet management on the SIM/USIM. This is based on TS 102 226.
+
+The remote APDU structure for SIM/USIM applications shall comply with the one defined in TS 102 226. The present document only contains additional requirements or explicit limitations for SIM/USIM applications.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.116V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/31/A31116-700.pdf |
+| CCSA | CCSA-TSD-131 116 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 131 116 | 7.0.0 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0631116v700 |
+| ATIS | ATIS.3GPP.31.116V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-31.116(R7-7.0.0) | 7.0.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-31.116(R7-7.0.0).zip |
+
+### 10.9.10 TS 31.120 UICC-terminal interface; Physical, electrical and logical test specification
+
+The present document specifies the interface test for the terminal/UICC.
+
+The present document specifies the tests of:
+
+- physical characteristics of the UICC;
+- the electrical interface between the UICC and the terminal;
+- the initial communication establishment and the transport protocols;
+- the application-independent procedures.
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|--------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-31.120(R7-7.0.0) | 7.0.0 | Approved | 2007-12-24 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-31.120(R7-7.0.0).zip |
+
+### 10.9.11 TS 31.121 UICC-terminal interface; Universal subscriber identity module (USIM) application test specification
+
+The present document provides the UICC-terminal interface conformance test specification between the 3rd generation terminal and USIM (universal subscriber identity module) as an application on
+
+the UICC and the terminal for 3G telecom network operation and between a GERAN terminal and USIM (universal subscriber identity module) as an application on the UICC and the GERAN terminal for 2G telecom network operation:
+
+- the default setting of the USIM;
+- the applicability of each test case;
+- the test configurations;
+- the conformance requirement and reference to the core specifications;
+- the test purposes; and
+- a brief description of the test procedure and the specific acceptance criteria.
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|--------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-31.121(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-31.121(R7-7.0.0).zip |
+
+### 10.9.12 TS 31.130 (U)SIM application programming interface; (U)SIM API for Java card
+
+The present document defines the (U)SIM application programming interface extending the "UICC API for Java card™".
+
+This API allows to develop a (U)SAT application running together with a (U)SIM application and using GSM/3G network features.
+
+The present document includes information applicable to network operators, service providers, server manufacturers, SIM manufacturers, USIM manufacturers, and database manufacturers.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.130V7.6.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/31/A31130-760.pdf |
+| CCSA | CCSA-TSD-131 130 | 7.6.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 131 130 | 7.6.0 | Published | 2007-06-25 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0631130v760 |
+| ATIS | ATIS.3GPP.31.130V760-2007 | 7.6.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-31.130(R7-7.5.0) | 7.5.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-31.130(R7-7.5.0).zip |
+
+### 10.9.13 TS 31.131 C-language binding to (U)SIM API
+
+A subscriber identity module application programming interface (SIM API) has been defined in 3G TS 42.019 as a technology-independent API by which toolkit applications and (U)SIMs cooperate. That specification is independent of the programming language technology used to create the application, the platform used to host the application and the runtime environment used to execute the application.
+
+The present document includes information applicable to (U)SIM toolkit application developers creating applications using the C programming language ISO/IEC 9899. The present document describes an interface between toolkit applications written in the C programming language and the (U)SIM in order to realize the cooperation set forth in 3G TS 42.019. In particular, the API described herein provides the service of assembling proactive commands and disassembling the responses to these commands for the application programmer.
+
+Software tools, integrated software development environments and software management systems that may be used to create application programs are explicitly out of scope of the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.131V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/31/A31131-700.pdf |
+| CCSA | CCSA-TSD-131 131 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 131 131 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0631131v700 |
+| ATIS | ATIS.3GPP.31.131V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-31.131(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-31.131(R7-7.0.0).zip |
+
+#### 10.9.14 TS 31.133 IP multimedia services identity module (ISIM) application programming interface (API); ISIM API for Java card™
+
+This document defines the ISIM application programming interface extending the "UICC API for Java card™" [ETSI TS 102 241].
+
+This API allows to develop an application running together with a ISIM application.
+
+The document includes information applicable to network operators, service providers, and manufacturers of ISIM server equipment and database.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.133V7.1.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/31/A31133-710.pdf |
+| CCSA | CCSA-TSD-131 133 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 131 133 | 7.1.0 | Published | 2007-06-22 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGC-0631133v710 |
+| ATIS | ATIS.3GPP.31.133V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-31.133(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-31.133(R7-7.1.0).zip |
+
+### 10.9.15 TS 31.213 Test specification for (U)SIM; Application programming interface (API) for Java card™
+
+This document covers the minimum characteristics considered necessary in order to provide compliance to TS 31.130.
+
+The document describes the technical characteristics and methods of test for testing the (U)SIM API for Java card™ (TS 31.130) implemented in the (U)SIM. It specifies the following parts:
+
+- test applicability;
+- test environment description;
+- tests format;
+- test area reference;
+- conformance requirements;
+- test suite files;
+- test procedure;
+- test coverage; and
+- a description of the associated testing tools that shall be used.
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|--------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-31.213(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-31.213(R7-7.0.0).zip |
+
+### 10.9.16 TR 31.900 SIM/USIM internal and external interworking aspects
+
+This document describes:
+
+- the different cases of interworking between a 2G or 3G ICC and a 2G or 3G ME;
+- the different cases of interworking between any given ME/ICC combination and the rest of the network;
+- the possibilities of interworking between a SIM and a USIM together on a single UICC;
+- the possibilities of interworking between several USIMs on a single UICC.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-31.900V7.1.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/31/A31900-710.pdf |
+| CCSA | CCSA-TSD-131 900 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 131 900 | 7.1.0 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGC-0631900v710 |
+| ATIS | ATIS.3GPP.31.900V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.9.17 TR 31.919 2G/3G Java card™ API-based applet interworking
+
+The present document describes:
+
+- description of 3G TS 43.019 APIs and ETSI TS 102 241/3G TS 31.130 APIs interworking;
+- the behaviour and limitations of the 3G TS 43.019 APIs used in 3G environment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-31.919V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/31/A31919-700.pdf |
+| CCSA | CCSA-TSD-131 919 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 131 919 | 7.0.0 | Published | 2007-06-22 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGC-0631919v700 |
+| ATIS | ATIS.3GPP.31.919V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+## 10.10 32-series, operation and maintenance
+
+### 10.10.1 TS 32.101 3G telecommunication management; Principles and high-level requirements
+
+The document establishes and defines the management principles and high-level requirements for the management of UMTS.
+
+In particular, this document identifies the requirements for:
+
+- the upper level of a UMTS management system;
+- the reference model, showing the elements the UMTS management system interacts with;
+- the network operator processes needed to run, operate and maintain a UMTS network;
+- the functional architecture of the UMTS management system;
+- the principles to be applied to UMTS management interfaces.
+
+The requirements identified in this document are directed to the further development of UMTS management specifications, as well as the development of UMTS management products. This document can be seen as guidance for the development of all other Technical Specifications addressing the management of UMTS.
+
+This document does not provide physical architectures of the UMTS management system. These aspects are defined and discussed in more detail in TS 32.102.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 101 | 7.3.1 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 101 | 7.3.1 | Published | 2007-03-30 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532101v731 |
+| ATIS | ATIS.3GPP.32.101V731-2007 | 7.3.1 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.101(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.101(R7-7.0.0).zip |
+| TTC | TS-3GA-32.101(Rel7)v7.3.1 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32101rel7v731.pdf |
+
+### 10.10.2 TS 32.102 3G telecommunication management; Architecture
+
+The document identifies and standardizes the most important and strategic contexts in the physical architecture for the management of UMTS. It serves as a framework to help define a telecom management physical architecture for a planned UMTS and to adopt standards and provide products that are easy to integrate.
+
+The requirements identified in this document are applicable to all further development of UMTS telecom management specifications as well as the development of UMTS management products. This document can be seen as guidance for the development of all other Technical Specifications addressing the management of UMTS, except TS 32.101.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 102 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 102 | 7.1.0 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532102v710 |
+| ATIS | ATIS.3GPP.32.102V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.102(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.102(R7-7.2.0).zip |
+| TTC | TS-3GA-32.102(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32102rel7v710.pdf |
+
+### 10.10.3 TS 32.111-1 Telecommunication management; Fault management; Part 1: 3G fault management requirements
+
+The document specifies the overall requirements for 3G fault management (FM) as it applies to the network elements (NE), element manager (EM) and network manager (NM).
+
+This document defines the FM concept and functional requirements for the detection of faults and the generation, collection and presentation of alarms, operational state data and test results across 3G systems. These functions are described on a non-formal level since the formal standardization of
+
+these functions across the different vendors' equipment is not required. The functional areas specified in this document cover:
+
+- fault surveillance and detection in the NEs;
+- notification of alarms (including alarm cease) and operational state changes;
+- retrieval of current alarms from the NEs;
+- fault isolation and defence mechanisms in the NEs;
+- alarm filtering;
+- management of alarm severity levels;
+- alarm and operational state data presentation and analysis at the operations system (OS);
+- retention of alarm and operational state data in the NEs and the OS; and
+- the management of tests.
+
+Any (re)configuration activity exerted from the EM as a consequence of faults will not be subject of this document; these are described in the TS 32.600-series.
+
+This document defines the functional requirements for the standard Itf-N, for the purpose of fault management of 3G networks, as seen from the network manager (NM). The Itf-N is fully standardized so as to connect systems of any vendor to the NM via this interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 111-1 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/technical.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 111-1 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532111-1v700 |
+| ATIS | ATIS.3GPP.32.111-1V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.111-01(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.111-01(R7-7.0.0).zip |
+| TTC | TS-3GA-32.111-1(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32111-1rel7v700.pdf |
+
+#### **10.10.4 TS 32.111-2 Telecommunication management; Fault management; Part 2: Alarm integration reference point: Information service**
+
+The document defines the alarm integration reference point (IRP) information service (IS), which addresses the alarm surveillance aspects of fault management (FM), applied to the N interface.
+
+The purpose of the alarm IRP is to define an interface through which a "system" (typically a network element manager or a network element) can communicate alarm information for its managed objects to one or several manager systems (typically network management systems).
+
+The alarm IRP IS defines the semantics of alarms and the interactions visible across the reference point in a protocol-neutral way. It defines the semantics of the operations and notifications visible in the IRP. It does not define the syntax or encoding of the operations, notifications and their parameters.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 111-2 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 111-2 | 7.1.0 | Published | 2007-03-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532111-2v710 |
+| ATIS | ATIS.3GPP.32.111-2V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.111-02(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.111-02(R7-7.1.0).zip |
+| TTC | TS-3GA-32.111-2(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32111-2rel7v710.pdf |
+
+### 10.10.5 TS 32.111-3 Telecommunication management; Fault management; Part 3: Alarm integration reference point: CORBA solution set
+
+The document specifies the CORBA solution set (SS) for the IRP whose semantics is specified in alarm IRP: information service (IS) (3G TS 32.111-2).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 111-3 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 111-3 | 7.1.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532111-3v710 |
+| ATIS | ATIS.3GPP.32.111-3V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.111-03(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.111-03(R7-7.1.0).zip |
+| TTC | TS-3GA-32.111-3(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32111-3rel7v710.pdf |
+
+### 10.10.6 TS 32.111-5 Telecommunication management; Alarm integration reference point (IRP): eXtensible markup language (XML) definitions
+
+This document specifies the XML definitions for the alarm integration reference point (alarm IRP) as it applies to Itf-N, in accordance with alarm IRP IS definitions in TS 32.111-2 as well as notification log IRP XML definitions in TS 32.335.
+
+The document defines the XML syntax of alarm IRP notifications that is to be used in conjunction with notification log IRP XML definitions for notification log IRP XML data file and the NL IRP XML notification format in TS 32.335.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 111-5 | 7.0.1 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 111-5 | 7.0.1 | Published | 2007-10-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532111-5v701 |
+| ATIS | ATIS.3GPP.32.111-5V701-2007 | 7.0.1 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.111-05(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.111-05(R7-7.0.0).zip |
+| TTC | TS-3GA-32.111-5(Rel7)v7.0.1 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32111-5rel7v710.pdf |
+
+### 10.10.7 TS 32.140 Telecommunication management; Subscription management (SuM) requirements
+
+The present document defines the service requirements and high-level architecture for SuM.
+
+SuM is expected to evolve in stages over several releases of 3GPP specifications.
+
+The present document provides additional supporting material, which whilst not within the scope of this release, provides an insight towards the future evolution. This is in order that initial work may be done with an appreciation of the wider context expected in future releases of 3GPP specifications.
+
+SuM for 3GPP is primarily concerned with the ability to define subscription profiles and associate the profile with subscribers, users and services that are authorized by agreements. The subscription profile may be used in the process of configuring various network resources (access and core) to make the service a reality for the user.
+
+The management capabilities extend to the creation, modification, synchronization, and re-application of subscription profiles.
+
+The present document is oriented towards a standardized interface into the home subscriber server (HSS) in order that services can be provisioned and maintained.
+
+The present document includes information applicable to network operators, content providers, and terminal and network manufacturers.
+
+The present document contains the core requirements for SuM, which are sufficient to provide management services.
+
+The method by which applications subscribe to OSA is not within the scope of the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 140 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 140 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TS/SGS-0532140v700 |
+| ATIS | ATIS.3GPP.32.140V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.140(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.140(R7-7.0.0).zip |
+| TTC | TS-3GA-32.140(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32140rel7v700.pdf |
+
+#### 10.10.8 TS 32.141 Telecommunication management; Subscription management (SuM) architecture
+
+Subscription management (SuM) is a feature that permits service providers, value-added service providers, and mobile operators to provision services for a specific subscriber. The feature is necessary to allow service providers and operators to provision, control, monitor and bill the configuration of services that they offer to their subscribers.
+
+For further details, please refer to 3G TS 32.140 SuM requirements specification that gives an overview of SuM requirements.
+
+The present document defines the architecture for subscription management (SuM).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 141 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 141 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TS/SGS-0532141v700 |
+| ATIS | ATIS.3GPP.32.141V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.141(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.141(R7-7.0.0).zip |
+| TTC | TS-3GA-32.141(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32141rel7v700.pdf |
+
+#### 10.10.9 TS 32.150 Telecommunication management; Integration reference point (IRP) concept and definitions
+
+The present document provides the overall concept for all integration reference point (IRP) specifications produced by 3GPP. Relevant IRP overview and high-level definitions are already provided in 3G TS 32.101 and 3G TS 32.102.
+
+The present document is a member of a TS-family consisting of 3G TS 32.150, 3G TS 32.151, 3G TS 32.152.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 150 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 150 | 7.2.0 | Published | 2007-04-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532150v720 |
+| ATIS | ATIS.3GPP.32.150V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.150(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.150(R7-7.2.0).zip |
+| TTC | TS-3GA-32.150(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32150rel7v720.pdf |
+
+#### 10.10.10 TS 32.151 Telecommunication management; Integration reference point (IRP) information service (IS) template
+
+The present document contains the template to be used for the production of all integration reference point (IRP) information service (IS) specifications within the 3GPP 32-series.
+
+The present document is a member of a TS-family consisting of 3G TS 32.150, 3G TS 32.151, 3G TS 32.152.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 151 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 151 | 7.2.0 | Published | 2007-03-30 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532151v720 |
+| ATIS | ATIS.3GPP.32.151V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.151(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.151(R7-7.2.0).zip |
+| TTC | TS-3GA-32.151(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32151rel7v720.pdf |
+
+#### 10.10.11 TS 32.152 Telecommunication management; Integration reference point (IRP) information service (IS) unified modelling language (UML) repertoire
+
+This TS documents the necessary and sufficient set of UML notations and model elements, including the ones built by the UML extension mechanism <>, for use by 3GPP IRP IS authors. Collectively, this set of notations and model elements is called the 3GPP IRP IS modelling repertoire.
+
+The selection of the UML notations and model elements in this repertoire is based on the needs of the existing 3GPP IRP IS specifications. Future IRP IS releases may require the use of additional UML notations or model elements.
+
+IRP IS specifications shall employ the UML notation and model elements of this repertoire and may also employ other UML notation and model elements considered necessary. However, before any other UML notation and model elements may be employed in an approved 3GPP IRP specification, the other notation and model elements should be agreed for inclusion first in this repertoire.
+
+The present document is a member of a TS-family consisting of 3G TS 32.150, 3G TS 32.151, 3G TS 32.152.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 152 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 152 | 7.1.0 | Published | 2007-04-13 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532152v710 |
+| ATIS | ATIS.3GPP.32.152V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.152(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.152(R7-7.1.0).zip |
+| TTC | TS-3GA-32.152(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32152rel7v710.pdf |
+
+#### **10.10.12 TS 32.154 Telecommunication management; Backward and forward compatibility (BFC); Concept and definitions**
+
+The present document gives recommendations to develop future IRP specifications in a backward compatible (BC) way so that the group of IRPManager(s) and IRPAgent(s) are not forced to be upgraded in lock step.
+
+The business case for supporting such group, as described above, is complex. It may not relate to the functions of the supported IRPs alone. Rather, it can relate to the cost of coordination of IRPVersion upgrades, the cost of maintaining an old IRPVersion and the cost of using single-vendor or multi-vendor IRPAgents. These considerations are operator deployment scenarios specific.
+
+Clause 4 specifies the Recommendations and clause 5 describes the system context where the Recommendations are applicable.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 154 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 154 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532154v700 |
+| ATIS | ATIS.3GPP.32.154V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.154(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.154(R7-7.0.0).zip |
+| TTC | TS-3GA-32.154(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32154rel7v700.pdf |
+
+#### 10.10.13 TS 32.171 Subscription management (SuM) network resource model (NRM) integration reference point (IRP): Requirements
+
+The present document defines, in addition to the requirements defined in 3G TS 32.101, 3G TS 32.102, 3G TS 32.140, 3G TS 32.141, requirements for the present SuM NRM IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 171 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 171 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532171v700 |
+| ATIS | ATIS.3GPP.32.171V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.171(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.171(R7-7.0.0).zip |
+| TTC | TS-3GA-32.171(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32171rel7v700.pdf |
+
+#### 10.10.14 TS 32.172 Telecommunication management; Subscription management (SuM) network resource model (NRM) integration reference point (IRP): Information service (IS)
+
+The interface Itf-N, defined in 3G TS 32.102, is built up by a number of integration reference points (IRPs) and a related name convention, which realize the functional capabilities over this interface. The basic structure of the IRPs is defined in 3G TS 32.101 and 3G TS 32.102.
+
+The present document defines the network resources model (NRM) for the SuM IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 172 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 172 | 7.1.0 | Published | 2007-10-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532172v710 |
+| ATIS | ATIS.3GPP.32.172V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.172(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.172(R7-7.0.0).zip |
+| TTC | TS-3GA-32.172(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32172rel7v710.pdf |
+
+#### 10.10.15 TS 32.175 Telecommunication management; Subscription management (SuM) network resource model (NRM) integration reference point (IRP): eXtensible markup language (XML) definition
+
+The purpose of this *Subscription Management (SuM) Network Resource Model IRP XML definition* is to define the mapping of the IRP information model (see TS 32.172) to the protocol specific details necessary for implementation of this IRP in an XML environment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 175 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 175 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532175v700 |
+| ATIS | ATIS.3GPP.32.175 V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.175(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.175(R7-7.0.0).zip |
+| TTC | TS-3GA-32.175(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32175rel7v700.pdf |
+
+#### 10.10.16 TS 32.240 Telecommunication management; Charging management; Charging architecture and principles
+
+The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in the present document, which thus provides an umbrella for other charging management TSs that specify:
+
+- the content of the CDRs per domain/subsystem/service (offline charging);
+- the content of real-time charging events per domain/subsystem/service (online charging);
+- the functionality of online and offline charging for those domains/subsystems/services;
+
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The purposes of the present document are:
+
+- to lay down common principles of charging in the network; and
+- to specify a logical common charging architecture that applies to all 3GPP domains, subsystems and services.
+
+A set of domain/subsystem/service-specific TSs covers the bearer (CS, PS, WLAN domains), subsystem (IMS) and service (MMS, LCS, etc.) levels, respectively, in the 3G TS 32.25x, 32.26x and 32.27x number range. These 3G TSs describe the mapping of the common architecture specified in the present document onto the specific domain/subsystem/service and the scenarios and information for online and offline charging that are specific to the domain/subsystem/service. They are commonly referred to as the "middle tier (charging) TSs".
+
+A set of 3G TSs in the 32.29x range covers common aspects such as CDR parameter and syntax descriptions, online and offline charging applications, and the charging interactions within the network (CDR transfer) as well as between the network and the billing domain (CDR file transfer).
+
+The complete document structure for these 3G TSs is outlined in Figure 10.10.16-1.
+
+
+
+```
+
+graph TD
+ 32.240[32.240 Charging Architecture and Principles] --> 32.250[32.250 CS-domain Charging]
+ 32.240 --> 32.251[32.251 PS-domain Charging]
+ 32.240 --> 32.252[32.252 WLAN Charging]
+ 32.240 --> 32.260[32.260 IM Subsystem Charging]
+ 32.250 --> 32.270[32.270 MMS Charging]
+ 32.251 --> 32.271[32.271 LCS Charging]
+ 32.252 --> 32.27x[32.27x tbd.]
+ 32.260 --> 32.27x
+ 32.270 --> 32.295[32.295 Charging Data Record (CDR) transfer]
+ 32.271 --> 32.297[32.297 Charging Data Record (CDR) file format and transfer]
+ 32.27x --> 32.299[32.299 Diameter Charging Application]
+ 32.295 --> 32.296[32.296 Online Charging System (OCS) applications and interfaces]
+ 32.297 --> 32.298[32.298 Charging Data Record (CDR) parameter description]
+ 32.299 --> 32.298
+
+```
+
+A hierarchical diagram showing the structure of 3G charging documents. At the top is '32.240 Charging Architecture and Principles'. Below it are four boxes: '32.250 CS-domain Charging', '32.251 PS-domain Charging', '32.252 WLAN Charging', and '32.260 IM Subsystem Charging'. Below these are three boxes: '32.270 MMS Charging', '32.271 LCS Charging', and '32.27x tbd.'. Below these are three boxes: '32.295 Charging Data Record (CDR) transfer', '32.297 Charging Data Record (CDR) file format and transfer', and '32.299 Diameter Charging Application'. Below these are two boxes: '32.296 Online Charging System (OCS) applications and interfaces' and '32.298 Charging Data Record (CDR) parameter description'.
+
+Q.1741.5(08)\_F10.10.16-1
+
+**Figure 10.10.16-1 – Charging documents structure**
+
+All references, abbreviations, definitions, descriptions, principles and requirements, used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, 3GPP TR 21.905. Those that are common across charging management in GSM/UMTS domains, services or subsystems are provided in the present document (umbrella TS), and are copied into clause 3 of the other TSs depicted in the figure above, for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-------------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132
240 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 240 | 7.2.0 | Published | 2007-03-30 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532240v720 |
+| ATIS | ATIS.3GPP.32.240
V720-2007 | 7.2.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-
32.240(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.240(R7-7.2.0).zip |
+| TTC | TS-3GA-
32.240(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32240rel7v720.pdf |
+
+#### 10.10.17 TS 32.250 Telecommunication management; Charging management; Circuit-switched (CS) domain charging
+
+The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in 3G TS 32.240, which provides an umbrella for other charging management TSs that specify:
+
+- the content of the CDRs per domain and subsystem (offline charging);
+- the content of real-time charging messages per domain/subsystem (online charging);
+- the functionality of online and offline charging for those domains and subsystems;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in 3G TS 32.240.
+
+The present document specifies the offline charging description for the 3GPP circuit-switched domain, based on the functional descriptions of the 3GPP bearer-, tele- and supplementary services in 3G TS 22.002, 3GPP TS 22.003 and 3G TS 22.004, respectively. This charging description includes the offline charging architecture and scenarios specific to the CS domain, as well as the mapping of the common charging architecture specified in 3G TS 32.240 onto the CS domain. It further specifies the structure and content of the CDRs for offline charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in 3G TS 32.240.
+- The parameters, abstract syntax and encoding rules for these CDR types are specified in 3G TS 32.298.
+- The file-based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in 3G TS 32.297.
+
+Note that online charging for the CS domain is solely based on CAMEL (3G TS 23.078 and 3G TS 29.078) and therefore outside the scope of the 32-series charging specifications.
+
+All references, abbreviations, definitions, descriptions, principles and requirements, used in the present document, that are common across 3G TSs, are defined in 3G TR 21.905. Those that are common across charging management in GSM/UMTS domains or subsystems are provided in the umbrella document 3G TS 32.240 and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 250 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 250 | 7.1.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532250v710 |
+| ATIS | ATIS.3GPP.32.250V 710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.250(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.250(R7-7.0.0).zip |
+| TTC | TS-3GA-32.250(Rel7)v7.1.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32250rel7v710.pdf |
+
+#### **10.10.18 TS 32.251 Telecommunication management; Charging management; Packet-switched (PS) domain charging**
+
+The present document is part of a series of documents specifying charging functionality and charging management in GSM/UMTS networks.
+
+The present document specifies the offline and online charging description for the packet-switched (PS) domain (i.e., GPRS), based on the functional Stage 2 description of GPRS in 3G TS 23.060. This charging description includes the offline and online charging architecture and scenarios specific to the PS domain, as well as the mapping of the common 3GPP charging architecture specified in 3G TS 32.240 onto the PS domain. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in 3G TS 32.240.
+- The parameters, abstract syntax and encoding rules for the CDRs are specified in 3G TS 32.298.
+- A transaction based mechanism for the transfer of CDRs within the network is specified in 3G TS 32.295.
+- The file-based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in 3G TS 32.297.
+- The 3GPP Diameter application that is used for PS domain offline and online charging is specified in 3G TS 32.299.
+
+Note that a CAMEL-based prepaid function and protocol is also specified for the PS domain (3G TS 23.078 and 3G TS 29.078). CAMEL entities and functions are outside the scope of the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 251 | 7.5.1 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 251 | 7.5.1 | Published | 2007-10-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532251v751 |
+| ATIS | ATIS.3GPP.32.251V751-2007 | 7.5.1 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.251(R7-7.4.0) | 7.4.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.251(R7-7.4.0).zip |
+| TTC | TS-3GA-32.251(Rel7)v7.5.1 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32251rel7v750.pdf |
+
+### 10.10.19 TS 32.252 Telecommunication management; Charging management; Wireless local area network (WLAN) charging
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in TS 32.240, which provides an umbrella for other charging management documents that specify:
+
+- the content of the CDRs per domain and subsystem (offline charging);
+- the content of real-time charging messages per domain/subsystem (online charging);
+- the functionality of online and offline charging for those domains and subsystems;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in TS 32.240.
+
+The document specifies the offline and online charging description for the 3GPP interworked wireless LAN (WLAN), based on the functional stage 2 description of 3GPP WLAN interworking in TS 23.234. This charging description includes the offline and online charging architecture and scenarios specific to the 3GPP interworked WLAN, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 onto the 3GPP interworked WLAN. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in TS 32.240.
+- The parameters, abstract syntax and encoding rules for these CDR types are specified in TS 32.298.
+- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in TS 32.297.
+- The 3GPP Diameter application that is used for WLAN offline and online charging is specified in TS 32.299.
+
+All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905. Those that are common across charging management in GSM/UMTS domains or subsystems are provided in the umbrella document TS 32.240 and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 252 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 252 | 7.0.0 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532252v700 |
+| ATIS | ATIS.3GPP.32.252V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.252(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-32.252(R7-7.0.0).zip |
+| TTC | TS-3GA-32.252(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32252rel7v700.pdf |
+
+### **10.10.20 TS 32.260 Telecommunication management; Charging management; IP multimedia subsystem (IMS) charging**
+
+The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks.
+
+The present document specifies the offline and online charging description for the IP multimedia subsystem (IMS), based on the functional descriptions of the IMS in 3G TS 23.228. This charging description includes the offline and online charging architecture and scenarios specific to IMS, as well as the mapping of common 3GPP charging architecture specified in 3G TS 32.240 onto IMS. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in 3G TS 32.240.
+- The parameters, abstract syntax and encoding rules for these CDR types are specified in 3G TS 32.298.
+- A transaction-based mechanism for the transfer of CDRs within the network is specified in 3G TS 32.295.
+- The file-based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in 3G TS 32.297.
+- The 3GPP Diameter application that is used for IMS offline and online charging is specified in 3G TS 32.299.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 260 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 260 | 7.4.0 | Published | 2007-10-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532260v740 |
+| ATIS | ATIS.3GPP.32.260V740-2007 | 7.4.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.260(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.260(R7-7.2.0).zip |
+| TTC | TS-3GA-32.260(Rel7)v7.4.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32260rel7v740.pdf |
+
+### 10.10.21 TS 32.270 Telecommunication management; Charging management; Multimedia messaging service (MMS) charging
+
+The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks.
+
+The complete document structure for these TSs is defined in 3G TS 32.240.
+
+The present document specifies the offline and online charging description for MMS charging, based on the functional Stage 2 descriptions of the MMS in 3G TS 23.140. This charging description includes the offline and online charging architecture and scenarios specific to the MMS, as well as the mapping of the common 3GPP charging architecture specified in 3G TS 32.240 onto MMS. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in 3G TS 32.240.
+- The parameters, abstract syntax and encoding rules for these CDR types are specified in 3G TS 32.298.
+- A transaction-based mechanism for the transfer of CDRs within the network is specified in 3G TS 32.295.
+- The file-based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in 3G TS 32.297.
+- The 3GPP Diameter application that is used for MMS online charging is specified in 3G TS 32.299.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 270 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 270 | 7.1.0 | Published | 2007-10-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532270v710 |
+| ATIS | ATIS.3GPP.32.270V 710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.270(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-32.270(R7-7.1.0).zip |
+| TTC | TS-3GA-32.270(Rel7)v7.1.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32270rel7v710.pdf |
+
+#### 10.10.22 TS 32.271 Telecommunication management; Charging management; Location services (LCS) charging
+
+The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks.
+
+The present document specifies the LCS offline and online charging description for the LCS domain, based on the functional Stage 2 description of the LCS in 3G TS 23.071. This charging description includes the offline and online charging architecture and scenarios specific to the LCS, as well as the mapping of the common 3GPP architecture specified in 3G TS 32.240 onto the LCS domain. It further specifies the structure and content of the CDRs for offline charging and the charging events for online charging.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 271 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 271 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532271v700 |
+| ATIS | ATIS.3GPP.32.271V 700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.271(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-32.271(R7-7.0.0).zip |
+| TTC | TS-3GA-32.271(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32271rel7v700.pdf |
+
+#### 10.10.23 TS 32.272 Telecommunication management; Charging management; Push-to-talk over cellular (PoC) charging
+
+The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in TS 32.240, which provides an umbrella for other charging management TSs that specify:
+
+- the content of the CDRs per domain and subsystem (offline charging);
+
+- the content of real-time charging messages per domain/subsystem (online charging);
+- the functionality of online and offline charging for those domains and subsystems;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in TS 32.240.
+
+The present document specifies the offline and online charging description for the "Push-to-Talk over Cellular" (PoC) service, based on the functional description of the PoC service in TR 23.979 "3GPP enablers for OMA PoC Services", in OMA-AD-POC "Push to talk over Cellular (PoC) – Architecture", in OMA-CP-POC "OMA PoC Control Plane" and in OMA-UP-POC: "OMA POC User Plane", respectively. This charging description includes the offline and online charging architecture and scenarios specific to PoC, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 onto the PoC service. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in TS 32.240.
+- The parameters, abstract syntax and encoding rules for these CDR types are specified in TS 32.298.
+- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in TS 32.297.
+- The 3GPP Diameter application that is used for WLAN offline and online charging is specified in TS 32.299.
+
+All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905. Those that are common across charging management in GSM/UMTS domains or subsystems are provided in the umbrella document TS 32.240 and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 272 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 272 | 7.4.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TS/SGS-0532272v740 |
+| ATIS | ATIS.3GPP.32.272V 740-2007 | 7.4.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.272(R7-7.4.0) | 7.4.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.272(R7-7.4.0).zip |
+| TTC | TS-3GA-32.272(Rel7)v7.4.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32272rel7v740.pdf |
+
+#### **10.10.24 TS 32.273 Telecommunication management; Charging management; Multimedia broadcast and multicast service (MBMS) charging**
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in TS 32.240, which provides an umbrella for other charging management TSs that specify:
+
+- the content of the CDRs per domain and subsystem (offline charging);
+- the content of real-time charging messages per domain/subsystem (online charging);
+- the functionality of online and offline charging for those domains and subsystems;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in TS 32.240.
+
+The present document specifies the offline and online charging description for the multimedia broadcast and multicast service (MBMS), based on the functional stage 2 description in TS 23.246. This charging description includes the offline and online charging architecture and scenarios specific to MBMS, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 onto MBMS. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in TS 32.240.
+- The parameters, abstract syntax and encoding rules for these CDR types are specified in TS 32.298.
+- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in TS 32.297.
+- The 3GPP Diameter application that is used for WLAN offline and online charging is specified in TS 32.299.
+
+All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905. Those that are common across charging management in GSM/UMTS domains or subsystems are provided in the umbrella document TS 32.240 and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 273 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 273 | 7.0.0 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532273v700 |
+| ATIS | ATIS.3GPP.32.273V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.273(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.273(R7-7.0.0).zip |
+| TTC | TS-3GA-32.273(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32273rel7v700.pdf |
+
+### 10.10.25 TS 32.295 Telecommunication management; Charging management; Charging data record (CDR) transfer
+
+The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks.
+
+The present document specifies the transaction-based mechanism for the near real-time transfer of CDRs within the network.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 295 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 295 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532295v700 |
+| ATIS | ATIS.3GPP.32.295V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.295(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.295(R7-7.0.0).zip |
+| TTC | TS-3GA-32.295(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32295rel7v700.pdf |
+
+### 10.10.26 TS 32.296 Telecommunication management; Charging management; Online charging system (OCS): Applications and interfaces
+
+The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks.
+
+The present document covers all internal aspects of the online charging system (OCS). The document contains the architecture and functions of the OCS logical components and thereby derives the functionality of the OCS interfaces. A detailed specification of interfaces between the logical OCS components is also included. The functionality of the OCS, as described in the present document, applies to all charging domains (bearer, session and service).
+
+The interfaces connecting to the OCS (e.g., Ro, CAP) are out of the scope of the present document.
+
+NOTE – In the current release, the present document is limited to the interface between the charging function and the rating function, namely Re.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 296 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 296 | 7.0.0 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532296v700 |
+| ATIS | ATIS.3GPP.32.296V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.296(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.296(R7-7.0.0).zip |
+| TTC | TS-3GA-32.296(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32296rel7v700.pdf |
+
+#### 10.10.27 TS 32.297 Telecommunication management; Charging management; Charging data record (CDR) file format and transfer
+
+The present document is part of a series of documents specifying charging functionality and charging management in GSM/UMTS networks.
+
+The present document specifies the mechanisms used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device). This includes the file transfer procedures and the layout of the CDR files, as well as file meta information and the encoding of the CDRs within the files.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 297 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 297 | 7.0.0 | Published | 2007-10-11 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532297v700 |
+| ATIS | ATIS.3GPP.32.297V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.297(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.297(R7-7.0.0).zip |
+| TTC | TS-3GA-32.297(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32297rel7v700.pdf |
+
+#### 10.10.28 TS 32.298 Telecommunication management; Charging management; Charging data record (CDR) parameter description
+
+The present document is part of a series of documents that specify charging functionality and charging management in GSM and UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in document TS 32.240, which provides an umbrella for other charging management documents that specify:
+
+- the content of the CDRs per domain and subsystem (offline charging);
+
+- the content of real-time charging events per domain/subsystem (online charging);
+- the functionality of online and offline charging for those domains and subsystems;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in TS 32.240.
+
+The present document specifies the CDR parameters, the abstract syntax and encoding rules for all the CDR types that are defined in the charging management TSs described above. Therefore, it is only applicable to offline charging. The mechanisms used to transfer the CDRs from the generating node to the operator's billing domain (e.g., the billing system or a mediation device) are specified in TS 32.297. Further details with respect to the operator's billing domain for offline charging are out of scope of 3GPP standardisation.
+
+Note that a generic Diameter application for online charging in 3GPP networks is specified in TS 32.299. Furthermore, 3GPP TSs are being created to standardize some technical aspects of the operator's billing domain for online charging, i.e., the online charging system (OCS).
+
+All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, [ETSI TR 121 905]. Those that are common across charging management in UMTS domains or subsystems are provided in the umbrella document TS 32.240 and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 298 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 298 | 7.4.0 | Published | 2007-10-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532298v740 |
+| ATIS | ATIS.3GPP.32.298V 740-2007 | 7.4.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.298(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.298(R7-7.2.0).zip |
+| TTC | TS-3GA-32.298(Rel7)v7.4.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32298rel7v740.pdf |
+
+### 10.10.29 TS 32.299 Telecommunication management; Charging management; Diameter charging applications
+
+The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks.
+
+The present document specifies in detail the Diameter-based offline and online charging applications for 3GPP networks. It includes all charging parameters, scenarios and message flows.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 299 | 7.7.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 299 | 7.7.0 | Published | 2007-10-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532299v770 |
+| ATIS | ATIS.3GPP.32.299V770-2007 | 7.7.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.299(R7-7.5.0) | 7.5.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.299(R7-7.5.0).zip |
+| TTC | TS-3GA-32.299(Rel7)v7.7.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32299rel7v770.pdf |
+
+### 10.10.30 TS 32.300 Telecommunication management; Configuration management (CM); Name convention for managed objects
+
+A more detailed background and introduction of the IRP concept is given in TS 32.101 and TS 32.102.
+
+To perform network management tasks, cooperating applications require identical interpretation of names assigned to network resources under management. Such names are required to be unambiguous as well. The document recommends one name convention for network resources under management in the IRP context.
+
+To facilitate integration of network management information obtained via multiple IRPs of different technologies such as CMIP and CORBA, identical network resource name semantics shall be conveyed in all IRPs. The document specifies one such name convention.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 300 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 300 | 7.1.0 | Published | 2007-10-16 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532300v710 |
+| ATIS | ATIS.3GPP.32.300V710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.300(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.300(R7-7.1.0).zip |
+| TTC | TS-3GA-32.300(Rel7)v7.1.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32300rel7v710.pdf |
+
+### 10.10.31 TS 32.301 Telecommunication management; Configuration management; Notification integration reference point (IRP): Requirements
+
+The purpose of notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. This document is the "Requirements" of notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the basic requirements that shall be fulfilled on Itf-N.
+
+How IRPManager discovers the IRPAgent's address or reference (so that IRPManager can invoke an operation) is outside the scope of this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 301 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 301 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532301v700 |
+| ATIS | ATIS.3GPP.32.301V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.301(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.301(R7-7.0.0).zip |
+| TTC | TS-3GA-32.301(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32301rel7v700.pdf |
+
+### **10.10.32 TS 32.302 Telecommunication management; Configuration management; Notification integration reference point; Information service**
+
+The purpose of notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. This document is the "Information Service" of notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information. It also defines the information common to all notifications which is called the "notificationHeader".
+
+An IRPAgent supporting this IRP IS may emit one or multiple categories of notifications, such as alarms (as specified in Alarm IRP: Information service 3G TS 32.111-2) and others. This IRP IS defines a mechanism that IRPManager can use to determine the categories of notifications supported by an IRPAgent. It also defines a mechanism (subscribe and unsubscribe operations) that IRPManager can use to specify the categories of notifications IRPAgent should emit to IRPManager during subscription. It also defines a mechanism (getSubscriptionIds operation) that IRPManager can use to check which categories of notifications it has subscribed to. IRPManager can set and change filter criteria applicable during the life-cycle of a subscription. IRPManager can also exercise flow-control on IRPAgent's emission of notifications (suspendSubscription and resumeSubscription operations).
+
+Using different managerReference, an IRPManager can subscribe several times. It will result in multiple subscriptions. As far as IRPAgent is concerned, notifications are sent to multiple "places".
+
+Using the same managerReference, an IRPManager can subscribe several times specifying different categories of notifications.
+
+This IRP IS does not specify information that is carried in some but not all notifications. That kind of information is specified in other IRP ISs involved. For example, perceivedSeverity is a piece of information specific for notifications carrying alarm information. This information is not defined in this document but in Alarm IRP: Information service 3G TS 32.111-2.
+
+How IRPManager discovers the IRPAgent's address or reference (so that IRPManager can invoke an operation) is outside the scope of this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 302 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 302 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532302v700 |
+| ATIS | ATIS.3GPP.32.302V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.302(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.302(R7-7.0.0).zip |
+| TTC | TS-3GA-32.302(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32302rel7v700.pdf |
+
+### 10.10.33 TS 32.303 Telecommunication management; Configuration management; Notification integration reference point; CORBA solution set
+
+The document specifies the common object request broker architecture (CORBA) solution set (SS) for the IRP whose semantics is specified in notification IRP: Information service 3G TS 32.302.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 303 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 303 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532303v700 |
+| ATIS | ATIS.3GPP.32.303V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.303(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.303(R7-7.0.0).zip |
+| TTC | TS-3GA-32.303(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32303rel7v700.pdf |
+
+### 10.10.34 TS 32.305 Telecommunication management; Configuration management (CM); Notification integration reference point (IRP): eXtensible markup language (XML) definition
+
+This document specifies the XML Definitions for the notification integration reference point (notification IRP) as it applies to Itf-N, in accordance with notification IRP IS definitions.
+
+This XML definitions specification defines the notification IRP XML notification header format.
+
+This specification is related to TS 32.302.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 305 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 305 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532305v700 |
+| ATIS | ATIS.3GPP.32.305V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.305(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.305(R7-7.0.0).zip |
+| TTC | TS-3GA-32.305(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32305rel7v700.pdf |
+
+### 10.10.35 TS 32.307 Telecommunication management; Configuration management (CM); Notification integration reference point (IRP): SOAP solution set
+
+This document specifies the SOAP solution set for the IRP whose semantics is specified in notification IRP: Information service (TS 32.302).
+
+This solution set specification is related to TS 32.302.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 307 | 7.0.2 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 307 | 7.0.2 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532307v702 |
+| ATIS | ATIS.3GPP.32.307V702-2007 | 7.0.2 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.307(R7-7.0.1) | 7.0.1 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.307(R7-7.0.1).zip |
+| TTC | TS-3GA-32.307(Rel7)v7.0.2 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32307rel7v701.pdf |
+
+### 10.10.36 TS 32.311 Telecommunication management; Generic IRP management; Requirements
+
+The purpose of the document is to define a common service supported by all IRPs. This document is the "Requirements" part. It defines, for the purpose of supporting the common service, the requirements that shall be fulfilled by all IRPs supporting this service.
+
+With this common service supported by all IRPs, an IRPManager shall be able to retrieve the profile of operations and notifications supported by a given IRP that are by an IRPAgent. An IRPManager shall also be able to retrieve the different versions supported by an IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 311 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 311 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532311v700 |
+| ATIS | ATIS.3GPP.32.311V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.311(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.311(R7-7.0.0).zip |
+| TTC | TS-3GA-32.311(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32311rel7v700.pdf |
+
+### 10.10.37 TS 32.312 Telecommunication management; Generic IRP management; Information service
+
+The purpose of the document is to define a common service supported by all IRPs. This document is the "Information Service" part. It defines, for the purpose of supporting the common service, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information.
+
+With this common service supported by all IRPs, an IRPManager can retrieve the profile of operations and notifications supported by a given IRP supported by an IRPAgent. An IRPManager can also retrieve the different versions supported by an IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 312 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 312 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532312v700 |
+| ATIS | ATIS.3GPP.32.312V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.312(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.312(R7-7.0.0).zip |
+| TTC | TS-3GA-32.312(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32312rel7v700.pdf |
+
+### 10.10.38 TS 32.313 Telecommunication management; Generic integration reference point (IRP) management; Common object request broker architecture (CORBA) solution set (SS)
+
+The present document specifies the CORBA solution set (SS) for generic integration reference point (IRP) management whose capabilities are specified in "Generic integration reference (IRP) management: Information service (IS)" (3G TS 32.312).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 313 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 313 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532313v700 |
+| ATIS | ATIS.3GPP.32.313V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.313(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.313(R7-7.0.0).zip |
+| TTC | TS-3GA-32.313(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32313rel7v700.pdf |
+
+### 10.10.39 TS 32.317 Telecommunication management; Generic integration reference point (IRP) management; SOAP solution set
+
+The present document specifies the SOAP solution set for generic IRP management whose capabilities are specified in Generic IRP management: Information service (TS 32.312).
+
+This solution set specification is related to TS 32.312.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 317 | 7.0.2 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 317 | 7.0.2 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532317v702 |
+| ATIS | ATIS.3GPP.32.317V702-2007 | 7.0.2 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.317(R7-7.0.2) | 7.0.2 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.317(R7-7.0.2).zip |
+| TTC | TS-3GA-32.317(Rel7)v7.0.2 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32317rel7v701.pdf |
+
+### 10.10.40 TS 32.321 Telecommunication management; Test management integration reference point (IRP); Requirements
+
+This document describes, in addition to the requirements defined in 3G TS 32.101 and 3G TS 32.102, the requirements for the test management IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 321 | 7.0.1 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 321 | 7.0.1 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532321v701 |
+| ATIS | ATIS.3GPP.32.321V701-2007 | 7.0.1 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.321(R7-7.0.1) | 7.0.1 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.321(R7-7.0.1).zip |
+| TTC | TS-3GA-32.321(Rel7)v7.0.1 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32321rel7v701.pdf |
+
+#### 10.10.41 TS 32.322 Telecommunication management; Test management integration reference point (IRP); Information service
+
+This document defines the IS part of the test management IRP, which describes the semantics of the information and the interactions visible across Itf-N in a protocol-independent way. The information is specified by means of information object classes and the interactions by means of operations and notifications. This document does not specify the syntax (encoding) of the information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 322 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 322 | 7.1.0 | Published | 2007-10-16 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532322v710 |
+| ATIS | ATIS.3GPP.32.322V710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.322(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.322(R7-7.1.0).zip |
+| TTC | TS-3GA-32.322(Rel7)v7.1.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32322rel7v710.pdf |
+
+#### 10.10.42 TS 32.323 Telecommunication management; Test management integration reference point (IRP); CORBA solution set
+
+This document specifies the CORBA solution set (SS) for the IRP whose semantics is specified in test management IRP: Information service (IS) (3G TS 32.322).
+
+Clauses 1 to 3 provide background information. Clause 4 provides key architectural features supporting the SS. Clause 5 defines the mapping of operations, notification, parameters and attributes defined in IS to their SS equivalents. Clause 6 describes the notification interface containing the push method. Annex A contains the IDL specification.
+
+This solution set specification is related to 3G TS 32.322.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 323 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 323 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532323v700 |
+| ATIS | ATIS.3GPP.32.323V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.323(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.323(R7-7.0.0).zip |
+| TTC | TS-3GA-32.323(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32323rel7v700.pdf |
+
+#### 10.10.43 TS 32.325 Telecommunication management; Test management integration reference point (IRP); eXtensible markup language (XML) definitions
+
+This document specifies the XML definitions for the test management IRP (TMIRP) as it applies to Itf-N, in accordance with TM IRP IS definitions in TS 32.322 as well as notification log IRP XML definitions in TS 32.335.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 325 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 325 | 7.0.0 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532325v700 |
+| ATIS | ATIS.3GPP.32.325V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.325(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.325(R7-7.0.0).zip |
+| TTC | TS-3GA-32.325(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32325rel7v700.pdf |
+
+#### 10.10.44 TS 32.331 Telecommunication management; Notification log integration reference point (IRP): Requirements
+
+The present document describes the requirements and information model necessary for telecommunications management (TM). The TM principles and TM architecture are specified in 3G TS 32.101 and 3G TS 32.102, respectively.
+
+The present document specifies the overall requirements for notification log management over Itf-N.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 331 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 331 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532331v700 |
+| ATIS | ATIS.3GPP.32.331V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.331(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.331(R7-7.0.0).zip |
+| TTC | TS-3GA-32.331(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32331rel7v700.pdf |
+
+#### 10.10.45 TS 32.332 Telecommunication management; Notification log integration reference point (IRP): Information service (IS)
+
+The present document specifies the information service for the notification log integration reference point (NL IRP) as it applies to Itf-N.
+
+This IRP IS defines the semantics of operations (and their parameters) visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 332 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 332 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532332v700 |
+| ATIS | ATIS.3GPP.32.332V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.332(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.332(R7-7.0.0).zip |
+| TTC | TS-3GA-32.332(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32332rel7v700.pdf |
+
+#### 10.10.46 TS 32.333 Telecommunication management; Notification log (NL) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)
+
+The present document specifies the CORBA solution set for the IRP whose semantics is specified in TS 32.332 notification log IRP: Information service.
+
+Clauses 1 to 3 provide background information. Clause 4 provides key architectural features supporting the SS.
+
+Clause 5 defines the mapping of operations, notification, parameters and attributes defined in IS to their SS equivalents. Clause 6 describes the notification interface containing the push method. Annex A contains the IDL specification.
+
+This solution set specification is related to TS 32.332.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 333 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 333 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532333v700 |
+| ATIS | ATIS.3GPP.32.333V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.333(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.333(R7-7.0.0).zip |
+| TTC | TS-3GA-32.333(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32333rel7v700.pdf |
+
+#### **10.10.47 TS 32.335 Telecommunication management; Notification log (NL) integration reference point (IRP): eXtensible markup language (XML) solution definitions**
+
+The present document specifies the XML definitions for the notification log IRP as it applies to Itf-N, in accordance with the requirements in TS 32.331 and information service definitions in TS 32.332.
+
+This XML definitions specification defines the XML syntax of the NL IRP XML data file.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 335 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 335 | 7.0.0 | Published | 2007-03-30 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532335v700 |
+| ATIS | ATIS.3GPP.32.335V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.335(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.335(R7-7.0.0).zip |
+| TTC | TS-3GA-32.335(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32335rel7v700.pdf |
+
+#### **10.10.48 TS 32.341 Telecommunication management; File transfer (FT) integration reference point (IRP): Requirements**
+
+The present document specifies the overall requirements for the file transfer integration reference point (FT IRP) as it applies to the Itf-N.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 341 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 341 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532341v700 |
+| ATIS | ATIS.3GPP.32.341V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.341(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.341(R7-7.0.0).zip |
+| TTC | TS-3GA-32.341(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32341rel7v700.pdf |
+
+#### **10.10.49 TS 32.342 Telecommunication management; File transfer (FT) integration reference point (IRP): Information service (IS)**
+
+The present document specifies the information service for the file transfer integration reference point (FileTransferIRP) as it applies to the Itf-N.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 342 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 342 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532342v700 |
+| ATIS | ATIS.3GPP.32.342V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.342(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.342(R7-7.0.0).zip |
+| TTC | TS-3GA-32.342(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32342rel7v700.pdf |
+
+#### **10.10.50 TS 32.343 Telecommunication management; File transfer (FT) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The present document specifies the common object request broker architecture (CORBA) solution set (SS) for the IRP whose semantics is specified in file transfer IRP: Information service TS 32.342.
+
+This solution set specification is related to TS 32.342.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 343 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 343 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532343v700 |
+| ATIS | ATIS.3GPP.32.343V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.343(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.343(R7-7.0.0).zip |
+| TTC | TS-3GA-32.343(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32343rel7v700.pdf |
+
+#### **10.10.51 TS 32.345 Telecommunication management; File transfer (FT) integration reference point (IRP); eXtensible markup language (XML) definitions**
+
+The present document specifies the XML definitions for the file transfer IRP (FTIRP) as it applies to Itf-N, in accordance with FT IRP IS definitions in TS 32.342 as well as notification log IRP XML definitions in TS 32.335.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 345 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 345 | 7.0.0 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532345v700 |
+| ATIS | ATIS.3GPP.32.345V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.345(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.345(R7-7.0.0).zip |
+| TTC | TS-3GA-32.345(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32345rel7v700.pdf |
+
+#### **10.10.52 TS 32.351 Telecommunication management; Communication surveillance (CS) integration reference point (IRP): Requirements**
+
+The present document describes the requirements of the communication surveillance IRP (CSIRP).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 351 | 7.0.1 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 351 | 7.0.1 | Published | 2007-07-25 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532351v701 |
+| ATIS | ATIS.3GPP.32.351V701-2007 | 7.0.1 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.351(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-32.351(R7-7.0.0).zip |
+| TTC | TS-3GA-32.351(Rel7)v7.0.1 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32351rel7v701.pdf |
+
+#### **10.10.53 TS 32.352 Telecommunication management; Communication surveillance (CS) integration reference point (IRP): Information service (IS)**
+
+The present document defines the IS part of the CSIRP, which describes the semantics of the information and the interactions visible across Itf-N in a protocol-independent way. The information is specified by means of information object classes and the interactions by means of operations and notifications. The present document does not specify the syntax (encoding) of the information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 352 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 352 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532352v700 |
+| ATIS | ATIS.3GPP.32.352V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.352(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-32.352(R7-7.0.0).zip |
+| TTC | TS-3GA-32.352(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32352rel7v700.pdf |
+
+#### **10.10.54 TS 32.353 Telecommunication management; Communication surveillance (CS) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The present document specifies the CORBA solution set for the IRP whose semantics is specified in 3G TS 32.352 communication surveillance IRP: Information service.
+
+This solution set specification is related to TS 32.352.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 353 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 353 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532353v700 |
+| ATIS | ATIS.3GPP.32.353V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.353(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.353(R7-7.0.0).zip |
+| TTC | TS-3GA-32.353(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32353rel7v700.pdf |
+
+#### **10.10.55 TS 32.361 Telecommunication management; Entry point (EP) integration reference point (IRP): Requirements**
+
+The present document describes the requirements of the EPIRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 361 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 361 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532361v700 |
+| ATIS | ATIS.3GPP.32.361V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.361(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.361(R7-7.0.0).zip |
+| TTC | TS-3GA-32.361(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32361rel7v700.pdf |
+
+#### **10.10.56 TS 32.362 Telecommunication management; Entry point (EP) integration reference point (IRP): Information service (IS)**
+
+The present document defines the IS part of the EPIRP, which describes the semantics of the information and the interactions visible across Itf-N in a protocol independent way. The information is specified by means of information object classes and the interactions by means of operations and notifications. The present document does not specify the syntax (encoding) of the information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 362 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 362 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532362v700 |
+| ATIS | ATIS.3GPP.32.362V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.362(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.362(R7-7.0.0).zip |
+| TTC | TS-3GA-32.362(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32362rel7v700.pdf |
+
+**10.10.57 TS 32.363 Telecommunication management; Entry point (EP) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The present document specifies the CORBA solution set for the IRP whose semantics is specified in the entry point IRP: Information service (3G TS 32.362).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 363 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 363 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532363v700 |
+| ATIS | ATIS.3GPP.32.363V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.363(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.363(R7-7.0.0).zip |
+| TTC | TS-3GA-32.363(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32363rel7v700.pdf |
+
+**10.10.58 TS 32.365 Telecommunication management; Entry point (EP) integration reference point (IRP); eXtensible markup language (XML) definitions**
+
+The present document specifies the XML definitions for the entry point IRP (EPIRP) as it applies to Itf-N, in accordance with EP IRP IS definitions TS 32.362 as well as notification log IRP XML definitions TS 32.335.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 365 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 365 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532365v700 |
+| ATIS | ATIS.3GPP.32.365V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.365(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.365(R7-7.0.0).zip |
+| TTC | TS-3GA-32.365(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32365rel7v700.pdf |
+
+### **10.10.59 TS 32.371 Telecommunication management; Security management concept and requirements**
+
+The present document defines, in addition to the requirements defined in 3G TS 32.101 and 3G TS 32.102, the requirements for security management IRP.
+
+The purpose of the present document is to specify the necessary security features, services and functions to protect the network management data, including Requests, Responses, Notifications and Files, exchanged across the Itf-N.
+
+Telecommunication network security can be breached by weaknesses in operational procedures, physical installations, communication links, computational processes and data storage. Of concern here in the present document is the security problems resulting from the weaknesses inherent in the communication technologies (i.e., the 3GPP-defined interface IRPs and their supporting protocol stacks) deployed across the Itf-N.
+
+An appropriate level of security for a telecommunication network is essential. Secured access to the network management applications, and network management data, is essential. The 3GPP-defined interface IRPs (and their supporting protocol stacks), deployed across the Itf-N, are used for such access, and therefore, their security is considered essential.
+
+Many network management security standards exist. However, there is no recommendation on how to apply them in the Itf-N context. Their deployment across the Itf-N is left to operators. The present document and the corresponding solutions identify and recommend security standards in the Itf-N context.
+
+The business case for secured Itf-N is complex as it does not relate to the functions of the interface IRPs (the functions are constant) but rather, it relates to variants such as the cost of recovering from security breaks, the probability of security incidents and the cost of implementing security management, all of which differ depending on specific deployment scenarios.
+
+The present document describes the security functions for a 3G network in terms of security domains.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 371 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 371 | 7.2.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532371v720 |
+| ATIS | ATIS.3GPP.32.371V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.371(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.371(R7-7.2.0).zip |
+| TTC | TS-3GA-32.371(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32371rel7v720.pdf |
+
+#### 10.10.60 TS 32.272 Telecommunication management; Security services for integration reference points (IRPs): Information service (IS)
+
+The purpose of the present document is to specify the necessary security features, services and functions to protect the network management data, including Requests, Responses, Notifications and Files, exchanged across the Itf-N.
+
+The present document specifies the security service for IRP information service.
+
+This security service for IRP IS defines the semantics of management information visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters.
+
+This information service specification is related to TS 32.371.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 272 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 272 | 7.4.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532272v740 |
+| ATIS | ATIS.3GPP.32.272V740-2007 | 7.4.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.272(R7-7.4.0) | 7.4.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.272(R7-7.4.0).zip |
+| TTC | TS-3GA-32.272(Rel7)v7.4.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32272rel7v740.pdf |
+
+#### 10.10.61 TS 32.273 Telecommunication management; Charging management; Multimedia broadcast and multicast service (MBMS) charging
+
+The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in TS 32.240, which provides an umbrella for other charging management TSs that specify:
+
+- the content of the CDRs per domain/subsystem/service (offline charging);
+
+- the content of real-time charging messages per domain/subsystem/service (online charging);
+- the functionality of online and offline charging for those domains/subsystems/services;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in TS 32.240.
+
+The present document specifies the offline and online charging description for the multimedia broadcast and multicast service (MBMS), based on the functional stage 2 description in TS 23.246. This charging description includes the offline and online charging architecture and scenarios specific to MBMS, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 onto MBMS. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in TS 32.240;
+- The parameters, abstract syntax and encoding rules for the CDRs are specified in TS 32.298;
+- A transaction based mechanism for the transfer of CDRs within the network is specified in TS 32.295;
+- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in TS 32.297;
+- The 3GPP Diameter application that is used for MBMS offline and online charging is specified in TS 32.299.
+
+All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905. Those that are common across charging management in GSM/UMTS domains or subsystems are provided in the umbrella document TS 32.240 and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 273 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 273 | 7.0.0 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532273v700 |
+| ATIS | ATIS.3GPP.32.273V 700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.273(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-32.273(R7-7.0.0).zip |
+| TTC | TS-3GA-32.273(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32273rel7v700.pdf |
+
+### 10.10.62 TS 32.295 Telecommunication management; Charging management; Charging data record (CDR) transfer
+
+The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in TS 32.240, which provides an umbrella for other charging management TSs that specify:
+
+- the content of the CDRs per domain/subsystem/service (offline charging),
+- the content of real-time charging messages per domain/subsystem/service (online charging);
+- the functionality of online and offline charging for those domains/subsystems/services;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in TS 32.240.
+
+The present document specifies the transaction based mechanism for the near real-time transfer of CDRs within the network.
+
+The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in TS 32.240;
+- The parameters, abstract syntax and encoding rules for the CDRs are specified in TS 32.298;
+- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the post-processing system or a mediation device) is specified in TS 32.297.
+
+The 3GPP Diameter application that is used for offline and online charging is specified in TS 32.299.
+
+All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905. Those that are common across charging management in GSM/UMTS domains services, or subsystems are provided in the umbrella document TS 32.240 and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 295 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 295 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532295v700 |
+| ATIS | ATIS.3GPP.32.295V 700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.295(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.295(R7-7.0.0).zip |
+| TTC | TS-3GA-32.295(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32295rel7v700.pdf |
+
+### 10.10.63 TS 32.296 Telecommunication management; Charging management; Online charging system (OCS): Applications and interfaces
+
+The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in TS 32.240, which provides an umbrella for other charging management documents that specify:
+
+- the content of the CDRs per domain and subsystem (offline charging);
+- the content of real-time charging messages per domain/subsystem (online charging);
+- the functionality of online and offline charging for those domains and subsystems;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in TS 32.240.
+
+The present document covers all internal aspects of the online charging system (OCS). The document contains the architecture and functions of the OCS logical components and thereby derives the functionality of the OCS interfaces. A detailed specification of interfaces between the logical OCS components is also included. The functionality of the OCS, as described in the present document, applies to all charging domains (bearer, session and service).
+
+The interfaces connecting to the OCS (e.g., Ro, CAP) are out of the scope of the present document.
+
+NOTE – In the current release, the present document is limited to the interface between the charging function and the rating function, namely Re.
+
+All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in TR 21.905. Those that are common across charging management in GSM/UMTS domains, services, or subsystems are provided in the umbrella document TS 32.240. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 296 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 296 | 7.0.0 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532296v700 |
+| ATIS | ATIS.3GPP.32.296V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.296(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.296(R7-7.0.0).zip |
+| TTC | TS-3GA-32.296(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32296rel7v700.pdf |
+
+### 10.10.64 TS 32.297 Telecommunication management; Charging management; Charging data record (CDR) file format and transfer
+
+The present document is part of a series of documents specifying charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging
+
+architecture and principles are specified in TS 32.240, which provides an umbrella for other charging management documents that specify:
+
+- the content of the CDRs per domain/subsystem/service (offline charging);
+- the content of real-time charging messages per domain/subsystem/service (online charging);
+- the functionality of online and offline charging for those domains/subsystems/services;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in TS 32.240.
+
+The present document specifies the mechanisms used to transfer CDR files from the network to the operator's billing domain (e.g., the billing system or a mediation device). This includes the file transfer procedures and the layout of the CDR files, as well as file meta information and the encoding of the CDRs within the files.
+
+The CDR types that can be transported in these files are specified in the respective "middle tier" charging TSs, i.e., TS 32.25x – TS 32.27x. A definition of the parameters, abstract syntax and encoding rules for these CDR types is specified in TS 32.298.
+
+Note that the present document, dealing with CDRs, is consequently only concerned with offline charging. A definition of the corresponding 3GPP online charging functionality and applications can be found in TS 32.299. Furthermore, TS 32.296 specifies the OCS internal charging applications and interfaces.
+
+All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905. Those that are common across charging management in GSM/UMTS domains, services or subsystems are provided in the umbrella document TS 32.240 and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 297 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 297 | 7.0.0 | Published | 2007-10-11 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532297v700 |
+| ATIS | ATIS.3GPP.32.297V 700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.297(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.297(R7-7.0.0).zip |
+| TTC | TS-3GA-32.297(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32297rel7v700.pdf |
+
+### 10.10.65 TS 32.298 Telecommunication management; Charging management; Charging data record (CDR) parameter description
+
+The present document is part of a series of documents that specify charging functionality and charging management in GSM and UMTS networks. The GSM/UMTS core network charging
+
+architecture and principles are specified in document TS 32.240, which provides an umbrella for other charging management documents that specify:
+
+- the content of the CDRs per domain and subsystem (offline charging);
+- the content of real-time charging events per domain/subsystem (online charging);
+- the functionality of online and offline charging for those domains and subsystems;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in TS 32.240.
+
+The present document specifies the CDR parameters, the abstract syntax and encoding rules for all the CDR types that are defined in the charging management TSs described above. Therefore, it is only applicable to offline charging. The mechanisms used to transfer the CDRs from the generating node to the operator's billing domain (e.g., the billing system or a mediation device) are specified in TS 32.297. Further details with respect to the operator's billing domain for offline charging are out of scope of 3GPP standardization.
+
+Note that a generic Diameter application for online charging in 3GPP networks is specified in TS 32.299. Furthermore, 3GPP TSs are being created to standardize some technical aspects of the operator's billing domain for online charging, i.e., the online charging system (OCS).
+
+All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905. Those that are common across charging management in UMTS domains or subsystems are provided in the umbrella document TS 32.240 and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 298 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 298 | 7.4.0 | Published | 2007-10-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532298v740 |
+| ATIS | ATIS.3GPP.32.298V 740-2007 | 7.4.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.298(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.298(R7-7.2.0).zip |
+| TTC | TS-3GA-32.298(Rel7)v7.4.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32298rel7v740.pdf |
+
+#### 10.10.66 TS 32.299 Telecommunication management; Charging management; Diameter charging applications
+
+The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network-charging architecture and principles are specified in TS 32.240, which provides an umbrella for other charging management documents that specify:
+
+- The content of the CDRs' per domain and subsystem (offline charging);
+- The content of real-time charging messages per domain/subsystem (online charging);
+
+- The functionality of online and offline charging for those domains and subsystems;
+- The interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in TS 32.240.
+
+The present document specifies in detail the Diameter based offline and online charging applications for 3GPP networks. It includes all charging parameters, scenarios and message flows.
+
+All terms, definitions and, abbreviations used in the present document, that are common across 3GPP TSs, are defined in TR 21.905. Those that are common across charging management in GSM/UMTS domains, services or subsystems are provided in the umbrella document TS 32.240 and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 299 | 7.7.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 299 | 7.7.0 | Published | 2007-10-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532299v770 |
+| ATIS | ATIS.3GPP.32.299V 770-2007 | 7.7.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.299(R7-7.5.0) | 7.5.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.299(R7-7.5.0).zip |
+| TTC | TS-3GA-32.299(Rel7)v7.7.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32299rel7v770.pdf |
+
+### **10.10.67 TS 32.300 Telecommunication management; Configuration management (CM); Name convention for managed objects**
+
+A detailed background and introduction of the IRP concept is given in TS 32.101 and TS 32.102.
+
+To perform network management tasks, co-operating applications require identical interpretation of names assigned to network resources under management. Such names are required to be unambiguous as well. The present document recommends one name convention for network resources under management in the IRP context.
+
+To facilitate integration of network management information obtained via multiple IRPs based on different IRP solution set technologies, identical network resource name semantics shall be conveyed in all IRPs. The present document specifies one such name convention.
+
+This document also specifies an IOC/MOC name recommendation (see Annex E) in order to avoid potential problems with valid characters in some programming languages.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 300 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 300 | 7.1.0 | Published | 2007-10-16 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532300v710 |
+| ATIS | ATIS.3GPP.32.300V710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.300(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-32.300(R7-7.1.0).zip |
+| TTC | TS-3GA-32.300(Rel7)v7.1.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32300rel7v710.pdf |
+
+#### **10.10.68 TS 32.301 Telecommunication management; Configuration management (CM); Notification integration reference point (IRP): Requirements**
+
+The purpose of notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. The present document is the "Requirements" of notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the basic requirements that shall be fulfilled on Itf-N.
+
+How IRPManager discovers the IRPAgent's address or reference (so that IRPManager can invoke an operation) is outside the scope of the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 301 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 301 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532301v700 |
+| ATIS | ATIS.3GPP.32.301V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.301(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-32.301(R7-7.0.0).zip |
+| TTC | TS-3GA-32.301(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32301rel7v700.pdf |
+
+#### **10.10.69 TS 32.302 Telecommunication management; Configuration management (CM); Notification integration reference point (IRP): Information service (IS)**
+
+The purpose of notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. The present document is the "information service" of notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information. It also defines the information common to all notifications which is called the notificationHeader.
+
+An IRP Agent supporting this IRP IS may emit one or multiple categories of notifications, such as alarms (as specified in alarm IRP: Information Service in TS 32.111-2) and others. This IRP IS defines a mechanism that IRP Manager can use to determine the categories of notifications supported by an IRP Agent. It also defines a mechanism (subscribe and unsubscribe operations) that IRP Manager can use to specify the categories of notifications IRP Agent should emit to IRP Manager during subscription. It also defines a mechanism (getSubscriptionIds operation) that IRP Manager can use to check which categories of notifications it has subscribed to. IRP Manager can set and change filter criteria applicable during the life-cycle of a subscription. IRP Manager can also exercise flow-control on IRP Agent's emission of notifications (suspendSubscription and resumeSubscription operations).
+
+Using different managerReference, an IRP Manager can subscribe several times. It will result in multiple subscriptions. As far as IRP Agent is concerned, notifications are sent to multiple "places".
+
+Using the same managerReference, an IRP Manager can subscribe several times specifying different categories of notifications.
+
+This IRP IS does not specify information that is carried in some but not all notifications. That kind of information is specified in other IRP ISs involved. For example, perceivedSeverity is a piece of information specific for notifications carrying alarm information. This information is not defined in the present document but in alarm IRP: Information service in TS 32.111-2.
+
+How IRP Manager discovers the IRP Agent's address or reference (so that IRP Manager can invoke an operation) is outside the scope of the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 302 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 302 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532302v700 |
+| ATIS | ATIS.3GPP.32.302V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.302(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.302(R7-7.0.0).zip |
+| TTC | TS-3GA-32.302(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32302rel7v700.pdf |
+
+#### **10.10.70 TS 32.303 Telecommunication management; Configuration management (CM); Notification integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The present document specifies the common object request broker architecture (CORBA) solution set (SS) for the IRP whose semantics is specified in notification IRP: Information service (TS 32.302).
+
+This solution set specification is related to 3GPP TS 32.302.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 303 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 303 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532303v700 |
+| ATIS | ATIS.3GPP.32.303V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.303(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-32.303(R7-7.0.0).zip |
+| TTC | TS-3GA-32.303(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32303rel7v700.pdf |
+
+**10.10.71 TS 32.305 Telecommunication management; Configuration management (CM); Notification integration reference point (IRP): eXtensible markup language (XML) definition**
+
+The present document specifies the XML definitions for the notification integration reference point (notification IRP) as it applies to Itf-N, in accordance with notification IRP IS definitions in TS 32.331.
+
+This XML definitions specification defines the notification IRP XML notification header format.
+
+This specification is related to TS 32.302.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 305 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 305 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532305v700 |
+| ATIS | ATIS.3GPP.32.305V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.305(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-32.305(R7-7.0.0).zip |
+| TTC | TS-3GA-32.305(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32305rel7v700.pdf |
+
+**10.10.72 TS 32.307 Telecommunication management; Configuration management (CM); Notification integration reference point (IRP): SOAP solution set (SS)**
+
+The present document specifies the SOAP solution set for the IRP whose semantics is specified in notification IRP: Information service (TS 32.302).
+
+This solution set specification is related to 3GPP TS 32.302.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 307 | 7.0.2 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 307 | 7.0.2 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532307v702 |
+| ATIS | ATIS.3GPP.32.307V702-2007 | 7.0.2 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.307(R7-7.0.1) | 7.0.1 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.307(R7-7.0.1).zip |
+| TTC | TS-3GA-32.307(Rel7)v7.0.2 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32307rel7v701.pdf |
+
+### 10.10.73 TS 32.311 Telecommunication management; Generic integration reference point (IRP) management; Requirements
+
+The purpose of the present document is to define a common service supported by all IRPs such as AlarmIRP. The present document is the "Requirements" part. It defines the requirements that shall be fulfilled by all IRPs, such as AlarmIRP, supporting this common service.
+
+With this common service supported by all IRPs, an IRPManager shall be able to retrieve the profile of operations and notifications supported by a given IRP which is name-contained by an IRPAgent. An IRPManager shall also be able to retrieve the IRPVersions supported by the given IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 311 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 311 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532311v700 |
+| ATIS | ATIS.3GPP.32.311V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.311(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.311(R7-7.0.0).zip |
+| TTC | TS-3GA-32.311(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32311rel7v700.pdf |
+
+### 10.10.74 TS 32.312 Telecommunication management; Generic integration reference point (IRP) management; Information service (IS)
+
+The purpose of the present document is to define a common service supported by all IRPs such as AlarmIRP. The present document is the "Information Service" part. It defines, for the purpose of supporting the common service, the information observable and controllable by management system's client (i.e., IRPManager) via the Itf-N.
+
+It also specifies the semantics of and the interactions used to carry this information.
+
+With this common service supported by all IRPs, an IRPManager can retrieve the profile of operations and notifications supported by a given IRP name-contained by an IRPAgent. An IRPManager can also retrieve the IRPVersions supported by a given IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 312 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 312 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532312v700 |
+| ATIS | ATIS.3GPP.32.312V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.312(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.312(R7-7.0.0).zip |
+| TTC | TS-3GA-32.312(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32312rel7v700.pdf |
+
+#### **10.10.75 TS 32.313 Telecommunication management; Generic integration reference point (IRP) management; Common object request broker architecture (CORBA) solution set (SS)**
+
+The present document specifies the CORBA solution set for generic integration reference point (IRP) management whose capabilities are specified in TS 32.312, the generic IRP management: information service.
+
+This solution set specification is related to TS 32.312.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 313 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 313 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532313v700 |
+| ATIS | ATIS.3GPP.32.313V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.313(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.313(R7-7.0.0).zip |
+| TTC | TS-3GA-32.313(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32313rel7v700.pdf |
+
+#### **10.10.76 TS 32.317 Telecommunication management; Generic integration reference point (IRP) management; SOAP solution set (SS)**
+
+The present document specifies the SOAP solution set for generic IRP management whose capabilities are specified in generic IRP management: Information service (TS 32.312).
+
+This solution set specification is related to TS 32.312.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 317 | 7.0.2 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 317 | 7.0.2 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532317v702 |
+| ATIS | ATIS.3GPP.32.317V702-2007 | 7.0.2 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.317(R7-7.0.2) | 7.0.2 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.317(R7-7.0.2).zip |
+| TTC | TS-3GA-32.317(Rel7)v7.0.2 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32317rel7v701.pdf |
+
+#### **10.10.77 TS 32.321 Telecommunication management; Test management integration reference point (IRP): Requirements**
+
+The present document describes, in addition to the requirements defined in TS 32.101 and TS 32.102, the requirements for the test management IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 321 | 7.0.1 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 321 | 7.0.1 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532321v701 |
+| ATIS | ATIS.3GPP.32.321V701-2007 | 7.0.1 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.321(R7-7.0.1) | 7.0.1 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.321(R7-7.0.1).zip |
+| TTC | TS-3GA-32.321(Rel7)v7.0.1 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32321rel7v701.pdf |
+
+#### **10.10.78 TS 32.322 Telecommunication management; Test management integration reference point (IRP): Information service (IS)**
+
+The present document defines the IS part of the test management IRP, which describes the semantics of the information and the interactions visible across Itf-N in a protocol independent way. The information is specified by means of information object classes and the interactions by means of operations and notifications. The present document does not specify the syntax (encoding) of the information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 322 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 322 | 7.1.0 | Published | 2007-10-16 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532322v710 |
+| ATIS | ATIS.3GPP.32.322V710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.322(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.322(R7-7.1.0).zip |
+| TTC | TS-3GA-32.322(Rel7)v7.1.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32322rel7v710.pdf |
+
+**10.10.79 TS 32.323 Telecommunication management; Test management integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The present document specifies the CORBA SS for the IRP whose semantics is specified in test management IRP IS (TS 32.322).
+
+Clauses 1 to 3 provide background information. Clause 4 provides key architectural features supporting the SS. Clause 5 defines the mapping of operations, notification, parameters and attributes defined in IS to their SS equivalents. Clause 6 describes the notification interface containing the push method. Annex A contains the IDL specification.
+
+This solution set specification is related to 3GPP TS 32.322.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 323 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 323 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532323v700 |
+| ATIS | ATIS.3GPP.32.323V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.323(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.323(R7-7.0.0).zip |
+| TTC | TS-3GA-32.323(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32323rel7v700.pdf |
+
+**10.10.80 TS 32.325 Telecommunication management; Test management integration reference point (IRP); eXtensible markup language (XML) definitions**
+
+The present document specifies the XML definitions for the test management IRP (TMRP) as it applies to Itf-N, in accordance with TM IRP IS definitions TS 32.322 as well as notification log IRP XML definitions TS 32.335.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 325 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 325 | 7.0.0 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532325v700 |
+| ATIS | ATIS.3GPP.32.325V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.325(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.325(R7-7.0.0).zip |
+| TTC | TS-3GA-32.325(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32325rel7v700.pdf |
+
+#### **10.10.81 TS 32.331 Telecommunication management; Notification log (NL) integration reference point (IRP): Requirements**
+
+The present document specifies the overall requirements for notification log management over Itf-N.
+
+Clause 4 provides the notification log management concept for the manipulation of notification logs and the retrieval of notifications selected for logging.
+
+Clause 5 of the present document defines the functional requirements for the notification log IRP, for the purpose of notification log management, as seen from a network manager (NM) through Itf-N. The Itf-N is fully standardized so as to connect systems of any vendor to an NM via this interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 331 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 331 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532331v700 |
+| ATIS | ATIS.3GPP.32.331V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.331(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.331(R7-7.0.0).zip |
+| TTC | TS-3GA-32.331(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32331rel7v700.pdf |
+
+#### **10.10.82 TS 32.332 Telecommunication management; Notification log (NL) integration reference point (IRP): Information service (IS)**
+
+The present document specifies the information service for the notification log integration reference point (NLIRP) as it applies to Itf-N.
+
+This IRP IS defines the semantics of operations (and their parameters) visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 332 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 332 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532332v700 |
+| ATIS | ATIS.3GPP.32.332V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.332(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-32.332(R7-7.0.0).zip |
+| TTC | TS-3GA-32.332(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32332rel7v700.pdf |
+
+#### **10.10.83 TS 32.333 Telecommunication management; Notification log (NL) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The present document specifies the CORBA solution set for the IRP whose semantics is specified in TS 32.332 notification log IRP: Information service.
+
+Clauses 1 to 3 provide background information. Clause 4 provides key architectural features supporting the SS.
+
+Clause 5 defines the mapping of operations, notification, parameters and attributes defined in IS to their SS equivalents. Clause 6 describes the notification interface containing the push method. Annex A contains the IDL specification.
+
+This solution set specification is related to TS 32.332.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 333 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 333 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532333v700 |
+| ATIS | ATIS.3GPP.32.333V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.333(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-32.333(R7-7.0.0).zip |
+| TTC | TS-3GA-32.333(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32333rel7v700.pdf |
+
+#### **10.10.84 TS 32.335 Telecommunication management; Notification log (NL) integration reference point (IRP): eXtensible markup language (XML) solution definitions**
+
+The present document specifies the XML definitions for the notification log IRP as it applies to Itf-N, in accordance with the requirements in TS 32.331 and information service definitions in TS 32.332.
+
+This XML definitions specification defines the XML syntax of the NL IRP XML data file.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 335 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 335 | 7.0.0 | Published | 2007-03-30 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532335v700 |
+| ATIS | ATIS.3GPP.32.335V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.335(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.335(R7-7.0.0).zip |
+| TTC | TS-3GA-32.335(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32335rel7v700.pdf |
+
+#### **10.10.85 TS 32.341 Telecommunication management; File transfer (FT) integration reference point (IRP): Requirements**
+
+The present document specifies the overall requirements for the file transfer integration reference point (FT IRP) as it applies to the Itf-N.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 341 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 341 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532341v700 |
+| ATIS | ATIS.3GPP.32.341V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.341(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.341(R7-7.0.0).zip |
+| TTC | TS-3GA-32.341(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32341rel7v700.pdf |
+
+#### **10.10.86 TS 32.342 Telecommunication management; File transfer (FT) integration reference point (IRP): Information service (IS)**
+
+The present document specifies the information service for the file transfer integration reference point (FileTransferIRP) as it applies to the Itf-N.
+
+The present document defines the semantics of operations (and their parameters) visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 342 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 342 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532342v700 |
+| ATIS | ATIS.3GPP.32.342V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.342(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.342(R7-7.0.0).zip |
+| TTC | TS-3GA-32.342(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32342rel7v700.pdf |
+
+**10.10.87 TS 32.343 Telecommunication management; File transfer (FT) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The present document specifies the common object request broker architecture (CORBA) solution set (SS) for the IRP whose semantics is specified in the file transfer IRP: Information service TS 32.342.
+
+This solution set specification is related to TS 32.342.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 343 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 343 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532343v700 |
+| ATIS | ATIS.3GPP.32.343V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.343(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.343(R7-7.0.0).zip |
+| TTC | TS-3GA-32.343(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32343rel7v700.pdf |
+
+**10.10.88 TS 32.345 Telecommunication management; File transfer (FT) integration reference point (IRP); eXtensible markup language (XML) definitions**
+
+The present document specifies the XML definitions for the file transfer IRP (FTIRP) as it applies to Itf-N, in accordance with FT IRP IS definitions TS 32.342, as well as notification log IRP XML definitions TS 32.335.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 345 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 345 | 7.0.0 | Published | 2007-07-19 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532345v700 |
+| ATIS | ATIS.3GPP.32.345V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.345(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.345(R7-7.0.0).zip |
+| TTC | TS-3GA-32.345(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32345rel7v700.pdf |
+
+#### **10.10.89 TS 32.351 Telecommunication management; Communication surveillance (CS) integration reference point (IRP): Requirements**
+
+The present document describes the requirements of the communication surveillance IRP (CSIRP).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 351 | 7.0.1 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 351 | 7.0.1 | Published | 2007-07-25 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532351v701 |
+| ATIS | ATIS.3GPP.32.351V701-2007 | 7.0.1 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.351(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.351(R7-7.0.0).zip |
+| TTC | TS-3GA-32.351(Rel7)v7.0.1 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32351rel7v701.pdf |
+
+#### **10.10.90 TS 32.352 Telecommunication management; Communication surveillance (CS) integration reference point (IRP): Information service (IS)**
+
+The present document defines the information service (IS) part of the communication surveillance IRP (CSIRP).
+
+It describes the semantics of the information and the interactions visible across Itf-N in a protocol independent way.
+
+The information is specified by means of information object classes (IOCs) and the interactions by means of operations and notifications. The present document does not specify the syntax (encoding) of the information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 352 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 352 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532352v700 |
+| ATIS | ATIS.3GPP.32.352V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.352(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.352(R7-7.0.0).zip |
+| TTC | TS-3GA-32.352(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32352rel7v700.pdf |
+
+**10.10.91 TS 32.353 Telecommunication management; Communication surveillance (CS) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The present document specifies the CORBA solution set for the IRP whose semantics is specified in TS 32.352 communication surveillance IRP: Information service.
+
+This solution set specification is related to TS 32.352.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 353 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 353 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532353v700 |
+| ATIS | ATIS.3GPP.32.353V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.353(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.353(R7-7.0.0).zip |
+| TTC | TS-3GA-32.353(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32353rel7v700.pdf |
+
+**10.10.92 TS 32.361 Telecommunication management; Entry point (EP) integration reference point (IRP): Requirements**
+
+The present document describes the requirements of the EPIRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 361 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 361 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532361v700 |
+| ATIS | ATIS.3GPP.32.361V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.361(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-32.361(R7-7.0.0).zip |
+| TTC | TS-3GA-32.361(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32361rel7v700.pdf |
+
+#### **10.10.93 TS 32.362 Telecommunication management; Entry point (EP) integration reference point (IRP): Information service (IS)**
+
+The present document defines the information service (IS) part of the entry point IRP (EPIRP). It describes the semantics of the information and the interactions visible across Itf-N in a protocol independent way.
+
+The information is specified by means of information object classes (IOCs) and the interactions by means of operations and notifications. The present document does not specify the syntax (encoding) of the information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 362 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 362 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532362v700 |
+| ATIS | ATIS.3GPP.32.362V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.362(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-32.362(R7-7.0.0).zip |
+| TTC | TS-3GA-32.362(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32362rel7v700.pdf |
+
+#### **10.10.94 TS 32.363 Telecommunication management; Entry point (EP) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The present document specifies the CORBA solution set for the IRP whose semantics is specified in the entry point IRP: Information service (TS 32.362).
+
+This solution set specification is related to TS 32.362.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 363 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 363 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532363v700 |
+| ATIS | ATIS.3GPP.32.363V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.363(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.363(R7-7.0.0).zip |
+| TTC | TS-3GA-32.363(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32363rel7v700.pdf |
+
+#### **10.10.95 TS 32.365 Telecommunication management; Entry point (EP) integration reference point (IRP); eXtensible markup language (XML) definitions**
+
+The present document specifies the XML definitions for the entry point IRP (EPIRP) as it applies to Itf-N, in accordance with EP IRP IS definitions TS 32.362, as well as the notification log IRP XML definitions TS 32.335.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 365 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 365 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532365v700 |
+| ATIS | ATIS.3GPP.32.365V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.365(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.365(R7-7.0.0).zip |
+| TTC | TS-3GA-32.365(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32365rel7v700.pdf |
+
+#### **10.10.96 TS 32.371 Telecommunication management; Security management concept and requirements**
+
+The present document defines, in addition to the requirements defined in TS 32.101 and TS 32.102, the requirements for security management IRP.
+
+The purpose of the present document is to specify the necessary security features, services and functions to protect the network management data, including Requests, Responses, Notifications and Files, exchanged across the Itf-N.
+
+Telecommunication network security can be breached by weaknesses in operational procedures, physical installations, communication links, computational processes and data storage. Of concern here in the present document is the security problems resulting from the weaknesses inherent in the communication technologies (i.e., the 3GPP-defined interface IRPs and their supporting protocol stacks) deployed across the Itf-N.
+
+An appropriate level of security for a telecommunication network is essential. Secured access to the network management applications, and network management data, is essential. The 3GPP-defined interface IRPs (and their supporting protocol stacks), deployed across the Itf-N, are used for such access, and therefore, their security is considered essential.
+
+Many network management security standards exist. However, there is no recommendation on how to apply them in the Itf-N context. Their deployment across the Itf-N is left to operators. The present document and the corresponding solutions identify and recommend security standards in the Itf-N context.
+
+The business case for secured Itf-N is complex as it does not relate to the functions of the interface IRPs (the functions are constant) but rather, it relates to variants such as the cost of recovering from security breaks, the probability of security incidents and the cost of implementing security management, all of which differ depending on specific deployment scenarios.
+
+The present document describes the security functions for a 3G network in terms of security domains (subclause 4.1). Clause 5 defines the Itf-N security management scope in terms of its context (subclause 5.1) and the possible threats that can occur there are defined in clause 6. Clause 7 specifies the Itf-N security requirements.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 371 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 371 | 7.2.0 | Published | 2007-07-18 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532371v720 |
+| ATIS | ATIS.3GPP.32.371V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.371(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.371(R7-7.2.0).zip |
+| TTC | TS-3GA-32.371(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32371rel7v720.pdf |
+
+#### **10.10.97 TS 32.372 Telecommunication management; Security services for integration reference point (IRP): Information service (IS)**
+
+The purpose of the present document is to specify the necessary security features, services and functions to protect the network management data, including Requests, Responses, Notifications and Files, exchanged across the Itf-N.
+
+The present document specifies the security service for IRP information service.
+
+This security service for IRP IS defines the semantics of management information visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters.
+
+This information service specification is related to 3GPP TS 32.371.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 372 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 372 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532372v700 |
+| ATIS | ATIS.3GPP.32.372V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.372(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.372(R7-7.0.0).zip |
+| TTC | TS-3GA-32.372(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32372rel7v700.pdf |
+
+#### **10.10.98 TS 32.373 Telecommunication management; Security service for integration reference point (IRP): Common object request broker architecture (CORBA)**
+
+The present document specifies the CORBA solution for the IRP whose semantics is specified in TS 32.372 security service for IRP information service.
+
+This solution set specification is related to TS 32.372.
+
+Note that within the present document, there are several alternate solutions. Specific choices will be made to counter identified security threats, and to consider performance and cost criteria, i.e., an implementation is not expected to have to support every option for every deployment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 373 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 373 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532373v700 |
+| ATIS | ATIS.3GPP.32.373V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.373(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.373(R7-7.0.0).zip |
+| TTC | TS-3GA-32.373(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32373rel7v700.pdf |
+
+#### **10.10.99 TS 32.375 Telecommunication management; Security services for integration reference point (IRP): File integrity solution**
+
+The present document contains the security services for IRP: File integrity solution whose semantics is specified in TS 32.372.
+
+This solution specification is related to TS 32.372.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 375 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 375 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532375v700 |
+| ATIS | ATIS.3GPP.32.375V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.375(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.375(R7-7.0.0).zip |
+| TTC | TS-3GA-32.375(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32375rel7v700.pdf |
+
+### **10.10.100 TS 32.381 Telecommunication management; Partial suspension of Itf-N integration reference point (IRP): Requirements**
+
+The purpose of partial suspension of Itf-N IRP is to define an interface through which an IRPManager can suspend the forwarding of notifications via Itf-N which were generated in parts of the managed systems.
+
+The present document contains the requirements of partial suspension of Itf-N IRP. It defines, for the purpose of generally suspending the forwarding of notifications, the basic requirements to be fulfilled on Itf-N.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 381 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 381 | 7.0.0 | Published | 2007-04-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532381v700 |
+| ATIS | ATIS.3GPP.32.381V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.381(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.381(R7-7.0.0).zip |
+| TTC | TS-3GA-32.381(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32381rel7v700.pdf |
+
+### **10.10.101 TS 32.382 Telecommunication management; Partial suspension of Itf-N integration reference point (IRP): Information service (IS)**
+
+The purpose of partial suspension of Itf-N IRP is to define an interface through which an IRPManager can suspend the forwarding of notifications via Itf-N which were generated in parts of the managed systems.
+
+The present document is the information service of partial suspension of Itf-N IRP. It defines, for the purpose of suspending generally the forwarding of notifications, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 382 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 382 | 7.0.0 | Published | 2007-04-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532382v700 |
+| ATIS | ATIS.3GPP.32.382V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.382(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.382(R7-7.0.0).zip |
+| TTC | TS-3GA-32.382(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32382rel7v700.pdf |
+
+### **10.10.102 TS 32.383 Telecommunication management; Partial suspension of Itf-N integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The purpose of partial suspension of Itf-N IRP is to define an interface through which an IRPManager can suspend the forwarding of notifications via Itf-N which were generated in parts of the managed systems.
+
+The present document is the "CORBA Solution Set" of partial suspension of Itf-N IRP for the IRP whose semantics is specified in partial suspension of Itf-N IRP: Information service (TS 32.382).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 383 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 383 | 7.0.0 | Published | 2007-04-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532383v700 |
+| ATIS | ATIS.3GPP.32.383V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.383(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.383(R7-7.0.0).zip |
+| TTC | TS-3GA-32.383(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32383rel7v700.pdf |
+
+### **10.10.103 TS 32.385 Telecommunication management; Partial suspension of Itf-N integration reference point (IRP): eXtensible markup language (XML) file format definition**
+
+The purpose of partial suspension of Itf-N IRP is to define an interface through which an IRPManager can suspend the forwarding of notifications via Itf-N which were generated in parts of the managed systems.
+
+The present document is the eXtensible markup language (XML) file format definition of partial suspension of Itf-N IRP for the IRP whose semantics is specified in partial suspension of Itf-N IRP: Information service (TS 32.382).
+
+This XML definitions specification defines the XML syntax of the partial suspension of Itf-N IRP. This XML definitions specification is related to TS 32.382.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 385 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 385 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532385v700 |
+| ATIS | ATIS.3GPP.32.385V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.385(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.385(R7-7.0.0).zip |
+| TTC | TS-3GA-32.385(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32385rel7v700.pdf |
+
+#### 10.10.104 TS 32.391 Telecommunication management; Delta synchronization integration reference point (IRP): Requirements
+
+The purpose of delta synchronization IRP is to define an interface through which an IRPManager can request only those data which changed (i.e., changed, were created or deleted) from a synchronization point onwards.
+
+The present document contains the requirements of delta synchronization IRP. It defines, for the purpose of delta synchronization, the basic requirements to be fulfilled on Itf-N.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 391 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 391 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532391v700 |
+| ATIS | ATIS.3GPP.32.391V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.391(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.391(R7-7.0.0).zip |
+| TTC | TS-3GA-32.391(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32391rel7v700.pdf |
+
+#### 10.10.105 TS 32.392 Telecommunication management; Delta synchronization integration reference point (IRP): Information service (IS)
+
+The purpose of delta synchronization IRP is to define an interface through which an IRPManager can request only those data which changed (i.e., changed, were created or deleted) from a synchronization point onwards.
+
+The present document is the information service of delta synchronization IRP. It defines, for the purpose of delta synchronization, the information observable and controlled by management system's client, and it also specifies the semantics of the interactions used to carry this information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 392 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 392 | 7.2.0 | Published | 2007-10-16 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532392v720 |
+| ATIS | ATIS.3GPP.32.392V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.392(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.392(R7-7.1.0).zip |
+| TTC | TS-3GA-32.392(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32392rel7v720.pdf |
+
+**10.10.106 TS 32.393 Telecommunication management; Delta synchronization integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The purpose of delta synchronization IRP is to define an interface through which an IRPManager can request only those data which changed (i.e., changed, were created or deleted) from a synchronization point onwards.
+
+The present document is the "CORBA Solution Set" of delta synchronization IRP for the IRP whose semantics is specified in delta synchronization IRP: Information service (TS 32.392).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 393 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 393 | 7.1.0 | Published | 2007-10-16 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532393v710 |
+| ATIS | ATIS.3GPP.32.393V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.393(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.393(R7-7.0.0).zip |
+| TTC | TS-3GA-32.393(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32393rel7v710.pdf |
+
+**10.10.107 TS 32.395 Telecommunication management; Delta synchronization integration reference point (IRP): eXtensible markup language (XML) file format definition**
+
+The purpose of delta synchronization IRP is to define an interface through which an IRPManager can request only those data which changed (i.e., changed, were created or deleted) from a synchronization point onwards.
+
+The present document is the eXtensible markup language (XML) file format definition of delta synchronization IRP for the IRP whose semantics is specified in delta synchronization IRP: Information service (TS 32.392).
+
+This XML definitions specification defines the XML syntax of the delta synchronization IRP XML data file.
+
+This XML definitions specification is related to 3GPP TS 32.392.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 395 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 395 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532395v700 |
+| ATIS | ATIS.3GPP.32.395V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.395(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.395(R7-7.0.0).zip |
+| TTC | TS-3GA-32.395(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32395rel7v700.pdf |
+
+### 10.10.108 TS 32.401 Telecommunication management; Performance management (PM); Concept and requirements
+
+The present document describes the requirements for the management of performance measurements and the collection of performance measurement result data across GSM and UMTS networks. It defines the administration of measurement schedules by the network element manager (EM), the generation of measurement results in the network elements (NEs) and the transfer of these results to one or more operations systems, i.e., EM(s) and/or network manager(s) (NM(s)).
+
+The basic performance management concept that the present document is built upon is described in clause 4. The requirements of how an EM administers the performance measurements and how the results can be collected are defined in detail in clause 5. Measurements available for collection by NEs are described in the following specifications:
+
+- TS 52.402 for GSM systems;
+- TS 32.405, TS 32.406, TS 32.407 and TS 32.408 for UMTS and combined UMTS/GSM systems;
+- TS 32.409 for IMS networks.
+
+Effort has been made to ensure consistency in the definition of measurements between different NEs and generations. The performance measurement result is described in performance measurement file format definition (TS 32.432).
+
+The following is beyond the scope of the present document, and therefore the present document does not describe:
+
+- the formal definition of the interface that the EM uses to administer performance measurements in the NEs;
+- the formal definition of the interface that the EM uses to collect measurement results from the NEs;
+
+- how the data, once accumulated and collected, could or should be processed, stored, or presented to an end user;
+- the information which may be obtained through the collection and processing of call or event-related records which have been produced by the NEs primarily for the purpose of raising bills and other charges.
+
+The management requirements have been derived from existing telecommunications operations experience. The management definitions were then derived from other standardization work so as to minimise the re-invention factor. References are given as appropriate.
+
+The objectives of this standardization are:
+
+- to provide the descriptions for a standard set of measurements;
+- to produce a common description of the management technique for measurement administration and result accumulation; and
+- to define a method for the bulk transmission of measurement results across a management interface.
+
+The definition of the standard measurements is intended to result in comparability of measurement result data produced in a multi-vendor wireless network, for those measurement types that can be standardized across all vendors' implementations.
+
+As far as possible, existing standardization in the area of performance management has been re-used and enhanced where particular requirements, peculiar to the mobile telephony environment, have been recognized.
+
+The present document considers all the above aspects of performance management for a GSM and UMTS network and its NEs defined in the core Technical Specifications. However, only those aspects which are specific to a GSM/UMTS system and particular to wireless network operation are included in the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 401 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 401 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532401v700 |
+| ATIS | ATIS.3GPP.32.401V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.401(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.401(R7-7.0.0).zip |
+| TTC | TS-3GA-32.401(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32401rel7v700.pdf |
+
+### **10.10.109 TS 32.404 Telecommunication management; Performance management (PM); Performance measurements – Definitions and template**
+
+This document describes the measurements for UMTS and combined UMTS/GSM.
+
+TS 32.401 describes performance management concepts and requirements.
+
+The present document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network.
+
+Only measurement types that are specific to UMTS or combined UMTS/GSM networks are defined within the present documents. Vendor-specific measurement types used in UMTS and combined UMTS/GSM networks are not covered. Instead, these could be applied according to the manufacturer's documentation.
+
+Measurements related to "external" technologies (such as ATM or IP), as described by "external" standards bodies (e.g., ITU-T or IETF), shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
+
+The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardized across all vendors' implementations.
+
+TS 32.411; Telecommunication management; performance management (PM) integration reference point (IRP): Requirements
+
+The present document specifies the overall requirements for the performance management integration reference point (PMIRP) as it applies to the network elements (NE), element manager (EM) and network manager (NM).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 404 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/technical/les.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 404 | 7.4.0 | Published | 2007-10-16 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532404v740 |
+| ATIS | ATIS.3GPP.32.404V740-2007 | 7.4.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| ETSI | TTAT.3G-32.404(R7-7.3.0) | 7.3.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.404(R7-7.3.0).zip |
+| TTA | TS-3GA-32.404(Rel7)v7.4.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32404rel7v740.pdf |
+
+#### **10.10.110 TS 32.405 Telecommunication management; Performance management (PM); Performance measurements universal terrestrial radio access network (UTRAN)**
+
+The present document describes the measurements for UMTS and combined UMTS/GSM. TS 32.401 describes performance management concepts and requirements.
+
+The present document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network. Only measurement types that are specific to UMTS or combined UMTS/GSM networks are defined within the present documents.
+
+Vendor-specific measurement types used in UMTS and combined UMTS/GSM networks are not covered. Instead, these could be applied according to the manufacturer's documentation.
+
+Measurements related to "external" technologies (such as ATM or IP), as described by "external" standards bodies (e.g., ITU-T or IETF), shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
+
+The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardized across all vendors' implementations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 405 | 7.6.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 405 | 7.6.0 | Published | 2007-10-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532405v760 |
+| ATIS | ATIS.3GPP.32.405V760-2007 | 7.6.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| ETSI | TTAT.3G-32.405(R7-7.5.0) | 7.5.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.405(R7-7.5.0).zip |
+| TTA | TS-3GA-32.405(Rel7)v7.6.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32405rel7v760.pdf |
+
+### 10.10.111 TS 32.406 Telecommunication management; Performance management (PM); Performance measurements core network (CN) packet switched (PS) domain
+
+The present document describes the measurements for UMTS and combined UMTS/GSM.
+
+TS 32.401 describes performance management concepts and requirements.
+
+The present document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network.
+
+Only measurement types that are specific to UMTS or combined UMTS/GSM networks are defined within the present documents. Vendor-specific measurement types used in UMTS and combined UMTS/GSM networks are not covered. Instead, these could be applied according to the manufacturer's documentation.
+
+Measurements related to "external" technologies (such as ATM or IP), as described by "external" standards bodies (e.g., ITU-T or IETF), shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
+
+The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardized across all vendors' implementations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 406 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 406 | 7.1.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532406v710 |
+| ATIS | ATIS.3GPP.32.406V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| ETSI | TTAT.3G-32.406(R7-7.1.0) | 7.1.0 | Approved | 2007-02-15 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.406(R7-7.1.0).zip |
+| TTA | TS-3GA-32.406(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32406rel7v710.pdf |
+
+**10.10.112 TS 32.407 Telecommunication management; Performance management (PM); Core network (CN) circuit switched (CS) domain; Performance measurements – UMTS and combined UMTS/GSM**
+
+The present document describes the CN CS measurements for UMTS and combined UMTS/GSM.
+
+TS 32.401 describes performance management concepts and requirements.
+
+The present document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network. These may be measurement types defined within the present document, measurements defined within other standards bodies, or vendor-specific measurement types.
+
+Only measurement types that are specific to CN CS UMTS or combined UMTS/GSM networks are defined within the present documents, i.e., vendor-specific measurement types used in UMTS and combined UMTS/GSM networks. Some ATM or IP measurements defined here are only used for load carrying. The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardized across all vendors' implementations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 407 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 407 | 7.1.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532407v710 |
+| ATIS | ATIS.3GPP.32.407V 710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.407(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.407(R7-7.1.0).zip |
+| TTC | TS-3GA-32.407(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32407rel7v710.pdf |
+
+**10.10.113 TS 32.408 Telecommunication management; Performance management (PM); Performance measurements teleservice**
+
+The present document describes the measurements for UMTS and combined UMTS/GSM.
+
+TS 32.401 describes performance management concepts and requirements.
+
+The present document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network.
+
+Only measurement types that are specific to UMTS or combined UMTS/GSM networks are defined within the present documents. Vendor-specific measurement types used in UMTS and combined UMTS/GSM networks are not covered. Instead, these could be applied according to the manufacturer's documentation.
+
+Measurements related to "external" technologies (such as ATM or IP), as described by "external" standards bodies (e.g., ITU-T or IETF), shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
+
+The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardized across all vendors' implementations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 408 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 408 | 7.2.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532408v720 |
+| ATIS | ATIS.3GPP.32.408V720-2007 | 7.2.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.408(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.408(R7-7.1.0).zip |
+| TTC | TS-3GA-32.408(Rel7)v7.2.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32408rel7v720.pdf |
+
+### 10.10.114 TS 32.409 Telecommunication management; Performance management (PM); Performance measurements – IP multimedia subsystem (IMS)
+
+The present document describes the measurements of IMS.
+
+TS 32.401 describes performance management concepts and requirements.
+
+The present document is valid for all measurement types provided by an implementation of an IMS network. These may be measurement types defined within the present document, measurements defined within other standards bodies, or vendor-specific measurement types.
+
+Only measurement types that are specific to IMS network are defined within the present documents, i.e., vendor-specific measurement types and measurements related to "external" technologies used in IMS network, such as ATM or IP, are not covered. Instead, these could be applied as described by the other, "external" standards bodies (e.g., ITU-T or IETF) or according to the manufacturer's documentation.
+
+The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardized across all vendors' implementations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 409 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 409 | 7.1.0 | Published | 2007-10-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532409v710 |
+| ATIS | ATIS.3GPP.32.409V710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.409(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.409(R7-7.0.0).zip |
+| TTC | TS-3GA-32.409(Rel7)v7.1.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32409rel7v710.pdf |
+
+### 10.10.115 TS 32.411 Telecommunication management; Performance management (PM) integration reference point (IRP): Requirements
+
+The present document specifies the overall requirements for the performance management integration reference point (PMIRP) as it applies to the network elements (NE), element manager (EM) and network manager (NM).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 411 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 411 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532411v700 |
+| ATIS | ATIS.3GPP.32.411V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.411(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.411(R7-7.0.0).zip |
+| TTC | TS-3GA-32.411(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32411rel7v700.pdf |
+
+### 10.10.116 TS 32.412 Telecommunication management; Performance management (PM) integration reference point (IRP): Information service (IS)
+
+The present document specifies the information service for the performance management integration reference point (PMIRP) as it applies to the Itf-N.
+
+This IRP IS defines the semantics of operations (and their parameters) visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 412 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 412 | 7.1.0 | Published | 2007-10-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532412v710 |
+| ATIS | ATIS.3GPP.32.412V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.412(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.412(R7-7.0.0).zip |
+| TTC | TS-3GA-32.412(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32412rel7v710.pdf |
+
+**10.10.117 TS 32.413 Telecommunication management; Performance management (PM) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The present document specifies the common object request broker architecture (CORBA) solution set (SS) for the IRP whose semantics is specified in PM (performance management) IRP: Information service 3G TS 32.412.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 413 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 413 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532413v700 |
+| ATIS | ATIS.3GPP.32.413V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.413(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.413(R7-7.0.0).zip |
+| TTC | TS-3GA-32.413(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32413rel7v700.pdf |
+
+**10.10.118 TS 32.415 Telecommunication management; Performance management (PM) integration reference point (IRP); eXtensible markup language (XML) definitions**
+
+The present document specifies the XML definitions for the performance management (PM) integration reference point (IRP) as it applies to Itf-N, in accordance with PM IRP IS definitions in 3GPP TS 32.412, as well as the notification log IRP XML definitions in 3GPP TS 32.335.
+
+This specification is related to 3GPP TS 32.412.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 415 | 7.0.1 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 415 | 7.0.1 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532415v701 |
+| ATIS | ATIS.3GPP.32.415V701-2007 | 7.0.1 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.415(R7-7.0.1) | 7.0.1 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.415(R7-7.0.1).zip |
+| TTC | TS-3GA-32.415(Rel7)v7.0.1 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32415rel7v701.pdf |
+
+**10.10.119 TS 32.421 Telecommunication management; Subscriber and equipment trace: Trace concepts and requirements**
+
+The present document describes the requirements for the management of trace and the reporting of trace data across UMTS networks as it refers to subscriber tracing (tracing of IMSI or private ID)
+
+and MS tracing (tracing of IMEI or IMEISV). It defines the administration of trace session activation/deactivation by the element manager (EM) or the network itself via signalling, the generation of trace results in the network elements (NEs) and the transfer of these results to one or more operations systems, i.e., EM(s) and/or network manager(s) (NM(s)).
+
+The basic subscriber and MS trace concept that the present document is built upon is described in clause 4. The high-level requirements for trace data, trace session activation/deactivation and trace reporting are defined in clause 5. Clause 5 also contains an overview of use cases for trace (the use cases are described in Annex B). Annex A provides a high-level view of trace functional architecture. Trace control and configuration management are described in 3GPP TS 32.422, and trace data definition and management are described in 3GPP TS 32.423.
+
+In this release, the present document does not cover any trace capability limitations within a NE (e.g., maximum number of simultaneous traced mobiles for a given NE) or any functionality related to these limitations (e.g., NE aborting a trace session due to resource limitations).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 421 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/technical.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 421 | 7.2.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TS/SGS-0532421v720 |
+| ATIS | ATIS.3GPP.32.421V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.421(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.421(R7-7.2.0).zip |
+| TTC | TS-3GA-32.421(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32421rel7v720.pdf |
+
+#### **10.10.120 TS 32.422 Telecommunication management; Subscriber and equipment trace; Trace control and configuration management**
+
+The present document describes the mechanisms used for the control and configuration of the trace functionality at the EMs and NEs. It covers the triggering events for starting/stopping of subscriber/MS activity traced over 3GPP standardized signalling interfaces, the types of trace mechanisms, configuration of a trace, level of detail available in the trace data, the generation of trace results in the network elements (NEs) and the transfer of these results to one or more EM(s) and/or network manager(s) (NM(s)).
+
+The mechanisms for trace activation/deactivation are detailed in clause 4; clause 5 details the various trace control and configuration parameters and the triggering events that can be set in a network. Trace concepts and requirements are covered in 3G TS 32.421, while trace data definition and management is covered in 3G TS 32.423.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 422 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 422 | 7.2.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532422v720 |
+| ATIS | ATIS.3GPP.32.422V720-2007 | 7.2.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.422(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.422(R7-7.2.0).zip |
+| TTC | TS-3GA-32.422(Rel7)v7.2.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32422rel7v720.pdf |
+
+#### **10.10.121 TS 32.423 Telecommunication management; Subscriber and equipment trace: Trace data definition and management**
+
+The present document describes trace data definition and management. It covers trace records content, their format and transfer.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 423 | 7.4.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 423 | 7.4.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532423v740 |
+| ATIS | ATIS.3GPP.32.423V740-2007 | 7.4.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.423(R7-7.4.0) | 7.4.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.423(R7-7.4.0).zip |
+| TTC | TS-3GA-32.423(Rel7)v7.4.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32423rel7v740.pdf |
+
+#### **10.10.122 TS 32.432 Telecommunication management; Performance measurement: File format definition**
+
+The present document describes the general semantics of performance measurement result and collection. It defines the report file format, report file conventions and the file transfer procedure. Clause 4 specifies the file format for the bulk transfer of performance measurement results to the NM, while clause 6 discusses the file transfer procedure utilized on that interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 432 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 432 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532432v700 |
+| ATIS | ATIS.3GPP.32.432V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.432(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.432(R7-7.0.0).zip |
+| TTC | TS-3GA-32.432(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32432rel7v700.pdf |
+
+#### **10.10.123 TS 32.435 Telecommunication management; Performance measurement eXtensible markup language (XML) file format definition**
+
+The present document describes the XML file format of performance measurement results whose semantics is defined in 3G TS 32.432.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 435 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 435 | 7.2.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532435v720 |
+| ATIS | ATIS.3GPP.32.435V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.435(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.435(R7-7.2.0).zip |
+| TTC | TS-3GA-32.435(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32435rel7v720.pdf |
+
+#### **10.10.124 TS 32.436 Telecommunication management; Performance measurement: Abstract syntax notation one (ASN.1) file format definition**
+
+The present document defines the ASN.1 file format definition for performance measurement results collection whose semantics is defined in 3G TS 32.432.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 436 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 436 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532436v700 |
+| ATIS | ATIS.3GPP.32.436V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.436(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.436(R7-7.0.0).zip |
+| TTC | TS-3GA-32.436(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32436rel7v700.pdf |
+
+### 10.10.125 TS 32.441 Telecommunication management; Trace management integration reference point (IRP): Requirements
+
+The present document specifies the overall requirements for the trace management integration reference point (TraceIRP) as it applies to Itf-N.
+
+The trace IRP supports the operations that are required for the subscriber and equipment trace, the service level trace and the cell traffic trace functionalities.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 441 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 441 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532441v700 |
+| ATIS | ATIS.3GPP.32.441V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.441(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.441(R7-7.0.0).zip |
+| TTC | TS-3GA-32.441(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32441rel7v700.pdf |
+
+**10.10.126 TS 32.442 Telecommunication management; Trace management integration reference point (IRP): Information service (IS)**
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 442 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 442 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532442v700 |
+| ATIS | ATIS.3GPP.32.442V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.442(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.442(R7-7.0.0).zip |
+| TTC | TS-3GA-32.442(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32442rel7v700.pdf |
+
+**10.10.127 TS 32.443 Telecommunication management; Trace management integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+This solution set specification is related to TS 32.442.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 443 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 443 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532443v700 |
+| ATIS | ATIS.3GPP.32.443V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.443(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.443(R7-7.0.0).zip |
+| TTC | TS-3GA-32.443(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32443rel7v700.pdf |
+
+**10.10.128 TS 32.445 Telecommunication management; Trace management integration reference point (IRP): eXtensible markup language (XML) file format definition**
+
+The present document is the eXtensible markup language (XML) file format definition of trace IRP for the IRP whose semantics is specified in trace IRP: Information service (TS 32.442).
+
+This XML definitions specification defines the XML syntax of the trace IRP XML data file for the notifications related to trace IRP. The XML file definitions for a trace data file can be found in Annex A of TS 32.423.
+
+This XML file format definition specification is related to 3GPP TS 32.442.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 445 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 445 | 7.0.0 | Published | 2007-07-10 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532445v700 |
+| ATIS | ATIS.3GPP.32.445V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.445(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.445(R7-7.0.0).zip |
+| TTC | TS-3GA-32.445(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32445rel7v700.pdf |
+
+### 10.10.129 TS 32.600 Telecommunication management; Configuration management (CM); Concept and high-level requirements
+
+The document describes the configuration management (CM) aspects of managing a 3G network. This is described from the management perspective in TS 32.101 and TS 32.102.
+
+This document defines a set of controls to be employed to effect set-up and changes to a 3G network in such a way that operational capability and quality of service (QoS), network integrity and system interworking are ensured. In this way, this document describes the interface definition and behaviour for the management of relevant 3G NEs in the context of the described management environment. The context is described for both the management system (OS) and network element (NE) functionality.
+
+The Itf-N for CM is built up by a number of integration reference points (IRPs) and a related name convention, which realize the functional capabilities over this interface. The basic structure of the IRPs is defined in TS 32.101 and TS 32.102. For CM, a number of IRPs (and a name convention TS 32.300) are defined, used by this as well as by other specifications for telecom management produced by 3GPP. These IRPs are defined in separate specifications.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 600 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 600 | 7.0.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532600v700 |
+| ATIS | ATIS.3GPP.32.600V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.600(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.600(R7-7.0.0).zip |
+| TTC | TS-3GA-32.600(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32600rel7v700.pdf |
+
+**10.10.130 TS 32.601 Telecommunication management; Configuration management (CM); Basic CM integration reference point (IRP); Requirements**
+
+The present document defines, in addition to the requirements defined in TS 32.101, TS 32.102 and TS 32.600, the requirements for the present IRP: Basic configuration management IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 601 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 601 | 7.2.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532601v720 |
+| ATIS | ATIS.3GPP.32.601V 720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.601(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.601(R7-7.2.0).zip |
+| TTC | TS-3GA-32.601(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32601rel7v720.pdf |
+
+**10.10.131 TS 32.602 Telecommunication management; Configuration management; Basic CM integration reference point (IRP) information service**
+
+The document defines a component of an integration reference point (IRP) through which an 'IRPAgent' (typically an element manager or network element) can communicate basic configuration management-related information to one or several 'IRPManagers' (typically network managers).
+
+This version of the IRP is mainly intended for "passive management" of high-level network configuration and status information as required by a network manager.
+
+The configuration management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs – as described in the introduction clause. An important aspect of such a split is that the network resource models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP information service. The Basic CM IRP: IS defined herein provides one such information service.
+
+The basic CM IRP: IS defined in the document has the following main purpose: to define an interface for retrieval of configuration management information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 602 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 602 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532602v700 |
+| ATIS | ATIS.3GPP.32.602V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.602(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.602(R7-7.0.0).zip |
+| TTC | TS-3GA-32.602(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32602rel7v700.pdf |
+
+### 10.10.132 TS 32.603 Telecommunication management; Configuration management; Basic configuration management IRP: CORBA solution set
+
+The purpose of this *Basic Configuration Management (CM) IRP: CORBA Solution Set* is to define the mapping of the basic CM IRP: IS (see TS 32.602) to the protocol-specific details necessary for implementation of this IRP in a CORBA/IDL environment.
+
+This document defines NRM independent data types, methods and notifications.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 603 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 603 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532603v700 |
+| ATIS | ATIS.3GPP.32.603V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.603(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.603(R7-7.0.0).zip |
+| TTC | TS-3GA-32.603(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32603rel7v700.pdf |
+
+### 10.10.133 TS 32.607 Telecommunication management; Configuration management (CM); Basic CM integration reference point (IRP): SOAP solution set (SS)
+
+The purpose of this basic CM IRP: SOAP solution set is to define the mapping of the basic CM IRP: IS (TS 32.602) to the protocol specific details necessary for the implementation of this IRP in a SOAP/WSDL environment.
+
+The present document defines NRM independent data types and methods.
+
+This solution set specification is related to 3G TS 32.602.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 607 | 7.0.3 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 607 | 7.0.3 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532607v703 |
+| ATIS | ATIS.3GPP.32.607V703-2007 | 7.0.3 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.607(R7-7.0.3) | 7.0.3 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.607(R7-7.0.3).zip |
+| TTC | TS-3GA-32.607(Rel7)v7.0.3 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32607rel7v702.pdf |
+
+### 10.10.134 TS 32.611 Telecommunication management; 3G configuration management (CM); Bulk CM integration reference point (IRP): Requirements
+
+The document describes the bulk configuration management (CM) requirements for managing a 3G network. This is described from the management perspective in TS 32.101 and TS 32.102.
+
+The Itf-N for CM is built up by a number of integration reference points (IRPs) and a related name convention TS 32.300, which realize the functional capabilities over this interface. The basic structure of the IRPs is defined in TS 32.101 and TS 32.102. For CM, a number of IRPs (and a name convention) are defined, used by this as well as by other specifications for telecom management. These IRPs are defined in separate specifications. This document defines the requirements for the bulk CM IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 611 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 611 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532611v700 |
+| ATIS | ATIS.3GPP.32.611V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.611(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.611(R7-7.0.0).zip |
+| TTC | TS-3GA-32.611(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32611rel7v700.pdf |
+
+### 10.10.135 TS 32.612 Telecommunication management; 3G configuration management (CM); Bulk CM integration reference point (IRP): Information service
+
+The document (bulk configuration management IRP: Information service) defines an integration reference point (IRP) through which an 'IRP Agent' (typically an element manager or network element) can communicate bulk configuration management related information to one or several 'IRP Managers' (typically network managers).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 612 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 612 | 7.2.0 | Published | 2007-04-05 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532612v720 |
+| ATIS | ATIS.3GPP.32.612V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.612(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.612(R7-7.2.0).zip |
+| TTC | TS-3GA-32.612(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32612rel7v720.pdf |
+
+### **10.10.136 TS 32.613 Telecommunication management; 3G configuration management (CM); Bulk CM integration reference point (IRP): CORBA solution set**
+
+The purpose of this *Bulk CM IRP: CORBA Solution Set* is to define the mapping of the IRP information service (see TS 32.612) to the protocol-specific details necessary for implementation of this IRP in a CORBA/IDL environment.
+
+The document does not describe any network resource models (NRMs) – they are described in generic network resources IRP: NRM TS 32.622, UTRAN network resources IRP: NRM TS 32.642.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 613 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 613 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532613v700 |
+| ATIS | ATIS.3GPP.32.613V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.613(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.613(R7-7.0.0).zip |
+| TTC | TS-3GA-32.613(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32613rel7v700.pdf |
+
+### **10.10.137 TS 32.615 Telecommunication management; Configuration management (CM); Bulk CM integration reference point (IRP): eXtensible markup language (XML) file format definition**
+
+The document defines the XML file formats for the configuration data files and session log files of bulk CM IRP IS TS 32.612.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 615 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 615 | 7.2.0 | Published | 2007-10-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532615v720 |
+| ATIS | ATIS.3GPP.32.615V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.615(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.615(R7-7.1.0).zip |
+| TTC | TS-3GA-32.615(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32615rel7v720.pdf |
+
+#### 10.10.138 TS 32.621 Telecommunication management; Configuration management (CM); Generic network resources integration reference point (IRP): Requirements
+
+The document defines, in addition to the requirements defined in TS 32.101, 32.102 and 32.600, the requirements for the present IRP: Generic network resources IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 621 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 621 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532621v700 |
+| ATIS | ATIS.3GPP.32.621V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.621(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.621(R7-7.0.0).zip |
+| TTC | TS-3GA-32.621(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32621rel7v700.pdf |
+
+#### 10.10.139 TS 32.622 Telecommunication management; Configuration management (CM); Generic network resources IRP; Network resource model (NRM)
+
+The document (generic network resources IRP: Network resource model) defines an integration reference point (IRP) through which an 'IRPAgent' (typically an element manager or network element) can communicate network management-related information to one or several 'IRPManagers' (typically network managers).
+
+The document specifies a generic network resource model (NRM) (also referred to as a management information model – MIM) with definitions of managed object classes.
+
+The configuration management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs. In addition to the subject IRP, it is expected that IRPs will be defined for functional areas like security management, software management, network & service provisioning, etc. An important aspect of such a split is that the network resource models (NRMs)
+
+defined in different IRPs are consistent. The generic network resources IRP here provides a base for all resource modelling.
+
+The generic network resources IRP main purpose is to define a generic network resource model that constitutes a base from which other (more specialized) resource models can inherit or have associations with.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 622 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 622 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532622v700 |
+| ATIS | ATIS.3GPP.32.622V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.622(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.622(R7-7.0.0).zip |
+| TTC | TS-3GA-32.622(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32622rel7v700.pdf |
+
+#### **10.10.140 TS 32.623 Telecommunication management; Configuration management (CM); Generic network resources IRP: CORBA solution set**
+
+The TS 32.620 series (generic network resources IRP) defines an integration reference point (IRP) through which an 'IRPAgent' (typically an element manager or network element) can communicate network management-related information to one or several 'IRPManagers' (typically network managers).
+
+This series of documents specifies a generic network resource model (NRM) (also referred to as a management information model – MIM) with definitions of information object classes and managed object classes.
+
+The document specifies the CORBA solution set.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 623 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 623 | 7.1.0 | Published | 2007-10-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532623v710 |
+| ATIS | ATIS.3GPP.32.623V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.623(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.623(R7-7.0.0).zip |
+| TTC | TS-3GA-32.623(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32623rel7v710.pdf |
+
+**10.10.141 TS 32.625 Telecommunication management; Configuration management (CM); Generic network resources IRP: Bulk CM eXtensible markup language (XML) file format definition**
+
+This document provides the NRM-specific part related to the generic network resources IRP NRM (3G TS 32.622) of the XML file format definition for the bulk configuration management IRP IS (3G TS 32.612).
+
+The main part of this XML file format definition is provided by 3G TS 32.615.
+
+This file format definition specification is related to 3G TS 32.622.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 625 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 625 | 7.1.0 | Published | 2007-10-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532625v710 |
+| ATIS | ATIS.3GPP.32.625V710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.625(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.625(R7-7.0.0).zip |
+| TTC | TS-3GA-32.625(Rel7)v7.1.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32625rel7v710.pdf |
+
+**10.10.142 TS 32.631 Telecommunication management; Configuration management (CM); Core network resources IRP: Requirements**
+
+The document defines, in addition to the requirements defined in TS 32.101, 32.102 and 32.600, the requirements for the present IRP: Core network resources IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 631 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 631 | 7.1.0 | Published | 2007-04-05 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532631v710 |
+| ATIS | ATIS.3GPP.32.631V710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.631(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.631(R7-7.1.0).zip |
+| TTC | TS-3GA-32.631(Rel7)v7.1.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32631rel7v710.pdf |
+
+### 10.10.143 TS 32.632 Telecommunication management; Configuration management; Core network resources IRP: Network resource model (NRM)
+
+The document is part of an integration reference point (IRP) named "Core Network Resources IRP", through which an 'IRPAgent' (typically an element manager or network element) can communicate configuration management information to one or several 'IRPManagers' (typically network managers) concerning CN resources. This version of the IRP is mainly intended for "passive management" of high-level network configuration and status information as required by a network manager. The "Core Network Resources IRP" comprises a set of specifications defining Requirements, a protocol-neutral network resource model (NRM) and corresponding solution set(s).
+
+The document specifies the protocol-neutral core network resources IRP: Network resource model. It reuses relevant parts of the generic NRM in TS 32.622, either by direct reuse or sub-classing, and in addition to that defines CN-specific managed object classes.
+
+The configuration management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs – as described in the Introduction clause. An important aspect of such a split is that the network resource models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP information service.
+
+The document has the following main purpose: to define the applied CN-specific network resource model, based on the generic NRM in TS 32.622.
+
+Finally, in order to access the information defined by this NRM, an IRP information service (IS) is needed, such as the basic CM IRP: IS TS 32.602. However, which information service that is applicable is outside the scope of this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 632 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 632 | 7.2.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532632v720 |
+| ATIS | ATIS.3GPP.32.632V720-2007 | 7.2.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.632(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.632(R7-7.1.0).zip |
+| TTC | TS-3GA-32.632(Rel7)v7.2.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32632rel7v720.pdf |
+
+### 10.10.144 TS 32.633 Telecommunication management; Configuration management (CM); Core network resources IRP: CORBA solution set
+
+The purpose of this *Core Network Resources IRP: CORBA Solution Set* is to define the mapping of the IRP information model (see TS 32.632) to the protocol-specific details necessary for implementation of this IRP in a CORBA/IDL environment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 633 | 7.3.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 633 | 7.3.0 | Published | 2007-10-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532633v730 |
+| ATIS | ATIS.3GPP.32.633V730-2007 | 7.3.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.633(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.633(R7-7.1.0).zip |
+| TTC | TS-3GA-32.633(Rel7)v7.3.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32633rel7v730.pdf |
+
+**10.10.145 TS 32.635 Telecommunication management; Configuration management (CM); Core network resources IRP: Bulk CM eXtensible markup language (XML) file format definition**
+
+This document provides the NRM-specific part related to the core network resources IRP NRM (3G TS 32.632) of the XML file format definition for the bulk configuration management IRP IS (3G TS 32.612).
+
+The main part of this XML file format definition is provided by 3G TS 32.615.
+
+This file format definition specification is related to 3G TS 32.632.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 635 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 635 | 7.2.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532635v720 |
+| ATIS | ATIS.3GPP.32.635V720-2007 | 7.2.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.635(R7-7.0.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.635(R7-7.1.0).zip |
+| TTC | TS-3GA-32.635(Rel7)v7.2.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32635rel7v720.pdf |
+
+**10.10.146 TS 32.641 Telecommunication management; Configuration management (CM); UTRAN network resources IRP: Requirements**
+
+The document defines, in addition to the requirements defined in TS 32.101, 32.102 and 32.600, the requirements for the present IRP: UTRAN network resources IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 641 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 641 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TS/SGS-0532641v700 |
+| ATIS | ATIS.3GPP.32.641V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.641(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.641(R7-7.0.0).zip |
+| TTC | TS-3GA-32.641(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32641rel7v700.pdf |
+
+#### **10.10.147 TS 32.642 Telecommunication management; Configuration management (CM); UTRAN network resources IRP: NRM**
+
+The document is part of an integration reference point (IRP) named "UTRAN Network Resources IRP", through which an 'IRPAgent' (typically an element manager or network element) can communicate configuration management information to one or several 'IRPManagers' (typically network managers) concerning UTRAN resources. The "UTRAN Network Resources IRP" comprises a set of specifications defining Requirements, a protocol neutral network resource model (NRM) and corresponding solution set(s).
+
+The document specifies the protocol neutral UTRAN network resources IRP: Network resource model. It reuses relevant parts of the generic NRM in TS 32.622, either by direct reuse or subclassing, and in addition to that defines UTRAN specific managed object classes.
+
+The configuration management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs – as described in the introduction clause. An important aspect of such a split is that the network resource models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP information service.
+
+The document has the following main purpose: to define the applied UTRAN-specific network resource model, based on the generic NRM in TS 32.600.
+
+Finally, in order to access the information defined by this NRM, an IRP information service (IS) is needed, such as the basic CM IRP: IS 32.602 or the bulk CM IRP: IS 32.612. However, which information service is applicable is outside the scope of this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 642 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 642 | 7.2.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532642v720 |
+| ATIS | ATIS.3GPP.32.642V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.642(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.642(R7-7.1.0).zip |
+| TTC | TS-3GA-32.642(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32642rel7v720.pdf |
+
+#### **10.10.148 TS 32.643 Telecommunication management; Configuration management (CM); UTRAN network resources IRP: CORBA solution set**
+
+The purpose of this UTRAN network resources IRP: CORBA solution set is to define the mapping of the IRP information model (see TS 32.642) to the protocol-specific details necessary for implementation of this IRP in a CORBA/IDL environment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 643 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 643 | 7.2.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532643v720 |
+| ATIS | ATIS.3GPP.32.643V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.643(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.643(R7-7.2.0).zip |
+| TTC | TS-3GA-32.643(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32643rel7v720.pdf |
+
+#### **10.10.149 TS 32.645 Telecommunication management; Configuration management (CM); UTRAN network resources IRP: Bulk CM eXtensible markup language (XML) file format definition**
+
+This document provides the NRM-specific part related to the UTRAN network resources IRP NRM (3G TS 32.642) of the XML file format definition for the bulk configuration management IRP IS (3G TS 32.612).
+
+The main part of this XML file format definition is provided by 3G TS 32.615.
+
+This file format definition specification is related to 3G TS 32.642.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 645 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 645 | 7.2.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532645v720 |
+| ATIS | ATIS.3GPP.32.645V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.645(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.645(R7-7.2.0).zip |
+| TTC | TS-3GA-32.645(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32645rel7v720.pdf |
+
+#### **10.10.150 TS 32.661 Telecommunication management; Configuration management (CM); Kernel CM; Requirements**
+
+This document defines, in addition to the requirements defined in 3G TS 32.101, 3G TS 32.102, and 3G TS 32.600, the requirements for the present IRP: Kernel configuration management IRP. It is the intent of Kernel configuration management to provide an IRP that contains the configuration management functionality that is basic and minimal. It is the functionality that is common to and required by both basic CM and bulk CM. While neither the basic CM IRP nor bulk CM IRP requires the other, they each require the Kernel CM IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 661 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 661 | 7.0.0 | Published | 2007-06-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532661v700 |
+| ATIS | ATIS.3GPP.32.661V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.661(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.661(R7-7.0.0).zip |
+| TTC | TS-3GA-32.661(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32661rel7v700.pdf |
+
+#### **10.10.151 TS 32.662 Telecommunication management; Configuration management (CM); Kernel CM; Information service**
+
+This document defines integration reference point (IRP) through which an 'IRPAgent' (typically an element manager or network element) can communicate configuration management-related information to one or several 'IRPManagers' (typically network managers).
+
+The function of this Kernel CM IRP information service is to define an interface that provides the essential CM services. While it is not expected that the Kernel CM IRP alone will provide adequate CM capability, the Kernel CM IRP is expected to provide the common supporting capability required for other IRPs such as the basic CM IRP or the bulk CM IRP, each of which requires the Kernel CM IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 662 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 662 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532662v700 |
+| ATIS | ATIS.3GPP.32.662V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.662(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.662(R7-7.0.0).zip |
+| TTC | TS-3GA-32.662(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32662rel7v700.pdf |
+
+#### **10.10.152 TS 32.663 Telecommunication management; Configuration management (CM); Kernel CM: CORBA solution set**
+
+The purpose of this document is to define the mapping of the Kernel CM IRP: IS (see 3G TS 32.662) to the protocol-specific details necessary for implementation of this IRP in a CORBA/IDL environment.
+
+This solution set specification is related to 3G TS 32.662.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 663 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 663 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532663v700 |
+| ATIS | ATIS.3GPP.32.663V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.663(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.663(R7-7.0.0).zip |
+| TTC | TS-3GA-32.663(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32663rel7v700.pdf |
+
+#### **10.10.153 TS 32.665 Telecommunication management; Configuration management (CM); Kernel CM integration reference point (IRP): eXtensible markup language (XML) definitions**
+
+The present document specifies the XML definitions for the Kernel CM integration reference point (IRP) as it applies to Itf-N, in accordance with Kernel CM IRP IS definitions in TS 32.662 as well as the notification log IRP XML definitions in TS 32.335.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 665 | 7.0.2 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 665 | 7.0.2 | Published | 2007-07-25 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532665v702 |
+| ATIS | ATIS.3GPP.32.665V702-2007 | 7.0.2 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.665(R7-7.0.1) | 7.0.1 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.665(R7-7.0.1).zip |
+| TTC | TS-3GA-32.665(Rel7)v7.0.2 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32665rel7v701.pdf |
+
+#### **10.10.154 TS 32.667 Telecommunication management; Configuration management (CM); Kernel CM integration reference point (IRP): SOAP solution set (SS)**
+
+The purpose of the present document is to define the mapping of the Kernel CM IRP: IS (TS 32.662) to the protocol-specific details necessary for the implementation of this IRP in a SOAP/WSDL environment.
+
+This solution set specification is related to TS 32.662.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 667 | 7.0.2 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 667 | 7.0.2 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532667v702 |
+| ATIS | ATIS.3GPP.32.667V702-2007 | 7.0.2 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.667(R7-7.0.1) | 7.0.1 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.667(R7-7.0.1).zip |
+| TTC | TS-3GA-32.667(Rel7)v7.0.2 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32667rel7v701.pdf |
+
+#### **10.10.155 TS 32.671 Telecommunication management; Configuration management (CM); State management integration reference point (IRP): Requirements**
+
+This document defines, in addition to the requirements defined in 3G TS 32.101, 3G TS 32.102 and 3G TS 32.600, the requirements for the present IRP: State management.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 671 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 671 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532671v700 |
+| ATIS | ATIS.3GPP.32.671V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.671(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.671(R7-7.0.0).zip |
+| TTC | TS-3GA-32.671(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32671rel7v700.pdf |
+
+#### **10.10.156 TS 32.672 Telecommunication management; Configuration management (CM); State management integration reference point (IRP): Information service**
+
+This document defines the information service (IS) part of the state management IRP. It specifies the semantics of the network resource state and status information visible across the Itf-N. It also specifies the interaction required for the management of the state and status information.
+
+The state and status attributes specified in this document shall be used, where applicable, as attributes in information object class (IOC) definitions of other 3G IRPs. When used by the IOC definition, the semantics of the state and status attributes can be qualified and enhanced, if deemed necessary.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 672 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 672 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532672v700 |
+| ATIS | ATIS.3GPP.32.672V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.672(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.672(R7-7.0.0).zip |
+| TTC | TS-3GA-32.672(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32672rel7v700.pdf |
+
+#### **10.10.157 TS 32.673 Telecommunication management; Configuration management (CM); State management integration reference point (IRP): CORBA solution set**
+
+This document specifies the CORBA solution set (SS) for the IRP whose semantics is specified in state management IRP: Information service (IS) (3G TS 32.672).
+
+Clauses 1 to 3 provide background information. Clause 4 provides key architectural features supporting the SS. Clause 5 defines the mapping of operations, notification, parameters and attributes defined in IS to their SS equivalents. Annex A contains the IDL specification.
+
+This solution set specification is related to 3G TS 32.672.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 673 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 673 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532673v700 |
+| ATIS | ATIS.3GPP.32.673V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.673(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.673(R7-7.0.0).zip |
+| TTC | TS-3GA-32.673(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32673rel7v700.pdf |
+
+**10.10.158 TS 32.675 Telecommunication management; Configuration management (CM); State management integration reference point (IRP): Bulk CM eXtensible markup language (XML) file format definition**
+
+The present document specifies the XML file format definition for the bulk configuration management IRP IS for the IRP whose semantics is specified in state management IRP: Information service (IS) (3G TS 32.672).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 675 | 7.0.2 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 675 | 7.0.2 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532675v702 |
+| ATIS | ATIS.3GPP.32.675V702-2007 | 7.0.2 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.675(R7-7.0.1) | 7.0.1 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.675(R7-7.0.1).zip |
+| TTC | TS-3GA-32.675(Rel7)v7.0.2 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32675rel7v702.pdf |
+
+**10.10.159 TS 32.690 Telecommunication management; Inventory management (IM): Requirements**
+
+The present document defines the requirements for the present IRP: Inventory management IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 690 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 690 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532690v700 |
+| ATIS | ATIS.3GPP.32.690V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.690(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.690(R7-7.0.0).zip |
+| TTC | TS-3GA-32.690(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32690rel7v700.pdf |
+
+#### **10.10.160 TS 32.691 Telecommunication management; Inventory management network resources integration reference point (IRP): Requirements**
+
+This document defines, in addition to the requirements defined in 3G TS 32.101, 3G TS 32.102 and 3G TS 32.600, the requirements for the present IRP: Inventory management network resources IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 691 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 691 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532691v700 |
+| ATIS | ATIS.3GPP.32.691V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.691(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.691(R7-7.0.0).zip |
+| TTC | TS-3GA-32.691(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32691rel7v700.pdf |
+
+#### **10.10.161 TS 32.692 Telecommunication management; Inventory management network resources integration reference point (IRP): Network resource model**
+
+This document defines an integration reference point (IRP) through which an 'IRPAgent' (typically an element manager or network element) can communicate network management-related information to one or several 'IRPManagers' (typically network managers).
+
+This document specifies an inventory management network resource model (NRM) (also referred to as a management information model – MIM) with definitions of information object classes.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 692 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 692 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532692v700 |
+| ATIS | ATIS.3GPP.32.692V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.692(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.692(R7-7.0.0).zip |
+| TTC | TS-3GA-32.692(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32692rel7v700.pdf |
+
+**10.10.162 TS 32.695 Telecommunication management; Inventory management (IM) network resource model (NRM) integration reference point (IRP): Bulk CM eXtensible markup language (XML) file format definition**
+
+The present document provides the NRM-specific part related to the inventory management NRM IRP IS 3GPP TS 32.692 of the XML file format definition for the bulk configuration management IRP IS 3GPP TS 32.612.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 695 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 695 | 7.0.0 | Published | 2007-07-02 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532695v700 |
+| ATIS | ATIS.3GPP.32.695V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.695(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.695(R7-7.0.0).zip |
+| TTC | TS-3GA-32.695(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32695rel7v700.pdf |
+
+**10.10.163 TS 32.711 Telecommunication management; Configuration management (CM); Transport network (TN) interface network resource model (NRM) integration reference point (IRP): Requirements**
+
+The present document defines the requirements for the present IRP: Transport network (TN) interface network resource model (NRM) integration reference point.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 711 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 711 | 7.0.0 | Published | 2007-07-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532711v700 |
+| ATIS | ATIS.3GPP.32.711V700-2007 | 7.0.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.711(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.711(R7-7.0.0).zip |
+| TTC | TS-3GA-32.711(Rel7)v7.0.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32711rel7v700.pdf |
+
+**10.10.164 TS 32.712 Telecommunication management; Configuration management (CM); Transport network (TN) interface network resource model (NRM) integration reference point (IRP): Information service (IS)**
+
+The present document is part of an integration reference point (IRP) named "Transport Network (TN) interface network resource model (NRM) IRP", through which an "IRPAgent" (typically an element manager or network element) can communicate configuration management information to one or several "IRPManagers" (typically network managers) concerning transport resources. The "Transport Network (TN) Interface Network Resource Model (NRM) IRP" comprises a set of specifications defining Requirements, a protocol-neutral network resource model (NRM) and corresponding solution set(s).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 712 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 712 | 7.1.0 | Published | 2007-10-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532712v710 |
+| ATIS | ATIS.3GPP.32.712V710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.712(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.712(R7-7.0.0).zip |
+| TTC | TS-3GA-32.712(Rel7)v7.1.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32712rel7v710.pdf |
+
+**10.10.165 TS 32.713 Telecommunication management; Configuration management (CM); Transport network (TN) interface network resource model (NRM) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The purpose of this transport network (TN) interface network resource model IRP: CORBA solution set is to define the mapping of the IRP information model (see 3G TS 32.712) to the protocol-specific details necessary for implementation of this IRP in a CORBA/IDL environment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 713 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 713 | 7.1.0 | Published | 2007-10-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532713v710 |
+| ATIS | ATIS.3GPP.32.713V710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.713(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.713(R7-7.0.0).zip |
+| TTC | TS-3GA-32.713(Rel7)v7.1.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32713rel7v710.pdf |
+
+**10.10.166 TS 32.715 Telecommunication management; Configuration management (CM); Transport network (TN) interface network resource model (NRM) integration reference point (IRP): Bulk CM eXtensible markup language (XML) file format definition**
+
+The present document provides the NRM-specific part related to 3G TS 32.712 transport network (TN) interface NRM IRP IS of the XML file format definition for the 3G TS 32.612 bulk configuration management IRP IS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 715 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 715 | 7.1.0 | Published | 2007-10-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532715v710 |
+| ATIS | ATIS.3GPP.32.715V710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.715(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.715(R7-7.0.0).zip |
+| TTC | TS-3GA-32.715(Rel7)v7.1.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32715rel7v710.pdf |
+
+**10.10.167 TS 32.721 Telecommunication management; Configuration management (CM); Repeater network resources integration reference point (IRP): Requirements**
+
+This document defines, in addition to the requirements defined in 3GPP TS 32.101, 3GPP TS 32.102 and 3GPP TS 32.600, the requirements for the present repeater network resources IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 721 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 721 | 7.1.0 | Published | 2007-04-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532721v710 |
+| ATIS | ATIS.3GPP.32.721V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.721(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.721(R7-7.1.0).zip |
+| TTC | TS-3GA-32.721(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32721rel7v710.pdf |
+
+### **10.10.168 TS 32.722 Telecommunication management; Configuration management (CM); Repeater network resources integration reference point (IRP): Information service (IS)**
+
+The present document is part of an integration reference point (IRP) named "Repeater Network Resources IRP", through which an "IRPAgent" (typically an element manager or network element) can communicate configuration management information to one or several "IRPManagers" (typically network managers) concerning repeater resources. The "Repeater Network Resources IRP" comprises a set of specifications defining Requirements, a protocol neutral network resource model (NRM) and corresponding solution set(s).
+
+The present document specifies the protocol neutral repeater network resources IRP: Network resource model. It reuses relevant parts of the generic NRM in TS 32.622 and 32.642, either by direct reuse or sub-classing, and in addition to that defines repeater specific information object classes.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 722 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 722 | 7.0.0 | Published | 2007-04-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532722v700 |
+| ATIS | ATIS.3GPP.32.722V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.722(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.722(R7-7.0.0).zip |
+| TTC | TS-3GA-32.722(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32722rel7v700.pdf |
+
+**10.10.169 TS 32.723 Telecommunication management; Configuration management (CM); Repeater network resources integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The purpose of this repeater network resources IRP: CORBA solution set is to define the mapping of the IRP information model (see 3GPP TS 32.722) to the protocol-specific details necessary for the implementation of this IRP in a CORBA/IDL environment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 723 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 723 | 7.1.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532723v710 |
+| ATIS | ATIS.3GPP.32.723V 710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.723(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.723(R7-7.1.0).zip |
+| TTC | TS-3GA-32.723(Rel7)v7.1.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32723rel7v700.pdf |
+
+**10.10.170 TS 32.725 Telecommunication management; Configuration management (CM); Repeater network resources integration reference point (IRP): Bulk CM eXtensible markup language (XML) file format definition**
+
+The present document provides the NRM-specific part related to the repeater network resources IRP NRM (3GPP TS 32.722) of the XML file format definition for the bulk configuration management IRP IS (3GPP TS 32.612).
+
+The main part of this XML file format definition is provided by 3GPP TS 32.615.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 725 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 725 | 7.0.0 | Published | 2007-04-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532725v700 |
+| ATIS | ATIS.3GPP.32.725V 700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.725(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.725(R7-7.0.0).zip |
+| TTC | TS-3GA-32.725(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32725rel7v700.pdf |
+
+**10.10.171 TS 32.731 Telecommunication management; IP multimedia subsystem (IMS) network resource model (NRM) integration reference point (IRP): Requirements**
+
+This document defines, in addition to the requirements defined in 3GPP TS 32.101, 3GPP TS 32.102 and 3GPP TS 32.600, the requirements for the IMS network resource model (NRM) IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 731 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 731 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532731v700 |
+| ATIS | ATIS.3GPP.32.731V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.731(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.731(R7-7.0.0).zip |
+| TTC | TS-3GA-32.731(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32731rel7v700.pdf |
+
+**10.10.172 TS 32.732 Telecommunication management; IP multimedia subsystem (IMS) network resource model (NRM) integration reference point (IRP): Information service (IS)**
+
+The present document is part of an integration reference point (IRP) named IMS network resource model (NRM) IRP, through which an IRP Agent can communicate configuration management information to one or several IRP Managers concerning IMS resources. The IMS NRM IRP comprises a set of specifications defining Requirements, a protocol neutral information service and one or more solution set(s).
+
+The present document specifies the protocol neutral IMS NRM IRP: Information service (IS). It reuses relevant parts of the generic NRM IRP: IS in 3GPP TS 32.622, either by direct reuse or sub-classing, and in addition to that defines IMS-specific information object classes.
+
+Finally, in order to access the information defined by this NRM, an interface IRP is needed, such as the basic CM IRP in 3GPP TS 32.602. However, which interface IRP is applicable is outside the scope of the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 732 | 7.3.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 732 | 7.3.0 | Published | 2007-10-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532732v730 |
+| ATIS | ATIS.3GPP.32.732V730-2007 | 7.3.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.732(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.732(R7-7.2.0).zip |
+| TTC | TS-3GA-32.732(Rel7)v7.3.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32732rel7v730.pdf |
+
+**10.10.173 TS 32.733 Telecommunication management; IP multimedia subsystem (IMS) network resource model (NRM) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The purpose of this *IMS NRM IRP: CORBA Solution Set* is to define the mapping of the IRP information service (see TS 32.732) to the protocol-specific details necessary for the implementation of this IRP in a CORBA/IDL environment.
+
+This solution set specification is related to 3GPP TS 32.732.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 733 | 7.3.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 733 | 7.3.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532733v730 |
+| ATIS | ATIS.3GPP.32.733V730-2007 | 7.3.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.733(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.733(R7-7.2.0).zip |
+| TTC | TS-3GA-32.733(Rel7)v7.3.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32733rel7v730.pdf |
+
+**10.10.174 TS 32.735 Telecommunication management; IP multimedia subsystem (IMS) network resource model (NRM) integration reference point (IRP): eXtensible markup language (XML) file format definition**
+
+The present document provides the NRM-specific part related to the IMS NRM IRP (3GPP TS 32.732) of the XML file format definition for the bulk configuration management IRP IS (3GPP TS 32.612).
+
+The main part of this XML file format definition is provided by 3GPP TS 32.615.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 735 | 7.3.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 735 | 7.3.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532735v730 |
+| ATIS | ATIS.3GPP.32.735V730-2007 | 7.3.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.735(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.735(R7-7.2.0).zip |
+| TTC | TS-3GA-32.735(Rel7)v7.3.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32735rel7v730.pdf |
+
+**10.10.175 TS 32.741 Telecommunication management; Configuration management (CM); Signalling transport network (STN) interface network resource model (NRM) integration reference point (IRP): Requirements**
+
+The present document defines the requirements for the signalling transport network (STN) interface NRM IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 741 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 741 | 7.1.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532741v710 |
+| ATIS | ATIS.3GPP.32.741V710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.741(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.741(R7-7.1.0).zip |
+| TTC | TS-3GA-32.741(Rel7)v7.1.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32741rel7v710.pdf |
+
+**10.10.176 TS 32.742 Telecommunication management; Configuration management (CM); Signalling transport network (STN) interface network resource model (NRM) integration reference point (IRP): Information service (IS)**
+
+The present document is part of an integration reference point (IRP) named "Signalling Transport Network (STN) network resources IRP", through which an "IRPAgent" (typically an element manager or network element) can communicate configuration management information to one or several "IRPManagers" (typically network managers) concerning signalling transport resources. The "Signalling Transport Network (STN) network resources IRP" comprises a set of specifications defining Requirements, a protocol-neutral network resource model (NRM) and corresponding solution set(s).
+
+The present document specifies the protocol-neutral STN resources IRP: Network resource model.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 742 | 7.0.1 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 742 | 7.0.1 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532742v701 |
+| ATIS | ATIS.3GPP.32.742V701-2007 | 7.0.1 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.742(R7-7.0.1) | 7.0.1 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.742(R7-7.0.1).zip |
+| TTC | TS-3GA-32.742(Rel7)v7.0.1 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32742rel7v701.pdf |
+
+**10.10.177 TS 32.743 Telecommunication management; Configuration management (CM); Signalling transport network (STN) interface network resource model (NRM) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The purpose of this STN network resources IRP: CORBA solution set is to define the mapping of the IRP information model (see 3G TS 32.742) to the protocol-specific details necessary for implementation of this IRP in a CORBA/IDL environment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 743 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 743 | 7.2.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532743v720 |
+| ATIS | ATIS.3GPP.32.743V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.743(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.743(R7-7.2.0).zip |
+| TTC | TS-3GA-32.743(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32743rel7v720.pdf |
+
+**10.10.178 TS 32.745 Telecommunication management; Configuration management (CM); Signalling transport network (STN) interface network resource model (NRM) integration reference point (IRP): Bulk CM eXtensible markup language (XML) file format definition**
+
+The present document provides the NRM-specific part related to the STN network resources IRP NRM 3G TS 32.742 of the XML file format definition for the bulk configuration management IRP IS 3G TS 32.612.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 745 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 132 745 | 7.1.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532745v710 |
+| ATIS | ATIS.3GPP.32.745V710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-32.745(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-32.745(R7-7.1.0).zip |
+| TTC | TS-3GA-32.745(Rel7)v7.1.0 | 1 | TTC
Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts32745rel7v710.pdf |
+
+## 10.11 33-series, Security aspects
+
+### 10.11.1 TS 33.102 3G security; Security architecture
+
+This specification defines the security architecture, i.e., the security features and the security mechanisms, for the third generation mobile telecommunication system.
+
+A security feature is a service capability that meets one or several security requirements. The complete set of security features addresses the security requirements as they are defined in "3G Security: Threats and Requirements" (TS 21.133) and implement the security objectives and principles described in TS 33.120. A security mechanism is an element that is used to realize a security feature. All security features and security mechanisms taken together form the security architecture.
+
+An example of a security feature is user data confidentiality. A security mechanism that may be used to implement that feature is a stream cipher using a derived cipher key.
+
+This specification defines 3G security procedures performed within 3G capable networks (R99+), i.e., intra-UMTS and UMTS-GSM. As an example, UMTS authentication is applicable to UMTS radio access as well as GSM radio access provided that the serving network node and the MS are UMTS capable. Interoperability with non-UMTS capable networks (R98-) is also covered.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.102V7.1.0 | 6.40 | ARIB
published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/33/A33102-710.pdf |
+| CCSA | CCSA-TSD-133 102 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 133 102 | 7.1.0 | Published | 2006-12-21 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333102v710 |
+| ATIS | ATIS.3GPP.33.102V710-2007 | 7.1.0 | ATIS
Specification
Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-33.102(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-33.102(R7-7.1.0).zip |
+
+### 10.11.2 TS 33.105 3G security; Cryptographic algorithm requirements
+
+This specification constitutes a requirements specification for the security functions which may be used to provide the network access security features defined in 3G TS 33.102.
+
+The specification covers the intended use of the functions, the technical requirements on the functions and the requirements as regards standardization.
+
+For those functions that require standardization, it also covers the intended use of the algorithm specification, the requirements on test data, and quality assurance requirements on both the algorithm and its documentation.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.105V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/33/A33105-700.pdf |
+| CCSA | CCSA-TSD-133 105 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 133 105 | 7.0.0 | Published | 2007-07-05 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333105v700 |
+| ATIS | ATIS.3GPP.33.105V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-33.105(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-33.105(R7-7.0.0).zip |
+
+### 10.11.3 TS 33.106 Lawful interception requirements
+
+The document provides basic interception requirements within a third generation mobile communication system (3GMS).
+
+The specification describes the service requirements from a law enforcement point of view only. The aim of this document is to define a 3GMS interception system that supports a number of regional interception regulations, but these regulations are not repeated here as they vary. Regional interception requirements shall rely on this specification to derive such information, as they require.
+
+These interception requirements shall be used to derive specific network requirements.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.106V7.0.1 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/33/A33106-701.pdf |
+| CCSA | CCSA-TSD-133 106 | 7.0.1 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 133 106 | 7.0.1 | Published | 2006-04-21 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333106v701 |
+| ATIS | ATIS.3GPP.33.106V701-2007 | 7.0.1 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-33.106(R7-7.0.1) | 7.0.1 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-33.106(R7-7.0.1).zip |
+
+#### 10.11.4 TS 33.107 3G security; Lawful interception architecture and functions
+
+The document describes the architecture and functional requirements within a third generation mobile communication system (3GMS).
+
+The specification shows the service requirements from a law enforcement point of view only. The aim of this document is to define a 3GMS interception system that supports a number of regional interception regulations, but these regulations are not repeated here as they vary. Regional interception requirements shall be met in using specific (regional) mediation functions allowing only required information to be transported.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.107V7.7.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/33/A33107-770.pdf |
+| CCSA | CCSA-TSD-133 107 | 7.7.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 133 107 | 7.7.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333107v770 |
+| ATIS | ATIS.3GPP.33.107V770-2007 | 7.7.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-33.107(R7-7.6.0) | 7.6.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-33.107(R7-7.6.0).zip |
+
+#### 10.11.5 TS 33.108 3G security; Handover interface for lawful interception (LI)
+
+This specification addresses the handover interfaces for lawful interception of packet-data services, circuit-switched services, and multimedia services within the UMTS network. The handover interface in this context includes the delivery of intercept related information (HI2) and content of communication (HI3) to the law enforcement monitoring facility.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.108V7.8.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/33/A33108-780.pdf |
+| CCSA | CCSA-TSD-133 108 | 7.8.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 133 108 | 7.8.0 | Published | 2007-07-05 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TS/SGS-0333108v780 |
+| ATIS | ATIS.3GPP.33.108V780-2007 | 7.8.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-33.108(R7-7.8.0) | 7.8.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-33.108(R7-7.8.0).zip |
+
+### 10.11.6 TS 33.110 Key establishment between a universal integrated circuit card (UICC) and a terminal
+
+The present document describes the security features and mechanisms to provision a shared key between a UICC and a terminal that may host the UICC or be connected to the device hosting the UICC via a local interface. Candidate applications to use this key establishment mechanism include, but are not restricted to, secure channel between a UICC and a terminal [ETSI TS 102 484].
+
+The scope of this specification includes an architecture overview and the detailed procedure how to establish the shared key between the UICC and the terminal.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.110V7.3.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/33/A33110-730.pdf |
+| CCSA | CCSA-TSD-133 110 | 7.3.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 133 110 | 7.3.0 | Published | 2007-10-15 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TS/SGS-0333110v730 |
+| ATIS | ATIS.3GPP.33.110V730-2007 | 7.3.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-33.110(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-33.110(R7-7.2.0).zip |
+
+### 10.11.7 TS 33.141 Presence service; Security
+
+The present document is the Stage 2 specification for the security requirements, security architecture, security features and security mechanisms for the presence service, which includes the elements necessary to realize the requirements in 3G TS 22.141 and 3G TS 23.141. As far as SIP-based procedures are concerned, this specification refers to 3G TS 33.203. The main content of this specification is the security for the Ut reference point, which is HTTP based, as applied in presence services.
+
+The present document includes information applicable to network operators, service providers and manufacturers.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.141V7.1.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/33/A33141-710.pdf |
+| CCSA | CCSA-TSD-133 141 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 133 141 | 7.1.0 | Published | 2006-07-25 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TS/SGS-0333141v710 |
+| ATIS | ATIS.3GPP.33.141V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-33.141(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-33.141(R7-7.1.0).zip |
+
+#### 10.11.8 TS 33.203 3G security; Access security for IP-based services
+
+The scope for this technical specification is to specify the security features and mechanisms for secure access to the IM subsystem (IMS) for the 3G mobile telecommunication system.
+
+The IMS in UMTS will support IP multimedia applications such as video, audio and multimedia conferences. Session initiation protocol (SIP [IETF RFC 3261]) has been chosen as the signalling protocol for creating and terminating multimedia sessions. This specification only deals with how the SIP signalling is protected between the subscriber and the IMS, how the subscriber is authenticated and how the subscriber authenticates the IMS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.203V7.7.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/33/A33203-770.pdf |
+| CCSA | CCSA-TSD-133 203 | 7.7.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 133 203 | 7.7.0 | Published | 2007-10-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TS/SGS-0333203v770 |
+| ATIS | ATIS.3GPP.33.203V770-2007 | 7.7.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-33.203(R7-7.5.0) | 7.5.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-33.203(R7-7.5.0).zip |
+
+#### 10.11.9 TS 33.204 3G Security; Network domain security (NDS); Transaction capabilities application part (TCAP) user security
+
+This technical specification covers the security mechanisms and procedures necessary to protect all TCAP user messages which are sent between different security domains. The complete set of enhancements and extensions to facilitate security protection for the TCAP protocol is termed
+
+TCAPsec and it covers transport security in the TCAP protocol itself and the security management procedures.
+
+This technical specification contains the stage 2 specification for security protection of the TCAP protocol. The actual implementation (stage 3) specification can be found in TS 29.204.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-133 204 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 133 204 | 7.2.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0333204v720 |
+| ATIS | ATIS.3GPP.33.204V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-33.204(R7-7.2.0) | 7.2.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-33.204(R7-7.2.0).zip |
+| TTC | TS-3GA-33.204(Rel7)v7.2.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/ts/ts33204rel7v720.pdf |
+
+#### 10.11.10 TS 33.210 3G security; Network domain security (NDS); IP network layer security
+
+This document defines the security architecture for the UMTS network domain IP-based control plane. The scope of the UMTS network domain control plane security is to cover the control signalling on selected interfaces between UMTS network elements.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.210V7.3.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/33/A33210-730.pdf |
+| CCSA | CCSA-TSD-133 210 | 7.3.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 133 210 | 7.3.0 | Published | 2007-10-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333210v730 |
+| ATIS | ATIS.3GPP.33.210V730-2007 | 7.3.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-33.210(R7-7.3.0) | 7.3.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-33.210(R7-7.3.0).zip |
+
+#### 10.11.11 TS 33.220 Generic authentication architecture (GAA); Generic bootstrapping architecture
+
+The present document describes the security features and a mechanism to bootstrap authentication and key agreement for application security from the 3GPP AKA mechanism. Candidate applications to use this bootstrapping mechanism include, but are not restricted to, subscriber certificate distribution 3GPP TS 33.221. Subscriber certificates support services whose provision mobile operator assists, as well as services that mobile operator provides.
+
+The scope of this specification includes a generic AKA bootstrapping function, an architecture overview and the detailed procedure how to bootstrap the credential.
+
+Clause 4 of this specification describes a mechanism, called GBA\_ME, to bootstrap authentication and key agreement, which does not require any changes to the UICC. Clause 5 of this specification describes a mechanism, called GBA\_U, to bootstrap authentication and key agreement, which does require changes to the UICC, but provides enhanced security by storing certain derived keys on the UICC.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.220V7.9.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/33/A33220-790.pdf |
+| CCSA | CCSA-TSD-133 220 | 7.9.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 133 220 | 7.9.0 | Published | 2007-10-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333220v790 |
+| ATIS | ATIS.3GPP.33.220V790-2007 | 7.9.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-33.220(R7-7.7.0) | 7.7.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stdfile/TTAT.3G-33.220(R7-7.7.0).zip |
+
+#### **10.11.12 TS 33.221 Generic authentication architecture (GAA); Support for subscriber certificates**
+
+The present document describes subscriber certificate distribution by means of generic bootstrapping architecture (GBA) 3GPP TS 33.220. Subscriber certificates support services whose provision the mobile operator assists, as well as services that are offered by the mobile operator.
+
+The scope of this specification presents signalling procedures for support of issuing certificates to subscribers and the standard format of certificates and digital signatures. It is not intended to duplicate existing standards being developed by other groups on these topics, and will reference these where appropriate.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.221V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/33/A33221-700.pdf |
+| CCSA | CCSA-TSD-133 221 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 133 221 | 7.0.0 | Published | 2007-06-25 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333221v700 |
+| ATIS | ATIS.3GPP.33.221V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-33.221(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-33.221(R7-7.0.0).zip |
+
+### 10.11.13 TS 33.222 Generic authentication architecture (GAA); Access to network application functions using hypertext transfer protocol over transport layer security (HTTPS)
+
+The present document specifies secure access methods to network application functions (NAFs) using HTTP over TLS in the generic authentication architecture (GAA), and provides Stage 2 security requirements, principles and procedures for the access. The present document describes both direct access to an application server (AS) and access to an application server through an authentication proxy (AP).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.222V7.2.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/33/A33222-720.pdf |
+| CCSA | CCSA-TSD-133 222 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 133 222 | 7.2.0 | Published | 2006-10-20 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333222v720 |
+| ATIS | ATIS.3GPP.33.222V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-33.222(R7-7.3.0) | 7.3.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-33.222(R7-7.3.0).zip |
+
+### 10.11.14 TS 33.234 3G Security; Wireless local area network (WLAN) interworking security
+
+The present document specifies the security architecture, trust model and security requirements for the interworking of the 3GPP System and WLAN access networks.
+
+Specifications of the appropriate mechanisms for user and network authentication, key management, service authorization, confidentiality and integrity protection of user and signalling data are also provided.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.234V7.5.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/33/A33234-750.pdf |
+| CCSA | CCSA-TSD-133 234 | 7.5.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 133 234 | 7.5.0 | Published | 2007-06-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333234v750 |
+| ATIS | ATIS.3GPP.33.234V750-2007 | 7.5.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-33.234(R7-7.5.0) | 7.5.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-33.234(R7-7.5.0).zip |
+
+#### 10.11.15 TS 33.246 3G security; Security of multimedia broadcast/multicast service
+
+The Technical Specification covers the security procedures of the multimedia broadcast/multicast service (MBMS) for 3GPP systems (UTRAN and GERAN). MBMS is a 3GPP system network bearer service over which many different applications could be carried. The actual method of protection may vary depending on the type of MBMS application.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.246V7.5.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/33/A33246-750.pdf |
+| CCSA | CCSA-TSD-133 246 | 7.5.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 133 246 | 7.5.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333246v750 |
+| ATIS | ATIS.3GPP.33.246V750-2007 | 7.5.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-33.246(R7-7.3.0) | 7.3.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-33.246(R7-7.3.0).zip |
+
+#### 10.11.16 TS 33.259 Key establishment between a UICC hosting device and a remote device
+
+The present document describes the security features and mechanisms to provision a shared key between a UICC hosting device and a remote device connected via a local interface. The shared secret is then intended to be used to secure the interface between the remote device and the UICC hosting device. Candidate applications to use this key establishment mechanism include, but are not restricted to personal network management (see TS 22.259).
+
+The scope of this specification includes an architecture overview and the detailed procedure how to establish the shared key between the UICC hosting device and the remote device. This is different from Technical Specification TS 33.110 that describes an architecture overview and the detailed procedure how to establish the shared key between the UICC itself and the terminal hosting the
+
+UICC. The use cases utilizing the mechanisms described in this specification are seen to be different to the use cases where "Key establishment between a UICC and a terminal", IETF RFC 4279 is utilized.
+
+The solution described in this document is built on the existing infrastructure defined in "GBA", TS 33.220.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.259V7.1.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/33/A33259-710.pdf |
+| CCSA | CCSA-TSD-133 259 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 133 259 | 7.1.0 | Published | 2007-10-16 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333259v710 |
+| ATIS | ATIS.3GPP.33.259V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-33.259(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-33.259(R7-7.0.0).zip |
+
+#### 10.11.17 TS 33.310 Network Domain Security (NDS); Authentication Framework (AF)
+
+For 3GPP systems, there is a need for truly scalable entity authentication framework (AF) since an increasing number of network elements and interfaces are covered by security mechanisms.
+
+This specification provides a highly scalable entity authentication framework for 3GPP network nodes. This framework is developed in the context of the network domain security work item, which effectively limits the scope to the control plane entities of the core network. Thus, *the Authentication Framework will provide entity authentication for the nodes that are using NDS/IP.*
+
+Feasible trust models (i.e., how CAs are organized) and their effects are provided. Additionally, requirements are presented for the used protocols and certificate profiles, to make it possible for operator IPsec and PKI implementations to interoperate.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.310V7.1.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/33/A33310-710.pdf |
+| CCSA | CCSA-TSD-133 310 | 7.1.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 133 310 | 7.1.0 | Published | 2006-10-20 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333310v710 |
+| ATIS | ATIS.3GPP.33.310V710-2007 | 7.1.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-33.310(R7-7.1.0) | 7.1.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-33.310(R7-7.1.0).zip |
+
+### 10.11.18 TR 33.905 Recommendations for trusted open platforms
+
+This technical report investigates relevant trust standards and technologies, both existing as well as the ones that are work-in-progress. It develops the recommendations for trusted open platforms for delivery of new applications and services to open platforms.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-133 905 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 133 905 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=DTR/TSGS-0333905v700 |
+| ATIS | ATIS.3GPP.33.905V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTC | TR-3GA-33.905(Rel7)v7.0.0 | 1 | TTC Published | 2008-03-31 | http://www.ttc.or.jp/imt2000/tr/tr33905rel7v700.pdf |
+
+### 10.11.19 TR 33.918 Generic authentication architecture (GAA); Early implementation of hypertext transfer protocol over transport layer security (HTTPS) connection between a universal integrated circuit card (UICC) and a network application function (NAF)
+
+The present document gives guidance on how to perform an early implementation of HTTPS connections between a UICC-based application and a network application function in the generic authentication architecture (GAA).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-33.918V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/33/A33918-700.pdf |
+| CCSA | CCSA-TSD-133 918 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 133 918 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=DTR/TSGS-0333918v700 |
+| ATIS | ATIS.3GPP.33.918V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.11.20 TR 33.919 3G Security; Generic authentication architecture (GAA); System description
+
+This 3GPP Technical Report aims to give an overview of the different mechanisms that mobile applications can rely upon for authentication between server and client (i.e., the UE). Additionally, it provides guidelines related to the use of GAA and to the choice of authentication mechanism in a given situation and for a given application.
+
+To this end, the TR puts the different GAA specifications that are related to peer authentication into perspective. It clarifies the logic for having three technical specifications, sketches their content and explains the interrelation between these three TSs and their relation with this TR.
+
+
+
+Diagram showing the relationships between GAA specifications and the protocols used by GAA interfaces. The diagram is a hierarchical table. The top row is 'GAA System Description TR 33.919'. Below it, 'GAA GBA TS 33.220' is split into two columns: 'GAA Ub & Ua TS 24.109' and 'GAA Zh and Zn TS 29.109'. To the left of these, 'GAA SSC 33.221' and 'GAA HTTPS TS 33.222' are grouped under 'Interfaces and specifications'. Below the top row, the interfaces 'Ua', 'Ub', 'Zh', and 'Zn' are listed. Under 'Ua' is 'HTTP Digest RFC 2617 (Note)'. Under 'Ub' is 'HTTP Digest AKA RFC 3310'. Under 'Zh' and 'Zn' is 'IMS Cx Diameter message definitions TS 29.229'. Below these are protocol layers: 'HTTP' (under Ua, Ub), 'Diameter Base Protocol RFC 3588' (under Zh, Zn), 'TCP' (under Ua, Ub), 'SCTP' (under Zh, Zn), and 'IP' at the base.
+
+Q.1741.5(08)\_F10.11.20-1
+
+NOTE – The GAA supports potentially many protocols on the Ua interface. One example is the HTTP digest.
+
+**Figure 10.11.20-1 – Relationships between GAA specifications and the protocols used by GAA interfaces**
+
+Figure 10.11.20-1 depicts protocols used over GAA interfaces and the relationships between different GAA specifications. New GAA specifications will be added to the figure as they become available. Also, other protocols may be added in the future. In particular, new kinds of Ua interfaces could be added in the future and then other protocols may be added below the Ua interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-33.919V7.2.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/33/A33919-720.pdf |
+| CCSA | CCSA-TSD-133 919 | 7.2.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 133 919 | 7.2.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0333919v720 |
+| ATIS | ATIS.3GPP.33.919V720-2007 | 7.2.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.11.21 TR 33.920 SIM card based generic bootstrapping architecture (GBA); Early implementation feature
+
+The present document describes which change requests are to be implemented in addition to the Release 6 specifications TS 33.220, TS 29.109, and TS 24.109 to enable the usage of 2G GBA.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-33.920V7.3.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/33/A33920-730.pdf |
+| CCSA | CCSA-TSD-133 920 | 7.3.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 133 920 | 7.3.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0333920v730 |
+| ATIS | ATIS.3GPP.33.920V730-2007 | 7.3.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.11.22 TR 33.978 Security aspects of early IP multimedia subsystem (IMS)
+
+The present document documents an interim security solution for early IMS implementations that are not fully compliant with the IMS security architecture specified in TS 33.203. For security reasons, the provisions in this TR only apply to IMS procedures used over the 3GPP PS domain.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-33.978V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/33/A33978-700.pdf |
+| CCSA | CCSA-TSD-133 978 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 133 978 | 7.0.0 | Published | 2007-06-25 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0333978v700 |
+| ATIS | ATIS.3GPP.33.978V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+### 10.11.23 TR 33.980 Liberty alliance and 3GPP security interworking; Interworking of liberty alliance identity federation framework (ID-FF), Identity web services framework (ID-WSF) and generic authentication architecture (GAA)
+
+The present document provides guidelines on the interworking of the generic authentication architecture (GAA) and the liberty alliance architecture. The document studies the details of possible interworking methods between the security assertion markup language v2.0, SAML v2.0 (or alternatively the liberty alliance identity federation framework, ID-FF), the identity web services framework (ID-WSF), the security assertion markup language (SAML) and a component of GAA called the generic bootstrapping architecture (GBA). This document only applies if liberty alliance and GBA or SAML v2.0 and GBA are used in combination.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-33.980V7.6.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/33/A33980-760.pdf |
+| CCSA | CCSA-TSD-133 980 | 7.6.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 133 980 | 7.6.0 | Published | 2007-10-24 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0333980v760 |
+| ATIS | ATIS.3GPP.33.980V760-2007 | 7.6.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+## 10.12 35-series, Algorithm specifications
+
+### 10.12.1 TS 35.201 Specification of the 3GPP confidentiality and integrity algorithms; Document 1: *f8* and *f9* specifications
+
+This specification gives a detailed specification of the confidentiality algorithm *f8*, and the integrity algorithm *f9*.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-35.201V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/35/A35201-700.pdf |
+| CCSA | CCSA-TSD-135 201 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 135 201 | 7.0.0 | Published | 2007-06-22 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0335201v700 |
+| ATIS | ATIS.3GPP.35.201V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TS 135 201 | 7.0.0 | Published | 2007-06-22 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0335201v700 |
+
+### 10.12.2 TS 35.202 Specification of the 3GPP confidentiality and integrity algorithms; Document 2: Kasumi specification
+
+This specification gives a detailed specification of the Algorithm KASUMI. KASUMI is a block cipher that forms the heart of the confidentiality algorithm *f8*, and the integrity algorithm *f9*.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-35.202V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/35/A35202-700.pdf |
+| CCSA | CCSA-TSD-135 202 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 135 202 | 7.0.0 | Published | 2007-06-22 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0335202v700 |
+| ATIS | ATIS.3GPP.35.202V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-35.202(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-35.202(R7-7.0.0).zip |
+
+### 10.12.3 TS 35.203 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 3: Implementors' test data
+
+This document is the third of four, which between them form the entire specification of the 3GPP confidentiality and integrity algorithms: 3G TS 35.201, 3G TS 35.202, 3G TS 35.203, 3G TS 35.204.
+
+This specification gives detailed test data for implementors of the algorithm set. It provides visibility of the internal state of the algorithm to aid in the realization of the algorithms.
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|--------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-35.203(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-35.203(R7-7.0.0).zip |
+
+### 10.12.4 TS 35.204 Specification of the 3GPP confidentiality and integrity algorithms; Document 4: Design conformance test data
+
+This specification gives black-box test data for the algorithm set. The test data has been selected to give a high degree of confidence that the implementation is correct. However, no claim is made that conformance with this test data guarantees a correct implementation.
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|--------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-35.204(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-35.204(R7-7.0.0).zip |
+
+### 10.12.5 TS 35.205 3G security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions $f1, f1^*, f2, f3, f4, f5$ and $f5^*$ ; Document 1: General
+
+This report is a description of the work undertaken by an ETSI SAGE Task Force on the design of the Milenage algorithm set: an example set of authentication and key generation functions.
+
+The authentication and key generation functions are not standardized. An example set of these algorithms has been produced with the intent that it shall be offered to the UMTS operators, to utilize instead of developing their own. An ETSI SAGE Task Force has carried out this work.
+
+The requirement specification stated that operator personalization of the example set must be possible and that the basic Kernel must be possible to replace.
+
+The example set is based on the block cipher Rijndael, which at the time was one of the AES candidates and the specification describes how the seven algorithms used in 3GPP authentication and key generation are scheduled around this basic Kernel. The specification and associated test data for the example algorithm set is documented in three documents:
+
+- A formal specification of both the modes and the example Kernel TS 35.206;
+- A detailed test data document, covering modes and the example Kernel TS 35.207;
+- A "black box" test data document TS 35.208.
+
+This report gives an overview of the overall work by the task force.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-135 205 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/technical/les.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 135 205 | 7.0.0 | Published | 2007-06-22 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0335205v700 |
+| ATIS | ATIS.3GPP.35.205V 700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-35.205(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-35.205(R7-7.0.0).zip |
+
+#### **10.12.6 TS 35.206 3G security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ ; Document 2: Algorithm specification**
+
+This document contains an example set of algorithms which may be used as the authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ . (It is not mandatory that the particular algorithms specified in this document are used – all seven functions are operator-specifiable rather than being fully standardized.)
+
+The algorithms specified in this document are examples that may be used by an operator who does not wish to design his own.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-135 206 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 135 206 | 7.0.0 | Published | 2007-06-22 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0335206v700 |
+| ATIS | ATIS.3GPP.35.206V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-35.206(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-35.206(R7-7.0.0).zip |
+
+**10.12.7 TS 35.207 3G security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ ; Document 3: Implementors' test data**
+
+This document contains an example set of algorithms which may be used as the authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ . (It is not mandatory that the particular algorithms specified in this document are used – all seven functions are operator-specifiable rather than being fully standardized.) This document is one of five, which between them form the entire specification of the example algorithms: 3G TS 35.205, 3G TS 35.206, 3G TS 35.207, 3G TS 35.208, 3G TS 35.209.
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|--------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-35.207(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-35.207(R7-7.0.0).zip |
+
+**10.12.8 TS 35.208 3G security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ ; Document 4: Design conformance test data**
+
+This document contains an example set of algorithms which may be used as the authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ . (It is not mandatory that the particular algorithms specified in this document are used – all seven functions are operator-specifiable rather than being fully standardized.)
+
+The algorithms specified in this document are examples that may be used by an operator who does not wish to design his own.
+
+For each of the algorithms, the test data sets have been selected such that, provided the entire set of tests is run:
+
+- each input bit of the Rijndael Kernel function will have been in both the '0' and '1' states;
+- each input bit of the modes (RAND, K, SQN, AMF) will have been in both the '0' and '1' states;
+- every S-Box entry of the Rijndael Kernel function will have been used.
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|--------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-35.208(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-35.208(R7-7.0.0).zip |
+
+#### 10.12.9 TS 35.215 Specification of the 3GPP confidentiality and integrity algorithms UEA2 & UIA2; Document 1: UEA2 and UIA2 specifications
+
+This document specifies the 3GPP confidentiality and integrity algorithms known as UEA2 and UIA2.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-35.215V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/35/A35215-700.pdf |
+| CCSA | CCSA-TSD-135 215 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 135 215 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0335215v700 |
+| ATIS | ATIS.3GPP.35.215V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-35.215(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-35.215(R7-7.0.0).zip |
+
+#### 10.12.10 TS 35.216 Specification of the 3GPP confidentiality and integrity algorithms UEA2 & UIA2; Document 2: SNOW 3G specification
+
+This document specifies the 3GPP confidentiality and integrity algorithms known as UEA2 and UIA2.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-35.216V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/2_T63/ARIB-STD-T63/Rel7/35/A35216-700.pdf |
+| CCSA | CCSA-TSD-135 216 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TS 135 216 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0335216v700 |
+| ATIS | ATIS.3GPP.35.216V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+| TTA | TTAT.3G-35.216(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-35.216(R7-7.0.0).zip |
+
+**10.12.11 TS 35.217 Specification of the 3GPP confidentiality and integrity algorithms UEA2 & UIA2; Document 3: Implementors' test data**
+
+This document specifies the 3GPP confidentiality and integrity algorithms known as UEA2 and UIA2.
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|--------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-35.217(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-35.217(R7-7.0.0).zip |
+
+**10.12.12 TS 35.218 Specification of the 3GPP confidentiality and integrity algorithms UEA2 & UIA2; Document 4: Design conformance test data**
+
+This document specifies the 3GPP confidentiality and integrity algorithms known as UEA2 and UIA2.
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|--------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-35.218(R7-7.0.0) | 7.0.0 | Approved | 2008-04-09 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-35.218(R7-7.0.0).zip |
+
+**10.12.13 TR 35.909 3G security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions $f_1, f_1^*, f_2, f_3, f_4, f_5$ and $f_5^*$ ; Document 5: Summary and results of design and evaluation**
+
+This report contains a detailed summary of the work performed during the design and evaluation of the 3G authentication functions denoted as the MILENAGE algorithm set.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-135 909 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 135 909 | 7.0.0 | Published | 2007-06-25 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0335909v700 |
+| ATIS | ATIS.3GPP.35.909V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+**10.12.14 TR 35.919 Specification of the 3GPP confidentiality and integrity algorithms UEA2 & UIA2; Document 5: Design and evaluation report**
+
+This document specifies the 3GPP confidentiality and integrity algorithms known as UEA2 and UIA2.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|-----------------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-35.919V7.0.0 | 6.40 | ARIB published | 2007-12-12 | http://www.arib.or.jp/IMT-2000/V640Dec07/3_T12/ARIB-TR-T12/Rel7/35/A35919-700.pdf |
+| CCSA | CCSA-TSD-135 919 | 7.0.0 | Approved | 2007-12-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-5/ |
+| ETSI | TR 135 919 | 7.0.0 | Published | 2007-07-23 | http://pda.etsi.org/pda/home.asp?wkr=DTR/TSGS-0335919v700 |
+| ATIS | ATIS.3GPP.35.919V700-2007 | 7.0.0 | ATIS Specification Approved | 2007-11-09 | https://www.atis.org/docstore/search.aspx |
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|---------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/01e00200a536673d6cd0e6d8705047a0_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/01e00200a536673d6cd0e6d8705047a0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..305b88183bcb7007cd6073e81ed2a965e74072ce
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/01e00200a536673d6cd0e6d8705047a0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e214b3ff2993feca861bcb896ceea4468708a7d2929015e5f20373baa46d6601
+size 14500
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/052543d8c9c0643b05b3ce45c6decca1_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/052543d8c9c0643b05b3ce45c6decca1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8cf798f18367718adb1716921db073b3600e8ff7
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/052543d8c9c0643b05b3ce45c6decca1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c02591b6a969e8357980575c46b89b87394c32dcdf20e31662811d634a60560
+size 26876
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fb0de9cdc038e99d0ae921bf97ca6ef699765efc
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0db03a18ac661d60f9887c2ed8b986ec3883ce85933f7a0763f63fedc0317435
+size 64658
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e4173651acfa8e8edf21330e157af382ca744e85
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c4f795181939f9b15b776cf9de90cc6390ec53ed0b329c01c202349b1b35aead
+size 42173
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/187d05bf7ead21e1394b61320d8b3632_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..59c52e5dd0d3fb0f4a587ad3ec781a8ce1358e91
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/187d05bf7ead21e1394b61320d8b3632_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:687dffca3dd71df8aacbbd330674fd6ab4f4074e2e0656fb515c9c0c9ed59891
+size 44034
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/1ce027dfd26183da52137cf990213724_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/1ce027dfd26183da52137cf990213724_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e740866d6daaa265ab84dbd63ee8411636693cb2
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/1ce027dfd26183da52137cf990213724_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f845fbdd992add5b57f143f32225980526d488740abc08c6b95337bc93698021
+size 6399
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b2511b82b7f822b0bdec11933825afd4aebdc902
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:44621a98b4d2dd2132a703f614c99a53c44bfa4cca73740b635b4bf1c64e6beb
+size 37806
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/2bd7e953f08179f9f531cc7a04c418e2_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/2bd7e953f08179f9f531cc7a04c418e2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1779bdf75eb6468542b02e959a1a8b4d77bbc509
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/2bd7e953f08179f9f531cc7a04c418e2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4dc1b306defaa9a912d88125e92b59df0c6dcaae5be77b6fbbbe6af15a4f2229
+size 40370
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2a803492c4d8580404c2c1edac7480d7aad2adba
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5c617fde3827302110f819b268db0f7d47b347e7396e95f7a7c735c137a01c2f
+size 17521
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..27fd40c71bb69a9080ea9590bb26d01ea600aa76
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7977fc09a01898f1d9fa2b9ce0144b738a3a51a9c313368255e21503a1a8372a
+size 43876
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/41aef1f5efab13d4f38f69e86c726062_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/41aef1f5efab13d4f38f69e86c726062_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7d96158cc1098a327ebcde8a5061a403c6ad4638
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/41aef1f5efab13d4f38f69e86c726062_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:53263a4b8958fdbaaa84fc0f238463ed895aa443a669f8e33357215965a56d94
+size 34005
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/458fdbcb4015a4ee90bd84809afc4aac_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/458fdbcb4015a4ee90bd84809afc4aac_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..52b19bc609c234f5d4994b5ece78bc94c5108ed1
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/458fdbcb4015a4ee90bd84809afc4aac_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c8c9f201846d05f77af2d0a7eb2e76c106580f7c3bd4545aec90f09090e73637
+size 27064
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/508bc574df81fa8d3027a374f6d155fc_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/508bc574df81fa8d3027a374f6d155fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8cfb257051de8b739791edefa87811b04c474001
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/508bc574df81fa8d3027a374f6d155fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9c88ba25087690acc638b5a9da8594dd9b830d766171bba93aac1f9561929981
+size 38050
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/5c3dd31372f59e15250f0ab1613ca485_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/5c3dd31372f59e15250f0ab1613ca485_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..faa588c8b6ceafe3b2c4d4fcfffad0176f4dc711
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/5c3dd31372f59e15250f0ab1613ca485_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:13631e5152e9e98e1506c2c8dfb2f7e053a60a33e000ebf4c7d1283cc5f96936
+size 61533
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/64aba6d3bacc69b7b90f08e02f2d5efe_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/64aba6d3bacc69b7b90f08e02f2d5efe_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f487f919c01d72ea1eae0eb8c73e43a9bb3681d5
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/64aba6d3bacc69b7b90f08e02f2d5efe_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:30bcb11037110a09c11b59740238561ba1391c3bd342b28b608f792042a21d91
+size 31488
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/65e8c0628536d6d4245e9ab46ba070c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7c6f57632034ccdee77253078671a1719fda2e42
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/65e8c0628536d6d4245e9ab46ba070c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:486e4f2587cf65a7a48d5b807c6e48d90e4366d28957006a8c416dd91762bf21
+size 38423
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/705f1de6c782e844714a323bda22ecd9_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/705f1de6c782e844714a323bda22ecd9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e6bc7301f34fb271aa49d2b9a4c81b728fd89f68
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/705f1de6c782e844714a323bda22ecd9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:45cd6b4be9f415a87ccb20924029df0197e93a0cdffd4d62332a7717bd7ff856
+size 72189
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..db06b3d23dd8e07f0962255289eb20c5b8ad4f32
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4c2dd9e297b16203737a9c3035acd60987ff97149f526e1b3b60f95d76248bfe
+size 38417
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..84f397a92c0807a1a388f845fc769668326985c0
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4b1f3ad74f3b19fc07c522aa32a77690331338cbd433db7cea4d9955f7f6b184
+size 26775
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/75a51aa7d7e96605567cc8bde2ee2999_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/75a51aa7d7e96605567cc8bde2ee2999_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..74ada0e8db286b40f52e2b5429bad87e6ab7a9eb
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/75a51aa7d7e96605567cc8bde2ee2999_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c6e6970b73f49f3f8c34008ba8e0763438c984df9d98ba0e6b56164b0af5682f
+size 22255
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/772cc583a60eeb058cc19de48269ad22_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/772cc583a60eeb058cc19de48269ad22_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..09e6fa81d66ea4696c59e6a72bb7edf5981aef50
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/772cc583a60eeb058cc19de48269ad22_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2811802f2c0c6fdbd5e8b0c184cfec83beb101a7479e8f7ae967a4fcb0ea740
+size 20262
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/789ee0a267b24f34bd1f45313e86c9a4_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/789ee0a267b24f34bd1f45313e86c9a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ea2b45a8b482deffe50fbc249eb5dadd54c47e54
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/789ee0a267b24f34bd1f45313e86c9a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a784cb04bc623d1498965ca26477d0f79d9450b8725dcf6eadb212deb67de71b
+size 51436
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/79e37b4f8cee1318b5ed68e32a2f12a4_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/79e37b4f8cee1318b5ed68e32a2f12a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2e5c741e92a8d5e1df3a7744b10af5c7b52fc745
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/79e37b4f8cee1318b5ed68e32a2f12a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bfa1946340d147bc2f759003b4215b31422147289d2b7511e2195cdfd1f6db41
+size 50441
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a8073c3055abc7731de1ae66c36e362f11443a0c
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4b4de5adc1d3cdb5e156cd79f5bd52f6701f25e443a1f8d3f0d1dce155ed63f9
+size 7472
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/8bd7adf738ea4b7e65e0d6f67e122d55_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/8bd7adf738ea4b7e65e0d6f67e122d55_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..914c31714d21216e132157f7f6b214b28cfe6a2d
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/8bd7adf738ea4b7e65e0d6f67e122d55_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8f8ac33e440afc748cc66b6523f129e1616c3759b5cdc3d9bf2cb01c9602201e
+size 85571
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0e3ba70355817cfc44f25c0ad29ee02dc3c8100e
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:68ba99a34f1862ed6db44b8c13dc20af6fd226ebf39eecfb0630d89a4b834bff
+size 40707
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/a5184899f915014fa38608754efcc9c7_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/a5184899f915014fa38608754efcc9c7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7939043954c696f6850a548cfc18526775232389
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/a5184899f915014fa38608754efcc9c7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1a3d532dc361b1691364939aaab608545d4039693a1497caf6503c05e99a49ad
+size 15602
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/aaf6dd7cde178eb3915671de6c6d8ad3_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/aaf6dd7cde178eb3915671de6c6d8ad3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8850d20be85f8e2b41a4208361b13c6e0daac781
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/aaf6dd7cde178eb3915671de6c6d8ad3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3c5eae9e18b46579dcc94c31b71652893e61c2c167b556f8bfff369462f2a8cc
+size 60798
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/ac5084f644988289daf6c0a519f232ba_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/ac5084f644988289daf6c0a519f232ba_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..20ccf5fc5a1bd9bf88d7853d3e5b0b6d1c9a924e
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/ac5084f644988289daf6c0a519f232ba_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9f517e6aaecef34b94d24af913a86c0fb68fcfc11a9b0225d0065846a1f05ee6
+size 24915
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/b9c0d46c1148cf65cb79f27fac420981_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/b9c0d46c1148cf65cb79f27fac420981_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9298650af5b43ef7006d06deb85d685ac836d20d
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/b9c0d46c1148cf65cb79f27fac420981_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:09e98addd37ae6d9b18732ed07631394a76f1cddc7443b65d21551bac10efadd
+size 100323
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/bbf92fa724597efff9a7b4625ec54041_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/bbf92fa724597efff9a7b4625ec54041_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6a2fba4a4b1a2f5db882ccedb6f3d6f5b1761df6
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/bbf92fa724597efff9a7b4625ec54041_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:299efe22cd33e57e04d0b00c25eb02747c86847cb49fe104fc148500b7a807df
+size 14114
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..40b5fec58618b24132ba8cfbdefefcd13be5c9cf
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:530d58443ddecfee4051cc80c5a10d310e93897f0a7dbd17d33f8edab220b2c0
+size 47469
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/c1278da91cbcabe32628e589ebc47418_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/c1278da91cbcabe32628e589ebc47418_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ee3fab4cc6715d04b6dd9465f1fba2393808fe09
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/c1278da91cbcabe32628e589ebc47418_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1a3e9b7885f466757a57c2b4bc1cffb481665aae6c32591f66cf539e19c6a195
+size 54019
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5136c804452ac91e583d0783794b47abcada8aac
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a528e3c1698341b9a9ce699c51a5392c9eb54f8764cfb715ac6e0448fd75eaae
+size 86030
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..247c28947cdb6d0a6a83366f2ce6ce285f57d149
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3bfe7227785f591f20f0635104d1e80f1a3a3185e8295170045b3d2d4f5b30aa
+size 127437
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/d9862ac8473902e7dfe441c5e88d47d8_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/d9862ac8473902e7dfe441c5e88d47d8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..599b48852f323757ceb884934bc4ac2a2757d5e2
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/d9862ac8473902e7dfe441c5e88d47d8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a0ffe19eb5bae76bafcf013fb48237517da9710871a51768b0c61e93a95fa124
+size 71913
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/da308c919c2b05d507cd6eb4dc7c00f9_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/da308c919c2b05d507cd6eb4dc7c00f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..908e4584bc499d961f5787efbae408bb9a4dd59d
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/da308c919c2b05d507cd6eb4dc7c00f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5f992e4186d9af4d15e950703691ac8b1d81882971359856f18c988488b2d903
+size 41188
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/e896e0bdda91f258fa9ce577d1264465_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/e896e0bdda91f258fa9ce577d1264465_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9880c837aaaa1a62ccf30be13e46c4dcd17d890f
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/e896e0bdda91f258fa9ce577d1264465_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:84fdc571b394e1f30d4969717b329915da84d0e3f6bb140948d00f562932a1f1
+size 95516
diff --git a/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..08451f84fba7961117f3fa72dda628ac129eace8
--- /dev/null
+++ b/marked/Q/T-REC-Q.1741.6-200910-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7458c8265473dce51f8aaae1fcd40ce33a8dc46374162efad44c7b826a0a2843
+size 129556
diff --git a/marked/Q/T-REC-Q.1742.5-200609-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1742.5-200609-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..311d45df9b0c49ae5380c0bfe184d95e5b503fcc
--- /dev/null
+++ b/marked/Q/T-REC-Q.1742.5-200609-I_PDF-E/raw.md
@@ -0,0 +1,3911 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.1742.5**
+
+(09/2006)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Signalling requirements and protocols for IMT-2000
+
+---
+
+**IMT-2000 references (approved as of
+31 December 2005) to ANSI-41 evolved core
+network with cdma2000 access network**
+
+ITU-T Recommendation Q.1742.5
+
+# 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 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## **ITU-T Recommendation Q.1742.5**
+
+# **IMT-2000 references (approved as of 31 December 2005) to ANSI-41 evolved core network with cdma2000 access network**
+
+## **Summary**
+
+This Recommendation associates the published core network standards from the regional standards development organizations (SDOs) with those 3GPP2 specifications that were approved as of 31 December 2005 for the IMT-2000 family member "ANSI-41 evolved Core Network with cdma2000 Access Network".
+
+3GPP2 specifications that were approved as of 17 July 2001 were associated with the published core network standards from the regional standards development organizations in ITU-T Rec. Q.1742.1. 3GPP2 specifications that were approved as of 11 July 2002 were associated with the published core network standards from the regional standards development organizations in ITU-T Rec. Q.1742.2. 3GPP2 specifications that were approved as of 30 June 2003 were associated with the published core network standards from the regional standards development organizations in ITU-T Rec. Q.1742.3. 3GPP2 specifications that were approved as of 30 June 2004 were associated with the published core network standards from the regional standards development organizations in ITU-T Rec. Q.1742.4. 3GPP2 specifications that are approved as of 31 December 2006 will be associated with published core network standards in future ITU-T Rec. Q.1742.6. The radio interface and radio access network and standards from the SDOs for this IMT-2000 Family Member are associated in ITU-R Rec. M.1457-5. The associations for other IMT-2000 family members are identified in the ITU-T Rec. Q.174x series.
+
+This Recommendation combines and associates the regional standards for the core network of this IMT-2000 Family Member into a global Recommendation.
+
+## **Source**
+
+ITU-T Recommendation Q.1742.5 was approved on 13 September 2006 by ITU-T Study Group 19 (2005-2008) under the ITU-T Recommendation A.8 procedure.
+
+## **Keywords**
+
+ANSI-41, cdma2000, core network, IMT-2000, third generation system.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2007
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## CONTENTS
+
+###### Page
+
+| | | |
+|------|---------------------------------------------------------------------------------------------------------|----|
+| 1 | Scope ..... | 1 |
+| 2 | References..... | 1 |
+| 3 | Definitions ..... | 2 |
+| 4 | Abbreviations and acronyms ..... | 5 |
+| 5 | Introduction ..... | 9 |
+| 6 | Basic architecture for the ANSI-41 evolved core network with cdma2000 access network family member..... | 10 |
+| 7 | Network entities..... | 15 |
+| 7.1 | Authentication, Authorization and Accounting (AAA) ..... | 15 |
+| 7.2 | Authentication Centre (AC) ..... | 15 |
+| 7.3 | Call Data Collection Point (CDCP)..... | 15 |
+| 7.4 | Call Data Generation Point (CDGP) ..... | 15 |
+| 7.5 | Call Data Information Source (CDIS)..... | 15 |
+| 7.6 | Call Data Rating Point (CDRP)..... | 16 |
+| 7.7 | Collection Function (CF) – [Intercept]..... | 16 |
+| 7.8 | Coordinate Routing Data Base (CRDB)..... | 16 |
+| 7.9 | Customer Service Centre (CSC)..... | 16 |
+| 7.10 | Delivery Function (DF) – [Intercept] ..... | 16 |
+| 7.11 | Equipment Identity Register (EIR)..... | 16 |
+| 7.12 | Home Agent (HA) ..... | 17 |
+| 7.13 | Home Location Register (HLR) ..... | 17 |
+| 7.14 | Intelligent Peripheral (IP) ..... | 17 |
+| 7.15 | Intercept Access Point (IAP) ..... | 17 |
+| 7.16 | Interworking Function (IWF) ..... | 17 |
+| 7.17 | Local Position Determining Entity (LPDE) ..... | 17 |
+| 7.18 | Managed Wireless Network Entity (MWNE) ..... | 17 |
+| 7.19 | Message Centre (MC)..... | 17 |
+| 7.20 | Mobile Position Centre (MPC)..... | 17 |
+| 7.21 | Mobile Switching Centre (MSC)..... | 18 |
+| 7.22 | Number Portability DataBase (NPDB) ..... | 18 |
+| 7.23 | Over-The-Air Service Provisioning Function (OTAF) ..... | 18 |
+| 7.24 | Packet Data Network (PDN) ..... | 18 |
+| 7.25 | Packet Data Serving Node (PDSN) ..... | 18 |
+| 7.26 | Position Determining Entity (PDE)..... | 18 |
+| 7.27 | Service Control Point (SCP)..... | 18 |
+| 7.28 | Service Node (SN)..... | 18 |
+| 7.29 | Short Message Entity (SME)..... | 18 |
+| 7.30 | Visitor Location Register (VLR)..... | 18 |
+
+| | | Page |
+|------|----------------------------------------------------------|------|
+| 7.31 | Voice Message Centre (VMS)..... | 19 |
+| 7.32 | Wireless Network Entity (WNE)..... | 19 |
+| 7.33 | Access Gateway (AGW) ..... | 19 |
+| 7.34 | Application Server..... | 19 |
+| 7.35 | Authentication, Authorization and Accounting (AAA) ..... | 19 |
+| 7.36 | Border Router (BR) ..... | 19 |
+| 7.37 | Breakout Gateway Control Function (BGCF)..... | 19 |
+| 7.38 | Call Session Control Function (CSCF) ..... | 20 |
+| 7.39 | Databases (DB)..... | 20 |
+| 7.40 | IP Multimedia Client ..... | 20 |
+| 7.41 | IP Network..... | 20 |
+| 7.42 | Media Gateway (MGW)..... | 20 |
+| 7.43 | Media Gateway Control Function (MGCF) ..... | 20 |
+| 7.44 | Media Resource Function Controller (MRFC)..... | 20 |
+| 7.45 | Media Resource Function Processor (MRFP)..... | 20 |
+| 7.46 | Mobile IP Home Agent (HA) ..... | 20 |
+| 7.47 | Mobile Station (MS)..... | 21 |
+| 7.48 | OSA Service Capability Server (OSA-SCS) ..... | 21 |
+| 7.49 | Policy Decision Function (PDF) ..... | 21 |
+| 7.50 | Position Determining Entity (PDE)..... | 21 |
+| 7.51 | Position Server..... | 21 |
+| 7.52 | Public Switched Telephone Network (PSTN)..... | 21 |
+| 8 | Reference Points ..... | 21 |
+| 8.1 | Reference Point B..... | 21 |
+| 8.2 | Reference Point C..... | 21 |
+| 8.3 | Reference Point D..... | 21 |
+| 8.4 | Reference Point d ..... | 22 |
+| 8.5 | Reference Point D 1 ..... | 22 |
+| 8.6 | Reference Point D i ..... | 22 |
+| 8.7 | Reference Point E ..... | 22 |
+| 8.8 | Reference Point E 3 ..... | 22 |
+| 8.9 | Reference Point E 5 ..... | 22 |
+| 8.10 | Reference Point E 9 ..... | 22 |
+| 8.11 | Reference Point E 11 ..... | 22 |
+| 8.12 | Reference Point E 12 ..... | 22 |
+| 8.13 | Reference Point e..... | 22 |
+| 8.14 | Reference Point F ..... | 22 |
+| 8.15 | Reference Point G..... | 22 |
+| 8.16 | Reference Point H..... | 22 |
+| 8.17 | Reference Point I ..... | 22 |
+
+| | Page |
+|-------------------------------------------|------|
+| 8.18 Reference Point J ..... | 23 |
+| 8.19 Reference Point K..... | 23 |
+| 8.20 Reference Point L ..... | 23 |
+| 8.21 Reference Point M 1 ..... | 23 |
+| 8.22 Reference Point M 2 ..... | 23 |
+| 8.23 Reference Point M 3 ..... | 23 |
+| 8.24 Reference Point N..... | 23 |
+| 8.25 Reference Point N 1 ..... | 23 |
+| 8.26 Reference Point O 1 ..... | 23 |
+| 8.27 Reference Point O 2 ..... | 23 |
+| 8.28 Reference Point P i ..... | 23 |
+| 8.29 Reference Point Q..... | 23 |
+| 8.30 Reference Point Q 1 ..... | 23 |
+| 8.31 Reference Point T 1 ..... | 23 |
+| 8.32 Reference Point T 2 ..... | 24 |
+| 8.33 Reference Point T 3 ..... | 24 |
+| 8.34 Reference Point T 4 ..... | 24 |
+| 8.35 Reference Point T 5 ..... | 24 |
+| 8.36 Reference Point T 6 ..... | 24 |
+| 8.37 Reference Point T 7 ..... | 24 |
+| 8.38 Reference Point T 8 ..... | 24 |
+| 8.39 Reference Point T 9 ..... | 24 |
+| 8.40 Reference Point V ..... | 24 |
+| 8.41 Reference Point X..... | 24 |
+| 8.42 Reference Point Y ..... | 24 |
+| 8.43 Reference Point Z ..... | 24 |
+| 8.44 Reference Point Z 1 ..... | 24 |
+| 8.45 Reference Point Z 2 ..... | 24 |
+| 8.46 Reference Point Z 3 ..... | 24 |
+| 8.47 Reference Point 1 ..... | 25 |
+| 8.48 Reference Point 2 ..... | 25 |
+| 8.49 Reference Point 3 ..... | 25 |
+| 8.50 Reference Point 4 ..... | 25 |
+| 8.51 Reference Point 5/Mk..... | 25 |
+| 8.52 Reference Point 6 ..... | 25 |
+| 8.53 Reference Point 7 ..... | 25 |
+| 8.54 Reference Point 8/OSA ..... | 25 |
+| 8.55 Reference Point 9/Mi..... | 25 |
+| 8.56 Reference Point 10 ..... | 25 |
+| 8.57 Reference Point 11/Sh ..... | 26 |
+
+| | | Page |
+|------|-------------------------------|------|
+| 8.58 | Reference Point 12/ISC ..... | 26 |
+| 8.59 | Reference Point 13 ..... | 26 |
+| 8.60 | Reference Point 14 ..... | 26 |
+| 8.61 | Reference Point 15 ..... | 26 |
+| 8.62 | Reference Point 16/Cx..... | 26 |
+| 8.63 | Reference Point 17/(Mg) ..... | 26 |
+| 8.64 | Reference Point 18 ..... | 26 |
+| 8.65 | Reference Point 19 ..... | 26 |
+| 8.66 | Reference Point 20 ..... | 26 |
+| 8.67 | Reference Point 21 ..... | 26 |
+| 8.68 | Reference Point 22 ..... | 26 |
+| 8.69 | Reference Point 23 ..... | 27 |
+| 8.70 | Reference Point 24/Mr ..... | 27 |
+| 8.71 | Reference Point 25/Mp..... | 27 |
+| 8.72 | Reference Point 26/PSTN..... | 27 |
+| 8.73 | Reference Point 27 ..... | 27 |
+| 8.74 | Reference Point 28/Go ..... | 27 |
+| 8.75 | Reference Point 29 ..... | 27 |
+| 8.76 | Reference Point 30/Mc ..... | 27 |
+| 8.77 | Reference Point 31 ..... | 27 |
+| 8.78 | Reference Point 32/Mb..... | 27 |
+| 8.79 | Reference Point 33/Mb..... | 27 |
+| 8.80 | Reference Point 34/Mb..... | 27 |
+| 8.81 | Reference Point 35 ..... | 28 |
+| 8.82 | Reference Point 36/Mb..... | 28 |
+| 8.83 | Reference Point 37/Mb..... | 28 |
+| 8.84 | Reference Point 38/Mb..... | 28 |
+| 8.85 | Reference Point 39 ..... | 28 |
+| 8.86 | Reference Point 40/Mb..... | 28 |
+| 8.87 | Reference Point 41 ..... | 28 |
+| 8.88 | Reference Point 42/Mb..... | 28 |
+| 8.89 | Reference Point 43/Mb..... | 28 |
+| 8.90 | Reference Point 44/Mb..... | 28 |
+| 8.91 | Reference Point 45/Mb..... | 28 |
+| 8.92 | Reference Point 46/Mb..... | 28 |
+| 8.93 | Reference Point 47 ..... | 29 |
+| 8.94 | Reference Point 48 ..... | 29 |
+| 8.95 | Reference Point 49/(Mj) ..... | 29 |
+| 8.96 | Reference Point 50 ..... | 29 |
+
+| | Page |
+|------|-----------------------------------------------------|
+| 9 | Technical specifications structure..... 29 |
+| 10 | Technical specifications..... 30 |
+| 10.1 | A Series RAN specifications ..... 30 |
+| 10.2 | Intersystem Specifications ..... 30 |
+| 10.3 | Packet Data specifications ..... 42 |
+| 10.4 | Services and system aspects specifications ..... 42 |
+| 10.5 | Core Network Specifications..... 81 |
+
+
+
+# **IMT-2000 references (approved as of 31 December 2005) to ANSI-41 evolved core network with cdma2000 access network**
+
+# **1 Scope**
+
+This Recommendation identifies the IMT-2000 family member, "ANSI-41 evolved core network with cdma2000 access network." This set of referenced specifications includes those 3GPP2 specifications that were approved as of 31 December 2005.
+
+The core network interfaces identified in this Recommendation and the radio interfaces and radio access network interfaces identified in ITU-R Rec. M.1457-5 [1] constitute a complete system specification for the 3rd generation mobile system for terrestrial usage of this IMT-2000 family member.
+
+It is the intent of the ITU-T that the references in this Recommendation are only to specifications that specify the network aspects of this IMT-2000 family member. In the event that a referenced specification also includes material that specifies any of the radio aspects of this IMT-2000 family member, ITU-R Rec. M.1457-5 [1], shall take precedence.
+
+# **2 References**
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [1] ITU-R Recommendation M.1457-5 (2006), *Detailed specifications of the radio interfaces of International Mobile Telecommunications-2000 (IMT-2000)*.
+- [2] ANSI/TIA/EIA 41-D (1997), *Cellular Radiotelecommunications Intersystem Operations (ANSI/TIA/EIA-41-D-97)*.
+- [3] ANSI/TIA/EIA 95 (1999), *Mobile Station-Base Station Compatibility Standard for Wideband Spread Spectrum Cellular Systems (ANSI/TIA/EIA-95-B-99)*.
+- [4] ANSI/TIA/EIA 124 (2001), *Wireless Radio Telecommunications Intersystem Non-Signalling Data Communication DMH (Data Message Handler) (ANSI/124-D-2001)*.
+- [5] ANSI/TIA/EIA 136 (2001), *TDMA Cellular PCS (ANSI/TIA/EIA-136, Rev C-2001)*.
+- [6] ANSI/TIA/EIA 553A (1999), *Mobile Station – Base Station Compatibility Standard (ANSI TIA/EIA-553-A-99)*.
+- [7] ANSI/TIA/EIA 664A (2000), *Cellular Features Description (ANSI/TIA/EIA-664-A-2000)*.
+- [8] TIA Specification IS-91 (1999), *Base Station – Mobile Station Compatibility Specification for 800 MHz Cellular, Auxiliary, and Residential Services (TIA/EIA/IS-91-A)*.
+- [9] TIA Specification IS-2000 (2000), *CDMA 2000 Series (TIA/EIA/IS-2000 Series Revision A)*.
+- [10] TIA Specification IS-2001-A (2001), *Interoperability Specifications (IOS) for cdma2000 Access Network Interfaces (TIA/EIA/IS-2001-A)*.
+
+- [11] TIA Specification TSB-29D (2000), *International Implementation of Wireless Telecommunication Systems Compliant with TIA/EIA-41*.
+- [12a] CWTS; CWTS-MC-S.R0005-B (2002), *Network Reference Model for cdma2000 Spread Spectrum Systems*.
+- [12b] TIA; TSB100-A (2001), *Wireless Network Reference Model*.
+- [12c] TTA; TTAE.3G-S.R0005-B (2001), *3GPP2 Network Reference Model for cdma2000 Spread Spectrum Systems*.
+- [12d] TTC; TS-3GB-S.R0005-B v1.0 (2001), *Network Reference Model for cdma2000 Spread Spectrum Systems*.
+- [13a] CWTS; CWTS-MC-N.S0037 (2002), *IP Network Architecture Model for cdma2000 Spread Spectrum Systems*.
+- [13b] TTA; TTAT.3G-S.R0037-0 v3.0 (2003), *IP Network Architecture Model for cdma2000 Spread Spectrum Systems*.
+- [13c] TTC; TS-3GB-S.R0037-0 v3.0 (2003), *IP Network Architecture Model for cdma2000 Spread Spectrum Systems*.
+- [14] TIA/EIA TSB29-E (2002), *International Implementation of Wireless Telecommunication Systems Compliant with TIA/EIA-41*.
+- [15] TIA/EIA/IS-826 (2003), *TIA/EIA-41-D Based Pre-Paid Charging Enhancements for Circuit Switched Data and Short Message (2003)*.
+
+# 3 Definitions
+
+This Recommendation defines the following terms:
+
+**3.1 access denial call treatment:** A tone, announcement, or call redirection applied as appropriate.
+
+**3.2 access network:** Network that connects access technologies (such as a Radio Access Network) to the core network.
+
+**3.3 active:** The MS is available for call delivery. This state is maintained by the MSC, the VLR and the HLR. (See also "available", "inactive" and "unavailable".)
+
+**3.4 adjunct MSC:** A Mobile Switching Centre (MSC) that is providing adjunct services such as voice response, voice recognition, DTMF tone detection, voice message storage, etc.
+
+**3.5 anchor MSC:** The Mobile Switching Centre (MSC), that is the first to assign a traffic channel to a call on origination or termination is called the Anchor MSC. For the duration of this call, this MSC shall be the anchor (fixed) point in the event that the Mobile Station (MS) should be handed off to other MSCs.
+
+**3.6 authentication:** The act of verifying the identity of an entity (e.g., a user, device).
+
+**3.7 available:** The MS can accept a call delivery (i.e., the MS is in a known location and it is in a state able to accept call deliveries). The availability of a MS to accept a call delivery is maintained only by the MSC. (See also "active", "inactive" and "unavailable".)
+
+**3.8 base transceiver station:** A piece of radio access network equipment that contains the radios and serves a geographic area.
+
+**3.9 call delivery:** The process by which calls directed to the cellular subscriber are delivered to the subscriber while roaming in a visited system.
+
+**3.10 call delivery method:** Method by which a call is delivered to a subscriber in MSC-V.
+
+- 3.11 call disconnect:** The process of requesting the release of a connection between two or more network addresses.
+- 3.12 call release:** The process of relinquishing the facilities and circuits used for a call.
+- 3.13 call termination:** The process of connecting a subscriber to an incoming call.
+- 3.14 candidate MSC:** This term is used during the handoff measurement request by the current serving MSC to reference the MSC that is being requested to provide its best CELL ID and SIGNAL QUALITY values.
+- 3.15 cell site:** The physical location of a cell's radio equipment and supporting systems. This term is also used to refer to the equipment located at the cell site.
+- 3.16 clearinghouse:** A service used for the exchange and management of information.
+- 3.17 data communications:** The digital transmission of information (other than voice).
+- 3.18 dialogue:** A user interaction sequence composed of tones and announcements that may gather information.
+- 3.19 gateway MSC:** See MSC-G.
+- 3.20 home system:** The system which is transmitting the System Identifier (SID) (refer to *EIA/TIA-553*) which is recognized by the MS as the "Home" SID.
+- 3.21 inactive:** The MS is not available for call delivery. The MS may not be registered. The MS may be registered, but is out of radio contact (e.g., missing autonomous registrations) or is intentionally inaccessible for periods of time (e.g., slotted mode, paging frame class, or sleep mode). An inactive MS may accept SMS message deliveries. This state is maintained by the MSC, the VLR and the HLR. (See also "active", "available" and "unavailable".)
+- 3.22 market identification (MarketID):** A unique market identifier that is specified by the service provider (e.g., FCC assigned SID, CIBERNET assigned BID – see *TIA/EIA TSB29*).
+- 3.23 mobile assisted handoff (MAHO):** A process where handoff measurements are done by the MS under the control of the MSC and Base Station. The MSC and Base Station retain the control over when the handoff actually occurs.
+- 3.24 mobility:** The ability to access services from any point in the network. The degree of service availability may depend on the access network capabilities, as well as any service level agreements between the user's home network and the visited network. Types of mobility include personal mobility, service mobility, and terminal mobility.
+- 3.25 mobility management:** The set of functions used to manage a mobile user accessing a network other than that user's home network. These functions include communication with the home network for purposes of authentication, authorization, location updating and download of user information.
+- 3.26 MSC-G:** An MSC that is capable of the Intersystem procedures, defined in this Recommendation, between entities in the network reference model so as to provide service.
+- 3.27 MSC-H:** The "home" MSC of an MS which is broadcasting the SID that is recorded in the MS's Security and Identification memory, and to which the MS's Directory Number is assigned.
+- 3.28 MSC-V:** A "visited" MSC in whose service area a roamer is operating.
+- 3.29 network reference model:** The functional entities and the associated interface reference points that may logically comprise a cellular network. (See clause 6.)
+
+- 3.30 number portability:** A mechanism that allows a user to retain the same directory number, regardless of the subscribed-to service provider. Number portability may be limited to specific geographical areas. In the context of the All-IP network, the term "number portability" refers specifically to E.164 numbers used for telephony.
+- 3.31 originating MSC:** The MSC-H or MSC-G that initiates the call delivery procedures defined in this Recommendation.
+- 3.32 originating SMS supplementary service:** Services or features that affect SMS message originations and are requested on a per message basis as supported by a particular teleservice, for example, delayed delivery, or message distribution to a list of destinations.
+- 3.33 personal mobility:** The ability of users to change their association with one or more terminals at any point and time. The user should continue to receive subscribed and otherwise authorized services as supported by the current MS and access network.
+- 3.34 personalized services:** Services that need access to the subscriber profile and/or are dependent on the overall call/session state (of the user) for reasons of service interaction. An example: a call termination service such as TIA/EIA-41's "Call Forward on Busy".
+- 3.35 protocol extension:** A mechanism provided to allow systems with a common bilateral agreement to extend the *TIA/EIA-41* protocol. There is a range of reserved Error Codes, Operation Codes, Parameter Identifiers (in addition to PRIVATE Parameter Identifiers), and ranges of values in enumerated parameter types and data fields. The only mechanism to resolve conflicting uses of protocol extension is to standardize their usage. The Protocol Extension mechanism is used at the risk of the implementation. Protocol Extensions should not be used unless the message recipient is known to support them.
+- 3.36 radio access network:** The network that connects radio base stations to the core network. The RAN provides and maintains radio-specific functions, which may be unique to a given radio access technology, that allow users to access the core network.
+- 3.37 registered:** The HLR has a pointer to a system serving an MS. A registered MS may be active or inactive.
+- 3.38 registration:** The procedure by which a MS becomes listed as being present in the service area of an MSC.
+- 3.39 remote feature control port (RFC port):** A terminating directory number supporting service profile modification.
+- 3.40 roamer port:** A terminating directory number supporting call delivery to mobile stations.
+- 3.41 roamer service profile:** The specific set of features, capabilities and/or operating restrictions, other than financial accountability, associated with the subscriber.
+- 3.42 roamer validation:** That aspect of roamer service qualification dealing with financial accountability. Also, the general procedure by which a roamer's financial accountability is established.
+- 3.43 roaming:** Action whereby users access services while outside of their subscribed home network.
+- 3.44 service qualification:** The service capabilities, features and privileges to which an MS is entitled. Also, the general procedure by which such service capabilities, features, and privileges become established in an MSC.
+- 3.45 serving MSC:** The MSC which currently has the MS obtaining service at one of its cell sites within its coverage area.
+
+- 3.46 signalling:** The information exchanged between the mobile station and the network, or within the network, for the purposes of service provision (e.g., connection establishment).
+- 3.47 switch number (SWNO):** A number uniquely identifying a particular switch (i.e., a group of cell sites and the associated switch resources) within a group of switches associated with a common MarketID.
+- 3.48 target MSC:** The MSC which was selected from the candidate list as having the cell site with the best signal quality value for the MS during the location request function.
+- 3.49 temporary local directory number (TLDN):** A network address temporarily assigned for call setup.
+- 3.50 terminating SMS supplementary service:** Services or features that affect SMS message terminations, for example, screening, forwarding, delivery to an MS, delayed delivery while roaming, or distribution to a group based upon a destination address.
+- 3.51 termination address:** One or more digits, as determined by the Home System, which identify the Terminating Party. This could include Speed Call Codes (when supported by the Home Service Provider), other Mobile Telephone Numbers or any valid World Telephone Number.
+- 3.52 traffic:** The information generated by the subscriber that is transported on the network (i.e., user voice or data).
+- 3.53 unavailable:** The MS cannot accept a normal call delivery (i.e., the MS is in an unknown location or it is in a state unable to accept call deliveries). The availability of an MS to accept a call delivery is maintained only by the MSC. (See also "active", "available" and "inactive".)
+- 3.54 unregistered:** A state where the MS is unavailable for any type of termination event and the HLR pointer is not directed to any visited system.
+- 3.55 visited network:** The visited network is a carrier's network where a subscriber currently is roaming. The term visited network is more business significant, than geographically significant.
+- 3.56 visited system:** From the MS's perspective, a system which is transmitting a SID which is not recognized by the MS as the "Home" SID. From a network perspective, the system in which an MS is currently registered.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|-------|----------------------------------------------------|
+| $\mu$ | Microsecond ( $10^{-6}$ second) |
+| 3G | Third Generation |
+| 3GPP2 | Third Generation Partnership Project (ANSI driven) |
+| AC | Authentication Centre |
+| ADDS | Application Data Delivery Service |
+| ADPCM | Adaptive Differential Pulse Code Modulation |
+| ADS | Asynchronous Data Service |
+| AH | Answer Hold |
+| AMPS | Advanced Mobile Phone System |
+| ANSI | American National Standards Institute |
+| AOC | Advice of Charge |
+| API | Application Programming Interface |
+
+| | |
+|-------|--------------------------------------------------------|
+| ARIB | Association of Radio Industries and Businesses (Japan) |
+| AS | Application Server |
+| BCMCS | Broadcast-Multicast Services |
+| BCSMs | Basic Call State Models |
+| BS | Base Station |
+| BSC | Base Station Controller |
+| BTS | Basic Transceiver System |
+| CCF | Call Control Function |
+| CDCP | Call Data Collection Point |
+| CDGP | Call Data Generation Point |
+| CDIS | Call Data Information Source |
+| CDMA | Code Division Multiple Access |
+| CDRP | Call Data Rating Point |
+| CN | Core Network |
+| CNAP | Calling Name Presentation |
+| CNAR | Calling Name Restriction |
+| CNIP | Calling Number Identification Presentation |
+| CSC | Customer Service Centre |
+| CSCF | Call Session Control Functions |
+| CWTS | China Wireless Telecommunication Standard Group |
+| DCCH | Dedicated Control Channel |
+| DFP | Distributed Functional Plane |
+| DMH | Data Message Handler |
+| DP | Detection Point |
+| DP | Data Privacy |
+| DSA | Data Subscriber Authentication |
+| DTMF | Dual Tone Multi-Frequency |
+| E2E | End-to-End |
+| EIA | Electronics Industry Association |
+| EIR | Equipment Identity Register |
+| EMS | Enhanced Message Service |
+| ESN | Electronic Serial Number |
+| ESP | Encapsulating Security Payload |
+| FCC | Federal Communications Commission |
+| FFMS | File Format for Multimedia Services |
+| FPH | FreePhone |
+
+| | |
+|----------|----------------------------------------------------------------------------------|
+| FPLMTS | Future Public Land Mobile Telecommunications Systems – now IMT-2000 |
+| GECO | Global ECO (Emergency Call Origination) |
+| GSM | Global System For Mobile Communications (Formerly: Group Special Mobile) |
+| HA | Home Agent |
+| HHS | Home Subscriber Server |
+| HLR | Home Location Register |
+| IETF | Internet Engineering Task Force |
+| IM | IP Multimedia |
+| IMS | IP Multimedia Subsystem |
+| IMSI | International Mobile Subscriber Identity |
+| IMT | International Mobile Telecommunications |
+| IMT-2000 | International Mobile Telecommunications – 2000 |
+| IOTA | IP Over-the-Air |
+| IOTA HCM | Internet based Over-the-Air Handset Configuration Management |
+| IP | Internet Protocol |
+| IP | Intelligent Peripheral |
+| IPE | In Path Equipment |
+| IS | Interim Standard |
+| ISDN | Integrated Services Digital Network |
+| ISIM | IP Multimedia Services identity Module |
+| ISLP | InterSystem Link Protocol |
+| ISO | International Organization for Standardization |
+| ITU | International Telecommunication Union |
+| ITU-R | International Telecommunication Union – Radiocommunication Sector |
+| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector |
+| IWF | Interworking Function |
+| LBSS | Location Based Services System |
+| LMSD | Legacy Mobile Station Domain |
+| MAP | Mobile Application Part |
+| MC | Multi-Carrier |
+| MC | Message Centre |
+| MDN | Mobile Directory Number |
+| MEID | Mobile Equipment Identifier |
+| MGW | Media Gateway |
+| MHz | Megahertz ( $10^6$ Hertz) |
+| MM | Multimedia Message |
+
+| | |
+|--------|----------------------------------------------------------|
+| MMS | Multimedia Messaging Service |
+| MS | Mobile Station |
+| MSC | Mobile Switching Centre |
+| MSID | Mobile Station Identifier |
+| NAM | Number Assignment Module |
+| NAMPS | Narrowband Advanced Mobile Phone Service |
+| NDSS | Network Directed System Selection |
+| NRM | Network Reference Model |
+| OAM&P | Operations, Administration, Maintenance and Provisioning |
+| OSA | Open Service Access |
+| OTAF | Over the-Air Function |
+| OTAPA | Over-the-Air Parameter Administration |
+| OTASP | Over-the-Air Service Provisioning |
+| PCF | Packet Control Function |
+| PCS | Personal Communications Service |
+| PCS | Personal Communications System |
+| PDE | Positioning Determining Element |
+| PDS | Packet Data Surveillance |
+| PDSN | Packet Data Serving Node |
+| PL | Preferred Language |
+| PN | Project Number |
+| PPC | Pre-Paid Charging |
+| PPP | Point-to-Point Protocol |
+| PRC | Premium Rate Charging |
+| RAN | Radio Access Network |
+| RUAC | Rejection of Undesired Annoying Calls |
+| R-UIIM | Removable User Identity Module |
+| SC | Subscriber Confidentially |
+| SCF | Service Call Forwarding |
+| SCF | Service Control Function |
+| SCP | Service Control Point |
+| SCS | Service Capability Server |
+| SDO | Standards Development Organization |
+| SDP | Session Description Protocol |
+| SID | System Identifier |
+| SIP | Session Initiation Protocol |
+
+| | |
+|------|---------------------------------------------------|
+| SME | Short Message Entity |
+| SMS | Service Management System |
+| SMS | Short Message Service |
+| SMTP | Simple Mail Transfer Protocol |
+| SN | Service Node |
+| SRG | System Release guide |
+| SS7 | Signalling System 7 |
+| SSF | Service Switching Function |
+| SSG | Special Study Group |
+| TFO | Tandem Free Operation |
+| TIA | Telecommunications Industry Association |
+| TMSI | Temporary Mobile Station Identification |
+| TR | Transmit-Receive (as in TR45) |
+| TRAU | Transcoder and Rate Adaptor Unit |
+| TrFO | Transcoder Free Operation |
+| TSB | Telecommunications Systems Bulletin |
+| TTA | Telecommunications Technology Association (Korea) |
+| TTC | Telecommunication Technology Committee (Japan) |
+| UICC | Universal Integrated Circuit Card |
+| UIM | User Identity Module |
+| USCF | User Selective Call Forwarding |
+| VASP | Value-Added Service Provider |
+| VLR | Visitor Location Register |
+| WIN | Wireless Intelligent Network |
+| WLL | Wireless Local Loop |
+| WNP | Wireless Number Portability |
+
+# 5 Introduction
+
+The core network for cdma2000 is based on an evolved ANSI-41 2nd generation mobile system. The core network technical specifications have been developed in a third generation partnership project (approved in 3GPP2 as of 31 December 2005) and transposed to the involved regional Standards Development Organizations (SDOs). The system will support different applications ranging from narrowband to wideband communications capability with integrated personal and terminal mobility to meet the user and service requirements.
+
+The core network interfaces identified in this Recommendation and the radio interfaces and radio access network interfaces identified in ITU-R Rec. M.1457-5 [1] constitute a complete system specification for the 3rd generation mobile system for terrestrial usage of this IMT-2000 family member.
+
+The descriptions in clauses 6, 7 and 8, and the descriptions of the technical specifications listed in clause 10 are for informative purposes only. Normative information is in the tables for the respective specification.
+
+# **6 Basic architecture for the ANSI-41 evolved core network with cdma2000 access network family member**
+
+The basic architecture for the ANSI-41 evolved core network with cdma2000 access network family member includes a circuit-based and packet-based core network and an all-IP multimedia domain.
+
+The following text is based on references [12 a-d] section 2.1.
+
+Figure 6-1 presents the network entities and associated reference points that comprise the ANSI-41 evolved core network with cdma2000 access network. The network entities are represented by squares, triangles and rounded corner rectangles; circles represent the reference points. The network reference model in this Recommendation is the compilation of several reference models currently in use.
+
+- The network reference model is a functional block diagram.
+- A network entity represents a group of functions, not a physical device. For example, a Mobile Switching Centre (MSC) is a physical device; it comprises frames, shelves, circuit packs, etc. The physical device may comprise a single network entity such as the MSC, or it may comprise some combination such as the MSC, the Visitor Location Register (VLR), the Home Location Register (HLR), and the Authentication Centre (AC). The physical realization is an implementation issue; a manufacturer may choose any physical implementation of network entities, either individually or in combination, as long as the implementation meets the functional requirements. Sometimes, for practical reasons, the functional network entity is a physical device. The Mobile Station (MS) is an excellent example.
+- A reference point is a conceptual point that divides two groups of functions. It is not necessarily a physical interface. A reference point only becomes a physical interface when the network entities on either side of it are contained in different physical devices.
+- A "collective entity" contains encompassed network entities that are an instance of the collective.
+- A "composite entity" contains encompassed network entities that are part of the composite.
+
+
+
+Figure 6-1/Q.1742.5 – ANSI-41 evolved core network with cdma2000 access network reference model. The diagram shows a complex network architecture with various entities and interfaces. On the left, a Mobile Station (MS) contains a Mobile Equipment (ME) with MT0, MT1, MT2, and a UIM, connected to a Vehicle. The ME connects to a Base Station (BS) via interfaces Um, Ater, and Abis. The BS connects to a Base Station Controller (BSC) via Ater and Abis. The BSC connects to a Mobile Switching Center (MSC) via interface A. The MSC is part of the Core Network (enclosed in a solid line) and connects to various other entities: IP (via T3, T8, T5, T9), SCP (via T7, T1, T2, T6, T4), SN (via D1, A1), PSTN (via W, DCE, R, TE2), PDN (via Ri, TE2), ISDN (via S, TE1), CSC (via X, TA, R, TE2), IWF (via D1), WNE (via Y), ESME (via E2), PDE (via E5), HA (via E12), AAA (via Pi), PDSN (via Pi), MC (via N, HLR), VLR (via D, Q1), AC (via H), OTAF (via G, D1), SME (via M1, M2, M3), PCF (via Aquarter), and CDIS (via I). The IP entity connects to NPDB (via Z), LPDE (via E7), and VMS (via Z1). The IP entity also connects to an all-IP multimedia domain containing CDGP (via J), CDCP (via K), CDRP, DF (via e), CF, and CRDB. Other interfaces shown include Z, E, F, Q, Z2, C, B, D, N1, E3, V, X, D1, E9, E11, and O2. A legend at the bottom defines symbols for specific network entities, composite entities, collective entities, interface reference points, interfaces to another instance of the same network entity, and line intersections. A note states that the portion within the solid line is the Core Network.
+
+Q.1742.5(06)\_F6-1
+
+
+
+Legend for the diagram. It defines symbols for: Specific network entity (triangle, square, rectangle), Composite entity (rounded rectangle), Collective entity (dashed rectangle), Interface reference point (circle with H), Interface to another instance of the same Network Entity (circle with X), and Line intersection (cross with dot).
+
+NOTE – The portion of the figure within the solid line is the Core Network.
+
+**Figure 6-1/Q.1742.5 – ANSI-41 evolved core network with cdma2000 access network reference model**
+
+The basic architecture for the ANSI-41 evolved core network with cdma2000 access network family member also includes an all-IP multimedia domain. The following text is based on references [13 a-c] section 2.1.
+
+### **All-IP MMD Core Network Architecture:**
+
+Figure 6-2 presents the core network entities and associated reference points that comprise the MMD (Multimedia Domain) of the wireless all-IP Network Architecture Model. The network entities are represented by squares and rectangles; the interfaces between network entities are
+
+reference points identified by numbers. Figure 6-2 includes several reference points that have dual labels. Either of these labels may be used in the specifications relating to these reference points.
+
+
+
+Figure 6-2/Q.1742.5 – ANSI-41 evolved core network with cdma2000 access network IP MMD core network architecture model. The diagram shows a complex network architecture with various components and reference points. At the top, a 'Databases' box contains EIR, DSI, Subscription profile, Network policy rules, and others. Below it, an 'Application server' and 'SIP application server' are connected to an 'OSA service capability server'. The 'OSA service capability server' is connected to an 'AAA' box, which is also connected to a 'Position server' and 'Position determining entity'. The 'AAA' box is connected to an 'Access gateway' (bold), which is part of the 'IP MMD core network' (shaded). The 'Access gateway' is connected to a 'Mobile IP home agent' (bold), which is connected to a 'Border router' (bold). The 'Border router' is connected to a 'PSTN' cloud and an 'IP network' cloud. The 'Mobile IP home agent' is also connected to a 'Media resource function processor' (bold), which is connected to a 'Media gateway' (bold). The 'Media gateway' is connected to the 'PSTN' cloud and the 'IP network' cloud. The 'Media resource function processor' is also connected to a 'Media resource function controller' (bold), which is connected to a 'Call session control function' (bold). The 'Call session control function' is connected to the 'AAA' box and a 'Policy decision function' (bold). The 'Policy decision function' is connected to a 'Breakout gateway control function' (bold). The 'Breakout gateway control function' is connected to the 'SIP application server' and the 'IP network' cloud. The 'Access gateway' is also connected to a 'cdma2000 access network' box, which contains 'BTS', 'BSC/RNC + PCF', and 'MM'. The 'cdma2000 access network' box is connected to 'Other access networks' and a 'Mobile station' (bold). Reference points are indicated by numbers and letters (e.g., 1, 2, 3, 4, 5/Mk, 6, 7, 8/OSA, 9/Mi, 10, 11/Sh, 12/ISC, 13, 14, 15, 16/Cx, 17/Mg, 18, 19, 20, 21, 22, 23, 24/Mr, 25/Mp, 26/PSTN, 27, 28/Go, 29, 30/Mc, 31, 32/Mb, 33/Mb, 34/Mb, 35, 36/Mb, 37/Mb, 38/Mb, 39, 40/Mb, 41, 42/Mb, 43/Mb, 44/Mb, 45/Mb, 46/Mb, 47, hh, 49/Mj).
+
+NOTE – The "IP MMD core network" is identified by the network elements and reference points indicated in bold (solid lines and dotted lines) and shaded in boxes (in blue in the electronic version).
+
+**Figure 6-2/Q.1742.5 – ANSI-41 evolved core network with cdma2000 access network IP MMD core network architecture model**
+
+The MMD of the all-IP Network offers both general packet data support and multimedia session capabilities. The multimedia session capabilities are built on top of the general packet data support
+
+capabilities. The general packet data capabilities may be deployed without the multimedia session capabilities. Some network entities are common to providing both capabilities.
+
+Figure 6-3 shows the entities that comprise the general packet data support portion of the MMD core network. These are known collectively as the Packet Data Subsystem (PDS). Figure 6-3 includes several reference points that have dual labels. Either of these labels may be used in the specifications relating to these reference points.
+
+
+
+The diagram illustrates the architecture of an ANSI-41 evolved core network with a cdma2000 access network packet data subsystem (PDS). The PDS is highlighted in blue and includes the following components and reference points:
+
+- Databases:** EIR, DSI, Subscription profile, Network policy rules, and others. These are connected to the AAA via reference points 1, 2, 3, and 4.
+- AAA:** A central authentication, authorization, and accounting entity. It is connected to the Position server (15), Position determining entity (19), cdma2000 access network (31), and the Access gateway (21, 22).
+- Access gateway:** A key component of the PDS, connected to the AAA (21, 22), cdma2000 access network (31), Mobile IP home agent (41, 43/Mb), and the Border router (40/Mb).
+- FA / attendant:** Located within the Access gateway, connected to the Mobile IP home agent (41, 43/Mb).
+- Mobile IP home agent:** A core component of the PDS, connected to the FA / attendant (41, 43/Mb), Media resource function processor (37/Mb), Media gateway (42/Mb), and the Border router (44/Mb, 45/Mb).
+- Border router:** A core component of the PDS, connected to the Access gateway (40/Mb), Mobile IP home agent (44/Mb, 45/Mb), PSTN (34/Mb), and the IP network (46/Mb).
+- Other network elements:**
+ - Application server:** Connected to the AAA (8/OSA).
+ - SIP application server:** Connected to the AAA (12/ISC).
+ - OSA service capability server:** Connected to the AAA (10, 11/Sh).
+ - Breakout gateway control function:** Connected to the AAA (5/Mk, 9/Mi, 17/Mj).
+ - Policy decision function:** Connected to the AAA (16/Cx, 23, 28/Go).
+ - Call session control function:** Connected to the AAA (11/Sh, 12/ISC, 16/Cx, 23, 50).
+ - Media resource function controller:** Connected to the AAA (24/Mr).
+ - Media resource function processor:** Connected to the AAA (25/Mp), Media resource function controller (25/Mp), and the Mobile IP home agent (37/Mb).
+ - Media gateway:** Connected to the AAA (26/PSTN, 30/Mc), Media resource function processor (33/Mb), and the Mobile IP home agent (38/Mb).
+ - Position server:** Connected to the AAA (15) and the Position determining entity (18).
+ - Position determining entity:** Connected to the Position server (18) and the AAA (19).
+- Access Networks:**
+ - cdma2000 access network:** Contains BTS, BSC/RNC + PCF, and MM. It is connected to the AAA (31) and the Access gateway (31, 35).
+ - Other access networks:** Connected to the AAA (35) and the Access gateway (35).
+- External Networks:**
+ - PSTN:** Connected to the Border router (34/Mb).
+ - IP network:** Connected to the Border router (46/Mb).
+- Mobile station:** Connected to the cdma2000 access network (47).
+
+Figure 6-3/Q.1742.5 – ANSI-41 evolved core network with cdma2000 access network packet data subsystem core network architecture model. The diagram shows various network elements and their interconnections, with the Packet Data Subsystem (PDS) highlighted in blue.
+
+NOTE – The "Packet Data Subsystem" is identified by the network elements and reference points indicated in bold (solid lines and dotted lines) and shaded in boxes (in blue in the electronic version).
+
+**Figure 6-3/Q.1742.5 – ANSI-41 evolved core network with cdma2000 access network packet data subsystem core network architecture model**
+
+Figure 6-4 shows the entities that comprise the multimedia session capabilities of an All-IP network. These entities are known collectively as the IP Multimedia Session Subsystem (IMS). Figure 6-4 includes several reference points that have dual labels. Either of these labels may be used in the specifications relating to these reference points.
+
+
+
+Figure 6-4/Q.1742.5 – ANSI-41 evolved core network with cdma2000 access network IP multimedia session subsystem core network architecture model. The diagram shows various network elements and their interconnections. A dashed box labeled 'Databases' contains EIR, DSI, Subscription profile, Network policy rules, and others. Other elements include Position server, Position determining entity, cdma2000 access network (BTS, BSC/RNC + PCF, MM), Other access networks, Mobile station, Access gateway, FA / attendant, Mobile IP home agent, Application server, SIP application server, OSA service capability server, Breakout gateway control function, AAA, Call session control function, Policy decision function, Media resource function controller, Media resource function processor, Media gateway control function, and Media gateway. Connections are labeled with reference points such as 1, 2, 3, 4, 5/Mk, 6, 7, 8/OSA, 9/Mi, 10, 11/Sh, 12/ISC, 13, 14, 15, 16/Cx, 17/Mg, 18, 19, 20, 21, 22, 23, 24/Mr, 25/Mp, 26/PSTN, 27, 28/Go, 29, 30/Mc, 31, 32/Mb, 33/Mb, 34/Mb, 35, 36/Mb, 37/Mb, 38/Mb, 39, 40/Mb, 41, 42/Mb, 43/Mb, 44/Mb, 45/Mb, 46/Mb, 47, and hh. The IMS core is highlighted in blue, containing the OSA service capability server, SIP application server, Call session control function, Policy decision function, Media resource function controller, Media resource function processor, and Media gateway control function. The diagram also shows connections to PSTN and IP network clouds at the bottom right.
+
+NOTE – The "IP Multimedia Session Subsystem" is identified by the network elements and reference points indicated in bold (solid lines and dotted lines) and shaded in boxes (in blue in the electronic version).
+
+**Figure 6-4/Q.1742.5 – ANSI-41 evolved core network with cdma2000 access network IP multimedia session subsystem core network architecture model**
+
+The session control functions within the IMS are logically interconnected in various ways in the session scenarios. Figure 6-5 identifies the reference points within the IMS between these session control entities. In many cases there are dual labels for these reference points either of which may be used in the applicable specifications.
+
+Image: Figure 6-5/Q.1742.5 – Session Control Reference Model
+
+```
+
+ graph LR
+ IP[IP multimedia client] -- hh/Gm --- P[Proxy Call session control function]
+ P -- dd/Mw --- I[Interrogating Call session control function]
+ I -- ff/Mw --- S[Serving Call session control function]
+ P -- 17/Mg --- MGCF[Media gateway control function]
+ I -- 9/Mi --- MGCF
+ MGCF -- 49/Mj --- BGCF1[Breakout gateway control function]
+ BGCF1 -- 5/Mk --- BGCF2[Breakout gateway control function]
+ S -- 9/Mi --- BGCF2
+
+```
+
+**Figure 6-5/Q.1742.5 – Session Control Reference Model**
+
+### 7 Network entities
+
+The following text is based on references [12 a-d] section 2.1.1.
+
+#### 7.1 Authentication, Authorization and Accounting (AAA)
+
+The AAA is an entity that provides IP-based authentication, authorization, and accounting. The AAA maintains security associations with peer AAA entities to support intra- and/or inter-administrative domain AAA functions.
+
+- The Authentication Function provides authentication of users.
+- The Authorization Function of AAA provides authorization of service requests based on subscriber profiles, and network policy. It also generates keys required for establishing security associations between PDSNs in access provider networks and HAs in home IP networks.
+- The Accounting Function gathers accounting data concerning the services used by individual subscribers.
+
+#### 7.2 Authentication Centre (AC)
+
+The AC is an entity that manages the authentication information related to the MS. The AC may, or may not be located within, and be indistinguishable from an HLR. An AC may serve more than one HLR.
+
+#### 7.3 Call Data Collection Point (CDCP)
+
+The CDCP is the entity that collects the call detail information.
+
+#### 7.4 Call Data Generation Point (CDGP)
+
+The CDGP is an entity which provides call detail information to the CDCP (in ANSI-124 format). This may be the entity that converts call detail information from a proprietary format into a standard format. All information from the CDGP to the CDCP must be in this standard format.
+
+#### 7.5 Call Data Information Source (CDIS)
+
+The CDIS is an entity that can be the source of call detail information. This information may be in proprietary format. It is not required to be in the standard format.
+
+**ITU-T Rec. Q.1742.5 (09/2006)**
+15
+
+## **7.6 Call Data Rating Point (CDRP)**
+
+The CDRP is the entity that takes the unrated call detail information and applies the applicable charge and tax-related information. The charge and tax information is added using the standard format.
+
+### **7.7 Collection Function (CF) – [Intercept]**
+
+The CF is an entity that is responsible for collecting intercepted communications for a lawfully authorized law enforcement agency.
+
+The CFs typically include:
+
+- The ability to receive and process call contents information for each intercept subject.
+- The ability to receive information regarding each intercept subject (e.g., call associated or non-call associated) from the Delivery function and process it.
+
+### **7.8 Coordinate Routing Data Base (CRDB)**
+
+The CRDB is an entity that stores information to translate a given position expressed as a latitude and longitude to a string of digits.
+
+### **7.9 Customer Service Centre (CSC)**
+
+The CSC is an entity where service provider representatives receive telephone calls from customers wishing to subscribe to initial wireless service or request a change in the customer's existing service. The CSC interfaces proprietarily with the OTAF to perform network and MS related changes necessary to complete the service provisioning request.
+
+### **7.10 Delivery Function (DF) – [Intercept]**
+
+The DF is an entity that is responsible for delivering intercepted communications to one or more collection functions.
+
+The DFs typically include:
+
+- The ability to accept call contents for each intercept subject over one or more channels from each Access function.
+- The ability to deliver call contents for each intercept subject over one or more channels to a Collection function as authorized for each law enforcement agency.
+- The ability to accept information over one or more data channels and combine that information into a single data flow for each intercept subject.
+- The ability to filter or select information on an intercept subject before delivery to a Collection function as authorized for a particular law enforcement agency.
+- The optional ability to detect audio in-band DTMF digits for translation and delivery to a Collection function as authorized for a particular law enforcement agency.
+- The ability to duplicate and deliver information on the intercept subject to one or more Collection functions as authorized for each law enforcement agency.
+- The ability to provide security to restrict access.
+
+### **7.11 Equipment Identity Register (EIR)**
+
+The EIR is an entity that is the register to which user equipment identity may be assigned for record purposes. The nature, purpose, and utilization of this information is an area for further study.
+
+### **7.12 Home Agent (HA)**
+
+The HA is an entity that:
+
+- authenticates Mobile IP registrations from the MS;
+- redirects packets to the foreign agent component of the PDSN, and optionally receives and routes reverse packets from the foreign agent component of the PDSN;
+- may establish, maintain and terminate secure communications to the PDSN;
+- receives provisioning information from the AAA function for users;
+- may assign a dynamic home IP address.
+
+### **7.13 Home Location Register (HLR)**
+
+The HLR is the location register to which a user identity is assigned for record purposes such as subscriber information (e.g., Electronic Serial Number (ESN), Mobile Directory Number (MDN), Profile Information, Current Location, Authorization Period).
+
+### **7.14 Intelligent Peripheral (IP)**
+
+The IP is an entity that performs specialized resource functions such as playing announcements, collecting digits, performing speech-to-text or text-to-speech conversion, recording and storing voice messages, facsimile services, data services, etc.
+
+### **7.15 Intercept Access Point (IAP)**
+
+The IAP is an entity that provides access to the communications to, or from, the equipment, facilities, or services of an intercept subject.
+
+### **7.16 Interworking Function (IWF)**
+
+The IWF is an entity that provides information conversion for one or more WNEs. An IWF may have an interface to a single WNE providing conversion services. An IWF may augment an identified interface between two WNEs, providing conversion services to both WNEs.
+
+### **7.17 Local Position Determining Entity (LPDE)**
+
+The LPDE facilitates the determination of the position or geographical location of a wireless terminal. Each LPDE supports one or more position-determining technologies. Multiple LPDEs using the same technology may serve the coverage area of a Mobile Position Centre (MPC) and the multiple LPDEs each using a different technology may serve the same coverage area of an MPC. Local PDEs (LPDEs) reside at the Base Station (BS).
+
+### **7.18 Managed Wireless Network Entity (MWNE)**
+
+A MWNE (within the Collective Entity) or any specific network entity having Operations System wireless management needs, including another Operations System.
+
+### **7.19 Message Centre (MC)**
+
+The MC is an entity that stores and forwards short messages. The MC may also provide supplementary services for Short Message Service (SMS).
+
+### **7.20 Mobile Position Centre (MPC)**
+
+The MPC selects a PDE to determine the position of a mobile station. The MPC may restrict access to position information (e.g., require that the MS be engaged in an emergency call or only release position information to authorized network entities).
+
+### **7.21 Mobile Switching Centre (MSC)**
+
+The MSC switches circuit mode MS originated or MS terminated traffic. An MSC is usually connected to at least one BS. It may connect to the other public networks (PSTN, ISDN, etc.), other MSCs in the same network, or MSCs in different networks. The MSC may store information to support these capabilities.
+
+### **7.22 Number Portability DataBase (NPDB)**
+
+The NPDB is an entity which provides portability information for portable Directory Numbers.
+
+### **7.23 Over-The-Air Service Provisioning Function (OTAF)**
+
+The OTAF is an entity that interfaces proprietarily to CSCs to support service provisioning activities. The OTAF interfaces with the MSC to send MS orders necessary to complete service provisioning requests.
+
+### **7.24 Packet Data Network (PDN)**
+
+A PDN, such as the Internet, provides a packet data transport mechanism between processing network entities capable of using such services.
+
+### **7.25 Packet Data Serving Node (PDSN)**
+
+The PDSN routes MS originated or MS terminated packet data traffic. The PDSN establishes, maintains, and terminates link layer sessions to MSs. The PDSN may interface to one or more MSs and may interface to one or more PDNs.
+
+### **7.26 Position Determining Entity (PDE)**
+
+A PDE facilitates determination of the position or geographical location of a wireless terminal. Each PDE supports one or more position-determining technologies. Multiple PDEs using the same technology may serve the coverage area of a Mobile Position Centre (MPC) and the multiple PDEs each using a different technology may serve the same coverage area of an MPC.
+
+### **7.27 Service Control Point (SCP)**
+
+The SCP is an entity that acts as a real-time database and transaction processing system that provides service control and service data functionality.
+
+### **7.28 Service Node (SN)**
+
+The SN is an entity that provides service control, service data, specialized resources and call control functions to support bearer-related services.
+
+### **7.29 Short Message Entity (SME)**
+
+The SME is an entity that composes and decomposes short messages. A SME may, or may not be located within, and be indistinguishable from, an HLR, MC, VLR, MS, or MSC.
+
+### **7.30 Visitor Location Register (VLR)**
+
+The VLR is the location register other than the HLR used by an MSC to retrieve information for handling of calls to or from a visiting subscriber. The VLR may, or may not be located within, and be indistinguishable from an MSC. The VLR may serve more than one MSC.
+
+### **7.31 Voice Message Centre (VMS)**
+
+A VMS stores received voice messages, data messages e.g., email, or both message types and supports a method to retrieve previously stored messages. A VMS may also support (on a Directory Number basis) notification of the presence of stored messages and notification of a change in the number of voice messages, data messages, or both message types that are waiting retrieval.
+
+### **7.32 Wireless Network Entity (WNE)**
+
+A Network Entity in the wireless Collective Entity.
+
+The remaining text in this clause is based on references [13 a-c] section 2.1.
+
+### **7.33 Access Gateway (AGW)**
+
+The CDMA2000 AGW consists of the PDSN and other logical functions required to interface the core network to the CDMA2000 RAN.
+
+- The PDSN routes MS originated or MS terminated packet data traffic. The PDSN establishes, maintains, and terminates link layer sessions to MSs. The PDSN may interface to one or more MSs and may interface to one or more PDNs.
+
+### **7.34 Application Server**
+
+Application Servers provide value-added network-based services for wireless subscribers. These services may be accessed via the OSA Service Capability Server (OSA-SCS) or accessed directly from the user's mobile station via other network entities, by-passing the OSA-SCS.
+
+### **7.35 Authentication, Authorization and Accounting (AAA)**
+
+The AAA is an entity that provides IP-based authentication, authorization, and accounting. The AAA maintains security associations with peer AAA entities to support intra- and/or inter-administrative domain AAA functions.
+
+- The Authentication Function is an entity that provides authentication of terminal devices and subscribers.
+- The Authorization Function provides authorization of requests for services and/or bandwidth, etc. and has access to the Policy Repository, the Directory Services, Subscriber Profiles, and the Device Register.
+- The Accounting Function gathers data concerning the services, QoS, and multimedia resources requested and used by individual subscribers.
+
+### **7.36 Border Router (BR)**
+
+The BR connects the Core Network with peer networks (e.g., other service providers, corporate networks, Internet). The BR performs IP packet routing, exterior gateway routing protocols, and policing of incoming and outgoing traffic, ensuring traffic complies with defined Service Level Agreements established with peer networks. The BR may intercept any QoS allocation request, and issue a request to the Policy Decision Function (PDF), which shall verify that the requested inbound and/or outbound QoS is available. A successful response from the PDF may cause the BR to forward the bandwidth allocation request to its final destination.
+
+### **7.37 Breakout Gateway Control Function (BGCF)**
+
+The BGCF selects the network in which PSTN breakout is to occur and, within the network where the breakout is to occur, selects the MGCF.
+
+### **7.38 Call Session Control Function (CSCF)**
+
+The CSCF establishes, monitors, supports, releases Multimedia sessions, and manages the user's service interactions.
+
+### **7.39 Databases (DB)**
+
+The information in the core network DBs may include but is not limited to EIR, Dynamic Subscriber Information, Network Policy Rules and Subscriber Profile data.
+
+### **7.40 IP Multimedia Client**
+
+The IP Multimedia Client communicates with Application Servers, P-CSCFs, and other IP Multimedia Clients. The IP Multimedia Client is an application that resides in the MS.
+
+### **7.41 IP Network**
+
+The IP network corresponds to IP-based packet data networks that provide a transport mechanism between the core network and external IP networks. IP Network represents packet networks connected to the core network including the public Internet, private IP backbone networks and private IP networks such as corporate Intranets.
+
+### **7.42 Media Gateway (MGW)**
+
+The MGW provides an interface between the packet environment of the Core Network and the circuit switched environment of the PSTN for bearer traffic, when equipped with circuit capabilities. The MGW may provide vocoding and/or transcoding functions to the bearer traffic. The MGW may also provide modem functions to convert digital byte streams to and from audio modem tones placed on circuits, and may provide the capability to terminate PPP (Point-to-Point Protocol) connections. It also provides policy enforcement relative to its activities and resources.
+
+### **7.43 Media Gateway Control Function (MGCF)**
+
+The MGCF provides the ability to control a Media Gateway through standardized interfaces. Such control includes allocation and deallocation of resources of the Media Gateway, as well as modification of the usage of those resources.
+
+### **7.44 Media Resource Function Controller (MRFC)**
+
+The MRFC, in conjunction with the MRFP, provides a set of resources within the core network that are useful in supporting services to subscribers. The MRFC, in conjunction with the MRFP, provides multi-way conference bridges, announcement playback services, tone playback services, etc.
+
+### **7.45 Media Resource Function Processor (MRFP)**
+
+The MRFP, in conjunction with the controlling entity, provides multi-way conference bridges, announcement playback services, tone playback services, etc.
+
+### **7.46 Mobile IP Home Agent (HA)**
+
+The HA provides two major functions: registering the current point of attachment of the user, and forwarding of IP packets to and from the current point of attachment (IPv4 Care of Address [CoA] and/or IPv6 Co-located CoA) of the user. The HA accepts registration requests using the Mobile IP protocol and uses the information in those requests to update internal information about the current point of attachment of the user, i.e., the current IP address to be used to transmit and receive IP packets to and from that user. The HA interacts with the AAA to receive Mobile IP registration requests that have been authenticated, and to return Mobile IP registration responses. The HA also
+
+interacts with the Access Gateway to receive subsequent Mobile IP registration requests. The HA may interact with several network entities in performing its work of forwarding IP packets to the current point of attachment of the user.
+
+### **7.47 Mobile Station (MS)**
+
+The MS is a wireless terminal used by subscribers to access the Legacy MS Domain or the IP Multimedia Domain services over a radio interface. MSs include portable units (e.g., hand-held units), units installed in vehicles, and somewhat paradoxically, fixed location MSs. The MS is the interface equipment used to terminate the radio path at the subscriber. A MS is a ME with a programmed UIM.
+
+### **7.48 OSA Service Capability Server (OSA-SCS)**
+
+The OSA-SCS provides access to network resources needed during service application execution. The interface towards the Application Server uses application programming interfaces such as Open Service Architecture (OSA). The interfaces towards other network entities use the relevant protocols.
+
+### **7.49 Policy Decision Function (PDF)**
+
+The PDF provides management of core network QoS resources within its own core network necessary to support services to network users. It communicates with the Access Gateway to provide authorization of resource allocations. The PDF makes policy decisions with regard to use of core network QoS resources within its own network, including consideration of Service Level Agreements (SLAs). QoS policy information for network resource utilization may be forwarded to and cached by the PDF.
+
+NOTE – The maintenance of SLAs is for further study.
+
+### **7.50 Position Determining Entity (PDE)**
+
+The PDE communicates with the Position Server to determine the precise geographic position of the MS based on input data provided by the Position Server.
+
+## **7.51 Position Server**
+
+The Position Server provides geographic position information to requesting entities.
+
+## **7.52 Public Switched Telephone Network (PSTN)**
+
+The PSTN is defined in accordance with the appropriate applicable national and regional standards.
+
+# **8 Reference Points**
+
+The following text is based on references [12 a-d] section 2.1.2.
+
+### **8.1 Reference Point B**
+
+Reference Point B is the interface between MSC and the VLR.
+
+## **8.2 Reference Point C**
+
+Reference Point C is the interface between the MSC and the HLR.
+
+## **8.3 Reference Point D**
+
+Reference Point D is the interface between the VLR and HLR.
+
+## **8.4 Reference Point d**
+
+Reference Point d is the interface between an IAP and the DF.
+
+## **8.5 Reference Point D1**
+
+Reference Point D1 is the interface between the OTAF and the VLR.
+
+### **8.6 Reference Point Di**
+
+Reference Point Di is the interface between:
+
+- the IP and the ISDN;
+- the IWF and the ISDN;
+- the MSC and the ISDN (ESBE);
+- the SN and the ISDN.
+
+## **8.7 Reference Point E**
+
+Reference Point E is the interface between the MSC and MSC.
+
+## **8.8 Reference Point E3**
+
+Reference Point E3 is the interface between MPC and the MSC.
+
+## **8.9 Reference Point E5**
+
+Reference Point E5 is the interface between the MPC and the PDE.
+
+## **8.10 Reference Point E9**
+
+Reference Point E9 is the interface between the MPC and the SCP.
+
+## **8.11 Reference Point E11**
+
+Reference Point E11 is the interface between the CRDB and the MPC.
+
+## **8.12 Reference Point E12**
+
+Reference Point E12 is the interface between MSC and the PDE.
+
+## **8.13 Reference Point e**
+
+Reference Point e is the interface between the CF and the DF.
+
+## **8.14 Reference Point F**
+
+Reference Point F is the interface between the MSC and the EIR.
+
+## **8.15 Reference Point G**
+
+Reference Point G is the interface between the VLR and the VLR.
+
+## **8.16 Reference Point H**
+
+Reference Point H is the interface between the HLR and the AC.
+
+## **8.17 Reference Point I**
+
+Reference Point I is the interface between the CDIS and the CDGP.
+
+### **8.18 Reference Point J**
+
+Reference Point J is the interface between the CDGP and the CDCP.
+
+## **8.19 Reference Point K**
+
+Reference Point K is the interface between the CDGP and the CDRP.
+
+## **8.20 Reference Point L**
+
+Reserved.
+
+## **8.21 Reference Point M1**
+
+Reference Point M1 is the interface between the SME and the MC.
+
+## **8.22 Reference Point M2**
+
+Reference Point M2 is the MC to MC interface.
+
+## **8.23 Reference Point M3**
+
+Reference Point M3 is the SME to SME interface.
+
+## **8.24 Reference Point N**
+
+Reference Point N is the interface between the HLR and the MC.
+
+## **8.25 Reference Point N1**
+
+Reference Point N1 is the interface between the HLR and the OTAF.
+
+## **8.26 Reference Point O1**
+
+Reference Point O1 is the interface between an MWNE and the OSF.
+
+## **8.27 Reference Point O2**
+
+Reference Point O2 is the interface between an OSF and the OSF.
+
+## **8.28 Reference Point Pi**
+
+Reference Point Pi is the interface between:
+
+- the AAA and the AAA;
+- the AAA and the PDN;
+- the IWF and the PDN;
+- the MSC and the PDN; plus
+- the PDSN and the PDN.
+
+### **8.29 Reference Point Q**
+
+Reference Point Q is the interface between the MC and the MSC.
+
+## **8.30 Reference Point Q1**
+
+Reference Point Q1 is the interface between the MSC and the OTAF.
+
+### **8.31 Reference Point T1**
+
+Reference Point T1 is the interface between the MSC and the SCP.
+
+### **8.32 Reference Point T2**
+
+Reference Point T2 is the interface between the HLR and the SCP.
+
+### **8.33 Reference Point T3**
+
+Reference Point T3 is the interface between the IP and the SCP.
+
+### **8.34 Reference Point T4**
+
+Reference Point T4 is the interface between the HLR and the SN.
+
+### **8.35 Reference Point T5**
+
+Reference Point T5 is the interface between the IP and the MSC.
+
+### **8.36 Reference Point T6**
+
+Reference Point T6 is the interface between the MSC and the SN.
+
+### **8.37 Reference Point T7**
+
+Reference Point T7 is the interface between the SCP and the SN.
+
+### **8.38 Reference Point T8**
+
+Reference Point T8 is the interface between the SCP and the SCP.
+
+### **8.39 Reference Point T9**
+
+Reference Point T9 is the interface between the HLR and the IP.
+
+### **8.40 Reference Point V**
+
+Reference Point V is the interface between the OTAF and the OTAF.
+
+## **8.41 Reference Point X**
+
+Reference Point X is the interface between the CSC and the OTAF.
+
+### **8.42 Reference Point Y**
+
+Reference Point Y is the interface between a Wireless Network Entity (WNE) and the IWF.
+
+### **8.43 Reference Point Z**
+
+Reference Point Z is the interface between the MSC and the NPDB.
+
+## **8.44 Reference Point Z1**
+
+Reference Point Z1 is the interface between the MSC and the VMS.
+
+### **8.45 Reference Point Z2**
+
+Reference Point Z2 is the interface between the HLR and the VMS.
+
+### **8.46 Reference Point Z3**
+
+Reference Point Z3 is the interface between the MC and the VMS.
+
+The remaining text in this clause is based on references [13 a-c] section 2.1.
+
+An interface exists when two Network Entities are interconnected through exactly one signalling or bearer stream Reference Point. The Reference Points and their associated Network Entities are:
+
+### **8.47 Reference Point 1**
+
+Reference Point 1 is the signalling interface between the Databases and the Position Server (Multimedia Domain only).
+
+### **8.48 Reference Point 2**
+
+Reference Point 2 is the signalling interface between the Databases and the cdma2000 Access Network.
+
+### **8.49 Reference Point 3**
+
+Reference Point 3 is the signalling interface between the Databases and the Policy Decision Function (Multimedia Domain only).
+
+### **8.50 Reference Point 4**
+
+Reference Point 4 is the signalling interface between the Databases and the AAA.
+
+### **8.51 Reference Point 5/Mk**
+
+Reference Point 5/Mk is the signalling interface between Breakout Gateway Control Functions (Multimedia Domain only).
+
+## **8.52 Reference Point 6**
+
+Reference Point 6 is the signalling interface between the Databases and the Legacy MS Domain Support (Legacy MS Domain only).
+
+## **8.53 Reference Point 7**
+
+Reference Point 7 is the signalling interface between the OSA Service Capability Server and the Databases.
+
+## **8.54 Reference Point 8/OSA**
+
+Reference Point 8/OSA is the signalling interface between the OSA Application Server and the OSA Service Capability Server. Reference Point 8/OSA may employ interfacing techniques that support a wide spectrum of capabilities, ranging from secure (e.g., application programming interfaces such as Parlay, used for un-trusted parties) to non-secure (e.g., used for trusted parties).
+
+### **8.55 Reference Point 9/Mi**
+
+Reference Point 9/Mi is the signalling interface between the Visited Network's BGCF and the Home Service Network's Serving-CSCF.
+
+## **8.56 Reference Point 10**
+
+Reference Point 10 is the signalling interface between the Position Server and the OSA Service Capability Server (Multimedia Domain only).
+
+### **8.57 Reference Point 11/Sh**
+
+Reference Point 11/Sh is the signalling interface between the SIP Application Server and the AAA and between the OSA Service Capability Server and the AAA for user's service authentication and/or authorization, and for retrieving information from the MMD database (Multimedia Domain only).
+
+### **8.58 Reference Point 12/ISC**
+
+Reference Point 12/ISC is the signalling interface between the SIP Application Server and Call Session Control Function and between the OSA Service Capability Server and the Call Session Control Function for service control (Multimedia Domain only).
+
+## **8.59 Reference Point 13**
+
+Reference Point 13 is the signalling interface between the Legacy MS Domain Support and the PSTN (Legacy MS Domain only).
+
+### **8.60 Reference Point 14**
+
+Reference Point 14 is the signalling interface between the Legacy MS Domain Support and the MAP (TIA/EIA-41 & GSM) (Legacy MS Domain only).
+
+### **8.61 Reference Point 15**
+
+Reference Point 15 is the signalling interface between the Position Server and AAA.
+
+### **8.62 Reference Point 16/Cx**
+
+Reference Point 16/Cx is the signalling interface between the AAA and the Call Session Control Function (Multimedia Domain only).
+
+### **8.63 Reference Point 17/(Mg)**
+
+Reference Point 17/(Mg) is the signalling interface between the Call Session Control Function and the Media Gateway Control Function (Multimedia Domain only).
+
+## **8.64 Reference Point 18**
+
+Reference Point 18 is the signalling interface between the Position Server and the Position Determining Entity.
+
+## **8.65 Reference Point 19**
+
+Reference Point 19 is the signalling interface between the Position Server and the Access Gateway (Multimedia Domain only).
+
+### **8.66 Reference Point 20**
+
+Reference Point 20 is the signalling interface between the AAA and the cdma2000 Access Network (Multimedia Domain only).
+
+### **8.67 Reference Point 21**
+
+Reference Point 21 is the signalling interface between the AAA and Access Gateway.
+
+### **8.68 Reference Point 22**
+
+Reference Point 22 is the signalling interface between the AAA and the Mobile IP Home Agent.
+
+### **8.69 Reference Point 23**
+
+Reference Point 23 is the signalling interface between the AAA and the Policy Decision Function (Multimedia Domain only).
+
+### **8.70 Reference Point 24/Mr**
+
+Reference Point 24/Mr is the signalling interface between the Call Session Control Function and the Media Resource Function Controller (Multimedia Domain only).
+
+### **8.71 Reference Point 25/Mp**
+
+Reference Point 25/Mp is the signalling interface between the Media Resource Function Controller and the Media Resource Function Processor.
+
+## **8.72 Reference Point 26/PSTN**
+
+Reference Point 26/PSTN is the signalling interface between the Media Gateway Control Function and the PSTN (Multimedia Domain only).
+
+## **8.73 Reference Point 27**
+
+Reference Point 27 is the bearer stream interface between the cdma2000 Access Network and the Media Gateway (Legacy MS Domain only).
+
+### **8.74 Reference Point 28/Go**
+
+Reference Point 28/Go is the signalling interface between the Policy Decision Function and Access Gateway.
+
+## **8.75 Reference Point 29**
+
+Reference Point 29 is the signalling interface between Policy Decision Function and the Border Router.
+
+### **8.76 Reference Point 30/Mc**
+
+Reference Point 30/Mc is the signalling interface between the Media Gateway Control Function and the Media Gateway (Multimedia Domain only).
+
+## **8.77 Reference Point 31**
+
+Reference Point 31 is the bearer stream interface between cdma2000 Access Network and the Access Gateway.
+
+### **8.78 Reference Point 32/Mb**
+
+Reference Point 32/Mb is the bearer stream interface between the Access Gateway and the Media Resource Function Processor (Multimedia Domain only).
+
+## **8.79 Reference Point 33/Mb**
+
+Reference Point 33/Mb is the bearer stream interface between the Media Resource Function Processor and the Media Gateway.
+
+## **8.80 Reference Point 34/Mb**
+
+Reference Point 34/Mb is the bearer stream interface between the Media Gateway and the PSTN.
+
+### **8.81 Reference Point 35**
+
+Reference Point 35 is the signalling interface between the cdma2000 Access Network and the Access Gateway.
+
+### **8.82 Reference Point 36/Mb**
+
+Reference Point 36/Mb is the bearer stream interface between the Access Gateway and the Media Gateway (Multimedia Domain only).
+
+### **8.83 Reference Point 37/Mb**
+
+Reference Point 37/Mb is the bearer stream interface between the Media Resource Function Processor and the Mobile IP Home Agent (Multimedia Domain only).
+
+### **8.84 Reference Point 38/Mb**
+
+Reference Point 38/Mb is the bearer stream interface between the Media Gateway and the Mobile IP Home Agent (Multimedia Domain only).
+
+### **8.85 Reference Point 39**
+
+Reference Point 39 is the signalling interface between the Media Gateway and the Legacy MS Domain Support (Legacy MS Domain only).
+
+### **8.86 Reference Point 40/Mb**
+
+Reference Point 40/Mb is the bearer stream interface between the Media Gateway and the Border Router.
+
+### **8.87 Reference Point 41**
+
+Reference Point 41 is the signalling interface between the Access Gateway and the Mobile IP Home Agent.
+
+### **8.88 Reference Point 42/Mb**
+
+Reference Point 42/Mb is the bearer stream interface between the Media Resource Function Processor and the Border Router.
+
+### **8.89 Reference Point 43/Mb**
+
+Reference Point 43/Mb is the bearer stream interface between the Access Gateway and the Mobile IP Home Agent.
+
+### **8.90 Reference Point 44/Mb**
+
+Reference Point 44/Mb is the bearer stream interface between the Mobile IP Home Agent and the Border Router.
+
+### **8.91 Reference Point 45/Mb**
+
+Reference Point 45/Mb is the bearer stream interface between the Access Gateway and the Border Router.
+
+## **8.92 Reference Point 46/Mb**
+
+Reference Point 46/Mb is the bearer stream interface between the Border Router and the IP Network.
+
+## **8.93 Reference Point 47**
+
+Reference Point 47 is the Radio Link (air interface) between the Mobile Station and the cdma2000 Access Network.
+
+## **8.94 Reference Point 48**
+
+Reference Point 48 is the signalling interface between the cdma2000 Access Network and the Legacy MS Domain Support (Legacy MS Domain only).
+
+## **8.95 Reference Point 49/(Mj)**
+
+Reference Point 49/(Mj) is the signalling interface between the Breakout Gateway Control Function and the Media Gateway Control Function (Multimedia Domain only).
+
+## **8.96 Reference Point 50**
+
+Reference Point 50 is the signalling interface between the Policy Decision Function and the P-CSCF (Multimedia Domain only).
+
+# **9 Technical specifications structure**
+
+This clause provides an overview of the specifications for this IMT-2000 family member based on ANSI-41 evolved core network with cdma2000 access network. Details for these specifications may be found in clause 10.
+
+The following text describes the numbering scheme for the specifications and reports for the 3GPP2 3rd Generation Mobile System.
+
+The 3GPP2 document-numbering scheme is indicated as follows:
+
+A.Bcccc-w-x version y.z
+
+where:
+
+- 1) A denotes the TSG (A, C, N, P, S) which developed the specification where:
+ - TSG-A develops RAN (i.e., A-interface) specifications;
+ - TSG-C develops air interface specifications;
+ - TSG-N develops intersystem interface specifications;
+ - TSG-P develops packet data specifications;
+ - TSG-S develops service and system aspects specifications including Stage 1 requirements descriptions and OAM&P specifications.
+- 2) B denotes project, report, specification (P, R, S).
+- 3) cccc denotes a four-digit number which identifies the specific specification.
+- 4) w denotes revision:
+ - 0 is the first release (0th revision);
+ - A is the first revision;
+ - and so on.
+- 5) x denotes whether this is the prime revision or an addendum:
+ - 0 is the prime revision, and is used when the document is first created;
+ - 1 is the first addendum;
+ - 2 is the second addendum;
+ - and so on.
+
+- 6) y is the "point release" indicator – 0 is used when the document is first created; the number is incremented whenever approved for publishing by the plenary of a TSG (e.g., 1 is the first approval by the plenary for publishing).
+- 7) z is an internal edit level. The internal edit level z, is always reset to 0 when the document is approved by the applicable plenary. It is incremented by the entity (e.g., working group) that is developing the document for each new edit release.
+
+NOTE 1 – If the designator w and the designator x are both equal to 0, then neither designator needs to be included.
+
+NOTE 2 – The document reference section does not need to include "version y.z" unless specifically needed to resolve a technical incompatibility that would exist.
+
+# **10 Technical specifications**
+
+All dates in the tables of clause 10 are formatted day-month-year. If no day is shown for the document, then the format is -month-year.1
+
+## **10.1 A Series RAN specifications**
+
+The 3GPP2 A Series RAN specifications are outside of the scope of this Recommendation. The radio access network to core network interface specifications for the cdma2000 (ANSI-41 evolved core network with cdma2000 access network) system family will be referenced in a new issue of ITU-R Rec. M.1457-5.
+
+## **10.2 Intersystem Specifications**
+
+### **10.2.1 N.S0003-0 – v.1.0 – User Identity Module (April 2001)**
+
+This standard defines the enhancements required for the support of mobile stations equipped with User Identification Modules (UIM). The UIM provides functionality to certain types of mobile stations to enable them to operate in the wireless network.
+
+This document defines requirements for the wireless network to support operation of UIM equipped mobile stations. A UIM provides compatible mobile stations with the parameters required of mobile stations operating in the TIA/EIA-41 environment and specific additional functionality unique to UIM-equipped mobile stations.
+
+The UIM can be in one of two forms, as either integrated within the mobile or removable that can be inserted or removed from the mobile equipment. This document addresses Removable UIM (R-UIM) only.
+
+---
+
+1 Note on nomenclature of TTA documents: before TTA was accredited, documents were created under EIA. After TTA was accredited as a standards development organization, documents were named beginning with TTA/EIA. TTA documents can now stand by themselves, so since 2000, documents are now titled TTA only. The IS was an interim standard valid for 3 years and that naming system is no longer used for new documents.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0003-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA/EIA/IS-808 | | Published | 01-12-2000 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2FEIA%2FIS%2D808 |
+| TTA | TTAE.3G-N.S0003 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0003.zip |
+| TTC | TS-3GB-N.S0003v1.0 | 1 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0003-v10.pdf |
+
+### 10.2.2 N.S0004-0 – v 1.0 – WIN Phase 2 (April 2001)
+
+**Triggers for Preferred Language;**
+
+**Advice of Charge;**
+
+**Rejection of Undesired Annoying Calls;**
+
+**Premium Rate Charging;**
+
+**Freephone.**
+
+Premium Rate Charging (PRC), Freephone (FPH) and Advice of Charging (AOC) are charging related services that provide a set of advanced wireless charging capabilities. Rejection of Undesired Annoying Calls (RUAC) is a screening service that blocks undesired annoying calls to the subscriber. Enhanced Preferred Language (EPL) uses Wireless Intelligent Network (WIN) capabilities to provide announcements to the subscriber in the subscriber's preferred language. This specification presents a recommended plan for the implementation of WIN capabilities that support these features. The WIN capabilities are for use in the Wireless Radiotelephone Service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0004-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA/EIA/IS-848 | | Published | 01-12-2000 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2FEIA%2FIS%2D848 |
+| TTA | TTAE.3G-N.S0004 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0004.zip |
+| TTC | TS-3GB-N.S0004-0v1.0 | 1 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0004-0v10.pdf |
+
+### 10.2.3 N.S0005-0 – Version 1.0 – Cellular Radiotelecommunications Intersystem Operations (no date)
+
+The purpose of this document is to identify those cellular services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | YDT 1031-1999 | 1.0 | Published | -12-1999 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA/EIA-41-D | | Published | 01-12-1997 | http://www.tiaonline.org/standards/sea_rch_results2.cfm?document_no=TIA%2FEIA%2D41%2DD |
+| TTA | TTAE.3G-N.S0005 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0005.zip |
+
+### 10.2.4 N.S0006 – Version 1.0.0 – PCS Multi-band Based on IS-41-C – Revision: 0 (28 January 2000)
+
+The 3GPP2 document was withdrawn.
+
+### 10.2.5 N.S0008 – Version 1.0 – Circuit Mode Services (no date)
+
+This standard presents a recommended plan for the implementation of Uniform Features for use in the Cellular Radiotelephone Service. Its intent is to describe services and features so that the manner in which a subscriber may place calls using such features and services may remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers.
+
+Services:
+
+- Asynchronous Data Service (ADS);
+- Data Privacy (DP);
+- Group 3 Facsimile Service (G3 Fax);
+- Service Negotiation (SN);
+- Mobile termination functions.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0008 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA-737 | | Published | 01-01-2002 | http://www.tiaonline.org/standards/sea_rch_results2.cfm?document_no=TIA%2D737 |
+| TTA | TTAE.3G-N.S0008 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0008v1_0.pdf |
+| TTC | JP-3GB-N.S0008 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0008.pdf |
+
+### 10.2.6 N.S0009-0 – Version 1.0 – IMSI (no date)
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0009-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA-751 | | Published | 01-01-2002 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D751 |
+| TTA | TTAE.3G-N.S0009 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0009.zip |
+| TTC | JP-3GB-N.S0009 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0009.pdf |
+
+### 10.2.7 N.S0010-0 – Version 1.0 – Advanced features in Wideband Spread Spectrum Systems (no date)
+
+For the revision of this standard, the advanced CDMA features include: Network Directed System Selection (NDSS) and Subscriber Confidentiality (SC) supported by TMSI.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0010-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA-735 | | Published | 01-01-2002 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D735 |
+| TTA | TTAE.3G-N.S0010 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0010-v1.0.pdf |
+| TTC | JP-3GB-N.S0010-0 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0010.pdf |
+
+### 10.2.8 N.S0011-0 – Version 1.0 – OTASP and OTAPA (no date)
+
+This document presents recommendations for supporting the Over-The-Air "Service Provisioning" (OTASP) and "Parameter Administration" (OTAPA) capability.
+
+Specifically, this document includes Stage-1 recommendations for OTASP Subscriber Feature and OTAPA Network Feature Descriptions. It also provides intersystem operation recommendations for supporting the OTASP & OTAPA capability for the CDMA and TDMA air interfaces, with Stage-2 operations and scenarios, Stage-3 operations and parameter definitions plus Stage-3 procedures.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0011-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA/EIA/IS-725-A | | Published | 01-07-1999 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2FEIA%2FIS%2D725%2DA |
+| TTA | TTAE.3G-N.S0011 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0011.zip |
+| TTC | JP-3GB.N.S0011 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0011.pdf |
+
+### 10.2.9 N.S0012-0 – CNAP/CNAR – Revision: 0 (28 January 2000)
+
+This document presents a recommended plan for the implementation of Calling Name Presentation (CNAP) and Calling Name Restriction (CNAR) for use in the Wireless Radiotelephone Service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0012-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA-764 | | Published | 01-01-2002 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D764 |
+| TTA | TTAE.3G-N.S0012 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0012.zip |
+| TTC | JP-3GB-N.S0012 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0012.pdf |
+
+### 10.2.10 N.S0013-0 – Version 1.0 – WIN Phase 1 (no date)
+
+The Wireless Intelligent Network (WIN) is a network which supports the use of intelligent network capabilities to provide seamless terminal services, personal mobility services and advanced network services in mobile environment.
+
+This document presents a recommended plan for the implementation of the Wireless Intelligent Network (WIN) for use in the Wireless Radiotelephone Service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-------------------|------------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0013-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA/EIA/IS-771 | | Published | 01-07-1999 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2FEIA%2FIS%2D771 |
+| | TIA/EIA/IS-771-1 | Addendum 1 | Published | 01-08-2001 | |
+| TTA | TTAE.3G-N.S0013 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0013.zip |
+| TTC | JP-3GB-N.S0013 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0013.pdf |
+
+### 10.2.11 N.S0014-0 – Version 1.0 – Authentication Enhancements (no date)
+
+This standard presents a recommended plan for the implementation of authentication enhancements for use in the Wireless Radiotelephone Service. Its intent is to describe the authentication enhancements so that the manner in which a system implements them may remain reasonably consistent from system to system.
+
+The authentication enhancements include:
+
+- Count Update after Handoff;
+- Obtaining subscriber profile before authentication on initial system access;
+- Handling of suspicious call originations;
+- Identifying the Serving MSC when reporting the outcome of a requested authentication operation;
+
+- Handling of authentication capable mobile stations when the home system is not authentication capable;
+- Clarification and editorial correction of authentication procedures;
+- Miscellaneous authentication enhancements.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0014-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA/EIA/IS-778 | | Published | 01-03-1999 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2FEIA%2FIS%2D778 |
+| TTA | TTAE.3G-N.S0014 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0014.zip |
+| TTC | JP-3GB-N.S0014 | 1 | TTC
Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0014.pdf |
+
+### 10.2.12 N.S0015 – Version 1.0.0 – ANSI-41-D Miscellaneous Enhancements (28 January 2000)
+
+This document is intended to justify *TIA/EIA-41-D* technical enhancement or technical correction contributions that have been supported for incorporation into PN-3590 (*TIA/EIA-41-E*) but are not expected to be published in a *TIA/EIA-41-D* enhancement Interim Standard (IS).
+
+This document is for tracking purposes only, there is no intention of publishing the contents of this document independent of ANSI/TIA/EIA-41-E.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0015 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-N.S0015
v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0015v1.0.0.pdf |
+
+### 10.2.13 N.S0016-0 – Version 1.0 – TIA/EIA-41-D Internationalization (no date)
+
+This document specifies the ANSI/TIA/EIA-41-D Chapters 1, 3, 5 and 6 enhancements that are necessary to support international intersystem operations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------------|------------|------------------------|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0016-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA/EIA/IS-807
TIA/EIA/IS-807-1 | Addendum 1 | Published
Published | 01-08-1999
01-03-2000 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2FEIA%2FIS%2D807 |
+| TTA | TTAE.3G-N.S0016 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0016.zip |
+| TTC | JP-3GB-N.S0016 | 1 | TTC
Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0016.pdf |
+
+### 10.2.14 N.S0017-B – Version 1.0.0 – International Implementation of Wireless Telecommunication Systems Compliant with TIA/EIA-41 – Revision: B (December 2002)
+
+When the first edition of Mobile Station – Land Station Compatibility Specification (*IS-3*, now *TIA/EIA-553-A*) was issued, it was envisioned that it would be adopted for use within Northern America. Provisions were included for international implementation; however, detailed guidelines to assist with such implementations were not included. Subcommittee TR-45.2 recognized the need to provide such guidance, and charted a Working Group (Working Group VI) with this responsibility. The result of this Working Group's deliberations has been the production of TSB-29 as well as ongoing internationalization of other TIA standards, such as *TIA/EIA-41-D (N.S0005)*, *TIA-751 (N.S0009)*, *TIA/EIA/IS-807 (N.S0016)*, *TIA/EIA/IS-875 (N.S0027)*, *TIA/EIA-124 (N.S0026)*, *TIA/EIA-136*, *IS-95*, *IS-91* and *TIA/EIA-2000 (C.S0001)*. TSG-N has taken TSB-29 and produced the specification N.S0017.
+
+The principal aspects of international implementation addressed by this document are:
+
+- the administration and assignment of System Identification Numbers (SIDs);
+- the administration and assignment of Mobile Identification Numbers (MINs);
+- format of International Mobile Subscriber Identifiers (IMSIs);
+
+The goal of this publication is to provide the international wireless telecommunications industry with the framework permitting the coordinated implementation of Wireless Radio Telecommunication Systems in compliance with the provisions of the AMPS family of air interface standards (e.g., *TIA/EIA-553*, *IS-54*, *IS-91*, *IS-95*, *TIA/EIA-2000* and *TIA/EIA-136*).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-N.S0017-B | 1.0.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 |
+| TIA | TSB-29E | | Published | 27-12-2002 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TSB29%2DE |
+| TTA | TTAT.3G-N.S0017-B_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-N.S0017-B_v1.0.zip |
+| TTC | TS-3GB-N.S0017-Bv1.0 | 1 | TTC Published | 30-05-2003 | http://www.ttc.or.jp/imt2000/ts/sns0017-Bv10.pdf |
+
+### 10.2.15 N.S0018 – Version 1.0.0 – TIA/EIA-41-D Prepaid Charging (14 July 2000)
+
+Pre-Paid Charging (PPC) allows the subscriber to pay for voice telecommunication services prior to usage. This document presents a recommended plan for the implementation of Wireless Intelligent Network (WIN) capabilities that support PPC. The WIN capabilities that support PPC are for use in the Wireless Radiotelephone Service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0018 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA/EIA/IS-826 | | Published | 01-09-2000 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2FEIA%2FIS%2D826 |
+| TTA | TTAE.3G-N.S0018 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0018.zip |
+| TTC | JP-3GB-N.S0018 | 2 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpns0018.pdf |
+
+### **10.2.16 N.S0019 – Version 1.0.0 – Intersystem Link Protocol – Revision: 0 (28 January 2000)**
+
+This document specifies an Intersystem Link Protocol (ISLP) for circuit-mode data services. These data services include Asynchronous Data Service (ADS) and Group-3 Fax as specified in IS-99 and IS-135. The ISLP adapts between air-interface data rates and higher-speed intersystem rates. The ISLP may be used between a serving system and an anchor system, possibly through one or more tandem systems.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0019 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA-728 | | Published | 01-01-2000 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D728 |
+| TTA | TTAE.3G-N.S0019 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0019.zip |
+| TTC | JP-3GB-N.S0019 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpns0019.pdf |
+
+### **10.2.17 N.S0020 – TIA/EIA-41-D – Message Segmentation (August 1999)**
+
+The 3GPP2 document was withdrawn.
+
+### **10.2.18 N.S0021 – Version 1.0.0 – User Selective Call Forwarding – Revision: 1 (14 July 2000)**
+
+This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the User Selective Call Forwarding (USCF) feature.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0021 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA/EIA/IS-838 | | Published | 01-07-2000 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2FEIA%2FIS%2D838 |
+| TTA | TTAE.3G-N.S0021 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0021v1.0.0.pdf |
+| TTC | JP-3GB-N.S0021 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpns0021.pdf |
+
+### **10.2.19 N.S0022 – Version 1.0.0 – Answer Hold (14 July 2000)**
+
+This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the Answer Hold (AH) feature.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0022 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA/EIA/IS-837 | | Published | 01-09-2000 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2FEIA%2FIS%2D837 |
+| TTA | TTAE.3G-N.S0022 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-N_S0022v1.0.0.pdf |
+| TTC | JP-3GB-N.S0022 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpns0022.pdf |
+
+### 10.2.20 N.S0023-0 – Version 1.0 – Automatic Code Gapping (no date)
+
+This document presents a recommended plan for the implementation of Automatic Code Gapping (ACG) for use in the Wireless Radiotelephone Service. ACG is used to reduce the rate at which a network entity, typically an MSC, sends service request messages to a service control function (SCF) network entity. ACG controls can be applied automatically by the SCF when it is in overload. ACG controls can also be applied by an SCF for purposes of SCF service management.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0023-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA/EIA/IS-786 | | Published | 01-11-2000 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2FEIA%2FIS%2D786 |
+| TTA | TTAE.3G-N.S0023-0 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0023-0v1.0.pdf |
+| TTC | JP-3GB-N.S0023 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpn/s0023.pdf |
+
+### 10.2.21 N.S0024-0 – Version 1.0 – Network support for MDN-Based Message Centres (November 2000)
+
+This document is intended to identify *TIA/EIA-41-D* WNP-PH3 (Wireless Number Portability – Phase III) technical enhancements required to support SMS (Short Message Service) delivery to MDN (Mobile Directory Number) based MCs (Message Centres). These enhancements have been supported for incorporation into PN-3590 (*TIA/EIA-41-E*) and are being published as a *TIA/EIA-41-D* enhancement Interim Standard (IS).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0024-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA/EIA/IS-841 | | Published | 01-09-2000 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2FEIA%2FIS%2D841 |
+| TTA | TTAE.3G-N.S0024-0 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0024-0v1.0.pdf |
+| TTC | TS-3GB-N.S0024v1.0 | 1 | TTC Published | 29-08-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0024-v10.pdf |
+
+### 10.2.22 N.S0025 – Version 1.0.0 – Roamer Database Verification (January 2001)
+
+This document presents a recommended plan for the implementation of Roamer Database Verification (RDV) for use in the Wireless Radiotelephone Service. RDV enables a home system to verify that a roaming partner's VLF database is correctly loaded for the MSID number ranges that "belong" to the home service provider. At the request of the HLR, the VLR examines its roamer database to verify that subscribers within the requested MSID range are allowed to roam in the visited system.
+
+RDV provides a tool to assist in resolving problems experienced by home system subscribers when roaming in the visited system.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0025 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-N.S0025 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0025v1.0.0.pdf |
+| TTC | TS-3GB-N.S0025v1.0 | 1 | TTC
Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0025-v10.pdf |
+
+##### 10.2.22.1 N.S0025-A – Version 1.0.0 – Roamer Database Verification – Revision: A (June 2002)
+
+This document presents a recommended plan for the implementation of Roamer Database Verification (RDV) for use in the Wireless Radiotelephone Service.
+
+Several types of network entities (NE) can initiate RDV service queries to verify the contents of databases relating to roaming in other network entities.
+
+RDV enables a home system to verify that a roaming partner's VLF database is correctly loaded for the MSID number ranges that "belong" to the home service provider. At the request of the HLR, the VLR examines its roamer database to verify that subscribers within the requested MSID range are allowed to roam in the visited system.
+
+RDV provides a tool to assist in resolving problems experienced by home system subscribers when roaming in the visited system.
+
+RDV may also be used to verify other message routing databases that may be used to support newer capabilities introduced in *IS-41-C* or in subsequent intersystem standards, including three message routing databases that may be maintained at an MSC and two message routing databases that may be maintained at an MC.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0025-A | 1.0.0 | Published | -09-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC |
+| TIA | TIA/EIA/IS-847-A | | Published | 01-07-2002 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA/EIA/IS-847-A |
+| TTA | TTAT.3G-N.S0025-A v1.0.0 | 1.0.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-N.S0025-A_v1.0.0.zip |
+
+##### 10.2.22.2 N.S0025-B – Version 1.0.0 – Roamer Database Verification – Revision: B (October 2002)
+
+This document presents a recommended plan for the implementation of Roamer Database Verification (RDV) for use in the Wireless Radiotelephone Service.
+
+Several types of network entities (NE) can initiate RDV service queries to verify the contents of databases relating to roaming in other network entities.
+
+RDV enables a home system to verify that a roaming partner's VLF database is correctly loaded for the MSID number ranges that "belong" to the home service provider. At the request of the HLR, the VLR examines its roamer database to verify that subscribers within the requested MSID range are allowed to roam in the visited system.
+
+RDV may also be used to verify other message routing databases that may be used to support newer capabilities introduced in *IS-41-C* or in subsequent intersystem standards, including three message routing databases that may be maintained at an MSC and two message routing databases that may be maintained at an MC.
+
+RDV provides a tool to assist in resolving problems experienced by home system subscribers when roaming in the visited system as well as other message routing database related problems.
+
+This document describes the RDV network capability and the intersystem operations to enable a wireless system to use RDV.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-N.S0025-B | 1.0.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 |
+| TTA | TTAT.3G-N.S0025-B_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-N.S0025-B_v1.0.zip |
+
+### 10.2.23 N.S0026 – Version 1.0.0 – Wireless Radio Telecommunication Intersystem Non-Signalling Data Communication DMH (August 2000)
+
+This standard is complementary to the *ANSI-41, Cellular Radiotelecommunications Intersystem Operations*, series of standards and identifies wireless services specifically involving non-signalling data communications which require intersystem cooperation, presents the general background against which those services are to be provided and summarizes the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations.
+
+This standard describes the messages and procedures required to perform call detail record data transmission between systems.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0026 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA/EIA-124-C | | Published | 13-09-2000 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2FEIA%2D124%2C |
+| TTA | TTAE.3G-N.S0026 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0026v1.0.0.pdf |
+
+##### 10.2.23.1 N.S0026-A – Version 1.0.0 – Wireless Radio Telecommunication Intersystem Non-Signalling Data Communication DMH – Revision A (December 2001)
+
+This standard is complementary to the *ANSI-41, Cellular Radiotelecommunications Intersystem Operations*, series of standards and identifies wireless services specifically involving non-signalling data communications which require intersystem cooperation, presents the general background against which those services are to be provided and summarizes the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations.
+
+This standard describes the messages and procedures required to perform call detail record data transmission between systems.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-N.S0026-A | 1.0.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 |
+| TIA | TIA/EIA-124-D | | Published | 01-12-2001 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2FEIA%2D124%2DD |
+| TTA | TTAT.3G-N.S0026-A_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-N.S0026-A_v1.0.zip |
+
+### 10.2.24 N.S0027 – Version 1.0.0 – Enhanced International Dialing, Calling Number Identification & Callback, Calling Party Category Identification (April 2001)
+
+This document presents a recommended plan for the implementation of enhanced international dialing, calling number identification and callback, and calling party category identification for use in the Wireless Radiotelephone Service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0027 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA/EIA/IS-875 | | Published | 01-05-2001 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2FEIA%2FIS%2D875 |
+| TTA | TTAE.3G-N.S0027 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-N.S0027v1.0.0.pdf |
+| TTC | TS-3GB-N.S0027v1.0 | 1 | TTC
Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsns0027-v10.pdf |
+
+### 10.2.25 N.S0028 – Version 1.0.0 – Network Interworking Between GSM MAP and ANSI-41 MAP Rev. B – Revision: 0 (April 2002)
+
+The 3GPP2 document was superseded by X.S0023-B v1.0.
+
+### 10.2.26 N.S0029 – Version 1.0.0 – TIA/EIA-41 Based Network Enhancements for CDMA Packet Data Service (C-PDS), Phase 1 – Revision: 0 (June 2002)
+
+This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with Packet Data Service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-N.S0029 | 1.0.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC |
+| TIA | TIA/EIA-IS-880 | | Published | -07-2002 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA/EIA/IS-880 |
+| TTA | TTAT.3G-N.S0029-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-N.S0029-0 v1.0.zip |
+| TTC | TS-3GB-N.S0029-0v1.0 | 1 | TTC
Published | 27-08-2002 | http://www.ttc.or.jp/imt2000/ts/tsns0029-0v10.pdf |
+
+### 10.2.27 N.S0030 – Version 1.0.0 – Enhanced Wireless 9-1-1 Phase 2 – Revision: 0 (April 2002)
+
+The 3GPP2 document was withdrawn.
+
+## 10.3 Packet Data specifications
+
+### 10.3.1 P.S0001-A – Version 3.0.0 – Wireless IP Network Standard (16 July 2001)
+
+This standard defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification is based on P.R0001; cdma2000 Wireless IP Network Architecture based on IETF protocols.
+
+This standard defines the two methods for accessing Public networks (Internet) and Private networks (Intranets): Simple IP and Mobile IP, and the required Quality of Service and Accounting support. IETF protocols are widely employed whenever possible to minimize the number of new protocols required and to maximize the utilization of well accepted standards and hence the speed to market. Reference to the required IETF protocols is provided in section 3 of this standard.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-P.S0001-A | 3.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA/EIA/IS-835-A | | Published | 01-05-2001 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2FEIA%2FIS%2D835%2DA |
+| TTA | TTAE.3G-P.S0001-A v3.0.0 | 3.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-P.S0001-Av3.0.0.pdf |
+| TTC | TS-3GB-P.S0001-Av3.0 | 1 | TTC
Published | 29-08-2001 | http://www.ttc.or.jp/imt2000/ts/tsps0001-A-v30.pdf |
+
+### 10.3.2 P.S0001-B – Version 1.0.0 – Wireless IP Network Standard (25 October 2002)
+
+The 3GPP2 document was superseded by X.S0011-C.
+
+### 10.3.3 P.S0001-B – Version 2.0 – cdma2000 Wireless IP Network Standard (September 2004)
+
+The 3GPP2 document was superseded by X.S0011-C.
+
+## 10.4 Services and system aspects specifications
+
+### 10.4.1 S.R0003 – Version 1.0.0 – 3GPP2 System Capability Guide – Release A (20 January 2000)
+
+This document is the 3GPP2 System Capability Guide (SCG) for 3GPP2 wireless telecommunication systems. It is developed and maintained under the auspices of 3GPP2 TSG-S, the TSG for Services and Systems Aspects for 3GPP2.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-------------------|---------|-------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | TR-T13-S.R0003 | 1.0 | ARIB
Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_TR-T13-S.R0003.PDF |
+| CCSA | CWTS-MC-S.R0003 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0003-A | 1 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0003-A.zip |
+
+#### 10.4.1.1 S.R0003-A – Version 1.0 – 3GPP2 System Capability Guide – Release B (14 June 2001)
+
+This document is the 3GPP2 System Capability Guide (SCG) for 3GPP2 wireless telecommunication systems. It is developed and maintained under the auspices of 3GPP2 TSG-S, the TSG for Services and Systems Aspects for 3GPP2.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-------------------|---------|-------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | TR-T13-S.R0003-A | 1.0 | ARIB
Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_TR-T13-S.R0003-A.PDF |
+| CCSA | CWTS-MC-S.R0003-A | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0003-A | 1 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0003-A.zip |
+
+#### 10.4.2 S.R0004 – Version 1.0.0 – Service Implementation Guide – Revision: 0 (20 January 2000)
+
+This Service Implementation document describes and defines features adopted by 3GPP2 TSG-S. The features descriptions may include both Stage 1 and Stage 2 functional levels.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0004 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0004v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0004v1.0.0.pdf |
+
+#### 10.4.3 S.R0005-B – Version 1.0 – Network Reference Model for cdma2000 Spread Spectrum Systems – Revision: B (16 April 2001)
+
+This document recommends the basic 3GPP2 Wireless Network Reference Model.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0005-B | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TSB100-A | | Published | 01-03-2001 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TSB100%2DA |
+| TTA | TTAE.3G-S.R0005-B | 1 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0005-B.zip |
+| TTC | TS-3GB-S.R0005-Bv1.0 | 1 | TTC
Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0005-B-v10.pdf |
+
+#### 10.4.4 S.R0006 – Version 1.0.0 – Wireless Features Description – Revision: 0 (13 December 1999)
+
+This standard presents a recommended plan for the implementation of Uniform Features for use in the Wireless Radiotelephone Service. Its intent is to describe services and features so that the manner in which a subscriber may place calls using such features and services may remain reasonably consistent from system to system. It is not intended that specific service offerings be required of all service providers.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0006 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TIA | TIA/EIA-664-A | | Published | 01-12-2000 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2FEIA%2D664 |
+| TTA | TTAE.3G-S.R0006 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0006v1.0.0.pdf |
+| TTC | JP-3GB-S.R.0006 | 1 | TTC
Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0006.pdf |
+
+#### 10.4.5 S.R0007 – Version 1.0.0 – User Selective Call Forwarding (Stage 1) – Revision: 0 (13 December 1999)
+
+This Interim Standard (IS) presents Stage-1 (new chapter *TIA/EIA-664-B*), Stage-2 (*TIA/EIA-41.3-D* enhancements), and Stage-3 (*TIA/EIA-41.5-D* and *TIA/EIA-41.6-D* enhancements) recommendations for supporting the User Selective Call Forwarding (USCF) feature use in the Wireless Radiotelephone Service.
+
+This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the User Selective Call Forwarding (USCF) feature.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0007 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0007(v.1.0) | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0007_v1.0.zip |
+
+##### 10.4.5.1 S.R0007 – Version 2.1 – User Selective Call Forwarding (Stage 1) (31 January 2001)
+
+This Interim Standard (IS) presents Stage-1 (new chapter *TIA/EIA-664-B*), Stage-2 (*TIA/EIA-41.3-D* enhancements), and Stage-3 (*TIA/EIA-41.5-D* and *TIA/EIA-41.6-D* enhancements) recommendations for supporting the User Selective Call Forwarding (USCF) feature use in the Wireless Radiotelephone Service.
+
+This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the User Selective Call Forwarding (USCF) feature.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0007 v2.1 | 2.1 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0007(v.2.1) | 2.1 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0007_v2.1.zip |
+| TTC | TS-3GB-S.R0007v2.1 | 1 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0007-v21.pdf |
+
+#### **10.4.6 S.R0008 – Version 1.0.0 – Answer Hold (Stage 1) – Revision: 0 (13 December 1999)**
+
+This Interim Standard (IS) presents Stage-1 (new chapter *TIA/EIA-664-B*), Stage-2 (*TIA/EIA-41.3-D* enhancements), and Stage-3 (*TIA/EIA-41.5-D* and *TIA/EIA-41.6-D* enhancements) recommendations for supporting the Answer Hold (AH) feature use in the Wireless Radiotelephone Service.
+
+This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the Answer Hold (AH) feature.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0008 | 2.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0008(V.1.0) | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0008_v1.0.zip |
+
+#### **10.4.6.1 S.R0008 – Version 2.0 – Answer Hold (Stage 1) – Revision: 0 (8 December 2000)**
+
+This Interim Standard (IS) presents Stage-1 (new chapter *TIA/EIA-664-B*), Stage-2 (*TIA/EIA-41.3-D* enhancements), and Stage-3 (*TIA/EIA-41.5-D* and *TIA/EIA-41.6-D* enhancements) recommendations for supporting the Answer Hold (AH) feature use in the Wireless Radiotelephone Service.
+
+This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the Answer Hold (AH) feature.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0008 v2.1 | 2.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0008(V.2.0) | 2.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0008_v2.0.zip |
+| TTC | JP-3GB-S.R0008 | 2 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0008.pdf |
+
+#### **10.4.7 S.R0009-0 v1.0 – User Identity Module (Stage 1) – Revision: 0 (13 December 1999)**
+
+This standard defines the enhancements required for the support of mobile stations equipped with User Identification Modules (UIM). The UIM provides functionality to certain types of mobile stations to enable them to operate in the wireless network.
+
+This document defines requirements for the wireless network to support operation of UIM-equipped mobile stations. A UIM provides compatible mobile stations with the parameters required of Mobile stations operating in the TIA/EIA-41 environment and specific additional functionality unique to UIM-equipped mobile stations.
+
+The UIM can be in one of two forms: either as integrated within the mobile, or removable that can be inserted or removed from the mobile equipment. This document addresses Removable UIM (R-UIM) only.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0009-0 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0009 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0009.zip |
+| TTC | TS-3GB-S.R0009 | 1 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0009-v10.pdf |
+
+#### 10.4.8 S.R0010 – Version 1.0.0 – Preferred Language (Stage 1) – Revision: 0 (13 December 1999)
+
+Preferred Language (PL) provides the subscriber the ability to specify the language for network services.
+
+Network services which could be offered in the subscriber's preferred language include:
+
+- Recorded announcements;
+- Directory assistance;
+- Operator services;
+- Emergency services;
+- "Help" lines;
+- Message Waiting Notification;
+- CNIP *number not available*;
+- CNIP *number restricted*.
+
+If the subscriber's preferred language is not available, service shall be provided in the default language, which shall be determined by the wireless network operator.
+
+PL does not impact a subscriber's ability to originate calls or to receive calls.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0010 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0010 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0010.zip |
+| TTC | JP-3GB-S.R0010 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0010.pdf |
+
+#### 10.4.9 S.R0011 – Version 1.0.0 – Advice of Charge (Stage 1) – Revision: 0 (13 December 1999)
+
+This specification presents Stage 1 for supporting the Advice of Charge feature for use in the Wireless Radiotelephone Service.
+
+This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the Advice of Charge (AoC) feature.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0011 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0011 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0011.zip |
+| TTC | JP-3GB-S.R0011 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0011.pdf |
+
+#### **10.4.10 S.R0012 – Version 1.0.0 – Rejection of Undesired Annoying Calls (Stage 1) – Revision: 0 (13 December 1999)**
+
+This specification presents Stage 1 for supporting Rejection of Undesired Annoying Calls feature for use in the Wireless Radiotelephone Service.
+
+This document specifies the wireless intersystem network operation enhancements required for supporting roaming subscribers with the Rejection of Undesired Annoying Calls (RUAC) feature.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0012 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0012 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0012.zip |
+| TTC | JP-3GB-S.R0012 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0012.pdf |
+
+#### **10.4.11 S.R0013 – Version 1.0.0 – Global Emergency Call Origination (GECO) – Revision: 0 (13 December 1999)**
+
+This document presents a Stage-1 description for a Global Emergency Call Origination (GECO) which will increase the probability that any user can originate a call to a Public Service Access Point (PSAP) even in those service areas where the Emergency Service Access Number (ESAN) is not known to the user.
+
+The intent of GECO is described as follows:
+
+- The MS may provide a means for the user to initiate an emergency call.
+- A special form of the call origination message (defined as a Global Emergency Call Origination Message (GECO\_MSG), may be issued by the MS in lieu of the normal call origination message to indicate that the call origination being requested is an emergency call origination. GECO\_MSGs may be accepted and the GECO call connected by the network from both subscribed and unsubscribed mobiles. The system may support "implicit registration" for GECO calls such that the use of registration request/acceptance protocol is not required prior to the issuance of a GECO\_MSG.
+- If the MS is currently registered on and accessing an operating network when the GECO call is initiated by the user, the MS may use that system to initiate the GECO call. If the MS is not currently accessing a system, the MS may attempt to access its preferred service as indicated by its internal system selection and system access restriction programming to maximize the probability that the GECO call will be accepted by the system. If no preferred system is available, the MS may override its internal system selection and system access restriction programming in an attempt to access any available system.
+- Initiation of GECO call by the MS shall in no way degrade the user's access to any other feature/service which would normally be available to him from the accessed service provider's network.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0013 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0013 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0013.zip |
+| TTC | JP-3GB-S.R0013 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0013.pdf |
+
+#### **10.4.12 S.R0014 – Version 1.0.0 – Tandem Free Operation (Stage 1) – Revision: 0 (13 December 1999)**
+
+It is expected that the need for Tandem Free Operations will be driven by the increasing market penetration of digital technologies which will result in an increase in percentage of mobile-to-mobile calls. In addition, given that the effects of tandem vocoding are greater for lower bit rate vocoders, the need for this feature becomes greater as the use of low bit rate vocoders increases. The Tandem Free Operation (TFO) feature, also known as Vocoder Bypass, improves the end-to-end voice quality observed in mobile-to-mobile voice calls in wireless networks.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0014 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0014 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0014.zip |
+| TTC | JP-3GB-S.R0014 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0014.pdf |
+
+#### **10.4.13 S.R0015 – Version 1.0.0 – ISDN Interworking (Stage 1) – Release A (13 December 1999)**
+
+This document presents Stage 1 (new chapter TIA/EIA-664-B) recommendations for supporting the ISDN Interworking feature use in Wireless Radiotelephone Service.
+
+This document specifies the wireless intersystem network operation enhancements required for supporting subscribers with the ISDN Interworking feature. This document defines the functional characteristics for interconnecting to ISDN in circuit-switched mode. The interworking function in ISDN packet mode, i.e., B-channel Packet is out of scope at present.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0015 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0015 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0015.zip |
+| TTC | JP-3GB-S.R0015 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0015.pdf |
+
+#### 10.4.14 S.R0016 – Version 1.0.0 – Automatic Code Gapping (Stage 1) – Revision: 0 (13 December 1999)
+
+Automatic Code Gapping (ACG) is intended to provide a Network Entity, such as a Service Control Point (SCP) or Service Control Function (SCF), the ability to turn off selected types of traffic that may be passing through its domain of operation. The purpose for ACG may be load related or in response to a traffic engineering command as from a Service Management System (SMS). This report provides a general description of ACG as it applies to 3G network operations. Specific applications will be defined in other documents or later versions of this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0016 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0016 (V.1.0) | 1 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0016.zip |
+
+#### 10.4.14.1 S.R0016 – Version 2.0 – Automatic Code Gapping (Stage 1) – Revision: 0 (8 December 2000)
+
+Automatic Code Gapping (ACG) is intended to provide a Network Entity, such as a Service Control Point (SCP) or Service Control Function (SCF), the ability to turn off selected types of traffic that may be passing through its domain of operation. The purpose for ACG may be load related or in response to a traffic engineering command as from a Service Management System (SMS). This report provides a general description of ACG as it applies to 3G network operations. Specific applications will be defined in other documents or later versions of this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0016 v2.0 | 2.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0016(V.2.0) | 2.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0016_v2.0.zip |
+| TTC | JP-3GB-S.R0016 | 2 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0016.pdf |
+
+#### 10.4.15 S.R0017 – 3G Wireless Network Management System High Level Requirements – Revision: 0 (13 December 1999)
+
+This report specifies the 3G Wireless Network Management System High Level Requirements Including: OAM&P TMN Applications Required Network and Systems Management Processes and Network Reference Model (NRM).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0017 | | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0017 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0017.zip |
+| TTC | TR-3GB-S.R0017-0v1.0 | 1 | TTC Published | 26-02-2002 | http://www.ttc.or.jp/imt2000/tr/trsr0017-0v10.pdf |
+
+#### **10.4.16 S.R0018 – Version 1.0.0 – Pre-Paid Charging (Stage 1) – Revision: 0 (13 December 1999)**
+
+PPC allows the subscriber to pay for voice telecommunication services prior to usage.
+
+A PPC subscriber establishes an account with the service provider to access voice telecommunication services in home and roaming networks. Charges for voice telecommunication services are applied to the PPC account by decrementing the account in real time. The PPC subscriber may be notified about the account information at the beginning, during, or at the end of the voice telecommunication service. When the account balance is low the subscriber may be notified so that the subscriber may refill the account. When the account balance is below a pre-defined threshold, the subscriber's use of voice telecommunication services may be de-authorized.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0018 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0018 | 1 | Approved | 13-07-2000 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0018.zip |
+| TTC | JP-3GB-S.R0018 | 1 | TTC Published | 31-03-2000 | http://www.ttc.or.jp/imt2000/std/jpsr0018.pdf |
+
+#### **10.4.17 S.R0019 – Version 1.0.0 – Location-Based Services System (LBSS) – Stage 1 Description (22 September 2000)**
+
+This document defines LBSS for implementation in 3GPP2 systems. The location services functionality has been adopted from existing TR-45 standards as defined and also as described in the following text.
+
+The scope of this document includes 3GPP2 system support required to facilitate Location-Based services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0019 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0019 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0019v1.0.0.pdf |
+| TTC | JP-3GB-S.R0019 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0019.pdf |
+
+#### **10.4.18 S.R0021 – Version 1.0 – Video Streaming Service – Stage 1 (10 July 2000)**
+
+The objective is to define and to standardize the functionality of Video Services that can be incorporated into the operations of wireless telecommunication networks. Audio-only streaming is a special case of video streaming. This document defines the functional characteristics and requirements of the video streaming services. The areas that must be defined are service features and system requirements, necessary for video streaming services to be provided in wireless telecommunication networks.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0021 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0021 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0021v1.0.pdf |
+| TTC | JP-3GB-S.R0021 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0021.pdf |
+
+#### 10.4.18.1 S.R0021 – Version 2.0 – Multimedia Streaming Services – Stage 1 (18 April 2002)
+
+The objective is to define and to standardize the functionality of Multimedia Services that can be incorporated into the operations of wireless telecommunication networks. Audio-only or video only streaming are a special case of multimedia streaming. This document defines the functional characteristics and requirements of the multimedia streaming services. The areas that must be defined are service features and system requirements, necessary for multimedia streaming services to be provided in wireless telecommunication networks.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0021 | 2.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 |
+| TTA | TTAT.3G-S.R0021-0_v2.0 | 2.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0021-0_v2.0.zip |
+| TTC | TS-3GB-S.R0021-0v2.0 | 1 | TTC Published | 27-08-2002 | http://www.ttc.or.jp/imt2000/ts/tsr0021-0v20.pdf |
+
+#### 10.4.19 S.R0022 – Version 1.0 – Video Conferencing Service (10 July 2000)
+
+The objective is to define and to standardize the functionality of Video Services that can be incorporated into the operations of wireless telecommunication networks. This report defines the functional characteristics and the requirements of the video conferencing services. The areas that must be defined are service features and system requirements in order for voice conferencing services to be provided in wireless telecommunication networks.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0022 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0022 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0022v1.0.pdf |
+| TTC | JP-3GB-S.R0022 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0022.pdf |
+
+#### 10.4.20 S.R0023 – Version 1.0 – High-Speed Data Enhancements for cdma2000 1x – Data Only (9 June 2000)
+
+This document outlines the key operator requirements for the evolution of the cdma2000 1x (current versions of C.S0001 through C.S0005) standard. This document will refer to this evolution as 1x evolved high-speed data only (1xEVDO). These requirements are defined to drive improvements to the fundamental packet data capabilities and efficiencies of cdma2000 1x systems to better meet the rapidly evolving needs of subscribers. This report is intended as a guide for wireless operators in the implementation of high-speed data-only systems beyond cdma2000 1x, to provide increased spectral efficiency and the capability to satisfy customer demand for wireless packet data applications.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0023 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0023 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-R0023v1.0.pdf |
+
+#### 10.4.20.1 S.R0023 – Version 2.0 – High-Speed Data Enhancements for cdma2000 1x – Data Only – Stage 1 Requirements (5 December 2000)
+
+This document outlines the key operator requirements for the evolution of the cdma2000 1x (current versions of C.S0001 through C.S0005) standard. This document will refer to this evolution as 1x evolved high-speed data only (1xEVDO). These requirements are defined to drive improvements to the fundamental packet data capabilities and efficiencies of cdma2000 1x systems to better meet the rapidly evolving needs of subscribers. This report is intended as a guide for wireless operators in the implementation of high-speed data-only systems beyond cdma2000 1x, to provide increased spectral efficiency and the capability to satisfy customer demand for wireless packet data applications.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|-------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | TR-T13-S.R0023 v2.0 | 2.0 | ARIB
Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_TR-T13-S.R0023_V2.PDF |
+| CCSA | CWTS-MC-S.R0023 v2.0 | 2.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0023 (v2.0) | 1 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S_R0023_v2.0.zip |
+
+#### 10.4.21 S.R0024 – Version 1.0 – Wireless Local Loop – Stage 1 Description (22 September 2000)
+
+Wireless Local Loop (WLL) is a feature implementation using a serving system that utilizes a wireless connection to a wireless device, such as a mobile station or a network interface unit to provide local loop service to an end user. WLL permits local loop service for subscriber call origination and for receipt of calls. WLL applies to voice and data services. WLL provides signalling mechanisms between the serving system and the mobile station or the network interface unit. This signalling mechanism permits the exchange of call control information.
+
+The essential signalling elements of WLL are:
+
+- Mobile station or Network interface unit Device Type specification and request for WLL of the serving system or optional serving system Device Type specification;
+- Mobile Station or Network interface unit Dial Tone or optional Dial Tone of the serving system;
+- Mobile Station or Network interface unit Hook Status enabling WLL call control of the serving system;
+- Serving system Autonomous Message Interval specification and request of the mobile station or the network interface unit or optional network interface unit Autonomous Message Interval specification;
+- Serving system Call Waiting Indicator notification to the mobile station or the network interface unit.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0024 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0024 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0024v1.0.pdf |
+
+#### 10.4.22 S.R0025 – Version 1.0 – Wireless Pay Phone – Stage 1 Description (22 September 2000)
+
+Wireless Pay Phone is a public telecommunication service feature that allows mobile station support of pay phone applications. The Wireless Pay Phone feature is useful to subscribers that originate or receive calls at a pay phone.
+
+The feature may be comprised of two signalling capabilities. The first signalling capability is that which allows a serving system to convey answer supervision. The second signalling capability is that which allows a serving system to meter calls.
+
+NOTE – A serving system may convey answer supervision using Alert-signalled or Flash-signalled Line Control. A serving system may meter using Alert-signalled or Flash-signalled Meter Pulses.
+
+Answer element of supervision is used by the mobile station to convey line polarity, which is useful as an answer supervision indication. Line Control specification and notification of the mobile station enables specification of Polarity Included, Toggle Mode, Reverse Polarity and Power Denial Time. These are specified in IS-95B section 7.7.5.15.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0025 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0025 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0025v1.0.pdf |
+
+#### 10.4.23 S.R0026 – Version 1.0 – High Speed Data Enhancements for cdma 2000 1x – Integrated Data and Voice – Stage 1 Requirements (17 October 2000)
+
+This document outlines the key operator requirements for the evolution of the cdma2000 1x (current versions of C.S0001 through C.S0005) standard. This document will refer to this evolution as 1x-evolved high-speed integrated data and voice (1xEV-DV). These requirements are defined to drive improvements to the fundamental packet data capabilities and efficiencies of cdma2000 1x systems to better meet the rapidly evolving needs of subscribers. This document is intended as a guide for 3GPP2 TSGs in the development of specifications for high-speed integrated data and voice systems beyond cdma2000 1x services (voice, fax, circuit switched data), to provide increased spectral efficiency and the capability to satisfy customer demand for wireless voice and packet data applications.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0026 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0026 | 1 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0026.zip |
+
+#### **10.4.24 S.R0027 – Version 1 – Personal Mobility – Stage 1 Requirements (8 December 2000)**
+
+The objective is to define and standardize the functionality of personal mobility that can be incorporated into the operations of both 2G/3G TTA/EIA-41 and 2G/3G GSM-derived wireless telecommunications networks. This document defines the requirements of personal mobility features and services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0027 | 1 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0027 | 1 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0027.zip |
+| TTC | JP-3GB-S.R0027 | 1 | TTC Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0027.pdf |
+
+#### **10.4.25 S.S0028 – Version 1.0 – OAM&P for cdma2000 (3GPP Delta Specification) (18 April 2001)**
+
+This document contains the OAM&P requirements and interface definitions for cdma2000-based systems. It is an extension of operations and maintenance requirements, per latest 3GPP 32-series specifications capabilities to enable operation in a cdma2000 systems environment as part of the TTA/EIA/IS-2000 family of standards. They are in alignment with OAM&P Stage 1 IS-2000 requirements.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.S0028 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.S0028 V.1.0 | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_S0028_v1.0.zip |
+| TTC | JP-3GB-S.S0028v1.0 | 1 | TTC Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tsss0028-v10.pdf |
+
+#### **10.4.25.1 S.S0028 – Version 2.0 – OAM&P for cdma2000 (3GPP Delta Specification) (23 July 2001)**
+
+This document is intended to define the OAM&P Stage-2 and Stage-3 requirements and interface definitions for cdma2000-based systems.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.S0028 | 2.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC |
+| TTA | TTAE.3G-S.S0028 (V.2.0) | 2.0 | Approved | 19-12-2001 | http://www.tta.or.kr/imt2000/TTAE_3G-S_S0028_v2.0.zip |
+| TTC | TS-3GB-S.S0028-0v2.0 | 1 | TTC Published | 28-11-2001 | http://www.ttc.or.jp/imt2000/ts/tsss0028-0v20.pdf |
+
+#### **10.4.25.2 S.S0028 – Version 3.0 – OAM&P for cdma2000 (3GPP Delta Specification) (11 March 2002)**
+
+This document is intended to define the OAM&P Stage-2 and Stage-3 requirements and interface definitions for cdma2000-based systems.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.S0028 | 3.0 | Published | -06-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC |
+| TTA | TTAT.3G-S.S0028-0 v3.0 | 3.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.S0028-0 v3.0.zip |
+| TTC | TS-3GB-S.S0028-0v3.0 | 1 | TTC
Published | 28-05-2002 | http://www.ttc.or.jp/imt2000/ts/tsss0028-0v30.pdf |
+
+#### **10.4.25.3 S.S0028-A – Version 1.0 – OAM&P for cdma2000 (3GPP R4 Delta Specification) – Revision: A (12 December 2002)**
+
+This document is intended to define the OAM&P Stage-2 and Stage-3 requirements and interface definitions for cdma2000-based systems.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.S0028-A | 1.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 |
+| TTA | TTAT.3G-S.S0028-A_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-A_v1.0.zip |
+
+#### **10.4.25.4 S.S0028-A – Version 2.0 – OAM&P for cdma2000 (3GPP R4 Delta Specification) – Revision: A (20 February 2003)**
+
+This document is intended to define the OAM&P Stage-2 and Stage-3 requirements and interface definitions for cdma2000-based systems.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|------------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.S0028-A | 2.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 |
+| TTA | TTAT.3G-S.S0028-A_v2.0 | 2.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-A_v2.0.zip |
+| TTC | TS-3GB-S.S0028-Av2.0 | 1 | TTC
Published | 30-05-2003 | http://www.ttc.or.jp/imt2000/ts/tsss0028-Av20.pdf |
+
+#### **10.4.25.5 S.S0028-A – Version 3.0 – OAM&P for cdma2000 (3GPP R4 Delta Specification) – Revision: A (20 February 2003)**
+
+This document is intended to define the OAM&P Stage-2 and Stage-3 requirements and interface definitions for cdma2000-based systems.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.S0028-A | 3.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.S0028-A v3.0 | 3.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-A v3.0.zip |
+| TTC | S.S0028-A v3.0 | 1 | TTC
Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-av30.pdf |
+
+#### 10.4.25.6 S.S0028-000-B – Version 1.0 – OAM&P for cdma2000 (Overview) – (17 February 2005)
+
+The present document is the overview component of a multipart specification intended to define the OAM&P Stage-2 and Stage-3 requirements and interface definitions for CDMA- & cdma2000®-based systems. This multipart specification consists of:
+
+- S.S0028-000-B: "OAM&P for cdma2000 (Overview)";
+- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)";
+- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)";
+- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)";
+- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)".
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.S0028-000-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.S0028-000-B v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-000-B v1.0.zip |
+| TTC | TS-3GB-S.S0028-000-Bv1.0 | 1 | TTC
Published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-000-bv10.pdf |
+
+#### 10.4.25.7 S.S0028-001-B – Version 1.0 – OAM&P for cdma2000 (3GPP R5 Delta Specification) (17 February 2005)
+
+The present document is the 3GPP R5 Delta Specification component of a multipart specification intended to define the OAM&P Stage-2 and Stage-3 requirements and interface definitions for CDMA- & cdma2000®-based systems. This multipart specification consists of:
+
+- S.S0028-000-B: "OAM&P for cdma2000 (Overview)";
+- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)";
+- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)";
+- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)";
+- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM)".
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.S0028-001-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.S0028-001-B v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-001-B v1.0.zip |
+| TTC | TS-3GB-S.S0028-001-Bv1.0 | 1 | TTC
Published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-001-bv10.pdf |
+
+2 cdma2000® is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of publication) cdma2000® is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States.
+
+#### 10.4.25.8 S.S0028-001-B – Version 2.0 – OAM&P for cdma2000 (3GPP R5 Delta Specification) – Revision: B (18 July 2005)
+
+The present document is the 3GPP R5 Delta Specification component of a multipart specification intended to define the OAM&P Stage-2 and Stage-3 requirements and interface definitions for CDMA- & cdma2000®-based systems. This multipart specification consists of:
+
+- S.S0028-000-B: "OAM&P for cdma2000 (Overview)";
+- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)";
+- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)";
+- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)";
+- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM)".
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.S0028-001-B | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.S0028-001-B v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-001-B v2.0.zip |
+| TTC | S.S0028-001-B v2.0 | 1 | TTC
Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-001-bv20.pdf |
+
+#### 10.4.25.9 S.S0028-002-B – Version 1.0 – OAM&P for cdma2000 (3GPP2 Generic NRM IRP) (17 February 2005)
+
+The present document is the 3GPP2 Generic NRM IRP component of a multipart specification intended to define the OAM&P Stage-2 and Stage-3 requirements and interface definitions for CDMA- & cdma2000®-based systems. This multipart specification consists of:
+
+- S.S0028-000-B: "OAM&P for cdma2000 (Overview)";
+- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)";
+- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)";
+- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)";
+- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM)".
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.S0028-002-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.S0028-002-B v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-002-B v1.0.zip |
+| TTC | TS-3GB-S.S0028-002-Bv1.0 | 1 | TTC
Published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-002-bv10.pdf |
+
+#### 10.4.25.10 S.S0028-003-B – Version 1.0 – OAM&P for cdma2000 (3GPP2 Core NRM IRP) (17 February 2005)
+
+The present document is the 3GPP2 Core NRM IRP component of a multipart specification intended to define the OAM&P Stage-2 and Stage-3 requirements and interface definitions for CDMA- & cdma2000®-based systems. This multipart specification consists of:
+
+- S.S0028-000-B: "OAM&P for cdma2000 (Overview)";
+- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)";
+- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)";
+
+- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)";
+- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)".
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.S0028-003-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.S0028-003-B v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-003-B v1.0.zip |
+| TTC | TS-3GB-S.S0028-003-Bv1.0 | 1 | TTC
Published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-003-bv10.pdf |
+
+#### 10.4.25.11 S.S0028-003-B – Version 2.0 – OAM&P for cdma2000 (3GPP2 Core NRM IRP) – Revision: B (18 July 2005)
+
+The present document is the 3GPP2 Core NRM IRP component of a multipart specification intended to define the OAM&P Stage-2 and Stage-3 requirements and interface definitions for CDMA- & cdma2000®-based systems. This multipart specification consists of:
+
+- S.S0028-000-B: "OAM&P for cdma2000 (Overview)";
+- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)";
+- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)";
+- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)";
+- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)".
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.S0028-003-B | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.S0028-003-B v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-003-B v2.0.zip |
+| TTC | S.S0028-003-B v2.0 | 1 | TTC
Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-003-bv20.pdf |
+
+#### 10.4.25.12 S.S0028-004-B – Version 1.0 – OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP) (17 February 2005)
+
+The present document is the 3GPP2 Radio Access NRM IRP component of a multipart specification intended to define the OAM&P Stage-2 and Stage-3 requirements and interface definitions for CDMA- & cdma2000®-based systems. This multipart specification consists of:
+
+- S.S0028-000-B: "OAM&P for cdma2000 (Overview)";
+- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)";
+- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)";
+- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)";
+- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)".
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.S0028-004-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.S0028-004-B v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-004-B v1.0.zip |
+| TTC | TS-3GB-S.S0028-004-Bv1.0 | 1 | TTC
Published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-004-bv10.pdf |
+
+#### 10.4.25.13 S.S0028-004-B – Version 2.0 – OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP) (17 February 2005)
+
+The present document is the 3GPP2 Radio Access NRM IRP component of a multipart specification intended to define the OAM&P Stage-2 and Stage-3 requirements and interface definitions for CDMA- & cdma2000®-based systems. This multipart specification consists of:
+
+- S.S0028-000-B: "OAM&P for cdma2000 (Overview)";
+- S.S0028-001-B: "OAM&P for cdma2000 (3GPP R5 Delta Specification)";
+- S.S0028-002-B: "OAM&P for cdma2000 (3GPP2 Generic NRM IRP)";
+- S.S0028-003-B: "OAM&P for cdma2000 (3GPP2 Core NRM IRP)";
+- S.S0028-004-B: "OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)".
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.S0028-004-B | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.S0028-004-B v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0028-004-B v2.0.zip |
+| TTC | S.S0028-004-B v2.0 | 1 | TTC
Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsss0028-004-bv20.pdf |
+
+#### 10.4.26 S.R0029 – Version 1.0.0 – Access Control Based on Call Type (22 September 2000)
+
+This document defines requirements for the cdma2000 Air Interface to support Access Control based on Call Type (ACCT). ACCT provides the control of access attempt from mobile stations by service option or a set of service options.
+
+Control for terminating calls to mobile stations is outside the scope of this feature description.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0029 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0029 v1.0.0 | 1.0.0 | Approved | 28-10-2002 | http://www.tta.or.kr/standardDB/stnfile/TTAE.3G-S.R0029v1.0.0.pdf |
+| TTC | TS-3GB-S.R0029v1.0 | 1 | TTC
Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0029-v10.pdf |
+
+#### 10.4.27 S.R0030 – Version 1.0 – Broadcast/Multicast Services – Stage 1 (22 August 2001)
+
+The objective of this document is to define and to standardize the functionality of Broadcast/Multicast Services that can be incorporated into the operations of cdma2000-based wireless telecommunications networks. This document defines the functional characteristics and requirements of Broadcast/Multicast services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0030 | 1.0.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC |
+| TTA | TTAE.3G-S.R0030-0 v1.0 | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/imt2000/TTAE.3G-S.R0030-0 v1.0.zip |
+| TTC | TS-3GB-S.R0030-0v1.0 | 1 | TTC
Published | 28-11-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0030-0v10.pdf |
+
+#### 10.4.27.1 S.R0030-A – Version 1.0 – Broadcast/Multicast Services – Stage 1 – Revision A (15 January 2004)
+
+The objective of this document is to define and to standardize the functionality of Broadcast/Multicast Services that can be incorporated into the operations of cdma2000-based wireless telecommunication networks. This document defines the functional characteristics and requirements of Broadcast/Multicast services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0030-A v1.0 | 1 | Approved | 15-01-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TTA | TTAT.3G-S.R0030-A v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0030-A v1.0.zip |
+| TTC | TS-3GB-S.R0030-Av1.0 | 1 | TTC
Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0030-av10.pdf |
+
+#### 10.4.28 S.R0032 – Version 1.0 – Enhanced Subscriber Authentication (ESA) and Enhanced Subscriber Privacy (ESP) (6 December 2000)
+
+This document defines requirements for the cdma2000 Air Interface to support Enhanced Subscriber Authentication (ESA) and Enhanced Subscriber Privacy (ESP). ESA provides enhanced security in authentication and ESP provides enhanced privacy of user data. Selection of cryptographic algorithms is outside the scope of this feature description.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0032 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0032 | 1 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0032.zip |
+| TTC | JP-3GB-S.R0032 | 1 | TTC
Published | 14-05-2001 | http://www.ttc.or.jp/imt2000/std/jpsr0032.pdf |
+
+#### 10.4.29 S.R0033 – Version 1.0 – Realm Configured Packet Data Session Dormancy Timer (6 December 2001)
+
+This document specifies the requirements for the operations of the RC-PDSDT (Realm Configured Packet Data Session Dormancy Timer) feature from the perspective of the user(s) and/or the system operator. The RC-PDSDT is a timer which is used to measure the duration of dormancy of a packet data session. The purpose of this timer is similar to the packet data inactivity timer specified in the C.S0017 standard.
+
+The objective is to define and to standardize the functionality of this feature/service that can be incorporated into the operations of cdma2000-based wireless telecommunication networks.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0033 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC |
+| TTA | TTAT.3G-S.R0033-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT_3G-S.R0033-0_v1.0.zip |
+
+#### 10.4.30 S.R0034 – Version 1.0 – User Identification Module ID Manufacturer's Code Assignment Guidelines and Procedures (18 April 2001)
+
+These guidelines are based on the content of the ANSI TIA/EIA-41 "Family of Standards" (e.g., AMPS (*EIA/TIA-553*), CDMA (*TIA/EIA-95 and TIA/EIA/IS-2000*), and TDMA (*IS-54, IS-136*). It is recommended that systems which are based on the ANSI TIA/EIA-41 family of standards and which are deployed outside of the United States follow these guidelines.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0034 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0034 | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0034.zip |
+| TTC | TS-3GB-S.R0034v1.0 | 1 | TTC
Published | 29-05-2001 | http://www.ttc.or.jp/imt2000/ts/ssr0034-v10.pdf |
+
+#### 10.4.30.1 S.R0034 – Version 2.0 – User Identification Module ID Manufacturer's Code Assignment Guidelines and Procedures (29 August 2002)
+
+These guidelines are based on the content of the ANSI TIA/EIA -41 "Family of Standards" (e.g., AMPS (*EIA/TIA-553*), CDMA (*TIA/EIA-95 and TIA/EIA/IS-2000*), and TDMA (*IS-54, IS-136*). It is recommended that systems which are based on the ANSI TIA/EIA-41 family of standards and which are deployed outside of the United States follow these guidelines. This is to facilitate international roaming and to minimize fraud.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0034 | 2.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 |
+| TTA | TTAT.3G-S.R0034-0_v2.0 | 2.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT_3G-S_R0034-0_v2.0.zip |
+| TTC | TS-3GB-S.R0034-0v2.0 | 1 | TTC
Published | 26-11-2002 | http://www.ttc.or.jp/imt2000/ts/ssr0034-0v20.pdf |
+
+#### 10.4.31 S.R0037-0 – Version 2.0 – IP Network Architecture Model for cdma2000 Spread Spectrum Systems (14 May 2002)
+
+The 3GPP2 document is superseded by S.R0037-0 Version 3.
+
+### 10.4.31.1 S.R0037-0 – Version 3.0 – IP Network Architecture Model for cdma2000 Spread Spectrum Systems (21 August 2003)
+
+This document recommends the basic 3GPP2 Wireless IP Network Architecture Model.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0037-0 v3.0 | | Published | 21-08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TTA | TSB-151 | 3 | Published | 01-12-2003 | http://www.ttaonline.org/standards/search_results2.cfm?document_no=TSB%2D151 |
+| TTA | TTAT.3G-S.R0037-0 V3.0 | 3.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0037-0 v3.0.zip |
+| TTC | TS-3GB-S.R0037-0V3.0 | 1 | TTC
Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsr0037-0v30.pdf |
+
+### 10.4.32 S.R0048 – Version 1.0 – 3G Mobile Equipment Identifier (MEID) (10 May 2001)
+
+The objective of this document is to define and standardize the structure of the 3G Mobile Equipment Identifier.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0048 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-R/M.1457/M.1457-4/MC |
+| TTA | TTAE.3G-S.R0048-0(V.1.0) | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/standardDB/stnfile/TTAE_3G-S_R0048 v1.0.zip |
+| TTC | TS-3GB-S.R0048v1.0 | 1 | TTC
Published | 29-08-2001 | http://www.ttc.or.jp/imt2000/ts/tsr0048-v10.pdf |
+
+### 10.4.32.1 S.R0048-A – Version 1.0 – 3G Mobile Equipment Identifier (MEID) (22 August 2003)
+
+The objective of this document is to define and standardize the structure of the 3G Mobile Equipment Identifier. To facilitate mobile equipment identification and reduce the need to rely on ESNs to track mobiles, the need for a new identifier is required. The Mobile Equipment Identifier (MEID) is proposed as a means to achieve these goals. Additionally, as global roaming and harmonization between 3G technologies become a reality, the need for a universal mobile equipment identifier is needed. The MEID is meant to address these issues.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0048-A v1.0 | 1 | Approved | 22-08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TTA | TTAT.3G-S.R0048-A v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0048-A v1.0.zip |
+| TTC | TS-3GB-S.R0048-Av1.0 | 1 | TTC
Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsr0048-av10.pdf |
+
+### 10.4.32.2 S.R0048-A – Version 2.0 – 3G Mobile Equipment Identifier (MEID) – Stage 1 (22 April 2004)
+
+The objective of this document is to define and standardize the structure of the 3G Mobile Equipment Identifier. To facilitate mobile equipment identification and reduce the need to rely on ESNs to track mobiles, the need for a new identifier is required. The Mobile Equipment Identifier (MEID) is proposed as a means to achieve these goals. Additionally, as global roaming and harmonization between 3G technologies become a reality, the need for a universal mobile equipment identifier is needed. The MEID is meant to address these issues.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0048-A-v2.0 | 1 | Approved | 22-04-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-928-1 | 2 | Approved | 22-04-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D928-1 |
+| TTA | TTAT.3G-S.R0048-A v2.0 | 2.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0048-A v2.0.zip |
+| TTC | TS-3GB-S.R0048-Av2.0 | 1 | TTC
Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/ssr0048-av20.pdf |
+
+### 10.4.32.3 S.R0048-A – Version 3.0 – 3G Mobile Equipment Identifier (MEID) – Stage 1 (23 September 2004)
+
+The objective of this document is to define and standardize the structure of the 3G Mobile Equipment Identifier. To facilitate mobile equipment identification and reduce the need to rely on ESNs to track mobiles, the need for a new identifier is required. The Mobile Equipment Identifier (MEID) is proposed as a means to achieve these goals. Additionally, as global roaming and harmonization between 3G technologies become a reality, a universal mobile equipment identifier is needed. The MEID is meant to address these issues.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0048-A | 3.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.R0048-A v3.0 | | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0048-A v3.0.zip |
+| TTC | TS-3GB-S.R0048-Av3.0 | 1 | TTC
Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/ssr0048-av30.pdf |
+
+### 10.4.32.4 S.R0048-A – Version 4.0 – 3G Mobile Equipment Identifier (MEID) – Stage 1 (23 June 2005)
+
+The objective of this document is to define and standardize the structure of the 3G Mobile Equipment Identifier.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0048-A | 4.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.R0048-A v4.0 | 4.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0048-A v4.0.zip |
+| TTC | TS-3GB-S.R0048-Av4.0 | 1 | TTC
Published | 03-03-2006 | http://www.ttc.or.jp/imt2000/ts/ssr0048-av40.pdf |
+
+### 10.4.33 S.R0051 – Version 1.0 – Enhanced Message Service (EMS) – Stage 1 Description (25 July 2001)
+
+This document specifies the system requirements for Enhanced Message Service (EMS).
+
+The objective is to define and to standardize the functionality of this capability that can be incorporated into the operation of cdma2000-based wireless telecommunication networks.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0051 | 1.0 | Published | -02-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC |
+| TTA | TTAE.3G-S.R0051-0(v.1.0) | 1.0 | Approved | 19-12-2001 | http://www.tta.or.kr/imt2000/TTAE_3G-S_R0051_v1.0.zip |
+| TTC | TS-3GB-S.R0051-0v1.0 | 1 | TTC
Published | 28-11-2001 | http://www.ttc.or.jp/imt2000/ts/tssr0051-0v10.pdf |
+
+### 10.4.34 S.R0052-0 – Version 1.0 – System Release Guide for the Release (ALPHA) of the cdma2000 System Specifications (15 January 2004)
+
+The 3GPP2 document is renamed as document SC.R2003-002-0 Version 1.0. This document is the System Release Guide (SRG) for the 3GPP2 wireless telecommunication system. It is developed and maintained under the auspices of 3GPP2 TSG-S, the TSG for Services and Systems Aspects for 3GPP2. The objective of this document is to provide an informative overview for and reference to the Release (ALPHA) of the 3GPP2 wireless telecommunication system (cdma2000) capabilities, features and services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0052-0 v1.0 | 1 | Approved | 15-01-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TTA | TTAT.3G-S.R0052-0 v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0052-0_v1.0.zip |
+| TTC | TS-3GB-S.R0052-0v1.0 | 1 | TTC
Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0052-0v10.pdf |
+
+### 10.4.35 S.S0053 – Version 1.0 – Common Cryptographic Algorithms (21 January 2002)
+
+This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mobile station authentication, subscriber message encryption, and encryption key and subscriber voice privacy key generation within wireless equipment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|-------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | STD-T64-S.S0053-0 v1.0 | 1.0 | ARIB
Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_STD-T64-S.S0053-0_V1.0.PDF |
+| TIA | (none) | D.1 | Published | 13-09-2000 | http://ftp.tiaonline.org/tr-45/tr45ahag/public/ |
+| TTA | TTAE.3G-S.S0053 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/imt2000/TTAE.3G-S.S0053-0v1.0.pdf |
+
+### 10.4.36 S.S0054 – Version 1.0 – Interface Specification for Common Cryptographic Algorithms (21 January 2002)
+
+This document describes the interfaces to cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mobile station authentication, subscriber message encryption, and encryption key and subscriber voice privacy key generation within wireless equipment. The procedures are described in detail in Common Cryptographic Algorithms.
+
+The purpose of this specification is to describe the cryptographic functions without revealing the technical details that are subject to export controls under regional laws. It is intended that developers of 3GPP2 specifications for systems using these cryptographic functions use the information in this document in standards that are not subject to export restrictions.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|-------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | STD-T64-S.S0054-0 v1.0 | 1.0 | ARIB
Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_STD-T64-S.S0054-0_V1.0.PDF |
+| TIA | (none) | D.1 | Published | 13-09-2000 | http://ftp.tiaonline.org/tr-45/tr45ahag/public/ |
+| TTA | TTAE.3G-S.S0054 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/imt2000/TTAE.3G-S.S0054-0v1.0.pdf |
+
+### 10.4.37 S.S0055 – Version 1.0 – Enhanced Cryptographic Algorithms (21 January 2002)
+
+This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mutual authentication between mobile stations and base stations, subscriber message encryption, and key agreement within wireless equipment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|-------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | STD-T64-S.S0055-0 v1.0 | 1.0 | ARIB
Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_STD-T64-S.S0055-0_V1.0.PDF |
+| TIA | (none) | A | Published | 13-11-2001 | http://ftp.tiaonline.org/tr-45/tr45ahag/public/ |
+| TTA | TTAE.3G-S.S0055 v1.0 | 1.0 | Approved | 28-10-2002 | http://www.tta.or.kr/imt2000/TTAE.3G-S.S0055-0v1.0.pdf |
+
+#### 10.4.37.1 S.S0055-A – Version 1.0 – Enhanced Cryptographic Algorithms (November 2003)
+
+This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mutual authentication between mobile stations and base stations, subscriber message encryption, and key agreement within wireless equipment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.S0055-A v1.0 | 1 | Approved | -11-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-946 | 1 | Published | 01-06-2003 | http://www.tiaonline.org/standards/sea_rch_results2.cfm?document_no=TIA%2D946 |
+| TTA | TTAT.3G-S.S0055-A V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0055-A v1.0.zip |
+
+### **10.4.37.2 S.S0055-A – Version 2.0 – Enhanced Cryptographic Algorithms (17 January 2005)**
+
+This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mutual authentication between mobile stations and base stations, subscriber message encryption, and key agreement within wireless equipment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|-------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | STD-T64-S.S0055-A v2.0 | 2.0 | ARIB
Published | 29-09-2005 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/T64forQ.1742_5/ARIB_STD-T64-S.S0055-A_v2.0.pdf |
+| CCSA | CCSA-TSD-MC-S.S0055-A | 2.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.S0055-A V2.0 | | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0055-A_v2.0.zip |
+
+### **10.4.37.3 S.S0055-A – Version 3.0 – Enhanced Cryptographic Algorithms (26 September 2005)**
+
+This document describes detailed cryptographic procedures for wireless system applications. These procedures are used to perform the security services of mutual authentication between mobile stations and base stations, subscriber message encryption, and key agreement within wireless equipment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.S0055-A | 3.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.S0055-A v3.0 | 3.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0055-A_v3.0.zip |
+
+### **10.4.38 S.R0057 – Version 1.0 – IP-based Service Architecture System Requirements (9 July 2002)**
+
+This document specifies the system requirements for the "IP-based Service Architecture" from the perspective of the user(s) and/or the network operator for the support of IP multimedia applications.
+
+IP multimedia applications are supported by IP multimedia sessions that use IP connectivity bearers of the all-IP network. This document identifies Stage-1 architectural requirements for the All-IP network to support the applications.
+
+The objective is to define and to standardize the "IP-based Service Architecture" that can be incorporated into the operations of cdma2000-based wireless telecommunication networks.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0057 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC |
+| TTA | TTAT.3G-S.R0057-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0057-0_v1.0.zip |
+| TTC | TS-3GB-S.R0057-0v1.0 | 1 | TTC
Published | 26-11-2002 | http://www.ttc.or.jp/imt2000/ts/tsr0057-0v10.pdf |
+
+#### **10.4.39 S.R0058 – Version 1.0 – IP Multimedia Domain System Requirements (17 April 2003)**
+
+This document specifies the system requirements for and operations of the IP Multimedia Domain (IP-MM Domain) system. The IP Multimedia Domain system encompasses the mobile station, the access network, and the core network. The various major functions and capabilities of the IP-MM Domain system are discussed with a focus on the broad requirements that shall be met in providing those functions and capabilities.
+
+The requirements contained in this document apply to the complete IP Multimedia Domain system. Actual development of Stage-2 and Stage-3 work is expected to be done in a phased manner, with releases of the specifications containing successively more complete implementations of these requirements.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0058 | 1.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 |
+| TTA | TTAT.3G-S.R0058_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0058_v1.0.zip |
+
+#### **10.4.40 S.R0059 – Version 1.0 – Legacy MS Domain – Step 1 – System Requirements (16 May 2002)**
+
+This document specifies the system requirements for and operations of the initial release (step 1) of the Legacy MS Domain (LMSD) of the all-IP network. Each of the functional entities of the LMSD is described with respect to functionality, interfaces and the roles it plays in the functioning of the network.
+
+The requirements contained in this document apply only to the initial step of the LMSD.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0059 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC |
+| TTA | TTAT.3G-S.R0059-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0059-0_v1.0.zip |
+
+#### **10.4.41 S.R0060 – Version 1.0 – Removable User Identity Module (R-UIM)/Mobile Equipment (ME) Interface Testing Stage 1 Description (14 March 2002)**
+
+This document specifies the product conformance objectives to be met by the Removable User Identity Module (R-UIM)/Mobile Equipment (ME) Interface Test Specification. The overall objective of this activity is the development of an industry standard compliance test specification, which can be employed to ensure that R-UIM equipped handsets properly interface with various vendor provided R-UIM cards.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|-------------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | TR-T13-S.R0060-0 v1.0 | 1.0 | ARIB
Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_TR-T13-S.R0060-0_V1.0.PDF |
+| CCSA | CWTS-MC-S.R0060 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC |
+| TTA | TTAT.3G-S.R0060-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0060-0_v1.0.zip |
+
+#### **10.4.42 S.R0061 – Version 1.0 – Wireless Immediate Messaging – Stage 1 Requirements (25 October 2002)**
+
+This document specifies the requirements for and operations of the immediate messaging feature from the perspective of the user(s) and/or the system operator. Immediate Messaging (IM) is one of the most popular services on the Internet because of its near real-time, interactive nature. IM, using Presence information, allows users to determine when their friends are online and communicate with them in near real-time.
+
+The objective is to define and to standardize the functionality of this feature/service that can be incorporated into the operations of 3GPP2-based wireless telecommunication networks. This document makes extensive use of the Internet terminology to ensure alignment with immediate messaging service description and behaviour in Internet recommendations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0061 | 1.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 |
+| TTA | TTAT.3G-S.R0061-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0061-0_v1.0.zip |
+
+#### **10.4.43 S.R0062 – Version 1.0 – Presence for Wireless Systems – Stage 1 Requirements (30 October 2002)**
+
+This document defines Stage-1 level requirements of the presence service from the perspective of the user and the system operator, so that it may be incorporated into cdma2000-based wireless networks. This document limits itself to presence service and does not delve into other applications that make use of presence, such as instant messaging.
+
+Presence is an attribute related to, but quite different from mobility information, and is a service that can be exploited to create additional services. The presence service enables presence information to be made available to other users or services. This Stage 1 makes extensive use of Internet terminology to ensure alignment with the presence service description and behaviour in Internet recommendations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0062 | 1.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 |
+| TTA | TTAT.3G-S.R0062-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0062-0_v1.0.zip |
+
+#### 10.4.44 S.R0064-0 – Version 1.0 – Multimedia Messaging Services (MMS) – Stage 1 Requirements (30 October 2002)
+
+This document defines the Stage-1 description of the non-real time Multimedia Messaging Service (MMS). MMS will allow users to send and receive messages exploiting the whole array of media types available today, e.g., text, images, audio, and video, while also making it possible to support new content types as they become popular. A multimedia message (MM), as observed by the user, is a combination of one or more different media elements in a multimedia presentation that can be transferred without the requirements for the need to be transferred in real time. The multimedia messaging service shall be capable of supporting current and future multimedia types, and exploit the advances being made in the multimedia technology, with additional mobile requirements. Stage 1 is the set of requirements seen primarily from the subscriber's and service providers' points of view. It includes information of relevance to network operators, media content suppliers, service providers, and terminal and network manufacturers.
+
+It contains core requirements for the Multimedia Messaging Service, sufficient to provide a complete service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0064-0 | 1.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 |
+| TTA | TTAT.3G-S.R0064-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0064-0_v1.0.zip |
+| TTC | TS-3GB-S.R0064-0v1.0 | 1 | TTC
Published | 14-02-2003 | http://www.ttc.or.jp/imt2000/ts/tsr0064-0v10.pdf |
+
+#### 10.4.45 S.R0065 – Version 1.0 – Fast Call Set-up – System Requirements (15 April 2002)
+
+This document specifies the system requirements for Fast Call Setup. This feature allows accelerated process in call setup (bearer resource assignment), which is particularly beneficial when a connection is returned from dormancy as a result of a packet arrival to the wireless network. The feature can be considered as falling into the category of standing requirements for network performance improvement.
+
+The objective is to define and to standardize the functionality of this capability that can be incorporated into the operations of cdma2000-based wireless telecommunication networks.
+
+The Fast Call Setup feature is a set of enhancements/mechanisms that reduce the latency involved in MS-terminated and MS-originated call setup.
+
+Call Setup involves a set of signalling message exchange between the Mobile Station, Base Station, and the Network in order to allocate resources and allow user communication to proceed. Each step of this process introduces delay that contributes to the end-to-end call setup latency. Enhancements that reduce the delay in each step of this process and enhancements that streamline this process result in reduced call setup latency which is beneficial to cdma2000 services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0065 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC |
+| TTA | TTAT.3G-S.R0065-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0065-0_v1.0.zip |
+| TTC | TS-3GB-S.R0065-0v1.0 | 1 | TTC
Published | 27-08-2002 | http://www.ttc.or.jp/imt2000/ts/tsr0065-0v10.pdf |
+
+#### 10.4.46 S.R0066-0 – Version 1.0 – IP Based Location Services – Stage 1 Requirements (17 April 2003)
+
+This version of the Stage 1 supports location through IP in current packet data connections offered in cdma2000. SIP-based services in the all-IP domain (MMD), such as VoIP, are not assumed to be supported. Thus, deployment of IP-based Location Services will be possible prior to a full standardization and deployment of MMD. By the same token, there is no concept of an "emergency call" in the current packet data domain.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0066-0 | 1.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 |
+| TIA | TIA-1020 | 1.0 | Approved | 17-04-2003 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-S.R0066-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0066-0_v1.0.zip |
+
+#### 10.4.47 S.R0068 – Version 1.0 – Link Layer Assisted Robust Header Compression – Stage 1 Requirements (11 June 2002)
+
+This document specifies the requirements for and operations of the Link Layer Assisted Header Compression (LLA HC) from the perspective of the user and the system operator.
+
+The objective is to define and to standardize the functionality of this feature that can be incorporated into the operations of cdma2000-based wireless telecommunication networks.
+
+The scope of this feature is in support of QoS-enabled packet data service. This feature may also be used to support the all-IP multimedia domain, although all-IP is not the only application.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0068 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC |
+| TTA | TTAT.3G-S.R0068-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0068-0_v1.0.zip |
+| TTC | TS-3GB-S.R0068-0v1.0 | 1 | TTC
Published | 26-11-2002 | http://www.ttc.or.jp/imt2000/ts/tssr0068-0v10.pdf |
+
+#### 10.4.48 S.R0069 – Version 1.0 – Header Stripping and Generation – Stage 1 Requirements (15 March 2002)
+
+This document specifies the requirements for and operations of the header stripping and generation feature from the perspective of the user and the system operator.
+
+The objective is to define and to standardize the functionality of this feature that can be incorporated into the operations of cdma2000-based wireless telecommunication networks.
+
+The scope of this feature is in support of QoS-enabled packet data service. This feature may also be used to support the all-IP multimedia domain, although all-IP is not the only application.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0069 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC |
+| TTA | TTAT.3G-S.R0069-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0069-0_v1.0.zip |
+
+#### **10.4.49 S.R0070 – Version 1.0 – Work Item, Stage 1 and System Requirements Process Guidelines (16 May 2002)**
+
+The 3GPP2 document is renamed as SC.R1003-0 Version 1.0. This document is to provide uniform procedures and guidance for the development, completion, distribution and approval of Work Items, Stage 1 and System Requirements across all TSGs.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0070 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC |
+| TTA | TTAT.3G-S.R0070-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0070-0 v1.0.zip |
+
+#### **10.4.50 S.R0071 – Version 1.0 – Legacy System Packet Data Surveillance Requirements – Stage 1 Requirements (18 April 2002)**
+
+The 3GPP2 Steering Committee found that the Packet Data Surveillance Feature (also known as Packet Data Intercept, Legal Surveillance, Lawful Surveillance, or Electronic Surveillance) was regional in nature and should be left to the appropriate SDOs to develop, with 3GPP2 consulting as requested.
+
+This document serves as a pointer to the appropriate Standards Development Organization (SDO) documents for Packet Data Surveillance (PDS) for 3GPP2 all-IP systems.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0071 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC |
+| TTA | TTAT.3G-S.R0071-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0071-0 v1.0.zip |
+
+#### **10.4.51 S.R0072 – Version 1.0 – All-IP Packet Data Surveillance Requirements – Stage 1 Requirements (18 April 2002)**
+
+The 3GPP2 Steering Committee found that the Packet Data Surveillance Feature (also known as Packet Data Intercept, Legal Surveillance, Lawful Surveillance, or Electronic Surveillance) was regional in nature and should be left to the appropriate SDOs to develop, with 3GPP2 consulting as requested.
+
+This document serves as a pointer to the appropriate Standards Development Organization (SDO) documents for Packet Data Surveillance (PDS) for 3GPP2 all-IP systems.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0072 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC |
+| TTA | TTAT.3G-S.R0072-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0072-0 v1.0.zip |
+
+#### 10.4.52 S.R0073 – Version 1.0 – Internet Over-the-Air Handset Configuration Management (IOTA) – Stage 1 (11 July 2002)
+
+This document specifies the requirements for and operation of Internet-based Over-the-Air Handset Configuration Management (IOTA HCM) from the perspective of the users and system operators.
+
+The objective of this document is to define the requirements of this feature for incorporation into the operations of cdma2000-based wireless telecommunication systems.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CWTS-MC-S.R0073 | 1.0 | Published | -12-2002 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/200306/MC |
+| TTA | TTAT.3G-S.R0073-0 v1.0 | 1.0 | Approved | 21-03-2003 | http://www.tta.or.kr/imt2000/TTAT.3G-S.R0073-0 v1.0.zip |
+| TTC | TS-3GB-S.R0073-0v1.0 | 1 | TTC
Published | 26-11-2002 | http://www.ttc.or.jp/imt2000/ts/tssr0073-0v10.pdf |
+
+#### 10.4.53 S.R0074 – Version 1.0 – File Format for Multimedia Services (FFMS) – Stage 1 Requirements (17 April 2003)
+
+This document specifies the requirements for the file format for multimedia services (FFMS) feature from the perspective of the user(s) and/or the system operator. The objective is to define and to standardize the file that can be used for interchanging multimedia data in general multimedia services including the Multimedia Messaging Services and the Multimedia Streaming Services. Multimedia data will be stored in a single file. Employing a common file format also enables combined services. For example, a multimedia message is sent to and stored in a multimedia streaming server, and then it is used for streaming to a multimedia streaming client terminal. This document does not specify how this file format is used in specific services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0074 | 1.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 |
+| TTA | TTAT.3G-S.R0074_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0074_v1.0.zip |
+
+#### 10.4.54 S.R0075-0 – Version 1.0 – Accounting & Auditing All-IP – System Requirements (17 April 2003)
+
+This document specifies the system requirements for Accounting & Auditing in the all-IP Network Architecture Model (Nam – S.R0037-0). The AAA is the primary functional entity with respect to the Accounting & Auditing functionality, interfaces, and the role it plays in the support of facilities and services message accounting in the network.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0075-0 | 1.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 |
+| TTA | TTAT.3G-S.R0075-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0075-0_v1.0.zip |
+
+#### **10.4.55 S.S0078-0 – Version 1.0 – Common Security Algorithms (12 December 2002)**
+
+This document defines detailed cryptographic procedures for common security algorithms in 3GPP2. The procedures include authentication algorithms and privacy algorithms that are intended to satisfy the export restriction requirements of 3GPP2 Organizational Partners' host countries.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|-------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | STD-T64-S.S0078-0 v1.0 | 1.0 | ARIB
Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_STD-T64-S.S0078-0_V1.0.PDF |
+| CCSA | CCSA-TSD-MC-S.S0078-0 | 1.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 |
+| TTA | TTAT.3G-S.S0078-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0078-0_v1.0.zip |
+
+#### **10.4.55.1 S.S0078-A – Version 1.0 – Common Security Algorithms (13 December 2004)**
+
+This document defines detailed cryptographic procedures for common security algorithms in 3GPP2. The procedures include authentication algorithms and privacy algorithms that are intended to satisfy the export restriction requirements of 3GPP2 Organizational Partners' host countries.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.S0078-A | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.S0078-A v1.0 | | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0078-A v1.0.zip |
+
+#### **10.4.55.2 S.S0078-A – Version 2.0 – Common Security Algorithms (17 January 2005)**
+
+This document defines detailed cryptographic procedures for common security algorithms in 3GPP2. The procedures include authentication algorithms and privacy algorithms that are intended to satisfy the export restriction requirements of 3GPP2 Organizational Partners' host countries.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|-------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | STD-T64-S.S0078-A v2.0 | 2.0 | ARIB
Published | 29-09-2005 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/T64forQ.1742_5/ARIB_STD-T64-S.S0078-A v2_0.pdf |
+| CCSA | CCSA-TSD-MC-S.S0078-A | 2.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.S0078-A v2.0 | | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0078-A v2.0.zip |
+
+### 10.4.55.3 S.S0078-A – Version 3.0 – Common Security Algorithms (26 September 2005)
+
+This document defines detailed cryptographic procedures for common security algorithms in 3GPP2. The procedures include authentication algorithms and privacy algorithms that are intended to satisfy the export restriction requirements of 3GPP2 Organizational Partners' host countries.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.S0078-A | 3.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.S0078-A v3.0 | 3.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0078-A_v3.0.zip |
+
+### 10.4.56 S.R0079-0 – Version 1.0 – Support for End-to-End QoS – Stage 1 Requirements (13 May 2004)
+
+This document describes the requirements necessary to support E2E (End-to-End) QoS in the cdma2000 wireless IP network. The requirements are based on leveraging, and extending where applicable, the standard IETF protocols for QoS. The proposed functionality described by the requirements include the use of intserv, diffserv, intserv to diffserv interworking, network policy and subscriber profile, network provisioning and link layer to upper layer QoS adaptation. The document also specifies the requirements for the cdma2000 Radio Link QoS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0079-0 v1.0 | 1 | Approved | 13-05-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TTA | TTAT.3G-S.R0079-0 v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0079-0_v1.0.zip |
+| TTC | TS-3GB-S.R0079-0v1.0 | 1 | TTC Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0079-0v10.pdf |
+
+### 10.4.57 S.R0080-0 – Version 1.0 – CDMA2000 Wideband Speech Codec – Stage 1 Requirements (20 February 2003)
+
+Wideband speech and audio coding has been gaining popularity in recent years. The emergence of the 3rd generation cellular systems as well as increasing public demand for applications such as Wireless multimedia, Voice over IP, Videophone, ISDN teleconferencing systems, Multipoint interactive audiovisual communication and Audio streaming require improved voice quality and intelligibility. Multimedia services are among the main deliverables of 3G wireless communications. This implies the use of high-quality audio and speech in multimedia content. Even in 3G voice applications, the introduction of wideband speech would be an important step for CDMA service providers to deliver speech quality beyond the traditional limits of wireline communication systems.
+
+This document describes the cdma2000 Wideband Speech Codec Stage-1 requirements.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | TR-T13-S.R0080-0v1.0 | 1.0 | ARIB Published | 29-07-2003 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T/ARIB_ITU-T_Q.1742/ARIB_TR-T13-S.R0080-0_v1.pdf |
+| CCSA | CCSA-TSD-MC-S.R0080-0 | 1.0 | Approved | -09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 |
+| TTA | TTAT.3G-S.R0080-0_v1.0 | 1.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0080-0_v1.0.zip |
+
+#### 10.4.58 S.R0082 – Version 1.0 – Enhanced Packet Data Air Interface Security (22 August 2003)
+
+This document defines requirements for the cdma2000 Air Interface to support Data Subscriber Authentication (DSA) and Data Privacy (DP) for packet data services. DSA provides enhanced security in authentication and DP provides enhanced privacy of user data. DSA provides mutual authentication between the Access Terminal and the serving Access Network. DP provides encryption to prevent signalling and user traffic from unauthorized disclosure, and to prevent hijacking of user data channels.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0082 v1.0 | 1 | Approved | 22-08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TTA | TTAT.3G-S.R0082 v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0082_v1.0.zip |
+| TTC | TS-3GB-S.R0082-0v1.0 | 1 | TTC
Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tssr0082-0v10.pdf |
+
+#### 10.4.59 S.S0083-A – Version 1.0 – Broadcast-Multicast Service Security Framework (26 August 2004)
+
+This document defines the security framework for the Broadcast-Multicast Services (BCMCS). The security framework provides a logical description of the security information, functions and protocols for BCMCS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.S0083-A | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-1053 | 1 | Published | -09-2004 | http://www.tiaonline.org/standards/sea_rch_results2.cfm?document_no=TIA%2D1053 |
+| TTA | TTAT.3G-S.S0083-A v1.0 | | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0083-A_v1.0.zip |
+| TTC | TS-3GB-S.S0083-Av1.0 | 1 | TTC
Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tsss0083-av10.pdf |
+
+#### 10.4.60 S.R0084-0 – Version 2.0 – Prepaid Packet Data Service in cdma2000 Wireless IP Network, Stage 1 Requirements (18 September 2003)
+
+Prepaid service allows the subscriber to pay for packet data services prior to usage. A prepaid subscriber establishes an account with the service provider to access packet data services in home and roaming networks.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0084-0v2.0 | 1 | Approved | 18-09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TTA | TTAT.3G-S.R0084-0 v2.0 | 2.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0084-0_v2.0.zip |
+| TTC | TS-3GB-S.R0084-0v2.0 | 1 | TTC
Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tssr0084-0v20.pdf |
+
+#### **10.4.61 S.R0086-A – Version 1.0 – IMS Security Framework (10 June 2004)**
+
+This document addresses the access and network security for IP-based services. The scope of this technical specification is to specify the security features and mechanisms for secure access to the IM subsystem (IMS) for the 3G mobile telecommunication system.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0086-Av1.0 | 1 | Approved | 10-06-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TTA | TTAT.3G-S.R0086-Av1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0086-Av1.0.zip |
+| TTC | TS-3GB-S.R0086-Av1.0 | 1 | TTC
Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/sssr0086-av10.pdf |
+
+#### **10.4.61.1 S.S0086-B – Version 1.0 – IMS Security Framework (8 December 2005)**
+
+This document addresses the access and network security for IP-based services. The scope of this technical specification is to specify the security features and mechanisms for secure access to the IM subsystem (IMS) for the 3G mobile telecommunication system.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.S0086-B | 1 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-1091 | 1 | Published | 08-12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-S.S0086-B v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0086-B v1.0.zip |
+| TTC | S.S0086-B v1.0 | 1 | TTC
Published | 03-03-2006 | http://www.ttc.or.jp/imt2000/ts/tsss0086-bv10.pdf |
+
+#### **10.4.62 S.R0087-0 – Version 1.0 – 3GPP2-WLAN Interworking – Stage 1 Requirements (22 July 2004)**
+
+This document describes requirements of interworking between 3GPP2 systems 2 and Wireless Local Area Networks (WLANs). The intent of 3GPP2-WLAN 3 Interworking is to extend 3GPP2 packet data services and/or capabilities to the 4 WLAN environment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0087-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.R0087-0 v1.0 | | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0087-0 v1.0.zip |
+| TTC | TS-3GB-S.R0087-0v1.0 | 1 | TTC
Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/sssr0087-0v10.pdf |
+
+#### 10.4.63 S.R0090-0 – Version 1.0 – Network Initiated Data Session (NIDS) – Stage 1 Requirements (10 June 2004)
+
+This document defines the requirements for providing the Network Initiated Data Session (NIDS) capability.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0090-0 v1.0 | 1 | Approved | 10-06-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TTA | TTAT.3G-S.R0090-0 v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0090-0 v1.0.zip |
+| TTC | TS-3GB-S.R0090-0v1.0 | 1 | TTC Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0090-0v10.pdf |
+
+#### 10.4.64 S.R0092-0 – Version 1.0 – Legacy MS Domain – Step 2 – System Requirements (18 March 2004)
+
+This document specifies the system requirements for and operations of the second release (Step 2) of the Legacy MS Domain (LMSD) of the all-IP network. Each of the functional entities of the LMSD is described with respect to functionality, interfaces, and the roles it plays in the functioning of the network.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0092-0 v1.0 | 1 | Approved | 18-03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TTA | TTAT.3G-S.R0092-0 v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0092-0%20v1.0.zip |
+| TTC | TS-3GB-S.R0092-0V1.0 | 1 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0092-0v10.pdf |
+
+#### 10.4.65 S.S0093-0 – Version 1.0 – cdma2000 Network Performance Measurement Types (11 December 2003)
+
+This document defines the Performance Measurement Types applicable to CDMA and cdma2000 systems.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|---------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.S0093-0 v1.0 | 1 | Approved | 11-12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TTA | TTAT.3G-S.S0093-0 v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.S0093-0 v1.0.zip |
+| TTC | TS-3GB-S.S0093-0v1.0 | 1 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0093-0v10.pdf |
+
+#### 10.4.66 S.R0094-0 – Version 1.0 – Rm Interface Enhancements for cdma2000 – System Requirements (17 February 2005)
+
+This document specifies the system requirements for an enhanced Rm Interface. The objective is to define and to standardize the functionality of this interface for incorporation into the operations of cdma2000®-based wireless telecommunication networks.
+
+The Rm Interface is between a Mobile Termination 2 (MT2) and a Terminal Equipment 2 (TE2). An MT2 is a cdma2000 network interface device, such as a hand-held phone. A TE2 is a general-purpose computer such as a laptop. The Rm Interface is currently specified in *Data Service Options for Wideband Spread Spectrum Systems* (C.S0017) to support only a best-effort,
+
+point-to-point packet data link assuming the presence of an RS-232 physical layer. Enhancements are needed to support applications hosted on the TE2 that require Quality of Service (QoS) from the cdma2000 network, and to support a network-layer interface that can be re-used across many different physical layer technologies.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0094-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.R0094-0 v1.0 | | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0094-0 v1.0.zip |
+| TTC | TS-3GB-S.R0094-0v1.0 | 1 | TTC
Published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tssr0094-0v10.pdf |
+
+#### **10.4.67 S.R0095-0 – Version 1.0 – Support for IP Multimedia Services Identity Module (ISIM) on Universal Integrated Circuit Card (UICC) in 3GPP2 Systems – Stage 1 Requirements (10 June 2004)**
+
+This document defines the enhancements required for the support of IMS capable mobile stations equipped with Universal Integrated Circuit Card (UICC). This document specifies the requirements and operations for the support of ISIM on UICC.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0095-0-v1.0 | 1 | Approved | 10-06-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TTA | TTAT.3G-S.R0095-0 v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0095-0 v1.0.zip |
+| TTC | TS-3GB-S.R0095-0v1.0 | 1 | TTC
Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0095-0v10.pdf |
+
+#### **10.4.68 S.R0096-0 – Version 1.0 – Transcoder Free Operation – Stage 1 Requirements (18 March 2004)**
+
+This document states that Transcoder Free Operation (TrFO) is the transport of compressed speech, from legacy mobiles, in a packet transport network through the elimination of unnecessary coding and decoding of the signal by intermediate elements in the bearer path. Transcoders may be associated either with the RAN or Media Gateway (MGW). By transporting only the compressed speech, TrFO achieves bandwidth efficiencies in the bearer stream and reduces round-trip delays introduced by unnecessary transcoding. Also, TrFO may increase voice quality. TrFO is not applicable to VoIP. TrFO is a capability of the Legacy MS domain.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0096-0 v1.0 | 1 | Approved | 18-03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TTA | TTAT.3G-S.R0096-0 v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0096-0 v1.0.zip |
+| TTC | TS-3GB-S.R0096-0v1.0 | 1 | TTC
Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tssr0096-0v10.pdf |
+
+#### **10.4.69 S.R0103-0 – Version 1.0 – Network Firewall Configuration and Control (NFCC) – Stage 1 Requirements (9 December 2004)**
+
+This document specifies the system requirements and operation of the Network Firewall Configuration and Control (NFCC) feature, from both the perspective of the subscriber and the system operator. The objective is to define and to standardize the functionality of this feature to be incorporated into the operations of cdma2000®-based wireless telecommunication networks.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0103-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.R0103-0 v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0103-0 v1.0.zip |
+| TTC | TS-3GB-S.R0103-0v1.0 | 1 | TTC
Published | 03-03-2005 | http://www.ttc.or.jp/imt2000/ts/tssr0103-0v10.pdf |
+
+#### **10.4.70 S.R0104-0 – Version 1.0 – HRPD Network Access Authentication for a Hybrid Access Terminal (HAT) with an R-UIM Used to Access Spread Spectrum Systems – Systems Requirements (21 October 2004)**
+
+A hybrid access terminal (referred to herein as a Hybrid Access Terminal, or HAT) is a device which can access both cdma2000® 1x and HRPD networks for packet data services.
+
+To access the cdma2000 1x network, a HAT that has an R-UIM uses R-UIM-supported CAVE-based authentication. To access the HRPD network, an optional network access authentication step may be required by the HRPD network. This optional step uses CHAP to exchange a challenge and response between the HAT and HRPD network. Currently, CHAP specifies that MD5 is used to compute the response. It is important to note that MD5 is not currently supported by all R-UIMs used to access a cdma2000 1x network.
+
+For an operator that deploys both cdma2000 1x and HRPD networks, there can be benefits to using common authentication credentials and authentication methods for accessing both networks.
+
+These requirements allow a properly configured HAT with an R-UIM to use CAVE-based authentication for access to both networks. These requirements specify the HAT authentication requirements and also the support required by the HRPD AN-AAA to authenticate such a HAT.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0104-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.R0104-0 v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0104-0 v1.0.zip |
+| TTC | TS-3GB-S.R0104-0v1.0 | 1 | TTC
Published | 03-03-2005 | http://www.ttc.or.jp/imt2000/ts/tssr0104-0v10.pdf |
+
+#### **10.4.71 S.R0105-0 – Version 1.0 – Hot-lining Service (Packet Data) – Stage 1 Requirements (8 December 2004)**
+
+This document specifies the system requirements for Hot-lining for packet data service. The objective is to define and to standardize the functionality of this capability that can be incorporated into the operations of cdma2000®-based wireless IP networks.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0105-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.R0105-0 v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0105-0 v1.0.zip |
+| TTC | TS-3GB-S.R0105-0v1.0 | 1 | TTC
Published | 03-03-2005 | http://www.ttc.or.jp/imt2000/ts/tssr0105-0v10.pdf |
+
+#### 10.4.72 S.R0106-0 – Version 1.0 – Packet-Switched Video Telephony – Stage 1 (21 July 2005)
+
+This document defines the functional characteristics and the requirements of the packet-switched Video Telephony (VT) services, sometimes also referred to as Multimedia Conversational Services (MCS). Video Telephony is defined as one-to-one video/speech communication capability.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0106-0 | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.R0106-0 v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0106-0 v1.0.zip |
+| TTC | S.R0106-0 v1.0 | 1 | TTC
Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tssr0106-0v10.pdf |
+
+#### 10.4.73 S.R0111-0 – Version 1.0 – Expanded R-UIM Identifier (26 October 2005)
+
+An expanded R-UIM identifier (EUIM-ID) solution is needed in time to address issues associated with the impending exhaustion of the existing 32-bit UIM\_ID/ESN numbering space in CDMA networks. The purpose of introducing a new identifier is to define a larger numbering space, and also set the stage for moving away from the functions such as authentication and reverse long code mask generation.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0111-0 | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.R0111-0 v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0111-0 v1.0.zip |
+| TTC | S.R0111-0 v1.0 | 1 | TTC
Published | 03-03-2006 | http://www.ttc.or.jp/imt2000/ts/tssr0111-0v10.pdf |
+
+#### 10.4.74 S.R0112-0 – Version 1.0 – Generic Bootstrapping Architecture System Requirements (8 December 2005)
+
+This specification contains the high level requirements for the Generic Bootstrapping Architecture work. The aim of this work is to specify a general method of providing an application and a mobile with some shared keying material. The requirements on how the application and mobile use this shared keying material is out of scope of this specification.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-S.R0112-0 | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-S.R0112-0 v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-S.R0112-0 v1.0.zip |
+| TTC | S.R0112-0 v1.0 | 1 | TTC
Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tssr0112-0v10.pdf |
+
+## 10.5 Core Network Specifications
+
+### 10.5.1 X.S0002-0 – Version 1.0 – TIA/EIA-41-D Location Services Enhancements (- March 2004)
+
+This document presents a recommended plan for the implementation of Location Services Enhancements for use in the Wireless Radiotelephone Service. The purpose of this document is to specify the intersystem operations that enable a wireless system to provide enhanced location services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0002-0 v1.0 | | Approved | -03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-881 | 1.0 | Published | 31-03-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D881 |
+| TTA | TTAT.3G-X.S0002-0 v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0002-0 v1.0.zip |
+| TTC | TS-3GB-X.S0002-0v1.0 | 1 | TTC
Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0002-0v10.pdf |
+
+### 10.5.2 X.S0003-0 – Version 1.0 – One-Way Roaming from X.S0004 to GSM (- January 2005)
+
+This document provides recommended *ANSI/TIA/EIA-41-D* enhancements required to support *TIA/EIA-41* SIM (Subscription Identification Module) roaming one-way into *GSM* serving areas (without modification to the *GSM* serving network).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0003-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-868 | 1.0 | Published | -01-2005 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D868 |
+| TTA | TTAT.3G-X.S0003-0 v1.0 | | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0003-0 v1.0.zip |
+| TTC | TS-3GB-X.S0003-0v1.0 | 1 | TTC
Published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0003-0v10.pdf |
+
+### 10.5.3 X.S0004-000-E – Version 1.0.0 – Introduction to TIA-41 (- March 2004)
+
+This document is to identify those cellular services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-000-E v1.0.0 | 1 | Approved | -03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-41.000-E | 1.0.0 | Published | 20-04-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D41.000-E |
+| TTA | TTAT.3G-X.S0004-000-E v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-000-E v1.0.0.zip |
+
+### **10.5.3.1 X.S0004-000-E – Version 2.0.0 – Introduction to TIA-41 (- March 2004)**
+
+The purpose of this standard is to identify those wireless services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-000-E | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0004-000-E v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-000-E v2.0.zip |
+
+### **10.5.3.2 X.S0004-000-E – Version 3.0.0 – Introduction to MAP (- October 2005)**
+
+The purpose of this standard is to identify those wireless services which require intersystem cooperation, to present the general background against which those services are to be provided, and to summarize the principal considerations which have governed and directed the particular approaches taken in the procedural recommendations. This part defines the range of application of the current issue of the series. It focuses on overall objectives and basic assumptions. Procedural details are presented in the other recommendations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-000-E | 3.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0004-000-E v3.0 | 3.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-000-E v3.0.zip |
+
+### **10.5.3.3 X.S0004-400-E – Version 1.0 – Operations, Administration and Maintenance (- July 2005)**
+
+This document defines the intersystem Operations, Administration, and Maintenance (OA&M) information flows and procedures required for intersystem trunk maintenance.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-400-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-41.400-E | 1.0 | Published | -12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-X.S0004-400-E v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-400-E v1.0.zip |
+
+### **10.5.3.4 X.S0004-500-E – Version 1.0.0 – Introduction to Signalling Protocols (- March 2004)**
+
+This document introduces the signalling protocols for this standard.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-500-E v1.0.0 | 1 | Approved | -03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-41.500-E | 1.0.0 | Published | 20-04-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D41.500-E |
+| TTA | TTAT.3G-X.S0004-500-E v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-500-E v1.0.0.zip |
+
+### **10.5.3.5 X.S0004-510-E – Version 1.0.0 – X.25 Transport Signalling Protocols (- March 2004)**
+
+This document describes X.25 Transport Signalling Protocols.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|----------------|---------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-510-E v1.0.0 | 1 | Approved | -03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-41.510-E | 1.0.0 | Published | 20-04-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D41%2D510%2DE |
+| TTA | TTAT.3G-X.S0004-510-E v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-510-E v1.0.0.zip |
+
+### **10.5.3.6 X.S0004-511-E – Version 1.0.0 – ANS/SS7 Transport Signalling Protocols (- March 2004)**
+
+This document describes ANS/SS7 Transport Signalling Protocols.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-511-E v1.0.0 | 1 | Approved | -03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-41.511-E | 1.0.0 | Published | 20-04-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D41.511-E |
+| TTA | TTAT.3G-X.S0004-511-E v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-511-E v1.0.0.zip |
+
+### **10.5.3.7 X.S0004-512-E – Version 1.0.0 – ITU-T SS7 Transport Signalling Protocols (- March 2004)**
+
+This document describes ITU-T SS7 Transport Signalling Protocols.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-512-E v1.0.0 | 1 | Approved | -03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-41.512.-E | 1.0.0 | Published | 20-04-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D41.512-E |
+| TTA | TTAT.3G-X.S0004-512-E v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-512-E v1.0.0.zip |
+
+### 10.5.3.8 X.S0004-520-E – Version 1.0.0 – TCAP Application Signalling Protocols (- March 2004)
+
+This document describes TCAP application signalling protocols.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-520-E v1.0.0 | 1 | Approved | -03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-41.520-E | 1.0.0 | Published | 20-04-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2F41%2E520%2DE |
+| TTA | TTAT.3G-X.S0004-520-E v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-520-E v1.0.0.zip |
+
+### 10.5.3.9 X.S0004-540-E – Version 1.0.0 – MAP Operations Signalling Protocols (- March 2004)
+
+This document supports systems conforming to air-interface technology, AMPS, NAMPS, TDMA, CDMA, including cdma2000.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-540-E v1.0.0 | 1 | Approved | -03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-41.540-E | 1.0.0 | Published | 20-04-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D41.540-E |
+| TTA | TTAT.3G-X.S0004-540-E v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-540-E v1.0.0.zip |
+
+### 10.5.3.10 X.S0004-550-E – Version 1.0.0 – MAP Parameters Signalling Protocols (- March 2004)
+
+This document supports systems conforming to air-interface technology, AMPS, NAMPS, TDMA, CDMA, including cdma2000.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-550-E v1.0.0 | 1 | Approved | -03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-41.550-E | 1.0.0 | Published | 20-04-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D41%2D550%2DE |
+| TTA | TTAT.3G-X.S0004-550-E v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-550-E v1.0.0.zip |
+
+### 10.5.3.11 X.S0004-551-E – Version 1.0.0 – Parameter Types Signalling Protocols (- March 2004)
+
+This document provides the definitions of the parameter types used in this Standard.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-551-E v1.0.0 | 1 | Approved | -03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-41.551-E | 1.0.0 | Published | 20-04-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D41.551-E |
+| TTA | TTAT.3G-X.S0004-551-E v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-551-E v1.0.0.zip |
+
+### 10.5.3.12 X.S0004-590-E – Version 1.0.0 – MAP Compatibility Signalling Protocols (- March 2004)
+
+While this document outlines guidelines and rules, which will in the near term be beneficial to implementation of this standard, other activities which may impact these rules are in progress. As such, the remainder of this Section, "MAP Compatibility Guidelines and Rules" may be subject to change and revision based on future TIA-41 recommendations. This is to ensure that there is no long-term impediment to Cellular Radiotelecommunications networks to evolve and implement significant new functionality. Also, this is to better allow for the longer-term alignment of TIA-41 with emerging international standards.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-590-E v1.0.0 | 1 | Approved | -03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-41.590-E | 1.0.0 | Published | 20-04-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D41.590-E |
+| TTA | TTAT.3G-X.S0004-590-E v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-590-E v1.0.0.zip |
+
+### 10.5.3.13 X.S0004-600-E – Version 1.0 – Introduction to Procedures (- July 2005)
+
+This document describes the signalling and call processing procedures required to perform automatic roaming features and services. The messages required to perform the automatic roaming are defined in Part 540. Conformance with this document shall mean that a system's externally visible behaviour is the same as the externally visible behaviour of the abstract system described here.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-600-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-41.600-E | 1.0 | Published | -12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-X.S0004-600-E v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-600-E v1.0.zip |
+
+### 10.5.3.14 X.S0004-630-E – Version 1.0 – Basic Call Processing (- July 2005)
+
+This document describes the signalling and call processing procedures required to perform automatic roaming features and services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-630-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-41.630-E | 1.0 | Published | -12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-X.S0004-630-E v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-630-E v1.0.zip |
+
+### 10.5.3.15 X.S0004-640-E – Version 1.0 – Intersystem Procedures (- July 2005)
+
+This document describes the signalling and call processing procedures required to perform automatic roaming features and services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-640-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-41.640-E | 1.0 | Published | -12-2006 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-X.S0004-640-E v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-640-E v1.0.zip |
+
+### 10.5.3.16 X.S0004-641-E – Version 1.0 – Short Message Services (SMS) (- July 2005)
+
+This document describes the signalling and call processing procedures required to perform automatic roaming features and services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-641-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-41.641-E | 1.0 | Published | -12-2006 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-X.S0004-641-E v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-641-E v1.0.zip |
+
+### 10.5.3.17 X.S0004-642-E – Version 1.0 – Segmentation (- July 2005)
+
+This section describes procedures to allow the transmission of messages, which may or may not require Segmentation and Reassembly (S&R).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-642-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-41.642-E | 1.0 | Published | -12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-X.S0004-642-E v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-642-E v1.0.zip |
+
+### 10.5.3.18 X.S0004-650-E – Version 1.0 – Common Voice Feature Procedures (- July 2005)
+
+This section describes common voice feature procedures to implement individual features.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-650-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-41.650-E | 1.0 | Published | -12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-X.S0004-650-E v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-650-E v1.0.zip |
+
+### 10.5.3.19 X.S0004-651-E – Version 1.0 – Voice Feature Procedures (- July 2005)
+
+This section describes modular procedures to implement individual features.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-651-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-41.651-E | 1.0 | Published | -12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-X.S0004-651-E v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-651-E v1.0.zip |
+
+### 10.5.3.20 X.S0004-660-E – Version 1.0 – Wireless Intelligent Network (WIN) Procedures (- July 2005)
+
+In addition to the specific procedures described in this part of the Standard, the functional entity call and service logic processing models provide a tool used by WIN architects to model a call and to understand and describe the distribution of functions between functional entities and functional entity relationships.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-660-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-41.660-E | 1.0 | Published | -12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-X.S0004-660-E v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-660-E v1.0.zip |
+
+### 10.5.3.21 X.S0004-690-E – Version 1.0 – Operation Timer Values (- July 2005)
+
+The following table provides a summary of the timers used for MAP operations. The timer values specified in this table are default values only and should be optimized for actual operating environments. Some timers are locally defined and are not in this table (e.g., alerting timer, no answer timer, page response timer, maximum interaction timer, interdigit timer).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-690-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-41.690-E | 1.0 | Published | -12-2005 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-X.S0004-690-E v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-690-E v1.0.zip |
+
+### 10.5.3.22 X.S0004-691-E – Version 1.0 – Annexes (- July 2005)
+
+This annex describes an algorithm for verifying the value of RANDC received from an MS. The algorithm used to verify RANDC is internal to an MSC and, as such, it does not constitute an intersystem operation.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-691-E | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0004-691-E v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-691-E v1.0.zip |
+
+### 10.5.3.23 X.S0004-691-E – Version 2.0 – Annexes (- September 2005)
+
+This annex describes an algorithm for verifying the value of RANDC received from an MS. The algorithm used to verify RANDC is internal to an MSC and, as such, it does not constitute an intersystem operation.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-691-E | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0004-691-E v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-691-E v2.0.zip |
+
+### 10.5.3.24 X.S0004-700-E – Version 1.0.0 – Wireless Intelligent Networks (- March 2004)
+
+This document part of TIA-41 defines the distributed functional plane (DFP) for the Wireless Intelligent Network (WIN).
+
+Specifically, the scope of this part of the Standard is:
+
+- 1) To define the WIN functional entities and the relationships applicable to WIN.
+- 2) To specify a high-level model description of call control function (CCF) activities required to establish and maintain communication paths for users.
+- 3) To specify a high-level model description of service switching function (SSF) activities required for interaction between the CCF and a service control function (SCF).
+- 4) To specify WIN triggers and provide a high-level model description of detection point processing.
+- 5) To describe mobility management and radio access control functions in the context of WIN.
+- 6) To illustrate how the WIN basic call state models interact with TIA-41 signalling.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-700-E v1.0.0 | 1 | Approved | -03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-41.700-E | 1.0.0 | Published | 20-04-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D41.700-E |
+| TTA | TTAT.3G-X.S0004-700-E v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-700-E v1.0.0.zip |
+
+### **10.5.3.25 X.S0004-730-E – Version 1.0.0 – WIN Distributed Functional Model (- March 2004)**
+
+This document depicts the functional entities and relationships applicable to WIN.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-730-E v1.0.0 | 1 | Approved | -03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-41.730-E | 1.0.0 | Published | 20-04-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D41.730-E |
+| TTA | TTAT.3G-X.S0004-730-E v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-730-Ev1.0.0.zip |
+
+### **10.5.3.26 X.S0004-750-E – Version 1.0.0 – SSF/CCF Call and Service Logic Model (- March 2004)**
+
+This document describes WIN call and service logic processing in terms of call modelling and modelling of service logic processing. WIN call and service logic encompasses call and connection processing in the SSF/CCF, service logic execution in the SCF, and the use of supporting resources and data in the SRF and SDF, respectively.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-750-E v1.0.0 | 1 | Approved | -03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-41.750-E | 1.0.0 | Published | 20-04-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D41.750-E |
+| TTA | TTAT.3G-X.S0004-750-E v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-750-Ev1.0.0.zip |
+
+### **10.5.3.27 X.S0004-790-E – Version 1.0.0 – WIN Call Delivery (- March 2004)**
+
+This annex describes how MS-to-MS call delivery can be modelled using the WIN Basic Call State Models (BCSMs). The message sequences shown in the annex are as in TIA-41.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0004-790-E v1.0.0 | 1 | Approved | -03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-41.790-E | 1.0.0 | Published | 20-04-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D41.790-E |
+| TTA | TTAT.3G-X.S0004-790-E v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0004-790-Ev1.0.0.zip |
+
+### 10.5.4 X.S0008-0 – Version 1.0 – Support for the Mobile Equipment Identity (MEID) (- June 2004)
+
+This section provides modifications for the introductory matter for TIA-41 (part 000).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0008-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-928-1 | 1 | Published | -06-2004 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-X.S0008-0 v1.0 | 1.0 | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0008-0 v1.0.zip |
+| TTC | TS-3GB-X.S0008-0v1.0 | 1 | TTC
Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0008-0v10.pdf |
+
+### 10.5.4.1 X.S0008-0 – Version 2.0 – Map Support for the Mobile Equipment Identity (MEID) (- October 2005)
+
+This section provides modifications for the introductory matter for TIA-41 (part 000).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0008-0 | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-928-2E | 2.0 | Published | -10-2005 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-X.S0008-0 v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0008-0 v2.0.zip |
+| TTC | TS-3GB-X.S0008-0v2.0 | 1 | TTC
Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0008-0v20.pdf |
+
+### 10.5.5 X.S0009-0 – Version 1.0 – Wireless Intelligent Network Support for Location Based Services (- June 2004)
+
+The purpose of this document is to describe FAM, LBC, LBIS and ECR, and to specify the intersystem operations that enable a wireless system to provide these location-based services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0009-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-843 | 1 | Published | 01-08-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D843 |
+| TTA | TTAT.3G-X.S0009-0 v1.0 | | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0009-0 v1.0.zip |
+| TTC | TS-3GB-X.S0009-0v1.0 | 1 | TTC
Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0009-0v10.pdf |
+
+### 10.5.6 X.S0010-A – Version 1.0 – Pre-Paid charging Enhancements for Circuit-Switched Data and Short Message Services (5 January 2004)
+
+This document describes the additions and modifications to TTA/EIA/IS-826, *Wireless Intelligent Network Capabilities for Pre-Paid Charging*, to support circuit-switched data and short message services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0010-A v1.0 | 1 | Approved | 05-01-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-826A | 1 | Published | 01-12-2003 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D826%2DA |
+| TTA | TTAT.3G-X.S0010-A v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0010-A v1.0.zip |
+| TTC | TS-3GB-X.S0010-Av1.0 | 1 | TTC
Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0010-av10.pdf |
+
+### 10.5.7 X.S0011-001-C – Version 1.0.0 – cdma2000 Wireless IP Network Standard: Introduction (- August 2003)
+
+This specification defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification defines the two methods for accessing public networks (Internet) and private networks (intranets): Simple IP and Mobile IP. It describes the required Quality of Service, Security, Mobility Management, and Accounting capabilities needed to support both methods.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0011-001-C v1.0.0 | 1 | Approved | -08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-835-C | 1.0.0 | Published | 01-08-2003 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D835-C |
+| TTA | TTAT.3G-X.S0011-001-C v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-001-C v1.0.0.zip |
+| TTC | TS-3GB-X.S0011-001-Cv1.0.0 | 1 | TTC
Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-001-cv100.pdf |
+
+### 10.5.7.1 X.S0011-001-C – Version 2.0 – cdma2000 Wireless IP Network Standard: Introduction (- July 2005)
+
+This specification defines requirements for support of wireless packet data networking capability on a third generation wireless system based on cdma2000. This specification supports the services and architecture. This specification defines the two methods for accessing public networks (Internet) and private networks (intranets): Simple IP and Mobile IP. It describes the required Quality of Service, Security, Mobility Management, and Accounting capabilities needed to support both methods.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0011-001-C | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0011-001-C v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-001-C v2.0.zip |
+| TTC | TS-3GB-X.S0011-001-Cv2.0 | 1 | TTC
Published | 26-08-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-001-cv20.pdf |
+
+### 10.5.7.2 X.S0011-002-C – Version 1.0.0 – cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Access Services (- August 2003)
+
+This document describes the required capabilities at the MS, the PDSN, the HA and the RADIUS servers to provide Simple IPv4, Simple IPv6 and Mobile IPv4 access services over PPP. It describes the mechanisms of updating the DNS with the user's assigned IP address as described in the IP Reachability Service capability.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0011-002-C v1.0.0 | 1 | Approved | -08-03 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-835-C | 1.0.0 | Published | 01-08-2003 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D835-C |
+| TTA | TTAT.3G-X.S0011-002-C v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-002-Cv1.0.0.zip |
+| TTC | TS-3GB-X.S0011-002-Cv1.0.0 | 1 | TTC
Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-002-cv100.pdf |
+
+### 10.5.7.3 X.S0011-002-C – Version 2.0 – cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Services (- July 2005)
+
+This document describes the required capabilities at the MS, the PDSN, the HA and the RADIUS servers to provide Simple IPv4, Simple IPv6 and Mobile IPv4 access services over PPP. It describes the mechanisms of updating the DNS with the user's assigned IP address as described in the IP Reachability Service capability.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0011-002-C | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0011-002-C v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-002-Cv2.0.zip |
+| TTC | TS-3GB-X.S0011-002-Cv2.0 | 1 | TTC
Published | 26-08-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-002-cv20.pdf |
+
+### 10.5.7.4 X.S0011-003-C – Version 1.0.0 – cdma2000 Wireless IP Network Standard: Packet Data Mobility and Resource Management (- August 2003)
+
+This document describes the mechanisms at the PDSN resulting from handoff of an MS from one BS/PCF to another BS/PCF, and which may result in changing the serving PDSN for the MS. This document describes an optional fast handoff capability, which is a low latency, low data loss handoff mechanism between PDSNs. Fast handoff mechanism delays re-negotiation of PPP until the MS becomes dormant at the Target PDSN. It also describes resource management procedures at the PDSN and the HA that are used following an inter-PDSN handoff or under other conditions that require release of resources. Furthermore, a procedure for provisioning the RN with resource management parameters such as RN packet data inactivity timers is specified in this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0011-003-C v1.0.0 | 1 | Approved | -08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-835-C | 1.0.0 | Published | 01-08-2003 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D835-C |
+| TTA | TTAT.3G-X.S0011-003-C v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-003-Cv1.0.0.zip |
+| TTC | TS-3GB-X.S0011-003-Cv1.0.0 | 1 | TTC
Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-003-cv100.pdf |
+
+### 10.5.7.5 X.S0011-003-C – Version 2.0 – cdma2000 Wireless IP Network Standard: Packet Data Mobility and Resource Management (- July 2005)
+
+This document describes the mechanisms at the PDSN resulting from handoff of an MS from one BS/PCF to another BS/PCF, and which may result in changing the serving PDSN for the MS. This document describes an optional fast handoff capability, which is a low latency, low data loss handoff mechanism between PDSNs. Fast handoff mechanism delays re-negotiation of PPP until the MS becomes dormant at the Target PDSN. It also describes resource management procedures at the PDSN and the HA that are used following an inter-PDSN handoff or under other conditions that require release of resources. Furthermore, a procedure for provisioning the RN with resource management parameters such as RN packet data inactivity timers is specified in this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0011-003-C | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0011-003-C v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-003-Cv2.0.zip |
+| TTC | TS-3GB-X.S0011-003-Cv2.0 | 1 | TTC
Published | 26-08-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-003-cv20.pdf |
+
+### 10.5.7.6 X.S0011-004-C – Version 1.0.0 – cdma2000 Wireless IP Network Standard: Quality of Service and Header Reduction (- August 2003)
+
+This document describes Flow Mapping/Treatment mechanisms and protocol used when more than one service instance is established for the MS. It also describes two optional Header Reduction techniques that are specific to service instances of SO type 60 and 61, that may be established by the MS for applications that require a synchronous flow of 20-ms frames, such as VoIP application.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0011-004-C v1.0.0 | 1 | Approved | -08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-835-C | 1.0.0 | Published | 01-08-2003 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D835-C |
+| TTA | TTAT.3G-X.S0011-004-C v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-004-Cv1.0.0.zip |
+| TTC | TS-3GB-X.S0011-004-Cv1.0.0 | 1 | TTC
Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-004-cv100.pdf |
+
+### 10.5.7.7 X.S0011-004-C – Version 2.0 – cdma2000 Wireless IP Network Standard: Quality of Service and Header Reduction (- July 2005)
+
+This document describes Flow Mapping/Treatment mechanisms and protocol used when more than one service instance is established for the MS. It also describes two optional Header Reduction techniques that are specific to service instances of SO type 60 and 61, that may be established by the MS for applications that require a synchronous flow of 20-ms frames, such as VoIP application.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0011-004-C | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0011-004-C v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-004-C v2.0.zip |
+| TTC | TS-3GB-X.S0011-004-Cv2.0 | 1 | TTC
Published | 26-08-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-004-cv20.pdf |
+
+### 10.5.7.8 X.S0011-005-C – Version 1.0.0 – cdma2000 Wireless IP Network Standard: Accounting Services and 3GPP2 RADIUS VSAs (- August 2003)
+
+This document describes the off-line accounting procedures and the Usage Data Records. It describes all the 3GPP2 VSAs used to support the capabilities described in this series of specifications X.S0011-001-C to X.S0011-006-C.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0011-005-C v1.0.0 | 1 | Approved | -08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-835-C | 1.0.0 | Published | 01-08-2003 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D835-C |
+| TTA | TTAT.3G-X.S0011-005-C v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-005-C v1.0.0.zip |
+| TTC | TS-3GB-X.S0011-005-Cv1.0.0 | 1 | TTC
Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-005-cv100.pdf |
+
+### 10.5.7.9 X.S0011-005-C – Version 2.0 – cdma2000 Wireless IP Network Standard: Accounting Services and 3GPP2 RADIUS VSAs (- July 2005)
+
+This document describes the off-line accounting procedures and the Usage Data Records. It describes all the 3GPP2 VSAs used to support the capabilities described in this series of specifications X.S0011-001-C to X.S0011-006-C.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0011-005-C | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0011-005-C v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-005-C v2.0.zip |
+| TTC | TS-3GB-X.S0011-005-Cv2.0 | 1 | TTC
Published | 26-08-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-005-cv20.pdf |
+
+### 10.5.7.10 X.S0011-006-C – Version 1.0.0 – cdma2000 Wireless IP Network Standard: PrePaid Packet Data Service (- August 2003)
+
+Support for PrePaid packet data services is optional in this specification. The PrePaid packet data service allows a user to purchase packet data service in advance based on volume or duration. In order to support PrePaid packet data service, the PDSN and/or the HA shall support the PrePaid client (PPC) function and the PrePaid server (PPS) function may be co-located with the Home RADIUS server.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------------|---------|---------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0011-006-C v1.0.0 | 1 | Approved | -08-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-835-C | 1.0 | Published | 01-08-2003 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D835 |
+| TTA | TTAT.3G-X.S0011-006-C v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-006-Cv1.0.0.zip |
+| TTC | TS-3GB-X.S0011-006-Cv1.0.0 | 1 | TTC Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-006-cv100.pdf |
+
+### 10.5.7.11 X.S0011-006-C – Version 2.0 – cdma2000 Wireless IP Network Standard: PrePaid Packet Data Services (- July 2005)
+
+Support for PrePaid packet data services is optional in this specification. The PrePaid packet data service allows a user to purchase packet data service in advance based on volume or duration. In order to support PrePaid packet data service, the PDSN and/or the HA shall support the PrePaid client (PPC) function and the PrePaid server (PPS) function may be co-located with the Home RADIUS server. In this revision of the specification, the PrePaid packet data service supports a set of capabilities as described in section 3 of the specification. Additional capabilities may be supported in future revisions of this specification.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0011-006-C | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0011-006-C v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0011-006-Cv2.0.zip |
+| TTC | TS-3GB-X.S0011-006-Cv2.0 | 1 | TTC Published | 26-08-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0011-006-cv20.pdf |
+
+### 10.5.8 X.S0012-0 – Version 2.0 – Legacy MS Domain Step 1 (- March 2004)
+
+This Recommendation supports the 3GPP2 All-IP Step 1 Evolution Path by providing Stages 1, 2 and 3 for the architecture identified. The Legacy MS Domain provides support for existing MSs in an IP core network environment. The Legacy MS Domain supports the features and capabilities provided in a legacy network in a manner transparent to the user. New features and capabilities supported by the IP core network may be made available to subscribers where they are supported by MS capabilities.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0012-0 v2.0 | 1 | Approved | -03-2004 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-872-A | 1 | Published | 04-05-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D872%2DA |
+| TTA | TTAT.3G-X.S0012-0 v2.0 | 2.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0012-0 v2.0.zip |
+| TTC | TS-3GB-X.S0012-0v2.0 | 1 | TTC
Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0012-0v20.pdf |
+
+### 10.5.9 X.S0013-000-0 – Version 1.0 – All-IP Core Network Multimedia Domain – Overview (- December 2003)
+
+This document contains the introduction of the Stage-1, Stage-2 and Stage-3 recommendations for the 3GPP2 All-IP Multimedia Domain. It includes an overview of the system elements and interfaces and lists the series of documents that provide the complete specifications for the core network portions of the MMD. Not all MMD entities and interfaces may be covered by this version of this series of specifications. The specific entities and interfaces covered by a particular version are identified in each of the individual specifications.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-000-0 v1.0 | 1 | Approved | -12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-873.000 | 1.0 | Published | 01-12-2003 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D873_000 |
+| TTA | TTAT.3G-X.S0013-000-0 v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-000-0 v1.0.zip |
+| TTC | TS-3GB-X.S0013-000-0v1.0 | 1 | TTC
Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-000-0v10.pdf |
+
+### 10.5.9.1 X.S0013-000-0 – Version 2.0 – All-IP Core Network Multimedia Domain – Overview (- July 2005)
+
+The Multimedia Domain (MMD) is a CDMA-based wireless network providing 3rd generation capabilities and based on IP protocols, elements and principles. This document provides an introduction to the core network elements and interfaces that make up a portion of the MMD. This document also introduces the series of documents that provide the complete specification of the core network interfaces and protocols that provide this part of the MMD capabilities.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-000-0 | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-873.000-1[E] | 2.0 | Published | -05-2006 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-X.S0013-000-0 v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-000-0 v2.0.zip |
+| TTC | TS-3GB-X.S0013-000-0v2.0 | 1 | TTC
Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-000-0v20.pdf |
+
+### 10.5.9.2 X.S0013-000-A – Version 1.0 – All-IP Core Network Multimedia Domain – Overview (- November 2005)
+
+The Multimedia Domain (MMD) is a collection of core network entities providing 3rd generation capabilities and based on IP protocols, elements and principles. This document provides an introduction to the core network elements and interfaces that make up a portion of the MMD. This document also introduces the series of documents that provide the complete specification of the core network interfaces and protocols that provide this part of the MMD capabilities.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-000-A | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-873.000-A | 1.0 | Published | -05-2006 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-X.S0013-000-A v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-000-A v1.0.zip |
+
+### 10.5.9.3 X.S0013-002-0 – Version 1.0 – All-IP Core Network Multimedia Domain – IP Multimedia Subsystem – Stage 2 (- December 2003)
+
+This document defines stage-2 service description for the IP Multimedia Core Network Subsystem (IMS), which includes the elements necessary to support IP Multimedia (IM) services in PLMNs and perhaps other networks. This document identifies the mechanisms to enable support for IP multimedia applications.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-002-0 v1.0 | 1 | Approved | -12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-873.002 | 1.0 | Published | 01-12-2003 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D873_002 |
+| TTA | TTAT.3G-X.S0013-002-0 v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-002-0 v1.0.zip |
+| TTC | TS-3GB-X.S0013-002-0v1.0 | 1 | TTC
Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-002-0v10.pdf |
+
+### 10.5.9.4 X.S0013-002-A – Version 1.0 – All-IP Core Network Multimedia Domain – IP Multimedia Subsystem – Stage 2 (- November 2005)
+
+This document defines stage-2 service description for the IP Multimedia Core Network Subsystem (IMS), which includes the elements necessary to support IP Multimedia (IM) services. ITU-T Rec. I.130 describes a three-stage method for characterization of telecommunication services, and ITU-T Rec. Q.65 defines stage 2 of the method. This document identifies the mechanisms to enable support for IP multimedia applications. In order to align IP multimedia applications wherever possible with non-IMS IP applications, the general approach is to adopt non-IMS specific IP-based solutions.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-002-A | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-873.002-A | 1.0 | Published | -05-2006 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-X.S0013-002-A v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-002-A v1.0.zip |
+
+**10.5.9.5 X.S0013-003-0 – Version 1.0 – All-IP Core Network Multimedia Domain –
+IP Multimedia (IMS) Session Handling; IP Multimedia (IM) Call Model – Stage 2
+(- December 2003)**
+
+This document specifies the IP Multimedia (IM) Call Model for handling of an IP multimedia session origination and termination for an IP Multimedia subscriber.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-003-0 v1.0 | 1 | Approved | -12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-873.003 | 1.0 | Published | 01-12-2003 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D873_003 |
+| TTA | TTAT.3G-X.S0013-003-0 v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-003-0 v1.0.zip |
+| TTC | TS-3GB-X.S0013-003-0v1.0 | 1 | TTC
Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-003-0v10.pdf |
+
+**10.5.9.6 X.S0013-003-0 – Version 2.0 – All-IP Core Network Multimedia Domain –
+IP Multimedia (IMS) Session Handling; IP Multimedia (IM) Call Model – Stage 2
+(- July 2005)**
+
+This document specifies the IP Multimedia (IM) Call Model for handling of an IP multimedia session origination and termination for an IP Multimedia subscriber. The present document includes interactions between an Application Server and IP multimedia sessions. The IP Multimedia (IM) Subsystem stage 2 is specified in TIA-873-002 or in 3GPP2 X.S0013-002 and the stage 3 for the IP multimedia call control based on SIP and SDP is specified in TIA-873-004 or in 3GPP2 X.S0013-004.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-003-0 | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-873-003-1[E] | 2.0 | Published | -05-2006 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-X.S0013-003-0 v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-003-0 v2.0.zip |
+| TTC | TS-3GB-X.S0013-003-0v2.0 | 1 | TTC
Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-003-0v20.pdf |
+
+**10.5.9.7 X.S0013-003-A – Version 1.0 – All-IP Core Network Multimedia Domain –
+IP Multimedia (IMS) Session Handling; IP Multimedia (IM) Call Model; Stage 2
+(- November 2005)**
+
+This document specifies the IP Multimedia (IM) Call Model for handling of an IP multimedia session origination and termination for an IP Multimedia subscriber. The present document includes interactions between an Application Server and IP multimedia sessions. The IP Multimedia (IM) Subsystem stage 2 is specified in TIA-873-002 or in 3GPP2 X.S0013-002 and the stage 3 for the IP multimedia call control based on SIP and SDP is specified in TIA-873-004 or in 3GPP2 X.S0013-004.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-003-A | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0013-003-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-003-A v1.0.zip |
+
+**10.5.9.8 X.S0013-004-0 – Version 1.0 – All-IP Core Network Multimedia Domain –
+IP Multimedia Call Control Protocol Based on SIP and SDP – Stage 3
+(- December 2003)**
+
+This document defines a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-004-0 v1.0 | 1 | Approved | -12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-873.004 | 1.0 | Published | 01-12-2003 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D873_004 |
+| TTA | TTAT.3G-X.S0013-004-0 v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-004-0 v1.0.zip |
+| TTC | TS-3GB-X.S0013-004-0v1.0 | 1 | TTC
Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-004-0v10.pdf |
+
+**10.5.9.9 X.S0013-004-0 – Version 2.0 – All-IP Core Network Multimedia Domain –
+IP Multimedia Call Control Protocol Based on SIP and SDP – Stage 3 (- July 2005)**
+
+This document defines a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-004-0 | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0013-004-0 v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-004-0 v2.0.zip |
+| TTC | TS-3GB-X.S0013-004-0v2.0 | 1 | TTC
Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-004-0v20.pdf |
+
+**10.5.9.10 X.S0013-004-A – Version 1.0 – All-IP Core Network Multimedia Domain –
+IP Multimedia Call Control Protocol Based on SIP and SDP – Stage 3
+(- November 2005)**
+
+This document defines a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-004-A | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0013-004-A v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-004-A v1.0.zip |
+
+**10.5.9.11 X.S0013-005-0 – Version 1.0 – All-IP Core Network Multimedia Domain –
+IP Multimedia Subsystem Cx interface Signalling flows and Message Contents
+(- December 2003)**
+
+This specification specifies the interactions between the HHS (Home Subscriber Server) and the CSCF (Call Session Control Functions), referred to as the Cx interface. This document addresses the signalling flows for the Cx interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-005-0 v1.0 | 1 | Approved | -12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-873.005 | 1.0 | Published | 01-12-2003 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D873_005 |
+| TTA | TTAT.3G-X.S0013-005-0v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-005-0v1.0.zip |
+| TTC | TS-3GB-X.S0013-005-0v1.0 | 1 | TTC
Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-005-0v10.pdf |
+
+### **10.5.9.12 X.S0013-005-0 – Version 2.0 – All-IP Core Network Multimedia Domain – IP Multimedia Subsystem Cx interface Signalling flows and Message Contents (- July 2005)**
+
+This specification specifies the interactions between the HHS (Home Subscriber Server) and the CSCF (Call Session Control Functions), referred to as the Cx interface. This document addresses the signalling flows for the Cx interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-005-0 | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0013-005-0 v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-005-0 v2.0.zip |
+| TTC | 3GB-X.S0013-005-0v2.0 | 1 | TTC
Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-005-0v20.pdf |
+
+### **10.5.9.13 X.S0013-005-A – Version 1.0 – All-IP Core Network Multimedia Domain – IP Multimedia Subsystem Cx interface Signalling flows and Message Contents (- November 2005)**
+
+This specification specifies the interactions between the HHS (Home Subscriber Server) and the CSCF (Call Session Control Functions), referred to as the Cx interface. This document addresses the signalling flows for the Cx interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-005-A | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0013-005-A v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-005-A v1.0.zip |
+
+### **10.5.9.14 X.S0013-006-0 – Version 1.0 – All-IP Core Network Multimedia Domain – Cx Interface Based on the Diameter Protocol; Protocol Details (- December 2003)**
+
+This document defines a transport protocol for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-006-0 v1.0 | 1 | Approved | -12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-873.006 | 1.0 | Published | 1-12-2003 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D873_006 |
+| TTA | TTAT.3G-X.S0013-006-0 v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-006-0 v1.0.zip |
+| TTC | TS-3GB-X.S0013-006-0v1.0 | 1 | TTC
Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-006-0v10.pdf |
+
+### **10.5.9.15 X.S0013-006-0 – Version 2.0 – All-IP Core Network Multimedia Domain Cx Interface Based on the Diameter Protocol; Protocol Details (- July 2005)**
+
+This document defines a transport protocol for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-006-0 | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0013-006-0 v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-006-0 v2.0.zip |
+| TTC | TS-3GB-X.S0013-006-0v2.0 | 1 | TTC
Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-006-0v20.pdf |
+
+### **10.5.9.16 X.S0013-006-A – Version 1.0 – All-IP Core Network Multimedia Domain – Cx Interface Based on the Diameter Protocol; Protocol Details (- November 2005)**
+
+This document defines a transport protocol for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. This document is applicable to: The Cx interface between the I-CSCF/S-CSCF and the HSS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-006-A | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0013-006-A v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-006-A v1.0.zip |
+
+### **10.5.9.17 X.S0013-007-0 – Version 1.0 – All-IP Core Network Multimedia Domain – IP Multimedia Subsystem – Charging Architecture (- December 2003)**
+
+This document describes the architecture for charging and billing for IMS services. For the purpose of this document, the charging data is considered to be generated and collected by charging functions in the network elements. The objectives of the present document are: to describe principles of charging in an IMS network, to provide a description of the charging architecture, and to provide the descriptions of events and triggers for the generation of charging data.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-007-0 v1.0 | 1 | Approved | -12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TTA | TTAT.3G-X.S0013-007-0 V1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-007-0 v1.0.zip |
+| TTC | TS-3GB-X.S0013-007-0v1.0 | 1 | TTC
Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-007-0v10.pdf |
+
+### **10.5.9.18 X.S0013-007-A – Version 1.0 – All-IP Core Network Multimedia Domain – IP Multimedia Subsystem – Charging Architecture (- November 2005)**
+
+This document describes the architecture for charging and billing for IMS services. For the purpose of this document, the charging data is considered to be generated and collected by charging functions in the network elements. The objectives of the present document are: to describe principles of charging in an IMS network, to provide a description of the charging architecture, and to provide the descriptions of events and triggers for the generation of charging data.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-007-A | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0013-007-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-007-A v1.0.zip |
+
+### **10.5.9.19 X.S0013-008-0 – Version 1.0 – All-IP Core Network Multimedia Domain – IP Multimedia Subsystem – Accounting Information Flows and Protocol (- December 2003)**
+
+This document defines a transport protocol for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-008-0 v1.0 | 1 | Approved | -12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-873.008 | 1.0 | Published | 01-12-2003 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D873_008 |
+| TTA | TTAT.3G-X.S0013-008-0 v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-008-0 v1.0.zip |
+| TTC | TS-3GB-X.S0013-008-0v1.0 | 1 | TTC
Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-008-0v10.pdf |
+
+### **10.5.9.20 X.S0013-008-0 – Version 2.0 – All-IP Core Network Multimedia Domain – IP Multimedia Subsystem – Accounting Information Flows and Protocol (- July 2005)**
+
+This document covers offline charging for the IMS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-008-0 | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0013-008-0 v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-008-0 v2.0.zip |
+| TTC | TS-3GB-X.S0013-008-0v2.0 | 1 | TTC
Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-008-0v20.pdf |
+
+**10.5.9.21 X.S0013-008-A – Version 1.0 – All-IP Core Network Multimedia Domain: IP Multimedia Subsystem – Accounting Information Flows and Protocols (- November 2005)**
+
+This document covers offline charging for the IMS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-008-A | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0013-008-A V1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-008-A v1.0.zip |
+
+**10.5.9.22 X.S0013-010-0 – Version 1.0 – All-IP Core Network Multimedia Domain IP Multimedia Subsystem Sh Interface; Signalling flows and message contents – Stage 2 (- December 2003)**
+
+This document specifies the interactions between HSS (Home Subscriber Server) and the SIP AS (Application Server) and between the HSS and the OSA SCS (Service Capability Server). This interface is referred to as the Sh reference point. This document addresses the signalling flows and message contents for the protocol at the Sh interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-010-0 v1.0 | 1 | Approved | -12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TTA | TIA-873.010 | 1.0 | Published | 01-12-2003 | http://www.ttaionline.org/standards/search_results2.cfm?document_no=TIA%2D873_010 |
+| TTA | TTAT.3G-X.S0013-010-0 v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-010-0 v1.0.zip |
+| TTC | TS-3GB-X.S0013-010-0v1.0 | 1 | TTC
Published | 2-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-010-0v10.pdf |
+
+**10.5.9.23 X.S0013-010-0 – Version 2.0 – All-IP Core Network Multimedia Domain: IP Multimedia Subsystem Sh Interface; Signalling Flows and Message Contents – Stage 2 (- July 2005)**
+
+This document specifies the interactions between HSS (Home Subscriber Server) and the SIP AS (Application Server) and between the HSS and the OSA SCS (Service Capability Server). This interface is referred to as the Sh reference point. This document addresses the signalling flows and message contents for the protocol at the Sh interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-010-0 | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0013-010-0 v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-010-0 v2.0.zip |
+| TTC | TS-3GB-X.S0013-010-0v2.0 | 1 | TTC
Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-010-0v20.pdf |
+
+**10.5.9.24 X.S0013-010-A – Version 1.0 – All-IP Core Network Multimedia Domain: IP Multimedia Subsystem Sh Interface; Signalling flows and message contents – Stage 2 (- November 2005)**
+
+This document specifies the interactions between HSS (Home Subscriber Server) and the SIP AS (Application Server) and between the HSS and the OSA SCS (Service Capability Server). This interface is referred to as the Sh reference point. This document addresses the signalling flows and message contents for the protocol at the Sh interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-010-A | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0013-010-A v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-010-A v1.0.zip |
+
+**10.5.9.25 X.S0013-011-0 – Version 1.0 – All-IP Core Network Multimedia Domain IP Multimedia – Sh Interface based on Diameter Protocols – Protocol Details – Stage 3 (- December 2003)**
+
+This document defines a transport for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. The present document is applicable to: The Sh interface between an SIP AS and the AAA, and the Sh interface between an SCS and the AAA.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-011-0 v1.0 | 1 | Approved | -12-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-873-011 | 1.0 | Published | 01-12-2003 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D873_011 |
+| TTA | TTAT.3G-X.S0013-011-0 v1.0 | 1.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-011-0 v1.0.zip |
+| TTC | TS-3GB-X.S0013-011-0v1.0 | 1 | TTC Published | 28-05-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-011-0v10.pdf |
+
+**10.5.9.26 X.S0013-011-0 – Version 2.0 – All-IP Core Network Multimedia Domain: IP Multimedia Subsystem Sh Interface based on Diameter Protocols; Protocol Details – Stage 3 (- July 2005)**
+
+This document defines a transport for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. The present document is applicable to: The Sh interface between an SIP AS and the AAA, and the Sh interface between an SCS and the AAA.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-011-0 | 2.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0013-011-0 v2.0 | 2.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-011-0 v2.0.zip |
+| TTC | TS-3GB-X.S0013-011-0v2.0 | 1 | TTC Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0013-011-0v20.pdf |
+
+**10.5.9.27 X.S0013-011-A – Version 1.0 – All-IP Core Network Multimedia Domain:
+IP Multimedia Subsystem Sh Interface based on Diameter Protocols; Protocol
+Details – Stage 3 (- November 2005)**
+
+This document defines a transport for use in the IP multimedia (IM) Core Network (CN) subsystem based on Diameter. The present document is applicable to: the Sh interface between an SIP AS and the AAA, and the Sh interface between an SCS and the AAA.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0013-011-A | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0013-011-A v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0013-011-A v1.0.zip |
+
+**10.5.10 X.S0014-E – Version 1.0 – Wireless Radio Telecommunications Intersystem
+Non-Signalling Data Communication DMH (Data Message Handler)
+(- December 2004)**
+
+This document describes the messages and procedures required to perform call detail record data transmission between systems.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0014-E | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-124-E | 1 | Published | -05-2005 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D124%2DE |
+| TTA | TTAT.3G-X.S0014-E v1.0 | | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0014-E v1.0.zip |
+| TTC | TS-3GB-X.S0014-Ev1.0 | 1 | TTC
Published | 02-06-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0014-ev10.pdf |
+
+**10.5.11 X.S0017 – Version 1.0.0 – Open Service Access (OSA) Application Programming
+Interface (API) OSA API – Revision: 0 (- June 2003)**
+
+This document is intended to define the OSA API Stage 3 interface definitions and it provides the complete OSA specifications for cdma2000-based systems. This document is an extension of OSA API, per latest 3GPP TS 29.198 series specifications capabilities to enable operation in cdma2000 systems environment as part of the TIA/EIA/IS-2000 family of standards. The information given here is to be used by developers in 3GPP2 cdma2000 network architecture to the 3GPP OSA Specifications.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0017 v1.0.0 | 1 | Approved | -06-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742 |
+| TIA | TIA-937 | 1.0.0 | Published | 01-06-2003 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D937 |
+| TTA | TTAT.3G-X.S0017 v1.0.0 | 1.0.0 | Approved | 15-11-2004 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0017 v1.0.0.zip |
+| TTC | TS-3GB-X.S0017-0v1.0.0 | 1 | TTC
Published | 28-11-2003 | http://www.ttc.or.jp/imt2000/ts/tsxs0017-0v100.pdf |
+
+### 10.5.12 X.S0018 – Version 1.0.0 – Legacy Mobile Station Domain (LMSD) Step 1 – Revision: 0 (May 2003)
+
+This standard specifies the necessary interfaces to support the bearer traffic between Media Gateways in the initial step of the Legacy Mobile Station Domain (LMSD). The requirements for this work are defined in S.R0059, and the overall architecture model is defined in S.R0037.
+
+This standard defines bearer support of G.711 PCM encoded voice over IP as defined in RFC 1890 at a minimum, for use between media gateways in a cdma2000 Legacy Mobile Station Domain. This standard utilizes existing IETF and 3GPP2 protocols when applicable to minimize the new work needed.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|-----------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0018-0 | 1.0.0 | Approved | 09-2003 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/R3-2003-11 |
+| TIA | TIA-930 | | Published | 17-01-2003 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D930 |
+| TTA | TTAT.3G-X.S0018_v1.0.0 | 1.0.0 | Approved | 30-10-2003 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0018_v1.0.0.zip |
+
+### 10.5.13 X.S0021-B – Version 1.0 – Roamer Database Verification (- July 2004)
+
+The purpose of this document is to describe the RDV network capability and to specify the operation of RDV so that wireless systems can use RDV.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0021-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-847 | 1 | Published | 01-08-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D847%2DB |
+| TTA | TTAT.3G-X.S0021-B v1.0 | | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0021-B v1.0.zip |
+| TTC | TS-3GB-X.S0021-Bv1.0 | 1 | TTC
Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0021-bv10.pdf |
+
+### 10.5.14 X.S0023-B – Version 1.0 – Network Interworking Between GSM MAP and TIA-41 MAP – cdma 2000 Support (- July 2004)
+
+The purpose of this standard is to define and describe the functions necessary for roaming between ANSI-41 MAP and GSM MAP-based networks in the support of roaming subscribers. This includes a capability to allow a subscriber to an ANSI-41 based network (e.g., a TDMA or CDMA native subscriber) with a mobile terminal supporting GPRS service to roam to a GPRS network in GSM Foreign Mode.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0023-B | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | J-STD-038-B | 1 | Published | 01-08-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=J%2DSTD%2D038%2DB |
+| TTA | TTAT.3G-X.S0023-B v1.0 | | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0023-B v1.0.zip |
+| TTC | TS-3GB-X.S0023-Bv1.0 | 1 | TTC
Published | 03-09-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0023-bv10.pdf |
+
+### 10.5.15 X.S0027-000-0 – Version 1.0 – Presence Overview (- September 2004)
+
+This document describes network aspects of the Presence Service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0027-000 0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-1032 | 1 | Published | 01-11-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D1032 |
+| TTA | TTAT.3G-X.S0027-000-0 v1.0 | | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0027-000-0 v1.0.zip |
+| TTC | TS-3GB-X.S0027-000-0v1.0 | 1 | TTC
Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0027-000-0v10.pdf |
+
+### 10.5.15.1 X.S0027-001-0 – Version 1.0 – Presence Service: Architecture and Functional Description (- September 2004)
+
+This document describes the Stage 2 (architectural solution and functionalities) for the presence service, which includes the elements necessary to realize the Stage 1 requirements.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0027-001-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-1032 | 1 | Published | 01-11-2004 | http://www.tiaonline.org/standards/search_results2.cfm?document_no=TIA%2D1032 |
+| TTA | TTAT.3G-X.S0027-001-0 v1.0 | | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0027-001-0 v1.0.zip |
+| TTC | TS-3GB-X.S0027-001-0v1.0 | 1 | TTC
Published | 30-11-2004 | http://www.ttc.or.jp/imt2000/ts/tsxs0027-001-0v10.pdf |
+
+### 10.5.16 X.S0030-0 – Version 1.0 – MAP Enhancements to Support Enhanced Message Waiting Notification (MWN) (- September 2005)
+
+This document provides automatic roaming information flows that illustrate enhanced Message Waiting Count operation. This document also describes the signalling protocol and signalling procedure modifications needed for enhanced Message Waiting Count operation.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0030-0 | 1 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-1055 | 1 | Published | -09-2005 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-X.S0030-0 v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0030-0 v1.0.zip |
+| TTC | TS-3GB-X.S0030-0v1.0 | 1 | TTC
Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0030-0v10.pdf |
+
+### **10.5.17 X.S0033-0 – Version 1.0 – OTA Support for MEID (- October 2005)**
+
+This document presents a recommended plan for the implementation of Over-The-Air (OTA) support for the Mobile Equipment Identity (MEID).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0033-0 | 1.0 | Approved | -01-2006 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TIA | TIA-1074 | 1.0 | Published | -03-2006 | http://www.tiaonline.org/standards/catalog/search.cfm |
+| TTA | TTAT.3G-X.S0033-0 v1.0 | 1.0 | Approved | 19-04-2006 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0033-0 v1.0.zip |
+| TTC | TS-3GB-X.S0033-0v1.0 | 1 | TTC
Published | 25-11-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0033-0v10.pdf |
+
+### **10.5.18 X.S0034-0 – Version 1.0 – cdma2000/GPRS Roaming (- September 2004)**
+
+The scope of this document includes the roaming of a subscriber homed in a cdma2000 packet data system to a GPRS system and vice versa. The roaming between cdma2000 packet data systems is outside the scope of this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-MC-X.S0034-0 | 1.0 | Approved | -09-2005 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1742/Q.1742.5 |
+| TTA | TTAT.3G-X.S0034-0 v1.0 | | Approved | 09-12-2005 | http://www.tta.or.kr/standardDB/stnfile/TTAT.3G-X.S0034-0 v1.0.zip |
+| TTC | TS-3GB-X.S0034-0v1.0 | 1 | TTC
Published | 26-08-2005 | http://www.ttc.or.jp/imt2000/ts/tsxs0034-0v10.pdf |
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|---------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/024914144d624b7f5dc22aaa5c3967b9_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/024914144d624b7f5dc22aaa5c3967b9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1eb640731884f7050f14f2194715d3660d362973
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/024914144d624b7f5dc22aaa5c3967b9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0788c00a7a14ce33f4adf80eb74e793a6556469889eedd744cad9d017707e868
+size 35127
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/07c5a1c0fddd7da92a8427f5af840ffa_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/07c5a1c0fddd7da92a8427f5af840ffa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e3008e9afe9a079e56d7e864e84d03afa1ba3063
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/07c5a1c0fddd7da92a8427f5af840ffa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e07cd040bc74b4ffb1fb7845368bc2582e6a567549c080ffec0cfaab314b394a
+size 34589
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/08f6ace0c83e7394657fa372b47aec04_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/08f6ace0c83e7394657fa372b47aec04_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5ffbc0b0e466a80fde1b5b18b3a28b515269ccb4
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/08f6ace0c83e7394657fa372b47aec04_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:148348eca8552252a79a3728f292e2a4bb6b8f3c50351962bb48e0ce52e46bcb
+size 61277
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ead6ccd4c9124ee2ba6f72384f33799bca4f7118
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:475ab0399066cd9b91632272db657f54287ffa288a918ac519dc6103d60e71e7
+size 89431
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ee13ac78034da54abe6bad23f83c070ddb621061
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ecba6943b7991c0bef0ad8d54fca5ffb3501fd035b01d0313f5b9bf4bb70ffc7
+size 65859
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/1ce027dfd26183da52137cf990213724_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/1ce027dfd26183da52137cf990213724_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9e5feaba40aaff6dab106467fd18e8e17fdbf8ab
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/1ce027dfd26183da52137cf990213724_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a6b1a70fd14ccd8466cd26502d0a21ada79e020c4cdc6bd41e5bdcdce4adefba
+size 47823
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/23b1b06f283db73b446ddc3277c4c8d1_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/23b1b06f283db73b446ddc3277c4c8d1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4d40d42ca4fff6b474ee2ee426e0bd1473bb4470
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/23b1b06f283db73b446ddc3277c4c8d1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:029db9e2264a74ea805f32efa4ff5dd8206f345ba945456ba799ba14fd568fbf
+size 63757
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/25fab88fda841d5eec316c440656187e_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/25fab88fda841d5eec316c440656187e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2e9b4ceaa32ecc81d015d44854fdcbdab583f22f
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/25fab88fda841d5eec316c440656187e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3d5f18d1a1b52369fcedd94bdad96784689e26d0efbca4cdcf172a8461c21060
+size 87469
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/27fc71a666ffdf8fdc4ce84d9d585008_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/27fc71a666ffdf8fdc4ce84d9d585008_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cc9039e3592209f4ae3337940fb4b2eb65dbc136
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/27fc71a666ffdf8fdc4ce84d9d585008_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2c7c6cfb6e4353f304827b1f60bdcacf23cf2752917e901d5403c7a80fcf3cda
+size 60146
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/32ff77da4286b58c4778033acaa10836_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..703eb07407ffa8cce6696279474a6277b7e9f251
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/32ff77da4286b58c4778033acaa10836_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d2b46fcb4166fca3437f9704d1f21649432daa8d15dec23dde0997589cc487cb
+size 82600
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/34b047489058d6400b412cd0ae2334ba_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/34b047489058d6400b412cd0ae2334ba_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..25579c0f6275c129aa11c0f46a8a79637fc74a1b
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/34b047489058d6400b412cd0ae2334ba_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e4d912db528e09dc05581805ff95e2f747d317fb16a5fac10fc72795766813ce
+size 61238
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/3d6f5edac3d5e7113d960c2202f1b0fa_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/3d6f5edac3d5e7113d960c2202f1b0fa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e545a113ad55c7b41b3e05fed2f5a7ee2690a313
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/3d6f5edac3d5e7113d960c2202f1b0fa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:baa641bb13283a3dc8a5fb938f56334a605807c36240f264dcc251d8ce4f9474
+size 42164
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ec0b4103270e613c80738ea5ba923b651514921a
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bc6185a69f3d4f3f0cbcc93d96445409cfc32096975e1d17fb7159aa01a1d5fa
+size 100982
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/4d9c52be1198628362ec7871f6e0f530_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/4d9c52be1198628362ec7871f6e0f530_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d7eaaba1ed7ae79a02e718b9535ba21e60b24013
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/4d9c52be1198628362ec7871f6e0f530_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b571474ba993006e4573d7ce8772a2b99d58cdfd5f96e76b031ffc5398d84c2f
+size 22173
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/50a63fe40eaa16cb8745c689fe8f8264_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/50a63fe40eaa16cb8745c689fe8f8264_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e64e459e126f442930ee29400e56ca278f7ce41b
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/50a63fe40eaa16cb8745c689fe8f8264_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:50a84cb1296b69ba1cea568085ad7756b8f947d1e25920c915421942286567f2
+size 70866
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/552328a9daaf3bc0069424b500025880_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/552328a9daaf3bc0069424b500025880_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ff0ffa0f06dd5444ac4a5ae5a506983435f9dfb7
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/552328a9daaf3bc0069424b500025880_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c832cad448a8c3b9b735f765f4e8c325e47ec89a80e9c5b5cbd0a4c9f725bb77
+size 26036
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/5cf80bac69830ea773ac17c87e0ae24d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6e3a39a843ba76cc33dbdab6729c7d05f2b1dd95
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/5cf80bac69830ea773ac17c87e0ae24d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:890ed9926ae711fc600434f72cf7fdb01235f519a31c5f3a63e07b82c83b8a18
+size 27665
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ffc6a1f6e16f6c6b7d4f12f8daf81334ba920296
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c4fcf6061486e03864ecec57a8d81803b382230ed4e9fd86c0d262a8d3d71aa4
+size 54681
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/700f2fb63fbb87c933cd81ca42fb890f_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/700f2fb63fbb87c933cd81ca42fb890f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..42d827055a632fac62271b60e00684e5c12a95be
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/700f2fb63fbb87c933cd81ca42fb890f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f5fb6acd8b54e7108655a63405fc193813ba8587783ce55dd27ec3da016467b9
+size 40489
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aa10be8733d89342f36f374eaf5d1e1c39c2bdc4
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0119bff5a3c6a804102bee23afbb24758bda745373dd92563e63d62bb2b7fe0f
+size 20123
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/811d62d08ce934a2a7e5bd877abff7ad_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/811d62d08ce934a2a7e5bd877abff7ad_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6ceccdbe999e207601970a05f209c5205d63707d
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/811d62d08ce934a2a7e5bd877abff7ad_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:36140aba0aa7056396d7a9ce5b9a15bc1a5a13ebde74418a388f46e12339e9a5
+size 13733
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/838c31609fac483fa2c01c7896a2fd6d_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/838c31609fac483fa2c01c7896a2fd6d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..702ece0cbe39b71e966f2ef5e6e0bcbc539dd9c5
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/838c31609fac483fa2c01c7896a2fd6d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9498d73598a21f745e68eff766283c599361bddb17d0278f3ad94e737837ee93
+size 61774
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/8d66c9c295023a1380f9986d3663bb1e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d3bee17dd206e628b64ff1be5302075ec32e36bf
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/8d66c9c295023a1380f9986d3663bb1e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b5cd61ea549f76e1a725fa3377d97de3541406a704b72e982ddc35afbe2392b1
+size 36948
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/94d3fdcc244924326f02533aeb2d93fc_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/94d3fdcc244924326f02533aeb2d93fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b64835a2330f9a34e97023c5adaaa1506658d6f6
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/94d3fdcc244924326f02533aeb2d93fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5527d22d3488ee02772e54d33d0cb8ad2fad9fc177c6da761b84d518772ac662
+size 14526
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/9a14684f8ae1345c6efea6f5994c730c_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/9a14684f8ae1345c6efea6f5994c730c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c2240f7d07a46ef0f4e0055c540edc7af3a9638a
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/9a14684f8ae1345c6efea6f5994c730c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:55dee8996c06eb3a69066b1f13806cfed2a94392cd153f0a5a69a8c7d49d2524
+size 70473
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c44cb4223a47f70118ec4e8a6eb8ee3d426c1992
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:47c8a5b33ef1303802dbf0aaf79d2083dba78e435df71377f530a75c52ce065a
+size 44906
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aff388ab59364ea195b280dcbaefbc97307ac5ae
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:06add4d710ba6dcf764e00fa491a08677de10a278c1ebaef062a3bd816d7fc97
+size 35504
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..34fa39c82699d3610124198fb41b6f5b257e8b5a
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:79392068de2c3193fac57ee186fca3a413edb6289ac3acc873457312ad46990b
+size 116732
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..529e4f72f14cdf7f41f56cfbfb26655bf8181c59
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:abb9e3ec6dfc8364cedc39a68cf796e9d3ff5529c79a1811eedeb12c6d6e7583
+size 3787
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/ae0a735d106290c594b0bafb1f5e72e7_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/ae0a735d106290c594b0bafb1f5e72e7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..07e9af85dfe559e0d52380b66fa6bd4cfbb59abf
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/ae0a735d106290c594b0bafb1f5e72e7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5477ea85de1f29aa617570d5900708d102a82861fa5f8d084dd125aa43fc769c
+size 38044
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/aeb2a26a07219661191294dba528067a_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/aeb2a26a07219661191294dba528067a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6d550891b0bd6f3b024303643306526585e9a836
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/aeb2a26a07219661191294dba528067a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c4212e504adec84426c69cad3261a6df3baf6fb1c2447d3802955dfda7ac5e84
+size 62858
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/b4cbe4bfe7868be70d1549b983749783_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/b4cbe4bfe7868be70d1549b983749783_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5550752b88c949c2adcf8d1389e1085f01ee4de8
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/b4cbe4bfe7868be70d1549b983749783_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae0136225b1a8801aeba8771678f0dee2ed1d95f9b2ddee3c2ad58044e2631b7
+size 22841
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/b73fce8bb6592c6a3c0cd51e9c08d517_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/b73fce8bb6592c6a3c0cd51e9c08d517_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..93cdc0fc520ca503ba76cc594e7d31aad079e7aa
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/b73fce8bb6592c6a3c0cd51e9c08d517_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:625098017de7112abef49f24dbca719665b06673d86f5b4d5effbddf106e3c63
+size 52168
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/c0ea30a51ceaa378aa076393915edc1d_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/c0ea30a51ceaa378aa076393915edc1d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7d4dfba0ce90e9af011676d34b0e16974104dcc7
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/c0ea30a51ceaa378aa076393915edc1d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8e5b389c4b8f5b75d556451860198c917b13e85aea59600b7493858ceb43debc
+size 107238
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/c700124873e73d0731c82ef7e12b71f4_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/c700124873e73d0731c82ef7e12b71f4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0d9790354043caf6013abe67ff1013bd1dca921f
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/c700124873e73d0731c82ef7e12b71f4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd49ca2c0ecbf01291d5bf1ae86c1e97f33b1dc7ca6cc3714ee5ef6803f25f4f
+size 44325
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c2ff577d303861e5052adea2312024c02fce75da
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dd7ffae0cf1ac7f7ea21a199d6bdff24e47a2fe55b29afa30439130eec70bd91
+size 73658
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f740f669e36ef1e17094b27b19726fbdf95b97fb
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9fd6f94a3e9cdb6ccde2d0cad0af103cba79dd2890e1a2e1c00d492cea4c1821
+size 52656
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/d5de4c1d2f0b71aa339b6b2118268fbb_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/d5de4c1d2f0b71aa339b6b2118268fbb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ae832e04f305ccfdb89e6e23861c9b66723d021d
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/d5de4c1d2f0b71aa339b6b2118268fbb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9666667b64c7b18c99873d0a73b33858d1f8350c11723c94ba832d47cf107930
+size 22834
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/e010000311ed958dd0bc2b16f8cc23d4_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/e010000311ed958dd0bc2b16f8cc23d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ca0d826bef2aeeb78e5a967eff8d6cfb659eea6c
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/e010000311ed958dd0bc2b16f8cc23d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:57b7a4441024569a11629058193408569fbfc7e594398e7de93284b0d3612dca
+size 36607
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/e22af684d8e56d4c61e61bb5ddac1087_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/e22af684d8e56d4c61e61bb5ddac1087_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a709f3696f1fc243195bd0994ba9b9d5c0cd945e
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/e22af684d8e56d4c61e61bb5ddac1087_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b75d4923f35b7d60c53ab842fd9f9c8768d6b5189896c1e7c3958ec79eac2855
+size 55800
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1200293f35944a6e744d4f022c33f94eccf2ce9f
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:146ec73aaa746c93cef7ef61315868929b40dd52996d5d5030c508ddad93cb49
+size 80811
diff --git a/marked/Q/T-REC-Q.1743-201609-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..73b93e0b33f07eed1540fddfcd8c363142a3ee38
--- /dev/null
+++ b/marked/Q/T-REC-Q.1743-201609-I_PDF-E/raw.md
@@ -0,0 +1,10022 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.1743**
+
+(09/2016)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Signalling requirements and protocols for IMT-2000
+
+---
+
+**IMT-Advanced references to Release 11 of
+LTE-Advanced evolved packet core network**
+
+Recommendation ITU-T Q.1743
+
+# 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 |
+| 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.1743
+
+# IMT-Advanced references to Release 11 of LTE-Advanced evolved packet core network
+
+## Summary
+
+Recommendation ITU-T Q.1743 identifies a release of the IMT-Advanced family member, "LTE-Advanced evolved packet core (EPC) network". This release of the family member is known to the Standards Development Organizations (i.e., ARIB, CCSA, ETSI, ATIS, TTA, TTC) as the "3GPP Release 11".
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.1743 | 2016-09-29 | 13 | 11.1002/1000/12982 |
+
+## Keywords
+
+Core network, evolved packet core, EPC, evolved packet system, EPS, IMT-Advanced, LTE-Advanced, Release 11.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2017
+
+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 |
+| 2.1 | Normative references..... | 1 |
+| 2.2 | Informative references..... | 3 |
+| 3 | Definitions ..... | 4 |
+| 4 | Abbreviations and acronyms ..... | 26 |
+| 5 | Introduction..... | 34 |
+| 6 | Basic EPC Architecture for LTE-Advanced evolved packet system (EPS)..... | 34 |
+| 6.1 | Architecture for 3GPP accesses..... | 34 |
+| 6.2 | Architecture for non-3GPP accesses ..... | 36 |
+| 6.3 | Architecture for MBMS ..... | 41 |
+| 6.4 | Architecture of E-UTRAN LCS ..... | 42 |
+| 6.5 | Architecture for CBS ..... | 42 |
+| 6.6 | Architecture for policy control and charging ..... | 42 |
+| 6.7 | Architecture for CSFB..... | 44 |
+| 6.8 | Architecture for single radio voice call continuity ..... | 44 |
+| 6.9 | Architecture for home (e)NodeB entities ..... | 46 |
+| 6.10 | Architecture for machine-type communication..... | 46 |
+| 7 | Network entities..... | 47 |
+| 7.1 | Home subscriber server (HSS) ..... | 47 |
+| 7.2 | Serving GPRS support node (SGSN)..... | 52 |
+| | Mobility management entity (MME)..... | 52 |
+| 7.4 | Serving GW ..... | 53 |
+| 7.5 | PDN GW ..... | 54 |
+| 7.6 | EPC SGSN..... | 55 |
+| 7.7 | Trusted and untrusted non-3GPP access network ..... | 55 |
+| 7.8 | Enhanced packet data gateway (ePDG) ..... | 55 |
+| 7.9 | 3GPP AAA server ..... | 56 |
+| 7.10 | 3GPP AAA proxy..... | 56 |
+| 7.11 | Access network discovery and selection function (ANDSF) ..... | 56 |
+| 7.12 | Border gateway (BG) ..... | 56 |
+| 7.13 | The location services (LCS) entities..... | 56 |
+| 7.14 | Security gateway (SEG) ..... | 57 |
+| 7.15 | Application Function (AF) ..... | 57 |
+| 7.16 | Multimedia broadcast multicast service (MBMS) specific entities ..... | 57 |
+| 7.17 | Generic user profile (GUP) server..... | 57 |
+| 7.18 | Policy and charging rules function (PCRF)..... | 58 |
+
+| | | |
+|-------|------------------------------------------------------------------------------------------------------------|-----|
+| 7.19 | Policy and charging enforcement function (PCEF)..... | 58 |
+| 7.20 | Support of short message service over generic 3GPP Internet protocol access (SMSIP) specific entities..... | 59 |
+| 7.21 | Subscription profile repository (SPR) ..... | 59 |
+| 7.22 | Service data flow based credit control function ..... | 59 |
+| 7.23 | Bearer binding and event reporting function (BBERF) ..... | 59 |
+| 7.24 | Traffic detection function (TDF)..... | 59 |
+| 7.25 | Home (e)NodeB entities ..... | 60 |
+| 7.26 | Specific entities to facilitate communications with packet data networks and applications ..... | 61 |
+| 8 | Interfaces and reference points ..... | 61 |
+| 8.1 | LCS interfaces related to the evolved packet core (EPC) ..... | 61 |
+| 8.2 | Reference point PDG – Packet data networks (Wi reference point) ..... | 62 |
+| 8.3 | Reference point WAG – WLAN access network (Wn reference point) ..... | 62 |
+| 8.4 | Interfaces internal to, or related to the evolved packet core (EPC)..... | 62 |
+| 8.5 | Reference points for 3GPP/WLAN interworking ..... | 68 |
+| 8.6 | MBMS specific reference points for EPS ..... | 71 |
+| 8.7 | Reference points for 3GPP generic user profile (GUP) ..... | 72 |
+| 8.8 | Reference points for policy and charging control ..... | 73 |
+| 8.9 | Reference point IP-SM-GW – HSS (J reference point) ..... | 75 |
+| 8.10 | Reference point application front ends – UDR (Ud reference point)..... | 75 |
+| 8.11 | Specific reference points for facilitating communications with packet data networks and applications ..... | 75 |
+| 9 | Technical specifications structure..... | 76 |
+| 10 | Technical specifications..... | 77 |
+| 10.1 | 21-series, Requirements ..... | 77 |
+| 10.2 | 22-series, Service aspects ..... | 78 |
+| 10.3 | 23-Series, Technical realisation..... | 116 |
+| 10.4 | 24-series, Signalling protocols – user equipment to network..... | 142 |
+| 10.5 | 26-series, CODECs..... | 158 |
+| 10.6 | 27-series, Data ..... | 192 |
+| 10.7 | 29-series, Signalling protocols – intra-fixed-network ..... | 197 |
+| 10.8 | 31-series, Subscriber identity module (SIM / USIM), IC cards. Test specifications ..... | 226 |
+| 10.9 | 32-series, OAM&P and Charging ..... | 235 |
+| 10.10 | 33-series, Security aspects ..... | 301 |
+| 10.11 | 35-series, Security algorithms ..... | 314 |
+
+# IMT-Advanced references to Release 11 of LTE-Advanced evolved packet core network
+
+# 1 Scope
+
+This Recommendation identifies the IMT-Advanced family member, "LTE-Advanced evolved packet core network". This release of the family member is known to the Standards Development Organizations (i.e., ARIB, CCSA, ETSI, ATIS, TTA, TTC) as the "3GPP Release 11".
+
+The core network interfaces identified in this Recommendation and the radio interfaces and radio access interfaces which are identified in [ITU-R M.2012] Annex 1 constitute a complete system specification for the terrestrial usage of this IMT-advanced family member.
+
+It is the intent of the ITU-T that the references in this Recommendation are only to specifications that specify the core network aspects of this IMT-Advanced Family Member. In the event that a referenced specification also includes material that specifies any of the radio aspects of this IMT-advanced family member, [ITU-R M.2012] shall take precedence.
+
+NOTE – The structure and content of this Recommendation have been organized for ease of use by those familiar with the original source material; as such, the usual style of ITU-T Recommendations has not been applied.
+
+# 2 References
+
+## 2.1 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; 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 I.113] Recommendation ITU-T I.113 (1997), *Vocabulary of terms for broadband aspects of ISDN*.
+- [ITU-T I.112] Recommendation ITU-T I.112 (1993), *Vocabulary of terms for ISDNs*.
+- [ITU-R M.2012-2] Recommendation ITU-R M.2012-2 (2015), *Detailed specifications of the terrestrial radio interfaces of International Mobile Telecommunications-Advanced (IMT-Advanced)*.
+- [ETSI TS 123 002] ETSI TS 123 002 (2013), *Network architecture (Release 11)*.
+- [TTC TS-3GA-23.002] TTC TS-3GA-23.002 (2013), *Network architecture (Release 11)*.
+- [ATIS 3GPP 23.002] ATIS 3GPP 23.002 (2013), *Network architecture (Release 11)*.
+- [TTA TTAT.3G-23.002] TTA TTAT.3G-23.002 (2013), *Network architecture (Release 11)*.
+- [TTC TS-3GA-23.060] TTC TS-3GA-23.060 (2014), *General Packet Radio Service (GPRS) Service description; Stage 2 (Release 11)*.
+- [ETSI TS 123 060] ETSI TS 123 060 (2015), *General Packet Radio Service (GPRS) Service description; Stage 2 (Release 11)*.
+
+| | |
+|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [TTA TTAT.3G-23.060] | TTA TTAT.3G-23.060 (2013), General Packet Radio Service (GPRS) Service description; Stage 2 (Release 11) . |
+| [ARIB STD-T63-23.203] | ARIB STD-T63-23.203 (2014), Policy and charging control architecture (Release 11) . |
+| [ETSI TS 123 203] | ETSI TS 123 203 (2014), Policy and charging control architecture(Release 11) . |
+| [ATIS 3GPP 23.203] | ATIS 3GPP 23.203 (2014), Policy and charging control architecture(Release 11) . |
+| [TTA TTAT.3G-23.203] | TTA TTAT.3G-23.203 (2013), Policy and charging control architecture(Release 11) . |
+| [ETSI TS 123 234] | ETSI TS 123 234 (2012), 3GPP system to Wireless Local Area Network (WLAN) interworking; System description (Release 11) . |
+| [TTC TS-3GA-23.234] | TTC TS-3GA-23.234 (2013), 3GPP system to Wireless Local Area Network (WLAN) interworking; System description (Release 11) . |
+| [ATIS 3GPP 23.234] | ATIS 3GPP 23.234 (2014), 3GPP system to Wireless Local Area Network (WLAN) interworking; System description (Release 11) . |
+| [TTA TTAT.3G-23.234] | TTA TTAT.3G-23.234 (2013), 3GPP system to Wireless Local Area Network (WLAN) interworking; System description (Release 11) . |
+| [ETSI TS 123 246] | ETSI TS 123 246 (2014), Multimedia broadcast/multicast service (MBMS); architecture and functional description . |
+| [TTC TS-3GA-23.246] | TTC TS-3GA-23.246 (2013), Multimedia broadcast/multicast service (MBMS); architecture and functional description . |
+| [ATIS 3GPP 23.246] | ATIS 3GPP 23.246 (2013), Multimedia broadcast/multicast service (MBMS); architecture and functional description . |
+| [TTA TTAT.3G-23.246] | TTA TTAT.3G-23.246(2013), Multimedia broadcast/multicast service (MBMS); architecture and functional description . |
+| [ETSI TS 123 401] | ETSI TS 123 401(2014), General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access . |
+| [TTC TS-3GA-23. 401] | TTC TS-3GA-23.401 (2014), General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access . |
+| [ATIS 3GPP 23. 401] | ATIS 3GPP 23.401 (2013), General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access . |
+| [TTA TTAT.3G-23.401] | TTA TTAT.3G-23.401(2013), General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access . |
+| [ETSI TS 123 402] | ETSI TS 123 402 (2013), Architecture enhancements for non-3GPP accesses . |
+| [TTC TS-3GA-23.402] | TTC TS-3GA-23.402 (2014), Architecture enhancements for non-3GPP accesses . |
+| [ATIS 3GPP 23.402] | ATIS 3GPP 23.402 (2013), Architecture enhancements for non-3GPP accesses . |
+
+| | |
+|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------|
+| [TTA TTAT.3G-23.402] | TTA TTAT.3G-23.402 (2013), Architecture enhancements for non-3GPP accesses. |
+| [TTC TS-3GA-23.682] | TTC TS-3GA-23.682 (2013), Architecture enhancements to facilitate communications with packet data networks and applications. |
+| [ETSI TS 123 682] | ETSI TS 123 682 (2013), Architecture enhancements to facilitate communications with packet data networks and applications. |
+| [ATIS 3GPP 23.682] | ATIS 3GPP 23.682 (2014), Architecture enhancements to facilitate communications with packet data networks and applications. |
+| [TTA TTAT.3G-23.682] | TTA TTAT.3G-23.682 (2013), Architecture enhancements to facilitate communications with packet data networks and applications. |
+| [ARIB STD-T63-26.346] | ARIB STD-T63-26.346 (2014), Multimedia broadcast/multicast service (MBMS); Protocols and codecs. |
+| [ETSI TS 126 346] | TS 126 346 (2014), Multimedia broadcast/multicast service (MBMS); Protocols and codecs. |
+| [ATIS 3GPP 26.346] | ATIS.3GPP.26.346 (2014), Multimedia broadcast/multicast service (MBMS); Protocols and codecs. |
+| [TTA TTAT.3G-26.346] | TTAT.3G-26.346 (2013), Multimedia broadcast/multicast service (MBMS); Protocols and codecs. |
+
+## 2.2 Informative references
+
+| | |
+|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [ITU-T F.703] | Recommendation ITU-T F.703 (2000), Multimedia conversational services. |
+| [ITU-T H.248.1] | Recommendation ITU-T H.248.1 (2002), Gateway control protocol: Version 1 |
+| [ITU-T H.323] | Recommendation ITU-T H.323 (2009), Packet-based multimedia communications systems. |
+| [ITU-T I.130] | Recommendation ITU-T I.130 (1988), Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN. |
+| [ITU-T I.210] | Recommendation ITU-T I.1210 (1993), Principles of telecommunication services supported by an ISDN and the means to describe them. |
+| [ITU-T I.350] | Recommendation ITU-T I.350 (1993), General aspects of quality of service and network performance in digital networks, including ISDNs. |
+| [ITU-T Q.65] | Recommendation ITU-T Q.65 (2000), The unified functional methodology for the characterization of services and network capabilities including alternative object oriented techniques. |
+| [ITU-T Q.1001] | Recommendation ITU-T Q.1001 (1988), General aspects of public land mobile networks. |
+| [ITU-T T.32] | Recommendation ITU-T T.32 (1995), Asynchronous facsimile DCE control – Service Class 2. |
+| [ITU-T V.24] | Recommendation ITU-T V.24 (2000), List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE). |
+
+| | |
+|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [ITU-T V.80] | Recommendation ITU-T V.80 (1996), In-band DCE control and synchronous data modes for asynchronous DTE . |
+| [ITU-T X.25] | Recommendation ITU-T X.25 (1996), Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit . |
+| [ITU-T X.140] | Recommendation ITU-T X.140 (1992), General quality of service parameters for communication via public data networks . |
+| [ITU-T X.213] | Rec. ITU-T X.213 (2001) ISO/IEC 8348: 2002, Information technology – Open Systems Interconnection – Network service definition . |
+| [ARIB TR-T12-21.905] | ARIB TR-T12-21.905 (2012), Vocabulary for 3GPP Specifications . |
+| [ETSI TR 121 905] | ETSI TR 121 905 (2013), Vocabulary for 3GPP Specifications . |
+| [ATIS 3GPP TR 21.905] | ATIS 3GPP TR 21.905 (2014), Vocabulary for 3GPP Specifications . |
+| [TTA TR-3GA-21.905] | TTA TTAT.3G-21.905 (2013), Vocabulary for 3GPP Specifications . |
+| [TTC TR-3GA-21.905] | TTC TR-3GA-21.905 (2013), Vocabulary for 3GPP Specifications . |
+
+# 3 Definitions
+
+The text is based on references in clause 2.2.
+
+This Recommendation defines the following terms:
+
+**3.0 3GPP generic user profile (GUP):** The 3GPP generic user profile is the collection of user related data which affects the way in which an individual user experiences services and which may be accessed in a standardised manner.
+
+**3.1 A/Gb mode:** Mode of operation of the MS when connected to the core network via GERAN and the A and/or Gb interfaces.
+
+**3.2 applet:** A small program that is intended not to be run on its own, but rather to be embedded inside another application.
+
+**3.3 application:** An application is a service enabler deployed by service providers, manufacturers or users. Individual applications will often be enablers for a wide range of services.
+
+**3.4 application interface:** Standardized interface used by application/clients to access service capability features.
+
+**3.5 application protocol:** The set of procedures required by the application.
+
+**3.6 authentication:** A property by which the correct identity of an entity or party is established with a required assurance. The party being authenticated could be a user, subscriber, home environment or serving network.
+
+**3.7 base station:** A base station is a network element in radio access network responsible for radio transmission and reception in one or more cells to or from the user equipment. A base station can have an integrated antenna or be connected to an antenna by feeder cables. In UTRAN, it terminates the Iub interface towards the RNC. In GERAN, it terminates the Abis interface towards the BSC.
+
+**3.8 base station subsystem:** Either a full network or only the access part of a GERAN offering the allocation, release and management of specific radio resources to establish means of connection between an MS and the GERAN. A base station subsystem is responsible for the resources and transmission/reception in a set of cells.
+
+- 3.9 baseline capabilities:** Capabilities which are required for a service-less user equipment (UE) to operate within a network. The baseline capabilities for a UE include the capabilities to search for, synchronise with and register (with authentication) to a network. The negotiation of the UE and the network capabilities, as well as the maintenance and termination of the registration are also part of the required baseline capabilities.
+- 3.10 baseline implementation capabilities:** Set of Implementation capabilities, in each technical domain, required to enable a UE to support the required Baseline capabilities.
+- 3.11 basic telecommunication service:** This term is used as a common reference to both bearer services and teleservices.
+- 3.12 bearer:** An information transmission path of defined capacity, delay and bit error rate, etc.
+- 3.13 bearer capability:** A transmission function, which the UE requests to the network.
+- 3.14 bearer independent protocol:** (UICC) Mechanism by which the ME provides the (U)SIM applications on the UICC with access to the data bearers supported by the ME and the network.
+- 3.15 bearer service:** A type of telecommunication service that provides the capability of transmission of signals between access points.
+- 3.16 billing:** A function whereby CDRs generated by the charging function are transformed into bills requiring payment.
+- 3.17 broadcast:** A value of the service attribute "communication configuration", which denotes unidirectional distribution to all users (source: [ITU-T I.113]).
+- 3.18 byte code:** (UICC) A hardware machine-independent representation of a primitive computer operation that serves as an instruction to a software program called an interpreter or a virtual machine that simulates the hypothetical computer's central processing unit. Code generated by a Java compiler and executed by the Java interpreter.
+- 3.19 call:** A logical association between several users (this could be connection-oriented or connectionless).
+- 3.20 charging data record (CDR):** A formatted collection of information about a chargeable event (e.g., time of call set-up, duration of the call, amount of data transferred, etc.) for use in billing and accounting. For each party to be charged for parts of or all charges of a chargeable event, a separate CDR shall be generated, i.e., more than one CDR may be generated for a single chargeable event, e.g., because of its long duration, or because more than one charged party is to be charged.
+- 3.21 cell:** Radio network object that can be uniquely identified by a user equipment from a (cell) identification that is broadcasted over a geographical area from one UTRAN or GERAN access point. A Cell in UTRAN is either FDD or TDD mode.
+- 3.22 cellular text telephone modem (CTM):** A modulation and coding method intended for transmission of text in voice channels for the application of real-time text conversation.
+- 3.23 charging:** A function whereby information related to a chargeable event is formatted and transferred in order to make it possible to determine usage for which the charged party may be billed.
+- 3.24 cipher key:** A code used in conjunction with a security algorithm to encode and decode user and/or signalling data.
+- 3.25 closed user group:** A group with a predefined set of members. Only defined members may participate in a closed group.
+
+- 3.26 confidentiality:** The avoidance of disclosure of information without the permission of its owner.
+- 3.27 connection:** A communication channel between two or more end-points (e.g., terminal, server, etc.).
+- 3.28 connectionless (for a bearer service):** In a connectionless bearer, no connection is established beforehand between the source and the destination entities; the source and destination network addresses need to be specified in each message. Transferred information cannot be guaranteed of ordered delivery. Connectionless bearer services lifetime is reduced to the transport of one message.
+- 3.29 connectionless service:** A service, which allows the transfer of information among service users without the need for end-to-end call establishment procedures (source: [ITU-T I.113]).
+- 3.30 control channel:** A logical channel that carries system control information.
+- 3.31 core network:** An architectural term relating to the part of a 3G system, which is independent of the connection technology of the terminal (e.g., radio, wired).
+- 3.32 core network operator:** Operator that offers core network services.
+- 3.33 corporate code:** Code which, when combined with the network and SP codes, refers to a unique corporate. The code is provided in the GID2 file on the (U)SIM and is correspondingly stored on the ME.
+- 3.34 corporate code group:** Combination of the corporate code and the associated SP and network codes.
+- 3.35 corporate personalization:** Allows a corporate customer to personalize MEs that he provides for his employees or customers use so that they can only be used with the company's own (U)SIMs.
+- 3.36 coverage area (of a mobile cellular system):** An area where mobile cellular services are provided by that mobile cellular system to the level required of that system.
+- 3.37 coverage area:** Area over which a 3G system service is provided with the service probability above a certain threshold.
+- 3.38 current directory:** The latest MF or DF selected on the UICC.
+- 3.39 current EF:** The latest EF selected.
+- 3.40 current serving cell:** This is the cell on which the MS is camped.
+- 3.41 data object:** Information coded as TLV objects, i.e., consisting of a tag, a length and a value part.
+- 3.42 dedicated channel:** A channel dedicated to a specific UE.
+- 3.43 de-personalization:** The process of deactivating the personalization so that the ME ceases to carry out the verification checks.
+- 3.44 dedicated file (DF):** A file containing access conditions and, optionally, elementary files (EFs) or other dedicated files (DFs).
+- 3.45 delivered QoS:** Actual QoS parameter values with which the content was delivered over the lifetime of a QoS session.
+- 3.46 demand service:** A type of telecommunication service in which the communication path is established almost immediately, in response to a user request effected by means of user-network signalling (source: [ITU-T I.112]).
+
+**3.47 dependability:** A performance criterion that describes the degree of certainty (or surety) with which a function is performed regardless of speed or accuracy, but within a given observational interval (source: [ITU-T I.350]).
+
+**3.48 destination user:** Entity to which calls to the general packet radio service (GPRS) are directed.
+
+**3.49 directory:** General term for the MF and/or a DF on the UICC.
+
+**3.50 directory number:** A string consisting of one or more of the characters from the set {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, \*, #, a, b, c} associated with a nature of address indicator and number plan indicator. When using the public MMI for the control of supplementary services however, \* and # cannot be part of any SC or SI field.
+
+NOTE 1 – No such restriction on the SC and SI fields exists when using other (e.g., menu-driven) MMI for the control of supplementary services.
+
+NOTE 2 – When using the public MMI, certain limitations on the use of one- and two-digit directory numbers may apply. The use of other MMI can remove these restrictions.
+
+NOTE 3 – This definition is not intended to require the support of all these characters in the MMI itself.
+
+**3.51 distribution service:** Service characterized by the unidirectional flow of information from a given point in the network to other (multiple) locations (source: [ITU-T I.113]).
+
+**3.52 domain:** The highest-level group of physical entities. Reference points are defined between domains.
+
+**3.53 donor network:** The subscription network from which a number is ported in the porting process. This may or may not be the number range owner network.
+
+**3.54 downlink:** Unidirectional radio link for the transmission of signals from a UTRAN access point to a UE. Also in general the direction from network to UE.
+
+**3.55 drift RNS:** The role an RNS can take with respect to a specific connection between a UE and UTRAN. An RNS that supports the serving RNS with radio resources when the connection between the UTRAN and the user equipment needs to use cell(s) controlled by this RNS is referred to as "Drift RNS".
+
+**3.56 element manager:** Provides a package of end-user functions for management of a set of closely related types of network elements. These functions can be divided into two main categories.
+
+**3.57 elementary file (EF):** A file containing access conditions and data and no other files on the UICC.
+
+**3.58 end-user:** An end-user is an entity (typically a user), associated with one or multiple subscriptions through identities (e.g., IMSIs, MSISDNs, IMPIs, IMPUs and application-specific identities). In the 3GPP system an end-user is characterised by an end-user identity.
+
+**3.59 end-user identity (EUI):** An end-user identity is an identity that uniquely characterises an end-user in the 3GPP system. An end-user identity is mainly intended for administration purposes of the operator.
+
+**3.60 enterprise systems:** Information systems that are used in the telecommunication organisation but are not directly or essentially related to the telecommunications aspects (call centre's, fraud detection and prevention systems, invoicing, etc.).
+
+**3.61 essential UE requirement (conditional):** Requirement which has to be implemented under certain service conditions, e.g., AMR codec in UE which supports speech service.
+
+**3.62 essential UE requirement (unconditional):** Requirement which has to be implemented in any 3G UE in order to exist in and communicate with the 3G network (e.g., chip rate of 3.84 Mcps).
+
+- 3.63 evolved packet core:** A framework for an evolution or migration of the 3GPP system to a higher-data-rate, lower-latency, packet-optimized system that supports, multiple RATs.
+- 3.64 evolved packet systems:** An evolution of the 3G UMTS characterized by higher-data-rate, lower-latency, packet-optimized system that supports multiple RATs. The evolved packet system comprises the evolved packet core together with the evolved radio access network (E-UTRA and E-UTRAN).
+- 3.65 evolved UTRA:** Evolved UTRA is an evolution of the 3G UMTS radio-access technology towards a high-data-rate, low-latency and packet-optimized radio-access technology.
+- 3.66 evolved UTRAN:** Evolved UTRAN is an evolution of the 3G UMTS radio-access network towards a high-data-rate, low-latency and packet-optimized radio-access network.
+- 3.67 explicit diversity gain (dB):** The effective gain achieved using diversity techniques.
+- 3.68 extra SDU delivery probability:** The ratio of total (unrequested) extra service data units (SDUs) to total service data units received by a destination user in a specified sample (source: [ITU-T X.140]).
+- 3.69 file:** A named and hierarchically-classified data set on the UICC.
+- 3.70 file identifier (FID):** The 2-byte name of a file or a directory on the UICC.
+- 3.71 fixed network user rate:** The user rate between IWF and the fixed network.
+- 3.72 flow control (FC):** A set of mechanisms used to prevent the network from becoming overloaded by regulating the input rate transmissions.
+- 3.73 flexible layer one (FLO):** GERAN feature that allows the channel coding of the layer one to be configured at call set-up.
+- 3.74 framework:** A framework defines a set of application programming interface (API) classes for developing applications and for providing system services to those applications.
+- 3.75 functional group:** A set of functions that may be performed by a single equipment (source: [ITU-T I.112]).
+- 3.76 geographical routing:** The conversion of the PDU's geographical area definition, which specifies the area in which the PDU will be broadcast, into an equivalent radio coverage map.
+- 3.77 GERAN radio network temporary identifier (G-RNTI):** An MS identifier which is allocated by the serving BSC and is unique within this SBSC. It is allocated for all MSs having an RRC connection. The G-RNTI is always reallocated when the Serving BSC for the RRC connection is changed and deallocated when the RRC connection is released. The G-RNTI is also used at RLC/MAC during contention resolution.
+- 3.78 GPRS MS:** An MS capable of GPRS services.
+- 3.79 group:** A set of members allowed to participate in the group call service. The group is defined by a set of rules that identifies a collection of members implicitly or explicitly. These rules may associate members for the purpose of participating in a group call, or may associate members who do not participate in data transfer but do participate in management, security, control, or accounting for the group.
+- 3.80 group call:** The relationship that exists between the members of a group for the purpose of transferring data. More than one group call may exist in a group. A group call establishes an active group.
+- 3.81 group call initiator:** A member (or third party) authorized to initiate a group call. More than one member may initiate group calls.
+
+- 3.82 group call participant:** A member of a group participating in a particular group call at a given time.
+- 3.83 group call server:** A logical entity that provides the group call service to the members.
+- 3.84 group call service:** A PTM service in which a relationship exists between participants of the group, and in which a single data unit transmitted by a source participant is received by multiple destination participants; it is a one-in, many-out service.
+- 3.85 group controller:** The member (or third party) responsible for the group creation and membership control.
+- 3.86 GSM/EDGE radio access network (GERAN):** A conceptual term identifying that part of the network which consists of BSCs and BTSs between A/Gb or Iu and Um interfaces.
+- 3.87 GSM BSS:** Refers in this Recommendation to the GSM/GPRS access network.
+- 3.88 GSM core network:** Refers in this Recommendation to the GSM NSS and GPRS backbone infrastructure.
+- 3.89 GSM coverage:** An area where mobile cellular services are provided in accordance with GSM standards.
+- 3.90 GSM session:** That part of the card session dedicated to the GSM operation.
+- 3.91 guaranteed service:** A service model which provides highly reliable performance, with little or no variance in the measured performance criteria.
+- 3.92 handoff gain/loss (dB):** This is the gain/loss factor (+ or –) brought by handoff to maintain specified reliability at the cell boundary.
+- 3.93 handover:** The transfer of a user's connection from one radio channel to another (can be the same or different cell).
+- 3.94 handover:** The process in which the radio access network changes the radio transmitters or radio access mode or radio system used to provide the bearer services, while maintaining a defined bearer service QoS.
+- 3.95 hard handover:** A category of handover procedures where all the old radio links in the UE are abandoned before the new radio links are established.
+- 3.96 heterogeneous network:** A 3GPP access network consisting of multiple cells with different characteristics (e.g., for the case of E-UTRA: a variety of e-NodeBs, Home e-NodeBs, e-UTRA Relays).
+- 3.97 home environment value-added service provider (HE-VASP):** This is a VASP that has an agreement with the home environment to provide services. The home environment provides services to the user in a managed way, possibly by collaborating with HE-VASPs, but this is transparent to the user. The same service could be provided by more than one HE-VASP and each HE-VASP can provide more than one service.
+- 3.98 home environment:** Responsible for overall provision and control of the personal service environment (PSE) of its subscribers.
+- 3.99 home PLMN:** PLMN where the mobile country code (MCC) and mobile network code (MNC) of the PLMN identity are the same as the MCC and MNC of the IMSI.
+- 3.100 IC card:** A card holding an integrated circuit containing subscriber, end-user, authentication and/or application data for one or more applications.
+- 3.101 idle mode:** The state of UE switched on but which does not have any established RRC connection.
+
+**3.102 implementation capability:** A capability that relates to a particular technical domain. Examples: a spreading factor of 128 (in the domain of the physical layer); the A5 algorithm; a 64-bit key length (in the domain of security); a power output of 21 dBm (in the domain of transmitter performance); support of AMR codec (in the domain of the codec); support of CHV1 (in the domain of the USIM).
+
+**3.103 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.104 information data rate:** Rate of the user information, which must be transmitted over the air interface. For example, output rate of the voice codec.
+
+**3.105 initial paging information:** This information indicates if the UE needs to continue to read more paging information and eventually receive a page message.
+
+**3.106 initial paging occasion:** The paging occasion the UE uses as starting point for its paging DRX cycle.
+
+**3.107 integrity:** (in the context of security) The avoidance of unauthorized modification of information.
+
+**3.108 inter-cell handover:** A handover between different cells. An inter-cell handover requires network connections to be altered.
+
+**3.109 inter-PLMN handover:** Handover between different PLMNs, i.e., having different MCC-MNC.
+
+**3.110 inter-system handover:** Handover between networks using different radiosystems, e.g., UMTS – GSM.
+
+**3.111 interactive service:** A service which provides the means for bidirectional exchange of information between users. Interactive services are divided into three classes of services: conversational services, messaging services and retrieval services (source: [ITU-T I.113]).
+
+**3.112 interface:** The common boundary between two associated systems (source: [ITU-T I.112]).
+
+**3.113 international mobile station equipment identity (IMEI):** An "International mobile station equipment identity" is a unique number, which shall be allocated to each individual mobile station equipment in the PLMN and shall be unconditionally implemented by the MS manufacturer.
+
+**3.114 international mobile user number (IMUN):** The international mobile user number is a dialable number allocated to a 3GPP system user.
+
+**3.115 interpreter:** A software program that simulates a hypothetical computer by performing the operations defined by the instructions of this computer. (See also "byte code" and "virtual machine").
+
+**3.116 interworking WLAN (I-WLAN):** A WLAN that interworks with a 3GPP system.
+
+**3.117 intra-cell handover:** A handover within one sector or between different sectors of the same cell. An intra-cell handover does not require network connections to be altered.
+
+**3.118 intra-PLMN handover:** Handover within the same network, i.e., having the same MCC-MNC regardless of radio access system.
+
+NOTE – This includes the case of UMTS <> GSM handover where MCC-MNC are the same in both cases.
+
+**3.119 IP-connectivity access network (IP-CAN):** The collection of network entities and interfaces that provides the underlying IP transport connectivity between the UE and the IMS entities. An example of an "IP-connectivity access network" is GPRS.
+
+**3.120 IP-connectivity access network bearer (IP-CAN bearer):** The data communications bearer provided by the IP-connectivity access network. When using GPRS, the IP-connectivity access network bearers are provided by PDP Contexts.
+
+**3.121 IRP information model:** An IRP information model consists of an IRP information service and a network resource model (see below for definitions of "IRP information service" and "Network resource model").
+
+**3.122 IRP information service:** An IRP information service describes the information flow and support objects for a certain functional area, e.g., the alarm information service in the fault management area. As an example of support objects, for the alarm IRP there is the alarm record and alarm list.
+
+**3.123 IRP solution set:** An IRP solution set is a mapping of the IRP information service to one of several technologies (CORBA/IDL, SNMP/SMI, CMIP/GDMO, etc.). An IRP information service can be mapped to several different IRP solution sets. Different technology selections may be done for different IRPs.
+
+**3.124 inter-system change:** A change of radio access between different radio access technologies such as GSM and UMTS.
+
+**3.125 IMS multimedia telephony:** A service that allows multimedia conversational communications between two or more users. It provides real time bidirectional conversational transfer of media, e.g., speech, video, text or other types of data. The IMS multimedia telephony service includes supplementary services and takes account of regulatory requirements.
+
+**3.126 IMS SIM (ISIM):** An application residing on the UICC that provides access to IP multimedia services.
+
+**3.127 Iu:** Interconnection point between an RNC and a core network. It is also considered as a reference point.
+
+**3.128 Iu-flex:** Routing functionality for intradomain connection of RAN nodes to multiple CN nodes.
+
+**3.129 Iu mode:** Mode of operation of the MS when connected to the core network via GERAN or UTRAN and the Iu interface.
+
+**3.130 Iub:** Interface between an RNC and a Node B.
+
+**3.131 Iur:** A logical interface between two RNC. Whilst logically representing a point-to-point link between RNC, the physical realization may not be a point-to-point link.
+
+**3.132 key pair:** Key pairs are matching private and public keys. If a block of data is encrypted using the private key, the public key from the pair can be used to decrypt it. The private key is never divulged to any other party, but the public key is available, e.g., in a certificate.
+
+**3.133 local service:** Services, which are provided by current roamed to network that are not HE services. The same service can be provided by a network as a local service to inbound roamers and as a HE service to the subscribers of this network.
+
+**3.134 local IP address:** Allows an IP-capable UE connected via a H(e)NB direct access to other IP-capable devices in the local residential/corporate IP network.
+
+**3.135 localized service area (LSA):** An operator-defined group of cells, for which specific access conditions apply. This may correspond to an area in which the core network offers specific services. A LSA may be defined within a PLMN or globally. Therefore, a LSA may offer a non-contiguous radio coverage.
+
+**3.136 location registration (LR):** The UE registers its presence in a registration area, for instance regularly or when entering a new registration area.
+
+**3.137 logical channel:** A logical channel is an information stream dedicated to the transfer of a specific type of information over the radio interface. Logical channels are provided on top of the MAC layer.
+
+**3.138 logical channel (UICC):** A command/response communication context multiplexed on the physical channel between the ME and the UICC.
+
+**3.139 logical model:** A logical model defines an abstract view of a network or network element by means of information objects representing network element, aggregations of network elements, the topological relationship between the elements, endpoints of connections (termination points), and transport entities (such as connections) that transport information between two or more termination points.
+
+The information objects defined in the logical model are used, among others, by connection management functions. In this way, a physical implementation independent management is achieved.
+
+**3.140 logical O&M:** The signalling associated with the control of logical resources (channels, cells) owned by the RNC but physically implemented in the Node B. The RNC controls these logical resources. A number of O&M procedures physically implemented in Node B impact on the logical resources and therefore require an information exchange between RNC and Node B. All messages needed to support this information exchange are classified as Logical O&M forming an integral part of NBAP.
+
+**3.141 LSA exclusive access cell:** A UE may only camp on this cell if the cell belongs to the LSAs to which the user has subscribed. Nevertheless, if no other cells are available, the UE of non-LSA users may originate emergency calls from this cell.
+
+**3.142 LSA only access:** When LSA only access applies to the user, the UE can only access cells that belong to the LSAs to which the user has subscribed. Outside the coverage area of the subscribed LSAs, the UE may camp on other cells and limited services apply.
+
+**3.143 LSA preferential access cell:** A LSA preferential access cell is a cell which is part of the LSA. UEs of users that have subscribed to a LSA of a LSA-preferential-access cell have higher priority to resources than non-LSA users in the same cell.
+
+**3.144 macro cells:** "Macro cells" are outdoor cells with a large cell radius.
+
+**3.145 macro diversity handover:** "Macro diversity" is an operation state in which a user equipment simultaneously has radio links with two or more UTRAN access points for the sole aim of improving quality of the radio connection or providing seamless.
+
+**3.146 management infrastructure:** The collection of systems (computers and telecommunications) a 3GPP system organization has in order to manage a 3GPP system.
+
+**3.147 mandatory UE requirement:** Regulatory requirement which is applicable to 3G UEs. It is determined by each country/region and beyond the scope of 3GPP specification (e.g., spurious emission in UK).
+
+**3.148 master file (MF):** The root directory of the file system hierarchy on the UICC.
+
+**3.149 maximum output power:** For UE, this is a measure of the maximum power supported by the UE (i.e., the actual power as would be measured assuming no measurement error) (TS 25.101). For FDD BS, the mean power level per carrier of the base station measured at the antenna connector in a specified reference condition (TS 25.104). For TDD BS, this refers to the measure of power when averaged over the transmit timeslot at the maximum power setting (TS 25.105).
+
+**3.150 maximum possible AIUR:** The highest possible AIUR that the multiple TCH/F can provide, e.g., 2 TCH/F using TCH/F9.6 provides a maximum possible AIUR of 19.2 kbit/s.
+
+- 3.151 maximum transmitter power per traffic channel (dBm):** The maximum power at the transmitter output for a single traffic channel.
+- 3.152 mean bit rate:** A measure of throughput. The average (mean) bit rate available to the user for the given period of time (source: [ITU-T I.210]).
+- 3.153 mean transit delay:** The average transit delay experienced by a (typically) large sample of PDUs within the same service category.
+- 3.154 medium access control:** A sub-layer of radio interface layer 2 providing unacknowledged data transfer service on logical channels and access to transport channels.
+- 3.155 messaging service:** An interactive service, which offers user-to-user communication between individual users via storage units with store-and-forward, mailbox and/or message handling (e.g., information editing, processing and conversion) functions (source: [ITU-T I.113]).
+- 3.156 MExE classmark:** A MExE classmark identifies a category of MExE UE supporting MExE functionality with a minimum level of processing, memory, display, and interactive capabilities. Several MExE classmarks may be defined to differentiate between the functionalities offered by different MExE UEs. A MExE application or applet defined as being of a specific MExE classmark indicates that it is supportable by a MExE UE of that classmark.
+- 3.157 MExE executable:** An executable is an applet, application, or executable content, which conforms to the MExE specification and may execute on the ME.
+- 3.158 MExE server:** A node supporting MExE services in the MExE service environment.
+- 3.159 MExE service:** A service enhanced (or made possible) by MExE technology.
+- 3.160 MExE service environment:** Depending on the configuration of the PLMN, the operator may be able to offer support to MExE services in various ways. Examples of possible sources are from traditional GSM nodes, IN nodes, operator-specific nodes, operator franchised nodes and services provider nodes, together with access to nodes external (i.e., vendor-specific) to the PLMN depending on the nature of the MExE service. These nodes are considered to constitute the MExE service environment. The MExE service environment shall support direct MExE UE to MExE UE interaction of MExE services.
+- 3.161 MExE SIM:** A (U)SIM application that is capable of storing a security certificate that is accessible using standard mechanisms.
+- 3.162 MExE subscriber:** The owner of a subscription who has entered into an agreement with a MExE service provider for MExE services.
+- 3.163 micro cells:** "Micro cells" are small cells.
+- 3.164 minimum transmit power:** The minimum controlled output power of the TDD BS is when the power control setting is set to a minimum value. This is when the power control indicates a minimum transmit output power is required (TS 25.105).
+- 3.165 mobile evaluated handover (MEHO):** A type of handover triggered by an evaluation made in the mobile. The mobile evaluates the necessity of handover based on the measured radio environment and based on criteria, defined by the network. When the evaluation meets the hand-off criteria the necessary information is sent from the mobile to the network. The network then decides on the necessity of the handover based on the reported evaluation result and other conditions, e.g., uplink radio environment and/or availability of network resources; the network may then execute the handover.
+- 3.166 mobile number portability:** The ability for a mobile subscriber to change subscription network within the same country whilst retaining their original MSISDN(s).
+
+- 3.167 mobile termination:** The mobile termination is the component of the mobile station which supports functions specific to management of the radio interface (Um).
+- 3.168 mobility:** The ability for the user to communicate whilst moving independent of location.
+- 3.169 mobility management:** A relation between the mobile station and the UTRAN that is used to set up, maintain and release the various physical channels.
+- 3.170 MTC device:** A MTC device is a UE equipped for machine type communication, which communicates through a PLMN with MTC Server(s) and/or other MTC Device(s).
+- 3.171 MTC server:** A MTC Server is a server, which communicates to the PLMN itself, and to MTC devices through the PLMN. The MTC server can also have an interface which can be accessed by the MTC user.
+- 3.172 MTC user:** A MTC user uses the service provided by the MTC server.
+- 3.173 MTC subscriber:** A MTC Subscriber is a subscriber, i.e., a legal entity having a contractual relationship with the network operator to provide service to one or more MTC Devices.
+- 3.174 multi-mode terminal:** UE that can obtain service from at least one UTRA radio access mode, and one or more different systems such as GSM bands or possibly other radio systems such as IMT-2000 family members.
+- 3.175 multicast service:** A unidirectional PTM service in which a message is transmitted from a single source entity to all subscribers currently located within a geographical area. The message contains a group identifier indicating whether the message is of interest to all subscribers or to only the subset of subscribers belonging to a specific multicast group.
+- 3.176 multipoint:** A value of the service attribute "communication configuration", which denotes that the communication involves more than two network terminations (source: [ITU-T I.113]).
+- 3.177 multimedia service:** Services that handle several types of media such as audio and video in a synchronized way from the user's point of view. A multimedia service may involve multiple parties, multiple connections, and the addition or deletion of resources and users within a single communication session.
+- 3.178 name:** A name is an alphanumeric label used for identification of end users and may be portable.
+- 3.179 negotiated QoS:** In response to a QoS request, the network shall negotiate each QoS attribute to a level that is in accordance with the available network resources. After QoS negotiation, the bearer network shall always attempt to provide adequate resources to support all of the negotiated QoS profiles.
+- 3.180 network code:** MCC and MNC.
+- 3.181 network code group:** Same as "network code".
+- 3.182 network connection:** An association established by a network layer between two users for the transfer of data, which provides explicit identification of a set of network data transmissions and agreement concerning the services to be provided by the set (source: Rec. [ITU-T X.213] ISO/IEC 8348]).
+- 3.183 network element:** A discrete telecommunications entity, which can be managed over a specific interface, e.g., the RNC.
+- 3.184 network manager:** Provides a package of end-user functions with the responsibility for the management of a network, mainly as supported by the EM(s) but it may also involve direct access to the network elements. All communication with the network is based on open and well-standardized interfaces supporting management of multi-vendor and multi-technology network elements.
+
+- 3.185 network operator:** See "PLMN operator".
+- 3.186 network personalization:** Allows the network operator to personalize a ME so that it can only be used with that particular network operator's (U)SIMs.
+- 3.187 network resource model:** A protocol-independent model describing managed objects representing network resources, e.g., an RNC or Node B.
+- 3.188 network service data unit (NSDU):** A unit of data passed between the user and the GPRS network across a network service access point (NSAP).
+- 3.189 network subset code:** Digits 6 and 7 of the IMSI.
+- 3.190 network subset personalization:** A refinement of network personalization, which allows network operators to limit the usage of a ME to a subset of (U)SIMs.
+- 3.191 network termination:** A functional group on the network side of a user-network interface (source: [ITU-T I.112]).
+- 3.192 nomadic operating mode:** Mode of operation where the terminal is transportable but being operated while stationary and may in addition require user cooperation (e.g., close to open spaces, antenna set-up, etc.).
+- 3.193 nominal maximum output power:** This is the nominal power defined by the UE power class.
+- 3.194 non-access stratum:** Protocols between UE and the core network that are not terminated in the UTRAN.
+- 3.195 normal GSM operation:** Relating to general, CHV-related, GSM security-related and subscription-related procedures.
+- 3.196 normal mode of operation:** The mode of operation into which the ME would have gone if it had no personalization checks to process.
+- 3.197 narrow TDD (NTDD):** The 1.28 Mcps chip rate UTRA-TDD option.
+- 3.198 number:** A string of decimal digits that uniquely indicates the public network termination point. The number contains the information necessary to route the call to this termination point.
+- A number can be in a format determined nationally or in an international format. The international format is known as the international public telecommunication number which includes the country code and subsequent digits, but not the international prefix.
+- 3.199 number portability:** Where the provision of dialable numbers is independent of home environment and/or serving network.
+- 3.200 off-line charging:** A charging process where charging information does not affect, in real time, the service rendered.
+- 3.201 on-line charging:** A charging process where charging information can affect, in real time, the service rendered and therefore directly interacts with the session/service control.
+- 3.202 one stop billing:** One bill for all charges incurred using the 3GPP System.
+- 3.203 open group:** A group that does not have a pre-defined set of members. Any user may participate in an open group.
+- 3.204 open service access:** Concept for introducing a vendor independent means for introduction of new services.
+- 3.205 open service architecture:** Concept for introducing a vendor-independent means for introduction of new services.
+
+- 3.206 operations system:** This term indicates a generic management system, independent of its location level within the management hierarchy.
+- 3.207 OSA interface:** Standardized interface used by application/clients to access service capability features.
+- 3.208 packet:** An information unit identified by a label at layer 3 of the OSI reference model (source: [ITU-T I.113]). A network protocol data unit (NPDU).
+- 3.209 packet data protocol (PDP):** Any protocol, which transmits data as discrete units known as packets, e.g., IP, or [ITU-T X.25].
+- 3.210 packet transfer mode:** Also known as "packet mode". A transfer mode in which the transmission and switching functions are achieved by packet-oriented techniques, so as to dynamically share network transmission and switching resources between a multiplicity of connections (source: [ITU-T I.113]).
+- 3.211 padding:** One or more bits appended to a message in order to cause the message to contain the required number of bits or bytes.
+- 3.212 paging:** The act of seeking a user equipment.
+- 3.213 paging occasion:** The frame where the UE monitors in FDD or the paging block, which consists of several frames, for TDD. For paging blocks, the value of paging occasion is equal to the first frame of the paging block.
+- 3.214 peak bit rate:** A measure of throughput. The maximum bit rate offered to the user for a given time period (to be defined) for the transfer of a bursty signal (source: [ITU-T I.210]). (The maximum user information transfer rate achievable by a user for a single service data unit transfer.)
+- 3.215 performance:** The ability to track service and resource usage levels and to provide feedback on the responsiveness and reliability of the network.
+- 3.216 personal service environment:** Contains personalized information defining how subscribed services are provided and presented towards the user. Each subscriber of the home environment has her own personal service environment. The personal service environment is defined in terms of one or more user profiles.
+- 3.217 personalization:** The process of storing information in the ME and activating the procedures, which verify this information against the corresponding information stored in the SIM whenever the ME is powered up or a SIM is inserted, in order to limit the SIMs with which the ME will operate.
+- 3.218 personalization entity:** Network, network subset, SP, Corporate or (U)SIM to which the ME is personalized.
+- 3.219 phonebook:** A dataset of personal or entity attributes. The simplest form is a set of name-subscriber phone number pairs as supported by GSM (U)SIMs.
+- 3.220 physical channel data stream:** In the uplink, a data stream that is transmitted on one physical channel. In the downlink, a data stream that is transmitted on one physical channel in each cell of the active set.
+- 3.221 physical channel:** In FDD mode, a physical channel is defined by code, frequency and, in the uplink, relative phase (I/Q). In TDD mode, a physical channel is defined by code, frequency, and time-slot.
+- 3.222 pico cells:** "Pico cells" are cells, mainly indoor cells, with a radius typically less than 50 metres.
+- 3.223 PICH monitoring occasion:** The time instance where the UE monitors PICH within paging occasion.
+
+**3.224 PLMN area:** The geographical area in which a PLMN provides communication services according to the specifications to mobile users. In the PLMN area, the mobile user can set up calls to a user of a terminating network. The terminating network may be a fixed network, the same PLMN, another PLMN or other types of PLMN. Terminating network users can also set up calls to the PLMN. The PLMN area is allocated to a PLMN. It is determined by the service and network provider in accordance with any provisions laid down under national law. In general, the PLMN area is restricted to one country. It can also be determined differently, depending on the different telecommunication services, or type of MS. If there are several PLMNs in one country, their PLMN areas may overlap. In border areas, the PLMN areas of different countries may overlap. Administrations will have to take precautions to ensure that cross border coverage is minimized in adjacent countries unless otherwise agreed.
+
+**3.225 public land mobile network operator (PLMN operator):** The entity which offers telecommunications services over an air interface.
+
+**3.226 point-to-multipoint service:** A service type in which data is sent to "all service subscribers or a predefined subset of all subscribers" within an area defined by the service requester.
+
+**3.227 point-to-point:** A value of the service attribute "communication configuration", which denotes that the communication involves only two network terminations.
+
+**3.228 point-to-point service:** A service type in which data is sent from a single network termination to another network termination.
+
+**3.229 port:** A particular interface, of the specified equipment (apparatus), with the electromagnetic environment. For example, any connection point on equipment intended for connection of cables to or from that equipment is considered as a port.
+
+**3.230 ported number:** A MSISDN that has undergone the porting process.
+
+**3.231 ported subscriber:** The subscriber of a ported number.
+
+**3.232 porting process:** A description of the transfer of a number between network operators.
+
+**3.233 power control dynamic range:** The difference between the maximum and the minimum total transmit output power for a specified reference condition (TS 25.104).
+
+**3.234 predictive service:** A service model which provides reliable performance, but allowing a specified variance in the measured performance criteria.
+
+**3.235 prepay billing:** Billing arrangement between customer and operator/service provider where the customer deposits an amount of money in advance, which is subsequently used to pay for service usage.
+
+**3.236 postpay billing:** Billing arrangement between customer and operator/service provider where the customer periodically receives a bill for service usage in the past period.
+
+**3.237 proactive SIM:** A SIM which is capable of issuing commands to the terminal. Part of SIM application toolkit.
+
+**3.238 protocol:** A formal set of procedures that are adopted to ensure communication between two or more functions within the same layer of a hierarchy of functions (source: [ITU-T I.112]).
+
+**3.239 public land mobile network:** A telecommunications network providing mobile cellular services.
+
+**3.240 QoS profile:** A QoS profile comprises a number of QoS parameters. A QoS profile is associated with each QoS session. The QoS profile defines the performance expectations placed on the bearer network.
+
+**3.241 QoS session:** Lifetime of PDP context. The period between the opening and closing of a network connection whose characteristics are defined by a QoS profile. Multiple QoS sessions may exist, each with a different QoS profile.
+
+**3.242 quality of service:** The collective effect of service performances, which determine the degree of satisfaction of a user of a service. It is characterized by the combined aspects of performance factors applicable to all services, such as:
+
+- service operability performance;
+- service accessibility performance;
+- service retainability performance;
+- service integrity performance; and
+- other factors specific to each service.
+
+**3.243 radio access bearer:** The service that the access stratum provides to the non-access stratum for transfer of user data between user equipment and CN.
+
+**3.244 radio access mode:** Mode of the cell, FDD or TDD.
+
+**3.245 RAN sharing:** Two or more CN operators share the same RAN, i.e., a RAN node (RNC or BSC) is connected to multiple CN nodes (SGSNs and MSC/VLRs) belonging to different CN operators.
+
+**3.246 radio access network application part:** Radio network signalling over the Iu.
+
+**3.247 radio access network operator:** Operator that offers radio access to one or more core network operators.
+
+**3.248 radio access network technology:** UTRAN, GERAN, etc.
+
+**3.249 radio interface:** The "radio interface" is the tether less interface between user equipment and a UTRAN access point. This term encompasses all the functionality required to maintain such interfaces.
+
+**3.250 radio link:** A "radio link" is a logical association between single user equipment and a single UTRAN access point. Its physical realization comprises one or more radio bearer transmissions.
+
+**3.251 radio link control:** A sublayer of radio interface layer 2 providing transparent, unacknowledged and acknowledged data transfer service.
+
+**3.252 radio network controller:** This equipment in the RNS is in charge of controlling the use and the integrity of the radio resources.
+
+**3.253 radio network subsystem:** Either a full network or only the access part of a UTRAN offering the allocation and the release of specific radio resources to establish means of connection in between an UE and the UTRAN. A radio network subsystem is responsible for the resources and transmission/reception in a set of cells.
+
+**3.254 radio system:** The selected 2nd or 3rd generation radio access technology.
+
+**3.255 real time:** Time, typically in number of seconds, to perform the online mechanism used for fraud control and cost control.
+
+**3.256 received signal code power:** Given only signal power is received, the average power of the received signal after despreading and combining.
+
+**3.257 receiver antenna gain (dBi):** The maximum gain of the receiver antenna in the horizontal plane (specified as dB relative to an isotropic radiator).
+
+- 3.258 receiver noise figure (dB):** The noise figure of the receiving system referenced to the receiver input.
+- 3.259 receiver sensitivity (dBm):** This is the signal level needed at the receiver input that just satisfies the required $E_b/(N_0+I_0)$ .
+- 3.260 recipient network:** The network which receives the number in the porting process. This network becomes the subscription network when the porting process is complete.
+- 3.261 record:** A string of bytes within an EF handled as a single entity.
+- 3.262 record number:** The number which identifies a record within an EF.
+- 3.263 record pointer:** The pointer which addresses one record in an EF.
+- 3.264 reference configuration:** A combination of functional groups and reference points that shows possible network arrangements (source: [ITU-T I.112]).
+- 3.265 reference point:** A conceptual point at the conjunction of two non-overlapping functional groups (source: [ITU-T I.112]).
+- 3.266 regionally provided service:** A service entitlement to only certain geographical part(s) of a PLMN, as controlled by the network operator.
+- 3.267 registration:** This is the process of camping on a cell of the PLMN and doing any necessary LRs.
+- 3.268 registered PLMN (RPLMN):** This is the PLMN on which the UE has performed a location registration successfully.
+- 3.269 registration area:** A (NAS) registration area is an area in which the UE may roam without a need to perform location registration, which is a NAS procedure.
+- 3.270 relay:** Terminal devices capable of ODMA relay communications.
+- 3.271 relay/seed gateway:** Relay or seed that communicates with the UTRAN, in either TDD or FDD mode.
+- 3.272 relaylink:** Relaylink is a communications link between two ODMA relay nodes.
+- 3.273 release 99:** A particular version of the 3G system standards produced by the 3GPP project. Also: Release 4, Release 5, Release 6, Release 7, Release 8, Release 9, Release 10, etc.
+- 3.274 repeater:** A radio transceiver used to extend the transmission of a base station beyond its normal range.
+- 3.275 requested QoS:** A QoS profile is requested at the beginning of a QoS session. QoS modification requests are also possible during the lifetime of a QoS session.
+- 3.276 required $E_b/(N_0+I_0)$ (dB):** The ratio between the received energy per information bit to the total effective noise and interference power density needed to satisfy the quality objectives.
+- 3.277 residual error rate:** A parameter describing service accuracy. The frequency of lost SDUs and of corrupted or duplicated network SDUs delivered at the user-network interface.
+- 3.278 retrieval service:** An interactive service which provides the capability of accessing information stored in database centres. The information will be sent to the user on demand only. The information is retrieved on an individual basis, i.e., the time at which an information sequence is to start is under the control of the user (source [ITU-T I.113]).
+- 3.279 roaming:** The ability for a user to function in a serving network different from the home network.
+- 3.280 root relay:** ODMA relay node where communications originate or terminate.
+
+- 3.281 RRC connection:** A point-to-point bidirectional connection between RRC peer entities on the UE and the UTRAN sides, respectively. An UE has either zero or one RRC connection.
+- 3.282 SDU error probability:** The ratio of total incorrect service data units (SDUs) to total successfully transferred service data units plus incorrect service data units in a specified sample (source: [ITU-T X.140]).
+- NOTE – The source document term “user information unit” has been replaced by the term “service data unit”.
+- 3.283 SDU loss probability:** The ratio of total lost service data units (SDUs) to total transmitted service data units in a specified sample (source: [ITU-T X.140]).
+- NOTE – The source document term "user information unit" has been replaced by the term "service data unit".
+- 3.284 SDU misdelivery probability:** The ratio of total misdelivered service data units (SDUs) to total service data units transferred between a specified source and destination user in a specified sample (source:[ITU-T X.140]).
+- NOTE – The source document term "user information unit" has been replaced by the term "service data unit".
+- 3.285 SDU transfer delay:** The value of elapsed time between the start of transfer and successful transfer of a specified service data unit (SDU) (source: [ITU-T X.140]).
+- NOTE – The source document term "user information unit" has been replaced by the term "service data unit".
+- 3.286 SDU transfer rate:** The total number of successfully transferred service data units (SDUs) in a transfer sample divided by the input/output time for that sample. The input/output time is the larger of the input time or the output time for the sample (source: [ITU-T X.140]).
+- NOTE – The source document term "user information unit" has been replaced by the term "service data unit".
+- 3.287 seamless handover:** A handover without perceptible interruption of the radio connection.
+- 3.288 sector:** A sub-area of a cell. All sectors within one cell are served by the same base station. A radio link within a sector can be identified by a single logical identification belonging to that sector.
+- 3.289 secured packet:** The information flow on top of which the level of required security has been applied. An application message is transformed with respect to a chosen transport layer and chosen level of security into one or more secured packets.
+- 3.290 security:** The ability to prevent fraud as well as the protection of information availability, integrity and confidentiality.
+- 3.291 seed:** Deployed ODMA relay node with or without a display/keypad.
+- 3.292 selected IT traffic offload:** Offload of selected types of IP traffic (e.g., internet traffic) towards a defined IP network close to the UE's point of attachment to the access network. Selected IP traffic offload (SIPTO) is applicable to traffic offload for the macro-cellular access network and for the H(e)NB subsystem.
+- 3.293 selected PLMN:** This is the PLMN that has been selected by the non-access stratum, either manually or automatically.
+- 3.294 service:** A component of the portfolio of choices offered by service providers to a user, a functionality offered to a user.
+- 3.295 service-less UE:** A UE that has only the Baseline capabilities.
+
+**3.296 service access point:** A conceptual point where a protocol layer offers access to its services to upper layer.
+
+**3.297 service area:** The service area is defined in the same way as the service area according to [ITU-T Q.1001]. In contrast to the PLMN area, it is not based on the coverage of a PLMN. Instead, it is based on the area in which a fixed network user can call a mobile user without knowing his location. The service area can therefore change when the signalling system is being extended, for example.
+
+**3.298 service attributes:** A specified characteristic of a telecommunication service ([ITU-T I.112]).
+
+NOTE – the value(s) assigned to one or more service attributes may be used to distinguish that telecommunications service from others.
+
+**3.299 service bit rate:** The bit rate that is available to a user for the transfer of user information ([ITU-T I.113]).
+
+**3.300 service capabilities:** Bearers defined by parameters, and/or mechanisms needed to realize services. These are within networks and under network control.
+
+**3.301 service capability feature:** Functionality offered by service capabilities that are accessible via the standardized application interface.
+
+**3.302 service capability server:** Network functionality providing open interfaces towards the functionality offered by 3G System service capabilities.
+
+**3.303 service category or service class:** A service offered to the users described by a set of performance parameters and their specified values, limits or ranges. The set of parameters provides a comprehensive description of the service capability.
+
+**3.304 service continuity:** The uninterrupted user experience of a service that is using an active communication (e.g., an ongoing voice call) when a UE undergoes a radio access technology change or a CS/PS domain change without, as far as possible, the user noticing the change.
+
+NOTE – In particular service continuity encompasses the possibility that after a RAT/domain change the user experience is maintained by a different telecommunication service (e.g., tele- or bearer service) than before the RAT/domain change.
+
+**3.305 service control:** The ability of the user, home environment or serving environment to determine what a particular service does, for a specific invocation of that service, within the limitations of that service.
+
+**3.306 service delay:** The time elapsed from the invocation of the service request, to the corresponding service request indication at the Service Receiver, indicating the arrival of application data.
+
+**3.307 service enabler:** A capability which may be used, either by itself or in conjunction with other service enablers, to provide a service to the end user.
+
+**3.308 service execution environment:** A capability which may be used, either by itself or in conjunction with other service enablers, to provide a service to the end user.
+
+**3.309 service feature:** A capability which may be used, either by itself or in conjunction with other service enablers, to provide a service to the end user.
+
+**3.310 service implementation capabilities:** A capability which may be used, either by itself or in conjunction with other service enablers, to provide a service to the end user.
+
+**3.311 service model:** A capability which may be used, either by itself or in conjunction with other service enablers, to provide a service to the end user.
+
+- 3.312 service provider:** A capability which may be used, either by itself or in conjunction with other service enablers, to provide a service to the end user.
+- 3.313 service receiver:** A capability which may be used, either by itself or in conjunction with other service enablers, to provide a service to the end user.
+- 3.314 service relationship:** A capability which may be used, either by itself or in conjunction with other service enablers, to provide a service to the end user.
+- 3.315 service request:** This is defined as being one invocation of the service through a service request primitive.
+- 3.316 service requester:** The entity which requests the initiation of a GPRS operation, through a service request.
+- 3.317 service subscriber:** The entity which subscribes to the general packet radio service (GPRS) service.
+- 3.318 services (of a mobile cellular system):** The set of functions that the mobile cellular system can make available to the user.
+- 3.319 serving network:** The serving network provides the user with access to the services of home environment.
+- 3.320 settlement:** Payment of amounts resulting from the accounting process.
+- 3.321 shared network:** When two or more network operators share network elements.
+- 3.322 signalling:** The exchange of information specifically concerned with the establishment and control of connections, and with management, in a telecommunications network.
+- 3.323 signalling connection:** An acknowledged-mode link between the user equipment and the core network to transfer higher layer information between the entities in the non-access stratum.
+- 3.324 signalling link:** Provides an acknowledged-mode link layer to transfer the UE-UTRAN signalling messages as well as UE-Core Network signalling messages (using the signalling connection).
+- 3.325 (U)SIM personalization:** Enables a user to personalize a ME so that it may only be used with particular (U)SIM(s).
+- 3.326 soft handover:** A performance criterion that describes the time interval required to perform a function or the rate at which the function is performed. (The function may or may not be performed with the desired accuracy.) (source: ITU-T I.350).
+- 3.327 speed:** A performance criterion that describes the time interval required to perform a function or the rate at which the function is performed. (The function may or may not be performed with the desired accuracy.) (source: ITU-T I.350).
+- 3.328 SRNC radio network temporary identifier (S-RNTI):** A UE identifier which is allocated by the serving RNC and unique within this serving radio network controller (SRNC). It is allocated for all UEs having a RRC connection. S-RNTI is reallocated always when the serving RNC for the RRC connection is changed and deallocated when the RRC connection is released.
+- 3.329 SRNS relocation:** The change of Iu instance and transfer of the serving RNS (SRNS) role to another RNS.
+- 3.330 stratum:** Grouping of protocols related to one aspect of the services provided by one or several domains.
+- 3.331 sub-network management functions:** Set of functions that are related to a network model for a set of network elements constituting a clearly defined sub-network, which may include relations between the network elements. This model enables additional functions on the
+
+sub-network level (typically in the areas of network topology presentation, alarm correlation, service impact analysis and circuit provisioning).
+
+**3.332 subscribed QoS:** The network will not grant a QoS greater than the subscribed QoS. The QoS profile subscription parameters are held in the HLR. An end user may have several QoS subscriptions. For security and the prevention of damage to the network, the end user cannot directly modify the QoS subscription profile data.
+
+**3.333 subscriber:** An entity (associated with one or more users) that is engaged in a subscription with a service provider. The subscriber is allowed to subscribe and unsubscribe services, to register a user or a list of users authorized to enjoy these services, and also to set the limits relative to the use that associated users make of these services.
+
+**3.334 subscription:** A subscription describes the commercial relationship between the subscriber and the service provider.
+
+**3.335 subscription management (SuM):** Set of capabilities that allow operators, service providers, and indirectly subscribers, to provision, control, monitor the subscription profile.
+
+**3.336 suitable cell:** This is a cell on which an UE may camp. It must satisfy certain conditions.
+
+**3.337 supplementary service:** A service which modifies or supplements a basic telecommunication service. Consequently, it cannot be offered to a user as a stand-alone service. It must be offered together with or in association with a basic telecommunication service. The same supplementary service may be common to a number of basic telecommunication services.
+
+**3.338 system area:** The group of PLMN areas accessible by MSs. Interworking of several PLMNs and interworking between PLMNs and fixed network(s) permit public land mobile communication services at international level.
+
+**3.339 telecommunication service:** What is offered by a PLMN operator or service provider to its customers in order to satisfy a specific telecommunication requirement. (source: [ITU-T I.112]). Telecommunication services are divided into two broad families: bearer services and teleservices (source: [ITU-T I.210]).
+
+**3.340 teleservice:** A type of telecommunication service that provides the complete capability, including terminal equipment functions, for communication between users according to standardized protocols and transmission capabilities established by agreement between operators.
+
+**3.341 text conversation:** Real-time transfer of text between users in at least two locations.
+
+**3.342 text telephony:** An audiovisual conversation service providing bidirectional real-time transfer of text and optionally audio between users in two locations. Audio may be transmitted alternating with text or simultaneously with text (source: [ITU-T F.703]).
+
+**3.343 throughput:** A parameter describing service speed. The number of data bits successfully transferred in one direction between specified reference points per unit time (source: [ITU-T I.113]).
+
+**3.344 toolkit applet:** An application on the UICC that generates proactive commands to the ME.
+
+**3.345 total conversation:** An audiovisual conversation service providing bidirectional symmetric real-time transfer of motion video, text and voice between users in two or more locations (source: [ITU-T F.703]).
+
+**3.346 total power dynamic range:** The difference between the maximum and the minimum total transmit output power for a specified reference condition (TS 25.104).
+
+**3.347 traffic channel:** A logical channel, which carries user information.
+
+**3.348 transit delay:** A parameter describing service speed. The time difference between the instant at which the first bit of a protocol data unit (PDU) crosses one designated boundary
+
+(reference point), and the instant at which the last bit of the PDU crosses a second designated boundary (source: [ITU-T I.113]).
+
+**3.349 transmission time interval:** The inter-arrival time of transport block sets, i.e., the time it shall take to transmit a transport block set.
+
+**3.350 transmitter antenna gain (dBi):** The maximum gain of the transmitter antenna in the horizontal plane (specified as dB relative to an isotropic radiator).
+
+**3.351 transport block:** The basic data unit exchanged between L1 and MAC. An equivalent term for transport block is "MAC PDU".
+
+**3.352 transport block set:** A set of transport blocks that is exchanged between L1 and MAC at the same time instance using the same transport channel. An equivalent term for transport block set is "MAC PDU Set".
+
+**3.353 transport block set size:** The number of bits in a transport block set.
+
+**3.354 transport block size:** The size (number of bits) of a transport block.
+
+**3.355 transport channel:** The channels offered by the physical layer to Layer 2 for data transport between peer L1 entities are denoted as transport channels. Different types of transport channels are defined by how and with which characteristics data is transferred on the physical layer, e.g., whether using dedicated or common physical channels.
+
+**3.356 transport format:** A format offered by L1 to MAC for the delivery of a transport block set during a transmission time interval on a transport channel. The transport format constitutes of two parts – one dynamic part and one semi-static part.
+
+**3.357 transport format combination:** The combination of currently valid transport formats on all transport channels of an UE, i.e., containing one transport format from each transport channel.
+
+**3.358 transport format combination set:** A set of transport format combinations to be used by a UE.
+
+**3.359 transport format combination indicator (TFCI):** A representation of the current transport format combination.
+
+**3.360 transport format identification (TFI in UTRAN, TFIN in GERAN):** A label for a specific transport format within a transport format set.
+
+**3.361 transport format set:** A set of transport formats. For example, a variable rate DCH has a transport format set (one transport format for each rate), whereas a fixed rate DCH has a single transport format.
+
+**3.362 UE service capabilities:** Capabilities that can be used either singly or in combination to deliver services to the user. The characteristic of UE service capabilities is that their logical function can be defined in a way that is independent of the implementation of the 3GPP system (although all UE service capabilities are of course constrained by the implementation of the 3GPP system). Examples: a data bearer of 144 kbit/s; a high-quality speech teleservice; an IP teleservice; a capability to forward a speech call.
+
+**3.363 universal IC card (UICC):** A physically secure device, an IC card (or 'smart card'), that can be inserted and removed from the terminal equipment. It may contain one or more applications. One of the applications may be a USIM.
+
+**3.364 universal subscriber identity module (USIM):** An application residing on the UICC used for accessing services provided by mobile networks, which the application is able to register on with the appropriate security.
+
+- 3.365 uplink:** A unidirectional radio link for the transmission of signals from a UE to a base station, from a mobile station to a mobile base station or from a mobile base station to a base station.
+- 3.366 URA updating:** A family of procedures that updates the UTRAN registration area of a UE when a RRC connection exists and the position of the UE is known on URA level in the UTRAN.
+- 3.367 user:** An entity, not part of the 3G system, which uses 3G system services. Example: a person using a 3G system mobile station as a portable telephone.
+- 3.368 user access or user network access:** The means by which a user is connected to a telecommunication network in order to use the services and/or facilities of that network (source: [ITU-T I.112]).
+- 3.369 user equipment:** A device allowing a user access to network services. For the purpose of 3G specifications, the interface between the UE and the network is the radio interface. A user equipment can be subdivided into a number of domains, the domains being separated by reference points. Currently defined domains are the USIM and ME Domains. The ME Domain can further be subdivided into several components showing the connectivity between multiple functional groups. These groups can be implemented in one or more hardware devices. An example of such a connectivity is the TE-MT interface. Further, an occurrence of a user equipment is a MS for GSM.
+- 3.370 UTRA radio access mode:** The selected UTRA radio access mode, i.e., UTRA-FDD; UTRA-TDD.
+- 3.371 UTRA-TDD:** Time division duplex UTRA radio access mode.
+- 3.372 UTRA-WTDD:** Time division duplex UTRA access mode 3.84 Mcps option.
+- 3.373 UTRAN access point:** A conceptual point within the UTRAN performing radio transmission and reception. A UTRAN access point is associated with one specific cell, i.e., there exists one UTRAN access point for each cell. It is the UTRAN-side endpoint of a radio link.
+- 3.374 UTRAN registration area:** An area covered by a number of cells. The URA is only internally known in the UTRAN.
+- 3.375 UTRAN radio network temporary identifier:** The U-RNTI is a unique UE identifier that consists of two parts, a SRNC identifier and a C-RNTI. U-RNTI is allocated to a UE having a RRC connection. It identifies the UE within UTRAN and is used as a UE identifier in cell update, URA update, RRC connection reestablishment and (UTRAN originated) paging messages and associated responses on the radio interface.
+- 3.376 user profile:** The set of information necessary to provide a user with a consistent, personalized service environment, irrespective of the user's location or the terminal used (within the limitations of the terminal and the serving network).
+- 3.377 Uu:** The Radio interface between UTRAN and the user equipment.
+- 3.378 value-added service provider:** Provides services other than basic telecommunications service for which additional charges may be incurred.
+- 3.379 variable bit rate service:** A type of telecommunication service characterized by a service bit rate specified by statistically expressed parameters which allow the bit rate to vary within defined limits (source: [ITU-T I.113]).
+- 3.380 virtual home environment:** A concept for personal service environment portability across network boundaries and between terminals.
+- 3.381 virtual machine:** A software program that simulates a hypothetical computer central processing unit. The programs executed by a virtual machine are represented as byte codes, which are primitive operations for this hypothetical computer.
+
+**3.382 visited PLMN of home country:** This is a PLMN, different from the home PLMN, where the MCC part of the PLMN identity is the same as the MCC of the IMSI.
+
+**3.383 wide TDD (WTDD):** The 3.84 Mcps chip rate UTRA-TDD option.
+
+**3.384 WLAN user equipment (WLAN UE):** A UE (equipped with UICC card including (U)SIM) utilized by a subscriber capable of accessing a WLAN network. A WLAN UE may include entities whose configuration, operation and software environment are not under the exclusive control of the 3GPP system operator, such as a laptop computer or PDA with a WLAN card, UICC card reader and suitable software applications.
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|--------|---------------------------------------------------------------------------------|
+| 2G | Second Generation |
+| 3G | Third Generation |
+| 3GMS | Third Generation Mobile Communication System |
+| 3GPP | Third Generation Partnership Project |
+| AC | Access Class, Access Condition, Application Context |
+| ACELP | Algebraic Code-Excited Linear Prediction |
+| AES | Advanced Encryption Standard |
+| AF | Application Function |
+| AGW | Access Gateway |
+| AID | Application Identifier |
+| AIM | Application Information Model |
+| AKA | Authentication and Key Agreement |
+| ALG | Application Level Gateway |
+| AMR | Adaptive Multi Rate (also appears as "Adaptive Multi-Rate") |
+| AMR-WB | Adaptive Multi Rate WideBand |
+| ANDSF | Access Network Discovery and Selection Function |
+| ANP | Access Network Provider |
+| AoC | Advice of Charge |
+| AoCC | Advice of Charge Charging (also appears as "Advice of Charge (Charging)") |
+| AoCI | Advice of Charge Information (also appears as "Advice of Charge (Information)") |
+| API | Application Programming Interface |
+| AS | Application Server |
+| ASE | Application Service Element |
+| ATM | Asynchronous Transfer Mode |
+| AuC | Authentication Centre |
+| BER | Bit Error Rate; Basic Encoding Rules (of ASN.1) |
+| BGCF | Breakout Gateway Control Function |
+
+| | |
+|---------|-----------------------------------------------------------------------------------------------|
+| BICC | Bearer Independent Call Control |
+| BS | Base Station |
+| BS | Bearer Service |
+| BSC | Base Station Controller |
+| BSS | Base Station Subsystem |
+| BSSMAP | Base Station Subsystem Management Application Part |
+| BTS | Base Transceiver Station |
+| CAI | Charge Advise Information |
+| CAMEL | Customized Applications for Mobile network Enhanced Logic |
+| CAP | CAMEL Application Part |
+| CB | Call Barring |
+| CBC | Cell Broadcast Centre |
+| CBIM | Common Baseline Information Model |
+| CBS | Cell Broadcast Service |
+| CC | Call Control |
+| CCBS | Completion of Calls to Busy Subscriber (also appears as "Call Completion to Busy Subscriber") |
+| CD | Call Deflection |
+| CDR | Charging Data Record |
+| CM | Configuration Management |
+| CMIP | Common Management Information Protocol |
+| CN | Core Network |
+| CORBA | Common Object Request Broker Architecture |
+| CS | Circuit Switched |
+| CSCF | Call Session Control Function |
+| CSFB | CS Fallback |
+| CSG | Closed Subscriber Group |
+| CS-MGW | Circuit Switched Media GateWay |
+| CSS | CSG Subscriber Server |
+| CTM | Cellular Text telephone Modem |
+| CUG | Closed User Group |
+| DCE | Data Circuit-terminating Equipment |
+| DIMS | Dynamic and Interactive Multimedia Scenes |
+| DSMIPv6 | Dual Stack Mobile IPv6 |
+| DTE | Data Terminal Equipment |
+| DTMF | Dual Tone Multiple Frequency |
+| DTX | Discontinuous Transmission |
+
+| | |
+|---------|----------------------------------------------------------|
+| EDGE | Enhanced Data rates for GSM Evolution |
+| EF | Elementary File |
+| EFR | Enhanced Full Rate |
+| EIR | Equipment Identity Register |
+| EM | Element Manager |
+| eMPS | enhanced Multimedia Priority Service |
+| EP | Elementary Procedure |
+| EP | Entry Point |
+| EPC | Evolved Packet Core |
+| EPS | Evolved Packet System |
+| E-UTRAN | Evolved Universal Terrestrial Radio Access Network |
+| FDD | Frequency Division Duplex |
+| FM | Fault Management |
+| GERAN | GSM/EDGE Radio Access Network |
+| GGSN | Gateway GPRS Support Node |
+| GLR | Gateway Location Register |
+| GMLC | Gateway Mobile Location Centre |
+| GMSC | Gateway Mobile Switching Centre |
+| GPL | Generic Push Layer |
+| GPRS | General Packet Radio Service |
+| gprsSSF | GPRS Service Switching Function |
+| GPS | Global Positioning System |
+| GSM | Global System for Mobile communications |
+| GSME | GSM Europe |
+| GSM-EFR | GSM Enhanced Full Rate speech Codec |
+| gsmSCF | GSM Service Control Function |
+| GSN | GPRS Support Nodes |
+| GT | Global Title |
+| GTP | Evolved General Packet Radio Service Tunnelling Protocol |
+| GTT | Global Text Telephony |
+| GUP | 3GPP Generic User Profile |
+| HA | Home Agent |
+| HE | Home Environment |
+| HeNB | Home enhanced Node B |
+| HeNS | Home enhanced Node B Subsystem |
+| HLR | Home Location Register |
+| HNB | Home Node B |
+
+| | |
+|--------|----------------------------------------------------------------------------------------------------|
+| HNS | Home Node B Subsystem |
+| HPLMN | Home Public Land Mobile Network |
+| HRPD | High Rate Packet Data |
+| IC | Integrated Circuit (also appears as "Integrated Circuits") |
+| ICC | Integrated Circuit Card |
+| ICS | IMS Centralized Services |
+| IDL | Interface Definition Language |
+| IKE | Internet Key Exchange |
+| IM | IP Multimedia |
+| IMEI | International Mobile Equipment Identity |
+| IM-MGW | Intermediate Media GateWay |
+| IMS | IP Multimedia Subsystem |
+| IMSI | International Mobile Subscriber Identity (also appears as "International Mobile Station Identity") |
+| IP | Internet Protocol |
+| IP-CAN | IP-Connectivity Access Network |
+| IrDA | Infrared Data Association |
+| IRP | Integration Reference Point |
+| IS | Information Service |
+| ISDN | Integrated Services Digital Network |
+| ISUP | ISDN User Part |
+| Itf-N | Interface N |
+| IWF | InterWorking Function |
+| I-WLAN | Interworking WLAN |
+| LAN | Local Area Network |
+| LCS | Location Services |
+| LMSI | Local Mobile Station Identity |
+| LMU | Location Measurement Unit |
+| LR | Location Registration |
+| MAC | Media Access Control |
+| MAC | Message Authentication Code |
+| MAP | Mobile Application Part |
+| MBMS | Multimedia Broadcast/Multicast Service |
+| MC | Multicall |
+| ME | Mobile Equipment |
+| MExE | Mobile station application Execution Environment, aka Mobile Execution Environment |
+
+| | |
+|--------|-----------------------------------------------------------------------------------------------|
+| MGC | Media Gateway Controller |
+| MGCF | Media Gateway Control Function |
+| MGW | Media GateWay |
+| MIM | Management Information Model |
+| MLC | Mobile Location Centre |
+| MM | Mobility Management |
+| MME | Mobility Management Entity |
+| MMI | Man-Machine Interface |
+| MMS | Multimedia Messaging Service |
+| MNP | Mobile Number Portability |
+| MO | Mobile Originated |
+| MOBIKE | IKEv2 Mobility and Multihoming Protocol |
+| MR | Multi Rate
Media Resource |
+| MRFC | Multimedia Resource Function Controller |
+| MRFP | Multimedia Resource Function Processor |
+| MS | Mobile Station |
+| MSC | Mobile Switching Centre (also appears as "Mobile-services Switching Centre") |
+| MSG | (ETSI TC) Mobile Standards Group |
+| MSISDN | Mobile Subscriber ISDN number (also appears as "Mobile Station International ISDN Number(s)") |
+| MSP | Multiple Subscriber Profile |
+| MSRN | Mobile Station Roaming Number |
+| MT | Mobile Terminal |
+| MT | Mobile Termination |
+| MTP | Message Transfer Part |
+| NE | Network Element |
+| NITZ | Network Identity and Time Zone |
+| NNSF | NAS Node Selection Function |
+| NM | Network Manager |
+| NRM | Network Resource Model |
+| NSS | Network Subsystem |
+| NW | Network |
+| OACSU | Off-Air Call Set-Up |
+| OAM&P | Operations, Administration, Maintenance and Provisioning |
+| ODB | Operator Determined Barring |
+| ODMA | Opportunity Driven Multiple Access |
+
+| | |
+|-------------|----------------------------------------------|
+| OMA | Open Mobile Alliance |
+| OoBTC | Out of Band Transcoder Control |
+| OP | OPerator |
+| OS | Operations System |
+| OSA | Open Service Architecture |
+| OSI | Open Systems Interconnection |
+| OTDOA | Observed Time Difference Of Arrival |
+| PBS | Personal Broadcast Service |
+| PBX | Private Branch eXchange |
+| PCC | Policy and Charging Control |
+| PCM | Pulse Code Modulation |
+| PCEF | Policy and Charging Enforcement Function |
+| PCRF | Policy and Charging Rules Function |
+| PDC | Personal Digital Communication |
+| PDC-EFR | ARIB PDC-EFR 6.7 kbit/s speech Codec |
+| PDG | Packet Data Gateway |
+| PDN | Packet Data Network |
+| PDP | Packet Data Protocol |
+| PDU | Protocol Data Unit |
+| PI | Presentation Indicator |
+| PIX | Proprietary application Identifier eXtension |
+| PLMN | Public Land Mobile Network |
+| PM | Performance Management |
+| PMIP | Proxy Mobile IP |
+| PMIP/PMIPv6 | Proxy Mobile IP version 6 |
+| PNM | Personal Network Management |
+| PP | Point-to-Point |
+| PPC | Policy Control and Charging |
+| PS | Packet Switched |
+| PSAP | Public Service Access Point |
+| PSE | Personal Service Environment |
+| PSS | Packet-switched Streaming Service |
+| PSTN | Public Switched Telephone Network |
+| QCI | QoS Class Identifier |
+| QoS | Quality of Service |
+| RANAP | Radio Access Network Application Part |
+| RLC/MAC | Radio Link Control/Media Access Control |
+
+| | |
+|-------|-------------------------------------------------------------------------------------|
+| RNC | Radio Network Controller |
+| RNS | Radio Network Subsystem (also appears as "Radio Network System") |
+| RR | Radio Resources |
+| RTP | Real Time Protocol |
+| SAT | SIM Application Toolkit |
+| SC | Service Centre (used for SMS) |
+| SCF | Service Control Function (IN context), Service Capability Feature (VHE/OSA context) |
+| SCR | Source Controlled Rate |
+| SCTP | Stream Control Transmission Protocol |
+| SGSN | Serving GPRS Support Node |
+| SGW | Signalling GateWay |
+| SID | Silence Descriptor |
+| SIM | GSM Subscriber Identity Module |
+| SIP | Session Initiation Protocol |
+| SIPTO | Selected IP Traffic Offload |
+| SLF | Subscription Locator Function |
+| SM | Session Management |
+| SM | Short Message |
+| SMC | Short Message Control |
+| SMIL | Synchronized Multimedia Integration Language |
+| SMLC | Serving Mobile Location Centre |
+| SM-RL | Short Message Relay Layer |
+| SMS | Short Message Service |
+| SP | Service Provider |
+| SRF | Speech Recognition Framework |
+| SRNC | Serving Radio Network Controller |
+| SRNS | Serving RNS |
+| SRVCC | Single Radio Voice Call Continuity |
+| SS | Solution Set |
+| SS | Supplementary Service |
+| SS7 | Signalling System No. 7 |
+| SSF | Service Switching Function |
+| STN | Signalling Transport Network |
+| SuM | Subscription Management |
+| TA | Terminal Adaptation |
+| TAF | Terminal Adaptation Function |
+
+| | |
+|----------|----------------------------------------------------------------|
+| TCAP | Transaction Capabilities |
+| TCH/F | A full rate Traffic Channel |
+| TDD | Time Division Duplex |
+| TDMA | Time Division Multiple Access |
+| TDMA_EFR | TIA IS-641 Enhanced speech Codec |
+| TDMA_USI | TIA TDMA-US1 (12.2 kbit/s Codec, similar to GSM-EFR) |
+| TE | Terminal Equipment |
+| TFO | Tandem Free Operation |
+| TFT | Traffic Flow Template |
+| TrFO | Transcoder Free Operation |
+| TrGW | Transition Gateway |
+| UA | User Agent |
+| UDC | User Data Convergence |
+| UDP | User Datagram Protocol |
+| UDR | User Data Repository |
+| UE | User Equipment |
+| UI | User Interaction |
+| UI | User Interface |
+| UICC | Universal IC Card |
+| UMTS | Universal Mobile Telecommunications System |
+| USAT | USIM Application Toolkit |
+| USIM | Universal Subscriber Identity Module |
+| USSD | Unstructured Supplementary Service Data |
+| UTRA | Universal Terrestrial Radio Access |
+| UTRA-FDD | Universal Terrestrial Radio Access – Frequency Division Duplex |
+| UTRAN | Universal Terrestrial Radio Access Network |
+| UTRA-TDD | Universal Terrestrial Radio Access – Time Division Duplex |
+| VAD | Voice Activity Detector |
+| VCC | Voice Call Continuity |
+| VHE | Virtual Home Environment |
+| VLR | Visitor Location Register |
+| VPLMN | Visited Public Land Mobile Network |
+| WAG | WLAN Access Gateway |
+| WLAN | Wireless Local Area Network |
+| WSDL | Web Service Description Language |
+| XML | extensible Markup Language |
+
+# 5 Introduction
+
+The LTE-Advanced evolved packet core (EPC) for this IMT-2000 family member, referred to as "3GPP Release 11", is based on an evolved core network from the 3rd generation Release 8 through to Release 10. The technical specifications have been developed in a partnership project and transposed to the involved Standards Development Organizations (SDOs). The system will support different applications ranging from narrow-band to wideband communications capability with integrated personal and terminal mobility to meet the user and service requirements.
+
+Release 11 is the fourth release of this third generation of mobile communications technology for EPC. The core network interfaces identified in this Recommendation constitute a complete evolved packet core network system for this IMT-2000 Family Member. The EPC network of 3GPP Release 11 supports third and fourth generation radio access networks as options.
+
+Refer to clause 10.2.18, Service principles, for more information.
+
+The descriptions of the technical specifications listed in clause 10 are for informative purposes only. Normative information is in the table for the respective specification.
+
+# 6 Basic EPC Architecture for LTE-Advanced evolved packet system (EPS)
+
+## 6.1 Architecture for 3GPP accesses
+
+The text in this clause is based on the text in references [ETSI TS 123 401], [TTC TS-3GA-23.401], [ATIS 3GPP 23.401] and [TTA TTAT.3G-23.401], clause 4.2.
+
+### 6.1.1 Non-roaming architecture
+
+
+
+The diagram illustrates the non-roaming architecture for 3GPP accesses. On the left, a 'UE' (User Equipment) is connected to an 'E-UTRAN' via the 'LTE-Uu' interface. The 'E-UTRAN' is part of the '3GPP access' group, which also includes 'UTRAN' and 'GERAN'. The 'E-UTRAN' connects to an 'MME' (Mobility Management Entity) via the 'S1-U' interface. The 'MME' is connected to an 'SGSN' (Serving GPRS Support Node) via the 'S3' interface. The 'SGSN' is connected to a 'HSS' (Home Subscriber Server) via the 'S6a' interface. The 'MME' is also connected to a 'Serving gateway' via the 'S11' interface. The 'Serving gateway' is connected to a 'PDN gateway' via the 'S5' interface. The 'PDN gateway' is connected to 'Operator's IP services (e.g. IMS, PSS etc.)' via the 'SGi' interface. A 'PCRF' (PDN Gateway Control and Policy Function) is connected to the 'PDN gateway' via the 'Gx' interface and to the 'Operator's IP services' via the 'Rx' interface. The '3GPP access' box contains the 'UTRAN', 'GERAN', 'SGSN', 'MME', and 'HSS' components. The 'UE' is outside the '3GPP access' box. The 'E-UTRAN' is also outside the '3GPP access' box. The 'Serving gateway', 'PDN gateway', and 'Operator's IP services' are also outside the '3GPP access' box. The 'PCRF' is also outside the '3GPP access' box. The diagram is labeled 'Q.1743(16)\_F6.1.1-1' at the bottom right.
+
+Diagram of Non-roaming architecture for 3GPP accesses
+
+**Figure 6.1.1-1 – Non-roaming architecture for 3GPP accesses**
+
+NOTE – The "3GPP Access" box represents a collection of functional entities and interfaces for the purpose of pictorial simplification of the architectural models presented below, in the figures of clause 6.2.
+
+
+
+Figure 6.1.1-2: Non-roaming architecture for 3GPP accesses. Single gateway configuration option. The diagram shows the following components and their interfaces: UE connects to E-UTRAN via LTE-Uu. E-UTRAN connects to MME via S1-MME and S1-U. MME connects to SGSN via S3, to HSS via S6a, and to Serving gateway via S11 and S10. SGSN connects to UTRAN/GERAN, HSS via S6a, and Serving gateway via S4 and S12. Serving gateway and PDN gateway are shown as a single block (single gateway configuration) connected to PCRF via Gx and Operator's IP services via SGi. PCRF connects to Operator's IP services via Rx.
+
+**Figure 6.1.1-2 – Non-roaming architecture for 3GPP accesses.
+Single gateway configuration option**
+
+NOTE 1 – Also in this configuration option, S5 can be used between non collocated serving gateway and PDN gateway.
+
+NOTE 2 – Additional interfaces for 2G/3G access are shown in TS 23.060. TTC TS-3GA-23.060
+
+### 6.1.2 Roaming architecture
+
+
+
+Figure 6.1.2-1: Roaming architecture for 3GPP accesses. Home routed traffic. The diagram is split by a dashed orange line into HPLMN (top) and VPLMN (bottom). In HPLMN: HSS, PDN gateway, PCRF, and Operator's IP services. In VPLMN: UE, E-UTRAN, MME, SGSN, UTRAN, GERAN, and Serving gateway. Key interfaces: S6a connects HSS (HPLMN) to MME (VPLMN). S8 connects PDN gateway (HPLMN) to Serving gateway (VPLMN). Gx connects PDN gateway to PCRF. SGi connects PDN gateway to Operator's IP services. Rx connects PCRF to Operator's IP services. Within VPLMN: UE to E-UTRAN via LTE-Uu; E-UTRAN to MME via S1-MME and S1-U; MME to SGSN via S3; MME to Serving gateway via S11 and S10; SGSN to Serving gateway via S4 and S12.
+
+**Figure 6.1.2-1 – Roaming architecture for 3GPP accesses. Home routed traffic**
+
+NOTE – Additional interfaces/reference points for 2G/3G accesses are documented in TS 23.060.
+
+Figures 6.1.2-2 and 6.1.2-3 represent the Roaming with local breakout case with application function (AF) in the home network and in the visited network respectively. The concurrent use of AF's in the home network and AF's in the visited network is not excluded.
+
+
+
+Figure 6.1.2-2: Roaming architecture for local breakout, with home operator's application functions only. The diagram shows a UE connected to E-UTRAN, which is connected to an MME. The MME is connected to a Serving gateway, which is connected to a PDN gateway. The PDN gateway is connected to a Visited operator PDN. The MME is also connected to an SGSN, which is connected to UTRAN and GERAN. The MME is connected to an HSS via S6a. The HSS is connected to an H-PCRF via S9. The H-PCRF is connected to Home operator's IP services via Rx. The PDN gateway is connected to a V-PCRF via Gx. The V-PCRF is connected to the H-PCRF via S9. The PDN gateway is connected to the Visited operator PDN via SGi. The diagram is divided into HPLMN and VPLMN by a dashed orange line. Reference points S1-MME, S1-U, S3, S4, S5, S6a, S9, S10, S11, S12, Gx, Rx, and SGi are labeled.
+
+**Figure 6.1.2-2 – Roaming architecture for local breakout, with home operator's application functions only**
+
+NOTE 2 – See TS 23.203 for the role of and functions related to home and visited PCRF and S9/Rx reference points.
+
+NOTE 3 – In Figure 6.1.2-2, the control plane signalling and the user plane for accessing to home operator's services traverse over the SGi reference point via the visited operator's PDN.
+
+
+
+Figure 6.1.2-3: Roaming architecture for local breakout, with visited operator's application functions only. This diagram is similar to Figure 6.1.2-2 but with a key difference: the H-PCRF is not connected to the Home operator's IP services. Instead, the V-PCRF is connected to the Visited operator IP service via Rx. The H-PCRF is connected to the V-PCRF via S9. The PDN gateway is connected to the Visited operator IP service via SGi. All other components and reference points (UE, E-UTRAN, MME, SGSN, UTRAN, GERAN, HSS, Serving gateway, PDN gateway, Visited operator PDN) remain the same as in Figure 6.1.2-2.
+
+**Figure 6.1.2-3 – Roaming architecture for local breakout, with visited operator's application functions only**
+
+## 6.2 Architecture for non-3GPP accesses
+
+The text in this clause is based on the text in references [ETSI TS 123 402], [TTC TS-3GA-23.402], [ATIS 3GPP 23.402] and [TTA TTAT.3G-23.402], clause 4.2.
+
+The EPS supports the use of non-3GPP IP access networks to access the EPC management mechanism (e.g., MIP) over S2 reference points. The EPS supports IETF-based network-based mobility management mechanism (i.e. PMIP) over S5 and S8 reference points.
+
+### 6.2.1 Non-roaming architecture
+
+The following considerations apply to interfaces where they occur in figures in this and the next clause:
+
+- S5, S2a and S2b can be GTP-based or PMIP-based.
+- Gxc is used only in the case of PMIP variant of S5 or S8.
+- Gxa is used when the trusted non-3GPP access network is owned by the same operator.
+- Gxb is used only in the case of PMIP variant of S2b.
+- S9 is used instead of Gxa to the trusted non-3GPP Access network not owned by the same operator.
+- Gxa or S9 are terminated in the trusted non-3GPP accesses if supported.
+- S2c is used only for dual stack mobile IPv6 (DSMIPv6) bootstrapping and DSMIPv6 de-registration (binding update with lifetime equals zero) when the user equipment (UE) is connected via 3GPP access. Dashed lines are used in Figure 6.2.1-2, Figure 6.2.1-3 and Figure 6.2.2-5 to indicate this case.
+
+NOTE 1 – SWu shown in Figure 6.2.1-1 also applies to architectural reference Figures 6.2.1-2 and 6.2.2-1 to 6.2.2-5, but is not shown for simplicity.
+
+
+
+Figure 6.2.1-1: Non-roaming architecture within EPS using S5, S2a, S2b. The diagram shows the internal architecture of an EPS. At the top, HSS is connected to PCRF via S6a. PCRF is connected to PDN gateway via Gx and Gxc. PDN gateway is connected to 3GPP access via S5 and to Operator's IP services via SGi. Operator's IP services are also connected to PCRF via Rx. PDN gateway is connected to ePDG via S2b. ePDG is connected to 3GPP AAA server via SWm and to Untrusted Non-3GPP IP access via SWn. 3GPP AAA server is connected to UE via STa. Trusted Non-3GPP IP access is connected to PDN gateway via S2a and Gxa, and to UE via SWu. Untrusted Non-3GPP IP access is connected to ePDG via SWn and to UE via SWa. A dashed red line separates the HPLMN (above) from Non-3GPP networks (below). SWx is shown at the top right, connected to PCRF.
+
+**Figure 6.2.1-1 – Non-roaming architecture within EPS using S5, S2a, S2b**
+
+NOTE 2 – For S2a using a trusted wireless local area network (WLAN) access, refer to [ETSI TS 123 402], [TTC TS-3GA-23.402], [ATIS 3GPP 23.402] and [TTA TTAT.3G-23.402], clause 16.
+
+
+
+Figure 6.2.1-2: Non-roaming architecture within EPS using S5, S2c. The diagram shows a UE connected to Trusted and Untrusted Non-3GPP IP access, which are connected to an ePDG. The ePDG is connected to a PDN gateway via S2c. The PDN gateway is connected to a Serving gateway via S5. The Serving gateway is connected to 3GPP access. The HSS is connected to the Serving gateway via S6a. The PDN gateway is connected to a PCRF via Gx. The PCRF is connected to the HSS via S6a. The PCRF is also connected to Operator's IP services via Rx. The PDN gateway is connected to Operator's IP services via SGi. The PDN gateway is also connected to the ePDG via Gxb. The ePDG is connected to the 3GPP AAA server via SWm. The 3GPP AAA server is connected to the HSS via SWx. The UE is connected to the Trusted Non-3GPP IP access via S2c. The UE is also connected to the Untrusted Non-3GPP IP access via S2c. The Trusted Non-3GPP IP access is connected to the PDN gateway via Gxa. The Untrusted Non-3GPP IP access is connected to the ePDG via SWn. The diagram is divided into HPLMN and Non-3GPP networks by a dashed red line. Reference Q.1743(16)\_F6.2.1-2 is shown at the bottom right.
+
+Figure 6.2.1-2 – Non-roaming architecture within EPS using S5, S2c
+
+### 6.2.2 Roaming architecture
+
+
+
+Figure 6.2.2-1: Roaming architecture for EPS using S8, S2a-S2b – Home routed. The diagram shows a UE connected to Trusted and Untrusted Non-3GPP IP access, which are connected to an ePDG. The ePDG is connected to a vPCRF via S2a. The vPCRF is connected to a PDN gateway via S2b. The PDN gateway is connected to a Serving gateway via S8. The Serving gateway is connected to 3GPP access. The HSS is connected to the PDN gateway via S6a. The PDN gateway is connected to a hPCRF via Gx. The hPCRF is connected to the HSS via S6a. The hPCRF is also connected to Operator's IP services via Rx. The PDN gateway is connected to Operator's IP services via SGi. The PDN gateway is also connected to the ePDG via Gxb. The ePDG is connected to a 3GPP AAA proxy via SWm. The 3GPP AAA proxy is connected to a 3GPP AAA server via SWd. The 3GPP AAA server is connected to the HSS via SWx. The UE is connected to the Trusted Non-3GPP IP access via S2a. The UE is also connected to the Untrusted Non-3GPP IP access via S2b. The Trusted Non-3GPP IP access is connected to the PDN gateway via Gxa. The Untrusted Non-3GPP IP access is connected to the ePDG via SWn. The diagram is divided into HPLMN and VPLMN (Non-3GPP networks) by dashed red lines. Reference Q.1743(16)\_F6.2.2-1 is shown at the bottom right.
+
+Figure 6.2.2-1 – Roaming architecture for EPS using S8, S2a-S2b – Home routed
+
+
+
+The diagram illustrates the roaming architecture for EPS using PMIP-based S8, S2a, and S2b interfaces in a home-routed scenario. It is divided into three main sections by horizontal dashed red lines: HPLMN (Home Public Land Mobile Network) at the top, VPLMN (Visited Public Land Mobile Network) in the middle, and Non-3GPP networks at the bottom.
+
+- HPLMN:** Contains the HSS (Home Subscriber Server), PDN gateway, hPCRF (home PCRF), and Operator's IP services (e.g., IMS, PSS etc.). The HSS is connected to the PDN gateway via the S6a interface. The PDN gateway is connected to the hPCRF via the Gx interface and to the Operator's IP services via the SGi interface. The hPCRF is connected to the Operator's IP services via the Rx interface.
+- VPLMN:** Contains the 3GPP access (Serving gateway\*\*), vPCRF (visited PCRF), and ePDG (evPDG). The Serving gateway\*\* is connected to the PDN gateway via the S8 interface. The Serving gateway\*\* is connected to the vPCRF via the Gxc interface. The Serving gateway\*\* is connected to the ePDG via the S2b interface. The Serving gateway\*\* is also connected to the Trusted Non-3GPP IP access via the S2a-PMIP interface. The vPCRF is connected to the ePDG via the Gxb interface. The ePDG is connected to the 3GPP AAA proxy via the SWm interface.
+- Non-3GPP networks:** Contains the Trusted Non-3GPP IP access and the Untrusted Non-3GPP IP access. The Trusted Non-3GPP IP access is connected to the Serving gateway\*\* via the S2a-PMIP interface and to the ePDG via the Gxa interface. The Untrusted Non-3GPP IP access is connected to the ePDG via the Wn\* interface and to the 3GPP AAA proxy via the SWa interface.
+- AAA and Proxy:** The 3GPP AAA server is connected to the HSS via the SWx interface and to the 3GPP AAA proxy via the SWd interface. The 3GPP AAA proxy is connected to the ePDG via the SWm interface and to the Untrusted Non-3GPP IP access via the SWa interface. The 3GPP AAA proxy is also connected to the HSS via the STa interface.
+
+Interfaces and labels: S6a, S8, S2a-PMIP, S2b, Gxc, Gxb, Gxa, Gx, SGi, Rx, SWx, SWd, SWm, SWa, STa, Wn\*, hPCRF, vPCRF, PDN gateway, Serving gateway\*\*, ePDG, 3GPP AAA server, 3GPP AAA proxy, Operator's IP services (e.g. IMS, PSS etc.), HSS, Trusted Non-3GPP IP access, Untrusted Non-3GPP IP access.
+
+Q.1743(16)\_F6.2.2-2
+
+Roaming architecture for EPS using PMIP-based S8, S2a, S2b (Chained PMIP-based S8-S2a/b) – Home routed diagram
+
+\*\* Chained S2a/S2b and S8 used when visited public land mobile network (VPLMN) has business relationship with non-3GPP Networks and S-GW in VPLMN includes local non-3GPP Anchor.
+
+**Figure 6.2.2-2 – Roaming architecture for EPS using PMIP-based S8, S2a, S2b (Chained PMIP-based S8-S2a/b) – Home routed**
+
+NOTE 1 – AAA, mobility, and QoS policy and event reporting related optimizations (e.g., signalling reduction and information hiding towards the home public land mobile network (HPLMN)) for PMIP-based S8-S2a/b chaining are not specified within this Release of the specification.
+
+NOTE 2 – GTP-based S8-S2b chaining is not specified within this Release of the specification.
+
+The following are some additional considerations in this case:
+
+- Gxc is used only in the case of PMIP-based S8 and for 3GPP access.
+
+NOTE 3 – If QoS enforcement on PMIP-based S8 is required by the serving gateway for un-trusted non-3GPP IP accesses, static policies will be used in this Release of the specification.
+
+- Gxc is not required for trusted non-3GPP IP Access; Gxa is used instead to signal the QoS policy and event reporting.
+
+NOTE 4 – For S2a using a trusted WLAN access, refer to [ETSI TS 123 402], [TTC TS-3GA-23.402], [ATIS 3GPP 23.402] and [TTA TTAT.3G-23.402], clause 16.
+
+
+
+Figure 6.2.2-3: Roaming architecture for EPS using S8 – S2c – Home routed. This diagram shows the network architecture for EPS roaming. It is divided into HPLMN (Home PLMN) and VPLMN (Visited PLMN) by a dashed red line. In the HPLMN, the HSS is connected to the PDN gateway via S6a. The PDN gateway is connected to the hPCRF via Gx and to the 3GPP AAA server via S6b. The hPCRF is connected to the Operator's IP services (e.g., IMS, PSS etc.) via Rx. The PDN gateway is also connected to the 3GPP AAA server via SWx. In the VPLMN, the 3GPP access is connected to the Serving gateway via S8. The Serving gateway is connected to the PDN gateway via Gxc. The Serving gateway is also connected to the vPCRF via Gxc. The vPCRF is connected to the hPCRF via S9. The vPCRF is connected to the ePDG via Gxb. The ePDG is connected to the 3GPP AAA proxy via SWm. The ePDG is also connected to the Untrusted Non-3GPP IP access via SWn. The Untrusted Non-3GPP IP access is connected to the 3GPP AAA proxy via SWa. The UE is connected to the Trusted Non-3GPP IP access via S2c and to the Untrusted Non-3GPP IP access via S2c. The Trusted Non-3GPP IP access is connected to the PDN gateway via Gxa. The UE is also connected to the PDN gateway via S2c. The 3GPP AAA proxy is connected to the 3GPP AAA server via SWd. The 3GPP AAA server is connected to the PDN gateway via S6b. The 3GPP AAA server is also connected to the 3GPP AAA proxy via SWd. The 3GPP AAA proxy is connected to the PDN gateway via S6b. The 3GPP AAA proxy is also connected to the 3GPP AAA server via SWd. The 3GPP AAA server is connected to the PDN gateway via S6b. The 3GPP AAA server is also connected to the 3GPP AAA proxy via SWd. The 3GPP AAA proxy is connected to the PDN gateway via S6b. The 3GPP AAA proxy is also connected to the 3GPP AAA server via SWd.
+
+Figure 6.2.2-3 – Roaming architecture for EPS using S8 – S2c – Home routed
+
+
+
+Figure 6.2.2-4: Roaming architecture for EPS using S5, S2a, S2b – Local breakout. This diagram shows the network architecture for EPS roaming with local breakout. It is divided into VPLMN (Visited PLMN) and HPLMN (Home PLMN) by a dashed line. In the HPLMN, the Subscription profile repository (SPR) is connected to the Policy and charging rules function (H-PCRF) via Sp. The H-PCRF is connected to the AF via Rx and to the Online charging system (OCS) via Sy. The H-PCRF is also connected to the V-PCRF via S9. In the VPLMN, the V-PCRF is connected to the AF via Rx. The V-PCRF is connected to the BBERF via Gxx. The V-PCRF is also connected to the TDF via Sd. The V-PCRF is connected to the Gateway via Gx. The Gateway is connected to the PCEF via Gy. The PCEF is connected to the Offline charging system (OFCS) via Gz. The Gateway is also connected to the OFCS via Gz. The V-PCRF is connected to the H-PCRF via S9. The H-PCRF is connected to the SPR via Sp. The H-PCRF is connected to the AF via Rx. The H-PCRF is connected to the OCS via Sy. The H-PCRF is also connected to the V-PCRF via S9. The V-PCRF is connected to the AF via Rx. The V-PCRF is connected to the BBERF via Gxx. The V-PCRF is also connected to the TDF via Sd. The V-PCRF is connected to the Gateway via Gx. The Gateway is connected to the PCEF via Gy. The PCEF is connected to the OFCS via Gz. The Gateway is also connected to the OFCS via Gz.
+
+Figure 6.2.2-4 – Roaming architecture for EPS using S5, S2a, S2b – Local breakout
+
+NOTE 5 – The two Rx instances in Figure 6.2.2-4 apply to different application functions in the HPLMN and VPLMN.
+
+NOTE 6 – For S2a using a Trusted WLAN access, refer to [ETSI TS 123 402], [TTC TS-3GA-23.402], [ATIS 3GPP 23.402] and [TTA TTAT.3G-23.402], clause 16.
+
+
+
+The diagram illustrates a roaming architecture for the Evolved Packet System (EPS) using S5 and S2c interfaces with local breakout. It is divided into three main horizontal sections: HPLMN (Home Public Land Mobile Network) at the top, VPLMN (Visited Public Land Mobile Network) in the middle, and Non-3GPP networks at the bottom.
+
+- HPLMN:** Contains the HSS (Home Subscriber Server), hPCRF (home Policy and Charging Rules Function), 3GPP AAA server, and Operator's IP services (e.g., IMS, PSS etc.).
+- VPLMN:** Contains the vPCRF (visited PCRF), PDN gateway, Serving gateway, 3GPP access, ePDG (evolved Packet Data Gateway), and 3GPP AAA proxy. It also includes Visited network IP services or proxies.
+- Non-3GPP networks:** Contains Trusted Non-3GPP IP access, Untrusted Non-3GPP IP access, and the UE (User Equipment).
+
+Key interfaces shown include S6a, Rx, SWx, S9, Gxc, Gx, S5, SGi, S6b, SWd, SWm, Gxa, SWn, S2c, SWa, and STa. Dashed lines represent the boundaries between HPLMN, VPLMN, and Non-3GPP networks.
+
+Figure 6.2.2-5 – Roaming architecture for EPS using S5, S2c – Local breakout
+
+**Figure 6.2.2-5 – Roaming architecture for EPS using S5, S2c – Local breakout**
+
+NOTE 7 – The two Rx instances in Figure 6.2.2-5 apply to different application functions in the HPLMN and VPLMN.
+
+### 6.3 Architecture for MBMS
+
+The text in this clause is based on the text in references [ETSI TS 123 246], [TTC TS-3GA-23.246], [ATIS 3GPP 23.246] and [TTA TTAT.3G-23.246], clause 4.2.2.
+
+
+
+This diagram shows the reference architecture for the evolved packet system supporting Multimedia Broadcast Multicast Service (MBMS) in broadcast mode only, involving both E-UTRAN and UTRAN access networks.
+
+- Core Network Entities:** MME (Mobility Management Entity), PDN gateway, MBMS GW (MBMS Gateway), BM-SC (Broadcast Multicast Service Center), SGSN (Serving GPRS Support Node), and Content provider.
+- Access Networks:** E-UTRAN and UTRAN.
+- User Equipment:** Two UE instances are shown, one connected to E-UTRAN via the E-UTRAN-Uu interface and another to UTRAN via the Uu interface.
+- Interfaces:** M3 (MME to E-UTRAN), Sm (MME to MBMS GW), SGmb/SGi-mb (MBMS GW to BM-SC), SGi (PDN gateway to BM-SC), M1 (MBMS GW to E-UTRAN), Sn (MBMS GW to SGSN), and Iu (SGSN to UTRAN).
+
+Figure 6.3-1 – Reference architecture for evolved packet system with E-UTRAN and UTRAN (MBMS broadcast mode only)
+
+**Figure 6.3-1 – Reference architecture for evolved packet system with E-UTRAN and UTRAN (MBMS broadcast mode only)**
+
+NOTE 1 – In addition to MBMS Bearers (over SGmb/SGi-mb), the BM-SC may use EPS bearers (over SGi) to realize an MBMS user service as specified in TS 26.346.
+
+NOTE 2 – The MCE (multi-cell/multicast coordination entity) is not shown in the figure.
+
+**Rec. ITU-T Q.1743 (09/2016)** 41
+
+NOTE 3 – MBMS service over Gn-SGSN is supported when the MBMS-GW is co-located with the PDN GW and this PDN GW has the necessary gateway GPRS support node (GGSN) functions to control the MBMS bearer service over Gn.
+
+## 6.4 Architecture of E-UTRAN LCS
+
+The following text is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 5.2.3.
+
+The basic configuration of evolved universal terrestrial radio access network (E-UTRAN) LCS is presented in Figure 6.4.
+
+
+
+Figure 6.4: Configuration of LCS entities for an E-UTRAN PLMN. The diagram shows a UE connected to an E-UTRAN via an LTE-Uu interface. The E-UTRAN is connected to an MME via an S1 interface. The MME is connected to an E-SMLC via an SLs interface and to a GMLC via an SLg interface. The GMLC is connected to an External LCS client via an Le interface and to an HSS via an SLh interface. The diagram is labeled Q.1743(16)\_F6-4.
+
+Figure 6.4 – Configuration of LCS entities for an E-UTRAN PLMN
+
+## 6.5 Architecture for CBS
+
+The following text is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clauses 4a.5 and 5.4.
+
+The cell broadcast service (CBS) is a teleservice, which enables an information provider to submit short messages for broadcasting to a specified area within the PLMN.
+
+
+
+Figure 6.5: Warning system architecture for E-UTRAN access. The diagram shows a UE connected to an E-UTRAN via an E-UTRAN-Uu interface. The E-UTRAN is connected to an MME via an S1-MME interface. The MME is connected to a CBC via an SBc interface. The CBC is connected to a CBE via an interface. The diagram is labeled Q.1743(16)\_F6-5.
+
+Figure 6.5 – Warning system architecture for E-UTRAN access
+
+NOTE – The CBE and the interface between CBE and CBC are out of scope of 3GPP specifications.
+
+## 6.6 Architecture for policy control and charging
+
+The following text is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 5.11 "Configuration of policy control and charging entities".
+
+The PCC functionality is comprised by the functions of the policy and charging enforcement function (PCEF), the bearer binding and event reporting function (BBERF), the policy and charging rules function (PCRF), the application function (AF), the online charging system (OCS), the offline charging system (OFCS), the traffic detection function (TDF) and the subscription profile repository (SPR) or the user data repository (UDR). Figures 6.6-1 through 6.6-4 describe the non-roaming and roaming architecture for PCC.
+
+The PCC architecture extends the architecture of an IP-CAN, where the policy and charging enforcement function is a functional entity in the gateway node implementing the IP access to the PDN. The allocation of the bearer binding and event reporting function is specific to each IP-CAN type and specified in the TS 23.203.
+
+PCC function makes it possible to apply policy and charging control to any kind of 3GPP IP CAN and any non-3GPP accesses connected via EPC complying with TS 23.402. Applicability of PCC to other IP CAN is not restricted; however, it shall be possible for the PCC architecture to base decisions upon the type of IP CAN used (e.g., GPRS, I-WLAN, etc.). Support for policy control and
+
+charging when local breakout and roaming are applied as specified in TS 23.401 and TS 23.402 is supported.
+
+
+
+Figure 6.6-1: Overall PCC logical architecture (non-roaming) when SPR is used. The diagram shows a central Policy and charging rules function (PCRF) connected to several entities: Subscription profile repository (SPR) via Sp, AF via Rx, Online charging system (OCS) via Sy, BBERF via Gxx, TDF via Sd, and Gateway via Gx. The Gateway contains a PCEF and is connected to the Offline charging system (OFCS) via Gy and Gz interfaces. A reference label Q.1743(16)\_F6.6-1 is present.
+
+Figure 6.6-1 – Overall PCC logical architecture (non-roaming) when SPR is used
+
+
+
+Figure 6.6-2: Overall PCC logical architecture (non-roaming) when UDR is used. This diagram is similar to Figure 6.6-1 but replaces the SPR with a User data repository (UDR) connected to the PCRF via the Ud interface. All other connections and components (AF, OCS, BBERF, TDF, Gateway with PCEF, and OFCS) remain the same. A reference label Q.1743(16)\_F6.6-2 is present.
+
+Figure 6.6-2 – Overall PCC logical architecture (non-roaming) when UDR is used
+
+
+
+Figure 6.6-3: Overall PCC architecture (roaming with home routed access) when SPR is used. This diagram illustrates a roaming scenario with home routed access, divided into HPLMN (Home PLMN) and VPLMN (Visited PLMN) by a dashed line. In the VPLMN, a Policy and charging rules function (V-PCRF) is connected to a BBERF via Gxx and to the H-PCRF via the S9 interface. In the HPLMN, the H-PCRF is connected to the SPR via Sp, AF via Rx, OCS via Sy, TDF via Sd, and Gateway via Gx. The Gateway contains a PCEF and is connected to the OFCS via Gy and Gz. A reference label Q.1743(16)\_F6.6-3 is present.
+
+Figure 6.6-3 – Overall PCC architecture (roaming with home routed access) when SPR is used
+
+
+
+Figure 6.6-4: Overall PCC architecture for roaming with PCEF in visited network (local breakout) when SPR is used. The diagram shows the interaction between various network elements across HPLMN and VPLMN boundaries. In the HPLMN, the SPR connects to the H-PCRF via the Sp interface. The AF connects to the H-PCRF via the Rx interface. The H-PCRF connects to the V-PCRF via the S9 interface. The V-PCRF connects to the BBERF via the Gxx interface, to the TDF via the Sd interface, and to the PCEF (Gateway) via the Gx interface. The PCEF connects to the OFCS via the Gy and Gz interfaces. The OCS connects to the H-PCRF via the Sy interface and to the PCEF via the Gy interface. The V-PCRF also connects to an AF via the Rx interface. A dashed line separates the HPLMN and VPLMN.
+
+**Figure 6.6-4 – Overall PCC architecture for roaming with PCEF in visited network (local breakout) when SPR is used**
+
+## 6.7 Architecture for CSFB
+
+The following text is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 5.12 "Configuration of CSFB (CS fallback)".
+
+The CS fallback in EPS enables the provisioning of voice and other CS-domain services (e.g., CS UDI video/ SMS/ LCS/ USSD) by reuse of circuit switched (CS) infrastructure when the UE is served by E-UTRAN. This function is only available in case E-UTRAN coverage is overlapped by either GSM/EDGE radio access network (GERAN) coverage or UTRAN coverage.
+
+The configurations of the CSFB entities are represented in Figure 6.7.
+
+
+
+Figure 6.7: Configuration of CSFB. The diagram shows the UE connected to E-UTRAN via the Uu interface. The E-UTRAN is connected to the MME via the S1-MME interface. The MME is connected to the MSC/VLR via the SGs interface. The MSC/VLR is connected to the UTRAN via the Iu-CS interface and to the GERAN via the A interface. The UE is also shown with connections to UTRAN (Uu) and GERAN (Um).
+
+**Figure 6.7 – Configuration of CSFB**
+
+NOTE – The MGW is not shown in Figure 6.7 since the CS fallback in EPS does not have any impacts to the user plane handling.
+
+## 6.8 Architecture for single radio voice call continuity
+
+The following text is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 5.13 "Configuration of single radio voice call continuity (SRVCC)".
+
+Single radio voice call continuity (PS to CS) refers to continuity between IMS over PS access and CS calls that are anchored in IMS when the UE is capable of transmitting/receiving on only one of those access networks at a given time. PS to CS SRVCC is specified in TS 23.216. Figure 6.8-1 shows the entities involved in PS to CS SRVCC.
+
+
+
+Figure 6.8-1: SRVCC architecture for E-UTRAN to 3GPP UTRAN/GERAN. The diagram shows two User Equipment (UE) units. The top UE is connected to a Target UTRAN/GERAN via Um/Uu. The Target UTRAN/GERAN is connected to an MSC server via Iu-cs/A and to an SGSN via Iu-ps/Gb. The SGSN is connected to an MME via S3. The MME is connected to the MSC server via Sv, to an HSS via S6a, and to a Serving/PDN GW via S11. The Serving/PDN GW is connected to the 3GPP IMS via SGi. The bottom UE is connected to an E-UTRAN via EUTRAN-Uu. The E-UTRAN is connected to the MME via S1-MME and to the Serving/PDN GW via S1-U. The Serving/PDN GW is also connected to the 3GPP IMS via SGi. A vertical arrow on the left indicates the flow from the bottom UE to the top UE. The diagram is labeled Q.1743(16)\_F6.8-1.
+
+**Figure 6.8-1 – SRVCC architecture for E-UTRAN to 3GPP UTRAN/GERAN**
+
+CS to PS single radio voice call continuity refers to continuity between a CS call and IMS call over PS access that are anchored in IMS when the UE is capable of transmitting/receiving on only one of those access networks at a given time. CS to PS SRVCC is specified in TS 23.216. Figure 6.8-2 shows the entities involved in CS to PS SRVCC.
+
+
+
+Figure 6.8-2: CS to PS SRVCC architecture for UTRAN/GERAN to E-UTRAN. The diagram shows two User Equipment (UE) units. The top UE is connected to a UTRAN/GERAN via Um/Uu. The UTRAN/GERAN is connected to an MSC Server via Iu-cs/A and to an SGSN via Iu-ps/Gb. The SGSN is connected to an MME via S3. The MME is connected to the MSC Server via Sv, to an HSS via S6a, and to a Serving/PDN GW via S11. The MSC Server is connected to an IMS via D. The Serving/PDN GW is connected to the IMS via SGi. The bottom UE is connected to a Target E-UTRAN via E-UTRAN-Uu. The Target E-UTRAN is connected to the MME via S1-MME and to the Serving/PDN GW via S1-U. The Serving/PDN GW is also connected to the IMS via SGi. A vertical arrow on the left indicates the flow from the top UE to the bottom UE. A legend at the bottom indicates: solid line for 'Bearer path before HO', dashed line for 'Bearer path after HO', and dash-dot line for 'SIP signaling path after HO'. The diagram shows the bearer path before HO from the top UE through the UTRAN/GERAN, MSC Server, and IMS. The bearer path after HO is shown from the bottom UE through the Target E-UTRAN, MME, and Serving/PDN GW to the IMS. The SIP signaling path after HO is shown from the bottom UE through the Target E-UTRAN, MME, and Serving/PDN GW to the IMS.
+
+**Figure 6.8-2 – CS to PS SRVCC architecture for UTRAN/GERAN to E-UTRAN**
+
+NOTE 1 – The above figure only shows the necessary components related to MSC Server enhanced for CS to PS SRVCC.
+
+NOTE 2 – MSC Server shown in the figure is enhanced for CS to PS SRVCC.
+
+NOTE 3 – This architecture also applies to roaming scenario (i.e., S8, S6a are not impacted due to CS to PS SRVCC).
+
+## 6.9 Architecture for home (e)NodeB entities
+
+The following text is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 5.17.2 "Configuration of the home eNodeB subsystem".
+
+The configuration of home eNodeB subsystem with a home eNodeB gateway present is shown in Figure 6-9. In the figure, all the functions are considered implemented in different logical nodes. If two logical nodes are implemented in the same physical equipment, the relevant interfaces may become internal to that equipment.
+
+The presence of home eNodeB gateway in the configuration of home eNodeB subsystem is optional.
+
+The Home eNodeB Gateway may also be used only for the S1-MME interface. In this case, the S1-U interface is directly between the Home eNodeB and the S-GW.
+
+
+
+```
+graph LR
+ UE[UE] -- LTE-Uu --> HeNS
+ subgraph HeNS [Home eNode B subsystem (HeNS)]
+ HNB[Home eNode B]
+ HNBGW[Home eNode B gateway (optional)]
+ end
+ HNB -- S1-MME --> MME
+ HNBGW -- S1-U --> SGW
+ MME -- S6a --> HSS
+ subgraph HomeNetwork [Located in the home network]
+ CSG[CSG list server]
+ HSS[HSS (HLR, AuC)]
+ end
+ MME -- S11 --> SGW
+ SGW -- S7a --> CSS
+ subgraph VisitedNetwork [Located in the visited network]
+ CSS[CSS]
+ end
+ UE -.->|Uh (OMA DM/OTA)| CSG
+```
+
+Figure 6-9: Configuration of PLMN supporting home eNodeB subsystem. The diagram shows a UE connected to a Home eNode B via an LTE-Uu interface. The Home eNode B is part of a Home eNode B subsystem (HeNS) which also includes an optional Home eNode B gateway. The Home eNode B connects to an MME via an S1-MME interface, and the Home eNode B gateway connects to the MME via an S1-U interface. The MME is connected to an HSS (HLR, AuC) via an S6a interface. The HSS is located in the home network and contains a CSG list server. The MME is also connected to an SGW via an S11 interface. The SGW is connected to a CSS (CSG server) via an S7a interface. The CSS is located in the visited network. A dashed line labeled Uh (OMA DM/OTA) connects the UE to the CSG list server.
+
+Figure 6-9 – Configuration of PLMN supporting home eNodeB subsystem
+
+## 6.10 Architecture for machine-type communication
+
+The following text is based on the text in references [ETSI TS 123 682], [TTC TS-3GA-23.682], [ATIS 3GPP 23.682] and [TTA TTAT.3G-23.682], clause 4.2.
+
+Figure 6-10 shows the architecture for a UE used for MTC connecting to the 3GPP network (UTRAN, E-UTRAN, GERAN, etc.) via the Um/Uu/LTE-Uu interfaces. The architecture covers the various architectural models described in clause 4.1.
+
+
+
+Figure 6-10 – 3GPP Architecture for machine-type communication. This complex block diagram illustrates the network architecture for Machine-Type Communication (MTC). A horizontal dashed orange line separates the Home Public Land Mobile Network (HPLMN) at the top from the Visited Public Land Mobile Network (VPLMN) at the bottom. In the VPLMN, a 'MTC UE application' within a 'UE' connects to a 'RAN'. The RAN has control plane (dashed line) and user plane (solid line) connections to an 'MSC', 'MME', and 'SGSN'. These nodes connect further into the HPLMN. The 'MME' and 'SGSN' connect to an 'MTC-IWF' via T5b and T5a interfaces respectively. The 'MSC' connects to 'MTC-IWF' via T5c. The 'SGSN' also connects to an 'S-GW', which connects to a 'G-GSN/P-GW'. In the HPLMN, the 'G-GSN/P-GW' connects to a 'Services capability server (SCS)' and two 'Application server (AS)' blocks (labeled 1 and 2). AS 1 is part of an 'Indirect model' (via SCS), while AS 2 is part of a 'Direct model' (directly to G-GSN/P-GW). A 'Hybrid model' involves both. Other HPLMN entities include 'IP-SM-GW', 'SMS-SG/GMSC/IWMSC', 'SME', 'HSS', 'MTC AAA', and 'CDF/CGF'. Various reference points like T4, S6m, S6n, Tsp, Gi/SGi, and Tsms are labeled on the connecting lines.
+
+Q.1743(16)\_F6-10
+
+**Figure 6-10 – 3GPP Architecture for machine-type communication**
+
+NOTE 1 – Refer to TS 23.002, TS 23.060, TS 23.401, TS 23.272 and TS 23.040 for the details of 3GPP network-internal reference points not specifically shown or labelled in Figure 6.10-1 or described in this specification.
+
+NOTE 2 – The SCS is controlled by the operator of the HPLMN or by a MTC service provider.
+
+NOTE 3 – In the non-roaming case, all 3GPP network entities providing functionality for MTC are in the same PLMN. In the roaming case, 3GPP architecture for MTC supports both the home routed (illustrated in Figure 6.10-1) and the local-breakout roaming (not illustrated) scenarios. For the home routed scenario, the MTC server/application user plane communication is routed through the HPLMN. In the local breakout scenario, the user plane communication is routed directly through the serving PLMN/VPLMN over deployed GGSN/P-GW.
+
+# 7 Network entities
+
+## 7.1 Home subscriber server (HSS)
+
+Entities in the mobile system can be either implemented in a monolithic way where user data are stored within the entity itself (or in an external entity via non-standard interfaces) or according to the user data convergence (UDC) concept (see TS 23.335) where the entity becomes a so-called user-data-less application front end (AFE). Application front ends access, via the Ud reference point, a user data repository (UDR), which stores the relevant user data managed by the applications. Unless explicitly stated otherwise, this document describes entities in the monolithic form, e.g., assuming that user data are stored in the HSS. If however the UDC concept applies, user data are actually stored in the UDR and managed by one or several application front ends, so that
+
+user data may be shared among the different application front ends, allowing several AFEs of the same application type (e.g., HSS) to serve the same user at any given time.
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4.1.1.1.
+
+The HSS is the master database for a given user. It is the entity containing the subscription-related information to support the network entities actually handling calls/sessions.
+
+A home network may contain one or several HSSs: it depends on the number of mobile subscribers, on the capacity of the equipment and on the organization of the network.
+
+As an example, the HSS provides support to the call control servers in order to complete the routing/roaming procedures by solving authentication, authorization, naming/addressing resolution, location dependencies, etc.
+
+The HSS is responsible for holding the following user-related information:
+
+- user identification, numbering and addressing information;
+- user security information: Network access control information for authentication and authorization;
+- user location information at inter-system level: The HSS supports the user registration, and stores inter-system location information, etc.;
+- user profile information.
+
+The HSS also generates user security information for mutual authentication, communication integrity check and ciphering.
+
+Based on this information, the HSS also is responsible for supporting the call control (CC) and session management (SM) entities of the different domains and subsystems of the operator as shown in Figure 7.1-1.
+
+
+
+```
+graph TD
+ HSS((HSS))
+ HSS --- SI[Subscription information]
+ HSS --- LI[Location information]
+ HSS --- Dots[...]
+ HSS -- Sh --> AS[AS]
+ HSS -- D --> MSC[MSC server]
+ HSS -- C --> GMSC[GMSC server]
+ HSS -- Gr/S6d --> SGSN[SGSN]
+ HSS -- Gc --> GGSN[GGSN]
+ HSS -- Cx --> CSCF[CSCF]
+ HSS -- S6a --> MME[MME]
+```
+
+Diagram of a generic HSS structure and basic interfaces. The HSS is shown as an oval containing 'Subscription information', 'Location information', and '...'. It is connected to various network entities via interfaces: Sh to AS, D to MSC server, C to GMSC server, Gr/S6d to SGSN, Gc to GGSN, Cx to CSCF, and S6a to MME.
+
+Figure 7.1-1 – Example of a generic HSS structure and basic interfaces
+
+The HSS may integrate heterogeneous information, and enable enhanced features in the core network to be offered to the application and services domain, at the same time hiding the heterogeneity.
+
+The HSS consists of the following functionalities:
+
+- IP multimedia (IM) functionality to provide support to control functions of the IM subsystem such as the CSCF. It is needed to enable subscriber usage of the IM CN subsystem services. This IP multimedia functionality is independent of the access network used to access the IM CN subsystem.
+- The subset of the HLR/AUC functionality required by the PS domain (GPRS and EPC).
+
+- The subset of the HLR/AUC functionality required by the CS domain, if it is desired to enable subscriber access to the CS domain or to support roaming to legacy GSM/UMTS CS domain networks.
+
+The organization of the subscriber data is outlined in 3GPP TS 23.008. It also indicates which numbers, addresses and identifiers specified in 3G TS 23.003 are stored in HSS.
+
+### 7.1.1 Home location register (HLR)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4.1.1.1.1.
+
+The HLR can be considered a subset of the HSS that holds the following functionalities:
+
+- The functionality required to provide support to PS Domain entities such as the SGSN, MME and GGSN, through the Gr, S6a, S6d and Gc interfaces and the 3GPP AAA Server for EPS in case of non-3GPP access via SWx and for the I-WLAN through the D'/Gr' interface. It is needed to enable subscriber access to the PS domain services.
+- The functionality required to provide support to CS domain entities such as the MSC/MSC server and GMSC/GMSC server, through the C and D interfaces. It is needed to enable subscriber access to the CS domain services and to support roaming to legacy GSM/UMTS CS domain networks.
+
+### 7.1.2 Authentication centre (AuC)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4.1.1.1.2.
+
+The AuC can be considered a subset of the HSS that holds the following functionalities for the CS domain and PS domain:
+
+- The AuC is associated with an HLR and stores an identity key for each mobile subscriber registered with the associated HLR. This key is used to generate security data for each mobile subscriber:
+ - data which are used for mutual authentication of the international mobile subscriber identity (IMSI) and the network;
+ - a key used to check the integrity of the communication over the radio path between the mobile station and the network;
+ - a key used to cipher communication over the radio path between the mobile station and the network.
+- The AuC communicates only with its associated HLR over a non-standardized interface denoted the H interface. The HLR requests the data needed for authentication and ciphering from the AuC via the H interface, stores them and delivers them to the visitor location register (VLR), SGSN and MME which need them to perform the security functions for a mobile station.
+
+### 7.1.3 HSS logical functions
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4.1.1.1.3.
+
+This clause provides a high level and not exhaustive description of HSS functionality.
+
+
+
+Figure 7.1.3-1 – HSS logical functions. A block diagram showing the HSS (Home Subscriber Server) at the top, containing ten logical functions: Mobility management, Identification handling, User security information generation, Service authorization support, User security support, Access authorization, Service provisioning support, Application services support, Call/session establishment support, CAMEL services support, and a GUP data repository. Below the HSS, the diagram shows connections to various network elements: CS domain (GMSC, MSC/VLR), GPRS (SGSN, GGSN), EPC (SGSN, MME), 3GPP AAA server, Applications, GUP server, and IM CN subsystem (SIP application server, OSA SCS, IM-SSF, CSCF). Interfaces are labeled with codes like SWx, C, D, gsmSCF, Gr, Gc, Rp, Sh, Si, Cx, S6d, S6a.
+
+Q.1743(16)\_F7.1.3-1
+
+**Figure 7.1.3-1 – HSS logical functions**
+
+- *Mobility management*
+
+This function supports the user mobility through CS domain, PS domain and IM CN subsystem.
+- *Call and/or session establishment support*
+
+The HSS supports the call and/or session establishment procedures in CS domain, PS domain and IM CN subsystem. For terminating traffic, it provides information on which call and/or session control entity currently hosts the user.
+- *User security information generation*
+
+The HSS generates user authentication, integrity and ciphering data for the CS and PS domains and for the IM CN subsystem.
+- *User security support*
+
+The HSS supports the authentication procedures to access CS domain, PS domain and IM CN subsystem services by storing the generated data for authentication, integrity and ciphering and by providing these data to the appropriate entity in the CN (i.e., MSC/VLR, SGSN, MME, 3GPP AAA Server or CSCF).
+- *User identification handling*
+
+The HSS provides the appropriate relations among all the identifiers uniquely determining the user in the system: CS domain, PS domain and IM CN subsystem (e.g., IMSI and MSISDNs for CS domain; IMSI, MSISDNs and IP addresses for PS domain, private identity and public identities for IM CN subsystem).
+- *Access authorization*
+
+The HSS authorizes the user for mobile access when requested by the MSC/VLR, SGSN, MME, 3GPP AAA Server or CSCF, by checking that the user is allowed to roam to that visited network.
+
+- *Service authorization support*
+
+The HSS provides basic authorization for MT call/session establishment and service invocation. Besides, the HSS updates the appropriate serving entities (i.e., MSC/VLR, SGSN, MME, 3GPP AAA Server, CSCF) with the relevant information related to the services to be provided to the user.
+
+- *Service provisioning support*
+
+The HSS provides access to the service profile data for use within the CS domain, PS domain and/or IM CN subsystem.
+
+- *Application services and CAMEL services support (for GERAN and UTRAN access)*
+
+The HSS communicates with the session initiation protocol (SIP) application server and the OSA-SCS to support application services in the IM CN subsystem. It communicates with the IP multimedia-service switching function (IM-SSF) to support the customized applications for mobile network enhanced logic (CAMEL) services related to the IM CN subsystem. It communicates with the GSM service control function (gsmSCF) to support CAMEL services in the CS domain and PS domain (for GERAN and UTRAN access).
+
+- *GUP data repository*
+
+The HSS supports the storage of IM CN Subsystem user related data, and provides access to these data through the Rp reference point as described in TS 23.240.
+
+### 7.1.4 Application front ends (AFE)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.26.
+
+When the user data convergence (UDC) architecture is applied, certain functional entities keep the application logic, but do not locally store user data permanently. Examples of such functional entities are HLR/HSS/AuC and application servers. These data-less functional entities are known in the UDC architecture as application front ends. The application that is handled by an AFE determines the type of AFE, e.g., HLR-FE or HSS-FE. The reference points between the front ends and the core and service layers are not affected by the UDC architecture. More information on application front ends can be found in TS 23.335.
+
+### 7.1.5 User data repository (UDR)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.27.
+
+The UDR is a functional entity that acts as a single logical repository storing user data. The user-related data traditionally stored in the HSS/HLR/AuC, Application Servers, etc., are now stored in the UDR. UDR facilitates the share and provisioning of user-related data. The UDR provides a unique reference point to Application Front Ends such as HSS/HLR/AuC/AS Front Ends. This reference point is named Ud. More information on the UDR can be found in TS 23.335.
+
+### 7.1.6 Subscription locator function (SLF)
+
+The SLF:
+
+- Is queried by the I-CSCF during the registration and session setup to get the name of the HSS containing the required subscriber specific data. Furthermore the SLF is also queried by the S-CSCF during the Registration.
+- Is queried by the AS in conjunction with the Sh interface operation to get the name of the HSS containing the required subscriber specific data.
+- Is queried by the 3GPP AAA server to get the name of the HSS containing the required subscriber specific data.
+
+- Is accessed via the Dx interface by the CSCF, via the Dh interface by the AS, and via the Dw interface by the 3GPP AAA Server.
+
+The SLF is not required in a single HSS environment. An example for a single HSS environment is a server farm architecture. Use of SLF is not required when AS are configured/managed to use pre-defined HSS.
+
+## 7.2 Serving GPRS support node (SGSN)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clauses 4.1.3 and 4.1.3.1.
+
+The UMTS GPRS support nodes (GSN) is the gateway GSN (GGSN) and the serving GSN (SGSN). They constitute the interface between the radio system and the fixed networks for packet-switched services. The GSN performs all necessary functions in order to handle the packet transmission to and from the mobile stations.
+
+The location register function in the SGSN stores two types of subscriber data needed to handle originating and terminating packet data transfer:
+
+- Subscription information:
+ - the IMSI;
+ - one or more temporary identities;
+ - zero or more PDP addresses.
+- Location information:
+ - depending on the operating mode of the MS, the cell or the routeing area where the MS is registered;
+ - the VLR number of the associated VLR (if the Gs interface is implemented);
+ - the GGSN address of each GGSN for which an active PDP context exists.
+
+The SGSN provides support for direct tunnel functions as specified in TS 23.060.
+
+The organisation of the subscriber data in the SGSN is defined in TS 23.008 and TS 23.060.
+
+The procedures for information transfer between the SGSN, the GGSN, the VLR and the HLR are defined in TS 23.016 and TS 23.060.
+
+NOTE – When this improves the readability, the term 2G-SGSN can be used to refer to a SGSN Release 98 or prior, and the term 3G-SGSN can be used to refer to a SGSN Release 99 or later.
+
+The SGSN provides support for SRVCC functions as specified in TS 23.216.
+
+### Mobility management entity (MME)
+
+MME is the control plane entity within EPS supporting functions as listed below and described in specifications 3G TS 23.401, 3G TS 23.402 and 3G TS 36.300.
+
+- Mobility management;
+- NAS signalling and security;
+- Inter core network (CN) node signalling for mobility between 3GPP access networks;
+- Tracking area list management;
+- PDN GW and serving GW selection;
+- SGSN selection for handovers to 2G or 3G 3GPP access networks;
+- Roaming;
+- Authentication;
+- Bearer management functions including dedicated bearer establishment.
+
+- Lawful interception of signalling traffic.
+
+In order to support 3GPP2 access, MME supports:
+
+- High rate packet data (HRPD) access node selection and maintenance for handovers to HRPD;
+- Transparent transfer of HRPD signalling messages and transfer of status information between E-UTRAN and HRPD access;
+
+The procedures for information transfer between the SGSN, the MME and the HSS are defined in 3G TS 23.401 and 3G TS 23.060.
+
+The CS fallback enabled MME supports the following additional functions according to 3G TS 23.272:
+
+- Deriving a VLR number and LAI out of the TAI
+- Maintaining of SGs association towards MSC/VLR for EPS/IMSI attached UE
+- Initiating IMSI detach at EPS detach
+- Initiating paging procedure towards eNodeB when MSC pages the UE for CS services
+- Supporting SMS procedures for CS fallback.
+- Support CS fallback interface and related functions for 1xRTT CDMA access.
+
+When the MME supports the interworking to CS, the MME supports the following functions as specified in 3G TS 23.216:
+
+- Performing the PS bearer splitting function by separating the voice PS bearer from the non-voice PS bearers.
+- Handling the non-voice PS bearers handover with the target cell as according to Inter RAT handover procedure as defined in 3G TS 23.401.
+- Initiating the SRVCC handover procedure for handover of the voice component to the target cell.
+- Coordinating PS handover and SRVCC handover procedures when both procedures are performed,
+- Support interworking and SRVCC related functions for 1xRTT CDMA access.
+
+## 7.4 Serving GW
+
+The serving GW is the gateway which terminates the interface towards E-UTRAN.
+
+For each UE associated with the EPS, at a given point of time, there is a single serving GW. For detailed S-GW functions, see 3G TS 23.401 and 3G TS 23.402.
+
+Connectivity to a GGSN is not supported.
+
+The functions of the serving GW include:
+
+- the local mobility anchor point for inter-eNodeB handover;
+- Mobility anchoring for inter-3GPP mobility;
+- ECM-IDLE mode downlink packet buffering and initiation of network triggered service request procedure;
+- Lawful interception;
+- Packet routing and forwarding;
+- Transport level packet marking in the uplink and the downlink;
+- Accounting on user and QoS class identifier (QCI) granularity for inter-operator charging;
+
+- A local non-3GPP anchor for the case of roaming when the non-3GPP IP accesses connected to the VPLMN;
+- Event reporting (change of RAT, etc.) to the PCRF;
+- Uplink and downlink bearer binding towards 3GPP accesses as defined in 3G TS 23.203;
+- Uplink bearer binding verification with packet dropping of "misbehaving UL traffic";
+- Mobile access gateway (MAG) functions if PMIP-based S5 or S8 is used;
+- Support necessary functions in order for enabling GTP/PMIP chaining functions.
+
+## 7.5 PDN GW
+
+The PDN GW is the gateway which terminates the SGi interface towards the PDN.
+
+If a UE is accessing multiple PDNs, there may be more than one PDN GW for that UE, however a mix of S5/S8 connectivity and Gn/Gp connectivity is not supported for that UE simultaneously.
+
+The PDN-GW provides PDN connectivity to both GERAN/UTRAN only UEs and E UTRAN capable UEs using any of E UTRAN, GERAN or UTRAN. The PDN-GW provides PDN connectivity to E UTRAN capable UEs using E UTRAN only over the S5/S8 interface. The PDN-GW may also provide PDN connectivity to UEs using non-3GPP access networks with the procedures defined in TS 23.402.
+
+For detailed PDN GW functions, see TS 23.401 and TS 23.402.
+
+PDN GW functions include:
+
+- Per-user based packet filtering (by, e.g., deep packet inspection);
+- Lawful interception;
+- UE IP address allocation;
+- Transport level packet marking in the uplink and downlink, e.g., setting the DiffServ Code Point, based on the QCI of the associated EPS bearer;
+- UL and DL service level charging, gating control, rate enforcement as defined in TS 23.203;
+- UL and DL rate enforcement based on APN-AMBR;
+- DL rate enforcement based on the accumulated MBRs of the aggregate of SDFs with the same GBR QCI (e.g., by rate policing/shaping);
+- DHCPv4 (server and client) and DHCPv6 (client and server) functions;
+
+Additionally the PDN GW includes the following functions for the GTP-based S5/S8/S2a/S2b:
+
+- UL and DL bearer binding as defined in TS 23.203;
+- UL bearer binding verification; The PDN GW function also includes user plane anchor for mobility between 3GPP access and non-3GPP access. It supports:
+- A LMA function for PMIPv6, if PMIP-based S5 or S8, or if PMIP based S2a or PMIP based S2b is used;
+- A DSMIPv6 Home Agent, if S2c is used;
+- Allocation of GRE key, which is used to encapsulate uplink traffic to the PDN GW on the PMIP-based S5/S8, or PMIP based S2a or PMIP based S2b interface;
+- A MIPv4 Home Agent, if S2a with MIPv4 FA CoA mode is used.
+- GPRS tunnelling protocol for the control plane and the user plane to provide PDN connectivity to UEs using non-3GPP accesses, if GTP based S2a or GTP based S2b is used.
+
+## 7.6 EPC SGSN
+
+In addition to the functions described for GPRS, for EPC SGSN functions include:
+
+- Inter EPC node signalling for mobility between 2G/3G and E-UTRAN 3GPP access networks;
+- PDN and Serving GW selection: the selection of S GW/PDN GW by the SGSN is as specified for the MME;
+- MME selection for handovers to E-UTRAN 3GPP access network.
+
+For details, see 3G TS 23.401 and 3G TS 23.060.
+
+## 7.7 Trusted and untrusted non-3GPP access network
+
+Trusted and untrusted non-3GPP access networks are IP access networks that use access technology whose specification is out of the scope of 3GPP.
+
+Whether a non-3GPP IP access network is trusted or untrusted is not a characteristic of the access network.
+
+In non-roaming scenario it is the HPLMN's operator decision if a Non-3GPP IP access network is used as trusted or untrusted non-3GPP access network.
+
+In roaming scenario, the HSS/3GPP AAA Server in HPLMN makes the final decision of whether a Non-3GPP IP access network is used as trusted or untrusted non-3GPP access network. The HSS/3GPP AAA Server may take the VPLMN's policy and capability returned from the 3GPP AAA proxy or roaming agreement into account.
+
+For details, see TS 23.402.
+
+## 7.8 Enhanced packet data gateway (ePDG)
+
+The functionality of ePDG includes the following:
+
+- Functionality defined for the PDG in 3G TS 23.234 for the allocation of a remote IP address as an IP address local to the ePDG which is used as CoA when S2c is used;
+- Functionality for transportation of a remote IP address as an IP address specific to a PDN when S2b is used;
+- Routing of packets from/to PDN GW (and from/to serving GW if it is used as local anchor in VPLMN) to/from UE; if GTP based S2b is used, this includes routing of uplink packets based on the uplink packet filters in the traffic flow templates (TFTs) assigned to the S2b bearers of the PDN connection;
+- Routing of downlink packets towards the SWu instance associated to the PDN connection;
+- De-capsulation/Encapsulation of packets for IPSec and, if network based mobility (S2b) is used, for GTP or PMIP tunnels;
+- Mobile access gateway (MAG) for PMIPv6 if PMIP based S2b is used;
+- Tunnel authentication and authorization (termination of IKEv2 signalling and relay via AAA messages);
+- Local mobility anchor within untrusted non-3GPP access networks using IKEv2 mobility and multihoming protocol (MOBIKE) (if needed);
+- Transport level packet marking in the uplink;
+- Enforcement of QoS policies based on information received via AAA infrastructure;
+- Lawful interception.
+
+For details, see 3G TS 23.402.
+
+## 7.9 3GPP AAA server
+
+The 3GPP AAA server is located at the HPLMN and provides support for non-3GPP access users with services like authentication, authorisation and location management services in order to get access to EPS. It also contains necessary user related information in order to grant access to non-3GPP access. It also coordinates the information needed to support mobility between 3GPP and non-3GPP accesses such as coordination of PDN-GW information. It interacts with HSS to maintain consistent information for users supporting mobility and service continuity between 3GPP and non-3GPP access. For details, see 3G TS 23.402.
+
+## 7.10 3GPP AAA proxy
+
+The 3GPP AAA proxy provides support for roaming non-3GPP Access users in the VPLMN necessary the Authentication, Authorisation and location management services in order to get access to EPS. It may also provide roaming related information for support of chaining scenarios as described in 3G TS 23.402. If an S-GW is needed for non-3GPP access in the visited network, the 3GPP AAA proxy selects an S-GW for the UE during initial attach or handover attach.
+
+## 7.11 Access network discovery and selection function (ANDSF)
+
+The ANDSF (which is an optional element in the architecture) contains data management and control functionality necessary to provide network discovery and selection assistance data as per operators' policy. The ANDSF is able to initiate data transfer to the UE, based on network triggers, and respond to requests from the UE. It provides functions such as inter-system mobility policy, access network discovery information.
+
+The ANDSF in the subscriber's home operator network may interact with other databases such as the HSS user profile information residing in subscriber's home operator network. Details of such interaction with these databases are not described in this Release of the specifications. For details on ANDSF, see 3G TS 23.402.
+
+NOTE – When the UE is roaming, how it discovers and interacts with the ANDSF is not specified in the specification of this release.
+
+## 7.12 Border gateway (BG)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4.1.5.
+
+The border gateway (BG) is a gateway between a PLMN supporting GPRS/EPC and an external inter-PLMN backbone network used to interconnect with other PLMNs also supporting GPRS/EPC. The role of the BG is to provide the appropriate level of security to protect the PLMN and its subscribers.
+
+The BG is only needed in PLMNs supporting GPRS and EPC.
+
+## 7.13 The location services (LCS) entities
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.3.
+
+This section describes the location services entities found in the core network that support positioning methods for the UE/MS.
+
+### 7.13.1 Gateway mobile location centre (GMLC)
+
+The gateway mobile location centre (GMLC) is the first node an external location application accesses in the GSM PLMN. The GMLC performs registration authorization and requests routing information from the HLR. There may be more than one GMLC in a PLMN.
+
+## **7.14 Security gateway (SEG)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.10.
+
+The universal mobile telecommunications system (UMTS) network domain shall be logically and physically divided into security domains in order to protect IP-based control plane signalling. These security domains typically coincide with operator borders.
+
+The interface between different security domains is protected by security gateways (SEGs). The SEGs are responsible for enforcing the security policy of an IP security domain towards other SEGs in the destination IP security domain. All NDS/IP traffic shall pass through a SEG before entering or leaving a security domain. The security policy between security domains is subject to interdomain agreements. This may differ from the security policy within the same security domain, which is optional to implementation and unilaterally decided by the security domain operator. For further details of SEG, see 3G TS 33.210.
+
+## **7.15 Application Function (AF)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.11.
+
+The Application Function (AF) is an element offering applications that require the control of IP bearer resources or the control of flow based bearer charging. The AF is capable of communicating with the PCRF to transfer dynamic QoS-related service information and/or dynamic charging-related service information.
+
+One example of an AF is the PCSCF of the IM CN subsystem.
+
+## **7.16 Multimedia broadcast multicast service (MBMS) specific entities**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.14.
+
+The multimedia broadcast multicast service (MBMS) is a point-to-multipoint service in which data is transmitted from a single source entity to multiple recipients. TS 23.246 contains the technical realization of the service.
+
+### **7.16.1 Broadcast-multicast service centre (BM-SC)**
+
+The broadcast-multicast service centre provides functions for MBMS user service provisioning and delivery. It may serve as an entry point for content provider MBMS transmissions, used to authorise and initiate MBMS bearer services within the PLMN and can be used to schedule and deliver MBMS transmissions.
+
+### **7.16.2 Multimedia broadcast-multicast service gateway (MBMS-GW)**
+
+The MBMS GW provides functions in the EPS for controlling MBMS session initiation/modification/termination by the MBMS user service and for providing delivery of IP multicast datagrams from the SGi-mb reference point to downstream nodes in the MBMS service area with a specified quality of service (QoS).
+
+### **7.16.3 Multi-cell/multicast coordination entity (MCE)**
+
+The MCE is a functional entity providing functions for admission control and allocation of radio resources (RR) by E UTRAN and for MBMS session control. See TS 36.300.
+
+## **7.17 Generic user profile (GUP) server**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.16.
+
+The GUP server is a functional entity providing a single point of access to the generic user profile data of a particular subscriber. The architecture does not specify or limit the physical location of the GUP Server enabling flexibility in the implementations. For further details of the GUP Server, see TS 23.240.
+
+## **7.18 Policy and charging rules function (PCRF)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.17.
+
+The policy and charging rules function (PCRF) acts as a policy decision point for policy and charging control of service data flows/applications and IP bearer resources. The PCRF selects and provides the applicable policy and charging control decision to the PCEF and, if applicable, application detection and control decision to the TDF or PCEF with application detection and control feature.
+
+When the Gxx interface applies, the PCRF maintains the correlation between the GW control session and the IP-CAN session. The PCRF also acts as an information exchange point a relay between BBERF and PCEF to forward event triggers, which can't be transferred directly.
+
+When the Sd interface applies, the PCRF maintains the correlation between the IP-CAN session and the TDF session. Events subscribed by the TDF are reported by the PCRF. PCRF is the policy and charging control element. PCRF functions are described in more detail in TS 23.203
+
+When S9a interface applies, the PCRF provides to the BPCF the UE/H(e)NB local IP address and user datagram protocol (UDP) port number, the QoS rules and PCC rules over S9a interface. PCRF maintains the correlation between the GW control session over S9a interface and the IP-CAN session over Gx interface (if IP-CAN session over Gx interface is available).
+
+When S15 interface applies, the PCRF provides dynamic QoS control policies to the BPCF for the purpose of allocation of QoS resources in the Fixed Broadband Access Network for HNB CS traffic.
+
+PCRF is the policy and charging control element. PCRF functions are described in more detail in TS 23.203.
+
+In non-roaming scenario, there is only a single PCRF in the HPLMN associated with one UE's IP-CAN session.
+
+In a roaming scenario with local breakout of traffic and/or when a Gxx interface applies there are two PCRFs associated with one UE's IP-CAN session:
+
+- H-PCRF that resides within the H-PLMN;
+- V-PCRF that resides within the V-PLMN.
+
+A single logical PCRF entity may be deployed by means of multiple and separately addressable PCRFs in the PLMN. In this case, the PCRF discovery and selection is enabled by Diameter routing agency (DRA).
+
+## **7.19 Policy and charging enforcement function (PCEF)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.18.
+
+The policy and charging enforcement function (PCEF) acts as a policy enforcement point for policy and charging control of IP bearer resources.
+
+This functional entity is located at the gateway (e.g., GGSN in the GPRS case) and in the PDN-GW for EPS).
+
+The functionality of PCEF is described in TS 23.203, TS 23.401 and TS 23.402.
+
+## **7.20 Support of short message service over generic 3GPP Internet protocol access (SMSIP) specific entities**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.19.
+
+Support of short message service over generic 3GPP Internet protocol access (SMSIP) provides 3GPP SMS messaging services across any form of IP connectivity access network. TS 23.204 contains the technical realization of the service.
+
+### **7.20.1 IP-short-message-gateway (IP-SM-GW)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.19.
+
+The IP short message gateway function is used for two functions: to deliver SMS messages over the IP network and to provide interworking between SMS users and Instant Messaging users. The interworking function translates between MAP and SIP signalling to convey messages and responses between the two systems. Both functions are described in TS 23.204.
+
+## **7.21 Subscription profile repository (SPR)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.20.
+
+The SPR logical entity contains all subscriber/subscription related information needed for subscription-based policies and charging control by the PCRF.
+
+## **7.22 Service data flow based credit control function**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.21.
+
+The service data flow based credit control function performs online credit control functions. It is a functional entity embedded in the online charging function (OCF) within the online charging system. (OCS) as specified in TS 32.296.
+
+## **7.23 Bearer binding and event reporting function (BBERF)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.24.
+
+The bearer binding and event reporting function (BBERF) acts as a policy enforcement point for bearer binding, uplink bearer binding verification and event reporting to the PCRF when Gxx applies.
+
+This function entity is located at a GW (e.g., S-GW in the 3GPP access with PMIP based S5/S8 case, HSGW in the HRPD case, A-GW in the non- 3GPP access when PMIP or DSMIPv6 based mobility is used, ePDG with PMIP based S2b or Untrusted S2c case if Gxb\* applies).
+
+The BBERF in the ePDG supports only reporting of the UE's Local IP address and UDP port number to the PCRF. Bearer binding and bearer binding verification functions are not supported.
+
+## **7.24 Traffic detection function (TDF)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.28.
+
+The traffic detection function (TDF) is a functional entity that performs application detection and control.
+
+The functional description of the TDF is in TS 23.203.
+
+## 7.25 Home (e)NodeB entities
+
+### 7.25.1 Home NodeB subsystem (HNS)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.25.1.
+
+The home NodeB subsystem (HNS) consists of a home NodeB (HNB), a home NodeB gateway (HNB-GW) and optionally a local GW (L-GW). The home NodeB subsystem appears as an radio network subsystem (RNS) to the core network and is connected by means of the Iu-CS interface to the MSC and by means of the Iu-PS interface to the SGSN.
+
+A home NodeB is a customer premises equipment (CPE) offering UTRAN coverage, further details can be found in TS 25.467.
+
+A home NodeB gateway is the gateway through which the home NodeB accesses the core network, more details can be found in TS 25.467.
+
+A local GW is a gateway towards the IP networks (e.g., residential/enterprise networks) associated with the home NodeB, more details can be found in TS 23.060. The local GW is co-located with the home NodeB.
+
+### 7.25.2 Home eNodeB subsystem (HeNS)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.25.2.
+
+The home enodeB subsystem (HeNS) consists of a home eNodeB (HeNB), optionally a home eNodeB gateway (HeNB-GW) and optionally a local GW (L-GW). The Home eNodeB Subsystem is connected by means of the S1 interface to the EPC (evolved packet core), more specifically to the MME (mobility management entity) by means of the S1-MME interface and to the serving gateway (S-GW) by means of the S1-U interface.
+
+A home eNodeB is a customer-premises equipment (CPE) offering E-UTRAN coverage, further details can be found in TS 36.300.
+
+A home eNodeB gateway is an optional gateway through which the home enodeB accesses the core network, more details can be found in TS 36.300.
+
+A local GW is a gateway towards the IP networks (e.g., residential/enterprise networks) associated with the home eNodeB, more details can be found in TS 23.401. The Local GW is co-located with the home eNodeB.
+
+### 7.25.3 CSG list server
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.25.3.
+
+The closed subscriber group (CSG) List Server provisions the allowed CSG list and the operator CSG list on the UE using the OTA procedures defined in TS 31.102 or the OMA DM procedures defined in TS 24.285.
+
+The allowed CSG list and the operator CSG list are applicable to both UTRAN and E-UTRAN CSG cells for HNB and HeNB respectively.
+
+### 7.25.4 CSG subscriber server (CSS)
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.25.4.
+
+The CSG subscriber server (CSS) is the entity in the VPLMN storing and managing CSG subscription-related information for roaming UEs to enable VPLMN autonomous CSG roaming (see TS 22.220 ).
+
+The CSS is responsible for holding the following user related information:
+
+- User identification;
+- CSG membership granted to the subscriber during his stay in the VPLMN, i.e., list of CSG IDs and associated expiration dates;
+- User location information: the CSS stores the location information of the subscriber for subsequent update of the CSG subscription information at the MME, SGSN and VLR upon subscription change.
+
+The CSS consists of the following functionalities:
+
+- download of the CSG subscription information upon request from the serving MME, SGSN and VLR, through the S7a, S7d, Ghv and Hv interfaces, to enable roaming subscribers to access to the PS and CS Domain services via CSG cells;
+- service provisioning, including updating the appropriate serving entities (i.e., MME, SGSN and VLR) with modifications of the CSG membership granted to the subscriber.
+
+The organisation of the subscriber data is outlined in TS 23.008. It also indicates which numbers and identifiers specified in TS 23.003 are stored in the CSS.
+
+## **7.26 Specific entities to facilitate communications with packet data networks and applications**
+
+### **7.26.1 Machine type communication-interworking function (MTC-IWF)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.29.1.
+
+The machine type communication-interworking function (MTC-IWF) is a functional entity that acts as an interface between the PLMN and a services capability server (SCS) to provide specific MTC functionalities in the PLMN such as device triggering.
+
+The functional description of the MTC-IWF is in TS 23.682.
+
+### **7.26.2 Machine type communication- authentication, authorization and accounting (MTC-AAA)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 4a.29.2.
+
+The machine type communication-authentication, authorization and accounting (MTC-AAA) is a functional entity that translates an IMSI to the external identifier(s) of the user.
+
+The functional description of the MTC-AAA is in TS 23.682.
+
+# **8 Interfaces and reference points**
+
+## **8.1 LCS interfaces related to the evolved packet core (EPC)**
+
+The following interfaces are not based on MAP in LCS.
+
+### **8.1.1 Interface between GMLC and MME (SLg interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.3.12.
+
+The SLg interface is used by the GMLC to communicate with MMEs. The SLg interface is defined in TS 29.172.
+
+### **8.1.2 Interface between MME and E-SMLC (SLs interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.3.13.
+
+The SLs interface is used to convey LCS messages between the MME and E-SMLC. It is also used for tunnelling positioning protocol messages between the E-SMLC and either E-UTRAN or UE which are transparent to the MME as described in TS 36.305. The SLs interface is defined in TS 29.171.
+
+### **8.1.3 Interface between GMLC and HSS (SLh interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.3.14.
+
+SLh interface between GMLC and HSS. This interface is used by the GMLC to request the address of the visited MME for a particular target UE whose location has been requested. The SLh interface is defined in TS 29.173.
+
+## **8.2 Reference point PDG – Packet data networks (Wi reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 7.6.
+
+This is the reference point between the PDG and a packet data network. It may be an operator external public or private packet data network or an intra operator packet data network, e.g., for provision of IMS services.
+
+## **8.3 Reference point WAG – WLAN access network (Wn reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 7.7.
+
+This is the reference point between the WLAN access gateway (WAG) and the WLAN access network. It is used to force traffic between a WLAN UE and PDG to go through the WAG.
+
+## **8.4 Interfaces internal to, or related to the evolved packet core (EPC)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clauses 6.2.3, 6.4.3 and 6.4.4.
+
+### **8.4.1 Interface between MME and E-UTRAN (S1-MME interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.2.3.1.
+
+Reference point for the control plane protocol between E-UTRAN and MME. This interface is defined in 3G TS 24.301.
+
+### **8.4.2 Interface between S-GW and E-UTRAN (S1-U interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.2.3.2.
+
+Reference point between E-UTRAN and S GW for the per bearer user plane tunnelling. This interface is defined in 3G TS 29.281.
+
+### **8.4.3 Interface between MSC/VLR and MME (SGs interface) for EPC**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.3.4.
+
+The SGs interface is the reference point between the MME and MSC/VLR which is used for the mobility management and paging procedures between EPS and CS domain, and it is based on the Gs interface procedures.
+
+The SGs interface is used to provide fallback for location services (LCS) and call independent supplementary services (SS).
+
+The SGs interface is also used for the delivery of both mobile originating and mobile terminating SMS over EUTRAN in case SMSIP is not used.
+
+The signalling on this interface uses SCTP. The SGs interface is defined in 3G TS 23.272 and TS 29.118.
+
+### **8.4.4 Interface between MSC/VLR and MME (Sv interface) for EPC**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.3.5.
+
+The Sv reference point provides SRVCC support for functions like sending forward relocation message between MME and MSC Server. This interface is specified in 3G TS 29.280.
+
+### **8.4.5 Interface between MME and HSS (S6a interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.1.
+
+This interface is used to exchange the data related to the location of the mobile station and to the management of the subscriber. The main service provided to the mobile subscriber is the capability to transfer packet data within the whole service area. The MME informs the HSS of the location of a mobile station managed by the latter. The HSS sends to the MME all the data needed to support the service to the mobile subscriber. Exchanges of data may occur when the mobile subscriber requires a particular service, when he wants to change some data attached to his subscription or when some parameters of the subscription are modified by administrative means.
+
+Signalling on this interface uses Diameter S6a/S6d Application as specified in 3G TS 29.272.
+
+### **8.4.6 Interface between SGSN and HSS (S6d interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.2.
+
+This interface is used to exchange the data related to the location of the mobile station and to the management of the subscriber. The main service provided to the mobile subscriber is the capability to transfer packet data within the whole service area. The SGSN informs the HSS of the location of a mobile station managed by the latter. The HSS sends to the SGSN all the data needed to support the service to the mobile subscriber. Exchanges of data may occur when the mobile subscriber requires a particular service, when he wants to change some data attached to his subscription or when some parameters of the subscription are modified by administrative means.
+
+Signalling on this interface uses Diameter S6a/S6d Application as specified in 3G TS 29.272.
+
+### **8.4.7 Interface between MME and S-GW (S11 interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.3.
+
+This interface is used to support mobility and bearer management between the MME and S-GW. This interface is specified in 3G TS 29.274.
+
+### **8.4.8 Interface between MME and MME (S10 interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.4.
+
+This interface is used to support user information transfer and MME relocation support between the MMEs. This interface is specified in 3G TS 29.274.
+
+### **8.4.9 Interface between S-GW and PDN-GW (S5 and S8 interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.5.
+
+These interfaces between S-GW and PDN-GW provide support for functions for packet data services towards end users during roaming and non-roaming cases (i.e., S8 is the inter PLMN variant of S5). These interfaces are specified in 3G TS 29.274 and 3G TS 29.281 for GTP, and in 3G TS 29.275 for PMIP.
+
+### **8.4.10 Interface between MME and EIR (S13 interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.6.
+
+This interface is used between MME and equipment identity register (EIR) to exchange data, in order that the EIR can verify the status of the international mobile equipment identity (IMEI) retrieved from the Mobile Station.
+
+Signalling on this interface uses the Diameter S13 Application in 3G TS 29.272.
+
+### **8.4.11 Interface between MME and SGSN (S3 interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.7.
+
+This interface enables user and bearer information exchange for inter 3GPP access network mobility in idle and/or active state. This interface is specified in 3G TS 29.274.
+
+### **8.4.12 Interface between S-GW and SGSN (S4 interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.8.
+
+This interface provides related control and mobility support between GPRS Core and the 3GPP Anchor function of Serving GW. In addition, if Direct Tunnel is not established, it provides the user plane tunnelling. This interface is specified in 3G TS 29.274 and 3G TS 29.281.
+
+### **8.4.13 Interface between S-GW and UTRAN (S12 interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.9.
+
+S12 is a reference point between UTRAN and serving GW for user plane tunnelling when direct tunnel is established. It is based on the Iu-u/Gn-u reference point using the GTP-U protocol as defined between SGSN and UTRAN or respectively between SGSN and GGSN. Usage of S12 is an operator configuration option. This interface is specified in 3G TS 29.274 and 3G TS 29.281.
+
+### **8.4.14 Interface between trusted non-3GPP IP Access and S-GW/P-GW (S2a interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.10.
+
+It provides the user plane with related control and mobility support between trusted non 3GPP IP access and the Gateway. This interface is specified in 3G TS 29.275 and 3G TS 24.304 for PMIP and Client Mobile IPv4 FA mode, respectively.
+
+### **8.4.15 Interface between PDN-GW/S-GW and ePDG (S2b interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.11.
+
+It provides the user plane with related control and mobility support between ePDG and the Gateway. This interface is specified in 3G TS 29.274 and 3G TS 24.281 for GTP, and in 3G TS 29.275 for PIMP.
+
+### **8.4.16 Interface between PDN-GW and UE (S2c interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.12.
+
+It provides the user plane with related control and mobility support between UE and the Gateway. This reference point is implemented over trusted and/or untrusted non-3GPP Access and/or 3GPP access. This interface is specified in 3G TS 24.303.
+
+### **8.4.17 Interface between PDN-GW and 3GPP AAA Server/proxy (S6b interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.13.
+
+It is the reference point between PDN GW and 3GPP AAA server/proxy for mobility related authentication and authorization. This reference point may also be used to retrieve and request storage of mobility parameters, such as the PDN GW Identity. This reference point may also be used to retrieve static QoS profile for a UE for non-3GPP access in case dynamic PCC is not supported. This interface is specified in 3G TS 29.273.
+
+### **8.4.18 Interface between Untrusted non-3GPP IP Access and 3GPP AAA server/proxy (SWa interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.14.
+
+It enables support for the untrusted non-3GPP IP access with the 3GPP AAA server/proxy and transports access authentication, authorization and charging-related information in a secure manner. This interface is specified in 3G TS 29.273.
+
+### **8.4.19 Interface between trusted non-3GPP IP Access and 3GPP AAA server/proxy (STa interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.15.
+
+It connects the trusted non-3GPP IP access with the 3GPP AAA server/proxy and transports access authentication, authorization, mobility parameters and charging-related information in a secure manner. This interface is specified in 3G TS 29.273.
+
+### **8.4.20 Interface between 3GPP AAA server and 3GPP AAA proxy (SWd interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.16.
+
+It connects the 3GPP AAA proxy, possibly via intermediate networks, to the 3GPP AAA server. This interface is specified in 3G TS 29.273.
+
+### **8.4.21 Interface between ePDG and 3GPP AAA server/proxy (SWm interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.17.
+
+This reference point is located between 3GPP AAA server/proxy and ePDG and is used for AAA signalling (transport of mobility parameters, tunnel authentication and authorization data). This reference point also includes the MAG-AAA interface functionality and Mobile IPv6 NAS-AAA interface functionality. This interface is specified in 3G TS 29.273.
+
+### **8.4.22 Interface between ePDG and untrusted non-3GPP access (SWn interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.18.
+
+This is the reference point between the untrusted non-3GPP IP Access and the ePDG. Traffic on this interface for a UE-initiated tunnel has to be forced towards ePDG. This interface is specified in 3G TS 29.273.
+
+### **8.4.23 Interface between ePDG and UE (SWu interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.19.
+
+This is the reference point between the UE and the ePDG and supports handling of IPSec tunnels. The functionality of SWu includes UE-initiated tunnel establishment, user data packet transmission within the IPSec tunnel and tear down of the tunnel and support for fast update of IPSec tunnels during handover between two untrusted non-3GPP IP accesses. This interface is specified in 3G TS 24.302.
+
+### **8.4.24 Interface between HSS and 3GPP AAA server (SWx interface)**
+
+The text in this clause is based on the text in reference [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.20.
+
+This reference point is located between 3GPP AAA server and HSS and is used for transport of authentication data. This interface is specified in 3G TS 29.273.
+
+### **8.4.25 Interface between UE and ANDSF (S14 interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.21.
+
+This reference point is between UE and ANDSF for direct queries via pull mechanism. It enables dynamic provision of information to the UE for Network discovery and selection procedures related to non-3GPP accesses. Push and/or combination of pull-push may be supported as well. This interface is specified in 3G TS 24.302.
+
+### **8.4.26 Reference point between HRDP AN and MME (S101 reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.22.
+
+The S101 interface supports procedures for pre-registration, session maintenance and active handovers between EUTRAN and HRPD networks. This is based on tunnelling over S101 signalling of one technology while the UE is in the other technology as specified in TS 23.402. The HRPD air interface messages tunnelled over S101 in EUTRAN to HRPD mobility are defined in 3GPP2 C.S0087 0.
+
+### **8.4.27 Reference point between 3GPP2 1xCS IWS and MME (S102 reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS3GA23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.23.
+
+The S102 reference point provides a tunnel between MME and 3GPP2 1xCS IWS to relay 3GPP2 1xCS signalling messages in order to support SRVCC as specified in TS 23.216 and CS fallback as specified in TS 23.272. 1x CS signalling messages are those messages that are defined for A21 interface as described in 3GPP2 A.S0008-C.
+
+In case of CS fallback to 1x CS network as specified in TS 23.272, S102 tunnel redirection procedure is used when the UE perform tracking area update with MME change (as specified in TS 23.402 in case of S101 tunnel redirection) while the UE is registered with the 1xRTT CS domain and the S102 session exists between the MME and the 1xCS IWS.
+
+### **8.4.28 Interface between HSGW and S-GW (S103 interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.24.
+
+The S103 interface between the serving GW and HRPD PDSN HSGW supports the forwarding of DL data during mobility from E-UTRAN to HRPD as specified in TS 23.402. Signalling procedures on the S101 interface are used to set up tunnels on the S103 interface.
+
+### **8.4.29 Reference point between UE and CSG list server (Uh reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.25.
+
+This reference point is used to provision the allowed CSG list and the operator CSG list subscription information to the mobile station via OMA DM or OTA. This interface is specified in TS 24.285 for OMA DM and in TS 31.102 for OTA.
+
+### **8.4.30 Reference point PDN-GW – packet data networks (SGi reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 7.2a.
+
+This is the reference point between the PDN-GW and a packet data network. It may be an operator external public or private packet data network or an intra operator packet data network, e.g., for provision of IMS services. For more details see 3G TS 29.061.
+
+### **8.4.31 Reference Point between the CSS and the S4-SGSN (S7d Reference Point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.26.
+
+This reference point is used to transfer to the S4-SGSN the CSG subscription information stored in the VPLMN for roaming UEs.
+
+Signalling on this interface uses Diameter S7d Application as specified in TS 29.272.
+
+### **8.4.32 Reference point between the CSS and the MME (S7a reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.27.
+
+This reference point is used to transfer to the MME the CSG subscription information stored in the VPLMN for roaming UEs.
+
+Signalling on this interface uses Diameter S7a Application as specified in TS 29.272.
+
+### **8.4.33 Reference point between the MME and the SMS-GMSC/SMS-IWMSC/SMS router (SGd reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.28.
+
+This reference point is used to transfer short messages between the MME and SMS-GMSC, SMS-IWMSC or SMS router.
+
+Signalling on this interface uses Diameter SGd Application as specified in TS 29.338.
+
+### **8.4.34 Reference point between the HSS and the SMS-GMSC/SMS-IWMSC/SMS router (S6c reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6.4.4.29.
+
+This reference point is used to interrogate the HSS of the required subscriber to obtain routing information for a short message directed to that subscriber.
+
+Signalling on this interface uses Diameter S6c Application as specified in TS 29.336.
+
+## **8.5 Reference points for 3GPP/WLAN interworking**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.9.
+
+NOTE – With the introduction of evolved packet core system, the 3GPP AAA server and 3GPP AAA Proxy provide a set of different and additional functions as specified in the EPC specific section of this specification.
+
+### **8.5.1 Interface reference point 3GPP AAA server – HLR (D'/Gr' reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.9.1.
+
+This is the reference point between the 3GPP AAA server and the HLR up to and including Rel4 and the HSS in later releases. The functionality of this reference point is similar to that of the Wx reference point. For more information see TS 23.234.
+
+### **8.5.2 Reference point WLAN access network – 3GPP AAA proxy/server (Wa reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.9.2.
+
+This is the reference point between the WLAN access network and 3GPP AAA proxy or server. The AAA protocol on this reference point is used to transport authentication, authorization and charging data.
+
+### **8.5.3 Reference point 3GPP AAA server – 3GPP AAA proxy (Wd reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.9.3.
+
+This is the reference point between the 3GPP AAA server and proxy. The purpose of the protocols crossing this reference point is to transport authentication, authorization and related information. For more information see TS 23.234.
+
+### **8.5.4 Reference point 3GPP AAA server/proxy – WAG (Wg reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.9.4.
+
+This is the reference point between the 3GPP AAA server/proxy and WAG. It is used to provide information needed by the WAG to perform policy enforcement functions for authorised users and to transport per-tunnel based charging information from the WAG to the AAA proxy in roaming scenarios.
+
+### **8.5.5 Reference point PDG – packet data networks (Wi reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.9.5.
+
+This is the reference point between the PDG and a packet data network. It may be an operator external public or private packet data network or an intra operator packet data network, e.g., for provision of IMS services.
+
+### **8.5.6 Reference point 3GPP AAA server/proxy – PDG (Wm reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.9.6.
+
+This is the reference point between the 3GPP AAA server/proxy and PDG. The functionality of this reference point is to enable:
+
+- The 3GPP AAA server/proxy to retrieve tunnelling attributes and WLAN UE's IP configuration parameters from/via packet data gateway
+- Carrying messages for service authentication and authorization
+- Carrying authentication data for the purpose of tunnel establishment, tunnel data authentication and encryption.
+
+For more information see TS 23.234.
+
+### **8.5.7 Reference point WAG – WLAN access network (Wn reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.9.7.
+
+This is the reference point between the WAG and the WLAN access network. It is used to force traffic between a WLAN UE and PDG to go through the WAG.
+
+### **8.5.8 Reference point WAG – PDG (Wp reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.9.8.
+
+This is the reference point between WAG and PDG. It is used to transport the Wu reference point protocol data packets.
+
+### **8.5.9 Reference point WLAN UE – PDG (Wu reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.9.9.
+
+This is the reference point between the 3GPP WLAN UE and PDG. The functionality of this reference point is to establish a tunnel between WLAN UE and PDG and to exchange data packets between WLAN UE and PDG.
+
+### **8.5.10 Reference point HA – external packet data network (HGi reference point)**
+
+The following text is based on the text in references [ETSI TS 123 327], [TTC TS-3GA-23.327], [ATIS 3GPP 23.327] and [TTA TTAT.3G-23.327], clause 5.5.
+
+This reference point defines the interface from the HA to external PDN.
+
+### **8.5.11 Reference point 3GPP AAA server – HSS (Wx reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.9.11.
+
+This is the reference point between the 3GPP AAA server and HSS. The functionality of this reference point is to enable:
+
+- Retrieval of authentication vectors;
+- Retrieval of WLAN access-related subscriber information (profile);
+- Registration of the 3GPP AAA server of an authorised WLAN user in the HSS;
+- Indication of change of subscriber profile.
+- Retrieval of online charging / offline charging function addresses from HSS.
+- Retrieval of service related information.
+
+For more information see TS 23.234.
+
+### **8.5.12 Reference point 3GPP AAA server – SLF (Dw reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.9.12.
+
+This reference point is between the 3GPP AAA server and the SLF. The prime purpose of the protocol(s) crossing this reference point is to enable the 3GPP AAA server to find the address of the HSS which holds the subscriber data for a given user identity in a configuration with multiple separately addressable HSSes.
+
+### **8.5.13 Reference point HA – UE (H1 reference point)**
+
+The following text is based on the text in references [ETSI TS 123 327], [TTC TS-3GA-23.327], [ATIS 3GPP 23.327] and [TTA TTAT.3G-23.327], clause 5.5.
+
+This is the reference point for signalling and user data transfer between UE and HA.
+
+NOTE – H1 may be transported over IP connectivity provided by IWLAN or 3GPP access system.
+
+### **8.5.14 Reference point HA – 3GPP AAA architecture (H2 reference point)**
+
+The following text is based on the text in references [ETSI TS 123 327], [TTC TS-3GA-23.327], [ATIS 3GPP 23.327] and [TTA TTAT.3G-23.327], clause 5.5.
+
+This reference point defines the interface between HA and 3GPP AAA infrastructure (3GPP AAA server or 3GPP AAA proxy) and is used to transport authentication, authorization and charging-related information in a secure manner.
+
+### **8.5.15 Reference point 3GPP AAA server – online charging system (Wo reference point)**
+
+The following text is based on the text in references [ETSI TS 123 234], [TTC TS-3GA-23.234], [ATIS 3GPP 23.234] and [TTA TTAT.3G-23.234], clause 6.3.4.
+
+The Wo reference point is used by a 3GPP AAA server to communicate with 3GPP online charging system (OCS). The prime purpose of the protocol(s) crossing this reference point is to transport online charging related information so as to perform credit control for the online charged subscriber.
+
+### **8.5.16 Reference point 3GPP AAA server – offline charging system (Wf reference point)**
+
+The following text is based on the text in references [ETSI TS 123 234], [TTC TS-3GA-23.234], [ATIS 3GPP 23.234] and [TTA TTAT.3G-23.234], clause 6.3.5.
+
+The Wf reference point is located between 3GPP AAA server/proxy and 3GPP offline charging system. The prime purpose of the protocols crossing this reference point is to transport/forward offline charging information towards 3GPP operator's offline charging system located in the visited network or home network where the subscriber is residing.
+
+The information forwarded to the offline charging system is typically used for:
+
+- Generating bills for offline charged subscribers by the subscribers' home operator.
+- Calculation of inter-operator accounting from all roaming users. This inter operator accounting is used to settle the payments between visited and home network operator and/or between home/visited network and WLAN.
+
+The functionality of the reference point is to transport:
+
+- WLAN access-related charging data per WLAN user.
+
+### **8.5.17 Reference point 3GPP AAA server – SLF (Dw reference point)**
+
+The following text is based on the text in references [ETSI TS 123 234], [TTC TS-3GA-23.234], [ATIS 3GPP 23.234] and [TTA TTAT.3G-23.234], clause 6.3.14.
+
+This reference point is between the 3GPP AAA server and the SLF. The prime purpose of the protocol(s) crossing this reference point is to enable the 3GPP AAA server to find the address of the HSS which holds the subscriber data for a given user identity in a configuration with multiple separately addressable HSS's.
+
+### **8.5.18 Reference point PDG – online charging system (Wy reference point)**
+
+The following text is based on the text in references [ETSI TS 123 234], [TTC TS-3GA-23.234], [ATIS 3GPP 23.234] and [TTA TTAT.3G-23.234], clause 6.3.15.
+
+The Wy reference point is used by a PDG to communicate with an online charging system (OCS). The purpose of the protocol(s) crossing this reference point is to transport online charging related information about WLAN 3GPP IP Access so as to perform credit control for the online charged subscriber.
+
+### **8.5.19 Reference point PDG – offline charging system (Wz reference point)**
+
+The following text is based on the text in references [ETSI TS 123 234], [TTC TS-3GA-23.234], [ATIS 3GPP 23.234] and [TTA TTAT.3G-23.234], clause 6.3.16.
+
+The Wz reference point is used by a PDG to communicate with an offline charging system. The purpose of the protocol(s) crossing this reference point is to transport offline charging related information about WLAN 3GPP IP Access.
+
+## **8.6 MBMS specific reference points for EPS**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.11.
+
+### **8.6.1 Reference point MBMS GW – BM-SC (SGmb reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.11.1.
+
+This reference point is used to exchange signalling between MBMS GW and BM-SC. This represents the network side boundary of the MBMS bearer service from a control plane perspective.
+
+This includes MBMS bearer service specific signalling. The details for this reference point are described in TS 23.246 and TS 29.061.
+
+### **8.6.2 Reference point MBMS GW – BM-SC (SGi-mb reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.11.2.
+
+This reference point is used between MBMS GW and BM-SC for MBMS data delivery. The details for this reference point are described in TS 23.246 and TS 29.061.
+
+### **8.6.3 Reference point MBMS GW – MME (Sm reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.11.3.
+
+This reference point is used to exchange signalling between MBMS GW and MME for MBMS session control. The details for this reference point are described in TS 23.246 and TS 29.274.
+
+### **8.6.4 Reference point MBMS GW – SGSN (Sn reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.11.4.
+
+This reference point is used to exchange signalling between MBMS GW and S4-SGSN for MBMS Session Control and for MBMS data delivery in point-to-point mode. The details for this reference point are described in TS 23.246 and TS 29.274.
+
+### **8.6.5 Reference point MBMS GW – E-UTRAN/UTRAN (M1 reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.11.5.
+
+This reference point is used between MBMS GW and E-UTRAN/UTRAN for MBMS data delivery using IP multicast. The details for this reference point are described in TS 23.246, TS 29.281 and TS 36.445.
+
+### **8.6.6 Reference point MME – MCE (M3 reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.11.6.
+
+This reference point is used to exchange signalling between MME and MCE for MBMS Session Control. The details for this reference point are described in TS 23.246, TS 36.300 and TS 36.444.
+
+### **8.6.7 Reference point MCE – eNodeB (M2 reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.11.7.
+
+This reference point is used to exchange signalling between MCE and eNodeB for MBMS Session Control. The details for this reference point are described in TS 23.246, TS 36.300 and TS 36.443.
+
+## **8.7 Reference points for 3GPP generic user profile (GUP)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.12.
+
+### **8.7.1 Reference point GUP server – Applications (Rg reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS3GA23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.12.1.
+
+The Rg reference point resides between the GUP server and the applications.
+
+The Rg reference point allows applications to create, read, modify and delete any user profile data using the harmonized access interface. The GUP server locates the data repositories responsible of the storage of the requested profile component(s).
+
+The details of the Rg reference point are described in TS 23.240.
+
+### **8.7.2 Reference point GUP server – HSS and applications – HSS (Rp reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS3GA23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.12.2.
+
+The Rp reference point resides between the GUP server and the HSS, and between the applications and the HSS.
+
+The Rp reference point enables the GUP server and the applications to access GUP data repositories. The HSS is one of the GUP data repositories. It stores the IM CN subsystem user related data.
+
+The details of the Rp reference point are described in TS 23.240.
+
+## **8.8 Reference points for policy and charging control**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.13.
+
+### **8.8.1 Reference point PCEF – PCRF/H-PCRF/V-PCRF (Gx reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.13.1.
+
+This interface provides transfer of policy and charging rules from PCRF to Policy and Charging Enforcement Function Point (PCEF) in the GW (e.g., GGSN, PDN GW). This interface is specified in TS 29.212.
+
+### **8.8.2 Reference point PCRF – Application function (Rx reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.13.2.
+
+This interface allows for dynamic QoS and charging-related service information to be exchanged between the policy and charging rules function (PCRF) and the application function (AF). This information is used by the PCRF for the control of service data flows and IP bearer resources. For more information see TS 23.203.
+
+### **8.8.3 Reference point SPR – PCRF (Sp reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.13.3.
+
+This interface allows for the PCRF to request subscription information from the SPR and the SPR to notify the PCRF when the subscription information has changed if the PCRF has requested such notifications. The details associated with the Sp reference point are not specified in this Release.
+
+### **8.8.4 Reference point OCS – PCEF (Gy reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.13.4.
+
+This interface allows for the online charging based on the Diameter credit control application between the online charging system (OCS) and the PCEF. For more information see TS 32.251 and RFC 4006.
+
+### **8.8.5 Reference point OFCS – PCEF (Gz reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.13.5.
+
+This interface allows for the offline charging based on the charging record data transfer between the offline charging system (OFCS) and the PCEF. For more information see TS 32.295.
+
+### **8.8.6 Reference point trusted non-3GPP IP access and PCRF/VPCRF (Gxa reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.13.6.
+
+This interface provides transfer of (QoS) policy information from PCRF to the trusted non-3GPP accesses. This interface is specified in TS 29.212.
+
+### **8.8.7 Reference point between S-GW and PCRF/VPCRF (Gxc interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.13.8.
+
+This interface provides transfer of (QoS) policy information from PCRF to the serving gateway, Gxc is used only in the case of PMIP-based S5/S8. This interface is specified in TS 29.212.
+
+### **8.8.8 Reference point PCRF/VPCRF – BBERF (Gxx reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.13.9.
+
+This interface allows for a PCRF to have a dynamic control over the bearer binding and event report function (BBERF) behaviour. For more information see TS 23.402 and TS 23.203. This interface is specified in TS 29.213.
+
+### **8.8.9 Reference point HPCRF – VPCRF (S9 interface)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.13.10.
+
+This interface provides transfer of policy and charging rules (in case of local breakout of traffic) and/or (QoS) policy information (when Gxx interface applies) between the Home PCRF and the Visited PCRF in order to support PCC roaming related functions. This interface is specified in TS 29.215.
+
+### **8.8.10 Reference point UDR – PCRF (Ud reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.13.11.
+
+This interface allows for the PCRF, acting as an UDC application frontend as defined in TS 23.335, to request subscription information from the UDR and the UDR to notify the PCRF when the subscription information has changed if the PCRF has requested such notifications. For details regarding the Ud reference point see TS 23.335 and TS 29.335.
+
+### **8.8.11 Reference point TDF – PCRF/H-PCRF/V-PCRF (Sd reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.13.12.
+
+The Sd reference point enables a PCRF to have dynamic control over the application detection and control behaviour at a TDF. The Sd reference point is specified in TS 29.212.
+
+### **8.8.12 Reference Point OCS – PCRF/H-PCRF (Sy reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.13.13.
+
+The Sy reference point enables transfer of information relating to subscriber spending from OCS to PCRF. The Sy reference point is specified in TS 29.219.
+
+### **8.8.13 Reference Point HNB GW – PCRF/V-PCRF (S15 reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.13.14.
+
+This reference point supports the initiation, modification and termination of sessions between the HNB GW and PCRF to support CS sessions. It triggers the PCRF to request allocation of resources in the fixed broadband access network for HNB CS calls. This interface is specified in TS 29.212.
+
+S15 is only applicable to the interworking with fixed broadband access network.
+
+### **8.8.14 Reference point BPCF – PCRF/v-PCRF (S9a reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.13.15.
+
+This interface supports the transfer of (QoS) policy information from PCRF to BPCF of broadband access network. This interface is specified in TS 29.215.
+
+S9a is only applicable to the interworking with fixed broadband access network.
+
+### **8.8.15 Reference point ePDG and PCRF/VPCRF (Gxb\* Reference Point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.13.7a.
+
+The reference point transports access information from ePDG to PCRF/vPCRF for WLAN UEs such as the UE local IP address and the UDP port number. This interface is specified in TS 29.212.
+
+Gxb\* is only applicable to the interworking with fixed broadband access network.
+
+## **8.9 Reference point IP-SM-GW – HSS (J reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.14.1.
+
+This reference point is used to exchange signalling between IP-SM-GW and the HSS for SMSIP delivery. The details for this reference point are described in TS 23.204.
+
+## **8.10 Reference point application front ends – UDR (Ud reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.15.1.
+
+This reference point is used to exchange user between application front ends and the UDR. The details for this reference point are described in TS 23.335 and TS 29.335.
+
+## **8.11 Specific reference points for facilitating communications with packet data networks and applications**
+
+### **8.11.1 Reference point MTC-IWF – SCS (Tsp reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.16.1.
+
+This reference point is used between the MTC-IWF and the services capability server (SCS) to invoke specific functionalities in the PLMN such as device triggering. The details for this reference point are described in TS 23.682 and TS 29.368.
+
+This interface is a PLMN internal interface if the SCS is controlled by the operator.
+
+Signalling on this interface uses Diameter Tsp Application as specified in TS 29.368.
+
+NOTE – See clause 7.8 when the SCS is not controlled by the operator.
+
+### **8.11.2 Reference point MTC-IWF – HSS/HLR (S6m reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.16.2.
+
+This reference point is used between the MTC-IWF and the HSS/HLR to authorize a certain SCS to request a specific service (e.g., device triggering), and to retrieve subscription information and routing information (i.e., serving SGSN/MME/MSC identities) from the HSS/HLR.
+
+The details for this reference point are described in TS 23.682 and TS 29.336.
+
+Signalling on this interface uses Diameter S6m Application as specified in TS 29.336.
+
+### **8.11.3 Reference point MTC-AAA – HSS/HLR (S6n reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.16.3.
+
+This reference point is used between the MTC-AAA and the HSS/HLR to translate an IMSI to external identifier(s) of the user.
+
+The details for this reference point are described in TS 23.682 and TS 29.336.
+
+Signalling on this interface uses Diameter S6n Application as specified in TS 29.336.
+
+### **8.11.4 Reference point MTC-IWF – SMS-SC (T4 reference point)**
+
+The text in this clause is based on the text in references [ETSI TS 123 002], [TTC TS-3GA-23.002], [ATIS 3GPP 23.002] and [TTA TTAT.3G-23.002], clause 6a.16.4.
+
+This reference point is used between the MTC-IWF and the SMS-SC to transfer device trigger to the SMS-SC inside the HPLMN.
+
+The details for this reference point are described in TS 23.682 and TS 29.337.
+
+Signalling on this interface uses Diameter T4 Application as specified in TS 29.337.
+
+# **9 Technical specifications structure**
+
+This clause provides an overview of the specifications for this IMT-advanced family member based on LTE-advanced evolved packet core (EPC) network. Details for these specifications may be found in clause 10.
+
+The following text describes the numbering scheme for the specifications and reports for the 3GPP 4th generation mobile system.
+
+Specifications for Release 11 of the fourth generation mobile system are identified by the "ab.cde" numbering scheme.
+
+The following series titles and descriptions are used for guidance only and may be further developed over time.
+
+The specification series are:
+
+| | |
+|-----------|------------------------------------------------------------------------|
+| 21-series | Requirements |
+| 22-series | Service aspects ("stage 1") |
+| 23-series | Technical realisation ("stage 2") |
+| 24-series | Signalling protocols ("stage 3") – user equipment to network |
+| 26-series | CODECs |
+| 27-series | Data |
+| 29-series | Signalling protocols ("stage 3") – intra-fixed-network |
+| 31-series | Subscriber identity module (SIM / USIM), IC Cards. Test specifications |
+| 32-series | OAM&P and Charging |
+| 33-series | Security aspects |
+| 35-series | Security algorithms |
+
+NOTE 1 – Technical Specifications in this series are not included in the scope for this Recommendation. They are described in [ITU-R M.2012-2].
+
+NOTE 2 – Technical Specifications in these series are not included in the scope for this Recommendation.
+
+# 10 Technical specifications
+
+The working procedures within the 3GPP allow a continuous improvement of their specifications by means of a change request procedure. The change requests are reviewed by each 3GPP working group and provided for approval to the quarterly 3GPP TSG plenary meetings. Therefore, the SDO standards/specifications can be updated after each 3GPP TSG plenary meetings. In this context, it is recommended to the reader to retrieve the latest version of the SDO standards/specifications from the location indicated within the template.
+
+NOTE – The format of the "issued date" column in clause 10 is **yyyy-mm-dd** (for year-month-day) or Month-yyyy, respectively, in case the day of month has not been specified.
+
+## 10.1 21-series, Requirements
+
+### 10.1.1 TS 21.111 USIM and IC card requirements
+
+This document defines the requirements of the USIM (universal subscriber identity module) and the IC card for 3G universal IC card (UICC). These are derived from the service and security requirements defined in 3G TS 22.100 and 3G TS 22.101. The USIM is a 3G application on an IC card. It inter-operates with a 3G terminal and provides access to 3G services. This document is intended to serve as a basis for the detailed specification of the USIM and the UICC, and the interface to the 3G terminal.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-21.111 | 11.0.1 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/21/A21111-b01.pdf |
+| ETSI | TS 121 111 | 11.0.1 | Published | 2013-01-10 | http://www.etsi.org/deliver/etsi_ts/121100_121199/121111/11.00.01_60/ts_121111v110001p.pdf |
+| ATIS | ATIS.3GPP.21.111V1101-2014 | 11.0.1 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-21.111(R11-11.0.1) | 11.0.1 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-21.111(R11-11.0.1) |
+
+## 10.2 22-series, Service aspects
+
+### 10.2.1 TS 22.011 Service accessibility
+
+The purpose of this technical specification is to describe the service access procedures as presented to the user.
+
+Definitions and procedures are provided in this technical specification for international roaming, national roaming and regionally provided service. These are mandatory in relation to the technical realization of the mobile station (UE).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 122 011 | 11.3.0 | Published | 2013-04-11 | http://www.etsi.org/deliver/etsi_ts/122000_122099/122011/11.03.00_60/ts_122011v110300p.pdf |
+| ATIS | ATIS.3GPP.22.011V1130-2014 | 11.3.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.011(R11-11.3.0) | 11.3.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.011(R11-11.3.0) |
+| TTC | TS-3GA-22.011(Rel11)v11.3.0 | 11.3.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-22.011(Rel11)v11.3.0.pdf |
+
+### 10.2.2 TS 22.016 International mobile station equipment identities (IMEI)
+
+The document defines the principal purpose and use of international mobile station equipment identities (IMEI).
+
+TS 23.003 describes the technical manner of numbering, addressing and identification.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.016 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22016-b00.pdf |
+| ETSI | TS 122 016 | 11.0.0 | Published | 2012-10-23 | http://www.etsi.org/deliver/etsi_ts/122000_122099/122016/11.00.00_60/ts_122016v110000p.pdf |
+| ATIS | ATIS.3GPP.22.016V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.016(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.016(R11-11.0.0) |
+
+### 10.2.3 TS 22.022 Personalization of mobile equipment (ME); Mobile functionality specification
+
+The document provides functional specifications of five features to personalize mobile equipment (ME) for GSM and 3G systems. These features are called:
+
+- Network personalization;
+- Network subset personalization;
+- Service provider (SP) personalization;
+- Corporate personalization;
+- SIM/USIM personalization (SIM for GSM systems or USIM for 3G systems).
+
+The document specifies requirements for MEs that provide these personalization features.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.022 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22022-b00.pdf |
+| ETSI | TS 122 022 | 11.0.0 | Published | 2012-10-23 | http://www.etsi.org/deliver/etsi_ts/122000_122099/122022/11.00.00_60/ts_122022v110000p.pdf |
+| ATIS | ATIS.3GPP.22.022V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.022(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.022(R11-11.0.0) |
+
+### 10.2.4 TS 22.024 Description of charge advice information (CAI)
+
+The charging supplementary service (SS) is described in TS 22.086. These services are designed to supply to a mobile user sufficient information to allow a realtime estimate to be made of the bill that will eventually be levied in the home PLMN on the mobile station (MS) subscriber.
+
+In the case of certain MS uses, for example a mobile payphone, this estimate could be subject to further processing (e.g., to present the charges in currency, rather than units, this may include an additional mark up). This additional processing is not described in this document in order to avoid constraining the evolution of the MS product in this area.
+
+This document gives an overall view of how this supplementary service shall operate both in the PLMN and within the MS. Text given in this document is required to define functionality and is not intended to constrain implementation.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 122 024 | 11.0.0 | Published | 2012-10-23 | http://www.etsi.org/deliver/etsi_ts/122000_122099/122024/11.00.00_60/ts_122024v110000p.pdf |
+| ATIS | ATIS.3GPP.22.024V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.024(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.024(R11-11.0.0) |
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTC | TS-3GA-22.024(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-22.024(Rel11)v11.0.0.pdf |
+
+### 10.2.5 TS 22.030 Man-machine interface (MMI) of the user equipment (UE)
+
+The document defines the requirements for and gives guidelines on the MMI on the user equipment (UE). This includes the requirements of the user procedures for call control and supplementary service control, the requirements on the physical input media and the output, such as indications and displayed information.
+
+This document includes requirements only to UE connected to CS Domain. See TS 22.101 for overall service principles and TS 22.001 for circuit telecommunication services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.030 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22030-b00.pdf |
+| ETSI | TS 122 030 | 11.0.0 | Published | 2012-10-23 | http://www.etsi.org/deliver/etsi_ts/122000_122099/122030/11.00.00_60/ts_122030v110000p.pdf |
+| ATIS | ATIS.3GPP.22.030V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.030(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatdesc.jsp?stdno=TTAT.3G-22.030(R11-11.0.0) |
+
+### 10.2.6 TS 22.031 Fraud information gathering system (FIGS); Service description; Stage 1
+
+This technical specification specifies the Stage 1 description of the fraud information gathering system (FIGS) feature which provides the means for the HPLMN to monitor the activities of its subscribers in a VPLMN.
+
+The purpose of this network feature is to enable the HPLMN to monitor the activities of its subscribers while they are roaming. The VPLMN collects information about a defined set of activities on monitored subscribers and sends this information back to the HPLMN. This enables the HPLMN to clear certain types of calls and so stop fraudulent use of the GSM system.
+
+This specification enables service providers/network operators to use FIGS, and service limitation controls such as operator determined barring (ODB) and immediate service termination (IST), to limit their financial exposure to subscribers producing large unpaid bills.
+
+HPLMNs may also choose to monitor the activities of its subscribers within the HPLMN.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.031 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22031-b00.pdf |
+| ETSI | TS 122 031 | 11.0.0 | Published | 2012-10-23 | http://www.etsi.org/deliver/etsi_ts/122000_122099/122031/11.00.00_60/ts_122031v110000p.pdf |
+| ATIS | ATIS.3GPP.22.031V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.031(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.031(R11-11.0.0) |
+
+### 10.2.7 TS 22.032 Immediate service termination (IST); Service description; Stage 1
+
+The document specifies the Stage 1 description of the immediate service termination (IST) service which provides the means for the HPLMN to terminate all the activities of an HPLMN subscriber in a VPLMN.
+
+The purpose of this network feature is to enable the HPLMN to control the activities of its subscribers, particularly while they are roaming. If the HPLMN decides (based upon information received via fraud information gathering system (FIGS) or other systems) that a roaming subscriber is behaving in a fraudulent or suspicious manner, the HPLMN can terminate all activities of the subscriber, including calls (including transferred and diverted calls) that are in progress.
+
+This procedure can also be used to terminate all the activities of a subscriber when the subscription has ended.
+
+The primary aim is to enable service providers/network operators to use IST to reduce the amount of money that they lose because of roaming fraud.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.032 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22032-b00.pdf |
+| ETSI | TS 122 032 | 11.0.0 | Published | 2012-10-23 | http://www.etsi.org/deliver/etsi_ts/122000_122099/122032/11.00.00_60/ts_122032v110000p.pdf |
+| ATIS | ATIS.3GPP.22.032V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.032(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.032(R11-11.0.0) |
+
+### 10.2.8 TS 22.038 USIM application toolkit (USAT); Service description; Stage 1
+
+This technical specification defines the Stage 1 description of the USIM application toolkit (USAT). Stage 1 is an overall service description, primarily from the subscriber's and serving environment's points of view, and does not deal with the details of the human interface itself.
+
+It includes information applicable to network operators, serving environments and terminal, switch and database manufacturers.
+
+The technical specification also contains the core requirements for a USIM application toolkit that are sufficient to provide a complete service.
+
+It is highly desirable, however, that technical solutions for a USIM application toolkit are sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in this technical specification may implement requirements that are considered outside the scope of this technical specification. This additional functionality may be on a network-wide basis, nationwide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service.
+
+As indicated in Figure 10.2.8-1, the scope of this technical specification encompasses the USAT functionality in the UE (comprising USIM and ME) and the interaction with the PLMN environment. The USAT server is not necessarily a separate entity as shown in the figure; nodes providing USAT services may also exist within the PLMN. The functionalities of the USAT servers (such as charging aspects, security level classification, etc.) are not covered by this specification.
+
+
+
+Diagram illustrating the scope of Technical Specification 22.038. It shows a Mobile Equipment (ME) connected to a PLMN cloud. The ME contains a SIM/USIM card, which is further divided into GSM/UMTS and SAT/USAT functionality. The SAT/USAT functionality is shown interacting with the PLMN and a SAT/USAT server(s). A label 'Scope of this TS' points to the ME and SIM/USIM components. The diagram is labeled Q.1743(16)\_F10.2.8-1.
+
+**Figure 10.2.8-1 – Scope of Technical Specification 22.038**
+
+The requirements are considered to be applicable to both GSM and UMTS systems.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.038 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22038-b00.pdf |
+| ETSI | TS 122 038 | 11.0.0 | Published | 2012-10-23 | http://www.etsi.org/deliver/etsi_ts/122000_122099/122038/11.00.00_60/ts_122038v110000p.pdf |
+| ATIS | ATIS.3GPP.22.038V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.038(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.038(R11-11.0.0) |
+
+### 10.2.9 TS 22.041 Operator determined barring (ODB)
+
+The document describes the network feature operator determined barring (ODB).
+
+This allows the network operator or service provider to regulate, by means of an exceptional procedure, access by the subscribers to services (both circuit and packet oriented), by the barring of certain categories of outgoing or incoming calls/packet oriented services or of roaming. ODB shall take effect immediately and shall terminate ongoing calls and bar future calls/packet oriented services.
+
+The purpose of this network feature is to be able to limit the service provider's financial exposure to new subscribers, or to those who have not promptly paid their bills. It may only be applied to the service provider's own subscribers.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 122 041 | 11.3.0 | Published | 2013-10-01 | http://www.etsi.org/deliver/etsi_ts/122000_122099/122041/11.03.00_60/ts_122041v110300p.pdf |
+| ATIS | ATIS.3GPP.22.041V1120-2014 | 11.2.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.041(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.041(R11-11.2.0) |
+| TTC | TS-3GA-22.041(Re11)v11.3.0 | 11.3.0 | TTC Approved | 2013-11-22 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-22.041(Re11)v11.3.0.pdf |
+
+### 10.2.10 TS 22.042 Network identity and time zone (NITZ); Service description; Stage 1
+
+The document describes the feature network identity and time zone (NITZ).
+
+This feature provides the means for serving PLMNs to transfer current identity, time, daylight saving time and the local time zone to mobile stations (MS)s, and for the MSs to store and use this information. This enhances roaming by permitting accurate indication of PLMN identities that are either newer than the mobile equipment (ME) or have changed their name since the ME was sold. Additionally, time, daylight saving time, and time zone information can be utilized by MEs as desired.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 122 042 | 11.0.0 | Published | 2012-10-23 | http://www.etsi.org/deliver/etsi_ts/122000_122099/122042/11.00.00_60/ts_122042v110000p.pdf |
+| ATIS | ATIS.3GPP.22.042V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.042(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.042(R11-11.0.0) |
+| TTC | TS-3GA-22.042(Re11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-22.042(Re11)v11.0.0.pdf |
+
+### 10.2.11 TS 22.053 Tandem free operation (TFO); Service description; Stage 1
+
+The document specifies the Stage 1 description for the tandem free operation (TFO) feature that provides the capability to avoid tandeming speech codecs in mobile-to-mobile speech calls. The primary aim is to realize improvements in speech quality. The TFO mode of operation could also be used to reduce inter-mobile service switching centre (MSC) transmission bandwidth requirements.
+
+In analogy with [ITU-T I.130], Stage 1 is an overall service description, from the service subscriber's and user's standpoints, that views the network as a single entity which provides services to the user.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.053 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22053-b00.pdf |
+| ETSI | TS 122 053 | 11.0.0 | Published | 2012-10-03 | http://www.etsi.org/deliver/etsi_ts/122000_122099/122053/11.00.00_60/ts_122053v110000p.pdf |
+| ATIS | ATIS.3GPP.22.053V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.053(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatdesc.jsp?stdno=TTAT.3G-22.053(R11-11.0.0) |
+
+### 10.2.12 TS 22.057 Mobile execution environment (MExE); Service description; Stage 1
+
+MExE provides a standardized execution environment in an UE, and an ability to negotiate its supported capabilities with a MExE service provider, allowing applications to be developed independently of any UE platform. The UE (consisting of the ME and SIM/USIM) can then be targeted at a range of implementations for MExE from small devices with low bandwidth, limited displays, low processor speeds, limited memory, MMI, etc., to sophisticated devices with a complete MExE execution environment.
+
+This technical specification defines Stage 1 description of the mobile execution environment (MExE). Stage 1 is an overall service description, primarily from the subscriber's and service providers' points of view, and does not deal with the details of the human interface itself.
+
+This technical specification includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
+
+This technical specification contains the core requirements for a mobile execution environment (MExE) that is sufficient to provide a complete service.
+
+It is highly desirable, however, that technical solutions for a mobile execution environment (MExE) be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in this technical specification may implement requirements that are considered outside the scope of this technical specification. This additional functionality may be on a network-wide basis, nationwide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service.
+
+As indicated in Figure 10.2.12-1, the scope of this technical specification encompasses the MExE functionality in the UE, interaction with the MExE service environment. The MExE service environment is not necessarily restricted to the PLMN, and nodes providing MExE services (i.e., MExE servers) may also exist outside the PLMN. Aspects of the support provided by MExE servers within the MExE service environment (such as charging aspects, security level classification, etc.) are covered by this specification, but not the MExE servers themselves.
+
+
+
+Q.1743(16)\_F10.2.12-1
+
+Diagram showing a UE (User Equipment) connected to a ME (Mobile Equipment) which is connected to a cloud labeled 'MExE service environment'. An arrow labeled 'Scope of this TS' points from the cloud to the UE.
+
+**Figure 10.2.12-1 – Scope of Technical Specification 22.057**
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.057 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22057-b00.pdf |
+| ETSI | TS 122 057 | 11.0.0 | Published | 2012-10-03 | http://www.etsi.org/deliver/etsi_ts/122000_122099/122057/11.00.00_60/ts_122057v110000p.pdf |
+| ATIS | ATIS.3GPP.22.057V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.057(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.057(R11-11.0.0) |
+
+### 10.2.13 TS 22.060 General packet radio service (GPRS); Service description; Stage 1
+
+This technical specification defines the Stage 1 description of the general packet radio service (GPRS). Stage 1 is an overall service description, primarily from the service subscriber's and user's points of view, but does not deal with the details of the human interface itself. This technical specification includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
+
+This technical specification contains the core requirements for the packet-switched 3G networks that are sufficient to provide a complete service. It defines a set of bearer services that provide packet mode transmission within the PLMN and interwork with external networks.
+
+The term "GPRS" shall be used in this document to refer the GPRS service offered via GERAN and UTRAN and the PS Domain of the 3G PLMN.
+
+The GPRS shall not prevent the user's operation of other 3GPP services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 122 060 | 11.0.0 | Published | 2012-10-23 | http://www.etsi.org/deliver/etsi_ts/122000_122099/122060/11.00.00_60/ts_122060v110000p.pdf |
+| ATIS | ATIS.3GPP.22.060V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.060(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.060(R11-11.0.0) |
+| TTC | TS-3GA-22.060(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-22.060(Rel11)v11.0.0.pdf |
+
+### **10.2.14 TS 22.066 Support of mobile number portability (MNP); Service description; Stage 1**
+
+This technical specification defines the Stage 1 description of the support of mobile number portability between networks in the same country as well as North America cross-sector portability (i.e., number portability between fixed and 3GPP system). Stage 1 is an overall service description, primarily from the service subscriber's and user's points of view, but does not deal with the details of the human interface itself.
+
+Mobile number portability (MNP) is applicable only to those telecommunication services identified by an MSISDN.
+
+This specification includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
+
+This specification contains the core requirements for the support of mobile number portability between network operators in the same country as well as North America cross-sector portability that are sufficient to provide a complete service.
+
+Other cross-sector portability options (e.g., number portability between fixed and mobile networks outside the North American region) are outside the scope of this Technical Specification. It is highly desirable, however, that technical solutions for MNP should be sufficiently flexible to allow for possible enhancements, e.g., cross-sector number portability, and MNP between analogue and digital mobile networks. Additional functionalities not documented in this specification may implement requirements that are considered outside the scope of this specification. This additional functionality may be on a network-wide basis, nationwide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service.
+
+Porting between service providers (i.e., service provider portability) that does not involve a change of network operator is outside the scope of this specification.
+
+The relationship between service providers and network operators is outside the scope of this specification.
+
+The relationship between a service provider and subscriber is outside the scope of this specification. The interface between the user equipment (UE) and any external applications are outside the scope of this specification. Charging principles are outside the scope of this specification, except where explicitly stated in the text.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|----------------|-----------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 122 066 | 11.0.0 | Published | 2012-10-03 | http://www.etsi.org/deliver/etsi_ts/122000_122099/122066/11.00.00_60/ts_122066v110000p.pdf |
+| ATIS | ATIS.3GPP.22.066V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.066(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.066(R11-11.0.0) |
+| TTC | TS-3GA-22.066(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-22.066(Rel11)v11.0.0.pdf |
+
+### 10.2.15 TS 22.071 Location services (LCS); Service description; Stage 1
+
+This document provides the Stage 1 description of location services (LCS). A Stage 1 description provides an overall service description, primarily from the service subscriber's and user's points of view, but not dealing with the details of the man-machine interface (MMI). This technical specification includes information applicable to network operators, service providers and terminal, base station system, switch, and database manufacturers.
+
+NOTE – Location services may be considered as a network-provided enabling technology consisting of standardized service capabilities that enable the provision of location-based applications. These applications may be service provider specific. The description of the numerous and varied possible location applications which are enabled by this technology are outside the scope of this specification. However, clarifying examples of how the functionality being specified may be used to provide specific location services is included in various clauses of the specification.
+
+This document provides core requirements to an extent sufficient to derive a complete definition of location services at the service level. However, this document also provides additional requirements that may suggest in a non-normative manner certain ways the system may be implemented to support location services.
+
+LCS can be offered without subscription to basic telecommunication services. LCS is available to the following categories of LCS clients:
+
+- Value-added services LCS clients – Use LCS to support various value-added services. These clients can include UE subscribers as well as non-subscribers to other services.
+- PLMN operator LCS clients – Use LCS to enhance or support certain O&M related tasks, supplementary services, IN-related services and bearer services and teleservices.
+- Emergency services LCS clients – Use LCS to enhance support for emergency calls from subscribers.
+- Lawful intercept LCS clients – Use LCS to support various legally required or sanctioned services.
+
+LCS is applicable to any target UE whether or not the UE supports LCS, but with restrictions on the choice of the positioning method or notification of a location request to the UE user when the LCS or the individual positioning methods, respectively, are not supported by the UE.
+
+LCS is being developed in phases with enhancements added in yearly releases.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.071 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22071-b00.pdf |
+| ETSI | TS 122 071 | 11.0.0 | Published | 2012-10-03 | http://www.etsi.org/deliver/etsi_ts/122000_122099/122071/11.00.00_60/ts_122071v110000p.pdf |
+| ATIS | ATIS.3GPP.22.071V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.071(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.071(R11-11.0.0) |
+
+### 10.2.16 TS 22.076 Noise suppression for the AMR codec; Service description; Stage 1
+
+This document specifies the Stage 1 description for the noise suppression feature for the AMR codec that enhances the input speech signal corrupted by acoustic noise. In analogy with [ITU-T I.130], Stage 1 is an overall service description, from the service subscriber's and user's standpoints, that views the network as a single entity which provides services to the user.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.076 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22076-b00.pdf |
+| ETSI | TS 122 076 | 11.0.0 | Published | 2012-10-03 | http://www.etsi.org/deliver/etsi_ts/122000_122099/122076/11.00.00_60/ts_122076v110000p.pdf |
+| ATIS | ATIS.3GPP.22.076V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.076(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.076(R11-11.0.0) |
+
+### 10.2.17 TS 22.097 Multiple subscriber profile (MSP) Phase 1; Service description; Stage 1
+
+The document gives an overall view of how this service shall operate both in the PLMN and within the mobile station (MS). This technical specification defines functionality and is not intended to constrain implementation.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 122 097 | 11.0.0 | Published | 2012-10-03 | http://www.etsi.org/deliver/etsi_ts/122000_122099/122097/11.00.00_60/ts_122097v110000p.pdf |
+| ATIS | ATIS.3GPP.22.097V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.097(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.097(R11-11.0.0) |
+| TTC | TS-3GA-22.097(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-22.097(Rel11)v11.0.0.pdf |
+
+### 10.2.18 TS 22.101 Service aspects; Service principles
+
+This technical specification (TS) describes the service principles for PLMNs. Principles and requirements for interworking with WLAN are covered in TS 22.234.
+
+3G specifications define integrated personal communications services. The system will support different applications ranging from narrow-band to wideband communications capability with integrated personal and terminal mobility to meet the user and service requirements of the 21st century.
+
+The specifications allow the realization of a new generation of mobile communications technology for a world in which personal communications services should allow person-to-person calling, independent of location, the terminal used, the means of transmission (wired or wireless) and the choice of technology. Personal communication services should be based on a combination of fixed and wireless/mobile services to form a seamless end-to-end service for the user.
+
+The specifications should be in compliance with the following objectives:
+
+- a) to provide a single integrated system in which the user can access services in an easy and uniform way to use in all environments;
+- b) to allow differentiation between service offerings of various serving networks and home environments;
+- c) to provide a wide range of telecommunication services including those provided by fixed networks and requiring user bit rates of up to 2 Mbit/s as well as services special to mobile communications. These services should be supported in residential, public and office environments and in areas of diverse population densities. These services are provided with a quality comparable with that provided by fixed networks such as ISDN;
+- d) to provide services via handheld, portable, vehicular-mounted, movable and fixed terminals (including those which normally operate connected to fixed networks), in all environments (in different service environments – residential, private domestic and different radio environments) provided that the terminal has the necessary capabilities;
+- e) to provide support of roaming users by enabling users to access services provided by their home environment in the same way even when roaming;
+- f) to provide audio, data, video and particularly multimedia services;
+- g) to provide for the flexible introduction of telecommunication services;
+- h) to provide within the residential environment the capability to enable a pedestrian user to access all services normally provided by fixed networks;
+- i) to provide within the office environment the capability to enable a pedestrian user to access all services normally provided by PBXs and LANs;
+- j) to provide a substitute for fixed networks in areas of diverse population densities, under conditions approved by the appropriate national or regional regulatory authority;
+- k) to provide support for interfaces which allow the use of terminals normally connected to fixed networks.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|----------------|----------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.101 | 11.9.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22101-b90.pdf |
+| ETSI | TS 122 101 | 11.9.0 | Published | 2013-07-11 | http://www.etsi.org/deliver/etsi_ts/122100_122199/122101/11_09.00_60/ts_122101v110900p.pdf |
+| ATIS | ATIS.3GPP.22.101V1180-2014 | 11.8.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.101(R11-11.8.0) | 11.8.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.101(R11-11.8.0) |
+
+### 10.2.19 TS 22.105 Services and service capabilities
+
+Existing systems have largely standardized the complete sets of bearer services, teleservices and supplementary services that they provide. 3G specifications specify service capabilities rather than services, allowing service differentiation and system continuity. This technical specification describes how and what kind of services the user has access to.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.105 | 11.1.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22105-b10.pdf |
+| ETSI | TS 122 105 | 11.1.0 | Published | 2014-01-10 | http://www.etsi.org/deliver/etsi_ts/122100_122199/122105/11.01.00_60/ts_122105v110100p.pdf |
+| ATIS | ATIS.3GPP.22.105V1101-2014 | 11.0.1 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.105(R11-11.0.1) | 11.0.1 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stno=TTAT.3G-22.105(R11-11.0.1) |
+
+### 10.2.20 TS 22.115 Service aspects; Charging and billing
+
+The document describes the service aspects of charging and billing of the 3GPP system.
+
+The document is not intended to duplicate existing standards or standards being developed by other groups on these topics, and will reference these where appropriate. The document will elaborate on the charging requirements described in the charging principles in TS 22.001 service principles. It will allow the generation of accurate charging information to be used in the commercial and contractual relationships between the parties concerned.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 122 115 | 11.6.0 | Published | 2012-09-25 | http://www.etsi.org/deliver/etsi_ts/122100_122199/122115/11.06.00_60/ts_122115v110600p.pdf |
+| ATIS | ATIS.3GPP.22.115V1160-2014 | 11.6.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.115(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stno=TTAT.3G-22.115(R11-11.6.0) |
+| TTC | TS-3GA-22.115(Re11)v11.6.0 | 11.6.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-22.115(Re11)v11.6.0.pdf |
+
+### 10.2.21 TS 22.129 Handover requirements between UTRAN and GERAN or other radio systems
+
+The scope of this document includes service requirements for handover maintaining continuity of service to a wireless terminal as it moves between the radio coverage area, or "cells", associated with different base station sites. This functionality is called "handover". Handover can also occur due to change of radio resource providing a service without necessarily any change of the base stations involved. In particular, when the radio resources providing a service change from one of the UTRA radio access modes to the other (UTRA-FDD and UTRA-TDD), this is regarded as handover. Particular emphasis has been placed on the description of requirements for service continuity within UTRAN and between UTRAN and GERAN, but requirements specific to other systems are incorporated as required.
+
+It is a key requirement to allow for dual or multimode terminals to hand over traffic from UTRAN to other radio systems such as GERAN and vice versa. This document describes the service requirements for intra- and inter-system handover.
+
+The following subject areas are within the scope of these service requirements:
+
+- User perceived performance that may be influenced by handover;
+- Operational requirements relating to handover;
+- Security requirements.
+
+The requirements set forth in this document are service requirements, in that they fulfil the following:
+
+- The requirements are independent of the implementation of the UTRAN.
+- The extent to which the requirements are met are in principle verifiable using observable that are not internal to the UTRAN.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 122 129 | 11.0.0 | Published | 2012-10-03 | http://www.etsi.org/deliver/etsi_ts/122100_122199/122129/11.00.00_60/ts_122129v110000p.pdf |
+| ATIS | ATIS.3GPP.22.129V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.129(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.129(R11-11.0.0) |
+| TTC | TS-3GA-22.129(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-22.129(Rel11)v11.0.0.pdf |
+
+### 10.2.22 TS 22.135 Multicall; Service description; Stage 1
+
+The document describes multicall (MC) supplementary service.
+
+The general aspects, including definitions and recommended provision, of the description of supplementary services are given in TS 22.004.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 122 135 | 11.0.0 | Published | 2012-10-23 | http://www.etsi.org/deliver/etsi_ts/122100_122199/122135/11.00.00_60/ts_122135v110000p.pdf |
+| ATIS | ATIS.3GPP.22.135V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.135(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.135(R11-11.0.0) |
+| TTC | TS-3GA-22.135(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-22.135(Rel11)v11.0.0.pdf |
+
+### 10.2.23 TS 22.140 Multimedia messaging service (MMS); Stage 1
+
+This technical specification defines the Stage 1 description of the non real-time multimedia messaging service (MMS). Stage 1 is the set of requirements which shall be supported for the provision of non real-time multimedia messaging service, seen primarily from the subscriber's and service providers' points of view.
+
+This technical specification includes information applicable to network operators, service providers, terminal and network manufacturers.
+
+This technical specification contains the core requirements for the multimedia messaging service, which is sufficient to provide a complete service.
+
+This TS defines the requirements for MMS to be understood as a framework to enable non real-time transmissions for different types of media including such functionality as:
+
+- multiple media elements per single message;
+- individual handling of message elements;
+- different delivery methods for each message element;
+- negotiating different terminal and network MM capabilities;
+- notification and acknowledgement of MM related events (e.g., delivery, deletion, etc.);
+- handling of undeliverable MM;
+- personalized MMS configuration;
+- flexible charging.
+
+The above list is not exhaustive.
+
+Thus, the MMS enables a unified application that integrates the composition, storage, access, and delivery of different kinds of media, e.g., text, voice, image or video in combination with additional mobile requirements.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.140 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22140-b00.pdf |
+| ETSI | TS 122 140 | 11.0.0 | Published | 2012-10-03 | http://www.etsi.org/deliver/etsi_ts/122100_122199/122140/11.00.00_60/ts_122140v110000p.pdf |
+| ATIS | ATIS.3GPP.22.140V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.140(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-22.140(R11-11.0.0) |
+
+### 10.2.24 TS 22.141 Presence service; Stage 1
+
+This TS defines the Stage 1 description for the presence service. Stage 1 is the set of requirements which shall be supported to enable the exploitation of the presence service, seen primarily from the users' and home environments' points of view.
+
+This TS includes information applicable to the home environment, device and network manufacturers which are sufficient to provide complete support of the presence service.
+
+Additional functionalities not documented in this TS are considered outside the scope of this TS. Such additional functionality may be on a network-wide basis, nationwide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the requirements of the presence service defined in this specification.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.141 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22141-b00.pdf |
+| ETSI | TS 122 141 | 11.0.0 | Published | 2012-10-03 | http://www.etsi.org/deliver/etsi_ts/122100_122199/122141/11.00.00_60/ts_122141v110000p.pdf |
+| ATIS | ATIS.3GPP.22.141V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.141(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.141(R11-11.0.0) |
+
+### 10.2.25 TS 22.146 Multimedia broadcast/multicast service; Stage 1
+
+This technical specification defines the Stage 1 description of the broadcast and multicast services for the 3GPP System (UTRAN and GERAN). Stage 1 is the set of requirements which shall be supported for the provision of broadcast and multicast services, seen primarily from the subscriber's and service providers' points of view.
+
+This TS includes information applicable to network operators, content providers, and terminal and network manufacturers.
+
+This TS contains the core requirements for multicast and broadcast services, which are sufficient to provide a complete service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.146 | 11.1.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22146-b10.pdf |
+| ETSI | TS 122 146 | 11.1.0 | Published | 2013-05-30 | http://www.etsi.org/deliver/etsi_ts/122100_122199/122146/11.01.00_60/ts_122146v110100p.pdf |
+| ATIS | ATIS.3GPP.22.146V1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.146(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.146(R11-11.1.0) |
+
+### 10.2.26 TS 22.153 Multimedia priority service
+
+This document specifies the service requirements for multimedia priority service (MPS).
+
+The scope of this document is to specify those requirements of MPS necessary to provide an end-to-end service and to interwork with external networks where needed. Service interactions with external networks are considered within the scope of this document although these interactions may be specified in other standards.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.153 | 11.1.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22153-b10.pdf |
+| ETSI | TS 122 153 | 11.1.0 | Published | 2012-11-13 | http://www.etsi.org/deliver/etsi_ts/122100_122199/122153/11_01_00_60/ts_122153v110100p.pdf |
+| ATIS | ATIS.3GPP.22.153V 1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.153(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.153(R11-11.1.0) |
+
+### 10.2.27 TS 22.173 IP Multimedia core network subsystem (IMS) multimedia telephony service and supplementary services; Stage 1
+
+This technical specification defines the Stage 1 description of the IMS multimedia telephony service and the minimum set of capabilities required to secure multi-vendor and multi-operator inter-operability for multimedia telephony and related supplementary services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 122 173 | 11.5.0 | Published | 2013-07-11 | http://www.etsi.org/deliver/etsi_ts/122100_122199/122173/11_05_00_60/ts_122173v110500p.pdf |
+| ATIS | ATIS.3GPP.22.173V 1140-2014 | 11.4.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.173(R11-11.4.0) | 11.4.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.173(R11-11.4.0) |
+| TTC | TS-3GA-22.173(Rel11)v11.5.0 | 11.5.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-22.173(Rel11)v11.5.0.pdf |
+
+### 10.2.28 TS 22.174 Push service; Service aspects; Stage 1
+
+This technical specification defines the Stage 1 description of the push service and is the set of requirements that shall be supported for the provision of push, seen primarily from the subscriber's, service providers' and delivery network points of view.
+
+This TS includes information applicable to network operators, service providers, terminal and network manufacturers. It is of use to manufacturers and organizations which have devices or machines benefiting by availability of push service.
+
+This TS contains the core requirements for the push service, for operator and external push initiators, which are sufficient to provide a complete service capability and service capability feature.
+
+This TS defines the requirements for the push service to enable delivery of push data, including such functionality as:
+
+- transfer of push data from a push initiator to a push recipient;
+- latency and priority classes;
+- definition of handling of undeliverable push data.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.174 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22174-b00.pdf |
+| ETSI | TS 122 174 | 11.0.0 | Published | 2012-10-03 | http://www.etsi.org/deliver/etsi_ts/122100_122199/122174/11.00.00_60/ts_122174v110000p.pdf |
+| ATIS | ATIS.3GPP.22.174V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.174(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.174(R11-11.0.0) |
+
+### 10.2.29 TS 22.182 Customized alerting tone (CAT) requirements; Stage 1
+
+The document specifies the requirements and technical considerations for customized alerting tone (CAT) service in both CS and PS domains, especially additional features for roaming and interoperability support.
+
+This document considers voice and multi-media CAT, so the CAT user may experience favourable songs, multi-media clips or other customized alerting tones.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.182 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22182-b00.pdf |
+| ETSI | TS 122 182 | 11.0.0 | Published | 2012-10-03 | http://www.etsi.org/deliver/etsi_ts/122100_122199/122182/11.00.00_60/ts_122182v110000p.pdf |
+| ATIS | ATIS.3GPP.22.182V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.182(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.182(R11-11.0.0) |
+
+### 10.2.30 TS 22.228 Service requirements for the Internet protocol (IP) multimedia core network subsystem; Stage 1
+
+This TS defines the service requirements from users' and operators' perspective for the support of IP multimedia applications.
+
+IP multimedia applications are supported by IP multimedia sessions in the IM CN subsystem. IP multimedia sessions use IP connectivity bearers (e.g., GPRS as a bearer). Examples of IP multimedia applications include speech communication, real-time multimedia applications, shared online whiteboards, etc.
+
+This TS, in general, does not standardize usage of IP multimedia applications, but instead identifies the requirements to enable their support.
+
+In order to align IP multimedia applications wherever possible with non-3GPP IP applications, the general approach is to adopt non-3GPP IP-based solutions.
+
+The existing legacy tele- and supplementary services shall not be re-standardized as IP multimedia applications, and multimedia equivalent applications may be created with toolkits.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.228 | 11.6.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22228-b60.pdf |
+| ETSI | TS 122 228 | 11.6.0 | Published | 2013-01-10 | http://www.etsi.org/deliver/etsi_ts/122200_122299/122228/11.06.00_60/ts_122228v110600p.pdf |
+| ATIS | ATIS.3GPP.22.228V1160-2014 | 11.6.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.228(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.228(R11-11.6.0) |
+| TTC | TS-3GA-22.228(Rel11)v11.6.0 | 11.6.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-22.228(Rel11)v11.6.0.pdf |
+
+### 10.2.31 TS 22.233 Transparent end-to-end packet-switched streaming service; Stage 1
+
+This technical specification defines the Stage 1 description of the packet-switched streaming service (PSS). Stage 1 is the set of requirements that shall be supported for the provision of a streaming service, seen primarily from the user's and service providers' points of view but also includes the service capabilities of the PSS itself.
+
+This TS includes information applicable to network operators, service providers, terminal and network manufacturers.
+
+This TS contains the core requirements for the packet-switched streaming service (PSS), which are sufficient to enable a range of services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.233 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22233-b00.pdf |
+| ETSI | TS 122 233 | 11.0.0 | Published | 2012-10-03 | http://www.etsi.org/deliver/etsi_ts/122200_122299/122233/11.00.00_60/ts_122233v110000p.pdf |
+| ATIS | ATIS.3GPP.22.233V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.233(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.233(R11-11.0.0) |
+
+### 10.2.32 TS 22.234 Requirements on 3GPP system to wireless local area network (WLAN) interworking
+
+The present document specifies the functional requirements placed on the 3GPP system for interworking WLAN with the 3GPP system. Guidance is given for WLAN operators intending to provide the interworked WLAN capability.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 122 234 | 11.0.0 | Published | 2012-10-23 | http://www.etsi.org/deliver/etsi_ts/122200_122299/122234/11.00.00/60/ts_122234v110000p.pdf |
+| ATIS | ATIS.3GPP.22.234V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.234(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.234(R11-11.0.0) |
+| TTC | TS-3GA-22.234(Re11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-22.234(Re11)v11.0.0.pdf |
+
+### 10.2.33 TS 22.240 Service requirements for 3GPP generic user profile (GUP); Stage 1
+
+This document defines the stage one description to the 3GPP generic user profile (GUP). It specifies requirements to the 3GPP generic user profile, seen primarily from the user, home environment, serving network and value added service provider's points of view.
+
+The present document includes information applicable to the home environment, device- and network manufacturers and value added service providers which are sufficient to provide complete support of services in 3GPP networks.
+
+While the 3GPP generic user profile may contain components that are out of scope of 3GPP (e.g., for services offered by third parties) the requirements in the present document pertain only to those components that lie within the 3GPP system.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 122 240 | 11.1.0 | Published | 2014-01-10 | http://www.etsi.org/deliver/etsi_ts/122200_122299/122240/11.01.00/60/ts_122240v110100p.pdf |
+| ATIS | ATIS.3GPP.22.240V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.240(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.240(R11-11.0.0) |
+| TTC | TS-3GA-22.240(Re11)v11.1.0 | 11.1.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-22.240(Re11)v11.1.0.pdf |
+
+### 10.2.34 TS 22.242 Digital rights management (DRM); Stage 1
+
+The text in this specification has been removed. DRM specifications are elaborated in the open mobile alliance (OMA) according to an agreement between 3GPP and OMA.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.242 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22242-b00.pdf |
+| ETSI | TS 122 242 | 11.0.0 | Published | 2012-10-03 | http://www.etsi.org/deliver/etsi_ts/122200_122299/122242/11.00.00_60/ts_122242v110000p.pdf |
+| ATIS | ATIS.3GPP.22.242V 1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.242(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-22.242(R11-11.0.0) |
+
+### 10.2.35 TS 22.243 Speech recognition framework for automated voice services; Stage 1
+
+The present document defines the Stage 1 description of the speech recognition framework (SRF) for automated voice services. Stage 1 is the set of requirements for data seen primarily from the user's and service providers' points of view.
+
+This technical specification includes information applicable to network operators, service providers, terminal and network manufacturers.
+
+This technical specification contains the core requirements for the speech recognition framework for automated voice services.
+
+The scope of this Stage 1 is to identify the requirements for 3G networks to support the deployments of a speech recognition framework-based automated voice services, and therefore to introduce a 3GPP speech recognition framework as part of speech-enabled services. The speech recognition framework for automated voice services is an optional feature in a 3GPP system.
+
+Figure 1 positions the speech recognition framework (SRF) with respect to other speech-enabled services. As illustrated, SRF is designed to support server-side speech recognition over packet switched network (e.g., IMS). As such, SRF also enables configurations of multimodal and multidevice services that include distributing the speech engines.
+
+Note that it is possible to design speech-enabled services that alternate or combine the use of client side only engines and SRF.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 122 243 | 11.0.0 | Published | 2012-10-03 | http://www.etsi.org/deliver/etsi_ts/122200_122299/122243/11.00.00_60/ts_122243v110000p.pdf |
+| ATIS | ATIS.3GPP.22.243V 1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.243(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-22.243(R11-11.0.0) |
+| TTC | TS-3GA-22.243(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-22.243(Rel11)v11.0.0.pdf |
+
+### 10.2.36 TS 22.246 Multimedia broadcast/multicast service (MBMS) user services; Stage 1
+
+The present document describes MBMS user services that use the capabilities of MBMS. Application scenarios including charging, QoS aspects and related service requirements derived from them are described. These scenarios and service requirements can be used as guidance for the design of codecs and bearers for both UTRAN and GERAN.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.246 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22246-b00.pdf |
+| ETSI | TS 122 246 | 11.0.0 | Published | 2012-10-03 | http://www.etsi.org/deliver/etsi_ts/122200_122299/122246/11.00.00/60/ts_122246v110000p.pdf |
+| ATIS | ATIS.3GPP.22.246V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.246(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.246(R11-11.0.0) |
+
+### 10.2.37 TS 22.250 IP multimedia subsystem (IMS) group management; Stage 1
+
+The present document defines the Stage 1 description of the IMS group management. Stage 1 is the set of requirements which shall be supported for the provision of IMS group management, seen primarily from the subscribers' and service providers' points of view.
+
+The TS includes information applicable to network operator, service provider, terminal and network manufacturer.
+
+Additional functionalities not documented in the TS are considered outside the scope of this TS. Such additional functionality may be on a network-wide basis, nationwide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the requirements of the IMS group management defined in this specification.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 122 250 | 11.0.0 | Published | 2012-10-03 | http://www.etsi.org/deliver/etsi_ts/122200_122299/122250/11.00.00/60/ts_122250v110000p.pdf |
+| ATIS | ATIS.3GPP.22.250V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.250(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.250(R11-11.0.0) |
+| TTC | TS-3GA-22.250(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-22.250(Rel11)v11.0.0.pdf |
+
+### 10.2.38 TS 22.259 Service requirements for personal network management (PNM); Stage 1
+
+The present document describes the service requirements for the personal network management (PNM). Aspects of data synchronisation and management of user data are out of scope.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.259 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22259-b00.pdf |
+| ETSI | TS 122 259 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_ts/122200_122299/122259/11_00.00_60/ts_122259v110000p.pdf |
+| ATIS | ATIS.3GPP.22.259V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.259(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.259(R11-11.0.0) |
+
+### 10.2.39 TS 22.278 Service requirements for the evolved packet system (EPS)
+
+This document describes the service requirements for the evolved packet system. Additional requirements for E-UTRAN are contained in the specifications identified in Annex B of the document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.278 | 11.6.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22278-b60.pdf |
+| ETSI | TS 122 278 | 11.6.0 | Published | 2012-09-25 | http://www.etsi.org/deliver/etsi_ts/122200_122299/122278/11_06.00_60/ts_122278v110600p.pdf |
+| ATIS | ATIS.3GPP.22.278V1160-2014 | 11.6.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.278(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.278(R11-11.6.0) |
+
+### 10.2.40 TS 22.368 Service requirements for Machine-type communications (MTC); Stage 1
+
+The present document specifies the service requirements for network improvements for machine type communications. In particular it will:
+
+- identify and specify general requirements for machine type communications;
+- identify service aspects where network improvements (compared to the current human-to-human oriented services) are needed to cater for the specific nature of machine-type communications;
+- specify machine type communication requirements for these service aspects where network improvements are needed for machine type communication.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-22.368 | 11.6.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/22/A22368-b60.pdf |
+| ETSI | TS 122 368 | 11.6.0 | Published | 2012-09-25 | http://www.etsi.org/deliver/etsi_ts/122300_122399/122368/11.06.00_60/ts_122368v110600p.pdf |
+| ATIS | ATIS.3GPP.22.368V1160-2014 | 11.6.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.368(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.368(R11-11.6.0) |
+
+### 10.2.41 TR 22.903 Study on videotelephony teleservice
+
+This document analyses the introduction of additional functionalities for the videotelephony service in addition to what is provided in the 3GPP specifications up to Release 6. The functionalities will include but are not limited to codec negotiation, charging principles, supplementary services support. The approach followed is to evaluate how functionalities which are applicable to existing teleservices can be replicated for videotelephony.
+
+The document will analyse how the new functionalities will impact the backwards compatibility with the existing CS multimedia service, and will analyse whether it is beneficial to create a videotelephony teleservice.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TR 122 903 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122903/11.00.00_60/tr_122903v110000p.pdf |
+| ATIS | ATIS.3GPP.22.903V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.903(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.903(R11-11.0.0) |
+| TTC | TR-3GA-22.903(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TR/TR-3GA-22.903(Rel11)v11.0.0.pdf |
+
+### 10.2.42 TR 22.908 Study on paging permission with access control (PPAC)
+
+This technical report (TR) presents the results of the study on paging permission with access control. The intent of this study is to assess the ability of 3GPP specifications to meet requirements identified for paging permission with access control. This study considers the following aspects:
+
+- Identify requirements and aspects for paging permission with access control.
+- Perform a gap analysis to assess the ability of existing 3GPP specifications to meet the requirements and aspects.
+
+Regarding use-cases, followings should be studied in order to identify issues which are caused by the existing access control mechanism which does not allow UEs applied the access class restriction to establish terminating calls (non-exhaustive list):
+
+- Priority service.
+- Emergency service.
+- Communication between UEs in the same area where access control is performed.
+
+This study should focus on providing this service using the CS/PS domain. This study includes the aspect of originating call and terminating call.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.908 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/22/A22908-b00.pdf |
+| ETSI | TR 122 908 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122908/11.00.00_60/tr_122908v110000p.pdf |
+| ATIS | ATIS.3GPP.22.908V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.908(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.908(R11-11.0.0) |
+
+### 10.2.43 TR 22.934 Feasibility study on 3GPP system to wireless local area network (WLAN) interworking
+
+This document studies the feasibility of interworking between 3GPP systems and wireless local area networks (WLANs). This document identifies and describes:
+
+- scenarios for 3GPP – WLAN interworking;
+- 3GPP-WLAN interworking service requirements;
+- guidelines for standardization of 3GPP-WLAN interworking.
+
+The document includes a number of different scenarios of 3GPP-WLAN interworking ranging from common billing to the provision of services seamlessly between the WLAN and the 3GPP system. In addition, 3GPP-WLAN interworking feasibility study includes the analysis of a number of environments where both the 3GPP system and WLAN may be deployed. Finally, this report outlines some of the different WLAN technologies that may be interworked with 3GPP systems.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TR 122 934 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122934/11.00.00_60/tr_122934v110000p.pdf |
+| ATIS | ATIS.3GPP.22.934V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.934(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.934(R11-11.0.0) |
+| TTC | TR-3GA-22.934(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TR/TR-3GA-22.934(Rel11)v11.0.0.pdf |
+
+### 10.2.44 TR 22.935 Feasibility study on location services (LCS) for wireless local area network (WLAN) interworking
+
+The 3GPP has developed and continues to develop location services (LCS) requirements and standards for GSM and UMTS. To further the advancement of LCS within the 3GPP, LCS requirements and standards may be extended for 3GPP WLAN interworking to support the same location-based services that have been deployed today for GSM and UMTS. LCS with 3GPP WLAN Interworking system is considered to enlarge the area of location services.
+
+The purpose of the feasibility study is to study a generic interworking functionality for LCS between 3GPP system and WLAN systems (e.g., IEEE 802.11 family, HIPERLAN/2, ...). Specifically, the feasibility study aims to:
+
+- Study the LCS requirements for 3GPP WLAN interworking scenarios.
+- Study the different possible LCS architectures for interworking.
+
+Also, the feasibility study will:
+
+- Assess the service requirements for support of LCS over I-WLAN.
+- Define the MMI aspects, i.e., the minimum set of functions to support LCS when the choice of access system by the user and/or terminal for when both access systems is available.
+- Assess the charging requirements and architecture impacts. In particular, consider whether or not WLAN charging for LCS should be integrated with the architecture for UMTS charging for LCS.
+- Assess the security requirements, given the prerequisite that a) the security level of the UMTS platform itself is not impacted, b) the security level provided to users in the WLAN mode is comparable to the one of UMTS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TR 122 935 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122935/11.00.00_60/tr_122935v110000p.pdf |
+| ATIS | ATIS.3GPP.22.935V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.935(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-22.935(R11-11.0.0) |
+| TTC | TR-3GA-22.935(Re11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TR/TR-3GA-22.935(Re11)v11.0.0.pdf |
+
+### 10.2.45 TR 22.936 Multi-system terminals
+
+This document studies the behaviour of a multi-system terminal that supports both 3GPP and non3GPP systems. Particular issues handled include, but are not restricted to:
+
+- Whether the system selection or PLMN selection should take higher priority in a multisystem terminal.
+- Criteria for system change.
+- Interaction between the user's and the operator's preferences.
+- Support of automatic and manual system selection mode.
+- Different methods of system selection and their impact on 3GPP specifications.
+- Some areas for possible standardization, to ensure 3GPP compliance and protection of 3GPP networks.
+
+The document treats non-3GPP networks in a generic way but it applies mainly to the case of 3GPP2/3GPP compliant terminals.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.936 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/22/A22936-b00.pdf |
+| ETSI | TR 122 936 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122936/11.00.00_60/tr_122936v110000p.pdf |
+| ATIS | ATIS.3GPP.22.936V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.936(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.936(R11-11.0.0) |
+
+### 10.2.46 TR 22.937 Requirements for service continuity between mobile and wireless local area network (WLAN) networks
+
+The present document develops the use cases and requirements for service continuity between a 3GPP network and another network, which can be:
+
+- a TISPAN NGN with an IMS, accessed by a WLAN
+- an ISP accessed via a WLAN
+
+Each access network has its own separate security system and the NOs have a commercial agreement for roaming and handover.
+
+The present document also examines the requirements and implications of:
+
+- service aspects: maintaining service quality and service continuity, while roaming between a 3GPP PLMN and an independently-owned WLAN;
+- security aspects: while roaming between a 3GPP PLMN and a WLAN, in particular when networks may be independently authenticated.
+- UICC aspects, including NAA types, personalisation and ownership.
+
+The present document is related to ongoing standardisation efforts in the following areas:
+
+- where the WLAN is an I-WLAN, requirements for which are described in 3G TS 22.234;
+- methods for selecting the 3GPP or the non-3GPP access network, requirements for which are described in 3G TR 22.912.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.937 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/22/A22937-b00.pdf |
+| ETSI | TR 122 937 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122937/11.00.00_60/tr_122937v110000p.pdf |
+| ATIS | ATIS.3GPP.22.937V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.937(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.937(R11-11.0.0) |
+
+### 10.2.47 TR 22.940 IP multimedia subsystem (IMS) messaging
+
+The objective of this technical report is to:
+
+- a) describe use cases that illustrate the service requirements for IMS messaging;
+- b) derive the broad 3GPP requirements for IMS messaging services;
+- c) investigate the possible requirements for interworking with networks outside the 3GPP domain;
+- d) develop an analysis of the possible interaction between IMS messaging services and existing 3GPP messaging services (SMS, EMS and MMS) as well as other relevant 3GPP services such as presence IMS group management, etc.;
+- e) identify possible routes to standardization by:
+ - 1) adopting existing and emerging standards, e.g., OMA, IETF;
+ - 2) modifying and enhancing existing and emerging standards;
+ - 3) developing of new standards.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TR 122 940 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122940/11.00.00_60/tr_122940v110000p.pdf |
+| ATIS | ATIS.3GPP.22.940V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.940(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.940(R11-11.0.0) |
+| TTC | TR-3GA-22.940(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TR/TR-3GA-22.940(Rel11)v11.0.0.pdf |
+
+### 10.2.48 TR 22.942 Study on value added services (VAS) for short message service (SMS)
+
+This document studies the service requirements associated with series of value-added features for short message service (SMS). Specifically, the objective of this document is to study potential new value-added services for SMS in 3GPP that need to be standardized.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.942 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/22/A22942-b00.pdf |
+| ETSI | TR 122 942 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122942/11.00.00_60/tr_122942v110000p.pdf |
+| ATIS | ATIS.3GPP.22.942V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.942(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.942(R11-11.0.0) |
+
+### 10.2.49 TR 22.944 Report on service requirements for UE functionality split
+
+This report identifies scenarios and requirements for UEs with functionality split over multiple devices. Scenarios that are required to be supported in the standard are defined in detail. The requirements in this report should enable interoperability between user equipment components from different vendors. This report is not intended to identify all possible or permitted functionality splits. Certain splits of functionality may be prohibited for security or other reasons. This report does not identify all prohibited scenarios.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.944 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/22/A22944-b00.pdf |
+| ETSI | TR 122 944 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122944/11.00.00_60/tr_122944v110000p.pdf |
+| ATIS | ATIS.3GPP.22.944V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.944(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.944(R11-11.0.0) |
+
+### 10.2.50 TR 22.947 Study on personal broadcast service (PBS)
+
+This technical Report presents potential use cases of personal broadcast service. It aims to take account of service and system aspect of PBS. The minimum set of service requirements associated with each use case will be identified.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TR 122 947 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122947/11.00.00_60/tr_122947v110000p.pdf |
+| ATIS | ATIS.3GPP.22.947V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.947(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.947(R11-11.0.0) |
+| TTC | TR-3GA-22.947(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TR/TR-3GA-22.947(Rel11)v11.0.0.pdf |
+
+### 10.2.51 TR 22.948 Study of requirements of IP-multimedia subsystem (IMS) convergent multimedia conferencing
+
+This document studies the requirements for IP-multimedia subsystem (IMS) convergent multimedia conferencing (CMMC) service in IMS. Specifically, the objective of this study item is to:
+
+- Identify features of IMS multimedia conferencing, and describe potential service requirements for IMS multimedia conferencing.
+- Identify the IMS requirements for multimedia conferencing services:
+ - the conference framework
+ - data sharing session establishment/termination/management in a conference
+ - media control for audio, video and data
+
+- floor control for audio, video and data
+- conference policy
+- Identify possible routes to standardization by:
+ - Adopting existing and emerging standards, e.g., OMA, IETF, W3C.
+ - Modifying and enhancing existing and emerging standards.
+ - Developing of new standards.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.948 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/22/A22948-b00.pdf |
+| ETSI | TR 122 948 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122948/11.00.00_60/tr_122948v110000p.pdf |
+| ATIS | ATIS.3GPP.22.948V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.948(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.948(R11-11.0.0) |
+
+### 10.2.52 TR 22.949 Study on a generalized privacy capability
+
+The present document aims to investigate and summarize the existing service requirements on privacy for 3GPP services. In order to ensure that these services and future 3GPP services will have a consistent set of rules that control the availability and usage of confidential information, it is the intention to identify a common way to handle privacy-related information in the network.
+
+Generic privacy requirements for the mobile industry are also being defined by the Open Mobile Alliance, and it is the intention of this document to present the existing requirements and any alternatives to achieving the required functionality within 3GPP networks.
+
+The scope of this study is to:
+
+- identify privacy-related information that is used in the 3GPP system;
+- identify the existing 3GPP services that handle privacy-related information;
+- identify the various stakeholders that handle, control or consume personal data, and to define their relationships;
+- document the definitions of the various functions, stakeholders and functions involved in a privacy capability;
+- identify the work being done by other organizations and the additional work to be done by 3GPP.
+
+The types of data subject to privacy rules within the scope of this study include:
+
+- privacy-related information specific to an individual user;
+- privacy-related information relating to entities such as corporations;
+- network data such as serving cell and broadcast area, e.g., data that relates to the user's location or presence in the network, and which could be used by applications to track the user.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.949 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/22/A22949-b00.pdf |
+| ETSI | TR 122 949 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122949/11.00.00_60/tr_122949v110000p.pdf |
+| ATIS | ATIS.3GPP.22.949V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.949(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.949(R11-11.0.0) |
+
+### 10.2.53 TR 22.950 Priority service feasibility study
+
+This technical report (TR) presents the results of the feasibility study on priority service. The intent of this feasibility study is to assess the ability of 3GPP specifications to meet high-level requirements identified for priority service. This feasibility study consisted of a multi-step process, namely:
+
+- 1) Identify high-level requirements for priority service.
+- 2) Determine existing relevant 3GPP specifications for priority service.
+- 3) Perform a gap analysis to assess the ability of existing 3GPP specifications to meet the high-level priority service requirements.
+
+Additional functionalities not documented in this TR are considered outside the scope of this TR. Such additional functionality may be on a network-wide basis, nationwide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the requirements of the priority service defined in this specification.
+
+The priority service is intended to be utilized for both voice and data and therefore both elements are considered within the scope of this document. While priority service is meant for both voice and data services, the initial set of requirements address circuit-switched services (voice as well as data). Multimedia and non-circuit-switched aspects of priority service have not been addressed in this feasibility study and are for further study.
+
+The priority service is intended to interwork with external networks to provide an end-to-end service. Therefore, service interactions with external networks are considered within the scope of this document, although the specification of these interactions may be in other standards. If this occurs, a reference to that specification shall be made.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.950 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/22/A22950-b00.pdf |
+| ETSI | TR 122 950 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122950/11.00.00_60/tr_122950v110000p.pdf |
+| ATIS | ATIS.3GPP.22.950V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.950(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.950(R11-11.0.0) |
+
+### 10.2.54 TR 22.951 Service aspects and requirements for network sharing
+
+In the current dynamic market place, as a result of partnerships, acquisitions, creative agreements among operators, etc., the need for tools that enable various degrees of network sharing is becoming increasingly important.
+
+When GSM and then UMTS were specified, the possibility of sharing part or all of the network by two or more separated commercial entities was not considered, and as a result the standards lack some functionalities that enable the realization of such commercial agreements.
+
+GSM was designed under the principle "one operator, one radio access network". The GSM network has some possibilities of infrastructure sharing, but it does not support true radio access network sharing. The initial design of 3GPP system has followed the same principle.
+
+This technical report is aimed to capture the service and user requirements that must be fulfilled by the 3GPP system in order to enable network sharing in a standardized way. Section 5 describes various network sharing and includes various scenarios, e.g., spanning from common radio access network connected to multiple core networks, or multiple radio access networks sharing one core network. Section 6 contains a summary of the user classification and network identities. In section 7 the user requirements are described, while section 8 deals with the network operator requirements. Section 9 describes the mobility requirements in a shared network. The rest of the document covers security (section 10) and charging (section 11). Some conclusions can be found in section 12 and an annex with examples of practical realization of network sharing is provided.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TR 122 951 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122951/11.00.00_60/tr_122951v110000p.pdf |
+| ATIS | ATIS.3GPP.22.951V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.951(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.951(R11-11.0.0) |
+| TTC | TR-3GA-22.951(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TR/TR-3GA-22.951(Rel11)v11.0.0.pdf |
+
+### 10.2.55 TR 22.952 Priority service guide
+
+This document addresses the service aspects (service description), network aspects (call flows), and management aspects (operations, administration, maintenance, and provisioning) of priority service, based on existing 3GPP specifications.
+
+The priority service is intended to be used for both voice and data. However, this document only addresses circuit-switched voice service. Data, multimedia and non-circuit-switched aspects of priority service have not been addressed and are for further study.
+
+The priority service is intended to interwork with external networks to provide an end-to-end service. Therefore, service interactions with external networks are considered within the scope of this document, although the specification of these interactions may be in another standard. If this occurs, a reference to that specification is made.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.952 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/22/A22952-b00.pdf |
+| ETSI | TR 122 952 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122952/11.00.00_60/tr_122952v110000p.pdf |
+| ATIS | ATIS.3GPP.22.952V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.952(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.952(R11-11.0.0) |
+
+### 10.2.56 TR 22.953 Multimedia priority service feasibility study
+
+This technical report (TR) presents the results of the feasibility study on multimedia priority service. The intent of this feasibility study is to assess the ability of 3GPP specifications to meet high-level requirements identified for multimedia priority service. This feasibility study consisted of a multi-step process, namely:
+
+- Identify high-level requirements for multimedia priority service.
+- Determine relevant 3GPP specifications for multimedia priority service.
+- Perform a gap analysis to assess the ability of existing 3GPP specifications to meet the high-level multimedia priority service requirements.
+
+Additional functionalities not documented in this TR are considered outside the scope of this TR. Such additional functionality may be on a network-wide basis, nationwide basis or particular to a group of users.
+
+The multimedia priority service is intended to be utilized for both voice and data in the packet switched (PS) domain and the IP multimedia subsystem (IMS).
+
+The multimedia priority service is intended to interwork with external networks to provide an end-to-end service. Therefore, service interactions with external networks are considered within the scope of this document, although the specification of these interactions may be in other standards. If this occurs, a reference to that specification is made.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.953 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/22/A22953-b00.pdf |
+| ETSI | TR 122 953 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122953/11.00.00_60/tr_122953v110000p.pdf |
+| ATIS | ATIS.3GPP.22.953V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.953(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.953(R11-11.0.0) |
+
+### 10.2.57 TR 22.967 Transferring of emergency call data
+
+This document examines the issues associated with the transmission of emergency call data from a vehicle to a public service access point (PSAP).
+
+Issues associated with the content of the emergency call data or the triggers of the emergency calls are outside the scope of this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.967 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/22/A22967-b00.pdf |
+| ETSI | TR 122 967 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122967/11.00.00_60/tr_122967v110000p.pdf |
+| ATIS | ATIS.3GPP.22.967V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.967(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.967(R11-11.0.0) |
+
+### 10.2.58 TR 22.968 Study for requirements for a public warning system (PWS) service
+
+This document presents results of the study on public warning system (PWS). The intent of this study is to identify requirements and aspects for a public warning system. The regulatory requirements and use cases for a public warning service have not been finalized in all regions (i.e., in the USA) therefore, the results of this study are not applicable for those regions which do not have regulatory requirements defined.
+
+The public warning system is intended to interwork with external networks to provide an end-to-end service. Therefore, service interactions with a warning notification provider in external networks are considered within the scope of this document, although the specification of these interactions may be in other standards. If this occurs, a reference to that specification shall be made.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.968 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/22/A22968-b00.pdf |
+| ETSI | TR 122 968 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122968/11.00.00_60/tr_122968v110000p.pdf |
+| ATIS | ATIS.3GPP.22.968V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.968(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttastddesc.jsp?stdno=TTAT.3G-22.968(R11-11.0.0) |
+
+### 10.2.59 TR 22.977 Feasibility study for speech-enabled services
+
+The advancement in the automatic speech recognition (ASR) technology, coupled with the rapid growth in the wireless telephony market has created a compelling need for speech-enabled services. Voice-activated dialling has become a *de facto* standard in many of the mobile phones in the market today. The speech recognition technology has also been applied more recently to voice messaging and personal access services. A voice extensible markup language (voice XML) has been designed to bring the full power of web development and content delivery to voice response applications. Voice portals that provide voice access to conventional graphically oriented services over the Internet are now becoming popular. Forecasts show that speech-driven services will play an important role on the 3G market. Users of mobile terminals want the ability to access information while on the move and the small portable mobile devices that will be used to access this information need improved user interfaces (UIs) using speech input.
+
+A brief overview of the speech-enabled services is presented. The different ways of enabling speech recognition for the speech-enabled services are described. Section 6 discusses multimodal services and options to enable multimodal and multi-device services. The scope of the report, references, definitions and abbreviations are detailed in the first few sections.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TR 122 977 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122977/11.00.00_60/tr_122977v110000p.pdf |
+| ATIS | ATIS.3GPP.22.977V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.977(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttastddesc.jsp?stdno=TTAT.3G-22.977(R11-11.0.0) |
+| TTC | TR-3GA-22.977(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TR/TR-3GA-22.977(Rel11)v11.0.0.pdf |
+
+### 10.2.60 TR 22.978 All-IP network (AIPN) feasibility study
+
+The present document studies the feasibility of the progression of the 3GPP system to an AIPN. More specifically, this document:
+
+- Identifies and describes the objectives and user, business and technological drivers for progression of the 3GPP system to an AIPN:
+ - Investigates the high level objectives.
+
+- ii) Investigates motivations and drivers.
+- iii) Investigates impacts upon current models (e.g., business/charging/service models).
+- Defines and develops the end-user and AIPN operator aspects of an AIPN:
+ - Produces an AIPN vision, taking into account the special requirements for the mobile community, e.g., carrier grade, optimisation for the radio environment, recognizing support of multiple access system scenarios.
+ - Investigates needs and requirements associated with the evolution of the 3GPP System to an AIPN.
+ - Investigates requirements associated with the reuse of legacy infrastructure and support of legacy terminals.
+ - Investigates migration and cost effective introduction of new technology.
+- Identifies the capability expansion required to introduce the AIPN concept into the 3GPP system (migration and co-existence)
+- Evaluates whether an AIPN should be standardised within 3GPP, and in the case of a positive conclusion identifies the subsequent steps to be taken to achieve this by defining the scope, target, and roadmap for work to be undertaken within future 3GPP releases.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.978 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/22/A22978-b00.pdf |
+| ETSI | TR 122 978 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122978/11.00.00_60/tr_122978v110000p.pdf |
+| ATIS | ATIS.3GPP.22.978V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.978(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-22.978(R11-11.0.0) |
+| TTC | TR-3GA-22.978(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TR/TR-3GA-22.978(Rel11)v11.0.0.pdf |
+
+### 10.2.61 TR 22.980 Network composition feasibility study
+
+This document explores the feasibility of a uniform procedure for the integration of, and the interworking with, a large variety of heterogeneous network types. This uniform procedure is called Network Composition. It focuses on ad-hoc networks, PANs, moving networks etc., but also includes access systems. The goal is to avoid the need for defining a new procedure for integration / interworking with each newly emerging network type and to explore the feasibility of making the Network Composition procedure dynamic and to minimize human intervention ("plug and play"). Of course, the high security (authentication, authorization) standards of 3GPP must thereby be maintained. Finally, it is desirable for the network composition procedure to be flexible regarding what functionality is assumed in the composing network.
+
+It is conceivable that roaming within a pre-set commercial and technological environment could be established dynamically using the same procedure.
+
+This feasibility study covers the following aspects:
+
+- Description of purpose and benefits of composition.
+- Composition use cases highlighting uniformity, dynamicity, security, manageability, scalability, flexibility, as well as business aspects.
+- Study of potential composition requirements.
+- Description of the composition process.
+- Definition of traits and/or implications of introducing this functionality into the 3GPP system, covering subjects such as management, multi-link radio access, mobility, context & policy awareness, security, and media transcoding & adaptation capabilities.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.980 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/22/A22980-b00.pdf |
+| ETSI | TR 122 980 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122980/11.00.00_60/tr_122980v110000p.pdf |
+| ATIS | ATIS.3GPP.22.980V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.980(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.980(R11-11.0.0) |
+
+### 10.2.62 TR 22.982 Study of customized alerting tone (CAT) requirements
+
+This document studies requirements and potential new capabilities that need to be standardized for the CAT service, especially additional features for roaming and interoperability support.
+
+The document specifies requirements for the technical implementation of CAT service in the CS domain as well as impacts on the PS domain.
+
+Basically, this TR is considering voice services, although an interaction with IMS multimedia telephony (MITe, see 3G TS 22.173) services will be studied. Also multi-media CAT will be taken into consideration, so the CAT user may experience favourable songs, multi-media clips or other customized alerting tones.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.982 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/22/A22982-b00.pdf |
+| ETSI | TR 122 982 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122982/11.00.00_60/tr_122982v110000p.pdf |
+| ATIS | ATIS.3GPP.22.982V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.982(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.982(R11-11.0.0) |
+
+### 10.2.63 TR 22.983 Services alignment and migration
+
+This document studies how services to the end user should be delivered and managed regardless of how the user accesses the services (e.g., using CS or IMS) and to ensure a consistent user experience.
+
+The services in scope include but are not restricted to:
+
+- Conversational voice and video services.
+- Messaging services.
+- Supplementary services as applied to the above.
+
+For each of the above types, the service features that should be supported when accessing the service via CS or IMS using any appropriate access type are described. Also, the way each service will behave when transferring between domains is described.
+
+The work will also consider how to support existing ("traditional") services while allowing new, innovative services to be provided to the end user using the enhanced capabilities of the IMS. It will cover possible migration paths from where services are provided on both CS and IMS to IMS call and service control. Also, this work will consider roaming and call handling, interaction with legacy terminals, and the provision of user state and location for services accessed via CS or IMS and for services transferred between them.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.983 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/22/A22983-b00.pdf |
+| ETSI | TR 122 983 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122983/11.00.00_60/tr_122983v110000p.pdf |
+| ATIS | ATIS.3GPP.22.983V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.983(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.983(R11-11.0.0) |
+
+### 10.2.64 TR 22.987 Study of haptic services requirements
+
+This technical report aims to present use cases in telecommunication services that are developed by applying haptic technology. It also justifies accepting haptic technology in telecommunication services by investigating readiness for its use in the telecommunication system and the level of benefit for the user experience.
+
+For such purpose this document investigates following questions:
+
+- Provide the overview of current haptic technology which might be deployed in telecommunication
+- Identify any adaption required for existing services enhanced by supporting the delivery of haptic sense
+- Identify key aspects of new services built on capabilities provided by haptic technology
+- Identify and specify general requirements for delivery of haptic sense in telecommunication networks
+- Identify the scope and roles of 3GPP for mobile haptic services and consult with OMA to coordinate on the development of mobile haptic services
+
+Note that this technical report considers all types of telecommunication networks within the scope of 3GPP, including mobile networks and IMS-based fixed networks, etc.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-22.987 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/22/A22987-b00.pdf |
+| ETSI | TR 122 987 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122987/11.00.00_60/tr_122987v110000p.pdf |
+| ATIS | ATIS.3GPP.22.987V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-22.987(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-22.987(R11-11.0.0) |
+
+## 10.3 23-Series, Technical realisation
+
+### 10.3.1 TS 23.002 Network architecture
+
+This document offers an overview of the PLMN and its architectures and configuration. The configuration and the functional entities of the PLMN and the interfaces between them are described on a general level in order to cope with possible implementations. These descriptions include interfaces between and within the core networks, the access networks, the user equipment, different service platforms, different domains and subsystems, and functional entities within domains and subsystems.
+
+This document covers different architectural aspects with varying level of detail. In general, other specifications shall be referred to for further details; these specifications enable the reader to acquire the full understanding of a system or service feature.
+
+Note that this document does not cover, or even list, all features of PLMNs.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 002 | 11.6.0 | Published | 2013-06-27 | http://www.etsi.org/deliver/etsi_ts/123000_123099/123002/11.06.00_60/ts_123002v110600p.pdf |
+| ATIS | ATIS.3GPP.23.002V1150-2014 | 11.5.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.002(R11-11.5.0) | 11.5.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.002(R11-11.5.0) |
+| TTC | TS-3GA-23.002(Rel11)v11.6.0 | 11.6.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.002(Rel11)v11.6.0.pdf |
+
+### 10.3.2 TS 23.007 Restoration procedures
+
+The data stored in location registers are automatically updated in normal operation; the main information stored in a location register defines the location of each mobile station and the subscriber data required to handle traffic for each mobile subscriber. The loss or corruption of these data will seriously degrade the service offered to mobile subscribers; it is therefore necessary to define procedures to limit the effects of failure of a location register, and to restore the location register data automatically. This document defines the necessary procedures.
+
+The basic principle is that restoration should be based on radio contact to avoid faulty data being spread in the system.
+
+Subscriber data for supplementary services must also be correctly restored, although the impact on service of corruption of supplementary service data is less severe.
+
+Procedures for supporting these functions are defined in 3G Technical Specifications 29.002 and 29.060.
+
+The MAP operation "IMSI Attach" is used only in MAP version 1; in MAP version 2 the same function is performed by the MAP operation "Update location area". References in this specification to IMSI attach apply only to MAP version 1 network entities.
+
+If the restoration of subscriber data in the VLR is triggered by location updating or IMSI Attach, the VLR retrieves subscriber data from the HLR by sending an "Update Location" request, which triggers one or more "Insert Subscriber Data" operations from the HLR. The "Update Location" request may also be used to send the local mobile station identity (LMSI) to the HLR.
+
+If the restoration of subscriber data in the VLR is triggered by a "Provide Roaming Number" request, the behaviour of the VLR depends on whether it is implemented according to MAP version 1 or MAP version 2. For MAP version 2, the VLR retrieves subscriber data from the HLR by sending a "Restore Data" request, which triggers one or more "Insert Subscriber Data" operations from the HLR. The "Restore Data" request is also used to send the LMSI to the HLR. For MAP version 1, the VLR retrieves subscriber data from the HLR by sending a "Send Parameters" request with parameter type "Subscriber Data", which cannot be used to send the LMSI to the HLR.
+
+The VLR number and MSC number in the subscriber data in the HLR are updated by the "Update Location" procedure.
+
+The GGSN (gateway GPRS support node) is the point of PDN interconnection with the GSM PLMN supporting GPRS. The GGSN contains routing information for GPRS users with a PDP context active. The necessary procedures needed to restore GGSN data information after a restart is described in this document.
+
+The SGSN (serving GPRS support node) is the node that is serving the MS. The SGSN stores information regarding, e.g., mobility management, routing and security. The necessary procedures needed to restore this SGSN information after a restart are described in this document.
+
+A Type A LMU (location measurement unit) is a network node, accessed over the GSM air interface that is functionally similar to an MS. All requirements associated with a non-GPRS MS in this specification apply also to a Type A LMU, except where specified otherwise.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 007 | 11.8.0 | Published | 2014-03-17 | http://www.etsi.org/deliver/etsi_ts/123000_123099/123007/11_08_00_60/ts_123007v110800p.pdf |
+| ATIS | ATIS.3GPP.23.007V1150-2014 | 11.5.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.007(R11-11.5.0) | 11.5.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.007(R11-11.5.0) |
+| TTC | TS-3GA-23.007(Rel11)v11.7.0 | 11.7.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-23.007(Rel11)v11.7.0.pdf |
+
+### 10.3.3 TS 23.008 Organization of subscriber data
+
+The document provides details concerning information to be stored in home subscriber servers, visitor location registers, GPRS support nodes and call session control function (CSCF) concerning mobile subscriber.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 008 | 11.9.0 | Published | 2013-12-19 | http://www.etsi.org/deliver/etsi_ts/123000_123099/123008/11.09.00_60/ts_123008v110900p.pdf |
+| ATIS | ATIS.3GPP.23.008V 1170-2014 | 11.7.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.008(R11-11.7.0) | 11.7.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.008(R11-11.7.0) |
+| TTC | TS-3GA-23.008(Rel11)v11.9.0 | 11.9.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-23.008(Rel11)v11.9.0.pdf |
+
+### 10.3.4 TS 23.012 Location management procedures
+
+The document describes the location management procedures for the circuit-switched domain, with respect to the application level functional behaviour. This is to be distinguished from the corresponding protocol handling behaviour, which is specified in 3G TS 29.002. The following location management procedures are included:
+
+- Location updating;
+- Location cancellation;
+- MS purging;
+- IMSI attach/detach.
+
+The procedures in the mobile station (MS) are described in GSM 03.22. The procedures between MSC, VLR and HLR utilize the mobile application part (MAP) and details concerning the protocol handling are contained in 3G TS 29.002.
+
+The document excludes location management procedures for the packet-switched domain, which are covered in 3G TS 23.060.
+
+The descriptions herein depict a logical separation between the MSC and VLR. This logical separation, as well as the messages transferred between the two logical entities are the basis of a model used to define the externally visible behaviour of the MSC/VLR, which may be a single physical entity. They do not impose any requirement except the definition of the externally visible behaviour.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 012 | 11.2.0 | Published | 2013-01-16 | http://www.etsi.org/deliver/etsi_ts/123000_123099/123012/11.02.00_60/ts_123012v110200p.pdf |
+| ATIS | ATIS.3GPP.23.012V 1120-2014 | 11.2.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.012(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.012(R11-11.2.0) |
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTC | TS-3GA-23.012(Rel11)v11.2.0 | 11.2.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.012(Rel11)v11.2.0.pdf |
+
+### 10.3.5 TS 23.018 Basic call handling – Technical realization
+
+This technical specification (TS) specifies the technical realization of the handling of calls originated by a UMTS or GSM mobile subscriber and calls directed to a UMTS or GSM mobile subscriber, up to the point where the call is established. Normal release of the call after establishment is also specified.
+
+In this specification, the term "MS" is used to denote a UMTS or GSM MS, as appropriate.
+
+The handling of dual tone multiple frequency (DTMF) signalling and off-air call set-up (OACSU) is not described in this specification.
+
+The details of the effects of UMTS or GSM supplementary services on the handling of a call are described in the relevant 23.07x, 23.08x and 23.09x series of specifications.
+
+The specification of the handling of a request from the HLR for subscriber information is not part of basic call handling, but is required for both CAMEL (TS 23.078) and optimal routeing (TS 23.079). The use of the provide subscriber information message flow is shown in TS 23.078 and TS 23.079.
+
+The logical separation of the MSC and VLR, and the messages transferred between them are the basis of a model used to define the externally visible behaviour of the MSC/VLR, which is a single physical entity. They do not impose any requirement except the definition of the externally visible behaviour.
+
+If there is any conflict between this specification and the corresponding Stage 3 specifications (TS 24.008, TS 25.413, GSM 48.008 and TS 29.002), the Stage 3 specifications shall prevail.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 018 | 11.4.0 | Published | 2013-04-02 | http://www.etsi.org/deliver/etsi_ts/123000_123099/123018/11_04_00_60/ts_123018v110400p.pdf |
+| ATIS | ATIS.3GPP.23.018V 1140-2014 | 11.4.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.018(R11-11.4.0) | 11.4.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.018(R11-11.4.0) |
+| TTC | TS-3GA-23.018(Rel11)v11.4.0 | 11.4.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.018(Rel11)v11.4.0.pdf |
+
+### 10.3.6 TS 23.038 Alphabets and language-specific information
+
+This technical specification defines the alphabets, languages and message handling requirements for SMS, CBS and unstructured supplementary service data (USSD) and may additionally be used for man-machine interface (MMI) (TS 22.030).
+
+The specification for the data circuit-terminating equipment/data terminal equipment (DCE/DTE) interface (TS 27.005) will also use the codes specified herein for the transfer of SMS data to an external terminal.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.038 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/23/A23038-b00.pdf |
+| ETSI | TS 123 038 | 11.0.0 | Published | 2012-10-04 | http://www.etsi.org/deliver/etsi_ts/123000_123099/123038/11.00.00_60/ts_123038v110000p.pdf |
+| ATIS | ATIS.3GPP.23.038V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.038(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.038(R11-11.0.0) |
+
+### 10.3.7 TS 23.042 Compression algorithm for text messaging services
+
+The document introduces the concepts and mechanisms involved in the compression and decompression of a stream of data.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.042 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/23/A23042-b00.pdf |
+| ETSI | TS 123 042 | 11.0.0 | Published | 2012-10-08 | http://www.etsi.org/deliver/etsi_ts/123000_123099/123042/11.00.00_60/ts_123042v110000p.pdf |
+| ATIS | ATIS.3GPP.23.042V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.042(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.042(R11-11.0.0) |
+
+### 10.3.8 TS 23.107 Quality of service (QoS) concept and architecture
+
+The document provides the framework for quality of service within UMTS. The main purpose is to specify the list of attributes applicable to UMTS bearer service and radio access bearer service, as well as describe the quality of service architecture to be used in UMTS networks.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.107 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/23/A23107-b00.pdf |
+| ETSI | TS 123 107 | 11.0.0 | Published | 2012-11-14 | http://www.etsi.org/deliver/etsi_ts/123100_123199/123107/11.00.00_60/ts_123107v110000p.pdf |
+| ATIS | ATIS.3GPP.23.107V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.107(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.107(R11-11.0.0) |
+
+### 10.3.9 TS 23.110 Universal mobile telecommunications system (UMTS) access stratum; services and functions
+
+The present document specifies the services provided by the access stratum to the rest of the system. The adopted architecture is given by 3GPP TS 23.101.
+
+The present document describes the main functions visible at the boundary between the access stratum and the rest of the system; it describes in general terms the information flows, both control and user data, over this boundary and relevant for the access stratum.
+
+The present document is the basis of the detailed specifications of the protocols which rule the information flows, both control and user data, between the access stratum and the parts of UMTS outside the access stratum, and of the detailed specifications of the UTRAN. These detailed specifications are to be found in other technical specifications.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 110 | 11.0.0 | Published | 2012-09-25 | http://www.etsi.org/deliver/etsi_ts/123100_123199/123110/11.00.00_60/ts_123110v110000p.pdf |
+| ATIS | ATIS.3GPP.23.110V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.110(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.110(R11-11.0.0) |
+| TTC | TS-3GA-23.110(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.110(Rel11)v11.0.0.pdf |
+
+### 10.3.10 TS 23.119 Gateway location register (GLR); Stage2
+
+The document gives the Stage 2 description of the gateway location register (GLR) within the UMTS core network as a means of reducing the amount of MAP signalling traffic associated with location management carried over inter-PLMN links for roaming users.
+
+The document will be restricted of the case where the GLR supports one VPLMN only.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 119 | 11.0.0 | Published | 2012-10-24 | http://www.etsi.org/deliver/etsi_ts/123100_123199/123119/11.00.00_60/ts_123119v110000p.pdf |
+| ATIS | ATIS.3GPP.23.119V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.119(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.119(R11-11.0.0) |
+| TTC | TS-3GA-23.119(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.119(Rel11)v11.0.0.pdf |
+
+### 10.3.11 TS 23.135 Multicall supplementary service; Stage 2
+
+The document gives the Stage 2 description of the multicall supplementary service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 135 | 11.0.0 | Published | 2012-10-24 | http://www.etsi.org/deliver/etsi_ts/123100_123199/123135/11.00.00_60/ts_123135v110000p.pdf |
+| ATIS | ATIS.3GPP.23.135V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.135(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttastddesc.jsp?stdno=TTAT.3G-23.135(R11-11.0.0) |
+| TTC | TS-3GA-23.135(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.135(Rel11)v11.0.0.pdf |
+
+### 10.3.12 TS 23.141 Presence service; architecture and functional description
+
+The present document describes the Stage 2 description (architectural solution and functionalities) for the presence service, which includes the elements necessary to realize the Stage 1 requirements in 3GPP TS 22.141.
+
+The present document includes information applicable to network operators, service providers and manufacturers.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 141 | 11.0.0 | Published | 2012-09-25 | http://www.etsi.org/deliver/etsi_ts/123100_123199/123141/11.00.00_60/ts_123141v110000p.pdf |
+| ATIS | ATIS.3GPP.23.141V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.141(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttastddesc.jsp?stdno=TTAT.3G-23.141(R11-11.0.0) |
+| TTC | TS-3GA-23.141(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.141(Rel11)v11.0.0.pdf |
+
+### 10.3.13 TS 23.142 Value-added services for SMS (VAS4SMS); Interface and signalling flow
+
+This document describes the Stage 2 of the VAS4SMS (value-added service for SMS). It includes:
+
+- The logic architecture;
+- The logic elements functionality;
+- The signalling flows;
+- The interaction with other features.
+
+The service requirements of VAS4SMS are specified in 3GPP TS 22.142.
+
+The functionality and mechanism of SMS Service is defined in 3GPP TS 23.040.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 142 | 11.0.0 | Published | 2012-10-26 | http://www.etsi.org/deliver/etsi_ts/123100_123199/123142/11.00.00_60/ts_123142v110000p.pdf |
+| ATIS | ATIS.3GPP.23.142V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.142(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.142(R11-11.0.0) |
+| TTC | TS-3GA-23.142(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.142(Rel11)v11.0.0.pdf |
+
+### 10.3.14 TS 23.153 Out-of-band transcoder control; Stage 2
+
+This technical specification specifies the Stage 2 description of the out-of-band transcoder control for speech services. It describes the principles and procedures to support transcoder free operation, tandem free operation and the interworking between transcoder free operation (TrFO) and TFO. Transcoder at the edge is also part of this specification.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 153 | 11.1.0 | Published | 2012-11-14 | http://www.etsi.org/deliver/etsi_ts/123100_123199/123153/11.01.00_60/ts_123153v110100p.pdf |
+| ATIS | ATIS.3GPP.23.153V1110-2014 | 11.1.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.153(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.153(R11-11.1.0) |
+| TTC | TS-3GA-23.153(Rel11)v11.1.0 | 11.1.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.153(Rel11)v11.1.0.pdf |
+
+### 10.3.15 TS 23.167 IP multimedia subsystem (IMS) emergency sessions
+
+This document defines the Stage 2 service description for emergency services in the IP multimedia core network subsystem (IMS), including the elements necessary to support IP multimedia (IM) emergency services. [ITU-T I.130] describes a three-stage method for the characterization of telecommunication services, and [ITU-T Q.65] defines Stage 2 of the method.
+
+This document covers also the access network aspects that are crucial for the provisioning of IMS emergency services. Other 3GPP specifications that are related to the IMS emergency services are TS 23.228 on IMS in general, including fixed broadband access aspects, TS 23.060 and TS 23.234 describing GPRS and 3GPP/WLAN interworking respectively and TS 23.271 that covers location services. TS 25.301 contains an overall description of the UMTS terrestrial radio access network.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 167 | 11.10.0 | Published | 2014-03-17 | http://www.etsi.org/deliver/etsi_ts/123100_123199/123167/11.10.00_60/ts_123167v111000p.pdf |
+| ATIS | ATIS.3GPP.23.167V1160-2014 | 11.6.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.167(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.167(R11-11.6.0) |
+| TTC | TS-3GA-23.167(Rel11)v11.9.0 | 11.9.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-23.167(Rel11)v11.9.0.pdf |
+
+### 10.3.16 TS 23.203 Policy and charging control architecture
+
+The present document specifies the overall Stage 2 level functionality for policy and charging control that encompasses the following high level functions for IP-CANs (e.g., GPRS, IWLAN, fixed broadband, etc.):
+
+- Flow based charging, including charging control and online credit control;
+- Policy control (e.g., gating control, QoS control, etc.).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.203 | 11.12.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/23/A23203-bc0.pdf |
+| ETSI | TS 123 203 | 11.13.0 | Published | 2014-03-17 | http://www.etsi.org/deliver/etsi_ts/123200_123299/123203/11.13.00_60/ts_123203v111300p.pdf |
+| ATIS | ATIS.3GPP.23.203V1190-2014 | 11.9.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.203(R11-11.9.0) | 11.9.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.203(R11-11.9.0) |
+
+### 10.3.17 TS 23.204 Support of short message service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2
+
+This document specifies the new capabilities and enhancements needed to support SMS over a generic IP connectivity access network (IP-CAN) using IMS capabilities (3G TS 23.228). These include (but are not limited) to:
+
+- Enhancements to the HSS;
+- Communication between the SMS-GMSC/SMS-IWMSC and the HSS;
+- Authentication of service usage and registration;
+- Transfer of UE terminated SMS, UE originated SMS, and delivery reports;
+- Mechanisms to handle SMS when there is more than one IP connection active with the UE, etc.
+
+The document also specifies the capabilities and enhancements needed to support the service level interworking for the short message service as defined in the 3G TS 23.040 and in this specification and the instant messaging service as defined by OMA. The features supported from the IM specification are limited to the exchange of short or large immediate messages in pager mode.
+
+NOTE – The page-mode immediate message as defined in TS 24.247 is considered as a subset of OMA.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.204 | 11.5.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/23/A23204-b50.pdf |
+| ETSI | TS 123 204 | 11.5.0 | Published | 2013-09-20 | http://www.etsi.org/deliver/etsi_ts/123200_123299/123204/11_05.00_60/ts_123204v110500p.pdf |
+| ATIS | ATIS.3GPP.23.204V1130-2014 | 11.3.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.204(R11-11.3.0) | 11.3.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.204(R11-11.3.0) |
+
+### 10.3.18 TS 23.205 Bearer-independent circuit-switched core network; Stage 2
+
+The document defines the Stage 2 description for the bearer independent CS core network. The Stage 2 shall cover the information flow between the gateway mobile switching centre (GMSC) server, MSC server and media gateways. Note that nothing in this document shall preclude an implementation of a combined MSC Server and MGW. This document shall show the CS core network termination of the Iu interface in order to cover the information flow stimulus to the core network and describe the interaction with the supplementary and value-added services and capabilities.
+
+For the purposes of this specification, the protocol used over the Nc interface is an enhanced call control protocol supporting call bearer separation such as BICC (which is specified in 3GP TS 29.205). The protocol used over the Mc interface is [ITU-T H.248.1]. Existing specifications and Recommendations shall not be repeated as such, the relevant specification shall be referred to.
+
+This technical specification is applicable only for asynchronous transfer mode (ATM) or IP transport in the CS core network.
+
+
+
+Figure 10.3.18-1 – CS core network logical architecture diagram. The diagram shows the logical architecture of a CS core network. At the top, UTRAN and GERAN are connected to an MGW via Iu and A/Iu interfaces respectively. The MGW is connected to a PSTN/Legacy/External network. Below the MGW is a green-shaded area containing an MSC server and a GMSC server. The MSC server is connected to the MGW via Mc and Nb interfaces. The GMSC server is connected to the MGW via Mc and Nb interfaces. The MSC server and GMSC server are connected to each other via the Nc interface. Both the MSC server and GMSC server are connected to Applications and services via CAP interfaces. Both the MSC server and GMSC server are connected to an HLR via D and C interfaces. A legend at the bottom indicates that dashed lines represent Signalling interfaces and solid lines represent Signalling and data transfer interfaces. The diagram is labeled Q.1743(16)\_F10.3.18-1.
+
+Figure 10.3.18-1 – CS core network logical architecture
+
+The CAMEL application part (CAP) interfaces and the interfaces towards the HLR are outside the scope of this technical specification.
+
+Details of transcoder-free operation are outside the scope of this technical specification. Please see TS 23.153 for more information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 205 | 11.0.0 | Published | 2012-11-14 | http://www.etsi.org/deliver/etsi_ts/123200_123299/123205/11.00.00_60/ts_123205v110000p.pdf |
+| ATIS | ATIS.3GPP.23.205V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.205(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.205(R11-11.0.0) |
+| TTC | TS-3GA-23.205(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.205(Rel11)v11.0.0.pdf |
+
+### 10.3.19 TS 23.207 End-to-end quality of service (QoS) concept and architecture
+
+This document provides the framework for end-to-end quality of service involving GPRS and complements TS 23.107 which describes the framework for quality of service within UMTS. The end-to-end QoS architecture is provided in Figure 10.3.19-1. The document describes the interaction between the TE/MT local bearer service, the GPRS bearer service, and the external bearer service, and how these together provide quality of service for the end-to-end service. The document also describes IP level mechanisms necessary in providing end-to-end quality of service involving GPRS networks, including possible interaction between the IP level and the GPRS level, as well as the application level and the IP level.
+
+In contrast to the TS 23.107, this specification is only applicable to GPRS packet-switched access services, and includes aspects of interworking to the IM subsystem as well as public switched telephone network (PSTN) and other networks. The document does not cover the circuit-switched access services.
+
+
+
+The diagram illustrates the End-to-end QoS architecture across several network components: TE, MT, UTRAN/GERAN, CN Iu EDGE NODE, CN gateway, and TE. A bracket at the top labeled 'GPRS' spans from MT to CN gateway. The architecture is layered as follows:
+
+- End-to-end service:** A single layer spanning from the first TE to the second TE.
+- GPRS bearer service:** A layer below the end-to-end service, spanning from MT to CN gateway. It is supported by:
+ - TE/MT local bearer service:** Located under the first TE and MT.
+ - External bearer service:** Located under the second TE.
+- Radio access bearer service:** A layer below the GPRS bearer service, located under UTRAN/GERAN and MT. It is supported by:
+ - Radio bearer service:** Located under UTRAN/GERAN.
+ - Iu bearer service:** Located under CN Iu EDGE NODE.
+- CN bearer service:** A layer below the GPRS bearer service, located under CN Iu EDGE NODE and CN gateway. It is supported by:
+ - Backbone bearer service:** Located under CN gateway.
+- Physical radio service:** Located at the bottom under UTRAN/GERAN, supporting the Radio bearer service.
+- Physical bearer service:** Located at the bottom under CN Iu EDGE NODE, supporting the Iu bearer service.
+
+Diagram of End-to-end QoS architecture showing layers of services across TE, MT, UTRAN/GERAN, CN Iu EDGE NODE, CN gateway, and TE components.
+
+Q.1743(16)\_F10.3.19-1
+
+Figure 10.3.19-1 – End-to-end QoS architecture
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.207 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/23/A23207-b00.pdf |
+| ETSI | TS 123 207 | 11.0.0 | Published | 2012-11-14 | http://www.etsi.org/deliver/etsi_ts/123200_123299/123207/11.00.00/60/ts_123207v110000p.pdf |
+| ATIS | ATIS.3GPP.23.207V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.207(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.207(R11-11.0.0) |
+
+### 10.3.20 TS 23.216 Single radio voice call continuity (SRVCC); Stage 2
+
+This document specifies the architecture enhancements for single radio voice call continuity (SRVCC) between EUTRAN access and 3GPP2's 1xCS, and between EUTRAN access and 3GPP's UTRAN/GERAN accesses and between UTRAN (HSPA) access and 3GPP's UTRAN/GERAN accesses, for circuit switched (CS) calls that are anchored in the IMS.
+
+This document will not describe 3GPP2 functional entities. However, interfaces between both 3GPP and 3GPP2 functional entities are described in this specification.
+
+SRVCC from EUTRAN access to 3GPP2 1xCS is covered in this specification. Handling of non-voice component and SRVCC from 3GPP2 1xCS to EUTRAN direction is not specified in this release.
+
+SRVCC from EUTRAN/UTRAN (HSPA) access to 3GPP UTRAN/GERAN CS accesses for voice calls that are anchored in the IMS, as well as the coordination between the SRVCC for voice call and the handover of non-voice PS bearers, are covered in this specification. The handover of non-voice PS bearer from E-UTRAN is specified by the procedures defined in 3G TS 23.401, TS 23.060, TS 25.413 and TS 43.129. The handover of non-voice PS bearer from UTRAN (HSPA) is specified by the procedures defined in 3G TS 23.060, TS 25.413 and TS 43.129. Handling of SRVCC from 3GPP UTRAN/GERAN CS accesses to EUTRAN/UTRAN (HSPA) direction is not specified in this release. The handling of multiple simultaneous voice bearers with SRVCC is not supported in this release.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 216 | 11.10.0 | Published | 2013-12-18 | http://www.etsi.org/deliver/etsi_ts/123200_123299/123216/11.10.00/60/ts_123216v111000p.pdf |
+| ATIS | ATIS.3GPP.23.216V1180-2014 | 11.8.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.216(R11-11.8.0) | 11.8.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.216(R11-11.8.0) |
+| TTC | TS-3GA-23.216(Rel11)v11.10.0 | 11.10.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-23.216(Rel11)v11.10.0.pdf |
+
+### 10.3.21 TS 23.218 IP multimedia (IM) session handling; IM call model; Stage 2
+
+This document specifies the IP multimedia (IM) call model for handling of an IP multimedia session origination and termination for an IP multimedia subscriber.
+
+This document includes interactions between an application server and IP multimedia sessions.
+
+The IP multimedia (IM) subsystem Stage 2 is specified in TS 23.228, and the signalling flows for the IP multimedia call control based on SIP and SDP are specified in TS 24.228.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 218 | 11.6.0 | Published | 2013-07-04 | http://www.etsi.org/deliver/etsi_ts/123200_123299/123218/11.06.00_60/ts_123218v110600p.pdf |
+| ATIS | ATIS.3GPP.23.218V 1150-2014 | 11.5.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.218(R11-11.5.0) | 11.5.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-23.218(R11-11.5.0) |
+| TTC | TS-3GA-23.218(Rel11)v11.6.0 | 11.6.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.218(Rel11)v11.6.0.pdf |
+
+### 10.3.22 TS 23.221 Architectural requirements
+
+This document covers details the architectural requirements for the GSM in Iu mode and UMTS systems. In particular, it details the high-level requirements for the circuit-switched (CS) domain and the Stage 2 procedures that span more than one domain/subsystem within UMTS and GSM. The reference model to which these procedures apply can be found within 3G TS 23.002. In addition, A mode-to-Iu mode handover for CS services is addressed. Detailed architectural requirements within the subsystems are contained within the remainder of the 23 series of specifications; e.g., the requirements for the packet-switched (PS) domain are contained within 3G TS 23.060 and the requirements for the bearer independent CS core network are contained in 3G TS 23.205.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 221 | 11.2.0 | Published | 2013-06-27 | http://www.etsi.org/deliver/etsi_ts/123200_123299/123221/11.02.00_60/ts_123221v110200p.pdf |
+| ATIS | ATIS.3GPP.23.221V 1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.221(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-23.221(R11-11.1.0) |
+| TTC | TS-3GA-23.221(Rel11)v11.2.0 | 11.2.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.221(Rel11)v11.2.0.pdf |
+
+### 10.3.23 TS 23.226 Global text telephony (GTT); Stage 2
+
+This technical specification defines the Stage 2 description of the real-time text conversation feature called global text telephony (GTT). GTT Stage 2 identifies the functional capabilities needed to support the service described in GTT Stage 1.
+
+This document contains the core functions for a real-time text conversation feature GTT, to be used in combination with other media in conversational services.
+
+GTT offers real-time conversation in text, to be used alone or in combination with other conversational media, and interworking with current and emerging text conversation features in the fixed networks and other mobile networks.
+
+GTT uses a number of functional entities to realize the requirements of the Stage 1 description (TS 22.226). This document describes how the service requirements are realized with these functional entities. As far as possible, existing protocols shall be used for the realization of the global text telephony feature. This may include, e.g., SIP, 3G.324, or circuit-switched voice service as protocol environments, and cellular text telephone modem (CTM), AL1 and RTP/text as transmission protocols. It also means usage of existing text presentation format [Rec. ITU-T T.140], common to all GTT text conversation environments.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 226 | 11.0.0 | Published | 2012-09-25 | http://www.etsi.org/deliver/etsi_ts/123200_123299/123226/11.00.00_60/ts_123226v110000p.pdf |
+| ATIS | ATIS.3GPP.23.226V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.226(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-23.226(R11-11.0.0) |
+| TTC | TS-3GA-23.226(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.226(Rel11)v11.0.0.pdf |
+
+### 10.3.24 TS 23.228 IP multimedia subsystem (IMS); Stage 2
+
+This document defines the Stage 2 service description for the IP multimedia core network subsystem (IMS), which includes the elements necessary to support IP multimedia (IM) services in UMTS. [ITU-T I.130] describes a three-stage method for characterization of telecommunication services, and [ITU-T Q.65] defines Stage 2 of the method.
+
+This document does not cover the access network functionality except as they relate to provision of IM services. The TS 23.060 describes GPRS. GSM 03.64 contains an overall description of the GSM GPRS radio interface. TS 25.301 contains an overall description of the UMTS terrestrial radio access network.
+
+This document identifies the mechanisms to enable support for IP multimedia applications. In order to align IP multimedia applications wherever possible with non-3GPP IP applications, the general approach is to adopt non-3GPP-specific IP-based solutions.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.228 | 11.10.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/23/A23228-ba0.pdf |
+| ETSI | TS 123 228 | 11.10.0 | Published | 2013-12-18 | http://www.etsi.org/deliver/etsi_ts/123200_123299/123228/11.10.00_60/ts_123228v111000p.pdf |
+| ATIS | ATIS.3GPP.23.228V1170-2014 | 11.7.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.228(R11-11.7.0) | 11.7.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-23.228(R11-11.7.0) |
+| TTC | TS-3GA-23.228(Rel11)v11.10.0 | 11.10.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-23.228(Rel11)v11.10.0.pdf |
+
+### 10.3.25 TS 23.234 3GPP system to wireless local area network (WLAN) interworking; system description
+
+This document specifies system description for interworking between 3GPP systems and wireless local area networks (WLANs). The intent of 3GPP-WLAN interworking is to extend 3GPP services and functionality to the WLAN access environment. The 3GPP-WLAN interworking system provides bearer services allowing a 3GPP subscriber to use a WLAN to access 3GPP PS-based services.
+
+This specification defines a 3GPP system architecture and procedures to do the following:
+
+- Provide access, authentication and authorization (AAA) services to the 3GPP-WLAN interworking system based on subscription.
+- Provide access to the locally connected IP network (e.g., the Internet) if allowed by subscription.
+- Provide WLAN UEs with IP bearer capability to the operator's network and PS services, if allowed by subscription.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 234 | 11.0.0 | Published | 2012-09-25 | http://www.etsi.org/deliver/etsi_ts/123200_123299/123234/11.00.00_60/ts_123234v110000p.pdf |
+| ATIS | ATIS.3GPP.23.234V 1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.234(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-23.234(R11-11.0.0) |
+| TTC | TS-3GA-23.234(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.234(Rel11)v11.0.0.pdf |
+
+### 10.3.26 TS 23.236 Intra-domain connection of radio access network (RAN) nodes to multiple core network (CN) nodes
+
+This document covers the details for the intra-domain connection of RAN nodes to multiple CN nodes for GSM and UMTS systems. In particular, it details the impacts to GSM and UMTS systems and the Stage 2 procedures for the support of connecting a RNC or base station controller (BSC) to multiple MSC servers or SGSNs. The overall solution is described, and the detailed impacts on the existing specifications are identified.
+
+The reference model to which these procedures apply can be found within TS 23.002. Detailed architectural requirements within the subsystems are contained within the remainder of the 23 series of specifications, e.g., the requirements for the packet-switched (PS) domain are contained within TS 23.060, and the requirements for the bearer independent CS core network are contained in TS 23.205.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-23.236 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/23/A23236-b00.pdf |
+| ETSI | TS 123 236 | 11.0.0 | Published | 2012-11-14 | http://www.etsi.org/deliver/etsi_ts/123200_123299/123236/11.00.00/60/ts_123236v110000p.pdf |
+| ATIS | ATIS.3GPP.23.236V 1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.236(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.236(R11-11.0.0) |
+
+### 10.3.27 TS 23.237 IP Multimedia Subsystem (IMS) Service Continuity; Stage 2
+
+This document specifies the architectural requirements and procedures for delivery of IMS Service Continuity.
+
+3G TS 23.206 is migrated to this specification.
+
+The scope of the specification includes:
+
+- PS-CS service continuity using IMS Centralized Services (see 3G TS 23.292);
+- PS-PS service continuity;
+- PS-PS service continuity in conjunction with PS-CS service continuity;
+- Adding and/or removing media flows to support service.
+
+The solution is restricted to service continuity using IMS procedures, i.e., mobility mechanisms on the IP-CAN level are not within the scope of this specification.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 237 | 11.9.0 | Published | 2013-09-20 | http://www.etsi.org/deliver/etsi_ts/123200_123299/123237/11.09.00/60/ts_123237v110900p.pdf |
+| ATIS | ATIS.3GPP.23.237V 1170-2014 | 11.7.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.237(R11-11.7.0) | 11.7.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.237(R11-11.7.0) |
+| TTC | TS-3GA-23.237(Rel11)v11.9.0 | 11.9.0 | TTC Approved | 2013-11-22 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.237(Rel11)v11.9.0.pdf |
+
+### 10.3.28 TS 23.240 3GPP generic user profile (GUP); architecture (Stage 2)
+
+The objective of specifying the 3GPP generic user profile is to provide a conceptual description to enable harmonized usage of the user-related information located in different entities. Technically, the 3GPP generic user profile provides an architecture, data description and interface with mechanisms to handle the data.
+
+The present document defines the Stage 2 architecture description to the 3GPP generic user profile (GUP), which includes the elements necessary to realize the Stage 1 requirements in 3G TS 22.240.
+
+The present document includes the GUP reference architecture with descriptions of functional entities, and their interfaces and procedures, as well as the high-level information model for the GUP data.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 240 | 11.0.0 | Published | 2012-09-25 | http://www.etsi.org/deliver/etsi_ts/123200_123299/123240/11.00.00_60/ts_123240v110000p.pdf |
+| ATIS | ATIS.3GPP.23.240V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.240(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-23.240(R11-11.0.0) |
+| TTC | TS-3GA-23.240(Re11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.240(Re11)v11.0.0.pdf |
+
+### 10.3.29 TS 23.246 Multimedia broadcast/multicast service (MBMS); architecture and functional description
+
+The present document describes the Stage 2 description (architectural solution and functionalities) for the MBMS bearer service, which includes, together with MBMS user services defined in 3G TS 26.346, all the elements necessary to realize the Stage 1 requirements in 3G TS 22.146 and 3G TS 22.246.
+
+The present document also includes considerations on the manner in which user services should make use of the MBMS bearer service described herein.
+
+The present document includes information applicable to network operators, service providers and manufacturers.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 246 | 11.1.0 | Published | 2012-11-14 | http://www.etsi.org/deliver/etsi_ts/123200_123299/123246/11.01.00_60/ts_123246v110100p.pdf |
+| ATIS | ATIS.3GPP.23.246V1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.246(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-23.246(R11-11.1.0) |
+| TTC | TS-3GA-23.246(Re11)v11.1.0 | 11.1.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.246(Re11)v11.1.0.pdf |
+
+### 10.3.30 TS 23.251 Network sharing; architecture and functional description
+
+Network sharing is a way for operators to share the heavy deployment costs for mobile networks, especially in the roll-out phase. In the current mobile telephony marketplace, functionality that enables various forms of network sharing is becoming more and more important.
+
+Scenarios and user requirements are described in 3G TR 22.951, while the current document presents the Stage 2 details and descriptions of how these requirements are supported in a 3GPP network.
+
+The present document covers the details of network sharing. It shows how several core network operators can share one radio access network and details the impacts on the network architecture. All UEs shall comply with existing requirements, among them PLMN selection and system information reception. The present document defines additional requirements for network-sharing supporting UEs.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 251 | 11.6.0 | Published | 2013-12-18 | http://www.etsi.org/deliver/etsi_ts/123200_123299/123251/11_06_00_60/ts_123251v110600p.pdf |
+| ATIS | ATIS.3GPP.23.251V 1150-2014 | 11.6.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.251(R11-11.5.0) | 11.5.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.251(R11-11.5.0) |
+| TTC | TS-3GA-23.251(Rel11)v11.6.0 | 11.6.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-23.251(Rel11)v11.6.0.pdf |
+
+### 10.3.31 TS 23.259 Personal network management (PNM); Procedures and information flows; Stage 2
+
+This document provides the procedure details and the information flows for support of personal network management (PNM) including the PN UE redirection and PN access control applications enabled by personal network management.
+
+NOTE – This specification does not currently cover the Stage 1 requirements for PNE Networks specified in 3GPP TS 22.259.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 259 | 11.0.0 | Published | 2012-10-08 | http://www.etsi.org/deliver/etsi_ts/123200_123299/123259/11_00_00_60/ts_123259v110000p.pdf |
+| ATIS | ATIS.3GPP.23.259V 1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.259(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.259(R11-11.0.0) |
+| TTC | TS-3GA-23.259(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.259(Rel11)v11.0.0.pdf |
+
+### 10.3.32 TS 23.261 IP flow mobility and seamless wireless local area network (WLAN) offload; Stage 2
+
+This document specifies the Stage 2 system description for IP flow mobility between a 3GPP and a WLAN. The technical solution is based on the working principles of DSMIPv6 [IETF RFC 5555] and it is applicable to both the evolved packet system and the I-WLAN mobility architecture.
+
+The specification covers the system description of seamless WLAN offload and IP flow mobility between 3GPP and WLAN as well as the respective interactions with the PCC and ANDSF frameworks. The system description for non-seamless WLAN offload is covered in 3GPP TS 23.402.
+
+This document specifies also the detailed extensions to S2c and H1 reference points for IP flow mobility. The extensions to the PCC and to the ANDSF framework are specified respectively in 3GPP TS 23.203 and in 3GPP TS 23.402.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 261 | 11.0.0 | Published | 2012-09-25 | http://www.etsi.org/deliver/etsi_ts/123200_123299/123261/11.00.00_60/ts_123261v110000p.pdf |
+| ATIS | ATIS.3GPP.23.261V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.261(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.261(R11-11.0.0) |
+| TTC | TS-3GA-23.261(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.261(Rel11)v11.0.0.pdf |
+
+###### 10.3.33 TS 23.271 Functional stage 2 description of LCS
+
+The document specifies Stage 2 of the location services (LCS) feature in UMTS and GSM, which provides the mechanisms to support mobile location services for operators, subscribers and third party service providers.
+
+Location services may be considered as a network-provided enabling technology consisting of standardized service capabilities, which enable the provision of location applications. The application(s) may be service-provider specific. The description of the numerous and varied possible location applications which are enabled by this technology are outside the scope of this document. However, clarifying examples of how the functionality being described may be used to provide specific location services may be included.
+
+This Stage 2 service description covers the LCS system functional model for the whole system, the LCS system architecture, state descriptions, message flows, etc.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 271 | 11.2.0 | Published | 2013-04-05 | http://www.etsi.org/deliver/etsi_ts/123200_123299/123271/11.02.00_60/ts_123271v110200p.pdf |
+| ATIS | ATIS.3GPP.23.271V1120-2014 | 11.2.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.271(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.271(R11-11.2.0) |
+| TTC | TS-3GA-23.271(Rel11)v11.2.0 | 11.2.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.271(Rel11)v11.2.0.pdf |
+
+### 10.3.34 TS 23.272 Circuit switched (CS) fallback in evolved packet system (EPS); Stage 2
+
+This document defines the Stage 2 architecture and specification for the CS fallback for EPS. The scope of this document includes the architecture enhancements for functionality to enable fallback from E-UTRAN access to UTRAN/GERAN CS domain access and functionality to reuse of voice and other CS-domain services (e.g., CS UDI video / SMS/ LCS / USSD) by reuse of CS infrastructure.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 272 | 11.8.0 | Published | 2014-03-17 | http://www.etsi.org/deliver/etsi_ts/123200_123299/123272/11_08_00_60/ts_123272v110800p.pdf |
+| ATIS | ATIS.3GPP.23.272V1140-2014 | 11.4.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.272(R11-11.4.0) | 11.4.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.272(R11-11.4.0) |
+| TTC | TS-3GA-23.272(Rel11)v11.7.0 | 11.7.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-23.272(Rel11)v11.7.0.pdf |
+
+### 10.3.35 TS 23.327 Mobility between 3GPP-wireless local area network (WLAN) interworking and 3GPP systems
+
+This document specifies the stage 2 system description for providing mobility between 3GPP wireless local area network interworking (IWLAN) and 3GPP Systems. It is to define a technical solution based on the working principles of DSMIPv6 with necessary enhancement of the IWLAN architecture for supporting mobility and roaming between 3GPPWLAN interworking system and 3GPP systems so that ongoing 3GPP PS based services can be maintained with minimal impact on the end-user's perceived quality on the services at a change of the access network (between IWLAN and 3GPP access systems).
+
+The specification includes both non-roaming and roaming scenarios and covers all aspects, including mobility between 3GPP Systems and IWLAN with access authentication and charging.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 327 | 11.0.0 | Published | 2012-11-14 | http://www.etsi.org/deliver/etsi_ts/123300_123399/123327/11_00_00_60/ts_123327v110000p.pdf |
+| ATIS | ATIS.3GPP.23.327V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.327(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.327(R11-11.0.0) |
+| TTC | TS-3GA-23.327(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.327(Rel11)v11.0.0.pdf |
+
+### 10.3.36 TS 23.333 Multimedia resource function controller (MRFC) – Multimedia resource function processor (MRFP) Mp interface: Procedures descriptions
+
+This specification describes the functional requirements and information flows that generate procedures between the multimedia resource function controller (MRFC) and the multimedia resource function processor (MRFP), the Mp interface.
+
+This specification is limited to information flows relevant to the Mp interface; in order to define these procedures and make the functional requirements clear some triggers from an external interface may be described; these may be specified within the MR interface, for example, or within an AS in which the MRFC function resides. However, for the overall stage 2 procedures of IMS, see 3GPP TS 23.228.
+
+The protocol on the Mp interface is defined to comply with ITU-T H.248.1 gateway control protocol; see [ITU-T H.248.1]. The goal of this specification is to provide the input to defining a formal Profile within the ITU-T H.248 protocol toolbox specifically for the Mp application.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 333 | 11.1.0 | Published | 2013-02-13 | http://www.etsi.org/deliver/etsi_ts/123300_123399/123333/11.01.00_60/ts_123333v110100p.pdf |
+| ATIS | ATIS.3GPP.23.333V 1110-2014 | 11.1.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.333(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.333(R11-11.1.0) |
+| TTC | TS-3GA-23.333(Rel11)v11.1.0 | 11.1.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.333(Rel11)v11.1.0.pdf |
+
+### 10.3.37 TS 23.334 IP multimedia subsystem (IMS) application level gateway (IMS-ALG) – IMS access gateway (IMS-AGW) interface: Procedures descriptions
+
+Annex G of 3GPP TS 23.228 gives out an IMS application level gateway (IMS-ALG) and IMS access media gateway (IMS-AGW) based reference model to support NAT-PF, gate control and traffic policing between IP-CAN and IMS domain.
+
+
+
+The diagram shows the following components and connections:
+
+- UE** (User Equipment) is connected to **IP-CAN** (IP Connectivity Access Network).
+- IP-CAN** is connected to a **NAT** (Network Address Translation) device.
+- The **NAT** device is part of the **Media access domain**.
+- The **Media access domain** is connected to the **IMS access gateway** (IMS-AGW).
+- The **IMS access gateway** is connected to the **P-CSCF** (PDN Connectivity Server) via the **Iq** reference point.
+- The **P-CSCF** contains an **IMS-ALG** (IMS Application Level Gateway).
+- The **IMS-ALG** is connected to the **UE** via the **Gm** reference point.
+- A dashed box labeled **Scope of this specification** encloses the **IMS-ALG** and the **IMS access gateway**.
+- A bold horizontal line represents the **Media** path between the **Media access domain** and the **IMS access gateway**.
+- A dashed line represents the **IP signalling-path** between the **UE** and the **P-CSCF**.
+- A vertical line represents the **Iq control-path** between the **IMS-ALG** and the **IMS access gateway**.
+
+Diagram illustrating the reference model for Iq. It shows a UE connected to an IP-CAN, which is connected to a NAT. The NAT is connected to a Media access domain. The Media access domain is connected to an IMS access gateway (IMS-AGW). The IMS-AGW is connected to a P-CSCF (IMS-ALG) via an Iq interface. The P-CSCF (IMS-ALG) is connected to the UE via a Gm interface. The scope of this specification is indicated by a dashed box around the IMS-ALG and IMS-AGW.
+
+Figure 10.3.37-1 – Scope of the specification
+
+The Figure 10.3.37-1 illustrates the reference model for Iq:
+
+- the dashed line represents the IP signalling-path with SIP (at Gm) as call/session control protocol between the UE and the P-CSCF (IMS-ALG);
+- the bold, horizontal line represents the IP media-path (also known as (IP) bearer-path or (IP) data-path; the notion 'media' is used as generic term for "IP application data"); and
+- the vertical line represents the Iq control-path with ITU-T H.248 as gateway/policy control protocol between the IMS-ALG and the IMS-AGW (ITU-T H.248 messages are transported over IP).
+
+The Iq reference point is between the P-CSCF (IMS-ALG) and the IMS-AGW. It conveys the necessary information that is needed to allocate, modify and release (IP) transport addresses.
+
+The present document defines the Stage 2 description for the Iq reference point. The Stage 2 shall cover the information flow between the P-CSCF (IMS-ALG) and IMS-AGW. The protocol used over the Iq interface is the gateway control protocol according to Recommendation ITU-T H.248 (which is specified for Iq by an ITU-T H.248 profile according 3GPP TS 29.334).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 334 | 11.2.0 | Published | 2013-01-16 | http://www.etsi.org/deliver/etsi_ts/123300_123399/123334/11_02_00_60/ts_123334v110200p.pdf |
+| ATIS | ATIS.3GPP.23.334V1120-2014 | 11.2.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.334(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.334(R11-11.2.0) |
+| TTC | TS-3GA-23.334(Rel11)v11.2.0 | 11.2.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.334(Rel11)v11_2_0.pdf |
+
+### 10.3.38 TS 23.335 User data convergence (UDC); Technical realization and information flows; Stage 2
+
+This document describes procedures and signalling flows associated to the technical realization of the 3GPP user data convergence (UDC). It furthermore indicates some requirements for the stage 3 specifications.
+
+Special consideration is put in the following areas:
+
+- reference architecture for the UDC concept
+- general description of procedures for the user data manipulation (e.g., create, delete, update, etc.)
+- identification of the requirements on the UDC for the applicability of the mechanisms described in this document.
+
+User data convergence is an optional concept to ensure data consistency and simplify creation of new services by providing easy access to the user data, as well as to ensure the consistency of storage and data models and to have minimum impact on traffic mechanisms, reference points and protocols of network elements.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 335 | 11.0.0 | Published | 2012-10-24 | http://www.etsi.org/deliver/etsi_ts/123300_123399/123335/11_00_00_60/ts_123335v110000p.pdf |
+| ATIS | ATIS.3GPP.23.335V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.335(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.335(R11-11.0.0) |
+| TTC | TS-3GA-23.335(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-23.335(Rel11)v11_0_0.pdf |
+
+### 10.3.39 TS 23.401 General packet radio service (GPRS) enhancements for evolved universal terrestrial radio access network (E-UTRAN) access
+
+This document defines the Stage 2 service description for the evolved 3GPP packet switched domain – also known as the evolved packet system (EPS) in this document. The evolved 3GPP packet switched domain provides IP connectivity using the evolved universal terrestrial radio access network (E-UTRAN).
+
+The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between E-UTRAN and pre-E-UTRAN 3GPP radio access technologies, policy control and charging, and authentication.
+
+The Radio Access Network functionality is documented only to the extent necessary to describe the overall system. 3G TS 36.300 contains the overall description of the Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
+
+Recommendation ITU-T I.130 describes a three-stage method for characterisation of telecommunication services, and Recommendation ITU-T Q.65 defines Stage 2 of the method.
+
+3G TS 23.402 is a companion specification to this specification.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 401 | 11.9.0 | Published | 2014-03-17 | http://www.etsi.org/deliver/etsi_ts/123400_123499/123401/11_09.00/60/ts_123401v110900p.pdf |
+| ATIS | ATIS.3GPP.23.401V1150-2014 | 11.5.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.401(R11-11.5.0) | 11.5.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-23.401(R11-11.5.0) |
+| TTC | TS-3GA-23.401(Rel11)v11.8.0 | 11.8.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-23.401(Rel11)v11.8.0.pdf |
+
+### 10.3.40 TS 23.402 Architecture enhancements for non-3GPP accesses
+
+This document specifies the Stage 2 service description for providing IP connectivity using non-3GPP accesses to the Evolved 3GPP packet switched domain. In addition, for E-UTRAN and non-3GPP accesses, the specification describes the evolved 3GPP PS domain where the protocols between its core network elements are IETF-based.
+
+Recommendation ITU-T I.130 describes a three-stage method for characterisation of telecommunication services, and Recommendation ITU-T Q.65 defines Stage 2 of the method.
+
+The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between 3GPP and non 3GPP accesses, policy control and charging, and authentication, related to the usage of non-3GPP accesses.
+
+3G TS 23.401 covers architecture aspects common to the Evolved 3GPP Packet Switched domain.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 123 402 | 11.8.0 | Published | 2013-12-18 | http://www.etsi.org/deliver/etsi_ts/123400_123499/123402/11_08.00/60/ts_123402v110800p.pdf |
+| ATIS | ATIS.3GPP.23.402V1160-2014 | 11.6.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.402(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-23.402(R11-11.6.0) |
+| TTC | TS-3GA-23.402(Rel11)v11.8.0 | 11.8.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-23.402(Rel11)v11.8.0.pdf |
+
+### **10.3.41 TR 23.854 Enhancements for multimedia priority service (MPS)**
+
+MPS will enable national security/emergency preparedness (NS/EP) users (herein called service users) to make priority calls/sessions using the public networks. This service needs to be ensured also under special conditions such as network congestion. Service Users are the government-authorized personnel, emergency management officials and/or other authorized users. Effective disaster response and management rely on the service user's ability to communicate during congestion conditions. Service Users are expected to receive priority treatment, in support of mission critical multimedia communications.
+
+The enhancements for MPS evaluated in this document are priority aspects of EPS packet bearer services and priority related interworking between IMS and EPS packet bearer services. These enhancements enable the network to support end-to-end priority treatment for MPS call/session origination/termination, including the non access stratum (NAS) and access stratum (AS) signalling establishment procedures at originating/terminating network side as well as resource allocation in the core and radio networks for bearers. Priority treatment will be applicable to IMS based multimedia services, priority EPS bearer services and CS fallback.
+
+This document clarifies the architectural requirements for MPS, considers the priority service scenarios, and evaluates solution alternatives. Solutions will be proposed and evaluated based on the following three service categories: IMS based multimedia service (voice, video etc.), priority EPS bearer services (PS data without IMS interaction) and CS fallback. Common issues for multiple service categories should be resolved by single solution to limit the amount of overall functionality and to avoid complexity.
+
+The basic enhanced multimedia priority service (eMPS), i.e., priority handling of IMS based multimedia service, EPS bearer services and CS fallback have completed in Rel-10. In Rel-11, single radio voice call continuity (SRVCC) from LTE to UTRAN/GERAN/1xCS will be investigated based on Rel-10 SRVCC specification.
+
+The result of the analysis should be suitable as a basis for normative MPS specification work.
+
+The scope of the MPS part is to further investigate:
+
+- The signalling and procedures for identifying priority and authorizing the usage of priority service.
+- The required priority attributes used in enabling end-to-end priority marking and priority treatment during establishment, modification and release of an IMS based priority voice/video/data session.
+- The scenarios and capabilities for supporting priority EPS bearer data services.
+- The potential impacts on existing and relevant standard procedures in order to provide preferential treatment for MPS requests in the event of congestion.
+- Inter-working with other IMS and CS networks to provide an end-to-end priority service.
+
+### **10.3.42 TR 23.857 Study of evolved packet core (EPC) nodes restoration**
+
+The document contains the study on EPC nodes failure and restoration.
+
+This document will consider any necessary operational protocol recovery mechanisms in the EPS in order to restore the subscriber service in the event of EPC node failure or clean up the hanging resource in other EPC nodes if the recovery of the failed node is not possible. The document will address the following aspects:
+
+- list the different network failure scenarios to be analysed for EPC nodes: MME, S4-SGSN, SGW and PGW;
+- identify precisely the problems resulting from the current definition of the standards;
+- list various possible solutions;
+
+- identify pros and cons of possible solutions;
+- conclude on potential enhancements to the standards (depending on gains vs complexity).
+
+### 10.3.43 TR 23.903 Redial solution for voice-video switching
+
+This document describes the idle mode redial mechanism which 3GPP based systems can use to enhance switching between circuit switched voice and video services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TR 123 903 | 11.0.0 | Published | 2012-09-25 | http://www.etsi.org/deliver/etsi_tr/123900_123999/123903/11.00.00_60/tr_123903v110000p.pdf |
+| ATIS | ATIS.3GPP.23.903V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.903(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-23.903(R11-11.0.0) |
+| TTC | TR-3GA-23.903(Re11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TR/TR-3GA-23.903(Re11)v11.0.0.pdf |
+
+### 10.3.44 TR 23.919 Direct tunnel deployment guideline
+
+The present document contains deployment guidelines for the use of direct tunnelling of user plane data between the RNC and the GGSN (earlier known as the one tunnel approach).
+
+This report highlights the impacts of the 3GPP Release 7 direct tunnel solution to the current UMTS system in order to guide equipment development and network deployment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TR 123 919 | 11.0.0 | Published | 2012-09-25 | http://www.etsi.org/deliver/etsi_tr/123900_123999/123919/11.00.00_60/tr_123919v110000p.pdf |
+| ATIS | ATIS.3GPP.23.919V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.919(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-23.919(R11-11.0.0) |
+| TTC | TR-3GA-23.919(Re11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TR/TR-3GA-23.919(Re11)v11.0.0.pdf |
+
+### 10.3.45 TR 23.975 IPv6 migration guidelines
+
+The technical report identifies various scenarios of transition to IPv6 and co-existence of IPv4 and IPv6, deployment options and impacts on 3GPP network elements. In particular:
+
+- Identify the transition and co-existence scenarios of interest for operators and the respective assumptions and requirements.
+- Analyse existing IP address allocation mechanism for IPv6 migration if necessary.
+- Investigate IPv6 transition mechanisms for the scenarios identified during the study and investigate their applicability for 3GPP network, and identify the compatibility among applicable transition mechanisms.
+- Identify any impact on 3GPP network elements.
+
+- Provide recommendations on IPv6 transition and co-existence of IPv4 and IPv6 and identify if any normative work is needed.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TR 123 975 | 11.0.0 | Published | 2012-11-15 | http://www.etsi.org/deliver/etsi_tr/123900_123999/123975/11.00.00_60/tr_123975v110000p.pdf |
+| ATIS | ATIS.3GPP.23.975V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.975(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-23.975(R11-11.0.0) |
+| TTC | TR-3GA-23.975(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TR/TR-3GA-23.975(Rel11)v11.0.0.pdf |
+
+### 10.3.46 TR 23.976 Push architecture
+
+The purpose of this technical report is to analyse the service requirements for push services as defined in 3GPP TS 22.174 "Push service; Stage 1".
+
+This technical report describes methods for supporting push services by 3GPP delivery networks. The mechanisms described apply to existing delivery networks for the 3GPP packet-switched (PS) domain, circuit-switched (CS) domain, IP multimedia core network subsystem (IMS), multimedia broadcast/multicast service (MBMS), and wireless local area network (WLAN). Any necessary changes identified during this work will be introduced by means of change requests to the appropriate specifications.
+
+The definition of push functionality that applies to push application servers is outside the scope of this work. The definition of push functionality that is best implemented in push application servers such as a push proxy and push initiator will be undertaken by other standards bodies and industry forums.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TR 123 976 | 11.0.0 | Published | 2012-09-25 | http://www.etsi.org/deliver/etsi_tr/123900_123999/123976/11.00.00_60/tr_123976v110000p.pdf |
+| ATIS | ATIS.3GPP.23.976V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.976(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-23.976(R11-11.0.0) |
+| TTC | TR-3GA-23.976(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TR/TR-3GA-23.976(Rel11)v11.0.0.pdf |
+
+### 10.3.47 TR 23.979 3GPP enablers for open mobile alliance (OMA) push-to-talk over cellular (PoC) services; Stage 2
+
+The present document studies the architectural requirements in order to enable services like PoC over 3GPP systems. The report looks into aspects of using 3GPP PS domain and radio access technologies (GERAN, UTRAN) for bearer services and IMS for reachability and connectivity for applications like PoC.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TR 123 979 | 11.0.0 | Published | 2012-09-25 | http://www.etsi.org/deliver/etsi_tr/123900_123999/123979/11.00.00_60/tr_123979v110000p.pdf |
+| ATIS | ATIS.3GPP.23.979V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.979(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.979(R11-11.0.0) |
+| TTC | TR-3GA-23.979(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TR/TR-3GA-23.979(Rel11)v11.0.0.pdf |
+
+### 10.3.48 TR 23.981 Interworking aspects and migration scenarios for IPv4-based IMS implementations
+
+3GPP specifications design the IMS to use exclusively IPv6; however, early IMS implementations and deployments may use IPv4, as specified in clause 5.1 of 3G TS 23.221. Therefore, it is understood that there will exist IPv4-based IMS implementations, namely initial IMS implementations and IMS implementations based on 3GPP2 specifications. This is the motivation to study interworking and migration scenarios related to IPv4-based IMS implementations.
+
+The present document studies interworking and migration scenarios related to IPv4-based IMS implementations. The study provides guidelines for operators and vendors on interworking aspects of IPv4-based IMS implementations, and provides guidelines on migrating to 3GPP IMS using IPv6.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TR 123 981 | 11.0.0 | Published | 2012-09-25 | http://www.etsi.org/deliver/etsi_tr/123900_123999/123981/11.00.00_60/tr_123981v110000p.pdf |
+| ATIS | ATIS.3GPP.23.981V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-23.981(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-23.981(R11-11.0.0) |
+| TTC | TR-3GA-23.981(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TR/TR-3GA-23.981(Rel11)v11.0.0.pdf |
+
+## 10.4 24-series, Signalling protocols – user equipment to network
+
+### 10.4.1 TS 24.007 Mobile radio interface signalling layer 3 – General aspects
+
+The document defines the principal architecture of layer 3 and its sublayers on the GSM Um interface, i.e., the interface between mobile station (MS) and network; for the configuration management (CM) sublayer, the description is restricted to paradigmatic examples, call control, supplementary services, and short message services for non-GPRS services. It also defines the basic message format and error handling applied by the layer 3 protocols.
+
+For non-GPRS services, the communication between sublayers and adjacent layers and the services provided by the sublayers are distributed by use of abstract service primitives. But only externally observable behaviour resulting from the description is normatively prescribed by this document.
+
+For GPRS services, in addition, the local information transfer and stimuli sent between sublayers is informatively included within Annex C of the document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 007 | 11.0.0 | Published | 2012-11-15 | http://www.etsi.org/deliver/etsi_ts/124000_124099/124007/11.00.00/60/ts_124007v110000p.pdf |
+| ATIS | ATIS.3GPP.24.007V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.007(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-24.007(R11-11.0.0) |
+| TTC | TS-3GA-24.007(Re11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.007(Re11)v11.0.0.pdf |
+
+#### 10.4.2 TS 24.008 Mobile radio interface layer 3 specification; Core network protocols; Stage 3
+
+The document specifies the procedures used at the radio interface core network protocols within the 3rd generation mobile telecommunications system and the digital cellular telecommunications system.
+
+It specifies the procedures used at the radio interface (reference point Um or Uu, see TS 24.002 or TS 23.002) for Call Control (CC), mobility management (MM), and session management (SM).
+
+These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The control channels are described in TS 44.003 and TS 25.301.
+
+The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in TS 24.007.
+
+The procedures currently described in this TS are for the call control of circuit-switched connections, session management for GPRS services, mobility management and radio resource management for circuit-switched and GPRS services.
+
+TS 24.010 contains functional procedures for support of supplementary services.
+
+TS 24.011 contains functional procedures for support of point-to-point short message services.
+
+TS 24.012 contains functional description of short message – cell broadcast.
+
+TS 44.060 contains procedures for radio link control and medium access control (RLC/MAC) of packet data physical channels.
+
+TS 24.071 contains functional descriptions and procedures for support of location services.
+
+NOTE – "layer 3" includes the functions and protocols described in this Technical Specification. The terms "data link layer" and "layer 2" are used interchangeably to refer to the layer immediately below layer 3.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 008 | 11.10.0 | Published | 2014-03-20 | http://www.etsi.org/deliver/etsi_ts/124000_124099/124008/11.10.00_60/ts_124008v111000p.pdf |
+| ATIS | ATIS.3GPP.24.008V1160-2014 | 11.6.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.008(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-24.008(R11-11.6.0) |
+| TTC | TS-3GA-24.008(Rel11)v11.9.0 | 11.9.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-24.008(Rel11)v11.9.0.pdf |
+
+#### 10.4.3 TS 24.010 Mobile radio interface layer 3 – Supplementary services specification – General aspects
+
+The document gives the general aspects of the specification of supplementary services at the layer 3 radio interface.
+
+TS 24.08x and 24.09xseries specify the procedures used at the radio interface (reference point Um as defined in TS 24.002) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
+
+TS 44.008 and TS 24.080 specify the formats and coding for the supplementary services.
+
+Definitions and descriptions of supplementary services are given in TS 22.004 and TS 22.08x and 22.09xseries.
+
+Technical realization of supplementary services is described in TS 23.011 and GSM 23.08x and 23.09xseries.
+
+The procedures for call control, mobility management and radio resource management at the layer 3 radio interface are defined in TS 24.007 and TS 44.008.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 010 | 11.0.0 | Published | 2012-10-25 | http://www.etsi.org/deliver/etsi_ts/124000_124099/124010/11.00.00_60/ts_124010v110000p.pdf |
+| ATIS | ATIS.3GPP.24.010V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.010(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-24.010(R11-11.0.0) |
+| TTC | TS-3GA-24.010(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.010(Rel11)v11.0.0.pdf |
+
+#### 10.4.4 TS 24.011 Point-to-point (PP) short message service (SMS) support on mobile radio interface
+
+The document specifies the procedures used across the mobile radio interface by the signalling layer 3 function short message control (SMC) and short message relay layer (SM-RL) for both circuit switched in A/Gb mode and GPRS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 011 | 11.1.0 | Published | 2012-10-08 | http://www.etsi.org/deliver/etsi_ts/124000_124099/124011/11.01.00_60/ts_124011v110100p.pdf |
+| ATIS | ATIS.3GPP.24.011V1110-2014 | 11.1.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.011(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-24.011(R11-11.1.0) |
+| TTC | TS-3GA-24.011(Rel11)v11.1.0 | 11.1.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.011(Rel11)v11.1.0.pdf |
+
+#### 10.4.5 TS 24.030 Location services LCS; Supplementary service operations; Stage 3
+
+The document gives the Stage 3 description of the location service (LCS) operations for mobile station. These operations shall apply to both CS and PS domain.
+
+The group of location services operations is divided into two different classes:
+
+- Network-initiated location services operations;
+- Mobile-initiated location services operations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 030 | 11.0.0 | Published | 2012-10-25 | http://www.etsi.org/deliver/etsi_ts/124000_124099/124030/11.00.00_60/ts_124030v110000p.pdf |
+| ATIS | ATIS.3GPP.24.030V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.030(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-24.030(R11-11.0.0) |
+| TTC | TS-3GA-24.030(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.030(Rel11)v11.0.0.pdf |
+
+#### 10.4.6 TS 24.080 Mobile radio interface Layer 3 supplementary service specification – Formats and coding
+
+The document contains the coding of information necessary for the support of supplementary service operation on the mobile radio interface layer 3.
+
+This document gives the functional definitions and contents of messages for call-independent supplementary service operations. Messages necessary for the support of call-related supplementary service operations are defined in TS 24.008.
+
+This document gives the general format and coding for messages used for call-independent supplementary service and the format and coding of information elements used for both call-related and call-independent supplementary service operations.
+
+This document gives the specification of the call-related and call-independent supplementary service operations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 080 | 11.0.0 | Published | 2012-10-25 | http://www.etsi.org/deliver/etsi_ts/124000_124099/124080/11.00.00_60/ts_124080v110000p.pdf |
+| ATIS | ATIS.3GPP.24.080V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.080(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-24.080(R11-11.0.0) |
+| TTC | TS-3GA-24.080(Re11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.080(Re11)v11.0.0.pdf |
+
+#### 10.4.7 TS 24.109 Bootstrapping interface (Ub) and network application function interface (Ua); Protocol details
+
+The present document defines Stage 3 for the HTTP Digest AKA [IETF RFC 3310: "*Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)*".] based implementation of Ub interface (UE-BSF) and the HTTP Digest [IETF RFC 2617: "*HTTP Authentication: Basic and Digest Access Authentication*"] and the PSK TLS [IETF RFC 4279: "*Pre-Shared Key Ciphersuites for Transport Layer Security (TLS)*"] based implementation of bootstrapped security association usage over Ua interface (UE-NAF) in generic authentication architecture (GAA) as specified in 3G TS 33.220. The purpose of the Ub interface is to create a security association between UE and BSF for further usage in GAA applications. The purpose of the Ua interface is to use the so created bootstrapped security association between UE and NAF for secure communication.
+
+The present document also defines Stage 3 for the authentication proxy usage as specified in 3G TS 33.222.
+
+The present document also defines Stage 3 for the subscriber certificate enrolment, as specified in 3G TS 33.221, which is one realization of the Ua interface. The subscriber certificate enrolment uses the HTTP Digest-based implementation of bootstrapped security association usage to enrol a subscriber certificate and the delivery of a CA certificate.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 109 | 11.4.0 | Published | 2014-03-20 | http://www.etsi.org/deliver/etsi_ts/124100_124199/124109/11.04.00_60/ts_124109v110400p.pdf |
+| ATIS | ATIS.3GPP.24.109V1120-2014 | 11.2.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.109(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-24.109(R11-11.2.0) |
+| TTC | TS-3GA-24.109(Re11)v11.3.0 | 11.3.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-24.109(Re11)v11.3.0.pdf |
+
+#### 10.4.8 TS 24.135 Multicall supplementary service; Stage 3
+
+The document gives the Stage 3 description of the multicall (MC) supplementary service. The document specifies the procedures used by the radio interface for normal operation, registration and interrogation of the multicall supplementary service. Provision, withdrawal, erasure, activation and deactivation of supplementary services is an administrative matter between the mobile subscriber and the service provider and causes no signalling on the radio interface.
+
+3G TS 24.010 describes the general aspects of the specification of supplementary services at the layer 3 radio interface.
+
+3G TS 24.080 specifies the formats and coding for the supplementary services.
+
+Definitions and descriptions of supplementary services are given in 3G TS 22.004, 3G TS 22.072, 3G TS 22.08x, 3G TS 22.09x-series and 3G TS 22.135. 3G TS 22.135 is related specifically to the Multicall supplementary service.
+
+The technical realization of supplementary services are described in 3G TS 23.011, 3G TS 23.072, 3G TS 23.08x, 23.09x-series and 3G TS 23.135. 3G TS 23.135 is related specifically to the Multicall supplementary service.
+
+The procedures for call control and mobility management at the layer 3 radio interface are defined in 3G TS 24.007 and 3G TS 24.008.
+
+The following supplementary services are described in this document:
+
+- Multicall (MC).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 135 | 11.0.0 | Published | 2012-10-25 | http://www.etsi.org/deliver/etsi_ts/124100_124199/124135/11.00.00_60/ts_124135v110000p.pdf |
+| ATIS | ATIS.3GPP.24.135V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.135(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-24.135(R11-11.0.0) |
+| TTC | TS-3GA-24.135(Re11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.135(Re11)v11.0.0.pdf |
+
+#### 10.4.9 TS 24.139 3GPP system – fixed broadband access network interworking; Stage 3
+
+The document specifies the UE – EPC procedures for accessing 3GPP evolved packet core (EPC) via a fixed broadband access network.
+
+The specification covers the Support of QoS, Tunnel management procedures including the support of NAT traversal, and non-seamless offloading impacts.
+
+The document is applicable to the UE and the network. In this technical specification the network is the 3GPP EPC.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 139 (2015-01) | 11.4.0 | Published | 2015-01-13 | http://www.etsi.org/deliver/etsi_ts/124100_124199/124139/11.04.00_60/ts_124139v110400p.pdf |
+| TTA | TTAT.3G-24.139(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-24.139(R11-11.2.0) |
+| TTC | TS-3GA-24.139(Re11)v11.3.0 | 11.3.0 | TTC
Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.139(Re11)v11.3.0.pdf |
+
+#### 10.4.10 TS 24.167 3GPP IMS management object (MO); Stage 3
+
+This document defines a mobile device 3GPP IMS management object. The management object is compatible with open mobile alliance (OMA) device management protocol specifications, version 1.2 and upwards, and is defined using the OMA DM device description framework.
+
+The 3GPP IMS management object consists of relevant parameters that can be managed for the IM CN subsystem. This includes the basic framework defined in 3GPP TS 23.228 and 3GPP TS 24.229, and early IMS as defined in 3GPP TS 23.221.
+
+The IMS management object defines a repository of data into the ME including parameters that are provisioned from the ISIM application (i.e., 3GPP TS 31.103) or, after derivation, from the USIM application (i.e., 3GPP TS 31.102).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 167 | 11.0.1 | Published | 2013-01-14 | http://www.etsi.org/deliver/etsi_ts/124100_124199/124167/11.00.01_60/ts_124167v110001p.pdf |
+| ATIS | ATIS.3GPP.24.167V 1101-2014 | 11.0.1 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.167(R11-11.0.1) | 11.0.1 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-24.167(R11-11.0.1) |
+| TTC | TS-3GA-24.167(Rel11)v11.0.1 | 11.0.1 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.167(Rel11)v11.0.1.pdf |
+
+#### 10.4.11 TS 24.171 Control plane location services (LCS) procedures in the evolved packet system (EPS)
+
+This document specifies the operations and information coding for the non-access stratum (NAS) layer protocol for supporting the location services (LCS) in the evolved universal terrestrial radio access network (E-UTRAN).
+
+The document is applicable to the user equipment (UE) and to the mobility management entity (MME) in the evolved packet system (EPS). It is developed in accordance to the general principles stated in 3GPP TS 23.271.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 171 | 11.0.0 | Published | 2012-10-25 | http://www.etsi.org/deliver/etsi_ts/124100_124199/124171/11.00.00_60/ts_124171v110000p.pdf |
+| ATIS | ATIS.3GPP.24.171V 1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.171(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-24.171(R11-11.0.0) |
+| TTC | TS-3GA-24.171(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.171(Rel11)v11.0.0.pdf |
+
+#### 10.4.12 TS 24.173 IMS multimedia telephony communication service and supplementary services; Stage 3
+
+The present document provides the protocol details for multimedia telephony communication service and associated supplementary services in the IP multimedia (IM) core network (CN) subsystem based on the requirements from 3GPP TS 22.173.
+
+Multimedia telephony and supplementary services allow users to establish communications between them and enrich that by enabling supplementary services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 173 | 11.5.0 | Published | 2013-04-11 | http://www.etsi.org/deliver/etsi_ts/124100_124199/124173/11.05.00_60/ts_124173v110500p.pdf |
+| ATIS | ATIS.3GPP.24.173V1150-2014 | 11.5.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.173(R11-11.5.0) | 11.5.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-24.173(R11-11.5.0.) |
+| TTC | TS-3GA-24.173(Re11)v11.5.0 | 11.5.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.173(Re11)v11.5.0.pdf |
+
+#### 10.4.13 TS 24.216 Communication continuity management object (MO)
+
+This document defines the communication continuity management object. The management object is compatible with OMA device management protocol specifications, version 1.2 and upwards, and is defined using the OMA DM device description framework.
+
+The communication continuity management object consists of relevant parameters that can be managed for communication continuity capabilities.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 216 | 11.1.0 | Published | 2013-01-18 | http://www.etsi.org/deliver/etsi_ts/124200_124299/124216/11.01.00_60/ts_124216v110100p.pdf |
+| ATIS | ATIS.3GPP.24.216V1110-2014 | 11.1.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.216(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-24.216(R11-11.1.0) |
+| TTC | TS-3GA-24.216(Re11)v11.1.0 | 11.1.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.216(Re11)v11.1.0.pdf |
+
+#### 10.4.14 TS 24.229 IP multimedia call control protocol based on SIP and SDP; Stage 3
+
+This document defines a call control protocol for use in the IP multimedia (IM) core network (CN) subsystem based on the session initiation protocol (SIP), and the associated session description protocol (SDP).
+
+This document is applicable to:
+
+- the interface between the user equipment (UE) and the call session control function (CSCF);
+- the interface between the CSCF and any other CSCF;
+
+- the interface between the CSCF and an application server (AS);
+- the interface between the CSCF and the media gateway control function (MGCF);
+- the interface between the S-CSCF and the media resource function controller (MRFC)
+- the interface between the CSCF and the breakout gateway control function (BGCF);
+- the interface between the BGCF and the MGCF;
+- the interface between the BGCF and any other BGCF; and
+- the interface between the CSCF and an external multimedia IP network.
+
+Where possible, this document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP and SDP. Where this is not possible, extensions to SIP and SDP are defined within this document. The document has therefore been structured in order to allow both forms of specification.
+
+As the IM CN subsystem is designed to interwork with different IP-connectivity access networks (IP-CANs), the IP-CAN independent aspects of the IM CN subsystem are described in the main body and Annex A of this specification. Aspects for connecting a UE to the IM CN subsystem through specific types of IP-CANs are documented separately in the annexes or in separate documents.
+
+NOTE – This document covers only the usage of SIP and SDP to communicate with the entities of the IM CN subsystem. It is possible, and not precluded, to use the capabilities of GPRS to allow a terminal containing a SIP UA to communicate with SIP servers or SIP UAs outside the IM CN subsystem, and therefore utilize the services provided by those SIP servers. The usage of SIP and SDP for communicating with SIP servers or SIP UAs outside the IM CN subsystem is outside the scope of this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 229 | 11.11.0 | Published | 2014-04-08 | http://www.etsi.org/deliver/etsi_ts/124200_124299/124229/11.11.00/60/ts_124229v111100p.pdf |
+| ATIS | ATIS.3GPP.24.229V1170-2014 | 11.7.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.229(R11-11.7.0) | 11.7.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT_3G-24.229(R11-11.7.0) |
+| TTC | TS-3GA-24.229(Rel11)v11.9.0 | 11.9.0 | TTC Approved | 2013-11-22 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.229(Rel11)v11.9.0.pdf |
+
+#### **10.4.15 TS 24.234 3GPP system to wireless local area network (WLAN) interworking; User equipment (UE) to network protocols; Stage 3**
+
+The present document specifies the network selection, including authentication and access authorization procedures used for the interworking of the 3GPP system and WLANs. In addition to these, the present document also specifies the tunnel management procedures used for establishing an end-to-end tunnel from the WLAN UE to the 3GPP network via the Wu reference point.
+
+The present document is applicable to the WLAN user equipment (UE) and the network. In this technical specification, the network includes the WLAN and 3GPP network.
+
+Tunnel management signalling is carried between WLAN-UE and WLAN by WLAN access technology-specific protocols; however, this signalling is transparent to the WLAN.
+
+Details of the security framework for the end-to-end tunnel establishment are covered in 3G TS 33.234. The transport of the tunnel management signalling between WLAN and
+
+3GPP network and within the 3GPP network (i.e., PDG, 3GPP AAA server and WAG) are covered in 3G TS 29.234.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 234 | 11.3.0 | Published | 2012-11-16 | http://www.etsi.org/deliver/etsi_ts/124200_124299/124234/11_03_00_60/ts_124234v110300p.pdf |
+| ATIS | ATIS.3GPP.24.234V 1130-2014 | 11.3.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.234(R11-11.3.0) | 11.3.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-24.234(R11-11.3.0) |
+| TTC | TS-3GA-24.234(Rel11)v11.3.0 | 11.3.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.234(Rel11)v11.3.0.pdf |
+
+#### 10.4.16 TS 24.238 Session initiation protocol (SIP) based user configuration; Stage 3
+
+This document provides a session initiation protocol (SIP) based protocol framework that serves as a means of user configuration of supplementary services in the IP multimedia (IM) core network (CN) subsystem. The protocol framework relies upon the contents of the request-URI in a SIP INVITE request to enable basic configuration of services without requiring use of the Ut interface.
+
+The document is applicable to user equipment (UE) and application servers (AS) which are intended to support user configuration of supplementary services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 238 | 11.2.0 | Published | 2013-04-11 | http://www.etsi.org/deliver/etsi_ts/124200_124299/124238/11_02_00_60/ts_124238v110200p.pdf |
+| ATIS | ATIS.3GPP.24.238V 1120-2014 | 11.2.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.238(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-24.238(R11-11.2.0) |
+| TTC | TS-3GA-24.238(Rel11)v11.2.0 | 11.2.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.238(Rel11)v11.2.0.pdf |
+
+#### 10.4.17 TS 24.259 Personal network management (PNM); Stage 3
+
+Personal network management (PNM) is a home network-based application and provides the home network-based management of personal network (PN) consisting of multiple devices belonging to a single user, as described in 3GPP TS 22.259 and 3GPP TS 23.259.
+
+This document provides protocol details for enabling personal network management (PNM) services in the IP multimedia (IM) core network (CN) subsystem, based on the protocols of XML configuration access protocol (XCAP), session initiation protocol (SIP) and the session description protocol (SDP). Further, it provides protocol details for enabling PNM services in circuit switched (CS) domain, based on the protocols of CAP, MAP, ISUP, USSD and BICC.
+
+The document is applicable to user equipment (UEs) and application servers (AS) providing PNM capabilities. It makes no PNM specific enhancements to SIP, SIP events or SDP specified in 3GPP TS 24.229, neither has it made any PNM specific enhancements to CAP, MAP, ISUP, USSD and BICC.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 259 | 11.4.0 | Published | 2014-03-20 | http://www.etsi.org/deliver/etsi_ts/124200_124299/124259/11_04_00_60/ts_124259v110400p.pdf |
+| ATIS | ATIS.3GPP.24.259V 1110-2014 | 11.1.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.259(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-24.259(R11-11.1.0) |
+| TTC | TS-3GA-24.259(Rel11)v11.3.0 | 11.3.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-24.259(Rel11)v11.3.0.pdf |
+
+#### 10.4.18 TS 24.285 Allowed closed subscriber group (CSG) list; Management object (MO)
+
+This document specifies an allowed closed subscriber group (CSG) list management object (MO).
+
+The allowed CSG list MO is compatible with the OMA device management (DM) protocol specifications, version 1.2 and upwards, and is defined using the OMA DM device description framework (DDF).
+
+The allowed CSG list MO consists of relevant parameters for that can be used by the UE to select the appropriate CSG cell based on its subscription.
+
+The allowed CSG List MO defines the relevant parameters related to the allowed CSG List and to the operator CSG List.
+
+The usage of the allowed CSG List for in the idle mode process and the mobility management procedure is defined in 3GPP TS 23.122, 3GPP TS 24.008 and 3GPP TS 24.301.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 285 | 11.0.0 | Published | 2012-10-08 | http://www.etsi.org/deliver/etsi_ts/124200_124299/124285/11_00_00_60/ts_124285v110000p.pdf |
+| ATIS | ATIS.3GPP.24.285V 1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.285(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-24.285(R11-11.0.0) |
+| TTC | TS-3GA-24.285(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.285(Rel11)v11.0.0.pdf |
+
+#### 10.4.19 TS 24.301 Non-access-stratum (NAS) protocol for evolved packet system (EPS); Stage 3
+
+This document specifies the procedures used by the protocols for mobility management and session management between user equipment (UE) and mobility management entity (MME) in the evolved packet system (EPS). These protocols belong to the non-access stratum (NAS).
+
+The EPS mobility management (EMM) protocol defined in the present document provides procedures for the control of mobility when the user equipment (UE) is using the evolved UMTS terrestrial radio access network (E-UTRAN). The EMM protocol also provides control of security for the NAS protocols.
+
+The EPS session management (ESM) protocol defined in the present document provides procedures for the handling of EPS bearer contexts. Together with the bearer control provided by the access stratum, this protocol is used for the control of user plane bearers.
+
+For both NAS protocols the present document specifies procedures for the support of inter-system mobility between EUTRAN and other 3GPP or non-3GPP access networks:
+
+- For inter-system mobility between E-UTRAN and GERAN or UTRAN, this includes rules for a mapping between parameters and procedures used by the NAS protocols defined in the present document and the NAS protocols specified in 3GPP TS 24.008.
+- For inter-system mobility between E-UTRAN and generic non-3GPP access networks, this includes specific NAS procedures to maintain IP connectivity to the PDN gateway and to provide parameters needed by the UE when using mobility management based on dual-stack mobile IPv6 (see 3GPP TS 24.303) or MIPv4 (see 3GPP TS 24.304).
+
+The present document is applicable to the UE and to the mobility management entity (MME) in the EPS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 301 | 11.10.0 | Published | 2014-03-20 | http://www.etsi.org/deliver/etsi_ts/124300_124399/124301/11.10.00_60/ts_124301v111000p.pdf |
+| ATIS | ATIS.3GPP.24.301V1160-2014 | 11.6.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.301(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-24.301(R11-11.6.0) |
+| TTC | TS-3GA-24.301(Rel11)v11.9.0 | 11.9.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-24.301(Rel11)v11.9.0.pdf |
+
+#### 10.4.20 TS 24.302 Access to the evolved packet core (EPC) via non-3GPP access networks; Stage 3
+
+This document specifies the discovery and network selection procedures for access to 3GPP evolved packet core (EPC) via non-3GPP access networks and includes authentication and access authorization using authentication, authorization and accounting (AAA) procedures used for the interworking of the 3GPP EPC and the non-3GPP access networks.
+
+The document also specifies the tunnel management procedures used for establishing an end-to-end tunnel from the UE to the ePDG to the point of obtaining IP connectivity and includes the selection of the IP mobility mode.
+
+The non-3GPP access networks considered in this present document are cdma2000® HRPD and worldwide interoperability for microwave access (WiMAX), and any access technologies covered in 3GPP TS 23.402. These non-3GPP access networks can be trusted or untrusted access networks.
+
+This document is applicable to the UE and the network. In this technical specification the network is the 3GPP EPC.
+
+NOTE – cdma2000® is a registered trademark of the telecommunications industry association (TIA-USA).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 302 | 11.7.0 | Published | 2013-07-04 | http://www.etsi.org/deliver/etsi_ts/124300_124399/124302/11.07.00_60/ts_124302v110700p.pdf |
+| ATIS | ATIS.3GPP.24.302V 1160-2014 | 11.6.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.302(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-24.302(R11-11.6.0) |
+| TTC | TS-3GA-24.302(Re11)v11.7.0 | 11.7.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.302(Re11)v11.7.0.pdf |
+
+#### 10.4.21 TS 24.303 Mobility management based on dual-stack mobile IPv6; Stage 3
+
+This document specifies the signalling procedures for accessing the 3GPP evolved packet core network and handling the mobility between 3GPP and non-3GPP accesses via the S2c reference point defined in 3GPP TS 23.402.
+
+The document is applicable to the user equipment (UE) and the network node implementing the home agent functionality.
+
+In addition, the document specifies the procedures used for the DSMIPv6 home agent discovery, for bootstrapping the DSMIPv6 security association between the UE and the home agent and for managing the DSMIPv6 tunnel. The specification of these procedures is compliant to IETF RFCs.
+
+DSMIPv6 procedures can be used independently of the underlying access technology.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 303 | 11.3.0 | Published | 2013-07-04 | http://www.etsi.org/deliver/etsi_ts/124300_124399/124303/11.03.00_60/ts_124303v110300p.pdf |
+| ATIS | ATIS.3GPP.24.303V 1120-2014 | 11.2.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.303(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-24.303(R11-11.2.0) |
+| TTC | TS-3GA-24.303(Re11)v11.3.0 | 11.3.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.303(Re11)v11.3.0.pdf |
+
+#### 10.4.22 TS 24.304 Mobility management based on Mobile IPv4; User Equipment (UE) – foreign agent interface; Stage 3
+
+This document describes Stage 3 aspects of mobility management for user equipment (UE) using IETF Mobile IPv4 foreign agent mode to access the evolved packet core network (EPC) through trusted non-3GPP access networks and for mobility management of UE between the 3GPP access network and trusted non-3GPP access networks.
+
+In particular, the document describes the UE – Mobile IPv4 foreign agent (FA) interface stage 3 aspects, where the FA functionality is located within the access network in the non-3GPP access domain.
+
+This document is applicable to the user equipment and the network node implementing the FA functionality.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 304 | 11.0.0 | Published | 2012-10-08 | http://www.etsi.org/deliver/etsi_ts/124300_124399/124304/11.00.00_60/ts_124304v110000p.pdf |
+| ATIS | ATIS.3GPP.24.304V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.304(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-24.304(R11-11.0.0) |
+| TTC | TS-3GA-24.304(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.304(Rel11)v11.0.0.pdf |
+
+#### 10.4.23 TS 24.305 Selective disabling of 3GPP user equipment capabilities (SDoUE) management object (MO)
+
+This present document specifies a mobile device selective disabling of 3GPP UE capabilities (SDoUE) management object (MO) and the rules and corresponding behaviour of the UE with regard to the selective disabling of 3GPP UE capabilities, for example, when services or functions are disabled/enabled.
+
+The SDoUE MO is compatible with the OMA device management (DM) protocol specifications, version 1.2 and upwards, and is defined using the OMA DM device description framework (DDF).
+
+The SDoUE MO consists of the relevant parameters that can be managed for selective disabling of 3GPP UE capabilities.
+
+The SDoUE MO defines a repository of data into the ME.
+
+The service requirements for selective disabling of 3GPP UE capabilities are defined in 3GPP TS 22.011.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 305 | 11.0.0 | Published | 2012-11-16 | http://www.etsi.org/deliver/etsi_ts/124300_124399/124305/11.00.00_60/ts_124305v110000p.pdf |
+| ATIS | ATIS.3GPP.24.305V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.305(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-24.305(R11-11.0.0) |
+| TTC | TS-3GA-24.305(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.305(Rel11)v11.0.0.pdf |
+
+#### 10.4.24 TS 24.312 Access network discovery and selection function (ANDSF) management object (MO)
+
+This document defines management objects that can be used by the access network discovery and selection function (ANDSF) and the UE.
+
+The management object (MO) is compatible with the OMA device management (DM) protocol specifications, version 1.2 and upwards, and is defined using the OMA DM device description framework (DDF).
+
+The MO consists of relevant parameters for intersystem mobility policy- and access network discovery information that can be managed by the ANDSF.
+
+The service requirements and the functional requirements for the access network discovery and selection are described in 3GPP TS 22.278 and in 3GPP TS 23.402 respectively.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 312 | 11.6.0 | Published | 2013-04-11 | http://www.etsi.org/deliver/etsi_ts/124300_124399/124312/11.06.00_60/ts_124312v110600p.pdf |
+| ATIS | ATIS.3GPP.24.312V 1160-2014 | 11.6.0 | | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.312(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-24.312(R11-11.6.0) |
+| TTC | TS-3GA-24.312(Rel11)v11.6.0 | 11.6.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.312(Rel11)v11.6.0.pdf |
+
+#### 10.4.25 TS 24.341 Support of SMS over IP networks; Stage 3
+
+This document provides the protocol details for SMS over IP within the IP multimedia (IM) core network (CN) subsystem based on the session initiation protocol (SIP) and SIP events as defined in 3GPP TS 24.229.
+
+Where possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP and SIP events, either directly, or as modified by 3GPP TS 24.229.
+
+The present document is applicable to application servers (ASs) and user equipment (UE) providing SMS over IP functionality.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 341 | 11.2.0 | Published | 2013-01-18 | http://www.etsi.org/deliver/etsi_ts/124300_124399/124341/11.02.00_60/ts_124341v110200p.pdf |
+| ATIS | ATIS.3GPP.24.341V 1120-2014 | 11.2.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.341(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-24.341(R11-11.2.0) |
+| TTC | TS-3GA-24.341(Rel11)v11.2.0 | 11.2.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.341(Rel11)v11.2.0.pdf |
+
+#### 10.4.26 TS 24.368 Non-access stratum (NAS) configuration management object (MO)
+
+This document defines a management object (MO) that can be used to configure the UE with parameters related to Non-access stratum (NAS) functionality.
+
+The MO is compatible with the OMA device management (DM) protocol specifications, version 1.2 and upwards, and is defined using the OMA DM device description framework (DDF) as described in the enabler release definition.
+
+The MO consists of relevant parameters for NAS related configuration of a UE.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 368 | 11.2.0 | Published | 2012-10-08 | http://www.etsi.org/deliver/etsi_ts/124300_124399/124368/11_02_00_60/ts_124368v110200p.pdf |
+| ATIS | ATIS.3GPP.24.368V1120-2014 | 11.2.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.368(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-24.368(R11-11.2.0) |
+| TTC | TS-3GA-24.368(Rel11)v11.2.0 | 11.2.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.368(Rel11)v11.2.0.pdf |
+
+#### 10.4.27 TS 24.623 Extensible markup language (XML) configuration access protocol (XCAP) over the Ut interface for manipulating simulation services
+
+This document defines a protocol used for manipulating data related to supplementary services. The protocol is based on the extensible markup language (XML) configuration access protocol (XCAP) [IETF RFC 4825]. A new XCAP application usage is defined for the purpose of manipulating the supplementary services data. The common XCAP related aspects that are applicable to supplementary services are specified in the present document. The protocol allows authorized users to manipulate service-related data either when they are connected to IMS or when they are connected to non-IMS networks (e.g., the public Internet).
+
+The document is applicable to user equipment (UE) and application servers (AS) which are intended to support XCAP application usage for manipulating data related to supplementary services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 124 623 | 11.1.0 | Published | 2013-01-22 | http://www.etsi.org/deliver/etsi_ts/124600_124699/124623/11_01_00_60/ts_124623v110100p.pdf |
+| ATIS | ATIS.3GPP.24.623V1110-2014 | 11.1.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-24.623(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-24.623(R11-11.1.0) |
+| TTC | TS-3GA-24.623(Rel11)v11.1.0 | 11.1.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-24.623(Rel11)v11.1.0.pdf |
+
+#### 10.4.28 TR 24.820 3GPP system to fixed broadband access network interworking
+
+The document studies the additional UE – EPC procedures within the scope of 3GPP TS 24.302 and 3GPP TS 24.229, for the interworking between a 3GPP system and a Fixed Broadband Access network defined by Broadband Forum to provide the IP connectivity to a 3GPP UE using a WLAN and a H(e)NB connected to a Fixed Broadband Access network.
+
+The report covers the discovery and network selection procedures, QoS aspects, tunnel management procedures, selection of the IP mobility mode, authentication and access authorization using authentication, authorization and accounting (AAA) procedures, and IP CAN session impacts.
+
+The document is applicable to the UE and the network. In this technical specification the network is the 3GPP EPC.
+
+## 10.5 26-series, CODECs
+
+### 10.5.1 TS 26.071 Mandatory speech CODEC speech processing functions; AMR speech codec; General description
+
+The document is an introduction to the speech processing parts of the narrow-band telephony speech service employing the adaptive multi-rate (AMR) speech coder. A general overview of the speech processing functions is given, with reference to the documents where each function is specified in detail.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.071 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26071-b00.pdf |
+| ETSI | TS 126 071 | 11.0.0 | Published | 2012-10-10 | http://www.etsi.org/deliver/etsi_ts/126000_126099/126071/11.00.00_60/ts_126071v110000p.pdf |
+| ATIS | ATIS.3GPP.26.071V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.071(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.071(R11-11.0.0) |
+
+### 10.5.2 TS 26.073 ANSI-C code for the adaptive multi-rate (AMR) speech codec
+
+The document contains an electronic copy of the ANSIC code for the adaptive multi-rate codec. The ANSIC code is necessary for a bit-exact implementation of the adaptive multi-rate speech transcoder (TS 26.090), voice activity detection (TS 26.094), comfort noise (TS 26.092), source controlled rate operation (TS 26.093) and example solutions for substituting and muting of lost frames (TS 26.091).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.073 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26073-b00.pdf |
+| ETSI | TS 126 073 | 11.0.0 | Published | 2012-10-10 | http://www.etsi.org/deliver/etsi_ts/126000_126099/126073/11.00.00_60/ts_126073v110000p.pdf |
+| ATIS | ATIS.3GPP.26.073V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.073(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.073(R11-11.0.0) |
+
+### 10.5.3 TS 26.074 Mandatory speech codec speech processing functions; Adaptive multi-rate (AMR) speech codec test sequences
+
+The document specifies the digital test sequences for the adaptive multi-rate (AMR) speech codec. These sequences test for a bit exact implementation of the adaptive multi-rate speech transcoder (TS 26.090 ), voice activity detection (TS 26.094 ), comfort noise (TS 26.092 ), and source controlled rate operation (TS 26.093).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.074 | 11.1.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26074-b10.pdf |
+| ETSI | TS 126 074 | 11.1.0 | Published | 2014-01-08 | http://www.etsi.org/deliver/etsi_ts/126000_126099/126074/11.01.00_60/ts_126074v110100p.pdf |
+
+#### 10.5.4 TS 26.077 Minimum performance requirements for noise suppresser; Application to the AMR speech encoder
+
+The document specifies recommended minimum performance requirements for noise suppression algorithms intended for application in conjunction with the AMR speech encoder. This specification is for guidance purposes. Noise suppression is intended to enhance the speech signal corrupted by acoustic noise at the input to the AMR speech encoder.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.077 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26077-b00.pdf |
+| ETSI | TS 126 077 | 11.0.0 | Published | 2012-10-10 | http://www.etsi.org/deliver/etsi_ts/126000_126099/126077/11.00.00_60/ts_126077v110000p.pdf |
+| ATIS | ATIS.3GPP.26.077V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.077(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-26.077(R11-11.0.0) |
+
+#### 10.5.5 TS 26.090 Mandatory speech codec speech processing functions; Adaptive multi-rate (AMR) speech codec; Transcoding functions
+
+The document describes the detailed mapping from input blocks of 160 speech samples in 13bit uniform PCM format to encoded blocks of 95, 103, 118, 134, 148, 159, 204, and 244 bits and from encoded blocks of 95, 103, 118, 134, 148, 159, 204, and 244 bits to output blocks of 160 reconstructed speech samples. The sampling rate is 8000 samples/s leading to a bit rate for the encoded bit stream of 4.75, 5.15, 5.90, 6.70, 7.40, 7.95, 10.2 or 12.2 kbit/s. The coding scheme for the multi-rate coding modes is the so-called algebraic code-excited linear prediction coder, hereafter referred to as ACELP. The multi-rate ACELP coder is referred to as MR-ACELP.
+
+In the case of discrepancy between the requirements described in the document and the fixed point computational description (ANSIC code) of these requirements contained in 3G TS 26.073, the description in 3G TS 26.073 will prevail. The ANSIC code is not described in this document; see 3G TS 26.073 for a description of the ANSIC code.
+
+The transcoding procedure specified in the document is mandatory for systems using the AMR speech codec.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.090 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26090-b00.pdf |
+| ETSI | TS 126 090 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126000_126099/126090/11.00.00_60/ts_126090v110000p.pdf |
+| ATIS | ATIS.3GPP.26.090V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.090(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.090(R11-11.0.0) |
+
+### 10.5.6 TS 26.091 Mandatory speech codec speech processing functions; Adaptive multi-rate (AMR) speech codec; Error concealment of lost frames
+
+The document defines an error concealment procedure, also termed "frame substitution and muting" procedure, which shall be used by the AMR speech codec receiving end when one or more lost speech or lost silence descriptor (SID) frames are received.
+
+The requirements of this document are mandatory for implementation in all networks and user equipments (UE)s capable of supporting the AMR speech codec. It is not mandatory to follow the bit-exact implementation outlined in this document and the corresponding C source code.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.091 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26091-b00.pdf |
+| ETSI | TS 126 091 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126000_126099/126091/11.00.00_60/ts_126091v110000p.pdf |
+| ATIS | ATIS.3GPP.26.091V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.091(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.091(R11-11.0.0) |
+
+### 10.5.7 TS 26.092 Mandatory speech codec speech processing functions; Adaptive multi-rate (AMR) speech codec; Comfort noise aspects
+
+The document gives the detailed requirements for the correct operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation for the AMR speech codec during source controlled rate (SCR) operation.
+
+The requirements described in this document are mandatory for implementation in all UEs capable of supporting the AMR speech codec.
+
+The receiver requirements are mandatory for implementation in all networks capable of supporting the AMR speech codec, the transmitter requirements only for those where downlink SCR will be used.
+
+In case of discrepancy between the requirements described in this document and the fixed point computational description of these requirements contained in 3G TS 26.073, the description in 3G TS 26.073 will prevail.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.092 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26092-b00.pdf |
+| ETSI | TS 126 092 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126000_126099/126092/11.00.00/60/ts_126092v110000p.pdf |
+| ATIS | ATIS.3GPP.26.092V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.092(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.092(R11-11.0.0) |
+
+### 10.5.8 TS 26.093 Mandatory speech codec speech processing functions Adaptive multi-rate (AMR) speech codec; Source controlled rate operation
+
+This document describes the source controlled rate (SCR) operation of the adaptive multi-rate speech codec in codec types UMTS\_AMR and GSM\_AMR for the UMTS system. The implementation of this SCR operation is mandatory in all UMTS equipment.
+
+This structure of distributing the various functions between system entities is not mandatory for implementation, as long as the operation on the speech decoder output remains the same.
+
+Annex A describes the discontinuous transmission (DTX) operation of the adaptive multi-rate speech codec in codec types FR\_AMR, HR\_AMR and OHR\_AMR for GERAN. This annex is the former GSM 06.93 (Release 98).
+
+Annexes B to E describe the SCR operation of the adaptive multi-rate speech codec in codec types GSM\_EFR, TDMA\_EFR, TDMA\_US1 and PDC\_EFR for the UMTS system.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.093 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26093-b00.pdf |
+| ETSI | TS 126 093 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126000_126099/126093/11.00.00/60/ts_126093v110000p.pdf |
+| ATIS | ATIS.3GPP.26.093V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.093(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.093(R11-11.0.0) |
+
+### 10.5.9 TS 26.094 Mandatory speech codec speech processing functions; Adaptive multi-rate (AMR) speech codec; Voice activity detector (VAD)
+
+The document specifies two alternatives for the voice activity detector (VAD) to be used in the discontinuous transmission (DTX) as described in 3G TS 26.093. Implementers of mobile station and infrastructure equipment conforming to the AMR specifications can choose which of the two VAD options to implement. There are no interoperability factors associated with this choice.
+
+The requirements are mandatory on any VAD to be used either in user equipment (UE) or base station systems (BSS)s that utilize the AMR speech codec.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.094 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26094-b00.pdf |
+| ETSI | TS 126 094 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126000_126099/126094/11.00.00_60/ts_126094v110000p.pdf |
+| ATIS | ATIS.3GPP.26.094V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.094(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.094(R11-11.0.0) |
+
+### 10.5.10 TS 26.101 Mandatory speech codec speech processing functions; Adaptive multi-rate (AMR) speech codec frame structure
+
+The document describes a generic frame format for the adaptive multi-rate (AMR) speech codec. This format shall be used as a common reference point when interfacing speech frames between different elements of the 3G system and between different systems. Appropriate mappings to and from this generic frame format will be used within and between each system element.
+
+Annex A describes a second frame format, which shall be used when octet alignment of AMR frames is required.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.101 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26101-b00.pdf |
+| ETSI | TS 126 101 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126101/11.00.00_60/ts_126101v110000p.pdf |
+| ATIS | ATIS.3GPP.26.101V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.101(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.101(R11-11.0.0) |
+
+### 10.5.11 TS 26.102 AMR speech codec; Interface to Iu, Uu and Nb
+
+The document specifies the mapping of the AMR generic frame format (TS 26.101) to the Iu Interface (TS 25.415), the Uu interface and the Nb interface (TS 29.415). It further specifies the mapping of enhanced full rate (GSM\_EFR) coded speech and of PCM 64 kbit/s [ITU-T G.711] coded speech to the Nb Interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.102 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26102-b00.pdf |
+| ETSI | TS 126 102 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126102/11.00.00_60/ts_126102v110000p.pdf |
+| ATIS | ATIS.3GPP.26.102V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.102(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.102(R11-11.0.0) |
+
+### 10.5.12 TS 26.104 ANSI-C code for the floating-point adaptive multi-rate (AMR) speech codec
+
+This technical standard (TS) contains an electronic copy of the ANSI-C code for a floating-point implementation of the adaptive multi-rate codec. This floating-point codec specification is mainly targeted to be used in multimedia applications such as the 3G-324M terminal specified in TS 26.110, or in packet-based (e.g., ITU-T H.323) applications. The bit-exact fixed-point ANSI-C code in TS 26.073 remains the preferred implementation for all applications, but the floating-point codec may be used instead of the fixed-point codec when the implementation platform is better suited for a floating-point implementation. It has been verified that the fixed-point and floating point codecs interoperate with each other without any artifacts.
+
+The floating-point ANSI-C code in this specification is the only standard conforming non-bit-exact implementation of the adaptive multi-rate speech transcoder (TS 26.090), voice activity detection (TS 26.094), comfort noise generation (TS 26.092), and source controlled rate operation (TS 26.093). The floating-point code also contains example solutions for substituting and muting of lost frames (TS 26.091).
+
+The fixed-point specification in TS 26.073 shall remain the only allowed implementation for the 3G mandatory speech services and the use of the floating-point codec is strictly limited to other services.
+
+The floating-point encoder in this specification is a non-bit-exact implementation of the fixed-point encoder producing quality indistinguishable from that of the fixed-point encoder. The decoder in this specification is functionally a bit-exact implementation of the fixed-point decoder, but the code has been optimized for speed and the standard fixed-point libraries are not used as such.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.104 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26104-b00.pdf |
+| ETSI | TS 126 104 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126104/11.00.00_60/ts_126104v110000p.pdf |
+| ATIS | ATIS.3GPP.26.104V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.104(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.104(R11-11.0.0) |
+
+### 10.5.13 TS 26.114 IP multimedia subsystem (IMS); Multimedia telephony; Media handling and interaction
+
+The present document specifies a client for the multimedia telephony service for IMS (MTSI) supporting conversational speech (including DTMF), video and text transported over RTP with the scope to deliver a user experience equivalent to or better than that of circuit switched (CS) conversational services using the same amount of network resources. It defines media handling (e.g., signalling, transport, jitter buffer management, packet-loss handling, adaptation), as well as interactivity (e.g., adding or dropping media during a call). The focus is to ensure a reliable and interoperable service with a predictable media quality, while allowing for flexibility in the service offerings.
+
+The scope includes maintaining backward compatibility in order to ensure seamless interworking with existing services available in the CS domain, such as CS speech and video telephony, as well as with terminals of earlier 3GPP releases. In addition, inter-working with traditional PSTN and emerging TISPAN network is covered.
+
+The specification is written in a forward-compatible way in order to allow additions of media components and functionality in later releases.
+
+NOTE 1 – MTSI clients can support more than conversational speech, video and text, which is the scope of the present document. See 3GPP TS 22.173 for the definition of the multimedia telephony service for IMS.
+
+NOTE 2 – 3GPP TS 26.235 and 3GPP TS 26.236 do not include the specification of an MTSI client, although they include conversational multimedia applications. Only those parts of 3GPP TS 26.235 and 3GPP TS 26.236 that are specifically referenced by the present document apply to multimedia telephony service for IMS.
+
+NOTE 3 – The present document was started as a conclusion from the study in 3GPP TR 26.914 on optimization opportunities in multimedia telephony for IMS (3GPP TR 22.973).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.114 | 11.9.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26114-b90.pdf |
+| ETSI | TS 126 114 | 11.9.0 | Published | 2014-01-08 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126114/11_09.00_60/ts_126114v110900p.pdf |
+| ATIS | ATIS.3GPP.26.114V1160-2014 | 11.6.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.114(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.114(R11-11.6.0) |
+
+### 10.5.14 TS 26.115 Echo control for speech and multimedia services
+
+The document specifies minimum performance requirements for the gateway echo control of 3G speech and multimedia services. The document is applicable to any narrow-band speech telephony or multimedia service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.115 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26115-b00.pdf |
+| ETSI | TS 126 115 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126115/11.00.00/60/ts_126115v110000p.pdf |
+| ATIS | ATIS.3GPP.26.115V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.115(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.115(R11-11.0.0) |
+
+### 10.5.15 TS 26.131 Terminal acoustic characteristics for telephony; Requirements
+
+The document is applicable to any terminal capable of supporting narrow-band or wideband telephony, either as a stand-alone service or as the telephony component of a multimedia service. The document specifies minimum performance requirements for the acoustic characteristics of 3G terminals when used to provide narrow-band or wideband telephony.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.131 | 11.3.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26131-b30.pdf |
+| ETSI | TS 126 131 | 11.3.0 | Published | 2014-01-08 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126131/11.03.00/60/ts_126131v110300p.pdf |
+| ATIS | ATIS.3GPP.26.131V1120-2014 | 11.3.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.131(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.131(R11-11.2.0) |
+
+### 10.5.16 TS 26.132 Speech and video telephony terminal acoustic test specification
+
+The document is applicable to any terminal capable of supporting narrowband or wideband telephony, either as a stand-alone service or as the telephony component of a multimedia service. The present document specifies test methods to allow the minimum performance requirements for the acoustic characteristics of GSM and 3G terminals when used to provide narrowband or wideband telephony to be assessed.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.132 | 11.4.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26132-b40.pdf |
+| ETSI | TS 126 132 | 11.4.0 | Published | 2014-01-08 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126132/11.04.00/60/ts_126132v110400p.pdf |
+
+### 10.5.17 TS 26.140 Multimedia messaging service (MMS); Media formats and codes
+
+This document specifies the media types, formats and codecs for the MMS within the 3GPP system. The scope of this document extends to codecs for speech, audio, video, still images, bitmap graphics, and other media in general, as well as scene description, multimedia integration and synchronization schemes.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.140 | 11.1.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26140-b10.pdf |
+| ETSI | TS 126 140 | 11.1.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126140/11.01.00_60/ts_126140v110100p.pdf |
+| ATIS | ATIS.3GPP.26.140V 1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.140(R11-11.0.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stno=TTAT.3G-26.140(R11-11.0.0) |
+
+### 10.5.18 TS 26.141 IP multimedia system (IMS) messaging and presence; Media formats and codecs
+
+The 3GPP Technical Specifications 3G TS 22.340 and 3G TS 22.141 define the requirements for the 3GPP IP multimedia subsystem (IMS)-based messaging and presence services. This Technical Specification takes the requirements into account when defining the minimal baseline and optional media codecs and message container format to be used by IMS messaging and associated presence service, when supported.
+
+IMS messaging services incorporate one or more of the following messaging types: immediate messaging, deferred delivery messaging, and session-based messaging. With immediate messaging the sender expects immediate message delivery in what is perceived as real time compared with deferred messaging, where the sender expects the network to deliver the message as soon as the recipient becomes available. With session-based messaging, a communications association is established between two or more users before communication can take place. In the simplest form, session-based messaging may be a direct communication between two users. This specification defines the media types and container formats for both the immediate message type and the session-based message type.
+
+The specification provides the ability to have an interoperable baseline set of media types for messaging and presence services, that will simultaneously maximize the technology reuse of the already existing 3GPP services with media types, defined in 3G TS 26.140 and 3G TS 26.234. Simultaneously, the specification will provide the ability to indicate the IMS system about the complete set of UE media and storage capabilities relevant for the IMS messaging and presence services.
+
+The present document specifies the basic media formats and codecs to be used in the IMS messaging and presence services. It defines the mandatory "baseline" set of media types for the services. Additionally, it also targets to allow possible message content type enhancements, either 3GPP-standardized or other generally used media types, in a flexible way.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.141 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26141-b00.pdf |
+| ETSI | TS 126 141 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126141/11.00.00/60/ts_126141v110000p.pdf |
+| ATIS | ATIS.3GPP.26.141V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.141(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.141(R11-11.0.0) |
+
+### 10.5.19 TS 26.142 Dynamic and interactive multimedia scenes
+
+Dynamic and interactive multimedia scenes (DIMS) defines a dynamic rich-media system, including a media type, its packaging, delivery, and interaction with the local terminal, user, and other local and remote sub-systems. Enhanced end-user experiences are provided by the coordinated management and synchronization of media and events, combined with end-user interaction.
+
+The DIMS media type can be used as a generic media type, allowing creating dynamic interactive rich-media services and can also benefit, or be used in association with other media types (e.g., audio codecs, video codecs, XHTML browser, etc.).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.142 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26142-b00.pdf |
+| ETSI | TS 126 142 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126142/11.00.00/60/ts_126142v110000p.pdf |
+| ATIS | ATIS.3GPP.26.142V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.142(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.142(R11-11.0.0) |
+
+### 10.5.20 TS 26.150 Syndicated feed reception (SFR) within 3GPP environments; Protocols and codecs
+
+This document defines a set of media codecs, formats and transport/application protocols to enable syndicated feed reception within the 3GPP system.
+
+The document includes information applicable to network operators, service providers and manufacturers.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.150 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26150-b00.pdf |
+| ETSI | TS 126 150 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126150/11.00.00/60/ts_126150v110000p.pdf |
+| ATIS | ATIS.3GPP.26.150V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.150(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.150(R11-11.0.0) |
+
+### 10.5.21 TS 26.171 Speech codec speech processing functions; Adaptive multi-rate – wideband (AMR-WB) speech codec; General description
+
+This document is an introduction to the speech processing parts of the wideband telephony speech service employing the adaptive multi-rate wideband (AMR-WB) speech coder. A general overview of the speech processing functions is given, with reference to the documents where each function is specified in detail.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.171 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26171-b00.pdf |
+| ETSI | TS 126 171 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126171/11.00.00/60/ts_126171v110000p.pdf |
+| ATIS | ATIS.3GPP.26.171V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.171(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.171(R11-11.0.0) |
+
+### 10.5.22 TS 26.173 ANSI-C code for the adaptive multi-rate – wideband (AMR-WB) speech codec
+
+This document contains an electronic copy of the ANSI-C code for the adaptive multi-rate wideband codec. The ANSI-C code is necessary for a bit-exact implementation of the adaptive multi-rate wideband speech transcoder (3G TS 26.190), voice activity detection (3G TS 26.194), comfort noise (3G TS 26.192), source controlled rate operation (3G TS 26.193) and example solutions for substituting and muting of lost frames (3G TS 26.191).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.173 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26173-b00.pdf |
+| ETSI | TS 126 173 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126173/11.00.00/60/ts_126173v110000p.pdf |
+| ATIS | ATIS.3GPP.26.173V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.173(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.173(R11-11.0.0) |
+
+### 10.5.23 TS 26.174 Speech codec speech processing functions; Adaptive multi-rate – wideband (AMR-WB) speech codec test sequences
+
+The document specifies the digital test sequences for the adaptive multi-rate wideband (AMR-WB) speech codec. These sequences test for a bit-exact implementation of the adaptive multi-rate wideband (AMR-WB) speech transcoder (TS 26.190), voice activity detection (TS 26.194), comfort noise (TS 26.192), and source controlled rate operation (TS 26.193).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.174 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26174-b00.pdf |
+| ETSI | TS 126 174 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126174/11.00.00/60/ts_126174v110000p.pdf |
+
+### 10.5.24 TS 26.177 Speech enabled services (SES); Distributed speech recognition (DSR) extended advanced front-end test sequences
+
+The document specifies the digital test sequences for the DSR Extended Advanced Front-end speech codec. These sequences can be used to test for a bit exact implementation of the DSR Advanced Front-end codec and quantization (3GPP TS 26.243).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.177 | 11.1.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26177-b10.pdf |
+| ETSI | TS 126 177 | 11.1.0 | Published | 2014-01-08 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126177/11.01.00/60/ts_126177v110100p.pdf |
+
+### 10.5.25 TS 26.190 Speech codec speech processing functions; Adaptive multi-rate – wideband (AMR-WB) speech codec; Transcoding functions
+
+This telecommunication standard (TS) describes the detailed mapping from input blocks of 320 speech samples in 16-bit uniform PCM format to encoded blocks of 132, 177, 253, 285, 317, 365, 397, 461 and 477 bits and from encoded blocks of 132, 177, 253, 285, 317, 365, 397, 461 and 477 bits to output blocks of 320 reconstructed speech samples. The sampling rate is 16 000 samples/s leading to a bit rate for the encoded bit stream of 6.60, 8.85, 12.65, 14.25, 15.85,
+
+18.25, 19.85, 23.05 or 23.85 kbit/s. The coding scheme for the multi-rate coding modes is the so-called algebraic code-excited linear prediction coder, hereafter referred to as ACELP. The multirate wideband ACELP coder is referred to as MRWB-ACELP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.190 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26190-b00.pdf |
+| ETSI | TS 126 190 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126190/11.00.00_60/ts_126190v110000p.pdf |
+| ATIS | ATIS.3GPP.26.190V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.190(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.190(R11-11.0.0) |
+
+### 10.5.26 TS 26.191 Speech codec speech processing functions; Adaptive multi-rate – wideband (AMR-WB) speech codec; Error concealment of erroneous or lost frames
+
+This specification defines an error concealment procedure, also termed frame substitution and muting procedure, which shall be used by the AMR-WB speech codec receiving end when one or more erroneous/lost speech or lost silence descriptor (SID) frames are received.
+
+The requirements of this document are mandatory for implementation in all networks and user equipments (UE)s capable of supporting the AMR-WB speech codec. It is not mandatory to follow the bit-exact implementation outlined in this document and the corresponding C source code.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.191 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26191-b00.pdf |
+| ETSI | TS 126 191 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126191/11.00.00_60/ts_126191v110000p.pdf |
+| ATIS | ATIS.3GPP.26.191V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.191(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.191(R11-11.0.0) |
+
+### 10.5.27 TS 26.192 Speech codec speech processing functions; Adaptive multi-rate – wideband (AMR-WB) speech codec; Comfort noise aspects
+
+This document gives the detailed requirements for the correct operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation for the AMR wideband (AMR-WB) speech codec during source controlled rate (SCR) operation.
+
+The requirements described in this document are mandatory for implementation in all UEs capable of supporting the AMR-WB speech codec.
+
+The receiver requirements are mandatory for implementation in all networks capable of supporting the AMR-WB speech codec, the transmitter requirements only for those where downlink SCR will be used.
+
+In case of discrepancy between the requirements described in this document and the fixed point computational description of these requirements contained in 3G TS 26.173, the description in 3G TS 26.173 will prevail.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.192 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26192-b00.pdf |
+| ETSI | TS 126 192 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126192/11.00.00_60/ts_126192v110000p.pdf |
+| ATIS | ATIS.3GPP.26.192V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.192(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.192(R11-11.0.0) |
+
+### 10.5.28 TS 26.193 Speech codec speech processing functions; Adaptive multi-rate – wideband (AMR-WB) speech codec; Source controlled rate operation
+
+This document describes the source controlled rate (SCR) operation of the adaptive multi-rate wideband speech codec. The implementation of this SCR operation is mandatory in all UMTS equipment implementing the adaptive multi-rate wideband speech codec.
+
+The description is structured according to the block diagram in Figure 10.5.28-1. This structure of distributing the various functions between system entities is not mandatory for implementation, as long as the operation on the speech decoder output remains the same.
+
+Annex A describes the discontinuous transmission (DTX) operation of the adaptive multi-rate wideband speech codec in codec type FR\_AMR-WB for the GSM system.
+
+An overall description of the speech processing parts can be found in 3G TS 26.171. An overview of one link SCR operation is shown in Figure 10.5.28-1.
+
+
+
+```
+
+graph LR
+ subgraph TX_SCR_handler [TX SCR handler]
+ SE[Speech encoder]
+ VAD[Voice activity detector]
+ CNPC[Comfort noise parameter computation]
+ end
+ subgraph Network ["Network"]
+ IPC[Information packeting, transport and classification]
+ end
+ subgraph RX_SCR_handler [RX SCR handler]
+ SD[Speech decoder]
+ EC[Error concealment]
+ CNG[Comfort noise generation]
+ end
+ SE -- "Information bits" --> IPC
+ VAD -- "Mode indication" --> IPC
+ CNPC -- "TX_TYPE" --> IPC
+ IPC -- "Information bits" --> SD
+ IPC -- "Mode indication" --> EC
+ IPC -- "RX_TYPE" --> CNG
+
+```
+
+The diagram illustrates the flow of data and control signals during a source controlled rate (SCR) operation. On the left, the TX SCR handler contains three functional blocks: a Speech encoder, a Voice activity detector, and a Comfort noise parameter computation block. The Speech encoder sends 'Information bits' to the central 'Network' block. The Voice activity detector sends a 'Mode indication' to the Network. The Comfort noise parameter computation block sends a 'TX\_TYPE' signal to the Network. The Network block, labeled 'Information packeting, transport and classification', processes these inputs and sends them out to the RX SCR handler on the right. The RX SCR handler contains three corresponding blocks: a Speech decoder, an Error concealment block, and a Comfort noise generation block. The Speech decoder receives 'Information bits' from the Network. The Error concealment block receives a 'Mode indication' from the Network. The Comfort noise generation block receives an 'RX\_TYPE' signal from the Network.
+
+Block diagram of one link SCR operation showing TX SCR handler, Network, and RX SCR handler components and their interactions.
+
+Q.1741.5(08)\_F10.5.30-1
+
+Figure 10.5.28-1 – Block diagram of one link SCR operation
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.193 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26193-b00.pdf |
+| ETSI | TS 126 193 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126193/11.00.00/60/ts_126193v110000p.pdf |
+| ATIS | ATIS.3GPP.26.193V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.193(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.193(R11-11.0.0) |
+
+### 10.5.29 TS 26.194 Speech codec speech processing functions; Adaptive multi-rate – wideband (AMR-WB) speech codec; Voice activity detector (VAD)
+
+This document specifies the voice activity detector (VAD) to be used in the discontinuous transmission (DTX) as described in 3GPP TS 26.193.
+
+The requirements are mandatory on any VAD to be used either in user equipment (UE) or base station systems (BSS)s that utilize the AMR wideband speech codec.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.194 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26194-b00.pdf |
+| ETSI | TS 126 194 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126100_126199/126194/11.00.00/60/ts_126194v110000p.pdf |
+| ATIS | ATIS.3GPP.26.194V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.194(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.194(R11-11.0.0) |
+
+### 10.5.30 TS 26.201 Speech codec speech processing functions; Adaptive multi-rate – wideband (AMR-WB) speech codec; Frame structure
+
+This document describes a generic frame format for the adaptive multi-rate wideband (AMRWB) speech codec. This format shall be used as a common reference point when interfacing speech frames between different elements of the 3G system and between different systems. Appropriate mappings to and from this generic frame format will be used within and between each system element.
+
+Annex A of this technical specification describes a second frame format which shall be used when octet alignment of AMR-WB frames is required.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.201 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26201-b00.pdf |
+| ETSI | TS 126 201 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126200_126299/126201/11.00.00/60/ts_126201v110000p.pdf |
+| ATIS | ATIS.3GPP.26.201V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.201(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.201(R11-11.0.0) |
+
+### 10.5.31 TS 26.202 Speech codec speech processing functions; Adaptive multi-rate – wideband (AMR-WB) speech codec; Interface to Iu, Uu and Nb
+
+This document specifies the mapping of the AMR wideband generic frame format (3G TS 26.201) to the Iu interface (3G TS 25.415), the Uu interface and the Nb interface (3G TS 29.415). It further specifies the mapping of PCM 64 kbit/s [ITU-T G.711] coded speech to the Nb interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.202 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26202-b00.pdf |
+| ETSI | TS 126 202 | 11.0.0 | Published | 2012-10-11 | http://www.etsi.org/deliver/etsi_ts/126200_126299/126202/11.00.00/60/ts_126202v110000p.pdf |
+| ATIS | ATIS.3GPP.26.202V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.202(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.202(R11-11.0.0) |
+
+### 10.5.32 TS 26.204 Speech codec speech processing functions; Adaptive multi-rate – wideband (AMR-WB) speech codec; ANSI-C code
+
+This document contains an electronic copy of the ANSI-C code for the floating-point adaptive multi-rate wideband codec. This floating-point codec specification is mainly targeted to be used in multimedia applications or in packet-based applications. The bit-exact fixed-point ANSI-C code in 3G TS 26.173 remains the preferred implementation for all applications, but the floating-point codec may be used instead of the fixed-point codec when the implementation platform is better suited for a floating-point implementation. It has been verified that the fixed-point and floating point codecs interoperate with each other without any artifacts.
+
+The floating-point ANSI-C code in this document is the only standard conforming non-bit-exact implementation of the adaptive multi-rate wideband speech transcoder (3G TS 26.190), voice activity detection (3G TS 26.194), comfort noise generation (3G TS 26.192), and source controlled rate operation (3G TS 26.193). The floating-point code also contains example solutions for substituting and muting of lost frames (3G TS 26.191).
+
+The fixed-point specification in 3G TS 26.173 shall remain the only allowed implementation for the 3G AMR-WB speech service and the use of the floating-point codec is strictly limited to other services.
+
+The floating-point encoder in this document is a non-bit-exact implementation of the fixed-point encoder producing quality indistinguishable from that of the fixed-point encoder. The decoder in this document is functionally a bit-exact implementation of the fixed-point decoder, but the code has been optimized for speed and the standard fixed-point libraries are not used as such.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.204 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26204-b00.pdf |
+| ETSI | TS 126 204 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/126200_126299/126204/11_00.00_60/ts_126204v110000p.pdf |
+| ATIS | ATIS.3GPP.26.204V 1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.204(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.204(R11-11.0.0) |
+
+### 10.5.33 TS 26.233 Transparent end-to-end packet-switched streaming service (PSS); General description
+
+The document contains a general description of a transparent packet-switched streaming service in 3G networks. In particular, it defines the usage scenarios, overall high-level end-to-end service concept, and lists terminal-related functional components. It also lists any identified service interworking requirements. PSS protocols and codecs are defined in 3G TS 26.234.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.233 | 11.1.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26233-b10.pdf |
+| ETSI | TS 126 233 | 11.2.0 | Published | 2014-03-21 | http://www.etsi.org/deliver/etsi_ts/126200_126299/126233/11_02.00_60/ts_126233v110200p.pdf |
+| ATIS | ATIS.3GPP.26.233V 1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.233(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.233(R11-11.0.0) |
+
+### 10.5.34 TS 26.234 Transparent end-to-end packet-switched streaming service (PSS); Protocols and codecs
+
+The document specifies the protocols and codecs for the PSS within the 3G system. Protocols for control signalling, capability exchange, scene description, media transport and media encapsulations are specified. Codecs for speech, natural and synthetic audio, video, still images, bitmap graphics, vector graphics, timed text, and text are specified.
+
+The document is applicable to IP-based packet-switched networks.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.234 | 11.3.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26234-b30.pdf |
+| ETSI | TS 126 234 | 11.3.0 | Published | 2014-01-08 | http://www.etsi.org/deliver/etsi_ts/126200_126299/126234/11_03_00_60/ts_126234v110300p.pdf |
+| ATIS | ATIS.3GPP.26.234V 1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.234(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.234(R11-11.0.0) |
+
+### 10.5.35 TS 26.235 Packet-switched conversational multimedia applications; Default codecs
+
+This document introduces the set of default codecs for packet-switched conversational multimedia applications within the 3G IP multimedia subsystem. Visual and sound communication are specifically addressed. The intended applications are assumed to require low-delay, real-time functionality.
+
+This document is applicable, but not limited, to PS video telephony.
+
+The applicability of this specification to GERAN is FFS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.235 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26235-b00.pdf |
+| ETSI | TS 126 235 | 11.0.0 | Published | 2012-10-12 | http://www.etsi.org/deliver/etsi_ts/126200_126299/126235/11_00_00_60/ts_126235v110000p.pdf |
+| ATIS | ATIS.3GPP.26.235V 1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.235(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.235(R11-11.0.0) |
+
+### 10.5.36 TS 26.236 Packet-switched conversational multimedia applications; Transport protocols
+
+This document introduces the required protocols for packet-switched conversational multimedia applications within 3GPP IP multimedia subsystem. Visual and sound communications are specifically addressed. The intended applications are assumed to require low-delay, real-time functionality.
+
+This document describes the required protocol-related elements for 3G PS multimedia terminal:
+
+- required SDP signalling regarding the media type bit rate, packet size, packet transport frequency;
+- usage of RTP payload for media types;
+- bandwidth adaptation;
+- QoS negotiation.
+
+This document is applicable, but not limited, to packet-switched video telephony.
+
+The applicability of this document to GERAN is FFS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB-STD-T63-26.236 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26236-b00.pdf |
+| ETSI | TS 126 236 | 11.0.0 | Published | 2012-10-12 | http://www.etsi.org/deliver/etsi_ts/126200_126299/126236/11.00.00_60/ts_126236v110000p.pdf |
+| ATIS | ATIS.3GPP.26.236V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.236(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.236(R11-11.0.0) |
+
+### 10.5.37 TS 26.237 IP multimedia subsystem (IMS) based packet switch streaming (PSS) and multimedia broadcast/multicast service (MBMS) user service; Protocols
+
+This document specifies the usage of IMS protocols to initiate and control PSS and MBMS streaming user services based applications. It applies to IMS enabled UEs that also implement PSS and/or MBMS clients. Existing protocols that are used are described in reference to relevant specifications. IMS based MBMS download user services are to be defined in a subsequent version of the present document.
+
+The present document is applicable to IP-based packet-switched networks over 3GPP systems.
+
+The present document includes information applicable to network operators, service providers and manufacturers.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB-STD-T63-26.237 | 11.3.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26237-b30.pdf |
+| ETSI | TS 126 237 | 11.3.0 | Published | 2014-01-08 | http://www.etsi.org/deliver/etsi_ts/126200_126299/126237/11.03.00_60/ts_126237v110300p.pdf |
+| ATIS | ATIS.3GPP.26.237V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.237(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.237(R11-11.0.0) |
+
+### 10.5.38 TS 26.243 ANSI-C code for the fixed-point distributed speech recognition extended advanced front-end
+
+The present document contains an electronic copy of the ANSI-C code for DSR extended advanced front-end. The ANSI-C code is necessary for a bit-exact implementation of DSR extended advanced front-end.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.243 | 11.1.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26243-b10.pdf |
+| ETSI | TS 126 243 | 11.1.0 | Published | 2014-01-08 | http://www.etsi.org/deliver/etsi_ts/126200_126299/126243/11.01.00_60/ts_126243v110100p.pdf |
+| ATIS | ATIS.3GPP.26.243V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.243(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.243(R11-11.0.0) |
+
+### 10.5.39 TS 26.244 Transparent end-to-end packet-switched streaming service (PSS); 3GPP file format (3GP)
+
+This document defines the 3GPP file format (3GP) as an instance of the ISO base media file format. The definition addresses 3GPP specific features such as codec registration and conformance within the MMS and PSS services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.244 | 11.1.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26244-b10.pdf |
+| ETSI | TS 126 244 | 11.1.0 | Published | 2012-10-12 | http://www.etsi.org/deliver/etsi_ts/126200_126299/126244/11.01.00_60/ts_126244v110100p.pdf |
+| ATIS | ATIS.3GPP.26.244V1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.244(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.244(R11-11.1.0) |
+
+### 10.5.40 TS 26.245 Transparent end-to-end packet-switched streaming service (PSS); Timed text format
+
+The 3GPP transparent end-to-end packet-switched streaming service (PSS) specification consists of six 3GPP TSs: 3G TS 22.233, 3G TS 26.233, 3G TS 26.234, 3G TS 26.244, 3G TS 26.245 and 3G TS 26.246.
+
+The 3G TS 22.233 contains the service requirements for the PSS. The 3G TS 26.233 provides an overview of the PSS. The 3G TS 26.234 provides the details of protocol and codecs used by the PSS. The 3G TS 26.244 defines the 3GPP file format (3GP) used by the PPS and MMS services. The 3G TS 26.246 defines the 3GPP SMIL language profile. The present document defines the timed text format used by the PSS.
+
+The 3G TS 26.244, 3G TS 26.245 and 3G TS 26.246 start with Release 6. Earlier releases of the 3GPP file format, the timed text format and the 3GPP SMIL language profile can be found in 3G TS 26.234.
+
+Timed text is text that is rendered at the terminal, in synchronization with other timed media such as video or audio. Timed text is used for such applications as closed captioning, titling, and other visual annotation of timed media.
+
+This document defines the timed text format relative to the 3GPP file format. This specification defines the format of timed text in downloaded files.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.245 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26245-b00.pdf |
+| ETSI | TS 126 245 | 11.0.0 | Published | 2012-10-12 | http://www.etsi.org/deliver/etsi_ts/126200_126299/126245/11.00.00/60/ts_126245v110000p.pdf |
+| ATIS | ATIS.3GPP.26.245V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.245(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.245(R11-11.0.0) |
+
+#### **10.5.41 TS 26.246 Transparent end-to-end packet-switched streaming service (PSS); 3GPP SMIL language profile**
+
+The present document includes the specification of the 3GPP SMIL language profile. The 3GPP SMIL language profile is also referred to as "3GPP PSS SMIL Language Profile" (3G TS 26.234) and also just "3GPP SMIL".
+
+The 3GPP SMIL language profile is based on SMIL 2.0 basic and SMIL scalability framework. It is a clean subset of SMIL 2.0 full profile, and a clear superset of SMIL 2.0 basic.
+
+The 3GPP SMIL language profile is used by the PSS and MMS services.
+
+The 3GPP SMIL language profile is in no way restricted to be used with only these services, but can also be used for other services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.246 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26246-b00.pdf |
+| ETSI | TS 126 246 | 11.0.0 | Published | 2012-10-12 | http://www.etsi.org/deliver/etsi_ts/126200_126299/126246/11.00.00/60/ts_126246v110000p.pdf |
+| ATIS | ATIS.3GPP.26.246V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.246(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.246(R11-11.0.0) |
+
+#### **10.5.42 TS 26.247 Transparent end-to-end packet-switched streaming service (PSS); Progressive download and dynamic adaptive streaming over HTTP (3GP-DASH)**
+
+The present document specifies progressive download and dynamic adaptive streaming over HTTP (3GP-DASH). This specification is part of packet-switched streaming service (PSS). HTTP-based progressive download and dynamic adaptive streaming are separated from TS 26.234 to differentiate from RTP-based streaming that is maintained in TS 26.234. HTTP-based progressive download and dynamic adaptive streaming may be deployed independently from RTP-based PSS, for example by using standard HTTP/1.1 servers for hosting data formatted as defined in the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.247 | 11.5.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26247-b50.pdf |
+| ETSI | TS 126 247 | 11.6.0 | Published | 2014-03-21 | http://www.etsi.org/deliver/etsi_ts/126200_126299/126247/11.06.00_60/ts_126247v110600p.pdf |
+| ATIS | ATIS.3GPP.26.247V1120-2014 | 11.2.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.247(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-26.247(R11-11.2.0) |
+
+#### 10.5.43 TS 26.273 ANSI-C code for the fixed-point extended AMR – wideband (AMR-WB+) codec
+
+This document contains an electronic copy of the ANSIC code for the fixed-point extended adaptive multirate wideband codec. Alternatively, floating-point ANSI-C code is specified in TS 26.304. The floating-point codec/encoder/decoder specified in the present document or the floating-point codec/encoder/decoder specified in TS 26.304 may be used depending on if the implementation platform is better suited for a floating-point or a fixed-point implementation. It has been verified that the fixed-point and floating-point codecs interoperate with each other without any artifacts.
+
+The fixed-point ANSIC code in the present document defines, besides the floating-point c-code specified in TS 26.304, one valid reference implementation of the extended adaptive multi-rate wideband transcoder (TS 26.290). Standard conformance is enforced by meeting the conformance criteria defined in TS 26.274.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.273 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26273-b00.pdf |
+| ETSI | TS 126 273 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/126200_126299/126273/11.00.00_60/ts_126273v110000p.pdf |
+| ATIS | ATIS.3GPP.26.273V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.273(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-26.273(R11-11.0.0) |
+
+#### 10.5.44 TS 26.274 Audio codec processing functions; Extended adaptive multi-rate – wideband (AMR-WB+) speech codec; Conformance testing
+
+The document specifies test procedures and digital test sequences to be used for conformance testing of implementations of the Extended Adaptive Multi-Rate Wideband (AMR-WB+) codec.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.274 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26274-b00.pdf |
+| ETSI | TS 126 274 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/126200_126299/126274/11.00.00_60/ts_126274v110000p.pdf |
+
+#### 10.5.45 TS 26.290 Audio codec processing functions; Extended adaptive multi-rate – wideband (AMR-WB+) codec; Transcoding functions
+
+This telecommunication standard describes the detailed mapping from input blocks of monophonic or stereophonic audio samples in 16-bit uniform PCM format to encoded blocks and from encoded blocks to output blocks of reconstructed monophonic or stereophonic audio samples. The coding scheme is an extension of the AMR-WB coding scheme (3G TS 26.194) and is referred to as extended AMR-WB or AMR-WB+ codec. It comprises all AMR-WB speech codec modes including VAD/DTX (TS 26.190) as well as extended functionality for encoding general audio signals such as music, speech, mixed, and other signals.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.290 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26290-b00.pdf |
+| ETSI | TS 126 290 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/126200_126299/126290/11.00.00_60/ts_126290v110000p.pdf |
+| ATIS | ATIS.3GPP.26.290V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.290(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-26.290(R11-11.0.0) |
+
+#### 10.5.46 TS 26.304 Extended adaptive multi-rate – wideband (AMR-WB+) codec; floating point ANSI-C code
+
+The present document contains an electronic copy of the ANSI-C code for the floating-point extended adaptive multi-rate wideband codec. Alternatively, fixed-point ANSI-C code is specified in 3G TS 26.273. The floating-point codec/encoder/decoder specified in this document or the fixed-point codec/encoder/decoder may be used depending on if the implementation platform is better suited for a floating-point or a fixed-point implementation. It has been verified that the fixed-point and floating-point codecs interoperate with each other without any artifacts.
+
+The floating-point ANSI-C code in the present document defines, besides the fixed-point c-code specified in 3G TS 26.273, one valid reference implementation of the extended adaptive multirate wideband transcoder (3G TS 26.290). Standard conformance is enforced by meeting the conformance criteria defined in 3G TS 26.290.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.304 | 11.0.1 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26304-b01.pdf |
+| ETSI | TS 126 304 | 11.0.1 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/126300_126399/126304/11.00.01_60/ts_126304v110001p.pdf |
+| ATIS | ATIS.3GPP.26.304V1101-2014 | 11.0.1 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.304(R11-11.0.1) | 11.0.1 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.304(R11-11.0.1) |
+
+#### 10.5.47 TS 26.346 Multimedia broadcast/multicast service (MBMS); Protocols and codecs
+
+This document defines a set of media codecs, formats and transport/application protocols to enable the deployment of MBMS user services either over the MBMS bearer service or other UMTS bearer services within the 3GPP system.
+
+In this version of the specification, only MBMS download and streaming delivery methods are specified. The present document does not preclude the use of other delivery methods.
+
+The present document includes information applicable to network operators, service providers and manufacturers.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.346 | 11.7.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26346-b70.pdf |
+| ETSI | TS 126 346 | 11.8.0 | Published | 2014-03-21 | http://www.etsi.org/deliver/etsi_ts/126300_126399/126346/11.08.00_60/ts_126346v110800p.pdf |
+| ATIS | ATIS.3GPP.26.346V1140-2014 | 11.4.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.346(R11-11.4.0) | 11.4.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.346(R11-11.4.0) |
+
+#### 10.5.48 TS 26.401 General audio codec audio processing functions; Enhanced aacPlus general audio codec; General description
+
+This telecommunication standard (TS) describes the detailed mapping from an MPEG-4 bitstream containing enhanced aacPlus coded audio to PCM sample output. The enhanced aacPlus audio codec is based on the AAC, SBR and parametric stereo coding tools defined in the MPEG-4 audio standard. In addition, it includes further tools such as error concealment, spline resampler, and stereo-to-mono downmix. It also describes the detailed mapping from a PCM sample input to an MPEG-4 bitstream containing enhanced aacPlus coded audio.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.401 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26401-b00.pdf |
+| ETSI | TS 126 401 | 11.0.0 | Published | 2012-10-12 | http://www.etsi.org/deliver/etsi_ts/126400_126499/126401/11.00.00/60/ts_126401v110000p.pdf |
+| ATIS | ATIS.3GPP.26.401V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.401(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.401(R11-11.0.0) |
+
+#### 10.5.49 TS 26.402 General audio codec audio processing functions; Enhanced aacPlus general audio codec; Additional decoder tools
+
+This telecommunication standard (TS) describes the error concealment algorithm, SBR parameter downmix and output resampling for the enhanced aacPlus general audio codec (3G TS 26.401).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.402 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26402-b00.pdf |
+| ETSI | TS 126 402 | 11.0.0 | Published | 2012-10-12 | http://www.etsi.org/deliver/etsi_ts/126400_126499/126402/11.00.00/60/ts_126402v110000p.pdf |
+| ATIS | ATIS.3GPP.26.402V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.402(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.402(R11-11.0.0) |
+
+#### 10.5.50 TS 26.403 General audio codec audio processing functions; Enhanced aacPlus general audio codec; Encoder specification AAC part
+
+This telecommunication standard (TS) describes the AAC encoder part of the enhanced aacPlus general audio codec (3G TS 26.401).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.403 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26403-b00.pdf |
+| ETSI | TS 126 403 | 11.0.0 | Published | 2012-10-12 | http://www.etsi.org/deliver/etsi_ts/126400_126499/126403/11.00.00/60/ts_126403v110000p.pdf |
+| ATIS | ATIS.3GPP.26.403V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.403(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.403(R11-11.0.0) |
+
+### 10.5.51 TS 26.404 General audio codec audio processing functions; Enhanced aacPlus general audio codec; Enhanced aacPlus encoder SBR part
+
+This telecommunication standard (TS) describes the SBR encoder part of the enhanced aacPlus general audio codec (3G TS 26.401).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.404 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26404-b00.pdf |
+| ETSI | TS 126 404 | 11.0.0 | Published | 2012-10-12 | http://www.etsi.org/deliver/etsi_ts/126400_126499/126404/11.00.00_60/ts_126404v110000p.pdf |
+| ATIS | ATIS.3GPP.26.404V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.404(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.404(R11-11.0.0) |
+
+### 10.5.52 TS 26.405 General audio codec audio processing functions; Enhanced aacPlus general audio codec; Encoder specification parametric stereo part
+
+This telecommunication standard (TS) describes the parametric stereo encoder part of the enhanced aacPlus general audio codec (3G TS 26.401).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.405 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26405-b00.pdf |
+| ETSI | TS 126 405 | 11.0.0 | Published | 2012-10-12 | http://www.etsi.org/deliver/etsi_ts/126400_126499/126405/11.00.00_60/ts_126405v110000p.pdf |
+| ATIS | ATIS.3GPP.26.405V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.405(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.405(R11-11.0.0) |
+
+### 10.5.53 TS 26.406 General audio codec audio processing functions; Enhanced aacPlus general audio codec; Conformance testing
+
+The document specifies the digital test sequences and conformance criteria for the Enhanced aacPlus audio codec.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.406 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26406-b00.pdf |
+| ETSI | TS 126 406 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/126400_126499/126406/11.00.00_60/ts_126406v110000p.pdf |
+
+### 10.5.54 TS 26.410 General audio codec audio processing functions; Enhanced aacPlus general audio codec; Floating-point ANSI-C code
+
+The present document contains an electronic copy of the ANSI-C code for the floating-point enhanced aacPlus codec (3G TS 26.401).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.410 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26410-b00.pdf |
+| ETSI | TS 126 410 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/126400_126499/126410/11.00.00_60/ts_126410v110000p.pdf |
+| ATIS | ATIS.3GPP.26.410V 1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.410(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.410(R11-11.0.0) |
+
+### 10.5.55 TS 26.411 General audio codec audio processing functions; Enhanced aacPlus general audio codec; Fixed-point ANSI-C code
+
+This document contains an electronic copy of the ANSI-C code for the fixed-point enhanced aacPlus codec as specified in TS 26.401.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.411 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26411-b00.pdf |
+| ETSI | TS 126 411 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/126400_126499/126411/11.00.00_60/ts_126411v110000p.pdf |
+| ATIS | ATIS.3GPP.26.411V 1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.411(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.411(R11-11.0.0) |
+
+### 10.5.56 TS 26.412 General audio codec audio processing functions; Source code for 3GP file format
+
+This document contains the source code of the 3GPP file format as specified in TS 26.244.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.412 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26412-b00.pdf |
+| ETSI | TS 126 412 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/126400_126499/126412/11.00.00_60/ts_126412v110000p.pdf |
+| ATIS | ATIS.3GPP.26.412V 1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-26.412(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.412(R11-11.0.0) |
+
+### 10.5.57 TS 26.430 Timed graphics
+
+This document defines a timed graphics media type which reuses components from existing media types. A transport system is defined as is a storage format.
+
+The specification is written in a forward-compatible way in order to allow additions of media components and functionality in future releases.
+
+It enhances the user experience by enabling graphics to be encoded as graphics (as opposed to video) and without requiring an umbrella system such as SMIL or DIMS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-26.430 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/26/A26430-b00.pdf |
+| ETSI | TS 126 430 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/126400_126499/126430/11.00.00_60/ts_126430v110000p.pdf |
+| ATIS | ATIS.3GPP.26.430V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.430(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.430(R11-11.0.0) |
+
+### 10.5.58 TR 26.851 Enhancements to multimedia (EMM); Download delivery enhancements (DDE) and IMS-based PSS and MBMS streaming synchronization enhancements (IPME) aspects
+
+The document contains the results of the work items EMM , EMM-DDE and EMM-IPME. This document does not include the results from the EMM-EFEC work item.
+
+### 10.5.59 TR 26.902 Video codec performance
+
+This document comprises a technical report on video codec performance, for packet-switched video-capable multimedia services standardized by 3GPP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.902 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/26/A26902-b00.pdf |
+| ETSI | TR 126 902 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_tr/126900_126999/126902/11.00.00_60/tr_126902v110000p.pdf |
+| ATIS | ATIS.3GPP.26.902V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.902(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.902(R11-11.0.0) |
+
+### 10.5.60 TR 26.903 Improved video support for packet switched streaming (PSS) and multimedia broadcast/multicast service (MBMS) Services
+
+This document provides an analysis of the future video capability requirements of streaming and multicast/broadcast services. The purpose of this document is two-fold. On the one hand, it studies the options to upgrade the minimal requirements for video reception and decoding. On the other hand, it studies use cases for support of more advanced UEs. The ultimate target of this study item is to recommend solutions for efficiently providing video support commensurate with UE and user capabilities and needs in PSS and MBMS services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.903 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/26/A26903-b00.pdf |
+| ETSI | TR 126 903 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_tr/126900_126999/126903/11.00.00_60/tr_126903v110000p.pdf |
+| ATIS | ATIS.3GPP.26.903V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.903(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-26.903(R11-11.0.0) |
+
+### 10.5.61 TR 26.904 Improved video coding support
+
+The present document provides an analysis of the future video capability requirements of streaming and multicast/broadcast services. The purpose of the present document is two-fold. On the one hand, it studies the options to upgrade the minimal requirements for video reception and decoding. On the other hand, it studies use cases for support of more advanced UEs. The ultimate target of this study item is to recommend solutions for efficiently providing video support commensurate with UE and user capabilities and needs in PSS and MBMS services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.904 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/26/A26904-b00.pdf |
+| ETSI | TR 126 904 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_tr/126900_126999/126904/11.00.00_60/tr_126904v110000p.pdf |
+| ATIS | ATIS.3GPP.26.904V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.904(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-26.904(R11-11.0.0) |
+
+### 10.5.62 TR 26.914 Multimedia telephony over IP multimedia subsystem (IMS); Optimization opportunities
+
+This document:
+
+- identifies opportunities for optimization of service quality and efficiency of multimedia telephony over IP in a qualitative sense;
+- provides the basis for developing a set of optional backward-compatible tools implementing such optimizations.
+
+The optimized multimedia telephony targets many different system configurations and operating conditions, e.g., GERAN, UTRAN, interworking between GERAN, UTRAN, GAN, and different PLMNs. Of the various use cases for multimedia telephony, the main focus of the present document is on voice calls, but the focus also includes other core media components, such as video. In particular, areas with optimization opportunities include handling of degraded channels, delay jitter, packet losses, efficiency, interworking with other voice systems, etc.
+
+The scope includes proposing solutions that maintain backward compatibility in order to ensure seamless interworking with existing services available in the CS domain, such as CS voice telephony and 3G-324M, as well as with terminals of earlier 3GPP releases. Alignment with legacy media formats avoids transcoding and even allows realizing at least parts of the optimization gains. All optimizations are hence based on the default codecs specified in TS 26.235 and TS 26.141.
+
+The optimizations identified in this document address mainly media transport and signalling. Most of the SIP signalling is out of scope. Issues regarding registration to the network and/or to IMS at power-on or at other occurrences are not included either.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.914 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/26/A26914-b00.pdf |
+| ETSI | TR 126 914 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_tr/126900_126999/126914/11.00.00_60/tr_126914v110000p.pdf |
+| ATIS | ATIS.3GPP.26.914V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.914(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.914(R11-11.0.0) |
+
+### 10.5.63 TR 26.935 Packet-switched conversational multimedia applications; Performance characterization of default codecs
+
+The present document provides information on the performances of default speech codecs in packet-switched conversational multimedia applications. The codecs under test are AMR-NB (adaptive multi-rate narrowband) and AMR-WB (adaptive multi-rate wideband). In addition, several ITU-T codecs (ITU-T G.723.1, ITU-T G.729, ITU-T G.722 and ITU-T G.711) are included in the testing. Experimental test results from the speech quality testing are reported to illustrate the behaviour of these codecs.
+
+The results give information of the performance of PS conversational multimedia applications under various operating and transmission conditions (e.g., considering radio transmission errors, IP packet losses, end-to-end delays, and several types of background noise). The performance results can be used, e.g., as guidance for network planning and to appropriately adjust the radio network parameters.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.935 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/26/A26935-b00.pdf |
+| ETSI | TR 126 935 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_tr/126900_126999/126935/11.00.00_60/tr_126935v110000p.pdf |
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ATIS | ATIS.3GPP.26.935V
1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-
26.935(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.935(R11-11.0.0) |
+
+#### 10.5.64 TR 26.936 Performance characterization of 3GPP audio codecs
+
+This document comprises the technical report for the characterization of the 3GPP audio codecs, enhanced aacPlus (*Eaac+*) and extended AMR-WB (*AMR-WB+*), standardized by 3GPP in Release 6 for packet-switched streaming service (PSS), multimedia messaging service (MMS), multimedia broadcast and multicast service (MBMS), and IMS messaging service and presence service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|-------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-
26.936 | 11.0.0 | ARIB
published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/26/A26936-b00.pdf |
+| ETSI | TR 126 936 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_tr/126900_126999/126936/11.00.00_60/tr_126936v110000p.pdf |
+| ATIS | ATIS.3GPP.26.936V
1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-
26.936(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.936(R11-11.0.0) |
+
+#### 10.5.65 TR 26.937 Transparent end-to-end packet-switched streaming service (PSS); RTP usage model
+
+The objective of this document is to characterize the 3GPP packet-switched streaming service (PSS). In doing so, the document considers the impacts of the underlying network configurations and how the streaming mechanism itself could be optimized.
+
+The scope of this document includes consideration of (non-exhaustive):
+
+- trade-off between radio usage efficiency and streaming QoS;
+- feedback of network conditions and adaptation of stream and/or the transmission of the stream;
+- optimal packetization of the media stream in line with the segmentation within the transport mechanism;
+- error robustness mechanisms (such as retransmission).
+
+Client buffering to ease the QoS requirements on the network and enable more flexibility in how the network transport resources are applied.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.937 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/26/A26937-b00.pdf |
+| ETSI | TR 126 937 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_tr/126900_126999/126937/11.00.00_60/tr_126937v110000p.pdf |
+| ATIS | ATIS.3GPP.26.937V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.937(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.937(R11-11.0.0) |
+
+### 10.5.66 TR 26.943 Recognition performance evaluations of codecs for speech-enabled services (SES)
+
+This technical report provides information on the recognition performance of the DSR extended advanced front end conducted by speech recognition vendors IBM and scan soft for the selection of a codec for speech-enabled services. The performance results are provided both as absolute word error rates for DSR and AMR-NB/AMR-WB on a range of extensive evaluation databases and as relative word error rate reductions when compared to both the AMR-NB and AMR-WB codecs.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.943 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/26/A26943-b00.pdf |
+| ETSI | TR 126 943 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_tr/126900_126999/126943/11.00.00_60/tr_126943v110000p.pdf |
+| ATIS | ATIS.3GPP.26.943V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.943(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.943(R11-11.0.0) |
+
+### 10.5.67 TR 26.946 Multimedia broadcast/multicast service (MBMS) user service guidelines
+
+MBMS user services can be built on top of the MBMS bearer service. This document describes the usage of the two delivery methods, which are defined in TS 26.346. The two delivery methods are streaming and download. Examples of applications using the download delivery method are news and software upgrades. Delivery of live music is an example of an application using the streaming delivery method.
+
+The objective of the document is to provide an overview of the MBMS system, and describes how the MBMS user services use the MBMS bearer services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.946 | 11.2.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/26/A26946-b20.pdf |
+| ETSI | TR 126 946 | 11.2.0 | Published | 2014-01-08 | http://www.etsi.org/deliver/etsi_tr/126900_126999/126946/11.02.00_60/tr_126946v110000p.pdf |
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | | | | 0/tr_126946v110200p.pdf |
+| ATIS | ATIS.3GPP.26.946V1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.946(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-26.946(R11-11.1.0) |
+
+### 10.5.68 TR 26.950 Study on surround sound codec extension for packet switched streaming (PSS) and multimedia broadcast/multicast service (MBMS)
+
+The present document investigates the potential user experience benefits of surround audio in 3GPP services. The investigation will be performed as follows:
+
+- Identify and document relevant use cases for surround sound in 3GPP.
+- Define design constraints that would need to be met by a surround audio codec extension method for adoption by 3GPP.
+- Identify suitable testing methodology for surround sound in relevant use cases of the PSS and MBMS services.
+- Define subjective minimum performance criteria that would need to be met in order to motivate the consideration of a surround audio coding extension for adoption by 3GPP.
+- Validate the user benefits and the feasibility of the deployment of surround sound for the PSS and MBMS services according to the defined minimum performance criteria, bit rate and design constraints for all the use cases (such as surround sound speaker set-up and headphone decoding mode) through evaluation of at least one example of surround sound coding methods which may be MPS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.950 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/26/A26950-b00.pdf |
+| ETSI | TR 126 950 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_tr/126900_126999/126950/11.00.00_60/tr_126950v110000p.pdf |
+| ATIS | ATIS.3GPP.26.950V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.950(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-26.950(R11-11.0.0) |
+
+### 10.5.69 TR 26.975 Performance characterization of the adaptive multi-rate (AMR) speech codec
+
+This document provides background information on the performances of the adaptive multirate (AMR) speech codec. Experimental test results from the verification and characterization phases of testing are reported to illustrate the behaviour of AMR in multiple operational conditions.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.975 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/26/A26975-b00.pdf |
+| ETSI | TR 126 975 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_tr/126900_126999/126975/11.00.00_60/tr_126975v110000p.pdf |
+| ATIS | ATIS.3GPP.26.975V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.975(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.975(R11-11.0.0) |
+
+### 10.5.70 TR 26.976 Performance characterization of the adaptive multi-rate wideband (AMRWB) speech codec
+
+This document provides information of the AMR wideband (AMR-WB) characterization, verification and selection phases. Experimental test results from the speech quality-related testing are reported to illustrate the behaviour of the AMR-WB codec. Additional information is provided, e.g., on implementation complexity of the AMR-WB codec. Also the verification results for the floating-point version of the AMR-WB codec (3G TS 26.204) are presented.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.976 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/26/A26976-b00.pdf |
+| ETSI | TR 126 976 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_tr/126900_126999/126976/11.00.00_60/tr_126976v110000p.pdf |
+| ATIS | ATIS.3GPP.26.976V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.976(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.976(R11-11.0.0) |
+
+### 10.5.71 TR 26.978 Results of the adaptive multi-rate (AMR) noise suppression selection phase
+
+The present document provides background information on the performance of the six candidates which were proposed as solutions for publication of an example noise suppression solution for application to the GSM adaptive multi-rate (AMR) speech codec. Experimental test results from the speech quality-related testing are reported to illustrate the behaviour of the candidate algorithms in multiple operational conditions. Additional information is also provided covering data not necessarily directly associated with speech quality (such as complexity, delay, effect on voice activity factor).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-26.978 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/26/A26978-b00.pdf |
+| ETSI | TR 126 978 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_tr/126900_126999/126978/11.00.00_60/tr_126978v110000p.pdf |
+| ATIS | ATIS.3GPP.26.978V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-26.978(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-26.978(R11-11.0.0) |
+
+## 10.6 27-series, Data
+
+### 10.6.1 TS 27.001 General on terminal adaptation functions (TAF) for mobile stations (MS)
+
+The present document is based on the principles of terminal adaptor functions presented in the ITU-T I-series of Recommendations (I.460 to I.463).
+
+The PLMN supports a wide range of voice and non-voice services in the same network. In order to enable non-voice traffic in the PLMN, there is a need to connect various kinds of terminal equipment to the mobile termination (MT). The target of the present document is to outline the functions needed for the terminal adaptation.
+
+The bearer services are described in 3GPP TS 22.002 and the general network configuration is described in 3GPP TS 23.002. The PLMN access reference configuration is defined in 3GPP TS 23.002. The various connection types used in the A/Gb mode or GERAN Iu mode PLMN are presented in 3GPP TR 21.905 and 3GPP TS 29.990. For support of data services between a PLMN and other networks, see 3GPP TS 29.007.
+
+The present document is valid for a 2nd generation PLMN (A/Gb mode) as well as for a third generation PLMN (Iu mode). If text applies only for one of these systems, it is explicitly mentioned by using the terms "A/Gb mode" and "Iu mode". If text applies to both of the systems, but a distinction between the ISDN/PSTN and the PLMN is necessary, the term "PLMN" is used.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 127 001 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/127000_127099/127001/11.00.00_60/ts_127001v110000p.pdf |
+| ATIS | ATIS.3GPP.27.001V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-27.001(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-27.001(R11-11.0.0) |
+| TTC | TS-3GA-27.001(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-27.001(Rel11)v11.0.0.pdf |
+
+### 10.6.2 TS 27.002 Terminal adaptation functions (TAF) for services using asynchronous bearer capabilities
+
+The document defines the interfaces and terminal adaptation functions (TAFs) integral to a mobile termination (MT) which enable the use of asynchronous bearer services in the PLMN and the attachment of asynchronous terminals to a MT (see TS 44.002 and TS 23.101).
+
+The general aspects of terminal adaptation functions are contained in TS 27.001.
+
+This document covers support of these services for the following interfaces and procedures:
+
+- [ITU-T V.14] procedures;
+- [ITU-T V.21] DTE/DCE interface;
+- [ITU-T V.22 *bis*] DTE/DCE interface;
+- [ITU-T V.32] DTE/DCE procedures;
+- [ITU-T I.420] S interface;
+- [ITU-T V.250] signalling procedures.
+
+The asynchronous data rates between the MT and the IWF are defined in TS 22.002.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 127 002 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/127000_127099/127002/11.00.00/60/ts_127002v110000p.pdf |
+| ATIS | ATIS.3GPP.27.002V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-27.002(R11-11.0.1) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-27.002(R11-11.0.0) |
+| TTC | TS-3GA-27.002(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-27.002(Rel11)v11.0.0.pdf |
+
+### 10.6.3 TS 27.003 Terminal adaptation functions (TAFs) for services using synchronous bearer capabilities
+
+The document defines terminal adaptation functions (TAFs) which are integrated in a mobile termination (MT) and which enable the use of synchronous bearer services in the PLMN and the attachment of synchronous terminals to an MT (see TS 24.002). For the case where asynchronous terminals are attached to the TAF when using synchronous bearer services in the PLMN, the reader is referred to TS 27.002 for the asynchronous MT-TAF interface specifics and to this document for synchronous bearer service specifics on the TAF-IWF interface. The general aspects of terminal adaptation functions are contained in specification TS 27.001. This document covers support of synchronous data services (see TS 22.002) for the following interfaces and procedures:
+
+- [ITU-T V.22] DTE/DCE interface;
+- [ITU-T V.22 *bis*] DTE/DCE interface;
+- [ITU-T V.26 *ter*] DTE/DCE interface;
+- [ITU-T X.21 *bis*] DTE/DCE interface;
+- [ITU-T X.32] procedure;
+- [ITU-T V.25 *bis*] procedure.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 127 003 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/127000_127099/127003/11.00.00_60/ts_127003v110000p.pdf |
+| ATIS | ATIS.3GPP.27.003V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-27.003(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-27.003(R11-11.0.0) |
+| TTC | TS-3GA-27.003(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-27.003(Rel11)v11.0.0.pdf |
+
+#### 10.6.4 TS 27.005 Use of data terminal equipment – data circuit-terminating equipment (DTE – DCE) interface for short message service (SMS) and cell broadcast service (CBS)
+
+This technical specification (TS) defines three interface protocols for control of SMS functions within a GSM/UMTS mobile telephone from a remote terminal via an asynchronous interface.
+
+This document defines a binary protocol ("Block Mode"). The protocol includes error protection and is suitable for use where the link may not be completely reliable. It will be of particular use where control of remote devices is required. Efficient transfer of binary encoded user data is possible.
+
+This document defines a character-based interface based on "AT" commands ("Text Mode"). This mode is suitable for unintelligent terminals or terminal emulators, and for application software built on command structures like those defined in [ITU-T V.25 *ter*]. Some of the commands defined in clause 3 will also be useful for implementations of clause 2 and/or clause 4, for example enabling an indication of incoming SMS messages.
+
+This document defines a character-based interface with hex-encoded binary transfer of message blocks ("PDU Mode"). This mode is suitable for software drivers based on AT command structures which do not understand the content of the message blocks and can only pass them between the MT and "upper level" software resident in the TE.
+
+In all three modes, the terminal is considered to be in control for SMS/CBS transactions.
+
+This specification considers the mobile termination to be a single entity. Other 3G/GSM technical specifications describe the split of functionality between the mobile equipment and (U)SIM.
+
+The three "modes" referred to above are represented in Figure 10.6.4-1.
+
+The "Block mode" is a self-contained mode in its own right, and when entered, control will remain within that mode until the procedures to exit the mode are executed, after which control is returned to the V.25 *ter* "command" state or "on-line command" state.
+
+The "Text" and "PDU" modes are not in themselves V.25 *ter* states but are simply sets of commands that will operate in either the V.25 *ter* "command" state or "on-line command" state. The "Text" and "PDU" modes are transitory states and after each operation, control is automatically returned to the V.25 *ter* "command" state or "on-line command" state. Whilst in the V.25 *ter* command state, the MS is available to handle incoming and outgoing calls such as data or facsimile.
+
+
+
+Q.1743(16)\_F10.6.4-1
+
+Diagram showing the relationship between V.25 ter states and SMS modes. A large circle contains two smaller circles labeled 'SMS text mode' and 'SMS PDU mode'. Above these circles, text reads 'V.25 ter "command" state and "on-line command" state'. Below the large circle, a rectangle is labeled 'SMS block mode'.
+
+**Figure 10.6.4-1 – Block, text and PDU modes**
+
+In the "Block mode" and "PDU" mode, a mobile is not permitted to modify any component of an SMS/CBS message received from the air interface or an SMS message received from a TE, before passing it on, except where TS 23.040 or TS 23.041 defines a "component modification facility" and where this "component modification facility" is supported by the mobile. In the text mode, the mobile may be unable to display characters coded in particular coding schemes. In this case, the mobile shall behave as described in TS 23.038 and assume the coding scheme to be the GSM 7-bit default alphabet.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-27.005 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/27/A27005-b00.pdf |
+| ETSI | TS 127 005 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/127000_127099/127005/11.00.00_60/ts_127005v110000p.pdf |
+| ATIS | ATIS.3GPP.27.005V 1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-27.005(R11-11.0.1) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-27.005(R11-11.0.0) |
+
+### 10.6.5 TS 27.007 AT command set for user equipment (UE)
+
+The document specifies a profile of AT commands and recommends that this profile be used for controlling mobile termination (MT) functions and GSM/UMTS network services from a terminal equipment (TE) through terminal adaptor (TA). The command prefix +C is reserved for digital cellular in [ITU-T V.25 *ter*]. This document has also the syntax details used to construct these extended GSM/UMTS commands. Commands from [ITU-T V.25 *ter*] and existing digital cellular standards (TIA IS99 and TIA IS135) are used whenever applicable. Some of the new commands are defined in such way that they can be easily applied to MT of networks other than GSM/UMTS. [ITU-T T.31] and [ITU-T T.32] fax AT commands may be used for GSM/UMTS fax transmission from TE. GSM/UMTS short message service AT commands are defined in 3G TS 27.005. GPRS AT commands are defined in clause 10 of this specification. This document assumes an abstract architecture comprising a TE (e.g., a computer) and a MT interfaced by a TA (see Figure 10.6.5-1).
+
+The span of control of the defined commands should allow handling any physical implementation that this abstract architecture may lead to:
+
+- TA, MT and TE as three separate entities;
+- TA integrated under the MT cover, and the TE implemented as a separate entity;
+- TA integrated under the TE cover, and the MT implemented as a separate entity;
+- TA and MT integrated under the TE cover as a single entity.
+
+
+
+Diagram of the Set-up architecture showing three main components: TE (Terminal Equipment), TA (Terminal Adapter), and MT (Mobile Terminal). The TE is connected to 'USER and APPLICATIONS' via a bidirectional arrow. The TE sends 'AT cmds' to the TA and receives 'responses' from it. The TA sends 'MT status' and 'MT control' to the MT. The MT is connected to 'NETWORK' via a bidirectional arrow labeled 'Network messages'. A reference code 'Q.1743(16)\_F10.6.5-1' is shown at the bottom right.
+
+**Figure 10.6.5-1 – Set-up**
+
+The commands described in this document may be observed on the link between the TE and the TA. However, most of the commands retrieve information about the MT, not about the TA.
+
+Interface between TE and TA is intended to operate over existing serial [ITU-T V.24] cables, infrared link, and all link types with similar behaviour. For correct operation, many of the defined commands require eight-bit data, and therefore it is recommended that TETA link is set to eight bits/byte mode. (For infrared operation implementation, refer to informative references infrared data association (IrDA). For embedding AT commands and data during on-line data state, refer to TTA IS617 [ITU-T V.80]). Interface between TA and MT is dependent on the interface in the MT.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-27.007 | 11.8.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/27/A27007-b80.pdf |
+| ETSI | TS 127 007 | 11.8.0 | Published | 2013-10-02 | http://www.etsi.org/deliver/etsi_ts/127000_127099/127007/11.08.00_60/ts_127007v110800p.pdf |
+| ATIS | ATIS.3GPP.27.007V1160-2014 | 11.6.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-27.007(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatdesc.jsp?stdno=TTAT.3G-27.007(R11-11.6.0) |
+
+#### 10.6.6 TS 27.010 Terminal equipment to user equipment (TE-UE) multiplexer protocol
+
+The document is to define a multiplexing protocol between a UE and a TE. The multiplexing protocol can be used to send any data, for instance, voice, SMS, USSD, fax, etc.
+
+The document describes the protocol, but not the commands or data transported with it.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-27.010 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/27/A27010-b00.pdf |
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 127 010 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/127000_127099/127010/11.00.00_60/ts_127010v110000p.pdf |
+| ATIS | ATIS.3GPP.27.010V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-27.010(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-27.010(R11-11.0.0) |
+
+### 10.6.7 TS 27.060 Packet domain; Mobile station (MS) supporting packet-switched services
+
+The document defines the requirements for TE-MT interworking over the R-reference point for the packet domain, within the GSM and 3G systems. It is up to the manufacturer how to implement the various functions but this document and existing Technical Specifications 27.001, 27.002, and 27.003 shall be followed where applicable.
+
+It is the intention that this document shall remain as the specification to develop a MS for the support of packet-switched services and its text includes references to UMTS/GSM standards.
+
+The UMTS/GSM PLMN supports a wide range of voice and non-voice services in the same network. In order to enable non-voice traffic in the PLMN, there is a need to connect various kinds of terminal equipments to the mobile station (MS). This document defines the requirements for TEMT interworking over the R-reference point for the packet domain, including the protocols and signalling needed to support packet-switched services, as defined in TS 22.060 and TS 23.060.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 127 060 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/127000_127099/127060/11.00.00_60/ts_127060v110000p.pdf |
+| ATIS | ATIS.3GPP.27.060V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-27.060(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-27.060(R11-11.0.0) |
+
+## 10.7 29-series, Signalling protocols – intra-fixed-network
+
+### 10.7.1 TS 29.010 Information element mapping between mobile station – base station system (MS – BSS) and base station system – mobile-services switching centre (BSS – MSC) signalling procedures and the mobile application part (MAP)
+
+The scope of the document is:
+
+- to provide a detailed specification for the interworking between information elements contained in layer 3 messages sent on the MS-MSC interface (call control and mobility management parts of GSM 04.08) and parameters contained in MAP services sent over the MSC-VLR interface (GSM 09.02) where the MSC acts as a transparent relay of information;
+- to provide a detailed specification for the interworking between information elements contained in BSSMAP messages sent on the BSC-MSC interface (GSM 08.08) and parameters contained in MAP services sent over the MSC-VLR interface (GSM 09.02) where the MSC acts as a transparent relay of information;
+- to provide a detailed specification for the interworking between information elements contained in BSSMAP messages (TS 48.008) and RANAP (TS 25.413);
+
+- iv) to provide a detailed specification for the interworking as in i) and ii) above when the MSC also processes the information.
+
+Interworking for supplementary services is given in GSM 09.11. Interworking for the short message service is given in GSM 03.40 and GSM 04.11. Interworking between the call control signalling of GSM 04.08 and the PSTN/ISDN is given in GSM 09.03, GSM 09.07 and TS 49.008. Interworking between the 'A' and 'E' interfaces for inter-MSC handover signalling is given in GSM 09.07 and 09.08.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 010 | 11.1.0 | Published | 2014-03-18 | http://www.etsi.org/deliver/etsi_ts/129000_129099/129010/11.01.00_60/ts_129010v110100p.pdf |
+| ATIS | ATIS.3GPP.29.010V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.010(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.010(R11-11.0.0) |
+| TTC | TS-3GA-29.010(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.010(Rel11)v11.0.0.pdf |
+
+### 10.7.2 TS 29.061 Interworking between the public land mobile network (PLMN) supporting packet-based services and packet data networks (PDNs)
+
+The document defines the requirements for packet domain interworking between a:
+
+- PLMN and PDN;
+- PLMN and PLMN.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 061 | 11.6.0 | Published | 2014-03-18 | http://www.etsi.org/deliver/etsi_ts/129000_129099/129061/11.06.00_60/ts_129061v110600p.pdf |
+| ATIS | ATIS.3GPP.29.061V1140-2014 | 11.4.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.061(R11-11.4.0) | 11.4.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.061(R11-11.4.0) |
+| TTC | TS-3GA-29.061(Rel11)v11.5.0 | 11.5.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.061(Rel11)v11.5.0.pdf |
+
+### 10.7.3 TS 29.108 Application of the radio access network application part (RANAP) on the E interface
+
+The document describes the subset of radio access network application part (RANAP) messages and procedures, defined in TS 25.413, which is used on the E interface. A general description can be found in TS 23.002 and TS 23.009.
+
+For the initiation and execution of relocation of SRNS ("relocation" for short, throughout the whole document) between MSCs, a subset of RANAP procedures are used. For the subsequent control of resources allocated to the user equipment (UE), RANAP procedures are used. The direct transfer elementary procedure (EP) of RANAP is used for the transfer of connection management and mobility management messages between the UE and the controlling 3G\_MSC.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 108 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/129100_129199/129108/11.00.00_60/ts_129108v110000p.pdf |
+| ATIS | ATIS.3GPP.29.108V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.108(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.108(R11-11.0.0) |
+| TTC | TS-3GA-29.108(Rel11)v11.1.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.108(Rel11)v11.0.0.pdf |
+
+#### 10.7.4 TS 29.109 Generic authentication architecture (GAA); Zh and Zn interfaces based on the Diameter protocol; Stage 3
+
+The present Stage 3 specification defines the Diameter-based implementation for bootstrapping Z interface (BSF-HSS) and GAA application Zn interface (BSF-NAF) in generic authentication architecture (GAA). The definition contains procedures, message contents and coding. The procedures for bootstrapping and usage of bootstrapped security association are defined in 3G TS 33.220.
+
+This specification is a part of the generic authentication architecture (GAA) specification series.
+
+The Diameter-based implementation is based on re-usage of Cx interface MultimediaAuthRequest/Answer messages originally between CSCF and HSS. These messages are defined in 3GPP TS 29.229. The 3GPP IMS mobility management uses the same definitions between CSCF and HSS. The present document defines how the defined messages are used with the bootstrapping and GAA application procedures (e.g., subscriber certificates) and the application logic that is needed in GAA network elements (BSF, HSS, and NAF).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 109 | 11.5.0 | Published | 2014-03-18 | http://www.etsi.org/deliver/etsi_ts/129100_129199/129109/11.05.00_60/ts_129109v110500p.pdf |
+| ATIS | ATIS.3GPP.29.109V1130-2014 | 11.3.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.109(R11-11.3.0) | 11.3.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.109(R11-11.3.0) |
+| TTC | TS-3GA-29.109(Rel11)v11.4.0 | 11.4.0 | TTC
Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-29.109(Rel11)v11.4.0.pdf |
+
+#### 10.7.5 TS 29.118 Mobility management entity (MME) – Visitor location register (VLR) SGs interface specification
+
+CS Fallback in the evolved packet system (EPS) enables the provisioning of CS-domain services (e.g., voice call, short messages service (SMS), location services (LCS) or supplementary services) by reuse of CS infrastructure when the UE is served by E-UTRAN.
+
+This document specifies the procedures and the SGs application part (SGsAP) messages used on the SGs interface between the mobility management entity (MME) in the EPS and the visitor location register (VLR), to allow location management coordination and to relay certain messages related to GSM circuit switched services over the EPS system.
+
+The document also specifies the use of stream control transmission protocol (SCTP) for the transport of SGsAP messages.
+
+This document is applicable to the MME in the EPS and to the VLR. The functional split between the MME and the VLR is defined in 3GPP TS 23.272.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 118 | 11.10.0 | Published | 2014-03-21 | http://www.etsi.org/deliver/etsi_ts/129100_129199/129118/11.10.00_60/ts_129118v111000p.pdf |
+| ATIS | ATIS.3GPP.29.118V 1160-2014 | 11.6.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.118(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.118(R11-11.6.0) |
+| TTC | TS-3GA-29.118(Rel11)v11.9.0 | 11.9.0 | TTC
Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-29.118(Rel11)v11.9.0.pdf |
+
+#### 10.7.6 TS 29.139 3GPP system – fixed broadband access network interworking; Home (e)Node B – security gateway interface
+
+The document specifies the H(e)NB – SeGW interface. The interface is used for the interworking between a 3GPP system and a fixed broadband access network defined by broadband forum. The interworking procedure provides the IP connectivity to a 3GPP UE using a H(e)NB connected to a fixed broadband access network as specified in 3GPP TS 23.139.
+
+The specification covers the QoS aspects and tunnel management procedures.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 139 | 11.1.0 | Published | 2013-01-28 | http://www.etsi.org/deliver/etsi_ts/129100_129199/129139/11.01.00_60/ts_129139v110100p.pdf |
+| ATIS | ATIS.3GPP.29.139V 1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.139(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.139(R11-11.1.0) |
+| TTC | TS-3GA-29.139(Rel11)v11.1.0 | 11.1.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.139(Rel11)v11.1.0.pdf |
+
+#### 10.7.7 TS 29.161 Interworking between the public land mobile network (PLMN) supporting packet-based services with wireless local area network (WLAN) access and packet data networks (PDNs)
+
+The present document describes the network interworking for the packet domain. Interworking to various external networks is defined together with the interworking for data forwarding while subscribers roam within the 3GPP system.
+
+The present document defines the requirements for packet domain interworking between a:
+
+- PLMN with WLAN access and PDN;
+- PLMN with WLAN access and PLMN.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 161 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/129100_129199/129161/11.00.00_60/ts_129161v110000p.pdf |
+| ATIS | ATIS.3GPP.29.161V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.161(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.161(R11-11.0.0) |
+| TTC | TS-3GA-29.161(Rel11)v11.0.1 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.161(Rel11)v11.0.0.pdf |
+
+### 10.7.8 TS 29.162 Interworking between the IM CN subsystem and IP networks
+
+The IM CN subsystem interworks with the external IP networks through the Mb reference point.
+
+This document details the interworking between the IM CN subsystem and external IP networks for IM service support. It addresses the issues of control plane interworking, user plane interworking and IP version interworking.
+
+The IP version interworking, between IP version 4 IETF RFC 791: "*Internet Protocol*" and IP version 6 IETF RFC 1883 (IETF RFC 2460: "*Internet Protocol, Version 6 (IPv6) Specification*") detailed in terms of the processes and protocol mappings required in order to support both mobile originated (MO) and terminated calls.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 162 | 11.2.0 | Published | 2014-01-13 | http://www.etsi.org/deliver/etsi_ts/129100_129199/129162/11.02.00_60/ts_129162v110200p.pdf |
+| ATIS | ATIS.3GPP.29.162V1110-2014 | 11.1.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.162(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.162(R11-11.1.0) |
+| TTC | TS-3GA-29.162(Rel11)v11.2.0 | 11.2.0 | TTC
Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-29.162(Rel11)v11.2.0.pdf |
+
+### 10.7.9 TS 29.163 Interworking between the IP multimedia (IM) core network (CN) subsystem and circuit-switched (CS) networks
+
+The present document specifies the principles of interworking between the 3GPP IM CN subsystem and BICC/ISUP based legacy CS networks, in order to support IM basic voice calls.
+
+The present document addresses the areas of control and user plane interworking between the IM CN subsystem and CS networks through the network functions, which include the MGCF and IMMGW. For the specification of control plane interworking, areas such as the interworking between SIP and BICC or ISUP are detailed in terms of the processes and protocol mappings required for the support of both IM originated and terminated voice calls.
+
+Other areas addressed encompass the transport protocol and signalling issues for negotiation and mapping of bearer capabilities and QoS information.
+
+The present document specifies the interworking between 3GPP profile of SIP (as detailed according to 3GPP TS 24.229) and BICC or ISUP, as specified in [ITU-T Q.1902.1] to
+
+[ITU-T Q.1902.6]: "*Bearer Independent Call Control*" and Recs ITU-T Q.761 to ITU-T Q.764: "*Signalling System No. 7 – ISDN User Part Signalling procedures*" respectively.
+
+The present document addresses two interworking scenarios with respect to the properties of the CS network:
+
+- The CS network does not use any 3GPP specific additions.
+- The CS network uses 3GPP-specific additions.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 163 | 11.10.0 | Published | 2014-03-18 | http://www.etsi.org/deliver/etsi_ts/129100_129199/129163/11.10.00_60/ts_129163v111000p.pdf |
+| ATIS | ATIS.3GPP.29.163V 1160-2014 | 11.6.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.163(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.163(R11-11.6.0) |
+| TTC | TS-3GA-29.163(Rel11)v11.9.0 | 11.9.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-29.163(Rel11)v11.9.0.pdf |
+
+#### 10.7.10 TS 29.165 Inter-IMS network to network interface
+
+The objective of this document is to address the Inter-IMS network to network interface (II-NNI) consisting of Iei and Izi reference points between IMS networks in order to support end-to-end service interoperability.
+
+The present document will address the issues related to control plane signalling (3GPP usage of SIP and SDP protocols, required SIP headers) as well as other interconnecting aspects like security, numbering/naming/addressing and user plane issues as transport protocol, media and codecs actually covered in a widespread set of 3GPP specifications. A profiling of the inter-IMS network to network interface (II-NNI) is also provided.
+
+Charging aspects will be addressed as far as SIP signalling is concerned.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 165 | 11.10.0 | Published | 2014-03-19 | http://www.etsi.org/deliver/etsi_ts/129100_129199/129165/11.10.00_60/ts_129165v111000p.pdf |
+| ATIS | ATIS.3GPP.29.165V 1160-2014 | 11.6.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.165(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.165(R11-11.6.0) |
+| TTC | TS-3GA-29.165(Rel11)v11.9.0 | 11.9.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-29.165(Rel11)v11.9.0.pdf |
+
+#### 10.7.11 TS 29.168 Cell broadcast centre interfaces with the evolved packet core; Stage 3
+
+The present document specifies the procedures and the SBc application part (SBc-AP) messages used on the SBc-AP interface between the mobility management entity (MME) and the cell broadcast centre (CBC).
+
+The present document supports the following functions.
+
+- Warning message transmission function in the EPS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 168 | 11.4.0 | Published | 2012-10-26 | http://www.etsi.org/deliver/etsi_ts/129100_129199/129168/11_04_00_60/ts_129168v110400p.pdf |
+| ATIS | ATIS.3GPP.29.168V
1140-2014 | 11.4.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-
29.168(R11-11.4.0) | 11.4.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.168(R11-11.4.0) |
+| TTC | TS-3GA-
29.168(Rel11)v11.4.0 | 11.4.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.168(Rel11)v11_4_0.pdf |
+
+#### **10.7.12 TS 29.171 Location services (LCS); LCS application protocol (LCS-AP) between the mobile management entity (MME) and evolved serving mobile location centre (E-SMLC); SLs interface**
+
+This document specifies the procedures and information coding for LCS application protocol (LCS-AP) that is needed to support the location services in E-UTRAN. The LCS-AP message set is applicable to the SLs interface between the E-SMLC and the MME. LCS-AP is developed in accordance to the general principles stated in 3GPP TS 23.271.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 171 | 11.3.0 | Published | 2013-06-28 | http://www.etsi.org/deliver/etsi_ts/129100_129199/129171/11_03_00_60/ts_129171v110300p.pdf |
+| ATIS | ATIS.3GPP.29.171V
1120-2014 | 11.2.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-
29.171(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.171(R11-11.2.0) |
+| TTC | TS-3GA-
29.171(Rel11)v11.3.0 | 11.3.0 | TTC
Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.171(Rel11)v11_3_0.pdf |
+
+#### **10.7.13 TS 29.172 Location services (LCS); evolved packet core (EPC) LCS protocol (ELP) between the gateway mobile location centre (GMLC) and the mobile management entity (MME); SLg interface**
+
+This document specifies the procedures and information coding for the EPC LCS protocol (ELP) that is needed to support the location services in E-UTRAN. The ELP message set is applicable to the SLg interface between the MME and the GMLC. ELP is developed in accordance to the general principles stated in 3GPP TS 23.271.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 172 | 11.1.0 | Published | 2013-09-24 | http://www.etsi.org/deliver/etsi_ts/129100_129199/129172/11_01_00_60/ts_129172v110100p.pdf |
+| ATIS | ATIS.3GPP.29.172V
1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-29.172(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-29.172(R11-11.0.0) |
+| TTC | TS-3GA-29.172(Rel11)v11.1.0 | 11.1.0 | TTC
Approved | 2013-11-22 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.172(Rel11)v11.1.0.pdf |
+
+#### 10.7.14 TS 29.173 Location services (LCS); Diameter-based SLh interface for control plane LCS
+
+The present document describes the Diameter-based SLh interface between the GMLC and the HSS defined for the control plane LCS in EPC.
+
+LCS procedures over the SLh interface are defined in the 3GPP TS 23.271.
+
+This specification defines the Diameter application for the GMLC-HSS, SLh reference point. The interactions between the HSS and the GMLC are specified, including the signalling flows. As LCS procedures over the Diameter-based SLh interface are identical to the MAP-based Lh interface, the descriptions of the Lh MAP operations defined in the 3GPP TS 29.002 are mapped into the descriptions of the SLh Diameter commands.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 173 | 11.1.0 | Published | 2013-01-28 | http://www.etsi.org/deliver/etsi_ts/129100_129199/129173/11.01.00_60/ts_129173v110100p.pdf |
+| ATIS | ATIS.3GPP.29.173V1110-2014 | 11.1.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.173(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-29.173(R11-11.1.0) |
+| TTC | TS-3GA-29.173(Rel11)v11.1.0 | 11.1.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.173(Rel11)v11.1.0.pdf |
+
+#### 10.7.15 TS 29.202 Signalling System No. 7 (SS7) signalling transport in core network; Stage 3
+
+The document defines the possible protocol architectures for transport of SS7 signalling protocols in core network.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 202 | 11.0.0 | Published | 2012-10-25 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129202/11.00.00_60/ts_129202v110000p.pdf |
+| ATIS | ATIS.3GPP.29.202V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.202(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-29.202(R11-11.0.0) |
+| TTC | TS-3GA-29.202(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.202(Rel11)v11.0.0.pdf |
+
+### 10.7.16 TS 29.204 Signalling system No. 7 (SS7) security gateway; Architecture, functional description and protocol details
+
+This document provides functional description of the SS7 security gateway. The document covers also network architecture, routeing considerations, and protocol details.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 204 | 11.0.0 | Published | 2012-10-25 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129204/11.00.00_60/ts_129204v110000p.pdf |
+| ATIS | ATIS.3GPP.29.204V1100-201 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.204(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.204(R11-11.0.0) |
+| TTC | TS-3GA-29.204(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.204(Rel11)v11.0.0.pdf |
+
+### 10.7.17 TS 29.212 Policy and charging control over reference points
+
+This document provides the stage 3 specification of the Gx, Gxx and Sd reference points for the present release. The functional requirements and the Stage 2 specifications of the Gx, Gxx and Sd reference points are contained in TS 23.203. The Gx reference point lies between the policy and charging rule function and the policy and charging enforcement function. The Gxx reference point lies between the policy and charging rule function and the bearer binding and event reporting function. The Sd reference point lies between the policy and charging rule function and the traffic detection function.
+
+Whenever it is possible, the present document specifies the requirements for the protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 212 | 11.12.0 | Published | 2014-03-19 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129212/11.12.00_60/ts_129212v111200p.pdf |
+| ATIS | ATIS.3GPP.29.212V1180-2014 | 11.8.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.212(R11-11.8.0) | 11.8.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.212(R11-11.8.0) |
+| TTC | TS-3GA-29.212(Rel11)v11.11.1.0 | 11.11.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-29.212(Rel11)v11.11.0.pdf |
+
+### 10.7.18 TS 29.213 Policy and charging control signalling flows and QoS parameter mapping
+
+The specification adds detailed flows of policy and charging control (PCC) over the Rx and Gx reference points and their relationship with the bearer level signalling flows over the Gn interface.
+
+The calls flows depicted in this technical specification represent usual cases, i.e., not all situations are covered. Detailed information provided in TS 29.212 and TS 29.214 shall be taken into consideration.
+
+The present specification also describes the binding and the mapping of QoS parameters among SDP, UMTS QoS parameters, and QoS authorization parameters.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 213 | 11.10.0 | Published | 2014-03-19 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129213/11.10.00_60/ts_129213v111000p.pdf |
+| ATIS | ATIS.3GPP.29.213V1160-2014 | 11.6.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.213(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.213(R11-11.6.0) |
+| TTC | TS-3GA-29.213(Rel11)v11.9.0 | 11.9.0 | TTC
Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-29.213(Rel11)v11.9.0.pdf |
+
+### 10.7.19 TS 29.214 Policy and charging control over Rx reference point
+
+The present document provides the Stage 3 specification of the Rx reference point for the present release. The functional requirements and the Stage 2 specifications of the Rx reference point are contained in TS 23.203. The Rx reference point lies between the application function and the policy and charging rule function.
+
+Whenever it is possible, the present document specifies the requirements for the protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 214 | 11.12.0 | Published | 2014-03-19 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129214/11.12.00_60/ts_129214v111200p.pdf |
+| ATIS | ATIS.3GPP.29.214V1180-2014 | 11.8.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.214(R11-11.8.0) | 11.8.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.214(R11-11.8.0) |
+| TTC | TS-3GA-29.214(Rel11)v11.11.0 | 11.11.0 | TTC
Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-29.214(Rel11)v11.11.0.pdf |
+
+### 10.7.20 TS 29.215 Policy and charging control (PCC) over S9 reference point
+
+The present document provides the Stage 3 specification of the S9 reference point for the present release. The functional requirements of Stage 2 specification for the S9 reference point are contained in 3GPP TS 23.203. The S9 reference point lies between the PCRF in the home PLMN (also known as H-PCRF) and the PCRF in the visited PLMN (also known as V-PCRF).
+
+Whenever it is possible the present document specifies the requirements for the protocols by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible extensions to Diameter are defined within the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 215 | 11.12.0 | Published | 2014-03-19 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129215/11.12.00_60/ts_129215v111200p.pdf |
+| ATIS | ATIS.3GPP.29.215V1180-2014 | 11.8.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|------------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-29.215(R11-11.8.0) | 11.8.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.215(R11-11.8.0) |
+| TTC | TS-3GA-29.215(Rel11)v11.11.0 | 11.11.0 | TTC
Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-29.215(Rel11)v11.11.0.pdf |
+
+#### 10.7.21 TS 29.228 IP multimedia (IM) subsystem Cx and Dx interfaces; Signalling flows and message contents
+
+This technical specification (TS) specifies:
+
+- 1) the interactions between the HSS (home subscriber server) and the CSCF (call session control functions), referred to as the Cx interface;
+- 2) the interactions between the CSCF and the SLF (server locator function), referred to as the Dx interface.
+
+The IP multimedia (IM) subsystem Stage 2 is specified in 3G TS 23.228 and the signalling flows for the IP multimedia call control based on SIP and SDP are specified in 3G TS 24.228.
+
+This document addresses the signalling flows for Cx and Dx interfaces.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 228 | 11.10.0 | Published | 2013-12-18 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129228/11_10.00_60/ts_129228v111000p.pdf |
+| ATIS | ATIS.3GPP.29.228V1170-2014 | 11.7.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.228(R11-11.7.0) | 11.7.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.228(R11-11.7.0) |
+| TTC | TS-3GA-29.228(Rel11)v11.10.0 | 11.10.0 | TTC
Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-29.228(Rel11)v11.10.0.pdf |
+
+#### 10.7.22 TS 29.229 Cx and Dx interfaces based on the Diameter protocol; Protocol details
+
+The document defines a transport protocol for use in the IP multimedia (IM) core network (CN) subsystem based on Diameter.
+
+This document is applicable to:
+
+- the Cx interface between the I-CSCF/S-CSCF and the HSS;
+- the Dx interface between the I-CSCF/S-CSCF and the SLF.
+
+Whenever it is possible, this document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 229 | 11.4.0 | Published | 2013-07-02 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129229/11_04.00_60/ts_129229v110400p.pdf |
+| ATIS | ATIS.3GPP.29.229V1130-2014 | 11.3.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-29.229(R11-11.3.0) | 11.3.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.229(R11-11.3.0) |
+| TTC | TS-3GA-29.229(Rel11)v11.4.0 | 11.4.0 | TTC
Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.229(Rel11)v11.4.0.pdf |
+
+### 10.7.23 TS 29.230 Diameter applications; 3GPP specific codes and identifiers
+
+The document lists the 3GPP-specific Diameter protocol codes, including the AVP codes and experimental result codes.
+
+This document lists also the application identifiers assigned to 3GPP-specific Diameter applications by IANA and the Diameter command code range which is assigned to 3GPP by IANA.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 230 | 11.10.0 | Published | 2014-03-19 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129230/11.10.00_60/ts_129230v111000p.pdf |
+| ATIS | ATIS.3GPP.29.230V1160-2014 | 11.6.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.230(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.230(R11-11.6.0) |
+| TTC | TS-3GA-29.230(Rel11)v11.9.0 | 11.9.0 | TTC
Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-29.230(Rel11)v11.9.0.pdf |
+
+### 10.7.24 TS 29.231 Application of SIP-I protocols to circuit switched (CS) core network architecture; Stage 3
+
+This document describes the protocols to be used when SIP-I is optionally used as call control protocol in a 3GPP CS core network on Nc interface, see 3GPP TS 23.231. The SIP-I protocol operates between (G)MSC servers. The SIP-I architecture consists of a number of protocols. The following types of protocols are described: call control protocol, resource control protocols and user plane protocol for this architecture. The architecture complies with the requirements imposed by 3GPP TS 23.231 and TS 23.153.
+
+Interworking of SIP-I on Nc to external networks is described by TS 29.235.
+
+The document is valid for a third generation PLMN (UMTS) complying with Release 9 and later.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 231 | 11.0.0 | Published | 2012-10-26 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129231/11.00.00_60/ts_129231v110000p.pdf |
+| ATIS | ATIS.3GPP.29.231V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.231(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.231(R11-11.0.0) |
+| TTC | TS-3GA-29.231(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.231(Rel11)v11.0.0.pdf |
+
+### 10.7.25 TS 29.232 Media gateway controller (MGC) – Media gateway (MGW) interface; Stage 3
+
+The document describes the protocol to be used on the media gateway controller (MGC) – media gateway (MGW) interface. The media gateway controllers covered in this specification are the MSC server and the GMSC server. The basis for this protocol is the ITU-T H.248.1 MEGACO protocol as specified in ITU-T and IETF. The BICC architecture, as described in TS 23.205 and 29.205, defines the usage of this protocol.
+
+This specification describes the changes to ITU-T H.248.1/MEGACO which are needed to handle 3G specific traffic cases. This is done by using the ITU-T H.248.1/MEGACO standard extension mechanism.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 232 | 11.2.0 | Published | 2013-07-02 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129232/11_02_00_60/ts_129232v110200p.pdf |
+| ATIS | ATIS.3GPP.29.232V1110-2014 | 11.1.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.232(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.232(R11-11.1.0) |
+| TTC | TS-3GA-29.232(Rel11)v11.2.0 | 11.2.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.232(Rel11)v11.2.0.pdf |
+
+### 10.7.26 TS 29.234 3GPP system to wireless local area network (WLAN) interworking; Stage 3
+
+This document defines the Stage 3 protocol description for several reference points in the WLAN-3GPP interworking system.
+
+The document is applicable to:
+
+- the Dw reference point between the 3GPP AAA server and an SLF;
+- the Wa reference point between the WLAN AN and the 3GPP AAA proxy;
+- the Wd reference point between the 3GPP AAA proxy and 3GPP AAA server;
+- the Wx reference point between the 3GPP AAA server and the HSS;
+- the Wm reference point between the 3GPP AAA server and the PDG;
+- the Wn reference point between the WLAN AN and the 3GPP WAG;
+- the Wg reference point between the 3GPP AAA server/proxy and the WAG.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 234 | 11.2.0 | Published | 2013-06-28 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129234/11_02_00_60/ts_129234v110200p.pdf |
+| ATIS | ATIS.3GPP.29.234V1110-2014 | 11.1.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.234(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.234(R11-11.1.0) |
+| TTC | TS-3GA-29.234(Rel11)v11.2.0 | 11.2.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.234(Rel11)v11.2.0.pdf |
+
+### 10.7.27 TS 29.235 Interworking between SIP-I based circuit-switched core network and other networks
+
+This document specifies the interworking between SIP-I based circuit-switched core network, as specified in 3GPP TS 23.231 and 3GPP TS 29.231, with out-of-band transcoder control related procedures in 3GPP TS 23.153, and:
+
+- an external SIP-I based signalling network compliant to ITU-T Q.1912.5
+- an ISUP (Recommendations ITU-T Q.761 to ITU-T Q.764) based network such as an ISUP based 3GPP CS domain or an PSTN
+- an BICC (Recommendations ITU-T Q.1902.1 to ITU-T Q.1902.6 ) based network such as an BICC based 3GPP CS domain as specified in 3GPP TS 23.205 and 3GPP TS 29.205
+- an Internet multimedia subsystem, as specified in 3GPP TS 23.228 and 3GPP TS 24.229
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 235 | 11.3.0 | Published | 2013-09-25 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129235/11.03.00_60/ts_129235v110300p.pdf |
+| ATIS | ATIS.3GPP.29.235V 1110-2014 | 11.1.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.235(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.235(R11-11.1.0) |
+| TTC | TS-3GA-29.235(Rel11)v11.3.0 | 11.3.0 | TTC Approved | 2013-11-22 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.235(Rel11)v11.3.0.pdf |
+
+### 10.7.28 TS 29.238 Interconnection border control functions (IBCF) – Transition gateway (TrGW) interface, Ix interface; Stage 3
+
+This document describes the protocol to be used on the interconnection border control function (IBCF) – Transition gateway (TrGW) interface and the CS-IBCF – CS-TrGW interface. The basis for this protocol is the H.248 protocol as specified in ITU-T. The Profile provides MG control function for IMS and CS border control. The IMS architecture is described in 3GPP TS 23.228. The underlying reference model and stage 2 information is described in Annex I of 3GPP TS 23.228 and in 3GPP TS 29.162. The CS architecture is described in Annex A of 3GPP TS 29.235.
+
+This specification describes the application of ITU-T H.248 Ix profile for both Ix and CS-Ix interfaces (see Figure 10.7.28-1 and Figure 10.7.28-2). Required extensions use the ITU-T H.248 standard extension mechanism. In addition certain aspects of the base protocol ITU-T H.248 are not needed for this interface and thus excluded by this profile.
+
+
+
+Reference model for IMS border control functions. The diagram shows a UE connected to an IP-CAN, which is part of an IMS network. The IMS network contains P-CSCF, S-CSCF, I-CSCF, BGCF, DNS, and HSS. A dashed box labeled 'Border control functions' contains IBCF (with IMS-ALG and THIG) and TrGW. Signalling (dashed lines) flows from UE through IP-CAN, P-CSCF, S-CSCF, I-CSCF, BGCF, and IBCF. Bearer (solid lines) flows from UE through IP-CAN, P-CSCF, and TrGW. The IBCF and TrGW interface with an 'Other IMS/SIP network'.
+
+**Figure 10.7.28-1 – Reference model for IMS border control functions**
+
+
+
+Reference model for CS border control functions. The diagram shows an IWU connected to a UP-IWU via an Mc interface. The UP-IWU is connected to a CS-TrGW, which is part of a 'Border control logical functions' box containing CS-IBCF (with ALG and THIG). Signalling (dashed lines) flows from IWU through CS-IBCF to a 'SIP-I based 3GPP CS domain/External SIP-I network'. Bearer (solid lines) flows from UP-IWU through CS-TrGW to the same network.
+
+**Figure 10.7.28-2 – Reference model for CS border control functions**
+
+NOTE – the Ix profile is applied over both IMS and CS Ix interfaces
+
+In the text the specification, terms IBCF and TrGW also include respectively the CS-IBCF and CS-TrGW functionalities.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 238 | 11.2.0 | Published | 2013-07-01 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129238/11.02.00_60/ts_129238v110200p.pdf |
+| ATIS | ATIS.3GPP.29.238V 1110-2014 | 11.1.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.238(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-29.238(R11-11.1.0) |
+| TTC | TS-3GA-29.238(Rel11)v11.2.0 | 11.2.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.238(Rel11)v11.2.0.pdf |
+
+### 10.7.29 TS 29.240 3GPP generic user profile (GUP); Stage 3; Network
+
+This document defines the stage 3 network protocol description to the 3GPP generic user profile (GUP), which includes the elements necessary to realise the Stage 2 requirements in TS 23.240.
+
+The fact of having several domains within the 3GPP mobile system (e.g., circuit-switched, packet-switched, IP multimedia subsystem) and access technologies (e.g., GERAN, UTRAN and WLAN)
+
+introduces a wide distribution of data associated with the user. Further, the new functions both in terminals and networks mean that the data related to users, services and user equipment will be increased greatly. This causes difficulties for users, subscribers, network operators and value-added service providers to create, access and manage the user-related data located in different entities.
+
+The objective of specifying the 3GPP generic user profile is to provide a conceptual description to enable harmonized usage of the user-related information located in different entities. Technically, the 3GPP generic user profile provides an architecture, data description and interface with mechanisms to handle the data.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 240 | 11.0.0 | Published | 2012-10-26 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129240/11.00.00_60/ts_129240v110000p.pdf |
+| ATIS | ATIS.3GPP.29.240V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.240(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-29.240(R11-11.0.0) |
+| TTC | TS-3GA-29.240(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.240(Rel11)v11.0.0.pdf |
+
+### 10.7.30 TS 29.272 Interworking between SIP-I based circuit-switched core network and other networks
+
+This document describes the mobility management entity (MME) and serving GPRS support node (SGSN) related Diameter-based interfaces towards the home subscriber server (HSS), and the MME and the SGSN related Diameter-based interface towards the equipment identity register (EIR).
+
+This specification defines the Diameter application for the MME-HSS, S6a reference point, and for the SGSN-HSS, S6d reference point. The interactions between the HSS and the MME/SGSN are specified, including the signalling flows.
+
+This specification defines the Diameter application for the MME-EIR, S13 reference point, and for the SGSN-EIR, S13' reference point. The interactions between the MME/SGSN and the EIR are specified, including the signalling flows.
+
+If there is no specific indication, the SGSN in the specification refers to a S4-SGSN which supports S4 interface.
+
+The evolved packet system Stage 2 description (architecture and functional solutions) is specified in 3GPP TS 23.401 and in 3GPP TS 23.060.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 272 | 11.9.0 | Published | 2013-12-19 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129272/11.09.00_60/ts_129272v110900p.pdf |
+| ATIS | ATIS.3GPP.29.272V1160-2014 | 11.6.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.272(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-29.272(R11-11.6.0) |
+| TTC | TS-3GA-29.272(Rel11)v11.9.0 | 11.9.0 | TTC
Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-29.272(Rel11)v11.9.0.pdf |
+
+### 10.7.31 TS 29.273 Evolved packet system (EPS); 3GPP EPS AAA interfaces
+
+This document defines the Stage-3 protocol description for several reference points for the non-3GPP access in EPS.
+
+The present document is applicable to:
+
+- The SWa reference point between an un-trusted non-3GPP IP access and the 3GPP AAA Server/Proxy.
+- The STa reference point between a trusted non-3GPP IP access and the 3GPP AAA Server/Proxy.
+- The SWd reference point between the 3GPP AAA proxy and 3GPP AAA Server.
+- The SWx reference point between the 3GPP AAA server and the HSS.
+- The S6b reference point between the 3GPP AAA server/proxy and the PDN GW.
+- The H2 reference point between the 3GPP AAA server and the HA.
+
+The SWm reference point between the 3GPP AAA server/proxy and the ePDG.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 273 | 11.9.0 | Published | 2014-03-19 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129273/11_09_00_60/ts_129273v110900p.pdf |
+| ATIS | ATIS.3GPP.29.273V1150-2014 | 11.5.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.273(R11-11.5.0) | 11.5.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.273(R11-11.5.0) |
+| TTC | TS-3GA-29.273(Rel11)v11.8.0 | 11.8.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-29.273(Rel11)v11.8.0.pdf |
+
+### 10.7.32 TS 29.274 3GPP Evolved packet system (EPS); Evolved general packet radio service (GPRS) tunnelling protocol for control plane (GTPv2-C); Stage 3
+
+This document specifies the stage 3 of the control plane of the GPRS tunnelling protocol, Version 2 for evolved packet system interfaces (GTPv2-C).
+
+In this document, unless otherwise specified the S5 interface refers always to "GTP-based S5" and S8 interface refers always to "GTP-based S8" interface.
+
+GTPv2-C shall be used across the following EPC signalling interfaces: S3, S4, S5, S8, S10, S11 and S16.
+
+GTPv2-C based protocols shall also be used across Sv (3GPP TS 29.280) and S101 (3GPP TS 29.276) interfaces.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 274 | 11.10.0 | Published | 2014-03-19 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129274/11_10_00_60/ts_129274v111000p.pdf |
+| ATIS | ATIS.3GPP.29.274V1160-2014 | 11.6.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.274(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.274(R11-11.6.0) |
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTC | TS-3GA-29.274(Rel11)v11.9.0 | 11.9.0 | TTC
Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-29.274(Rel11)v11.9.0.pdf |
+
+### 10.7.33 TS 29.275 Proxy mobile IPv6 (PMIPv6) based mobility and tunnelling protocols; Stage 3
+
+This document specifies the stage 3 of the PMIPv6 based mobility and tunnelling protocols used over the PMIP-based S2a, S2b, S5, and S8 reference points defined in 3GPP TS 23.402, and are thus applicable to the serving GW, PDN gateway, ePDG, and trusted non-3GPP access. Protocols specifications are compliant with relevant IETF RFCs. In this specification PMIP refers to PMIPv6 as defined in [IETF RFC 5213].
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 275 | 11.9.0 | Published | 2014-03-19 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129275/11_09_00_60/ts_129275v110900p.pdf |
+| ATIS | ATIS.3GPP.29.275V 1160-2014 | 11.6.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.275(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.275(R11-11.6.0) |
+| TTC | TS-3GA-29.275(Rel11)v11.8.0 | 11.8.0 | TTC
Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-29.275(Rel11)v11.8.0.pdf |
+
+### 10.7.34 TS 29.276 Optimized handover procedures and protocols between EUTRAN access and cdma2000 HRPD access
+
+This document specifies the Stage 3 of the evolved packet system S101 interface between the MME and the HRPD access network. The S101 interface supports procedures for pre-registration, session maintenance and active handoffs between E-UTRAN and HRPD networks.
+
+It also specifies the S103 interface between the Serving GW and HRPD PDSN. This user plane interface is used to forward DL data to minimize packet losses in mobility from E-UTRAN to HRPD. Signalling procedures on the S101 interface are used to set up tunnels on the S103 interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 276 | 11.0.0 | Published | 2012-10-26 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129276/11_00_00_60/ts_129276v110000p.pdf |
+| ATIS | ATIS.3GPP.29.276V 1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.276(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.276(R11-11.0.0) |
+| TTC | TS-3GA-29.276(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.276(Rel11)v11.0.0.pdf |
+
+### 10.7.35 TS 29.277 Optimized handover procedures and protocols between EUTRAN access and cdma2000 HRPD access
+
+This document specifies the Stage 3 of the evolved packet system S102 interface between the MME and the 1x CS IWS to relay the 1xCS signalling messages documented in 3GPP TS 23.216.
+
+The S102 interface is used to support UEs that do not transmit and receive on both the LTE and 1x radio interfaces simultaneously. S102 protocol aspects for SRVCC from E-UTRAN access to 3GPP2 1xCs is covered in this specification.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 277 | 11.1.0 | Published | 2013-01-29 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129277/11.01.00_60/ts_129277v110100p.pdf |
+| ATIS | ATIS.3GPP.29.277V1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.277(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.277(R11-11.1.0) |
+| TTC | TS-3GA-29.277(Rel11)v11.1.0 | 11.1.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.277(Rel11)v11.1.0.pdf |
+
+### 10.7.36 TS 29.279 Mobile IPv4 (MIPv4) based mobility protocols; Stage 3
+
+This document specifies the Stage 3 of the MIPv4 based mobility protocol used over the S2a reference point defined in 3GPP TS 23.402, and is thus applicable to the PDN gateway and trusted non-3GPP Access. Protocol specification is compliant with relevant IETF RFCs.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 279 | 11.0.0 | Published | 2012-10-26 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129279/11.00.00_60/ts_129279v110000p.pdf |
+| ATIS | ATIS.3GPP.29.279V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.279(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.279(R11-11.0.0) |
+| TTC | TS-3GA-29.279(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.279(Rel11)v11.0.0.pdf |
+
+### 10.7.37 TS 29.280 Evolved packet system (EPS); 3GPP Sv interface (MME to MSC, and SGSN to MSC) for SRVCC
+
+This document describes the Sv interface between the mobility management entity (MME) or serving GPRS support node (SGSN) and 3GPP MSC server enhanced for SRVCC. Sv interface is used to support Inter-RAT handover from VoIP/IMS over EPS to CS domain over 3GPP UTRAN/GERAN access or from UTRAN (HSPA) to 3GPP UTRAN/GERAN access.
+
+If there is no specific indication, the term "MSC server" denotes 3GPP MSC server enhanced for SRVCC as defined in 3GPP TS 23.216.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 280 | 11.5.0 | Published | 2013-09-25 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129280/11.05.00_60/ts_129280v110500p.pdf |
+| ATIS | ATIS.3GPP.29.280V 1130-2014 | 11.3.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.280(R11-11.3.0) | 11.3.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.280(R11-11.3.0) |
+| TTC | TS-3GA-29.280(Rel11)v11.5.0 | 11.5.0 | TTC Approved | 2013-11-22 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.280(Rel11)v11.5.0.pdf |
+
+### 10.7.38 TS 29.281 General packet radio System (GPRS) tunnelling protocol user plane (GTPv1-U)
+
+This document defines the user plane of GTP used on:
+
+- the Gn and Gp interfaces of the general packet radio service (GPRS);
+- the Iu, Gn and Gp interfaces of the UMTS system;
+- the S1-U, X2, S4, S5, S8 and S12 interfaces of the evolved packet system (EPS);
+
+This definition ensures full backwards compatibility with RNC, SGSN and GGSN implementations according to release 7 of 3GPP TS 29.060.
+
+NOTE – Releases previous to Release-8 have used 3GPP TS 29.060 as normative definition of the user plane of GTP. This shall be considered when essential corrections are included in the present document or in pre-release-8 version of 3GPP TS 29.060.
+
+Fallback from GTPv1-U to GTPv0-U shall not be supported. Therefore, 3GPP Rel-8 and onwards GTPv1-U entity should not listen to the well-known GTPv0 port 3386. If GTPv1 entity listens to the GTPv0 port, the entity shall silently discard any received GTPv0-U message.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 281 | 11.6.0 | Published | 2013-04-09 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129281/11.06.00_60/ts_129281v110600p.pdf |
+| ATIS | ATIS.3GPP.29.281V 1160-2014 | 11.6.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.281(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.281(R11-11.6.0) |
+| TTC | TS-3GA-29.281(Rel11)v11.6.0 | 11.6.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.281(Rel11)v11.6.0.pdf |
+
+### 10.7.39 TS 29.282 Mobile IPv6 vendor specific option format and usage within 3GPP
+
+This document specifies the format and usage of the mobile IPv6 vendor specific option within the third generation partnership project.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 282 | 11.1.0 | Published | 2013-01-29 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129282/11_01_00_60/ts_129282v110100p.pdf |
+| ATIS | ATIS.3GPP.29.282V 1110-2014 | 11.1.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.282(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.282(R11-11.1.0) |
+| TTC | TS-3GA-29.282(Rel11)v11.1.0 | 11.1.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.282(Rel11)v11.1.0.pdf |
+
+#### 10.7.40 TS 29.292 Interworking between the IP multimedia (IM) core network (CN) subsystem (IMS) and MSC server for IMS centralized services (ICS)
+
+IMS centralized services (ICS) enable the delivery of IM CN subsystem based multimedia telephony and supplementary services as defined in 3GPP TS 24.173 to users regardless of the attached access network type; e.g., CS domain access or IP-CAN.
+
+This document specifies the principles of interworking between the IM CN subsystem and CS domain in order to enable ICS for UEs using CS domain access.
+
+The present document addresses the area of registration procedures interworking between the CS domain and IM CN subsystem.
+
+The document addresses the areas of control and user plane interworking between the IM CN subsystem and CS domain through an MSC Server enhanced for ICS and circuit switched media gateway (CS-MGW) respectively. This includes the signalling procedures between the MSC Server and CS-MGW. For the specification of control plane interworking, present document defines the protocol interworking between the 3GPP profile of SIP as described in 3GPP TS 24.229 and NAS signalling as described in 3GPP TS 24.008 required for the support of IM CN subsystem based multimedia telephony and supplementary services.
+
+This document addresses the area of supplementary service configuration interworking between the CS domain and IM CN subsystem.
+
+The document is applicable to the MSC Server and CS-MGW.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 292 | 11.6.0 | Published | 2013-07-09 | http://www.etsi.org/deliver/etsi_ts/129200_129299/129292/11_06_00_60/ts_129292v110600p.pdf |
+| ATIS | ATIS.3GPP.29.292V 1150-2014 | 11.5.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.292(R11-11.5.0) | 11.5.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.292(R11-11.5.0) |
+| TTC | TS-3GA-29.292(Rel11)v11.6.0 | 11.6.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.292(Rel11)v11.6.0.pdf |
+
+#### 10.7.41 TS 29.303 Domain Name System Procedures; Stage 3
+
+This document describes Domain Name System (DNS) Procedures for the evolved packet system (EPS). This document covers the Evolved Packet Core gateway node selection using DNS (e.g.,
+
+SGW and PGW nodes) excluding all user equipment (UE) initiated DNS-based discovery and selection procedures.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 303 | 11.2.0 | Published | 2012-10-26 | http://www.etsi.org/deliver/etsi_ts/129300_129399/129303/11.02.00_60/ts_129303v110200p.pdf |
+| ATIS | ATIS.3GPP.29.303V 1120-2014 | 11.2.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.303(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-29.303(R11-11.2.0) |
+| TTC | TS-3GA-29.303(Rel11)v11.2.0 | 11.2.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.303(Rel11)v11.2.0.pdf |
+
+#### 10.7.42 TS 29.305 Interworking function (IWF) between MAP based and Diameter based interfaces
+
+This document specifies the interworking function (IWF) between MAP-based Gr, Gf interfaces and Diameter-based S6a, S6d, S13, S13a interfaces.
+
+For each IWF scenario, the present document will specify the mapping of related procedures and the corresponding parameter handling.
+
+The document will also specify the related mechanisms for the IWF, e.g., message routing, user data handling. The other mechanism, such as security, will also be described in this document as a part of the whole solution.
+
+If there is no specific indication, the SGSN in the specification refers to a S4-SGSN which supports S4 interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 305 | 11.7.0 | Published | 2013-12-19 | http://www.etsi.org/deliver/etsi_ts/129300_129399/129305/11.07.00_60/ts_129305v110700p.pdf |
+| ATIS | ATIS.3GPP.29.305V 1140-2014 | 11.4.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.305(R11-11.4.0) | 11.4.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-29.305(R11-11.4.0) |
+| TTC | TS-3GA-29.305(Rel11)v11.7.0 | 11.7.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-29.305(Rel11)v11.7.0.pdf |
+
+#### 10.7.43 TS 29.311 Service level interworking for messaging services
+
+This document specifies the protocol details of service level interworking between instant message using the 3GPP IP multimedia CN subsystem and the short message service over both legacy CS/PS network as specified in the 3GPP TS 23.040 and a generic IP connectivity access network (IP-CAN) as specified in the 3GPP TS 24.341. These include:
+
+- Procedures to implement service level interworking between IM and SM.
+- Enhancement of the IP-SM-GW as an application server to support service selection, authorization and mapping between IM and SM protocols.
+- Interaction between service level interworking and transport layer interworking.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 311 | 11.1.0 | Published | 2013-07-09 | http://www.etsi.org/deliver/etsi_ts/129300_129399/129311/11_01_00_60/ts_129311v110100p.pdf |
+| ATIS | ATIS.3GPP.29.311V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.311(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.311(R11-11.0.0) |
+| TTC | TS-3GA-29.311(Rel11)v11.1.0 | 11.1.0 | TTC
Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.311(Rel11)v11.1.0.pdf |
+
+#### 10.7.44 TS 29.328 IP multimedia (IM) subsystem Sh interface; signalling flows and message contents
+
+This technical specification (TS) specifies the interactions between the HSS (home subscriber server) and the SIP AS (application server) and between the HSS and the OSA SCS (service capability server). This interface is referred to as the Sh reference point.
+
+The IP multimedia (IM) core network subsystem Stage 2 is specified in 3G TS 23.228 and the signalling flows for the IP multimedia call control based on SIP and SDP are specified in 3G TS 24.228.
+
+The IP multimedia (IM) session handling with the IP multimedia (IM) call model is specified in 3G TS 23.218.
+
+This document addresses the signalling flows and message contents for the protocol at the Sh interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 328 | 11.10.0 | Published | 2013-12-19 | http://www.etsi.org/deliver/etsi_ts/129300_129399/129328/11_10_00_60/ts_129328v111000p.pdf |
+| ATIS | ATIS.3GPP.29.328V1170-2014 | 11.7.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.328(R11-11.7.0) | 11.7.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.328(R11-11.7.0) |
+| TTC | TS-3GA-29.328(Rel11)v11.9.0 | 11.9.0 | TTC
Approved | 2013-11-22 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.328(Rel11)v11.9.0.pdf |
+
+#### 10.7.45 TS 29.329 Sh interface based on the Diameter protocol; Protocol details
+
+The document defines a transport protocol for use in the IP multimedia (IM) core network (CN) subsystem based on Diameter.
+
+This document is applicable to:
+
+- the Sh interface between an AS and the HSS;
+- the Sh interface between an SCS and the HSS.
+
+Whenever it is possible, this document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 329 | 11.7.0 | Published | 2013-07-01 | http://www.etsi.org/deliver/etsi_ts/129300_129399/129329/11.07.00_60/ts_129329v110700p.pdf |
+| ATIS | ATIS.3GPP.29.329V1160-2014 | 11.6.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.329(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.329(R11-11.6.0) |
+| TTC | TS-3GA-29.329(Rel11)v11.7.0 | 11.7.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.329(Rel11)v11.7.0.pdf |
+
+#### 10.7.46 TS 29.332 Media gateway control function (MGCF) – IM media gateway; Mn interface
+
+The present document describes the protocol to be used on the media gateway control function (MGCF) – IM media gateway (IM-MGW) interface. The basis for this protocol is the ITU-T H.248.1/MEGACO protocol as specified in ITU-T and IETF. The IMS architecture is described in 3G TS 23.228. The interaction of the MGCF-IM MGW interface signalling procedures in relation to the SIP, and BICC/ISUP signalling at the MGCF are described in 3G TS 29.163.
+
+This specification describes the application of ITU-T H.248.1/MEGACO on the Mn interface. Required extensions use the ITU-T H.248.1/MEGACO standard extension mechanism.
+
+The present document is valid for a 3rd generation PLMN (UMTS) complying with Release 6 and later.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 332 | 11.3.0 | Published | 2013-07-01 | http://www.etsi.org/deliver/etsi_ts/129300_129399/129332/11.03.00_60/ts_129332v110300p.pdf |
+| ATIS | ATIS.3GPP.29.332V1120-2014 | 1.2.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.332(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.332(R11-11.2.0) |
+| TTC | TS-3GA-29.332(Rel11)v11.3.0 | 11.3.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.332(Rel11)v11.3.0.pdf |
+
+#### 10.7.47 TS 29.333 Multimedia resource function controller (MRFC) – Multimedia resource function processor (MRFP) Mp interface; Stage 3
+
+This document describes the protocol to be used on the multimedia resource function controller (MRFC) – multimedia resource function processor (MRFP) interface (Mp interface). The IMS architecture is described in TS 23.228, the functional requirements are described in 3G TS 23.333.
+
+This specification defines a profile of the gateway control protocol [ITU-T H.248.1], for controlling multimedia resource function processor supporting in-band user interaction (UI), conferencing and transcoding for multimedia-services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 333 | 11.3.0 | Published | 2013-07-01 | http://www.etsi.org/deliver/etsi_ts/129300_129399/129333/11_03_00_60/ts_129333v110300p.pdf |
+| ATIS | ATIS.3GPP.29.333V1120-2014 | 11.2.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.333(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.333(R11-11.2.0) |
+| TTC | TS-3GA-29.333(Rel11)v11.3.0 | 11.3.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.333(Rel11)v11_3_0.pdf |
+
+### 10.7.48 TS 29.334 IMS application level gateway (IMS-ALG) – IMS access gateway (IMS-AGW); Iq Interface; Stage 3
+
+This document describes the protocol to be used on the IMS application level gateway (ALG) – IMS access gateway (IMS-AGW) interface. The basis for this protocol is the H.248 protocol as specified in ITU-T. The IMS architecture is described in 3GPP TS 23.228. The underlying reference model and Stage 2 information is described in Annex G of 3GPP TS 23.228 and in 3GPP TS 23.334.
+
+This specification describes the application of H.248 on the Iq interface (see Figure 10.7.48-1). Required extensions use the ITU-T H.248 standard extension mechanism. In addition certain aspects of the base protocol ITU-T H.248 are not needed for this interface and thus excluded by this profile.
+
+
+
+The diagram illustrates the reference model for IMS access. On the left, a 'UE' (User Equipment) is connected to an 'IP-CAN' (IP Connectivity Access Network). The 'IP-CAN' is connected to a 'P-CSCF' (PDN Connectivity Service Function) via a 'Gm' interface, which is marked with an 'X'. The 'P-CSCF' contains an 'IMS-ALG' (IMS Application Level Gateway). The 'IMS-ALG' is connected to an 'IMS access gateway' via an 'Iq' interface. The 'IMS access gateway' contains a 'NAT' (Network Address Translation). The 'IMS access gateway' is connected to the 'IP-CAN' via a 'Media' interface. A dashed box labeled 'Scope of this specification' is positioned around the 'Iq' interface and the 'IMS-ALG'/'IMS access gateway' connection.
+
+Reference model for IMS access diagram showing UE, IP-CAN, P-CSCF (with IMS-ALG), and IMS access gateway (with NAT) connected via Gm, Media, and Iq interfaces.
+
+Q.1743(16)\_F10.7.48-1
+
+Figure 10.7.48-1 – Reference model for IMS access
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 334 | 11.2.0 | Published | 2013-07-01 | http://www.etsi.org/deliver/etsi_ts/129300_129399/129334/11_02_00_60/ts_129334v110200p.pdf |
+| ATIS | ATIS.3GPP.29.334V1110-2014 | 11.1.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.334(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.334(R11-11.1.0) |
+| TTC | TS-3GA-29.334(Rel11)v11.2.0 | 11.2.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.334(Rel11)v11_2_0.pdf |
+
+### 10.7.49 TS 29.335 User data convergence (UDC); User data repository access protocol over the Ud interface; Stage 3
+
+This document specifies the Stage 3 of the Ud interface between the front-ends (FEs) and the user data repository (UDR) in the user data convergence (UDC architecture).
+
+This 3GPP technical specification (TS) specifies the protocol and interactions between the FE and the UDR for Ud reference point, in particular:
+
+- The details of the LDAP protocol that are to be considered
+- The details of the SOAP envelope that provide support for subscriptions to notifications and notifications about data changes service (S/N operations).
+
+The user data convergence Stage 2 description (architecture and information flows) is specified in 3GPP TS 23.335.
+
+Details related to the data model used with LDAP (e.g., directory tree) are left outside the scope of this specification.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 335 | 11.1.0 | Published | 2013-01-30 | http://www.etsi.org/deliver/etsi_ts/129300_129399/129335/11.01.00_60/ts_129335v110100p.pdf |
+| ATIS | ATIS.3GPP.29.335V1110-2014 | 11.1.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.335(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.335(R11-11.1.0) |
+| TTC | TS-3GA-29.335(Re11)v11.1.0 | 11.1.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.335(Re11)v11.1.0.pdf |
+
+### 10.7.50 TS 29.364 IP multimedia subsystem (IMS) application server (AS) service data descriptions for AS interoperability
+
+This specification standardizes the structure and the coding of the service data that are transported over the Sh interface between an Application Server supporting Multimedia Telephony supplementary services as defined in 3GPP TS 22.173 and the HSS. Two optional formats are specified. One is based on a binary coding of the service data and supports the subset of MMTEL services corresponding to PSTN/ISDN and CS supplementary services. The other uses an XML format and supports the full set of MMTEL Services.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 364 | 11.2.0 | Published | 2013-04-09 | http://www.etsi.org/deliver/etsi_ts/129300_129399/129364/11.02.00_60/ts_129364v110200p.pdf |
+| ATIS | ATIS.3GPP.29.364V1120-2014 | 11.2.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.364(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.364(R11-11.2.0) |
+| TTC | TS-3GA-29.364(Re11)v11.2.0 | 11.2.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.364(Re11)v11.2.0.pdf |
+
+### 10.7.51 TS 29.368 Tsp interface protocol between the MTC interworking function (MTC-IWF) and service capability server (SCS)
+
+The document provides the Stage 3 specification of the Tsp reference point for the present release. The functional requirements and the Stage 2 specifications of the Tsp reference point are contained in 3GPP TS 23.682. The Tsp reference point lies between the service capability server (SCS) and the machine type communication inter working function (MTC-IWF).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 368 | 11.4.0 | Published | 2013-09-25 | http://www.etsi.org/deliver/etsi_ts/129300_129399/129368/11.04.00_60/ts_129368v110400p.pdf |
+| ATIS | ATIS.3GPP.29.368V1120-2014 | 11.2.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.368(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.368(R11-11.2.0) |
+| TTC | TS-3GA-29.368(Rel11)v11.4.0 | 11.4.0 | TTC Approved | 2013-11-22 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.368(Rel11)v11.4.0.pdf |
+
+### 10.7.52 TS 29.414 Core network Nb data transport and transport signalling
+
+The document specifies the bearer data transport and bearer control protocols used between MGWs within the CS core network across the Nb Interface. This document assumes the implementation of the split of the call control and the bearer transport and control, as specified in TS 22.173 TS 23.205; see Figure 10.7.52-1. The user plane protocol that uses this bearer data transport (Nb UP) is described in TS 29.415. Note that the document does not preclude an implementation of a combined MSC server and MGW.
+
+
+
+Figure 10.7.52-1 – CS core network logical architecture diagram. The diagram shows the logical architecture of a CS core network. On the left, UTRAN \ GERAN Iu mode and GERAN A/Gb mode are connected to an MGW. The MGW is connected to a central green-shaded area containing two MGWs, an MSC server, and a GMSC server. The MGW on the left is connected to the MSC server via an A interface. The MGW on the right is connected to the GMSC server via an A interface. The MGW on the left is also connected to the MGW on the right via an Nb interface. The MGW on the left is connected to the MSC server via an Mc interface. The MGW on the right is connected to the GMSC server via an Mc interface. The MGW on the left is connected to the GMSC server via an Nc interface. The MGW on the right is connected to the PSTN/ Legacy/External via an Nb interface. The legend indicates that dashed lines represent Signalling Interfaces and solid lines represent Signalling and Data Transfer Interfaces.
+
+Figure 10.7.52-1 – CS core network logical architecture
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 414 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/129400_129499/129414/11.00.00_60/ts_129414v110000p.pdf |
+| ATIS | ATIS.3GPP.29.414V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.414(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.414(R11-11.0.0) |
+| TTC | TS-3GA-29.414(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.414(Rel11)v11.0.0.pdf |
+
+### 10.7.53 TS 29.415 Core network Nb user plane protocols
+
+The document specifies the user plane protocol of the bearer used between two MGWs within the CS core network, called the Nb UP protocol. This document assumes the implementation of the split between call control and the bearer transport and control, as specified in TS 23.205. Note that the document does not preclude an implementation of a combined MSC server and MGW.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 415 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/129400_129499/129415/11.00.00/60/ts_129415v110000p.pdf |
+| ATIS | ATIS.3GPP.29.415V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.415(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-29.415(R11-11.0.0) |
+| TTC | TS-3GA-29.415(Re11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.415(Re11)v11.0.0.pdf |
+
+### 10.7.54 TS 29.658 SIP transfer of IP multimedia service tariff information; Protocol specification
+
+The present document specifies the Stage 3 of the real-time transfer of tariff information between a charge determination point (CDP) and a charge generation point (CGP) by means of the session initiation protocol (SIP).
+
+It identifies the protocol procedures and switching functions needed to support the transfer of tariff information related to IP multimedia services. The information needed to support the ISDN user part (ISUP) signalling aspects of charging ([ETSI ES 201 296]) for advice of charge information purposes is also specified, however, it can be used for other purposes as well where applicable.
+
+The present document is applicable to an environment where different operators are working together. It is also applicable to a single network operator environment.
+
+Whether the present document is applicable to a national environment and/or can be used for inter-network purposes depends on regulatory demands and/or bilateral agreements. It should be noted that there are network requirements and signalling limitations that are not covered because they are outside the scope of the present document. Examples of these are as follows:
+
+- the on-line provided advice of charge information may not accurately reflect the correct charging rate due to discount rates, special charging arrangements, etc. It is out of scope to ensure alignment of this information;
+- complaint handling between network operators in case of incorrect advice of charge information;
+- explicit encryption or special security mechanisms;
+- usage of the transferred tariff information for charging purposes;
+- interaction between UE and CGP for possible confirmation of provided tariffs;
+- any function behind the CGP towards the UE.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 129 658 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/129600_129699/129658/11.00.00_60/ts_129658v110000p.pdf |
+| ATIS | ATIS.3GPP.29.658V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.658(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.658(R11-11.0.0) |
+| TTC | TS-3GA-29.658(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-29.658(Rel11)v11.0.0.pdf |
+
+### 10.7.55 TR 29.909 Diameter-based protocols usage and recommendations in 3GPP
+
+This document contains a common set of principles, rules and recommendations across 3GPP WGs to ensure Diameter-based interfaces have the same treatment for release control and generating new applications-id. Also to address in a unified manner the use/re-use of AVPs, and other Diameter BASE [IETF RFC 3588] related decisions.
+
+The present document covers all aspects of Diameter usage within 3GPP, including description of the current situation of Diameter usage in different 3GPP WGs (CT3, CT4, SA5) in Release 6/7, describe recommendations and conditions to re-use existing Diameter applications (3GPP or IETF application-id), commands, AVPs and/or AVP values, describe recommendations and conditions to define new Diameter applications, commands, AVPs and/or AVP values, and any other related issues, e.g., the cross-release issue, whether to apply proposed guideline back to existing Diameter applications or not, or only new SAE Diameter interfaces, etc.
+
+To achieve maximum benefit from this work it is strongly recommended that all 3GPP Diameter-based protocols follow the recommendations in the present document.
+
+The present document also serves a placeholder for Diameter inter-operator considerations with brief guidelines on how to deploy & realize the inter-operator Diameter-based roaming infrastructure.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TR 129 909 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_tr/129900_129999/129909/11.00.00_60/tr_129909v110000p.pdf |
+| ATIS | ATIS.3GPP.29.909V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.909(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-29.909(R11-11.0.0) |
+| TTC | TR-3GA-29.909(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TR/TR-3GA-29.909(Rel11)v11.0.0.pdf |
+
+### 10.7.56 TR 29.994 Recommended infrastructure measures to overcome specific mobile station (MS) faults
+
+The document clarifies recommended measures which may be adopted by 3GPP infrastructure utilizing GSM or GERAN as access network to enable interworking to be obtained between network and various user equipment (UE) implementations of the 3GPP specification. The objective is to obtain compatibility without changing the consolidated set of specifications. The
+
+present document describes the recommended changes to the infrastructure to cater for specific faults within some types of UE.
+
+The lifetime of the herein-described measures together with their potential impact on optimal network performance is out of the scope of the document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TR 129 994 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_tr/129900_129999/129994/11.00.00_60/tr_129994v110000p.pdf |
+| ATIS | ATIS.3GPP.29.994V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-29.994(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-29.994(R11-11.0.0) |
+| TTC | TR-3GA-29.994(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TR/TR-3GA-29.994(Rel11)v11.0.0.pdf |
+
+## 10.8 31-series, Subscriber identity module (SIM / USIM), IC cards. Test specifications
+
+### 10.8.1 TS 31.101 UICC-terminal interface; Physical and logical characteristics
+
+The document specifies the interface between the UICC and the terminal for 3G-telecom network operation.
+
+The document specifies:
+
+- the requirements for the physical characteristics of the UICC;
+- the electrical interface between the UICC and the terminal;
+- the initial communication establishment and the transport protocols;
+- the model which serves as a basis for the logical structure of the UICC;
+- the communication commands and the procedures;
+- the application independent files and protocols.
+
+The administrative procedures and initial card management are not part of the document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.101 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/31/A31101-b00.pdf |
+| ETSI | TS 131 101 | 11.0.0 | Published | 2012-11-13 | http://www.etsi.org/deliver/etsi_ts/131100_131199/131101/11.00.00_60/ts_131101v110000p.pdf |
+| ATIS | ATIS.3GPP.31.101V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-31.101(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-31.101(R11-11.0.0) |
+
+### 10.8.2 TS 31.102 Characteristics of the USIM application
+
+The document defines the USIM application for 3G-telecom network operation.
+
+The document specifies:
+
+- specific command parameters;
+- file structures;
+- contents of EFs (elementary files);
+- security functions;
+- application protocol to be used on the interface between UICC (USIM) and ME.
+
+This is to ensure interoperability between a USIM and an ME independently of the respective manufacturer, card issuer or operator.
+
+The document does not define any aspects related to the administrative management phase of the USIM. Any internal technical realization of either the USIM or the ME is only specified where these are reflected over the interface. The document does not specify any of the security algorithms that may be used.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.102 | 11.6.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/31/A31102-b60.pdf |
+| ETSI | TS 131 102 | 11.6.0 | Published | 2013-10-02 | http://www.etsi.org/deliver/etsi_ts/131100_131199/131102/11.06.00_60/ts_131102v110600p.pdf |
+| ATIS | ATIS.3GPP.31.102V 1140-2014 | 11.4.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-31.102(R11-11.4.0) | 11.4.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-31.102(R11-11.4.0) |
+
+### 10.8.3 TS 31.103 Characteristics of the IP multimedia services identity module (ISIM) application
+
+This document defines the ISIM application for access to IMS services.
+
+This document specifies:
+
+- specific command parameters;
+- file structures;
+- contents of EFs (elementary files);
+- security functions;
+- application protocol to be used on the interface between UICC (ISIM) and terminal.
+
+This is to ensure interoperability between an ISIM and terminal independently of the respective manufacturer, card issuer or operator.
+
+This document does not define any aspects related to the administrative management phase of the ISIM. Any internal technical realization of either the ISIM or the terminal is only specified where these are reflected over the interface. This document does not specify any of the security algorithms that may be used.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.103 | 11.1.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/31/A31103-b10.pdf |
+| ETSI | TS 131 103 | 11.2.0 | Published | 2014-03-25 | http://www.etsi.org/deliver/etsi_ts/131100_131199/131103/11.02.00_60/ts_131103v110200p.pdf |
+| ATIS | ATIS.3GPP.31.103V1110-2014 | 11.1.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-31.103(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-31.103(R11-11.1.0) |
+
+#### 10.8.4 TS 31.111 USIM application toolkit (USAT)
+
+The document defines the interface between the universal ICC (UICC) and the mobile equipment (ME), and mandatory ME procedures, specifically for "USIM application toolkit".
+
+USAT is a set of commands and procedures for use during the network operation phase of 3G, in addition to those defined in TS 31.101.
+
+Specifying the interface is to ensure interoperability between a UICC and an ME independently of the respective manufacturers and operators.
+
+The document defines:
+
+- the commands;
+- the application protocol;
+- the mandatory requirements on the UICC and ME for each procedure.
+
+This document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the UICC or the ME is only specified where these reflect over the interface. The document does not specify any of the security algorithms that may be used.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.111 | 11.7.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/31/A31111-b70.pdf |
+| ETSI | TS 131 111 | 11.8.0 | Published | 2014-04-02 | http://www.etsi.org/deliver/etsi_ts/131100_131199/131111/11.08.00_60/ts_131111v110800p.pdf |
+| ATIS | ATIS.3GPP.31.111V1150-2014 | 11.5.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-31.111(R11-11.5.0) | 11.5.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-31.111(R11-11.5.0) |
+
+#### 10.8.5 TS 31.115 Secured packet structure for (U)SIM toolkit applications
+
+This document specifies the structure of the secured packets in implementations using short message service point-to-point (SMS-PP), short message service cell broadcast (SMS-CB), and unstructured supplementary service data (USSD) based on TS 102 225.
+
+The structure of the secured packets shall comply with the one defined in TS 102 225. The present document only contains additional requirements or explicit limitations for SIM/USIM applications.
+
+It is applicable to the exchange of secured packets between an entity in a 3G or GSM PLMN and an entity in the (U)SIM.
+
+Secured packets contain application messages to which certain mechanisms according to TS 102 224 have been applied. Application messages are commands or data exchanged between an application resident in or behind the 3G or GSM PLMN and on the (U)SIM. The sending/receiving entity in the 3G or GSM PLMN and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into secured packets.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.115 | 11.0.1 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/31/A31115-b01.pdf |
+| ETSI | TS 131 115 | 11.0.1 | Published | 2013-08-06 | http://www.etsi.org/deliver/etsi_ts/131100_131199/131115/11.00.01_60/ts_131115v110001p.pdf |
+| ATIS | ATIS.3GPP.31.115V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-31.115(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-31.115(R11-11.0.0) |
+
+#### 10.8.6 TS 31.116 Remote APDU structure for (U)SIM toolkit applications
+
+The present document defines the remote management of files and applets on the SIM/USIM.
+
+It describes the APDU format for remote management.
+
+Furthermore, the document specifies:
+
+- a set of commands coded according to this APDU structure and used in the remote file management on the SIM/USIM specified in 3G TS 51.011, 3G TS 31.101 and 3G TS 31.102;
+- a set of commands coded according to this APDU structure and used in the remote applet management on the SIM/USIM. This is based on TS 102 226.
+
+The remote APDU structure for SIM/USIM applications shall comply with the one defined in TS 102 226. The present document only contains additional requirements or explicit limitations for SIM/USIM applications.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.116 | 11.1.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/31/A31116-b10.pdf |
+| ETSI | TS 131 116 | 11.1.0 | Published | 2013-07-16 | http://www.etsi.org/deliver/etsi_ts/131100_131199/131116/11.01.00_60/ts_131116v110100p.pdf |
+| ATIS | ATIS.3GPP.31.116V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-31.116(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-31.116(R11-11.0.0) |
+
+### 10.8.7 TS 31.120 UICC-Terminal interface; Physical, electrical and logical test specification
+
+The document specifies the interface test for the Terminal/UICC.
+
+The document specifies the tests of:
+
+- physical characteristics of the UICC;
+- the electrical interface between the UICC and the Terminal;
+- the initial communication establishment and the transport protocols;
+- the application independent procedures.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.120 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/31/A31120-b00.pdf |
+| ETSI | TS 131 120 | 11.0.0 | Published | 2012-11-13 | http://www.etsi.org/deliver/etsi_ts/131100_131199/131120/11.00.00_60/ts_131120v110000p.pdf |
+
+### 10.8.8 TS 31.121 UICC-terminal interface; Universal subscriber identity module (USIM) application test specification
+
+The document provides the UICC –Terminal interface conformance test specification between a 2G, 3G or 3G E-UTRAN terminal and the USIM (universal subscriber identity module) as an application on the UICC and the Terminal for a 2G, 3G or 3G E-UTRAN network operation:
+
+- the default setting of the USIM;
+- the applicability of each test case;
+- the test configurations;
+- the conformance requirement and reference to the core specifications;
+- the test purposes; and
+- a brief description of the test procedure and the specific acceptance criteria.
+
+For the avoidance of doubt, references to clauses of ETSI TS 102 221 include all the subclauses of that clause, unless specifically mentioned.
+
+ETSI TS 102 221 contains material that is outside of the scope of 3GPP requirements. A 3GPP ME may support functionality that is not required by 3GPP, but the requirements to do so are outside of the scope of 3GPP. Thus the present document does not contain tests for features defined in ETSI TS 102 221 which are out of the scope of 3GPP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.121 | 11.3.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/31/A31121-b30.pdf |
+| ETSI | TS 131 121 | 11.4.0 | Published | 2014-04-02 | http://www.etsi.org/deliver/etsi_ts/131100_131199/131121/11.04.00_60/ts_131121v110400p.pdf |
+
+### **10.8.9 TS 31.122 Universal subscriber identity module (USIM) conformance test specification**
+
+The document provides the conformance test specification for a universal IC card (UICC) defined in TS 31.101 with universal subscriber identity module (USIM) defined in TS 31.102.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|----------------|----------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.122 | 11.1.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/31/A31122-b10.pdf |
+| ETSI | TS 131 122 | 11.1.0 | Published | 2013-07-16 | http://www.etsi.org/deliver/etsi_ts/131100_131199/131122/11.01.00_60/ts_131122v110100p.pdf |
+
+### **10.8.10 TS 31.124 Mobile equipment (ME) conformance test specification; Universal subscriber identity module application toolkit (USAT) conformance test specification**
+
+The present document describes the technical characteristics and methods of test for testing the USIM application toolkit implemented in third generation mobile equipments (ME) or mobile station (MS) for the 3G and 2G digital cellular communications systems within the 3GPP digital cellular telecommunications system, in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 and ETSI ETS 300 406.
+
+The present document is valid for ME implemented according to 3GPP Release 99, or Release 4, or Release 5, or Release 6, or Release 7 or Release 8.
+
+The present document covers the minimum characteristics considered necessary in order to provide sufficient performance for mobile equipment and to prevent interference to other services or to other users, and to the PLMNs.
+
+It does not necessarily include all the characteristics which may be required by a user or subscriber, nor does it necessarily represent the optimum performance achievable.
+
+The document is part of the 3GPP-series of technical specifications. The present document neither replaces any of the other 3GPP technical specifications or 3GPP related ETSs or ENs, nor is it created to provide full understanding of (or parts of) the UMTS. The present document lists the requirements, and provides the methods of test for testing the USIM Application Toolkit implemented in a ME for conformance to the 3GPP standard.
+
+For a full description of the system, reference should be made to all the 3GPP technical specifications or 3GPP related ETSIs, ETSs or ENs. Clause 2 provides a complete list of the 3GPP technical specifications, 3GPP related ETSIs' ETSs, ENs, and ETRs, on which this conformance test specifications is based.
+
+If there is a difference between this present conformance document, and any other 3GPP technical specification or 3GPP related ETSI, ETS, EN, or 3GPP TS, then the other 3GPP technical specification or 3GPP related ETSI ETS, EN or 3GPP TS shall prevail.
+
+Within the context of this document, the term "terminal" used in ETSI TS 102 384 refers to the Mobile Equipment (ME).
+
+Within the context of this document, the term "UICC" used in ETSI TS 102 384 refers to the USIM card.
+
+Within the context of this document, the term "NAA" used in ETSI TS 102 384 refers to the USIM application.
+
+For the avoidance of doubt, references to clauses of ETSI TS 102 384 or ETSI TS 102 221 include all the subclauses of that clause, unless specifically mentioned.
+
+The target test specification ETSI TS 102 384 contains material that is outside of the scope of 3GPP requirements and the present document indicates which parts are in the scope and which are not.
+
+A 3GPP ME may support functionality that is not required by 3GPP, but the requirements to do so are outside of the scope of 3GPP. Thus the present document does not contain tests or references to ETSI TS 102 384 tests for features which are out of scope of 3GPP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.124 | 11.5.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/31/A31124-b50.pdf |
+| ETSI | TS 131 124 | 11.6.0 | Published | 2014-04-02 | http://www.etsi.org/deliver/etsi_ts/131100_131199/131124/11.06.00_60/ts_131124v110600p.pdf |
+
+#### 10.8.11 TS 31.130 (U)SIM application programming interface; (U)SIM API for Java card
+
+The present document defines the (U)SIM application programming interface extending the "UICC API for Java card™".
+
+This API allows to develop a (U)SAT application running together with a (U)SIM application and using GSM/3G network features.
+
+The present document includes information applicable to network operators, service providers, server manufacturers, SIM manufacturers, USIM manufacturers, and database manufacturers.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.130 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/31/A31130-b00.pdf |
+| ETSI | TS 131 130 | 11.0.0 | Published | 2013-04-26 | http://www.etsi.org/deliver/etsi_ts/131100_131199/131130/11.00.00_60/ts_131130v110000p.pdf |
+| ATIS | ATIS.3GPP.31.130V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-31.130(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-31.130(R11-11.0.0) |
+
+#### 10.8.12 TS 31.131 C-language binding to (U)SIM API
+
+A subscriber identity module application programming interface (SIM API) has been defined in 3G TS 42.019 as a technology-independent API by which toolkit applications and (U)SIMs cooperate. That specification is independent of the programming language technology used to create the application, the platform used to host the application and the runtime environment used to execute the application.
+
+The present document includes information applicable to (U)SIM toolkit application developers creating applications using the C programming language ISO/IEC 9899. The present document describes an interface between toolkit applications written in the C programming language and the (U)SIM in order to realize the cooperation set forth in 3G TS 42.019. In particular, the API described herein provides the service of assembling proactive commands and disassembling the responses to these commands for the application programmer.
+
+Software tools, integrated software development environments and software management systems that may be used to create application programs are explicitly out of scope of the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.131 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/31/A31131-b00.pdf |
+| ETSI | TS 131 131 | 11.0.0 | Published | 2012-11-13 | http://www.etsi.org/deliver/etsi_ts/131100_131199/131131/11.00.00_60/ts_131131v110000p.pdf |
+| ATIS | ATIS.3GPP.31.131V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-31.131(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-31.131(R11-11.0.0) |
+
+### 10.8.13 TS 31.133 IP multimedia services identity module (ISIM) application programming interface (API); ISIM API for Java card™
+
+This document defines the ISIM application programming interface extending the "UICC API for Java card™" [142 201 ST ISTE].
+
+This API allows to develop an application running together with an ISIM application.
+
+The document includes information applicable to network operators, service providers, and manufacturers of ISIM server equipment and database.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.133 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/31/A31133-b00.pdf |
+| ETSI | TS 131 133 | 11.0.0 | Published | 2012-11-13 | http://www.etsi.org/deliver/etsi_ts/131100_131199/131133/11.00.00_60/ts_131133v110000p.pdf |
+| ATIS | ATIS.3GPP.31.133V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-31.133(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-31.133(R11-11.0.0) |
+
+### 10.8.14 TS 31.213 Test specification for (U)SIM; Application programming interface (API) for Java card™
+
+The document covers the minimum characteristics considered necessary in order to provide compliance to TS 31.130.
+
+The document describes the technical characteristics and methods of test for testing the (U)SIM API for Java card™ (TS 31.130) implemented in the (U)SIM. It specifies the following parts:
+
+- test applicability;
+- test environment description;
+- test format;
+- test area reference;
+- conformance requirements;
+- test suite files;
+- test procedure;
+
+- test coverage; and
+- a description of the associated testing tools that shall be used.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.213 | 11.2.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/31/A31213-b20.pdf |
+| ETSI | TS 131 213 | 11.2.0 | Published | 2013-10-02 | http://www.etsi.org/deliver/etsi_ts/131200_131299/131213/11.02.00_60/ts_131213v110200p.pdf |
+
+#### 10.8.15 TS 31.220 Characteristics of the contact manager for 3GPP UICC applications
+
+This document defines the contact manager for 3GPP UICC applications.
+
+The document specifies the external interface between the contact manager server in the UICC and the contact manager external client in the ME;
+
+Any internal technical realization of either the contact manager server or clients is only specified where these are reflected over the interfaces.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.220 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/31/A31220-b00.pdf |
+| ETSI | TS 131 220 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/131200_131299/131220/11.00.00_60/ts_131220v110000p.pdf |
+| ATIS | ATIS.3GPP.31.220V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-31.220(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-31.220(R11-11.0.0) |
+
+#### 10.8.16 TS 31.221 Contact manager application programming interface (API); Contact manager API for Java card™
+
+This document defines the internal interface characteristics of the contact manager for 3GPP UICC applications (see TS 31.220).
+
+The internal interface between the contact manager server application on the UICC and the contact manager client application on the UICC enables Java card™ platform based applet, to invoke and register to the contact manager server services. In particular, the contact manager Java card™ based API provides methods to:
+
+- Read/Update/Create/Delete contact(s) in the contact manager server;
+- Manage group of contacts in the contact manager server;
+- Search for a contact in the contact manager server storage;
+- manage the contacts structure;
+- Register/Un-register the application to pre-defined events (e.g., application to be notified when contacts are modified in the contact manager server).
+
+This API allows to develop an application running together with a contact manager (see TS 31.220).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-31.221 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/31/A31221-b00.pdf |
+| ETSI | TS 131 221 | 11.0.0 | Published | 2012-11-13 | http://www.etsi.org/deliver/etsi_ts/131200_131299/131221/11.00.00_60/ts_131221v110000p.pdf |
+| ATIS | ATIS.3GPP.31.221V1100-2014 | 11.0.0 | Approved | 2014-05-09 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-31.221(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-31.221(R11-11.0.0) |
+
+### 10.8.17 TR 31.900 SIM/USIM internal and external interworking aspects
+
+This document describes:
+
+- the different cases of interworking between a 2G or 3G ICC and a 2G or 3G ME;
+- the different cases of interworking between any given ME/ICC combination and the rest of the network;
+- the possibilities of interworking between a SIM and a USIM together on a single UICC;
+- the possibilities of interworking between several USIMs on a single UICC.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-31.900 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/31/A31900-b00.pdf |
+| ETSI | TR 131 900 | 11.0.0 | Published | 2012-11-13 | http://www.etsi.org/deliver/etsi_tr/131900_131999/131900/11.00.00_60/tr_131900v110000p.pdf |
+| ATIS | ATIS.3GPP.31.900V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-31.900(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-31.900(R11-11.0.0) |
+
+## 10.9 32-series, OAM&P and Charging
+
+### 10.9.1 TS 32.101 3G Telecommunication management; Principles and high-level requirements
+
+The document establishes and defines the management principles and high-level requirements for the management of UMTS.
+
+In particular, this document identifies the requirements for:
+
+- the upper level of a UMTS management system;
+- the reference model, showing the elements the UMTS management system interacts with;
+- the network operator processes needed to run, operate and maintain a UMTS network;
+- the functional architecture of the UMTS management system;
+- the principles to be applied to UMTS management interfaces.
+
+The requirements identified in this document are directed to the further development of UMTS management specifications, as well as the development of UMTS management products. This document can be seen as guidance for the development of all other technical specifications addressing the management of UMTS.
+
+This document does not provide physical architectures of the UMTS management system. These aspects are defined and discussed in more detail in TS 32.102.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 101 | 11.1.0 | Published | 2013-01-31 | http://www.etsi.org/deliver/etsi_ts/132100_132199/132101/11_01_00_60/ts_132101v110100p.pdf |
+| ATIS | ATIS.3GPP.32.101V1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.101(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.101(R11-11.1.0) |
+| TTC | TS-3GA-32.101(Rel11)v11.1.0 | 11.1.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.101(Rel11)v11.1.0.pdf |
+
+### 10.9.2 TS 32.102 3G Telecommunication management; Architecture
+
+The document identifies and standardizes the most important and strategic contexts in the physical architecture for the management of UMTS. It serves as a framework to help define a telecom management physical architecture for a planned UMTS and to adopt standards and provide products that are easy to integrate.
+
+The requirements identified in this document are applicable to all further development of UMTS telecom management specifications as well as the development of UMTS management products. This document can be seen as guidance for the development of all other technical specifications addressing the management of UMTS, except TS 32.101.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 102 | 11.2.0 | Published | 2013-10-04 | http://www.etsi.org/deliver/etsi_ts/132100_132199/132102/11_02_00_60/ts_132102v110200p.pdf |
+| ATIS | ATIS.3GPP.32.102V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.102(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.102(R11-11.0.0) |
+| TTC | TS-3GA-32.102(Rel11)v11.2.0 | 11.2.0 | TTC Approved | 2013-11-22 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.102(Rel11)v11.2.0.pdf |
+
+### 10.9.3 TS 32.103 Telecommunication management; Integration reference point (IRP) overview and usage guide
+
+This document gives an overview about 3GPP's management interface capabilities and related functionality.
+
+It provides high-level information about IRP Framework, available IRP's as well as their relationship with each other. This document is intended to be a guide into the world of 3GPP management specifications, enabling also non-subject matter experts to gain an understanding about 3GPP's management solutions.
+
+In addition Annex A provides IRP packaging suggestions, intended to guide service providers as well as equipment and solutions providers to identify and choose suitable standardized management interface capabilities.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 103 | 11.3.0 | Published | 2013-10-04 | http://www.etsi.org/deliver/etsi_ts/132100_132199/132103/11.03.00_60/ts_132103v110300p.pdf |
+| ATIS | ATIS.3GPP.32.103V1120-2014 | 11.2.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.103(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.103(R11-11.2.0) |
+| TTC | TS-3GA-32.103(Rel11)v11.3.0 | 11.3.0 | TTC Approved | 2013-11-22 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.103(Rel11)v11.3.0.pdf |
+
+#### 10.9.4 TS 32.111-1 Telecommunication management; Fault management; Part 1: 3G fault management requirements
+
+The document specifies the overall requirements for 3G fault management (FM) as it applies to the network elements (NE), element manager (EM) and network manager (NM).
+
+This document defines the FM concept and functional requirements for the detection of faults and the generation, collection and presentation of alarms, operational state data and test results across 3G systems. These functions are described on a non-formal level since the formal standardization of these functions across the different vendors' equipment is not required. The functional areas specified in this document cover:
+
+- fault surveillance and detection in the NEs;
+- notification of alarms (including alarm cease) and operational state changes;
+- retrieval of current alarms from the NEs;
+- fault isolation and defence mechanisms in the NEs;
+- alarm filtering;
+- management of alarm severity levels;
+- alarm and operational state data presentation and analysis at the operations system (OS);
+- retention of alarm and operational state data in the NEs and the OS; and
+- the management of tests.
+
+Any (re)configuration activity exerted from the EM as a consequence of faults will not be subject of this document; these are described in the TS 32.600-series.
+
+This document defines the functional requirements for the standard interface N (Itf-N), for the purpose of fault management of 3G networks, as seen from the network manager (NM). The Itf-N is fully standardized so as to connect systems of any vendor to the NM via this interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 111-1 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132100_132199/1321101/11.00.00_60/ts_1321101v110000p.pdf |
+| ATIS | ATIS.3GPP.32.111-1V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|-------------------------------|---------|-----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-32.111-1(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.111-1(R11-11.0.0) |
+| TTC | TS-3GA-32.111-1(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.111-1(Rel11)v11.0.0.pdf |
+
+### 10.9.5 TS 32.111-2 Telecommunication management; Fault management; Part 2: Alarm integration reference point: Information service
+
+The document defines the alarm integration reference point (IRP) information service (IS), which addresses the alarm surveillance aspects of fault management (FM), applied to the N interface.
+
+The purpose of the alarm IRP is to define an interface through which a "system" (typically a network element manager or a network element) can communicate alarm information for its managed objects to one or several manager systems (typically network management systems).
+
+The alarm IRP IS defines the semantics of alarms and the interactions visible across the reference point in a protocol-neutral way. It defines the semantics of the operations and notifications visible in the IRP. It does not define the syntax or encoding of the operations, notifications and their parameters.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-------------------------------|---------|-----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 111-2 | 11.1.0 | Published | 2013-01-31 | http://www.etsi.org/deliver/etsi_ts/132100_132199/13211102/11.01.00_60/ts_13211102v110100p.pdf |
+| ATIS | ATIS.3GPP.32.111-2V1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.111-2(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.111-2(R11-11.1.0) |
+| TTC | TS-3GA-32.111-2(Rel11)v11.1.0 | 11.1.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.111-2(Rel11)v11.1.0.pdf |
+
+### 10.9.6 TS 32.111-6 Telecommunication management; Fault management; Part 6: Alarm integration reference point (IRP): Solution set (SS) definitions
+
+This document contains solution sets for IRP whose semantics as specified in Alarm IRP: Information service TS 32.111-2.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 111-6 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/132100_132199/13211106/11.00.00_60/ts_13211106v110000p.pdf |
+| ATIS | ATIS.3GPP.32.111-6V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.111-6(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.111-6(R11-11.0.0) |
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|-------------------------------|---------|-----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTC | TS-3GA-32.111-6(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.111-6(Rel11)v11.0.0.pdf |
+
+### 10.9.7 TS 32.121 Telecommunication management; Advanced alarm management (AAM) integration reference point (IRP): Requirements
+
+The purpose of this set of specifications is to provide a mechanism enabling the IRP Manager to improve the information content of alarms, thereby contributing to reduce the time-to-repair. For this configurable rules for advanced alarm filtering are defined to reduce the number of alarms by applying such advanced alarm filtering.
+
+This document contains the requirements of advanced alarm management (AAM) on Itf-N IRP. It defines, for the purpose of AAM on Itf-N, the basic requirements to be fulfilled on Itf-N.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 121 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132100_132199/132121/11.00.00_60/ts_132121v110000p.pdf |
+| ATIS | ATIS.3GPP.32.121V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.121(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.121(R11-11.0.0) |
+| TTC | TS-3GA-32.121(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.121(Rel11)v11.0.0.pdf |
+
+### 10.9.8 TS 32.122 Telecommunication management; Advanced alarm management (AAM) integration reference point (IRP); Information service (IS)
+
+The purpose of advanced alarm management (AAM) IRP is to define an interface through which an IRPManager can categorize alarm notifications.
+
+This document is the information service of AAM. It defines, for the purpose of categorizing alarm notifications, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 122 | 11.0.0 | Published | 2012-09-26 | http://www.etsi.org/deliver/etsi_ts/132100_132199/132122/11.00.00_60/ts_132122v110000p.pdf |
+| ATIS | ATIS.3GPP.32.122V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.122(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.122(R11-11.0.0) |
+| TTC | TS-3GA-32.122(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.122(Rel11)v11.0.0.pdf |
+
+### **10.9.9 TS 32.126 Telecommunication management; Advanced alarm management (AAM) integration reference point (IRP); Solution set (SS) definitions**
+
+The document specifies Solution Set definitions for IRP whose semantics as specified in the advanced alarm management (AAM) IRP information service in TS 32.122.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|----------------|-----------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 126 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/132100_132199/132126/11.00.00/60/ts_132126v110000p.pdf |
+| ATIS | ATIS.3GPP.32.126V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.126(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.126(R11-11.0.0) |
+| TTC | TS-3GA-32.126(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.126(Rel11)v11.0.0.pdf |
+
+### **10.9.10 TS 32.140 Telecommunication management; Subscription management (SuM) requirements**
+
+This document defines the service requirements and high-level architecture for SuM.
+
+SuM is expected to evolve in stages over several releases of 3GPP specifications.
+
+The document provides additional supporting material, which whilst not within the scope of this release, provides an insight towards the future evolution. This is in order that initial work may be done with an appreciation of the wider context expected in future releases of 3GPP specifications.
+
+SuM for 3GPP is primarily concerned with the ability to define subscription profiles and associate the profile with subscribers, users and services that are authorized by agreements. The subscription profile may be used in the process of configuring various network resources (access and core) to make the service a reality for the user.
+
+The management capabilities extend to the creation, modification, synchronization, and reapplication of subscription profiles.
+
+This document is oriented towards a standardized interface into the home subscriber server (HSS) in order that services can be provisioned and maintained.
+
+The document includes information applicable to network operators, content providers, and terminal and network manufacturers.
+
+The document contains the core requirements for SuM, which are sufficient to provide management services.
+
+The method by which applications subscribe to OSA is not within the scope of the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 140 | 11.1.0 | Published | 2013-07-10 | http://www.etsi.org/deliver/etsi_ts/132100_132199/132140/11.01.00/60/ts_132140v110100p.pdf |
+| ATIS | ATIS.3GPP.32.140V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-32.140(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.140(R11-11.0.0) |
+| TTC | TS-3GA-32.140(Rel11)v11.1.0 | 11.1.0 | TTC
Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.140(Rel11)v11.1.0.pdf |
+
+#### 10.9.11 TS 32.141 Telecommunication management; Subscription management (SuM) architecture
+
+Subscription management (SuM) is a feature that permits service providers, value-added service providers, and mobile operators to provision services for a specific subscriber. The feature is necessary to allow service providers and operators to provision, control, monitor and bill the configuration of services that they offer to their subscribers.
+
+For further details, please refer to 3G TS 32.140 SuM requirements specification that gives an overview of SuM requirements.
+
+The document defines the architecture for subscription management.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 141 | 11.1.0 | Published | 2013-07-10 | http://www.etsi.org/deliver/etsi_ts/132100_132199/132141/11_01_00_60/ts_132141v110100p.pdf |
+| ATIS | ATIS.3GPP.32.141V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.141(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.141(R11-11.0.0) |
+| TTC | TS-3GA-32.141(Rel11)v11.1.0 | 11.1.0 | TTC
Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.141(Rel11)v11.1.0.pdf |
+
+#### 10.9.12 TS 32.150 Telecommunication management; Integration reference point (IRP) concept and definitions
+
+This document provides the overall concept for all integration reference point (IRP) specifications produced by 3GPP. Relevant IRP overview and high-level definitions are already provided in 3G TS 32.101 and 3G TS 32.102.
+
+The document is a member of a TS-family consisting of 3G TS 32.150, 3G TS 32.151, 3G TS 32.152.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 150 | 11.2.0 | Published | 2013-04-17 | http://www.etsi.org/deliver/etsi_ts/132100_132199/132150/11_02_00_60/ts_132150v110200p.pdf |
+| ATIS | ATIS.3GPP.32.150V1120-2014 | 11.2.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.150(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.150(R11-11.2.0) |
+| TTC | TS-3GA-32.150(Rel11)v11.2.0 | 11.2.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.150(Rel11)v11.2.0.pdf |
+
+### **10.9.13 TS 32.151 Telecommunication management; Integration reference point (IRP) information service (IS) template**
+
+This document contains the template to be used for the production of all integration reference point (IRP) information service (IS) specifications within the 3GPP 32-series.
+
+The document is a member of a TS-family consisting of 3G TS 32.150, 3G TS 32.151, 3G TS 32.152.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|----------------|-----------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 151 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132100_132199/132151/11.00.00_60/ts_132151v110000p.pdf |
+| ATIS | ATIS.3GPP.32.151V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.151(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.151(R11-11.0.0) |
+| TTC | TS-3GA-32.151(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.151(Rel11)v11.0.0.pdf |
+
+### **10.9.14 TS 32.152 Telecommunication management; Integration reference point (IRP) information service (IS) unified modelling language (UML) repertoire**
+
+This TS documents the necessary and sufficient set of UML notations and model elements, including the ones built by the UML extension mechanism <>, for use by 3GPP IRP IS authors. Collectively, this set of notations and model elements is called the 3GPP IRP IS modelling repertoire.
+
+The selection of the UML notations and model elements in this repertoire is based on the needs of the existing 3GPP IRP IS specifications. Future IRP IS releases may require the use of additional UML notations or model elements.
+
+IRP IS specifications shall employ the UML notation and model elements of this repertoire and may also employ other UML notation and model elements considered necessary. However, before any other UML notation and model elements may be employed in an approved 3GPP IRP specification, the other notation and model elements should be agreed for inclusion first in this repertoire.
+
+This document is a member of a TS-family consisting of 3G TS 32.150, 3G TS 32.151, 3G TS 32.152.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|----------------|-----------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 152 | 11.1.0 | Published | 2013-01-31 | http://www.etsi.org/deliver/etsi_ts/132100_132199/132152/11.01.00_60/ts_132152v110100p.pdf |
+| ATIS | ATIS.3GPP.32.152V1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.152(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.152(R11-11.1.0) |
+| TTC | TS-3GA-32.152(Rel11)v11.1.0 | 11.1.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.152(Rel11)v11.1.0.pdf |
+
+### 10.9.15 TS 32.153 Telecommunication management; Integration Reference Point (IRP) technology specific templates, rules and guidelines
+
+The present document contains the templates to be used for the production of integration reference point (IRP) technology-specific specifications.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 153 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132100_132199/132153/11.00.00_60/ts_132153v110000p.pdf |
+| ATIS | ATIS.3GPP.32.153V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.153(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.153(R11-11.0.0) |
+| TTC | TS-3GA-32.153(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.153(Rel11)v11.0.0.pdf |
+
+### 10.9.16 TS 32.154 Telecommunication management; Backward and forward compatibility (BFC); Concept and definitions
+
+This document gives recommendations to develop future IRP specifications in a backward compatible (BC) way so that the group of IRPManager(s) and IRPAgent(s) are not forced to be upgraded in lock step.
+
+The business case for supporting such group, as described above, is complex. It may not relate to the functions of the supported IRPs alone. Rather, it can relate to the cost of coordination of IRPVersion upgrades, the cost of maintaining an old IRPVersion and the cost of using single-vendor or multi-vendor IRPAgents. These considerations are operator deployment scenarios specific.
+
+Clause 4 specifies the recommendations and clause 5 describes the system context where the recommendations are applicable.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 154 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132100_132199/132154/11.00.00_60/ts_132154v110000p.pdf |
+| ATIS | ATIS.3GPP.32.154V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.154(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.154(R11-11.0.0) |
+| TTC | TS-3GA-32.154(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.154(Rel11)v11.0.0.pdf |
+
+### 10.9.17 TS 32.155 Telecommunication management; Requirements template
+
+The document contains the template to be used for the production of all requirements TSs for the 3GPP telecommunication management.
+
+This template is mainly based on the requirements template (mainly Annex A) in the [ITU-T M.3020].
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 155 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132100_132199/132155/11.00.00_60/ts_132155v110000p.pdf |
+| ATIS | ATIS.3GPP.32.155V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.155(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.155(R11-11.0.0) |
+| TTC | TS-3GA-32.155(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.155(Rel11)v11.0.0.pdf |
+
+#### 10.9.18 TS 32.171 Subscription management (SuM) network resource model (NRM) integration reference point (IRP): Requirements
+
+The document defines, in addition to the requirements defined in 3G TS 32.101, 3G TS 32.102, 3G TS 32.140, 3G TS 32.141, requirements for the present SuM NRM IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 171 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132100_132199/132171/11.00.00_60/ts_132171v110000p.pdf |
+| ATIS | ATIS.3GPP.32.171V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.171(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.171(R11-11.0.0) |
+| TTC | TS-3GA-32.171(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.171(Rel11)v11.0.0.pdf |
+
+#### 10.9.19 TS 32.172 Telecommunication management; Subscription management (SuM) network resource model (NRM) integration reference point (IRP): Information service (IS)
+
+The interface Itf-N, defined in 3G TS 32.102, is built up by a number of integration reference points (IRPs) and a related name convention, which realize the functional capabilities over this interface. The basic structure of the IRPs is defined in 3G TS 32.101 and 3G TS 32.102.
+
+This document defines the network resources model (NRM) for the SuM IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 172 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132100_132199/132172/11.00.00_60/ts_132172v110000p.pdf |
+| ATIS | ATIS.3GPP.32.172V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.172(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.172(R11-11.0.0) |
+| TTC | TS-3GA-32.172(Rel11)v11.2.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.172(Rel11)v11.0.0.pdf |
+
+### **10.9.20 TS 32.176 Telecommunication management; Subscription management (SuM) Network resource model (NRM) integration reference point (IRP); Solution set (SS) definitions**
+
+This document is part of an integration reference point (IRP) named subscription management (SuM) network resource model (NRM) IRP, through which an IRP Agent can communicate configuration management information to one or several IRP Managers concerning SuM resources. The SuM NRM IRP comprises a set of specifications defining requirements, a protocol neutral information service and one or more solution set(s).
+
+The document specifies the solution sets for the SuM NRM IRP.
+
+This specification is related to TS 32.172.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|----------------|-----------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 176 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132100_132199/132176/11.00.00_60/ts_132176v110000p.pdf |
+| ATIS | ATIS.3GPP.32.176V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.176(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.176(R11-11.0.0) |
+| TTC | TS-3GA-32.176(Re11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.176(Re11)v11.0.0.pdf |
+
+### **10.9.21 TS 32.240 Telecommunication management; Charging management; Charging architecture and principles**
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in the present document, which thus provides an umbrella for other charging management TSs that specify:
+
+- the content of the CDRs per domain/subsystem/service (offline charging);
+- the content of real-time charging events per domain/subsystem/service (online charging);
+- the functionality of online and offline charging for those domains/subsystems/services;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The purposes of the present document are:
+
+- to lay down common principles of charging in the network; and
+- to specify a logical common charging architecture that applies to all 3GPP domains, subsystems and services.
+
+A set of domain/subsystem/service-specific TSs covers the bearer (CS, PS, WLAN domains), subsystem (IMS) and service (MMS, LCS, etc.) levels, respectively, in the 3G TS 32.25x, 32.26x and 32.27x number range. These 3G TSs describe the mapping of the common architecture specified in the present document onto the specific domain/subsystem/service and the scenarios and information for online and offline charging that are specific to the domain/subsystem/service. They are commonly referred to as the "middle tier (charging) TSs".
+
+A set of 3G TSs in the 32.29x range covers common aspects such as CDR parameter and syntax descriptions, online and offline charging applications, and the charging interactions within the network (CDR transfer) as well as between the network and the billing domain (CDR file transfer).
+
+The complete document structure for these 3G TSs is outlined in Figure 10.9.21-1.
+
+
+
+```
+
+graph TD
+ Root[32.240 Charging Architecture and Principles] --> CS[32.250 CS-domain Charging]
+ Root --> PS[32.251 PS-domain Charging]
+ Root --> WLAN[32.252 WLAN Charging]
+ Root --> IM[32.260 IM Subsystem Charging]
+ CS --> MMS[32.270 MMS Charging]
+ PS --> LCS[32.271 LCS Charging]
+ WLAN --> TBD[32.27x tbd.]
+ IM --> CDR_T[32.295 Charging Data Record (CDR) transfer]
+ IM --> OCS[32.296 Online Charging System (OCS) applications and interfaces]
+ IM --> CDR_F[32.297 Charging Data Record (CDR) file format and transfer]
+ IM --> CDR_P[32.298 Charging Data Record (CDR) parameter description]
+ IM --> DIAMETER[32.299 Diameter Charging Application]
+
+```
+
+Figure 10.9.21-1 – Charging documents structure. A hierarchical tree diagram showing the relationship between various 3G charging standards. The root node is '32.240 Charging Architecture and Principles'. It branches into four main categories: '32.250 CS-domain Charging', '32.251 PS-domain Charging', '32.252 WLAN Charging', and '32.260 IM Subsystem Charging'. Below '32.250' and '32.251' are '32.270 MMS Charging', '32.271 LCS Charging', and '32.27x tbd.'. Below '32.252' and '32.260' are '32.295 Charging Data Record (CDR) transfer', '32.296 Online Charging System (OCS) applications and interfaces', '32.297 Charging Data Record (CDR) file format and transfer', '32.298 Charging Data Record (CDR) parameter description', and '32.299 Diameter Charging Application'.
+
+Q.1743(16)\_F10.9.21-1
+
+**Figure 10.9.21-1 – Charging documents structure**
+
+All references, abbreviations, definitions, descriptions, principles and requirements, used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, 3GPP TR 21.905. Those that are common across charging management in GSM/UMTS domains, services or subsystems are provided in the present document (umbrella TS), and are copied into clause 3 of the other TSs depicted in the figure above, for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 240 | 11.6.0 | Published | 2013-04-17 | http://www.etsi.org/deliver/etsi_ts/132200_132299/132240/11.06.00_60/ts_132240v110600p.pdf |
+| ATIS | ATIS.3GPP.32.240 V1160-2014 | 11.6.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.240(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttastdesc.jsp?stdno=TTAT.3G-32.240(R11-11.6.0) |
+| TTC | TS-3GA-32.240(Rel11)v11.6.0 | 11.6.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.240(Rel11)v11.6.0.pdf |
+
+### **10.9.22 TS 32.251 Telecommunication management; Charging management; Packet-switched (PS) domain charging**
+
+This document is part of a series of documents specifying charging functionality and charging management in GSM/UMTS networks.
+
+The document specifies the offline and online charging description for the packet-switched (PS) domain (i.e., GPRS), based on the functional Stage 2 description of GPRS in 3G TS 23.060. This charging description includes the offline and online charging architecture and scenarios specific to the PS domain, as well as the mapping of the common 3GPP charging architecture specified in 3G TS 32.240 onto the PS domain. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in 3G TS 32.240.
+- The parameters, abstract syntax and encoding rules for the CDRs are specified in 3G TS 32.298.
+- A transaction based mechanism for the transfer of CDRs within the network is specified in 3G TS 32.295.
+- The file-based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in 3G TS 32.297.
+- The 3GPP Diameter application that is used for PS domain offline and online charging is specified in 3G TS 32.299.
+
+Note that a CAMEL-based prepaid function and protocol is also specified for the PS domain (3G TS 23.078 and 3G TS 29.078). CAMEL entities and functions are outside the scope of the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|----------------|---------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 251 | 11.9.0 | Published | 2014-03-21 | http://www.etsi.org/deliver/etsi_ts/132200_132299/132251/11.09.00_60/ts_132251v110900p.pdf |
+| ATIS | ATIS.3GPP.32.251V1160-2014 | 11.6.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.251(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stno=TTAT.3G-32.251(R11-11.6.0) |
+| TTC | TS-3GA-32.251(Re11)v11.8.0 | 11.8.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-32.251(Re11)v11.8.0.pdf |
+
+### **10.9.23 TS 32.252 Telecommunication management; Charging management; Wireless local area network (WLAN) charging**
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in TS 32.240, which provides an umbrella for other charging management documents that specify:
+
+- the content of the CDRs per domain and subsystem (offline charging);
+- the content of real-time charging messages per domain/subsystem (online charging);
+- the functionality of online and offline charging for those domains and subsystems;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in TS 32.240.
+
+The document specifies the offline and online charging description for the 3GPP interworked wireless LAN (WLAN), based on the functional stage 2 description of 3GPP WLAN interworking in TS 23.234. This charging description includes the offline and online charging architecture and scenarios specific to the 3GPP interworked WLAN, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 onto the 3GPP interworked WLAN. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in TS 32.240.
+- The parameters, abstract syntax and encoding rules for these CDR types are specified in TS 32.298.
+- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in TS 32.297.
+- The 3GPP Diameter application that is used for WLAN offline and online charging is specified in TS 32.299.
+
+All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905. Those that are common across charging management in GSM/UMTS domains or subsystems are provided in the umbrella document TS 32.240 and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 252 | 11.1.0 | Published | 2013-07-10 | http://www.etsi.org/deliver/etsi_ts/132200_132299/132252/11.01.00_60/ts_132252v110100p.pdf |
+| ATIS | ATIS.3GPP.32.252V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.252(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.252(R11-11.0.0) |
+| TTC | TS-3GA-32.252(Rel11)v11.1.0 | 11.1.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.252(Rel11)v11.1.0.pdf |
+
+#### **10.9.24 TS 32.260 Telecommunication management; Charging management; IP multimedia subsystem (IMS) charging**
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks.
+
+The document specifies the offline and online charging description for the IP multimedia subsystem (IMS), based on the functional descriptions of the IMS in 3G TS 23.228. This charging description includes the offline and online charging architecture and scenarios specific to IMS, as well as the mapping of common 3GPP charging architecture specified in 3G TS 32.240 onto IMS. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. This document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in 3G TS 32.240.
+- The parameters, abstract syntax and encoding rules for these CDR types are specified in 3G TS 32.298.
+
+- A transaction-based mechanism for the transfer of CDRs within the network is specified in 3G TS 32.295.
+- The file-based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in 3G TS 32.297.
+- The 3GPP Diameter application that is used for IMS offline and online charging is specified in 3G TS 32.299.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 260 | 11.11.0 | Published | 2014-03-21 | http://www.etsi.org/deliver/etsi_ts/132200_132299/132260/11.11.00_60/ts_132260v111100p.pdf |
+| ATIS | ATIS.3GPP.32.260V1170-2014 | 11.7.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.260(R11-11.7.0) | 11.7.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.260(R11-11.7.0) |
+| TTC | TS-3GA-32.260(Rel11)v11.10.0 | 11.10.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-32.260(Rel11)v11.10.0.pdf |
+
+### 10.9.25 TS 32.270 Telecommunication management; Charging management; Multimedia messaging service (MMS) charging
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks.
+
+The complete document structure for these TSs is defined in 3G TS 32.240.
+
+This document specifies the offline and online charging description for MMS charging, based on the functional Stage 2 descriptions of the MMS in 3G TS 23.140. This charging description includes the offline and online charging architecture and scenarios specific to the MMS, as well as the mapping of the common 3GPP charging architecture specified in 3G TS 32.240 onto MMS. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in 3G TS 32.240.
+- The parameters, abstract syntax and encoding rules for these CDR types are specified in 3G TS 32.298.
+- A transaction-based mechanism for the transfer of CDRs within the network is specified in 3G TS 32.295.
+- The file-based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in 3G TS 32.297.
+- The 3GPP Diameter application that is used for MMS online charging is specified in 3G TS 32.299.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 270 | 11.0.0 | Published | 2012-09-28 | http://www.etsi.org/deliver/etsi_ts/132200_132299/132270/11.00.00_60/ts_132270v110000p.pdf |
+| ATIS | ATIS.3GPP.32.270V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-32.270(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.270(R11-11.0.0) |
+| TTC | TS-3GA-32.270(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.270(Rel11)v11.0.0.pdf |
+
+### 10.9.26 TS 32.271 Telecommunication management; Charging management; Location services (LCS) charging
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks.
+
+The document specifies the LCS offline and online charging description for the LCS domain, based on the functional Stage 2 description of the LCS in 3G TS 23.071. This charging description includes the offline and online charging architecture and scenarios specific to the LCS, as well as the mapping of the common 3GPP architecture specified in 3G TS 32.240 onto the LCS domain. It further specifies the structure and content of the CDRs for offline charging and the charging events for online charging.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 271 | 11.1.1 | Published | 2013-04-17 | http://www.etsi.org/deliver/etsi_ts/132200_132299/132271/11_01_01_60/ts_132271v110101p.pdf |
+| ATIS | ATIS.3GPP.32.271V1111-2014 | 11.1.1 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.271(R11-11.1.1) | 11.1.1 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.271(R11-11.1.1) |
+| TTC | TS-3GA-32.271(Rel11)v11.1.1 | 11.1.1 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.271(Rel11)v11.1.1.pdf |
+
+### 10.9.27 TS 32.272 Telecommunication management; Charging management; Push-to-talk over cellular (PoC) charging
+
+The document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in TS 32.240, which provides an umbrella for other charging management TSs that specify:
+
+- the content of the CDRs per domain and subsystem (offline charging);
+- the content of real-time charging messages per domain/subsystem (online charging);
+- the functionality of online and offline charging for those domains and subsystems;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in TS 32.240.
+
+This document specifies the offline and online charging description for the "Push-to-Talk over Cellular" (PoC) service, based on the functional description of the PoC service in TR 23.979 "3GPP enablers for OMA PoC Services", in OMA-AD-POC "Push to talk over Cellular (PoC) – Architecture", in OMA-CP-POC "OMA PoC Control Plane" and in OMA-UP-POC: "OMA POC User Plane", respectively. This charging description includes the offline and online charging architecture and scenarios specific to PoC, as well as the mapping of the common 3GPP charging
+
+architecture specified in TS 32.240 onto the PoC service. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in TS 32.240.
+- The parameters, abstract syntax and encoding rules for these CDR types are specified in TS 32.298.
+- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in TS 32.297.
+- The 3GPP Diameter application that is used for WLAN offline and online charging is specified in TS 32.299.
+
+All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905. Those that are common across charging management in GSM/UMTS domains or subsystems are provided in the umbrella document TS 32.240 and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 272 | 11.1.0 | Published | 2014-01-15 | http://www.etsi.org/deliver/etsi_ts/132200_132299/132272/11_01_00_60/ts_132272v110100p.pdf |
+| ATIS | ATIS.3GPP.32.272V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.272(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.272(R11-11.0.0) |
+| TTC | TS-3GA-32.272(Re11)v11.1.0 | 11.1.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-32.272(Re11)v11.1.0.pdf |
+
+### 10.9.28 TS 32.273 Telecommunication management; Charging management; Multimedia broadcast and multicast service (MBMS) charging
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in TS 32.240, which provides an umbrella for other charging management TSs that specify:
+
+- the content of the CDRs per domain and subsystem (offline charging);
+- the content of real-time charging messages per domain/subsystem (online charging);
+- the functionality of online and offline charging for those domains and subsystems;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSes is defined in TS 32.240.
+
+This document specifies the offline and online charging description for the multimedia broadcast and multicast service (MBMS), based on the functional stage 2 description in TS 23.246. This charging description includes the offline and online charging architecture and scenarios specific to MBMS, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 onto MBMS. It further specifies the structure and content of the CDRs for offline charging, and the
+
+charging events for online charging. The present document is related to other 3GPP charging TSes as follows:
+
+- The common 3GPP charging architecture is specified in TS 32.240.
+- The parameters, abstract syntax and encoding rules for these CDR types are specified in TS 32.298.
+- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in TS 32.297.
+- The 3GPP Diameter application that is used for WLAN offline and online charging is specified in TS 32.299.
+
+All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSes, are defined in the 3GPP Vocabulary, TR 21.905. Those that are common across charging management in GSM/UMTS domains or subsystems are provided in the umbrella document TS 32.240 and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 273 | 11.1.0 | Published | 2014-01-15 | http://www.etsi.org/deliver/etsi_ts/132200_132299/132273/11_01_00_60/ts_132273v110100p.pdf |
+| ATIS | ATIS.3GPP.32.273V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.273(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT_3G-32.273(R11-11.0.0) |
+| TTC | TS-3GA-32.273(Re11)v11.1.0 | 11.1.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-32.273(Re11)v11.1.0.pdf |
+
+### 10.9.29 TS 32.274 Telecommunication management; Charging management; Short message service (SMS) charging
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in 3GPP TS 32.240, which provides an umbrella for other charging management TSs that specify:
+
+- the content of the CDRs per domain/subsystem/service (offline charging);
+- the content of real-time charging messages per domain/subsystem/service (online charging);
+- the functionality of online and offline charging for those domains/subsystems/services;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in 3GPP TS 32.240.
+
+This document specifies the Offline and Online Charging description for the Short Message Service (SMS), based on the functional description in 3GPP TS 23.040 and on the SMS over IP in 3GPP TS 23.204. The document does not replace existing offline SMS charging functionality and therefore is in addition to that defined in 3GPP TS 32.250 and 3GPP TS 32.251. This charging description includes the offline and online charging architecture and scenarios specific to SMS, as well as the
+
+mapping of the common 3GPP charging architecture specified in 3GPP TS 32.240 onto SMS. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. This document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in 3GPP TS 32.240;
+- The parameters, abstract syntax and encoding rules for the CDRs are specified in 3GPP TS 32.298;
+- A transaction based mechanism for the transfer of CDRs within the network is specified in TS 32.295;
+- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in 3GPP TS 32.297;
+- The 3GPP Diameter application that is used for SMS offline and online charging is specified in 3GPP TS 32.299.
+
+Furthermore, requirements that govern the charging work are specified in 3GPP TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 274 | 11.0.0 | Published | 2012-09-28 | http://www.etsi.org/deliver/etsi_ts/132200_132299/132274/11.00.00_60/ts_132274v110000p.pdf |
+| ATIS | ATIS.3GPP.32.274V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.274(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.274(R11-11.0.0) |
+| TTC | TS-3GA-32.274(Re11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.274(Re11)v11.0.0.pdf |
+
+### 10.9.30 TS 32.275 Telecommunication management; Charging management; MultiMedia telephony (MMTel) charging
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in 3GPP TS 32.240, which provides an umbrella for other charging management TSs that specify:
+
+- the content of the CDRs per domain and subsystem (offline charging);
+- the content of real-time charging messages per domain / subsystem (online charging);
+- the functionality of online and offline charging for those domains and subsystems;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSes is defined in TS 32.240.
+
+The present document specifies the offline and online charging for multiMedia telephony (MMTel) service and supplementary services, based on the functional description of MMTel in 3GPP TS 22.173. Charging for the following supplementary services is specified:
+
+- a) Communications Diversion (CDIV)
+- b) Communication Hold (HOLD)
+- c) CONference (CONF)
+- d) Message Waiting Indication (MWI)
+
+- e) Originating Identity Presentation (OIP) / Originating Identity Restriction (OIR)
+- f) Terminating Identity Presentation (TIP) / Terminating Identity Restriction (TIR)
+- g) Call Barring (CB)
+- h) Explicit Call Transfer (ECT)
+- i) Communication Wait (CW)
+- j) Completion of Communications to Busy Subscriber (CCBS)
+- k) Completion of Communications by No Reply (CCNR)
+- l) Malicious Communication Identification (MCID)
+- m) Customized Alerting Tone (CAT)
+- n) Closed User Group (CUG)
+- o) Personal Network Management (PNM)
+- p) Customized Ringing Signal (CRS)
+- q) Reverse Charging
+
+Charging of these supplementary services is performed at the respective MMTel AS. The MMTel charging aspects are an extension of the basic IMS charging capabilities as specified in the TS 32.260.
+
+This charging description includes the offline and online charging architecture and scenarios specific to the MMTel, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 onto the MMTel. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging.
+
+The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in TS 32.240;
+- The common IMS charging principles are specified in the TS 32.260;
+- The parameters, abstract syntax and encoding rules for these CDR types are specified in TS 32.298;
+- A transaction based mechanism for the transfer of CDRs within the network is specified in TS 32.295;
+- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in TS 32.297;
+- The 3GPP Diameter application that is used for MMTel offline and online charging is specified in TS 32.299.
+
+All references, abbreviations, definitions, descriptions, principles and requirements, used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905. Those that are common across charging management in GSM/UMTS domains or subsystems are provided in the umbrella document TS 32.240. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 275 | 11.3.0 | Published | 2013-10-04 | http://www.etsi.org/deliver/etsi_ts/132200_132299/132275/11_03_00_60/ts_132275v110300p.pdf |
+| ATIS | ATIS.3GPP.32.275V1121-2014 | 11.2.1 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.275(R11-11.2.1) | 11.2.1 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.275(R11-11.2.1) |
+| TTC | TS-3GA-32.275(Rel11)v11.3.0 | 11.3.0 | TTC Approved | 2013-11-22 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.275(Rel11)v11.3.0.pdf |
+
+### 10.9.31 TS 32.280 Telecommunication management; Charging management; Advice of charge (AoC) service
+
+This document specifies the AoC framework for relevant events, sessions, and services. The 3GPP umbrella charging architecture and principles are defined in 3GPP TS 32.240.
+
+The AoC framework detailed herein provides for both offline and online charging models. It specifies the following:
+
+- The AoC architecture.
+- The common principles that govern AoC.
+- The AoC function that enables the IMS AoC framework.
+- Exemplary message flows.
+- AoC interface data description.
+
+All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905. Those that are common across charging management in 3GPP network, services or subsystems are provided in the umbrella document TS 32.240 and may be copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Requirements that govern the AoC work are specified in 3GPP TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 280 | 11.1.0 | Published | 2014-01-20 | http://www.etsi.org/deliver/etsi_ts/132200_132299/132280/11_01_00_60/ts_132280v110100p.pdf |
+| ATIS | ATIS.3GPP.32.280V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.280(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.280(R11-11.0.0) |
+| TTC | TS-3GA-32.280(Rel11)v11.1.0 | 11.1.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-32.280(Rel11)v11.1.0.pdf |
+
+### 10.9.32 TS 32.295 Telecommunication management; Charging management; Charging data record (CDR) transfer
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks.
+
+The document specifies the transaction-based mechanism for the near real-time transfer of CDRs within the network.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 295 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132200_132299/132295/11.00.00_60/ts_132295v110000p.pdf |
+| ATIS | ATIS.3GPP.32.295V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.295(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.295(R11-11.0.0) |
+| TTC | TS-3GA-32.295(Re11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.295(Re11)v11.0.0.pdf |
+
+### 10.9.33 TS 32.296 Telecommunication management; Charging management; Online charging system (OCS): Applications and interfaces
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks.
+
+The document covers all internal aspects of the online charging system (OCS). The document contains the architecture and functions of the OCS logical components and thereby derives the functionality of the OCS interfaces. A detailed specification of interfaces between the logical OCS components is also included. The functionality of the OCS, as described in the present document, applies to all charging domains (bearer, session and service).
+
+The interfaces connecting to the OCS (e.g., Ro, CAP) are out of the scope of the present document.
+
+NOTE – In the current release, the present document is limited to the interface between the charging function and the rating function, namely Re.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 296 | 11.5.0 | Published | 2013-04-18 | http://www.etsi.org/deliver/etsi_ts/132200_132299/132296/11.05.00_60/ts_132296v110500p.pdf |
+| ATIS | ATIS.3GPP.32.296V1150-2014 | 11.5.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.296(R11-11.5.0) | 11.5.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.296(R11-11.5.0) |
+| TTC | TS-3GA-32.296(Re11)v11.5.0 | 11.5.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.296(Re11)v11.5.0.pdf |
+
+### 10.9.34 TS 32.297 Telecommunication management; Charging management; Charging data record (CDR) file format and transfer
+
+This document is part of a series of documents specifying charging functionality and charging management in GSM/UMTS networks.
+
+The document specifies the mechanisms used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device). This includes the file transfer procedures and the layout of the CDR files, as well as file meta information and the encoding of the CDRs within the files.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 297 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132200_132299/132297/11.00.00_60/ts_132297v110000p.pdf |
+| ATIS | ATIS.3GPP.32.297V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.297(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.297(R11-11.0.0) |
+| TTC | TS-3GA-32.297(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.297(Rel11)v11.0.0.pdf |
+
+### 10.9.35 TS 32.299 Telecommunication management; Charging management; Diameter charging applications
+
+The document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks.
+
+This document specifies in detail the Diameter-based offline and online charging applications for 3GPP networks. It includes all charging parameters, scenarios and message flows.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 299 | 11.11.0 | Published | 2014-03-21 | http://www.etsi.org/deliver/etsi_ts/132200_132299/132299/11.11.00_60/ts_132299v111100p.pdf |
+| ATIS | ATIS.3GPP.32.299V1170-2014 | 11.7.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.299(R11-11.7.0) | 11.7.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.299(R11-11.7.0) |
+| TTC | TS-3GA-32.299(Rel11)v11.10.0 | 11.10.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-32.299(Rel11)v11.10.0.pdf |
+
+### 10.9.36 TS 32.300 Telecommunication management; Configuration management (CM); Name convention for managed objects
+
+A more detailed background and introduction of the IRP concept is given in TS 32.101 and TS 32.102.
+
+To perform network management tasks, cooperating applications require identical interpretation of names assigned to network resources under management. Such names are required to be unambiguous as well. The document recommends one name convention for network resources under management in the IRP context.
+
+To facilitate integration of network management information obtained via multiple IRPs of different technologies such as common management information protocol (CMIP) and common object request broker architecture (CORBA), identical network resource name semantics shall be conveyed in all IRPs. The document specifies one such name convention.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 300 | 11.2.0 | Published | 2013-07-10 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132300/11_02_00_60/ts_132300v110200p.pdf |
+| ATIS | ATIS.3GPP.32.300V1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.300(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.300(R11-11.1.0) |
+| TTC | TS-3GA-32.300(Rel11)v11.2.0 | 11.2.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.300(Rel11)v11.2.0.pdf |
+
+### 10.9.37 TS 32.301 Telecommunication management; Configuration management (CM); Notification integration reference point (IRP): Requirements
+
+The purpose of notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. This document is the "Requirements" of notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the basic requirements that shall be fulfilled on Itf-N.
+
+How IRPManager discovers the IRPAgent's address or reference (so that IRPManager can invoke an operation) is outside the scope of this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 301 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132301/11_00_00_60/ts_132301v110000p.pdf |
+| ATIS | ATIS.3GPP.32.301V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.301(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.301(R11-11.0.0) |
+| TTC | TS-3GA-32.301(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.301(Rel11)v11.0.0.pdf |
+
+### 10.9.38 TS 32.302 Telecommunication management; Configuration management (CM); Notification integration reference point (IRP); Information service (IS)
+
+The purpose of notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. This document is the "Information Service" of notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information. It also defines the information common to all notifications which is called the "notificationHeader".
+
+An IRPAgent supporting this IRP IS may emit one or multiple categories of notifications, such as alarms (as specified in Alarm IRP: Information service 3G TS 32.111-2) and others. This IRP IS defines a mechanism that IRPManager can use to determine the categories of notifications supported by an IRPAgent. It also defines a mechanism (subscribe and unsubscribe operations) that IRPManager can use to specify the categories of notifications IRPAgent should emit to IRPManager during subscription. It also defines a mechanism (getSubscriptionIds operation) that IRPManager can use to check which categories of notifications it has subscribed to. IRPManager can set and change filter criteria applicable during the life-cycle of a subscription. IRPManager can
+
+also exercise flow-control on IRP Agent's emission of notifications (suspendSubscription and resumeSubscription operations).
+
+Using different managerReference, an IRP Manager can subscribe several times. It will result in multiple subscriptions. As far as IRP Agent is concerned, notifications are sent to multiple "places".
+
+Using the same managerReference, an IRP Manager can subscribe several times specifying different categories of notifications.
+
+This IRP IS does not specify information that is carried in some but not all notifications. That kind of information is specified in other IRP ISs involved. For example, perceivedSeverity is a piece of information specific for notifications carrying alarm information. This information is not defined in this document but in Alarm IRP: Information service 3G TS 32.111-2.
+
+How IRP Manager discovers the IRP Agent's address or reference (so that IRP Manager can invoke an operation) is outside the scope of this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 302 | 11.1.0 | Published | 2013-01-31 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132302/11.01.00_60/ts_132302v110100p.pdf |
+| ATIS | ATIS.3GPP.32.302V1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.302(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.302(R11-11.1.0) |
+| TTC | TS-3GA-32.302(Rel11)v11.1.0 | 11.1.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.302(Rel11)v11.1.0.pdf |
+
+### 10.9.39 TS 32.311 Telecommunication management; Generic IRP management: Requirements
+
+The purpose of the document is to define a common service supported by all IRPs. This document is the "Requirements" part. It defines, for the purpose of supporting the common service, the requirements that shall be fulfilled by all IRPs supporting this service.
+
+With this common service supported by all IRPs, an IRP Manager shall be able to retrieve the profile of operations and notifications supported by a given IRP that are by an IRP Agent. An IRP Manager shall also be able to retrieve the different versions supported by an IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 311 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132311/11.00.00_60/ts_132311v110000p.pdf |
+| ATIS | ATIS.3GPP.32.311V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.311(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.311(R11-11.0.0) |
+| TTC | TS-3GA-32.311(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.311(Rel11)v11.0.0.pdf |
+
+#### **10.9.40 TS 32.312 Telecommunication management; Generic IRP management; Information service**
+
+The purpose of the document is to define a common service supported by all IRPs. This document is the "Information Service" part. It defines, for the purpose of supporting the common service, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information.
+
+With this common service supported by all IRPs, an IRPManager can retrieve the profile of operations and notifications supported by a given IRP supported by an IRPAgent. An IRPManager can also retrieve the different versions supported by an IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 312 | 11.1.0 | Published | 2013-04-18 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132312/11_01_00_60/ts_132312v110100p.pdf |
+| ATIS | ATIS.3GPP.32.312V 1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.312(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.312(R11-11.1.0) |
+| TTC | TS-3GA-32.312(Rel11)v11.1.0 | 11.1.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.312(Rel11)v11.1.0.pdf |
+
+#### **10.9.41 TS 32.316 Telecommunication management; Generic integration reference point (IRP) management; Solution set (SS) definitions**
+
+The document provides the solution set definitions for generic integration reference point (IRP) management, whose capabilities are specified in TS 32.312, the generic IRP management: Information service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 316 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132316/11_00_00_60/ts_132316v110000p.pdf |
+| ATIS | ATIS.3GPP.32.316V 1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.316(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.316(R11-11.0.0) |
+| TTC | TS-3GA-32.316(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.316(Rel11)v11.0.0.pdf |
+
+#### **10.9.42 TS 32.321 Telecommunication management; Test management integration reference point (IRP): Requirements**
+
+This document describes, in addition to the requirements defined in 3G TS 32.101 and 3G TS 32.102, the requirements for the test management IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 321 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132321/11.00.00_60/ts_132321v110000p.pdf |
+| ATIS | ATIS.3GPP.32.321V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.321(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.321(R11-11.0.0) |
+| TTC | TS-3GA-32.321(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.321(Rel11)v11.0.0.pdf |
+
+#### 10.9.43 TS 32.322 Telecommunication management; Test management integration reference point (IRP); Information service
+
+This document defines the IS part of the test management IRP, which describes the semantics of the information and the interactions visible across Itf-N in a protocol-independent way. The information is specified by means of information object classes and the interactions by means of operations and notifications. This document does not specify the syntax (encoding) of the information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 322 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132322/11.00.00_60/ts_132322v110000p.pdf |
+| ATIS | ATIS.3GPP.32.322V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.322(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.322(R11-11.0.0) |
+| TTC | TS-3GA-32.322(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.322(Rel11)v11.0.0.pdf |
+
+#### 10.9.44 TS 32.326 Telecommunication management; Test management integration reference point (IRP): Solution set (SS) definitions
+
+The document contains solution sets for the IRP whose semantics is specified in test management IRP IS (TS 32.322).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 326 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132326/11.00.00_60/ts_132326v110000p.pdf |
+| ATIS | ATIS.3GPP.32.326V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.326(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.326(R11-11.0.0) |
+| TTC | TS-3GA-32.326(Rel11)v11.1.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.326(Rel11)v11.0.0.pdf |
+
+#### 10.9.45 TS 32.331 Telecommunication management; Notification log integration reference point (IRP): Requirements
+
+The document describes the requirements and information model necessary for telecommunications management (TM). The TM principles and TM architecture are specified in 3G TS 32.101 and 3G TS 32.102, respectively.
+
+This document specifies the overall requirements for notification log management over ItfN.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 331 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132331/11.00.00_60/ts_132331v110000p.pdf |
+| ATIS | ATIS.3GPP.32.331V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.331(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.331(R11-11.0.0) |
+| TTC | TS-3GA-32.331(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.331(Rel11)v11.0.0.pdf |
+
+#### 10.9.46 TS 32.332 Telecommunication management; Notification log integration reference point (IRP): Information service (IS)
+
+The document specifies the information service for the notification log integration reference point (NL IRP) as it applies to Itf-N.
+
+This IRP IS defines the semantics of operations (and their parameters) visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 332 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132332/11.00.00_60/ts_132332v110000p.pdf |
+| ATIS | ATIS.3GPP.32.332V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.332(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.332(R11-11.0.0) |
+| TTC | TS-3GA-32.332(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.332(Rel11)v11.0.0.pdf |
+
+#### 10.9.47 TS 32.336 Telecommunication management; Notification log (NL) integration reference point (IRP): Solution sets (SS) definitions
+
+The document specifies the solution sets for the IRP whose semantics is specified in notification log (NL) IRP IS (TS 32.332).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 336 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132336/11.00.00_60/ts_132336v110000p.pdf |
+| ATIS | ATIS.3GPP.32.336V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.336(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.336(R11-11.0.0) |
+| TTC | TS-3GA-32.336(Re11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.336(Re11)v11.0.0.pdf |
+
+#### 10.9.48 TS 32.341 Telecommunication management; File transfer (FT) integration reference point (IRP): Requirements
+
+The document specifies the overall requirements for the file transfer integration reference point (FT IRP) as it applies to the Itf-N.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 341 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132341/11.00.00_60/ts_132341v110000p.pdf |
+| ATIS | ATIS.3GPP.32.341V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.341(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.341(R11-11.0.0) |
+| TTC | TS-3GA-32.341(Re11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.341(Re11)v11.0.0.pdf |
+
+#### 10.9.49 TS 32.342 Telecommunication management; File transfer (FT) integration reference point (IRP): Information service (IS)
+
+The document specifies the information service for the file transfer integration reference point (FileTransferIRP) as it applies to the Itf-N.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 342 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132342/11.00.00_60/ts_132342v110000p.pdf |
+| ATIS | ATIS.3GPP.32.342V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.342(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.342(R11-11.0.0) |
+| TTC | TS-3GA-32.342(Re11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.342(Re11)v11.0.0.pdf |
+
+#### 10.9.50 TS 32.346 Telecommunication management; File Transfer (FT) Integration reference point (IRP): Solution set (SS) definitions
+
+The document contains the solution sets for the IRP whose semantics are specified in File Transfer IRP: Information service TS 32.342.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 346 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132346/11.00.00_60/ts_132346v110000p.pdf |
+| ATIS | ATIS.3GPP.32.346V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.346(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.346(R11-11.0.0) |
+| TTC | TS-3GA-32.346(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.346(Rel11)v11.0.0.pdf |
+
+### 10.9.51 TS 32.351 Telecommunication management; Communication surveillance (CS) integration reference point (IRP): Requirements
+
+The document describes the requirements of the communication surveillance IRP (CSIRP).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 351 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132351/11.00.00_60/ts_132351v110000p.pdf |
+| ATIS | ATIS.3GPP.32.351V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.351(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.351(R11-11.0.0) |
+| TTC | TS-3GA-32.351(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.351(Rel11)v11.0.0.pdf |
+
+### 10.9.52 TS 32.352 Telecommunication management; Communication surveillance (CS) integration reference point (IRP): Information service (IS)
+
+The document defines the IS part of the CSIRP, which describes the semantics of the information and the interactions visible across Itf-N in a protocol-independent way. The information is specified by means of information object classes and the interactions by means of operations and notifications. The present document does not specify the syntax (encoding) of the information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 352 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132352/11.00.00_60/ts_132352v110000p.pdf |
+| ATIS | ATIS.3GPP.32.352V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.352(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.352(R11-11.0.0) |
+| TTC | TS-3GA-32.352(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.352(Rel11)v11.0.0.pdf |
+
+### 10.9.53 TS 32.356 Telecommunication management; Communication surveillance (CS) Integration reference point (IRP); Solution set (SS) definitions
+
+The document specifies Solution Set definitions for the IRP whose semantics is specified in TS 32.352 Communication surveillance IRP: Information service.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 356 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132356/11.00.00_60/ts_132356v110000p.pdf |
+| ATIS | ATIS.3GPP.32.356V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.356(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.356(R11-11.0.0) |
+| TTC | TS-3GA-32.356(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.356(Rel11)v11.0.0.pdf |
+
+### 10.9.54 TS 32.361 Telecommunication management; Entry point (EP) integration reference point (IRP): Requirements
+
+The document describes the requirements of the EPIRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 361 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132361/11.00.00_60/ts_132361v110000p.pdf |
+| ATIS | ATIS.3GPP.32.361V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.361(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.361(R11-11.0.0) |
+| TTC | TS-3GA-32.361(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.361(Rel11)v11.0.0.pdf |
+
+### 10.9.55 TS 32.362 Telecommunication management; Entry point (EP) integration reference point (IRP): Information service (IS)
+
+The document defines the IS part of the EPIRP, which describes the semantics of the information and the interactions visible across Itf-N in a protocol independent way. The information is specified by means of information object classes and the interactions by means of operations and notifications. The present document does not specify the syntax (encoding) of the information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 362 | 11.1.0 | Published | 2013-04-18 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132362/11.01.00_60/ts_132362v110100p.pdf |
+| ATIS | ATIS.3GPP.32.362V1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.362(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.362(R11-11.1.0) |
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTC | TS-3GA-32.362(Rel11)v11.1.0 | 11.1.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.362(Rel11)v11.1.0.pdf |
+
+### 10.9.56 TS 32.366 Telecommunication management; Entry point (EP) Integration reference point (IRP); Solution set (SS) definitions
+
+The document specifies solution set definitions for the IRP whose semantics are specified in the Entry Point IRP: Information service (TS 32.362).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 366 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132366/11.00.00/60/ts_132366v110000p.pdf |
+| ATIS | ATIS.3GPP.32.366V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.366(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.366(R11-11.0.0) |
+| TTC | TS-3GA-32.366(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.366(Rel11)v11.0.0.pdf |
+
+### 10.9.57 TS 32.371 Telecommunication management; Security management concept and requirements
+
+The document defines, in addition to the requirements defined in 3G TS 32.101 and 3G TS 32.102, the requirements for security management IRP.
+
+The purpose of this document is to specify the necessary security features, services and functions to protect the network management data, including requests, responses, notifications and files, exchanged across the Itf-N.
+
+Telecommunication network security can be breached by weaknesses in operational procedures, physical installations, communication links, computational processes and data storage. Of concern here in the present document is the security problems resulting from the weaknesses inherent in the communication technologies (i.e., the 3GPP-defined interface IRPs and their supporting protocol stacks) deployed across the Itf-N.
+
+An appropriate level of security for a telecommunication network is essential. Secured access to the network management applications, and network management data, is essential. The 3GPP-defined interface IRPs (and their supporting protocol stacks), deployed across the Itf-N, are used for such access, and therefore, their security is considered essential.
+
+Many network management security standards exist. However, there is no recommendation on how to apply them in the Itf-N context. Their deployment across the Itf-N is left to operators. The present document and the corresponding solutions identify and recommend security standards in the Itf-N context.
+
+The business case for secured Itf-N is complex as it does not relate to the functions of the interface IRPs (the functions are constant) but rather, it relates to variants such as the cost of recovering from security breaks, the probability of security incidents and the cost of implementing security management, all of which differ depending on specific deployment scenarios.
+
+This document describes the security functions for a 3G network in terms of security domains.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 371 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132371/11.00.00_60/ts_132371v110000p.pdf |
+| ATIS | ATIS.3GPP.32.371V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.371(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttastddesc.jsp?stdno=TTAT.3G-32.371(R11-11.0.0) |
+| TTC | TS-3GA-32.371(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.371(Rel11)v11.0.0.pdf |
+
+#### **10.9.58 TS 32.372 Telecommunication management; Security services for integration reference point (IRP): Information service (IS)**
+
+The purpose of this document is to specify the necessary security features, services and functions to protect the network management data, including requests, responses, notifications and files, exchanged across the ItfN.
+
+The document specifies the security service for IRP information service.
+
+This security service for IRP IS defines the semantics of management information visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters.
+
+This information service specification is related to 3GPP TS 32.371.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 372 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132372/11.00.00_60/ts_132372v110000p.pdf |
+| ATIS | ATIS.3GPP.32.372V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.372(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttastddesc.jsp?stdno=TTAT.3G-32.372(R11-11.0.0) |
+| TTC | TS-3GA-32.372(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.372(Rel11)v11.0.0.pdf |
+
+#### **10.9.59 TS 32.376 Telecommunication management; Security services for integration reference point (IRP); Solution set (SS) definitions**
+
+This document specifies solution set for the IRP whose semantics is specified in TS 32.372 security service for IRP information service.
+
+Note that within the document there are several alternate solutions. Specific choices will need to be made to counter identified security threats, and to consider performance and cost criteria, i.e., an implementation is not expected to have to support every option for every deployment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 376 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132376/11.00.00_60/ts_132376v110000p.pdf |
+| ATIS | ATIS.3GPP.32.376V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.376(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.376(R11-11.0.0) |
+| TTC | TS-3GA-32.376(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.376(Rel11)v11.0.0.pdf |
+
+#### **10.9.60 TS 32.381 Telecommunication management; Partial suspension of Itf-N integration reference point (IRP): Requirements**
+
+The purpose of partial suspension of Itf-N IRP is to define an interface through which an IRPManager can suspend the forwarding of notifications via Itf-N which were generated in parts of the managed systems.
+
+This document contains the requirements of partial suspension of Itf-N IRP. It defines, for the purpose of generally suspending the forwarding of notifications, the basic requirements to be fulfilled on Itf-N.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 381 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132381/11.00.00_60/ts_132381v110000p.pdf |
+| ATIS | ATIS.3GPP.32.381V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.381(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.381(R11-11.0.0) |
+| TTC | TS-3GA-32.381(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.381(Rel11)v11.0.0.pdf |
+
+#### **10.9.61 TS 32.382 Telecommunication management; Partial suspension of Itf-N integration reference point (IRP): Information service (IS)**
+
+The purpose of partial suspension of Itf-N IRP is to define an interface through which an IRPManager can suspend the forwarding of notifications via Itf-N which were generated in parts of the managed systems.
+
+This document is the information service of partial suspension of Itf-N IRP. It defines, for the purpose of suspending generally the forwarding of notifications, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 382 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132382/11.00.00_60/ts_132382v110000p.pdf |
+| ATIS | ATIS.3GPP.32.382V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.382(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.382(R11-11.0.0) |
+| TTC | TS-3GA-32.382(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.382(Rel11)v11.0.0.pdf |
+
+#### 10.9.62 TS 32.386 Telecommunication management; Partial suspension of Itf-N integration reference point (IRP); Solution set (SS) definitions
+
+This document specifies the SOAP SS for the IRP whose semantics is specified partial suspension of Itf-N IRP IS (TS 32.382).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 386 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132386/11.00.00_60/ts_132386v110000p.pdf |
+| ATIS | ATIS.3GPP.32.386V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.386(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.386(R11-11.0.0) |
+| TTC | TS-3GA-32.386(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.386(Rel11)v11.0.0.pdf |
+
+#### 10.9.63 TS 32.391 Telecommunication management; Delta synchronization integration reference point (IRP): Requirements
+
+The purpose of delta synchronization IRP is to define an interface through which an IRPManager can request only those data which changed (i.e., changed, were created or deleted) from a synchronization point onwards.
+
+This document contains the requirements of delta synchronization IRP. It defines, for the purpose of delta synchronization, the basic requirements to be fulfilled on Itf-N.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 391 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132391/11.00.00_60/ts_132391v110000p.pdf |
+| ATIS | ATIS.3GPP.32.391V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.391(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.391(R11-11.0.0) |
+| TTC | TS-3GA-32.391(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.391(Rel11)v11.0.0.pdf |
+
+### 10.9.64 TS 32.392 Telecommunication management; Delta synchronization integration reference point (IRP): Information service (IS)
+
+The purpose of delta synchronization IRP is to define an interface through which an IRPManager can request only those data which changed (i.e., changed, were created or deleted) from a synchronization point onwards.
+
+This document is the information service of delta synchronization IRP. It defines, for the purpose of delta synchronization, the information observable and controlled by management system's client, and it also specifies the semantics of the interactions used to carry this information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 392 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132392/11.00.00/60/ts_132392v110000p.pdf |
+| ATIS | ATIS.3GPP.32.392V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.392(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.392(R11-11.0.0) |
+| TTC | TS-3GA-32.392(Re11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.392(Re11)v11.0.0.pdf |
+
+### 10.9.65 TS 32.396 Telecommunication management; Delta synchronization integration reference point (IRP); Solution set (SS) definitions
+
+This document specifies solution set definitions for the IRP whose semantics is specified in Delta Synchronization IRP IS (TS 32.392).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 396 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/132300_132399/132396/11.00.00/60/ts_132396v110000p.pdf |
+| ATIS | ATIS.3GPP.32.396V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.396(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.396(R11-11.0.0) |
+| TTC | TS-3GA-32.396(Re11)v11.1.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.396(Re11)v11.0.0.pdf |
+
+### 10.9.66 TS 32.401 Telecommunication management; Performance management (PM); Concept and requirements
+
+The present document describes the requirements for the management of performance measurements and the collection of performance measurement result data across GSM and UMTS networks. It defines the administration of measurement schedules by the network element manager (EM), the generation of measurement results in the network elements (NEs) and the transfer of these results to one or more operations systems, i.e., EM(s) and/or network manager(s) (NM(s)).
+
+The basic performance management concept that the present document is built upon is described in clause 4. The requirements of how an EM administers the performance measurements and how the results can be collected are defined in detail in clause 5. Measurements available for collection by NEs are described in the following specifications:
+
+- TS 52.402 for GSM systems;
+- TS 32.405, TS 32.406, TS 32.407 and TS 32.408 for UMTS and combined UMTS/GSM systems;
+- TS 32.409 for IMS networks.
+
+Effort has been made to ensure consistency in the definition of measurements between different NEs and generations. The performance measurement result is described in performance measurement file format definition (TS 32.432).
+
+The following is beyond the scope of the present document, and therefore the present document does not describe:
+
+- the formal definition of the interface that the EM uses to administer performance measurements in the NEs;
+- the formal definition of the interface that the EM uses to collect measurement results from the NEs;
+- how the data, once accumulated and collected, could or should be processed, stored, or presented to an end user;
+- the information which may be obtained through the collection and processing of call or event-related records which have been produced by the NEs primarily for the purpose of raising bills and other charges.
+
+The management requirements have been derived from existing telecommunications operations experience. The management definitions were then derived from other standardization work so as to minimise the re-invention factor. References are given as appropriate.
+
+The objectives of this standardization are:
+
+- to provide the descriptions for a standard set of measurements;
+- to produce a common description of the management technique for measurement administration and result accumulation; and
+- to define a method for the bulk transmission of measurement results across a management interface.
+
+The definition of the standard measurements is intended to result in comparability of measurement result data produced in a multi-vendor wireless network, for those measurement types that can be standardized across all vendors' implementations.
+
+As far as possible, existing standardization in the area of performance management has been reused and enhanced where particular requirements, peculiar to the mobile telephony environment, have been recognized.
+
+This document considers all the above aspects of performance management for a GSM and UMTS network and its NEs defined in the core Technical Specifications. However, only those aspects which are specific to a GSM/UMTS system and particular to wireless network operation are included in the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 401 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132400_132499/132401/11.00.00_60/ts_132401v110000p.pdf |
+| ATIS | ATIS.3GPP.32.401V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.401(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.401(R11-11.0.0) |
+| TTC | TS-3GA-32.401(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.401(Rel11)v11.0.0.pdf |
+
+### 10.9.67 TS 32.404 Telecommunication management; Performance management (PM); Performance measurements – Definitions and template
+
+This document describes the measurements for UMTS and combined UMTS/GSM.
+
+TS 32.401 describes performance management concepts and requirements.
+
+The present document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network.
+
+Only measurement types that are specific to UMTS or combined UMTS/GSM networks are defined within the present documents. Vendor-specific measurement types used in UMTS and combined UMTS/GSM networks are not covered. Instead, these could be applied according to the manufacturer's documentation.
+
+Measurements related to "external" technologies (such as ATM or IP), as described by "external" standards bodies (e.g., ITU-T or IETF), shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
+
+The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardized across all vendors' implementations.
+
+TS 32.411; Telecommunication management; performance management (PM) integration reference point (IRP): Requirements
+
+This document specifies the overall requirements for the performance management integration reference point (PMIRP) as it applies to the network elements (NE), element manager (EM) and network manager (NM).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 404 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132400_132499/132404/11.00.00_60/ts_132404v110000p.pdf |
+| ATIS | ATIS.3GPP.32.404V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.404(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.404(R11-11.0.0) |
+| TTC | TS-3GA-32.404(Rel11)v11.1.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.404(Rel11)v11.1.0.pdf |
+
+### **10.9.68 TS 32.406 Telecommunication management; Performance management (PM); Performance measurements core network (CN) packet switched (PS) domain**
+
+This document describes the measurements for UMTS and combined UMTS/GSM.
+
+TS 32.401 describes performance management concepts and requirements.
+
+This document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network.
+
+Only measurement types that are specific to UMTS or combined UMTS/GSM networks are defined within the present documents. Vendor-specific measurement types used in UMTS and combined UMTS/GSM networks are not covered. Instead, these could be applied according to the manufacturer's documentation.
+
+Measurements related to "external" technologies (such as ATM or IP), as described by "external" standards bodies (e.g., ITU-T or IETF), shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
+
+The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardized across all vendors' implementations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 406 | 11.3.0 | Published | 2012-11-19 | http://www.etsi.org/deliver/etsi_ts/132400_132499/132406/11_03.00/60/ts_132406v110300p.pdf |
+| ATIS | ATIS.3GPP.32.406V1130-2014 | 11.3.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.406(R11-11.3.0) | 11.3.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT_3G-32.406(R11-11.3.0) |
+| TTC | TS-3GA-32.406(Rel11)v11.3.0 | 11.3.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.406(Rel11)v11_3_0.pdf |
+
+### **10.9.69 TS 32.408 Telecommunication management; Performance management (PM); Performance measurements teleservice**
+
+This document describes the measurements for UMTS and combined UMTS/GSM.
+
+TS 32.401 describes performance management concepts and requirements.
+
+This document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network.
+
+Only measurement types that are specific to UMTS or combined UMTS/GSM networks are defined within the present documents. Vendor-specific measurement types used in UMTS and combined UMTS/GSM networks are not covered. Instead, these could be applied according to the manufacturer's documentation.
+
+Measurements related to "external" technologies (such as ATM or IP), as described by "external" standards bodies (e.g., ITU-T or IETF), shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
+
+The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardized across all vendors' implementations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 408 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132400_132499/132408/11.00.00_60/ts_132408v110000p.pdf |
+| ATIS | ATIS.3GPP.32.408V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.408(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.408(R11-11.0.0) |
+| TTC | TS-3GA-32.408(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.408(Rel11)v11.0.0.pdf |
+
+#### 10.9.70 TS 32.411 Telecommunication management; Performance management (PM) integration reference point (IRP): Requirements
+
+The present document specifies the overall requirements for the performance management integration reference point (PMIRP) as it applies to the network elements (NE), element manager (EM) and network manager (NM).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 411 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132400_132499/132411/11.00.00_60/ts_132411v110000p.pdf |
+| ATIS | ATIS.3GPP.32.411V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.411(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.411(R11-11.0.0) |
+| TTC | TS-3GA-32.411(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.411(Rel11)v11.0.0.pdf |
+
+#### 10.9.71 TS 32.412 Telecommunication management; Performance management (PM) integration reference point (IRP): Information service (IS)
+
+This document specifies the information service for the performance management integration reference point (PMIRP) as it applies to the Itf-N.
+
+This IRP IS defines the semantics of operations (and their parameters) visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 412 | 11.1.0 | Published | 2013-02-01 | http://www.etsi.org/deliver/etsi_ts/132400_132499/132412/11.01.00_60/ts_132412v110100p.pdf |
+| ATIS | ATIS.3GPP.32.412V1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.412(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.412(R11-11.1.0) |
+| TTC | TS-3GA-32.412(Rel11)v11.1.0 | 11.1.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.412(Rel11)v11.1.0.pdf |
+
+### 10.9.72 TS 32.416 Telecommunication management; Performance management (PM) integration reference Point (IRP); Solution set (SS) definitions
+
+This document specifies solution set definitions for the IRP whose semantics is specified in PM (Performance Management) IRP: Information service (TS 32.412).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 416 | 11.1.0 | Published | 2013-07-10 | http://www.etsi.org/deliver/etsi_ts/132400_132499/132416/11.01.00_60/ts_132416v110100p.pdf |
+| ATIS | ATIS.3GPP.32.416V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.416(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.416(R11-11.0.0) |
+| TTC | TS-3GA-32.416(Rel11)v11.1.0 | 11.1.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.416(Rel11)v11.1.0.pdf |
+
+### 10.9.73 TS 32.421 Telecommunication management; Subscriber and equipment trace: Trace concepts and requirements
+
+This document describes the requirements for the management of trace and the reporting of trace data across UMTS networks as it refers to subscriber tracing (tracing of IMSI or private ID) and MS tracing (tracing of IMEI or IMEISV). It defines the administration of trace session activation/deactivation by the element manager (EM) or the network itself via signalling, the generation of trace results in the network elements (NEs) and the transfer of these results to one or more operations systems, i.e., EM(s) and/or network manager(s) (NM(s)).
+
+The basic subscriber and MS trace concept that the present document is built upon is described in clause 4. The high-level requirements for trace data, trace session activation/deactivation and trace reporting are defined in clause 5. Clause 5 also contains an overview of use cases for trace (the use cases are described in Annex B). Annex A provides a high-level view of trace functional architecture. Trace control and configuration management are described in 3GPP TS 32.422, and trace data definition and management are described in 3GPP TS 32.423.
+
+In this release, this document does not cover any trace capability limitations within a NE (e.g., maximum number of simultaneous traced mobiles for a given NE) or any functionality related to these limitations (e.g., NE aborting a trace session due to resource limitations).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 421 | 11.6.0 | Published | 2013-04-18 | http://www.etsi.org/deliver/etsi_ts/132400_132499/132421/11.06.00_60/ts_132421v110600p.pdf |
+| ATIS | ATIS.3GPP.32.421V1160-2014 | 11.6.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.421(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.421(R11-11.6.0) |
+| TTC | TS-3GA-32.421(Rel11)v11.6.0 | 11.6.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.421(Rel11)v11.6.0.pdf |
+
+### **10.9.74 TS 32.422 Telecommunication management; Subscriber and equipment trace; Trace control and configuration management**
+
+This document describes the mechanisms used for the control and configuration of the trace functionality at the EMs and NEs. It covers the triggering events for starting/stopping of subscriber/MS activity traced over 3GPP standardized signalling interfaces, the types of trace mechanisms, configuration of a trace, level of detail available in the trace data, the generation of trace results in the network elements (NEs) and the transfer of these results to one or more EM(s) and/or network manager(s) (NM(s)).
+
+The mechanisms for trace activation/deactivation are detailed in clause 4; clause 5 details the various trace control and configuration parameters and the triggering events that can be set in a network. Trace concepts and requirements are covered in 3G TS 32.421, while trace data definition and management is covered in 3G TS 32.423.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 422 | 11.9.0 | Published | 2014-03-24 | http://www.etsi.org/deliver/etsi_ts/132400_132499/132422/11.09.00_60/ts_132422v110900p.pdf |
+| ATIS | ATIS.3GPP.32.422V 1170-2014 | 11.7.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.422(R11-11.7.0) | 11.7.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.422(R11-11.7.0) |
+| TTC | TS-3GA-32.422(Rel11)v11.8.0 | 11.8.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.422(Rel11)v11.8.0.pdf |
+
+### **10.9.75 TS 32.423 Telecommunication management; Subscriber and equipment trace: Trace data definition and management**
+
+The document describes trace data definition and management. It covers trace records content, their format and transfer.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 423 | 11.7.0 | Published | 2014-03-24 | http://www.etsi.org/deliver/etsi_ts/132400_132499/132423/11.07.00_60/ts_132423v110700p.pdf |
+| ATIS | ATIS.3GPP.32.423V 1140-2014 | 11.4.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.423(R11-11.4.0) | 11.4.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.423(R11-11.4.0) |
+| TTC | TS-3GA-32.423(Rel11)v11.6.0 | 11.6.0 | TTC Approved | 2013-11-22 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.423(Rel11)v11.6.0.pdf |
+
+### **10.9.76 TS 32.426 Telecommunication management; Performance management (PM); Performance measurements evolved packet core network (EPC)**
+
+This document describes the measurements for EPC and combined EPC/UMTS/GSM.
+
+TS 32.401 describes performance management concepts and requirements.
+
+The present document is valid for all measurement types provided by an implementation of an EPC network and combined EPC/UMTS/GSM network. Only measurement types that are specific to EPC or combined EPC/UMTS/GSM networks are defined within the present documents.
+
+Vendor specific measurement types used in EPC and combined EPC/UMTS/GSM networks are not covered. Instead, these could be applied according to manufacturer's documentation.
+
+Measurements related to "external" technologies (such as IP) as described by "external" standards bodies (e.g., IETF) shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
+
+The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
+
+The structure of the present document is as follows:
+
+- Header 1: Network element (e.g., MME related measurements);
+- Header 2: Measurement function;
+- Header 3: Measurements.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 426 | 11.4.0 | Published | 2013-07-10 | http://www.etsi.org/deliver/etsi_ts/132400_132499/132426/11.04.00_60/ts_132426v110400p.pdf |
+| ATIS | ATIS.3GPP.32.426V1130-2014 | 11.3.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.426(R11-11.3.0) | 11.3.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.426(R11-11.3.0) |
+| TTC | TS-3GA-32.426(Rel11)v11.4.0 | 11.4.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.426(Rel11)v11.4.0.pdf |
+
+#### 10.9.77 TS 32.432 Telecommunication management; Performance measurement: File format definition
+
+The document describes the general semantics of performance measurement result and collection. It defines the report file format, report file conventions and the file transfer procedure. Clause 4 specifies the file format for the bulk transfer of performance measurement results to the NM, while clause 6 discusses the file transfer procedure utilized on that interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 432 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132400_132499/132432/11.00.00_60/ts_132432v110000p.pdf |
+| ATIS | ATIS.3GPP.32.432V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.432(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.432(R11-11.0.0) |
+| TTC | TS-3GA-32.432(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.432(Rel11)v11.0.0.pdf |
+
+#### 10.9.78 TS 32.435 Telecommunication management; Performance measurement extensible markup language (XML) file format definition
+
+The document describes the XML file format of performance measurement results whose semantics is defined in 3G TS 32.432.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 435 | 11.0.0 | Published | 2012-10-30 | http://www.etsi.org/deliver/etsi_ts/132400_132499/132435/11.00.00_60/ts_132435v110000p.pdf |
+| ATIS | ATIS.3GPP.32.435V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.435(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.435(R11-11.0.0) |
+| TTC | TS-3GA-32.435(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.435(Rel11)v11.0.0.pdf |
+
+#### 10.9.79 TS 32.436 Telecommunication management; Performance measurement: Abstract syntax notation one (ASN.1) file format definition
+
+The document defines the ASN.1 file format definition for performance measurement results collection whose semantics is defined in 3G TS 32.432.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 436 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/132400_132499/132436/11.00.00_60/ts_132436v110000p.pdf |
+| ATIS | ATIS.3GPP.32.436V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.436(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.436(R11-11.0.0) |
+| TTC | TS-3GA-32.436(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.436(Rel11)v11.0.0.pdf |
+
+#### 10.9.80 TS 32.441 Telecommunication management; Trace management integration reference point (IRP): Requirements
+
+This document specifies the overall requirements for the trace management integration reference point (TraceIRP) as it applies to Itf-N.
+
+The trace IRP supports the operations that are required for the subscriber and equipment trace, the service level trace and the cell traffic trace functionalities.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 441 | 11.3.0 | Published | 2013-01-31 | http://www.etsi.org/deliver/etsi_ts/132400_132499/132441/11.03.00_60/ts_132441v110300p.pdf |
+| ATIS | ATIS.3GPP.32.441V1130-2014 | 11.3.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.441(R11-11.3.0) | 11.3.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.441(R11-11.3.0) |
+| TTC | TS-3GA-32.441(Rel11)v11.3.0 | 11.3.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.441(Rel11)v11.3.0.pdf |
+
+### 10.9.81 TS 32.442 Telecommunication management; Trace management integration reference point (IRP): Information service (IS)
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 442 | 11.6.0 | Published | 2013-04-18 | http://www.etsi.org/deliver/etsi_ts/132400_132499/132442/11.06.00_60/ts_132442v110600p.pdf |
+| ATIS | ATIS.3GPP.32.442V1160-2014 | 11.6.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.442(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.442(R11-11.6.0) |
+| TTC | TS-3GA-32.442(Rel11)v11.6.0 | 11.6.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.442(Rel11)v11.6.0.pdf |
+
+### 10.9.82 TS 32.446 Telecommunication management; Trace management integration reference point (IRP); Solution set (SS) definitions
+
+This document specifies solution set definitions for the IRP whose semantics is specified in Trace management IRP: Information service (TS 32.442).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 446 | 11.5.0 | Published | 2013-02-01 | http://www.etsi.org/deliver/etsi_ts/132400_132499/132446/11.05.00_60/ts_132446v110500p.pdf |
+| ATIS | ATIS.3GPP.32.446V1150-2014 | 11.5.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.446(R11-11.5.0) | 11.5.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.446(R11-11.5.0) |
+| TTC | TS-3GA-32.446(Rel11)v11.5.0 | 11.5.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.446(Rel11)v11.5.0.pdf |
+
+### 10.9.83 TS 32.455 Telecommunication management; Key performance indicators (KPI) for the evolved packet core (EPC): Definitions
+
+This document specifies key performance indicators (KPIs) for the EPC.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 455 | 11.0.0 | Published | 2012-10-31 | http://www.etsi.org/deliver/etsi_ts/132400_132499/132455/11.00.00_60/ts_132455v110000p.pdf |
+| ATIS | ATIS.3GPP.32.455V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.455(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.455(R11-11.0.0) |
+| TTC | TS-3GA-32.455(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.455(Rel11)v11.0.0.pdf |
+
+### 10.9.84 TS 32.501 Telecommunication management; Self-Configuration of Network elements; Concepts and integration reference point (IRP): Requirements
+
+This document describes the concepts how self-configuration works and what IRP requirements need to be met to support this functionality. The document also captures if a requirement shall be met via the Itf-N interface or via other protocols. This version of the TS is restricted to self-configuration of eNBs. The requirements in this document are not imposed on HNBs.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 501 | 11.0.0 | Published | 2012-09-28 | http://www.etsi.org/deliver/etsi_ts/132500_132599/132501/11.00.00_60/ts_132501v110000p.pdf |
+| ATIS | ATIS.3GPP.32.501V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.501(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.501(R11-11.0.0) |
+| TTC | TS-3GA-32.501(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.501(Rel11)v11.0.0.pdf |
+
+### 10.9.85 TS 32.502 Telecommunication management; Self-configuration of network elements integration reference point (IRP); Information service (IS)
+
+This document defines the information service (IS) part of the self-configuration IRP (SCIRP). It describes the semantics of the information and the interactions visible across Itf-N in a protocol independent way. The information is specified by means of Information object classes (IOCs) and the interactions by means of operations and notifications. The present document does not specify the syntax (encoding) of the information.
+
+The scope of this version of the TS is restricted to self-configuration of eNBs.
+
+The document also describes how already defined Itf-N functionalities are used in the context of self-configuration.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 502 | 11.0.0 | Published | 2012-10-31 | http://www.etsi.org/deliver/etsi_ts/132500_132599/132502/11.00.00_60/ts_132502v110000p.pdf |
+| ATIS | ATIS.3GPP.32.502V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.502(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.502(R11-11.0.0) |
+| TTC | TS-3GA-32.502(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.502(Rel11)v11.0.0.pdf |
+
+### 10.9.86 TS 32.506 Telecommunication management; Self-configuration of network elements integration reference point (IRP); Solution set (SS) definitions
+
+This document specifies Solution Set definitions for the IRP whose semantics are specified in self-configuration of network elements integration reference point (IRP): Information service (TS 32.502).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 506 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/132500_132599/132506/11.00.00_60/ts_132506v110000p.pdf |
+| ATIS | ATIS.3GPP.32.506V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.506(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.506(R11-11.0.0) |
+| TTC | TS-3GA-32.506(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.506(Rel11)v11.0.0.pdf |
+
+### 10.9.87 TS 32.531 Telecommunication management; Software management (SWM); Concepts and integration reference point (IRP) requirements
+
+This document describes the concepts how SWM of NEs works and what IRP requirements need to be met to support this functionality.
+
+The present document focuses on automated software management of eNBs.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 531 | 11.0.0 | Published | 2012-09-28 | http://www.etsi.org/deliver/etsi_ts/132500_132599/132531/11.00.00_60/ts_132531v110000p.pdf |
+| ATIS | ATIS.3GPP.32.531V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.531(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.531(R11-11.0.0) |
+| TTC | TS-3GA-32.531(Rel11)v11.1.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.531(Rel11)v11.0.0.pdf |
+
+### 10.9.88 TS 32.532 Telecommunication management; Software management integration reference point (IRP); Information service (IS)
+
+The document contains the software management interface IRP information services descriptions.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 532 | 11.0.0 | Published | 2012-09-28 | http://www.etsi.org/deliver/etsi_ts/132500_132599/132532/11.00.00_60/ts_132532v110000p.pdf |
+| ATIS | ATIS.3GPP.32.532V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.532(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.532(R11-11.0.0) |
+| TTC | TS-3GA-32.532(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.532(Rel11)v11.0.0.pdf |
+
+### 10.9.89 TS 32.536 Telecommunication management; Software management integration reference point (IRP); Solution set (SS) definitions
+
+This document specifies solution set definitions for the IRP whose semantics are specified in software management IRP information service (TS 32.532).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 536 | 11.0.0 | Published | 2012-09-28 | http://www.etsi.org/deliver/etsi_ts/132500_132599/132536/11.00.00_60/ts_132536v110000p.pdf |
+| ATIS | ATIS.3GPP.32.536V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.536(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.536(R11-11.0.0) |
+| TTC | TS-3GA-32.536(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.536(Rel11)v11.0.0.pdf |
+
+### 10.9.90 TS 32.551 Telecommunication management; Energy saving management (ESM); Concepts and requirements
+
+This document describes concepts and requirements for managing energy savings. It also describes if a requirement shall be met via the Itf-N interface or via other means.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 551 | 11.3.1 | Published | 2013-07-11 | http://www.etsi.org/deliver/etsi_ts/132500_132599/132551/11.03.01_60/ts_132551v110301p.pdf |
+| ATIS | ATIS.3GPP.32.551V1130-2014 | 11.3.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.551(R11-11.3.0) | 11.3.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.551(R11-11.3.0) |
+| TTC | TS-3GA-32.551(Rel11)v11.3.0 | 11.3.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.551(Rel11)v11.3.0.pdf |
+
+### 10.9.91 TS 32.600 Telecommunication management; Configuration management (CM); Concept and high-level requirements
+
+This document describes configuration management (CM) aspects of managing a PLMN. This is described from the management perspective in TS 32.101 and TS 32.102.
+
+The document defines a set of controls to be employed to effect set-up and changes to a PLMN network in such a way that operational capability and quality of service (QoS), network integrity and system interworking are ensured. In this way, this document describes the interface definition and behaviour for the management of relevant NEs in the context of the described management environment. The context is described for both the management system (OS) and network element (NE) functionality.
+
+The Itf N for CM is built up by a number of integration reference points (IRPs) and a related name convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in TS 32.150. For CM, a number of IRPs (and a Name Convention TS 32.300) are defined, used by this as well as by other specifications for Telecom Management produced by 3GPP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 600 | 11.0.0 | Published | 2012-10-31 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132600/11.00.00_60/ts_132600v110000p.pdf |
+| ATIS | ATIS.3GPP.32.600V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.600(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.600(R11-11.0.0) |
+| TTC | TS-3GA-32.600(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.600(Rel11)v11.0.0.pdf |
+
+### 10.9.92 TS 32.601 Telecommunication management; Configuration management (CM); Basic CM integration reference point (IRP): Requirements
+
+The document defines, in addition to the requirements defined in TS 32.101, TS 32.102 and TS 32.600, the requirements for the present IRP: Basic configuration management IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 601 | 11.0.0 | Published | 2012-10-31 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132601/11.00.00_60/ts_132601v110000p.pdf |
+| ATIS | ATIS.3GPP.32.601V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.601(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.601(R11-11.0.0) |
+| TTC | TS-3GA-32.601(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.601(Rel11)v11.0.0.pdf |
+
+### 10.9.93 TS 32.602 Telecommunication management; Configuration management; Basic CM integration reference point (IRP) information service
+
+The document defines a component of an integration reference point (IRP) through which an 'IRPAgent' (typically an element manager or network element) can communicate basic configuration management-related information to one or several 'IRPManagers' (typically network managers).
+
+This version of the IRP is mainly intended for "passive management" of high-level network configuration and status information as required by a network manager.
+
+The configuration management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs – as described in the introduction clause. An important aspect of such a split is that the network resource models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP information service. The Basic CM IRP: IS defined herein provides one such information service.
+
+The basic CM IRP: IS defined in the document has the following main purpose: to define an interface for retrieval of configuration management information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 602 | 11.2.0 | Published | 2013-04-18 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132602/11_02_00_60/ts_132602v110200p.pdf |
+| ATIS | ATIS.3GPP.32.602V1120-2014 | 11.2.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.602(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.602(R11-11.2.0) |
+| TTC | TS-3GA-32.602(Rel11)v11.2.0 | 11.2.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.602(Rel11)v11.2.0.pdf |
+
+#### **10.9.94 TS 32.606 Telecommunication management; Configuration management (CM); Basic CM integration reference point (IRP); Solution set (SS) definitions**
+
+The purpose of this document is to define the mapping of the basic CM IRP: IS (TS 32.602) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment and in a SOAP/WSDL environment.
+
+This document defines NRM independent data types and methods.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 606 | 11.0.0 | Published | 2012-10-16 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132606/11_00_00_60/ts_132606v110000p.pdf |
+| ATIS | ATIS.3GPP.32.606V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.606(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.606(R11-11.0.0) |
+| TTC | TS-3GA-32.606(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.606(Rel11)v11.0.0.pdf |
+
+#### **10.9.95 TS 32.611 Telecommunication management; 3G configuration management (CM); Bulk CM integration reference point (IRP): Requirements**
+
+The document describes the bulk configuration management (CM) requirements for managing a 3G network. This is described from the management perspective in TS 32.101 and TS 32.102.
+
+The ItfN for CM is built up by a number of integration reference points (IRPs) and a related name convention TS 32.300, which realize the functional capabilities over this interface. The basic structure of the IRPs is defined in TS 32.101 and TS 32.102. For CM, a number of IRPs (and a name convention) are defined, used by this as well as by other specifications for telecom management. These IRPs are defined in separate specifications. This document defines the requirements for the bulk CM IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 611 | 11.0.0 | Published | 2012-10-31 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132611/11.00.00_60/ts_132611v110000p.pdf |
+| ATIS | ATIS.3GPP.32.611V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.611(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttastddesc.jsp?stdno=TTAT.3G-32.611(R11-11.0.0) |
+| TTC | TS-3GA-32.611(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.611(Rel11)v11.0.0.pdf |
+
+### 10.9.96 TS 32.612 Telecommunication management; 3G configuration management (CM); Bulk CM integration reference point (IRP): Information service
+
+The document (bulk configuration management IRP: Information service) defines an integration reference point (IRP) through which an 'IRPAgent' (typically an element manager or network element) can communicate bulk configuration management related information to one or several 'IRPManagers' (typically network managers).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 612 | 11.0.0 | Published | 2012-10-31 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132612/11.00.00_60/ts_132612v110000p.pdf |
+| ATIS | ATIS.3GPP.32.612V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.612(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttastddesc.jsp?stdno=TTAT.3G-32.612(R11-11.0.0) |
+| TTC | TS-3GA-32.612(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.612(Rel11)v11.0.0.pdf |
+
+### 10.9.97 TS 32.616 Telecommunication management; Configuration management (CM); Bulk CM integration reference point (IRP); Solution set (SS) definitions
+
+This document specifies Solution Sets for the IRP whose semantics are specified in Bulk CM IRP: Information Service (TS 32.612).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 616 | 11.1.0 | Published | 2014-01-20 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132616/11.01.00_60/ts_132616v110100p.pdf |
+| ATIS | ATIS.3GPP.32.616V1100-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.616(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttastddesc.jsp?stdno=TTAT.3G-32.616(R11-11.0.0) |
+| TTC | TS-3GA-32.616(Rel11)v11.1.0 | 11.1.0 | TTC Approved | 2014-03-20 | http://www.ttc.or.jp/jp/document_list/free/3gpps2014/TS/TS-3GA-32.616(Rel11)v11.1.0.pdf |
+
+**10.9.98 TS 32.621 Telecommunication management; Configuration management (CM); Generic network resources integration reference point (IRP): Requirements**
+
+The document defines, in addition to the requirements defined in TS 32.101, TS 32.102 and TS 32.600, the requirements for the present IRP: Generic network resources IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 621 | 11.0.0 | Published | 2012-10-31 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132621/11.00.00_60/ts_132621v110000p.pdf |
+| ATIS | ATIS.3GPP.32.621V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.621(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.621(R11-11.0.0) |
+| TTC | TS-3GA-32.621(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.621(Rel11)v11.0.0.pdf |
+
+**10.9.99 TS 32.622 Telecommunication management; Configuration management (CM); Generic network resources IRP; Network resource model (NRM)**
+
+The document (generic network resources IRP: Network resource model) defines an integration reference point (IRP) through which an 'IRPAgent' (typically an element manager or network element) can communicate network management-related information to one or several 'IRPManagers' (typically network managers).
+
+The document specifies a generic network resource model (NRM) (also referred to as a management information model – MIM) with definitions of managed object classes.
+
+The configuration management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs. In addition to the subject IRP, it is expected that IRPs will be defined for functional areas like security management, software management, network & service provisioning, etc. An important aspect of such a split is that the network resource models (NRMs) defined in different IRPs are consistent. The generic network resources IRP here provides a base for all resource modelling.
+
+The generic network resources IRP main purpose is to define a generic network resource model that constitutes a base from which other (more specialized) resource models can inherit or have associations with.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 622 | 11.1.0 | Published | 2013-07-11 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132622/11.01.00_60/ts_132622v110100p.pdf |
+| ATIS | ATIS.3GPP.32.622V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.622(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.622(R11-11.0.0) |
+| TTC | TS-3GA-32.622(Rel11)v11.1.0 | 11.1.0 | TTC Approved | 2013-08-30 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.622(Rel11)v11.1.0.pdf |
+
+### 10.9.100 TS 32.626 Telecommunication management; Configuration Management (CM); Generic network resources integration reference point (IRP); Solution set (SS) definitions
+
+The TS 32.62x-series (generic network resources IRP) defines an integration reference point (IRP) through which an "IRP Agent" (typically an element manager or network element) can communicate network management related information to one or several "IRP Managers" (typically network managers).
+
+This TS-family specifies a generic network resource model, NRM (also referred to as a management information model – MIM) with definitions of information object classes (IOCs) and managed object classes (MOCs).
+
+This document specifies the solution sets for the generic NRM IRP.
+
+These solution set specifications are related to TS 32.622.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 626 | 11.2.0 | Published | 2013-10-04 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132626/11_02.00_60/ts_132626v110200p.pdf |
+| ATIS | ATIS.3GPP.32.626V1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.626(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.626(R11-11.1.0) |
+| TTC | TS-3GA-32.626(Rel11)v11.2.0 | 11.2.0 | TTC Approved | 2013-11-22 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.626(Rel11)v11.2.0.pdf |
+
+### 10.9.101 TS 32.631 Telecommunication management; Configuration management (CM); Core network resources IRP: Requirements
+
+The document defines, in addition to the requirements defined in TS 32.101, TS 32.102 and TS 32.600, the requirements for the present IRP: Core network resources IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 631 | 11.0.0 | Published | 2012-10-31 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132631/11_00.00_60/ts_132631v110000p.pdf |
+| ATIS | ATIS.3GPP.32.631V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.631(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.631(R11-11.0.0) |
+| TTC | TS-3GA-32.631(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.631(Rel11)v11.0.0.pdf |
+
+### 10.9.102 TS 32.632 Telecommunication management; Configuration management; Core network resources IRP: Network resource model (NRM)
+
+The document is part of an integration reference point (IRP) named "Core Network Resources IRP", through which an 'IRP Agent' (typically an element manager or network element) can communicate configuration management information to one or several 'IRP Managers' (typically network managers) concerning CN resources. This version of the IRP is mainly intended for
+
+"passive management" of high-level network configuration and status information as required by a network manager. The "Core Network Resources IRP" comprises a set of specifications defining Requirements, a protocol-neutral network resource model (NRM) and corresponding solution set(s).
+
+The document specifies the protocol-neutral core network resources IRP: Network resource model. It reuses relevant parts of the generic NRM in TS 32.622, either by direct reuse or subclassing, and in addition to that defines CN-specific managed object classes.
+
+The configuration management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs – as described in the Introduction clause. An important aspect of such a split is that the network resource models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRP Agent implementation can be accessed as one coherent model through one IRP information service.
+
+The document has the following main purpose: to define the applied CN-specific network resource model, based on the generic NRM in TS 32.622.
+
+Finally, in order to access the information defined by this NRM, an IRP information service (IS) is needed, such as the basic CM IRP: IS TS 32.602. However, which information service that is applicable is outside the scope of this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 632 | 11.0.0 | Published | 2012-10-31 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132632/11.00.00_60/ts_132632v110000p.pdf |
+| ATIS | ATIS.3GPP.32.632V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.632(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttastddesc.jsp?stdno=TTAT.3G-32.632(R11-11.0.0) |
+| TTC | TS-3GA-32.632(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.632(Rel11)v11.0.0.pdf |
+
+### 10.9.103 TS 32.636 Telecommunication management; Configuration management (CM); Core network resources integration reference point (IRP); Solution set (SS) definitions
+
+The purpose of this document is to define the mapping of the IRP information model (see TS 32.632) to protocol specific details necessary for implementation of this IRP in a specific solution set environment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 636 | 11.0.0 | Published | 2012-10-18 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132636/11.00.00_60/ts_132636v110000p.pdf |
+| ATIS | ATIS.3GPP.32.636V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.636(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttastddesc.jsp?stdno=TTAT.3G-32.636(R11-11.0.0) |
+| TTC | TS-3GA-32.636(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.636(Rel11)v11.0.0.pdf |
+
+**10.9.104 TS 32.646 Telecommunication management; Configuration management (CM); UTRAN network resources integration reference point (IRP); Solution set (SS) definitions**
+
+This document specifies solution sets for the UTRAN NRM IRP.
+
+This solution set specification is related to TS 32.642.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 646 | 11.2.0 | Published | 2013-02-01 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132646/11.02.00_60/ts_132646v110200p.pdf |
+| ATIS | ATIS.3GPP.32.646V1120-2014 | 11.2.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.646(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.646(R11-11.2.0) |
+| TTC | TS-3GA-32.646(Rel11)v11.2.0 | 11.2.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.646(Rel11)v11.2.0.pdf |
+
+**10.9.105 TS 32.656 Telecommunication management; Configuration management (CM); GERAN network resources Integration reference point (IRP); Solution set (SS) definitions**
+
+This document specifies Solution Sets for the GERAN NRM IRP.
+
+This Solution Set specification is related to TS 32.652.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 656 | 11.2.0 | Published | 2013-04-18 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132656/11.02.00_60/ts_132656v110200p.pdf |
+| ATIS | ATIS.3GPP.32.656V1120-2014 | 11.2.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.656(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.656(R11-11.2.0) |
+| TTC | TS-3GA-32.656(Rel11)v11.2.0 | 11.2.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.656(Rel11)v11.2.0.pdf |
+
+**10.9.106 TS 32.661 Telecommunication management; Configuration management (CM); Kernel CM; Requirements**
+
+This document defines, in addition to the requirements defined in 3G TS 32.101, 3G TS 32.102, and 3G TS 32.600, the requirements for the present IRP: Kernel configuration management IRP. It is the intent of Kernel configuration management to provide an IRP that contains the configuration management functionality that is basic and minimal. It is the functionality that is common to and required by both basic CM and bulk CM. While neither the basic CM IRP nor bulk CM IRP requires the other, they each require the Kernel CM IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 661 | 11.0.0 | Published | 2012-10-31 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132661/11.00.00_60/ts_132661v110000p.pdf |
+| ATIS | ATIS.3GPP.32.661V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.661(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.661(R11-11.0.0) |
+| TTC | TS-3GA-32.661(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.661(Rel11)v11.0.0.pdf |
+
+#### 10.9.107 TS 32.662 Telecommunication management; Configuration management (CM); Kernel CM; Information service
+
+This document defines integration reference point (IRP) through which an 'IRP Agent' (typically an element manager or network element) can communicate configuration management-related information to one or several 'IRP Managers' (typically network managers).
+
+The function of this Kernel CM IRP information service is to define an interface that provides the essential CM services. While it is not expected that the Kernel CM IRP alone will provide adequate CM capability, the Kernel CM IRP is expected to provide the common supporting capability required for other IRPs such as the basic CM IRP or the bulk CM IRP, each of which requires the Kernel CM IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 662 | 11.1.0 | Published | 2013-02-01 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132662/11.01.00_60/ts_132662v110100p.pdf |
+| ATIS | ATIS.3GPP.32.662V1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.662(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.662(R11-11.1.0) |
+| TTC | TS-3GA-32.662(Rel11)v11.1.0 | 11.1.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.662(Rel11)v11.1.0.pdf |
+
+#### 10.9.108 TS 32.666 Telecommunication management; Configuration management (CM); Kernel CM integration reference point (IRP); Solution set (SS) definitions
+
+This document specifies Solution Set definitions for the IRP whose semantics is specified in Kernel CM (configuration management) IRP: Information Service TS 32.662.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 666 | 11.0.0 | Published | 2012-10-18 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132666/11.00.00_60/ts_132666v110000p.pdf |
+| ATIS | ATIS.3GPP.32.666V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.666(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.666(R11-11.0.0) |
+| TTC | TS-3GA-32.666(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.666(Rel11)v11.0.0.pdf |
+
+#### **10.9.109 TS 32.671 Telecommunication management; Configuration management (CM); State management integration reference point (IRP): Requirements**
+
+This document defines, in addition to the requirements defined in 3G TS 32.101, 3G TS 32.102 and 3G TS 32.600, the requirements for the present IRP: State management.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 671 | 11.0.0 | Published | 2012-11-06 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132671/11.00.00_60/ts_132671v110000p.pdf |
+| ATIS | ATIS.3GPP.32.671V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.671(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.671(R11-11.0.0) |
+| TTC | TS-3GA-32.671(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.671(Rel11)v11.0.0.pdf |
+
+#### **10.9.110 TS 32.672 Telecommunication management; Configuration management (CM); State management integration reference point (IRP): Information service**
+
+This document defines the information service (IS) part of the state management IRP. It specifies the semantics of the network resource state and status information visible across the Itf-N. It also specifies the interaction required for the management of the state and status information.
+
+The state and status attributes specified in this document shall be used, where applicable, as attributes in information object class (IOC) definitions of other 3G IRPs. When used by the IOC definition, the semantics of the state and status attributes can be qualified and enhanced, if deemed necessary.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 672 | 11.0.0 | Published | 2012-11-06 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132672/11.00.00_60/ts_132672v110000p.pdf |
+| ATIS | ATIS.3GPP.32.672V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.672(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.672(R11-11.0.0) |
+| TTC | TS-3GA-32.672(Re11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.672(Re11)v11.0.0.pdf |
+
+### 10.9.111 TS 32.676 Telecommunication management; Configuration management (CM); State management integration reference point (IRP); Solution set (SS) definitions
+
+This document specifies solution set (SS) definitions for the IRP whose semantics is specified in State Management IRP: Information service (IS) (TS 32.672).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 676 | 11.0.0 | Published | 2012-10-18 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132676/11.00.00_60/ts_132676v110000p.pdf |
+| ATIS | ATIS.3GPP.32.676V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.676(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.676(R11-11.0.0) |
+| TTC | TS-3GA-32.676(Re11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.676(Re11)v11.0.0.pdf |
+
+### 10.9.112 TS 32.690 Telecommunication management; Inventory management (IM): Requirements
+
+The document defines the requirements for the present IRP: Inventory management IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 690 | 11.0.0 | Published | 2012-09-28 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132690/11.00.00_60/ts_132690v110000p.pdf |
+| ATIS | ATIS.3GPP.32.690V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.690(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.690(R11-11.0.0) |
+| TTC | TS-3GA-32.690(Re11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.690(Re11)v11.0.0.pdf |
+
+### 10.9.113 TS 32.691 Telecommunication management; Inventory management network resources integration reference point (IRP): Requirements
+
+This document defines, in addition to the requirements defined in 3G TS 32.101, 3G TS 32.102 and 3G TS 32.600, the requirements for the present IRP: Inventory management network resources IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 691 | 11.0.0 | Published | 2012-11-06 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132691/11.00.00/60/ts_132691v110000p.pdf |
+| ATIS | ATIS.3GPP.32.691V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.691(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.691(R11-11.0.0) |
+| TTC | TS-3GA-32.691(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.691(Rel11)v11.0.0.pdf |
+
+### 10.9.114 TS 32.692 Telecommunication management; Inventory management network resources integration reference point (IRP): Network resource model
+
+This document defines an integration reference point (IRP) through which an 'IRP Agent' (typically an element manager or network element) can communicate network management-related information to one or several 'IRP Managers' (typically network managers).
+
+This document specifies an inventory management network resource model (NRM) (also referred to as a management information model – MIM) with definitions of information object classes.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 692 | 11.0.0 | Published | 2012-09-28 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132692/11.00.00/60/ts_132692v110000p.pdf |
+| ATIS | ATIS.3GPP.32.692V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.692(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.692(R11-11.0.0) |
+| TTC | TS-3GA-32.692(Rel11)v11.1.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.692(Rel11)v11.0.0.pdf |
+
+### 10.9.115 TS 32.696 Telecommunication management; inventory management (IM) network resource model (NRM) integration reference point (IRP); Solution set (SS) definitions
+
+This document provides the NRM-specific part related to the inventory management NRM IRP IS in TS 32.692 of solution set definitions.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 696 | 11.1.0 | Published | 2013-02-01 | http://www.etsi.org/deliver/etsi_ts/132600_132699/132696/11_01_00_60/ts_132696v110100p.pdf |
+| ATIS | ATIS.3GPP.32.696V1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.696(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.696(R11-11.1.0) |
+| TTC | TS-3GA-32.696(Rel11)v11.1.0 | 11.1.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.696(Rel11)v11.1.0.pdf |
+
+**10.9.116 TS 32.711 Telecommunication management; Configuration management (CM); Transport network (TN) interface network resource model (NRM) integration reference point (IRP): Requirements**
+
+The document defines the requirements for the present IRP: Transport network (TN) interface network resource model (NRM) integration reference point.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 711 | 11.0.0 | Published | 2012-11-06 | http://www.etsi.org/deliver/etsi_ts/132700_132799/132711/11_00_00_60/ts_132711v110000p.pdf |
+| ATIS | ATIS.3GPP.32.711V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.711(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.711(R11-11.0.0) |
+| TTC | TS-3GA-32.711(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.711(Rel11)v11.0.0.pdf |
+
+**10.9.117 TS 32.712 Telecommunication management; Configuration management (CM); Transport network (TN) interface network resource model (NRM) integration reference point (IRP): Information service (IS)**
+
+This document is part of an integration reference point (IRP) named "Transport Network (TN) interface network resource model (NRM) IRP", through which an "IRPAgent" (typically an element manager or network element) can communicate configuration management information to one or several "IRPManagers" (typically network managers) concerning transport resources. The "Transport Network (TN) Interface Network Resource Model (NRM) IRP" comprises a set of specifications defining requirements, a protocol-neutral network resource model (NRM) and corresponding solution set(s).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 712 | 11.1.0 | Published | 2013-10-04 | http://www.etsi.org/deliver/etsi_ts/132700_132799/132712/11_01_00_60/ts_132712v110100p.pdf |
+| ATIS | ATIS.3GPP.32.712V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.712(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.712(R11-11.0.0) |
+| TTC | TS-3GA-32.712(Rel11)v11.1.0 | 11.1.0 | TTC Approved | 2013-11-22 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.712(Rel11)v11.1.0.pdf |
+
+**10.9.118 TS 32.716 Telecommunication management; Configuration management (CM); Transport network (TN) interface network resource model (NRM) Integration Reference Point (IRP); Solution set (SS) definitions**
+
+This document is part of an integration reference point (IRP) named transport network (TN) interface network resource model (NRM) IRP, through which an IRP Agent can communicate configuration management information to one or several IRP Managers concerning TN resources. The TN NRM IRP comprises a set of specifications defining requirements, a protocol neutral information service and one or more solution set(s).
+
+The document specifies solution sets for the TN NRM IRP. It is related to TS 32.712.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 716 | 11.0.0 | Published | 2012-10-18 | http://www.etsi.org/deliver/etsi_ts/132700_132799/132716/11_00_00_60/ts_132716v110000p.pdf |
+| ATIS | ATIS.3GPP.32.716V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.716(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.716(R11-11.0.0) |
+| TTC | TS-3GA-32.716(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.716(Rel11)v11.0.0.pdf |
+
+**10.9.119 TS 32.721 Telecommunication management; Configuration management (CM); Repeater network resources integration reference point (IRP): Requirements**
+
+This document defines, in addition to the requirements defined in 3GPP TS 32.101, 3GPP TS 32.102 and 3GPP TS 32.600, the requirements for the present repeater network resources IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 721 | 11.0.0 | Published | 2012-11-06 | http://www.etsi.org/deliver/etsi_ts/132700_132799/132721/11.00.00_60/ts_132721v110000p.pdf |
+| ATIS | ATIS.3GPP.32.721V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.721(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.721(R11-11.0.0) |
+| TTC | TS-3GA-32.721(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.721(Rel11)v11.0.0.pdf |
+
+**10.9.120 TS 32.722 Telecommunication management; Configuration management (CM); Repeater network resources integration reference point (IRP): Information service (IS)**
+
+This document is part of an integration reference point (IRP) named "Repeater Network Resources IRP", through which an "IRPAgent" (typically an element manager or network element) can communicate configuration management information to one or several "IRPManagers" (typically network managers) concerning repeater resources. The "Repeater Network Resources IRP" comprises a set of specifications defining Requirements, a protocol neutral network resource model (NRM) and corresponding solution set(s).
+
+The document specifies the protocol neutral repeater network resources IRP: Network resource model. It reuses relevant parts of the generic NRM in TS 32.622 and TS 32.642, either by direct reuse or sub-classing, and in addition to that defines repeater specific information object classes.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 722 | 11.0.0 | Published | 2012-11-06 | http://www.etsi.org/deliver/etsi_ts/132700_132799/132722/11.00.00_60/ts_132722v110000p.pdf |
+| ATIS | ATIS.3GPP.32.722V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.722(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.722(R11-11.0.0) |
+| TTC | TS-3GA-32.722(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.722(Rel11)v11.0.0.pdf |
+
+**10.9.121 TS 32.726 Telecommunication management; Configuration management (CM); Repeater network resources integration reference point (IRP); Solution set (SS) definitions**
+
+This document specifies solution set definitions for the IRP whose semantics are specified in the repeater network resources IRP NRM information service (TS 32.722).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 726 | 11.0.0 | Published | 2012-10-18 | http://www.etsi.org/deliver/etsi_ts/132700_132799/132726/11.00.00_60/ts_132726v110000p.pdf |
+| ATIS | ATIS.3GPP.32.726V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.726(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.726(R11-11.0.0) |
+| TTC | TS-3GA-32.726(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.726(Rel11)v11.0.0.pdf |
+
+#### **10.9.122 TS 32.731 Telecommunication management; IP multimedia subsystem (IMS) network resource model (NRM) integration reference point (IRP): Requirements**
+
+This document defines, in addition to the requirements defined in 3GPP TS 32.101, 3GPP TS 32.102 and 3GPP TS 32.600, the requirements for the IMS network resource model (NRM) IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 731 | 11.0.0 | Published | 2012-11-06 | http://www.etsi.org/deliver/etsi_ts/132700_132799/132731/11.00.00_60/ts_132731v110000p.pdf |
+| ATIS | ATIS.3GPP.32.731V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.731(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.731(R11-11.0.0) |
+| TTC | TS-3GA-32.731(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.731(Rel11)v11.0.0.pdf |
+
+#### **10.9.123 TS 32.732 Telecommunication management; IP multimedia subsystem (IMS) network resource model (NRM) integration reference point (IRP): Information service (IS)**
+
+This document is part of an integration reference point (IRP) named IMS network resource model (NRM) IRP, through which an IRP Agent can communicate configuration management information to one or several IRP Managers concerning IMS resources. The IMS NRM IRP comprises a set of specifications defining Requirements, a protocol neutral information service and one or more solution set(s).
+
+The document specifies the protocol neutral IMS NRM IRP: Information service (IS). It reuses relevant parts of the generic NRM IRP: IS in 3GPP TS 32.622, either by direct reuse or subclassing, and in addition to that defines IMS-specific information object classes.
+
+Finally, in order to access the information defined by this NRM, an interface IRP is needed, such as the basic CM IRP in 3GPP TS 32.602. However, which interface IRP is applicable is outside the scope of the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 732 | 11.0.0 | Published | 2012-11-19 | http://www.etsi.org/deliver/etsi_ts/132700_132799/132732/11.00.00_60/ts_132732v110000p.pdf |
+| ATIS | ATIS.3GPP.32.732V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.732(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.732(R11-11.0.0) |
+| TTC | TS-3GA-32.732(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.732(Rel11)v11.0.0.pdf |
+
+**10.9.124 TS 32.741 Telecommunication management; Configuration management (CM); Signalling transport network (STN) interface network resource model (NRM) integration reference point (IRP): Requirements**
+
+The document defines the requirements for the signalling transport network (STN) interface NRM IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 741 | 11.0.0 | Published | 2012-11-06 | http://www.etsi.org/deliver/etsi_ts/132700_132799/132741/11.00.00_60/ts_132741v110000p.pdf |
+| ATIS | ATIS.3GPP.32.741V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.741(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.741(R11-11.0.0) |
+| TTC | TS-3GA-32.741(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.741(Rel11)v11.0.0.pdf |
+
+**10.9.125 TS 32.742 Telecommunication management; Configuration management (CM); Signalling transport network (STN) interface network resource model (NRM) integration reference point (IRP): Information service (IS)**
+
+This document is part of an integration reference point (IRP) named "Signalling Transport Network (STN) network resources IRP", through which an "IRPAgent" (typically an element manager or network element) can communicate configuration management information to one or several "IRPManagers" (typically network managers) concerning signalling transport resources. The "Signalling Transport Network (STN) network resources IRP" comprises a set of specifications defining Requirements, a protocol-neutral network resource model (NRM) and corresponding solution set(s).
+
+The document specifies the protocol-neutral STN resources IRP: Network resource model.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 742 | 11.0.0 | Published | 2012-11-06 | http://www.etsi.org/deliver/etsi_ts/132700_132799/132742/11.00.00_60/ts_132742v110000p.pdf |
+| ATIS | ATIS.3GPP.32.742V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.742(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.742(R11-11.0.0) |
+| TTC | TS-3GA-32.742(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.742(Rel11)v11.0.0.pdf |
+
+#### **10.9.126 TS 32.751 Telecommunication management; Evolved packet core (EPC) Network resource model (NRM) integration reference point (IRP); Requirements**
+
+The document defines, in addition to the requirements defined in 3GPP TS 32.101, TS 32.102 and TS 32.600, the requirements for the EPC network resource model (NRM) IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 751 | 11.0.0 | Published | 2012-11-06 | http://www.etsi.org/deliver/etsi_ts/132700_132799/132751/11.00.00_60/ts_132751v110000p.pdf |
+| ATIS | ATIS.3GPP.32.751V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.751(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-32.751(R11-11.0.0) |
+| TTC | TS-3GA-32.751(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.751(Rel11)v11.0.0.pdf |
+
+#### **10.9.127 TS 32.752 Telecommunication management; Evolved packet core (EPC) Network resource model (NRM) integration reference point (IRP); Information service (IS)**
+
+This document specifies the protocol neutral EPC Network Resource Model IRP Information Service, through which an 'IRP Agent' (typically an Element Manager or Network Element) can communicate information to one or several 'IRP Managers' (typically Network Managers) concerning EPC resources. It reuses relevant parts of the Generic NRM in 3GPP TS 32.622, either by direct reuse or sub-classing, and in addition to that defines EPC specific information object classes.
+
+In order to access the information defined by this NRM, an Interface IRP such as the "Basic CM IRP" is needed (3GPP TS 32.602). However, which Interface IRP is applicable is outside the scope of the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 752 | 11.0.1 | Published | 2013-08-02 | http://www.etsi.org/deliver/etsi_ts/132700_132799/132752/11.00.01_60/ts_132752v110001p.pdf |
+| ATIS | ATIS.3GPP.32.752V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.752(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.752(R11-11.0.0) |
+| TTC | TS-3GA-32.752(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.752(Rel11)v11.0.0.pdf |
+
+#### 10.9.128 TS 32.756 Telecommunication management; Evolved packet core (EPC) network resource model (NRM) integration reference point (IRP); Solution set (SS) definitions
+
+The TS 32.75x-series (EPC NRM IRP) define an integration reference point (IRP) named EPC network resource model (NRM) IRP, through which an "IRPAgent" (typically an element manager or network element) can communicate network management related information to one or several "IRPManagers" (typically Network Managers).
+
+The present document provides solution set definitions for EPC Network Resources IRP, which define the mapping of the IRP information model (see TS 32.752) to the protocol specific details necessary for implementation of this IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 756 | 11.0.0 | Published | 2012-10-18 | http://www.etsi.org/deliver/etsi_ts/132700_132799/132756/11.00.00_60/ts_132756v110000p.pdf |
+| ATIS | ATIS.3GPP.32.756V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-32.756(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-32.756(R11-11.0.0) |
+| TTC | TS-3GA-32.756(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-32.756(Rel11)v11.0.0.pdf |
+
+#### 10.9.129 TR 32.901 Telecommunication management; Study on user data convergence (UDC) information model handling and provisioning: Example use cases
+
+3GPP TR 22.985 Service requirement for the UDC describes the architecture of the user data convergence, a concept that proposes to move the user data from where it has been distributed and siloed in network elements, applications, and other network resources to a single logical consolidated facility here called user data repository (UDR) where it can be accessed, stored and managed in a common way.
+
+The introduction of a user data convergence of user data for network services and management applications could significantly enhance the ability of 3GPP based networks to offer complex and combined services. User data can be decomposed and reformed by a common data model framework (e.g., tree-like data model, rational data model) provided by UDR. In that case, user data categorized by services can be regrouped and identified by user ID, leaving no data redundancy. Also, convergence in data model will unify the user data access interface and its protocol, which
+
+will promote new service application development. Thereby, the capability of user data convergence can be open to creation of data-less applications.
+
+Methods for data protection against access by unauthorized parties are outside the scope of this document.
+
+3GPP TS 32.181 UDC Framework for Model Handling and Management and 3GPP TS 29.335 UDC; User data repository access protocol over the Ud interface; Stage 3 provide various types of information and data models associated with the architecture of UDC. These include the common baseline information model (CBIM) (see 3GPP TS 32.182), the specialized information model (SpIM), application information models (AIMs), application data models (ADMs), and the consolidated data model (CDM) of the user data repository (UDR). Figure 1 from 3GPP TS 32.181 UDC framework for model handling and management shows the operational environment of the UDC.
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|-----------------------------|---------|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTC | TR-3GA-32.901(Rel11)v11.0.0 | 11.0.0 | TTC
Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TR/TR-3GA-32.901(Rel11)v11.0.0.pdf |
+
+## 10.10 33-series, Security aspects
+
+### 10.10.1 TS 33.102 3G security; Security architecture
+
+This specification defines the security architecture, i.e., the security features and the security mechanisms, for the third generation mobile telecommunication system.
+
+A security feature is a service capability that meets one or several security requirements. The complete set of security features addresses the security requirements as they are defined in "3G Security: Threats and Requirements" (TS 21.133) and implement the security objectives and principles described in TS 33.120. A security mechanism is an element that is used to realize a security feature. All security features and security mechanisms taken together form the security architecture.
+
+An example of a security feature is user data confidentiality. A security mechanism that may be used to implement that feature is a stream cipher using a derived cipher key.
+
+This specification defines 3G security procedures performed within 3G capable networks (R99+), i.e., intra-UMTS and UMTS-GSM. As an example, UMTS authentication is applicable to UMTS radio access as well as GSM radio access provided that the serving network node and the MS are UMTS capable. Interoperability with non-UMTS capable networks (R98-) is also covered.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.102 | 11.5.1 | ARIB
published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/33/A33102-b51.pdf |
+| ETSI | TS 133 102 | 11.6.0 | Published | 2014-03-24 | http://www.etsi.org/deliver/etsi_ts/133100_133199/133102/11.06.00_60/ts_133102v110600p.pdf |
+| ATIS | ATIS.3GPP.33.102V1150-2014 | 11.5.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.102(R11-115.0) | 11.5.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.102(R11-115.0) |
+
+### 10.10.2 TS 33.105 3G security; Cryptographic algorithm requirements
+
+This specification constitutes a requirements specification for the security functions which may be used to provide the network access security features defined in 3G TS 33.102.
+
+The specification covers the intended use of the functions, the technical requirements on the functions and the requirements as regards standardization.
+
+For those functions that require standardization, it also covers the intended use of the algorithm specification, the requirements on test data, and quality assurance requirements on both the algorithm and its documentation.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.105 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/33/A33105-b00.pdf |
+| ETSI | TS 133 105 | 11.0.0 | Published | 2012-11-09 | http://www.etsi.org/deliver/etsi_ts/133100_133199/133105/11.00.00_60/ts_133105v110000p.pdf |
+| ATIS | ATIS.3GPP.33.105V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.105(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.105(R11-11.0.0) |
+
+### 10.10.3 TS 33.106 Lawful interception requirements
+
+The document provides basic interception requirements within a third generation mobile communication system (3GMS).
+
+The specification describes the service requirements from a law enforcement point of view only. The aim of this document is to define a 3GMS interception system that supports a number of regional interception regulations, but these regulations are not repeated here as they vary. Regional interception requirements shall rely on this specification to derive such information, as they require.
+
+These interception requirements shall be used to derive specific network requirements.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.106 | 11.1.1 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/33/A33106-b11.pdf |
+| ATIS | ATIS.3GPP.33.106V1111-2014 | 11.1.1 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+
+### 10.10.4 TS 33.107 3G security; Lawful interception architecture and functions
+
+The document describes the architecture and functional requirements within a third generation mobile communication system (3GMS).
+
+The specification shows the service requirements from a law enforcement point of view only. The aim of this document is to define a 3GMS interception system that supports a number of regional interception regulations, but these regulations are not repeated here as they vary. Regional interception requirements shall be met in using specific (regional) mediation functions allowing only required information to be transported.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.107 | 11.3.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/33/A33107-b30.pdf |
+| ETSI | TS 133 107 | 11.3.0 | Published | 2012-10-02 | http://www.etsi.org/deliver/etsi_ts/133100_133199/133107/11.03.00_60/ts_133107v110300p.pdf |
+| ATIS | ATIS.3GPP.33.107V1130-2014 | 11.3.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.107(R11-11.3.0) | 11.3.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.107(R11-11.3.0) |
+
+#### 10.10.5 TS 33.108 3G security; Handover interface for lawful interception (LI)
+
+This specification addresses the handover interfaces for lawful interception of packet-data services, circuit-switched services, and multimedia services within the UMTS network. The handover interface in this context includes the delivery of intercept related information (HI2) and content of communication (HI3) to the law enforcement monitoring facility.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.108 | 11.4.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/33/A33108-b40.pdf |
+| ETSI | TS 133 108 | 11.4.0 | Published | 2012-10-02 | http://www.etsi.org/deliver/etsi_ts/133100_133199/133108/11.04.00_60/ts_133108v110400p.pdf |
+| ATIS | ATIS.3GPP.33.108V1140-2014 | 11.4.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.108(R11-11.4.0) | 11.4.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.108(R11-11.4.0) |
+
+#### 10.10.6 TS 33.110 Key establishment between a universal integrated circuit card (UICC) and a terminal
+
+This document describes the security features and mechanisms to provision a shared key between a UICC and a terminal that may host the UICC or be connected to the device hosting the UICC via a local interface. Candidate applications to use this key establishment mechanism include, but are not restricted to, secure channel between a UICC and a terminal [ETSI TS 102 484].
+
+The scope of this specification includes an architecture overview and the detailed procedure how to establish the shared key between the UICC and the terminal.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.110 | 11.0.1 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/33/A33110-b01.pdf |
+| ETSI | TS 133 110 | 11.0.1 | Published | 2012-11-19 | http://www.etsi.org/deliver/etsi_ts/133100_133199/133110/11.00.01_60/ts_133110v110001p.pdf |
+| ATIS | ATIS.3GPP.33.110V1101-2014 | 11.0.1 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.110(R11-11.0.1) | 11.0.1 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.110(R11-11.0.1) |
+
+### 10.10.7 TS 33.141 Presence service; Security
+
+This document is the Stage 2 specification for the security requirements, security architecture, security features and security mechanisms for the presence service, which includes the elements necessary to realize the requirements in 3G TS 22.141 and 3G TS 23.141. As far as SIP-based procedures are concerned, this specification refers to 3G TS 33.203. The main content of this specification is the security for the Ut reference point, which is HTTP based, as applied in presence services.
+
+The document includes information applicable to network operators, service providers and manufacturers.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.141 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/33/A33141-b00.pdf |
+| ETSI | TS 133 141 | 11.0.0 | Published | 2012-11-19 | http://www.etsi.org/deliver/etsi_ts/133100_133199/133141/11.00.00_60/ts_133141v110000p.pdf |
+| ATIS | ATIS.3GPP.33.141V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.141(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.141(R11-11.0.0) |
+
+### 10.10.8 TS 33.203 3G security; Access security for IP-based services
+
+The scope for this technical specification is to specify the security features and mechanisms for secure access to the IM subsystem (IMS) for the 3G mobile telecommunication system.
+
+The IMS in UMTS will support IP multimedia applications such as video, audio and multimedia conferences. Session initiation protocol (SIP [IETF RFC 3261]) has been chosen as the signalling protocol for creating and terminating multimedia sessions. This specification only deals with how the SIP signalling is protected between the subscriber and the IMS, how the subscriber is authenticated and how the subscriber authenticates the IMS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.203 | 11.2.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/33/A33203-b20.pdf |
+| ETSI | TS 133 203 | 11.2.0 | Published | 2012-11-19 | http://www.etsi.org/deliver/etsi_ts/133200_133299/133203/11.02.00_60/ts_133203v110200p.pdf |
+| ATIS | ATIS.3GPP.33.203V1120-2014 | 11.2.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.203(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.203(R11-11.2.0) |
+
+#### 10.10.9 TS 33.204 3G Security; Network domain security (NDS); Transaction capabilities application part (TCAP) user security
+
+This technical specification covers the security mechanisms and procedures necessary to protect all TCAP user messages which are sent between different security domains. The complete set of enhancements and extensions to facilitate security protection for the TCAP protocol is termed TCAPsec and it covers transport security in the TCAP protocol itself and the security management procedures.
+
+This technical specification contains the Stage 2 specification for security protection of the TCAP protocol. The actual implementation (Stage 3) specification can be found in TS 29.204.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 133 204 | 11.0.0 | Published | 2012-11-09 | http://www.etsi.org/deliver/etsi_ts/133200_133299/133204/11.00.00_60/ts_133204v110000p.pdf |
+| ATIS | ATIS.3GPP.33.204V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.204(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.204(R11-11.0.0) |
+| TTC | TS-3GA-33.204(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-33.204(Rel11)v11.0.0.pdf |
+
+#### 10.10.10 TS 33.210 3G security; Network domain security (NDS); IP network layer security
+
+This document defines the security architecture for the UMTS network domain IP-based control plane. The scope of the UMTS network domain control plane security is to cover the control signalling on selected interfaces between UMTS network elements.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.210 | 11.4.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/33/A33210-b40.pdf |
+| ETSI | TS 133 210 | 11.4.0 | Published | 2012-10-02 | http://www.etsi.org/deliver/etsi_ts/133200_133299/133210/11.04.00_60/ts_133210v110400p.pdf |
+| ATIS | ATIS.3GPP.33.210V1140-2014 | 11.4.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.210(R11-11.4.0) | 11.4.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.210(R11-11.4.0) |
+
+### 10.10.11 TS 33.220 Generic authentication architecture (GAA); Generic bootstrapping architecture
+
+This document describes the security features and a mechanism to bootstrap authentication and key agreement for application security from the 3GPP AKA mechanism. Candidate applications to use this bootstrapping mechanism include, but are not restricted to, subscriber certificate distribution 3GPP TS 33.221. Subscriber certificates support services whose provision mobile operator assists, as well as services that mobile operator provides.
+
+The scope of this specification includes a generic AKA bootstrapping function, an architecture overview and the detailed procedure how to bootstrap the credential.
+
+Clause 4 of this specification describes a mechanism, called GBA\_ME, to bootstrap authentication and key agreement, which does not require any changes to the UICC. Clause 5 of this specification describes a mechanism, called GBA\_U, to bootstrap authentication and key agreement, which does require changes to the UICC, but provides enhanced security by storing certain derived keys on the UICC.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.220 | 11.5.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/33/A33220-b50.pdf |
+| ETSI | TS 133 220 | 11.5.0 | Published | 2013-07-11 | http://www.etsi.org/deliver/etsi_ts/133200_133299/133220/11.05.00_60/ts_133220v110500p.pdf |
+| ATIS | ATIS.3GPP.33.220V1140-2014 | 11.4.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.220(R11-11.4.0) | 11.4.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.220(R11-11.4.0) |
+
+### 10.10.12 TS 33.221 Generic authentication architecture (GAA); Support for subscriber certificates
+
+This document describes subscriber certificate distribution by means of generic bootstrapping architecture (GBA) 3GPP TS 33.220. Subscriber certificates support services whose provision the mobile operator assists, as well as services that are offered by the mobile operator.
+
+The scope of this specification presents signalling procedures for support of issuing certificates to subscribers and the standard format of certificates and digital signatures. It is not intended to duplicate existing standards being developed by other groups on these topics, and will reference these where appropriate.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.221 | 11.1.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/33/A33221-b10.pdf |
+| ETSI | TS 133 221 | 11.1.0 | Published | 2014-01-22 | http://www.etsi.org/deliver/etsi_ts/133200_133299/133221/11.01.00_60/ts_133221v110100p.pdf |
+| ATIS | ATIS.3GPP.33.221V 1101-2014 | 11.0.1 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.221(R11-11.0.1) | 11.0.1 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-33.221(R11-11.0.1) |
+
+### 10.10.13 TS 33.222 Generic authentication architecture (GAA); Access to network application functions using hypertext transfer protocol over transport layer security (HTTPS)
+
+The document specifies secure access methods to network application functions (NAFs) using HTTP over TLS in the generic authentication architecture (GAA), and provides Stage 2 security requirements, principles and procedures for the access. The present document describes both direct access to an application server (AS) and access to an application server through an authentication proxy (AP).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.222 | 11.3.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/33/A33222-b30.pdf |
+| ETSI | TS 133 222 | 11.3.0 | Published | 2014-01-22 | http://www.etsi.org/deliver/etsi_ts/133200_133299/133222/11.03.00_60/ts_133222v110300p.pdf |
+| ATIS | ATIS.3GPP.33.222V 1122-2014 | 11.2.2 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.222(R11-11.2.2) | 11.2.2 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-33.222(R11-11.2.2) |
+
+### 10.10.14 TS 33.223 Generic authentication architecture (GAA); Generic bootstrapping architecture (GBA): Push function
+
+The present document specifies a push function as a functional add-on for the generic authentication architecture (GAA) described in 3GPP TS 33.220.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.223 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/33/A33223-b00.pdf |
+| ETSI | TS 133 223 | 11.0.0 | Published | 2012-10-02 | http://www.etsi.org/deliver/etsi_ts/133200_133299/133223/11.00.00/60/ts_133223v110000p.pdf |
+| ATIS | ATIS.3GPP.33.223V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.223(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.223(R11-11.0.0) |
+
+#### 10.10.15 TS 33.224 Generic authentication architecture (GAA); Generic bootstrapping architecture (GBA) Push Layer
+
+This document specifies a generic push layer that makes use of the GBA push function as specified in TS 33.223. The GPL specification includes a message format, cipher suites and processing model. GPL assumes that keys and other SA parameters have been preinstalled in the Push-NAF and UE in the form of a NAF SA. GPL is a protection protocol that can be applied in a unidirectional fashion.
+
+The rationale for GPL is that having each application specify its own security mechanisms would for obvious reasons lead to duplication of work, specifications and implementations. Using a generic secure push layer avoids these problems. A generic secure push layer may also relieve the applications using the service of having to be aware of inner working of the security layer. As an analogy, TS 33.222 can be mentioned, which provides a generic security layer for HTTP based applications.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 133 224 | 11.1.0 | Published | 2013-04-19 | http://www.etsi.org/deliver/etsi_ts/133200_133299/133224/11.01.00/60/ts_133224v110100p.pdf |
+| ATIS | ATIS.3GPP.33.224V1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.224(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.224(R11-11.1.0) |
+| TTC | TS-3GA-33.224(Rel11)v11.1.0 | 11.1.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TS/TS-3GA-33.224(Rel11)v11.1.0.pdf |
+
+#### 10.10.16 TS 33.234 3G Security; Wireless local area network (WLAN) interworking security
+
+This document specifies the security architecture, trust model and security requirements for the interworking of the 3GPP System and WLAN access networks.
+
+Specifications of the appropriate mechanisms for user and network authentication, key management, service authorization, confidentiality and integrity protection of user and signalling data are also provided.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.234 | 11.4.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/33/A33234-b40.pdf |
+| ETSI | TS 133 234 | 11.4.0 | Published | 2012-11-19 | http://www.etsi.org/deliver/etsi_ts/133200_133299/133234/11.04.00_60/ts_133234v110400p.pdf |
+| ATIS | ATIS.3GPP.33.234V 1140-2014 | 11.4.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.234(R11-11.4.0) | 11.4.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.234(R11-11.4.0) |
+
+#### 10.10.17 TS 33.246 3G security; Security of multimedia broadcast/multicast service
+
+The technical specification covers the security procedures of the multimedia broadcast/multicast service (MBMS) for 3GPP systems (UTRAN and GERAN). MBMS is a 3GPP system network bearer service over which many different applications could be carried. The actual method of protection may vary depending on the type of MBMS application.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.246 | 11.2.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/33/A33246-b20.pdf |
+| ETSI | TS 133 246 | 11.2.0 | Published | 2013-07-11 | http://www.etsi.org/deliver/etsi_ts/133200_133299/133246/11.02.00_60/ts_133246v110200p.pdf |
+| ATIS | ATIS.3GPP.33.246V 1110-2014 | 11.1.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.246(R11-11.1.0) | 11.1.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.246(R11-11.1.0) |
+
+#### 10.10.18 TS 33.259 Key establishment between a UICC hosting device and a remote device
+
+This document describes the security features and mechanisms to provision a shared key between a UICC hosting device and a remote device connected via a local interface. The shared secret is then intended to be used to secure the interface between the remote device and the UICC hosting device. Candidate applications to use this key establishment mechanism include, but are not restricted to personal network management (see TS 22.259).
+
+The scope of this Specification includes an architecture overview and the detailed procedure how to establish the shared key between the UICC hosting device and the remote device. This is different from Technical Specification TS 33.110 that describes an architecture overview and the detailed procedure how to establish the shared key between the UICC itself and the terminal hosting the UICC. The use cases utilizing the mechanisms described in this specification are seen to be different to the use cases where "Key establishment between a UICC and a terminal", IETF RFC 4279 is utilized.
+
+The solution described in this document is built on the existing infrastructure defined in "GBA", TS 33.220.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.259 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/33/A33259-b00.pdf |
+| ETSI | TS 133 259 | 11.0.0 | Published | 2012-10-02 | http://www.etsi.org/deliver/etsi_ts/133200_133299/133259/11.00.00_60/ts_133259v110000p.pdf |
+| ATIS | ATIS.3GPP.33.259V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.259(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.259(R11-11.0.0) |
+
+### 10.10.19 TS 33.310 Network domain security (NDS); Authentication framework (AF)
+
+For 3GPP systems, there is a need for truly scalable entity authentication framework (AF) since an increasing number of network elements and interfaces are covered by security mechanisms.
+
+This specification provides a highly scalable entity authentication framework for 3GPP network nodes. This framework is developed in the context of the network domain security work item, which effectively limits the scope to the control plane entities of the core network. Thus, *the Authentication Framework will provide entity authentication for the nodes that are using NDS/IP.*
+
+Feasible trust models (i.e., how CAs are organized) and their effects are provided. Additionally, requirements are presented for the used protocols and certificate profiles, to make it possible for operator IPsec and PKI implementations to interoperate.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.310 | 11.2.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/33/A33310-b20.pdf |
+| ETSI | TS 133 310 | 11.2.0 | Published | 2013-02-01 | http://www.etsi.org/deliver/etsi_ts/133300_133399/133310/11.02.00_60/ts_133310v110200p.pdf |
+| ATIS | ATIS.3GPP.33.310V1120-2014 | 11.2.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.310(R11-11.2.0) | 11.2.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.310(R11-11.2.0) |
+
+### 10.10.20 TS 33.401 3GPP system architecture evolution (SAE); Security architecture
+
+This document specifies the security architecture, i.e., the security features and the security mechanisms for the evolved packet system and the evolved packet core, and the security procedures performed within the evolved packet system (EPS) including the evolved packet core (EPC) and the evolved UTRAN (E-UTRAN).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.401 | 11.7.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/33/A33401-b70.pdf |
+| ETSI | TS 133 401 | 11.7.0 | Published | 2013-07-11 | http://www.etsi.org/deliver/etsi_ts/133400_133499/133401/11.07.00_60/ts_133401v110700p.pdf |
+| ATIS | ATIS.3GPP.33.401V1160-2014 | 11.6.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.401(R11-11.6.0) | 11.6.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.401(R11-11.6.0) |
+
+### 10.10.21 TS 33.402 3GPP system architecture evolution (SAE); Security aspects of non-3GPP accesses
+
+The present document specifies the security architecture, i.e., the security feature groups and the security mechanisms performed during inter working between non-3GPP accesses and the evolved packet system (EPS).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.402 | 11.4.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/33/A33402-b40.pdf |
+| ETSI | TS 133 402 | 11.4.0 | Published | 2012-11-19 | http://www.etsi.org/deliver/etsi_ts/133400_133499/133402/11.04.00_60/ts_133402v110400p.pdf |
+| ATIS | ATIS.3GPP.33.402V1140-2014 | 11.4.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.402(R11-11.4.0) | 11.4.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.402(R11-11.4.0) |
+
+### 10.10.22 TR 33.838 Study on protection against unsolicited communication for IMS (PUCI)
+
+The document studies more focussed the high-level solutions possibilities for PUCI described in the technical report (TR 33.937) on PUCI.
+
+The scope of the study includes:
+
+- Study of the PUCI related information:
+ - What information to be stored in the HSS.
+ - Type of PUCI information to be exchanged (e.g., scoring information, contextual information) and how this information should be structured, or even between which nodes the information should be sent.
+ - If and how PUCI information should be sent inside SIP.
+- Study on invoking of third party PUCI AS or supplementary services (SS) depending on configuration.
+- Interworking
+ - with non-IMS networks.
+ - with other IMS services like SRVCC, ICS, and service continuity.
+
+- Types of communication that should/can be covered by PUCI, and how the different types of communication affect the PUCI solution.
+- How much of PUCI that can be achieved via prevention and how much needs to be done via treatment.
+- PUCIF to PUCIF communication.
+- Use of existing methods of user notification for PUCI communication.
+- Mitigation of source identity spoofing, especially from non-IMS networks, on the effectiveness of the PUCI mechanism.
+- Illustrative use of standardized PUCI features in typical deployment scenarios.
+
+### 10.10.23 TR 33.905 Recommendations for trusted open platforms
+
+This technical report investigates relevant trust standards and technologies, both existing as well as the ones that are work-in-progress. It develops the recommendations for trusted open platforms for delivery of new applications and services to open platforms.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TR 133 905 | 11.0.0 | Published | 2012-11-09 | http://www.etsi.org/deliver/etsi_tr/133900_133999/133905/11.00.00_60/tr_133905v110000p.pdf |
+| ATIS | ATIS.3GPP.33.905V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.905(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.905(R11-11.0.0) |
+| TTC | TR-3GA-33.905(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TR/TR-3GA-33.905(Rel11)v11.0.0.pdf |
+
+### 10.10.24 TR 33.919 3G Security; Generic authentication architecture (GAA); System description
+
+This 3GPP technical report aims to give an overview of the different mechanisms that mobile applications can rely upon for authentication between server and client (i.e., the UE). Additionally, it provides guidelines related to the use of GAA and to the choice of authentication mechanism in a given situation and for a given application.
+
+To this end, the TR puts the different GAA specifications that are related to peer authentication into perspective. It clarifies the logic for having three technical specifications, sketches their content and explains the interrelation between these three TSs and their relation with this TR.
+
+
+
+Diagram showing the relationships between GAA specifications and the protocols used by GAA interfaces. The diagram is a hierarchical table. The top row is 'GAA System Description TR 33.919'. The second row is 'GAA GBA TS 33.220'. The third row shows 'GAA SSC 33.221' and 'GAA HTTPS TS 33.222' on the left, 'GAA Ub & Ua TS 24.109' in the middle, and 'GAA Zh and Zn TS 29.109' on the right. The fourth row labels the interfaces: 'Ua', 'Ub', 'Zh', and 'Zn'. The fifth row shows protocols for each interface: 'HTTP Digest RFC 2617 (Note)' for Ua, 'HTTP Digest AKA RFC 3310' for Ub, and 'IMS Cx Diameter message definitions TS 29.229' for Zh and Zn. The sixth row shows 'HTTP' for Ua and Ub, and 'Diameter Base Protocol RFC 3588' for Zh and Zn. The seventh row shows 'TCP' for Ua and Ub, and 'SCTP' for Zh and Zn. The bottom row shows 'IP' for all interfaces.
+
+Q.1743(16)\_F10.10.24-1
+
+NOTE – The GAA supports potentially many protocols on the Ua interface. One example is the HTTP digest.
+
+**Figure 10.10.24-1 – Relationships between GAA specifications and the protocols used by GAA interfaces**
+
+Figure 10.10.24-1 depicts protocols used over GAA interfaces and the relationships between different GAA specifications. New GAA specifications will be added to the figure as they become available. Also, other protocols may be added in the future. In particular, new kinds of Ua interfaces could be added in the future and then other protocols may be added below the Ua interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB-TR-T12-33.919 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/33/A33919-b00.pdf |
+| ETSI | TR 133 919 | 11.0.0 | Published | 2012-11-09 | http://www.etsi.org/deliver/etsi_tr/133900_133999/133919/11.00.00_60/tr_133919v110000p.pdf |
+| ATIS | ATIS.3GPP.33.919V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.919(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttattdesc.jsp?stdno=TTAT.3G-33.919(R11-11.0.0) |
+
+## 10.10.25 TR 33.937 Study of mechanisms for protection against unsolicited communication for IMS (PUCI)
+
+The scope of this report is to highlight alternative solutions that could be used to protect mobile subscribers from receiving unsolicited communication over IMS and to analyse these solutions in respect of their requirements and impacts on standardized interfaces.
+
+This activity took into account the study done in TISPAN TR 187 009 on "Feasibility study of prevention of unsolicited communications in the NGN".
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TR 133 937 | 11.0.0 | Published | 2012-11-09 | http://www.etsi.org/deliver/etsi_tr/133900_133999/133937/11.00.00_60/tr_133937v110000p.pdf |
+| ATIS | ATIS.3GPP.33.937V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.937(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.937(R11-11.0.0) |
+| TTC | TR-3GA-33.937(Rel11)v11.0.0 | 11.0.0 | TTC Approved | 2013-06-25 | http://www.ttc.or.jp/jp/document_list/free/3gpps2013/TR/TR-3GA-33.937(Rel11)v11.0.0.pdf |
+
+### 10.10.26 TR 33.980 Liberty alliance and 3GPP security interworking; Interworking of liberty alliance identity federation framework (ID-FF), identity web services framework (ID-WSF) and generic authentication architecture (GAA)
+
+The present document provides guidelines on the interworking of the generic authentication architecture (GAA) and the liberty alliance architecture. The document studies the details of possible interworking methods between the security assertion markup language v2.0, SAML v2.0 (or alternatively the liberty alliance identity federation framework, ID-FF), the identity web services framework (ID-WSF), the security assertion markup language (SAML) and a component of GAA called the generic bootstrapping architecture (GBA). This document only applies if liberty alliance and GBA or SAML v2.0 and GBA are used in combination.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB-TR-T12-33.980 | 11.1.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/33/A33980-b10.pdf |
+| ETSI | TR 133 980 | 11.1.0 | Published | 2014-01-22 | http://www.etsi.org/deliver/etsi_tr/133900_133999/133980/11.01.00_60/tr_133980v110100p.pdf |
+| ATIS | ATIS.3GPP.33.980V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-33.980(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-33.980(R11-11.0.0) |
+
+## 10.11 35-series, Security algorithms
+
+### 10.11.1 TS 35.201 Specification of the 3GPP confidentiality and integrity algorithms; Document 1: *f8* and *f9* specifications
+
+This specification gives a detailed specification of the confidentiality algorithm *f8*, and the integrity algorithm *f9*.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-35.201 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/35/A35201-b00.pdf |
+| ETSI | TS 135 201 | 11.0.0 | Published | 2012-11-09 | http://www.etsi.org/deliver/etsi_ts/135200_135299/135201/11.00.00/60/ts_135201v110000p.pdf |
+| ATIS | ATIS.3GPP.35.201V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-35.201(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-35.201(R11-11.0.0) |
+
+#### 10.11.2 TS 35.202 Specification of the 3GPP confidentiality and integrity algorithms; Document 2: Kasumi specification
+
+This specification gives a detailed specification of the Algorithm KASUMI. KASUMI is a block cipher that forms the heart of the confidentiality algorithm *f8*, and the integrity algorithm *f9*.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-35.202 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/35/A35202-b00.pdf |
+| ETSI | TS 135 202 | 11.0.0 | Published | 2012-11-09 | http://www.etsi.org/deliver/etsi_ts/135200_135299/135202/11.00.00/60/ts_135202v110000p.pdf |
+| ATIS | ATIS.3GPP.35.202V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-35.202(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-35.202(R11-11.0.0) |
+
+#### 10.11.3 TS 35.203 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 3: Implementors' test data
+
+This specification gives detailed test data for implementors of the algorithm set. It provides visibility of the internal state of the algorithm to aid in the realisation of the algorithms.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-35.203 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/35/A35203-b00.pdf |
+| ETSI | TS 135 203 | 11.0.0 | Published | 2012-11-09 | http://www.etsi.org/deliver/etsi_ts/135200_135299/135203/11.00.00/60/ts_135203v110000p.pdf |
+
+#### 10.11.4 TS 35.204 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 4: Design conformance test data
+
+This specification gives black-box test data for the algorithm set. The test data has been selected to give a high degree of confidence that the implementation is correct. However, no claim is made that conformance with this test data guarantees a correct implementation.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-35.204 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/35/A35204-b00.pdf |
+| ETSI | TS 135 204 | 11.0.0 | Published | 2012-11-09 | http://www.etsi.org/deliver/etsi_ts/135200_135299/135204/11.00.00_60/ts_135204v110000p.pdf |
+
+### 10.11.5 TS 35.205 3G security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions $f1, f1^*, f2, f3, f4, f5$ and $f5^*$ ; Document 1: General
+
+This report is a description of the work undertaken by an ETSI SAGE Task Force on the design of the milenage algorithm set: an example set of authentication and key generation functions.
+
+The authentication and key generation functions are not standardized. An example set of these algorithms has been produced with the intent that it shall be offered to the UMTS operators, to utilize instead of developing their own. An ETSI SAGE Task Force has carried out this work.
+
+The requirement specification stated that operator personalization of the example set must be possible and that the basic Kernel must be possible to replace.
+
+The example set is based on the block cipher Rijndael, which at the time was one of the advanced encryption standard (AES) candidates and the specification describes how the seven algorithms used in 3GPP authentication and key generation are scheduled around this basic Kernel. The specification and associated test data for the example algorithm set is documented in three documents:
+
+- A formal specification of both the modes and the example Kernel TS 35.206;
+- A detailed test data document, covering modes and the example Kernel TS 35.207;
+- A "black box" test data document TS 35.208.
+
+This report gives an overview of the overall work by the task force.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 135 205 | 11.0.0 | Published | 2012-11-09 | http://www.etsi.org/deliver/etsi_ts/135200_135299/135205/11.00.00_60/ts_135205v110000p.pdf |
+| ATIS | ATIS.3GPP.35.205V 1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-35.205(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-35.205(R11-11.0.0) |
+
+### 10.11.6 TS 35.206 3G security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions $f1, f1^*, f2, f3, f4, f5$ and $f5^*$ ; Document 2: Algorithm specification
+
+This document contains an example set of algorithms which may be used as the authentication and key generation functions $f1, f1^*, f2, f3, f4, f5$ and $f5^*$ . (It is not mandatory that the particular algorithms specified in this document are used – all seven functions are operator-specifiable rather than being fully standardized.)
+
+The algorithms specified in this document are examples that may be used by an operator who does not wish to design his own.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 135 206 | 11.0.0 | Published | 2012-11-09 | http://www.etsi.org/deliver/etsi_ts/135200_135299/135206/11.00.00/60/ts_135206v110000p.pdf |
+| ATIS | ATIS.3GPP.35.206V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-35.206(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-35.206(R11-11.0.0) |
+
+### 10.11.7 TS 35.207 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ ; Document 3: Implementors' test data
+
+This document has been prepared by the 3GPP Task Force, and contains an example set of algorithms which may be used as the authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ . (It is not mandatory that the particular algorithms specified in this document are used — all seven functions are operator-specifiable rather than being fully standardised). This document is one five, which between them form the entire specification of the example algorithms, entitled:
+
+- 3GPP TS 35.205: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ ; Document 1: General".
+- 3GPP TS 35.206: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ ; Document 2: Algorithm Specification".
+- 3GPP TS 35.207: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ ; Document 3: Implementors' Test Data".
+- 3GPP TS 35.208: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ ; Document 4: Design Conformance Test Data".
+- 3GPP TR 35.909: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ ; Document 5: Summary and results of design and evaluation".
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 135 207 | 11.0.0 | Published | 2012-11-09 | http://www.etsi.org/deliver/etsi_ts/135200_135299/135207/11.00.00/60/ts_135207v110000p.pdf |
+
+### 10.11.8 TS 35.208 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions $f1, f1^*, f2, f3, f4, f5$ and $f5^*$ ; Document 4: Design conformance test data
+
+This document has been prepared by the 3GPP Task Force, and contains an example set of algorithms which may be used as the authentication and key generation functions $f1, f1^*, f2, f3, f4, f5$ and $f5^*$ . (It is not mandatory that the particular algorithms specified in this document are used – all seven functions are operator-specifiable rather than being fully standardised). This document is one five, which between them form the entire specification of the example algorithms, entitled:
+
+- 3GPP TS 35.205: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions $f1, f1^*, f2, f3, f4, f5$ and $f5^*$ ; Document 1: General".
+- 3GPP TS 35.206: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions $f1, f1^*, f2, f3, f4, f5$ and $f5^*$ ; Document 2: Algorithm Specification".
+- 3GPP TS 35.207: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions $f1, f1^*, f2, f3, f4, f5$ and $f5^*$ ; Document 3: Implementors' Test Data".
+- 3GPP TS 35.208: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions $f1, f1^*, f2, f3, f4, f5$ and $f5^*$ ; Document 4: Design Conformance Test Data".
+- 3GPP TR 35.909: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions $f1, f1^*, f2, f3, f4, f5$ and $f5^*$ ; Document 5: Summary and results of design and evaluation".
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|--------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 135 208 | 11.0.0 | Published | 2012-11-09 | http://www.etsi.org/deliver/etsi_ts/135200_135299/135208/11.00.00/60/ts_135208v110000p.pdf |
+
+### 10.11.9 TS 35.215 Specification of the 3GPP confidentiality and integrity algorithms UEA2 & UIA2; Document 1: UEA2 and UIA2 specifications
+
+This document specifies the 3GPP confidentiality and integrity algorithms known as UEA2 and UIA2.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-35.215 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/35/A35215-b00.pdf |
+| ETSI | TS 135 215 | 11.0.0 | Published | 2012-11-09 | http://www.etsi.org/deliver/etsi_ts/135200_135299/135215/11.00.00/60/ts_135215v110000p.pdf |
+| ATIS | ATIS.3GPP.35.215V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-35.215(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-35.215(R11-11.0.0) |
+
+**10.11.10 TS 35.216 Specification of the 3GPP confidentiality and integrity algorithms
+UEA2 & UIA2; Document 2: SNOW 3G specification**
+
+This document specifies the 3GPP confidentiality and integrity algorithms known as UEA2 and UIA2.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-35.216 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/35/A35216-b00.pdf |
+| ETSI | TS 135 216 | 11.0.0 | Published | 2012-11-09 | http://www.etsi.org/deliver/etsi_ts/135200_135299/135216/11.00.00_60/ts_135216v110000p.pdf |
+| ATIS | ATIS.3GPP.35.216V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-35.216(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-35.216(R11-11.0.0) |
+
+**10.11.11 TS 35.217 Specification of the 3GPP confidentiality and integrity algorithms
+UEA2 & UIA2; Document 3: Implementors' test data**
+
+The document specifies the 3GPP confidentiality and integrity algorithms known as UEA2 and UIA2.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-35.217 | 11.1.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/35/A35217-b10.pdf |
+| ETSI | TS 135 217 | 11.1.0 | Published | 2013-02-01 | http://www.etsi.org/deliver/etsi_ts/135200_135299/135217/11.01.00_60/ts_135217v110100p.pdf |
+
+**10.11.12 TS 35.218 Specification of the 3GPP confidentiality and integrity algorithms
+UEA2 & UIA2; Document 4: Design conformance test data**
+
+The document specifies the 3GPP confidentiality and integrity algorithms known as UEA2 and UIA2.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-35.218 | 11.1.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/35/A35218-b10.pdf |
+| ETSI | TS 135 218 | 11.1.0 | Published | 2013-02-06 | http://www.etsi.org/deliver/etsi_ts/135200_135299/135218/11.01.00_60/ts_135218v110100p.pdf |
+
+**10.11.13 TS 35.221 Specification of the 3GPP confidentiality and integrity algorithms
+EEA3 & EIA3; Document 1: EEA3 and EIA3 specifications**
+
+The document specifies the 3GPP confidentiality and integrity algorithms known as EEA3 and EIA3.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-35.221 | 11.0.1 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/35/A35221-b01.pdf |
+| ETSI | TS 135 221 | 11.0.1 | Published | 2012-05-30 | http://www.etsi.org/deliver/etsi_ts/135200_135299/135221/11.00.01_60/ts_135221v110001p.pdf |
+| ATIS | ATIS.3GPP.35.221V1101-2014 | 11.0.1 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-35.221(R11-11.0.1) | 11.0.1 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-35.221(R11-11.0.1) |
+
+**10.11.14 TS 35.222 Specification of the 3GPP confidentiality and integrity algorithms
+EEA3 & EIA3; Document 2: ZUC specification**
+
+The document specifies the 3GPP confidentiality and integrity algorithms known as EEA3 and EIA3.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-35.222 | 11.0.1 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/35/A35222-b01.pdf |
+| ETSI | TS 135 222 | 11.0.1 | Published | 2012-05-30 | http://www.etsi.org/deliver/etsi_ts/135200_135299/135222/11.00.01_60/ts_135222v110001p.pdf |
+| ATIS | ATIS.3GPP.35.222V1101-2014 | 11.0.1 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-35.222(R11-11.0.1) | 11.0.1 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-35.222(R11-11.0.1) |
+
+**10.11.15 TS 35.223 Specification of the 3GPP confidentiality and integrity algorithms
+EEA3 & EIA3; Document 3: Implementors' test data**
+
+The document specifies the 3GPP confidentiality and integrity algorithms known as EEA3 and EIA3.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-35.223 | 11.0.1 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/2_T63/ARIB-STD-T63/Rel11/35/A35223-b01.pdf |
+| ETSI | TS 135 223 | 11.0.1 | Published | 2012-05-30 | http://www.etsi.org/deliver/etsi_ts/135200_135299/135223/11.00.01_60/ts_135223v110001p.pdf |
+
+**10.11.16 TR 35.909 3G security; Specification of the MILENAGE algorithm set:
+An example algorithm set for the 3GPP authentication and key generation functions $f_1, f_1^*, f_2, f_3, f_4, f_5$ and $f_5^*$ ; Document 5: Summary and results of design and evaluation**
+
+This report contains a detailed summary of the work performed during the design and evaluation of the 3G authentication functions denoted as the MILENAGE algorithm set.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TR 135 909 | 11.0.0 | Published | 2012-11-09 | http://www.etsi.org/deliver/etsi_tr/135900_135999/135909/11.00.00_60/tr_135909v110000p.pdf |
+| ATIS | ATIS.3GPP.35.909V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-35.909(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-35.909(R11-11.0.0) |
+
+**10.11.17 TR 35.919 Specification of the 3GPP confidentiality and integrity algorithms UEA2 & UIA2; Document 5: Design and evaluation report**
+
+This document specifies the 3GPP confidentiality and integrity algorithms known as UEA2 and UIA2.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB-TR-T12-35.919 | 11.0.0 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/35/A35919-b00.pdf |
+| ETSI | TR 135 919 | 11.0.0 | Published | 2012-11-09 | http://www.etsi.org/deliver/etsi_tr/135900_135999/135919/11.00.00_60/tr_135919v110000p.pdf |
+| ATIS | ATIS.3GPP.35.919V1100-2014 | 11.0.0 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-35.919(R11-11.0.0) | 11.0.0 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-35.919(R11-11.0.0) |
+
+**10.11.18 TR 35.924 Specification of the 3GPP confidentiality and integrity algorithms EEA3 & EIA3; Document 4: Design and evaluation report**
+
+The document specifies the 3GPP confidentiality and integrity algorithms known as EEA3 and EIA3.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB-TR-T12-35.924 | 11.0.1 | ARIB published | 2014-03-18 | http://www.arib.or.jp/english/html/overview/doc/STD-T63v10_30/3_T12/ARIB-TR-T12/Rel11/35/A35924-b01.pdf |
+| ETSI | TS 135 924 | 11.0.1 | Published | 2012-05-30 | http://www.etsi.org/deliver/etsi_tr/135900_135999/135924/11.00.01_60/tr_135924v110001p.pdf |
+| ATIS | ATIS.3GPP.35.924V1101-2014 | 11.0.1 | Approved | 2014-09-26 | https://www.atis.org/docstore/default.aspx |
+| TTA | TTAT.3G-35.924(R11-11.0.1) | 11.0.1 | Published | 2013-08-26 | http://www.tta.or.kr/English/new/standardization/eng_ttatddesc.jsp?stdno=TTAT.3G-35.924(R11-11.0.1) |
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.1762-200709-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1762-200709-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..6dbc7505709eb3a7a2aae65164174fe883259e96
--- /dev/null
+++ b/marked/Q/T-REC-Q.1762-200709-I_PDF-E/raw.md
@@ -0,0 +1,722 @@
+
+
+**ITU-T**
+
+**Q.1762/Y.2802**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(09/2007)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Signalling requirements and protocols for IMT-2000
+
+SERIES Y: GLOBAL INFORMATION
+INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS
+AND NEXT-GENERATION NETWORKS
+
+Next Generation Networks – Generalized mobility
+
+# --- **Fixed-mobile convergence general requirements**
+
+ITU-T Recommendation Q.1762/Y.2802
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+# SWITCHING AND SIGNALLING
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120-Q.499 |
+| DIGITAL EXCHANGES | Q.500-Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 |
+| Q3 INTERFACE | Q.800-Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 |
+| INTELLIGENT NETWORK | Q.1200-Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 |
+| BROADBAND ISDN | Q.2000-Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# **ITU-T Recommendation Q.1762/Y.2802**
+
+# **Fixed-mobile convergence general requirements**
+
+## **Summary**
+
+ITU-T Recommendation Q.1762/Y.2802 defines the requirements for fixed-mobile convergence (FMC). For this purpose, this Recommendation describes the considerations for FMC, including the fundamental characteristics, service requirements, network capabilities, approach, scenarios and the relevant network environments.
+
+## **Source**
+
+ITU-T Recommendation Q.1762/Y.2802 was approved on 21 September 2007 by ITU-T Study Group 19 (2005-2008) under the ITU-T Recommendation A.8 procedure.
+
+### **Keywords**
+
+Convergence, fixed, FMC, mobile, NGN, Systems beyond IMT-2000.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+### NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2008
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## CONTENTS
+
+###### Page
+
+| | | |
+|------|-----------------------------------------------------------------|----|
+| 1 | Scope and purpose ..... | 1 |
+| 2 | References..... | 1 |
+| 3 | Definitions ..... | 2 |
+| 3.1 | Terms defined elsewhere ..... | 2 |
+| 3.2 | Terms defined in this Recommendation..... | 2 |
+| 4 | Abbreviations and acronyms ..... | 2 |
+| 5 | Conventions ..... | 4 |
+| 5.1 | Usage of the term "IMS" ..... | 4 |
+| 6 | Objectives of FMC ..... | 4 |
+| 6.1 | General objectives of FMC ..... | 4 |
+| 6.2 | Objectives from different perspectives..... | 5 |
+| 7 | Fundamental characteristics of FMC..... | 5 |
+| 8 | FMC service requirements..... | 6 |
+| 8.1 | Access service support ..... | 6 |
+| 8.2 | Enhanced VPN ..... | 6 |
+| 8.3 | Unified messaging..... | 7 |
+| 9 | FMC capability requirements ..... | 7 |
+| 9.1 | Access independence..... | 7 |
+| 9.2 | Uniform authentication and uniform authorization mechanism..... | 7 |
+| 9.3 | Charging and management ..... | 7 |
+| 9.4 | Service access environment..... | 7 |
+| 9.5 | Quality of service ..... | 8 |
+| 9.6 | Interworking ..... | 8 |
+| 9.7 | Reliability requirements ..... | 8 |
+| 9.8 | Security requirements..... | 8 |
+| 9.9 | Public services issues ..... | 8 |
+| 9.10 | Network selection..... | 8 |
+| 9.11 | Location identification..... | 9 |
+| 9.12 | Personalized configuration ..... | 9 |
+| 9.13 | Personal data network storage ..... | 9 |
+| 9.14 | Accounting support capabilities ..... | 9 |
+| 9.15 | Message processing..... | 9 |
+| 9.16 | Presence information..... | 9 |
+| 9.17 | Mechanism for applications to access user data..... | 10 |
+| 9.18 | User identifier management ..... | 10 |
+
+| | Page |
+|----------------------------------------------|-------------|
+| 10 Network environment ..... | 10 |
+| 10.1 General network environments..... | 10 |
+| 10.2 FMC network scenarios..... | 11 |
+| Appendix I – FMC approach and scenarios..... | 13 |
+| I.1 Convergence in the control layer..... | 13 |
+| I.2 Convergence in application layer ..... | 14 |
+| I.3 Convergence in the management layer..... | 15 |
+| Bibliography ..... | 16 |
+
+# **Fixed-mobile convergence general requirements**
+
+# **1 Scope and purpose**
+
+This Recommendation is intended to be used as the general requirements document leading to the development of recommendations and implementation guidelines for the realization of fixed-mobile convergence (FMC). This is to ensure that all elements required for interoperability and the associated network capabilities to support applications globally across an FMC environment are adequately addressed by ITU-T standardization activities.
+
+The scope of this Recommendation is to provide FMC principles, high-level service requirements and capabilities. More specifically, this Recommendation identifies the fundamental characteristics, requirements and capabilities that FMC supports.
+
+As next generation networks (as described in [ITU-T Y.2011]) evolve, they will increasingly support the general FMC requirements and capabilities defined in this Recommendation. NGN specific FMC requirements will be captured in releasing specific NGN requirements Recommendations.
+
+# **2 References**
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; 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.1741] ITU-T Recommendation Q.1741-series:
+- Q.1741.1 (2002), *IMT-2000 references to release 1999 of GSM evolved UMTS core network with UTRAN access network.*
+ - Q.1741.2 (2002), *IMT-2000 references to release 4 of GSM evolved UMTS core network with UTRAN access network.*
+ - Q.1741.3 (2003), *IMT-2000 references to release 5 of GSM evolved UMTS core network.*
+ - Q.1741.4 (2005), *IMT-2000 references to release 6 of GSM evolved UMTS core network.*
+- [ITU-T Q.1742] ITU-T Recommendation Q.1742-series:
+- Q.1742.1 (2002), *IMT-2000 references to ANSI-41 evolved core network with cdma2000 access network.*
+ - Q.1742.2 (2003), *IMT-2000 references (approved as of 11 July 2002) to ANSI-41 evolved core network with cdma2000 access network.*
+ - Q.1742.3 (2004), *IMT-2000 references (approved as of 30 June 2003) to ANSI-41 evolved core network with cdma2000 access network.*
+ - Q.1742.4 (2005), *IMT-2000 references (approved as of 30 June 2004) to ANSI-41 evolved core network with cdma2000 access network.*
+
+- Q.1742.5 (2006), *IMT-2000 references (approved as of 31 December 2005) to ANSI-41 evolved core network with cdma2000 access network.*
+ - Q.1742.6 (2007), *IMT-2000 references (approved as of 31 December 2006) to ANSI-41 evolved core network with cdma2000 access network.*
+- [ITU-T Q.1761] ITU-T Recommendation Q.1761 (2004), *Principles and requirements for convergence of fixed and existing IMT-2000 systems.*
+- [ITU-T Y.2001] ITU-T Recommendation Y.2001 (2004), *General overview of NGN.*
+- [ITU-T Y.2011] ITU-T Recommendation Y.2011 (2004), *General principles and general reference model for Next Generation Networks.*
+- [ITU-T Y.2021] ITU-T Recommendation Y.2021 (2006), *IMS for Next Generation Networks.*
+- [ITU-T Y.2031] ITU-T Recommendation Y.2031 (2006), *PSTN/ISDN emulation architecture.*
+- [ITU-T Y.2091] ITU-T Recommendation Y.2091 (2007), *Terms and definitions for Next Generation Networks.*
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following term defined elsewhere:
+
+**3.1.1 identifier** [ITU-T Y.2091]: An identifier is a series of digits, characters and symbols or any other form of data used to identify subscriber(s), user(s), network element(s), function(s), network entity(ies) providing services/applications, or other entities (e.g., physical or logical objects). Identifiers can be used for registration or authorization. They can be either public to all networks, shared between a limited number of networks or private to a specific network (private IDs are normally not disclosed to third parties).
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 fixed mobile convergence:** In a given network configuration, the capabilities that provide services and application to the end user defined in [ITU-T Y.2091] regardless of the fixed or mobile access technologies being used and independent of the user's location. In the NGN environment [ITU-T Y.2011], it means to provide NGN services to end users regardless of the fixed or mobile access technologies being used.
+
+**3.2.2 fixed network:** A network that provides wire-based (e.g., copper, fibre) or wireless access to its services. The fixed network may support nomadism, but does not support mobility.
+
+**3.2.3 mobile network:** A network that provides wireless access to its services and supports mobility.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|-----|-----------------------------------|
+| 2G | Second Generation |
+| API | Application Programming Interface |
+| AS | Application Server |
+
+| | |
+|----------|-------------------------------------------------------------------|
+| ATM | Asynchronous Transfer Mode |
+| CAMEL | Customized Applications for Mobile network Enhanced Logic |
+| CAP | CAMEL Application Part |
+| CATV | Community Antenna Television (commonly referred to as Cable TV) |
+| CDMA | Code Division Multiple Access |
+| CDR | Call Detail Record |
+| CS | Circuit Switched |
+| DAB | Digital Audio Broadcast |
+| DSL | Digital Subscriber Line |
+| DVB | Digital Video Broadcasting |
+| DVB-H | Digital Video Broadcasting Hand-held |
+| FMC | Fixed-Mobile Convergence |
+| FTTH | Fibre to the Home |
+| GAN | Generic Access Network |
+| GPRS | General Packet Radio Service |
+| GSM | Global System for Mobile communications |
+| GW | Gateway |
+| HRPD | High Rate Packet Data |
+| IM | Instant Message |
+| IMS | IP Multimedia Subsystem |
+| IMT-2000 | International Mobile Telecommunications – 2000 |
+| INAP | Intelligent Network Application Protocol |
+| IP | Internet Protocol |
+| IPTV | IP-based TV |
+| ISDN | Integrated Services Digital Network |
+| ISIM | IMS Subscriber Identity Module |
+| LAN | Local Area Network |
+| LMSD | Legacy Mobile Station Domain |
+| LTE | Long Term Evolution |
+| MMD | Multimedia Domain |
+| MMS | Multimedia Message Service |
+| NGN | Next Generation Network |
+| OSA | Open Service Architecture |
+| PBX | Private Branch Exchange |
+| PDA | Personal Digital Assistant (typically a small hand-held computer) |
+| PES | PSTN Emulation Subsystem |
+| PHS | Personal Handyphone System |
+
+| | |
+|--------|---------------------------------------------|
+| PLC | Power Line Communication |
+| PLMN | Public Land Mobile Network |
+| POTS | Plain Old Telephone Service |
+| PSDN | Packet Switched Data Network |
+| PSTN | Public Switched Telephone Network |
+| QoS | Quality of Service |
+| SAE | System Architecture Evolution |
+| SCP | Service Control Point |
+| SIP | Session Initiation Protocol |
+| SMS | Short Message Service |
+| SSP | Service Switching Point |
+| UMA | Unlicensed Mobile Access |
+| UMTS | Universal Mobile Telecommunication System |
+| UTRAN | UMTS Terrestrial Radio Access Network |
+| VCC | Voice Call Continuity |
+| VoIP | Voice over IP |
+| VPMN | Virtual Private Mobile Network |
+| VPN | Virtual Private Network |
+| WAN | Wide Area Network |
+| W-CDMA | Wideband CDMA |
+| WiMAX | World Interoperability for Microwave Access |
+| WLAN | Wireless LAN |
+| xDSL | Any of the various types of DSL |
+
+# 5 Conventions
+
+## 5.1 Usage of the term "IMS"
+
+The term "IMS" without any prefix as used in this Recommendation refers to the IMS concept in [ITU-T Y.2021] and as updated in the most recent versions of [ITU-T Q.1741] and [ITU-T Q.1742].
+
+# 6 Objectives of FMC
+
+## 6.1 General objectives of FMC
+
+The following points provide the general objectives for FMC:
+
+- Seamless service operation from the end user perspective across heterogeneous fixed networks (i.e., PSTN, ISDN, PSDN, WAN/LAN/CATV, etc.) and mobile networks (i.e., GSM, CDMA2000, WiMAX, etc.), subject to any limitations imposed by the characteristics of the particular access technology being used.
+
+- Seamless service provisioning from the service provider's perspective across heterogeneous fixed and mobile networks, subject to any limitations imposed by the characteristics of the particular access technology being used.
+- Generalized Mobility defined in [ITU-T Y.2001] is supported in FMC (i.e., terminal device mobility, user mobility and session mobility). For a given scenario, different levels of mobility may be needed.
+- Ubiquity of service availability where the end users can enjoy virtually any application, from any location, on any terminal device subject to any limitations imposed by the characteristics of the particular access technologies and terminal devices being used, given that the service has been subscribed.
+- Support of multiple user identifier and authentication/authorization mechanisms.
+
+## 6.2 Objectives from different perspectives
+
+The following subclauses provide more specific objectives for FMC:
+
+### 6.2.1 End users' perspective
+
+- Converged services that function consistently independent of the access technology or terminal device being used with associated, reduced complexity of telecommunications operation and subscription.
+- Convenient access to and usage of a wide range of services of multiple service providers through technology that enables easy configuration, allowing an end user to obtain only one bill if so desired by this end user, even when multiple service providers are involved.
+- Seamless service experiences, whenever desired and wherever the end user may be, limited only by the capabilities of the access technology and the terminal device being used, and with the expectation that the end user will have access to multiple terminal devices with different ranges of capabilities.
+
+### 6.2.2 Service providers' perspective
+
+- Ability to offer a wide range of services.
+- Simplified network deployment and operation through the ability to offer access and terminal device independent services, as opposed to having to provide multiple access-specific and terminal device-specific instances of the same service.
+- Ability to reuse the fixed-line assets from traditional fixed service providers and mixed service providers in an FMC context.
+- Ability to provide better coverage and QoS to end users compared to traditional mobile service providers in an FMC context.
+
+# 7 Fundamental characteristics of FMC
+
+The following points describe the fundamental characteristics of FMC:
+
+- Consistency of user experience is provided through a generic service delivery environment, which satisfies the needs of the fixed network and of the mobile network. The user is able to obtain services in a consistent manner as allowed by the connectivity and terminal device capabilities. Services are offered in accordance with FMC capabilities. For example, an ongoing call could be downgraded for some reasons, such as change of access technology or terminal device capability. A video communication may be downgraded to a voice communication when the user migrates to mobile-only coverage where the access technology is not able to support it.
+- Subscriptions and service provisioning are access-technology agnostic but the service stratum may be aware of both the access and terminal device capabilities involved in a
+
+communication instance. Services are supported in all existing and emerging fixed and mobile access technologies where possible and subject to user preferences. Service registration, triggering and execution adapt to network and terminal device capabilities. The user's availability, reachability, and the terminal device's capabilities are perceptible to network functions, and as needed to services and applications, including those provided by a third party; assuming that
+
+FMC respects
+
+- the user's privacy and privacy-sensitive data (e.g., address book, preferences, presence settings, billing/payment settings and other security settings) contained in the user's profile,
+ - the user's personal preferences (e.g., availability, reachability), and
+ - the terminal's device capabilities;
+- and adequately protects this information
+- against loss of privacy and loss of confidentiality,
+ - against unauthorized access, and
+ - against unauthorized manipulation;
+
+during storage and/or during communication within and beyond a service provider's domain.
+
+- FMC's service and application processing may depend on terminal device capabilities. Compatible terminal device capabilities may be selected by end-to-end interaction between terminal devices, or between the terminal device and the FMC service stratum according to the service and application needs.
+- Support of generalized mobility, which includes service mobility, user, terminal device and network mobility. Reduced or partial mobility may be supported in some specific networks.
+- A generic user profile for services which contains the criteria for session establishment and connectivity and is applicable both in fixed and in mobile networks, and which is specific to an individual user's subscription, containing, e.g., the user's address book, preferences, presence options, billing and payment options, service subscriptions and authentication parameters.
+
+# **8 FMC service requirements**
+
+The following service requirements are defined.
+
+## **8.1 Access service support**
+
+FMC is required to provide access-independent service for users.
+
+FMC is required to offer the user the choice to select a suitable access transport to obtain service.
+
+NOTE 1 – Typical access transports include xDSL, WLAN, LAN, optical fibre and ATM, etc.
+
+If the user has given specific permission to FMC to make a choice on his/her behalf, FMC may select from available access transports without further user intervention.
+
+NOTE 2 – This service allows users to choose an access mode, or makes a suitable choice on behalf of the user providing seamless access and a better service experience for users.
+
+## **8.2 Enhanced VPN**
+
+Enhanced VPN service is an access-independent virtual private service network supporting multiple terminal types.
+
+Enhanced VPN makes it possible to provide a consistent virtual private network service by using a variety of public network resources, i.e., consistent VPN service across fixed networks, mobile networks and converged networks, and a variety of terminal devices.
+
+It is required to support the capability to allow users connecting to different public networks (i.e., PSTN, PLMN, etc.). For this, it is required to support private network capabilities, such as use of a private numbering plan.
+
+## **8.3 Unified messaging**
+
+Unified messaging means users can receive several types of messages, such as short message service, multimedia message service, instant messaging, e-mail, etc.
+
+FMC is required to let an end user choose the message type to be received. The end user may express message types to be received based on favourites, online state or terminal device type. FMC is required to support all types of messages from the sender and to transcode messages as far as possible into a format which the recipient is able to receive.
+
+An example scenario is where a user could receive instant messages on his mobile phone as short message service (SMS) messages when he is otherwise offline.
+
+# **9 FMC capability requirements**
+
+The following general requirements for FMC capabilities are defined.
+
+NOTE – Specific FMC charging, security, public service, reliability and interworking requirements are not given. Such FMC requirements are deferred for further study.
+
+## **9.1 Access independence**
+
+Services and features offered via FMC are required to be access-independent so that services are offered to users regardless of how they gain access.
+
+## **9.2 Uniform authentication and uniform authorization mechanism**
+
+Due to the nature of FMC (see Appendix I for an analysis of FMC scenarios), FMC is required to provide a uniform authentication and a uniform authorization mechanism at the FMC service stratum applicable to any given configuration.
+
+NOTE 1 – Uniform security mechanism (authentication or authorization) is meant to encompass a single, common, generic security mechanism and is understood in the sense to bridge both for wireless- and for wire-based access networks at the FMC service stratum. Thus, the notion of uniform applies only to the security mechanism as such but does not impose any requirements to use uniform security keys/credentials, such as used by a single-sign on mechanism for example.
+
+NOTE 2 – As FMC may contain access-specific or access-dependent parts, a uniform authentication and uniform authorization mechanism may not be available at the FMC transport stratum. For different users, the data relating to authentication and authorization may vary, and the parameters in the related messages may also differ, but the procedure for handling these is uniform.
+
+It is left for future study to identify FMC security requirements for uniform authentication and authorization mechanisms (i.e., authentication and authorization combined).
+
+## **9.3 Charging and management**
+
+FMC is required to provide charging and management mechanisms.
+
+NOTE – This requirement supports collecting resource usage information and managing data relating to subscriber resource usage.
+
+## **9.4 Service access environment**
+
+FMC is required to provide the capabilities to access a wide range of application servers or service platforms. The underlying network may be circuit-based or packet-based.
+
+## **9.5 Quality of service**
+
+FMC is required to provide QoS mechanisms.
+
+NOTE – This requirement enables service level agreements supporting user and service requirements, such as dynamic negotiation of QoS parameters between the service and transport layers, including both the access and the core networks.
+
+## **9.6 Interworking**
+
+FMC is required to support interworking with existing networks, e.g., the legacy PSTN.
+
+Interworking does not impose any new requirements upon existing, non-FMC-capable networks other than to provide interfaces to interworking functions according to standardized mechanisms that are already supported by existing networks.
+
+## **9.7 Reliability requirements**
+
+FMC is required to support reliable communications, including appropriate overload control and failure recovery mechanisms. The support of specific overload control and failure recovery mechanisms to manage and mitigate the consequences of such events to achieve the required level of reliability is not needed if the transport network and the processing systems are considered to yield sufficient reliability and are able to adequately mitigate overload situations.
+
+## **9.8 Security requirements**
+
+FMC is required to provide security mechanisms to meet service requirements.
+
+## **9.9 Public services issues**
+
+FMC is required to provide all the means to support public interest services required by regulations or laws of relevant national or regional administrations and international treaties. This includes requirements for:
+
+- lawful interception;
+- malicious communication identification;
+- unsolicited bulk telecommunications;
+- emergency telecommunications;
+- location information related to emergency telecommunication;
+- user identity presentation and privacy;
+- network or service provider selection;
+- users with disabilities;
+- number portability; and
+- service unbundling.
+
+## **9.10 Network selection**
+
+FMC is required to support that a provider is able to define the preferred access network for service delivery in case the user has both fixed and mobile coverage. A user may indicate via the terminal device the preferred access network for access to services.
+
+The provider defines the policy regarding when handover between access networks is required to occur.
+
+For example, an ongoing communication over a mobile access network may be switched to a wire-based access technology for connection when it is determined that the terminal has moved to a location where it is able to access the service via fixed coverage.
+
+## **9.11 Location identification**
+
+FMC is required to support the ability to identify a user's location, and offers the location information to location-related services when the end user has given permission, and this is subject to public service requirements.
+
+The resolution of location information is dependent on the capabilities of the access technology.
+
+FMC is required to harmonize the different location identification mechanisms from existing networks.
+
+## **9.12 Personalized configuration**
+
+FMC is required to support the ability to provide personalized services according to a user's requirement.
+
+NOTE – This capability may be implemented through a network-based profile which can be customized by the user within defined limits and such that all services work well according to the indications in the profile.
+
+## **9.13 Personal data network storage**
+
+FMC is required to store personal data on behalf of (or with permission by) the end user. It is required that the end user is able to access and manipulate those personal data through one of the user's various terminal devices.
+
+For example, FMC can store a contact address book on behalf of (or with permission by) the end user. The end user can utilize this address book from different terminal devices thereby avoiding multiple independent and unsynchronized address books for the different terminal devices the end user may have.
+
+## **9.14 Accounting support capabilities**
+
+FMC is required to support the ability to collect CDR information from different network elements, which are used by the charging/billing system to gather together relevant usage data to initiate a unified bill to the specific user for multiple kinds of services with different terminal devices.
+
+NOTE – CDR information collection among one or several providers can only take place if the end user has given implicit or explicit permission.
+
+In the case that the end user may be reachable by one identifier on different terminal devices, FMC is required to support to associate all relevant CDR information with the particular identifier.
+
+## **9.15 Message processing**
+
+FMC is required to support the storage, transcoding, conversion and relay of different types of messages (SMS, MMS, IM, email, etc.).
+
+For example, it may be appropriate to transcode and to convert a video contained within an IM into an MMS message with associated compression and recoding of the content. These functions are implemented by application servers or by application gateways with control elements recognizing the need to do the transformation in relation to the type of message being sent and the capabilities of the terminal device to which it is being sent.
+
+NOTE – Transport-level interworking through encapsulation may be appropriate in certain scenarios.
+
+## 9.16 Presence information
+
+FMC is required to be able to store user presence information which can be accessed by appropriate applications.
+
+## 9.17 Mechanism for applications to access user data
+
+With permission given by the end user, FMC is required to provide mechanisms to enable applications to access relevant user data independent of where the end user data is stored.
+
+## 9.18 User identifier management
+
+An end user may have several different kinds of terminal devices, such as a legacy fixed terminal, a mobile phone, a PDA, a portable computer with extended capabilities, or a desktop fixed computer operating as a terminal with substantial multimedia capabilities.
+
+FMC has the ability to provide a unique user identifier at the transport stratum which allows differentiation among user terminal devices. Additional identifiers may be used at the service stratum to identify the user for end-user services.
+
+NOTE – The Administration or service providers choose the identification scheme and the corresponding identifier(s). Such identifiers can exhibit the property of being public or of being private. In some FMC environments, a user may have different identifiers depending on the access network technology.
+
+It is required to support user identification by:
+
+- a) a single and unique identifier related to the user's subscription; or
+- b) a number of such user identifiers mapped to a unique user identifier.
+
+FMC may apply a different end users' identifier when end user accesses different technologies, therefore Administrations or service providers may require common user identifier management to provide registration and authorization for the user regardless of the access mechanisms or terminals being used.
+
+# 10 Network environment
+
+## 10.1 General network environments
+
+FMC needs to cover the possibilities for convergence across existing different network infrastructures and access mechanisms.
+
+The following are among the envisaged network infrastructures:
+
+- Fixed network, such as PSTN/ISDN, cable TV network, softswitch-based/IMS-based PES, IPTV service network, H.323 VoIP network and IMS-based NGN.
+- Mobile network, multiple IMT-2000 family members consisting of the various releases of GSM evolved UMTS core network with UTRAN access network [ITU-T Q.1741], the various releases of ANSI-41 evolved core network with cdma2000 access network [ITU-T Q.1742], mobile WiMAX, etc.
+
+The following are among the envisaged access mechanisms:
+
+- The access network parts of IMT-2000: GSM/UTRAN and ANSI-41/cdma2000.
+- WLAN in hot spots or as mesh networks.
+- WiMAX broadband wireless access.
+- xDSL, Cable, PLC, FTTH fixed access.
+- Legacy PSTN systems used for narrow-band IP services access.
+- The access network parts of digital audio broadcast (DAB) and digital video broadcasting (DVB)/digital video broadcasting handheld (DVB-H).
+
+NOTE – The various systems listed above encompass very different network infrastructures, different bandwidth capabilities, as well as very different access technologies. It is therefore not anticipated that a single multimode terminal device will be able to handle every possible access. Rather, it is anticipated that users will access their services via a range of terminal devices, some of them capable of multimode operation. Consequently, mobility across this heterogeneous environment requires service adaptation for terminal device mobility as well as for personal mobility.
+
+## **10.2 FMC network scenarios**
+
+The following subclauses describe several scenarios for fixed-mobile convergence and indicate requirements associated with these scenarios.
+
+### **10.2.1 IMS-based FMC**
+
+This convergence of fixed and mobile networks enables users to move between fixed and mobile access networks and still have access to the same set of IMS-based services. The fixed and mobile access networks might both be part of the user's home network, but it is a requirement that the case where one or both are visited networks is also supported.
+
+IMS-based FMC includes the scenario that during mobility, only one access is on an IMS-based network. Service continuity needs to be supported between the fixed and the mobile access technologies if the session control layer corresponding to one of the access technologies is IMS-based (i.e., handover of voice calls between the mobile circuit domain and the fixed network controlled by IMS).
+
+Service provisioning is required to be independent of the access technologies.
+
+User experience may be limited by the access network capabilities when using different access technologies, such as lower quality video communication when low bandwidth access is used, etc.
+
+ISIM functionalities are required for user identification mechanisms, but it is also necessary to support legacy terminal devices without ISIM functionality for service access, especially when one side is not IMS-based network.
+
+Broadcasting/Multicasting capabilities are needed but may be limited by the network capabilities.
+
+Access-agnostic uniform mechanisms are required; the end user could access the services from broadband fixed-access (e.g., xDSL, cable) and mobile access (e.g., WiMAX).
+
+Voice call continuity (VCC) is required in this scenario to provide ongoing call continuity between the cellular CS domain and the IMS domain. When users with dual-mode terminal devices move between the two domains, handover may happen from a cellular CS domain to an IMS domain or the reverse and no break is perceived by users during the handover.
+
+Enhanced VPN support is required in this scenario.
+
+IMS-based FMC could in principle also support service continuity for video calls between the IMS and a cellular CS domain. This capability is for further study.
+
+IMS-based FMC may provide services to mobile as well as PSTN/ISDN terminal devices through IMS-based PSTN/ISDN emulation. This FMC scenario is detailed in [ITU-T Y.2031]. Specific requirements for this scenario are for further study.
+
+### **10.2.2 FMC between circuit-switched mobile and PSTN networks**
+
+This convergence of fixed and mobile networks enables users to roam into the legacy PSTN network outside a GSM/UTRAN or ANSI-41/cdma2000 network. The requirement to support that users roam into a PBX network is for future study.
+
+Limited mobility is supported, e.g., nomadism, but service continuity (handover) is not required to be supported for this scenario.
+
+NOTE – Technologies for access to the PSTN could be GSM/UTRAN or ANSI-41/cdma2000 radio technologies and local radio technologies such as Bluetooth or Wi-Fi.
+
+Voice communication services in this scenario are required to be supported using a single personal number or user identifier. Video communication services could also be supported in this scenario.
+
+GSM/UTRAN or ANSI-41/cdma2000 supplementary services are required to be supported when the user makes and receives calls under PSTN access unless limited by PSTN network capabilities.
+
+Enhanced VPN support is required in this scenario.
+
+### **10.2.3 FMC in access network by UMA/GAN**
+
+This convergence of fixed and mobile networks to enable the provision of service continuity for a multi-mode WLAN/2G terminal device when it changes its point of attachment is known as unlicensed mobile access (UMA). Demand for such capabilities is driven by competition on price and user convenience and the desire to extend service coverage in buildings with poor mobile radio reception.
+
+UMA is also known as generic access network (GAN) [b-ETSI TS 143 318].
+
+This scenario does not provide an evolution path to an all-IP NGN, since it keeps voice calls in the CS domain. This scenario is for further study.
+
+# Appendix I
+
+## FMC approach and scenarios
+
+(This appendix does not form an integral part of this Recommendation)
+
+NGN gives the framework to provide FMC service capabilities irrespective of the different access technologies. Service providers may also provide FMC services based on existing networks they operate by changing or upgrading selected components of their network. Different approaches are required to obtain the ability to provide the desired FMC service experience to users.
+
+End users are able to use FMC services from both the fixed access network and from the mobile access network.
+
+An example FMC solution is a single multi-mode terminal device, which supports both fixed and mobile access can provide the user a better service experience, than when using different terminal devices to achieve the same service result. However, multi-mode terminals may not be able to fully support all necessary access networks.
+
+Several scenarios for network implementation to achieve FMC services are given in the following clauses.
+
+The transport network is not explicitly shown in these figures. FMC may also support seamless mobility in transport network between heterogeneous access networks, so the service continuity between these access transport networks can be achieved. From the service aspect, a multi-mode terminal attached to different access transport networks may access unified and consistent services and applications. From the network aspect, mobility-enabled transport network may support any type of IP-based access transport network regardless of its mobility features. Transport network convergence is for further study.
+
+### I.1 Convergence in the control layer
+
+In this scenario, a unified control layer network is provided to support both fixed and mobile access. This convergence occurs in the control layer as shown in Figure I.1. In this architecture, both the fixed access network and the mobile access network are controlled by this unified control layer network enabling the same applications/service support functions to be adopted for the network.
+
+
+
+The diagram shows a 'Unified/Converged network' represented by a large grey rectangle. It is divided into three horizontal layers by dashed lines. The top layer is labeled 'Management layer' and contains a box for 'Charging and billing functions'. The middle layer is labeled 'Application layer' and contains two boxes: 'Applications' and 'Application/Service support functions'. The bottom layer is labeled 'Control layer' and contains a box for 'Service control functions'. Below the main rectangle, two ovals are shown: 'Fixed access network' on the left and 'Mobile access network' on the right. Both ovals have lines connecting them to the 'Service control functions' box in the Control layer. The text 'Q.1762/Y.2802(07)\_FI.1' is located in the bottom right corner of the diagram area.
+
+Diagram illustrating the convergence in service control functions. A central 'Unified/Converged network' box is divided into three layers: Management layer (top), Application layer (middle), and Control layer (bottom). The Management layer contains 'Charging and billing functions'. The Application layer contains 'Applications' and 'Application/Service support functions'. The Control layer contains 'Service control functions'. Below the box, two ovals represent 'Fixed access network' and 'Mobile access network', both connected to the Control layer. A dashed line separates the Management layer from the Application layer, and another dashed line separates the Application layer from the Control layer. The label 'Q.1762/Y.2802(07)\_FI.1' is in the bottom right corner.
+
+**Figure I.1 – Scenario: Convergence in service control functions**
+
+NOTE – IMS-based solution described in [ITU-T Y.2021] uses the access-independent IMS network to support different accesses to provide FMC services. The UMA solution [b-ETSI TS 143 318] uses the unified GSM/UMTS network to provide FMC services.
+
+### I.2 Convergence in application layer
+
+In this scenario, the different service control network is used to provide the service when the user accesses FMC using fixed access network or mobile access network. Convergence does not occur in the service control layer (call control or session control functions), but occurs in the service support functions in the application layer as illustrated in Figure I.2.
+
+
+
+Q.1762/Y.2802(07)\_FI.2
+
+Diagram of Figure I.2: Scenario: Convergences in application/service support functions. The diagram shows three layers: Management layer (top), Application layer (middle), and Control layer (bottom). The Management layer contains 'Charging and billing functions'. The Application layer contains 'Applications' and 'Application/Service support functions'. The Control layer contains 'Service control functions'. The diagram is split into 'Fixed network' and 'Mobile network' sections. At the bottom, 'Fixed access network' and 'Mobile access network' are shown. The 'Application/Service support functions' are shared between the fixed and mobile networks, indicating convergence. The 'Service control functions' are separate for each network. Reference Q.1762/Y.2802(07)\_FI.2 is at the bottom right.
+
+**Figure I.2 – Scenario: Convergences in application/service support functions**
+
+NOTE – The example in Figure I.2 is a scenario where convergence occurs in the application/service support functions.
+
+Convergence may also occur only in the applications in the application layer as shown in Figure I.3.
+
+
+
+Q.1762/Y.2802(07)\_FI.3
+
+Diagram of Figure I.3: Scenario: Convergence in applications. The diagram shows three layers: Management layer (top), Application layer (middle), and Control layer (bottom). The Management layer contains 'Charging and billing functions'. The Application layer contains 'Applications' and 'Application/Service support functions'. The Control layer contains 'Service control functions'. The diagram is split into 'Fixed network' and 'Mobile network' sections. At the bottom, 'Fixed access network' and 'Mobile access network' are shown. The 'Applications' are shared between the fixed and mobile networks, indicating convergence. The 'Application/Service support functions' and 'Service control functions' are separate for each network. Reference Q.1762/Y.2802(07)\_FI.3 is at the bottom right.
+
+**Figure I.3 – Scenario: Convergence in applications**
+
+### I.3 Convergence in the management layer
+
+In this scenario, the control layer and the application layer of the fixed and mobile networks are unchanged, but some changes occur in the charging and billing functions to provide bundled billing of at least some services. This may also be referred to as FMC and is illustrated in Figure I.4.
+
+
+
+The diagram illustrates the network architecture for fixed and mobile networks, showing the convergence of charging and billing functions. It is divided into three horizontal layers by dashed lines, labeled on the right: Management layer, Application layer, and Control layer.
+
+- Management layer:** Contains a single box labeled "Charging and billing functions" that spans across both the fixed and mobile network columns.
+- Application layer:** Contains two identical columns. Each column has a box labeled "Applications" at the top, a box labeled "Application/Service support functions" in the middle, and a box labeled "Service control functions" at the bottom.
+- Control layer:** The bottom of the Application layer boxes ("Service control functions") connect to the "Fixed access network" (represented by an oval) on the left and the "Mobile access network" (represented by an oval) on the right.
+
+The left column is labeled "Fixed network" and the right column is labeled "Mobile network". A small text label "Q.1762/Y.2802(07)\_FI.4" is located in the bottom right corner of the diagram area.
+
+Diagram illustrating the convergence in charging and billing functions between fixed and mobile networks.
+
+**Figure I.4 – Scenario: Convergence in charging and billing functions**
+
+# Bibliography
+
+[b-ETSI TS 143 318] ETSI TS 143 318 (2008), *Digital cellular telecommunications system (Phase 2+); Generic Access Network (GAN); Stage 2.*
+
+## ITU-T Y-SERIES RECOMMENDATIONS
+
+## GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS
+
+### GLOBAL INFORMATION INFRASTRUCTURE
+
+| | |
+|-------------------------------------------|-------------|
+| General | Y.100–Y.199 |
+| Services, applications and middleware | Y.200–Y.299 |
+| Network aspects | Y.300–Y.399 |
+| Interfaces and protocols | Y.400–Y.499 |
+| Numbering, addressing and naming | Y.500–Y.599 |
+| Operation, administration and maintenance | Y.600–Y.699 |
+| Security | Y.700–Y.799 |
+| Performances | Y.800–Y.899 |
+
+### INTERNET PROTOCOL ASPECTS
+
+| | |
+|--------------------------------------------------------------------|---------------|
+| General | Y.1000–Y.1099 |
+| Services and applications | Y.1100–Y.1199 |
+| Architecture, access, network capabilities and resource management | Y.1200–Y.1299 |
+| Transport | Y.1300–Y.1399 |
+| Interworking | Y.1400–Y.1499 |
+| Quality of service and network performance | Y.1500–Y.1599 |
+| Signalling | Y.1600–Y.1699 |
+| Operation, administration and maintenance | Y.1700–Y.1799 |
+| Charging | Y.1800–Y.1899 |
+
+### NEXT GENERATION NETWORKS
+
+| | |
+|-------------------------------------------------------------------|----------------------|
+| Frameworks and functional architecture models | Y.2000–Y.2099 |
+| Quality of Service and performance | Y.2100–Y.2199 |
+| Service aspects: Service capabilities and service architecture | Y.2200–Y.2249 |
+| Service aspects: Interoperability of services and networks in NGN | Y.2250–Y.2299 |
+| Numbering, naming and addressing | Y.2300–Y.2399 |
+| Network management | Y.2400–Y.2499 |
+| Network control architectures and protocols | Y.2500–Y.2599 |
+| Security | Y.2700–Y.2799 |
+| Generalized mobility | Y.2800–Y.2899 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.2150.1-200105-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2150.1-200105-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..686d5282e8001d0effcc4ba1ad3454c23d4559c1
--- /dev/null
+++ b/marked/Q/T-REC-Q.2150.1-200105-I_PDF-E/raw.md
@@ -0,0 +1,1056 @@
+
+
+
+
+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.2150.1**
+
+(05/2001)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Broadband ISDN – Signalling ATM adaptation layer
+(SAAL)
+
+---
+
+**Signalling Transport Converter on MTP3 and
+MTP3b**
+
+ITU-T Recommendation Q.2150.1
+
+(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 |
+| General aspects | Q.2000-Q.2099 |
+| Signalling ATM adaptation layer (SAAL) | Q.2100-Q.2199 |
+| Signalling network protocols | Q.2200-Q.2299 |
+| Common aspects of B-ISDN application protocols for access signalling and network signalling and interworking | Q.2600-Q.2699 |
+| B-ISDN application protocols for the network signalling | Q.2700-Q.2899 |
+| B-ISDN application protocols for access signalling | Q.2900-Q.2999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+# **Signalling Transport Converter on MTP3 and MTP3b**
+
+## **Summary**
+
+This Recommendation specifies the Signalling Transport Converter on MTP3 and MTP3b. This Signalling Transport Converter on MTP utilizes the services offered by the Message Transfer Part of Signalling System No. 7. The sublayer structure, the PDU structures of the signalling transport converter sublayer, and the mechanisms for the provision of the generic signalling transport service are defined in depth.
+
+The intent of this Recommendation is to provide a protocol specification that can be used in the ISDN and B-ISDN environment for the provision of a signalling transport service. In particular, this protocol provides a Generic Signalling Transport Service that is used by AAL type 2 and Bearer Independent Call Control (BICC) signalling protocols.
+
+## **Source**
+
+ITU-T Recommendation Q.2150.1 was revised by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 15 May 2001.
+
+## **Keywords**
+
+ATM Adaptation Layer (AAL), Asynchronous Transfer Mode (ATM), Bearer Independent Call Control (BICC), Broadband Integrated Services Digital Network (B-ISDN), Message Transfer Part (MTP), Signalling AAL (SAAL), Signalling Transport Converter (STC).
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2001
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU.
+
+# CONTENTS
+
+| | | Page |
+|-------|-----------------------------------------------------------------------------------------------|------|
+| 1 | Scope..... | 1 |
+| 2 | References..... | 1 |
+| 2.1 | Normative references..... | 1 |
+| 2.2 | Bibliography ..... | 2 |
+| 3 | Definitions ..... | 2 |
+| 4 | Abbreviations..... | 2 |
+| 5 | General description of the Signalling Transport Converter on MTP3 and MTP3b.... | 3 |
+| 5.1 | Structure of the Signalling Transport Converter on MTP ..... | 3 |
+| 5.2 | Services provided by the STC ..... | 4 |
+| 5.3 | Functions of the STC ..... | 5 |
+| 6 | Elements for layer-to-layer communication ..... | 5 |
+| 6.1 | The Generic Signalling Transport Service..... | 5 |
+| 6.2 | The Service provided by MTP..... | 6 |
+| 6.2.1 | Primitive definition..... | 7 |
+| 6.2.2 | Parameter definition ..... | 7 |
+| 6.2.3 | Restart..... | 8 |
+| 6.3 | Primitives between the STC and layer management ..... | 8 |
+| 6.3.1 | Primitive definition..... | 8 |
+| 6.3.2 | Parameters ..... | 9 |
+| 6.4 | State transition diagram for sequences of primitives at the layer boundaries of the STC ..... | 9 |
+| 7 | Protocol elements for peer-to-peer communication..... | 10 |
+| 7.1 | STC PDUs..... | 10 |
+| 7.1.1 | STC PDU formats..... | 10 |
+| 7.1.2 | STC Signalling Message PDU fields..... | 10 |
+| 7.2 | STC state variable..... | 11 |
+| 7.3 | STC timers ..... | 11 |
+| 7.4 | Provisioned STC parameters ..... | 11 |
+| 8 | Specification of the STC..... | 12 |
+| 8.1 | Overview..... | 12 |
+| 8.1.1 | State 1: Service Unavailable..... | 12 |
+| 8.1.2 | State 2: STC Service Available ..... | 12 |
+| 8.1.3 | State 3: Congestion 1 ..... | 13 |
+| 8.1.4 | State 4: Congestion 2 ..... | 13 |
+| 8.2 | Procedures of the STC ..... | 15 |
+
+| | Page |
+|----------------------------------------------------------------------------------|-------------|
+| 8.2.1 Initial Conditions ..... | 15 |
+| 8.2.2 STC signalling message transfer procedure ..... | 15 |
+| 8.2.3 Destination availability procedure..... | 16 |
+| 8.2.4 Congestion Indication procedure..... | 16 |
+| 8.2.5 User Part availability ..... | 16 |
+| 8.3 State Transition Table..... | 17 |
+| 8.4 SDL diagrams ..... | 20 |
+| Appendix I – Protocol Implementation Conformance Statement (PICS) Proforma ..... | 26 |
+
+# Signalling Transport Converter on MTP3 and MTP3b
+
+# 1 Scope
+
+This Recommendation specifies the signalling transport converter sublayer on top of the message transfer part (MTP) specified in ITU-T Q.704 [4] "MTP3" and ITU-T Q.2210 [6] "MTP3b"; both Recommendations specify the peer-to-peer protocol for the transfer of information and control between any pair of MTP level 3 entities. Since the service provided by either of these Recommendations is the same, this Recommendation only describes the actions in terms of MTP3 for clarity of expression. This Recommendation covers the specification of the sublayer structure, the PDU structures of the signalling transport converter sublayer, and the mechanisms for the provision of the Generic Signalling Transport Service.
+
+When this Signalling Transport Converter on MTP is applied for a signalling protocol entity, that entity is liberated from considering peculiarities of the underlying signalling transport service. This is achieved by relying on a Generic Signalling Transport Service that is provided, for example, by the sublayer specified in this Recommendation.
+
+This Recommendation describes the interactions between the Signalling Transport Converter (STC) and the next higher layer, e.g. the AAL type 2 or BICC signalling protocol entity, between the STC and the Message Transfer Part, and between the STC and layer management.
+
+# 2 References
+
+## 2.1 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; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
+
+- [1] ITU-T Q.2150.0 (2001), *Generic signalling transport service*.
+- [2] ITU-T Q.701 (1993), *Functional description of the message transfer part (MTP) of Signalling System No. 7*.
+- [3] ITU-T Q.703 (1996), *Signalling link*.
+- [4] ITU-T Q.704 (1996), *Signalling network functions and messages*.
+- [5] ITU-T Q.764 (1999), *Signalling System No. 7 – ISDN User Part signalling procedures*.
+- [6] ITU-T Q.2210 (1996), *Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140*.
+- [7] ITU-T X.200 (1994), *Information technology – Open Systems Interconnection – Basic reference model: The basic model*.
+- [8] ITU-T X.210 (1993), *Information technology – Open Systems Interconnection – Basic reference model: Conventions for the definition of OSI services*.
+
+## 2.2 Bibliography
+
+The following ITU-T Recommendations and other publications contain information that may be useful to understanding the usage of this Recommendation. There are no additional provisions of this Recommendation derived from these publications.
+
+- [9] ITU-T Q.2140 (1995), *B-ISDN ATM adaptation layer – Service specific coordination function for signalling at the network node interface (SSCF at NNI)*.
+- [10] ITU-T Q.2630.1 (1999), *AAL type 2 signalling protocol – Capability Set 1*.
+- [11] ITU-T Q.2630.2 (2000), *AAL type 2 signalling protocol – Capability Set 2*.
+- [12] ITU-T Q.1901 (2001), *Bearer independent call control protocol*.
+- [13] ITU-T Q.1902.1 (2001), *Bearer independent call control protocol CS2 functional description*.
+- [14] IETF RFC 791 (1981), *Internet Protocol*.
+- [15] IETF RFC 2474 (1998), *Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers*.
+
+# 3 Definitions
+
+This Recommendation is based upon the concepts developed in ITU-T X.200 [7] and X.210 [8].
+
+# 4 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+- AAL ATM Adaptation Layer
+- ATM Asynchronous Transfer Mode
+- CL Congestion Level
+- DPC Destination Point Code
+- MTP Message Transfer Part
+- NI Network Indicator
+- NNI Network Node Interface
+- OPC Originating Point Code
+- PDU Protocol Data Unit
+- PICS Protocol Implementation Conformance Statement
+- SAP Service Access Point
+- SDL Specification and Description Language
+- SDU Service Data Unit
+- SI Service Indicator
+- SIO Service Information Octet
+- SLS Signalling Link Selection code
+- STC Signalling Transport Converter
+
+# **5 General description of the Signalling Transport Converter on MTP3 and MTP3b**
+
+## **5.1 Structure of the Signalling Transport Converter on MTP**
+
+The sublayer providing the Signalling Transport Converter (STC) resides on top of the Message Transfer Part. It uses the services provided by level 3 of the Message Transfer Part defined in ITU-T Q.704 [4] and Q.2210 [6].
+
+The STC provides the service that is requested by the Generic Signalling Transport Service defined in ITU-T Q.2150.0 [1], where the signalling protocol makes use of this service. The complete protocol stack is illustrated in Figure 5-1.
+
+This Recommendation specifies:
+
+- the interactions between the STC and the signalling protocol entity;
+- the interactions between the STC and the MTP level 3 sublayer; and
+- the interactions between the STC and layer management.
+
+
+
+The diagram illustrates the structure of the Signalling Transport Converter on MTP. At the top is the **Signalling Application**. Below it, the **Generic Signalling Transport Service** (ITU-T Q.2150.0) is accessed via a **SAP** using **Primitives**. The **Signalling Transport Converter on MTP3 and MTP3b** (this Recommendation) (ITU-T Q.2150.1) is shown in the center. Below the converter, there are two main paths: **MTP3** (ITU-T Q.704) and **MTP3b** (ITU-T Q.2210). **MTP3** connects to **MTP2** (ITU-T Q.703) via a **SAP** and **Primitives**. **MTP3b** connects to **SSCF-NNI** (ITU-T Q.2140) via a **SAP** and **Primitives**. Below **SSCF-NNI**, there are three example transport paths: **SSCOP** (ITU-T Q.2110) which connects to **AAL type 5** (ITU-T I.363.5) containing **CPCS** and **SAR**; **SSCOPMCE** (ITU-T Q.2111) which connects to **AAL type 5** (ITU-T I.363.5) containing **CPCS** and **SAR**; and **IP DIFFSERV** which uses **IETF RFC 791** and **IETF RFC 2474**. A vertical bracket on the left labeled **EXAMPLES** groups the **MTP2**, **SSCOP**, and **SSCOPMCE** paths.
+
+Diagram showing the structure of the Signalling Transport Converter on MTP. It illustrates the layers and interfaces for both MTP3 and MTP3b. At the top is the Signalling Application connected via a SAP to the Generic Signalling Transport Service (ITU-T Q.2150.0). Below this is the Signalling Transport Converter on MTP3 and MTP3b (ITU-T Q.2150.1). The converter connects to MTP3 (ITU-T Q.704) and MTP3b (ITU-T Q.2210) via SAPs. MTP3 connects to MTP2 (ITU-T Q.703). MTP3b connects to SSCF-NNI (ITU-T Q.2140). Below SSCF-NNI are examples of transport paths: one through SSCOP (ITU-T Q.2110) to AAL type 5 (ITU-T I.363.5) with CPCS and SAR; another through SSCOPMCE (ITU-T Q.2111) to AAL type 5 (ITU-T I.363.5) with CPCS and SAR; and a third through IP DIFFSERV with IETF RFC 791 and IETF RFC 2474. A vertical bracket on the left labeled 'EXAMPLES' groups the MTP2, SSCOP, and SSCOPMCE paths.
+
+NOTE – The Service Access Points shown in this diagram are for modelling purposes only. They are not necessarily visible or accessible from outside.
+
+**Figure 5-1/Q.2150.1 – Structure of the Signalling Transport Converter on MTP**
+
+## 5.2 Services provided by the STC
+
+The STC provides for the transparent transfer of data, i.e. signalling application (STC user) data between peer STC users. The supporting communication resources to achieve this transfer stay invisible to the signalling application.
+
+In particular, the STC service provides for:
+
+### a) *Independence from the underlying transmission media*
+
+The STC service relieves its users from all concerns of the manner in which the STC service is provided. Except for possible influences of the quality of service, the transfer of data over different underlying networks is, thus, invisible.
+
+### b) *Transparency of the information transferred*
+
+The STC service provides for the transparent transfer of octet-aligned STC user data. It does not restrict the content, format, or coding of the information nor is there ever a need to interpret its structure or meaning.
+
+### c) *Service Availability Reporting*
+
+As the underlying service (MTP) reports about availability/unavailability of the data transfer service, after the necessary translation, these notifications are forwarded to the STC user.
+
+## 5.3 Functions of the STC
+
+The STC performs the following functions:
+
+### a) *Data transfer service availability reporting to the STC user*
+
+This function reports the availability or unavailability of the MTP message transfer service to the user of the STC.
+
+### b) *Congestion reporting to the STC user*
+
+This function translates and forwards the congestion indications provided by the MTP to the STC user.
+
+### c) *Maximum length indication to the STC user*
+
+This function indicates to the STC user the maximum length of the PDU that the STC can transfer; it is indicated at creation of the STC entity.
+
+### d) *CIC control indication to the STC user*
+
+This function indicates to the STC user, at creation of the STC entity, whether it serves as the controlling node of the call association.
+
+# 6 Elements for layer-to-layer communication
+
+## 6.1 The Generic Signalling Transport Service
+
+The Generic Signalling Transport Service is specified in ITU-T Q.2150.0 [1]. For convenience, a summary of the primitives for accessing the service is reproduced in Table 6-1. In the event of any difference between this table and the definitions in ITU-T Q.2150.0, the definitions in ITU-T Q.2150.0 take precedence.
+
+**Table 6-1/Q.2150.1 – Primitives and parameters of the Generic Signalling Transport Sublayer**
+
+| Primitive
Generic Name | Type | | | |
+|---------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|------------------------------------|----------|---------|
+| | Request | Indication | Response | Confirm |
+| START-INFO | – | Max_Length
CIC_Control | – | – |
+| IN-SERVICE | – | Level | – | – |
+| OUT-OF-SERVICE | – | (Note 1) | – | – |
+| CONGESTION | – | Level | – | – |
+| TRANSFER | Sequence Control
STC User Data
Priority (Note 2) | STC User Data
Priority (Note 2) | – | – |
+| – This primitive is not defined.
NOTE 1 – This primitive has no parameters.
NOTE 2 – This parameter is a national option. | | | | |
+
+On the establishment of a Signalling Transport Converter entity and the associated Signalling Transport Converter user entity, for example at power up, the initial conditions is the same as if an OUT-OF-SERVICE.indication primitive had been conveyed across this SAP. Also at this time the START-INFO.indication is sent to the signalling entity.
+
+## 6.2 The Service provided by MTP
+
+This clause specifies the information flow across the Signalling Transport Converter-Message Transfer Part (MTP) boundary. This boundary is defined in 8/Q.701 [2] and 6.2/Q.2210 [6] and summarized below. In the event of any difference between the following summary and the definitions in ITU-T Q.701 or Q.2210, the definitions in ITU-T Q.701 or Q.2210 take precedence.
+
+The primitives and parameters between STC and MTP are shown in Table 6-2.
+
+NOTE – This service corresponds to the "Specific Signalling Transport Service" in Figure 5-1 in ITU-T Q.2150.0.
+
+**Table 6-2/Q.2150.1 – Primitives and parameters of the Message Transfer Part**
+
+| Primitive
Generic Name | Type | | | |
+|----------------------------------|------------------------------------|------------------------------------|----------|---------|
+| | Request | Indication | Response | Confirm |
+| MTP-TRANSFER | OPC, DPC,
SLS, SIO,
UserData | OPC, DPC,
SLS, SIO,
UserData | – | – |
+| MTP-PAUSE (Stop) | – | Affected DPC | – | – |
+| MTP-RESUME (Start) | – | Affected DPC | – | – |
+| MTP-STATUS | – | Affected DPC
Cause | – | – |
+| – This primitive is not defined. | | | | |
+
+### 6.2.1 Primitive definition
+
+The definition of these primitives is as follows:
+
+#### a) **MTP-TRANSFER:**
+
+The primitive "MTP-TRANSFER" is used between level 4 and level 3 (SMH) to provide the MTP message transfer service, i.e. to transfer STC PDUs from one STC peer entity to the other.
+
+#### b) **MTP-RESUME:**
+
+The primitive "MTP-RESUME" indicates to the "User" the ability of providing the MTP service to the specified destination (see 7.2.6/Q.701 [2]).
+
+This primitive corresponds to the destination accessible state as defined in ITU-T Q.704 [4].
+
+NOTE 1 – When the MTP-RESUME indication is given to each user, the MTP does not know whether the remote peer user is available. This is the responsibility of each user.
+
+#### c) **MTP-PAUSE:**
+
+The primitive "MTP-PAUSE" indicates to the "Users" the total inability of providing the MTP service to the specified destination (see 7.2.6/Q.701 [2]).
+
+NOTE 2 – The signalling point is inaccessible via the MTP. The MTP will determine when the signalling point is again accessible and send MTP-RESUME indication. The user should wait for such an indication and, meanwhile is not allowed to send messages to that signalling point. If the remote peer user is thought to be unavailable, that condition may be maintained or cancelled at the local user's discretion.
+
+#### d) **MTP-STATUS:**
+
+The primitive "MTP-STATUS" indicates to the "Users" the partial inability of providing the MTP service to the specified destination. The primitive is also used to indicate to a User that a remote corresponding User is unavailable and the cause for unavailability (see 11.2.7/Q.704 [4]).
+
+In the case of national option with congestion priorities or multiple signalling link congestion states without priorities as in ITU-T Q.704 [4] are implemented, this "MTP-STATUS" primitive is also used to indicate a change of congestion level.
+
+This primitive corresponds to the destination congested/User Part unavailable state as defined in Q.704 [4].
+
+NOTE 3 – In the case of remote user unavailability, the user is responsible for determining the availability of this peer user. The user is cautioned not to send normal traffic to the peer user because, while such peer is unavailable, no message will be delivered but each will result in a repeated MTP-STATUS indication. The MTP will not send any further indications about the unavailability or availability of this peer user unless the local user continues to send messages to the peer user.
+
+### 6.2.2 Parameter definition
+
+Table 6-2 lists the parameters associated with each MTP primitive. The definition of the parameters is as follows:
+
+#### a) **Point code of the originating exchange (OPC):**
+
+The OPC parameter indicates the originating point of the message (see 2.2.3/Q.704 [4]).
+
+NOTE 1 – This parameter is a fixed value per STC entity.
+
+#### b) **Point code of the destination exchange (DPC):**
+
+The DPC parameter indicates the destination point of the message (see 2.2.3/Q.704 [4]).
+
+NOTE 2 – This parameter is a fixed value per STC entity.
+
+#### c) **Signalling Link Selection code (SLS):**
+
+Selection of the SLS parameter is based on the Sequence Control parameter received in the TRANSFER.request primitive (see 2.2.4/Q.704 [4]).
+
+NOTE 3 – The MTP users should take into account that this parameter is used for load sharing by the MTP, therefore, the SLS values should be distributed as equally as possible. The MTP guarantees (to a high degree of probability) an in-sequence delivery of messages that contain the same SLS code.
+
+#### d) **Service Information Octet (SIO):**
+
+The service information octet of message signal units contains the service indicator (SI) and the subservice field. The service indicator indicates an STC user entity, e.g. BICC, AAL type 2 signalling, etc. (see 14.2/Q.704 [4]).
+
+#### e) **User Data:**
+
+The User Data parameter carries the PDUs constructed before transmission and interpreted upon receipt by the STC (see 2.3.8/Q.703 [3]).
+
+#### f) **Cause:**
+
+The cause parameter has, at present, four values:
+
+1) Signalling network congestion (plus optional level).
+
+The level value is included if national options with congestion priorities or multiple signalling link states without congestion priorities as in ITU-T Q.704 [4] are implemented.
+
+2) User part unavailability – unknown.
+
+3) User part unavailability – unequipped remote user.
+
+4) User part unavailability – inaccessible remote user.
+
+#### g) **Affected DPC:**
+
+Destination Point Code identifying the node, the state of which is reported by the corresponding primitive (see 7.2.6/Q.701 [2]).
+
+### **6.2.3 Restart**
+
+When the MTP restart procedure is terminated, the MTP indicates the end of MTP restart to all local MTP Users showing each signalling point's accessibility or inaccessibility. The means of doing this is implementation dependent (see 9/Q.704 [4]).
+
+## **6.3 Primitives between the STC and layer management**
+
+This clause specifies the information flow across the STC-Layer Management boundary.
+
+The primitive between STC and layer management is listed in Table 6-3.
+
+**Table 6-3/Q.2150.1 – Primitives and parameters between the STC and layer management**
+
+| Primitive
Generic Name | Type | | | |
+|----------------------------------|---------|------------|----------|---------|
+| | Request | Indication | Response | Confirm |
+| MSTC-ERROR | – | Cause | – | – |
+| – This primitive is not defined. | | | | |
+
+### **6.3.1 Primitive definition**
+
+#### • **MSTC-ERROR:**
+
+MSTC-ERROR primitives are used to inform layer management about errors.
+
+### 6.3.2 Parameters
+
+- **Cause:**
+The cause parameter can indicate the following errors:
+ - a) user part unavailable (unknown);
+ - b) user part unavailable (inaccessible); and
+ - c) user part unequipped.
+
+## 6.4 State transition diagram for sequences of primitives at the layer boundaries of the STC
+
+This clause defines the constraints on the sequences in which the primitives may occur at the layer boundaries of the STC. The sequences are related to the states at one STC endpoint between the STC and the STC user and between the STC and MTP.
+
+The possible overall sequences of primitives at an STC connection endpoint are defined in ITU-T Q.2150.0 [1] and shown in the state transition diagram, Figure 6-1, for convenience. The primitives and state transitions are defined in ITU-T Q.2150.0 [1]. If any discrepancy is detected between the representation here and the one in ITU-T Q. 2150.0, the definition in ITU-T Q. 2150.0 shall apply. The model assumes that the primitives are serviced immediately and in zero time.
+
+
+
+```
+stateDiagram-v2
+ [*] --> Out_of_Service : START-INFO.indication
+ state "Out of Service" as Out_of_Service {
+ <>
+ TRANSFER.request --> Out_of_Service : TRANSFER.indication
+ }
+ state "In Service" as In_Service {
+ <>
+ TRANSFER.request --> In_Service : TRANSFER.indication
+ CONGESTION.indication --> In_Service
+ }
+ Out_of_Service --> In_Service : IN-SERVICE.indication
+ In_Service --> Out_of_Service : OUT-OF-SERVICE.indication
+```
+
+State transition diagram for sequences of primitives between the STC and its user. The diagram shows two states: 'Out of Service' (labeled 1) and 'In Service' (labeled 2). Transitions are triggered by primitives. From 'Start', a 'START-INFO.indication' leads to 'Out of Service'. From 'Out of Service', an 'IN-SERVICE.indication' leads to 'In Service'. From 'In Service', an 'OUT-OF-SERVICE.indication' leads back to 'Out of Service'. Both states have self-loops for 'TRANSFER.request' and 'TRANSFER.indication' primitives. The 'In Service' state also has a self-loop for 'CONGESTION.indication'. The diagram is labeled T11112780-01.
+
+**Figure 6-1/Q.2150.1 – State transition diagram for sequences of primitives between the STC and its user**
+
+The possible overall sequences of primitives at a MTP endpoint are shown in the state transition diagram in Figure 6-2. These primitives and state transitions are defined in ITU-T Q.2210 [6]. If any discrepancy is detected between the representation here and the one in ITU-T Q.2210, the definition in ITU-T Q.2210 shall apply.
+
+The model in Figure 6-2 illustrates the behaviour of the MTP as seen by the STC. This model assumes that a request or response primitive is never issued at the same time as an indication or confirm primitive. The model also assumes that the primitives are serviced immediately and in zero time. In the diagram:
+
+- a) Any primitive that is not shown to result in a transition (from one state to the same state, or from one state to a different state) is not permitted in that state.
+- b) It is assumed that the primitives passed between STC and the STC user as well as the primitives passed between the STC and MTP are coordinated such that collisions do not occur.
+
+NOTE – The MTP-STATUS.indication can indicate either the unavailability for a remote MTP user or MTP congestion.
+
+
+
+State transition diagram for sequences of primitives between MTP and STC. It shows two states: 'MTP Signalling Relation unavailable' (state 2) and 'MTP Signalling Relation available' (state 3). Transitions between states are triggered by MTP primitives. From state 2 to state 3, the trigger is 'MTP-PAUSE.indication'. From state 3 to state 2, the trigger is 'MTP-RESUME.indication'. Self-loops on each state are triggered by 'MTP-TRANSFER.indication' and 'MTP-STATUS.indication'. The diagram is labeled T11112790-01.
+
+**Figure 6-2/Q.2150.1 – State transition diagram for sequences of primitives between MTP and STC**
+
+# 7 Protocol elements for peer-to-peer communication
+
+The peer-to-peer STC protocol utilizes the mechanisms provided by the underlying sublayer (MTP3 or MTP3b, ITU-T Q.704 [4] or ITU-T Q.2210 [6]). In particular:
+
+- In order to provide service availability information it uses the information received in MTP-PAUSE.indication and MTP-RESUME.indication primitives.
+- In order to provide congestion indication, it relies on the information received in MTP-STATUS.indication primitives.
+- STC PDU transfer utilizes the MTP-TRANSFER.request and MTP-TRANSFER.indication primitives. MTP-TRANSFER.request is used for sending PDUs while MTP-TRANSFER.indication is used for receiving PDUs.
+
+## 7.1 STC PDUs
+
+### 7.1.1 STC PDU formats
+
+The following STC messages (PDUs) are used for exchanging information between peer STC entities:
+
+#### STC signalling message
+
+This PDU is used for carrying STC signalling messages to a peer STC entity via the MTP network. The length of such a signalling message may not exceed the maximum length indicated in the Max\_Length parameter. The STC is not adding any Protocol Control Information to the message. Figure 7-1 illustrates the format of the STC PDU.
+
+
+
+Diagram of STC Signalling Message PDU format. It shows a horizontal bar representing the PDU. The first byte is labeled 'Octet 1' and the last byte is labeled 'Octet N'. The middle section is labeled 'STC User Data'. The diagram is labeled T11112800-01.
+
+**Figure 7-1/Q.2150.1 – STC Signalling Message PDU**
+
+### 7.1.2 STC Signalling Message PDU fields
+
+An STC Signalling Message PDU contains the following field:
+
+- **STC User Data field:**
+
+This field in the STC Signalling Message PDU contains a complete STC-SDU.
+
+## 7.2 STC state variable
+
+The STC maintains the following state variable:
+
+### - **Congestion Level (CL):**
+
+This variable can hold the values from a level indicating "no congestion" through to a level indicating "maximum congestion" in increments.
+
+NOTE – The number of steps of congestion level and/or amount of increase/decrease is considered to be network implementation dependent.
+
+## 7.3 STC timers
+
+The STC entity requires the following timers:
+
+### - a) **Timer\_Long:**
+
+This timer corresponds to timer T30, see 2.10.2/Q.764 [5].
+
+NOTE 1 – This timer is used by the congestion indication procedure. Receipt of a repeated congestion indication from MTP before the expiry of this timer is interpreted as the congestion situation having worsened in the meantime. On the other hand, if no congestion indication is received from MTP before expiry of this timer, the congestion situation is considered to have improved.
+
+### - b) **Timer\_Short:**
+
+This timer corresponds to timer T29, see 2.10.2/Q.764 [5].
+
+NOTE 2 – This timer is used by the congestion indication procedure. The role of this timer is to avoid overreacting if multiple congestion indications are received from MTP in quick succession.
+
+## 7.4 Provisioned STC parameters
+
+STC parameters are specified at the creation of a new STC entity and are unchanged during the lifetime of the STC entity. The following parameters are defined:
+
+### - a) **STC\_DPC:**
+
+Point Code corresponding to the destination point served by the STC entity.
+
+### - b) **STC\_OPC:**
+
+Point Code corresponding to the originating point served by the STC entity.
+
+### - c) **STC\_SIO:**
+
+The service information octet contains the service indicator (SI) and the subservice field. The subservice field carries the network indicator bits and spare bits; the spare bits are for national use to indicate message priority. The network indicator (NI) must indicate to which network the signalling relation belongs. The service indicator must indicate the STC user, e.g. "AAL type 2 signalling", "BICC signalling", etc.
+
+NOTE 1 – The value of the Service Indicator for the Bearer Independent Call Control is "13" (see ITU-T Q.704 [4] and Q.2210 [6] and their respective Implementors' Guides).
+
+NOTE 2 – The value of the Service Indicator for the AAL type 2 signalling is "12" (see ITU-T Q.704 [4] and Q.2210 [6] and their respective Implementors' Guides).
+
+### - d) **Value of Timer\_Long (vTimer\_Long):**
+
+The value of Timer\_Long is defined in 2.10.2/Q.764 [5] as the value for timer T30.
+
+NOTE 3 – Timer\_Long is typically in the range of 5 to 10 seconds.
+
+### - e) **Value of Timer\_Short (vTimer\_Short):**
+
+The value of Timer\_Short is defined in 2.10.2/Q.764 [5] as the value for timer T29.
+
+NOTE 4 – Timer\_Short is typically in the range of 0.3 to 0.6 seconds.
+
+### f) **Value of Max\_Length:**
+
+The value of Max\_Length can be set to either "272" or "4096".
+
+NOTE 5 – The value of the Max\_Length parameter is chosen by network operators.
+
+NOTE 6 – The Max\_Length parameter is a characterization of the underlying MTP length limitation; this value includes the MTP header. For precise information see ITU-T Q.704 [4] and Q.2210 [6].
+
+NOTE 7 – The Max\_Length parameter is set as follows:
+
+- If the STC is deployed in an MTP3 signalling relation, the Max\_Length parameter is set to "272".
+- If the STC is deployed in an MTP3b signalling relation, the Max\_Length parameter is set to "272" or "4096". The value to be provisioned is chosen by network operators.
+
+### g) **Value of Congestion Level "no congestion" (CLnc):**
+
+This value is used in the CONGESTION.indication and IN-SERVICE.indication primitives to indicate "no congestion".
+
+### h) **Value of Congestion Level "maximum congestion" (CLmc):**
+
+This value is used in the CONGESTION.indication and IN-SERVICE.indication primitives to indicate "maximum congestion".
+
+### i) **Value "step" for Congestion Levels (CLst):**
+
+This value indicates the amount of increase or decrease of congestion levels.
+
+NOTE 8 – Variable sizes of the value "step" are not shown in this Recommendation; nevertheless, they are explicitly allowed.
+
+NOTE 9 – The values for indication "no congestion" and "maximum congestion" as well as the number of steps of congestion level and/or amount of increase/decrease are considered to be network implementation dependent.
+
+NOTE 10 – In BICC CS 1 (see ITU-T Q.1901 [12]), the value for "no congestion" is set to "0", the value for "maximum congestion" is set to "10", and the value for "step" is set to "1".
+
+NOTE 11 – The value of the CIC\_Control parameter of the START-INFO primitive is computed at power-up from the values of the STC parameters STC\_DPC and STC\_OPC, i.e. it need not be provisioned.
+
+# 8 Specification of the STC
+
+This clause provides a set of SDL diagrams defining the procedures of the Signalling Transport Converter (STC). These SDL diagrams are the definitive description of the procedures and in case of conflict with the text, the SDL diagrams take precedence.
+
+## 8.1 Overview
+
+Figure 8-1 gives an overview about the states of STC and the major state transitions between them. The full specification of the STC state transitions can be found in 8.4.
+
+These states are used in the specification of the peer-to-peer protocol. The states are conceptual and reflect the general condition of the STC entity in the sequences of primitives and PDU exchanges with its user, peer, underlying sublayer.
+
+### 8.1.1 State 1: Service Unavailable
+
+In this state, STC is not able to transfer signalling messages.
+
+### 8.1.2 State 2: STC Service Available
+
+In this state, STC is able to provide unrestricted transfer of signalling messages.
+
+### **8.1.3 State 3: Congestion 1**
+
+In this state, STC is able to provide a restricted service because of congestion in the signalling network. Both Timer\_Short and Timer\_Long are running in this state.
+
+### **8.1.4 State 4: Congestion 2**
+
+In this state, STC is able to provide a restricted service because of congestion in the signalling network. Timer\_Long is running in this state.
+
+
+
+The diagram illustrates the state transitions for the STC (Service Transfer Control) across four states:
+
+- STC Service Unavailable (State 1):**
+ - Entry: **TRANSFER.request**
+ - Exit to State 2: **MTP-RESUME.indication** (Note 1), **IN-SERVICE.indication** (Note 1)
+ - Exit to State 3: **MTP-PAUSE.indication**, **OUT-OF-SERVICE.indication**
+ - Self-loops: **MTP-PAUSE.indication**, **OUT-OF-SERVICE.indication**; **MTP-TRANSFER.indication**, **TRANSFER.indication**
+- STC Service Available (State 2):**
+ - Entry from State 1: **MTP-RESUME.indication** (Note 1), **IN-SERVICE.indication** (Note 1), **start Timer\_Long**
+ - Exit to State 1: **MTP-PAUSE.indication**, **OUT-OF-SERVICE.indication**
+ - Exit to State 3: **TRANSFER.request**, **MTP-TRANSFER.request**
+ - Self-loops: **MTP-TRANSFER.indication**, **TRANSFER.indication**; **MTP-STATUS.indication**, **CONGESTION.indication**, **start Timer\_Long**, **start Timer\_Short**
+- Congestion 1 (State 3):**
+ - Entry from State 2: **TRANSFER.request**, **MTP-TRANSFER.request**
+ - Exit to State 2: **MTP-STATUS.indication**, **Timer\_Short**
+ - Self-loops: **MTP-TRANSFER.indication**, **TRANSFER.indication**; **MTP-STATUS.indication**, **CONGESTION.indication**, **re-start Timer\_Long**, **start Timer\_Short** (Note 4)
+- Congestion 2 (State 4):**
+ - Entry from State 3: **MTP-STATUS.indication**, **Timer\_Short**
+ - Exit to State 3: **Timer\_Long**, **CONGESTION.indication** (Note 2), **start Timer\_Long**
+ - Self-loops: **TRANSFER.request**, **MTP-TRANSFER.request**; **MTP-TRANSFER.indication**, **TRANSFER.indication**; **MTP-STATUS.indication**, **re-start Timer\_Long** (Note 3)
+
+Additional transitions and indications:
+
+- From State 2 to State 4: **MTP-PAUSE.indication**, **OUT-OF-SERVICE.indication**, **stop Timer\_Long**, **stop Timer\_Short** (Note 1)
+- From State 4 to State 2: **MTP-PAUSE.indication**, **OUT-OF-SERVICE.indication**, **stop Timer\_Long**
+
+State transition diagram for STC states showing four states: STC Service Unavailable (1), STC Service Available (2), Congestion 1 (3), and Congestion 2 (4). Transitions are triggered by various MTP and TRANSFER messages and include timer actions like start/stop/re-start Timer\_Long and Timer\_Short. Notes 1-4 provide conditions for specific transitions based on the Congestion Level (CL).
+
+NOTE 1 – This transition is executed if CL is zero.
+
+NOTE 2 – This transition is executed if CL is non-zero.
+
+NOTE 3 – This transition is executed if CL is equal to 10.
+
+NOTE 4 – This transition is executed if CL is not equal to 10.
+
+T11112810-01
+
+Figure 8-1/Q.2150.1 – Overview of STC states and major transitions between them
+
+## 8.2 Procedures of the STC
+
+### 8.2.1 Initial Conditions
+
+This clause specifies how the STC operates at power up.
+
+When the STC is initialized, it determines the CIC\_Control parameter and indicates it, together with the parameter Max\_Length, to the STC user in the START-INFO.indication primitive.
+
+The CIC\_Control parameter is computed the following way:
+
+- If the value of the STC\_OPC parameter is greater than the value of the STC\_DPC parameter, then the CIC\_Control shall be set to **EVEN**.
+- If the value of the STC\_DPC parameter is greater than the value of the STC\_OPC parameter, then the CIC\_Control shall be set to **ODD**.
+
+NOTE – If BICC receives a CIC\_Control parameter set to **EVEN** then it is controlling node for **EVEN** CIC values of the call association; if it receives a CIC\_Control parameter set to **ODD** then it is controlling node for **ODD** CIC values of the call association.
+
+If an MTP-RESUME.indication primitive is received by the STC, the MTP service is successfully initialized towards its peer MTP. STC then sends an IN-SERVICE.indication primitive to the STC user signalling entity. The IN-SERVICE.indication primitive carries a Level parameter; the value of the parameter is network dependent. If the Level indicates congestion, then congestion indication procedure (specified in 8.2.4.) is started.
+
+### 8.2.2 STC signalling message transfer procedure
+
+#### 8.2.2.1 Sending a signalling message
+
+Upon receipt of a TRANSFER.request primitive from the STC user, the STC shall place the signalling message unaltered into an STC Signalling Message PDU and derive the Signalling Link Selection Value (SLS) from the received Sequence Control parameter. It shall then transfer the PDU to the MTP using the MTP-TRANSFER.request primitive. The primitive carries the parameters shown in Table 8-1.
+
+**Table 8-1/Q.2150.1 – Parameters in the MTP-TRANSFER.request primitive**
+
+| Parameter | Content |
+|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|
+| MTP User Data | unaltered STC Signalling Message as received in the STC user Data parameter |
+| Point code of the originating exchange | value of STC_OPC provisioned parameter |
+| Point code of the destination exchange | value of STC_DPC provisioned parameter |
+| Service Information Octet | value of STC_SIO provisioned parameter (Note) |
+| Signalling Link Selection Value (SLS) | derived from received Sequence Control parameter |
+| NOTE – The SIO may be augmented, as a national option, with priority indication with the value received in the Priority parameter. | |
+
+#### 8.2.2.2 Receiving a signalling message
+
+Upon receipt of an MTP-TRANSFER.indication primitive containing an STC Signalling Message PDU, the STC shall pass the MTP User Data unaltered to the STC user in a TRANSFER.indication primitive. As a national option, the TRANSFER.indication primitive may indicate priority as extracted from the Service Information Octet.
+
+All the other parameters (OPC, DPC, SIO and SLS) are ignored.
+
+### 8.2.3 Destination availability procedure
+
+On the reception of an MTP-PAUSE.indication primitive by the STC, an OUT-OF-SERVICE.indication primitive is transmitted to the STC user. Layer Management is informed.
+
+On the reception of an MTP-RESUME.indication primitive by the STC, an IN-SERVICE.indication primitive is transmitted to the STC user. IN-SERVICE.indication carries a Level parameter; the value of the parameter is network dependent. If the Level indicates congestion then the congestion indication procedure (specified in 8.2.4) is started.
+
+NOTE 1 – The Level value used here can be different from the value used at start up.
+
+NOTE 2 – With the concept of one STC entity per "DPC OPC SI NI" quadruplet, the primitives MTP-PAUSE.indication and MTP-RESUME.indication are always routed to the STC entity whose provisioned parameter "STC\_DPC" is identical to the parameter "Affected DPC" in the primitives.
+
+### 8.2.4 Congestion Indication procedure
+
+On receipt of a MTP-STATUS.indication primitive with the cause set to "signalling network congestion", the STC acts as follows:
+
+- 1) When the first congestion indication is received by the STC, a CONGESTION.indication primitive with the parameter Level indicating onset of congestion shall be issued towards the STC user. At the same time, timers Timer\_Short and Timer\_Long shall be started.
+- 2) While Timer\_Short is running, all received congestion indications for the same destination point code shall be ignored in order not to reduce traffic too rapidly.
+- 3) Reception of a congestion indication after the expiry of timer Timer\_Short, but still while Timer\_Long is running, shall result in the transfer of a CONGESTION.indication primitive being sent to the STC user. It contains a Level parameter that is stepped up from the previous level. At the same time, Timer\_Short and Timer\_Long shall be restarted.
+- 4) This stepwise increase of the congestion level shall continue until a maximum level is reached by arriving at the last step.
+- 5) If Timer\_Long expires (i.e. no congestion indications have been received while Timer\_Long was running), a CONGESTION.indication containing the Level parameter that is stepped down from the previous level shall be sent to the STC user. Timer\_Long shall be restarted unless full traffic load has been resumed.
+
+NOTE 1 – The number of steps of congestion level and/or amount of increase/decrease is considered to be network implementation dependent.
+
+NOTE 2 – With the concept of one STC entity per "DPC OPC SI NI" quadruplet, the primitive MTP-STATUS.indication is always routed to the STC entity whose provisioned parameter "STC\_DPC" is identical to the parameter "Affected DPC" in the primitive.
+
+### 8.2.5 User Part availability
+
+On receipt of an MTP-STATUS.indication primitive with the cause parameter set to "user part unavailability-unknown", "user part unavailability-inaccessible remote user" or "user part unavailability-unequipped remote user", the STC user shall be informed via an OUT-OF-SERVICE.indication primitive, and an MSTC-ERROR.indication primitive with the cause parameter set to the value indicated in Table 8-2 shall be issued. If the STC receives an MTP-TRANSFER.indication primitive, it will issue an IN-SERVICE.indication primitive prior to performing the procedure specified in 8.2.2.2. The IN-SERVICE.indication primitive carries a Level parameter; the value of the parameter is network dependent. If the Level indicates congestion then the congestion indication procedure (specified in 8.2.4) is started.
+
+**Table 8-2/Q.2150.1 – Cause parameter mapping**
+
+| Cause parameter in
MTP-STATUS.indication | Cause parameter in
MSTC-ERROR.indication |
+|---------------------------------------------------|---------------------------------------------|
+| user part unavailability-unknown | user part unavailable (unknown) |
+| user part unavailability-inaccessible remote user | user part unavailable (inaccessible) |
+| user part unavailability-unequipped remote user | user part unequipped |
+
+NOTE – With the concept of one STC entity per "DPC OPC SI NI" quadruplet, the primitive MTP-STATUS.indication is always routed to the STC entity whose provisioned parameter "STC\_DPC" is identical to the parameter "Affected DPC" in the primitive.
+
+## 8.3 State Transition Table
+
+The State Transition Table for STC (Table 8-3) describes the primitives and primitives that lead to state transitions. The table only shows the major transition paths; the SDL diagrams in 8.4 show the full transitions.
+
+**Table 8-3/Q.2150.1 – State transition table (part 1 of 2)**
+
+| Event | State | | | |
+|-------------------------|----------------------------------------------------------------------------------------------------------------|------------------------------------------|-----------------------------------------------------------------------------------|----------------------------------------------------------|
+| | 1
STC Service
Unavailable | 2
STC Service
Available | 3
Congestion
I | 4
Congestion
II |
+| TRANSFER.request | → 1 | MTP-TRANSFER.
request
→ 2 | MTP-TRANSFER.
request
→ 3 | MTP-TRANSFER.
request
→ 4 |
+| MTP-RESUME.indication | Set CL (Note 2)
IN-SERVICE.
indication (CL)
If CL > CLnc then
set Timer_Long
→ 4
else
→ 2 | – | – | – |
+| MTP-PAUSE.indication | – | OUT-OF-
SERVICE.
indication
→ 1 | OUT-OF-
SERVICE.
indication
reset Timer_Long
reset Timer_Short
→ 1 | OUT-OF-SERVICE.
indication
reset Timer_Long
→ 1 |
+| MTP-TRANSFER.indication | TRANSFER.
indication
→ 1 | TRANSFER.
indication
→ 2 | TRANSFER.
indication
→ 3 | TRANSFER.
indication
→ 4 |
+
+**Table 8-3/Q.2150.1 – State transition table (part 1 of 2)**
+
+| Event | State | | | |
+|-----------------------------------|---------------------------------|-------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|
+| | 1
STC Service
Unavailable | 2
STC Service
Available | 3
Congestion
I | 4
Congestion
II |
+| MTP-STATUS.indication
(Note 3) | – | CL := 1
CONGESTION.
indication (CL)
set Timer_Long
set Timer_Short
→ 3 | 3 | set Timer_Long
if CL < CLmc then
CL := CL + CLst
CONGESTION.
indication (CL)
set Timer_Short
→ 3
else
→ 4 |
+| Expiry of Timer_Long | – | – | – | CL := CL – CLst
CONGESTION.
indication (CL)
if CL > CLnc then
set Timer_Long
→ 4
else
→ 2 |
+| Expiry of Timer_Short | – | – | → 4 | – |
+| MTP-STATUS.indication
(Note 4) | → 1 | OUT-OF-
SERVICE.
indication
MSTC-ERROR.
indication
→ 1 | OUT-OF-
SERVICE.
indication
reset Timer_Long
reset Timer_Short
MSTC-ERROR.
indication
→ 1 | OUT-OF-SERVICE.
indication
reset Timer_Long
MSTC-ERROR.
indication
→ 1 |
+
+**Table 8-3/Q.2150.1 – State transition table (part 2 of 2)**
+
+| Event | State | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|---------------------------------------------------------------------------------------------------------------------------------------------|--|
+| | start | | |
+| Power-up | | START-
INFO.indication
Set CL (Note 2)
IN-SERVICE.
indication (CL)
If CL > CLnc then
set Timer_Long
→ 4
else
→ 2 | |
+| NOTE 1 – In this state transition table, the values for CL are used as follows: "CFnc" indicates "no congestion" and "CFmc" indicates maximum congestion; the amount of step up or down is "CFst". These values are provisioned (see 7.4) and used to illustrate the algorithm and are in no way binding for implementations; the number of steps of congestion level and/or amount of increase/decrease are considered to be network implementation dependent.
NOTE 2 – The value of CL when an MTP-RESUME.indication is received or at start-up is a network option.
NOTE 3 – Congestion indication without level.
NOTE 4 – Peer MTP user unavailable.
NOTE 5 – Congestion indication with congestion level is a national option; no state transitions are shown in this table.
| | | |
+
+## 8.4 SDL diagrams
+
+The SDL diagrams are represented in Figures 8-2 to 8.4.
+
+
+
+System STC11 STC11S(1)
+
+The diagram illustrates the System STC11 (STC11S(1)). It features several lifelines and a central state box labeled STC11.
+
+- ToGSTuser**: A lifeline at the top left.
+- FromGSTuser**: A lifeline below ToGSTuser.
+- TRANSFER.request**: A message box on the FromGSTuser lifeline.
+- Indications (Top Group)**: A list of messages on the right side: IN-SERVICE.indication, OUT-OF-SERVICE.indication, CONGESTION.indication, TRANSFER.indication, and START-INFO.indication.
+- ToLM**: A lifeline on the left side, below FromGSTuser.
+- MSTC-ERROR.indication**: A message box on the ToLM lifeline.
+- STC11**: A large rectangular state box in the center.
+- MTP-TRANSFER.request**: A message box on the right side, below the top indications.
+- Indications (Bottom Group)**: A list of messages on the right side: MTP-TRANSFER.indication, MTP-RESUME.indication, MTP-PAUSE.indication, and MTP-STATUS.indication.
+- ToMTP3**: A lifeline at the bottom left.
+- FromMTP3**: A lifeline below ToMTP3.
+
+SDL diagram for System STC11 showing lifelines for ToGSTuser, FromGSTuser, ToLM, MSTC-ERROR.indication, MTP-TRANSFER.request, ToMTP3, and FromMTP3. It includes a central state box labeled STC11 and two groups of indications.
+
+Figure 8-2/Q.2150.1 – SDL system of the Signalling Transport Converter
+
+
+
+Block STC11 STC11B(1)
+
+```
+
+stateDiagram-v2
+ [*] --> ToGSTuser
+ ToGSTuser --> FromGSTuser
+ FromGSTuser --> STC11 : TRANSFER.request
+ STC11 --> ToLM
+ ToLM --> FromLM : MSTC-ERROR.indication
+ FromLM --> STC11 : MTP-TRANSFER.request
+ STC11 --> ToMTP3
+ ToMTP3 --> FromMTP3
+
+```
+
+The diagram illustrates the internal structure of the STC11 block. At the top, the 'ToGSTuser' interface is shown with a return path 'FromGSTuser'. A 'TRANSFER.request' message is sent from 'FromGSTuser' to the central 'STC11' component. The 'STC11' component sends a group of indications ('IN-SERVICE.indication', 'OUT-OF-SERVICE.indication', 'CONGESTION.indication', 'TRANSFER.indication', 'START-INFO.indication') back to 'ToGSTuser'. Below the central component, the 'ToLM' interface is shown with a return path 'FromLM'. An 'MSTC-ERROR.indication' is sent from 'ToLM' to 'FromLM', and an 'MTP-TRANSFER.request' is sent from 'FromLM' to 'STC11'. At the bottom, the 'ToMTP3' interface is shown with a return path 'FromMTP3'. The 'STC11' component sends a group of indications ('MTP-TRANSFER.indication', 'MTP-RESUME.indication', 'MTP-PAUSE.indication', 'MTP-STATUS.indication') to 'ToMTP3'.
+
+SDL block structure of the Signalling Transport Converter (STC11).
+
+**Figure 8-3/Q.2150.1 – SDL block structure of the Signalling Transport Converter**
+
+
+
+```
+
+stateDiagram-v2
+ [*] --> STC_Service_Unavailable
+ STC_Service_Unavailable --> STC_OPC_Greater_Than_STC_DPC {STC_OPC > STC_DPC}
+ STC_OPC_Greater_Than_STC_DPC -- false --> CIC_Control_Odd [CIC_Control := odd]
+ STC_OPC_Greater_Than_STC_DPC -- true --> CIC_Control_Even [CIC_Control := even]
+ CIC_Control_Odd --> START_INFO_Indication [START-INFO indication (Max_Length, CIC_Control)]
+ CIC_Control_Even --> START_INFO_Indication
+ START_INFO_Indication --> STC_Service_Unavailable
+ STC_Service_Unavailable --> MTP_RESUME_Indication [MTP-RESUME indication (Affected DCP)]
+ STC_Service_Unavailable --> TRANSFER_Request [TRANSFER request (SC, SUD, PRIO)]
+ STC_Service_Unavailable --> MTP_TRANSFER_Indication [MTP-TRANSFER indication (OPC, DPC, SLS, SIO, Msg)]
+ MTP_RESUME_Indication --> CL_Value [CL := value]
+ TRANSFER_Request --> STC_Service_Unavailable
+ MTP_TRANSFER_Indication --> SUD_Msg [SUD := Msg : extract PRIO from SIO]
+ SUD_Msg --> TRANSFER_Indication [TRANSFER indication (SUD, PRIO)]
+ TRANSFER_Indication --> STC_Service_Unavailable
+ CL_Value --> IN_SERVICE_Indication [IN-SERVICE indication (Level := CL)]
+ IN_SERVICE_Indication --> CL_Greater_Than_CLnc {CL > CLnc}
+ CL_Greater_Than_CLnc -- false --> STC_Service_Available
+ CL_Greater_Than_CLnc -- true --> set_Timer [set (now+vTimer_Long, Timer_Long)]
+ set_Timer --> Congestion_2 [Congestion 2]
+ set_Timer --> STC_Service_Available
+ note right of CL_Value: The value of CL when an MTP-RESUME indication is received is a network option. (Note 1)
+
+```
+
+```
+
+syntype
+ Natural14 = Natural
+ constants 0:16383 ;
+endsyntype ;
+
+fpar
+ STC_DPC Natural14,
+ STC_OPC Natural14,
+ STC_SIO Natural8,
+ vTimer_Long Duration,
+ vTimer_Short Duration,
+ Max_Length Enumerated
+ (272,4096),
+ CLnc Natural,
+ CLmc Natural,
+ CLst Natural ;
+
+syntype
+ Congestion_Level =
+ Natural
+ constants 0:10 ;
+endsyntype
+
+dcl
+ CL_Congestion_Level,
+ CIC_Control Enumerated
+ (even,odd) ;
+
+```
+
+SDL diagram for Process STC11. It shows state transitions between 'STC Service Unavailable' and 'STC Service Available'. Transitions are triggered by events like 'STC\_OPC > STC\_DPC', 'MTP-RESUME indication', 'TRANSFER request', and 'MTP-TRANSFER indication'. Actions include 'CIC\_Control := even/odd', 'START-INFO indication', 'CL := value', 'set (now+vTimer\_Long, Timer\_Long)', and 'SUD := Msg : extract PRIO from SIO'. A decision 'CL > CLnc' leads to 'Congestion 2' or 'STC Service Available'. A note indicates 'The value of CL when an MTP-RESUME indication is received is a network option. (Note 1)'.
+
+**NOTES**
+
+1. The number of steps of congestion level and/or amount of increase/decrease are considered to be network implementation dependent.
+2. The parameters of the TRANSFER request and TRANSFER indication primitives are abbreviated as SUD (STC User Data), SC (Sequence Control), and PRIO (Priority) for clarity. The use of the parameter Priority is a national option.
+3. With the concept of one STC entity per "DPC OPC SI NI" quadruplet, the primitives MTP-PAUSE indication, MTP-RESUME indication, and MTP-STATUS indication are always routed to the STC entity whose provisioned parameter "STC\_DPC" is identical to the parameter "Affected DPC" in the primitive.
+4. As a national option congestion with a congestion level can be conveyed by the MTP-STATUS indication primitive; these SDL diagrams do not show such national options.
+
+Figure 8-4/Q.2150.1 – SDL diagram for the Signalling Transport Converter (part 1 of 4)
+
+
+
+```
+
+stateDiagram-v2
+ [*] --> STC_Service_Available : STC Service Available
+ STC_Service_Available --> TRANSFER_request : TRANSFER.request (SC, SUD, PRIO)
+ TRANSFER_request --> map_SC_into_SLS : map SC into SLS ; Msg := SUD ; merge PRIO into SIO
+ map_SC_into_SLS --> MTP_TRANSFER_request : MTP-TRANSFER.request (OPC, DPC, SLS, SIO, Msg)
+ MTP_TRANSFER_request --> STC_Service_Available
+
+ STC_Service_Available --> MTP_TRANSFER_indication : MTP-TRANSFER.indication (OPC, DPC, SLS, SIO, Msg)
+ MTP_TRANSFER_indication --> SUD := Msg : SUD := Msg ; extract PRIO from SIO
+ SUD := Msg --> TRANSFER_indication : TRANSFER.indication (SUD, PRIO)
+ TRANSFER_indication --> STC_Service_Available
+
+ STC_Service_Available --> MTP_PAUSE_indication : MTP-PAUSE.indication (Affected DPC)
+ MTP_PAUSE_indication --> OUT_OF_SERVICE_indication : OUT-OF-SERVICE.indication
+ OUT_OF_SERVICE_indication --> STC_Service_Unavailable : STC Service Unavailable
+
+ STC_Service_Available --> MTP_STATUS_indication : MTP-STATUS.indication (Affected DPC, Cause)
+ MTP_STATUS_indication --> cause : cause
+ cause --> else : else
+ else --> STC_Service_Available
+
+ cause --> congestion_without_level : congestion without level
+ congestion_without_level --> CL := CLnc + CLst : CL := CLnc + CLst
+ CL := CLnc + CLst --> CONGESTION_indication : CONGESTION.indication (Level := CL)
+ CONGESTION_indication --> set_long_timer : set (now+vTimer_Long, Timer_Long)
+ set_long_timer --> set_short_timer : set (now+vTimer_Short, Timer_Short)
+ set_short_timer --> Congestion_1 : Congestion 1
+
+ cause --> User_part_unavailability : User part unavailability -- unknown -- unequipped -- inaccessible
+ User_part_unavailability --> OUT_OF_SERVICE_indication : OUT-OF-SERVICE.indication
+ OUT_OF_SERVICE_indication --> MSTC_ERROR_indication : MSTC-ERROR.indication (cause)
+ MSTC_ERROR_indication --> STC_Service_Unavailable : STC Service Unavailable
+
+```
+
+SDL diagram for the Signalling Transport Converter (part 2 of 4). The diagram shows state transitions for Process STC11 starting from 'STC Service Available'. Transitions include TRANSFER.request, MTP-TRANSFER.indication, MTP-PAUSE.indication, and MTP-STATUS.indication. The MTP-STATUS.indication path includes a 'cause' decision leading to 'else' (back to Available), 'congestion without level' (leading to congestion handling), or 'User part unavailability' (leading to OUT-OF-SERVICE).
+
+Figure 8-4/Q.2150.1 – SDL diagram for the Signalling Transport Converter (part 2 of 4)
+
+
+
+The diagram is an SDL state transition diagram for the Signalling Transport Converter (STC). It features three main states: **Congestion 1** (initial state), **Congestion 2**, and **STC Service Unavailable**.
+
+- From Congestion 1:**
+ - TRANSFER.request (SC, SUD, PRIO)** leads to **map SC into SLS ; Msg := SUD ; merge PRIO into SIO**, which leads to **MTP-TRANSFER.request (OPC, DPC, SLS, SIO, Msg)**, returning to **Congestion 1**.
+ - MTP-TRANSFER.indication (OPC, DPC, SLS, SIO, Msg)** leads to **SUD := Msg ; extract PRIO from SIO**, which leads to **TRANSFER.indication (SUD, PRIO)**, returning to **Congestion 1**.
+ - MTP-PAUSE.indication (Affected DPC)** leads to **OUT-OF-SERVICE.indication**, which leads to **reset (Timer\_Long)**, then **reset (Timer\_Short)**, and finally to **STC Service Unavailable**.
+ - Timer\_Short** leads to **Congestion 2**.
+ - MTP-STATUS.indication (Affected DPC, Cause)** leads to a **cause** decision:
+ - If the cause is identified, it returns to **Congestion 1**.
+ - If the cause is **else** (User part unavailability: unknown, unequipped, or inaccessible), it leads to **OUT-OF-SERVICE.indication**, then **MSTC-ERROR.indication (cause)**, then **reset (Timer\_Long)**, then **reset (Timer\_Short)**, and finally to **STC Service Unavailable**.
+- From Congestion 2:**
+ - No explicit transitions are shown from this state in this part of the diagram.
+
+SDL diagram for the Signalling Transport Converter (part 3 of 4). The diagram shows state transitions for Congestion 1, Congestion 2, and STC Service Unavailable states based on various input indications like TRANSFER.request, MTP-TRANSFER.indication, MTP-PAUSE.indication, Timer\_Short, and MTP-STATUS.indication.
+
+Figure 8-4/Q.2150.1 – SDL diagram for the Signalling Transport Converter (part 3 of 4)
+
+
+
+```
+
+stateDiagram-v2
+ [*] --> Congestion_2
+ Congestion_2 --> TRANSFER_request [TRANSFER.request (SC, SUD, PRIO)]
+ Congestion_2 --> MTP_TRANSFER_indication [MTP-TRANSFER.indication (OPC, DPC, SLS, SIO, Msg)]
+ Congestion_2 --> Timer_Long
+ Congestion_2 --> MTP_STATUS_indication [MTP-STATUS.indication (Affected DPC, Cause)]
+ Congestion_2 --> MTP_PAUSE_indication [MTP-PAUSE.indication (Affected DPC)]
+
+ TRANSFER_request --> map_SC_into_SLS [map SC into SLS ; Msg := SUD ; merge PRIO into SIO]
+ map_SC_into_SLS --> MTP_TRANSFER_request [MTP-TRANSFER.request (OPC, DPC, SLS, SIO, Msg)]
+ MTP_TRANSFER_request --> Congestion_2
+
+ MTP_TRANSFER_indication --> SUD_extract_PRIO [SUD := Msg ; extract PRIO from SIO]
+ SUD_extract_PRIO --> TRANSFER_indication [TRANSFER.indication (SUD, PRIO)]
+ TRANSFER_indication --> Congestion_2
+
+ Timer_Long --> CL_decrement [CL := CL - CLst]
+ CL_decrement --> CONGESTION_indication_Level_CL [CONGESTION.indication (Level := CL)]
+ CONGESTION_indication_Level_CL --> CL_greater_CLnc {CL > CLnc}
+
+ CL_greater_CLnc -- false --> Congestion_2
+ CL_greater_CLnc -- true --> set_timer_long [set (now+VTimer_Long, Timer_Long)]
+ set_timer_long --> Congestion_2
+
+ set_timer_long --> STC_Service_Available [STC Service Available]
+
+ MTP_STATUS_indication --> cause {cause}
+
+ cause -- else --> Congestion_2
+ cause -- congestion without level --> set_timer_long
+ cause -- User part unavailability --> OUT_OF_SERVICE_indication [OUT-OF-SERVICE.indication]
+ User part unavailability --> MSTC_ERROR_indication [MSTC-ERROR.indication (cause)]
+ MSTC_ERROR_indication --> reset_timer_long [reset (Timer_Long)]
+ reset_timer_long --> STC_Service_Unavailable [STC Service Unavailable]
+
+ set_timer_long --> CL_less_CLmc {CL < CLmc}
+
+ CL_less_CLmc -- false --> Congestion_2
+ CL_less_CLmc -- true --> CL_increment [CL := CL + CLst]
+ CL_increment --> CONGESTION_indication_Level_CL
+ CONGESTION_indication_Level_CL --> set_timer_short [set (now+VTimer_Short, Timer_Short)]
+ set_timer_short --> Congestion_1
+
+ MTP_PAUSE_indication --> OUT_OF_SERVICE_indication
+ OUT_OF_SERVICE_indication --> reset_timer_long
+ reset_timer_long --> STC_Service_Unavailable
+
+```
+
+SDL diagram for the Signalling Transport Converter (part 4 of 4). The diagram shows state transitions and actions for various inputs like TRANSFER.request, MTP-TRANSFER.indication, Timer\_Long, MTP-STATUS.indication, and MTP-PAUSE.indication. It includes decision points for congestion levels (CL, CLnc, CLmc) and actions for service availability and unavailability.
+
+Figure 8-4/Q.2150.1 – SDL diagram for the Signalling Transport Converter (part 4 of 4)
+
+# APPENDIX I
+
+## **Protocol Implementation Conformance Statement (PICS) Proforma**
+
+There exists no actions of the Signalling Transport Converter that are visible from outside a system, therefore a Protocol Implementation Conformance Statement is not possible. If the Generic Signalling Transport Service is based on MTP3 or MTP3b, all of clauses 7 and 8 of this Recommendation apply.
+
+# SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure and Internet protocol aspects |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.2632.1-200310-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2632.1-200310-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..05ef0167a424d52157f977cc520d0045abd8b246
--- /dev/null
+++ b/marked/Q/T-REC-Q.2632.1-200310-I_PDF-E/raw.md
@@ -0,0 +1,1088 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt striking through it, symbolizing global communication.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**Q.2632.1**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(10/2003)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Broadband ISDN – Common aspects of B-ISDN
+application protocols for access signalling and network
+signalling and interworking
+
+---
+
+**Interworking between AAL type 2 signalling
+protocol Capability Set 2 and IP connection
+control signalling protocol Capability Set 1**
+
+ITU-T Recommendation Q.2632.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 |
+| General aspects | Q.2000-Q.2099 |
+| Signalling ATM adaptation layer (SAAL) | Q.2100-Q.2199 |
+| Signalling network protocols | Q.2200-Q.2299 |
+| Common aspects of B-ISDN application protocols for access signalling and network signalling and interworking | Q.2600-Q.2699 |
+| B-ISDN application protocols for the network signalling | Q.2700-Q.2899 |
+| B-ISDN application protocols for access signalling | Q.2900-Q.2999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## **ITU-T Recommendation Q.2632.1**
+
+## **Interworking between AAL type 2 signalling protocol Capability Set 2 and IP connection control signalling protocol Capability Set 1**
+
+## **Summary**
+
+This Recommendation describes the interworking between the AAL type 2 signalling protocol and the IP connection control signalling protocol. This Recommendation describes the mapping tables and diagrams which support interworking between the two protocols for call set-up, modification and clear down.
+
+## **Source**
+
+ITU-T Recommendation Q.2632.1 was approved by ITU-T Study Group 11 (2001-2004) under the ITU-T Recommendation A.8 procedure on 14 October 2003.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2004
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## CONTENTS
+
+| | Page |
+|-----------------------------------------------------------------------------------------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References..... | 2 |
+| 2.1 Normative References ..... | 2 |
+| 2.2 Informative references..... | 2 |
+| 3 Abbreviations..... | 2 |
+| 4 General statements on interworking ..... | 4 |
+| 5 Successful connection set-up..... | 5 |
+| 5.1 Mapping of the establish request message ..... | 5 |
+| 5.2 Mapping of the establish confirm message ..... | 7 |
+| 6 Unsuccessful connection set-up..... | 8 |
+| 6.1 Mapping of the RLC message ..... | 8 |
+| 7 Connection release..... | 9 |
+| 7.1 Mapping of the REL message ..... | 9 |
+| 7.2 Mapping of the RLC message ..... | 10 |
+| 8 Successful modification..... | 10 |
+| 8.1 Mapping of the MOD message..... | 10 |
+| 8.2 Mapping of the MOA message..... | 11 |
+| 9 Unsuccessful modification ..... | 12 |
+| 9.1 Mapping of the MOR message..... | 12 |
+| 10 Reset ..... | 13 |
+| 10.1 Reset initiated in AAL type 2/IP network ..... | 13 |
+| 10.2 Reset initiated by the IWU ..... | 15 |
+| 11 Messages requiring no interworking ..... | 16 |
+| 11.1 AAL type 2 messages..... | 16 |
+| 11.2 IPC messages..... | 17 |
+| Appendix I – Interworking of AAL type 2 link characteristics and SSISU parameters
with IPC IP transfer capabilities..... | 17 |
+| I.0 Guidelines and definitions ..... | 17 |
+| I.1 Interworking for AAL type 2 to IP..... | 19 |
+| I.2 Interworking for IP to AAL type 2..... | 21 |
+
+
+
+# **Interworking between AAL type 2 signalling protocol Capability Set 2 and IP connection control signalling protocol Capability Set 1**
+
+# **1 Scope**
+
+This Recommendation defines the interworking relationship between the AAL type 2 signalling protocol Capability Set 2 and the IP connection control signalling protocol. For the purpose of this interworking, AAL type 2 signalling is defined in ITU-T Rec. Q.2630.2 [1] and subject to restrictions stated in TRQ.2800 [3]. For the purpose of this interworking, IP Connection Control signalling is defined in ITU-T Rec. Q.2631.1 [2].
+
+The interworking between the above two signalling protocols typically may occur in 3GPP UTRANs with AAL type 2 and IP network portions connected via an Interworking Unit.
+
+The objective of this ITU-T Recommendation is to specify the interworking between the AAL type 2 protocol and the IP Connection Control signalling protocol.
+
+Interworking is shown as message arrow diagrams. The diagrams included represent a sample of typical situations. Mapping tables are provided to define the relationship between AAL type 2 protocol messages and parameters, on the one hand, and IP Connection Control signalling protocol messages and parameters on the other hand.
+
+Tables are provided for each AAL type 2 message that maps onto an IP Connection Control message. These tables also specify the mapping of parameters, which are carried by the concerned messages.
+
+Parameters that are of local significance only, i.e. are not mapped onto parameters in the other signalling system, are not shown.
+
+The arrow diagrams used in this Recommendation show the message movement for interworking the bearer control protocols of AAL type 2 signalling and IP Connection Control signalling. The working inside of the exchanges will not be shown, but rather the external stimulus to the exchange only (see Figures 1 and 2).
+
+
+
+The diagram illustrates the interworking process between an AAL type 2 node and an IPC service endpoint via an Interworking Unit (IWU). It consists of three rectangular boxes arranged horizontally: 'AAL type 2 node' on the left, 'IWU' in the center, and 'IPC service endpoint' on the right. Vertical lines extend downwards from each box. A horizontal arrow points from the vertical line of the AAL type 2 node to the vertical line of the IWU, labeled 'incoming AAL type 2 signalling message'. Another horizontal arrow points from the vertical line of the IWU to the vertical line of the IPC service endpoint, labeled 'outgoing IPC signalling message'. In the bottom right corner of the diagram area, the text 'Q.2632.1\_F01' is present.
+
+Diagram showing the flow of signalling messages from an AAL type 2 node, through an IWU, to an IPC service endpoint. The first arrow is labeled 'incoming AAL type 2 signalling message' and the second is 'outgoing IPC signalling message'. A small label 'Q.2632.1\_F01' is at the bottom right.
+
+**Figure 1/Q.2632.1 – AAL type 2 to IPC signalling interworking**
+
+
+
+```
+
+sequenceDiagram
+ participant AAL type 2 node
+ participant IWU
+ participant IPC service endpoint
+ Note right of IPC service endpoint: Q.2632.1_F02
+ IPC service endpoint->>IWU: incoming IPC signalling message
+ IWU->>AAL type 2 node: outgoing AAL type 2 signalling message
+
+```
+
+Diagram illustrating IPC to AAL type 2 signalling interworking. It shows three entities: AAL type 2 node, IWU, and IPC service endpoint. Arrows indicate the flow of signalling messages: 'outgoing AAL type 2 signalling message' from IWU to AAL type 2 node, and 'incoming IPC signalling message' from IPC service endpoint to IWU. The diagram is labeled Q.2632.1\_F02.
+
+**Figure 2/Q.2632.1 – IPC to AAL type 2 signalling interworking**
+
+# 2 References
+
+## 2.1 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; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [1] ITU-T Recommendation Q.2630.2 (2001), *AAL type 2 signalling protocol – Capability Set 2*.
+- [2] ITU-T Recommendation Q.2631.1 (2003), *IP connection control signalling protocol – Capability Set 1*.
+
+## 2.2 Informative references
+
+- [3] ITU-T Q-series Recommendations – Supplement 44 (2003), *Technical Report TRQ.2800: Transport control signalling requirements – Signalling requirements for AAL type 2 to IP interworking Capability Set 1*.
+
+# 3 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|------|------------------------------------------|
+| 3GPP | 3rd Generation Partnership Project |
+| A2EA | AAL type 2 Service Endpoint Address |
+| A2IP | AAL type 2 – IP |
+| AAL | ATM Adaptation Layer |
+| AAL2 | AAL type 2 |
+| ATM | Asynchronous Transfer Mode |
+| BLC | Block Confirm Message |
+| BLO | Block Request Message |
+| CAU | Cause Parameter |
+| CEID | AAL type 2 Connection Element Identifier |
+
+| | |
+|---------|-----------------------------------------------------------------------|
+| CFN | ConFusioN message |
+| CPS | (AAL type 2) Common Part Sublayer |
+| DEAE | Destination Endpoint E.164 Address |
+| DEAX | Destination Endpoint X.213 Address |
+| ECF | Establish Confirm Message |
+| ERQ | Establish Request Message |
+| ESEA | Destination E.164 Service Endpoint Address parameter |
+| HBx | Header bit rate associated with x |
+| IP | Internet Protocol |
+| IPC | IP Connection Control |
+| IPHL | Total length of the header of an IP packet |
+| IPQOS | IP Quality of Service parameter |
+| IPTT | IP Transport Type parameter |
+| IWU | InterWorking Unit |
+| LC | (AAL type 2) Link Characteristics parameter |
+| MAX | Maximum function |
+| MIN | Minimum function |
+| MOA | Modification Acknowledge message |
+| MOD | Modification Request message |
+| MOR | Modification Reject message |
+| MSLC | Modify Support for Link Characteristics parameter |
+| MSSSI | Modify Support for SSCS Information parameter |
+| MSTC | Modify Support for IP Transfer Capability parameter |
+| NSEA | Destination NSAP Service Endpoint Address parameter |
+| PLC | Preferred Link Characteristics parameter |
+| PSSCS | Preferred SSCS Information parameter |
+| PSSIAE | Preferred Service Specific Information (Audio Extended) parameter |
+| PSSIME | Preferred Service Specific Information (Multirate Extended) parameter |
+| PT | Path Type parameter |
+| PTC | Preferred IP Transfer Capability |
+| PTC-DBW | Dedicated Bandwidth Preferred IP Transfer Capability |
+| PTC-SBW | Statistical Bandwidth Preferred IP Transfer Capability |
+| REL | Release Request Message |
+| RES | Reset Request Message |
+| RLC | Release Confirm Message |
+| RSC | Reset Confirm Message |
+| SAR | Segmentation and Reassembly (Sublayer) |
+
+| | |
+|--------|-------------------------------------------------------------------|
+| SDU | Service Data Unit |
+| SSCS | Service Specific Convergence Sublayer |
+| SSIA | Service Specific Information (Audio) parameter |
+| SSIAE | Service Specific Information (Audio Extended) parameter |
+| SSIM | Service Specific Information (Multirate) parameter |
+| SSIME | Service Specific Information (Multirate Extended) parameter |
+| SSISA | Service Specific Information (SAR-assured) parameter |
+| SSISU | Service Specific Information (SAR-unassured) parameter |
+| SSSAR | Segmentation and Reassembly Service Specific Convergence Sublayer |
+| SUCI | Served User Correlation ID parameter |
+| SUGR | Served User Generated Reference parameter |
+| SUT | Served User Transport parameter |
+| TC | (IP) Transfer Capability |
+| TC-DBW | Dedicated Bandwidth IP Transfer Capability |
+| TC-SBW | Statistical Bandwidth IP Transfer Capability |
+| TCI | Test Connection Indication parameter |
+| UBC | Unblock Confirm Message |
+| UBL | Unblock Request Message |
+| UTRAN | UMTS Terrestrial Radio Access Network |
+
+# 4 General statements on interworking
+
+- No ATM or AAL type 2 specific parameters defined for AAL type 2 signalling will be carried in the IP connection control signalling.
+- No IP specific parameters defined for IP connection control signalling will be carried in the AAL type 2 signalling.
+- All AAL type 2 and all IP connection control messages carry message compatibility information.
+- All AAL type 2 and all IP connection control parameters carry parameter compatibility information.
+- Through-connection in the IWU will occur immediately after either the AAL type 2 or the IP connection control signalling sends the Establish Request Message (ERQ).
+- According to TRQ.2800 [3] interworking is specified for AAL type 2 signalling with SSCS support restricted to SSSAR unassured. Therefore, reception of any of the parameters listed in Table 1 at the IWU shall lead to the behaviour as specified there. Furthermore, none of these parameters shall be generated at the IWU in AAL type 2 signalling messages.
+
+**Table 1/Q.2632.1 – List of non-supported AAL type 2 parameters**
+
+| AAL type 2 parameter | Action on reception | |
+|-------------------------------|----------------------------------------------|-------------------------------|
+| | AAL type 2 side | IP side |
+| MSSSI in ERQ and ECF messages | Discard parameter, do not send notification | As specified in 5.1.1 and 5.2 |
+| PSSIAE in ERQ message | Discard parameter, do not send notification | As specified in 5.1.1 |
+| PSSIME in ERQ message | Discard parameter, do not send notification | As specified in 5.1.1 |
+| SSIAE in ERQ message | Release connection, do not send notification | – |
+| SSIA in ERQ message | Release connection, do not send notification | – |
+| SSIME in ERQ message | Release connection, do not send notification | – |
+| SSIM in ERQ message | Release connection, do not send notification | – |
+| SSISA in ERQ message | Release connection, do not send notification | – |
+| SUCI in MOD and MOA messages | Discard parameter, do not send notification | As specified in 8.1.1 and 8.2 |
+
+NOTE – These parameters are not shown in the mapping tables.
+
+# **5 Successful connection set-up**
+
+## **5.1 Mapping of the establish request message**
+
+### **5.1.1 Connection establishment initiated from the AAL type 2 network**
+
+
+
+```
+
+sequenceDiagram
+ participant AAL type 2 node
+ participant IWU
+ participant IPC service endpoint
+ Note right of IPC service endpoint: Q.2632.1_F03
+ AAL type 2 node->>IWU: ERQ
+ IWU->>IPC service endpoint: ERQ
+
+```
+
+Sequence diagram showing ERQ message flow from AAL type 2 node to IWU to IPC service endpoint. The diagram shows three vertical lifelines: AAL type 2 node, IWU, and IPC service endpoint. Arrows labeled 'ERQ' show the message flow from left to right: AAL type 2 node to IWU, and IWU to IPC service endpoint.
+
+**Figure 3/Q.2632.1 – ERQ from AAL type 2 network**
+
+**Table 2/Q.2632.1 – Mapping of ERQ parameters (ERQ initiated from AAL2)**
+
+| Incoming AAL type 2 ERQ | Outgoing IPC ERQ |
+|-------------------------|----------------------|
+| ESEA (Note 1) | DEAE (Note 2) |
+| NSEA (Note 1) | DEAX (Note 2) |
+| LC | TC (Note 3) |
+| PLC | PTC (Note 3) |
+| MSLC | MSTC |
+| SSISU | (Note 3) |
+| SUGR | SUGR |
+| SUT | SUT |
+| TCI | Not carried |
+| PT | Not carried (Note 4) |
+| | IPQOS (Note 4) |
+| | IPTT (Note 5) |
+
+NOTE 1 – Only one of these parameters is present.
+NOTE 2 – Only one of these parameters is present. Values may be taken unchanged or with format conversion (E.164 to NSAP, NSAP to E.164) or derived by address translation with and without format change from the received ESEA or NSEA parameter.
+NOTE 3 – TC and PTC are of the form of a Dedicated Bandwidth or Statistical Bandwidth IP Transfer Capability. Appendix I gives a guideline for the derivation of these parameters.
+NOTE 4 – The PT value may be taken into account to derive the value of this parameter.
+NOTE 5 – The value of this parameter may be determined from administrative settings and/or routing decisions.
+
+### 5.1.2 Connection establishment initiated from the IP network
+
+
+
+```
+
+sequenceDiagram
+ participant AAL type 2 node
+ participant IWU
+ participant IPC service endpoint
+ Note right of IPC service endpoint: Q.2632.1_F04
+ IPC service endpoint->>IWU: ERQ
+ IWU->>AAL type 2 node: ERQ
+
+```
+
+The diagram illustrates the flow of ERQ messages for connection establishment initiated from the IP network. It features three vertical lifelines: 'AAL type 2 node' on the left, 'IWU' in the center, and 'IPC service endpoint' on the right. A horizontal arrow labeled 'ERQ' points from the 'IPC service endpoint' to the 'IWU'. Another horizontal arrow labeled 'ERQ' points from the 'IWU' to the 'AAL type 2 node'. A small note 'Q.2632.1\_F04' is located in the bottom right corner of the diagram area.
+
+Sequence diagram showing ERQ messages from IPC service endpoint to IWU and then to AAL type 2 node.
+
+**Figure 4/Q.2632.1 – ERQ from IP network**
+
+**Table 3/Q.2632.1 – Mapping of ERQ parameters (ERQ initiated from IP)**
+
+| Outgoing AAL type 2 ERQ | Incoming IPC ERQ |
+|-------------------------|------------------|
+| ESEA (Note 2) | DEAE (Note 1) |
+| NSEA (Note 2) | DEAX (Note 1) |
+| LC (Note 3) | TC (Note 4) |
+| PLC (Note 3) | PTC (Note 4) |
+| MSLC | MSTC |
+| SSISU (Note 3) | Not carried |
+| SUGR | SUGR |
+| SUT | SUT |
+| TCI (Note 6) | |
+| PT (Note 5) | |
+| Not carried | IPQOS |
+| Not carried | IPTT |
+
+NOTE 1 – Only one of these parameters is present.
+NOTE 2 – Only one of these parameters is present. Values may be taken unchanged or with format conversion (E.164 to NSAP, NSAP to E.164) or derived by address translation with and without format change from the received DEAE or DEAX parameter.
+NOTE 3 – Appendix I gives a guideline for the derivation of these parameters.
+NOTE 4 – TC and PTC are of the form of a Dedicated Bandwidth or Statistical Bandwidth IP Transfer Capability.
+NOTE 5 – The IPQOS value may be taken into account to derive the value of this parameter.
+NOTE 6 – TCI shall not be generated by the IWU. Only listed for completeness.
+
+## **5.2 Mapping of the establish confirm message**
+
+
+
+```
+
+sequenceDiagram
+ participant AAL type 2 node
+ participant IWU
+ participant IPC service endpoint
+ Note right of IPC service endpoint: Q.2632.1_F05
+ AAL type 2 node->>IWU: ECF
+ IWU->>IPC service endpoint: ECF
+
+```
+
+Sequence diagram showing the flow of ECF messages from AAL type 2 node to IWU to IPC service endpoint.
+
+**Figure 5/Q.2632.1 – ECF from AAL type 2 network**
+
+
+
+Q.2632.1\_F06
+
+Sequence diagram showing ECF messages from IPC service endpoint and IWU to AAL type 2 node. The diagram includes three lifelines: AAL type 2 node, IWU, and IPC service endpoint. Arrows labeled 'ECF' point from the IPC service endpoint and IWU to the AAL type 2 node. The identifier 'Q.2632.1\_F06' is in the bottom right.
+
+Figure 6/Q.2632.1 – ECF from IP network
+
+Table 4/Q.2632.1 – Mapping of ECF parameters
+
+| Incoming/Outgoing AAL type 2 ECF | Outgoing/Incoming IPC ECF |
+|----------------------------------|---------------------------|
+| MSLC | MSTC |
+
+# **6 Unsuccessful connection set-up**
+
+## **6.1 Mapping of the RLC message**
+
+
+
+Q.2632.1\_F07
+
+Sequence diagram showing RLC messages from AAL type 2 node and IWU to IPC service endpoint. The diagram includes three lifelines: AAL type 2 node, IWU, and IPC service endpoint. Arrows labeled 'RLC' point from the AAL type 2 node and IWU to the IPC service endpoint. The identifier 'Q.2632.1\_F07' is in the bottom right.
+
+Figure 7/Q.2632.1 – RLC from AAL type 2 network
+
+
+
+Q.2632.1\_F08
+
+Sequence diagram showing RLC messages from IPC service endpoint and IWU to AAL type 2 node. The diagram includes three lifelines: AAL type 2 node, IWU, and IPC service endpoint. Arrows labeled 'RLC' point from the IPC service endpoint and IWU to the AAL type 2 node. The identifier 'Q.2632.1\_F08' is in the bottom right.
+
+Figure 8/Q.2632.1 – RLC from IP network
+
+**Table 5/Q.2632.1 – Mapping of RLC parameters**
+
+| Incoming/Outgoing AAL type 2 RLC | Outgoing/Incoming IPC RLC |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| CAU (Notes 1 and 2) | CAU (Notes 1 and 2) |
+| NOTE 1 – Cause values received at the IWU that are unique to the network portion where they are generated, i.e., unknown in the other network portion, shall be mapped to "Normal, unspecified".
NOTE 2 – If Cause parameters are received containing compatibility information, the cause value shall be mapped to "Normal unspecified" and the diagnostics shall be discarded.
| |
+
+# **7 Connection release**
+
+In AAL type 2 signalling the Connection Establishment procedures show an end-to-end behaviour, whereas the Connection Release procedures are of a link-by-link characteristic. The A2IP Interworking Unit simulates these principles; i.e., the A2IP IWU behaves from the point of view of the AAL type 2 network portion like an AAL type 2 switch.
+
+Guided by this principle, a Connection Release procedure will be handled by the A2IP IWU in the following manner:
+
+
+
+```
+
+sequenceDiagram
+ participant AAL2/IP
+ participant IWU
+ participant IP/AAL2
+ Note right of AAL2/IP: (1) REL
+ AAL2/IP->>IWU: (1) REL
+ Note right of IWU: (2) REL
+ IWU->>IP/AAL2: (2) REL
+ Note right of AAL2/IP: (3) RLC
+ AAL2/IP->>IWU: (3) RLC
+ Note right of IP/AAL2: (4) RLC
+ IP/AAL2->>IWU: (4) RLC
+
+```
+
+Q.2632.1\_F09
+
+Sequence diagram showing general release handling between AAL2/IP, IWU, and IP/AAL2 entities. Arrows 1 and 3 are between AAL2/IP and IWU. Arrows 2 and 4 are between IWU and IP/AAL2.
+
+**Figure 9/Q.2632.1 – General release handling**
+
+The REL message (1) causes the REL message (2) and the RLC message (3) to be sent. There is no time or logical correlation between (2) and (3) or between (3) and (4).
+
+## **7.1 Mapping of the REL message**
+
+
+
+```
+
+sequenceDiagram
+ participant AAL type 2 node
+ participant IWU
+ participant IPC service endpoint
+ Note right of AAL type 2 node: REL
+ AAL type 2 node->>IWU: REL
+ Note right of IWU: REL
+ IWU->>IPC service endpoint: REL
+
+```
+
+Q.2632.1\_F10
+
+Sequence diagram showing the mapping of a REL message from an AAL type 2 node through an IWU to an IPC service endpoint.
+
+**Figure 10/Q.2632.1 – REL from AAL type 2 network**
+
+
+
+Sequence diagram showing REL messages from IPC service endpoint to IWU and then to AAL type 2 node. The diagram shows three vertical lifelines: AAL type 2 node, IWU, and IPC service endpoint. Arrows labeled 'REL' point from the IPC service endpoint to the IWU, and from the IWU to the AAL type 2 node. The text 'Q.2632.1\_F11' is in the bottom right corner.
+
+Figure 11/Q.2632.1 – REL from IP network
+
+Table 6/Q.2632.1 – Mapping of REL parameters
+
+| Incoming/Outgoing AAL type 2 REL | Outgoing/Incoming IPC REL |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| CAU (Notes 1 and 2) | CAU (Notes 1 and 2) |
+| NOTE 1 – Cause values received at the IWU that are unique to the network portion where they are generated, i.e., unknown in the other network portion, shall be mapped to "Normal, unspecified".
NOTE 2 – If Cause parameters are received containing compatibility information, the cause value shall be mapped to "Normal unspecified" and the diagnostics shall be discarded. | |
+
+## 7.2 Mapping of the RLC message
+
+There is no interworking of RLC messages at connection release.
+
+A RLC message that is received in response to a REL message which has been initiated in the IWU due to a reset procedure in the other network portion (see clause 10), shall not be interworked.
+
+NOTE – Interworking of RLC messages takes place if and only if the RLC message is received as negative acknowledgement to an ERQ message in case of unsuccessful connection set-up (see 6.1)
+
+# 8 Successful modification
+
+## 8.1 Mapping of the MOD message
+
+### 8.1.1 Modification initiated from the AAL type 2 network
+
+
+
+Sequence diagram showing MOD messages from AAL type 2 node to IWU and then to IPC service endpoint. The diagram shows three vertical lifelines: AAL type 2 node, IWU, and IPC service endpoint. Arrows labeled 'MOD' point from the AAL type 2 node to the IWU, and from the IWU to the IPC service endpoint. The text 'Q.2632.1\_F12' is in the bottom right corner.
+
+Figure 12/Q.2632.1 – MOD from AAL type 2 network
+
+**Table 7/Q.2632.1 – Mapping of MOD parameters (MOD initiated from AAL2)**
+
+| Incoming AAL type 2 MOD | Outgoing IPC MOD |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|
+| LC | TC (Note) |
+| NOTE – TC is of the form of a Dedicated Bandwidth or Statistical Bandwidth IP Transfer Capability. Appendix I gives a guideline for the derivation of these parameters. | |
+
+### **8.1.2 Modification initiated from the IP network**
+
+
+
+The diagram illustrates the flow of a MOD message when initiated from the IP network. It features three vertical lifelines: 'AAL type 2 node', 'IWU', and 'IPC service endpoint'. Arrows indicate the message flow: a 'MOD' message is sent from the 'IPC service endpoint' to the 'IWU', and another 'MOD' message is sent from the 'IWU' to the 'AAL type 2 node'. A label 'Q.2632.1\_F13' is located at the bottom right of the diagram.
+
+Sequence diagram showing MOD message flow from IPC service endpoint to AAL type 2 node via IWU.
+
+**Figure 13/Q.2632.1 – MOD from IP network**
+
+**Table 8/Q.2632.1 – Mapping of MOD parameters (MOD initiated from IP)**
+
+| Outgoing AAL type 2 MOD | Incoming IPC MOD |
+|------------------------------------------------------------------------------------------------------|------------------|
+| LC (Note 1) | TC (Note 2) |
+| NOTE 1 – Appendix I gives guidelines for the derivation of this parameter. | |
+| NOTE 2 – TC is of the form of a Dedicated Bandwidth or Statistical Bandwidth IP Transfer Capability. | |
+
+## **8.2 Mapping of the MOA message**
+
+
+
+The diagram illustrates the flow of an MOA message when initiated from the AAL type 2 network. It features three vertical lifelines: 'AAL type 2 node', 'IWU', and 'IPC service endpoint'. Arrows indicate the message flow: an 'MOA' message is sent from the 'AAL type 2 node' to the 'IWU', and another 'MOA' message is sent from the 'IWU' to the 'IPC service endpoint'. A label 'Q.2632.1\_F14' is located at the bottom right of the diagram.
+
+Sequence diagram showing MOA message flow from AAL type 2 node to IPC service endpoint via IWU.
+
+**Figure 14/Q.2632.1 – MOA from AAL type 2 network**
+
+
+
+A sequence diagram with three lifelines: AAL type 2 node, IWU, and IPC service endpoint. Two arrows labeled 'MOA' are shown. The first arrow originates from the IPC service endpoint and points to the IWU. The second arrow originates from the IWU and points to the AAL type 2 node. Vertical lines extend downwards from each box. A label 'Q.2632.1\_F15' is located at the bottom right.
+
+Sequence diagram showing MOA messages from IPC service endpoint to IWU and then to AAL type 2 node. The diagram includes three lifelines: AAL type 2 node, IWU, and IPC service endpoint. Arrows labeled 'MOA' point from right to left.
+
+Figure 15/Q.2632.1 – MOA from IP network
+
+Table 9/Q.2632.1 – Mapping of MOA parameters
+
+| Incoming/Outgoing AAL type 2 MOA | Outgoing/Incoming IPC MOA |
+|-----------------------------------------------------------------|---------------------------|
+| (Note) | (Note) |
+| NOTE – MOA messages carry no parameters requiring interworking. | |
+
+# **9 Unsuccessful modification**
+
+## **9.1 Mapping of the MOR message**
+
+
+
+A sequence diagram with three lifelines: AAL type 2 node, IWU, and IPC service endpoint. Two arrows labeled 'MOR' are shown. The first arrow originates from the AAL type 2 node and points to the IWU. The second arrow originates from the IWU and points to the IPC service endpoint. Vertical lines extend downwards from each box. A label 'Q.2632.1\_F16' is located at the bottom right.
+
+Sequence diagram showing MOR messages from AAL type 2 node to IWU and then to IPC service endpoint. The diagram includes three lifelines: AAL type 2 node, IWU, and IPC service endpoint. Arrows labeled 'MOR' point from left to right.
+
+Figure 16/Q.2632.1 – MOR from AAL type 2 network
+
+
+
+A sequence diagram with three lifelines: AAL type 2 node, IWU, and IPC service endpoint. Two arrows labeled 'MOR' are shown. The first arrow originates from the IPC service endpoint and points to the IWU. The second arrow originates from the IWU and points to the AAL type 2 node. Vertical lines extend downwards from each box. A label 'Q.2632.1\_F17' is located at the bottom right.
+
+Sequence diagram showing MOR messages from IPC service endpoint to IWU and then to AAL type 2 node. The diagram includes three lifelines: AAL type 2 node, IWU, and IPC service endpoint. Arrows labeled 'MOR' point from right to left.
+
+Figure 17/Q.2632.1 – MOR from IP network
+
+**Table 10/Q.2632.1 – Mapping of MOR parameters**
+
+| Incoming/Outgoing AAL type 2 MOR | Outgoing/Incoming IPC MOR |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| CAU (Notes 1 and 2) | CAU (Notes 1 and 2) |
+| NOTE 1 – Cause values received at the IWU that are unique to the network portion where they are generated, i.e., unknown in the other network portion, shall be mapped to "Normal, unspecified".
NOTE 2 – If Cause parameters are received containing compatibility information, the cause value shall be mapped to "Normal unspecified" and the diagnostics shall be discarded.
| |
+
+# **10 Reset**
+
+## **10.1 Reset initiated in AAL type 2/IP network**
+
+In AAL type 2 signalling, the reset procedures are confined to two adjacent nodes.
+
+Guided by this principle, a reset procedure will be handled by the A2IP IWU in the following manner:
+
+
+
+Sequence diagram showing reset handling between AAL type 2 node, IWU, and IPC service endpoint. The diagram shows four numbered messages: 1. RES from AAL type 2 node to IWU; 2. REL from IWU to IPC service endpoint; 3. RSC from IWU to AAL type 2 node; 4. RLC from IPC service endpoint to IWU. A note at the bottom left indicates that there may be several REL sequences initiated by the A2IP IWU depending on the scope of the RES and the number of connections affected. The diagram is labeled Q.2632.1\_F18.
+
+**Figure 18/Q.2632.1 – General reset handling**
+
+Reception of the RES message (1) causes the REL message (2) and the RSC message (3) to be sent. There is no time or logical correlation between (2) and (3) or between (3) and (4).
+
+The handling is analogous in cases where the RES is received from the IP network portion or generated by the IWU.
+
+### 10.1.1 Reset initiated in AAL type 2 network
+
+
+
+```
+
+sequenceDiagram
+ participant AAL type 2 node
+ participant IWU
+ participant IPC service endpoint
+ AAL type 2 node->>IWU: RES
+ IWU->>IPC service endpoint: REL
+
+```
+
+Sequence diagram for Figure 19: Reset initiated in AAL type 2 network. The diagram shows three entities: AAL type 2 node, IWU, and IPC service endpoint. The AAL type 2 node sends a RES message to the IWU. The IWU then sends a REL message to the IPC service endpoint. The diagram is labeled Q.2632.1\_F19.
+
+Figure 19/Q.2632.1 – RES from AAL type 2 network
+
+Table 11/Q.2632.1 – Mapping of RES parameters
+
+| Incoming AAL type 2 RES | Outgoing IPC REL (Note 3) |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| (Note 1) | CAU (Note 2) |
+| NOTE 1 – RES messages carry no parameters requiring interworking.
NOTE 2 – Cause value set to "Temporary failure".
NOTE 3 – If the RES applies to one or more AAL type 2 paths affecting several active connections, a REL message for each of these connections shall be generated at the IP side. | |
+
+### 10.1.2 Reset initiated in IP network
+
+
+
+```
+
+sequenceDiagram
+ participant AAL type 2 node
+ participant IWU
+ participant IPC service endpoint
+ IPC service endpoint->>IWU: RES
+ IWU->>AAL type 2 node: REL
+
+```
+
+Sequence diagram for Figure 20: Reset initiated in IP network. The diagram shows three entities: AAL type 2 node, IWU, and IPC service endpoint. The IPC service endpoint sends a RES message to the IWU. The IWU then sends a REL message to the AAL type 2 node. The diagram is labeled Q.2632.1\_F20.
+
+Figure 20/Q.2632.1 – RES from IP network
+
+Table 12/Q.2632.1 – Mapping of RES parameters
+
+| Outgoing AAL type 2 REL | Incoming IPC RES (Note 3) |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| CAU (Note 2) | (Note 1) |
+| NOTE 1 – RES messages carry no parameters requiring interworking.
NOTE 2 – Cause value set to "Temporary failure".
NOTE 3 – If the RES affects several active connections, a REL message for each of these connections shall be generated at the AAL type 2 side. | |
+
+## 10.2 Reset initiated by the IWU
+
+Analogous to the reset handling in AAL type 2 signalling, a reset procedure initiated by the IWU shall be handled according to Figure 21:
+
+
+
+There may be several REL sequences initiated by the A2IP IWU depending on the scope of the RES and the number of connections affected
+
+Q.2632.1\_F21
+
+Sequence diagram for Figure 21 showing reset handling between AAL2/IP, IWU, and IP/AAL2. The IWU sends a RES message (1) to the AAL2/IP side. The AAL2/IP side responds with an RSC message (3) to the IWU. The IWU then sends a REL message (2) to the IP/AAL2 side. The IP/AAL2 side responds with an RLC message (4) to the IWU. A note indicates that there may be several REL sequences initiated by the A2IP IWU depending on the scope of the RES and the number of connections affected.
+
+**Figure 21/Q.2632.1 – General IWU-initiated reset handling**
+
+Sending of the RES message (1) causes the REL message (2) to be sent.
+
+### 10.2.1 Reset towards the AAL type 2 network
+
+
+
+Q.2632.1\_F22
+
+Sequence diagram for Figure 22 showing RES towards the AAL2 network. The IWU sends a RES message to the AAL type 2 node. The IWU also sends a REL message to the IPC service endpoint.
+
+**Figure 22/Q.2632.1 – RES towards AAL2 network**
+
+**Table 13/Q.2632.1 – Mapping of RES parameters**
+
+| Outgoing AAL type 2 RES | Outgoing IPC REL (Note 3) |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| CAU (Note 2) | (Note 1) |
+| NOTE 1 – RES messages carry no parameters requiring interworking.
NOTE 2 – Cause value set to "Temporary failure".
NOTE 3 – If the RES affects several active connections, a REL message for each of these connections shall be generated at the IP side. | |
+
+### 10.2.2 Reset towards the IP network
+
+
+
+```
+
+sequenceDiagram
+ participant AAL type 2 node
+ participant IWU
+ participant IPC service endpoint
+ Note right of IPC service endpoint: Q.2632.1_F23
+ AAL type 2 node->>IWU: REL
+ IWU->>IPC service endpoint: RES
+
+```
+
+Sequence diagram showing the flow of REL and RES messages between an AAL type 2 node, an IWU, and an IPC service endpoint. The AAL type 2 node sends a REL message to the IWU, which then sends a RES message to the IPC service endpoint. The diagram is labeled Q.2632.1\_F23.
+
+Figure 23/Q.2632.1 – RES towards IP network
+
+Table 14/Q.2632.1 – Mapping of RES parameters
+
+| Outgoing AAL type 2 REL | Outgoing IPC RES (Note 3) |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| CAU (Note 2) | (Note 1) |
+| NOTE 1 – RES messages carry no parameters requiring interworking.
NOTE 2 – Cause value set to "Temporary failure".
NOTE 3 – If the RES affects several active connections, a REL message for each of these connections shall be generated at the AAL2 side. | |
+
+# 11 Messages requiring no interworking
+
+## 11.1 AAL type 2 messages
+
+The following AAL type 2 messages are not interworked when received at the IWU: CFN, RSC, BLO, BLC, UBL, and UBC.
+
+
+
+```
+
+sequenceDiagram
+ participant AAL type 2 node
+ participant IWU
+ participant IPC service endpoint
+ Note right of IPC service endpoint: Q.2632.1_F24
+ AAL type 2 node->>IWU: CFN / RSC / BLO / BLC / UBL / UBC
+ IWU-XIWU:
+
+```
+
+Sequence diagram showing the flow of AAL type 2 messages (CFN, RSC, BLO, BLC, UBL, UBC) from an AAL type 2 node to an IWU. The IWU does not interwork these messages, indicated by an 'X' on the timeline. The diagram is labeled Q.2632.1\_F24.
+
+Figure 24/Q.2632.1 – AAL type 2 messages without interworking
+
+## 11.2 IPC messages
+
+The following IPC messages are not interworked when received at the IWU: CFN, RSC.
+
+
+
+The diagram illustrates the flow of IPC messages between three entities: AAL type 2 node, IWU, and IPC service endpoint. The IPC service endpoint sends a message labeled 'CFN / RSC' towards the IWU. The IWU has an 'X' mark on its vertical line, indicating that these messages are not interworked and are discarded. The AAL type 2 node is shown on the left, connected to the IWU's vertical line. A small label 'Q.2632.1\_F25' is present in the bottom right corner of the diagram area.
+
+Diagram showing IPC messages without interworking. An IPC service endpoint sends CFN / RSC messages to an IWU, which are then discarded (indicated by an X) before reaching an AAL type 2 node.
+
+Figure 25/Q.2632.1 – IPC messages without interworking
+
+# Appendix I
+
+## Interworking of AAL type 2 link characteristics and SSISU parameters with IPC IP transfer capabilities
+
+## I.0 Guidelines and definitions
+
+This Appendix provides rules for conversions between LC-type and TC-type parameters. In some cases, explicit expressions are defined that allow computing outgoing parameter values based on incoming parameter values. These expressions should be understood as formal in the sense that:
+
+- they do not intrinsically request the existence of certain parameters neither incoming nor outgoing,
+- they do not overrule constraints of any type that are defined within any of the interworked protocols.
+
+Due to the modification capability of both interworked protocols, situations may arise where parameters are received in a Modification Request message that contain, in part, identical values compared to those that are already in operation for the part of the network where the modification is received from. Here, application of the conversion rules might lead to an "artificial" alteration of connection parameters in the other network part. In order to avoid these artificial alterations, the corresponding values already in operation in the succeeding network portion shall be used.
+
+This is illustrated with the following example:
+
+For an established connection, the IP side wants to modify only the token bucket sizes. Therefore, a MOD message is sent that contains identical bit rates and maximum packet sizes compared to those that are in use for the IP part of the connection and new token bucket size values. In this case, the MOD message generated by the A2IP IWU for the AAL type 2 network shall contain a Link Characteristics parameter with values identical to those already in use in the AAL type 2 network portion for this connection.
+
+For the purposes of this Appendix, the following shorthand notation shall be used (see Tables I.1 to I.5).
+
+**Table I.1/Q.2632.1 – LC parameter fields**
+
+| |
+|--------------------------------------------------------|
+| A = maximum CPS-SDU bit rate in the forward direction |
+| B = average CPS-SDU bit rate in the forward direction |
+| C = maximum CPS-SDU bit rate in the backward direction |
+| D = average CPS-SDU bit rate in the backward direction |
+| E = maximum CPS-SDU size in the forward direction |
+| F = average CPS-SDU size in the forward direction |
+| G = maximum CPS-SDU size in the backward direction |
+| H = average CPS-SDU size in the backward direction |
+
+**Table I.2/Q.2632.1 – SSISU parameter fields**
+
+| |
+|-----------------------------------------------------------|
+| I = maximum length of SSSAR-SDU in the forward direction |
+| J = maximum length of SSSAR-SDU in the backward direction |
+
+**Table I.3/Q.2632.1 – TC parameter fields**
+
+| |
+|-----------------------------------------------------------|
+| U = peak bit rate in the forward direction |
+| V = sustainable bit rate in the forward direction |
+| W = peak bit rate in the backward direction |
+| X = sustainable bit rate in the backward direction |
+| Y = maximum allowed packet size in the forward direction |
+| Z = maximum allowed packet size in the backward direction |
+
+**Table I.4/Q.2632.1 – PLC parameter fields**
+
+| |
+|--------------------------------------------------------|
+| a = maximum CPS-SDU bit rate in the forward direction |
+| b = average CPS-SDU bit rate in the forward direction |
+| c = maximum CPS-SDU bit rate in the backward direction |
+| d = average CPS-SDU bit rate in the backward direction |
+| e = maximum CPS-SDU size in the forward direction |
+| f = average CPS-SDU size in the forward direction |
+| g = maximum CPS-SDU size in the backward direction |
+| h = average CPS-SDU size in the backward direction |
+
+**Table I.5/Q.2632.1 – PTC parameter fields**
+
+| |
+|-----------------------------------------------------------|
+| u = peak bit rate in the forward direction |
+| v = sustainable bit rate in the forward direction |
+| w = peak bit rate in the backward direction |
+| x = sustainable bit rate in the backward direction |
+| y = maximum allowed packet size in the forward direction |
+| z = maximum allowed packet size in the backward direction |
+
+IPHL shall denote the total length of the header of the IP packet measured in octets and including the IP packet header, the UDP header, and, if RTP is used, the RTP header.
+
+For any real number $x$ , $[x]$ is defined as the smallest integer greater or equal to $x$ .
+
+MAX ( $x_1, \dots, x_n$ ) determines the maximum, MIN ( $x_1, \dots, x_n$ ) the minimum of the values $x_1, \dots, x_n$ .
+
+Bit rates are measured in bit per second ("bit/s"), sizes, e.g., of data structures, in octets.
+
+### I.1 Interworking for AAL type 2 to IP
+
+#### I.1.1 Bit rates
+
+The conversion from LC-type bit rates to TC-type bit rates requires to estimate the rate that will be caused by the IP overhead of length IPHL. This estimate is given in Table I.6. The values are "normalized" to multiples of 64 bit/s.
+
+**Table I.6/Q.2632.1 – IP overhead rates**
+
+| Definition | Meaning |
+|------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|
+| $HBA: = [(IPHL \times A) / (64 \times F)] \times 64$ | Estimate of the IPHL bit rate for the Peak Bit Rate in the forward direction for given LC |
+| $HBA: = [(IPHL \times a) / (64 \times f)] \times 64$ | Estimate of the IPHL bit rate for the Peak Bit Rate in the forward direction for given PLC |
+| $HBB: = [(IPHL \times B) / (64 \times F)] \times 64$ | Estimate of the IPHL bit rate for the Sustainable Bit Rate in the forward direction for given LC |
+| $HBb: = [(IPHL \times b) / (64 \times f)] \times 64$ | Estimate of the IPHL bit rate for the Sustainable Bit Rate in the forward direction for given PLC |
+| $HBC: = [(IPHL \times C) / (64 \times H)] \times 64$ | Estimate of the IPHL bit rate for the Peak Bit Rate in the backward direction for given LC |
+| $HBc: = [(IPHL \times c) / (64 \times h)] \times 64$ | Estimate of the IPHL bit rate for the Peak Bit Rate in the backward direction for given PLC |
+| $HBD: = [(IPHL \times D) / (64 \times H)] \times 64$ | Estimate of the IPHL bit rate for the Sustainable Bit Rate in the backward direction for given LC |
+| $HBd: = [(IPHL \times d) / (64 \times h)] \times 64$ | Estimate of the IPHL bit rate for the Sustainable Bit Rate in the backward direction for given PLC |
+| NOTE 1 – If a denominator turns out to be zero in any of the expressions above, the result of the expression shall be set equal to zero. | |
+| NOTE 2 – If a factor does not exist in any of the expressions above, the result of the expression shall be set equal to zero. | |
+| NOTE 3 – The definitions in this table are formal. Whether or not a certain expression is required, is determined by the interworking. | |
+
+Table I.7 defines the interworking of LC bit rates (AAL type 2) to TC bit rates (IP).
+
+**Table I.7/Q.2632.1 – TC bit rates determined from LC**
+
+| TC parameter field | Value |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|
+| U | A + HBA |
+| V | B + HBB |
+| W | C + HBC |
+| X | D + HBD |
+| NOTE 1 – The interworking and the involved protocols determine whether or not a certain field is required.
NOTE 2 – The involved protocol determines whether or not a certain value is meaningful and valid. | |
+
+Table I.8 defines the interworking of PLC bit rates (AAL type 2) to PTC bit rates (IP).
+
+**Table I.8/Q.2632.1 – PTC bit rates determined from PLC**
+
+| PTC parameter field | Value |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|
+| u | a + HBa |
+| v | b + HBb |
+| w | c + HBc |
+| x | d + HBd |
+| NOTE 1 – The interworking and the involved protocols determine whether or not a certain field is required.
NOTE 2 – The involved protocol determines whether or not a certain field is required. | |
+
+#### I.1.2 Maximum allowed packet sizes
+
+Table I.9 defines the derivation of TC and PTC maximum allowed packet sizes from LC and PLC CPS-SDU sizes and/or SSISU.
+
+**Table I.9/Q.2632.1 – Determination of maximum allowed packet sizes**
+
+| TC/PTC SDU size subfields | Value |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|
+| Y | IPHL + MAX (E, I) |
+| Z | IPHL + MAX (G, J) |
+| y | IPHL + MAX (e, I) |
+| z | IPHL + MAX (g, J) |
+| NOTE 1 – "0" is assumed as value to guarantee a correct working of the MAXimum function if a certain parameter does not exist.
NOTE 2 – The interworking and the involved protocols determine whether or not a certain field is required.
NOTE 3 – The involved protocol determines whether or not a certain field is required. | |
+
+#### I.1.3 Token bucket sizes
+
+The A2IP interworking unit shall set the token bucket sizes to the allowed maximum values. The allowed maximum value is the minimum out of the maximum defined by the protocol and the maximum defined within the network.
+
+NOTE – An appropriate adjustment of the token bucket sizes controlled by the served user may be initiated from the IP network portion with a subsequent MOD message.
+
+#### **I.1.4 Determination of the TC class**
+
+ITU-T Rec. Q.2631.1 [2] supports two IP transfer capability classes: dedicated bandwidth and statistical bandwidth transfer capability.
+
+For an incoming connection set-up from the AAL type 2 network portion, the AAL2IP interworking unit has to determine the IP transfer capability class to be used in the IP portion.
+
+If all subsequent conditions
+
+- C1) A = B
+- C2) C = D
+- C3) E = F
+- C4) G = H
+- C5) MSLC not set
+
+are satisfied, the dedicated bandwidth transfer capability shall be selected. If at least one of the conditions C1), ..., C5) is not fulfilled, the statistical bandwidth transfer capability shall be applied.
+
+NOTE – If no LC parameter is received and no specific provisions are applied for this case, the A2IP IWU may reject the connection request.
+
+### **I.2 Interworking for IP to AAL type 2**
+
+#### **I.2.1 Bit rates**
+
+The conversion from TC-type bit rates to LC-type bit rates necessitates the estimation of the portion that is induced by the IP overhead of length IPHL. This estimate is given in Table I.10. The values are "normalized" to multiples of 64 bit/s.
+
+**Table I.10/Q.2632.1 – Received IP overhead rates**
+
+| Definition | Meaning |
+|----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|
+| $\text{HBU} := [(\text{IPHL} \times \text{U}) / (64 \times \text{Y})] \times 64$ | Estimate of the IPHL bit rate portion in the Peak Bit Rate in the forward direction for given TC |
+| $\text{HBu} := [(\text{IPHL} \times \text{u}) / (64 \times \text{y})] \times 64$ | Estimate of the IPHL bit rate portion in the Peak Bit Rate in the forward direction for given PTC |
+| $\text{HBV} := [(\text{IPHL} \times \text{V}) / (64 \times \text{Y})] \times 64$ | Estimate of the IPHL bit rate portion in the Sustainable Bit Rate in the forward direction for given TC |
+| $\text{HBv} := [(\text{IPHL} \times \text{v}) / (64 \times \text{y})] \times 64$ | Estimate of the IPHL bit rate portion in the Sustainable Bit Rate in the forward direction for given PTC |
+| $\text{HBW} := [(\text{IPHL} \times \text{W}) / (64 \times \text{Z})] \times 64$ | Estimate of the IPHL bit rate portion in the Peak Bit Rate in the backward direction for given TC |
+| $\text{HBw} := [(\text{IPHL} \times \text{w}) / (64 \times \text{z})] \times 64$ | Estimate of the IPHL bit rate portion in the Peak Bit Rate in the backward direction for given PTC |
+| $\text{HBX} := [(\text{IPHL} \times \text{X}) / (64 \times \text{Z})] \times 64$ | Estimate of the IPHL bit rate portion in the Sustainable Bit Rate in the backward direction for given TC |
+| $\text{HBx} := [(\text{IPHL} \times \text{x}) / (64 \times \text{z})] \times 64$ | Estimate of the IPHL bit rate portion in the Sustainable Bit Rate in the backward direction for given PTC |
+
+NOTE 1 – If a denominator turns out to be zero in any of the expressions above, the result of the expression shall be set equal to zero.
+
+NOTE 2 – If a factor does not exist in any of the expressions above, the result of the expression shall be set equal to zero.
+
+NOTE 3 – The definitions in this table are formal. Whether or not a certain expression is required, is determined by the interworking.
+
+Tables I.11 and I.12 define the interworking of TC/PTC bit rates (IP) to LC/PLC bit rates (AAL type 2) if a statistical bandwidth transfer capability was received.
+
+**Table I.11/Q.2632.1 – Interworking of TC to LC bit rates**
+
+| LC parameter field | Value |
+|--------------------|---------|
+| A | U – HBU |
+| B | V – HBV |
+| C | W – HBW |
+| D | X – HBX |
+
+NOTE 1 – The interworking and the involved protocols determine whether or not a certain field is required.
+
+NOTE 2 – The involved protocol determines whether or not a certain field is required.
+
+**Table I.12/Q.2632.1 – PLC bit rates determined from PTC**
+
+| PLC parameter field | Value |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|
+| a | u – HBu |
+| b | v – HBv |
+| c | w – HBw |
+| d | x – HBx |
+| NOTE 1 – The interworking and the involved protocols determine whether or not a certain field is required.
NOTE 2 – The involved protocol determines whether or not a certain field is required. | |
+
+For received dedicated bandwidth transfer capability, Tables I.13 and I.14 define the interworking of TC/PTC bit rates (IP) to LC/PLC bit rates (AAL type 2).
+
+**Table I.13/Q.2632.1 – Interworking of TC to LC bit rates**
+
+| LC parameter field | Value |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|
+| A | U – HBU |
+| B | U – HBU |
+| C | W – HBW |
+| D | W – HBW |
+| NOTE 1 – The interworking and the involved protocols determine whether or not a certain field is required.
NOTE 2 – The involved protocol determines whether or not a certain field is required. | |
+
+**Table I.14/Q.2632.1 – PLC bit rates determined from PTC**
+
+| PLC parameter field | Value |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|
+| a | u – HBu |
+| b | u – HBu |
+| c | w – HBw |
+| d | w – HBw |
+| NOTE 1 – The interworking and the involved protocols determine whether or not a certain field is required.
NOTE 2 – The involved protocol determines whether or not a certain field is required. | |
+
+#### I.2.2 CPS-SDU sizes
+
+Tables I.15 and I.16 define the derivation of LC/PLC CPS-SDU sizes from TC/PTC maximum allowed packet sizes.
+
+**Table I.15/Q.2632.1 – TC to LC CPS-SDU size interworking**
+
+| LC CPS-SDU size subfields | Value |
+|---------------------------|--------------------|
+| E, F | MIN (Y – IPHL, 45) |
+| G, H | MIN (Z – IPHL, 45) |
+
+**Table I.16/Q.2632.1 – PTC to PLC CPS-SDU size interworking**
+
+| PLC CPS-SDU size subfields | Value |
+|----------------------------|--------------------|
+| e, f | MIN (y – IPHL, 45) |
+| g, h | MIN (z – IPHL, 45) |
+
+#### I.2.3 SSISU SDU sizes
+
+Table I.17 defines the derivation of SSISU SDU sizes from TC and PTC maximum allowed packet sizes.
+
+**Table I.17/Q.2632.1 – TC and PTC to SSISU interworking**
+
+| SSISU subfields | Value |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|
+| I | MAX (Y – IPHL, y – IPHL) |
+| J | MAX (Z – IPHL, z – IPHL) |
+| NOTE 1 – "0" is assumed as value to guarantee a correct working of the MAXimum function if a certain parameter does not exist.
NOTE 2 – If the value of all SSISU subfields determined according to these rules does not exceed 45, no SSISU parameter will be generated at all.
| |
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure, Internet protocol aspects and Next Generation Networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.2730-199912-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cc355b2fd573fd17849e29784150d1e9f191b20f
--- /dev/null
+++ b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a54dd979fe9978deb2d90e58213549d7a175abac306f96b6a511dc4f145def1e
+size 95114
diff --git a/marked/Q/T-REC-Q.2730-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ab2cbdd4af6bc1ea9ffa8cca87f9d455eb147008
--- /dev/null
+++ b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:94ee226724314e8b36ac3c73e99f9ed2a4fbb4786e0c7f3f43c1debd5966aa00
+size 8239
diff --git a/marked/Q/T-REC-Q.2730-199912-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..db884e8b39ec38efe6efa6f1ac7e50e026782be1
--- /dev/null
+++ b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2e7ba586da6310cc34a74e262de007cc2c0dc08765eb42d1a536f067b13b593e
+size 143417
diff --git a/marked/Q/T-REC-Q.2730-199912-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..20e26fe88f2c050048d466d2ad3379edda255ea5
--- /dev/null
+++ b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b0c2ce5cfe751c3502e7ccdeab2c08186b29f90f7c04c3a4c13acf52162e0575
+size 143839
diff --git a/marked/Q/T-REC-Q.2730-199912-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..54271ac2b493475c8f6a3905b01e4842f9ff3006
--- /dev/null
+++ b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ed9f74538dfd8c7d4f9287e0ca3dd29beae47cc3c8aa82beba548b85cd8da753
+size 168797
diff --git a/marked/Q/T-REC-Q.2730-199912-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..09110394009a0349e354ac0572885ee706476b0b
--- /dev/null
+++ b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:28a89c87d29914e8ac420e6db9341941e12c2247cefa8f950e2c7665dcfa71a4
+size 96238
diff --git a/marked/Q/T-REC-Q.2730-199912-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7548a5bcf854a8889d34f35fe42dc72ab93763f8
--- /dev/null
+++ b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e100c9c13f5126b2e8800a956ec621b622913dde2d22bebdff7b6f6d5b947470
+size 113865
diff --git a/marked/Q/T-REC-Q.2730-199912-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..260a5e06011b0f9b1b6d5f8ef75c1e1c16b5091e
--- /dev/null
+++ b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2619ef28484b324940a3a1647ea13e24f41b5755d61464cd28c5f17e6dc766c5
+size 167465
diff --git a/marked/Q/T-REC-Q.2730-199912-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a8d9e1c4379a34f04fa3f2313d6170123fb68e2d
--- /dev/null
+++ b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8697484e4c89bd3475e246d8920526d6be237e85008304775cecd63f4507f5cf
+size 135939
diff --git a/marked/Q/T-REC-Q.2730-199912-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6682f239699208860762975688d8537874fe8e0a
--- /dev/null
+++ b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d4c97d92830632a3e15b32dc95fc7387e5a937748342272d87f0c993e022a2ca
+size 95853
diff --git a/marked/Q/T-REC-Q.2730-199912-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d25ea7ed8a805fe474040278cc7b4fa7d54a1f2c
--- /dev/null
+++ b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8e82f063c75049e2c3c8b4f6fb0c5df005c1321e063aff6d0dfe19da08b4c89f
+size 160069
diff --git a/marked/Q/T-REC-Q.2730-199912-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..052ce18e10e96d66ce0194fbcb8256875e9adf8c
--- /dev/null
+++ b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:baf0c485b2e95b367464a956c7d8777a806e93e3da3dae47754f93fb64754ec7
+size 111578
diff --git a/marked/Q/T-REC-Q.2730-199912-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f92a349dee2cf3f059c343b6a459aa86172343e0
--- /dev/null
+++ b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc6b9760b6646131fbf41323555fe639d049bacc494402c35a15cc23cbd6d642
+size 92334
diff --git a/marked/Q/T-REC-Q.2730-199912-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7255dd3b6a5525b5b0e41c26f11c665fa9169729
--- /dev/null
+++ b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae251e1cc634b40371899c00340877a40665223938cfb7e1993abba5c237cad6
+size 104126
diff --git a/marked/Q/T-REC-Q.2730-199912-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f78db91135ef97cb342c7d894d0badf8826b2170
--- /dev/null
+++ b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:57b4ac67767ffca27324dc27529425d4804ef5dd72e80dc6763c8221081505cc
+size 88277
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/00a0b3a0485d8e735df9cb73dbdf36d6_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/00a0b3a0485d8e735df9cb73dbdf36d6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..25be1068bde5960be2f63127b359fec97c306465
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/00a0b3a0485d8e735df9cb73dbdf36d6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a1c872e929cf9472ce81974d0356893d10be7a4532109367d8dd4781806b03cf
+size 20520
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/01f07707259cb0193a962c1eaf725055_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/01f07707259cb0193a962c1eaf725055_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9b44abdc7d83d1c5b1f7f1fd38949d3d39d692ea
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/01f07707259cb0193a962c1eaf725055_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:28c642a3f9509575f797648b3a33e3c6bfe48354d019611ed08c6818dcd3ab0d
+size 181383
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/04f1a971a602ced3c6096d46de1cf29c_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/04f1a971a602ced3c6096d46de1cf29c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e3c1ffeb3e4728c8a21c8979bb6448f20b548ab5
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/04f1a971a602ced3c6096d46de1cf29c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8792242fc409ec7dfe9b9f6f6adffae76a0b6bfdb65dadc46570d07d6bcbac21
+size 193366
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/07c0c40e07af066b06f77e9d74b193fc_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/07c0c40e07af066b06f77e9d74b193fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9f94abc75ffb945ff6db3c8b75b31e5c39aa57ec
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/07c0c40e07af066b06f77e9d74b193fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b29e5d7a8a49f110841746ff969a79e336dceb2b6db025ab05d722438c47577b
+size 16344
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/0850300da6b28250eb47881da35cabad_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/0850300da6b28250eb47881da35cabad_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dcaba24f4cace0e07c13bd90407ebf5082fab37f
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/0850300da6b28250eb47881da35cabad_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:70a1949ffc622b1127245d1228ea33f83cfc6edb7d1bfe67f2bfadb56a18a892
+size 35661
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..538f0ce0d0908f0f03a81d1602b45019abac879c
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:55b256f0619c594c8afe79412d8cb6dde7cb529010e4c0ac360d49213aa820eb
+size 48824
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/0e97550fb1a8a7e793a8325afac3700a_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/0e97550fb1a8a7e793a8325afac3700a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bf7c0a4e28691e84c9ddd6867fc538d9b50b4bd4
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/0e97550fb1a8a7e793a8325afac3700a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a5402f4afe61d613ef5222cb436f792f8962a8b1a1d0d1e6bc3259f9aa466263
+size 134257
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/100034b8a21a13b0ad0925a2c38c220f_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/100034b8a21a13b0ad0925a2c38c220f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6b6bf5b318c697b44d6ffaec14a5b75aa320be16
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/100034b8a21a13b0ad0925a2c38c220f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ac8cbc7adcbf076be044a097c5d7903cdb2ad9c95ef63d8f82a71bc3e10bddf5
+size 113579
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/10010fcefe204986cf1b520d10619766_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/10010fcefe204986cf1b520d10619766_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..220342dc7d9702870874546c741312099c186a51
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/10010fcefe204986cf1b520d10619766_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f6200c97f6a07ebb784dc37dbbca99bccebf72ff47ebc3472c42aac797c0354d
+size 84297
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/10f4e3a2f3c016555ee12a5b556ba834_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/10f4e3a2f3c016555ee12a5b556ba834_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c3e0aefe5818fed574f767de47a1ce63512e822c
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/10f4e3a2f3c016555ee12a5b556ba834_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:702b00309d942d13973fcc732507bf3e302c06d835a405f92138caf5643fe09b
+size 68218
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/166d8ee3cc0c825044a113560f81799c_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/166d8ee3cc0c825044a113560f81799c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4d05e9ea263741a4fd6525bad80757faa0542898
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/166d8ee3cc0c825044a113560f81799c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:39f5a935b1b6b6fcdeea67fbbce876f1c6eb72cda3e53f94a8666c9eddf7d4e9
+size 52208
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1684f5f8c34bd0ef6e933664d88b9d86_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1684f5f8c34bd0ef6e933664d88b9d86_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..31edcb73f19ff79a7e58c56117d9668f5d02c512
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1684f5f8c34bd0ef6e933664d88b9d86_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5afa25e50301081a11813095ef646736525279bdce78efb7ad921a9b4cae5765
+size 97726
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/16c8aea7b68120358abcb5ef6ef3ae0b_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/16c8aea7b68120358abcb5ef6ef3ae0b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..97ded8b549146a19399793b45245fcd62203c15f
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/16c8aea7b68120358abcb5ef6ef3ae0b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4cc62f117d0b8525680a545a51eb23f424c787eadfa970849454e3d7ff106e5b
+size 131269
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..366b6eda3a9465b7e257f335c6041df65727f107
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:32d343de22e498188f340adeaec3907842175ec9bd20210529d4181aa5104f2f
+size 52104
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1b2ad37940c441d410002c05ff71c7c5_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1b2ad37940c441d410002c05ff71c7c5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0eb890551d5134e6fe5c87104f126d2b52f5a45b
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1b2ad37940c441d410002c05ff71c7c5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:85749a74a8c2287ad317addb3f0f460568f6ab9628718d08667e7ca23b783e72
+size 16164
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1c3caf3c28fe1461a879e214f5df25ae_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1c3caf3c28fe1461a879e214f5df25ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..458c9b0836581a0f2ce414ec58e192328f6b9bf6
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1c3caf3c28fe1461a879e214f5df25ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c07f647b6d3977ab92fbc4150b899c90e74194c14531fe11cd7d090662a93745
+size 129375
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c0f44c8cae08f31f2daca3553634e94eb80a33ed
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:105c722a497986dbe280254b223b73662aa7e58ded29237f04d51537c257abe3
+size 39001
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1ce027dfd26183da52137cf990213724_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1ce027dfd26183da52137cf990213724_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aa158ce5678f0b74aababe4789bb01a6e330702b
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1ce027dfd26183da52137cf990213724_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cd0bb21616a016108700c3374c7c644e0b205413f37e6c3e4c3996d1dc834ac0
+size 32136
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1daee79ab1ab652586116f083d50ed9d_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1daee79ab1ab652586116f083d50ed9d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..223c8de341198ec56fc9836296a4acb4e27aeab8
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1daee79ab1ab652586116f083d50ed9d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8f6e46344784142d2a78093edbeb6af92bb989504d676db8adb11ecdb2296f81
+size 37389
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1e95fc0be1c9782d078a26fb32facddd_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1e95fc0be1c9782d078a26fb32facddd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1c5eec62a8dbfcac2ea47d76c89015b33a031ce0
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1e95fc0be1c9782d078a26fb32facddd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1f8a282e25ab6603a4fa3814dc854c3dbc302763076a6a2c4009efd28b40e8f5
+size 112071
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..18f99512927950552bdae054be231f161c785b37
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:47b141a4530dd973b2d2abbcef6faa99b182983237654a063597a88e5bbfd5b8
+size 37514
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/200e768e8ed91aadff59c651287d1009_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/200e768e8ed91aadff59c651287d1009_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9cff92653e285e0a61a74f47ca8ba0c9cf9a562e
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/200e768e8ed91aadff59c651287d1009_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e52f631a9cec08efe5ea46a6cfb99caa568ccbb47d7bcc0cd5bd544385947511
+size 119911
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/23e6f8e908eb73b54a419d58740a33bb_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/23e6f8e908eb73b54a419d58740a33bb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..45c120a88f60c8e576b74c97dcd9f2739a7232f5
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/23e6f8e908eb73b54a419d58740a33bb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6eab15f5993b96bc941fed631a3526729519fc16fe01c3adc786c10bb22dadac
+size 31379
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/2459fa4a80d88e7c50e49e56d67c2e76_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/2459fa4a80d88e7c50e49e56d67c2e76_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..829ffa6e4709509ede2c34090dfcf3fe7d7d3e5a
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/2459fa4a80d88e7c50e49e56d67c2e76_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dc8ff41a3783fd968b26b668aa6a60b566832e7ca8ff8fdc0e2ebbc4f5d480e4
+size 43020
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/24a5d31d8d81bf0e4fe402416b8b2f49_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/24a5d31d8d81bf0e4fe402416b8b2f49_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6c344b5bddf5a56e6286e0f2063572a85a517e86
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/24a5d31d8d81bf0e4fe402416b8b2f49_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d1195608c60e8646e1f8c46ae656e55b802ab74acf22d9ca189c199993c77452
+size 120758
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5f1d111bc2220aad7d0275fdb437af1d908a23c8
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4bab2a3c7d3df22a79c7738fd7dc8f9f8b4cb8ad8e8cd031a4b96c8317cb0598
+size 16446
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/2650ae98f0e6dda48ae00a936ddea0ef_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/2650ae98f0e6dda48ae00a936ddea0ef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bf021235bca36e961f13ec206f466c873a7f3032
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/2650ae98f0e6dda48ae00a936ddea0ef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dc1df10f29a29bf03c9ccd75902e39ecc8624463a887cb469afda1942640ff6b
+size 37123
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/29043c6ca27a7cfbc757a5d2eb029d33_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/29043c6ca27a7cfbc757a5d2eb029d33_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9064fc91cad217afa98f759bfdc93a3a95785059
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/29043c6ca27a7cfbc757a5d2eb029d33_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dec64ebad30cc8afabfd7e0eef944c2fdfc079b6ca3ee4d582dd254823c3204e
+size 43036
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/2cdc3be3de33b97cdd52a0805b399419_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/2cdc3be3de33b97cdd52a0805b399419_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ccbab3dc4e34d4fd5c3c27fd9fd9b84d72a6b056
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/2cdc3be3de33b97cdd52a0805b399419_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:54c68a786bf76b5f615f3fda6974bd3dedcbbea8941a8c8a925cd9f6f916de84
+size 127817
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/2cf1f70c3a387c43e15192a30d212546_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/2cf1f70c3a387c43e15192a30d212546_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c39657d57888970cf079aed524830efc40e6e269
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/2cf1f70c3a387c43e15192a30d212546_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2964b1ff1a4a367be5acdfa1cb63208ffd5d9c78422875cc8abeac4ae4ddd2bb
+size 150866
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f3526b4bfa3e723ad003c1802f255891ae4506e1
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e22990b3b220b8e4f150c8128119ecc9de91fc2f01e56bed1f6ccfb4a46ddf3e
+size 8197
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/30510f8d9131bf007cc020f25046c9ad_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/30510f8d9131bf007cc020f25046c9ad_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b75e687a6641e5271725045c22071abad3c3cf06
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/30510f8d9131bf007cc020f25046c9ad_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0739326fc727cfa9b1cdfa07a1dfb2dd6e85fb60d14f672b369f1fedec6f0be4
+size 130748
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3054e46608784063609e8c7a253fcd24_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3054e46608784063609e8c7a253fcd24_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ce3a2e855b290dea6b332b69b141f51a74ca5c75
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3054e46608784063609e8c7a253fcd24_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0226d7f59be136a87fd4361b01d170682efabdb518089449868556b3c8b203d9
+size 134941
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..91ed6508b44ce961191a3d7b78ecbadbcc02b650
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4ae49abd6c1ac603ff5f743696b4a352d675a94aee80115289ca3e7b3c10e480
+size 36216
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3220d3a933797114c1ba20d5c4ec093d_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3220d3a933797114c1ba20d5c4ec093d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8c872a777ecf26083ae47ce2634e5740dd2df36f
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3220d3a933797114c1ba20d5c4ec093d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:926e2db1de63e458efd607b294985bbf01380973b588ef4b95960d5450e7cfe1
+size 155502
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9de4dfab6a41aafbb474474158153f22d09f4ffb
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fc49fd00f6c39949861c42f010a6342cce6e8e12aac92f1157137af210cd425b
+size 42445
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3429a2cee05dee88538d8b6816a5a877_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3429a2cee05dee88538d8b6816a5a877_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..df732de7461e4a002b6a9fc103cbf947f086dacb
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3429a2cee05dee88538d8b6816a5a877_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9943a60d8db67ea91810b8c876262a11cde5428072155632cb95a01520acf079
+size 106626
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/387a316ca4f909a5260b0c5e232d5cc8_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/387a316ca4f909a5260b0c5e232d5cc8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d0633c3a3266c20c21fd64d669a8ad359cea04b2
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/387a316ca4f909a5260b0c5e232d5cc8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1ce2e201834532a2df1d232aebed1de9ea49fa4b7b3f701840c2844c12c4190c
+size 10834
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3b20eb477ef174b7adaad37703f5d611_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3b20eb477ef174b7adaad37703f5d611_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d083b06db961dcca72f60f87b2c7b2d483ee5e0e
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3b20eb477ef174b7adaad37703f5d611_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bea0d4581ee772b4ee1a3eb9a78b68ed685d68bdc620f7eaeeb7586e7b214a70
+size 125535
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3c0be9369e1f99f7f820fda3f9d676e6_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3c0be9369e1f99f7f820fda3f9d676e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6aa14ba203def27ab333186a97cef964b9d8f69e
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3c0be9369e1f99f7f820fda3f9d676e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:736ef421f3c5c37e8bf3347afe6e05b6b3cd98298c42b121c7f6a23e5bb541f2
+size 115122
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3c8ddf97c5854434ed0c16c733ac5d95_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3c8ddf97c5854434ed0c16c733ac5d95_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..00c4984e495352e76fe474cece2507f5485c87a5
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3c8ddf97c5854434ed0c16c733ac5d95_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2217db6e492b455f2a439f90082a5075b629d853346ed1798b67560df10c6d8
+size 83216
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3d13999d5257e24e629f65f28bf10251_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3d13999d5257e24e629f65f28bf10251_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3f8bf94532d720680663655ffe611676ce57d93e
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3d13999d5257e24e629f65f28bf10251_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f29988a9134e9169e31dc51e3326612bc0fe63db24f25a49d0550f4d53411b61
+size 115405
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3f2ccb513ccdda4c3e19aea59f7f6215_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3f2ccb513ccdda4c3e19aea59f7f6215_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8709643837d4b45e32d292d66d3b2f5038fbf0bb
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/3f2ccb513ccdda4c3e19aea59f7f6215_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:99788482752399136d8a1a9fe671b59f0c9df8e1b0c8613574c27019a8f00a63
+size 53799
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/40135f3a8f5a6789225806e70870256d_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/40135f3a8f5a6789225806e70870256d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..19d52a36ef17ac463435c6bb2a5030c9c56dda6a
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/40135f3a8f5a6789225806e70870256d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fc521bbb38630266ca7c5b94a3a5ea2459f42173684e629eba170e76eaa3e073
+size 70295
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/401f020d9ab5904f584424eabb596d2c_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/401f020d9ab5904f584424eabb596d2c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f9526af4d39acdb8ec1d084a9b998b5ea09fcbc6
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/401f020d9ab5904f584424eabb596d2c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1e2af0befa5fbfff9a0372620431bf228baa2e2eefd6e0fd3e367c89d61bbf8
+size 51724
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/4224f170b677d60f6f86ce95d8dc725a_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/4224f170b677d60f6f86ce95d8dc725a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..138055b00bbb2fecf3f0d7c5a328609511bc8508
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/4224f170b677d60f6f86ce95d8dc725a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:13e84062e443621d8bf390ad18a38ddbe3dfc09d2fe02e122322aa147440a002
+size 36564
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/426a0ab9454f31706038a0ac0bc37b9c_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/426a0ab9454f31706038a0ac0bc37b9c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9a439958a3c6cb7101c63e2028bbfe9e41f94c55
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/426a0ab9454f31706038a0ac0bc37b9c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7c48bc6d72f40eb7f74b679cd86dcc89a4492a22eab655204d8ae1e1f0729a8f
+size 111324
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/4537891530c9f6f139a2e1ebf544edc4_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/4537891530c9f6f139a2e1ebf544edc4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..68077bf13eb8bad4f31a9b07a2946423f5a2d449
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/4537891530c9f6f139a2e1ebf544edc4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4d66f0503076cc8cdcfa8a9f91ee89cb9cdd990698309fe39d0e12e36f1cc13b
+size 36343
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/46357bd4781f8f8f776667fb096f54a9_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/46357bd4781f8f8f776667fb096f54a9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ba305b4c9efa68078381abd3cfc5a53968d71bb7
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/46357bd4781f8f8f776667fb096f54a9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:075e0813ef56019b2c841f2f5e4ae73a436dd29a8711918932990bdecbab1470
+size 33747
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/47702b55f927e2e85ac03e79a7ebe350_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/47702b55f927e2e85ac03e79a7ebe350_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..26a2d46711b7b78d9f9e4154bedd763278f0ea8c
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/47702b55f927e2e85ac03e79a7ebe350_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:674c8b7c8666b303ae9713dc49204a6076f9fe6f3a577897faed5114a48ea6f0
+size 35562
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/4847c98185bc52e8786b78738bc52b45_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/4847c98185bc52e8786b78738bc52b45_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5c9af23335439c692c8a55ce0f60c43bcd968bb6
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/4847c98185bc52e8786b78738bc52b45_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3f91e84a9ccc89309a3dca5fc1d39a585932b184323b4ac317c82e0d64c38ce0
+size 43371
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/49b3ce1af68a5ece151a15b0b693f80b_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/49b3ce1af68a5ece151a15b0b693f80b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7066a22cc1410fa084d9aa166715cc0e42db785b
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/49b3ce1af68a5ece151a15b0b693f80b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:29d30b8629ec6c1b841fc7e5d39bd57c48a06490ee93ef2fe4420962173796bc
+size 40926
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/49fe8fe978c0f7e73112d231feb377eb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3e5069b97f7f30f2acb551418a46d7c38f8ccfc2
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/49fe8fe978c0f7e73112d231feb377eb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:91de3f3af81bd4b3b001381f89addb7a3f635774320a52bf8d69b2c69083a127
+size 34728
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/4b9e2f848d66a0b3c2d4553b965933c7_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/4b9e2f848d66a0b3c2d4553b965933c7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6bacf95604a72943330fa83c6b7603ba48a2c89f
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/4b9e2f848d66a0b3c2d4553b965933c7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0952911b2adff01d2dc9617a7369620f4d9e771f2e7343150d6e74671a415aff
+size 20612
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/4c63a0e17b54c7e61d512c276932114c_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/4c63a0e17b54c7e61d512c276932114c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0bc93e3c17a17c93a323a5bbce20db52153dd4f6
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/4c63a0e17b54c7e61d512c276932114c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:44603494856cef6fd8b106c1932d3791dc08505f9abe6e650bf31c7de14e6953
+size 32923
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/53499879d98034410ecba2c386c58f0c_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/53499879d98034410ecba2c386c58f0c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cf318572ddaa39e141462447441d7f9cf04240c9
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/53499879d98034410ecba2c386c58f0c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b3a33e0ea034fd8d12dac980018a80a71a7f9fe1f180cdffe88f75bbfaec6d3a
+size 65572
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/5496c3d362352cb64af48bb3a5dd20f5_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/5496c3d362352cb64af48bb3a5dd20f5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e3f454b3528f1e7da116942ffe2efeac0a8656ee
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/5496c3d362352cb64af48bb3a5dd20f5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:12175b6560f51c6440f01c7cb54bbf87da4ff8ba386b273c3855442b177d0cf9
+size 155244
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/5661815043254c37a4e3e4833f51e727_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/5661815043254c37a4e3e4833f51e727_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9984d929fa48dd203be516993c10064d2116ce7f
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/5661815043254c37a4e3e4833f51e727_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:776b7db388c9da08569e177881c5d3fe4ed22046303f9d180b6ce7ef0b7bc48e
+size 21296
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/5a3dccee8ce4d2fa1986aba4ae8ad6e2_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/5a3dccee8ce4d2fa1986aba4ae8ad6e2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1f03d9d81d97186f683e8e298747cbfce8435c5e
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/5a3dccee8ce4d2fa1986aba4ae8ad6e2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:11669c1c4aff404cce76ed27cfbe140c134976d19b3d77b3dee421466772e125
+size 129754
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9d48ae2c518ea107741253906cafbdb340645827
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:800413a1fe57d642da83c9fbc5bdd85ef907464003d4cf11c2011858674817ac
+size 39566
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f38163e4ea1a33d592e2123330fddbc69087029c
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd68bcf255f2ceb3a7d9f4b55bdae4c0b64c4e321aecd455cc10a37be589a8b3
+size 48278
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/60b089b85e598003112e72e9d4f19c5c_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/60b089b85e598003112e72e9d4f19c5c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..eba64f9cbc24096baf6d6c0034eabf39e34ffe6c
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/60b089b85e598003112e72e9d4f19c5c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ab8f47832ef7bea580c5aa0efde25b91504d449cba794c065813ad4055766972
+size 63460
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/633486b12958f97e062b5cf9e0801e99_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/633486b12958f97e062b5cf9e0801e99_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fad349d957facc7a3dd6adfbb52a0a3048d96fb2
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/633486b12958f97e062b5cf9e0801e99_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:367df38814cd6e5ffb3907a1cf13d0f7d46b05734e95a101456ed9334a4cd285
+size 114521
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6424fc1c7a7c26364a135780c1e479f9_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6424fc1c7a7c26364a135780c1e479f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c35019f58c9cf94b7ce675a163b66afe76571539
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6424fc1c7a7c26364a135780c1e479f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fc553a01e9a2eadb242da3374542b3b43bd7cd4235f323d0155367884d773733
+size 44718
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/662c84f65e27aff9b64ec351f9d8cca8_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/662c84f65e27aff9b64ec351f9d8cca8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..520097e0ecd944f746e838619853b2f3bacf8122
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/662c84f65e27aff9b64ec351f9d8cca8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5e84c28e6f5b1cba6903d17bec076d5c968c00aca7aae586c71d9cb50631f999
+size 113562
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/670a9057bbab8c7c0eb91db3a6de4d55_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/670a9057bbab8c7c0eb91db3a6de4d55_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bac776ada30c400cb46207c41ae0255349da6f22
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/670a9057bbab8c7c0eb91db3a6de4d55_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:110af71fea61e867bc5e13798d279d105e8de00e779285e10d7f92730e9d02d9
+size 60016
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/683f755e8456c884716de4fce48c7e63_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/683f755e8456c884716de4fce48c7e63_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..41cb44175ef1ebe697fbcbef5702108def44d058
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/683f755e8456c884716de4fce48c7e63_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1d4e413b1aedaf6a0eeda2f98b3feb3f2513b5571db5a7d63e8028d458237e38
+size 35740
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/68b20651884fcd557e865537f0803de5_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/68b20651884fcd557e865537f0803de5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2f925b3f2f5456178d4b82d7a197161a59d2bbb4
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/68b20651884fcd557e865537f0803de5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f945f00a6e1a041e8746593d8a2ae86b3bb28adb3903a913b3f2e224016aac07
+size 57320
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6a2b92323d788c2e7e9e570025885181_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6a2b92323d788c2e7e9e570025885181_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d4b10cdaafc44ba36139b9fdd9a7a790614af70f
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6a2b92323d788c2e7e9e570025885181_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7446b5abadc27fa1a7ae125e626a135a4f7eaa9848f9bae50f24ac8ec80a3006
+size 131929
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6ab36474772ce6a61e97fd5d19770270_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6ab36474772ce6a61e97fd5d19770270_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..37d100ea754a68863a934b3b4b587e6d15827a3a
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6ab36474772ce6a61e97fd5d19770270_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:51b5a3f9716cc12a0613c4f9c51a2cb40050c1a9f76a8640773d1aeeb91bcdb5
+size 23880
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6ca842602b0473809416a9cf0d4106a4_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6ca842602b0473809416a9cf0d4106a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c12ed1ad787e2ef9642136f792c0c1d9ab7c6a4f
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6ca842602b0473809416a9cf0d4106a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a00961154bcba98d6cc3337c629f3e98c1211aed5dc9ec71464eaa4e0017a242
+size 99098
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6e0f8561f98e81dc4918793f6a884357_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6e0f8561f98e81dc4918793f6a884357_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bc9c63803ee4a7180a184b5c1d1ebd970c9c57bb
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6e0f8561f98e81dc4918793f6a884357_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:36144bc8b92df39b0183d8bfb4f6d4ab344e68927cc4ba0cfbcb0dd1661aa717
+size 108226
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6ebc3724d8a9c6dac981f189ea2e77dc_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6ebc3724d8a9c6dac981f189ea2e77dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..de4f2fdd87cb053ef39de1a4013f263f1f72aabf
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6ebc3724d8a9c6dac981f189ea2e77dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9f2c4b6dc4e7b6eab6189794bd1b8b8bf79dea713c62ce434ed849735d099279
+size 87254
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6f7323b820d2c28a31e1161ca131cf03_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6f7323b820d2c28a31e1161ca131cf03_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..244f7da554846867826316bb1b0de1516b5a41e5
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/6f7323b820d2c28a31e1161ca131cf03_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b5eb135cecee01994fcebdd54e0685d1ff885fcd0f84f32fa7a6d13bea217403
+size 60668
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/755df4375784e80e5a00ba5b78fa8679_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/755df4375784e80e5a00ba5b78fa8679_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1446f2c6589ae409d0ea03ab0988c0b89313a82c
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/755df4375784e80e5a00ba5b78fa8679_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5e11e036af03717990716437b109eddb8221a04266e53a3078c0577447bd53ac
+size 137827
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3bb98c0efe948ff6b959c66654339c142203ea6d
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e42831afa5b660b6e5910aed99fb1a1ed5d4e38f33aa0eaa1e0dfb854dfe11ab
+size 33734
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/7d1b7ee3543f5a1a9b7ad98572d52f85_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/7d1b7ee3543f5a1a9b7ad98572d52f85_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0ca065321bfdd86e7a018c5e54374f7cda21df34
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/7d1b7ee3543f5a1a9b7ad98572d52f85_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f8c64fe7cbe56dd28c3fcdd73ed0b8bb7911ee42bec7ed6f8016616ce0b2815f
+size 73111
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/7f160d34246308c7a49fa34793b776da_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/7f160d34246308c7a49fa34793b776da_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8b04fd9ee2ca2fabbfd50b316cbbe4530d911c04
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/7f160d34246308c7a49fa34793b776da_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b10c1a2fe93f28a016fc68279d64a41664895949628f1cce68a262f1a8582cb1
+size 13881
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/7fbdef79403f482e82031e3591c98bc2_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/7fbdef79403f482e82031e3591c98bc2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..952dc9a8c1c116dcebaeb551cb47e59c3ce011ae
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/7fbdef79403f482e82031e3591c98bc2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:910c4391fe5b6f7356371af416632a1c8dda427a5768e2fe314d3a22acaa138a
+size 21443
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bbe27bec8ed7f3c09eeec0bc7aec7e86ecc5b001
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:79beec5de383ea12bf174dc83155e289464a8f3494ff94ab32790b246cf1ae90
+size 37358
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/83fd0d406cba6f9c189e77e05859a600_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/83fd0d406cba6f9c189e77e05859a600_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..853ce5c2aa877e07b34ff8bc8998f1e35bd10b0c
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/83fd0d406cba6f9c189e77e05859a600_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4661ae05cac5f22bf28c00a78cf7bcd686b387a6874e4a0ebb90523b4279785a
+size 17352
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/8579e6ff712a88fe7ae237a5ec602f12_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/8579e6ff712a88fe7ae237a5ec602f12_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9731f83130cd993431e80e6f1585db3729896d2e
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/8579e6ff712a88fe7ae237a5ec602f12_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88a63c55982b88b08c70f660e894e71c7d4d7b106b850d83a2fb19f743b945bf
+size 53759
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/87f8b579bc67022e8dd0a0a50585fd4d_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/87f8b579bc67022e8dd0a0a50585fd4d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6b21e179b336742fba38a30b18b99e5e7cee0756
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/87f8b579bc67022e8dd0a0a50585fd4d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6d085a7d22de33990d4d2eaadce988a487651907e316e2cda3cb9cfe9e214f42
+size 135468
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/893d65bf826925a7283359b1672010a0_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/893d65bf826925a7283359b1672010a0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4d4e3c8caee2768bec307988727fc0fc8a278703
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/893d65bf826925a7283359b1672010a0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0e6b4c91fb49a9ed13603725be63a07d4483192a9e741df289eaba627c313870
+size 104940
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/89d5117b5c8c5209f100f1f0bf8ef540_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/89d5117b5c8c5209f100f1f0bf8ef540_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1a4dd9309c41ea9ec3d695dfd931658f18503698
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/89d5117b5c8c5209f100f1f0bf8ef540_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fa7201034ec5f01be9893fd342984c9946ba2c4670842823875addcdf54ab6eb
+size 37391
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/8daeed01030a7b9e2c3fbc068514132f_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/8daeed01030a7b9e2c3fbc068514132f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..195e5af954d18f255cb4c52a0562705fc5691079
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/8daeed01030a7b9e2c3fbc068514132f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:37ce55722761121b8c7d9af832e151e3c47d2e697415a089ff5281b19d41c905
+size 123174
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/8fce89f02626b8a0c50e2245bc3e7ce7_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/8fce89f02626b8a0c50e2245bc3e7ce7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..83f39d8c099b2f472e52f8708d65d348f614eae9
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/8fce89f02626b8a0c50e2245bc3e7ce7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8d2b7db32a77f532330e33e6aa0e9be65bb489b53e7cf682cddc82efe7ad024e
+size 30869
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/92c9263daf7fbd044894e2b273ae21af_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/92c9263daf7fbd044894e2b273ae21af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3d9673577ed5baf20c3f34c3d6e947bae8515617
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/92c9263daf7fbd044894e2b273ae21af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e5dbb5258acec1af3b102b016559bc412a58ca963e4896e780e6ff80503032dd
+size 69869
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/943f54e37bccb82a595569b2a232b9cc_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/943f54e37bccb82a595569b2a232b9cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..60b441f71a81e20f6fd528fb9a4729d185087ca9
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/943f54e37bccb82a595569b2a232b9cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e6d24aac6538675d0758fa31775dcee594113d4eb2783afccbf317cb38e037aa
+size 120570
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dc22b452f12eb83ccacf673aa8bec0975d558f3f
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8835868ec99547ac97eb32b45f6770c930ed03c035a62368933763e9adf2c29c
+size 59423
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/9a14684f8ae1345c6efea6f5994c730c_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/9a14684f8ae1345c6efea6f5994c730c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..24e701db0f2340b859e802ff56799b52b4f82460
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/9a14684f8ae1345c6efea6f5994c730c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fba8339bb57b6dfcdb02de584a373c79c5b207bb34865ad76b2d635fadd396cd
+size 36060
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/9a8f8276c7199f1dd9f3754cf60555c6_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/9a8f8276c7199f1dd9f3754cf60555c6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..637718b3027892d6361395ee127bd9624e54b037
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/9a8f8276c7199f1dd9f3754cf60555c6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6d57d5c33849ee5fb93bf6ce4879db0d3aa908400c238ee9cfa3194e84220e6f
+size 62969
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/9aa5975930cebfd669fe7585394719e0_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/9aa5975930cebfd669fe7585394719e0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f1bcc8754d1f407ac627503defa0d5ea9e84dca3
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/9aa5975930cebfd669fe7585394719e0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7fbffe2dfffda7faa279341007aa8ea7c62b439ce020d62442bc591be6be2bf7
+size 49596
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/9b1ec0090070bdf52ea28763b8d52477_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7b0da97d089791696687d67897651078b092cbba
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/9b1ec0090070bdf52ea28763b8d52477_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a10fbdf6c2637ae2128df0620d8ca4640f88ff69129ac4f090795936b9ae1444
+size 41446
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4c8fc0b65a5544aed3befb935d4fbb98932bea60
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:775b78397ba80c391f1348a4910dac1c182024bd6c570eda05f4c6cb030b95e5
+size 94813
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/a4c80b98452e7949d9f8d969dc9cebf7_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/a4c80b98452e7949d9f8d969dc9cebf7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f1735742ea6ac0b0e5517c225c32c97b20d87d82
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/a4c80b98452e7949d9f8d969dc9cebf7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c16137006cb414c73c9eadf05e41818d1c69c45e78efa6c75434a962c1620ec9
+size 75085
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/a76fa39f5daf6a026e032495262ed0f6_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/a76fa39f5daf6a026e032495262ed0f6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4c06209390e181fec7f5a2020b42560fd31330e2
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/a76fa39f5daf6a026e032495262ed0f6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a7396521e0076acf282f9886bf5d2f08929470f129da7783d3b45d562f81a0f1
+size 29990
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/a78db21022e0687c18d97ed547dd7ecb_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/a78db21022e0687c18d97ed547dd7ecb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d12d52210b0b297402806e3f01a00daebf721da6
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/a78db21022e0687c18d97ed547dd7ecb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:95b5a2cf44c999f010730c14bb089aca2382601919eb9126ee67e9cd9d7d0d16
+size 57331
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/aadbdbdbe20c27e20e40cc56c1b8ee9c_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/aadbdbdbe20c27e20e40cc56c1b8ee9c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4156cd26259b1cc0be3a7b4c89d468ab5b13c12d
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/aadbdbdbe20c27e20e40cc56c1b8ee9c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:745d7e1f6e7f222ae1d5ce755616517e07a20db5852b81725faef90b8efc9550
+size 158337
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/b43ec8e53bbe827c4572d9fd80ebc21a_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/b43ec8e53bbe827c4572d9fd80ebc21a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..feb400afd99406719f72d442f612a23f7f5bfb10
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/b43ec8e53bbe827c4572d9fd80ebc21a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:41d2319c303cc674b553ec9c88755628e3b69d3710dd524f1e20dd8525a92301
+size 112994
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/b54b769d67164910c7c5b2a0ea74257b_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/b54b769d67164910c7c5b2a0ea74257b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a39a80c8b9de3bd3ad92d737b3c4b9bf1c573fdd
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/b54b769d67164910c7c5b2a0ea74257b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4c54725dc938acd9c1e0d56ed926c0732405e16cd6aa9da293ca6d3cf9444c01
+size 202651
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/b55cd9b5721bd8aabc979c85316924e4_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/b55cd9b5721bd8aabc979c85316924e4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2802d0c67fca078309cecca81a072203aa1a9944
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/b55cd9b5721bd8aabc979c85316924e4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:19d553b3bcdf47c68f6b9d6093a38d12dc1a8f9e348e92b9ec3d283df0d928fa
+size 57612
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/b904ac2472cab80892d1e783e6230d6e_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/b904ac2472cab80892d1e783e6230d6e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..155a4a17b6e07d7d653d990756d40277f095bcdd
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/b904ac2472cab80892d1e783e6230d6e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:207a3b5008a00d40408f2f004e2e3f622ff3e1b2be668df163c1d2346a7dfcf5
+size 43040
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/bae60391325927710f2cb0599f4ce1d5_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/bae60391325927710f2cb0599f4ce1d5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..39f1a26ae55bb993ec1ed985a2268356b96a96d1
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/bae60391325927710f2cb0599f4ce1d5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:71114e1b1d890dee1e2e25788a190d8fc3f9c886106b775dc590c7d73f7bdefa
+size 78078
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/bb100d4069b5ff6f9ee2e366ca169c24_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/bb100d4069b5ff6f9ee2e366ca169c24_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..641c64a05f168bf0e68f9e92f5eca2d631f7a897
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/bb100d4069b5ff6f9ee2e366ca169c24_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7f32d974e1e165e68171182a8033ea067d9150b8e181bedf881ad7bf5752d50d
+size 43331
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/bc38deb2fec0ea26c5b2e0ed8884d852_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/bc38deb2fec0ea26c5b2e0ed8884d852_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0a5d541cbe7603829f77e3481e7ba01bbedd1f25
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/bc38deb2fec0ea26c5b2e0ed8884d852_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cee9d92be16b9628a785ed69f5aeb67576f787c87a2cd4b8bfd75098ef003c3c
+size 121421
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/beefc2239bc009e7b97963ac4f166db1_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/beefc2239bc009e7b97963ac4f166db1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c5fa2cfbbd5601dfc534a1be08e10c5162e63be0
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/beefc2239bc009e7b97963ac4f166db1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:71e8ace9426a2b746e4eee5cab4c2a39b64ae67137a5a5f47a95c2375607856e
+size 37600
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/c6240283e2f65a6d02db47fa4ab0c518_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/c6240283e2f65a6d02db47fa4ab0c518_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8ee478f81624355452b73c583742bd4efb5ab18b
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/c6240283e2f65a6d02db47fa4ab0c518_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:db4e09139ad2d6752c19215c6e4d3c6e2a869aec06d1ccf2779ecdf991edea3c
+size 63759
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/c916a9fb4d2c440522379dedf3f76119_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/c916a9fb4d2c440522379dedf3f76119_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8dd8c0b784cb271f21c0bcb916a61ddab8dc619b
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/c916a9fb4d2c440522379dedf3f76119_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fff6ad415a9efecd8ed24628c1e5fc4df1ce4ac1559956ce3232607ed64ef0c4
+size 66896
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cb53dba6052b59d69ecc7e8017b70def_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cb53dba6052b59d69ecc7e8017b70def_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ec334a7c7febeb238beed011208ec3cb12d404a3
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cb53dba6052b59d69ecc7e8017b70def_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a06f19fa665c74ef2b14d0ba9b36cc016a5294cbc0ba27d0eb35f639ac18983e
+size 68194
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cb86a44ccb06c552d4c8c1d8374aaeae_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cb86a44ccb06c552d4c8c1d8374aaeae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f76fa9e53f2444b2e9963d2f6ccdb33d3e2f2031
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cb86a44ccb06c552d4c8c1d8374aaeae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:32e34d0ff089e9f8a3406c75684f47bdefdf504b6b318dc20c0473ea99207659
+size 82706
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cc91bf9aed46f8b219ebceaee276d195_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cc91bf9aed46f8b219ebceaee276d195_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4047ca5b3e970565b3d09e4ff42614ae56167f2e
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cc91bf9aed46f8b219ebceaee276d195_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:65ef7bb3673b714e71390afa08eef8a4206d84163707411d69212e6f3a6e3253
+size 57586
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cdc2deee0f3dc8e23ea41a27e91d2bb5_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cdc2deee0f3dc8e23ea41a27e91d2bb5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5fe49d2e25e112fd0b94265a74c47095ebee75f9
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cdc2deee0f3dc8e23ea41a27e91d2bb5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0a38531d9a85d9ca11e1d86b3ea5a2091e1cbdbd29f894270365c59f0e81af85
+size 101158
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cf03eff1218a8cc1be6b05de892162de_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cf03eff1218a8cc1be6b05de892162de_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..57fe69cd470b10f2a3875200369e5723cb37a680
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cf03eff1218a8cc1be6b05de892162de_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b1580edbfbf4d4c3a3ce90f64ccb6051e27775919c8a56f1544540964ec7f3d
+size 156263
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cf75ef88724c24497dfe437c81b74325_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cf75ef88724c24497dfe437c81b74325_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7d7a309fb4ce84cf71010a98b3bfe78d45c986cc
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cf75ef88724c24497dfe437c81b74325_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:070095c5ed90d6f216670264abe5edd24a18b10112d5ec900a5de4a69792ccfc
+size 10149
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cfb616f789aa01c087849ad7701e64d7_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cfb616f789aa01c087849ad7701e64d7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9029e7554ea2f6f3491e053120836c700ca085c2
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cfb616f789aa01c087849ad7701e64d7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cf2145d33e9dcfd0f1d0fed23d5fa04b2e16c0d50993f08f1dcc0e58175367c2
+size 66221
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cfd911568094b540490a86efe5c0ead6_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cfd911568094b540490a86efe5c0ead6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..39e4f6020395644b318641e9bb916e1e5ed89a37
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/cfd911568094b540490a86efe5c0ead6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4833210cb82f378e7e0e9ad6a4bb9a0ae8f72c167590728b19ba834858f91c9a
+size 60562
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/d13d29ff2ebef1a20c60c05fc4bca45b_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/d13d29ff2ebef1a20c60c05fc4bca45b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7de6fe96fee9b8f22dd73e5ad07e8fc612526197
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/d13d29ff2ebef1a20c60c05fc4bca45b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3a60576cb4a2b1be3d9400aafd3497d6e6921e3c1e0eff483bdfb6c9b148f171
+size 45508
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/d4369a53cb56f10f74fbed39280e9245_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/d4369a53cb56f10f74fbed39280e9245_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8475a68c904658db5bb6f90bca5eff8058b743a3
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/d4369a53cb56f10f74fbed39280e9245_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:23fa100961795bcf78425e2a8b9abf0b2fa7a785372f4b852a13dd0f01f2fe98
+size 32898
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/d7896dd2d38adf224c3b76cd22d29c10_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/d7896dd2d38adf224c3b76cd22d29c10_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f69fa4cc8cbb6114325d354902ed8aef4797a014
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/d7896dd2d38adf224c3b76cd22d29c10_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1b33a2eba1e1eedceca0f9689c3d695c3530a3bbfb4b4fe259b2d274c745ee65
+size 52927
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/dbe4ffa9778863279b48b56fe097cd23_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/dbe4ffa9778863279b48b56fe097cd23_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c0519eceaa21ffffd885650adb1b7a926e5c639c
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/dbe4ffa9778863279b48b56fe097cd23_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e18767774bf76a13fbd06824cfad0c2121828f55ee235344787dbd88f38aabf3
+size 56703
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/dbe8aad2b5ea5fdf87cc3a21e496e1b9_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/dbe8aad2b5ea5fdf87cc3a21e496e1b9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..71c438ce3fb4c2a56ad10b1c7113e27f161ca034
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/dbe8aad2b5ea5fdf87cc3a21e496e1b9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0489d01357402afa48da81e79d96514260d9ad004f343500d4b00dd5b9b46620
+size 64794
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/dbf5c0f3c7836f717d9fe62c6c40b280_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/dbf5c0f3c7836f717d9fe62c6c40b280_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a93ffce80d97cd674b0dc624de5b18a8c844ce3f
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/dbf5c0f3c7836f717d9fe62c6c40b280_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b4d6520465695acfb88b2c8b37b6e0a08378cbe1de194582ea0039be4bd77dd4
+size 150209
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/dd6c544ab685b25dd17f59456efcfbfc_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/dd6c544ab685b25dd17f59456efcfbfc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..03cbf439e62c85df28f24e845d30731c560c561d
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/dd6c544ab685b25dd17f59456efcfbfc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b3c2a8507ef723e22462313a45418b1f6527e6cf905041ce9e0a0a791e26e286
+size 35449
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/decc27040435a188fd6734a9002e5312_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/decc27040435a188fd6734a9002e5312_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..65f5edfc454b5b8ddf07afae78e69890bac6e767
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/decc27040435a188fd6734a9002e5312_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8f4c0d9803ba734e62d7331cd1fd8b8a12be4acc6c8d55bd12a387625d31290b
+size 101857
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/e01c6273c4177746475715ee9c17a882_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/e01c6273c4177746475715ee9c17a882_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7c5e8d0190cc939a488c8b5911e88d15ba87e942
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/e01c6273c4177746475715ee9c17a882_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7717a309671669058ddbe184963f35d752ae5dbccc3996db1b0de333b3939796
+size 62157
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/e151d3468319b81f042ca232c4d82e4b_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/e151d3468319b81f042ca232c4d82e4b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d22c6fda3473d2560dca2a5a793c1043cc68bad8
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/e151d3468319b81f042ca232c4d82e4b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f827eb72639bcf3d585906d92c928b903017275d9aeb45d9909e2c2e9167c661
+size 12163
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/e2245b4865907ad1259fd155f4beb6cf_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/e2245b4865907ad1259fd155f4beb6cf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f0336721a0f27a5fadb5f6e871efe179f9a43db8
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/e2245b4865907ad1259fd155f4beb6cf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:686f1aa8f9a71acd15e11ee2d5beb87da6d1b51ca5c8b391aff10b322bdb2ba0
+size 161258
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/e3e0f694ce5b09acae963f8a5fdb1cc0_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/e3e0f694ce5b09acae963f8a5fdb1cc0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..26eb546dff6ff51dff4aa92f2e1ececbee4ab5ed
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/e3e0f694ce5b09acae963f8a5fdb1cc0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d4cea0d32a2d3bef49fa00bbdfddeada911a71459703cd68d80ab602d5f50e9d
+size 38623
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1d5c8712bcca63d324d7d4b467cfb8cce3f9e641
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1ae1428027c2a8cc64e9a5708cd7afef979b4c4d598dee86e852a7484eed5630
+size 37257
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/e5eedb1e90a22814f090917b3411be8f_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/e5eedb1e90a22814f090917b3411be8f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e766de4480b7f93c2520cc7c4176c116be9e2d8b
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/e5eedb1e90a22814f090917b3411be8f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:82abaa5ceb05989e847443bd9a8037580f98ecc51ac8b0e6e49644cf9021ad2c
+size 77303
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/ea161d4dcfcbbecb95428d543a19e0dc_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/ea161d4dcfcbbecb95428d543a19e0dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b9b5cde0ba93aed582f8c313c0710b2a45f6277b
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/ea161d4dcfcbbecb95428d543a19e0dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8150eaac3df4ce9f274186a65704939bc7f0512e4444c6f438fb2315be63c26f
+size 72323
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/ecae674475cecdd0962200a5d1e2591e_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/ecae674475cecdd0962200a5d1e2591e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3b815d5096d2224840a7578753834252be1eb111
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/ecae674475cecdd0962200a5d1e2591e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:73fcce02d9d9e5dea8ca20cab4cf8c02f2e04fa42ce0f984cd83773327492d0b
+size 39182
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/f3c73e8e478b8b2d9f6a96a970040556_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/f3c73e8e478b8b2d9f6a96a970040556_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c4d107c5d1d0d1917d2dd1c766a2a198029c45a3
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/f3c73e8e478b8b2d9f6a96a970040556_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0dd26e573b40c1c667cdca617147acb76b8675efa35460a40c6e5960dd55ee31
+size 164034
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/f4aaee6522d9ab40472939a4a178e5a3_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/f4aaee6522d9ab40472939a4a178e5a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cdec097e2a4cbc5be5a585f8dd1f99a24fbc0f4d
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/f4aaee6522d9ab40472939a4a178e5a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e5c6114262eec0eb0b2f91546744c4bd1d4a5f584d91feb957d532566d59856
+size 119455
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..77fe626717367c46c5a134fd275236c7743ae1cb
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1096c07112838fc6c1345f116fda9de0eff50ac205dcc17c4d7f258811165029
+size 33375
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/f9802d8871078af5421372727c628e2a_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/f9802d8871078af5421372727c628e2a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b0d9a9bf09b8dbc498bee902358a3008e9f09b0b
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/f9802d8871078af5421372727c628e2a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e688fbb9e7d6df973862bd5a89959686850226155838cc54c0871a7121029320
+size 129678
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..65604ba0a620f820c1adb220b0e4f0efc9983eab
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e1d73b0d2aa88459862ab01c8951d57c9ae3f183dd53157329bdb875f6f93d40
+size 16558
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/ffb6acd27b8e3a54392840948a75869f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cf999210754c868ab4fec322722fb66985788165
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/ffb6acd27b8e3a54392840948a75869f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e159fd792a6cf81dd3faa182fef06feec5600f357c8617e71e2c842bb5780135
+size 58355
diff --git a/marked/Q/T-REC-Q.2931F-200012-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2931F-200012-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..104a57fbd03964ffd2520508b2be42e03343d20f
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931F-200012-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2468dfa77e8d32611a5fe8a2ebb904676994eeb54463226fd865698560c960c
+size 8232
diff --git a/marked/Q/T-REC-Q.2955.1-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2955.1-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a7da83ecb82b51a4cef7694858eef2c35f1986ff
--- /dev/null
+++ b/marked/Q/T-REC-Q.2955.1-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d77a478c5b78d330a2a6abbd32e7d0ac053d8b9c1ffe8a96476214afa6ddf7ae
+size 8196
diff --git a/marked/Q/T-REC-Q.2955.1-199706-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/Q/T-REC-Q.2955.1-199706-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0234b8ad0bb4171e60cd5a89a5c95644d3621f34
--- /dev/null
+++ b/marked/Q/T-REC-Q.2955.1-199706-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a05b75b82ceeeece75b4b65440dd337167f5801668722d034a31387ca354ba03
+size 116478
diff --git a/marked/Q/T-REC-Q.2955.1-199706-I_PDF-E/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/marked/Q/T-REC-Q.2955.1-199706-I_PDF-E/e9d825d87c5f85c8dba0664eace96ef4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f658d4b9ed3ab0bf636c4fc70930055f3616dcec
--- /dev/null
+++ b/marked/Q/T-REC-Q.2955.1-199706-I_PDF-E/e9d825d87c5f85c8dba0664eace96ef4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:571f967967582c838fbcfac5f3fff3cbff3a73deb945d2cf774bdef62a80a33b
+size 33212
diff --git a/marked/Q/T-REC-Q.2961.2-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2961.2-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8c1dfa8ee22ad063471e82648f8515dd37ce784d
--- /dev/null
+++ b/marked/Q/T-REC-Q.2961.2-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1699fae88e3fee843d3e7c6630ffd354a895d007811a17ddd3575320a6443bfe
+size 8191
diff --git a/marked/Q/T-REC-Q.2961.2-199706-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2961.2-199706-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..65307b66bc3d618e72fc75155a8fef2e4106c61f
--- /dev/null
+++ b/marked/Q/T-REC-Q.2961.2-199706-I_PDF-E/raw.md
@@ -0,0 +1,534 @@
+
+
+
+
+ITU logo: A globe with the letters ITU and a lightning bolt.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**Q.2961.2**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(06/97)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Broadband ISDN – B-ISDN application protocols for
+access signalling
+
+---
+
+**Digital subscriber signalling system No. 2 –
+Additional traffic parameters: Support of ATM
+transfer capability in the broadband bearer
+capability information element**
+
+ITU-T Recommendation Q.2961.2
+
+(Previously CCITT Recommendation)
+
+---
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## **SWITCHING AND SIGNALLING**
+
+| | |
+|--------------------------------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| General aspects | Q.2000–Q.2099 |
+| Signalling ATM adaptation layer (SAAL) | Q.2100–Q.2199 |
+| Signalling network protocols | Q.2200–Q.2299 |
+| Common aspects of B-ISDN application protocols for access signalling and network signalling and interworking | Q.2600–Q.2699 |
+| B-ISDN application protocols for the network signalling | Q.2700–Q.2899 |
+| B-ISDN application protocols for access signalling | Q.2900–Q.2999 |
+
+For further details, please refer to ITU-T List of Recommendations.
+
+## **ITU-T RECOMMENDATION Q.2961.2**
+
+## **DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 2 – ADDITIONAL TRAFFIC PARAMETERS: SUPPORT OF ATM TRANSFER CAPABILITY IN THE BROADBAND BEARER CAPABILITY INFORMATION ELEMENT**
+
+## **Summary**
+
+This Recommendation is part of the DSS 2 family of Recommendations. It specifies the revision of the Broadband bearer capability information element coding from that which was specified in the first edition of Recommendation Q.2931 (1995) in order to enable the identification of the ATM transfer capability as defined in the second edition of Recommendation I.371 (1996). This Recommendation is designed, in addition, to be compatible with implementations conforming to the first edition of ITU-T Recommendation I.371 (1993) and Recommendation Q.2931 (1995).
+
+## **Source**
+
+ITU-T Recommendation Q.2961.2 was prepared by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 5th June 1997.
+
+## FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
+
+The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+### NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, the ITU had/had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 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 |
+|-------------------------------------------------------------------------------------------------------------------------|------|
+| 2.1 Scope..... | 1 |
+| 2.2 References..... | 1 |
+| 2.3 Definitions ..... | 1 |
+| 2.4 Abbreviations..... | 2 |
+| 2.5 Description..... | 2 |
+| 2.6 Coding requirements..... | 2 |
+| 2.6.1 Broadband bearer capability ..... | 2 |
+| Annex A – Valid combinations of bearer class, broadband transfer capability and ATM traffic descriptor parameters ..... | 6 |
+| Appendix I – Guidelines on meaning of bearer class field ..... | 11 |
+| I.1 Bearer class ..... | 11 |
+| I.1.1 BCOB-A ..... | 11 |
+| I.1.2 BCOB-C ..... | 11 |
+| I.1.3 BCOB-X ..... | 11 |
+| I.1.4 FR ..... | 11 |
+| Appendix II – Guidelines on use of BTC field ..... | 11 |
+| II.1 Guidelines on the use of BTC value of 7 ..... | 12 |
+| II.2 Guidelines on the use of BTC value of 11 ..... | 12 |
+| II.3 Guidelines on the use of BTC value of 19 ..... | 12 |
+
+# Introduction
+
+This Recommendation has been prepared to provide information on the use of the Broadband bearer capability that is consistent with the second edition of Recommendation I.371.
+
+This Recommendation is issued in conjunction with an addendum to Recommendation Q.2931. This Recommendation is designed in addition to be compatible with implementations conforming to the first edition of Recommendation I.371 (1993) and Recommendation Q.2931 (1995).
+
+Within this Recommendation, the changes from Recommendation Q.2931 (1995) are as follows:
+
+- Octet 5a of the Broadband bearer capability information element was restructured to support the ATM Transfer Capabilities (ATC) specified in the second edition of Recommendation I.371. This restructuring is backward compatible with the first edition of Recommendation Q.2931 (i.e. values of Octet 5a defined in the first edition of Recommendation Q.2931 still have the same meaning). These values may be either those used on transmission and reception, those not generated by terminal equipment complying with this Recommendation, or those that are reserved.
+- A new octet, Octet 7, of the Broadband bearer capability information element specified in Recommendation Q.2933, is shown.
+
+## Recommendation Q.2961.2
+
+# **DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 2 – ADDITIONAL TRAFFIC PARAMETERS SUPPORT OF ATM TRANSFER CAPABILITY IN THE BROADBAND BEARER CAPABILITY INFORMATION ELEMENT**
+
+(Geneva, 1997)
+
+## 2.1 Scope
+
+Recommendation Q.2961 covers the support of additional traffic parameters for the Broadband Integrated Services Digital Network (B-ISDN) at the $T_B$ reference point or coincident $S_B$ and $T_B$ reference point as defined in Recommendation I.413 [1] by means of the Digital Subscriber Signalling System No. 2 (DSS 2). This Recommendation defines DSS 2 protocol formats that support the indication of ATM traffic-related capabilities.
+
+This Recommendation is part of the DSS 2 family of ITU-T Recommendations. It specifies the revised coding of the Q.2931 [2] Broadband bearer capability information element specifically to enable the identification of the ATM transfer capability (see Recommendation I.371 [4]).
+
+## 2.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 I.413 (1993), *B-ISDN user-network interface*.
+- [2] ITU-T Recommendation Q.2931 (1995) (amended in 1997), *Digital Subscriber Signalling System No. 2 – User-Network Interface (UNI) layer 3 specification for basic call/connection control*.
+- [3] ITU-T Recommendation Q.2961.1 (1995), *Digital Subscriber Signalling System No. 2 – Additional traffic parameters: Additional signalling capabilities to support traffic parameters for the tagging option and the sustainable cell rate parameter set*.
+- [4] ITU-T Recommendation I.371 (1996), *Traffic control and congestion control in B-ISDN*.
+- [5] ITU-T Recommendation I.356 (1996), *B-ISDN ATM layer cell transfer performance*.
+- [6] ITU-T Recommendation Q.2933 (1996), *Digital Subscriber Signalling System No. 2 (DSS 2) – Signalling specification for frame relay service*.
+
+## 2.3 Definitions
+
+The definitions of Annex J/Q.2931 [2] apply. In addition, this Recommendation uses the following terms as defined in Recommendation I.371 [4]:
+
+- Traffic parameter, ATM transfer capability, Deterministic Bit Rate (DBR), Statistical Bit Rate (SBR), SBR configuration 1, SBR configuration 2, SBR configuration 3.
+
+## **2.4 Abbreviations**
+
+The abbreviations of Annex J/Q.2931 [2] apply. For the purpose of this Recommendation, the following abbreviations apply in addition:
+
+- ATC ATM Transfer Capability
+- BTC Broadband Transfer Capability
+- DBR Deterministic Bit Rate ATM transfer capability
+- FR Frame relay
+- SBR Statistical Bit Rate ATM transfer capability
+- SBR1 SBR configuration 1 ATM transfer capability
+- SBR2 SBR configuration 2 ATM transfer capability
+- SBR3 SBR configuration 3 ATM transfer capability
+
+## **2.5 Description**
+
+This Recommendation specifies the revision of the broadband bearer capability information element coding as specified by Recommendation Q.2931 [2] in order to enable the identification of the ATM transfer capability (see Recommendation I.371 [4]).
+
+## **2.6 Coding requirements**
+
+### **2.6.1 Broadband bearer capability**
+
+The purpose of the Broadband bearer capability information element is to indicate a requested broadband connection-oriented bearer service to be provided by the network. It contains only information that may be used by the network. The use of the Broadband bearer capability information element in relation to compatibility checking is described in Annex B/Q.2931 [2].
+
+No default broadband bearer capability may be assumed by the absence of this information element.
+
+The Broadband bearer capability information element will be examined by both the network and the customer equipment.
+
+The Broadband bearer capability information element is coded as shown in Figure 1 and Table 1. The maximum length of this information element is 8 octets.
+
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | | |
+|------------------------------------------------------|-------------------------------------|-------|--------------------------------------|------|-------------------------------------------|---|---|-----------|--|--|--|
+| Broadband bearer capability | | | | | | | | | | | |
+| 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | | | |
+| Information element identifier | | | | | | | | | | | |
+| 1
ext. | Coding
standard | | IE Instruction Field | | | | | 2 | | | |
+| | | | Flag | Res. | IE Action Indicator | | | | | | |
+| Length of the
Broadband bearer capability content | | | | | | | | 3 | | | |
+| | | | | | | | | 4 | | | |
+| 0/1
ext. | 0 | 0 | Bearer class | | | | | 5 | | | |
+| | Spare | | | | | | | | | | |
+| 1
ext. | Broadband Transfer Capability (BTC) | | | | | | | 5a* | | | |
+| 1
ext. | Susceptibility
to clipping | 0 | 0 | 0 | User plane
connection
configuration | | | 6 | | | |
+| | | Spare | | | | | | | | | |
+| 1
ext. | 0 | 1 | User information
layer 2 protocol | | | | | 7* (Note) | | | |
+| | Layer id | | | | | | | | | | |
+
+NOTE – This octet shall be included when interworking with other networks providing frame relay data transfer service is required. Otherwise it is optional.
+
+**Figure 1/Q.2961.2 – Broadband bearer capability information element**
+
+**Table 1/Q.2961.2 – Broadband bearer capability information element**
+
+| | | |
+|-----------------------------------------------------------|-------------------------------|----------------------------------------------------------------|
+| – Bearer class (octet 5) | | |
+| Bits | | |
+| 5 4 3 2 1 | | |
+| 0 0 0 0 1 | BCOB-A | |
+| 0 0 0 1 1 | BCOB-C | |
+| 0 0 1 0 1 | frame relaying bearer service | |
+| 1 0 0 0 0 | BCOB-X | |
+| All other values are reserved. | | |
+| – Broadband transfer capability (octet 5a) | | |
+| Values used on transmission and reception (Note 1) | | |
+| – Broadband transfer capability (octet 5a) | | |
+| Bits | | |
+| 7 6 5 4 3 2 1 | | |
+| 0 0 0 0 1 0 1 | BTC5, | constant bit rate with end-to-end timing required (Note 2) |
+| 0 0 0 0 1 1 1 | DBR | (Note 3) |
+| 0 0 0 1 0 0 1 | BTC9, | variable bit rate with end-to-end timing required (Note 4) |
+| 0 0 0 1 0 1 0 | BTC10, | variable bit rate with end-to-end timing not required (Note 5) |
+| 0 0 0 1 0 1 1 | SBR1 | (Note 6) with end-to-end timing not required |
+| 0 0 1 0 0 1 1 | SBR1 | (Note 6) with end-to-end timing required |
+| Additional values recognized on reception (Note 7) | | |
+| – Broadband transfer capability (octet 5a) | | |
+| Bits | | |
+| 7 6 5 4 3 2 1 | | |
+| 0 0 0 0 0 0 0 | BTC10, | variable bit rate with end-to-end timing not required |
+| 0 0 0 0 0 0 1 | BTC9, | variable bit rate with end-to-end timing required |
+| 0 0 0 0 0 1 0 | BTC10, | variable bit rate with end-to-end timing not required |
+| 0 0 0 0 1 0 0 | BTC5, | constant bit rate with end-to-end timing required |
+| 0 0 0 0 1 1 0 | BTC5, | constant bit rate with end-to-end timing required |
+| 0 0 0 1 0 0 0 | BTC10, | variable bit rate with end-to-end timing not required |
+| Additional reserved values (Note 8) | | |
+| – Broadband transfer capability (octet 5a) | | |
+| Bits | | |
+| 7 6 5 4 3 2 1 | | |
+| x x 0 0 0 0 0 | | reserved for backward compatibility |
+| x x 0 0 0 0 1 | | reserved for backward compatibility |
+| x x 0 0 0 1 0 | | reserved for backward compatibility |
+| x x 0 0 1 0 0 | | reserved for backward compatibility |
+| x x 0 0 1 0 1 | | reserved for backward compatibility |
+| x x 0 0 1 1 0 | | reserved for backward compatibility |
+| x x 0 1 0 0 0 | | reserved for backward compatibility |
+| x x 0 1 0 0 1 | | reserved for backward compatibility |
+| x x 0 1 0 1 0 | | reserved for backward compatibility |
+| where: | | |
+| x x = "0 1", "1 0", or "1 1" | | |
+| All other values are reserved. | | |
+
+**Table 1/Q.2961.2 – Broadband bearer capability information element (concluded)**
+
+#### **Notes relative to Table 1:**
+
+NOTE 1 – The valid combinations of the BTC field values defined in this Recommendation and the values of the bearer class field are specified in Annex A.
+
+NOTE 2 – This codepoint is defined to promote backward compatibility with the first edition of Recommendation Q.2931 (1995). When the bearer class is coded "BCOB-A", this octet shall only be present if the BTC field has a coding other than "constant bit rate with end-to-end timing required".
+
+NOTE 3 – DBR is specified in Recommendation I.371 [3].
+
+NOTE 4 – This codepoint is defined to promote backward compatibility with the first edition of Recommendation Q.2931 (1995).
+
+NOTE 5 – This codepoint is defined to promote backward compatibility with the first edition of Recommendation Q.2931 (1995). When the bearer class is coded "BCOB-C", this octet shall only present if the BTC field has a coding other than "variable bit rate with end-to-end timing not required".
+
+NOTE 6 – SBR1 is specified in Recommendation I.371 [4].
+
+NOTE 7 – In order to be backward compatible with the first edition of Recommendation Q.2931 (1995) and with Recommendation Q.2933 [6], these codepoints shall be recognized in combination with a bearer class field coding of "BCOB-X" or "FR". At the SB reference point or coincident SB/TB reference point, a user compliant to this Recommendation shall not include these values in a transmitted SETUP message. A network compliant to this Recommendation shall relay these values.
+
+NOTE 8 – These values are reserved to promote backward compatibility with the first edition of Recommendation Q.2931 (1995) (i.e. the two bits marked xx are spare bits in the first edition of Recommendation Q.2931 and would accordingly be ignored by such equipment) and shall not be used.
+
+#### – Susceptibility to clipping (octet 6)
+
+Bits
+
+7 6
+
+0 0 not susceptible to clipping
+
+0 1 susceptible to clipping
+
+All other values are reserved.
+
+#### – User plane connection configuration (octet 6)
+
+Bits
+
+2 1
+
+0 0 point-to-point
+
+0 1 point-to-multipoint (Note 9)
+
+All other values are reserved.
+
+NOTE 9 – Procedures for point-to-multipoint connections are optional. However, the support of this codepoint may allow a user to participate via a point-to-point connection segment in a point-to-multipoint connection (e.g. when a user, implementing Release 1 procedures, receives a SETUP message with the user plane connection configuration coding set to "point-to-multipoint", it shall treat it as if the coding were "point-to-point". This will allow the user to be a "leaf" of a point-to-multipoint connection).
+
+#### – User information layer 2 protocol (octet 7)
+
+Bits
+
+5 4 3 2 1
+
+0 1 1 1 1 Core aspects of Annex A/Q.922
+
+## ANNEX A
+
+## **Valid combinations of bearer class, broadband transfer capability and ATM traffic descriptor parameters**
+
+The parameters specified in the Broadband bearer capability information element, and the ATM traffic descriptor information element of the SETUP message shall be consistent. Table A.1 shows the valid combinations of the bearer class, BTC, and ATM traffic descriptor parameters.
+
+NOTE 1 – The BTC values considered in Table A.1 are the ones specified in this Recommendation. This does not preclude other valid combinations to be defined in the future when new specified BTC values are specified (e.g. for Available bit rate [4], ATM block transfer [4]).
+
+If a SETUP message is received with a Broadband bearer capability information element containing any other combination of values in Octet 5 and Octet 5a than those specified in Table A.1, a RELEASE COMPLETE message shall be returned with cause #65, "Bearer capability not supported".
+
+If the combination of Traffic parameters, excluding the tagging field, in a SETUP message is not a valid combination specified in Table A.1 for the received values of Octet 5 and Octet 5a in the Broadband bearer capability information element, it shall be considered an unsupported combination of traffic parameters and a RELEASE COMPLETE message shall be returned with cause #73, "Unsupported combination of traffic parameters".
+
+Table A.1 identifies the ATM transfer capability requested for the given direction of the connection. The implicitly requested QOS row in Table A.1 identifies the QOS requested for the given direction of the connection when the QOS Class is 0. In addition, Table A.1 identifies the Recommendation I.371 [4] ATM transfer capability that supports the requested ATM transfer capability and the Recommendation I.356 [5] QOS class that supports the implicitly requested QOS.
+
+NOTE 2 – Recommendation I.371 [4] constrains the ATM transfer capability to be the same for both direction of a connection.
+
+NOTE 3 – There is not a one-to-one correspondence between the codepoints of the BTC field and the ATM Transfer Capability (ATC) defined in Recommendation I.371 [4]. This is in part due to the need to be backward compatible with the first edition of Recommendation Q.2931 (1995) and also due to the implicit association of end-to-end timing requirements for some of the BTC codepoints.
+
+**Table A.1/Q.2961.2 (Part 1 of 3) – Valid combinations of traffic-related parameters in the SETUP message**
+
+| | | | | | | | | |
+|----------------------------------------------------------------------|---------|---------------|---------|---------|---------------------|---------|-----------|---------|
+| Broadband bearer capability | | | | | | | | |
+| Bearer class | A | A | A | C | C | C | C | C |
+| BTC (value) (Note 1) | absent | absent | 7 | absent | absent | absent | absent | 11 |
+| Traffic descriptor for a given direction | | | | | | | | |
+| PCR (CLP = 0) | | S | | | S | | | |
+| PCR (CLP = 0 + 1) | S | S | S | S | S | S | S | S |
+| {SCR, MBS} (CLP = 0) | | | | | | | S | |
+| {SCR, MBS} (CLP = 0 + 1) | | | | | | S | | S |
+| Tagging (Note 13) | N | Y/N | N | N | Y/N | N | Y/N | N |
+| End-to-end timing required | Y | Y | Y | N | N | N | N | N |
+| For the given direction: | | | | | | | | |
+| Requested ATC [4] | Note 2 | Note 2 | DBR | Note 2 | SBR2/SBR3
Note 6 | Note 7 | SBR2/SBR3 | SBR1 |
+| Implicitly requested QOS
when the QOS class is 0 | Note 3 | Note 3 | Class 1 | Note 5 | Class 3 | Note 5 | Class 3 | Class 2 |
+| For the given direction: | | | | | | | | |
+| I.371 [4] ATC that supports
the requested ATC | DBR | DBR
Note 4 | DBR | DBR | SBR2/SBR3
Note 6 | SBR1 | SBR2/SBR3 | SBR1 |
+| I.356 [5] QOS class that
supports the implicitly
requested QOS | Class 1 | Class 1 | Class 1 | Class 2 | Class 3 | Class 2 | Class 3 | Class 2 |
+| | Note 11 | Note 11 | Note 12 | Note 11 | Note 11 | Note 11 | Note 11 | Note 12 |
+
+**Table A.1/Q.2961.2 (Part 2 of 3) – Valid combinations of traffic-related parameters in the SETUP message**
+
+| | | | | | | | | |
+|----------------------------------------------------------------|---------|------------|---------|-----------------------|-----------------------|-----------------------|-----------------------|---------|
+| Broadband bearer capability | | | | | | | | |
+| Bearer class | C | C | C | X or FR | X or FR | X or FR | X or FR | X or FR |
+| BTC (value) (Note 1) | 19 | 9 | 9 | absent, 0, 2, 8 or 10 | absent, 0, 2, 8 or 10 | absent, 0, 2, 8 or 10 | absent, 0, 2, 8 or 10 | 7 |
+| Traffic descriptor for a given direction | | | | | | | | |
+| PCR (CLP = 0) | | | | | S | | | |
+| PCR (CLP = 0 + 1) | S | S | S | S | S | S | S | S |
+| {SCR , MBS} (CLP = 0) | | S | | | | | S | |
+| {SCR , MBS} (CLP = 0 + 1) | S | | S | | | S | | |
+| Tagging (Note 13) | N | Y/N | N | N | Y/N | N | Y/N | N |
+| End-to-end timing required | Y | Y | Y | N | N | N | N | Y |
+| For the given direction: | | | | | | | | |
+| Requested ATC [4] | SBR1 | SBR2/SB R3 | Note 7 | Note 2 | SBR2/SBR3
Note 6 | Note 7 | SBR2/SBR3 | DBR |
+| Implicitly requested QOS when the QOS class is 0 | Note 10 | Note 8 | Note 8 | Note 5 | Class 3 | Note 5 | Class 3 | Class 1 |
+| For the given direction: | | | | | | | | |
+| I.371 [4] ATC that supports the requested ATC | SBR1 | Note 9 | SBR1 | DBR | SBR2/SBR3
Note 6 | SBR1 | SBR2/SBR3 | DBR |
+| I.356 [5] QOS class that supports the implicitly requested QOS | Class 1 | | Class 1 | Class 2 | Class 3 | Class 2 | Class 3 | Class 1 |
+| | Note 12 | | | Note 11 | Note 11 | Note 11 | Note 11 | Note 12 |
+
+**Table A.1/Q.2961.2 (Part 3 of 3) – Valid combinations of traffic-related parameters in the SETUP message**
+
+| | | | | | | | | |
+|----------------------------------------------------------------------|---------|---------|-----------|---------------|---------|---------------------|---------|-----------|
+| Broadband bearer capability | | | | | | | | |
+| Bearer class | X or FR | X or FR | X or FR | X or FR | X or FR | X or FR | X or FR | X or FR |
+| BTC (value) (Note 1) | 11 | 19 | 4, 5 or 6 | 4, 5 or 6 | 1 or 9 | 1 or 9 | 1 or 9 | 1 or 9 |
+| Traffic descriptor for a given direction | | | | | | | | |
+| PCR (CLP = 0) | | | | S | | S | | |
+| PCR (CLP = 0 + 1) | S | S | S | S | S | S | S | S |
+| {SCR , MBS} (CLP = 0) | | | | | | | | S |
+| {SCR , MBS} (CLP = 0 + 1) | S | S | | | | | S | |
+| Tagging (Note 13) | N | N | N | Y/N | N | Y/N | N | Y/N |
+| End-to-end timing required | N | Y | Y | Y | Y | Y | Y | Y |
+| For the given direction: | | | | | | | | |
+| Requested ATC [4] | SBR1 | SBR1 | Note 2 | Note 2 | Note 2 | SBR2/SBR3
Note 6 | Note 7 | SBR2/SBR3 |
+| Implicitly requested QOS
when the QOS class is 0 | Class 2 | Note 10 | Note 3 | Note 3 | Note 8 | Note 8 | Note 8 | Note 8 |
+| For the given direction: | | | | | | | | |
+| I.371 [4] ATC that supports
the requested ATC | SBR1 | SBR1 | DBR | DBR
Note 4 | DBR | Note 9 | SBR1 | Note 9 |
+| I.356 [5] QOS class that
supports the implicitly
requested QOS | Class 2 | Class 1 | Class 1 | Class 1 | Class 1 | | Class 1 | |
+| | Note 12 | Note 12 | Note 11 | Note 11 | Note 11 | Note 11 | Note 11 | Note 11 |
+
+**Table A.1/Q.2961.2 – Valid combinations of traffic-related parameters in the SETUP message (concluded)**
+
+### **Notes relative to Table A.1:**
+
+NOTE 1 – BTC values 0, 1, 2, 4, 6, 8 are not used on transmission but shall be understood on reception.
+
+NOTE 2 – The requested capability in this case is not defined in Recommendation I.371 [4] and differs from the DBR ATM transfer capability (see Recommendation I.371 [4]) only in that selective discardability of CLP = 1 cells may apply.
+
+NOTE 3 – The implicitly requested QOS class in this case is not defined in Recommendation I.356 [5] and differs from QOS class 1 (see Recommendation I.356 [5]) in that the CLR commitment is only for CLP = 0 cells.
+
+NOTE 4 – PCR (CLP = 0) is ignored and tagging is not performed.
+
+NOTE 5 – The implicitly requested QOS class corresponds to QOS class 3 (see Recommendation I.356 [5]).
+
+NOTE 6 – This is equivalent to SBR2/SBR3 with SCR (CLP = 0) equal to specified PCR (CLP = 0) and with MBS (CLP = 0) equal to 1.
+
+NOTE 7 – The requested capability in this case is not defined in Recommendation I.371 [4] and differs from the SBR1 ATM transfer capability (see Recommendation I.371 [4]) only in that selective discardability of CLP = 1 cells may apply.
+
+NOTE 8 – The implicitly requested QOS class in this case is not defined in I.356 [5] and differs from QOS class 3 (see Recommendation I.356 [5]) in that end-to-end timing is required.
+
+NOTE 9 – There is no combination recommended in Recommendation I.356 [5].
+
+NOTE 10 – The implicitly requested QOS class in this case is not defined in Recommendation I.356 [5].
+
+NOTE 11 – This combination is supported in order to promote backward compatibility with the first edition of Recommendation Q.2931 (1995), with Recommendations Q.2961.1 [3] and Q.2933 [6].
+
+NOTE 12 – For this combination, the ATC and the QOS class is the same in both directions.
+
+NOTE 13 – If tagging is not specified but requested by a user, or if tagging is specified for a combination but not supported by a network, the call shall proceed without tagging being applied.
+
+A Blank in this table means that the traffic parameter is not applicable for this combination.
+
+PCR = Peak Cell Rate, SCR = Sustainable Cell Rate, MBS = Maximum Burst Size, S = Specified
+
+For the Tagging row: Y = Yes, N = No or No indication, Y/N = either "Yes" or "No or No Indication"
+
+SBR2/SBR3 = If tagging is allowed (as indicated in the CONNECT message) then the ATC is SBR3; otherwise, the ATC is SBR2.
+
+# APPENDIX I
+
+## Guidelines on meaning of bearer class field
+
+### I.1 Bearer class
+
+The following provides a brief description of what is meant by the various codings of the bearer class field in the Broadband bearer capability information element.
+
+#### I.1.1 BCOB-A
+
+This class provides for a virtual channel-based capability where the service data unit integrity will depend on the presence of other parameters, e.g. when a Narrowband bearer capability information element is present and specifies a request for an emulated 64 kbit/s-based N-ISDN bearer service, the service data unit integrity is provided for the emulated 64 kbit/s channel (8 kHz \* 8 bits). In this case, the network may act upon the contents of the AAL parameters information element to provide interworking with N-ISDN.
+
+#### I.1.2 BCOB-C
+
+This class provides for a virtual channel-based capability where AAL service data unit integrity is provided. Thus, the network may look at the AAL parameters information element in order to provide this service data unit integrity.
+
+#### I.1.3 BCOB-X
+
+This class provides for a virtual channel-based capability where ATM service data unit integrity is provided.
+
+#### I.1.4 FR
+
+This class provides for a virtual channel-based capability where layer 2 frame service data unit integrity is provided. In this, the network may not process any higher layer user plane protocols. Thus, the network may look at the AAL parameters, link layer core parameters, and the link layer protocol parameters information elements in order to provide this service data unit integrity.
+
+# APPENDIX II
+
+## Guidelines on use of BTC field
+
+Although great effort was put into making the restructuring of Octet 5a (BTC field) of the Broadband bearer capability information element backward-compatible, some of the allowed combinations in Table A.1 will not be supported by equipment that do not implement this Recommendation. This appendix will identify where backward compatibility is not preserved and provide guidance on when these non-backward-compatible codings should be used.
+
+The following identifies the non-backward-compatible codings:
+
+- Octet 5a present with bearer classes BCOB-A or BCOB-C;
+- BTC field values of 7, 11 and 19.
+
+A call placed with either of the above will not complete if the call must transit a network that does not support the BTC field or if the called party does not support the BTC field.
+
+### II.1 Guidelines on the use of BTC value of 7
+
+The BTC value of 7 may be used with BCOB-A and with BCOB-X to request the I.371-defined DBR ATC. A similar capability may be requested by using the BTC value of 5 for BCOB-X or by the absence of octet 5a of the Broadband bearer capability information element for BCOB-A. This capability differs from DBR only in that cells with the CLP bit set to 1 may be subject to preferential discard. If the user sends only CLP = 0 cells, the service provided is the same. Thus, when backward compatibility is a concern and the user is willing to accept that cells with CLP = 1 are subject to discard, the user should request:
+
+- BCOB-A with octet 5a absent instead of BCOB-A with a BTC value of 7;
+- BCOB-X with BTC value of 5 instead of BCOB-A with a BTC value of 7.
+
+If discardability of CLP = 1 cells is not acceptable to the user, then the BTC value of 7 should be used. This way, if the connection is established, it will have the desired ATC.
+
+### II.2 Guidelines on the use of BTC value of 11
+
+The BTC value of 11 may be used with BCOB-C and with BCOB-X to request the I.371-defined SBR1 ATC. A similar capability may be requested by using the BTC value of 10 for BCOB-X or by the absence of octet 5a of the Broadband bearer capability information element for BCOB-C. This capability differs from SBR1 only in that cells with the CLP bit set to 1 may be subject to preferential discard. If the user sends only CLP = 0 cells, the service provided is the same. Thus when backward compatibility is a concern and the user is willing to accept that cells with CLP = 1 are subject to discard, the user should request:
+
+- BCOB-C with octet 5a absent instead of BCOB-C with a BTC value of 11;
+- BCOB-X with either octet 5a absent or BTC value of 10 instead of BCOB-X with a BTC value of 11;
+- FR with either octet 5a absent or BTC value of 10 instead of FR with a BTC value of 11.
+
+If discardability of CLP = 1 cells is not acceptable to the user, then the BTC value of 11 should be used. This way, if the connection is established, it will have the desired ATC.
+
+### II.3 Guidelines on the use of BTC value of 19
+
+The BTC value of 19 may be used with BCOB-A and with BCOB-X to request the I.371-defined SBR1 ATC. A similar capability may be requested by using the BTC value of 9 for BCOB-X or by the absence of octet 5a of the Broadband bearer capability information element for BCOB-C. This capability differs from SBR1 only in that cells with the CLP bit set to 1 may be subject to preferential discard. If the user sends only CLP = 0 cells, the service provided is the same. Thus when backward compatibility is a concern and the user is willing to accept that cells with CLP = 1 are subject to discard, the user should request:
+
+- BCOB-C with BTC value of 9 instead of BCOB-C with a BTC value of 19;
+- BCOB-X with BTC value of 9 instead of BCOB-X with a BTC value of 19;
+- FR with BTC value of 9 instead of FR with a BTC value of 19.
+
+If discardability of CLP = 1 cells is not acceptable to the user, then the BTC value of 19 should be used. This way, if the connection is established, it will have the desired ATC.
+
+# ITU-T RECOMMENDATIONS SERIES
+
+- Series A Organization of the work of the ITU-T
+- Series B Means of expression: definitions, symbols, classification
+- Series C General telecommunication statistics
+- Series D General tariff principles
+- Series E Overall network operation, telephone service, service operation and human factors
+- Series F Non-telephone telecommunication services
+- Series G Transmission systems and media, digital systems and networks
+- Series H Audiovisual and multimedia systems
+- Series I Integrated services digital network
+- Series J Transmission of television, sound programme and other multimedia signals
+- Series K Protection against interference
+- Series L Construction, installation and protection of cables and other elements of outside plant
+- Series M TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits
+- Series N Maintenance: international sound programme and television transmission circuits
+- Series O Specifications of measuring equipment
+- Series P Telephone transmission quality, telephone installations, local line networks
+- Series Q Switching and signalling**
+- Series R Telegraph transmission
+- Series S Telegraph services terminal equipment
+- Series T Terminals for telematic services
+- Series U Telegraph switching
+- Series V Data communication over the telephone network
+- Series X Data networks and open system communication
+- Series Z Programming languages
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.2961C-200012-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2961C-200012-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..30cfe151623b1f627b726f9ae4f3f6aa53cc0095
--- /dev/null
+++ b/marked/Q/T-REC-Q.2961C-200012-I_PDF-E/raw.md
@@ -0,0 +1,245 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**Q.2961 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
+(DSS2) – Additional traffic parameters:
+Test suite structure and test purposes
+(TSS & TP) for the user**
+
+ITU-T Recommendation Q.2961 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.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 |
+| INTELLIGENT NETWORK | Q.1200-Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 |
+| BROADBAND ISDN | Q.2000-Q.2999 |
+| General aspects | Q.2000-Q.2099 |
+| Signalling ATM adaptation layer (SAAL) | Q.2100-Q.2199 |
+| Signalling network protocols | Q.2200-Q.2299 |
+| Common aspects of B-ISDN application protocols for access signalling and network signalling and interworking | Q.2600-Q.2699 |
+| B-ISDN application protocols for the network signalling | Q.2700-Q.2899 |
+| B-ISDN application protocols for access signalling | Q.2900-Q.2999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## **Digital subscriber signalling system No. 2 (DSS2) – Additional traffic parameters: 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_B$ reference point or coincident $S_B$ and $T_B$ reference point (as defined in ITU-T I.413 [10]) of implementations conforming to the procedures for the handling of additional traffic parameters that may be used for basic call and connection control of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the Broadband Integrated Services Digital Network (B-ISDN), ITU-T Q.2961 [1], [2], [3], [4], [5] and [6].
+
+Other Recommendations of the Q.2961 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.2961 C was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 6 December 2000.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+### NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2001
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU.
+
+## CONTENTS
+
+| | Page |
+|---------------------------------|-------------|
+| 1 Scope ..... | 1 |
+| 2 References ..... | 1 |
+| 3 Endorsement..... | 2 |
+| 4 Coverage ..... | 2 |
+| 5 Modifications ..... | 2 |
+| Appendix I – Bibliography ..... | 3 |
+
+
+
+## **Digital subscriber signalling system No. 2 (DSS2) – Additional traffic parameters: 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_B$ reference point or coincident $S_B$ and $T_B$ reference point (as defined in ITU-T I.413 [10]) of implementations conforming to the procedures for the handling of additional traffic parameters that may be used for basic call and connection control of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the Broadband Integrated Services Digital Network (B-ISDN), ITU-T Q.2961 [1], [2], [3], [4], [5] and [6].
+
+Other Recommendations of the Q.2961 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 capabilities for the indication of traffic parameters above of the peak cell rate at connection request time, to be attached at either side of a $T_B$ reference point or coincident $S_B$ and $T_B$ reference point when used as an access to the public B-ISDN.
+
+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 Q.2961.1 (1995), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Additional signalling capabilities to support traffic parameters for the tagging option and the sustainable cell rate parameter set.*
+- [2] ITU-T Q.2961.2 (1997), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Support of ATM transfer capability in the broadband bearer capability information element.*
+- [3] ITU-T Q.2961.3 (1997), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Signalling capabilities to support traffic parameters for the available bit rate (ABR) ATM transfer capability.*
+- [4] ITU-T Q.2961.4 (1997), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Signalling capabilities to support traffic parameters for the ATM block transfer (ABT) ATM transfer capability.*
+- [5] ITU-T Q.2961.5 (1999), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Additional traffic parameters for cell delay variation tolerance indication.*
+
+- [6] ITU-T Q.2961.6 (1998), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Additional signalling procedures for the support of the SBR2 and SBR3 ATM transfer capabilities.*
+- [7] ITU-T Q.2961 B (2000), *Digital subscriber signalling system No. 2 (DSS2) – Additional traffic parameters: Protocol implementation conformance statement (PICS) proforma.*
+- [8] ITU-T Q.2931 (1995), *Digital subscriber signalling system No. 2 – User-network interface (UNI) layer 3 specification for basic call/connection control.*
+- [9] ITU-T Q.2962 (1998), *Digital subscriber signalling system No. 2 – Connection characteristics negotiation during call/connection establishment phase.*
+- [10] ITU-T I.413 (1993), *B-ISDN user-network interface.*
+- [11] ETSI EN 301 068-3 V1.1.2 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; ATM transfer capability and traffic parameter indication; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user.*
+
+## 3 Endorsement
+
+The text of ETSI EN 301 068-3 [11] was approved by ITU-T as Recommendation Q.2961 C with agreed modifications as given below.
+
+## 4 Coverage
+
+This Recommendation covers ITU-T Q.2961.1 [1], Q.2961.2 [2], Q.2961.3 [3], Q.2961.4 [4] and Q.2961.6 [6].
+
+NOTE – For testing of Q.2961.6, test groups for checking conformance to Q.2961.1 and Q.2961.2 shall be used with the exception of test groups 02 and 08 ("Traffic management option for support of tagging").
+
+## 5 Modifications
+
+Throughout the text of ETSI EN 301 068-3 [11] replace references and text as shown in the following table:
+
+| Reference in ETSI EN 301 068-3 | Modified reference |
+|---------------------------------------------|-------------------------------|
+| EN 301 068-1 | Q.2961-series Recommendations |
+| EN 301 068-1 [1] (ITU-T Q.2961.1, modified) | ITU-T Q.2961.1 [1] |
+| EN 301 068-1 [1] (ITU-T Q.2961.2, modified) | ITU-T Q.2961.2 [2] |
+| EN 301 068-1 [1] (ITU-T Q.2961.3, modified) | ITU-T Q.2961.3 [3] |
+| EN 301 068-1 [1] (ITU-T Q.2961.4, modified) | ITU-T Q.2961.4 [4] |
+| EN 300 443-1 [2] | ITU-T Q.2931 [8] |
+| EN 301 068-2 [4] | ITU-T Q.2961 B [7] |
+| EN 301 067-1 | ITU-T Q.2962 |
+| 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 17, Bibliography**
+
+Delete the whole clause "Bibliography".
+
+NOTE 2 – It is replaced by Appendix I "Bibliography" of this Recommendation.
+
+###### **Page 18, 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 068-1 V1.2.4 (1998), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; ATM transfer capability and traffic parameter indication; Part 1: Protocol specification.*
+- [C] ETSI EN 301 068-2 V1.1.3 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; ATM transfer capability and traffic parameter indication; Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification.*
+- [D] ETSI EN 301 068-4 V1.1.1 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; ATM transfer capability and traffic parameter indication; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the user.*
+- [E] ETSI EN 301 068-5 V1.1.2 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; ATM transfer capability and traffic parameter indication; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network.*
+
+- [F] ETSI EN 301 068-6 V1.1.1 (2000), Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; ATM transfer capability and traffic parameter indication; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network.
+- [G] ETSI EN 301 067-1 V1.1.3 (1999), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Negotiation during call/connection establishment phase; Part 1: Protocol specification.*
+- [H] 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 | Transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure and Internet protocol aspects |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.2961D-200012-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2961D-200012-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..22ae9ebdea9b51453430f8f1eec96d3dbc3b7c43
--- /dev/null
+++ b/marked/Q/T-REC-Q.2961D-200012-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e10c8f5c58c1323c42c6cd1928d748c09cc309115dcd821f1e68faff41795380
+size 8357
diff --git a/marked/Q/T-REC-Q.2963.1B-200012-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2963.1B-200012-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c839d5ca25348e6d37a2adcf57fbff1d7b8bac2f
--- /dev/null
+++ b/marked/Q/T-REC-Q.2963.1B-200012-I_PDF-E/raw.md
@@ -0,0 +1,254 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**Q.2963.1 B**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(12/2000)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Broadband ISDN – B-ISDN application protocols for
+access signalling
+
+---
+
+**Digital subscriber signalling system No. 2 –
+Connection modification: Peak cell rate
+modification by the connection owner: Protocol
+implementation conformance statement (PICS)
+proforma**
+
+ITU-T Recommendation Q.2963.1 B
+
+(Formerly CCITT Recommendation)
+
+---
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|-----------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 |
+| DIGITAL EXCHANGES | Q.500-Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 |
+| Q3 INTERFACE | Q.800-Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 |
+| INTELLIGENT NETWORK | Q.1200-Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 |
+| BROADBAND ISDN | Q.2000-Q.2999 |
+| B-ISDN application protocols for access signalling | Q.2900-Q.2999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## **Digital subscriber signalling system No. 2 – Connection modification: Peak cell rate modification by the connection owner: Protocol implementation conformance statement (PICS) proforma**
+
+## **Summary**
+
+This Recommendation specifies the Protocol Implementation Conformance Statement (PICS) proforma the $T_B$ reference point or coincident $S_B$ and $T_B$ reference point (as defined in ITU-T I.413 [3]) 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 [2].
+
+Other Recommendations of the Q.2963.1 family specify Test Suite Structure and Test Purposes (TSS & TP) and Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on this Recommendation.
+
+NOTE – This Recommendation related to protocol conformance is published only in English; it is based on an external SDO's standard published in English.
+
+### **Source**
+
+ITU-T Recommendation Q.2963.1 B was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 6 December 2000.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2001
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU.
+
+## CONTENTS
+
+| | Page |
+|----------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References ..... | 1 |
+| 3 Endorsement..... | 2 |
+| 4 Coverage ..... | 2 |
+| 5 Modifications ..... | 2 |
+| 5.1 General..... | 2 |
+| 5.2 CONNECTION AVAILABLE message ..... | 3 |
+| Appendix I – Bibliography ..... | 3 |
+
+## **Digital subscriber signalling system No. 2 – Connection modification: Peak cell rate modification by the connection owner: Protocol implementation conformance statement (PICS) proforma**
+
+# **1 Scope**
+
+This Recommendation specifies the Protocol Implementation Conformance Statement (PICS) proforma the $T_B$ reference point or coincident $S_B$ and $T_B$ reference point (as defined in ITU-T I.413 [3]) 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 [2].
+
+Other Recommendations of the Q.2963.1 family specify Test Suite Structure and Test Purposes (TSS & TP) and Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on this Recommendation.
+
+This Recommendation is applicable to equipment, supporting 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_B$ reference point or coincident $S_B$ and $T_B$ reference point when used as an access to the public B-ISDN.
+
+To evaluate conformance of a particular implementation, it is necessary to have a statement of which capabilities and options have been implemented for a given protocol. Such a statement is called an Implementation Conformance Statement (ICS). An ICS stating what capabilities and options have been implemented for a particular protocol is called a protocol ICS. This is commonly abbreviated to "PICS".
+
+The supplier of a protocol implementation that is claimed to conform to ITU-T Q.2963.1 [2] is required to complete a copy of the PICS proforma provided in Annex A of the endorsed document as modified by this Recommendation.
+
+## **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 Q.2931 (1995), *Digital subscriber signalling system No. 2 (DSS2) – User-network interface (UNI) layer 3 specification for basic call/connection control.*
+- [2] ITU-T Q.2963.1 (1999), *Digital subscriber signalling system No. 2 – Connection modification: Peak cell rate modification by the connection owner.*
+- [3] ITU-T I.413 (1993), *B-ISDN user-network interface.*
+- [4] 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.*
+
+# 3 Endorsement
+
+The text of ETSI EN 301 003-2 [4] was approved by ITU-T as Recommendation Q.2963.1 B with agreed modifications as given below.
+
+NOTE – Underlining and/or strike-out is used to highlight new or deleted text where detailed indication of modifications is necessary.
+
+# 4 Coverage
+
+This Recommendation covers ITU-T Q.2963.1 [2].
+
+# 5 Modifications
+
+## 5.1 General
+
+Throughout the text of ETSI EN 301 003-2 [4] replace references and text as shown in the following table:
+
+| Reference in ETSI EN 301 003-2 | Modified reference |
+|--------------------------------------------|--------------------|
+| EN 300 443-1 | ITU-T Q.2931 |
+| ITU-T Q.2931 as modified by EN 300 443-1 | ITU-T Q.2931 |
+| EN 301 003-1 | ITU-T Q.2963.1 |
+| ITU-T Q.2963.1 as modified by EN 301 003-1 | ITU-T Q.2963.1 |
+| EN | Recommendation |
+| Standard | Recommendation |
+
+### Page 4, Intellectual Property Rights
+
+Delete the whole section.
+
+#### Page 4, Foreword
+
+Delete the whole Foreword.
+
+NOTE – It is replaced by the Foreword of this Recommendation.
+
+#### Page 5, Clause 1 Scope
+
+Replace the whole clause with the following:
+
+#### "1 Scope
+
+See clause 1 Scope of this Recommendation above."
+
+#### Page 5, Clause 2 References
+
+Replace reference [1] with the following below:
+
+[1] Void
+
+#### Page 8, clause "Reference column"
+
+Modify the text of the clause as below:
+
+"Except where explicitly stated, the reference column refers to the appropriate text of ITU-T Q.2963.1 [2] ~~Q.2931 as modified by EN 300 443-1 [1]~~ describing the particular item. Note, however, that a reference indicates only the location of the most essential information about an item. All
+
+| additional requirements contained in ITU-T Q.2931 [1] ~~EN 300 443-1 [1]~~ have also to be taken into account when making a statement about the conformance of that particular item."
+
+#### **Page 12, clause A.3 "Identification of the protocol to which this PICS proforma applies"**
+
+Replace the whole clause by the following:
+
+"This PICS proforma applies to the following Recommendation:
+
+ITU-T Q.2963.1 (1999), *Digital subscriber signalling system No. 2 – Connection modification: Peak cell rate modification by the connection owner*".
+
+#### **Page 19, History**
+
+Delete the whole clause "History".
+
+### **5.2 CONNECTION AVAILABLE message**
+
+On page 17, clause A.7.3.2 "Requesting entity protocol data unit parameters transmitted", delete Table A.8: "Connection Available PDU parameters transmitted".
+
+On page 17, clause A.8.3.1 "Responding entity protocol data unit parameters received", delete Table A.12 "Connection Available PDU parameters received".
+
+## **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-3 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 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user*.
+- [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*.
+
+### SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure and Internet protocol aspects |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.2963.1E-200012-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2963.1E-200012-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..22ae9ebdea9b51453430f8f1eec96d3dbc3b7c43
--- /dev/null
+++ b/marked/Q/T-REC-Q.2963.1E-200012-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e10c8f5c58c1323c42c6cd1928d748c09cc309115dcd821f1e68faff41795380
+size 8357
diff --git a/marked/Q/T-REC-Q.3050-201208-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3050-201208-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..854266053f2012b8db1f6ad602b59c6c7848cf02
--- /dev/null
+++ b/marked/Q/T-REC-Q.3050-201208-I_PDF-E/raw.md
@@ -0,0 +1,468 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.3050**
+
+(08/2012)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Signalling requirements and protocols for the NGN –
+Network signalling and control functional architecture
+
+---
+
+**Description of signalling protocols supporting
+next generation network capability sets**
+
+Recommendation ITU-T Q.3050
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|---------------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3999 |
+| General | Q.3000–Q.3029 |
+| Network signalling and control functional architecture | Q.3030–Q.3099 |
+| Network data organization within the NGN | Q.3100–Q.3129 |
+| Bearer control signalling | Q.3130–Q.3179 |
+| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 |
+| Resource control protocols | Q.3300–Q.3369 |
+| Service and session control protocols | Q.3400–Q.3499 |
+| Service and session control protocols – supplementary services | Q.3600–Q.3649 |
+| NGN applications | Q.3700–Q.3849 |
+| Testing for next generation networks | Q.3900–Q.3999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## Recommendation ITU-T Q.3050
+
+# Description of signalling protocols supporting next generation network capability sets
+
+## Summary
+
+Recommendation ITU-T Q.3050 provides brief descriptions of signalling protocols supporting next generation network (NGN) capability sets in terms of the overall protocol Recommendations defined in ITU-T. The descriptions are from the aspects of NGN capability set, NGN functional architecture, NGN signalling architecture and protocol Recommendations that have been standardized in ITU-T.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group |
+|---------|----------------|------------|-------------|
+| 1.0 | ITU-T Q.3050 | 2012-08-13 | 11 |
+
+## Keywords
+
+Architecture, NGN, Protocol set.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2012
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|--------------------------------------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 2 |
+| 4 Abbreviations and acronyms ..... | 2 |
+| 5 Conventions ..... | 3 |
+| 6 NGN capability sets..... | 3 |
+| 6.1 NGN capability set 1 ..... | 3 |
+| 6.2 NGN capability set 2 ..... | 4 |
+| 7 NGN functional architecture..... | 4 |
+| 7.1 Overview of NGN architecture ..... | 4 |
+| 7.2 Generalized NGN functional architecture ..... | 5 |
+| 8 NGN signalling architecture ..... | 6 |
+| 8.1 Mapping functions and functional blocks into physical entities ..... | 7 |
+| 8.2 Mapping reference points to interfaces ..... | 8 |
+| 9 Signalling protocols supporting NGN capability sets ..... | 8 |
+| 9.1 External interfaces of NGN ..... | 8 |
+| 9.2 Internal interfaces of NGN ..... | 9 |
+
+
+
+# Description of signalling protocols supporting next generation network capability sets
+
+# 1 Scope
+
+This Recommendation provides brief descriptions of signalling protocols supporting next generation network (NGN) capability sets in terms of the overall protocol Recommendations defined in ITU-T. The descriptions are from the aspects of NGN capability sets, NGN functional architecture, NGN signalling architecture and protocol Recommendations that have been standardized in ITU-T.
+
+# 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.1741.6] Recommendation ITU-T Q.1741.6 (2009), *IMT-2000 references to Release 8 of GSM-evolved UMTS core network*.
+- [ITU-T Q.3221] Recommendation ITU-T Q.3221 (2008), *Requirements and protocol at the interface between the service control entity and the transport location management physical entity (S-TCI interface)*.
+- [ITU-T Q.3301.1] Recommendation ITU-T Q.3301.1 (2010), *Resource control protocol No. 1, version 2 – Protocol at the Rs interface between service control entities and the policy decision physical entity*.
+- [ITU-T Q.3302.1] Recommendation ITU-T Q.3302.1 (2010), *Resource control protocol No. 2 (rcp2) – Protocol at the Rp interface between transport resource control physical entities*.
+- [ITU-T Q.3303.0] Recommendation ITU-T Q.3303.0 (2007), *Resource control protocol No. 3 – Protocols at the Rw interface between a policy decision physical entity (PD-PE) and a policy enforcement physical entity (PE-PE): Overview*.
+- [ITU-T Q.3303.1] Recommendation ITU-T Q.3303.1 (2012), *Resource control protocol No. 3 – Protocol at the interface between a Policy Decision Physical Entity (PD-PE) and a Policy Enforcement Physical Entity (PE-PE): COPS alternative version 2*.
+- [ITU-T Q.3303.2] Recommendation ITU-T Q.3303.2 (2007), *Resource control protocol No. 3 – Protocol at the interface between a Policy Decision Physical Entity (PD-PE) and a Policy Enforcement Physical Entity (PE-PE) (Rw interface): H.248 alternative*.
+- [ITU-T Q.3303.3] Recommendation ITU-T Q.3303.3 (2012), *Resource control protocol No. 3 – Protocols at the Rw interface between a policy decision physical entity (PD-PE) and a policy enforcement physical entity (PE-PE): Diameter profile version 2*.
+
+- [ITU-T Q.3304.1] Recommendation ITU-T Q.3304.1 (2012), *Resource control protocol No. 4 (rcp4) – Protocols at the Rc interface between a transport resource control physical entity and a transport physical entity: COPS alternative.*
+- [ITU-T Q.3304.2] Recommendation ITU-T Q.3304.2 (2012), *Resource control protocol No. 4 (rcp4) – Protocols at the Rc interface between a transport resource control physical entity (TRC-PE) and a transport physical entity (T-PE): SNMP alternative.*
+- [ITU-T Q.3305.1] Recommendation ITU-T Q.3305.1 (2011), *Resource control protocol No. 5 (rcp5) – Protocol at the interface between transport resource control physical entity and policy decision physical entity (Rt interface): Diameter-based.*
+- [ITU-T Q.3401] Recommendation ITU-T Q.3401 (2007), *NGN NNI signalling profile (protocol set 1).*
+- [ITU-T Q.3402] Recommendation ITU-T Q.3402 (2008), *NGN UNI signalling profile (Protocol set 1).*
+- [ITU-T Y.2006] Recommendation ITU-T Y.2006 (2008), *Description of capability set 1 of NGN release 1.*
+- [ITU-T Y.2007] Recommendation ITU-T Y.2007 (2010), *NGN capability set 2.*
+- [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.2211] Recommendation ITU-T Y.2211 (2007), *IMS-based real-time conversational multimedia services over NGN emulation.*
+- [ITU-T Y.2271] Recommendation ITU-T Y.2271 (2006), *Call server-based PSTN/ISDN emulation.*
+- [IETF RFC 2616] IETF RFC 2616 (1999), *Hypertext Transfer Protocol -- HTTP/1.1.*
+
+# 3 Definitions
+
+None.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|---------|-------------------------------------------------|
+| AF-PE | Application Function Physical Entity |
+| ANI | Application Network Interface |
+| ASS-PE | Application and Service Support Physical Entity |
+| CD-PE | Content Distribution Physical Entity |
+| COPS | Common Open Policy Service |
+| COPS-PR | COPS usage for Policy Provisioning |
+| DTMF | Dual Tone Multi-Frequency |
+| IP PBX | Internet Protocol Private Branch eXchange |
+| IPTV | IP Television |
+| ISDN | Integrated Services Digital Network |
+
+| | |
+|--------|--------------------------------------------|
+| NACF | Network Attachment Control Functions |
+| NAC-PE | Network Attachment Control Physical Entity |
+| NGN | Next Generation Network |
+| NNI | Network-Network Interface |
+| PD-PE | Policy Decision Physical Entity |
+| PE-PE | Policy Enforcement Physical Entity |
+| PSTN | Public Switched Telephone Network |
+| QoS | Quality of Service |
+| RCIP | Resource Connection Initiation Protocol |
+| RACE | Resource and Admission Control Entity |
+| SC-PE | Service Control Physical Entity |
+| SDP | Session Description Protocol |
+| SIP | Session Initiation Protocol |
+| SNI | Service Network Interface |
+| SNMP | Simple Network Management Protocol |
+| TRC-PE | Transport Resource Control Physical Entity |
+| T-PE | Transport Physical Entity |
+| UE | User Equipment |
+| UNI | User Network Interface |
+| VoD | Video on Demand |
+| VoIP | Voice over IP |
+
+# 5 Conventions
+
+None.
+
+# 6 NGN capability sets
+
+## 6.1 NGN capability set 1
+
+Capability set 1 is primarily focused on session based conversational services such as telephony and video phone service. Services supported by capability set 1 include:
+
+- PSTN/ISDN emulation services.
+
+PSTN/ISDN emulation services are provided by an NGN to support legacy terminals and interfaces. The PSTN/ISDN emulation services are the same or better than those provided by circuit-switched networks. The PSTN/ISDN emulation services are defined in [ITU-T Y.2271].
+
+- PSTN/ISDN simulation services
+
+PSTN/ISDN simulation services provide PSTN/ISDN-like services. The requirements are independent of the media that is used during the communication. PSTN/ISDN simulation services requirements are defined in [ITU-T Y.2211].
+
+Transport connectivity, communication modes, codecs and other capabilities for NGN capability set 1 are described in clause 7 of [ITU-T Y.2006].
+
+## **6.2 NGN capability set 2**
+
+Capability set 2 includes features that are necessary to provide basic IPTV services (e.g., linear TV and VoD) in NGN. Therefore, capability set 2 includes ITU-T Recommendations related to NGN-based IPTV.
+
+Internet Protocol Version 6 (IPv6) support, multicast support and other capabilities for NGN capability set 2 are described in clause 7 of [ITU-T Y.2007].
+
+# **7 NGN functional architecture**
+
+## **7.1 Overview of NGN architecture**
+
+NOTE – The following text is based on the text provided in clause 7 of [ITU-T Y.2012].
+
+Figure 1 shows an overview of the NGN functional architecture.
+
+The NGN functional architecture supports the UNI, NNI, ANI and SNI reference points as described in clause 6.2 of [ITU-T Y.2012].
+
+The NGN functions are divided into service stratum functions and transport stratum functions according to [ITU-T Y.2011]. To provide these services, several functions are necessary in both the service stratum and the transport stratum, as illustrated in Figure 1. For detailed description of these functions, refer to [ITU-T Y.2012].
+
+
+
+The diagram illustrates the NGN architecture overview, organized into three main strata and several functional blocks:
+
+- Applications:** A light blue box at the top.
+- Service Stratum:** A green box containing:
+ - Application Support Functions and Service Support Functions:** A white box at the top of the Service Stratum.
+ - Service Control and Content Delivery Functions:** A white box below the Application Support Functions, containing:
+ - Service User Profiles:** Represented by a cylinder icon.
+ - Service Control Functions:** A white box.
+ - Content Delivery Functions:** A white box.
+- Transport Stratum:** A yellow box containing:
+ - Transport Control Functions:** A white box containing:
+ - Network Attachment and Control Functions:** A white box containing a **Transport User Profiles** cylinder icon.
+ - Mobility Management and Control Functions:** A white box.
+ - Resource and Admission control Functions:** A white box.
+ - Transport Functions:** A white box at the bottom of the Transport Stratum.
+
+**Management Functions:** A vertical pink bar on the left side.
+
+**IdM Functions:** A vertical yellow bar on the left side, connected to Management Functions.
+
+**End-User Functions:** A white box on the left side, connected to Management Functions.
+
+**Interfaces:**
+
+- UNI (User Network Interface):** A vertical red line on the left side.
+- ANI (Application Network Interface):** A vertical red line on the right side.
+- SNI (Service Network Interface):** A vertical red line on the right side.
+- NNI (Network Network Interface):** A vertical red line on the right side.
+
+**External Connections:**
+
+- Functions from other Service Providers:** A white box on the right side, connected to the SNI.
+- Functions from Other Networks:** A white box on the right side, connected to the NNI.
+
+**Legend:**
+
+- Control:** Dashed black line.
+- Management:** Dashed pink line.
+- Media:** Solid blue line.
+- IdM:** Dashed orange line.
+
+NGN architecture overview diagram showing layers for Applications, Service Stratum, and Transport Stratum, with Management, IdM, and End-User functions, and interfaces like ANI, SNI, UNI, and NNI.
+
+NOTE – Figure 1 is an exact replica of Figure 7-1 of [ITU-T Y.2012].
+
+**Figure 1 – NGN architecture overview**
+
+## 7.2 Generalized NGN functional architecture
+
+Clause 9 of [ITU-T Y.2012] describes the generalized functional architecture for NGN, including the definitions of the generalized functional entities and reference points.
+
+Figure 2 shows the NGN functional architecture framework.
+
+For a detailed description of the functional entities and reference points of the generalized NGN functional architecture, refer to clause 9 of [ITU-T Y.2012].
+
+
+
+Figure 2 – NGN functional architecture framework. This diagram illustrates the functional architecture of a Next Generation Network (NGN). It is organized into three main strata: the NGN service stratum (top, green), the Transport Control Functions stratum (middle, yellow), and the NGN transport stratum (bottom, yellow). A vertical pink bar on the left represents Management Functions, which connect to IdM Functions and End-User Functions. The service stratum contains Application Support Functions and Service Support Functions, which further branch into Service Control Functions and Content Delivery Functions. The transport control stratum includes NACF, MMCF, and RACF. The transport stratum contains Transport Processing Functions. External entities on the right include Content Provider Functions, Other NGNs, IP Multimedia Networks, and PSTN/ISDN, all connected via various interfaces like ANI, A-ON1, TC-ON1, T-ON2, T-ON1, and T-ON3. Numerous interfaces are labeled throughout the diagram, such as I-An, I-Mn, I-Sn, I-TCn, I-Un, A-U1, A-U2, S-U1, S-U2, S-U3, C-U1, C-U2, TC-Ux, TC-U1, TC-U2, TC-U3, TC-U4, TC-U5, T-U1, T-U2, T-U3, T-U4, A-S1 through A-S7, A-C1 through A-C3, S-ON1, S-ON2, A-T1, S-TC1, S-T1 through S-T5, S-TC2 through S-TC5, C-T1, C-T2, TC-TC1, TC-TC2 through TC-TC4, TC-TC5, TC-T1, TC-T7, TC-T8, TC-T2 through TC-T9, and TC-TC3 through TC-TC4.
+
+NOTE – Figure 2 is an exact replica of Figure 9-1 of [ITU-T Y.2012].
+
+**Figure 2 – NGN functional architecture framework**
+
+# 8 NGN signalling architecture
+
+When implementing NGN architecture, some functional entities may be integrated into one or more physical entities. Figure 3 provides an example of how functional entities could be grouped into physical entities in NGN architecture.
+
+
+
+The diagram illustrates the NGN architecture with the following components and interfaces:
+
+- AF-PE** (Application Functions) is at the top, connected to the Service Stratum via the **ANI** (Application Network Interface).
+- Service Stratum** (green box) contains:
+ - ASS-PE** (Application Support Functions) connected to AF-PE and SC-PE/CD-PE via **la-s** and **la-c** interfaces.
+ - SC-PE** (Service Control) and **CD-PE** (Content Distribution) connected to each other via **ls-c** and to ASS-PE via **ls-s**.
+- Transport Stratum** (yellow box) contains:
+ - NAC-PE** (Network Attachment Control) connected to the Service Stratum via **ls-n** and to T-PE via **In-t**.
+ - RACE** (Resource Allocation and Control Entity) containing **PD-PE** (Policy Decision) and **TRC-PE** (Transport Resource Control), connected to NAC-PE via **Rs** and to T-PE via **Rc**.
+ - T-PE** (Transport Functions) connected to NAC-PE, RACE, and PE-PE via **Rs**, **Rc**, and **Rw** interfaces.
+ - PE-PE** (Policy Enforcement) connected to T-PE via **lc-t**.
+- External Interfaces:**
+ - UNI** (User Network Interface) connects the User Entity to the Transport Stratum.
+ - SNI** (Service Network Interface) connects the Service Stratum to external networks: Content Provider, other NGNs, IP Multimedia Networks, and PSTN/ISDN.
+ - NNI** (Network Network Interface) connects the Transport Stratum to external networks.
+
+Diagram of NGN architecture showing physical entities and interfaces. It is divided into three strata: Service Stratum (green) and Transport Stratum (yellow). AF-PE is at the top, connected via ANI. Service Stratum contains ASS-PE, SC-PE, and CD-PE. Transport Stratum contains NAC-PE, RACE (PD-PE, TRC-PE), T-PE, and PE-PE. Interfaces include UNI, SNI, and NNI. External entities include User Entity, Content Provider, other NGNs, IP Multimedia Networks, and PSTN/ISDN.
+
+Figure 3 – Example of physical entities and interfaces in NGN architecture
+
+## 8.1 Mapping functions and functional blocks into physical entities
+
+The mapping of functions and functional blocks into physical entities is shown in Table 8-1.
+
+Table 8-1 – Mapping functions and functional blocks into physical entities
+
+| Physical entities | Functions and functional blocks included |
+|-------------------|---------------------------------------------------------------------------------------------|
+| AF-PE | Application functions |
+| ASS-PE | Application support functions, service support functions, etc. |
+| SC-PE | Service control functional, service user profile functional block |
+| CD-PE | Content distribution and location control functions, content delivery and storage functions |
+| NAC-PE | Network attachment control functions (NACF) |
+| PD-PE | Policy decision functional entity |
+| TRC-PE | Transport resource control functional entity |
+| T-PE | Access network functions, edge functions, core transport functions |
+| PE-PE | Policy enforcement functional entity |
+
+**Table 8-1 – Mapping functions and functional blocks into physical entities**
+
+| Physical entities | Functions and functional blocks included |
+|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------|
+| UE | Application client functions, session client functional block, SCP client functions, content delivery client functions, home network functions |
+
+## 8.2 Mapping reference points to interfaces
+
+The mapping of reference points to interfaces is shown in Table 8-2.
+
+**Table 8-2 – Mapping reference points to interfaces**
+
+| Interfaces | Interface description | Mapping reference points in NGN architecture |
+|------------|------------------------------------|------------------------------------------------------------------------------------------|
+| Ia-s | Interface between ASS-PE and SC-PE | A-S1, A-S2, A-S3, A-S4, A-S5, A-S6, A-S7 |
+| Ia-c | Interface between ASS-PE and CD-PE | A-C1, A-C2, A-C3 |
+| Is-c | Interface between SC-PE and CD-PE | S-C1, S-C2, S-C3, S-C4 |
+| Is-n | Interface between SC-PE and NAC-PE | S-TC1 |
+| Ic-t | Interface between CD-PE and T-PE | C-T1, C-T2 |
+| In-t | Interface between NAC-PE and T-PE | TC-T1 |
+| Rs | Interface between SC-PE and PD-PE | S-TC2
S-TC3
S-TC4
S-TC5 |
+| Rt | Interface between PD-PE and TRC-PE | – |
+| Rw | Interface between PD-PE and PE-PE | TC-T1
TC-T2
TC-T5
TC-T6
TC-T9 |
+| Rc | Interface between TRC-PE and T-PE | Transport resource control physical entity (TRC-PE) and transport physical entity (T-PE) |
+
+# 9 Signalling protocols supporting NGN capability sets
+
+## 9.1 External interfaces of NGN
+
+External interfaces of NGN imply UNI, NNI, ANI and SNI. The technical specifications of external interfaces are listed as follows:
+
+### 9.1.1 UNI as per ITU-T Q.3402
+
+The following text is based on the text provided in clause 1 of [ITU-T Q.3402].
+
+[ITU-T Q.3402] specifies a service-level profile, i.e., SIP/SDP interface description between a user and a network. It also specifies a transport-level profile, e.g., RTP.
+
+Capability set 1 of NGN release 1 of the NGN UNI profile covers voice, video, and data, such as VoIP, multimedia telephony, DTMF, and ITU-T T.38 fax.
+
+[ITU-T Q.3402] specifies common content for all terminal types, e.g., SIP residential gateway terminal adapter, SIP phone, soft phone/client, and SIP IP PBX.
+
+Detailed aspects of the UNI are specified in [ITU-T Q.3402].
+
+### 9.1.2 NNI as per ITU-T Q.3401
+
+The following text is based on the text provided in clause 1 of [ITU-T Q.3401].
+
+[ITU-T Q.3401] contains a service-level profile, i.e., SIP/SDP interface description, between two different network operators (NNI signalling profile), where the two different network operators may support different SIP/SDP profiles (i.e., they differ in terms of SIP extensions, SIP information elements and SDP lines that are supported). A transport-level profile, e.g., RTP, is also described. This is necessary just like the description of the media used in service-level signalling.
+
+Detailed aspects of the NNI are specified in [ITU-T Q.3401].
+
+### 9.1.3 ANI as per ITU-T Q.1741.6
+
+[ITU-T Q.1741.6] endorsed the Third Generation Partnership Project (3GPP) specifications, which specified the SIP protocol used in this interface.
+
+#### 9.1.4 SNI as per IETF RFC 2616
+
+The SNI interface will use HTTP as per [IETF RFC 2616].
+
+## 9.2 Internal interfaces of NGN
+
+Interfaces included in Figure 3 are listed in Table 9-1.
+
+**Table 9-1 – Internal interfaces of NGN**
+
+| Interfaces | Interface description | Protocol passing through interface | Recommendation defining stage 3 |
+|------------|------------------------------------|------------------------------------|---------------------------------|
+| Ia-s | Interface between ASS-PE and SC-PE | SIP | [ITU-T Q.1741.6] (Note) |
+| Ia-c | Interface between ASS-PE and CD-PE | SIP | [ITU-T Q.1741.6] (Note) |
+| Is-c | Interface between SC-PE and CD-PE | SIP | [ITU-T Q.1741.6] (Note) |
+| Is-n | Interface between SC-PE and NAC-PE | Diameter | [ITU-T Q.3221] |
+| Ic-t | Interface between CD-PE and T-PE | For further study | – |
+| In-t | Interface between NAC-PE and T-PE | For further study | – |
+| Rs | Interface between SC-PE and PD-PE | Diameter | [ITU-T Q.3301.1] |
+| Rp | Between TRC-PE | RCIP | [ITU-T Q.3302.1] |
+| Rw | Interface between PD-PE and PE-PE | Introduction | [ITU-T Q.3303.0] |
+| | | COPS-PR | [ITU-T Q.3303.1] |
+| | | ITU-T H.248 | [ITU-T Q.3303.2] |
+| | | Diameter | [ITU-T Q.3303.3] |
+| Rc | Interface between TRC-PE and T-PE | COPS-PR | [ITU-T Q.3304.1] |
+| | | SNMP | [ITU-T Q.3304.2] |
+| Rt | Interface between PD-PE and TRC-PE | Diameter | [ITU-T Q.3305.1] |
+
+NOTE – [ITU-T Q.1741.6] endorsed the 3GPP specifications which specified the SIP protocol used in this interface.
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|---------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3062-202209-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3062-202209-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..07474261b87ca45dd038d8948ee0fb066884a33e
--- /dev/null
+++ b/marked/Q/T-REC-Q.3062-202209-I_PDF-E/raw.md
@@ -0,0 +1,907 @@
+
+
+# Recommendation**ITU-T Q.3062 (09/2022)**
+
+SERIES Q: Switching and signalling, and associated measurements and tests
+
+Signalling requirements and protocols for the NGN –
+Network signalling and control functional architecture
+
+---
+
+**Signalling procedures and protocols for
+enabling interconnection between trustable
+network entities in support of existing and
+emerging networks**
+
+
+
+The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue circular emblem with a stylized globe and the letters 'ITU' in white.
+
+ITU logo
+
+## ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS**
+
+| | |
+|---------------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 |
+| General | Q.3000–Q.3029 |
+| Network signalling and control functional architecture | Q.3030–Q.3099 |
+| Network data organization within the NGN | Q.3100–Q.3129 |
+| Bearer control signalling | Q.3130–Q.3179 |
+| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 |
+| Resource control protocols | Q.3300–Q.3369 |
+| Service and session control protocols | Q.3400–Q.3499 |
+| Service and session control protocols – supplementary services | Q.3600–Q.3616 |
+| Service and session control protocols – supplementary services based on SIP-IMS | Q.3617–Q.3639 |
+| VoLTE/ViLTE network signalling | Q.3640–Q.3655 |
+| NGN applications | Q.3700–Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100–Q.4139 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000–Q.5049 |
+| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050–Q.5069 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T Q.3062
+
+# Signalling procedures and protocols for enabling interconnection between trustable network entities in support of existing and emerging networks
+
+## Summary
+
+Signalling system No. 7 (SS7) is a stack of signalling protocols, which was initially developed by ITU (CCITT) in the 1980s. Since then, SS7 standards have become a generic stack which is widely applied in public switched telephone networks (PSTNs) all over the world. With the growth of mobile telecommunications and the appearance of the mobile application part (MAP) and Camel application part (CAP) protocols, SS7 stack became suitable for public land mobile networks (PLMNs), e.g., 2G, 3G networks. Later, SS7 migrated to the signalling transport or SIGTRAN stack developed by the Internet Engineering Task Force (IETF) which allows operators to set up interconnection of SS7-based networks over Internet protocol (IP) networks. Furthermore, the SS7 logic migrated to Diameter signalling protocol which is currently widely used for interconnection of IP multimedia subsystem (IMS)-based networks, including 4G (VoLTE/ViLTE).
+
+At the development stage, SS7 was designed to be managed by operators with the understanding that anyone connected to the SS7 network was considered trustworthy. With the current network environment, including interconnection over the Internet, SS7-based networks have become vulnerable and can be easily attacked. Moreover, the latest move to Diameter protocol has not solved any of the basic vulnerabilities found in SS7.
+
+Presently, there have been multiple cases where SS7 vulnerabilities have been used for different hackers' attacks. Amongst well-known attacks on SS7 networks include telephone spam, spoofing numbers, location tracking, subscriber fraud, intercept calls and messages, denial of service (DoS), infiltration attacks, routing attacks, etc.
+
+The goal of Recommendation ITU-T Q.3062 is to define the signalling requirements for authentication of signalling messages, in order for operators to be able to verify the authenticity of signalling exchanges based on an accepted trust anchor. This Recommendation includes codes and signalling procedures based on Recommendation ITU-T Q.3057.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.3062 | 2022-09-29 | 11 | 11.1002/1000/15042 |
+
+## Keywords
+
+Authentication, certification authority, data integrity, digital signature, end entity public key certificate, post quantum cryptography, public key certificate, signalling procedures, trust, trust anchor.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at .
+
+© ITU 2022
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|-----------------------------------------------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 2 |
+| 3.1 Terms defined elsewhere ..... | 2 |
+| 3.2 Terms defined in this Recommendation..... | 2 |
+| 4 Abbreviations and acronyms ..... | 3 |
+| 5 Conventions ..... | 3 |
+| 6 Architecture for interconnection between trustable network entities ..... | 4 |
+| 6.1 Reference architecture ..... | 4 |
+| 6.2 Functional entities ..... | 5 |
+| 6.3 Reference points ..... | 5 |
+| 7 Security services ..... | 5 |
+| 8 Security association attribute definition ..... | 5 |
+| 8.1 Security association identifier (SAI) ..... | 6 |
+| 8.2 Cryptographic parameters per security association..... | 6 |
+| 9 Structure of protected messages ..... | 6 |
+| 9.1 Security header ..... | 6 |
+| 9.2 Security payload ..... | 6 |
+| 9.3 Digital signature algorithms (DSA) signature algorithms..... | 7 |
+| 10 Signalling procedures ..... | 7 |
+| 10.1 TSa..... | 7 |
+| 10.2 Sa ..... | 10 |
+| 10.3 Sc ..... | 14 |
+| Annex A – List of verifiable CSP identifiers to be sent in the PEEC request ..... | 16 |
+| Annex B – ASN.1 format for signalling messages ..... | 18 |
+| Appendix I – Information validation techniques ..... | 20 |
+| Bibliography..... | 21 |
+
+
+
+# Recommendation ITU-T Q.3062
+
+# Signalling procedures and protocols for enabling interconnection between trustable network entities in support of existing and emerging networks
+
+# 1 Scope
+
+This Recommendation specifies signalling procedures and protocols involved in the application of the signalling requirements and architecture, as well as reference points TSa, Sa and Sc specified in [ITU-T Q.3057], for interconnection between trustable network entities (NEs) in support of existing and emerging networks.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T Q.3057] Recommendation ITU-T Q.3057 (2020), *Signalling requirements and architecture for interconnection between trustable network entities*.
+- [ITU-T X.509] Recommendation ITU-T X.509 (2019), *Information technology – Open Systems Interconnection – The Directory: Public-key and attribute certificate frameworks*.
+- [ITU-T X.510] Recommendation ITU-T X.510 (2020), *Information technology – Open Systems Interconnection – The Directory: Protocol specifications for secure operations*.
+- [FIPS PUB 140-2] Federal Information Processing Standards Publication FIPS PUB 140-2 (2001) + change notices (2002), *Security requirements for cryptographic modules*.
+- [FIPS PUB 186-4] Federal Information Processing Standards Publication FIPS PUB 186-4 (2013), *Digital signature standard (DSS)*.
+- [IETF RFC 4703] IETF RFC 4703 (2006), *Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host Configuration Protocol (DHCP) Clients*.
+- [NIST SP 800-57-3] NIST SP 800-57 Part 3 Rev.1 (2015), *Recommendation for Key Management – Part 3: Application-Specific Key Management Guidance*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 authority** [ITU-T X.509]: An entity, responsible for the issuance of certificates or of revocation lists.
+
+- 3.1.2 certification authority (CA)** [ITU-T X.509]: An authority trusted by one or more entities to create and digital sign public-key certificates. Optionally the certification authority may create the subjects' keys.
+- 3.1.3 cross-certificate** [ITU-T X.509]: A certification authority (CA) where the issuer and the subject are different CAs. CAs issue cross-certificates to other CAs as a mechanism to authorize the subject CA's existence.
+- 3.1.4 data integrity**: [b-ITU-T T.411] The property that data has not been altered or destroyed.
+- 3.1.5 data origin authentication** [b-ITU-T X.800]: The corroboration that the source of data received is as claimed.
+- 3.1.6 end-entity public-key certificate** [ITU-T X.509]: A public-key certificate issued to an entity, which then acts as an end entity within a public-key infrastructure.
+- 3.1.7 fully qualified domain name (FQDN)** [IETF RFC 4703]: Network entity address indicator on Internet protocol interconnect (IPX).
+- 3.1.8 global title (GT)** [b-ITU-T Q.1400]: This is addressing used by the SCCP, comprising dialed digits or another form of address that will not be recognized by the SS No. 7 network layer. Therefore, translation of this information to an SS No. 7 network address is necessary.
+- 3.1.9 hash function** [ITU-T X.509]: A (mathematical) function which maps data of arbitrary size into data of a fixed size called a digest.
+- 3.1.10 security domain** [ITU-T Q.3057]: A set of objects or entities of whose security policy can be administered by one organization.
+- 3.1.11 signalling security gateway (SSGW)** [ITU-T Q.3057]: An entity on the borders of the security domains that terminates and initiates secure native signalling/protocols, relays signalling traffic between security domains, configures security parameters or protocols and can perform a security policy management function.
+- 3.1.12 trust** [b-ITU-T X.1163]: The relationship between two entities where each one is certain that the other will behave exactly as it expects.
+- 3.1.13 trust anchor** [ITU-T X.509] An entity that is trusted by a relying party and used for validating public-key certificates.
+- 3.1.14 trusted signalling certification authority (TSCA)** [ITU-T Q.3057]: The root of trust for verifying digital signatures using the root certification authority (CA) model.
+
+## **3.2 Terms defined in this Recommendation**
+
+This Recommendation defines the following terms:
+
+- 3.2.1 local signalling security gateway**: A signalling security gateway (SSGW) that sends messages on behalf of a network entity within the same security domain towards another SSGW.
+- 3.2.2 peer signalling security gateway**: A signalling security gateway (SSGW) that receives messages on behalf of a network entity within the same security domain from another SSGW.
+- 3.2.3 provisional end entity public-key certificate (PEEC)**: A short-term end entity public-key certificate with a 6-month validity period.
+- 3.2.4 security association (SA)**: A logical connection created for security purposes. All traffic traversing an SA is provided with the same security protection. The SA specifies protection levels, algorithms to be used, lifetimes of the connection, etc.
+- 3.2.5 validated end entity public-key certificate (VEEC)**: A long-term end entity public-key certificate with a 2-year validity period.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|-------|----------------------------------------------------|
+| CA | Certification Authority |
+| CAP | Camel Application Part |
+| CSP | Communications Service Provider |
+| DoS | Denial of Service |
+| DS | Digital Signature |
+| DSA | Digital Signature Algorithm |
+| ECDSA | Elliptic Curve Digital Signature Algorithm |
+| EEC | End Entity public-key Certificate |
+| FQDN | Fully Qualified Domain Name |
+| GT | Global Title |
+| IE | Information Element |
+| IMS | IP Multimedia Subsystem |
+| IPX | Internet Protocol interconnect |
+| ISDN | Integrated Services Digital Network |
+| MAP | Mobile Application Part |
+| NE | Network Entity |
+| PEEC | Provisional End Entity public-key Certificate |
+| REST | Representational State Transfer |
+| SA | Security Association |
+| SAI | Security Association Identifier |
+| SCCP | Signalling Connection Control Part |
+| SGC | Signalling security Gateway public-key Certificate |
+| SIP | Session Initiation Protocol |
+| SS | Signalling System |
+| SS7 | Signalling System No. 7 |
+| SSGW | Signalling Security Gateway |
+| TSCA | Trusted Signalling Certification Authority |
+| TVP | Time Variant Parameter |
+| UTC | Coordinated Universal Time |
+| VEEC | Validated End Entity public-key Certificate |
+
+# 5 Conventions
+
+None.
+
+# 6 Architecture for interconnection between trustable network entities
+
+[ITU-T Q.3057] introduced a centralized trust anchor for issuing and verifying digital signatures in signalling interconnection. In cryptography, a certification authority (CA) is an entity that issues digital public-key certificates. A digital public-key certificate certifies the ownership of a public key by the named subject of the certificate. This allows others (relying parties) to rely upon signatures or on assertions made about the private key that corresponds to the certified public key. A CA acts as a trusted third party – trusted both by the subject (owner) of the public-key certificate and by the party relying upon it. The format of these public-key certificates is specified in [ITU-T X.509]. A CA can issue end-entity public-key certificates to each operator that is signed by the root public-key certificate, which is the topmost public-key certificate of the tree. In order to create a trustable interconnection between network entities, all operator end-entity public-key certificates need to be signed by the trust anchor (using the root public-key certificate), thus inheriting the trustworthiness of the trust anchor.
+
+Establishment of a trusted signalling certification authority (TSCA) as the trust anchor asserts control and traceability to the process of creating and signing digital public-key certificates.
+
+## 6.1 Reference architecture
+
+Figure 6-1 shows the reference architecture specified in [ITU-T Q.3057] for the interconnection between trustable network entities (NEs). This Recommendation specifies the signalling procedures for TSa, Sc and Sb interfaces.
+
+
+
+The diagram illustrates the reference architecture for interconnection between trustable network entities (NEs) across two security domains, A and B. At the top center is the Trusting Signalling Certification Authority (TSCA), represented by a cube icon with red arrows. It connects to the Signalling Security Gateways (SSGWs) in both domains via TSa interfaces. Security domain A (left) contains a Certification Authority (CA) represented by a server icon, which issues certificates to the SSGW and NEs via Sc interfaces. The SSGW in domain A connects to two NEs (represented by dashed boxes) via Sb interfaces. The CA also connects to the NEs via Sc interfaces. Security domain B (right) has a similar structure with its own CA, SSGW, and NEs. The SSGWs in domains A and B are interconnected via an Sd interface. The diagram is labeled Q.3062(22) in the bottom right corner.
+
+Figure 6-1: Reference architecture of interconnection between trustable network entities. The diagram shows two security domains, A and B, connected via a central TSCA (Trust Anchor). Domain A contains a CA (Certification Authority), two NEs (Network Entities), and an SSGW (Signalling Security Gateway). Domain B contains a CA, two NEs, and an SSGW. The TSCA is connected to the SSGWs in both domains via TSa interfaces. The CA in each domain is connected to the SSGW via Sc interfaces. The SSGW is connected to the NEs via Sb interfaces. The CA is also connected to the NEs via Sc interfaces. The SSGWs are connected to each other via an Sd interface. The diagram is labeled Q.3062(22) in the bottom right corner.
+
+Figure 6-1– Reference architecture of interconnection between trustable network entities
+
+### 6.2 Functional entities
+
+#### 6.2.1 Certification authority
+
+The CA issues digital public-key certificates for the signalling security gateway (SSGW) end entity. These digital public-key certificates contain a public key and the identity of the owner of the SSGWs/NEs within a particular security domain and are signed by the TSCA.
+
+#### **6.2.2 Trusted signalling certification authority**
+
+The TSCA is the trust anchor for the reference architecture; it functions in the same way as an Internet-based trust anchor providing services to the CAs in each security domain.
+
+#### **6.2.3 Signalling security gateway**
+
+The SSGW is an entity on the border of the security domain used for communication between two security domains. SSGW is responsible for whether protection is applied and enforces security policies towards the external domain.
+
+#### **6.2.4 Network entity**
+
+The NE is the origin or destination of the messages. It generates messages, such as those of the integrated services digital network (ISDN) user part or mobile application part types, and receives, interprets and processes those received.
+
+### **6.3 Reference points**
+
+#### **6.3.1 Sa reference point**
+
+The Sa reference point is located between an SSGW and a NE. This reference point provides security interconnection to support protection of the domain.
+
+#### **6.3.2 Sc reference point**
+
+The Sc reference point is located between an SSGW or NE and a CA. This reference point is for distribution and validation public-key certificates for the NE and SSGW.
+
+#### **6.3.3 TSa reference point**
+
+The Sa reference point is located between a CA that belongs to a Communications Service Provider's (CSP) security domain and the TSCA. This reference point issues digital public-key certificates to the CA by the TSCA.
+
+# **7 Security services**
+
+This Recommendation specifies the provision of the following security services:
+
+- signalling data integrity
+- signalling data origin authentication
+
+# **8 Security association attribute definition**
+
+The security association (SA) shall contain the following data elements that are classified into two groups.
+
+- Security association identifier (SAI) attributes.
+
+The SSGW of each security domain creates a SA for each SSGW from other security domains it interacts with. The SA identification is based on the peer SSGW ID. The SSGW shall keep only one SA per destination SSGW.
+
+- Assigned cryptographic parameters per SA: digital signature, key, algorithm identifiers (IDs) and SA lifetime.
+
+## **8.1 Security association identifier (SAI)**
+
+`Security Association Identifier = Local SSGW ID || Peer SSGW ID`
+
+where
+
+- Peer SSGW ID is either:
+
+- a) the global title (GT) of the peer SSGW on the SS7 network.
+- b) the peer SSGW fully qualified domain name (FQDN) (as defined in clause 3.1.7) on the Internet protocol interconnect (IPX) network.
+- Local SSGW ID is either:
+ - a) the GT of the local SSGW on the SS7 network.
+ - b) the local SSGW FQDN (as defined in clause 3.1.7) on the IPX network.
+
+## 8.2 Cryptographic parameters per security association
+
+A **digital signature algorithm (DSA) ID** identifies the DSA. The mode of operation of an algorithm is implicitly determined by the algorithm ID. Mapping of algorithm IDs is specified in clause 9.3.
+
+A **signalling security gateway public-key certificate (SGC)** contains the public-key certificate (public part) used to sign the signalling messages of a given SA. The host parameter of the public-key certificate is the security association identifier (SAI). The length of an SGC is determined according to the algorithm ID; key generation is determined according to the algorithm ID.
+
+The **SA expiry time** determines the actual expiry time of the SA. The expiry time shall be given in coordinated universal time (UTC) time with the format "YYYYMM-DDThh:mm:ssTZD" as specified in [b-W3C DTF].
+
+## 9 Structure of protected messages
+
+If a message does not require a digital signature (as indicated by the signalling procedure of the Sa reference point), then the message shall be routed unchanged to the NE by the SSGW (via the Sb reference point).
+
+If a message requires a signature, the SSGW adds a security header and security payload to the message. Both the security header and security payload are sent in cleartext.
+
+## 9.1 Security header
+
+Security Header = SAI || TVP
+
+where
+
+- SAI: see clause 8.1.
+- TVP: time variant parameter.
+
+The time variant parameter (TVP), used for replay protection of signed messages, is a 32-bit timestamp. The receiving SSGW accepts an operation only if the timestamp is within a certain time window. The resolution of the clock from which the timestamp is derived is 0.1 s. The size of the time-window at the receiving NE is not standardized.
+
+## 9.2 Security payload
+
+Security Payload = DS || EEC
+
+where
+
+- The digital signature (DS), bit-string of the DS, as specified in clause 6.2 of [ITU-T X.509], is the result of applying the DSA onto the signalling message sent to the SSGW by the NE (via the Sb reference point);
+- The end entity public-key certificate (EEC) as specified in clause 7.2 of [ITU-T X.509].
+
+## 9.3 Digital signature algorithms (DSA) signature algorithms
+
+This Recommendation specifies several DSAs that can be used to sign protected messages, each algorithm is designated as DSA-*x*, where *x* represents the ID of the DSA. Table 9-1 lists current usable DSAs.
+
+**Table 9-1 – Digital signature algorithms (DSAs) in this Recommendation**
+
+| DSA Identifier
DSA ID | Description | Notes |
+|--------------------------|---------------------------------------------------------------------------------|------------------|
+| 0 | No signature | |
+| 1 | Elliptic curve digital signature algorithm (ECDSA) p-384 curve with SHA256 hash | [FIPS PUB 186-4] |
+| 2 | Not assigned yet | |
+| 3 | Not assigned yet | |
+| 4 | Not assigned yet | |
+| 5 | Not assigned yet | |
+| 6 | Not assigned yet | |
+| ... | | |
+| 15 | Not assigned yet | |
+
+#### 9.3.1 Description of DSA-0
+
+When DSA-0 is selected, the security payload is omitted from the message.
+
+#### 9.3.2 Description of DSA-1
+
+The use of ECDSA (including key-pair generations) is specified in clause 6 of [FIPS PUB 186-4]. The point of the curve selected for ECDSA is p-384 and the hash function selected is SHA256.
+
+NOTE – In preparation of post-quantum cryptography, it is recommended to use (including key-pair generations) one of the NIST PQC third round candidates for DSA. Details of on-going work by NIST and the status of each of the submitted candidates can be found in [b-NIST-PQC], current PQC DSA leaders are: [b-Crystals], [b-Falcon] and [b-Rainbow].
+
+# 10 Signalling procedures
+
+### 10.1 TSa
+
+#### 10.1.1 Trusted signalling certification authority signalling procedures
+
+[ITU-T Q.3057] specifies the signalling procedure of the TSCA, shown in Figure 10-1.
+
+
+
+```
+
+graph TD
+ Begin([Begin]) --> CR{{Certification request}}
+ CR --> CRIE[Check required IEs]
+ CRIE --> RIP{Required IEs present}
+ RIP -- No --> RR((Reject request))
+ RIP -- Yes --> VRIE[Verify received IEs]
+ VRIE --> IEV{IEs verified}
+ IEV -- No --> RPC[Revoke provisional certificate]
+ IEV -- Yes --> IPC[Issue provisional certificate]
+ IPC --> MRC1{{Message to requesting CA}}
+ IPC --> VRI[Verify requestor identity]
+ VRI --> IV{Identity verified}
+ IV -- No --> RPC
+ IV -- Yes --> IFC[Issue full certificate]
+ IFC --> MRC2{{Message to requesting CA}}
+ RR --> Idle([Idle])
+ RPC --> Idle
+ IFC --> Idle
+
+```
+
+Q.3062(22)
+
+Flowchart of signalling procedures of a trusted signalling certification authority. The process starts with 'Begin', followed by 'Certification request', and 'Check required IEs'. A decision 'Required IEs present' follows. If 'No', it goes to 'Reject request'. If 'Yes', it goes to 'Verify received IEs'. Another decision 'IEs verified' follows. If 'No', it goes to 'Revoke provisional certificate'. If 'Yes', it goes to 'Issue provisional certificate' and 'Message to requesting CA', then to 'Verify requestor identity'. A decision 'Identity verified' follows. If 'No', it goes to 'Revoke provisional certificate'. If 'Yes', it goes to 'Issue full certificate' and 'Message to requesting CA'. All paths eventually lead to 'Idle'.
+
+**Figure 10-1 – Signalling procedures of a trusted signalling certification authority**
+
+#### 10.1.2 TSa signalling procedures
+
+##### *Introduction*
+
+Figure 10-2 describes the signalling flow between a CA of a CSP and the TSCA, interacting over the TSa reference point. The TSCA component that handles the public-key certificate generation is required to be in a high security zone, such as a secure alcove or trusted execution environment, as recommended by [FIPS PUB 140-2].
+
+
+
+```
+
+sequenceDiagram
+ participant CSP's CA
+ participant TSCA
+ participant Secure alcove
+ Note right of TSCA: 2. Verify identity information
+ CSP's CA->>TSCA: 1. Provisional certificate request
+ TSCA->>Secure alcove: 3. Generate EEC request
+ Secure alcove-->>TSCA: 4. EEC response
+ TSCA-->>CSP's CA: 5. Provisional certificate response
+ Note right of TSCA: 6. Verify identity information
+ TSCA-->>CSP's CA: 7. Validated certificate issuance
+ CSP's CA->>TSCA: 8. Validated certificate accept
+
+```
+
+Q.3062(22)
+
+Sequence diagram of the TSa signalling procedure. Lifelines: CSP's CA, TSCA, and Secure alcove. The sequence is: 1. Provisional certificate request (CSP's CA to TSCA); 2. Verify identity information (TSCA internal); 3. Generate EEC request (TSCA to Secure alcove); 4. EEC response (Secure alcove to TSCA); 5. Provisional certificate response (TSCA to CSP's CA); 6. Verify identity information (TSCA internal); 7. Validated certificate issuance (TSCA to CSP's CA); 8. Validated certificate accept (CSP's CA to TSCA).
+
+**Figure 10-2 – TSa signalling procedure**
+
+##### *Description*
+
+The CA of each CSP holds the EEC for the security domain of an operator, an EEC can become invalid for these reasons:
+
+- a) the validity date of the EEC has expired;
+- b) the TSCA has revoked the EEC validity;
+- c) the private key of the EEC is compromised or lost.
+
+When the EEC of a CSA becomes invalid, the CA requests a new EEC from the TSCA using the following procedure:
+
+- 1 The requesting CA of a CSP sends a secure provisional end entity public-key certificate (PEEC) request to the TSCA via the relevant medium connecting the CA to the TSCA (either the IPX or the Internet). In the provisional PEEC request the CSP will include its identity information, which the TSCA will verify in order to provision the PEEC (a list of such IDs can be found in Annex A).
+- 2 Once the TSCA receives the provisional PEEC request from the CA of a CSP, it validates the attached identity information (see Appendix I).
+- 3 Once the identity information has been validated, the TSCA sends its secure alcove a request to generate an EEC based on the realm FQDN of the CSP. If the identity information sent by the CSP fails to verify, then steps 3 and 4 are omitted.
+- 4 The secure alcove returns an ITU-T X.509 EEC signed by the TSCA private-key, the end-entity is denoted the realm FQDN of the CSP.
+- 5 The TSCA sends the CA the signed EEC in the provisional public-key certificate response.
+- 6 The TSCA validates the identity information with the validation process specified in Appendix I.
+
+- 7 Once validated, the TSCA issues a validated end entity public-key certificate (VEEC) to the CA.
+- 8 The CA acknowledges the receipt of the VEEC and begins using it to sign SAs.
+
+#### **10.1.3 TSa messages**
+
+- The provisional EEC request is sent over a hypertext transfer protocol secure-based representational state transfer (REST) API and contains all information specified in Annex A as electronic documents attached to the request.
+- The provisional EEC response and VEEC issuance response are sent to the requesting CSP via email with the EEC securely attached as specified in [NIST SP 800-57-3].
+
+## **10.2 Sa**
+
+#### **10.2.1 Signalling security gateway signalling procedures**
+
+[ITU-T Q.3057] specifies the signalling procedure of the SSGW reference point, as shown in Figure 10-3.
+
+
+
+```
+
+graph TD
+ Begin([Begin]) --> Signalling[Signalling message]
+ Signalling --> Check[Check origin and destination]
+ Check --> Inbound[Inbound-outside to inside]
+ Check --> Outbound[Outbound-inside to outside]
+ Check --> Outside[Outside to outside]
+
+ Inbound --> Sig1{Message contains signature}
+ Sig1 -- No --> Allowed1{Is it allowed according to the security policy?}
+ Allowed1 -- No --> Block((Block))
+ Allowed1 -- Yes --> Verify1{Verify signature and data}
+ Verify1 -- No --> Remove[Remove signature]
+ Remove --> Message1{{Message}}
+ Verify1 -- Yes --> Message1
+
+ Outbound --> Sig2{Message contains signature}
+ Sig2 -- No --> Needed2{Signature is needed according to the security policy?}
+ Needed2 -- Yes --> Signature[Signature]
+ Signature --> Message2{{Message}}
+ Needed2 -- No --> Message2
+
+ Outside --> Message2
+
+ Message1 --> Idle([Idle])
+ Message2 --> Idle
+ Block --> Idle
+
+```
+
+Q.3062(22)
+
+Flowchart of Signalling procedures of SSGW. The process starts with 'Begin', followed by 'Signalling message', and 'Check origin and destination'. It then branches into three paths: 'Inbound-outside to inside', 'Outbound-inside to outside', and 'Outside to outside'. Each path has decision diamonds for 'Message contains signature', 'Is it allowed according to the security policy?', 'Verify signature and data', and 'Signature is needed according to the security policy'. The 'Inbound-outside to inside' path includes a 'Remove signature' step. All paths lead to 'Message', 'Block', or 'Idle' states. A small note 'Q.3062(22)' is in the bottom right.
+
+**Figure 10-3 – Signalling procedures of SSGW**
+
+#### 10.2.2 Sa signalling procedures
+
+##### 10.2.2.1 Sa signalling happy flow
+
+###### *Introduction*
+
+Figure 10-4 describes the happy signalling flow between two SSGWs in two different security domains interacting over the Sa reference point. Happy flow is a successful signalling message traversal between SSGWs due to successful validation of the digital signature.
+
+
+
+```
+
+sequenceDiagram
+ participant NE-A
+ participant SA-A as SA storage
+ participant Local-SSGW as Local SSGW
+ participant Peer-SSGW as Peer SSGW
+ participant SA-B as SA storage
+ participant NE-B
+
+ Note over NE-A, Local-SSGW: Security domain A
+ Note over Peer-SSGW, NE-B: Security domain B
+
+ NE-A->>Local-SSGW: 1. Signalling message
+ Local-SSGW->>SA-A: 2. Query SA
+ SA-A-->>Local-SSGW: 2. SA
+ rect rgb(240, 240, 240)
+ Note right of Local-SSGW: 3. Sign message
+ end
+ Local-SSGW->>Peer-SSGW: 4. Security header || Security payload || Signalling message
+ Peer-SSGW->>SA-B: 5. Query SA
+ SA-B-->>Peer-SSGW: 5. SA
+ rect rgb(240, 240, 240)
+ Note right of Peer-SSGW: 6. Validate signature
+ end
+ Peer-SSGW->>NE-B: 7. Signalling message
+
+```
+
+The diagram illustrates the 'Happy flow' of the Sa signalling procedure. It is divided into two security domains: Security domain A and Security domain B. In Security domain A, an originating Network Element (NE-A) sends a '1. Signalling message' to the 'Local SSGW'. The Local SSGW then sends a '2. Query SA' to its 'SA storage', which returns the '2. SA'. The Local SSGW then performs a '3. Sign message' operation. It then sends a combined '4. Security header || Security payload || Signalling message' to the 'Peer SSGW' in Security domain B. The Peer SSGW sends a '5. Query SA' to its 'SA storage', which returns the '5. SA'. The Peer SSGW then performs a '6. Validate signature' operation. Finally, it sends the '7. Signalling message' to the terminating Network Element (NE-B). The diagram is labeled 'Q.3062(22)' at the bottom right.
+
+Sequence diagram of the Sa signalling procedure – Happy flow between Security domain A and Security domain B.
+
+**Figure 10-4 – Sa signalling procedure – Happy flow**
+
+##### *Description*
+
+- 1 An originating NE in security domain A (denoted NE-A) initiates a signalling message to a terminating NE in security domain B (denoted as NE-B). NE-A sends the signalling message to the security domain A SSGW (denoted local SSGW-A).
+- 2 Local SSGW-A (the originating SSGW) queries its internal SA storage with the SAI (derived from the destination address of the signalling message of NE-A) to retrieve the SA of the destination SSGW (denoted peer SSGW-B).
+ - If there is no SA for the SSGW-B, then local SSGW-A contacts the CA to generate a new SA according to the security policy (specified in the signalling procedures of the Sc reference point)
+- 3 SSGW-A applies the DSA to the received signalling message according to the DSA ID of the SA and attaches the security header and payload (if applicable) to the signalling message received from NE-A.
+- 4 The SSGW sends the combined signalling message to the local SSGW. The local SSGW sends the combined signalling message to the peer SSGW via the relevant medium (i.e., SS No. 7 or IPX).
+- 5 The peer SSGW (terminating SSGW) receives a signed message from the local SSGW with a security header that includes the SAI. The peer SSGW-B retrieves the SA according to the SAI from its internal storage.
+ - If there is no SA for the local SSGW, then the peer SSGW contacts the CA to generate a new SA according to the security policy (specified in the signalling procedures of the Sc reference point).
+
+- 6 The peer SSGW validates the digital signature found in the security payload of the received message (if DSA-0 is specified as the DSA ID in the SA, then no payload is present).
+- 7 If the signature is valid, the peer SSGW then removes the security header and payload (if present) from the signalling message and forwards it to the terminating NE.
+
+#### 10.2.2.2 Sa signalling unhappy flow
+
+###### Introduction
+
+Figure 10-5 shows unhappy signalling flow between two SSGWs in two different security domains interacting over the Sa reference point. Unhappy flow is a failed signalling message traversal between the SSGWs due to failure in digital signature validation.
+
+
+
+```
+
+sequenceDiagram
+ participant NE-A
+ participant SA_storage_A as SA storage
+ participant Local_SSGW as Local SSGW
+ participant Peer_SSGW as Peer SSGW
+ participant SA_storage_B as SA storage
+ participant NE-B
+
+ Note over NE-A, Local_SSGW: Security domain A
+ Note over Peer_SSGW, NE-B: Security domain B
+
+ NE-A->>Local_SSGW: 1. Signalling message
+ Local_SSGW->>SA_storage_A: 2. Query SA
+ SA_storage_A-->>Local_SSGW: 2. SA
+ rect rgb(240, 240, 240)
+ Note right of Local_SSGW: 3. Sign
+message
+ end
+ Local_SSGW->>Peer_SSGW: 4. Security header || Security payload || Signalling message
+ Peer_SSGW->>SA_storage_B: 5. Query SA
+ SA_storage_B-->>Peer_SSGW: 5. SA
+ rect rgb(240, 240, 240)
+ Note right of Peer_SSGW: 6. Validate
+signature
+ end
+ Peer_SSGW->>NE-B: 7. Signalling message
+
+```
+
+The diagram illustrates the 'Unhappy flow' of the Sa signalling procedure. It is divided into two security domains: Security domain A and Security domain B. In Security domain A, an originating Network Element (NE-A) sends a '1. Signalling message' to its Local SSGW. The Local SSGW then queries its 'SA storage' for the Security Association (SA) using '2. Query SA'. The SA storage responds with '2. SA'. The Local SSGW then performs an internal step '3. Sign message'. It then forwards a combined message '4. Security header || Security payload || Signalling message' to the Peer SSGW in Security domain B. The Peer SSGW queries its own 'SA storage' with '5. Query SA' and receives '5. SA'. It then performs '6. Validate signature'. Finally, it forwards the '7. Signalling message' to the terminating NE-B. A small label 'Q.3062(22)' is present at the bottom right of the diagram.
+
+Sequence diagram of Sa signalling procedure - Unhappy flow between Security domain A and Security domain B.
+
+**Figure 10-5 – Sa signalling procedure – Unhappy flow**
+
+###### Description
+
+- 1 An originating NE in security domain A (denoted NE-A) initiates a signalling message to a terminating NE in security domain B (denoted NE-B). NE-A sends the signalling message to the SSGW of security domain A (denoted local SSGW).
+- 2 Local SSGW (the originating SSGW) queries its internal SA storage with the SAI (derived from the destination address of the signalling message of NE-A) to retrieve the SA of the destination SSGW (denoted peer SSGW).
+ - If there is no SA for the peer SSGW, then the local SSGW contacts the CA to generate a new SA according to the security policy (specified in the signalling procedures of the Sc reference point).
+- 3 The local SSGW applies the DSA to the received signalling message according to the DSA ID of the SA and attaches the security header and payload (if applicable) to the
+
+signalling message received from NE-A and sends the signalling message to the peer SSGW via the relevant medium (i.e., SS7 or IPX).
+
+- 4 The peer SSGW (terminating SSGW) receives a signed message from local SSGW with a security header that includes the SAI. Peer SSGW retrieves the SA according to the SAI from its internal storage.
+ - If there is no SA for the local SSGW, then the peer SSGW contacts the CA to generate a new SA according to the security policy (specified in the signalling procedures of the Sc reference point).
+- 5 The peer SSGW fails to validate the digital signature found in the security payload of the received message, i.e., the signature validation process fails, because it does not match the SAI.
+- 6 The peer SSGW (terminating) sends a signature validation failure message to the local SSGW (originating), announcing that peer SSGW has blocked the signalling message via the relevant medium (i.e., SS7 or IPX).
+- 7 The local SSGW (originating) sends NE-A (originating) an origination failure message via the Sb reference point.
+
+#### 10.2.3 Sa messages ASN.1 format
+
+See Annex B for the ASN.1 schema.
+
+### 10.3 Sc
+
+[ITU-T Q.3057] specifies high-level functions of the CA:
+
+- public key infrastructure key-pair provisioning
+- build CA certification path
+
+#### 10.3.1 Sc signalling procedures
+
+##### *Introduction*
+
+Figure 10-6 describes the signalling flow between the SSGW and the CA in the same security domain, interacting over the Sc reference point. The SSGW requests a new SA from the CA if it does not have a valid SA for the inbound or outbound SAI in its internal storage.
+
+
+
+```
+
+sequenceDiagram
+ participant PeerSSGW as Peer SSGW
+ participant NE-A as NE-A
+ participant LocalSSGW as Local SSGW
+ participant CA-A as Peer CA-A
+
+ Note left of PeerSSGW: Security domain B
+ Note right of LocalSSGW: Security domain A
+
+ PeerSSGW->>LocalSSGW: 1a. Inbound signalling message
+ NE-A->>LocalSSGW: 1b. Outbound signalling message
+ LocalSSGW->>LocalSSGW: 2. Query SA storage
+ LocalSSGW->>CA-A: 3. Issue SA request
+ Note right of CA-A: 4. Generate new SA
+ CA-A->>LocalSSGW: 5. Issue SA response
+
+```
+
+Q.3062(22)
+
+Sequence diagram of Sc signalling procedure between Security domain B and Security domain A. The diagram shows five steps: 1a. Inbound signalling message from Peer SSGW to Local SSGW; 1b. Outbound signalling message from NE-A to Local SSGW; 2. Query SA storage from Local SSGW; 3. Issue SA request from Local SSGW to Peer CA-A; 4. Generate new SA (internal step for CA-A); 5. Issue SA response from Peer CA-A to Local SSGW. A dashed line separates Security domain B (left) and Security domain A (right).
+
+**Figure 10-6 – Sc signalling procedure**
+
+##### *Description*
+
+- 1 (a) A peer SSGW from another security domain sends an inbound signalling message that contains a security payload.
+ (b) An internal NE sends the SSGW an outbound signalling message addressed to another security domain.
+- 2 The query of the local SSGW to its internal SA storage for the relevant SA (as described in clause 10.2.2) comes up empty, i.e., there is no valid SA for the relevant SAI, thus a new one needs to be created.
+- 3 The local SSGW sends an issue SA request to the CA.
+- 4 The CA uses its EEC (provisional or validated) to generate a new SA that contains an SAI specific public-key certificate, which corresponds to the security realm FQDN or SS7 GT address of domain B.
+- 5 The CA sends the generated SA back to the local SSGW to sign and verify signalling messages to or from security domain B.
+
+#### **10.3.2 Sc messages ASN.1 format**
+
+See Annex B for the ASN.1 schema.
+
+## Annex A
+
+### List of verifiable CSP identifiers to be sent in the PEEC request
+
+(This annex forms an integral part of this Recommendation.)
+
+This Recommendation seeks to use already established and field proven models for its processes. Thus, reference is drawn from the extended verification certification process for SSL public-key certificates issuance ratified by the CA/Browser Forum [b-EV-Cert]. For the TSCA to issue a provisional PEEC to the requesting CSP, the following information must be sent by the SCP to the TSCA:
+
+- 1 Include all information about the applicant in the EEC.
+- 2 The applicant information shall include, but is not limited to, the following details:
+ - a) Organization name. Include the formal legal organization name of the applicant in the EEC, as recorded with the incorporating or registration agency in the applicant's jurisdiction of incorporation or registration (for private organizations), or as specified in the law of the political subdivision in which the government entity operates (for government entities), or as registered with the government business registration agency (for business entities).
+ - b) Assumed name (optional). Include the assumed name (e.g., "doing business as" appellation) of the applicant in the EEC, as recorded in the jurisdiction of Applicant's place of business, if requested by the applicant.
+ - c) Security domain name (FQDN). Include the domain name(s) of the applicant in the EEC.
+ - d) Jurisdiction of incorporation or registration. Include the jurisdiction of incorporation or registration of the applicant in the EEC, consisting of:
+ - a city or town (if any).
+ - b state or province (if any).
+ - c country.
+ - e) Incorporating or registration agency. Include the name of applicant's incorporating or registration agency in the EEC.
+ - f) Registration number. Include the registration number assigned to the applicant by the incorporating or registration agency in the jurisdiction of incorporation or registration of the applicant in the EEC. If the incorporating or registration agency does not issue registration numbers, then the date of incorporation or registration shall be recorded.
+ - g) Applicant address. Include the address of the place of business of the applicant in the EEC, including:
+ - i) building number and street
+ - ii) city or town
+ - iii) state or province (if any)
+ - iv) country
+ - v) postal code (zip code)
+ - vi) main telephone number
+
+- h) Public-key certificate requester. Include the name and contact information of the public-key certificate requester submitting the EEC request on behalf of the applicant.
+
+3 The applicant agreement includes the following elements.
+
+- a) **General.** Prior to the issuance of the EEC, the TSCA obtains the agreement of the applicant to a legally enforceable applicant agreement with the TSCA for the express benefit of relying parties and application software vendors. The applicant agreement must be signed by an authorized contract signer acting on behalf of the applicant in accordance with local or peer SSGW law and must apply to the EEC to be issued pursuant to the EEC request. A separate applicant agreement may be used for each EEC request, or a single applicant agreement may be used to cover multiple future EEC requests and resulting EEC(s), so long as each EEC that the TSCA issues to the applicant is clearly covered by an applicant agreement signed by an authorized contract signer acting on behalf of the applicant.
+- b) **Agreement requirements.** The applicant agreement must, at a minimum, specifically name both the applicant and the individual contract signer signing the agreement on behalf of the applicant and contain provisions imposing on the applicant the following obligations and warranties:
+ - i) **Accuracy of information:** An obligation and warranty to provide accurate and complete information at all times to the TSCA, both in the EEC request and as otherwise requested by the TSCA in connection with the issuance of the EEC(s) to be supplied by the TSCA.
+ - ii) **Protection of private key.** An obligation and warranty by the applicant or a subcontractor (e.g., hosting provider) to take all reasonable measures to maintain sole control of, keep confidential and properly protect at all times the private key that corresponds to the public key to be included in the requested EEC(s) (and any associated access information or device, e.g., password or token).
+ - iii) **Acceptance of EEC.** An obligation and warranty that it will not install and use the EEC(s) until it has reviewed and verified the accuracy of the data in each EEC.
+ - iv) **Use of EEC.** An obligation and warranty to install the EEC only on a SSGW accessible at the security domain name listed on the EEC and to use the EEC solely in compliance with all applicable laws, solely for signalling and solely in accordance with the applicant agreement
+ - v) **Reporting and revocation.** Upon compromise, an obligation and warranty to promptly cease using an EEC and its associated private key, and promptly request the TSCA to revoke the EEC, if:
+ - any information in the EEC is or becomes incorrect or inaccurate, or there is any actual or suspected misuse or compromise of the private key of the applicant associated with the public key listed in the EEC
+ - vi) **Termination of use of EEC.** An obligation and warranty to promptly cease all use of the private key corresponding to the public key listed in an EEC upon expiration or revocation of that EEC.
+ - vii) Appendix I – Information validation techniques
+
+## Annex B
+
+### ASN.1 format for signalling messages
+
+(This annex forms an integral part of this Recommendation.)
+
+```
+ProTrustSchema {itu-t recommendation q 3062
+ protrustschema(1)} DEFINITIONS AUTOMATIC TAGS ::= BEGIN
+IMPORTS
+
+ -- from Rec. ITU-T X.509 | ISO/IEC 9594-8
+ AlgorithmIdentifier{}, SIGNATURE{}, SIGNED
+ FROM AuthenticationFramework authenticationFramework
+
+ -- from Rec. ITU-T X.520 | ISO/IEC 9594-6
+ UniqueIdentifier
+ FROM SelectedAttributeTypes selectedAttributeTypes;
+
+SaSignallingMessage ::= SEQUENCE {
+ SecurityHeader SEQUENCE {
+ sai SEQUENCE {
+ localSsgwId UTF8String,
+ peerSsgwId UTF8String,
+ tvp UTF8String
+ },
+ securityPayload SEQUENCE {
+ digitalSignature SIGNATURE,
+ eec UTF8String
+ }
+ }
+}
+
+Sc_IssueCAreqs ::= SEQUENCE {
+ sai SEQUENCE {
+ localSsgwId UTF8String,
+ peerSsgwId UTF8String,
+ tvp UTF8String
+ }
+}
+
+Sc_IssueCAresponds ::= SEQUENCE {
+ securityAssociationIdentifier SEQUENCE {
+ dsa INTEGER (0..15),
+ sgc Certificate,
+ expiryTime UTCTime
+ }
+}
+
+/* The following ASN.1 data type specifies the syntax of public-key certificates which is
+defined in 7.2.1 of [ITU-T X.509]. */
+
+Certificate ::= SIGNED{TBSCertificate}
+
+TBSCertificate ::= SEQUENCE {
+ version [0] Version DEFAULT v1,
+ serialNumber CertificateSerialNumber,
+ signature AlgorithmIdentifier{{SupportedAlgorithms}},
+ issuer Name,
+ validity Validity,
+ subject Name,
+ subjectPublicKeyInfo SubjectPublicKeyInfo,
+ issuerUniqueIdentifier [1] IMPLICIT UniqueIdentifier OPTIONAL,
+ ...
+ [[2: -- if present, version shall be v2 or v3
+ subjectUniqueIdentifier [2] IMPLICIT UniqueIdentifier OPTIONAL]],
+ [[3: -- if present, version shall be v2 or v3
+ extensions [3] Extensions OPTIONAL]]
+}
+
+Version ::= INTEGER {v1(0), v2(1), v3(2)}
+```
+
+```
+
+CertificateSerialNumber ::= INTEGER
+
+Validity ::= SEQUENCE {
+ notBefore Time,
+ notAfter Time,
+ ... }
+
+SubjectPublicKeyInfo ::= SEQUENCE {
+ algorithm AlgorithmIdentifier{{SupportedAlgorithms}},
+ subjectPublicKey BIT STRING,
+ ... }
+
+Time ::= CHOICE {
+ utcTime UTCTime,
+ generalizedTime GeneralizedTime }
+
+Extensions ::= SEQUENCE SIZE (1..MAX) OF Extension
+
+Extension ::= SEQUENCE {
+ extnId EXTENSION.&id({ExtensionSet}),
+ critical BOOLEAN DEFAULT FALSE,
+ extnValue OCTET STRING
+ (CONTAINING EXTENSION.&ExtnType({ExtensionSet}{@extnId})
+ ENCODED BY der),
+ ... }
+
+der OBJECT IDENTIFIER ::=
+ {joint-iso-itu-t asnl(1) ber-derived(2) distinguished-encoding(1)}
+
+ExtensionSet EXTENSION ::= {...}
+
+Name ::= UTF8String
+END
+
+```
+
+## **Appendix I**
+
+### **Information validation techniques**
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Information validation techniques are listed in section F, pp. 16-39 of [b-EV-Cert]
+
+## Bibliography
+
+- [b-ITU-T Q.1400] Recommendation ITU-T Q.1400 (1993), *Architecture framework for the development of signalling and OA&M protocols using OSI concepts*.
+- [b-ITU-T T.411] Recommendation ITU-T T.411 (1993), *Information technology – Open document architecture (ODA) and interchange format: Introduction and general principles*.
+- [b-ITU-T X.800] Recommendation ITU-T X.800 (1991), *Security architecture for Open Systems Interconnection for CCITT applications*.
+- [b-ITU-T X.1163] Recommendation ITU-T X.1163 (2015), *Security requirements and mechanisms of peer-to-peer-based telecommunication networks*.
+- [b-Crystals] Crystals Team (2022), *Crystals: Cryptographic suite for algebraic lattices*. Available [2022-06-04] at:
+- [b-EV-Cert] CA/Browser Forum (2007), *Guidelines for the issuance and management of extended validation public-key certificates*, version 1.0. 78 pp. Available [viewed 2022-06-03] at: [https://cabforum.org/wp-content/uploads/EV\\_Certificate\\_Guidelines.pdf](https://cabforum.org/wp-content/uploads/EV_Certificate_Guidelines.pdf)
+- [b-Falcon] Fouque, P.-A., Hoffstein, J., Kirchner, P., Lyubashevsky, V., Pornin, T., Prest, T., Riccosset, T., Seiler, G., Whyte, W., Zhang, Z. (2017), *Falcon: Fast-Fourier lattice-based compact signatures over NTRU*. Available [2022-06-04] at:
+- [b-NIST-PQC] Computer Security Resource Center (Internet), *Post-quantum cryptography – PQC – Round 3 submissions*. Gaithersburg, MD: National Institute of Standards and Technology. Available [2022-06-04] at:
+- [b-Rainbow] Rainbow Team (Internet), *PQCRainbow: Rainbow signature: One of the three post-quantum signature NIST finalists*. Available [2022-06-04] at:
+- [b-W3C DTF] W3C (1998), *Date and time formats*. Boston, MA: World Wide Web Consortium. Available [2022-06-04] at:
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling, and associated measurements and tests |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a
--- /dev/null
+++ b/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8f24b214263bab4142643453a604fb5196f9397e2500c675cde79d53ce5e5d8e
+size 3645
diff --git a/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..16aaad88c6c7d66433be057b7d328ae189189efd
--- /dev/null
+++ b/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b8f01d08ab346924d17844ec13caf2cdef26de8d2122a9cdd002dacfd054a4d0
+size 253568
diff --git a/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b45a6fc7a5ff40cb96ba302f5e8293007cc74dd6
--- /dev/null
+++ b/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:71793afc94e90f135db2bcd498a9ad27749f49c7d5ba88b9a207c864d32f95de
+size 133212
diff --git a/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9b235d738a02b531771db5a138e4fe1564af1d40
--- /dev/null
+++ b/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:32af13b76a4b72c95edd11e33826b8e473b8453f558cea85210370357c9af7ac
+size 254403
diff --git a/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9d788da9dcc95a4f49828c86427652293ae49953
--- /dev/null
+++ b/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ccbf8c79b006abb7917f2c7806f7af1e6139779b63237b3a65cb2da532148d1f
+size 83239
diff --git a/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9f391d78a7e16911cf7d7820d3fd42e8d0e300ff
--- /dev/null
+++ b/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b431a04946fc24c5d8709fd4199989b7b930b97c368ec1a554111078e40dfca1
+size 37791
diff --git a/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a993e0464bc285569a2074a3e6d5a26c4ae8524f
--- /dev/null
+++ b/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a3c85ca60490dbeffda96fe5581a34ca1411e8bb7579b696d4a8c7c4f51e1205
+size 65132
diff --git a/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..50d023c4f2f04cf0d9dc9a060dd59375194e420b
--- /dev/null
+++ b/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:843fea21ed1ee5d1910c39159910a7ee4119e7a49238dd3cc42c3959121cd61b
+size 42663
diff --git a/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c8876445fd1698afd9f75cf427456bb8c2c8de49
--- /dev/null
+++ b/marked/Q/T-REC-Q.3202.1-200805-I_PDF-E/raw.md
@@ -0,0 +1,560 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.3202.1**
+
+(05/2008)
+
+# **SERIES Q: SWITCHING AND SIGNALLING**
+
+Signalling requirements and protocols for the NGN –
+Signalling and control requirements and protocols to
+support attachment in NGN environments
+
+## --- **Authentication protocols based on EAP-AKA for interworking among 3GPP, WiMax, and WLAN in NGN**
+
+Recommendation ITU-T Q.3202.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.3999 |
+| General | Q.3000–Q.3029 |
+| Network signalling and control functional architecture | Q.3030–Q.3099 |
+| Network data organization within the NGN | Q.3100–Q.3129 |
+| Bearer control signalling | Q.3130–Q.3179 |
+| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 |
+| Resource control protocols | Q.3300–Q.3369 |
+| Service and session control protocols | Q.3400–Q.3499 |
+| Service and session control protocols – supplementary services | Q.3600–Q.3649 |
+| NGN applications | Q.3700–Q.3849 |
+| Testing for NGN networks | Q.3900–Q.3999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+### **Recommendation ITU-T Q.3202.1**
+
+### **Authentication protocols based on EAP-AKA for interworking among 3GPP, WiMax, and WLAN in NGN**
+
+## **Summary**
+
+In Recommendation ITU-T Q.3202.1, a couple of authentication protocols for heterogeneous access authentication are discussed. 3GPP has standardized the 3GPP system-based EAP-AKA for interworking 3GPP and WLAN networks. The WiMax or WLAN device requires an external UICC reader for applying the current EAP-AKA defined in 3GPP TS 33.234. This Recommendation proposes to apply the EAP-AKA protocol to non-3GPP network devices not equipped with UICC for interworking among 3GPP, WiMax, and WLAN in NGN.
+
+###### **Source**
+
+Recommendation ITU-T Q.3202.1 was approved on 22 May 2008 by ITU-T Study Group 11 (2005-2008) under Recommendation ITU-T A.8 procedure.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+### NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2009
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## CONTENTS
+
+| | Page |
+|------------------------------------------------------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 1.1 Relationship ..... | 1 |
+| 2 References..... | 1 |
+| 3 Abbreviations..... | 1 |
+| 4 Security Requirements for Authentication Interworking ..... | 2 |
+| 5 Network architecture for access authentication interworking in NGN ..... | 3 |
+| 6 Authentication protocols based on EAP-AKA for heterogeneous access authentication..... | 5 |
+| 7 Security considerations..... | 5 |
+| Appendix I – Example authentication in heterogeneous environments..... | 7 |
+| I.1 Example using EAP-AKA with UICC authentication mechanism ..... | 7 |
+| I.2 Example using EAP-AKA based on a password and the Diffie-Hellman algorithm..... | 10 |
+| I.3 Example of fast re-authentication procedure..... | 14 |
+| Bibliography ..... | 16 |
+
+
+
+## Recommendation ITU-T Q.3202.1
+
+### Authentication protocols based on EAP-AKA for interworking among 3GPP, WiMax, and WLAN in NGN
+
+# 1 Scope
+
+This Recommendation describes the authentication protocol based on the EAP-AKA for interworking 3GPP, WiMax [b-IEEE 802.16e], and WLAN [b-IEEE 802.11] access in NGN. 3GPP has standardized the 3GPP system-based EAP-AKA for interworking 3GPP and WLAN networks. The WiMax or WLAN device, however, requires an external UICC reader. Without UICC, the EAP-AKA mechanism loses its own advantages in security and portability aspects. This Recommendation proposes a modified version of the EAP-AKA protocol for extending its usage to existing WiMax/WLAN devices. In this Recommendation, two EAP-AKA full authentication protocols are described and proposed. Also, the fast re-authentication procedure of EAP-AKA is described.
+
+### 1.1 Relationship
+
+Work for this Recommendation is based upon the context of [ITU-T Q.3201]. This Recommendation complies with the EAP-based security signalling architecture for network attachment in [ITU-T Q.3201], and considers the compatibility with the functional architecture in [ITU-T Y.2012].
+
+This Recommendation refers to [ETSI TS 133 234] for authentication protocol based on EAP-AKA with UICC and fast re-authentication procedure.
+
+## 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.3201] Recommendation ITU-T Q.3201 (2007), *EAP-based security signalling protocol architecture for network attachment*.
+- [ITU-T Y.2012] Recommendation ITU-T Y.2012 (2006), *Functional requirements and architecture of the NGN Release 1*.
+- [ETSI TS 133 102] ETSI TS 133 102 (2006), *Universal Mobile Telecommunications System (UMTS); 3G security; Security architecture (3GPP TS 33.102 version 7.1.0 Release 7)*. <[http://webapp.etsi.org/workprogram/Report\\_WorkItem.asp?WKI\\_ID=25801](http://webapp.etsi.org/workprogram/Report_WorkItem.asp?WKI_ID=25801)>
+- [ETSI TS 133 234] ETSI TS 133 234 (2007), *Universal Mobile Telecommunications System (UMTS); 3G security; Wireless Local Area Network (WLAN) interworking security (3GPP TS 33.234 version 7.5.0 Release 7)*. <[http://webapp.etsi.org/workprogram/Report\\_WorkItem.asp?WKI\\_ID=27022](http://webapp.etsi.org/workprogram/Report_WorkItem.asp?WKI_ID=27022)>
+
+## 3 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+AAA Authentication, Authorization and Accounting
+
+| | |
+|--------|--------------------------------------------------------------|
+| ACR | Access Control Router |
+| AK | Authentication Key |
+| AKA | Authentication and Key Agreement |
+| AM-FE | Access Management Functional Entity |
+| AS | Authentication Server |
+| AV | Authentication Vector |
+| CK | Confidentiality Key |
+| DH | Diffie-Hellman |
+| EAP | Extensible Authentication Protocol |
+| EP | Enforcement Point |
+| GGSN | Gateway GPRS Support Node |
+| ID | IDentity |
+| IK | Integrity Key |
+| IMSI | International Mobile Subscriber Identity |
+| MAC | Message Authentication Code |
+| NACF | Network Attachment Control Functions |
+| RAS | Radio Access Station |
+| SGSN | Serving GPRS Support Node |
+| TAA-FE | Transport Authentication and Authorization Functional Entity |
+| TUP-FE | Transport User Profile Functional Entity |
+| UE | User Equipment |
+| UICC | UMTS IC Card |
+| USIM | Universal Subscriber Identity Module |
+| UTRAN | UMTS Terrestrial Radio Access Network |
+| VPLMN | Visited Public Land Mobile Network |
+| WAG | Wireless Access Gateway |
+| WiMax | Worldwide Interoperability for Microwave Access |
+| WLAN | Wireless Local Area Network |
+
+## 4 Security Requirements for Authentication Interworking
+
+- The EAP-AKA authentication protocol shall be applied easily to any mobile networks in NGN.
+ - Mobile terminals equipped with UICC
+ - Mobile terminals not equipped with UICC
+- Authentication mechanisms in NGN shall include mutual authentication and key agreement.
+- The key distribution and freshness for protecting signalling and user data on the wireless link shall be supported.
+
+- Authentication protocols shall be secure against several attacks:
+ - Man-in-the-middle attack (MITM)
+ - Replay attack
+ - Impersonation attack
+ - Forgery attack
+ - Dictionary attack
+ - Eavesdropping
+- A full re-authentication procedure shall be supported.
+- A fast re-authentication procedure may be supported.
+
+## 5 Network architecture for access authentication interworking in NGN
+
+This clause describes the network model for access authentications interworking among the 3GPP, WiMax, and WLAN in NGN. There are two approaches. One approach is to apply WLAN authentication model based on the 3GPP system, defined in [ETSI TS 133 234], for heterogeneous access authentication. Figure 1 shows the 3GPP system-based authentication.
+
+
+
+Figure 1 – 3GPP system-based authentication model. The diagram shows a WLAN UE connected to a WLAN Access Network. The WLAN Access Network is connected to an Intranet/Internet cloud and to a 3GPP Home Network. The 3GPP Home Network contains several entities: SLF, HSS, HLR, 3GPP AAA Server, CGW/CC F, OCS, WAG, PDG, and Wi. The 3GPP AAA Server is connected to the WLAN Access Network via a 'Wa' interface. The 3GPP AAA Server is also connected to the SLF via a 'Dw' interface, to the HSS via a 'Wx' interface, to the HLR via a 'D/Gf' interface, to the CGW/CC F via a 'Wf' interface, to the OCS via a 'Wo' interface, to the WAG via a 'Wg' interface, and to the PDG via a 'Wm' interface. The WAG is connected to the PDG via a 'Wp' interface. The PDG is connected to the Wi interface. A 'Wu' interface is shown between the WLAN UE and the 3GPP Home Network.
+
+**Figure 1 – 3GPP system-based authentication model**
+
+The other proposal is the authentication model, based on the function entities of NGN, as shown in Figure 2. The network architecture might be classified into four components of NGN: AR-FE, AM-FE, TAA-FE, and TUP-FE. This Recommendation describes signalling protocols for access authentication in this architecture. Also, the signalling protocols based on authentication model specified in [ITU-T Q.3201] are provided. Figures 3 and 4 show an integrated authentication model defined in [ITU-T Q.3201].
+
+
+
+Figure 2: An example authentication architecture for interworking among wireless access networks in NGN. The diagram shows four layers: Intranet / Internet (top), Authentication Server (TUP-FE/TAA-FE), Authenticator (AM-FE), and EP (AR-FE). Below these are three parallel paths for 3GPP, WiMax, and WLAN. Each path contains a Home Network (with HSS/HLR and AAA Server/Proxy), an Authenticator (GGSN/SGSN, ACR, or AR), a Link Access Network, and a Peer (UE).
+
+**Figure 2 – An example authentication architecture for interworking among wireless access networks in NGN**
+
+Figure 3 shows an integrated authentication model, which is being controlled by an authenticator. The peer sends authentication information to the enforcement point, and the enforcement points forward it to the authenticator. This architecture helps the authenticator manage the authentication procedure.
+
+
+
+Figure 3: Integrated authentication model. The diagram shows three Peers connected to three Enforcement points (EP). Each EP is connected to a central Authenticator. The Authenticator is connected to an Authentication server (AS). Dashed lines represent authentication control, and solid lines represent media. The text 'Q.3202.1(08)\_F03' is in the bottom right.
+
+**Figure 3 – Integrated authentication model**
+
+Figure 4 illustrates an integrated authentication model in NGN. It is assumed that the network attachment control function entities are the authenticator (AM-FE) and authentication server (TUP-FE/TAA-FE), and the AR-FE in access transport acts as the enforcement point. The AR-FE performs filtering data packet allowing only the authenticated packets. After successful authentication of the end-user function, the access transport allows the packets from the end-user function to be entered into the access network.
+
+
+
+Figure 4: An example of an integrated authentication model in NGN. The diagram shows a 'Transport stratum' (yellow box) containing 'NACF' (green box) and 'Access Transport' (blue box). NACF contains 'TUP-FE/TAA-FE (AS)' and 'AM-FE (Authenticator)'. Access Transport contains 'AR-FE (EP)', 'AN-FE', 'ED-FE', and 'Access Packet Transport Functions'. 'End-User Functions (Peer)' (pink box) is connected to 'AR-FE'. 'RACF' (white box) is connected to 'NACF' and 'Core Transport' (white box). 'Core Transport' is connected to 'Other Networks' (white box). A legend at the bottom indicates that solid lines represent 'Authentication Control'.
+
+**Figure 4 – An example of an integrated authentication model in NGN**
+
+## 6 Authentication protocols based on EAP-AKA for heterogeneous access authentication
+
+The authentication protocols based on EAP-AKA for heterogeneous access authentication are shown in Appendix I. Appendix I describes how three authentication protocols based on EAP-AKA, two EAP-AKA authentication protocols for interworking authentication in wireless access (e.g., 3GPP, [b-IEEE 802.16e], and [b-IEEE 802.11]) and the fast re-authentication procedure of the EAP-AKA in NGN, could be used to provide authentication in heterogeneous access network. The existing EAP-AKA with UICC is basically used for access authentication mechanism in 3GPP, WiMax, and WLAN networks. This scheme requires that the WiMax or WLAN UE should be equipped with UICC card for access authentication. To solve this problem, this Recommendation proposes an access authentication scheme without UICC: EAP-AKA based on a password. The EAP-AKA based on a password provides access authentication for the UE without UICC. The UE equipped with the AKA algorithm uses Diffie-Hellman key instead of the long-term secret key stored in UICC.
+
+## 7 Security considerations
+
+Since the 3GPP system-based EAP-AKA uses a long-term key shared between the UICC and HSS/HLR, it can provide strong security and portability. Compared to the 3GPP system-based EAP-AKA, the proposed EAP-AKA based on non-UICC can also provide robust and enhanced security functions.
+
+The dictionary attack in authentication protocol based on a password is the most critical attack. In the proposed protocol with non-UICC, it is impossible for an attacker to guess a legitimate password by obtaining public values during authentication session. The password in the authentication messages is protected against dictionary attack owing to the one-way hash function, random numbers, and discrete logarithm problem (DLP).
+
+The perfect forward secrecy (PFS) and perfect backward secrecy (PBS) are very important security requirements, which mean that disclosure of a long-term key in the EAP-AKA should not reveal all the previous and upcoming communications. If an attacker gets a UICC, the attacker can disclose a long-term key by a physical access to the storage medium, which means that PFS and PBS are not provided. The EAP-AKA with non-UICC, however, provides PFS and PBS because the DH session
+
+key is changed whenever the authentication procedure for generating a set of AVs is performed. In other words, it uses a short-term key.
+
+The proposed EAP-AKA with non-UICC is secure against replay attack because DH private keys are changed every authentication procedure. Also, it can protect the UE and the TAA-FE against MITM attack using a password.
+
+## Appendix I
+
+### Example authentication in heterogeneous environments
+
+(This appendix does not form an integral part of this Recommendation)
+
+This appendix describes how two EAP-AKA authentication protocols and a fast re-authentication procedure could be used to provide authentication when heterogeneous accesses are used.
+
+### I.1 Example using EAP-AKA with UICC authentication mechanism
+
+The EAP-AKA [b-IETF RFC 4187] authentication scheme for interworking between the 3GPP and WLAN is specified in [ETSI TS 133 234]. This clause shows that this mechanism is also used in the WiMax technology for interworking between the 3GPP and WLAN terminals. The complete operation is defined in [b-IETF RFC 4187].
+
+Operational steps of the EAP-AKA with UICC:
+
+1. The control channel between the UE and access network functions is established (out of the scope of this Recommendation).
+2. The AR-FE notifies the AM-FE that the control channel is established between the UE and access network functions.
+3. The AM-FE sends an EAP Request/Identity message to the UE.
+4. The UE responds with an EAP Response/Identity including NAI based on a pseudonym or IMSI.
+
+The EAP message is routed towards the UE's AAA server based on the realm part of the NAI. The EAP message may be passed by one or several AAA proxies. The TAA-FE acts as an AAA server.
+
+5. The communication between the AM-FE and TAA-FE may be achieved using the AAA protocol, such as Diameter [b-IETF RFC 3588] and [b-IETF RFC 4072] or Radius [b-IETF RFC 3579] and [b-IETF RFC 2865]. The AM-FE may act as an AAA client and the TAA-FE may act as an AAA server. The AM-FE generates a diameter AVP including the EAP payload and forwards the diameter message to the TAA-FE. Upon receiving the message, the TAA-FE retrieves the EAP Response/Identity message including the user identity, identifier of the access network, and VPLMN identity from the received diameter message.
+
+NOTE – This Recommendation omits AAA communication between the AM-FE and TAA-FE to simplify description.
+
+6. The TAA-FE identifies the subscriber, and then checks whether it has unused AV for the subscriber or not. If not, the TAA-FE retrieves a set of new AVs from the TUP-FE.
+7. The TAA-FE sends an EAP Request/AKA-Identity again to the UE in order to request the subscriber identity. There exist some situations that intermediate nodes between the UE and the TAA-FE may have revised or replaced the user's identity received in the EAP Response/Identity message, as specified in [ETSI TS 133 234]. For the reason, this procedure may be performed. The service operator, however, can omit this new request if there exists the assurance that the user identity is not changed or modified by some reasons during EAP-AKA procedure.
+8. The AM-FE sends the EAP Request/AKA-Identity to the AR-FE, and the AR-FE forwards the message to the UE.
+9. The UE responds to the new request with the same identity. The AR-FE forwards the EAP Response/AKA-Identity including the same identity to the AM-FE.
+
+10. The AM-FE sends the message to the TAA-FE. If the identity in the two messages of the EAP Response/Identity and EAP Response/AKA-Identity is the same, the TAA-FE will use the AV for authentication process. Otherwise, the TAA-FE shall repeat step 6 before step 11.
+11. The TAA-FE checks whether it has the access network profile of the subscriber or not. If not, the TAA-FE retrieves the profile from the TUP-FE. The TAA-FE verifies whether or not the user is authorized to utilize the network service.
+12. The TAA-FE derives new keying materials required by the EAP-AKA from IK and CK, see [ETSI TS 133 234]. Also, some additional keying materials may be generated for message confidentiality and/or integrity in the WiMax or WLAN environment.
+13. The TAA-FE sends the EAP Request/AKA-Challenge that contains the RAND, AUTN, and MAC value to the AM-FE. The MAC is computed by using the new keying material derived from IK and CK. If two user identities, such as pseudonym and re-authentication identifier, are generated, they are also transferred securely to the AR-FE. The re-authentication identifier depends on whether the network operator allows the UE to perform re-authentication process in the access network or not. The TAA-FE may send a result indication to the UE. It also depends on the home operator's policies.
+14. The AM-FE sends the EAP Request/AKA-Challenge message to the AR-FE, and the AR-FE forwards the message to the UE.
+15. The UE performs the UMTS algorithm on the UICC. The UICC verifies the received AUTN to authenticate the network. If it is successful, the UICC computes RES, IK, and CK based on a long-term key. The UE derives new keying material from the new IK and CK, and then verifies the received MAC using the new derived keys. If the UE received a protected pseudonym and(or) re-authentication identity, it stores the received identity for future authentication.
+16. The UE computes a new MAC value with the new derived key, and then sends the EAP Response/AKA-Challenge including the computed RES and the new MAC to the AR-FE. The UE may send a result indication to the TAA-FE if it received the result indication from the TAA-FE. It also depends on the home operator's policies. The AR-FE forwards the messages to the AM-FE.
+17. The AM-FE forwards the EAP Response/AKA-Challenge message to the TAA-FE.
+18. The TAA-FE verifies the received MAC, and then compares the XRES with the received RES.
+19. If all validation is successful, the TAA-FE sends the EAP Request/AKA-Notification that notifies the success of the authentication to the UE. This notification can be protected by using a MAC.
+20. The AM-FE sends the EAP message to the AR-FE, and it forwards the EAP message to the UE.
+21. The UE sends the EAP Response/AKA-Notification to the AM-FE through the AR-FE.
+22. The AM-FE sends the EAP Response/AKA-Notification to the TAA-FE.
+23. The TAA-FE sends the EAP Success with keying material for providing message confidentiality and/or integrity in the WiMax or WLAN to the AM-FE.
+24. The AM-FE sends the EAP Success to the AR-FE. The AR-FE stores the keying material. In future, the keying material is used to communicate with the UE.
+25. The AR-FE informs the UE that its authentication and key distribution have been successful and complete.
+26. The user channel is established between the UE and AN. The UE can access the network such as the 3GPP, WiMax, and WLAN.
+
+
+
+```
+
+sequenceDiagram
+ participant UE as End-User Functions
+ participant AR-FE
+ participant AM-FE
+ participant TAA-FE
+ participant TUP-FE
+
+ Note right of AR-FE: Transport Stratum
+ Note right of AM-FE: NACF
+
+ Note left of UE: 1. Control channel is established between UE and AN
+ UE->>AR-FE: 2. Notify connection setup
+ AR-FE->>AM-FE: 3. EAP Request/Identity
+ AM-FE->>UE: 4. EAP Response/Identity (NAI based on a pseudonym or IMSI)
+ Note right of AM-FE: The EAP message is routed towards the proper AAA server (the realm part of the NAI)
+ AM-FE->>TAA-FE: 5. EAP Response/Identity (NAI based on a pseudonym or IMSI)
+ Note right of TAA-FE: 6. Identify the subscriber
+ TAA-FE->>AM-FE: 7. EAP Request/AKA-Identity (Any identity)
+ AM-FE->>UE: 8. EAP Request/AKA-Identity (Any identity)
+ UE->>AM-FE: 9. EAP Response/AKA-Identity (Identity)
+ AM-FE->>TAA-FE: 10. EAP Response/AKA-Identity (Identity)
+ Note right of TAA-FE: 11. Check WiMax/WLAN access profile of the subscriber
+ Note right of TAA-FE: 12. New keying material is derived from the IK and CK
+ TAA-FE->>AM-FE: 13. EAP Request/AKA-Challenge (RAND, AUTN, MAC, Protected {pseudoym, Next re-auth id}, Result ind)
+ AM-FE->>UE: 14. EAP Request/AKA-Challenge (RAND, AUTN, MAC, Protected {pseudoym, Next re-auth id}, Result ind)
+ Note left of UE: 15. UE runs UMTS algorithm on the USIM
+ UE->>AM-FE: 16. EAP Response/AKA-Challenge (RES, MAC, Result ind)
+ AM-FE->>TAA-FE: 17. EAP Response/AKA-Challenge (RES, MAC, Result ind)
+ Note right of TAA-FE: 18. Verify the received MAC and compares XRES with the received RES
+ TAA-FE->>AM-FE: 19. EAP Request/AKA-Notification (Success notification)
+ AM-FE->>UE: 20. EAP Request/AKA-Notification (Success notification)
+ UE->>AM-FE: 21. EAP Response/AKA-Notification
+ AM-FE->>TAA-FE: 22. EAP Response/AKA-Notification
+ TAA-FE->>AM-FE: 23. EAP Success (keying material)
+ AM-FE->>UE: 24. EAP Success (keying material)
+ UE->>AR-FE: 25. EAP Success
+ Note left of UE: 26. User channel is established between UE and AN
+
+```
+
+Sequence diagram of the EAP-AKA authentication protocol in NGN. Lifelines: End-User Functions, AR-FE, AM-FE, TAA-FE, TUP-FE. The Transport Stratum contains AR-FE. The NACF contains AM-FE, TAA-FE, and TUP-FE. The sequence shows 26 steps of message exchange between the UE (via End-User Functions) and the network elements (AR-FE, AM-FE, TAA-FE, TUP-FE) for authentication and key derivation.
+
+Figure I.1 – Authentication protocol based on EAP-AKA scheme with UICC in NGN
+
+### I.2 Example using EAP-AKA based on a password and the Diffie-Hellman algorithm
+
+This clause proposes an access authentication protocol which uses a non-UICC authentication mechanism. Specifically, the example uses EAP-AKA based on a password and Diffie-Hellman (DH) key exchange algorithm among 3GPP, WiMax, and WLAN terminals. The proposed scheme can be used for legacy terminals with and without UICC. The legacy terminals only require an AKA algorithm based on a software module. Therefore, this authentication mechanism does not use a long-term secret key in UICC but a DH key generated through the authentication procedure. 3GPP AKA functions $f_1$ , $f_1^*$ , $f_2$ , $f_3$ , $f_4$ , $f_5$ , and $f_5^*$ used in this mechanism are the same as EAP-AKA with UICC.
+
+Operational steps of the EAP-AKA with non-UICC:
+
+1. The control channel between the UE and access network functions is established (out of the scope of this Recommendation).
+2. The AR-FE notifies the AM-FE that the control channel is established between the UE and access network functions.
+3. The AM-FE sends an EAP Request/Identity message to the UE.
+4. The UE responds with an EAP Response/Identity including NAI based on a pseudonym or IMSI.
+
+The EAP message is routed towards the UE's AAA server based on the realm part of the NAI. The EAP message may be passed by one or several AAA proxies. The TAA-FE acts as an AAA server.
+
+5. The communication between the AM-FE and TAA-FE may be achieved using the AAA protocol, such as Diameter [b-IETF RFC 3588] and [b-IETF RFC 4072] or Radius [b-IETF RFC 3579] and [b-IETF RFC 2865]. The AM-FE may act as an AAA client and the TAA-FE may act as an AAA server. The AM-FE generates a diameter AVP including the EAP payload and forwards the diameter message to the TAA-FE. Upon receiving the message, the TAA-FE retrieves the EAP Response/Identity message including the user identity, identifier of the access network, and VPLMN identity from the received diameter message.
+
+NOTE – This Recommendation omits AAA communication between the AM-FE and TAA-FE to simplify description.
+
+6. The TAA-FE identifies the subscriber, and then checks whether it has unused AVs for the subscriber or not. If not, the TAA-FE retrieves a set of new AVs from the TUP-FE. The new AV will be calculated after receiving the DH value of the UE (step 10).
+
+In the EAP-AKA with non-UICC, the TUP-FE should store user's password verifier $g^{pwd}$ , where *pwd* is the user's password.
+
+7. The TAA-FE sends an EAP Request/AKA-Identity again to the UE in order to request the subscriber identity. There exist some situations that intermediate nodes between the UE and the TAA-FE may have revised or replaced the user's identity received in the EAP Response/Identity message, as specified in [ETSI TS 133 234]. For the reason, this procedure may be performed. The service operator, however, can omit this new request if there exists assurance that the user identity is not changed or modified by some reasons during EAP-AKA procedure.
+8. The AM-FE sends the EAP Request/AKA-Identity to the AR-FE, and it forwards the message to the UE.
+9. The UE without UICC generates a DH value $g^{(x+pwd)} \bmod p$ , where the $p$ is a large prime number, the $g$ is primitive root modular $p$ , the $x$ is a random number, the expression " $^$ " is exponent operation, and the expression " $\bmod$ " is modular operation. For a simple expression, this recommendation omits the expression " $\bmod p$ " (e.g., not " $g^{(x+pwd)} \bmod$
+
+$p''$ but " $g^{(x+pwd)}$ "). The UE also computes the value $H(g^{pwd}, g^x || Identity)$ , where $H()$ is one-way hash function, such as SHA-1 and $||$ is concatenation. The UE responds with the new request EAP Response/AKA-Identity including the computed values and the same identity. The AR-FE forwards the EAP Response/AKA-Identity to the AM-FE.
+
+10. The AM-FE sends the message to the TAA-FE. If the identity in the two messages of the EAP Response/Identity and EAP Response/AKA-Identity is the same, the TAA-FE will use the AV for authentication process. Otherwise, the TAA-FE shall repeat step 6 before step 11.
+11. The TAA-FE checks that it has the access network profile of the subscriber. If not, the TAA-FE retrieves the profile from the TUP-FE. The TAA-FE verifies whether or not the user is authorized to utilize the network service.
+
+The TUP-FE creates the AKA values based on the password and DH algorithm. The TUP-FE generates a value $g^x$ by computing $g^{(x+pwd)}/g^{pwd}$ and verifies the received hash value $H(g^{pwd}, g^x || Identity)$ . If it is successful, the TUP-FE generates a random value $y$ and computes a DH value $g^y$ and $g^{xy}$ . Finally, the TUP-FE runs 3GPP AKA functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ , and $f5^*$ with the DH session key $g^{(xy)}$ to generate a new AV. The TUP-FE distributes the new AV to the TAA-FE.
+
+12. The TAA-FE derives new keying materials required by the EAP-AKA from IK and CK, see [ETSI TS 133 234]. Also, some additional keying materials may be generated for message confidentiality and/or integrity in the WiMax or WLAN environment.
+13. The TAA-FE sends the EAP Request/AKA-Challenge that contains the RAND, AUTN, and MAC value to the AM-FE. The MAC is computed by using the new keying material derived from IK and CK. If two user identities, such as pseudonym and re-authentication identifier, are generated, they are also transferred securely to the AR-FE. The re-authentication identifier depends on whether network operator allows the UE to perform re-authentication process in the access network or not. The TAA-FE may send a result indication to the UE. It also depends on the home operator's policies.
+
+In the EAP-AKA with non-UICC, the TAA-FE also sends the values $g^{(y+pwd)}$ and $H(g^{pwd}, g^y || Identity)$ to the UE.
+
+14. The AM-FE sends the EAP Request/AKA-Challenge message to the AR-FE, and it forwards the message to the UE.
+15. The UE retrieves a value $g^y$ by computing $g^{(y+pwd)}/g^{pwd}$ and verifies the received hash value $H(g^{pwd}, g^y || Identity)$ . If it is successful, the UE generates the DH session key $g^{(xy)}$ . The UE performs AKA algorithm to generate an AV using the DH session key instead of a long-term key. The UE verifies the received AUTN to authenticate the network. The UE derives new keying material from the new IK and CK, and then verifies the received MAC using the new derived keys. If the UE receives a protected pseudonym and(or) re-authentication identity, it stores the received identity for future authentication.
+16. The UE computes a new MAC value with the new derived keys, and then sends the EAP Response/AKA-Challenge, including the computed RES and the new MAC to the AR-FE. The UE may send a result indication to the TAA-FE if it received the result indication from the TAA-FE. It also depends on the home operator's policies. The AR-FE forwards the message to the AM-FE.
+17. The AM-FE sends the EAP Response/AKA-Challenge message to the TAA-FE server.
+18. The TAA-FE verifies the received MAC, and then compares the XRES with the received RES.
+19. If all validation is successful, the TAA-FE sends the EAP Request/AKA-Notification that notifies the success of authentication to the UE. This notification can be protected by using a MAC.
+
+20. The AM-FE sends the EAP message to the AR-FE, and it forwards the EAP message to the UE.
+21. The UE sends the EAP Response/AKA-Notification to the AM-FE through the AR-FE.
+22. The AM-FE sends the EAP Response/AKA-Notification to the TAA-FE.
+23. The TAA-FE sends the EAP Success with keying material for providing message confidentiality and/or integrity in the WiMax or WLAN to the AM-FE.
+24. The AM-FE sends the EAP Success to the AR-FE. The AR-FE stores the keying material. In future, the keying material is used to communicate with the UE.
+25. The AR-FE informs the UE that its authentication and key distribution have been successful and complete.
+26. The user channel is established between the UE and AN. The UE can access the network such as the 3GPP, WiMax, and WLAN.
+
+
+
+```
+
+sequenceDiagram
+ participant EUF as End-User Functions
+ participant AR as AR-FE
+ participant AM as AM-FE
+ participant TAA as TAA-FE
+ participant TUP as TUP-FE
+
+ Note over AR: Transport Stratum
+ Note over AM, TUP: NACF
+
+ Note left of EUF: 1. Control channel is established
+between UE and AN
+ AR->>AM: 2. Notify connection setup
+ AM->>AR: 3. EAP Request/Identity
+ AR->>EUF: 4. EAP Response/Identity
+(NAI based on a pseudonym or IMSI)
+ Note over AR, AM: The EAP message is routed towards the
+proper AAA server (the realm part of the NAI)
+ AR->>AM: 5. EAP Response/Identity
+(NAI based on a pseudonym or IMSI)
+ Note right of TAA: 6. Identify the subscriber
+ TAA->>AM: 7. EAP Request/AKA-Identity
+(Any identity)
+ AM->>AR: 8. EAP Request/AKA-Identity
+(Any identity)
+ AR->>EUF: 9. EAP Response/AKA-Identity
+(Identity, $g^{x+pwd}$ , $H(g^{pwd}, g^x || ID)$ )
+ EUF->>AR: 10. EAP Response/AKA-Identity
+(Identity, $g^{x+pwd}$ , $H(g^{pwd}, g^x || ID)$ )
+ Note right of TAA: 11. Check 3GPP/WiMax/WLAN
+access profile of the subscriber
+and generate AV
+ Note right of TAA: 12. New keying material is
+derived from the IK and CK
+ TAA->>AM: 13. EAP Request/AKA-Challenge
+(RAND, AUTN, MAC, Protected {pseudonym, Next re-auth id},
+Result ind, $g^{y+pwd}$ , $H(g^{pwd}, g^y)$ )
+ AM->>AR: 14. EAP Request/AKA-Challenge
+(RAND, AUTN, MAC, Protected {pseudonym,
+Next re-auth id}, Result ind, $g^{y+pwd}$ , $H(g^{pwd}, g^y)$ )
+ Note left of EUF: 15. UE runs AKA algorithm
+using the DH session key
+ EUF->>AR: 16. EAP Response/AKA-Challenge
+(RES, MAC, Result ind)
+ AR->>AM: 17. EAP Response/AKA-Challenge
+(RES, MAC, Result ind)
+ Note right of TAA: 18. Verify the received MAC and
+compares XRES with the
+received RES
+ TAA->>AM: 19. EAP Request/AKA-Notification
+(Success notification)
+ AM->>AR: 20. EAP Request/AKA-Notification
+(Success notification)
+ AR->>EUF: 21. EAP Response/AKA-Notification
+ EUF->>AR: 22. EAP Response/AKA-Notification
+ TAA->>AM: 23. EAP Success (keying material)
+ AM->>AR: 24. EAP Success (keying material)
+ AR->>EUF: 25. EAP Success
+ Note left of EUF: 26. User channel is established
+between UE and AN
+
+```
+
+Sequence diagram of the EAP-AKA authentication protocol for non-UICC in NGN. The diagram shows interactions between End-User Functions, AR-FE, AM-FE, TAA-FE, and TUP-FE. The Transport Stratum includes AR-FE, and the NACF includes AM-FE, TAA-FE, and TUP-FE. The process involves connection setup, identity exchange, subscriber identification, challenge-response authentication, and final keying material exchange.
+
+**Figure I.2 – Authentication protocol based on EAP-AKA scheme with non-UICC in NGN**
+
+### **I.3 Example of fast re-authentication procedure**
+
+The fast re-authentication mechanism for interworking between the 3GPP and WLAN terminals is described in [ETSI TS 133 234]. This clause shows that this mechanism is also used in the EAP-AKA based on non-UICC. Since the fast re-authentication procedure is performed by reusing keys generated from previous authentication process, the fast re-authentication procedure of the two EAP-AKA protocols is the same. The complete operation is defined in [b-IETF RFC 4187]. This clause shows how the procedure could work in NGN.
+
+Operational steps of the EAP-AKA fast re-authentication:
+
+1. The AM-FE sends an EAP Request/Identity message to the UE.
+2. The UE responds with an EAP Response/Identity message including re-auth. id that is previously obtained from the TAA-FE during a full EAP-AKA authentication procedure.
+3. The AM-FE sends an EAP Response/Identity message to the TAA-FE.
+
+NOTE – This Recommendation omits AAA communication between the AM-FE and TAA-FE to simplify description.
+
+4. Upon receiving the message, the TAA-FE sends EAP Request/AKA-Re-authentication message to the AM-FE. This message contains the Counter, the Nonce, the MAC, the protected re-authentication id for the next fast re-authentication procedure, and the Result indication to protect the success result message at the end of the process. If the TAA-FE cannot deliver a re-auth. id, the UE shall force a full EAP-AKA authentication procedure. The protection of the result message depends on the network operator's policies.
+5. The AM-FE forwards EAP Request/AKA-Re-authentication message to the UE.
+6. The UE checks that the Counter is fresh and the MAC value is correct, and then sends the EAP Response/AKA-Re-authentication message to the AM-FE. This message contains the same Counter value and a calculated MAC. If the UE receives the same result indication from the TAA-FE, it shall include the result indication in this message. Otherwise, the UE shall ignore this indication.
+7. The AM-FE sends the EAP Response/AKA-Re-authentication message to the TAA-FE.
+8. If the TAA-FE requested to use protected Result Indications in the previous steps, the TAA-FE verifies whether or not the received Counter value is the same value as it was sent before, and the MAC is correct. And then, it sends the EAP Request/AKA-Notification message to AM-FE. This message contains the protected MAC and an encrypted copy of the Counter.
+9. The AM-FE forwards the EAP Request/AKA-Notification message to the UE.
+10. The UE sends the EAP Response/AKA-Notification message to the AM-FE.
+11. The AM-FE forwards the EAP Response/AKA-Notification message to the TAA-FE.
+12. The TAA-FE sends an EAP Success message to the UE. If some additional keying materials were generated for protecting signalling and user data in access link, then the TAA-FE delivers the keying material embedded in the RADIUS or Diameter messages to the AR-FE. The AR-FE stores the keying material to be used in communication with the authenticated UE.
+13. The AR-FE forwards the EAP Success message to the UE except the keying material.
+
+
+
+```
+
+sequenceDiagram
+ participant End-User Functions
+ participant AR-FE
+ participant AM-FE
+ participant TAA-FE
+ participant TUP-FE
+
+ Note right of AR-FE: Transport Stratum
+ Note right of AM-FE: NACF
+
+ AR-FE->>End-User Functions: 1. EAP Request/Identity
+ End-User Functions-->>AM-FE: 2. EAP Response/Identity (re-auth. id)
+ AM-FE->>TAA-FE: 3. EAP Response/Identity (re-auth. id)
+ TAA-FE->>AM-FE: 4. EAP Request/AKA-Reauthentication (Counter, Nonce, MAC, Protected Next re-auth. Id, Result ind)
+ AM-FE->>End-User Functions: 5. EAP Request/AKA-Reauthentication (Counter, Nonce, MAC, Protected Next re-auth. Id, Result ind)
+ End-User Functions-->>AM-FE: 6. EAP Response/AKA-Reauthentication (Counter, MAC, Result ind)
+ AM-FE->>TAA-FE: 7. EAP Response/AKA-Reauthentication (Counter, MAC, Result ind)
+ TAA-FE->>AM-FE: 8. EAP Request/AKA-Notification (Success notification, Counter)
+ AM-FE->>End-User Functions: 9. EAP Request/AKA-Notification (Success notification, Counter)
+ End-User Functions-->>AM-FE: 10. EAP Response/AKA-Notification
+ AM-FE->>TAA-FE: 11. EAP Response/AKA-Notification
+ TAA-FE->>AR-FE: 12. EAP Success (keying material)
+ AR-FE->>End-User Functions: 13. EAP Success
+
+```
+
+Sequence diagram of the Fast re-authentication procedure of the EAP-AKA protocol in NGN. The diagram shows interactions between End-User Functions, AR-FE, AM-FE, TAA-FE, and TUP-FE. The Transport Stratum includes AR-FE, and the NACF includes AM-FE, TAA-FE, and TUP-FE.
+
+Figure I.3 – Fast re-authentication procedure of the EAP-AKA protocol in NGN
+
+## Bibliography
+
+- [b-IEEE 802.11] IEEE 802.11-2007, *IEEE Standard for information technology – Telecommunications and information exchange between systems – local and metropolitan area networks – Specific requirements – Part 11: Wireless LAN Medium Access Control (MAC) and Physical layer (PHY) Specifications.*
+- [b-IEEE 802.16e] IEEE 802.16e-2005 and 802.16/Cor1 Part 16: *Amendment for Physical and Medium Access Control layers for combined Fixed and Mobile Operation.*
+- [b-IETF RFC 2865] IETF RFC 2865 (2000), *Remote Authentication Dial In User Service (RADIUS).*
+- [b-IETF RFC 3579] IETF RFC 3579 (2003), *RADIUS (Remote Authentication Dial In User Service) Support for Extensible Authentication Protocol (EAP).*
+- [b-IETF RFC 3588] IETF RFC 3588 (2003), *Diameter Base Protocol.*
+- [b-IETF RFC 3748] IETF RFC 3748 (2004), *Extensible Authentication Protocol (EAP).*
+- [b-IETF RFC 4072] IETF RFC 4072 (2005), *Diameter Extensible Authentication Protocol (EAP) Application.*
+- [b-IETF RFC 4187] IETF RFC 4187 (2006), *Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA).*
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|---------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3228-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3228-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bd7c24e83d75a6b1baa7fb4210f76345166390c9
--- /dev/null
+++ b/marked/Q/T-REC-Q.3228-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5866ab521163bd4f911ae6e27d0a1cf1f491c665e9b87b7d7076098a143f4bff
+size 3944
diff --git a/marked/Q/T-REC-Q.3228-201608-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Q/T-REC-Q.3228-201608-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..03dee167d29a4834c2b8ede3c7df28a0e26f63a5
--- /dev/null
+++ b/marked/Q/T-REC-Q.3228-201608-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a18134ea39cc6e37c89d37199bde7470d01f52e9c8f31d208c8686d1c5ae61b0
+size 71361
diff --git a/marked/Q/T-REC-Q.3228-201608-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Q/T-REC-Q.3228-201608-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c92f96a5ebc2d06ad1f75dde1d436ac34906429e
--- /dev/null
+++ b/marked/Q/T-REC-Q.3228-201608-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2c31e5289ba5c32ce32f6641f35905d920e29806b493ce075d57937bed1b55a
+size 17105
diff --git a/marked/Q/T-REC-Q.3228-201608-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3228-201608-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..0b4c2a234f066c84b3c57992b4f87c6c99847628
--- /dev/null
+++ b/marked/Q/T-REC-Q.3228-201608-I_PDF-E/raw.md
@@ -0,0 +1,734 @@
+
+
+**ITU-T**
+
+**Q.3228**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(08/2016)
+
+SERIES Q: SWITCHING AND SIGNALLING, AND
+ASSOCIATED MEASUREMENTS AND TESTS
+
+Signalling requirements and protocols for the NGN –
+Signalling and control requirements and protocols to
+support attachment in NGN environments
+
+---
+
+**Signalling requirements and protocol at the M1
+interface between the transport location
+management physical entity and the mobile
+location management physical entity (P)**
+
+Recommendation ITU-T Q.3228
+
+# 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 |
+| General | Q.3000–Q.3029 |
+| Network signalling and control functional architecture | Q.3030–Q.3099 |
+| Network data organization within the NGN | Q.3100–Q.3129 |
+| Bearer control signalling | Q.3130–Q.3179 |
+| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 |
+| Resource control protocols | Q.3300–Q.3369 |
+| Service and session control protocols | Q.3400–Q.3499 |
+| Service and session control protocols – supplementary services | Q.3600–Q.3616 |
+| Service and session control protocols – supplementary services based on SIP-IMS | Q.3617–Q.3639 |
+| NGN applications | Q.3700–Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## Recommendation ITU-T Q.3228
+
+# Signalling requirements and protocol at the M1 interface between the transport location management physical entity and the mobile location management physical entity (P)
+
+## Summary
+
+Recommendation ITU-T Q.3228 provides the protocol for the interface between the TLM-PE of the NACE and the MLM-PE (P) of the MMCE. M1 interface allows distribution of information from the TLM-PE to the MLM-PE (P). This Recommendation supports information flows across the M1 reference point as specified in Recommendation ITU-T Y.2018.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.3228 | 2016-08-29 | 11 | 11.1002/1000/12984 |
+
+## Keywords
+
+Mobile location management physical entity, MLM-PE(P), M1 interface, TLM-PE, transport location management physical entity
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+###### Page
+
+| | | |
+|------|-----------------------------------------------------------------------------|----|
+| 1 | Scope..... | 1 |
+| 2 | References..... | 1 |
+| 3 | Definitions ..... | 2 |
+| 3.1 | Terms defined elsewhere ..... | 2 |
+| 3.2 | Terms defined in this Recommendation..... | 2 |
+| 4 | Abbreviations and acronyms ..... | 2 |
+| 5 | Conventions ..... | 2 |
+| 6 | M1 interface..... | 3 |
+| 6.1 | Overview ..... | 3 |
+| 6.2 | Physical entities ..... | 3 |
+| 7 | Signalling requirements ..... | 3 |
+| 7.1 | Indication of host-based mobility ..... | 4 |
+| 7.2 | Indication of network-based mobility ..... | 5 |
+| 8 | Description of procedures..... | 6 |
+| 8.1 | General ..... | 6 |
+| 8.2 | Procedures on the M1 interface ..... | 6 |
+| 9 | Use of Diameter-based protocol ..... | 9 |
+| 9.1 | Securing Diameter messages ..... | 9 |
+| 9.2 | Accounting functionality ..... | 9 |
+| 9.3 | Use of sessions ..... | 9 |
+| 9.4 | Transport protocol ..... | 9 |
+| 9.5 | Routing considerations ..... | 9 |
+| 9.6 | Advertising application support ..... | 10 |
+| 10 | Message specification ..... | 10 |
+| 10.1 | Commands..... | 10 |
+| 10.2 | Experimental-Result-Code AVP values ..... | 12 |
+| 10.3 | Attribute-value pairs ..... | 12 |
+| 10.4 | Use of namespaces ..... | 14 |
+| 11 | Security considerations ..... | 14 |
+| | Appendix I – Mapping to mobility signalling requirements for IMT-2020 ..... | 15 |
+| | Bibliography..... | 16 |
+
+
+
+## Recommendation ITU-T Q.3228
+
+## Signalling requirements and protocol at the M1 interface between the transport location management physical entity and the mobile location management physical entity (P)
+
+# 1 Scope
+
+This Recommendation specifies the protocol for the M1 interface [ITU-T Y.2014] between the TLM-PE and the MLM-PE (P). The M1 reference point supports delivery of the information, including mobility service.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. 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.3230] Recommendation ITU-T Q.3230 (2012), *Signalling requirements and protocol at the M13 interface between the transport location management and network information distribution physical entities.*
+- [ITU-T Q.3232] Recommendation ITU-T Q.3232 (2014), *Signalling requirements and protocol at the Nc interface between the transport location management physical entity and the transport authentication and authorization physical entity.*
+- [ITU-T Y.2014] Recommendation ITU-T Y.2014 (2010), *Network attachment control functions in next generation networks.*
+- [ITU-T Y.2018] Recommendation ITU-T Y.2018 (2009), *Mobility management and control framework and architecture within the NGN transport stratum.*
+- [ETSI TS 129 229] ETSI TS 129 229 V13.0.0 (2016), *Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Cx and Dx interfaces based on the Diameter protocol; Protocol details (3GPP TS 29.229 version 13.0.0 Release 13).*
+- [ETSI TS 129 329] ETSI TS 129 329 V12.6.0 (2016), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Sh interface based on the Diameter protocol; Protocol details (3GPP TS 29.329 version 12.6.0 Release 12).*
+- [ETSI ES 283 034] ETSI ES 283 034 V2.2.0 (2008), *Telecommunications and Internet converged Services and Protocols for Advanced Networks (TISPAN); Network Attachment Sub-System (NASS); e4 interface based on the DIAMETER protocol.*
+- [ETSI ES 283 035] ETSI ES 283 035 V3.1.1 (2015), *Network Technologies (NTECH); Network Attachment; e2 interface based on the DIAMETER protocol.*
+
+[IETF RFC 4960] IETF RFC 4960 (2007), *Stream Control Transmission Protocol*.
+
+[IETF RFC 6733] IETF RFC 6733 (2012), *Diameter Base Protocol*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following term defined elsewhere:
+
+**3.1.1 security association** [b-IETF RFC 2401]: A simplex "connection" that affords security services to the traffic carried by it.
+
+## 3.2 Terms defined in this Recommendation
+
+None.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|--------|------------------------------------------------------------|
+| 3GPP | 3rd Generation Partnership Project |
+| AAA | Authentication, Authorization and Accounting |
+| AM-PE | Access Management Physical Entity |
+| ABNF | Augmented Backus-Naur Form |
+| AVP | Attribute-Value Pair |
+| CPE | Customer Premises Equipment |
+| HDC-PE | Handover Decision and Control Physical Entity |
+| IP | Internet Protocol |
+| IPsec | IP security protocol |
+| MLM-PE | Mobile Location Management Physical Entity |
+| MMCE | Mobility Management and Control Entity |
+| MMCF | Mobility Management and Control Function |
+| NACE | Network Attachment Control Entity |
+| NACF | Network Attachment Control Function |
+| NAC-PE | Network Access Configuration Physical Entity |
+| NGN | Next Generation Network |
+| SCTP | Stream Control Transmission Protocol |
+| TAA-PE | Transport Authentication and Authorization Physical Entity |
+| TLM-PE | Transport Location Management Physical Entity |
+| TUP-PE | Transport User Profile Physical Entity |
+| UE | User Equipment |
+
+# 5 Conventions
+
+None.
+
+# 6 M1 interface
+
+## 6.1 Overview
+
+This information flow is used to distribute several types of information from the TLM-PE to the MLM-PE(P) defined in the stage 2 specification [ITU-T Y.2014] and [ITU-T Y.2018]. The M1 interface allows the exchange of information about mobility service parameters.
+
+
+
+Figure 6-1: Reference points between the NACF and the MMCF. The diagram shows two main boxes: NACF on the left and MMCF on the right. NACF contains several functional entities (FE): T-15 (Home gateway configuration FE), T-12 (T. User profile FE), T-13 (T. Location management FE), T-11 (T. Authentication and authorization FE), T-10 (Network access configuration FE), and T-14 (Access management FE). External reference points for NACF are TC-Ux (top left), S-TC1 (top), TC-TC1 (top right), TC-UI (bottom left), and TC-T1 (bottom). Internal reference points within NACF are Nc, Nb, Nk, Na, Ne, and Nd. MMCF contains MLM-FE (P), MLM-FE (C), HDC-FE, NID-FE, and NIRF. Reference points M1, M2, and M13 connect NACF to MMCF: M1 connects T-13 to MLM-FE (P), M2 connects T-13 to HDC-FE, and M13 connects T-13 to NID-FE. A small code Q.3228(16)\_F6-1 is at the bottom right.
+
+Figure 6-1 – Reference points between the NACF and the MMCF [ITU-T Y.2018]
+
+## 6.2 Physical entities
+
+### 6.2.1 Transport location management physical entity (TLM-PE)
+
+The TLM-PE is assumed to be able to contact the NAC-PE via an internal reference point to obtain the persistent and temporary IP addresses.
+
+In the host-based mobility case, the information passed from the TLM-PE includes the keying material derived from the UE authentication procedure to support the security association between the MLM-PE(P) and the UE. Also, it may include mobility service user ID, persistent IP address of the user, and binding between mobile user ID and persistent IP address. In the case of network-based mobility, the transferred information includes the identifier or persistent address, the address of the MLM-PE(C) instance for this connection, and may include the lower tunnel end point address and other parameters relating to mobility service.
+
+### 6.2.2 Mobility location management physical entity (MLM-PE)
+
+When the TLM-PE indicates network-based mobility service to the MLM-PE(P), this indication will trigger the mobile location registration procedure, and indirectly trigger handover.
+
+# 7 Signalling requirements
+
+Reference point M1 allows the TLM-PE to interact with the MLM-PE(P) for pushing mobility service parameters, such as keying material and anchor address. The TLM-PE holds keying material, anchor address, etc. in the mobility service parameters information shown in Table 7-1 and pushes keying material to MLM-PE(P).
+
+The M1 reference point should allow information exchange as follows:
+
+- information about mobility service parameters is pushed by the TLM-PE to MLM-PE(P).
+
+**Table 7-1 – Information about mobility service parameters in TLM-PE**
+
+| Parameter | Description | Received from |
+|--------------------------|-----------------------------------------------------------------------------------------------------------|---------------|
+| Address of MLM-PE(C) | The address of the instance of the MLM-PE containing the mobile address binding information. | NAC-PE |
+| Address of MLM-PE(P) | The address of the MLM-PE instance which sends the location registration. | |
+| Keying Material | The material used for the security association between the UE and MMCE. | TAA-PE |
+| Mobility Protocol Type | The type of mobility protocol, such as host-based or network-based mobility. | |
+| Anchor point address | The upper tunnel end point address, from the point of view of the UE. | |
+| Tunnel end point address | The tunnelling end point address for the network node which works as UE's proxy (lower tunnel end point). | |
+
+The following information flows shall be used on the M1 interface:
+
+- Indication of host-based mobility;
+- Indication of network-based mobility.
+
+Figure 7-1 shows the information flows between the TLM-PE and the MLM-PE(P) through the M1 interface.
+
+
+
+Diagram showing information flows between TLM-PE and MLM-PE(P). Two boxes, TLM-PE and MLM-PE(P), are shown. Two arrows point from TLM-PE to MLM-PE(P): the top arrow is labeled 'Indication of host-based mobility' and the bottom arrow is labeled 'Indication of network-based mobility'. Below the arrows is the text 'Q.3228(16)\_F7-1'.
+
+**Figure 7-1 – Information flow**
+
+## 7.1 Indication of host-based mobility
+
+In the host-based mobility case, the transferred information includes the keying material derived from the UE authentication procedure, in support of the security association required between the MLM-PE(P) and the UE. The information passed from the TLM-PE to the MLM-PE(P) may also include:
+
+- mobility service user ID;
+- persistent IP address of the user;
+- binding between mobile user ID and persistent IP address.
+
+The TAA-PE obtains these mobility service parameters from an AAA entity in the mobile subscriber's home network. How the TAA-PE determines that mobility service is to be provided and that mobility service parameters are required is out of the scope of this Recommendation.
+
+The contents of the "indication of host-based mobility" primitive described in [ITU-T Y.2018] are shown in Table 7-2.
+
+**Table 7-2 – Indication of host-based mobility (TLM-PE → MLM-PE(P))**
+
+| Information element | Explanation |
+|-------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Transport subscriber identifier (optional) (Note) | The user/UE identifier authenticated for attachment. |
+| Mobility service subscriber identifier | The user/UE identifier authenticated for mobility services. This will be the same as the transport subscriber identifier in the integrated scenario. |
+| Persistent IP address information (optional) (Note) | A set of IP address information used for locating the mobile UE. |
+| – Unique IP address | The persistent IP address allocated to the attached mobile UE. |
+| – Address realm | The addressing domain in which the IP address is significant. |
+| Keying material | The material used for the security association between the UE and MLM-PE(P). |
+| RACE contact point (optional) | The FQDN or IP address of the RACE entity where the resource requests are required to be sent (i.e., PD-PE address). |
+| Anchor point address (optional) | The upper tunnel end point address, from the point of view of the UE. |
+| NOTE – Either the UE identifier or the persistent IP address must be present. | |
+
+## 7.2 Indication of network-based mobility
+
+The transferred information in the case of network-based mobility includes the identifier or persistent address, the address of the MLM-PE(C) instance for this connection, and may include the lower tunnel end point address and other parameters relating to mobility service. The "indication of network-based mobility" primitive described in [ITU-T Y.2018] is shown in Table 7-3.
+
+When the TLM-PE indicates network-based mobility service to the MLM-PE(P), this indication will trigger the mobile location registration procedure, and indirectly trigger handover.
+
+**Table 7-3 – Indication of network-based mobility (TLM-PE → MLM-PE(P))**
+
+| Information element | Explanation |
+|-------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Transport subscriber identifier (optional) (Note 1) | The user/UE identifier authenticated for attachment. |
+| Mobility service subscriber identifier | The user/UE identifier authenticated for mobility services. This will be the same as the transport subscriber identifier in the integrated scenario. |
+| Persistent IP address information (optional) (Note 1) | A set of IP address information used for locating the mobile UE. |
+| – Unique IP address | The persistent IP address allocated to the attached mobile UE. |
+| – Address realm | The addressing domain in which the IP address is significant. |
+| Address of MLM-PE(C) | The address of the instance of the MLM-PE containing the mobile address binding information. |
+| Tunnel end-point address (optional) (Note 2) | The tunnelling end point address for the network node which works as UE's proxy (lower tunnel end point). |
+| RACE contact point (optional) | The FQDN or IP address of the RACE entity where resource requests shall be sent (i.e., PD-FE address). |
+
+**Table 7-3 – Indication of network-based mobility (TLM-PE → MLM-PE(P))**
+
+| Information element | Explanation |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|
+| Anchor point address (optional) | The upper tunnel end point address, from the point of view of the UE. |
+| NOTE 1 – Either the UE identifier or the persistent IP address must be present. | |
+| NOTE 2 – If the tunnel end-point address is statically provisioned or the MLM-PE can obtain it with its own mechanisms, this information is not required. | |
+
+# 8 Description of procedures
+
+## 8.1 General
+
+The following clauses describe the realization of the functional procedures defined in the NACE [ITU-T Y.2014] and MMCE specifications [ITU-T Y.2018] using Diameter commands described in clause 10. They include mapping between the information elements defined in the NACE specification and the Diameter attribute-value pairs (AVPs).
+
+In the tables that describe this mapping (Tables 8-1 to 8-4), each information element is marked as (M) mandatory, (C) conditional, or (O) optional [ETSI ES 283 035].
+
+## 8.2 Procedures on the M1 interface
+
+This procedure is used to push mobility service parameters from the TLM-PE to the MLM-PE. This information flow occurs from the UE authentication procedure to connect the security association between UE and MLM-PE(P) to distribute mobility service information.
+
+### 8.2.1 Indication of host-based mobility
+
+This procedure is mapped to the Push-Notifications-Request/Answer commands in the Diameter application specified in clause 10. Tables 8-1 and 8-2 detail the involved information elements as defined in the NACE specification [ITU-T Y.2014] and their mapping to Diameter AVPs.
+
+**Table 8-1 – Indication of host-based mobility**
+
+| Information Element name | Mapping to Diameter AVP | Category |
+|----------------------------------------|-------------------------|----------|
+| | Mobility-Protocol-Type | M |
+| Mobility service subscriber identifier | User-Name | M |
+| Transport subscriber identifier | User-Name | C |
+| Persistent IP address | Globally-Unique-Address | C |
+| Keying material | Keying-Material | M |
+| RACE address | RACE-Contact-Point | O |
+| Anchor point address | Anchor-Point-Address | O |
+
+**Table 8-2 – Indication of host-based mobility response**
+
+| Information element name | Mapping to Diameter AVP | Category |
+|--------------------------|---------------------------------|----------|
+| Result | Result-Code/Experimental_Result | M |
+
+#### **8.2.1.1 Procedure at the TLM-PE side**
+
+The TLM-PE shall deliver the Indication of host-based mobility by including the following information elements:
+
+- (1) At a minimum, a User-Name AVP for a transport subscriber identifier or a Globally-Unique-Address AVP shall be included conditionally. The Globally-Unique-Address AVP shall contain a Frame-IP-Address AVP or a Frame-IPv6-Prefix AVP, and an Address-Realm AVP.
+- (2) A RACE-Contact-Point AVP or an Anchor-Point-Address AVP may be included optionally.
+- (3) The Mobility-Protocol-Type AVP, the User-Name AVP for a Mobility service subscriber identifier, and the Keying-Material AVP shall be present.
+
+#### **8.2.1.2 Procedure at the MLM-PE side**
+
+Upon reception of the Indication of host-based mobility, the MLM-PE shall:
+
+- (1) If User-Name AVP for transport subscriber is present, go to step (4). Otherwise, go to the next step.
+- (2) If User-Name AVP for transport subscriber is absent, but Globally-Unique-Address AVP is present, go to step (4). Otherwise, go to the next step.
+- (3) If both User-Name AVP for transport subscriber and Globally-Unique-Address AVP are absent, return Indication of host-based mobility response with Result-Code set to DIAMETER\_MISSING\_AVP.
+- (4) If no session record is stored for the User-Name AVP or Globally-Unique-Address AVP, return network selection key transfer indication response with the Experimental-Result-Code AVP set to DIAMETER\_ERROR\_USER\_UNKNOWN. Otherwise, go to the next step.
+- (5) If Mobility-Protocol-Type AVP is present, go to step the next step. Otherwise, return indication of host-based mobility response with Result-Code set to DIAMETER\_MISSING\_AVP.
+- (6) If User-Name AVP for Mobility service is present, go to step the next step. Otherwise, return indication of host-based mobility response with Result-Code set to DIAMETER\_MISSING\_AVP.
+- (7) If Keying-Material AVP is present, go to step the next step. Otherwise, return indication of host-based mobility response with Result-Code set to DIAMETER\_MISSING\_AVP.
+- (8) Under temporary overload conditions, the MLM-PE shall stop processing the request and return a network selection key transfer indication response with the Experimental-Result-Code set to DIAMETER\_USER\_DATA\_NOT\_AVAILABLE. Otherwise, go to the next step.
+- (9) If the MLM-PE cannot fulfil the received request for reasons not stated in the above-mentioned steps, e.g., due to database error, it shall stop processing the request and, return a network selection key transfer indication response with the Result-Code set to DIAMETER\_UNABLE\_TO\_COMPLY. Otherwise, go to the next step.
+- (10) The MLM-PE shall return the Result-Code AVP set to DIAMETER\_SUCCESS in the indication of host-based mobility response.
+
+### **8.2.2 Indication of network-based mobility**
+
+This procedure is mapped to the commands Push-Notifications-Request/Answer in the Diameter application specified in clause 10. Tables 8-3 and 8-4 detail the relevant information elements as defined in the NACE specification [ITU-T Y.2014] and their mapping to Diameter AVPs.
+
+**Table 8-3 – Indication of network-based mobility**
+
+| Information element name | Mapping to Diameter AVP | Category |
+|----------------------------------------|------------------------------|----------|
+| | Mobility-Protocol-Type | M |
+| Mobility service subscriber identifier | User-Name | M |
+| Transport subscriber identifier | User-Name | C |
+| Persistent IP address | Globally-Unique-Address | C |
+| Address of MLM-PE(C) | Central-MLM-PE-Contact-Point | M |
+| Tunnel end-point address | Tunnel-End-Point-Address | O |
+| Address of RACE | RACE-Contact-Point | O |
+| Address of anchor point | Anchor-Point-Address | O |
+
+**Table 8-4 – Indication of network-based mobility response**
+
+| Information element name | Mapping to Diameter AVP | Category |
+|--------------------------|---------------------------------|----------|
+| Result | Result-Code/Experimental_Result | M |
+
+#### **8.2.2.1 Procedure at the TLM-PE side**
+
+The TLM-PE shall deliver the indication of network-based mobility by including the following information elements:
+
+- (1) At a minimum, a User-Name AVP for a transport subscriber identifier or a Globally-Unique-Address AVP shall be included conditionally. The Globally-Unique-Address AVP shall contain a Frame-IP-Address AVP or a Frame-IPv6-Prefix AVP, and an Address-Realm AVP.
+- (2) A Tunnel-End-Point-Address AVP or a RACE-Contact-Point AVP or an Anchor-Point-Address AVP may be included optionally.
+- (3) The Mobility-Protocol-Type AVP, the User-Name AVP for a mobility service subscriber identifier, and the Central-MLM-PE-Contact-Point AVP shall be present.
+
+#### **8.2.2.2 Procedure at the MLM-PE side**
+
+Upon reception of the Indication of host-based mobility, the MLM-PE shall:
+
+- (1) If User-Name AVP for transport subscriber is present, go to step (4). Otherwise, go to the next step.
+- (2) If User-Name AVP for transport subscriber is absent, but Globally-Unique-Address AVP is present, go to step (4). Otherwise, go to the next step.
+- (3) If both User-Name AVP for transport subscriber and Globally-Unique-Address AVP are absent, return Indication of host-based mobility response with Result-Code set to DIAMETER\_MISSING\_AV.
+- (4) If no session record is stored for the User-Name AVP or Globally-Unique-Address AVP, return network selection key transfer indication response with the Experimental-Result-Code AVP set to DIAMETER\_ERROR\_USER\_UNKNOWN. Otherwise, go to the next step.
+- (5) If Mobility-Protocol-Type AVP is present, go to step the next step. Otherwise, return Indication of host-based mobility response with Result-Code set to DIAMETER\_MISSING\_AV.
+- (6) If User-Name AVP for Mobility service is present, go to step the next step. Otherwise, return Indication of host-based mobility response with Result-Code set to DIAMETER\_MISSING\_AV.
+
+- (7) If Central-MLM-PE-Contact-Point AVP is present, go to step the next step. Otherwise, return Indication of host-based mobility response with Result-Code set to DIAMETER\_MISSING\_AVP.
+- (8) Under temporary overload conditions, the MLM-PE shall stop processing the request and return a network selection key transfer indication response with the Experimental-Result-Code set to DIAMETER\_USER\_DATA\_NOT\_AVAILABLE. Otherwise, go to the next step.
+- (9) If the MLM-PE cannot fulfil the received request for reasons not stated in the above steps, e.g., due to database error, it shall stop processing the request and, return a network selection key transfer indication response with the Result-Code set to DIAMETER\_UNABLE\_TO\_COMPLY. Otherwise, go to the next step.
+- (10) The MLM-PE shall return the Result-Code AVP set to DIAMETER\_SUCCESS in the Indication of host-based mobility response.
+
+# 9 Use of Diameter-based protocol
+
+With the clarifications listed in the following clauses, the Diameter base protocol defined by [IETF RFC 6733] shall apply.
+
+## 9.1 Securing Diameter messages
+
+For secure transport of Diameter messages, IP security (IPsec) may be used. Guidelines on the use of stream control transmission protocol (SCTP) with IPsec can be found in [b-IETF RFC 3554].
+
+## 9.2 Accounting functionality
+
+Accounting functionality (accounting session state machine, related command codes and AVPs) is not used at the M1 interface.
+
+## 9.3 Use of sessions
+
+Diameter sessions are implicitly terminated. An implicitly terminated session is one for which the server does not maintain state information. The client does not need to send any re-authorization or session termination requests to the server [IETF RFC 6733].
+
+The Diameter base protocol includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions.
+
+The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1), as described in [IETF RFC 6733]. As a consequence, the server does not maintain any state information about this session and the client does not need to send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses.
+
+## 9.4 Transport protocol
+
+Diameter messages over the M1 interface shall make use of SCTP [IETF RFC 4960] and shall utilize the new SCTP checksum method specified in [IETF RFC 4960].
+
+## 9.5 Routing considerations
+
+This clause specifies the use of the Diameter routing AVPs: Destination-Realm and Destination-Host.
+
+With regard to the Diameter diameter protocol used at the M1 interface, the TLM-PE acts as a Diameter server and the MLM-PE(P) acts as the Diameter client.
+
+Requests initiated by the MLM-PE(P) towards the TLM-PE shall include both Destination-Host and Destination-Realm AVPs. The MLM-PE(P) obtains the Destination-Host AVP to use in requests towards a TLM-PE, from configuration data in TAA-PE or the user profile from the TUP-PE. Consequently, the Destination-Host AVP is declared as mandatory in the augmented Backus-Naur form (ABNF) for all requests initiated by the MLM-PE(P).
+
+Requests initiated by the TLM-PE towards the MLM-PE(P) shall include both Destination-Host and Destination-Realm AVPs. The TLM-PE obtains the Destination-Host AVP to use in requests towards a MLM-PE(P), from the Origin-Host and Origin-Realm AVPs received in previous commands from the MLM-PE(P) related to the same IP realm. Consequently, the Destination-Host AVP is declared as mandatory in the ABNF for all requests initiated by the TLM-PE.
+
+Destination-Realm AVP is declared as mandatory in the ABNF for all requests.
+
+## 9.6 Advertising application support
+
+The Capabilities-Exchange-Request (CER) and Capabilities-Exchange-Answer (CEA) commands are specified in [IETF RFC 6733]. The Diameter base application identifier (0) shall be used in the Diameter message header of these messages.
+
+If TLM-PE and MLM-PE(P) indicate support of the M1 application, then the M1 application identifier (16777352) shall be used in the Diameter message header of all subsequent messages exchanged within this association.
+
+Support of the M1 application within the CER/CEA is indicated by supplying an instance of the Vendor-Specific-Application-Id containing a Vendor-Id AVP set to ITU-T (11502) and an Auth-Application-Id AVP set to M1 (16777352).
+
+The TLM-PE and MLM-PE(P) are required to advertise the support of AVPs specified in 3GPP, ETSI, and ITU-T documents by including the values 10415 (3GPP), 13019 (ETSI), and 11502 (ITU-T) in three different instances of the Supported-Vendor-Id AVP in the CER and CEA commands, respectively (see Table 9-1).
+
+**Table 9-1 – Vendor identifiers for M1**
+
+| Vendor | Vendor identifier |
+|---------------|--------------------------|
+| 3GPP | 10415 |
+| ETSI | 13019 |
+| ITU-T | 11502 |
+
+NOTE – The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that are not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per [IETF RFC 6733].
+
+# 10 Message specification
+
+## 10.1 Commands
+
+This Recommendation reuses the Diameter command defined in [ETSI TS 129 329]. Other commands shall be ignored by the TLM-PE and NAC-PE (see Table 10-1).
+
+**Table 10-1 – Command code**
+
+| Command | Abbreviation | Defining reference | Command code | See clause |
+|---------------------------|--------------|--------------------|--------------|------------|
+| Push-Notification-Request | PNR | [ETSI TS 129 329] | 309 | 10.1.1 |
+| Push-Notification-Answer | PNA | [ETSI TS 129 329] | 309 | 10.1.2 |
+
+### **10.1.1 Push-Notification-Request command**
+
+The Push-Notification-Request (PNR) command, indicated by the Command-Code field set to 309 and the "R" bit set in the Command Flags field, is sent by a Diameter server to a Diameter client in order to notify changes in the user data in the server. This command is defined in [ETSI TS 129 329] and used with additional AVPs defined in this Recommendation.
+
+#### *Message Format:*
+
+```
+< Push-Notification-Request > ::= < Diameter Header: 309, REQ, PXY, 16777352>
+< Session-Id >
+{ Vendor-Specific-Application-Id }
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+{ Destination-Host }
+{ Destination-Realm }
+{ Mobility-Protocol-Type }
+[ User-Name ]
+[ User-Name ]
+[ Globally-Unique-Address ]
+[ Keying-Material ]
+[ RACE-Contact-Point ]
+[ Anchor-Point-Address ]
+[ Central-MLM-PE-Contact-Point ]
+[ Tunnel-End-Point-Address ]
+*[ AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+```
+
+### **10.1.2 Push-Notification-Answer command**
+
+The Push-Notification-Answer (PNA) command, indicated by the Command-Code field set to 309 and the "R" bit cleared in the Command Flags field, is sent by a client in response to the Push-Notification-Request command. The Experimental-Result-Code AVP may contain one of the values defined in clause 10.2.
+
+#### *Message Format:*
+
+```
+< Push-Notification-Answer > ::= < Diameter Header: 309, PXY, 16777352>
+< Session-Id >
+{ Vendor-Specific-Application-Id }
+[ Result-Code ]
+[ Experimental-Result ]
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+*[ AVP ]
+*[ Failed-AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+```
+
+## 10.2 Experimental-Result-Code AVP values
+
+This clause defines specific values of the Experimental-Result-Code AVP used in this Recommendation. Most of these are imported from 3GPP and ETSI specifications, as indicated in the following clauses.
+
+### 10.2.1 Experimental-Result-Code AVP values imported from [ETSI TS 129 229] and [ETSI TS 129 329]
+
+This clause defines the specific values of the Experimental-Result-Code AVP imported from [ETSI TS 129 229] and [ETSI TS 129 329] (vendor-id is ETSI):
+
+DIAMETER\_ERROR\_USER\_UNKNOWN (5001)
+
+The request failed because the IP address or Globally-Unique Address is not found.
+
+DIAMETER\_USER\_DATA\_NOT\_AVAILABLE (4100)
+
+The requested data is not available at this time to satisfy the requested operation
+
+## 10.3 Attribute-value pairs
+
+The following tables (Tables 10-2 to 10-5) summarize the AVPs used in this Recommendation. These are, in addition to the AVPs, defined in [IETF RFC 6733].
+
+Table 10-2 describes the Diameter AVPs defined by [ETSI ES 283 034] and used within this Recommendation. These AVPs are described in this Recommendation for information; however, the normative detail for these AVPs is contained in [ETSI ES 283 034]. The Vendor-Id header of all AVPs defined in Table 10-2 shall be set to ETSI (13019).
+
+**Table 10-2 – Diameter AVPs imported from [ETSI ES 283 034]**
+
+| Attribute name | AVP code | Clause defined | Value type | AVP flag rules | | | | May encrypt |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------------|------------|----------------|-----|------------|----------|-------------|
+| | | | | Must | May | Should not | Must not | |
+| Globally-Unique-Address | 300 | 10.3.1 | Grouped | M,V | | | | Y |
+| NOTE – The AVP flag bit denoted as "M" indicates support of the AVP is required. The AVP flag bit denoted as "V" indicates the optional Vendor-ID field is present in the AVP header. | | | | | | | | |
+
+Table 10-3 describes the Diameter AVPs that are used within this Recommendation that have been defined by [ETSI ES 283 035], providing their AVP code values, types, possible flag values and whether or not the AVP may be encrypted. The Vendor-Id header of all AVPs identified in Table 10-3 shall be set to ETSI (13019). These AVPs are described in this Recommendation for information; however, the normative detail for these AVPs is contained in [ETSI TS 283 035].
+
+**Table 10-3 – Diameter AVPs imported from [ETSI ES 283 035]**
+
+| Attribute name | AVP code | Clause defined | Value type | AVP flag rules | | | | May encrypt |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------------|------------------|----------------|-----|------------|----------|-------------|
+| | | | | Must | May | Should not | Must not | |
+| RACE-Contact-Point | 351 | 10.3.2 | DiameterIdentity | V | M | | | Y |
+| NOTE – The AVP flag bit denoted as "M" indicates support of the AVP is required. The AVP flag bit denoted as "V" indicates the optional Vendor-ID field is present in the AVP header. | | | | | | | | |
+
+Table 10-4 describes the Diameter AVPs defined by [ITU-T Q.3230] and used within this Recommendation. These AVPs are described in this Recommendation for information; however, the
+
+normative detail for these AVPs is contained in [ITU-T Q.3230]. The Vendor-Id header of all AVPs defined in Table 10-4 shall be set to ITU-T (11502).
+
+**Table 10-4 – Diameter AVPs imported from [ITU-T Q.3230]**
+
+| Attribute name | AVP code | Clause defined | Value type | AVP flag rules | | | | May encrypt |
+|-----------------|----------|----------------|--------------|----------------|-----|------------|----------|-------------|
+| | | | | Must | May | Should not | Must not | |
+| Keying-Material | 1040 | 10.3.3 | Octet String | M,V | | | | Y |
+
+Table 10-5 describes the AVPs defined solely within this Recommendation. The ITU-T Vendor-Id (11502) shall be used in the Vendor-Id field of the AVP header.
+
+**Table 10-5 – Diameter AVPs imported from [ITU-T Q.3232]**
+
+| Attribute name | AVP code | Clause defined | Value type | AVP flag rules | | | | May encrypt |
+|------------------------------|----------|----------------|------------------|----------------|-----|------------|----------|-------------|
+| | | | | Must | May | Should not | Must not | |
+| Central-MLM-PE-Contact-Point | 1054 | 10.3.4 | DiameterIdentity | V | M | | | Y |
+| Mobility-Protocol-Type | 1056 | 10.3.5 | Enumerated | V | M | | | Y |
+| Anchor-Point-Address | 1057 | 10.3.6 | DiameterIdentity | V | M | | | Y |
+| Tunnel-End-Point-Address | 1058 | 10.3.7 | DiameterIdentity | V | M | | | Y |
+
+NOTE – The AVP flag bit denoted as "M" indicates support of the AVP is required. The AVP flag bit denoted as "V" indicates the optional Vendor-ID field is present in the AVP header.
+
+### 10.3.1 Globally-Unique-Address AVP
+
+The Globally-Unique-IP-Address AVP (AVP code 300 13019) is of type Grouped.
+
+*AVP format:*
+
+```
+Globally-Unique-Address ::= < AVP Header: 300 13019 >
+ [Framed-IP-Address]
+ [Framed-IPv6-Prefix]
+ [Address-Realm]
+```
+
+### 10.3.2 RACE-Contact-Point AVP
+
+The RACE-Contact-Point AVP (AVP code 351 13019) is of type DiameterIdentity and identifies the RACE element to which resource reservation requests shall be sent.
+
+### 10.3.3 Keying-Material AVP
+
+The Keying-Material AVP (AVP code 1040 11502) is of type Octet String, and provides the material used for security association.
+
+### 10.3.4 Central-MLM-PE-Contact-Point AVP
+
+The Central-MLM-PE-Contact-Point AVP (AVP code 1054 11502) is of type DiameterIdentity and identifies the address of the instance of the MLM-PE containing the mobile address binding information.
+
+### **10.3.5 Mobility-Protocol-Type AVP**
+
+The Mobility-Protocol-Type AVP (AVP code 1056 11502) is of type Enumerated and identifies the type of mobility protocol that TE or CPE could support, for example host-based or network-based mobility.
+
+The following values are defined:
+
+- HOST-BASED-MOBILITY (0);
+- NETWORK-BASED-MOBILITY (1).
+
+### **10.3.6 Anchor-Point-Address AVP**
+
+The Anchor-Point-Address AVP (AVP code 1057 11502) is of type DiameterIdentity and identifies the upper tunnel end point address, from the UE point of view.
+
+### **10.3.7 Tunnel-End-Point-Address AVP**
+
+The Tunnel-End-Point-Address AVP (AVP code 1058 11502) is of type DiameterIdentity and identifies the tunnel end point address for the network node which works as UE's proxy (lower tunnel end point).
+
+## **10.4 Use of namespaces**
+
+This clause contains the namespaces that have either been created in this Recommendation or the values assigned to existing namespaces managed by the Internet Assigned Numbers Authority (IANA).
+
+### **10.4.1 AVP codes**
+
+This Recommendation uses AVP values from the AVP Code namespace managed by ETSI for its Diameter vendor-specific applications. In addition, this Recommendation assigns AVP code values within the Diameter AVP Code namespace managed by ITU-T. See clause 10.3.
+
+### **10.4.2 Experimental-Result-Code AVP values**
+
+This Recommendation assigns the Experimental-Result-Code AVP values from the AVP Code namespace managed by ETSI for its Diameter vendor-specific applications. See clause 10.2.
+
+### **10.4.3 Command code values**
+
+This Recommendation does not assign command code values but uses existing commands defined by the Internet Engineering Task Force (IETF), including those requested by 3GPP.
+
+### **10.4.4 Application-ID value**
+
+This Recommendation defines the M1 Diameter application with application ID 16777352. The vendor identifier assigned by IANA to ITU-T is 11502 ().
+
+# **11 Security considerations**
+
+Security requirements within the functional requirements and architecture of the NACF are addressed by the security requirements for NGN [b-ITU-T Y.2701]. The M1 interface shall follow the security requirements of the network attachment control functions (NACF) [ITU-T Y.2014].
+
+Clause 10.1 recommends the use of IPSec to ensure secure transport of Diameter messages. Guidelines on the use of SCTP with IPSec can be found in [b-IETF RFC 3554].
+
+Additional considerations are provided in the security considerations section of [IETF RFC 6733].
+
+# Appendix I
+
+## **Mapping to mobility signalling requirements for IMT-2020**
+
+(This appendix does not form an integral part of this Recommendation.)
+
+The ITU-T FG IMT-2020 network is recommended to support distributed network architecture, and optimized routes for application data and signalling data, Control/User-plane functions should be clearly separated with defined interface [b-ITU-T FG IMT-2020].
+
+NGN is also designed to separate control/user-plane functions, and even NACE and MMCE are separated within the control plane to be responsible for the initialization of CPE for accessing the NGN services [ITU-T Y.2014] and the mobile location management [ITU-T Y.2018], respectively. Reference point M1 allows the TLM-PE (NACE) to interact with the MLM-PE (MMCE) for pushing mobility service parameters, such as keying material, and anchor address. Information flows used on the M1 interface may be adapted to the information flows for indicating mobility service types between modular functional entities if functional entities similar to NACE and MMCE are defined according to [b-ITU-T FG IMT-2020].
+
+# Bibliography
+
+- [b-ITU-T Y.2701] Recommendation ITU-T Y.2701 (2007), *Security requirements for NGN release 1*.
+- [b-ITU-T FG IMT-2020] FG IMT-2020: *Report on Standards Gap analysis*.
+- [b-IETF RFC 2401] IETF RFC 2401 (1998), *Security Architecture for the Internet Protocol*.
+- [b-IETF RFC 3554] IETF RFC 3554 (2003), *On the Use of Stream Control Transmission Protocol (SCTP) with IPSec*.
+
+
+
+## **SERIES OF ITU-T RECOMMENDATIONS**
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3304.2-201208-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3304.2-201208-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..647c80548c08886c4187332e3c71529c97e7a092
--- /dev/null
+++ b/marked/Q/T-REC-Q.3304.2-201208-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9a714270e2101b36cfb0bc037b45130e7e395251ac65b06a62efb2a46b71474c
+size 4002
diff --git a/marked/Q/T-REC-Q.3304.2-201208-I_PDF-E/731f533b0599c8e42a063f06e4332045_img.jpg b/marked/Q/T-REC-Q.3304.2-201208-I_PDF-E/731f533b0599c8e42a063f06e4332045_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5708e3b7a2bb24f6f911112ee7157f8e5b0aec99
--- /dev/null
+++ b/marked/Q/T-REC-Q.3304.2-201208-I_PDF-E/731f533b0599c8e42a063f06e4332045_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0bef5ac3b537d8f83f46a80712f45d35514846bcb4d7372a9dd9229da1227493
+size 41967
diff --git a/marked/Q/T-REC-Q.3304.2-201208-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3304.2-201208-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..0426f52ac5df2c690858f9d95f253132b11cf167
--- /dev/null
+++ b/marked/Q/T-REC-Q.3304.2-201208-I_PDF-E/raw.md
@@ -0,0 +1,313 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.3304.2**
+
+(08/2012)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Signalling requirements and protocols for the NGN –
+Resource control protocols
+
+---
+
+**Resource control protocol No. 4 (rcp4) –
+Protocols at the Rc interface between a
+transport resource control physical entity and a
+transport physical entity: SNMP alternative**
+
+Recommendation ITU-T Q.3304.2
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|---------------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3999 |
+| General | Q.3000–Q.3029 |
+| Network signalling and control functional architecture | Q.3030–Q.3099 |
+| Network data organization within the NGN | Q.3100–Q.3129 |
+| Bearer control signalling | Q.3130–Q.3179 |
+| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 |
+| Resource control protocols | Q.3300–Q.3369 |
+| Service and session control protocols | Q.3400–Q.3499 |
+| Service and session control protocols – supplementary services | Q.3600–Q.3649 |
+| NGN applications | Q.3700–Q.3849 |
+| Testing for next generation networks | Q.3900–Q.3999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## **Recommendation ITU-T Q.3304.2**
+
+## **Resource control protocol No. 4 (rcp4) – Protocols at the Rc interface between a transport resource control physical entity and a transport physical entity: SNMP alternative**
+
+## **Summary**
+
+Recommendation ITU-T Q.3304.2 specifies the profile of a variant of the resource control protocol No. 4 (rcp4) that uses the simple network management protocol (SNMP) at the Rc interface, i.e., between the transport resource control physical entity (TRC-PE) and the transport physical entity (T-PE) in the resource and admission control functional block. This protocol operates across the Rc reference point, as defined in Recommendation ITU-T Y.2111. The interface is used for checking the network topology and resource status information of an access or a core network.
+
+## **History**
+
+| Edition | Recommendation | Approval | Study Group |
+|---------|-------------------|------------|-------------|
+| 1.0 | ITU-T Q.3304.2 | 2007-10-29 | 11 |
+| 2.0 | ITU-T Q.3304.2 v2 | 2012-08-13 | 11 |
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2013
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|-----------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 3.2 Terms defined in this Recommendation..... | 1 |
+| 4 Abbreviations and acronyms ..... | 2 |
+| 5 Conventions ..... | 2 |
+| 6 Rc interface..... | 2 |
+| 6.1 Rc reference model..... | 2 |
+| 7 Protocol specification ..... | 3 |
+| 8 Protocols and messages ..... | 3 |
+| 8.1 Resource query message..... | 3 |
+| 8.2 Resource state report message..... | 3 |
+| 9 Security considerations..... | 3 |
+| Appendix I – Management information base..... | 4 |
+| Bibliography..... | 6 |
+
+
+
+## Recommendation ITU-T Q.3304.2
+
+## Resource control protocol No. 4 (rcp4) – Protocols at the Rc interface between a transport resource control physical entity and a transport physical entity: SNMP alternative
+
+## 1 Scope
+
+This Recommendation provides the Stage 3 technical specifications for a protocol variant which uses the simple network management protocol (SNMP) to satisfy the requirements for information transfer across the Rc reference point, as defined in clause 8.3 of [ITU-T Y.2111]. This protocol allows the transport resource control physical entity (TRC-PE) to collect network topology and resource status information from elements of an access or a core network.
+
+## 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.3300 v2] Recommendation ITU-T Q.3300 v2 (2010), *Architectural framework for the Q.33xx series of Recommendations*.
+- [ITU-T Y.2012] Recommendation ITU-T Y.2012 (2006), *Functional requirements and architecture of the NGN release 1*.
+- [ITU-T Y.2111] Recommendation ITU-T Y.2111 (2008), *Resource and admission control functions in next generation networks*.
+- [IETF RFC 3416] IETF RFC 3416 (2002), *Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP)*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 transport physical entity (T-PE)** [ITU-T Q.3300]: A term used to refer to any device implementing the transport functions in the limited sense provided in clause 7.2.4 of [ITU-T Y.2111] (i.e., those with which the RACF interacts).
+
+**3.1.2 transport resource control physical entity (TRC-PE)** [ITU-T Q.3300]: A device that implements the transport resource control functional entity (TRC-FE) as defined in clause 7.2.3.3 of [ITU-T Y.2111].
+
+### 3.2 Terms defined in this Recommendation
+
+None.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|--------|------------------------------------------------|
+| DoS | Denial of Service |
+| MIB | Management Information Base |
+| NACE | Network Attachment Control Entity |
+| OID | Object ID |
+| PD-PE | Policy Decision Physical Entity |
+| PE-PE | Policy Enforcement Physical Entity |
+| SCE | Service Control Entity |
+| SNMP | Simple Network Management Protocol |
+| T-PE | Transport Physical Entity |
+| TRC-PE | Transport Resource Control Physical Entity |
+| TRE-PE | Transport Resource Enforcement Physical Entity |
+
+## 5 Conventions
+
+None.
+
+# 6 Rc interface
+
+The Rc interface allows a transport resource control physical entity (TRC-PE) to collect network topology and resource status information about an access or a core network. The Rc interface is relevant to a transport physical entity (T-PE) at the network boundary or inside the network.
+
+### 6.1 Rc reference model
+
+The Rc interface, as shown in Figure 6-1, is defined between the TRC-PE and T-PE.
+
+
+
+The diagram illustrates the Rc reference model across two strata: Service stratum and Transport stratum. In the Service stratum, a Service Control Entity (SCE) is connected to a Policy Decision Physical Entity (PD-PE). In the Transport stratum, a Network Attachment Control Entity (NACE) is connected to a Resource Allocation Control Function (RACF). The RACF contains a Transport Resource Control Physical Entity (TRC-PE) and a PD-PE. The TRC-PE is connected to a Transport Physical Entity (T-PE), which in turn contains a Transport Resource Enforcement Physical Entity (TRE-PE) and a Policy Enforcement Physical Entity (PE-PE). The TRE-PE is connected to the TRC-PE via the Rc interface, which is highlighted by a dashed box and labeled 'Scope of this Recommendation'. Other interfaces are labeled: Ru (between NACE and RACF), Rp (between RACF and TRC-PE), Rd (between PD-PE and RACF), Rs (between SCE and PD-PE), Ri (between PD-PE and Other NGNs), Rt (between PD-PE and TRC-PE), Rn (between TRC-PE and TRE-PE), Rc (between TRC-PE and TRE-PE), and Rw (between PE-PE and TRE-PE). A box labeled 'Other NGNs' is connected to the PD-PE and PE-PE. The diagram is identified by the code Q.3304.2v2(12)\_F6-1.
+
+Figure 6-1 – Rc reference model diagram showing the network architecture and the location of the Rc interface.
+
+Figure 6-1 – Rc reference model
+
+## **7 Protocol specification**
+
+SNMPv2 [IETF RFC 3416] shall apply to the Rc interface, where the TRC-PE acts as an SNMP manager and the transport elements are SNMP agents. The TRC-PE issues the SNMP-get (resource query message) to the T-PE and collects the resource information by retrieving interface information. If a change has occurred in the operational status or administrative status at the interfaces of the T-PE, the change is reported by the SNMP-trap (resource state report message) issued by the T-PE, and the TRC-PE then updates its resource information.
+
+## **8 Protocols and messages**
+
+### **8.1 Resource query message**
+
+The TRC-PE collects interface information by issuing the SNMP-get to transport elements, as shown in [IETF RFC 3416]. The interface information to be retrieved corresponds to the object IDs (OIDs) under OID:1.3.6.1.2.1. The management information bases (MIBs) and OIDs associated with SNMP-get are shown in Appendix I.
+
+### **8.2 Resource state report message**
+
+The change in the operational status at the interfaces of the transport element is reported to the TRC-PE by the SNMP-trap [IETF RFC 3416]. The generic SNMP-trap can be used for resource state report messages. SNMP-traps with generic trap Type 2 (linkDown) and generic trap Type 3 (linkUp) are utilized. The OIDs associated with the SNMP-trap are shown in Appendix I.
+
+## **9 Security considerations**
+
+There might be several possible security threats at the Rc interface, such as denial of service (DoS), message disclosure by unauthorized snooping, and unauthorized message creation and modification.
+
+In general, an attacker can surreptitiously intercept information, attempt to create unauthorized information, and/or send modified or reordered information. There might be a risk that an attacker can impersonate an SNMP manager and illicitly acquire and tamper with the information. Even though the information is encrypted, a replay attack might be possible.
+
+For these security threats, operators need to be aware that no sufficient authentication and encryption mechanisms are provided between the SNMP manager (TRC-PE) and SNMP agents (T-PE) in the SNMP version 2 framework. To minimize the risk, the SNMP entity needs to be properly configured so that only authorized SNMP managers and agents can access information and exchange it with each other. Particular attention to the credence and information integrity is necessary.
+
+Therefore, it is recommended that the implementers consider security features, such as authentication and encryption mechanisms, at the application level in the case where SNMP messages are open to an insecure domain in order to prevent possibilities of attacks from such a domain. At the same time, operators need to consider physical and/or logical SNMP traffic separation, packet filtering from an unauthorized SNMP manager (TRC-PE) and SNMP agents (T-PE). Operators should note that a long-term solution would be to consider implementing the SNMP version 3 framework and its security control model described in [b-IETF RFC 3414] and [b-IETF RFC 3415]. However, that is outside of the scope of this Recommendation.
+
+## Appendix I
+
+### Management information base
+
+(This appendix does not form an integral part of this Recommendation.)
+
+The following Tables I.1, I.2 and I.3 shows the management information base (MIB) referenced respectively in [b-IETF RFC 1213], [b-IETF RFC 4293] and [b-IETF RFC 2863].
+
+**Table I.1 – Management information base [b-IETF RFC 1213]**
+
+| RFC | MIB object | | Type | Object identifier |
+|------------|-------------------|---------------|-------------|--------------------------|
+| 1213 | mib-2 | | | 1.3.6.1.2.1 |
+| | System | | | 1.3.6.1.2.1.1 |
+| | | sysDescr | SCALAR | 1.3.6.1.2.1.1.1 |
+| | | sysObjectID | SCALAR | 1.3.6.1.2.1.1.2 |
+| | | sysName | SCALAR | 1.3.6.1.2.1.1.5 |
+| | Interface | | | 1.3.6.1.2.1.2 |
+| | | ifTable | TABLE | 1.3.6.1.2.1.2.2 |
+| | | ifEntry | ENTRY | 1.3.6.1.2.1.2.2.1 |
+| | | ifIndex | TABULAR | 1.3.6.1.2.1.2.2.1.1 |
+| | | ifDescr | TABULAR | 1.3.6.1.2.1.2.2.1.2 |
+| | | ifType | TABULAR | 1.3.6.1.2.1.2.2.1.3 |
+| | | ifSpeed | TABULAR | 1.3.6.1.2.1.2.2.1.5 |
+| | | ifPhysAddress | TABULAR | 1.3.6.1.2.1.2.2.1.6 |
+| | | ifAdminStatus | TABULAR | 1.3.6.1.2.1.2.2.1.7 |
+| | | ifOperStatus | TABULAR | 1.3.6.1.2.1.2.2.1.8 |
+
+**Table I.2 – Management information base [b-IETF RFC 4293]**
+
+| RFC | MIB object | | Type | Object identifier |
+|------------|-------------------|-------------------|-------------|--------------------------|
+| 4293 | mib-2 | | | 1.3.6.1.2.1 |
+| | Ip | | | 1.3.6.1.2.1.4 |
+| | | ipv6IpForwarding | SCALAR | 1.3.6.1.2.1.4.25 |
+| | | ipAddressTable | TABLE | 1.3.6.1.2.1.4.34 |
+| | | ipAddressEntry | ENTRY | 1.3.6.1.2.1.4.34.1 |
+| | | ipAddressAddrType | TABULAR | 1.3.6.1.2.1.4.34.1.1 |
+| | | ipAddressAddr | TABULAR | 1.3.6.1.2.1.4.34.1.2 |
+| | | ipAddressIfIndex | TABULAR | 1.3.6.1.2.1.4.34.1.3 |
+| | | ipAddressPrefix | TABULAR | 1.3.6.1.2.1.4.34.1.5 |
+
+**Table I.3 – Management information base [b-IETF RFC 2863]**
+
+| RFC | MIB object | | | | | Type | Object identifier |
+|------------|-------------------|--|--|--|--|-------------|--------------------------|
+| 2863 | mib-2 | | | | | | 1.3.6.1.2.1 |
+| | ifMIBObjects | | | | | | 1.3.6.1.2.1.31.1 |
+| | ifIXTable | | | | | TABLE | 1.3.6.1.2.1.31.1.1 |
+| | ifIXEntry | | | | | ENTRY | 1.3.6.1.2.1.31.1.1.1 |
+| | ifName | | | | | TABULAR | 1.3.6.1.2.1.31.1.1.1.1 |
+| | ifHighSpeed | | | | | TABULAR | 1.3.6.1.2.1.31.1.1.1.15 |
+| | ifStackTable | | | | | TABLE | 1.3.6.1.2.1.31.1.2 |
+| | ifStackEntry | | | | | ENTRY | 1.3.6.1.2.1.31.1.2.1 |
+| | ifStackStatus | | | | | TABULAR | 1.3.6.1.2.1.31.1.2.1.3 |
+| | | | | | | | |
+
+## Bibliography
+
+- [b-IETF RFC 1213] IETF RFC 1213 (1991), *Management Information Base for Network Management of TCP/IP-based internets: MIB-II*.
+- [b-IETF RFC 2863] IETF RFC 2863 (2000), *The Interfaces Group MIB*.
+- [b-IETF RFC 3414] IETF RFC 3414 (2002), *User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)*.
+- [b-IETF RFC 3415] IETF RFC 3415 (2002), *View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)*.
+- [b-IETF RFC 4293] IETF RFC 4293 (2006), *Management Information Base for the Internet Protocol (IP)*.
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|---------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3611-200906-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..52da08667aedc74bf9e8174011f34d42212ae2f6
--- /dev/null
+++ b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c49b601f376633a0555d0f401654fca7a4b0f26a937283a8372e055b088fe7a5
+size 57987
diff --git a/marked/Q/T-REC-Q.3611-200906-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f77ce29be3be1b6ffdcc8305394191292f6a4395
--- /dev/null
+++ b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:898c1662077f0cfb188edf334f0bf83a96acdc117e6851d6271895eada223535
+size 15254
diff --git a/marked/Q/T-REC-Q.3611-200906-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..627b2031b36035789f33c1afe9b7d94ce86f6716
--- /dev/null
+++ b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b6fae3cf6ae4e0a1d84627826421ebda7e2100f2da11c6be301d79d5ff94dfde
+size 102401
diff --git a/marked/Q/T-REC-Q.3611-200906-I_PDF-E/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b0cddb19d40776ab0c6bc3e35dcc5800e88a1e16
--- /dev/null
+++ b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:23e2e28cce5610d33e10ea92c6e449378957cfc39228de7e47cf36ad46dfe423
+size 121794
diff --git a/marked/Q/T-REC-Q.3611-200906-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c88f028cb9d529f4c0f605e96af99c5af4f5f8e7
--- /dev/null
+++ b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:df162d93b5b724da2ee602ac70ef229676c2924610b44b26ac49d36a515248a5
+size 14770
diff --git a/marked/Q/T-REC-Q.3611-200906-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ce8817dc8904bb7ad00b22357a8a54175c375f51
--- /dev/null
+++ b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a6c3eb9dd0f7592365794abc06c9c67c49af8711ab8880b190b66fa1fd9dba4f
+size 3934
diff --git a/marked/Q/T-REC-Q.3611-200906-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..61b0abd298fa62ea40473ea4d3f9eafd20a18e01
--- /dev/null
+++ b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae1f29a9790f3a8eebcf8069e6d13e9b413535b3affaa89c09fb13917b1e1369
+size 53180
diff --git a/marked/Q/T-REC-Q.3611-200906-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64957d02c2c8e10ec2cea14107f5ea160fbef90b
--- /dev/null
+++ b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0608443c0e8aa140fc99e4749ad23a6d6a63045b619d4460cebfa536b7e4e21d
+size 50539
diff --git a/marked/Q/T-REC-Q.3611-200906-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..33d0a96bdc55a65c9991df70fde5895cde3eeb20
--- /dev/null
+++ b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c53a07fad611735f0ac9b7e5e147e7a0ec93138aa43a9791d15e1eec791ec87f
+size 98989
diff --git a/marked/Q/T-REC-Q.3611-200906-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..02b9a67548c1b81777a1923a0e1b22a982259c15
--- /dev/null
+++ b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:13e2e59622ad90b3e1f37b262a100a29bb58bee6689e96a6120f9d99ec1b339f
+size 189436
diff --git a/marked/Q/T-REC-Q.3611-200906-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2353cf388b56a93f2a381190c863a7146302322a
--- /dev/null
+++ b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:73a03c767de81cfdd5c9935307c2d2553166a1f217eba614890bfd9be592b5a4
+size 46441
diff --git a/marked/Q/T-REC-Q.3612-201106-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3612-201106-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..5bb25678ab8a46d0542d5b9290296b935264042a
--- /dev/null
+++ b/marked/Q/T-REC-Q.3612-201106-I_PDF-E/raw.md
@@ -0,0 +1,1846 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.3612**
+
+(06/2011)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Signalling requirements and protocols for the NGN –
+Service and session control protocols – supplementary
+services
+
+---
+
+**Signalling requirements and protocol profiles
+for IP Centrex service**
+
+Recommendation ITU-T Q.3612
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|---------------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3999 |
+| General | Q.3000–Q.3029 |
+| Network signalling and control functional architecture | Q.3030–Q.3099 |
+| Network data organization within the NGN | Q.3100–Q.3129 |
+| Bearer control signalling | Q.3130–Q.3179 |
+| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 |
+| Resource control protocols | Q.3300–Q.3369 |
+| Service and session control protocols | Q.3400–Q.3499 |
+| Service and session control protocols – supplementary services | Q.3600–Q.3649 |
+| NGN applications | Q.3700–Q.3849 |
+| Testing for NGN networks | Q.3900–Q.3999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## Recommendation ITU-T Q.3612
+
+## Signalling requirements and protocol profiles for IP Centrex service
+
+## Summary
+
+The IP Centrex service, which is defined in Recommendation ITU-T Y.2211, can be provided over either IMS-based or call-server based components. This Recommendation provides the general architecture of the IP Centrex service, and specifies the signalling requirements and protocol profiles for the IP Centrex service. The signalling flows of the IP Centrex service are also provided in this Recommendation.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group |
+|---------|----------------|------------|-------------|
+| 1.0 | ITU-T Q.3612 | 2011-06-29 | 11 |
+
+## Keywords
+
+IP Centrex, NGN, SDP, SIP.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2012
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+###### Page
+
+| | | |
+|------|----------------------------------------------------------------------------------|----|
+| 1 | Scope ..... | 1 |
+| 2 | References..... | 1 |
+| 3 | Definitions ..... | 2 |
+| 3.1 | Terms defined elsewhere ..... | 2 |
+| 3.2 | Terms defined within this Recommendation..... | 2 |
+| 4 | Abbreviations and acronyms ..... | 2 |
+| 5 | Conventions ..... | 3 |
+| 6 | Service architecture ..... | 3 |
+| 6.1 | General architecture..... | 3 |
+| 6.2 | Functional entities involved in IP Centrex service..... | 4 |
+| 7 | Signalling requirements ..... | 5 |
+| 7.1 | General description..... | 5 |
+| 7.2 | Signalling requirements..... | 5 |
+| 8 | Protocol profiles..... | 18 |
+| 9 | Security considerations ..... | 19 |
+| | Appendix I – IMS-based signalling flows for the IP Centrex service ..... | 20 |
+| I.1 | Internal communication..... | 20 |
+| I.2 | Outgoing communication ..... | 22 |
+| I.3 | Incoming communication..... | 23 |
+| I.4 | Originating identification presentation..... | 24 |
+| I.5 | Originating identification restriction ..... | 26 |
+| I.6 | Terminating identification presentation ..... | 28 |
+| I.7 | Terminating identification restriction..... | 29 |
+| I.8 | Communication transfer ..... | 31 |
+| I.9 | Communication diversion ..... | 32 |
+| I.10 | Communication pickup ..... | 34 |
+| I.11 | Communication hold ..... | 35 |
+| | Appendix II – Call server based signalling flows for the IP Centrex service..... | 37 |
+| | Bibliography..... | 39 |
+
+# **Introduction**
+
+The IP Centrex service is a PBX-like service, but it is provided by the central office rather than the customer's premises and is implemented over an IP-basic network, such as an NGN. The IP Centrex service is defined in [ITU-T Y.2211]. This Recommendation specifies the signalling requirements and protocol profiles for the IP Centrex service provided over an NGN. The signalling flows of the IP Centrex service are also provided in this Recommendation.
+
+## Recommendation ITU-T Q.3612
+
+## Signalling requirements and protocol profiles for IP Centrex service
+
+# 1 Scope
+
+This Recommendation specifies signalling requirements and protocol profiles of the IP Centrex service. The Recommendation also contains signalling flows.
+
+The IP Centrex service can be provided over either IMS-based or call-server-based networks, as per [ITU-T Y.2211].
+
+# 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.3402] Recommendation ITU-T Q.3402 (2008), *NGN UNI signalling profile (Protocol set 1)*.
+- [ITU-T Y.2211] Recommendation ITU-T Y.2211 (2007), *IMS-based real-time conversational multimedia services over NGN*.
+- [ITU-T Y.2701] Recommendation ITU-T Y.2701 (2007), *Security requirements for NGN release 1*.
+- [IETF RFC 2246] IETF RFC 2246 (1999), *The TLS Protocol Version 1.0*.
+- [IETF RFC 2401] IETF RFC 2401 (1998), *Security Architecture for the Internet Protocol*.
+- [IETF RFC 2633] IETF RFC 2633 (1999), *S/MIME Version 3 Message Specification*.
+- [IETF RFC 3262] IETF RFC 3262 (2002), *Reliability of Provisional Responses in the Session Initiation Protocol (SIP)*.
+- [IETF RFC 3323] IETF RFC 3323 (2002), *A Privacy Mechanism for the Session Initiation Protocol (SIP)*.
+- [IETF RFC 3325] IETF RFC 3325 (2002), *Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks*.
+- [IETF RFC 3515] IETF RFC 3325 (2002), *The Session Initiation Protocol (SIP) Refer Method*.
+- [IETF RFC 3891] IETF RFC 3891 (2004), *The Session Initiation Protocol (SIP) "Replaces" Header*.
+- [IETF RFC 3892] IETF RFC 3892 (2004), *The Session Initiation Protocol (SIP) Referred-By Mechanism*.
+- [IETF RFC 4244] IETF RFC 4244 (2005), *An Extension to the Session Initiation Protocol (SIP) for Request History Information*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 picking-up endpoint/user** [b-ITU-T H.450.5]: A user/endpoint that picks-up a parked call or an alerting call.
+
+**3.1.2 pickup group** [b-ITU-T H.450.5]: A group of users that may be notified when one of the group members receives a call that can be picked up. Each group member is authorized to answer the call by using SS-PICKUP.
+
+## 3.2 Terms defined within this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 Centrex service:** A services package which provides an emulation of a private branch exchange (PBX) by using special programming software at the central office, instead of at the customer's premises.
+
+NOTE – The typical feature is that users within the same group can communicate with each other by using the private number instead of the public number (i.e., full subscriber number).
+
+**3.2.2 communication pickup:** A service that enables an IP Centrex user to pick up an alerting call within the same Centrex group when the alerted user is unavailable to answer the call.
+
+**3.2.3 group pickup:** One of the two service features for communication pickup. Group pickup enables a pickup group user to pick up an alerting call within the same pickup group without dialling the picked-up user's private number.
+
+**3.2.4 IP Centrex service:** A certain type of Centrex service which is provided over an IP-based network, such as an NGN. The typical service features included in the IP Centrex service are defined in [ITU-T Y.2211].
+
+**3.2.5 picked-up user:** A user whose call is picked up by a picking-up user.
+
+**3.2.6 private number:** A certain number only used within a given Centrex group. It is shorter than the user's local public number, and typically has only three, four or five digits, depending on how large the Centrex group is.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|----------|------------------------------------------------------|
+| AGC-FE | Access Gateway Control Functional Entity |
+| ASF | Application Service Function |
+| AS-FE | Application Server Functional Entity |
+| EUF | End-User Function |
+| I-CSC-FE | Interrogating Call Session Control Functional Entity |
+| IMS | IP Multimedia Subsystem |
+| ISDN | Integrated Services Digital Network |
+| MGC-FE | Media Gateway Control Functional Entity |
+| PBX | Private Branch eXchange |
+| P-CSC-FE | Proxy Call-Session-Control Functional Entity |
+| SCF | Service Control Function |
+
+| | |
+|----------|------------------------------------------------|
+| S-CSC-FE | Serving Call-Session-Control Functional Entity |
+| SDP | Session Description Protocol |
+| SIP | Session Initiation Protocol |
+| SUP-FE | Service User Profile Functional Entity |
+| TLS | Transport Layer Security |
+| UE | User Equipment |
+| UNI | User Network Interface |
+
+# 5 Conventions
+
+In this Recommendation:
+
+The keyword "shall" indicates 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 "shall not" 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 keywords "should not" indicate a requirement which is not recommended but which is not specifically prohibited. Thus, conformance with this Recommendation can still be claimed even if this requirement is present.
+
+The 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 Service architecture
+
+## 6.1 General architecture
+
+The IP Centrex service as defined in [ITU-T Y.2211] can be provided over either an IMS-based or a call-server-based subsystem. Figure 6-1 depicts the general architecture [ITU-T Y.2211].
+
+The IP Centrex service logic and service executing environments are provided by an application service function (ASF) within the service stratum. The originating and terminating IP Centrex service logics serving for a designated Centrex group are provided by one ASF. When serving the originating network, the ASF performs the originating IP Centrex service logic invoked by the originating service control function (SCF), which shall include internal communication and originating identification restriction service features. When serving the terminating network, the ASF performs the terminating IP Centrex service logic invoked by the terminating SCF, which shall include the internal communication, the originating identification presentation and the terminating identification restriction.
+
+The SCF holds the service subscription profile for the NGN user and performs the service-trigger function. The end user who subscribes to the IP Centrex service may reside in the IMS component or in the call-server component. Both of these components can invoke the IP Centrex service.
+
+
+
+Figure 6-1: The general architecture of IP Centrex service. This diagram shows the architecture across two networks: Originating network and Terminating network, separated by a dashed vertical line. On the left (Originating network), an 'Originating end user function' box contains 'NGN terminal' and 'Legacy terminal'. It connects via 'NGN UNI' to a 'Service stratum' box labeled 'ASF'. Inside 'ASF' is a dashed oval 'Originating IP centrex service logic'. Below 'Service stratum' is an 'SCF' box containing 'Call server component' and 'IMS component'. At the bottom is a 'Transport stratum' box. On the right (Terminating network), the structure is mirrored: 'Transport stratum' at the bottom, 'SCF' box with 'Call server component' and 'IMS component' above it, and 'Service stratum' box labeled 'ASF' with a dashed oval 'Terminating IP centrex service logic' at the top. It connects via 'NGN UNI' to a 'Terminating end user function' box containing 'NGN terminal' and 'Legacy terminal'. A reference code 'Q.3612(11)\_F6-1' is at the bottom right.
+
+**Figure 6-1 – The general architecture of IP Centrex service**
+
+## 6.2 Functional entities involved in IP Centrex service
+
+Figure 6-2 illustrates the functional entities involved in the IP Centrex service.
+
+In the originating network, the originating end-user function is the end user that originates the IP Centrex session. If the end-user function resides in the call-server-based component, the related functional entities shall be the call server, the service-user-profile functional entity (SUP-FE) and the application-server functional entity (AS-FE). When the end-user function resides in the IMS-based component, the related functional entities shall be the access gateway control functional entity (AGC-FE), the proxy/serving call-session-control functional entity (P/S-CSC-FE) and the application server functional entity (AS-FE).
+
+In the terminating network, the terminating end-user function is the end user that terminates the IP Centrex session. When the end user resides in the call-server-based component, the related functional entities shall be the call server, the SUP-FE and the AS-FE. When the end user resides in the IMS-based component, the related functional entities shall be the AGC-FE, the P/S-CSC-FE, the interrogating call session control functional entity (I-CSC-FE) and the AS-FE.
+
+
+
+Figure 6-2: The functional entities involved in the IP Centrex service. This diagram shows functional entities across 'Originating network' and 'Terminating network', separated by a dashed vertical line. At the top, a box 'AS-FE (For IP centrex service)' contains two dashed ovals: 'Originating IP centrex service logic' (left) and 'Terminating IP centrex service logic' (right). Below this, on the left (Originating network), a box contains 'SUP-FE', 'Call server', 'MRC-FE', 'S-CSC-FE', 'P-CSC-FE', and 'AGCF'. On the right (Terminating network), a box contains 'SUP-FE', 'I-CSC-FE' (dashed box), 'S-CSC-FE', 'MRC-FE', 'Call server', 'AGCF', and 'P-CSC-FE'. Both sides connect to a 'Transport stratum' box at the bottom. The 'Originating end user function' (left) and 'Terminating end user function' (right) both connect to their respective 'Transport stratum' boxes and also to the 'NGN terminal' within their side's user function box. A reference code 'Q.3612(11)\_F6-2' is at the bottom right.
+
+**Figure 6-2 – The functional entities involved in the IP Centrex service**
+
+# **7 Signalling requirements**
+
+## **7.1 General description**
+
+According to [ITU-T Y.2211] and service features used in the current PBX service, this Recommendation defines the signalling requirements of the following service features:
+
+- 1) Internal communication
+- 2) Outgoing communication
+- 3) Incoming communication
+- 4) Originating identification presentation
+- 5) Originating identification restriction
+- 6) Terminating identification presentation
+- 7) Terminating identification restriction
+- 8) Communication transfer
+- 9) Communication diversion
+- 10) Communication pickup
+- 11) Communication hold
+
+## **7.2 Signalling requirements**
+
+### **7.2.1 Internal communication**
+
+The internal communication service feature enables a Centrex user to communicate with another user in the same Centrex Group with a private number.
+
+When initiating a call, the originating party can directly dial the private number of the terminating party. Based on the terminating party's service profile, if the identities of the originating party can be presented to the terminating party, the private number of the originating party shall be presented.
+
+#### **7.2.1.1 Requirements for the originating user equipment (UE)**
+
+When the originating user equipment (UE) initiates an INVITE request, the private number of the terminating party shall be included in the Request-URI.
+
+#### **7.2.1.2 Requirements for the originating access gateway control functional entity (AGC-FE)**
+
+When the originating AGC-FE initiates an INVITE request, the private number of terminating party shall be included in the Request-URI.
+
+#### **7.2.1.3 Requirements for the originating proxy call-session-control functional entity (P-CSC-FE)**
+
+No special requirement for this FE.
+
+#### **7.2.1.4 Requirements for the originating serving call-session-control functional entity (S-CSC-FE)**
+
+No special requirement for this FE.
+
+#### **7.2.1.5 Requirements for the originating call server**
+
+No special requirement for this FE.
+
+#### **7.2.1.6 Requirements for the application server functional entity (AS-FE)**
+
+When sending an INVITE request to the terminating interrogating call-session-control functional entity (I-CSC-FE), the terminating S-CSC-FE or the terminating call server, the AS-FE shall:
+
+- 1) include the private number of the originating party in the P-Asserted-identity header field.
+- 2) include the public user identity of the terminating party in the Request-URI.
+
+#### **7.2.1.7 Requirements for the terminating call server**
+
+No special requirement for this FE.
+
+#### **7.2.1.8 Requirements for the terminating interrogating call session control functional entity (I-CSC-FE)**
+
+No special requirement for this FE.
+
+#### **7.2.1.9 Requirements for the terminating S-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.1.10 Requirements for the terminating P-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.1.11 Requirements for the terminating UE**
+
+If the identities of the originating party are allowed to be presented to the terminating party, the private number shall be presented.
+
+#### **7.2.1.12 Requirements for the terminating AGC-FE**
+
+If the identities of the originating party are allowed to be presented to the terminating party, the private number shall be presented.
+
+### **7.2.2 Outgoing communication**
+
+The outgoing communication service feature enables a Centrex user to initiate the communication with a public user.
+
+#### **7.2.2.1 Requirements for the originating UE**
+
+No special requirement for this FE.
+
+#### **7.2.2.2 Requirements for the originating AGC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.2.3 Requirements for the originating P-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.2.4 Requirements for the originating S-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.2.5 Requirements for the originating call server**
+
+No special requirement for this FE.
+
+#### **7.2.2.6 Requirements for the AS-FE**
+
+When the AS-FE sends an INVITE request to the originating S-CSC-FE or the originating call server, the public user identity of the terminating party shall be included in the Request-URI header field.
+
+#### **7.2.2.7 Requirements for the terminating call server**
+
+No special requirement for this FE.
+
+#### **7.2.2.8 Requirements for the terminating I-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.2.9 Requirements for the terminating S-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.2.10 Requirements for the terminating P-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.2.11 Requirements for the terminating UE**
+
+No special requirement for this FE.
+
+#### **7.2.2.12 Requirements for the terminating AGC-FE**
+
+No special requirement for this FE.
+
+### **7.2.3 Incoming communication**
+
+The incoming communication service feature enables a public user to initiate the communication with a Centrex user.
+
+#### **7.2.3.1 Requirements for the originating UE**
+
+No special requirement for this FE.
+
+#### **7.2.3.2 Requirements for the originating AGC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.3.3 Requirements for the originating P-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.3.4 Requirements for the originating S-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.3.5 Requirements for the originating call server**
+
+No special requirement for this FE.
+
+#### **7.2.3.6 Requirements for the AS-FE**
+
+When the AS-FE sends an INVITE request to the terminating I-CSC-FE, or the terminating S-CSC-FE, or the call server, the originating party's identities contained in the P-Asserted-Identity header field can be used by the terminating party to call back directly.
+
+If the outgoing communication needs a prefix, the public user identity with the prefix shall be presented to the terminating party in the incoming communication.
+
+#### **7.2.3.7 Requirements for the terminating call server**
+
+No special requirement for this FE.
+
+#### **7.2.3.8 Requirements for the terminating I-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.3.9 Requirements for the terminating S-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.3.10 Requirements for the terminating P-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.3.11 Requirements for the terminating UE**
+
+No special requirement for this FE.
+
+#### **7.2.3.12 Requirements for the terminating AGC-FE**
+
+No special requirement for this FE.
+
+### **7.2.4 Originating identification presentation**
+
+The originating identification presentation service feature enables the originating party's identification to be presented to the terminating party.
+
+- 1) The private number of the originating party shall be presented to the terminating party in the internal communication scenario.
+- 2) The public user identity of the originating party shall be presented to the terminating party in the incoming communication scenario.
+
+This service feature can be activated by the terminating party.
+
+#### **7.2.4.1 Requirements for the originating UE**
+
+No special requirement for this FE.
+
+#### **7.2.4.2 Requirements for the originating AGC-FE**
+
+When sending an INVITE request to the originating S-CSC-FE, the AGC-FE shall insert a P-Asserted-Identity header field. The P-Asserted-Identity header field shall be set to the public user identity which has been registered in the network by the originating party.
+
+#### **7.2.4.3 Requirements for the originating P-CSC-FE**
+
+When sending an INVITE request to the originating S-CSC-FE, the P-CSC-FE shall insert a P-Asserted-Identity header field. The P-Asserted-Identity header field shall be set to the public user identity which has been registered in the network by the originating party.
+
+#### **7.2.4.4 Requirements for the originating S-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.4.5 Requirements for the originating call server**
+
+When sending an INVITE request to the originating AS-FE, the call server shall insert a P-Asserted-Identity header field. The P-Asserted-Identity header field shall be set to the public user identity which has been registered in the network by the originating party.
+
+#### **7.2.4.6 Requirements for the AS-FE**
+
+When AS-FE receives an INVITE request from the terminating S-CSC-FE or call server, the terminating party AS-FE shall:
+
+- 1) verify whether the terminating party has activated the originating identification presentation service. If not, the AS-FE shall add the Privacy header field, if it is not contained in the INVITE request, and set the value to "id", then set the From header field to "Anonymous" and send the INVITE request to the terminating S-CSC-FE or the call server.
+
+NOTE – The value of the Privacy header field refers to [IETF RFC 3323] and [IETF RFC 3325].
+
+- 2) verify whether the originating party and the terminating party are in the same Centrex group. If they are, then the AS-FE shall change the public user identity of the originating party in the P-Asserted-Identity header field into Private number.
+
+#### **7.2.4.7 Requirements for the terminating call server**
+
+When receiving an INVITE request,
+
+- 1) if the Privacy header field is contained with the value unequal to "none", the terminating call server shall delete the P-Asserted-Identity header field if it is contained in the INVITE request before forwarding the message to the terminating party.
+- 2) otherwise, the P-Asserted-Identity header field shall be forwarded to the terminating party.
+
+#### **7.2.4.8 Requirements for the terminating I-CSCF-FE**
+
+No special requirement for this FE.
+
+#### **7.2.4.9 Requirements for the terminating S-CSCF-FE**
+
+No special requirement for this FE.
+
+#### **7.2.4.10 Requirements for the terminating P-CSCF-FE**
+
+When receiving an INVITE request,
+
+- 1) if the Privacy header field is contained with the value unequal to "none", the P-CSCF-FE shall delete the P-Asserted-Identity header field if it is contained in the INVITE request before forwarding the INVITE request to the terminating party.
+- 2) otherwise, the P-Asserted-Identity header field shall be forwarded to the terminating party.
+
+#### **7.2.4.11 Requirements for the terminating UE**
+
+If a P-Asserted-Identity header field is included in an INVITE request, the originating identification in the header field shall be presented to the terminating party. If more than one P-Asserted-Identity header field is received, the identity that is presented will be decided by a local policy.
+
+If the P-Asserted-Identity header field is not contained in the INVITE request, the information about the FROM header field shall be presented to the terminating party.
+
+#### **7.2.4.12 Requirements for the terminating AGC-FE**
+
+When receiving an INVITE request,
+
+- 1) if a P-Asserted-Identity header field is contained in the INVITE request, and the Privacy header field is not contained or is contained with the value setting at "none", the information about the P-Asserted-Identity shall be presented to the terminating party.
+- 2) otherwise, the information about the FROM header field shall be presented to the terminating party.
+
+### **7.2.5 Originating identification restriction**
+
+The originating identification-restriction-service feature restricts the calling party's identities to be presented to the called party, even when the called party has activated the originating identification presentation.
+
+This service feature shall be activated by the calling party.
+
+#### **7.2.5.1 Requirements for the originating UE**
+
+No special requirement for this FE.
+
+#### **7.2.5.2 Requirements for the originating AGC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.5.3 Requirements for the originating P-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.5.4 Requirements for the originating S-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.5.5 Requirements for the originating call server**
+
+No special requirement for this FE.
+
+#### **7.2.5.6 Requirements for the AS-FE**
+
+When the AS-FE receives an INVITE request from the originating S-CSC-FE or call server and executes the originating IP Centrex service logic, the INVITE request sent from the AS-FE shall:
+
+- 1) include the Privacy header field with the value setting at "id";
+- 2) set the From header field to "Anonymous".
+
+#### **7.2.5.7 Requirements for the terminating call server**
+
+When receiving an INVITE request, the terminating call server shall delete the P-Asserted-Identity header field before forwarding the message to the called party if the Privacy header field is contained with the value unequal to "none".
+
+#### **7.2.5.8 Requirements for the terminating I-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.5.9 Requirements for the terminating S-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.5.10 Requirements for the terminating P-CSC-FE**
+
+When receiving an INVITE request, the P-CSC-FE shall delete the P-Asserted-Identity header field before forwarding the message to the called party if the Privacy header field is contained with the value unequal to "none".
+
+#### **7.2.5.11 Requirements for the terminating UE**
+
+When receiving an INVITE request, the information about the FROM header field shall be presented to the called party.
+
+#### **7.2.5.12 Requirements for the terminating AGC-FE**
+
+When receiving an INVITE request, if a Privacy header field is contained with the value unequal to "none", the information of the FROM header field shall be presented to the called party.
+
+### **7.2.6 Terminating identification presentation**
+
+#### **7.2.6.1 Requirements for the originating UE**
+
+If a 200 (OK) response for the INVITE request includes more than one P-Asserted-Identity header field, the UE shall select one and present it to the originating party.
+
+#### **7.2.6.2 Requirements for the originating AGC-FE**
+
+When receiving a 200 (OK) response to the INVITE request, if the Privacy header field is not included in this response or the Privacy header field which is included with a value of "none", the AGC-FE shall provide the information extracted from P-Asserted-Identity to the Originating UE.
+
+NOTE – If more than one P-Asserted-Identity header field is received, the identity that is presented to the originating party will be decided by a local policy.
+
+#### **7.2.6.3 Requirements for the originating P-CSC-FE**
+
+When receiving a 200 (OK) response to the INVITE request, if the Privacy header field is not included in this response or the Privacy header field which is included in this response has a value of "none", the P-CSC-FE shall provide the P-Asserted-Identity to the originating UE.
+
+#### **7.2.6.4 Requirements for the originating S-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.6.5 Requirements for the originating call server**
+
+When receiving a 200 (OK) response to the INVITE request, if the Privacy header field is not included in this response or the Privacy header field which is included in this response has a value of "none", the originating call server shall provide the information extracted from the P-Asserted-Identity to the originating UE.
+
+NOTE – If more than one P-Asserted-Identity header field is received, the identity that is presented to the originating party will be decided by a local policy.
+
+#### **7.2.6.6 Requirements for the AS-FE**
+
+When AS-FE receives a 200 (OK) response to the INVITE request from the originating S-CSC-FE or call server, AS-FE shall:
+
+- a) verify whether the originating party has activated the terminating identification presentation service. If not, the AS-FE shall add the Privacy header field if it is not contained in the 200 (OK) response and set the value to "id", then send this response to the originating S-CSC-FE or the originating call server, and
+- b) verify whether the originating party and the terminating party are in the same Centrex. If they are, then the AS-FE shall change the public user identity of the terminating party in the P-Asserted-Identity into private number.
+
+#### **7.2.6.7 Requirements for the terminating call server**
+
+When the terminating party answers the call, the terminating call server shall insert a P-Asserted-Identity header field into a 200 (OK) response to the INVITE request before forwarding this 200 OK. The P-Asserted-Identity shall be set to the public user identity of the terminating party which has been registered in the network by the terminating party.
+
+#### **7.2.6.8 Requirements for the terminating I-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.6.9 Requirements for the terminating S-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.6.10 Requirements for the terminating P-CSC-FE**
+
+When the terminating P-CSC-FE receives a 200 (OK) response to the INVITE request from the terminating UE. The Terminating P-CSC-FE shall then insert a P-Asserted-Identity header field into the 200 (OK) response before forwarding it to the terminating S-CSC-FE. The P-Asserted-Identity shall be set to the public user identity which has been registered in the network by the terminating party.
+
+#### **7.2.6.11 Requirements for the terminating UE**
+
+No special requirement for this FE.
+
+#### **7.2.6.12 Requirements for the terminating AGC-FE**
+
+When the terminating party answers the call, the terminating AGC-FE shall insert a P-Asserted-Identity header field into a 200 (OK) response to the INVITE request before forwarding this 200 (OK) response to the terminating S-CSC-FE. The P-Asserted-Identity shall be set to the public user identity which has been registered in the network by the terminating party.
+
+### **7.2.7 Terminating identification restriction**
+
+The terminating identification restriction service feature restricts the terminating party's identities to be presented to the originating party.
+
+NOTE – In this case, the terminating party means the party who answers the call.
+
+This service feature shall be activated by the terminating party.
+
+#### **7.2.7.1 Requirements for the originating UE**
+
+No special requirement for this FE.
+
+NOTE – If there is no P-Asserted-Identity in a received 200 (OK) response to the INVITE request, it is recommended that the originating UE does not present any information about the terminating party's identity, not even that contained in the To header field to the originating party.
+
+#### **7.2.7.2 Requirements for the originating AGC-FE**
+
+When receiving a 200 (OK) response to the INVITE request, if the Privacy header field is set to "id", "header" or "user", the originating AGC-FE shall not present the terminating party's identity to the originating party.
+
+#### **7.2.7.3 Requirements for the originating P-CSC-FE**
+
+When receiving a 200 (OK) response to the INVITE request, if the Privacy header field which has a value of "id", "header" or "user" is included in the response, the originating P-CSC-FE shall delete the P-Asserted-Identity header field before forwarding this response to the originating UE.
+
+#### **7.2.7.4 Requirements for the originating S-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.7.5 Requirements for the originating call server**
+
+When receiving a 200 (OK) response to the INVITE request, and the Privacy header field which has a value of "id", "header" or "user" is included in the response, the originating call server shall not provide the originating party with the terminating party's identity.
+
+#### **7.2.7.6 Requirements for the AS-FE**
+
+When the AS-FE receives a 200 (OK) response to the INVITE request from the terminating S-CSC-FE or call server, the AS-FE shall add the Privacy header field in the 200 (OK) response to the INVITE request and set the value to "id", then send this response to the terminating S-CSC-FE or call server.
+
+#### **7.2.7.7 Requirements for the terminating call server**
+
+When the terminating party answers the call, the terminating call server shall insert a P-Asserted-Identity header field into a 200 (OK) response to the INVITE request before forwarding this 200 (OK) response. The P-Asserted-Identity shall be set to the public user identity which has been registered in the network by the terminating party.
+
+#### **7.2.7.8 Requirements for the terminating I-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.7.9 Requirements for the terminating S-CSC-FE**
+
+No special requirement for this FE.
+
+#### **7.2.7.10 Requirements for the terminating P-CSC-FE**
+
+When the terminating P-CSC-FE receives a 200 (OK) response to the INVITE request from the terminating UE, the terminating P-CSC-FE shall insert a P-Asserted-Identity header field into the 200 (OK) response before forwarding this 200 OK to the terminating S-CSC-FE. The P-Asserted-Identity shall be set to the public user identity which has been registered in the network by the terminating party.
+
+#### **7.2.7.11 Requirements for the terminating UE**
+
+No special requirement for this FE.
+
+#### **7.2.7.12 Requirements for the terminating AGC-FE**
+
+When the terminating party answers the call, the terminating AGC-FE shall insert a P-Asserted-Identity header field into a 200 (OK) response to the INVITE request before forwarding it to the terminating S-CSC-FE. The P-Asserted-Identity shall be set to the public user identity which has been registered in the network by the terminating party.
+
+### **7.2.8 Communication transfer**
+
+When user A and user B are in the same Centrex group, and they have set up a call, user B can transfer this call to user C which can be a Centrex user or a public user.
+
+When user B successfully transfers the call to user C, user A and user C will establish a call and the call between user A and user B will be released.
+
+If user B fails to transfer the call for some reason, for example, network congestion, or user C is busy, or user C gives no reply, then the call between user A and user B shall remain unchanged.
+
+In this service, user A is a transferee, user B is a transferor, and user C is a transfer target.
+
+#### **7.2.8.1 Requirements for the transferee UE (user A)**
+
+No special requirement for this FE.
+
+#### **7.2.8.2 Requirements for the transferee AGC-FE (user A)**
+
+No special requirement for this FE.
+
+#### **7.2.8.3 Requirements for the transferee P-CSC-FE (user A)**
+
+No special requirement for this FE.
+
+#### **7.2.8.4 Requirements for the transferee S-CSC-FE (user A)**
+
+No special requirement for this FE.
+
+#### **7.2.8.5 Requirements for the transferee call server (user A)**
+
+No special requirement for this FE.
+
+#### **7.2.8.6 Requirements for the transferor UE (user B)**
+
+The UE shall send a REFER request when user B wants to transfer the call.
+
+When the UE receives a NOTIFY message sent by the AS-FE, which indicates that the call has been transferred successfully to user C, the UE shall send a BYE message to the AS-FE to release the call between user A and user B.
+
+If the NOTIFY message sent by AS-FE indicates that the call has not been transferred successfully to user C, the UE shall not send the BYE message.
+
+#### **7.2.8.7 Requirements for the transferor AGC-FE (user B)**
+
+The AGC-FE shall send a REFER request when user B wants to transfer the call.
+
+When the AGC-FE receives a NOTIFY message, which indicates that the call has been transferred successfully to user C, the AGC-FE shall send a BYE message to the AS-FE to release the call between user A and user B.
+
+If the NOTIFY message sent by AS-FE indicates that the call has not been transferred successfully to user C, the AGC-FE shall not send the BYE message.
+
+#### **7.2.8.8 Requirements for the transferor P-CSC-FE (user B)**
+
+No special requirement for this FE.
+
+#### **7.2.8.9 Requirements for the transferor S-CSC-FE (user B)**
+
+No special requirement for this FE.
+
+#### **7.2.8.10 Requirements for the transferor call server (user B)**
+
+No special requirement for this FE.
+
+#### **7.2.8.11 Requirements for the AS-FE**
+
+When the AS-FE receives a REFER request sent from user B and the AS-FE confirms that user B wants to transfer the call to user C, the AS-FE shall:
+
+- 1) send a 202 (Accepted) response to user B
+- 2) create an INVITE request based on the REFER message, and the Request-URI shall be the URI of user C.
+
+When the AS-FE receives a 200 (OK) responses for the re-INVITE sent to user C, the AS-FE shall:
+
+- 1) send a re-INVITE message with the SDP information of user C to user A
+- 2) send a NOTIFY message to user B to indicate the successful transfer of the call to user C.
+
+When the AS-FE receives a BYE message sent by user B that wants to release the call between user A and user B, the AS-FE shall send a 200 (OK) response to user B. The BYE message shall not be forwarded to user A.
+
+#### **7.2.8.12 Requirements for the transfer target UE (user C)**
+
+No special requirement for this FE.
+
+#### **7.2.8.13 Requirements for the transfer target AGC-FE (user C)**
+
+No special requirement for this FE.
+
+#### **7.2.8.14 Requirements for the transfer target P-CSC-FE (user C)**
+
+No special requirement for this FE.
+
+#### **7.2.8.15 Requirements for the transfer target S-CSC-FE (user C)**
+
+No special requirement for this FE.
+
+#### **7.2.8.16 Requirements for the transfer target call server (user C)**
+
+No special requirement for this FE.
+
+### **7.2.9 Communication diversion**
+
+When the communication diversion service is activated for Centrex user B, the service is triggered and the call shall be forwarded to user C automatically. The service-triggered condition can be unconditional, busy or no reply. User C can be a Centrex user or a public user.
+
+#### **7.2.9.1 Requirements for the UE of user A**
+
+No special requirement for this FE.
+
+#### **7.2.9.2 Requirements for the AGC-FE of user A**
+
+No special requirement for this FE.
+
+#### **7.2.9.3 Requirements for the P-CSC-FE of user A**
+
+No special requirement for this FE.
+
+#### **7.2.9.4 Requirements for the S-CSC-FE of user A**
+
+No special requirement for this FE.
+
+#### **7.2.9.5 Requirements for the call server of user A**
+
+No special requirement for this FE.
+
+#### **7.2.9.6 Requirements for the UE of user B**
+
+No special requirement for this FE.
+
+#### **7.2.9.7 Requirements for the AGC-FE of user B**
+
+No special requirement for this FE.
+
+#### **7.2.9.8 Requirements for the P-CSC-FE of user B**
+
+No special requirement for this FE.
+
+#### **7.2.9.9 Requirements for the S-CSC-FE of user B**
+
+No special requirement for this FE.
+
+#### **7.2.9.10 Requirements for the call server of user B**
+
+No special requirement for this FE.
+
+#### **7.2.9.11 Requirements for the AS-FE**
+
+When the AS-FE confirms that the call shall be forwarded, the AS-FE shall create a new INVITE request, and:
+
+- 1) the Request-URI shall be the information of user C.
+- 2) a History header field shall be included.
+
+#### **7.2.9.12 Requirements for the UE of user C**
+
+No special requirement for this FE.
+
+#### **7.2.9.13 Requirements for the AGC-FE of user C**
+
+No special requirement for this FE.
+
+#### **7.2.9.14 Requirements for the P-CSC-FE of user C**
+
+No special requirement for this FE.
+
+#### **7.2.9.15 Requirements for the S-CSC-FE of user C**
+
+No special requirement for this FE.
+
+#### **7.2.9.16 Requirements for the call server of user C**
+
+No special requirement for this FE.
+
+### **7.2.10 Communication pickup**
+
+#### **7.2.10.1 Service description**
+
+There are two scenarios for communication pickup.
+
+##### a) Explicitly identified pickup
+
+A call is alerting user A. User B, who is in the same Centrex group as user A, is aware of the alerting call and willing to retrieve the call. User B shall identify the number of user A and connect to the calling user, typically by dialling "Pickup Access Code + picked-up user number #".
+
+##### b) Group pickup
+
+In the group pickup scenario, users in the same Centrex group can be divided into several pickup groups. Each user in the pickup group can pick up any alerting call within the same pickup group. When a call is alerting a user belonging to a pickup group, any other group member willing to retrieve the call may connect to the calling user, typically by dialling a specific pickup access code.
+
+In this scenario, the picking-up user is not required to explicitly identify the phone number of the picked-up user. If multiple calls are alerting, the first alerting call may be picked up first.
+
+#### **7.2.10.2 Requirements for the UE of calling user**
+
+No special requirement for this FE.
+
+#### **7.2.10.3 Requirements for the AGC-FE of calling user**
+
+No special requirement for this FE.
+
+#### **7.2.10.4 Requirements for the P-CSC-FE of calling user**
+
+No special requirement for this FE.
+
+#### **7.2.10.5 Requirements for the S-CSC-FE of calling user**
+
+No special requirement for this FE.
+
+#### **7.2.10.6 Requirements for the call server of calling user**
+
+No special requirement for this FE.
+
+#### **7.2.10.7 Requirements for the UE of picked-up user**
+
+No special requirement for this FE.
+
+#### **7.2.10.8 Requirements for the AGC-FE of picked-up user**
+
+No special requirement for this FE.
+
+#### **7.2.10.9 Requirements for the P-CSC-FE of picked-up user**
+
+No special requirement for this FE.
+
+#### **7.2.10.10 Requirements for the S-CSC-FE of picked-up user**
+
+No special requirement for this FE.
+
+#### **7.2.10.11 Requirements for the call server of picked-up user**
+
+No special requirement for this FE.
+
+#### **7.2.10.12 Requirements for the AS-FE**
+
+When the AS-FE confirms that the alerting call can be picked up by the picking-up user, the AS-FE shall:
+
+- 1) cancel the INVITE request sent to the picked-up user,
+- 2) update the dialogue between the AS-FE and the calling user by the newly received SDP from the picking-up user, and
+- 3) send the SDP answer which is based on the updated SDP received from the calling user to the picking-up user.
+
+#### **7.2.10.13 Requirements for the UE of the picking-up user**
+
+When the picking-up user is willing to pick up an alerting call and request the communication pickup service, the UE of the picking-up user shall send an INVITE request with a specific pickup access code to the AS-FE.
+
+#### **7.2.10.14 Requirements for the AGC-FE of the picking-up user**
+
+No special requirement for this FE.
+
+#### **7.2.10.15 Requirements for the P-CSC-FE of the picking-up user**
+
+No special requirement for this FE.
+
+#### **7.2.10.16 Requirements for the S-CSC-FE of the picking-up user**
+
+No special requirement for this FE.
+
+#### **7.2.10.17 Requirements for the call server of the picking-up user**
+
+No special requirement for this FE.
+
+### **7.2.11 Communication hold**
+
+When user A and user B have established a call, both users can place the call on hold. The user that places the call on hold is called the served user. The other user who is being put on hold is called the held user.
+
+As an enhanced function, the served user of the hold service can make a new call to user C, and it can be switched between the new call and the original call.
+
+#### **7.2.11.1 Requirements for the UE (served user)**
+
+If a UE places a call on hold and the media stream is a bi-directional media stream, it shall send a re-INVITE request containing a SDP with "a=" line set to "sendonly".
+
+#### **7.2.11.2 Requirements for the AGC-FE (served user)**
+
+If a user under the control of the AGC-FE places a call on hold and the media stream is a bi-directional media stream, AGC-FE shall send a re-INVITE request containing a SDP with "a=" line set to "sendonly".
+
+#### **7.2.11.3 Requirements for the P-CSC-FE (served user)**
+
+No special requirement for this FE.
+
+#### **7.2.11.4 Requirements for the S-CSC-FE (served user)**
+
+No special requirement for this FE.
+
+#### **7.2.11.5 Requirements for the call server (served user)**
+
+No special requirement for this FE.
+
+#### 7.2.11.6 Requirements for the AS-FE
+
+When the AS-FE receives a re-INVITE request containing an SDP with "sendonly" media, if the AS-FE wants to supply the service announcement, the AS-FE shall modify the "c=" line of the SDP to indicate the address which shall supply the service announcement.
+
+#### 7.2.11.7 Requirements for the UE (held user)
+
+No special requirement for this FE.
+
+#### 7.2.11.8 Requirements for the AGC-FE (held user)
+
+No special requirement for this FE.
+
+#### 7.2.11.9 Requirements for the P-CSC-FE (held user)
+
+No special requirement for this FE.
+
+#### 7.2.11.10 Requirements for the S-CSC-FE (held user)
+
+No special requirement for this FE.
+
+#### 7.2.11.11 Requirements for the call server (held user)
+
+No special requirement for this FE.
+
+# 8 Protocol profiles
+
+The protocol profiles for the IP Centrex service shall be based on [ITU-T Q.3402] identified in Table 8.1.
+
+**Table 8.1 – Base Recommendation for IP Centrex protocol profiles**
+
+| Profile | Interface | Protocol | Recommendation |
+|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------------|
+| NGN UNI | Between the originating end user function and the service control function in the Originating network.
Between the terminating end user function and the service control function in the terminating network. | SIP/SDP | [ITU-T Q.3402] |
+
+In terms of the IMS-based IP Centrex service, some special requirements needed for the SIP are provided in Table 8.2, as follows:
+
+- M indicates "mandatory"
+- C indicates "conditionally mandatory"
+- For the "mandatory" case, the EUF or SCF implementing the IP Centrex shall comply with the listed RFCs
+- For the "conditionally mandatory" case, the EUF or SCF implementing the IP Centrex shall comply with the listed RFCs when the stated conditions have been met.
+
+**Table 8.2 – RFCs to be supported for the IMS-based IP Centrex service**
+
+| Category | RFC | RFC Title | EUF | SCF |
+|-------------------|-----------------|---------------------------------------------------------------------------------|-----|-----|
+| SIP and Extension | [IETF RFC 3262] | Reliability of Provisional Responses in Session Initiation Protocol (SIP) | M | M |
+| SIP and Extension | [IETF RFC 3515] | The Session Initiation Protocol (SIP) Refer Method | C1 | C1 |
+| | [IETF RFC 3892] | The Session Initiation Protocol (SIP) Referred-By Mechanism | C1 | C1 |
+| | [IETF RFC 3891] | The Session Initiation Protocol (SIP) "Replaces" Header | C1 | C1 |
+| SIP and Extension | [IETF RFC 4244] | An Extension to the Session Initiation Protocol for Request History Information | C2 | C2 |
+
+C1: [IETF RFC 3515], [IETF RFC 3891] and [IETF RFC 3892] are conditionally mandatory when an explicit communication transfer service feature is required.
+C2: [IETF RFC 4244] is conditionally mandatory when communication diversion is required and communication diversion related information is transferred over the UNI.
+
+# 9 Security considerations
+
+The IP Centrex service shall use the appropriate security mechanisms to meet the general security requirements of the NGN [ITU-T Y.2701].
+
+Also, as the IP Centrex service provides media transport and signalling messages, the NGN network infrastructure for the IP Centrex service should ensure the confidentiality and integrity of the signalling messages transported on it. For this purpose, security mechanisms of different layers, such as transport layer security (TLS), IPSec and S/MIME, should be used when implementing the IP Centrex service.
+
+The TLS should be used for providing transport layer security over connection-oriented protocols (such as TCP). The TLS is specified in [IETF RFC 2246].
+
+IPSec should be used for providing security at network layer. IPSec is a set of network-layer protocol tools that collectively can be used as a secure replacement for traditional IP (Internet Protocol). IPSec is specified in [IETF RFC 2401].
+
+S/MIME should also be used to provide mechanisms for securing message bodies. S/MIME can provide end-to-end confidentiality and integrity for MIME contents, as well as mutual authentication. S/MIME is specified in [IETF RFC 2633].
+
+# Appendix I
+
+## IMS-based signalling flows for the IP Centrex service
+
+(This appendix does not form an integral part of this Recommendation.)
+
+## I.1 Internal communication
+
+
+
+```
+
+sequenceDiagram
+ participant UE1
+ participant P-CSC-FE(O)
+ participant S-CSC-FE(O)
+ participant IP_Centrex_AS as IP Centrex AS
+ participant S-I-CSC-FE(T)
+ participant P-CSC-FE(T)
+ participant UE2
+
+ Note right of UE2: Q.3612(11)_FI.1
+
+ UE1->>P-CSC-FE(O): 1) INVITE
+ P-CSC-FE(O)->>S-CSC-FE(O): 2) INVITE
+ S-CSC-FE(O)->>IP_Centrex_AS: 3) INVITE
+ IP_Centrex_AS->>S-CSC-FE(O): 4) INVITE
+ S-CSC-FE(O)->>IP_Centrex_AS: 5) INVITE
+ IP_Centrex_AS->>S-I-CSC-FE(T): 6) INVITE
+ S-I-CSC-FE(T)->>IP_Centrex_AS: 7) INVITE
+ IP_Centrex_AS->>S-I-CSC-FE(T): 8) INVITE
+ S-I-CSC-FE(T)->>P-CSC-FE(T): 9) INVITE
+ P-CSC-FE(T)->>UE2: 10) INVITE
+ UE2->>P-CSC-FE(T): 11) 180 ring
+ P-CSC-FE(T)->>S-I-CSC-FE(T): 12) 180 ring
+ S-I-CSC-FE(T)->>IP_Centrex_AS: 13) 180 ring
+ IP_Centrex_AS->>S-CSC-FE(O): 14) 180 ring
+ S-CSC-FE(O)->>IP_Centrex_AS: 15) 180 ring
+ IP_Centrex_AS->>S-CSC-FE(O): 16) 180 ring
+ S-CSC-FE(O)->>P-CSC-FE(O): 17) 180 ring
+ P-CSC-FE(O)->>UE1: 18) 180 ring
+ UE2->>P-CSC-FE(T): 19) 200 OK
+ P-CSC-FE(T)->>S-I-CSC-FE(T): 20) 200 OK
+ S-I-CSC-FE(T)->>IP_Centrex_AS: 21) 200 OK
+ IP_Centrex_AS->>S-I-CSC-FE(T): 22) 200 OK
+ S-I-CSC-FE(T)->>S-CSC-FE(O): 23) 200 OK
+ S-CSC-FE(O)->>IP_Centrex_AS: 24) 200 OK
+ IP_Centrex_AS->>S-CSC-FE(O): 25) 200 OK
+ S-CSC-FE(O)->>P-CSC-FE(O): 26) 200 OK
+ P-CSC-FE(O)->>UE1: 27) 200 OK
+ UE1->>P-CSC-FE(O): 28) ACK
+ P-CSC-FE(O)->>S-CSC-FE(O): 29) ACK
+ S-CSC-FE(O)->>IP_Centrex_AS: 30) ACK
+ IP_Centrex_AS->>S-CSC-FE(O): 31) ACK
+ S-CSC-FE(O)->>IP_Centrex_AS: 32) ACK
+ IP_Centrex_AS->>S-I-CSC-FE(T): 33) ACK
+ S-I-CSC-FE(T)->>IP_Centrex_AS: 34) ACK
+ IP_Centrex_AS->>S-I-CSC-FE(T): 35) ACK
+ S-I-CSC-FE(T)->>P-CSC-FE(T): 36) ACK
+ Note left of UE1: RTP connection
+
+```
+
+Sequence diagram showing internal communication call flow between UE1 and UE2 via various IMS components. The diagram includes 36 numbered messages for INVITE, 180 ring, 200 OK, and ACK. A large double-headed arrow at the bottom indicates the RTP connection path.
+
+Figure I.1 – Internal communication call flow
+
+- 1) UE1 sends an INVITE request to the originating P-CSC-FE. Based on the originating party's dial plan, the Request-URI may be the terminating party's private number or public user identity.
+- 2) The INVITE request is forwarded to the S-CSC-FE serving for the originating party.
+- 3) Based on the originating party's subscription, the INVITE request is forwarded to the IP Centrex AS.
+- 4) Based on the originating party's identities and the terminating party's identities, the IP Centrex AS confirms that it is an internal communication. If the terminating party identity is a private number in step 1), the IP Centrex AS shall transform it into a public user identity and include it in the Request-URI header field. The IP Centrex AS forwards the INVITE request to the originating S-CSC-FE.
+- 5) After invoking all the services subscribed to by the originating party, the originating S-CSC-FE will locate the terminating party and based on the normal procedure, the INVITE request will be sent to the terminating S-CSC-FE.
+- 6) The terminating S-CSC-FE analyses the terminating party's service subscription and sends the INVITE request to the IP Centrex AS.
+- 7) Based on the originating party's identities and terminating party's identities, the IP Centrex AS confirms that it is an internal communication. The originating party's identities will be transformed to the private number and included in the P-Asserted-Identity header field. The INVITE request is sent to the terminating S-CSC-FE.
+- 8) After invoking all the services subscribed to by the terminating party, the terminating S-CSC-FE sends the INVITE message to the terminating P-CSC-FE.
+- 9) The terminating P-CSC-FE sends the INVITE request to the UE2.
+- 10)-18) The terminating party is alerted and a 180 message is sent by the UE2. The 180 message is forwarded to the UE1.
+
+
+NOTE – If the SIP Precondition procedure is used, a message such as 183 PRACK UPDATE shall be shown.
+- 19)-27) The terminating party answers and a 200 (OK) response for the INVITE request is sent by the UE2. The 200 (OK) message is forwarded to the UE1.
+- 28)-36) The UE1 sends an ACK message after receiving the 200 (OK). The ACK message is forwarded to the UE2. The RTP connection is established between the UE1 and UE2.
+
+## I.2 Outgoing communication
+
+
+
+The diagram illustrates the call flow for an outgoing communication between UE1 and UE2. The sequence of messages is as follows:
+
+- 1) INVITE: UE1 to P-CSC-FE(O)
+- 2) INVITE: P-CSC-FE(O) to S-CSC-FE(O)
+- 3) INVITE: S-CSC-FE(O) to IP Centrex AS
+- 4) INVITE: IP Centrex AS to S-CSC-FE(O)
+- 5) INVITE: S-CSC-FE(O) to S/I-CSC-FE(T)
+- 6) INVITE: S/I-CSC-FE(T) to P-CSC-FE(T)
+- 7) INVITE: P-CSC-FE(T) to UE2
+- 8) 180 ring: UE2 to P-CSC-FE(T)
+- 9) 180 ring: P-CSC-FE(T) to S/I-CSC-FE(T)
+- 10) 180 ring: S/I-CSC-FE(T) to S-CSC-FE(O)
+- 11) 180 ring: S-CSC-FE(O) to IP Centrex AS
+- 12) 180 ring: IP Centrex AS to S-CSC-FE(O)
+- 13) 180 ring: S-CSC-FE(O) to P-CSC-FE(O)
+- 14) 180 ring: P-CSC-FE(O) to UE1
+- 15) 200 OK: UE2 to P-CSC-FE(T)
+- 16) 200 OK: P-CSC-FE(T) to S/I-CSC-FE(T)
+- 17) 200 OK: S/I-CSC-FE(T) to S-CSC-FE(O)
+- 18) 200 OK: S-CSC-FE(O) to IP Centrex AS
+- 19) 200 OK: IP Centrex AS to S-CSC-FE(O)
+- 20) 200 OK: S-CSC-FE(O) to P-CSC-FE(O)
+- 21) 200 OK: P-CSC-FE(O) to UE1
+- 22) ACK: UE1 to P-CSC-FE(O)
+- 23) ACK: P-CSC-FE(O) to S-CSC-FE(O)
+- 24) ACK: S-CSC-FE(O) to IP Centrex AS
+- 25) ACK: IP Centrex AS to S-CSC-FE(O)
+- 26) ACK: S-CSC-FE(O) to S/I-CSC-FE(T)
+- 27) ACK: S/I-CSC-FE(T) to P-CSC-FE(T)
+- 28) ACK: P-CSC-FE(T) to UE2
+
+A thick double-headed arrow at the bottom indicates the RTP connection between UE1 and UE2.
+
+Q.3612(11)\_FI.2
+
+Sequence diagram of outgoing communication call flow between UE1 and UE2 via various network elements.
+
+**Figure I.2 – Outgoing communication call flow**
+
+- 1) UE1 sends an INVITE request to the originating P-CSC-FE. The Request-URI is the information about the terminating party's public identity.
+- 2) The INVITE request is forwarded to the S-CSC-FE serving for the originating party.
+- 3) Based on the originating party's subscription, the INVITE request is forwarded to the IP Centrex AS.
+- 4) Based on the originating party's public identity and the terminating party's identity, the IP Centrex AS confirms that it is an outgoing communication. When the AS-FE sends the INVITE request to the originating S-CSC-FE, the public user identity of the terminating party shall be included in the Request-URI header field.
+- 5) After invoking all the service subscribed by the originating party, the Originating S-CSC-FE will locate the terminating party and based on the normal procedure, the INVITE request will be sent to the terminating S-CSC-FE.
+- 6) After invoking all the services subscribed to by the terminating party, the terminating S-CSC-FE sends the INVITE message to the terminating P-CSC-FE.
+- 7) The terminating P-CSC-FE sends the INVITE request to the UE2.
+
+8)-14) The terminating party is alerted and a 180 message is sent by the UE2. The 180 message is forwarded to the UE1.
+
+NOTE – If the SIP Precondition procedure is used, a message such as 183 PRACK UPDATE shall be shown.
+
+15)-21) The terminating party answers and a 200 (OK) response for the INVITE request is sent by the UE2. The 200 (OK) response is forwarded to the UE1.
+
+22)-28) The UE1 sends an ACK message after receiving the 200 (OK). The ACK message is forwarded to the UE2. The RTP connection is established between the UE1 and UE2.
+
+## I.3 Incoming communication
+
+
+
+```
+
+sequenceDiagram
+ participant UE1
+ participant PCSCF_O as P-CSC-FE(O)
+ participant SCSCF_O as S-CSC-FE(O)
+ participant IP_Centrex_AS as IP Centrex AS
+ participant SI_CSCF_T as S/I-CSC-FE(T)
+ participant PCSCF_T as P-CSC-FE(T)
+ participant UE2
+
+ UE1->>PCSCF_O: 1) INVITE
+ PCSCF_O->>SCSCF_O: 2) INVITE
+ SCSCF_O->>IP_Centrex_AS: 3) INVITE
+ IP_Centrex_AS->>SI_CSCF_T: 4) INVITE
+ SI_CSCF_T->>IP_Centrex_AS: 5) INVITE
+ IP_Centrex_AS->>SI_CSCF_T: 6) INVITE
+ SI_CSCF_T->>PCSCF_T: 7) INVITE
+ PCSCF_T->>UE2: 7) INVITE
+ UE2-->>PCSCF_T: 8) 180 ring
+ PCSCF_T-->>SI_CSCF_T: 9) 180 ring
+ SI_CSCF_T-->>IP_Centrex_AS: 10) 180 ring
+ IP_Centrex_AS-->>SI_CSCF_T: 11) 180 ring
+ SI_CSCF_T-->>SCSCF_O: 12) 180 ring
+ SCSCF_O-->>PCSCF_O: 13) 180 ring
+ PCSCF_O-->>UE1: 14) 180 ring
+ UE2-->>PCSCF_T: 15) 200 OK
+ PCSCF_T-->>SI_CSCF_T: 16) 200 OK
+ SI_CSCF_T-->>IP_Centrex_AS: 17) 200 OK
+ IP_Centrex_AS-->>SI_CSCF_T: 18) 200 OK
+ SI_CSCF_T-->>SCSCF_O: 19) 200 OK
+ SCSCF_O-->>PCSCF_O: 20) 200 OK
+ PCSCF_O-->>UE1: 21) 200 OK
+ UE1->>PCSCF_O: 22) ACK
+ PCSCF_O->>SCSCF_O: 23) ACK
+ SCSCF_O->>IP_Centrex_AS: 24) ACK
+ IP_Centrex_AS->>SI_CSCF_T: 25) ACK
+ SI_CSCF_T->>IP_Centrex_AS: 26) ACK
+ IP_Centrex_AS->>SI_CSCF_T: 27) ACK
+ SI_CSCF_T->>PCSCF_T: 28) ACK
+ PCSCF_T->>UE2: 28) ACK
+ Note over UE1, UE2: RTP connection
+
+```
+
+The diagram illustrates the incoming communication call flow. It shows the sequence of messages between UE1 (User Equipment 1) and UE2 (User Equipment 2) through various network elements: P-CSC-FE(O) (Proxy-CSCF for the originating party), S-CSC-FE(O) (Serving-CSCF for the originating party), IP Centrex AS (IP Centrex Application Server), S/I-CSC-FE(T) (Serving/Interrogating-CSCF for the terminating party), and P-CSC-FE(T) (Proxy-CSCF for the terminating party). The flow starts with an INVITE from UE1 to P-CSC-FE(O), which is then forwarded through S-CSC-FE(O), IP Centrex AS, S/I-CSC-FE(T), and P-CSC-FE(T) to UE2. UE2 responds with a 180 ring message, which is then forwarded back through the network elements to UE1. UE2 then sends a 200 OK response, which is also forwarded back through the network elements to UE1. Finally, UE1 sends an ACK message, which is forwarded through the network elements to UE2. A large double-headed arrow at the bottom indicates the RTP connection established between UE1 and UE2.
+
+Sequence diagram of incoming communication call flow between UE1 and UE2 via various network elements.
+
+Q.3612(11)\_FI.3
+
+**Figure I.3 – Incoming communication call flow**
+
+- 1) UE1 sends an INVITE request to the originating P-CSC-FE. The Request-URI is the information on the terminating party's public user identity.
+- 2) The INVITE request is forwarded to the S-CSC-FE serving for the originating party.
+- 3) After invoking all the services subscribed to by the originating party, the originating S-CSC-FE will locate the terminating party and, based on the normal procedure, the INVITE request will be sent to the terminating S-CSC-FE.
+- 4) The terminating S-CSC-FE analyzes the terminating party's service subscription and sends the INVITE request to the IP Centrex AS.
+
+- 5) Based on the originating party's public identity and the terminating party's public identity, the IP Centrex AS confirms that it is an incoming communication. When the AS-FE sends the INVITE request to the terminating I-CSCF, or the terminating S-CSCF, the originating party's identities contained in the P-Asserted-Identity header field can be used for call back directly by the terminating party.
+- 6) After invoking all the services subscribed to by the terminating party, the terminating S-CSCF sends the INVITE request to the terminating P-CSCF.
+- 7) The terminating P-CSCF sends the INVITE request to the UE2.
+- 8)-14) The terminating party is alerted and a 180 message is sent by the UE2. The 180 message is forwarded to the UE1.
+
+
+NOTE – If the SIP Precondition procedure is used, a message such as 183 PRACK UPDATE shall be shown.
+- 15)-21) The terminating party answers and a 200 (OK) response for the INVITE request is sent by the UE2. The 200 (OK) response is forwarded to the UE1.
+- 22)-28) The UE1 sends an ACK message after receiving the 200 (OK). The ACK message is forwarded to the UE2. The RTP connection is established between the UE1 and UE2.
+
+## **I.4 Originating identification presentation**
+
+The following diagram describes the call flow of the originating identification presentation service. It is assumed that UE1 and UE2 belong to the same Centrex group and that UE2 has activated the originating identification presentation service.
+
+
+
+```
+
+sequenceDiagram
+ participant UE1
+ participant PCSCFEO as P-CSC-FE(O)
+ participant SCSCFEO as S-CSC-FE(O)
+ participant IPCentrexAS as IP Centrex AS
+ participant SICSCFET as S/I-CSC-FE(T)
+ participant PCSCFET as P-CSC-FE(T)
+ participant UE2
+
+ UE1->>PCSCFEO: 1) INVITE
+ PCSCFEO->>SCSCFEO: 2) INVITE
+P-Asserted-Identity: UE1
+ SCSCFEO->>IPCentrexAS: 3) INVITE
+P-Asserted-Identity: UE1
+ IPCentrexAS->>SCSCFEO: 4) INVITE
+P-Asserted-Identity: UE1
+ SCSCFEO->>SICSCFET: 5) INVITE
+P-Asserted-Identity: UE1
+ SICSCFET->>IPCentrexAS: 6) INVITE
+P-Asserted-Identity: UE1
+ IPCentrexAS->>SICSCFET: 7) INVITE
+P-Asserted-Identity: UE1'
+ SICSCFET->>PCSCFET: 8) INVITE
+P-Asserted-Identity: UE1'
+ PCSCFET->>UE2: 9) INVITE
+P-Asserted-Identity: UE1'
+ UE2-->>PCSCFET: 10) 180 ring
+ PCSCFET-->>SICSCFET: 11) 180 ring
+ SICSCFET-->>IPCentrexAS: 12) 180 ring
+ IPCentrexAS-->>SICSCFET: 13) 180 ring
+ SICSCFET-->>SCSCFEO: 14) 180 ring
+ SCSCFEO-->>IPCentrexAS: 15) 180 ring
+ IPCentrexAS-->>SCSCFEO: 16) 180 ring
+ SCSCFEO-->>PCSCFEO: 17) 180 ring
+ PCSCFEO-->>UE1: 18) 180 ring
+ UE2-->>PCSCFET: 19) 200 OK
+ PCSCFET-->>SICSCFET: 20) 200 OK
+ SICSCFET-->>IPCentrexAS: 21) 200 OK
+ IPCentrexAS-->>SICSCFET: 22) 200 OK
+ SICSCFET-->>SCSCFEO: 23) 200 OK
+ SCSCFEO-->>IPCentrexAS: 24) 200 OK
+ IPCentrexAS-->>SCSCFEO: 25) 200 OK
+ SCSCFEO-->>PCSCFEO: 26) 200 OK
+ PCSCFEO-->>UE1: 27) 200 OK
+ UE1->>PCSCFEO: 28) ACK
+ PCSCFEO->>SCSCFEO: 29) ACK
+ SCSCFEO->>IPCentrexAS: 30) ACK
+ IPCentrexAS->>SCSCFEO: 31) ACK
+ SCSCFEO->>SICSCFET: 32) ACK
+ SICSCFET->>IPCentrexAS: 33) ACK
+ IPCentrexAS->>SICSCFET: 34) ACK
+ SICSCFET->>PCSCFET: 35) ACK
+ PCSCFET->>UE2: 36) ACK
+ Note over UE1, UE2: RTP connection
+
+```
+
+Sequence diagram of the originating identification presentation call flow. Lifelines: UE1, P-CSC-FE(O), S-CSC-FE(O), IP Centrex AS, S/I-CSC-FE(T), P-CSC-FE(T), UE2. The diagram shows the flow of INVITE, 180 ring, 200 OK, and ACK messages between these entities. A large double-headed arrow at the bottom indicates the RTP connection path from UE1 to UE2.
+
+Q.3612(11)\_FI.4
+
+**Figure I.4 – Originating identification presentation call flow**
+
+- 1) UE1 sends an INVITE request to the originating P-CSC-FE. The originating P-CSC-FE inserts a P-Asserted-Identity header field into the INVITE request before forwarding it to the S-CSC-FE. The P-Asserted-Identity shall be set to the public user identity of the originating party which has been registered in the network by the originating party.
+- 2) The INVITE request is forwarded to the S-CSC-FE serving for the originating party.
+- 3) Based on the originating party's subscription, the INVITE request is forwarded to the IP Centrex AS.
+
+- 4) The IP Centrex AS forwards the INVITE request to the originating S-CSC-FE.
+- 5) After invoking all the services subscribed to by the originating party, the originating S-CSC-FE will locate the terminating party and, based on the normal procedure, the INVITE request will be sent to the terminating S-CSC-FE.
+- 6) The terminating S-CSC-FE analyzes the terminating party's service subscription and sends the INVITE request to the IP Centrex AS.
+- 7) The IP Centrex AS confirms that the terminating party has activated the originating identification presentation service, before sending the received INVITE request to the terminating S-CSC-FE. IP Centrex AS can either add a Privacy header field into the INVITE request with the value set to "none", or just leave the INVITE request without the Privacy header field, and change the public user identity (UE1) of the originating party in the P-Asserted-Identity into a private number (UE1'). The INVITE request is then sent to the terminating S-CSC-FE.
+
+NOTE – The public user identity (UE1) can be changed to a private number (UE1') in step 4) or step 7), depending on the operators' policy.
+
+- 8) After invoking all the service subscribed to by the terminating party, the terminating S-CSC-FE sends the INVITE request to the terminating P-CSC-FE.
+ - 9) If the Privacy header field is contained in the INVITE request with the value unequal to "none", the P-CSC-FE shall delete the P-Asserted-Identity header field before forwarding the INVITE request to UE2. If there is no Privacy header field in the INVITE request, or the Privacy header field is set to "none", then P-Asserted-Identity has to be provided to UE2.
+ - 10)-18) The terminating party is alerted and a 180 message is sent by the UE2. The 180 message is forwarded to the UE1.
+- NOTE – If the SIP Precondition procedure is used, a message such as 183 PRACK UPDATE shall be shown.
+- 19)-27) The terminating party answers and a 200 (OK) response for the INVITE request is sent by the UE2. The 200 (OK) response is forwarded to the UE1.
+ - 28)-36) The UE1 sends an ACK message after receiving the 200 (OK). The ACK message is forwarded to the UE2. The RTP connection is established between the UE1 and UE2.
+
+## I.5 Originating identification restriction
+
+The following diagram describes the call flow of the originating identification restriction service. It is assumed that UE1 has subscribed to the IP Centrex service and has activated the originating identification restriction service.
+
+
+
+Q.3612(11)\_FI.5
+
+Sequence diagram showing the originating identification restriction call flow between UE1 and UE2 through various network elements: P-CSC-FE(O), S-CSC-FE(O), IP Centrex AS, S/I-CSC-FE(T), and P-CSC-FE(T). The diagram includes 28 numbered messages such as INVITE, 180 ring, 200 OK, and ACK. A large double-headed arrow at the bottom indicates the RTP connection path between UE1 and UE2.
+
+**Figure I.5 – Originating identification restriction call flow**
+
+- 1) UE1 sends an INVITE request to the originating P-CSC-FE. The originating P-CSC-FE inserts a P-Asserted-Identity header field into the INVITE request before forwarding it to the S-CSC-FE. The P-Asserted-Identity shall be set to the public user identity of the UE1 which has been registered in the network by the originating party.
+- 2) The INVITE request is forwarded to the S-CSC-FE serving for the originating party.
+- 3) Based on the originating party's subscription, the INVITE request is forwarded to the IP Centrex AS.
+- 4) In this case, since the originating party has activated the originating identification restriction service, the IP Centrex AS shall add the Privacy header field in the INVITE request and set the value to "id", then set the From header field to "Anonymous" and send the INVITE request to the originating S-CSC-FE.
+- 5) After invoking all the services subscribed to by the originating party, the originating S-CSC-FE will locate the terminating party and, based on the normal procedure, the INVITE request will be sent to the terminating S-CSC-FE.
+- 6) After invoking all the services subscribed to by the terminating party, the terminating S-CSC-FE sends the INVITE request to the terminating P-CSC-FE.
+
+- 7) The P-CSC-FE shall delete the P-Asserted-Identity header field before forwarding the INVITE request to UE2.
+- 8)-14) The terminating party is alerted and a 180 message is sent by the UE2. The 180 message is forwarded to the UE1.
+**NOTE** – If the SIP Precondition procedure is used, a message such as 183 PRACK UPDATE shall be shown.
+- 15)-21) The terminating party answers and a 200 (OK) response for the INVITE request is sent by the UE2. The 200 (OK) response is forwarded to the UE1.
+- 22)-28) The UE1 sends an ACK message after receiving the 200 (OK). The ACK message is forwarded to the UE2. The RTP connection is established between the UE1 and UE2.
+
+## **I.6 Terminating identification presentation**
+
+The following diagram describes one of the scenarios of the terminating identification presentation service. In this case, it is assumed that both the UE1 and UE2 are in the same IP Centrex group and that UE1 has activated the terminating identification presentation service.
+
+
+
+```
+
+sequenceDiagram
+ participant UE1
+ participant PCSCF_O as P-CSC-FE(O)
+ participant SCSCF_O as S-CSC-FE(O)
+ participant IP_AS as IP Centrex AS
+ participant SICSCF_T as S/I-CSC-FE(T)
+ participant PCSCF_T as P-CSC-FE(T)
+ participant UE2
+
+ Note over UE1, UE2: 1) ~ 18) The same as Figure I.1
+ UE2->>PCSCF_T: 19) 200 OK (INVITE)
+ PCSCF_T->>SICSCF_T: 20) 200 OK P-Asserted-Identity: UE1
+ SICSCF_T->>IP_AS: 21) 200 OK P-Asserted-Identity: UE2
+ IP_AS->>SICSCF_T: 22) 200 OK P-Asserted-Identity: UE2
+ SICSCF_T->>SCSCF_O: 23) 200 OK P-Asserted-Identity: UE2
+ SCSCF_O->>IP_AS: 24) 200 OK P-Asserted-Identity: UE2
+ IP_AS->>SCSCF_O: 25) 200 OK P-Asserted-Identity: UE2'
+ SCSCF_O->>PCSCF_O: 26) 200 OK P-Asserted-Identity: UE2'
+ PCSCF_O->>UE1: 27) 200 OK P-Asserted-Identity: UE2'
+ UE1->>PCSCF_O: 28) ACK
+ PCSCF_O->>SCSCF_O: 29) ACK
+ SCSCF_O->>IP_AS: 30) ACK
+ IP_AS->>SCSCF_O: 31) ACK
+ SCSCF_O->>SICSCF_T: 32) ACK
+ SICSCF_T->>IP_AS: 33) ACK
+ IP_AS->>SICSCF_T: 34) ACK
+ SICSCF_T->>PCSCF_T: 35) ACK
+ PCSCF_T->>UE2: 36) ACK
+ Note over UE1, UE2: RTP connection
+
+```
+
+The sequence diagram illustrates the call flow for terminating identification presentation. It begins with a shared phase (1) ~ 18) labeled 'The same as Figure I.1'. The main sequence starts at step 19) with a 200 OK (INVITE) message from UE2 to P-CSC-FE(T). Step 20) shows a 200 OK response with P-Asserted-Identity: UE1 from P-CSC-FE(T) to S/I-CSC-FE(T). Step 21) shows a 200 OK response with P-Asserted-Identity: UE2 from S/I-CSC-FE(T) to IP Centrex AS. Step 22) shows a 200 OK response with P-Asserted-Identity: UE2 from IP Centrex AS to S/I-CSC-FE(T). Step 23) shows a 200 OK response with P-Asserted-Identity: UE2 from S/I-CSC-FE(T) to S-CSC-FE(O). Step 24) shows a 200 OK response with P-Asserted-Identity: UE2 from S-CSC-FE(O) to IP Centrex AS. Step 25) shows a 200 OK response with P-Asserted-Identity: UE2' from IP Centrex AS to S-CSC-FE(O). Step 26) shows a 200 OK response with P-Asserted-Identity: UE2' from S-CSC-FE(O) to P-CSC-FE(O). Step 27) shows a 200 OK response with P-Asserted-Identity: UE2' from P-CSC-FE(O) to UE1. Step 28) shows an ACK message from UE1 to P-CSC-FE(O). Step 29) shows an ACK message from P-CSC-FE(O) to S-CSC-FE(O). Step 30) shows an ACK message from S-CSC-FE(O) to IP Centrex AS. Step 31) shows an ACK message from IP Centrex AS to S-CSC-FE(O). Step 32) shows an ACK message from S-CSC-FE(O) to S/I-CSC-FE(T). Step 33) shows an ACK message from S/I-CSC-FE(T) to IP Centrex AS. Step 34) shows an ACK message from IP Centrex AS to S/I-CSC-FE(T). Step 35) shows an ACK message from S/I-CSC-FE(T) to P-CSC-FE(T). Step 36) shows an ACK message from P-CSC-FE(T) to UE2. A large double-headed arrow at the bottom indicates the RTP connection between UE1 and UE2.
+
+Q.3612(11)\_FI.6
+
+Sequence diagram for Terminating identification presentation call flow showing SIP message exchange between UE1, P-CSC-FE(O), S-CSC-FE(O), IP Centrex AS, S/I-CSC-FE(T), P-CSC-FE(T), and UE2.
+
+**Figure I.6 – Terminating identification presentation call flow**
+
+- 1)~18) UE1 initiates a call to UE2, and UE2 is alerting. Up to this point, it is almost the same as the first 18 steps depicted in Figure I.1.
+- 19) The terminating party answers the call and a 200 (OK) response to the INVITE request is sent by the UE2 to the terminating P-CSC-FE.
+- 20) The terminating P-CSC-FE inserts a P-Asserted-Identity header field into the 200 (OK) response before forwarding the 200 (OK) response to the terminating S-CSC-FE. The P-Asserted-Identity shall be set to the public user identity of the terminating party.
+- 21) The terminating S-CSC-FE forwards the 200 (OK) response with P-Asserted-Identity to IP Centrex AS.
+- 22) IP Centrex AS forwards the 200 (OK) response to the terminating S-CSC-FE.
+- 23) The terminating S-CSC-FE forwards the 200 (OK) response with P-Asserted-Identity to the originating S-CSC-FE.
+- 24) The originating S-CSC-FE forwards the 200 (OK) response to IP Centrex AS.
+- 25) In this case, since the originating party has activated the terminating identification presentation service, before forwarding the received 200 (OK) response to the originating S-CSC-FE, IP Centrex AS can either add a Privacy header field into the 200 (OK) response to the INVITE request with the value setting to "none", or just leave the 200 (OK) response without a Privacy header field, and change the public user identity of the terminating party in the P-Asserted-Identity into a private number.
+- 26) The originating S-CSC-FE forwards the 200 (OK) response to the originating P-CSC-FE.
+- 27) In this case, since there is no Privacy header field within the 200 (OK) response or the value of the Privacy is "none", then P-Asserted-Identity has to be provided to UE1.
+- 28)-36) The UE1 sends an ACK message after receiving the 200 (OK). The ACK message is forwarded to the UE2. The RTP connection is established between the UE1 and UE2.
+
+## I.7 Terminating identification restriction
+
+The following diagram describes one of the scenarios of the terminating identification restriction service. In this case, it is assumed that both UE1 and UE2 are in the same IP Centrex group and that UE2 has activated the terminating identification restriction service.
+
+
+
+```
+
+sequenceDiagram
+ participant UE1
+ participant P-CSC-FE(O)
+ participant S-CSC-FE(O)
+ participant IP_Centrex_AS as IP Centrex AS
+ participant S-I-CSC-FE(T)
+ participant P-CSC-FE(T)
+ participant UE2
+
+ Note over all: 1) ~ 18) the same as Figure I.1
+
+ UE2->>P-CSC-FE(T): 19) 200 OK (INVITE)
+ P-CSC-FE(T)-->>S-I-CSC-FE(T): 20) 200 OK P-Asserted-Identity: UE1
+ S-I-CSC-FE(T)-->>IP_Centrex_AS: 21) 200 OK P-Asserted-Identity: UE2
+ IP_Centrex_AS-->>S-I-CSC-FE(T): 22) 200 OK P-Asserted-Identity: UE2 Privacy: id
+ S-I-CSC-FE(T)-->>S-CSC-FE(O): 23) 200 OK P-Asserted-Identity: UE2 Privacy: id
+ S-CSC-FE(O)-->>IP_Centrex_AS: 24) 200 OK P-Asserted-Identity: UE2 Privacy: id
+ IP_Centrex_AS-->>S-CSC-FE(O): 25) 200 OK P-Asserted-Identity: UE2 Privacy: id
+ S-CSC-FE(O)-->>P-CSC-FE(O): 26) 200 OK P-Asserted-Identity: UE2 Privacy: id
+ P-CSC-FE(O)-->>UE1: 27) 200 OK
+ UE1-->>P-CSC-FE(O): 28) ACK
+ P-CSC-FE(O)-->>S-CSC-FE(O): 29) ACK
+ S-CSC-FE(O)-->>IP_Centrex_AS: 30) ACK
+ IP_Centrex_AS-->>S-CSC-FE(O): 31) ACK
+ S-CSC-FE(O)-->>S-I-CSC-FE(T): 32) ACK
+ S-I-CSC-FE(T)-->>IP_Centrex_AS: 33) ACK
+ IP_Centrex_AS-->>S-I-CSC-FE(T): 34) ACK
+ S-I-CSC-FE(T)-->>P-CSC-FE(T): 35) ACK
+ P-CSC-FE(T)-->>UE2: 36) ACK
+
+ Note over UE1, UE2: RTP connection
+
+```
+
+Sequence diagram for Terminating identification restriction call flow. Lifelines: UE1, P-CSC-FE(O), S-CSC-FE(O), IP Centrex AS, S/I-CSC-FE(T), P-CSC-FE(T), UE2. The diagram shows the response and ACK messages starting from step 19, with an RTP connection established between UE1 and UE2.
+
+Q.3612(11)\_FI.7
+
+**Figure I.7 – Terminating identification restriction call flow**
+
+- 1)-18) UE1 initiates a call to UE2, and UE2 is alerting. Up to this point, it is almost the same as the first 18 steps depicted in the Figure I.1.
+- 19) The terminating party answers the call and a 200 (OK) response to the INVITE request is sent by the UE2 to the terminating P-CSC-FE.
+- 20) The terminating P-CSC-FE inserts a P-Asserted-Identity header field into the 200 (OK) response before forwarding the message to the terminating S-CSC-FE. The P-Asserted-Identity shall be set to the public user identity of the terminating party.
+- 21) The terminating S-CSC-FE forwards the 200 (OK) response with P-Asserted-Identity to IP Centrex AS.
+- 22) In this case, since the terminating party has activated the terminating identification restriction service, the IP Centrex AS shall add the Privacy header field into the 200 (OK) response to the INVITE request and set the value to "id", and send this response to the terminating S-CSC-FE.
+- 23) The terminating S-CSC-FE forwards the 200 (OK) response with P-Asserted-Identity and Privacy header fields to originating S-CSC-FE.
+
+- 24) The originating S-CSC-FE forwards the 200 (OK) response to IP Centrex AS.
+- 25) IP Centrex AS forwards the 200 (OK) response to the originating S-CSC-FE.
+NOTE – Since UE1 and UE2 are in the same IP Centrex group, IP Centrex AS may change the public user identity of the terminating party into a private number in the P-Asserted-Identity header field in the 200 (OK) response.
+- 26) The originating S-CSC-FE forwards the 200 OK received from the IP Centrex AS to the originating P-CSC-FE.
+- 27) The P-CSC-FE shall delete the P-Asserted-Identity header field before forwarding the 200 (OK) response to UE1.
+- 28)-36) The UE1 sends an ACK message after receiving the 200 (OK). The ACK message is forwarded to the UE2. The RTP connection is established between the UE1 and UE2.
+
+## I.8 Communication transfer
+
+The following diagram describes the call flow of the communication transfer service. It is assumed that UE2 is a Centrex user and that it has activated the communication transfer service.
+
+
+
+The sequence diagram illustrates the call flow for communication transfer. The participants are UE1/P-CSC-FE, S-CSC-FE(O), IP Centrex AS, S/I-CSC-FE(T), P-CSC-FE/UE2, and P-CSC-FE/UE3. The process begins with an RTP connection between UE1 and UE2. UE2 initiates the transfer (1) by sending a REFER message (2) to S/I-CSC-FE(T). S/I-CSC-FE(T) sends a REFER (3) to IP Centrex AS, which responds with 202 Accepted (4). S/I-CSC-FE(T) then sends 202 Accepted (5) to P-CSC-FE/UE2. IP Centrex AS sends an INVITE UE3 (6) to S/I-CSC-FE(T), which is forwarded (7) to P-CSC-FE/UE3. P-CSC-FE/UE3 sends a 180 ring (8) to S/I-CSC-FE(T), which is forwarded (9) to IP Centrex AS. S/I-CSC-FE(T) sends a 200 OK (SDP UE3) (10) to P-CSC-FE/UE3, which is forwarded (11) to IP Centrex AS. IP Centrex AS sends a Notify (12) to S/I-CSC-FE(T), which is forwarded (13) to P-CSC-FE/UE2. S/I-CSC-FE(T) sends a Bye (14) to P-CSC-FE/UE2, which is forwarded (15) to IP Centrex AS. IP Centrex AS sends a 200 OK (16) to S/I-CSC-FE(T), which is forwarded (17) to P-CSC-FE/UE2. IP Centrex AS sends a re-INVITE (SDP UE3) (18) to S-CSC-FE(O), which is forwarded (19) to UE1/P-CSC-FE. UE1/P-CSC-FE sends a 200 OK (SDP UE1) (20) to S-CSC-FE(O), which is forwarded (21) to IP Centrex AS. IP Centrex AS sends an ACK (SDP UE1) (22) to S-CSC-FE(O), which is forwarded (23) to P-CSC-FE/UE3. S-CSC-FE(O) sends an ACK (24) to UE1/P-CSC-FE, which is forwarded (25) to S-CSC-FE(O). Finally, a new RTP connection is established between UE1 and UE3.
+
+Sequence diagram showing the communication transfer call flow between UE1, S-CSC-FE(O), IP Centrex AS, S/I-CSC-FE(T), P-CSC-FE/UE2, and P-CSC-FE/UE3. The diagram illustrates the transfer of a call from UE2 to UE3 while maintaining an RTP connection with UE1.
+
+Q.3612(11)\_FI.8
+
+Figure I.8 – Communication transfer call flow
+
+- 1) The RTP connection is established between the UE1 and UE2. The UE2 transfers the call to UE3 which can be a Centrex user or a public user.
+- 2), 3) The UE2 sends a REFER request to IP Centrex AS.
+- 4)-7) The AS confirms that UE2 wants to transfer the call to UE3. The AS sends a 202 (Accepted) response to UE2 and creates an INVITE request based on the REFER message. In the INVITE request, The Request-URI shall be set to the public user identity of UE3. The INVITE request is forwarded to UE3.
+- 8), 9) The terminating party is alerted and a 180 message is sent by the UE3. The 180 message is forwarded to the AS.
+- 10), 11) The terminating party answers and a 200 (OK) response for the INVITE request is sent by the UE3. The 200 (OK) response is forwarded to the AS.
+- 12), 13) The AS sends a NOTIFY message to UE2 to indicate the successful transfer of the call to UE3.
+- 14)-17) UE2 sends a BYE message to the AS-FE to release the connection between UE1 and UE2.
+- 18), 19) The AS sends a re-INVITE message to UE1 to indicate the capability of UE3.
+- 20), 21) UE1 sends a 200 (OK) response for the reINVITE request with the SDP information of UE1.
+- 22)-25) The AS sends an ACK message after receiving the 200 (OK). The RTP connection is established between the UE1 and UE3.
+
+## **I.9 Communication diversion**
+
+The following diagram describes the call flow of the communication diversion service. It is assumed that UE2 is a Centrex user and that it has activated the communication forwarding service on the condition of no reply. UE1 and UE3 are public users.
+
+
+
+```
+
+sequenceDiagram
+ participant UE1/P-CSC-FE
+ participant S-CSC-FE(O)
+ participant IP_Centrex_AS as IP Centrex AS
+ participant S_I-CSC-FE_T as S/I-CSC-FE(T)
+ participant P-CSC-FE-UE2 as P-CSC-FE/UE2
+ participant P-CSC-FE-UE3 as P-CSC-FE/UE3
+
+ Note right of S-CSC-FE(O): No final response from UE2
+
+ UE1/P-CSC-FE->>S-CSC-FE(O): 1) INVITE UE2
+ S-CSC-FE(O)->>IP_Centrex_AS: 2) INVITE UE2
+ IP_Centrex_AS->>S_I-CSC-FE_T: 3) INVITE UE2
+ S_I-CSC-FE_T->>IP_Centrex_AS: 4) INVITE UE2
+ IP_Centrex_AS->>S_I-CSC-FE_T: 5) INVITE UE2
+ S_I-CSC-FE_T->>P-CSC-FE-UE2: 6) 180 ring
+ P-CSC-FE-UE2->>S_I-CSC-FE_T: 7) 180 ring
+ S_I-CSC-FE_T->>IP_Centrex_AS: 8) 180 ring
+ IP_Centrex_AS->>S_I-CSC-FE_T: 9) 180 ring
+ S_I-CSC-FE_T->>S-CSC-FE(O): 10) 180 ring
+ S-CSC-FE(O)->>UE1/P-CSC-FE: 11) 181 Call being forwarded
+ UE1/P-CSC-FE->>S-CSC-FE(O): 12) 181 Call being forwarded
+ IP_Centrex_AS->>S_I-CSC-FE_T: 13) CANCEL
+ S_I-CSC-FE_T->>P-CSC-FE-UE2: 14) CANCEL
+ P-CSC-FE-UE2->>S_I-CSC-FE_T: 15) 487
+ S_I-CSC-FE_T->>IP_Centrex_AS: 16) 487
+ IP_Centrex_AS->>S_I-CSC-FE_T: 17) ACK
+ S_I-CSC-FE_T->>P-CSC-FE-UE2: 18) ACK
+ P-CSC-FE-UE2->>S_I-CSC-FE_T: 19) 200 OK (CANCEL)
+ S_I-CSC-FE_T->>IP_Centrex_AS: 20) 200 OK (CANCEL)
+ IP_Centrex_AS->>S_I-CSC-FE_T: 21) INVITE UE3
+ S_I-CSC-FE_T->>P-CSC-FE-UE3: 22) INVITE UE3
+ P-CSC-FE-UE3->>S_I-CSC-FE_T: 23) 180 ring
+ S_I-CSC-FE_T->>IP_Centrex_AS: 24) 180 ring
+ IP_Centrex_AS->>S-CSC-FE(O): 25) 180 ring
+ S-CSC-FE(O)->>UE1/P-CSC-FE: 26) 180 ring
+ P-CSC-FE-UE3->>S_I-CSC-FE_T: 27) 200 OK
+ S_I-CSC-FE_T->>IP_Centrex_AS: 28) 200 OK
+ IP_Centrex_AS->>S-CSC-FE(O): 29) 200 OK
+ S-CSC-FE(O)->>UE1/P-CSC-FE: 30) 200 OK
+ UE1/P-CSC-FE->>S-CSC-FE(O): 31) ACK
+ S-CSC-FE(O)->>IP_Centrex_AS: 32) ACK
+ IP_Centrex_AS->>S_I-CSC-FE_T: 33) ACK
+ S_I-CSC-FE_T->>P-CSC-FE-UE3: 34) ACK
+ Note left of P-CSC-FE-UE3: RTP connection between UE1 and UE3
+
+```
+
+Sequence diagram showing communication diversion call flow between UE1, S-CSC-FE(O), IP Centrex AS, S/I-CSC-FE(T), P-CSC-FE/UE2, and P-CSC-FE/UE3. The diagram illustrates the SIP signaling for call forwarding from UE2 to UE3.
+
+Q.3612(11)\_FI.9
+
+**Figure I.9 – Communication diversion call flow**
+
+- 1)-10) The UE1 initiates a call to UE2, and UE2 is alerting.
+- 11)-20) The IP Centrex AS does not receive any final response from UE2, and then triggers call-forwarding on the no-reply service. IP Centrex AS informs UE1 that the call is being forwarded, and cancels the INVITE request sent to UE2.
+- 21), 22) Based on UE2's subscription, the call shall be forwarded to UE3. The IP Centrex AS sends an INVITE request to UE3. In the INVITE request, the Request-URI shall be set to the public user identity of UE3 and the History header field shall be set to the public user identity of UE2.
+- 23)-26) the UE3 is alerted and a 180 message is sent by the UE3. The 180 message is forwarded to the UE1.
+NOTE – If the SIP Precondition procedure is used, a message such as 183 PRACK UPDATE shall be shown.
+- 27)-30) The UE3 answers and a 200 (OK) response for the INVITE request is sent by the UE3. The 200 (OK) response is forwarded to the UE1.
+- 31)-34) The UE1 sends an ACK message after receiving the 200 (OK). The ACK message is forwarded to the UE2. The RTP connection is established between the UE1 and UE3.
+
+## I.10 Communication pickup
+
+
+
+```
+
+sequenceDiagram
+ participant UE1 as UE1/P-CSC-FE
+ participant SCSCF_O as S-CSC-FE(O)
+ participant AS as IP Centrex AS
+ participant SCSCF_T as S/I-CSC-FE(T)
+ participant UE2 as P-CSC-FE/UE2
+ participant UE3 as P-CSC-FE/UE3
+
+ UE1->>SCSCF_O: 1) INVITE(SDP UE1)
+ SCSCF_O->>AS: 2) INVITE(SDP UE1)
+ AS->>SCSCF_O: 3) INVITE(SDP UE1)
+ SCSCF_O->>SCSCF_T: 4) INVITE(SDP UE1)
+ SCSCF_T->>AS: 5) INVITE(SDP UE1)
+ AS->>SCSCF_T: 6) INVITE(SDP UE1)
+ SCSCF_T->>UE2: 7) INVITE(SDP UE1)
+ UE2->>SCSCF_T: 8) 180 ring(SDP UE2)
+ SCSCF_T->>AS: 9) 180 ring(SDP UE2)
+ AS->>SCSCF_T: 10) 180 ring(SDP UE2)
+ SCSCF_T->>SCSCF_O: 11) 180 ring(SDP UE2)
+ SCSCF_O->>AS: 12) 180 ring(SDP UE2)
+ AS->>SCSCF_O: 13) 180 ring(SDP UE2)
+ SCSCF_O->>UE1: 14) 180 ring(SDP UE2)
+ UE3->>SCSCF_T: 15) INVITE(SDP UE1)
+ SCSCF_T->>AS: 16) INVITE(SDP UE1)
+ AS->>SCSCF_T: 17) CANCEL
+ SCSCF_T->>UE2: 18) CANCEL
+ UE2->>SCSCF_T: 19) 200 OK(CANCEL)
+ SCSCF_T->>AS: 20) 200 OK(CANCEL)
+ AS->>SCSCF_T: 21) 487
+ SCSCF_T->>UE2: 22) 487
+ UE2->>SCSCF_T: 23) ACK
+ SCSCF_T->>AS: 24) ACK
+ AS->>SCSCF_T: 25) 200 OK(CANCEL)
+ SCSCF_T->>SCSCF_O: 26) 200 OK (INVITE)
+ SCSCF_O->>AS: 27) 200 OK(INVITE)
+ AS->>SCSCF_O: 28) 200 OK(INVITE)
+ SCSCF_O->>UE1: 29) 200 OK(INVITE)
+ UE1->>SCSCF_O: 30) ACK
+ SCSCF_O->>AS: 31) ACK
+ AS->>SCSCF_O: 32) ACK
+ SCSCF_O->>SCSCF_T: 33) ACK
+ SCSCF_T->>AS: 34) ACK
+ AS->>SCSCF_T: 35) re-INVITE (SDP UE3)
+ SCSCF_T->>SCSCF_O: 36) re-INVITE (SDP UE3)
+ SCSCF_O->>AS: 37) re-INVITE (SDP UE3)
+ AS->>SCSCF_O: 38) re-INVITE (SDP UE3)
+ SCSCF_O->>UE1: 39) re-INVITE (SDP UE3)
+ UE1->>SCSCF_O: 40) 200 OK(SDP UE1')
+ SCSCF_O->>AS: 41) 200 OK(SDP UE1')
+ AS->>SCSCF_O: 42) 200 OK(SDP UE1')
+ SCSCF_O->>SCSCF_T: 43) 200 OK(SDP UE1')
+ SCSCF_T->>AS: 44) 200 OK(SDP UE1')
+ AS->>SCSCF_T: 45) ACK
+ SCSCF_T->>SCSCF_O: 46) ACK
+ SCSCF_O->>AS: 47) ACK
+ AS->>SCSCF_O: 48) ACK
+ SCSCF_O->>UE1: 49) ACK
+ SCSCF_O->>SCSCF_T: 50) 200 OK(SDP UE1')
+ SCSCF_T->>UE3: 51) 200 OK(SDP UE1')
+ UE3->>SCSCF_T: 52) ACK
+ SCSCF_T->>AS: 53) ACK
+ Note over UE1, UE3: RTP connection between UE1 and UE3
+
+```
+
+Sequence diagram for Communication pickup call flow between UE1, S-CSCF, IP Centrex AS, S/I-CSCF, and UE2/UE3.
+
+Q.3612(11)\_FI.10
+
+**Figure I.10 – Communication pickup call flow**
+
+- 1)-14) UE1 initiates a call to UE2, and UE2 is alerting. Up to this point, it is almost the same as the first 18 steps depicted in Figure I.1.
+- 15) UE3 picks up the alerting call by using a specific pickup access code. UE3 sends an INVITE request with the pickup access code to S-CSC-FE of UE2. The SDP UE3 is provided in the INVITE request.
+- 16) Based on UE3's subscription, the INVITE request is forwarded to IP Centrex AS.
+- 17)-24) The AS confirms that UE3 is picking up the call to UE2 by analysing the phone number followed by the access code for the explicitly identified pickup scenario, or based on the fact that UE2 and UE3 are in the same pickup group for the group pickup scenario. The AS then decides to cancel the INVITE request sent to UE2.
+NOTE – The AS is now in back-to-back user agent (B2BUA) mode.
+- 25)-29) The AS sends a 200 (OK) response upstream to the UE1 so that it can establish the confirmed dialogue with UE1.
+- 30)-34) UE1 sends an ACK to AS. Now, AS has established a call leg (SIP dialogue) for UE1.
+- 35)-39) AS uses the SDP UE3 received in the INVITE request from UE3 to generate an INVITE (re-INVITE) to UE1.
+- 40)-44) UE1 responds with an SDP Answer to AS. The SDP Answer in 200 (OK) response may be different from the one sent in Step 1), and it is therefore denoted as SDP UE1'.
+- 45)-49) AS sends an ACK towards UE1.
+- 50), 51) AS sends a 200 (OK) response, including the newly received SDP UE1' from UE1, towards UE3.
+- 52), 53) UE3 sends an ACK towards AS. Now, AS has established two call-legs, one for UE1, the other for UE3, and the RTP connection is established between UE1 and UE3.
+
+## I.11 Communication hold
+
+The following diagram describes the call flow of the communication hold service. It is assumed that UE1 is a Centrex user and that it has activated the communication hold service.
+
+
+
+```
+
+sequenceDiagram
+ participant UE1 as UE1/P-CSC-FE
+ participant S_O as S-CSC-FE(O)
+ participant AS as IP Centrex AS
+ participant S_T as S/I-CSC-FE(T)
+ participant UE2 as P-CSC-FE/UE2
+
+ Note over UE1, UE2: RTP connection between UE1 and UE2
+ Note left of UE1: 1) UE1 place the call on hold
+ UE1->>S_O: 2) Invite (sendonly)
+ S_O->>AS: 3) Invite (sendonly)
+ AS->>S_T: 4) Invite (sendonly)
+ S_T->>UE2: 5) Invite (sendonly)
+ UE2-->>S_T: 6) 200 OK (recvonly)
+ S_T-->>AS: 7) 200 OK (recvonly)
+ AS-->>S_O: 8) 200 OK (recvonly)
+ S_O-->>UE1: 9) 200 OK (recvonly)
+ UE1->>S_O: 10) ACK
+ S_O->>AS: 11) ACK
+ AS->>S_T: 12) ACK
+ S_T->>UE2: 13) ACK
+
+ Note over UE1, UE2:
+
+ Note left of UE1: Resume the call
+ UE1->>S_O: 14) Invite (sendrecv)
+ S_O->>AS: 15) Invite (sendrecv)
+ AS->>S_T: 16) Invite (sendrecv)
+ S_T->>UE2: 17) Invite (sendrecv)
+ UE2-->>S_T: 18) 200 OK (sendrecv)
+ S_T-->>AS: 19) 200 OK (sendrecv)
+ AS-->>S_O: 20) 200 OK (sendrecv)
+ S_O-->>UE1: 21) 200 OK (sendrecv)
+ UE1->>S_O: 22) ACK
+ S_O->>AS: 23) ACK
+ AS->>S_T: 24) ACK
+ S_T->>UE2: 25) ACK
+ Note over UE1, UE2: RTP connection between UE1 and UE2
+
+```
+
+Q.3612(11)\_FI.11
+
+Sequence diagram showing the communication hold call flow between UE1/P-CSC-FE, S-CSC-FE(O), IP Centrex AS, S/I-CSC-FE(T), and P-CSC-FE/UE2. The diagram illustrates the process of placing a call on hold and then resuming it, involving re-INVITE and 200 OK messages with specific SDP lines.
+
+**Figure I.11 – Communication hold call flow**
+
+- 1) The RTP connection is established between the UE1 and UE2. UE1 places the call on hold.
+- 2)-5) The UE1 sends a re-INVITE request containing a SDP with "a=" line set to "sendonly". The re-INVITE request is forwarded to UE2.
+NOTE – The AS can play the service announcement to UE2 in step 5), which depends on operators' policy.
+- 6)-9) The UE2 sends a 200 (OK) response containing a SDP with "a=" line set to "recvonly". The 200 (OK) response is forwarded to UE1.
+- 10)-13) The UE1 sends an ACK message after receiving the 200(OK).
+- 14)-17) The UE1 wants to resume the call. The UE1 sends a re-INVITE request containing a SDP with "a=" line set to "sendrecv". The re-INVITE request is forwarded to UE2.
+- 18)-25) The UE2 sends a 200 (OK) response containing a SDP with "a=" line set to "sendrecv". The 200 (OK) response is forwarded to UE1. The ACK message is forwarded to the UE2. The RTP connection between the UE1 and UE2 is resumed.
+
+# Appendix II
+
+## Call server based signalling flows for the IP Centrex service
+
+(This appendix does not form an integral part of this Recommendation.)
+
+For call server based IP Centrex, the access protocol between UE and the call server can be ISDN, ISUP, or ITU-T H.248, etc. The access protocol in the signalling flow given in Figure II.1 just illustrates the message sequence. In the actual implementation, it could be any of the protocols mentioned above. Figure II.1 gives an example of internal communication in the call server based context, i.e., UE1 and UE2 are in the same IP Centrex group.
+
+UEs in Figure II.1 refer to legacy terminals.
+
+
+
+```
+sequenceDiagram
+ participant UE1
+ participant CS_O as Call server (O)
+ participant IP_Centrex_AS as IP Centrex AS
+ participant CS_T as Call server (T)
+ participant UE2
+
+ Note left of UE1: 1) make a call
+ UE1->>CS_O:
+ CS_O->>IP_Centrex_AS: 2) INVITE
+ IP_Centrex_AS->>CS_O: 3) INVITE
+ CS_O->>CS_T: 4) INVITE
+ CS_T->>IP_Centrex_AS: 5) INVITE
+ IP_Centrex_AS->>CS_T: 6) INVITE
+ Note right of CS_T: 7) make a call
+ CS_T->>UE2:
+ UE2->>CS_T: 8) ringing
+ CS_T->>IP_Centrex_AS: 9) 180 ring
+ IP_Centrex_AS->>CS_T: 10) 180 ring
+ CS_T->>CS_O: 11) 180 ring
+ CS_O->>IP_Centrex_AS: 12) 180 ring
+ IP_Centrex_AS->>CS_O: 13) 180 ring
+ Note left of UE1: 14) ringing
+ CS_O->>UE1:
+ Note right of UE2: 15) answer a call
+ UE2->>CS_T:
+ CS_T->>IP_Centrex_AS: 16) 200 OK
+ IP_Centrex_AS->>CS_T: 17) 200 OK
+ CS_T->>CS_O: 18) 200 OK
+ CS_O->>IP_Centrex_AS: 19) 200 OK
+ IP_Centrex_AS->>CS_O: 20) 200 OK
+ Note left of UE1: 21) answer a call
+ CS_O->>UE1:
+ CS_O->>IP_Centrex_AS: 22) ACK
+ IP_Centrex_AS->>CS_O: 23) ACK
+ CS_O->>CS_T: 24) ACK
+ CS_T->>IP_Centrex_AS: 25) ACK
+ IP_Centrex_AS->>CS_T: 26) ACK
+```
+
+Q.3612(11)\_FII.1
+
+Sequence diagram showing internal communication call flow between UE1, Call server (O), IP Centrex AS, Call server (T), and UE2. The diagram illustrates the message sequence for a call, including INVITE, 180 ring, 200 OK, and ACK messages, with a large double-headed arrow at the bottom indicating RTP flow.
+
+Figure II.1 – Internal communication call flow
+
+- 1) UE1 initiates a call to UE2. The originating party can either dial the private number or the public user identity of the terminating party. The corresponding number information shall be sent to the call server.
+- 2) The originating call server sends an INVITE request to IP Centrex AS with the dialled digits in the request-URI, according to the originating party's subscription.
+- 3) Based on the originating party's identities and the terminating party's identities, the IP Centrex AS confirms that it is an internal communication. If the digits in the request-URI represent the private number in step 1), the IP Centrex AS shall transform it into a public user identity. The IP Centrex AS forwards the INVITE request to the originating call server.
+- 4) The originating call server will route the call to the terminating call server and forward the INVITE request to the terminating call server.
+- 5) The terminating call server analyzes the terminating party's service subscription and forwards the INVITE request to the IP Centrex AS.
+- 6) IP Centrex AS confirms that it is an internal communication. The originating party's identities in the P-Asserted-Identity header field in the INVITE request need to be transformed into the private number of the originating party. The INVITE request is sent to the terminating call server.
+- 7) The terminating call server then routes the call to the UE2.
+- 8) If the UE2 is free, it will ring at this time.
+- 9)-14) A 180 response is forwarded along to the originating call server. Then the alerting information of the terminating party is provided to UE1.
+NOTE – If the SIP Precondition procedure is used, a message such as 183 PRACK UPDATE shall be shown.
+- 15)-21) The terminating party answers the call and related information is transmitted to UE1 by appropriate messages, e.g., 200 (OK), to the INVITE request.
+- 22)-26) To complete the INVITE transaction, an ACK request is needed in order to comply with the basic SIP protocol. After that, RTP connection between UE1 and UE2 is established.
+
+# Bibliography
+
+[b-ITU-T H.450.5] Recommendation ITU-T H.450.5 (1999), *Call park and call pickup supplementary services for H.323*.
+
+
+
+
+
+# SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|---------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3622-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3622-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ffdffaa305a676704a0882bdb37fa339cfb15c63
--- /dev/null
+++ b/marked/Q/T-REC-Q.3622-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aabf7e54909f44fdbc817ea80c7f1889ab563371aebbe198922f7dee431c115f
+size 4133
diff --git a/marked/Q/T-REC-Q.3622-201602-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3622-201602-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..3d8aef8770b6ceffbd51738c79daee008030d9e9
--- /dev/null
+++ b/marked/Q/T-REC-Q.3622-201602-I_PDF-E/raw.md
@@ -0,0 +1,180 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.3622**
+
+(02/2016)
+
+# **SERIES Q: SWITCHING AND SIGNALLING**
+
+Signalling requirements and protocols for the NGN –
+Service and session control protocols – supplementary
+services based on SIP-IMS
+
+## --- **Communication waiting using IP multimedia core network subsystem – Protocol specification**
+
+Recommendation ITU-T Q.3622
+
+## 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 |
+| General | Q.3000–Q.3029 |
+| Network signalling and control functional architecture | Q.3030–Q.3099 |
+| Network data organization within the NGN | Q.3100–Q.3129 |
+| Bearer control signalling | Q.3130–Q.3179 |
+| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 |
+| Resource control protocols | Q.3300–Q.3369 |
+| Service and session control protocols | Q.3400–Q.3499 |
+| Service and session control protocols – supplementary services | Q.3600–Q.3616 |
+| Service and session control protocols – supplementary services based on SIP-IMS | Q.3617–Q.3639 |
+| NGN applications | Q.3700–Q.3849 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+### Recommendation ITU-T Q.3622
+
+## Communication waiting using IP multimedia core network subsystem – Protocol specification
+
+## Summary
+
+Recommendation ITU-T Q.3622 v.1 (2016) specifies requirements for supplementary service such as a communication waiting (CW) to be provided on the IMS platform.
+
+The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.3622, and that it relates to Release 10 of the relevant 3GPP/ETSI standard.
+
+This Recommendation endorses ETSI TS 124 615 V10.6.0 (2015-07), "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification (3GPP TS 24.615 version 10.6.0 Release 10)".
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|------------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.3622 v.1 | 2016-02-13 | 11 | 11.1002/1000/12720 |
+
+## Keywords
+
+CW, IMS, network side, SDP, SIP, testing, user side.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+### NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+### Recommendation ITU-T Q.3622
+
+## Communication waiting using IP multimedia core network subsystem — Protocol specification
+
+## 1 Scope
+
+This Recommendation specifies the requirements to protocols implementation for providing supplementary service such as a communication waiting (CW) on the IMS basis.
+
+The Recommendation endorses ETSI TS 124 615 V10.6.0 (2015-07), "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification (3GPP TS 24.615 version 10.6.0 Release 10)".
+
+## 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.
+
+[ETSI TS 124 615 V10.6.0] ETSI TS 124 615 V10.6.0 (2015-07), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification (3GPP TS 24.615 version 10.6.0 Release 10)*.
+
+## 3 Definitions
+
+None.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|-----|-------------------------|
+| CW | Communication Waiting |
+| IMS | IP Multimedia Subsystem |
+| IP | Internet Protocol |
+
+## 5 Conventions
+
+None.
+
+## 6 Endorsement
+
+[ETSI TS 124 615 V10.6.0]
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3629-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3629-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426
--- /dev/null
+++ b/marked/Q/T-REC-Q.3629-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:476aa07e8e41a13b741a431c04ad0f9bd3a7bd0a3822f14a669b12f2abaf0e0d
+size 3828
diff --git a/marked/Q/T-REC-Q.3629-201608-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3629-201608-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..8fb450987a240fb3240f3c1d4a6c08feec5999ec
--- /dev/null
+++ b/marked/Q/T-REC-Q.3629-201608-I_PDF-E/raw.md
@@ -0,0 +1,182 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.3629**
+
+(08/2016)
+
+# **SERIES Q: SWITCHING AND SIGNALLING**
+
+Signalling requirements and protocols for the NGN –
+Service and session control protocols – supplementary
+services based on SIP-IMS
+
+## --- **Interworking between the IP multimedia core network subsystem and circuit switched networks – Protocol specification**
+
+Recommendation ITU-T Q.3629
+
+## ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|---------------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 |
+| General | Q.3000–Q.3029 |
+| Network signalling and control functional architecture | Q.3030–Q.3099 |
+| Network data organization within the NGN | Q.3100–Q.3129 |
+| Bearer control signalling | Q.3130–Q.3179 |
+| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 |
+| Resource control protocols | Q.3300–Q.3369 |
+| Service and session control protocols | Q.3400–Q.3499 |
+| Service and session control protocols – supplementary services | Q.3600–Q.3616 |
+| Service and session control protocols – supplementary services based on SIP-IMS | Q.3617–Q.3639 |
+| NGN applications | Q.3700–Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+### Recommendation ITU-T Q.3629
+
+# Interworking between the IP multimedia core network subsystem and circuit switched networks – Protocol specification
+
+## Summary
+
+Recommendation ITU-T Q.3629 v.1 (2016) specifies the interworking requirements between the IP multimedia (IM) core network (CN) subsystem and circuit switched (CS) networks.
+
+The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.3629, and that it relates to Release 10 of the relevant 3GPP/ETSI standard.
+
+This Recommendation endorses ETSI TS 129 163 V10.19.0 (2016-01) "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Interworking between the IP Multimedia (IM), Core Network (CN), subsystem and Circuit Switched (CS) networks; (ETSI TS 129 163 V10.19.0 Release 10)".
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|------------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.3629 v.1 | 2016-08-29 | 11 | 11.1002/1000/12988 |
+
+## Keywords
+
+Interworking, IP multimedia subsystem, IMS, session initiation protocol, SIP.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Recommendation ITU-T Q.3629
+
+# Interworking between the IP multimedia core network subsystem and circuit switched networks – Protocol specification
+
+## 1 Scope
+
+This Recommendation specifies the requirements for providing the interworking between the IP multimedia (IM) core network (CN) subsystem and circuit switched (CS) networks.
+
+The Recommendation endorses [ETSI TS 129 163 V10.19.0](#) (2016-01) Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks (3GPP TS 29.163 version 10.19.0 Release 10).
+
+## 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.
+
+[[ETSI TS 129 163 V10.19.0](#)] ETSI TS 129 163 V10.19.0 (2016), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks (3GPP TS 29.163 version 10.19.0 Release 10)*.
+
+## 3 Definitions
+
+None.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|-----|------------------------------|
+| IMS | IP Multimedia Subsystem |
+| IP | Internet Protocol |
+| SDP | Session Description Protocol |
+| SIP | Session Initiation Protocol |
+
+## 5 Conventions
+
+None.
+
+## 6 Endorsement
+
+[[ETSI TS 129 163 V10.19.0](#)]
+
+
+
+
+
+## **SERIES OF ITU-T RECOMMENDATIONS**
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3910-201006-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/Q/T-REC-Q.3910-201006-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a8073c3055abc7731de1ae66c36e362f11443a0c
--- /dev/null
+++ b/marked/Q/T-REC-Q.3910-201006-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4b4de5adc1d3cdb5e156cd79f5bd52f6701f25e443a1f8d3f0d1dce155ed63f9
+size 7472
diff --git a/marked/Q/T-REC-Q.3910-201006-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Q/T-REC-Q.3910-201006-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ddad928809ef238f3eca28e05480d0f26787a3e2
--- /dev/null
+++ b/marked/Q/T-REC-Q.3910-201006-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:20d67e99353360c04852e69756ab385d55e8ce60144d21172256836ff2f6ea8f
+size 94382
diff --git a/marked/Q/T-REC-Q.3920-201608-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/Q/T-REC-Q.3920-201608-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..79de3bd74a454358db16912308021cded44a327a
--- /dev/null
+++ b/marked/Q/T-REC-Q.3920-201608-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d18879b3f8f06edf1da4afe1e455b13b861dafba77e198bf988f550203964bd7
+size 7157
diff --git a/marked/Q/T-REC-Q.3932.4-201605-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3932.4-201605-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c96ef90bf7e2ed0fffefee0006cac32f005fd736
--- /dev/null
+++ b/marked/Q/T-REC-Q.3932.4-201605-I_PDF-E/raw.md
@@ -0,0 +1,609 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.3932.4**
+
+(05/2016)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Testing specifications – Testing specifications for next generation networks
+
+---
+
+**IMS/NGN performance benchmark – Part 4:
+Testing of the performance design objectives**
+
+Recommendation ITU-T Q.3932.4
+
+**ITU-T**
+
+
+
+ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union'
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120-Q.499 |
+| DIGITAL EXCHANGES | Q.500-Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 |
+| Q3 INTERFACE | Q.800-Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 |
+| INTELLIGENT NETWORK | Q.1200-Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 |
+| BROADBAND ISDN | Q.2000-Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900-Q.4099 |
+| Testing specifications for next generation networks | Q.3900-Q.3999 |
+| Testing specifications for SIP-IMS | Q.4000-Q.4039 |
+| Testing specifications for Cloud computing | Q.4040-Q.4059 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+### Recommendation ITU-T Q.3932.4
+
+# IMS/NGN performance benchmark – Part 4: Testing of the performance design objectives
+
+## Summary
+
+Recommendation ITU-T Q.3932.4 contains the benchmark testing of signalling parameters against the performance design objectives specified in Recommendation ITU-T Q.543 and ETSI TS 101 563, which are applicable to IMS/PES/NGN and VoLTE implementations.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.3932.4 | 2016-05-14 | 11 | 11.1002/1000/12863 |
+
+## Keywords
+
+Benchmark, IP multimedia subsystem, IMS, new generation network, NGN, performance, PSTN/ISDN emulation subsystem, PES, signalling, testing, VoLTE.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|------------------------------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Abbreviations and acronyms ..... | 2 |
+| 4 Metrics and design objectives..... | 2 |
+| 4.1 Delay probability ..... | 2 |
+| 4.2 Loads definitions ..... | 2 |
+| 4.3 Parameter requirements (performance design objectives) ..... | 4 |
+| 4.4 Call processing performance objectives ..... | 27 |
+| 4.5 Transmission performance ..... | 27 |
+| 4.6 Slip rate..... | 27 |
+| Bibliography..... | 29 |
+
+
+
+# IMS/NGN performance benchmark – Part 4: Testing of the performance design objectives
+
+# 1 Scope
+
+This Recommendation contains the benchmark testing of signalling parameters against the performance design objectives specified in ITU-T Q.543 and ETSI TS 101 563, which are applicable to IMS/PES/NGN and VoLTE implementations. The values of the performance design objectives (reference load A and reference load B), which are contained in this Recommendation and found in Table 1 to Table 9, are taken from ETSI TS 101 563. These values are "best practice" performance values measured on IMS/PES/NGN and VoLTE implementations.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T G.812] Recommendation ITU-T G.812 (2004), *Timing requirements of slave clocks suitable for use as node clocks in synchronization networks.*
+- [ITU-T G.823] Recommendation ITU-T G.823 (2000), *The control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy.*
+- [ITU-T Q.541] Recommendation ITU-T Q.541 (1993), *Digital exchange design objectives – General.*
+- [ITU-T Q.543] Recommendation ITU-T Q.543 (1993), *Digital exchange performance design objectives.*
+- [ITU-T Q.3403 v.1] Recommendation ITU-T Q.3403 v.1 (2016), *IP multimedia call control protocol based on the session initiation protocol and the session description protocol – Basic call: Requirements for the user side and the network side.*
+- [ETSI TS 101 563] ETSI TS 101 563 V1.4.1 (2015), *Speech and multimedia Transmission Quality (STQ); IMS/PES/VoLTE exchange performance requirements.*
+- [ETSI TS 102 250-2] ETSI TS 102 250-2 V2.4.1 (2015), *Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in mobile networks; Part 2: Definition of Quality of Service parameters and their computation.*
+- [ETSI TS 102 928] ETSI TS 102 928 V1.1.3 (2014), *Speech and multimedia Transmission Quality (STQ); End-to-End Transmission Planning Requirements for Real Time Services in an NGN context.*
+- [ETSI TS 183 036] ETSI TS 183 036 V3.5.1 (2012), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); ISDN/SIP interworking; Protocol specification.*
+- [ETSI TS 183 043] ETSI TS 183 043 V3.4.1 (2011), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation; Stage 3 specification.*
+
+# 3 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|--------|----------------------------------------------|
+| AGCF | Access Gateway Control Function |
+| CSCF | Call Session Control Function |
+| ECM | EPS Connection Management |
+| GW | Gateway |
+| IAD | Integrated Access Device |
+| IMS | IP Multimedia Subsystem |
+| ISDN | Integrated Service Digital Network |
+| ITU-T | ITU Telecommunication Standardization Sector |
+| MGW | Media Gateway |
+| MME | Mobility Management Entity |
+| MSAN | Multi Service Access Node |
+| NGN | New Generation Network |
+| P-CSCF | Proxy Call Server Control Function |
+| PES | PSTN/ISDN Emulation Subsystem |
+| QCI | QoS Class Identifier |
+| RTP | Real Time Protocol |
+| SBC | Session Border Control |
+| SC | Sending Complete |
+| SDP | Session Description Protocol |
+| S-GW | Signalling Gateway |
+| SIP | Session Initiation Protocol |
+| TIE | Time Interval Error |
+| UE | User Equipment |
+| VGW | Voice Gateway |
+| VoLTE | Voice over LTE |
+
+# 4 Metrics and design objectives
+
+## 4.1 Delay probability
+
+This clause defines delay parameters related to ISDN/PSTN, IMS and VoLTE. The values are based on the values in [ITU-T Q.543] and [ETSI TS 101 563].
+
+## 4.2 Loads definitions
+
+The ISDN/PSTN, IMS and VoLTE reference loads definitions and values described in Table 1 to Table 9 are the reference loads definitions described in [ITU-T Q.543] and [ETSI TS 101 563]. The derived ISDN procedures are based on the ISDN/SIP interworking [ETSI TS 183 036] procedures, the derived PES procedures are based on the IMS/PES Emulation specification [ETSI TS 183 043]
+
+and the derived SIP procedures are based on session initiation protocol (SIP) and session description protocol (SDP) [ITU-T Q.3403 v.1].
+
+
+
+Figure 1: IMS/LTE basic configuration diagram. This diagram shows the network architecture for IMS over LTE. On the left, three User Equipment (UE) blocks, each containing an IMS UA, are connected to different radio access networks: GERAN (via lu-ps), UTRAN (via lu-ps), and LTE-Uu (via eNodeB). The eNodeB connects to an S-GW (via S1-U and S12). The S-GW connects to an MME (via S1-MME) and a P-GW/GGSN (via S5). The MME connects to the HSS (via S6a and S11) and the PCRF (via S12). The PCRF connects to the P-GW/GGSN (via Gx). The P-GW/GGSN connects to the IMS core (via SGi). The IMS core contains several functional entities: VCC AS, MMTel AS, IS-CSCF, P-CSCF (ALG/AGW), and HSS. The P-CSCF connects to the IS-CSCF (via Mw) and the HSS (via Cx). The IS-CSCF connects to the MMTel AS (via ISC) and the VCC AS (via ISC). The VCC AS connects to the HSS (via Sh) and the MMTel AS (via Sh). The HSS connects to the P-CSCF (via Gm). The P-CSCF connects to the MME (via S6b). The MME connects to the MSC Server (VCC) (via S4). The MSC Server (VCC) connects to the MSC server (RAN) (via ISUP). The MSC server (RAN) connects to the GERAN (via lu-cs) and the UTRAN (via lu-cs). The GERAN connects to the UE (via lu-ps). The UTRAN connects to the UE (via lu-ps). The LTE-Uu connection between the UE and the eNodeB is labeled LTE-Uu. The diagram also shows various reference points: Mb, Ut, lu-cs, lu-ps, S4, S6b, S6a, S3, S11, S12, S1-U, S5, Gx, SGi, Gm, Mw, Sh, ISC, Cx, and ISUP/SIP.
+
+Q.3932.4(16)\_F01
+
+Figure 1 – IMS/LTE basic configuration
+
+
+
+Figure 2: AGCF/VGW session processing models diagram. This diagram illustrates the session processing model for AGCF and VGW. It shows two parallel processing paths. The left path starts with a UE connected to a P-CSCF, which is connected to an S-CSCF, which is connected to an AS. The P-CSCF is also connected to a VGW. The VGW contains an MGC, FM, and SIP UA. The MGC is connected to an MGF, which is connected to another UE. The right path starts with a UE connected to an AGCF. The AGCF contains a SIP UA, FM, and MGC. The SIP UA is connected to an S-CSCF, which is connected to an AS. The MGC is connected to an MGF, which is connected to another UE. Both MGFs are connected to a central RTP cloud. The diagram also shows the internal components of the VGW and AGCF: MGC, FM, SIP UA, and MGF.
+
+Q.3932.4(16)\_F02
+
+Figure 2 – AGCF/VGW session processing models
+
+Figure 2 illustrates the session processing model used by the AGCF and VGW functional entities.
+
+An AGCF is modelled as comprising ITU-T H.248 Media Gateway Controller (MGC), Feature Manager (FM), and SIP UA functionality. An AGCF interfaces to a Media Gateway (MG) and also to the S-CSCF (via P1 and Mw reference points respectively).
+
+A functional modelling of the VGW contains an entity similar to ITU-T H.248 Media Gateway Controller, a Feature Manager, a SIP UA, and MGW functionality. The VGW interfaces to the P-CSCF using the Gm reference point.
+
+The SIP UA functionality provides the interface to the other components of the IMS-based architecture. It is involved in registration and session processing as well as in event subscription/notification procedures with application servers.
+
+The MGC functionality enable the session processing functionality to interface with existing line signalling such as analogue signalling or DSS1.
+
+Session and registration processing in the AGCF or VGW involves two halves: ITU-T H.248 based MGC processing and SIP user agent (UA) processing (see Figure 2). MGC processing focuses on the interactions with the media gateway functions, while SIP UA processing focuses on the interactions with the IMS components. The feature manager (FM) coordinates the two processing activities.
+
+## **4.3 Parameter requirements (performance design objectives)**
+
+IMS/PES/VoLTE exchange implementations shall comply with the requirements given in Table 1 to Table 9.
+
+NOTE – The values of the performance design objectives (reference load A and reference load B), which are contained in this Recommendation and found in Table 1 to Table 9, are taken from [ETSI TS 101 563].
+
+**Table 1**
+
+| Meaning of timers | Parameter ITU-T Q.543 | IMS, PES equivalent | Reference load A | | Reference load B | |
+|----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|----------------------------------|------------------|----------------------------------|
+| | | | Mean value | 95% probability of not exceeding | Mean value | 95% probability of not exceeding |
+| Local exchange call request delay – originating outgoing and internal traffic connections | | | | | | |
+| ANALOGUE SUBSCRIBER LINES
Local exchange call request delay – originating outgoing and internal traffic connections. | Clause 2.3.2.1 of [ITU-T Q.543]
For ANALOGUE SUBSCRIBER LINES, call request delay is defined as the interval from the instant when the off-hook condition is recognizable at the subscriber line interface of the exchange until the exchange begins to apply dial tone to the line. The call request delay interval is assumed to correspond to the period at the beginning of a call attempt during which the exchange is unable to receive any call address information from the subscriber. | PES [ETSI TS 183 043]
For ANALOGUE SUBSCRIBER LINES connected to the AGCF/MSAN.
Call request delay is defined as the interval from the instant when the off-hook condition is recognizable at the subscriber line interface of the AGCF/MSAN until the AGCF/MSAN begins to apply dial tone to the line. | ≤ 400 ms | ≤ 600 ms | ≤ 800 ms | ≤ 1 000 ms |
+| ANALOGUE SUBSCRIBER with IAD (VGW)
Local exchange call request delay – originating outgoing and internal traffic connections. | | PES [ETSI TS 183 043]
For ANALOGUE SUBSCRIBER LINES connected to the VGW.
Call request delay is defined as the interval from the instant when the off-hook condition is recognizable at the subscriber line interface of the VGW until the VGW begins to apply dial tone to the line. | ≤ 400 ms | ≤ 600 ms | ≤ 800 ms | ≤ 1 000 ms |
+
+
+
+The diagram consists of two side-by-side timing diagrams illustrating the call request delay for an analogue subscriber in two different network architectures.
+
+- ITU-T Q.543:** On the left, a horizontal line labeled "Analogue line" has an arrow pointing to a box labeled "OLE". Above the arrow is the text "Off hook". Below the arrow is a sine wave labeled "Dial tone". A vertical blue arrow points downwards from the "Off hook" point on the line to the "Dial tone" waveform, indicating the time delay between the two events.
+- IMS:** On the right, a similar horizontal line labeled "Analogue line" has an arrow pointing to a box labeled "AGCF". Above the arrow is the text "Off hook". Below the arrow is a sine wave labeled "Dial tone". A vertical blue arrow points downwards from the "Off hook" point on the line to the "Dial tone" waveform, indicating the time delay between the two events.
+
+Below the IMS diagram, the text "Q.3932.4(16)\_F03" is present.
+
+Timing diagrams for ITU-T Q.543 and IMS showing call request delay with overlap sending.
+
+**Figure 3 – Local exchange analogue subscriber call request delay: overlap sending**
+
+**Table 2**
+
+| Meaning of timers | Parameter ITU-T Q.543 | IMS, PES equivalent | Reference load A | | Reference load B | |
+|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------------------------|-------------------------|-----------------------------------------|
+| | | | Mean value | 95% probability of not exceeding | Mean value | 95% probability of not exceeding |
+| Local exchange ISDN subscriber call request delay: overlap sending | | | | | | |
+| ISDN SUBSCRIBER LINES
Local exchange call request delay – Overlap sending. | Clause 2.3.2.2 of [ITU-T Q.543]
Local exchange call request delay.
Call request delay is defined as the interval from the instant at which the SET-UP message has been received from the subscriber signalling system until the SET-UP ACKNOWLEDGE message is passed back to the subscriber signalling system. | ISDN [ETSI TS 183 036]
Call request delay is defined as the interval from the instant at which the SET-UP message has been received from the subscriber signalling system until the SET-UP ACKNOWLEDGE message is passed back to the subscriber signalling system. | ≤ 200 ms | ≤ 250 ms | ≤ 300 ms | ≤ 400 ms |
+| IMS SUBSCRIBER
Local exchange call request delay. | | IMS [ITU-T Q.3403 v.1]
Call request delay is defined as the interval from the instant at which the INVITE message has been received from the SIP subscriber until the 100 Trying from the SBC/P-CSCF is passed back to the subscriber. | ≤ 15 ms | ≤ 20 ms | ≤ 30 ms | ≤ 40 ms |
+
+
+
+Sequence diagrams comparing ITU-T Q.543 and IMS call request delays. The ITU-T Q.543 diagram shows an OLE receiving a SETUP message on an ISDN line and sending a SETUP ACK. The IMS diagram shows an AGCF/VGW receiving a SETUP message on an ISDN line and sending a SETUP ACK, and an SBC/P-CSCF receiving an INVITE message on a SIP line and sending a 100 trying. Blue vertical arrows indicate the call request delay in each case. The source 'Q.3932.4(16)\_F04' is noted at the bottom right.
+
+Figure 4 – Local exchange ISDN subscriber call request delay: overlap sending
+
+Table 3
+
+| Meaning of timers | Parameter ITU-T Q.543 | IMS, PES equivalent | Reference load A | | Reference load B | |
+|-------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|----------------------------------|------------------|----------------------------------|
+| | | | Mean value | 95% probability of not exceeding | Mean value | 95% probability of not exceeding |
+| Local exchange ISDN subscriber call request delay: en-block sending | | | | | | |
+| ISDN SUBSCRIBER LINES
Local exchange call request delay en- block sending. | Clause 2.3.2.3 of [ITU-T Q.543]
For DIGITAL SUBSCRIBER LINES using en-bloc sending, call request delay is defined as the interval from the instant at which the SET-UP message is received | ISDN [ETSI TS 183 036]
For ISDN using en-bloc sending, call request delay is defined as the interval from the instant at which the SET-UP message is received from the subscriber signalling system until | ≤ 300 ms | ≤ 400 ms | ≤ 500 ms | ≤ 600 ms |
+
+| Meaning of timers | Parameter ITU-T Q.543 | IMS, PES equivalent | Reference load A | | Reference load B | |
+|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|------------------|----------------------------------|------------------|----------------------------------|
+| | | | Mean value | 95% probability of not exceeding | Mean value | 95% probability of not exceeding |
+| Local exchange ISDN subscriber call request delay: en-block sending | | | | | | |
+| | from the subscriber signalling system until the call proceeding message is passed back to the subscriber signalling system. | the CALL PROCEEDING message is passed back to the subscriber signalling system. | | | | |
+
+
+
+The diagram consists of two sequence diagrams side-by-side. The left diagram is labeled 'ITU-T Q.543' and shows an 'OLE' (Office Line Equipment) box. A horizontal arrow labeled 'SETUP' points from an 'ISDN line' to the 'OLE'. A vertical blue line drops from the 'OLE' box. A horizontal arrow labeled 'CALL PROCEEDING' points from the 'OLE' back to the 'ISDN line'. The right diagram is labeled 'IMS' and shows an 'AGCF/VGW' (Access Gateway Control Function/Voice Gateway) box. It follows the same pattern: a 'SETUP' arrow from 'ISDN line' to 'AGCF/VGW', a vertical blue line at the 'AGCF/VGW', and a 'CALL PROCEEDING' arrow back to the 'ISDN line'. Below the diagrams is the text 'Q.3932.4(16)\_F05'.
+
+Sequence diagrams comparing ITU-T Q.543 (OLE) and IMS (AGCF/VGW) call request delays. Both show a SETUP message from an ISDN line to the network element and a CALL PROCEEDING message back to the ISDN line. A vertical blue line indicates the delay between the two messages at the network element.
+
+Figure 5 – Local exchange ISDN subscriber call request delay: en-block sending
+
+**Table 4**
+
+| Meaning of timers | Parameter ITU-T Q.543 | IMS, PES equivalent | Reference load A | | Reference load B | |
+|-------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------------------------|-------------------------|-----------------------------------------|
+| | | | Mean value | 95% probability of not exceeding | Mean value | 95% probability of not exceeding |
+| Alerting sending delay for terminating traffic (the users are in different locations, controlled by different S-CSCF/P-CSCF) | | | | | | |
+| ANALOGUE SUBSCRIBER LINES
Alerting sending Delay for terminating traffic. | Clause 2.3.6.1.1 of [ITU-T Q.543]
For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant when the last digit is available for processing in the exchange until the ringing tone is sent backwards toward the calling user. | PES [ETSI TS 183 043]
For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant when the last digit is available for processing in the AGCF/MSAN until the ringing tone is sent toward the calling user. | ≤ 300 ms | ≤ 450 ms | ≤ 600 ms | ≤ 750 ms |
+| ISDN SUBSCRIBER LINES
Alerting sending Delay for terminating traffic. | Clause 2.3.6.1.2 of [ITU-T Q.543]
For calls terminating on DIGITAL SUBSCRIBER LINES, the alerting sending delay is defined as the interval from the instant that an ALERTING message is received from the digital subscriber line signalling system to the instant at which an ADDRESS COMPLETE message is passed to the interexchange signalling system or ringing tone is sent backward toward the calling user. | ISDN [ETSI TS 183 036]
For calls terminating on ISDN, the alerting sending delay is defined as the interval from the instant that an ALERTING message is received from the digital subscriber line signalling to the instant at which an AGCF/MSAN sends the 180 Ringing backward toward the calling user. | ≤ 250 ms | ≤ 300 ms | ≤ 350 ms | ≤ 400 ms |
+
+
+
+The diagram illustrates the local exchange alerting sending delay for terminating traffic across different network types and locations.
+
+**ITU-T Q.543:**
+
+- Analogue line:** Shows a DLE (Digital Line Equipment) connected to an analogue line. The "Latest address digit" is received, and the "Ringing tone" is generated. A blue arrow indicates the delay from the digit to the start of the ringing tone.
+- ISDN line:** Shows a DLE connected to an ISDN line. The "ALERTING" message is sent to the network, and the "ACM" (Answer Control Message) is received. A blue arrow indicates the delay from the start of the ringing tone to the "ALERTING" message.
+
+**IMS:**
+
+- Analogue line:** Shows an AGCF/VGW (Access Gateway Control Function/Voice Gateway) connected to an analogue line. Similar to the ITU-T Q.543 analogue line, it shows the "Latest address digit" and "Ringing tone" with a delay indicated by a blue arrow.
+- ISDN line:** Shows an AGCF/VGW connected to an ISDN line. The "ALERTING" message is sent, and "180 ringing" is received. A blue arrow indicates the delay from the start of the ringing tone to the "ALERTING" message.
+- SIP line:** Shows an SBC/P-CSCF (Session Border Controller/Proxy-CSCF) connected to a SIP line. The "180 ringing" message is sent to the network, and another "180 ringing" message is received. A blue arrow indicates the delay from the start of the ringing tone to the outgoing "180 ringing" message.
+
+Q.3932.4(16)\_F06
+
+Timing diagrams for ITU-T Q.543 and IMS showing alerting sending delays for analogue, ISDN, and SIP lines.
+
+**Figure 6 – Local exchange alerting sending delay for terminating traffic (in different locations)**
+
+**Table 5**
+
+| Meaning of timers | Parameter ITU-T Q.543 | IMS, PES equivalent | Reference load A | | Reference load B | |
+|----------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------------------------|-------------------------|-----------------------------------------|
+| | | | Mean value | 95% probability of not exceeding | Mean value | 95% probability of not exceeding |
+| Alerting sending delay for internal traffic (the user are in same locations, controlled by same AGCF/VGW or P-CSCF) | | | | | | |
+| ANALOGUE SUBSCRIBER LINES
Alerting sending Delay for internal traffic. | Clause 2.3.6.2.1 of [ITU-T Q.543]
For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant that the signalling information is available for processing in the exchange until ringing tone is applied to an ANALOGUE calling subscriber. | PES [ETSI TS 183 043]
For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant that the signalling information is available for processing in the AGCF/MSAN until Ringing tone is sent towards the calling subscriber. | ≤ 300 ms | ≤ 450 ms | ≤ 600 ms | ≤ 750 ms |
+| ANALOGUE SUBSCRIBER LINES
Alerting sending Delay for internal traffic. | | PES [ETSI TS 183 043]
For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant that the signalling information is available for processing in the MGW/VGW until Ringing tone is sent towards the calling subscriber. | ≤ 550 ms | ≤ 800 ms | ≤ 1 000 ms | ≤ 1 100 ms |
+
+**Table 5**
+
+| Meaning of timers | Parameter ITU-T Q.543 | IMS, PES equivalent | Reference load A | | Reference load B | |
+|-----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------------------------|-------------------------|-----------------------------------------|
+| | | | Mean value | 95% probability of not exceeding | Mean value | 95% probability of not exceeding |
+| Detailed description | | | | | | |
+| ISDN SUBSCRIBER LINES
Alerting sending Delay for Internal traffic. | Clause 2.3.6.2.2 of [ITU-T Q.543]
For internal calls terminating on DIGITAL SUBSCRIBER LINES originating from DIGITAL SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant that an ALERTING message is received from the signalling system of the called subscriber's line until the ALERTING message is applied to the calling subscriber line. | ISDN [ETSI TS 183 036]
For calls terminating on ISDN, alerting sending delay is defined as the interval from the instant that an ALERTING message is received and ALERTING is sent towards the calling subscriber. | ≤ 300 ms | ≤ 350 ms | ≤ 400 ms | ≤ 450 ms |
+| IMS SUBSCRIBER LINES
180 sending Delay for Internal traffic. | | IMS
For calls terminating sending delay is defined as the interval from the instant that a 180 message at the Gm interface has received and 180 is sent on the Gm towards the calling subscriber. | ≤ 100 ms | ≤ 150 ms | ≤ 200 ms | ≤ 250 ms |
+| VoLTE SUBSCRIBER LINES
180 sending Delay for Internal traffic. | | VoLTE
For calls terminating sending delay is defined as the interval from the instant that a 180 message at the VoLTE – UE interface has received and 180 is sent on the VoLTE – UE towards the calling subscriber. | ≤ 150 ms | ≤ 200 ms | ≤ 250 ms | ≤ 300 ms |
+
+
+
+The diagram illustrates the alerting sending delay for internal traffic in two scenarios: ITU-T Q.543 and IMS.
+
+**ITU-T Q.543:**
+
+- Top part:** Shows an analogue line connection between a calling party and a called party via an OLE/DLE. The 'Latest address digit' is sent from the calling party to the OLE/DLE. A 'Ringing tone' is generated by the OLE/DLE and sent to the called party. A blue arrow indicates the alerting signal being sent from the OLE/DLE to the called party.
+- Bottom part:** Shows an ISDN line connection between a calling party and a called party via an OLE/DLE. The calling party sends an 'ALERTING' message to the OLE/DLE, which then sends an 'ALERTING' message to the called party. A blue arrow indicates the alerting signal being sent from the OLE/DLE to the called party.
+
+**IMS:**
+
+- Top part:** Similar to the ITU-T Q.543 analogue line scenario, but the network element is an AGCF/VGW. The 'Latest address digit' is sent from the calling party to the AGCF/VGW, which generates a 'Ringing tone' for the called party. A blue arrow indicates the alerting signal being sent from the AGCF/VGW to the called party.
+- Middle part:** Similar to the ITU-T Q.543 ISDN line scenario, but the network element is an AGCF/VGW. The calling party sends an 'ALERTING' message to the AGCF/VGW, which then sends an 'ALERTING' message to the called party. A blue arrow indicates the alerting signal being sent from the AGCF/VGW to the called party.
+- Bottom part:** Shows a SIP line connection between a calling party and a called party via a Gm interface. The calling party sends a '180 ringing' message to the Gm interface, which then sends a '180 ringing' message to the called party. A blue arrow indicates the alerting signal being sent from the Gm interface to the called party.
+
+Q.3932.4(16)\_F07
+
+Sequence diagrams comparing alerting sending delays for ITU-T Q.543 and IMS internal traffic. The diagrams show the flow of signals like 'Latest address digit', 'Ringing tone', 'ALERTING', and '180 ringing' between calling and called parties through various network elements like OLE/DLE, AGCF/VGW, and Gm interface.
+
+**Figure 7 – Alerting sending delay for internal traffic
+(the user are in same locations, controlled by same AGCF/VGW or P-CSCF)**
+
+**Table 6**
+
+| Meaning of timers | Parameter ITU-T Q.543 | IMS, PES equivalent | Reference load A | | Reference load B | |
+|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------------------------|-------------------------|-----------------------------------------|
+| | | | Mean value | 95% probability of not exceeding | Mean value | 95% probability of not exceeding |
+| Call set-up delay | | | | | | |
+| ISDN
SUBSCRIBER
LINES
Call set-up delay
using overlap
signalling. | Clause 2.4.3.1 of [ITU-T Q.543]
Call set-up delay is defined as the interval from the instant when the signalling information required for routing is received from the incoming signalling system until the instant when the corresponding signalling information is passed to the outgoing signalling system.
Exchange call set-up delay for originating outgoing traffic connections, digital subscriber lines. The time interval starts when the INFORMATION message received contains a "sending complete indication" or when the address information necessary for call set-up is complete and ends when the corresponding signalling information is passed to the outgoing signalling system. | ISDN [ETSI TS 183 036]
Sending, the time interval starts when the INFORMATION message received contains a "sending complete indication" and ends when the INVITE message on the Ic interface has been sent. | ≤ 400 ms | ≤ 500 ms | ≤ 550 ms | ≤ 650 ms |
+| | | ISDN [ETSI TS 183 036]
Sending, the time interval starts when the INFORMATION message received contains a "sending complete indication" and ends when the INVITE message on terminating Gm interface has been sent. | ≤ 450 ms | ≤ 450 ms | ≤ 550 ms | ≤ 650 ms |
+
+**Table 6**
+
+| Meaning of timers | Parameter ITU-T Q.543 | IMS, PES equivalent | Reference load A | | Reference load B | |
+|--------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------------------------|-------------------------|-----------------------------------------|
+| | | | Mean value | 95% probability of not exceeding | Mean value | 95% probability of not exceeding |
+| | Detailed description | IMS [ITU-T Q.3403 v.1]
Session initiation call set-up delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating Gm interface until the instant when the corresponding INVITE signalling information is passed on the terminating Ic interface to the called user | ≤ 250 ms | ≤ 350 ms | ≤ 450 ms | ≤ 550 ms |
+
+
+
+The diagram illustrates call set-up delay using overlap sending across three scenarios:
+
+- ITU-T Q.543:** An OLE (Office Line Equipment) receives **SETUP**, **INFO**, and **INFO (SC)** messages from an **ISDN line**. As soon as the **SETUP** message is received, an **IAM** (Initial Address Message) is forwarded to the next hop, as indicated by a blue arrow.
+- IMS (Option 1):** An **AGCF/VGW** (Access Gateway Control Function/Video Gateway) receives **SETUP**, **INFO**, and **INFO (SC)** messages from an **ISDN line**. Upon receiving **SETUP**, it immediately sends an **INVITE** message to the **IBCF/terminating Gm** (Interconnection Boundary Control Function/terminating Gateway). The **AGCF/VGW** is labeled as the **Calling** party and the **IBCF/terminating Gm** as the **Called** party.
+- or**
+- IMS (Option 2):** An **AGCF/VGW** receives **SETUP**, **INFO**, and **INFO (SC)** messages from an **ISDN line**. Upon receiving **SETUP**, it immediately sends a **SETUP** message to the **Called** party.
+- IMS (Option 3):** An **originating Gm** receives **INVITE**, **INFO/INVITE**, and **INFO/INVITE** messages from a **SID line**. Upon receiving the first **INVITE**, it immediately sends an **INVITE** message to the **IBCF/terminating Gm**. The **originating Gm** is labeled as the **Calling** party and the **IBCF/terminating Gm** as the **Called** party.
+
+Sequence diagrams illustrating call set-up delay with overlap sending for ITU-T Q.543 and IMS protocols.
+
+Q.3932.4(16)\_F08
+
+**Figure 8 – Call set-up delay: Overlap sending is used**
+
+**Table 7**
+
+| Meaning of timers | Parameter ITU-T Q.543 | IMS, PES equivalent | Reference load A | | Reference load B | |
+|-----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------------------------|-------------------------|-----------------------------------------|
+| | | | Mean value | 95% probability of not exceeding | Mean value | 95% probability of not exceeding |
+| Call set-up delay: en-block sending is used | | | | | | |
+| ISDN
SUBSCRIBER
LINES
Call set-up delay
using en-block
signalling. | Clause 2.4.3.1 of [ITU-T Q.543]
Exchange call set-up delay for originating outgoing traffic connections.
For call attempts using en-bloc sending
Call set-up delay is defined as the interval from the instant when the signalling information required for routing is received from the incoming signalling system until the instant when the corresponding signalling information is passed to the outgoing signalling system.
The time interval starts when the SET-UP message received contains a "sending complete indication" or when the address information necessary for call set-up is complete and ends when the call set-up is sent on the outgoing signalling system. | ISDN [ETSI TS 183 036]
Call set-up delay is defined as the interval from the instant when the signalling information including Sending Complete (#) is received from the incoming signalling system until the instant when the corresponding INVITE signalling information is passed to the Ic interface. | ≤ 350 ms | ≤ 450 ms | ≤ 550 ms | ≤ 650 ms |
+| | | ISDN [ETSI TS 183 036]
Call set-up delay is defined as the interval from the instant when the signalling information including Sending Complete (#) is received from the incoming signalling system until the instant when the corresponding INVITE signalling information is passed to the terminating Gm interface. | ≤ 350 ms | ≤ 450 ms | ≤ 550 ms | ≤ 650 ms |
+| | | ISDN [ETSI TS 183 036]
Call set-up delay for Internal traffic is defined as the interval from the instant when the SET-UP including Sending Complete (#) is received from the incoming signalling system until the | ≤ 450 ms | ≤ 550 ms | ≤ 650 ms | ≤ 750 ms |
+
+**Table 7**
+
+| Meaning of timers | Parameter ITU-T Q.543 | IMS, PES equivalent | Reference load A | | Reference load B | |
+|-----------------------------------------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------------------------|-------------------------|-----------------------------------------|
+| | | | Mean value | 95% probability of not exceeding | Mean value | 95% probability of not exceeding |
+| Call set-up delay: en-block sending is used | | | | | | |
+| | Detailed description | instant when the corresponding SET-UP signalling information is passed to the called line signalling system (see Note 1). | | | | |
+| IMS SUBSCRIBER
Call set-up delay using for Internal traffic. | | IMS [ITU-T Q.3403 v.1]
Session initiation call set-up delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating Gm interface until the instant when the corresponding INVITE signalling information is passed on the terminating Gm interface to the called user. | ≤ 250 ms | ≤ 350 ms | ≤ 450 ms | ≤ 550 ms |
+| | | VoLTE
Session initiation delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating VoLTE – UE (ECM idle ) interface until the instant when the corresponding INVITE signalling information is passed on the terminating VoLTE – UE (ECM Idle) | ≤ 1 800 ms | ≤ 1900 ms | ≤ 2 000 ms | ≤ 2 100 ms |
+
+**Table 7**
+
+| Meaning of timers | Parameter ITU-T Q.543 | IMS, PES equivalent | Reference load A | | Reference load B | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------------------------|-------------------------|-----------------------------------------|
+| | | | Mean value | 95% probability of not exceeding | Mean value | 95% probability of not exceeding |
+| Call set-up delay: en-block sending is used | | | | | | |
+| | | interface to the called user with QCI 1 (see Note 2). | | | | |
+| | | VoLTE
Session initiation delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating VoLTE – UE (ECM Connected ) interface until the instant when the corresponding INVITE signalling information is passed on the terminating VoLTE – UE (ECM Connected ) interface to the called user (see Note 3). | ≤ 280 ms | ≤ 380 ms | ≤ 500 ms | ≤ 600 ms |
+| Call set-up time: | | | | | | |
+| | | VoLTE
The definition of Call set-up time is defined in [ETSI TS 102 250-2]. | ≤ 1 950 ms | ≤ 2 100 ms | ≤ 2 250 ms | ≤ 2 400 ms
(Note 4) |
+| NOTE 1 – If SC (#) is not included the set-up delay may increase up to the digit collection timer (15 s).
NOTE 2 – Paging Cycle 1.28 s.
NOTE 3 – S1-Control plane delay: 2 ms – 15 ms (S1 is the interface between eNode Bs and MME and S-GW).
NOTE 4 – The maximum value should not exceed 5.9 seconds. | | | | | | |
+
+
+
+The figure consists of three sequence diagrams illustrating call set-up delay when en-block sending is used.
+
+**ITU-T Q.543 Diagram:** An ISDN line sends a **SETUP** message to an **OLE** (Office Line Equipment). The OLE then sends an **IAM** (Initial Address Message) to the next node. A blue arrow indicates the processing delay at the OLE.
+
+**IMS Diagram 1:** An ISDN line sends a **SETUP** message to an **AGCF/VGW** (Access Gateway Control Function/Video Gateway). The AGCF/VGW sends an **INVITE** message to an **IBCF/terminating Gm** (Interconnection Border Control Function/terminating Gateway). A blue arrow indicates the processing delay at the AGCF/VGW.
+
+**IMS Diagram 2:** An ISDN line sends a **SETUP** message to an **AGCF/VGW**. This AGCF/VGW sends a **SETUP** message to another **AGCF/VGW**. A blue arrow indicates the processing delay at the first AGCF/VGW.
+
+**IMS Diagram 3:** A **Gm interface** receives an **INVITE** message from a **SIP line**. This Gm interface sends an **INVITE** message to another **Gm interface**, which then sends it to another **SIP line**. A blue arrow indicates the processing delay at the first Gm interface.
+
+Q.3932.4(16)\_F09
+
+Sequence diagrams illustrating call set-up delay for ITU-T Q.543 and IMS. The diagrams show the flow of signaling messages (SETUP, IAM, INVITE) between an ISDN line and various network elements like OLE, AGCF/VGW, IBCF/terminating Gm, and Gm interface. Blue arrows indicate processing delays at each node.
+
+Figure 9 – Call set-up delay: en-block sending is used
+
+**Table 8**
+
+| Meaning of timers | Parameter ITU-T Q.543 | IMS, PES equivalent | Reference load A | | Reference load B | |
+|----------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------------------|-------------------------|------------------------------------------|
+| | | | Mean value | 95 % probability of not exceeding | Mean value | 95 % probability of not exceeding |
+| Through-connection delay | | | | | | |
+| ISDN
SUBSCRIBER
LINES
Through-connection delay. | Clause 2.4.4.2 of ITU-T Q.543
Through-connection delay.
The through connection delay is defined as the interval from the instant that the CONNECT message is received from the called line signalling system until the through connection is established and available for carrying traffic and the ANSWER and CONNECT ACKNOWLEDGEMENT messages have been passed to the appropriate signalling systems. | ISDN [ETSI TS 183 036]
The through connection delay is defined as the interval from the instant that the CONNECT message is received from the called line signalling system until the through connection is established and available for carrying traffic and the CONNECT message has been sent to the calling user signalling system (see Note). | ≤ 300 ms | ≤ 350 ms | ≤ 400 ms | ≤ 450 ms |
+| IMS
Through-connection delay
Delay for Internal traffic. | | IMS [ITU-T Q.3403 v.1]
The through connection delay is defined as the interval from the instant that the 200 OK message is received from the called user at the terminating Gm interface until the through connection is established and available for carrying traffic and the 200 OK message has been sent to the calling user on the originating Gm interface. | ≤ 100 ms | ≤ 150 ms | ≤ 200 ms | ≤ 250 ms |
+
+| Meaning of timers | Parameter ITU-T Q.543 | IMS, PES equivalent | Reference load A | | Reference load B | |
+|---------------------------------------------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-----------------------------------|------------------|-----------------------------------|
+| | | | Mean value | 95 % probability of not exceeding | Mean value | 95 % probability of not exceeding |
+| VoLTE | Detailed description | VoLTE
The through connection delay is defined as the interval from the instant that the 200 OK message is received from the called user at the terminating VoLTE – UE interface until the through connection is established and available for carrying traffic and the 200 OK message has been sent to the calling user on the originating VoLTE – UE interface. | ≤ 150 ms | ≤ 200 ms | ≤ 250 ms | ≤ 300 ms |
+| NOTE – The through connection of RTP is not considered. | | | | | | |
+
+
+
+Sequence diagrams illustrating through-connection delay for ITU-T Q.543 and IMS. The ITU-T Q.543 diagram shows a DLE sending a 'Connect' message over an ISDN line, receiving a 'Connect ACK', and then sending an 'ANM' message. The IMS diagram shows two parts: the top part shows an originating AGCF/VGW sending a 'Connect' message over an ISDN line to a terminating AGCF/VGW, which then sends a 'Connect' message over another ISDN line. The bottom part shows an originating Gm interface sending a '200 OK INVITE' message over a SIP line to a terminating Gm interface, which then sends a '200 OK INVITE' message over another SIP line. Blue vertical arrows indicate the start and end points for measuring the through-connection delay in each scenario. A label 'Q.3932.4(16)\_F10' is present at the bottom right of the IMS diagram.
+
+Figure 10 – Through-connection delay
+
+Table 9
+
+| Meaning of timers | Parameter ITU-T Q.543 | IMS, PES equivalent | Reference load A | | Reference load B | | |
+|---------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-----------------------------------|------------------|-----------------------------------|--|
+| | | | Mean value | 95 % probability of not exceeding | Mean value | 95 % probability of not exceeding | |
+| | Detailed description | | | | | | |
+| Connection release delay: | | | | | | | |
+| ISDN SUBSCRIBER LINES
Connection call release delay. | Clause 2.4.6 of ITU-T Q.543
Connection release delay is defined as the interval from the instant when DISCONNECT or RELEASE message is received from a signalling system until the instant | ISDN [ETSI TS 183 036]
Connection release delay is defined as the interval from the instant when DISCONNECT or RELEASE message is received from a signalling system until the instant when | ≤ 300 ms | ≤ 350 ms | ≤ 400 ms | ≤ 450 ms | |
+
+| Meaning of timers | Parameter ITU-T Q.543 | IMS, PES equivalent | Reference load A | | Reference load B | |
+|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-----------------------------------|------------------|-----------------------------------|
+| | | | Mean value | 95 % probability of not exceeding | Mean value | 95 % probability of not exceeding |
+| | Detailed description | | | | | |
+| | when the connection is no longer available for use on the call (and is available for use on another call) and a corresponding RELEASE or DISCONNECT message is passed to the other signalling system involved in the connection. | RELEASE COMPLETE is sent and a corresponding RELEASE or DISCONNECT message is sent, or vice versa. | | | | |
+| IMS SUBSCRIBER
Connection call release delay
Delay for Internal traffic. | | IMS [ITU-T Q.3403 v.1]
Connection release delay is defined as the interval from the instant when a BYE message is received at the originating or terminating Gm interface until the instant when 200OK is sent and a corresponding BYE message is sent at the terminating or originating Gm interface respectively. | ≤ 100 ms | ≤ 150 ms | ≤ 200 ms | ≤ 250 ms |
+| VoLTE – IMS SUBSCRIBER
Connection call release delay
Delay for Internal traffic. | | VoLTE
Connection release delay is defined as the interval from the instant when a BYE message is received at the originating or terminating VoLTE – UE interface until the instant when 200OK is sent and a corresponding BYE message is sent at the terminating or originating VoLTE – UE interface respectively. | ≤ 150 ms | ≤ 200 ms | ≤ 250 ms | ≤ 300 ms |
+
+
+
+The diagram illustrates two call release scenarios:
+
+- ITU-T Q.543:**
+ - Entities: OLE and DLE.
+ - Interfaces: ISDN line for both.
+ - Release Sequence:
+ - OLE sends a DISCONNECT/RELEASE message to DLE.
+ - A blue vertical arrow points down from the OLE lifeline, indicating a delay.
+ - After the delay, DLE sends a DISCONNECT/RELEASE message to the OLE.
+- IMS:**
+ - AGCF/VGW Interface:**
+ - Entities: originating AGCF/VGW and terminating AGCF/VGW.
+ - Interfaces: ISDN line for both.
+ - Release Sequence:
+ - terminating AGCF/VGW sends a DISCONNECT/RELEASE message to originating AGCF/VGW.
+ - A blue vertical arrow points down from the terminating AGCF/VGW lifeline, indicating a delay.
+ - After the delay, originating AGCF/VGW sends a DISCONNECT/RELEASE message to the terminating AGCF/VGW.
+ - Gm Interface:**
+ - Entities: originating Gm interface and terminating Gm interface.
+ - Interfaces: SIP line for both.
+ - Release Sequence:
+ - terminating Gm interface sends a BYE message to originating Gm interface.
+ - A blue vertical arrow points down from the terminating Gm interface lifeline, indicating a delay.
+ - After the delay, originating Gm interface sends a BYE message to the terminating Gm interface.
+
+Q.3932.4(16)\_F11
+
+Sequence diagrams for ITU-T Q.543 and IMS call release delays. The ITU-T Q.543 diagram shows OLE and DLE entities with ISDN lines and DISCONNECT/RELEASE messages. The IMS diagram shows originating and terminating AGCF/VGW and Gm interfaces with ISDN and SIP lines, using DISCONNECT/RELEASE and BYE messages. Blue arrows indicate release delays.
+
+Figure 11 – Connection call release delay
+
+### **4.4 Call processing performance objectives**
+
+#### **4.4.1 Premature release**
+
+The probability that an exchange malfunction will result in the premature release of an established connection in any one minute interval shall be:
+
+$$P \leq 2 \times 10^{-5}$$
+
+#### **4.4.2 Release failure**
+
+The probability that an exchange malfunction will prevent the required release of a connection shall be:
+
+$$P \leq 2 \times 10^{-5}$$
+
+#### **4.4.3 Incorrect charging or accounting**
+
+The probability of a call attempt receiving incorrect charging or accounting treatment due to an exchange malfunction shall be:
+
+$$P \leq 10^{-4}$$
+
+#### **4.4.4 Misrouting**
+
+The probability of a call attempt misrouted following receipt by the exchange of a valid address shall be:
+
+$$P \leq 10^{-4}$$
+
+#### **4.4.5 No tone**
+
+The probability of a call attempt encountering no tone following receipt of a valid address by the exchange shall be:
+
+$$P \leq 10^{-4}$$
+
+#### **4.4.6 Other failures**
+
+The probability of the exchange causing a call failure for any other reason not identified specifically above shall be:
+
+$$P \leq 10^{-4}$$
+
+### **4.5 Transmission performance**
+
+#### **4.5.1 64 kbit/s switched connections**
+
+The probability of a connection being established with an unacceptable transmission quality across the exchange shall be:
+
+$$P \leq 10^{-5}$$
+
+The transmission quality across the exchange is said to be unacceptable when the bit error ratio is above the alarm condition.
+
+NOTE – According to [b-ITU-T G.826] and [b-ITU-T G.828], budgets of 18.5% of $1.5 \times 10^{-6}$ were allocated to each national network, so the packet loss for a national connection should be no more than $2.75 \times 10^{-7}$ [ETSI TS 102 928].
+
+### **4.6 Slip rate**
+
+#### **4.6.1 Normal conditions**
+
+The slip rate under normal conditions is covered in [ITU-T Q.541].
+
+#### **4.6.2 Temporary loss of timing control**
+
+The case of temporary loss of timing control corresponds to the "holdover operation" defined and recommended in [ITU-T G.812]. The allowable slip rate will correspond to the maximum relative TIE also recommended in [ITU-T G.812].
+
+#### **4.6.3 Abnormal conditions at the exchange input**
+
+The slip rate in case of abnormal conditions (wide phase deviations, etc.) at the exchange input is the subject of further study taking into account the requirements of [ITU-T G.823].
+
+## Bibliography
+
+- [b-ITU-T G.826] *Recommendation ITU-T G.826 (1993), End-to-end performance parameters and objectives for international, constant bit-rate digital paths and connections.*
+- [b- ITU-T G.828] *Recommendation ITU-T G.828 (2000), Error performance parameters and objectives for international, constant bit-rate synchronous digital paths.*
+
+
+
+
+
+## **SERIES OF ITU-T RECOMMENDATIONS**
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/01e00200a536673d6cd0e6d8705047a0_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/01e00200a536673d6cd0e6d8705047a0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4538b515486dcb5bb155ddb956b11a55593bb6f1
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/01e00200a536673d6cd0e6d8705047a0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:58749d05c5eb0fb036323f368a50f33625577a885a9200f5bdc981920cc2945f
+size 20738
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..75c8affa0dfe148b248e447bbd43aec0d7f1d076
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b665234525c405503904947a2b697104ca797108d7f2a94a449cea42cd525e0e
+size 114251
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/0eb57eefa7cd45d30e68829ca8a03843_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/0eb57eefa7cd45d30e68829ca8a03843_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2f05d1c90933a5f351e2f22d30a2fce4fd100de2
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/0eb57eefa7cd45d30e68829ca8a03843_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:62e476b31919c870a138541597f5b055cbd34ebaced3d1013df1838bd60eab0a
+size 76586
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..30586157f094bde64775d7f6794f0f459ab3f7de
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/21ad58fee90f2be50708ff541d225507_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:40d59883575b465baeeedfb2d1bf02c754324edbf996196cbbc8fc9ec6e73e50
+size 62476
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5fd2bff0601f1ed3e338fe1fef044fda1e24e8ab
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7d88dd67e3f92d42517d3fcbea6facc2e85f5fd65defb8a4595716f67e25a033
+size 62461
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4774b3a190fdc9f65b8ae6259a55d3a725a7dd4a
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e646b535623af01c7c140e1a16eb3827d9384182b9f72383794dfee880e853f
+size 8208
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/41aef1f5efab13d4f38f69e86c726062_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/41aef1f5efab13d4f38f69e86c726062_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2840142b419fa68e700a5d6a9148860e43f3195b
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/41aef1f5efab13d4f38f69e86c726062_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1e0d52d85fe400eb01e0bde72d4ce3b260a9692fbf24e6e11068471e940fa2a8
+size 56172
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b391e3265fa7fe5e26ce4d2e623f5370d132ebd0
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0e752388efe2382a80228efec45668c22e87fa1427c2aa95a76bd74ca2e89857
+size 64073
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2e7a88cabb00f7eb8ce497746528655c2a1930dc
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c005dfa3fb3c745aefc3d991fe8b7611b8561b49ad975628da59e83a0c4e3199
+size 19437
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/50fecd0e7c9bf4ebf321d8367d42cc94_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/50fecd0e7c9bf4ebf321d8367d42cc94_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b6b59ed527b0d66cb1b22822bfabaedc41624e12
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/50fecd0e7c9bf4ebf321d8367d42cc94_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:90e6ddd5214ee08ae2db7691355df07b9202500239e24638ffafc833960b2fb2
+size 36193
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d70cb5d8e9220867f4409b70dad50d2d442b2a28
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:11cdec06b7f45b37dab1d46059118c0dd7562f50ef74ebdefb0f5a34d6f43718
+size 55071
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1d17b4d6a9016d083c4e761beff47ca5b564732a
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/5eb69662cc4fa7d0d49b4eb22951c204_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e7d4452b78ef7658f4fccc604fe46768094c803242f47407b2ed97cd2a44247
+size 115301
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b2531ffac5e17b4a93d79ab999f5e93cb3ca0096
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae16b748380b42ff1ecb3d3bde731d653de20eeebd7976a5bbb2e75232c9dfb4
+size 106860
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/6350c3c1007ce4254a7d803c527ee254_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/6350c3c1007ce4254a7d803c527ee254_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..89fc6ef340f1cc761709c170d78ea6d07257ed59
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/6350c3c1007ce4254a7d803c527ee254_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0a7144697741b412397b63763e0d3c69570e3dbbff275e1401ef97346689b695
+size 29558
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..719152dea08585697252b4f58ef043cb02109e14
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e522f90c03297a44cc33074d5b2ed0e696f371a51c334d97c5d2a9b9ef1641f0
+size 83941
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5758efb1e5c0da7acfb0524ae0a25e70b78e1c8f
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:168ab67ff147ba9539add6c4a7484af8f6a991e37af45b5cf83abf038464e635
+size 96283
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/7bed2d7c96d86bf922295a1252da52a5_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/7bed2d7c96d86bf922295a1252da52a5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f467b18be9c2767e20de4e9d548aba8f27ccb35c
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/7bed2d7c96d86bf922295a1252da52a5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a789d374bd7bc263e7c640e9ee0acaeda703ec164b6ef63c8de952a5ddd5e13b
+size 56315
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/7f7211748473542096717109ebe5a9d6_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/7f7211748473542096717109ebe5a9d6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..770d2fb2f5cfae60fdf9fcb5d5a839034feb4a5e
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/7f7211748473542096717109ebe5a9d6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:436bfa1470e23b123097ef0c87a35275efb0f6db3d80ddadd98fda583139157e
+size 46484
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/81a0abf9a79b27cf9d765553216b173c_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/81a0abf9a79b27cf9d765553216b173c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..63816c1ad6af2c4809ebc60058ec1d8d08f89a1d
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/81a0abf9a79b27cf9d765553216b173c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5a58caaaa49ab29e490a4265deaefc0fdbc3a5d64eab9fcb9ff0ba37958a7299
+size 83886
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..17cf9278dfdbbfa8491a8929291641b893599e93
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f3d3563a5fcd0827f0297b4bb7a27314d160ffb121111bcdce20cc6ad82d555d
+size 21401
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8bbf367a57f75b20c49838d9f11ca67743fef70a
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6bd88d11cacac486c7844ac03e53e84b89e660ab12f3e010dbfefe17ad33f05d
+size 72949
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b710d83031e96ba9d94a07cb3236fa0920248514
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:29abc12e18f6c1fe715dafbb4fce7cd7e75a8a40e8fddc89925b56ac2b9e5a4d
+size 83797
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/8c3eb53c927f55acd19723cfcd0c43b6_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/8c3eb53c927f55acd19723cfcd0c43b6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..439ae726e6201041481f75e724f72a1f654c05f4
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/8c3eb53c927f55acd19723cfcd0c43b6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1302fd7e4d434100add08d6695bc115ea75c892a8503a20e1c342dd1c5f61d7d
+size 14329
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/a1545557e366b6302109d13360b199c3_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/a1545557e366b6302109d13360b199c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e2d5bfacabe24ed5959b432f595a204dcb1148d9
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/a1545557e366b6302109d13360b199c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2765ec0e7ab6026cf529f001cf15b2315d1f4086871914818ed557c0f54655d6
+size 15335
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e0bebb665c7c1b78bf79ef63302ca31630c8b15a
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c497e6d3ad73b5158c212c643777c297ebe7c84bbaa280bd0ac52fbd0ee10ccc
+size 96837
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c2a58df150fe079ee40a124ff4756baae5f79441
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:80db07b1b59e0aedf23d32b27b960a62280bda44a568bddd4cabc9e64ee2a031
+size 57781
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/b20942bb14022381a243971ab9790dd9_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/b20942bb14022381a243971ab9790dd9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1c8001def4e8443283c36ab236aea05930d688e4
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/b20942bb14022381a243971ab9790dd9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ef42ad518b55641626c7d97cc9d26c3550adc47b61461a6692f4506793ecbb60
+size 42483
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/b2cc37ae1974ec7b87b91f54963b855d_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/b2cc37ae1974ec7b87b91f54963b855d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7a4d8b1cf54457dd06ce979fb24046abb3c10a9e
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/b2cc37ae1974ec7b87b91f54963b855d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b16eaaed7e1db84b67c4f6aea53ddcc0891cab156af5f2a062f0e9234b27f142
+size 124208
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/b2d16e07bfa79d67a8adabf7e26c7764_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/b2d16e07bfa79d67a8adabf7e26c7764_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aa86f39e54a6283df5f07962f8ac83b5efdf18ee
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/b2d16e07bfa79d67a8adabf7e26c7764_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8d6c52d5aec895430ba97cc3f6f0ecc31ec0dbdc63f72e2523313d33bb968c1d
+size 65190
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/b774dfc5023e15e9c352b97ca25a56d4_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/b774dfc5023e15e9c352b97ca25a56d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e3508d37336d0c7acd61c79aadd1975801be4f48
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/b774dfc5023e15e9c352b97ca25a56d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ad8ea47088f5e54b3a1d347924e6549a573e6b6e15fecb4adac824c0bdafd927
+size 60890
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/bb4d2112ed07e2031c92fbff3494af9f_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/bb4d2112ed07e2031c92fbff3494af9f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..675d7c6804a1506df47dcfc3b2d552518f095c98
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/bb4d2112ed07e2031c92fbff3494af9f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f19fdaae25af1ba5f02d31bd2d26f9f7a0163374b41f97b96d9246b6dc9fe4f0
+size 171275
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2f1c4e49c6c4211a28c206a879d5620c4ef30822
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c4a13d6250535fbb360e4e5dea471a790d7b33ab00adb943d0901214889a3a87
+size 112119
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..67c23506f7bcba9d790cd5b566998cf71305f039
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d6217570bc6d54e1059c679d1e12ba7fd19ca193c5f9eba3b4e2b9d7961f28d
+size 40358
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/c2f36c545b190860d04e1d84e58d22cc_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/c2f36c545b190860d04e1d84e58d22cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0763beb394d063fddbe328151e8f33c86323445b
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/c2f36c545b190860d04e1d84e58d22cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bb69bfcb89df184933c56077669fdd36babb88aac04b4586a870f6610975595d
+size 93525
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/c2f5e14ca0ed0f7944c7606451f67d85_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/c2f5e14ca0ed0f7944c7606451f67d85_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f46a8859f8e715bbca834e8b5a38be70ec4075a9
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/c2f5e14ca0ed0f7944c7606451f67d85_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a595fa36e657c5c05fa6fb248124cb63c13ffca04ece2962eb66eee55d441414
+size 48454
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..eaac05b35564d2d9153df443f9ca648f45ac6eb3
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7411d7f531da33ec470ff5c4c94d015d5461ce1d38fffbaf2a83e7390f0bacfb
+size 14995
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..da96d0e62dbd6a044df3ad81c0bbca84432fce44
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:568dfe73f025578a71d147c14254632854fcdd4aa123a9a206ad27ca455fe944
+size 48902
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b1ced87147e520e0a64fafd3cacf68bd100fb138
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3e1b12737f044144c802fb59d6f07bad434bc9c0f6990db91e8cbc3230eadaf0
+size 122878
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cbd68e98f34769ac9250a7f1dc39e94b96096bb0
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bd4a441b729e5c9fa7a7eac95871d5e9bfac0221a58d84f7f81fa3daffb7afcd
+size 13372
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/d5661c3661190c44429a1a75f61d7550_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/d5661c3661190c44429a1a75f61d7550_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d569f5dd9d72398df189869bd4fa1a3182c58fb0
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/d5661c3661190c44429a1a75f61d7550_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1379b6fc0857eb83f2a9234c508bdc16dc7fae0087a2edd11a8e19763a38cd9
+size 76387
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..82487a61179f0456b40d807970e97bbb0a5112e0
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3bf3eeb8b10f8b9f00fcd5d9dd2fae5ec64880b87689ed4768aeddb709bd01a5
+size 116744
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/ec3647789b5c38fb686f2a0833324e79_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/ec3647789b5c38fb686f2a0833324e79_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ff9152879eda5e25df94a11919eadf2533246382
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/ec3647789b5c38fb686f2a0833324e79_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0ac6c83944ec6010276c750294515d423fe3b74e449e4fc2b0f6dd569be07eb2
+size 80361
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..17db4cea291aacb8572afacce83dd6a648546bd8
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f0b3f9c9beac6105dcb8184a35c1252dacc4b6c4de4863a15e927d827a7426c1
+size 19919
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b352f96597bc49ce98c54d9ebe9b6d951536c5f3
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9637a975462ee347878ca6dcdb1afd8841bfb61d8de31f3be9f4b049211d065e
+size 38633
diff --git a/marked/Q/T-REC-Q.4002.1-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.4002.1-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a308271fb239928318c461337c31936dd84fe604
--- /dev/null
+++ b/marked/Q/T-REC-Q.4002.1-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f6a0f146a2a7abe73d858cf87904646fa5525273febbbbb82a1db78580ee044a
+size 3757
diff --git a/marked/Q/T-REC-Q.4002.1-201602-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4002.1-201602-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..71e697b86189255fc1452f35c52f22c67c13ed2a
--- /dev/null
+++ b/marked/Q/T-REC-Q.4002.1-201602-I_PDF-E/raw.md
@@ -0,0 +1,407 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.4002.1**
+
+(02/2016)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Testing specifications – Testing specifications for SIP-IMS
+
+---
+
+**Originating identification presentation and
+originating identification restriction using IP
+multimedia core network subsystem;
+Conformance testing – Part 1: Network side and
+user side; Protocol implementation
+conformance statement**
+
+Recommendation ITU-T Q.4002.1
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+| Testing specifications for next generation networks | Q.3900–Q.3999 |
+| Testing specifications for SIP-IMS | Q.4000–Q.4039 |
+| Testing specifications for Cloud computing | Q.4040–Q.4059 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## Recommendation ITU-T Q.4002.1
+
+# Originating identification presentation and originating identification restriction using IP multimedia core network subsystem; Conformance testing – Part 1: Network side and user side; Protocol implementation conformance statement
+
+## Summary
+
+Recommendation ITU-T Q.4002.1 v.1 (2016) is part 1 of the testing specifications for originating identification presentation/originating identification restriction (OIP/OIR) services implemented on IP multimedia subsystem (IMS) basis on the network and user side. This Recommendation specifies the protocol implementation conformance statement (PICS) that can be used for testing against Recommendation ITU-T Q.3618 v.1, "*Originating identification presentation and originating identification restriction using IP multimedia core network subsystem – Protocol specification*".
+
+The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.4002.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.3943.1 | 2013-04-29 | 11 | 11.1002/1000/11925 |
+| 2.0 | ITU-T Q.4002.1 v.1 | 2016-02-13 | 11 | 11.1002/1000/12744 |
+
+## Keywords
+
+IP multimedia subsystem, IMS, network side, originating identification presentation, OIP, originating identification restriction, OIR, protocol implementation conformance statement, PICS, session description protocol, SDP, session initiation protocol, SIP, testing, user side.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|--------------------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 4 Abbreviations and acronyms ..... | 2 |
+| 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 ITU-T Q.3618 v.1 ..... | 5 |
+| 5.4 Global statement of conformance..... | 5 |
+| 5.5 Roles ..... | 5 |
+| 5.6 User role ..... | 5 |
+| 5.7 Network role..... | 6 |
+
+
+
+## Recommendation ITU-T Q.4002.1
+
+## Originating identification presentation and originating identification restriction using IP multimedia core network subsystem; Conformance testing – Part 1: Network side and user side; Protocol implementation conformance statement
+
+# 1 Scope
+
+The following ITU-T Recommendation provides the implementation conformance statement (ICS) proforma for the originating identification presentation (OIP) supplementary service and the originating identification restriction (OIR) supplementary services, based on stage one and two of the ISDN and CLIR supplementary service defined in [ITU-T Q.3618 v.1] in compliance with the relevant requirements, and in accordance with the relevant guidance given in [ITU-T X.296].
+
+# 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.3618 v.1] Recommendation ITU-T Q.3618 v.1 (2016), *Originating identification presentation and originating identification restriction 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
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 Implementation Conformance Statement (ICS)** [ITU-T X.290]: 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.1.2 ICS proforma** [ITU-T X.290]: A document, in the form of a questionnaire, which when completed for an implementation or system becomes an ICS.
+
+**3.1.3 Protocol ICS (PICS)** [ITU-T X.290]: 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:
+
+| | |
+|------|-----------------------------------------------|
+| CLIR | Calling Line Identification Presentation |
+| ICS | Implementation Conformance Statement |
+| IUT | Implementation Under Test |
+| OIP | Originating Identification Presentation |
+| OIR | Originating Identification Restriction |
+| PICS | Protocol Implementation Conformance Statement |
+| SUT | System Under Test |
+
+# 5 Conformance to this PICS proforma specification
+
+If it claims to conform to this Recommendation, the actual PICS proforma to be filled in by a supplier shall be technically equivalent to the text of the PICS proforma given in clause 5, and shall preserve the numbering/naming and ordering of the proforma items.
+
+A protocol implementation conformance statement (PICS) that 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.3618 v.1] may provide information about the implementation in a standardized manner.
+
+The PICS proforma is subdivided into clauses for the following categories of information:
+
+- guidance for completing the PICS proforma;
+- identification of the implementation;
+- identification of the ;
+- global statement of conformance;
+- *roles*;
+- *user role*;
+ - *major capabilities*;
+- *network role*;
+ - *major capabilities*.
+
+### 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 each respective item (e.g., parameters, timers, etc.). It implicitly means "is - supported by the implementation?".
+
+##### **Status column**
+
+The following notations, defined in [ITU-T X.296], are used for the status column:
+
+- m mandatory – the capability is required to be supported.
+- o optional – the capability may be supported or not.
+- n/a not applicable – in the given context, it is impossible to use the capability.
+
+##### **Reference column**
+
+The reference column makes reference to [ITU-T Q.3618 v.1] (3GPP Release 10), except where explicitly stated otherwise.
+
+##### **Support column**
+
+The support column shall be filled in by the supplier of the implementation. The following common notations, defined in [ITU-T X.296], are used for the support column:
+
+- Y or y supported by the implementation.
+- N or n not supported by the implementation.
+- N/A, n/a or – no answer required (allowed only if the status is n/a, directly or after evaluation of a conditional status).
+
+##### **Prerequisite line**
+
+A prerequisite line takes the form: Prerequisite: .
+
+A prerequisite line after a clause or table title indicates that the whole clause or the whole table is not required to be completed if the predicate is FALSE.
+
+### **5.1.3 Instructions for completing the PICS proforma**
+
+The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. In particular, an explicit answer shall be entered, in each of the support column boxes provided, using the notation described in clause 5.1.2.
+
+However, the tables containing in "user role" clause shall only be completed for user implementations, and the tables containing in "network role" clause shall only be completed for network implementations.
+
+If necessary, the supplier may provide additional comments in the space at the bottom of the tables or separately.
+
+More detailed instructions are given at the beginning of the different clauses of the PICS proforma.
+
+## **5.2 Identification of the implementation**
+
+Identification of the implementation under test (IUT) and the system in which it resides (the system under test (SUT)) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options.
+
+The product supplier information and client information should both be filled in if they are different.
+
+A person who can answer queries regarding information supplied in the ICS should be named as the contact person.
+
+#### **5.2.1 Date of the statement**
+
+| | |
+|-------------------------------|--|
+| 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: | |
+| Address: | |
+| Telephone number: | |
+| Facsimile number: | |
+| E-mail address | |
+| Additional information: | |
+
+## 5.3 Identification of ITU-T Q.3618 v.1
+
+This PICS proforma applies to the following standard:
+
+[ITU-T Q.3618 v.1] "Originating identification presentation and originating identification restriction using IP multimedia core network subsystem – Protocol specification"
+
+## 5.4 Global statement of conformance
+
+| | |
+|---------------------------------------------|----------|
+| | (Yes/No) |
+| Are all mandatory capabilities implemented? | |
+
+NOTE – Answering "No" to this question indicates non-conformance to the specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conforming, on pages attached to the PICS proforma.
+
+### 5.5 Roles
+
+**Table 5-1 – Roles**
+
+| Item | Item description | Reference | Status | Support |
+|------|------------------|-------------------------------------------------|--------|---------|
+| 1 | User | Clauses 4.5.2.1, 4.5.2.12 of [ITU-T Q.3618 v.1] | o.1 | |
+| 2 | Network | Clauses 4.5.2.4, 4.5.2.9 of [ITU-T Q.3618 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.1/1 -- user role
+
+### 5.6.1 Major capabilities
+
+**Table 5-2 – User related requirements and options**
+
+| Item | Item description | Reference | Status | Support |
+|------|--------------------------------------------------------------------------------|---------------------------------------|--------|---------|
+| 1 | Is the implementation an originating user equipment? | Clause 4.5.2.1 of [ITU-T Q.3618 v.1] | o | |
+| 2 | Does the originating user equipment inserts P-Preferred-Identity header field? | Clause 4.5.2.1 of [ITU-T Q.3618 v.1] | o | |
+| 3 | Is the terminating user a terminating user equipment? | Clause 4.5.2.12 of [ITU-T Q.3618 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.1/2 -- network role
+
+### 5.7.1 Major capabilities
+
+**Table 5-3 – Network related requirements and options**
+
+| Item | Item description | Reference | Status | Support |
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|--------|---------|
+| 1 | Does the Application Server serving the originating user modify the From header field to remove the identification information or set the Privacy header value to "user" if the originating user identity is restricted? | Clause 4.5.2.4 of [ITU-T Q.3618 v.1] | o | |
+| 2 | Does the Application Server serving the originating user set the From header field to the default public user identities if the received From header field does not match with one of the registered public user identities? | Clause 4.5.2.4 of [ITU-T Q.3618 v.1] | o | |
+| 3 | Does the originating user subscribe the "no screening" special arrangement? | Clause 4.5.2.4 of [ITU-T Q.3618 v.1] | o | |
+| 4 | Does the SUT supports the OIR service in permanent mode? | Clause 4.5.2.4 of [ITU-T Q.3618 v.1] | o | |
+| 5 | Does the SUT supports the OIR service in temporary mode? | Clause 4.5.2.4 of [ITU-T Q.3618 v.1] | o | |
+| 6 | Does the Application Server serving the terminating user anonymize the contents of the From header by setting it to a default non-significant value if the terminating user does not subscribe the OIR service? | Clause 4.5.2.9 of [ITU-T Q.3618 v.1] | o | |
+| 7 | Does the network serving the terminating user support the override category? | Clause 4.5.2.9 of [ITU-T Q.3618 v.1] | o | |
+| 8 | Does the Application Server serving the terminating user remove the Privacy header value 'id' if it removes the P-Asserted-Identity or the terminating user has an override category? | Clause 4.5.2.9 of [ITU-T Q.3618 v.1] | o | |
+
+Comments:
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.4003.2-201602-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4003.2-201602-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..d11dd33df565143c5215d182d2e60d9868b9b093
--- /dev/null
+++ b/marked/Q/T-REC-Q.4003.2-201602-I_PDF-E/raw.md
@@ -0,0 +1,728 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.4003.2**
+
+(02/2016)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Testing specifications – Testing specifications for SIP-IMS
+
+---
+
+**Communication HOLD using IP multimedia core
+network subsystem; Conformance testing –
+Part 2: Network side; Test suite structure and
+test purposes**
+
+Recommendation ITU-T Q.4003.2
+
+ITU-T
+
+
+
+The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with red lightning bolts striking across it, and the text "International Telecommunication Union" to its right.
+
+ITU logo: A globe with red lightning bolts, next to the text 'International Telecommunication Union'.
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+| Testing specifications for next generation networks | Q.3900–Q.3999 |
+| Testing specifications for SIP-IMS | Q.4000–Q.4039 |
+| Testing specifications for Cloud computing | Q.4040–Q.4059 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## Recommendation ITU-T Q.4003.2
+
+# Communication HOLD using IP multimedia core network subsystem; Conformance testing – Part 2: Network side; Test suite structure and test purposes
+
+## Summary
+
+Recommendation ITU-T Q.4003.2 v.1 (2006) is part 2 of the testing specifications for HOLD service implemented on an IMS basis on the network side. The Recommendation specifies the test suite structure and test purposes (TSS&TP) which can be used for testing against the Recommendation ITU-T Q.3619 v.1, "Communication HOLD using IP multimedia core network subsystem – Protocol specification".
+
+The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.4003.2, and that it relates to Release 10 of the relevant 3GPP/ETSI standard.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|--------------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.4003.2 v.1 | 2016-02-13 | 11 | 11.1002/1000/12734 |
+
+## Keywords
+
+HOLD, IP multimedia subsystem, IMS, network side, protocol implementation conformance statement, PICS, session description protocol, SDP, session initiation protocol, SIP, testing, user side.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|----------------------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 4 Abbreviations and acronyms ..... | 2 |
+| 5 Test Suite Structure (TSS) and Test configuration..... | 2 |
+| 5.0 Introduction ..... | 2 |
+| 5.1 Configuration..... | 2 |
+| 6 Test Purposes (TP)..... | 3 |
+| 6.1 Introduction ..... | 3 |
+| 6.2 Network TPs for HOLD ..... | 3 |
+
+
+
+## Recommendation ITU-T Q.4003.2
+
+## Communication HOLD using IP multimedia core network subsystem; Conformance testing – Part 2: Network side; Test suite structure and test purposes
+
+# 1 Scope
+
+The present Recommendation provides the test suite structure (TSS) and test purposes (TP) for the test specifications for the communication HOLD on the network side using IP multimedia (IM) core network (CN) subsystem as specified in [ITU-T Q.3619 v.1] and [IETF RFC 3264] in compliance with the relevant requirements and in accordance with the relevant guidance given in [ITU-T X.296].
+
+This Recommendation can be used for compliance testing against Recommendation [ITU-T Q.3619 v.1] "Communication HOLD using IP multimedia core network subsystem—Protocol specification" on the network side.
+
+The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.4003.2, and that it relates to Release 10 of the relevant 3GPP/ETSI standard.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T Q.3619 v.1] Recommendation ITU-T Q.3619 v.1, *Communication HOLD using IP multimedia core network subsystem. Protocol specification.*
+- [ITU-T Q.4003.1 v.1] Recommendation ITU-T Q.4003.1 v.1, *Communication HOLD using IP multimedia core network subsystem; Conformance Testing – Part 1: Network side and user side; Protocol implementation conformance statement.*
+- [ITU-T X.290] Recommendation ITU-T X.290 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – General concepts.*
+- [ITU-T X.296] Recommendation ITU-T X.296 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – Implementation conformance statements.*
+- [IETF RFC 3264] IETF RFC 3264 (2002), *An Offer/Answer Model with the Session Description Protocol (SDP).*
+
+# 3 Definitions
+
+For the purposes of this Recommendation, the terms and definitions given in [ITU-T Q.3619 v.1] and the following apply:
+
+- 3.1 abstract test suite (ATS):** Refer to [ITU-T X.290].
+
+- 3.2 **implementation under test (IUT)**: Refer to [ITU-T X.290].
+- 3.3 **PICS proforma**: Refer to [ITU-T X.290].
+- 3.4 **point of control and observation**: Refer to [ITU-T X.290].
+- 3.5 **protocol implementation conformance statement (PICS)**: Refer to [ITU-T X.290].
+- 3.6 **system under test (SUT)**: Refer to [ITU-T X.290].
+- 3.7 **test purpose (TP)**: Refer to [ITU-T X.290].
+- 3.8 **Gm reference point**: Reference point between User Equipment and P-CSCF
+
+NOTE – This may contain additional information.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+- IMS IP Multimedia Subsystem
+- IP Internet Protocol
+- IUT Implementation Under Test
+- PICS Protocol Implementation Conformance Statement
+- SDP Session Description Protocol
+- SIP Session Initiation Protocol
+- SUT System Under Test
+- UE User Equipment
+
+# 5 Test suite structure (TSS) and test configuration
+
+## 5.0 Introduction
+
+The following test suite structure is used in this Recommendation.
+
+**Table 1 – Test suite structure**
+
+| | |
+|---------|------------|
+| Network | |
+| | CH_N01_xxx |
+
+## 5.1 Configuration
+
+The scope of this Recommendation is to test the signalling and procedural aspects of the stage 3 requirements as described in [ITU-T Q.3619 v.1]. The stage 3 description respects the requirements to several network entities and also to requirements regarding end devices. Therefore several interfaces (reference points) are addressed to satisfy the test of the different entities.
+
+Therefore to test the appropriate entities the configurations below is applicable:
+
+**Testing of the network:** This entity is responsible to perform the service. In case only the Gm interface is accessible this shall be used instead. In this case, be aware that the verification of several requirements is impeded, see Figure 5-1.
+
+
+
+```
+
+graph LR
+ TS1[Test system] ---|Mw, Mg, Mx| IUT[CSCF (and/or AS)
+Implementation under test]
+ IUT ---|Mw, Mg, Mx| TS2[Test system]
+
+```
+
+Diagram showing a central green box labeled 'CSCF (and/or AS) Implementation under test' connected to two cyan boxes labeled 'Test system'. The connections are labeled 'Mw, Mg, Mx'.
+
+Q.4003.2v1(16)\_F5-1
+
+**Figure 5-1 – Applicable interfaces to test using the (generic) NNI interface**
+
+# 6 Test purposes (TP)
+
+## 6.1 Introduction
+
+For each test requirement a TP is defined.
+
+### 6.1.1 TP naming convention
+
+Test purposes (TPs) are numbered, starting at 001, within each group. Groups are organized according to the test suite structure (TSS). Additional references are added to identify the actual test suite and whether it applies to the network or the user (see Table 2).
+
+**Table 2 – TP identifier naming convention scheme**
+
+| | | | | | | |
+|-------------------------------------|--------------------------|----------------------------------------------------------------------------------------------------|---|------|---|---------|
+| Identifier: __ | | | | | | |
+| | = supplementary service: | e.g. "CH" | | | | |
+| | = type of IUT: | | U | User | N | Network |
+| U | User | | | | | |
+| N | Network | | | | | |
+| | = group | 2 digit field representing group reference according to TSS | | | | |
+| | = sequential number | (001-999) | | | | |
+
+### 6.1.2 Test strategy
+
+As the base standard [ITU-T Q.3619 v.1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the protocol implementation conformance statement (PICS) specification Recommendation [ITU-T Q.4003.1 v.1].
+
+## 6.2 Network TPs for HOLD
+
+All PICS items referred to in this clause are as specified in [ITU-T Q.4003.1 v.1] unless indicated otherwise by another numbered reference.
+
+| | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|------------------------------------------------------------------|-------------------------------------------|----------------------------|------------|----------------------------|--|------------------------------------|--|---------------------------|---|-----------------------------|----------------------------|---|------------------------------|--|--------------------------------|--|
+| TSS
Network | TP
CH_N01_001 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression
PICS 5.3/1 | | | | | | | | | | | | | | | |
+| Test purpose:
Session hold in the early dialogue. The media streams were previously set to sendrecv.
Ensure that the SUT transfers the HOLD request in an early dialogue. The 200 OK response contains an SDP body with an attribute line indicating 'a=recvonly'. | | | | | | | | | | | | | | | | | | |
+| Precondition: - An early dialogue was established between the served user and a remote user according to the 'basic Call' procedures
- The media stream was previously set to 'sendrecv'
- The originating party sets the session on HOLD
| | | | | | | | | | | | | | | | | | |
+| Comments:
| Test Equipment (Gm) | SUT | Test Equipment (Gm) |
| Establish an early dialogue | |
| UPDATE(sendonly) | → | → UPDATE(sendonly) |
| 200 OK (recvonly) | ← | ← 200 OK (recvonly) |
| Apply post test routine | |
| | | | Test Equipment (Gm) | SUT | Test Equipment (Gm) | | Establish an early dialogue | | UPDATE( sendonly ) | → | → UPDATE( sendonly ) | 200 OK ( recvonly ) | ← | ← 200 OK ( recvonly ) | | Apply post test routine | |
+| Test Equipment (Gm) | SUT | Test Equipment (Gm) | | | | | | | | | | | | | | | | |
+| | Establish an early dialogue | | | | | | | | | | | | | | | | | |
+| UPDATE( sendonly ) | → | → UPDATE( sendonly ) | | | | | | | | | | | | | | | | |
+| 200 OK ( recvonly ) | ← | ← 200 OK ( recvonly ) | | | | | | | | | | | | | | | | |
+| | Apply post test routine | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|------------------------------------------------------------------|-------------------------------------------|----------------------------|------------|----------------------------|--|------------------------------------|--|---------------------------|---|-----------------------------|----------------------------|---|------------------------------|---------------------------|---|-----------------------------|----------------------------|---|------------------------------|--|--------------------------------|--|
+| TSS
Network | TP
CH_N01_002 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression
PICS 5.3/1 | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose:
Session retrieval in the early dialogue. The media streams were previously set to sendrecv.
Ensure that the SUT transfers the HOLD request in an early dialogue. The 200 OK response contains an SDP body with an attribute line indicating 'a=sendrecv'. | | | | | | | | | | | | | | | | | | | | | | | | |
+| Precondition: - An early dialogue was established between the served user and a remote user according to the 'basic Call' procedures
- The media stream was previously set to 'sendonly'
- The originating party retrieves the session
| | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test Equipment (Gm) | SUT | Test Equipment (Gm) |
| Establish an early dialogue | |
| UPDATE(sendonly) | → | → UPDATE(sendonly) |
| 200 OK (recvonly) | ← | ← 200 OK (recvonly) |
| UPDATE(sendrecv) | → | → UPDATE(sendrecv) |
| 200 OK (sendrecv) | ← | ← 200 OK (sendrecv) |
| Apply post test routine | |
| | | | Test Equipment (Gm) | SUT | Test Equipment (Gm) | | Establish an early dialogue | | UPDATE( sendonly ) | → | → UPDATE( sendonly ) | 200 OK ( recvonly ) | ← | ← 200 OK ( recvonly ) | UPDATE( sendrecv ) | → | → UPDATE( sendrecv ) | 200 OK ( sendrecv ) | ← | ← 200 OK ( sendrecv ) | | Apply post test routine | |
+| Test Equipment (Gm) | SUT | Test Equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | |
+| | Establish an early dialogue | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE( sendonly ) | → | → UPDATE( sendonly ) | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( recvonly ) | ← | ← 200 OK ( recvonly ) | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE( sendrecv ) | → | → UPDATE( sendrecv ) | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( sendrecv ) | ← | ← 200 OK ( sendrecv ) | | | | | | | | | | | | | | | | | | | | | | |
+| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|-----------------------------------------------------------------|-------------------------------------------|
+| TSS
Network | TP
CH_N01_003 | HOLD reference
Clause 4.5.2.1 of
ITU-T Q.3619 v.1] | Selection expression
PICS 5.3/1 |
+| Test purpose:
Session set on HOLD in the early dialogue. Retrieval in the confirmed dialogue.
Ensure that the SUT transfers the HOLD request in an early dialogue and the revival in the confirmed dialogue. The 200 OK response contains an SDP body with an attribute line indicating 'a=sendrecv'. | | | |
+| Precondition: | | | |
+| - An early dialogue was established between the served user and a remote user according to the 'basic Call' procedures
- The media stream was previously set to 'sendonly' in the early dialogue
- The terminating user confirms the dialogue.
- The originating party retrieves the session
| | | |
+| Comments: | | | |
+| Test Equipment (Gm) | SUT | | Test Equipment (Gm) |
+| | Establish an early dialogue | | |
+| UPDATE( sendonly ) | → | → | UPDATE( sendonly ) |
+| 200 OK ( recvonly ) | ← | ← | 200 OK ( recvonly ) |
+| 200 OK ( recvonly ) | ← | ← | 200 OK ( recvonly ) |
+| ACK | → | → | ACK |
+| CASE A | | | |
+| INVITE( sendrecv ) | → | | CASE a |
+| 200 OK ( sendrecv ) | ← | → | INVITE( sendrecv ) |
+| ACK | → | ← | 200 OK ( sendrecv ) |
+| | | → | ACK |
+| | | | CASE b |
+| | | → | UPDATE( sendrecv ) |
+| | | ← | 200 OK ( sendrecv ) |
+| CASE B | | | |
+| UPDATE( sendrecv ) | → | | CASE a |
+| 200 OK ( sendrecv ) | ← | → | UPDATE( sendrecv ) |
+| | | ← | 200 OK ( sendrecv ) |
+| | | | CASE b |
+| | | → | INVITE( sendrecv ) |
+| | | ← | 200 OK ( sendrecv ) |
+| | | → | ACK |
+| Apply post test routine | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------|----------------------------|------------|----------------------------|--|---------------------------------------|--|---------------|--|--|---------------------------|---|--|----------------------------|---|---|-----|---|---|--|--|---|--|--|---------------|--|--|---------------------------|--|--|----------------------------|--|--|-----|--|--|---------------|--|--|---------------------------|--|--|----------------------------|---------------|--|--|---------------------------|---|--|----------------------------|---|---|--|--|---|--|--|---------------|--|--|---------------------------|--|--|----------------------------|--|--|---------------|--|--|---------------------------|--|--|----------------------------|--|--|-----|--|--------------------------------|--|
+| TSS
Network | TP
CH_N01_004 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose:
Session hold in a confirmed dialogue. The media streams were previously set to sendrecv.
Ensure that the SUT transfers the HOLD request from the originating party in a confirmed dialogue. The 200 OK response containing an SDP body with an attribute line indicating 'a=recvonly'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Precondition: - • A confirmed dialogue was established between the served user and a remote user according to the 'basic Call' procedures
- • The media stream was previously set to 'sendrecv'
- • The originating party sets the session on HOLD
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test Equipment (Gm) | SUT | Test Equipment (Gm) |
| Establish a confirmed dialogue | |
| CASE A | | |
| INVITE(sendonly) | → | |
| 200 OK (recvonly) | ← | → |
| ACK | ← | ← |
| | → |
| | CASE a |
| | INVITE(sendonly) |
| | 200 OK (recvonly) |
| | ACK |
| | CASE b |
| | UPDATE(sendonly) |
| | 200 OK (recvonly) |
| CASE B | | |
| UPDATE(sendonly) | → | |
| 200 OK (recvonly) | ← | → |
| | ← |
| | CASE a |
| | UPDATE(sendonly) |
| | 200 OK (recvonly) |
| | CASE b |
| | INVITE(sendonly) |
| | 200 OK (recvonly) |
| | ACK |
| Apply post test routine | |
| | | | Test Equipment (Gm) | SUT | Test Equipment (Gm) | | Establish a confirmed dialogue | | CASE A | | | INVITE( sendonly ) | → | | 200 OK ( recvonly ) | ← | → | ACK | ← | ← | | | → | | | CASE a | | | INVITE( sendonly ) | | | 200 OK ( recvonly ) | | | ACK | | | CASE b | | | UPDATE( sendonly ) | | | 200 OK ( recvonly ) | CASE B | | | UPDATE( sendonly ) | → | | 200 OK ( recvonly ) | ← | → | | | ← | | | CASE a | | | UPDATE( sendonly ) | | | 200 OK ( recvonly ) | | | CASE b | | | INVITE( sendonly ) | | | 200 OK ( recvonly ) | | | ACK | | Apply post test routine | |
+| Test Equipment (Gm) | SUT | Test Equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Establish a confirmed dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE( sendonly ) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( recvonly ) | ← | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | CASE a | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | INVITE( sendonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | 200 OK ( recvonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | UPDATE( sendonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | 200 OK ( recvonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE( sendonly ) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( recvonly ) | ← | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | CASE a | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | UPDATE( sendonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | 200 OK ( recvonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | INVITE( sendonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | 200 OK ( recvonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------|----------------------------|------------|----------------------------|--|---------------------------------------|--|---------------|--|--|---------------|--|-----------------------------|---------------------------|---|------------------------------|----------------------------|---|-------|-----|---|--|-------------------|--|--|---------------------------|---|--|----------------------------|---|--|-------------------|--|--|---------------|--|-----------------------------|---------------------------|---|------------------------------|----------------------------|---|--|-------------------|--|--|---------------------------|---|--|----------------------------|---|--|-----|---|--|--|--------------------------------|--|
+| TSS
Network | TP
CH_N01_005 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose:
Session hold in a confirmed dialogue. The media streams were previously set to sendrecv.
Ensure that the SUT transfers the HOLD request from the terminating party in aconfirmed dialogue. The 200 OK response containing an SDP body with an attribute line indicating 'a=recvonly'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Precondition: - • A confirmed dialogue was established between the served user and a remote user according to the 'basic Call' procedures
- • The media stream was previously set to 'sendrecv'
- • The terminating party sets the session on HOLD
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments: | Test Equipment (Gm) | SUT | Test Equipment (Gm) |
| Establish a confirmed dialogue | |
| CASE A | | |
| CASE a | | ← INVITE(sendonly) |
| INVITE(sendonly) | ← | → 200 OK (recvonly) |
| 200 OK (recvonly) | → | ← ACK |
| ACK | ← | |
CASE b | | |
| UPDATE(sendonly) | ← | |
| 200 OK (recvonly) | → | |
CASE B | | |
| CASE a | | ← UPDATE(sendonly) |
| UPDATE(sendonly) | ← | → 200 OK (recvonly) |
| 200 OK (recvonly) | → | |
CASE b | | |
| INVITE(sendonly) | ← | |
| 200 OK (recvonly) | → | |
| ACK | ← | |
| Apply post test routine | |
| | | | Test Equipment (Gm) | SUT | Test Equipment (Gm) | | Establish a confirmed dialogue | | CASE A | | | CASE a | | ← INVITE( sendonly ) | INVITE( sendonly ) | ← | → 200 OK ( recvonly ) | 200 OK ( recvonly ) | → | ← ACK | ACK | ← | |
CASE b | | | UPDATE( sendonly ) | ← | | 200 OK ( recvonly ) | → | |
CASE B | | | CASE a | | ← UPDATE( sendonly ) | UPDATE( sendonly ) | ← | → 200 OK ( recvonly ) | 200 OK ( recvonly ) | → | |
CASE b | | | INVITE( sendonly ) | ← | | 200 OK ( recvonly ) | → | | ACK | ← | | | Apply post test routine | |
+| Test Equipment (Gm) | SUT | Test Equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Establish a confirmed dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE a | | ← INVITE( sendonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE( sendonly ) | ← | → 200 OK ( recvonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( recvonly ) | → | ← ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE( sendonly ) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( recvonly ) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE a | | ← UPDATE( sendonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE( sendonly ) | ← | → 200 OK ( recvonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( recvonly ) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE( sendonly ) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( recvonly ) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Network | TP
CH_N01_006 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|------------------------------------------------------------------|-----------------------------|---------------------|-----|---------------------|--|------------------------------------------------------------------------------------|--|---------------|--|--|---------------------------|---|---------------|-------------------|---|--------------------|-----|---|------------------------------|--|---|-----|--|--|--|--|--|---------------|--|---|------------------|--|---|----------------------------|--|--|--|---------------|--|--|---------------------------|---|---------------|-------------------|---|--------------------|--|---|------------------------------|--|--|--|--|--|---------------|--|---|------------------|--|---|----------------------------|--|---|-----|--|--------------------------------|--|
+| Test purpose:
Retrieve the session in a confirmed dialogue. The media streams were previously set to sendonly.
Ensure that the SUT is able to support the retrieval of a hold session. The session was previously set on HOLD by the originating party. The originating party sends an INVITE or UPDATE request. The 'a' attribute in the SDP is set to 'sendrecv' or this attribute is absent. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Precondition: - • A confirmed dialogue was established between the served user and a remote user according to the 'basic Call' procedures
- • The media stream was previously set to 'sendonly' HOLD requested by the originating party
- • The originating party retrieves the held session
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test Equipment (Gm) | SUT | Test Equipment (Gm) |
| Establish a confirmed dialogue
Session on HOLD by the originating party | |
| CASE A | | |
| INVITE(sendrecv) | → | CASE a |
| 200 OK (sendrecv) | ← | → INVITE(sendrecv) |
| ACK | ← | ← 200 OK (sendrecv) |
| → | ACK |
| | |
| | CASE b |
| → | UPDATE(sendrecv) |
| ← | 200 OK (sendrecv) |
| | |
| CASE B | | |
| UPDATE(sendrecv) | → | CASE a |
| 200 OK (sendrecv) | ← | → UPDATE(sendrecv) |
| ← | ← 200 OK (sendrecv) |
| | |
| | CASE b |
| → | INVITE(sendrecv) |
| ← | 200 OK (sendrecv) |
| → | ACK |
| Apply post test routine | |
| | | | Test Equipment (Gm) | SUT | Test Equipment (Gm) | | Establish a confirmed dialogue
Session on HOLD by the originating party | | CASE A | | | INVITE( sendrecv ) | → | CASE a | 200 OK (sendrecv) | ← | → INVITE(sendrecv) | ACK | ← | ← 200 OK ( sendrecv ) | | → | ACK | | | | | | CASE b | | → | UPDATE(sendrecv) | | ← | 200 OK ( sendrecv ) | | | | CASE B | | | UPDATE( sendrecv ) | → | CASE a | 200 OK (sendrecv) | ← | → UPDATE(sendrecv) | | ← | ← 200 OK ( sendrecv ) | | | | | | CASE b | | → | INVITE(sendrecv) | | ← | 200 OK ( sendrecv ) | | → | ACK | | Apply post test routine | |
+| Test Equipment (Gm) | SUT | Test Equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Establish a confirmed dialogue
Session on HOLD by the originating party | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE( sendrecv ) | → | CASE a | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (sendrecv) | ← | → INVITE(sendrecv) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | ← 200 OK ( sendrecv ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | UPDATE(sendrecv) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 200 OK ( sendrecv ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE( sendrecv ) | → | CASE a | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (sendrecv) | ← | → UPDATE(sendrecv) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | ← 200 OK ( sendrecv ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | INVITE(sendrecv) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 200 OK ( sendrecv ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|------------------------------------------------------------------|-----------------------------|----------------------------|------------|----------------------------|------------------------------------------------------------------------------------------|--|--|---------------|--|--|---------------|--|--------------------|------------------|---|---------------------|-------------------|---|-------|-----|---|--|---------------|--|--|------------------|---|--|-------------------|---|--|---------------|--|--|---------------|--|--------------------|------------------|---|---------------------|-------------------|---|--|---------------|--|--|------------------|---|--|-------------------|---|--|-----|---|--|--|--------------------------------|--|
+| TSS
Network | TP
CH_N01_007 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose:
Retrieve the session in a confirmed dialogue. The media streams were previously set to sendonly.
Ensure that the SUT is able support the retrieval of a hold session. The session was previous set on HOLD by the terminating party. The terminating party sends an INVITE or UPDATE request. The 'a' attribute in the SDP is set to 'sendrecv' or this attribute is absent. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Precondition: - • A confirmed dialogue was established between the served user and a remote user according to the 'basic Call' procedures
- • The media stream was previously set to 'sendonly' HOLD requested by the terminating party
- • The terminating party retrieves the held session
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test Equipment (Gm) | SUT | Test Equipment (Gm) |
Establish a confirmed dialogue
Session on HOLD by the terminating party |
| CASE A | | |
| CASE a | | ← INVITE(sendrecv) |
| INVITE(sendrecv) | ← | → 200 OK (sendrecv) |
| 200 OK (sendrecv) | → | ← ACK |
| ACK | ← | |
| CASE b | | |
| UPDATE(sendrecv) | ← | |
| 200 OK (sendrecv) | → | |
| CASE B | | |
| CASE a | | ← UPDATE(sendrecv) |
| UPDATE(sendrecv) | ← | → 200 OK (sendrecv) |
| 200 OK (sendrecv) | → | |
| CASE b | | |
| INVITE(sendrecv) | ← | |
| 200 OK (sendrecv) | → | |
| ACK | ← | |
| Apply post test routine | |
| | | | Test Equipment (Gm) | SUT | Test Equipment (Gm) | Establish a confirmed dialogue
Session on HOLD by the terminating party | | | CASE A | | | CASE a | | ← INVITE(sendrecv) | INVITE(sendrecv) | ← | → 200 OK (sendrecv) | 200 OK (sendrecv) | → | ← ACK | ACK | ← | | CASE b | | | UPDATE(sendrecv) | ← | | 200 OK (sendrecv) | → | | CASE B | | | CASE a | | ← UPDATE(sendrecv) | UPDATE(sendrecv) | ← | → 200 OK (sendrecv) | 200 OK (sendrecv) | → | | CASE b | | | INVITE(sendrecv) | ← | | 200 OK (sendrecv) | → | | ACK | ← | | | Apply post test routine | |
+| Test Equipment (Gm) | SUT | Test Equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Establish a confirmed dialogue
Session on HOLD by the terminating party | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE a | | ← INVITE(sendrecv) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE(sendrecv) | ← | → 200 OK (sendrecv) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (sendrecv) | → | ← ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE(sendrecv) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (sendrecv) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE a | | ← UPDATE(sendrecv) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE(sendrecv) | ← | → 200 OK (sendrecv) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (sendrecv) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE(sendrecv) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (sendrecv) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Network | TP
CH_N01_008 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|------------------------------------------------------------------|-----------------------------|----------------------------|------------|----------------------------|--|---------------------------------------|--|--|-------------------------------------------------|--|---------------|--|--|------------------|---|---------------|-------------------|---|---|------------------|-----|---|---|----------------------------|--|--|---|-----|--|--|--|--|--|--|--|---------------|--|--|---|------------------|--|--|---|----------------------------|--|--|--|--|---------------|--|--|--|------------------|---|--|---------------|-------------------|---|---|------------------|--|--|---|----------------------------|--|--|--|--|--|--|--|---------------|--|--|---|------------------|--|--|---|----------------------------|--|--|---|-----|--|--------------------------------|--|--|
+| Test purpose:
Session hold in a confirmed dialogue. The media streams were previously set to recvonly.
Ensure that the SUT transfers the hold request from the originating party in a confirmed dialogue. The 200 OK response containing an SDP body with an attribute line indicating 'a= inactive'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Precondition: - An confirmed dialogue was established between the served user and a remote user according to the 'basic Call' procedures
- The media stream was previously set to 'recvonly' HOLD requested by the terminating party
- The originating party sets the session on HOLD
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test Equipment (Gm) | SUT | Test Equipment (Gm) |
| Establish a confirmed dialogue | |
| Session on HOLD by the terminating party | |
| CASE A | | |
| INVITE(inactive) | → | CASE a |
| 200 OK (inactive) | ← | → | INVITE(inactive) |
| ACK | ← | ← | 200 OK (inactive) |
| | → | ACK |
| | | |
| | | CASE b |
| | → | UPDATE(inactive) |
| | ← | 200 OK (inactive) |
| | | |
| CASE B | | | |
| UPDATE(inactive) | → | | CASE a |
| 200 OK (inactive) | ← | → | UPDATE(inactive) |
| | ← | 200 OK (inactive) |
| | | |
| | | CASE b |
| | → | INVITE(inactive) |
| | ← | 200 OK (inactive) |
| | → | ACK |
| Apply post test routine | | |
| | | | Test Equipment (Gm) | SUT | Test Equipment (Gm) | | Establish a confirmed dialogue | | | Session on HOLD by the terminating party | | CASE A | | | INVITE(inactive) | → | CASE a | 200 OK (inactive) | ← | → | INVITE(inactive) | ACK | ← | ← | 200 OK ( inactive ) | | | → | ACK | | | | | | | | CASE b | | | → | UPDATE(inactive) | | | ← | 200 OK ( inactive ) | | | | | CASE B | | | | UPDATE(inactive) | → | | CASE a | 200 OK (inactive) | ← | → | UPDATE(inactive) | | | ← | 200 OK ( inactive ) | | | | | | | | CASE b | | | → | INVITE(inactive) | | | ← | 200 OK ( inactive ) | | | → | ACK | | Apply post test routine | | |
+| Test Equipment (Gm) | SUT | Test Equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Establish a confirmed dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Session on HOLD by the terminating party | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE(inactive) | → | CASE a | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (inactive) | ← | → | INVITE(inactive) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | ← | 200 OK ( inactive ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → | UPDATE(inactive) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← | 200 OK ( inactive ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE(inactive) | → | | CASE a | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (inactive) | ← | → | UPDATE(inactive) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← | 200 OK ( inactive ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → | INVITE(inactive) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← | 200 OK ( inactive ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|------------------------------------------------------------------|-----------------------------|----------------------------|------------|----------------------------|------------------------------------------------------------------------------------------|--|--|---------------|--|--|---------------|--|--------------------|------------------|---|---------------------|----------------------------|---|-------|-----|---|--|-------------------|--|--|------------------|---|--|----------------------------|---|--|-------------------|--|--|---------------|--|--------------------|------------------|---|---------------------|----------------------------|---|--|-------------------|--|--|------------------|---|--|----------------------------|---|--|-----|---|--|--|--------------------------------|--|
+| TSS
Network | TP
CH_N01_009 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose:
Session hold in a confirmed dialogue. The media streams were previously set to recvonly.
The session in a confirmed dialogue is set on HOLD Ensure that the SUT transfers the HOLD request from the terminating party. The 200 OK response containing an SDP body with an attribute line indicating 'a=inactive'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Precondition: - • A confirmed dialogue was established between the served user and a remote user according to the 'basic Call' procedures
- • The media stream was previously set to 'recvonly' HOLD requested by the originating party
- • The terminating party sets the session on HOLD
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test Equipment (Gm) | SUT | Test Equipment (Gm) |
Establish a confirmed dialogue
Session on HOLD by the originating party |
| CASE A | | |
| CASE a | | ← INVITE(inactive) |
| INVITE(inactive) | ← | → 200 OK (inactive) |
| 200 OK (inactive) | → | ← ACK |
| ACK | ← | |
CASE b | | |
| UPDATE(inactive) | ← | |
| 200 OK (inactive) | → | |
CASE B | | |
| CASE a | | ← UPDATE(inactive) |
| UPDATE(inactive) | ← | → 200 OK (inactive) |
| 200 OK (inactive) | → | |
CASE b | | |
| INVITE(inactive) | ← | |
| 200 OK (inactive) | → | |
| ACK | ← | |
| Apply post test routine |
| | | | Test Equipment (Gm) | SUT | Test Equipment (Gm) | Establish a confirmed dialogue
Session on HOLD by the originating party | | | CASE A | | | CASE a | | ← INVITE(inactive) | INVITE(inactive) | ← | → 200 OK (inactive) | 200 OK ( inactive ) | → | ← ACK | ACK | ← | |
CASE b | | | UPDATE(inactive) | ← | | 200 OK ( inactive ) | → | |
CASE B | | | CASE a | | ← UPDATE(inactive) | UPDATE(inactive) | ← | → 200 OK (inactive) | 200 OK ( inactive ) | → | |
CASE b | | | INVITE(inactive) | ← | | 200 OK ( inactive ) | → | | ACK | ← | | | Apply post test routine | |
+| Test Equipment (Gm) | SUT | Test Equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Establish a confirmed dialogue
Session on HOLD by the originating party | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE a | | ← INVITE(inactive) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE(inactive) | ← | → 200 OK (inactive) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( inactive ) | → | ← ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE(inactive) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( inactive ) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE a | | ← UPDATE(inactive) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE(inactive) | ← | → 200 OK (inactive) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( inactive ) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE(inactive) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( inactive ) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|------------------------------------------------------------------|-----------------------------|----------------------------|------------|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|---------------|--|--|---------------|---|------------------|------------------|---|---------------------|----------------------------|---|-------|-----|---|--|-------------------|--|--|------------------|---|--|----------------------------|---|--|-------------------|--|--|---------------|---|------------------|------------------|---|---------------------|----------------------------|---|--|-------------------|--|--|------------------|---|--|----------------------------|---|--|-----|---|--|--|--------------------------------|--|
+| TSS
Network | TP
CH_N01_010 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose:
Retrieve the session in a confirmed dialogue. The media streams were previously set to inactive.
Ensure that the SUT transfers the RETRIVE request from the terminating party in a confirmed dialogue. The 200 OK response containing an SDP body with an attribute line indicating 'a=sendonly'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Precondition: - • A confirmed dialogue was established between the served user and a remote user according to the 'basic Call' procedures
- • The media stream was previously set to 'recvonly'
- • The media stream was previously set to 'inactive'
- • The terminating party retrieves the held session
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test Equipment (Gm) | SUT | Test Equipment (Gm) |
Establish a confirmed dialogue
The originating party sets the session on HOLD
The terminating party sets the session on HOLD |
| CASE A | | |
| CASE a | ← | INVITE(recvonly) |
| INVITE(recvonly) | ← | → 200 OK (sendonly) |
| 200 OK (sendonly) | → | ← ACK |
| ACK | ← | |
CASE b | | |
| UPDATE(recvonly) | ← | |
| 200 OK (sendonly) | → | |
CASE B | | |
| CASE a | ← | UPDATE(recvonly) |
| UPDATE(recvonly) | ← | → 200 OK (sendonly) |
| 200 OK (sendonly) | → | |
CASE b | | |
| INVITE(recvonly) | ← | |
| 200 OK (sendonly) | → | |
| ACK | ← | |
| Apply post test routine |
| | | | Test Equipment (Gm) | SUT | Test Equipment (Gm) | Establish a confirmed dialogue
The originating party sets the session on HOLD
The terminating party sets the session on HOLD | | | CASE A | | | CASE a | ← | INVITE(recvonly) | INVITE(recvonly) | ← | → 200 OK (sendonly) | 200 OK ( sendonly ) | → | ← ACK | ACK | ← | |
CASE b | | | UPDATE(recvonly) | ← | | 200 OK ( sendonly ) | → | |
CASE B | | | CASE a | ← | UPDATE(recvonly) | UPDATE(recvonly) | ← | → 200 OK (sendonly) | 200 OK ( sendonly ) | → | |
CASE b | | | INVITE(recvonly) | ← | | 200 OK ( sendonly ) | → | | ACK | ← | | | Apply post test routine | |
+| Test Equipment (Gm) | SUT | Test Equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Establish a confirmed dialogue
The originating party sets the session on HOLD
The terminating party sets the session on HOLD | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE a | ← | INVITE(recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE(recvonly) | ← | → 200 OK (sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( sendonly ) | → | ← ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE(recvonly) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( sendonly ) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE a | ← | UPDATE(recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE(recvonly) | ← | → 200 OK (sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( sendonly ) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE(recvonly) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( sendonly ) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------------------------------------------|-----------------------------|----------------------------|------------|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|---------------|--|--|------------------|---|---------------|-------------------|---|---|------------------|-----|---|---|-------------------|--|--|---|-----|--|--|--|---------------|--|--|---|------------------|--|--|---|-------------------|---------------|--|--|------------------|---|---------------|-------------------|---|---|------------------|--|--|---|-------------------|--|--|--|---------------|--|--|---|------------------|--|--|---|-------------------|--|--|---|-----|--------------------------------|--|--|
+| TSS
Network | TP
CH_N01_011 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose:
Retrieve the session in a confirmed dialogue. The media streams were previously set to inactive.
Ensure that the SUT transfers the RETRIVE request from the originating party in a confirmed dialogue. The 200 OK response containing an SDP body with an attribute line indicating 'a=recvonly'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Precondition: - • A confirmed dialogue was established between the served user and a remote user according to the 'basic Call' procedures
- • The media stream was previously set to 'recvonly'
- • The media stream was previously set to 'inactive'
- • The originating party retrieves the held session
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test Equipment (Gm) | SUT | Test Equipment (Gm) |
Establish a confirmed dialogue
The originating party sets the session on HOLD
The terminating party sets the session on HOLD |
| CASE A | | |
| INVITE(sendonly) | ➔ | CASE a |
| 200 OK (recvonly) | ← | ➔ | INVITE(sendonly) |
| ACK | ← | ← | 200 OK (recvonly) |
| | ➔ | ACK |
| | | CASE b |
| | ➔ | UPDATE(sendonly) |
| | ← | 200 OK (recvonly) |
| CASE B | | |
| UPDATE(sendonly) | ➔ | CASE a |
| 200 OK (recvonly) | ← | ➔ | UPDATE(sendonly) |
| | ← | 200 OK (recvonly) |
| | | CASE b |
| | ➔ | INVITE(sendonly) |
| | ← | 200 OK (recvonly) |
| | ➔ | ACK |
| Apply post test routine |
| | | | Test Equipment (Gm) | SUT | Test Equipment (Gm) | Establish a confirmed dialogue
The originating party sets the session on HOLD
The terminating party sets the session on HOLD | | | CASE A | | | INVITE(sendonly) | ➔ | CASE a | 200 OK (recvonly) | ← | ➔ | INVITE(sendonly) | ACK | ← | ← | 200 OK (recvonly) | | | ➔ | ACK | | | | CASE b | | | ➔ | UPDATE(sendonly) | | | ← | 200 OK (recvonly) | CASE B | | | UPDATE(sendonly) | ➔ | CASE a | 200 OK (recvonly) | ← | ➔ | UPDATE(sendonly) | | | ← | 200 OK (recvonly) | | | | CASE b | | | ➔ | INVITE(sendonly) | | | ← | 200 OK (recvonly) | | | ➔ | ACK | Apply post test routine | | |
+| Test Equipment (Gm) | SUT | Test Equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Establish a confirmed dialogue
The originating party sets the session on HOLD
The terminating party sets the session on HOLD | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE(sendonly) | ➔ | CASE a | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (recvonly) | ← | ➔ | INVITE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | ← | 200 OK (recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | UPDATE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← | 200 OK (recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE(sendonly) | ➔ | CASE a | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (recvonly) | ← | ➔ | UPDATE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← | 200 OK (recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | INVITE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← | 200 OK (recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Network | TP
CH_N01_012 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-----------------------------------------------------------|----------------------|----------------------------|------------|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|---------------|--|--|---------------|--|--------------------|------------------|---|---------------------|-------------------|---|-------|-----|---|--|---------------|--|--|------------------|---|--|-------------------|---|--|---------------|--|--|---------------|--|--------------------|------------------|---|---------------------|-------------------|---|--|---------------|--|--|------------------|---|--|-------------------|---|--|-----|---|--|--|--------------------------------|--|
+| Test purpose:
Retrieve the session in a confirmed dialogue. The media streams were previously set to inactive.
Ensure that the SUT transfers the RETRIVE request from the terminating party in a confirmed dialogue. The 200 OK response containing an SDP body with an attribute line indicating 'a=recvonly'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Precondition: - A confirmed dialogue was established between the served user and a remote user according to the 'basic Call' procedures
- The media stream was previously set to 'sendonly'
- The media stream was previously set to 'inactive'
- The terminating party retrieves the held session
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test Equipment (Gm) | SUT | Test Equipment (Gm) |
Establish a confirmed dialogue
The terminating party sets the session on HOLD
The originating party sets the session on HOLD |
| CASE A |
| CASE a | | ← INVITE(sendonly) |
| INVITE(sendonly) | ← | → 200 OK (recvonly) |
| 200 OK (recvonly) | → | ← ACK |
| ACK | ← | |
| CASE b |
| UPDATE(sendonly) | ← | |
| 200 OK (recvonly) | → | |
| CASE B |
| CASE a | | ← UPDATE(sendonly) |
| UPDATE(sendonly) | ← | → 200 OK (recvonly) |
| 200 OK (recvonly) | → | |
| CASE b |
| INVITE(sendonly) | ← | |
| 200 OK (recvonly) | → | |
| ACK | ← | |
| Apply post test routine |
| | | | Test Equipment (Gm) | SUT | Test Equipment (Gm) | Establish a confirmed dialogue
The terminating party sets the session on HOLD
The originating party sets the session on HOLD | | | CASE A | | | CASE a | | ← INVITE(sendonly) | INVITE(sendonly) | ← | → 200 OK (recvonly) | 200 OK (recvonly) | → | ← ACK | ACK | ← | | CASE b | | | UPDATE(sendonly) | ← | | 200 OK (recvonly) | → | | CASE B | | | CASE a | | ← UPDATE(sendonly) | UPDATE(sendonly) | ← | → 200 OK (recvonly) | 200 OK (recvonly) | → | | CASE b | | | INVITE(sendonly) | ← | | 200 OK (recvonly) | → | | ACK | ← | | | Apply post test routine | |
+| Test Equipment (Gm) | SUT | Test Equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Establish a confirmed dialogue
The terminating party sets the session on HOLD
The originating party sets the session on HOLD | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE a | | ← INVITE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE(sendonly) | ← | → 200 OK (recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (recvonly) | → | ← ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE(sendonly) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (recvonly) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE a | | ← UPDATE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE(sendonly) | ← | → 200 OK (recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (recvonly) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE(sendonly) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (recvonly) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------------------------------------------|-----------------------------|----------------------------|--|------------|--|----------------------------|---------------------------------------|--|--|--|--|-------------------------------------------------------|--|--|--|--|-------------------------------------------------------|--|--|--|--|---------------|--|--|--|--|------------------|---|--|--|---------------|-------------------|---|--|---|------------------|-----|---|--|---|----------------------------|--|--|--|---|-----|--|--|--|--|---------------|--|--|--|---|------------------|--|--|--|---|----------------------------|---------------|--|--|--|--|------------------|---|--|--|---------------|-------------------|---|--|---|------------------|--|--|--|---|----------------------------|--|--|--|--|---------------|--|--|--|---|------------------|--|--|--|---|----------------------------|--|--|--|---|-----|--------------------------------|--|--|--|--|
+| TSS
Network | TP
CH_N01_013 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose:
Retrieve the session in a confirmed dialogue. The media streams were previously set to inactive.
Ensure that the SUT transfers the RETRIVE request from the originating party in a confirmed dialogue. The 200 OK response containing an SDP body with an attribute line indicating 'a=recvonly'. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Precondition: - • A confirmed dialogue was established between the served user and a remote user according to the 'basic Call' procedures
- • The media stream was previously set to 'sendonly'
- • The media stream was previously set to 'inactive'
- • The originating party retrieves the held session
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test Equipment (Gm) | | SUT | | Test Equipment (Gm) |
| Establish a confirmed dialogue |
| The terminating party sets the session on HOLD |
| The originating party sets the session on HOLD |
| CASE A | | | | |
| INVITE(recvonly) | → | | | CASE a |
| 200 OK (sendonly) | ← | | → | INVITE(recvonly) |
| ACK | ← | | ← | 200 OK (sendonly) |
| | | → | ACK |
| | | | CASE b |
| | | → | UPDATE(recvonly) |
| | | ← | 200 OK (sendonly) |
| CASE B | | | | |
| UPDATE(recvonly) | → | | | CASE a |
| 200 OK (sendonly) | ← | | → | UPDATE(recvonly) |
| | | ← | 200 OK (sendonly) |
| | | | CASE b |
| | | → | INVITE(recvonly) |
| | | ← | 200 OK (sendonly) |
| | | → | ACK |
| Apply post test routine |
| | | | Test Equipment (Gm) | | SUT | | Test Equipment (Gm) | Establish a confirmed dialogue | | | | | The terminating party sets the session on HOLD | | | | | The originating party sets the session on HOLD | | | | | CASE A | | | | | INVITE(recvonly) | → | | | CASE a | 200 OK (sendonly) | ← | | → | INVITE(recvonly) | ACK | ← | | ← | 200 OK ( sendonly ) | | | | → | ACK | | | | | CASE b | | | | → | UPDATE(recvonly) | | | | ← | 200 OK ( sendonly ) | CASE B | | | | | UPDATE(recvonly) | → | | | CASE a | 200 OK (sendonly) | ← | | → | UPDATE(recvonly) | | | | ← | 200 OK ( sendonly ) | | | | | CASE b | | | | → | INVITE(recvonly) | | | | ← | 200 OK ( sendonly ) | | | | → | ACK | Apply post test routine | | | | |
+| Test Equipment (Gm) | | SUT | | Test Equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Establish a confirmed dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| The terminating party sets the session on HOLD | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| The originating party sets the session on HOLD | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE(recvonly) | → | | | CASE a | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (sendonly) | ← | | → | INVITE(recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | | ← | 200 OK ( sendonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → | UPDATE(recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← | 200 OK ( sendonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE(recvonly) | → | | | CASE a | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (sendonly) | ← | | → | UPDATE(recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← | 200 OK ( sendonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → | INVITE(recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← | 200 OK ( sendonly ) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|------------------------------------------------------------------|-------------------------------------------|----------------------------|------------|----------------------------|--|---------------------------------------|--|------------------------------------------------------------------------|-------------|--|--|---------------------|--|-----------------------------------------------------------------|--------|--|--|---------------------|--|--|--------------------------------|--|
+| TSS
Network | TP
CH_N01_014 | HOLD reference
Clause 4.5.2.4 of
[ITU-T Q.3619 v.1] | Selection expression
PICS 5.3/3 | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose:
The network provides an announcement to the originating user when setting the session on HOLD.
Ensure that the SUT provides an announcement to the originating user when setting the session on HOLD. | | | | | | | | | | | | | | | | | | | | | | | | |
+| Precondition: - • A confirmed dialogue was established between the served user and a remote user according to the 'basic Call' procedures
- • The media stream is set on HOLD
- • The SUT provides an announcement
| | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test Equipment (Gm) | SUT | Test Equipment (Gm) |
| Establish a confirmed dialogue | |
CASE A
INVITE(sendonly)
200 OK (recvonly)
ACK | ➔
←
← | |
| Announcement | |
CASE B
UPDATE(sendonly)
200 OK (recvonly) | ➔
← | |
| Announcement | |
| Apply post test routine | |
| | | | Test Equipment (Gm) | SUT | Test Equipment (Gm) | | Establish a confirmed dialogue | | CASE A
INVITE( sendonly )
200 OK (recvonly)
ACK | ➔
←
← | | | Announcement | | CASE B
UPDATE( sendonly )
200 OK (recvonly) | ➔
← | | | Announcement | | | Apply post test routine | |
+| Test Equipment (Gm) | SUT | Test Equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | |
+| | Establish a confirmed dialogue | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE A
INVITE( sendonly )
200 OK (recvonly)
ACK | ➔
←
← | | | | | | | | | | | | | | | | | | | | | | | |
+| | Announcement | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE B
UPDATE( sendonly )
200 OK (recvonly) | ➔
← | | | | | | | | | | | | | | | | | | | | | | | |
+| | Announcement | | | | | | | | | | | | | | | | | | | | | | | |
+| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|------------------------------------------------------------------|-------------------------------------------|----------------------------|------------|----------------------------|--|---------------------------------------|--|--|---------------|--|--|-------------------------------------------------------------|--|--|---------------------|--|--|---------------|--|--|----------------------------------------------------|--|--|---------------------|--|--|--------------------------------|--|
+| TSS
Network | TP
CH_N01_015 | HOLD reference
Clause 4.5.2.4 of
[ITU-T Q.3619 v.1] | Selection expression
PICS 5.3/3 | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose:
The network provides an announcement to the terminating user when setting the session on HOLD.
Ensure that the SUT provides an announcement to the terminating user when setting the session on HOLD. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Precondition: - • A confirmed dialogue was established between the served user and a remote user according to the 'basic Call' procedures
- • The media stream is set on HOLD
- • The SUT provides an announcement
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test Equipment (Gm) | SUT | Test Equipment (Gm) |
| Establish a confirmed dialogue | |
| CASE A | |
| ← INVITE(sendonly)
➔ 200 OK (recvonly)
← ACK | |
| Announcement | |
| CASE B | |
| ← UPDATE(sendonly)
➔ 200 OK (recvonly) | |
| Announcement | |
| Apply post test routine | |
| | | | Test Equipment (Gm) | SUT | Test Equipment (Gm) | | Establish a confirmed dialogue | | | CASE A | | | ← INVITE( sendonly )
➔ 200 OK (recvonly)
← ACK | | | Announcement | | | CASE B | | | ← UPDATE( sendonly )
➔ 200 OK (recvonly) | | | Announcement | | | Apply post test routine | |
+| Test Equipment (Gm) | SUT | Test Equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Establish a confirmed dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← INVITE( sendonly )
➔ 200 OK (recvonly)
← ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Announcement | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← UPDATE( sendonly )
➔ 200 OK (recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Announcement | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Network | TP
CH_N01_016 | HOLD reference
Clause 4.5.2.4 of
[ITU-T Q.3619 v.1] | Selection expression
PICS 5.3/4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|------------------------------------------------------------------|-------------------------------------------|---------------------|-----|---------------------|--|---------------------------------------|--|---------------|--|--|------------------|---|---------------|-------------------|---|---|------------------|-----|---|---|-------------------|--|--|---|-----|--|--|--|---------------|--|--|---|------------------|--|--|---|-------------------|---------------|--|--|--|------------------|---|--|---------------|-------------------|---|---|------------------|--|--|---|-------------------|--|--|--|---------------|--|--|---|------------------|--|--|---|-------------------|--|--|---|-----|--|--------------------------------|--|
+| Test purpose:
The SUT lower the bandwidth by setting the b=AS to a small value.
Ensure that the SUT shall lower the bandwidth for each media stream when the originating user sets the session on HOLD marked "recvonly" by setting the "b=AS:" parameter to a small value, e.g. "b=AS:0". The "b=RR:" and "b=RS:" parameters shall be set to values large enough to enable continuation of the RTCP flow, e.g. "b=RR:800" and "b=RS:800". | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
200 OK (recvonly)
b=AS:<>
b=RR:<>
b=RS:<> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test Equipment (Gm) | SUT | Test Equipment (Gm) |
| Establish a confirmed dialogue | |
| CASE A | | |
| INVITE(sendonly) | → | CASE a |
| 200 OK (recvonly) | ← | → | INVITE(sendonly) |
| ACK | ← | ← | 200 OK (recvonly) |
| | → | ACK |
| | | CASE b |
| | → | UPDATE(sendonly) |
| | ← | 200 OK (recvonly) |
| CASE B | | | |
| UPDATE(sendonly) | → | | CASE a |
| 200 OK (recvonly) | ← | → | UPDATE(sendonly) |
| | ← | 200 OK (recvonly) |
| | | CASE b |
| | → | INVITE(sendonly) |
| | ← | 200 OK (recvonly) |
| | → | ACK |
| Apply post test routine | |
| | | | Test Equipment (Gm) | SUT | Test Equipment (Gm) | | Establish a confirmed dialogue | | CASE A | | | INVITE(sendonly) | → | CASE a | 200 OK (recvonly) | ← | → | INVITE(sendonly) | ACK | ← | ← | 200 OK (recvonly) | | | → | ACK | | | | CASE b | | | → | UPDATE(sendonly) | | | ← | 200 OK (recvonly) | CASE B | | | | UPDATE(sendonly) | → | | CASE a | 200 OK (recvonly) | ← | → | UPDATE(sendonly) | | | ← | 200 OK (recvonly) | | | | CASE b | | | → | INVITE(sendonly) | | | ← | 200 OK (recvonly) | | | → | ACK | | Apply post test routine | |
+| Test Equipment (Gm) | SUT | Test Equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Establish a confirmed dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE(sendonly) | → | CASE a | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (recvonly) | ← | → | INVITE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | ← | 200 OK (recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → | UPDATE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← | 200 OK (recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE(sendonly) | → | | CASE a | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (recvonly) | ← | → | UPDATE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← | 200 OK (recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → | INVITE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← | 200 OK (recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS | TP | HOLD reference | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|-----------------------------------------|-----------------------------|---------------------|-----|---------------------|--|---------------------------------------|--|---------------|--|--|---------------|--|--|------------------|---|--------------------|----------------------------|---|---------------------|-----|---|-------|---------------|--|--|------------------|---|--|----------------------------|---|--|---------------|--|--|---------------|--|--|------------------|---|--------------------|----------------------------|---|---------------------|---------------|--|--|------------------|---|--|----------------------------|---|--|-----|---|--|--|--------------------------------|--|
+| Network | CH_N01_017 | Clause 4.5.2.4 of
[ITU-T Q.3619 v.1] | PICS 5.3/4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose:
The SUT lower the bandwidth by setting the b=AS to a small value.
Ensure that the SUT shall lower the bandwidth for each media stream when the terminating user sets the session on HOLD marked "recvonly" by setting the "b=AS:" parameter to a small value, e.g. "b=AS:0". The "b=RR:" and "b=RS:" parameters shall be set to values large enough to enable continuation of the RTCP flow, e.g. "b=RR:800" and "b=RS:800".
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
200 OK (recvonly)
b=AS:<>
b=RR:<>
b=RS:<>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test Equipment (Gm) | SUT | Test Equipment (Gm) |
| Establish a confirmed dialogue | |
| CASE A |
| CASE a |
| INVITE(sendonly) | ← | ← INVITE(sendonly) |
| 200 OK (recvonly) | → | → 200 OK (recvonly) |
| ACK | ← | ← ACK |
| CASE b |
| UPDATE(sendonly) | ← | |
| 200 OK (recvonly) | → | |
| CASE B |
| CASE a |
| UPDATE(sendonly) | ← | ← UPDATE(sendonly) |
| 200 OK (recvonly) | → | → 200 OK (recvonly) |
| CASE b |
| INVITE(sendonly) | ← | |
| 200 OK (recvonly) | → | |
| ACK | ← | |
| Apply post test routine | |
| | | | Test Equipment (Gm) | SUT | Test Equipment (Gm) | | Establish a confirmed dialogue | | CASE A | | | CASE a | | | INVITE(sendonly) | ← | ← INVITE(sendonly) | 200 OK ( recvonly ) | → | → 200 OK (recvonly) | ACK | ← | ← ACK | CASE b | | | UPDATE(sendonly) | ← | | 200 OK ( recvonly ) | → | | CASE B | | | CASE a | | | UPDATE(sendonly) | ← | ← UPDATE(sendonly) | 200 OK ( recvonly ) | → | → 200 OK (recvonly) | CASE b | | | INVITE(sendonly) | ← | | 200 OK ( recvonly ) | → | | ACK | ← | | | Apply post test routine | |
+| Test Equipment (Gm) | SUT | Test Equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Establish a confirmed dialogue | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE a | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE(sendonly) | ← | ← INVITE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( recvonly ) | → | → 200 OK (recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | ← ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE(sendonly) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( recvonly ) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE a | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE(sendonly) | ← | ← UPDATE(sendonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( recvonly ) | → | → 200 OK (recvonly) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE(sendonly) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK ( recvonly ) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Network | TP
CH_N01_018 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------------------------------------------------------------|-----------------------------|---------------------|-----|---------------------|------------------------------------------------------------------------------------------|--|--|---------------------------------------------------------------|-----------------|-------------------------------------------------------------------------|--|------------|------------------------------------------------------------|------------------------------------------------------------|----------------|----------------------------------------------------------------|--|-----------------|---------------------------------------------------------------------|
+| Test purpose:
The SUT lower the bandwidth by setting the b=AS to a small value.
Ensure that the SUT shall lower the bandwidth for each media stream when the originating user sets the session on HOLD marked "inactive" by setting the "b=AS:" parameter to a small value, e.g. "b=AS:0". The "b=RR:" and "b=RS:" parameters shall be set to values large enough to enable continuation of the RTCP flow, e.g. "b=RR:800" and "b=RS:800". | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
200 OK (recvonly)
b=AS:<>
b=RR:<>
b=RS:<> | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test Equipment (Gm) | SUT | Test Equipment (Gm) |
Establish a confirmed dialogue
Session on HOLD by the terminating party |
CASE A
INVITE(inactive)
200 OK (inactive)
ACK |
→
←
← |
CASE a
→ INVITE(inactive)
← 200 OK (inactive)
→ ACK |
|
→
← | CASE b
→ UPDATE(inactive)
← 200 OK (inactive) |
CASE B
UPDATE(inactive)
200 OK (inactive) |
→
← |
CASE a
→ UPDATE(inactive)
← 200 OK (inactive) |
|
→
←
→ | CASE b
→ INVITE(inactive)
← 200 OK (inactive)
→ ACK |
Apply post test routine
| | | | Test Equipment (Gm) | SUT | Test Equipment (Gm) | Establish a confirmed dialogue
Session on HOLD by the terminating party | | | CASE A
INVITE(inactive)
200 OK (inactive)
ACK |
→
←
← |
CASE a
→ INVITE(inactive)
← 200 OK (inactive)
→ ACK | |
→
← | CASE b
→ UPDATE(inactive)
← 200 OK (inactive) |
CASE B
UPDATE(inactive)
200 OK (inactive) |
→
← |
CASE a
→ UPDATE(inactive)
← 200 OK (inactive) | |
→
←
→ | CASE b
→ INVITE(inactive)
← 200 OK (inactive)
→ ACK |
+| Test Equipment (Gm) | SUT | Test Equipment (Gm) | | | | | | | | | | | | | | | | | | | |
+| Establish a confirmed dialogue
Session on HOLD by the terminating party | | | | | | | | | | | | | | | | | | | | | |
+| CASE A
INVITE(inactive)
200 OK (inactive)
ACK |
→
←
← |
CASE a
→ INVITE(inactive)
← 200 OK (inactive)
→ ACK | | | | | | | | | | | | | | | | | | | |
+| |
→
← | CASE b
→ UPDATE(inactive)
← 200 OK (inactive) | | | | | | | | | | | | | | | | | | | |
+|
CASE B
UPDATE(inactive)
200 OK (inactive) |
→
← |
CASE a
→ UPDATE(inactive)
← 200 OK (inactive) | | | | | | | | | | | | | | | | | | | |
+| |
→
←
→ | CASE b
→ INVITE(inactive)
← 200 OK (inactive)
→ ACK | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Network | TP
CH_N01_019 | HOLD reference
Clause 4.5.2.1 of
[ITU-T Q.3619 v.1] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|-----------------------------------------------------------|----------------------|----------------------------|------------|----------------------------|--|------------------------------------------------------------------------------------|--|---------------|--|--|---------------|--|--|------------------|---|--------------------|-------------------|---|---------------------|-----|---|-------|---------------|--|--|------------------|---|--|-------------------|---|--|---------------|--|--|---------------|--|--|------------------|---|--------------------|-------------------|---|---------------------|---------------|--|--|------------------|---|--|-------------------|---|--|-----|---|--|--|--------------------------------|--|
+| Test purpose:
The SUT lower the bandwidth by setting the b=AS to a small value.
Ensure that the SUT shall lower the bandwidth for each media stream when the terminating user sets the session on HOLD marked "inactive" by setting the "b=AS:" parameter to a small value, e.g. "b=AS:0". The "b=RR:" and "b=RS:" parameters shall be set to values large enough to enable continuation of the RTCP flow, e.g. "b=RR:800" and "b=RS:800". | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
200 OK (recvonly)
b=AS:<>
b=RR:<>
b=RS:<> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test Equipment (Gm) | SUT | Test Equipment (Gm) |
| Establish a confirmed dialogue
Session on HOLD by the originating party | |
| CASE A |
| CASE a |
| INVITE(inactive) | ← | ← INVITE(inactive) |
| 200 OK (inactive) | → | → 200 OK (inactive) |
| ACK | ← | ← ACK |
| CASE b |
| UPDATE(inactive) | ← | |
| 200 OK (inactive) | → | |
| CASE B |
| CASE a |
| UPDATE(inactive) | ← | ← UPDATE(inactive) |
| 200 OK (inactive) | → | → 200 OK (inactive) |
| CASE b |
| INVITE(inactive) | ← | |
| 200 OK (inactive) | → | |
| ACK | ← | |
| Apply post test routine | |
| | | | Test Equipment (Gm) | SUT | Test Equipment (Gm) | | Establish a confirmed dialogue
Session on HOLD by the originating party | | CASE A | | | CASE a | | | INVITE(inactive) | ← | ← INVITE(inactive) | 200 OK (inactive) | → | → 200 OK (inactive) | ACK | ← | ← ACK | CASE b | | | UPDATE(inactive) | ← | | 200 OK (inactive) | → | | CASE B | | | CASE a | | | UPDATE(inactive) | ← | ← UPDATE(inactive) | 200 OK (inactive) | → | → 200 OK (inactive) | CASE b | | | INVITE(inactive) | ← | | 200 OK (inactive) | → | | ACK | ← | | | Apply post test routine | |
+| Test Equipment (Gm) | SUT | Test Equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Establish a confirmed dialogue
Session on HOLD by the originating party | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE a | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE(inactive) | ← | ← INVITE(inactive) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (inactive) | → | → 200 OK (inactive) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | ← ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE(inactive) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (inactive) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE a | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| UPDATE(inactive) | ← | ← UPDATE(inactive) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (inactive) | → | → 200 OK (inactive) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE b | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE(inactive) | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (inactive) | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.4008.1-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.4008.1-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426
--- /dev/null
+++ b/marked/Q/T-REC-Q.4008.1-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:476aa07e8e41a13b741a431c04ad0f9bd3a7bd0a3822f14a669b12f2abaf0e0d
+size 3828
diff --git a/marked/Q/T-REC-Q.4008.1-201608-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4008.1-201608-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..4cf1bf797f8652947a99f605c96284769dd3d3f5
--- /dev/null
+++ b/marked/Q/T-REC-Q.4008.1-201608-I_PDF-E/raw.md
@@ -0,0 +1,179 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.4008.1**
+
+(08/2016)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Testing specifications – Testing specifications for SIP-IMS
+
+---
+
+**Malicious communication identification using IP
+multimedia core network subsystem;
+Conformance test specification – Part 1:
+Protocol implementation conformance
+statement**
+
+Recommendation ITU-T Q.4008.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.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+| Testing specifications for next generation networks | Q.3900–Q.3999 |
+| Testing specifications for SIP-IMS | Q.4000–Q.4039 |
+| Testing specifications for Cloud computing | Q.4040–Q.4059 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## Recommendation ITU-T Q.4008.1
+
+## **Malicious communication identification using IP multimedia core network subsystem; Conformance test specification – Part 1: Protocol implementation conformance statement**
+
+## **Summary**
+
+Recommendation ITU-T Q.4008.1 v.1 (2016) specifies the testing requirements for malicious communication identification (MCID) using IP multimedia (IM) core network (CN) subsystem; Conformance test specification – Part 1: Protocol implementation conformance statement (PICS).
+
+The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.4008.1, and that it relates to Release 10 of the relevant 3GPP/ETSI standard.
+
+This Recommendation endorses ETSI TS 101 595-1 V5.1.1 (2012-10); "IMS Network Testing (INT); Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Test Specification; Part 1: Protocol Implementation Conformance Statement (PICS) ".
+
+## **History**
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|--------------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.4008.1 v.1 | 2016-08-29 | 11 | 11.1002/1000/12996 |
+
+## **Keywords**
+
+Interworking, IP multimedia subsystem, IMS, session description protocol, SDP, session initiation protocol, SIP , testing.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+### NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Recommendation ITU-T Q.4008.1
+
+### **Malicious communication identification using IP multimedia core network subsystem; Conformance test specification – Part 1: Protocol implementation conformance statement**
+
+## **1 Scope**
+
+This Recommendation specifies the testing requirements for malicious communication identification (MCID) using IP multimedia (IM) core network (CN) subsystem; Conformance test specification – Part 1: Protocol implementation conformance statement (PICS).
+
+This Recommendation endorses [ETSI TS 101 595-1 V5.1.1] (2012-10), "IMS Network Testing (INT); Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Test Specification; Part 1: Protocol Implementation Conformance Statement (PICS) ".
+
+## **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.
+
+[ETSI TS 101 595-1 V5.1.1] ETSI TS 101 595-1 V5.1.1 (2012-10); *IMS Network Testing (INT); Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Test Specification; Part 1: Protocol Implementation Conformance Statement (PICS).*
+
+## **3 Definitions**
+
+None.
+
+## **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|-----|------------------------------|
+| IMS | IP Multimedia Subsystem |
+| IP | Internet Protocol |
+| SDP | Session Description Protocol |
+| SIP | Session Initiation Protocol |
+
+## **5 Conventions**
+
+None.
+
+## **6 Endorsement**
+
+[ETSI TS 101 595-1 V5.1.1]
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.4009.2-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.4009.2-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cd85c5f0cf29767d5fce2cdb865aece52387c01d
--- /dev/null
+++ b/marked/Q/T-REC-Q.4009.2-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:09082581f21d9548df66739aba3c0950a4cd19b319365b8f1c69a3129a386b3c
+size 4070
diff --git a/marked/Q/T-REC-Q.4009.2-201608-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4009.2-201608-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..d29e466c7bf1e7d3b281838b91ce714637cb6c89
--- /dev/null
+++ b/marked/Q/T-REC-Q.4009.2-201608-I_PDF-E/raw.md
@@ -0,0 +1,177 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.4009.2**
+
+(08/2016)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Testing specifications – Testing specifications for SIP-IMS
+
+---
+
+**Completion of communications to busy
+subscriber and completion of communications
+by no reply using IP multimedia core network
+subsystem; Conformance test specification –
+Part 2: Test suite structure and test purposes**
+
+Recommendation ITU-T Q.4009.2
+
+# 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 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+| Testing specifications for next generation networks | Q.3900–Q.3999 |
+| Testing specifications for SIP-IMS | Q.4000–Q.4039 |
+| Testing specifications for Cloud computing | Q.4040–Q.4059 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## Recommendation ITU-T Q.4009.2
+
+### **Completion of communications to busy subscriber and completion of communications by no reply using IP multimedia core network subsystem; Conformance test specification – Part 2: Test suite structure and test purposes**
+
+## Summary
+
+Recommendation ITU-T Q.4009.2 v.1 (2016) specifies the testing requirements for supplementary service "Completion of communications to busy subscriber (CCBS) and completion of communications by no reply (CCNR) using IP multimedia (IM) core network (CN) subsystem; Conformance test specification – Part 2: Test suite structure and test purposes (TSS&TP)".
+
+The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.4009.2, and that it relates to Release 10 of the relevant 3GPP/ETSI standard.
+
+This Recommendation endorses ETSI TS 101 588-2 V5.1.1 (2012-10); "IMS Network Testing (INT); Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Test Specification; Part 2: Test Suite Structure and Test Purposes (TSS&TP)".
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|--------------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.4009.2 v.1 | 2016-08-29 | 11 | 11.1002/1000/13000 |
+
+## Keywords
+
+IMS, IP multimedia subsystem, interworking, session description protocol, SDP, session initiation protocol, SIP, testing.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+### NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Recommendation ITU-T Q.4009.2
+
+## **Completion of communications to busy subscriber and completion of communications by no reply using IP multimedia core network subsystem; Conformance test specification – Part 2: Test suite structure and test purposes**
+
+## **1 Scope**
+
+This Recommendation specifies the testing requirements for supplementary service "Completion of communications to busy subscriber (CCBS) and completion of communications by no reply (CCNR) using IP multimedia (IM) core network (CN) subsystem; Conformance test specification – Part 2: Test suite structure and test purposes (TSS&TP)".
+
+This Recommendation endorses [ETSI TS 101 588-2 V5.1.1] (2012-10); "IMS Network Testing (INT); Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Test Specification; Part 2: Test Suite Structure and Test Purposes (TSS&TP)".
+
+## **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.
+
+[ETSI TS 101 588-2 V5.1.1] ETSI TS 101 588-1 V5.1.1 (2012-10), *IMS Network Testing (INT); Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Test Specification; Part 2: Test Suite Structure and Test Purposes (TSS&TP)*.
+
+## **3 Definitions**
+
+None.
+
+## **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|-----|------------------------------|
+| IMS | IP Multimedia Subsystem |
+| IP | Internet Protocol |
+| SDP | Session Description Protocol |
+| SIP | Session Initiation Protocol |
+
+## **5 Conventions**
+
+None.
+
+## **6 Endorsement**
+
+[ETSI TS 101 588-2 V5.1.1]
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.4015.2-201605-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.4015.2-201605-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ffdffaa305a676704a0882bdb37fa339cfb15c63
--- /dev/null
+++ b/marked/Q/T-REC-Q.4015.2-201605-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aabf7e54909f44fdbc817ea80c7f1889ab563371aebbe198922f7dee431c115f
+size 4133
diff --git a/marked/Q/T-REC-Q.4015.2-201605-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4015.2-201605-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a76c08828d175a3d16e1d0a9dbd8097cf9883471
--- /dev/null
+++ b/marked/Q/T-REC-Q.4015.2-201605-I_PDF-E/raw.md
@@ -0,0 +1,178 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.4015.2**
+
+(05/2016)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Testing specifications – Testing specifications for SIP-IMS
+
+---
+
+**Interworking between the IP multimedia core
+network subsystem and circuit switched
+networks; Conformance testing – Part 2: Test
+suite structure and test purposes**
+
+Recommendation ITU-T Q.4015.2
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+| Testing specifications for next generation networks | Q.3900–Q.3999 |
+| Testing specifications for SIP-IMS | Q.4000–Q.4039 |
+| Testing specifications for Cloud computing | Q.4040–Q.4059 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## Recommendation ITU-T Q.4015.2 v.1
+
+### Interworking between the IP multimedia core network subsystem and circuit switched networks; Conformance testing – Part 2: Test suite structure and test purposes
+
+## Summary
+
+Recommendation ITU-T Q.4015.2 v.1 (2016) specifies the testing requirements for the interworking between the IP multimedia (IM) core network (CN) subsystem and circuit switched (CS) networks; Conformance test specification – Part 2: Test suite structure and test purposes (TSS&TP).
+
+The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.4015.2 and that it relates to Release 10 of the relevant 3GPP/ETSI standard.
+
+This Recommendation endorses ETSI TS 102 710-2 V5.2.1 (2016), Core Network and Interoperability Testing (INT); Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks; Conformance Test Specification; Part 2: Test Suite Structure and Test Purposes (TSS&TP).
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|--------------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.4015.2 v.1 | 2016-05-14 | 11 | 11.1002/1000/12865 |
+
+## Keywords
+
+Interworking, IP multimedia subsystem, IMS, session description protocol, SDP, session initiation protocol, SIP , testing.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+### NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Recommendation ITU-T Q.4015.2 v.1
+
+### Interworking between the IP multimedia core network subsystem and circuit switched networks; Conformance testing – Part 2: Test suite structure and test purposes
+
+## 1 Scope
+
+This Recommendation specifies the testing requirements for the interworking between the IP multimedia (IM) core network (CN) subsystem and circuit switched (CS) networks; Conformance test specification – Part 2: Test suite structure and test purposes (TSS&TP).
+
+This Recommendation endorses ETSI TS 102 710-2 V5.2.1 (2016-02), Core Network and Interoperability Testing (INT); Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks; Conformance Test Specification; Part 2: Test Suite Structure and Test Purposes (TSS&TP).
+
+## 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.
+
+[ETSI TS 102 710-2 V5.2.1] ETSI TS 102 710-2 V5.2.1 (2016), *Core Network and Interoperability Testing (INT); Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks; Conformance Test Specification; Part 2: Test Suite Structure and Test Purposes (TSS&TP)*.
+
+## 3 Definitions
+
+None.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+IMS IP Multimedia Subsystem
+
+IP Internet Protocol
+
+SDP Session Description Protocol
+
+SIP Session Initiation Protocol
+
+## 5 Conventions
+
+None.
+
+## 6 Endorsement
+
+[ETSI TS 102 710-2 V5.2.1].
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.4061-201904-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/Q/T-REC-Q.4061-201904-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..529e4f72f14cdf7f41f56cfbfb26655bf8181c59
--- /dev/null
+++ b/marked/Q/T-REC-Q.4061-201904-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:abb9e3ec6dfc8364cedc39a68cf796e9d3ff5529c79a1811eedeb12c6d6e7583
+size 3787
diff --git a/marked/Q/T-REC-Q.4061-201904-I_PDF-E/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Q/T-REC-Q.4061-201904-I_PDF-E/d0abac95583b52a3b35f74a215567334_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ce57f264a8b97618df43304c3348fcf1f8079b7b
--- /dev/null
+++ b/marked/Q/T-REC-Q.4061-201904-I_PDF-E/d0abac95583b52a3b35f74a215567334_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:922f8c9bbd378869f397f6be2fcb1efa31db6a400aff2a2eac259a1fb51da02b
+size 94978
diff --git a/marked/Q/T-REC-Q.4061-201904-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.4061-201904-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..daa375c1a1928bd94de98ec85b44ee8972d9fb3c
--- /dev/null
+++ b/marked/Q/T-REC-Q.4061-201904-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2f3772b4b049ca0c24fa9a736385e1094397c46c6a2b2bbe7fa0c7d0e9d95da
+size 91956
diff --git a/marked/Q/T-REC-Q.4061-201904-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4061-201904-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..240902616a31c39c9d62a1d8df5e4d55592c9160
--- /dev/null
+++ b/marked/Q/T-REC-Q.4061-201904-I_PDF-E/raw.md
@@ -0,0 +1,322 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.4061**
+
+(04/2019)
+
+SERIES Q: SWITCHING AND SIGNALLING, AND
+ASSOCIATED MEASUREMENTS AND TESTS
+
+Testing specifications – Testing specifications for IMT-
+2020 and IoT
+
+# --- **Framework for software-defined network controller testing**
+
+Recommendation ITU-T Q.4061
+
+## ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS**
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+| Testing specifications for next generation networks | Q.3900–Q.3999 |
+| Testing specifications for SIP-IMS | Q.4000–Q.4039 |
+| Testing specifications for Cloud computing | Q.4040–Q.4059 |
+| Testing specifications for IMT-2020 and IoT | Q.4060–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.4061
+
+# Framework for software-defined network controller testing
+
+## Summary
+
+The concept of the International Mobile Telecommunications-2020 (IMT-2020) system is represented by a wide spectrum of information communication technology applications, cloud services and network infrastructure, dynamically responding to the relevant requirements of each service, whether already widely used or new. One approach to building network infrastructure is that of the software-defined network (SDN). It is described in ONF TR-526 and ITU-R M.2083.
+
+Recommendation ITU-T Q.4061 contains: a classification of SDN controller tests; parameters, structure, sequence and methodology of SDN controller testing.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.4061 | 2019-04-29 | 11 | 11.1002/1000/13887 |
+
+## Keywords
+
+Layers, northbound interface, openflow, parameters testing, SDN, southbound interface.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2019
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|------------------------------------------------------------------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 3.2 Terms defined in this Recommendation..... | 1 |
+| 4 Abbreviations and acronyms ..... | 1 |
+| 5 Conventions ..... | 1 |
+| 6 Classification of approaches to testing controller software-defined networking ..... | 2 |
+| 7 The number of parameters determined during testing of the software-defined network controller..... | 2 |
+| 8 Structure of software-defined network controller testing..... | 5 |
+| 9 Methodology for testing the software-defined network controller..... | 6 |
+| 10 The list of works carried out after completion of the tests ..... | 7 |
+| Bibliography..... | 8 |
+
+
+
+## Recommendation ITU-T Q.4061
+
+## Framework for software-defined network controller testing
+
+# 1 Scope
+
+This Recommendation describes the general approach to testing of software-defined network (SDN) controllers, specifies a number of key parameters, the totality of which determine the ability of a controller to handle a specific load and type of controlled network.
+
+# 2 References
+
+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 technologies 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 network virtualization** [b-ITU-T Y.3011]: A technology that enables the creation of logically isolated network partitions over shared physical networks so that heterogeneous collections of multiple virtual networks can simultaneously coexist over the shared networks. This includes the aggregation of multiple resources in a provider and appearing as a single resource.
+
+## 3.2 Terms defined in this Recommendation
+
+None.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|----------|---------------------------------------------|
+| App | Application |
+| API | Application Programming Interface |
+| CPU | Central Processing Unit |
+| IMT-2020 | International Mobile Telecommunication-2020 |
+| LAN | Local Area Network |
+| PCB | Printed Circuit Board |
+| RAM | Random Access Memory |
+| SDN | Software-Defined Network |
+
+# 5 Conventions
+
+None.
+
+# 6 Classification of approaches to testing controller software-defined networking
+
+An SDN is a flexible structure, which in turn can be implemented in different conditions and constructed according to the parameters required in each case. In accordance with this provision, SDN controller testing requires appropriate approaches, taking into account the peculiarities of the SDN implementation variant. Many factors in the implementation of the network infrastructure and the infrastructure of the application-level controller are considered. In some cases, testing is also required, subject to a different reservation controller. As a result of ongoing tests with subsequent collection of the results obtained, a comprehensive analysis is required, which involves the study of parameters related to testing performed on all interfaces that can possibly give an informed decision about the suitability for use of this controller in many different situations, either particular or general. However, following systems theory and in particular system properties, such as emergence, in the study of controller parameters separately from the subsequent integrated analysis does not give an accurate picture of the behaviour of the controller subject to the complex interplay of all possible effects considered separately. Study of this complex interplay is also required and needs consideration, thus the necessary resources need to be made available according to the relevant characteristics.
+
+See Figure 1.
+
+
+
+```
+graph TD; A[Classification types of testing SDN controller] --> B[Network infrastructure (Controlled network)]; A --> C[Infrastructure of applications]; A --> D[A cyber criminal's attack]; B --> E[Static calculation given the resource reserve]; E --> E1[LAN]; E --> E2[Access network]; E --> E3[Aggregation network]; E --> E4[Core network]; E --> E5[Enterprise network]; C --> F[Dynamic calculation (Taking into account the dynamics of scaling)]; F --> F1[LAN]; F --> F2[Access network]; F --> F3[Aggregation network]; F --> F4[Core network]; F --> F5[Enterprise network]; D --> D1[Attack at the level of the network infrastructure]; D --> D2[Attack at the control level and the reservation channel]; D --> D3[Application-level attack];
+```
+
+Q.4061(19)\_F01
+
+Flowchart showing the classification types of testing SDN controller. The main category branches into three: Network infrastructure (Controlled network), Infrastructure of applications, and A cyber criminal's attack. Network infrastructure branches into Static calculation (LAN, Access network, Aggregation network, Core network, Enterprise network) and Dynamic calculation (LAN, Access network, Aggregation network, Core network, Enterprise network). A cyber criminal's attack branches into Attack at the level of the network infrastructure, Attack at the control level and the reservation channel, and Application-level attack.
+
+**Figure 1 – Classification types of testing software-defined network controller**
+
+# 7 The number of parameters determined during testing of the software-defined network controller
+
+During controller testing, determination of the characteristics of several parameters is required for the complex analysis of controller operability in the program-defined network, carried out at a subsequent step, under specific conditions. Each type of testing requires several specific parameters, a complex analysis of which gives a more realistic answer about the suitability of the controller under study.
+
+Table 1 lists a number of possible parameters, the type of test, the relevant characteristics and recommendations for considering a parameter as a necessary element for conducting a subsequent analysis of the set of characteristics, and deciding whether the controller is suitable under specific conditions.
+
+**Table 1 – List of parameters for testing**
+
+| No | Name of test | Type of test | Estimated characteristics | Conditions for using the controller |
+|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|
+| 1 | Measuring the bandwidth of the controller, depending on the number of connected managed switches, with a constant number of hosts behind each switch | Load testing | 1. Bandwidth controller [flow/s] | 1. In all cases |
+| 2 | Measurement of the bandwidth of the controller depending on the number of hosts connected to a constant number of switches controlled by the controller | Load testing | 1. Bandwidth controller [flow/s] | 1. In all cases |
+| 3 | Measuring the processing time of one request (delay) depending on the number of connected switches, with a constant number of hosts | Load testing | 1. The processing time per request [ms] | 1. Aggregation-level networks;
2. Core-level networks;
3. Corporate networks |
+| 4 | Measuring the processing time of a single query (delay) depending on the number of terminal nodes, at a constant number of switches | Load testing | 1. The processing time per request [ms] | 1. Local networks;
2. Corporate networks |
+| 5 | Study of the scalability of the controller (controller performance, in the maximum load on the controller) | Load testing | 1. Productivity of the processor of the controller [kbyte/s] for cores
2. The availability of the file service (SDN controller) [%] | 1. In all cases |
+| 6 | Testing the reliability of the controller (the controller's performance, in the maximum load on the controller) | Load testing | 1. Productivity of the processor of the controller [%] for cores
2. Removable memory random access memory (RAM) [GB]
3. Temperature [°C] | 1. In all cases |
+
+**Table 1 – List of parameters for testing**
+
+| No | Name of test | Type of test | Estimated characteristics | Conditions for using the controller |
+|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|
+| 7 | Testing the performance of the controller, depending on the time and frequency of changes in the network topology, with a constant parameter of the number of measurements. | Load testing | 1. Productivity of the processor of the controller [%] for cores
2. Removable memory RAM [GB,%] | 1. Core-level networks |
+| 8 | Testing the influence of loadable module of a protocol on the performance of the controller, with increasing load on this module | Load testing | 1. Productivity of the processor of the controller [%] for cores
2. Removable memory RAM [GB,%]
3. Processing time of one request [ms] for this module | 1. In all cases |
+| 9 | Testing the influence of loadable module of a protocol on the performance of the controller, with increasing load on the controller | Load testing | 1. Productivity of the processor of the controller [%] for cores
2. Removable memory RAM [GB,%]
3. The processing time of one request [ms] | 1. In all cases |
+| 10 | Testing the performance of the controller, depending on the increased load on the controller application programming interface (API) (each of its modules) | Load testing | 1. Productivity of the processor of the controller [%] for cores
2. Removable memory RAM [GB,%]
3. The processing time of one request [ms] with a constant number of hosts and switches | 1. In all cases |
+
+**Table 1 – List of parameters for testing**
+
+| No | Name of test | Type of test | Estimated characteristics | Conditions for using the controller |
+|----|------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|
+| 11 | Performance testing of the controller depending on the number of connected applications and their maximum load | Load testing | 1. Productivity of the processor of the controller [%] for cores
2. Removable memory RAM [GB,%]
3. The processing time of one request [ms] with a constant number of hosts and switches | 1. In all cases |
+| 12 | Testing the response of the controller to the switching speed, with using it as a backup (at the time of a sharp increase in the number of requests) | Load testing | 1. The availability of file service (controller printed circuit board (PCB)) [%]
2. The performance of the central processing unit (CPU) of the controller [%] in the kernels
3. The processing time per request [ms] switching to reserve.
4. The duration of the transition process [ms] | 1. In all cases |
+
+# 8 Structure of software-defined network controller testing
+
+The program-defined network controller is a complex object of the general architecture of SDN, which is responsible for both the functioning of the network as a whole and the operation of individual services and applications. One requirement for the projected or developed SDN is its fault tolerance, which in turn depends on the stability and correctness of the controller of the program-defined network in various possible non-ordinary cases of operation. This requires building the SDN controller testing approach on the basis of systematic analysis of the necessary range of parameters, which in turn gives with some certainty the suitability of this controller in a specific case under review. The overall structure of the test is shown in Figure 2. This structure is based on the general SDN architecture and shows the main interfaces through which the controller can be disabled.
+
+
+
+The diagram illustrates the architecture of a software-defined network (SDN) controller for testing. It is organized into three horizontal layers:
+
+- Application layer:** At the top, multiple applications (App #1, App #2, App #3, ..., App #N) are shown as clouds. They connect to the Control layer via the **Nb-i** (Northbound interface).
+- Control layer:** This layer contains two SDN controllers. The primary controller and a reserve controller (SDN controller (Reserve)) both consist of an **API module**, **Main modules (protocols)**, a **Data base**, and a **New module**. Within each controller, white dotted lines labeled **Cd** (controller access bus to database) and **Ca** (controller access bus) connect these components. A **Reservation Link** labeled **Cr** connects the two controllers.
+- Network layer:** At the bottom, **Managed network elements** are shown. They connect to the Control layer via the **St-i** (Southbound interface).
+
+Reference points are labeled as follows: **Nb-i** (Northbound interface), **St-i** (Southbound interface), **Cr** (controller reservation link), **Ca** (controller access bus), and **Cd** (controller access bus to database).
+
+Q.4061(19)\_F02
+
+Figure 2: Structure of testing of controller software-defined network. The diagram shows three layers: Application layer (App #1 to App #N), Control layer (SDN controller and SDN controller (Reserve)), and Network layer (Managed network elements). The SDN controller contains an API module, Main modules (protocols), Data base, and New module. Reference points Nb-i, St-i, Cr, Ca, and Cd are indicated.
+
+**Figure 2 – Structure of testing of controller software-defined network**
+App: application
+
+Figure 2 shows the general architecture of the test controller, the main communication modules and related reference points reflecting the total number of interfaces through which the controller can be overloaded and subsequently destroyed.
+
+Figure 2 identifies a number of reference points:
+
+- St-i: southbound interface;
+- Cr: controller reservation link;
+- Ca: controller access bus;
+- Cd: controller access bus to database;
+- Nb-i: northbound interface.
+
+White dotted lines labelled "Ca" and "Cd" denote the software bus of the programming language framework based on which is the developed controller. For example, white dotted lines labelled "Ca" denote the software bus for interconnections between modules: main modules (protocols); database; new module.
+
+# 9 Methodology for testing the software-defined network controller
+
+The sequence of tests is an algorithm consisting of four stages. Tests should be carried out in the order given in this paragraph. Tests that are present at the next stage do not begin until all the processes of the previous stage are completed.
+
+Step 1. Development of test procedures for the controller.
+
+- The necessary parameters for testing the controller are determined. Strict quality assessments of each parameter (boundary conditions) are determined taking into account the network infrastructure that the SDN controller controls.
+
+Step 2. An initial test of the controller.
+
+Step 3. Identifying program and test method errors and their adjustment.
+
+Step 4. Conducting the main tests and analysis of results.
+
+- Tests of specific hardware and software characteristics of the SDN controller must be carried out.
+- The tests should show that certain characteristics of the SDN controller meet the specified evaluation criteria and test metrics.
+
+# **10 The list of works carried out after completion of the tests**
+
+Upon completion of the tests, the results are recorded in the test book, which is in the laboratory. A test report is also prepared, which contains the relevant general and special data.
+
+General data
+
+1. A description of the material side of the test object – name, colour, use, manufacturer, etc.
+2. Date of testing and the roles of the personnel participating in the trials.
+3. The conditions for finding a test object prior to the tests.
+4. Test conditions – relative humidity of indoor air, ambient temperature, atmospheric pressure, etc.
+5. Measuring instruments with an indication of their precision class and a description of the laboratory stand for testing.
+
+Special data are determined by the purpose and method of testing, the features of the object under test.
+
+The document on the tests carried out is signed by the head and personnel who conducted the tests.
+
+## Bibliography
+
+- [b-ITU-T Y.3011] Recommendation ITU-T Y.3011 (2012), *Framework of network virtualization for future networks*.
+- [b-ITU-T Y.3300] Recommendation ITU-T Y.3300 (2014), *Framework of software-defined networking*.
+- [b-ITU-R M.2083] Recommendation ITU-R M.2083-0 (2015), [\*IMT vision – Framework and overall objectives of the future development of IMT for 2020 and beyond\*](#).
+- [b-ONF TR-526] Open Network Foundation TR-526 (2016), [\*Applying SDN architecture to 5G slicing\*](#).
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling, and associated measurements and tests |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.4067-202105-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/Q/T-REC-Q.4067-202105-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a331adb768c2606c4c42b6927a71635dfbc1d781
--- /dev/null
+++ b/marked/Q/T-REC-Q.4067-202105-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:92f0970c1093c8300b29a3bd178cc3ef14075c93538da3043b15ce0a1d8e77ad
+size 15509
diff --git a/marked/Q/T-REC-Q.4067-202105-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.4067-202105-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2585edab110a1df8ff9f636903e1b13280ccbfda
--- /dev/null
+++ b/marked/Q/T-REC-Q.4067-202105-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5c17359bdc002ff65ca8303c0bbee4fc5e9e3b5a78247d0bd146ea55b66047d8
+size 6147
diff --git a/marked/Q/T-REC-Q.4067-202105-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg b/marked/Q/T-REC-Q.4067-202105-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a51e670a11c9b2ce4406ada7fda598e2370e1b29
--- /dev/null
+++ b/marked/Q/T-REC-Q.4067-202105-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:18af3c36be56f17a8571b93367a944e645237e70d2152784a33241bf83b2fa0c
+size 32641
diff --git a/marked/Q/T-REC-Q.4067-202105-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg b/marked/Q/T-REC-Q.4067-202105-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fce94f898644c8958a4250f5887c6a21f829a03e
--- /dev/null
+++ b/marked/Q/T-REC-Q.4067-202105-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:48248bc19fa8ffdbd880859515bf41e23921c98b2b6e77df4826907923cfb148
+size 51692
diff --git a/marked/Q/T-REC-Q.4067-202105-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4067-202105-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..7612dfea47517d141740fdccd28855fe1f09c417
--- /dev/null
+++ b/marked/Q/T-REC-Q.4067-202105-I_PDF-E/raw.md
@@ -0,0 +1,528 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.4067**
+
+(05/2021)
+
+SERIES Q: SWITCHING AND SIGNALLING, AND
+ASSOCIATED MEASUREMENTS AND TESTS
+
+Testing specifications – Testing specifications for
+IMT-2020 and IoT
+
+---
+
+**Signalling requirements for the virtualized
+network function lifecycle management in a
+testing environment**
+
+Recommendation ITU-T Q.4067
+
+# ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS**
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+| Testing specifications for next generation networks | Q.3900–Q.3999 |
+| Testing specifications for SIP-IMS | Q.4000–Q.4039 |
+| Testing specifications for Cloud computing | Q.4040–Q.4059 |
+| Testing specifications for IMT-2020 and IoT | Q.4060–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.4067
+
+# Signalling requirements for the virtualized network function lifecycle management in a testing environment
+
+## Summary
+
+Recommendation ITU-T Q.4067 specifies the process and signalling requirements for virtualized network function (VNF) lifecycle management in a testing environment by architecturally adding the testing platform in the network functions virtualization (NFV) framework. The signalling focuses on the interface between the VNF instantiation functional component in a testing platform and the network functions virtualization orchestrator (NFVO) functional component in management and orchestration (MANO).
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|----------------|------------|-------------|-----------------------------------------------------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.4067 | 2021-05-14 | 11 | 11.1002/1000/14610 |
+
+## Keywords
+
+Signalling requirements, testing, VNF lifecycle management.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at .
+
+© ITU 2021
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|------------------------------------------------------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 3.2 Terms defined in this Recommendation..... | 1 |
+| 4 Abbreviations and acronyms ..... | 1 |
+| 5 Conventions ..... | 2 |
+| 6 Overview of VNF lifecycle management in a testing environment ..... | 2 |
+| 6.1 Problem statement ..... | 2 |
+| 6.2 Signalling architecture..... | 2 |
+| 6.3 Interface requirements of Stn ..... | 3 |
+| 7 Signalling requirements of the VNF lifecycle management in a testing environment ..... | 3 |
+| 7.1 Message type ..... | 3 |
+| 7.2 Message format ..... | 4 |
+| Bibliography..... | 9 |
+
+
+
+# Recommendation ITU-T Q.4067
+
+## Signalling requirements for the virtualized network function lifecycle management in a testing environment
+
+# 1 Scope
+
+The scope of this Recommendation consists of:
+
+- Overview of virtualized network function (VNF) lifecycle management in a testing environment;
+- Signalling requirements of VNF lifecycle management in a testing environment.
+
+# 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.3321] Recommendation ITU-T Y.3321 (2015), *Requirements and capability framework for NICE implementation making use of software-defined networking technologies*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following term defined elsewhere:
+
+**3.1.1 virtualized network function** [ITU-T Y.3321]: A network function whose functional software is decoupled from hardware, and runs on virtual machine(s).
+
+## 3.2 Terms defined in this Recommendation
+
+None.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|------|------------------------------------------------|
+| GUI | Graphical User Interface |
+| ID | Identity |
+| MANO | Management and Orchestration |
+| NFV | Network Functions Virtualization |
+| NFVI | Network Function Virtualization Infrastructure |
+| NFVO | Network Functions Virtualization Orchestrator |
+| SCTP | Stream Control Transmission Protocol |
+| TCP | Transmission Control Protocol |
+
+| | |
+|-------|-----------------------------------------|
+| TLS | Transport Layer Security |
+| UDP | User Datagram Protocol |
+| vBRAS | virtual Broadband Remote Access Server |
+| vEPC | virtual Evolved Packet Core |
+| vFW | virtual Firewall |
+| VIM | Virtualized Infrastructure Manager |
+| VNF | Virtualized Network Function |
+| VNFD | Virtualized Network Function Descriptor |
+| VNFM | Virtualized Network Function Manager |
+| XML | Extensible Markup Language |
+
+## 5 Conventions
+
+In this Recommendation:
+
+In the body of this Recommendation and its appendixes, 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;
+
+[A]: indicates that the parameter A is optional;
+
+\*: indicates that the parameter may be multiple items.
+
+# 6 Overview of VNF lifecycle management in a testing environment
+
+## 6.1 Problem statement
+
+According to the definition in [b-ETSI GS NFV-IFA 011], each virtualized network function (VNF) has a specific virtualized network function manager (VNFM) to be responsible for its lifecycle management in a production environment. Even if the VNFs from different vendors have the same functionality, their respective VNFMs are not the same. From the perspective of operators, it is too redundant and inefficient to use different interfaces and signalling to test different VNFs. As an orchestrator, the network functions virtualization orchestrator (NFVO) can interact with different VNFMs to achieve the orchestration of network services. Therefore, operators can build a testing platform to connect with NFVO and realize the lifecycle management of different VNFs through a uniform interface. This mechanism can shield the difference of different VNFMs and achieve the unified testing management.
+
+The testing platform contains multiple functional components, such as a graphical user interface (GUI) functional component, a VNF instantiation functional component, a test case management functional component, etc. This Recommendation defines the signalling between the VNF instantiation functional component in a testing platform and a NFVO functional component in management and orchestration (MANO).
+
+## 6.2 Signalling architecture
+
+The VNF lifecycle management signalling architecture in a testing environment is shown in Figure 6-1. A testing platform is used to test the function and performance of VNF via a VNF
+
+instantiation functional component, such as a virtual evolved packet core (vEPC), a virtual firewall (vFW), a virtual broadband remote access server (vBRAS), etc.
+
+The functions and reference points of NFVO, VNFM, virtualized infrastructure manager (VIM), and network functions virtualization infrastructure (NFVI) are defined in [b-ETSI GS NFV 002]. Besides those, the VNF instantiation functional component exchanges the necessary information with NFVO functional component to accomplish the operation of VNF instance in its lifecycle time in the testing environment automatically.
+
+
+
+Q.4067(21)\_F6-1
+
+Figure 6-1: The VNF lifecycle management signalling architecture in a testing environment. The diagram shows a 'Testing platform' on the left containing 'VNF instantiation' and a box with 'vBRAS', 'vFW', 'vEPC', and '...' (representing other VNFs) on top of 'NFVI'. On the right is 'NFV-MANO' containing 'NFVO', 'VNFM', and 'VIM'. A red line labeled 'Stn' connects 'VNF instantiation' to 'NFVO'. Other lines connect the VNF box to 'VNFM' and 'NFVI' to 'VIM'.
+
+**Figure 6-1 – The VNF lifecycle management signalling architecture in a testing environment**
+
+## 6.3 Interface requirements of Stn
+
+The Stn interface presented in Figure 6-1 is used to exchange information to perform VNF lifecycle management functionality in a testing environment.
+
+The Stn interface permits the interaction between a VNF instantiation functional component and a NFVO functional component. The NFVO functional component receives the VNF lifecycle management request from the VNF instantiation functional component. If it fails, the VNF instantiation functional component sends the failure message to the NFVO functional component.
+
+# 7 Signalling requirements of the VNF lifecycle management in a testing environment
+
+## 7.1 Message type
+
+For the VNF lifecycle management in a testing environment, the message types presented in Figure 7-1 should be followed.
+
+
+
+Q.4067(21)\_F7-1
+
+Figure 7-1: Messages of the VNF lifecycle management in the testing environment. This sequence diagram shows interactions between 'VNF instantiation' (top) and 'NFVO' (bottom). The messages are: 1. VNF on-boarding request (solid arrow down), 2. VNF on-boarding response (dashed arrow up), 3. VNF instantiation request (solid arrow down), 4. VNF instantiation response (dashed arrow up), 5. VNF updating request (solid arrow down), 6. VNF updating response (dashed arrow up), 7. VNF query request (solid arrow down), 8. VNF query response (dashed arrow up), 9. VNF termination request (solid arrow down), 10. VNF termination response (dashed arrow up), 11. VNF package deletion request (solid arrow down), 12. VNF package deletion response (dashed arrow up).
+
+**Figure 7-1 – Messages of the VNF lifecycle management in the testing environment**
+
+As depicted in Figure 7-1, all the message interactions between the VNF instantiation functional component and NFVO functional component are in request and response mode. The request messages include VNF on-boarding, VNF instantiation, VNF updating, VNF query, VNF termination and VNF package deletion. The response message from the NFVO functional component contains the handing results of the corresponding requests and parameters.
+
+Detailed descriptions of the message pairs are as follows:
+
+- 1) VNF on-boarding: used for uploading the VNF package, including VNF image file, VNFD, VNF information file including VNF type and resource information, VNF service configuration script file and VNF manifest file, as defined in [b-ETSI GS NFV-IFA 011].
+- 2) VNF instantiation: used for instantiating the VNF, which is not in use.
+- 3) VNF updating: used for updating the status, information and scaling of the current VNF instance.
+- 4) VNF query: used for querying the status of the current VNF instance.
+- 5) VNF termination: used for terminating the current VNF instance.
+- 6) VNF package deletion: used for deleting the VNF package when it is disabled and not in use.
+
+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) transmission control protocol (TCP), user datagram protocol (UDP), stream control transmission protocol (SCTP), transport layer security (TLS), etc. All of the messages are in the message header and message body format.
+
+The message format is described in Figure 7-2.
+
+
+
+| | | | |
+|--------------|----------------|----------------|--------------|
+| Message type | Message length | Transaction ID | Message body |
+|--------------|----------------|----------------|--------------|
+
+Message header
+
+Q.4067(21)\_F7-2
+
+Figure 7-2 – Message composition diagram showing a message structure with a header and a body.
+
+**Figure 7-2 – Message composition**
+
+The message header field should contain the following information:
+
+- 1) Message type: uniquely specifies the type of the message;
+- 2) Message length: specifies the length of the message body, which comes right after the message header;
+- 3) 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 content of the message.
+
+## 7.2 Message format
+
+### 7.2.1 VNF on-boarding message and response message
+
+The VNF on-boarding request (OB-REQ) message, indicated by the message type in the message header field, is sent by the VNF instantiation functional component to upload the VNF package.
+
+Message format:
+
+```
+< OB-REQ-Message > ::= < Message header >
+ *{ Flow-Attribute }
+ { VNF-Package-ID }
+```
+
+Meanings and explanations:
+
+- 1) Flow-Attribute distinguishes the network flows to be handled. This contains several fields of network flows. The type of network flow is indicated in the packet header. There may be multiple network flow attribute items.
+- 2) VNF-Package-ID uniquely specifies the installation file ID of VNF instance.
+
+The response message to the OB-REQ message is defined as the VNF on-boarding response (OB-RSP) message.
+
+The OB-RSP message, indicated by the message type in the message header field, is sent by the NFVO functional component to the VNF instantiation functional component in response to the OB-REQ message.
+
+Message format:
+
+```
+< OB-RSP-Message > ::= < Message Header >
+ { On-boarding-Result }
+ [ VNF-Package-ID ]
+```
+
+Meanings and explanations:
+
+- 1) On-boarding-Result specifies VNF on-boarding result. If the VNF on-boarding is allowed, On-boarding-Result is TRUE; if not, On-boarding-Result is FALSE.
+- 2) VNF-Package-ID uniquely specifies the installation file ID of VNF instance.
+
+### 7.2.2 VNF instantiation message and response message
+
+The VNF instantiation request (INS-REQ) message, indicated by the message type in the message header field, is sent by the VNF instantiation functional component to instantiate the VNF.
+
+Message format:
+
+```
+< INS-REQ-Message > ::= < Message header >
+ *{ Flow-Attribute }
+ { VNF-Package-ID }
+ { VNFD-ID }
+```
+
+Meanings and explanations:
+
+- 1) Flow-Attribute distinguishes the network flows to be handled. This contains several fields of network flows. The type of network flow is indicated in the packet header. There may be multiple network flow attribute items.
+- 2) VNF-Package-ID uniquely identifies the VNF package to be used to instantiate the VNF;
+- 3) VNFD-ID uniquely identifies the VNFD to be used to instantiate the VNF.
+
+The response message to the INS-REQ message is defined as the VNF instantiation response (INS-RSP) message.
+
+The INS-RSP message, indicated by the message type in the message header field, is sent by the NFVO functional component to the VNF instantiation functional component in response to the INS-REQ message. This message shows the handling results of the INS-REQ message.
+
+Message format:
+
+```
+< INS-RSP-Message > ::= < Message Header >
+ { Instantiation-Result }
+ [ VNF-ID ]
+```
+
+Meanings and explanations:
+
+- 1) Instantiation-Result specifies VNF instantiation result. If the VNF instantiation is successful, Instantiation-Result is TRUE; if not, Instantiation-Result is FALSE.
+- 2) VNF-ID uniquely identifies the created VNF instance.
+
+### 7.2.3 VNF updating message and response message
+
+The VNF updating request (UPD-REQ) message, indicated by the message type in the message header field, is sent by the VNF instantiation functional component to update the VNF instance.
+
+Message format:
+
+```
+< UPD-REQ-Message > ::= < Message header >
+ { VNF-ID }
+ *{ Flow-Attribute }
+ { VNF-Package-ID }
+ { VNFD-ID }
+```
+
+Meanings and explanations:
+
+- 1) VNF-ID uniquely identifies the VNF instance which needs updating.
+- 2) Flow-Attribute distinguishes the network flows to be handled. This contains several fields of network flows. The type of network flow is indicated in the packet header. There may be multiple network flow attribute items.
+- 3) VNF-Package-ID uniquely identifies the VNF package to be used to update the VNF instance;
+- 4) VNFD-ID uniquely identifies the VNFD to be used to update the VNF instance.
+
+The response message to the UPD-REQ message is defined as the VNF updating response (UPD-RSP) message.
+
+The UPD-RSP message, indicated by the message type in the message header field, is sent by the NFVO functional component to the VNF instantiation functional component in response to the UPD-REQ message. This message shows the handling results of the UPD-REQ.
+
+Message format:
+
+```
+< UPD-RSP-Message > ::= < Message Header >
+ { Updating-Result }
+ [ VNF-ID ]
+```
+
+Meanings and explanations:
+
+- 1) Updating-Result specifies VNF updating result. If the VNF instance is updated successfully, Updating-Result is TRUE; if not, Updating-Result is FALSE.
+- 2) VNF-ID uniquely identifies the updated VNF instance.
+
+### 7.2.4 VNF query message and response message
+
+The VNF query request (QUE-REQ) message, indicated by the message type in the message header field, is sent by the VNF instantiation functional component to query the VNF instance.
+
+Message format:
+
+```
+< QUE-REQ-Message > ::= < Message header >
+ { VNF-ID }
+```
+
+Meanings and explanations:
+
+- 1) VNF-ID uniquely identifies the VNF instance to be queried.
+
+The response message to the QUE-REQ message is defined as the VNF query response (QUE-RSP) message.
+
+The QUE-RSP message, indicated by the message type in the message header field, is sent by the NFVO functional component to the VNF instantiation functional component in response to the QUE-REQ message. This message shows the handling results of the QUE-REQ message.
+
+Message format:
+
+```
+< QUE-RSP-Message > ::= < Message Header >
+ { Query-Result }
+ [ VNF-ID ]
+ [ VNF-Package-ID ]
+ [ VNFD-ID ]
+```
+
+Meanings and explanations:
+
+- 1) Query-Result specifies VNF query result. If the VNF instance is queried successfully, Query-Result is TRUE; if not, Query-Result is FALSE.
+- 2) VNF-ID uniquely identifies the queried VNF instance.
+- 3) VNF-Package-ID uniquely identifies the queried VNF package of the VNF instance.
+- 4) VNFD-ID uniquely identifies the queried VNFD of the VNF instance.
+
+### 7.2.5 VNF termination message and response message
+
+The VNF deletion request (TER-REQ) message, indicated by the message type in the message header field, is sent by the VNF instantiation functional component to terminate the VNF instance.
+
+Message format:
+
+```
+< TER-REQ-Message > ::= < Message header >
+ { VNF-ID }
+```
+
+Meanings and explanations:
+
+- 1) VNF-ID uniquely identifies the VNF instance to be terminated.
+
+The response message to the TER-REQ message is defined as the VNF termination response (TER-RSP) message.
+
+The TER-RSP message, indicated by the message type in the message header field, is sent by the NFVO functional component to the VNF instantiation functional component in response to the TER-REQ message. This message shows the handling results of the TER-REQ message.
+
+Message format:
+
+```
+< TER-RSP-Message > ::= < Message Header >
+ { Termination-Result }
+ [ VNF-ID ]
+```
+
+Meanings and explanations:
+
+- 1) Termination-Result specifies VNF termination result. If the VNF instance is terminated successfully, Termination-Result is TRUE; if not, Termination-Result is FALSE.
+- 2) VNF-ID uniquely identifies the terminated VNF instance.
+
+### 7.2.6 VNF package deletion message and response message
+
+The VNF package deletion request (PAD-REQ) message, indicated by the message type in the message header field, is sent by the VNF instantiation functional component to delete the VNF package.
+
+Message format:
+
+```
+< PAD-REQ-Message > ::= < Message header >
+ { VNF-Package-ID }
+```
+
+Meanings and explanations:
+
+- 1) VNF-Package-ID uniquely identifies the VNF package to be deleted.
+
+The response message to the PAD-REQ message is defined as the VNF package deletion response (PAD-RSP) message.
+
+The PAD-RSP message, indicated by the message type in the message header field, is sent by the NFVO functional component to the VNF instantiation functional component in response to the PAD-REQ message. This message shows the handling results of the PAD-REQ message.
+
+Message format:
+
+```
+< PAD-RSP-Message > ::= < Message Header >
+ { VNF-Package-Deletion-Result }
+ [ VNF-Package-ID ]
+```
+
+Meanings and explanations:
+
+- 1) VNF-Package-Deletion-Result specifies VNF package deletion result. If the VNF package is deleted successfully, VNF-Package-Deletion-Result is TRUE; if not, VNF-Package-Deletion-Result is FALSE.
+- 2) VNF-Package-ID uniquely identifies the deleted VNF package.
+
+## Bibliography
+
+- [b-ETSI GS NFV-IFA 011] ETSI GS NFV-IFA 011 V4.1.1 (2020), *Network Functions Virtualisation (NFV) Release 4; Management and Orchestration; VNF Descriptor and VNF Packaging Specification.*
+- [b-ETSI GS NFV 002] ETSI GS NFV 002 V1.2.1(2014), *Network Functions Virtualisation (NFV); Architectural Framework.*
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling, and associated measurements and tests |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/052828841894e42527af88a5b40c01b6_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/052828841894e42527af88a5b40c01b6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dae4fcccad75fb3da922e53c9e6d9cbe3f6ec698
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/052828841894e42527af88a5b40c01b6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6029ab8f774f1b6ff34e5eef98319bf0bdb8730ffacff41f9c94d8d1a382b92f
+size 11742
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..400aa35c04f7fdf16d20bcdaedaf669e218913d4
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6b4792574b9dc7b5a2c41d3a7e647408c707965835d70e023a12f8e5037e5ffd
+size 7298
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/0ab9a68225dbbb7b10a942dd72725e97_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/0ab9a68225dbbb7b10a942dd72725e97_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..eb50eacce3dba9a293eef057b4d4f63899965137
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/0ab9a68225dbbb7b10a942dd72725e97_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:21aa368099aafe5d564caf8337f8bfe29a3bf0f1c6cca9cfa982953bf5178101
+size 25737
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8b0c53c3b60d277193ea81bf11298f29e55df58b
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b7a776ef294d9f58f37c3d34ed53c4f15594eccefde35a6c4d22d05086f4b373
+size 13330
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/488003921de6c92bcf32ca46b1dc6975_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/488003921de6c92bcf32ca46b1dc6975_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5aa678259b4671495e26766effd47f667c0ead94
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/488003921de6c92bcf32ca46b1dc6975_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:42d254559aab3d06bf65c9ffbd8d3132a82b122c3fd1585ead624351ce9cd603
+size 10685
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/4af57c86e477d0a9768ad67205a5a458_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/4af57c86e477d0a9768ad67205a5a458_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1053b5468e4c7a244de5b6c4abbefbf93659d989
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/4af57c86e477d0a9768ad67205a5a458_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:af88c6744c058ef20f8f87fc42e754ef64baaf5eed87f92e90cf021b84f4a88f
+size 24765
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/538205b91311e27e0c0d7dd5c8bbf92b_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/538205b91311e27e0c0d7dd5c8bbf92b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..adb4b472d8cfbbfb78d0da27907ed63eb7ad2e0d
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/538205b91311e27e0c0d7dd5c8bbf92b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:74d6c5aec7338a08bab9fb8586798cf40bd0e3137c87472d4c1e4b57a7f8c10e
+size 25119
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1949d1967913520a21d379918d88b5e70effc3d4
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f32b348eebcd3d44738f31027a59660edb87d40e83aabd89ca443918987a97ea
+size 63152
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/674fc7821da62db98fb7cbd53cd2fb76_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/674fc7821da62db98fb7cbd53cd2fb76_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4ca3fa4aaee8d19ee7c8cc32d67a613b4c9afb3f
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/674fc7821da62db98fb7cbd53cd2fb76_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fba4e8cd124a6f28c6d383ee627442f6363161bce1443f8d5ecd24dcdd1857df
+size 12622
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/6b6b22c2fc806e6a6596dfcd3649bf32_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/6b6b22c2fc806e6a6596dfcd3649bf32_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..401bed4e85792c531c0aaf3fb8c07b9202f66450
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/6b6b22c2fc806e6a6596dfcd3649bf32_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:287215a52c59677ae8a2fb805c91520ca8ee08abf406d24f6a1bea6f106a81b0
+size 10889
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/8e12ca90e98a93de3a5d9f254adbc810_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/8e12ca90e98a93de3a5d9f254adbc810_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ee02c7407b49ad7c04506edadb93becd9d6680b5
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/8e12ca90e98a93de3a5d9f254adbc810_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:249238656cc8d320d93133321ddc5c0d4a86e07f831d4de204418eac4c090b18
+size 13442
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/9461d066dfa719ad9b1dd2d11dc592c3_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/9461d066dfa719ad9b1dd2d11dc592c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1053b5468e4c7a244de5b6c4abbefbf93659d989
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/9461d066dfa719ad9b1dd2d11dc592c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:af88c6744c058ef20f8f87fc42e754ef64baaf5eed87f92e90cf021b84f4a88f
+size 24765
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f7df7aed0e675e862a1de148404e511c3dce3361
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:94f47f8963c58afb7d2179c40d5dac7c05eefb508f19fe4d7bf554f4161618b8
+size 11734
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/ad6c36347e94fca1b0d1be8b0035401e_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/ad6c36347e94fca1b0d1be8b0035401e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1053b5468e4c7a244de5b6c4abbefbf93659d989
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/ad6c36347e94fca1b0d1be8b0035401e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:af88c6744c058ef20f8f87fc42e754ef64baaf5eed87f92e90cf021b84f4a88f
+size 24765
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b054f63cb756eb12101d76f1db34e5c44b386a02
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2c8ab5d0b52e7f6c0494e2d37ff7d20a7746fa36f148041f0cbe967088a7810c
+size 108519
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/b21fbf2040002a2bcda79d57ee476460_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/b21fbf2040002a2bcda79d57ee476460_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fcb9fb62377d5a8ab78d5f5437b198ed8934212d
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/b21fbf2040002a2bcda79d57ee476460_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f631257b5cbd64aa9a881b0f2ebab5fbca8b51b0deff7202c467c89b8d6d2b3b
+size 25667
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/c9c04560f9f5cb3989786d9a574e73a6_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/c9c04560f9f5cb3989786d9a574e73a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b8c312db5857a80a29475ebf26633854e850a441
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/c9c04560f9f5cb3989786d9a574e73a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8fd84392f8da5df40cbcf4e3ded1432a78c27ae442b71dc0035a43c7ecce199b
+size 24412
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..99b274c14117bd8a233ab7326a5f5def39387be5
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fff3a5f1f375a280e02f25459b4afd8a7526d3f549663672cdd407b0eaaa5c8f
+size 13301
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..50536d4bbbd55cd253f6a2d5536b89191e98071d
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a3d4251c64e0891a5aa20a6b2d64ca428c558fd5ade2dc8b046bc64a4c4498af
+size 76465
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/e04fc3d761ae4568a8308bd74b8b150f_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/e04fc3d761ae4568a8308bd74b8b150f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5be4a675abfd210c959f7d243c767ad8f1e76312
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/e04fc3d761ae4568a8308bd74b8b150f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:51108285190ff8c241e7170ac0b0496f41ec0d733945ab1100d6feee056450fe
+size 12605
diff --git a/marked/Q/T-REC-Q.4069-202209-I_PDF-E/ff8dab4f7e2c82e0852b448b24d50415_img.jpg b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/ff8dab4f7e2c82e0852b448b24d50415_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..efbe442a71dc259a89691de0336adaee170721d4
--- /dev/null
+++ b/marked/Q/T-REC-Q.4069-202209-I_PDF-E/ff8dab4f7e2c82e0852b448b24d50415_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1974803ab26bcce4a25fd94c495b3744c0bcaa2534144a1ffdb53bb1100d48da
+size 25691
diff --git a/marked/Q/T-REC-Q.4103-202202-I_PDF-E/19a59d6b53059ebd27b13c98793f88e0_img.jpg b/marked/Q/T-REC-Q.4103-202202-I_PDF-E/19a59d6b53059ebd27b13c98793f88e0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7b950c9eff8ff92181e4075111035e73fb3782e9
--- /dev/null
+++ b/marked/Q/T-REC-Q.4103-202202-I_PDF-E/19a59d6b53059ebd27b13c98793f88e0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ccee73ddde4be0114ae524c3b636ec6901b522b94ea8958824af3e035d416fe9
+size 28332
diff --git a/marked/Q/T-REC-Q.4103-202202-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/Q/T-REC-Q.4103-202202-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..02c867db247b73a15587957467b2922ca0b6db76
--- /dev/null
+++ b/marked/Q/T-REC-Q.4103-202202-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e06becb0e1455c118f5723a2d03305113ce40e113ee9ae5d7f4e43b70f1a9f4
+size 6126
diff --git a/marked/Q/T-REC-Q.4103-202202-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg b/marked/Q/T-REC-Q.4103-202202-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3f65630cc9c48e10f21f6e1f86a7b5bb86bc33d9
--- /dev/null
+++ b/marked/Q/T-REC-Q.4103-202202-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:602d86505a61ea9f6c42263ebebffbc430b58601bcd93865fe9d1d0555ee2774
+size 38910
diff --git a/marked/Q/T-REC-Q.4103-202202-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg b/marked/Q/T-REC-Q.4103-202202-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..58e3ab5f8a6d1dc68929950b64d1cfc380d50c98
--- /dev/null
+++ b/marked/Q/T-REC-Q.4103-202202-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:93cac88469f6d53d031666bdcffd335394d12ef6b73b04fa274602c76d5795c3
+size 21918
diff --git a/marked/Q/T-REC-Q.4103-202202-I_PDF-E/90ddf538ef276510e2b631f7b96654e6_img.jpg b/marked/Q/T-REC-Q.4103-202202-I_PDF-E/90ddf538ef276510e2b631f7b96654e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..01008ef2724cfedeb2bceee29963e1dd45d4da33
--- /dev/null
+++ b/marked/Q/T-REC-Q.4103-202202-I_PDF-E/90ddf538ef276510e2b631f7b96654e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ff3f09be53d6c3c519d390327634c62aaec7964bf661e42ed2737b08c267b7ec
+size 28371
diff --git a/marked/Q/T-REC-Q.4103-202202-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg b/marked/Q/T-REC-Q.4103-202202-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ba3842cc95d9a4a15fe0e6e101fb048d3df7356d
--- /dev/null
+++ b/marked/Q/T-REC-Q.4103-202202-I_PDF-E/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:53b28d5541726bf05873aaba7bc4c5a83a67a07f331747e1c02e2eb54ac0ff14
+size 32060
diff --git a/marked/Q/T-REC-Q.4103-202202-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4103-202202-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..fd11d46230961df3a3573b269f0f946cd2baf95d
--- /dev/null
+++ b/marked/Q/T-REC-Q.4103-202202-I_PDF-E/raw.md
@@ -0,0 +1,883 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.4103**
+
+(02/2022)
+
+SERIES Q: SWITCHING AND SIGNALLING, AND
+ASSOCIATED MEASUREMENTS AND TESTS
+
+Protocols and signalling for peer-to-peer communications
+
+---
+
+**Hybrid peer-to-peer communications: Overlay
+management protocol**
+
+Recommendation ITU-T Q.4103
+
+ITU-T
+
+
+
+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 white, bold, sans-serif font superimposed on the globe.
+
+ITU logo
+
+# ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS**
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100–Q.4139 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000–Q.5049 |
+| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050–Q.5069 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## Recommendation ITU-T Q.4103
+
+# Hybrid peer-to-peer communications: Overlay management protocol
+
+## Summary
+
+Recommendation ITU-T Q.4103 specifies a hybrid peer-to-peer overlay network management protocol that runs on the interface between a hybrid peer and a hybrid overlay management server. This protocol provides management functionalities such as creation, removal, retrieval, and update, and describes the behaviour of protocols including the specifications of protocol messages.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.4103 | 2022-02-13 | 11 | 11.1002/1000/14924 |
+
+## Keywords
+
+Hybrid peer-to-peer, overlay management, overlay network, protocol.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at .
+
+© ITU 2022
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|----------------------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere..... | 1 |
+| 3.2 Terms defined in this Recommendation..... | 2 |
+| 4 Abbreviations and acronyms ..... | 2 |
+| 5 Conventions ..... | 2 |
+| 6 Resource element types and message syntax of HOMP..... | 2 |
+| 6.1 Resource elements..... | 2 |
+| 6.2 Messages syntaxes..... | 5 |
+| 7 Protocol operations and information flows..... | 15 |
+| 7.1 Hybrid overlay network management ..... | 15 |
+| 7.2 Hybrid overlay peer management ..... | 18 |
+| Bibliography..... | 21 |
+
+
+
+## Recommendation ITU-T Q.4103
+
+# Hybrid peer-to-peer communications: Overlay management protocol
+
+# 1 Scope
+
+This Recommendation describes the overlay management protocol for hybrid peer-to-peer communications as follows:
+
+- protocol elements;
+- protocol messages and its parameters;
+- protocol behaviours including information flow.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions that, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T Q.4100] Recommendation ITU-T Q.4100 (2020), *Hybrid peer-to-peer communications: Functional architecture*.
+- [ITU-T Q.4101] Recommendation ITU-T Q.4101 (2021), *Hybrid peer-to-peer communications: Tree and data recovery procedures*.
+- [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
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 hybrid overlay network** [ITU-T Q.4100]: A peer-to-peer overlay network in which participating peers exchange data using the pull and push method. The hybrid overlay network also provides a way to organize and maintain a tree-style path for pushing data to all peers without loops, as well as fetching data from other peers simultaneously.
+
+**3.1.2 hybrid peer** [ITU-T Q.4100]: A peer capable of exchanging data using mesh-based and tree-based methods running over a hybrid overlay network.
+
+**3.1.3 overlay network** [b-ITU-T X.1162]: An overlay network is a virtual network that runs on top of another network. Like any other network, the overlay network comprises a set of nodes and links between them. Because the links are logical ones, they may correspond to many physical links of the underlying network.
+
+**3.1.4 peer** [b-ITU-T X.1161]: Communication node on a P2P network that functions simultaneously as both "client" and "server" to the other nodes on the network.
+
+**3.1.5 peer-to-peer (P2P)** [b-ITU-T Y.2206]: A system is considered to be P2P if the nodes of the system share their resources in order to provide the service the system supports. The nodes in the system both provide services to other nodes and request services from other nodes.
+
+NOTE – Peer is the node in a P2P system.
+
+**3.1.6 reference point** [b-ITU-T Y.2012]: A conceptual point at the conjunction of two non-overlapping functional entities that can be used to identify the type of information passing between these functional entities.
+
+## **3.2 Terms defined in this Recommendation**
+
+None.
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|------|------------------------------------|
+| FQDN | Fully Qualified Domain Name |
+| HOMP | Hybrid Overlay Management Protocol |
+| HON | Hybrid Overlay Network |
+| HP2P | Hybrid Peer-to-Peer |
+| IoT | Internet of Things |
+| P2P | Peer-to-Peer |
+| URI | Uniform Resource Identifier |
+
+# **5 Conventions**
+
+Resource elements in clause 6.1 and fields of the message under clause 6.2 are encoded in JavaScript object notation (JSON) [IETF RFC 7159], and the grammar used in representing objects defined in this Recommendation is as follows:
+
+- "STRING", "BOOLEAN", "DICT", "LIST" and "NUMBER" types are used to indicate string, Boolean, dictionary, list and number, respectively;
+- An array of collective values are enclosed in brackets "[ ]" with values separated by commas ",";
+- Selective options are separated by a vertical bar " | ".
+
+# **6 Resource element types and message syntax of HOMP**
+
+This clause describes the message formats for the hybrid overlay management protocol (HOMP). For extensibility, HOMP is a representational state transfer (REST) architecture [b-Fielding] and messages are encoded in JavaScript object notation (JSON) [IETF RFC 7159].
+
+## **6.1 Resource elements**
+
+This clause specifies the basic resource elements to be used for conveying information regarding the activities on the overlay network.
+
+### **6.1.1 OVERLAY\_INFO**
+
+The OVERLAY\_INFO element include details about a hybrid overlay network (HON). This element contains overlay network attributes as shown in the following Table 6-1:
+
+**Table 6-1 – OVERLAY\_INFO resource element**
+
+| Keyword | Type | Description |
+|--------------------|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
+| overlay-id | STRING | overlay-id is an identifier for a specific HON. |
+| title | STRING | title is a human readable description on the HON. |
+| type | STRING | type indicates the type of the HON, and it should be one of 'core' or 'sub'. |
+| sub-type | STRING | sub-type indicates the shape of the overlay topology, and it should be one of 'tree' or 'mesh'. |
+| owner-id | STRING | owner-id indicates the peer identifier who created the HON. |
+| expires | NUMBER | expires indicates the time that the HON will be removed in seconds. |
+| status | OVERLAY_STATUS | status indicates the status of the HON such as the number of peers, peer list, and human readable status like 'active', 'terminated', etc. |
+| description | STRING | descriptions provide more detailed information regarding the HON. |
+| heartbeat-interval | NUMBER | heartbeat-interval indicates the interval for checking the aliveness of peers. |
+| heartbeat-timeout | NUMBER | heartbeat-timeout indicates when a peer decides a corresponding peer is no longer alive. |
+| auth | OVERLAY_AUTH | auth includes the authentication information to be used for access control to the HON. |
+| cr-policy | CR_POLICY | cr-policy includes caching and recovery policies for the tree and data recovery policies of the HON. |
+| trans-policy | TRANS_POLICY | trans-policy includes policy regarding data broadcasting floor control. |
+
+### 6.1.2 PEER\_INFO
+
+The PEER\_INFO element includes details about peer information such as peer identifier, the network address and authentication information as shown in the following Table 6-2.
+
+**Table 6-2 – PEER\_INFO resource element**
+
+| Keyword | Type | Description |
+|---------|-----------|---------------------------------------------------------------------------------------------------|
+| peer-id | STRING | peer-id includes the identifier of a hybrid peer. |
+| Address | STRING | Address includes the network address that another peer is able to access. |
+| auth | PEER_AUTH | auth includes authentication information needed for establishing a connection among peers. |
+
+### 6.1.3 OVERLAY\_AUTH
+
+The OVERLAY\_AUTH element includes authentication details for managing the overlay network as shown in the following Table 6-3. This element is used for creating and manipulating the attributes of a hybrid overlay network.
+
+**Table 6-3 – OVERLAY\_AUTH resource element**
+
+| Keyword | Type | Description |
+|------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| type | STRING | type indicates whether it is public or not. If it is public, this value is 'open', if not, it is 'closed'. |
+| admin_key | STRING | admin_key includes the encrypted key phrase for managing the hybrid overlay network. This is used only by the owner of this HON. |
+| access_key | STRING | access_key includes the encrypted key phrase for accessing the hybrid overlay network. This value is valid when type is 'closed'. |
+| peerlist | LIST[STRING] | peerlist includes the list of peer identifiers that have access grants. This value is valid when type is 'closed'. The listed peer can access the HON without an access_key . |
+
+### 6.1.4 OVERLAY\_STATUS
+
+The OVERLAY\_STATUS element includes information to express the status of a hybrid overlay network as shown in following Table 6-4. It provides the number of peers within a particular HON, the list of peers and its status.
+
+**Table 6-4 – OVERLAY\_STATUS resource element**
+
+| Keyword | Type | Description |
+|----------------|-----------------|------------------------------------------------------------------------------------------------------------------------------|
+| num_peers | NUMBER | num_peers indicates the number of peers of the HON. |
+| peer_info_list | LIST[PEER_INFO] | peer_info_list includes the information of peers such as peer identifier, network address, etc. |
+| status | STRING | status includes human readable information regarding the status of the HON, such as 'active', 'terminated' and so on. |
+
+### 6.1.5 PEER\_STATUS
+
+The PEER\_STATUS element represents the status of a peer such as the number of primary / candidate path and the cost map that describes the routing path with other peers in detail as shown in the following Table 6-5.
+
+**Table 6-5 – PEER\_STATUS resource element**
+
+| Keyword | Type | Description |
+|-------------------|--------------|--------------------------------------------------------------------------------------------------------|
+| num_primary | NUMBER | num_primary indicates the number of current primary paths of the peer. |
+| num_out_candidate | NUMBER | num_out_candidate indicates the number of current secured outgoing candidate paths of the peer. |
+| num_in_candidate | NUMBER | num_in_candidate indicates the number of incoming candidate paths of the peer. |
+| costmap | PEER_COSTMAP | costmap includes details on the routing path of the peer. |
+
+#### 6.1.6 PEER\_COSTMAP
+
+The PEER\_COSTMAP element includes details on the paths to adjacent peers of the peer as shown in the following Table 6-6.
+
+**Table 6-6 – PEER\_COSTMAP resource element**
+
+| Keyword | Type | Description |
+|--------------------|------|-------------------------------------------------------------------------------------------------------------------------|
+| primary | LIST | primary includes the list of peer identifiers that are connected as a primary path. |
+| outgoing_candidate | LIST | outgoing_candidate includes the list of peer identifiers connected as candidate paths initiated by this peer. |
+| incoming_candidate | LIST | incoming_candidate includes the list of peer identifiers connected as candidate paths initiated by remote peers. |
+
+#### 6.1.7 PEER\_AUTH
+
+The PEER\_AUTH element includes authentication information for establishing a path with the peer as shown in the following Table 6-7. This is for preventing DoS attacks rather than authorization.
+
+**Table 6-7 – PEER\_AUTH resource element**
+
+| Keyword | Type | Description |
+|----------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------|
+| password | STRING | password includes a key phrase for authenticating an incoming connection request. The key phrase consists of alpha-numeric characters only. |
+
+NOTE – The password is randomly generated whenever the hybrid peer instance is initiated
+
+### 6.1.8 CR\_POLICY
+
+This resource element represents the caching and recovery policy of the overlay network, and all participating peer is required to obey this rule. The detailed parameters are described in Table 6-8.
+
+**Table 6-8 – CR\_POLICY resource element**
+
+| Keyword | Type | Description |
+|-------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| mN_Cache | NUMBER | mN_Cache includes the number of messages to be cached. Each peer should make the circular queue bigger than this value. If this value is 0, the circular queue is not maintained. That is, the data recovery function is not provided. |
+| mD_Cache | NUMBER | mD_Cache includes the minimum duration in seconds that each peer should maintain for each cached data. |
+| recovery-by | STRING | recovery-by parameter is used when creating an overlay network requiring lost data recovery. The value will be one of "push" or "pull". |
+
+## 6.2 Messages syntaxes
+
+This clause describes the messages for managing a hybrid overlay network to be used in the reference point R1 that is specified in [ITU-T Q.4100]. In the body of an HTTP request/response message, the following notation is used for representing the requirements on the specific parameter.
+
+- m: mandatory
+- o: optional
+- c: conditional mandatory; requirement on the parameter depends on the context of the message usages.
+
+Since the hybrid overlay management protocol runs on top of the HTTP [IETF RFC 7231], it obeys the semantics and syntaxes of the HTTP if not specifically described in this Recommendation.
+
+### 6.2.1 HybridOverlayCreation
+
+This *HybridOverlayCreation* primitive is used for creating a new hybrid overlay network. Table 6-9 describes the syntax of the request message.
+
+**Table 6-9 – Request message syntax for HybridOverlayCreation**
+
+| HTTP method | POST | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--|--|----------------|-------------|------------|-------|--------|---|------|--------|---|----------|--------|---|----------|--------|---|---------|--------|---|-------------|--------|---|--------------------|--------|---|-------------------|--------|---|------|--------------|---|-----------|-----------|---|
+| HTTP URI | http:// [HOMS-FQDN] : [port] /homs | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| BODY | overlay_info | | OVERLAY_INFO |
| keyword | type | m/o |
| title | STRING | m |
| type | STRING | m |
| sub-type | STRING | m |
| owner-id | STRING | m |
| expires | NUMBER | o |
| description | STRING | m |
| heartbeat-interval | NUMBER | m |
| heartbeat-timeout | NUMBER | m |
| auth | OVERLAY_AUTH | m |
| cr-policy | CR-POLICY | o |
| OVERLAY_INFO | | | keyword | type | m/o | title | STRING | m | type | STRING | m | sub-type | STRING | m | owner-id | STRING | m | expires | NUMBER | o | description | STRING | m | heartbeat-interval | NUMBER | m | heartbeat-timeout | NUMBER | m | auth | OVERLAY_AUTH | m | cr-policy | CR-POLICY | o |
+| OVERLAY_INFO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| title | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| type | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| sub-type | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| owner-id | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| expires | NUMBER | o | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| description | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| heartbeat-interval | NUMBER | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| heartbeat-timeout | NUMBER | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| auth | OVERLAY_AUTH | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| cr-policy | CR-POLICY | o | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+- If the *expires* field is not specified, it assumes it as 86 400 seconds (one day).
+- For preventing heartbeat storming, *heartbeat-interval* shall be bigger than 5 seconds, and *heartbeat-timeout* shall be bigger than *heartbeat-interval* x 3 seconds.
+- If *cr-policy* is not present, it means that the HON does not support data recovery.
+- If *auth* is not present, the HON is open to the public.
+
+Table 6-10 describes the syntax of the response for *HybridOverlayCreation*.
+
+**Table 6-10 – Response message syntax for HybridOverlayCreation**
+
+| HTTP response code | rsp_code | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------|--|--|----------------|-------------|------------|------------|--------|---|------|--------|---|----------|--------|---|----------|--------|---|---------|--------|---|--------------------|--------|---|-------------------|--------|---|------|--------------|---|-----------|-----------|---|
+| BODY | overlay | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | OVERLAY_INFO |
| keyword | type | m/o |
| overlay-id | STRING | m |
| type | STRING | m |
| sub-type | STRING | m |
| owner-id | STRING | m |
| expires | NUMBER | m |
| heartbeat-interval | NUMBER | m |
| heartbeat-timeout | NUMBER | m |
| auth | OVERLAY_AUTH | c |
| cr-policy | CR-POLICY | c |
| | OVERLAY_INFO | | | keyword | type | m/o | overlay-id | STRING | m | type | STRING | m | sub-type | STRING | m | owner-id | STRING | m | expires | NUMBER | m | heartbeat-interval | NUMBER | m | heartbeat-timeout | NUMBER | m | auth | OVERLAY_AUTH | c | cr-policy | CR-POLICY | c |
+| OVERLAY_INFO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| overlay-id | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| type | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| sub-type | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| owner-id | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| expires | NUMBER | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| heartbeat-interval | NUMBER | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| heartbeat-timeout | NUMBER | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| auth | OVERLAY_AUTH | c | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| cr-policy | CR-POLICY | c | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+c: If the parameter is present in the request message, this parameter must be included.
+
+- *rsp\_code* indicates the result of the request. If successful, this is 200, and it uses the appropriate HTTP response code if it fails.
+- *overlay-id* is an identifier that is created by HOMS for the creation request.
+
+### **6.2.2 HybridOverlayQuery**
+
+This *HybridOverlayQuery* primitive is used for querying detailed information of a hybrid overlay network. Table 6-11 describes the syntax of the request.
+
+**Table 6-11 – Request message syntax for HybridOverlayQuery**
+
+| HTTP method | GET | | | | | | | | | | | | | | | | |
+|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--|--|----------------|-------------|------------|------------|--------|---|-------|--------|---|-------------|--------|---|--|
+| HTTP URI | http:// [HOMS-FQDN] : [port] /homs | | | | | | | | | | | | | | | | |
+| | URI params | | | | | | | | | | | | | | | | |
+| | | URI params |
| keyword | type | m/o |
| overlay-id | STRING | o |
| title | STRING | o |
| description | STRING | o |
| URI params | | | keyword | type | m/o | overlay-id | STRING | o | title | STRING | o | description | STRING | o | |
+| URI params | | | | | | | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | | | | | | | |
+| overlay-id | STRING | o | | | | | | | | | | | | | | | |
+| title | STRING | o | | | | | | | | | | | | | | | |
+| description | STRING | o | | | | | | | | | | | | | | | |
+
+- If no params in the HTTP uniform resource identifier (URI), HOMS returns the list of HONs.
+- If *description* parameter is present, the HOMS returns the list of HONs that contains the keyword within the description of HON.
+- If *title* parameter is present, the HOMS returns the list of HONs that contains the keyword within the *title* of HON.
+
+Table 6-12 describes the syntax of the response for *HybridOverlayQuery*.
+
+**Table 6-12 – Response message syntax for HybridOverlayQuery**
+
+| HTTP response code | rsp_code | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--|--|----------------|-------------|------------|------------|--------|---|-------|--------|---|------|--------|---|----------|--------|---|----------|--------|---|---------|--------|---|--------|----------------|---|-------------|--------|---|------|--------------|---|-----------|-----------|---|--------------|--------------|---|
+| BODY | overlay[] | OVERLAY_INFO |
| keyword | type | m/o |
| overlay-id | STRING | m |
| title | STRING | m |
| type | STRING | m |
| sub-type | STRING | m |
| owner-id | STRING | m |
| expires | STRING | m |
| status | OVERLAY_STATUS | m |
| description | STRING | o |
| auth | OVERLAY_AUTH | m |
| cr-policy | CR_POLICY | c |
| trans policy | TRANS POLICY | o |
| OVERLAY_INFO | | | keyword | type | m/o | overlay-id | STRING | m | title | STRING | m | type | STRING | m | sub-type | STRING | m | owner-id | STRING | m | expires | STRING | m | status | OVERLAY_STATUS | m | description | STRING | o | auth | OVERLAY_AUTH | m | cr-policy | CR_POLICY | c | trans policy | TRANS POLICY | o |
+| OVERLAY_INFO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| overlay-id | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| title | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| type | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| sub-type | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| owner-id | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| expires | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| status | OVERLAY_STATUS | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| description | STRING | o | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| auth | OVERLAY_AUTH | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| cr-policy | CR_POLICY | c | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| trans policy | TRANS POLICY | o | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+- If the *cr-policy* of the hybrid overlay network is present, it is included in the response message.
+- *rsp\_code* indicates the result of the request. If successful, this is 200, and it uses the appropriate HTTP response code if it fails.
+- In the HTTP body, HOMS returns the list of OVERLAY\_INFO resource elements.
+
+### **6.2.3 HybridOverlayModification**
+
+This *HybridOverlayModification* primitive is used for modifying the attributes of a hybrid overlay network. Table 6-13 describes the syntax of the request. By using this primitive, an owner of the HON is capable of modifying the title, description, expires and auth.
+
+**Table 6-13 – Request message syntax for HybridOverlayModification**
+
+| HTTP method | PUT | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--|--|---------|------|-----|------------|--------|---|-------|--------|---|----------|--------|---|---------|--------|---|-------------|--------|---|------|--------------|---|--------------|--------------|---|
+| HTTP URI | http:// [HOMS-FQDN] : [port] /homs | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| BODY | overlay | | OVERLAY_INFO |
| keyword | type | m/o |
| overlay-id | STRING | m |
| title | STRING | o |
| owner-id | STRING | m |
| expires | NUMBER | o |
| description | STRING | o |
| auth | OVERLAY_AUTH | m |
| trans_policy | TRANS_POLICY | o |
| OVERLAY_INFO | | | keyword | type | m/o | overlay-id | STRING | m | title | STRING | o | owner-id | STRING | m | expires | NUMBER | o | description | STRING | o | auth | OVERLAY_AUTH | m | trans_policy | TRANS_POLICY | o |
+| OVERLAY_INFO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| overlay-id | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| title | STRING | o | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| owner-id | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| expires | NUMBER | o | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| description | STRING | o | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| auth | OVERLAY_AUTH | m | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| trans_policy | TRANS_POLICY | o | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+– In the *auth* parameter, *admin-key* is mandatory, and *access-key* and *peerlist* are optional.
+
+Table 6-14 describes the syntax of the response for *HybridOverlayModification*.
+
+**Table 6-14 – Response message syntax for HybridOverlayModification**
+
+| HTTP response code | rsp_code | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--|--|---------|------|-----|------------|--------|---|-------|--------|---|----------|--------|---|---------|--------|---|-------------|--------|---|------|--------------|---|
+| BODY | overlay | | OVERLAY_INFO |
| keyword | type | m/o |
| overlay-id | STRING | m |
| title | STRING | c |
| owner-id | STRING | m |
| expires | NUMBER | o |
| description | STRING | c |
| auth | OVERLAY_AUTH | m |
| OVERLAY_INFO | | | keyword | type | m/o | overlay-id | STRING | m | title | STRING | c | owner-id | STRING | m | expires | NUMBER | o | description | STRING | c | auth | OVERLAY_AUTH | m |
+| OVERLAY_INFO | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | | | | | | | | | | | | | | | | |
+| overlay-id | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | |
+| title | STRING | c | | | | | | | | | | | | | | | | | | | | | | | | |
+| owner-id | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | |
+| expires | NUMBER | o | | | | | | | | | | | | | | | | | | | | | | | | |
+| description | STRING | c | | | | | | | | | | | | | | | | | | | | | | | | |
+| auth | OVERLAY_AUTH | m | | | | | | | | | | | | | | | | | | | | | | | | |
+
+- If *description* is present in the attributes of the hybrid overlay network, it is included in the response message.
+- *rsp\_code* indicates the result of the request. If successful, this is 200, and it uses the appropriate HTTP response code if it fails.
+- In the *auth* parameter, *admin-key*, *access-key* and *peerlist* are mandatory if the attributes are present for the HON.
+
+### 6.2.4 HybridOverlayRemoval
+
+This *HybridOverlayRemoval* primitive is used for removing a particular hybrid overlay network. Table 6-15 describes the syntax of the request.
+
+**Table 6-15 – Request message syntax for HybridOverlayRemoval**
+
+| HTTP method | DELETE | | | | | | | | | | | | | | | | |
+|--------------------|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--|--|---------|------|-----|------------|--------|---|----------|--------|---|------|--------------|---|
+| HTTP URI | http://[HOMS-FQDN]:[port]/homs | | | | | | | | | | | | | | | | |
+| BODY | overlay | | OVERLAY_INFO |
| keyword | type | m/o |
| overlay-id | STRING | m |
| owner-id | STRING | m |
| auth | OVERLAY_AUTH | m |
| OVERLAY_INFO | | | keyword | type | m/o | overlay-id | STRING | m | owner-id | STRING | m | auth | OVERLAY_AUTH | m |
+| OVERLAY_INFO | | | | | | | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | | | | | | | |
+| overlay-id | STRING | m | | | | | | | | | | | | | | | |
+| owner-id | STRING | m | | | | | | | | | | | | | | | |
+| auth | OVERLAY_AUTH | m | | | | | | | | | | | | | | | |
+
+– In the *auth* parameter, *admin-key* is mandatory.
+
+Table 6-16 describes the syntax of the response for *HybridOverlayModification*.
+
+**Table 6-16 – Response message syntax for HybridOverlayRemoval**
+
+| HTTP response code | rsp_code | | | | | | | | | | |
+|---------------------------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--|--|---------|------|-----|------------|--------|---|
+| BODY | overlay | | OVERLAY_INFO |
| keyword | type | m/o |
| overlay-id | STRING | m |
| OVERLAY_INFO | | | keyword | type | m/o | overlay-id | STRING | m |
+| OVERLAY_INFO | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | |
+| overlay-id | STRING | m | | | | | | | | | |
+
+– *rsp\_code* indicates the result of the request. If successful, this is 200, and it uses the appropriate HTTP response code if it fails.
+
+### 6.2.5 HybridOverlayJoin
+
+This *HybridOverlayJoin* primitive is used for joining an existing hybrid overlay network. Table 6-17 describes the syntax of the request.
+
+**Table 6-17 – Request message syntax for HybridOverlayJoin**
+
+| HTTP method | POST | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|--|--|----------------|-------------|------------|------------|--------|---|---------|--------|---|----------|-----------|---|---------|--------|---|------|--------------|---|----------|---------|---|-----------|--------|---|
+| HTTP URI | http:// [HOMS-FQDN] : [port] /peer | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| BODY | overlay | | OVERLAY_INFO |
| keyword | type | m/o |
| overlay-id | STRING | m |
| type | STRING | m |
| sub-type | STRING | m |
| expires | NUMBER | o |
| auth | OVERLAY_AUTH | o |
| recovery | BOOLEAN | o |
| ticket-id | STRING | o |
| OVERLAY_INFO | | | keyword | type | m/o | overlay-id | STRING | m | type | STRING | m | sub-type | STRING | m | expires | NUMBER | o | auth | OVERLAY_AUTH | o | recovery | BOOLEAN | o | ticket-id | STRING | o |
+| OVERLAY_INFO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| overlay-id | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| type | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| sub-type | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| expires | NUMBER | o | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| auth | OVERLAY_AUTH | o | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| recovery | BOOLEAN | o | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ticket-id | STRING | o | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | peer | | PEER_INFO |
| keyword | type | m/o |
| peer-id | STRING | m |
| address | STRING | m |
| auth | PEER_AUTH | m |
| PEER_INFO | | | keyword | type | m/o | peer-id | STRING | m | address | STRING | m | auth | PEER_AUTH | m | | | | | | | | | | | | |
+| PEER_INFO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| peer-id | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| address | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| auth | PEER_AUTH | m | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+- If there is no refresh before the timer, specified in the *expires* parameter and the fields, the peer will be removed from the HON.
+- When the requesting peer is already in the hybrid overlay network, *recovery* parameter is set to be *true*.
+- When the requesting peer sends this message for refresh or recovery, *ticket-id* parameter must be present. That is, if the peer is already a member of the HON, this value must be embedded in the request message.
+
+Table 6-18 describes the syntax of the response for *HybridOverlayJoin*.
+
+**Table 6-18 – Response message syntax for HybridOverlayJoin**
+
+| HTTP response code | rsp_code | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------------|--|--|---------|------|-----|------------|--------|---|------|--------|---|----------|--------|---|---------|--------|---|--------|----------------|---|--------------|--------------|---|
+| BODY | overlay | OVERLAY_INFO |
| keyword | type | m/o |
| overlay-id | STRING | m |
| type | STRING | m |
| sub-type | STRING | m |
| expires | NUMBER | m |
| status | OVERLAY_STATUS | m |
| trans_policy | TRANS_POLICY | o |
| | OVERLAY_INFO | | | keyword | type | m/o | overlay-id | STRING | m | type | STRING | m | sub-type | STRING | m | expires | NUMBER | m | status | OVERLAY_STATUS | m | trans_policy | TRANS_POLICY | o |
+| OVERLAY_INFO | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | | | | | | | | | | | | | | | | |
+| overlay-id | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | |
+| type | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | |
+| sub-type | STRING | m | | | | | | | | | | | | | | | | | | | | | | | | |
+| expires | NUMBER | m | | | | | | | | | | | | | | | | | | | | | | | | |
+| status | OVERLAY_STATUS | m | | | | | | | | | | | | | | | | | | | | | | | | |
+| trans_policy | TRANS_POLICY | o | | | | | | | | | | | | | | | | | | | | | | | | |
+
+- *rsp\_code* indicates the result of the request. If successful, this is 200, and it uses the appropriate HTTP response code if it fails.
+- *overlay-id* is an identifier that is created by HOMS for the creation request.
+
+### **6.2.6 HybridOverlayReport**
+
+This *HybridOverlayReport* primitive is used for reporting the status of a peer. Table 6-19 describes the syntax of the request.
+
+**Table 6-19 – Request message syntax for HybridOverlayReport**
+
+| HTTP method | POST | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|------|-----|------------|-------------|-----|------------|-----------|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|--|--|---------|------|-----|---------|--------|---|------|-----------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--|--|---------|------|-----|--------|-------------|---|
+| HTTP URI | http:// [HOMS-FQDN] : [port] /peer/report | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| BODY | overlay | OVERLAY_INFO | | keyword | type | m/o | | overlay-id | string | m | |
peer | PEER_INFO | | keyword | type | m/o | | peer-id | string | m | | auth | PEER_AUTH | m | |
status | PEER_STATUS | | keyword | type | m/o | | status | PEER_STATUS | m | |
| | overlay | OVERLAY_INFO |
| keyword | type | m/o |
| overlay-id | string | m |
| OVERLAY_INFO | | | keyword | type | m/o | overlay-id | string | m | peer | PEER_INFO |
| keyword | type | m/o |
| peer-id | string | m |
| auth | PEER_AUTH | m |
| PEER_INFO | | | keyword | type | m/o | peer-id | string | m | auth | PEER_AUTH | m | status | PEER_STATUS |
| keyword | type | m/o |
| status | PEER_STATUS | m |
| PEER_STATUS | | | keyword | type | m/o | status | PEER_STATUS | m |
+| overlay | OVERLAY_INFO |
| keyword | type | m/o |
| overlay-id | string | m |
| OVERLAY_INFO | | | keyword | type | m/o | overlay-id | string | m | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| OVERLAY_INFO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| overlay-id | string | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| peer | PEER_INFO |
| keyword | type | m/o |
| peer-id | string | m |
| auth | PEER_AUTH | m |
| PEER_INFO | | | keyword | type | m/o | peer-id | string | m | auth | PEER_AUTH | m | | | | | | | | | | | | | | | | | | | | | | | |
+| PEER_INFO | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| peer-id | string | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| auth | PEER_AUTH | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| status | PEER_STATUS |
| keyword | type | m/o |
| status | PEER_STATUS | m |
| PEER_STATUS | | | keyword | type | m/o | status | PEER_STATUS | m | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| PEER_STATUS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| status | PEER_STATUS | m | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+Table 6-20 describes the syntax of the response for *HybridOverlayReport*.
+
+**Table 6-20 – Response message syntax for HybridOverlayReport**
+
+| HTTP response code | rsp_code | | | | | | | | | | |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------|--|--|----------------|-------------|------------|-------------------|--------|----------|
+| BODY | overlay | | | | | | | | | | |
+| | | OVERLAY_INFO |
| keyword | type | m/o |
| overlay-id | STRING | o |
| | OVERLAY_INFO | | | keyword | type | m/o | overlay-id | STRING | o |
+| OVERLAY_INFO | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | |
+| overlay-id | STRING | o | | | | | | | | | |
+| | | | | | | | | | | | |
+
+- *rsp\_code* indicates the result of the request. If successful, this is 200, and it uses appropriate HTTP response code if it fails.
+- If *overlay-id* is not included, *overlay* is also emitted. That is, the HTTP body of the response may be empty.
+
+### 6.2.7 HybridOverlayRefresh
+
+This *HybridOverlayRefresh* primitive is used for continuous stay in the overlay network by a peer. A peer needs to send this message periodically to prevent it from being removed from the peer list of a specific overlay network due to timeout. Table 6-21 describes the syntax of the request.
+
+**Table 6-21 – Request message syntax for HybridOverlayRefresh**
+
+| HTTP method | PUT | | | | | | | | | | | | | | | | |
+|--------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------|--|--|----------------|-------------|------------|-------------------|--------|----------|----------------|--------|----------|-------------|--------------|----------|
+| HTTP URI | http:// [HOMS-FQDN] : [port] /peer | | | | | | | | | | | | | | | | |
+| BODY | overlay | | | | | | | | | | | | | | | | |
+| | | OVERLAY_INFO |
| keyword | type | m/o |
| overlay-id | STRING | m |
| expires | NUMBER | o |
| auth | OVERLAY_AUTH | o |
| | OVERLAY_INFO | | | keyword | type | m/o | overlay-id | STRING | m | expires | NUMBER | o | auth | OVERLAY_AUTH | o |
+| OVERLAY_INFO | | | | | | | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | | | | | | | |
+| overlay-id | STRING | m | | | | | | | | | | | | | | | |
+| expires | NUMBER | o | | | | | | | | | | | | | | | |
+| auth | OVERLAY_AUTH | o | | | | | | | | | | | | | | | |
+| | peer | | | | | | | | | | | | | | | | |
+| | | PEER_INFO |
| keyword | type | m/o |
| peer-id | STRING | m |
| address | STRING | m |
| auth | PEER_AUTH | m |
| | PEER_INFO | | | keyword | type | m/o | peer-id | STRING | m | address | STRING | m | auth | PEER_AUTH | m |
+| PEER_INFO | | | | | | | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | | | | | | | |
+| peer-id | STRING | m | | | | | | | | | | | | | | | |
+| address | STRING | m | | | | | | | | | | | | | | | |
+| auth | PEER_AUTH | m | | | | | | | | | | | | | | | |
+
+Table 6-22 describes the syntax of the response for *HybridOverlayRefresh*.
+
+**Table 6-22 – Response message syntax for HybridOverlayRefresh**
+
+| HTTP response code | rsp_code | | | | | | | | | | | | | |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|--|----------------|----------------|-------------|------------|------------|--------|---|---------|--------|---|
+| BODY | overlay | | OVERLAY_INFO |
| keyword | type | m/o |
| overlay-id | STRING | m |
| expires | NUMBER | m |
| OVERLAY_INFO | | | keyword | type | m/o | overlay-id | STRING | m | expires | NUMBER | m |
+| | OVERLAY_INFO | | | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | | | | |
+| overlay-id | STRING | m | | | | | | | | | | | | |
+| expires | NUMBER | m | | | | | | | | | | | | |
+| peer | | PEER_INFO |
| keyword | type | m/o |
| peer-id | STRING | m |
| PEER_INFO | | | keyword | type | m/o | peer-id | STRING | m | | | | |
+| PEER_INFO | | | | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | | | | |
+| peer-id | STRING | m | | | | | | | | | | | | |
+
+– *rsp\_code* indicates the result of the request. If successful, this is 200, and it uses the appropriate HTTP response code if it fails.
+
+### **6.2.8 HybridOverlayLeave**
+
+This *HybridOverlayLeave* primitive is used for leaving an overlay network explicitly for graceful leaving. If a peer leaves without sending this message, HOMS will remove it after a timeout or another peer can detect the disconnection of the primary path with the leaving peer. If the peer detects the event, it initiates the tree recovery procedures specified in [ITU-T Q.4101]. On successful recovery of the network, each peer sends a *HybridOverlayReport* message to HOMS.
+
+Table 6-23 describes the syntax of the request.
+
+**Table 6-23 – Request message syntax for HybridOverlayLeave**
+
+| HTTP method | DELETE | | | | | | | | | | | | | |
+|--------------------|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--|--|----------------|-------------|------------|------------|--------|---|------|--------------|---|
+| HTTP URI | http:// [HOMS-FQDN] : [port]/peer | | | | | | | | | | | | | |
+| BODY | overlay | | OVERLAY_INFO |
| keyword | type | m/o |
| overlay-id | STRING | m |
| auth | OVERLAY_AUTH | c |
| OVERLAY_INFO | | | keyword | type | m/o | overlay-id | STRING | m | auth | OVERLAY_AUTH | c |
+| OVERLAY_INFO | | | | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | | | | |
+| overlay-id | STRING | m | | | | | | | | | | | | |
+| auth | OVERLAY_AUTH | c | | | | | | | | | | | | |
+| | peer | | PEER_INFO |
| keyword | type | m/o |
| peer-id | STRING | m |
| auth | PEER_AUTH | m |
| PEER_INFO | | | keyword | type | m/o | peer-id | STRING | m | auth | PEER_AUTH | m |
+| PEER_INFO | | | | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | | | | |
+| peer-id | STRING | m | | | | | | | | | | | | |
+| auth | PEER_AUTH | m | | | | | | | | | | | | |
+
+– If the overlay network is public, *auth* field is not included.
+Table 6-24 describes the syntax of the response for *HybridOverlayLeave*.
+
+**Table 6-24 – Response message syntax for HybridOverlayLeave**
+
+| HTTP response code | rsp_code | | | | | | | | | | |
+|---------------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--|--|----------------|-------------|------------|------------|--------|---|
+| BODY | overlay | | OVERLAY_INFO |
| keyword | type | m/o |
| overlay-id | STRING | m |
| OVERLAY_INFO | | | keyword | type | m/o | overlay-id | STRING | m |
+| OVERLAY_INFO | | | | | | | | | | | |
+| keyword | type | m/o | | | | | | | | | |
+| overlay-id | STRING | m | | | | | | | | | |
+
+– *rsp\_code* indicates the result of the request. If successful, this is 200, and it uses the appropriate HTTP response code if it fails.
+
+# 7 Protocol operations and information flows
+
+The hybrid overlay management protocol (HOMP) consists of two parts; hybrid overlay network management and hybrid overlay peer management.
+
+## 7.1 Hybrid overlay network management
+
+This clause describes the functionalities for managing a hybrid overlay network such as creation, query, modification and deletion.
+
+### 7.1.1 Creation of hybrid overlay network
+
+As shown in Figure 7-1, a peer sends the *HybridOverlayCreation* request message to HOMS to create a new hybrid overlay network. The peer keeps ownership of the network, and it has the privilege to update or delete it.
+
+
+
+A sequence diagram illustrating the information flow for hybrid overlay network creation. It features three main entities: an 'Overlay network owner' (represented by a person icon), a 'Peer', and 'HOMS'. The interaction begins with the 'Overlay network owner' sending a 'Create overlay' message (dashed line) to the 'Peer'. The 'Peer' then sends a '1. HybridOverlayCreation' request (solid line) to 'HOMS'. 'HOMS' responds with '2. 200 OK' (solid line). A dashed box labeled 'w. overlay-id' is shown below the '2. 200 OK' message, indicating a return value. A legend at the bottom indicates that dashed lines represent 'User behaviour' and solid lines represent 'Protocol behaviour'. The diagram is labeled 'Q.4103(22)' in the bottom right corner.
+
+Sequence diagram for hybrid overlay network creation
+
+**Figure 7-1 – Information flow for hybrid overlay network creation**
+
+- 1 A peer sends a *HybridOverlayCreation* request message to create a HON and uses a parameter of message defined in clause 6 to specify the properties of an overlay network.
+- 2 The HOMS receiving the *HybridOverlayCreation* message creates the requested HON, and when successfully created, transmits the network attribute information including the newly issued overlay-id to the peer through a 200 OK response.
+
+### 7.1.2 Query of hybrid overlay network
+
+When a user wants to get the list of the overlay network with details, the user sends *HybridOverlayQuery* messages to HOMS. This clause describes the operational procedures for querying the details on a specific hybrid overlay network that is already created by any peer as specified in clause 7.1.1, as shown in Figure 7-2.
+
+
+
+A sequence diagram illustrating the information flow for hybrid overlay network query. It features three main entities: 'Overlay network participants' (represented by a person icon), a 'Peer', and 'HOMS'. The interaction begins with the 'Overlay network participants' sending a 'Query overlay' message (dashed line) to the 'Peer'. The 'Peer' then sends a '1. HybridOverlayQuery' request (solid line) to 'HOMS'. 'HOMS' responds with '2. 200 OK' (solid line). A legend at the bottom indicates that dashed lines represent 'User behaviour' and solid lines represent 'Protocol behaviour'. The diagram is labeled 'Q.4103(22)' in the bottom right corner.
+
+Sequence diagram for hybrid overlay network query
+
+**Figure 7-2 – Information flow for hybrid overlay network query**
+
+- 1 A peer sends a *HybridOverlayQuery* request message to HOMS, and this request message can contain keywords to be queried such as overlay-id, title, description, etc.
+- 2 The HOMS receiving the *HybridOverlayQuery* message returns the requested information within the body of the 200 OK response. If there is no keyword in the URI parameter of the request message, HOMS returns the list of the current available overlay networks.
+
+### 7.1.3 HybridOverlayModification
+
+This clause describes the operational procedures for modifying the details on a specific hybrid overlay network. Figure 7-3 shows the information flow for the modification of a hybrid overlay network.
+
+
+
+The diagram illustrates the information flow for modifying a hybrid overlay network. It features three main entities: an 'Overlay network owner' (represented by a person icon), a 'Peer', and 'HOMS'. The interaction begins with the 'Overlay network owner' sending a 'Modify overlay' request (dashed line) to the 'Peer'. The 'Peer' then sends a '1. HybridOverlayModification' request (solid line) to 'HOMS'. 'HOMS' responds with a '2. 200 OK' message (solid line) back to the 'Peer'. A legend at the bottom indicates that dashed lines represent 'User behaviour' and solid lines represent 'Protocol behaviour'. The reference 'Q.4103(22)' is shown in the bottom right corner.
+
+Sequence diagram for HybridOverlayModification showing the interaction between an Overlay network owner, a Peer, and HOMS.
+
+**Figure 7-3 – Information flow for hybrid overlay network modification**
+
+- 1 A peer sends a *HybridOverlayModification* request message to HOMS to modify attributes of a specific overlay network. The overlay network owner is able to modify the *description*, *title*, *expires* and *auth*.
+
+NOTE – The updated information is reflected immediately by HOMS but does not take effects from already joined peers. On periodic refreshing by a peer, peers will receive the latest information.
+
+- 2 The HOMS receiving the *HybridOverlayModification* message returns details of the overlay network to check the modification result by the peer.
+
+### 7.1.4 HybridOverlayRemoval
+
+This clause describes the operational procedures for removing a specific hybrid overlay network by an owner. Figure 7-4 shows the information flow for removing a hybrid overlay network by an owner.
+
+
+
+The diagram illustrates the information flow for removing a hybrid overlay network. It features three main entities: an 'Overlay network owner' (represented by a person icon), a 'Peer', and 'HOMS'. The interaction begins with the 'Overlay network owner' sending a 'Remove overlay' request (dashed line) to the 'Peer'. The 'Peer' then sends a '1. HybridOverlayRemoval' request (solid line) to 'HOMS'. 'HOMS' responds with a '2. 200 OK' message (solid line) back to the 'Peer'. A legend at the bottom indicates that dashed lines represent 'User behaviour' and solid lines represent 'Protocol behaviour'. The reference 'Q.4103(22)' is shown in the bottom right corner.
+
+Sequence diagram for HybridOverlayRemoval showing the interaction between an Overlay network owner, a Peer, and HOMS.
+
+**Figure 7-4 – Information flow for hybrid overlay network removal**
+
+- 1 A peer sends a *HybridOverlayRemoval* request message to HOMS to remove a specific overlay network explicitly.
+
+- 2 The HOMS receiving the *HybridOverlayRemoval* message returns the 200 OK messages.
+
+NOTE 1 – This operation just removes information in HOMS, and HOMS does not notify the event to the peers of the overlay network. When a peer refreshes its status, it will find out that the overlay network is no longer valid. However, the implementation or service is dependent on whether the HON is leaving the network or not.
+
+NOTE 2 – When the lifetime of the overlay network is expired, HOMS removes the overlay network information silently. If the owner wants to extend the lifetime, it updates by using the *HybridOverlayModification* message.
+
+## 7.2 Hybrid overlay peer management
+
+This clause describes the procedures related to a peer's activity such as join, leave, report and refresh.
+
+### 7.2.1 HybridOverlayJoin
+
+This clause describes the operational procedures for joining an overlay network by a peer. It is assumed that the peer has an overlay-id to join an overlay network, and it can be acquired by the use of the *HybridOverlayQuery* message specified in clause 7.1.2 of this Recommendation. Figure 7-5 shows the information flow for joining into an existing hybrid overlay network.
+
+
+
+```
+sequenceDiagram
+ participant Peer
+ participant HOMS
+ Note left of Peer: Overlay network participants
+ User behaviour: Peer->>HOMS: 1. HybridOverlayJoin (w. overlay-id, peer information)
+ Protocol behaviour: HOMS-->>Peer: 2. 200 OK (w. peer list)
+```
+
+Sequence diagram showing the information flow for hybrid overlay network join. A 'Peer' sends a 'HybridOverlayJoin' request to 'HOMS' with 'w. overlay-id, peer information'. 'HOMS' responds with a '200 OK' message containing a 'w. peer list'. A callout 'Overlay network participants' points to the Peer. Legend: dashed line = User behaviour, solid line = Protocol behaviour. Reference: Q.4103(22).
+
+**Figure 7-5 – Information flow for hybrid overlay network join**
+
+- 1 A peer sends a *HybridOverlayJoin* request message to HOMS to join a specific overlay network. In the request message, it includes the overlay-id as well as the peer information as specified in clause 6.2.5 of this Recommendation.
+- 2 The HOMS receiving the *HybridOverlayRemoval* message returns the 200 OK message with a peer list that contains the entry peer list as specified in clause 6.2.5.
+
+### 7.2.2 HybridOverlayReport
+
+This clause describes the operational procedures for reporting the status of a peer. When a peer detects an event to be reported to HOMS, it sends a *HybridOverlayReport* message. The reported information is used to optimize and analyse the overlay network. HOMS can figure out the structure of CoreTree by using aggregated reports from many peers simultaneously. The types of events include the following but are not limited:
+
+- changes of primary/candidate path;
+- attachment of a new application on the peer;
+- etc.
+
+Figure 7-6 shows information flows for reporting peer's status to HOMS.
+
+
+
+```
+
+sequenceDiagram
+ participant Peer
+ participant HOMS
+ Note right of Peer: w. peer information
+ Peer->>HOMS: 1. HybridOverlayReport
+ HOMS-->>Peer: 2. 200 OK
+ Note right of HOMS: Q.4103(22)
+
+```
+
+Sequence diagram showing information flow for hybrid overlay network report. A Peer sends a '1. HybridOverlayReport' message to HOMS, with a dashed box labeled 'w. peer information' above it. HOMS responds with '2. 200 OK'. A dashed arrow labeled 'Report status' points to the first message. The diagram is labeled Q.4103(22).
+
+**Figure 7-6 – Information flow for hybrid overlay network report**
+
+- 1 A peer sends a *HybridOverlayReport* request message to HOMS to report the status of the peer.
+- 2 The HOMS receiving the *HybridOverlayReport* message returns a 200 OK message with overlay information as specified in clause 6.2.6.
+
+### 7.2.3 HybridOverlayRefresh
+
+This clause describes the operational procedures for a peer's prolong joining to a specific HON and updating the application attachment to the peer. When a peer joins a HON, there is a lifetime for the join that is specified in the expire parameter of the response message. When the lifetime expires, the peer is excluded from the overlay network. In order to keep the join, the peer needs to send a *HybridOverlayRefresh* message periodically before the expiration. In addition, it needs to also report to HOMS on any attachment of a new data prosumer application such as Internet of things (IoT), multimedia, blockchain, etc.
+
+Figure 7-7 shows the information flow for refreshing the peer's joining to a specific HON.
+
+
+
+```
+
+sequenceDiagram
+ participant Peer
+ participant HOMS
+ Note right of Peer: w. overlay/peer/app information
+ Peer->>HOMS: 1. HybridOverlayRefresh
+ HOMS-->>Peer: 2. 200 OK
+ Note right of HOMS: Q.4103(22)
+
+```
+
+Sequence diagram showing information flow for hybrid overlay network refresh. A Peer sends a '1. HybridOverlayRefresh' message to HOMS, with a dashed box labeled 'w. overlay/peer/app information' above it. HOMS responds with '2. 200 OK'. The diagram is labeled Q.4103(22).
+
+**Figure 7-7 – Information flow for hybrid overlay network refresh**
+
+- 1 A peer sends a *HybridOverlayRefresh* request message to HOMS to refresh the status of the peer.
+- 2 The HOMS receiving the *HybridOverlayRefresh* message returns a 200 OK message with the overlay information as specified in clause 6.2.7. On sending the response, the HOMS extends the lifetime of the peer's joining and embeds the updated lifetime into the *expires* parameter in the overlay information.
+
+### 7.2.4 HybridOverlayLeave
+
+This clause describes the operational procedures for leaving a HON by a peer explicitly. These procedures are performed after the peer release peer relationship with other peers. On receiving this request, HOMS remove the peer from the overlay network immediately. If a peer leaves without these
+
+procedures, it will remain in the overlay network for the time being before its expiration, and HOMS will provide the peer's information to another peer's *HybridOverlayJoin* request. However, other peers do not make a connection with this peer and it causes no problem. Furthermore, peers connected with the ungracefully leaving peer detects the disconnection with the peer and the HON gets recovered immediately as specified in [ITU-T Q.4101].
+
+Figure 7-8 shows the information flow for leaving a specific HON by a peer.
+
+
+
+The diagram is a sequence diagram with two lifelines: 'Peer' on the left and 'HOMS' on the right. A dashed box labeled 'w. overlay/peer information' is shown above the first message. The sequence of messages is: 1. A solid arrow labeled '1. HybridOverlayLeave' points from the Peer to HOMS. 2. A solid arrow labeled '2. 200 OK' points from HOMS back to the Peer. The text 'Q.4103(22)' is located at the bottom right of the diagram.
+
+Sequence diagram showing the information flow for hybrid overlay network leave between a Peer and HOMS.
+
+**Figure 7-8 – Information flow for hybrid overlay network leave**
+
+- 1 A peer sends a *HybridOverlayLeave* request message to HOMS to leave a specific HON. On sending this request, the request message includes the PEER\_AUTH elements for authenticating the peer by HOMS.
+- 2 The HOMS receiving the *HybridOverlayLeave* message returns the 200 OK message, and removes the peer from the HON.
+
+# Bibliography
+
+- [b-ITU-T X.1161] Recommendation ITU-T X.1161 (2008), *Framework for secure peer-to-peer communications*.
+- [b-ITU-T X.1162] Recommendation ITU-T X.1162 (2008), *Security architecture and operations for peer-to-peer networks*.
+- [b-ITU-T Y.2012] Recommendation ITU-T Y.2012 (2010), *Functional requirements and architecture of next generation networks*.
+- [b-ITU-T Y.2206] Recommendation ITU-T Y.2206 (2010), *Requirements for distributed service networking capabilities*.
+- [b-Fielding] Fielding, R., T. (2000), *Architectural Styles and the Design of Network-based Software Architectures*, Doctoral Dissertation, University of California, Irvine.
+<>
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling, and associated measurements and tests |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.4163-202312-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Q/T-REC-Q.4163-202312-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477
--- /dev/null
+++ b/marked/Q/T-REC-Q.4163-202312-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:37aed4fc114a39843438175326e0b7e1d09a9d6075723d82fea32040fd560ee4
+size 7192
diff --git a/marked/Q/T-REC-Q.4163-202312-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg b/marked/Q/T-REC-Q.4163-202312-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c2544c5318880088c49337b5589f6a773b0e6f20
--- /dev/null
+++ b/marked/Q/T-REC-Q.4163-202312-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d8446d2bc493062408fc7ca9fda77dc35a082c8992e707d602834d505d2798a8
+size 9959
diff --git a/marked/Q/T-REC-Q.4163-202312-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.4163-202312-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..05b24a0166f5e068a9c3fd3bd1e4217c283a296d
--- /dev/null
+++ b/marked/Q/T-REC-Q.4163-202312-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3370f8c701ee870828ebf5e3d03098411003a4955f2fafe3529d9027b60f5b7b
+size 11376
diff --git a/marked/Q/T-REC-Q.4163-202312-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Q/T-REC-Q.4163-202312-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..794a2eb98788219d49bafadf9c768bb1e698563c
--- /dev/null
+++ b/marked/Q/T-REC-Q.4163-202312-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:283ca0933590d59ab841ceaaa17b74269900569ef2db43a240d9da1a865ca0e7
+size 14904
diff --git a/marked/Q/T-REC-Q.45bis-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.45bis-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7
--- /dev/null
+++ b/marked/Q/T-REC-Q.45bis-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e
+size 7392
diff --git a/marked/Q/T-REC-Q.45bis-198811-I_PDF-E/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg b/marked/Q/T-REC-Q.45bis-198811-I_PDF-E/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ebd082b407008a818f4c06aff4d79d41e2212583
--- /dev/null
+++ b/marked/Q/T-REC-Q.45bis-198811-I_PDF-E/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5b53775122e5a714c0ebbc44e23b8343ad2c00f8c982a967dd555385b3545c4e
+size 26808
diff --git a/marked/Q/T-REC-Q.45bis-198811-I_PDF-E/6b32b7b928d34eeccb15c29cdf9d2cb3_img.jpg b/marked/Q/T-REC-Q.45bis-198811-I_PDF-E/6b32b7b928d34eeccb15c29cdf9d2cb3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1bfb55965eb455ec0815ab5ecbeaec2ee9bfdd54
--- /dev/null
+++ b/marked/Q/T-REC-Q.45bis-198811-I_PDF-E/6b32b7b928d34eeccb15c29cdf9d2cb3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88aae05cfbebe3c7aa869de152b1b9b71e39108798057891750247095f415f61
+size 123054
diff --git a/marked/Q/T-REC-Q.45bis-198811-I_PDF-E/e394c2b5c61344f6a12397f430086072_img.jpg b/marked/Q/T-REC-Q.45bis-198811-I_PDF-E/e394c2b5c61344f6a12397f430086072_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1deb4eb11f0921beb8de199d6bcd74d5d9c2a0c9
--- /dev/null
+++ b/marked/Q/T-REC-Q.45bis-198811-I_PDF-E/e394c2b5c61344f6a12397f430086072_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:93e88b6bb897fcf8ffbb9bbe7beb74a31326d40bc0524ed16991ab8b3a9db991
+size 60605
diff --git a/marked/Q/T-REC-Q.45bis-198811-I_PDF-E/f89631cc38aa971e8d15cbffe28f1183_img.jpg b/marked/Q/T-REC-Q.45bis-198811-I_PDF-E/f89631cc38aa971e8d15cbffe28f1183_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c69ff4e3a03305f1620249d04a84b88d047fbcaa
--- /dev/null
+++ b/marked/Q/T-REC-Q.45bis-198811-I_PDF-E/f89631cc38aa971e8d15cbffe28f1183_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3da1d3126fd604dd1b315e70b78367b64d3b5dc443d7b6bd7c47d7879049c79b
+size 71810
diff --git a/marked/Q/T-REC-Q.500-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.500-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a253fa3467f78916e4481e4b9e29e0fa4dc80977
--- /dev/null
+++ b/marked/Q/T-REC-Q.500-198811-I_PDF-E/raw.md
@@ -0,0 +1,171 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**Q.500**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+# **DIGITAL EXCHANGES** ---
+
+## **DIGITAL LOCAL, COMBINED, TRANSIT AND INTERNATIONAL EXCHANGES – INTRODUCTION AND FIELD OF APPLICATION**
+
+**ITU-T Recommendation Q.500**
+
+(Extract from the *Blue Book*)
+
+---
+
+### NOTES
+
+- 1 ITU-T Recommendation Q.500 was published in Fascicle VI.5 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.
+
+### Recommendation Q.500
+
+## DIGITAL LOCAL, COMBINED, TRANSIT AND INTERNATIONAL EXCHANGES INTRODUCTION AND FIELD OF APPLICATION
+
+## 1 Introduction
+
+This series of Recommendations Q.500-554 applies to digital local, combined1, transit and international exchanges for telephony in Integrated Digital Networks (IDNs) and mixed analogue/digital networks, and also to local, combined, transit and international exchanges in an Integrated Services Digital Network (ISDN).
+
+The series of Recommendations comprises:
+
+- Q.500 Introduction and field of application
+- Q.511 Exchange interfaces towards other exchanges
+- Q.512 Exchange interfaces for subscriber access
+- Q.513 Exchange interfaces for operations, administration and maintenance
+- Q.521 Exchange functions
+- Q.522 Digital exchange connections, signalling and ancillary functions
+- Q.541 Design objectives – General
+- Q.542 Design objectives – Operations and Maintenance
+- Q.543 Performance design objectives
+- Q.544 Exchange measurements
+- Q.551 Transmission characteristics of digital exchanges
+- Q.552 Transmission characteristics at 2-wire analogue interfaces
+- Q.553 Transmission characteristics at 4-wire analogue interfaces
+- Q.554 Transmission characteristics at digital interfaces.
+
+Considerations have been primarily on exchanges utilizing, at least in part, time division switching techniques. However, these Recommendations are implementation independent, and other system implementations using alternative techniques (e.g., space division switching) may be possible, which would meet the requirements of these Recommendations.
+
+## 2 Field of application
+
+These Recommendations are intended to be applied as indicated below.
+
+### 2.1 *Application and evolution to the ISDN*
+
+The selection of features, functions and interfaces to be provided in a digital local, combined, transit or international exchange in a particular network application will be determined by the administration concerned. Reference to a function in these Recommendations, including their diagrams, does not imply that it will necessarily be provided in every exchange type or configuration. Similarly, it is possible that some functions may be provided which are not mentioned.
+
+---
+
+1 A “combined” digital exchange is one which includes both local exchange and transit exchange functions (see definition 1005 in Recommendation Q.9).
+
+### 2.2 *Relationship of design performance requirements to operational performance requirements*
+
+Performance requirements as defined in this series of Recommendations should be considered as design objectives for systems under the conditions stated in the Recommendations. These conditions are defined by such parameters as average circuit occupancy, busy hour call attempts, etc. They should be distinguished from the operational performance requirements which administrations establish for exchanges operating in their particular environment.
+
+Further clarification of this point can be obtained in Recommendation G.102.
+
+## 3 **The Q.500-Series of Recommendations**
+
+### 3.1 *Exchange interfaces (Recommendations Q.511, Q.512 and Q.513)*
+
+The interface functions defined are those necessary for interworking with digital and analogue transmission systems on both circuits to other exchanges and on subscriber lines, and with telecommunications management networks.
+
+#### 3.1.1 *Characteristics of exchange interfaces towards other exchanges (Recommendation Q.511)*
+
+This Recommendation describes the exchange interfaces used to provide transmission facilities towards other exchanges. It applies to digital local, combined, transit and international exchanges for telephony in integrated digital networks (IDN) and mixed (analogue/digital) networks, and also to local, combined, transit and international exchanges in an integrated services digital network (ISDN).
+
+#### 3.1.2 *Characteristics of exchange interfaces for subscriber access (Recommendation Q.512)*
+
+The Recommendation describes the subscriber side interface characteristics. It applies to digital local and combined exchanges for telephony in Integrated Digital Networks (IDN) and mixed (analogue/digital) networks, and also to local and combined exchanges in an integrated digital network (ISDN).
+
+#### 3.1.3 *Exchange interfaces for operations, administration and maintenance (Recommendation Q.513)*
+
+The interfaces defined are those necessary for transmission of messages associated with operations, administration and maintenance of the exchange.
+
+These interfaces include OAM interfaces between the exchange and the following: OAM systems, mediation devices, user workstations, and other network elements.
+
+#### 3.1.4 *Interfaces to non-voice handling facilities*
+
+The need for the Recommendation of interfaces between digital transit, local and combined exchanges and non-voice handling facilities remains for further study. (An example of such a non-voice facility is a packet switched data node.) Attention is drawn to Recommendation X.300 which describes the general principles for interworking between public data networks and also to the I.400/I.500-Series Recommendations for interworking between ISDN and other dedicated networks.
+
+### 3.2 *Exchange functions (Recommendation Q.521)*
+
+This Recommendation covers the definition of the principal exchange functions to support services and includes a description of an exchange functional model.
+
+### 3.3 *Exchange connections, signalling and ancillary functions (Recommendation Q.522)*
+
+This Recommendation covers the following functions:
+
+#### a) *Connections through an exchange*
+
+This section includes the switch block(s), the characteristics associated with connections through exchanges and a set of diagrams showing typical types of connection.
+
+A connection through an exchange may include one or more stages of time and/or space division switching, providing a path for transmission through the exchange.
+
+#### b) *Signalling*
+
+Signalling includes reception of call-related and other information, interaction with the call control function and transfer of information to subscribers and network(s) as required.
+
+Signalling may involve common channel and/or channel associated signalling.
+
+#### c) *Control and call handling*
+
+Control and call handling includes initiation, supervision and termination of most actions in the exchange.
+
+Commands are initiated and information passed/received to/from the other functions within the exchange.
+
+Control functions may be contained in one block or distributed throughout the exchange.
+
+#### d) *Ancillaries*
+
+Examples of such functions are:
+
+- recorded announcements;
+- tone generation;
+- conferencing facilities.
+
+Their location is dependent on the function itself and the exchange configuration.
+
+### 3.4 *Exchange design objectives (Recommendations Q.541, Q.542, Q.543 and Q.544)*
+
+#### 3.4.1 *General design objectives (Recommendation Q.541)*
+
+This includes the general design objective principles, availability and hardware design objectives as well as the design objectives associated with the operation of an exchange in an Integrated Digital Network. The latter encompasses timing and synchronization design objectives.
+
+Timing comprises the generation and distribution of timing signals and includes timing of outgoing signals. It enables those parts of the exchange which form the switched path of a connection to operate synchronously. Synchronization will depend on the national synchronization plan and exchange timing arrangements.
+
+Exchanges will usually extract synchronizing information from one or more incoming bit streams or a separate synchronization network and use this to adjust the timing signals generated in the distribution within the exchange.
+
+#### 3.4.2 *Operations and maintenance design objectives (Recommendation Q.542)*
+
+This covers the operations and maintenance design objectives including network management controls, alarm handling and subscriber line maintenance and testing.
+
+#### 3.4.3 *Performance design objectives (Recommendation Q.543)*
+
+Exchange performance design objectives are defined for guiding system design and for comparing the capabilities of different systems. (Recommendations relating to provisioning and operational performance of exchanges in the network are covered in the E.500-E.543 Series.)
+
+#### 3.4.4 *Exchange measurements (Recommendation Q.544)*
+
+Measurements that may be used for planning, operation, maintenance and network management of exchanges and their associated networks are described. The measurement data consists primarily of event counts and traffic intensity levels experienced by the various traffic handling elements of the exchange.
+
+### 3.5 *Transmission characteristics (Recommendations Q.551 to Q.554)*
+
+#### 3.5.1 *Transmission characteristics of digital exchanges (Recommendation X.551)*
+
+This includes the general definitions associated with Recommendations Q.551 to Q.554, and transmission parameters from a total exchange perspective such as absolute group delay and the transfer function for jitter and wander. These Recommendations define, for any connection which may be set up by a local, combined, transit or international exchange, the necessary levels of transmission performance to conform with overall objectives for the complete user-to-user connections in which the exchange may be involved.
+
+#### 3.5.2 *Transmission characteristics at 2-wire interfaces (Recommendation Q.552), 4-wire interfaces (Recommendation Q.553) and digital interfaces (Recommendation Q.554)*
+
+These cover the detailed transmission characteristics of the various types of interface that may be provided on a digital exchange.
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.5005-202302-I_PDF-E/raw.md b/marked/Q/T-REC-Q.5005-202302-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..68c94bed9fd7ab1f785d6a87edd7269422feda49
--- /dev/null
+++ b/marked/Q/T-REC-Q.5005-202302-I_PDF-E/raw.md
@@ -0,0 +1,828 @@
+
+
+# Recommendation**ITU-T Q.5005 (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
+
+---
+
+### **Requirements, framework and protocols for signalling network analysis and optimization in IMT-2020**
+
+
+
+The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font superimposed on the globe.
+
+ITU logo
+
+## ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS**
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120-Q.499 |
+| DIGITAL EXCHANGES | Q.500-Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 |
+| Q3 INTERFACE | Q.800-Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 |
+| INTELLIGENT NETWORK | Q.1200-Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 |
+| BROADBAND ISDN | Q.2000-Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900-Q.4099 |
+| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100-Q.4139 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000-Q.5049 |
+| Signalling requirements and architecture of IMT-2020 | Q.5000-Q.5019 |
+| Protocols for IMT-2020 | Q.5020-Q.5049 |
+| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050-Q.5069 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T Q.5005
+
+# Requirements, framework and protocols for signalling network analysis and optimization in IMT-2020
+
+## Summary
+
+Recommendation ITU-T Q.5005 specifies the framework, interfaces (IFs) and protocols, as well as service procedures for signalling network analysis and optimization in IMT-2020. The signalling network is the totality of network functions and the signalling exchanges that are related to telecommunication services. Recommendation ITU-T Q.5005 covers aspects including an overview of signalling networks, requirements for signalling collection, requirements for signalling network analysis, requirements for signalling network optimization, framework, IFs and protocols, service procedures, artificial intelligence-assisted functions and general security considerations of signalling network analysis and optimization in IMT-2020.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.5005 | 2023-02-13 | 11 | 11.1002/1000/15257 |
+
+## Keywords
+
+Framework, IMT-2020, interfaces, protocols, requirements, signalling network analysis, signalling network optimization.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at .
+
+© ITU 2023
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+###### Page
+
+| | | |
+|------|-----------------------------------------------------------------------------------------|----|
+| 1 | Scope ..... | 1 |
+| 2 | References..... | 1 |
+| 3 | Definitions ..... | 2 |
+| 3.1 | Terms defined elsewhere ..... | 2 |
+| 3.2 | Terms defined in this Recommendation ..... | 2 |
+| 4 | Abbreviations and acronyms ..... | 2 |
+| 5 | Conventions ..... | 4 |
+| 6 | Overview of the IMT-2020 signalling network..... | 5 |
+| 7 | Requirements for IMT-2020 signalling network analysis and optimization..... | 6 |
+| 7.1 | Requirements for signalling collection in IMT-2020..... | 7 |
+| 7.2 | Requirements for signalling network analysis in IMT-2020 ..... | 9 |
+| 7.3 | Requirements for signalling network optimization in IMT-2020 ..... | 11 |
+| 8 | Framework of IMT-2020 signalling network analysis and optimization ..... | 12 |
+| 9 | Interfaces and protocols of IMT-2020 signalling network analysis and optimization ..... | 14 |
+| 9.1 | Signalling collection interfaces ..... | 14 |
+| 9.2 | Signalling processing interfaces ..... | 14 |
+| 10 | Service procedures for IMT-2020 signalling network analysis and optimization ..... | 15 |
+| 10.1 | Signalling collection procedures ..... | 15 |
+| 10.2 | Signalling network analysis procedures..... | 16 |
+| 10.3 | Signalling network optimization procedures ..... | 16 |
+| 10.4 | AI/ML-related procedures ..... | 18 |
+| 11 | AI-assisted functions of IMT-2020 signalling network analysis and optimization ..... | 18 |
+| 11.1 | Requirements for AI capabilities provided by the AI assistance component..... | 19 |
+| 11.2 | Requirements for AI capabilities provided by external AI platform ..... | 20 |
+| 12 | Security considerations ..... | 20 |
+| | Bibliography ..... | 22 |
+
+
+
+# Recommendation ITU-T Q.5005
+
+# Requirements, framework and protocols for signalling network analysis and optimization in IMT-2020
+
+# 1 Scope
+
+This Recommendation specifies requirements, framework, interfaces (IFs) and protocols for signalling network analysis and optimization in an IMT-2020 network. The signalling network in IMT-2020 is the totality of network functions and corresponding signalling exchanges that are related to IMT-2020 service procedures. The IMT-2020 signalling network analysis and optimization system is a network management system that consists of components for signalling collection, signalling network analysis, signalling network optimization and artificial intelligence or machine learning (AI/ML) assistance. The IMT-2020 signalling network analysis and optimization system is designed with the characteristics of high efficiency, real time reaction, reliability and intelligence, aimed at application in an IMT-2020 network.
+
+The following aspects of IMT-2020 signalling network analysis and optimization system are addressed in this Recommendation.
+
+- Overview, which presents the main network entities and IFs that are used in IMT-2020 signalling network analysis and optimization systems.
+- Requirements for IMT-2020 signalling network analysis and optimization, including general signalling requirements for collection, network analysis and network optimization.
+- A framework for IMT-2020 signalling network analysis and optimization systems, including global view, system architecture, external boundary and component design of signalling network analysis and optimization systems.
+- IFs and protocols of IMT-2020 signalling network analysis and optimization systems, including internal IFs, external IFs and corresponding protocols.
+- Service procedures of signalling interworking between collection, network analysis and network optimization.
+- Functions of IMT-2020 signalling network analysis and optimization systems that are provided by an internal AI assistance component or external AI platforms. The architectural framework for an external AI platform is specified in [ITU-T Y.3172].
+- Security considerations of IMT-2020 signalling network analysis and optimization systems, including signalling collection security, signalling network analysis security, signalling network optimization security, AI/ML-related security, inter-working security, data transport security and user privacy.
+
+# 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.3644] Recommendation ITU-T Q.3644 (2019), *Requirements for signalling network analyses and optimization in VoLTE*.
+
+- [ITU-T Y.2701] Recommendation ITU-T Y.2701 (2007), *Security requirements for NGN release 1*.
+- [ITU-T Y.3101] Recommendation ITU-T Y.3101 (2018), *Requirements of the IMT-2020 network*.
+- [ITU-T Y.3102] Recommendation ITU-T Y.3102 (2018), *Framework of the IMT-2020 network*.
+- [ITU-T Y.3104] Recommendation ITU-T Y.3104 (2018), *Architecture of the IMT-2020 Network*.
+- [ITU-T Y.3172] Recommendation ITU-T Y.3172 (2019), *Architectural framework for machine learning in future networks including IMT-2020*.
+- [ITU-R M.1645] Recommendation ITU-R M.1645 (2003), *Framework and overall objectives of the future development of IMT-2000 and systems beyond IMT-2000*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 signalling network** [ITU-T Q.3644]: Refers to the network entities and the signalling exchange which are related to telecommunications services.
+
+**3.1.2 signalling collection** [ITU-T Q.3644]: Refers to signalling collection on the interfaces which are related to the signalling processes of telecommunications services.
+
+**3.1.3 signalling network analysis** [ITU-T Q.3644]: Refers to analysis on quotas using the information obtained in signalling collecting, and analyses on status information of signalling network.
+
+**3.1.4 signalling network optimization** [ITU-T Q.3644]: Refers to signalling network optimization on network entities and optimization of signalling exchange between network entities in signalling network, on the basis of signalling network analysis.
+
+**3.1.5 IMT-2020** [b-ITU-T Y.3100]: Systems, system components, and related technologies that support to provide far more enhanced capabilities than those described in [ITU-R M.1645].
+
+**3.1.6 machine learning (ML)** [ITU-T Y.3172]: Processes that enable computational systems to understand data and gain knowledge from it without necessarily being explicitly programmed.
+
+## 3.2 Terms defined in this Recommendation
+
+None.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|------|-----------------------------------|
+| 5G | fifth Generation |
+| AI | Artificial Intelligence |
+| AF | Application Function |
+| AS | Application Server |
+| ASF | Authentication Server Function |
+| BGCF | Breakout Gateway Control Function |
+| CEF | Capability Exposure Function |
+
+| | |
+|----------|------------------------------------------------------------|
+| CHF | Charging Function |
+| CU | Centralized Unit |
+| DU | Distributed Unit |
+| DRA | Diameter Routing Agent |
+| EPC | Evolved Packet Core |
+| EPS | Evolved Packet System |
+| EPSFB | Evolved Packet System Fallback |
+| eMSC | enhanced Mobile Switching Centre |
+| eNB | evolved Node B |
+| GMLC | Gateway Mobile Location Centre |
+| gNB | next generation Node B |
+| GTP | General packet radio service Tunnel Protocol |
+| GTP-C | General packet radio service Tunnel Protocol-Control plane |
+| GTP-U | General packet radio service Tunnel Protocol-User plane |
+| HSS | Home Subscriber Server |
+| HTTP | Hypertext Transfer Protocol |
+| IBCF | Interconnection Border Control Function |
+| I-CSCF | Interrogating Call Session Control Function |
+| IF | Interface |
+| IMS | Internet Protocol Multimedia Subsystem |
+| IMT-2020 | International Mobile Telecommunication-2020 |
+| IP | Internet Protocol |
+| MEP | Mobile Edge Platform |
+| MGCF | Media Gateway Control Function |
+| MME | Mobility Management Entity |
+| ML | Machine Learning |
+| MO | Mobile Originated |
+| MT | Mobile Terminated |
+| NACF | Network Access Control Function |
+| NAF | Network Application Function |
+| NAS | Non-Access Stratum |
+| NFR | Network Function Repository |
+| NGAP | Next Generation Application Protocol |
+| NG-RAN | Next Generation Radio Access Network |
+| NRF | Network Repository Function |
+| NSSF | Network Slice Selection Function |
+| PCF | Policy Control Function |
+
+| | |
+|--------|---------------------------------------|
+| PCRF | Policy and Charging Rules Function |
+| P-CSCF | Proxy Call Session Control Function |
+| PGW | Packet Gateway |
+| PGW-C | Packet Gateway-Control plane |
+| PGW-U | Packet Gateway-User plane |
+| RAT | Radio Access Technology |
+| S1AP | S1 Application Protocol |
+| SBA | Service-Based Architecture |
+| SBC | Session Border Controller |
+| SBI | Service-Based Interface |
+| SCEF | Service Capability Exposure Function |
+| SCP | Service Communication Proxy |
+| S-CSCF | Serving Call Session Control Function |
+| SDTP | Shared Data Transfer Protocol |
+| SGW | Serving Gateway |
+| SIP | Session Initiation Protocol |
+| SMF | Session Management Function |
+| SMSC | Short Message Service Centre |
+| SMSF | Short Message Service Function |
+| TCP | Transmission Control Protocol |
+| UDR | Unified Data Repository |
+| UE | User Equipment |
+| UPF | User Plane Function |
+| USM | Unified Subscription Management |
+| VoLTE | Voice over Long-Term Evolution |
+
+# 5 Conventions
+
+In this Recommendation:
+
+The phrase "is required to" indicates a requirement that must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed.
+
+The phrase "is recommended" indicates a requirement that is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance.
+
+The phrase "can optionally" indicates an optional requirement that is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option, and the feature can be optionally enabled by the network operator or service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with this Recommendation.
+
+# 6 Overview of the IMT-2020 signalling network
+
+The IMT-2020 signalling network is required to be analysed and optimized, in order to support and maintain the IMT-2020 network services specified in [ITU-T Y.3102], in addition to the IMT-2020 network functions specified in [ITU-T Y.3104]. The IMT-2020 signalling network is the totality of network functions and interfaces that are related to the signalling processes of IMT-2020 services in the Internet protocol multimedia subsystem (IMS), evolved packet system (EPS), and IMT-2020 domain. Compared with the baseline of voice over long-term evolution (VoLTE) signalling network, the following main network functions and interfaces of IMT-2020 signalling network are introduced.
+
+The network entities in an IMS domain include a serving call session control function (S-CSCF), interrogating call session control function (I-CSCF), proxy call session control function (P-CSCF) and application server (AS); network entities in an EPS domain include mobility management entity (MME), serving gateway (SGW) and policy and charging rules function (PCRF).
+
+The network functions in an IMT-2020 domain include a network access control function (NACF), session management function (SMF), policy control function (PCF), user plane function (UPF), unified subscription management (USM) function, network slice selection function (NSSF) and authentication server function (ASF).
+
+The interfaces in IMS and EPS domains include Cx, Rx, Sh, Gm, ISC, Mw, S11 and S1-MME, which exchange signalling between network IMS and EPS entities based on a session initiation protocol (SIP), diameter protocol, general packet radio service tunnel protocol-control plane (GTP-C) and S1 application protocol (S1AP).
+
+The service-based interfaces (SBIs) in an IMT-2020 signalling network include Nnacf, Nsmf, Npcf, Nusm and Nnssf. The reference points in an IMT-2020 signalling network include N1, N2, N3, N5, N6, N7, N8, N10, N11, N14, N15, N22, N26, etc. The SBIs and reference points exchange signalling between IMT-2020 network functions. The interfaces in an IMT-2020 signalling network are based on the hypertext transfer protocol (HTTP).
+
+The network entities and interfaces in IMS and EPS domains are inherited from a VoLTE signalling network and used to help trace and analyse voice service, such as an EPS fallback procedure. Packet gateway-control plane (PGW-C) and SMF as well as packet gateway-user plane (PGW-U) and UPF are converged network functions for interworking between IMT-2020 and an evolved packet core (EPC). Figure 6-1 shows the main network functions and interfaces of an IMT-2020 signalling network, which are for further study.
+
+
+
+Figure 6-1: The main network functions and interfaces of IMT-2020 signalling network. This is a complex architectural diagram showing the interconnections between various network functions. At the top, the IMS (IP Multimedia Subsystem) contains IBCF, I/S-CSCF/BGCF, SCP, IP-SM-GW, and GMLC. Below it, the Data network is shown. The central part of the diagram features the Converged network functions, which include HSS/ASF/USM, UDR, PCRF/PCF, NACF, NSSF, PGW-C/SMF, NFR, CHF, and PGW-U/UPF. These are interconnected by various interfaces such as N10, N11, N15, N22, N26, N33, N40, and N6. On the left, the 2G core network (SMSC, DRA, PGW, SGW, MME) and 4G core network (MME, PGW) are shown, connected via interfaces like S1-MME, S1-U, S5, S11, and S6a. At the bottom, the UE (User Equipment) is connected to the network via LTE access (eNB) and IMT-2020 access (gNB, which includes CU and DUs). The UPF/MEP is also shown at the bottom, connecting to the UE and the network functions.
+
+Q.5005(23)
+
+**Figure 6-1 – The main network functions and interfaces of IMT-2020 signalling network**
+
+The hard data collection mode is used for control plane data collection in IMT-2020. A different data collection method could be chosen according to integration deployment, including acquisition by vSwitch image or spectrometer.
+
+Original data from the N3 interface is collected by hard data collection mode, splitting the beam on the UPF side.
+
+# 7 Requirements for IMT-2020 signalling network analysis and optimization
+
+The general requirements for IMT-2020 signalling network analysis and optimization are inherited from those for VoLTE, specified in [ITU-T Q.3644]. Additional general requirements for IMT-2020 signalling network analysis and optimization include signalling collection, signalling network analysis and optimization on SBIs plus reference points between different IMT-2020 network functions, as well as interworking between EPCs and IMT-2020. In addition, different quotas and status information are proposed in IMT-2020 signalling network analysis; service procedures of optimization on signalling exchange and network function running status are specified in IMT-2020 signalling network optimization.
+
+## 7.1 Requirements for signalling collection in IMT-2020
+
+This clause presents requirements for signalling collection on interfaces that are related to signalling processes of services in IMT-2020.
+
+The IFs to be collected in an IMT-2020 signalling network are divided into the following categories:
+
+- IFs based on diameter protocol, e.g., Cx, Rx, Sh;
+- IFs based on SIP, e.g., Gm, ISC, Mw;
+- IFs based on the general packet radio service tunnel protocol or general packet radio service tunnel protocol-control plane (GTP/GTP-C), e.g., Sv, S11;
+- IFs based on S1AP, e.g., S1-MME;
+- IFs based on extensible markup language configuration access protocol, e.g., Ut;
+- IFs based on HTTP protocol, e.g., N11, N15;
+- SBIs, e.g., Npcf, Nsmf;
+- IFs based on non-access stratum (NAS) protocol, e.g., N1.
+
+The requirements of a signalling collection function are as follows:
+
+- Signalling collection is required from all IFs shown in Figure 6-1 for end-to-end signalling analysis.
+- Specified signalling can be collected for one IF or signalling exchanges between two network entities.
+- A signalling collection function is required to support all the IFs and protocols to be collected.
+- Signalling collection information is required to be configurable.
+- Signalling collection information is required to be as accurate and brief as possible.
+- A signalling collection function is required to cache the information obtained for subsequent processing.
+- A signalling collection function is required to support a flexible extension capability to meet new requirements of operators and to adapt to the evolution of the IMT-2020 network.
+- A signalling collection function is required not to influence the functions of the network entities related to the collected IFs.
+- A signalling collection function is required to avoid the impact on the performance of the network entities related to collected IFs.
+- A signalling collection function is required not to affect the service procedure and maintenance of the IMT-2020 network. The collected original data can be encapsulated into a formatted packet for an AI assistance component or AI platform to use.
+- A signalling collection function is required to decode and synthesize the original data, and correlate the original data with a corresponding protocol.
+- A signalling collection function is required to backfill the user plane information, then generate the complete data structure for analysis.
+- A signalling collection function is required to encapsulate the collected data, according to the standard of IF.
+- A signalling collection function is required to fill the collecting time and data number, and integrate a multi-segment original code stream base on the data number.
+- It is recommended to use AI/ML technologies to assist in signalling collection.
+
+The IFs to be collected and corresponding protocols, as well as connected network entities in the IMT-2020 signalling network, are listed in Table 1. Based on network status, calculation requirements
+
+and capabilities of the signalling collection system, the collected IFs can be customized by the operator.
+
+**Table 1 – Interfaces to be collected in IMT-2020 signalling network**
+
+| Interface | Protocol | Connected network entities |
+|------------------|------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|
+| S6a | Diameter | MME and home subscriber server (HSS) |
+| Gx | Diameter | Packet gateway (PGW) and PCRF |
+| Rx | Diameter | P-CSCF and PCRF |
+| Cx | Diameter | S/I-CSCF and HSS |
+| Sh | Diameter | AS and HSS |
+| Zh | Diameter | Bootstrapping server function and HSS |
+| ISC | SIP | S-CSCF and AS |
+| Ma | SIP | I-CSCF and AS |
+| Mg | SIP | S/I-CSCF and media gateway control function (MGCF) |
+| Mj | SIP | Breakout gateway control function (BGCF) and MGCF |
+| Mw | SIP | P-CSCF and S/I-CSCF; S/I-CSCF and S/I-CSCF; S/I-CSCF and enhanced mobile switching centre (eMSC) |
+| Mx | SIP | S/I-CSCF and interconnection border control function (IBCF); BGCF and IBCF |
+| Mr | SIP | S-CSCF and multimedia resource function controller |
+| Gm | SIP | User equipment (UE) and P-CSCF |
+| Sv | GTP-C | MME and eMSC |
+| S1-MME | SIAP | MME and evolved nodeB |
+| S11 | GTP-C | MME and SGW |
+| S5/S8 | GTP-C and General packet radio service tunnel protocol user plane (GTP-U) | SGW and PGW |
+| Sh/J | Diameter/mobile application part | HSS and Internet protocol (IP) short message gateway |
+| Imc | Bearer independent call control /SIP/integrated services digital network user part | MGCF and entities in the circuit-switched domain |
+| N1/N2 | Next generation application protocol/NAS | UE/next generation radio access network (NG-RAN) and NACF |
+| N4 | Packet forwarding control protocol | UPF and SMF |
+| N7 | HTTP2 | SMF and PCF |
+| N8 | HTTP2 | USM and AMF |
+| N10 | HTTP2 | USM and SMF |
+| N11 | HTTP2 | NACF and SMF |
+| N12 | HTTP2 | NACF and ASF |
+| N14 | HTTP2 | Between two NACFs |
+| N15 | HTTP2 | PCF and NACF |
+
+**Table 1 – Interfaces to be collected in IMT-2020 signalling network**
+
+| Interface | Protocol | Connected network entities |
+|------------------|-----------------|-----------------------------------------------------------------------------------|
+| N16 | HTTP2 | Between two SMFs |
+| N22 | HTTP2 | NACF and NSSF |
+| N40 | HTTP2 | SMF and charging function (CHF) |
+| N5 | HTTP2 | PCF and AF |
+| N24 | HTTP2 | PCF in home network and visited network |
+| N26 | HTTP2 | NACF and MME |
+| N3 | GTP-U | NG-RAN and UPF |
+| Namf | SBI | SBI exhibited by NACF |
+| Nsmf | SBI | SBI exhibited by SMF |
+| Nnef | SBI | SBI exhibited by NEF |
+| Npcf | SBI | SBI exhibited by PCF |
+| Nudm | SBI | SBI exhibited by USM |
+| Naf | SBI | SBI exhibited by AF |
+| Nnrf | SBI | SBI exhibited by network repository function (NRF) |
+| Nnssaa | SBI | SBI exhibited by network slice-specific authentication and authorization function |
+| Nnssf | SBI | SBI exhibited by NSSF |
+| Nausf | SBI | SBI exhibited by ASF |
+| Nchf | SBI | SBI exhibited by CHF |
+
+## **7.2 Requirements for signalling network analysis in IMT-2020**
+
+#### **7.2.1 General functional requirements for signalling network analysis in IMT-2020**
+
+The requirements of signalling network analysis function are as follows:
+
+- Signalling from different IFs is required to be related for the same call or session, in order to form end-to-end signalling procedures for quota calculating and fault fixing.
+- Services with the same failure code are required to be counted, such as voice call, short message, user registration. Furthermore, end-to-end signalling for a specified call failure can be presented.
+- Quotas that are needed by operators to examine the quality of an IMT-2020 can optionally be obtained by signalling network analysis.
+- The methods and quotas of signalling network analysis in IMT-2020 are required to support customization to meet the various requirements of different operators.
+- Status information about network entities and signalling exchanges between them is also recommended to be obtained and analysed in the processes of signalling network analysis, which can be used in quota analysis and subsequent signalling network optimization processes.
+- A signalling network analysis function is required to receive the data reported by the data collection function, and synthesize complete end-to-end procedure information from the original data collected by a single IF.
+
+- A signalling network analysis function is required to analyse original data and then report the analytical result to the signalling network optimization function.
+- A signalling network analysis function is required to determine the reason for failure, including that due to service selection or signalling feedback.
+- It is recommended that AI/ML technologies be used to assist in signalling network analysis.
+
+#### 7.2.2 Quota requirements for signalling network analysis in IMT-2020
+
+Key quota requirements for signalling network analysis in IMT-2020 follow.
+
+- Call set-up success rate
+
+$$\text{call set-up success rate} = \frac{\text{S-CSCF call set-up request success times}}{\text{S-CSCF call set-up request times received}} \times 100\%$$
+
+where
+
+S-CSCF call set-up request times received is the number of times an S-CSCF receives invite messages;
+
+S-CSCF call set-up request success times is the number of times an S-CSCF sends ringing messages corresponding to the invite messages that were received by an S-CSCF in a specified period.
+
+- Mobile originated (MO) call set-up success rate
+
+$$\text{MO call set-up success rate} = \frac{\text{P-CSCF original call set-up request success times}}{\text{P-CSCF original call set-up request times}} \times 100\%$$
+
+where
+
+P-CSCF original call set-up request times is the number of times P-CSCF sends invite messages;
+
+P-CSCF original call set-up request success times is the number of times P-CSCF receives ringing messages corresponding to the invite messages that were sent by a P-CSCF in a specified period.
+
+- Mobile terminated (MT) call set-up success rate
+
+$$\text{MT call set-up success rate} = \frac{\text{S-CSCF MT call set-up request success times}}{\text{S-CSCF MT call set-up request times received}} \times 100\%$$
+
+where
+
+S-CSCF MT call set-up request times is the number of times S-CSCF receives invite messages;
+
+S-CSCF MT call set-up request success times is the number of times S-CSCF sends ringing messages corresponding to the invite messages that were received by an S-CSCF in a specified period.
+
+- Call answer rate
+
+$$\text{call answer rate} = \frac{\text{S-CSCF call answer times}}{\text{S-CSCF call set-up request times received}} \times 100\%$$
+
+where
+
+S-CSCF call set-up request times received is the number of times S-CSCF receives invite messages;
+
+S-CSCF call answer times is the number of times S-CSCF sends 200 OK messages corresponding to the invite messages that were received by an S-CSCF in a specified period.
+
+- Average call set-up latency
+
+average call set-up latency = average of interval between SIP message 180 and invite in P-CSCF
+
+Interval between SIP message 180 and invite in P-CSCF is the time that a P-CSCF receives a ringing message minus the time that P-CSCF sends an invite message for the same session.
+
+NOTE – A prerequisite is user access from a wireless IMT-2020 network, when the above quotas are calculated.
+
+- Evolved packet system fallback (EPSFB) success rate with N26
+
+$$\text{EPSFB success rate with N26} = \frac{\text{EPSFB success times with N26}}{\text{EPSFB request times received}} \times 100\%$$
+
+where
+
+EPSFB request times received is the number of times next generation node B (gNB) makes its EPS fallback configuration decision to reject the fifth generation quality of service identifier, 5QI = 1 wireless resource establishment that the NACF sends, returns the PDU session resource modification response, and the rejection reason value is "IMS voice EPS fallback or radio access technology (RAT) fallback triggered";
+
+EPSFB success times with N26 is the number of times the MME returns the tau accept to the evolved node B (eNB).
+
+- EPSFB average latency with N26
+
+EPSFB average latency with N26 = average of interval between timer of EPSFB success and EPSFB request with N26
+
+Interval between timer of EPSFB success and EPSFB request is the time that gNB returns the PDU session resource modification response, and the rejection reason value is "IMS voice EPS fallback or RAT fallback triggered" by the time that MME returns the tau accept to the eNB.
+
+- IMT-2020 initial registration rate
+
+$$\text{IMT-2020 initial registration rate} = \frac{\text{IMT-2020 registration success times}}{\text{IMT-2020 registration received times}} \times 100\%$$
+
+where
+
+IMT-2020 registration received times is the number of times a gNB sends a registration request (initial registration) to a NACF;
+
+IMT-2020 registration success times is the number of times gNB receives a registration accept (initial registration) from the NACF.
+
+#### 7.2.3 Status information requirements for signalling network analysis in IMT-2020
+
+Status information about IMT-2020 signalling network is recommended to be obtained and analysed. This clause presents the common status information to be obtained.
+
+- Status information about network entities in IMT-2020 signalling network includes hardware capacity, software capacity, real-time load, computing resources, storage resources, network resources and signalling process configuration.
+- Status information about signalling exchange between network entities, which refers to the status information of all signalling exchanges in an IMT-2020 signalling network, includes the signalling route mechanism, signalling transmission mechanism, signalling messages and their parameters, as well as fault code.
+
+## 7.3 Requirements for signalling network optimization in IMT-2020
+
+This clause presents the requirements for optimization of an IMT-2020 signalling network that is implemented based on the results of signalling network analysis.
+
+The requirements of signalling network optimization function are as follows:
+
+- By adjusting the configuration of network entities related to the signalling processes of IMT-2020 services, the performance of IMT-2020 signalling network can be improved.
+- By dynamically increasing resources for computing, storage and network of bottleneck network entities related to the signalling processes of IMT-2020 network services, their performance can be improved.
+- Optimization of the signalling exchange between the network entities is achieved by:
+ - adjusting signalling mechanisms for route selection, route fail-over and fallback, route re-selection and re-transmission;
+ - removing unnecessary or optional parameters in signalling exchange messages.
+- By locating overloaded or malfunctioning network entities in advance, disaster and fallback operations can be avoided in some cases; in this way, IMT-2020 signalling network performance can be improved.
+- A signalling network optimization function is required to support both manual and automatic operation based on optimization instructions.
+- A signalling network optimization function is required to support flexible extension capability to meet the various requirements of operators and adapt to the evolution of the IMT-2020 network. Both forward and backward compatibility issues are required to be addressed.
+- A signalling network optimization function is required not to influence the functions of the network entities in an IMT-2020 signalling network, also it is required to have no negative effects on the performance of the IMT-2020 signalling network.
+- A signalling network optimization function is required to locate the cause of an IMT-2020 signalling network malfunction, and adjust IMT-2020 signalling network configuration according to the reason for malfunction.
+- It is recommended that AI/ML technologies be used to assist in signalling network optimization.
+
+Operation of signalling network optimization has the following preconditions.
+
+- The quotas of a signalling network, status information about network entities and signalling exchange between network entities, which can reflect the network status and assist in the generation of optimization instructions, have been obtained by signalling network analysis.
+- Optimization instructions are machine- and human-readable messages that contain operational details, generated according to information from the signalling network analysis.
+- The network entities support dynamic configuration based on optimization instructions.
+- Signalling exchange between network entities supports dynamic configuration based on the optimization instructions.
+- The network entities and signalling exchange between them support a fallback mechanism if signalling network optimization fails or is invalid.
+- The network entities support the automatic generation of signalling network optimization reports for future reference or manual intervention.
+
+# 8 Framework of IMT-2020 signalling network analysis and optimization
+
+Figure 8-1 depicts a framework for signalling network analysis and optimization in an IMT-2020 network. The signalling network analysis and optimization system interacts with network entities and signalling exchange to implement for signalling, collection, network analysis and further network optimization. The results of signalling network analysis and optimization can be provided to users for
+
+IMT-2020 network maintenance or other uses. The AI platform is a recommended external system that provides AI capabilities to the signalling network analysis and optimization system. The architectural framework of AI platforms is specified in [ITU-T Y.3172].
+
+
+
+Figure 8-1 – Framework of IMT-2020 signalling network analysis and optimization. The diagram shows a 'User' connected to a '5G signalling network analysis and optimization system' via interface IF8. Inside the system, an 'AI assistance component' is connected to an external 'AI platform' via IF7. The AI assistance component is connected to three internal components: '5G signalling network optimization component' (via IF3-3), '5G signalling network analysis component' (via IF3-2), and '5G signalling collection component' (via IF3-1). These three components are interconnected by interfaces IF1, IF2, and IF3. The system is connected to 'SBA interfaces' via interfaces IF4, IF5, IF6, and IF4. Two network functions, 'NF1' and 'NF2', are shown below the SBA interfaces, connected by a dashed line labeled 'Reference points'. The diagram is labeled 'Q.5005(23)'.
+
+**Figure 8-1 – Framework of IMT-2020 signalling network analysis and optimization**
+
+In the framework, the IMT-2020 signalling network analysis and optimization system mainly consists of the following components.
+
+- IMT-2020 signalling collection component: A required component, which performs signalling collection on the IFs that are related to the signalling processes of IMT-2020 services, including SBIs and reference points between different network functions. It also collects the network statuses of network entities to ascertain their running conditions.
+- IMT-2020 signalling network analysis component: A required component, which performs analysis according to quotas, and executes network entities running status analysis. The input information for a signalling network analysis component is the information obtained in signalling collection. An IMT-2020 signalling network analysis component analyses information about the IMT-2020 signalling network based on operator-customized settings.
+- IMT-2020 signalling network optimization component: A required component, which performs IMT-2020 signalling network optimization on network functions and optimization of signalling exchange between network functions in an IMT-2020 signalling network, on the basis of signalling network analysis.
+- AI assistance component: A recommended component, which acts on an IMT-2020 signalling collection component, IMT-2020 signalling network analysis component and IMT-2020 signalling network optimization component to provide AI capabilities. It is recommended for an AI assistance component to use the AI capabilities of external AI platform with invoking IFs.
+
+In addition to the preceding components, the signalling network analysis and optimization system also provides common management and orchestration functions that comply with standards of management and orchestration elaborated by ITU-T and other standards development organizations.
+
+# 9 Interfaces and protocols of IMT-2020 signalling network analysis and optimization
+
+In the framework of IMT-2020 signalling network analysis and optimization system, five internal and five external IFs are addressed in this Recommendation, as follows:
+
+Internal IFs:
+
+- IF1: A required IF exists between an IMT-2020 signalling network analysis component and an IMT-2020 signalling collection component.
+- IF2: A required IF exists between an IMT-2020 signalling network optimization component and an IMT-2020 signalling network analysis component.
+- IF3-1: A recommended IF exists between an IMT-2020 signalling collection component and an AI assistance component.
+- IF3-2: A recommended IF exists between an IMT-2020 signalling network analysis component and an AI assistance component.
+- IF3-3: A recommended IF exists between an IMT-2020 signalling network optimization component and an AI assistance component.
+
+External IFs:
+
+- IF4: A required IF exists between an IMT-2020 signalling network analysis and optimization system, and network functions.
+- IF5: A required IF exists between an IMT-2020 signalling network analysis and optimization system, and SBIs between different network functions.
+- IF6: A required IF exists between an IMT-2020 signalling network analysis and optimization system, and reference points between different network functions.
+- IF7: A recommended IF exists between an AI assistance component of an IMT-2020 signalling network analysis and optimization system, and an external AI platform.
+- IF8: A required IF between an IMT-2020 signalling network analysis and optimization system, and the user, who will use result of signalling collection, signalling network analysis, and signalling network optimization.
+
+## 9.1 Signalling collection interfaces
+
+Signalling collection IFs include IF4, IF5 and IF6, described as follows:
+
+- IF4 is the IF between a signalling collection component and a network entity, which is used for raw data collection on network entities of an IMT-2020 signalling network, including hardware capacity, software capacity, real-time load, computing resources, storage resources, network resources and signalling process configuration.
+- IF5 is the IF for service-based signalling collection and signalling exchange between network entities.
+- IF6 is the IF between a signalling collection component and signalling exchange between network entities, which is used for raw data collection from signalling exchanges in an IMT-2020 signalling network.
+- The protocols of IF4, IF5, and IF6 could be shared data transfer protocol (SDTP) or other trusted protocols, which are required to ensure data integrity and security of raw data collection.
+
+IF4, IF5 and IF6 could be decoupled from an IMT-2020 signalling network or integrated with IMT-2020 signalling network entities, depending on different deployment demands.
+
+## 9.2 Signalling processing interfaces
+
+Signalling processing IFs include IF1 and IF2, and IF3-x, IF7, IF8, described as follows:
+
+- IF1 is the required IF between a signalling network analysis component and signalling collection component, which is used to upload decoding data, synthetic, and backfill data of a signalling network generated by the signalling collection component to the signalling network analysis component.
+- IF2 is the required IF between a signalling network optimization component and signalling network analysis component, which is used to upload the quotas and status information about a signalling network generated by the signalling network analysis component to the signalling network optimization component.
+- IF1 and IF2 are required to support the function of data reverse query. The protocol of these two IFs could be SDTP or other trustable protocols.
+- IF3-1, IF3-2 and IF3-3 are the recommended IFs between an AI/ML assistance component and other components in a IMT-2020 signalling analysis and optimization system, which are used for providing AI/ML-related capabilities in the processes of an IMT-2020 signalling analysis and optimization system.
+- IF7 is the recommended IF between an AI/ML assistance component and an external AI/ML platform, which is used to provide AI/ML-related capabilities of the external AI/ML platform to a signalling network analysis and optimization system.
+- IF3-1, IF3-2, IF3-3 and IF7 are recommended to adopt the protocol stack of HTTP, transmission control protocol (TCP) or IP to facilitate the invocation of external AI/ML-related capabilities.
+- IF8 is the required IF between an IMT-2020 signalling network analysis and optimization system and the user, who will use the results of signalling collection, signalling network analysis and signalling network optimization.
+- IF8 is recommended to adopt a user-friendly IF and protocol, such as an application programming IF or graphical IF, which adopts the protocol stack of HTTP, TCP or IP.
+
+# 10 Service procedures for IMT-2020 signalling network analysis and optimization
+
+After having collected original data of signalling and network status, the signalling collection component then generates raw data, including the single data, padding data and synthetic data of a complete IMT-2020 session. The signalling collection component then uploads the raw data to the signalling network analysis component, which uses it to process and analyse data. The signalling network analysis component then uploads the resulting quotas and status information to the signalling network optimization component, which uses that information to recognize the operational status of the signalling network, such as signalling fault and network entity breakdown, in order to develop corresponding solutions and instructions to optimize the IMT-2020 signalling network.
+
+The three components described in the previous paragraph interact with the AI assistance component to perform intelligent signalling collection, intelligent signalling network analysis, intelligent signalling network optimization, and intelligent self-management and self-orchestration.
+
+The signalling network analysis and optimization system provides the results of signalling collection, signalling network analysis, and signalling network optimization to users, if necessary.
+
+## 10.1 Signalling collection procedures
+
+The signalling collection procedures are as follows:
+
+Raw data collection from signalling exchange of an IMT-2020 signalling network is performed on IF5; the related IFs and detail network functions appear in clause 7.1.
+
+Raw data collection from network entities of an IMT-2020 signalling network is performed on IF4; related data includes hardware capacity, software capacity, real-time load, computing resources, storage resources, network resources, signalling process configuration and alarm information.
+
+Synthetic data is generated from raw data derived from a whole service session that is collected from different IFs.
+
+## **10.2 Signalling network analysis procedures**
+
+The signalling network analysis procedures are as follows:
+
+Raw and synthetic data are uploaded to the signalling network analysis component by signalling collection component, using IF1.
+
+The signalling network analysis component generates the quotas, calculation results and analysis of status information about the IMT-2020 signalling network. It then uploads these data to the signalling network optimization component by using IF2.
+
+The quota and status requirements for signalling network analysis appear in clauses 7.2 and 7.3.
+
+## **10.3 Signalling network optimization procedures**
+
+The signalling network optimization procedures are as follows:
+
+- Signalling network optimization on network entities.
+
+The signalling network optimization component dynamically adjusts the configuration of network entities according to the results of the analysis of their running status (including resource usage and alarm information). The reliability and stability of the IMT-2020 signalling network can be improved by dynamic adjustment of the configuration of network entities, increasing computing and storage resources appropriately and optimizing the mechanism of routing automatically. Furthermore, Figure 10-1 shows the process of signalling network optimization on network entities.
+
+- 1) The system dynamically and periodically monitors the analytical results of network functions in the IMT-2020 signalling network.
+- 2) The system compares the analytical results of the signalling network with threshold requirements, which are preconfigured in the signalling network optimization component. If analytical results satisfy threshold requirements, the system continues to monitor. If they do not, the system initiates the optimization of the signalling network on network entities.
+- 3) The system generates the optimization instructions for different network entities, e.g., modifying the signalling processing configuration, initiating the overload control mechanism and dynamically increasing the computing resources.
+- 4) The network entities execute the optimization instructions.
+- 5) The system checks the effect after optimization instructions have been executed on network entities. If quotas have been improved, the signalling network optimization ends this procedure and generates a success report. Then the system continues to monitor the analysis result. If they have not, the system instructs the appropriate network entities to fall back to their previous status and generates a failure report for manual operation. The system then continues to monitor the analytical results.
+
+
+
+```
+
+graph TD
+ A[Dynamically and periodically monitors the analysis result of signalling network] --> B{Checks if the analysis results of signalling network comply with the threshold requirements}
+ B -- Yes --> A
+ B -- No --> C[The system generates the optimization instructions]
+ C --> D[The network functions execute the optimization instructions]
+ D --> E{Checks if the quotas have been improved after optimization instruction}
+ E -- Yes --> F([End])
+ E -- No --> G([Network functions fallback])
+ G --> A
+ style F fill:none,stroke:none
+ style G fill:none,stroke:none
+
+```
+
+Q.5005(23)
+
+Flowchart of the signalling network optimization process. The process starts with 'Dynamically and periodically monitors the analysis result of signalling network', which leads to a decision 'Checks if the analysis results of signalling network comply with the threshold requirements'. If 'Yes', it loops back to the start. If 'No', it proceeds to 'The system generates the optimization instructions', then 'The network functions execute the optimization instructions', and then to a decision 'Checks if the quotas have been improved after optimization instruction'. If 'Yes', it ends at 'End'. If 'No', it proceeds to 'Network functions fallback', which then loops back to the start. The reference 'Q.5005(23)' is at the bottom right.
+
+**Figure 10-1 – The process of signalling network optimization on network functions**
+
+- Optimization of signalling exchange between network entities
+
+Information about exchange signalling is collected and analysed by the signalling collection component and signalling network analysis component, respectively. The optimization instructions are generated by the signalling network optimization component and applied to signalling exchange between network entities in IMT-2020 network; the corresponding effect of optimization is received by using IF5 and IF6. Figure 10-2 depicts the process of optimization of signalling exchange between network entities.
+
+- 1) The system of signalling network optimization dynamically and periodically monitors the analytical results of the signalling network analysis component.
+- 2) The system compares the analytical results with threshold requirements that have been configured in the system. If quotas satisfy the threshold requirements, the system continues to monitor. If they do not, the system determines aspects for improvement and initiates the corresponding operation of optimization for signalling exchange between network entities.
+- 3) The system generates the optimization instructions for related signalling exchange, e.g., adjusting the signalling route selection mechanism, adjusting the signalling re-transmission mechanism and removing unnecessary or optional parameters in signalling messages.
+- 4) The network entities that are related to the signalling exchange perform optimization based on the optimization instructions.
+- 5) The system checks the effect of optimization of signalling exchange between network entities. If quotas have been improved, the signalling network optimization ends this procedure and generates a success report. Then the system continues to monitor the analysis result. If they have not, the system instructs the appropriate network entities to fall back to
+
+their previous status, and generates a failure report for manual operation, then the system continues to monitor the analytical results.
+
+
+
+```
+graph TD; A[Dynamically and periodically monitors the analysis result of signalling network] --> B{Checks if the analysis results of signalling network comply with the threshold value requirements}; B -- Yes --> A; B -- No --> C[The system generates the optimization instructions on signalling exchange between network functions]; C --> D[Executes the optimization instructions on signalling exchange between network functions]; D --> E{Checks if the quotas have been improved after optimization instruction executed}; E -- Yes --> F([End]); E -- No --> G([Fallback]); G --> A;
+```
+
+The flowchart illustrates the process of optimization of signalling exchange between network functions. It begins with a rectangular box labeled 'Dynamically and periodically monitors the analysis result of signalling network'. An arrow points down to a decision diamond labeled 'Checks if the analysis results of signalling network comply with the threshold value requirements'. If 'Yes', the flow loops back to the top box. If 'No', it proceeds to a rectangular box labeled 'The system generates the optimization instructions on signalling exchange between network functions', which then leads to another rectangular box labeled 'Executes the optimization instructions on signalling exchange between network functions'. From there, it goes to a decision diamond labeled 'Checks if the quotas have been improved after optimization instruction executed'. If 'Yes', it ends at an oval labeled 'End'. If 'No', it goes to an oval labeled 'Fallback', which then loops back to the top box. The text 'Q.5005(23)' is located at the bottom right of the diagram.
+
+Flowchart of the optimization process for signalling exchange between network functions.
+
+**Figure 10-2 – The process of optimization of signalling exchange between network functions**
+
+## **10.4 AI/ML-related procedures**
+
+The AI/ML-related procedures are as follows:
+
+- The AI/ML-related capabilities are invoked, mapped and utilized in the processes of signalling collection with the support of the AI assistance component by using IF7 and IF3-1.
+- The AI/ML-related capabilities are invoked, mapped and utilized in the processes of signalling network analysis with the support of the AI assistance component by using IF7 and IF3-2.
+- The AI/ML-related capabilities are invoked, mapped and utilized in the processes of signalling network optimization with the support of the AI assistance component, by using IF7 and IF3-3.
+
+# **11 AI-assisted functions of IMT-2020 signalling network analysis and optimization**
+
+The AI-assisted functions are provided by newly deployed AI capabilities contained in the AI assistance component of the IMT-2020 signalling network analysis and optimization system, or by existing AI capabilities contained in external AI platform. The requirements for AI capabilities are as follows:
+
+## **11.1 Requirements for AI capabilities provided by the AI assistance component**
+
+The requirements for AI capabilities provided by the AI assistance component are as follows:
+
+- intelligent signalling collection functions;
+- intelligent signalling network analysis functions;
+- intelligent signalling network optimization functions;
+- intelligent system self-management and self-orchestration functions.
+
+#### **11.1.1 Intelligent signalling collection functions**
+
+The intelligent signalling collection functions are as follows:
+
+- to manage the facilities of data collection and data storage to ensure high reliability and high efficiency;
+- to collect the signalling data and network status information related to the IMT-2020 service procedure for some given inputs;
+- to process and store mass raw data collected from the IMT-2020 signalling network;
+- to search the signalling data related to the analysed IMT-2020 service procedure;
+- to search the network status data related to the analysed IMT-2020 service procedure.
+
+#### **11.1.2 Intelligent signalling network analysis functions**
+
+The intelligent signalling network analysis functions are as follows:
+
+- to chain the signalling related to the IMT-2020 service procedure for some given inputs;
+- to specify the IMT-2020 service procedures related to a given optimization target;
+- to support the definition and self-learning of the data model for specific network problems;
+- to specify the existing network problems based on the data model and the analysis of collected signalling data and status information of IMT-2020 signalling network.
+
+#### **11.1.3 Intelligent signalling network optimization functions**
+
+The intelligent signalling network optimization functions are as follows:
+
+- to provide the optimization solutions and corresponding optimization instructions to solve the existing network problems or for the given optimization target;
+- to predict the results of the given optimization solutions and corresponding optimization instructions;
+- to choose the best optimization solution based on the experience of experts or optimization records.
+
+#### **11.1.4 Intelligent self-management and self-orchestration functions**
+
+The intelligent self-management and self-orchestration functions are as follows:
+
+- to achieve self-management of components of the signalling network analysis and optimization system;
+- to achieve self-management of internal IFs and external IFs of the signalling network analysis and optimization system;
+- to achieve self-orchestration of hardware resources and software resources of the signalling network analysis and optimization system;
+- to customize the capabilities of the signalling network analysis and optimization system on demand.
+
+## 11.2 Requirements for AI capabilities provided by external AI platform
+
+The requirements for AI capabilities provided by external AI platform are as follows:
+
+- Function of connecting with an external AI platform
+
+Providing the IFs for interacting with external AI/ML platforms.
+
+Managing the available external AI/ML platform(s) and external AI/ML-related capabilities.
+
+Invoking the external AI/ML-related capabilities based on the requirements of the signalling collection component, signalling network analysis component, and signalling network optimization component.
+
+Receiving the optimized policies or solutions from external AI/ML platforms that are authorized.
+
+Choosing the best-suited external AI/ML platform for a specific AI/ML-related capability, when multiple external AI/ML platforms are available.
+
+- Function mapping with external AI platform
+
+Adapting the protocol that is used for interaction with an external AI/ML platform.
+
+Managing the functions of an external AI/ML platform, which is used for extension, or use the capabilities of the signalling network analysis and optimization system.
+
+Performing protocol transition between components of the signalling network analysis and optimization system.
+
+# 12 Security considerations
+
+Security considerations of the IMT-2020 signalling network analysis and optimization system are as follows:
+
+- Information security
+
+To ensure information security for both user and network, the information obtained in the processes of signalling collection, signalling network analysis and signalling network optimization in IMT-2020 should be protected from leakage, unauthorized access and misuse, with the application of mature technologies of access control, authentication and authorization, transport security and data encryption.
+
+- Network operation security
+
+To ensure the security of telecommunications network operation, the functions of the network entities in an IMT-2020 signalling network should not be influenced in the processes of signalling collection, signalling network analysis and signalling network optimization. In addition, signalling network optimization should not have negative effects on the performance of a VoLTE signalling network, both on network entities themselves and signalling exchange between them.
+
+- Equipment security
+
+The equipment shall provide effective safety and confidentiality measures: to ensure the safety of the system and data resources; and to prevent the illegal intrusion into system resources.
+
+- System component security
+
+Signalling collection security considers signalling data collection security and network status data collection security.
+
+Signalling network analysis security considers quota analysis security and network status information analysis security.
+
+Signalling network optimization security considers security of optimization on network entities and optimization on signalling exchange.
+
+AI/ML-related security considers on intelligent signalling collection security, intelligent signalling network analysis security, intelligent signalling network optimization security, intelligent self-management and self-orchestration security, external AI/ML platform connecting security and external AI/ML capability mapping security.
+
+The security and privacy considerations of signalling network analysis and optimization should be aligned with the requirements specified in [ITU-T Y.2701] and [ITU-T Y.3101].
+
+# Bibliography
+
+[b-ITU-T Y.3100] Recommendation ITU-T Y.3100 (2017), *Terms and definitions for IMT-2020 network*.
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling, and associated measurements and tests |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.5032-202406-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c9bf6b58e0db42f57a3a53f73cd133e76d767a41
--- /dev/null
+++ b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ffb3da47afeb2f322c82f0137dd9848cca7fd790490f8721e2a4eca4c2aefab0
+size 14169
diff --git a/marked/Q/T-REC-Q.5032-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb
--- /dev/null
+++ b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3763acd7a0ed56aa30f3f90468c1fb0cb54573eb9045bca3eddf8976b4f0f41d
+size 7219
diff --git a/marked/Q/T-REC-Q.5032-202406-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..657525780a9c060dd9c457e548a6797299d8ffe8
--- /dev/null
+++ b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dcc09dc03fcffca939013d981efc19f03375127f9f666b022dc8ac5dc3d4fad3
+size 28291
diff --git a/marked/Q/T-REC-Q.5032-202406-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..51fc8d99335efa052b7bdb7af1289897686c1221
--- /dev/null
+++ b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d474b34c1b44e00b77779709b14468bf8b6a179abf75732bbd7c47ec64a5c7db
+size 52255
diff --git a/marked/Q/T-REC-Q.5032-202406-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..376cc2e31fe94c7e628d91aefb68a0d03e68d703
--- /dev/null
+++ b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d5dfea12d27c3c9559a86a5be64a49cd3989946ed9badea3af6c60857860ed85
+size 7064
diff --git a/marked/Q/T-REC-Q.5032-202406-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..333e6a88bf153ccb167af1807bffc6edd3e1827c
--- /dev/null
+++ b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e6a04e192452044ef8401a47a4202e6f3b198735d4ad4ed5380b012888639293
+size 18781
diff --git a/marked/Q/T-REC-Q.5032-202406-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b262985b22ed538098b690df1f36bd8f3bdcce2b
--- /dev/null
+++ b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b99378c2155d20c41146ae9cadab780838413044aba4696329ed58ef760c56ca
+size 62231
diff --git a/marked/Q/T-REC-Q.5032-202406-I_PDF-E/5a95b187de0044da69b7322e04761b86_img.jpg b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/5a95b187de0044da69b7322e04761b86_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3fe4c302d576b6b200baa5e54515d06bea29068f
--- /dev/null
+++ b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/5a95b187de0044da69b7322e04761b86_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:06566983b09861a930c40b4f51f429f310a6f3f132726207db8be2d926c29831
+size 39553
diff --git a/marked/Q/T-REC-Q.5032-202406-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..79afeb62451d10cc7f5996a23dceb79b6ff67b56
--- /dev/null
+++ b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8d6d97193726bec70e30f1675ea126df86ec88a0152adde2d82a0668ca0dcabb
+size 46017
diff --git a/marked/Q/T-REC-Q.5032-202406-I_PDF-E/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b03346954196e98c813b37f5b60485e84dae827f
--- /dev/null
+++ b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ccea5a9c1ea0a31217db6955f23af02e14ffb19237712149afd741526f9c4f0a
+size 24290
diff --git a/marked/Q/T-REC-Q.5032-202406-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..904853adf7c924706171fc9eb6e72943140199d7
--- /dev/null
+++ b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e8c918b31ca7e56d9e912ed1bfdd493a1ca3726cf8e2366e67fe7ea5fa1f3af7
+size 16941
diff --git a/marked/Q/T-REC-Q.5032-202406-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..81e40059de4dfd366b0bf77397da9839c4ec54cf
--- /dev/null
+++ b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:370231d6fa19edc843f5be8e3582d64b22620aa587e0b8f4c2b61bb1be2a2029
+size 51595
diff --git a/marked/Q/T-REC-Q.5032-202406-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8da726a05bef6d46705b89234202b6faf78cd00c
--- /dev/null
+++ b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a4508ad3a53da4d01762eb704ca72d82ec9a384f582881466aaf0d35abd6581b
+size 23361
diff --git a/marked/Q/T-REC-Q.5032-202406-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..709c6a507f771b121962810d125c1a085eed9b29
--- /dev/null
+++ b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a11ce3388c61edb478f02cfe1cbf78f7808a9f5aac0d6a03938d493c61312bcb
+size 12099
diff --git a/marked/Q/T-REC-Q.5032-202406-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e9fac74ec868cf6e75dbb1aa5557b0bdbfe4861e
--- /dev/null
+++ b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1982d8f2f7fa9c6e124787478334c9a709a6defc5fcceebfc79b3ed8accd758c
+size 28740
diff --git a/marked/Q/T-REC-Q.5032-202406-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0f98219542c8ab88fc439e061462964e324db903
--- /dev/null
+++ b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e2d1f9c08b7195fd1f8459f5a7189b38a9e87c8e0a193f8e30eccb4f57d31be
+size 9133
diff --git a/marked/Q/T-REC-Q.5032-202406-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2218d9679b789348f8850d8f1f130996e1bc02bc
--- /dev/null
+++ b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fa3a604e289ada6c726ddd054fdb90757036ced9110593137005055eed0f8a8f
+size 22553
diff --git a/marked/Q/T-REC-Q.5032-202406-I_PDF-E/raw.md b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..7003a559ab2d33e374f70196a09791a7744be172
--- /dev/null
+++ b/marked/Q/T-REC-Q.5032-202406-I_PDF-E/raw.md
@@ -0,0 +1,625 @@
+
+
+# Recommendation**ITU-T Q.5032 (06/2024)**
+
+SERIES Q: Switching and signalling, and associated measurements and tests
+
+Signalling requirements and protocols for IMT-2020 –
+Protocols for IMT-2020
+
+# --- **Network coding protocol for network repeaters**
+
+
+
+The logo of the International Telecommunication Union (ITU), featuring the letters 'ITU' in blue inside a circle with a globe-like pattern.
+
+ITU logo
+
+## ITU-T Q-SERIES RECOMMENDATIONS
+
+## **Switching and signalling, and associated measurements and tests**
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS NO. 4, 5, 6, R1 AND R2 | Q.120-Q.499 |
+| DIGITAL EXCHANGES | Q.500-Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM NO. 7 | Q.700-Q.799 |
+| Q3 INTERFACE | Q.800-Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 1 | Q.850-Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 |
+| INTELLIGENT NETWORK | Q.1200-Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 |
+| BROADBAND ISDN | Q.2000-Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900-Q.4099 |
+| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100-Q.4139 |
+| PROTOCOLS AND SIGNALLING FOR COMPUTING POWER NETWORKS | Q.4140-Q.4159 |
+| PROTOCOLS AND SIGNALLING FOR QUANTUM KEY DISTRIBUTION NETWORKS | Q.4160-Q.4179 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000-Q.5049 |
+| Signalling requirements and architecture of IMT-2020 | Q.5000-Q.5019 |
+| Protocols for IMT-2020 | Q.5020-Q.5049 |
+| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050-Q.5069 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T Q.5032
+
+# Network coding protocol for network repeaters
+
+## Summary
+
+Recommendation ITU-T Q.5032 considers networks with repeaters. A repeater is usually a device designed to receive a signal from a remote transmitter and then retransmit this signal to a remote receiver that is unable to receive a signal from the original transmitter without retransmission due to certain conditions, for example, due to too large a distance, transmission medium, low power of the source signal, or other reasons. Implementation of network coding at a repeater with a two-way relay channel allows us to reduce the network load and, consequently, data transmission delays in such networks.
+
+This Recommendation includes:
+
+- description of a network architecture where the protocol could be implemented;
+- coding and decoding procedures;
+- packet types and formats;
+- signalling procedures and diagrams.
+
+## History\*
+
+| Edition | Recommendation | Approval | Study Group | Unique ID |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0 | ITU-T Q.5032 | 2024-06-29 | 11 | 11.1002/1000/15982 |
+
+## Keywords
+
+Network coding, protocol.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at .
+
+© ITU 2024
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|-----------------------------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 3.2 Terms defined in this Recommendation..... | 1 |
+| 4 Abbreviations and acronyms ..... | 1 |
+| 5 Conventions ..... | 2 |
+| 6 Overview ..... | 2 |
+| 7 Network coding ..... | 3 |
+| 7.1 The principle of network coding ..... | 3 |
+| 7.2 Retransmission with network coding ..... | 3 |
+| 7.3 Application of network coding in transmission networks..... | 4 |
+| 8 NCRP description ..... | 4 |
+| 8.1 Protocol header structure ..... | 4 |
+| 8.2 Protocol header for the general case..... | 6 |
+| 8.3 Packet exchange procedure ..... | 9 |
+| Appendix I – Use case for NCRP protocol ..... | 10 |
+| Bibliography..... | 11 |
+
+
+
+# Recommendation ITU-T Q.5032
+
+## Network coding protocol for network repeaters
+
+# 1 Scope
+
+This Recommendation provides information about a network coding protocol for network repeaters. The aim of the new protocol is to reduce the network load in the networks with repeaters.
+
+# 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 term defined elsewhere:
+
+**3.1.1 network coding** [b-IETF RFC 8406]: A system where coding can be performed at the source as well as at intermediate forwarding nodes (all or a subset of them).
+
+## 3.2 Terms defined in this Recommendation
+
+None.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|--------|-----------------------------------------------|
+| D2D | Device-to-Device |
+| FL | Field Length |
+| FT | Field Type |
+| FV | Field Value |
+| HT | Header Type |
+| IP | Internet Protocol |
+| LoRa | Long Range |
+| LP-WAN | Low-Power Wide Area Network |
+| NC | Network Coding |
+| NCRP | Network Coding Protocol for network Repeaters |
+| OSI | Open Systems Interconnection model |
+| TCP | Transmission Control Protocol |
+
+TWRC Two-Way Relay Channel
+ UDP User Datagram Protocol
+
+# 5 Conventions
+
+None.
+
+# 6 Overview
+
+Emerging access networks can be designed not only as star networks but also using mesh topologies, as well as D2D technologies. At the same time, in such networks the question of reducing network load and, consequently, network delays are quite acute.
+
+A repeater is usually a wireless device designed to receive a signal from a remote transmitter and then retransmit this signal to a remote receiver that is unable to receive a signal from the original transmitter without retransmission due to certain conditions, for example, due to too large a distance, transmission medium, low power of the source signal or other reasons. Repeaters are used in conventional voice radio and telephony and in modern wireless data transmission systems.
+
+In the case when a repeater uses omnidirectional antennas for reception and transmission and data packets are transmitted in both directions, the situation presented in Figure 1 arises. Such a transmission scheme is called a two-way relay channel (TWRC). For clarity, we assume that the transmission is carried out on the same carrier frequency with a time duplex (half duplex) and a time interval $\Delta t$ is a time slot length (time allocated for the transmission of each packet). Thus, when node $N_1$ sends a data packet $P_1$ to node $N_2$ , repeater $R$ retransmit it, and packet $P_1$ reaches both nodes $N_2$ and $N_1$ . This requires two time slots; a similar situation occurs when node $N_2$ sends a $P_2$ packet to node $N_1$ . In total, four time slots with a total duration of four $\Delta t$ will be required to transmit two packets.
+
+
+
+The diagram illustrates the sequence of packet transmissions between two nodes $N_1$ and $N_2$ via a repeater $R$ over four discrete time intervals:
+
+- $\Delta t_1$ : Node $N_1$ transmits packet $P_1$ to repeater $R$ .
+- $\Delta t_2$ : Repeater $R$ broadcasts packet $P_1$ to both $N_1$ and $N_2$ .
+- $\Delta t_3$ : Node $N_2$ transmits packet $P_2$ to repeater $R$ .
+- $\Delta t_4$ : Repeater $R$ broadcasts packet $P_2$ to both $N_1$ and $N_2$ .
+
+Vertical dashed lines represent the timeline for each node, ending in an arrow labeled $t$ . Horizontal arrows indicate the direction of packet flow. A reference label Q.5032(24) is located at the bottom right.
+
+Figure 1: Repeater operation without network coding. A sequence diagram showing three vertical timelines for nodes N1, R, and N2. Time flows downward. In slot Δt1, an arrow goes from N1 to R with packet P1. In slot Δt2, arrows go from R to both N1 and N2 with packet P1. In slot Δt3, an arrow goes from N2 to R with packet P2. In slot Δt4, arrows go from R to both N1 and N2 with packet P2.
+
+**Figure 1 – Repeater operation without network coding**
+
+It should be noted that this scheme with the repeater could also represent the wireless networks with the star topology in cases of multicast data transmission, where all data transmission is conducted through the central node $R$ .
+
+This Recommendation represents the application of a network coding procedure at repeaters in order to reduce the number of packets transmitted in the channel and thereby reduce the packet delivery delay in a system with a repeater.
+
+## Protocol placement
+
+A network coding protocol for network repeaters (NCRP) is a transport layer protocol enabling the transmission of user data (and application layer protocols) between network nodes using repeaters. It should be noted that NCRP can operate on top of conventional transport protocols, on top of network protocols or on top of link layer technology if the operation of the implemented repeater
+
+system does not require the use of a separate network protocol. This depends on the data transfer technology and protocol stack used. The latter approach can be used, for instance, when using wireless technology, like LP-WAN, as a method of data transfer. The positioning of the protocol is shown in Figures 2, 3 and 4.
+
+
+
+| |
+|-----------------|
+| NCRP protocol |
+| Transport layer |
+| Network layer |
+| Data link layer |
+
+Q.5032(24)
+
+**Figure 2 – NCPR works on the top of transport layer**
+
+
+
+| |
+|-----------------|
+| NCRP protocol |
+| Network layer |
+| Data link layer |
+
+Q.5032(24)
+
+**Figure 3 – NCRP works on the top of network layer**
+
+
+
+| |
+|-----------------|
+| NCRP protocol |
+| Data link layer |
+
+Q.5032(24)
+
+**Figure 4 – NCPR works on the top of data link layer**
+
+# 7 Network coding
+
+## 7.1 The principle of network coding
+
+[b-IETF RFC 8406] defines network-encoded transmission systems as a system where coding can be performed at the source as well as at intermediate forwarding nodes (all or a subset of them). In this case, coding is a reversible linear transformation of two or more data packets by means of mathematical operations such as a bitwise modulo 2 addition as the simplest reversible operation.
+
+Let us consider the network encoding procedure with two source packets $P_1$ and $P_2$ . The result of network encoding is represented by a packet:
+
+$$P_{NC} = P_1 \oplus P_2 \quad (1)$$
+
+where $\oplus$ is a bitwise modulo 2 addition or an "exclusive-or" (XOR) operation.
+
+Given the reversibility of the bitwise modulo 2 addition, with the encoded packet $P_{NC}$ and one of the original packets, it is possible to restore the second original packet:
+
+$$\begin{cases} P_1 \oplus P_{NC} = P_1 \oplus P_1 \oplus P_2 = P_2; \\ P_2 \oplus P_{NC} = P_2 \oplus P_1 \oplus P_2 = P_1. \end{cases} \quad (2)$$
+
+## 7.2 Retransmission with network coding
+
+The application of network coding at the repeater in the TWRC is represented by the scheme in Figure 5.
+
+
+
+Figure 5 – Repeater operation network coding. The diagram shows three nodes: N1, R (repeater), and N2. Time slots are labeled Δt1, Δt2, and Δt3. In Δt1, N1 sends packet P1 to R. In Δt2, N2 sends packet P2 to R. In Δt3, R sends the network-coded packet P\_NC = P1 ⊕ P2 to both N1 and N2. Vertical arrows labeled 't' indicate the progression of time.
+
+**Figure 5 – Repeater operation network coding**
+
+As in Figure 1, node $N_1$ transmits packet $P_1$ to repeater $R$ , node $N_2$ transmits packet $P_2$ to repeater $R$ , and each transmission occupies one time slot $\Delta t$ . After receiving the packets, the repeater $R$ performs the network encoding procedure $P_{NC}=P_1\oplus P_2$ and sends the result to both recipients simultaneously, which takes another time slot. Each of the recipients, knowing one of the original packets, restores the second packet. Thus, packet transmission requires only three time slots and has a duration of $3\Delta t$ .
+
+As can be seen from the above, the development and implementation of the NCRP will reduce the network load and, consequently, data transmission delays.
+
+It should be noted that when using network encoding, the repeater and the end nodes must have memory buffers to store packets until they are used for network encoding on the repeater or decoding the received packets on the end nodes.
+
+## 7.3 Application of network coding in transmission networks
+
+Network coding in communication networks is usually implemented in special network protocols. Currently, there are a significant number of network coding protocols designed for use in wired and wireless data transmission systems.
+
+In order to use network encoding in a network with a repeater, it is necessary, in addition to payload data, to transmit service information necessary for the correct encoding and decoding of packets. Thus, there is a task of developing an NCRP that ensures the operation of network coding in the network.
+
+Since network encoding can be used with various wireless transmission technologies, the repeater protocol must also be universal and extensible.
+
+To solve this problem, this Recommendation proposes an NCRP designed to work in networks with repeaters.
+
+# 8 NCRP description
+
+## 8.1 Protocol header structure
+
+Based on the principles of network coding and the operation of the relay system discussed above, the following three parameters are important for each packet of the NCRP:
+
+- end node identifier;
+- packet order number so that the node knows which outgoing packet to use for decoding;
+- data block length in case it can be different in different packets.
+
+Since the NCRP protocol is supposed to be used in conjunction with various wireless technologies and protocols working on top of them, it should be kept in mind that some of the necessary information may already be transmitted in the headers of other protocols. Also, some technologies may have a fixed data block size, which, accordingly, does not need to be specified in the header of
+
+the repeater protocol in this case. In addition, some wireless technologies have limitations on the size of the transmitted packet. Therefore, the NCRP header should have a variable size and dynamic structure, which allows it to be adjusted to a specific protocol stack and reduce redundancy.
+
+The correct processing of a variable-sized header consisting of optional fields can be organized in two ways:
+
+- three-parameter fields organized according to the "type-length-value" scheme;
+- predefined sequence of fields with a general indication of presence.
+
+These approaches do not contradict each other and could be applied in parallel in the NCRP, which allows us to choose the way to organize the NCRP packets depending on the features of the underlying protocols and technologies. The choice of a specific scheme is carried out by the Header Type (HT) flag.
+
+The general structure of the NCRP header is shown in Figure 6. The header consists of a mandatory part consisting of the technology field indicating the transmission technology used, a Header Type (HT) flag and a Network Coding (NC) flag, and a variable part containing the fields, required for network encoding and decoding.
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------|---|---|---|---|----|----|-------------------------|---|---|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|
+| 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 |
+| Technology | | | | | HT | NC | Variable part of header | | | | | | | | | | | | | | | | | | | | | | | | |
+
+Q.5032(24)
+
+Diagram of the general structure of the NCRP header showing bit fields for Technology, HT, NC, and the Variable part of the header.
+
+**Figure 6 – General structure of the NCRP header**
+
+The technology field represents the transmission technology and allows us to vary the number of fields necessary for the system operation and their size. Since the total number of wireless technologies currently used and at the same time structurally and logically allowing us to work in a network with a repeater is relatively small and some technologies require the same sets of fields, 5 bits are used for their numbering, allowing one of the 32 possible technologies to be chosen. The total size of the required part of the header is 1 byte. One bit is left for potential expansion and can be used as an additional flag or can expand the technology field if necessary. The Header Type flag should be set as "0" for three-parameter fields and "1" for a predefined sequence of fields.
+
+The variable part of the header based on three-parameter fields is shown in Figure 7.
+
+
+
+| | | | | | | | | | | | | | | | |
+|------------|---|---|---|--------------|---|---|---|-------------|---|----|----|----|----|----|----|
+| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 |
+| Field type | | | | Field length | | | | Field value | | | | | | | |
+| Field type | | | | Field length | | | | Field value | | | | | | | |
+| | | | | | | | | | | | | | | | |
+| Field type | | | | Field length | | | | Field value | | | | | | | |
+
+Q.5032(24)
+
+Diagram of the variable part of the header based on three-parameter fields, showing repeating Field type, Field length, and Field value segments.
+
+**Figure 7 – The variable part of the header of three-parameter fields**
+
+Each field consists of three parameters:
+
+- Field Type (FT)
+- Field Length (FL)
+- Field Value (FV).
+
+This approach is universal and easily extensible but introduces additional overhead. In the NCRP, the size of the field type parameter is set to 4 bits, which allows numbering up to 16 field types. The
+
+Field Length parameter is also equal to 4 bits, allowing us to specify fields with a value up to 16 bytes long. Thus, for each transmitted field there is an overhead equal to 1 byte.
+
+The variable part of the header with a predefined sequence of fields is shown in Figure 8.
+
+
+
+| | | | |
+|-------------|-----|---------|---------|
+| Field flags | | Field 1 | Field 2 |
+| Field 3 | ... | | |
+
+Q.5032(24)
+
+**Figure 8 – The variable part of the header with a predefined fields sequence**
+
+The Field Flags field contains bit flags indicating the presence or absence of the following value fields. The size of the Field Flags field depends on the required number of value fields; therefore, it depends on the data transmission technology.
+
+## 8.2 Protocol header for the general case
+
+An NCRP header for a relay system is set up in a star topology with a straightforward channel transmission method. Let us make the supposition that the transmission technology frame has a sync preamble and a data field where the NCRP packet will be sent. The NCRP will function as a channel protocol in this scenario.
+
+In this instance, it is assumed that the Technology field has a value of 0.
+
+For the star topology, in which there may be more than two end nodes in the network, device addressing is required. As an illustration, consider the device's 6-byte MAC address as the end node address.
+
+The length of the encoded data field and the packet number must be transmitted in addition to the address, as was already established. Consider the case where the data block size is equal to the size of the IP packet and the length of the data block may be encoded using a 2-byte field. A 2-byte field similarly controls packet numbering, allowing for cyclic numbering of up to 65536 packets without duplicating the number.
+
+Therefore, before network encoding, the following information would need to be included in the NCRP packet header:
+
+- 1) receiver address (1);
+- 2) sender address (5);
+- 3) package number (9);
+- 4) data field length (13);
+- 5) data.
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------|--|--|--|--------|---|---|--------|----------------|--|--------|--|--|--|------------------|--|---------|--|--|--|--------|--|--|--|-------------|--|--|--|--------|--|--|--|
+| 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 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Tech = 0 | | | | | 0 | 0 | FT = 1 | | | FL = 6 | | | | Receiver address | | | | | | | | | | | | | | | | | |
+| Receiver address | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| FT = 5 | | | | FL = 6 | | | | Sender address | | | | | | | | | | | | | | | | | | | | | | | |
+| Sender address | | | | | | | | | | | | | | | | | | | | | | | | FT = 9 | | | | FL = 2 | | | |
+| Packet number | | | | | | | | | | | | | | | | FT = 13 | | | | FL = 2 | | | | Data length | | | | | | | |
+| Data length | | | | | | | | Data ... | | | | | | | | | | | | | | | | | | | | | | | |
+
+Q.5032(24)
+
+**Figure 9 – Format of an NCRP packet header with three parameter fields before network coding**
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------|--|--|--|--|---|---|--|--|--|--|--|---|---|---|---|------------------|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|
+| 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 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Tech = 0 | | | | | 1 | 0 | | | | | | 1 | 1 | 1 | 1 | Receiver address | | | | | | | | | | | | | | | |
+| Receiver address | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Sender address | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Sender address | | | | | | | | | | | | | | | | Packet number | | | | | | | | | | | | | | | |
+| Data length | | | | | | | | | | | | | | | | Data ... | | | | | | | | | | | | | | | |
+
+Q.5032(24)
+
+**Figure 10 – NCRP packet header format before network coding with predetermined field sequence**
+
+According to Figure 10, the Field Flags field's 8 bits, which represent its length, are allocated as the following 4 insignificant bits:
+
+FDL flag = 1 – the Data length field is present
+
+FPN flag = 1 – the Packet number field is present
+
+FSA flag = 1 – the Sender address field is present
+
+FRA flag = 1 – the Receiver address field is present
+
+You must include the following fields in the NCRP packet header following network encoding on the repeater:
+
+- 1) receiver address 1 (1);
+- 2) sender address 1 (5);
+- 3) package number 1 (9);
+- 4) data field length 1 (13);
+- 5) receiver address 2 (2);
+- 6) sender address 2 (6);
+- 7) package number 2 (10);
+- 8) data field length 2 (14);
+- 9) data.
+
+Figures 11 and 12 illustrate the form of the NCRP packet header following network encoding with three-parameter fields and an identified field sequence, respectively.
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------|--|--|--|--------|--|--------|--|--------------------|--|--------|--|--------|--|--------------------|--|---------------|--|--|--|--------|--|--|--|-----------------|--|--|--|--------|--|--|--|
+| 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 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Tech = 0 | | | | 0 1 | | FT = 1 | | | | FL = 6 | | | | Receiver 1 address | | | | | | | | | | | | | | | | | |
+| Receiver 1 address | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| FT = 2 | | | | FL = 6 | | | | Receiver 2 address | | | | | | | | | | | | | | | | | | | | | | | |
+| Receiver 2 address | | | | | | | | | | | | | | | | | | | | | | | | FT = 5 | | | | FL = 6 | | | |
+| Sender 1 address | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Sender 1 address | | | | | | | | | | | | | | | | FT = 9 | | | | FL = 2 | | | | Packet 1 number | | | | | | | |
+| Packet 1 number | | | | | | | | FT = 13 | | | | FL = 2 | | | | Data 1 length | | | | | | | | | | | | | | | |
+| FT = 6 | | | | FL = 6 | | | | Sender 2 address | | | | | | | | | | | | | | | | | | | | | | | |
+| Sender 2 address | | | | | | | | | | | | | | | | | | | | | | | | FT = 10 | | | | FL = 2 | | | |
+| Packet 2 number | | | | | | | | | | | | | | | | FT = 14 | | | | FL = 2 | | | | Data 2 length | | | | | | | |
+| Data 2 length | | | | | | | | Data ... | | | | | | | | | | | | | | | | | | | | | | | |
+
+Q.5032(24)
+
+**Figure 11 – Three-parameter NCRP packet header structure after network encoding**
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------|--|--|--|-------------------------|--|--|--|--|--|--|--|--|--|--|--|--------------------|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|
+| 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 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Tech = 0 | | | | 1 1 1 1 1 1 1 1 1 1 1 1 | | | | | | | | | | | | Receiver 1 address | | | | | | | | | | | | | | | |
+| Receiver 1 address | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Receiver 2 address | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Receiver 2 address | | | | | | | | | | | | | | | | Sender 1 address | | | | | | | | | | | | | | | |
+| Sender 1 address | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Packet 1 number | | | | | | | | | | | | | | | | Data 1 length | | | | | | | | | | | | | | | |
+| Sender 2 address | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Sender 2 address | | | | | | | | | | | | | | | | Packet 2 number | | | | | | | | | | | | | | | |
+| Data 2 length | | | | | | | | | | | | | | | | Data ... | | | | | | | | | | | | | | | |
+
+Q.5032(24)
+
+**Figure 12 – Form of an NCRP packet header with preset fields after network encoding**
+
+So that end nodes can immediately process them and discard packets that are not intended for them, destination addresses are listed first.
+
+According to Figure 10, field flags are distributed as follows:
+
+FDL2 flag = 1 – there being a field Data 2 length
+
+FPN2 flag = 1 – there being a field Packet 2 number
+
+FSA2 flag = 1 – there being a field Sender 2 address
+
+FRA2 flag = 1 – there being a field Receiver 2 address
+
+FDL1 flag = 1 – there being a field Data 1 length
+
+FPN1 flag = 1 – there being a field Packet 1 number
+
+FSA1 flag = 1 – there being a field Sender 1 address
+
+FRA1 flag = 1 – there being a field Receiver 1 address
+
+Figures 13 and 14 provide an illustration of the NCRP headers following network encoding for the scenario of sending packets with a fixed data field size. In this instance, the data block's length is not necessary, hence the appropriate "Data length" fields are left blank. The FDL1 and FDL2 flags are consequently set to zero in a header with a preset order of fields in the Field Flags field.
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------|--|--|--|--------|--|--------|--|--------------------|--|--------|--|--------|--|--------------------|--|------------------|--|--|--|--------|--|--|--|-----------------|--|--|--|--------|--|--|--|
+| 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 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Tech = 0 | | | | 0 1 | | FT = 1 | | | | FL = 6 | | | | Receiver 1 address | | | | | | | | | | | | | | | | | |
+| Receiver 1 address | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| FT = 2 | | | | FL = 6 | | | | Receiver 2 address | | | | | | | | | | | | | | | | | | | | | | | |
+| Receiver 2 address | | | | | | | | | | | | | | | | | | | | | | | | FT = 5 | | | | FL = 6 | | | |
+| Sender 1 address | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Sender 1 address | | | | | | | | | | | | | | | | FT = 9 | | | | FL = 2 | | | | Packet 1 number | | | | | | | |
+| Packet 1 number | | | | | | | | FT = 6 | | | | FL = 6 | | | | Sender 2 address | | | | | | | | | | | | | | | |
+| Sender 2 address | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| FT = 10 | | | | FL = 2 | | | | Packet 2 number | | | | | | | | | | | | | | | | Data ... | | | | | | | |
+
+Q.5032(24)
+
+**Figure 13 – NCRP packet header structure after network encoding with three-parameter fields without "Data length" field**
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------|--|--|--|-----|--|-----|--|-----|--|-----|--|-----|--|--------------------|--|------------------|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|
+| 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 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Tech = 0 | | | | 1 1 | | 0 1 | | 1 1 | | 0 1 | | 1 1 | | Receiver 1 address | | | | | | | | | | | | | | | | | |
+| Receiver 1 address | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Receiver 2 address | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Receiver 2 address | | | | | | | | | | | | | | | | Sender 1 address | | | | | | | | | | | | | | | |
+| Sender 1 address | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Packet 1 number | | | | | | | | | | | | | | | | Sender 2 address | | | | | | | | | | | | | | | |
+| Sender 2 address | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Packet 2 number | | | | | | | | | | | | | | | | Data ... | | | | | | | | | | | | | | | |
+
+Q.5032(24)
+
+**Figure 14 – The format of the NCRP packet header after network encoding, without the "Data length" field and with a specified series of fields**
+
+## 8.3 Packet exchange procedure
+
+The order of exchange of NCRP packets fully corresponds to the scheme in Figure 5.
+
+Node $N_1$ sends packet $P_1$ to repeater $R$ and stores it in the outgoing packet buffer. The repeater stores the packet $P_1$ in the memory buffer and waits for the packet from $N_2$ . After receiving the $P_2$ packet from $N_2$ , the repeater $R$ generates a $P_{NC}$ packet based on $P_1$ and $P_2$ and sends it to both nodes $N_1$ and $N_2$ simultaneously. After receiving the $P_{NC}$ packet, nodes $N_1$ and $N_2$ check the recipient addresses and packet numbers, read the corresponding packet from the outgoing packet buffer, and perform decoding, restoring the packet addressed to them according to the formula (2).
+
+## Appendix I
+
+### Use case for NCRP protocol
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Consider a data transmission system based on one of the LP-WAN technologies, LoRa technology, as an illustration of how to use the NCRP protocol in a packet relay system. Let us say we need to connect two distant end nodes that are unable to communicate with one another directly. In this situation, a relay node will be required. The lowest levels of the OSI model are already implemented by the LoRa transmission technology, hence the NCRP protocol fills the position of a network protocol. There is no need to enter node addressing because there are just two end nodes, as seen in Figure 4, for instance. We assume that when network encoding packets, one node is always labelled as 1, and the second node is always designated as 2 (Figures 11 and 12).
+
+We employ the header structure with a set of predetermined fields to build the NCRP packet because the frame size of the LoRa technology is constrained. Additionally, the Data length field in the NCRP header is 1st octet in size because of the 256-octet limit on the number of data fields in LoRa frames. Additionally, 1st octet is selected for the Packet Number field. The value of Tech is assumed to be 1.
+
+Figures I.1 and I.2 show the NCRP packet header as an example of operating on top of LoRa before network encoding.
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------|---|---|---|---|---|---|---|---|---|----|----|----|----|----|----|---------------|----|----|----|-------------|----|----|----|----|----|----|----|----|----|----|----|
+| 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 |
+| Tech = 1 | | | | | 1 | 0 | | | | | | 0 | 0 | 1 | 1 | Packet number | | | | Data length | | | | | | | | | | | |
+| Data ... | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+Q.5032(24)
+
+**Figure I.1 – NCRP packet header for an example of working over LoRa before network encoding**
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-----------------|---|---|---|---|---|---|---|---------------|---|----|----|----|----|----|-----------------|----------|----|----|---------------|----|----|----|----|----|----|----|----|----|----|----|----|
+| 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 |
+| Tech = 1 | | | | | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | Packet 1 number | | | | Data 1 length | | | | | | | | | | | | |
+| Packet 2 number | | | | | | | | Data 2 length | | | | | | | | Data ... | | | | | | | | | | | | | | | |
+
+Q.5032(24)
+
+**Figure I.2 – NCRP packet header for an example of working over LoRa after network encoding**
+
+## Bibliography
+
+[b-IETF RFC 8406] IETF RFC 8406 (2018), *Taxonomy of Coding Techniques for Efficient Network Communications*.
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling, and associated measurements and tests |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.5033-202504-I_PDF-E/raw.md b/marked/Q/T-REC-Q.5033-202504-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..3106b650793ec20b07124982e68a1db94db95368
--- /dev/null
+++ b/marked/Q/T-REC-Q.5033-202504-I_PDF-E/raw.md
@@ -0,0 +1,665 @@
+
+
+# Recommendation
+
+## **ITU-T Q.5033 (04/2025)**
+
+SERIES Q: Switching and signalling, and associated measurements and tests
+
+Signalling requirements and protocols for IMT-2020 –
+Protocols for IMT-2020
+
+---
+
+# **Network coding multistream protocol for parallel data transmission**
+
+
+
+The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with a white grid pattern, overlaid by a stylized 'ITU' text in blue.
+
+ITU logo
+
+## ITU-T Q-SERIES RECOMMENDATIONS Switching and signalling, and associated measurements and tests
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS NO. 4, 5, 6, R1 AND R2 | Q.120-Q.499 |
+| DIGITAL EXCHANGES | Q.500-Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM NO. 7 | Q.700-Q.799 |
+| Q3 INTERFACE | Q.800-Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 1 | Q.850-Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 |
+| INTELLIGENT NETWORK | Q.1200-Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 |
+| BROADBAND ISDN | Q.2000-Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900-Q.4099 |
+| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100-Q.4139 |
+| PROTOCOLS AND SIGNALLING FOR COMPUTING POWER NETWORKS | Q.4140-Q.4159 |
+| PROTOCOLS AND SIGNALLING FOR QUANTUM KEY DISTRIBUTION NETWORKS | Q.4160-Q.4179 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000-Q.5049 |
+| Signalling requirements and architecture of IMT-2020 | Q.5000-Q.5019 |
+| Protocols for IMT-2020 | Q.5020-Q.5049 |
+| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050-Q.5069 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+# Recommendation ITU-T Q.5033
+
+# Network coding multistream protocol for parallel data transmission
+
+## Summary
+
+Multistream data transmission over parallel channels is one of the well-known options for reducing network delay by increasing the total bandwidth of the connection between the nodes exchanging data. This method is used in particular in the stream control transmission protocol (SCTP), a well-known disadvantage of which is its limited support by network equipment, both terminal and routing.
+
+This is why many modern protocols of the transport and session layers of the open systems interconnection (OSI) model are developed as extensions of the transmission control protocol (TCP) or work on top of the user datagram protocol (UDP), implementing flow control mechanisms and reliable data delivery.
+
+There are several examples of multistream protocols based on traditional transport protocols. The Multipath TCP (MPTCP) was created by the Internet Engineering Task Force (IETF) and described in RFC 8684. Korean researchers proposed the *Dynamic Multi-stream Transport Protocol* over TCP (b-seok). Also, there is a modification of protocol SCTP over UDP suggested by Indian researchers (b-belkhode).
+
+Combining multistream data transmission with the principles of network coding allows, in addition to increasing the throughput, to increase the security of the transmitted user data, since the data in this case is transmitted not in clear form, but in the form of linear combinations of data blocks, which complicates their interception by a third party, requiring the interception of all blocks of data to restore the original information. These aspects are considered in this Recommendation.
+
+Recommendation ITU-T Q.5033 includes:
+
+- principle of multistream transmission with network coding;
+- protocol placement in the TCP/IP stack;
+- protocol logic;
+- packet structure.
+
+## History\*
+
+| Edition | Recommendation | Approval | Study Group | Unique ID |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0 | ITU-T Q.5033 | 2025-04-13 | 11 | 11.1002/1000/16296 |
+
+## Keywords
+
+Multistream data transmission, multistream protocol, network coding.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at .
+
+© ITU 2025
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|-------------------------------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 3.2 Terms defined in this Recommendation..... | 1 |
+| 4 Abbreviations and acronyms ..... | 1 |
+| 5 Conventions ..... | 2 |
+| 6 Overview..... | 2 |
+| 7 Principle of multistream transmission with network coding ..... | 2 |
+| 8 Protocol placement in the TCP/IP stack ..... | 4 |
+| 9 Protocol logic..... | 4 |
+| Appendix I – Packets structures..... | 8 |
+| I.1 Packet format and message types ..... | 8 |
+| I.2 INIT message..... | 9 |
+| I.3 INIT ACK and INIT CONF messages ..... | 9 |
+| I.4 DATA message ..... | 9 |
+| I.5 ACK message ..... | 10 |
+| I.6 FIN and FIN ACK messages ..... | 11 |
+| I.7 RESET message ..... | 11 |
+| I.8 Messages SET, SET ACK and SET CONF ..... | 11 |
+| Appendix II – Use cases..... | 12 |
+| Bibliography..... | 13 |
+
+
+
+# Recommendation ITU-T Q.5033
+
+# Network coding multistream protocol for parallel data transmission
+
+## 1 Scope
+
+This Recommendation describes a multistream protocol for parallel data transmission based on network coding. The aim of the new protocol is to reduce network delay and increase the security of the transmitted user data volume without a reduction in the volume of transmitted information. It covers the following aspects:
+
+- principle of multistream transmission with network coding;
+- technical details of protocol implementation including signalling procedures, packet types and formats, and coding procedures.
+
+## 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 term defined elsewhere:
+
+**3.1.1 network coding** [b-IETF RFC 8406]: A system where coding can be performed at the source as well as at intermediate forwarding nodes (all or a subset of them).
+
+### 3.2 Terms defined in this Recommendation
+
+None.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|---------|------------------------------------------------|
+| AT | Association Tag |
+| DoS | Denial of Service |
+| DSL | Digital Subscriber Line |
+| HAN | Hybrid Access Network |
+| IMT | International Mobile Telecommunications |
+| MP-DCCP | Multipath Datagram Congestion Control Protocol |
+| MP-QUIC | Multipath Quick |
+| MP-TCP | Multipath Transmission Control Protocol |
+
+| | |
+|-------|--------------------------------------|
+| NAT | Network Address Translation |
+| NCMSP | Network Coding Multistream Protocol |
+| OSI | Open Systems Interconnection |
+| PON | Passive Optical Network |
+| SCTP | Stream Control Transmission Protocol |
+| TCP | Transmission Control Protocol |
+| UDP | User Datagram Protocol |
+
+## 5 Conventions
+
+None.
+
+## 6 Overview
+
+Multistream data transmission over parallel channels is one of the well-known options for reducing network delay by increasing the total bandwidth of the connection between the nodes exchanging data. This method is used in particular in the SCTP protocol, a well-known disadvantage of which is its limited support by network equipment, both terminal and routing.
+
+That is why many modern protocols of the transport and session layers of the OSI model are developed as extensions of the TCP protocol or work on top of the UDP protocol, implementing flow control mechanisms and reliable data delivery.
+
+The proposed network coding multistream protocol (NCMSP) implements a mechanism for multistream parallel transmission over the UDP protocol based on the principles of network coding. The use of network coding for parallel data transmission allows us, in addition to increasing the throughput, to increase the security of transmitted user data, since the data in this case is transmitted not in clear form but in the form of linear combinations of data blocks, which complicates their interception by a third party, requiring the interception of all blocks of data to restore the original information.
+
+## 7 Principle of multistream transmission with network coding
+
+The protocol is based on a well-known approaches of network coding, the parallel transmission of linear combinations of $k$ data blocks along $k$ parallel routes ( $k \geq 2$ ).
+
+The transmission principle as an example of $k = 2$ data blocks and their corresponding two parallel routes is shown in Figure 1.
+
+
+
+Diagram illustrating parallel transmission with network coding. Node A transmits two data blocks, x1 and x2, to Node B via two parallel routes. The first route goes through router R1, and the second route goes through router R2. Node A performs linear transformations on the original blocks to create derived blocks y1 and y2. y1 is transmitted via R1 and y2 via R2. Node B receives both y1 and y2 and reconstructs the original blocks x1 and x2 by solving a system of linear equations. The diagram shows Node A on the left, Node B on the right, R1 as the top router, and R2 as the bottom router. Arrows indicate the flow of data blocks: y1 = a11x1 + a12x2 from A to R1 to B, and y2 = b11x1 + b12x2 from A to R2 to B.
+
+Q.5033(25)
+
+**Figure 1 – Parallel transmission with network coding**
+
+Node A must transmit two data blocks $x_1$ and $x_2$ to node B. Two routes are established between nodes: A-R1-B through node R1 and A-R2-B through node R2.
+
+Node A forms two new (derived) data blocks by linear transformation of the original blocks $x_1$ and $x_2$ :
+
+$$y_1 = a_{11}x_1 + a_{12}x_2 \text{ and } y_2 = a_{21}x_1 + a_{22}x_2 \quad (1)$$
+
+where $a_{ij}$ are coefficients (keys) known to both A and B.
+
+Block $y_1$ is transmitted via route A-R1-B. Block $y_2$ is transmitted via route A-R2-B.
+
+Node B receives both blocks $y_1$ and $y_2$ , and then reconstructs the original blocks $x_1$ and $x_2$ by solving a system of linear equations:
+
+$$\begin{cases} y_1 = a_{11}x_1 + a_{12}x_2 \\ y_2 = a_{21}x_1 + a_{22}x_2 \end{cases} \quad (2)$$
+
+By means of transformations we can get the following formulas for the data blocks we are looking for:
+
+$$\begin{cases} x_1 = \frac{a_{12}y_2 + a_{22}y_1}{a_{11}a_{22} + a_{12}a_{21}} \\ x_2 = \frac{a_{11}y_2 + a_{21}y_1}{a_{11}a_{22} + a_{12}a_{21}} \end{cases} \quad (3)$$
+
+Such an approach to data transmission reduces data delivery time by paralleling the routes of transmission streams and increases the security of data delivery due to the fact that to recover the original data blocks $x_1$ and $x_2$ it is necessary to intercept both derivatives of the transmitted blocks $y_1$ and $y_2$ .
+
+This approach can be scaled to any number of $k \geq 2$ data blocks and corresponding parallel channels.
+
+In general, with $k$ data blocks transmitted, the receiver node B will have to solve the following system of linear equations:
+
+$$\begin{cases} y_1 = a_{11}x_1 + a_{12}x_2 + \dots + a_{1k}x_k \\ y_2 = a_{21}x_1 + a_{22}x_2 + \dots + a_{2k}x_k \\ \vdots \\ y_k = a_{k1}x_1 + a_{k2}x_2 + \dots + a_{kk}x_k \end{cases} \quad (4)$$
+
+The more blocks $k$ are transmitted in parallel, the shorter their transmission time per unit of information and the higher the data protection from interception, but the more complicated the system solution will be to recover the original packets $x_1, x_2, \dots, x_k$ .
+
+## 8 Protocol placement in the TCP/IP stack
+
+The protocol is proposed to be used on top of the standard UDP protocol, which will provide transport for NCMSP packets. Using UDP allows to use the standard packet processing mechanisms present in modern network operating systems and network equipment. This includes the network address translation (NAT) mechanism when one of the nodes in the system is located in the local network behind a router.
+
+The NCMSP protocol provides connection establishment over UDP and mechanisms to manage this connection.
+
+## 9 Protocol logic
+
+The protocol works in client/server mode. The server is always running, in the listen state, listening to the channel and waiting to receive packets from the client. The client is initially in the closed state.
+
+As the protocol is oriented on simultaneous work with two and more data streams, which can be transmitted via different physical channels (Figure 1), we should speak not only about connection, but about association, as in the case of the SCTP protocol. Accordingly, all packets of the protocol transmitted within the association should have a common distinctive feature, which we will call an association tag and be transmitted in each packet belonging to it.
+
+The association is established in four steps by transmitting three messages:
+
+- 1) The client sends an INIT message that specifies: an association tag (AT), which is randomly generated, the number of threads $k_{\text{client}} \geq 2$ , and the size of the $s_{\text{client}}$ coefficients $a_{ij}$ , a multiple of 1 octet. Optionally, bit flags indicate the necessity of using acknowledgements and re-requests to ensure guaranteed data delivery. After sending the message, the client enters the INIT sent state.
+- 2) The server acknowledges the connection with an INIT ACK message, in which it quotes the number of threads $k_{\text{server}} \geq 2$ and the size of the server coefficients on its side. This message also transmits a specially generated 32-bit cookie code used to acknowledge the client to counter DoS attacks similar to TCP SYN-flood. After sending the INIT ACK, the server remains in its original listen state. No memory is allocated for association processing.
+- 3) The client confirms the connection with an INIT CONF message. In it they indicate the final agreed number of routes $k = \min(k_{\text{client}}, k_{\text{server}}) \geq 2$ and the size $s = \min(s_{\text{client}}, s_{\text{server}})$ of the $a_{ij}$ factors. Also in this message the client returns to the server the cookie received from it. The client goes to the established state.
+- 4) Upon receiving the INIT CONF message, the server checks that the cookie code is correct. If the check is successful, it reads the association parameters, allocates memory for its processing and enters the established state. If the cookie code is incorrect or association parameters do not match those that can be processed by the server, the server sends a RESET message and goes to the initial state.
+
+The cookie code is formed as a hash function of the following data: association tag, client IP address, client port, server IP address, server port:
+
+$$\text{Cookie} = \text{Hash}(\text{AT} + \text{IP}_{\text{client}} + \text{Port}_{\text{client}} + \text{IP}_{\text{server}} + \text{Port}_{\text{server}}) \quad (5)$$
+
+To calculate a cookie, any hash function can be used that is able to take as input an array with length 128 bits and return a result with length no less than 32 bits. If the result of a hash function is longer than 32 bits, then the lowest 32 bits of the result should be used as a cookie.
+
+Figure 2 shows the association diagram.
+
+
+
+```
+
+sequenceDiagram
+ participant Client
+ participant Server
+ Note left of Client: Closed
+ Note right of Server: Listen
+ Client->>Server: INIT (AT, k_client, s_client)
+ Note left of Client: Init sent
+ Server-->>Client: INIT ACK (AT, k_server, s_server, Cookie)
+ Note left of Client: Established
+ Note right of Server: Established
+ Client->>Server: INIT CONF (AT, k, s, Cookie)
+
+```
+
+Sequence diagram of association establishment between a Client and a Server. The Client starts in a 'Closed' state and sends an 'INIT (AT, k\_client, s\_client)' message to the Server. The Server starts in a 'Listen' state and responds with 'INIT ACK (AT, k\_server, s\_server, Cookie)'. The Client receives this and enters an 'Init sent' state. The Client then sends 'INIT CONF (AT, k, s, Cookie)' to the Server. The Server receives this and enters an 'Established' state. The Client also enters an 'Established' state. The diagram is labeled Q.5033(25).
+
+**Figure 2 – Diagram of association establishment**
+
+When establishing an association, it should be taken into account that, based on the chosen principle of network coding, both parties must know the coefficients $a_{ij}$ . Various mechanisms can be used to ensure this:
+
+- 1) Use the same coefficients for all transmitted data, agreeing on them at the beginning of the dialogue.
+- 2) Use new coefficients for each packet by passing them in the packet itself.
+- 3) Generate new coefficients for each packet according to the rule agreed upon at the beginning of the dialogue.
+
+It is suggested in the protocol to use the second method. However, since the flags service field used in the association establishment messages has free fields, if necessary, the protocol can be modified to use the first or third method of forming and matching coefficients.
+
+After association is established, data (DATA messages) is transmitted over the agreed number of routes.
+
+If during the establishment of association participants agreed on the need to use acknowledgements and re-requests to ensure guaranteed data delivery, then ACK messages are used.
+
+If necessary, either party may send a RESET message at any time during the dialogue, indicating the cookie used to establish the association and the number of the last acknowledged DATA message sent/received. After sending/receiving this message, the association is terminated without waiting for confirmation. Both parties return to the initial state.
+
+It may be necessary to change the association parameters by renegotiating the number of parallel links/routes used and the size of the data block depending on the quality and quantity of parallel links in use that were negotiated at the beginning of the association, the performance of the end devices, the length of the queues in the sender and receiver memory buffers, and the latency differences in the parallel links. Three messages SET, SET ACK, and SET CONF are utilized in this process, which is analogous to the association setup operation. The sender encourages the recipient to modify the association's fundamental parameters using the SET message. The SET ACK response message either verifies the suggested parameters or maintains the parameters' original value if the other party is unable to change them. The initiator replies with a SET CONF message after receiving the SET ACK, reiterating the use of the proper set of parameters. The parties specify the packet number from which the agreed settings will be applied in the SET ACK and SET CONF messages.
+
+Figure 3 shows the renegotiating dialogue using the SET group of messages.
+
+
+
+```
+
+sequenceDiagram
+ participant Client
+ participant Server
+ Note left of Client: Established
+ Client->>Server: SET (Suggested modified parameters)
+ Note right of Server: Check suggested parameters
+ Server->>Client: SET ACK (Verify suggested par./Original par.)
+ Note left of Client: Form set of confirmed parameters
+ Client->>Server: SET CONF (Confirmed par. and start number)
+ Note right of Server: Q.5033(25)
+
+```
+
+The diagram illustrates the renegotiating dialogue between a Client and a Server. Both start in the 'Established' state. The Client sends a 'SET (Suggested modified parameters)' message to the Server. The Server checks the suggested parameters and responds with a 'SET ACK (Verify suggested par./Original par.)' message. The Client then forms a set of confirmed parameters and sends a 'SET CONF (Confirmed par. and start number)' message to the Server. The Server acknowledges this with a reference to Q.5033(25).
+
+Sequence diagram of the renegotiating dialogue between a Client and a Server.
+
+**Figure 3 – Diagram of the renegotiating dialogue**
+
+The connection is terminated with the FIN message and acknowledged with the FIN ACK message. These indicate the number of the last acknowledged DATA message sent/received. After the FIN message is transmitted, the sending party enters the FIN sent state and starts the acknowledgement waiting timer. After sending/receiving the FIN ACK acknowledgement message, the sending side goes to the original state. If the party that sent the FIN does not receive a confirmation when the timer expires, it additionally sends a RESET message, terminates the association and goes to the initial state.
+
+Figure 4 shows the association terminating diagram.
+
+
+
+```
+
+sequenceDiagram
+ participant Client
+ participant Server
+ Note left of Client: Established
+ Client->>Server: FIN (Number of last acknowledged packet)
+ Note left of Client: Fin sent
+ Server->>Client: FIN ACK (Number of last acknowledged packet)
+ Note left of Client: Closed
+ Note right of Server: Listen
+ Note right of Server: Q.5033(25)
+
+```
+
+The diagram illustrates the association terminating process between a Client and a Server. Both start in the 'Established' state. The Client sends a 'FIN (Number of last acknowledged packet)' message to the Server and enters the 'Fin sent' state. The Server receives the FIN message and responds with a 'FIN ACK (Number of last acknowledged packet)' message. The Client receives the FIN ACK message and enters the 'Closed' state. The Server enters the 'Listen' state and acknowledges this with a reference to Q.5033(25).
+
+Sequence diagram of association terminating between a Client and a Server.
+
+**Figure 4 – Diagram of association terminating**
+
+Figure 5 shows a finite state machine of the NCMSP protocol, containing possible states and transitions between them.
+
+
+
+```
+
+stateDiagram-v2
+ [*] --> Closed : Client starting point
+ [*] --> Listen : Server starting point
+ Closed --> Init sent : send: INIT
+ Init sent --> Closed : send: RESET, rcvd: RESET
+ Init sent --> Established : send: INIT CONF, rcvd: INIT ACK
+ Listen --> Established : rcvd: INIT CONF, send: INIT ACK
+ Established --> Listen : send: RESET, rcvd: RESET
+ Established --> Fin sent : send: FIN
+ Fin sent --> Closed : send: RESET, rcvd: FIN ACK/RESET
+ Fin sent --> Listen : send: RESET, rcvd: FIN ACK/RESET
+ Established --> Closed : send: RESET, rcvd: RESET
+
+```
+
+The diagram illustrates the NCMSP protocol finite state machine with five states: Closed, Init sent, Listen, Established, and Fin sent. The Client's starting point is the Closed state, and the Server's starting point is the Listen state. Transitions are triggered by specific message sends or receives. From Closed, the Client sends an INIT message to enter Init sent. From Init sent, the Client can send a RESET message to return to Closed or an INIT CONF message to enter Established, which is acknowledged by an INIT ACK. The Server, starting in Listen, enters Established upon receiving an INIT CONF and sending an INIT ACK. Both Client and Server can transition from Established to Fin sent by sending a FIN message. From Fin sent, both can return to Closed or Listen by sending a RESET message and receiving a FIN ACK or RESET. Additionally, both Client and Server can transition from Closed to Init sent or Listen to Established by sending a RESET message and receiving a RESET message.
+
+NCMSP protocol finite state machine diagram showing Client and Server state transitions between Closed, Init sent, Listen, Established, and Fin sent states with associated send/rcvd messages.
+
+**Figure 5 – NCMSP protocol finite state machine**
+
+Next to the arrows, representing transitions between states, the messages accompanying the transition are indicated. Messages sent by the node are labelled "send" and messages received are labelled "rcvd".
+
+## Appendix I
+
+## Packets structures
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### I.1 Packet format and message types
+
+The NCMSP packet has the block structure shown in Figure I.1. It contains a basic header, which is present in all packets, followed by the individual blocks (chunks) corresponding to the individual messages to be transmitted. Several message blocks can be transmitted in one NCMSP packet.
+
+
+
+Figure I.1 – NCMSP protocol packet structure diagram. The diagram shows a 32-bit packet structure. The first 24 bits (bits 0-23) are labeled 'Association tag'. The next 8 bits (bits 24-31) are labeled 'Message count'. These two fields are grouped by a bracket on the right labeled 'Base header'. Below the base header, the remaining bits (bits 0-31) are labeled 'NCMSP messages ...'. A small label 'Q.5033(25)' is at the bottom right.
+
+Figure I.1 – NCMSP protocol packet
+
+The base header is 32 bits long. It contains a 24-bit association tag and an 8-bit field indicating the number of messages encapsulated in it.
+
+The structure of the message depends on its purpose. Accordingly, at the beginning of each message, there is a mandatory message type field with a length of 8 bits, as shown in Figure I.2. The rest of the message is determined by its type.
+
+
+
+Figure I.2 – Structure of NCMSP protocol message diagram. The diagram shows a 32-bit message structure. The first 8 bits (bits 0-7) are labeled 'Message type'. The remaining 24 bits (bits 8-31) are labeled 'Variable part of message ...'. A small label 'Q.5033(25)' is at the bottom right.
+
+Figure I.2 – Structure of NCMSP protocol message
+
+The list of possible messages with their corresponding codes is presented in Table I.1.
+
+Table I.1 – NCMSP message types
+
+| Code | HEX | Message type |
+|------|------|--------------|
+| 1 | 0x01 | DATA |
+| 2 | 0x02 | DATA SIZED |
+| 3 | 0x03 | ACK |
+| 4 | 0x04 | INIT |
+| 5 | 0x05 | INIT ACK |
+| 6 | 0x06 | INIT CONF |
+| 7 | 0x07 | FIN |
+| 8 | 0x08 | FIN ACK |
+| 9 | 0x09 | RESET |
+| 10 | 0x0A | SET |
+| 11 | 0x0B | SET ACK |
+| 12 | 0x0C | SET CONF |
+
+### I.2 INIT message
+
+The INIT message is used to establish an association (Figure 2). The structure of the INIT message is shown in Figure I.3.
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------|---|---|---|---|---|---|---|--------------|---|----|----|----|----|----|----|----------|----|----|----|----|----|----|----|-------|----|----|----|----|----|----|----|
+| 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 |
+| Message type
0x04 | | | | | | | | Stream count | | | | | | | | Key size | | | | | | | | Flags | | | | | | | |
+
+Figure I.3: Structure of the INIT message of the NC MSP protocol. The diagram shows a 32-bit message structure with four fields: Message type (0x04) for bits 0-7, Stream count for bits 8-15, Key size for bits 16-23, and Flags for bits 24-31.
+
+Q.5033(25)
+
+**Figure I.3 – Structure of the INIT message of the NC MSP protocol**
+
+The message contains the number of parallel routes offered by the client, the size of $a_{ij}$ coefficients of linear network coding, as well as the flags field, for specifying additional association parameters.
+
+The structure of the flags field and the purpose of the flags used are presented in Table I.2.
+
+**Table I.2 – Structure of the flags field of the NC MSP protocol**
+
+| Bit | Name | Function |
+|-----|-----------------------|----------------------------------------------------------------------------------------------------------------|
+| 0-6 | Reserved | – |
+| 7 | Acknowledge Flag (AF) | If it is "1", then it is necessary to use confirmations and repeat requests to ensure guaranteed data delivery |
+
+### I.3 INIT ACK and INIT CONF messages
+
+The INIT ACK and INIT CONF messages, also used to establish an association, have an identical structure, as shown in Figure I.4.
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------|---|---|---|---|---|---|---|--------------|---|----|----|----|----|----|----|----------|----|----|----|----|----|----|----|-------|----|----|----|----|----|----|----|
+| 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 |
+| Message type
0x05, 0x06 | | | | | | | | Stream count | | | | | | | | Key size | | | | | | | | Flags | | | | | | | |
+| Cookie | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+Figure I.4: Structure of the INIT ACK and INIT CONF messages of the NC MSP protocol. The diagram shows a 32-bit message structure with five fields: Message type (0x05, 0x06) for bits 0-7, Stream count for bits 8-15, Key size for bits 16-23, Flags for bits 24-31, and a Cookie field spanning bits 0-31.
+
+Q.5033(25)
+
+**Figure I.4 – Structure of the INIT ACK and INIT CONF messages of the NC MSP protocol**
+
+In comparison with the INIT message described above, the INIT ACK and INIT CONF messages additionally contain a 32-bit cookie field, in which a special confirmation code is transmitted.
+
+### I.4 DATA message
+
+The DATA message is intended for data transmission (upper level protocol messages). In addition to the message type field it contains the following fields:
+
+- 1) Packet number is 32 bits long. The packet number is used to match derived data blocks that match each other. Thus, matching packets transmitted via different routes will have the same number. Such packets will be called a packet set.
+- 2) Stream number is 8 bits long.
+- 3) A group of keys fields to transmit the $a_{ij}$ coefficients is used to form the message being transmitted. The number $k$ and the size $s$ of these fields are agreed upon when the association is established.
+- 4) Data.
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------|--|--|--|--|--|--|--|---------------|--|--|--|--|--|--|--|-------------------|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|
+| 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 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message type
0×01 | | | | | | | | Packet number | | | | | | | | | | | | | | | | | | | | | | | |
+| Packet number | | | | | | | | Stream number | | | | | | | | Keys $a_{ij}$ ... | | | | | | | | | | | | | | | |
+| Data ... | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+Q.5033(25)
+
+**Figure I.5 – Structure of the DATA message of the NCMSP protocol**
+
+When it is necessary to specify the lengths of each of the original data blocks, a special packet DATA SIZED is used, which contains an additional field 'Data Length', as shown in Figure I.6. This field contains the length of the block whose number corresponds to the route/stream number. Suppose that we transmit three packets $p_1, p_2, p_3$ via three parallel routes $r_1, r_2, r_3$ , and accordingly, each time we transmit three blocks of data: $b_1$ of length $l_1$ , $b_2$ of length $l_2$ and $b_3$ of length $l_3$ . The length $l_1$ will be transmitted in packet $p_1$ , $l_2$ - in packet $p_2$ , and $l_3$ - in packet $p_3$ . The total length of derived data blocks $l = \max(l_1, l_2, l_3)$ . When generating derived data blocks, the initial data blocks of length less than $l$ are augmented with zeros.
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------|--|--|--|--|--|--|--|---------------|--|--|--|--|--|--|--|-------------------|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|
+| 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 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message type
0×02 | | | | | | | | Packet number | | | | | | | | | | | | | | | | | | | | | | | |
+| Packet number | | | | | | | | Stream number | | | | | | | | Keys $a_{ij}$ ... | | | | | | | | | | | | | | | |
+| Data length | | | | | | | | | | | | | | | | Data ... | | | | | | | | | | | | | | | |
+
+Q.5033(25)
+
+**Figure I.6 – Structure of the DATA SIZED message of the NCMSP protocol**
+
+### I.5 ACK message
+
+The ACK message is necessary to acknowledge or retry data packets. It transmits the number of the last successfully received complete packet set.
+
+The use of ACK packets is agreed upon when the association is established. When using them, different situations are possible, which we will consider in the example of the transmission of a set of packets with number $k$ via $m$ routes: $P_{k1}, P_{k2}, \dots, P_{km}$ .
+
+- 1) If the receiving node B receives all $m$ packets from the set, it sends a confirmation ACK message with the number $k + \text{"Data length"} + 1$ .
+- 2) If at least one of the $m$ packets is not received after the waiting timer expires, an ACK re-request message with the number $k$ is sent, which tells the sender node A to retransmit the packet set.
+
+In slow channels with high losses it is required to acknowledge each received set of packets.
+
+In fast low-loss channels it is allowed to acknowledge a group of successive packet sets at once.
+
+The number of acknowledged packets may vary during the interaction of nodes A and B. Node B decides on the acknowledgment frequency. Both traditional decision-making principles and methods based on AI systems can be used to select the acknowledgement frequency.
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------|---|---|---|---|---|---|---|---------------|---|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|
+| 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 |
+| Message type
0×03 | | | | | | | | Packet number | | | | | | | | | | | | | | | | | | | | | | | |
+| Packet number | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+Q.5033(25)
+
+**Figure I.7 – Structure of the ACK message of the NCMSP protocol**
+
+### I.6 FIN and FIN ACK messages
+
+The FIN and FIN ACK message group is for terminating a connection. The number of the last successfully received complete packet set is transmitted in the messages.
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------|---|---|---|---|---|---|---|---------------|---|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|
+| 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 |
+| Message type
0×07, 0×08 | | | | | | | | Packet number | | | | | | | | | | | | | | | | | | | | | | | |
+| Packet number | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+Q.5033(25)
+
+**Figure I.8 – Structure of the FIN and FIN ACK messages of the NCMSP protocol**
+
+### I.7 RESET message
+
+The RESET message is intended to terminate the connection without acknowledgement. The RESET message transmits a cookie code calculated by equation (5) in clause 9, Protocol logic, and the number of the last successfully received complete packet set.
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------|---|---|---|---|---|---|---|---------------|---|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|
+| 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 |
+| Message type
0×09 | | | | | | | | Packet number | | | | | | | | | | | | | | | | | | | | | | | |
+| Packet number | | | | | | | | Cookie | | | | | | | | | | | | | | | | | | | | | | | |
+| Cookie | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+Q.5033(25)
+
+**Figure I.9 – Structure of the RESET message of the NCMSP protocol**
+
+### I.8 Messages SET, SET ACK and SET CONF
+
+SET, SET ACK and SET CONF messages used to change parameters' associations have an identical structure, shown in Figure I.10.
+
+
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------|---|---|---|---|---|---|---|--------------|---|----|----|----|----|----|----|----------|----|----|----|----|----|----|----|-------|----|----|----|----|----|----|----|
+| 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 |
+| Message type
0×0A, 0×0B, 0×0C | | | | | | | | Stream count | | | | | | | | Key size | | | | | | | | Flags | | | | | | | |
+| Packet number | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Cookie | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+Q.5033(25)
+
+**Figure I.10 – The NCMSP protocol's SET, SET ACK, and SET CONF message structures**
+
+## Appendix II
+
+## Use cases
+
+(This appendix does not form an integral part of this Recommendation.)
+
+When using end devices with multiple access channels to external networks, the NCMSP protocol can be used. Smartphones, for instance, can browse the Internet concurrently using a Wi-Fi connection and mobile Internet connection (from IMT-2020) family devices to modern ones supported IMT-2020 technologies), including over several bands if the device is capable of doing so. Laptops are capable of using all three types of connectivity at once: wired, wireless and mobile. The NCMSP protocol can also be used to interface with servers that are heavily loaded, enabling the utilization of parallel communication channels to speed up data transfer. Because it will be necessary to listen to and intercept traffic on all parallel channels in order to retrieve the provided data in all of these scenarios, using the NCMSP protocol makes it feasible to further strengthen the security of the transmitted data from being read by a third party.
+
+A characteristic example of the use of the NCMSP protocol, as well as similar multipath protocols such as MP-TCP, MP-DCCP, and MP-QUIC, is its application in hybrid access networks (HANs). These networks utilize multiple connections to provide user devices with access to the global Internet. Hybrid access allows for the aggregation of bandwidth from various access networks, including wired (xDSL, Ethernet, PON) and wireless (Wi-Fi, mobile access networks, satellite access networks), as shown in Figure II.1.
+
+
+
+```
+graph LR; subgraph Access_network; Client[Client (NCMSP)]; WR[Wireless router]; R[Router]; end; Client -.->|Wireless channel| WR; Client -->|Wired channel| R; WR --> Internet((Internet)); R --> Internet; Internet --> Server[Server (NCMSP)];
+```
+
+Diagram illustrating a simple use case of the NCMSP protocol. A Client (NCMSP) is connected to a Wireless router via a dashed line labeled 'Wireless channel' and to a Router via a solid line labeled 'Wired channel'. Both the Wireless router and the Router are connected to a central cloud labeled 'Internet'. The Internet cloud is also connected to a Server (NCMSP). The Client, Wireless router, and Router are grouped under a bracket labeled 'Access network'. A small label 'Q.5033(25)' is present near the bottom right of the diagram.
+
+Figure II.1 – Simple use case
+
+Another application of the NCMSP protocol is its use in peer-to-peer networks with multiple routes. The use of NCMSP also enables the aggregation of bandwidth from several peer-to-peer communication channels, for example, in ad hoc networks of smartphones based on Wi-Fi and Bluetooth technologies.
+
+## Bibliography
+
+- [b-IETF RFC 8406] IRTF RFC 8406 (2018), *Taxonomy of Coding Techniques for Efficient Network Communications*.
+- [b-RFC 8684] IETF RFC 8684 (2020), *TCP Extensions for Multipath Operation with Multiple Addresses*.
+- [b-belkhode] Belkhode, V.V., and Dakhane, D.M. (2015), *UDP-Based Multi-Stream Communication Protocol*, International Journal of Innovative Research in Electronics and Communications (IJIREC), Vol. 2, No. 7, September, pp. 11-15.
+- [b-seok] Seok, S.-J., Kim, H.-J., Jung, K.-M., Kim, K.-H., and Kang, C.-H. (2008), *Dynamic Multi-stream Transport Protocol*, Proceedings of the 11th Asia-Pacific Symposium on Network Operations and Management: Challenges for Next Generation Network Operations and Service Management (APNOMS'08), Berlin, Heidelberg, Springer-Verlag, pp. 287-296.
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling, and associated measurements and tests |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.5035-202601-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb
--- /dev/null
+++ b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3763acd7a0ed56aa30f3f90468c1fb0cb54573eb9045bca3eddf8976b4f0f41d
+size 7219
diff --git a/marked/Q/T-REC-Q.5035-202601-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..efa5c3693d00102b2348228f0ffee461f8be3a4f
--- /dev/null
+++ b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4b2bcb345f6e459a4757d83605a3b4ef6b66d66abef31700963c3528c354db00
+size 17378
diff --git a/marked/Q/T-REC-Q.5035-202601-I_PDF-E/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..122372e8eb50baded13a9b12b438ef71656dadac
--- /dev/null
+++ b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:588ad00c1913db063d7cf0e459af3ceb971cd0727aa59d657487aeb4a176319f
+size 16708
diff --git a/marked/Q/T-REC-Q.5035-202601-I_PDF-E/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..573698e1a6bd2a98f3dbabdddbac5a83e686d0f6
--- /dev/null
+++ b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c54f2370859b362eea3c84452cdeb5139f3b053cd8befe4021a8771891da5b7f
+size 16001
diff --git a/marked/Q/T-REC-Q.5035-202601-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2309c8112528a356099252ff30407ae335116c24
--- /dev/null
+++ b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7cd36992bde65d33fc7ff15b238d43f7d29f18bb5868befb583886b69b5203fe
+size 16884
diff --git a/marked/Q/T-REC-Q.5035-202601-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..008a299b65e28494fdd041a21d461287eb3eff1e
--- /dev/null
+++ b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/4356776ca004ecba5d599667a155d7d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:632635d57a2c96149ca3daafcebd2afb5bfb5a0fd22fa382e2e747148c60bcf1
+size 16413
diff --git a/marked/Q/T-REC-Q.5035-202601-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0f4d9190eaaa3361cd9a5a2256f108cc546611b6
--- /dev/null
+++ b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8427a993fc4e9f2dd49c6f9326be1fbc523fa478736d00976355c2775eb0849c
+size 17594
diff --git a/marked/Q/T-REC-Q.5035-202601-I_PDF-E/51db757d054ce1ce83c436a3578b56ca_img.jpg b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/51db757d054ce1ce83c436a3578b56ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bc72d8f4d197f63c87917cbd218801a3934ad7d6
--- /dev/null
+++ b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/51db757d054ce1ce83c436a3578b56ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd2149ef2188a29f2ab0aea6e0a447113234f2cdb6dc4b43142ab80b23383b52
+size 16329
diff --git a/marked/Q/T-REC-Q.5035-202601-I_PDF-E/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..093bf7c0c138cc3319b69037e799396018cf759c
--- /dev/null
+++ b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bb000f232e3d445208840212946ea7b673f423fde147926fbdaea36fb48a19e9
+size 15999
diff --git a/marked/Q/T-REC-Q.5035-202601-I_PDF-E/66c2bf11a8f117cddf67eff92d4c736c_img.jpg b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/66c2bf11a8f117cddf67eff92d4c736c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ea52493bfe7a57baa76a47e3c59e5fc206acf44c
--- /dev/null
+++ b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/66c2bf11a8f117cddf67eff92d4c736c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1f37514989dd2bfdc45bb39aedfa39ed5835367e11381c1e3e0b8bb5b27f7df3
+size 17483
diff --git a/marked/Q/T-REC-Q.5035-202601-I_PDF-E/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..374e87eaf715d0011aec1d67ba6feef19841fbea
--- /dev/null
+++ b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1cd4440665d8d09531df0cba46583fef98955c8f0717b895a0f78394dc20714a
+size 50090
diff --git a/marked/Q/T-REC-Q.5035-202601-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5a3c5b5a2cfcd9981613dfcb8f873c1042a58d00
--- /dev/null
+++ b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8752d6ee5e9ca5ab4c9c4afee97f6a6fb0e48ced6166eefa0b1729ecaf5f041d
+size 18011
diff --git a/marked/Q/T-REC-Q.5035-202601-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c0c0b08746c00da4c6c866f3f9caf4cc8af47855
--- /dev/null
+++ b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f0153f4c9d661ae12e218b9ac7e00fd6ffc981629c6cf1b616b5535bf06ad0e7
+size 16382
diff --git a/marked/Q/T-REC-Q.5035-202601-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bd1d4daa91536a888a7dea103951d289435417a0
--- /dev/null
+++ b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3f1d8056eefdd59edd3a097aaf2c2227ea18dc45e7fe154532cfdbe41f26ad37
+size 16428
diff --git a/marked/Q/T-REC-Q.5035-202601-I_PDF-E/a7c51c18111139f9aca2805114108565_img.jpg b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/a7c51c18111139f9aca2805114108565_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..363ef3c7515f06b8dedef0fd6cff1f472630ee6b
--- /dev/null
+++ b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/a7c51c18111139f9aca2805114108565_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d20be1121ea22da44afe0608370c6efeaf70068df175a5e01a556830e070091
+size 16894
diff --git a/marked/Q/T-REC-Q.5035-202601-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a0371a10c06eeaae42cc83cc5ab0a5d50085b223
--- /dev/null
+++ b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e51432bb307e43006576271148db56cef4e1f2ca4d1a16ef55f3cd5247d8161a
+size 17389
diff --git a/marked/Q/T-REC-Q.5035-202601-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fee8586e41b942262f7fce8d494d68a205f54f18
--- /dev/null
+++ b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fda26a105ab51623594fd4d4e9cd062e1ec735ef5479cfdd626d29f563bff349
+size 16776
diff --git a/marked/Q/T-REC-Q.5035-202601-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..39bbafe08d0060de264f2b3b71d1f43e45d2311a
--- /dev/null
+++ b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e60e91a97986b67f41c65e2d21d410f7560e5638631ddd9b8ea263501e0a6857
+size 15811
diff --git a/marked/Q/T-REC-Q.5035-202601-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c017bc38dd7d88492752c1ac04659a5216c2c064
--- /dev/null
+++ b/marked/Q/T-REC-Q.5035-202601-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ca00f62522610812e87015830b6cdf9c4be7833dd70629ee8bae262a018acda
+size 60861
diff --git a/marked/Q/T-REC-Q.5053-202101-I_PDF-E/raw.md b/marked/Q/T-REC-Q.5053-202101-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..641ddb2abb4c58ddbe70ba5fdaedb58b95cb23eb
--- /dev/null
+++ b/marked/Q/T-REC-Q.5053-202101-I_PDF-E/raw.md
@@ -0,0 +1,509 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.5053**
+
+(01/2021)
+
+SERIES Q: SWITCHING AND SIGNALLING, AND
+ASSOCIATED MEASUREMENTS AND TESTS
+
+Combating counterfeiting and stolen ICT devices
+
+# --- **Mobile device access list audit interface**
+
+Recommendation ITU-T Q.5053
+
+## ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS**
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100–Q.4139 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000–Q.5049 |
+| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050–Q.5069 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## Recommendation ITU-T Q.5053
+
+# Mobile device access list audit interface
+
+## Summary
+
+Recommendation ITU-T Q.5053 defines the methodologies and interfaces between mobile device access list audit system (MDALAS) and mobile network operators' equipment identity register (EIR) to audit and reconcile whether the mobile network operators (MNOs) are complying with the defined mobile device access list requirements. This Recommendation proposes different types of methodologies and interfaces to check and reconcile the mobile device access list used by the MNOs to comply with the regulations for the mobile device access list audit system (MDALAS).
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.5053 | 2021-01-13 | 11 | 11.1002/1000/14587 |
+
+## Keywords
+
+Access list, audit, blacklist, mobile device, whitelist.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2021
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|-------------------------------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 3.2 Terms defined in this Recommendation..... | 1 |
+| 4 Abbreviations and Acronyms ..... | 2 |
+| 5 Conventions ..... | 2 |
+| 6 Reference model ..... | 2 |
+| 6.1 Method 1 – Get IMEI status for mobile device..... | 2 |
+| 6.2 Method 2 – Get IMEI status through HTTP..... | 4 |
+| 6.3 Method 3 – Get Complete List of IMEIs..... | 5 |
+| 6.4 Method 4 – Non-intrusive blacklist audit system (NIBAS) ..... | 6 |
+| Annex A – Message structure ..... | 8 |
+| A.1 GetImeiStatusReq request message..... | 8 |
+| A.2 GetImeiStatusResp response message..... | 8 |
+| A.3 GetIMEIListReq request message..... | 8 |
+| A.4 GetIMEIListResp response message..... | 9 |
+| Bibliography..... | 10 |
+
+
+
+## Recommendation ITU-T Q.5053
+
+# Mobile device access list audit interface
+
+# 1 Scope
+
+In some countries, international mobile equipment identities (IMEIs) to be blacklisted, thus blocking access to the mobile network, or to be allowed (whitelisted) by the mobile network operators (MNOs), may be provided by a telecom authority or law enforcement agency (LEA) via mobile device identifier database (MDID). The mobile device access list as defined by the regulators under the country's governing laws and regulations are either directly provided to the MNOs by the authorities or only the access to these lists is provided to the MNOs instead of providing the actual lists.
+
+There is no established mechanism to check and verify if the IMEI lists contained within each MNO's equipment identity register (EIR) contain all of the data provided by the various other IMEI sources and are therefore in compliance with locally mandated and/or agreed policies. Thus, there is a requirement to develop a common approach for audits and/or reconciliations of blacklist data to be undertaken.
+
+This Recommendation suggests mechanisms to carry out such audits or reconciliations.
+
+# 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.5052] Recommendation ITU-T Q.5052 (2020), *Addressing mobile devices with a duplicate unique identifier*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following term defined elsewhere:
+
+**3.1.1 mobile device identifier database (MDID)** [ITU-T Q.5052]: A database containing aggregated information about mobile device unique identifiers.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 mobile device access list audit system (MDALAS)**: A system that authorised entities may use to audit, reconcile or verify accuracy of blocked or allowed international mobile equipment identity (IMEI) lists in individual mobile network operator (MNO) equipment identity registers (EIRs).
+
+**3.2.2 blacklist override (BLO)**: The list of subscribers that have blacklisted mobile devices (blocked international mobile equipment identities (IMEIs)), but who are still allowed to access mobile networks and services.
+
+NOTE – A blacklist override comprises a combination of the international mobile equipment identity (IMEI) and the international mobile subscriber identity (IMSI).
+
+# **4 Abbreviations and Acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|--------|------------------------------------------|
+| AMF | Access and Mobility Management Function |
+| BLO | Blacklist Override |
+| EIR | Equipment Identity Register |
+| GSMSC | Gateway MSC |
+| GPRS | General Packet Radio Service |
+| HTTPS | Hyper Text Transfer Protocol Secure |
+| IMEI | International Mobile Equipment Identity |
+| IMSI | International Mobile Subscriber Identity |
+| IWF | Interworking Function |
+| LEA | Law Enforcement Agency |
+| LTE | Long-Term Evolution |
+| MDALAS | Mobile Device Access List Audit System |
+| MDID | Mobile Device Identifier Database |
+| ME | Mobile Equipment |
+| MME | Mobility Management Entity |
+| MNO | Mobile Network Operator |
+| MSC | Mobile Switching Centre |
+| NIBAS | Non-Intrusive Blacklist Audit System |
+| SGSN | Serving GPRS Support Node |
+| SIM | Subscriber Identification Module |
+
+# **5 Conventions**
+
+None.
+
+# **6 Reference model**
+
+This Recommendation describes the possible mechanisms to confirm on the status of international mobile equipment identities (IMEIs).
+
+## **6.1 Method 1 – Get IMEI status for mobile device**
+
+In this method the mobile device access list audit system (MDALAS) will query the MNO's equipment identity register (EIR) through standard 3GPP signalling messages.1 As MNOs receive external messages through their gateway node only, so the MDALAS needs to send the message through this gateway depending on the network technology used by the MNO. This allows the MDALAS to check the status of a blacklisted, grey-listed or whitelisted international mobile
+
+---
+
+1 All the relevant 3GPP standards for the current technologies are listed in the bibliography.
+
+equipment identity (IMEI), based on an implementation scheme on an MNO's EIR through online interfaces and to validate if the IMEI list has been implemented correctly. Figure 1 shows the interface between the MDALAS and the MNO.
+
+
+
+```
+
+graph LR
+ MDALAS[MDALAS] -- "3GPP signalling" --- MNO[MNO gateway]
+ MNO -- "3GPP signalling" --- EIR[EIR]
+ subgraph " "
+ MNO
+ EIR
+ end
+
+```
+
+Q.5053(21)\_F01
+
+Figure 1 – Interface between MDALAS and MNO
+
+**Figure 1 – Interface between MDALAS and MNO**
+
+### 6.1.1 Message exchange
+
+– The MDALAS sends a CheckIMEI/ME\_IdentityCheck/N5g-eir\_EquipmentIdentityCheck request message to the gateway. The gateway forwards the request to the MNO's EIR.
+
+– The MNO's EIR receives the message and returns a response message to the MNO gateway. The gateway forwards the response to the MDALAS. Figure 2 shows message flow between the MDALAS and the MNO.
+
+
+
+```
+
+sequenceDiagram
+ participant MDALAS
+ participant MNO as MNO gateway
+ participant EIR
+ MDALAS->>MNO: Request
+ MNO->>EIR: Request
+ EIR->>MNO: Response
+ MNO->>MDALAS: Response
+
+```
+
+Q.5053(21)\_F02
+
+Figure 2 – Message flow between MDALAS and MNO
+
+**Figure 2 – Message flow between MDALAS and MNO**
+
+### 6.1.2 Detailed behaviour of MDALAS
+
+Depending on the network architecture, the MDALAS shall use the CheckIMEI/ME\_IdentityCheck/N5g-eir\_EquipmentIdentityCheck message to get the IMEI status of a mobile device from the MNO's EIR. While receiving the response message from the MNO's EIR, the MDALAS shall check the IMEI status received on the status of the queried IMEI. Depending upon the result, the MDALAS takes following action:
+
+– Received IMEI status from MNO EIR to be matched with the expected status as available with the MDALAS and reconciliation report to be prepared accordingly.
+
+### 6.1.3 Detailed behaviour of EIR
+
+When receiving the CheckIMEI/ME\_IdentityCheck/N5g-eir\_EquipmentIdentityCheck request message, the MNO's EIR shall check whether the mobile device is known. The EIR shall identify the mobile device based on the first 14 digits of the IMEI. The EIR shall return the IMEI status as White/Grey/Black in the response message.
+
+### 6.1.4 Practical considerations
+
+While this method offers certain advantages, such as avoiding the need to develop any proprietary interface or standardize any new message/protocol thus alleviating the need for any EIR upgrade or configuration changes itself, it may require an upgrade or configuration changes to the other network nodes, as explained below.
+
+More importantly, the ability to channel messages to the MNO's EIR over the signalling network will only be possible if the MNO policies and network configurations allow receipt and processing of these messages from entities such as the MDALAS. This may not be possible depending on the signalling security policies and measures that have been deployed by the MNO and that have been mandated by local regulation.
+
+**Rec. ITU-T Q.5053 (01/2021)** 3
+
+As MNOs normally do not allow connection to their EIR from any external source, connection from a MDALAS needs to be through the gateway node. For example, a 2G/3G network could be connected through a gateway MSC (GMSC) or interworking function (IWF), a GPRS network through a serving GPRS support node (SGSN), a long-term evolution (LTE) network through a mobility management entity (MME), or a 5G network through an access and mobility management function (AMF). The MNO needs to allow the particular node MDALAS to connect to their network for performing an audit.
+
+## 6.2 Method 2 – Get IMEI status through HTTP
+
+In the online interface of Method 1 as presented in clause 6.1, the MDALAS can get the confirmation of listed international mobile equipment identity (IMEI) numbers only. IMEI/IMSI pairs or BLO subscribers can not be confirmed with this method. In this methodology, the MDALAS will need to get the IMEI status from the MNO's EIR using the HTTPS interface. Figure 3 shows the interface between MDALAS and EIR.
+
+
+
+Figure 3: Interface between MDALAS and EIR. A diagram showing a box labeled 'MDALAS' on the left and a box labeled 'EIR' on the right. A dashed vertical line between them is labeled 'HTTPS interface'. Below the EIR box is the text 'Q.5053(21)\_F03'.
+
+**Figure 3 – Interface between MDALAS and EIR**
+
+### 6.2.1 Message exchange
+
+The MDALAS sends a GetImeiStatusReq message to the EIR. The MNO's EIR receives the message and sends a response in GetImeiStatusResp message to the MDALAS. The MDALAS and EIR message flow diagram is shown in Figure 4.
+
+
+
+Figure 4: GetImeiStatusReq message flow. A sequence diagram showing MDALAS on the left and multiple EIR boxes on the right, labeled 'MNO1 EIR' and 'MNO\_n EIR'. Arrows show GetImeiStatusReq messages from MDALAS to each EIR and GetImeiStatusResp messages from each EIR back to MDALAS. Below the bottom EIR box is the text 'Q.5053(21)\_F04'.
+
+**Figure 4 – GetImeiStatusReq message flow**
+
+Annexes A.1 and A.2 indicate the structure of the messages flow between the MDALAS and MNO EIR application server.
+
+### 6.2.2 Detailed behaviour of MDALAS
+
+The MDALAS shall use the GetImeiStatusReq message to get the IMEI status of mobile equipment from the MNO's EIR. When receiving the GetImeiStatusResp response message from the MNO's EIR, the MDALAS shall check the IMEI status. Depending upon the result, the MDALAS takes the following action:
+
+- Received IMEI status from MNO EIR to be matched with the expected status as available with MDALAS and reconciliation report to be prepared accordingly.
+
+### 6.2.3 Detailed behaviour of EIR
+
+When receiving the GetImeiStatusReq request message, the MNO's EIR shall check whether the mobile device is known. The EIR shall identify the mobile device based on the first 14 digits of the IMEI. The EIR shall return the IMEI status as White/Grey/Black in the GetImeiStatusResp
+
+response. If the mobile device is blacklisted and BLO list exists within the EIR for that IMEI, then the EIR shall send the BLO list corresponding to that IMEI.
+
+### 6.2.4 Practical considerations
+
+The EIR interface on HTTP messages is available for 5G only. Proprietary interfaces and APIs/messages will need to be standardized by the standardization bodies among all EIRs and MDALAS for the all other technologies.
+
+## 6.3 Method 3 – Get Complete List of IMEIs
+
+In the two methodologies, presented in clauses 6.1 and 6.2, an IMEI lists audit has been proposed for an individual mobile device. But to perform actual reconciliation, the MDALAS needs to know if there are some extra mobile devices in any MNO's EIR. In this methodology, the MDALAS will get the IMEI list for the provided status (White/Grey/Black) from the MNO's EIR using an HTTPS interface. Figure 5 shows the interface between the MDALAS and EIR.
+
+
+
+```
+graph LR; MDALAS[MDALAS] <--> |HTTPS interface| EIR[EIR];
+```
+
+Figure 5: Interface between the MDALAS and EIR. A diagram showing a box labeled 'MDALAS' on the left and a box labeled 'EIR' on the right. A double-headed arrow labeled 'HTTPS interface' connects them. A dashed vertical line separates the two boxes. Below the EIR box is the text 'Q.5053(21)\_F05'.
+
+**Figure 5 – Interface between the MDALAS and EIR**
+
+### 6.3.1 Message exchange
+
+- The MDALAS sends a GetIMEIListReq message to the EIR.
+- The MNO's EIR receives the message and sends a response in GetIMEIListResp message to the MDALAS.
+
+The MDALAS and EIR message flow diagram is shown in Figure 6.
+
+
+
+```
+graph LR; MDALAS[MDALAS] -- GetIMEIListReq --> MNO1_EIR[MNO1 EIR]; MNO1_EIR -- GetIMEIListResp --> MDALAS; MDALAS -- GetIMEIListReq --> MNO_n_EIR[MNO_n EIR]; MNO_n_EIR -- GetIMEIListResp --> MDALAS;
+```
+
+Figure 6: Get IMEIlist message flow. A diagram showing a box labeled 'MDALAS' on the left. On the right, there are two boxes labeled 'MNO1 EIR' and 'MNO\_n EIR', with a dashed vertical line between them. Arrows show the message flow: GetIMEIListReq from MDALAS to MNO1 EIR, GetIMEIListResp from MNO1 EIR to MDALAS, GetIMEIListReq from MDALAS to MNO\_n EIR, and GetIMEIListResp from MNO\_n EIR to MDALAS. Below the MNO\_n EIR box is the text 'Q.5053(21)\_F06'.
+
+**Figure 6 – Get IMEIlist message flow**
+
+Annexes A.3 and A.4 indicate the structure of the messages flow between the MDALAS and MNO EIR application server.
+
+### 6.3.2 Detailed behaviour of MDALAS
+
+The MDALAS shall use the GetIMEIListReq message to get the complete list of IMEIs from the MNO's EIR. When receiving the GetIMEIListResp response message from the MNO's EIR, the MDALAS shall match the list with its own IMEIlist. Depending upon the result, the MDALAS takes the following actions:
+
+- The MDALAS shall generate additional IMEI list reports if the response message contains additional IMEIs for the provided status.
+- The MDALAS shall generate a missing IMEI list report if the response message contains missing IMEIs for the provided status.
+
+In instances where additional IMEIs are identified in the IMEI access lists provided by the MNOs that were not part of the list provided by the authorities, the MDALAS audit system will generate a separate report to highlight those IMEIs.
+
+### 6.3.3 Detailed behaviour of EIR
+
+When receiving the GetIMEIListReq request message, the MNO's EIR shall check its database for the complete list of IMEIs for requested IMEI status. The EIR shall return the complete list of IMEIs of requested status in a GetIMEIListResp response message. If the requested IMEI status is black, then in addition to the blacklist the MNO EIR will send the BLO list corresponding to the blacklisted IMEIs.
+
+### 6.3.4 Practical considerations
+
+EIR interfaces on HTTP messages are available for 5G only. Proprietary interfaces and APIs/messages will need to be standardized by the standardization bodies among all EIRs and MDALAS.
+
+The authorities will need to ensure standard operating procedures between the authorized entities and the MNOs are in place to avoid any disruption in the verification and audit process.
+
+## 6.4 Method 4 – Non-intrusive blacklist audit system (NIBAS)
+
+This clause provides an alternate methodology specific to blacklist implementations to verify whether the provided blacklists have been properly provisioned into the MNOs EIRs and are in effect as per the regulatory mandate barring non-compliant devices from accessing the mobile network without any need to directly connect to the MNO's network (MSC/GMSC) or their EIRs on the dedicated link.
+
+This approach is notably useful in countries where connectivity of an external system (such as MDALAS) to the MNOs' network nodes may not be possible. This proposed mechanism ensures continued regulatory compliance and conformity to the regulations by the MNOs.
+
+This non-intrusive approach provides a mechanism that ensures MNO's comply to the regulatory mandate while providing the following benefits:
+
+- Eliminates the need to define a new standard/protocol for messaging
+- Eradicates the burden on EIR vendors to support any new interfaces and messaging for blacklist auditing
+- Eradicates the burden on network infrastructure vendors to upgrade their network nodes
+- Eliminates the need for interoperability testing between equipment of multiple EIR and network infrastructure vendors
+- Alleviates the need to connect to MNO's EIR relieving any concerns of external components connecting to a live network
+- Not prone to any inaccuracies or inconsistencies in an MNO's system as this approach does not directly rely on any information from the MNO's EIR
+
+This methodology shall not use a regular mobile device but instead it shall utilize a specialized audit equipment/system available only to the authorised entity/regulator responsible for the IMEI audit purposes, that allows for verification of blacklisted IMEIs.
+
+This process will allow the regulators or authorities to verify blacklisted IMEIs one-by-one by performing an automated network procedure for blacklisted IMEIs on all mobile networks using respective mobile operators' subscriber identification modules (SIM). Successful access to the given networks will indicate the blacklisted IMEIs were not blocked on a given MNO's network.
+
+The sample procedure along with sample flow diagram (see Figure 7) is described below:
+
+1. Originate a mobile call with a local SIM from an MNO on whose network the blacklisted IMEIs are being verified/audited using a blacklisted IMEI on the apparatus.
+2. Generate a report if the call is successful indicating a violation by the MNO (MNO is not blocking the blacklisted IMEI on its network). Add that IMEI to a "Violation-List" with the network-IMEI information.
+3. Repeat the above steps for the selected sample blacklisted IMEI.
+4. Repeat the above procedure using SIMs from all other operators one at a time.
+
+
+
+```
+graph TD; Start([Start]) --> Step1[/Establish calls on list audit equipment using blacklisted IMEIs/]; DB[(Blacklisted IMEI database)] --> Step1; Step1 --> Step2[Originate a mobile call using an MNO's local SIM]; Step2 --> Decision{Call successful?}; Decision -- No --> Result1[IMEI is blacklisted on the MNO's network]; Decision -- Yes --> Result2[IMEI is not blacklisted on the MNO's network]; Result2 --> Step3[/Add device IMEI and IMSI in the violation list/]; Step3 -- "Repeat for next IMEI/Next SIM" --> Step1;
+```
+
+Flowchart of the NIBAS workflow. The process starts with 'Start', followed by 'Establish calls on list audit equipment using blacklisted IMEIs' (which interacts with a 'Blacklisted IMEI database'). Then 'Originate a mobile call using an MNO's local SIM'. A decision 'Call successful?' follows. If 'No', 'IMEI is blacklisted on the MNO's network'. If 'Yes', 'IMEI is not blacklisted on the MNO's network', which leads to 'Add device IMEI and IMSI in the violation list'. A feedback loop labeled 'Repeat for next IMEI/Next SIM' returns to the 'Establish calls...' step.
+
+**Figure 7 – NIBAS workflow**
+
+### 6.4.1 Practical considerations
+
+It should be noted that most country regulations normally do not allow any IMEI tampering or reprogramming. This process requires special provisions in the regulations for the government and government authorized entities to utilize a specialized audit equipment/system. The availability of such equipment/system is usually restricted to government's verification/audit use only.
+
+The authorities are encouraged to ensure that standard operating procedures between the authorized entities and the MNOs are in place to avoid any disruption in the verification and audit process.
+
+The authorities can decide the appropriate sample size and periodicity to perform this audit procedure to ensure the process is not overburdened.
+
+# Annex A
+
+## Message structure
+
+(This annex forms an integral part of this Recommendations.)
+
+## A.1 GetImeiStatusReq request message
+
+This message will be sent by the MDALAS to the MNO EIR to get the status of the IMEI. It will have the content described in the Table A.1.
+
+### A.1.1 Message elements
+
+**Table A.1 - GetImeiStatusReq request message content**
+
+| Name | Type | Length | Required | Description |
+|---------------|-------------------|--------|----------|-----------------------------------------------------|
+| MessageHeader | MessageHeaderType | | R | Will contain the information of MNO, Zone and Date. |
+| IMEI | IMEIType | 14-16 | R | IMEI of the mobile device |
+
+## A.2 GetImeiStatusResp response message
+
+This message will be sent by the MNO EIR node to the MDALAS in response to the GetImeiStatusReq message. It will have the content described in Table A.2.
+
+### A.2.1 Message elements
+
+**Table A.2 - GetImeiStatusResp response message content**
+
+| Name | Type | Length | Required/
Conditional | Description |
+|-----------------|-------------------|--------|--------------------------|------------------------------------------------------------------------------------------------------------|
+| MessageHeader | MessageHeaderType | | R | Will contain the information of MNO, Zone and Date. |
+| ImeiStatus | String | 5 | R | It can be WHITE/ GREY/ BLACK |
+| BLO | BLOType | | C | Complete BLO List corresponding if the requested IMEI status is black |
+| BLO/RecordCount | RecordCountType | | R | Will contain the BLO List Count if BLO exists. |
+| BLO/Record | BLORecordType | | C | Will contain the Pair of the complete BLO List. It is mandatory if Record Count is available. |
+
+## A.3 GetIMEIListReq request message
+
+This message will be sent by the MDALAS to the EIR to get the complete list of IMEIs of a particular IMEI status. It will have the content described in Table A.3
+
+### A.3.1 Message elements
+
+**Table A.3 - GetIMEIListReq request message content**
+
+| Name | Type | Length | Required | Description |
+|---------------|-------------------|--------|----------|-----------------------------------------------------|
+| MessageHeader | MessageHeaderType | | R | Will contain the information of MNO, Zone and Date. |
+| ImeiStatus | String | 5 | R | It can be WHITE/ GREY/ BLACK |
+
+## A.4 GetIMEIListResp response message
+
+This message will be sent by the EIR node to the MDALAS in response to the GetIMEIListReq message. It will have the content described in Table A.4.
+
+### A.4.1 Message elements
+
+**Table A.4 - GetIMEIListResp response message content**
+
+| Name | Type | Length | Required/ Optional | Description |
+|----------------------|---------------------|--------|--------------------|---------------------------------------------------------------------------------------------------------------|
+| MessageHeader | MessageHeaderType | | R | Will contain the information of MNO, Zone and Date. |
+| ImeiStatus | String | 5 | R | It can be WHITE/ GREY/ BLACK |
+| IMEIList | IMEIListType | | R | Complete List corresponding to the requested IMEI |
+| IMEIList/RecordCount | RecordCountType | | R | Will contain total number of records of requested IMEI status if exists. |
+| IMEIList/Record | BlackListRecordType | | C | Will contain exact IMEI, IMSI (optional) of requested IMEI status if RecordCount exists |
+| BLO | BLOType | 5 | C | It will contain BLO if BLO exists for any IMEI in case of requested IMEI status is black. |
+| BLO/RecordCount | RecordCountType | | R | Will contain the BLO List Count if BLO exists for the IMEI status as black |
+| IMEIBloList/Record | BloListRecordType | | C | Will contain the Pair of the complete BLO List if BLO count exists for the IMEI status as black. |
+
+# Bibliography
+
+- [b-3GPP TS 23.060] 3GPP TS 23.060 (ETSI TS 123.060) *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); General Packet Radio Service (GPRS); Service description.*
+- [b-3GPP TS 23.401] 3GPP TS 23.401 (ETSI TS 123.401) *LTE; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access.*
+- [b-3GPP TS 29.002] 3GPP TS 29.002 (ETSI TS 129.002) *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Mobile Application Part (MAP) specification.*
+- [b-3GPP TS 29.272] 3GPP TS 29.272 (ETSI TS 129.272) *Universal Mobile Telecommunications System (UMTS); LTE; Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol.*
+- [b-3GPP TS 29.511] 3GPP TS 29.511 (ETSI TS 129.511) *5G System; Equipment Identity Register Services.*
+
+
+
+# SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling, and associated measurements and tests |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.521-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.521-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ab2b0b2d73b247fc8d38494c438665beb0b34dde
--- /dev/null
+++ b/marked/Q/T-REC-Q.521-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d968315bfd08bea8a3c05b4e9fc37faa6d95aeb204c966b61eaaf1aca7232874
+size 8237
diff --git a/marked/Q/T-REC-Q.521-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg b/marked/Q/T-REC-Q.521-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a14a83ef676732c5892e2d4722bb7600d0fb6ef4
--- /dev/null
+++ b/marked/Q/T-REC-Q.521-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:261e113f95724c529c4403f94255b70cbcfd3bcf54a2447f3e33a3ef8a76ddf7
+size 56278
diff --git a/marked/Q/T-REC-Q.521-199303-I_PDF-E/raw.md b/marked/Q/T-REC-Q.521-199303-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..dd9795113e3bd473973740471e415d7238a54561
--- /dev/null
+++ b/marked/Q/T-REC-Q.521-199303-I_PDF-E/raw.md
@@ -0,0 +1,378 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' written across the center.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.521**
+
+(03/93)
+
+**DIGITAL EXCHANGES**
+
+---
+
+**DIGITAL EXCHANGE FUNCTIONS**
+
+**ITU-T Recommendation Q.521**
+
+(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.521 was revised by the ITU-T Study Group XI (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993).
+
+# --- NOTES
+
+1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector.
+
+In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms "CCITT, CCIR or IFRB" or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure.
+
+2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+# CONTENTS
+
+| | Page |
+|-----------------------------------------------------------------------------------------------------------------------|-------------|
+| 1 General ..... | 1 |
+| 2 Exchange functions – Introduction and framework ..... | 1 |
+| 2.1 General..... | 1 |
+| 2.2 Exchange model..... | 1 |
+| 2.3 Utilization of exchange functions for services..... | 1 |
+| 3 General functions required in an exchange for operation in the IDN, ISDN or mixed analogue/digital environment..... | 2 |
+| 3.1 Timing and synchronization ..... | 2 |
+| 3.2 Signalling..... | 3 |
+| 3.3 Data Packet Handling ..... | 3 |
+| 3.4 Information retrieval and analysis ..... | 3 |
+| 3.5 Resource management ..... | 4 |
+| 3.6 Ongoing operations..... | 4 |
+| 4 Functions used in processing bearer service call attempts ..... | 5 |
+| 4.1 Process Service Request ..... | 5 |
+| 4.2 Connect (through connect)/Disconnect ..... | 5 |
+| 4.3 Perform originating screening (in originating exchange) ..... | 5 |
+| 4.4 Perform terminating screening (in terminating exchange)..... | 6 |
+| 4.5 Process Attempt..... | 6 |
+| 5 Additional functions required to provide ISDN Supplementary Services ..... | 7 |
+
+
+
+# DIGITAL EXCHANGE FUNCTIONS
+
+(Melbourne 1988, modified at Helsinki, 1993)
+
+# 1 General
+
+This Recommendation applies to digital local, combined, transit and international exchanges for telephony in Integrated Digital Networks (IDN) and mixed (analogue/digital) networks and also to local, combined, transit and international exchanges in an Integrated Services Digital Network (ISDN).
+
+The field of application of this Recommendation is more fully defined in Recommendation Q.500.
+
+Some text may only apply to a certain type (types) of exchange, e.g. digital transit, local or combined. Where this occurs, the application is defined in the text. Not all the recommended functions will necessarily be provided in every exchange.
+
+# 2 Exchange functions – Introduction and framework
+
+## 2.1 General
+
+The purpose of this Recommendation is to specifically address those functions required to support basic and supplementary services in performing this test, this Recommendation takes account of the principles set down in Recommendation I.310 and draws a clear distinction between services and the exchange capabilities required to support them.
+
+It should be noted that the list of functions identified in this Recommendation is not necessarily extensive.
+
+## 2.2 Exchange model
+
+The functions described in this and associated Recommendations can be considered within the framework of an exchange functional model. Such a model is shown in Figure 1. This divides the exchange into three functional areas as follows:
+
+- a) *control functions* – Those functions required to control services and connections, e.g. signalling, routing and connection/resources handling functions;
+- b) *connection functions* – Those functions directly related to the connection path through an exchange, i.e. switching and transmission mechanism (including ET);
+- c) *operation and maintenance functions* – Those functions of an operational, management and maintenance nature which are not employed for call establishment and supervisory purposes, e.g. test functions.
+
+The exchange functional model shown in Figure 1 is appropriate to exchanges operating in an IDN and also those operating in an IDN which is evolving towards an ISDN. In terms of this Recommendation, most of the functions fall within the control functions area.
+
+Connection functions are primarily covered in Recommendation Q.522. These address the basic switch characteristics of different connection types. OA&M functions are primarily covered in Recommendation Q.542.
+
+## 2.3 Utilization of exchange functions for services
+
+Exchange functions are used and reused in various stages of call processing. Some may be combined with others to create features used in providing supplementary services. The specific functions used in a given context will be determined by the requested service.
+
+
+
+Exchange functional model diagram showing various functional blocks within a 3D box. The top section is labeled 'Connection functions' and contains 'Switching functions' and two 'ET' (Exchange Terminal) blocks. Below 'Switching functions' are 'Connection/resources handling functions', 'Service processing functions', and 'Signalling functions'. The bottom section is labeled 'Control functions' and contains 'Operation and maintenance functions'. Lines connect the 'ET' blocks to the 'Switching functions', 'Signalling functions', and 'Operation and maintenance functions'. A reference code 'T1157050-93/d01' is at the bottom right.
+
+FIGURE 1/Q.521
+**Exchange functional model**
+
+Within the framework of the model shown in Figure 1, the utilization of functions arising from a service request can be considered in the following way:
+
+- a) on receipt of a service request (via the Signalling Functions) the Service Processing Functions are used to identify the appropriate connection type(s);
+- b) the appropriate type of connection is established by use of the Connection/Resources Handling Functions;
+- c) Supplementary Services which involve additional functions and information flows beyond those required for bearer services, are provided under the control of logic residing in the Service Processing Function. This logic is designed to provide specific services. Corresponding service/feature capabilities must also reside in the Signalling and Connection/Resources Handling Functions.
+
+In addition to services provided by use of logic/data residing in the exchange, some services may be provided under the control of logic located at separate specialized nodes (Service Control Points). Also, data required or process certain service requests may be kept in a remote data base accessed by use of the Signalling Function.
+
+# 3 General functions required in an exchange for operation in the IDN, ISDN or mixed analogue/digital environment
+
+## 3.1 Timing and synchronization
+
+### 3.1.1 Exchange timing
+
+Distribute timing within the exchange so that it will maintain synchronism on 64 kbit/s channel timeslots in a connection through the exchange.
+
+### 3.1.2 Synchronization
+
+Operate in the IDN or ISDN in synchronism with other digital entities and provide timing signals to other network entities as required.
+
+### 3.1.3 Interval timing
+
+Measure time between events as required for call processing and/or signalling.
+
+### **3.1.4 Time of day clock**
+
+Determine and indicate as required, time of day.
+
+NOTE – The level of accuracy of the time of day clock is for further study.
+
+## **3.2 Signalling**
+
+### **3.2.1 User access signalling functions**
+
+#### **3.2.1.1 In-band signalling**
+
+Receive/transmit and interpret decadic or Dual Tone Multi-Frequency (DTMF) signalling from/to users.
+
+#### **3.2.1.2 Digital subscriber signalling**
+
+- Support user access signalling layers 1 and 2 in accordance with Recommendations I.430, I.431 and Q.921.
+- Communicate with user terminals using layer 3 signalling in accordance with Recommendation Q.931.
+
+### **3.2.2 Network signalling functions**
+
+#### **3.2.2.1 CCITT Signalling systems**
+
+- Support and use CCITT signalling systems included in Recommendation Q.7 as required, particularly CCITT Signalling System No. 7.
+- Communicate with other network entities using the CCITT Signalling System No. 7, Q.700-Series of Recommendations User Parts.
+
+## **3.3 Data Packet Handling**
+
+### **3.3.1 Handle Packets**
+
+Transmit and receive data messages to/from users and data networks in accordance with Recommendation X.31.
+
+### **3.3.2 Interwork with data network(s)**
+
+Interface and interact with data networks in accordance with Recommendations X.31.
+
+## **3.4 Information retrieval and analysis**
+
+### **3.4.1 Access data bases**
+
+Gain access to data bases internal or external to the exchange.
+
+### **3.4.2 Retrieve information from:**
+
+#### **3.4.2.1 User/line data bases**
+
+Retrieve information about access lines and/or users such as “class of service”, priority level, parameters of basic bearer and teleservices subscribed to, etc.
+
+#### **3.4.2.2 Interexchange circuit data bases**
+
+Retrieve information about interexchange circuit groups, such as the identity of the entity to which it connects, the size of the circuit group and the location of its terminations, the type of circuits (incoming, outgoing or both ways), type of transmission system (analogue, digital), signalling required, etc.
+
+#### **3.4.2.3 Data base relating to “other terminations”**
+
+Retrieve information about other terminations on the exchange (tone circuits, announcements, bridge terminations, etc.).
+
+#### **3.4.2.4 Data base related to routing information**
+
+Retrieve information needed to determine how to route a call attempt based on the called number, call history and/or other pertinent information (e.g. network management information).
+
+#### **3.4.2.5 Data base of charging information**
+
+Retrieve information needed to determine the charging functions and rates needed for a particular call attempt or service usage.
+
+### **3.4.3 Analyze information**
+
+Relate information pertaining to a call attempt or service request to information obtained from data base(s) to determine the appropriate course of action.
+
+## **3.5 Resource management**
+
+### **3.5.1 Monitor the status of resources**
+
+Detect changes in status (busy, idle, out of service, etc.) of resources (lines, interexchange circuits, other terminations, exchange components, etc.).
+
+### **3.5.2 Maintain status information**
+
+Determine in real time the availability of all resources for use in call attempt or service request processing and for other functions (e.g. network management).
+
+### **3.5.3 Establish and maintain information relating to call attempts**
+
+Establish and maintain in registers for as long as necessary, information (service used, calling and called numbers, resources used, etc.) and events (connect time, disconnect time, etc.) related to individual calls, attempts or services used.
+
+### **3.5.4 Check continuity**
+
+Verify that proper transmission capability is available on a connection or resource when such a check is required and take appropriate action when the check fails.
+
+### **3.5.5 Check proper operation of resources**
+
+Verify the proper operation of user access and exchange or transit resources, as required, and to take appropriate action when verification fails.
+
+### **3.5.6 Handle queues**
+
+Establish and manage queues, as required, when the number of bids exceeds the available resources required to handle them.
+
+## **3.6 Ongoing operations**
+
+### **3.6.1 Make measurements**
+
+Make and record counts of attempts and events, measurements of usage and occupancy of resources, as required.
+
+### **3.6.2 Calculate percentages**
+
+Calculate in real time the ratio or percent of total volumes attempts, events, etc., as required.
+
+### **3.6.3 Detect and react to congestion**
+
+Detect when specified congestion thresholds are reached and to take appropriate action.
+
+### **3.6.4 Generate/respond to network management controls**
+
+Generate and respond as required to network management controls, signals and/or messages.
+
+### **3.6.5 Interact with TMN operations systems/centres**
+
+Communicate and interact with Operations Systems (Network Management, Accounting, Maintenance, etc.) via the Telecommunications Management Network (TMN).
+
+### **3.6.6 Report faults/failure events**
+
+Detect and report faults and their cause, if known, to the appropriate system(s) or centre(s).
+
+### **3.6.7 Perform charging functions:**
+
+#### **3.6.7.1 Accumulate and store charging data**
+
+Accumulate and store call or service information required for proper billing.
+
+#### **3.6.7.2 Format charging data**
+
+Assemble call or service charging details into the proper format for transfer as required for billing computation.
+
+#### **3.6.7.3 Transfer charging data**
+
+Send charging details as required (batch or per call), to accounting centre or billing system or function.
+
+#### **3.6.7.4 Send charging information to user**
+
+Indicate to the user, as required, the amount of charging involved in the use of the service.
+
+NOTE- This function may be a service feature provided on a national basis.
+
+# **4 Functions used in processing bearer service call attempts**
+
+## **4.1 Process Service Request**
+
+Recognize and respond to service request.
+
+Recognize and interpret signals or messages from users that indicate the initiation of a call (or a request for service), acknowledge the receipt of the signal or message as required and take action to process the call or initiate the service.
+
+## **4.2 Connect (through connect)/Disconnect**
+
+Establish, as required, a path or virtual path through exchange (one-way or two-way)/ take down connection through exchange and make resources available for other call attempts.
+
+## **4.3 Perform originating screening (in originating exchange)**
+
+### **4.3.1 Identify the calling user**
+
+Determine the ISDN number of the user based on line or channel class and information sent by the user.
+
+### **4.3.2 Determine the user terminal characteristics**
+
+Determine the characteristics of the user terminal based on its ISDN number.
+
+### **4.3.3 Examine service request**
+
+Determine the required service characteristics by examining information sent by the calling terminal.
+
+### **4.3.4 Examine user's service authorization**
+
+Determine whether or not the user is authorized to use the requested service.
+
+### **4.3.5 Determine priority**
+
+Determine the priority level assigned to a user line or terminal and/or priority level of a particular call/message based on priority information associated with the call/message.
+
+### **4.3.6 Establish call reference**
+
+Assign and retain for the duration of a call (or service usage), internal reference(s) for associating the resources used with the call (or service usage) and for keeping status information.
+
+## **4.4 Perform terminating screening (in terminating exchange)**
+
+### **4.4.1 Identify called user (in exchange serving the called user)**
+
+Identify the called user line(s)/channel(s) and their characteristics based on the called subscriber number.
+
+### **4.4.2 Determine the user terminal characteristics based on its ISDN number.**
+
+### **4.4.3 Verify that the called user is authorized and/or capable of receiving the call/service request.**
+
+### **4.4.4 Establish call reference**
+
+Assign and retain for the duration of the call (or service usage), internal reference(s) for associating the resources used with the call (or service usage) and for keeping status information.
+
+## **4.5 Process Attempt**
+
+### **4.5.1 Analyze called number**
+
+Examine the called number and determine routing and other required treatment (e.g. special handling and/or treatment).
+
+### **4.5.2 Analyze routing information**
+
+Analyze routing information, service requirements, any network management controls in effect and routing information sent by the user (e.g. restriction on using satellite links).
+
+### **4.5.3 Determine connection elements type**
+
+Determine the connection types and elements (resources) required to provide the requested service.
+
+### **4.5.4 Determine outgoing route/circuit group**
+
+Determine the appropriate sequence of routing choices (e.g. circuit groups) based on address and routing information analysis.
+
+### **4.5.5 Select resources**
+
+Select specific available resources (access channel, outgoing circuit, other resources, etc.) for use in setting up the call or service. In a terminating exchange, if called user channels are busy or unable to complete the call or establish service, return appropriate signal or message toward originating user.
+
+### **4.5.6 Select path through exchange**
+
+Select an available path through the exchange for use on the call to provide a connection between incoming and outgoing terminations or a means of passing data messages through the exchange.
+
+### **4.5.7 Reserve resources:**
+
+#### **4.5.7.1 User-network access**
+
+Hold the selected channel(s)/virtual channel available for use in supporting the requested service or call attempt.
+
+#### **4.5.7.2 Interexchange circuits**
+
+Hold the selected circuit(s)/virtual channel available for use on a call attempt or service.
+
+#### **4.5.7.3 Other resources**
+
+Hold echo suppression, pads and other equipment or functions available for use on the call or call attempt, if required.
+
+**4.5.8** Forward SETUP information as required and/or send alerting signal/indication or message(s) toward called user/calling user, as required.
+
+# **5 Additional functions required to provide ISDN Supplementary Services**
+
+(For further study.)
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.542-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.542-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f5f0163b6639177fb1759bb7ae266b7ea0e74bae
--- /dev/null
+++ b/marked/Q/T-REC-Q.542-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:09b354e87129f05bcb77020c381f41a37d9e662173cd868065a773273dd51ee0
+size 8243
diff --git a/marked/Q/T-REC-Q.542-199303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.542-199303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3c20b9030c52bf161e9185febd96d8218adb803a
--- /dev/null
+++ b/marked/Q/T-REC-Q.542-199303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:51e89a3bb6f1ea54365b7d5424dc3fdc228c785b51b20c2fe2db057ec2f49c55
+size 30383
diff --git a/marked/Q/T-REC-Q.601-199303-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg b/marked/Q/T-REC-Q.601-199303-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..17d45d9ec8bcace082cc1fa41f356b0c65c70329
--- /dev/null
+++ b/marked/Q/T-REC-Q.601-199303-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:23b202216cd67da83a0e8e890d13f58b5709e0c8a4f8e432d869af5bea6b17b5
+size 77256
diff --git a/marked/Q/T-REC-Q.601-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.601-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fc3613d199fb5f1141376b048e331e8f59322e59
--- /dev/null
+++ b/marked/Q/T-REC-Q.601-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6d0489a5a2a7a54dfc039e7a210c900fb99a610a86ac83095811d5346c95e690
+size 8283
diff --git a/marked/Q/T-REC-Q.614-199303-I_PDF-E/191a4a245a7d36d03be9a990d0f758f5_img.jpg b/marked/Q/T-REC-Q.614-199303-I_PDF-E/191a4a245a7d36d03be9a990d0f758f5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..522679e65755398e4fe564fec20006b7f293f7c7
--- /dev/null
+++ b/marked/Q/T-REC-Q.614-199303-I_PDF-E/191a4a245a7d36d03be9a990d0f758f5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3b111089942393543a2e081eec409dd060cd7742320f916c78585c7df063b3de
+size 147400
diff --git a/marked/Q/T-REC-Q.614-199303-I_PDF-E/1956f44611abd5c3c41049836aa78ad8_img.jpg b/marked/Q/T-REC-Q.614-199303-I_PDF-E/1956f44611abd5c3c41049836aa78ad8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8d5aff1524b0abf97fc2575c4a52171ecfa1e9cd
--- /dev/null
+++ b/marked/Q/T-REC-Q.614-199303-I_PDF-E/1956f44611abd5c3c41049836aa78ad8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:854b272d1e699b13ac967fd26e50f8b65de54f1afa20ef6706050b6766aa635e
+size 155432
diff --git a/marked/Q/T-REC-Q.614-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.614-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fc3613d199fb5f1141376b048e331e8f59322e59
--- /dev/null
+++ b/marked/Q/T-REC-Q.614-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6d0489a5a2a7a54dfc039e7a210c900fb99a610a86ac83095811d5346c95e690
+size 8283
diff --git a/marked/Q/T-REC-Q.614-199303-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg b/marked/Q/T-REC-Q.614-199303-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8decc90c1cb974e5945cf847fccfb2a7cdb93c87
--- /dev/null
+++ b/marked/Q/T-REC-Q.614-199303-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:205fa6b42386e47a23f70d05e445a3ccde6a450eea48104f5755d14df877d91d
+size 156486
diff --git a/marked/Q/T-REC-Q.614-199303-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg b/marked/Q/T-REC-Q.614-199303-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..352f62b1f496b4c0e58def3610f79037b39f49e0
--- /dev/null
+++ b/marked/Q/T-REC-Q.614-199303-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e700bd8c776d8135d26b23a4a0a7d001dbf2e821e5b96a8d32fc47f73cf94e93
+size 185593
diff --git a/marked/Q/T-REC-Q.614-199303-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg b/marked/Q/T-REC-Q.614-199303-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..16c874d9f5c021af9b7af637f5a84d594de45793
--- /dev/null
+++ b/marked/Q/T-REC-Q.614-199303-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b6657348ed051ec274d4db2a8f4b153f80c9d3bb272837e12fb8def7115e4f2d
+size 87864
diff --git a/marked/Q/T-REC-Q.614-199303-I_PDF-E/69edc2887e907309499ac95b47ab6905_img.jpg b/marked/Q/T-REC-Q.614-199303-I_PDF-E/69edc2887e907309499ac95b47ab6905_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2769abb4e1535535eddfc19c40dd23155f7e7178
--- /dev/null
+++ b/marked/Q/T-REC-Q.614-199303-I_PDF-E/69edc2887e907309499ac95b47ab6905_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:310f21e451067e82f00adac4235aa5694260ff979ab6f3a7d9c2854c51084b69
+size 56977
diff --git a/marked/Q/T-REC-Q.614-199303-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.614-199303-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36ca8c042cb38d7c74b0592aa1dd3ede26df0cce
--- /dev/null
+++ b/marked/Q/T-REC-Q.614-199303-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:69781cd74999e7d17dda48bc4a52d72d4202b63f38d9f05ec7868ed08205a90e
+size 101172
diff --git a/marked/Q/T-REC-Q.614-199303-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg b/marked/Q/T-REC-Q.614-199303-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0ec0302c31cf5771d2979d5c0d2293c657053192
--- /dev/null
+++ b/marked/Q/T-REC-Q.614-199303-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a538aafe844aa54f67beda600a0043ea4b29dd526ae1a4aff6897e70607f300e
+size 96657
diff --git a/marked/Q/T-REC-Q.614-199303-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg b/marked/Q/T-REC-Q.614-199303-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8daa69b6bfa8fe319c72098747c8ef3b33dd47e2
--- /dev/null
+++ b/marked/Q/T-REC-Q.614-199303-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:61996c41f0248f84a94f730a6f40d777b34001261107f30ff875d48b2344061a
+size 151945
diff --git a/marked/Q/T-REC-Q.614-199303-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg b/marked/Q/T-REC-Q.614-199303-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..026d90fba34b8973c17a8bfd40d9da456f34a862
--- /dev/null
+++ b/marked/Q/T-REC-Q.614-199303-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f08833155b3178219d29c3586d5863c06bd29fe9a3df95b0fac721944529c84b
+size 111499
diff --git a/marked/Q/T-REC-Q.614-199303-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg b/marked/Q/T-REC-Q.614-199303-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..935e4039bbfb791bead536c207e8680b9c456413
--- /dev/null
+++ b/marked/Q/T-REC-Q.614-199303-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:859bdd10d9d61997141b3f0ba7c652b06c588ba13c7e95344db886f3020e49df
+size 148162
diff --git a/marked/Q/T-REC-Q.614-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.614-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..084f30fe9467c19d4edbc74954d5dc113c84320d
--- /dev/null
+++ b/marked/Q/T-REC-Q.614-199303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ad3d543e359e15f0c6240fa212dec2701edf80b2c11a5d67535eeddec7ff900e
+size 105379
diff --git a/marked/Q/T-REC-Q.614-199303-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.614-199303-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ca551dc70427d4deef7af911f48a92067e3ab277
--- /dev/null
+++ b/marked/Q/T-REC-Q.614-199303-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:490d3c427fca4c9ea3f41fa65c98b562d65bd189a612ccc66dd166c6ab6d6d0b
+size 70000
diff --git a/marked/Q/T-REC-Q.614-199303-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg b/marked/Q/T-REC-Q.614-199303-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2f62f1a34ce82da2259d0e8d6cbd20fd8c4b92a9
--- /dev/null
+++ b/marked/Q/T-REC-Q.614-199303-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:097630a8a368dd15ffa7000cebecc584e35f5e2768038ee987263e7bd2d3cadf
+size 120532
diff --git a/marked/Q/T-REC-Q.614-199303-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg b/marked/Q/T-REC-Q.614-199303-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b5126f593de06dc10d3b40d2b72762080fe0bf9b
--- /dev/null
+++ b/marked/Q/T-REC-Q.614-199303-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:96274d36ff0591d94f8833652cf18aaff895a589a5d388c424739aa098ae7846
+size 123277
diff --git a/marked/Q/T-REC-Q.643-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.643-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..58422460ac68383d489df264ecc68ec71942a51a
--- /dev/null
+++ b/marked/Q/T-REC-Q.643-198811-I_PDF-E/raw.md
@@ -0,0 +1,165 @@
+
+
+
+
+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.643**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**INTERWORKING OF SIGNALLING SYSTEMS**
+
+---
+
+**LOGIC PROCEDURES FOR
+INTERWORKING OF SIGNALLING
+SYSTEM No.5 TO No.7 (TUP)**
+
+**ITU-T Recommendation Q.643**
+
+(Extract from the *Blue Book*)
+
+---
+
+# NOTES
+
+1 ITU-T Recommendation Q.643 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. 7 (TUP)
+
+
+
+```
+
+ graph LR
+ 00((00)) --> 01((01))
+ 01 --> 02((02))
+ 02 --> 03((03))
+ 03 --> 04((04))
+ 04 --> 05((05))
+ 05 --> 06((06))
+ 06 --> 05
+ 06 --> 00
+ 05 --> 00
+ 04 --> 00
+ 03 --> 00
+ 02 --> 00
+ 01 --> 00
+
+```
+
+State overview diagram showing states 00 through 06 with transitions between them. 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 include 00 to 01, 01 to 02, 02 to 03, 03 to 04, 04 to 05, 05 to 06, and various return paths to 00 or 01.
+
+CCITT-48650
+
+| State number | State description | Sheet reference |
+|---------------------|---------------------------|------------------------|
+| 00 | Idle | 1, 2, 3 |
+| 01 | Wait for CPCI-FITE | 1 |
+| 02 | Wait for ST | 2 |
+| 03 | Wait for address-complete | 3 |
+| 04 | Wait for answer | 3 |
+| 05 | Answered | 3 |
+| 06 | Clear-back | 3 |
+
+FIGURE 1/Q.643
+
+State overview diagram for interworking of Signalling System No. 5 to No. 7 (TUP)
+
+FIGURE 2/Q.643
+
+(Reserved for future notes)
+
+Connector reference
+
+
+
+The flowchart illustrates the interworking process between Signalling System No. 5 and No. 7 (TUP). It begins with an 'Idle' state (00), followed by 'Activate I/W No. 5/No. 7 (TUP)'. The next state is 'Wait for CPCI-FITE' (01). From this state, the process branches into three parallel paths: 'FITE 1', 'FITEs 9-13, 17', and 'FITE 22'. The 'FITE 1' path leads to a junction point. The 'FITEs 9-13, 17' path leads to 'Activate outgoing No. 7', which then leads to a decision diamond 'SPITE 36'. If 'SPITE 36' is 'Yes', the path goes to 'FITE 26'. If 'SPITE 36' is 'No', the path goes to 'FITE 25'. Both 'FITE 26' and 'FITE 25' lead to 'FITE 24'. The 'FITE 22' path leads to an 'Idle' state (00). From 'FITE 24', the path leads to a decision diamond 'SPITE 22'. If 'SPITE 22' is 'Yes', the path goes to 'FITE 3'. If 'SPITE 22' is 'No', the path goes to 'FITE 2'. Both 'FITE 3' and 'FITE 2' lead to a decision diamond 'SPITE 20'. If 'SPITE 20' is 'Yes', the path goes to 'FITE 21'. If 'SPITE 20' is 'No', the path goes to 'FITE 20'. Both 'FITE 21' and 'FITE 20' lead to a connector circle labeled '1' with a subscript '2' below it. The text 'CCITT - 60170' is located at the bottom right of the diagram.
+
+```
+graph TD; Idle00_1((00 Idle)) --> ActivateI[Activate I/W No. 5/No. 7 (TUP)]; ActivateI --> Wait01((01 Wait for CPCI-FITE)); Wait01 --> FITE1[FITE 1]; Wait01 --> FITEs91317[FITEs 9-13, 17]; Wait01 --> FITE22[FITE 22]; FITE1 --> Junction1(( )); FITEs91317 --> ActivateOut[Activate outgoing No. 7]; ActivateOut --> SPITE36{SPITE 36}; SPITE36 -- Yes --> FITE26[FITE 26]; SPITE36 -- No --> FITE25[FITE 25]; FITE26 --> FITE24[FITE 24]; FITE25 --> FITE24; FITE22 --> Idle00_2((00 Idle)); FITE24 --> SPITE22{SPITE 22}; SPITE22 -- Yes --> FITE3[FITE 3]; SPITE22 -- No --> FITE2[FITE 2]; FITE3 --> SPITE20{SPITE 20}; FITE2 --> SPITE20; SPITE20 -- Yes --> FITE21[FITE 21]; SPITE20 -- No --> FITE20[FITE 20]; FITE21 --> Connector((1 2)); FITE20 --> Connector; CCITT[CCITT - 60170];
+```
+
+Flowchart for interworking of Signalling System No. 5 to No. 7 (TUP).
+
+FIGURE 3/Q.643 (Sheet 1 of 3)
+
+## **Interworking of Signalling System No. 5 to No. 7 (TUP)**
+
+Connector reference
+
+
+
+```
+
+ graph TD
+ Start((1)) --> SPITE21{SPITE 21}
+ SPITE21 -- No --> FITE4{{FITE 4}}
+ SPITE21 -- Yes --> FITE5{{FITE 5}}
+ FITE4 --> WhichCPCI{Which CPCI-FITE}
+ FITE5 --> WhichCPCI
+ WhichCPCI -- 9-13 --> FITE913{{FITE 9-13}}
+ WhichCPCI -- 17 --> FITE17{{FITE 17}}
+ FITE913 --> Connector2((2))
+ FITE17 --> Connector2
+ Connector2 --> AnyMoreFITE1{Any more FITE 1}
+ AnyMoreFITE1 -- No --> Connector10((10))
+ AnyMoreFITE1 -- Yes --> WaitST([Wait for ST])
+ WaitST --> FITE1{{FITE 1}}
+ WaitST --> BITEs9101219{{BITEs 9, 10, 12, 19}}
+ WaitST --> FITE22{{FITE 22}}
+ WaitST --> BITEs23{{BITEs 2, 3}}
+ WaitST --> BITE15{{BITE 15}}
+ WaitST --> BITE30_1{{BITE 30}}
+ FITE1 --> CountryCode{Country code FITE}
+ BITEs9101219 --> BITE8{{BITE 8}}
+ BITE8 --> Idle([Idle])
+ FITE22 --> Connector3((3))
+ BITEs23 --> Connector4((4))
+ BITE15 --> Connector5((5))
+ BITE30_1 --> BITE30_2{{BITE 30}}
+ BITE30_2 --> Connector10_2((10))
+ CountryCode -- Yes --> SPITE22{SPITE 22}
+ CountryCode -- No --> FITE1_2{{FITE 1}}
+ SPITE22 -- Yes --> Idle
+ SPITE22 -- No --> OmitCC[Omit country code FITE]
+ OmitCC --> Connector2_2((2))
+ FITE1_2 --> STFITE{ST FITE}
+ STFITE -- No --> Connector2_2
+ STFITE -- Yes --> Connector6((6))
+
+```
+
+The flowchart illustrates the interworking process between Signalling System No. 5 and No. 7 (TUP). It begins at connector reference 1, leading to a decision 'SPITE 21'. If 'No', it goes to 'FITE 4'; if 'Yes', it goes to 'FITE 5'. Both lead to a decision 'Which CPCI-FITE'. From there, paths 9-13 lead to 'FITE 9-13' and path 17 leads to 'FITE 17'. Both converge at connector reference 2. The next decision is 'Any more FITE 1'. If 'No', it goes to connector reference 10. If 'Yes', it goes to 'Wait for ST'. From 'Wait for ST', multiple parallel paths emerge: 'FITE 1', 'BITEs 9, 10, 12, 19', 'FITE 22', 'BITEs 2, 3', 'BITE 15', and 'BITE 30'. 'FITE 1' leads to 'Country code FITE'. 'BITEs 9, 10, 12, 19' leads to 'BITE 8', which leads to 'Idle'. 'FITE 22', 'BITEs 2, 3', and 'BITE 15' lead to connector references 3, 4, and 5 respectively. 'BITE 30' leads to another 'BITE 30' block, which leads to connector reference 10. From 'Country code FITE', a 'Yes' leads to 'SPITE 22' (which leads to 'Idle') and a 'No' leads to 'FITE 1'. From this 'FITE 1', a decision 'ST FITE' is made. If 'No', it goes to connector reference 2. If 'Yes', it goes to connector reference 6. A 'No' from 'SPITE 22' leads to 'Omit country code FITE', which then goes to connector reference 2. Connector references are indicated by circles with numbers and subscripts (e.g., 102).
+
+Flowchart for interworking of Signalling System No. 5 to No. 7 (TUP).
+
+CCITT - 60180
+
+FIGURE 3/Q.643 (Sheet 2 of 3)
+
+## **Interworking of Signalling System No. 5 to No. 7 (TUP)**
+
+Connector reference
+
+
+
+Flowchart showing the interworking of Signalling System No. 5 to No. 7 (TUP). The diagram is divided into three main horizontal sections. The top section starts with a connector '6' (2, 3) leading to state '03 Wait for address complete'. From here, it branches into several paths: one through 'BITEs 2-7' (dashed box) to 'BITE 27' (4, 2) to state '04 Wait for answer'; another through 'BITEs 9, 10, 12, 19' to 'BITE 8' to state '00 Idle'; a third through 'BITEs 14-17, 20' (5, 2) to 'BITE 28' to 'SPITE 6 Return appropriate tone' to state '00 Idle'; a fourth through 'FITE 22' (3, 3) to connector '6'; a fifth through 'BITE 30' to 'BITE 30' to connector '6'; and a sixth through 'BITE 31' to 'SPITE 48' to 'FITE 31' to connector '6'. A 'Note' is present near the bottom right of this section. The middle section starts from state '04 Wait for answer' and branches into 'BITEs 22, 23' to 'BITE 22' (3, 8) to state '05 Answered'; 'BITEs 10, 12, 19' to 'BITE 8' to state '00 Idle'; 'FITE 23' (3, 3) to connector '7'; and 'FITE 22' (3, 3) to connector '3'. The bottom section starts from state '05 Answered' and branches into 'BITE 26' to 'FITE 25' (3, 9) to state '06 Clear-back'; 'FITE 23' (3, 8) to connector '8'; and 'FITE 22' (3, 3) to connector '3'. From state '06 Clear-back', it branches into 'FITE 22' (3, 3) to 'FITE 22' (2, 3(3X)) to state '00 Idle'; 'FITE 23' (3, 9) to connector '9'; and 'BITE 24' to 'BITE 22' (3, 8) to connector '8'. Connector references are listed on the far left: 6, 5, 4, 3, 2, 7, 6, 3, 8, 7, 3, 9, 8, 3, 9, 8.
+
+TI104830-87
+
+Note — This FITE 31 is to be translated as appropriate (e.g. Calling Party Category).
+
+FIGURE 3/Q.643 (Sheet 3 of 3)
+Interworking of Signalling System No. 5 to No. 7 (TUP)
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.644-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.644-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7
--- /dev/null
+++ b/marked/Q/T-REC-Q.644-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e
+size 7392
diff --git a/marked/Q/T-REC-Q.644-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg b/marked/Q/T-REC-Q.644-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..802ad0c44aa857f25e399221e9a5de88a47a92ed
--- /dev/null
+++ b/marked/Q/T-REC-Q.644-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fe12d224b87ec7745dadd24d5f619a8ca2ee56a92dfb97eeb38ddb65f1d4d34a
+size 137958
diff --git a/marked/Q/T-REC-Q.644-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg b/marked/Q/T-REC-Q.644-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..63d38b1033290c27c947e5385bb590a2fd0b9ee8
--- /dev/null
+++ b/marked/Q/T-REC-Q.644-198811-I_PDF-E/7055f51feb10ea4ea48b27c36f085286_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e2a3cdc2738b95d6d8ac00de204841e27617b2255b15d11354c2482ef85481fa
+size 15802
diff --git a/marked/Q/T-REC-Q.692-199303-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg b/marked/Q/T-REC-Q.692-199303-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..184acb3ff2ce1bde9c048d3ce7783db69ccb5de4
--- /dev/null
+++ b/marked/Q/T-REC-Q.692-199303-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:454462fa79a389f2821c9cac0f9b67bcb8e32bfdc93a78baaa4374dda3eeab8c
+size 102980
diff --git a/marked/Q/T-REC-Q.692-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.692-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4b5559cf9a04d2a8e852b41c26b061989ed057a1
--- /dev/null
+++ b/marked/Q/T-REC-Q.692-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d4347473be39f5fd6731072a5226322bd7af51a20a089e7c488009f059b8dff8
+size 8248
diff --git a/marked/Q/T-REC-Q.692-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg b/marked/Q/T-REC-Q.692-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..531d83ec573f7319ed64a3e86919f4534c582e3d
--- /dev/null
+++ b/marked/Q/T-REC-Q.692-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b0e45747e206b39729caee6d717b16335f405d33b08ba7b3cdece6ece58c2308
+size 78843
diff --git a/marked/Q/T-REC-Q.692-199303-I_PDF-E/69edc2887e907309499ac95b47ab6905_img.jpg b/marked/Q/T-REC-Q.692-199303-I_PDF-E/69edc2887e907309499ac95b47ab6905_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f2e8630fc7b268d8781046762bd06eefbf6f9dc5
--- /dev/null
+++ b/marked/Q/T-REC-Q.692-199303-I_PDF-E/69edc2887e907309499ac95b47ab6905_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:210ff3656c7c14e548d5234a47b0a9e59b7281561db43ed12c291308a155199d
+size 15880
diff --git a/marked/Q/T-REC-Q.692-199303-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg b/marked/Q/T-REC-Q.692-199303-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b8585be52cd682b203b9cc45fb0094dfd0c32f0a
--- /dev/null
+++ b/marked/Q/T-REC-Q.692-199303-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6dd59e95cea1d8089a98f1f7848a7765527e5003622910abff31f6cc12bd88e8
+size 96769
diff --git a/marked/Q/T-REC-Q.692-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/Q/T-REC-Q.692-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9efd57fd87cc59592cf5f411aa2b09399892ab7c
--- /dev/null
+++ b/marked/Q/T-REC-Q.692-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:80eba1326cb2e1ebed51cdebe897e91f882f6c31798f021e8b85ced8e4c1929a
+size 115931
diff --git a/marked/Q/T-REC-Q.695-199303-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg b/marked/Q/T-REC-Q.695-199303-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..31836fecc96c6633ed258eb38ee5e01f502686b5
--- /dev/null
+++ b/marked/Q/T-REC-Q.695-199303-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d996fde06aaa52622be157417be0e76bfd050e05be509a304f632c55b8a3b94f
+size 42987
diff --git a/marked/Q/T-REC-Q.695-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.695-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0eeb8829efe00ca6857e17a1c883c5415de977de
--- /dev/null
+++ b/marked/Q/T-REC-Q.695-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7314649a623c7a570ebd4418127f3815eeb09d6580453c739863947abec1a6f1
+size 8274
diff --git a/marked/Q/T-REC-Q.695-199303-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg b/marked/Q/T-REC-Q.695-199303-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ae9de1c94bc234f525ad19aa2c094ad4e23475a8
--- /dev/null
+++ b/marked/Q/T-REC-Q.695-199303-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:afbf9a835525409cb75d6b92d4907621065eeae6f6ea58938e4957f160f5c0e4
+size 34702
diff --git a/marked/Q/T-REC-Q.695-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg b/marked/Q/T-REC-Q.695-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e2e1255e4a76a2c405fdc8c1c02323d01ffb8cb8
--- /dev/null
+++ b/marked/Q/T-REC-Q.695-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2b24111c172fc19e41e572bd1174e3e0823254432f98fc9ef4e6445bd928bca2
+size 89669
diff --git a/marked/Q/T-REC-Q.695-199303-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg b/marked/Q/T-REC-Q.695-199303-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..304f29886afe26a6816b461055c3c7a70e1fa91d
--- /dev/null
+++ b/marked/Q/T-REC-Q.695-199303-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2494ad83bd05852d27aa19ba60c231f4a3c08518ec8217b71a5a5ac4db29f0f8
+size 59149
diff --git a/marked/Q/T-REC-Q.695-199303-I_PDF-E/69edc2887e907309499ac95b47ab6905_img.jpg b/marked/Q/T-REC-Q.695-199303-I_PDF-E/69edc2887e907309499ac95b47ab6905_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..09748ce5d22ffaa1ae3f98705fda1603964dcb93
--- /dev/null
+++ b/marked/Q/T-REC-Q.695-199303-I_PDF-E/69edc2887e907309499ac95b47ab6905_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:32bda7bd8761b8675a730e6805a2bf433a3f2496e3f972514552c8c1505b730e
+size 14697
diff --git a/marked/Q/T-REC-Q.695-199303-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.695-199303-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1ff152fce44e2c18a504111c2f1fe81c05dc4ae2
--- /dev/null
+++ b/marked/Q/T-REC-Q.695-199303-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8bd1d991460f4b774f5ce406aa457c20ac45fbfc28e28e08b9a031c3ead6842c
+size 67323
diff --git a/marked/Q/T-REC-Q.695-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/Q/T-REC-Q.695-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ddfe7d3797928b3518fbc4b38f3043306790c2f0
--- /dev/null
+++ b/marked/Q/T-REC-Q.695-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1192860a4351411d38fe95740c1170e08444218082941ff343bec6006e5435de
+size 58023
diff --git a/marked/Q/T-REC-Q.695-199303-I_PDF-E/raw.md b/marked/Q/T-REC-Q.695-199303-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..3cd1e648f0de01588c2c14f9337eae2a0fc10a3a
--- /dev/null
+++ b/marked/Q/T-REC-Q.695-199303-I_PDF-E/raw.md
@@ -0,0 +1,335 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' written across the center.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**Q.695**
+
+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 R2**
+
+**ITU-T Recommendation Q.695**
+
+(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.695 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 SYSTEMS – LOGIC PROCEDURES FOR INTERWORKING OF SIGNALLING SYSTEM No. 7 (ISUP) TO R2**
+
+*(Helsinki, 1993)*
+
+
+
+```
+
+stateDiagram-v2
+ [*] --> 00
+ 00 --> 01
+ 01 --> 02
+ 02 --> 03
+ 03 --> 04
+ 04 --> 05
+ 05 --> 04
+ 02 --> 00
+ 03 --> 00
+ 04 --> 00
+ 05 --> 00
+
+```
+
+State overview diagram showing six states (00 to 05) in a sequence. State 00 is Idle, 01 is Wait for call set up information, 02 is Wait for address-complete, 03 is Wait for answer, 04 is Answered, and 05 is Clear-back. Transitions are shown between consecutive states, with feedback loops from 02, 03, 04, and 05 back to 00. A return transition is also shown from 05 to 04. The diagram is labeled T114 1650-92/d01.
+
+| State number | State description | Sheet reference |
+|---------------------|----------------------------------|------------------------|
+| 00 | Idle | 1, 2, 4, 5, 6 |
+| 01 | Wait for call set up information | 1 |
+| 02 | Wait for address-complete | 2 |
+| 03 | Wait for answer | 4 |
+| 04 | Answered | 6 |
+| 05 | Clear-back | 6 |
+
+FIGURE 1/Q.695
+
+**State overview diagram for interworking of Signalling System No. 7 (ISUP) to R2**
+
+
+
+Connector reference
+
+```
+
+graph TD
+ 00([00 Idle]) --> Act1[Activate SS No. 7 (ISUP) to R2]
+ Act1 --> 01([01 Wait for call set up info.])
+ 01 --> FITEA[FITE A Call set up info.]
+ FITEA --> SPITE53[SPITE 53 Analyse info received and generate appropriate BITE and FITE]
+ SPITE53 --> Act2[Activate outgoing R2]
+ Act2 --> B((B))
+
+```
+
+T1130820-91/d02
+
+Flowchart showing the interworking of Signalling System No. 7 (ISUP) to R2. The sequence starts at state 00 (Idle), followed by activating SS No. 7 (ISUP) to R2, state 01 (Wait for call set up info.), FITE A (Call set up info.), SPITE 53 (Analyse info received and generate appropriate BITE and FITE), and finally activating outgoing R2, leading to connector B.
+
+FIGURE 3/Q.695 (sheet 1 of 6)
+**Interworking of Signalling System No. 7 (ISUP) to R2**
+
+Connector
+reference
+
+
+
+```
+
+graph TD
+ B((B 1)) --> FITEs{{FITEs 9-13, 15, 18, 19}}
+ FITEs --> SPITE22{SPITE 22}
+ SPITE22 -- Yes --> SPITE21_R{SPITE 21}
+ SPITE22 -- No --> FITE2{{FITE 2}}
+ FITE2 --> SPITE21_L{SPITE 21}
+ SPITE21_L -- No --> FITE4{{FITE 4}}
+ SPITE21_L -- Yes --> FITE5{{FITE 5}}
+ SPITE21_R -- No --> FITE7{{FITE 7}}
+ SPITE21_R -- Yes --> FITE8{{FITE 8}}
+ FITE4 --> C1((1 3))
+ FITE5 --> C1
+ FITE7 --> C1
+ FITE8 --> C1
+
+```
+
+T1130830-91/d03
+
+Flowchart showing interworking of Signalling System No. 7 (ISUP) to R2. It starts at connector B (1), goes through FITEs 9-13, 15, 18, 19, then SPITE 22. If SPITE 22 is Yes, it goes to SPITE 21. If No, it goes to FITE 2. From FITE 2, it goes to SPITE 21. If SPITE 21 is Yes, it goes to FITE 5. If No, it goes to FITE 4. From the first SPITE 21, if Yes, it goes to FITE 8. If No, it goes to FITE 7. All FITEs (4, 5, 7, 8) lead to connector 1 (3).
+
+FIGURE 3/Q.695 (sheet 2 of 6)
+**Interworking of Signalling System No. 7 (ISUP) to R2**
+
+
+
+Connector reference
+
+```
+
+graph TD
+ 1((1)) -- "2, 3(2x)" --> 02[02
+Wait for
+address
+complete]
+ 02 --> C((C))
+ 02 --> FITE1_1[/FITE 1/]
+ 02 --> FITE25[/FITE 25/]
+ 02 --> FITE24[/FITE 24/]
+ FITE25 --> AnyFITEWithheld{Any FITE
+withheld?}
+ FITE24 --> AnyFITEWithheld
+ AnyFITEWithheld -- Yes --> FITE1_2[/FITE 1/]
+ AnyFITEWithheld -- No --> 1_3((1
+3))
+ FITE1_2 --> T1130840_91_d04[T1130840-91/d04]
+ FITE1_1 --> CountryCodeFITE{Country
+code FITE?}
+ CountryCodeFITE -- Yes --> SPITE22{SPITE 22}
+ CountryCodeFITE -- No --> FITE24or25{FITE
+24 or 25 received?}
+ FITE24or25 -- Yes --> SPITE22
+ FITE24or25 -- No --> WithholdCodeFITE{Withhold
+code FITE?}
+ WithholdCodeFITE -- Yes --> 1_3
+ WithholdCodeFITE -- No --> FITE1_3[/FITE 1/]
+ FITE1_3 --> 1_3
+ SPITE22 -- Yes --> 1_3
+ SPITE22 -- No --> 1_3
+ WithholdCodeFITE -.-> Note["(Note)"]
+
+```
+
+Flowchart for Intertworking of Signalling System No. 7 (ISUP) to R2. The process starts at connector 1, goes to a 'Wait for address complete' state (02), then branches through FITE 1, FITE 25, and FITE 24 to connector C (4). From FITE 25 and FITE 24, it proceeds to a decision 'Any FITE withheld?'. If 'Yes', it goes through FITE 1. If 'No', it goes to connector 1 (3). From FITE 1 (after C), it goes to 'Country code FITE?'. If 'Yes', it goes to 'SPITE 22'. If 'No', it goes to 'FITE 24 or 25 received?'. If 'Yes' to 'FITE 24 or 25 received?', it goes to 'SPITE 22'. If 'No', it goes to 'Withhold code FITE?'. If 'Yes' to 'Withhold code FITE?', it goes to connector 1 (3). If 'No', it goes through FITE 1 to connector 1 (3). A 'Note' is associated with the 'Withhold code FITE?' decision. The diagram is labeled T1130840-91/d04.
+
+NOTE – Sufficient FITEs must be withheld to prevent an address-complete signal being received before (continuity) has been established when this is performed.
+
+FIGURE 3/Q.695 (sheet 3 of 6)
+Intertworking of Signalling System No. 7 (ISUP) to R2
+
+
+
+Connector reference
+
+```
+
+graph TD
+ C((C
+3)) --> A((A
+5))
+ A --> B1[BITes 2, 5, 6]
+ B1 --> B2[SPITE 53
+(Table 1)]
+ B2 --> B3{BITE X}
+ B3 --> B4((03
+Wait for
+answer))
+ B4 --> B5{BITE 21}
+ B4 --> B6{FITE Z}
+ B5 --> B7[SPITE 53
+(Table 3)]
+ B6 --> B8{FITE 22}
+ B7 --> B9{BITE Y}
+ B8 --> B10((Idle))
+ B9 --> 2((2
+6))
+ B10 --> T1130850-91/d05
+
+```
+
+C, A
+
+3
+
+C
+
+A
+
+5
+
+BITes 2, 5, 6
+
+SPITE 53
+(Table 1)
+
+BITE X
+
+03
+Wait for
+answer
+
+BITE 21
+
+FITE Z
+
+SPITE 53
+(Table 3)
+
+FITE 22
+
+BITE Y
+
+Idle
+
+T1130850-91/d05
+
+2
+
+6
+
+Flowchart showing the interworking of Signalling System No. 7 (ISUP) to R2. The process starts at connector C (3) and ends at connector A (5). It includes steps for BITes 2, 5, 6, SPITE 53 (Table 1), BITE X, waiting for an answer (03), BITE 21, FITE Z, SPITE 53 (Table 3), FITE 22, BITE Y, and an Idle state, eventually reaching connector 2 (6).
+
+FIGURE 3/Q.695 (sheet 4 of 6)
+**Interworking of Signalling System No. 7 (ISUP) to R2**
+
+Connector
+reference
+
+
+
+```
+graph TD; A((A
+4)) --> FITE_Z{{FITE Z}}; FITE_Z --> FITE_22{{FITE 22}}; FITE_22 --> Idle1([Idle]); A --> BITes["BITes 11, 12, 13, 15, 16, 17, 20"]; BITes --> SPITE_53["SPITE 53
+(Table 2)"]; SPITE_53 --> BITE_Z{{BITE Z}}; BITE_Z --> Idle2([Idle]);
+```
+
+Flowchart showing the interworking of Signalling System No. 7 (ISUP) to R2. It starts at connector 'A' (labeled '4'), leading to 'FITE Z'. 'FITE Z' connects to 'FITE 22', which leads to an 'Idle' state. A parallel path from 'A' goes to a block with 'BITes 11, 12, 13, 15, 16, 17, 20', which connects to 'SPITE 53 (Table 2)'. 'SPITE 53' connects to 'BITE Z', which leads to another 'Idle' state. A vertical double line on the left is labeled 'A'. The diagram is labeled 'T1 130860-91/d06' at the bottom right.
+
+FIGURE 3/Q.695 (sheet 5 of 6)
+Interworking of Signalling System No. 7 (ISUP) to R2
+
+
+
+Connector reference
+
+```
+
+stateDiagram-v2
+ [*] --> 04 : 2 (4, 6)
+ 04 --> FITE_Z_1 : FITE Z
+ FITE_Z_1 --> FITE_22_1 : FITE 22
+ FITE_22_1 --> 00_1 : 00 Idle
+ 04 --> BITE_25_1 : BITE 25
+ BITE_25_1 --> BITE_25_2 : BITE 25
+ BITE_25_2 --> 05 : 2 (6)
+ 05 --> FITE_Z_2 : FITE Z
+ FITE_Z_2 --> FITE_22_2 : FITE 22
+ FITE_22_2 --> 00_2 : 00 Idle
+ 05 --> BITE_21 : BITE 21
+ BITE_21 --> BITE_24 : BITE 24
+ BITE_24 --> 2_6 : 2 (6)
+
+```
+
+T1130870-91/d07
+
+State transition diagram for the interworking of Signalling System No. 7 (ISUP) to R2. The diagram shows two parallel state transition paths. The left path starts at connector 2 (4, 6), goes to state 04 'Answered', then through FITE Z to FITE 22, and finally to state 00 'Idle'. The right path starts at connector 2 (4, 6), goes to BITE 25, then through BITE 25 to state 05 'Clear-back'. From state 05, the path goes through FITE Z to FITE 22, and finally to state 00 'Idle'. Another connector 2 (6) is shown between the two paths, pointing to the transition from BITE 25 to state 05. A third connector 2 (6) is shown at the bottom right, pointing to the transition from BITE 24 to state 00 'Idle'. Connector reference '2' is indicated on the left side of the diagram at three points.
+
+FIGURE 3/Q.695 (sheet 6 of 6)
+**Interworking of Signalling System No. 7 (ISUP) to R2**
+
+TABLE 1/Q.695
+
+| | Received BITE | | |
+|---------------------------------|---------------|----|----|
+| | 2 | 5 | 6 |
+| Backward call indicators in ACM | | | |
+| Charging indicator | 10 | 10 | 01 |
+| Called party's status | 00 | 01 | 01 |
+| Called party's category | 00 | 00 | 00 |
+| Interworking indicator | 1 | 1 | 1 |
+
+TABLE 2/Q.695
+
+| Received BITE (release) | Cause sent | Location |
+|---------------------------------------|----------------------|-------------------------|
+| 13 | 34 | 1010 |
+| 11 | 34 | 1010 |
+| 12 | 34/127 a) | 1010/0111 a) |
+| 15 | 1 | 1010 |
+| 16 | 17 | 1010 |
+| 17 | 27 | 1010 |
+| 20 | 4 | 1010 |
+| a) Only in timeout expiry. | | |
+
+TABLE 3/Q.695
+
+| |
+|----------------------------------------------------|
+| Backward call indicators in ANM |
+| ANM without backward call indicators is to be sent |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.696-199706-I_PDF-E/01e00200a536673d6cd0e6d8705047a0_img.jpg b/marked/Q/T-REC-Q.696-199706-I_PDF-E/01e00200a536673d6cd0e6d8705047a0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..32879451bcb5c3f933df43e211424a1d98ed4d26
--- /dev/null
+++ b/marked/Q/T-REC-Q.696-199706-I_PDF-E/01e00200a536673d6cd0e6d8705047a0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f835f8f57f9093c107b0e72802a362e1e874b47bb322ed289de697e7b54b1305
+size 15846
diff --git a/marked/Q/T-REC-Q.696-199706-I_PDF-E/030c758fd425016b03290c8f11bef69d_img.jpg b/marked/Q/T-REC-Q.696-199706-I_PDF-E/030c758fd425016b03290c8f11bef69d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1203ed5147345bee96cab8d20c6c91644ea4eb95
--- /dev/null
+++ b/marked/Q/T-REC-Q.696-199706-I_PDF-E/030c758fd425016b03290c8f11bef69d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9f50e52914e09bcf085f854206f91e3955ce6a0d42dec01efd95ba0481864284
+size 15393
diff --git a/marked/Q/T-REC-Q.696-199706-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg b/marked/Q/T-REC-Q.696-199706-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f102a58439e8f7fe5f121d6f230456984d0ebe48
--- /dev/null
+++ b/marked/Q/T-REC-Q.696-199706-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf6e37a19803efd010b29d15199aed390c1b7952956f5ba043400c11f82adcef
+size 14425
diff --git a/marked/Q/T-REC-Q.696-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.696-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cc6438bcedc9e72173b2d8e74cd31c264ae32aeb
--- /dev/null
+++ b/marked/Q/T-REC-Q.696-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:40203e46b9f9a68e88bdb204bdd4b7e5899358c088ed2f2902abbc4eb57db8cb
+size 8190
diff --git a/marked/Q/T-REC-Q.696-199706-I_PDF-E/41aef1f5efab13d4f38f69e86c726062_img.jpg b/marked/Q/T-REC-Q.696-199706-I_PDF-E/41aef1f5efab13d4f38f69e86c726062_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a1cbd7e7941ca022c14399676405136e5f7569b3
--- /dev/null
+++ b/marked/Q/T-REC-Q.696-199706-I_PDF-E/41aef1f5efab13d4f38f69e86c726062_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:71acdd3ba0a1a3df161ff608784835c6581eac84cc7b4d4e2143245de41eca3f
+size 15599
diff --git a/marked/Q/T-REC-Q.696-199706-I_PDF-E/4ae4505e885586e481a3ad3bff5198b7_img.jpg b/marked/Q/T-REC-Q.696-199706-I_PDF-E/4ae4505e885586e481a3ad3bff5198b7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..08603cc1daae4a175d3dc338a22c28df5e1eccb2
--- /dev/null
+++ b/marked/Q/T-REC-Q.696-199706-I_PDF-E/4ae4505e885586e481a3ad3bff5198b7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88abd0b2b4973e23050387fa275aabd6b971360afa523845d1878e399aac817b
+size 13790
diff --git a/marked/Q/T-REC-Q.696-199706-I_PDF-E/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Q/T-REC-Q.696-199706-I_PDF-E/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9fc4d695bea707b7fee341be3e71c811e6a14b42
--- /dev/null
+++ b/marked/Q/T-REC-Q.696-199706-I_PDF-E/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e1a8dec9cfe66a5b63080b976172285f8da8d9ce7ef0a8d1c95e845543bae22d
+size 16424
diff --git a/marked/Q/T-REC-Q.696-199706-I_PDF-E/82fbb97c1145cac89ac72dd080fad17a_img.jpg b/marked/Q/T-REC-Q.696-199706-I_PDF-E/82fbb97c1145cac89ac72dd080fad17a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1f17921c481ea0ca3277c3800c25c32f8c8daca2
--- /dev/null
+++ b/marked/Q/T-REC-Q.696-199706-I_PDF-E/82fbb97c1145cac89ac72dd080fad17a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:61acd815694838458ed2f822feb3a5258c31c59165c0ee5c4766eeb35cb604f3
+size 14378
diff --git a/marked/Q/T-REC-Q.696-199706-I_PDF-E/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Q/T-REC-Q.696-199706-I_PDF-E/8e80de0cac529b2c3775d677c5203133_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3d3f6885375079f8d8bb651cafb0b77382a1dcb3
--- /dev/null
+++ b/marked/Q/T-REC-Q.696-199706-I_PDF-E/8e80de0cac529b2c3775d677c5203133_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c3572bf41f6a9b2366aaead6883e201fb2cc13e9d1cf2909cbe4be6ed794dacb
+size 29899
diff --git a/marked/Q/T-REC-Q.696-199706-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Q/T-REC-Q.696-199706-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..eed0394b6319248aa323c6b992f53c7380db0e2c
--- /dev/null
+++ b/marked/Q/T-REC-Q.696-199706-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:36c01727b507a5373634a611ac850182f440b18edcf1e597bf6f44042c3b3173
+size 13670
diff --git a/marked/Q/T-REC-Q.696-199706-I_PDF-E/ae0a735d106290c594b0bafb1f5e72e7_img.jpg b/marked/Q/T-REC-Q.696-199706-I_PDF-E/ae0a735d106290c594b0bafb1f5e72e7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5f27a42aa8ae65382b4bca118d304db58eef8aa9
--- /dev/null
+++ b/marked/Q/T-REC-Q.696-199706-I_PDF-E/ae0a735d106290c594b0bafb1f5e72e7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1c507cecb2e4940a0f65f3f79cfad3370bd30b6dd31b70aa6d08beab98392232
+size 16186
diff --git a/marked/Q/T-REC-Q.696-199706-I_PDF-E/b05bae46f7079e5c9b1da38adb2319e8_img.jpg b/marked/Q/T-REC-Q.696-199706-I_PDF-E/b05bae46f7079e5c9b1da38adb2319e8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bac834e8ff623744004253b1f950b43e07fb68f0
--- /dev/null
+++ b/marked/Q/T-REC-Q.696-199706-I_PDF-E/b05bae46f7079e5c9b1da38adb2319e8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d12d875b4ea0304819addc5fbbbe3b61edb8d3ca55a188d8825771221ebade75
+size 16234
diff --git a/marked/Q/T-REC-Q.696-199706-I_PDF-E/bb4d2112ed07e2031c92fbff3494af9f_img.jpg b/marked/Q/T-REC-Q.696-199706-I_PDF-E/bb4d2112ed07e2031c92fbff3494af9f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b1a8188ad923e4af6ed3d9a4294c36f03484d2b2
--- /dev/null
+++ b/marked/Q/T-REC-Q.696-199706-I_PDF-E/bb4d2112ed07e2031c92fbff3494af9f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:973d1af6c5ef8bb80fa50c3eeb9b2a8929a368c88102ff8d2eb197c9b1448c59
+size 15169
diff --git a/marked/Q/T-REC-Q.696-199706-I_PDF-E/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg b/marked/Q/T-REC-Q.696-199706-I_PDF-E/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e52324cc721b0040addf0adb08ad4245ba77ff1d
--- /dev/null
+++ b/marked/Q/T-REC-Q.696-199706-I_PDF-E/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:45b83b899b9693752520ad8cbebd3f3c4495901c4a632f9736f27c63ced160c5
+size 14709
diff --git a/marked/Q/T-REC-Q.696-199706-I_PDF-E/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Q/T-REC-Q.696-199706-I_PDF-E/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..57e597cf3cb6120a03193b6fb618ca7f0192a750
--- /dev/null
+++ b/marked/Q/T-REC-Q.696-199706-I_PDF-E/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4714e11dbf3afa2d03b855855ed35c13d77003f1aa35d5b18ee43b372c4522bd
+size 16465
diff --git a/marked/Q/T-REC-Q.696-199706-I_PDF-E/e05122559f56af5699789b7118d8fe87_img.jpg b/marked/Q/T-REC-Q.696-199706-I_PDF-E/e05122559f56af5699789b7118d8fe87_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c83b3ccaba82023fefbc68a63cb7ffa4efef334f
--- /dev/null
+++ b/marked/Q/T-REC-Q.696-199706-I_PDF-E/e05122559f56af5699789b7118d8fe87_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e68974d6a263c7524a9b19f22d8baf6cdf2d66b3c801b3a12c1c9b2786db3c90
+size 13791
diff --git a/marked/Q/T-REC-Q.696-199706-I_PDF-E/e22af684d8e56d4c61e61bb5ddac1087_img.jpg b/marked/Q/T-REC-Q.696-199706-I_PDF-E/e22af684d8e56d4c61e61bb5ddac1087_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b52788dd8704ba04f561f75ee3b3085d7d92e478
--- /dev/null
+++ b/marked/Q/T-REC-Q.696-199706-I_PDF-E/e22af684d8e56d4c61e61bb5ddac1087_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3142dc382cebf3b297e565d48cb599b4e14d9c6633fed3857fb688e0f1c637b9
+size 16040
diff --git a/marked/Q/T-REC-Q.696-199706-I_PDF-E/ec3647789b5c38fb686f2a0833324e79_img.jpg b/marked/Q/T-REC-Q.696-199706-I_PDF-E/ec3647789b5c38fb686f2a0833324e79_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..063894db31c46e9da67ffdd2e66590802595ebf6
--- /dev/null
+++ b/marked/Q/T-REC-Q.696-199706-I_PDF-E/ec3647789b5c38fb686f2a0833324e79_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:880fd45da0920ef532bbd750056186c9db9593696ab0672434d674fad9c2dd07
+size 12846
diff --git a/marked/Q/T-REC-Q.696-199706-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg b/marked/Q/T-REC-Q.696-199706-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7d6c0ed3a32d68f72d5b26a559677a672e20a7db
--- /dev/null
+++ b/marked/Q/T-REC-Q.696-199706-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:892ef69a4a58f9102f787b2117b604db875d3faa94b453b34d5f2ae601b77374
+size 16717
diff --git a/marked/Q/T-REC-Q.703-199607-I_PDF-E/raw.md b/marked/Q/T-REC-Q.703-199607-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c20b22e0c2881adef1b29731c2a8d1d063710fac
--- /dev/null
+++ b/marked/Q/T-REC-Q.703-199607-I_PDF-E/raw.md
@@ -0,0 +1,3883 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.703**
+
+(07/96)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Specifications of Signalling System No. 7 – Message
+transfer part
+
+---
+
+**Signalling link**
+
+ITU-T Recommendation Q.703
+
+(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 |
+| 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 |
+| General | Q.700 |
+| Message transfer part | Q.701–Q.709 |
+| Simplified message transfer part | Q.710 |
+| Signalling connection control part | Q.711–Q.719 |
+| Telephone user part | Q.720–Q.729 |
+| ISDN supplementary services | Q.730–Q.739 |
+| Data user part | Q.740–Q.749 |
+| Signalling System No. 7 management | Q.750–Q.759 |
+| ISDN user part | Q.760–Q.769 |
+| Transaction capabilities application part | Q.770–Q.779 |
+| Test specification | Q.780–Q.799 |
+| Q3 interface | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+
+For further details, please refer to ITU-T List of Recommendations.
+
+## **ITU-T RECOMMENDATION Q.703**
+
+## **SIGNALLING LINK**
+
+## **Summary**
+
+This Recommendation describes the functions and procedures for and relating to the transfer of messages over one signalling data link. Annex A has been added to support the use of data rates of 1.5 and 2.0 Mbit/s as a national option. In addition some errors in the SDL diagrams have been corrected.
+
+## **Source**
+
+ITU-T Recommendation Q.703 was revised by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 9th of July 1996.
+
+## 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 (Helsinki, March 1-12, 1993).
+
+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.
+
+© ITU 1997
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+# CONTENTS
+
+###### Page
+
+| | | |
+|--------|-----------------------------------------------------------------------------|----|
+| 1 | General..... | 1 |
+| 1.1 | Introduction..... | 1 |
+| 1.2 | Signal unit delimitation and alignment..... | 1 |
+| 1.3 | Error detection ..... | 1 |
+| 1.4 | Error correction..... | 2 |
+| 1.5 | Initial alignment..... | 3 |
+| 1.6 | Signalling link error monitoring ..... | 3 |
+| 1.7 | Link state control functions ..... | 3 |
+| 1.8 | Flow control..... | 3 |
+| 2 | Basic signal unit format ..... | 4 |
+| 2.1 | General..... | 4 |
+| 2.2 | Signal unit format ..... | 6 |
+| 2.3 | Function and codes of the signal unit fields..... | 6 |
+| 2.3.1 | General..... | 6 |
+| 2.3.2 | Flag..... | 6 |
+| 2.3.3 | Length indicator..... | 7 |
+| 2.3.4 | Service information octet..... | 7 |
+| 2.3.5 | Sequence numbering..... | 7 |
+| 2.3.6 | Indicator bits ..... | 7 |
+| 2.3.7 | Check bits ..... | 7 |
+| 2.3.8 | Signalling information field..... | 7 |
+| 2.3.9 | Status field ..... | 7 |
+| 2.3.10 | Spare fields ..... | 7 |
+| 2.4 | Order of bit transmission ..... | 8 |
+| 3 | Signal unit delimitation..... | 8 |
+| 3.1 | Flags..... | 8 |
+| 3.2 | Zero insertion and deletion ..... | 8 |
+| 4 | Acceptance procedure..... | 8 |
+| 4.1 | Acceptance of alignment..... | 8 |
+| 4.2 | Error detection ..... | 8 |
+| 5 | Basic error correction method..... | 9 |
+| 5.1 | General..... | 9 |
+| 5.2 | Acknowledgements (positive acknowledgement and negative acknowledgement)... | 10 |
+| 5.2.1 | Sequence numbering..... | 10 |
+
+| | Page |
+|--------------------------------------------------------------|-------------|
+| 5.2.2 Signal unit sequence control..... | 10 |
+| 5.2.3 Positive acknowledgement ..... | 11 |
+| 5.2.4 Negative acknowledgement..... | 11 |
+| 5.3 Retransmission..... | 11 |
+| 5.3.1 Response to a positive acknowledgement ..... | 11 |
+| 5.3.2 Response to a negative acknowledgement..... | 12 |
+| 5.3.3 Repetition of message signal units ..... | 13 |
+| 6 Error correction by preventive cyclic retransmission ..... | 13 |
+| 6.1 General..... | 13 |
+| 6.2 Acknowledgements..... | 13 |
+| 6.2.1 Sequence numbering..... | 13 |
+| 6.2.2 Signal unit sequence control..... | 13 |
+| 6.2.3 Positive acknowledgement ..... | 14 |
+| 6.3 Preventive cyclic retransmission..... | 14 |
+| 6.3.1 Response to a positive acknowledgement ..... | 14 |
+| 6.3.2 Preventive cyclic retransmission procedure ..... | 15 |
+| 6.4 Forced retransmission ..... | 15 |
+| 6.4.1 Forced retransmission procedure..... | 15 |
+| 6.4.2 Limitation of the values $N_1$ and $N_2$ ..... | 15 |
+| 7 Initial alignment procedure..... | 16 |
+| 7.1 General..... | 16 |
+| 7.2 Initial alignment status indications ..... | 16 |
+| 7.3 Initial alignment procedure..... | 16 |
+| 7.4 Proving periods ..... | 18 |
+| 8 Processor outage ..... | 19 |
+| 9 Level 2 flow control..... | 20 |
+| 9.1 General..... | 20 |
+| 9.2 Detection of congestion ..... | 20 |
+| 9.3 Procedure in the congestion situation ..... | 20 |
+| 9.4 Congestion abatement procedure..... | 20 |
+| 10 Signalling link error monitoring ..... | 21 |
+| 10.1 General..... | 21 |
+| 10.2 Signal unit error rate monitor..... | 21 |
+| 10.3 Alignment error rate monitor ..... | 22 |
+| 11 Level 2 codes and priorities ..... | 22 |
+
+| | Page |
+|--------------------------------------------------------------------------------|-------------|
+| 11.1 Link status signal unit ..... | 22 |
+| 11.2 Transmission priorities within level 2 ..... | 23 |
+| 12 State transition diagrams, abbreviations and timers ..... | 24 |
+| 12.2 Abbreviations..... | 24 |
+| 12.3 Timers ..... | 26 |
+| Annex A –Additions for a national option for high speed signalling links ..... | 81 |
+| A.1 Introduction..... | 81 |
+| A.1.1 Procedures for 1.5 and 2.0 Mbit/s data rate signalling links ..... | 82 |
+| A.4 Acceptance procedure..... | 83 |
+| A.4.1 Acceptance of alignment ..... | 83 |
+| A.10.1 General..... | 83 |
+| A.10.2 Errored interval monitor for 1.5 Mbit/s and 2.0 Mbit/s links ..... | 83 |
+| A.10.3 Alignment error rate monitor..... | 84 |
+| A.12.3 Timers..... | 84 |
+
+
+
+# **SIGNALLING LINK**
+
+*(Geneva 1980; modified at Helsinki, 1993, revised in 1996)*
+
+# **1 General**
+
+## **1.1 Introduction**
+
+**1.1.1** This Recommendation describes the functions and procedures for and relating to the transfer of signalling messages over one signalling data link. The signalling link functions, together with a signalling data link as bearer, provide a signalling link for reliable transfer of signalling messages between two directly connected *signalling points*.
+
+Signalling messages delivered by superior hierarchical levels are transferred over the signalling link in variable length *signal units*. The signal units include transfer control information for proper operation of the signalling link in addition to the signalling information.
+
+**1.1.2** The signalling link functions comprise:
+
+- a) signal unit delimitation;
+- b) signal unit alignment;
+- c) error detection;
+- d) error correction;
+- e) initial alignment;
+- f) signalling link error monitoring;
+- g) flow control.
+
+All these functions are coordinated by the *link state control* (see Figure 1).
+
+## **1.2 Signal unit delimitation and alignment**
+
+The beginning and end of a signal unit are indicated by a unique 8-bit pattern, called the *flag*. Measures are taken to ensure that the pattern cannot be imitated elsewhere in the unit.
+
+Loss of alignment occurs when a bit pattern disallowed by the delimitation procedure (more than six consecutive 1 s) is received, or when a certain maximum length of signal unit is exceeded.
+
+Loss of alignment will cause a change in the mode of operation of the *signal unit error rate monitor*.
+
+## **1.3 Error detection**
+
+The error detection function is performed by means of 16 check bits provided at the end of each signal unit. The check bits are generated by the transmitting signalling link terminal by operating on the preceding bits of the signal unit following a specified algorithm. At the receiving *signalling link terminal*1, the received check bits are operated on using specified rules which correspond to that algorithm.
+
+---
+
+1 A *signalling link terminal* refers to the means of performing all of the functions defined at level 2 regardless of their implementation.
+
+If consistency is not found between the received check bits and the preceding bits of the signal unit, according to the algorithm, then the presence of errors is indicated and the signal unit is discarded.
+
+
+
+The diagram illustrates the interactions between functional specification blocks for signalling link control. It shows the flow of Message Signal Units (MSUs), Link Status Signal Units (LSSUs), and Signal Units (SUs) between various components.
+
+- Signalling network functions (level 3)** on the left interact with the **Link state control part** via dashed lines (controls and indications).
+- The **Link state control part** sends **MSUa)** (solid line) to the **Transmission part** and receives **LSSUa)** (dashed line) from the **Reception part**.
+- The **Reception part** (under **Signalling link control (level 2)**) receives **SUa)** (solid line) from the **Error detection delimitation and alignment** block and sends **LSSUa)** (dashed line) to the **Link state control part**.
+- The **Reception part** and **Transmission part** are connected by a dashed line (controls and indications) and both interact with the **Congestion control part** via dashed lines.
+- The **Transmission part** sends **MSUa)** (solid line) to the **Signalling data link (level 1)** and receives **Retrieved MSUa)** (solid line) from the **Error detection delimitation and alignment** block.
+- The **Error detection delimitation and alignment** block receives **Transmitted and received bits** (solid line) from the **Signalling data link (level 1)** and sends **SUa)** (solid line) to the **Reception part**.
+
+Legend:
+
+- Signalling message flows
+- - - - Controls and indications
+- MSU Message Signal Unit
+- SU Signal Unit
+- LSSU Link Status Signal Units
+
+a) These signal units do not include all error control information.
+
+T1156520-93
+
+Diagram showing interactions of functional specification blocks for signalling link control. It illustrates the flow of MSUs, LSSUs, and SUs between Signalling network functions (level 3), Signalling link control (level 2) blocks (Link state control, Reception, Congestion control, Transmission), Error detection delimitation and alignment, and Signalling data link (level 1).
+
+**Figure 1/Q.703 – Interactions of the functional specification blocks for signalling link control**
+
+## 1.4 Error correction
+
+**1.4.1** Two forms of error correction are provided, the *basic method* and the *preventive cyclic retransmission method*. The following criteria should be used for determining the international fields of application for the two methods:
+
+- the basic method applies for signalling links using non-intercontinental terrestrial transmission means and for intercontinental signalling links where the one-way propagation delay is less than 15 ms;
+- the preventive cyclic retransmission method applies for intercontinental signalling links where the one-way propagation delay is greater than or equal to 15 ms and for all signalling links established via satellite.
+
+In cases where one signalling link within an international link set is established via satellite, the preventive cyclic retransmission method should be used for all signalling links of that link set (combined linkset).
+
+**1.4.2** The basic method is a non-compelled, positive/negative acknowledgement, retransmission error correction system. A signal unit which has been transmitted is retained at the transmitting signalling link terminal until a positive acknowledgement for that signal unit is received. If a negative acknowledgement is received, then the transmission of new signal units is interrupted and those signal units which have been transmitted but not yet positively acknowledged starting with that
+
+indicated by the negative acknowledgement will be retransmitted once, in the order in which they were first transmitted.
+
+**1.4.3** The preventive cyclic retransmission method is a non-compelled, positive acknowledgement, cyclic retransmission, forward error correction system. A signal unit which has been transmitted is retained at the transmitting signalling link terminal until a positive acknowledgement for that signal unit is received. During the period when there are no new signal units to be transmitted, all the signal units which have not yet been positively acknowledged are retransmitted cyclically.
+
+The *forced retransmission procedure* is defined to ensure that forward error correction occurs in adverse conditions (e.g. high error rate and/or high traffic loading).
+
+When a predetermined number of retained, unacknowledged signal units exists, the transmission of new signal units is interrupted and the retained signal units are retransmitted cyclically until the number of unacknowledged signal units is reduced.
+
+## **1.5 Initial alignment**
+
+The initial alignment procedure is appropriate to both first time initialization (e.g. after "switch-on") and alignment in association with restoration after a link failure. The procedure is based on the compelled exchange of status information between the two *signalling points* concerned and the provision of a proving period. No other signalling link is involved in the initial alignment of any particular link, the exchange occurs only on the link to be aligned.
+
+## **1.6 Signalling link error monitoring**
+
+Two signalling link error rate monitor functions are provided: one which is employed whilst a signalling link is in service and which provides one of the criteria for taking the link out of service, and one which is employed whilst a link is in the proving state of the initial alignment procedure. These are called the *signal unit error rate monitor* and the *alignment error rate monitor* respectively. The characteristics of the signal unit error rate monitor are based on a signal unit error count, incremented and decremented using the "leaky bucket" principle whilst the alignment error rate monitor is a linear count of signal unit errors. During loss of alignment, the signal unit error rate monitor error count is incremented in proportion to the period of the loss of alignment.
+
+## **1.7 Link state control functions**
+
+*Link state control* is a function of the signalling link which provides directives to the other signalling link functions. The interfaces with link state control are shown in Figures 1 and 7. The split into the functional blocks shown in the figures is made to facilitate description of the signalling link procedures and should not be taken to imply any particular implementation.
+
+The link state control function is shown in the overview diagram, Figure 2, and the detailed state transition diagram, Figure 8.
+
+## **1.8 Flow control**
+
+Flow control is initiated when congestion is detected at the receiving end of the signalling link. The congested receiving end of the link notifies the remote transmitting end of the condition by means of an appropriate link status signal unit and it withholds acknowledgements of all incoming message signal units. When congestion abates acknowledgements of all incoming message signal units is resumed. While congestion exists, the remote transmitting end is periodically notified of this condition. The remote transmitting end will indicate the link as failed if the congestion continues too long.
+
+# 2 Basic signal unit format
+
+## 2.1 General
+
+Signalling and other information originating from a User Part is transferred over the signalling link by means of signal units.
+
+A signal unit is constituted of a variable length *signalling information field* which carries the information generated by a *User Part* and a number of fixed length fields which carry information required for message transfer control. In the case of link status signal units, the signalling information field and the service information octet is replaced by a status field which is generated by the signalling link terminal.
+
+
+
+```
+
+graph TD
+ %% Aligned already section
+ AA([Aligned already]) --> AA_FISU[/FISU or MSU/]
+ AA --> AA_SIPO[/SIPO/]
+ AA --> AA_LPO[/Local processor outage/]
+ AA --> AA_SIO[/SIO or SIOS/]
+ AA --> AA_LF[/Link failure/]
+ AA --> AA_Stop[/Stop/]
+
+ AA_FISU --> AA_SendMSU[Send MSU] --> InService([In Service])
+ AA_SIPO --> AA_PO[Processor outage]
+ AA_LPO --> AA_SendSIPO[Send SIPO] --> ANR([Aligned not ready])
+ AA_SIO --> AA_SendSIOS[Send SIOS] --> OS([Out of service])
+ AA_LF --> AA_SendSIOS
+ AA_Stop --> AA_SendSIOS
+
+ %% In service section
+ IS([In service]) --> IS_LPR[/Local processor recovered/]
+ IS --> IS_SIPO[/SIPO/]
+ IS --> IS_FISU[/FISU or MSU/]
+ IS --> IS_LF[/Link failure/]
+ IS --> IS_SIO[/SIO, SIN, SIE, SIOS/]
+ IS --> IS_Stop[/Stop/]
+
+ IS_LPR --> IS_SendFISU[Send FISU] --> AR([Aligned ready])
+ IS_SIPO --> IS_PO[Processor outage]
+ IS_FISU --> IS_SendFISU2[Send FISU] --> IS_PO2[Processor outage]
+ IS_LF --> IS_SendSIOS[Send SIOS] --> OS2([Out of service])
+ IS_SIO --> IS_SendSIOS
+ IS_Stop --> IS_SendSIOS
+
+ %% Out of service section (middle right)
+ OS_State([Out of service]) --> OS_LPR[/Local processor recovered/]
+ OS_State --> OS_SIPO[/SIPO/]
+ OS_State --> OS_FISU[/FISU or MSU/]
+ OS_State --> OS_LF[/Link failure/]
+ OS_State --> OS_SIO[/SIO, SIN, SIE, SIOS/]
+ OS_State --> OS_Stop[/Stop/]
+
+ OS_LPR --> OS_SendFISU[Send FISU] --> AR2([Aligned ready])
+ OS_SIPO --> OS_PO[Processor outage]
+ OS_FISU --> OS_SendFISU2[Send FISU] --> OS_PO2[Processor outage]
+ OS_LF --> OS_SendSIOS[Send SIOS] --> OS3([Out of service])
+ OS_SIO --> OS_SendSIOS
+ OS_Stop --> OS_SendSIOS
+
+ %% Power management section (left)
+ PowerOff([Power off]) --> PowerOn[/Power on/]
+ PowerOn --> SendSIOS_P[Send SIOS] --> OS_P([Out of service])
+ OS_P --> Start[/Start/] --> IA([Initial alignment])
+
+ %% Initial alignment section (bottom)
+ IA --> IA_ANP[/Aligned not possible/]
+ IA --> IA_Stop[/Stop/]
+ IA --> IA_LF[/Link failure/]
+ IA --> IA_AC[/Alignment complete/]
+
+ IA_ANP --> IA_SendSIOS[Send SIOS] --> OS_IA([Out of service])
+ IA_Stop --> IA_SendSIOS
+ IA_LF --> IA_SendSIOS
+ IA_AC --> IA_Dec{Local processor outage}
+ IA_Dec -- Yes --> IA_SendSIPO[Send SIPO] --> ANR_IA([Aligned not ready])
+ IA_Dec -- No --> IA_SendFISU[Send FISU] --> AR_IA([Aligned ready])
+
+```
+
+T1156530-93
+
+FISU Fill-In Signal Unit
+MSU Message Signal Unit
+SIE Status Indication “E”
+SIN Status Indication “N”
+SIO Status Indication “O”
+SIOS Status Indication “out of service”
+SIPO Status Indication “processor outage”
+
+Figure 2/Q.703 – Overview diagram of link state control. A complex flowchart showing transitions between states like 'In service', 'Out of service', 'Aligned ready', and 'Aligned not ready' based on signal units (FISU, MSU) and status indications (SIO, SIN, SIE, SIOS, SIPO).
+
+**Figure 2/Q.703 – Overview diagram of link state control**
+
+## 2.2 Signal unit format
+
+Three types of signal unit are differentiated by means of the *length indicator* contained in all signal units, i.e. message signal units, link status signal units and fill-in signal units. Message signal units are retransmitted in case of error, link status signal unit and fill-in signal units are not. The basic formats of the signal units are shown in Figure 3.
+
+
+
+**a) Basic format of a Message Signal Unit (MSU)**
+
+| | | | | | | | | | |
+|---|----|-----------|-----|----|-----|-----|-----|-----|---|
+| F | CK | SIF | SIO | LI | FIB | FSN | BIB | BSN | F |
+| 8 | 16 | 8n, n ≥ 2 | 8 | 6 | 1 | 7 | 1 | 7 | 8 |
+
+**b) Format of a Link Status Signal Unit (LSSU)**
+
+| | | | | | | | | |
+|---|----|---------|----|-----|-----|-----|-----|---|
+| F | CK | SF | LI | FIB | FSN | BIB | BSN | F |
+| 8 | 16 | 8 or 16 | 6 | 1 | 7 | 1 | 7 | 8 |
+
+**c) Format of a Fill-In Signal Unit (FISU)**
+
+| | | | | | | | |
+|---|----|----|-----|-----|-----|-----|---|
+| F | CK | LI | FIB | FSN | BIB | BSN | F |
+| 8 | 16 | 6 | 1 | 7 | 1 | 7 | 8 |
+
+T1156540-93
+
+Figure 3/Q.703 – Signal unit formats. Three diagrams showing the bit structure of MSU, LSSU, and FISU signal units. Each diagram shows fields: F (8 bits), CK (16 bits), SIF/SF (variable), SIO (8 bits), LI (6 bits), FIB (1 bit), FSN (7 bits), BIB (1 bit), BSN (7 bits), and F (8 bits). Arrows indicate the first bit transmitted.
+
+BIB Backward Indicator Bit
+ BSN Backward Sequence Number
+ CK Check bits
+ F Flag
+ FIB Forward Indicator Bit
+ FSN Forward Sequence Number
+ LI Length Indicator
+ n Number of octets in the SIF
+ SF Status Field
+ SIF Signalling Information Field
+ SIO Service Information Octet
+
+Figure 3/Q.703 – Signal unit formats
+
+## 2.3 Function and codes of the signal unit fields
+
+### 2.3.1 General
+
+The message transfer control information encompasses 8 fixed length fields in the signal unit which contains information required for error control and message alignment.
+
+### 2.3.2 Flag
+
+The opening flag indicates the start of a signal unit. The opening flag of one signal unit is normally the closing flag of the preceding signal unit. The closing flag indicates the end of a signal unit. The bit pattern for the flag is 01111110.
+
+### 2.3.3 Length indicator
+
+The length indicator is used to indicate the number of octets following the length indicator octet and preceding the *check bits* and is a number in binary code in the range 0-63. The length indicator differentiates between the three types of signal units as follows:
+
+| | |
+|----------------------------|-------------------------|
+| Length indicator = 0: | Fill-in signal unit |
+| Length indicator = 1 or 2: | Link status signal unit |
+| Length indicator > 2: | Message signal unit |
+
+In the case that the signalling information field of a message signal unit is spanning 62 octets or more, the length indicator is set to 63.
+
+It is mandatory that LI is set by the transmitting end to its correct value as specified above.
+
+### 2.3.4 Service information octet
+
+The *service information octet* is divided into the *service indicator* and the *subservice field*. The service indicator is used to associate signalling information with a particular user part and is present only in message signal units.
+
+The content of the subservice field is described in 14.2.2/Q.704.
+
+NOTE – The Message Transfer Part may handle messages for different users (i.e. messages with different service indicators) with different priorities. These priorities are for further study.
+
+### 2.3.5 Sequence numbering
+
+The *forward sequence number* is the sequence number of the signal unit in which it is carried.
+
+The *backward sequence number* is the sequence number of a signal unit being acknowledged.
+
+The forward sequence number and backward sequence number are numbers in binary code from a cyclic sequence ranging from 0 to 127 (see clauses 5 and 6).
+
+### 2.3.6 Indicator bits
+
+The *forward indicator bit* and *backward indicator bit* together with the forward sequence number and backward sequence number are used in the basic error control method to perform the signal unit sequence control and acknowledgement functions (see 5.2 and clause 6).
+
+### 2.3.7 Check bits
+
+Every signal unit has 16 check bits for error detection (see clause 4).
+
+### 2.3.8 Signalling information field
+
+The *signalling information field* consists of an integral number of octets, greater than or equal to 2 and less than or equal to 272.
+
+The value 272 allows a single message signal unit to accommodate information blocks of up to 268 octets in length accompanied by a routing label.
+
+The format and codes of the signalling information field are defined for each user part.
+
+### 2.3.9 Status field
+
+The formats and codes of the *status field* are described in clause 11.
+
+### 2.3.10 Spare fields
+
+Spare fields are coded 0, unless otherwise indicated (see Figures 3 and 6).
+
+## 2.4 Order of bit transmission
+
+Each of the fields mentioned in 2.3 will be transmitted in the order indicated in Figure 3.
+
+Within each field or subfield the bits will be transmitted with the least significant bit first. The 16 check bits are transmitted in the order generated (see clause 4).
+
+# 3 Signal unit delimitation
+
+## 3.1 Flags
+
+A signal unit includes an opening flag (see 2.2). The opening flag of a signal unit is normally considered to be the closing flag of the preceding signal unit. In certain conditions (e.g. signalling link overload) a limited number of flags may be generated between two consecutive signal units. However, a signalling link terminal always should be able to receive consecutive signal units with one or more multiple flags inserted between them.
+
+## 3.2 Zero insertion and deletion
+
+To ensure that the flag code is not imitated by any other part of the signal unit the transmitting signalling link terminal inserts a 0 after every sequence of five consecutive 1s before the flags are attached and the signal unit is transmitted. At the receiving signalling link terminal, after flag detection and removal, each 0 which directly follows a sequence of five consecutive 1s is deleted.
+
+# 4 Acceptance procedure
+
+## 4.1 Acceptance of alignment
+
+**4.1.1** A flag which is not followed immediately by another flag is considered an opening flag. Whenever an opening flag is received, the beginning of a signal unit is assumed. When the next flag (a closing flag) is received it is assumed to be the termination of the signal unit.
+
+**4.1.2** If seven or more consecutive 1s are received, the signal unit error rate monitor or alignment error rate monitor enters the "octet counting" mode (see 4.1.4) and the next valid flag is searched for.
+
+**4.1.3** After deletion of the 0s inserted for transparency, the received signal unit length is checked for being a multiple of 8 bits and at least 6 octets, including opening flag. If it is not, then the signal unit is discarded and the signal unit error rate monitor or alignment error rate monitor is incremented. If more than $m + 7$ octets are received before a closing flag, the "octet counting" mode is entered (see Figure 11) and the signal unit is discarded. $m$ is the maximum length of the signalling information field (in octets) allowed on a signalling link. $m$ takes the value 272. In the case of the basic error control method a negative acknowledgement will be sent, if required, according to the rules set out in 5.2.
+
+**4.1.4** When the "octet counting" mode is entered all the bits received after the last flag and before the next flag are discarded. The "octet counting" mode is left when the next correctly-checking signal unit is received, and this signal unit is accepted.
+
+## 4.2 Error detection
+
+The error detection function is performed by means of 16 check bits provided at the end of each signal unit.
+
+The check bits are generated by the transmitting signalling link terminal. They are the ones complement of the sum (modulo 2) of
+
+- i) the remainder of $x^k (x^{15} + x^{14} + x^{13} + x^{12} \dots + x^2 + x + 1)$ divided (modulo 2) by the generator polynomial $x^{16} + x^{12} + x^5 + 1$ , where $k$ is the number of bits in the signal unit existing between, but not including, the final bit of the opening flag and the first bit of the check bits, excluding bits inserted for transparency; and
+- ii) the remainder after multiplication by $x^{16}$ and then division (modulo 2) by the generator polynomial $x^{16} + x^{12} + x^5 + 1$ of the content of the signal unit existing between, but not including, the final bit of the opening flag and the first bit of the check bits, excluding bits inserted for transparency.
+
+As a typical implementation, at the transmitting signalling link terminal, the initial remainder of the division is preset to all 1 s and is then modified by division by the generator polynomial (as described above) on all the fields of the signal unit; the 1 s complement of the resulting remainder is transmitted as the 16 check bits.
+
+At the receiving signalling link terminal, the correspondence between the check bits and the remaining part of the signal unit is checked; if a complete correspondence is not found the signal unit is discarded.
+
+As a typical implementation at the receiving signalling link terminal, the initial remainder is preset to all 1 s, and the serial incoming protected bits including the check bits (after the bits inserted for transparency are removed) when divided by the generator polynomial will result in a remainder of 0001110100001111 ( $x^{15}$ through $x^0$ , respectively) in the absence of transmission errors.
+
+# 5 Basic error correction method
+
+## 5.1 General
+
+The basic error correction method is a noncompelled method in which correction is performed by retransmission. In normal operation, the method ensures correct transfer of message signal units over the signalling link, in sequence and with no double delivery. As a consequence, no resequencing or eliminating of the received information is required within the user parts.
+
+*Positive acknowledgements* are used to indicate correct transfer of message signal units. *Negative acknowledgements* are used as explicit requests for retransmission of signal units received in a corrupt form.
+
+To minimize the number of retransmissions and the resulting message signal unit delay, a request for retransmission is made only when a message signal unit (not another signal unit) has been lost because of, for example, transmission errors or disturbances.
+
+The method requires that transmitted but not yet positively acknowledged message signal units remain available for retransmission. To maintain the correct message signal unit sequence when a retransmission is made, the message signal unit, the retransmission of which has been requested, and any subsequently transmitted message signal units are retransmitted in the order in which they were originally transmitted.
+
+As part of the error correction method, each signal unit carries a forward sequence number, a *forward indicator bit*, a backward sequence number and a *backward indicator bit*. The error correction procedure operates independently in the two transmission directions. The forward sequence number and forward indicator bit in one direction together with the backward sequence number and backward indicator bit in the other direction are associated with the message signal unit flow in the first direction. They function independently of the message signal unit flow in the other
+
+direction and its associated forward sequence number, forward indicator bit, backward sequence number and backward indicator bit.
+
+The transmission of new message signal units is temporarily stopped during retransmissions or when no forward sequence number values are available to be assigned to new message signal units (due to a high momentary load or corruption of positive acknowledgements) (see 5.2.2).
+
+Under normal conditions, when no message signal units are to be transmitted or retransmitted, fill-in signal units are sent continuously. In some particular cases link status signal units, continuous fill-in signal units or flags may be sent as described in clauses 7, 8 and 11.
+
+## **5.2 Acknowledgements (positive acknowledgement and negative acknowledgement)**
+
+### **5.2.1 Sequence numbering**
+
+For the purposes of acknowledgement and signal unit sequence control, each signal unit carries two sequence numbers. The signal unit sequence control is performed by means of the forward sequence number. The acknowledgement function is performed by means of the backward sequence number.
+
+The value of the forward sequence number of a message signal unit is obtained by incrementing (modulo 128, see 2.3.5) the last assigned value by 1.
+
+This forward sequence number value uniquely identifies the message signal unit until its delivery is accepted without errors, and in correct sequence, by the receiving terminal. The forward sequence number of a signal unit other than a message signal unit assumes the value of the forward sequence number of the last transmitted message signal unit.
+
+### **5.2.2 Signal unit sequence control**
+
+Information regarding the service information octet, signalling information field, forward sequence number and the length of each message signal unit is retained at the transmitting signalling link terminal until a positive acknowledgement for that signal unit is received (see 5.2.3). In the meantime the same forward sequence number cannot be used for another message signal unit (see 5.2.3).
+
+A forward sequence number value can be assigned to a new message signal unit when a positive acknowledgement concerning that value incremented by at least 1 (modulo 128) is received (see 5.2.3).
+
+This means that not more than 127 message signal units may be available for retransmission.
+
+The action to be taken at the receiving signalling link terminal upon receipt of a correctly checking signal unit is determined by comparison of the received forward sequence number with the forward sequence number of the last previously accepted signal unit, and on comparison of the received forward indicator bit with the latest sent backward indicator bit. In addition, as the appropriate action differs for a message signal unit and another signal unit, the length indicator of the received signal unit must be examined.
+
+- a) If the signal unit is a fill-in signal unit then:
+ - i) if the forward sequence number value equals the forward sequence number value of the last accepted message signal unit, the signal unit is processed within the message transfer part;
+ - ii) if the forward sequence number value is different from the forward sequence number of the last accepted message signal unit, the signal unit is processed within the message transfer part. If the received forward indicator bit is in the same state as the last sent backward indicator bit, a negative acknowledgement is sent.
+
+- b) If the signal unit is a link status signal unit, then it is processed within the message transfer part.
+- c) If the signal unit is a message signal unit then:
+ - i) if the forward sequence number value is the same as that of the last accepted signal unit, the signal unit is discarded, regardless of the state of the indicator bits;
+ - ii) if the forward sequence number value is one more (modulo 128, see 2.3.5) than that of the last accepted signal unit and if the received forward indicator bit is in the same state as the last sent backward indicator bit, the signal unit is accepted and delivered to level 3.
+
+Explicit positive acknowledgements to the accepted signal units are sent as specified in 5.2.3.
+
+If the forward sequence number is one more than that of the last accepted signal unit and if the received forward indicator bit is not in the same state as the last sent backward indicator bit, then the signal unit is discarded;
+
+- iii) if the forward sequence number value is different from those values mentioned in i) and ii) above, the signal unit is discarded. If the received forward indicator bit is in the same state as the last sent backward indicator bit, a negative acknowledgement is sent.
+
+Processing of the backward sequence number value and backward indicator bit value as described in 5.3 is performed for message signal units and fill-in signal units except when unreasonable backward sequence number value or unreasonable forward indicator bit value is received. Discarding a signal unit means that if it is a message signal unit, it is not delivered to level 3.
+
+### **5.2.3 Positive acknowledgement**
+
+The receiving signalling link terminal acknowledges the acceptance of one or more message signal units by assigning the forward sequence number value of the latest accepted message signal unit to the backward sequence number of the next signal unit sent in the opposite direction. The backward sequence numbers of subsequent signal units retain this value until a further message signal unit is acknowledged, which will cause a change of the backward sequence number sent.
+
+The acknowledgement to an accepted message signal unit also represents an acknowledgement to all, if any, previously accepted, though not yet acknowledged, message signal units.
+
+### **5.2.4 Negative acknowledgement**
+
+If a negative acknowledgement is to be sent (see 5.2.2), then the backward indicator bit value of the signal units transmitted is inverted. The new backward indicator bit value is maintained in subsequently sent signal units until a new negative acknowledgement is to be sent. The backward sequence number assumes the value of the forward sequence number of the last accepted message signal unit.
+
+## **5.3 Retransmission**
+
+### **5.3.1 Response to a positive acknowledgement**
+
+The transmitting signalling link terminal examines the backward sequence number value of the received message signal units and fill-in signal units that have satisfied the polynomial error check. The previously sent message signal unit, which has a forward sequence number value identical to the received backward sequence number value, will no longer be available for transmission.
+
+When an acknowledgement of a message signal unit having a given forward sequence number value is received, all other message signal units which preceded that message signal unit are considered to be acknowledged even though the corresponding backward sequence numbers have not been received.
+
+In the case that the same positive acknowledgement is consecutively received a number of times, no further action is taken.
+
+In the case that a message signal unit or fill-in signal unit is received having a backward sequence number value which is not the same as the previous one or one of the forward sequence number values of the signal units available for retransmission, the signal unit is discarded. The following message signal unit or fill-in signal unit is discarded.
+
+If any two backward sequence number values in three consecutively received message signal units or fill-in signal units are not the same as the previous one or any of the forward sequence number values of the signal units in the retransmission buffer at the time that they are received, then level 3 is informed that the link is faulty.
+
+A timing mechanism, timer T72, shall be provided which generates an indication of excessive delay of acknowledgement if, assuming that there are at least one outstanding MSU in the retransmission buffer, no new-acknowledgement has been received within a time-out T7 (see 12.3). In the case of excessive delay in the reception of acknowledgements, a link failure indication is given to level 3.
+
+### 5.3.2 Response to a negative acknowledgement
+
+When the received backward indicator bit is not in the same state as the last sent forward indicator bit, all the message signal units available for retransmission are transmitted in correct sequence starting with the signal unit which has a forward sequence number value of one more (modulo 128, see 2.3.5) than the backward sequence number associated with the received backward indicator bit.
+
+New message signal units can only be sent when the last message signal unit available for retransmission has been transmitted.
+
+At the start of a retransmission the forward indicator bit is inverted, it thus becomes equal to the backward indicator bit value of the received signal units. The new forward indicator bit value is maintained in subsequently transmitted signal units until a new retransmission is started. Thus, under normal conditions the forward indicator bit included in the transmitted signal units is equal to the backward indicator bit value of the received signal units. If a retransmitted message signal unit is lost, then this is detected by a check on the forward sequence number and forward indicator bit (see 5.2.2) and a new retransmission request is made.
+
+In the case that a message signal unit or a fill-in signal unit is received having a forward indicator bit value indicating the start of a retransmission when no negative acknowledgement has been sent, then that signal unit is discarded. The following message signal unit or fill-in signal unit is discarded.
+
+If any two forward indicator bit values in three consecutively received message signal units or fill-in signal units indicate the start of a retransmission when no negative acknowledgement has been sent at the time that they are received, then level 3 is informed that the link is faulty.
+
+---
+
+2 Timers defined in this Recommendation are absolute time values. This means that, due to the possibility to insert multiple flags between signal units (see 3.1), there may be no fixed relation between the time-out values and the number of signal units transmitted/received during the time-out periods.
+
+### **5.3.3 Repetition of message signal units**
+
+The signal unit sequence control makes it possible to repeat a message signal unit which has not yet been acknowledged without affecting the basic error correction procedure. Thus a form of forward error correction by means of repetition of message signal units is possible as a national option (e.g. to reduce the effective signalling link speed in special national applications, and in long loop delay applications to lower the retransmission rate and thus reduce the average message delay). In the case of repetition, each signal unit should be defined by its own opening and closing flags (i.e. there should be at least two flags between signal units) to ensure that the repeated signal unit is not lost by the corruption of only a single flag.
+
+# **6 Error correction by preventive cyclic retransmission**
+
+## **6.1 General**
+
+The preventive cyclic retransmission method is essentially a noncompelled forward error correction method, whereby positive acknowledgements are needed to support the forward error correction.
+
+Each message signal unit must be retained at the transmitting signalling link terminal until a positive acknowledgement arrives from the receiving signalling link terminal.
+
+Error correction is effected by preventive cyclic retransmission of the message signal units already sent, though not yet acknowledged. Preventive cyclic retransmission takes place whenever there are no new message signal units or link status signal units available to be sent.
+
+To complement preventive cyclic retransmission, the message signal units available for retransmission are retransmitted with priority when a limit of the number of message signal units or a limit of the number of message signal unit octets available for retransmission has been reached.
+
+Under normal conditions, when no message signal units are to be transmitted or cyclically retransmitted, fill-in signal units are sent. In some particular cases link status signal units, continuous fill-in signal units or flags may be sent as described in clauses 7, 8 and 11.
+
+## **6.2 Acknowledgements**
+
+### **6.2.1 Sequence numbering**
+
+For the purposes of acknowledgement and signal unit sequence control, each signal unit carries 2 sequence numbers. The signal unit sequence control is performed by means of the forward sequence number. The acknowledgement function is performed by means of the backward sequence number.
+
+The value of the forward sequence number of a message signal unit is obtained by incrementing (modulo 128, see 2.3.5) the last assigned value by 1. This forward sequence number value uniquely identifies the message signal unit until its delivery is accepted without errors and in correct sequence, by the receiving signalling link terminal. The forward sequence number of a signal unit other than a message signal unit assumes the value of the forward sequence number of the last transmitted message signal unit.
+
+### **6.2.2 Signal unit sequence control**
+
+Information regarding the service information octet, signalling information field, forward sequence number and the length of each message signal unit is retained at the transmitting signal link terminal until the related acknowledgement for that signal unit is received (see 6.2.3). In the meantime the same forward sequence number value cannot be used for another message signal unit (see 6.2.3).
+
+A forward sequence number value can be assigned to a new message signal unit to be sent when a positive acknowledgement concerning that value incremented by at least 1 (modulo 128) is received (see 6.2.3).
+
+The action to be taken at the receiving signalling link terminal upon receipt of a correctly checking signal unit is determined by comparison of the received forward sequence number with the forward sequence number of the last previously accepted signal unit.
+
+In addition, as the appropriate action differs for a message signal unit and another signal unit, the length indicator of the received signal unit must be examined. The forward indicator bit and the backward indicator bit are not used and are set to 1.
+
+- a) If the signal unit is not a message signal unit, then the signal unit is processed within the message transfer part.
+- b) If the signal unit is a message signal unit then:
+ - i) if the forward sequence number value is the same as that of the last accepted signal unit, the signal unit is discarded;
+ - ii) if the forward sequence number value is one more (modulo 128, see 2.3.5) than that of the last accepted signal unit, the signal unit is accepted and delivered to level 3. Explicit positive acknowledgements for the accepted signal units are sent as specified in 6.2.3;
+ - iii) if the forward sequence number value is different from the values mentioned in i) and ii) above, the signal unit is discarded. Processing of the backward sequence number value as described in 6.3 is performed for message signal units and fill-in signal units except when unreasonable backward sequence number value is received. Discarding a signal unit means that if it is a message signal unit, it is not delivered to level 3.
+
+### 6.2.3 Positive acknowledgement
+
+The receiving signalling link terminal acknowledges the acceptance of one or more message signal units by assigning the forward sequence number value of the latest accepted message signal unit to the backward sequence number of the next signal unit sent. The backward sequence numbers of subsequent signal units retain this value until a further message signal unit is acknowledged, which will cause a change of the backward sequence number sent. The acknowledgement to an accepted message signal unit also represents an acknowledgement to all, if any, previously accepted though not yet acknowledged signal units.
+
+## 6.3 Preventive cyclic retransmission
+
+### 6.3.1 Response to a positive acknowledgement
+
+All message signal units sent for the first time are retained until they have been positively acknowledged.
+
+The transmitting signalling link terminal examines the backward sequence number value of the received message signal units and fill-in signal units that have satisfied the polynomial error check. The previously sent message signal unit, the forward sequence number value of which is the same as the backward sequence number value, will no longer be available for retransmission.
+
+When an acknowledgement for a message signal unit having a given forward sequence number value is received, all other message signal units, if any, having forward sequence number values preceding that value (modulo 128) are considered to be acknowledged, even though the corresponding backward sequence number has not been received.
+
+In the case that the same positive acknowledgement is consecutively received a number of times, no further action is taken.
+
+In the case that a message signal unit or fill-in signal unit is received having a backward sequence number value which is not the same as the previous one or one of the forward sequence number values of the signal units in the retransmission buffer, the signal unit is discarded. The following message signal unit or fill-in signal unit is discarded.
+
+If any two backward sequence number values in three consecutively received message signal units or fill-in signal units are not the same as the previous one or any of the forward sequence number values of the signal units in the retransmission buffer at the time that they are received, then level 3 is informed that the link is faulty.
+
+A timing mechanism, timer T7, shall be provided which generates an indication of excessive delay of acknowledgement if, assuming that there is at least one outstanding MSU in the retransmission buffer, no new acknowledgement has been received within a time-out T7 (see 12.3). In the case of excessive delay in the reception of acknowledgements, a link failure indications is given to level 3.
+
+### 6.3.2 Preventive cyclic retransmission procedure
+
+- i) If no new signal units are available to be sent, the message signal units available for retransmission are retransmitted cyclically.
+- ii) If new signal units are available, the retransmission cycle, if any, must be interrupted and the signal units be sent with priority.
+- iii) Under normal conditions, when no message signal units are to be transmitted or cyclically retransmitted, fill-in signal units are sent continuously. In some particular cases link status signal units, continuous fill-in signal units or flags may be sent as described in clauses 7, 8 and 10.
+
+## 6.4 Forced retransmission
+
+To maintain the efficiency of error correction in those cases where automatic error correction by preventive cyclic retransmission alone is made impossible (by, for example, high signalling load), the preventive cyclic retransmission procedures must be complemented by the forced retransmission procedure.
+
+### 6.4.1 Forced retransmission procedure
+
+Both the number of message signal units available for retransmission ( $N_1$ ) and the number of message signal unit octets available for retransmission ( $N_2$ ) are monitored continuously.
+
+If one of them reaches its set limit, no new message signal units or fill-in signal units are sent and the retransmission cycle is continued up to the last message signal unit entered into retransmission buffer with priority, in the order in which they were originally transmitted. If all those message signal units have been sent once and neither $N_1$ nor $N_2$ is at its limit value, the normal preventive cyclic retransmission procedure can be resumed. If not, all the message signal units available for retransmission are sent again with priority.
+
+### 6.4.2 Limitation of the values $N_1$ and $N_2$
+
+$N_1$ is limited by the maximum numbering capacity of the forward sequence number range which dictates that not more than 127 message signal units can be available for retransmission.
+
+In the absence of errors, $N_2$ is limited by the signalling link loop delay $T_L$ . It must be ensured that not more than $T_L/T_{eb} + 1$ message signal unit octets are available for retransmission,
+
+where:
+
+$T_L$ is the signalling link loop delay, i.e. the time between the sending of a message signal unit and the reception of the acknowledgement for this message signal unit in undisturbed operation; and
+
+$T_{eb}$ is the emission time of one octet.
+
+When some signalling data links of different loop delays are alternated for application to that signalling link, the longest possible signalling link delay may be used to calculate the value of $T_L$ .
+
+# 7 Initial alignment procedure
+
+## 7.1 General
+
+The procedure is applicable to activation and to restoration of the link. The procedure provides a "normal" proving period for "normal" initial alignment and an "emergency" proving period for "emergency" initial alignment. The decision to apply either the "normal" or the "emergency" procedures is made unilaterally at level 3 (see Recommendation Q.704). Only the signalling link to be aligned is involved in the initial alignment procedure (i.e. no transfer of alignment information over other signalling links is required).
+
+## 7.2 Initial alignment status indications
+
+The initial alignment procedure employs four different alignment status indications:
+
+- status indication "O": out of alignment;
+- status indication "N": "normal" alignment status;
+- status indication "E": "emergency" alignment status;
+- status indication "OS": out of service.
+
+These indications are carried in the status field of the link status signal units (see 2.2).
+
+Status indication "O" is transmitted when initial alignment has been started and none of the status indications "O", "N" or "E" are received from the link. Status indication "N" is transmitted when, after having started initial alignment, status indication "O", "N" or "E" is received and the terminal is in the "normal" alignment status. Status indication "E" is transmitted when, after having started initial alignment, status indication "O", "N" or "E" is received and the terminal is in the "emergency" alignment status, i.e. it must employ the short "emergency" proving period.
+
+Status indications "N" and "E" indicate the status of the transmitting signalling link terminal; this is not changed by reception of status indications indicating a different status at the remote signalling link terminal. Hence, if a signalling link terminal with a "normal" alignment status receives a status indication "E" it continues to send status indication "N" but initiates the short "emergency" proving period.
+
+Status indication "OS" informs the remote signalling link terminal that for reasons other than processor outage (e.g. link failure) the signalling link terminal can neither receive nor transmit message signal units. Status indication OS is sent on completion of "power on" (see Figures 2 and 8) until initial alignment is started.
+
+## 7.3 Initial alignment procedure
+
+The alignment procedure passes through a number of states during the initial alignment:
+
+- State Idle: The procedure is suspended.
+
+- State "not aligned": The signalling link is not aligned and the terminal is sending status indication "O". Time-out T23 is started on entry to State and stopped when State is left4.
+- State "aligned": The signalling link is aligned and the terminal is sending status indication "N" or "E", status indications "N", "E" or "OS" are not received. Time-out T33 is started on entry to State and stopped when State is left.
+- State 03, "proving": The signalling link terminal is sending status indication "N" or "E", status indication "O" or "OS" are not received, proving has been started.
+
+Proving is the means by which the signalling link terminal validates the link's ability to carry signal units correctly by inspecting the signal units. «Proving» must last for a period of T4 before the link can enter the «aligned ready» link state. Expiry of timer T4 (see 12.3) indicates a successful proving period unless the proving period has been previously aborted up to four times.
+
+- Following successful alignment and proving procedure, the signalling terminal enters Aligned Ready state and the aligned ready time-out T1 is stopped on entry in the In-service state and the duration of time-out T1 should be chosen such that the remote end can perform four additional proving attempts.
+
+The procedure itself is described in the overview diagram, Figure 4, and in state transition diagram, Figure 9.
+
+---
+
+3 Timers defined in this Recommendation are absolute time values. This means that, due to the possibility to insert multiple flags between signal units (see 3.1), there may be no fixed relation between the time-out values and the number of signal units transmitted/received during the time-out periods.
+
+4 If automatic allocation of signalling terminals or signalling data links is applied at both ends of a signalling link, it must be ensured that the values of this time-out are different at each end of a signalling link (see clause 12/Q.704). In this case T2 low (see 12.3) is allocated to the signalling point with the lower point code and T2 high to the signalling point with the higher point code. In all other cases, the value of time-out T2 can be the same at both ends of the link.
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> Start[/Start/]
+ Start --> SendSIO[/Send SIO/]
+ SendSIO --> NotAligned([Not aligned])
+ NotAligned --> Stop1[/Stop/]
+ Stop1 --> Idle2([Idle])
+ NotAligned --> SIO_SIN[/SIO SIN/]
+ SIO_SIN --> Emergency1{Emergency}
+ Emergency1 -- No --> NormalProving[Use normal proving period]
+ NormalProving --> SendSIN1[/Send SIN/]
+ Emergency1 -- Yes --> EmergencyProving1[Use emergency proving period]
+ EmergencyProving1 --> SendSIE1[/Send SIE/]
+ NotAligned --> SIE1[/SIE/]
+ SIE1 --> Emergency2{Emergency}
+ Emergency2 -- No --> EmergencyProving2[Use emergency proving period]
+ EmergencyProving2 --> SendSIN2[/Send SIN/]
+ Emergency2 -- Yes --> EmergencyProving3[Use emergency proving period]
+ EmergencyProving3 --> SendSIE2[/Send SIE/]
+ SendSIN1 --> Aligned1([Aligned])
+ SendSIE1 --> Aligned1
+ SendSIN2 --> Aligned1
+ SendSIE2 --> Aligned1
+ Aligned1 --> SIN[/SIN/]
+ Aligned1 --> SIE2[/SIE/]
+ Aligned1 --> SIOS[/SIOS/]
+ Aligned1 --> Stop2[/Stop/]
+ Aligned1 --> Emergency3[/Emergency/]
+ SIN --> Proving1([Proving])
+ SIE2 --> Proving1
+ SIOS --> AlignmentNotPossible1[/Alignment not possible/]
+ AlignmentNotPossible1 --> Idle3([Idle])
+ Stop2 --> Idle4([Idle])
+ Emergency3 --> EmergencyProving4[Use emergency proving period]
+ EmergencyProving4 --> SendSIE3[/Send SIE/]
+ SendSIE3 --> Aligned2([Aligned])
+ Proving1 --> ProvingPeriodExpires[/Proving period expires/]
+ ProvingPeriodExpires --> AlignmentComplete[/Alignment complete/]
+ AlignmentComplete --> Idle5([Idle])
+ Proving1 --> SIE3[/SIE/]
+ SIE3 --> EmergencyProving5[Use emergency proving period]
+ EmergencyProving5 --> Proving2([Proving])
+ Proving1 --> Emergency4[/Emergency/]
+ Emergency4 --> SendSIE4[/Send SIE/]
+ SendSIE4 --> EmergencyProving6[Use emergency proving period]
+ EmergencyProving6 --> Proving3([Proving])
+ Proving1 --> Stop3[/Stop/]
+ Stop3 --> Idle6([Idle])
+ Proving1 --> SIOS2[/SIOS/]
+ SIOS2 --> AlignmentNotPossible2[/Alignment not possible/]
+ AlignmentNotPossible2 --> Idle7([Idle])
+ Proving1 --> HighLinkErrorRate[/High link error rate/]
+ HighLinkErrorRate --> AlignmentNotPossible3[/Alignment not possible/]
+ AlignmentNotPossible3 --> Idle8([Idle])
+ Proving1 --> SIO[/SIO/]
+ SIO --> Aligned3([Aligned])
+
+```
+
+SIE Status Indication “E”
+ SIN Status Indication “N”
+ SIO Status Indication “O”
+ SIOS Status Indication “out of service”
+
+T1156550-93
+
+Flowchart of initial alignment control. The process starts at 'Idle', goes through 'Start' and 'Send SIO' to 'Not aligned'. From 'Not aligned', it branches into 'Stop' (Idle), 'SIO SIN' (Emergency? No: normal proving period, SIN; Yes: emergency proving period, SIE), and 'SIE' (Emergency? No: emergency proving period, SIN; Yes: emergency proving period, SIE). All lead to 'Aligned'. From 'Aligned', it branches into 'SIN' (Proving), 'SIE' (Proving), 'SIOS' (Alignment not possible: Idle), 'Stop' (Idle), and 'Emergency' (emergency proving period, SIE: Aligned). The 'Proving' state branches into 'Proving period expires' (Alignment complete: Idle), 'SIE' (emergency proving period: Proving), 'Emergency' (Send SIE: emergency proving period: Proving), 'Stop' (Idle), 'SIOS' (Alignment not possible: Idle), 'High link error rate' (Alignment not possible: Idle), and 'SIO' (Aligned). A legend defines SIE, SIN, SIO, and SIOS. Reference T1156550-93 is noted.
+
+**Figure 4/Q.703 – Overview diagram of initial alignment control**
+
+## 7.4 Proving periods
+
+The nominal values of the proving periods are:
+
+$P_n = 2^{16}$ octets transmission time;
+
+$P_e = 2^{12}$ octets transmission time,
+
+for both 64 kbit/s and lower bit rates. For the corresponding timer T4 values (proving periods), see 12.3.
+
+# 8 Processor outage
+
+The procedure for dealing with local and/or remote processor outage is described in Figure 10.
+
+A processor outage situation occurs when, due to factors at a functional level higher than level 2, use of the link is precluded.
+
+In this context, processor outage refers to a situation when signalling messages cannot be transferred to functional levels 3 and/or 4. This may be because of, for example, a central processor failure. A processor outage condition may not necessarily affect all signalling links in a signalling point, nor does it exclude the possibility that level 3 is able to control the operation of the signalling link.
+
+When level 2 identifies a local processor outage condition, it transmits link status signal units indicating processor outage and discards message signal units received. Provided that the level 2 function at the far end of the signalling link is in its normal operating state (i.e. transmitting message signal units or fill-in signal units), upon receiving link status signal units indicating processor outage, it notifies level 3 and begins continuously to transmit fill-in signal units.
+
+When the local processor outage condition ceases, normal transmission of message signal units and fill-in signal units is resumed (provided that no local processor outage condition has arisen also at the remote end). As soon as the level 2 function at the remote end correctly receives a message signal unit or fill-in signal unit, it notifies level 3 and returns to the In service state5. However, in order to avoid problems with the flushing of old messages, it is recommended that level 2 on both sides should wait to resume its normal operation after it is explicitly notified by level 3 that it may do so.
+
+It should be noted that in the case that processor outage is of "long term", i.e. when timer T1 in MTP level 3 (see 16.8/Q.704) has expired, problems exist with old messages, which are those messages stored within level 2 buffers after the switch of new traffic on the alternative link(s) has been performed. This is because, in general, the level 2 buffers on both sides of the link contain some MSUs. If normal operation of the link is resumed, (re)transmission of these messages would result in message missequencing. Furthermore, it is very likely that these messages are related to calls that have already been released or to network management situations that have long since passed.
+
+Because of the above, in order to avoid sending of old messages, the level 2 buffers on both sides should be flushed immediately after the local/remote processor outage state terminates. In addition, the synchronization of the level 2 sequence numbers has to be assured. This is necessary for the correct operation of the link. It is understood that each side is responsible for the flushing and synchronization concerning its own level 2 and that the specific actions concerning the synchronization of the level 2 sequence numbers must not rely on the actions of the other side. How these measures are performed is considered to be implementation dependent.
+
+Format and code of link status signal units indicating processor outage (status indication "PO") appear in clause 11.
+
+---
+
+5 Whether the just received MSU/FISU and a limited number of following ones are discarded or not is an implementation dependent decision.
+
+# **9 Level 2 flow control**
+
+## **9.1 General**
+
+The procedure is used to handle a level 2 congestion situation. After the congestion is detected at the receiving end of the signalling link, both positive and negative acknowledgements to message units are withheld and a status indication "B" (Busy) is sent from the receiving end of the link to the remote end in order to enable the remote transmitting end to distinguish between congestion and failure situations.
+
+This indication is carried in the status field of a link status signal unit.
+
+NOTE – The receiving end continues to process BSN and BIB carried in signal units received in order to avoid, as far as possible, disturbance of the message flow in the opposite direction and in addition may continue to accept message signal units.
+
+## **9.2 Detection of congestion**
+
+The mechanism for detecting congestion at the receiving end of a signalling link is implementation dependent and not to be specified.
+
+## **9.3 Procedure in the congestion situation**
+
+The receiving end of a signalling link which detected a congestion situation, periodically returns a link status signal unit containing a status indication "B" to the remote transmitting end of the link at interval T5 (see 12.3).
+
+The receiving level 2 also withholds acknowledgement of the message signal unit, which triggered off the congestion detection, and of message signal units received during the congestion situation; that is fill-in signal units or message signal units are sent as usual, but with the backward sequence number and backward indicator bit assigned the values which are contained in the last transmitted signal unit before the congestion is recognized.
+
+At the remote end of the signalling link, every reception of a link status signal unit containing indication "B" causes the excessive delay of acknowledgement timer T7 to be restarted, if the timer is already running. In addition first reception of the link status signal unit containing a status indication "B" starts a longer supervision timer T6 (see 12.3) only if there are message signal units in the retransmission buffer. Should timer T6 expire, link failure indication is generated.
+
+## **9.4 Congestion abatement procedure**
+
+When congestion abates at the receiving end of the signalling link, transmission of link status signal unit containing a status indication "B" is stopped and normal operation resumed.
+
+At the remote end, the supervision timer T6 is stopped when a negative or positive acknowledgement whose backward sequence number acknowledges a message signal unit in the retransmission buffer is received in case of the basic error correction method, or a positive acknowledgement in case of the PCR method.
+
+NOTE – Congestion onset and abatement detection is an implementation dependent function. Sufficient hysteresis should be provided in the implementation to prevent excessive oscillation between congested and non-congested states.
+
+# 10 Signalling link error monitoring
+
+## 10.1 General
+
+Two link error rate monitor functions are provided: one which is employed whilst a signalling link is in service and which provides one of the criteria for taking the link out of service, and one which is employed whilst a link is in the proving state of the initial alignment procedure (see 7.3). These are called the signal unit error rate monitor and the alignment error rate monitor respectively.
+
+## 10.2 Signal unit error rate monitor
+
+**10.2.1** The signal unit error rate monitor has as its function the estimation of the signal unit error rate in order to decide about the signalling link fault condition. The signal units in error are those rejected by the acceptance procedure (see clause 4). The three parameters which determine the signal unit error rate monitor are: the number $T$ (signal units), of consecutive signal units received in error that will cause an error rate high indication to level 3, the lowest signal unit error rate $1/D$ (signal unit errors/signal unit) which will ultimately cause an error rate high indication to level 3, and the number $N$ (octets) of octets that causes an increment of the counter while in the "octet counting" mode. See Figure 5.
+
+**10.2.2** The signal unit error rate monitor may be implemented in the form of an up/down counter decremented at a fixed rate (for every $D$ received signal units or signal unit errors indicated by the acceptance procedure), but not below zero, and incremented every time a signal unit error is detected by the signal unit acceptance procedure (see clause 4), but not above the threshold [ $T$ (signal units)]. An excessive error rate will be indicated whenever the threshold $T$ is reached.
+
+**10.2.3** In the "octet counting" mode (see 4.1) the counter is incremented for every $N$ octets received until a correctly-checking signal unit is detected (causing the "octet counting" mode to be left).
+
+**10.2.4** When the link is brought into service the monitor count should start from zero.
+
+**10.2.5** The values of the three parameters are:
+
+| | | | |
+|-----|---|------------------------------------|---------------------|
+| $T$ | = | 64 signal units | For 64 kbit/s |
+| $D$ | = | 256 signal units/signal unit error | For 64 kbit/s |
+| $N$ | = | 16 octets | For 64 kbit/s |
+| $T$ | = | 32 signal units | For lower bit rates |
+| $D$ | = | 256 signal units/signal unit error | For lower bit rates |
+| $N$ | = | 16 octets | For lower bit rates |
+
+In the case of loss of alignment, these figures will give times of approximately 128 ms and 854 ms to initiate changeover for 64 kbit/s and 4.8 kbit/s respectively.
+
+**10.2.6** In the case where only random signal unit errors occur over the signalling link, the relationship between the expected number of signal units until threshold of $T$ (signal units) is reached and the signal unit errors rate (signal unit errors/signal units) can be established. This relationship may be expressed by an orthogonal hyperbola which has parameters ( $T$ , $1/D$ ) (see Figure 5).
+
+
+
+Figure 5/Q.703 – Relationship between the expected number of signal units to fault indication and signal units errors rates. The figure contains two graphs. The left graph is for 64 kbit/s, showing the percentage of signal units in error (y-axis, 0.4 to 100) versus signal units (x-axis, 64 to 11 000) and time to inform level 3. The right graph is for bit rates lower than 64 kbit/s, showing the percentage of signal units in error (y-axis, 0.4 to 100) versus signal units (x-axis, 32 to 5500) and time to inform level 3. Both graphs show a curve that starts at 100% error and decreases towards 0.4% as the number of signal units increases.
+
+T1156560-93
+
+**Figure 5/Q.703 – Relationship between the expected number of signal units to fault indication and signal units errors rates**
+
+## 10.3 Alignment error rate monitor
+
+**10.3.1** The alignment error rate monitor is a linear counter which is operated during normal and emergency proving periods.
+
+**10.3.2** The counter is started from zero whenever the proving state (see Figure 9) of the alignment procedure is entered and is then incremented for every signal unit error detected, if not in the octet counting mode. It is also incremented for every $N$ octets received while in the octet counting mode, as described in 10.2.3.
+
+**10.3.3** When the counter reaches a threshold $T_i$ , that particular proving period is aborted; on receipt of a correct signal unit or the expiry of the aborted proving period the proving state is reentered. If proving is aborted $M$ times, the link is returned to the out-of-service state. A threshold is defined for each of the two types of proving period (normal and emergency, see clause 7). These are $T_{in}$ and $T_{ie}$ and apply to the normal proving period and the emergency proving period respectively.
+
+Proving is successfully completed when a proving period expires without an excessive error rate being detected and without the receipt of status indication "O" or "OS".
+
+**10.3.4** The values of the four parameters for both 64 kbit/s and lower bit rates are:
+
+$$T_{in} = 4$$
+
+$$T_{ie} = 1$$
+
+$$M = 5$$
+
+$$N = 16$$
+
+NOTE – It is noted that the emergency proving period may be successfully completed with some probability with a marginal and degraded bit error rate, i.e. around one error in $10^4$ bits - subsequently, the SUERM will quickly indicate an excessive error rate. However, short term operation on a degraded link may be acceptable (e.g. to send management messages).
+
+# 11 Level 2 codes and priorities
+
+## 11.1 Link status signal unit
+
+**11.1.1** The link status signal unit is identified by a length indicator value equal to 1 or 2. If the length indicator has a value of 1 then the status field consists of one octet; if the length indicator has a value of 2 then the status field consists of two octets.
+
+11.1.2 The format of the one octet status field is shown in Figure 6.
+
+When a terminal, which is able to process only a one-octet status field, receives a link status signal unit with a two-octet status field, the terminal shall ignore the second octet for compatibility reasons but process the first octet as specified.
+
+
+
+| | | | |
+|-------|--------------------|---|---|
+| | C | B | A |
+| Spare | Status indications | | |
+| 5 | 3 | | |
+
+First bit transmitted →
+T1156570-93/d06
+
+Diagram of the one octet status field format. It shows a table with two columns: 'Spare' (5 bits) and 'Status indications' (3 bits labeled C, B, A). An arrow points to the right side of the 'Status indications' section, labeled 'First bit transmitted'. Below the diagram is the text 'T1156570-93/d06'.
+
+Figure 6/Q.703 – Status field format
+
+11.1.3 The use of the link status indications is described in clause 7. They are coded as follows:
+
+| C | B | A | |
+|---|---|---|--------------------------|
+| 0 | 0 | 0 | – Status indication "O" |
+| 0 | 0 | 1 | – Status indication "N" |
+| 0 | 1 | 0 | – Status indication "E" |
+| 0 | 1 | 1 | – Status indication "OS" |
+| 1 | 0 | 0 | – Status indication "PO" |
+| 1 | 0 | 1 | – Status indication "B" |
+
+The spare bits should be ignored at the receiving side.
+
+NOTE – For the use of spare bit D in the national option for a SIF compatibility mechanism, see 7.2.6/Q.701.
+
+## 11.2 Transmission priorities within level 2
+
+11.2.1 Five different items can be transmitted:
+
+- i) new message signal units;
+- ii) message signal units which have not yet been acknowledged;
+- iii) link status signal units;
+- iv) fill-in signal units;
+- v) flags.
+
+In certain failure conditions, it may only be possible to send flags or nothing at all.
+
+11.2.2 For the basic error control method, the priorities are:
+
+- | | | |
+|---------|----|-----------------------------------------------------------------------------------------------------------------------|
+| Highest | 1. | Link status signal units. |
+| | 2. | Message signal units which have not yet been acknowledged and for which a negative acknowledgement has been received. |
+| | 3. | New message signal units. |
+| | 4. | Fill-in signal units. |
+| Lowest | 5. | Flags. |
+
+11.2.3 For the preventive cyclic retransmission method, the priorities are:
+
+- Highest
+1. Link status signal units.
+ 2. Message signal units which have not yet been acknowledged and which are stored in a retransmission buffer and exceed one of the parameters $N_1$ and $N_2$ .
+ 3. New message signal units.
+ 4. Message signal units which have not yet been acknowledged.
+ 5. Fill-in signal units.
+- Lowest
+6. Flags.
+
+NOTE – In the basic error control method, where the repetition of message signal units is employed as a national option, the repeated message signal unit will have a priority immediately below that of link status signal units.
+
+# 12 State transition diagrams, abbreviations and timers
+
+**12.1** This clause contains the description of the signalling link control functions, described in this Recommendation, in the form of state transition diagrams according to the CCITT Specification and Description Language (SDL). The following list summarizes these diagrams:
+
+- Level 2 – Functional block diagram: Figure 7.
+- Link State Control (LSC): Figure 8.
+- Initial Alignment Control (IAC): Figure 9.
+- Processor Outage Control (POC): Figure 10.
+- Delimitation, Alignment and Error Detection (Receiving) (DAEDR): Figure 11.
+- Delimitation, Alignment and Error Detection (Transmitting) (DAEDT): Figure 12.
+- Basic Transmission Control (TC): Figure 13.
+- Basic Reception Control (RC): Figure 14.
+- Preventive Cyclic Retransmission – Transmission Control (PCR-TC): Figure 15.
+- Preventive Cyclic Retransmission – Reception Control (PCR-RC): Figure 16.
+- Alignment Error Rate Monitor (AERM): Figure 17.
+- Signal Unit Error Rate Monitor (SUERM): Figure 18.
+- Congestion Control part (CC): Figure 19.
+
+The detailed functional breakdown shown in the following diagrams is intended to illustrate a reference model and to assist interpretation of the text in the earlier clauses. The state transition diagrams are intended to show precisely the behaviour of the signalling system under normal and abnormal conditions as viewed from a remote location. It must be emphasized that the functional partitioning shown in the following diagrams is used only to facilitate understanding of the system behaviour and is not intended to specify the functional partitioning to be adopted in a practical implementation of the signalling system.
+
+In Figures 7 to 19, the term *signal unit* refers to units which do not contain all error control information.
+
+## 12.2 Abbreviations
+
+For the purposes of this Recommendation, the following abbreviations apply:
+
+| | |
+|------|------------------------------|
+| AERM | Alignment Error Rate Monitor |
+| BIB | Backward Indicator Bit |
+
+| | |
+|-------|-------------------------------------------------------------------------------------------------------------------|
+| BIBR | BIB received |
+| BIBT | BIB to be transmitted |
+| BIBX | BIB expected |
+| BSN | Backward Sequence Number |
+| BSNR | BSN received |
+| BSNT | BSN to be transmitted |
+| $C_p$ | Count of aborted proving attempts [Figure 9 (sheets 2 of 6 and 3 of 6)] |
+| $C_m$ | Counter of MSU in TB [Figure 13 (sheet 1 of 7) and Figure 15 (sheet 1 of 7)] |
+| $C_a$ | AERM count (Figure 17) |
+| $C_s$ | SUERM count (Figure 18) |
+| CC | Congestion Control |
+| DAEDR | Delimitation, Alignment and Error Detection (Receiving) |
+| DAEDT | Delimitation, Alignment and Error Detection (Transmitting) |
+| FIB | Forward Indicator Bit |
+| FIBR | FIB received |
+| FIBT | FIB transmitted |
+| FIBX | FIB expected |
+| FISU | Fill-In Signal Unit |
+| FSN | Forward Sequence Number |
+| FSNC | Forward sequence number of last message signal unit accepted by remote level 2 |
+| FSNF | FSN of the oldest MSU in the RTB |
+| FSNL | FSN of the last MSU in the RTB |
+| FSNR | FSN received |
+| FSNT | FSN of the last MSU transmitted |
+| FSNX | FSN expected |
+| IAC | Initial Alignment Control |
+| L2 | Level 2 |
+| L3 | Level 3 |
+| LSC | Link State Control |
+| LSSU | Link Status Signal Unit |
+| MGMT | Management system – Unspecified implementation dependent management function |
+| MSU | Message Signal Unit |
+| NSU | Correct SU count |
+| NACK | Negative acknowledgement |
+| $N_1$ | Maximum number of MSU which are available for retransmission (fixed by the numbering capacity of the FSN) |
+| $N_2$ | Maximum number of MSU octets which are available for retransmission (fixed by the common channel loop delay time) |
+| POC | Processor Outage Control |
+| RC | Reception Control |
+
+| | |
+|----------|-----------------------------------------------|
+| RTB | Retransmission buffer |
+| RTR | If = 1 means retransmission expected |
+| SIB | Status Indication "B" ("Busy") |
+| SIE | Status Indication "E" ("emergency alignment") |
+| SIN | Status Indication "N" ("normal alignment") |
+| SIO | Status Indication "O" ("out of alignment") |
+| SIOS | Status Indication "OS" ("out of service") |
+| SIPO | Status Indication "PO" ("processor outage") |
+| SU | Signal Unit |
+| SUEM | Signal Unit Error Rate Monitor |
+| TB | Transmission Buffer |
+| $T_i$ | AERM threshold |
+| $T_{ie}$ | Emergency AERM threshold |
+| $T_{in}$ | Normal AERM threshold |
+| TXC | Transmission control |
+| UNB | Counter of unreasonable BSN |
+| UNF | Counter of unreasonable FIB |
+
+## 12.3 Timers
+
+| | |
+|-----------------------|---------------------------------------------------------------------|
+| T1 | Timer "alignment ready" |
+| T1 (64) = 40-50 s | Bit rate of 64 kbit/s |
+| T1 (4.8) = 500-600 s | Bit rate of 4.8 kbit/s |
+| T2 = 5-150 s | Timer "not aligned" |
+| T2 low = 5-50 s | Only for automatic allocation of |
+| T2 high = 70-150 s | signalling data links and terminals |
+| T3 = 1-2 s | Timer "aligned" |
+| T4 | Proving period timer = $2^{16}$ or $2^{12}$ octet transmission time |
+| T4n (64) = 7.5-9.5 s | Normal proving period at 64 kbit/s |
+| Nominal value 8.2 s | (corresponding to $P_n = 2^{16}$ ) |
+| T4n (4.8) = 100-120 s | Nominal proving period at 4.8 kbit/s |
+| Nominal value 110 s | (corresponding to $P_n = 2^{16}$ ) |
+| T4e (64) = 400-600 ms | Emergency proving period at 64 kbit/s |
+| Nominal value 500 ms | (corresponding to $P_e = 2^{12}$ ) |
+| T4e (4.8) = 6-8 s | Emergency proving period at 4.8 kbit/s |
+| Nominal value 7 s | (corresponding to $P_e = 2^{12}$ ) |
+| T5 = 80-120 ms | Timer "sending SIB" |
+| T6 | Timer "remote congestion" |
+
+| | |
+|-------------------|--------------------------------------------|
+| T6 (64) = 3-6 s | Bit rate of 64 kbit/s |
+| T6 (4.8) = 8-12 s | Bit rate of 4.8 kbit/s |
+| T7 | Timer "excessive delay of acknowledgement" |
+| T7 (64) = 0.5-2 s | Bit rate of 64 kbit/s |
+| For PCR method, | Values less than 0.8 s should not be used |
+| T7 (4.8) = 4-6 s | Bit rate of 4.8 kbit/s |
+| $P_e$ | Emergency proving period |
+| $P_n$ | Normal proving period |
+
+
+
+Functional block diagram for Level 2 of Recommendation Q.703. The diagram shows the interaction between Level 1 (top) and Level 3 (bottom) through various functional blocks. Key components include: Transmission control (receiving bits from Level 1 and messages from Level 3, sending bits to Level 1 and messages to Level 3); Reception control (receiving bits from Level 1 and messages from Level 3, sending bits to Level 1 and messages to Level 3); Signal unit error rate monitor (receiving signals from Transmission and Reception controls, sending AERM messages); Initial alignment control (receiving signals from Transmission and Reception controls, sending SIO/SIOS messages); Link state control (receiving signals from Transmission and Reception controls, sending SUERM messages); Processor outage control (receiving signals from Link state control, sending signals to Level 3); Congestion control (receiving signals from Reception control, sending signals to Level 3); AERM (receiving signals from Signal unit error rate monitor and Initial alignment control, sending signals to Level 3); DAEDR (receiving signals from Transmission and Reception controls, sending signals to Level 3); IAC (receiving signals from Congestion control, sending signals to Level 3); TXC (receiving signals from DAEDR, sending signals to Level 3); and Received message BSNT (receiving signals from TXC, sending signals to Level 3). The diagram also includes various state transitions and error handling mechanisms.
+
+a) Only for the national option of latching of processor outage.
+
+## **NOTES**
+
+1 – Abbreviated message names have been used in this diagram (i.e. origin – destination codes are omitted).
+
+2 – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 7/Q.703 – Level 2 – Functional block diagram**
+
+
+
+A vertical flowchart illustrating the link state control process. The sequence of steps is as follows:
+
+- Power off** (represented by an oval shape)
+- Power on** (represented by a chevron shape pointing right)
+- MGMT → LSC** (represented by a rectangle)
+- Start** (represented by a chevron shape pointing right)
+- LSC → TXC** (represented by a rectangle)
+- Send SIOS** (represented by a chevron shape pointing right)
+- LSC → TXC** (represented by a rectangle)
+- Set $T_i$ to $T_{in}$** (represented by a chevron shape pointing right)
+- LSC → AERM** (represented by a rectangle)
+- Cancel local processor outage** (represented by a rectangle)
+- Cancel emergency** (represented by a rectangle)
+- Out of service** (represented by an oval shape)
+
+The flowchart is connected by vertical lines, with a downward-pointing arrow between the 'Cancel emergency' and 'Out of service' steps. To the left of the flowchart, there are two parallel vertical lines.
+
+Flowchart of Link state control process
+
+T1156590-93
+
+NOTE – The Notes are found after the last sheet (sheet 14 of 14) of this Figure.
+
+**Figure 8/Q.703 (sheet 1 of 14) – Link state control**
+
+
+
+```
+
+graph TD
+ OutOfService([Out of service]) --> Start1{{Start
+L3 → LSC}}
+ OutOfService --> Retrieve1{{Retrieve BSNT
+L3 → LSC}}
+ OutOfService --> Retrieval1{{Retrieval request
+and FSNC
+L3 → LSC}}
+ Start1 --> Start2{{Start
+LSC → RC}}
+ Retrieve1 --> Retrieve2{{Retrieve BSNT
+LSC → RC}}
+ Retrieval1 --> Retrieval2{{Retrieval request
+and FSCN
+LSC → TXC}}
+ Start2 --> Start3{{Start
+LSC → TXC}}
+ Retrieve2 --> Connector2((2))
+ Retrieval2 --> Connector2
+ Start3 --> Emergency{Emergency}
+ Emergency -- No --> Start4{{Start
+LSC → IAC}}
+ Emergency -- Yes --> Emergency2{{Emergency
+LSC → IAC}}
+ Emergency2 --> Start4
+ Start4 --> InitialAlignment([Initial alignment])
+ Connector1((1))
+ Connector2
+ Connector3((3))
+ Start1 -.-> Connector1
+ Retrieve2 -.-> Connector2
+ Retrieval2 -.-> Connector2
+ Connector1 -.-> Connector3
+ Connector2 -.-> Connector3
+
+```
+
+Flowchart for Link state control (Figure 8/Q.703 sheet 2 of 14). The diagram shows three main paths starting from 'Out of service'. Path 1: 'Start L3 → LSC' leads to 'Start LSC → RC' and then to connector '1'. Path 2: 'Retrieve BSNT L3 → LSC' leads to 'Retrieve BSNT LSC → RC' and then to connector '2'. Path 3: 'Retrieval request and FSNC L3 → LSC' leads to 'Retrieval request and FSCN LSC → TXC' and then to connector '2'. From connector '2', the flow goes to 'Start LSC → TXC', then to an 'Emergency' decision diamond. If 'No', it goes to 'Start LSC → IAC'. If 'Yes', it goes to 'Emergency LSC → IAC', which then leads to 'Start LSC → IAC'. All 'Start LSC → IAC' paths lead to 'Initial alignment'. Connector '3' is also shown next to connectors '1' and '2'.
+
+T1156600-93
+
+**Figure 8/Q.703 (sheet 2 of 14) – Link state control**
+
+
+
+```
+
+graph TD
+ 1((1)) --> E1{Emergency
+L3 -> LSC}
+ 1 --> EC1{Emergency ceases
+L3 -> LSC}
+ 1 --> LP1{Local processor outage
+MGMT -> LSC
+(Note 2)}
+ 1 --> LF1{Level 3 failure
+MGMT -> LSC}
+ 1 --> LR1{Local processor recovered
+L3 -> LSC
+(Note 2)}
+ E1 --> ME[Mark emergency]
+ EC1 --> CE[Cancel emergency]
+ LP1 --> MLO[Mark local processor outage]
+ LF1 --> MLO
+ LR1 --> CLO[Cancel local processor outage]
+ ME --> 2((2))
+ CE --> 2
+ MLO --> 2
+ CLO --> 2
+ 2 --> OS([Out of service])
+ T1156610-93
+
+```
+
+Flowchart for Link state control (sheet 3 of 14). It starts at connector 1, showing four parallel paths: Emergency (L3 -> LSC) leading to 'Mark emergency'; Emergency ceases (L3 -> LSC) leading to 'Cancel emergency'; Local processor outage (MGMT -> LSC (Note 2)) leading to 'Mark local processor outage'; and Local processor recovered (L3 -> LSC (Note 2)) leading to 'Cancel local processor outage'. A 'Level 3 failure' (MGMT -> LSC) path also exists. All four main paths converge at connector 2, leading to an 'Out of service' state. Reference T1156610-93.
+
+Figure 8/Q.703 (sheet 3 of 14) – Link state control
+
+
+
+```
+
+graph TD
+ IA1([Initial alignment]) --> LP1{Local processor outage
+MGMT -> LSC
+(Note 2)}
+ IA1 --> LF1{Level 3 failure
+MGMT -> LSC}
+ IA1 --> LP2{Local processor recovered
+MGMT -> LSC
+(Note 2)}
+ IA1 --> E1{Emergency
+L3 -> LSC}
+ LP1 --> MLO1[Mark local processor outage]
+ LF1 --> MLO1
+ LP2 --> CLO[Cancel local processor outage]
+ E1 --> ME[Mark emergency]
+ ME --> E2{Emergency
+LSC -> IAC}
+ MLO1 --> IA2([Initial alignment])
+ CLO --> IA2
+ E2 --> IA2
+ T1156620-93
+
+```
+
+Flowchart for Link state control (sheet 4 of 14). It starts at 'Initial alignment', showing four parallel paths: Local processor outage (MGMT -> LSC (Note 2)) leading to 'Mark local processor outage'; Level 3 failure (MGMT -> LSC) leading to 'Mark local processor outage'; Local processor recovered (MGMT -> LSC (Note 2)) leading to 'Cancel local processor outage'; and Emergency (L3 -> LSC) leading to 'Mark emergency'. The 'Mark emergency' path leads to another 'Emergency' block (LSC -> IAC). All paths converge at 'Initial alignment' at the bottom. Reference T1156620-93.
+
+Figure 8/Q.703 (sheet 4 of 14) – Link state control
+
+
+
+```
+
+graph TD
+ Start((3)) --> A1[Alignment complete
+IAC → LSC]
+ Start --> A2[Stop
+L3 → LSC]
+ Start --> A3[Link failure
+RC → LSC]
+ Start --> A4[Alignment not possible
+IAC → LSC]
+
+ A1 --> S1[Start
+LSC → SUERM]
+ S1 --> T1[Start T1]
+ T1 --> D1{Local processor outage}
+ D1 -- Yes --> POC[Local processor outage
+LSC → POC]
+ D1 -- No --> FISU[Send FISU
+LSC → TXC]
+ FISU --> MSU[Accept MSU/FISU
+LSC → RC]
+ MSU --> Ready1([Aligned/ready])
+
+ POC --> SIPO[Send SIPO
+LSC → TXC]
+ SIPO --> Reject[Reject MSU/FISU
+LSC → RC]
+ Reject --> NotReady1([Aligned/not ready])
+
+ A2 --> Stop2[Stop
+LSC → IAC]
+ Stop2 --> Stop3[Stop
+LSC → RC]
+ Stop3 --> SIOS[Send SIOS
+LSC → TXC]
+ SIOS --> CancelOutage[Cancel local processor outage]
+ CancelOutage --> CancelEmergency[Cancel emergency]
+ CancelEmergency --> OutOfService1([Out of service])
+
+ A3 --> OutOfService2[Out of service
+LSC → L3]
+ OutOfService2 --> Stop2
+
+ A4 --> OutOfService3[Out of service
+LSC → L3]
+ OutOfService3 --> Stop2
+
+```
+
+The flowchart illustrates the link state control process. It begins at a start node (3) and branches into four initial conditions: 'Alignment complete' (IAC → LSC), 'Stop' (L3 → LSC), 'Link failure' (RC → LSC), and 'Alignment not possible' (IAC → LSC). The 'Alignment complete' path leads to 'Start' (LSC → SUERM), then 'Start T1', and then a decision 'Local processor outage'. If 'Yes', it leads to 'Local processor outage' (LSC → POC), then 'Send SIPO' (LSC → TXC), then 'Reject MSU/FISU' (LSC → RC), and finally 'Aligned/not ready'. If 'No', it leads to 'Send FISU' (LSC → TXC), then 'Accept MSU/FISU' (LSC → RC), and finally 'Aligned/ready'. The 'Link failure' path leads to 'Out of service' (LSC → L3), then 'Stop' (LSC → IAC), then 'Stop' (LSC → RC), then 'Send SIOS' (LSC → TXC), then 'Cancel local processor outage', then 'Cancel emergency', and finally 'Out of service'. The 'Alignment not possible' path leads to 'Out of service' (LSC → L3), which then leads to 'Stop' (LSC → IAC).
+
+Flowchart for Link state control (Figure 8/Q.703 sheet 5 of 14).
+
+T1177570-95
+
+Figure 8/Q.703 (sheet 5 of 14) – Link state control
+
+
+
+```
+
+graph TD
+ Start([Aligned ready]) --> HLine[ ]
+ HLine --> LF1[/Link failure
+SUERM → LSC/]
+ HLine --> LF2[/Link failure
+RC → LSC/]
+ HLine --> SIOS[/SIO, SIOS
+RC → LSC/]
+ HLine --> StopL3[/Stop
+L3 → LSC/]
+
+ LF1 --> StopT1_1[/Stop T1/]
+ StopT1_1 --> OutService1[/Out of service
+LSC → L3/]
+ OutService1 --> StopLSCRC[/Stop
+LSC → RC/]
+ StopLSCRC --> StopLSCSUERM[/Stop
+LSC → SUERM/]
+ StopLSCSUERM --> SendSIOS[/Send SIOS
+LSC → TXC/]
+ SendSIOS --> CancelEmergency[Cancel emergency]
+ CancelEmergency --> OutServiceEnd([Out of service])
+
+ LF2 --> J2[ ]
+ SIOS --> J2
+ StopL3 --> StopT1_2[/Stop T1/]
+
+ J2 --> T1_Box{{T1}}
+ StopT1_2 --> T1_Box
+ T1_Box --> OutService2[/Out of service
+LSC → L3/]
+ OutService2 --> HLine
+
+ Connector((4)) --> HLine
+ Label7[7] --> Connector
+
+```
+
+T1177580-95
+
+Flowchart for Link state control. It starts with 'Aligned ready' (oval) leading to a horizontal line. From this line, four paths branch out: 1) 'Link failure SUERM → LSC' (parallelogram) leading to 'Stop T1' (parallelogram), then 'Out of service LSC → L3' (parallelogram), then 'Stop LSC → RC' (parallelogram), then 'Stop LSC → SUERM' (parallelogram), then 'Send SIOS LSC → TXC' (parallelogram), then 'Cancel emergency' (rectangle), and finally 'Out of service' (oval). 2) 'Link failure RC → LSC' (parallelogram) leading down to a junction. 3) 'SIO, SIOS RC → LSC' (parallelogram) leading down to the same junction. 4) 'Stop L3 → LSC' (parallelogram) leading to 'Stop T1' (parallelogram), then to a junction. A junction point on the right side receives inputs from the 'Link failure RC → LSC', 'SIO, SIOS RC → LSC', and 'Stop T1' (right) paths. From this junction, one path leads down to 'Out of service LSC → L3' (parallelogram), and another path leads up and left to a junction point on the top horizontal line. A circle with the number '4' is on the left, with a line labeled '7' pointing to it from the top. The text 'T1177580-95' is at the bottom right of the diagram.
+
+**Figure 8/Q.703 (sheet 6 of 14) – Link state control**
+
+
+
+```
+
+graph TD
+ subgraph Inputs
+ SIPO[SIPO
+RC → LSC]
+ FISU[FISU/MSU received
+RC → LSC]
+ LPO[Local processor outage
+MGMT → LSC
+(Note 2)]
+ L3F[Level 3 failure
+MGMT → LSC]
+ end
+
+ SIPO --> StopT1_1{{Stop T1}}
+ StopT1_1 --> RPO_1[Remote processor outage
+LSC → L3]
+ RPO_1 --> RPO_2[Remote processor outage
+LSC → POC]
+ RPO_2 --> PO([Processor outage])
+
+ FISU --> IS_1[In service
+LSC → L3]
+ IS_1 --> StopT1_2{{Stop T1}}
+ StopT1_2 --> SM[Send MSU
+LSC → TXC]
+ SM --> IS_2([In service])
+
+ LPO --> LPO_3[Local processor outage
+LSC → POC]
+ LPO_3 --> SS[Send SIPO
+LSC → TXC]
+ SS --> RM[Reject MSU/FISU
+LSC → RC]
+ RM --> ANR([Aligned/not ready])
+
+ L3F --> LPO_3
+ L3F --> LPO
+ L3F --> C((4))
+
+```
+
+T1177590-95
+
+Flowchart for Link state control (Figure 8/Q.703 sheet 7 of 14). The diagram shows four main columns of logic starting from different input conditions: SIPO, FISU/MSU received, Local processor outage, and Level 3 failure. Each column leads through a series of processing steps to a final state: Processor outage, In service, or Aligned/not ready. A connector '4' is shown at the top right.
+
+**Figure 8/Q.703 (sheet 7 of 14) – Link state control**
+
+
+
+5
+
+```
+
+graph TD
+ Start([Aligned/not ready]) --> P1[Link failure SUERM → LSC]
+ Start --> P2[Link failure RC → LSC]
+ Start --> P3[SIO, SIOS RC → LSC]
+ Start --> P4[Stop L3 → LSC]
+ P1 --> StopT1_1[Stop T1]
+ P2 --> StopT1_1
+ P3 --> StopT1_1
+ P4 --> StopT1_2[Stop T1]
+ StopT1_1 --> OutOfService1[Out of service LSC → L3]
+ StopT1_2 --> T1[ $\overline{T1}$ ]
+ T1 --> OutOfService2[Out of service LSC → L3]
+ OutOfService1 --> StopL3_1[Stop LSC → L3]
+ OutOfService2 --> StopL3_1
+ StopL3_1 --> StopSUERM[Stop LSC → SUERM]
+ StopSUERM --> SendSIOS[Send SIOS LSC → TXC]
+ SendSIOS --> StopPOC[Stop LSC → POC]
+ StopPOC --> CancelOutage[Cancel emergency and local processor outage]
+ CancelOutage --> End([Out of service])
+
+```
+
+T1156660-93
+
+Flowchart for Link state control. It starts with 'Aligned/not ready' leading to four parallel paths: 'Link failure SUERM → LSC', 'Link failure RC → LSC', 'SIO, SIOS RC → LSC', and 'Stop L3 → LSC'. The first three paths lead to 'Stop T1' then 'Out of service LSC → L3'. The 'Stop L3 → LSC' path leads to 'Stop T1' then to a timer 'T1' (labeled with a bar over T1). From 'T1', it goes to 'Out of service LSC → L3'. All 'Out of service LSC → L3' paths converge to a 'Stop LSC → L3' block. From there, the flow goes through 'Stop LSC → SUERM', 'Send SIOS LSC → TXC', 'Stop LSC → POC', and 'Cancel emergency and local processor outage' to a final 'Out of service' state. A connector '5' is at the top left, and a label 'T1156660-93' is near the bottom right.
+
+**Figure 8/Q.703 (sheet 8 of 14) – Link state control**
+
+
+
+```
+
+graph TD
+ Start((5)) --> SIPO
+ SIPO --> SIPO_LSC[RC → LSC]
+ SIPO_LSC --> SIPO_Outage[Remote processor outage
+LSC → L3]
+ SIPO_Outage --> SIPO_Outage_POC[Remote processor outage
+LSC → POC]
+ SIPO_Outage_POC --> SIPO_StopT1[Stop T1]
+ SIPO_StopT1 --> ProcessorOutage([Processor outage])
+ FISU[FISU/MSU received] --> FISU_LSC[RC → LSC]
+ FISU_LSC --> FISU_InService[In service
+LSC → L3]
+ FISU_InService --> FISU_StopT1[Stop T1]
+ FISU_StopT1 --> ProcessorOutage
+ LocalProc[Local processor recovered
+MGMT → LSC
+(Note 2)] --> LocalProc_Recovered[Local processor recovered
+LSC → POC]
+ LocalProc_Recovered --> LocalProc_Outage[Cancel local processor outage]
+ LocalProc_Outage --> LocalProc_FISU[Send FISU
+LSC → TXC]
+ LocalProc_FISU --> LocalProc_Accept[Accept MSU/FISU
+LSC → RC]
+ LocalProc_Accept --> AlignedReady([Aligned/ready])
+
+```
+
+T1177600-95
+
+Flowchart for Link state control showing three main paths: Local processor recovered, FISU/MSU received, and SIPO. It includes steps for MGMT to LSC, RC to LSC, LSC to POC, LSC to L3, Stop T1, Send FISU, LSC to TXC, Accept MSU/FISU, LSC to RC, and Processor outage.
+
+Figure 8/Q.703 (sheet 9 of 14) – Link state control
+
+
+
+```
+
+graph TD
+ InService([In service]) --> Branch[ ]
+ Branch --> LF1[Link failure
+RC → LSC]
+ Branch --> LF2[Link failure
+TXC → LSC]
+ Branch --> LF3[Link failure
+SUERM → LSC]
+ Branch --> SIO[SIO, SIN,
+SIE, SIOS
+RC → LSC]
+
+ LF1 --> OOS_L3[Out of service
+LSC → L3]
+ LF2 --> OOS_L3
+ LF3 --> OOS_L3
+ SIO --> StopLSC[Stop
+L3 → LSC]
+
+ StopLSC --> OOS_L3
+ OOS_L3 --> StopSUERM[Stop
+LSC → SUERM]
+ StopSUERM --> StopRC[Stop
+LSC → RC]
+ StopRC --> SendSIOS[Send SIOS
+LSC → TXC]
+ SendSIOS --> CancelEmergency[Cancel
+emergency]
+ CancelEmergency --> OutOfService([Out of service])
+
+ T1156680-93[T1156680-93]
+
+ style Branch fill:none,stroke:none
+ style LF1 fill:none,stroke:none
+ style LF2 fill:none,stroke:none
+ style LF3 fill:none,stroke:none
+ style SIO fill:none,stroke:none
+ style OOS_L3 fill:none,stroke:none
+ style StopLSC fill:none,stroke:none
+ style StopSUERM fill:none,stroke:none
+ style StopRC fill:none,stroke:none
+ style SendSIOS fill:none,stroke:none
+ style CancelEmergency fill:none,stroke:none
+ style T1156680-93 fill:none,stroke:none
+
+```
+
+Flowchart for Link state control starting from 'In service' state. It branches into four paths based on inputs: Link failure (RC → LSC), Link failure (TXC → LSC), Link failure (SUERM → LSC), and SIO/SIN/SIE/SIOS (RC → LSC). These paths converge into a sequence of actions: Out of service (LSC → L3), Stop (LSC → SUERM), Stop (LSC → RC), Send SIOS (LSC → TXC), and Cancel emergency, finally reaching the 'Out of service' state.
+
+**Figure 8/Q.703 (sheet 10 of 14) – Link state control**
+
+
+
+```
+graph TD; subgraph Inputs; direction TB; I1[/Local processor outage
MGMT -> LSC (Note 2)/]; I2[/Level 3 failure
MGMT -> LSC/]; I3[/SIPO
RC -> LSC/]; end; I1 --> L1{Local processor outage
LSC -> POC}; I2 --> L1; I3 --> R1{Send FISU
LSC -> TXC}; L1 --> L2{Send SIPO
LSC -> TXC}; L2 --> L3{Reject MSU/FISU
LSC -> RC}; R1 --> R2{Remote processor outage
LSC -> L3}; R2 --> R3{Remote processor outage
LSC -> POC}; L3 --> M[Mark processor outage]; R3 --> M; M --> P([Processor outage]);
+```
+
+Flowchart for Link state control. It starts with three parallel inputs: 'Local processor outage (MGMT -> LSC (Note 2))', 'Level 3 failure (MGMT -> LSC)', and 'SIPO (RC -> LSC)'. The first two lead to 'Local processor outage (LSC -> POC)', which then leads to 'Send SIPO (LSC -> TXC)', which leads to 'Reject MSU/FISU (LSC -> RC)'. The third input leads to 'Send FISU (LSC -> TXC)', which leads to 'Remote processor outage (LSC -> L3)', which leads to another 'Remote processor outage (LSC -> POC)'. Both 'Reject MSU/FISU' and the second 'Remote processor outage' lead to 'Mark processor outage', which finally leads to 'Processor outage'. A connector circle with '6' and '10' is at the top right.
+
+T1142110-92
+
+Figure 8/Q.703 (sheet 11 of 14) – Link state control
+
+7
+
+
+
+Flowchart for Link state control (Figure 8/Q.702 sheet 12 of 14). The process starts with a 'Processor outage' (oval) leading to a horizontal line. From this line, six chevron-shaped boxes represent different input events: 'Retrieval request and FSNC (L3 -> LSC)', 'FISU/MSU received (RC -> LSC)', 'Retrieve BSNT (L3 -> LSC)', 'Level 3 failure (MGMT -> LSC)', 'Local processor outage (MGMT -> LSC (Note 2))', and 'SIPO (RC -> LSC)'. Each chevron leads to a corresponding parallelogram-shaped box representing the system's response: 'Retrieval request and FSNC (LSC -> TXC)', 'Remote processor recovered (LSC -> POC)', 'Retrieve BSNT (LSC -> RC)', 'Local processor outage (LSC -> POC)', 'Send SIPO (LSC -> TXC)', and 'Remote processor outage (LSC -> L3)'. The 'Local processor outage' path continues from its parallelogram to another parallelogram 'Remote processor outage (LSC -> POC)'. All parallelograms lead to a common horizontal line at the bottom, which converges to a final 'Processor outage' (oval). A connector circle with the number '7' is on the top right line, with the number '13' next to it. The text 'T1142120-92' is at the bottom right.
+
+Figure 8/Q.702 (sheet 12 of 14) – Link state control
+
+
+
+```
+
+graph TD
+ 7((7)) --> L1[Local processor recovered
+MGMT -> LSC]
+ 7 --> L2[Flush buffers
+L3 -> LSC]
+ 7 --> L3[Continue
+L3 -> LSC]
+ 7 --> L4[No processor outage
+POC -> LSC]
+ 9((9))
+ 14[14]
+ L1 --> L1b[Local processor recovered
+LSC -> POC]
+ L1b --> L1c[Retrieve FSNX
+LSC -> RC]
+ L1c --> L1d[Send FISU
+LSC -> TXC]
+ L1d --> L1e([Processor outage])
+ L2 --> L2b[Flush buffers
+LSC -> TXC]
+ L2b --> L2c[Mark Level 3 indication received]
+ L3 --> L2c
+ L4 --> L4b[Cancel processor outage]
+ L1d --> D1{Processor outage?}
+ L2c --> D1
+ D1 -- Yes --> D1e([Processor outage])
+ D1 -- No --> D2{Level 3 indication received?}
+ L4b --> D2
+ D2 -- Yes --> D2e([Processor outage])
+ D2 -- No --> D2b[Cancel Level 3 indication received]
+ D2b --> D2c[Send MSU/FISU
+LSC -> TXC]
+ D2c --> D2d[Cancel local processor outage]
+ D2d --> D2e[Accept MSU/FISU
+LSC -> RC]
+ D2e --> D2f([In service])
+ L1d -.-> Note3[Note 3]
+
+```
+
+Flowchart for Link state control (Figure 8/Q.703 sheet 13 of 14). The process starts at connector 7 and ends at connector 9. It branches into four main paths: 'Local processor recovered', 'Flush buffers', 'Continue', and 'No processor outage'. The 'Local processor recovered' path leads to 'Local processor recovered (LSC -> POC)', 'Retrieve FSNX (LSC -> RC)', 'Send FISU (LSC -> TXC)', and finally 'Processor outage'. The 'Flush buffers' path leads to 'Flush buffers (LSC -> TXC)', 'Mark Level 3 indication received', and then a decision diamond 'Processor outage?'. The 'Continue' path leads directly to the 'Processor outage?' decision. The 'No processor outage' path leads to 'No processor outage (POC -> LSC)', 'Cancel processor outage', and then a decision diamond 'Level 3 indication received?'. Both decision diamonds lead to 'Processor outage' on the 'Yes' path or to 'Cancel Level 3 indication received' on the 'No' path. The 'Cancel Level 3 indication received' path continues with 'Send MSU/FISU (LSC -> TXC)', 'Cancel local processor outage', 'Accept MSU/FISU (LSC -> RC)', and finally 'In service'. A note indicates that the 'Send FISU' step is referenced in Note 3.
+
+Figure 8/Q.703 (sheet 13 of 14) – Link state control
+
+
+
+13
+
+9
+
+```
+
+graph TD
+ 9((9)) --> P1[Link failure
+SUERM → LSC]
+ 9 --> P2[Link failure
+RC → LSC]
+ 9 --> P3[SIO, SIN,
+SIE, SIOS
+RC → LSC]
+ 9 --> P4[Stop
+L3 → LSC]
+ P1 --> C1[Out of service
+LSC → L3]
+ P2 --> C1
+ P3 --> C1
+ P4 --> C1
+ C1 --> C2[Stop
+LSC → SUERM]
+ C2 --> C3[Stop
+LSC → RC]
+ C3 --> C4[Stop
+LSC → POC]
+ C4 --> C5[Send SIOS
+LSC → TXC]
+ C5 --> C6[Cancel emergency and
+local processor outage]
+ C6 --> C7([Out of service])
+
+```
+
+T1156690-93
+
+Flowchart for Link state control. It starts with a circle labeled '9'. Four parallel paths lead to a central vertical sequence. The paths are: 1) 'Link failure' (SUERM → LSC), 2) 'Link failure' (RC → LSC), 3) 'SIO, SIN, SIE, SIOS' (RC → LSC), and 4) 'Stop' (L3 → LSC). All four paths converge to a central vertical sequence of blocks: 'Out of service' (LSC → L3), 'Stop' (LSC → SUERM), 'Stop' (LSC → RC), 'Stop' (LSC → POC), 'Send SIOS' (LSC → TXC), 'Cancel emergency and local processor outage', and finally 'Out of service' (oval).
+
+###### NOTES
+
+- 1 – See the abbreviations and timers used in this Figure in 12.2.
+- 2 – For the national option of latching of processor outage, the input "Local processor outage" can also come from "L3".
+- 3 – For a correct synchronization of the sequence numbers at the remote side, the BSN within the FISU must be BSN:=FSNX-1.
+- 4 – Alternatively, the flushing of buffers and synchronization of sequence numbers may be replaced by taking the signalling link out of service. In addition, this would cater for *Blue Book* level 3 and the present version level 2 interworking.
+
+**Figure 8/Q.703 (sheet 14 of 14) – Link state control**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> Emergency{Emergency
+LSC → IAC}
+ Idle1 --> Start{Start
+LSC → IAC}
+ Emergency --> Mark[Mark
+emergency]
+ Mark --> Idle2([Idle])
+ Start --> SIO{Send SIO
+IAC → TXC}
+ SIO --> T2_start{Start T2}
+ T2_start --> NotAligned([Not aligned])
+ NotAligned --> Stop{Stop
+LSC → IAC}
+ NotAligned --> T2_bar{T2}
+ Stop --> T2_stop{Stop T2}
+ T2_bar --> NotPossible{Alignment
+not possible
+IAC → LSC}
+ T2_stop --> Cancel[Cancel
+emergency]
+ NotPossible --> Cancel
+ Cancel --> Idle3([Idle])
+ NotAligned --> Connector((1))
+ Connector --> NotAligned
+ style Connector fill:none,stroke:none
+ style T2_bar fill:none,stroke:none
+ style T2_stop fill:none,stroke:none
+
+```
+
+Flowchart for Initial alignment control. It starts at 'Idle', branches into 'Emergency' (LSC -> IAC) leading to 'Mark emergency' and back to 'Idle', and 'Start' (LSC -> IAC) leading to 'Send SIO' (IAC -> TXC), 'Start T2', and 'Not aligned'. From 'Not aligned', it branches into 'Stop' (LSC -> IAC) leading to 'Stop T2' and 'Cancel emergency' back to 'Idle', and 'T2' leading to 'Alignment not possible' (IAC -> LSC) which also leads to 'Cancel emergency'.
+
+T1156700-93
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 9/Q.703 (sheet 1 of 6) – Initial alignment control**
+
+
+
+```
+
+graph TD
+ subgraph Path1 [ ]
+ P1_1[/SIO, SIN
+RC → IAC/] --> P1_2[/Stop T2/]
+ P1_2 --> P1_3{Emergency?}
+ end
+ subgraph Path2 [ ]
+ P2_1[/SIE
+RC → IAC/] --> P2_2[/Stop T2/]
+ P2_2 --> P2_3{Emergency?}
+ end
+ subgraph Path3 [ ]
+ P3_1[/Emergency
+LSC → IAC/] --> P3_2[Mark emergency]
+ P3_2 --> P3_3([Not aligned])
+ end
+ P1_3 -- Yes --> P2_3
+ P1_3 -- No --> P1_4[Set T4 to Pn]
+ P2_3 -- Yes --> P2_4[Set T4 to Pe]
+ P2_3 -- No --> P3_4[Set T4 to Pe]
+ P1_4 --> P1_5[/Send SIN
+IAC → TXC/]
+ P2_4 --> P2_5[/Send SIE
+IAC → TXC/]
+ P3_4 --> P3_5[/Send SIN
+IAC → TXC/]
+ P1_5 --> P4_1[/Start T3/]
+ P2_5 --> P4_1
+ P3_5 --> P4_1
+ P4_1 --> P4_2([Aligned])
+ style Path1 fill:none,stroke:none
+ style Path2 fill:none,stroke:none
+ style Path3 fill:none,stroke:none
+
+```
+
+Flowchart for Initial alignment control. The process starts with three parallel paths: 1) SIO, SIN / RC → IAC leads to Stop T2, then to an Emergency? decision. 2) SIE / RC → IAC leads to Stop T2, then to an Emergency? decision. 3) Emergency / LSC → IAC leads to Mark emergency, then to Not aligned. From the first Emergency? decision, a 'Yes' leads to the second Emergency? decision, and a 'No' leads to Set T4 to Pn. From the second Emergency? decision, a 'Yes' leads to Set T4 to Pe, and a 'No' leads to Set T4 to Pe. All three Set T4 steps lead to Send (SIN or SIE) / IAC → TXC. All three Send steps lead to Start T3, which finally leads to Aligned. A connector circle '1' is at the top right, with an arrow pointing to the start of the third path.
+
+T1156710-93
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 9/Q.703 (sheet 2 of 6) – Initial alignment control**
+
+
+
+2
+
+```
+
+graph TD
+ Aligned1([Aligned]) --> SIE[SIE
+RC → IAC]
+ Aligned1 --> SIN[SIN
+RC → IAC]
+ Aligned1 --> Emergency[Emergency
+LSC → IAC]
+ Aligned1 --> Connector((2))
+ SIE --> SetT4_1[Set T4 to Pe]
+ SetT4_1 --> StopT3[Stop T3]
+ StopT3 --> T4EqPe{T4 = Pe ?}
+ T4EqPe -- No --> StopT3
+ T4EqPe -- Yes --> SetI[Set i to ie
+IAC → AERM]
+ SIN --> Start[Start
+IAC → AERM]
+ Emergency --> SendSIE[Send SIE
+IAC → TXC]
+ SendSIE --> SetT4_2[Set T4 to Pe]
+ SetT4_2 --> Aligned2([Aligned])
+ SetI --> Start
+ Start --> StartT4[Start T4]
+ StartT4 --> Cp[Cp := 0]
+ Cp --> Cancel[Cancel further proving]
+ Cancel --> Proving([Proving])
+ T1156720-93[T1156720-93]
+
+```
+
+T1156720-93
+
+Flowchart for Initial alignment control. It starts with 'Aligned' (oval), leading to three parallel paths: SIE (RC -> IAC), SIN (RC -> IAC), and Emergency (LSC -> IAC). The SIE path leads to 'Set T4 to Pe', then 'Stop T3', then a decision 'T4 = Pe?'. If 'No', it loops back to 'Stop T3'. If 'Yes', it leads to 'Set i to ie' and 'IAC -> AERM'. The SIN path leads directly to the 'Start' block. The Emergency path leads to 'Send SIE' (IAC -> TXC), then 'Set T4 to Pe', then 'Aligned' (oval). All three paths converge to the 'Start' block, which leads to 'IAC -> AERM', 'Start T4', 'Cp := 0', 'Cancel further proving', and finally 'Proving' (oval). A connector '2' (circle) is on the right, with a '4' next to it. A reference 'T1156720-93' is at the bottom.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 9/Q.703 (sheet 3 of 6) – Initial alignment control**
+
+
+
+2 3
+
+```
+
+graph TD
+ Start((2)) --> Stop1[Stop
+LSC → IAC]
+ Start --> T3[T3]
+ Start --> SIOS[SIOS
+RC → IAC]
+ Stop1 --> StopT3_1[Stop T3]
+ T3 --> AlignNotPossible1[Alignment
+not possible
+IAC → LSC]
+ SIOS --> AlignNotPossible2[Alignment
+not possible
+IAC → LSC]
+ AlignNotPossible2 --> StopT3_2[Stop T3]
+ StopT3_1 --> Cancel[Cancel
+emergency]
+ AlignNotPossible1 --> Cancel
+ StopT3_2 --> Cancel
+ Cancel --> Idle([Idle])
+ T1156730-93[T1156730-93]
+
+```
+
+Flowchart for Initial alignment control. It starts with a circle containing '2'. Three parallel paths lead to 'Cancel emergency' and then 'Idle'. Path 1: 'Stop LSC → IAC' → 'Stop T3'. Path 2: 'T3' → 'Alignment not possible IAC → LSC'. Path 3: 'SIOS RC → IAC' → 'Alignment not possible IAC → LSC' → 'Stop T3'. A label 'T1156730-93' is near the bottom right.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 9/Q.703 (sheet 4 of 6) – Initial alignment control**
+
+
+
+```
+
+graph TD
+ Proving([Proving]) --> SIO[SIO
+RC → IAC]
+ Proving --> CorrectSU[Correct SU
+DAEDR → IAC]
+ Proving --> T4[T4]
+ Proving --> SIOS[SIOS
+RC → IAC]
+ Proving --> C3((3 6))
+
+ SIO --> StopT4_1[Stop T4]
+ StopT4_1 --> Stop_1[Stop
+IAC → AERM]
+ Stop_1 --> StartT3[Start T3]
+ StartT3 --> Aligned([Aligned])
+
+ CorrectSU --> FP1{Further proving?}
+ FP1 -- No --> C6((6 6))
+ FP1 -- Yes --> StopT4_2[Stop T4]
+ StopT4_2 --> FP2{Further proving?}
+ FP2 -- Yes --> C5((5 6))
+ FP2 -- No --> AC[Alignment complete
+IAC → LSC]
+
+ T4 --> FP2
+
+ SIOS --> Stop_2[Stop
+LSC → IAC]
+ Stop_2 --> StopT4_3[Stop T4]
+ StopT4_3 --> C4((4 6))
+
+ AC --> C4
+ AP[Alignment not possible
+IAC → LSC] --> C4
+
+```
+
+Flowchart for Initial alignment control. The process starts with 'Proving' and branches into four parallel paths: SIO, Correct SU, T4, and SIOS. Each path has specific steps and decision points leading to 'Aligned', 'Stop', or connector circles 3, 4, and 5. Timers (T3, T4) and state transitions (RC to IAC, IAC to AERM, IAC to LSC) are indicated.
+
+T1156740-93
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 9/Q.703 (sheet 5 of 6) – Initial alignment control**
+
+
+
+```
+
+graph TD
+ C3((3)) --> AP[Abort proving
+AERM → IAC]
+ C3 --> EM[Emergency
+LSC → IAC]
+ C3 --> SIE[SIE
+RC → IAC]
+
+ AP --> CP1[Cp := Cp + 1]
+ CP1 --> CP5{Cp := 5?}
+ CP5 -- No --> MFP[Mark
+further proving]
+ CP5 -- Yes --> ANP[Alignment
+not possible
+IAC → LSC]
+ ANP --> ST4_1[Stop T4]
+ ST4_1 --> C4
+
+ EM --> SSIE[Send SIE
+IAC → TXC]
+ SSIE --> MFP
+
+ SIE --> T4PE{T4 = Pe?}
+ T4PE -- Yes --> PROVING
+ T4PE -- No --> ST4_2[Stop T4]
+ ST4_2 --> ST4PE[Set T4 to Pe]
+ ST4PE --> STOP1[Stop
+IAC → AERM]
+ STOP1 --> SETTI[Set Ti to Tie
+IAC → AERM]
+ SETTI --> C5
+
+ C4((4)) --> STOP2[Stop
+IAC → AERM]
+ STOP2 --> CE[Cancel
+emergency]
+ CE --> IDLE([Idle])
+
+ C5((5)) --> START[Start
+IAC → AERM]
+ START --> CFP[Cancel
+further proving]
+ CFP --> ST4_3[Start T4]
+ ST4_3 --> PROVING
+
+ MFP --> PROVING
+ C6((6)) --> PROVING
+ PROVING([Proving])
+
+ style IDLE fill:none,stroke-width:1px
+ style PROVING fill:none,stroke-width:1px
+
+```
+
+T1156750-93
+
+Flowchart for Initial alignment control (sheet 6 of 6). The chart shows logic paths starting from connectors 3, 4, 5, and 6, involving variables like Cp, T4, and Pe, and states like Idle and Proving.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 9/Q.703 (sheet 6 of 6) – Initial alignment control**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> LPO[Local processor outage
+LSC → POC]
+ Idle1 --> RPO[Remote processor outage
+LSC → POC]
+ LPO --> LPO_state([Local processor outage])
+ RPO --> RPO_state([Remote processor outage])
+ LPO_state --> Stop1[Stop
+LSC → POC]
+ LPO_state --> RPO2[Remote processor outage
+LSC → POC]
+ LPO_state --> LPR[Local processor recovered
+LSC → POC]
+ Stop1 --> Idle2([Idle])
+ RPO2 --> BothOut([Both processors out])
+ LPR --> NoOutage1[No processor outage
+POC → LSC]
+ NoOutage1 --> Idle3([Idle])
+ BothOut --> RPR[Remote processor recovered
+LSC → POC]
+ BothOut --> LPR2[Local processor recovered
+LSC → POC]
+ BothOut --> Stop2[Stop
+LSC → POC]
+ RPR --> LPO2([Local processor outage])
+ LPR2 --> RPO3([Remote processor outage])
+ Stop2 --> Idle4([Idle])
+ LPO2 --> BothOut2([Both processors out])
+ RPO3 --> NoOutage2[No processor outage
+POC → LSC]
+ Stop3[Stop
+LSC → POC] --> Idle5([Idle])
+ NoOutage2 --> Idle6([Idle])
+ T1156760-93
+
+```
+
+Flowchart for Processor outage control. The process starts at 'Idle' and branches based on 'Local processor outage' or 'Remote processor outage' (both LSC → POC). It tracks the state of both processors through various intermediate states like 'Local processor outage', 'Remote processor outage', 'Both processors out', 'Local processor recovered', and 'No processor outage' until it returns to 'Idle'.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 10/Q.703 – Processor outage control**
+
+
+
+```
+
+graph TD
+ Idle([Idle]) --> Start[Start
+RC → DAEDR]
+ Start --> Cancel[Cancel
+octet counting mode]
+ Cancel --> Zero[Start
+zero deletion]
+ Zero --> Flag[Start
+flag detection]
+ Flag --> Bit[Start
+bit counting]
+ Bit --> Octet[Start
+octet counting]
+ Octet --> Seven[Start
+detection of 7 consecutive one's]
+ Seven --> Check[Start
+check bit control]
+ Check --> InService1([In service])
+
+ InService2([In service]) --> BeforeZero[Before
+zero deletion]
+ BeforeZero --> Seven1[7 consecutive one's]
+ Seven1 --> Mark[Mark
+octet counting mode]
+ Mark --> InService1
+
+ InService2 --> M7[m + 7 octets
+without flags]
+ M7 --> OctetCounting[16 octets]
+ OctetCounting --> OctetCountingMode{Octet
+counting mode?}
+ OctetCountingMode -- Yes --> SUError1[SU in error
+DAEDR → SUERM]
+ SUError1 --> SUError2[SU in error
+DAEDR → AERM]
+ SUError2 --> InService1
+ OctetCountingMode -- No --> InService1
+
+ InService2 --> Connector1((1))
+ Connector1 --> Start
+ InService2 --> Connector2((2))
+ Connector2 --> OctetCounting
+
+```
+
+The flowchart illustrates the receiving process for delimitation, alignment, and error detection. It begins with an 'Idle' state, followed by 'Start RC → DAEDR'. A sequence of actions follows: 'Cancel octet counting mode', 'Start zero deletion', 'Start flag detection', 'Start bit counting' (with a note 'Number of bits between flags'), 'Start octet counting' (with a note 'output every m + 7 octets without flags and every 16 octets'), 'Start detection of 7 consecutive one's', and 'Start check bit control', leading to an 'In service' state. From another 'In service' state, a 'Before zero deletion' phase leads to '7 consecutive one's' detection, then 'Mark octet counting mode', which also leads to 'In service'. Another path from 'In service' goes through 'm + 7 octets without flags' and '16 octets' to a decision 'Octet counting mode?'. If 'Yes', it leads to 'SU in error DAEDR → SUERM' and then 'SU in error DAEDR → AERM', which both lead to 'In service'. If 'No', it leads directly to 'In service'. Connector 1 leads from 'In service' back to 'Start RC → DAEDR'. Connector 2 leads from 'In service' to the '16 octets' block. Reference T1156770-93 is noted near connector 2.
+
+Flowchart for Delimitation, alignment and error detection (receiving)
+
+*m* Maximum length in octet of SIF permitted on this signalling link
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 11/Q.703 (sheet 1 of 2) – Delimitation, alignment and error detection (receiving)**
+
+
+
+```
+
+graph TD
+ Start((1)) --> BitsReceived[Bits received]
+ BitsReceived -.-> BetweenFlags[Between flags after zero deletion]
+ BitsReceived --> HowManyBits{How many received bits?}
+ HowManyBits -- "N x 8 (5 <= N < m + 7)" --> CheckBitsCorrect{Check bits correct?}
+ HowManyBits -- "Other" --> DiscardBits[Discard all received bits]
+ CheckBitsCorrect -- No --> DiscardBits
+ CheckBitsCorrect -- Yes --> OctetCountingMode1{Octet counting mode?}
+ OctetCountingMode1 -- No --> CancelOctetCounting[Cancel octet counting mode]
+ OctetCountingMode1 -- Yes --> DeleteCheckBits[Delete check bits]
+ CancelOctetCounting --> DeleteCheckBits
+ DeleteCheckBits --> SignalUnitRC[Signal unit DAEDR -> RC]
+ SignalUnitRC --> CorrectSU_IAC[Correct SU DAEDR -> IAC]
+ CorrectSU_IAC --> CorrectSU_SUERM[Correct SU DAEDR -> SUERM]
+ CorrectSU_SUERM --> InService((In service))
+ DiscardBits --> OctetCountingMode2{Octet counting mode?}
+ OctetCountingMode2 -- Yes --> InService
+ OctetCountingMode2 -- No --> SU_Error_SUERM[SU in error DAEDR -> SUERM]
+ SU_Error_SUERM --> SU_Error_AERM[SU in error DAEDR -> AERM]
+ SU_Error_AERM --> InService
+ InService -.-> T1156780-93[T1156780-93]
+
+```
+
+Flowchart for delimitation, alignment and error detection (receiving). The process starts with 'Bits received' (between flags after zero deletion), followed by 'How many received bits?'. If N x 8 (5 <= N < m + 7), it proceeds to 'Check bits correct?'. If 'No', it goes to 'Discard all received bits'. If 'Yes', it proceeds to 'Octet counting mode?'. If 'No', it goes to 'Cancel octet counting mode'. If 'Yes', it goes to 'Delete check bits'. From 'Delete check bits', it goes to 'Signal unit DAEDR -> RC', then 'Correct SU DAEDR -> IAC', then 'Correct SU DAEDR -> SUERM', and finally 'In service'. From 'Discard all received bits', it proceeds to 'Octet counting mode?'. If 'Yes', it goes to 'In service'. If 'No', it goes to 'SU in error DAEDR -> SUERM', then 'SU in error DAEDR -> AERM', and finally 'In service'. A connector '2' is shown on the left side of the 'Check bits correct?' decision.
+
+*N* Number of octets received between flags
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 11/Q.703 (sheet 2 of 2) – Delimitation, alignment and error detection (receiving)**
+
+
+
+```
+
+graph TD
+ Idle([Idle]) --> Start[/Start
+TXC → DAEDT/]
+ Start --> TR1[/Transmission request
+DAEDT → TXC/]
+ TR1 --> InService1([In service])
+ InService1 --> SignalUnit[/Signal unit
+TXC → DAEDT/]
+ SignalUnit --> GCB[Generate check bits]
+ GCB --> IZ[Insert zero]
+ IZ -.-> Note["Following each five consecutive one's"]
+ IZ --> GF[Generate flags]
+ GF --> BT[/Bits for transmission
+DAEDT → L1/]
+ BT --> TR2[/Transmission request
+DAEDT → TXC/]
+ TR2 --> InService2([In service])
+
+```
+
+T1156790-93
+
+Flowchart showing the transmitting process for delimitation, alignment, and error detection. The steps are: Idle (oval) -> Start (parallelogram, TXC -> DAEDT) -> Transmission request (parallelogram, DAEDT -> TXC) -> In service (oval) -> Signal unit (parallelogram, TXC -> DAEDT) -> Generate check bits (rectangle) -> Insert zero (rectangle, with a note 'Following each five consecutive one's') -> Generate flags (rectangle) -> Bits for transmission (parallelogram, DAEDT -> L1) -> Transmission request (parallelogram, DAEDT -> TXC) -> In service (oval).
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 12/Q.703 – Delimitation, alignment and error detection (transmitting)**
+
+
+
+```
+
+graph TD
+ Idle([Idle]) --> Start1{{Start
+LSC → TXC}}
+ Start1 --> Start2{{Start
+TXC → DAEDT}}
+ Start2 --> CancelLSSU[Cancel LSSU available]
+ CancelLSSU --> CancelSIB[Cancel SIB received]
+ CancelSIB --> CancelRTB[Cancel RTB full]
+ CancelRTB --> CancelMSU[Cancel MSU inhibited]
+ CancelMSU --> SetVars1["FSNL := 127
+FSNT := 127
+FSNX := 0
+FIB := BIB := 1"]
+ SetVars1 --> SetVars2["FSNF := 0
+Cm := 0"]
+ SetVars2 --> InService([In service])
+
+```
+
+T1177660-95
+
+Flowchart of Basic transmission control. The process starts at 'Idle', proceeds through 'Start LSC -> TXC', 'Start TXC -> DAEDT', 'Cancel LSSU available', 'Cancel SIB received', 'Cancel RTB full', 'Cancel MSU inhibited', then sets variables (FSNL := 127, FSNT := 127, FSNX := 0, FIB := BIB := 1), then sets (FSNF := 0, Cm := 0), and finally reaches 'In service'. A connector circle with '1' inside and '2' outside points to the flow between 'Cancel LSSU available' and 'Cancel SIB received'. A vertical line on the left is labeled '1' and '2'.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 13/Q.703 (sheet 1 of 7) – Basic transmission control**
+
+
+
+```
+
+stateDiagram-v2
+ [*] --> In_service
+ state "In service" as In_service
+ In_service --> Send_SIOS_SIPO [Send SIOS, SIPO
+LSC -> TXC]
+ In_service --> Send_SIO_SIN_SIE [Send SIO, SIN, SIE
+IAC -> TXC]
+ In_service --> T6_bar [T6-bar]
+ In_service --> Start_LSC_TXC [Start
+LSC -> TXC]
+ Send_SIOS_SIPO --> Stop_T7_1 [Stop T7]
+ Stop_T7_1 --> Mark_LSSU [Mark LSSU available]
+ Mark_LSSU --> Store_status [Store status indication]
+ Store_status --> In_service
+ Send_SIO_SIN_SIE --> Send_SIB [Send SIB
+CC -> TXC]
+ Send_SIB --> Stop_T7_1
+ T6_bar --> Link_failure [Link failure
+TXC -> LSC]
+ Link_failure --> Cancel_SIB [Cancel SIB received]
+ Cancel_SIB --> Stop_T7_2 [Stop T7]
+ Stop_T7_2 --> In_service
+ Start_LSC_TXC --> In_service
+ Start_LSC_TXC --> Connector_2((2))
+ Connector_2 --> Connector_3((3))
+ Connector_3 --> Connector_1((1))
+ Connector_1 --> Stop_T7_1
+
+```
+
+The flowchart illustrates the basic transmission control logic. It begins with an 'In service' state. From this state, four possible actions are initiated: 'Send SIOS, SIPO' (LSC → TXC), 'Send SIO, SIN, SIE' (IAC → TXC), a timer condition $\overline{T6}$ , or 'Start' (LSC → TXC). The 'Send SIOS, SIPO' path leads to 'Stop T7', then 'Mark LSSU available', then 'Store status indication', and finally back to 'In service'. The 'Send SIO, SIN, SIE' path leads to 'Send SIB' (CC → TXC), which then leads to 'Stop T7'. The $\overline{T6}$ path leads to 'Link failure' (TXC → LSC), then 'Cancel SIB received', then 'Stop T7', and finally back to 'In service'. The 'Start' (LSC → TXC) path leads directly back to 'In service'. Reference numbers 1, 2, and 3 are used for cross-referencing between sheets. A small code 'T1156810-93' is present near the bottom right of the diagram.
+
+Flowchart for Basic transmission control (Figure 13/Q.703 sheet 2 of 7). The diagram shows state transitions between 'In service' and 'Link failure' states. It includes actions like 'Send SIOS, SIPO', 'Send SIB', and 'Start LSC -> TXC'. Reference numbers 1, 2, and 3 are used for cross-referencing between sheets.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 13/Q.703 (sheet 2 of 7) – Basic transmission control**
+
+3, 2
+
+
+
+```
+
+graph TD
+ 2((2)) --> TR[Transmission request
+DAEDT → TXC]
+ TR --> LSSU_Avail{LSSU available?}
+ LSSU_Avail -- Yes --> Insert[Insert stored status indication]
+ LSSU_Avail -- No --> MSU_Inh{MSU inhibited?}
+ MSU_Inh -- Yes --> 4a((4))
+ MSU_Inh -- No --> FSNT_FSNL{FSNT = FSNL?}
+ FSNT_FSNL -- Yes --> Cm_0{Cm = 0?}
+ FSNT_FSNL -- No --> 6((6))
+ Cm_0 -- Yes --> Insert
+ Cm_0 -- No --> RTB_Full{RTB full?}
+ RTB_Full -- Yes --> Insert
+ RTB_Full -- No --> Fetch[Fetch MSU from TB]
+ Fetch --> 5((5))
+ Insert --> LSSU_SIB{LSSU is SIB?}
+ LSSU_SIB -- Yes --> Cancel[Cancel LSSU available]
+ LSSU_SIB -- No --> 4b((4))
+ Cancel --> 4c((4))
+
+```
+
+Annotations:
+
+- FSNT = FSNL during a retransmission cycle
+- In this case FSNT is the FSN of the last MSU transmitted
+- Cm = 0 indicates TB empty
+
+Flowchart for Basic transmission control. The process starts at connector 2, goes to 'Transmission request DAEDT -> TXC', then to decision 'LSSU available?'. If 'Yes', it goes to 'Insert stored status indication'. If 'No', it goes to 'MSU inhibited?'. If 'Yes', it goes to connector 4. If 'No', it goes to 'FSNT = FSNL?'. If 'Yes', it goes to 'Cm = 0?'. If 'No', it goes to 'RTB full?'. If 'Yes', it goes to connector 6. If 'No', it goes to 'Fetch MSU from TB' and then to connector 5. From 'Insert stored status indication', it goes to 'LSSU is SIB?'. If 'Yes', it goes to 'Cancel LSSU available' and then to connector 4. If 'No', it goes to connector 4. Annotations include: 'FSNT = FSNL during a retransmission cycle', 'In this case FSNT is the FSN of the last MSU transmitted', and 'Cm = 0 indicates TB empty'.
+
+6
+
+4, 5
+
+T1177620-95
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 13/Q.703 (sheet 3 of 7) – Basic transmission control**
+
+5, 6
+
+3 5
+
+3 6
+
+ $C_m := C_m - 1$
+
+FSNT := FSNT + 1
+
+ FSNL := FSNL + 1
+ FSNT := FSNL
+
+ Fetch MSU
+ from RTB
+
+ 1st
+ message
+ in RTB?
+
+FSNL = FSNF?
+
+No
+
+Yes
+
+ FSNT value
+ TXC → RC
+
+Start T7
+
+ Store MSU
+ in RTB
+
+ Depending on
+ implementation
+ there may be
+ other considerations
+ that lead to an RTB
+ full condition,
+ e.g. buffer space
+
+ FSNT value
+ TXC → RC
+
+4
+
+4
+
+3
+
+ FSNL =
+ FSNF – 2?
+
+Yes
+
+No
+
+ BIBT := BIB
+ BSNT := FSNX – 1
+ FIBT := FIB
+
+ Mark
+ RTB full
+
+ Signal unit
+ TXC → DAEDT
+
+T1177630-95
+
+In service
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 13/Q.703 (sheet 4 of 7) – Basic transmission control**
+**Recommendation Q.703 (07/96)**
+
+55
+
+
+
+```
+
+ graph TD
+ Start5((3 5)) --> Op1["Cm := Cm - 1"]
+ Op1 --> Op2["FSNL := FSNL + 1
+FSNT := FSNL"]
+ Op2 --> Dec1{"FSNL = FSNF?"}
+ Dec1 -- Yes --> Op3["Start T7"]
+ Dec1 -- No --> Op4["Store MSU in RTB"]
+ Op3 --> Op4
+ Op4 --> Op5["FSNT value
+TXC → RC"]
+ Op5 --> Dec2{"FSNL = FSNF - 2?"}
+ Dec2 -- Yes --> Op6["Mark RTB full"]
+ Dec2 -- No --> Op7["BIBT := BIB
+BSNT := FSNX - 1
+FIBT := FIB"]
+ Op6 --> Op7
+ Op7 --> Op8["Signal unit
+TXC → DAEDT"]
+ Op8 --> End([In service])
+
+ Start6((3 6)) --> Op9["FSNT := FSNT + 1"]
+ Op9 --> Op10["Fetch MSU from RTB"]
+ Op10 --> Op11["FSNT value
+TXC → RC"]
+ Op11 --> Op8
+
+ Start4((4)) --> Op7
+
+```
+
+Flowchart of Basic transmission control process
+
+
+
+```
+
+graph TD
+ Entry((3)) --> P1[Send FISU
+LSC → TXC]
+ Entry --> P2[Send MSU
+LSC → TXC]
+ Entry --> P3[—
+T7]
+ Entry --> P4[NACK to be sent
+RC → TXC]
+ Entry --> P5[SIB received
+RC → TXC]
+ Entry --> P6[Message for transmission
+L3 → TXC]
+
+ P1 --> S1[Stop T7]
+ S1 --> M1[Mark MSU inhibited]
+ M1 --> C1[Cancel LSSU available]
+
+ P2 --> D2{FSNL = FSNF - 1?}
+ D2 -- Yes --> L1[Link failure
+TXC → LSC]
+ D2 -- No --> S2[Start T7]
+ L1 --> S3[Stop T6]
+ S3 --> C2[Cancel SIB received]
+ S2 --> C3[Cancel MSU inhibited]
+ C3 --> C4[Cancel LSSU available]
+
+ P3 --> L1
+ L1 --> S3
+ S3 --> C2
+
+ P4 --> B1[—
+BIB := BIB]
+
+ P5 --> D5{SIB received?}
+ D5 -- Yes --> S4[Start T7]
+ D5 -- No --> S5[Start T6]
+ S5 --> M2[Mark SIB received]
+ M2 --> S4
+
+ P6 --> S6[Store MSU in TB]
+
+ C1 --> Exit((6))
+ C4 --> Exit
+ C2 --> Exit
+ B1 --> Exit
+ S4 --> Exit
+ S6 --> Exit
+
+ Exit --> InService([In service])
+
+```
+
+Flowchart for Basic transmission control (Figure 13/Q.703 sheet 5 of 7). The diagram shows five parallel processing paths starting from a common entry point (3) and converging to a common exit point (6) leading to 'In service'. Path 1: Send FISU (LSC -> TXC) -> Stop T7 -> Mark MSU inhibited -> Cancel LSSU available. Path 2: Send MSU (LSC -> TXC) -> Decision: FSNL = FSNF - 1? (If Yes, RTB empty -> Link failure TXC -> LSC -> Stop T6 -> Cancel SIB received; If No -> Start T7 -> Cancel MSU inhibited -> Cancel LSSU available). Path 3: T7 timer -> Link failure TXC -> LSC -> Stop T6 -> Cancel SIB received. Path 4: NACK to be sent (RC -> TXC) -> BIB := BIB. Path 5: SIB received (RC -> TXC) -> Decision: SIB received? (If Yes -> Start T7; If No -> Start T6 -> Mark SIB received -> Start T7). Path 6: Message for transmission (L3 -> TXC) -> Store MSU in TB. All paths lead to a common horizontal line that exits at point 6.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+Figure 13/Q.703 (sheet 5 of 7) – Basic transmission control
+
+
+
+Flowchart illustrating Basic transmission control (Figure 13/Q.703 (sheet 6 of 7)).
+
+The process starts at connector 5 (circle 7) and branches into three main paths:
+
+- Path 1 (Left):** Input: BSNR and BIBR (RC → TXC) → Decision: $FSNF = BSNR + 1?$
+ - If **Yes**: Decision: FIB = BIBR?
+ - If **Yes**: Update FSNX → In service.
+ - If **No**: Decision: SIB received?
+ - If **Yes**: Cancel SIB received → Stop T6 → FIB := BIBR, $FSNT := FSNF - 1$ → In service.
+ - If **No**: Stop T6 → FIB := BIBR, $FSNT := FSNF - 1$ → In service.
+ - If **No**: Decision: SIB received?
+ - If **Yes**: Cancel SIB received → Stop T6 → Erase in RTB MSUs up to FSN = BSNR → $FSNF = BSNR + 1$ → Decision: $FSNL = FSNF - 1?$ (RTB empty?)
+ - If **Yes**: Stop T7 → In service.
+ - If **No**: Start T7 → Cancel RTB full → connector 6 (circle 8).
+ - If **No**: Erase in RTB MSUs up to FSN = BSNR → $FSNF = BSNR + 1$ → Decision: $FSNL = FSNF - 1?$ (RTB empty?)
+ - If **Yes**: Stop T7 → In service.
+ - If **No**: Start T7 → Cancel RTB full → connector 6 (circle 8).
+- Path 2 (Middle):** Input: FSNX value (RC → TXC) → Update FSNX → In service.
+- Path 3 (Right):** From connector 7 (circle 9): Input: Retrieval request and FSNC (LSC → TXC) → Erase in RTB MSUs up to FSN = FSNC → $FSNF := FSNC + 1$ → Retrieval messages (TXC → L3) [Content of RTB followed by content of TB] → Cancel RTB full → Retrieval complete (TXC → L3) → $C_m = 0$ → $FSNL := FSNC$ , $FSNT := FSNL$ → In service.
+
+Connector 6 (circle 8) is an entry point leading to the decision "SIB received?" on the left path.
+
+Reference: T1177650-95
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 13/Q.703 (sheet 6 of 7) – Basic transmission control**
+
+9
+
+
+
+```
+graph TD; Start((6
+9)) --> F[Flush buffers
+LSC → TXC]; F --> E[Erase all MSUs
+in RTB and TB]; E --> C[Cancel
+RTB full]; C --> M[Cm := 0]; M --> FSNF[FSNF := BSNR + 1]; FSNF -.-> N2a[Note 2]; FSNF --> FSNL[FSNL := BSNR
+FSNT := BSNR]; FSNL -.-> N2b[Note 2]; FSNL --> StopT7[/Stop T7/]; StopT7 --> InService([In service])
+```
+
+Flowchart for Basic transmission control. The process starts at connector 6 (labeled 9), followed by 'Flush buffers' (LSC -> TXC), 'Erase all MSUs in RTB and TB', 'Cancel RTB full', 'Cm := 0', 'FSNF := BSNR + 1' (Note 2), 'FSNL := BSNR' and 'FSNT := BSNR' (Note 2), 'Stop T7', and ends at 'In service'.
+
+T1142170-92
+
+###### **NOTES**
+
+1 – See the abbreviations and timers used in this Figure in 12.2.
+
+2 – The BSNR is from the first MSU/FSU terminating the remote processor outage state.
+
+**Figure 13/Q.703 (sheet 7 of 7) – Basic transmission control**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> Start1[/Start
+LSC → RC/]
+ Idle1 --> RetrieveBSNT[/Retrieve BSNT
+LSC → RC/]
+ Start1 --> Start2[/Start
+RC → DAEDR/]
+ RetrieveBSNT --> BSNTCalc[BSNT := FSNX - 1]
+ Start2 --> Init1[FSNX := 0
+FIBX := 1]
+ BSNTCalc --> BSNT2[/BSNT
+RC → L3/]
+ Init1 --> Init2[FSNF := 0
+FSNT := 127
+RTR := 0]
+ BSNT2 --> Idle2([Idle])
+ Init2 --> CancelFISU[Cancel
+FISU/MSU
+accepted]
+ CancelFISU --> CancelBSNR[Cancel
+abnormal
+BSNR]
+ CancelBSNR --> CancelFIBR[Cancel
+abnormal
+FIBR]
+ CancelFIBR --> CancelCongestion[Cancel
+congestion discard
+and
+congestion accept]
+ CancelCongestion --> InService([In service])
+
+```
+
+T1156820-93
+
+Flowchart for Basic reception control. It starts at 'Idle', branches into 'Start' (LSC -> RC) and 'Retrieve BSNT' (LSC -> RC). The 'Start' path leads to 'Start' (RC -> DAEDR), then initializes FSNX, FIBX, FSNF, FSNT, and RTR, followed by cancellation of FISU/MSU, abnormal BSNR, abnormal FIBR, and congestion discard/accept, ending at 'In service'. The 'Retrieve BSNT' path calculates BSNT := FSNX - 1, then proceeds to 'BSNT' (RC -> L3) and back to 'Idle'.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 14/Q.703 (sheet 1 of 7) – Basic reception control**
+
+
+
+```
+
+ graph TD
+ Start([In service]) --> J1((1))
+ J1 --> Stop[/Stop
+LSC → RC/]
+ J1 --> FSNT[/FSNT value
+TXC → RC/]
+ J1 --> Reject[/Reject MSU/FISU
+LSC → RC/]
+ J1 --> Accept[/Accept MSU/FISU
+LSC → RC/]
+ J1 --> SignalUnit[/Signal unit
+DAEDR → RC/]
+
+ Stop --> Normal[/Normal
+RC → CC/]
+ Normal --> Idle([Idle])
+
+ FSNT --> Update[Update FSNT]
+ Update --> InService1([In service])
+
+ Reject --> Cancel[Cancel MSU/FISU accepted]
+ Cancel --> InService1
+
+ Accept --> Mark[Mark MSU/FISU accepted]
+ Mark --> InService1
+
+ SignalUnit --> IsLSSU{Signal unit is LSSU?}
+ IsLSSU -- No --> J2((2))
+ IsLSSU -- Yes --> LSSUType{LSSU type?}
+
+ LSSUType --> SIN[/SIN
+RC → LSC/]
+ LSSUType --> SIE[/SIE
+RC → LSC/]
+ LSSUType --> SIO[/SIO
+RC → LSC/]
+ LSSUType --> SIOS[/SIOS
+RC → LSC/]
+ LSSUType --> SIPO[/SIPO
+RC → LSC/]
+ LSSUType --> SIB[/SIB received
+RC → TXC/]
+
+ SIN --> SIN2[/SIN
+RC → IAC/]
+ SIE --> SIE2[/SIE
+RC → IAC/]
+ SIO --> SIO2[/SIO
+RC → IAC/]
+ SIOS --> SIOS2[/SIOS
+RC → IAC/]
+ SIPO --> InService2([In service])
+ SIB --> InService2
+
+```
+
+Flowchart for Basic reception control. It starts with 'In service' and branches into various signal unit types (Stop, FSNT value, Reject MSU/FISU, Accept MSU/FISU, Signal unit). It includes decision diamonds for 'Signal unit is LSSU?' and 'LSSU type?', leading to states like 'Idle', 'Normal', 'Update FSNT', 'Cancel MSU/FISU accepted', 'Mark MSU/FISU accepted', and various signal unit processing paths (SIN, SIE, SIO, SIOS, SIPO, SIB).
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+Figure 14/Q.703 (sheet 2 of 7) – Basic reception control
+
+
+
+2
+
+BSNR in RTB or same as previous BSNR?
+Inequalities are expressed Modulo 128
+
+2
+
+3
+
+4
+
+3
+
+4
+
+5
+
+4, 6
+
+7
+
+```
+
+graph TD
+ 2((2)) --> D1{FSNF - 1 <= BSNR <= FSNT?}
+ D1 -- No --> P1[Discard Signal unit]
+ D1 -- Yes --> D2{Abnormal BSNR?}
+ D2 -- Yes --> D3{UNB := 1?}
+ D2 -- No --> D4{FIBR = FIBX?}
+ D3 -- Yes --> P2[Cancel abnormal BSNR]
+ D3 -- No --> P3[UNB := 1]
+ P2 --> D4
+ P3 --> P4[Discard signal unit]
+ P4 --> E1([In service])
+ D4 -- No --> 5((5))
+ D4 -- Yes --> D5{Abnormal FIBR?}
+ D5 -- Yes --> 6((6))
+ D5 -- No --> P5[FISU/MSU received
+RC -> LSC]
+ P5 --> P6[BSNR and BIBR
+RC -> TXC]
+ P6 --> P7[FSNF := BSNR + 1]
+ P7 --> 7((7))
+ D2 --> D6{Abnormal BSNR?}
+ D6 -- Yes --> P8[Link failure
+RC -> LSC]
+ P8 --> E2([Idle])
+ D6 -- No --> P9[Mark abnormal BSNR]
+ P9 --> P10[UNB := 0]
+ P10 --> P11[Discard signal unit]
+ P11 --> E1
+
+```
+
+T1156840-93/d41
+
+Flowchart for Basic reception control (Figure 14/Q.703 sheet 3 of 7). The process starts at connector 2, checks if FSNF - 1 <= BSNR <= FSNT. If No, it discards the signal unit. If Yes, it checks if BSNR is abnormal. If Yes, it checks if UNB := 1. If Yes, it cancels abnormal BSNR. If No, it checks if FIBR = FIBX. If Yes, it checks if FIBR is abnormal. If Yes, it goes to connector 6. If No, it receives FISU/MSU, RC -> LSC, BSNR and BIBR, RC -> TXC, and sets FSNF := BSNR + 1, then goes to connector 7. If FIBR != FIBX, it goes to connector 5. If BSNR is not abnormal, it checks if UNB := 1. If Yes, it sets UNB := 1, discards signal unit, and goes to In service. If No, it checks if BSNR is abnormal. If Yes, it goes to Link failure, RC -> LSC, and Idle. If No, it marks abnormal BSNR, sets UNB := 0, discards signal unit, and goes to In service.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+Figure 14/Q.703 (sheet 3 of 7) – Basic reception control
+
+
+
+```
+
+graph TD
+ 5((5)) --> DSU1[Discard signal unit]
+ DSU1 --> AF{Abnormal FIBR?}
+ AF -- Yes --> 3a((3))
+ AF -- No --> RTR{RTR = 1?}
+ RTR -- Yes --> BSNR[BSNR and BIBR]
+ BSNR --> RC[RC -> TXC]
+ RC --> FSNF[FSNF := BSNR + 1]
+ RTR -- No --> MAF[Mark abnormal FIBR]
+ MAF --> UNF0[UNF := 0]
+ UNF0 --> IS([In service])
+ FSNF --> IS
+ 6((6)) --> UNF1{UNF = 1?}
+ UNF1 -- Yes --> CAF[Cancel abnormal FIBR]
+ CAF --> 4((4))
+ UNF1 -- No --> UNF1a[UNF := 1]
+ UNF1a --> DSU2[Discard signal unit]
+ 8((8)) --> DSU2
+ DSU2 --> IS
+ T1156850-93[T1156850-93]
+
+```
+
+Flowchart for Basic reception control. The process starts at node 5, leading to 'Discard signal unit'. From there, it checks 'Abnormal FIBR?'. If 'Yes', it goes to node 3. If 'No', it checks 'RTR = 1?'. If 'Yes', it goes to 'BSNR and BIBR' -> 'RC -> TXC' -> 'FSNF := BSNR + 1'. If 'No', it goes to 'Mark abnormal FIBR' -> 'UNF := 0'. Both 'UNF := 0' and 'FSNF := BSNR + 1' lead to 'In service'. Another path starts at node 6, checking 'UNF = 1?'. If 'Yes', it goes to 'Cancel abnormal FIBR' -> node 4. If 'No', it goes to 'UNF := 1' -> 'Discard signal unit'. Node 8 also leads to 'Discard signal unit'. The diagram includes node numbers (3, 4, 5, 6, 8) and internal labels like 'T1156850-93'.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 14/Q.703 (sheet 4 of 7) – Basic reception control**
+
+7
+
+8
+
+
+
+```
+
+graph TD
+ Start((7)) --> MSU_FISU_Accepted{MSU/FISU accepted?}
+ MSU_FISU_Accepted -- No --> End((8))
+ MSU_FISU_Accepted -- Yes --> Congestion_Discard{Congestion discard?}
+ Congestion_Discard -- Yes --> Signal_Unit_MSU{Signal unit = MSU?}
+ Congestion_Discard -- No --> FSNR_FSNX{FSNR = FSNX?}
+ Signal_Unit_MSU -- No --> Discard_Signal_Unit_1[Discard signal unit]
+ Signal_Unit_MSU -- Yes --> RTR_1[RTR := 1]
+ RTR_1 --> Discard_Signal_Unit_1
+ FSNR_FSNX -- No --> FSNR_FSNX_minus_1{FSNR = FSNX - 1?}
+ FSNR_FSNX -- Yes --> Signal_Unit_MSU_2{Signal unit = MSU?}
+ Signal_Unit_MSU_2 -- No --> FSNR_FSNX_minus_1
+ Signal_Unit_MSU_2 -- Yes --> Received_Message[Received message
+RC → L3]
+ Received_Message --> FSNX_Update[FSNX := FSNX + 1
+RTR := 0]
+ FSNX_Update --> Congestion_Accept_1{Congestion accept?}
+ Congestion_Accept_1 -- Yes --> Discard_Signal_Unit_1
+ Congestion_Accept_1 -- No --> FSNX_Value[FSNX value
+RC → TXC]
+ FSNR_FSNX_minus_1 -- Yes --> Busy_1[Busy
+RC → CC]
+ FSNR_FSNX_minus_1 -- No --> Congestion_Accept_2{Congestion accept?}
+ Congestion_Accept_2 -- Yes --> Busy_1
+ Congestion_Accept_2 -- No --> NACK_Sent[NACK to be sent
+RC → TXC]
+ NACK_Sent --> RTR_FIBX[RTR := 1
+FIBX := FIBX]
+ RTR_FIBX --> Discard_Signal_Unit_2[Discard signal unit]
+ Busy_1 --> Discard_Signal_Unit_3[Discard signal unit]
+ Discard_Signal_Unit_1 --> In_Service([In service])
+ FSNX_Value --> In_Service
+ Discard_Signal_Unit_2 --> In_Service
+ Discard_Signal_Unit_3 --> In_Service
+
+```
+
+The flowchart illustrates the basic reception control process. It begins at node 7, checking if an MSU/FISU is accepted. If not, it ends at node 8. If accepted, it checks for congestion discard. If yes, it checks if the signal unit is an MSU. If yes, RTR is set to 1, and the signal unit is discarded. If no, it checks if FSNR equals FSNX. If yes, it checks if the signal unit is an MSU. If yes, the message is received and RC is set to L3, then FSNX is incremented and RTR is set to 0. If no, it checks if FSNR equals FSNX minus 1. If yes, it checks for congestion accept. If yes, RC is set to CC and the signal unit is discarded. If no, a NACK is sent and RC is set to TXC, then RTR is set to 1 and FIBX is updated. Finally, all paths lead to the 'In service' state.
+
+Flowchart for Basic reception control (Figure 14/Q.703 sheet 5 of 7).
+
+T1156860-93
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+Figure 14/Q.703 (sheet 5 of 7) – Basic reception control
+
+64 Recommendation Q.703 (07/96)
+
+Image: Figure 14/Q.703 (sheet 6 of 7) – Basic reception control flowchart
+
+```
+
+ graph TD
+ Start((1)) --> RetrieveBSNT[Retrieve BSNT
+LSC → RC]
+ RetrieveBSNT --> BSNT_Calc[BSNT = FSNX - 1]
+ BSNT_Calc --> BSNT_Out[BSNT
+RC → L3]
+
+ FromUnspecified[From unspecified implementation dependent function] -.-> CongestionDiscard[Congestion discard]
+ FromUnspecified -.-> CongestionAccept[Congestion accept]
+ FromUnspecified -.-> NoCongestion[No congestion]
+
+ CongestionDiscard --> MarkDiscard[Mark congestion discard]
+ CongestionAccept --> MarkAccept[Mark congestion accept]
+ NoCongestion --> CancelCongestion[Cancel congestion discard and congestion accept]
+
+ MarkDiscard --> Join1
+ MarkAccept --> Join1
+ CancelCongestion --> Normal[Normal
+RC → CC]
+
+ Normal --> FSNXValue[FSNX value
+RC → TXC]
+ FSNXValue --> RTRDecision{RTR = 1?}
+
+ RTRDecision -- Yes --> Join1
+ RTRDecision -- No --> NACK[NACK to be sent
+RC → TXC]
+ NACK --> FIBXCalc[FIBX = NOT FIBX]
+ FIBXCalc --> Join1
+
+ BSNT_Out --> Join1
+ Join1(( )) --> InService([In service])
+
+ InService --> End((9))
+
+```
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+### Figure 14/Q.703 (sheet 6 of 7) – Basic reception control
+
+T1131070-91
+
+
+
+9
+
+6
+
+9
+
+```
+
+graph TD
+ Start((9)) --> Retrieve[Retrieve FSNX
+LSC → RC]
+ Retrieve --> FSNX[FSNX value
+RC → TXC]
+ FSNX --> Cancel[Cancel
+congestion discard
+and
+congestion accept]
+ Cancel --> Normal[Normal
+RC → CC]
+ Normal --> RTR[RTR := 0]
+ RTR --> InService([In service])
+
+```
+
+T1177670-95
+
+Flowchart for Basic reception control. The process starts at a circle labeled '9' with '6' above it. It proceeds to a parallelogram 'Retrieve FSNX LSC → RC', then a chevron 'FSNX value RC → TXC', then a rectangle 'Cancel congestion discard and congestion accept', then a chevron 'Normal RC → CC', then a rectangle 'RTR := 0', and finally an oval 'In service'. The diagram is labeled T1177670-95 at the bottom.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 14/Q.703 (sheet 7 of 7) – Basic reception control**
+
+
+
+```
+
+graph TD
+ Idle([Idle]) --> Start1[/Start
+LSC → TXC/]
+ Start1 --> Start2[/Start
+TXC → DAEDT/]
+ Start2 --> Cancel1[Cancel LSSU
+available]
+ Cancel1 --> Cancel2[Cancel forced
+retransmission]
+ Cancel2 --> Cancel3[Cancel SIB
+received]
+ Cancel3 --> Cancel4[Cancel RTB
+full]
+ Cancel4 --> Cancel5[Cancel MSU
+inhibited]
+ Cancel5 --> Init1[FSNL := 127
+FSNX := 0
+FIB := BIB := 1]
+ Init1 --> Init2[FSNF := 0
+C := 0
+Z := 0]
+ Init2 --> InService([In service])
+
+```
+
+Flowchart for Preventive cyclic retransmission - Transmission control. The process starts at 'Idle', goes through 'Start LSC -> TXC', 'Start TXC -> DAEDT', and then a series of 'Cancel' steps: 'Cancel LSSU available', 'Cancel forced retransmission', 'Cancel SIB received', 'Cancel RTB full', and 'Cancel MSU inhibited'. It then initializes variables: 'FSNL := 127, FSNX := 0, FIB := BIB := 1', followed by 'FSNF := 0, C := 0, Z := 0', and finally reaches 'In service'. A connector circle with '1' inside is linked to the line between 'Cancel LSSU available' and 'Cancel forced retransmission'. To the left of the connector are two vertical lines labeled '1' and '2'.
+
+T1177680-95
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 15/Q.703 (sheet 1 of 7) – Preventive cyclic retransmission – Transmission control**
+
+
+
+```
+
+graph TD
+ InService1([In service]) --> SIOS[Send SIOS, SIPO
+LSC → TXC]
+ InService1 --> SIO[Send SIO, SIN
+SIE
+IAC → TXC]
+ InService1 --> T6[— T6]
+ InService1 --> Start[Start
+LSC → TXC]
+ SIOS --> StopT7_1[Stop T7]
+ SIO --> SIB[Send SIB
+CC → TXC]
+ SIB --> StopT7_1
+ StopT7_1 --> MarkLSSU[Mark LSSU
+available]
+ MarkLSSU --> StoreStatus[Store status
+indication]
+ StoreStatus --> InService2([In service])
+ T6 --> LinkFailure[Link failure
+TXC → LSC]
+ LinkFailure --> CancelSIB[Cancel SIB
+received]
+ CancelSIB --> StopT7_2[Stop T7]
+ StopT7_2 --> InService2
+ Start --> Callout1((1))
+ Callout1 --> Callout2((2))
+ Callout2 --> Callout3((3))
+ Callout3 --> InService1
+
+```
+
+T1156880-93
+
+Flowchart for Preventive cyclic retransmission - Transmission control. The diagram shows two main paths starting from 'In service'. Path 1 (left) involves sending SIOS, SIPO, SIB, and SIO, SIN, SIE, IAC messages, stopping timer T7, marking LSSU available, and storing status indication. Path 2 (right) involves a timer T6, handling a link failure, canceling SIB, and stopping timer T7. Both paths lead back to 'In service'. Callouts 1, 2, and 3 are present.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 15/Q.703 (sheet 2 of 7) – Preventive cyclic retransmission – Transmission control**
+
+
+
+2, 3
+
+```
+
+graph TD
+ 2((2)) --> TXC[Transmission request DAEDT → TXC]
+ TXC --> LSSU_Available{LSSU available?}
+ LSSU_Available -- Yes --> Insert_Status[Insert stored status indication]
+ LSSU_Available -- No --> MSU_Inhibited{MSU inhibited?}
+ MSU_Inhibited -- Yes --> Generate_FISU[Generate FISU FSNT := FSNL]
+ MSU_Inhibited -- No --> Forced_Retransmission{Forced retransmission?}
+ Forced_Retransmission -- Yes --> FSNF_FSNL{FSNF = FSNL + 1?}
+ FSNF_FSNL -- Yes --> 5((5))
+ FSNF_FSNL -- No --> Cancel_Force[Cancel forced retransmission]
+ Cancel_Force --> Cancel_RTB[Cancel RTB full]
+ Forced_Retransmission -- No --> Cm_0{Cm = 0?}
+ Cm_0 -- Yes --> FSNF_FSNL_2{FSNF = FSNL + 1?}
+ FSNF_FSNL_2 -- Yes --> 5
+ Cm_0 -- No --> RTB_Full{RTB full?}
+ RTB_Full -- Yes --> Mark_Force[Mark forced retransmission]
+ Mark_Force --> 5
+ RTB_Full -- No --> Fetch_MSU[Fetch MSU from TB]
+ Fetch_MSU --> Cm_Dec[ $C_m := C_m - 1$ ]
+ Cm_Dec --> 4((4))
+ Insert_Status --> LSSU_SIB{LSSU is SIB?}
+ LSSU_SIB -- Yes --> Cancel_LSSU[Cancel LSSU available]
+ Cancel_LSSU --> Generate_FISU
+ Generate_FISU --> BSNT[BSNT := FSNX - 1]
+ BSNT --> Signal_Unit[Signal unit TXC → DAEDT]
+ Signal_Unit --> In_Service([In service])
+
+```
+
+5
+
+5
+
+5
+
+4
+
+T1177690-95
+
+Flowchart for Preventive cyclic retransmission - Transmission control. The process starts at connector 2, proceeds to a transmission request, then checks if LSSU is available. If not, it checks if MSU is inhibited. If not inhibited, it checks for forced retransmission. If forced retransmission is active and FSNF equals FSNL + 1, it goes to connector 5. Otherwise, it checks if Cm equals 0. If Cm is 0 and FSNF equals FSNL + 1, it goes to connector 5. If Cm is not 0, it checks if the RTB is full. If full, it marks forced retransmission and goes to connector 5. If not full, it fetches an MSU from the TB, decrements Cm, and goes to connector 4. If LSSU is available, it inserts a stored status indication and checks if it is a SIB. If a SIB, it cancels LSSU availability. Finally, it generates a FISU, updates BSNT, sends a signal unit, and goes 'In service'.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 15/Q.703 (sheet 3 of 7) – Preventive cyclic retransmission – Transmission control**
+
+
+
+```
+
+graph TD
+ subgraph Path1 [Path 1]
+ Start1((3 4)) --> Init1["FSNL := FSNL + 1
+FSNT := FSNL
+BSNT := FSNX - 1"]
+ Init1 --> Store1[Store MSU in RTB]
+ Store1 --> Decision1{FSNL = FSNF?}
+ Decision1 -- Yes --> StartT7[/Start T7/]
+ Decision1 -- No --> UpdateOctet[Update octet count]
+ StartT7 --> UpdateOctet
+ UpdateOctet --> FSNTValue[/FSNT value
+TXC -> RC/]
+ FSNTValue --> Decision2{FSNL = FSNF+N1-1?}
+ Decision2 -- Yes --> MarkRTBFull[Mark RTB full]
+ Decision2 -- No --> OctetCount{Octet count > N2?}
+ OctetCount -- Yes --> MarkRTBFull
+ OctetCount -- No --> SignalUnit1[/Signal unit
+TXC -> DAEDT/]
+ MarkRTBFull --> MarkForcedRetransmission[Mark forced retransmission]
+ MarkForcedRetransmission --> SignalUnit1
+ end
+
+ subgraph Path2 [Path 2]
+ Start2((3 5)) --> FetchMSU[Fetch MSU in RTB with FSNT = Z]
+ FetchMSU --> FSNTZ[FSNT := Z]
+ FSNTZ --> BSNT["BSNT := FSNX - 1"]
+ BSNT --> SignalUnit2[/Signal unit
+TXC -> DAEDT/]
+ SignalUnit2 --> Decision3{Z = FSNL?}
+ Decision3 -- Yes --> ZFSNF[Z = FSNF]
+ Decision3 -- No --> Zplus1[Z := Z + 1]
+ ZFSNF --> CancelForced[Cancel forced retransmission]
+ Zplus1 --> CancelForced
+ end
+
+ Note1[1st message in RTB?] -.-> Decision1
+ T117770095[T1177700-95]
+ InService([In service])
+ SignalUnit1 --> InService
+ CancelForced --> InService
+ Zplus1 --> InService
+
+```
+
+Flowchart for Preventive cyclic retransmission - Transmission control. It consists of two main vertical paths starting from circles labeled '3 4' and '3 5'. Path 1 (left) starts with FSNL := FSNL + 1, FSNT := FSNL, BSNT := FSNX - 1, then Store MSU in RTB. A decision diamond 'FSNL = FSNF?' has a 'Yes' path to 'Start T7' and a 'No' path that bypasses it. A bracket labeled '1st message in RTB?' points to the 'No' path. From 'Start T7', the flow goes to 'Update octet count', then 'FSNT value TXC -> RC'. A decision diamond 'FSNL = FSNF+N1-1?' has a 'Yes' path to 'Mark RTB full' and a 'No' path to 'Octet count > N2?'. 'Octet count > N2?' has a 'Yes' path to 'Mark RTB full' and a 'No' path to 'Signal unit TXC -> DAEDT'. 'Mark RTB full' leads to 'Mark forced retransmission', which then leads to 'Signal unit TXC -> DAEDT'. Path 2 (right) starts with 'Fetch MSU in RTB with FSNT = Z', then 'FSNT := Z', then 'BSNT := FSNX - 1', then 'Signal unit TXC -> DAEDT'. A decision diamond 'Z = FSNL?' has a 'Yes' path to 'Z = FSNF' and a 'No' path to 'Z := Z + 1'. Both 'Z = FSNF' and 'Z := Z + 1' lead to 'Cancel forced retransmission'. All paths converge to a final oval labeled 'In service'. A small code 'T1177700-95' is at the bottom right of the diagram.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 15/Q.703 (sheet 4 of 7) – Preventive cyclic retransmission – Transmission control**
+
+
+
+```
+
+graph TD
+ 3((3)) --> F1[Send FISU LSC → TXC]
+ F1 --> T7_stop{Stop T7}
+ T7_stop --> M1[Mark MSU inhibited]
+ M1 --> C1[Cancel LSSU available]
+ C1 --> IS([In service])
+
+ 3 --> M2[Send MSU LSC → TXC]
+ M2 --> D1{FSNL = FSNF - 1?}
+ D1 -- Yes --> RTB[RTB empty]
+ D1 -- No --> T7_start{Start T7}
+ T7_start --> M3[Cancel MSU inhibited]
+ M3 --> C3[Cancel LSSU available]
+ C3 --> IS
+
+ M2 --> T7_double[// T7]
+ T7_double --> LF[Link failure TXC → LSC]
+ LF --> T6_stop{Stop T6}
+ T6_stop --> IS
+
+ 3 --> S1[SIB received RC → TXC]
+ S1 --> D2{SIB received?}
+ D2 -- Yes --> C5[Cm := Cm + 1]
+ D2 -- No --> T6_start{Start T6}
+ T6_start --> M4[Mark SIB received]
+ M4 --> T7_start2{Start T7}
+ T7_start2 --> C5
+ C5 --> IS
+
+ 3 --> L3[Message for transmission L3 → TXC]
+ L3 --> S2[Store MSU in TB]
+ S2 --> C5
+ C5 --> IS
+
+```
+
+Flowchart illustrating the transmission control process for preventive cyclic retransmission. The process starts at node 3 and ends at node 6, leading to the 'In service' state.
+
+**Path 1 (FISU/MSU handling):**
+
+- From node 3, send FISU (LSC → TXC). Stop T7. Mark MSU inhibited. Cancel LSSU available. Proceed to 'In service'.
+- From node 3, send MSU (LSC → TXC). Check if FSNL = FSNF - 1? (RTB empty). If Yes, proceed to 'In service'. If No, Start T7. Cancel MSU inhibited. Cancel LSSU available. Proceed to 'In service'.
+- Alternatively, from node 3, send MSU (LSC → TXC) and encounter a double T7 timer. This leads to a link failure (TXC → LSC). Stop T6. Proceed to 'In service'.
+
+**Path 2 (SIB handling):**
+
+- From node 3, receive SIB (RC → TXC). Check if SIB received? If Yes, increment $C_m := C_m + 1$ . Proceed to 'In service'.
+- If No, Start T6. Mark SIB received. Start T7. Increment $C_m := C_m + 1$ . Proceed to 'In service'.
+
+**Path 3 (L3 message handling):**
+
+- From node 3, prepare message for transmission (L3 → TXC). Store MSU in TB. Increment $C_m := C_m + 1$ . Proceed to 'In service'.
+
+Reference: T1156910-93
+
+Flowchart for Preventive cyclic retransmission – Transmission control. It shows two main paths starting from node 3 and ending at node 6. The left path handles FISU and MSU transmissions with timers T7 and T6. The right path handles SIB transmissions with timers T6 and T7. Both paths lead to an 'In service' state.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+Figure 15/Q.703 (sheet 5 of 7) – Preventive cyclic retransmission – Transmission control
+
+
+
+```
+
+graph TD
+ %% Entry Points
+ E5((5)) --> C6_1((6))
+ C6_1 --> BSNR[BSNR
+RC->TXC]
+ C6_1 --> FSNX_VAL[FSNX value
+RC->TXC]
+
+ E7((7)) --> C8((8))
+ C8 --> RET_REQ[Retrieval request and FSNC
+LSC->TXC]
+
+ E9((9)) --> C9((9))
+ C9 --> SIB_REC{SIB received}
+
+ %% Left Column Logic (SIB)
+ SIB_REC -- Yes --> CANCEL_SIB[Cancel SIB received]
+ CANCEL_SIB --> STOP_T6[Stop T6]
+ STOP_T6 --> ERASE_RTB_BSNR[Erase in RTB
+MSUs up to
+FSN=BSNR]
+ SIB_REC -- No --> ERASE_RTB_BSNR
+
+ ERASE_RTB_BSNR --> FSNF_BSNR_1[FSNF=BSNR+1]
+ FSNF_BSNR_1 --> FSNL_FSNF_1{FSNL=FSNF-1}
+
+ FSNL_FSNF_1 -- Yes --> STOP_T7[Stop T7]
+ FSNL_FSNF_1 -- No --> START_T7[Start T7]
+
+ START_T7 --> OCTET_COUNT{Octet count > N2?}
+ OCTET_COUNT -- Yes --> IN_SERVICE
+ OCTET_COUNT -- No --> CANCEL_RTB_FULL_L[Cancel RTB full]
+ CANCEL_RTB_FULL_L --> C7_L((7))
+ C7_L --> E7
+
+ STOP_T7 --> IN_SERVICE
+
+ %% Middle Column Logic (BSNR/FSNX)
+ BSNR --> FSNF_BSNR_EQ{FSNF = BSNR+1}
+ FSNF_BSNR_EQ -- No --> C6_M((6))
+ C6_M --> FSNX_VAL
+
+ FSNF_BSNR_EQ -- Yes --> C7_M((7))
+ C7_M --> FSNF_Z_FSNL{FSNF < Z < FSNL?}
+
+ FSNF_Z_FSNL -- Yes --> UPDATE_FSNX
+ FSNF_Z_FSNL -- No --> Z_FSNF[Z:=FSNF]
+ Z_FSNF --> UPDATE_FSNX
+
+ FSNX_VAL --> UPDATE_FSNX[Update FSNX]
+ UPDATE_FSNX --> IN_SERVICE
+
+ %% Right Column Logic (Retrieval)
+ RET_REQ --> ERASE_RTB_RSN[Erase in RTB
+MSUs up to
+RSN=FSNC]
+ ERASE_RTB_RSN --> FSNF_FSNC_1[FSNF:=FSNC+1
+Z:=FSNF]
+ FSNF_FSNC_1 --> RET_MSG[Retrieved messages
+TXC->L3]
+
+ %% Annotation for RTB content
+ RET_MSG -.-> RTB_CONTENT[Content of RTB followed by content of TB]
+
+ RET_MSG --> CANCEL_RTB_FULL_R[Cancel RTB full]
+ CANCEL_RTB_FULL_R --> RET_COMP[Retrieval complete
+TXC->L3]
+ RET_COMP --> CM_0[Cm := 0]
+ CM_0 --> FSNL_FSNC[FSNL:=FSNC
+FSNT:=FSNL]
+ FSNL_FSNC --> IN_SERVICE([In service])
+
+ %% Additional connections
+ FSNL_FSNF_1 -.-> RTB_EMPTY[RTB empty?]
+
+```
+
+Flowchart for Figure 15/Q.703 (sheet 6 of 7) – Preventive cyclic retransmission – Transmission control. The diagram shows complex logic for handling SIB reception, BSNR updates, FSNX updates, and retrieval requests, leading to an 'In service' state.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 15/Q.703 (sheet 6 of 7) – Preventive cyclic retransmission – Transmission control**
+
+
+
+```
+
+graph TD
+ Start((6
+8)) --> Flush[Flush buffers
+LSC → TXC]
+ Flush --> Erase[Erase all MSUs in RTB and TB]
+ Erase --> Cancel[Cancel RTB full]
+ Cancel --> CmZ["Cm := 0
+Z := BSNR + 1"]
+ CmZ --- Note2_1["(Note 2)"]
+ CmZ --> FSNF["FSNF := BSNR + 1"]
+ FSNF --- Note2_2["(Note 2)"]
+ FSNF --> FSNLNT["FSNL := BSNR
+FSNT := BSNR"]
+ FSNLNT --- Note2_3["(Note 2)"]
+ FSNLNT --> StopT7{{Stop T7}}
+ StopT7 --> InService([In service])
+
+```
+
+The flowchart illustrates the transmission control process for preventive cyclic retransmission. It begins with a start node (6 8), followed by a process to flush buffers (LSC → TXC). This is followed by erasing all MSUs in RTB and TB, and canceling RTB full. The next step is initializing $C_m := 0$ and $Z := BSNR + 1$ , which is noted as (Note 2). This is followed by setting $FSNF := BSNR + 1$ , also noted as (Note 2). Then, setting $FSNL := BSNR$ and $FSNT := BSNR$ , which is also noted as (Note 2). The process then stops timer T7 and enters the 'In service' state.
+
+Flowchart for Preventive cyclic retransmission – Transmission control
+
+T1177720-95
+
+###### NOTES
+
+- 1 – See the abbreviations and timers used in this Figure in 12.2.
+- 2 – The BSNR is from the first MSU/FISU terminating the remote processor outage state.
+
+**Figure 15/Q.703 (sheet 7 of 7) – Preventive cyclic retransmission – Transmission control**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> Start1[/Start
+LSC → RC/]
+ Idle1 --> Retrieve[/Retrieve BSNT
+LSC → RC/]
+ Start1 --> Start2[/Start
+RC → DAEDR/]
+ Retrieve --> BSNTCalc[BSNT := FSNX - 1]
+ Start2 --> FSNXInit[FSNX := 0
+FIBX := 1]
+ BSNTCalc --> BSNTL3[/BSNT
+RC → L3/]
+ FSNXInit --> FSNFInit[FSNF := 0
+FSNT := 127]
+ BSNTL3 --> Idle2([Idle])
+ FSNFInit --> CancelFISU[Cancel FISU/MSU
+accepted]
+ CancelFISU --> CancelAbnormal[Cancel
+abnormal
+BSNR]
+ CancelAbnormal --> CancelCongestion[Cancel
+congestion discard
+and
+congestion accept]
+ CancelCongestion --> InService([In service])
+
+```
+
+Flowchart for Preventive cyclic retransmission - Reception control. The process starts at 'Idle' and branches into two paths. The left path goes through 'Start LSC -> RC', 'Start RC -> DAEDR', 'FSNX := 0, FIBX := 1', 'FSNF := 0, FSNT := 127', 'Cancel FISU/MSU accepted', 'Cancel abnormal BSNR', and 'Cancel congestion discard and congestion accept' to reach 'In service'. The right path goes through 'Retrieve BSNT LSC -> RC', 'BSNT := FSNX - 1', 'BSNT RC -> L3', and back to 'Idle'.
+
+T1156920-93
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 16/Q.703 (sheet 1 of 6) – Preventive cyclic retransmission – Reception control**
+
+
+
+```
+
+graph TD
+ InService1([In service])
+ InService1 --> Stop[Stop
LSC->RC]
+ InService1 --> FSNT[FSNT value
TXC->RC]
+ InService1 --> Reject[Reject
MSU/FISU
LSC->RC]
+ InService1 --> Accept[Accept
MSU/FISU
LSC->RC]
+ InService1 --> SignalUnit[Signal unit
DAEDR->RC]
+
+ Stop --> Normal[Normal
RC -> CC]
+ Normal --> Idle([Idle])
+
+ FSNT --> Update[Update
FSNT]
+ Reject --> Cancel[Cancel
MSU/FISU
accepted]
+ Accept --> Mark[Mark
MSU/FISU
accepted]
+
+ Update --> InService2([In service])
+ Cancel --> InService2
+ Mark --> InService2
+
+ SignalUnit --> IsLSSU{Signal unit
is LSSU}
+ IsLSSU -- No --> Conn2((2))
+ Conn2 --> Conn3((3))
+ IsLSSU -- Yes --> LSSUType{LSSU type}
+
+ LSSUType -- SIN --> SIN_LSC[SIN
RC->LSC]
+ SIN_LSC --> SIN_IAC[SIN
RC->IAC]
+
+ LSSUType -- SIE --> SIE_LSC[SIE
RC->LSC]
+ SIE_LSC --> SIE_IAC[SIE
RC->IAC]
+
+ LSSUType -- SIO --> SIO_LSC[SIO
RC->LSC]
+ SIO_LSC --> SIO_IAC[SIO
RC->IAC]
+
+ LSSUType -- SIOS --> SIOS_LSC[SIOS
RC->LSC]
+ SIOS_LSC --> SIOS_IAC[SIOS
RC->IAC]
+
+ LSSUType -- SIPO --> SIPO_LSC[SIPO
RC->LSC]
+
+ LSSUType -- SIB --> SIB_Rec[SIB
received
RC->LSC]
+
+ SIN_IAC --> InService3([In service])
+ SIE_IAC --> InService3
+ SIO_IAC --> InService3
+ SIOS_IAC --> InService3
+ SIPO_LSC --> InService3
+ SIB_Rec --> InService3
+
+ Conn1((1)) --> Conn5((5))
+
+```
+
+T1178390-96
+
+Flowchart for Figure 16/Q.703 (sheet 2 of 6) – Preventive cyclic retransmission – Reception control. The diagram shows logic paths starting from an 'In service' state. Paths include: 1) Stop (LSC->RC) leading to Normal (RC->CC) and then Idle state. 2) FSNT value (TXC->RC) leading to Update FSNT and back to In service. 3) Reject MSU/FISU (LSC->RC) leading to Cancel MSU/FISU accepted and back to In service. 4) Accept MSU/FISU (LSC->RC) leading to Mark MSU/FISU accepted and back to In service. 5) Signal unit (DAEDR->RC) leading to a decision 'Signal unit is LSSU'. If No, it goes to connector 2. If Yes, it branches by 'LSSU type' into SIN, SIE, SIO, SIOS, SIPO, and SIB paths. Each path has specific RC->LSC and/or RC->IAC actions before returning to In service. Connector 1 leads to connector 5.
+
+NOTE - See the abbreviations and timers used in this Figure in 12.2
+
+**Figure 16/Q.703 (sheet 2 of 6) – Preventive cyclic retransmission – Reception control**
+
+2
+
+
+
+BSNR in RTB or same as previous BSNR?
+(inequalities are expressed Modulo 128)
+
+```
+
+graph TD
+ 2((2)) --> D1{FSNF - 1 <= BSNR <= FSNF?}
+ D1 -- No --> P1[Discard signal unit]
+ D1 -- Yes --> D2{Abnormal BSNR?}
+ D2 -- Yes --> D3{UNB = 1?}
+ D3 -- Yes --> P2[Cancel abnormal BSNR]
+ D3 -- No --> D2
+ D2 -- No --> D4{Abnormal BSNR?}
+ D4 -- Yes --> P3[Link failure
+RC → LSC]
+ P3 --> O1([Idle])
+ D4 -- No --> P4[Mark abnormal BSNR]
+ P4 --> P5[UNB := 0]
+ P5 --> O2([In service])
+ P2 --> P6[FISU/MSU received
+RC → LSC]
+ P6 --> P7[BSNR
+RC → TXC]
+ P7 --> P8[FSNF := BSNR + 1]
+ P8 --> D5{MSU/FISU accepted?}
+ D5 -- Yes --> 3((3))
+ D5 -- No --> P9[Discard signal unit]
+ P9 --> O2
+ P9 --> P10[UNB := 1]
+ P10 --> O2
+
+```
+
+Flowchart for Preventive cyclic retransmission - Reception control. The process starts at connector 2, checks if FSNF - 1 <= BSNR <= FSNF. If No, it discards the signal unit. If Yes, it checks if it's an Abnormal BSNR. If Yes, it checks if UNB = 1. If Yes, it cancels the abnormal BSNR. If No, it checks if it's an Abnormal BSNR. If Yes, it leads to Link failure (RC -> LSC) and Idle. If No, it marks the abnormal BSNR and sets UNB := 0. If No, it sets UNB := 1. Both UNB := 0 and UNB := 1 lead to In service. If the initial FSNF check is Yes and it's not an Abnormal BSNR, it receives the FISU/MSU (RC -> LSC), sends the BSNR (RC -> TXC), updates FSNF := BSNR + 1, and checks if the MSU/FISU was accepted. If Yes, it goes to connector 3. If No, it discards the signal unit and goes to In service.
+
+T1177730-95
+
+3
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 16/Q.703 (sheet 3 of 6) – Preventive cyclic retransmission – Reception control**
+
+
+
+```
+
+graph TD
+ Start((3)) --> CD{Congestion
+discard?}
+ CD -- Yes --> DSU1[Discard
+signal unit]
+ CD -- No --> FSNR{FSNR =
+FSNX?}
+ FSNR -- No --> DSU2[Discard
+signal unit]
+ FSNR -- Yes --> SUMSU{Signal
+unit = MSU?}
+ SUMSU -- No --> DSU2
+ SUMSU -- Yes --> RM[/Received
+message
+
+RC → L3/]
+ RM --> FSNXINC[FSNX :=
+FSNX + 1]
+ FSNXINC --> CA{Congestion
+accept?}
+ CA -- Yes --> Busy[/Busy
+
+RC → CC/]
+ CA -- No --> FSNXV[/FSNX value
+
+RC → TXC/]
+ DSU1 --> InService([In service])
+ DSU2 --> InService
+ Busy --> InService
+ FSNXV --> InService
+
+```
+
+T1156950-93
+
+Flowchart for Figure 16/Q.703 (sheet 4 of 6) – Preventive cyclic retransmission – Reception control. The process starts at connector 3, leading to a 'Congestion discard?' decision. 'Yes' leads to 'Discard signal unit'. 'No' leads to 'FSNR = FSNX?'. 'No' leads to 'Discard signal unit'. 'Yes' leads to 'Signal unit = MSU?'. 'No' leads to 'Discard signal unit'. 'Yes' leads to 'Received message RC → L3', then 'FSNX := FSNX + 1', then 'Congestion accept?'. 'Yes' leads to 'Busy RC → CC'. 'No' leads to 'FSNX value RC → TXC'. All paths eventually lead to 'In service'.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 16/Q.703 (sheet 4 of 6) – Preventive cyclic retransmission – Reception control**
+
+
+
+1, 4
+
+2
+
+From unspecified implementation dependent function
+
+6
+
+1
+
+4
+
+```
+
+graph TD
+ 1((1)) --> Retrieve[Retrieve BSNT
+LSC → RC]
+ Retrieve --> BSNT_eq[BSNT =
+FSNX - 1]
+ BSNT_eq --> BSNT_rc[BSNT
+RC → L3]
+ BSNT_rc --> InService([In service])
+ 6((6)) -.-> DashedLine[From unspecified implementation dependent function]
+ DashedLine -.-> CongestionDiscard{Congestion discard}
+ DashedLine -.-> CongestionAccept{Congestion accept}
+ DashedLine -.-> NoCongestion{No congestion}
+ CongestionDiscard --> MarkDiscard[Mark congestion discard]
+ CongestionAccept --> MarkAccept[Mark congestion accept]
+ NoCongestion --> Cancel[Cancel congestion discard and congestion accept]
+ Cancel --> Normal[Normal
+RC → CC]
+ Normal --> FSNX[FSNX value
+RC → TXC]
+ MarkDiscard --> InService
+ MarkAccept --> InService
+ FSNX --> InService
+
+```
+
+T1131110-91
+
+Flowchart for Preventive cyclic retransmission - Reception control. The process starts at node 1, proceeds through 'Retrieve BSNT LSC -> RC', then 'BSNT = FSNX - 1', and 'BSNT RC -> L3'. A dashed line from node 6 indicates an unspecified implementation-dependent function. The main path continues from 'BSNT RC -> L3' to 'In service'. Along the way, there are decision points: 'Congestion discard', 'Congestion accept', and 'No congestion'. 'Congestion discard' leads to 'Mark congestion discard'. 'Congestion accept' leads to 'Mark congestion accept'. 'No congestion' leads to 'Cancel congestion discard and congestion accept', which then leads to 'Normal RC -> CC' and 'FSNX value RC -> TXC'. All three paths ('Mark congestion discard', 'Mark congestion accept', and 'FSNX value RC -> TXC') converge to 'In service'.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 16/Q.703 (sheet 5 of 6) – Preventive cyclic retransmission – Reception control**
+
+
+
+4
+
+```
+
+graph TD
+ Start((5
+4)) --> Step1[/Retrieve FSNX
+LSC → RC/]
+ Step1 --> Step2[/FSNX value
+RC → TXC/]
+ Step2 --> Step3[Cancel congestion discard and congestion accept]
+ Step3 --> Step4[/Normal
+RC → CC/]
+ Step4 --> End([In service])
+
+```
+
+T1142200-92
+
+Flowchart for Preventive cyclic retransmission - Reception control. The flow starts at a circle labeled '5' and '4'. It proceeds to a parallelogram 'Retrieve FSNX LSC → RC', then a parallelogram 'FSNX value RC → TXC', then a rectangle 'Cancel congestion discard and congestion accept', then a parallelogram 'Normal RC → CC', and finally an oval 'In service'. A vertical line with two parallel lines is on the left side of the flowchart.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 16/Q.703 (sheet 6 of 6) – Preventive cyclic retransmission – Reception control**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> Set1[Set to LSC → AERM]
+ Idle1 --> Start[Start IAC → AERM]
+ Idle1 --> Set2[Set to IAC → AERM]
+ Set1 --> Set3[Set to]
+ Set3 --> Idle2([Idle])
+ Start --> Ca0[Ca := 0]
+ Ca0 --> Monitoring1([Monitoring])
+ Set2 --> Set4[Set to]
+ Set4 --> Idle3([Idle])
+ Monitoring1 --> Stop[Stop IAC → AERM]
+ Monitoring1 --> SUerror[SU in error DAEDR → AERM]
+ Stop --> Set5[Set to]
+ Set5 --> Idle4([Idle])
+ SUerror --> CaInc[Ca := Ca + 1]
+ CaInc --> CaCheck{Ca := ?}
+ CaCheck -- Yes --> Abort[Abort proving AERM → IAC]
+ Abort --> Idle4
+ CaCheck -- No --> Monitoring2([Monitoring])
+ Monitoring2 --> Idle4
+ T1156960-93
+
+```
+
+Flowchart for Alignment error rate monitor. It starts with an 'Idle' state, branches into three paths (one returning to 'Idle', one starting monitoring with Ca=0, and one returning to 'Idle'), then from 'Monitoring' it branches into 'Stop' (returning to 'Idle') or 'SU in error' (incrementing Ca and checking a condition).
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 17/Q.703 – Alignment error rate monitor**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> Start[/Start
+LSC → SUERM/]
+ Start --> Init["Cs := 0
+su := 0"]
+ Init --> InService1([In service])
+ InService1 --> Stop[/Stop
+LSC → SUERM/]
+ InService1 --> SUinError[/SU in error
+DAEDR → SUERM/]
+ InService1 --> CorrectSU[/Correct SU
+DAEDR → SUERM/]
+ SUinError --> IncCS["Cs := Cs + 1
+su := su + 1"]
+ IncCS --> CsCheck{Cs := ?}
+ CsCheck -- No --> Circle1((1))
+ Circle1 --> CorrectSU
+ CsCheck -- Yes --> LinkFailure[/Link failure
+SUERM → LSC/]
+ LinkFailure --> Idle2([Idle])
+ Stop --> Idle2
+ CorrectSU --> IncSU["su := su + 1"]
+ IncSU --> SuCheck{su = 256?}
+ SuCheck -- No --> Circle2((1))
+ Circle2 --> CorrectSU
+ SuCheck -- Yes --> ResetSU["su := 0"]
+ ResetSU --> CsZeroCheck{Cs = 0?}
+ CsZeroCheck -- Yes --> Idle2
+ CsZeroCheck -- No --> DecCS["Cs := Cs - 1"]
+ DecCS --> InService2([In service])
+
+```
+
+Flowchart for Signal unit error rate monitor. The process starts at 'Idle', goes through 'Start' (LSC -> SUERM), initializes Cs := 0 and su := 0, and enters 'In service'. From 'In service', it branches into three paths: 'Stop' (LSC -> SUERM) leading back to 'Idle'; 'SU in error' (DAEDR -> SUERM) which increments Cs and su, then checks if Cs meets a threshold; and 'Correct SU' (DAEDR -> SUERM) which increments su and checks if su reaches 256. If su reaches 256, su is reset to 0 and the system checks if Cs is 0. If Cs is 0, it returns to 'Idle'; otherwise, it decrements Cs and returns to 'In service'. If the Cs threshold is met in the 'SU in error' path, it indicates a 'Link failure' (SUERM -> LSC) and returns to 'Idle'.
+
+T1156970-93
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 18/Q.703 – Signal unit error rate monitor**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> Busy1[/Busy
+RC → CC/]
+ Idle1 --> Normal1[/Normal
+RC → CC/]
+ Busy1 --> Circle1((1))
+ Circle1 --> SendSIB[/Send SIB
+CC → TXC/]
+ SendSIB --> StartT5[/Start T5/]
+ StartT5 --> Level2Congestion1([Level 2 congestion])
+ Level2Congestion1 --> Busy2[/Busy
+RC → CC/]
+ Level2Congestion1 --> Normal2[/Normal
+RC → CC/]
+ Level2Congestion1 --> T5Bar[/T5-bar/]
+ Busy2 --> Level2Congestion2([Level 2 congestion])
+ Normal2 --> StopT5[/Stop T5/]
+ StopT5 --> Idle2([Idle])
+ T5Bar --> Circle2((1))
+ Circle2 --> Normal3[/Normal
+RC → CC/]
+ Normal3 --> Circle1
+
+```
+
+Flowchart of congestion control procedure (Figure 19/Q.703). The process starts at 'Idle', transitions to 'Busy' (RC → CC) or 'Normal' (RC → CC) via a circle labeled '1'. From 'Busy', it goes to 'Send SIB' (CC → TXC), then 'Start T5', then 'Level 2 congestion'. From 'Level 2 congestion', it branches to 'Busy' (RC → CC), 'Normal' (RC → CC), or 'T5-bar'. 'Busy' leads to 'Level 2 congestion'. 'Normal' leads to 'Stop T5', which then returns to 'Idle'. 'T5-bar' leads to a circle labeled '1', which then returns to 'Normal' (RC → CC). The diagram is labeled T1156980-93.
+
+NOTE – See the abbreviations and timers used in this Figure in 12.2.
+
+**Figure 19/Q.703 – Congestion control**
+
+# ANNEX A
+
+## Additions for a national option for high speed signalling links
+
+## A.1 Introduction
+
+This Annex provides the additions to this Recommendation to support enhanced MTP Level 2 functions and procedures that are suitable for the operation and control of signalling links at data rates of 1.5 and 2.0 Mbit/s as a national option.
+
+### **A.1.1 Procedures for 1.5 and 2.0 Mbit/s data rate signalling links**
+
+The additions to this Recommendation presented below will use the numbering sequences, after the A., that correspond to the numbering in this Recommendation to facilitate the identification of those procedures.
+
+#### **A.2.3.3 Length indicator**
+
+The procedure for the length indicator remains as specified in 2.3.3/Q.703. If the extended sequence number format is used, then the length indicator will encode the length of the message, ranging from 0 to 273 octets.
+
+#### **A.2.3.5 Sequence numbering for 1.5 and 2.0 Mbit/s data rates**
+
+The existing Level 2 MTP format is used. Depending on the delay characteristics, the network operator may decide to use extended sequence numbers (12 bits). In this case, the forward sequence number and backward sequence number are in binary code from a cyclic sequence from 0 to 40956. (See clause 5/Q.703 and clause 6/Q.703.)
+
+---
+
+6 If extended sequence numbers are used, then the FSN value will not fit into the FSN field conveyed in MTP3 Changeover Order and Changeover Acknowledgement message types, therefore the MTP used should have the capabilities of Recommendation Q.2210.
+
+
+
+**a) Basic format of a Message Signal Unit (MSU)**
+
+| | | | | | | | | | | | | |
+|---|----|-----------|-----|-------|----|-------------|-----|-----|-------------|-----|-----|---|
+| F | CK | SIF | SIO | Spare | LI | F
I
B | Res | FSN | B
I
B | Res | BSN | F |
+| 8 | 16 | 8n, n ≥ 2 | 8 | 7 | 9 | 1 | 3 | 12 | 1 | 3 | 12 | 8 |
+
+First bit transmitted →
+
+**b) Format of a Link Status Signal Unit (LSSU)**
+
+| | | | | | | | | | | | |
+|---|----|---------|-------|----|-------------|-----|-----|-------------|-----|-----|---|
+| F | CK | SF | Spare | LI | F
I
B | Res | FSN | B
I
B | Res | BSN | F |
+| 8 | 16 | 8 or 16 | 7 | 9 | 1 | 3 | 12 | 1 | 3 | 12 | 8 |
+
+First bit transmitted →
+
+**c) Format of a Fill-In Signal Unit (FISU)**
+
+| | | | | | | | | | | |
+|---|----|-------|----|-------------|-----|-----|-------------|-----|-----|---|
+| F | CK | Spare | LI | F
I
B | Res | FSN | B
I
B | Res | BSN | F |
+| 8 | 16 | 7 | 9 | 1 | 3 | 12 | 1 | 3 | 12 | 8 |
+
+First bit transmitted →
+T1178370-96
+
+BIB Backward Indicator Bit
+ BSN Backward Sequence Number
+ CK Check bits
+ F Flag
+ FIB Forward Indicator Bit
+ FSN Forward Sequence Number
+ LI Length Indicator
+ n Number of octets in the SIF
+ SF Status Field
+ SIF Signalling Information Field
+ SIO Service Information Octet
+
+**Figure A.1/Q.703 – Signal unit formats for 1.5 and 2.0 Mbit/s rates**
+
+(extended sequence numbers)
+
+## A.4 Acceptance procedure
+
+### A.4.1 Acceptance of alignment
+
+The errored interval monitor is applied instead of the signal unit error rate monitor.
+
+**A.4.1.2** The octet counting mode is not used when a flag is lost.
+
+**A.4.1.3** If the extended sequence number format is used, then the check for the correct signal unit length is increased by 3 octets.
+
+### A.10.1 General
+
+When link data rates of 1.5 Mbit/s and 2.0 Mbit/s are used, the errored interval monitor is applied instead of the signal unit error rate monitor.
+
+### A.10.2 Errored interval monitor for 1.5 Mbit/s and 2.0 Mbit/s links
+
+**A.10.2.1** The errored interval monitor has as its function the estimation of signalling link fault conditions by monitoring errors over a prescribed interval to model the queue build up on the transmitting end. An interval is errored if one or more signal units are rejected by the acceptance procedure (see clause 4/Q.703), or a flag is lost. The four parameters that determine the errored interval monitor are:
+
+- the number of intervals where signal units have been received in error that will cause an error rate high indication to level 3, $T_E$ (intervals);
+- the constant $U_E$ for incrementing the counter;
+- the constant $D_E$ for decrementing the counter; and
+- timer T8, the interval for monitoring errors.
+
+**A.10.2.2** The errored interval monitor is implemented in the form of an up and down counter decremented at a fixed rate $D_E$ for every interval where no signal unit is errored, but not below zero, and incremented at a fixed rate $U_E$ for every interval where one or more signal unit errors are detected by the signal unit acceptance procedure (see 4.1.3) or where no flag is received but not above threshold $T_E$ . An excessive error rate shall be indicated whenever the threshold $T_E$ is reached.
+
+**A.10.2.3** The octet counting mode, which provides an estimate of a signal unit, is not used for the errored interval monitor, because this procedure is not based on an accounting of individual errors.
+
+**A.10.2.4** When the link is brought into service, the monitor count shall start from zero.
+
+**A.10.2.5** The values for the four parameters of the errored interval monitor are given in Table A.1.
+
+**Table A.1/Q.703 – Values for the errored interval parameters**
+
+| Parameter | Definition | 1.5 Mbit/s links | 2.0 Mbit/s links |
+|-----------|----------------------------|------------------|------------------|
+| $T_E$ | Threshold count | 577.169 | 793.544 |
+| $U_E$ | Constant for upcount | 144 292 | 198 384 |
+| $D_E$ | Constant for downcount | 9308 | 11 328 |
+| T8 | Monitoring interval (msec) | 100 msec | 100 msec |
+
+### A.10.3 Alignment error rate monitor
+
+The procedure in 10.3/Q.703 is applicable, except that the octet counting mode is not used.
+
+### A.12.3 Timers
+
+The timer values that are changed for these high speed signalling links are as follows:
+
+| | | |
+|----|---------------------------------|---------------------------------------------------------------------|
+| T1 | | Timer "alignment ready" |
+| | $T1 = 300$ s (range 25 - 350 s) | Bit rate of 1.5 and 2.0 Mbit/s |
+| T4 | | Proving period timer = $2^{16}$ or $2^{12}$ octet transmission time |
+| | $T4n = 30$ s (range 3 - 70 s) | Normal proving period at 1.5 and 2.0 Mbit/s |
+| | $T4e = 400 - 600$ ms | Emergency proving period at 1.5 and 2.0 Mbit/s |
+
+
+
+```
+graph TD; Idle([Idle]) --> Start{Start}; Start -- "LSC -> EIM" --> CE["CE := 0"]; CE --> CIM[Cancel interval monitor]; CIM --> CSU[Cancel SU received]; CSU --> StartT8{Start T8}; StartT8 --> Monitoring([Monitoring]);
+```
+
+T1177550-95
+
+Flowchart of the errored interval monitor process. The steps are: Idle (oval), Start (diamond) with LSC -> EIM, CE := 0 (rectangle), Cancel interval monitor (rectangle), Cancel SU received (rectangle), Start T8 (diamond), and Monitoring (oval).
+
+**Figure A.2/Q.703 (sheet 1 of 2) – Errored interval monitor for 1.5 and 2.0 Mbit/s links**
+
+
+
+```
+
+graph TD
+ Monitoring1([Monitoring]) --- BranchPoint[ ]
+ style BranchPoint width:0px,height:0px
+
+ BranchPoint --- Stop[Stop
+LSC → EIM]
+ BranchPoint --- T8[T8]
+ BranchPoint --- CorrectSU[Correct SU
+DAEDR → EIM]
+ BranchPoint --- SUinError[SU in error
+DAEDR → EIM]
+
+ Stop --> Idle([Idle])
+
+ T8 --> StartT8[Start T8]
+ StartT8 --> SUreceived{SU
+received?}
+
+ SUreceived -- No --> CE_U[CE := CE + U]
+ SUreceived -- Yes --> CancelSU[Cancel
+SU received]
+
+ CancelSU --> IntervalError{Interval
+error?}
+
+ IntervalError -- No --> CE_D[CE :=
+max(0, CE – D)]
+ IntervalError -- Yes --> CE_U
+
+ CE_U --> CancelInterval[Cancel
+interval
+error]
+ CancelInterval --> CEGT{CE > TE}
+
+ CEGT -- No --> MonitoringEnd([Monitoring])
+ CEGT -- Yes --> LinkFailure[Link
+failure
+EIM → LSC]
+
+ LinkFailure --> Idle
+
+ CE_D --> MonitoringEnd
+
+ CorrectSU --> MarkSU[Mark
+SU received]
+ MarkSU --> MonitoringEnd
+
+ SUinError --> MarkError[Mark
+interval error]
+ MarkError --> MonitoringEnd
+
+```
+
+T1177560-95
+
+Flowchart for an errored interval monitor. It starts at 'Monitoring', branches into 'Stop LSC -> EIM', 'T8' (Start T8), 'Correct SU DAEDR -> EIM' (Mark SU received), and 'SU in error DAEDR -> EIM' (Mark interval error). The 'Start T8' path leads to 'SU received?' (No/Yes). 'Yes' leads to 'Cancel SU received' -> 'Interval error?' (No/Yes). 'Yes' leads to 'CE := CE + U' -> 'Cancel interval error' -> 'CE > TE' (No/Yes). 'Yes' leads to 'Link failure EIM -> LSC' -> 'Idle'. 'No' from 'Interval error?' and 'No' from 'CE > TE' lead to a common 'Monitoring' end. 'SU in error' also leads to this 'Monitoring' end. 'Correct SU' leads to 'Mark SU received' -> 'Monitoring'.
+
+**Figure A.2/Q.703 (sheet 2 of 2) – Errored interval monitor
+for 1.5 and 2.0 Mbit/s links**
+
+# ITU-T RECOMMENDATIONS SERIES
+
+- Series A Organization of the work of the ITU-T
+- Series B Means of expression
+- Series C General telecommunication statistics
+- Series D General tariff principles
+- Series E Telephone network and ISDN
+- Series F Non-telephone telecommunication services
+- Series G Transmission systems and media
+- Series H Transmission of non-telephone signals
+- Series I Integrated services digital network
+- Series J Transmission of sound-programme and television signals
+- Series K Protection against interference
+- Series L Construction, installation and protection of cables and other elements of outside plant
+- Series M Maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits
+- Series N Maintenance: international sound-programme and television transmission circuits
+- Series O Specifications of measuring equipment
+- Series P Telephone transmission quality
+- Series Q Switching and signalling**
+- Series R Telegraph transmission
+- Series S Telegraph services terminal equipment
+- Series T Terminal equipments and protocols for telematic services
+- Series U Telegraph switching
+- Series V Data communication over the telephone network
+- Series X Data networks and open system communication
+- Series Z Programming languages
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/028803093e6d1195c9c470b0abd490c6_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/028803093e6d1195c9c470b0abd490c6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..950ea1fb958d07e9063b9c34c638c3cbcd68dba1
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/028803093e6d1195c9c470b0abd490c6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c02355704f7728eab181ccff5c948b667a45fc21b30b96611c4133b3bb299c4d
+size 120525
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/0317016f1967843fe2643d09bd7bee9d_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/0317016f1967843fe2643d09bd7bee9d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..efa02e3917e5e385138567372cbcb6af2821255d
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/0317016f1967843fe2643d09bd7bee9d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:457c1056cfc68f6d4d272451a17eb7aeeb6ed9176b0ba9f25b9d2fda33a83f8b
+size 71490
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0b0f6945902289167992a8d54ae85af8db72eaa5
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:468a0c1eceee87e471c43531f94990e70a5508881e4894beab0d8a73cbed2fbe
+size 97086
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fb1819bf9649fbe0a9d5b4a60eb537312a4cc1ea
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/043e64d41a3368d138ace3816fd26469_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cb73b827e6963f45f379823db1736b3c3ed25e8bc295c35d046e4b1cddba78cd
+size 123334
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/050e982c5a050f0d6bc92975d0ba27ab_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/050e982c5a050f0d6bc92975d0ba27ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c9771416eb5fe7961bdc1829a220fb4c0a7701af
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/050e982c5a050f0d6bc92975d0ba27ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8bce82cf81fb21ee8c0ed56213bf30c79f0cd7ab1cd7663db221376bc337e09f
+size 175552
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..28f9372816ff4fb4b22d0b595f4b72bbf0de43fd
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3620283ec73f8d193af6cf344871c78cf8068c7bf689b5c5488f0e5ce50ce4bc
+size 137931
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/09797d4289ec96309d21a9a993153dab_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/09797d4289ec96309d21a9a993153dab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..15255d40a4fbcf1ff028d7a7e4c5aa8c5b5a88c6
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/09797d4289ec96309d21a9a993153dab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d2a9c5cc1fbf14f80173471f796071a9692fd11deb1783908d3c23319fc3bc32
+size 88491
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/0ab0282f295c2fcf97b7197e7aeb1381_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/0ab0282f295c2fcf97b7197e7aeb1381_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fd26e5401c2cd26af494589b0da2c4599db3cb92
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/0ab0282f295c2fcf97b7197e7aeb1381_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:67d9a717f95ed06319edb679d9589a5d67dd62b2ff6b5b8d44e32ecbe6928105
+size 104116
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/0f007a07756791edf7be50672cb010a4_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/0f007a07756791edf7be50672cb010a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..15ba8478805ed033c5be9e295630b2c402759a97
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/0f007a07756791edf7be50672cb010a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8e2f39b51dd5b009694e84c0bf72d59f23c162abd089c842c1fc8c824e489512
+size 98574
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/0fdef87ff1fd322c626d1ff8df725749_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/0fdef87ff1fd322c626d1ff8df725749_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2a70dd772aacbde7253c79ada890154c6b7f1d70
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/0fdef87ff1fd322c626d1ff8df725749_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:77fe950f8debcd6ad9da96215fc10590f30d8bb3602c8e24dad5905533e69181
+size 100993
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/12280970bb3eea7f6fbdc08200d444c2_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/12280970bb3eea7f6fbdc08200d444c2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b67824272b80c8ed4ba72ad162ff51f3d9ba355e
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/12280970bb3eea7f6fbdc08200d444c2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:08602a0e89a6f82043d4262ce81dd2974e1fbb85d9caec75b00a521ff0fabd6e
+size 118421
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/130b3107ad97fbf300d3562dab05285b_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/130b3107ad97fbf300d3562dab05285b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bf8a3fd53263426ef36987fdd99d997922c87ccd
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/130b3107ad97fbf300d3562dab05285b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2db25491119670a4f338d3d11f7a002ba9cb2473ff23cb053cc1827ccea8fb61
+size 177730
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/130e5cca4d4856272e57a0247d14e094_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/130e5cca4d4856272e57a0247d14e094_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..873d36d3b27e970b7a7335de3d365cf9b3ca58b0
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/130e5cca4d4856272e57a0247d14e094_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:56dcc6bcdfa02d05a11397cadd087377dcf59e77b28d70658a34a1c6a49a93d8
+size 144143
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..49329350f92729b50a494661a8eae5be041a5f74
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/13fde41de77bf026013a0b81684d1fc9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:322c063c05f77a99449b1cd6538da628600e626be2657230f3de9dcaca55db08
+size 13666
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/1922717e4a5ef189ba4572ea65b2f0ae_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/1922717e4a5ef189ba4572ea65b2f0ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9f3ff5b158be9335fd7018bb59f2e8b807dffbb8
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/1922717e4a5ef189ba4572ea65b2f0ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:59196308441fe6455ce2ef0dd7b62846454214bcf247920cc7dd97320764cb3d
+size 134411
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/199607ec43a5b7ad43b1896e152e742b_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/199607ec43a5b7ad43b1896e152e742b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f7da1e021a8b0bbc0fc815c3f25e49f9f5da02a5
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/199607ec43a5b7ad43b1896e152e742b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e7284c7a59b66c7580b337a390663057351c09fca1d58bd44b7ded193c4f60c8
+size 74557
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/1ab8da167ae10f58b4b0b57e0c1283ad_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/1ab8da167ae10f58b4b0b57e0c1283ad_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b83f6914c744edf5d6bada265dced58a8081da64
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/1ab8da167ae10f58b4b0b57e0c1283ad_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:48aaa68c1aba1a502731766326af3a4ebdc8116a6026a268c8fe3b1a0332af71
+size 163136
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/1d62ade6b682fdfb8e192d10a06246a4_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/1d62ade6b682fdfb8e192d10a06246a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0cf50e5aa48c77d637d23f6286cc37fa28bc9264
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/1d62ade6b682fdfb8e192d10a06246a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02b842aa7d7e3f632c05180ad74d660c72dd661d7c11c0f75e792644ebc4a593
+size 150382
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/21ea5add6a61cc951b5c43ddffefb3ff_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/21ea5add6a61cc951b5c43ddffefb3ff_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2ca083250ee9a38f889eaeb6775f062eff6afd5b
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/21ea5add6a61cc951b5c43ddffefb3ff_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1b6e381a46a06220c22121f603841b1ad89cb19558c0b65916d430d81c273772
+size 100044
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/25b2ef5bcf30bfa9a31d59f48fddb3a7_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/25b2ef5bcf30bfa9a31d59f48fddb3a7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..09f3e4a371b58ba73b113d095d8473aabf2127cd
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/25b2ef5bcf30bfa9a31d59f48fddb3a7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:68b668f3c9b9083b0f3ba8d6ed62ef81403a7ab36a9f969d64b91fe00de9828d
+size 75313
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/26d6d8d333f84acff82b7a9f9b303da6_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/26d6d8d333f84acff82b7a9f9b303da6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..828c9f95b8d928be4358ad6077dde0ab142a1150
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/26d6d8d333f84acff82b7a9f9b303da6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:61cdd19b3dc7c76b97a391403a6abfd25b7347f04de0c7be08792b512a7bfceb
+size 63503
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/284768c5ee1a05aa1b9ce396f606a040_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/284768c5ee1a05aa1b9ce396f606a040_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..061ac66ec757135df02805428e20b4095b0ed7ac
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/284768c5ee1a05aa1b9ce396f606a040_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:971676c574bc1e32ecbe298b5b94aba84315fa197106efd492bbf0eb59bd9e3f
+size 88575
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/28e47e64ac18ca4d8924dab65cedc2d8_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/28e47e64ac18ca4d8924dab65cedc2d8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8da258f558f094e52b3753effea91b8d55e7109c
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/28e47e64ac18ca4d8924dab65cedc2d8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e5f1cda4980934eaaf1a1d6cd51de63cd2f559f61b610ec0e693526c7229f097
+size 70926
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/29aa6165ccf449dee0b4335676fa7b1a_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/29aa6165ccf449dee0b4335676fa7b1a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3b862887b3a6635d912c07e3c094a03eb24c5bbe
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/29aa6165ccf449dee0b4335676fa7b1a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f5152d5ab1a7d2db05bceaec666dcf529817c71d577eef247336eca5afaf638c
+size 78843
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/2cc98b619abc7a0e53aac9c44226ca89_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/2cc98b619abc7a0e53aac9c44226ca89_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bf57bcfbb1defddd470470a506cc088027638bea
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/2cc98b619abc7a0e53aac9c44226ca89_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:84aa1084b2af3d5832759164901704637b782655bc2eeaa4a9d478b0440c5644
+size 70956
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..597350198bf183a462cef91611cc21dc746957d4
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:30a6e102b1da0d13af03d660db963eef109c7d460e75a8e2594ffa6362039a83
+size 8212
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/2fa686ed8033ac35efddee0c7be47d59_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/2fa686ed8033ac35efddee0c7be47d59_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..afbedfbae433cf928a4d3739eec8caca707bf054
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/2fa686ed8033ac35efddee0c7be47d59_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:735f869f40b11a14805eea3d2dabd896f138f93f3d6314b406c7cbe875f89849
+size 84875
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/301f4a188198a15b1415d54545b07e0d_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/301f4a188198a15b1415d54545b07e0d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6c249feb49ab71407c52a0c98dce70d7c7438ada
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/301f4a188198a15b1415d54545b07e0d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b0df70349c8af1423775eef91c8a54b1559fba9dcf7ffe2be2f614f4681e893
+size 153332
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/3100b9f8708f586e472f3d9e44f10e52_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/3100b9f8708f586e472f3d9e44f10e52_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c741d6fde97a2d669e6027922f6769916ab11b29
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/3100b9f8708f586e472f3d9e44f10e52_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc9144377a6c67c0eac4778d4efd9cc1ecc8b2d73e692cf837163f692e1b9eef
+size 32949
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/33d95af6c9ade7cf0415756cc5ea9803_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/33d95af6c9ade7cf0415756cc5ea9803_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..44b2ec811b88a88bb3d858b3b4a736460a427d6c
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/33d95af6c9ade7cf0415756cc5ea9803_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa2fab7f27304974154c2829f993d31eb4f7e3621ed9c071d2fb0de3d5619fc6
+size 121283
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/3481cde1adf61b0452dd6489dada6d6a_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/3481cde1adf61b0452dd6489dada6d6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4445cc26a984ed86b0f4165b4f0d22bf6fcee759
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/3481cde1adf61b0452dd6489dada6d6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a1c98c1bf52cb0fa83ed20e7f935de79a582f74f9091d32e33bc249cdf8b0fbb
+size 82643
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/37806e0fc150d857046ebc7e47893d7a_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/37806e0fc150d857046ebc7e47893d7a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4ddac38e547bd22bf673e75e9a078d3773e11657
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/37806e0fc150d857046ebc7e47893d7a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4c58e09ffce7684ec06c9ca062a25113abe14a648d7120a780cc66c1d76300c0
+size 24926
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/384ca4ed072674dbb16642cd334b1c15_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/384ca4ed072674dbb16642cd334b1c15_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3f1b3b66ed58b531ecc50569299cc88e0ffc7126
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/384ca4ed072674dbb16642cd334b1c15_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3a956d5f89d1522fab0c23c77d1f49f77ce0546973d9b494c2a4354adf8ad360
+size 19065
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/38f40809bd67962bd0ab172bff2239fd_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/38f40809bd67962bd0ab172bff2239fd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3dab78cdddc3903865358eeb2f687020be48ec1f
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/38f40809bd67962bd0ab172bff2239fd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:05d56af6c70f0880424e26f94ba58aa1ea4bc0359d093ef467cc81c227233290
+size 166144
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/3a006a7c9c9934695f0fc731344eff8a_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/3a006a7c9c9934695f0fc731344eff8a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0bcd622e77ee328836430896a7d12e9d04a1ec54
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/3a006a7c9c9934695f0fc731344eff8a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d55aa31f9f25377bcaace7d4bc14d8ef3a38710694820e2aca1007947c1df22d
+size 75324
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/3c721884a92b102becb43b52f6110e47_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/3c721884a92b102becb43b52f6110e47_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..343228c248a92958e6e54ed5cb0aa95bec346dd0
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/3c721884a92b102becb43b52f6110e47_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e0bab6f114850668375335af36df1a42af9e6c178157997ae029af7c18156e49
+size 54751
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/3ce6b213ec556257e32ff7451182369d_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/3ce6b213ec556257e32ff7451182369d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2b409279e00ea69551ff89e89c602cd7e2fb0a3f
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/3ce6b213ec556257e32ff7451182369d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:addbf902f087bc12d006c2bd6d192176b8006925655b2b314f7e9aea29a2bae3
+size 179262
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/3eb2af31c2e61e2595c8440d726f5d4e_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/3eb2af31c2e61e2595c8440d726f5d4e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dcb08a6ff2190cc42fcfcb1e33adb66769eca7db
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/3eb2af31c2e61e2595c8440d726f5d4e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b008b6b725731bee411497d90e956f60abcbcf2c9c15163dd9e43c00ad948f1b
+size 138171
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/3f1b6583b85a3ffee7d3341f131a657c_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/3f1b6583b85a3ffee7d3341f131a657c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36709b39957a0ee497a526b565b722c9184734ef
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/3f1b6583b85a3ffee7d3341f131a657c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1d9168eef2ed4237b4ca8bd4cc9ab243034b90e6ddd6021010d2d9b230b0c4d
+size 95740
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/40d0aaaa3afa0a9fabe637941ca250bb_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/40d0aaaa3afa0a9fabe637941ca250bb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b0bd6c2e75bd782e2e3e37ea8a2107663e9dee55
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/40d0aaaa3afa0a9fabe637941ca250bb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1ba8a6ba7e18c1d4386a8fb3d594300b0489951ef3523a27261abb4bcf851dc9
+size 162907
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/426a0ab9454f31706038a0ac0bc37b9c_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/426a0ab9454f31706038a0ac0bc37b9c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b38807267f633cf22dddc98b45fd5d1e97ad8465
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/426a0ab9454f31706038a0ac0bc37b9c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ddf4779511673a7008dca05152d5e5a13e464dec542b485aa3ae21ab2258def
+size 78589
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/43f7b6b61db9a2f3e3920740a9527d97_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/43f7b6b61db9a2f3e3920740a9527d97_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e97a28a6415cee959866e307e17fcee4f3911019
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/43f7b6b61db9a2f3e3920740a9527d97_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:87eba9638641147d4151ab89fb37472eac74142c43873fa629bbfadc1b4aca22
+size 122600
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/4540c7355b250cb891be0b54b0ba25c7_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/4540c7355b250cb891be0b54b0ba25c7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c19fe6db5d13840d0fc687d94960acc4ebd3e892
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/4540c7355b250cb891be0b54b0ba25c7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc25a34b299b011c583468d420a49a91f7bdda688e23254938778570b066935c
+size 28394
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/4562b7df9e2e257eac16ccb0e5eb8932_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/4562b7df9e2e257eac16ccb0e5eb8932_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..305f1f7aa0e4a3c3a28d7930b31c8441ae562034
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/4562b7df9e2e257eac16ccb0e5eb8932_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d5274826ff94e343e8f19c4bd52539aabf9a2bdf4ec27155b3ca9bc399670395
+size 39145
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/46b6ae100e671c34c024598495e56c99_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/46b6ae100e671c34c024598495e56c99_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a2118c753f214d7d1c9e21cf49f062046957b71f
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/46b6ae100e671c34c024598495e56c99_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8d1056b8015e2a0a0152caf49a118faed2bf7bd49d1737d5d27b877b037b7a94
+size 78724
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/4851479cde0f63d07f4db536c69bbdef_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/4851479cde0f63d07f4db536c69bbdef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f4eed257af599f68089f289c5aaa3e9d7513d28e
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/4851479cde0f63d07f4db536c69bbdef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:846ebc0abd56b1fd06524e07b0e49725b80b8f7a4e1a62b0cf6971ec0643b04c
+size 118895
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/49d7bfbc65a92a7e1bd61777326a212d_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/49d7bfbc65a92a7e1bd61777326a212d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a9743e8436d4d846ada6452cd8bee633707365f7
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/49d7bfbc65a92a7e1bd61777326a212d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e076945191a264bcb2ecab2a6d67d4d5f01a1d85812179c45cb47bb49653e4e5
+size 130378
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/4aeaa51a3999fab21171224e238cb571_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/4aeaa51a3999fab21171224e238cb571_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aca80b6a928a26b761b7175d8e063e42b7430768
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/4aeaa51a3999fab21171224e238cb571_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:85e4747dcf082f85da0d0bded4ab1443333323b5334e24378d4427b6a283afb3
+size 18667
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/4c4cd9cc5afb43f9e3111e1ba45e701a_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/4c4cd9cc5afb43f9e3111e1ba45e701a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..32c8d8033b4c6fc28fa0562592150732ffc434b2
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/4c4cd9cc5afb43f9e3111e1ba45e701a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3b2bdf1f1fb9e6ae215edb785e3645bb38f1392f8e4664953616601017e71471
+size 93620
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/4ef412e08808c40e0beb7808d36b9379_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/4ef412e08808c40e0beb7808d36b9379_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e312631fd23a8747fcf24ba9fdb20c8a54cf5bcb
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/4ef412e08808c40e0beb7808d36b9379_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:724a93e099b7451c3bf2d52f9df606427d79ff8a46dc69b208ddb22650376637
+size 103130
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/52ed951cbf3a5e682e913881bc0d13c5_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/52ed951cbf3a5e682e913881bc0d13c5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a5fec68134ef3d015f505adb4fb52d0c3018c3b3
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/52ed951cbf3a5e682e913881bc0d13c5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:18756dafdac2fde769310c2eef0198d8c1f6a356186636bcaff131cb22999287
+size 109286
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/54f73f693f36dcbd300fa21ac4e410e8_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/54f73f693f36dcbd300fa21ac4e410e8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3f339fe710bf377f2f063b9545c2bbec35ea463c
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/54f73f693f36dcbd300fa21ac4e410e8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8375b3244638cf03efc592fe6e7dc87bef757221325c4177f37ec099da6b67dc
+size 156729
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/55f11fbbe5ef616ee7a1814f932acbaa_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/55f11fbbe5ef616ee7a1814f932acbaa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ecad047fa7799edbaa30abba15beb0eebca430fc
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/55f11fbbe5ef616ee7a1814f932acbaa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:78acf531f22f1cccbd7b7bedb393a2806941b7fbda5e993b37ecf0276bb90956
+size 113518
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/5c690861d263afceef4f7ab56ab13264_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/5c690861d263afceef4f7ab56ab13264_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..694b89ec17205ce53a378eda2fc76acb7ce97abb
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/5c690861d263afceef4f7ab56ab13264_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d088c1f700f2ff13dffcde34fe63f5c774b66f6e35f677d3f9ad2a4196db1b0c
+size 38987
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/5c78294af0232beec48c3b98db1d0cfa_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/5c78294af0232beec48c3b98db1d0cfa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..21c556ee540e84dd998e603a1a312d41c0ed75c0
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/5c78294af0232beec48c3b98db1d0cfa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02524c37e438160485d25862eebe9dfe6377122f5bae85168591a85d54a4d674
+size 80992
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/5cc9a312ebe733ae244e3b93cfea67e1_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/5cc9a312ebe733ae244e3b93cfea67e1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bdf58db1a314d2701d04442d6c576d64de777cd3
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/5cc9a312ebe733ae244e3b93cfea67e1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8f4fbe0718f66251b30672fc8fbb57f7f51308166f78ce29e1b3bf39f34fba81
+size 133956
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/5ec2b6e9c9133bfbb26789d85dc49774_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/5ec2b6e9c9133bfbb26789d85dc49774_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..41199e9c2e8b550ea168c07d68e491e2fa9c113c
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/5ec2b6e9c9133bfbb26789d85dc49774_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1256bf5d26d5aeaa7419edbbcf9fd6e66c92bd5218d0de2066bbc6f1d51c3b6
+size 25828
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/633486b12958f97e062b5cf9e0801e99_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/633486b12958f97e062b5cf9e0801e99_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5e74c9b8bca3008eb088d7f7165761246fcd830e
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/633486b12958f97e062b5cf9e0801e99_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ca743f33d963d972dd441dbc50b65114d599dd933a6fd7eec847243ed3d7bc25
+size 32514
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/64323b705244afc70bf77babdacb6ce5_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/64323b705244afc70bf77babdacb6ce5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bf2a8d3ed181a157a60f39b9777a08f023426b8e
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/64323b705244afc70bf77babdacb6ce5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d71589334d81b18dfbc85d5f0d48579e8e9529f0d09c8b70a18b1e139be37d12
+size 20366
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/669c88c4149a2add62ce1cbc7e8bb659_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/669c88c4149a2add62ce1cbc7e8bb659_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..418aa48b9445d70ba587830cae8e516812abad66
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/669c88c4149a2add62ce1cbc7e8bb659_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3e862da3e56f4999d4c582f379fdf9dcff1867c709a85eb71930f42d7639bb15
+size 64962
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/6726e50ea08adfda77603ec4afa549e1_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/6726e50ea08adfda77603ec4afa549e1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aef535277a96ba634def049c752919e8a614be1d
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/6726e50ea08adfda77603ec4afa549e1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:98f7140846b2101b2d39f8c809eadf53352280eae46330a456e04f12bb214c0f
+size 100881
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/6762c05f927b2b9c2404c465ef0a8d01_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/6762c05f927b2b9c2404c465ef0a8d01_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..647b6e366128afac19c423831c89e7c097f7a500
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/6762c05f927b2b9c2404c465ef0a8d01_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:711cb332ce4f9dad30c52886a59ecd5de72025f941b6a11ca4706129fc69ebce
+size 118058
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/68b20651884fcd557e865537f0803de5_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/68b20651884fcd557e865537f0803de5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..27e84b96f2b07c250ff2e78cfa7e5ec0f81bdb2a
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/68b20651884fcd557e865537f0803de5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:58a30056b73123aff327dc2aa235f27a19cc732891a00213d48f749f3bbf668f
+size 285729
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/6ca842602b0473809416a9cf0d4106a4_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/6ca842602b0473809416a9cf0d4106a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1b26fbe6ec638841e5e0fbe994a8d98b76b10659
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/6ca842602b0473809416a9cf0d4106a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:05c97a21f86cf27f0c41cbfeb252c0df5daa27eed9be3bf4c66338501a09f033
+size 128000
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/6e15fc9ea763541c5913d26f85072ae1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a00a43db1d8573da3853c86131b1181a575b4b72
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/6e15fc9ea763541c5913d26f85072ae1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:30f8d17795479afce0f8e0eedce7b885362de48d03f71f536285bc7bf945f1d3
+size 39365
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/6e30434e24bb6d94869199fec410fea4_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/6e30434e24bb6d94869199fec410fea4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a1209f28a56f62d016bb644a48a88cf32297bbae
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/6e30434e24bb6d94869199fec410fea4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c5c735ab0c769d6063c248de04047f785ade9f73474b9f738a95143e95329b26
+size 78127
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/6e3f478cc692027abd35e473223d677e_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/6e3f478cc692027abd35e473223d677e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..86c65d61be142fc014a9c6eb146822724cdb0e73
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/6e3f478cc692027abd35e473223d677e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:398a6de889c1a6d3b4eab21907f575766f67024b408c74dca11f0dec8c61c91a
+size 123506
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/773bb1698c96c3aea54d138ddcc7cfd5_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/773bb1698c96c3aea54d138ddcc7cfd5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36e5a065ad8a3c51b82a818eb38bc3abe03cd763
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/773bb1698c96c3aea54d138ddcc7cfd5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6f986e5db64024b09111947429815e9f6597e6b68e12e436c229487c57819054
+size 130555
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/792a3e6edb8dc2fc545f0782d6b4d3f7_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/792a3e6edb8dc2fc545f0782d6b4d3f7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..58d832d99f793ee589f7529068f9c1370a4e80ed
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/792a3e6edb8dc2fc545f0782d6b4d3f7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:32b83d4dc970cd52f98536bc356659f9dfdaecb21ade15ded3db524a7894a0af
+size 167820
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/79403f771ea4876ca26ecee2f288b1d1_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/79403f771ea4876ca26ecee2f288b1d1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..82f11c866b1b02ed3b7cd67f6bd59eb00a0ae95b
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/79403f771ea4876ca26ecee2f288b1d1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4f0b3b338c0dce0f1467bc9c80749b61411f0f02bec70518736c46251c56f7c1
+size 165892
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/79e37b4f8cee1318b5ed68e32a2f12a4_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/79e37b4f8cee1318b5ed68e32a2f12a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8e8d17d456067d67f1be6981a07af2534675395c
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/79e37b4f8cee1318b5ed68e32a2f12a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:605c115de7a734c30e1a711307a28911a630f08b74e452e326d77852214d84a7
+size 38124
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/7a0750f26d97d22b11aca5bbce495726_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/7a0750f26d97d22b11aca5bbce495726_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a2cd96fcc377cb87e6f781920ce3c1a974e7f2d9
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/7a0750f26d97d22b11aca5bbce495726_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7901d5034971d76755776294a30709fb4306f1a7c3efff3d83142d86fe015a4d
+size 178571
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f36c30abc775fb6467bd8c52eb0bed972d11a98b
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e03897625231dc07ba1c2240dae54c30809cca7f50ed6e042f112b0b6675a99a
+size 25965
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/7d1b7ee3543f5a1a9b7ad98572d52f85_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/7d1b7ee3543f5a1a9b7ad98572d52f85_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7e4fdd0f38802e54cbfa0daebaf27b66534d8ea1
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/7d1b7ee3543f5a1a9b7ad98572d52f85_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ef354804d3c8b32034498fa6aa26d9d0d9fd47395855bf2c67086e6f3ae1c9df
+size 36890
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/7e1f88e0cc7be8060240e12252a833d1_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/7e1f88e0cc7be8060240e12252a833d1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..68fcfc21da3a50112531d3a0fa5b275ddea86257
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/7e1f88e0cc7be8060240e12252a833d1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:030839aed4c1339d1f3c267216b401ce3d8138ba60d011bc6e81ddb62c71ace2
+size 107573
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/8159756d3acf4761a73fa0d263f1d338_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/8159756d3acf4761a73fa0d263f1d338_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..912d39822b8bb5160580b22fa0bb6e8f1a090d20
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/8159756d3acf4761a73fa0d263f1d338_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fe2eb4ec362be7a9754fc14f13b120d06b53ce2fa625b5174fd24a717e44ed70
+size 104670
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/8181865f1fd5e629dbe12ed89d22dc83_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/8181865f1fd5e629dbe12ed89d22dc83_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7a93de4cc57bc4348860872405039e352de5f7df
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/8181865f1fd5e629dbe12ed89d22dc83_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b606acaf1f78083f4cee1728c3318a323748b2c97e53df84b55396d6006790d6
+size 110391
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fe2a26f907996f306eedf27235b967dff2a4d425
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ca20530972300ee55283628a6287bb224bb35d03c2664d7db382a3a7146785a5
+size 24199
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/845e014e3b8677eb735d0e21f21206be_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/845e014e3b8677eb735d0e21f21206be_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b9a7cb269bed1234b1a5dacf112b96e66f79f2dd
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/845e014e3b8677eb735d0e21f21206be_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2fc3169e3f4085f71ee71189dd99865a4adf5abe7edfbd6adad9f8a239683346
+size 133267
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/88c92858439684b2103e88cb143fb98e_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/88c92858439684b2103e88cb143fb98e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3f8a78fe384a589bb878016049a21c5ef4c42f75
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/88c92858439684b2103e88cb143fb98e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2dc61090bdaddb6a96e856b923cb904693174daccaf5a6b86066576dac8a2941
+size 172656
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ce9af30a486bd0daeb06cb56dc94dcc2697bfa5a
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8877bb5a9114b939c27852266df65f05f481e8b9e0610e50ace49bb3c4205d14
+size 160122
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/92e26d86c5a582766cb9afdbd2c1aee7_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/92e26d86c5a582766cb9afdbd2c1aee7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3c34161e8b1fe850a08aab5ee2106bd5cc2cbc1d
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/92e26d86c5a582766cb9afdbd2c1aee7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5757fcccfef86457aec9aa42aef3e4c3bf4bc45fa2a37359c8909039ec8ae73d
+size 187210
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/955eff49369c0dcaa1a0e8ed9bfd8342_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/955eff49369c0dcaa1a0e8ed9bfd8342_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8c593ac2a99dee7a674f6b867c083a83fbb0e1df
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/955eff49369c0dcaa1a0e8ed9bfd8342_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b9bc9055affb850bf0f2b799ec0e2b4ff2e317d0cf156e153064bc04eb102b99
+size 89916
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/95be50ec094942200786128aa936cfae_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/95be50ec094942200786128aa936cfae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..653a89f826844936da5ca8c7d28f536a62cbfe71
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/95be50ec094942200786128aa936cfae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e7e6046388ebb47a1403d70f696345b9213107599dcf58a5792073e4cfd01d8a
+size 124514
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/95e259e8cb3519025066052af263f8c0_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/95e259e8cb3519025066052af263f8c0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d39babd94f412f7221e1f3cde5c3f7e297d1034d
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/95e259e8cb3519025066052af263f8c0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:995f439fccecb32b5e57443a73f4caeecad0431959f0528f72426b03affc352c
+size 11829
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/9687bd5e8b62cadba093b0d1b70536cd_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/9687bd5e8b62cadba093b0d1b70536cd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0328802d2f0e6ca6df1b81045f2665611fdffc95
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/9687bd5e8b62cadba093b0d1b70536cd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:64a4f83a36d116527079b0167fe57befa9803ca485bd0cde450e1db0ce5314de
+size 206030
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/96b5a08abda472c0c3838ecf1357f57f_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/96b5a08abda472c0c3838ecf1357f57f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e6f0deb20716bca08571b1e874cbd7c206d69448
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/96b5a08abda472c0c3838ecf1357f57f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:75227e11295cafbc50b65d336e64d542243f1df06c972de23ba17dcef9f384d2
+size 20227
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..08149828db56d5b95b149856c49f6d27ba39a91e
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:94b9d01376c3af968f45b154d7f4095106bfedaf75acfc77d2a7ee1da4fe7888
+size 7953
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/9b6977f95ef47e2c87cd4979c09a7edb_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/9b6977f95ef47e2c87cd4979c09a7edb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2597ba436ec08c54071b1dfcc8e3bbf32d6854df
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/9b6977f95ef47e2c87cd4979c09a7edb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:55211f7c8753fbaaceceefdd46fa281e48cdcbb7d5b7e9e92669cd8d0e6dd1d8
+size 151659
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9f9283e7be81f32dc1cc35f95cfb3a96d09b243c
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1ad8d43c7f2322956e47bd93d0c23e0fab100fb409f52192b08909ffb6463231
+size 32351
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/9d0d314eecc9c87cee25c0336bfe5dbf_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/9d0d314eecc9c87cee25c0336bfe5dbf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..996646c8d2eef9681ae6667ac1a6973b5229b576
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/9d0d314eecc9c87cee25c0336bfe5dbf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6af0c993762e57e99ca76c7cdbc94c2a5714672e0f18acd7949e0f73038a4609
+size 109016
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/9dc88fb2c48bc64047fc3e79814f1d47_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/9dc88fb2c48bc64047fc3e79814f1d47_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c629c0e19ea83c9a2eb8d47aa0778892cafa0ec3
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/9dc88fb2c48bc64047fc3e79814f1d47_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c2bd114b6dcc8393ab244d787c7f98700f9d0f4a882cdbe9af7a163a56372bad
+size 109192
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/9faa3512b2ff7973283e76192e91bf65_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/9faa3512b2ff7973283e76192e91bf65_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dca608f0174df6806faf9b755f92ff842bc79745
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/9faa3512b2ff7973283e76192e91bf65_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d55b9e7c21f036c394c20e0deb68ab258e02fba03c40a0ad7768eaf2e5358eb3
+size 150433
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/a1890b9a9b85f13e67ed59bbad623659_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/a1890b9a9b85f13e67ed59bbad623659_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7a51df615245d0c949265c4063f9acbe2d526540
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/a1890b9a9b85f13e67ed59bbad623659_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:05d2f99adcf6067cdcc70b960535e5858c34f43e1bd747a7ec5df3de37a3cc5c
+size 25574
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/a279b24bee8e82a60177168f08cce415_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/a279b24bee8e82a60177168f08cce415_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..51fb54e080d6bc35f349631103d18f8abccfb45e
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/a279b24bee8e82a60177168f08cce415_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7db4a93347b8cecc16ad48abcbe8acc5113fa5c8cdfd388fb3857039814ed5a4
+size 127564
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d6d1b989c9cbbc26d83e7e16f3122c51eb1b1410
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e42c3b1a058ec1a7caccda9c0259624719a83b7684d40cf0e8958303ae3615d2
+size 17641
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/a447b2987d1c97785a18fc8c036ab70c_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/a447b2987d1c97785a18fc8c036ab70c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..79068e6ed59bdc45ec38635a33431ddae76bb211
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/a447b2987d1c97785a18fc8c036ab70c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:97cd95f48bed462c7f88b86c7be1fc4acdc2c529c108726e21b3d154e5b40d0d
+size 251980
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ade769e09368ff814746be9e4141d8bfd5192444
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d02a44cce51c29243414aa1d0a9750f39dfbcc61c0294c14ea5f3e87d48c3d4
+size 197455
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/a76fd8608a1490167e6c1a4ed32b38e6_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/a76fd8608a1490167e6c1a4ed32b38e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..40e0c060ad1616de90fd1dfbc6fb16bdf305ecdb
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/a76fd8608a1490167e6c1a4ed32b38e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bcfb131009ac453b6121948b6e3a98e73ba3d104fdc7351894cd497e5970f8dd
+size 135518
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/aa757e4ac9b0e12f51a06396c4e86b52_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/aa757e4ac9b0e12f51a06396c4e86b52_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..518982ddc221c59227e3a6b1dfd9739f15d4cb0a
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/aa757e4ac9b0e12f51a06396c4e86b52_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:837899357d068905a3547388250b5b43c4751fcec6e0d2fafd867cca752f1a43
+size 110786
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/aba8dccaf13118eb55ca5acb43b47874_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/aba8dccaf13118eb55ca5acb43b47874_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3da372e892868c3ebe281a32b594650fe2638e48
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/aba8dccaf13118eb55ca5acb43b47874_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:07ef3da66ce91ca91d761191b3f51bf427c2617894a6fb878b1a5117bdd5c3e3
+size 119718
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/ac8194ec0d833d53a0a36adada95b39e_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/ac8194ec0d833d53a0a36adada95b39e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d245e5f7529a5886c168c420afea99d86ad4ee18
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/ac8194ec0d833d53a0a36adada95b39e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ef4c7bcdfa6ea7e5871c92e4460c6bf8851abe427746b3c1684394c6599805fb
+size 24081
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/af4f213abb5ad1891a43425e0d758021_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/af4f213abb5ad1891a43425e0d758021_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..89f5661dc6a7f5bbe5f5a2b153f79a329590968a
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/af4f213abb5ad1891a43425e0d758021_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1adf6c6d0f8f2d2af16526cc39a18eb88b6c277dd487c37e40ef27a3ab5a0723
+size 121031
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/b1a6ab9f3d33d6e8d64173bfa595b763_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/b1a6ab9f3d33d6e8d64173bfa595b763_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..87d0c4730298a74a2d1d5a57858068d348a73f0a
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/b1a6ab9f3d33d6e8d64173bfa595b763_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:733f7500879612059d5e77e23c6ea33fe216188ebba1c503bb45fa3dde946aaf
+size 106100
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/b327d9f0565f7e032fc82b4322c844dc_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/b327d9f0565f7e032fc82b4322c844dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a9ec245f2f73d8285808f76c678ad378f3ede135
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/b327d9f0565f7e032fc82b4322c844dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:91182c7a0f3ffc9c05732951316fd856dc8bad003784b4532f90ccdb4b8fd4d0
+size 19794
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..523ba384a97bb76d4c6675cd002a5bd489daa913
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aebf756e571304262f8ba8ede952640ff5b726e423ba734f7f6d9e6a56dfdf4a
+size 24351
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/b5ce6d659e1431289c2e79b01bf38a15_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/b5ce6d659e1431289c2e79b01bf38a15_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..df2d61e7db9b6e0b105886687e627f5ec30affa0
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/b5ce6d659e1431289c2e79b01bf38a15_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cb54999015f16cdcedfdf6a444decfec2a63d39c04fe0aa6c4734bbc28bb509d
+size 147044
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/b898dcb574f08ea237dd3326abecd185_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/b898dcb574f08ea237dd3326abecd185_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..057a95c0f5166eb7a0150f03ab9a0da4bb43c4af
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/b898dcb574f08ea237dd3326abecd185_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:441bb345962db97f26d4d36f26d8362708150f0b29ecd2b1c0b4e3bd84e7f812
+size 118028
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/b8d855a06aad434aeafa2739bf62e7de_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/b8d855a06aad434aeafa2739bf62e7de_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..646af7b329dfb592d720f9a21cf43504a6ed77dd
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/b8d855a06aad434aeafa2739bf62e7de_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bef27fb486a91706851b3d554b8efe3d24410e896a77d9c4a5d8517304a38de4
+size 80241
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/b989b7ceff18d5840ba42e8bd64e4292_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/b989b7ceff18d5840ba42e8bd64e4292_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..79c06702821502048d9490f1f55f0b8c64cbd266
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/b989b7ceff18d5840ba42e8bd64e4292_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1e3ebb3499ddfe202a649d8399d374f7dbe1cbdfeb62cbc4c74f5e9222976a7a
+size 83058
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/baf8e707713cfcf1fd4e6aa38dd94597_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/baf8e707713cfcf1fd4e6aa38dd94597_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..355d0615373736b1d7a68a38a90c3022dc0a2118
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/baf8e707713cfcf1fd4e6aa38dd94597_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:70d5a9e11db3870cc6e0ea5a5b5a1f5e9dc16d1f2b9400123afaca041d66c970
+size 44643
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/bb8035cd106b4d77b3615e90645f8e37_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/bb8035cd106b4d77b3615e90645f8e37_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6de783e1e50b8eb3bfd35adfeffd23889ff0d4fd
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/bb8035cd106b4d77b3615e90645f8e37_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5aaeac971eb80028bb1962e9993ef412dae3f670df9ed1bf080602acb90e81b5
+size 101142
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/bd0fe87fe6e236bc4778830b4f26d9e2_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/bd0fe87fe6e236bc4778830b4f26d9e2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d52131ccea86bd2804afbea6bd33bad9f729598d
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/bd0fe87fe6e236bc4778830b4f26d9e2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dea32a0615c345d62ce260dc9979f37c76306cb6f23e89aa0e8b1848b907ded5
+size 31336
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/bd33d5bc49161429f4c7da76529bcd18_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/bd33d5bc49161429f4c7da76529bcd18_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fc46755eba11e6339a58fea89b4b889fd72ae1fa
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/bd33d5bc49161429f4c7da76529bcd18_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bad835cc6e1ebbf19492de58e5b914c5233d847e1471d0795d57e02ac4d873a6
+size 179116
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/bdee2715697a4142d16a360549fa7c7f_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/bdee2715697a4142d16a360549fa7c7f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8c7717356dde147f2224c86731d6b827866c383a
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/bdee2715697a4142d16a360549fa7c7f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:390e109a1759b3f5dd1384a9386b6345e6ae2490fa686e22b1b3c268259ceee9
+size 20264
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ab7c2d1f1b24028c5720571ea6bee1d9690f4095
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2b5004b9089bf313df3264a2f5e5fa02e3a0769fc5f066e82f1860698179e5ee
+size 13090
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/beda549cc2a4e2b9ac7f74fe9ed72b67_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/beda549cc2a4e2b9ac7f74fe9ed72b67_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e18b82b557b7adc93168221ed2c96a1d8f50fae9
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/beda549cc2a4e2b9ac7f74fe9ed72b67_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9062f84c9d8a521b84bfdb6ceaa0ece5608fc133745fd7029d595ca30ad9ed4f
+size 154472
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/c07637986c84860270f00b7af39e1956_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/c07637986c84860270f00b7af39e1956_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6d175e1b716c0b162e3a88a95a2b1c26fe6c3641
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/c07637986c84860270f00b7af39e1956_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:264d35de92d96d2cfa821fb41241e2319979f40c6931ed9764a4b5b7eecc2b18
+size 137021
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/c3ba400c25c28fedce1c7d29414198de_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/c3ba400c25c28fedce1c7d29414198de_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cfe7762944a2cc9e73b8e4dd0da5817c11d2ff55
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/c3ba400c25c28fedce1c7d29414198de_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5bb7f532d32bc0ba79f4d2a0af4d8be1ee206831c7e38bd9f2c2e47cdea56479
+size 93944
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c1c5c44e08008e574118e96338950d6bf677693e
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2f5306b4f2be003950125e048835e991945b214f2e9062cb61f620b3602e122a
+size 41198
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/c7111699f84f3e2bc4016b7876f10de6_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/c7111699f84f3e2bc4016b7876f10de6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..10f94ffde6e3e3b235ae3030a917b03617d1b296
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/c7111699f84f3e2bc4016b7876f10de6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f9378713dcadc97178006c81422885ef57452a64d1c4ee49ebddbc6cf0c80074
+size 283816
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/c80e1284549c9914d0249b0e749c500a_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/c80e1284549c9914d0249b0e749c500a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c1761fbbb7c644ec8b59915c3821ecd4be8dd5ed
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/c80e1284549c9914d0249b0e749c500a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:10133b56c60179283bc080f88cca73ce28b4c0ac493b1c5d0c9a818e94430a41
+size 88925
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fb7e1e373846e405ce11860855b501c60a877709
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:850fec332b167dc9faac2b8ea463fe1db922cdfc52eecc3221c9efdc70daa749
+size 137932
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/c93353297f7ed04bc9173ac1f224d406_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/c93353297f7ed04bc9173ac1f224d406_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..24de9138350e412ad53a8c3e852684b4edaa5ec4
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/c93353297f7ed04bc9173ac1f224d406_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ce0d2e379e4277079fe33977160f6dd9c05cbe1044375a94e3ff1b8397b05b64
+size 122396
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/c93c4b33a2b42c8dd6d82a354f2f89f1_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/c93c4b33a2b42c8dd6d82a354f2f89f1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d5d016f9dadee70706a7113170323f9905f16eee
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/c93c4b33a2b42c8dd6d82a354f2f89f1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:198502d6d268afb858a36d1c5c0ddfa388ef91771143701a7d4324d966554412
+size 89948
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/ca7e6c1823b101e869d4f177c147bea6_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/ca7e6c1823b101e869d4f177c147bea6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3c3a1bbc4a20aed91f4a34ab0a66c26f6b67c64d
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/ca7e6c1823b101e869d4f177c147bea6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b4cdb6a988abb4c72d2af66fd8199e14724c21352480faea043be8b17c80ea53
+size 73296
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/cb9e3603e260c7b07aca73128586df80_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/cb9e3603e260c7b07aca73128586df80_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c7bab9c5ec3054b239c91686b02614a00b6d678e
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/cb9e3603e260c7b07aca73128586df80_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:58e783e856b154287537f9d8541a75c51ec0d7443b6646c687703449cf75324c
+size 137215
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/ce06eec6bb6d76bf7688932b2f6eb6fa_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/ce06eec6bb6d76bf7688932b2f6eb6fa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a6bcbdad0cd402c4bbb535c93100dbbf111be937
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/ce06eec6bb6d76bf7688932b2f6eb6fa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a0bfb88abad11457271cb44cc2f6419219f91cef7d45b5d03730fe4b514782e2
+size 93911
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/cf8650780cc9719622f013f33967b37c_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/cf8650780cc9719622f013f33967b37c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5f20fc33919449a5b4115eecae9eb6cc71877f1c
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/cf8650780cc9719622f013f33967b37c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:25ed42045ca5f21b309a90cb9a02bfd17e4b91f107d0d0d0216b8b499fe1f623
+size 160710
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/cf8d9315f7f99ef87b4040c7312c5c6f_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/cf8d9315f7f99ef87b4040c7312c5c6f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f8015614b883f56dfa29b685cc81f777a4460922
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/cf8d9315f7f99ef87b4040c7312c5c6f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f31dc895445f1283c8053bbdf5f6809aea646e9236fae68a54fbf2480201eb37
+size 131457
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/cfd911568094b540490a86efe5c0ead6_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/cfd911568094b540490a86efe5c0ead6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2934f52a3385d7eed62861b344266e44dbdfd849
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/cfd911568094b540490a86efe5c0ead6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5fe182764cfb6741cbc72889693560b930367a91e094e394532a4e46803e76b9
+size 27778
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..744a36fc9b8fbcba643fa70fc29fee00afe66d90
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0db8cc593510f6f5389781861f4ed1db525107051d75bbcfc065009a954c3b4a
+size 28663
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/d33f50868e9cfda1b1206833c4061e12_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/d33f50868e9cfda1b1206833c4061e12_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6d74248041b53346b0fdd2eea1c204b32b11707b
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/d33f50868e9cfda1b1206833c4061e12_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8f4ed439ea292d1f02102b86f62f8c21c17d0fd7417dd910c0a219f48f9ca23f
+size 60064
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/d5de4c1d2f0b71aa339b6b2118268fbb_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/d5de4c1d2f0b71aa339b6b2118268fbb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..76e1552ef0d8399bcd1b38b4e79f8d41276597fe
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/d5de4c1d2f0b71aa339b6b2118268fbb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:435b704e41b1d7a8854d98cb4eb7b88adf3ea4c67d388b8a59123ade93063628
+size 130633
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/d7996c295c6d5c251be4bce3dea03f2e_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/d7996c295c6d5c251be4bce3dea03f2e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7746ab6d261dba6f9c750501ef45c0000d630ec7
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/d7996c295c6d5c251be4bce3dea03f2e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:70d92dd57249cb6dbc4b2e183a5397d5e0edcb8aaa920a78d2c86e48c19b644e
+size 169947
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/d9862ac8473902e7dfe441c5e88d47d8_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/d9862ac8473902e7dfe441c5e88d47d8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2f398ca99c163afd23e710e6ecc7e3da75808c0b
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/d9862ac8473902e7dfe441c5e88d47d8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:abaeac4de4c84c7e99e8fb9c5c06d88377f3a1ca58ad61370a815271cc5b6df9
+size 77618
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/da90447206621f137780272a2bf807a4_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/da90447206621f137780272a2bf807a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..76496da45f883c89d4119748232145b6b20a0b00
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/da90447206621f137780272a2bf807a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5d7756ca92e0d52ddf80602fe8fcaec2b55b965727165954544ec650f4f9388d
+size 24026
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/dc7665c574da4162d51b543b66d87eda_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/dc7665c574da4162d51b543b66d87eda_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5cb17e9ebcfaaa34e6642bb9cf8bf34f5ae5d009
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/dc7665c574da4162d51b543b66d87eda_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c026cd9dae2e0bdef43ac7bc9c8bbd577c8a5a42960e6663dbf46f0da6be149b
+size 134076
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/dd00cc2325415c09afb8bf178f60f33b_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/dd00cc2325415c09afb8bf178f60f33b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1e1c7d3d37aadc281d859251afd67adabaa7ecb5
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/dd00cc2325415c09afb8bf178f60f33b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:09a097d56c82d1d9a562562e0467cacd6327b5eb592624344800d2328dfaea44
+size 93122
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/defe20e5056d0c3552de2d50ce88c5cb_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/defe20e5056d0c3552de2d50ce88c5cb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5a232976ecfbe2944b48920c76402b39edbc6651
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/defe20e5056d0c3552de2d50ce88c5cb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a13f72aee201fcd597ffc6f20d86498d17a77e8a2c58503e83037d7fb87f93fe
+size 179036
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/df803281854ce2cbde7019b5aeefd8cd_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/df803281854ce2cbde7019b5aeefd8cd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9c60ad6a300a753f14a9098145f6bf5e0eb4eb39
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/df803281854ce2cbde7019b5aeefd8cd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1eb615ca970ca90c0a714f1faf9ea2a3c404d21f7bf4361eaa57ad6b986b4b7e
+size 169854
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/dfaa8b98082261913dac00eae86b2889_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/dfaa8b98082261913dac00eae86b2889_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c7fa2947fab90ea38d605906271cda33006815bf
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/dfaa8b98082261913dac00eae86b2889_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ddf6ef4c9da08cb1b08c382a75c27eb8601bb099ec1738bbbdbe2dae473a19ca
+size 23911
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/e47d450f315d0b633906c03cc91f90ef_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/e47d450f315d0b633906c03cc91f90ef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..681e1d7ddf9b19b921bcece27d95792b8da2f4cc
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/e47d450f315d0b633906c03cc91f90ef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:925d60adea530019e3cbc85d8d5091b79529fda4b4c16982347a56f1213b71f7
+size 124538
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/e492fe1061d82aa76cbf7114f57eb90c_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/e492fe1061d82aa76cbf7114f57eb90c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..22248176c2ca119a866987ae64df34cc87b1132d
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/e492fe1061d82aa76cbf7114f57eb90c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a21a8571b0eed7cca53be1827c0889a881bb360d030f052a04b642abb97cc83f
+size 193423
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/e5ded42f8e352da02ee86cb55550c45d_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/e5ded42f8e352da02ee86cb55550c45d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cdeac39e936d429fa37730e15ee49aaff0552978
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/e5ded42f8e352da02ee86cb55550c45d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:048663bfc6c788257f256e04fc6ce99392925541af824b0f174bd8fe4c757734
+size 15368
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/ea40403ee09ad7bcb209382495f36547_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/ea40403ee09ad7bcb209382495f36547_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9e41e6e024a17e4370d3dd00e66bd4331d41d414
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/ea40403ee09ad7bcb209382495f36547_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8dc5dd175a39cb8e0ccc44fd937aa2849c630873cacdc11e8ea545465ca43677
+size 62149
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/eda1a0f033926f48febc095bce470c58_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/eda1a0f033926f48febc095bce470c58_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d655aae6032377e2b27dd00c82896ee55c517756
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/eda1a0f033926f48febc095bce470c58_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c765e347f16c91641890768900f9bd63013f100634d6db2093e188aa1d30d18c
+size 110648
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/efb282bed9f06eef1987a14fb27bc599_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/efb282bed9f06eef1987a14fb27bc599_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f6e07c363604a2d07de5f22961294ddaecc717ea
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/efb282bed9f06eef1987a14fb27bc599_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1321f104159b48d560e7c9288288c92d88e9ac8d370377b897f41f1d0c1d7d2e
+size 13991
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/f2a3faa7fc860dd26eda5b88460b0bcf_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/f2a3faa7fc860dd26eda5b88460b0bcf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8963a8f5ac844d3111d5c9b5ba4298059685b6c2
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/f2a3faa7fc860dd26eda5b88460b0bcf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a7093c6c48614ace9e9e71a934a9d2986bc2b5459a5a07e13d7a9d0e62375a2f
+size 237740
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/f2a6c46fa05d5588ce4c6e1a3ee194c7_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/f2a6c46fa05d5588ce4c6e1a3ee194c7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..67424036d06589e677535b03ea7e3aef03cca534
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/f2a6c46fa05d5588ce4c6e1a3ee194c7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d762f18e8ac2aec68f920bb334b37f480caed5bd9a0dcd9b27d918bc1847bc87
+size 128616
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/f2b561f8d2d2b8402379552179d9fbef_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/f2b561f8d2d2b8402379552179d9fbef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2335fbff166264c2b7fe69806f0611188bc21511
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/f2b561f8d2d2b8402379552179d9fbef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:51525c825be61b68362b85e837d4b2a7b92b768ce02f09255250590b2575e1b6
+size 55603
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/f431b5db0c635c95318cff1adbe10c05_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/f431b5db0c635c95318cff1adbe10c05_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..da592fa0be5bd42556f6ee981976ec7ed68c65f9
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/f431b5db0c635c95318cff1adbe10c05_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bda5cda75c82d17db8cdf5a6bafb0499643dbe93c4e3fb94515044a29f6726d6
+size 86267
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/f57a881fcbcaf494a7dedc4f61224991_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/f57a881fcbcaf494a7dedc4f61224991_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c1395f55bc7730e0bebfea3dcc9b155e785df7bb
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/f57a881fcbcaf494a7dedc4f61224991_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9726348bf1c8b76cc60fcea2ab54e4d36142d17222bbf21bb89254e5a9b3e032
+size 9965
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/f5f5c0161d7d582a5a4c7227eb4e8eb0_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/f5f5c0161d7d582a5a4c7227eb4e8eb0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1c4dcc9f274e094834362c262229f55fe8186b12
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/f5f5c0161d7d582a5a4c7227eb4e8eb0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d31e8026f7956fc914cf192d739f7494a7d5b1c2f06ad9c695944027420f0ce8
+size 96987
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/f6944ef450a5560fc697a86a01b70b36_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/f6944ef450a5560fc697a86a01b70b36_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4ed617f1ceccc909f6d19456359c0b16a832af28
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/f6944ef450a5560fc697a86a01b70b36_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d2a268768afce50982ff28391bd849c07900bbee64da93223fcbcbb3c954d695
+size 72930
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..627edb529314398d57c32cc10d0ff583deab8535
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:26973665fd14fee2955c2aa2969a9ab7be3590612ade8fbdaea4a8617031f9ca
+size 26337
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/fc7c83167c4e9e614f40e52b39ef735d_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/fc7c83167c4e9e614f40e52b39ef735d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..61e2f2a0d54ee5b37e0fe02ce50f9b27d35e13e1
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/fc7c83167c4e9e614f40e52b39ef735d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:318eb8c2d5e91a4a7ee7b8a91973e4ac33df54f89fe497208a6ba5f34840bc3b
+size 54202
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/fda85db2e355bb8e3edcd5a74bf3d673_img.jpg b/marked/Q/T-REC-Q.704-199607-I_PDF-E/fda85db2e355bb8e3edcd5a74bf3d673_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fc27d34b4d7264e9930bbcaa10fad44b0d270ea5
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/fda85db2e355bb8e3edcd5a74bf3d673_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d5cf3dda8e0327b986041ac82549ea30bd0f9a503be00c3d35d3a1b01becd8dd
+size 71518
diff --git a/marked/Q/T-REC-Q.704-199607-I_PDF-E/raw.md b/marked/Q/T-REC-Q.704-199607-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..50bea829743784e6497527f98227d2ddc871c964
--- /dev/null
+++ b/marked/Q/T-REC-Q.704-199607-I_PDF-E/raw.md
@@ -0,0 +1,8745 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.704**
+
+(07/96)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Specifications of Signalling System No. 7 – Message
+transfer part
+
+---
+
+**Signalling network functions and messages**
+
+ITU-T Recommendation Q.704
+
+(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 |
+| 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 |
+| General | Q.700 |
+| Message transfer part | Q.701–Q.709 |
+| Simplified message transfer part | Q.710 |
+| Signalling connection control part | Q.711–Q.719 |
+| Telephone user part | Q.720–Q.729 |
+| ISDN supplementary services | Q.730–Q.739 |
+| Data user part | Q.740–Q.749 |
+| Signalling System No. 7 management | Q.750–Q.759 |
+| ISDN user part | Q.760–Q.769 |
+| Transaction capabilities application part | Q.770–Q.779 |
+| Test specification | Q.780–Q.799 |
+| Q3 interface | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+
+For further details, please refer to ITU-T List of Recommendations.
+
+## **ITU-T RECOMMENDATION Q.704**
+
+## **SIGNALLING NETWORK FUNCTIONS AND MESSAGES**
+
+## **Summary**
+
+This Recommendation describes the functions and procedures for and relating to the transfer of messages between the signalling points, which are the nodes of the signalling network. It has been modified to allow use by the broadband ISDN User Part in the narrow-band environment, and the Satellite ISDN User Part.
+
+### **Source**
+
+ITU-T Recommendation Q.704 was revised by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 9th of July 1996.
+
+## 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 Introduction..... | 1 |
+| 1.1 General characteristics of the signalling network functions..... | 1 |
+| 1.2 Signalling message handling..... | 1 |
+| 1.3 Signalling network management..... | 2 |
+| 2 Signalling message handling..... | 3 |
+| 2.1 General..... | 3 |
+| 2.2 Routing label..... | 4 |
+| 2.3 Message routing function..... | 6 |
+| 2.3.4 Handling of level 3 messages ..... | 7 |
+| 2.3.5 Handling of messages under signalling link congestion..... | 7 |
+| 2.4 Message discrimination and distribution functions ..... | 8 |
+| 3 Signalling network management..... | 9 |
+| 3.1 General..... | 9 |
+| 3.2 Status of signalling links..... | 10 |
+| 3.2.2 Signalling link failure ..... | 10 |
+| 3.2.3 Signalling link restoration ..... | 11 |
+| 3.2.4 Signalling link deactivation ..... | 11 |
+| 3.2.5 Signalling link activation..... | 11 |
+| 3.2.6 Signalling link blocking..... | 11 |
+| 3.2.7 Signalling link unblocking..... | 11 |
+| 3.2.8 Signalling link inhibiting..... | 16 |
+| 3.2.9 Signalling link uninhibiting..... | 16 |
+| 3.3 Procedures used in connection with link status changes ..... | 16 |
+| 3.3.1 Signalling link failed ..... | 16 |
+| 3.3.2 Signalling link restored..... | 16 |
+| 3.3.3 Signalling link deactivated ..... | 18 |
+| 3.3.4 Signalling link activated ..... | 19 |
+| 3.3.5 Signalling link blocked..... | 19 |
+| 3.3.6 Signalling link unblocked..... | 19 |
+| 3.3.7 Signalling link inhibited ..... | 19 |
+| 3.3.8 Signalling link uninhibited ..... | 19 |
+| 3.4 Status of signalling routes..... | 20 |
+| 3.4.1 Signalling route unavailability..... | 20 |
+| 3.4.2 Signalling route availability..... | 20 |
+
+| | Page |
+|-----------------------------------------------------------------------------------|-------------|
+| 3.4.3 Signalling route restricted 1 ..... | 20 |
+| 3.5 Procedures used in connection with route status changes..... | 20 |
+| 3.5.1 Signalling route unavailable ..... | 20 |
+| 3.5.2 Signalling route available ..... | 20 |
+| 3.5.3 Signalling route restricted 1 ..... | 21 |
+| 3.6 Status of signalling points..... | 21 |
+| 3.6.1 Signalling point unavailability..... | 21 |
+| 3.6.2 Signalling point availability..... | 21 |
+| 3.7 Procedures used in connection with point status changes ..... | 21 |
+| 3.7.1 Signalling point unavailable ..... | 21 |
+| 3.7.2 Signalling point available ..... | 22 |
+| 3.8 Signalling network congestion..... | 22 |
+| 3.8.1 General..... | 22 |
+| 3.8.2 Congestion status of signalling links ..... | 22 |
+| 3.8.3 Procedures used in connection with link congestion status changes..... | 25 |
+| 3.8.4 Congestion status of signalling route sets..... | 25 |
+| 3.8.5 Procedures used in connection with route set congestion status changes..... | 26 |
+| 4 Signalling traffic management..... | 26 |
+| 4.1 General..... | 26 |
+| 4.2 Normal routing situation..... | 27 |
+| 4.3 Signalling link unavailability..... | 28 |
+| 4.4 Signalling link availability..... | 28 |
+| 4.5 Signalling route unavailability..... | 29 |
+| 4.6 Signalling route availability..... | 29 |
+| 4.7 Signalling route restriction 1 ..... | 29 |
+| 4.8 Signalling point availability..... | 29 |
+| 5 Changeover ..... | 29 |
+| 5.1 General..... | 29 |
+| 5.2 Network configurations for changeover ..... | 30 |
+| 5.3 Changeover initiation and actions..... | 30 |
+| 5.4 Buffer updating procedure ..... | 32 |
+| 5.5 Retrieval and diversion of traffic ..... | 32 |
+| 5.6 Emergency changeover procedures..... | 32 |
+| 5.7 Procedures in abnormal conditions..... | 34 |
+| 6 Changeback..... | 34 |
+
+| | Page | |
+|--------|-----------------------------------------------------------------------------------------------|----|
+| 6.1 | General..... | 34 |
+| 6.2 | Changeback initiation and actions ..... | 34 |
+| 6.3 | Sequence control procedure..... | 36 |
+| 6.4 | Time-controlled diversion procedure..... | 37 |
+| 6.5 | Procedures in abnormal conditions..... | 37 |
+| 7 | Forced rerouting..... | 38 |
+| 7.1 | General..... | 38 |
+| 7.2 | Forced rerouting initiation and actions ..... | 38 |
+| 8 | Controlled rerouting..... | 38 |
+| 8.1 | General..... | 38 |
+| 8.2 | Controlled rerouting initiation and actions ..... | 39 |
+| 9 | MTP restart ..... | 39 |
+| 9.1 | General..... | 39 |
+| 9.2 | Actions in a signalling point whose MTP is restarting..... | 40 |
+| 9.3 | Actions in a signalling point X, adjacent to a signalling point Y
whose MTP restarts ..... | 41 |
+| 9.4 | Short term isolations ..... | 42 |
+| 9.5 | TRA messages and timer T19..... | 42 |
+| 9.6 | General rules ..... | 43 |
+| 9.7 | Sequence diagrams..... | 43 |
+| 9.7.1 | SP with restarting MTP according to subclause 9.2..... | 44 |
+| 9.7.2 | Actions in SP X adjacent to SP Y whose MTP restarts according to
subclause 9.3..... | 45 |
+| 10 | Management inhibiting ..... | 45 |
+| 10.1 | General..... | 45 |
+| 10.2 | Inhibiting initiation and actions ..... | 46 |
+| 10.3 | Uninhibiting initiation and actions ..... | 47 |
+| 10.3.1 | Management-initiated uninhibiting ..... | 47 |
+| 10.3.2 | Signalling routing control initiated uninhibiting ..... | 48 |
+| 10.4 | Receipt of unexpected management inhibition messages..... | 48 |
+| 10.5 | Management inhibited link status and processor recovery ..... | 48 |
+| 10.6 | Inhibit test procedure ..... | 49 |
+| 11 | Signalling traffic flow control..... | 49 |
+| 11.1 | General..... | 49 |
+| 11.2 | Flow control indications ..... | 50 |
+
+| | Page | |
+|--------|----------------------------------------------------------------------------------------------------------------------------|----|
+| 11.2.1 | Signalling route set unavailability ..... | 50 |
+| 11.2.2 | Signalling route set availability ..... | 50 |
+| 11.2.3 | Signalling route set congestion (International signalling network)..... | 50 |
+| 11.2.4 | Signalling route set congestion (National option with congestion priorities) ..... | 51 |
+| 11.2.5 | Signalling route set congestion (National options without congestion priorities) ..... | 51 |
+| 11.2.6 | Signalling point/signalling transfer point congestion..... | 51 |
+| 11.2.7 | User Part availability control..... | 51 |
+| 11.2.8 | User Part congestion..... | 52 |
+| 12 | Signalling link management ..... | 52 |
+| 12.1 | General..... | 52 |
+| 12.2 | Basic signalling link management procedures..... | 54 |
+| 12.2.1 | Signalling link activation..... | 54 |
+| 12.2.2 | Signalling link restoration ..... | 54 |
+| 12.2.3 | Signalling link deactivation..... | 54 |
+| 12.2.4 | Link set activation..... | 54 |
+| 12.3 | Signalling link management procedures based on automatic allocation of signalling terminals..... | 55 |
+| 12.3.1 | Signalling link activation..... | 55 |
+| 12.3.2 | Signalling link restoration ..... | 56 |
+| 12.3.3 | Signalling link deactivation..... | 57 |
+| 12.3.4 | Link set activation..... | 57 |
+| 12.4 | Signalling link management procedures based on automatic allocation of signalling data links and signalling terminals..... | 58 |
+| 12.4.1 | Signalling link activation..... | 58 |
+| 12.4.2 | Signalling link restoration ..... | 59 |
+| 12.4.3 | Signalling link deactivation..... | 60 |
+| 12.4.4 | Link set activation..... | 60 |
+| 12.5 | Automatic allocation of signalling terminals..... | 61 |
+| 12.6 | Automatic allocation of signalling data links ..... | 61 |
+| 12.7 | Different signalling link management procedures at the two ends of a link set..... | 63 |
+| 13 | Signalling route management ..... | 63 |
+| 13.1 | General..... | 63 |
+| 13.2 | Transfer-prohibited ..... | 63 |
+| 13.3 | Transfer-allowed..... | 64 |
+| 13.4 | Transfer-restricted (National option)..... | 65 |
+| 13.5 | Signalling-route-set-test..... | 66 |
+
+| | Page |
+|-------------------------------------------------------------------------------|-------------|
+| 13.6 Transfer-controlled (International network) ..... | 67 |
+| 13.7 Transfer-controlled (National option with congestion priorities)..... | 67 |
+| 13.8 Transfer-controlled (National option without congestion priorities)..... | 68 |
+| 13.9 Signalling-route-set-congestion-test (National Option)..... | 68 |
+| 14 Common characteristics of message signal unit formats..... | 70 |
+| 14.1 General..... | 70 |
+| 14.2 Service information octet..... | 70 |
+| 14.2.1 Service indicator ..... | 70 |
+| 14.2.2 Sub-service field ..... | 71 |
+| 14.3 Label ..... | 71 |
+| 15 Formats and codes of signalling network management messages..... | 71 |
+| 15.1 General..... | 71 |
+| 15.2 Label ..... | 72 |
+| 15.3 Heading code (H0)..... | 72 |
+| 15.4 Changeover message..... | 75 |
+| 15.5 Changeback message ..... | 75 |
+| 15.6 Emergency changeover message..... | 76 |
+| 15.7 Transfer-prohibited message..... | 76 |
+| 15.8 Transfer-allowed message..... | 77 |
+| 15.9 Transfer-restricted message (national option)..... | 77 |
+| 15.10 Signalling-route-set-test message ..... | 78 |
+| 15.11 Management inhibit message..... | 78 |
+| 15.12 Traffic restart allowed message ..... | 79 |
+| 15.13 Signalling-data-link-connection-order message ..... | 79 |
+| 15.14 Signalling-data-link-connection-acknowledgement message..... | 80 |
+| 15.15 Transfer-controlled message..... | 81 |
+| 15.16 Signalling-route-set-congestion-test message (national option)..... | 81 |
+| 15.17 User Part unavailable message..... | 82 |
+| 16 State transition diagrams, abbreviations and timers ..... | 83 |
+| 16.1 General..... | 83 |
+| 16.2 Drafting conventions..... | 83 |
+| 16.2.5 Notations for national operations ..... | 84 |
+| 16.3 Signalling message handling..... | 84 |
+| 16.4 Signalling traffic management..... | 84 |
+
+| | Page |
+|----------------------------------------------------|-------------|
+| 16.5 Signalling link management ..... | 85 |
+| 16.6 Signalling route management ..... | 85 |
+| 16.7 Abbreviations used in Figures 23 onwards..... | 85 |
+| 16.8 Timers and timer values..... | 86 |
+
+# **SIGNALLING NETWORK FUNCTIONS AND MESSAGES**
+
+*(Geneva, 1980; modified at Helsinki, 1993; revised in 1996)*
+
+## **1 Introduction**
+
+### **1.1 General characteristics of the signalling network functions**
+
+**1.1.1** This Recommendation describes the functions and procedures for and relating to the transfer of messages between the signalling points, which are the nodes of the signalling network. Such functions and procedures are performed by the Message Transfer Part at level 3, and therefore they assume that the signalling points are connected by signalling links, incorporating the functions described in Recommendations Q.702 and Q.703. The signalling network functions must ensure a reliable transfer of the signalling messages, according to the requirements specified in Recommendation Q.706, even in the case of the failure of signalling links and signalling transfer points; therefore, they include the appropriate functions and procedures necessary both to inform the remote parts of the signalling network of the consequences of a fault, and to appropriately reconfigure the routing of messages through the signalling network.
+
+**1.1.2** According to these principles, the signalling network functions can be divided into two basic categories, namely:
+
+- *signalling message handling*; and
+- *signalling network management*.
+
+The signalling message handling functions are briefly summarized in 1.2, the signalling network management functions in 1.3. The functional interrelations between these functions are indicated in Figure 1.
+
+### **1.2 Signalling message handling**
+
+**1.2.1** The purpose of the signalling message handling functions is to ensure that the signalling messages originated by a particular User Part at a signalling point (originating point) are delivered to the same User Part at the destination point indicated by the sending User Part.
+
+Depending on the particular circumstances, this delivery may be made through a signalling link directly interconnecting the originating and destination points, or via one or more intermediate signalling transfer points.
+
+**1.2.2** The signalling message handling functions are based on the label contained in the messages which explicitly identifies the destination and originating points.
+
+The label part used for signalling message handling by the Message Transfer Part is called the *routing label* its characteristics are described in clause 2.
+
+**1.2.3** As illustrated in Figure 1, the signalling message handling functions are divided into:
+
+- the *message routing* function, used at each signalling point to determine the outgoing signalling link on which a message has to be sent towards its destination point;
+- the *message discrimination* function, used at a signalling point to determine whether or not a received message is destined to the point itself. When the signalling point has the transfer capability and a message is not destined to it, that message has to be transferred to the message routing function;
+
+- the *message distribution* function, used at each signalling point to deliver the received messages (destined to the point itself) to the appropriate User Part.
+
+The characteristics of the message routing, discrimination and distribution functions are described in clause 2.
+
+
+
+The diagram illustrates the internal structure of the Level 3 Message Transfer Part (MTP). It is divided into two main functional blocks: 'Signalling network functions' and 'Signalling network management'. The 'Signalling network functions' block contains 'Message distribution', 'Message discrimination', and 'Message routing'. 'Message distribution' and 'Message discrimination' are connected to Level 4 User Parts and Level 2 Message Transfer Part. 'Message routing' is connected to Level 2 Message Transfer Part. The 'Signalling network management' block contains 'Signalling traffic management', 'Signalling route management', and 'Signalling link management'. These three functions are interconnected with dashed lines representing indications and controls. 'Signalling traffic management' is connected to Level 4 User Parts and Level 2 Message Transfer Part. 'Signalling route management' and 'Signalling link management' are connected to Level 2 Message Transfer Part. A vertical line on the left represents the interface with Level 4 User Parts, and a vertical line on the right represents the interface with Level 2 Message Transfer Part. At the bottom, a line points to 'Testing and maintenance (Message Transfer Part)'. A legend at the bottom left indicates that solid lines represent 'Signalling message flow' and dashed lines represent 'Indications and controls'. The diagram is labeled 'T1158780-94/d001'.
+
+Diagram of Signalling network functions showing Level 3 (Message Transfer Part) interacting with Level 4 (User Parts) and Level 2 (Message Transfer Part).
+
+Figure 1/Q.704 – Signalling network functions
+
+### 1.3 Signalling network management
+
+**1.3.1** The purpose of the signalling network management functions is to provide reconfiguration of the signalling network in the case of failures and to control traffic in case of congestion. Such a reconfiguration is effected by use of appropriate procedures to change the routing of signalling traffic in order to bypass the faulty links or signalling points; this requires communication between signalling points (and, in particular, the signalling transfer points) concerning the occurrence of the failures. Moreover, in some circumstances it is necessary to activate and align new signalling links, in order to restore the required signalling traffic capacity between two signalling points. When the faulty link or signalling point is restored, the opposite actions and procedures take place, in order to reestablish the normal configuration of the signalling network.
+
+**1.3.2** As illustrated in Figure 1, the signalling network management functions are divided into:
+
+- *signalling traffic management;*
+- *signalling link management; and*
+- *signalling route management.*
+
+These functions are used whenever an event (such as the failure or restoration of a signalling link) occurs in the signalling network; the list of the possible events and the general criteria used in relation to each signalling network management function are specified in clause 3.
+
+**1.3.3** Clauses 4 to 11 specify the procedures pertaining to signalling traffic management. In particular, the rules to be followed for the modification of signalling routing appear in clause 4. The diversion of traffic according to these rules is made, depending on the particular circumstances, by means of one of the following procedures: *changeover*, *changeback*, *forced rerouting*, *controlled rerouting* and *MTP restart*. They are specified in clauses 5 to 9, respectively. A signalling link may be made unavailable to User Part generated traffic by means of the management inhibiting procedure described in clause 10. Moreover, in the case of congestion at signalling points, the signalling traffic management may need to slow down signalling traffic on certain routes by using the *signalling traffic flow control* procedure specified in clause 11.
+
+**1.3.4** The different procedures pertaining to signalling link management are: *restoration*, *activation* and *inactivation* of a signalling link, *link set activation* and *automatic allocation* of signalling terminals and signalling data links. These procedures are specified in clause 12.
+
+**1.3.5** The different procedures pertaining to signalling route management are: the *transfer-prohibited*, *transfer-allowed*, *transfer-restricted*1, *transfer-controlled*, *signalling-route-set-test* and *signalling-route-set-congestion-test* procedures specified in clause 13.
+
+**1.3.6** The format characteristics, common to all message signal units which are relevant to the Message Transfer Part, level 3, are specified in clause 14.
+
+**1.3.7** Labelling, formatting and coding of the signalling network management messages are specified in clause 15.
+
+**1.3.8** The description of signalling network functions in the form of state transition diagrams according to the CCITT Specification and Description Language (SDL) is given in clause 16.
+
+## **2 Signalling message handling**
+
+### **2.1 General**
+
+**2.1.1** Signalling message handling comprises message routing, discrimination and distribution functions which are performed at each signalling point in the signalling network.
+
+Message routing is a function concerning the messages to be sent, while message distribution is a function concerning the received messages. The functional relations between message routing and distribution appear in Figure 2.
+
+**2.1.2** When a message comes from level 4 (or is originated at level 3, in the case of Message Transfer Part level 3 messages), the choice of the particular signalling link on which it has to be sent is made by the message routing function. When two or more links are used at the same time to carry traffic having a given destination, this traffic is distributed among them by the load sharing function, which is a part of the message routing function.
+
+---
+
+1 National option.
+
+**2.1.3** When a message comes from level 2, the discrimination function is activated, in order to determine whether it is destined to another signalling point. When the signalling point has the transfer capability and the received message is not destined to it, the message has to be transmitted on an outgoing link according to the routing function.
+
+**2.1.4** In the case that the message is destined to the receiving signalling point, the message distribution function is activated in order to deliver it to the appropriate User Part (or to the local Message Transfer Part level 3 functions).
+
+**2.1.5** Message routing, discrimination and distribution are based on the part of the label called the routing label, on the service indicator and, in national networks, also on the network indicator. They can also be influenced by different factors, such as a request (automatic or manual) obtained from a management system.
+
+
+
+T1158790-94/d02
+
+Diagram illustrating message routing, discrimination, and distribution functions. On the left, 'To/from level 4 (up level)' is indicated by a bracket. Two arrows point from this bracket to two boxes: 'Distribution' and 'Routing'. On the right, 'To/from level 2' is indicated by a bracket. Two arrows point from this bracket to two boxes: 'Discrimination' and 'Routing'. A vertical arrow points from the 'Distribution' box to the 'Discrimination' box. A small label 'T1158790-94/d02' is at the bottom right of the diagram.
+
+**Figure 2/Q.704 – Message routing, discrimination and distribution**
+
+**2.1.6** The position and coding of the service indicator and of the network indicator are described in 14.2. The characteristics of the label of the messages pertaining to the various User Parts are described in the specification of each separate User Part and in clause 15 for the signalling network management messages. The label used for signalling network management messages is also used for testing and maintenance messages (see Recommendation Q.707). Moreover, the general characteristics of the routing label are described in 2.2.
+
+A description of the detailed characteristics of the message routing function, including load sharing, appears in 2.3; principles concerning the number of load-shared links appear in Recommendation Q.705.
+
+A description of the detailed characteristics of the message discrimination and distribution functions appears in 2.4.
+
+**2.1.7** In addition to the normal signalling message handling procedures it may, as an option, be possible to prevent the unauthorized use of the message transfer capability of a node. The procedures to be used are implementation-dependent and further information is given in clause 8/Q.705.
+
+### **2.2 Routing label**
+
+**2.2.1** The label contained in a signalling message, and used by the relevant User Part to identify the particular task to which the message refers (e.g. a telephone circuit), is also used by the Message Transfer Part to route the message towards its destination point.
+
+The part of the message label that is used for routing is called the *routing label* and it contains the information necessary to deliver the message to its destination point.
+
+Normally the routing label is common to all the services and applications in a given signalling network, national or international (however, if this is not the case, the particular routing label of a message is determined by means of the service indicator).
+
+The standard routing label is specified in the following. This label should be used in the international signalling network and is applicable also in national applications.
+
+NOTE – There may be applications using a modified label having the same order and function, but possibly different sizes, of sub-fields as the standard routing label.
+
+**2.2.2** The standard routing label has a length of 32 bits and is placed at the beginning of the Signalling Information Field. Its structure appears in Figure 3.
+
+**2.2.3** The Destination Point Code (DPC) indicates the destination point of the message. The Originating Point Code (OPC) indicates the originating point of the message. The coding of these codes is pure binary. Within each field, the least significant bit occupies the first position and is transmitted first.
+
+A unique numbering scheme for the coding of the fields will be used for the signalling points of the international network, irrespective of the User Parts connected to each signalling point.
+
+
+
+| | | | | | |
+|--------------|-----------------------------|-----|-----|-----|-------------------------|
+| | | SLS | OPC | DPC | |
+| Length (bit) | $n \times 8$ ( $n \geq 0$ ) | 4 | 14 | 14 | First bit transmitted → |
+
+Labels: 'Routing label' spans SLS, OPC, and DPC. 'Label' spans Length, SLS, OPC, and DPC. Reference: T1158800-94/d03.
+
+DPC Destination Point Code
+ OPC Originating Point Code
+ SLS Signalling Link Selection
+
+Diagram of the routing label structure showing fields for Length, SLS, OPC, and DPC with their bit lengths and transmission order.
+
+**Figure 3/Q.704 – Routing label structure**
+
+**2.2.4** The Signalling Link Selection (SLS) field is used, where appropriate, in performing load sharing (see 2.3). This field exists in all types of messages and always in the same position. The only exception to this rule is some Message Transfer Part level 3 messages (e.g. the changeover order), for which the message routing function in the signalling point of origin of the message is not dependent on the field: in this particular case the field does not exist as such, but it is replaced by other information (e.g. in the case of the changeover order, the identity of the faulty link).
+
+In the case of circuit related messages of the TUP, the field contains the least significant bits of the circuit identification code (or bearer identification code, in the case of the Data User Part), and these bits are not repeated elsewhere. In the case of all other User Parts, the SLS is an independent field in accordance with the criteria stated in 2.2.5.
+
+In the case of Message Transfer Part level 3 messages, the signalling link selection field exactly corresponds to the *Signalling Link Code* (SLC) which indicates the signalling link between the destination point and originating point to which the message refers.
+
+**2.2.5** From the rule stated in 2.2.4 above, it follows that the signalling link selection of messages generated by any User Parts will be used in the load sharing mechanism. As a consequence, in the case of User Parts which are not specified (e.g. transfer of charging information) but for which there is the requirement to maintain the order of transmission of the messages, the field should be coded with the same value for all messages belonging to the same transaction, sent in a given direction.
+
+**2.2.6** The above principles should also apply to modified label structures that may be used nationally.
+
+### 2.3 Message routing function
+
+**2.3.1** The message routing function is based on information contained in the routing label, namely on the destination point code and on the signalling link selection field; moreover, in some circumstances the service indicator may also need to be used for routing purposes.
+
+NOTE – A possible case for the use of the service indicator is that which would arise from the use of messages supporting the signalling route management function (i.e. transfer-prohibited, transfer-allowed and signalling-route-set-messages) referring to a destination more restrictive than a single signalling point (e.g. an individual User Part) (see clause 13). Some specific routing may be required for the MTP Testing User Part (for further study).
+
+The number of such cases should be kept to a minimum in order to apply the same routing criteria to as many User Parts as possible.
+
+Each signalling point will have routing information that allows it to determine the signalling link over which a message has to be sent on the basis of the destination point code and signalling link selection field and, in some cases, of the network indicator (see 2.4.3). Typically the destination point code is associated with more than one signalling link that may be used to carry the message; the selection of the particular signalling link is made by means of the signalling link selection field, thus effecting load sharing.
+
+**2.3.2** Two basic cases of load sharing are defined, namely:
+
+- load sharing between links belonging to the same link set;
+- load sharing between links not belonging to the same link set.
+
+A load sharing collection of two or more link sets is called a combined link set.
+
+The capability to operate in load sharing according to both these cases is mandatory for any signalling point in the international network.
+
+In case a), the traffic flow carried by a link set is shared (on the basis of the signalling link selection field) between different signalling links belonging to the link set. An example of such a case is given by a link set directly interconnecting the originating and destination points in the associated mode of operation, such as represented in Figure 4.
+
+
+
+T1158810-94/d04
+
+Diagram illustrating load sharing within a link set between two signalling points A and B. Two parallel dashed lines represent the links. The top link is labeled 'SLS = XXX0' and the bottom link is labeled 'SLS = XXX1'. Arrows indicate traffic flow from A to B on both links. The text 'T1158810-94/d04' is shown below the diagram.
+
+**Figure 4/Q.704 – Example of load sharing within a link set**
+
+In case b) traffic relating to a given destination is shared (on the basis of the signalling link selection field) between different signalling links not belonging to the same link set, such as represented in Figure 5. The load sharing rule used for a particular signalling relation may or may not apply to all the signalling relations which use one of the signalling links involved (in the example, traffic destined to B is shared between signalling links DE and DF with a given signalling link selection field assignment, while that destined to C is sent only on link DF, due to the failure of link EC).
+
+As a result of the message routing function, in normal conditions all the messages having the same routing label (e.g. call set-up messages related to a given circuit) are routed via the same signalling links and signalling transfer points.
+
+Principles relating to the number of load-shared links appear in Recommendation Q.705.
+
+**2.3.3** The routing information mentioned in 2.3.1 should be appropriately updated when some event happens in the signalling network, which is relevant to the concerned signalling point (e.g. failure of a signalling link or unavailability of a signalling route). The updating of the routing information is made according to the particular event (see clause 3) and to the signalling routing modification rules specified in clause 4. If a signalling transfer point receives a message for destination point code which according to the routing information does not exist, the message is discarded and an indication is given to a management system.
+
+#### **2.3.4 Handling of level 3 messages**
+
+**2.3.4.1** Messages not related to a signalling link may be assigned any Signalling Link Code (SLC) to allow load sharing of the messages, or may be assigned a default SLC such as 0000. They are routed in accordance with the normal routing function, where the (SLC) is used as SLS for load sharing.
+
+
+
+Diagram illustrating load sharing between link sets. A source node A sends traffic to a transfer point D. From D, traffic is split: one path goes via link XXX0 to node E and then to destination B; the other path goes via a faulty link (indicated by 'X' marks) to node F and then to destination C. A legend indicates: solid arrow for traffic to B, dashed arrow for traffic to C, and a crossed line for a faulty link. The diagram is labeled T1158820-94/d05.
+
+**Figure 5/Q.704 – Example of load sharing between link sets**
+
+NOTE – In the unlikely case that a TFA will be overtaken by a corresponding TFP (or vice versa) when load sharing is used, this situation will be rectified by standard network management activities. If wanted, however, the sequence of TFPs/TFAs can be guaranteed by assigning a fixed SLC value for TFPs/TFAs referring to one specific destination.
+
+**2.3.4.2** Messages related to a signalling link should be subdivided into two groups:
+
+- Messages that are to be transmitted over a specific signalling link [e.g. changeback declaration (see clause 6) and signalling link test messages (see Recommendation Q.707)], where a special routing function must ensure that these messages are transmitted exclusively over a particular signalling link.
+- Messages that must not be transmitted over a specific signalling link [e.g. changeover messages and emergency changeover messages (see clause 5)], whose transmission over the signalling link defined by the SLC contained in the label must be avoided.
+
+#### **2.3.5 Handling of messages under signalling link congestion**
+
+**2.3.5.1** In the international signalling network, congestion priorities of messages are only assigned and the decision to discard under congestion is only made within each User Part. Message discard will only occur in the MTP should there be an extreme resource limitation (for the MTP there is no congestion priority).
+
+In national signalling networks, each message may be assigned by its generating User Part a congestion priority. This is used by the MTP to determine whether or not a message should be discarded under signalling link congestion. $N + 1$ levels of congestion priority ( $0 \leq N \leq 3$ ) are accommodated in the signalling network, with 0 being the lowest and $N$ the highest.
+
+In national signalling networks using more than one congestion priority, the highest priority is assigned to signalling network management messages.
+
+##### **2.3.5.2 In national signalling networks using multiple congestion priorities**
+
+When a signalling link has been selected for transmitting a message, comparison of the congestion priority of the message is made with the congestion status of the selected signalling link (see 3.8). If the congestion priority is not less than the signalling link congestion status, that message is transmitted using the selected signalling link.
+
+Otherwise, a transfer-controlled message is sent in response as specified in 13.7. In this case, the disposition of the concerned message is determined according to the following criteria:
+
+- i) If the congestion priority of the message is greater than or equal to the signalling link discard status, the message is transmitted.
+- ii) If the congestion priority of the message is less than the signalling link discard status, the message is discarded.
+
+### **2.4 Message discrimination and distribution functions**
+
+**2.4.1** The routing criteria and load sharing method described in 2.3 imply that a signalling point, sending messages pertaining to a given signalling transaction on a given link, should be able to receive and process messages pertaining to that transaction, e.g. in response to the sent ones, coming from any (but only one) link.
+
+The destination point code field of the received message is examined by the discrimination function in order to determine whether or not it is destined to the receiving signalling point. When the receiving signalling point has the transfer capability and the message is not destined to it, that message has to be directed to the routing function, as described in the previous subclauses, in order to be sent on the appropriate outgoing link towards the message destination point.
+
+When a signalling transfer point detects that a received message cannot be delivered to its destination point, it sends in response a transfer-prohibited message as specified in 13.2.
+
+**2.4.2** If the destination point code of the message identifies the receiving signalling point, the service indicator is examined by the message distribution function and the message is delivered to the corresponding User Part (or to the Message Transfer Part level 3).
+
+Should a User become unavailable (User unavailability is an implementation dependent notion), this is detected by the MTP. Whether the distribution is marked accordingly is implementation dependent.
+
+When the distribution function detects that a received message cannot be delivered to the required User (implementation dependent criteria), a User Part Unavailable message should be returned to the originating end on a response basis. In the originating signalling point, the relevant User Part should be informed via an MTP-STATUS primitive. A mandatory parameter Cause is included in the MTP status indication with four possible values:
+
+- Signalling Network Congestion;
+- User Part Unavailability: unequipped remote User;
+
+- User Part Unavailability: inaccessible remote User;
+- User Part Unavailability: unknown.
+
+The User Part should reduce its traffic in an appropriate manner and take specific actions.
+
+**2.4.3** In the case of a signalling point handling both international and national signalling traffic (e.g. an international gateway exchange), the network indicator is also examined in order to determine the relevant numbering scheme (international or national) and possibly the label structure. Moreover, within a national network, the network indicator may be examined to discriminate between different label structures or between different signalling point numbering if dependent on the network levels (see 14.2).
+
+## **3 Signalling network management**
+
+### **3.1 General**
+
+**3.1.1** The signalling network management functions provide the actions and procedures required to maintain signalling service, and to restore normal signalling conditions in the event of disruption in the signalling network, either in signalling links or at signalling points. The disruption may be in the form of complete loss of a signalling link or a signalling point, or in reduced accessibility due to congestion. For example, in the case of a link failure, the traffic conveyed over the faulty link should be diverted to one or more alternative links. The link failure may also result in unavailable signalling routes and this, in turn, may cause diversion of traffic at other signalling points in the signalling network (i.e. signalling points to which no faulty links are connected).
+
+**3.1.2** The occurrence of, or recovery from failures or congestion generally results in a change of the status of the affected signalling link(s) and route(s). A signalling link may be considered by level 3, either as "available" or "unavailable" to carry signalling traffic; in particular, an available signalling link becomes unavailable if it is recognized as "failed", "deactivated" "blocked2" or "inhibited", and it becomes once again available if it is recognized as "restored", "activated", "unblocked" or "uninhibited" respectively. A signalling route may be considered by level 3 as "available", "restricted1" or "unavailable" too. A signalling point may be "available" or "unavailable". A signalling route set may be "congested" or "uncongested". The detailed criteria for the determination of the changes in the status of signalling links, routes and points are described in 3.2, 3.4 and 3.6, respectively.
+
+**3.1.3** Whenever a change in the status of a signalling link, route or point occurs, the three different signalling network management functions (i.e. signalling traffic management, link management and route management) are activated, when appropriate, as follows:
+
+- a) The signalling traffic management function is used to divert signalling traffic from a link or route to one or more different links or routes, to restart a signalling point's MTP, or to temporarily slow down signalling traffic in the case of congestion at a signalling point; it comprises the following procedures:
+ - changeover (see clause 5);
+ - changeback (see clause 6);
+ - forced rerouting (see clause 7);
+ - controlled rerouting (see clause 8);
+
+---
+
+2 The "blocked" condition arises when the unavailability of a signalling link does not depend on a failure in the link itself, but on other causes, such as a "processor outage" condition in a signalling point.
+
+- MTP restart (see clause 9);
+ - management inhibiting (see clause 10);
+ - signalling traffic flow control (see clause 11).
+- b) The signalling link management function is used to restore failed signalling links, to activate idle (not yet aligned) links and to deactivate aligned signalling links; it comprises the following procedures (see clause 12):
+- signalling link activation, restoration and deactivation;
+ - link set activation;
+ - automatic allocation of signalling terminals and signalling data links.
+- c) The signalling route management function is used to distribute information about the signalling network status, in order to block or unblock signalling routes; it comprises the following procedures:
+- transfer-controlled procedure (see 13.6, 13.7 and 13.8);
+ - transfer-prohibited procedure (see 13.2);
+ - transfer-allowed procedure (see 13.3);
+ - transfer-restricted procedure (see 13.4);
+ - signalling-route-set-test procedure (see 13.5);
+ - signalling-route-set-congestion test procedure (see 13.9).
+
+**3.1.4** An overview of the use of the procedures relating to the different management functions on occurrence of the link, route and point status changes is given in 3.3, 3.5 and 3.7, respectively.
+
+### **3.2 Status of signalling links**
+
+**3.2.1** A signalling link is always considered by level 3 in one of two possible major states: available and unavailable. Depending on the cause of unavailability, the unavailable state can be subdivided into seven possible cases as follows (see also Figure 6):
+
+- unavailable, failed or inactive;
+- unavailable, blocked;
+- unavailable (failed or inactive) and blocked;
+- unavailable, inhibited;
+- unavailable, inhibited and (failed or inactive);
+- unavailable, inhibited and blocked;
+- unavailable, (failed or inactive), blocked and inhibited.
+
+The concerned link can be used to carry signalling traffic only if it is available except possibly for certain classes of test and management messages. Eight possible events can change the status of a link: signalling link failure, restoration, deactivation, activation, blocking, unblocking, inhibiting and uninhibiting; they are described in 3.2.2 to 3.2.9.
+
+#### **3.2.2 Signalling link failure**
+
+A signalling link (in service or blocked, see 3.2.6) is recognized by level 3 as failed when:
+
+- a) A link failure indication is obtained from level 2. The indication may be caused by:
+- intolerably high signal unit error rate (see clause 10/Q.703);
+ - excessive length of the realignment period (see 4.1/Q.703 and clause 7/Q.703);
+
+- excessive delay of acknowledgements (see 5.3/Q.703 and 6.3/Q.703);
+- failure of signalling terminal equipment;
+- two out of three unreasonable backward sequence numbers or forward indicator bits (see 5.3/Q.703 and 6.3/Q.703);
+- reception of consecutive link status signal units indicating out of alignment, out of service, normal or emergency terminal status (see 1.7/Q.703);
+- excessive periods of level 2 congestion (see clause 9/Q.703).
+
+The first two conditions are detected by the *signal unit error rate monitor* (see clause 10/Q.703).
+
+- b) A request (automatic or manual) is obtained from a management or maintenance system.
+
+Moreover a signalling link which is available (not blocked) is recognized by level 3 as failed when a changeover order is received.
+
+#### 3.2.3 Signalling link restoration
+
+A signalling link previously failed is restored when both ends of the signalling link have successfully completed an initial alignment procedure (see clause 7/Q.703).
+
+#### 3.2.4 Signalling link deactivation
+
+A signalling link (in service, failed or blocked) is recognized by level 3 as deactivated (i.e. removed from operation) when:
+
+- a) a request is obtained from the signalling link management function (see clause 12);
+- b) a request (automatic or manual) is obtained from an external management or maintenance system.
+
+#### 3.2.5 Signalling link activation
+
+A signalling link previously inactive is recognized by level 3 as activated when both ends of the signalling link have successfully completed an initial alignment procedure (see clause 7/Q.703).
+
+#### 3.2.6 Signalling link blocking
+
+A signalling link (in service, failed or inactive) is recognized as blocked when an indication is obtained from the signalling terminal that a processor outage condition exists at the remote terminal (i.e. link status signal units with processor outage indication are received), or when a local processor outage situation is detected, (see clause 8/Q.703).
+
+NOTE – A link becomes unavailable when it is failed or deactivated or [(failed or deactivated) and blocked] or inhibited. See Figure 6.
+
+#### 3.2.7 Signalling link unblocking
+
+A signalling link previously blocked is unblocked when an indication is obtained from the signalling terminal that the processor outage condition has ceased at the remote terminal. (Applies in the case when the processor outage condition was initiated by the remote terminal.)
+
+NOTE – A link becomes available when it is restored or activated or unblocked, or [(restored or activated) and (unblocked)] or uninhibited. See Figure 6.
+
+
+
+The diagram illustrates the state transitions for a signalling link. It includes the following states and transitions:
+
+- Top Level:**
+ - States: 'Link inhibited' (state 7), 'Link blocked' (state 4), 'Link unavailable' (state 2, labeled '(Faulty/inactive and blocked)'), 'Link available' (state 5), 'Link not active' (state 3), 'Link unavailable (faulty/inactive)' (state 2), and 'Link unavailable (blocked)' (state 3).
+ - Transitions: 'Link inhibited' to state 7; 'Link blocked' to state 4 and 'Link unavailable'; 'Link unavailable' to 'Link active'; 'Link available' to state 5; 'Link not active' to 'Link unavailable (faulty/inactive)'; 'Link unavailable (faulty/inactive)' to 'Link active'; 'Link unavailable (blocked)' to 'Link active'.
+ - Actions: 'Initiate change over' (from state 2 to state 5); 'Initiate change over' (from state 3 to state 5).
+- Middle Level:**
+ - States: 'Link active' (state 3), 'Link unblocked' (state 2), 'Link inhibited' (state 8), 'Link unavailable' (state 8, labeled '(Faulty/inactive), blocked and inhibited)'), 'Link available' (state 4), and 'Link inhibited' (state 6).
+ - Transitions: 'Link active' to state 3; 'Link unblocked' to state 2; 'Link inhibited' to state 8; 'Link unavailable' to 'Link active', 'Link unblocked', and 'Link uninhibited'; 'Link available' to state 4; 'Link inhibited' to state 6.
+ - Actions: 'Initiate change back' (from state 4 to 'Link available').
+- Bottom Level:**
+ - States: 'Link active' (state 6), 'Link unblocked' (state 7), and 'Link uninhibited' (state 4).
+ - Transitions: 'Link active' to state 6; 'Link unblocked' to state 7; 'Link uninhibited' to state 4.
+
+T1158830-94/d06
+
+A complex state transition diagram for 'Signalling link availability'. It shows various states such as 'Link active', 'Link unavailable', 'Link inhibited', 'Link blocked', 'Link not active', and 'Link available' connected by arrows representing transitions. Some transitions are labeled with actions like 'Initiate change over' or 'Initiate change back'. Numbers 1-8 are used as state identifiers in circles. The diagram is organized into several horizontal levels with different link states.
+
+Signalling link availability
+
+NOTE – Link not active signal represents both link failure and link deactivation. Link active signal represents both link restoration and link activation.
+
+**Figure 6/Q.704 (sheet 1 of 4) – Signalling traffic management overview diagram**
+
+
+
+```
+
+graph TD
+ 5((5)) --> L1[Link inhibited]
+ 5 --> S1[Signalling link congested]
+ 5 --> S2[Signalling link uncongested]
+ L1 --> L2[Link unavailable]
+ S1 --> R1[Route congested]
+ S2 --> R2[Route uncongested]
+ L2 --> L3([Link unavailable (inhibited)])
+ R1 --> L3
+ R2 --> L4([Link available])
+ L3 --> L5[Link blocked]
+ L3 --> L6[Link not active]
+ L3 --> L7[Link uninhibited]
+ 6((6)) --> L5
+ L5 --> L8([Link unavailable, blocked and inhibited])
+ L6 --> 7((7))
+ 7 --> L9([Link unavailable (failed/inactive) inhibited])
+ L7 --> L10[Link available]
+ L10 --> L11([Link available])
+ L9 --> L12[Link blocked]
+ L9 --> L13[Link active]
+ L9 --> L14[Link uninhibited]
+ L12 --> 8((8))
+ L13 --> 9((9))
+ L14 --> 2((2))
+ L8 --> L15[Link inactive]
+ L8 --> L16[Link uninhibited]
+ L8 --> L17[Link unblocked]
+ L15 --> 8((8))
+ L16 --> 3((3))
+ L17 --> 9((9))
+
+```
+
+T1158840-94/d07
+
+Flowchart illustrating Signalling link availability states and transitions. The diagram starts with state 5 and branches into Link inhibited, Signalling link congested, and Signalling link uncongested. It includes transitions for 'Initiate change over' and 'Initiate change back', leading to various states like Link unavailable, Link blocked, Link not active, Link inactive, Link unblocked, and Link active, ending with states 8, 3, 9, and 2.
+
+Signalling link availability
+
+Figure 6/Q.704 (sheet 2 of 4) – Signalling traffic management overview diagram
+
+
+
+```
+
+graph TD
+ A([Route available]) --> B[Signalling route unavailable/restricted*]
+ B --> C[Route unavailable/restricted*]
+ C --> D([Route unavailable/restricted])
+ D --> E[Signalling route available]
+ E --> F[Signalling route available]
+ F --> G([Route available])
+
+```
+
+The flowchart illustrates the state transitions for a signalling route. It begins with a 'Route available' state (oval), which transitions to a 'Signalling route unavailable/restricted\*' state (parallelogram). This is followed by a 'Route unavailable/restricted\*' state (parallelogram), which then transitions to a 'Route unavailable/restricted' state (oval). From there, it goes to a 'Signalling route available' state (parallelogram), which leads to another 'Signalling route available' state (parallelogram), and finally returns to the 'Route available' state (oval). Two actions are indicated: 'Initiate forced/controlled rerouting\*' is associated with the transition from 'Route unavailable/restricted\*' to 'Route unavailable/restricted', and 'Initiate controlled rerouting' is associated with the transition from 'Signalling route available' to 'Signalling route available'.
+
+Flowchart showing signalling route availability status transitions between 'Route available' and 'Route unavailable/restricted' states, triggered by signalling route availability changes and rerouting actions.
+
+T1158850-94/d08
+
+Signalling route availability status
+
+**Figure 6/Q.704 (sheet 3 of 4) – Signalling traffic management overview diagram**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> L1[Link unavailable]
+ Idle1 --> L2[Link available]
+ Idle1 --> R1[Route unavailable]
+ Idle1 --> R2[Route available]
+ Idle1 --> R3[Route restricted]
+ Idle1 --> RS1[Route set congested]
+
+ L1 --> C1([Changeover])
+ C1 --> CE1[Changeover executed]
+ CE1 --> 1_1((1))
+
+ L2 --> CB1([Changeback])
+ CB1 --> CB2[Changeback executed]
+ CB2 --> 1_2((1))
+
+ R1 --> FR1([Forced rerouting])
+ FR1 --> FR2[Forced rerouting executed]
+ FR2 --> 1_3((1))
+
+ R2 --> CR1([Controlled rerouting])
+ CR1 --> CR2[Controlled rerouting executed]
+ CR2 --> 1_4((1))
+
+ R3 --> CR3([Controlled rerouting])
+ CR3 --> CR4[Controlled rerouting executed]
+ CR4 --> 1_5((1))
+
+ RS1 --> SP1([SP(s) congested])
+ SP1 --> IUP1[Inform user parts]
+ IUP1 --> CR5[Controlled rerouting not possible]
+ CR5 --> 1_6((1))
+
+ 1_1 --> CNP1[Changeover not possible]
+ 1_2 --> DU1[Destination(s) unblocked]
+ 1_3 --> FRNP1[Forced rerouting not possible]
+ 1_4 --> DU2[Destination unblocked]
+ 1_5 --> CRNP1[Controlled rerouting not possible]
+
+ CNP1 --> RSU1[Route set(s) unavailable]
+ RSU1 --> SPNA1[SP(s) not accessible]
+ SPNA1 --> 1_7((1))
+
+ DU1 --> RSA1[Route set(s) available]
+ RSA1 --> SPA1[SP(s) accessible]
+ SPA1 --> Idle2([Idle])
+
+ FRNP1 --> RSU2[Route set available]
+ RSU2 --> SPNA2[SP not accessible]
+ SPNA2 --> Idle2
+
+ DU2 --> RSA2[Route set available]
+ RSA2 --> SPA2[SP accessible]
+ SPA2 --> Idle2
+
+ CRNP1 --> ISRM[Inform signalling route management]
+ CRNP1 --> IUP2[Inform user parts]
+ CRNP1 --> Idle2
+
+ T1158860-94/d09
+
+```
+
+Flowchart for Signalling traffic management overview diagram. It starts at 'Idle' and branches into 'Link unavailable', 'Link available', 'Route unavailable', 'Route available', 'Route restricted', and 'Route set congested'. Each branch leads to specific management actions like 'Changeover', 'Changeback', 'Forced rerouting', 'Controlled rerouting', and 'SP(s) congested', eventually returning to 'Idle' or entering intermediate states like 'Route set(s) unavailable' or 'SP(s) not accessible'.
+
+Signalling traffic reconfiguration and flow control
+
+Figure 6/Q.704 (sheet 4 of 4) – Signalling traffic management overview diagram
+
+#### **3.2.8 Signalling link inhibiting**
+
+A signalling link is recognized as inhibited when:
+
+- a) an acknowledgement is received from a remote signalling point in response to an inhibit request sent to the remote end by the local signalling link management. Level 3 has marked the link locally inhibited;
+- b) upon receipt of a request from a remote signalling point to inhibit a link and successful determination that no destination will become inaccessible by inhibiting the link, the link has been marked remotely inhibited by level 3.
+
+#### **3.2.9 Signalling link uninhibiting**
+
+A signalling link previously inhibited is uninhibited when:
+
+- a) a request is received to uninhibit the link from a remote end or from a local routing function;
+- b) an acknowledgement is received from a remote signalling point in response to an uninhibit request sent to the remote end by the local signalling link management.
+
+### **3.3 Procedures used in connection with link status changes**
+
+In this subclause, the procedures relating to each signalling management function, which are applied in connection with link status changes, are listed. See also Figures 6, 7 and 8. Typical examples of the application of the procedures to the particular network cases appear in Recommendation Q.705.
+
+#### **3.3.1 Signalling link failed**
+
+**3.3.1.1** Signalling traffic management: the changeover procedure (see clause 5) is applied, if required, to divert signalling traffic from the unavailable link to one or more alternative links with the objective of avoiding message loss, repetition or mis-sequencing; it includes determination of the alternative link or links where the affected traffic can be transferred and procedures to retrieve messages sent over the failed link but not received by the far end.
+
+**3.3.1.2** Signalling link management: the procedures described in clause 12 are used to restore a signalling link and to make it available for signalling. Moreover, depending on the link set status, the procedures can also be used to activate another signalling link in the same link set to which the unavailable link belongs and to make it available for signalling.
+
+**3.3.1.3** Signalling route management: in the case when the failure of a signalling link causes a signalling route set to become unavailable or restricted1, the signalling transfer point which can no longer route the concerned signalling traffic applies the transfer-prohibited procedures or transfer-restricted procedures described in clause 13.
+
+#### **3.3.2 Signalling link restored**
+
+**3.3.2.1** Signalling traffic management: the changeback procedure (see clause 6) is applied, if required, to divert signalling traffic from one or more links to a link which has become available; it includes determination of the traffic to be diverted and procedures for maintaining the correct message sequence.
+
+**3.3.2.2** Signalling link management: the signalling link deactivation procedure (see clause 12) is used if, during the signalling link failure, another signalling link of the same link set was activated; it is used to assure that the link set status is returned to the same state as before the failure. This requires that the active link activated during the link failure is deactivated and considered no longer available for signalling.
+
+**3.3.2.3** Signalling route management: in the case when the restoration of a signalling link causes a signalling route set to become available, the signalling transfer point which can once again route the concerned signalling traffic applies the transfer-allowed procedures described in clause 13.
+
+
+
+```
+
+graph TD
+ L1([Link inactive]) --> A1[/Activate Link/]
+ A1 --> L2([Link activation])
+ L2 -.->|Initial alignment completed| L3[/Link in service/]
+ L3 -.->|Inform signalling traffic management| L4[/Link active/]
+ L4 --> C2((2))
+ L4 --> LF[/Link failure/]
+ L4 --> LD[/Link de-activation/]
+ L4 --> LB[/Link blocking/inhibiting/]
+ L4 --> LU[/Link un-blocking/uninhibiting/]
+ LF --> LN1[/Link not active/]
+ LN1 -.->|Inform signalling traffic management| LF1([Link failed])
+ LF1 -->|Link restoration| L5[/Link in service/]
+ L5 -.->|Initial alignment completed| L6[/Link active/]
+ L6 -.->|Inform signalling traffic management| C3((2))
+ LD -->|Inform signalling traffic management| LN2[/Link not active/]
+ LN2 --> LI([Link inactive])
+ LB -->|Inform signalling traffic management| LB1[/Link blocked/inhibited/]
+ LB1 -.->|Inform signalling traffic management| C4((2))
+ LU -->|Inform signalling traffic management| LU1[/Link unblocked/uninhibited/]
+ LU1 -.->|Inform signalling traffic management| C5((2))
+
+```
+
+Flowchart of Signalling link management overview diagram. The process starts with 'Link inactive' (oval) leading to 'Activate Link' (parallelogram), which leads to 'Link activation' (oval). From 'Link activation', a dashed line labeled 'Initial alignment completed' leads to 'Link in service' (parallelogram). From 'Link in service', a dashed line labeled 'Inform signalling traffic management' leads to 'Link active' (parallelogram). A circle with the number '2' is connected to this 'Link active' state. The flow then branches into four paths: 1) 'Link failure' (parallelogram) leads to 'Link not active' (parallelogram), which leads to 'Link failed' (oval) via a dashed line labeled 'Inform signalling traffic management'. 'Link failed' leads to 'Link in service' (parallelogram) via a dashed line labeled 'Link restoration'. 'Link in service' leads to 'Link active' (parallelogram) via a dashed line labeled 'Initial alignment completed'. 'Link active' leads to a circle with the number '2' via a dashed line labeled 'Inform signalling traffic management'. 2) 'Link de-activation' (parallelogram) leads to 'Link not active' (parallelogram) via a dashed line labeled 'Inform signalling traffic management'. 'Link not active' leads to 'Link inactive' (oval). 3) 'Link blocking/inhibiting' (parallelogram) leads to 'Link blocked/inhibited' (parallelogram) via a dashed line labeled 'Inform signalling traffic management'. 'Link blocked/inhibited' leads to a circle with the number '2' via a dashed line labeled 'Inform signalling traffic management'. 4) 'Link un-blocking/uninhibiting' (parallelogram) leads to 'Link unblocked/uninhibited' (parallelogram) via a dashed line labeled 'Inform signalling traffic management'. 'Link unblocked/uninhibited' leads to a circle with the number '2' via a dashed line labeled 'Inform signalling traffic management'. The diagram is labeled 'T1158870-94/010' at the bottom right.
+
+**Figure 7/Q.704 – Signalling link management overview diagram**
+
+
+
+Figure 8/Q.704 – Signalling route management overview diagram. The diagram is split into two horizontal sections. The top section shows transitions from an 'Idle' state to various message types: 'Route set unavailable', 'Route set available', 'Transfer restricted message' (TR), 'Transfer prohibited message', and 'Transfer allowed message'. These lead to further actions like 'Transfer prohibited message', 'Transfer allowed message', 'Signalling route restricted', 'Signalling route unavailable', and 'Signalling route available', which then lead to 'Start route set test procedure', 'Stop route set test procedure', or back to 'Idle'. Annotations include 'From adjacent STP' and 'Inform signalling traffic management'. The bottom section shows transitions from an 'Idle' state to 'Route set test message', 'Route set restricted' (TR), 'Transfer controlled message', and 'Signalling route set congestion test message'. These lead to a decision 'Route status correct'. If 'Yes', it goes to connector '1'. If 'No', it goes to 'Status message' and then to connector '1'. Annotations include 'From testing SP', 'To testing SP', and 'MCS'. Both sections end at connector '1' and return to an 'Idle' state. A reference code 'T1158880-94/d11' is present.
+
+**Figure 8/Q.704 – Signalling route management overview diagram**
+
+#### 3.3.3 Signalling link deactivated
+
+##### 3.3.3.1 Signalling traffic management: as specified in 3.3.1.1.
+
+NOTE – The signalling traffic has normally already been removed when signalling link deactivation is initiated.
+
+**3.3.3.2** Signalling link management: if the number of active signalling links in the link set to which the deactivated signalling link belongs has become less than the normal number of active signalling links in that link set, the procedures described in clause 12 may be used to activate another signalling link in the link set.
+
+**3.3.3.3** Signalling route management: as specified in 3.3.1.3.
+
+#### **3.3.4 Signalling link activated**
+
+**3.3.4.1** Signalling traffic management: as specified in 3.3.2.1.
+
+**3.3.4.2** Signalling link management: if the number of active signalling links in the link set to which the activated signalling link belongs has become greater than the normal number of active signalling links in that link set, the procedures described in clause 12 may be used to deactivate another signalling link in the link set.
+
+**3.3.4.3** Signalling route management: as specified in 3.3.2.3.
+
+#### **3.3.5 Signalling link blocked**
+
+**3.3.5.1** Signalling traffic management: as specified in 3.3.1.1.
+
+As a national option, local processor outage may also be applied to the affected signalling link before commencement of the appropriate signalling traffic management option. On completion of that signalling traffic management action, local processor outage is removed from the affected signalling link. No further signalling traffic management will be performed on that affected signalling link until a timer T24 (see 16.8) has expired or been cancelled, thus allowing time for indications from the remote end to stabilize as it carries out any signalling traffic management of its own.
+
+**3.3.5.2** Signalling route management: if the blocking of the link causes a signalling route set to become unavailable or restricted1, the signalling transfer point which can no longer route the concerned signalling traffic applies the transfer-prohibited or transfer-restricted procedures described in clause 13.
+
+#### **3.3.6 Signalling link unblocked**
+
+**3.3.6.1** Signalling traffic management: the actions will be the same as in 3.3.2.1.
+
+**3.3.6.2** Signalling route management: if the link unblocked causes a signalling route set to become available, the signalling transfer point which can once again route the signalling traffic in that route set applies the transfer-allowed procedures described in clause 13.
+
+#### **3.3.7 Signalling link inhibited**
+
+**3.3.7.1** Signalling traffic management: as specified in 3.3.1.1.
+
+**3.3.7.2** Signalling link management: as specified in 3.3.3.2.
+
+#### **3.3.8 Signalling link uninhibited**
+
+**3.3.8.1** Signalling traffic management: as specified in 3.3.2.1.
+
+**3.3.8.2** Signalling link management: as specified in 3.3.4.2.
+
+**3.3.8.3** Signalling route management: if the link uninhibited causes a signalling route set to become available, the signalling transfer point which can once again route the signalling traffic in that route set applies the transfer-allowed procedures described in clause 13.
+
+### **3.4 Status of signalling routes**
+
+A signalling route can be in three states for signalling traffic having the concerned destination; these are available, restricted1, unavailable (see also Figure 6).
+
+#### **3.4.1 Signalling route unavailability**
+
+A signalling route becomes unavailable when a transfer-prohibited message, indicating that signalling traffic towards a particular destination cannot be transferred via the signalling transfer point sending the concerned message, is received (see clause 13).
+
+#### **3.4.2 Signalling route availability**
+
+A signalling route becomes available when a transfer-allowed message, indicating that signalling traffic towards a particular destination can be transferred via the signalling transfer point sending the concerned message, is received (see clause 13).
+
+#### **3.4.3 Signalling route restricted1**
+
+A signalling route becomes restricted when a transfer-restricted message, indicating that the signalling traffic towards a particular destination is being transferred with some difficulty via the signalling transfer point sending the concerned message is received (see clause 13).
+
+### **3.5 Procedures used in connection with route status changes**
+
+In this subclause, the procedures relating to each signalling management function, which in general are applied in connection with route status changes, are listed. See also Figures 6 and 8. Typical examples of the application of the procedures to particular network cases appear in Recommendation Q.705.
+
+#### **3.5.1 Signalling route unavailable**
+
+**3.5.1.1** Signalling traffic management: the forced rerouting procedure (see clause 7) is applied; it is used to transfer signalling traffic to the concerned destination from the link set, belonging to the unavailable route, to an alternative link set which terminates in another signalling transfer point. It includes actions to determine the alternative route.
+
+**3.5.1.2** Signalling route management: because of the unavailability of the signalling route, the network is reconfigured; in the case that a signalling transfer point can no longer route the concerned signalling traffic, it applies the procedures described in clause 13.
+
+#### **3.5.2 Signalling route available**
+
+**3.5.2.1** Signalling traffic management: the controlled rerouting procedure (see clause 8) is applied; it is used to transfer signalling traffic to the concerned destination from a signalling link or link set belonging to an available route, to another link set which terminates in another signalling transfer point. It includes the determination of which traffic should be diverted and procedures for maintaining the correct message sequence.
+
+**3.5.2.2** Signalling route management: because of the restored availability of the signalling route, the network is reconfigured; in the case that a signalling transfer point can once again route the concerned signalling traffic, it applies the procedures described in clause 13.
+
+#### **3.5.3 Signalling route restricted1**
+
+**3.5.3.1** Signalling traffic management: the controlled rerouting procedure (see clause 8) is applied; it is used to transfer signalling traffic to the concerned destination from the link set belonging to the restricted route, to an alternative link set if one is available to give more, if possible, efficient routing. It includes actions to determine the alternative route.
+
+**3.5.3.2** Signalling route management: because of restricted availability of the signalling route, the network routing is, if possible, reconfigured; procedures described in clause 13 are used to advise adjacent signalling points.
+
+### **3.6 Status of signalling points**
+
+A signalling point can be in two states; available or unavailable (see Figure 6). However, implementation dependent congestion states may exist.
+
+#### **3.6.1 Signalling point unavailability**
+
+**3.6.1.1** Unavailability of a signalling point itself: A signalling point becomes unavailable when all connected signalling links are unavailable.
+
+**3.6.1.2** Unavailability of an adjacent signalling point: A signalling point considers that an adjacent signalling point becomes unavailable when:
+
+- all signalling links connected to the adjacent signalling point are unavailable; and
+- the adjacent signalling point is inaccessible.
+
+#### **3.6.2 Signalling point availability**
+
+**3.6.2.1** Availability of a signalling point itself: A signalling point becomes available when at least one signalling link connected to this signalling point becomes available.
+
+**3.6.2.2** Availability of an adjacent signalling point: A signalling point considers that an adjacent signalling point Y becomes available when:
+
+- 1) at least one signalling link connected to Y becomes available at level 3 and the MTP restart procedure (see clause 9) has been completed; or
+- 2) the adjacent signalling point Y becomes accessible:
+ - on the receipt of a transfer allowed message or a transfer restricted1 message;
+ - if an alternative route becomes available again via the corresponding local linkset; or
+ - if a traffic restart allowed message from another adjacent signalling point Z, whose MTP is restarting, is received so that a route towards Y using Z becomes available.
+
+### **3.7 Procedures used in connection with point status changes**
+
+#### **3.7.1 Signalling point unavailable**
+
+There is no specific procedure used when a signalling point becomes unavailable. The transfer prohibited procedure is used to update the status of the recovered routes in all nodes of the signalling network (see 13.2).
+
+#### **3.7.2 Signalling point available**
+
+**3.7.2.1** Signalling traffic management: the MTP restart procedure (see clause 9) is applied; it is used to restart the traffic between the signalling network and the signalling point which becomes available. This restart is based on the following criteria:
+
+- avoid loss of messages;
+- limit the level 3 load due to the restart of a signalling point's MTP;
+- restart, as much as possible, simultaneously in both directions of the signalling relations.
+
+**3.7.2.2** Signalling link management: The first step of the MTP restart procedure attempts to restore the signalling links of the point which becomes available; the signalling link restoration procedure is used (see clause 12);
+
+**3.7.2.3** Signalling route management: The second step of the MTP restart procedure consists of updating the signalling route states before carrying traffic to the point which becomes available and in all adjacent points; the transfer prohibited and transfer restricted procedures1 are used (see clause 13).
+
+**3.7.3** Signalling point congested: (implementation-dependent option, see 11.2.6).
+
+### **3.8 Signalling network congestion**
+
+#### **3.8.1 General**
+
+In this subclause, criteria for the determination of signalling link congestion status and signalling route set congestion status are specified. The procedures relating to each signalling network management function, which in general are applied in connection with congestion status changes, are listed.
+
+#### **3.8.2 Congestion status of signalling links**
+
+**3.8.2.1** When predetermined levels of MSU fill in the transmission or retransmission buffer are crossed, an indication is given to level 3 advising of congestion/congestion abatement. The location and setting of the congestion thresholds are considered to be implementation-dependent.
+
+NOTE – The criterion for setting the congestion thresholds is based on:
+
+- 1) the proportion of the total (transmit and retransmit) buffer capacity that is occupied; and/or
+- 2) the total number of messages in the transmit and retransmit buffers.
+
+(The buffer capacity below the threshold should be sufficient to overcome load peaks due to signalling network management functions and the remaining buffer capacity should allow User Parts time to react to congestion indications before message discard occurs.) The monitoring may be performed in different ways depending on the relative sizes of the transmit and retransmit buffers. In the case of a relatively small retransmit buffer, monitoring of the transmit buffer may be sufficient. In the case of a relatively large retransmit buffer, both the transmit buffer and retransmit buffer occupancies may need to be monitored.
+
+- a) In the international signalling network, one congestion onset and one congestion abatement threshold are provided. The congestion abatement threshold should be placed lower than the congestion onset threshold in order to provide hysteresis during the process of recovering from congestion.
+- b) In national signalling networks, with multiple congestion thresholds, $N$ ( $1 \leq N \leq 3$ ) separate thresholds are provided for detecting the onset of congestion. They are called congestion onset thresholds and are numbered 1, ..., $N$ , respectively. $N$ separate thresholds are provided for monitoring the abatement of congestion. They are called congestion abatement thresholds and are numbered 1, ..., $N$ , respectively.
+
+**3.8.2.2** In national signalling networks with multiple congestion thresholds $N$ separate thresholds are provided for determining whether, under congestion conditions, a message should be discarded or transmitted using the signalling link. They are called congestion discard thresholds and are numbered 1, ..., $N$ , respectively.
+
+Congestion discard threshold $n$ ( $n = 1, \dots, N$ ) is placed higher than congestion onset threshold $n$ in order to minimize message loss under congestion conditions.
+
+Congestion discard threshold $n$ ( $n = 1, \dots, N - 1$ ) should be placed at or lower than congestion onset threshold $n + 1$ in order to make congestion control effective.
+
+When the current buffer occupancy does not exceed congestion discard threshold 1, the current signalling link discard status is assigned the zero value.
+
+Each congestion abatement threshold should be placed lower than the corresponding congestion onset threshold in order to provide hysteresis during the process of recovering from congestion.
+
+In national signalling networks with $N > 1$ , the congestion abatement threshold $n$ ( $n = 2, \dots, N$ ) should be placed higher than the congestion onset threshold $n - 1$ so as to allow for a precise determination of signalling link congestion status.
+
+Congestion abatement threshold 1 should be placed higher than the normally engineered buffer occupancy of a signalling link.
+
+Under normal operation, when the signalling link is uncongested, the signalling link congestion status is assigned the zero value.
+
+At the onset of congestion, when the buffer occupancy is increasing, the signalling link congestion status is determined by the highest congestion onset threshold exceeded by the buffer occupancy. That is, if congestion onset threshold $n$ ( $n = 1, \dots, N$ ) is the highest congestion onset threshold exceeded by the current buffer occupancy, the current signalling link congestion status is assigned the value $n$ (see Figure 8a).
+
+
+
+The diagram illustrates a buffer for a signalling link. Data enters from 'From level 3' on the left and exits 'To signalling link' on the right. The buffer is divided into segments. Two vertical lines represent congestion onset thresholds: 'Congestion onset threshold $n + 1$ ' and 'Congestion onset threshold $n$ '. An arrow points from the 'Congestion onset threshold $n$ ' line to the left, indicating the current buffer occupancy level. Below the buffer, an upward-pointing arrow is labeled 'Buffer occupancy', indicating the current level of data in the buffer. The text 'T1158890-94/d12' is located at the bottom right of the buffer diagram.
+
+Diagram of a buffer showing congestion onset thresholds n and n+1. Data flows from 'From level 3' to 'To signalling link'. Buffer occupancy is shown increasing towards threshold n.
+
+**Figure 8a/Q.704 – Signalling link congestion status = $n$ (congestion onset)**
+
+At the abatement of congestion, when the buffer occupancy is decreasing, the signalling link congestion status is determined by the lowest congestion abatement threshold below which the buffer occupancy has dropped. That is, if congestion abatement threshold $n$ ( $n = 1, \dots, N$ ) is the lowest congestion abatement threshold below which the current buffer occupancy has dropped, the current signalling link congestion status is assigned the value $n - 1$ (see Figure 8b).
+
+The use of the signalling link congestion status is specified in 2.3.5.2.
+
+
+
+From level 3 →
+
+... | $n + 1$ | $n$ | ...
+
+→ To signalling link
+
+T1158900-94/d13
+
+↑ Buffer occupancy
+
+—— Congestion onset threshold
+- - - - Congestion abatement threshold
+
+Figure 8b/Q.704: Buffer occupancy diagram for congestion abatement. The diagram shows a horizontal buffer divided into segments. An arrow labeled 'From level 3' enters from the left, and an arrow labeled 'To signalling link' exits to the right. A vertical arrow labeled 'Buffer occupancy' points to a specific point in the buffer. Above the buffer, a bracket labeled 'n' spans a segment, and another bracket labeled 'n + 1' spans the next segment. A solid vertical line marks the 'Congestion onset threshold' and a dashed vertical line marks the 'Congestion abatement threshold'. The text 'T1158900-94/d13' is at the bottom right.
+
+**Figure 8b/Q.704 – Signalling link congestion status = $n$ (congestion abatement)**
+
+When the current buffer occupancy exceeds congestion discard threshold $n$ ( $n = 1, \dots, N - 1$ ), but does not exceed congestion discard threshold $n + 1$ , the current signalling link discard status is assigned the value $n$ (see Figure 8c).
+
+When the current buffer occupancy exceeds congestion discard threshold $N$ , the current signalling link discard status is assigned the value $N$ .
+
+The use of the signalling link discard status is specified in 2.3.5.2.
+
+**3.8.2.3** In national signalling networks using multiple signalling link congestion states without congestion priority, $S + 1$ ( $1 \leq S \leq 3$ ) levels of signalling link congestion status are accommodated in the signalling network, 0 being the lowest and $S$ the highest.
+
+
+
+From level 3 →
+
+... | $n + 1$ | $n + 1$ | $n$ | $n$ | ...
+
+→ To signalling link
+
+T1158910-94/d14
+
+↑ Buffer occupancy
+
+—— Congestion onset threshold
+- - - - Congestion discard threshold
+
+Figure 8c/Q.704: Buffer occupancy diagram for congestion discard. The diagram shows a horizontal buffer divided into segments. An arrow labeled 'From level 3' enters from the left, and an arrow labeled 'To signalling link' exits to the right. A vertical arrow labeled 'Buffer occupancy' points to a specific point in the buffer. Above the buffer, a bracket labeled 'n' spans a segment, and another bracket labeled 'n + 1' spans the next segment. A dashed vertical line marks the 'Congestion onset threshold' and a solid vertical line marks the 'Congestion discard threshold'. The text 'T1158910-94/d14' is at the bottom right.
+
+**Figure 8c/Q.704 – Signalling link congestion status = $n$**
+
+The signalling link congestion status is determined by a timing mechanism after the buffer occupancy exceeds the congestion onset threshold, or drops below the congestion abatement threshold. Under normal operation, when the signalling link is uncongested, the signalling link congestion status is assigned the zero value.
+
+At the onset of congestion, when the buffer occupancy exceeds the congestion onset threshold, the first signalling link congestion status is assigned a value $s$ , predetermined in the signalling network.
+
+If the signalling link congestion status is set to $s$ ( $s = 1, \dots, S - 1$ ) and the buffer occupancy continues to be above the congestion onset threshold during Tx, the signalling link congestion status is updated by the new value $s + 1$ .
+
+If the signalling link congestion status is set to $s(s = 1, \dots, S)$ and the buffer occupancy continues to be below the abatement threshold during $T_y$ , the signalling link congestion status is updated by the new value $s - 1$ .
+
+Otherwise, the current signalling link congestion status is maintained (see Figure 8d).
+
+The congestion abatement threshold should be placed lower than the congestion onset threshold.
+
+
+
+```
+
+stateDiagram-v2
+ direction LR
+ 0 --> 1: (T_x, l > l_o)
+ 1 --> 2: (T_x, l > l_o)
+ 2 --> 3: (T_x, l > l_o)
+ 3 --> 2: (T_y, l < l_a)
+ 2 --> 1: (T_y, l < l_a)
+ 1 --> 0: (T_y, l < l_a)
+ 0 --> 0: (-, l > l_o)
+
+```
+
+0~3 Congestion status $s$
+ $l$ Buffer occupancy
+ $l_o$ Congestion onset threshold
+ $l_a$ Congestion abatement threshold
+ $(.)$ Transition condition
+ $T_x$ Timing for updating $s \rightarrow s + 1$
+ $T_y$ Timing for updating $s \rightarrow s - 1$
+ $-$ Timing is zero
+
+State transition diagram for signalling link congestion status with four states (0, 1, 2, 3). Transitions from 0 to 1, 1 to 2, and 2 to 3 are triggered by (Tx, l > lo). Transitions from 3 to 2, 2 to 1, and 1 to 0 are triggered by (Ty, l < la). A self-loop on state 0 is triggered by (-, l > lo).
+
+**Figure 8d/Q.704 – An example of signalling link congestion status
+(using multiple signalling link congestion states without congestion priority)**
+
+#### 3.8.3 Procedures used in connection with link congestion status changes
+
+In this subclause, the procedures relating to each signalling network management function, which in general are applied in connection with link congestion status changes, are listed.
+
+Signalling route management: in the case when the congestion of a signalling link causes a signalling route set to become congested, the transfer-controlled procedure (see 13.6 and 13.7) is used, if required, to notify originating signalling points that they should reduce the concerned signalling traffic towards the affected destination.
+
+#### 3.8.4 Congestion status of signalling route sets
+
+At each originating signalling point, there is associated with each signalling route set a congestion status, which indicates the degree of congestion in the signalling route set.
+
+- a) In the international signalling network, two states are provided, congested and uncongested.
+If a link in a signalling route towards a given destination becomes congested, the congestion status of the signalling route set towards the affected destination is changed to congested.
+When a transfer controlled message relating to a given destination is received, the congestion status of the signalling route set towards the affected destination is indicated to the level 4 User Parts in accordance with the transfer-controlled procedure specified in 13.6. The congestion status is not retained by level 3 at the receiving signalling point.
+
+- b) In national signalling networks with multiple congestion levels1 corresponding to the $N + 1$ levels of signalling link congestion, there are $N + 1$ values of signalling route set congestion status, with 0 being the lowest and $N$ the highest.
+
+Normally the congestion status of a signalling route set is assigned the zero value, indicating that the signalling route set is uncongested.
+
+If a signalling link in the signalling route set to a given destination becomes congested, the congestion status of the signalling route set is assigned the value of the signalling link congestion status, if it is higher than the current signalling route set congestion status.
+
+When a transfer-controlled message relating to a given destination is received, the congestion status of the signalling route set towards that destination is updated, in accordance with the transfer-controlled procedure as specified in 13.7.
+
+The congestion status of the signalling route set towards that destination may be decremented in accordance with the signalling-route-set-congestion-test procedure as specified in 13.9.
+
+- c) In national signalling networks using multiple congestion levels1 without congestion priority, there are $S + 1$ values of signalling route set congestion states, with 0 being the lowest and $S$ the highest.
+
+Normally the congestion status of a signalling route set is assigned the zero value, indicating that the signalling route set is uncongested.
+
+If a local signalling link in the signalling route set to a given destination becomes congested, the congested status of the signalling route set is assigned the value of the signalling link congestion status, if it is larger than the current signalling route set congestion status.
+
+When a transfer-controlled message relating to a given destination is received, the congestion status of the affected destination is indicated to the level 4 user parts in accordance with the transfer-controlled procedure specified in 13.8.
+
+#### **3.8.5 Procedures used in connection with route set congestion status changes**
+
+In this subclause, the procedures relating to each signalling network management function, which in general are applied in connection with route set congestion status changes, are listed.
+
+**3.8.5.1** Signalling traffic management: the signalling traffic flow control procedure (see clause 11) is applied; it is used to regulate the input of signalling traffic from User Parts to the concerned signalling route set.
+
+**3.8.5.2** Signalling route management: as a national option, the signalling-route-set-congestion-test procedure (see 13.9) is applied; it is used to update the congestion status of the concerned signalling route set until the congestion status is reduced to the zero value.
+
+## **4 Signalling traffic management**
+
+### **4.1 General**
+
+**4.1.1** The signalling traffic management function is used, as indicated in clause 3, to divert signalling traffic from signalling links or routes, or to temporarily reduce it in quantity in the case of congestion.
+
+**4.1.2** The diversion of traffic in the cases of unavailability or availability or restriction of signalling links and routes is typically made by means of the following basic procedures, included in the signalling traffic management function:
+
+- signalling link unavailability (failure, deactivation, blocking or inhibiting): the changeover procedure (see clause 5) is used to divert signalling traffic to one or more alternative links (if any);
+- signalling link availability (restoration, activation, unblocking or uninhibiting): the changeback procedure (see clause 6) is used to divert signalling traffic to the link made available;
+- signalling route unavailability: the forced rerouting procedure (see clause 7) is used to divert signalling traffic to an alternative route (if any);
+- signalling route availability: the controlled rerouting procedure (see clause 8) is used to divert signalling traffic to the route made available;
+- signalling route restricted1: the controlled rerouting procedure (see clause 8) is used to divert signalling traffic to an alternative route (if any);
+- signalling point availability: the MTP restart procedure (see clause 9) is used to divert the signalling traffic to (or via) the point made available.
+
+Each procedure includes different elements of procedure, the application of one or more of which depends on the particular circumstances, as indicated in the relevant subclauses. Moreover, these procedures include a modification of the signalling routing, which is made in a systematic way, as described in 4.2 to 4.7.
+
+**4.1.3** The signalling traffic flow control procedures are used in the case of congestion, in order to limit signalling traffic at its source. The procedures are specified in clause 11.
+
+### **4.2 Normal routing situation**
+
+**4.2.1** Signalling traffic to be sent to a particular signalling point in the network is normally routed to one or, in the case of load sharing between link sets in the international network, two link sets. A load sharing collection of two or more link sets is called a combined link set. Within a link set, a further routing may be performed in order to load share the traffic over the available signalling links (see clause 2).
+
+To cater for the situations when signalling links or routes become unavailable, alternative routing data are defined.
+
+For each destination which may be reached from a signalling point, one or more alternative link sets (combined link sets) are allocated. An alternative combined link set may consist of two or more (or all) of the remaining available link sets, which may carry signalling traffic towards the concerned destination. The possible link set (combined link sets) appear in a certain priority order. The link set (combined link set) having the highest priority is used whenever it is available. It is defined that the normal link set (combined link set) for traffic to the concerned destination. The link set (combined link set) which is in use at a given time is called the current link set (combined link set). The current link set (combined link set) consists either of the normal link set (combined link set) or of an alternative link set (combined link set).
+
+For each signalling link, the remaining signalling links in the link set are alternative links. The signalling links of a link set are arranged in a certain priority order. Under normal conditions the signalling link (or links) having the highest priority is used to carry the signalling traffic.
+
+These signalling links are defined as normal signalling links, and each portion of load shared traffic has its own normal signalling link. Signalling links other than normal may be active signalling links (but not carrying any signalling traffic at the time) or inactive signalling links (see clause 12).
+
+**4.2.2** Message routing (normal as well as alternative) is in principle independently defined at each signalling point. Thus, signalling traffic between two signalling points may be routed over different signalling links or paths in the two directions.
+
+### **4.3 Signalling link unavailability**
+
+**4.3.1** When a signalling link becomes unavailable (see 3.2) signalling traffic carried by the link is transferred to one or more alternative links by means of a changeover procedure. The alternative link or links are determined in accordance with the following criteria.
+
+**4.3.2** In the case when there is one or more alternative signalling links available in the link set to which the unavailable link belongs, the signalling traffic is transferred within the link set to:
+
+- a) an active and unblocked signalling link, currently not carrying any traffic. If no such signalling link exists, the signalling traffic is transferred to;
+- b) one or possibly more than one signalling link currently carrying traffic. In the case of transfer to one signalling link, the alternative signalling link is that having the highest priority of the signalling links in service.
+
+**4.3.3** In the case when there is no alternative signalling link within the link set to which the unavailable signalling link belongs, the signalling traffic is transferred to one or more alternative link sets (combined link sets) in accordance with the alternative routing defined for each destination. For a particular destination, the alternative link set (combined link set) is the link set (combined link set) in service having the highest priority.
+
+Within a new link set, signalling traffic is distributed over the signalling links in accordance with the routing currently applicable for that link set; i.e. the transferred traffic is routed in the same way as the traffic already using the link set.
+
+### **4.4 Signalling link availability**
+
+**4.4.1** When a previously unavailable signalling link becomes available again (see 3.2), signalling traffic may be transferred to the available signalling link by means of the changeback procedure. The traffic to be transferred is determined in accordance with the following criteria.
+
+**4.4.2** In the case when the link set, to which the available signalling link belongs, already carries signalling traffic on other signalling links in the link set, the traffic to be transferred includes the traffic for which the available signalling link is the normal one. Note that the assignment of the normal traffic to a signalling link may be changed during the changeback process taking into account, for example, system performance.
+
+The normal traffic is transferred from one or more signalling links, depending on the criteria applied when the signalling link became unavailable (see 4.3.2), and upon the criteria applied if any of the alternative signalling link(s) themselves became unavailable, or available, in the meantime.
+
+If signalling links in the linkset are still unavailable, and if it is required for load balancing purposes, signalling traffic extra to that normally carried by any link might also be identified for diversion to the signalling link made available, and to other available links in the linkset.
+
+This extra traffic is transferred from one or more signalling links.
+
+**4.4.3** In the case when the link set (combined link set) to which the available signalling links belong, does not carry any signalling traffic [i.e. a link set (combined link set) has become available], the traffic to be transferred is the traffic for which the available link set (combined link set) has higher priority than the link set (combined link set) currently used.
+
+The traffic is transferred from one or more link sets (combined link sets) and from one or more signalling links within each link set.
+
+### **4.5 Signalling route unavailability**
+
+When a signalling route becomes unavailable (see 3.4), signalling traffic currently carried by the unavailable route is transferred to an alternative route by means of forced re-routing procedure. The alternative route (i.e. the alternative link set or link sets) is determined in accordance with the alternative routing defined for the concerned destination (see 4.3.3).
+
+### **4.6 Signalling route availability**
+
+When a previously unavailable signalling route becomes available again (see 3.4), signalling traffic may be transferred to the available route by means of a controlled rerouting procedure. This is applicable in the case when the available route (link set) has higher priority than the route (link set) currently used for traffic to the concerned destination (see 4.4.3).
+
+The transferred traffic is distributed over the links of the new link set in accordance with the routing currently applicable for that link set.
+
+### **4.7 Signalling route restriction1**
+
+When a signalling route becomes restricted (see 3.4), signalling traffic carried by the restricted route is, if possible, transferred to an alternative route by means of the controlled rerouting procedure, if an equal priority alternative is available and not restricted. The alternative route is determined in accordance with alternate routing defined for the concerned destination (see 4.3.3).
+
+### **4.8 Signalling point availability**
+
+When a previously unavailable signalling point becomes available (see 3.6), signalling traffic may be transferred to the available point by means of the MTP restart procedure (see clause 9).
+
+## **5 Changeover**
+
+### **5.1 General**
+
+**5.1.1** The objective of the changeover procedure is to ensure that signalling traffic carried by the unavailable signalling link is diverted to the alternative signalling link(s) as quickly as possible while avoiding message loss, duplication or mis-sequencing. For this purpose, in the normal case the changeover procedure includes buffer updating and retrieval, which are performed before reopening the alternative signalling link(s) to the diverted traffic. Buffer updating consists of identifying all those messages in the retransmission buffer of the unavailable signalling link which have not been received by the far end. This is done by means of a hand-shake procedure, based on changeover messages, performed between the two ends of the unavailable signalling link. Retrieval consists of transferring the concerned messages to the transmission buffer(s) of the alternative link(s).
+
+**5.1.2** Changeover includes the procedures to be used in the case of unavailability (due to failure, blocking or inhibiting) of a signalling link, in order to divert the traffic pertaining to that signalling link to one or more alternative signalling links.
+
+These signalling links can be carrying their own signalling traffic and this is not interrupted by the changeover procedure.
+
+The different network configurations to which the changeover procedure may be applied are described in 5.2.
+
+The criteria for initiation of changeover, as well as the basic actions to be performed, are described in 5.3.
+
+Procedures necessary to cater for equipment failure or other abnormal conditions are also provided.
+
+### **5.2 Network configurations for changeover**
+
+**5.2.1** Signalling traffic diverted from an unavailable signalling link is routed by the concerned signalling point according to the rules specified in clause 4. In summary, two alternative situations may arise (either for the whole diverted traffic or for traffic relating to each particular destination):
+
+- i) traffic is diverted to one or more signalling links of the same link set; or
+- ii) traffic is diverted to one or more different link sets.
+
+**5.2.2** As a result of these arrangements, and of the message routing function described in clause 2, three different relationships between the new signalling link and the unavailable one can be identified, for each particular traffic flow. These three basic cases may be summarized as follows:
+
+- a) the new signalling link is parallel to the unavailable one (see Figure 9);
+- b) the new signalling link belongs to a signalling route other than that to which the unavailable signalling link belongs, but this signalling route still passes through the signalling point at the far end of the unavailable signalling link (see Figure 10);
+- c) the new signalling link belongs to a signalling route other than that to which the unavailable signalling link belongs, and this signalling route does not pass through the signalling point acting as signalling transfer point, at the far end of the unavailable signalling link (see Figure 11).
+
+Only in the case of c) does a possibility of message mis-sequencing exist: therefore its use should take into account the overall service dependability requirements described in Recommendation Q.706.
+
+### **5.3 Changeover initiation and actions**
+
+**5.3.1** Changeover is initiated at a signalling point when a signalling link is recognized as unavailable according to the criteria listed in 3.2.2.
+
+The following actions are then performed:
+
+- a) transmission and acceptance of message signal units on the concerned signalling link is terminated;
+- b) transmission of link status signal units or fill in signal units, as described in 5.3/Q.703 takes place;
+- c) the alternative signalling link(s) are determined according to the rules specified in clause 4;
+- d) a procedure to update the content of the retransmission buffer of the unavailable signalling link is performed as specified in 5.4 below;
+- e) signalling traffic is diverted to the alternative signalling link(s) as specified in 5.5 below.
+
+In addition, if traffic towards a given destination is diverted to an alternative signalling link terminating in a signalling transfer point not currently used to carry traffic towards that destination, a transfer-prohibited procedure is performed as specified in 13.2.
+
+**5.3.2** In the case when there is no traffic to transfer from the unavailable signalling link action, only item b) of 5.3.1 is required.
+
+
+
+Diagram of a changeover to a parallel link. A horizontal line with two circles at its ends represents a link. A dashed arrow points from the left circle to the right circle. A solid arrow points from the left circle to the right circle, passing through a cross mark on the horizontal line. The text 'T1158930-94/d16' is at the bottom right.
+
+**Figure 9/Q.704 – Example of changeover to a parallel link**
+
+
+
+Diagram of a changeover to a signalling route passing through the remote signalling point. A horizontal line with two circles at its ends represents a link. A dashed arrow points from the left circle to the right circle. A solid arrow points from the left circle to a square box below the right circle, and then from the square box to the right circle. The text 'T1158940-94/d17' is at the bottom right.
+
+**Figure 10/Q.704 – Example of changeover to a signalling route passing through the remote signalling point**
+
+
+
+Diagram of a changeover to a signalling route not passing through the remote signalling point. A horizontal line with two circles at its ends represents a link. A dashed arrow points from the left circle to the right circle. A solid arrow points from the left circle to a square box below the right circle, and then from the square box to the right circle. The text 'T1158950-94/d18' is at the bottom right.
+
+**Figure 11/Q.704 – Example of changeover to a signalling route not passing through the remote signalling point**
+
+**5.3.3** If no alternative signalling link exists for signalling traffic towards one or more destinations, the concerned destination(s) are declared inaccessible and the following actions apply:
+
+- i) the routing of the concerned signalling traffic is blocked and the concerned messages already stored in the transmission and retransmission buffers of the unavailable signalling link, as well as those received subsequently, are discarded;3
+- ii) a command is sent to the User Part(s) (if any) in order to stop generating the concerned signalling traffic;
+- iii) the transfer-prohibited procedure is performed, as specified in 13.2;
+- iv) the appropriate signalling link management procedures are performed, as specified in clause 12.
+
+3 The adequacy of this procedure to meet the acceptable dependability objective in terms of loss of messages requires further study.
+
+**5.3.4** In some cases of failures or in some network configurations, the normal buffer updating and retrieval procedures described in 5.4 and 5.5 cannot be accomplished. In such cases, the emergency changeover procedures described in 5.6 apply.
+
+Other procedures to cover possible abnormal cases appear in 5.7.
+
+### **5.4 Buffer updating procedure**
+
+**5.4.1** When a decision to changeover is made, a changeover order is sent to the remote signalling point. In the case that the changeover was initiated by the reception of a changeover order (see 5.2), a changeover acknowledgement is sent instead.
+
+A changeover order is always acknowledged by a changeover acknowledgement, even when changeover has already been initiated in accordance with another criterion.
+
+No priority is given to the changeover order or changeover acknowledgement in relation to the normal traffic of the signalling link on which the message is sent.
+
+**5.4.2** The changeover order and changeover acknowledgement are signalling network management messages and contain the following information:
+
+- the label, indicating the destination and originating signalling points and the identity of the unavailable signalling link;
+- the changeover-order (or changeover-acknowledgement) signal; and
+- the forward sequence number of the last message signal unit accepted from the unavailable signalling link.
+
+Formats and codes of the changeover order and the changeover acknowledgement appear in clause 15.
+
+**5.4.3** Upon reception of a changeover order or changeover acknowledgement, the retransmission buffer of the unavailable signalling link is updated (except as noted in 5.6), according to the information contained in the message. The message signal units successive to that indicated by the message are those which have to be retransmitted on the alternative signalling link(s), according to the retrieval and diversion procedure.
+
+### **5.5 Retrieval and diversion of traffic**
+
+When the procedure to update the retransmission buffer content is completed, the following actions are performed:
+
+- the routing of the signalling traffic to be diverted is changed;
+- the signal traffic already stored in the transmission buffers and retransmission buffer of the unavailable signalling link is sent directly towards the new signalling link(s), according to the modified routing.
+
+The diverted signalling traffic will be sent towards the new signalling link(s) in such a way that the correct message sequence is maintained. The diverted traffic has no priority in relation to normal traffic already conveyed on the signalling link(s).
+
+### **5.6 Emergency changeover procedures**
+
+**5.6.1** Due to the failure in a signalling terminal, it may be impossible for the corresponding end of the faulty signalling link to determine the forward sequence number of the last message signal unit accepted over the unavailable link. In this case, the concerned end accomplishes, if possible, the buffer updating procedures described in 5.4 but it makes use of an emergency changeover order or an emergency changeover acknowledgement instead of the corresponding normal message; these
+
+emergency messages, the format of which appears in clause 15, do not contain the forward sequence number of the last accepted message signal unit. Furthermore, the signalling link is taken out of service, i.e. the concerned end initiates, if possible, the sending of *out-of-service* link status signal units on the unavailable link (see 5.3/Q.703).
+
+When the other end of the unavailable signalling link receives the emergency changeover order or acknowledgement, it accomplishes the changeover procedures described in 5.4 and 5.5, the only difference being that it does not perform either buffer updating or retrieval. Instead, it directly starts sending the signalling traffic not yet transmitted on the unavailable link on the alternative signalling link(s).
+
+The use of normal or emergency changeover messages depends on the local conditions of the sending signalling point only, in particular:
+
+- an emergency changeover order is acknowledged by a changeover acknowledgement if the local conditions are normal; and
+- a changeover order is acknowledged by an emergency changeover acknowledgement if there are local fault conditions.
+
+**5.6.2** Time-controlled changeover is initiated when the exchange of changeover messages is not possible or not desirable, i.e. if any (or several) of the following cases apply:
+
+- i) No signalling path exists between the two ends of the unavailable link, so that the exchange of changeover messages is impossible.
+- ii) Processor outage indication is received on a link. In this case, if the remote processor outage condition is only transitory, sending of a changeover order could result in failure of the link.
+- iii) A signalling link currently carrying traffic has been marked (locally or remotely) inhibited. In this case, time controlled changeover is used to divert traffic for the inhibited link without causing the link to fail.
+
+When the concerned signalling point decides to initiate changeover in such circumstances, after the expiry of a time T1 (see 16.8), it starts signalling traffic not yet transmitted on the unavailable signalling link on the alternative link(s); the purpose of withholding traffic for the time T1 (see 16.8) is to reduce the probability of message mis-sequencing.
+
+An example of such a case appears in Annex A/Q.705.
+
+In the abnormal case when the concerned signalling point is not aware of the situation, it will start the normal changeover procedure and send a changeover order; in this case it will receive no changeover message in response and the procedure will be completed as indicated in 5.7.2. Possible reception of a transfer-prohibited message (sent by an involved signalling transfer point on reception of the changeover order, see 13.2) will not affect changeover procedures.
+
+If time-controlled changeover has been initiated according to case ii) above and if a changeover order is received from the remote and during the Time T1, it is advantageous to switch to the normal changeover procedure including retrieval because unnecessary message loss or sending of old messages is avoided in a simple way. The ability to perform this switch is considered to be implementation dependent. A changeover acknowledgement however, must be returned in any case in order to assure the normal completion of the changeover procedure at the remote end. If a changeover order is received after timer T1 has expired time-controlled changeover is completed (if not yet done) and an emergency changeover acknowledgement is sent to the remote end.
+
+In the case that processor outage is of long-term, the remote side completes the time-controlled changeover procedure. In order to avoid sending out old messages (see clause 8/Q.703) the level 2 buffers on both sides of the link should be flushed immediately, when the local/remote processor outage state terminates. How the flushing is performed is implementation dependent. The decision
+
+whether processor outage is of long-term is a local thing. At the remote side long-term processor outage occurs when the time-controlled changeover timer T1 expires. At the local side an equivalent timer is used in quite the same way.
+
+**5.6.3** Due to failures, it may be impossible for a signalling point to perform retrieval even if it has received the retrieval information from the far end of the unavailable signalling link. In this case, it starts sending new traffic on reception of the changeover message (or on time-out expiry, see 5.6.2 and 5.7.2); no further actions in addition to the other normal changeover procedures are performed.
+
+### **5.7 Procedures in abnormal conditions**
+
+**5.7.1** The procedures described in this subclause allow the completion of the changeover procedures in abnormal cases other than those described in 5.6.
+
+**5.7.2** If no changeover message in response to a changeover order is received within a timer T2 (see 16.8), new traffic is started on the alternative signalling link(s).
+
+**5.7.3** If a changeover order or acknowledgement containing an unreasonable value of the forward sequence number is received, no buffer updating or retrieval is performed, and new traffic is started on the alternative signalling link(s).
+
+**5.7.4** If a changeover acknowledgement is received without having previously sent a changeover order, no action is taken.
+
+**5.7.5** If a changeover order is received relating to a particular signalling link after the completion of changeover from that signalling link, an emergency changeover acknowledgement is sent in response, without any further action.
+
+## **6 Changeback**
+
+### **6.1 General**
+
+**6.1.1** The objective of the changeback procedure is to ensure that signalling traffic is diverted from the alternative signalling link(s) to the signalling link made available as quickly as possible, while avoiding message loss, duplication or mis-sequencing. For this purpose (in the normal case), changeback includes a procedure to control the message sequence.
+
+**6.1.2** Changeback includes the basic procedures to be used to perform the opposite action to changeover, i.e. to divert traffic from the alternative signalling link(s) to a signalling link which has become available (i.e. it was uninhibited, restored or unblocked). The characteristics of the alternative signalling link(s) from which changeback can be made are described in 5.2. In all the cases mentioned in 5.2, the alternative signalling links can be carrying their own signalling traffic and this is not interrupted by the changeback procedures.
+
+Procedures necessary to cater for particular network configuration or other abnormal conditions are also provided.
+
+NOTE – The term "alternative signalling link(s)" refers to signalling link(s) terminating in the signalling point at which a changeback is initiated (see also clause 4).
+
+### **6.2 Changeback initiation and actions**
+
+**6.2.1** Changeback is initiated at a signalling point when a signalling link is restored, unblocked or uninhibited, and therefore it becomes once again available, according to the criteria listed in 3.2.3 and 3.2.7. The following actions are then performed:
+
+- a) the alternative signalling link(s) to which traffic normally carried by the signalling link made available was previously diverted (e.g. on occurrence of a changeover), are determined. To this set are added, if applicable, other links determined as defined in 4.4.2;
+- b) signalling traffic is diverted (if appropriate, according to the criteria specified in clause 4) to the concerned signalling link by means of the sequence control procedure specified in 6.3; traffic diversion can be performed at the discretion of the signalling point initiating changeback, as follows:
+ - i) individually for each traffic flow (i.e. on destination basis);
+ - ii) individually for each alternative signalling link (i.e. for all the destinations previously diverted on that alternative signalling link);
+ - iii) at the same time for a number of, or for all the alternative signalling links.
+
+On occurrence of changeback, it may happen that traffic towards a given destination is no longer routed via a given adjacent signalling transfer point, towards which a transfer-prohibited procedure was previously performed on occurrence of changeover (see 5.3.1); in this case a transfer-allowed procedure is performed, as specified in 13.3.
+
+In addition, if traffic towards a given destination is diverted to an alternative signalling link terminating in a signalling transfer point not currently used to carry traffic toward that destination, a transfer-prohibited procedure is performed as specified in 13.2.
+
+**6.2.2** In the case when there is no traffic to transfer to the signalling link made available, none of the previous actions are performed.
+
+**6.2.3** In the case that the signalling link made available can be used to carry signalling traffic towards a non-adjacent destination which was previously declared inaccessible, the following actions apply:
+
+- i) the routing of the concerned signalling traffic is unblocked and transmission of the concerned messages (if any) is started on the link made available;
+- ii) an indication is sent to the User Part(s) (if any) to restart the concerned signalling traffic;
+- iii) the transfer-allowed procedure is performed, as specified in 13.3. However, in national networks, when the recovered link is not on the normal route for that destination, the transfer-restricted1 procedure may be performed as specified in 13.4;
+- iv) the transfer-prohibited procedure is performed as specified in 13.2.2 i).
+
+**6.2.4** In the case that the signalling link made available will be the first link to be used on the normal route towards a destination previously declared restricted, the status of the route is changed to available and the transfer-allowed procedure is performed as specified in 13.3.
+
+**6.2.5** If the signalling point at the far end of the link made available currently is inaccessible, from the signalling point initiating changeback (see clause 9 on MTP Restart), the sequence control procedure specified in 6.3 (which requires communication between the two concerned signalling points) does not apply; instead, the time-controlled diversion specified in 6.4 is performed. This is made also when the concerned signalling points are accessible, but there is no signalling route to it using the same outgoing signalling link(s) (or one of the same signalling links) from which traffic will be diverted.
+
+The time-controlled diversion procedure may also be used for the changeback between different link sets instead of the sequence control procedure in order to avoid possible message mis-sequencing (see Note) or problems with multiple parallel changebacks.
+
+NOTE – The sequence control procedure can only guarantee correct sequencing of MSUs in all cases if the alternative link terminates in the same signalling point (i.e. the destination of the changeback declaration) as the newly available one.
+
+### 6.3 Sequence control procedure
+
+**6.3.1** When a decision is made at a given signalling point to divert a given traffic flow (towards one or more destinations) from an alternative signalling link to the signalling link made available, the following actions are performed if possible (see 6.4):
+
+- i) transmission of the concerned traffic on the alternative signalling link is stopped; such traffic is stored in a *changeback buffer*;
+- ii) a changeback declaration is sent to the remote signalling point of the signalling link made available via the concerned alternative signalling link; this message indicates that no more message signal units relating to the traffic being diverted to the link made available will be sent on the alternative signalling link.
+
+**6.3.2** The concerned signalling point will restart diverted traffic over the signalling link made available when it receives a changeback acknowledgement from the far signalling point of the link made available; this message indicates that all signal messages relating to the concerned traffic flow and routed to the remote signalling point via the alternative signalling link have been received. The remote signalling point will send the changeback acknowledgement to the signalling point initiating changeback in response to the changeback declaration; any available signalling route between the two signalling points can be used to carry the changeback acknowledgement.
+
+**6.3.3** The changeback declaration and changeback acknowledgement are signalling network management messages and contain:
+
+- the label, indicating the destination and originating signalling points, and the identity of the signalling link to which traffic will be diverted;
+- the changeback-declaration (or changeback-acknowledgement) signal; and
+- the changeback code.
+
+Formats and codes of the changeback-declaration and changeback-acknowledgement appear in clause 15.
+
+**6.3.4** A particular configuration of the changeback code is autonomously assigned to the changeback declaration by the signalling point initiating changeback; the same configuration is included in the changeback acknowledgement by the acknowledging signalling point. This allows discrimination between different changeback declarations and acknowledgements when more than one sequence control procedures are initiated in parallel, as follows.
+
+**6.3.5** In the case that a signalling point intends to initiate changeback in parallel from more than one alternative signalling link, a sequence control procedure is accomplished for each involved signalling link, and a changeback-declaration is sent on each of them; each changeback-declaration is assigned a different configuration of the changeback code. Stopped traffic is stored in one or more changeback buffers (in the latter case, a changeback buffer is provided for each alternative signalling link). When the changeback-acknowledgement relating to that alternative signalling link is received, traffic being diverted from a given alternative signalling link can be restarted on the signalling link made available, starting with the content of the changeback buffer; discrimination between the different changeback-acknowledgements is made by the changeback code configuration, which is the same as that sent in the changeback-declaration.
+
+This procedure allows either reopening the recovered signalling link to traffic in a selective manner (provided that different changeback buffers are used) as soon as each changeback-acknowledgement is received, or only when all the changeback-acknowledgements have been received.
+
+### 6.4 Time-controlled diversion procedure
+
+**6.4.1** The time-controlled diversion procedure is used at the end of the MTP restart procedure (see clause 9) when an adjacent signalling point becomes available, as well as for the reasons given in 6.2.5. An example of such a use appears in Figure 12.
+
+
+
+```
+graph LR; A((A)) -- "X" --> B[B]; B --> D((D)); A --> C[C]; C --> D; style A fill:none,stroke:none; style B fill:none,stroke:none; style C fill:none,stroke:none; style D fill:none,stroke:none;
+```
+
+Diagram illustrating the time-controlled diversion procedure. A signalling point A is connected to B and C. B is connected to D. A dashed arrow indicates traffic from A to B, which is blocked by an 'X'. A solid arrow indicates traffic from A to C. A dashed arrow indicates traffic from B to D. A solid arrow indicates traffic from C to D. The text 'T1158960-94/d19' is present near the bottom right of the diagram.
+
+**Figure 12/Q.704 – Example of time-controlled diversion procedure**
+
+In this example, on failure of signalling link AB, traffic towards the destination D was directed to signalling link AC. When AB becomes available, the point A considers itself as the neighbour of a point which restarts and applies the MTP restart procedure (see clause 9).
+
+**6.4.2** When changeback is initiated after the MTP restart procedure, the adjacent signalling point of the point whose MTP is restarting stops traffic to be directed from the alternative signalling link(s) for a time T3, after which it starts traffic on the signalling link(s) made available. The time delay minimizes the probability of out-of-sequence delivery to the destination point(s).
+
+### 6.5 Procedures in abnormal conditions
+
+**6.5.1** If a changeback-acknowledgement is received by a signalling point which has not previously sent a changeback-declaration, no action is taken.
+
+**6.5.2** If a changeback-declaration is received after the completion of the changeback procedure, a changeback-acknowledgement is sent in response, without taking any further action. This corresponds to the normal action described in 6.3.2 above.
+
+**6.5.3** If no changeback-acknowledgement is received in response to a changeback declaration within a time T4 (see 16.8), the changeback-declaration is repeated and a new timer T5 (see 16.8) is started. If no changeback-acknowledgement is received before the expiry of T5, the maintenance functions are alerted and traffic on the link made available is started. The changeback code contained in the changeback-acknowledgement message makes it possible to determine, in the case of parallel changebacks from more than one reserve path, which changeback-declaration is unacknowledged and has therefore to be repeated.
+
+## 7 Forced rerouting
+
+### 7.1 General
+
+**7.1.1** The objective of the forced rerouting procedure is to restore, as quickly as possible, the signalling capability between two signalling points towards a particular destination, in such a way as to minimize the consequences of a failure. However, since the unavailability of a signalling route is, in general, caused by the fact that the concerned destination has become inaccessible to a signalling transfer point, a probability of message loss exists (see 5.3.3). Therefore, the structure of the signalling network should be such as to reduce the probability of signalling route unavailability to limits compatible with the overall dependability requirements (see Recommendation Q.706).
+
+**7.1.2** Forced rerouting is the basic procedure to be used in the case where a signalling route towards a given destination becomes unavailable (due to, for example, remote failures in the signalling network) to divert signalling traffic towards that destination to an alternative signalling route outgoing from the concerned signalling point. Signalling links pertaining to the alternative signalling route can be carrying their own signalling traffic (relating to different signalling routes), and this is not interrupted by the forced rerouting procedure.
+
+### 7.2 Forced rerouting initiation and actions
+
+**7.2.1** Forced rerouting is initiated at a signalling point when a transfer-prohibited message, indicating a signalling route unavailability is received.
+
+The following actions are then performed:
+
+- a) transmission of signalling traffic towards the concerned destination on the link set(s) pertaining to the unavailable route is immediately stopped; such traffic is stored in a *forced rerouting buffer*;
+- b) the alternative route is determined according to the rules specified in clause 4;
+- c) as soon as action b) is completed, the concerned signalling traffic is restarted on a link set pertaining to the alternative route, starting with the content of the forced rerouting buffer;
+- d) if appropriate, a transfer-prohibited procedure is performed (see 13.2.2).
+
+**7.2.2** In the case when there is no signalling traffic to be diverted from the unavailable route, actions b) and d) in 7.2.1 apply.
+
+**7.2.3** If no alternative route exists for signalling traffic towards the concerned destination, that destination is declared inaccessible, and the actions specified in 5.3.3 apply.
+
+## 8 Controlled rerouting
+
+### 8.1 General
+
+**8.1.1** The objective of the controlled rerouting procedure is to restore the optimal signalling routing and to minimize mis-sequencing of messages. Therefore, controlled rerouting includes a time-controlled traffic diversion procedure, which is the same as that used in some cases of changeback (see 6.4).
+
+**8.1.2** Controlled rerouting is the basic procedure to be used in the following two cases:
+
+- a) when a signalling route towards a given destination becomes available (due to, for example, recovery of previous remote failures in the signalling network), to divert back signalling traffic towards that destination from the alternative to the normal signalling route outgoing from the concerned signalling point;
+
+- b) when a transfer-restricted1 message is received, after signalling traffic management has decided that alternative routing is appropriate (e.g. because it would be more efficient than routing via the link set over which the transfer-restricted message was received).
+
+Signalling links pertaining to the alternative signalling route can be carrying their own signalling traffic (relating to different routes) and this is not interrupted by the controlled rerouting procedure.
+
+### **8.2 Controlled rerouting initiation and actions**
+
+**8.2.1** Controlled rerouting is initiated at a signalling point when a transfer-allowed message, indicating that the signalling route has become available, is received; also when a transfer-restricted message1 is received.
+
+The following actions are then performed:
+
+- a) transmission of signalling traffic towards the concerned destination on the link set belonging to the alternative route or the route over which the transfer-restricted1 message was received is stopped; such traffic is stored in a "controlled rerouting buffer"; a timer T6 (see 16.8), is started;
+- b) if the signalling point serves as a signalling transfer point, a transfer-prohibited procedure is performed for the route made available (or the alternative route in the case of reception of a transfer-restricted1 message, if the alternative route was not previously used), and a transfer-allowed procedure for the alternative one (or on the restricted route in the case of the reception of a transfer-restricted1 message) (see 13.2.2 and 13.3.2, respectively);
+- c) at the expiry of T6, the concerned signalling traffic is restarted on an outgoing link set pertaining to the signalling route made available, or the alternative route in the case of reception of the transfer-restricted1 message, starting with the content of the controlled rerouting buffer; the aim of the time delay is to minimize the probability of out-of-sequence delivery to the destination point(s).
+
+**8.2.2** In the case when there is no signalling traffic to be diverted from the route made available, only action b) in 8.2.1 applies.
+
+**8.2.3** If the destination was inaccessible or restricted1, when the route is made available, then the destination is declared accessible and actions specified in 6.2.3 and 6.2.4 apply (if appropriate).
+
+## **9 MTP restart**
+
+### **9.1 General**
+
+When a signalling point is isolated from the network for some time, it cannot be sure that its routing data are still valid (note that circumstances might cause the management entity to isolate the node, i.e. make all links unavailable, in order to facilitate recovery from a partial isolation). Thus, problems could be present when the sending of User traffic is resumed, due to wrong routing data as well as due to many parallel activities (e.g. link activation, changebacks etc.) which have to be performed within the node whose MTP is restarting.
+
+The objective of the MTP restart procedure is to protect the node whose MTP is restarting, and the network. This is done by giving the restarting MTP time to activate sufficient links, and to exchange enough routing data with the network, before User traffic is restarted. Note that in this context "sufficient" and "enough" mean that potential remaining problems should not cause the node to fail again.
+
+A central part of the restart procedure is the exchange of network status information between the restarting MTP and the adjacent nodes. In order for the procedure to make sense, the network status should not change significantly during this information exchange. As a consequence there is an overall restart time defined for the node whose MTP is restarting as well as for the adjacent nodes. During this time, all activities within the node whose MTP is restarting as well as the adjacent nodes should be completed. This requires that the time available is used in an efficient way.
+
+As a basis of the restart procedure it is assumed that most of the signalling points within the network are accessible. Thus, at the beginning of the restart procedure, all concerned routes are considered to be allowed, and the update of the network status is performed by the exchange of transfer-prohibited (TFP) and/or transfer-restricted (TFR)1 messages.
+
+The MTP restart procedure uses the Traffic Restart Allowed (TRA) message which contains:
+
+- the label, indicating the originating signalling point and the adjacent destination signalling point;
+- the traffic restart allowed signal.
+
+The format and coding of this message appear in clause 15.
+
+When an adjacent node has finished sending all relevant TFP and/or TFR1 messages to the node with the restarting MTP, it finally sends a TRA message which indicates that all relevant routing information has been transferred. Thus, at the node with the restarting MTP, the number of received TRA messages is an indication of the completeness of the routing data.
+
+When the restarting MTP has completed all actions or when the overall restart time is over, it sends TRA messages directly to all of its adjacent nodes accessible via a direct link set. These messages indicate that the restart procedure is terminated and User traffic should be started.
+
+### **9.2 Actions in a signalling point whose MTP is restarting**
+
+**9.2.1** A signalling point starts the MTP restart procedure when its first link is in service at level 2. The restarting MTP:
+
+- if it has the transfer function starts a timer T18;
+- starts an overall restart timer T20; and
+- continues activating or unblocking all of its signalling links by means of the basic signalling link management procedures (see 12.2).
+
+NOTE – In order to use the overall restart time in an efficient way, it is preferable to make all link sets available at nearly the same time, by activating first one link per link set, and by applying emergency alignment for at least the first link in each link set. Because of this measure, the routing data update can be started for all routes at the very beginning of the restart procedure.
+
+**9.2.2** If the signalling point's restarting MTP has the transfer function, the MTP restart procedure consists of two phases. Within the first phase, supervised by timer T18, links are activated and the routing tables within the restarting MTP are updated according to the transfer-prohibited, transfer-allowed and transfer-restricted1 messages (see clause 15) received from the adjacent nodes. In addition, the restarting MTP takes into account any traffic restart allowed messages received from adjacent nodes. Timer T18 is implementation and network dependent, and is stopped when:
+
+- 1) sufficient links and link sets are available to carry the expected signalling traffic; and
+- 2) enough TRA messages (and therefore routing data) have been received to give a high level of confidence in the MTP routing tables.
+
+NOTE – In normal circumstances the restarting MTP should wait for TRA messages from all adjacent nodes. There are, however, other situations where this might not be useful, e.g. for a long-term equipment failure.
+
+When T18 is stopped or expires, the second phase begins, which includes as a major part a broadcast of non-preventive transfer prohibited messages [i.e. those TFPs according to 13.2.2 v)] and transfer-restricted1 messages, taking into account signalling link sets which are not available and any TFP, TFA and TFR1 messages received during phase 1. Note that timer T18 is determined such that during phase 2 the broadcast of TFP and TFR1 messages may be completed in normal situations.
+
+TRA messages received during phase 2 should be ignored. If during phase 2 a destination has been declared to be inaccessible by sending of a TFP message, and afterwards, but still within phase 2, this destination becomes accessible to the restarting MTP by reception of a TFA or TFR1 message or the availability of a corresponding link, this new accessibility is a late event and should be treated outside the restart procedure. The handling of the new accessibility of the said destination before the sending of a TFP referring to that destination is an implementation dependent matter.
+
+When all TFP and TFR1 messages have been sent, the overall restart timer T20 is stopped and phase 2 is finished. Note that preventive TFP messages [i.e. those according to 13.2.2 i)], except possibly those for highest priority routes, must have been sent before normal User traffic is carried. This might be done during or after phase 2.
+
+**9.2.3** If the restarting MTP has no transfer function, phase 1 (see 9.2.2) but not phase 2 is present. In this case, the whole restart time is available for phase 1. The overall restart timer T20 is stopped when:
+
+- 1) sufficient links and link sets are available to carry the expected signalling traffic; and
+- 2) enough TRA messages (and therefore routing data) have been received to give a high level of confidence in the MTP routing tables.
+
+**9.2.4** When T20 is stopped or expires, the restarting MTP of the signalling point or signalling transfer point sends traffic restart allowed messages to all adjacent signalling points via corresponding available direct link sets, and an indication of the end of MTP restart is sent to all local MTP Users showing each signalling point's accessibility or inaccessibility. The means of doing the latter is implementation dependent.
+
+In addition, timer T19 is started (see 9.5.2) for all signalling points to which a TRA message has just been sent. Normal operation is then resumed.
+
+When T20 expires the transmission of TFP and TFR1 messages is stopped. However, preventive TFP messages [i.e. those according to 13.2.2 i)] except possibly those for highest priority routes, must have been sent before MTP User traffic is restarted.
+
+### **9.3 Actions in a signalling point X, adjacent to a signalling point Y whose MTP restarts**
+
+**9.3.1** A signalling point X considers that the MTP of an inaccessible adjacent signalling point Y is restarting when:
+
+- the first link in a direct link set is in the "in service" state at level 2; or
+- another route becomes available due either to reception of a corresponding TFA, TFR1 or TRA message, or by the corresponding link set becoming available (see 3.6.2.2).
+
+**9.3.2** When the first link in a direct linkset towards signalling point Y, whose MTP is restarting, is in the "in service" state at level 2, signalling point X starts a timer T21 and takes account of any TFP, TFA and TFR1 messages received from signalling point Y. In addition X takes the following action:
+
+- if X has the transfer function, when the direct linkset is available at level 3, X sends any necessary TFP and TFR1 messages to Y; then
+- X sends a traffic restart allowed message to signalling point Y.
+
+If a signalling point, previously declared to be inaccessible, becomes available again before T21 is stopped or expires, a corresponding TFA or TFR1 message is sent to the signalling point Y whose MTP is restarting.
+
+If a signalling point becomes prohibited or restricted to signalling point X after a TRA message has been sent by X to Y, X sends a corresponding TFP or TFR1 message to Y.
+
+When a traffic restart allowed message has been received by X from signalling point Y, and a TRA message has been sent by X to Y, X stops timer T21.
+
+Note that preventive TFP messages according to 13.2.2 i) must be sent before MTP User traffic is restarted.
+
+NOTE – This includes the case where the MTP of Y is restarting as well as the case that both X and Y start the adjacent signalling point MTP restart procedure at the new availability of the interconnecting direct link set. In the latter case, one side will receive a TRA message from the other while still sending TFP and/or TFR1 messages, so that it has not yet sent its TRA message. The transmission of routing information should be completed before this TRA message is sent to the adjacent node and timer T21 stopped.
+
+When T21 is stopped or expires, signalling point X sends an MTP-RESUME primitive concerning Y, and all signalling points made available via Y, to all local MTP Users. If X has the transfer function, it broadcasts to adjacent available signalling points transfer-allowed and/or transfer-restricted1 messages concerning Y and all signalling points made accessible via Y.
+
+Note that preventive TFPs according to 13.2.2 i) must be sent before MTP User traffic is restarted.
+
+In the abnormal case where transfer prohibited and transfer restricted1 messages are still being sent to Y when T21 expires (and hence no TRA message has yet been sent to Y), such routing data transmission is stopped and no TRA message is sent to Y. Note that preventive TFPs according to 13.2.2 i) must still be sent during the changeback procedure.
+
+**9.3.3** When signalling point Y becomes accessible by means other than via a direct link set between X and Y, X sends an MTP-RESUME primitive concerning Y to all local MTP Users. In addition, if signalling point X has the transfer function, X sends to Y any required transfer-prohibited and transfer-restricted1 messages on the available route. X then broadcasts TFA and/or TFR1 messages (see clause 13) concerning Y. Note that X should not in this case alter any routing data other than that for Y.
+
+### **9.4 Short term isolations**
+
+**9.4.1** In the case where a signalling point is isolated due to a short term processor outage [lasting less than T1 (see 16.8)] occurring on some or all of its links at nearly the same time, the restart procedure should not be started.
+
+If an isolation lasts longer than T1, the restart procedure must be performed.
+
+**9.4.2** When a destination Y becomes inaccessible, and routing control finds an inhibited link within the route set to Y, a signalling routing control initiated uninhibiting action is performed (see 10.3). If at least one inhibited link is in the level 2 "in service" state, and uninhibiting is successful, the isolation will be of short term and no restart procedure should be performed on either side of the link.
+
+### **9.5 TRA messages and timer T19**
+
+**9.5.1** If a signalling point X receives an unexpected TRA message from an adjacent node Y and no associated T19 timer is running, X sends to Y any necessary TFP and TFR1 messages if X has the transfer function, and a TRA message to Y. In addition, X starts a timer T19 associated with Y.
+
+**9.5.2** If a signalling point receives a TRA message from an adjacent node and an associated timer T19 is running, this TRA is discarded and no further action is necessary.
+
+### **9.6 General rules**
+
+**9.6.1** When the MTP of a signalling point restarts, it considers at the beginning of the MTP restart procedure all signalling routes to be allowed.
+
+**9.6.2** After the MTP of an adjacent node X has restarted, and if T21 has been started (see 9.3.2), all routes using X are considered to be available unless corresponding TFP or TFR1 messages have been received whilst T21 was running.
+
+**9.6.3** A signalling route set test message received in a restarting MTP is ignored during the MTP restart procedure.
+
+Signalling route set test messages received in a signalling point adjacent to signalling point Y whose MTP is restarting before T21 expires are handled, but the replies assume that all signalling routes using Y are prohibited.
+
+**9.6.4** Late events, i.e. link restorations or reception of TFA or TFR1 messages, occurring in phase 2 at a node whose MTP is restarting after the node has sent out TFPs or TFRs1 referring to the concerned signalling points, are treated outside the restart procedure as normal events.
+
+Handling of late events in phase 2 before sending out TFPs or TFRs1 referring to the concerned signalling points is an implementation dependent matter. In addition, it is an implementation dependent matter whether the reception of TFPs or link set failures during phase 2 are handled within or after the termination of the restart procedure.
+
+**9.6.5** When an adjacent signalling point Y becomes accessible on receipt of a TFA, TFR1 or TRA message (see 3.6.2), the concerned signalling point performs controlled rerouting towards Y.
+
+**9.6.6** All messages to another destination received at a signalling point whose MTP is restarting are discarded.
+
+All messages received during the restart procedure concerning a local MTP User (service indicator $\neq$ 0000 and $\neq$ 0001) are discarded.
+
+All messages received with service indicator = 0000 in a restarting MTP for the signalling point itself are treated as described in the MTP restart procedure. Those messages not described elsewhere in the procedure are discarded and no further action is taken on them (message groups CHM, ECM, FCM, RSM, UFC, MIM and DLM).
+
+**9.6.7** In adjacent signalling points during the restart procedure, messages not part of the restart procedure but which are destined to or through the signalling point whose MTP is restarting, are discarded.
+
+Messages received with service indicator = 0001 are handled normally during the restart procedure.
+
+**9.6.8** If a gateway node's MTPs are restarting in multiple networks, it may be of advantage to co-ordinate their restarting procedures (implementation dependent).
+
+### **9.7 Sequence diagrams**
+
+Arrow diagrams illustrate the procedures. In case of conflict, the text takes precedence over the diagrams.
+
+#### 9.7.1 SP with restarting MTP according to subclause 9.2
+
+
+
+```
+
+sequenceDiagram
+ participant User
+ participant SP as Restarting SP
+ participant MTP
+
+ Note over MTP: All links unavailable (e.g. LPO)
+ Note over MTP: First link in service at level 2
+ Note right of MTP: time > ~T1
+
+ rect rgb(240, 240, 240)
+ Note over SP: SP is an STP?
+ alt No
+ MTP->>SP: start T20
+ MTP->>MTP: TFP [,TFR], TRA messages
+ MTP-->>SP: TFA negating previous TFP [or TFR]
+ MTP->>MTP: Sufficient links available
+ else Yes
+ SP->>SP: start T18
+ MTP->>MTP: TFP [,TFR], TRA messages
+ MTP-->>SP: TFA negating previous TFP [or TFR]
+ MTP->>MTP: Enough TRA messages received or T18 expiry
+ end
+ end
+
+ rect rgb(240, 240, 240)
+ Note over SP: SP is an STP?
+ alt Yes
+ Note over SP: T20 still running
+ MTP->>MTP: TFP [,TFR] broadcast
+ MTP-->>SP: Late availability of link, TFP [,TFR] or TFA received
+ MTP->>MTP: Last TFP [,TFR], or T20 expiry
+ else No
+ Note over SP: T20 still running
+ end
+ end
+
+ SP->>SP: Enough TRAs received, or T20 expiry
+ MTP-->>User: MTP-RESUME indications
+ MTP->>MTP: TRA broadcast over direct link sets
+ MTP-->>MTP: TFAs, TFPs, [,TFRs] broadcast due to late events
+ SP->>SP: start T19s
+
+```
+
+T1178290-96
+
+Sequence diagram showing the interaction between a User, a Restarting SP, and an MTP during MTP restart. It details message flows, timer starts (T18, T20, T19s), and decision points based on whether the SP is an STP.
+
+Arrow diagram 1
+
+#### 9.7.2 Actions in SP X adjacent to SP Y whose MTP restarts according to subclause 9.3
+
+![Sequence diagram showing actions in SP X adjacent to SP Y whose MTP restarts. The diagram involves User, MTP, and SP X components. It starts with 'All links to Y unavailable (e.g. LPO)' and ends with 'broadcast TFA [,TFR] referring to Y and all SPs accessible via Y'.](284768c5ee1a05aa1b9ce396f606a040_img.jpg)
+
+SP X adjacent to restarting SP Y
+
+```
+
+sequenceDiagram
+ participant User
+ participant MTP
+ participant SP_X as SP X
+
+ Note over MTP: All links to Y unavailable (e.g. LPO)
+ Note right of MTP: time > ~T1
+ Note over MTP: First link in direct link set to Y
+in service at level 2
+ Note over SP_X: start T21
+ Note over SP_X: SP X has STP fn. ?
+ Note left of SP_X: No
+ Note right of SP_X: Yes
+ Note right of SP_X: When 1st. link in direct
+link set is available at level 3:
+TFP [,TFR] messages to Y
+ SP_X->>MTP: TRA to Y
+ Note over SP_X: T21 still running
+ Note right of SP_X: If X is STP: TFA, TFP [,TFR] msgs to Y because of recent events
+ MTP->>SP_X: TFP [,TFR] messages from Y
+ MTP->>User: MTP-RESUME indications w.r.t. Y and all SPs now accessible due to Y
+ MTP->>SP_X: TRA from Y, or T21 expiry
+ Note over SP_X: SP X has STP fn. ?
+ Note left of SP_X: No
+ Note right of SP_X: Yes
+ Note right of SP_X: broadcast TFA [,TFR] referring
+to Y and all SPs accessible via Y
+ Note right of SP_X: T1178300-96
+
+```
+
+Sequence diagram showing actions in SP X adjacent to SP Y whose MTP restarts. The diagram involves User, MTP, and SP X components. It starts with 'All links to Y unavailable (e.g. LPO)' and ends with 'broadcast TFA [,TFR] referring to Y and all SPs accessible via Y'.
+
+Arrow diagram 2
+
+## 10 Management inhibiting
+
+### 10.1 General
+
+Signalling link management inhibiting is requested by management when it becomes necessary, e.g. for maintenance or testing purposes (for example, if the link experiences too many changeovers and changebacks in a short time, or there is a significant link error rate), to make or keep a signalling link unavailable to User Part-generated signalling traffic. Management inhibiting is a signalling traffic management action, and does not cause any link status changes at level 2. A signalling link is marked "inhibited" under the management inhibiting procedure. In particular, a signalling link that
+
+was active and in service prior to being inhibited will remain so, and will thus be able to transmit maintenance and test messages, for which the signalling link test message could be used (see clause 2/Q.707).
+
+Inhibiting of a signalling link may be requested by management functions at either end of the link. The request is granted, provided that the inhibiting action does not cause any previously accessible destinations to become inaccessible at either end of the signalling link. The request may also be refused under certain circumstances such as congestion.
+
+A signalling link normally remains inhibited until uninhibiting is invoked in the signalling point at which inhibiting was initiated. Uninhibiting is initiated either at the request of a management function or by routing functions at either end of the signalling link when it is found that a destination has become inaccessible for signalling traffic and the link sets associated with routes to that destination contain inhibited links. Unless unavailable for other reasons, uninhibiting causes the signalling link to enter the available state and changeback to be initiated.
+
+Periodic tests are made on the inhibit status of inhibited links. Such periodic tests should not add significantly to the traffic load on the signalling network, and remove the need for a signalling point to perform inhibit tests at signalling point restart.
+
+If a test on the inhibit status of a link reveals discrepancies between the signalling points at each end of the link, the link is either uninhibited or force uninhibited as appropriate, to align the inhibit status at each end of the link.
+
+### 10.2 Inhibiting initiation and actions
+
+When at signalling point X a request is received from a management function to inhibit a signalling link to signalling point Y, the following actions take place:
+
+- a) A check is performed at signalling point X to determine whether, in the case of an available link, inhibiting will result in a destination becoming inaccessible, or in the case of an unavailable link, signalling point Y is inaccessible. If either is the case, management is informed that the inhibiting request is denied.
+- b) If inhibiting is permitted, signalling point X sends an inhibit message to signalling point Y indicating that it wishes to inhibit the signalling link identified in the message.
+- c) Signalling point Y, on receiving the inhibit message from X, checks whether, in the case of an available link, inhibiting will result in a destination becoming inaccessible and, if so, an inhibit denied message is returned to signalling point X. The latter then informs the management function which requested inhibiting that the request cannot be granted.
+- d) If the signalling point Y finds that inhibiting of the concerned link is permissible, it sends an inhibit acknowledgement to signalling point X and marks the link remotely inhibited.
+
+If the link concerned is currently carrying traffic, signalling point Y sends the inhibit acknowledgement via that link and diverts subsequent traffic for it, using the time controlled changeover procedure. Y then starts inhibit test timer T23.
+
+- e) On receiving an inhibit acknowledgement message, signalling point X marks the link locally inhibited and informs management that the link is inhibited.
+
+If the link concerned is currently carrying traffic, signalling point X diverts subsequent traffic for that link, using the time-controlled changeover procedure. X then starts inhibit test timer T22.
+
+- f) When changeover has been completed, the link while inhibited, will be unavailable for the transfer of user-generated traffic but still permits the exchange of test messages.
+
+- g) If, for any reason, the inhibit acknowledgement message is not received, a timer T14 expires and the procedure is restarted including inspection of the status of the destination of the inhibit message. If the destination is not available, management is informed.
+
+At most two consecutive automatic attempts may be made to inhibit a particular signalling link.
+
+A signalling point may not transmit an inhibit message for a particular signalling link if it has already transmitted an uninhibit message for that link, and neither an acknowledgement for that uninhibit message has been received nor has the uninhibit procedure finally timed out.
+
+### **10.3 Uninhibiting initiation and actions**
+
+Signalling link uninhibiting is initiated at the signalling point which originally caused the link to be inhibited, upon receipt of an uninhibit or forced uninhibit request.
+
+In a given signalling point, an uninhibit request may be initiated for a locally inhibited link by the management or signalling routing control function, while a forced uninhibit request may be initiated for a remotely inhibited link by the signalling routing control function only.
+
+Signalling routing control will initiate signalling link uninhibit if an inhibited link is found to be a member of a link set in a route to a destination which has become inaccessible.
+
+If such signalling routing control uninhibiting were unsuccessful because of a failed or blocked inhibited link, and if that link later recovers or becomes unblocked with the destination still unavailable, uninhibiting is re-attempted.
+
+A signalling point may not transmit an uninhibit message for a particular signalling link if it has already transmitted an inhibit message for that link, and neither an acknowledgement for that inhibit message has been received nor has the inhibit procedure finally timed out.
+
+#### **10.3.1 Management-initiated uninhibiting**
+
+Upon receipt of an uninhibiting request from the management function of signalling point X regarding an inhibited link to signalling point Y, the following actions take place:
+
+- a) A check is performed at signalling point X to determine whether an uninhibit message can be sent to signalling point Y, either over an available route, or if all routes to signalling point Y are unavailable, over the concerned inhibited link. If all routes to signalling point Y are unavailable and the concerned inhibited link is marked failed or processor outage, management is informed that uninhibiting is not possible.
+- b) If uninhibiting is possible, signalling point X sends an uninhibit signalling link message to signalling point Y indicating that the link identified in the message should be uninhibited.
+- c) Upon receipt of the uninhibit link message, signalling point Y returns an uninhibit acknowledgement message to signalling point X and cancels the remote inhibit indication. If no local inhibited, failed or blocked condition exists on the link, it is put in the available state and changeback is initiated.
+- d) On receipt of the uninhibit acknowledgement message, signalling point X cancels the local inhibit indication and informs management that the link has been uninhibited. If no remote inhibited, failed or blocked condition exists on the link, it is put in the available state and changeback is initiated.
+- e) If, for any reason, the uninhibit acknowledgement message is not received, a timer T12 expires. If this is the first expiry of T12 for this uninhibition attempt on this link, the procedure is restarted including inspection of the status of the destination of the uninhibit message. If the destination is not available, or T12 has expired for the second time during the
+
+uninhibition attempt on this link, management is informed, and the uninhibition is abandoned.
+
+#### **10.3.2 Signalling routing control initiated uninhibiting**
+
+Upon receipt of an uninhibit request from signalling routing control at signalling point X regarding an inhibited link to signalling point Y, the following actions take place:
+
+- a) A check is performed at signalling point X to determine whether the concerned inhibited link is marked failed or blocked. If it is, then signalling point X is unable to transmit an uninhibit message to signalling point Y, uninhibiting is therefore not possible, and the uninhibiting attempt is abandoned.
+- b) If uninhibiting is possible, a further check is performed by signalling point X to determine whether inhibiting initiated by X (local inhibiting) or inhibiting initiated by Y (remote inhibiting) is in effect.
+- c) If local inhibiting is in effect, then the actions described in 10.3.1 b), c), d) and e) take place. If uninhibition is abandoned, step f) below is taken.
+- d) If remote inhibiting is in effect, then signalling point X requests forced uninhibiting of the signalling link by sending a force uninhibit signalling link message to signalling point Y, which will then initiate uninhibiting in accordance with the description given in 10.3.1 b), c), d) and e).
+
+The force uninhibit signalling link message is transmitted down the link to be uninhibited.
+
+- e) If, for any reason, an uninhibit signalling link message is not received in response to the force uninhibit message, a timer T13 expires. If this is the first expiry of T13 for this uninhibition attempt on this link, the procedure is restarted including inspection of the status of the inhibited link. If the link is marked failed or blocked, or timer T13 has expired for the second time during uninhibition of this link, management is informed and the uninhibition is abandoned.
+- f) If an attempt to uninhibit a signalling link is abandoned, signalling routing control attempts to uninhibit the next inhibited link to signalling point Y, starting from a) above. The search continues until either a link is successfully uninhibited or all possible links to Y in the routing table have been exhausted, or the destination has become available for other reasons.
+
+### **10.4 Receipt of unexpected management inhibition messages**
+
+- a) An inhibit signalling link message concerning an inhibited signalling link is answered with an inhibit acknowledgement message without taking any further action.
+- b) An uninhibit signalling link message concerning an uninhibited signalling link is answered with an uninhibit acknowledgement message without taking any further action.
+- c) A force uninhibit signalling link message concerning an uninhibited link is answered with an uninhibit signalling link message without taking any further action.
+- d) If an inhibit acknowledgement message is received and no inhibit signalling link message is outstanding for the concerned link, no action is taken.
+- e) If an uninhibit acknowledgement message is received and no uninhibit signalling link message is outstanding for the concerned link, no action is taken.
+
+### **10.5 Management inhibited link status and processor recovery**
+
+- a) After a local processor recovery that involves loss of inhibit status information, the signalling point will mark all links as uninhibited, and message traffic will be restarted.
+
+- b) If messages for Level 4 are received on an inhibited signalling link, the messages will be discriminated and distributed.
+
+### **10.6 Inhibit test procedure**
+
+When a signalling link becomes management inhibited, periodic tests are started to guard the inhibition status at each end of the link.
+
+**10.6.1** A local inhibit test is performed when timer T22 expires at signalling point X and the concerned link is marked locally inhibited. In this case, a local inhibit test message is sent to the signalling point Y at the other end of the link, and timer T22 is restarted.
+
+Reception of a local inhibit test message causes:
+
+- i) no action, if the concerned link is marked remotely inhibited at the receiving signalling point Y; or
+- ii) the force uninhibit procedure to be invoked at the receiving signalling point Y, if the concerned link is not marked remotely inhibited at Y. This procedure causes the locally inhibited status of the link at X to be cancelled.
+
+If a timer T22 expires and the concerned link is not locally inhibited, no further action is taken.
+
+**10.6.2** A remote inhibit test is performed when timer T23 expires at signalling point Y and the concerned link is marked remotely inhibited. In this case a remote inhibit test message is sent to signalling point X at the other end of the link, and timer T23 is restarted.
+
+Reception of a remote inhibit test message causes:
+
+- i) no action, if the concerned link is marked locally inhibited at the receiving signalling point X; or
+- ii) the uninhibit procedure to be invoked at the receiving signalling point X, if the concerned link is not marked locally inhibited at X. This procedure causes the remotely inhibited status of the link at Y to be cancelled.
+
+If a timer T23 expires and the concerned link is not remotely inhibited, no further action is taken.
+
+## **11 Signalling traffic flow control**
+
+### **11.1 General**
+
+The purpose of the signalling traffic flow control function is to limit signalling traffic at its source in the case when the signalling network is not capable of transferring all signalling traffic offered by the user because of network failures or congestion situations.
+
+Flow control action may be taken as a consequence of a number of events; the following cases have been identified:
+
+- Failure in the signalling network (signalling links or signalling points) has resulted in route set unavailability. In this situation, flow control may provide a short-term remedy until more appropriate actions can be taken.
+- Congestion of a signalling link or signalling point has resulted in a situation where reconfiguration is not appropriate.
+- Failure of a part has made it impossible for the user to handle messages delivered by the Message Transfer Part.
+
+When the normal transfer capability is restored, the flow control functions initiate resumption of the normal traffic flow.
+
+### **11.2 Flow control indications**
+
+The need for the following indications has been identified.
+
+#### **11.2.1 Signalling route set unavailability**
+
+In the case when no signalling route is available for traffic towards a particular destination (see 5.3.3 and 7.2.3), an indication is given from the Message Transfer Part to the local user parts informing them that signalling messages destined to the particular signalling point cannot be transferred via the signalling network. Each user then takes appropriate actions in order to stop generation of signalling information destined for the inaccessible signalling point.
+
+#### **11.2.2 Signalling route set availability**
+
+In the case when a signalling route becomes available for traffic to a previously unavailable destination (see 6.2.3 and 8.2.3), an indication is given from the Message Transfer Part to the local user parts informing them that signalling messages destined to the particular signalling point can be transferred via the signalling network. Each user then takes appropriate actions in order to start generation of signalling information destined for the now accessible signalling point.
+
+#### **11.2.3 Signalling route set congestion (International signalling network)**
+
+**11.2.3.1** When the congestion status of a signalling route set changes to congested, the following actions will be taken:
+
+- i) When a message signal unit from a local User Part is received for a congested route set the following actions are performed:
+ - a) The MSU is passed to level 2 for transmission.
+ - b) An MTP-STATUS primitive will be returned to each level 4 User Part, for the initial message, or alternatively for the first octet, and for at least every n message (n = 8), or alternatively N octets4 (N = 279 to 300 provisional value), received for the congested route set or for any link of the congested route set or for any link set of the congested route set or for any congested link of the congested route set. The MTP-STATUS primitive contains as a parameter the DPC of the affected destination, and a cause parameter whose value is "signalling network congested" plus possibly a congestion level.
+- ii) When a message signal unit is received at an STP for a congested route set, the following actions take place:
+ - a) The MSU is passed to level 2 for transmission.
+ - b) A transfer controlled message is sent to the originating point of the initial message, or alternatively the first octet, and for every n messages (n = 8), or alternatively every N octet4 (N = 279 to 300 provisional value) received from any originating point for the congested route set or for any link of the congested route set or for any link set of the congested route set or for any congested link of the congested route set.
+
+**11.2.3.2** After the reception of a transfer controlled message, the receiving signalling point informs each level 4 User Part of the affected destination by means of an MTP-STATUS primitive specified in 11.2.3.1 i).
+
+---
+
+4 Where the measured length is the full level 2 MSU length.
+
+**11.2.3.3** When the status of a signalling route set changes to uncongested, normal operation is resumed. Resumption of message transmission towards the concerned destination is the responsibility of the level 4 User Parts.
+
+#### **11.2.4 Signalling route set congestion (National option with congestion priorities)**
+
+In the case when the congestion status of a signalling route set changes as a result of either the receipt of a transfer controlled message relating to a particular destination (see 13.7) or an indication of local signalling link congestion, or due to the signalling route-set-congestion-test procedure (see 13.9) an indication is given from the Message Transfer Part to the local level 4 informing it about the current congestion status of the signalling route set. Each user then takes appropriate actions in order to stop generation of signalling messages destined for the affected signalling point with congestion priorities lower than the specified congestion status. Messages received from the local level 4 with congestion priorities lower than the current signalling route set congestion status are discarded by the Message Transfer Part.
+
+#### **11.2.5 Signalling route set congestion (National options without congestion priorities)**
+
+For national signalling networks using multiple signalling link congestion states without congestion priority, $S + 1$ ( $1 \leq S \leq 3$ ) levels of route set congestion status are provided.
+
+The procedure is the same as that specified in 11.2.3, except that the MTP-STATUS primitive contains the congestion status as a parameter in addition to the DPC of the affected destination.
+
+#### **11.2.6 Signalling point/signalling transfer point congestion**
+
+The detection of congestion onset and abatement in a signalling point or signalling transfer point should, if required, be implementation dependent. Any resulting action taken, and messages and primitives sent, should align with those procedures, messages and primitives specified for signalling route set congestion.
+
+#### **11.2.7 User Part availability control**
+
+**11.2.7.1** If the Message Transfer Part is unable to distribute a received message to a local user because that user is unavailable (User Part unavailability is an implementation dependent notion – it can include unavailability for management reasons, the user might even be unequipped), the Message Transfer Part sends a User Part Unavailable (UPU) message to the Message Transfer Part at the originating signalling point. The detailed information whether the user is unequipped or unavailable for management reasons is contained in the UPU message.
+
+**11.2.7.2** When the originating signalling point's Message Transfer Part receives a User Part Unavailable message, it:
+
+- a) informs the management process5;
+- b) sends an indication (MTP-STATUS with parameters identifying the signalling point containing the unavailable User Part, as well as the cause "unequipped remote user" if no such user exists, or "inaccessible remote user" if the user exists but the MTP cannot currently distribute messages to it) to the local user designated in the message, if it is available.
+
+Note that the MTP does not maintain status information regarding the availability of the remote User Part.
+
+---
+
+5 Whether or not the management process is informed is implementation dependent.
+
+**11.2.7.3** The user should then take appropriate action in order to stop generation of normal signalling information for the unavailable User Part.
+
+**11.2.7.4** If the unavailability cause is "inaccessible remote user" or "unknown", it is the responsibility of the User Part to determine when the remote User Part is again available (User Part availability is an implementation dependent notion). This might be done, for example, by the user testing periodically, or by using the reception of a message from the remote user as an implicit indication of availability, or both. If the unavailability cause is "unequipped remote user", these actions should not be performed.
+
+**11.2.7.5** The User Part Unavailable message contains:
+
+- the label, indicating the destination and originating points;
+- the User Part Unavailable signal;
+- the identity of the unavailable User Part;
+- the cause of the unavailability.
+
+The format and coding of this message appear in clause 15.
+
+**11.2.7.6** When the Message Transfer Part is again able to distribute received messages to a previously unavailable local User Part (local User Part availability is an implementation dependent notion), the Message Transfer Part delivers the received messages to that user.
+
+**11.2.7.7** If a User Part Unavailable message is received by the Message Transfer Part referring to a remote User Part whose local peer is unequipped, the Message Transfer Part informs the management process5 and discards the UPU message.
+
+#### **11.2.8 User Part congestion**
+
+There are no specific User Part congestion control procedures defined in the MTP.
+
+## **12 Signalling link management**
+
+### **12.1 General**
+
+**12.1.1** The signalling link management function is used to control the locally connected signalling links. The function provides means for establishing and maintaining a certain predetermined capability of a link set. Thus, in the event of signalling link failures the signalling link management function controls actions aimed at restoring the capability of the link set.
+
+Three sets of signalling link management procedures are specified in the following subclauses. Each set corresponds to a certain level of automation as regards allocation and reconfiguration of signalling equipment. The basic set of signalling link management procedures (see 12.2) provides no automatic means for allocation and reconfiguration of signalling equipment. The basic set includes the minimum number of functions which must be provided for international application of the signalling system.
+
+Two alternative sets of signalling link management procedures are provided as options and include functions allowing for a more efficient use of signalling equipment in the case when signalling terminal devices have switched access to signalling data links.
+
+**12.1.2** A signalling link set consists of one or more signalling links having a certain order of priority as regards the signalling traffic conveyed by the link set (see clause 4). Each signalling link in operation is assigned a signalling data link and a signalling terminal at each end of the signalling data link.
+
+The signalling link identity is independent of the identities of the constituent signalling data link and signalling terminals. Thus, the identity referred to by the Signalling Link Code (SLC) included in the label of messages originated at Message Transfer Part level 3 is the signalling link identity and not the signalling data link identity or the signalling terminal identity.
+
+Depending on the level of automation in an application of the signalling system, allocation of signalling data link and signalling terminals to a signalling link may be made manually or automatically.
+
+In the first case, applicable for the basic signalling link management procedures, a signalling link includes predetermined signalling terminals and a predetermined signalling data link. To replace a signalling terminal or signalling data link, a manual intervention is required. The signalling data link to be included in a particular signalling link is determined by bilateral agreement (see also Recommendation Q.702).
+
+In the second case for a given signalling point, a signalling link includes any of the signalling terminals and any of the signalling data links applicable to a *link group*. As a result of, for example, signalling link failure, the signalling terminal and signalling data link included in a signalling link, may be replaced automatically. The criteria and procedures for automatic allocation of signalling terminals and signalling data links are specified in 12.5 and 12.6, respectively. The implementation of these functions requires that for a given link group any signalling terminal can be connected to any signalling data link.
+
+NOTE – A link group is a group of identical signalling links directly connecting two signalling points. A link set may include one or more link groups.
+
+**12.1.3** When a link set is to be brought into service, actions are taken to establish a predetermined number of signalling links. This is done by connecting signalling terminals to signalling data links and for each signalling link performing an initial alignment procedure (see 7.3/Q.703). The process of making a signalling link ready to carry signalling traffic is defined as *signalling link activation*.
+
+Activation of a signalling link may also be applicable, for example when a link set is to be extended or when a persisting failure makes another signalling link in the link set unavailable for signalling traffic.
+
+In the case of signalling link failure, actions should be taken to restore the faulty signalling link, i.e. to make it available for signalling again. The restoration process may include replacement of a faulty signalling data link or signalling terminal.
+
+A link set or single signalling link is taken out of service by means of a procedure defined as *signalling link deactivation*.
+
+The procedures for activation, restoration and deactivation are initiated and performed in different ways depending on the level of automation applicable for a particular implementation of the signalling system. In the following, procedures are specified for the cases when:
+
+- a) no automatic functions are provided for allocation of signalling terminals and signalling data links (see 12.2).
+- b) an automatic function is provided for allocation of signalling terminals (see 12.3).
+- c) automatic functions are provided for allocation of signalling terminals and signalling data links (see 12.4).
+
+### **12.2 Basic signalling link management procedures**
+
+#### **12.2.1 Signalling link activation**
+
+**12.2.1.1** In the absence of failures, a link set contains a certain predetermined number of active (i.e. aligned) signalling links. In addition, the link set may contain a number of inactive signalling links, i.e. signalling links which have not been put into operation. Predetermined signalling terminals and a signalling data link are associated with each inactive signalling link.
+
+The number of active and inactive signalling links in the absence of failures, and the priority order for the signalling links in a link set, should be identical at both ends of the link set.
+
+NOTE – In the typical case, all signalling links in a link set are active in the absence of failures.
+
+**12.2.1.2** When a decision is taken to activate an inactive signalling link, initial alignment starts. If the initial alignment procedure is successful, the signalling link is active and a signalling link test is started. If the signalling link test is successful the link becomes ready to convey signalling traffic. In the case when initial alignment is not possible, as determined at Message Transfer Part level 2 (see clause 7/Q.703), new initial alignment procedures are started on the same signalling link after a time T17 (delay to avoid the oscillation of initial alignment failure and link restart. The value of T17 should be greater than the loop delay and less than timer T2, see 7.3/Q.703). If the signalling link test fails, link restoration starts until the signalling link is activated or a manual intervention is made.
+
+#### **12.2.2 Signalling link restoration**
+
+After a signalling link failure is detected, signalling link initial alignment will take place. In the case when the initial alignment procedure is successful, a signalling link test is started. If the signalling link test is successful the link becomes restored and thus available for signalling.
+
+If initial alignment is not possible, as determined at Message Transfer Part level 2 (see clause 7/Q.703), new initial alignment procedures may be started on the same signalling link after a time T17 until the signalling link is restored or a manual intervention is made, e.g. to replace the signalling data link or the signalling terminal.
+
+If the signalling link test fails, the restoration procedure is repeated until the link is restored or a manual intervention made.
+
+#### **12.2.3 Signalling link deactivation**
+
+An active signalling link may be made inactive by means of a deactivation procedure, provided that no signalling traffic is carried on that signalling link. When a decision has been taken to deactivate a signalling link, the signalling terminal of the signalling link is taken out of service.
+
+#### **12.2.4 Link set activation**
+
+A signalling link set not having any signalling links in service is started by means of a link set activation procedure. Two alternative link set activation procedures are defined:
+
+- link set normal activation;
+- link set emergency restart.
+
+##### **12.2.4.1 Link set normal activation**
+
+Link set normal activation is applicable when a link set is to be put into service for the first time (link set initial activation) or when a link set is to be restarted (link set normal restart); the latter is applicable for example in the case when:
+
+- all signalling links in a link set are faulty;
+- a processor restart in a signalling point makes it necessary to re-establish a link set;
+
+- a signalling point recognizes other irregularities concerning the interworking between the two signalling points,
+
+provided that none of the above events creates an emergency situation.
+
+When link set normal activation is initiated, signalling link activation starts on as many signalling links as possible. (All signalling links in the link set are regarded as being inactive at the start of the procedure.)
+
+The signalling link activation procedures are performed on each signalling link in parallel as specified in 12.2.1 until the signalling links are made active.
+
+Signalling traffic may, however, commence when one signalling link is successfully activated.
+
+##### **12.2.4.2 Link set emergency restart**
+
+Link set emergency restart is applicable when an immediate re-establishment of the signalling capability of a link set is required, (i.e. in a situation when the link set normal restart procedure is not fast enough). The precise criteria for initiating link set emergency restart instead of normal restart may vary between different applications of the signalling system. Possible situations for emergency restart are, for example:
+
+- when signalling traffic that may be conveyed over the link set to be restarted is blocked;
+- when it is not possible to communicate with the signalling point at the remote end of the link set.
+
+When link set emergency restart is initiated, signalling link activation starts on as many signalling links as possible, in accordance with the principles specified for normal link set activation. In this case, the signalling terminals will have emergency status (see clause 7/Q.703) resulting in the sending of status indications of type "E" when applicable. Furthermore, the signalling terminals employ the emergency proving procedure and short time-out values in order to accelerate the procedure.
+
+When the emergency situation ceases, a transition from emergency to normal signalling terminal status takes place resulting in the employment of the normal proving procedure and normal time-out values.
+
+##### **12.2.4.3 Time-out values**
+
+The initial alignment procedure (specified in 7.3/Q.703) includes time-outs, the expiry of which indicates the failure of an activation or restoration attempt.
+
+### **12.3 Signalling link management procedures based on automatic allocation of signalling terminals**
+
+#### **12.3.1 Signalling link activation**
+
+**12.3.1.1** In the absence of failures, a link set contains a certain predetermined number of active (i.e. aligned) signalling links. The link set may also contain a number of inactive signalling links.
+
+An inactive signalling link is a signalling link not in operation. A predetermined signalling data link is associated with each inactive signalling link; however, signalling terminals may not yet be allocated.
+
+The number of active and inactive signalling links in the absence of failures, and the priority order for the signalling links in a link set, should be identical at both ends of the link set.
+
+**12.3.1.2** Whenever the number of active signalling links is below the value specified for the link set, actions to activate new inactive signalling links should be taken automatically. This is applicable, for example, when a link set is to be brought into service for the first time (see 12.3.4) or when a link failure occurs. In the latter case, activation starts when the restoration attempts on the faulty link are considered unsuccessful (see 12.3.2).
+
+The signalling link(s) to activate is the inactive link(s) having the highest priority in the link set.
+
+Generally, if it is not possible to activate a signalling link, an attempt to activate the next inactive signalling link (in priority order) is made. In the case when an activation attempt performed on the last signalling link in the link set is unsuccessful, the "next" signalling link is the first inactive signalling link in the link set (i.e. there is a cyclic assignment).
+
+Activation of a signalling link may also be initiated manually.
+
+Activation shall not be initiated automatically for a signalling link previously deactivated by means of a manual intervention.
+
+**12.3.1.3** When a decision is taken to activate a signalling link, the signalling terminal to be employed has to be allocated at each end.
+
+The signalling terminal is allocated automatically by means of the function defined in 12.5.
+
+In the case when the automatic allocation function cannot provide a signalling terminal the activation attempt is aborted.
+
+The predetermined signalling data link which may be utilized for other purposes when not connected to a signalling terminal must be removed from its alternative use (e.g. as a speech circuit) before signalling link activation can start.
+
+**12.3.1.4** The chosen signalling terminal is then connected to the signalling data link and initial alignment starts (see clause 7/Q.703).
+
+If the initial alignment procedure is successful, the signalling link is active and a signalling link test is started. If the signalling link test is successful the link becomes ready to convey signalling traffic.
+
+If initial alignment is not possible, as determined at Message Transfer Part level 2 (see clause 7/Q.703), the activation is unsuccessful and activation of the next inactive signalling link (if any) after a time T17 is initiated. Successive initial alignment attempts may, however, continue on the previous (faulty) signalling link after a time T17 until it is restored or its signalling terminal is disconnected (see 12.5).
+
+In view of the fact that if it is not possible to activate a signalling link, an attempt is made to activate the next inactive signalling link in a link set, it may be that the two ends of a link set continuously attempt to activate different signalling links. By having different values of initial alignment time-out T2 at the two ends of the link set (see 12.3.4.3), it is ensured that eventually both ends of the link set will attempt to activate the same signalling link.
+
+#### **12.3.2 Signalling link restoration**
+
+**12.3.2.1** After a signalling link failure is recognized, signalling link initial alignment will take place (see clause 7/Q.703). In the case when the initial alignment is successful, a signalling link test is started. If the signalling link test is successful the link becomes restored and thus available for signalling. If the initial alignment is unsuccessful or the test fails, the signalling terminals and signalling link may be faulty and require replacement.
+
+**12.3.2.2** The signalling terminal may be automatically replaced in accordance with the principles defined for automatic allocation of signalling terminals (see 12.5). After the new signalling terminal has been connected to the signalling data link, signalling link initial alignment starts. If successful, the signalling link is restored.
+
+If initial alignment is not possible or if no alternative signalling terminal is available for the faulty signalling link, activation of the next signalling link in the link set (if any) starts. In the case when it is not appropriate to replace the signalling terminal of the faulty signalling link (e.g. because it is assumed that the signalling data link is faulty) activation of the next inactive signalling link (if any) is also initiated. In both cases successive initial alignment attempts may continue on the faulty signalling link after a time T17 until a manual intervention is made or the signalling terminal is disconnected (see 12.5).
+
+NOTE – In the case when a signalling terminal cannot be replaced, activation of the next signalling link is only initiated if the link set includes an alternative link group having access to signalling terminals other than the one used by the signalling link for which restoration is not possible.
+
+#### **12.3.3 Signalling link deactivation**
+
+In the absence of failures a link set contains a specified number of active (i.e. aligned) signalling links. Whenever that number is exceeded (e.g. as a result of signalling link restoration), the active signalling link having the lowest priority in the link set is to be made inactive automatically provided that no signalling traffic is carried on that signalling link.
+
+Deactivation of a particular signalling link may also be initiated manually, for example in conjunction with manual maintenance activities.
+
+When a decision has been taken to deactivate a signalling link, the signalling terminal and signalling data link may be disconnected.
+
+After deactivation, the idle signalling terminal may become part of other signalling links (see 12.5).
+
+#### **12.3.4 Link set activation**
+
+A signalling link set not having any signalling links in service is started by means of a link set activation procedure. The objective of the procedure is to activate a specified number of signalling links for the link set. The activated signalling links should, if possible, be the signalling links having the highest priority in the link set. Two alternative link set activation procedures are defined:
+
+- link set normal activation;
+- link set emergency restart.
+
+##### **12.3.4.1 Link set normal activation**
+
+Link set normal activation is applicable when a link set is to be put into service for the first time (link set initial activation) or when a link set is to be restarted (link set normal restart); the latter is applicable, for example, in the case when:
+
+- all signalling links in a link set are faulty;
+- a processor restart in a signalling point makes it necessary to re-establish a link set;
+- a signalling point recognizes other irregularities concerning the interworking between the two signalling points, e.g. that a certain signalling data link is associated with different signalling links at the two ends of the link set,
+
+provided that none of the above events creates an emergency situation.
+
+When link set normal activation is initiated, signalling link activation starts on as many signalling links as possible. (All signalling links in the link set are regarded as being inactive at the start of the procedure). If activation cannot take place on all signalling links in the link set (e.g. because a sufficient number of signalling terminals is not available), then the signalling links to activate are determined in accordance with the link priority order.
+
+NOTE – All idle signalling terminals may not necessarily be made available for link set activation. Thus making possible, for example, restoration of faulty signalling links in other link sets at the same time.
+
+The signalling link activation procedures are performed as specified in 12.3.1.
+
+If the activation attempt for a signalling link is unsuccessful (i.e. initial alignment is not possible), activation of the next inactive signalling link, if any, in the priority order is initiated. (Inactive links exist in the case when the number of signalling terminals available is less than the number of signalling links defined for the link set). According to the principles for automatic allocation of signalling terminals defined in 12.5, the signalling terminal connected to the unsuccessfully activated signalling link will typically be connected to the signalling data link of that signalling link for which the new activation attempt is to be made.
+
+When a signalling link is successfully activated, signalling traffic may commence.
+
+After the successful activation of one signalling link, the activation attempts on the remaining signalling links continue in accordance with the principles defined in 12.3.1, in such a way that the signalling links having the highest priorities are made active. This is done in order to obtain, if possible, the normal configuration within the link set. Signalling link activation continues until the predetermined number of active signalling links is obtained.
+
+##### **12.3.4.2 Link set emergency restart**
+
+Link set emergency restart is applicable in the case the link set normal restart procedure is not fast enough. Emergency restart is performed in the same way as link set normal activation except that, in the case of emergency restart, the emergency proving procedure and the short emergency time-out values (see clause 7/Q.703) are employed in order to accelerate the procedure (see further 12.2.4.2).
+
+##### **12.3.4.3 Time-out values**
+
+The values of the initial alignment time-out T2 (see clause 7/Q.703) will be different at the two ends of the link set, if automatic allocation of signalling terminals or signalling data links is applied at both ends of a signalling link set.
+
+### **12.4 Signalling link management procedures based on automatic allocation of signalling data links and signalling terminals**
+
+#### **12.4.1 Signalling link activation**
+
+**12.4.1.1** In the absence of failures a link set contains a certain predetermined number of active (i.e. aligned) signalling links. The link set may also contain a number of inactive signalling links.
+
+An inactive signalling link is a signalling link currently not in operation. It is not associated with any signalling terminal or signalling data link (i.e. the signalling link is only identified by its position in the link set).
+
+The number of active and inactive signalling links (in the absence of failures), and the priority order for the signalling links in a link set, should be identical at both ends of the link set.
+
+**12.4.1.2** Whenever the number of active signalling links is below the value specified for the link set, actions to activate new inactive signalling links should be taken automatically. This is, for example, applicable when a link set is to be brought into service for the first time (see 12.4.4) or when a link failure occurs. In the latter case, activation starts when the restoration attempts on the faulty link are considered unsuccessful (see 12.4.2).
+
+The signalling link(s) to activate is the inactive link(s) having the highest priority in the link set.
+
+If it is not possible to activate a signalling link, an attempt to activate the next inactive signalling link (in priority order) is made. In the case when an activation attempt performed on the last signalling link in the link set is unsuccessful, the "next" signalling link is the first inactive link in the link set (i.e. a cyclic assignment).
+
+NOTE – Activation of the next signalling link is only initiated if the link set includes an alternative link group, having access to other signalling terminals and/or other signalling data links than the signalling link for which activation is not possible.
+
+Activation of a particular signalling link may also be initiated upon receiving a request from the remote signalling point, or by a manual request.
+
+Activation shall not be initiated automatically for a signalling link previously inactivated by means of a manual intervention.
+
+**12.4.1.3** When a decision is taken to activate a signalling link, the signalling terminals and signalling data link to be employed have to be allocated.
+
+A signalling terminal is allocated automatically by means of the function defined in 12.5.
+
+The signalling data link is allocated automatically by means of the function defined in 12.6. However, in conjunction with link set activation the identity of the signalling data link to use may be predetermined (see further 12.4.4). A signalling data link which is not connected to a signalling terminal may be utilized for other purposes, e.g. as a speech circuit. When the data link is to be employed for signalling, it must be removed from its alternative use.
+
+In the case when the automatic allocation functions cannot provide a signalling terminal or a signalling data link, the activation attempt is aborted.
+
+**12.4.1.4** When the signalling data link and signalling terminal to be used for a particular signalling link are determined, the signalling terminal is connected to the signalling data link and signalling link initial alignment starts (see clause 7/Q.703). If the initial alignment procedure is successful, the signalling link is active and a signalling link test is started. If the signalling link test is successful, the link becomes ready to convey signalling traffic.
+
+If initial alignment is not possible, as determined at Message Transfer Part level 2 (see clause 7/Q.703), alternative signalling data links are automatically connected to the signalling terminal, until an initial alignment procedure is successfully completed. In the case when the function for automatic allocation of signalling data links cannot provide an alternative signalling data link, the activation is regarded as unsuccessful and activation of the next inactive signalling link (if any) is initiated (see, however, the Note to 12.4.1.2 above). Successive initial alignment attempts may continue on the previous signalling link after a time T17 until it is activated or its signalling terminal is disconnected (see 12.5).
+
+#### **12.4.2 Signalling link restoration**
+
+**12.4.2.1** After a signalling link failure is recognized, signalling link initial alignment will take place (see clause 7/Q.703). In the case when the initial alignment is successful, a signalling link test is started. If the signalling link test is successful the link becomes restored and thus available for signalling.
+
+If the initial alignment is unsuccessful or if the test fails, the signalling terminal and signalling data link may be faulty and require replacement.
+
+**12.4.2.2** The signalling data link may be automatically replaced by an alternative, in accordance with the principles defined in 12.6. After the new signalling data link has been connected to the signalling terminal, signalling link initial alignment starts. If successful, the signalling link is restored. If not, alternative data links are connected to the signalling terminal, until an initial alignment procedure is successfully completed.
+
+If the automatic allocation function cannot provide a new signalling data link, activation of the next inactive signalling link (if any) is initiated (see, however, the Note to 12.4.1.2). Successive initial alignment attempts may, however, continue on the previous (faulty) signalling link after a time T17 until it is restored or its signalling terminal is disconnected.
+
+**12.4.2.3** The signalling terminal may be automatically replaced in accordance with the principles defined in 12.5. After the new signalling terminal has been connected to the signalling data link, signalling link initial alignment starts. If successful, the signalling link is restored. If not, activation of the next signalling link in the link set (if any) starts (see, however, the Note to 12.4.1.2).
+
+Successive initial alignment attempts may, however, continue on the previous (faulty) signalling link after a time T17 until it is restored or, for example, the signalling terminal or signalling data link is disconnected.
+
+NOTE – Activation of the next signalling link in the link set should not be initiated as long as one of the activities described in 12.4.2.2 and 12.4.2.3 above is taking place.
+
+#### **12.4.3 Signalling link deactivation**
+
+In the absence of failures, a link set contains a specified number of active (i.e. aligned) signalling links. Whenever that number is exceeded (e.g. as a result of signalling link restoration) the active signalling link having the lowest priority in the link set is to be made inactive automatically, provided that no signalling traffic is carried on that signalling link.
+
+Deactivation of a particular signalling link may also be initiated manually, e.g. in conjunction with manual maintenance activities.
+
+When a decision has been taken to deactivate a signalling link, the signalling terminal and signalling data link may be disconnected. After deactivation the idle signalling terminal and signalling data link may become parts of other signalling links (see 12.5 and 12.6).
+
+#### **12.4.4 Link set activation**
+
+Link set activation is applicable in the case when a link set not having any signalling links in service is to be started for the first time or after a failure (see 12.3.4). The link set activation procedure is performed as specified in 12.3.4, also as regards the allocation of signalling data links, i.e. signalling data links are allocated in accordance with predetermined list assigning a signalling data link to some or all of the signalling links in the link set. This is done in order to cater for the situation when it is not possible to communicate with the remote end of the link set (see 12.6). However, when a signalling link has become active, signalling data link allocation may again be performed automatically (i.e. activation of a signalling link takes place as specified in 12.4.1).
+
+### 12.5 Automatic allocation of signalling terminals
+
+In conjunction with the signalling link activation and restoration procedures specified in 12.3 and 12.4, signalling terminals may be allocated automatically to a signalling link. A signalling terminal applicable to the link group is allocated in accordance with the following principles:
+
+- a) an idle signalling terminal (i.e. a signalling terminal not connected to a signalling data link) is chosen if possible;
+- b) if no idle signalling terminal is available, a signalling terminal is chosen which is connected to an unsuccessfully restored or activated signalling link.
+
+NOTE 1 – Activation and restoration is regarded as unsuccessful when it is not possible to complete the initial alignment procedure successfully (see 12.3 and 12.4).
+
+Measures should be employed to ensure that signalling terminal to be allocated to signalling links are able to function correctly (see Recommendation Q.707).
+
+A link set may be assigned a certain number of signalling terminals. A signalling terminal may be transferred from a signalling link in one link set to a signalling link in another set [in accordance with b) above] only when the remaining number of signalling terminals in the link set is not below the specified value.
+
+NOTE 2 – From a link set with a minimum number of signalling terminals, only one signalling terminal and signalling data link may be removed at a time (e.g. for testing, see Recommendation Q.707).
+
+### 12.6 Automatic allocation of signalling data links
+
+**12.6.1** In conjunction with the signalling link activation and restoration procedures specified in 12.4, signalling data links may be allocated automatically. Any signalling data link applicable to a link group may be chosen for a signalling link within that link group.
+
+The signalling data links applicable to a link group are determined by bilateral agreement and may, for example, include all speech circuits between two exchanges. A signalling data link may also be established as a semi-permanent connection via one or more intermediate exchanges.
+
+When a potential signalling data link is not employed for signalling, it is normally used for other purposes (e.g. as a speech circuit).
+
+The identity of the signalling data link to be used for a particular signalling link is determined at one of the two involved signalling points and reported to the remote end by a signalling data link connection order message. The signalling point controlling the choice of signalling data link is the signalling point initiating the activation or restoration procedure or, in the case when both ends initiate the procedure at the same time, the signalling point having the highest signalling point code (included in the label of the message).
+
+**12.6.2** When a signalling data link has been chosen at a signalling point, the data link is made unavailable for other uses (e.g. as a speech circuit) and an order to connect the appointed signalling data link to a signalling terminal is sent to the signalling point at the remote end of the signalling link.
+
+The signalling-data-link-connection-order message contains:
+
+- the label, indicating the destination and originating signalling points and the identity of the signalling link to activate or restore;
+- the signalling-data-link-connection-order;
+- the identity of the signalling data link.
+
+Formats and codes for the signalling-data-link-connection-order message appear in clause 15.
+
+**12.6.3** Upon reception of the signalling-data-link-connection-order, the following applies:
+
+- a) In the case when the signalling link to which a received signalling-data-link-connection-order message refers is inactive as seen from the receiving signalling point, the message is regarded as an order to activate the concerned signalling link, resulting in, for example, allocation of a signalling terminal. The signalling data link indicated in the signalling-data-link-connection-order is then connected to the associated signalling terminal and signalling link initial alignment starts. An acknowledgement is sent to the remote signalling point.
+
+If it is not possible to connect the appointed signalling data link to a signalling terminal (e.g. because there is no working signalling terminal available), the acknowledgement contains an indication informing the remote signalling point whether or not an alternative signalling data link should be allocated to the concerned signalling link.
+
+- b) If the signalling point receives a signalling-data-link-connection-order when waiting for an acknowledgement, the order is disregarded in the case when the signalling point code of the receiving signalling point is higher than the signalling point code of the remote signalling point. If the remote signalling point has the higher signalling point code, the message is acknowledged and the signalling data link referred to in the received message is connected.
+- c) If a signalling-data-link-connection-order is received in other situations (e.g. in the case of an error in procedure), no actions are taken.
+
+The signalling-data-link-connection-acknowledgement contains the label, indicating the destination and originating signalling points and the identity of the signalling link to activate or restore, and one of the following signals:
+
+- connection-successful signal, indicating that the signalling data link has been connected to a signalling terminal;
+- connection-not-successful signal, indicating that it was not possible to connect the signalling data link to a signalling terminal, and that an alternative signalling data link should be allocated;
+- connection-not-possible signal, indicating that it was not possible to connect the signalling data link to a signalling terminal, and that no alternative signalling data link should be allocated.
+
+The formats and codes for the signalling data link connection acknowledgement message appear in clause 15.
+
+**12.6.4** When the signalling point initiating the procedure receives a message indicating that signalling data link and signalling terminal have been connected at the remote end, the signalling data link is connected to the associated signalling terminal and initial alignment starts (see 12.4).
+
+If the acknowledgement indicates that it was not possible to connect the signalling data link to a signalling terminal at the remote end, an alternative signalling data link is allocated and a new signalling-data-link-connection-order is sent (as specified above). However, if the acknowledgement indicates that no alternative signalling data link should be allocated, the activation or restoration procedure is terminated for the concerned signalling link.
+
+If no signalling-data-link-connection-acknowledgement or order is received from the remote signalling point within a time T7 (see clause 16), the signalling-data-link-connection-order is repeated.
+
+**12.6.5** When a signalling data link is disconnected in conjunction with signalling link restoration or deactivation, the signalling data link is made idle (and available, e.g. as a speech circuit).
+
+### 12.7 Different signalling link management procedures at the two ends of a link set
+
+Normally both ends of a link set will use the same signalling link management procedures.
+
+However, if one end uses the basic signalling link management procedures, the other end may use the signalling link management procedures based on automatic allocation of signalling terminals. In that case a signalling link includes a predetermined signalling terminal at one end, a predetermined signalling data link and at the other end, any of the signalling terminals applicable to the concerned link group.
+
+If one end of a link set uses the basic signalling link management procedures and the other end uses the signalling link management procedures based on automatic allocation of signalling terminals, the values of the initial alignment time-out T2 do not have to be different at the two ends of the link set.
+
+## 13 Signalling route management
+
+### 13.1 General
+
+The purpose of the signalling route management function is to ensure a reliable exchange of information between the signalling points about the availability of the signalling routes.
+
+The unavailability, restriction1 and availability of a signalling route is communicated by means of the transfer-prohibited, transfer-restricted1 and transfer-allowed procedures, respectively in 13.2, 13.4 and 13.3.
+
+Recovery of signalling route status information is made by means of the signalling-route-set-test procedure specified in 13.5.
+
+In the international signalling network, congestion of a route set is communicated by means of the transfer-controlled (TFC) messages specified in 13.6.
+
+In national networks, congestion of a signalling route set may be communicated by means of the TFC as specified in 13.7 and 13.8 and the signalling-route-set-congestion-test procedure specified in 13.9.
+
+### 13.2 Transfer-prohibited
+
+**13.2.1** The transfer-prohibited procedure is performed at a signalling point acting as a signalling transfer point for messages relating to a given destination, when it has to notify one or more adjacent signalling points that they must no longer route the concerned messages via that signalling transfer point.
+
+The transfer-prohibited procedure makes use of the transfer-prohibited message which contains:
+
+- the label, indicating the destination and originating points;
+- the transfer-prohibited signal; and
+- the destination for which traffic transfer is no longer possible.
+
+Format and code of these messages appear in clause 15.
+
+Transfer-prohibited messages are always addressed to an adjacent signalling point. They may use any available signalling route that leads to that signalling point6.
+
+---
+
+6 The possibility of referring to a more general destination than a single signalling point (e.g. a signalling region), or more restrictive destination than a single signalling point might need further study.
+
+**13.2.2** A transfer-prohibited message relating to a given destination X is sent from a signalling transfer point Y in the following cases:
+
+- i) When signalling transfer point Y starts to route (at changeover, changeback, forced or controlled rerouting) signalling destined to signalling point X via a signalling transfer point Z not currently used by signalling transfer point Y for this traffic. In this case the transfer-prohibited message is sent to signalling transfer point Z.
+- ii) When signalling transfer point Y recognizes the inaccessibility of signalling point X (see 5.3.3 and 7.2.3). In this case a transfer-prohibited message is sent to all accessible adjacent signalling points (Broadcast method) and timer T8 (see clause 16) is started concerning SP X.
+- iii) When a message destined to signalling point X is received at signalling transfer point Y and Y is unable7 to transfer the message, and if no corresponding timer T8 is running. In this case the transfer-prohibited message is sent to the adjacent signalling point from which the message concerned was received (Response Method). In addition, timer T8 is started concerning SP X.
+- iv) When an adjacent signalling point Z becomes accessible, STP Y sends to Z a transfer prohibited message concerning destination X, if X is inaccessible from Y (see clause 9).
+- v) When a signalling transfer point Y restarts, it broadcasts to all accessible adjacent signalling points transfer prohibited messages concerning destination X, if X is inaccessible from Y (see clause 9).
+
+Within T8 (see clause 16) after the last transfer-prohibited message was transmitted according to ii) or iii) above no transfer prohibited message will be sent via the Response Method referring to that destination.
+
+Examples of the above situation appear in Recommendation Q.705.
+
+**13.2.3** When a signalling point receives a transfer-prohibited message from signalling transfer point Y, it performs the actions specified in clause 7 (since reception of transfer-prohibited message indicates the unavailability of the concerned signalling route, see 3.4.1). In other words, it may perform forced re-routing and, if appropriate, generate additional transfer-prohibited messages.
+
+**13.2.4** In some circumstances it may happen that a signalling point receives either a repeated transfer-prohibited message relating to a non-existent route (i.e. there is no route from that signalling point to the concerned destination via signalling transfer point Y, according to the signalling network configuration) or to a destination which is already inaccessible, due to previous failures; in this case no actions are taken.
+
+### **13.3 Transfer-allowed**
+
+**13.3.1** The transfer-allowed procedure is performed at a signalling point, acting as signalling transfer point for messages relating to a given destination, when it has to notify one or more adjacent signalling points that they may start to route to it, if appropriate, the concerned messages.
+
+---
+
+7 "unable" normally means that X is inaccessible or that Y has no routing data for X. It might be of advantage in national networks (at the discretion of the network operator) not to send a TFP if no routing data for X exists at Y. This would avoid signalling route set tests for non-existent destinations, which otherwise might destabilize the network.
+
+The transfer-allowed procedure makes use of the transfer-allowed message which contains:
+
+- the label, indicating the destination and originating points;
+- the transfer-allowed signal; and
+- the destination for which transfer is now possible.
+
+The format and code of these messages appear in clause 15.
+
+Transfer-allowed messages are always addressed to an adjacent signalling point. They may use any available signalling route that leads to that signalling point6.
+
+**13.3.2** A transfer-allowed message relating to a given destination X is sent from signalling transfer point Y in the following cases:
+
+- i) When signalling transfer point Y stops routing (at changeback or controlled re-routing), signalling traffic destined to signalling point X via a signalling transfer point Z (to which the concerned traffic was previously diverted as a consequence of changeover or forced rerouting). In this case the transfer-allowed message is sent to signalling transfer point Z.
+- ii) When signalling transfer point Y recognizes that it is again able to transfer signalling traffic destined to signalling point X (see 6.2.3 and 8.2.3). In this case a transfer-allowed message is sent to all accessible adjacent signalling points, except those signalling points that receive a TFP message according to 13.2.2 i) and except signalling point X if it is an adjacent point. (Broadcast method).
+
+Examples of the above situations appear in Recommendation Q.705.
+
+**13.3.3** When a signalling point receives a transfer-allowed message from signalling transfer point Y, it performs the actions specified in clause 8 [since reception of a transfer-allowed message indicates the availability of the concerned signalling route, (see 3.4.2)]. In other words, it may perform controlled re-routing and, if appropriate, generate additional transfer-allowed messages.
+
+**13.3.4** In some circumstances it may happen that a signalling point receives either a repeated transfer-allowed message or a transfer-allowed message relating to a non-existent signalling route (i.e. there is no route from that signalling point to the concerned destination via signalling transfer point Y according to the signalling network configuration); in this case no actions are taken.
+
+### **13.4 Transfer-restricted (National option)**
+
+**13.4.1** The transfer-restricted procedure is performed at a signalling point acting as a signalling transfer point for messages relating to a given destination, when it has to notify one or more adjacent signalling points that they should, if possible, no longer route the concerned messages via the signalling transfer point.
+
+The transfer-restricted procedure makes use of the transfer-restricted message which contains:
+
+- the label, indicating the destination and originating points;
+- the transfer-restricted signal; and
+- the destination for which traffic is no longer desirable.
+
+Formats and codes of this message appear in clause 15.
+
+Transfer-restricted messages are always addressed to an adjacent signalling point. They may use any available signalling route that leads to that signalling point.
+
+NOTE – Undesirable situations result in increased signalling delays, possibly overloading portions of the network. These inefficiencies could be avoided if the traffic can be appropriately diverted.
+
+**13.4.2** A transfer-restricted message relating to a given destination X is sent from a signalling transfer point Y when the normal link set (combined link set) used by signalling point Y to route to destination X experiences a long-term failure such as an equipment failure, or there is congestion on an alternate link set currently being used to destination X. In this case, a transfer-restricted message is sent to all accessible adjacent signalling points except those that receive a TFP message according to 13.2.2 i), and except signalling point X if it is an adjacent point (Broadcast Method).
+
+When an adjacent signalling point X becomes accessible, the STP Y sends to X transfer-restricted messages concerning destinations that are restricted from Y (see clause 9).
+
+When a signalling point Y restarts, it broadcasts to all accessible adjacent signalling points transfer-restricted messages concerning destinations that are restricted from Y (see clause 9).
+
+NOTE – Characterization of long-term failure remains for further study.
+
+**13.4.3** When a signalling point receives a transfer-restricted message from signalling transfer point Y and has an alternative equal priority link set available and not restricted to destination X, it performs the actions in 8.2. In other words, it performs controlled re-routing to maintain the sequence of messages while diverting them to the alternative link set. If it cannot perform alternate routing to destination X because no alternative link set is available, it may generate additional transfer-restricted messages.
+
+**13.4.4** In some circumstances, it may happen that a signalling point receives either a repeated transfer-restricted message or a transfer-restricted message relating to a non-existent route (i.e. there is no route from that signalling point to the concerned destination via signalling transfer point Y, according to the signalling network configuration); in this case, no actions are taken.
+
+**13.4.5** When a transfer-restricted message is received updating a transfer-prohibited status, signalling traffic management decides if an alternative route is available or restricted; if it is not (i.e. no alternative route exists), the concerned traffic is restarted towards the signalling point from which the transfer-restricted message was received. Otherwise, no other actions are taken.
+
+### **13.5 Signalling-route-set-test**
+
+**13.5.1** The signalling-route-set-test procedure is used at a signalling point to test whether or not signalling traffic towards a certain destination may be routed via an adjacent signalling transfer point. The procedure makes use of the signalling-route-set-test message, and the transfer-allowed and the transfer-prohibited procedures.
+
+The signalling-route-set-test message contains:
+
+- the label, indicating the destination and originating points;
+- the signalling-route-set-test signal;
+- the destination, the accessibility of which is to be tested; and
+- the current route status of the destination being tested6.
+
+The format and coding of this message appear in clause 15.
+
+**13.5.2** A signalling-route-set-test message is sent from a signalling point after a transfer-prohibited or transfer-restricted1 message is received from an adjacent signalling transfer point (see 13.2.4 and 13.4.4). In this case, a signalling-route-set-test message is sent to that signalling transfer point referring to the destination declared inaccessible or restricted by the transfer-prohibited or transfer-restricted1 message, every T10 period (see clause 16) until a transfer-allowed message, indicating that the destination has become accessible, is received.
+
+This procedure is used in order to recover the signalling route availability information that may not have been received because of some signalling network failure.
+
+**13.5.3** A signalling-route-set-test message is sent to the adjacent signalling transfer point as an ordinary signalling network management message.
+
+**13.5.4** At the reception of a signalling-route-set-test message, a signalling transfer point will compare the status of the destination in the received message with the actual status of the destination. If they are the same, no further action is taken. If they are different, one of the following messages is sent in response, dictated by the actual status of the destination:
+
+- a transfer-allowed message, referring to the destination the accessibility of which is tested, if the signalling transfer point can reach the indicated destination via a signalling link not connected to the signalling point from which the signalling-route-set-test message was received (and if the transfer restricted procedure is used in the network, the signalling link is on the normal route or an equally efficient alternative route);
+- a transfer-restricted1 message when access to the destination is possible via an alternative to the normal routing which is less efficient, but still not via the signalling point from which the signalling-route-set-test was originated;
+- a transfer-prohibited message in all other cases (including the inaccessibility of that destination).
+
+**13.5.5** At the reception of the transfer-prohibited or transfer-allowed message, the signalling point will perform the procedures specified in 13.2.3 or 13.2.4 and 13.3.3 or 13.3.4 respectively.
+
+### **13.6 Transfer-controlled (International network)**
+
+The only use made of the transfer-controlled procedure in the international signalling network is to convey the congestion indication from the SP where congestion was detected to the originating SP (see 11.2.3) in a transfer controlled message.
+
+The transfer controlled message contains:
+
+- the label, indicating the destination and origination points;
+- the transfer-controlled signal;
+- the identity of the congested destination.
+
+The format and coding of the transfer controlled message appear in clause 15.
+
+### **13.7 Transfer-controlled (National option with congestion priorities)**
+
+**13.7.1** The transfer-controlled procedure is performed at a signalling transfer point for messages relating to a given destination, when it has to notify one or more originating signalling points that they should no longer send to the concerned destination messages with a given priority or lower.
+
+The transfer-controlled procedure makes use of the transfer-controlled message which contains:
+
+- the label, indicating the destination and originating points;
+- the transfer-controlled signal;
+- the destination for which messages with a congestion priority lower than the specified congestion status should no longer be sent; and
+- the current congestion status encountered in routing a particular message towards the concerned destination.
+
+The format and coding of this message appear in clause 15.
+
+**13.7.2** A transfer-controlled message relating to a given destination X is sent from a signalling transfer point Y in response to a received message originating from signalling point Z destined to signalling point X when the congestion priority of the concerned message is less than the current congestion status of the signalling link selected to transmit the concerned message from Y to X.
+
+In this case, the transfer-controlled message is sent to the originating point Z with the congestion status field set to the current congestion status of the signalling link.
+
+**13.7.3** When the originating signalling point Z receives a transfer-controlled message relating to destination X, if the current congestion status of the signalling route set towards destination X is less than the congestion status in the transfer-controlled message, it updates the congestion status of the signalling route set towards destination X with the value of the congestion status carried in the transfer-controlled message.
+
+**13.7.4** If within T15 (see clause 16) after the receipt of the last transfer-controlled message relating to destination X, signalling point Z receives another transfer-controlled message relating to the same destination, the following action is taken:
+
+If the value of the congestion status carried in the new transfer-controlled message is greater than the current value of the congestion status of the signalling route set towards destination X, then the current value is updated to the new value.
+
+**13.7.5** If T15 (see clause 16) expires after the last update of the signalling route set towards destination X by a transfer-controlled message relating to the same destination, the signalling-route-set-congestion-test procedure is invoked (see 13.9).
+
+**13.7.6** In some circumstances it may happen that a signalling point receives a transfer-controlled message relating to a destination which is already inaccessible due to previous failures; in this case the transfer-controlled message is ignored.
+
+### **13.8 Transfer-controlled (National option without congestion priorities)**
+
+The only use made of the TFC procedure by the national signalling network, using multiple congestion states without congestion priorities, is to convey the congestion indication primitive from the SP where congestion was detected to the originating SP (see 11.2.5) in a transfer-controlled message.
+
+The transfer-controlled message contains:
+
+- the label, indicating the destination and originating points;
+- the transfer-controlled signal;
+- the identity of the congested destination;
+- the current congestion status encountered in routing a particular message towards the concerned destination.
+
+The format and coding of this message appear in clause 15.
+
+### **13.9 Signalling-route-set-congestion-test (National Option)**
+
+**13.9.1** The signalling-route-set-congestion-test procedure is used at an originating signalling point to update the congestion status associated with a route set towards a certain destination. The purpose is to test whether or not signalling messages destined towards that destination with a given congestion priority or higher may be sent.
+
+In the case of a processor restart the congestion status of all signalling route sets will be initialized to the zero value. The response mechanism within the transfer-controlled procedure will correct signalling route sets whose congestion status does not have the zero value.
+
+The procedure makes use of the signalling-route-set-congestion-test message, and the transfer-controlled procedure.
+
+The signalling-route-set-congestion-test message contains:
+
+- the label, indicating the destination and originating points; and
+- the signalling-route-set-congestion-test signal.
+
+The format and coding of this message appear in clause 15.
+
+**13.9.2** The signalling-route-set-congestion-test message differs from other signalling network management messages in that it is not assigned the highest congestion priority. Instead, the congestion priority assigned to a signalling-route-set-congestion-test message to be sent to a given destination is equal to one less than the current congestion status associated with the signalling route set towards the destination.
+
+**13.9.3** If within T16 (see clause 16), after sending a signalling-route-set-congestion-test message, a transfer-controlled message relating to the concerned destination is received, the signalling point updates the congestion status of the signalling route set towards the concerned destination with the value of the congestion status carried in the transfer-controlled message. Following this, the procedures specified in 13.9.4 and 13.9.5 are performed.
+
+If T16 (see clause 16) expires after sending a signalling-route-set-congestion-test message without a transfer-controlled message relating to the concerned destination having been received, the signalling point changes the congestion status associated with the signalling route set towards the concerned destination to the next lower status.
+
+**13.9.4** Provided that the signalling route set towards destination X is not in the "unavailable" state, a signalling-route-set-congestion-test message is sent from an originating signalling point to destination X in the following cases:
+
+- i) When T15 (see clause 16) expires after the last update of the congestion status of the signalling route set toward destination X by a transfer-controlled message relating to the same destination.
+- ii) When T16 (see clause 16) expires after sending a signalling-route-set-congestion-test message to destination X without a transfer-controlled message relating to the same destination having been received. After the congestion status has been decremented by one, the test is repeated, unless the congestion status is zero.
+
+**13.9.5** At the reception of a signalling-route-set-congestion-test message, a signalling transfer point will route it as an ordinary message, i.e. according to the procedure specified in 2.3.5.
+
+**13.9.6** When a signalling-route-set-congestion-test message reaches its destination, it is discarded.
+
+## 14 Common characteristics of message signal unit formats
+
+### 14.1 General
+
+The basic signal unit format which is common to all message signal units is described in clause 2/Q.703. From the point of view of the Message Transfer Part level 3 functions, common characteristics of the message signal units are the presence of:
+
+- the service information octet;
+- the label, contained in the signalling information field, and, in particular, the routing label.
+
+### 14.2 Service information octet
+
+The service information octet of message signal units contains the service indicator and the sub-service field. The structure of the service information octet is shown in Figure 13.
+
+
+
+Diagram of the Service Information Octet structure. It is a 1-byte octet divided into two 4-bit nibbles. The left nibble is the 'Sub-service field' and the right nibble is the 'Service indicator'. Both nibbles are labeled 'DCBA' at the top. Below each nibble is the number '4'. An arrow on the right points to the rightmost bit of the Service indicator, labeled 'First bit transmitted'. The diagram is labeled 'T1158970-94/d022'.
+
+Figure 13/Q.704 – Service information octet
+
+#### 14.2.1 Service indicator
+
+The service indicator is used by signalling handling functions to perform message distribution (see 2.4) and, in some special applications, to perform message routing (see 2.3).
+
+The service indicator codes *for the international signalling network* are allocated as follows:
+
+| bits | D | C | B | A | |
+|------|---|---|---|---|------------------------------------------------------------------|
+| | 0 | 0 | 0 | 0 | Signalling network management messages |
+| | 0 | 0 | 0 | 1 | Signalling network testing and maintenance messages |
+| | 0 | 0 | 1 | 0 | Spare |
+| | 0 | 0 | 1 | 1 | SCCP |
+| | 0 | 1 | 0 | 0 | Telephone User Part |
+| | 0 | 1 | 0 | 1 | ISDN User Part |
+| | 0 | 1 | 1 | 0 | Data User Part (call and circuit-related messages) |
+| | 0 | 1 | 1 | 1 | Data User Part (facility registration and cancellation messages) |
+| | 1 | 0 | 0 | 0 | Reserved for MTP Testing User Part |
+| | 1 | 0 | 0 | 1 | Broadband ISDN User Part |
+| | 1 | 0 | 1 | 0 | Satellite ISDN User Part |
+| | 1 | 0 | 1 | 1 | ) |
+| | 1 | 1 | 0 | 0 | ) |
+| | 1 | 1 | 0 | 1 | ) Spare |
+| | 1 | 1 | 1 | 0 | ) |
+| | 1 | 1 | 1 | 1 | ) |
+
+The allocation of the service indicator codes for national signalling networks is a national matter. However, it is suggested to allocate the same service indicator code to a User Part which performs similar functions as in the international network.
+
+#### 14.2.2 Sub-service field
+
+The sub-service field contains the network indicator (bits C and D) and two spare bits (bits A and B).
+
+The network indicator is used by signalling message handling functions (e.g. in order to determine the relevant version of a User Part), see 2.3 and 2.4.
+
+If the network indicator is set to 00 or 01, the two spare bits, coded 00, are available for possible future needs that may require a common solution for all international User Parts.
+
+If the network indicator is set to 10 or 11, the two spare bits are for national use. They may be used, for example, to indicate message priority, which is used in the optional flow control procedure in national applications.
+
+The network indicator provides for discrimination between international and national messages. It can also be used, for example, for the discrimination between functionally two national signalling networks, each having different routing label structures and including up to 16 User Parts defined by the 16 possible codes of the service indicator.
+
+In the case of only one national signalling network the spare code of the network indicator reserved for national use can be used, for example, to define an additional 16 User Parts (making a total of 32 User Parts) for that national signalling network.
+
+The network indicator codes are allocated as follows:
+
+| bits | D | C | |
+|------|---|---|------------------------------------|
+| | 0 | 0 | International network |
+| | 0 | 1 | Spare (for international use only) |
+| | 1 | 0 | National network |
+| | 1 | 1 | Reserved for national use |
+
+The international spare code (01) should not be used for implementing features which are to be provided both internationally and nationally.
+
+In national applications, when the discrimination provided by the network indicator between international and national messages is not used, i.e. in a closed national signalling network seen from the signalling point of view, the whole sub-service field can be used independently for different User Parts.
+
+### 14.3 Label
+
+The structure and content of the label is defined for each User Part and is defined in the relevant specification. The common part of the label used for signalling message handling, the routing label, is specified in 2.2.
+
+## 15 Formats and codes of signalling network management messages
+
+### 15.1 General
+
+**15.1.1** The signalling network management messages are carried on the signalling channel in message signal units, the format of which is described in clause 14 and in clause 2/Q.703. In particular, as indicated in 14.2, these messages are distinguished by the configuration 0000 of the Service Indicator (SI). The Sub-Service Field (SSF) of the messages is used according to the rules indicated in 14.2.2.
+
+**15.1.2** The signalling information field consists of an integral number of octets and contains the label, the heading code and one or more signals and indications. The structure and function of the label, and of the heading code, are described in 15.2 and 15.3, respectively; the detailed message formats are described in the following subclauses. For each message the sequence of fields is shown in the corresponding figure, including fields that may or may not be present.
+
+In the figures, the fields are shown starting from the right to the left (i.e. the first field to be transmitted is at the right). Within each field the information is transmitted least significant bit first. Spare bits are coded 0 unless otherwise indicated.
+
+### 15.2 Label
+
+For signalling network management messages the label coincides with the routing label and indicates the destination and originating signalling points of the message; moreover, in the case of messages related to a particular signalling link, it also indicates the identity of the signalling link among those interconnecting the destination and originating points. The standard label structure of Message Transfer Part level 3 messages appears in Figure 14; the total length is 32 bits.
+
+
+
+| | | | |
+|-----------------|-----|-----|-------------------------|
+| SLC | OPC | DPC | First bit transmitted → |
+| 4 | 14 | 14 | |
+| Length
(bit) | | | T1158980-94/d023 |
+
+**Figure 14/Q.704 – Standard label structure**
+
+The meaning and use of the Destination Point Code (DPC) and of the Originating Point Code (OPC) fields are described in clause 2. The Signalling Link Code (SLC) indicates the signalling link, connecting the destination and originating points, to which the message is related. If the message is not related to a signalling link, or another particular code is not specified, it is coded 0000.
+
+### 15.3 Heading code (H0)
+
+The heading code (H0) is the 4-bit field following the label and identifies the message group.
+
+The different heading codes are allocated as follows:
+
+- 0000 Spare
+- 0001 Changeover and changeback messages
+- 0010 Emergency changeover message
+- 0011 Transfer-controlled and signalling route set congestion messages
+- 0100 Transfer-prohibited-allowed-restricted messages
+- 0101 Signalling-route-set-test messages
+- 0110 Management inhibit messages
+- 0111 Traffic restart allowed message
+- 1000 Signalling-data-link-connection messages
+- 1001 Spare
+- 1010 User part flow control messages
+
+The remaining codings are spare.
+
+The synopsis of signalling network management messages is given in Table 1.
+
+**Table 1/Q.704 – Heading code allocation of signalling network management messages**
+
+| Message Group | H0 | H1 | | | | | | | | | | | | | | | |
+|---------------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|
+| | | 0000 | 0001 | 0010 | 0011 | 0100 | 0101 | 0110 | 0111 | 1000 | 1001 | 1010 | 1011 | 1100 | 1101 | 1110 | 1111 |
+| | 0000 | | | | | | | | | | | | | | | | |
+| CHM | 0001 | | COO | COA | | | CBD | CBA | | | | | | | | | |
+| ECM | 0010 | | ECO | ECA | | | | | | | | | | | | | |
+| FCM | 0011 | | RCT | TFC | | | | | | | | | | | | | |
+| TFM | 0100 | | TFP | * | TFR | | TFA | * | | | | | | | | | |
+| RSM | 0101 | | RST | RSR | | | | | | | | | | | | | |
+| MIM | 0110 | | LIN | LUN | LIA | LUA | LID | LFU | LLT | LRT | | | | | | | |
+| TRM | 0111 | | TRA | | | | | | | | | | | | | | |
+| DLM | 1000 | | DLC | CSS | CNS | CNP | | | | | | | | | | | |
+| | 1001 | | | | | | | | | | | | | | | | |
+| UFC | 1010 | | UPU | | | | | | | | | | | | | | |
+| | 1011 | | | | | | | | | | | | | | | | |
+| | 1100 | | | | | | | | | | | | | | | | |
+| | 1101 | | | | | | | | | | | | | | | | |
+| | 1110 | | | | | | | | | | | | | | | | |
+| | 1111 | | | | | | | | | | | | | | | | |
+
+NOTE – Values marked \* should not be used (codes used in the *Yellow Book* for TFP and TFA acknowledgement).
+
+CBA Changeback-acknowledgement signal
+CBD Changeback-declaration signal
+CHM Changeover and changeback messages
+CNP Connection-not-possible signal
+CNS Connection-not-successful signal
+COA Changeover-acknowledgement signal
+COO Changeover-order signal
+CSS Connection-successful signal
+DLC Signalling-data-link-connection-order signal
+DLM Signalling-data-link-connection-order message
+ECA Emergency-changeover-acknowledgement signal
+ECM Emergency-changeover message
+ECO Emergency-changeover-order signal
+FCM Signalling-traffic-flow-control messages
+LFU Link forced uninhibit signal
+LIA Link inhibit acknowledgement signal
+LID Link inhibit denied signal
+LIN Link inhibit signal
+LLT Link local inhibit test signal
+LUA Link uninhibit acknowledgement signal
+LUN Link uninhibit signal
+LRT Link remote inhibit test signal
+MIM Management inhibit messages
+RCT Signalling-route-set-congestion-test signal
+RSM Signalling-route-set-test message
+RSR Signalling-route-set-test signal for restricted destination (national option)
+RST Signalling-route-set-test signal for prohibited destination
+TFA Transfer-allowed signal
+TFC Transfer-controlled signal
+TFM Transfer-prohibited-transfer-allowed-transfer-restricted messages
+TFP Transfer-prohibited signal
+TFR Transfer-restricted signal (national option)
+TRA Traffic-restart-allowed signal
+TRM Traffic-restart-allowed message
+UFC User part flow control messages
+UPU User part unavailable signal
+
+### 15.4 Changeover message
+
+15.4.1 The format of the changeover message is shown in Figure 15.
+
+
+
+| | | | | | |
+|---|--------------------------|-----------------|-----------------|-------|----|
+| 0 | | DCBA | 0001 | | |
+| / | FSN of last accepted MSU | Heading code H1 | Heading code H0 | Label | |
+| | 1 | 7 | 4 | 4 | 32 |
+
+T1158990-94/d024
+
+**Figure 15/Q.704 – Changeover message**
+
+15.4.2 The changeover message is made up of the following fields:
+
+- Label (32 bits): see 15.2.
+- Heading code H0 (4 bits): see 15.3.
+- Heading code H1 (4 bits): see 15.4.3.
+- Forward sequence number of last accepted message signal unit (7 bits).
+- A filler bit coded 0
+
+15.4.3 The heading code H1 contains signal codes as follows:
+
+| bits | D | C | B | A | |
+|------|---|---|---|---|-----------------------------------|
+| | 0 | 0 | 0 | 1 | Changeover order signal |
+| | 0 | 0 | 1 | 0 | Changeover acknowledgement signal |
+
+### 15.5 Changeback message
+
+15.5.1 The format of the changeback message is shown in Figure 16.
+
+
+
+| | | | | |
+|-----------------|-----------------|-----------------|-------|-------------------------|
+| | DCBA | 0001 | | |
+| Changeback code | Heading code H1 | Heading code H0 | Label | |
+| 8 | 4 | 4 | 32 | First bit transmitted → |
+
+T1159000-94/d025
+
+**Figure 16/Q.704 – Changeback message**
+
+15.5.2 The changeback message is made up of the following fields:
+
+- Label (32 bits): see 15.2.
+- Heading code H0 (4 bits): see 15.3.
+- Heading code H1 (4 bits): see 15.5.3.
+- Changeback code (8 bits): see 15.5.4.
+
+15.5.3 The header code H1 contains signal codes as follows:
+
+| bits | D | C | B | A | |
+|------|---|---|---|---|-----------------------------------|
+| | 0 | 1 | 0 | 1 | Changeback declaration signal |
+| | 0 | 1 | 1 | 0 | Changeback acknowledgement signal |
+
+15.5.4 The changeback code is an 8-bit code assigned by the signalling point which sends the message according to the criteria described in clause 6.
+
+### 15.6 Emergency changeover message
+
+15.6.1 The format of the emergency changeover message is shown in Figure 17.
+
+
+
+| | | |
+|-----------------|-----------------|-------|
+| DCBA | 0010 | |
+| Heading code H1 | Heading code H0 | Label |
+| 4 | 4 | 32 |
+
+First bit transmitted →
+
+T1159010-94/d026
+
+Figure 17/Q.704 – Emergency changeover message
+
+15.6.2 The emergency changeover message is made up of the following fields:
+
+- Label (32 bits): see 15.2.
+- Heading code H0 (4 bits): see 15.3.
+- Heading code H1 (4 bits): see 15.6.3.
+
+15.6.3 The header code H1 contains signal codes as follows:
+
+| bits | D | C | B | A | |
+|------|---|---|---|---|---------------------------------------------|
+| | 0 | 0 | 0 | 1 | Emergency changeover order signal |
+| | 0 | 0 | 1 | 0 | Emergency changeover acknowledgement signal |
+
+### 15.7 Transfer-prohibited message
+
+15.7.1 The format of the transfer-prohibited message is shown in Figure 18.
+
+
+
+| | | | | |
+|----|-------------|-----------------|-----------------|-------|
+| 00 | | DCBA | 0100 | |
+| | Destination | Heading code H1 | Heading code H0 | Label |
+| 2 | 14 | 4 | 4 | 32 |
+
+First bit transmitted →
+
+T1159020-94/d027
+
+Figure 18/Q.704 – Transfer-prohibited message
+
+**15.7.2** The transfer-prohibited message is made up of the following fields:
+
+- Label (32 bits): see 15.2.
+- Heading code H0 (4 bits): see 15.3.
+- Heading code H1 (4 bits): see 15.7.3.
+- Destination (14 bits): see 15.7.4.
+- Spare bits (2 bits) code 00.
+
+**15.7.3** The heading code H1 contains one signal code as follows:
+
+| | | | | | |
+|-----|---|---|---|---|----------------------------|
+| bit | D | C | B | A | |
+| | 0 | 0 | 0 | 1 | Transfer-prohibited signal |
+
+**15.7.4** The destination field contains the identity of the signalling point to which the message refers.
+
+### **15.8 Transfer-allowed message**
+
+**15.8.1** The format of the transfer-allowed message is shown in Figure 19.
+
+
+
+| | | | | |
+|----|-------------|-----------------|-----------------|-------|
+| 00 | Destination | DCBA | 0100 | Label |
+| / | | Heading code H1 | Heading code H0 | |
+| 2 | 14 | 4 | 4 | 32 |
+
+T1159030-94/d028
+
+Arrow pointing right with text 'First bit transmitted'
+
+**Figure 19/Q.704 – Transfer-allowed message**
+
+**15.8.2** The transfer-allowed message is made up of the following fields:
+
+- Label (32 bits): see 15.2.
+- Heading code H0 (4 bits): see 15.3.
+- Heading code H1 (4 bits): see 15.8.3.
+- Destination (14 bits): see 15.7.4.
+- Spare bits (2 bits) coded 00.
+
+NOTE – For the use of the 2 spare bits in the national option for a SIF compatibility mechanism, see 7.2.6/Q.701.
+
+**15.8.3** The heading code H1 contains one signal code as follows:
+
+| | | | | | |
+|-----|---|---|---|---|-------------------------|
+| bit | D | C | B | A | |
+| | 0 | 1 | 0 | 1 | Transfer-allowed signal |
+
+### **15.9 Transfer-restricted message (national option)**
+
+**15.9.1** The format of the transfer-restricted message is shown in Figure 18.
+
+**15.9.2** The transfer-restricted message is made up of the following fields:
+
+- Label (32 bits): see 15.2.
+- Heading code H0 (4 bits): see 15.3.
+- Heading code H1 (4 bits): see 15.9.3.
+
+- Destination (14 bits): see 15.9.4.
+- Spare (2 bits) coded 00.
+
+**15.9.3** The heading code H1 contains one signal code as follows:
+
+| | | | | | |
+|-----|---|---|---|---|---------------------|
+| bit | D | C | B | A | |
+| | 0 | 0 | 1 | 1 | Transfer-restricted |
+
+**15.9.4** The destination field contains the identity of the signalling point to which the message refers.
+
+### 15.10 Signalling-route-set-test message
+
+**15.10.1** The format of the signalling-route-set-test message is shown in Figure 20.
+
+
+
+| | | | | | |
+|----|-------------|-----------------|-----------------|-------|-------------------------|
+| 00 | | DCBA | 0101 | | |
+| | Destination | Heading code H1 | Heading code H0 | Label | |
+| 2 | 14 | 4 | 4 | 32 | First bit transmitted → |
+
+T1159040-94/d029
+
+**Figure 20/Q.704 – Signalling-route-set-test message**
+
+**15.10.2** This message is made up of the following fields:
+
+- Label (32 bits): see 15.2
+- Heading code H0 (4 bits): see 15.3
+- Heading code H1 (4 bits): see 15.10.3
+- Destination (14 bits): see 15.7.4
+- Spare bits (2 bits) coded 00.
+
+**15.10.3** The heading code H1 contains signal codes as follows:
+
+| | | | | | |
+|-----|---|---|---|---|-------------------------------------------------------------------------------|
+| bit | D | C | B | A | |
+| | 0 | 0 | 0 | 1 | Signalling-route-set-test signal for prohibited destination |
+| | 0 | 0 | 1 | 0 | Signalling-route-set-test signal for restricted destination (national option) |
+
+### 15.11 Management inhibit message
+
+**15.11.1** The format of the management inhibit message is shown in Figure 20a.
+
+
+
+| | | | |
+|-----------------|-----------------|-------|-------------------------|
+| DCBA | 0110 | | |
+| Heading code H1 | Heading code H0 | Label | |
+| 4 | 4 | 32 | First bit transmitted → |
+
+T1159050-94/d030
+
+**Figure 20a/Q.704 – Management inhibit message**
+
+**15.11.2** The management inhibit message is made up of the following fields:
+
+- Label (32 bits): see 15.2.
+- Heading code H0 (4 bits): see 15.3.
+- Heading code H1 (4 bits): see 15.11.3.
+
+**15.11.3** The header code H1 contains signal codes as follows:
+
+| bits | D | C | B | A | |
+|------|---|---|---|---|-----------------------------------------|
+| | 0 | 0 | 0 | 1 | Link inhibit signal |
+| | 0 | 0 | 1 | 0 | Link uninhibit signal |
+| | 0 | 0 | 1 | 1 | Link inhibited acknowledgement signal |
+| | 0 | 1 | 0 | 0 | Link uninhibited acknowledgement signal |
+| | 0 | 1 | 0 | 1 | Link inhibit denied signal |
+| | 0 | 1 | 1 | 0 | Link force uninhibit signal |
+| | 0 | 1 | 1 | 1 | Link local inhibit test signal |
+| | 1 | 0 | 0 | 0 | Link remote inhibit test signal |
+
+### **15.12 Traffic restart allowed message**
+
+**15.12.1** The format of the traffic restart allowed message is shown in Figure 21.
+
+
+
+| | | | |
+|-----------------|-----------------|-------|--|
+| DCBA | 0111 | | |
+| Heading code H1 | Heading code H0 | Label | |
+| 4 | 4 | 32 | |
+
+First bit transmitted →
+T1159060-94/d031
+
+**Figure 21/Q.704 – Traffic restart allowed message**
+
+**15.12.2** The traffic restart allowed message is made up of the following fields:
+
+- Label (32 bits): see 15.2.
+- Heading code H0 (4 bits): see 15.3.
+- Heading code H1 (4 bits): see 15.12.3.
+
+**15.12.3** The heading code H1 contains one signal code as follows:
+
+| bits | D | C | B | A | |
+|------|---|---|---|---|--------------------------------|
+| | 0 | 0 | 0 | 1 | Traffic restart allowed signal |
+
+### **15.13 Signalling-data-link-connection-order message**
+
+**15.13.1** The format of the signalling-data-link-connection-order message is shown in Figure 22.
+
+
+
+| | | | | | |
+|------|-------------------------------|-----------------|-----------------|-------|-------------------------|
+| 0000 | | DCBA | 1000 | | First bit transmitted → |
+| / | Signalling data link identity | Heading code H1 | Heading code H0 | Label | |
+| | 4 | 12 | 4 | 4 | |
+
+T1159070-94/d032
+
+**Figure 22/Q.704 – Signalling-data-link-connection-order message**
+
+**15.13.2** The signalling-data-link-connection-order message is made up of the following fields:
+
+- Label (32 bits): see 15.2.
+- Heading code H0 (4 bits): see 15.3.
+- Heading code H1 (4 bits): see 15.13.3.
+- Signalling data link identity (12 bits): see 15.13.4.
+- Spare bits (4 bits) coded 0000.
+
+**15.13.3** The heading code H1 contains one signal code as follows:
+
+| | | | | | |
+|------|---|---|---|---|----------------------------------------------|
+| bits | D | C | B | A | |
+| | 0 | 0 | 0 | 1 | Signalling-data-link-connection-order signal |
+
+**15.13.4** The signalling data link identity field contains the Circuit Identification Code (CIC), or the Bearer Identification Code (BIC) in case of a 64 kbit/s channel used to carry submultiplex data streams, of the transmission link corresponding to the signalling data link.
+
+### **15.14 Signalling-data-link-connection-acknowledgement message**
+
+**15.14.1** The format of the signalling-data-link-connection-acknowledgement message is shown in Figure 22a.
+
+
+
+| | | | |
+|-----------------|-----------------|-------|-------------------------|
+| DCBA | 1000 | | First bit transmitted → |
+| Heading code H1 | Heading code H0 | Label | |
+| 4 | 4 | 32 | |
+
+T1159080-94/d033
+
+**Figure 22a/Q.704 – Signalling-data-link-connection-acknowledgement message**
+
+**15.14.2** The signalling-data-link-connection acknowledgement message is made up of the following fields:
+
+- Label (32 bits): see 15.2.
+- Heading code H0 (4 bits): see 15.3.
+- Heading code H1 (4 bits): see 15.14.3.
+
+15.14.3 The heading code H1 contains signal codes as follows:
+
+| bit | D | C | B | A | |
+|-----|---|---|---|---|----------------------------------|
+| | 0 | 0 | 1 | 0 | Connection-successful signal |
+| | 0 | 0 | 1 | 1 | Connection-not-successful signal |
+| | 0 | 1 | 0 | 0 | Connection-not-possible signal |
+
+### 15.15 Transfer-controlled message
+
+15.15.1 The format of the TFC message is shown in Figure 22b.
+
+
+
+| | | | | | |
+|----|-------------|-----------------|-----------------|-------|-------------------------|
+| 00 | | DCBA | 0011 | | |
+| | Destination | Heading code H1 | Heading code H0 | Label | |
+| 2 | 14 | 4 | 4 | 32 | First bit transmitted → |
+
+T1159090-94/d034
+
+Figure 22b/Q.704 – Transfer-controlled message
+
+15.15.2 The transfer-controlled message is made up of the following fields:
+
+- Label (32 bits): see 15.2.
+- Heading code H0 (4 bits): see 15.3.
+- Heading code H1 (4 bits): see 15.15.3.
+- Destination (14 bits): see 15.15.4.
+- Spare (2 bits): see 15.15.5.
+
+15.15.3 The heading code H1 contains one signal code as follows:
+
+| bit | D | C | B | A | |
+|-----|---|---|---|---|----------------------------|
+| | 0 | 0 | 1 | 0 | Transfer-controlled signal |
+
+15.15.4 The destination field carries the address of the destination to which the message refers.
+
+15.15.5 In national signalling networks using multiple congestion states, the spare bits in the transfer-controlled message are used to carry the congestion status associated with the destination.
+
+### 15.16 Signalling-route-set-congestion-test message (national option)
+
+15.16.1 The format of the signalling-route-set-congestion-test message is shown in Figure 22c.
+
+
+
+| | | | |
+|-----------------|-----------------|-------|-------------------------|
+| DCBA | 0011 | | |
+| Heading code H1 | Heading code H0 | Label | |
+| 4 | 4 | 32 | First bit transmitted → |
+
+T1159100-94/d035
+
+Figure 22c/Q.704 – Signalling-route-set-congestion-test message
+
+**15.16.2** The signalling-route-set-congestion test message is made up of the following fields:
+
+- Label (32 bits): see 15.2.
+- Heading code H0 (4 bits): see 15.3.
+- Heading code H1 (4 bits): see 15.16.3.
+
+**15.16.3** The heading code H1 contains one signal code as follows:
+
+| | | | | | |
+|-----|---|---|---|---|---------------------------------------------|
+| bit | D | C | B | A | |
+| | 0 | 0 | 0 | 1 | Signalling-route-set-congestion-test signal |
+
+### **15.17 User Part unavailable message**
+
+**15.17.1** The format of the user part unavailable message is shown in Figure 22d.
+
+
+
+| | | | | | | |
+|----------------------|--------------|----|-------------|-----------------|-----------------|-------|
+| DCBA | DCBA | 00 | | DCBA | 1010 | |
+| Unavailability cause | User part ID | | Destination | Heading code H1 | Heading code H0 | Label |
+| 4 | 4 | 2 | 14 | 4 | 4 | 32 |
+
+First bit transmitted →
+T1159110-94/d036
+
+**Figure 22d/Q.704 – User part unavailable message**
+
+**15.17.2** The user part unavailable message is made up of the following fields:
+
+- Label (32 bits): see 15.2.
+- Heading code H0 (4 bits): see 15.3.
+- Heading code H1 (4 bits): see 15.17.3.
+- Destination (14 bits): see 15.15.4.
+- Spare (2 bits): coded 00.
+- User part identity (4 bits): see 15.17.4.
+- Unavailability cause (4 bits): see 15.17.5.
+
+**15.17.3** The heading code H1 contains signal codes as follows:
+
+| | | | | | |
+|-----|---|---|---|---|-----------------------|
+| bit | D | C | B | A | |
+| | 0 | 0 | 0 | 1 | User part unavailable |
+
+**15.17.4** The User Part identity is coded as follows:
+
+| | | | | | |
+|-----|---|---|---|---|-----------------------|
+| bit | D | C | B | A | |
+| | 0 | 0 | 0 | 0 | Spare |
+| | 0 | 0 | 0 | 1 | Spare |
+| | 0 | 0 | 1 | 0 | Spare |
+| | 0 | 0 | 1 | 1 | SCCP |
+| | 0 | 1 | 0 | 0 | TUP |
+| | 0 | 1 | 0 | 1 | ISUP |
+| | 0 | 1 | 1 | 0 | DUP |
+| | 0 | 1 | 1 | 1 | Spare |
+| | 1 | 0 | 0 | 0 | MTP Testing User Part |
+
+| | | | | |
+|---|---|----|---|--------------------------|
+| 1 | 0 | 0 | 1 | Broadband ISDN User Part |
+| 1 | 0 | 1 | 0 | Satellite ISDN User Part |
+| 1 | 0 | 1 | 1 | ) |
+| | | to | | ) Spare |
+| 1 | 1 | 1 | 1 | ) |
+
+**15.17.5** The unavailability cause is coded as follows:
+
+| bit | D | C | B | A | |
+|-----|---|---|----|---|--------------------------|
+| | 0 | 0 | 0 | 0 | unknown |
+| | 0 | 0 | 0 | 1 | unequipped remote user |
+| | 0 | 0 | 1 | 0 | inaccessible remote user |
+| | 0 | 0 | 1 | 1 | ) |
+| | | | to | | ) Spare |
+| | 1 | 1 | 1 | 1 | ) |
+
+## 16 State transition diagrams, abbreviations and timers
+
+### 16.1 General
+
+This clause contains the description of the signalling network functions described in clauses 2 to 13 in the form of state transition diagrams according to the CCITT Specification and Description Language (SDL).
+
+A set of diagrams is provided for each of the following major functions:
+
+- Signalling Message Handling (SMH), described in clause 2;
+- Signalling Traffic Management (STM), described in clauses 4 to 11;
+- Signalling Route Management (SRM), described in clause 13;
+- Signalling Link Management (SLM), described in clause 12.
+
+**16.1.1** For each major function a figure illustrates a subdivision into functional specification blocks, showing their functional interactions as well as the interactions with the other major functions. In each case this is followed by figures showing state transition diagrams for each of the functional specification blocks.
+
+The detailed functional breakdown shown in the following diagrams is intended to illustrate a reference model and to assist interpretation of the text in the earlier subclauses. The state transition diagrams are intended to show precisely the behaviour of the signalling system under normal and abnormal conditions as viewed from a remote location. It must be emphasized that the functional partitioning shown in the following diagrams is used only to facilitate understanding of the system behaviour and is not intended to specify the functional partitioning to be adopted in a practical implementation of the signalling system.
+
+### 16.2 Drafting conventions
+
+**16.2.1** Each major function is designated by its acronym (e.g. SMH = signalling message handling).
+
+**16.2.2** Each functional block is designated by an acronym which identifies it and also identifies the major function to which it belongs (e.g. HMRT = signalling message handling – message routing; TLAC = signalling traffic management – link availability control).
+
+**16.2.3** External inputs and outputs are used for interactions between different functional blocks. Included within each input and output symbol in the state transition diagrams are acronyms which identify the functions which are the source and destination of the message, e.g.:
+
+L2 → L3 indicates that the message is sent between functional levels:
+
+from: functional level 2;
+to: functional level 3.
+
+RTPC → TSRC indicates that the message is sent within a functional level (3 in this case):
+
+from: signalling route management-transfer prohibited control;
+to: signalling traffic management-signalling routing control.
+
+**16.2.4** Internal inputs and outputs are only used to indicate control of time-outs.
+
+#### **16.2.5 Notations for national operations**
+
+National options are included in the main body of the state transition diagrams (STDs) with dotted or dashed lines; if their use should exclude or modify some of the international logic, the relevant sections are marked “t” and a note is added to the figure. Also, the options are marked as follows:
+
+Transfer restricted – dashed lines.
+
+Multiple congestion states – dotted lines (with the hatched symbols removed where shown).
+
+### **16.3 Signalling message handling**
+
+Figure 23 shows a subdivision of the signalling message handling (SMH) function into smaller functional specification blocks and also shows the functional interactions between them. Each of these functional specification blocks is described in detail in a state transition diagram as follows:
+
+- a) message discrimination (HMDC) is shown in Figure 24;
+- b) message distribution (HMDT) is shown in Figure 25;
+- c) message routing (HMRT) is shown in Figure 26;
+- d) handling of messages under signalling link congestion is shown in Figure 26a.
+
+### **16.4 Signalling traffic management**
+
+Figure 27 shows a subdivision of the signalling traffic management (STM) function into smaller functional specification blocks and also shows functional interactions between them. Each of these functional specification blocks is described in detail in a state transition diagram as follows:
+
+- a) link availability control (TLAC) is shown in Figure 28;
+- b) signalling routing control (TSRC) is shown in Figure 29;
+- c) changeover control (TCOC) is shown in Figure 30;
+- d) changeback control (TCBC) is shown in Figure 31;
+- e) forced rerouting control (TFRC) is shown in Figure 32;
+- f) controlled rerouting control (TCRC) is shown in Figure 33;
+- g) signalling traffic flow control (TSFC) is shown in Figure 34a;
+- h) signalling route set congestion control (TRCC) is shown in Figure 29a;
+- i) signalling point restart control (TPRC) is shown in Figure 34b.
+
+### 16.5 Signalling link management
+
+Figure 35 shows a subdivision of the signalling link management function (SLM) into smaller functional specification blocks and also shows functional interactions between them. Each of these functional specification blocks is described in detail in a state transition diagram as follows:
+
+- a) link set control (LLSC) is shown in Figure 36;
+- b) signalling link activity control (LSAC) is shown in Figure 37;
+- c) signalling link activation (LSLA) is shown in Figure 38;
+- d) signalling link restoration (LSLR) is shown in Figure 39;
+- e) signalling link deactivation (LSLD) is shown in Figure 40;
+- f) signalling terminal allocation (LSTA) is shown in Figure 41;
+- g) signalling data link allocation (LSDA) is shown in Figure 42.
+
+### 16.6 Signalling route management
+
+Figure 43 shows a subdivision of the signalling route management (SRM) function into smaller functional specification blocks and also shows functional interactions between them. Each of these functional specification blocks is described in detail in a state transition diagram as follows:
+
+- a) transfer prohibited control (RTPC) is shown in Figure 44;
+- b) transfer allowed control (RTAC) is shown in Figure 45;
+- c) transfer restricted control (RTRC) is shown in Figure 46c;
+- d) transfer controlled control (RTCC) is shown in Figure 46a;
+- e) signalling route set test control (RSRT) is shown in Figure 46;
+- f) signalling-route-set-congestion-test control (RCAT) is shown in Figure 46b.
+
+### 16.7 Abbreviations used in Figures 23 onwards
+
+| | |
+|------|--------------------------------------------------------------------------------|
+| BSNT | Backward sequence number of next signal unit to be transmitted |
+| DPC | Destination point code |
+| FSNC | Forward sequence number of last message signal unit accepted by remote level 2 |
+| HMCG | Signalling link congestion |
+| HMDC | Message discrimination |
+| HMDT | Message distribution |
+| HMRT | Message routing |
+| L1 | Level 1 |
+| L2 | Level 2 |
+| L3 | Level 3 |
+| L4 | Level 4 |
+| LLSC | Link set control |
+| LSAC | Signalling link activity control |
+| LSDA | Signalling data link allocation |
+| LSLA | Signalling link activation |
+
+| | |
+|------|----------------------------------------------|
+| LSLD | Signalling link deactivation |
+| LSLR | Signalling link restoration |
+| LSTA | Signalling terminal allocation |
+| MGMT | Management system |
+| RCAT | Signalling-route-set-congestion-test control |
+| RSRT | Signalling route set test control |
+| RTAC | Transfer allowed control |
+| RTCC | Transfer controlled control |
+| RTPC | Transfer prohibited control |
+| RTRC | Transfer restricted control |
+| SLM | Signalling link management |
+| SLS | Signalling link selection |
+| SLTC | Signalling link test control |
+| SMH | Signalling message handling |
+| SRM | Signalling route management |
+| STM | Signalling traffic management |
+| TCBC | Changeback control |
+| TCOC | Changeover control |
+| TCRC | Controlled rerouting control |
+| TFRC | Forced rerouting control |
+| TLAC | Link availability control |
+| TPRC | Signalling point restart control |
+| TRCC | Signalling route set congestion control |
+| TSFC | Signalling traffic flow control |
+| TSRC | Signalling routing control |
+
+### 16.8 Timers and timer values
+
+The following timers have been defined. The ranges are given below. The values, in brackets, are the minimum values for use when routes with long propagation delays are used (e.g. routes including satellite sections).
+
+| | |
+|----|-------------------------------------------------------------------------------------------------|
+| T1 | Delay to avoid message mis-sequencing on changeover.
500 (800) to 1200 ms. |
+| T2 | Waiting for changeover acknowledgement.
700 (1400) to 2000 ms. |
+| T3 | Time controlled diversion-delay to avoid mis-sequencing on changeback.
500 (800) to 1200 ms. |
+| T4 | Waiting for changeback acknowledgement (first attempt).
500 (800) to 1200 ms. |
+
+- T5 Waiting for changeback acknowledgement (second attempt).
+500 (800) to 1200 ms.
+- T6 Delay to avoid message mis-sequencing on controlled rerouting.
+500 (800) to 1200 ms.
+- T7 Waiting for signalling data link connection acknowledgement.
+1 to 2 seconds.
+- T8 Transfer prohibited inhibition timer (transient solution).
+800 to 1200 ms.
+- T9 Not used.
+- T10 Waiting to repeat signalling route set test message.
+30 to 60 seconds.
+The maximum value may be extended at the discretion of the management function in certain situations, e.g. many signalling points being unavailable or signalling point of known long term unavailability.
+- T11 Transfer restricted timer. (This is one way of implementing the function described in 13.4 and mainly intended to simplify STPs.)
+30 to 90 seconds.
+- T12 Waiting for uninhibit acknowledgement.
+800 to 1500 ms.
+- T13 Waiting for force uninhibit.
+800 to 1500 ms.
+- T14 Waiting for inhibition acknowledgement.
+2 to 3 seconds.
+- T15 Waiting to start signalling route set congestion test.
+2 to 3 seconds.
+- T16 Waiting for route set congestion status update.
+1.4 to 2 seconds.
+- T17 Delay to avoid oscillation of initial alignment failure and link restart.
+800 to 1500 ms.
+- T18 Timer8 within a signalling point whose MTP restarts for supervising link and link set activation as well as the receipt of routing information.
+The value is implementation and network dependent.
+Criteria to choose T18 are given in 9.2.
+
+---
+
+8 The values of the MTP restart timers (T18 to T21) defined above are for use during normal operation. It might be advantageous for the network operator to define an alternative value for each timer, for use in potential network failures. Such an emergency might be recognised by an abnormally large number of outages, and it would be at the discretion of the operator to use the emergency set of timer values within the network.
+
+Thus, the selection of the appropriate timer set is within the responsibility of the network Administration.
+
+- T19 Supervision timer during MTP restart to avoid possible ping-pong of TFP, TFR1 and TRA messages.
+67 to 69 seconds
+- T20 Overall MTP restart timer at the signalling point whose MTP restarts.
+59 to 61 seconds.
+- T21 Overall MTP restart timer at a signalling point adjacent to one whose MTP restarts.
+63 to 65 seconds.
+- T22 Local inhibit test timer.
+3 to 6 minutes (provisional value).
+- T23 Remote inhibit test timer.
+3 to 6 minutes (provisional value).
+- T24 Stabilising timer after removal of local processor outage, used in LPO latching to RPO (national option).
+500 ms (provisional value).
+
+
+
+The diagram illustrates the functional block interactions for Level 3 Signalling message handling (SMH). It shows the flow of messages between various management and control blocks and external entities.
+
+**External Entities and Connections:**
+
+- To level 4 (L4):** MTP Transfer (Transfer prohibited, Transfer restricted, Transfer allowed, Signalling route set test, Transfer controlled, Signalling route set congestion test, User part unavailable).
+- To signalling route management (SRM):** Signalling route set test, Transfer controlled, Signalling route set congestion test, User part unavailable.
+- To signalling link management (SLM):** Signalling data link connection order, Connection successful, Connection not successful, Connection not possible.
+- To signalling traffic management (STM):** Inhibit/uninhibit messages, Changeover order, Changeover acknowledgement, Emergency changeover order, Emergency changeover acknowledgement, Changeback declaration, Changeback acknowledgement, Traffic restart allowed.
+- To signalling link test control (SLTC):** Signalling link test message, Signalling link test acknowledgement message.
+- From level 4 (L4):** MTP Transfer (Transfer prohibited, Transfer restricted, Transfer allowed, Signalling route set test, Transfer controlled, Signalling route set congestion test).
+- From signalling route management (SRM):** Signalling route set test, Transfer controlled, Signalling route set congestion test.
+- From signalling link management (SLM):** Signalling data link connection order, Connection successful, Connection not successful, Connection not possible.
+- From signalling traffic management (STM):** Inhibit/uninhibit messages, Changeover order, Changeover acknowledgement, Emergency changeover order, Emergency changeover acknowledgement, Changeback declaration, Changeback acknowledgement, Traffic restart allowed.
+- From signalling link test control (SLTC):** Signalling link test message, Signalling link test acknowledgement message.
+- From level 2 (L2):** Received message.
+
+**Internal Functional Blocks:**
+
+- Message distribution (HMDT) Figure 25:** Receives 'Message for distribution' from HMDT and sends it to 'User part unavailable' and 'Message routing (HMRT) Figure 26'.
+- Message discrimination (HMDC) Figure 24:** Receives 'Received message' from L2 and sends it to 'Message for distribution' and 'Message for routing'.
+- User part unavailable:** Receives messages from HMDT and HMRT, and sends 'Message for routing' to HMRT.
+- Message routing (HMRT) Figure 26:** Receives messages from HMDT, HMDC, and 'User part unavailable'. It sends 'Message' to 'MCS' and 'Update routing tables'. It also receives 'Message received for inaccessible SP' from SRM and 'Message received for an unknown SP' from MGMT.
+- MCS (Message Control System):** Contains 'Signalling link congestion (HMCG) Figure 26a'. It sends 'Message for transmission' to L2 and 'Send transfer controlled message' to SRM.
+
+**Interactions:**
+
+- External entities send messages to the internal blocks (HMDT, HMDC, HMRT).
+- Internal blocks send messages to external entities (HMRT to SRM, STM, MGMT; MCS to L2, SRM).
+- There are feedback loops between HMRT and external entities (SRM, STM, MGMT).
+
+Functional block interactions diagram for Level 3 Signalling message handling (SMH).
+
+T1159120-94/d037
+
+Figure 23/Q.704 – Level 3 – Signalling message handling (SMH); functional block interactions
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> RM[Received message
+L2, L3]
+ RM --> DLS[Determine label structure]
+ DLS -.-> FNI[From network indicator]
+ DLS --> DTS{Destined to this SP?}
+ DTS -- No --> RB[Restart begins
+TPRC_HMDC]
+ DTS -- Yes --> MFD[Message for distribution
+HMDC_HMDT]
+ MFD --> OSR{Own SP restart?}
+ OSR -- Yes --> DM[Discard message]
+ OSR -- No --> MFRT[Message for routing
+HMDC_HMRT]
+ RB --> MOSR[Mark own SP restart]
+ MOSR --> RE[Restart ends
+TPRC_HMDC]
+ RE --> COSR[Cancel own SP restart]
+ COSR --> Idle2([Idle])
+ DM --> Idle2
+ MFRT --> Idle2
+ T1142560-92/d038
+
+```
+
+Flowchart for Signalling message handling; message discrimination (HMDC). The process starts at an 'Idle' state, proceeds to 'Received message' (L2, L3), then 'Determine label structure' (with a 'From network indicator' input). A decision 'Destined to this SP?' follows. If 'No', it goes to 'Restart begins' (TPRC\_HMDC). If 'Yes', it goes to 'Message for distribution' (HMDC\_HMDT). From 'Message for distribution', a decision 'Own SP restart?' is made. If 'Yes', it goes to 'Discard message'. If 'No', it goes to 'Message for routing' (HMDC\_HMRT). Both 'Discard message' and 'Message for routing' lead to a final 'Idle' state. There is also a 'Restart ends' (TPRC\_HMDC) state leading to 'Cancel own SP restart', which then leads to the final 'Idle' state. A reference code 'T1142560-92/d038' is present.
+
+Figure 24/Q.704 – Signalling message handling; message discrimination (HMDC)
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> HMDC[Message for distribution
+HMDC → HMDT]
+ Idle1 --> TPRC[Restart
+begins
+TPRC → HMDT]
+ TPRC --> OwnSP([Own SP
+restart])
+ HMDC --> Service{Service
+indicator?}
+ Service --> SNM[Signalling network management]
+ Service --> OwnSP
+ SNM --> Type{Message
+type?}
+ Type --> SRM[Signalling
+route management
+message
+HMDT → SRM]
+ Type --> SLM[Signalling
+link management
+message
+HMDT → SLM]
+ Type --> STM[Signalling
+traffic management
+message
+HMDT → STM]
+ SRM --> Idle2([Idle])
+ SLM --> Idle2
+ STM --> Idle2
+
+```
+
+T1142570-92/d039
+
+Signalling route management message may be:
+
+- transfer prohibited
+- transfer restricted
+- signalling route set test
+- transfer allowed
+- transfer controlled
+- signalling route set congestion test
+- user part unavailable
+
+Signalling link management message may be:
+
+- signalling data link connection order
+- connection successful
+- connection not successful
+- connection not possible
+
+Signalling traffic management message may be:
+
+- changeover acknowledgement
+- emergency changeover acknowledgement
+- changeback declaration
+- changeback acknowledgement
+- changeover order
+- emergency changeover order
+- inhibit signalling link
+- uninhibit signalling link
+- inhibit acknowledgement
+- uninhibit acknowledgement
+- inhibit denied
+- force uninhibit signalling link
+- traffic restart allowed
+
+Flowchart of Signalling message handling; message distribution (HMDT).
+
+**Figure 25/Q.704 (sheet 1 of 3) – Signalling message handling;
+message distribution (HMDT)**
+
+
+
+1
+
+```
+
+graph TD
+ Start((1)) -- Invalid --> Discard1[Discard message]
+ Discard1 --> Idle1([Idle])
+ Start -- "Signalling network testing and maintenance" --> SLTC{{"Signalling link test control message
+HMDT->SLTC"}}
+ SLTC --> Idle1
+ Start -- "Other User Parts not including MTP Testing User Part" --> UserPartAvail{User Part Available?}
+ UserPartAvail -- Yes --> L4{{"MTP Transfer indication
+HMDT->L4"}}
+ L4 --> Idle2([Idle])
+ UserPartAvail -- No --> Discard2[Discard Message]
+ Discard2 --> HMRT{{"User Part Unavailable
+HMDT->HMRT"}}
+ HMRT --> Idle2
+
+```
+
+1
+
+Invalid
+
+Discard message
+
+Idle
+
+Signalling network testing and maintenance
+
+Signalling link test control message
+HMDT->SLTC
+
+Signalling link test control message may be:
+ – signalling link test message
+ – signalling link test message acknowledgement
+
+Other User Parts not including MTP Testing User Part
+
+Yes
+
+No
+
+User Part Available?
+
+MTP Transfer indication
+HMDT->L4
+
+Discard Message
+
+User Part Unavailable
+HMDT->HMRT
+
+Idle
+
+T1159130-94/d040
+
+Flowchart for Signalling message handling; message distribution (HMDT). It shows two main paths: one for 'Invalid' messages leading to 'Discard message' and 'Idle', and another for 'Signalling network testing and maintenance' messages leading to 'HMDT->SLTC' and 'Idle'. A third path for 'Other User Parts not including MTP Testing User Part' leads to a decision 'User Part Available?'. If 'Yes', it goes to 'HMDT->L4' and 'Idle'. If 'No', it goes to 'Discard Message', 'HMDT->HMRT', and 'Idle'.
+
+**Figure 25/Q.704 (sheet 2 of 3) – Signalling message handling;
+message distribution (HMDT)**
+
+
+
+```
+
+graph TD
+ A([Own SP restart]) --> B[/Message for distribution HMDT_HMDT/]
+ A --> C[/Restart ends TPRC_HMDT/]
+ C --> D([Idle])
+ B --> E{Service indicator?}
+ E -- Signalling network maintenance --> F[/Signalling link test control message HMDT_S LTC/]
+ E -- Signalling network management --> G{Message type?}
+ E -- Other User Parts or invalid --> H[Other management message]
+ G -- "Traffic restart allowed message" --> I[/Signalling traffic management message HMDT_S TM/]
+ G -- "TFP, TFR and TFA message" --> J[/Signalling route management message HMDT_S RM/]
+ G --> K[Discard message]
+ F --> L([Own SP restart])
+ I --> L
+ J --> L
+ K --> L
+ T1142580-92/d041
+
+```
+
+Flowchart for Signalling message handling; message distribution (HMDT). The process starts with 'Own SP restart', leading to 'Message for distribution HMDT\_HMDT' and 'Restart ends TPRC\_HMDT'. 'Restart ends' leads to 'Idle'. 'Message for distribution' leads to 'Service indicator?'. From 'Service indicator?', three paths emerge: 'Signalling network maintenance' leading to 'Signalling link test control message HMDT\_S LTC', 'Signalling network management' leading to 'Message type?', and 'Other User Parts or invalid' leading to 'Other management message'. 'Message type?' leads to 'Traffic restart allowed message' (HMDT\_S TM), 'TFP, TFR and TFA message' (HMDT\_S RM), and 'Discard message'. All three lead to 'Own SP restart'. A reference code T1142580-92/d041 is present.
+
+NOTE – For meanings of abbreviated message names, see Table 1.
+
+**Figure 25/Q.704 (sheet 3 of 3) – Signalling message handling; message distribution (HMDT)**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> MsgRouting[Message for routing HMDC → HMRT]
+ Idle1 --> MTP[MTP Transfer request L4 → L3]
+ Idle1 --> AdjRestart[Adjacent SP restart TSRC → HMRT]
+
+ MsgRouting --> DPCExist{Does routing for that DPC exist?}
+ MTP --> DPCExist
+
+ DPCExist -- No --> DPCRestart{DPC SP restart?}
+ DPCExist -- Yes --> DestCongested{Destination congested?}
+
+ DPCRestart -- Yes --> DPCVia[DPC to or via restarting adjacent SP]
+ DPCRestart -- No --> Conn1((1))
+
+ DPCVia -.-> MarkRestart[Mark adjacent SP restarting]
+ MarkRestart --> Idle2([Idle])
+
+ DestCongested -- Yes --> MsgCongested[Message for congested destination HMRT → TSEC]
+ DestCongested -- No --> LoadSharing{Load sharing between link sets?}
+
+ MsgCongested --> Conn1
+
+ LoadSharing -- Yes --> SelectLinkSet[Select link set on the basis of SLS]
+ LoadSharing -- No --> SelectLink[Select link in link set on the basis of SLS]
+
+ SelectLinkSet --> SelectLink
+
+ SelectLink --> MsgHMCG[Message HMRT → HMCG]
+ MsgHMCG --> MsgTrans[Message for transmission I3-I2]
+ MsgTrans --> Idle3([Idle])
+ MsgTrans -.-> ToLink[To selected link]
+
+ Conn1 --> Originate{Did message originate at this 'SP'?}
+ Originate -- Yes --> Discard[Discard message]
+ Originate -- No --> DPCUnknown[DPC unknown]
+
+ DPCUnknown --> MsgUnknown[Message received for unknown SP HMRT → MGMT]
+ MsgUnknown --> MsgInaccessible[Message received for inaccessible SP HMRT → RTPC]
+ MsgInaccessible --> Discard
+ Discard --> Idle3
+
+ FromRerouting[From changeover, changeback, forced or controlled rerouting] --> UpdateTables[Update routing tables STM → HMRT]
+ UpdateTables --> UpdateAction[Update routing tables]
+ UpdateAction --> Idle2
+
+ subgraph Connectors
+ Conn2((2))
+ Conn3((3))
+ Conn4((4))
+ Conn5((5))
+ Conn6((6))
+ end
+
+```
+
+The flowchart illustrates the message routing (HMRT) process. It begins with an 'Idle' state, leading to several possible inputs: 'Message for routing HMDC → HMRT', 'MTP Transfer request L4 → L3', or 'Adjacent SP restart TSRC → HMRT'.
+
+A primary decision point is 'Does routing for that DPC exist?'. If 'No', it checks 'DPC SP restart?'. If 'Yes' to restart, it processes 'DPC to or via restarting adjacent SP' and marks the SP as restarting. If 'No' to restart, it proceeds to check if the message originated at this SP.
+
+If routing exists, it checks 'Destination congested?'. If 'Yes', a message is sent to TSEC. If 'No', it evaluates 'Load sharing between link sets?'. Depending on this, it selects a link set and/or a link based on SLS, eventually leading to 'Message HMRT → HMCG' and 'Message for transmission I3-I2' before returning to 'Idle'.
+
+Messages that cannot be routed are checked to see if they originated at the current SP. If so, they are discarded. If not, they are handled as messages for unknown or inaccessible SPs before being discarded.
+
+Additionally, routing tables are updated (STM → HMRT) following changeover, changeback, or rerouting events.
+
+Flowchart for Signalling message handling; message routing (HMRT).
+
+NOTE – Dotted symbols apply only to multiple congestion states option. Delete hatched symbols when using option.
+
+**Figure 26/Q.704 (sheet 1 of 5) – Signalling message handling; message routing (HMRT)**
+
+
+
+A signal is accompanied by routing data obtained at the source of the signal from TSRC
+
+```
+
+graph TD
+ C2_1((2
+ 1)) --> SLM[Signalling link management message
+ SLM → HMRT]
+ SLM -.-> DPC_Adj[DPC to or via restarting adjacent SP]
+ SLM --> DPC_SR{DPC
+ SP restart?}
+ DPC_SR -- Yes --> C4_1((4
+ 1))
+ DPC_SR -- No --> DPC_E1{Does routing for that DPC exist?}
+ DPC_E1 -- No --> C1_1((1
+ 1))
+ DPC_E1 -- Yes --> SEL_A1[Select an available link] --> C3_1((3
+ 1))
+
+ Idle1([Idle]) --> MTP[MTP Testing User Part message
+ L4 → L3
+ (Note)] --> C7_3((7
+ 3))
+
+ RE[Restart ends
+ TPRC → HMRT] --> CMarks[Cancel marks] --> Idle2([Idle])
+
+ C8_3((8
+ 3)) --> MIM{Management inhibit message?}
+ MIM -- Yes --> FU{Forced uninhibit?}
+ FU -- Yes --> C7_3
+ FU -- No --> UUA{Uninhibit or uninhibit ack?}
+ UUA -- No --> SEL_A2[Select an available link] --> C3_1
+ UUA -- Yes --> DPC_E2{Does routing for DPC exist?}
+ DPC_E2 -- Yes --> SEL_A3[Select an available link] --> C3_1
+ DPC_E2 -- No --> SEL_SLC[Select link coded in SLC field of message] --> C3_1
+
+ MIM -- No --> DPC_E3{Does routing for that DPC exist?}
+ DPC_E3 -- No --> C1_2((1
+ 1))
+ DPC_E3 -- Yes --> CBM{Changeback message?}
+ CBM -- No --> UUA
+ CBM -- Yes --> CBD{Changeback declarations?}
+ CBD -- No --> SEL_A4[Select an available link] --> C3_1
+ CBD -- Yes --> SEL_ALT[Select alternative link on the basis of SLC and the changeback code] --> C3_1
+
+ subgraph Footer
+ T1142600-92/d043
+ end
+
+```
+
+Signalling link management message may be:
+– signalling data link connection order
+– connection successful
+– connection not successful
+– Connection not possible
+
+Flowchart for Signalling message handling; message routing (HMRT).
+
+NOTE – Some special routing for MTP Testing User Part may be needed depending on the functions and requirements of such a User Part.
+
+**Figure 26/Q.704 (sheet 2 of 5) – Signalling message handling; message routing (HMRT)**
+
+
+
+A signal is accompanied by routing data obtained at the source of the signal from TSRC
+
+```
+
+graph TD
+ Idle1([Idle]) --> SRM[Signalling route management message SRM_HMRT]
+ Idle1 --> TPRC[Restart begins TPRC_HMRT]
+ Idle1 --> STM[Signalling traffic management message STM_HMRT]
+ Idle1 --> SLTC[Signalling link test control message SLTC_HMRT]
+
+ TPRC --> OwnSP([Own SP restart])
+
+ SRM --> DPCSRM{DPC SP restart?}
+ DPCSRM -- No --> 5((5))
+ DPCSRM -- Yes --> DPCExist{Does routing for that DPC exist?}
+ DPCExist -- No --> 1((1))
+ DPCExist -- Yes --> MessageTypeSRM{Message type?}
+ MessageTypeSRM -- "TFA, TFR and TFP message" --> 5
+ MessageTypeSRM -- "Other SRM message" --> Discard[Discard message]
+ Discard --> Idle2([Idle])
+
+ STM --> DPCSTM{DPC SP restart?}
+ DPCSTM -- No --> 8((8))
+ DPCSTM -- Yes --> MessageTypeSTM{Message type?}
+ MessageTypeSTM -- "Other STM message" --> Discard
+ MessageTypeSTM -- "Traffic restart allowed message" --> SelectLinkSTM[Select a link in the direct linkset to DPC]
+ SelectLinkSTM --> 3((3))
+
+ SLTC --> SelectLinkSLTC[Select link coded in SLC field of message]
+ SelectLinkSLTC --> 3
+
+```
+
+**Signalling route management message may be:**
+
+- transfer prohibited
+- transfer restricted
+- signalling route set test
+- transfer allowed
+- transfer controlled
+- signalling route set congestion test
+- user part unavailable.
+
+**Signalling traffic management message may be:**
+
+- changeover ack
+- emergency changeover ack
+- changeback declaration
+- changeback ack
+- changeover order
+- emergency changeover order
+- inhibit signalling link
+- uninhibit signalling link
+- inhibit ack
+- uninhibit ack
+- inhibit denied
+- force uninhibit signalling link
+- traffic restart allowed
+
+**Signalling link test control message may be:**
+
+- signalling link test message
+- signalling link test message ack
+
+T1142610-92/d044
+
+Flowchart for Signalling message handling; message routing (HMRT). The process starts at 'Idle' and branches into four message types: SRM\_HMRT, TPRC\_HMRT, STM\_HMRT, and SLTC\_HMRT. Each branch has decision diamonds for 'DPC SP restart?' and 'Message type?' leading to various outcomes like 'Own SP restart', 'Discard message', or 'Select a link'.
+
+NOTE – For meanings of abbreviated message names, see Table 1.
+
+**Figure 26/Q.704 (sheet 3 of 5) – Signalling message handling; message routing (HMRT)**
+
+
+
+```
+
+graph TD
+ Start([Own SP restart]) --> MTP_Testing[/MTP Testing User Part message L4 → L3/]
+ Start --> Msg_Routing[/Message for routing HMDC → HMRT/]
+ Start --> MTP_Transfer[/MTP Transfer request L4 → L3/]
+ Start --> SLM_Msg[/Signalling link management message SLM → HMRT/]
+ Start --> Conn9_1((9))
+
+ MTP_Testing --> Discard1[Discard message]
+ Msg_Routing --> Discard1
+ MTP_Transfer --> Discard1
+ Discard1 --> Restart1([Own SP restart])
+
+ SLM_Msg --> Conn9_1
+
+ Conn9_2((9)) --> SRM_Msg[/Signalling route management message SRM → HMRT/]
+ Conn9_2 --> SLTC_Msg[/Signalling link test control message SLTC → HMRT/]
+ Conn9_2 --> STM_Msg[/Signalling traffic management message STM → HMRT/]
+ Conn9_2 --> Restart_Ends[/Restart ends TPRC → HMRT/]
+
+ SRM_Msg --> SRM_Type{Message type?}
+ SRM_Type --> Other_SRM[Other SRM message]
+ SRM_Type --> TFP_TFA[TFP, TFA and TFR message]
+
+ SLTC_Msg --> Select_Link[Select link coded in SLC field of message]
+ Select_Link --> Conn10((10))
+
+ STM_Msg --> STM_Type{Message type?}
+ STM_Type --> Traffic_Restart[Traffic restart allowed message]
+ STM_Type --> Other_STM[Other STM message]
+
+ Restart_Ends --> Cancel_Marks[Cancel marks]
+ Cancel_Marks --> Idle([Idle])
+
+ Conn10 --> TFP_TFA
+ TFP_TFA --> Conn11((11))
+ Traffic_Restart --> Conn11
+ Other_SRM --> Conn11
+
+ Conn11 --> Discard2[Discard message]
+ Other_STM --> Discard2
+ Discard2 --> Restart2([Own SP restart])
+
+```
+
+Signalling link management message may be:
+
+- signalling data link connection order
+- connection successful
+- connection not successful
+- connection not possible
+
+T1142620-92/d45
+
+Flowchart for Signalling message handling; message routing (HMRT).
+
+NOTE – For meanings of abbreviated message names, see Table 1.
+
+**Figure 26/Q.704 (sheet 4 of 5) – Signalling message handling; message routing (HMRT)**
+
+
+
+```
+
+graph TD
+ 11((11 5)) --> D1{Does routing for that DPC exist?}
+ D1 -- No --> Discard[Discard message]
+ Discard --> SP1([Own SP restart])
+ D1 -- Yes --> D2{Destination congested?}
+ D2 -- Yes --> H1{{Message for congested destination
+HMRT → TSFC}}
+ H1 --> SP2([Own SP restart])
+ D2 -- No --> S1[Select link in direct linkset on the basis of SLS]
+ S1 --> 10((10 4))
+ 10 --> H2{{Message
+HMRT → HMCG}}
+ H2 --> H3{{Message for transmission
+L3-L2}}
+ H3 --> Link[To selected link]
+ H3 --> SP3([Own SP restart])
+ T1142630-92/d046
+
+```
+
+Flowchart for signalling message handling and message routing (HMRT). The process starts at connector 11 (5), checks if routing for that DPC exists. If No, it discards the message and performs an Own SP restart. If Yes, it checks if the destination is congested. If Yes, it sends a message for congested destination (HMRT → TSFC) and performs an Own SP restart. If No, it selects a link in the direct linkset based on SLS, then passes through connector 10 (4). The message then goes through HMRT → HMCG (dotted symbol) and then to the selected link via L3-L2 processing, resulting in an Own SP restart. Reference T1142630-92/d046 is noted at the bottom.
+
+NOTE – Dotted symbols apply only to the multiple congestion states option. Delete hatched symbols when using option.
+
+**Figure 26/Q.704 (sheet 5 of 5) – Signalling message handling; message routing (HMRT)**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> Message[/Message
+HMRT→HMCG/]
+ Message --> P_cong{P < congestion status?}
+ P_cong -- Yes --> Send[Send transfer controlled message
+HMCG→RTCC]
+ P_cong -- No --> ToLink[Message for transmission
+L3→L2]
+ Send --> P_disc{P < discard status?}
+ P_disc -- Yes --> Discard[Discard message]
+ P_disc -- No --> ToLink
+ Discard --> Idle2([Idle])
+ ToLink --> ToLinkText[To selected link]
+ ToLinkText -.-> Idle2
+
+```
+
+P is message priority, the congestion status is updated by an implementation dependent procedure in conformance to 3.6
+
+The discard status is updated by an implementation dependent procedure in conformance to 3.6
+
+T1188800-97
+
+Flowchart for signalling message handling (HMCG) showing the process from Idle state to Message (HMRT→HMCG), then through congestion and discard status checks, leading to either discarding the message or sending it for transmission (L3→L2) to a selected link, returning to Idle.
+
+NOTE – Dotted symbols apply only to the multiple congestion states option.
+
+**Figure 26a/Q.704 – Signalling message handling; signalling link congestion (HMCG)**
+
+
+
+To/from remote level 3
+
+To message routing (HMRT)
+
+To level 4 User parts
+
+From Management System (MGMT)
+
+To/from signalling route management (SRM)
+
+From unspecified implementation dependent function
+
+**Functional Blocks:**
+
+- Controlled rerouting control (TCRC) Figure 33
+- Forced rerouting control (TFRC) Figure 32
+- Signalling traffica) flow control (TSFC) Figure 34a
+- Signal-linga) routing control (TSRC) Figure 29
+
+**Signal Labels (Vertical/Horizontal):** TCOC, TCBC, TFRC, TCRC, TSFC, TPRC, TLAC, TSRC.
+
+**Message Groups:**
+
+- Changeover acknowledgement, Emergency changeover acknowledgement, Changeback declaration, Changeback acknowledgement, Inhibit/uninhibit/test messages, Changeover order, Emergency changeover order, Traffic restart allowed.
+- MTP resume/pause, MTP status, MTP restart ends. (Note 1)
+- Inhibit signalling link, Uninhibit signalling link, SP restart indication.
+- Controlled rerouting terminated, Send TFCa), Destination congesteda), Distant user part unavailable, Accessibility data request, Signalling route unavailable, Signalling route available, Signalling route restricted, Signalling route available, Restart begins/ends, Forced rerouting not required, Forced rerouting terminated.
+- Accessibility data, Start routine set test, Destination inaccessible/restricted, Destination accessible, Send transfer prohibited message, Adjacent SP restarted, Send transfer restricted message, Forced rerouting, STP no longer used for destination, Adjacent SP restarting, Adjacent SP restarted.
+- Emergency, Emergency ceases.
+- Inhibit allowed/denied, Uninhibit possible/impossible, Uninhibit signalling link, Adjacent SP restarting, SP restart indication, Status sent, Destination accessible, Destination inaccessible, Alternative routing data, Changeover status, Congestion of the signalling link, Adjacent SP restarting, Adjacent SP restricted, Signalling route unavailable, Signalling route restricted.
+
+T1131720-91/d047
+
+Functional block interactions diagram for Level 3 Signalling traffic management (STM). The diagram shows interactions between various functional blocks (TCRC, TFRC, TSFC, TSRC) and external entities (Remote level 3, Message routing HMRT, Level 4 User parts, Management System MGMT, Signalling route management SRM). Key signals include Changeover, Changeback, Inhibit/Uninhibit, Traffic restart, and Routing updates. Arrows indicate the direction of signal flow between blocks and interfaces.
+
+a) Functions modified by sheet 3 in case of multiple congestion states.
+
+NOTE 1 – Implementation dependent.
+
+NOTE 2 – Abbreviated message names have been used in this diagram (i.e. origin-destination codes are omitted).
+
+**Figure 27/Q.704 (sheet 1 of 3) – Level 3 – Signalling traffic management (STM); functional block interactions**
+
+
+
+The diagram illustrates the functional block interactions for Level 3 STM. It features four main functional blocks: Changeback control (TCBC) Figure 31, Changeover control (TCOC) Figure 30, Signalling point restart (TPRC) Figure 34b, and Link availability control (TLAC) Figure 28. These blocks interact with various external entities and internal layers.
+
+- External Entities:**
+ - To/from level 2 (L2):** Interactions include 'Update routing tables', 'Changeback declaration', 'Changeback acknowledgement', 'Retrieve BSNT', 'Retrieval request and FNSC', 'Update routing tables', 'Changeover order', 'Emergency changeover', 'Changeover acknowledgement', 'Emergency changeover acknowledgement', 'Emergency changeover ack.', and 'Inhibit/uninhibit/test messages'.
+ - To/from signalling link management (SLM):** Interactions include 'Changeover order', 'Emergency changeover order', 'Signalling link unavailable', 'Signalling link available', 'Signalling link available', 'Signalling link unavailable', 'Signalling link available', 'Link inhibited', 'Inhibit/uninhibit request', 'Cancel link inhibited', 'Changeover order received', 'Flush buffers', and 'Continue'.
+ - To management system (MGMT):** Interactions include 'Stop L2', 'STM ready', 'Restart begins', 'Restart ends', 'Traffic restart allowed', 'Sending status phase', and 'Send status'.
+ - From unspecified implementation dependent function:** Interactions include 'Link inhibited', 'Link uninhibited', 'Inhibit denied', 'Uninhibit not possible', 'BSNT not retrievable', and 'Retrieval not possible'.
+- Internal Layers:** A vertical stack of layers is shown on the right, including TCOC, TCBC, TFRC, TCRC, TSFC, TPRC, TLAC, and TSRC. Arrows indicate data flow and control signals between the functional blocks and these layers.
+- Functional Block Details:**
+ - Changeback control (TCBC) Figure 31:** Receives 'Alternative routing data request' and 'Procedure terminated' from the layers. It sends 'Update routing tables', 'Changeback declaration', and 'Changeback acknowledgement' to L2. It also receives 'Signalling link available' from SLM and sends 'Changeover order' and 'Emergency changeover order' to SLM.
+ - Changeover control (TCOC) Figure 30:** Receives 'Alternative routing data request' and 'Changeover status request' from the layers. It sends 'Retrieve BSNT', 'Retrieval request and FNSC', 'Update routing tables', 'Changeover order', 'Emergency changeover', 'Changeover acknowledgement', and 'Emergency changeover acknowledgement' to L2. It also receives 'Signalling link available' and 'Signalling link unavailable' from SLM and sends 'Changeover order received', 'Flush buffers', and 'Continue' to SLM.
+ - Signalling point restart (TPRC) Figure 34b:** Receives 'Stop L2', 'STM ready', 'Restart begins', 'Restart ends', 'Traffic restart allowed', 'Sending status phase', and 'Send status' from MGMT. It sends 'Emergency changeover ack.' and 'Inhibit/uninhibit/test messages' to L2. It also receives 'Link inhibited', 'Link uninhibited', 'Inhibit denied', and 'Uninhibit not possible' from the unspecified function.
+ - Link availability control (TLAC) Figure 28:** Receives 'Signalling link available' and 'Signalling link unavailable' from SLM. It sends 'Signalling link available', 'Signalling link unavailable', 'Signalling link failed', 'Signalling link in service', 'Remote processor outage', and 'Remote processor recovered' to SLM. It also receives 'Alternative routing data request' from the layers.
+
+T1142640-92/d048
+
+Functional block interactions diagram for Level 3 STM. It shows interactions between Changeback control (TCBC), Changeover control (TCOC), Signalling point restart (TPRC), and Link availability control (TLAC).
+
+NOTE – Abbreviation message names have been used in this diagram (i.e. origin-destination codes are omitted).
+
+**Figure 27/Q.704 (sheet 2 of 3) – Level 3 – Signalling traffic management (STM); functional block interactions**
+
+
+
+The diagram illustrates the functional block interactions for Level 3 - Signalling traffic management (STM). It features three main functional blocks: **Signalling traffic flow control (TSFC) Figure 34a**, **Signalling route set congestion control (TRCC) Figure 29a**, and **Signalling routing control (TSRC) Figure 29**.
+
+- External Interactions:**
+ - To level 4 (L4):** MTP status (output from TSFC).
+ - From message routing (HMRT):** Message for congested destination (input to TSFC).
+ - To/from signalling route management (SRM):**
+ - Destination congestion status (output from TRCC).
+ - Decrement destination congestion status (input to TRCC).
+ - Start congestion test (input to TRCC).
+ - Stop congestion test (input to TRCC).
+ - From signalling route management (SRM):** Destination congestion status (input to TSFC).
+ - From unspecified implementation dependent function:** Signalling link congestion status (input to TSRC).
+- Internal Interactions:**
+ - TSFC to TRCC:** Destination congestion status (output from TSFC to TRCC).
+ - TRCC to TSFC:** Destination congestion status (input to TSFC).
+ - TRCC to TSRC:** Accessibility data request (output from TRCC to TSRC).
+ - TSRC to TRCC:** Destination inaccessible accessibility data (output from TSRC to TRCC).
+ - TSRC to TSFC:** Signalling link congestion status (output from TSRC to TSFC).
+
+Functional block diagram for Level 3 - Signalling traffic management (STM).
+
+T1131740-91/d049
+
+NOTE – This functional block replaces the items superscripted witha) on sheet 1 in the case of multiple congestion states.
+
+**Figure 27/Q.704 (sheet 3 of 3) – Level 3 – Signalling traffic management (STM); functional block interactions**
+
+
+
+```
+
+graph TD
+ Start([Available]) --> HMDT_Inhibit{Inhibit signalling link HMDT->TLAC}
+ Start --> MGMT_Inhibit{Inhibit signalling link MGMT->TLAC}
+ Start --> Local_Inhibit_Denied{Local inhibit denied TSRC->TLAC}
+
+ HMDT_Inhibit --> Remote_Denied{Remote inhibit denied TSRC->TLAC}
+ Remote_Denied --> Inhibit_Denied_HMRT{Inhibit denied TLAC->HMRT}
+ Inhibit_Denied_HMRT --> Remote_Request{Remote inhibit request TLAC->TSRC}
+ Remote_Request --> End1([Available])
+
+ MGMT_Inhibit --> T14_Timer{T14}
+ T14_Timer --> Cancel_Progress{Cancel local inhibit in progress}
+ Cancel_Progress --> Local_Request{Local inhibit request TLAC->TSRC}
+ Local_Request --> End2([Available])
+
+ Local_Inhibit_Denied --> Local_Allowed{Local inhibit allowed TSRC->TLAC}
+ Local_Allowed --> Inhibit_Signalling_HMRT{Inhibit signalling link TLAC->HMRT}
+ Inhibit_Signalling_HMRT --> Mark_Progress{Mark local inhibit in progress}
+ Mark_Progress --> Start_T14[Start T14]
+ Start_T14 --> Inhibit_Denied_MGMT{Inhibit denied TLAC->MGMT}
+ Inhibit_Denied_MGMT --> End3([Available])
+
+ T1159140-94/d050
+
+```
+
+Flowchart for Signalling traffic management; link availability control (TLAC). The diagram shows three main paths starting from an 'Available' state. Path 1 (left) involves 'Inhibit signalling link HMDT->TLAC', leading to 'Remote inhibit denied TSRC->TLAC', then 'Inhibit denied TLAC->HMRT', and finally 'Remote inhibit request TLAC->TSRC' back to 'Available'. Path 2 (middle) involves 'Inhibit signalling link MGMT->TLAC', leading to a timer 'T14', then 'Cancel local inhibit in progress', then 'Local inhibit request TLAC->TSRC' back to 'Available'. Path 3 (right) involves 'Local inhibit denied TSRC->TLAC', leading to 'Local inhibit allowed TSRC->TLAC', then 'Inhibit signalling link TLAC->HMRT', then 'Mark local inhibit in progress', then 'Start T14', and finally 'Inhibit denied TLAC->MGMT' back to 'Available'. A reference code 'T1159140-94/d050' is present.
+
+**Figure 28/Q.704 (sheet 1 of 18) – Signalling traffic management; link availability control (TLAC)**
+
+
+
+```
+
+graph TD
+ Start([Available]) --> InhibitDenied{Inhibit denied HMDT → TLAC}
+ Start --> InhibitAck{Inhibit ack HMDT → TLAC}
+ Start --> RemoteInhibit{Remote inhibit allowed TSRC → TLAC}
+ InhibitDenied --> InhibitDeniedMgmt{Inhibit denied TLAC → MGMT}
+ InhibitDeniedMgmt --> CancelLocalInhibit[Cancel local inhibit in progress]
+ CancelLocalInhibit --> StopT14[Stop T14]
+ StopT14 --> AvailableEnd([Available])
+ InhibitAck --> LocalInhibitProgress{Local inhibit in progress?}
+ LocalInhibitProgress -- No --> StopT14
+ LocalInhibitProgress -- Yes --> MarkLinkLocallyInhibited[Mark link locally inhibited]
+ MarkLinkLocallyInhibited --> CancelLocalInhibitMgmt[Cancel local inhibit in progress]
+ CancelLocalInhibitMgmt --> StopT14Mgmt[Stop T14]
+ StopT14Mgmt --> LinkInhibitedTsrc{Link inhibited TLAC → TSRC}
+ LinkInhibitedTsrc --> LinkInhibitedMgmt{Link inhibited TLAC → MGMT}
+ RemoteInhibit --> MarkLinkRemotelyInhibited[Mark link remotely inhibited]
+ MarkLinkRemotelyInhibited --> InhibitAckHmrt{Inhibit ack TLAC → HMRT}
+ InhibitAckHmrt --> LinkInhibitedTsrc
+ LinkInhibitedMgmt --> LinkLocallyInhibited{link locally inhibited?}
+ LinkLocallyInhibited -- Yes --> StartT22[Start T22]
+ LinkLocallyInhibited -- No --> LinkRemotelyInhibited{link remotely inhibited?}
+ StartT22 --> LinkRemotelyInhibited
+ LinkRemotelyInhibited -- Yes --> StartT23[Start T23]
+ LinkRemotelyInhibited -- No --> End((1))
+ StartT23 --> End
+ End -.-> T1159150-94/d051
+ T1159150-94/d051 --> LinkInhibitedTsrc
+ InhibitDenied -.-> Connector2((2))
+ Connector2 -.-> Start
+ style Connector2 fill:none,stroke:none
+ style T1159150-94/d051 fill:none,stroke:none
+
+```
+
+Flowchart for Signalling traffic management; link availability control (TLAC). The process starts with 'Available' and branches into three main paths: 'Inhibit denied HMDT → TLAC', 'Inhibit ack HMDT → TLAC', and 'Remote inhibit allowed TSRC → TLAC'. It includes decision diamonds for 'Local inhibit in progress?', 'link locally inhibited?', and 'link remotely inhibited?'. It ends at connector '1'.
+
+**Figure 28/Q.704 (sheet 2 of 18) – Signalling traffic management; link availability control (TLAC)**
+
+
+
+The flowchart illustrates the signalling traffic management and link availability control (TLAC) process. It begins with a horizontal line at the top labeled "From remote level 3". Below this line, six input conditions are listed, each with a corresponding action and subsequent decision logic:
+
+- Local processor outage (MGMT → TLAC):** Action: "Mark local blocked". This leads to a decision diamond "Changeback in progress?". If "Yes", the action is "Mark link unavailable", leading to connector 3. If "No", the action is "Signalling link unavailable (TLAC → TCOC)", which leads to connector 4. From connector 4, the action is "Mark changeover in progress", leading to the final state "Unavailable".
+- Signalling link failed (LSAC → TLAC):** Action: "Mark failed". This leads directly to the "Changeback in progress?" decision diamond.
+- Remote processor outage (LSAC → TLAC):** Action: "Mark remote blocked". This leads directly to the "Changeback in progress?" decision diamond.
+- Changeover order (HMDT → TLAC):** Action: "Mark failed". This leads to a decision diamond "Changeover order received (TLAC → LSAC)". If "Yes", it leads to another "Changeback in progress?" decision diamond. If "Yes", the action is "Mark changeover order", leading to connector 3(2). From connector 3(2), the action is "Signalling link unavailable (TLAC → TSRC)", leading to connector 4. From connector 4, the action is "Mark changeover in progress", leading to the final state "Unavailable". If "No", the action is "Changeover order (TLAC → TCOC)", leading to connector 3(2), which then leads to connector 4.
+- Changeback terminated (TCBC → TLAC):** Action: "Cancel changeback in progress". This leads directly to the final state "Available".
+- Emergency changeover order (HMDT → TLAC):** Action: "Mark failed". This leads to a decision diamond "Changeover order received (TLAC → LSAC)". If "Yes", it leads to a "Changeback in progress?" decision diamond. If "Yes", the action is "Mark emergency changeover order", leading to connector 3. If "No", the action is "Emergency changeover order (TLAC → TCOC)", leading to connector 4.
+
+Connectors are represented by circles with numbers: 1, 2, 3, 3(2), 4. The numbers 2, 1, 3, 4 are also placed on the left margin next to their respective connector circles. The numbers 3, 4 are placed on the left margin next to the "Mark changeover in progress" and "Signalling link unavailable (TLAC → TSRC)" actions.
+
+Flowchart for Signalling traffic management; link availability control (TLAC).
+
+NOTE 1 – See sheet 3 *bis* for national option.
+
+NOTE 2 – The layer management informs level 3 that the concerned link is locally blocked (implementation dependent).
+
+**Figure 28/Q.704 (sheet 3 of 18) – Signalling traffic management;
+link availability control (TLAC)**
+
+
+
+The flowchart illustrates the signalling traffic management and link availability control (TLAC) process. It begins with a horizontal line at the top labeled 'From remote level 3'. Below this line, six input conditions are listed, each leading to a specific action and subsequent decision logic:
+
+- Local processor outage (MGMT → TLAC):** Leads to 'Mark local blocked', which then leads to connector '2'. Connector '2' leads to a decision diamond 'Changeback in progress?'. If 'Yes', it leads to 'Mark link unavailable' and then to connector '3'. If 'No', it leads to 'Signalling link unavailable (TLAC → TCOC)', which leads to 'Signalling link unavailable (TLAC → TSRC)', which leads to 'Mark changeover in progress', which finally leads to the 'Unavailable' state.
+- Signalling link failed (LSAC → TLAC):** Leads to 'Mark failed', which then leads to connector '1'. Connector '1' leads to the same 'Changeback in progress?' decision diamond.
+- Remote processor outage (LSAC → TLAC):** Leads to 'Mark remote blocked', which leads to 'Local processor outage (TLAC → LSAC)', which then leads to connector '1'.
+- Changeover order (HMDT → TLAC):** Leads to 'Mark failed', which leads to 'Changeover order received (TLAC → LSAC)', which leads to a decision diamond 'Changeback in progress?'. If 'Yes', it leads to 'Mark changeover order', which leads to connector '4'. If 'No', it leads to 'Changeover order (TLAC → TCOC)', which leads to connector '3 bis(2)' and then to connector '4'.
+- Changeback terminated (TCBC → TLAC):** Leads to 'Cancel changeback in progress', which leads to the 'Available' state.
+- Emergency changeover order (HMDT → TLAC):** Leads to 'Mark failed', which leads to 'Changeover order received (TLAC → LSAC)', which leads to a decision diamond 'Changeback in progress?'. If 'Yes', it leads to 'Mark emergency changeover order', which leads to connector '3 bis' and then to connector '3'. If 'No', it leads to 'Emergency changeover order (TLAC → TCOC)', which leads to connector '3 bis' and then to connector '4'.
+
+Additional connectors and labels include '3 bis', '4', '3 bis(2)', and '4, 3, 4' on the left side of the diagram. A reference code 'T1142660-92/d53' is located at the bottom right.
+
+Flowchart for Signalling traffic management; link availability control (TLAC) (National option).
+
+NOTE – The layer management informs level 3 that the concerned link is locally blocked (implementation dependent).
+
+**Figure 28/Q.704 (sheet 3 bis of 18) – Signalling traffic management; link availability control (TLAC) (National option)**
+
+
+
+```
+
+graph TD
+ Start([Unavailable]) --> Step1[/Changeback terminated
+TCBC→TLAC/]
+ Step1 --> Step2[Cancel changeback
+in progress]
+ Step2 --> Decision1{Changeover
+order?}
+ Decision1 -- Yes --> Step3[/Changeover
+order
+TLAC→TCOC/]
+ Decision1 -- No --> Decision2{Emergency
+changeover
+order?}
+ Decision2 -- Yes --> Step4[/Emergency
+changeover
+order
+TLAC→TCOC/]
+ Decision2 -- No --> Decision3{Link
+unavailable?}
+ Decision3 -- Yes --> Step5[/Signalling link
+unavailable
+TLAC→TCOC/]
+ Decision3 -- No --> Step4
+ Step3 --> Step6[Cancel link
+unavailable]
+ Step4 --> Step6
+ Step5 --> Step6
+ Step6 --> Step7[Cancel emergency
+changeover order]
+ Step7 --> Step8[Cancel
+changeover order]
+ Step8 --> End((4))
+ subgraph Footer
+ T1159160-94/d054
+ end
+
+```
+
+Flowchart for Signalling traffic management; link availability control (TLAC).
+
+4
+
+3
+
+4
+
+**Figure 28/Q.704 (sheet 4 of 18) – Signalling traffic management;
+link availability control (TLAC)**
+
+
+
+```
+
+graph TD
+ Start([Unavailable]) --> 10((10))
+ Start --> SLF[Signalling link failed
+LSAC→TLAC]
+ Start --> SLS[Signalling link in service
+LSAC→TLAC]
+ Start --> LPO[Local processor outage
+MGMT→TLAC]
+ Start --> RPO[Remote processor outage
+LSAC→TLAC]
+
+ SLF --> SLF_A[Mark failed;
+cancel remote
+blocked and
+local blocked]
+ SLS --> SLS_A[Cancel failed]
+ LPO --> LPO_A[Mark local
+blocked;
+cancel failed]
+ RPO --> RPO_A[Mark remote
+blocked;
+cancel failed]
+
+ SLF_A --> LI{Link inhibited?
+(Note 1)}
+ SLS_A --> 11((11))
+ LPO_A --> LI
+ RPO_A --> 11
+ RPO_A --> U1([Unavailable])
+
+ LI -- Yes --> U2([Unavailable])
+ LI -- No --> 6((6))
+ LI -- No --> CIP{Changeover in progress?}
+
+ CIP -- No --> 5((5))
+ CIP -- Yes --> SLA[Signalling link available
+TLAC→TCOC]
+
+ SLA --> U3([Unavailable])
+
+```
+
+Flowchart for Signalling traffic management; link availability control (TLAC). The process starts with an 'Unavailable' state, leading to four parallel paths based on the cause: 'Signalling link failed LSAC→TLAC', 'Signalling link in service LSAC→TLAC', 'Local processor outage MGMT→TLAC', and 'Remote processor outage LSAC→TLAC'. Each path leads to specific actions like marking failed or blocked, and then to decision diamonds for 'Link inhibited?' and 'Changeover in progress?'. The flowchart includes various connectors (circles 5, 6, 7, 10, 11) and ends in 'Unavailable' states or a 'Signalling link available TLAC→TCOC' state. Reference numbers 10, 11, 6, 6, 10(2), 7 are present next to connectors. A note 'T1142670-92/d055' is also visible.
+
+NOTE 1 – "Inhibited" indicates either locally or remotely inhibited, or both.
+
+NOTE 2 – See sheet 5 *bis*, for national option.
+
+**Figure 28/Q.704 (sheet 5 of 18) – Signalling traffic management;
+link availability control (TLAC)**
+
+
+
+```
+
+graph TD
+ Start([Unavailable]) --> J1(( ))
+ J1 --> S1{Signalling link failed
+LSAC→TLAC}
+ J1 --> S2{Signalling link in service
+LSAC→TLAC}
+ J1 --> S3{Remote processor recovered
+LSAC→TLAC}
+ J1 --> S4{Remote processor outage
+LSAC→TLAC}
+ S1 --> M1[Mark failed;
+cancel remote
+blocked and
+local blocked]
+ M1 --> T1{{Stop T24}}
+ T1 --> U1([Unavailable])
+ S2 --> M2[Cancel failed]
+ M2 --> T2{{Stop T24}}
+ T2 --> J2((11))
+ J2 --> L1{Link inhibited?}
+ L1 -- Yes --> U2([Unavailable])
+ L1 -- No --> J3((6))
+ J3 --> C1{Changeover in progress?}
+ C1 -- No --> J4((5))
+ C1 -- Yes --> S5{Signalling link available
+TLAC→TCOC}
+ S5 --> U3([Unavailable])
+ S3 --> M3[Cancel remote blocked]
+ M3 --> T3{T24 running?}
+ T3 -- No --> J5((6))
+ T3 -- Yes --> U4([Unavailable])
+ S4 --> M4[Mark remote blocked;
+cancel failed]
+ M4 --> U4
+ U4 -.-> T1142690-92/d056
+ S4 -.-> J6((10))
+ J6 -.-> 6bis[6 bis]
+
+```
+
+The flowchart illustrates the signalling traffic management and link availability control (TLAC) process. It begins with an 'Unavailable' state, leading to a junction point. From this junction, four paths emerge based on the status of the signalling link and remote processor.
+
+1. 'Signalling link failed' (LSAC→TLAC) leads to marking the link as failed, cancelling remote blocked and local blocked states, stopping T24, and resulting in an 'Unavailable' state.
+
+2. 'Signalling link in service' (LSAC→TLAC) leads to cancelling failed states, stopping T24, and then checking if the link is inhibited. If inhibited, it becomes 'Unavailable'; otherwise, it checks if a changeover is in progress. If not, it leads to junction 5; if yes, it checks if the signalling link is available (TLAC→TCOC) and becomes 'Unavailable'.
+
+3. 'Remote processor recovered' (LSAC→TLAC) leads to cancelling remote blocked states and checking if T24 is running. If not, it leads to junction 6; if yes, it becomes 'Unavailable'.
+
+4. 'Remote processor outage' (LSAC→TLAC) leads to marking the remote blocked and cancelling failed states, resulting in an 'Unavailable' state. This path also connects to junction 10 and is associated with '6 bis'.
+
+Additional junctions and notes include: Junction 11 leads to the 'Link inhibited?' decision; Junction 6 (after 'Link inhibited?' No) leads to 'Changeover in progress?'; Junction 5 is the exit point for 'Changeover in progress? No'; Junction 6 (after 'T24 running? No') is an exit point; a note indicates that 'Inhibited' means locally or remotely inhibited; and a reference T1142690-92/d056 is provided for the 'Unavailable' state in the remote processor outage path.
+
+Flowchart for Signalling traffic management; link availability control (TLAC) (National option).
+
+NOTE – “Inhibited” indicates either locally or remotely inhibited, or both.
+
+**Figure 28/Q.704 (sheet 5 bis of 18) – Signalling traffic management;
+link availability control (TLAC) (National option)**
+
+
+
+```
+
+graph TD
+ 10((10)) --> LSAC_TLAC[Link in service at level 2 LSAC→TLAC]
+ 10 --> Remote_Recovered[Remote processor recovered LSAC→TLAC]
+ 10 --> Local_Recovered[Local processor recovered MGMT→TLAC]
+
+ LSAC_TLAC --> Link_Service[Link in service at level 2 TLAC→TSRC]
+ Link_Service --> Unavailable1([Unavailable])
+
+ Remote_Recovered --> Cancel_Remote[Cancel remote blocked]
+ Cancel_Remote --> Local_Blocked{Link local blocked?}
+
+ Local_Recovered --> Cancel_Local[Cancel local blocked]
+ Cancel_Local --> Remote_Blocked{Link remote blocked?}
+
+ Local_Blocked -- Yes --> Unavailable2([Unavailable])
+ Local_Blocked -- No --> Changeover{Changeover in progress?}
+
+ Remote_Blocked -- Yes --> Unavailable2
+ Remote_Blocked -- No --> Changeover
+
+ Changeover -- Yes --> T1_Running[T1 is running]
+ T1_Running --> Continue[Continue TLAC→LSAC]
+
+ Changeover -- No --> T1_Expired[T1 expired]
+ T1_Expired --> Flush[Flush buffers TLAC→LSAC]
+
+ Continue --> 11((11))
+ Flush --> 11
+
+```
+
+Flowchart for Signalling traffic management; link availability control (TLAC). The process starts at connector 10 and branches into three main paths: 'Link in service at level 2 LSAC→TLAC', 'Remote processor recovered LSAC→TLAC', and 'Local processor recovered MGMT→TLAC'. The first path leads to 'Link in service at level 2 TLAC→TSRC' and then to 'Unavailable'. The second and third paths lead to 'Cancel remote blocked' and 'Cancel local blocked' respectively, which then lead to decision diamonds 'Link local blocked?' and 'Link remote blocked?'. If either is 'Yes', it leads to 'Unavailable'. If both are 'No', it leads to 'Changeover in progress?'. From there, if 'Yes' and 'T1 is running', it leads to 'Continue TLAC→LSAC'. If 'No' and 'T1 expired', it leads to 'Flush buffers TLAC→LSAC'. Both 'Continue' and 'Flush buffers' lead to connector 11.
+
+NOTE – See sheet 6 bis, for national option.
+
+**Figure 28/Q.704 (sheet 6 of 18) – Signalling traffic management; link availability control (TLAC)**
+
+
+
+10
+
+5 bis
+
+```
+
+graph TD
+ 10((10)) --> L1[Link in service at level 2
+LSAC→TLAC]
+ 10 --> L2[Local processor outage
+MGMT→TLAC]
+ 10 --> L3[Local processor recovered
+MGMT→TLAC]
+ L1 --> L1b[Link in service at level 2
+TLAC→TSRC]
+ L2 --> L2b[Mark local blocked;
+cancel failed]
+ L3 --> L3b[Cancel local blocked]
+ L1b --> U1([Unavailable])
+ L2b --> U2([Unavailable])
+ L3b --> D{Link remote blocked?}
+ D -- No --> 11((11))
+ D -- Yes --> U3([Unavailable])
+
+```
+
+11
+
+5 bis
+
+T1142700-92/d058
+
+Flowchart for Signalling traffic management; link availability control (TLAC) (National option). The flowchart starts at connector 10 and branches into three main paths based on the status of the link and local processor. Path 1: 'Link in service at level 2' (LSAC→TLAC) leads to 'Link in service at level 2' (TLAC→TSRC) which results in 'Unavailable'. Path 2: 'Local processor outage' (MGMT→TLAC) leads to 'Mark local blocked; cancel failed' which also results in 'Unavailable'. Path 3: 'Local processor recovered' (MGMT→TLAC) leads to 'Cancel local blocked' which leads to a decision 'Link remote blocked?'. If 'No', it goes to connector 11. If 'Yes', it results in 'Unavailable'.
+
+**Figure 28/Q.704 (sheet 6 bis of 18) – Signalling traffic management;
+link availability control (TLAC) (National option)**
+
+112 Recommendation Q.704 (07/96)
+
+5
+
+Image: Figure 28/Q.704 (sheet 7 of 18) – Signalling traffic management; link availability control (TLAC)
+
+```
+
+ graph TD
+ Start([Unavailable]) --> Choice{ }
+ Choice --> |Link is available again| ChangeoverNotReq[Changeover not required
TCOC → TLAC]
+ Choice --> |Link is available again| ChangeoverExec[Changeover executed
TCOC → TLAC]
+
+ ChangeoverNotReq --> Cancel1[Cancel changeover in progress]
+ ChangeoverExec --> Cancel2[Cancel changeover in progress]
+
+ Cancel2 --> LinkInhibited{Link inhibited?}
+ LinkInhibited -->|Yes| UnavailableEnd([Unavailable])
+ LinkInhibited -->|No| RemotelyInhibited{Remotely inhibited?}
+
+ RemotelyInhibited -->|Yes| UnavailableEnd
+ RemotelyInhibited -->|No| FailedLocally{Failed locally blocked?}
+
+ FailedLocally -->|Yes| UnavailableEnd
+ FailedLocally -->|No| FailedRemotely{Failed remotely blocked?}
+
+ FailedRemotely -->|Yes| UnavailableEnd
+ FailedRemotely -->|No| SignallingLinkAvail1[Signalling link available
TLAC → TCBC]
+
+ Cancel1 --> SignallingLinkAvail2[Signalling link available
TLAC → TSRC]
+
+ SignallingLinkAvail1 --> MarkChangeback[Mark changeback in progress]
+ MarkChangeback --> SignallingLinkAvail2
+ SignallingLinkAvail2 --> Available([Available])
+
+ Connector((5)) --> SignallingLinkAvail1
+
+```
+
+Detailed description: The flowchart starts at an 'Unavailable' state. When a 'Link is available again', it branches into two paths: 'Changeover not required TCOC → TLAC' and 'Changeover executed TCOC → TLAC'. Both lead to a 'Cancel changeover in progress' process. The 'executed' path then enters a series of four decision diamonds: 'Link inhibited?', 'Remotely inhibited?', 'Failed locally blocked?', and 'Failed remotely blocked?'. If any are 'Yes', it leads to an 'Unavailable' terminal state. If all are 'No', it proceeds to 'Signalling link available TLAC → TCBC', which is also an entry point for connector '5'. This is followed by 'Mark changeback in progress' and then 'Signalling link available TLAC → TSRC'. The 'not required' path skips the decisions and goes directly to 'Signalling link available TLAC → TSRC'. The final state is 'Available'.
+
+NOTE 1 – See sheet 7 *bis*, for national option.
+
+NOTE 2 – The changes performed on this sheet are clarifications compared to the *Blue Book*.
+
+**Figure 28/Q.704 (sheet 7 of 18) – Signalling traffic management; link availability control (TLAC)**
+
+T1176680-95
+
+
+
+```
+
+graph TD
+ Start([Unavailable]) --> TCOC_TLAC_1{Changeover not required
+TCOC→TLAC}
+ Start --> TCOC_TLAC_2{Changeover executed
+TCOC→TLAC}
+ Start --> T24_1{T24}
+
+ TCOC_TLAC_1 --> LinkAvailable1[Link is available again]
+ LinkAvailable1 --> Cancel1[Cancel changeover in progress]
+ Cancel1 --> Signalling1[Signalling link available
+TLAC→TCBC]
+ Signalling1 --> Mark1[Mark changeback in progress]
+ Mark1 --> Signalling2[Signalling link available
+TLAC→LSAC]
+ Signalling2 --> Available1([Available])
+
+ TCOC_TLAC_2 --> Cancel2[Cancel changeover in progress]
+ Cancel2 --> Local[Local processor recovered
+TLAC→LSAC]
+ Local --> StartT24[Start T24]
+ StartT24 --> Mark2[Mark changeback required]
+ Mark2 --> Unavailable2([Unavailable])
+
+ T24_1 --> LinkInhibited{Link inhibited?}
+ LinkInhibited -- Yes --> LinkFailed{Link failed?}
+ LinkInhibited -- No --> LinkBlocked{Link blocked?}
+ LinkFailed -- Yes --> LinkBlocked
+ LinkFailed -- No --> LinkBlocked
+ LinkBlocked -- Yes --> ChangebackRequired{Changeback required?}
+ LinkBlocked -- No --> ChangebackRequired
+ ChangebackRequired -- Yes --> Connector5((5
+7 bis))
+ ChangebackRequired -- No --> Signalling3[Signalling link available
+TLAC→LSAC]
+ Signalling3 --> Available2([Available])
+
+```
+
+The flowchart illustrates the link availability control (TLAC) process. It begins with an 'Unavailable' state. From here, three paths emerge based on the TCOC→TLAC changeover status and T24 status.
+
+1. If a changeover is not required (TCOC→TLAC), the link is available again, and the process moves to 'Cancel changeover in progress', then 'Signalling link available (TLAC→TCBC)', 'Mark changeback in progress', 'Signalling link available (TLAC→LSAC)', and finally to an 'Available' state.
+
+2. If a changeover is executed (TCOC→TLAC), the process moves to 'Cancel changeover in progress', 'Local processor recovered (TLAC→LSAC)', 'Start T24', 'Mark changeback required', and ends in an 'Unavailable' state.
+
+3. If the T24 status is checked, the process moves to a decision 'Link inhibited?'. If 'Yes', it moves to 'Link failed?'. If 'No', it moves to 'Link blocked?'. Both 'Link failed?' (if 'Yes') and 'Link blocked?' (if 'Yes') lead to 'Changeback required?'. If 'Changeback required?' is 'Yes', the process reaches connector '5 (7 bis)'. If 'No', it moves to 'Signalling link available (TLAC→LSAC)' and ends in an 'Available' state.
+
+A connector '5 (5 bis, 7 bis)' is also shown between the first and second paths.
+
+Flowchart for Signalling traffic management; link availability control (TLAC) (National option).
+
+**Figure 28/Q.704 (sheet 7 bis of 18) – Signalling traffic management;
+link availability control (TLAC) (National option)**
+
+T1142720-92/d060
+
+
+
+```
+
+graph TD
+ Start1([Unavailable]) --> HMDT_TLAC1{{Changeover order
+HMDT→TLAC}}
+ Start2([Unavailable]) --> HMDT_TLAC2{{Emergency changeover order
+HMDT→TLAC}}
+ HMDT_TLAC1 --> Progress1{Changeover in progress?}
+ Progress1 -- No --> Ack1{{Emergency changeover acknowledgement
+TLAC→HMRT}}
+ Progress1 -- Yes --> TCOC1{{Changeover order
+TLAC→TCOC}}
+ HMDT_TLAC2 --> Progress2{Changeover in progress?}
+ Progress2 -- No --> Ack2{{Emergency changeover acknowledgement
+TLAC→HMRT}}
+ Progress2 -- Yes --> TCOC2{{Emergency changeover order
+TLAC→TCOC}}
+ Ack1 --> End([Unavailable])
+ TCOC1 --> End
+ TCOC2 --> End
+ Ack2 --> End
+ FromRemote3[From remote level 3] -.-> HMDT_TLAC2
+ T1159170-94/d061
+
+```
+
+The flowchart illustrates the signalling traffic management and link availability control (TLAC) process. It begins with two 'Unavailable' states. The left path involves a 'Changeover order HMDT→TLAC', followed by a decision 'Changeover in progress?'. If 'No', an 'Emergency changeover acknowledgement TLAC→HMRT' is sent. If 'Yes', a 'Changeover order TLAC→TCOC' is sent. The right path involves an 'Emergency changeover order HMDT→TLAC', also followed by a 'Changeover in progress?' decision. If 'No', an 'Emergency changeover acknowledgement TLAC→HMRT' is sent. If 'Yes', an 'Emergency changeover order TLAC→TCOC' is sent. All four resulting actions lead to a final 'Unavailable' state. A dashed line from 'From remote level 3' points to the 'Emergency changeover order HMDT→TLAC' block. The identifier 'T1159170-94/d061' is located at the bottom right.
+
+Flowchart for signalling traffic management; link availability control (TLAC).
+
+**Figure 28/Q.704 (sheet 8 of 18) – Signalling traffic management;
+link availability control (TLAC)**
+
+
+
+```
+
+graph TD
+ Start([Unavailable]) --> P1[Uninhibiting not possible TSRC→TLAC]
+ Start --> P2[Uninhibiting possible TSRC→TLAC]
+ Start --> P3[Force uninhibit signalling link HMDT→TLAC]
+ Start --> P4[T12]
+ Start --> P5[Uninhibit signalling link MGMT→TLAC]
+
+ P1 --> D1{Failed or blocked?}
+ D1 -- No --> C7((7))
+ D1 -- Yes --> P6[Uninhibiting not possible TLAC→MGMT]
+ P6 --> P7[Cancel management request]
+ P7 --> C9((9))
+
+ P2 --> D2{Link inhibited?}
+ D2 -- Yes --> C7
+ D2 -- No --> P8[Uninhibit signalling link TLAC→HMRT]
+ P8 --> C10((10))
+
+ P3 --> D2
+ D2 -- Yes --> C7
+ D2 -- No --> P9[Uninhibit signalling link TLAC→HMRT]
+ P9 --> C10
+
+ P4 --> P10[Cancel uninhibit in progress]
+ P10 --> D3{2nd time T12 expires?}
+ D3 -- Yes --> C9
+ D3 -- No --> D4{Management request?}
+ D4 -- Yes --> P11[Uninhibit request TLAC→TSRC]
+ D4 -- No --> C7
+ P11 --> C9
+
+ P5 --> P12[Mark management request]
+ P12 --> C9
+
+ C7 --> End([Unavailable])
+ C9 --> End
+ C10 --> End
+
+```
+
+Flowchart for Signalling traffic management; link availability control (TLAC). The process starts with 'Unavailable' and branches into five main paths: 'Uninhibiting not possible TSRC→TLAC', 'Uninhibiting possible TSRC→TLAC', 'Force uninhibit signalling link HMDT→TLAC', 'T12', and 'Uninhibit signalling link MGMT→TLAC'. Each path leads to various decision diamonds and process blocks, eventually converging back to 'Unavailable' or to connector circles 7, 9, and 10.
+
+NOTE – The word "blocked" indicates remote blocked.
+
+Figure 28/Q.704 (sheet 9 of 18) – Signalling traffic management; link availability control (TLAC)
+
+
+
+```
+
+graph TD
+ Start([Unavailable]) --> P1[Uninhibit signalling link HMDT->TLAC]
+ Start --> P2[T13]
+ Start --> P3[Uninhibit signalling link TSRC->TLAC]
+ Start --> P4[Uninhibit ack HMDT->TLAC]
+
+ P1 --> D1{Link inhibited?}
+ D1 -- No --> C1((8 10))
+ D1 -- Yes --> D2{Cancel link remotely inhibited?}
+ D2 --> P5[Uninhibit acknowledgement TLAC->HMRT]
+ P5 --> P6[Stop T13]
+ P6 --> D3{Link locally inhibited?}
+ D3 -- Yes --> C2((9))
+ D3 -- No --> P7[Cancel link inhibited TLAC->TSRC]
+ P7 --> D4{Failed or blocked?}
+ D4 -- Yes --> P8[Uninhibit acknowledgement TLAC->HMRT]
+ D4 -- No --> C3((6 5))
+
+ P2 --> D5{2nd time T13 expires?}
+ D5 -- Yes --> C4((9))
+ D5 -- No --> D6{Locally inhibited?}
+ D6 -- No --> C5((8 10))
+ D6 -- Yes --> P9[Uninhibit signalling link TLAC->HMRT]
+ P9 --> P10[Start T12]
+ P10 --> D7{Remotely inhibited?}
+ D7 -- Yes --> P11[Force uninhibit signalling link TLAC->HMRT]
+ P11 --> P12[Start T13]
+ P12 --> P13[Uninhibit acknowledgement TLAC->HMRT]
+ P13 --> C5
+ D7 -- No --> C6((6 5))
+
+ P3 --> D8{Failed or blocked?}
+ D8 -- Yes --> C6
+ D8 -- No --> D9{Locally inhibited?}
+ D9 -- No --> C5
+ D9 -- Yes --> P9
+
+ P4 --> D10{Uninhibit in progress?}
+ D10 -- Yes --> P14[Cancel link locally inhibited management request]
+ P14 --> P15[Link uninhibited TLAC->MGMT]
+ P15 --> P16[Cancel uninhibit in progress]
+ P16 --> P17[Stop T12]
+ P17 --> D11{Link remotely inhibited?}
+ D11 -- Yes --> C6
+ D11 -- No --> P18[Cancel link inhibited TLAC->TSRC]
+ P18 --> D12{Failed or blocked?}
+ D12 -- Yes --> C6
+ D12 -- No --> C3
+
+```
+
+NOTE – The word "blocked" indicates remotely blocked.
+
+Flowchart for Signalling traffic management; link availability control (TLAC). The process starts with 'Unavailable' and branches into four main paths: Uninhibit signalling link HMDT->TLAC, T13 timer, Uninhibit signalling link TSRC->TLAC, and Uninhibit ack HMDT->TLAC. Each path contains decision diamonds for 'Link inhibited?', 'Failed or blocked?', 'Locally inhibited?', 'Remotely inhibited?', and '2nd time T13 expires?'. It includes process steps like 'Cancel link remotely inhibited?', 'Uninhibit acknowledgement TLAC->HMRT', 'Stop T13', 'Link locally inhibited?', 'Cancel link inhibited TLAC->TSRC', 'Uninhibit acknowledgement TLAC->HMRT', 'Start T13', 'Uninhibit signalling link TLAC->HMRT', 'Start T12', 'Link uninhibited TLAC->MGMT', 'Cancel link locally inhibited management request', 'Cancel uninhibit in progress', 'Stop T12', and 'Force uninhibit signalling link TLAC->HMRT'. The flowchart ends at 'Unavailable' or connector circles 8, 9, 10, 6, 5. A note indicates 'The word "blocked" indicates remotely blocked.'
+
+**Figure 28/Q.704 (sheet 10 of 18) – Signalling traffic management; link availability control (TLAC)**
+
+
+
+```
+
+graph TD
+ Start([Unavailable])
+ End([Unavailable])
+
+ Start --- Path1
+ Start --- Path2
+ Start --- Path3
+
+ subgraph Path1
+ Inhibit1[Inhibit
+signalling link
+MGMT → TLAC] --> T14_Wait{{T14}}
+ T14_Wait --> Cancel[Cancel local
+inhibit in progress]
+ end
+
+ subgraph Path2
+ LocalInhibitDenied[Local inhibit
+denied
+TSRC → TLAC] --> InhibitDenied[Inhibit
+denied
+TLAC → MGMT]
+
+ LocalInhibitAllowed[Local inhibit
+allowed
+TSRC → TLAC] --> InhibitHMRT[Inhibit
+signalling link
+TLAC → HMRT]
+ InhibitHMRT --> MarkLocal[Mark local
+inhibit in progress]
+ MarkLocal --> StartT14[Start T14]
+ end
+
+ subgraph Path3
+ InhibitHMDT[Inhibit
+signalling link
+HMDT → TLAC] --> LinkRemotely{Link
+remotely
+inhibited?}
+ LinkRemotely -- Yes --> InhibitAck1[Inhibit
+ack
+TLAC → HMRT]
+ LinkRemotely -- No --> MarkRemote[Mark link
+remotely inhibited]
+ MarkRemote --> InhibitAck2[Inhibit
+ack
+TLAC → HMRT]
+ InhibitAck2 --> LinkInhibited[Link
+inhibited
+TLAC → TSRC]
+ LinkInhibited --> StartT22[Start T22]
+ end
+
+ Cancel --> LocalInhibitReq[Local inhibit
+request
+TLAC → TSRC]
+ LocalInhibitReq --> End
+ StartT14 --> End
+ InhibitDenied --> End
+ InhibitAck1 --> End
+ StartT22 --> End
+
+```
+
+The flowchart illustrates the signalling traffic management and link availability control (TLAC) process. It begins with an 'Unavailable' state and branches into several paths based on input signals like 'Inhibit signalling link MGMT → TLAC', 'Local inhibit denied TSRC → TLAC', 'Local inhibit allowed TSRC → TLAC', and 'Inhibit signalling link HMDT → TLAC'. The process involves decision points such as checking if a link is remotely inhibited, marking inhibit statuses, sending acknowledgement signals (e.g., 'Inhibit ack TLAC → HMRT'), and starting timers T14 and T22. All paths eventually return to the 'Unavailable' state.
+
+Flowchart for Signalling traffic management; link availability control (TLAC).
+
+T1159180-94/d064
+
+**Figure 28/Q.704 (sheet 11 of 18) – Signalling traffic management;
+link availability control (TLAC)**
+
+
+
+```
+
+graph TD
+ Start([Available]) --> H1(( ))
+ H1 --> T1[Uninhibit signalling link HMDT→TLAC]
+ H1 --> T2[Force uninhibit signalling link HMDT→TLAC]
+ H1 --> T3[Uninhibit ack HMDT→TLAC]
+ T1 --> T4[Uninhibit ack TLAC→HMRT]
+ T2 --> T5[Uninhibit signalling link TLAC→HMRT]
+ T3 --> H2(( ))
+ T4 --> H2
+ T5 --> H2
+ H2 --> End([Available])
+ style H1 fill:none,stroke:none
+ style H2 fill:none,stroke:none
+
+```
+
+T1159190-94/d065
+
+Flowchart for Signalling traffic management; link availability control (TLAC). The process starts with 'Available', leading to three parallel actions: 'Uninhibit signalling link HMDT→TLAC', 'Force uninhibit signalling link HMDT→TLAC', and 'Uninhibit ack HMDT→TLAC'. The first two lead to 'Uninhibit ack TLAC→HMRT' and 'Uninhibit signalling link TLAC→HMRT' respectively. All three parallel paths converge to a final 'Available' state. Reference code T1159190-94/d065 is present.
+
+**Figure 28/Q.704 (sheet 12 of 18) – Signalling traffic management; link availability control (TLAC)**
+
+
+
+```
+
+graph TD
+ Start([Unavailable]) --> Inhibit[Inhibit ack HMDT→TLAC]
+ Inhibit --> Decision{Local inhibit in progress?}
+ Decision -- No --> StartT22[/Start T22/]
+ Decision -- Yes --> Mark[Mark link locally inhibited]
+ Mark --> LinkInhibited1[/Link Inhibited TLAC→TSRC/]
+ LinkInhibited1 --> LinkInhibited2[/Link Inhibited TLAC→MGMT/]
+ LinkInhibited2 --> Cancel[Cancel local inhibit in progress]
+ Cancel --> StopT14[/Stop T14/]
+ StopT14 --> StartT22
+ StartT22 --> End([Unavailable])
+
+```
+
+T1159200-94/d066
+
+Flowchart for Signalling traffic management; link availability control (TLAC). The process starts with 'Unavailable', followed by 'Inhibit ack HMDT→TLAC'. A decision diamond asks 'Local inhibit in progress?'. If 'No', it goes to 'Start T22'. If 'Yes', it goes through 'Mark link locally inhibited', 'Link Inhibited TLAC→TSRC', 'Link Inhibited TLAC→MGMT', 'Cancel local inhibit in progress', and 'Stop T14' before reaching 'Start T22'. Both 'Start T22' and 'Stop T14' lead to the final 'Unavailable' state.
+
+**Figure 28/Q.704 (sheet 13 of 18) – Signalling traffic management; link availability control (TLAC)**
+
+
+
+```
+
+graph TD
+ Start([Available]) --> L1[Local inhibit test HMDT → TLAC]
+ Start --> R1[Remote inhibit test HMDT → TLAC]
+ Start --> T23[T23]
+ Start --> T22[T22]
+ L1 --> F1[Force uninhibit signalling link TLAC → HMRT]
+ F1 --> S13[Start T13]
+ R1 --> U1[Uninhibit signalling link TLAC → HMRT]
+ U1 --> S12[Start T12]
+ S13 --> End([Available])
+ S12 --> End
+ T23 --> End
+ T22 --> End
+ T1159210-94/d067
+
+```
+
+Flowchart for 'Available' link state management. It starts with 'Available' and branches into four paths: Local inhibit test (HMDT → TLAC), Remote inhibit test (HMDT → TLAC), T23, and T22. The first two paths lead to 'Force uninhibit signalling link (TLAC → HMRT)' and 'Start T13' or 'Uninhibit signalling link (TLAC → HMRT)' and 'Start T12' respectively. All paths converge to a final 'Available' state. Reference T1159210-94/d067.
+
+**Figure 28/Q.704 (sheet 14 of 18) – Signalling traffic management; link availability control (TLAC)**
+
+
+
+```
+
+graph TD
+ Start([Unavailable]) --> L1[Local inhibit test HMDT → TLAC]
+ Start --> R1[Remote inhibit test HMDT → TLAC]
+ Start --> T22[T22]
+ Start --> T23[T23]
+ L1 --> D1{Link remotely inhibited?}
+ D1 -- No --> End([Unavailable])
+ D1 -- Yes --> F1[Force uninhibit signalling link TLAC → HMRT]
+ F1 --> S13[Start T13]
+ S13 --> End
+ R1 --> D2{Link locally inhibited?}
+ D2 -- No --> End
+ D2 -- Yes --> U1[Uninhibit signalling link TLAC → HMRT]
+ U1 --> S12[Start T12]
+ S12 --> End
+ T22 --> D3{Link locally inhibited?}
+ D3 -- No --> D4{Link remotely inhibited?}
+ D3 -- Yes --> L2[Local inhibit test TLAC → HMRT]
+ L2 --> S22[Start T22]
+ S22 --> End
+ D4 -- No --> End
+ D4 -- Yes --> R2[Remote inhibit test TLAC → HMRT]
+ R2 --> S23[Start T23]
+ S23 --> End
+ T1159220-94/d 068
+
+```
+
+Flowchart for 'Unavailable' link state management. It starts with 'Unavailable' and branches into four paths: Local inhibit test (HMDT → TLAC), Remote inhibit test (HMDT → TLAC), T22, and T23. Each path includes decision diamonds for 'Link remotely inhibited?' or 'Link locally inhibited?'. Depending on the answers, it leads to actions like 'Force uninhibit signalling link (TLAC → HMRT)', 'Start T13', 'Uninhibit signalling link (TLAC → HMRT)', 'Start T12', 'Local inhibit test (TLAC → HMRT)', 'Start T22', 'Remote inhibit test (TLAC → HMRT)', or 'Start T23'. All paths converge to a final 'Unavailable' state. Reference T1159220-94/d 068.
+
+**Figure 28/Q.704 (sheet 15 of 18) – Signalling traffic management; link availability control (TLAC)**
+
+
+
+The diagram consists of two flowcharts, one for the 'Available' state and one for the 'Unavailable' state.
+
+**Available State Flowchart:**
+
+- Starts with a connector 'Available'.
+- Branches into two parallel paths:
+ - 'Restart begins' followed by 'TPRC→TLAC'.
+ - 'Adjacent SP restarting' followed by 'TSRC→TLAC'.
+- Both paths converge to a single sequence:
+ - 'Cancel all marks'.
+ - 'Mark link unavailable'.
+ - Connector 'SP restarting'.
+- A note with a dashed line pointing to the 'Mark link unavailable' step states: "Only for those links in the direct linkset to the adjacent, restarting SP".
+
+**Unavailable State Flowchart:**
+
+- Starts with a connector 'Unavailable'.
+- Branches into two parallel paths:
+ - 'Restart begins' followed by 'TPRC→TLAC'.
+ - 'Adjacent SP restarting' followed by 'TSRC→TLAC'.
+- Both paths converge to a single sequence:
+ - 'Cancel all marks'.
+ - 'Mark link unavailable'.
+ - Connector 'SP restarting'.
+
+T1142750-92/d069
+
+Flowcharts for 'Available' and 'Unavailable' link states in signalling traffic management. Both follow a similar path: 'Restart begins' or 'Adjacent SP restarting' (with TLAC messages) -> 'Cancel all marks' -> 'Mark link unavailable' -> 'SP restarting'. A note indicates the process applies only to direct linksets to the adjacent restarting SP.
+
+Figure 28/Q.704 (sheet 16 of 18) – Signalling traffic management; link availability control (TLAC)
+
+
+
+```
+
+graph TD
+ Start([SP restarting]) --> SLF[Signalling link failed
+LSAC→TLAC]
+ Start --> RPO[Remote processor outage
+LSAC→TLAC]
+ Start --> ASR[Adjacent SP restarted
+TSRC→TLAC]
+ Start --> RE[Restart ends
+TPRC→TLAC]
+
+ SLF --> MF[Mark failed]
+ RPO --> MRB[Mark Remote blocked]
+
+ MF --> MLU[Mark link unavailable]
+ MRB --> MLU
+
+ MLU --> SLU1[Signalling link unavailable
+TLAC→TSRC]
+ SLU1 --> SLU2[Signalling link unavailable
+TLAC→TCOC]
+ SLU2 --> SLU3[Signalling link unavailable
+TLAC→TPRC]
+ SLU3 --> End([SP restarting])
+
+ ASR --> U1{Unavailable?}
+ U1 -- No --> A1([Available])
+ U1 -- Yes --> U2([Unavailable])
+
+ RE --> U3{Unavailable?}
+ U3 -- No --> A2([Available])
+ U3 -- Yes --> U2
+
+```
+
+T1159230-94/d070
+
+Flowchart for Signalling traffic management; link availability control (TLAC). The process starts with 'SP restarting' and branches into four main paths: 'Signalling link failed' (LSAC→TLAC), 'Remote processor outage' (LSAC→TLAC), 'Adjacent SP restarted' (TSRC→TLAC), and 'Restart ends' (TPRC→TLAC). The first two paths lead to marking the link as failed or blocked, then unavailable to TSRC, TCOC, and TPRC, returning to 'SP restarting'. The third path leads to an 'Unavailable?' decision; if 'No', it's 'Available'; if 'Yes', it's 'Unavailable'. The fourth path leads to another 'Unavailable?' decision; if 'No', it's 'Available'; if 'Yes', it's 'Unavailable'. A reference code T1159230-94/d070 is shown at the bottom right.
+
+**Figure 28/Q.704 (sheet 17 of 18) – Signalling traffic management;
+link availability control (TLAC)**
+
+
+
+```
+
+graph TD
+ Start1([SP restarting]) --> Branch1(( ))
+ Branch1 --> Path1[Signalling link in service LSAC→TLAC]
+ Branch1 --> Path2[Remote processor recovered LSAC→TLAC]
+ Branch1 --> Path3[Link in service at level 2 LSAC→TLAC]
+ Path1 --> C1[Cancel failed]
+ Path2 --> C2[Cancel Remote blocked]
+ Path3 --> C3[Link in service at level 2 TLAC→TSRC]
+ C1 --> C4[Cancel link unavailable]
+ C2 --> C4
+ C4 --> C5[Signalling link available TLAC→TSRC]
+ C5 --> C6[Signalling link unavailable TLAC→TPRC]
+ C6 --> End1([SP restarting])
+ C3 --> End2([SP restarting])
+ T1142760-92/d071
+
+```
+
+Flowchart for Signalling traffic management; link availability control (TLAC). The process starts with 'SP restarting' and branches into three parallel paths based on the state of a signalling link, remote processor, or level 2 link. The left path handles 'Signalling link in service LSAC→TLAC' via 'Cancel failed' to 'Cancel link unavailable', then checks for 'Signalling link available' (TLAC→TSRC) or 'Signalling link unavailable' (TLAC→TPRC) before returning to 'SP restarting'. The middle path handles 'Remote processor recovered LSAC→TLAC' via 'Cancel Remote blocked'. The right path handles 'Link in service at level 2 LSAC→TLAC' via 'Link in service at level 2 TLAC→TSRC' to 'SP restarting'. A reference code T1142760-92/d071 is present.
+
+**Figure 28/Q.704 (sheet 18 of 18) – Signalling traffic management; link availability control (TLAC)**
+
+
+
+```
+
+ graph TD
+ Idle1([Idle])
+
+ %% Entry Points
+ RestartBegins[Restart begins
+TPRC → TSRC]
+ TrafficRestart[Traffic restart allowed
+TPRC → TSRC]
+ SendingStatus[Sending status phase
+TPRC → TSRC]
+ T21_Start{{T21}}
+
+ Idle1 --- RestartBegins
+ Idle1 --- TrafficRestart
+ Idle1 --- SendingStatus
+ Idle1 --- T21_Start
+
+ %% Restart Begins Path
+ RestartBegins --> C4((4))
+ C4 --> MarkRoutes[Mark all routes available]
+ MarkRoutes --> CancelInhibit[Cancel all local/remote inhibit requests]
+ CancelInhibit --> CancelLinks[Cancel inhibited links]
+ CancelLinks --> Idle2([Idle])
+
+ %% Traffic Restart Path
+ TrafficRestart --> FromAdj{From an adjacent SP restarting?}
+ FromAdj -- Yes --> SendingPhase{Sending phase finished?}
+ FromAdj -- No --> STP{STP function?}
+
+ STP -- No --> C1((1))
+ STP -- Yes --> AnyDest{Any destination inaccessible?}
+
+ AnyDest -- No --> Idle3([Idle])
+ AnyDest -- Yes --> SelectDest[Select one of the inaccessible destinations]
+ SelectDest --> SendTFP[Send transfer prohibited message
+TSRC → RTPC]
+ SendTFP --> LastDest{Last destination?}
+ LastDest -- No --> SelectDest
+ LastDest -- Yes --> C2((2))
+
+ %% Sending Phase Path
+ SendingPhase -- No --> ForEach[For each adjacent restarting SP]
+ SendingPhase -- Yes --> CancelSend[Cancel sending phase finished]
+
+ ForEach -.-> MarkTRA[Mark TRA received]
+ MarkTRA --> Idle4([Idle])
+
+ CancelSend --> StopT21[Stop T21]
+ StopT21 --> CancelAdj[Cancel adjacent SP restarting]
+ CancelAdj --> AdjRestarted1[Adjacent SP restarted
+TSRC → TLAC]
+ AdjRestarted1 --> AdjRestarted2[Adjacent SP restarted
+TSRC → RSRT]
+ AdjRestarted2 --> C3((3))
+
+ %% Sending Status Path
+ SendingStatus --> Wait05([Wait 05])
+
+ %% T21 Path
+ T21_Start --> C5((5))
+
+ %% Other Connectors
+ UnexpectedTRA[Unexpected TRA] -.-> FromAdj
+ C6((6)) --> StopT21
+ C9((9)) -.-> Idle4
+ C5_1((5)) -- 1 --> AdjRestarted1
+ C2_2((2)) -- 2 --> C2
+
+```
+
+Flowchart for Signalling traffic management; signalling routing control (TSRC).
+
+**Figure 29/Q.704 (sheet 1 of 21) – Signalling traffic management;
+signalling routing control (TSRC)**
+
+
+
+The flowchart illustrates the signalling traffic management and signalling routing control (TSRC) process. It is divided into two main vertical paths.
+
+**Left Path:**
+
+- Starts at a circle labeled '2' with a '1' next to it.
+- An arrow points down to a dashed diamond decision: 'Any destination restricted?'.
+- If 'No', the path goes left and then down to a circle labeled '1' with a '1' next to it.
+- If 'Yes', the path goes down to a dashed rectangle: 'Select one of the restricted destinations'.
+- From there, it goes down to a dashed parallelogram: 'Send transfer restricted message TSRC → RTRC'.
+- Then to a dashed diamond decision: 'Last destination?'.
+- If 'No', it loops back up to the 'Select one of the restricted destinations' box.
+- If 'Yes', it goes down to a circle labeled '1' with a '1' next to it.
+- From this circle, it goes down to a parallelogram: 'Traffic restart allowed TSRC → HMRT'.
+- Finally, it goes down to an oval labeled 'Idle'.
+
+**Right Path:**
+
+- Starts at a circle labeled '3' with a '1' next to it.
+- An arrow points down to a diamond decision: 'Any unavailable or restricted route?'.
+- If 'No', the path goes left and then down to a circle labeled '1' with a '1' next to it.
+- If 'Yes', the path goes down to a rectangle: 'Select one of these destinations'.
+- Then to a parallelogram: 'Start route set test TSRC → RSRT'.
+- Then to a diamond decision: 'Last destination?'.
+- If 'No', it loops back up to the 'Select one of these destinations' box.
+- If 'Yes', it goes down to a diamond decision: 'STP function?'.
+- If 'No', the path goes left and then down to a circle labeled '1' with a '1' next to it.
+- If 'Yes', it goes down to a parallelogram: 'Destination accessible TSRC → RTAC'.
+- From this parallelogram, a dashed line points right to the text 'Concerning the adjacent SP'.
+- Below the parallelogram, the path goes down to another parallelogram: 'Destination accessible TSRC → TSFC'.
+- Finally, it goes down to a circle labeled '3' with a '7' next to it.
+
+On the far left, there are three labels: '2, 3' at the top, '1' in the middle, and '7' at the bottom.
+
+Flowchart for signalling traffic management and signalling routing control (TSRC).
+
+T1142780-92/d73
+
+**Figure 29/Q.704 (sheet 2 of 21) – Signalling traffic management; signalling routing control (TSRC)**
+
+
+
+```
+
+ graph TD
+ Start((7)) --> D1{Any destination becoming available?}
+ D1 -- No --> D10{Last destination?}
+ D1 -- Yes --> P1[Select one destination]
+ P1 --> P2{{Destination accessible TSRC → TSFC}}
+ P2 -- No --> D2{STP function?}
+ D2 -- Yes --> P3{{Destination accessible TSRC → RTAC}}
+ P3 --> D3{Adjacent SP becoming available?}
+ D3 -- Yes --> D1
+ D3 -- No --> D10
+ D10 -- No --> D1
+ D10 -- Yes --> End([Idle])
+
+ D10 -- No --> D4{Any destination inaccessible?}
+ D4 -- No --> D4
+ D4 -- Yes --> P4[Select one of the inaccessible destinations]
+ P4 --> P5{{Send transfer prohibited message TSRC → RTPC}}
+ P5 --> D5{Last destination?}
+ D5 -- No --> D4
+ D5 -- Yes --> D6{Any destination restricted?}
+ D6 -- No --> D6
+ D6 -- Yes --> P6[Select one of the restricted destinations]
+ P6 --> P7{{Send transfer restricted message TSRC → RTRC}}
+ P7 --> D7{Last destination?}
+ D7 -- No --> D6
+ D7 -- Yes --> D10
+
+ Note1[Via the adjacent SP restarted?] -.-> D1
+ Note2[To the newly available SP] -.-> P5
+ Note3[To the newly available SP] -.-> P7
+
+```
+
+The flowchart illustrates the signalling routing control (TSRC) process. It begins at connector 7, leading to a decision: 'Any destination becoming available?'. If 'No', it proceeds to 'Last destination?'. If 'Yes', it selects a destination and checks if it's accessible via TSRC → TSFC. If not accessible, it checks the STP function. If the STP function is 'Yes', it checks if the destination is accessible via TSRC → RTAC. If the adjacent SP becomes available, it loops back to the initial availability check. If not, it proceeds to 'Last destination?'. If 'Last destination?' is 'No', it loops back to the initial availability check. If 'Yes', the process ends at 'Idle'. If 'Last destination?' is 'No' from the initial check, it proceeds to 'Any destination inaccessible?'. If 'Yes', it selects an inaccessible destination and sends a transfer prohibited message (TSRC → RTPC). If this was the last destination, it checks if any destination is restricted. If 'Yes', it selects a restricted destination and sends a transfer restricted message (TSRC → RTRC). If this was the last restricted destination, it loops back to 'Last destination?'. If 'No' at any point in this section, it loops back to 'Any destination inaccessible?'. A note 'Via the adjacent SP restarted?' points to the initial availability check. Notes 'To the newly available SP' point to the transfer message outputs.
+
+Flowchart for signalling traffic management; signalling routing control (TSRC).
+
+T1142790-92/d74
+
+**Figure 29/Q.704 (sheet 3 of 21) – Signalling traffic management; signalling routing control (TSRC)**
+
+
+
+```
+
+ graph TD
+ Start1([Idle]) --> Entry1{8}
+ Entry1 --> SignallingLinkUnavailable[Signalling link unavailable
+TLAC → TSRC]
+ SignallingLinkUnavailable --> MarkLinkUnavailable[Mark link unavailable]
+ MarkLinkUnavailable --> Emergency1{Emergency?}
+ Emergency1 -- No --> AltLink{Alternative link in linkset?}
+ Emergency1 -- Yes --> EmergencyTSRC[Emergency
+TSRC → LLSC]
+ EmergencyTSRC --> AltLink
+ AltLink -- Yes --> Idle1([Idle])
+ AltLink -- No --> SelectAffected[Select one of affected destinations]
+ SelectAffected --> SPRestarting{SP restarting?}
+ SPRestarting -- No --> Connector10((10))
+ SPRestarting -- Yes --> MarkUnavailable[Mark unavailable?]
+ MarkUnavailable --> LastDestination{Last destination?}
+ LastDestination -- No --> Connector9((9))
+ LastDestination -- Yes --> Connector11_4((11))
+
+ Start2([Idle]) --> AccessibilityRequest[Accessibility data request
+RSRT → TSRC]
+ AccessibilityRequest --> ObtainData[Obtain accessibility data for concerned destination]
+ ObtainData --> AccessibilityData[Accessibility data
+TSRC → RSRT]
+ AccessibilityData --> Idle2([Idle])
+
+ Entry2((8)) --> SignallingLinkAvailable[Signalling link available
+TLAC → TSRC]
+ SignallingLinkAvailable --> MarkLinkAvailable[Mark link available]
+ MarkLinkAvailable --> Emergency2{Emergency?}
+ Emergency2 -- Yes --> OtherLinks{Other links available in linkset?}
+ Emergency2 -- No --> EmergencyCeases[Emergency ceases
+TSRC → LLSC]
+ EmergencyCeases --> OtherLinks
+ OtherLinks -- Yes --> Idle1
+ OtherLinks -- No --> OwnSPRestarting{Own SP restarting?}
+ OwnSPRestarting -- Yes --> Connector12((12))
+ OwnSPRestarting -- No --> StopT11[Stop T11]
+ StopT11 --> Connector12
+
+ LateEvent[May be treated as a late event after T18 expired] -.-> AnyAvailableLinks{Any available links?}
+ Connector11_4_top((11)) --> AnyAvailableLinks
+ AnyAvailableLinks -- Yes --> Idle3([Idle])
+ AnyAvailableLinks -- No --> CancelRestarting[Cancel own SP restarting]
+ CancelRestarting --> StopRestart[Stop restart
+TSRC → TPRC]
+ StopRestart --> Idle3
+
+```
+
+The diagram is a flowchart for signalling routing control (TSRC). It details procedures for signalling link unavailability, accessibility data requests, and signalling link availability. It includes decision points for emergency status, alternative link availability, and SP restarting status. Various timers (T11, T18) and inter-process signals (TLAC, RSRT, LLSC, TPRC) are referenced. Connectors indicate transitions to other parts of the logic (sheets).
+
+Note: Routes via restarting adjacent SPs are considered prohibited.
+
+T1142800-92/d75
+
+**Figure 29/Q.704 (sheet 4 of 21) – Signalling traffic management;
+signalling routing control (TSRC)**
+
+**Recommendation Q.704 (07/96)** 127
+
+8
+
+13
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> L1[Link in service at level 2
+TLAC -> TSRC]
+ L1 --> M1[Mark link in service at level 2]
+ M1 --> D1{Other links in service at level 2?}
+ D1 -- Yes --> D2{Adjacent SP inaccessible?}
+ D1 -- No --> S1[Signalling point restart indication
+TSRC -> TPRC]
+ S1 --> M2[Mark own SP restarting]
+ M2 --> Idle2([Idle])
+ Restart[Restart ends
+TPRC -> TSRC] --> C[Cancel SP restarting]
+ C --> Idle2
+ D2 -- Yes --> C1((8))
+ D2 -- No --> Idle2
+ Note[Prior to the link becoming available, SP at remote end of linkset] -.-> D2
+
+```
+
+Flowchart for signalling traffic management; signalling routing control (TSRC). The process starts at 'Idle', proceeds to 'Link in service at level 2 TLAC -> TSRC', then 'Mark link in service at level 2'. A decision 'Other links in service at level 2?' follows. If 'Yes', it goes to 'Adjacent SP inaccessible?'. If 'No', it goes to 'Signalling point restart indication TSRC -> TPRC', then 'Mark own SP restarting'. Both 'Mark own SP restarting' and 'Cancel SP restarting' lead to the final 'Idle' state. A connector '8' is shown at the top left of the main flow.
+
+T1142810-92/d76
+
+**Figure 29/Q.704 (sheet 5 of 21) – Signalling traffic management; signalling routing control (TSRC)**
+
+
+
+```
+
+graph TD
+ Start1((4, 10
+10)) --> Q1{Alternative link set for destination?}
+ Q1 -- Yes --> Q2{New STP to be used for destination?}
+ Q1 -- No --> Q3{Any links inhibited?}
+ Q3 -- Yes --> P1[Uninhibit signalling link
+TSRC → TLAC]
+ P1 --> P2[Mark route unavailable]
+ Q3 -- No --> P2
+ P2 --> P3[Destination inaccessible
+TSRC → RTPC]
+ P3 --> P4[Destination inaccessible
+TSRC → TSFC]
+ P4 -.-> P5[Destination inaccessible
+TSRC → TRCC]
+ P5 -.-> P6[Stop T11]
+ P6 -.-> P7[Mark destination inaccessible]
+ Q2 -- Yes --> P8[Send transfer prohibited message
+TSRC → RTPC]
+ P8 -.-> P9[To new STP]
+ P8 --> P10[Mark STP in use for destination]
+ P10 --> P11[Mark route unavailable]
+ P11 --> Q4{New STP lower priority?}
+ Q4 -- Yes --> P12[Start T11]
+ P12 -.-> P13[Idle]
+ Q4 -- No --> Q5{New route restricted?}
+ Q5 -- Yes --> P14[Destination restricted
+TSRC → RTRC]
+ Q5 -- No --> P5
+ P14 -.-> P13
+ P7 --> Q6{Last affected destination?}
+ Q6 -- No --> End1((9
+4))
+ Q6 -- Yes --> End2[Idle]
+ Start2((4, 6
+12)) --> P15[Select destination for which linkset may be used]
+ P15 --> Q7{Own SP restarting?}
+ Q7 -- No --> End3((7
+14))
+ Q7 -- Yes --> P16[Mark route available?]
+ P16 --> Q8{Last destination?}
+ Q8 -- No --> End4((6
+12))
+ Q8 -- Yes --> End5[Idle]
+
+```
+
+Flowchart for Signalling traffic management; signalling routing control (TSRC). The process starts at connector 10 (4, 10). It checks for an alternative link set. If none, it checks if any links are inhibited. If inhibited, it un inhibits them and marks the route unavailable. If not inhibited, it marks the route unavailable and sends a destination inaccessible message (TSRC → RTPC). If an alternative link set is found, it checks if a new STP should be used. If yes, it sends a transfer prohibited message (TSRC → RTPC) to the new STP, marks the STP in use, and marks the route unavailable. It then checks if the new STP has lower priority. If yes, it starts T11 and becomes idle. If no, it checks if the new route is restricted. If restricted, it sends a destination restricted message (TSRC → RTRC) and becomes idle. If not restricted, it sends a destination inaccessible message (TSRC → TRCC), stops T11, and marks the destination inaccessible. After these steps, it checks the last affected destination. If not the last, it goes to connector 9 (4). If it was the last, it becomes idle. A separate path starts at connector 12 (4, 6), selecting a destination for which a linkset may be used. It checks if its own SP is restarting. If not, it goes to connector 7 (14). If restarting, it marks the route available and checks the last destination. If not the last, it goes to connector 6 (12). If it was the last, it becomes idle.
+
+Flowchart for Signalling traffic management; signalling routing control (TSRC).
+
+T1142820-92/d77
+
+NOTE – Dashed symbols apply only to the Transfer Restricted option.
+
+**Figure 29/Q.704 (sheet 6 of 21) – Signalling traffic management;
+signalling routing control (TSRC)**
+
+
+
+```
+
+graph TD
+ C14((14)) -- 6, 10 --> D1{Destination
+accessible?}
+ D1 -- Yes --> C15_top((15))
+ D1 -- No --> P1[Destination
+accessible
+TSRC → RTAC]
+ P1 --> P2[Destination
+accessible
+TSRC → TSFC]
+ P2 --> P3[Mark
+destination
+accessible]
+ P3 --> D2{Adjacent SP
+becoming avail-
+able?}
+ D2 -- Yes --> C15_mid((15))
+ D2 -- No --> C16_top((16))
+
+ C16_top -- 7 --> D3{New STP
+to be used for
+destination?}
+ D3 -- Yes --> D4{STP
+function?}
+ D4 -- Yes --> P4[Send transfer
+prohibited
+message
+TSRC → RTPC]
+ P4 --> P5[Mark STP
+in use for
+destination]
+ P5 --> D5{Last
+destination?}
+ D5 -- Yes --> Idle([Idle])
+ D5 -- No --> C12_bot((12))
+ D4 -- No --> P5
+ D3 -- No --> D5
+
+ C15_top -- 7 --> D6{STP
+function?}
+ D6 -- Yes --> D7{Any
+destination
+inaccessible?}
+ D7 -- Yes --> P6[Select one of
+the inaccessible
+destinations]
+ P6 --> P7[Send transfer
+prohibited
+message
+TSRC → RTPC]
+ P7 --> D8{Last
+destination?}
+ D8 -- Yes --> C16_bot((16))
+ D8 -- No --> D7
+ D7 -- No --> D9{Any
+destination
+restricted?}
+ D9 -- Yes --> P8[Select one of
+the restricted
+destinations]
+ P8 --> P9[Send transfer
+restricted
+message
+TSRC → RTBC]
+ P9 --> D10{Last
+destination?}
+ D10 -- Yes --> C16_bot((16))
+ D10 -- No --> D9
+ D9 -- No --> C16_bot
+ D6 -- No --> C12_mid((12))
+
+ C12_mid -- 6 --> D11{STP
+no longer
+used for des-
+tination?}
+ D11 -- Yes --> P10[STP no longer
+used for
+destination
+TSRC → RTAC]
+ P10 --> P11[Mark STP
+not in use for
+destination]
+ P11 --> D12{Destination
+restricted?}
+ D12 -- Yes --> P12[Destination
+accessible
+TSRC → RTAC]
+ P12 --> C16_bot
+ D12 -- No --> C16_bot
+ D11 -- No --> C16_bot
+
+ subgraph Callouts
+ T1[Prior to link or route
+becoming available]
+ T2[After re-routing of
+signalling traffic]
+ T3[To the newly
+available SP]
+ end
+
+```
+
+The flowchart illustrates the signalling routing control (TSRC) process. It begins with connector 14 (labeled 6, 10) leading to a decision 'Destination accessible?'. If 'Yes', it proceeds to connector 15 (labeled 7). If 'No', it goes through a series of steps: 'Destination accessible TSRC → RTAC', 'Destination accessible TSRC → TSFC', and 'Mark destination accessible'. This leads to a decision 'Adjacent SP becoming available?'. If 'Yes', it goes to connector 15 (labeled 7). If 'No', it goes to connector 16 (labeled 7). From connector 16, the path goes to 'New STP to be used for destination?'. If 'Yes', it checks 'STP function?'. If 'Yes', it sends a 'transfer prohibited message TSRC → RTPC', marks 'STP in use for destination', and checks 'Last destination?'. If 'Yes', it ends at 'Idle'. If 'No', it goes to connector 12 (labeled 6). If 'STP function?' is 'No', it goes to connector 16. If 'New STP to be used for destination?' is 'No', it goes to connector 16. From connector 16, there is also a path to 'Destination restricted?'. If 'Yes', it goes to 'Destination accessible TSRC → RTAC'. If 'No', it goes to connector 16. From connector 15 (labeled 7), the path goes to 'STP function?'. If 'Yes', it checks 'Any destination inaccessible?'. If 'Yes', it selects one of the inaccessible destinations, sends a 'transfer prohibited message TSRC → RTPC', and checks 'Last destination?'. If 'Yes', it goes to connector 16 (labeled 7). If 'No', it checks 'Any destination restricted?'. If 'Yes', it selects one of the restricted destinations, sends a 'transfer restricted message TSRC → RTBC', and checks 'Last destination?'. If 'Yes', it goes to connector 16 (labeled 7). If 'No', it goes to connector 16 (labeled 7). If 'STP function?' is 'No', it goes to connector 12 (labeled 6). From connector 12 (labeled 6), the path goes to 'STP no longer used for destination?'. If 'Yes', it goes to 'STP no longer used for destination TSRC → RTAC', marks 'STP not in use for destination', and checks 'Destination restricted?'. If 'Yes', it goes to 'Destination accessible TSRC → RTAC'. If 'No', it goes to connector 16 (labeled 7). If 'STP no longer used for destination?' is 'No', it goes to connector 16 (labeled 7). Callouts indicate transitions 'Prior to link or route becoming available' and 'After re-routing of signalling traffic'. A callout 'To the newly available SP' points to the 'transfer restricted message' step.
+
+Flowchart for Signalling traffic management; signalling routing control (TSRC).
+
+T1142830-92/d78
+
+NOTE – Dashed symbols apply only to the Transfer Restricted option.
+
+**Figure 29/Q.704 (sheet 7 of 21) – Signalling traffic management; signalling routing control (TSRC)**
+
+
+
+```
+
+graph TD
+ Start13((13)) -- 5 --> MarkRestarting[Mark adjacent SP restarting]
+ MarkRestarting --> StartT21{{Start T21}}
+ StartT21 -.- ForAdjacentSP[For that adjacent SP]
+ StartT21 --> MarkRoutes[Mark all routes available]
+ MarkRoutes -.- OnlyDest[Only for the destinations becoming accessible due to the availability of the adjacent SP]
+ MarkRoutes --> TSRC_TPRC[Adjacent SP restarting TSRC → TPRC]
+ TSRC_TPRC --> TSRC_TLAC[Adjacent SP restarting TSRC → TLAC]
+ TSRC_TLAC -.- ForAllLinks[For all links of the linkset]
+ TSRC_TLAC --> TSRC_RSRT[Adjacent SP restarting TSRC → RSRT]
+ TSRC_RSRT --> TSRC_HMRT[Adjacent SP restarting TSRC → HMRT]
+ TSRC_HMRT --> STPFunction{STP function?}
+ STPFunction -- Yes --> Conn17_8((17))
+ STPFunction -- No --> TrafficRestart[Traffic restart allowed TSRC → HMRT]
+ TrafficRestart -.- TRAMessage[The TRA message should be sent after the link is in the available state at level 3]
+ TrafficRestart --> Idle([Idle])
+
+ Start17((17)) -- 8 --> AnyInaccessible{Any inaccessible destination?}
+ AnyInaccessible -- No --> LastDest{Last destination?}
+ AnyInaccessible -- Yes --> SendNonPreventive[Send non-preventive TFPs]
+ SendNonPreventive --> SendingStatus[Sending status information]
+ SendingStatus -.- SendingTFP[The sending of TFP or TFR messages is started after the link is in service at level 3]
+ SendingStatus --> SendStatusInfo[Send status information]
+ SendStatusInfo --> T20Expired{{T20 expired TPRC → TSRC}}
+ SendStatusInfo --> SelectInaccessible[Select one of the inaccessible destinations]
+ SelectInaccessible --> DestStatus{Destination status?}
+ DestStatus -- Inaccessible --> SendTFP[Send transfer prohibited message TSRC → RTPC]
+ DestStatus -- Restricted -.- SendTFR[Send transfer restricted message TSRC → RTRC]
+ SendTFP --> LastDest
+ SendTFR --> LastDest
+ LastDest -- No --> AnyInaccessible
+ LastDest -- Yes --> End18((18))
+ End18 -- 9 --> Exit
+ T20Expired --> End18
+
+ ToAdjacentSP[To the adjacent SP becoming accessible] -.- SendTFP
+ ToAdjacentSP -.- SendTFR
+
+```
+
+8
+
+13
+
+5
+
+17
+
+17
+
+8
+
+17
+
+18
+
+9
+
+T1142840-92/d79
+
+Flowchart for Signalling traffic management; signalling routing control (TSRC). The process starts at connector 13 (labeled 5) and ends at connector 18 (labeled 9). It includes steps for marking adjacent SP restarting, starting T21, marking routes available, and various routing control messages (TPRC, TLAC, RSRT, HMRT). It also includes decision points for STP function, traffic restart allowed, and handling of inaccessible destinations.
+
+**Figure 29/Q.704 (sheet 8 of 21) – Signalling traffic management; signalling routing control (TSRC)**
+
+
+
+8 18
+
+19 10, 11
+
+```
+
+graph TD
+ subgraph Path1 [Path 1: New STP]
+ 18((18)) --> D1{New STP to be used for destination?}
+ D1 -- No --> D2{TRA received?}
+ D1 -- Yes --> B1[Select one of the concerned destinations]
+ B1 --> P1{{Send transfer prohibited message TSRC → RTPC}}
+ P1 -.- T1[Preventive TFP
+Might not be done on highest priority route f.f.s.]
+ P1 --> D4{Last destination?}
+ D4 -- No --> B1
+ D4 -- Yes --> D2
+ D2 -- Yes --> T2[For each adjacent restarting SP]
+ D2 -- No --> B2[Mark sending phase finished]
+ B2 --> I1([Idle])
+ T2 -.- B3[Cancel TRA received]
+ B3 --> C6((6))
+ end
+
+ subgraph Path2 [Path 2: Inaccessible/Restricted]
+ 19((19)) --> D3{Any destination inaccessible?}
+ D3 -- No --> D5{Any destination restricted?}
+ D3 -- Yes --> B4[Select one of the inaccessible destinations]
+ B4 --> P2{{Send transfer prohibited message TSRC → RTPC}}
+ P2 -.- T3[To the newly available SP]
+ P2 --> D6{Last destination?}
+ D6 -- No --> B4
+ D6 -- Yes --> D5
+ D5 -- No --> I2([Idle])
+ D5 -- Yes --> B5[Select one of the restricted destinations]
+ B5 --> P3{{Send transfer restricted message TSRC → RTRC}}
+ P3 -.- T4[To the newly available SP]
+ P3 --> D7{Last destination?}
+ D7 -- No --> B5
+ D7 -- Yes --> I2
+ end
+
+```
+
+f.f.s. For further study
+
+T1142850-92/d80
+
+**Figure 29/Q.704 (sheet 9 of 21) – Signalling traffic management;
+signalling routing control (TSRC)**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> Branch1(( ))
+ Branch1 --> Available{Signalling route available
+RTAC → TSRC}
+ Branch1 --> Unavailable{Signalling route unavailable
+RTPC → TSRC}
+ Available -.-> DueTo[Due to TFA, TFR
+or TRA message]
+ Available --> MarkAvailable[Mark route available]
+ Unavailable --> MarkUnavailable[Mark route unavailable]
+ MarkAvailable --> OwnSPRestarting1{Own SP restarting?}
+ MarkUnavailable --> OwnSPRestarting2{Own SP restarting?}
+ OwnSPRestarting1 -- Yes --> Junction(( ))
+ OwnSPRestarting2 -- Yes --> Junction
+ OwnSPRestarting1 -- No --> AdjacentSPInaccessible{Adjacent SP inaccessible?}
+ OwnSPRestarting2 -- No --> RouteInUse{Route in use?}
+ Junction --> Idle2([Idle])
+ AdjacentSPInaccessible -- No --> Connector14((14 7))
+ AdjacentSPInaccessible -- Yes --> MarkDestinationAccessible[Mark destination accessible]
+ MarkDestinationAccessible -.-> PriorTo[Prior to the route becoming available]
+ MarkDestinationAccessible -.-> AdjacentSPIndirectly[Adjacent SP indirectly accessible]
+ MarkDestinationAccessible --> DestAccessibleTSFC{{Destination accessible
+TSRC → TSFC}}
+ DestAccessibleTSFC --> STPFunction{STP function?}
+ STPFunction -- No --> Idle3([Idle])
+ STPFunction -- Yes --> DestAccessibleRTAC{{Destination accessible
+TSRC → RTAC}}
+ DestAccessibleRTAC --> Connector19((19 9))
+ RouteInUse -- No --> Idle4([Idle])
+ RouteInUse -- Yes --> SignallingRouteUnavailableTSRC{{Signalling route unavailable
+TSRC → TFRC}}
+ SignallingRouteUnavailableTSRC --> ForcedRerouting{{Forced rerouting
+TSRC → RTAC}}
+ ForcedRerouting --> Connector10((6 10))
+
+```
+
+Flowchart for Signalling traffic management; signalling routing control (TSRC). The process starts at 'Idle' and branches based on whether the signalling route is available (RTAC → TSRC) or unavailable (RTPC → TSRC). It includes decision points for 'Own SP restarting?', 'Adjacent SP inaccessible?', 'Route in use?', and 'STP function?'. Actions include 'Mark route available', 'Mark route unavailable', 'Mark destination accessible', 'Destination accessible TSRC → TSFC', 'Destination accessible TSRC → RTAC', and 'Forced rerouting TSRC → RTAC'. The flowchart ends at 'Idle' or connector circles (14, 19, 10).
+
+NOTE – For meanings of abbreviated message names, see Table 1.
+
+**Figure 29/Q.704 (sheet 10 of 21) – Signalling traffic management;
+signalling routing control (TSRC)**
+
+19
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> SR[Signalling route restricted
+RTRC → TSRC]
+ SR --> MR[Mark route restricted]
+ MR --> SP[SP restarting?]
+ SP -- Yes --> Idle2([Idle])
+ SP -- No --> AS[Adjacent SP inaccessible?]
+ AS -- Yes --> MD[Mark destination restricted]
+ AS -- No --> IR[Is route in use?]
+ IR -- Yes --> AL[Alternative linkset for destination?]
+ IR -- No --> STP[STP function?]
+ AL -- Yes --> ALR[Alternate linkset restricted?]
+ ALR -- Yes --> DR1[Destination restricted
+TSRC → RTRC]
+ ALR -- No --> SR2[Signalling route restricted
+TSRC → TCRC]
+ STP -- Yes --> DR2[Destination restricted
+TSRC → RTRC]
+ STP -- No --> DA[Destination accessible
+TSRC → TSFC]
+ DA --> DR2
+ DR1 --> MD2[Mark destination restricted]
+ DR2 --> MD2
+ MD2 --> Idle3([Idle])
+ T1142870-92/d82
+
+```
+
+Flowchart for Signalling traffic management; signalling routing control (TSRC). The process starts at 'Idle', proceeds to 'Signalling route restricted RTRC → TSRC', then 'Mark route restricted'. A decision diamond 'SP restarting?' follows. If 'Yes', it returns to 'Idle'. If 'No', it checks 'Adjacent SP inaccessible?'. If 'Yes', it goes to 'Mark destination restricted'. If 'No', it checks 'Is route in use?'. If 'Yes', it checks 'Alternative linkset for destination?'. If 'Yes', it checks 'Alternate linkset restricted?'. If 'Yes', it goes to 'Destination restricted TSRC → RTRC'. If 'No', it goes to 'Signalling route restricted TSRC → TCRC'. If 'No' to 'Is route in use?', it goes to 'STP function?'. If 'Yes', it goes to 'Destination restricted TSRC → RTRC'. If 'No', it goes to 'Destination accessible TSRC → TSFC'. A callout 'Prior to the route becoming restricted' points to the 'SP restarting?' decision. Another callout 'Traffic can be diverted to an equal priority STP' points to the 'Alternative linkset for destination?' decision. The flowchart ends at 'Idle' with connector 'T1142870-92/d82'.
+
+NOTE – Dashed symbols apply only to the transfer restricted option.
+
+**Figure 29/Q.704 (sheet 11 of 21) – Signalling traffic management; signalling routing control (TSRC)**
+
+20
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> TCOC_Request[/Alternative routing data request TCOC → TSRC/]
+ Idle1 --> TCBC_Request[/Alternative routing data request TCBC → TSRC/]
+ TCOC_Request --> TCOC_Obtain[Obtain alternative routing data]
+ TCBC_Request --> TCBC_Obtain[Obtain alternative routing data]
+ TCOC_Obtain --> TCOC_Data[/Alternative routing data TSRC → TCOC/]
+ TCBC_Obtain --> TCBC_Data[/Alternative routing data TSRC → TCBC/]
+ TCOC_Data --> Wait01_1([Wait 01])
+ TCBC_Data --> Wait02_1([Wait 02])
+ Wait01_1 --> LSDA_Request[/Alternative routing data request LSDA → TSRC/]
+ Wait01_1 --> NotRequired[/Changover not required TCOC → TSRC/]
+ Wait01_1 --> Executed[/Changover executed TCOC → TSRC/]
+ Wait02_1 --> Terminated[/Procedure terminated TCBC → TSRC/]
+ LSDA_Request --> LSDA_Obtain[Obtain alternative routing data]
+ LSDA_Obtain --> LSDA_Data[/Alternative routing data TSRC → LSDA/]
+ LSDA_Data --> Wait01_2([Wait 01])
+ NotRequired --> Idle2([Idle])
+ Executed --> MarkCompleted[Mark changeover completed]
+ MarkCompleted --> Idle2
+ Terminated --> CancelCompleted[Cancel changeover completed]
+ CancelCompleted --> Idle2
+ RSRT_Request[/Accessibility data request RSRT → TSRC/] -.-> Rules[According to rules specified in 4.4]
+ Rules -.-> TCOC_Obtain
+ Rules -.-> TCBC_Obtain
+ SP_Restart[During SP restart the adjacent SP is considered as inaccessible] -.-> Wait01_1
+ SP_Restart -.-> Wait02_1
+ Connector20((20)) -.-> RSRT_Request
+ Connector20 -.-> LSDA_Request
+ Connector21((21)) -.-> Idle2
+
+```
+
+Flowchart for signalling traffic management; signalling routing control (TSRC). The process starts at 'Idle' and branches into two main paths: one for TCOC to TSRC requests and another for TCBC to TSRC requests. Both paths involve obtaining routing data and then waiting. The TCOC path leads to 'Wait 01' and then to a decision point for 'Alternative routing data request LSDA to TSRC', 'Changover not required', or 'Changover executed'. The TCBC path leads to 'Wait 02' and then to a decision point for 'Procedure terminated'. Annotations include 'According to rules specified in 4.4' and 'During SP restart the adjacent SP is considered as inaccessible'. Connector circles 20 and 21 are used to link different sheets.
+
+20
+
+21
+
+**Figure 29/Q.704 (sheet 12 of 21) – Signalling traffic management; signalling routing control (TSRC)**
+
+
+
+```
+
+graph TD
+ Idle([Idle]) --> TFRC_Req[/Alternative routing data request
+TFRC → TSRC/]
+ Idle --> TCRC_Req[/Alternative routing data request
+TCRC → TSRC/]
+ TFRC_Req --> TFRC_Obtain[Obtain alternative routing data]
+ TCRC_Req --> TCRC_Obtain[Obtain alternative routing data]
+ TFRC_Obtain --> TFRC_Return[/Alternative routing data
+TSRC → TFRC/]
+ TCRC_Obtain --> TCRC_Return[/Alternative routing data
+TSRC → TCRC/]
+ TFRC_Return --> Wait03([Wait 03])
+ TCRC_Return --> Wait04([Wait 04])
+ Wait03 --> RTAC_Diag[/Signalling route available
+RTAC → TSRC/]
+ Wait03 --> TFRC_Term[/Procedure terminated
+TFRC → TSRC/]
+ Wait04 --> TCRC_Term[/Procedure terminated
+TCRC → TSRC/]
+ TFRC_Term --> C12_21((12 21))
+ TCRC_Term --> C12_21
+ C12_21 --> Wait01([Wait 01])
+ C12_21 --> Wait02([Wait 02])
+ C12_21 --> Wait03b([Wait 03])
+ C12_21 --> Wait04b([Wait 04])
+ Wait01 --> TPRC_Restart1[/Restart begins
+TPRC → TSRC/]
+ Wait02 --> TPRC_Restart2[/Restart begins
+TPRC → TSRC/]
+ Wait03b --> TPRC_Restart3[/Restart begins
+TPRC → TSRC/]
+ Wait04b --> TPRC_Restart4[/Restart begins
+TPRC → TSRC/]
+ TPRC_Restart1 --> C1_4_1((1 4))
+ TPRC_Restart2 --> C1_4_2((1 4))
+ TPRC_Restart3 --> C1_4_3((1 4))
+ TPRC_Restart4 --> C1_4_4((1 4))
+ T1142890-92/d84[T1142890-92/d84]
+
+```
+
+Flowchart for Signalling traffic management; signalling routing control (TSRC). The diagram shows two main paths starting from an 'Idle' state. The first path involves a request from TFRC to TSRC, obtaining data, and returning it from TSRC to TFRC, leading to 'Wait 03'. The second path involves a request from TCRC to TSRC, obtaining data, and returning it from TSRC to TCRC, leading to 'Wait 04'. Both 'Wait' states lead to a 'Procedure terminated' message back to the requester. A 'Signalling route available' message from RTAC to TSRC is also shown. A connector '12 21' links the top section to the bottom section. The bottom section shows four parallel 'Wait' states (01, 02, 03, 04) each leading to a 'Restart begins' message from TPRC to TSRC, ending at connector '1 4'. A reference code T1142890-92/d84 is present near the bottom right.
+
+21
+
+4
+
+**Figure 29/Q.704 (sheet 13 of 21) – Signalling traffic management;
+signalling routing control (TSRC)**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> LinkStatus{Link congestion status}
+ LinkStatus -.-> ID[From implementation dependent function]
+ LinkStatus --> AlternateLinkset{Alternate linkset in use?}
+ AlternateLinkset -- No --> DestAffected[Determine destinations affected]
+ DestAffected --> DestCongStatus[Destination(s) congestion status TSRC → TSFC]
+ AlternateLinkset -- Yes --> DestRestricted{Destination restricted?}
+ DestRestricted -- Yes --> StopT11[Stop T11]
+ StopT11 --> DestRestRTRC[Destination restricted TSRC → RTRC]
+ DestRestRTRC --> MarkDestRest[Mark destination restricted]
+ MarkDestRest --> Idle2([Idle])
+ DestCongStatus --> Idle2
+ LinkStatus -.-> AccReq[Accessibility data request TRCC → TSRC]
+ AccReq -.-> ObtainData[Obtain accessibility data for concerned destination]
+ ObtainData -.-> AccData[Accessibility data TSRC → TRCC]
+ Note1[Routes via restarting adjacent SPs are considered prohibited] -.-> AccData
+ AccData --> Idle2
+ T115924094d85[T1159240-94/d85]
+
+```
+
+Flowchart for Signalling traffic management; signalling routing control (TSRC). The process starts at an 'Idle' state and branches based on 'Link congestion status'. One path involves 'Accessibility data request TRCC → TSRC' and 'Obtain accessibility data for concerned destination', leading to 'Accessibility data TSRC → TRCC'. A note indicates that routes via restarting adjacent SPs are considered prohibited. The other path from 'Link congestion status' (linked to an implementation-dependent function) leads to a decision 'Alternate linkset in use?'. If 'No', it goes to 'Determine destinations affected' and then 'Destination(s) congestion status TSRC → TSFC'. If 'Yes', it leads to 'Destination restricted?'. If 'Yes' to 'Destination restricted?', it goes to 'Stop T11', 'Destination restricted TSRC → RTRC', and 'Mark destination restricted'. Both main paths lead to a final 'Idle' state. A label T1159240-94/d85 is present near the bottom right.
+
+NOTE – Dotted symbols apply only to the multiple congestion states option; dashed symbols apply only to the transfer restricted option.
+
+**Figure 29/Q.704 (sheet 14 of 21) – Signalling traffic management; signalling routing control (TSRC)**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> Inhibit1{Local inhibit request
+TLAC → TSRC}
+ Idle1 --> Inhibit2{Remote inhibit request
+TLAC → TSRC}
+ Idle1 --> Inhibit3{Link inhibited
+TLAC → TSRC}
+ Idle1 --> Inhibit4{Cancel link inhibited
+TLAC → TSRC}
+ Idle1 --> Inhibit5{Uninhibit request
+TLAC → TSRC}
+
+ Inhibit1 --> MarkLocal[Mark local inhibit request]
+ Inhibit2 --> MarkRemote[Mark remote inhibit request]
+ Inhibit3 --> MarkLink[Mark link inhibited]
+ Inhibit4 --> CancelLink[Cancel link inhibited]
+ Inhibit5 --> ObtainData[Obtain accessibility data for remote SPs]
+
+ MarkLocal --> Connector22((22))
+ MarkRemote --> Connector22
+ MarkLink --> Idle2([Idle])
+ CancelLink --> Connector22
+ ObtainData --> SPAccessible{SP accessible?}
+
+ SPAccessible -- No --> UninhibitNotPossible[Uninhibiting not possible
+TSRC → TLAC]
+ SPAccessible -- Yes --> UninhibitPossible[Uninhibiting possible
+TSRC → TLAC]
+
+ UninhibitNotPossible --> Connector22
+ UninhibitPossible --> Idle2
+
+ T1142900-92/d86
+
+```
+
+Flowchart for signalling traffic management; signalling routing control (TSRC). The process starts at an 'Idle' state and branches into five parallel paths based on input requests: Local inhibit, Remote inhibit, Link inhibited, Cancel link inhibited, and Uninhibit. The Local and Remote inhibit paths lead to marking the request and then to connector 22. The Link inhibited path leads to marking the link inhibited and then back to the 'Idle' state. The Cancel link inhibited path leads to cancelling the link inhibited and then to connector 22. The Uninhibit path leads to obtaining accessibility data, then a decision 'SP accessible?'. If 'No', it leads to 'Uninhibiting not possible' and then to connector 22. If 'Yes', it leads to 'Uninhibiting possible' and then back to the 'Idle' state. A reference code T1142900-92/d86 is present.
+
+Figure 29/Q.704 (sheet 15 of 21) – Signalling traffic management; signalling routing control (TSRC)
+
+
+
+```
+
+graph TD
+ Start((22)) --> LinkStatus{Link status available?}
+ LinkStatus -- No --> ObtainData[Obtain accessibility data for remote SP]
+ ObtainData --> SPAccessible{SP accessible?}
+ SPAccessible -- No --> C23((23))
+ SPAccessible -- Yes --> InhibitRequest1{Inhibit request?}
+ LinkStatus -- Yes --> AltLink{Alternative link in linkset?}
+ AltLink -- No --> C23
+ AltLink -- Yes --> LastDestination{Last destination?}
+ LastDestination -- No --> C23
+ LastDestination -- Yes --> InhibitRequest1
+ InhibitRequest1 -- Local --> LocalInhibitAllowed1[/Local inhibit allowed TSRC -> TLAC/]
+ InhibitRequest1 -- Remote --> RemoteInhibitAllowed1[/Remote inhibit allowed TSRC -> TLAC/]
+ LocalInhibitAllowed1 --> CancelLocal1[Cancel local inhibit request]
+ RemoteInhibitAllowed1 --> CancelRemote1[Cancel remote inhibit request]
+ CancelRemote1 --> MarkLinkInhibited[Mark link inhibited]
+ MarkLinkInhibited --> Idle([Idle])
+ CancelLocal1 --> Idle
+ InhibitRequest1 --> AltLinkset{Alternative linkset for destination?}
+ AltLinkset -- No --> C24((24))
+ C24 --> InhibitRequest2{Inhibit request?}
+ InhibitRequest2 -- Local --> LocalInhibitDenied1[/Local inhibit denied TSRC -> TLAC/]
+ InhibitRequest2 -- Remote --> RemoteInhibitDenied1[/Remote inhibit denied TSRC -> TLAC/]
+ LocalInhibitDenied1 --> CancelLocal2[Cancel local inhibit request]
+ RemoteInhibitDenied1 --> CancelRemote2[Cancel remote inhibit request]
+ CancelLocal2 --> Idle
+ CancelRemote2 --> Idle
+ C23 --> SelectDest[Select one of concerned destinations]
+ SelectDest --> AltLinkset
+ T1142910-92/d87
+
+```
+
+Flowchart for Signalling traffic management; signalling routing control (TSRC). The process starts at connector 22 (line 15) and proceeds through various decision points: 'Link status available?', 'SP accessible?', 'Alternative link in linkset?', 'Alternative linkset for destination?', and 'Last destination?'. It then branches into 'Inhibit request?' (Local/Remote) and subsequent actions like 'Local inhibit allowed TSRC -> TLAC', 'Cancel local inhibit request', 'Mark link inhibited', and finally reaching the 'Idle' state. Connector 23 (line 16) is used as a loopback point.
+
+**Figure 29/Q.704 (sheet 16 of 21) – Signalling traffic management; signalling routing control (TSRC)**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> Decision[From implementation dependent function]
+ Decision --> Congested[Signalling link congested]
+ Decision --> Uncongested[Signalling link uncongested]
+ Decision --> Request[Alternative routing data request
+LSDA → TSRC]
+ Congested --> Dest1[Determine destinations affected]
+ Dest1 --> Mark[Mark destination congested]
+ Uncongested --> Dest2[Determine destinations affected]
+ Dest2 --> Cancel[Cancel destination congested]
+ Request --> Obtain[Obtain alternative routing data]
+ Obtain --> Data[Alternative routing data
+TSRC → LSDA]
+ Mark --> Idle2([Idle])
+ Cancel --> Idle2
+ Data --> Idle2
+ T1159250-94/d88
+
+```
+
+Flowchart for Signalling traffic management; signalling routing control (TSRC). The process starts at an 'Idle' state, branches based on a 'From implementation dependent function' into three paths: 'Signalling link congested' (leading to 'Determine destinations affected' and 'Mark destination congested'), 'Signalling link uncongested' (leading to 'Determine destinations affected' and 'Cancel destination congested'), and 'Alternative routing data request LSDA -> TSRC' (leading to 'Obtain alternative routing data' and 'Alternative routing data TSRC -> LSDA'). All three paths converge back to an 'Idle' state. A label 'T1159250-94/d88' is present near the bottom right.
+
+NOTE – Delete hatched symbols when using multiple congestion states option.
+
+**Figure 29/Q.704 (sheet 17 of 21) – Signalling traffic management;
+signalling routing control (TSRC)**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> T11[/T11/]
+ T11 --> Select[Select an affected destination]
+ Select --> Mark[Mark destination restricted]
+ Mark --> Dest[Destination restricted TSRC -> RTRC]
+ Dest --> Last{Last destination?}
+ Last -- No --> Select
+ Last -- Yes --> Idle2([Idle])
+
+```
+
+After link set failure, delay marking destination(s) restricted
+
+T1159260-94/d89
+
+Flowchart for signalling traffic management; signalling routing control (TSRC). The process starts at an 'Idle' state, followed by a delay 'T11'. It then enters a loop: 'Select an affected destination' -> 'Mark destination restricted' -> 'Destination restricted TSRC -> RTRC' -> 'Last destination?'. If 'No', it loops back to 'Select an affected destination'. If 'Yes', it returns to the 'Idle' state. A note indicates that after a link set failure, there is a delay in marking destination(s) restricted.
+
+NOTE – Dashed symbols apply only to the transfer restricted option.
+
+**Figure 29/Q.704 (sheet 18 of 21) – Signalling traffic management; signalling routing control (TSRC)**
+
+26
+
+27
+25
+
+
+
+```
+
+graph TD
+ W1([Wait 05]) --> S1{Signalling route available
+RTAC → TSRC}
+ W1 --> S2{Signalling route unavailable
+RTPC → TSRC}
+ W1 --> S3{Signalling route restricted
+RTRC → TSRC}
+ S1 --> A1[Signalling route available]
+ S2 --> A2[Signalling route available]
+ S3 --> A3[Signalling route available]
+
+ W2([Wait 05]) --> S4{Signalling link available
+TLAC → TSRC}
+ W2 --> S5{Signalling link unavailable
+TLAC → TSRC}
+ S4 --> A4[Signalling link available]
+ S5 --> A5[Signalling link available]
+
+ W3([Wait 05]) --> S6{Restart ends
+TPRC → TSRC}
+ W3 --> S7{Send status
+TPRC → TSRC}
+ S6 --> C26((26))
+ C26 --- L26[21]
+ S7 --> D{STP function?}
+ D -- No --> C27((27))
+ C27 --- L27[21]
+ D -- Yes --> C25((25))
+ C25 --- L25[20]
+ D -- Yes --> T[Send all TFPs (and TFRs), including preventive TFPs]
+
+```
+
+Flowchart for Signalling traffic management; signalling routing control (TSRC). The diagram consists of three main vertical sections, each starting with a 'Wait 05' oval. The first section handles route availability (RTAC, RTPC, RTRC). The second section handles link availability (TLAC). The third section handles restart and status sending (TPRC), followed by an STP function decision leading to either connector 27 or connector 25 (with a TFP/TFR action).
+
+T1142920-92/d90
+
+**Figure 29/Q.704 (sheet 19 of 21) – Signalling traffic management; signalling routing control (TSRC)**
+
+25
+
+28
+
+28
+
+
+
+```
+
+graph TD
+ Start((19 25)) --> AllAcc{All destinations fully accessible?}
+ AllAcc -- Yes --> End1((28 21))
+ AllAcc -- No --> Send1{{Send status information}}
+ Send1 --> Send2{{Sending status information}}
+ Send2 --> Send3{{Send status information}}
+ Send3 --> Select[Select one of the destinations not fully accessible]
+ Select --> DestStatus{Destination status?}
+ DestStatus -- Inaccessible --> DirectLink{Only if direct linkset is available}
+ DirectLink -- Yes --> InaccMsg{{Destination inaccessible TSRC->RTPC}}
+ DestStatus -- Restricted --> RestMsg{{Destination restricted TSRC->RTRC}}
+ InaccMsg --> LastDest{Last destination?}
+ RestMsg --> LastDest
+ LastDest -- No --> Send3
+ LastDest -- Yes --> End2((28 21))
+ T20Exp{{T20 expired TPRC->TSRC}} --> LastDest
+
+```
+
+Flowchart for signalling traffic management; signalling routing control (TSRC). The process starts at connector 19 (25), checks if all destinations are fully accessible. If yes, it goes to connector 28 (21). If no, it sends status information, then enters a loop: sending status information, sending status information, selecting a destination not fully accessible, checking destination status. If inaccessible, it checks if a direct linkset is available. If yes, it sends 'Destination inaccessible TSRC->RTPC'. If no, it checks if it's the last destination. If yes, it goes to connector 28 (21). If no, it loops back to 'Send status information'. If the status is 'Restricted', it sends 'Destination restricted TSRC->RTRC'. A 'T20 expired TPRC->TSRC' message also leads to the 'Last destination?' check.
+
+T1142930-92/d91
+
+**Figure 29/Q.704 (sheet 20 of 21) – Signalling traffic management; signalling routing control (TSRC)**
+
+
+
+```
+
+graph TD
+ subgraph LeftFlow [ ]
+ direction TB
+ L20((20)) --> L28((28))
+ L28 --> L1{New STP to be used for destination?}
+ L1 -- No --> L19((19))
+ L1 -- Yes --> L2[Select one of the concerned destinations]
+ L2 --> L3{{Send transfer prohibited message TSRC->RTPC}}
+ L3 --> L4{Last destination?}
+ L4 -- No --> L19
+ L4 -- Yes --> L5{{Status sent TSRC->TPRC}}
+ L5 --> L6([Wait 05])
+ end
+
+ subgraph RightFlow [ ]
+ direction TB
+ R19((19)) --> R26((26))
+ R26 --> R1[Select one of the accessible adjacent destinations]
+ R1 --> R2{{Traffic restart allowed TSRC->HMRT}}
+ R2 --> R3{Last destination?}
+ R3 -- No --> R1
+ R3 -- Yes --> R4[Cancel SP restarting]
+ R4 --> R5{Any route unavailable or restricted?}
+ R5 -- No --> R19
+ R5 -- Yes --> R6[Select one of the concerned destinations]
+ R6 --> R7{{Start route set test TSRC->RSRT}}
+ R7 --> R8{Last route?}
+ R8 -- No --> R6
+ R8 -- Yes --> R9([Idle])
+ end
+
+ L19 --> R19
+ L27((27)) --> R19
+
+ Note1[Sending of preventive TFP messages may come after T20 expires] -.-> L1
+ Note2[Only if direct linkset is available] -.-> L3
+ Note3[Might not be done on highest priority route (f.f.s.)] -.-> L3
+ Note4[Only if direct linkset is available] -.-> R2
+
+```
+
+Flowchart for Signalling traffic management; signalling routing control (TSRC). The diagram consists of two main vertical flows. The left flow starts at connector 20/28, proceeds to a decision 'New STP to be used for destination?'. If 'No', it goes to connector 19/27. If 'Yes', it goes to 'Select one of the concerned destinations', then 'Send transfer prohibited message TSRC->RTPC' (with notes: 'Only if direct linkset is available' and 'Might not be done on highest priority route (f.f.s.)'). This is followed by 'Last destination?' decision. If 'No', it goes to connector 19/27. If 'Yes', it goes to 'Status sent TSRC->TPRC', then 'Wait 05'. The right flow starts at connector 19/26, goes to 'Select one of the accessible adjacent destinations', then 'Traffic restart allowed TSRC->HMRT' (with note: 'Only if direct linkset is available'). This is followed by 'Last destination?' decision. If 'No', it loops back to the start of the right flow. If 'Yes', it goes to 'Cancel SP restarting', then 'Any route unavailable or restricted?' decision. If 'No', it goes to connector 19/27. If 'Yes', it goes to 'Select one of the concerned destinations', then 'Start route set test TSRC->RSRT', then 'Last route?' decision. If 'No', it loops back to the start of the right flow. If 'Yes', it goes to 'Idle'. A note 'Sending of preventive TFP messages may come after T20 expires' is near the top left. Connector 27 is linked to connector 19.
+
+f.f.s. For further study
+
+**Figure 29/Q.704 (sheet 21 of 21) – Signalling traffic management; signalling routing control (TSRC)**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> DCS[Destination congestion status RTCC→TRCC]
+ Idle1 --> DCS_Dec[Decrement destination congestion status RCAT→TRCC]
+ Idle1 --> AD[Accessibility data TSRC→TRCC]
+ Idle1 --> DI[Destination inaccessible TSRC→TRCC]
+ DCS --> SDCS[Store destination congestion status]
+ DCS_Dec --> Idle2([Idle])
+ AD --> Idle2
+ DI --> Idle2
+ SDCS --> ADReq[Accessibility data request TRCC→TSRC]
+ ADReq --> Wait01([Wait 01])
+ Wait01 --> AD2[Accessibility data TSRC→TRCC]
+ Wait01 --> DCS2[Destination congestion status RTCC→TRCC]
+ Wait01 --> DI2[Destination inaccessible TSRC→TRCC]
+ AD2 --> IsAcc[Is destination accessible?]
+ IsAcc -- Yes --> UpdateDCS[Update destination congestion status]
+ IsAcc -- No --> Idle3([Idle])
+ UpdateDCS --> DCS3[Destination congestion status TRCC→TSFC]
+ DCS3 --> StartT15[Start T15]
+ StartT15 --> Wait02([Wait 02])
+ DCS2 --> NewCong[New congestion status greater?]
+ NewCong -- Yes --> SDCS2[Store destination congestion status]
+ SDCS2 --> Wait01
+ NewCong -- No --> Idle3
+ DI2 --> Idle3
+
+```
+
+NOTE – Dotted symbols apply only to the Multiple Congestion States option.
+
+T1188770-97
+
+Flowchart for signalling traffic management; signalling route set congestion control (TRCC). The process starts at 'Idle' and branches into four options: 'Destination congestion status RTCC→TRCC', 'Decrement destination congestion status RCAT→TRCC', 'Accessibility data TSRC→TRCC', and 'Destination inaccessible TSRC→TRCC'. The first three lead to a central 'Idle' state. The first option also leads to 'Store destination congestion status', then 'Accessibility data request TRCC→TSRC', then 'Wait 01'. From 'Wait 01', it branches into 'Accessibility data TSRC→TRCC', 'Destination congestion status RTCC→TRCC', and 'Destination inaccessible TSRC→TRCC'. The first leads to 'Is destination accessible?'. If 'Yes', it goes to 'Update destination congestion status', then 'Destination congestion status TRCC→TSFC', then 'Start T15', then 'Wait 02'. If 'No', it goes to 'Idle'. The second option from 'Wait 01' leads to 'New congestion status greater?'. If 'Yes', it goes to 'Store destination congestion status', then 'Wait 01'. If 'No', it goes to 'Idle'. The third option from 'Wait 01' leads to 'Idle'. A connector circle on the left contains '1' and '3'. A note states 'NOTE – Dotted symbols apply only to the Multiple Congestion States option.' and a code 'T1188770-97' is present.
+
+**Figure 29a/Q.704 (sheet 1 of 3) – Signalling traffic management; signalling route set congestion control (TRCC)**
+
+
+
+```
+
+graph TD
+ Start([Wait 02]) --> Branch1[Destination congestion status RTCC→TRCC]
+ Start --> Branch2[T15]
+ Start --> Branch3[Destination inaccessible TSRC→TRCC]
+ Start --> Branch4[Decrement destination congestion status RCAT→TRCC]
+
+ Branch1 --> Decision1{Is new congestion status greater?}
+ Decision1 -- Yes --> Update1[Update destination congestion status]
+ Update1 --> Output1[Destination congestion status TRCC→TSFC]
+ Output1 --> Reset1[Reset T15]
+ Reset1 --> End1([Wait 02])
+
+ Decision1 -- No --> End1
+
+ Branch2 --> StartTest[Start congestion test TRCC→RCAT]
+ StartTest --> End2([Wait 03])
+
+ Branch3 --> Update2[Update destination congestion status equal to zero]
+ Update2 --> StopT15[Stop T15]
+ StopT15 --> Idle[Idle]
+
+ Branch4 --> End3([Wait 02])
+
+ Connector2((2)) -.-> Branch2
+ Connector3((3)) -.-> Decision1
+
+```
+
+Flowchart for signalling traffic management; signalling route set congestion control (TRCC). The process starts at 'Wait 02' and branches into four main paths: 1) 'Destination congestion status RTCC→TRCC' leads to a decision 'Is new congestion status greater?'. If 'Yes', it proceeds to 'Update destination congestion status', then 'Destination congestion status TRCC→TSFC', then 'Reset T15', and finally back to 'Wait 02'. If 'No', it bypasses these steps and goes directly to 'Wait 02'. 2) A path labeled 'T15' leads to 'Start congestion test TRCC→RCAT', which then leads to 'Wait 03'. 3) A path labeled 'Destination inaccessible TSRC→TRCC' leads to 'Update destination congestion status equal to zero', then 'Stop T15', and finally to 'Idle'. 4) A path labeled 'Decrement destination congestion status RCAT→TRCC' leads directly to 'Wait 02'. There are connector circles labeled '2' and '3' with arrows pointing to the 'T15' and 'Is new congestion status greater?' decision paths respectively. A vertical line on the left is labeled '2'. A small text 'TI188780-97' is in the bottom right of the diagram area.
+
+NOTE – Dotted symbols apply only to the Multiple Congestion States option.
+
+**Figure 29a/Q.704 (sheet 2 of 3) – Signalling traffic management; signalling route set congestion control (TRCC)**
+
+
+
+```
+
+graph TD
+ Start([Wait 03]) --> Branch(( ))
+ Branch --> Path1[/Destination congestion status RTCC→TRCC/]
+ Branch --> Path2[/Decrement destination congestion status RCAT→TRCC/]
+ Branch --> Path3[/Destination inaccessible TSRC→TRCC/]
+ Path1 --> Stop1[/Stop congestion test TRCC→RCAT/]
+ Stop1 --> Decision1{Is new congestion status different?}
+ Decision1 -- No --> End1([Idle])
+ Decision1 -- Yes --> Update1[Update destination congestion status]
+ Update1 --> Path4[/Destination congestion status TRCC→TSFC/]
+ Path4 --> Connector1((1))
+ Path2 --> Decrement[Decrement destination congestion status]
+ Decrement --> Path5[/Destination congestion status TRCC→TSFC/]
+ Path5 --> Decision2{Congestion status = 0?}
+ Decision2 -- Yes --> End2([Idle])
+ Decision2 -- No --> Connector2((2))
+ Path3 --> Update2[Update destination congestion status equal to zero]
+ Update2 --> Stop2[/Stop congestion test TRCC→RCAT/]
+ Stop2 --> End3([Idle])
+
+```
+
+The flowchart illustrates the signalling traffic management process for signalling route set congestion control (TRCC). It begins with a 'Wait 03' state, leading to a decision point. From this point, three paths emerge:
+
+
+- Path 1:** 'Destination congestion status RTCC→TRCC' leads to 'Stop congestion test TRCC→RCAT', which then checks if the new congestion status is different. If 'No', the state becomes 'Idle'. If 'Yes', it proceeds to 'Update destination congestion status', then 'Destination congestion status TRCC→TSFC', and finally to connector '1'.
+- Path 2:** 'Decrement destination congestion status RCAT→TRCC' leads to 'Decrement destination congestion status', then 'Destination congestion status TRCC→TSFC', and then checks if 'Congestion status = 0?'. If 'Yes', the state becomes 'Idle'. If 'No', it proceeds to connector '2'.
+- Path 3:** 'Destination inaccessible TSRC→TRCC' leads to 'Update destination congestion status equal to zero', then 'Stop congestion test TRCC→RCAT', and finally to an 'Idle' state.
+
+ Connectors '1' and '2' lead to the next sheet in the sequence. The diagram is labeled '1, 2' on the left and 'T1188790-97' on the bottom right.
+
+Flowchart for signalling traffic management: signalling route set congestion control (TRCC).
+
+**Figure 29a/Q.704 (sheet 3 of 3) – Signalling traffic management; signalling route set congestion control (TRCC)**
+
+
+
+1
+
+```
+
+graph TD
+ Idle([Idle]) --> SLU[Signalling link unavailable
+TLAC→TCOC]
+ SLU --> BMSL[Buffer messages
+for affected
+signalling link]
+ BMSL --> ARDR[Alternative routing
+data request
+TCOC→TSRC]
+ ARDR --> W01([Wait 01])
+ W01 --> ARD[Alternative routing
+data
+TSRC→TCOC]
+ W01 --> ECO[ECO
+TLAC→TCOC]
+ W01 --> COO[COO
+TLAC→TCOC]
+ W01 --> SLA[Signalling link
+available
+TLAC→TCOC]
+ ARD --> RQ{Retrieval
+required?}
+ RQ -- No --> C54((5 4))
+ RQ -- Yes --> CM{Can
+changeover
+messages be exchanged?}
+ CM -- Yes --> RB[Retrieve
+BSNT
+L3→L2]
+ CM -- No --> STM[STM ready a)
+TCOC→LSAC]
+ RB --> W02([Wait 02])
+ STM --> ST1[Start T1]
+ ST1 --> W07([Wait 07])
+ SLA --> C23((2 3))
+ W07 --> C16((1 6))
+
+```
+
+Annotations:
+
+- Due to failure, blocking or inhibiting
+- Failed signalling link may not have been loaded
+- For inhibiting of link or other SP might be inaccessible
+- To reduce risk that diversion will cause mis-sequencing
+- Identifies alternative signalling links, if any, and also identifies whether unavailable link was loaded and accessibility of other SP
+
+T1142950-92/d93
+
+2
+
+4
+
+Flowchart for Signalling traffic management; changeover control (TCOC). The process starts at 'Idle' and proceeds through 'Signalling link unavailable TLAC→TCOC', 'Buffer messages for affected signalling link', 'Alternative routing data request TCOC→TSRC', and 'Wait 01'. It then branches into 'Alternative routing data TSRC→TCOC', 'ECO TLAC→TCOC', 'COO TLAC→TCOC', and 'Signalling link available TLAC→TCOC'. A decision 'Retrieval required?' follows. If 'No', it leads to connector '5 4'. If 'Yes', it asks 'Can changeover messages be exchanged?'. If 'Yes', it leads to 'Retrieve BSNT L3→L2' and 'Wait 02'. If 'No', it leads to 'STM ready a) TCOC→LSAC', 'Start T1', and 'Wait 07'. Annotations include 'Due to failure, blocking or inhibiting', 'Failed signalling link may not have been loaded', 'For inhibiting of link or other SP might be inaccessible', and 'To reduce risk that diversion will cause mis-sequencing'. Connector '1 6' is at the top right, and connector '2 3' is on the right side.
+
+a) This message is required only if signalling link restoration attempts may interfere with message retrieval.
+
+NOTE – In the processor outage and management inhibiting states, changeover messages should not be exchanged.
+
+**Figure 30/Q.704 (sheet 1 of 6) – Signalling traffic management;
+changeover control (TCOC)**
+
+
+
+2
+
+```
+
+graph TD
+ Start([Wait 02]) --> Branch1[ ]
+ subgraph Branch1 [ ]
+ direction LR
+ ECO[/ECO
+TLAC->TCOC/]
+ COO[/COO
+TLAC->TCOC/]
+ BSNT{BSNT
+L2->L3}
+ BSNT_not_retrievable{BSNT not
+retrievable
+L2->L3}
+ Signalling_link_available{Signalling link
+available
+TLAC->TCOC}
+ end
+ BSNT --> Mark_local[Mark local
+BSNT
+retrieved]
+ BSNT_not_retrievable --> Cancel_local[Cancel local
+BSNT
+retrieved]
+ Cancel_local --> STOP_L2{{STOP L2
+TCOC->LSAC}}
+ STOP_L2 --> Emergency_changeover{{Emergency
+changeover
+order
+TCOC->HMRT}}
+ Mark_local --> Changeover_order{{Changeover
+order
+TCOC->HMRT}}
+ Emergency_changeover --> Start_T2{{Start T2}}
+ Changeover_order --> Start_T2
+ Start_T2 --> Wait_ack([Wait for
+acknowledgement])
+ Signalling_link_available --> Connector((3 2))
+ Unspecified[From unspecified
+implementation
+dependent function] -.-> BSNT
+ Unspecified -.-> BSNT_not_retrievable
+ To_remote[To remote level 3] -.-> Changeover_order
+ To_remote -.-> Emergency_changeover
+
+```
+
+T1159270-94/d94
+
+Flowchart for Signalling traffic management; changeover control (TCOC). The process starts with 'Wait 02' and branches based on ECO, COO, BSNT, and Signalling link availability. It includes steps like 'Mark local BSNT retrieved', 'Cancel local BSNT retrieved', 'STOP L2 TCOC->LSAC', 'Changeover order TCOC->HMRT', 'Emergency changeover order TCOC->HMRT', 'Start T2', and 'Wait for acknowledgement'. Annotations include 'From unspecified implementation dependent function' and 'To remote level 3'. A connector '3 2' is also shown.
+
+**Figure 30/Q.704 (sheet 2 of 6) – Signalling traffic management;
+changeover control (TCOC)**
+
+
+
+```
+
+graph TD
+ Note["To reduce risk that diversion will cause mis-sequencing"] -.-> Wait07([Wait 07])
+ Wait07 --> SL[Signalling link available TLAC-TCOC]
+ Wait07 --> T1[T1]
+ T1 --> C3((3))
+ C3 --> StopT1[/Stop T1/]
+ StopT1 --> C2((2))
+ C2 --> SB[Send buffered messages on restored link a)]
+ SB --> SBuff[Stop buffering messages for restored link a)]
+ SBuff --> CNR1[/Changeover not required TCOC→TLAC/]
+ CNR1 --> CNR2[/Changeover not required TCOC→TSRC/]
+ CNR2 --> Idle([Idle])
+ Numbers["1, 2, 4, 5 6(2)"] -.-> SB
+
+```
+
+Flowchart for Signalling traffic management; changeover control (TCOC). The process starts with 'Wait 07' (linked to a note: 'To reduce risk that diversion will cause mis-sequencing'), followed by 'Signalling link available TLAC-TCOC' and 'T1'. A connector '3' leads to 'Stop T1'. From 'Stop T1', a connector '2' leads to 'Send buffered messages on restored link a)'. This is followed by 'Stop buffering messages for restored link a)', 'Changeover not required TCOC→TLAC', 'Changeover not required TCOC→TSRC', and finally 'Idle'. A list of numbers '1, 2, 4, 5 6(2)' is next to the 'Send buffered messages' step. A vertical line on the left has markers '2' and '3'.
+
+T1142960-92/d95
+
+a) These tasks should be carried out in the order shown.
+
+**Figure 30/Q.704 (sheet 3 of 6) – Signalling traffic management; changeover control (TCOC)**
+
+
+
+```
+
+graph TD
+ Start([Wait for acknowledgement]) --> HMDT_TOCOC_Ack[Changeover ack HMDT→TCOC]
+ Start --> HMDT_TOCOC_EmergencyAck[Emergency changeover ack HMDT→TCOC]
+ Start --> TLAC_TOCOC_Order[Changeover order TLAC→TCOC]
+ Start --> TLAC_TOCOC_Signalling[Signalling link available TLAC→TCOC]
+ Start --> TLAC_TOCOC_EmergencyOrder[Emergency changeover order TLAC→TCOC]
+ Start --> T2Bar[ $\overline{T2}$ ]
+
+ HMDT_TOCOC_Ack --> StopT2_1[Stop T2]
+ StopT2_1 --> C1((5))
+ C1 --> L3_L2[Retrieval Request and FSNC L3→L2]
+ L3_L2 --> MarkUnavailable[Mark link unavailable]
+ MarkUnavailable --> Retrieving([Retrieving])
+
+ HMDT_TOCOC_EmergencyAck --> StopT2_2[Stop T2]
+ StopT2_2 --> C2((4))
+
+ TLAC_TOCOC_Order --> StopT2_3[Stop T2]
+ StopT2_3 --> LocalBSNTRetrieved_1{Local BSNT retrieved?}
+ LocalBSNTRetrieved_1 -- No --> EmergencyAck_HMRT[Emergency changeover ack TCOC→HMRT]
+ LocalBSNTRetrieved_1 -- Yes --> ChangeoverAck_HMRT[Changeover ack TCOC→HMRT]
+ EmergencyAck_HMRT --> C3((5))
+ ChangeoverAck_HMRT --> C4((4))
+
+ TLAC_TOCOC_Signalling --> StopT2_4[Stop T2]
+ StopT2_4 --> C5((2))
+
+ TLAC_TOCOC_EmergencyOrder --> StopT2_5[Stop T2]
+ StopT2_5 --> LocalBSNTRetrieved_2{Local BSNT retrieved?}
+ LocalBSNTRetrieved_2 -- No --> EmergencyAck_HMRT_2[Emergency changeover ack TCOC→HMRT]
+ LocalBSNTRetrieved_2 -- Yes --> ChangeoverAck_HMRT_2[Changeover ack TCOC→HMRT]
+ EmergencyAck_HMRT_2 --> C6((4))
+ ChangeoverAck_HMRT_2 --> C7((5))
+
+ T2Bar --> StopL2[Stop L2 TCOC→LSAC]
+ StopL2 --> C8((4))
+
+ C1 -.-> RemoteLevel3_1[From remote level 3]
+ C3 -.-> RemoteLevel3_2[To remote level 3]
+ C6 -.-> RemoteLevel3_3[To remote level 3]
+
+ subgraph Annotations
+ A1[5, 4
+2, 4]
+ A2[5, 4]
+ end
+
+```
+
+Flowchart for Signalling traffic management; changeover control (TCOC). The diagram shows various message exchanges between HMDT, TCOC, TLAC, and LSAC, leading to states like 'Retrieving' or 'Mark link unavailable'. It includes decision points for 'Local BSNT retrieved?' and various 'Stop T2' or 'Stop L2' actions.
+
+T1159280-94/d96
+
+Figure 30/Q.704 (sheet 4 of 6) – Signalling traffic management; changeover control (TCOC)
+
+
+
+Flowchart for Signalling traffic management; changeover control (TCOC). The process starts with 'Retrieving' (oval), leading to 'Retrieved messages L2 → L3' (parallelogram). This leads to 'Save retrieved messages' (rectangle), which then leads back to 'Retrieving' (oval). From 'Retrieved messages L2 → L3', the flow also goes to 'Retrieval complete L2 → L3' (parallelogram). From 'Retrieval complete L2 → L3', the flow goes to a decision 'Link unavailable?' (diamond). If 'No', it goes to 'Send retrieved messages on restored link b)' (rectangle), which then leads to a connector '2' 3'. If 'Yes', it goes to 'Send retrieved messages on alternative signalling link(s) b)' (rectangle), which then leads to a connector '4' 1, 4(3) 6'. From 'Retrieval not possible L2 → TCOC' (parallelogram), the flow goes to a connector '2' 3'. From 'Signalling link available TLAC → TCOC' (parallelogram), the flow goes to 'Signalling link unavailable TLAC → TCOC' (parallelogram). From 'Signalling link unavailable TLAC → TCOC', the flow goes to 'Cancel link unavailable' (rectangle), which then goes to 'Mark link unavailable' (rectangle), which then leads to 'Retrieving' (oval). From 'Send retrieved messages on alternative signalling link(s) b)', the flow goes to 'STM ready a) TCOC → LSAC' (parallelogram), which then leads to a connector '3' 3'. From 'STM ready a) TCOC → LSAC', the flow goes to 'Send buffered messages on alternative signalling link(s) b)' (rectangle), which then leads to a connector '3' 3'. From 'Send buffered messages on alternative signalling link(s) b)', the flow goes to 'Update routing tables TCOC → HMRT' (parallelogram), which then leads to a connector '3' 3'. From 'Update routing tables TCOC → HMRT', the flow goes to 'Changeover executed TCOC → TLAC' (parallelogram), which then goes to 'Changeover executed TCOC → TSRC' (parallelogram), which finally leads to 'Idle' (oval). There are several callouts: 'From unspecified implementation dependent function' (dashed line to 'Retrieval complete L2 → L3'), 'Messages for inaccessible destinations are discarded' (dashed line to 'Send buffered messages on alternative signalling link(s) b)'), and 'To ensure that subsequent messages for unavailable link are diverted to alternative link(s) (if any) or discarded' (dashed line to 'Update routing tables TCOC → HMRT'). Numbers 8, 4, 2, 4, 3 are on the left margin. T1142970-92/d97 is at the bottom right of the diagram area.
+
+a) This message is required only if signalling link restoration may interfere with message retrieval.
+
+b) These tasks should be carried out in the order shown.
+
+**Figure 30/Q.704 (sheet 5 of 6) – Signalling traffic management; changeover control (TCOC)**
+
+
+
+Flowchart for Signalling traffic management; changeover control (TCOC). The process starts with 'Retrieving' (oval), leading to 'Retrieved messages L2 → L3' (parallelogram). This leads to 'Save retrieved messages' (rectangle), which then leads back to 'Retrieving' (oval). From the initial 'Retrieving' oval, there is a dashed line to 'From unspecified implementation dependent function' (text). The main flow continues from 'Retrieved messages L2 → L3' to 'Retrieval complete L2 → L3' (parallelogram). This leads to a decision 'Link unavailable?' (diamond). If 'No', it leads to 'Send retrieved messages on restored link b)' (rectangle), which then leads to connector '2' (circle). If 'Yes', it leads to 'Send retrieved messages on alternative signalling link(s) b)' (rectangle). From 'Send retrieved messages on restored link b)', the flow goes to connector '2' (circle), then to connector '4' (circle) with labels '1, 4(3)' and '6'. From connector '4', the flow goes to 'STM ready a)' (parallelogram), which leads to 'TCOC → LSAC' (parallelogram). From 'STM ready a)', the flow goes to connector '3' (circle) with label '3'. From connector '3', the flow goes to 'Send buffered messages on alternative signalling link(s) b)' (rectangle). From 'Send buffered messages on alternative signalling link(s) b)', the flow goes to 'Update routing tables TCOC → HMRT' (parallelogram). From 'Update routing tables TCOC → HMRT', the flow goes to 'Changeover executed TCOC → TLAC' (parallelogram). From 'Changeover executed TCOC → TLAC', the flow goes to 'Changeover executed TCOC → TSRC' (parallelogram). From 'Changeover executed TCOC → TSRC', the flow goes to 'Idle' (oval). There is a dashed line from 'Update routing tables TCOC → HMRT' to 'To ensure that subsequent messages for unavailable link are diverted to alternative link(s) (if any) or discarded' (text). There is also a dashed line from 'Send buffered messages on alternative signalling link(s) b)' to 'Messages for inaccessible destinations are discarded' (text). On the right side, 'Retrieval not possible L2 → TCOC' (parallelogram) leads to 'Signalling link available TLAC → TCOC' (parallelogram). 'Signalling link available TLAC → TCOC' leads to 'Signalling link unavailable TLAC → TCOC' (parallelogram). 'Signalling link unavailable TLAC → TCOC' leads to 'Cancel link unavailable' (rectangle), which leads to 'Mark link unavailable' (rectangle), which then leads to 'Retrieving' (oval). The flowchart includes numbered connectors (1, 2, 3, 4, 6, 8) and various annotations like 'a)' and 'b)'.
+
+a) This message is required only if signalling link restoration may interfere with message retrieval.
+
+b) These tasks should be carried out in the order shown.
+
+**Figure 30/Q.704 (sheet 6 of 6) – Signalling traffic management; changeover control (TCOC)**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> SLA[Signalling link available
+TLAC → TCBC]
+ Idle1 --> CD[Changeback declaration
+HMDT → TCBC]
+ CD --> CD_W["With changeback code x
+(from remote level 3)"]
+ CD --> CA[Changeback acknowledgement
+TCBC → HMRT]
+ CA --> CA_W["With changeback code x
+(to remote level 3)"]
+ CA --> Idle2([Idle])
+ SLA --> ARD[Alternative routing data request
+TCBC → TSRC]
+ ARD --> W[Wait for routing data]
+ W --> ARD_T[Alternative routing data
+TSRC → TCBC]
+ ARD_T --> RC{Routing changed?}
+ CD --> CD_T[Changeback declaration
+HMDT → TCBC]
+ W --> CD_T
+ CD_T --> Idle2
+ CD_T --> RT[Restart traffic on link
+buffered messages first]
+ RT --> UR[Update routing tables
+TCBC → HMRT]
+ UR --> RC
+ RC -- No --> CT[Changeback terminated
+TCBC → TLAC]
+ RC -- Yes --> B[Buffer concerned messages in
+changeback buffer(s)]
+ B --> C2((2))
+ C2 --> C2_2((2 (2)))
+ C2_2 --> RT
+ CT --> PT[Procedure terminated
+TCBC → TSRC]
+ PT --> Idle3([Idle])
+
+```
+
+1
+
+2
+
+Identifies alternative link(s) carrying traffic to be changed back and also identifies routing and SP accessibility changes
+
+Newly available link may not normally carry traffic
+
+Typically one changeback buffer per alternative link
+
+On newly available link
+
+With changeback code x (from remote level 3)
+
+With changeback code x (to remote level 3)
+
+T1159290-94/d99
+
+Flowchart for Signalling traffic management; changeback control (TCBC). The process starts at 'Idle', branches based on 'Signalling link available' or 'Changeback declaration', involves routing data requests, waiting, and decision points for 'Routing changed?'. It includes steps for buffering messages, updating tables, and terminating the procedure, ending at 'Idle'.
+
+NOTE – For simplicity, changeback from only one alternative link is shown.
+
+**Figure 31/Q.704 (sheet 1 of 2) – Signalling traffic management; changeback control (TCBC)**
+
+
+
+2
+
+```
+
+graph TD
+ Start2((2)) --> Q{Remote
+SP accessible?}
+ Q -- No --> StartT3{{Start T3}}
+ StartT3 --> TCD1([Time controlled
+diversion])
+ TCD1 --> CBD1[Changeback
+declaration
+HMDT → TCBC]
+ CBD1 --> TCD2([Time controlled
+diversion])
+ TCD2 --> T3_Wait[/T3/]
+ T3_Wait --> End1_1((1))
+
+ Q -- Yes --> CBD2[Changeback
+declaration
+TCBC → HMRT]
+ CBD2 --> StartT4{{Start T4}}
+ StartT4 --> Attempt1([First attempt])
+ Attempt1 --> T4_Wait[/T4/]
+
+ T4_Wait --> CBD3[Changeback
+declaration
+TCBC → HMRT]
+ CBD3 --> StartT5{{Start T5}}
+ StartT5 --> Attempt2([Second attempt])
+ Attempt2 --> T5_Wait[/T5/]
+ T5_Wait --> End1_2((1))
+
+ %% Side paths for acknowledgements and retries
+ T4_Wait --> CBD_Retry1[Changeback
+declaration
+HMDT → TCBC]
+ CBD_Retry1 --> Attempt1_Retry([First attempt])
+
+ T5_Wait --> CBD_Retry2[Changeback
+declaration
+HMDT → TCBC]
+ CBD_Retry2 --> Attempt2_Retry([Second attempt])
+
+ %% Acknowledgement paths
+ Ack1[Changeback
+ack
+HMDT → TCBC] --> StopT4{{Stop T4}}
+ StopT4 --> T3_Wait
+
+ Ack2[Changeback
+ack
+HMDT → TCBC] --> StopT5{{Stop T5}}
+ StopT5 --> End1_2
+
+ %% External inputs
+ FromSP[From above SP with
+changeback code y
+from remote level 3] -.-> Ack1
+ FromSP -.-> Ack2
+
+```
+
+Is SP at remote end of newly available link accessible via alternative link?
+
+Send to above SP via alternative link with changeback code y (to remote level 3)
+
+Wait to reduce risk that diversion causes mis-sequencing
+
+From above SP with changeback code y (from remote level 3)
+
+T1159300-94/d100
+
+Flowchart for Signalling traffic management; changeback control (TCBC). The process starts at connector 2, checks if a remote SP is accessible. If No, it starts T3, performs a time-controlled diversion, and sends a changeback declaration HMDT → TCBC. If Yes, it sends a changeback declaration TCBC → HMRT, starts T4, and attempts a changeback. The process includes two attempts with time-controlled diversions and acknowledgements. It ends at connector 1.
+
+NOTE – For simplicity, changeback from only one alternative link is shown.
+
+**Figure 31/Q.704 (sheet 2 of 2) – Signalling traffic management; changeback control (TCBC)**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> SRU[Signalling route unavailable
+TSRC → TFRC]
+ SRU --> Buffer[Buffer concerned traffic in forced rerouting buffer]
+ Buffer -.-> IfAny[If any exists]
+ Buffer --> ARD[Alternative routing data request
+TFRC → TSRC]
+ ARD --> Wait[Wait for routing data]
+ Wait --> Connector1((1))
+ Connector1 --> ARD2[Alternative routing data
+TSRC → TFRC]
+ ARD2 -.-> Identifies[Identifies routing change and availability of alternative route]
+ ARD2 --> Changed{Routing changed?}
+ Changed -.-> Newly[Newly unavailable route may not have been carrying traffic]
+ Changed -- No --> Update[Update routing tables
+TFRC → HMRT]
+ Changed -- Yes --> Available{Alternative route available?}
+ Available -- No --> Discard[Discard messages in forced rerouting buffer]
+ Available -- Yes --> StartNew[Start traffic on new route, buffered messages first]
+ Discard --> Update
+ StartNew --> Update
+ Update --> Terminated1[Procedure terminated
+TFRC → TSRC]
+ Terminated1 --> Terminated2[Forced rerouting terminated
+TFRC → RTAC]
+ Terminated2 --> Idle2([Idle])
+ ARD2 --> Available2[Signalling route available
+RTAC → TFRC]
+ Available2 --> StartNewly[Start traffic on newly available route, buffered message first]
+ StartNewly --> NotRequired[Forced rerouting not required
+TFRC → RTAC]
+ NotRequired --> Idle3([Idle])
+
+```
+
+The flowchart illustrates the forced rerouting control (TFRC) process. It begins with an 'Idle' state, followed by 'Signalling route unavailable TSRC → TFRC'. The next step is 'Buffer concerned traffic in forced rerouting buffer', which has a conditional branch 'If any exists'. This leads to 'Alternative routing data request TFRC → TSRC', then 'Wait for routing data', and finally a connector '1'. From connector '1', the process continues to 'Alternative routing data TSRC → TFRC', which identifies routing changes. A decision 'Routing changed?' follows, with a note that newly unavailable routes may not have been carrying traffic. If 'No', it proceeds to 'Update routing tables TFRC → HMRT'. If 'Yes', it checks 'Alternative route available?'. If 'No', it discards messages in the forced rerouting buffer. If 'Yes', it starts traffic on the new route, buffered messages first. Both paths lead to 'Update routing tables TFRC → HMRT'. The next steps are 'Procedure terminated TFRC → TSRC', 'Forced rerouting terminated TFRC → RTAC', and finally 'Idle'. There is also a path from 'Alternative routing data TSRC → TFRC' to 'Signalling route available RTAC → TFRC', which leads to 'Start traffic on newly available route, buffered message first', then 'Forced rerouting not required TFRC → RTAC', and finally 'Idle'.
+
+Flowchart for Signalling traffic management; forced rerouting control (TFRC).
+
+Figure 32/Q.704 – Signalling traffic management; forced rerouting control (TFRC)
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> SR{Signalling route available
+RTAC → TCRC}
+ SR -.-> SRD[Signalling route restricted
+TSRC → TCRC]
+ SR --> ARD{Alternative routing data request
+TCRC → TSRC}
+ ARD --> W1([Wait for routing data])
+ W1 --> ARD2{Alternative routing data
+TSRC → TCRC}
+ ARD2 --> RC{Routing changed?}
+ RC -- No --> PT{Procedure terminated
+TCRC → TSRC}
+ RC -- Yes --> BT[Buffer concerned traffic in controlled rerouting buffer]
+ BT --> ST6{Start T6}
+ ST6 --> W2([Wait])
+ W2 --> Idle2([Idle])
+ SRD -.-> ARD
+ SRD -.-> ARD2
+ ARD2 -.-> IC[Identifies routing change]
+ RC -.-> NM[Newly available route may not normally carry traffic]
+ W2 -.-> TR[To reduce risk that re-routing will cause mis-sequencing]
+ Idle1 --> C1((1))
+ C1 --> T6{— T6}
+ T6 --> ST[Start traffic on new route, buffered messages first]
+ ST --> UT{Update routing tables
+TCRC → HMRT}
+ UT --> PT
+ PT --> CRT{Controlled rerouting terminated
+TCRC → RTPC}
+ CRT --> Idle2
+ Idle2 --> C2((1))
+ C2 --> Idle1
+
+```
+
+Flowchart for Signalling traffic management; controlled rerouting control (TCRC). The process starts at 'Idle' and branches based on whether the signalling route is restricted or available. The 'restricted' path involves requesting alternative routing data and waiting, while the 'available' path involves starting traffic on the new route and updating routing tables. Both paths lead to a decision 'Routing changed?'. If 'No', the procedure is terminated. If 'Yes', traffic is buffered and the process continues through 'Start T6', 'Wait', and back to 'Idle'.
+
+NOTE – Dashed symbols apply only to the transfer restricted option.
+
+**Figure 33/Q.704 – Signalling traffic management; controlled rerouting control (TCRC)**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> D1{Destination congested
+RTCC → TSFC}
+ Idle1 --> D2{Message for congested destination
+HMRT → TSFC}
+ Idle1 --> D3{Destination inaccessible
+TSRC → TSFC}
+ Idle1 --> D4{Destination accessible
+TSRC → TSFC}
+
+ D1 --> M1[MTP Status L3 → L4]
+ M1 --> Is1st{Is this 1st msg for congested DPC?}
+ Is1st -- No --> IsN{Is this the n, 2n, 3n message for DPC?}
+ IsN -- No --> Idle2([Idle])
+ IsN -- Yes --> D5{Does OPC = own OPC?}
+ D5 -- Yes --> M2[MTP Status L3 → L4]
+ D5 -- No --> M3[Send transfer controlled TSFC → RTCC]
+ M3 -- To concerned SP --> Idle2
+
+ D2 --> Is1st
+ Is1st -- Yes --> D5
+
+ D3 --> M4[MTP Pause L3 → L4]
+ M4 -- To all user parts --> Idle3([Idle])
+
+ D4 --> M5[MTP Resume L3 → L4]
+ M5 -- To all user parts --> Idle3
+
+```
+
+Flowchart for signalling traffic management (TSFC) starting from an Idle state. It branches into four main paths: Destination congested (RTCC -> TSFC), Message for congested destination (HMRT -> TSFC), Destination inaccessible (TSRC -> TSFC), and Destination accessible (TSRC -> TSFC). The congested paths lead to decision diamonds about whether it's the 1st or n, 2n, 3n message for a DPC. If it's the 1st message, it checks if OPC = own OPC. If yes, it sends an MTP Status L3 -> L4. If no, it sends a transfer controlled message TSFC -> RTCC to a concerned SP. Both lead back to Idle. If it's not the 1st message, it checks if it's the n, 2n, 3n message. If yes, it sends an MTP Status L3 -> L4. If no, it goes directly to Idle. The inaccessible path leads to an MTP Pause L3 -> L4 message to all user parts, then to Idle. The accessible path leads to an MTP Resume L3 -> L4 message to all user parts, then to Idle.
+
+T1159330-94/d103
+
+NOTE – Delete hatched symbols when using Multiple Congestion States option.
+
+**Figure 34a/Q.704 (sheet 1 of 3) – Signalling traffic management; signalling traffic flow control (TSFC)**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --- D1{ }
+ D1 -.-> TRCC[Destination
+congestion
+status
+TRCC → TSFC]
+ D1 -.-> RTCC[Destination
+congestion
+status
+RTCC → TSFC]
+ D1 -.-> TSRC[Destination
+congestion
+status
+TSRC → TSFC]
+ D1 --> TPRC[Restart
+begins
+TPRC → TSFC]
+ TRCC -.-> MTP[MTP
+Status
+indication
+L3 → L4]
+ RTCC -.-> MTP
+ TSRC -.-> MTP
+ TPRC --> Restart([Restart])
+ MTP -.-> Idle2([Idle])
+ ToUser1[To all user parts] -.-> MTP
+ StopTraffic[Stop traffic with
+message priority less
+than congestion status] -.-> MTP
+
+```
+
+Flowchart for signalling traffic management (TSFC) starting from Idle state. It branches into two paths: one for multiple congestion states (TRCC, RTCC, TSRC to TSFC) leading to MTP Status indication (L3 to L4) and back to Idle; another for Restart (TPRC to TSFC) leading to Restart state. Annotations include 'To all user parts' and 'Stop traffic with message priority less than congestion status'.
+
+NOTE – Dotted symbols apply only to the multiple congestion states option.
+
+
+
+```
+
+graph TD
+ Restart1([Restart]) --> TPRC[Restarts
+ends
+TPRC → TSFC]
+ TPRC --> MTP[MTP restart
+ends
+indication
+L3 → L4]
+ MTP --> Idle2([Idle])
+ ToUser[To all user parts] -.-> MTP
+ ToRestart[To restart traffic taking into account
+accessibility and inaccessibility
+information from MTP] -.-> TPRC
+
+```
+
+Flowchart for signalling traffic management (TSFC) starting from Restart state. It leads to 'Restarts ends TPRC to TSFC', which then leads to 'MTP restart ends indication L3 to L4' (with 'To all user parts' annotation), and finally back to Idle state. An annotation 'To restart traffic taking into account accessibility and inaccessibility information from MTP' is present.
+
+T1142990-92/d104
+
+**Figure 34a/Q.704 (sheet 2 of 3) – Signalling traffic management; signalling traffic flow control (TSFC)**
+
+
+
+```
+graph TD; Idle1([Idle]) --> Distant["Distant user part unavailable RTCC → TSFC"]; Distant --> MTP["MTP Status indication L3 → L4"]; MTP --> Idle2([Idle])
+```
+
+The diagram illustrates a process flow for signalling traffic management and signalling traffic flow control (TSFC). It consists of four main components connected vertically by arrows. The process starts with an 'Idle' state (represented by a rounded rectangle). This leads to a decision block labeled 'Distant user part unavailable RTCC → TSFC' (represented by a chevron shape). From this block, an arrow points down to a block labeled 'MTP Status indication L3 → L4' (represented by a chevron shape). Finally, an arrow points down to another 'Idle' state (represented by a rounded rectangle). A vertical double line is positioned to the left of the flowchart.
+
+Flowchart showing signalling traffic management and signalling traffic flow control (TSFC) process.
+
+T1159340-94/d105
+
+**Figure 34a/Q.704 (sheet 3 of 3) – Signalling traffic management;
+signalling traffic flow control (TSFC)**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> J1(( ))
+ J1 --> In1[Adjacent SP restarting
+TSRC → TPRC]
+ J1 --> In2[Signalling point restart indication
+MGMT → TPRC]
+ J1 --> In3[T19]
+ J1 --> In4[Traffic restart allowed
+HMDT → TPRC]
+ In1 --> Out1[Mark adjacent SP restarting]
+ Out1 --> Idle2([Idle])
+ In2 --> Out2[Restart begins
+TPRC → LLSC]
+ Out2 --> Idle2
+ In3 --> Out3[Cancel T19 running]
+ Out3 --> Idle2
+ Note1[This applies to system initialisation] -.-> J1
+ Note2[For that destination] -.-> Out3
+ In4 --> Dec1{From an adjacent SP restarting?}
+ Dec1 -- Yes --> Note3[Unexpected TRA message]
+ Note3 --> Out4[Cancel adjacent SP restarting]
+ Dec1 -- No --> Dec2{T19 running?}
+ Dec2 -- Yes --> Note4[For that destination]
+ Note4 --> Idle2
+ Dec2 -- No --> Out5[Start T19]
+ Out5 --> Note4
+ Out4 --> Out6[Traffic restart allowed
+TPRC → TSRC]
+ Out5 --> Out6
+ Out6 --> Idle3([Idle])
+
+```
+
+Flowchart for signalling point restart control (TPRC). It starts with 'Idle' and branches based on four inputs: 'Adjacent SP restarting TSRC → TPRC', 'Signalling point restart indication MGMT → TPRC', 'T19', and 'Traffic restart allowed HMDT → TPRC'. The first two lead to 'Mark adjacent SP restarting' and 'Restart begins TPRC → LLSC' respectively, both returning to 'Idle'. The 'T19' input leads to 'Cancel T19 running', which returns to 'Idle' for that destination. The 'Traffic restart allowed' input leads to a decision 'From an adjacent SP restarting?'. If 'Yes', it's an 'Unexpected TRA message' and leads to 'Cancel adjacent SP restarting'. If 'No', it leads to 'T19 running?'. If 'Yes' to 'T19 running?', it returns to 'Idle' for that destination. If 'No', it leads to 'Start T19', which returns to 'Idle' for that destination. Both 'Cancel adjacent SP restarting' and 'Start T19' lead to 'Traffic restart allowed TPRC → TSRC', which finally returns to 'Idle'.
+
+T1143000-92/d106
+
+**Figure 34b/Q.704 (sheet 1 of 7) – Signalling traffic management; signalling point restart control (TPRC)**
+
+
+
+```
+
+graph TD
+ Idle([Idle]) -- "1" --> S1[Signalling point restart indication
+TSRC → TPRC]
+ S1 --> R1[Restart begins
+TPRC → TSFC]
+ R1 --> R2[Restart begins
+TPRC → TLAC]
+ R2 --> R3[Restart begins
+TPRC → HMRT]
+ R3 --> R4[Restart begins
+TPRC → HMDT]
+ R4 --> R5[Restart begins
+TPRC → HMDR]
+ R5 -- "2" --> C2((2))
+ C2 -- "2" --> R6[Restart begins
+TPRC → RTRC]
+ R6 --> R7[Restart begins
+TPRC → RTPC]
+ R7 --> R8[Restart begins
+TPRC → RSRT]
+ R8 --> R9[Restart begins
+TPRC → RTAC]
+ R9 --> T20[Start T20]
+ T20 --> STP{STP function?}
+ STP -- Yes --> T18[Start T18]
+ STP -- No --> W03([Wait 03])
+ T18 --> W01([Wait 01])
+
+```
+
+T1143010-92/d107
+
+Flowchart for signalling point restart control (TPRC). The process starts at 'Idle' and proceeds through a series of restart steps for various functions (TSRC, TSFC, TLAC, HMRT, HMDT, HMDR) until it reaches connector '2'. From connector '2', it continues with restart steps for RTRC, RTPC, RSRT, RTAC, then starts timers T20 and T18, and finally reaches 'Wait 01' or 'Wait 03' based on the STP function status.
+
+**Figure 34b/Q.704 (sheet 2 of 7) – Signalling traffic management;
+signalling point restart control (TPRC)**
+
+3
+
+4
+
+
+
+```
+
+graph TD
+ W01_1([Wait 01]) --> J1(( ))
+ J1 --> T18[/T18/]
+ J1 --> SLA[Signalling link available
+TLAC -> TPRC]
+ J1 --> TRA[Traffic restart allowed
+HMDT -> TPRC]
+ J1 --> SLU[Signalling link unavailable
+TLAC -> TPRC]
+ SLA --> MLA[Mark link available]
+ TRA --> MTR[Mark TRA received]
+ SLU --> CMLA[Cancel mark link available]
+ CMLA --> W01_2([Wait 01])
+ MLA --> ETM{Enough TRA messages?}
+ MTR --> ETM
+ ETM -- Yes --> SLA_V{Sufficient links available?}
+ ETM -- No --> W01_3([Wait 01])
+ SLA_V -- Yes --> ST18[/Stop T18/]
+ SLA_V -- No --> W01_3
+ ST18 --> RE[Restart ends
+TPRC -> LLSC]
+ RE --> SSP[Sending status phase
+TPRC -> TSRC]
+ SSP --> SS[Send status
+TPRC -> TSRC]
+ SS --> W02([Wait 02])
+ RE -.-> L1[Any links still restoring
+are reported failed,
+but keep trying]
+ SS -.-> L2[The status information
+is sent after the
+linkset is available
+at level 3]
+
+```
+
+Flowchart for Signalling traffic management; signalling point restart control (TPRC). The process starts at 'Wait 01' and branches based on four conditions: T18, Signalling link available (TLAC -> TPRC), Traffic restart allowed (HMDT -> TPRC), and Signalling link unavailable (TLAC -> TPRC). It includes decision diamonds for 'Enough TRA messages?' and 'Sufficient links available?', and various state transitions like 'Mark link available', 'Stop T18', 'Restart ends TPRC -> LLSC', and 'Send status TPRC -> TSRC'.
+
+T1143020-92/d108
+
+**Figure 34b/Q.704 (sheet 3 of 7) – Signalling traffic management; signalling point restart control (TPRC)**
+
+
+
+```
+
+graph TD
+ Wait01([Wait 01])
+ C3((3))
+ SR1{{Stop
+restart
+TSRC → TPRC}}
+ SR2{{Stop
+restart
+TPRC → TSFC}}
+ SR3{{Stop
+restart
+TPRC → TLAC}}
+ SR4{{Stop
+restart
+TPRC → RTRC}}
+ SR5{{Stop
+restart
+TPRC → RTPC}}
+ SR6{{Stop
+restart
+TPRC → RSRT}}
+ SR7{{Stop
+restart
+TPRC → RTAC}}
+ SR8{{Stop
+restart
+TPRC → HMRT}}
+ C4_1((4))
+
+ C4_2((4))
+ SR9{{Stop
+restart
+TPRC → HMDC}}
+ SR10{{Stop
+restart
+TPRC → HMDT}}
+ StopT18{{Stop T18}}
+ StopT20{{Stop T20}}
+ Idle([Idle])
+
+ Wait01 --> C3
+ C3 -- 3 --> SR1
+ SR1 --> SR2
+ SR2 --> SR3
+ SR3 --> SR4
+ SR4 --> SR5
+ SR5 --> SR6
+ SR6 --> SR7
+ SR7 --> SR8
+ SR8 --> C4_1
+
+ C4_2 -- 4 --> SR9
+ SR9 --> SR10
+ SR10 --> StopT18
+ StopT18 --> StopT20
+ StopT20 --> Idle
+
+```
+
+T1143030-92/d109
+
+Flowchart for signalling traffic management; signalling point restart control (TPRC). The process starts at 'Wait 01', proceeds through a series of 'Stop restart' steps for various signalling points (TSRC, TSFC, TLAC, RTRC, RTPC, RSRT, RTAC, HMRT), then enters a loop of 'Stop restart' steps for HMDC, HMDT, followed by 'Stop T18' and 'Stop T20', ending at 'Idle'.
+
+**Figure 34b/Q.704 (sheet 4 of 7) – Signalling traffic management;
+signalling point restart control (TPRC)**
+
+
+
+The flowchart illustrates the signalling point restart control (TPRC) process. It begins at the 'Wait 02' state and branches into three main paths:
+
+- Path 1 (Status sent TSRC → TPRC):** Leads to 'Stop T20', then 'T20 expired TPRC → TSRC', then 'Restart ends TPRC → TSRC', then 'Start T19', then 'Restart ends TPRC → LLSC', then 'Restart ends TPRC → TSFC', then 'Restart ends TPRC → TLAC', then 'Restart ends TPRC → RTRC', ending at connector '5'.
+- Path 2 (T20):** Leads to 'T20 expired TPRC → TSRC', then 'Stop restart TPRC → HMDC', then 'Stop T20', then 'T20 expired TPRC → TSRC', ending at 'Idle' state.
+- Path 3 (Stop restart TSRC → TPRC):** Leads to 'Stop restart TPRC → TSFC', then 'Stop restart TPRC → TLAC', then 'Stop restart TPRC → RTRC', then 'Stop restart TPRC → RTPC', then 'Stop restart TPRC → RSRT', then 'Stop restart TPRC → RTAC', then 'Stop restart TPRC → HMRT', ending at connector '6'.
+
+Additional transitions include:
+
+- From connector '5' (top left): 'Restart ends TPRC → RTPC', 'Restart ends TPRC → RSRT', 'Restart ends TPRC → RTAC', 'Restart ends TPRC → HMRT', 'Restart ends TPRC → HMDC', 'Restart ends TPRC → HMDT', ending at 'Idle' state.
+- From connector '6' (middle): 'Stop restart TPRC → HMDC', 'Stop restart TPRC → HMDT', 'Stop restart TPRC → RTAC', 'Stop restart TPRC → HMRT', ending at connector '6' (bottom right).
+
+A dashed line indicates a transition from 'T20 expired TPRC → TSRC' to 'Stop restart TPRC → HMDC' for all SPs to which a TRA message was sent.
+
+Labels on the left margin: 5, 6, 6, 5.
+
+Connector labels: 5 (top left), 5 (bottom center), 6 (middle), 6 (bottom right).
+
+Text: T1143040-92/d110
+
+Flowchart for signalling point restart control (TPRC) starting from 'Wait 02' state. It branches into three main paths: 'Status sent TSRC -> TPRC', 'T20', and 'Stop restart TSRC -> TPRC'. Each path leads to a series of state transitions and timer actions (Stop T20, Start T19, T20 expired) eventually leading to 'Idle' or back to initial states.
+
+**Figure 34b/Q.704 (sheet 5 of 7) – Signalling traffic management; signalling point restart control (TPRC)**
+
+7, 8
+
+
+
+```
+
+ graph TD
+ Start1([Wait 03]) --> T20{T20}
+ Start1 --> HMDT{Traffic restart allowed
+HMDT → TPRC}
+ Start1 --> TSRC{Stop restart
+TSRC → TPRC}
+
+ T20 --> T20_expired{[T20 expired
+TPRC → TSRC]}
+
+ HMDT --> Enough{Enough TRA messages?}
+
+ Enough -- No --> Start2([Wait 03])
+
+ Enough -- Yes --> StopT20{[Stop T20]}
+
+ StopT20 --> T20_expired
+
+ T20_expired --> Sending{[Sending status phase
+TPRC → TSRC]}
+
+ Sending -.-> Note1[Puts TSRC into "Wait 05" so that
+TRA message is sent]
+
+ Sending --> RestartEnd1{[Restart ends
+TPRC → LLSC]}
+
+ RestartEnd1 --> RestartEnd2{[Restart ends
+TPRC → TSRC]}
+
+ RestartEnd2 -.-> Note2[The status information
+is sent after the
+linkset is available
+at level 3]
+
+ RestartEnd2 --> RestartEnd3{[Restart ends
+TPRC → TSFC]}
+
+ RestartEnd3 --> End1((7))
+
+ End1 -.-> Note3[6]
+
+ TSRC --> StopRestart1{[Stop restart
+TPRC → LLSC]}
+
+ StopRestart1 --> StopRestart2{[Stop restart
+TPRC → TSFC]}
+
+ StopRestart2 --> StopRestart3{[Stop restart
+TPRC → TLAC]}
+
+ StopRestart3 --> StopRestart4{[Stop restart
+TPRC → RTRC]}
+
+ StopRestart4 --> StopRestart5{[Stop restart
+TPRC → RTPC]}
+
+ StopRestart5 --> StopRestart6{[Stop restart
+TPRC → RSRT]}
+
+ StopRestart6 --> StopRestart7{[Stop restart
+TPRC → RTAC]}
+
+ StopRestart7 --> End2((8))
+
+ End2 -.-> Note4[6]
+
+```
+
+Flowchart for Signalling traffic management; signalling point restart control (TPRC).
+
+T1143050-92/d111
+
+**Figure 34b/Q.704 (sheet 6 of 7) – Signalling traffic management; signalling point restart control (TPRC)**
+
+
+
+The diagram illustrates two parallel sequences of signalling point restart control (TPRC) steps, labeled 7 and 8.
+
+**Sequence 7 (Restart):**
+
+- Start (7 5)
+- Restart ends TPRC → TLAC
+- Restart ends TPRC → RTRC
+- Restart ends TPRC → RTPC
+- Restart ends TPRC → RSRT
+- Restart ends TPRC → RTAC
+- Restart ends TPRC → HMRT
+- Restart ends TPRC → HMDC
+- Restart ends TPRC → HMDT
+- Idle
+
+**Sequence 8 (Stop restart):**
+
+- Start (8 5)
+- Stop restart TPRC → HMRT
+- Stop restart TPRC → HMDC
+- Stop restart TPRC → HMDT
+- Stop T20
+- T20 expired TPRC → TSRC
+- Idle
+
+T1143060-92/d112
+
+Flowchart showing two parallel sequences of signalling point restart control (TPRC) steps. The left sequence (7) shows restart steps for TLAC, RTRC, RTPC, RSRT, RTAC, HMRT, HMDC, and HMDT, ending in Idle. The right sequence (8) shows stop restart steps for HMRT, HMDC, and HMDT, followed by Stop T20, T20 expired (TPRC -> TSRC), and ending in Idle.
+
+Figure 34b/Q.704 (sheet 7 of 7) – Signalling traffic management; signalling point restart control (TPRC)
+
+
+
+This diagram illustrates the functional block interactions for Level 3 - Signalling link management (SLM). It shows the flow of control and data between various functional blocks and external entities.
+
+**External Entities and Interactions:**
+
+- From management system (MGMT):** Provides control signals to the Link set control (LLSC) block.
+- To/from signalling traffic management (STM):** Exchanges emergency and restart signals with the LLSC block.
+- To/from signalling link test control (SLTC):** Exchanges SLT success/failure signals with the LLSC block.
+- To/from level 2 (L2):** Exchanges status and control signals with the Signalling link activity control (LSAC) block.
+- To/from remote level 3 (L3):** Exchanges connection orders and status with the Signalling data link allocation (LSDA) block.
+- To/from level 1 (L1):** Exchanges disconnect/connect signals with the Signalling terminal allocation (LSTA) block.
+
+**Functional Blocks and Interactions:**
+
+- Link set control (LLSC) Figure 36:**
+ - Receives input from MGMT (Activate link set, Deactivate link set).
+ - Exchanges emergency/restart signals with STM.
+ - Exchanges SLT success/failure signals with SLTC.
+ - Controls the LSAC block via Activate/Deactivate link, Emergency ceases, and Restart ends signals.
+- Signalling link activity control (LSAC) Figure 37:**
+ - Receives control signals from LLSC.
+ - Exchanges status and control signals with L2.
+ - Controls the LSLA, LSLR, and LSDA blocks via Start activation, Restart activation, Deactivate link, Start restoration, and Start signalling link un- Restoration un- successful signals.
+- Signalling link activation (LSLA) Figure 38:**
+ - Receives activation signals from LSAC.
+ - Exchanges data link status (Data link, No data link) with the LSDA block.
+- Signalling link restoration (LSLR) Figure 39:**
+ - Receives restoration signals from LSAC.
+ - Exchanges data link status (Data link, No data link) with the LSDA block.
+- Signalling link allocation (LSDA) Figure 42:**
+ - Receives connection orders from L3.
+ - Exchanges data link status with LSLA, LSLR, and LSTA blocks.
+- Signalling terminal allocation (LSTA) Figure 41:**
+ - Receives terminal status (Terminal, No terminal) from LSLA, LSLR, and LSDA blocks.
+ - Exchanges disconnect/connect signals with L1.
+- Signalling link deactivation (LSD) Figure 40:**
+ - Receives deactivation signals from LSAC.
+ - Exchanges data link status (Data link, No data link) with the LSDA block.
+
+**Internal Control Signals:**
+
+- From LLSC to LSAC:** Activate link, Deactivate link, Emergency ceases, Restart ends.
+- From LSAC to LLSC:** Link active, Link failed, Activate another link, Link inactive.
+- From LSAC to LSLA/LSLR/LSDA:** Start activation, Restart activation, Deactivate link, Start restoration, Start signalling link un- Restoration un- successful.
+- From LSLA/LSLR/LSDA to LSAC:** Data link, No data link.
+- From LSLA/LSLR/LSDA to LSTA:** Terminal, No terminal.
+
+Functional block interactions diagram for Level 3 - Signalling link management (SLM).
+
+T1143070-92/d113
+
+NOTE – Abbreviated message names have been used in this diagram (i.e. origin →destination codes are omitted).
+
+**Figure 35/Q.704 – Level 3 – Signalling link management (SLM); functional block interactions**
+
+
+
+```
+
+graph TD
+ Inactive1([Inactive]) --> A1[Activate link set MGMT -> LLSC]
+ Inactive1 --> R1[Restart begins TPRC -> LLSC]
+ A1 --> S1[Select links to activate]
+ R1 --> S2[Select links to activate]
+ S1 --> AL1[Activate link LLSC -> LSAC]
+ S2 --> AL1
+ AL1 --> Active([Active])
+ Active --> D1[Deactivate link set MGMT -> LLSC]
+ Active --> A2[Activate link set MGMT -> LLSC]
+ Active --> LA1[Link active LSAC -> LLSC]
+ D1 --> DL1[Deactivate link LLSC -> LSAC]
+ DL1 --> Inactive2([Inactive])
+ A2 --> LA1
+ LA1 --> DQ{Deactivation of a link}
+ DQ -- No --> Active
+ DQ -- Yes --> SL1[Select a link to deactivate]
+ SL1 --> DL2[Deactivate link LLSC -> LSAC]
+ DL2 --> Active
+ LinksetRestart[Link set restart] -.-> LA1
+ IsCurrentNumber{Is current number of active links greater than specified number?} -.-> DQ
+ OneIndication1[One indication for each link to be activated] -.-> AL1
+ OneIndication2[One indication for each link in the link set] -.-> DL1
+
+```
+
+Annotations and connector details:
+
+- Annotations on the left margin: '1, 4' near the top, '2' near the middle, '1, 2' near the bottom, and '2' at the very bottom.
+- Connector numbers: '1' at the start of activation, '4' at the start of restart, '2' between activation and active state, '3' between active and deactivation/activation, '1' between activation and link active, '2' between link active and deactivation decision, '1' between deactivation decision and deactivate link, '2' between deactivate link and active state.
+- Brackets: 'One indication for each link to be activated' for the activation step, 'One indication for each link in the link set' for the deactivate link step, and 'Is current number of active links greater than specified number?' for the deactivation decision.
+- A dashed line labeled 'Link set restart' connects the 'Active' state to the 'Link active LSAC -> LLSC' step.
+
+Flowchart for Signalling link management; link set control (LLSC). The diagram shows two main paths: activation and deactivation of link sets. Activation starts from 'Inactive', goes through 'Activate link set MGMT -> LLSC', 'Select links to activate', and 'Activate link LLSC -> LSAC' to reach 'Active'. Deactivation starts from 'Active', goes through 'Deactivate link set MGMT -> LLSC', 'Deactivate link LLSC -> LSAC' to return to 'Inactive', or through 'Activate link set MGMT -> LLSC' to 'Link active LSAC -> LLSC', then a decision 'Deactivation of a link'. If 'No', it returns to 'Active'. If 'Yes', it goes through 'Select a link to deactivate', 'Deactivate link LLSC -> LSAC', and returns to 'Active'. Annotations include 'One indication for each link to be activated', 'One indication for each link in the link set', and 'Is current number of active links greater than specified number?'. Connector numbers 1, 2, 3, 4 are used throughout the diagram.
+
+T1160130-94/d114
+
+**Figure 36/Q.704 (sheet 1 of 3) – Signalling link management; link set control (LLSC)**
+
+
+
+```
+
+graph TD
+ subgraph Inputs
+ direction TB
+ I1((3
+1)) --> L1[Link failed
+LSAC → LLSC]
+ I2(( )) --> L2[Activate
+another link
+LSAC → LLSC]
+ I3(( )) --> L3[Emergency
+TSRC → LLSC]
+ I4(( )) --> L4[Link inactive
+LSAC → LLSC]
+ end
+
+ L1 --> D1{Any
+active link
+in link set?}
+ D1 -- No --> C1((1
+1))
+ D1 -- Yes --> D2{Activation
+of a link?}
+ D2 -- Yes --> S1[Select link
+to activate]
+ S1 --> A1[Activate
+link
+LLSC → LSAC]
+ A1 --> C2((2
+1))
+ D2 -- No --> D3{Is current number
+of active links less
+than specified
+number?}
+ D3 -- Yes --> L2
+ D3 -- No --> C2
+ L3 --> E1[Emergency
+ceases
+TSRC → LLSC]
+ E1 --> E2[Emergency
+ceases
+LLSC → LSAC]
+ E2 --> C2
+ L4 --> C2
+
+ C1 -.-> LS[Link set]
+ C2 -.-> OI[One indication
+for each link
+in the link set]
+
+```
+
+Flowchart for Signalling link management; link set control (LLSC). The diagram shows four main input paths at the top: 'Link failed LSAC → LLSC', 'Activate another link LSAC → LLSC', 'Emergency TSRC → LLSC', and 'Link inactive LSAC → LLSC'. The 'Link failed' path leads to a decision 'Any active link in link set?'. If 'No', it goes to connector '1'. If 'Yes', it goes to 'Activation of a link?'. 'Activation of a link?' has a 'Yes' path to 'Select link to activate' → 'Activate link LLSC → LSAC' → connector '2'. A 'No' path from 'Activation of a link?' leads to a decision 'Is current number of active links less than specified number?'. If 'Yes', it goes to 'Activate another link LSAC → LLSC'. If 'No', it goes to connector '2'. The 'Emergency TSRC → LLSC' path leads to 'Emergency ceases TSRC → LLSC' → 'Emergency ceases LLSC → LSAC' → connector '2'. The 'Link inactive LSAC → LLSC' path leads directly to connector '2'. Connector '1' is labeled 'Link set'. Connector '2' is labeled 'One indication for each link in the link set'. A reference 'T1160140-94/d115' is at the bottom right.
+
+NOTE 1 – It is assumed that this function has access to information regarding the number and status of links in a link set.
+
+NOTE 2 – It should be ensured that signalling link activation and deactivation attempts are not made simultaneously for the same signalling link.
+
+**Figure 36/Q.704 (sheet 2 of 3) – Signalling link management;
+link set control (LLSC)**
+
+
+
+4
+
+```
+
+graph TD
+ Active1([Active]) --> RB[Restart begins TPRC → LLSC]
+ Active1 --> RE[Restart ends TPRC → LLSC]
+ RE -.-> Note[One indication for each link in the link set]
+ RB --> Circle((4
+1))
+ RE --> REL[Restart ends LLSC → LSAC]
+ REL --> Active2([Active])
+
+```
+
+T1160150-94/d116
+
+Flowchart of signalling link management; link set control (LLSC). The process starts at an 'Active' state, branches into 'Restart begins TPRC → LLSC' and 'Restart ends TPRC → LLSC'. The left path leads to a circle with '4' and '1'. The right path leads to 'Restart ends LLSC → LSAC' and back to an 'Active' state. A note indicates that the 'Restart ends TPRC → LLSC' step has one indication for each link in the link set.
+
+**Figure 36/Q.704 (sheet 3 of 3) – Signalling link management;
+link set control (LLSC)**
+
+1
+
+
+
+The flowchart illustrates the signalling link management process for the LSAC (Signalling Link Activity Control). It begins with an 'Inactive' state (oval), which leads to a horizontal line. From this line, three parallel paths emerge: 'Activate link LLSC → LSAC', 'Activate link MGMT → LSAC', and 'Data link LSDA → LSAC'. These paths converge into a single arrow pointing to a circle containing the number '1', with the text '2, 2 bis' next to it. Below this, the process continues with 'Start activation LSAC → LSLA' (parallelogram), 'Mark activation' (rectangle), and 'Activating/restoring' (oval). This is followed by 'Activation not possible LSLA → LSAC' (parallelogram) and 'Deactivate link LSAC → LSDA' (parallelogram). A decision diamond asks 'Activation/restoration unsuccessful?'. If 'No', it leads to 'Activate another link LSAC → LLSC' (parallelogram). If 'Yes', it leads directly to the final 'Inactive' state (oval). The text 'T1160160-94/d117' is located near the bottom right of the flow.
+
+```
+graph TD; Inactive1([Inactive]) --> Junction(( )); Junction --> A1[/Activate link LLSC → LSAC/]; Junction --> A2[/Activate link MGMT → LSAC/]; Junction --> A3[/Data link LSDA → LSAC/]; A1 --> B1(( )); A2 --> B1; A3 --> B1; B1 --> B2((1 2, 2 bis)); B2 --> B3[/Start activation LSAC → LSLA/]; B3 --> B4[Mark activation]; B4 --> B5([Activating/restoring]); B5 --> B6[/Activation not possible LSLA → LSAC/]; B6 --> B7[/Deactivate link LSAC → LSDA/]; B7 --> B8{Activation/restoration unsuccessful?}; B8 -- No --> B9[/Activate another link LSAC → LLSC/]; B8 -- Yes --> B10([Inactive]); B9 --> B10;
+```
+
+Flowchart for signalling link management (LSAC)
+
+**Figure 37/Q.704 (sheet 1 of 10) – Signalling link management; signalling link activity control (LSAC)**
+
+
+
+This state transition diagram shows the management of a signalling link. It begins with an initial state (circle with '1'). Two transitions, 'Emergency LLSC → LSAC' and 'Emergency ceases LLSC → LSAC', lead to 'Mark emergency' and 'Cancel emergency' blocks respectively. Both blocks lead to the 'Inactive' state (oval). A self-loop transition is also shown from the initial state.
+
+```
+
+stateDiagram-v2
+ [*] --> [*] : Emergency LLSC → LSAC
+ [*] --> [*] : Emergency ceases LLSC → LSAC
+ [*] --> Mark emergency
+ [*] --> Cancel emergency
+ Mark emergency --> [*] : Inactive
+ Cancel emergency --> [*] : Inactive
+
+```
+
+T1160170-94/d118
+
+State transition diagram for signalling link management (sheet 2 of 10).
+
+NOTE – See sheet 2 *bis*, for a national option.
+
+**Figure 37/Q.704 (sheet 2 of 10) – Signalling link management; signalling link activity control (LSAC)**
+
+
+
+This state transition diagram is an extended version of the previous one. It includes two additional transitions: 'Local processor outage LLSC → LSAC' leading to 'Mark local processor outage' and 'Local processor recovered LLSC → LSAC' leading to 'Cancel local processor outage'. Both of these blocks also lead to the 'Inactive' state.
+
+```
+
+stateDiagram-v2
+ [*] --> [*] : Emergency LLSC → LSAC
+ [*] --> [*] : Emergency ceases LLSC → LSAC
+ [*] --> Mark emergency
+ [*] --> Cancel emergency
+ [*] --> Mark local processor outage
+ [*] --> Cancel local processor outage
+ Mark emergency --> [*] : Inactive
+ Cancel emergency --> [*] : Inactive
+ Mark local processor outage --> [*] : Inactive
+ Cancel local processor outage --> [*] : Inactive
+
+```
+
+T1160180-94/d119
+
+State transition diagram for signalling link management (sheet 2 bis of 10).
+
+**Figure 37/Q.704 (sheet 2 *bis* of 10) – Signalling link management; signalling link activity control (LSAC)**
+
+
+
+```
+
+graph TD
+ Start([Activating/restoring]) --> SLT_Succ{SLT successful
+SLTC → LSAC}
+ Start --> In_Service{In service
+L2 → L3}
+ Start --> Out_of_Service{Out of service
+L2 → L3}
+ SLT_Succ --> Signalling_Link[Signalling link in service
+LSAC → TLAC]
+ Signalling_Link --> Link_Active[Link active
+LSAC → LLSC]
+ Link_Active --> Cancel_Failure[Cancel first failure]
+ Cancel_Failure --> Cancel_Activation[Cancel activation/
+restoration unsuccessful]
+ Cancel_Activation --> Active([Active])
+
+ In_Service --> Start_SLT[Start SLT
+LSAC → SLTC]
+ Start_SLT --> Activating_Restoring([Activating/restoring])
+
+ Out_of_Service --> First_Failure{First failure?}
+ First_Failure -- No --> Mark_Failure[Mark first failure]
+ First_Failure -- Yes --> Terminal_Available[Terminal available
+LSAC → LSTA]
+ Terminal_Available --> Cancel_Failure_2[Cancel first failure]
+
+ Mark_Failure --> Restart_Restoration[Restart restoration
+LSAC → LSLR]
+ Cancel_Failure_2 --> Activation{Activation?}
+ Activation -- No --> Restart_Restoration
+ Activation -- Yes --> Cancel_Activation_2[Cancel activation]
+ Cancel_Activation_2 --> Restart_Activation[Restart activation
+LSAC → LSLA]
+
+ Restart_Restoration --> Activating_Restoring_2([Activating/restoring])
+ Restart_Activation --> Activating_Restoring_2
+
+ End((2))
+ T1160190-94/d120
+
+```
+
+Flowchart for Signalling link management; signalling link activity control (LSAC). The process starts with 'Activating/restoring' and branches based on SLT status (successful, in service, or out of service).
+
+**Figure 37/Q.704 (sheet 3 of 10) – Signalling link management; signalling link activity control (LSAC)**
+
+
+
+```
+
+graph TD
+ subgraph Entry
+ direction LR
+ E1((2)) --> S1[Start signalling link LSLA → LSAC]
+ E2((3)) --> S2[Start signalling link LSLR → LSAC]
+ end
+ S1 --> T17_start[Start T17]
+ S2 --> T17_start
+ T17_start --> Wait[Wait]
+ Wait --> T17_flow[ ]
+ style T17_flow fill:none,stroke:none
+ T17_flow --> Emergency{Emergency?}
+ Emergency -- Yes --> Emergency_L3L2[Emergency L3 → L2]
+ Emergency -- No --> Activating[Activating/restoring]
+ Emergency_L3L2 --> Start_L3L2[Start L3 → L2]
+ Start_L3L2 --> Activating
+ S1 --> Unsuccessful{Activation/restoration unsuccessful?}
+ S2 --> Unsuccessful
+ Unsuccessful -- Yes --> Activating
+ Unsuccessful -- No --> Mark[Mark activation/restoration unsuccessful]
+ Mark --> Activate[Activate another link LSAC → LLSC]
+ Activate --> Activating
+ E3((5)) --> Restoration[Restoration unsuccessful LSLR → LSAC]
+ Restoration --> Unsuccessful
+ Activating --> End([Activating/restoring])
+ Ref[T1160200-94/d121]
+
+```
+
+Flowchart for signalling link management (LSAC) showing activation and restoration processes. It starts with two entry points (2 and 3) leading to 'Start signalling link' (LSLA or LSLR to LSAC). Both lead to 'Start T17' and 'Wait'. From 'Wait', it goes to 'T17' and then to an 'Emergency?' decision. If 'Yes', it goes to 'Emergency L3 to L2' and then 'Start L3 to L2'. If 'No', it goes to 'Activating/restoring'. Both 'Start signalling link' paths also lead to a decision 'Activation/restoration unsuccessful?'. If 'Yes', it goes to 'Activating/restoring'. If 'No', it goes to 'Mark activation/restoration unsuccessful' and then 'Activate another link LSAC to LLSC', which then leads to 'Activating/restoring'. A third entry point (5) leads to 'Restoration unsuccessful LSLR to LSAC', which also leads to the 'Activation/restoration unsuccessful?' decision. A reference 'T1160200-94/d121' is present near the end.
+
+**Figure 37/Q.704 (sheet 4 of 10) – Signalling link management;
+signalling link activity control (LSAC)**
+
+
+
+```
+
+graph TD
+ 3((3
+4)) --> SLT[SLT failed
+SLTC → LSAC]
+ SLT --> LLSC[Deactivate link
+LLSC → LSAC]
+ LLSC --> LSTA[Deactivate link
+LSTA → LSAC]
+ LSTA --> MGMT[Deactivate link
+MGMT → LSAC]
+ MGMT --> Stop[Stop
+L3 → L2]
+ Stop --> LSAC_LSLD[Deactivate link
+LSAC → LSLD]
+ LSAC_LSLD --> LSAC_LSLA[Deactivate link
+LSAC → LSLA]
+ LSAC_LSLA --> LSAC_LLSC[Link inactive
+LSAC → LLSC]
+ LSAC_LLSC --> Decision{Activation/
+restoration unsuccessful?}
+ Decision -- Yes --> Cancel[Cancel activation/
+restoration
+unsuccessful]
+ Decision -- No --> Activate[Activate
+another link
+LSAC → LLSC]
+ Cancel --> Inactive([Inactive])
+ Activate --> Inactive
+ Inactive --> 4((4
+6))
+
+```
+
+The flowchart illustrates the management of a signalling link failure. It begins at node 3 (labeled 3, 4) and proceeds through a series of deactivation steps: SLT failed (SLTC → LSAC), Deactivate link (LLSC → LSAC), Deactivate link (LSTA → LSAC), and Deactivate link (MGMT → LSAC). A bracket labeled 'Take signalling link out of service' groups the transition from MGMT to Stop (L3 → L2). Following Stop, the link is deactivated at lower layers: LSAC → LSLD, LSAC → LSLA, and finally Link inactive (LSAC → LLSC). A decision diamond asks 'Activation/ restoration unsuccessful?'. If 'Yes', the process goes to 'Cancel activation/ restoration unsuccessful'. If 'No', it goes to 'Activate another link (LSAC → LLSC)'. Both paths lead to the 'Inactive' state, which then connects to node 4 (labeled 6).
+
+Flowchart for Signalling link management; signalling link activity control (LSAC). The process starts at node 3 (labeled 3, 4) and ends at node 4 (labeled 6). It details the steps taken when a signalling link fails, including deactivation of various components (SLTC, LLSC, LSTA, MGMT) and subsequent attempts to reactivate or deactivate the link at different layers (L3, L2, LSLD, LSLA, LLSC).
+
+T1160210-94/d122
+
+**Figure 37/Q.704 (sheet 5 of 10) – Signalling link management;
+signalling link activity control (LSAC)**
+
+
+
+4
+
+5
+
+```
+
+graph TD
+ Start((4)) --> E1[Emergency LLSC → LSAC]
+ E1 --> M[Mark emergency]
+ M --> EL3[Emergency L3 → L2]
+ E2[Emergency ceases LLSC → LSAC] --> C[Cancel emergency]
+ C --> EC3[Emergency ceases L3 → L2]
+ E3[Restart ends LLSC → LSAC] --> SLF[Signalling link failed LSAC → TLAC]
+ E4[Remote processor recovered L2 → LSAC] --> SLT[Start SLT LSAC → SLTC]
+ EL3 --> AR([Activating/ restoring])
+ EC3 --> AR
+ SLF --> AR
+ SLT --> AR
+
+```
+
+The flowchart illustrates the signalling link management (LSAC) process. It begins with a start node (4) leading to an 'Emergency LLSC → LSAC' event. This event triggers a 'Mark emergency' action, which in turn leads to an 'Emergency L3 → L2' message. Another 'Emergency ceases LLSC → LSAC' event triggers a 'Cancel emergency' action, leading to an 'Emergency ceases L3 → L2' message. A 'Restart ends LLSC → LSAC' event triggers a 'Signalling link failed LSAC → TLAC' message. A 'Remote processor recovered L2 → LSAC' event triggers a 'Start SLT LSAC → SLTC' message. All four messages ('Emergency L3 → L2', 'Emergency ceases L3 → L2', 'Signalling link failed LSAC → TLAC', and 'Start SLT LSAC → SLTC') lead to a common 'Activating/ restoring' state. The diagram is labeled T1160220-94/d123.
+
+Flowchart of signalling link management (LSAC)
+
+**Figure 37/Q.704 (sheet 6 of 10) – Signalling link management;
+signalling link activity control (LSAC)**
+
+5
+
+
+
+```
+
+ graph TD
+ Active([Active]) --> 5((5))
+ Active --> StopL2[Stop L2
+TCOC → LSAC]
+ StopL2 --> StopL3[Stop
+L3 → L2]
+ StopL3 --> StopL3
+ StopL3 --> SignallingLinkFailed[Signalling
+link failed
+LSAC → TLAC]
+ SignallingLinkFailed --> LinkFailed[Link failed
+LSAC → LLSC]
+ LinkFailed --> Failed
+ subgraph DashedBox [Only required if retrieval cannot be carried out in parallel with signalling link restoration]
+ Failed([Failed]) --> STMReady[STM ready
+TCOC → LSAC]
+ end
+ STMReady --> StartRestoration[Start
+restoration
+LSAC → LSLR]
+ StartRestoration --> ActivatingRestoring([Activating/
+restoring])
+
+```
+
+Flowchart for signalling link management (LSAC) showing states: Active, Out of service, Failed, and Activating/restoring. Transitions include Stop L2, Changeover order received, Stop L3, Signalling link failed, Link failed, STM ready, and Start restoration.
+
+T1160230-94/d124
+
+**Figure 37/Q.704 (sheet 7 of 10) – Signalling link management; signalling link activity control (LSAC)**
+
+
+
+5, 6
+
+```
+
+graph TD
+ 5((5
+7)) --> D1[Deactivate link
+LLSC → LSAC]
+ 5 --> D2[Deactivate link
+MGMT → LSAC]
+ D2 --> A1[Activate another link
+LSAC → LLSC]
+ D1 --> S1[Signalling link failed
+LSAC → TLAC]
+ A1 --> S1
+ S1 --> W1([Wait])
+ W1 --> R1[STM ready
+TCOC → LSAC]
+ R1 --> F1[Link failed
+LSAC → LLSC]
+ F1 --> ST1[Stop
+L3 → L2]
+ ST1 --> DL1[Deactivate link
+LSAC → LSLD]
+ DL1 --> LI1[Link inactive
+LSAC → LLSC]
+ LI1 --> I1([Inactive])
+ 6((6
+9))
+
+```
+
+T1160240-94/d125
+
+Flowchart for Signalling link management; signalling link activity control (LSAC). The process starts at node 5 (labeled 7) and ends at node 6 (labeled 9). It includes steps for deactivating links, signaling failure, waiting, STM readiness, link failure handling, stopping L3, and finally becoming inactive.
+
+**Figure 37/Q.704 (sheet 8 of 10) – Signalling link management;
+signalling link activity control (LSAC)**
+
+
+
+6, 7
+
+6 8 7 10
+
+```
+
+stateDiagram-v2
+ [*] --> 6
+ 6 --> 7
+ 6 --> Emergency_LLSC_LSAC : Emergency LLSC → LSAC
+ Emergency_LLSC_LSAC --> Mark_emergency : Mark emergency
+ 6 --> Emergency_ceases_LSAC : Emergency ceases LLSC → LSAC
+ Emergency_ceases_LSAC --> Cancel_emergency : Cancel emergency
+ 6 --> Flush_buffers_TLAC_LSAC : Flush buffers TLAC → LSAC
+ Flush_buffers_TLAC_LSAC --> Flush_buffers_L3_L2 : Flush buffers L3 → L2
+ 6 --> Continue_TLAC_LSAC : Continue TLAC → LSAC
+ Continue_TLAC_LSAC --> Continue_L3_L2 : Continue L3 → L2
+ Mark_emergency --> Active
+ Cancel_emergency --> Active
+ Flush_buffers_L3_L2 --> Active
+ Continue_L3_L2 --> Active
+
+```
+
+T1143080-92/d126
+
+State transition diagram for signalling link management (LSAC) emergency handling. It shows transitions between states triggered by LLSC, TLAC, and L3 messages, leading to an 'Active' state.
+
+**Figure 37/Q.704 (sheet 9 of 10) – Signalling link management; signalling link activity control (LSAC)**
+
+
+
+7
+
+7 9
+
+```
+
+stateDiagram-v2
+ [*] --> 7
+ 7 --> Remote_processor_outage_L2_L3 : Remote processor outage L2 → L3
+ Remote_processor_outage_L2_L3 --> Remote_processor_outage_LSAC_TLAC : Remote processor outage LSAC → TLAC
+ 7 --> Remote_processor_recovered_L2_L3 : Remote processor recovered L2 → L3
+ Remote_processor_recovered_L2_L3 --> Remote_processor_recovered_LSAC_TLAC : Remote processor recovered LSAC → TLAC
+ Remote_processor_outage_LSAC_TLAC --> Active
+ Remote_processor_recovered_LSAC_TLAC --> Active
+
+```
+
+T1160250-94/d127
+
+State transition diagram for signalling link management (LSAC) remote processor handling. It shows transitions between states triggered by L2, L3, and LSAC messages, leading to an 'Active' state.
+
+NOTE – See sheet 10 bis, for a national option.
+
+**Figure 37/Q.704 (sheet 10 of 10) – Signalling link management; signalling link activity control (LSAC)**
+
+
+
+7
+
+9
+
+```
+
+graph TD
+ Start((7)) --> Path1[Local processor outage
+TLAC → LSAC]
+ Start --> Path2[Local processor recovered
+TLAC → LSAC]
+ Start --> Path3[Remote processor outage
+L2 → L3]
+ Start --> Path4[Remote processor recovered
+L2 → L3]
+ Path1 --> Action1[Mark local processor outage]
+ Action1 --> State1[Local processor outage
+L3 → L2]
+ Path2 --> Action2[Cancel local processor outage]
+ Action2 --> State2[Local processor recovered
+L3 → L2]
+ Path3 --> State3[Remote processor outage
+LSAC → TLAC]
+ Path4 --> State4[Remote processor recovered
+LSAC → TLAC]
+ State1 --> Active([Active])
+ State2 --> Active
+ State3 --> Active
+ State4 --> Active
+
+```
+
+T1160260-94/d128
+
+Flowchart for signalling link management (LSAC) showing four parallel paths: Local processor outage (TLAC to LSAC), Local processor recovered (TLAC to LSAC), Remote processor outage (L2 to L3), and Remote processor recovered (L2 to L3). Each path leads to a specific action and then to a state transition (L3 to L2 or LSAC to TLAC), all converging to an 'Active' state.
+
+**Figure 37/Q.704 (sheet 10 bis of 10) – Signalling link management;
+signalling link activity control (LSAC)
+(National option)**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --- Start[Start activation
+LSAC → LSLA]
+ Idle1 --- Restart[Restart activation
+LSAC → LSLA]
+
+ Start --> T{Terminal
+predetermined?}
+ T -.-> T_note[Terminal is predetermined
+in the case when automatic
+allocation of terminals is
+not implemented]
+ T -- Yes --> C1((1))
+ T -- No --> D1[Determine
+terminal
+LSLA → LSTA]
+
+ D1 --> DL{Data link
+predetermined?}
+ DL -.-> DL_note[Data link is predetermined in the case
+when automatic allocation of data links
+is not implemented and also in link set
+restart situations]
+ DL -- Yes --> Wait
+ DL -- No --> D2[Determine
+data link
+LSLA → LSDA]
+
+ D2 --> Wait([Wait])
+
+ C1 --- C2((2))
+
+ Restart --> R{Replace
+data link?}
+ R -.-> R_note[Possible only when automatic
+allocation of data links is
+implemented decided according
+to application dependent rules]
+ R -- No --> A[Activation
+unsuccessful
+LSLA → LSAC]
+ R -- Yes --> D3[Determine
+data link
+LSLA → LSDA]
+
+ A --> S[Start
+signalling link
+LSLA → LSAC]
+ S --> Idle2([Idle])
+
+ D3 --> Wait
+
+```
+
+1
+
+2
+
+T1160270-94/d129
+
+Flowchart for signalling link activation (LSLA) showing two main paths: Start activation and Restart activation. Both paths lead to a 'Wait' state, with one path potentially returning to 'Idle' via a connector.
+
+**Figure 38/Q.704 (sheet 1 of 3) – Signalling link management;
+signalling link activation (LSLA)**
+
+
+
+```
+
+graph TD
+ Wait1([Wait]) --> In1{{Data link
+LSDA → LSLA}}
+ Wait1 --> In2{{Terminal
+LSTA → LSLA}}
+ Wait1 --> C2((2))
+
+ In1 --> P1[Mark
+data link
+determined]
+ P1 --> D1{Terminal
+determined?}
+ D1 -- No --> Wait2([Wait])
+ D1 -- Yes --> In3{{Connect
+L3 → L1}}
+
+ In2 --> P2[Mark
+terminal
+determined]
+ P2 --> D2{Data link
+determined?}
+ D2 -- No --> Wait2
+ D2 -- Yes --> C1((1))
+
+ C1_in((1)) --> In3
+ In3 --> In4{{Start
+signalling link
+LSLA → LSAC}}
+ In4 --> P3[Cancel
+terminal
+determined]
+ P3 --> P4[Cancel
+terminal
+determined]
+ P4 --> Idle([Idle])
+
+ C3((3)) --> P3
+
+```
+
+Detailed description of the flowchart:
+ The process starts at a 'Wait' state. From here, two parallel inputs are possible: 'Data link LSDA → LSLA' or 'Terminal LSTA → LSLA'.
+ If 'Data link LSDA → LSLA' is received, the process 'Mark data link determined' occurs, followed by a decision 'Terminal determined?'. If 'No', it enters another 'Wait' state. If 'Yes', it proceeds to 'Connect L3 → L1'.
+ If 'Terminal LSTA → LSLA' is received, the process 'Mark terminal determined' occurs, followed by a decision 'Data link determined?'. If 'No', it enters the 'Wait' state. If 'Yes', it goes to connector (1), which leads to 'Connect L3 → L1'.
+ From 'Connect L3 → L1', the signal 'Start signalling link LSLA → LSAC' is sent. Then, two sequential processes 'Cancel terminal determined' occur (notably, the text is identical for both boxes). Finally, the process reaches the 'Idle' state.
+ There are also external connectors: (2) from the initial 'Wait' line, (3) entering before the first 'Cancel terminal determined' process, and (1) entering before 'Connect L3 → L1'.
+
+Flowchart for Signalling link activation (LSLA)
+
+T1160280-94/d130
+
+**Figure 38/Q.704 (sheet 2 of 3) – Signalling link management;
+signalling link activation (LSLA)**
+
+**Recommendation Q.704 (07/96)** 183
+
+
+
+```
+
+graph TD
+ Start((2)) --> NoDataLink{No data link
+LSDA → LSLA}
+ NoDataLink --> NoTerminal{No terminal
+LSTA → LSLA}
+ NoTerminal --> DeactivateLink{Deactivate link
+LSAC → LSLA}
+ DeactivateLink --> ActivationNotPossible{Activation not possible
+LSLA → LSAC}
+ ActivationNotPossible --> End((3))
+ End --- Note2[2]
+ Note1[2] --- Start
+
+```
+
+This flowchart illustrates the process for signalling link activation (LSLA). It begins at a connector labeled '2'. The first decision point is 'No data link LSDA → LSLA'. If this condition is met, the process moves to 'No terminal LSTA → LSLA'. If this second condition is met, the process moves to 'Deactivate link LSAC → LSLA'. From there, it moves to 'Activation not possible LSLA → LSAC', which then leads to connector '3'. A note '2' is associated with connector '3'.
+
+Flowchart for signalling link activation (LSLA)
+
+T1160290-94/d131
+
+**Figure 38/Q.704 (sheet 3 of 3) – Signalling link management; signalling link activation (LSLA)**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> StartRestoration1{Start restoration
+LSAC → LSLR}
+ Idle1 --> StartRestoration2{Restart restoration
+LSAC → LSLR}
+ StartRestoration1 --> StartSignallingLink1{Start signalling link
+LSLR → LSAC}
+ StartSignallingLink1 --> Idle2([Idle])
+ StartRestoration2 --> ReplaceTerminal{Replace terminal?}
+ ReplaceTerminal -- Yes --> Note1[Possible only when automatic allocation of terminals is implemented; decided according to application dependent rules]
+ Note1 --> DetermineTerminal{Determine terminal
+LSLR → LSTA}
+ DetermineTerminal --> WaitTerminal([Wait for terminal])
+ ReplaceTerminal -- No --> ReplaceDataLink{Replace data link?}
+ ReplaceDataLink -- Yes --> DetermineDataLink{Determine data link
+LSLR → LSDA}
+ DetermineDataLink --> WaitDataLink([Wait for data link])
+ ReplaceDataLink -- No --> Note2[Possible only when automatic allocation of data links is implemented; decided according to application dependent rules]
+ Note2 --> RestorationUnsuccessful{Restoration unsuccessful
+LSLR → LSAC}
+ RestorationUnsuccessful --> StartSignallingLink2{Start signalling link
+LSLR → LSAC}
+ StartSignallingLink2 --> Idle3([Idle])
+
+```
+
+This flowchart illustrates the process for signalling link restoration (LSLR). It starts from an 'Idle' state. There are two initial actions: 'Start restoration LSAC → LSLR' and 'Restart restoration LSAC → LSLR'. The 'Start restoration' path leads to 'Start signalling link LSLR → LSAC' and then back to 'Idle'. The 'Restart restoration' path leads to a decision 'Replace terminal?'. If 'Yes', a note indicates this is only possible with automatic terminal allocation, followed by 'Determine terminal LSLR → LSTA' and 'Wait for terminal'. If 'No', it leads to 'Replace data link?'. If 'Yes', it leads to 'Determine data link LSLR → LSDA' and 'Wait for data link'. If 'No', a note indicates this is only possible with automatic data link allocation, followed by 'Restoration unsuccessful LSLR → LSAC', 'Start signalling link LSLR → LSAC', and finally 'Idle'.
+
+Flowchart for signalling link restoration (LSLR)
+
+T1160300-94/d132
+
+**Figure 39/Q.704 (sheet 1 of 2) – Signalling link management; signalling link restoration (LSLR)**
+
+
+
+```
+
+graph TD
+ WDL([Wait for data link])
+ WT([Wait for terminal])
+
+ WDL --> DL_IN{{Data link
+LSDA → LSLR}}
+ WDL --> NDL_IN{{No data link
+LSDA → LSLR}}
+
+ WT --> NT_IN{{No terminal
+LSTA → LSLR}}
+ WT --> T_IN{{Terminal
+LSTA → LSLR}}
+
+ DL_IN --> C1((1))
+ C1 --> CONN[Connect
+L3 → L1]
+ CONN --> SL1{{Start
+signalling link
+LSLR → LSAC}}
+ SL1 --> IDLE([Idle])
+
+ NDL_IN --> NT_IN
+ NT_IN --> RU{{Restoration
+unsuccessful
+LSLR → LSAC}}
+ RU --> SL2{{Start
+signalling link
+LSLR → LSAC}}
+ SL2 --> IDLE
+
+ T_IN --> C2((1))
+ %% Note: The '2' below the circle in the image is a page/sheet reference or connector label
+
+```
+
+Specified terminal
+and data link
+
+SDL Flowchart for Signalling link restoration (LSLR). The process starts from two states: 'Wait for data link' and 'Wait for terminal'. From 'Wait for data link', it can receive 'Data link LSDA → LSLR' or 'No data link LSDA → LSLR'. 'Data link' leads to a connector (1) then to 'Connect L3 → L1' and 'Start signalling link LSLR → LSAC' ending in 'Idle'. 'No data link' leads to the 'No terminal' path. From 'Wait for terminal', it can receive 'No terminal LSTA → LSLR' or 'Terminal LSTA → LSLR'. 'No terminal' leads to 'Restoration unsuccessful LSLR → LSAC' then 'Start signalling link LSLR → LSAC' ending in 'Idle'. 'Terminal' leads to connector (1) with a (2) below it.
+
+T1160310-94/d133
+
+**Figure 39/Q.704 (sheet 2 of 2) – Signalling link management;
+signalling link restoration (LSLR)**
+
+
+
+```
+graph TD; Idle1([Idle]) --> Deactivate[Deactivate link LSAC -> LSLD]; Deactivate --> Disconnect[Disconnect L3 -> L1]; Disconnect --> DataLink[Data link available LSLD -> LSDA]; DataLink --> TerminalIdle[Terminal idle LSLD -> LSTA]; TerminalIdle --> Idle2([Idle])
+```
+
+Flowchart of signalling link management for deactivation (LSLD). The sequence starts at 'Idle', followed by 'Deactivate link LSAC -> LSLD', 'Disconnect L3 -> L1', 'Data link available LSLD -> LSDA', 'Terminal idle LSLD -> LSTA', and ends at 'Idle'.
+
+T1160320-94/d134
+
+**Figure 40/Q.704 – Signalling link management; signalling link deactivation (LSLD)**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> D1[/Determine terminal LSLA -> LSTA/]
+ Idle1 --> D2[/Determine terminal LSLR -> LSTA/]
+ Idle1 --> D3[/Terminal idle LSLD -> LSTA/]
+ Idle1 --> D4[/Terminal available LSAC -> LSTA/]
+
+ D1 --> M1[Mark activation]
+ D2 --> M2[Mark restoration]
+ D3 --> M3[Mark terminal idle]
+ D4 --> M4[Mark terminal available]
+
+ M3 --> Idle2([Idle])
+ M4 --> Idle2
+
+ M1 --> Q1{Any terminals idle?}
+ M2 --> Q1
+
+ Q1 -- Yes --> S1[Select terminal]
+ S1 --> C1((1))
+
+ Q1 -- No --> Q2{Any terminals available?}
+
+ Q2 -- Yes --> S2[Select terminal]
+ S2 --> C2((2))
+
+ Q2 -- No --> Q3{Activation or restoration?}
+
+ Q3 -- Restoration --> N1[/No terminal LSTA -> LSLR/]
+ N1 --> C2
+
+ Q3 -- Activation --> N2[/No terminal LSTA -> LSLA/]
+ N2 --> C2
+
+ C1 --> D5[/Deactivate link LSTA -> LSAC/]
+ C2 --> D5
+
+ D5 --> Wait([Wait])
+
+```
+
+Terminal associated with unsuccessfully activated and restored link
+
+Terminal associated with unsuccessfully activated or restored link
+
+Deactivate the link which is associated with the selected terminal
+
+T1160330-94/d135
+
+Flowchart for signalling link management; signalling terminal allocation (LSTA). The process starts at 'Idle' and branches into four parallel paths: 'Determine terminal LSLA -> LSTA' (Mark activation), 'Determine terminal LSLR -> LSTA' (Mark restoration), 'Terminal idle LSLD -> LSTA' (Mark terminal idle), and 'Terminal available LSAC -> LSTA' (Mark terminal available). A note indicates that terminals associated with unsuccessfully activated and restored links are handled in the 'Mark activation' and 'Mark restoration' paths. The 'Mark terminal idle' and 'Mark terminal available' paths lead to another 'Idle' state. The 'Mark activation' and 'Mark restoration' paths lead to a decision 'Any terminals idle?'. If 'Yes', it leads to 'Select terminal' and then to connector '1'. If 'No', it leads to another decision 'Any terminals available?'. A note indicates that terminals associated with unsuccessfully activated or restored links are handled in the 'Any terminals available?' decision. If 'Yes', it leads to 'Select terminal' and then to connector '2'. If 'No', it leads to a decision 'Activation or restoration?'. If 'Restoration', it leads to 'No terminal LSTA -> LSLR' and then to connector '2'. If 'Activation', it leads to 'No terminal LSTA -> LSLA' and then to connector '2'. Both connectors '1' and '2' lead to a decision 'Deactivate link LSTA -> LSAC'. A note indicates that the link associated with the selected terminal is deactivated. The process ends at 'Wait'.
+
+**Figure 41/Q.704 (sheet 1 of 2) – Signalling link management; signalling terminal allocation (LSTA)**
+
+
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> D1{Determine data link
+LSLA → LSDA}
+ D1 --> M1[Mark activation]
+ M1 --> AR1{Alternative routing data request
+LSDA → TSRC}
+ AR1 --> Wait1([Wait])
+
+ Idle1 --> D2{Determine data link
+LSLR → LSDA}
+ D2 --> M2[Mark restoration]
+ M2 --> AR2{Alternative routing data request
+LSDA → TSRC}
+ AR2 --> Wait1
+
+ Idle1 --> D3{Data link available
+LSLD → LSDA}
+ D3 --> M3[Mark data link available]
+ M3 --> Idle2([Idle])
+
+ Idle1 --> D4{Signalling data link connection order
+HMDT → LSDA}
+ D4 --> AR3{Alternative routing data request
+LSDA → TSRC}
+ AR3 --> Waiting1([Waiting])
+
+ subgraph FromRemoteLevel3 [From remote level 3]
+ D4
+ end
+
+```
+
+T1160350-94/d137
+
+Flowchart for signalling link management; signalling data link allocation (LSDA). The diagram shows four parallel paths starting from an 'Idle' state. Path 1: 'Determine data link LSLA → LSDA' leads to 'Mark activation', which then leads to 'Alternative routing data request LSDA → TSRC' and finally 'Wait'. Path 2: 'Determine data link LSLR → LSDA' leads to 'Mark restoration', which also leads to 'Alternative routing data request LSDA → TSRC'. Path 3: 'Data link available LSLD → LSDA' leads to 'Mark data link available', which returns to the 'Idle' state. Path 4: 'Signalling data link connection order HMDT → LSDA' (triggered 'From remote level 3') leads to 'Alternative routing data request LSDA → TSRC', which finally leads to 'Waiting'. A common vertical line on the left side of the diagram.
+
+**Figure 42/Q.704 (sheet 1 of 4) – Signalling link management;
+signalling data link allocation (LSDA)**
+
+190 Recommendation Q.704 (07/96)
+
+
+
+```
+
+ graph TD
+ %% States
+ Wait1([Wait])
+ Wait2([Wait])
+ Waiting1([Waiting])
+ Waiting2([Waiting])
+ WaitingForConn([Waiting for connection])
+ Idle([Idle])
+
+ %% Inputs/Outputs
+ DL_Avail_LSLD_LSDA1{{Data link available
+LSLD → LSDA}}
+ Alt_Routing_TSRC_LSDA1{{Alternative routing data
+TSRC → LSDA}}
+ Sig_Data_Conn_HMDT_LSDA{{Signalling data link connection order
+HMDT → LSDA}}
+ Alt_Routing_TSRC_LSDA2{{Alternative routing data
+TSRC → LSDA}}
+ DL_Avail_LSLD_LSDA2{{Data link available
+LSLD → LSDA}}
+ Sig_Data_Conn_LSDA_HMRT{{Signalling data link connection order
+LSDA → HMRT}}
+ DL_LSDA_LSAC{{Data link
+LSDA → LSAC}}
+ Conn_Succ_LSDA_HMRT{{Connection successful
+LSDA → HMRT}}
+ Conn_Not_Succ_LSDA_HMRT{{Connection not successful
+LSDA → HMRT}}
+ Conn_Not_Poss_LSDA_HMRT{{Connection not possible
+LSDA → HMRT}}
+
+ %% Actions
+ Mark_DL_Avail1[Mark data link available]
+ Mark_DL_Avail2[Mark data link available]
+ Select_DL[Select data link]
+ Start_T7[Start T7]
+
+ %% Decisions
+ DL_Avail_Q{Data link available?}
+ Indicated_DL_Avail_Q{Indicated data link available?}
+ Another_DL_Avail_Q{Another data link available?}
+
+ %% Connectors
+ C1((1))
+ C2((2))
+ C3((3))
+ C4((4))
+
+ %% Flow
+ Wait1 --- DL_Avail_LSLD_LSDA1
+ DL_Avail_LSLD_LSDA1 --> Mark_DL_Avail1
+ Mark_DL_Avail1 --> Wait2
+
+ Wait1 --- Alt_Routing_TSRC_LSDA1
+ Alt_Routing_TSRC_LSDA1 --> DL_Avail_Q
+ DL_Avail_Q -- Yes --> Select_DL
+ DL_Avail_Q -- No --> C4
+
+ Wait1 --- Sig_Data_Conn_HMDT_LSDA
+ Sig_Data_Conn_HMDT_LSDA --> DL_Avail_Q
+
+ Select_DL --> Sig_Data_Conn_LSDA_HMRT
+ Sig_Data_Conn_LSDA_HMRT --> Start_T7
+ Start_T7 --> WaitingForConn
+
+ Waiting1 --- Alt_Routing_TSRC_LSDA2
+ Alt_Routing_TSRC_LSDA2 --> Indicated_DL_Avail_Q
+
+ Waiting1 --- DL_Avail_LSLD_LSDA2
+ DL_Avail_LSLD_LSDA2 --> Mark_DL_Avail2
+ Mark_DL_Avail2 --> Waiting2
+
+ Indicated_DL_Avail_Q -- Yes --> DL_LSDA_LSAC
+ Indicated_DL_Avail_Q -- No --> Another_DL_Avail_Q
+
+ Another_DL_Avail_Q -- Yes --> DL_LSDA_LSAC
+ Another_DL_Avail_Q -- No --> Conn_Not_Poss_LSDA_HMRT
+
+ DL_LSDA_LSAC --> Conn_Succ_LSDA_HMRT
+ DL_LSDA_LSAC --> Conn_Not_Succ_LSDA_HMRT
+
+ Conn_Succ_LSDA_HMRT --> Idle
+ Conn_Not_Succ_LSDA_HMRT --> Idle
+ Conn_Not_Poss_LSDA_HMRT --> Idle
+
+ %% Logical links (dashed)
+ C1 -.-> Alt_Routing_TSRC_LSDA1
+ C4 -.-> Alt_Routing_TSRC_LSDA2
+ Sig_Data_Conn_HMDT_LSDA -.-> |From remote level 3| Sig_Data_Conn_HMDT_LSDA
+ C4 -.-> |Identifies alternative link to be used for routing link management messages| Alt_Routing_TSRC_LSDA2
+ Start_T7 -.-> |To remote level 3 Alternative routing data included for use by local HMRT| Conn_Succ_LSDA_HMRT
+
+```
+
+Figure 42/Q.704 (sheet 2 of 4) – Signalling link management; signalling data link allocation (LSDA) flowchart
+
+**Figure 42/Q.704 (sheet 2 of 4) – Signalling link management; signalling data link allocation (LSDA)**
+
+T1160360-94/d138
+
+
+
+```
+
+graph TD
+ Start([Waiting for connection]) --> DLA{Data link available LSLD → LSDA}
+ Start --> CS[Connection successful HMDT → LSDA]
+ Start --> CNS[Connection not successful HMDT → LSDA]
+ Start --> CNP[Connection not possible HMDT → LSDA]
+ DLA --> MDL[Mark data link available]
+ MDL --> WFC([Waiting for connection])
+ CS --> ST7_1[Stop T7]
+ CNS --> ST7_2[Stop T7]
+ CNP --> ST7_3[Stop T7]
+ ST7_1 --> AR1{Activation or restoration?}
+ ST7_2 --> AR2{Activation or restoration?}
+ ST7_3 --> AR3{Activation or restoration?}
+ AR1 -- Restoration --> DL1[Data link LSDA → LSLR]
+ AR1 -- Activation --> DL2[Data link LSDA → LSLA]
+ AR2 -- Restoration --> DL3[No data link LSDA → LSLR]
+ AR2 -- Activation --> DL4[No data link LSDA → LSLA]
+ AR3 -- Restoration --> DL5[Data link LSDA → LSLR]
+ AR3 -- Activation --> DL6[Data link LSDA → LSLA]
+ DL1 --> CA[Cancel activation]
+ DL2 --> CA
+ DL3 --> CR[Cancel restoration]
+ DL4 --> CR
+ DL5 --> CR
+ DL6 --> CR
+ CA --> CR
+ CR --> Idle([Idle])
+ WFC --> 6((6))
+ AR1 --> 5((5))
+ AR2 --> 1((1))
+ AR3 --> 4((4))
+ 5 --> 4
+ 1 --> 2
+ 4 --> 2
+ 2 --> 3
+ 3 --> 4
+ 4 --> 6
+ 6 --> 4
+ subgraph RemoteLevel3 [From remote level 3]
+ 6
+ 4
+ end
+
+```
+
+The flowchart illustrates the signalling link management and signalling data link allocation (LSDA) process. It begins with a 'Waiting for connection' state, which leads to four possible outcomes: 'Data link available LSLD → LSDA', 'Connection successful HMDT → LSDA', 'Connection not successful HMDT → LSDA', and 'Connection not possible HMDT → LSDA'. The 'Data link available' path leads to 'Mark data link available' and back to 'Waiting for connection'. The other three paths lead to 'Stop T7' states. From these 'Stop T7' states, the process moves to an 'Activation or restoration?' decision. If 'Restoration' is chosen, the path leads to 'Data link LSDA → LSLR' or 'No data link LSDA → LSLR'. If 'Activation' is chosen, the path leads to 'Data link LSDA → LSLA' or 'No data link LSDA → LSLA'. All four paths then lead to 'Cancel activation' or 'Cancel restoration' states, which both lead to the final 'Idle' state. There are also connector symbols (circles with numbers) and a dashed line indicating a connection to 'From remote level 3'.
+
+Flowchart for signalling link management and signalling data link allocation (LSDA).
+
+T1160370-94/d139
+
+**Figure 42/Q.704 (sheet 3 of 4) – Signalling link management; signalling data link allocation (LSDA)**
+
+
+
+```
+
+graph TD
+ Start((6
+3)) --> HMDT[Signalling data link connection order HMDT → LSDA]
+ T7[— T7] --> HMDT
+ HMDT --> LocalSP{Local SP controlling?}
+ LocalSP -- Yes --> C3((3
+2))
+ LocalSP -- No --> StopT7[Stop T7]
+ StopT7 --> Indicated{Indicated data link available?}
+ Indicated -- Yes --> Success[Connection successful LSDA → HMRT]
+ Indicated -- No --> Another{Another data link possible?}
+ Another -- Yes --> NotSuccess[Connection not successful LSDA → HMRT]
+ Another -- No --> NotPossible[Connection not possible LSDA → HMRT]
+ Success --> C5((5
+3))
+ NotSuccess --> C3_2((3
+2))
+ NotPossible --> C4((4
+3))
+ SelectNew{Select new data link?} -- Yes --> C1((1
+2))
+ SelectNew -- No --> C2((2
+2))
+ HMDT -.-> Remote3[From remote level 3]
+ Success -.-> Remote3_2[To remote level 3]
+ NotSuccess -.-> Remote3_2
+ NotPossible -.-> Remote3_2
+
+```
+
+Flowchart for signalling link management; signalling data link allocation (LSDA). The process starts with 'Signalling data link connection order HMDT -> LSDA' and 'T7'. It branches based on 'Local SP controlling?' and 'Select new data link?'. If 'Local SP controlling?' is Yes, it goes to connector 3. If No, it goes to 'Stop T7'. From 'Stop T7', it checks 'Indicated data link available?'. If Yes, it goes to 'Connection successful LSDA -> HMRT' (connector 5). If No, it checks 'Another data link possible?'. If Yes, it goes to 'Connection not successful LSDA -> HMRT' (connector 3). If No, it goes to 'Connection not possible LSDA -> HMRT' (connector 4). 'Select new data link?' Yes leads to connector 1, and No leads to connector 2. External connections are 'From remote level 3' and 'To remote level 3'. Connector numbers and levels are: 6 (3), 3 (2), 1 (2), 2 (2), 4 (3), 3 (2), 5 (3).
+
+**Figure 42/Q.704 (sheet 4 of 4) – Signalling link management; signalling data link allocation (LSDA)**
+
+T1160380-94/d140
+
+
+
+The diagram illustrates the functional block interactions for Level 3 Signalling route management (SRM). It shows three main control blocks: Transfer prohibited control (RTPC) Figure 44, Signalling route set test control (RSRT) Figure 46, and Transfer allowed control (RTAC) Figure 45. These blocks are connected to various external entities and internal message flows.
+
+- External Inputs:**
+ - From signalling message handling (SMH) provides a "Message received for inaccessible SP" to the RTPC block.
+ - From/to remote level 3 (L3) provides "Transfer prohibited" and "Transfer allowed" signals to the RTPC and RTAC blocks respectively.
+ - From/to remote level 3 (L3) provides "Signalling route set test" signals to the RSRT block.
+- Internal Message Flows:**
+ - The RTPC block sends a "Send transfer prohibited message" to the RSRT block.
+ - The RSRT block sends a "Send transfer allowed message" to the RTAC block.
+- Internal Control Interactions:**
+ - The RSRT block has bidirectional dashed connections with the RTPC block for "Controlled rerouting terminated", "Destination inaccessible", "Send transfer prohibited message", and "Restart begins/ends".
+ - The RSRT block has bidirectional dashed connections with the RTAC block for "Signalling route available" and "Restart begins/ends".
+ - The RSRT block has bidirectional dashed connections with the "RTRC" block for "Send transfer restricted message", "Accessibility data", "Start route set test", "Adjacent SP restarting", "Adjacent SP restarted", "Restart begins/ends", "Accessibility data request", and "Start route set test".
+ - The RTAC block has bidirectional dashed connections with the "RTRC" block for "Forced rerouting", "Forced rerouting not required", "Forced rerouting terminated", "Destination accessible", "STP no longer used for destination", and "Restart begins/ends".
+ - The RTAC block has bidirectional dashed connections with "To/from signalling traffic management (STM)" for "Signalling route available".
+- External Outputs:**
+ - The RTPC block sends "Transfer prohibited" signals to/to remote level 3 (L3).
+ - The RSRT block sends "Signalling route set test" signals to/to remote level 3 (L3).
+ - The RTAC block sends "Transfer allowed" signals to/to remote level 3 (L3).
+ - The RTAC block sends "To/from signalling traffic management (STM)" signals.
+
+Functional block interactions diagram for Level 3 Signalling route management (SRM).
+
+T1160390-94/d141
+
+NOTE – Abbreviated message names have been used in this diagram (i.e. origin →destination codes have been omitted).
+
+Figure 43/Q.704 (sheet 1 of 2) – Level 3 – Signalling route management (SRM); functional block interactions
+
+
+
+The diagram illustrates the functional block interactions for Level 3 Signalling route management (SRM), organized into three main horizontal sections:
+
+- Transfer Restricted (TR) Section:**
+ - External inputs/outputs: "To/from remote level 3 (L3)" (Transfer restricted).
+ - Internal control blocks: "Send transfer restricted" and "Start route set test" (RSRT).
+ - Main functional block: "Transfer restricted control (RTRC)" (Figure 46c).
+ - Interactions with STM: "Send transfer restricted message" (Destination restricted, Restart begins/ends) from STM; "Signalling route restricted" to STM.
+- Transfer Controlled (TC) Section:**
+ - External inputs/outputs: "To/from remote level 3 (L3)" (Transfer controlled, User part unavailable).
+ - Main functional block: "Transfer controlled control (RTCC)" (Figure 46a).
+ - Interactions with STM: "Send transfer controlled message" from STM; "Destination congestion, Distant user part unavailable" and "Destination congestion status" to STM.
+ - Interactions with SMH: "Send transfer controlled message" from SMH (via MCS).
+- Signalling Route Set Congestion Test (RCAT) Section:**
+ - External inputs/outputs: "To/from remote level 3 (L3)" (Signalling route set Congestion test).
+ - Main functional block: "Signalling route set congestion test control (RCAT)" (Figure 46b).
+ - Interactions with STM: "Start congestion test, Stop congestion test" from STM; "Decrement destination Congestion status" to STM.
+ - Internal MCS block: "MCS" (Management Control Signal).
+
+T1132050-91/d142
+
+Functional block interactions diagram for Level 3 Signalling route management (SRM).
+
+Figure 43/Q.704 (sheet 2 of 2) – Level 3 – Signalling route management (SRM); functional block interactions
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> State1((1))
+ State1 --> Action1[/Message received for inaccessible SP
+HMRT -> RTPC/]
+ State1 --> Action2[/Send transfer prohibited message
+RSRT -> RTPC/]
+ State1 --> Action3[/Send transfer prohibited message
+TSRC -> RTPC/]
+ State1 --> Action4[/Destination inaccessible
+TSRC -> RTPC/]
+ Action1 --> TransferLeft[/Transfer prohibited
+RTPC -> HMRT/]
+ Action2 --> TransferLeft
+ Action3 --> TransferRight[/Transfer prohibited
+RTPC -> HMRT/]
+ Action4 --> TransferRight
+ TransferLeft --> ToConcerned[To concerned SP or STP]
+ TransferLeft -.-> ToRemote[To remote level 3]
+ TransferRight --> ToAll[To all adjacent SPs]
+ ToConcerned --> StartT8[/Start T8/]
+ ToRemote -.-> StartT8
+ ToAll --> StartT8
+ StartT8 --> Wait([Wait])
+ Wait --> T8[/T8/]
+ T8 --> Idle2([Idle])
+ subgraph Legend
+ direction TB
+ L1((1))
+ L2((2))
+ end
+ Ref[T1160400-94/d143]
+
+```
+
+Flowchart for Signalling route management; transfer prohibited control (RTPC). The process starts at an 'Idle' state, transitions to state '1' (indicated by a circle with '1' and a label '2' nearby), then branches into four parallel actions: 'Message received for inaccessible SP HMRT -> RTPC', 'Send transfer prohibited message RSRT -> RTPC', 'Send transfer prohibited message TSRC -> RTPC', and 'Destination inaccessible TSRC -> RTPC'. These lead to 'Transfer prohibited RTPC -> HMRT' blocks. The left block has outputs 'To concerned SP or STP' and 'To remote level 3' (via a dashed line). The right block has an output 'To all adjacent SPs'. Both lead to 'Start T8', then 'Wait', then a 'T8' timer symbol, and finally back to an 'Idle' state. A reference code 'T1160400-94/d143' is at the bottom left.
+
+**Figure 44/Q.704 (sheet 1 of 3) – Signalling route management;
+transfer prohibited control (RTPC)**
+
+
+
+The flowchart illustrates the signalling route management process for transfer prohibited control (RTPC). It begins at a connector labeled '1'. From this connector, three parallel paths emerge, each starting with a chevron-shaped process block: 'Transfer prohibited HMDT → RTPC', 'Controlled rerouting terminated TCRC → RTPC', and 'Controlled rerouting RTAC → RTPC'. The first path leads to a decision diamond 'Controlled rerouting in progress?'. If 'Yes', it goes to a rectangular process block 'Mark transfer prohibited'. If 'No', it proceeds to a chevron-shaped process block 'Signalling route unavailable RTPC → TSRC'. The second path from the initial connector leads to a rectangular process block 'Cancel controlled rerouting in progress', which then leads to a decision diamond 'Transfer prohibited?'. If 'Yes', it goes to a rectangular process block 'Cancel transfer prohibited'. If 'No', it bypasses this block. The third path from the initial connector leads to a rectangular process block 'Mark controlled rerouting in progress'. All three paths (from 'Mark transfer prohibited', 'Cancel transfer prohibited', and 'Mark controlled rerouting in progress') converge to the 'Signalling route unavailable RTPC → TSRC' block. From this block, the flow proceeds to a decision diamond 'SP restarting?'. If 'Yes', it bypasses the next block. If 'No', it goes to a chevron-shaped process block 'Start route set test RTPC → RSRT'. Both the 'SP restarting?' 'Yes' path and the 'Start route set test' block lead to a final oval-shaped terminal block labeled 'Idle'.
+
+```
+graph TD; C1((1)) --> P1[/Transfer prohibited HMDT -> RTPC/]; C1 --> P2[/Controlled rerouting terminated TCRC -> RTPC/]; C1 --> P3[/Controlled rerouting RTAC -> RTPC/]; P1 --> D1{Controlled rerouting in progress?}; D1 -- Yes --> P4[Mark transfer prohibited]; D1 -- No --> P5[/Signalling route unavailable RTPC -> TSRC/]; P2 --> P6[Cancel controlled rerouting in progress]; P6 --> D2{Transfer prohibited?}; D2 -- Yes --> P7[Cancel transfer prohibited]; D2 -- No --> P5; P3 --> P8[Mark controlled rerouting in progress]; P4 --> P5; P7 --> P5; P8 --> P5; P5 --> D3{SP restarting?}; D3 -- Yes --> T1([Idle]); D3 -- No --> P9[/Start route set test RTPC -> RSRT/]; P9 --> T1;
+```
+
+Flowchart for signalling route management; transfer prohibited control (RTPC).
+
+T1160410-94/d144
+
+**Figure 44/Q.704 (sheet 2 of 3) – Signalling route management; transfer prohibited control (RTPC)**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> RB[Restart begins
+TPRC -> RTPC]
+ Idle1 --> RE[Restart ends
+TPRC -> RTPC]
+ RB --> CAM[Cancel all marks]
+ RE --> CSR[Cancel SP restarting]
+ CAM --> MSR[Mark SP restarting]
+ CSR --> Idle2([Idle])
+ MSR --> Idle2
+ T1160420-94/d145
+
+```
+
+Flowchart for Signalling route management; transfer prohibited control (RTPC). The process starts at an 'Idle' state, branches into 'Restart begins' and 'Restart ends' (both TPRC -> RTPC), followed by 'Cancel all marks' and 'Cancel SP restarting' respectively, then 'Mark SP restarting', and finally returns to an 'Idle' state. Reference T1160420-94/d145 is noted.
+
+**Figure 44/Q.704 (sheet 3 of 3) – Signalling route management;
+transfer prohibited control (RTPC)**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> T1[Transfer allowed message HMDT -> RTAC]
+ Idle1 --> T2[Destination accessible TSRC -> RTAC]
+ Idle1 --> T3[STP no longer used for destination TSRC -> RTAC]
+ Idle1 --> T4[Send transfer allowed message RSRT -> RTAC]
+ T1 --> S1{Signalling route available RTAC -> TSRC}
+ T2 --> S2{Transfer allowed RTAC -> HMRT}
+ T3 --> S3{Transfer allowed RTAC -> HMRT}
+ T4 --> S3
+ S1 --> D1{SP restarting?}
+ S2 --> D1
+ S3 --> D1
+ D1 -- Yes --> Idle2([Idle])
+ D1 -- No --> S4{Signalling route available RTAC -> RSRT}
+ S4 --> D2{Forced rerouting in progress?}
+ D2 -- Yes --> Idle2
+ D2 -- No --> S5{Signalling route available RTAC -> TCRC}
+ D2 -- No --> S6{Signalling route available RTAC -> TFRC}
+ S5 --> S7{Controlled rerouting RTAC -> RTPC}
+ S6 --> Idle2
+ S7 --> Idle2
+ T1 -.-> FromRemote[From remote level 3]
+ S2 -.-> ToAdjacent[To all adjacent SPs]
+ S3 -.-> ToConcerned[To concerned STP]
+ S3 -.-> ToRemote[To remote level 3]
+ T1 -.-> C1((1))
+ C1 -.-> C2((2))
+
+```
+
+Flowchart for Signalling route management; transfer allowed control (RTAC). The process starts at an 'Idle' state and branches based on various conditions such as 'Transfer allowed message HMDT -> RTAC', 'Destination accessible TSRC -> RTAC', 'STP no longer used for destination TSRC -> RTAC', and 'Send transfer allowed message RSRT -> RTAC'. It includes decision diamonds for 'SP restarting?' and 'Forced rerouting in progress?', leading to various route availability checks and control messages like 'Signalling route available RTAC -> TSRC', 'Transfer allowed RTAC -> HMRT', 'Signalling route available RTAC -> RSRT', 'Signalling route available RTAC -> TCRC', 'Signalling route available RTAC -> TFRC', and 'Controlled rerouting RTAC -> RTPC'. The flowchart ends at another 'Idle' state.
+
+T1160430-94/d146
+
+**Figure 45/Q.704 (sheet 1 of 2) – Signalling route management; transfer allowed control (RTAC)**
+
+
+
+The diagram consists of two state transition flowcharts for signalling route management.
+
+**Top Flowchart:** Starts at state '1'. Transitions to 'Forced rerouting TSRC → RTAC', 'Forced rerouting terminated TFRC → RTAC', and 'Forced rerouting not required TFRC → RTAC'. From 'Forced rerouting TSRC → RTAC', transition to 'Mark forced rerouting in progress'. From 'Forced rerouting terminated TFRC → RTAC', transition to 'Cancel forced rerouting in progress'. From 'Forced rerouting not required TFRC → RTAC', transition to 'Cancel forced rerouting in progress'. Both 'Mark forced rerouting in progress' and 'Cancel forced rerouting in progress' lead to the 'Idle' state.
+
+**Bottom Flowchart:** Starts at the 'Idle' state. Transitions to 'Restart begins TPRC → RTAC' and 'Restart ends TPRC → RTAC'. From 'Restart begins TPRC → RTAC', transition to 'Cancel all marks', then 'Mark SP restarting', which leads to the 'Idle' state. From 'Restart ends TPRC → RTAC', transition to 'Cancel SP restarting', which also leads to the 'Idle' state. Reference T1160440-94/d147 is noted near the bottom right.
+
+State transition diagrams for signalling route management. The top diagram shows forced rerouting states (TSRC, TFRC) leading to Idle via Mark or Cancel actions. The bottom diagram shows Restart states (TPRC) leading to Idle via Cancel or Mark actions. Reference T1160440-94/d147 is noted.
+
+**Figure 45/Q.704 (sheet 2 of 2) – Signalling route management; transfer allowed control (RTAC)**
+
+
+
+The diagram illustrates the state transitions for the signalling route set test control (RSRT) process. It starts from an 'Idle' state (oval) and branches into three main paths based on the type of route set test initiated:
+
+- Start route set test RTRC → RSRT:** This path is associated with 'Transfer restricted received'. It leads to a dashed box 'Start route set test RTRC → RSRT' (parallelogram), which then leads to a dashed box 'Set route set test for restricted destination' (rectangle). This leads to a circle with the number '3' and '1' below it. A dashed line also connects this path to the 'Start T10' box.
+- Start route set test RTPC → RSRT:** This path is associated with 'Transfer prohibited received'. It leads to a box 'Start route set test RTPC → RSRT' (parallelogram), which then leads to a box 'Set route set test for prohibited destination' (rectangle). This leads to a circle with the number '4' and '1' below it. A dashed line also connects this path to the 'Start T10' box.
+- Start route set test TSRC → RSRT:** This path leads to a box 'Start route set test TSRC → RSRT' (parallelogram), which then leads to a box 'Signalling route set test RSRT → HMRT' (parallelogram). This leads to a circle with the number '2' and '2' below it. A dashed line connects this path to 'Referred to concerned destination' and 'To remote level 3'.
+
+All three paths converge to a central box 'Start T10' (parallelogram), which leads to a 'Wait' state (oval). From 'Wait', the diagram branches into four paths:
+
+- Start route set test RTRC → RSRT:** Leads to a dashed box 'Start route set test RTRC → RSRT' (parallelogram), which leads to a dashed circle with the number '3' and '1' below it.
+- Start route set test RTPC → RSRT:** Leads to a dashed box 'Start route set test RTPC → RSRT' (parallelogram), which leads to a dashed circle with the number '4' and '1' below it.
+- Signalling route available RTAC → RSRT:** Leads to a box 'Signalling route available RTAC → RSRT' (parallelogram), which leads to a box 'Stop T10' (parallelogram), which leads to an 'Idle' state (oval).
+- T10:** Leads to a box 'T10' (parallelogram), which leads to a box 'Signalling route set test RSRT → HMRT' (parallelogram), which leads to a circle with the number '1' and '1' below it.
+
+Vertical labels on the left indicate levels: '2' at the top, '3, 4' and '1' in the middle section, and '3, 4' and '1' in the bottom section. A reference code 'T1160450-94/d148' is at the bottom right.
+
+State transition diagram for signalling route set test control (RSRT).
+
+NOTE – Dashed symbols apply only to the Transfer restricted option.
+
+**Figure 46/Q.704 (sheet 1 of 3) – Signalling route management; signalling route set test control (RSRT)**
+
+
+
+```
+
+graph TD
+ Start((2)) --> SRT[Signalling route set test HMDT -> RSRT]
+ SRT -.-> Note1[Originated by STP Y
+From remote level 3]
+ SRT --> OwnSP{Own SP restarting?}
+ OwnSP -- Yes --> Idle1([Idle])
+ OwnSP -- No --> ADReq[Accessibility data request RSRT -> TSRC]
+ ADReq -.-> Note2[For the concerned destination]
+ ADReq --> Wait[Wait for data]
+ Wait --> ADData[Accessibility data TSRC -> RSRT]
+ ADData --> DataOK{Data OK?}
+ DataOK -.-> Note3[Is accessibility data the same as in route set test message?]
+ DataOK -- Yes --> Idle2([Idle])
+ DataOK -- No --> DestAcc{Is destination accessible?}
+ DestAcc -- No --> RTPC[Send transfer prohibited message RSRT -> RTPC]
+ DestAcc -- Yes --> OnlyViaY{Only via Y?}
+ OnlyViaY -- Yes --> RTPC
+ OnlyViaY -- No --> NotViaY{Not via Y or FPLS?}
+ NotViaY -.-> Note4[Has a transfer restricted message already been sent for this destination to any SP including possibly Y?]
+ NotViaY -- Yes --> RTRC[Send transfer restricted message RSRT -> RTRC]
+ NotViaY -- No --> RTAC[Send transfer allowed message RSRT -> RTAC]
+ RTPC --> Idle2
+ RTRC --> Idle2
+ RTAC --> Idle2
+
+```
+
+Flowchart for Signalling route set test control (RSRT). The process starts at point 2, leading to 'Signalling route set test HMDT -> RSRT'. A note indicates this is 'Originated by STP Y' and 'From remote level 3'. It then checks 'Own SP restarting?'. If Yes, it goes to 'Idle'. If No, it sends 'Accessibility data request RSRT -> TSRC' (for the concerned destination) and enters 'Wait for data'. It then receives 'Accessibility data TSRC -> RSRT'. It checks 'Data OK?'. If Yes, it goes to 'Idle'. If No, it checks 'Is destination accessible?'. If No, it sends 'Send transfer prohibited message RSRT -> RTPC' and goes to 'Idle'. If Yes, it checks 'Only via Y?'. If Yes, it sends 'Send transfer prohibited message RSRT -> RTPC' and goes to 'Idle'. If No, it checks 'Not via Y or FPLS?'. If Yes, it sends 'Send transfer restricted message RSRT -> RTRC' and goes to 'Idle'. If No, it sends 'Send transfer allowed message RSRT -> RTAC' and goes to 'Idle'. A note for 'Data OK?' asks if it's the same as in the route set test message. A note for 'Only via Y?' asks if the destination is accessible only via STP Y. A note for 'Not via Y or FPLS?' asks if a transfer restricted message has already been sent for this destination to any SP including possibly Y. The diagram is labeled T1160460-94/d149.
+
+FPLS First Priority Link Set
+
+NOTE – Dashed symbols apply only to the Transfer restricted option.
+
+**Figure 46/Q.704 (sheet 2 of 3) – Signalling route management; signalling route set test control (RSRT)**
+
+
+
+```
+
+graph TD
+ Idle1([Idle]) --> E1[Adjacent SP restarting TSRC → RSRT]
+ Idle1 --> E2[Restart begins TSRC → RSRT]
+ Idle1 --> E3[Adjacent SP restarted TSRC → RSRT]
+ Idle1 --> E4[Restart ends TPRC → RSRT]
+ E1 --> A1[Mark adjacent SP restarting]
+ E2 --> A2[Mark own SP restarting]
+ E3 --> E4
+ A1 --> Idle2([Idle])
+ A2 --> Idle2
+ E4 --> A3[Cancel own SP restarting]
+ A3 --> Idle3([Idle])
+
+ Wait([Wait]) --> E5[Restart begins TPRC → RSRT]
+ Wait --> E6[Adjacent SP restarting TSRC → RSRT]
+ E5 --> A4[Cancel all marks]
+ A4 --> A5[Mark own SP restarting]
+ A5 --> Idle4([Idle])
+ E6 --> A6[Cancel all marks]
+ A6 --> A7[Mark adjacent SP restarting]
+ A7 --> Idle4
+
+```
+
+T1132060-91/d150
+
+Two state transition diagrams for signalling route management. The top diagram starts at 'Idle' and branches into four events: 'Adjacent SP restarting TSRC → RSRT', 'Restart begins TSRC → RSRT', 'Adjacent SP restarted TSRC → RSRT', and 'Restart ends TPRC → RSRT'. The first two lead to 'Mark adjacent SP restarting' and 'Mark own SP restarting' respectively, both leading to 'Idle'. The third leads to 'Restart ends TPRC → RSRT', which leads to 'Cancel own SP restarting', which leads to 'Idle'. The bottom diagram starts at 'Wait' and branches into two events: 'Restart begins TPRC → RSRT' and 'Adjacent SP restarting TSRC → RSRT'. The first leads to 'Cancel all marks', then 'Mark own SP restarting', leading to 'Idle'. The second leads to 'Cancel all marks', then 'Mark adjacent SP restarting', leading to 'Idle'. A small text 'T1132060-91/d150' is present near the bottom right of the second diagram.
+
+**Figure 46/Q.704 (sheet 3 of 3) – Signalling route management;
+signalling route set test control (RSRT)**
+
+
+
+```
+
+graph TD
+ Start([Idle]) --> HMDT[Transfer controlled
+HMDT → RTCC]
+ HMDT --- Remote[From remote
+level 3]
+
+ HMDT --> TRCC{...}
+ subgraph Option_Multiple_Congestion
+ TRCC -.-> DCS_TRCC[Destination
+congestion
+status
+RTCC → TRCC]
+ DCS_TRCC -.-> Idle2([Idle])
+ end
+
+ HMDT --> DC_TSFC[Destination
+congested
+RTCC → TSFC]
+ DC_TSFC --> Idle2
+
+ HMDT -.-> HMCG[Send transfer
+controlled
+message
+HMCG → RTCC]
+ HMCG -.-> Originate{Did
+message
+originate at
+SP?}
+
+ Originate -.->|Yes| DCS_TSFC[Destination
+congestion
+status
+RTCC → TSFC]
+ DCS_TSFC -.-> HMRT[Transfer
+controlled
+RTCC → HMRT]
+
+ Originate -.->|No| TSPC[Send transfer
+controlled
+message
+TSPC → RTCC]
+ TSPC -.-> HMRT
+
+ HMRT --> Idle2
+ HMRT -.- SP[To concerned
+SP]
+
+```
+
+This flowchart illustrates the signalling route management for transfer controlled control (RTCC). It begins with an 'Idle' state, which transitions to a 'Transfer controlled HMDT → RTCC' process. From this process, a dashed line indicates an input 'From remote level 3'. The flow then splits into multiple paths. One path leads to a hatched box 'Destination congested RTCC → TSFC', which then leads to another 'Idle' state. A dotted path leads to 'Destination congestion status RTCC → TRCC'. Another dotted path starts with 'Send transfer controlled message HMCG → RTCC', leading to a decision diamond 'Did message originate at SP?'. If 'No', it goes to a hatched box 'Send transfer controlled message TSPC → RTCC', which then leads to a 'Transfer controlled RTCC → HMRT' process. If 'Yes', it goes to a dotted box 'Destination congestion status RTCC → TSFC', which then leads to the same 'Transfer controlled RTCC → HMRT' process. From this process, a dashed line indicates an output 'To concerned SP', and the flow finally reaches an 'Idle' state.
+
+Flowchart for Figure 46a/Q.704 (sheet 1 of 2) – Signalling route management; transfer controlled control (RTCC).
+
+T1132070-91/d151
+
+NOTE – Dotted symbols apply only to the multiple congestion states option. Delete hatched symbols when using option.
+
+**Figure 46a/Q.704 (sheet 1 of 2) – Signalling route management;
+transfer controlled control (RTCC)**
+
+
+
+```
+
+graph TD
+ Start([Idle]) --> HMDT[User part
+unavailable
+message
+HMDT → RTCC]
+ HMDT --- Remote[From remote
+level 3]
+ HMDT --> TSFC[Distant
+user part
+unavailable
+RTCC → TSFC]
+ TSFC --> End([Idle])
+
+```
+
+This flowchart illustrates the signalling route management for transfer controlled control (RTCC). It begins with an 'Idle' state, which transitions to a 'User part unavailable message HMDT → RTCC' process. From this process, a dashed line indicates an input 'From remote level 3'. The flow then proceeds to a 'Distant user part unavailable RTCC → TSFC' process, which finally leads to an 'Idle' state.
+
+Flowchart for Figure 46a/Q.704 (sheet 2 of 2) – Signalling route management; transfer controlled control (RTCC).
+
+T1160470-94/d152
+
+**Figure 46a/Q.704 (sheet 2 of 2) – Signalling route management;
+transfer controlled control (RTCC)**
+
+
+
+```
+
+stateDiagram-v2
+ [*] --> Idle
+ Idle --> StartCongestionTest: Start congestion test TRCC -> RCAT
+ Idle --> SignallingRouteSetCongestionTestHMDT: Signalling route set congestion test HMDT -> RCAT
+ StartCongestionTest --> SignallingRouteSetCongestionTestRCAT: Signalling route set congestion test RCAT -> HMRT
+ SignallingRouteSetCongestionTestHMDT --> DiscardMessage: Discard message
+ SignallingRouteSetCongestionTestHMDT --> StopCongestionTestTRCC: Stop congestion test TRCC -> RCAT
+ SignallingRouteSetCongestionTestRCAT --> StartT16: Start T16
+ StartT16 --> Wait: Wait
+ Wait --> StopCongestionTestTRCC
+ StopCongestionTestTRCC --> StopT16: Stop T16
+ StopT16 --> DecrementDestinationCongestionStatus: Decrement destination congestion status RCAT -> TRCC
+ DecrementDestinationCongestionStatus --> Idle
+ DiscardMessage --> Idle
+ StopCongestionTestTRCC --> T16: T16
+ T16 --> DecrementDestinationCongestionStatus
+
+```
+
+State transition diagram for signalling route management. It starts at 'Idle' and branches into 'Start congestion test TRCC -> RCAT' and 'Signalling route set congestion test HMDT -> RCAT' (from remote level 3). The left path goes to 'Signalling route set congestion test RCAT -> HMRT' (to remote level 3), then 'Start T16', 'Wait', 'Stop congestion test TRCC -> RCAT', 'Stop T16', and 'Decrement destination congestion status RCAT -> TRCC'. The right path from 'Signalling route set congestion test HMDT -> RCAT' goes to 'Discard message' and 'Stop congestion test TRCC -> RCAT'. Both paths lead to 'Idle'. A 'T16' state is also shown between 'Stop congestion test' and 'Decrement destination congestion status'.
+
+T1160480-94/d153
+
+NOTE – Dotted symbols apply only to the multiple congestion states option.
+
+**Figure 46b/Q.704 – Signalling route management; signalling-route-set-congestion-test control (RCAT)**
+
+
+
+```
+
+graph TD
+ subgraph TopProcess [ ]
+ Idle1([Idle]) --> HMDT[Transfer restricted HMDT → RTRC]
+ Idle1 --> RSRT[Send transfer restricted message RSRT → RTRC]
+ Idle1 --> TSRC1[Send transfer restricted message TSRC → RTRC]
+ Idle1 --> Dest[Destination restricted TSRC → RTRC]
+ HMDT --> SigRoute[Signalling route restricted RTRC → TSRC]
+ RSRT --> HMRT1[Transfer restricted message RTRC → HMRT]
+ TSRC1 --> HMRT1
+ Dest --> HMRT2[Transfer restricted message RTRC → HMRT]
+ SigRoute --> SPRestart{SP restarting?}
+ HMRT1 --> ToRemote[To remote level 3]
+ HMRT1 --> ToConcerned[To the concerned SP]
+ HMRT2 --> AllSPs[To all adjacent SPs, except those to which transfer prohibited messages are sent]
+ SPRestart -- Yes --> AllSPs
+ SPRestart -- No --> StartTest[Start route set test RTRC → RSRT]
+ AllSPs --> Idle2([Idle])
+ StartTest --> Idle2
+ end
+ subgraph BottomProcess [ ]
+ Idle3([Idle]) --> RestartBegins[Restart begins TPRC → RTRC]
+ Idle3 --> RestartEnds[Restart ends TPRC → RTRC]
+ RestartBegins --> Mark[Mark SP restarting]
+ RestartEnds --> Cancel[Cancel SP restarting]
+ Mark --> Idle4([Idle])
+ Cancel --> Idle4
+ end
+ style TopProcess fill:none,stroke:none
+ style BottomProcess fill:none,stroke:none
+
+```
+
+Flowchart for Signalling route management; transfer restricted control (RTRC). The diagram shows two main processes. The top process handles 'From remote level 3' inputs through four parallel paths: 'Transfer restricted HMDT → RTRC', 'Send transfer restricted message RSRT → RTRC', 'Send transfer restricted message TSRC → RTRC', and 'Destination restricted TSRC → RTRC'. These lead to 'Signalling route restricted RTRC → TSRC', 'Transfer restricted message RTRC → HMRT' (with sub-options 'To remote level 3' and 'To the concerned SP'), and 'Transfer restricted message RTRC → HMRT'. A decision 'SP restarting?' follows. 'Yes' leads to 'To all adjacent SPs, except those to which transfer prohibited messages are sent'. 'No' leads to 'Start route set test RTRC → RSRT'. Both lead to an 'Idle' state. The bottom process starts at an 'Idle' state, leading to 'Restart begins TPRC → RTRC' and 'Restart ends TPRC → RTRC'. These lead to 'Mark SP restarting' and 'Cancel SP restarting', which both lead to an 'Idle' state.
+
+T1160490-94/d154
+
+NOTE – Dashed symbols apply only to the Transfer restricted option.
+
+**Figure 46c/Q.704 – Signalling route management;
+transfer restricted control (RTRC)**
+
+
+
+# ITU-T RECOMMENDATIONS SERIES
+
+- Series A Organization of the work of the ITU-T
+- Series B Means of expression
+- Series C General telecommunication statistics
+- Series D General tariff principles
+- Series E Telephone network and ISDN
+- Series F Non-telephone telecommunication services
+- Series G Transmission systems and media
+- Series H Transmission of non-telephone signals
+- Series I Integrated services digital network
+- Series J Transmission of sound-programme and television signals
+- Series K Protection against interference
+- Series L Construction, installation and protection of cables and other elements of outside plant
+- Series M Maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits
+- Series N Maintenance: international sound-programme and television transmission circuits
+- Series O Specifications of measuring equipment
+- Series P Telephone transmission quality
+- Series Q Switching and signalling**
+- Series R Telegraph transmission
+- Series S Telegraph services terminal equipment
+- Series T Terminal equipments and protocols for telematic services
+- Series U Telegraph switching
+- Series V Data communication over the telephone network
+- Series X Data networks and open system communication
+- Series Z Programming languages
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.705-199303-I_PDF-E/raw.md b/marked/Q/T-REC-Q.705-199303-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..e35151d6e1634838e5202dc6041afe0cad83fed4
--- /dev/null
+++ b/marked/Q/T-REC-Q.705-199303-I_PDF-E/raw.md
@@ -0,0 +1,755 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**Q.705**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(03/93)
+
+**SPECIFICATIONS OF SIGNALLING
+SYSTEM No. 7**
+
+---
+
+**SIGNALLING SYSTEM No. 7 –
+SIGNALLING NETWORK STRUCTURE**
+
+**ITU-T Recommendation Q.705**
+
+(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.705 was revised by the ITU-T Study Group XI (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993).
+
+# --- NOTES
+
+1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector.
+
+In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms "CCITT, CCIR or IFRB" or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure.
+
+2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+# CONTENTS
+
+| | | Page |
+|-----|--------------------------------------------------------------------------------------|-------------|
+| 1 | Introduction..... | 1 |
+| 2 | Network components ..... | 1 |
+| 2.1 | Signalling links ..... | 1 |
+| 2.2 | Signalling points ..... | 1 |
+| 3 | Structural independence of international and national signalling networks..... | 2 |
+| 4 | Considerations common to both international and national signalling networks..... | 3 |
+| 4.1 | Availability of the network ..... | 3 |
+| 4.2 | Message transfer delay..... | 3 |
+| 4.3 | Message sequence control ..... | 3 |
+| 4.4 | Number of signalling links used in load sharing ..... | 3 |
+| 4.5 | Satellite working..... | 3 |
+| 5 | International signalling network..... | 4 |
+| 5.1 | General..... | 4 |
+| 5.2 | Number of signalling transfer points in signalling relations..... | 4 |
+| 5.3 | Numbering of signalling points ..... | 4 |
+| 5.4 | Routing rules..... | 4 |
+| 5.5 | Structures ..... | 4 |
+| 5.6 | Procedures ..... | 4 |
+| 6 | Signalling network for cross-border traffic ..... | 5 |
+| 6.1 | General..... | 5 |
+| 6.2 | Use of international hierarchical level ..... | 5 |
+| 6.3 | Integrated numbering of national signalling networks ..... | 5 |
+| 6.4 | Interworking of national signalling networks ..... | 5 |
+| 7 | National signalling network ..... | 5 |
+| 8 | Procedures prevent unauthorized use of an STP (optional) ..... | 5 |
+| 8.1 | General..... | 5 |
+| 8.2 | Identifying unauthorized SS No. 7 messages ..... | 6 |
+| 8.3 | Treatment of unauthorized SS No. 7 messages ..... | 6 |
+| 8.4 | Measurements ..... | 6 |
+| 8.5 | Notification to unauthorized user ..... | 6 |
+| 9 | SS No. 7 Planning Tools ..... | 7 |
+| | Annex A – Mesh signalling network examples..... | 7 |
+| A.1 | General..... | 7 |
+| A.2 | Basic network structures (example)..... | 7 |
+| A.3 | Routing ..... | 9 |
+| A.4 | Actions relating to failure conditions..... | 17 |
+| A.5 | Explanatory note from the implementors forum for clarification of load sharing ..... | 22 |
+
+
+
+# SIGNALLING SYSTEM No. 7 – SIGNALLING NETWORK STRUCTURE
+
+(Geneva, 1980; modified at Helsinki, 1993)
+
+# 1 Introduction
+
+This Recommendation describes aspects which are pertinent to and should be considered in the design of international Signalling System No. 7 (SS No. 7) signalling networks. Some or all of these aspects may also be relevant to the design of national networks. Some aspects are dealt with for both international and national networks (e.g. availability), others are discussed in the context of the international network only (e.g. the number of *signalling transfer points* in a signalling relation). A number of aspects require further study for national networks. This Recommendation also gives in Annex A examples of how the signalling network procedures may be applied to the mesh network representation.
+
+The national and international networks are considered to be structurally independent and, although a particular *signalling point* may belong to both networks, signalling points are allocated *signalling point codes* according to the rules of each network.
+
+The signalling network procedures are provided in order to effectively operate a signalling network having different degrees of complexity. They provide for reliable message transfer across the network and for reconfiguration of the network in the case of failures.
+
+The most elementary signalling network consists of *originating and destination signalling points* connected by a single *signalling link*. To meet availability requirements this may be supplemented by additional links in parallel which may share the signalling load between them. If, for all signalling relations, the originating and destination signalling points are directly connected in this way in a network, then the network operates in the *associated mode*.
+
+For technical or economic reasons a simple associated network may not be suitable and a *quasi-associated network* may be implemented in which the information between originating and destination signalling points may be transferred via a number of signalling transfer points. Such a network may be represented by a *mesh network* such as that given in Annex A, as other networks are either a subset of the mesh network or are structured using this network or its subsets as components.
+
+## 2 Network components
+
+### 2.1 Signalling links
+
+Signalling links are basic components in a signalling network connecting together signalling points. The signalling links encompass the *level 2* functions which provide for message error control (detection and subsequent correction). In addition, provision for maintaining the correct message sequence is provided (see Recommendation Q.703).
+
+### 2.2 Signalling points
+
+Signalling links connect signalling points at which signalling network functions such as message routing are provided at *level 3* and at which the user functions may be provided at *level 4* if it is also an originating or destination point (see 2.4/Q.704).
+
+A signalling point that only transfers messages from one signalling link to another at level 3 serves as a signalling transfer point (STP).
+
+The signalling links, signalling transfer points, and signalling (originating or destination) points may be combined in many different ways to form a *signalling network*.
+
+## 3 Structural independence of international and national signalling networks
+
+The worldwide signalling network is structured into two functionally independent levels, namely the international and national levels, as illustrated in Figure 1. This structure makes possible a clear division of responsibility for signalling network management and allows numbering plans of signalling points of the international network and the different national networks to be independent of one another.
+
+
+
+I International hierarchical level
+
+N National hierarchical level
+
+□ International signalling point (ISP)
+
+○ National signalling point (NSP)
+
+T1156180-93/d01
+
+Diagram illustrating the structural independence of international and national signalling networks. It shows two levels: the International hierarchical level (I) and the National hierarchical level (N). The International level includes International Signalling Points (ISPs) represented by squares. The National level includes National Signalling Points (NSPs) represented by circles. In Country 1, NSP1, NSP3 (ISP1), and NSP4 (ISP2) are shown. In Country 2, NSP4 (ISP2) and NSP2 are shown. Vertical lines connect the International level to the National level in each country. A legend at the bottom left defines the symbols: 'I' for International hierarchical level, 'N' for National hierarchical level, a square for International signalling point (ISP), and a circle for National signalling point (NSP). The diagram is labeled 'T1156180-93/d01'.
+
+FIGURE 1/Q.705
+**International and national signalling networks**
+
+A signalling point (SP), including a signalling transfer point (STP), may be assigned to one of three categories:
+
+- national signalling point (NSP) (signalling transfer point) which belongs to the national signalling network only (e.g. NSP1) and is identified by a signalling point code (OPC or DPC) according to the national numbering plan of signalling points;
+- international signalling point (ISP) (signalling transfer point) which belongs to the international signalling network only (e.g. ISP3) and is identified by a signalling point code (OPC or DPC) according to the international numbering plan of signalling points;
+- a node that functions both as an international signalling point (signalling transfer point) and a national signalling point (signalling transfer point) and therefore belongs to both the international signalling network and a national signalling network and accordingly is identified by a specific signalling point code (OPC or DPC) in each of the signalling networks.
+
+If a discrimination between international and national signalling point codes is necessary at a signalling point, the network indicator is used (see 14.2/Q.704).
+
+## 4 Considerations common to both international and national signalling networks
+
+### 4.1 Availability of the network
+
+The signalling network structure must be selected to meet the most stringent availability requirements of any User Part served by a specific network. The availability of the individual components of the network signalling links (signalling points and signalling transfer points) must be considered in determining the network structure (see Recommendation Q.709).
+
+Considerable attention is required to STP routing tables to ensure that circular routing does not occur. (See Annex A/Q.780 – Testing and Planning Tools.)
+
+### 4.2 Message transfer delay
+
+In order to take account of signalling message delay considerations, regard should be given, in the structuring of a particular signalling network, to the overall number of signalling links (where there are a number of signalling relations in tandem) related to a particular user transaction (e.g. to a specific call in the telephone application) (see Recommendation Q.709).
+
+### 4.3 Message sequence control
+
+For all messages for the same transaction (e.g. a telephone call) the MTP will maintain the same routing provided that the same *signalling link selection* code is used in the absence of failure. However, a transaction does not necessarily have to use the same signalling route for both forward and backward messages.
+
+### 4.4 Number of signalling links used in load sharing
+
+The number of signalling links used to share the load of a given flow of signalling traffic typically depends on
+
+- the total traffic load;
+- the availability of the links;
+- the required availability of the path between the two signalling points concerned; and
+- the bit rate of the signalling links.
+
+Load sharing requires at least two signalling links for all bit rates, but more may be needed at lower bit rates.
+
+When two links are used, each of them should be able to carry the total signalling traffic in case of failure of the other link. When more than two links are used, sufficient reserve link capacity should exist to satisfy the availability requirements specified in Recommendation Q.706.
+
+### 4.5 Satellite working
+
+The service performance criteria and network operation aspects require balanced consideration in structuring SS No. 7 networks. Despite the relatively long delay of satellite connections, these connections can also be suitable for providing signalling data links.
+
+Especially for long distance international operation, transmission diversity (including satellites) is an important criterion in structuring SS No. 7 networks from a network availability and reliability point of view.
+
+In international operation, a terrestrial signalling data link using the basic error correction method may be restored, in exceptional circumstances and with bilateral agreement, by using a satellite data link. If this is done, the following precautions should be taken into account:
+
+- in order to ensure in these circumstances the correct operation of the basic error correction method over the satellite data link, timer T7 (12.3/Q.703), at both ends of the restored signalling link, should have a value of at least 800 ms;
+- in order to take into account the additional delay caused by the satellite data link, the minimum values of the timers T1–T6, specified in 16.8/Q.704, should take the specified values for routes with long propagation delays;
+- the bit error rate guaranteed by the satellite link used is of significant influence. If the bit error rate is worse than $10^{-7}$ , the dimensioning of the link loads should consider from the beginning the possibly lower loading potential of a satellite link (see 5/Q.706).
+
+The calculation of the value N2 (the number of message signal unit octets available for retransmission in the PCR error correction method (see 6.4.2/Q.703) should take a signalling loop delay $T_{(L)}$ range, depending on the geographical conditions, between a minimum of 480 ms and a maximum of 600 ms.
+
+# **5 International signalling network**
+
+### **5.1 General**
+
+The international signalling network will use the procedures to be defined in the SS No. 7 Recommendations. The international network structure to be defined can also serve as a model for the structure of national networks.
+
+### **5.2 Number of signalling transfer points in signalling relations**
+
+In the international signalling network the number of signalling transfer points between an originating and a destination signalling point should not exceed two in a normal situation. In failure situations, this number may become three or even four for a short period of time. This constraint is intended to limit the complexity of the administration of the international signalling network.
+
+### **5.3 Numbering of signalling points**
+
+A 14-bit code is used for the identification of signalling points. The allocation scheme of international signalling point codes is defined in Recommendation Q.708.
+
+### **5.4 Routing rules**
+
+**5.4.1** In order to ensure full flexibility for the routing of signalling in the SS No. 7 international signalling network it appears desirable that at least one signalling point in each country should provide means for the international STP function. Such an approach should ease the use of SS No. 7 on small traffic routes.
+
+#### **5.4.2 Other routing rules**
+
+For further study.
+
+### **5.5 Structures**
+
+Requires further study.
+
+### **5.6 Procedures**
+
+Requires further study.
+
+## **6 Signalling network for cross-border traffic**
+
+### **6.1 General**
+
+For cross-border traffic between signalling points, the need for a special signalling network configuration is identified, because their common interests are such as to generate a considerable volume of traffic between them.
+
+Two alternative arrangements of the signalling network for cross-border traffic are provided so that Administrations may adopt either alternative upon a bilateral agreement.
+
+### **6.2 Use of international hierarchical level**
+
+**6.2.1** This arrangement could be applied in the case that there are only a relatively small number of signalling points in a country which serve for cross-border traffic.
+
+**6.2.2** The signalling points and the signalling transfer points which are involved in a signalling of cross-border traffic should belong to the international hierarchical level described in 3. When those signalling points or signalling transfer points are also involved in signalling of national traffic, they should belong to their national hierarchical level as well. Therefore the double numbering of signalling point codes based on both the international and national numbering schemes should be required.
+
+**6.2.3** A discrimination between international and national point codes is made by the network indicator in the service information octet (see 14.2/Q.704).
+
+**6.2.4** Signalling network management procedures in this network arrangement require further study.
+
+### **6.3 Integrated numbering of national signalling networks**
+
+**6.3.1** By this arrangement the signalling points, which serve cross-border traffic, should be identified by common national signalling point codes.
+
+**6.3.2** Common block of national signalling point codes is provided by bilateral agreement (further study is required).
+
+### **6.4 Interworking of national signalling networks**
+
+At the cross-border signalling network interface, the international specification of SS No. 7 should be preferred without exclusion of bilateral agreements.
+
+## **7 National signalling network**
+
+No specific structures for national signalling networks are included in this Recommendation; however, Administrations should cater for the requirements imposed on a national network for the protection of international services in terms of network related user requirements, such as availability and performance of the network perceived by users (see Recommendation Q.709).
+
+## **8 Procedures prevent unauthorized use of an STP (optional)**
+
+## **8.1 General**
+
+Administrations may make bilateral agreements to operate SS No. 7 between their networks. These agreements may place restrictions on the SS No. 7 messages authorized for one Administration to send to the other. Restrictions could be made, for example, in the interest of network security or as a result of service restrictions. Unauthorized signalling traffic may be, for example, STP traffic for calls set-up via networks other than that containing the STP, which has not been agreed bilaterally.
+
+An Administration making an agreement with restrictions may wish to identify and provide special treatment to unauthorized SS No. 7 messages.
+
+The measurements in Table 6/Q.752 provide some capability to identify unauthorized SS No. 7 messages. The procedures described in this clause for identifying and responding to unauthorized traffic are additional options for use at an STP with signalling links to other networks.
+
+## **8.2 Identifying unauthorized SS No. 7 messages**
+
+In addition to the normal signalling message handling, procedures specified in Recommendation Q.704, it shall be possible to inhibit/allow messages destined for another signalling point (SP) based on any one or combination of the following options:
+
+- i) To inhibit/allow STP access by a combination of designated incoming link sets to designated DPCs.
+
+This combination of DPC/incoming link set shall effectively operate in the form of a single matrix. This matrix shall consist of a maximum of 128 DPCs and a maximum of 64 incoming link sets. (These values are for guidance and may be adjusted to satisfy the requirements of the concerned Operator/Administration.)
+
+- ii) To inhibit/allow STP access by a combination of designated outgoing link sets to designated DPCs.
+
+This combination of DPC/outgoing link set shall effectively operate in the form of a single matrix. This matrix shall consist of a maximum of 128 DPCs and a maximum of 64 outgoing link sets. (These values are for guidance and may be adjusted to satisfy the requirements of the concerned Operator/Administration.)
+
+- iii) To inhibit/allow STP access by examination of OPC and DPC combination in the incoming STP message.
+
+This combination of DPC/OPC shall effectively operate in the form of a single matrix. This matrix shall consist of a maximum of 128 DPCs and a maximum of 128 OPCs. (These values are for guidance and may be adjusted to satisfy the requirements of the concerned Operator/Administration.)
+
+## **8.3 Treatment of unauthorized SS No. 7 messages**
+
+An STP identifying unauthorized SS No. 7 messages should be able, on a per link set or per signalling point code basis, to
+
+- i) provide all unauthorized SS No. 7 messages with the same handling as authorized traffic; or
+- ii) discard all unauthorized SS No. 7 messages.
+
+In addition, an STP should be able to
+
+- i) allow all STP messages outside the designated ranges as given in 8.2;
+- ii) bar (discard) all STP messages outside the designated ranges as given in 8.2.
+
+## **8.4 Measurements**
+
+An STP identifying unauthorized SS No. 7 messages incoming from another network should be able to count and record details of the unauthorized messages on a per link set and/or signalling point code basis.
+
+## **8.5 Notification to unauthorized user**
+
+An STP identifying unauthorized SS No. 7 messages from another network may wish to notify the Administration originating the unauthorized message(s).
+
+This notification should be undertaken by administrative means and not involve any mechanism in SS No. 7.
+
+In addition, a violation fault report shall be issued giving the unauthorized message content. It shall be possible to selectively restrict the number of violation reports on a per link set and/or signalling point code basis.
+
+It shall also be possible to inhibit the violation reporting mechanism on a point code/link set basis, nodally, or on a message direction, i.e. if an inhibited message is destined for an ROA, then it shall be possible to suppress the violation reports whilst allowing violation reports on inhibited messages from the ROA.
+
+# 9 SS No. 7 Planning Tools
+
+Annex A/Q.780 contains brief descriptions of some SS No. 7 Planning Tools.
+
+# Annex A
+
+## Mesh signalling network examples
+
+(This annex forms an integral part of this Recommendation)
+
+## A.1 General
+
+This annex is provided to demonstrate the procedures defined in Recommendation Q.704. While the example uses a specific *mesh* network to demonstrate the procedures, it is not the intent of this annex to recommend either implicitly or explicitly, the network described.
+
+The *mesh* network is used to demonstrate the MTP level 3 procedures because it is thought to be a possible international network implementation as shown on it, or subsets of it, may be used to construct other network structures.
+
+## A.2 Basic network structures (example)
+
+Figure A.1 shows the basic mesh network structure, while three simplified versions derived from this basic network structure are shown in Figure A.2. More complex signalling networks can be built, using these as building components.
+
+
+
+T1156190-93/d02
+
+○ Signalling point with level 4 functions
+
+□ Signalling transfer point (STP)
+
+Diagram of a basic mesh network structure with nodes A, B, C, D, E, and F. Nodes A and F are circles (level 4 functions), while B, C, D, and E are squares (STPs). Connections: A-B, A-C, B-C, B-D, C-E, D-E, and E-F.
+
+FIGURE A.1/Q.705
+Basic mesh network
+
+
+
+Diagram (a) showing a mesh network with nodes A, B, C, D, E, and F. Node A is connected to B and C. Node B is connected to A, C, and D. Node C is connected to A, B, and E. Node D is connected to B, E, and F. Node E is connected to C, D, and F. Node F is connected to D and E. This represents a full mesh where two out of four inter-STP link sets have been deleted.
+
+**a) Two out of four inter-STP link sets deleted**
+
+
+
+Diagram (b) showing a mesh network with nodes A, B, C, D, E, and F. Node A is connected to B and C. Node B is connected to A, C, and D. Node C is connected to A, B, and E. Node D is connected to B, E, and F. Node E is connected to C, D, and F. Node F is connected to D and E. This represents a mesh where the link sets between nodes B and D have been deleted.
+
+**b) Link sets between STPs of the same pair deleted**
+
+
+
+Diagram (c) showing a mesh network with nodes A, B, C, D, E, and F. Node A is connected to B and C. Node B is connected to A, C, and D. Node C is connected to A, B, and E. Node D is connected to B, E, and F. Node E is connected to C, D, and F. Node F is connected to D and E. This represents a mesh where two out of four inter-STP link sets and the link sets between nodes B and D have been deleted.
+
+T1156200-93/d03
+
+**c) Two out of four inter-STP link sets and link sets between STPs of the same pair deleted**
+
+**FIGURE A.2/Q.705
+Simplified versions of the basic mesh network**
+
+In the following, the basic mesh network Figure A.1 is taken as an example to explain the procedures defined in Recommendation Q.704.
+
+In this network, each signalling point with level 4 functions is connected by two link sets to two signalling transfer points. Each pair of signalling transfer points is connected to each other pair by four link sets. Moreover, there is a link set between the two signalling transfer points of each pair.
+
+The simplified versions a), b) and c) of the basic signalling network are obtained by deleting respectively:
+
+- a) two out of four intersignalling transfer point link sets;
+- b) link sets between signalling transfer points of the same pair; and
+- c) a) and b) together.
+
+It should be noted that for a given signalling link availability, the more signalling link sets removed from the basic signalling network (e.g. in going from Figure A.1 to Figure A.2), the lower the availability of the signalling network. However, an increase in the availability of the simplified signalling networks may be attained by adding one or more parallel signalling links to each of the remaining signalling link sets.
+
+## **A.3 Routing**
+
+### **A.3.1 General**
+
+This subclause gives some routing examples in the basic mesh network in Figure A.1. Routing actions required to change message routes under failure conditions are described in A.4. The following routing principles are assumed for the examples in this subclause:
+
+- Message routes should pass through a minimum number of intermediate signalling transfer points.
+- Routing at each signalling point will not be affected by message routes used up to the concerned signalling transfer points.
+- When more than one message route is available, signalling traffic should be load-shared by such message routes.
+- Messages relating to a given user transaction and sent in a given direction will be routed over the same message route to ensure correct message sequence.
+
+### **A.3.2 Routing in the absence of failures**
+
+Figure A.3 illustrates an example of routing in the absence of failures for messages from signalling point A to signalling point F.
+
+The following points are worthy of note:
+
+- a) In distributing traffic for load-sharing at the originating signalling point and intermediate signalling transfer points, care should be taken in the use of signalling link selection (SLS) codes so that traffic will be distributed over four available routes evenly. In the example, originating signalling point A uses the second least significant bit of the signalling link selection code, and signalling transfer points B and C the least significant bit.
+- b) Other than that described above, the choice of a particular link for a given signalling link selection code can be made at each signalling point independently. As a result, message routes for a given user transaction (e.g. SLS = 0010) in two directions may take different paths (e.g. A -> C -> D -> F and F -> E -> B -> A).
+- c) Links BC and DE are not used in the absence of failures. They will be used in certain failure situations described in A.4.
+- d) When the number of links in a link set is not a power of 2 (i.e. 1, 2, 4, 8), SLS load sharing does not achieve even distribution of traffic across the individual links.
+
+
+
+Diagram of a mesh network with nodes A, B, C, D, E, and F. Node A is on the left, connected to B (top) and C (bottom). B is connected to D (right) and C (bottom). C is connected to E (right) and D (top-right). D is connected to F (right) and E (bottom). E is connected to F (top-right). Arrows indicate message routes from A to F with associated SLS codes: A to B (SLS = XX0X), A to C (SLS = XX1X), B to D (SLS = XX00), C to D (SLS = XX10), C to E (SLS = XX11), D to F (SLS = XX01), and E to F (SLS = XX11). A label T1156210-93/d04 is in the bottom right.
+
+Normal message routes from A to F:
+
+- A → B → D → F (SLS = XX00)
+- A → C → D → F (SLS = XX10)
+- A → B → E → F (SLS = XX01)
+- A → C → E → F (SLS = XX11)
+
+SLS Signalling link selection code in the routing label
+ Assumption There is only one link between adjacent signalling points
+
+FIGURE A.3/Q.705
+ An example of routing in the absence of failures
+
+### A.3.3 Routing under failure conditions
+
+#### A.3.3.1 Alternative routing information
+
+In order to cope with failure conditions that may arise, each signalling point has alternative routing information which specifies, for each normal link set, alternative link set(s) to be used when the former become(s) unavailable (see 4.2/Q.704).
+
+Table A.1 gives, as an example, a list of alternative link sets for all normal link sets at signalling point A and at signalling transfer point B. In the basic mesh network, all link sets except those between signalling transfer points of the same pair are normal links which carry signalling traffic in the absence of failures. In case a normal link set becomes unavailable, signalling traffic formerly carried by that link set should be diverted to the alternative link set with priority 1. Alternative link sets with priority 2 (i.e. link sets between signalling transfer points of the same pair) will be used only when both the normal link set and alternative link set(s) with priority 1 become unavailable.
+
+Subclauses A.3.3.2 to A.3.3.5 present some typical examples of the consequences of faults in signalling links and signalling points on the routing of signalling traffic. For the sake of simplicity, link sets are supposed to consist of only one link each.
+
+#### A.3.3.2 Single link failure examples
+
+*Example 1:* Failure of a link between a signalling point and a signalling transfer point (e.g. link AB) (see Figure A.4).
+
+As indicated in Table A.1, A diverts traffic formerly carried by link AB to link AC, while B diverts such traffic to link BC. It should be noted that the number of signalling transfer points traversed by signalling messages from F to A which passes through B is increased by one and becomes three in this case.
+
+TABLE A.1/Q.705
+
+##### **List of alternative link sets at signalling points A and B**
+
+| | Normal link set | Alternative link set | Priority a) |
+|-----------------------------|-----------------|----------------------|------------------------|
+| Signalling point A | AB | AC | 1 |
+| | AC | AB | 1 |
+| Signalling transfer point B | BA | BC | 2 |
+| | BC | None | |
+| | BE | BD | 1 |
+| | | BC | 2 |
+| | BD | BE | 1 |
+| | | BC | 2 |
+
+a) *Priority 1* – Used with normal link set on load-sharing basis in the absence of failures.
+*Priority 2* – Used only when all the link sets with priority 1 become unavailable.
+
+
+
+T1156220-93/d05
+
+Legend:
+ ———→ Diverted traffic
+ - - - - → Original traffic
+ ———→ Direction of traffic diversion
+
+Diagram illustrating the failure of link AB and the resulting traffic diversion. The network consists of nodes A (circle), B (square), C (square), D (square), E (square), and F (circle). Link AB is shown as failed with a cross. Original traffic from A to B is shown as a dashed arrow. Diverted traffic from A is shown as a solid arrow pointing to C. From C, the diverted traffic proceeds to E and then to F. A legend indicates: solid arrow for Diverted traffic, dashed arrow for Original traffic, and a solid line with an arrowhead for Direction of traffic diversion.
+
+FIGURE A.4/Q.705
+
+###### **Failure of link AB**
+
+The principle to minimize the number of intermediate signalling transfer points in A.3.1 is applied in this case at signalling transfer point B to get around the failure. In fact, the procedures defined in Recommendation Q.704 assume that traffic is diverted at a signalling point only in the case of a signalling link being unavailable on the route outgoing from that signalling point. Therefore, the procedures do not provide for sending an indication that traffic routed via signalling transfer point B will traverse a further signalling transfer point.
+
+*Example 2:* Failure of an intersignalling transfer points link (e.g. link BD) (see Figure A.5).
+
+
+
+The diagram shows a network with nodes A, B, C, D, E, and F. Node A is connected to B and C. B is connected to C, D, and E. C is connected to E. D is connected to E and F. The link between B and D is shown with a dashed line and an 'X' mark, indicating a failure. Two arrows originate from node B: one pointing to node E and another pointing to node C, representing traffic diversion. Similarly, two arrows originate from node D: one pointing to node C and another pointing to node E. The text 'T1156230-93/d06' is located at the bottom right of the diagram.
+
+Diagram of a network failure (Figure A.5/Q.705).
+
+FIGURE A.5/Q.705
+**Failure of link BD**
+
+As indicated in Table A.1, B diverts traffic carried by link BD to link BE. In the same sense, D diverts traffic carried by link DB to link DC.
+
+*Example 3:* Failure of a link between signalling transfer points of the same pair (e.g. link BC) (see Figure A.6).
+
+No routing change is required as a result of this kind of failure. Only B and C take note that the link BC has become unavailable.
+
+
+
+The diagram shows the same network topology as Figure A.5. In this case, the link between nodes B and C is shown with a dashed line and an 'X' mark, indicating a failure. The text 'T1156240-93/d07' is located at the bottom right of the diagram.
+
+Diagram of a network failure (Figure A.6/Q.705).
+
+FIGURE A.6/Q.705
+**Failure of link BC**
+
+#### A.3.3.3 Multiple link failure examples
+
+As there are a variety of cases in which more than one link set becomes unavailable, only some typical cases are given as examples in the following.
+
+*Example 1:* Failure of a link between a signalling point and a signalling transfer point, and of the link between that signalling transfer point and that of the same pair (e.g. links DF, DE) (see Figure A.7).
+
+
+
+T1156250-93/d08
+
+Diagram of a network with nodes A, B, C, D, E, and F. Node A is connected to B and C. B is connected to C, D, and E. C is connected to D and E. D is connected to E and F. E is connected to F. Links DF and DE are shown with an 'X' mark, indicating failure. Arrows show traffic diversion: from B to E (dashed), from C to E (solid), and from F to E (solid).
+
+FIGURE A.7/Q.705
+**Failure of links DE and DF**
+
+B diverts traffic destined to F from link BD to link BE, because destination F becomes inaccessible via D. It should be noted that only the traffic destined to F is diverted from link BD to link BE, and not all the traffic on link BD. The same applies to C, which diverts traffic destined to F from link CD to link CE. F diverts all the traffic formerly carried by link FD to link FE in the same way as the single link failure example in A.3.3.2.
+
+*Example 2:* Failure of two intersignalling transfer point links (e.g. links BD, BE) (see Figure A.8).
+
+
+
+T1156260-93/d09
+
+Diagram of a network with nodes A, B, C, D, E, and F. Node A is connected to B and C. B is connected to C, D, and E. C is connected to D and E. D is connected to E and F. E is connected to F. Links BD and BE are shown with an 'X' mark, indicating failure. Arrows show traffic diversion: from B to C (dashed), from D to E (solid), and from E to C (solid).
+
+FIGURE A.8/Q.705
+**Failure of links BD and BE**
+
+B diverts traffic formerly carried by link BD to link BC, because its alternative link set with priority 1, i.e. link BE, is also unavailable. The same applies to traffic formerly carried by link BE, and B diverts it to link BC. D and E divert traffic formerly carried by links DB and EB respectively to links DC and EC in the same way as the single link failure example in A.3.3.2.
+
+*Example 3:* Failure of a link between a signalling point and a signalling transfer point, and of an intersignalling transfer point link (e.g. links DF and BD) (see Figure A.9).
+
+
+
+Diagram of a network topology showing nodes A, B, C, D, E, and F. Node A is connected to B and C. B is connected to C, D, and E. C is connected to D and E. D is connected to E and F. E is connected to F. Links BD and DF are shown with an 'X' mark, indicating failure. Arrows indicate traffic diversion: from B to C (solid arrow), from D to C (solid arrow), from D to E (solid arrow), and from F to E (solid arrow). Dashed arrows show the original paths: B to D, D to B, D to F, and F to D.
+
+T1156270-93/d10
+
+FIGURE A.9/Q.705
+Failure of links BD and DF
+
+This example is a combination of Examples 1 and 2 in A.3.3.2. D diverts traffic formerly carried by link DF to link DE, while F diverts it to link FE. Moreover D diverts traffic formerly carried by link DB to link DC (this traffic will be that generated by signalling points other than F connected to D). In the same sense, B diverts traffic carried by link BD to link BC.
+
+It should be noted that in this case only the portion of traffic sent by C to F via D traverses three signalling transfer points (C, D and E), while all the other portions continue to traverse two.
+
+*Example 4:* Failure of the two links between a signalling point and its signalling transfer points (e.g. DF and EF) (see Figure A.10).
+
+In this case the signalling relations between F and any other signalling point of the network are blocked. Therefore F stops all outgoing signalling traffic, while A stops only traffic destined to F.
+
+#### A.3.3.4 Single signalling point failure examples
+
+*Example 1:* Failure of a signalling transfer point (e.g. D) (see Figure A.11).
+
+B diverts all the traffic formerly carried by link BD to link BE. The same applies to C which diverts all the traffic carried by link CD to link CE. Originating point F diverts all the traffic carried by link FD to link FE as in the case of the link FD failure (see Example 1 in A.3.3.2).
+
+Attention is drawn to the difference to Example 1 in A.3.3.3 where only a part of the traffic previously carried by links BD and CD was diverted.
+
+
+
+Network diagram showing a failure of links DF and EF. Nodes A (circle), B (square), C (square), D (square), E (square), and F (circle) are shown. Links connect A-B, A-C, B-C, B-D, C-E, D-E, D-F, and E-F. Links D-F and E-F are marked with an 'X'. Arrows from A point to F, labeled 'Traffic to F is stopped'. Arrows from F point to E and D, labeled 'All traffic is stopped'. Reference T1156280-93/d11 is at the bottom right.
+
+FIGURE A.10/Q.705
+**Failure of links DF and EF**
+
+
+
+Network diagram showing a failure of signalling transfer point D. Nodes A (circle), B (square), C (square), D (square with an 'X'), E (square), and F (circle) are shown. Links connect A-B, A-C, B-C, B-D, C-E, D-E, D-F, and E-F. Node D is marked with an 'X'. Arrows from B point to D and C. Arrows from C point to D and E. Arrows from D point to F. Reference T1156290-93/d12 is at the bottom right.
+
+FIGURE A.11/Q.705
+**Failure of signalling transfer point D**
+
+*Example 2:* Failure of a destination point (e.g. F) (see Figure A.12).
+
+In this case A stops all the traffic to F formerly carried on links AB and AC.
+
+
+
+The diagram shows a network with nodes A, B, C, D, E, and F. Node A is a circle on the left. Nodes B, C, D, and E are squares arranged in a rectangle. Node F is a circle on the right with a large 'X' through it, indicating failure. Links connect A to B and A to C. B is connected to D and C. D is connected to E and F. C is connected to E. Two dashed arrows originate from A, one pointing to B and the other to C, representing traffic that would normally go to F but is now stopped at the intermediate nodes.
+
+Diagram of a network failure where the destination point F has failed.
+
+FIGURE A.12/Q.705
+**Failure of signalling point F**
+
+#### A.3.3.5 Multiple signalling transfer point failure examples
+
+Two typical cases of two signalling transfer points failing together are presented in the following examples:
+
+*Example 1:* Failure of two signalling transfer points not pertaining to the same pair (e.g. B and D) (see Figure A.13).
+
+
+
+The diagram shows the same network as Figure A.12, but with nodes B and D marked with a large 'X', indicating they have failed. Node F is now a normal circle. Solid arrows show traffic from A to B and A to C. From node C, two solid arrows point to node E, representing traffic that was previously transferred at B and D but is now rerouted. From node E, two dashed arrows point to node F, representing the continuation of the traffic to the destination.
+
+Diagram of a network failure where two signalling transfer points, B and D, have failed.
+
+FIGURE A.13/Q.705
+**Failure of signalling transfer points B and D**
+
+As a result of the failure of B, A diverts traffic formerly carried by link AB to link AC, while E diverts traffic formerly carried by link EB to link EC. Similarly, as a result of the failure of D, F diverts traffic formerly carried by link FD to link FE, while C diverts traffic formerly carried by link CD to link CE.
+
+It should be noted that, in this example, all the traffic between A and F is concentrated on only one intersignalling transfer point link, since failure of a signalling transfer point has an effect similar to a simultaneous failure of all the signalling links connected to it.
+
+*Example 2:* Failure of two signalling transfer points pertaining to the same pairs (e.g. D and E) (see Figure A.14).
+
+This example is equivalent to Example 4 in A.3.3.3 as far as the inaccessibility of F is concerned, but in this case any other signalling point connected by its links to D and E also becomes inaccessible. In this case A stops signalling traffic destined to F, while F stops all outgoing signalling traffic.
+
+
+
+Diagram illustrating the failure of signalling transfer points D and E. The network consists of nodes A, B, C, D, E, and F. Node A is connected to B and C. Node B is connected to D. Node C is connected to E. Node D is connected to E and F. Node E is connected to F. Nodes D and E are marked with an 'X' to indicate failure. Arrows show traffic from A to F being stopped at A, and all traffic from F being stopped at F. The diagram is labeled T1156320-93/d15.
+
+FIGURE A.14/Q.705
+Failure of signalling transfer points D and E
+
+## A.4 Actions relating to failure conditions
+
+In the following, four typical examples of the application of signalling network management procedures to the failure cases illustrated in A.3.3 are shown. In the case of multiple failures, an arbitrary failure (and restoration) sequence is assumed for illustrative purpose.
+
+### A.4.1 Example 1: Failure of a link between a signalling point and a signalling transfer point (e.g. link AB) (see Figure A.15)
+
+(Same as A.3.3.2, Example 1.)
+
+#### A.4.1.1 Failure of link AB
+
+- When the failure of link AB is detected in A and in B, they initiate the changeover procedure, by exchanging changeover messages via C. Once buffer updating is completed, A restarts the traffic originally carried by the failed link on link AC; similarly, B restarts traffic destined to A on link BC.
+- In addition, B sends a transfer-prohibited message to C referred to destination A (according to the criterion indicated in 13.2.2/Q.704).
+- On the reception of the transfer-prohibited message, C starts the periodic sending of signalling-route-set-test messages, referred to A, to B (see 13.5.2/Q.704).
+
+
+
+Diagram of a network failure scenario (FIGURE A.15/Q.705). The network consists of nodes A (circle), B (square), C (square), D (square), E (square), and F (circle). Links connect A-B, A-C, B-C, B-D, C-E, D-E, and E-F. A failure is indicated by a cross on the link between A and B. Arrows show traffic being diverted from the failed link AB to the link AC. A label 'T1156330-93/d16' is present in the bottom right corner of the diagram area.
+
+FIGURE A.15/Q.705
+**Failure of link AB**
+
+#### A.4.1.2 Restoration of link AB
+
+When the restoration of link AB is completed, the following applies:
+
+- a) B initiates the changeback procedure, by sending a changeback declaration to A via C. Once it has received the changeback acknowledgement, it restarts traffic on the restored link. Moreover, it sends to C a transfer-allowed message, referred to destination A (see 13.3.2/Q.704). When C receives the transfer-allowed message, it stops sending signalling-route-set-test messages to B.
+- b) A initiates the changeback procedure, by sending a changeback declaration to B via C; once it has received the changeback acknowledgement, it restarts traffic on the normal link. The only traffic to be diverted is that for which link AB is the normal link set according to the load sharing rule (see A.3.3.1). It must be pointed out, however, that if there is load sharing on parallel links between B and C, there is the possibility of missequencing. Concerning b), for example, the changeback declaration sent from A to B via C might overrun messages still buffered at signalling point C (due to, e.g. retransmissions on the parallel link CB).
+
+### A.4.2 Example 2: Failure of signalling transfer point D (see Figure A.16)
+
+(Same as A.3.3.4, Example 1.)
+
+
+
+Diagram of a network failure scenario (FIGURE A.16/Q.705). The network consists of nodes A (circle), B (square), C (square), D (square), E (square), and F (circle). Links connect A-B, A-C, B-C, B-D, C-E, D-E, and E-F. Node D is marked with a cross, indicating a failure. Arrows show traffic being diverted from node D to node C. A label 'T1156340-93/d17' is present in the bottom right corner of the diagram area.
+
+FIGURE A.16/Q.705
+**Failure of signalling transfer point D**
+
+#### A.4.2.1 Failure of signalling transfer point D
+
+- a) Changeover is initiated at signalling points B, C and F from blocked links BD, CD and FD to the first priority alternative links BE, CE and FE respectively. Due to the failure of D, the concerned signalling points will receive no changeover acknowledgement message in response, and therefore they will restart traffic on alternative links at the expiry of the time T2 (see Recommendation 5.7.2/Q.704). In addition E will send to B, C and F transfer-prohibited messages referred to destination D. These signalling points (B, C and F) will thus start periodic sending to E of signalling-route-set-test messages referred to D.
+- b) When B receives a transfer-prohibited message from E referred to D, it updates its routing information so that traffic to D will be diverted to C, thus sending a transfer-prohibited message to C referred to D. The same applies to C, and C sends a transfer-prohibited message to B.
+- c) So, when B receives a transfer-prohibited message from C, it finds that destination D has become inaccessible and sends a transfer-prohibited message to A. The same applies to C and thus C also sends a transfer-prohibited message to A. Having received transfer-prohibited messages from both B and C, A recognizes that D has become inaccessible and stops traffic to D.
+- d) In the same manner, i.e. link-by-link transmission of transfer-prohibited messages referred to D, other signalling points B, C, E and F will finally recognize that destination D has become inaccessible. Each signalling point will, therefore, start periodic sending of signalling-route-set-test messages referred to D to their respective adjacent signalling points.
+
+#### A.4.2.2 Recovery of signalling transfer point D
+
+- a) Signalling points B, C, E send traffic restart allowed messages to signalling point D, as soon as signalling point D becomes accessible.
+- b) Signalling transfer point D broadcasts traffic restart allowed messages, after T20 (see 16.8/Q.704) has stopped or expired, to all adjacent SPs.
+- c) Changeback at signalling points B, C and F from the alternative to their normal links is performed. In all the three cases changeback includes the time-controlled diversion procedure (see 6.4/Q.704), since D is still inaccessible via E at B, C and F (as a result of previous reception of transfer-prohibited message from E).
+- d) E sends to B, C and F transfer-allowed messages referred to destination D. These signalling points will thus send transfer allowed messages to their respective adjacent signalling points. Thus, the link-by-link transmission of transfer-allowed messages will declare to all signalling points that destination D has become accessible.
+- e) On reception of a transfer-allowed message, each signalling point stops periodic sending of signalling-route-set-test messages to their respective adjacent signalling points.
+- f) On recovery of the previously unavailable links BD, CD and FD, signalling points B, C and F will restart all the traffic normally routed via signalling transfer point D after T21 (see 16.8/Q.704) has stopped or expired. (They would restart any traffic terminating at D, if D had an endpoint function as well as being an STP, immediately D becomes accessible, that is after successful signalling link tests to D.)
+
+### A.4.3 Example 3: Failure of link between a signalling point and a signalling transfer point, and of the link between that signalling transfer point and that of the same pair (e.g. links DF, DE) (see Figure A.17)
+
+(Same as A.3.3.3, Example 1.)
+
+#### A.4.3.1 Failure of link DE
+
+On failure of link DE, this link is marked unavailable at both signalling transfer points D and E. Since in the absence of failures, link DE does not carry signalling traffic, no change in message routing takes place at this time.
+
+
+
+Diagram of a network topology showing nodes A, B, C, D, E, and F. Node A is connected to B and C. B and C are connected to D and E. D and E are connected to F. The diagram illustrates the failure of links DE and DF. Arrows indicate traffic diversion from links terminating on D to links terminating on E. A label 'T1156350-93/d18' is present in the bottom right corner of the diagram area.
+
+FIGURE A.17/Q.705
+**Failure of links DE and DF**
+
+However, D and E send to signalling points B, C and F transfer-prohibited messages referred to destination E or D respectively. These signalling points will thus start periodic sending of signalling-route-set-test messages, referred to D or E, to E and D respectively.
+
+#### A.4.3.2 Failure of link DF in the presence of failure of link DE
+
+- a) On failure of link DF the following actions occur:
+ - i) Signalling point D which no longer has access to signalling point F indicates this condition to signalling transfer points B and C by sending transfer-prohibited messages. B and C will thus start the periodic sending of signalling-route-set-test messages referred to F, to D.
+ - ii) Emergency changeover from link FD to link FE is initiated at signalling point F, since D becomes inaccessible to F due also to the previous failure.
+- b) On receiving the transfer-prohibited messages forced rerouting is initiated at points B and C. This causes traffic destined to F to be diverted from links terminating on D to links terminating on E. Forced rerouting thus permits recovery from a failure condition caused by a fault in a remote part of the network.
+
+#### A.4.3.3 Restoration of link FD in the presence of failure of link DE
+
+- a) On recovery of link FD the following actions occur:
+ - i) Signalling point D sends a transfer-allowed message to B and C to indicate that D once again has access to F. B and C will thus stop the sending of signalling-route-set-test messages referred to F to D.
+ - ii) F initiates changeback with time controlled diversion from link FE to link FD. This procedure permits changeback to be executed at one end of a link, when it is impossible to notify the other end of the link (in this example, because link DE is unavailable). Traffic in this case is not diverted from the alternative link until a time interval has elapsed, in order to minimize the danger of missequencing messages (see 6.4/Q.704).
+- b) On receiving the transfer-allowed message, controlled rerouting of traffic from the alternative routes (BEF, CEF) to the normal routes (BDF, CDF) is initiated at points B and C. Controlled rerouting involves diversion of traffic to a route which has become available after a time interval (see 8.2.1/Q.704), provisionally set at one second to minimize the danger of missequencing messages.
+
+#### A.4.3.4 Restoration of link DE
+
+On recovery of link DE it is marked available at signalling transfer points D and E. Signalling points D and E send to B, C and F transfer-allowed messages referred to destination E or D respectively. These signalling transfer points will thus stop sending of signalling-route-set-test messages.
+
+### A.4.4 Example 4: Failure of links DF and EF (see Figure A.18)
+
+
+
+The diagram shows a network of nodes A, B, C, D, E, and F. Node A is on the left, connected to B and C. B and C are connected to D and E. D and E are connected to F. The links DF and EF are shown with a slash, indicating failure. Arrows from A to F are stopped. Arrows from F to D and E are stopped. Text labels 'Traffic to F is stopped' and 'All traffic is stopped' are present. The diagram is labeled T1156360-93/d19.
+
+Diagram illustrating the failure of links DF and EF. Nodes A, B, C, D, E, and F are shown. Node A is on the left, connected to B and C. B and C are connected to D and E. D and E are connected to F. The links DF and EF are shown with a slash, indicating failure. Arrows from A to F are stopped. Arrows from F to D and E are stopped. Text labels 'Traffic to F is stopped' and 'All traffic is stopped' are present. The diagram is labeled T1156360-93/d19.
+
+FIGURE A.18/Q.705
+**Failure of links DF and EF**
+
+#### A.4.4.1 Failure of link DF
+
+When the failure of link DF is detected, D and F perform the changeover procedure; D diverts traffic, destined to F, to link DE, while F concentrates all the outgoing traffic on link FE.
+
+In addition, D sends to E a transfer-prohibited message, referred to destination F; E will thus start sending of signalling-route-set-test messages, referred to F, towards D (see also A.4.1.1).
+
+#### A.4.4.2 Failure of link EF in the presence of failure of link DF
+
+- a) When the failure of link EF is detected, the following applies:
+ - i) Since all destinations become inaccessible F stops sending all signalling traffic.
+ - ii) E sends to B, C and D a transfer-prohibited message, referred to destination F. B, C and D start periodic sending of signalling-route-set-test messages referred to F to E.
+- b) When D receives the transfer-prohibited message, it sends to B and C a transfer-prohibited message, referred to destination F [see 13.2.2 ii)/Q.704]. B and C start periodic sending of test messages referred to F to D.
+- c) When B receives the transfer-prohibited messages from D and E, it sends a transfer-prohibited message to C; the same applies for C (it sends the message to B). As soon as B and C have received the transfer-prohibited messages from all the three possible routes (BD, BE and BC, or CD, CE and CB respectively), they send a transfer-prohibited message to A.
+
+NOTE – Depending on the sequence of reception of transfer-prohibited messages at B or C, they may start a forced rerouting procedure on a route not yet declared to be unavailable; such procedure is then aborted as soon as a transfer-prohibited message is received also from that route.
+
+- d) As soon as A receives the transfer-prohibited messages from B and C, it declares destination F inaccessible and stops sending traffic towards it. Moreover, it starts the periodic sending of signalling-route-set-test messages, referred to F, to B and C.
+
+#### A.4.4.3 Restoration of link EF in the presence of failure on link DF
+
+- a) When restoration of link EF is completed, the following applies:
+ - i) Signalling point F restarts traffic on link EF.
+ - ii) E sends a transfer-allowed message, referred to destination F, to B, C and D; moreover, it restarts traffic on the restored link.
+- b) When B and C receive the transfer-allowed message, they send a transfer-allowed message to A and C or A and B, respectively and they stop sending signalling-route-set-test messages to E; moreover, they restart the concerned traffic on link BE or CE respectively.
+- c) When D receives the transfer-allowed message from E, it sends transfer-allowed messages to B and C and stops sending signalling-route-set-test messages to E; moreover, it starts the concerned traffic on link DE. On receipt of the transfer-allowed message, B and C will divert to links BD and CD, by means of a controlled rerouting procedure, traffic carried by links BE and CE for which they are the normal links (see A.3.3). Moreover, they will stop sending signalling-route-set-test messages to D.
+
+NOTE – According to the rules stated in 13.3.2/Q.704, on receipt of transfer-allowed messages from E [phase b) above], B and C should send transfer-allowed messages also to D and E. However, this is not appropriate in the network configurations such as the one here considered, taking into account that
+
+- there is no route, for example, from D (or E) to F via B (or C) and therefore the transfer-allowed messages would be ignored by D and E;
+ - on restarting traffic to F on links BD, BE, CD and CE it would anyway be necessary that B and C send transfer-prohibited messages to D and E, which would contradict the previous transfer-allowed messages.
+- d) As soon as A receives a transfer-allowed message from B or C, it restarts signalling traffic to B and C. If traffic has already been restarted on one link when the transfer-allowed message is received on the other link, a changeback procedure is performed to establish the normal routing situation on both links (i.e. to divert part of the traffic on the latter link).
+
+#### A.4.4.4 Restoration of link DF
+
+When the restoration of link DF is completed, the following applies:
+
+- a) D initiates the changeback procedure to link DF; moreover, it sends to E a transfer-allowed message, referred to destination F.
+- b) F sends signalling-route-set-test message to D referred to the destination points it normally accesses via D. It initiates the changeback procedure to link DF; this procedure refers only to the traffic for which link DF is the normal one, according to the routing rules.
+
+## A.5 Explanatory note from the implementors forum for clarification of load sharing
+
+**A.5.1** In general, to improve the distribution of traffic, load sharing at a particular signalling point (amongst link sets to a given destination) will be on the basis of a part of the signalling link selection field which is different than that part used for load sharing amongst signalling links within a selected link set. In the example represented in Figure 5/Q.704, if link set DF contains more than one signalling link, then the least significant bit of the signalling link selection field is not used in sharing traffic within link set DF amongst the signalling links. Similar considerations can apply to link set DE.
+
+**A.5.2** At an originating signalling point it is assumed that for a given signalling relation, signalling link selection field values are evenly distributed and traffic is shared over the appropriate link sets and signalling links within each link set on this basis. In general, to achieve this a different load sharing rule is needed for each number of link sets, and each number of signalling links within a link set, over which traffic is to be shared. The intention is to attain, for a given signalling relation, as soon as possible, a traffic balance over the link sets and the signalling links within each
+
+link set, based on the signalling link selection field and the numbers of link sets and signalling links within each link set; such an even traffic balance may result if the fixed part of the signalling link selection field is not excluded from consideration by the load sharing rules.
+
+**A.5.3** At a signalling transfer point, for a given signalling relation, signalling link selection field values may not be evenly distributed (see Figure 5/Q.704, signalling transfer point E). A different set of load sharing rules to those for originating signalling points may be provided to deal with this possibility. These are again based on the signalling link selection field and the numbers of link sets and signalling links within each link set, but assume that a particular part of the signalling link selection field is fixed. The fixed part of the signalling link selection field may be different at different signalling transfer points. Where signalling messages for different signalling relations arriving at a particular signalling transfer point do not have the same part of the signalling link selection field fixed, an uneven sharing of traffic for a particular signalling relation amongst the relevant link sets and signalling links within each link set may result.
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.708-199903-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg b/marked/Q/T-REC-Q.708-199903-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b9fe5ac7c88c13e17d34862ebf9babebce594649
--- /dev/null
+++ b/marked/Q/T-REC-Q.708-199903-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e4f3890675bf7f7bce688ae8256e088ba193e0eda7f8a01d8bbc7b59950ce8bd
+size 92778
diff --git a/marked/Q/T-REC-Q.708-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.708-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ef7101f2cd473b38f65d28749285aa431fc4c52c
--- /dev/null
+++ b/marked/Q/T-REC-Q.708-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7062fe51e06885c3cf3e5ca637b411aa8badd1232d955dc96fd273effe6082ff
+size 8232
diff --git a/marked/Q/T-REC-Q.708-199903-I_PDF-E/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Q/T-REC-Q.708-199903-I_PDF-E/d0abac95583b52a3b35f74a215567334_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1e4348ffd328ec35dc5e1c4d3d211f67e111fac7
--- /dev/null
+++ b/marked/Q/T-REC-Q.708-199903-I_PDF-E/d0abac95583b52a3b35f74a215567334_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88cf6737016234eb3bdfe748d2e193df126171e8cf5e664e3a8969303043fa96
+size 29970
diff --git a/marked/Q/T-REC-Q.708-199903-I_PDF-E/raw.md b/marked/Q/T-REC-Q.708-199903-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..73f3e0e971e6eed401d85400135bca92716a048f
--- /dev/null
+++ b/marked/Q/T-REC-Q.708-199903-I_PDF-E/raw.md
@@ -0,0 +1,489 @@
+
+
+
+
+ITU logo: A globe with the letters ITU and a lightning bolt.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.708**
+
+(03/99)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Specifications of Signalling System No. 7 – Message
+transfer part (MTP)
+
+---
+
+**Assignment procedures for international
+signalling point codes**
+
+ITU-T Recommendation Q.708
+
+(Previously CCITT Recommendation)
+
+---
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+# **SWITCHING AND SIGNALLING**
+
+| | |
+|----------------------------------------------------------|--------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 |
+| General | Q.700 |
+| Message transfer part (MTP) | Q.701–Q.709 |
+| Signalling connection control part (SCCP) | Q.711–Q.719 |
+| Telephone user part (TUP) | Q.720–Q.729 |
+| ISDN supplementary services | Q.730–Q.739 |
+| Data user part | Q.740–Q.749 |
+| Signalling System No. 7 management | Q.750–Q.759 |
+| ISDN user part | Q.760–Q.769 |
+| Transaction capabilities application part | Q.770–Q.779 |
+| Test specification | Q.780–Q.799 |
+| Q3 interface | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+
+For further details, please refer to ITU-T List of Recommendations.
+
+# **ASSIGNMENT PROCEDURES FOR INTERNATIONAL SIGNALLING POINT CODES**
+
+## **Summary**
+
+This Recommendation describes the format of the code used to identify international signalling points in the international Signalling System No. 7 network which is identified by the Network Indicator NI=00. This Recommendation, additionally, includes principles and procedures for the assignment of Signalling Area/Network Codes and International Signalling Point Codes.
+
+## **Source**
+
+ITU-T Recommendation Q.708 was revised by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 15th of March 1999.
+
+## FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
+
+The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation the term *recognized operating agency (ROA)* includes any individual, company, corporation or governmental organization that operates a public correspondence service. The terms *Administration*, *ROA* and *public correspondence* are defined in the *Constitution of the ITU (Geneva, 1992)*.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 1999
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+## CONTENTS
+
+| | Page |
+|-------------------------------------------------------------------------------------------------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 4 Abbreviations..... | 1 |
+| 5 Format of the ISPC ..... | 2 |
+| 6 General principles ..... | 2 |
+| 7 Assignment procedures..... | 3 |
+| 8 Criteria for the assignment of a SANC ..... | 4 |
+| 9 Criteria for the assignment of an ISPC ..... | 4 |
+| 10 Responsibilities of the Director of the TSB..... | 5 |
+| 11 Responsibilities of the Administration ..... | 5 |
+| 12 Signalling point operator responsibilities ..... | 6 |
+| 13 Expansion of the ISPC resource ..... | 6 |
+| Annex A – Notification of Assignment or Withdrawal of International Signalling Point Codes (ISPC) for Signalling System No. 7 ..... | 8 |
+| Annex B – Proposed form to be used in accordance with provisions of subclause 9.7 ..... | 10 |
+| Annex C – Assignment evolution ..... | 11 |
+
+## **Introduction**
+
+The worldwide signalling network has two functionally independent levels: the international level and the national level. This provides for a clear division of responsibility for signalling network management and allows identification plans of signalling points in the international network and the different national networks to be independent of one another. Within the international Signalling System No. 7 network a signalling point is identified by an International Signalling Point Code (ISPC). The use of an ISPC within a signalling message and the technical aspects of the signalling network are described in Recommendations of the Q.7xx series.
+
+# **ASSIGNMENT PROCEDURES FOR INTERNATIONAL SIGNALLING POINT CODES**
+
+*(revised in 1999)*
+
+## **1 Scope**
+
+This Recommendation describes the format of an ISPC in the international Signalling System No. 7 network identified by the Network Indicator NI=00. Additionally, it provides principles and procedures for the assignment of both Signalling Area/Network Code (SANCs) and ISPCs.
+
+## **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.700 (1993), *Introduction to CCITT Signalling System No. 7*.
+
+## **3 Definitions**
+
+This Recommendation defines the following terms:
+
+- 3.1 signalling point:** A node in a signalling network that originates and receives signalling messages, or transfers signalling messages from one signalling link to another, or both.
+- 3.2 signalling relation:** An association between two signalling points that allows interexchange of Signalling System No. 7 messages.
+- 3.3 signalling point code:** A code used to identify a signalling point and processed within the Message Transfer Part (MTP) of each signalling point and within users of the MTP.
+- 3.4 international signalling point code (ISPC):** A signalling point code with a unique 14-bit format used at the international level for signalling message routing and identification of signalling points involved. The ISPC is used in signalling messages containing the Network Indicator NI=00.
+
+## **4 Abbreviations**
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|-------|----------------------------------------------------------------------------------|
+| GMSC | Gateway Mobile Switching Centre |
+| ISC | International Switching Centre |
+| ISPC | International Signalling Point Code |
+| ITU | International Telecommunication Union |
+| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector |
+| LR | Location Register |
+| MTP | Message Transfer Part |
+
+| | |
+|------|------------------------------------------|
+| NI | Network Indicator |
+| NMC | Network Management Centre |
+| OMC | Operation and Maintenance Centre |
+| SANC | Signalling Area/Network Code |
+| SCCP | Signalling Connection Control Part |
+| SCP | Service Control Point |
+| SEP | Signalling End Point |
+| SP | Signalling Point |
+| SSP | Service Switching Point |
+| STP | Signalling Transfer Point |
+| TSB | Telecommunication Standardization Bureau |
+
+## 5 Format of the ISPC
+
+5.1 The format of the 14-bit binary code used for the identification of international signalling points is illustrated in Figure 1. The binary code is represented by three (3) decimal numbers: the first indicating the three (3) most significant bits (NML), with a range of 0 to 7; the second indicating the following eight (8) bits (K-D), with a range of 000 to 255; and the third consisting of the three (3) least significant bits (CBA), with a range of 0 to 7. The combination of the fields containing bits NML and bits K-D is regarded as the SANC. The three (3) bits (CBA) identify a specific signalling point which when combined with the SANC forms the 14-bit ISPC (e.g. 2-068-1).
+
+
+
+| | | | | | | | | | | | | | |
+|--------------------------------------------|---|---|--------|---|---|---|---|---|---|---|---------------------------------|---|---|
+| N | M | L | K | J | I | H | G | F | E | D | C | B | A |
+| 3 bits | | | 8 bits | | | | | | | | 3 bits | | |
+| Signalling area network code (SANC) | | | | | | | | | | | Signalling point identification | | |
+| International signalling point code (ISPC) | | | | | | | | | | | | | |
+
+T11105130-99
+
+Diagram showing the format of the International Signalling Point Code (ISPC). It is a 14-bit binary code divided into three parts: NML (3 bits), KJDHGFED (8 bits), and CBA (3 bits). The NML and KJDHGFED parts together form the Signalling area network code (SANC). The CBA part is the Signalling point identification. The entire 14-bit code is the International signalling point code (ISPC).
+
+Figure 1/Q.708 – Format of the International Signalling Point Code (ISPC)
+
+5.2 The fields within the format of the ISPC have only an administrative use and are not to be used individually in any way by the protocol or signalling functions.
+
+## 6 General principles
+
+6.1 The SANC/ISPC resource should be managed in such a manner as to ensure adequate capacity to meet the demand for the resource. The need for conservation of the resource is not a reason in itself to deny an application for the assignment of the resource.
+
+6.2 SANC/ISPC resources should be efficiently utilized and managed (e.g. only a single ISPC is to be assigned to a signalling point).
+
+6.3 SANC/ISPC resources are to be assigned with fairness and equity.
+
+6.4 Assignment confers use of the SANC and ISPC resource but does not imply ownership by the Member State and signalling point operator, respectively.
+
+**6.5** Signalling point codes for the national level and the international level are assigned separately. The assignment of a point code in a national network does not automatically entitle the code holder to an ISPC.
+
+## **7 Assignment procedures**
+
+**7.1** SANCs shall be assigned by the Director of the TSB to a Member State1, 2, Country (or geographical area).
+
+**7.2** A single SANC is to be initially assigned to a new Member State. The SANC is combined with eight signalling point identifications to create eight ISPCs.
+
+**7.3** An ISPC(s) is to be assigned, as required, to signalling point operators by each Member State's designated Administrator3 in accordance with the rules and procedures of the Member State and this Recommendation. ISPC assignments will be on an individual ISPC basis and not on a SANC basis. The Administrator will notify the Director of the TSB of the assignment.
+
+**7.4** The SANC ranges beginning with 0 and 1 (identified by bits NML in Figure 1) are reserved for future use.
+
+**7.5** Assignment of a SANC(s) to a Member State will be made from spare SANCs within the same range from which SANCs have been currently assigned to that Member State. If there are no available spares within this range, the TSB will assign a SANC(s) from available spare(s) in another range.
+
+**7.6** A signalling point4 is assigned only one ISPC.
+
+**7.7** An ISPC(s) may be assigned by the Administrator for test purposes. However, this assignment should not be considered a permanent one and may be subject to reassignment as necessary.
+
+**7.8** An ISPC derived from a SANC assigned to a Member State is expected to be used within the territory of that Member State.
+
+**7.9** In exceptional cases, an ISPC derived from a SANC assigned to one Member State may be used in another Member State with the agreement of the Administrations of both Member States (see 9.7).
+
+**7.10** ISPCs are not transferable between signalling point operators. ISPCs may not be sold, licensed or traded by the signalling point operators. ISPCs may not be transferred, except in the case of a merger, acquisition, divestiture, or joint venture. The Administrator(s) shall be notified of any such transfer by the signalling point operators.
+
+---
+
+1 The terms "Member State", "Country" (or geographical area), and/or "Administration" shall be considered to have the same meaning for purposes of this Recommendation.
+
+2 For purposes of this Recommendation, Intergovernmental Organizations Operating Satellite Systems may be assigned SANCs.
+
+3 The term "Administrator" is to be used hereafter to indicate a Member State's/Administration's designated Administrator for the purpose of requesting SANCs or assigning ISPCs.
+
+4 A signalling point being a part of more than one signalling network, e.g. when serving as an international gateway, should be assigned a signalling point in each signalling network.
+
+## **8 Criteria for the assignment of a SANC**
+
+**8.1** A request for a SANC(s) is to be made by the Administration in writing to the Director of the TSB.
+
+**8.2** In order to request an additional SANC(s) an Administration must provide the Director of the TSB notification (see 11.2) of the current assignment of ISPCs by that Administration.
+
+**8.3** Assignment of an additional SANC(s) requires assignment of 75 percent of the ISPCs in all SANCs previously assigned to the Administration concerned5.
+
+## **9 Criteria for the assignment of an ISPC**
+
+The criteria listed below are provided as a guideline to assist Administrations in assigning and administering assignments for an ISPC.
+
+**9.1** The signalling point operator6 is to apply in writing to the Administrator.
+
+**9.2** The signalling point operator is to certify conformance to the laws and regulations of the Member State in which the ISPC will be used.
+
+**9.3** The signalling point operator has put into service or is about to put into service a signalling point having at least one MTP signalling relation in the international signalling network.
+
+**9.4** The signalling point operator is to comply with relevant ITU-T Recommendations (e.g. Q.7xx).
+
+**9.5** The signalling point operator is to provide the Administrator with the information required in 11.2 as a minimum. The Administrator may require additional information, such as:
+
+- Contact person;
+- Nature of use in the network (more than one function may apply):
+ - STP,
+ - SEP (SP without STP function),
+ - SCCP relay,
+ - ISC,
+ - GMSC,
+ - LR,
+ - OMC,
+ - SCP,
+ - SSP,
+ - Other;
+- Signalling point manufacturer/type;
+- Physical address of the signalling point;
+- In-service date of the signalling point (month/year);
+- Identification of at least one planned MTP signalling relation:
+ - name and address of distant signalling point,
+
+---
+
+5 This may be on a per country or dependent territory basis.
+
+6 The term "signalling point operator" is used even if an applicant has not yet any signalling point in operation.
+
+- location of distant signalling point,
+- ISPC of distant signalling point, if known.
+
+**9.6** The signalling point operator is to confirm that the requested ISPC shall be placed in service within the period defined by the Administration (e.g. 12 months starting from the date of the assignment).
+
+**9.7** The signalling point operator applying for an ISPC assignment under the provisions of 7.9 will request permission in writing (attaching the proposed form in Annex B) from the Administration of the Member State where the ISPC will be put into service. The signalling point operator will apply to its Administration (attaching the completed proposed form in Annex B obtained above) for an ISPC assignment.
+
+## **10 Responsibilities of the Director of the TSB**
+
+**10.1** The Director of the TSB shall assign an initial SANC or additional SANC(s) in accordance with the Assignment procedures (clause 7) and Criteria (clause 8) in response to a request from an Administration.
+
+**10.2** Assignments shall be made, normally, within one calendar month from receipt of the request; if not, the requesting Administration is to be notified as to why the assignment has not been made [e.g. that the request does not meet the Assignment procedures (clause 7) and/or Criteria (clause 8), indicating the relevant clause or other reasons].
+
+**10.3** The Director of the TSB will notify the Chairman of the Study Group responsible for this Recommendation if the content of this Recommendation does not provide the TSB with sufficient direction to fulfill an application for a SANC(s) from an Administration.
+
+**10.4** The TSB will publish in the Operational Bulletin the notification of assigned ISPCs as received from Administrations on the form in Annex A. Complete lists of the ISPC and SANC assignments will be published (at least annually) as annexes to the Operational Bulletin. In addition, the lists will be made available electronically for remote access (update every three months). The annexes will contain three lists as follows:
+
+- 1) a list of SANCs in numerical order and the country to which each SANC has been assigned;
+- 2) a list of the countries in alphabetical order and of the SANCs in numerical order assigned to each country;
+- 3) a list of the countries in alphabetical order where each country name is followed by a list of ISPCs in numerical order reported by the country. The entry for each ISPC contains the name of the signalling point operator, the unique name of the signalling point, and the country where the signalling point has been, or is to be put into service if it is not used in the country to which the SANC was assigned.
+
+## **11 Responsibilities of the Administration**
+
+The following items of responsibility are being provided as a guideline to assist Administrations in developing their own procedures:
+
+**11.1** Assign or withdraw an ISPC(s). Notify the Director of the TSB of the assignment/withdrawal within 90 days, using the form in Annex A. The Administration is encouraged to respond to a request for an ISPC within 90 days from receipt of the request.
+
+**11.2** Provide the following information to the Director of the TSB on signalling point assignments or withdrawals:
+
+- ISPC assigned or withdrawn;
+
+- unique name of signalling point that may include location (city/town);
+- name of (former) signalling point operator;
+- Member State where signalling point will be put into service (if assigned under 7.9).
+
+**11.3** When an assignment of an ISPC is made under the provisions of 7.9, the Administration of the territory within which the ISPC is to be used will note on the proposed Annex B form its concurrence with the agreement. The proposed Annex B form shall accompany the Annex A form when the Administration assigning the point code informs the TSB of the assignment.
+
+**11.4** An ISPC assignment should be withdrawn if the signalling point operator to whom the ISPC was assigned has not placed the ISPC into service within the period as established in accordance with 9.6. However, there may be extenuating circumstances (e.g. the vendor missed installation date, the distant end was not ready, etc.) in which case the Administrator should be contacted to establish a new in-service date or other resolution.
+
+**11.5** Notify the Director of the TSB, preferably within 90 days, of any change in the published information provided in accordance with 11.2.
+
+**11.6** Administrations should publish their rules for use of, application for, and assignment of, ISPCs. Such rules should also include a rationale for withdrawal of ISPCs for other than a missed timeframe, e.g.:
+
+- ISPC is being used in a different way from that for which it was assigned.
+- Resource is being used by a signalling point operator other than the one to whom the ISPC was assigned (i.e. a transfer was made without the Administrator's knowledge).
+- Assigned ISPC is no longer in use or required by the signalling point operator.
+
+**11.7** ISPCs which have been withdrawn should have an adequate ageing period before becoming available for reassignment. (It is recommended that the ageing period be between 6 and 18 months.)
+
+## **12 Signalling point operator responsibilities**
+
+Some responsibilities are listed below. These are provided as a guide to assist Administrations in developing their own requirements and procedures. Additional responsibilities may be derived from the criteria in clause 9.
+
+**12.1** The signalling point operator should inform its Administrator of any change of information that was requested by that Administrator under the terms of 9.5.
+
+**12.2** Additionally, if not specifically required under the terms of 9.5, the signalling point operator should inform its Administrator about any changes such as its name, its registered office, the name of its contact person or the location where the signalling point is in operation, etc.
+
+**12.3** If the procedure in 7.9 is to be invoked, then the signalling point operator will be responsible for contacting both Administrations and for obtaining their agreement.
+
+## **13 Expansion of the ISPC resource**
+
+Given the rapid increase in the size and use of the current Signalling System No. 7 network, it is difficult to forecast the potential demand for ISPCs. An expansion plan is presented as the basis for ongoing work with regard to increasing the availability of the ISPC resource. In order to meet future requirements, a phased plan is proposed to remove the constraints on the use of specific ranges and to change the management of the resource.
+
+The plan proposes and encourages continued close cooperation and collaboration between the TSB and the entities responsible for assigning and for monitoring the assignment of the ISPC resource.
+
+**13.1** Figure C.1 provides an outline of the procedure for the TSB to monitor the assignment of the current SANC resource and to trigger actions to ensure that there is sufficient resource to meet future needs.
+
+**13.2** The TSB will monitor the assignment of the available SANC resource and inform the Study Group responsible for this Recommendation with regard to the assignment situation as appropriate.
+
+**13.3** When 70% of the available SANC resource from ranges 2-7 (identified by bits NML) has been assigned, the Study Group responsible for this Recommendation will commence studies on alternative solutions to provide additional SANC/ISPC resource. Once the Study Group has commenced its studies, the TSB will report at each Study Group meeting on the SANC assignment situation.
+
+**13.4** When 95% of the available SANC resource from ranges 2-7 (identified by bits NML) has been assigned, the TSB will notify the Study Group. If the Study Group has not yet agreed on an alternative solution, the Study Group should make the SANC range 1 available to the TSB for assignment.
+
+**13.5** When 90% of the available SANC resource from ranges 1-7 (identified by bits NML) has been assigned, the TSB will notify the Study Group. If the Study Group has not yet agreed on an alternative solution, then the Study Group should make the SANC range 0 available to the TSB for assignment. Caution is recommended with regard to the use of zero in all fields of an ISPC.
+
+**13.6** Similarly, when 80% of the total available SANC resource from ranges 0-7 (identified by bits NML) has been assigned, and if the study of alternative solutions has not yet provided an agreed-upon solution, then it is proposed that the TSB in consultation with the Study Group responsible for this Recommendation should consider the establishment of a centralized resource pool of all the ISPCs not assigned at that time. This means that ISPCs not yet assigned from SANCs already assigned to Member States will be returned to the TSB for centralized management. The TSB will then assume responsibility for the assignment and management of ISPCs.
+
+**13.7** It is desirable that before 90% of the total ISPC resource pool has been assigned, the new procedure for the provision of ISPCs be made available for implementation.
+
+## ANNEX A
+
+### **Notification of Assignment or Withdrawal of International Signalling Point Codes (ISPC) for Signalling System No. 7**
+
+To be returned to ITU/TSB Fax No.: +41 22 730 5853
+
+This form should be used to notify the Director of the TSB of ISPCs that have been assigned or withdrawn by a Member State since the last notification.
+
+**Country/Area:** \_\_\_\_\_
+
+**Member State Contact-person Name:** \_\_\_\_\_
+
+**Address:** \_\_\_\_\_
+
+\_\_\_\_\_
+
+\_\_\_\_\_
+
+**Tel:** \_\_\_\_\_ **Fax:** \_\_\_\_\_ **E-mail:** \_\_\_\_\_
+
+**Table A.1/Q.708**
+
+| ISPC | Unique name of the Signalling Point | Name of the Signalling Point Operator | Country where Signalling Point is to be put into service under subclause 7.9a) |
+|------------------------------------------------------------------------------|--------------------------------------------|----------------------------------------------|--------------------------------------------------------------------------------------------------|
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| | | | |
+| a) An entry is only made in this column if subclause 7.9 applies. | | | |
+
+**Recommendation Q.708 (03/99)** 9
+
+## ANNEX B
+
+### Proposed form to be used in accordance with provisions of subclause 9.7
+
+(Date)
+
+**To:** (Signalling point operator making application for ISPC)
+
+**From:** (Member State/Administration/Administrator where an ISPC is to be put into service)
+
+(Applicable Administration title) hereby agrees to allow (name of signalling point operator) to put an International Signalling Point Code (ISPC) into service when assigned by (Member State/Administration/Administrator of the signalling point operator), in accordance with the provisions of ITU-T Recommendation Q.708 (subclause 7.9), in the country/territory of (Member State/Administration where the ISPC is to be put into service).
+
+(Signature)
+
+(Date signed)
+
+(Authorized Signature for Member State/Administration/Administrator)
+
+## ANNEX C
+
+### Assignment evolution
+
+
+
+| Assignment process | Trigger mechanism |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|
+| 1) Allocation from SANC ranges 2-7
(1536 SANCs available) | 70% of available SANCs assigned
(See 13.3) |
+| 2) The Study Group starts considering alternative solutions | 95% of available SANCs assigned
(See 13.4) |
+| 3) Open range 1
(1792 SANCs available) | 90% of available SANCs assigned
(See 13.5) |
+| 4) Open range 0
(2048 SANCs available) | 80% of total available SANCs assigned
(See 13.6) |
+| 5) Centralized assignment of ISPCs
ISPC register established
Create a single ISPC Resource Pool
Registrar assigns individual ISPCs
(16 320 ISPCs available) | Solution to provide additional signalling point code resource
90% of total ISPCs assigned
(See 13.7) |
+| 6) Expand resource | |
+
+T11100550-98
+
+**Figure C.1/Q.708 – Assignment evolution**
+
+
+
+# ITU-T RECOMMENDATIONS SERIES
+
+- Series A Organization of the work of the ITU-T
+- Series B Means of expression: definitions, symbols, classification
+- Series C General telecommunication statistics
+- Series D General tariff principles
+- Series E Overall network operation, telephone service, service operation and human factors
+- Series F Non-telephone telecommunication services
+- Series G Transmission systems and media, digital systems and networks
+- Series H Audiovisual and multimedia systems
+- Series I Integrated services digital network
+- Series J Transmission of television, sound programme and other multimedia signals
+- Series K Protection against interference
+- Series L Construction, installation and protection of cables and other elements of outside plant
+- Series M TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits
+- Series N Maintenance: international sound programme and television transmission circuits
+- Series O Specifications of measuring equipment
+- Series P Telephone transmission quality, telephone installations, local line networks
+- Series Q Switching and signalling**
+- Series R Telegraph transmission
+- Series S Telegraph services terminal equipment
+- Series T Terminals for telematic services
+- Series U Telegraph switching
+- Series V Data communication over the telephone network
+- Series X Data networks and open system communications
+- Series Y Global information infrastructure and Internet protocol aspects
+- Series Z Languages and general software aspects for telecommunication systems
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg b/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ea78ff2f08bc48f4b00fabeb063c1246f607699a
--- /dev/null
+++ b/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1d27432d5e20bce4ee2c38d8671544803fa293000143e89e85899f75b5ebefb2
+size 125560
diff --git a/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg b/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ee40c4d06bbc38a7bf6243d54223b6e1c01b1c43
--- /dev/null
+++ b/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:17eaa49771c7d9ba04ca6f59f739845bd38370f7c4635488a0358a2b2b4b0a98
+size 123638
diff --git a/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/145d00f59802048185303f15937ea65c_img.jpg b/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/145d00f59802048185303f15937ea65c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f3af0c1259d0df08a4cb481cdb3d3e7a8bd585ca
--- /dev/null
+++ b/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/145d00f59802048185303f15937ea65c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c21a0b7ff1ec5f0f1e73e952a02aa75802a5ddc5ed1958f305613a07b3a978e
+size 43392
diff --git a/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cc6438bcedc9e72173b2d8e74cd31c264ae32aeb
--- /dev/null
+++ b/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:40203e46b9f9a68e88bdb204bdd4b7e5899358c088ed2f2902abbc4eb57db8cb
+size 8190
diff --git a/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg b/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bdb151fd2239d6eaceb0d43fda2ed15ac66186a3
--- /dev/null
+++ b/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eaffc06b40a0692a3537c7e2978622f819fb8b964bb519f101239033c2e4843b
+size 63809
diff --git a/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/6be06b7dc72bb42afcb3465394667c3b_img.jpg b/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/6be06b7dc72bb42afcb3465394667c3b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ba4fa78c9a0b2a2fa3873f735ff7b432a2bf870b
--- /dev/null
+++ b/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/6be06b7dc72bb42afcb3465394667c3b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:694be3e2d10c3125b44ece800cd15105802d41230b4af5d74b659d2295831fd3
+size 39223
diff --git a/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d0a6132e97e25fb79f3bd23650f5b6ec93c0da15
--- /dev/null
+++ b/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5f3f0a83581df7a317c36f60c1c475188d17b1493a144a11da22d7b78cc54d7c
+size 25606
diff --git a/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg b/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..08e9df4e5cf4ba97d2f7c761f010ff8cef14f983
--- /dev/null
+++ b/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a033c6ff8392bdabcb613c4573ea0d8e031a5e088d28826c360a245a19898317
+size 63214
diff --git a/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/b2ddf2a678bd20b1b491023eb1db6458_img.jpg b/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/b2ddf2a678bd20b1b491023eb1db6458_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..569eeead54a9f2289e051f2beb70bdd5b90074e2
--- /dev/null
+++ b/marked/Q/T-REC-Q.733.3-199706-I_PDF-E/b2ddf2a678bd20b1b491023eb1db6458_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c6615c4bb2a0affc9077c2e1380fe8dc1fa9c5710b6987ff4533e017c5487beb
+size 39601
diff --git a/marked/Q/T-REC-Q.762-199912-I_PDF-E/raw.md b/marked/Q/T-REC-Q.762-199912-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..161ddd6d21a2dba1606fed98394496f75c3b5b66
--- /dev/null
+++ b/marked/Q/T-REC-Q.762-199912-I_PDF-E/raw.md
@@ -0,0 +1,932 @@
+
+
+
+
+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.762**
+
+(12/1999)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Specifications of Signalling System No. 7 – ISDN user part
+
+---
+
+**Signalling System No. 7 – ISDN User Part
+general functions of messages and signals**
+
+ITU-T Recommendation Q.762
+
+(Formerly CCITT Recommendation)
+
+---
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+# SWITCHING AND SIGNALLING
+
+| | |
+|----------------------------------------------------------|--------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 |
+| DIGITAL EXCHANGES | Q.500-Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.849 |
+| General | Q.700 |
+| Message transfer part (MTP) | Q.701-Q.709 |
+| Signalling connection control part (SCCP) | Q.711-Q.719 |
+| Telephone user part (TUP) | Q.720-Q.729 |
+| ISDN supplementary services | Q.730-Q.739 |
+| Data user part | Q.740-Q.749 |
+| Signalling System No. 7 management | Q.750-Q.759 |
+| ISDN user part | Q.760-Q.769 |
+| Transaction capabilities application part | Q.770-Q.779 |
+| Test specification | Q.780-Q.799 |
+| Q3 interface | Q.800-Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 |
+| INTELLIGENT NETWORK | Q.1200-Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 |
+| BROADBAND ISDN | Q.2000-Q.2999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## **ITU-T Recommendation Q.762**
+
+### **Signalling System No. 7 – ISDN User Part general functions of messages and signals**
+
+### **Summary**
+
+This ITU-T Recommendation describes the messages, parameters and the signalling information contained within parameters used by the ISDN user part protocol, and their function.
+
+### **Source**
+
+ITU-T Recommendation Q.762 was prepared by ITU-T Study Group 11 (1997-2000) and approved under the WTSC Resolution 1 procedure on 3 December 1999.
+
+# FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSC Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2001
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+## CONTENTS
+
+| | | Page |
+|-----|-----------------------------|-------------|
+| 1 | General ..... | 1 |
+| 1.1 | Scope ..... | 1 |
+| 1.2 | References ..... | 1 |
+| 1.3 | Terms and definitions ..... | 1 |
+| 1.4 | Abbreviations ..... | 2 |
+| 2 | Signalling messages ..... | 4 |
+| 3 | Signalling parameters ..... | 7 |
+| 4 | Parameter information ..... | 12 |
+
+## ITU-T Recommendation Q.762
+
+### Signalling System No. 7 – ISDN User Part general functions of messages and signals
+
+# 1 General
+
+## 1.1 Scope
+
+This ITU-T Recommendation describes the elements of signalling information used by the ISDN user part protocol and their function. The encoding of these elements, the format of the messages in which they are conveyed, and an indication of whether or not they are for national use, are described in ITU-T Recommendation Q.763 [1].
+
+## 1.2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
+
+- [1] ITU-T Recommendation Q.763 (1999), *Signalling System No. 7 – ISDN user part formats and codes*.
+- [2] CCITT Recommendation Q.28 (1988), *Determination of the moment of the called subscriber's answer in the automatic service*.
+- [3] CCITT Recommendation E.260 (1988), *Basic technical problems concerning the measurement and recording of call durations*.
+- [4] CCITT Recommendation Q.101 (1988), *Facilities provided in international semi-automatic working*.
+- [5] ITU-T Recommendation Q.1218 (1995), *Interface Recommendation for intelligent network CS-1*.
+- [6] ITU-T Recommendation Q.1228 (1997), *Interface Recommendation for intelligent network CS-2*.
+- [7] ITU-T Recommendation E.412 (1998), *Network management controls*.
+- [8] ITU-T Recommendation Q.850 (1998), *Use of cause and location in the digital subscriber Signalling System No. 1 and Signalling System No. 7 ISDN user part*.
+- [9] CCITT Recommendation X.229 (1988), *Remote Operations: Protocol specification*.
+- [10] ITU-T Recommendation X.121 (1996), *International numbering plan for public data networks*.
+- [11] CCITT Recommendation E.212 (1988), *Identification plan for land mobile stations*.
+- [12] ITU-T Recommendation Q.704 (1996), *Signalling network functions and messages*.
+
+## 1.3 Terms and definitions
+
+See clauses 2 to 4.
+
+## 1.4 Abbreviations
+
+This ITU-T Recommendation uses the following abbreviations:
+
+| | |
+|--------|----------------------------------------------|
+| APP | Application Transport Parameter |
+| ASE | Application Service Element |
+| ATII | Application Transport Instruction Indicators |
+| CCBS | Completion of Calls to Busy Subscriber |
+| CCNR | Completion of Calls on No Reply |
+| CCSS | Call Completion Service Setup |
+| DNIC | Data Network Identification Code |
+| ECT | Explicit Call Transfer |
+| GVNS | Global Virtual Network Service |
+| ID | Identifier |
+| IN | Intelligent Network |
+| ISC | International Switching Centre |
+| LFB | Look For Busy |
+| MCID | Malicious Call Identification |
+| MLPP | Multilevel Precedence and Pre-emption |
+| MNIC | Mobile Network Identification Code |
+| PDU | Protocol Data Unit |
+| QoR | Query on Release |
+| ROER | Remote Operation Error |
+| ROIV | Remote Operation Invoke |
+| RORJ | Remote Operation Reject |
+| RORS | Remote Operation Result |
+| SCCP | Signalling Connection Control Part |
+| SCF | Service Control Function |
+| SLR | Segmentation Local Reference |
+| UID | User Interactive Dialogue |
+| WGS-84 | World Geodetic System 1984 |
+
+Table 1 defines the acronyms used for ISDN user part messages.
+
+**Table 1/Q.762 – ISDN user part message acronyms**
+
+| Acronym | Message |
+|----------------|---------------------------------------------------|
+| ACM | Address complete |
+| ANM | Answer |
+| APM | Application transport |
+| BLA | Blocking acknowledgement |
+| BLO | Blocking |
+| CCR | Continuity check request |
+| CFN | Confusion |
+| CGB | Circuit group blocking |
+| CGBA | Circuit group blocking acknowledgement |
+| CGU | Circuit group unblocking |
+| CGUA | Circuit group unblocking acknowledgement |
+| CON | Connect |
+| COT | Continuity |
+| CPG | Call progress |
+| CRG | Charge information |
+| CQM | Circuit group query |
+| CQR | Circuit group query response |
+| DRS | Delayed release (reserved – used in 1988 version) |
+| FAA | Facility accepted |
+| FAC | Facility |
+| FAR | Facility request |
+| FOT | Forward transfer |
+| FRJ | Facility reject |
+| GRA | Circuit group reset acknowledgement |
+| GRS | Circuit group reset |
+| IAM | Initial address |
+| IDR | Identification request |
+| IRS | Identification response |
+| INF | Information |
+| INR | Information request |
+| LPA | Loop back acknowledgement |
+| LOP | Loop prevention |
+| NRM | Network resource management |
+| OLM | Overload |
+| PAM | Pass-along |
+| PRI | Pre-release information |
+| REL | Release |
+| RES | Resume |
+| RLC | Release complete |
+| RSC | Reset circuit |
+| SAM | Subsequent address |
+| SDM | Subsequent directory number |
+| SGM | Segmentation |
+| SUS | Suspend |
+| UBL | Unblocking |
+| UBA | Unblocking acknowledgement |
+| UCIC | Unequipped circuit identification code |
+| UPA | User part available |
+| UPT | User part test |
+| USR | User-to-user information |
+
+# 2 Signalling messages
+
+**2.1 Address Complete Message (ACM):** A message sent in the backward direction indicating that all the address signals required for routing the call to the called party have been received.
+
+**2.2 Answer message (ANM):** A message sent in the backward direction indicating that the call has been answered. In semi-automatic working, this message has a supervisory function. In automatic working, this message is used in conjunction with charging information in order to:
+
+- start metering the charge to the calling subscriber (see Recommendation Q.28 [2]); and
+- start measurement of call duration for international accounting purposes (see Recommendation E.260 [3]).
+
+**2.3 Application Transport message (APM):** A message sent in either direction to convey application information using the Application Transport mechanism.
+
+**2.4 Blocking message (BLO):** A message sent only for maintenance purposes to the exchange at the other end of a circuit, to cause an engaged condition of that circuit for subsequent calls outgoing from that exchange. When a circuit is used in the bothway mode of operation, an exchange receiving the blocking message must be capable of accepting incoming calls on the concerned circuit unless it has also sent a blocking message. Under certain conditions, a blocking message is also a proper response to a reset circuit message.
+
+**2.5 Blocking Acknowledgement message (BLA):** A message sent in response to a blocking message indicating that the circuit has been blocked.
+
+**2.6 Call Progress message (CPG):** A message, sent in either direction during the setup or active phase of the call, indicating that an event, which is of significance, and should be relayed to the originating or terminating access, has occurred.
+
+**2.7 Charge information message (CRG):** Information sent in either direction for accounting and/or call charging purposes.
+
+**2.8 Circuit Group Blocking message (CGB):** A message sent to the exchange at the other end of an identified group of circuits to cause an engaged condition of this group of circuits for subsequent calls outgoing from that exchange. An exchange receiving a circuit group blocking message must be able to accept incoming calls on the group of blocked circuits unless it has also sent a blocking message. Under certain conditions, a circuit group blocking message is also a proper response to a reset circuit message.
+
+**2.9 Circuit Group Blocking Acknowledgement message (CGBA):** A message sent in response to a circuit group blocking message to indicate that the requested group of circuits has been blocked.
+
+**2.10 circuit Group Reset message (GRS):** A message sent to release an identified group of circuits when, due to memory mutilation or other causes, it is unknown whether for example, a release or release complete message is appropriate for each of the circuits in the group. If at the receiving end a circuit is remotely blocked, reception of this message should cause that condition to be removed.
+
+**2.11 circuit Group Reset Acknowledgement message (GRA):** A message sent in response to a circuit group reset message and indicating that the requested group of circuits has been reset. The message also indicates the maintenance blocking state of each circuit.
+
+**2.12 Circuit Group Unblocking message (CGU):** A message sent to the exchange at the other end of an identified group of circuits to cause cancellation in that group of circuits of an engaged condition invoked earlier by a blocking or circuit group blocking message.
+
+- 2.13 Circuit Group Unblocking Acknowledgement message (CGUA):** A message sent in response to a circuit group unblocking message to indicate that the requested group of circuits has been unblocked.
+- 2.14 Circuit group Query Message (CQM):** A message sent on a routine or demand basis to request the far-end exchange to give the state of all circuits in a particular range.
+- 2.15 Circuit group Query Response message (CQR):** A message sent in response to a circuit group query message to indicate the state of all circuits in a particular range.
+- 2.16 Confusion message (CFN):** A message sent in response to any message (other than a confusion message) if the exchange does not recognize the message or detects a part of the message as being unrecognizable.
+- 2.17 Connect message (CON):** A message sent in the backward direction indicating that all the address signals required for routing the call to the called party have been received and that the call has been answered.
+- 2.18 Continuity message (COT):** A message sent in the forward direction indicating whether or not there is continuity on the preceding circuit(s) as well as of the selected circuit to the following exchange, including verification of the communication path across the exchange with the specified degree of reliability.
+- 2.19 Continuity Check Request message (CCR):** A message sent by an exchange for a circuit on which a continuity check is to be performed, to the exchange at the other end of the circuit, requesting continuity checking equipment to be attached.
+- 2.20 Facility Accepted message (FAA):** A message sent in response to a facility request message indicating that the requested facility has been invoked.
+- 2.21 Facility message (FAC):** A message sent in either direction at any phase of the call to request an action at another exchange. The message is also used to carry the results, error or rejection of a previously requested action.
+- 2.22 Facility Reject message (FRJ):** A message sent in response to a facility request message to indicate that the facility request has been rejected.
+- 2.23 Facility Request message (FAR):** A message sent from an exchange to another exchange to request activation of a facility.
+- 2.24 Forward Transfer message (FOT):** A message sent in the forward direction on semi-automatic calls when the outgoing international exchange operator wants the help of an operator at the incoming international exchange. The message will normally serve to bring an assistance operator (see Recommendation Q.101 [4]) into the circuit if the call is automatically set up at the exchange. When the call is completed via an operator (incoming or delay operator) at the incoming international exchange, the message should preferably cause this operator to be recalled.
+- 2.25 Identification Request message (IDR):** A message sent in the backward direction to request action regarding the malicious call identification supplementary service.
+- 2.26 Identification Response message (IRS):** A message sent in response to the identification request message.
+- 2.27 Information message (INF):** A message sent to convey information in association with a call, which may have been requested in an information request message.
+- 2.28 Information Request message (INR):** A message sent by an exchange to request information in association with a call.
+- 2.29 Initial Address message (IAM):** A message sent in the forward direction to initiate seizure of an outgoing circuit and to transmit number and other information relating to the routing and handling of a call.
+
+- 2.30 Loop back Acknowledgement message (LPA):** A message sent in the backward direction in response to a continuity check request message indicating that a loop (or transceiver in the case of a 2-wire circuit) has been connected.
+- 2.31 Loop Prevention message (LOP):** A message sent to convey information required by the ECT supplementary service.
+- 2.32 Network Resource Management message (NRM):** A message sent in order to modify network resources associated with a certain call. The message is sent along an established path in any direction in any phase of the call.
+- 2.33 Overload Message (OLM):** A message sent in the backward direction, on non-priority calls in response to an IAM, to invoke temporary trunk blocking of the circuit concerned when the exchange generating the message is subject to load control.
+- 2.34 Pass-Along Message (PAM):** A message that may be sent in either direction to transfer information between two signalling points along the same signalling path as that used to establish a physical connection between those two points.
+- 2.35 Pre-release Information message (PRI):** A message to be used with the Release message for the transport of information where sending of that information in the Release message itself would cause compatibility problems with ISUP 1992 and subsequent versions of the ISUP protocol.
+- 2.36 Release message (REL):** A message sent in either direction to indicate that the circuit is being released due to the reason (cause) supplied and is ready to be put into the idle state on receipt of the release complete message. Where the call is to be redirected the message will also carry the redirection number.
+- 2.37 Release Complete message (RLC):** A message sent in either direction in response to the receipt of a release message, or if appropriate to a reset circuit message, when the circuit concerned has been brought into the idle condition.
+- 2.38 Reset Circuit message (RSC):** A message sent to release a circuit when, due to memory mutilation or other causes, it is unknown whether for example, a release or a release complete message is appropriate. If, at the receiving end, the circuit is remotely blocked, reception of this message should cause that condition to be removed.
+- 2.39 Resume message (RES):** A message sent in either direction indicating that the calling or called party, after having been suspended, is reconnected.
+- 2.40 Segmentation Message (SGM):** A message sent in either direction to convey an additional segment of an overlength message.
+- 2.41 Subsequent Directory Number message (SDM):** A message that may be sent in the forward direction following an Initial Address Message, to convey additional called party number information, when the called party number in the Initial Address Message was contained in the Called Directory Number parameter.
+- 2.42 Subsequent Address Message (SAM):** A message that may be sent in the forward direction following an initial address message, to convey additional called party number information.
+- 2.43 Suspend message (SUS):** A message sent in either direction indicating that the calling or called party has been temporarily disconnected.
+- 2.44 Unblocking message (UBL):** A message sent to the exchange at the other end of a circuit to cancel, in that exchange, the engaged condition of the circuit caused by a previously sent blocking or circuit group blocking message.
+- 2.45 Unblocking Acknowledgement Message (UBA):** A message sent in response to an unblocking message indicating that the circuit has been unblocked.
+
+**2.46 Unequipped Circuit Identification Code message (UCIC):** A message sent from one exchange to another when it receives an unequipped circuit identification code.
+
+**2.47 User Part Available message (UPA):** A message sent in either direction as a response to a user part test message, to indicate that the user part is available.
+
+**2.48 User Part Test message (UPT):** A message sent in either direction to test the status of a user part marked as unavailable for a signalling point.
+
+**2.49 User-to-user information message (USR):** A message to be used for the transport of user-to-user signalling independent of call control messages.
+
+# **3 Signalling parameters**
+
+**3.1 access delivery information:** Information sent in the backward direction indicating that a SETUP message was generated at the destination access.
+
+**3.2 access transport:** Information generated on the access side of a call and transferred transparently in either direction between originating and terminating local exchanges. The information is significant to both users and local exchanges.
+
+**3.3 application transport parameter (APP):** Information sent in either direction to allow the peer-to-peer communication of Application Transport mechanism user applications.
+
+**3.4 automatic congestion level:** Information sent to the exchange at the other end of a circuit to indicate that a particular level of congestion exists at the sending exchange.
+
+**3.5 backward call indicators:** Information relating to the characteristics of the connection, signalling path and called party sent in the backward direction.
+
+**3.6 backward GVNS:** Information sent in the backward direction used for a GVNS call to convey GVNS related information.
+
+**3.7 call diversion information:** Information sent in the backward direction indicating the redirecting reason and the notification subscription option of the redirecting user.
+
+**3.8 call diversion treatment indicators:** Information sent in the forward direction concerning treatment of call diversion.
+
+**3.9 call history information:** Information sent in the backward direction to indicate the accumulated propagation delay of a connection.
+
+**3.10 call offering treatment indicators:** Information sent in the forward direction concerning treatment of call offering.
+
+**3.11 call reference:** Circuit independent information identifying a particular call.
+
+**3.12 call transfer number:** Information sent in both directions to identify each of the users involved in a call transfer.
+
+**3.13 call transfer reference:** Information used to convey a reference number associated with the ECT supplementary service.
+
+**3.14 called directory number:** Information to indicate the directory number. The directory number is a number in the national numbering scheme that is allocated to a customer for a telephony service.
+
+**3.15 called IN number:** Information indicating the number which was received in the SSP as called party number in IAM and SAM messages.
+
+**3.16 called party number:** Information to identify the called party.
+
+**3.17 calling geodetic location:** Information that indicates the geodetic location of the calling party. The reference system for the coding is the World Geodetic System 1984, (WGS-84). The origin of the WGS-84 coordinate system is the geometric centre of the WGS-84 ellipsoid. The ellipsoid is constructed by the rotation of an ellipse around the minor axis that is oriented in the north-south direction. The rotation axis is the polar axis of the ellipsoid, and the plane orthogonal to it and including the centre of symmetry is the equatorial plane.
+
+The relevant dimensions are as follows:
+
+Major Axis (a) = 6 378 137 m
+
+Minor Axis (b) = 6 356 752.314 m
+
+Coordinates are then expressed in terms of longitude and latitude relevant to this ellipsoid. The range of longitude is $-180^\circ$ to $+180^\circ$ , and the range of latitude is $-90^\circ$ to $+90^\circ$ . $0^\circ$ longitude corresponds to the Greenwich Meridian, and positive angles are to the East, while negative angles are to the West. $0^\circ$ latitude corresponds to the equator, and positive angles are to the North, while negative angles are to the South. Altitudes are defined as the distance between the ellipsoid and the point, along a line orthogonal to the ellipsoid.
+
+**3.18 calling party number:** Information sent in the forward direction to identify the calling party.
+
+**3.19 calling party's category:** Information sent in the forward direction indicating the category of the calling party and, in case of semi-automatic calls, the service language to be spoken by the incoming, delay and assistance operators.
+
+**3.20 cause indicators:** Information sent in either direction indicating the reason for sending the message (e.g. release message).
+
+**3.21 CCNR possible indicator:** Information sent in ACM (subscriber free)/CPG (alerting) to indicate the possibility to invoke a possible succeeding CCNR service request.
+
+**3.22 CCSS:** Information sent in an initial address message indicating that a call is a CCBS or a CCNR call as defined in the CCBS or CCNR supplementary service.
+
+**3.23 charged party identification:** Information identifying the charged party, e.g. the account number.
+
+**3.24 circuit assignment map:** Information sent in the forward direction to identify the circuits used for an $N \times 64$ kbit/s connection.
+
+**3.25 circuit group supervision message type:** Information sent in a circuit group blocking or unblocking message, indicating whether blocking (unblocking) is maintenance oriented or hardware oriented.
+
+**3.26 circuit state indicator:** Information indicating the state of a circuit according to the sending exchange.
+
+**3.27 closed user group interlock code:** Information uniquely identifying a closed user group within a network.
+
+**3.28 collect call request:** Information sent in the forward direction indicating whether or not a call is a collect call.
+
+**3.29 conference treatment indicators:** Information sent in both directions concerning treatment of a multi-party call.
+
+**3.30 connected number:** Information sent in the backward direction to identify the connected party.
+
+**3.31 connection request:** Information sent in the forward direction on behalf of the signalling connection control part requesting the establishment of an end-to-end connection.
+
+**3.32 continuity indicators:** Information sent in the forward direction indicating whether or not the continuity check on the outgoing circuit was successful. A continuity check successful indication also implies continuity of the preceding circuits and successful verification of the path across the exchange with the specified degree of reliability.
+
+**3.33 correlation id:** Information used by the SCF for correlation with a previous connection (see ITU-T Recommendations Q.1218 [5] and Q.1228 [6] – Definition of common data types).
+
+**3.34 display information:** Information sent in either direction indicating a text string to be sent to the user.
+
+**3.35 echo control information:** Indicators used to request activation and deactivation of echo control devices, and to respond to such requests.
+
+**3.36 end of optional parameters:** The end of optional parameters field indicates that there are no more optional parameters in the message.
+
+**3.37 event information:** Information indicating the type of event which caused a call progress message to be sent.
+
+**3.38 facility indicator:** Information sent in facility related messages identifying the facility or facilities with which the message is concerned.
+
+**3.39 forward call indicators:** Information relating to the characteristics of the connection, signalling path and calling party sent in the forward direction.
+
+**3.40 forward GVNS:** Information sent in the forward direction used for a GVNS call to convey GVNS related information.
+
+**3.41 generic digits:** Digit information, which is not suitable to be sent within numbering address parameter, sent in either direction to convey information between exchanges due to supplementary service.
+
+**3.42 generic notification:** Information sent in either direction intended to provide supplementary service notification to a user.
+
+**3.43 generic number:** Number information sent in either direction to enhance network operation or for supplementary services.
+
+**3.44 generic reference:** (not used in the 1997 and subsequent versions of the ISUP Recommendations).
+
+**3.45 hop counter:** Information sent in the forward direction to minimize the impact of looping. The initial count determines the maximum number of contiguous ISUP interexchange circuits that are allowed to complete the call, assuming all subsequent intermediate exchanges decrement the hop counter.
+
+**3.46 HTR information:** Information identifying a Hard to Reach destination (see E.412 [7]).
+
+**3.47 information indicators:** Information identifying the optional parameters included in a message.
+
+**3.48 information request indicators:** Information identifying the optional parameters requested in a message.
+
+**3.49 location number:** Information sent to identify the geographical area (e.g. region, country, city, etc.) of the origin of a call. It is primarily intended to provide services for mobile originated calls.
+
+- 3.50 loop prevention indicators:** Information sent in association with a request (or response to a request) when the loop prevention procedure is performed in the ECT supplementary service.
+- 3.51 MCID request indicator:** Information sent in the backward direction to request the identity of the calling party for the purpose of malicious call identification.
+- 3.52 MCID response indicator:** Information sent in the forward direction to respond to a MCID request and indicating whether or not the MCID information is available.
+- 3.53 message compatibility information:** Information sent in either direction indicating how an exchange should react in case this message is unrecognised.
+- 3.54 MLPP precedence:** Information relating specifically to the multilevel precedence and pre-emption service.
+- 3.55 nature of connection indicators:** Information relating to the transmission path used on a connection.
+- 3.56 network management controls:** Information sent in the forward direction concerning network management related action for a call.
+- 3.57 network routeing number:** Information to indicate the network routeing number. The network routeing number is a number used by the network to route a call.
+- 3.58 network specific facility:** Service related information transparently transferred in either direction between the local exchange and the identified network which contracts the service. The information is significant to both user and the identified network.
+- 3.59 number portability forward information:** Information sent in the forward direction concerning treatment of number portability.
+- 3.60 optional backward call indicators:** Information relating to the characteristics of the connection, signalling path and called party sent in the backward direction.
+- 3.61 optional forward call indicators:** Information relating to the characteristics of the connection, signalling path and called party sent in the forward direction.
+- 3.62 original called number:** Information sent in the forward direction when a call is redirected and identifies the original called party.
+- 3.63 original called IN number:** Information sent in the forward direction indicating the original called IN number, if multiple IN interactions have taken place.
+- 3.64 origination ISC point code:** Information sent in the initial address message of an international call, indicating the point code of the originating ISC.
+- 3.65 parameter compatibility information:** Information sent in either direction indicating how an exchange should react in case the parameter is unrecognised.
+- 3.66 pivot capability:** General information about allowed operation of pivot routeing.
+- 3.67 pivot counter:** Information indicating the number of pivot attempts (successful and unsuccessful) that a call has undergone.
+- 3.68 pivot routeing backward information:** Information sent in the backward direction in support of pivot routeing.
+- 3.69 pivot routeing forward information:** Information sent in the forward direction in support of pivot routeing.
+- 3.70 pivot routeing indicators:** Information used in the FAC message to indicate the pivot routeing action to be performed at the next (failure action) or previous (request action or cancel action) exchange.
+
+**3.71 pivot status:** Information used to inform exchanges regarding the possibility that an offer to pivot route will be accepted later.
+
+**3.72 propagation delay counter:** Information sent in forward direction to indicate the propagation delay of a connection. This information is accumulated whilst the parameter is transferred through the network. The propagation delay information is represented by a counter counting in integer multiples of 1 ms.
+
+**3.73 QoR capability:** Information sent in the forward direction to indicate that at least one exchange in the connection is able to perform the query to the database as described in the QoR procedures.
+
+**3.74 range and status:** Information sent in a circuit group supervision message (e.g. circuit group blocking) to indicate the range and status of circuits affected by the action in the message.
+
+**3.75 redirect backward information:** Information sent in the backward direction in support of redirection.
+
+**3.76 redirect capability:** Information sent in the forward direction to indicate that at least one exchange in the connection is able to redirect the call and the call states in which the procedure is possible.
+
+**3.77 redirect counter:** Information indicating the number of invocations of redirection that a call has undergone.
+
+**3.78 redirect forward information:** Information sent in the forward direction in support of redirection.
+
+**3.79 redirect status:** Information used to inform exchanges regarding the possibility that an offer to redirect will be accepted later.
+
+**3.80 redirecting number:** Information sent in the forward direction when a call is diverted, indicating the number from which the call was diverted.
+
+**3.81 redirection information:** Information sent in either direction giving information about call redirection or call rerouteing.
+
+**3.82 redirection number:** Information sent in the backward direction indicating the number towards which the call must be redirected or has been forwarded.
+
+**3.83 redirection number restriction:** Information sent in the backward direction indicating whether the diverted-to user allows the presentation of his number.
+
+**3.84 remote operations:** The Remote Operations parameter is used to indicate the invocation of a supplementary service identified by an operation value and also carry the result or error indications depending on the outcome of the operation.
+
+**3.85 SCF id:** Information indicating the SCF identifier (see ITU-T Recommendations Q.1218 [5] and Q.1228 [6] – Definition of common data types).
+
+**3.86 service activation:** Information sent in either direction to indicate the invocation, acceptance or rejection of supplementary services, when no service associated parameter is to be sent.
+
+**3.87 signalling point code:** Information sent to identify the signalling point in which an event occurred.
+
+**3.88 subsequent number:** Additional called party address digits sent subsequent to the sending of the called party number parameter.
+
+**3.89 suspend/resume indicators:** Information sent in the suspend and resume messages to indicate whether suspend/resume was initiated by an ISDN subscriber or by the network.
+
+- 3.90 transit network selection:** Information sent in the initial address message indicating the transit network requested to be used in the call.
+- 3.91 transmission medium requirement:** Information sent in the forward direction indicating the type of transmission medium required for the connection (e.g. 64 kbit/s unrestricted, speech).
+- 3.92 transmission medium requirement prime:** Information sent in the forward direction indicating the fallback connection type in case of fallback.
+- 3.93 transmission medium used:** Information sent in the backward direction indicating a resulting fallback connection type used for a call after fallback has occurred.
+- 3.94 UID action indicators:** Information sent in the backward direction to instruct preceding exchanges to enable a user interactive dialogue to occur.
+- 3.95 UID capability indicators:** Information sent in the forward direction to inform succeeding exchanges that on request a user interactive dialogue is possible.
+- 3.96 user service information:** Information sent in the forward direction indicating the bearer capability requested by the calling party.
+- 3.97 user service information prime:** Information sent in the forward direction indicating the additional bearer capability requested by the calling party.
+- 3.98 user teleservice information:** Information sent in the initial address message indicating the Higher Layer Compatibility information requested by the calling party.
+- 3.99 user-to-user indicators:** Information sent in association with a request (or response to a request) for user-to-user signalling supplementary service(s).
+- 3.100 user-to-user information:** Information generated by a user and transferred transparently through the interexchange network between the originating and terminating local exchanges.
+
+# **4 Parameter information**
+
+- 4.1 access delivery indicator:** Information sent in the backward direction indicating that a SETUP message was generated at the destination access.
+- 4.2 address presentation restricted indicator:** Information sent in either direction to indicate that the address information is not to be presented to a public network user, but can be passed to another public network. It may also be used to indicate that the address cannot be ascertained.
+- 4.3 address signal:** An element of information in a network number. The address signal may indicate digit values 0 to 9, code 11 or code 12. One address Signal Value (ST) is reserved to indicate the end of the called party number.
+- 4.4 altitude:** Information that indicates the geodetic location of the calling party in terms of distance above or below the WGS-84 ellipsoid surface.
+- 4.5 altitude sign:** Information that indicates the geodetic location of the calling party in terms of above or below the WGS-84 ellipsoid surface.
+- 4.6 altitude uncertainty code:** Information indicating the level of uncertainty inherent to the associated altitude information.
+- 4.7 APM Segmentation indicator:** Information sent in either direction to indicate the number of remaining segments carrying information using the APM mechanism that will be forwarded.
+- 4.8 application context identifier:** A value that uniquely identifies the application using the application transport mechanism.
+
+**4.9 application transport instruction indicators (ATII):** Information sent in either direction indicating how an exchange should react in case the indicated application using the application transport mechanism is not supported.
+
+**4.10 binary code:** A code allocated to a closed user group administered by a particular ISDN or data network.
+
+**4.11 call diversion may occur indicator:** Information sent in the backward direction indicating that call diversion may occur, depending on the response received (or lack thereof) from the called party.
+
+**4.12 call identity:** Information sent in the call reference parameter indicating the identity of a call in a signalling point.
+
+**4.13 call to be diverted indicator:** Information sent in the forward direction indicating whether diverting of the call shall be accepted.
+
+**4.14 call to be offered indicator:** Information sent in the forward direction indicating whether the call shall be offered if the access is marked with call offering restrictions.
+
+**4.15 called party's category indicator:** Information sent in the backward direction indicating the category of the called party, e.g. ordinary subscriber or payphone.
+
+**4.16 called party's status indicator:** Information sent in the backward direction indicating the status of the called party, e.g. subscriber free.
+
+**4.17 calling party address request indicator:** Information sent in the backward direction indicating a request for the calling party address to be returned.
+
+**4.18 calling party address response indicator:** Information sent in response to a request for the calling party address, indicating whether the requested address is included, not included, not available or incomplete.
+
+**4.19 calling party's category request indicator:** Information sent in the backward direction indicating a request for the calling party's category to be returned.
+
+**4.20 calling party's category response indicator:** Information sent in response to a request for the calling party's category, indicating whether or not the requested information is included in the response.
+
+**4.21 cause value:** Information sent in either direction indicating the reason for sending the message (e.g. release message). Definitions for each cause value are defined in ITU-T Recommendation Q.850 [8].
+
+**4.22 CCSS call indicator:** Information sent in the forward direction, used in a CCBS or CCNR call setup, to distinguish this call from an ordinary call, at the destination local exchange.
+
+**4.23 CCNR possible indicator:** Indicator used in the CCNR Possible Indicator parameter in the ACM (subscriber free)/CPG (alerting) to indicate the possibility to invoke a possible succeeding CCNR service request.
+
+**4.24 charge indicator:** Information sent in the backward direction indicating whether or not the call is chargeable.
+
+**4.25 charge information request indicator:** Information sent in either direction requesting charge information to be returned.
+
+**4.26 charge information response indicator:** Information sent in response to a request for charge information indicating whether or not the requested information is included.
+
+**4.27 circuit identification code:** Information identifying the physical path between a pair of exchanges.
+
+**4.28 closed user group call indicator:** Information indicating whether or not the concerned call can be set up as a closed user group call and, if a closed user group call, whether or not outgoing access is allowed.
+
+**4.29 coding standard:** Information sent in association with a parameter (e.g. cause indicators) identifying the standard in which the parameter format is described.
+
+**4.30 component ID tag:** Information identifying the type of component ID used in remote operations.
+
+**4.31 component type:** There are four types of components that may be present in the Remote Operations parameter. The four Protocol Data Units (PDU) defined in ITU-T Recommendation X.229 [9] are used, viz.:
+
+| Component | X.229 PDU |
+|---------------|-----------|
+| Invoke | ROIV |
+| Return Result | RORS |
+| Return Error | ROER |
+| Reject | RORJ |
+
+These component types are defined as follows:
+
+a) *Invoke*
+
+The Invoke component requests that an operation be performed. It may be linked to another operation invocation previously sent by the other end. In this case it is known as a "Linked Invoke".
+
+b) *Return Result*
+
+The Return Result component reports successful completion of an operation.
+
+c) *Return Error*
+
+The Return Error component reports that an operation has not been successfully completed.
+
+d) *Reject*
+
+The Reject component reports the receipt and rejection of an incorrect component other than a Reject component. The possible causes for rejecting a component are defined by the Problem Code element.
+
+**4.32 component type tag:** Information identifying the type of component used in remote operations.
+
+**4.33 confidence:** Information identifying the confidence by which it is known that the calling party lies within the associated shape description.
+
+**4.34 conference acceptance indicator:** Information sent in both directions indicating whether a request for a multi-party call, i.e. conference or three-party call, shall be accepted.
+
+**4.35 connected line identity request indicator:** Information sent in the forward direction indicating a request for the connected party number to be returned.
+
+**4.36 continuity check indicator:** Information sent in the forward direction indicating whether or not a continuity check will be performed on the circuit(s) concerned or is being (has been) performed on a previous circuit in the connection.
+
+**4.37 credit:** Information sent in a connection request, indicating the window size requested by the signalling connection control part for an end-to-end connection.
+
+**4.38 degrees of latitude:** Information that indicates the geodetic location of the calling party in terms of degrees of latitude north or south of the equator.
+
+**4.39 degrees of longitude:** Information that indicates the geodetic location of the calling party in terms of degrees of longitude east or west of the Greenwich Meridian.
+
+**4.40 diagnostic:** Information sent in association with a cause and which provides supplementary information about the reason for sending the message.
+
+**4.41 discard message indicator:** Information sent to inform another node to discard the related message, due to compatibility reasons.
+
+**4.42 discard parameter indicator:** Information sent to inform another node to discard the related parameter, due to compatibility reasons.
+
+**4.43 echo control device indicator:** Information indicating whether or not an echo control device is included in the connection.
+
+**4.44 ellipse on the ellipsoid shape description:** Information that describes the set of points on the ellipsoid that lie within the defining ellipse. The ellipse is characterized by the coordinates of an ellipsoid point (the origin), the major and minor radii of the ellipse $r_{\text{major}}$ and $r_{\text{minor}}$ , and the orientation of the ellipse $\theta$ which describes the angle between the major radius of the ellipse and North, as shown in Figure 1.
+
+Similar to the ellipsoid point, this shape description can be used to indicate points on the Earth's surface, or near the surface.
+
+
+
+T11103460-99
+
+Figure 1: Description of an ellipse on the ellipsoid. The diagram shows a tilted ellipse. A vertical dashed line with an arrow pointing up represents North. An angle θ is shown between the North line and the major axis of the ellipse. The major radius is labeled r\_major and the minor radius is labeled r\_minor. The origin point is at the center of the ellipse where the axes intersect.
+
+**Figure 1/Q.762 – Description of an ellipse on the ellipsoid**
+
+**4.45 ellipsoid circle sector shape description:** Information that describes the set of points on the ellipsoid that lie within the defining circle sector. The circle sector is characterized by the coordinates of an ellipsoid point (the origin), the radius of the circle sector $r$ , being the geodesic distance over the surface of the ellipsoid, the offset angle ( $\theta$ ) between the first defining radius of the sector and North, and the included angle ( $\beta$ ) being the angle between the first and second defining radius, as shown in Figure 2.
+
+
+
+T11103470-99
+
+Figure 2: Description of a circle sector. The diagram shows a sector of a circle originating from a point. A vertical dashed line represents North. The angle between North and the first radius is θ. The angle between the first and second radius is β. The length of the radii is labeled r.
+
+**Figure 2/Q.762 – Description of a circle sector**
+
+**4.46 ellipsoid point shape description:** Information that describes a point on the surface of the WGS-84 ellipsoid that consists of latitude and longitude. In practice, such a description can be used to refer to a point on Earth's surface, or close to Earth's surface, with the same longitude and latitude. Figure 3 illustrates a point on the surface of the ellipsoid and its coordinates.
+
+
+
+A 3D wireframe representation of an ellipsoid. A vertical central axis and a horizontal equatorial plane are shown. A meridian arc passes through a point on the surface. Two angles are labeled: 'Longitude' is the angle in the equatorial plane between a reference meridian and the point's meridian; 'Latitude' is the angle between the equatorial plane and a line from the center to the point on the surface.
+
+Figure 3: Description of an ellipsoid point as two coordinates.
+
+T11103480-99
+
+**Figure 3/Q.762 – Description of an ellipsoid point as two coordinates**
+
+The latitude is the angle between the equatorial plane and the perpendicular to the plane tangent to the ellipsoid surface at the point. Positive latitudes correspond to the North hemisphere. The longitude is the angle between the half-plane determined by the Greenwich meridian and the half-plane defined by the point and the polar axis, measured Eastward.
+
+**4.47 ellipsoid point with uncertainty shape description:** Information that describes a point that is characterized by the coordinates of an ellipsoid point (the origin) and a distance $r$ . It describes the set of points on the ellipsoid which are at a distance from the origin less than or equal to $r$ , the distance being the geodesic distance over the ellipsoid, i.e. the minimum length of a path staying on the ellipsoid and joining the two points, as shown in Figure 4. Similar to the ellipsoid point, this can be used to indicate points on the Earth's surface, or near the Earth's surface, of same latitude and longitude. The typical use of this shape is to indicate a point when its position is known only with a limited accuracy.
+
+
+
+A circle filled with diagonal hatching lines. A central black dot represents the origin point. A line segment labeled ' $r$ ' extends from the center to the boundary of the circle, indicating the radius of uncertainty.
+
+Figure 4: Description of uncertainty.
+
+T11103490-99
+
+**Figure 4/Q.762 – Description of uncertainty**
+
+**4.48 encapsulated application information:** Application information required to be transported by the application transport mechanism.
+
+- 4.49 encoding scheme:** Information sent to indicate the coding type for the digit information, e.g. BCD-coded.
+- 4.50 end-to-end information indicator:** Information sent in either direction indicating whether or not the sending exchange has further call information available for end-to-end transmission. In the forward direction, an indication that end-to-end information is available will imply that the destination exchange may obtain the information before alerting the called party.
+- 4.51 end-to-end method indicator:** Information sent in either direction indicating the available methods, if any, for end-to-end transfer of information.
+- 4.52 error code:** The Error code element contains the reason why an operation cannot be completed successfully. It is present only in a Return Error component. As with operations, errors may be local or global. These errors and associated parameters are defined in relevant supplementary service specifications.
+- 4.53 event indicator:** Information indicating the type of event which caused a call progress message to be sent.
+- 4.54 event presentation restricted indicator:** Information sent in the backward direction indicating that the event should not be presented to the calling party.
+- 4.55 extension indicator:** Information sent in every octet in a multi-octet parameter field with variable length, indicating whether the octet is the last one or is followed by another one.
+- 4.56 GVNS user group identification:** Information sent in the forward direction that uniquely identifies the GVNS customer.
+- 4.57 feature code:** Information sent in either direction to invoke, accept, or reject a specific action for a supplementary service.
+- 4.58 filler:** A number of bits used to complete a partially used octet to full octet length. Mainly the filler is used in number parameters that are carrying odd number of digits, where the remaining four bits in the last octet have no digit information.
+- 4.59 holding indicator:** Information sent in the backward direction indicating that holding of the connection is requested.
+- 4.60 hold provided indicator:** Information sent in the forward direction indicating that the connection will be held after the calling or called party has attempted to release.
+- 4.61 in-band information indicator:** Information sent in the backward direction indicating that in-band information or an appropriate pattern is now available.
+- 4.62 included angle:** Information identifying the included angle of a circle sector.
+- 4.63 incoming echo control device request indicator:** Information sent to request the activation or deactivation of an incoming echo control device.
+- 4.64 incoming echo control device information indicator:** Information sent to inform whether an incoming echo control device has been included or not and, if not, whether the device is available or not.
+- 4.65 instruction indicator:** Information indicating the reactions to be taken if an unrecognized message or unrecognized parameter is received.
+- 4.66 internal network number:** Information sent to the destination exchange for specific numbers, e.g. roaming numbers indicating whether or not the number contained in the parameter is generated by the network.
+- 4.67 interworking indicator:** Information sent in either direction indicating whether or not Signalling System No. 7 is used in all parts of the network connection.
+
+- 4.68 interworking to redirection indicator:** Information used to indicate whether interworking from pivot routing to redirection is allowed.
+- 4.69 invoke ID:** An Invoke ID is used as a reference number to identify uniquely an operation invocation. It is present in the Invoke component and in any reply to the Invoke (Return Result, Return Error or Reject), enabling the reply to be correlated with the invoke.
+- 4.70 invoking pivot reason:** Information sent in the pivot routing backward information parameter or the pivot routing forward information parameter that conveys the reason for invoking the pivot function.
+- 4.71 invoking redirect reason:** Information sent in the redirect backward information parameter or the redirect forward information parameter that conveys the reason for invoking the redirection function.
+- 4.72 ISDN access indicator:** Information sent in either direction indicating whether or not the access signalling protocol is ISDN.
+- 4.73 ISDN user part indicator:** Information sent in either direction to indicate that the ISDN user part is used in all preceding parts of the network connection. When sent in the backward direction, the preceding parts are those towards the called party.
+- 4.74 ISDN user part preference indicator:** Information sent in the forward direction indicating whether or not the ISDN user part is required or preferred in all parts of the network connection.
+- 4.75 length (of each component or of an information element):** Binary coded information indicating the number of octets in a component or information element. The value does not include the parameter name, length or end of optional parameters octets.
+- 4.76 linked ID:** A Linked ID is included in an Invoke component by a node when it responds to an operation invocation with a linked operation invocation. The node receiving the Linked ID uses it for correlation purposes in the same way that it uses the Invoke ID in Return Result, Return Error and Reject components.
+- 4.77 local reference:** Information sent in the connection request, indicating the local reference allocated by the signalling connection control part to an end-to-end connection.
+- 4.78 latitude sign:** Information that indicates the geodetic location of the calling party in terms of northern or southern Hemisphere.
+- 4.79 location:** Information sent in either direction indicating where an event (e.g. release) was generated. Definition of each location value is given in ITU-T Recommendation Q.850 [8].
+- 4.80 location presentation restricted indicator:** Information that indicates that the geodetic location information is not to be presented to a public network user, but can be passed to another public network. It may also be used to indicate that the geodetic location cannot be ascertained.
+- 4.81 Look For Busy (LFB):** Information sent in the forward direction to indicate whether the LFB option is allowed or if the path for the call is reserved.
+- 4.82 major radius:** Information identifying the size of the major axis of an ellipse on the ellipsoid shape description.
+- 4.83 minor radius:** Information identifying the size of the minor axis of an ellipse on the ellipsoid shape description.
+- 4.84 MLPP service domain:** Information sent in the forward direction to identify the specific MLPP service domain subscribed to by the calling user.
+- 4.85 MLPP user indicator:** Information sent in the backward direction to indicate that the called user is an MLPP user.
+
+**4.86 more instruction indicators:** Octets reserved for future use for enhancement of the instruction indicators.
+
+**4.87 national/international call indicator:** Information sent in the forward direction indicating in the destination national network whether the call has to be treated as an international call or as a national call.
+
+**4.88 nature of address indicator:** Information sent in association with an address indicating the nature of that address, e.g. ISDN international number, ISDN national significant number, or ISDN subscriber number.
+
+**4.89 network discard indicator:** This indicator indicates that user-to-user information included in the call control message has been discarded by the network.
+
+**4.90 network identification plan:** Information sent to indicate the identification plan for identifying the network, e.g. ITU-T Recommendation X.121 [10] or E.212 [11] (DNIC or MNIC).
+
+**4.91 network identification:** Information sent to identify a network.
+
+**4.92 network identity:** Information sent to identify the network which administers the supplementary service.
+
+**4.93 network specific facility indicator:** Information identifying specific facilities requested or provided.
+
+**4.94 notification indicator:** Information sent in either direction intended to provide supplementary service notification to a user.
+
+**4.95 notification subscription option:** Information sent in the backward direction indicating that the diversion with or without redirection number can be presented to the calling user.
+
+**4.96 Nth upgraded parameter name:** Information identifying the Nth parameter which has been upgraded for compatibility purposes.
+
+**4.97 number incomplete indicator:** Information sent to indicate whether the delivered number is complete or incomplete.
+
+**4.98 number portability status indicator:** Information sent in the forward direction identifying whether number portability checks have taken place at an exchange in the call path and also whether the called number is ported or non-ported.
+
+**4.99 number qualifier indicator:** Information sent in association with a generic number, qualifying the number that is transferred, e.g. a network specific number or a number related to a specific supplementary service.
+
+**4.100 numbering plan indicator:** Information sent in association with a number indicating the numbering plan used for that number (e.g. ISDN number, Telex number).
+
+**4.101 odd/even indicator:** Information sent in association with an address, indicating whether the number of address signals contained in the address is even or odd.
+
+**4.102 offset:** Information identifying the offset of a circle sector from North.
+
+**4.103 operation code:** The Operation code element indicates the precise operation to be invoked, and is present in an Invoke component type. It is also present in the Return Result component if the result contains parameters. The operation may be a local operation or a global operation. A local operation can be used in one ASE only. The same global operation can be used in several different ASEs. The actual operation codes, the definition of the operations and their associated parameters, are defined in relevant supplementary service specifications.
+
+**4.104 orientation:** Information identifying the orientation of an ellipse on the ellipsoid.
+
+- 4.105 original redirection reason:** Information sent in either direction indicating the reason why the call was originally redirected.
+- 4.106 originating participating service provider identification:** Information sent in the forward direction that uniquely identifies the participating service provider that provides customer access to GVNS to the calling user/interface.
+- 4.107 outgoing echo control device request indicator:** Information sent to request the activation or deactivation of an outgoing echo control device.
+- 4.108 outgoing echo control device information indicator:** Information sent to inform whether an outgoing echo control device has been included or not and, if not, whether the device is available or not.
+- 4.109 parameter tag:** Information identifying the type of parameter used in remote operations.
+- 4.110 pass on not possible indicator:** Information sent to inform another node on what action to take if "pass on" was requested due to compatibility reason but "pass on" was not possible due to interworking with pre-ISUP 1992 signalling.
+- 4.111 performing pivot indicator:** Information sent in the pivot routing forward information parameter that indicates a willingness to perform the pivot function for a particular reason.
+- 4.112 performing redirect indicator:** Information sent in the redirect forward information parameter that indicates a willingness to perform redirection for a particular reason.
+- 4.113 pivot possible indicator:** Information used to indicate the call state until which the pivot routing is possible.
+- 4.114 point with altitude and uncertainty shape description:** Information that describes a point that is characterized by the coordinates of an ellipsoid point, an uncertainty distance $r$ , an altitude $a$ and an altitude uncertainty $h$ . It describes the set of points which are at a vertical distance $h$ or less from the origin. The origin is a point at altitude $a$ above an ellipsoid point with uncertainty (see 4.47) as shown in Figure 5.
+
+
+
+Figure 5/Q.762 – Description of a point with altitude and uncertainty. The diagram shows a sphere representing an ellipsoid. A point on the sphere is defined by its Latitude and Longitude. A vertical line segment from the center to this point is labeled 'a' (altitude). At this point, a small ellipsoid shape represents the uncertainty region, with a radius labeled 'r' (uncertainty distance). A vertical dashed line segment passing through the point is labeled 'h' (altitude uncertainty). The diagram is labeled T11103500-99.
+
+**Figure 5/Q.762 – Description of a point with altitude and uncertainty**
+
+**4.115 polygon shape description:** Information that describes an arbitrary shape that is described by an ordered series of points (in the example pictured in Figure 6, A to E). The minimum number of points allowed is three, and the maximum number of points allowed is 15. The points shall be connected in the order that they are given. A connecting line is defined as the line over the ellipsoid joining the two points and of minimum distance (geodesic). The last point is connected to the first. The list of points must respect a number of conditions:
+
+- a connecting line shall not cross another connecting line;
+- two successive points must not be diametrically opposed on the ellipsoid.
+
+The described area is situated to the right of the lines with the downward direction being toward the Earth's centre and the forward direction being from a point to the next.
+
+
+
+T11103510-99
+
+Figure 6: A diagram showing a polygon shape defined by five points: A, B, C, D, and E. The points are connected in the order A-B-C-D-E-A. The area enclosed by the polygon is shaded with diagonal lines. The polygon is oriented such that the interior is to the right of the boundary lines when traversed in the order A-B-C-D-E-A. The label 'T11103510-99' is present below the diagram.
+
+**Figure 6/Q.762 – Description of a polygon**
+
+**4.116 precedence level:** Information sent in the forward direction to indicate the priority of the call.
+
+**4.117 problem code:** The Problem code element used in remote operations contains the reason for the rejection of a component and one such element is present in a Reject component. Four problem code elements are defined, viz.:
+
+### a) *General Problem*
+
+This element contains one of the problem codes which apply to the Remote Operation capability of ISUP in general and which do not relate to any specific component type. All of these are generated by the Remote Operation capability of ISUP. They are:
+
+- Unrecognized Component:
+The component type is not recognized as being one of those defined in 4.118 describing component types.
+- Mistyped Component:
+The elemental structure of a component does not conform to the structure of that component as defined in ITU-T Recommendation Q.763 [1].
+- Badly Structured Component:
+The contents of the component do not conform to the encoding rules defined in ITU-T Recommendation Q.763 [1].
+
+### b) *Invoke problem*
+
+This element contains one of the problem codes that relate only to the Invoke component type. They are:
+
+- Duplicate Invoke ID:
+The Invoke ID is already in use by a previously invoked operation.
+
+- Unrecognized operation:
+The operation code value is not one of those used by the ASE.
+- Mistyped Parameter:
+Signifies that the type of invoke parameter is not that agreed between the users.
+- Resource Limitation:
+Sufficient resources are not available to perform the requested operation.
+- Initiating Release:
+The requested operation cannot be invoked because the association is about to be released.
+- Unrecognized Linked ID:
+The Linked ID does not correspond to a previously invoked operation.
+- Linked Response Unexpected:
+The operation referred to by the Linked ID is not an operation for which linked invokes are allowed.
+- Unexpected Linked Operation:
+The operation referred to by the Linked ID does not allow this linked operation.
+
+### c) *Return Result Problem*
+
+This element contains one of the problem codes that relate only to the Return Result component type. They are:
+
+- Unrecognized Invoke ID:
+No operation with the specified Invoke ID is in progress.
+- Return Result Unexpected:
+The invoked operation does not report success.
+- Mistyped Parameter:
+Signifies that the type of Return Result parameter is not that agreed between the users.
+
+### d) *Return Error Problem*
+
+This element contains one of the problem codes that relate only to the Return Error component type. They are:
+
+- Unrecognized Invoke ID:
+No operation with the specified Invoke ID is in progress.
+- Return Error Unexpected:
+The invoked operation does not report failure.
+- Unrecognized Error:
+The reported error is not one of those defined for the invoked operation.
+- Unexpected Error:
+The received error is not one of those that the invoked operation may report.
+- Mistyped Parameter:
+Signifies that the type of Error parameter is not that agreed between the users.
+
+**4.118 protocol class:** Information indicating the protocol class requested by the signalling connection control part for the end-to-end connection.
+
+**4.119 protocol profile:** Information sent in either direction to indicate the protocol used in the Remote Operations parameter.
+
+**4.120 protocol control indicator:** Information consisting of the end-to-end method indicator, the interworking indicator, the end-to-end information indicator, the SCCP method indicator and the ISDN user part indicator sent in either direction to describe the signalling capabilities within the network connection.
+
+**4.121 radius:** Information identifying the size of the radius of the associates circle sector shape description.
+
+**4.122 range:** Information sent in a circuit group supervision message (e.g. circuit group blocking) to indicate the range of circuits affected by the action in the message.
+
+**4.123 redirect possible indicator:** Information sent in the forward direction to indicate that at least one exchange in the connection is able to redirect the call and the call states in which the procedure is possible.
+
+**4.124 redirecting indicator:** Information sent in either direction indicating whether the call has been diverted or rerouted and whether or not presentation of redirection information to the calling party is restricted.
+
+**4.125 redirecting reason:** Information sent in either direction indicating, in the case of calls undergoing redirection, the reason why the call has been redirected.
+
+**4.126 redirection counter:** Information sent in either direction indicating the number of redirections which have occurred on a call.
+
+**4.127 release call indicator:** Information sent to inform another node to release the call or not, by compatibility reasons, if the related message or parameter is unrecognised.
+
+**4.128 return to invoking exchange call identifier:** Information used by the return to invoking exchange function to identify a call.
+
+**4.129 return to invoking exchange duration:** Information sent in the backward direction to indicate how long information will be retained at the invoking exchange to facilitate the return to invoking exchange function.
+
+**4.130 return to invoking exchange possible:** Information sent in the forward direction to indicate the capability to make use of the return to invoking exchange call identifier and return to invoking exchange duration.
+
+**4.131 routeing label:** Information provided to the message transfer part for the purpose of message routeing (see 2.2/Q.704 [12]).
+
+**4.132 satellite indicator:** Information sent in the forward direction indicating the number of satellite circuits in the connection.
+
+**4.133 SCCP method indicator:** Information sent in either direction indicating the available SCCP methods, if any, for end-to-end transfer of information.
+
+**4.134 screening indicator:** Information sent in either direction to indicate whether the address/location information was provided by the user or network.
+
+**4.135 segmentation local reference (SLR):** A unique value to a call used to associate segments in an APM segmentation procedure.
+
+**4.136 send notification indicator:** Information sent to inform another node to send notification, due to compatibility reason, if the related message or parameter is unrecognised.
+
+**4.137 sequence:** The sequence is an ordered set used in remote operations.
+
+**4.138 sequence indicator:** Used to indicate the beginning (first segment) of an APM segmentation procedure sequence.
+
+**4.139 set:** The Set element is used in remote operations to contain a set of information elements accompanying a component. It is required in the case of more than one information elements being included in a component. The information elements themselves are defined in relevant supplementary service specifications.
+
+**4.140 shape description:** Information that describes the geodetic location of the calling party.
+
+**4.141 signalling point code:** Information identifying the signalling point.
+
+**4.142 simple segmentation indicator:** Information sent in either direction to indicate that additional information will be forwarded in a segmentation message (unsolicited).
+
+**4.143 solicited information indicator:** Information sent in an information message to indicate whether or not the message is a response to an information request message.
+
+**4.144 status:** Information sent in a circuit group supervision message (e.g. circuit group blocking) to indicate the specific circuits, within the range of circuits stated in the message, that are affected by the action specified in the message.
+
+**4.145 T9 timer indicator:** Information sent in the forward direction to inform succeeding exchanges that on request stopping of the timer T9 is possible.
+
+**4.146 T9 timer instruction indicator:** Information sent in the backward direction to instruct preceding exchanges to stop or not to start, respectively, the timer T9.
+
+**4.147 temporary alternative routeing indicator:** Information sent in the forward direction indicating that a call is a temporary alternative routeing controlled call.
+
+**4.148 terminating access indicator:** Information sent in the backward direction that identifies the type of terminating access from a GVNS terminating participating service provider actually used to complete the call.
+
+**4.149 terminating network routeing number:** A number sent in the forward direction which a terminating functional entity may use to complete a GVNS call to on-net locations.
+
+**4.150 through connection indicator:** Information sent in the forward direction to inform succeeding exchanges that on request through-connection of the transmission path in both directions is possible.
+
+**4.151 through connection instruction indicator:** Information sent in the backward direction to instruct preceding exchanges to through-connect the transmission path in both directions.
+
+**4.152 transit at intermediate exchange indicator:** Information sent to inform a transit node (type B), whether it shall react on the rest of the instruction indicators or not, if the related message or parameter is unrecognised.
+
+**4.153 type:** Information sent in either direction to indicate whether the message is a request or a response.
+
+**4.154 type of digits:** Information sent in association with a generic digit to indicate the type of digit, e.g. authorization code.
+
+**4.155 type of network identification:** Information sent to inform whether the identification of a network is by ITU-T standardization identification or by national network identification.
+
+**4.156 type of shape:** Information that indicates the format of the geodetic location information held in the associated shape description.
+
+**4.157 uncertainty code:** Information that indicates the level of uncertainty inherent to the associated longitude/latitude information.
+
+## **SERIES OF ITU-T RECOMMENDATIONS**
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure and Internet protocol aspects |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fac0e3af9b9be1feda384e887b7d39af0a2b4343
--- /dev/null
+++ b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:26d34537c63c29a44c8c988a42a1b7f8656d653d64c6094c749ab19a9cb30380
+size 20738
diff --git a/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a7da83ecb82b51a4cef7694858eef2c35f1986ff
--- /dev/null
+++ b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d77a478c5b78d330a2a6abbd32e7d0ac053d8b9c1ffe8a96476214afa6ddf7ae
+size 8196
diff --git a/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f754f7a9dec4217be56ed031e6ea469d72d3279f
--- /dev/null
+++ b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3ed9bfeab3ab82d1e40e70d323ff497f2def8e0e535363705342ad02ec3f8bb5
+size 27189
diff --git a/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a43c8ff879431f55bce64bc755d820f0d1d23ce8
--- /dev/null
+++ b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:617087b24e8660d2c35de070359dd5b6a4629e8e8800adb7186b9523254973f9
+size 100266
diff --git a/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..85b3155240043047279a88a397c0c7b71b372192
--- /dev/null
+++ b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a36f23ad925273016424a5aef3d1de267ffb6eb6365ecfda258db07b030a53b4
+size 131374
diff --git a/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6048056a63eaf375f2ab99b699097cb7a2321dbf
--- /dev/null
+++ b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:21d1bd9d33b86eacf9ef9f3431c7b7ae60a88f4b77b027b7f2ce01461f9bd8a9
+size 23767
diff --git a/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..356a5b43465bf0c6aceae8c87b96599349589c43
--- /dev/null
+++ b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b4914c60dcf50ca168a41240610f9797774fd177ae9c84f87b50e84f30ed0a3b
+size 61009
diff --git a/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/80ec3bf791fd8eb41f73a420c2122529_img.jpg b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/80ec3bf791fd8eb41f73a420c2122529_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..615a4b4e45661a1d756e8ce7cf5e0ad728d0065b
--- /dev/null
+++ b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/80ec3bf791fd8eb41f73a420c2122529_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:048f47d391c363b3a01cbde52224242af93e2b9e8c733bb38082daacdf2929f6
+size 19433
diff --git a/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/9a047c6501a487b3f18cfff971bcb33f_img.jpg b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/9a047c6501a487b3f18cfff971bcb33f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..91e81fd964f6b24be97e8cb1fde820ec55e4fb29
--- /dev/null
+++ b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/9a047c6501a487b3f18cfff971bcb33f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1737bac67114c9c763cf9320171f473b7f8c8c6bd123a4fa45fa7aea93ef9f3f
+size 26086
diff --git a/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b8c4e0e19d357592bd737095a4495ca667ab9499
--- /dev/null
+++ b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8fcc5694624deb596bc63ac61256ca160d2f54e10af3a053667a664d2501937d
+size 27185
diff --git a/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..da43e626ab6f364c2616cee745fbbe1a434f29df
--- /dev/null
+++ b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d2f66aa68ecdc7ba0153b5b7cb28d7f4761742006ab121f7d68b19b4c6303f1f
+size 20040
diff --git a/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2dbb75f531690bbf1983d2bd8776d6f925650d43
--- /dev/null
+++ b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1fabfec2bb9e13cfb0070935f8d0b0caaf33fad23aeb525682cf2d72f47e212e
+size 39156
diff --git a/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..def240ea5db7470dcd8d7c120735049d2c42685d
--- /dev/null
+++ b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7e7b759859602c029414fb3794f24db4ffc82ddfb78ed46a29f7ef5dbcb489f5
+size 24406
diff --git a/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8684511d37d53c9b520b63fa634bf1bcc57b3d3b
--- /dev/null
+++ b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c9a5e9937b48de17897484a00611e824023bca965bfbe872f67f1a630bec3b4d
+size 70304
diff --git a/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/raw.md b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..018be9ff622529913dec3b52cb431d004fda03e9
--- /dev/null
+++ b/marked/Q/T-REC-Q.765.1-199805-I_PDF-E/raw.md
@@ -0,0 +1,1822 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.765.1**
+
+(05/98)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Specifications of Signalling System No. 7 – ISDN user part
+
+---
+
+**Signalling System No. 7 – Application transport
+mechanism – Support of VPN applications with
+PSS1 information flows**
+
+ITU-T Recommendation Q.765.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 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 |
+| General | Q.700 |
+| Message transfer part (MTP) | Q.701–Q.709 |
+| Signalling connection control part (SCCP) | Q.711–Q.719 |
+| Telephone user part (TUP) | Q.720–Q.729 |
+| ISDN supplementary services | Q.730–Q.739 |
+| Data user part | Q.740–Q.749 |
+| Signalling System No. 7 management | Q.750–Q.759 |
+| ISDN user part | Q.760–Q.769 |
+| Transaction capabilities application part | Q.770–Q.779 |
+| Test specification | Q.780–Q.799 |
+| Q3 interface | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+
+For further details, please refer to ITU-T List of Recommendations.
+
+## **ITU-T RECOMMENDATION Q.765.1**
+
+## **SIGNALLING SYSTEM No. 7 – APPLICATION TRANSPORT MECHANISM – SUPPORT OF VPN APPLICATIONS WITH PSS1 INFORMATION FLOWS**
+
+## **Summary**
+
+This Recommendation describes the extensions for the support of the VPN applications over the public Network Node Interface (NNI). This application makes use of the Application Transport Mechanism described in Recommendation Q.765 for bearer related signalling, and the Transaction Capability (TCAP) for signalling involving no bearer. This Recommendation specifies the respective users (i.e. APM-user, TC-user) to support the PSS1 information flows continuity in VPN applications (Transparent transfer of PSS1 information flows between PINX entities). The public NNI provides transparency to the services of the private network.
+
+## **Source**
+
+ITU-T Recommendation Q.765.1 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**
+
+APM, ASN.1, ISUP, PSS1, TCAP
+
+## 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 1999
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+## CONTENTS
+
+###### Page
+
+| | | |
+|-------|------------------------------------------------------------------------------------|----|
+| 1 | Scope ..... | 1 |
+| 2 | References ..... | 2 |
+| 3 | Definitions ..... | 3 |
+| 4 | Abbreviations ..... | 3 |
+| 5 | Recommendation structure..... | 5 |
+| 6 | Modelling ..... | 6 |
+| 6.1 | Network model..... | 6 |
+| 6.2 | Specification model..... | 8 |
+| 6.2.1 | Introduction ..... | 8 |
+| 6.2.2 | General model ..... | 8 |
+| 6.2.3 | Dynamic primitive flows..... | 12 |
+| 6.2.4 | Basic call ..... | 15 |
+| 6.2.5 | Transit PINX function – Generic functional protocol..... | 15 |
+| 6.2.6 | Gateway PINX function..... | 15 |
+| 7 | Application Process functions ..... | 16 |
+| 7.1 | General ..... | 16 |
+| 7.2 | VPN Application Process functions – Connection with call (bearer related) ..... | 17 |
+| 7.2.1 | Introduction ..... | 17 |
+| 7.2.2 | Primitive interface (AP – ISUP SACF) ..... | 19 |
+| 7.2.3 | Procedures ..... | 19 |
+| 7.2.4 | Exceptional procedures ..... | 25 |
+| 7.2.5 | Error indication primitive..... | 25 |
+| 7.2.6 | Primitive contents ..... | 25 |
+| 7.3 | VPN Application Process functions – Connection without call (bearer unrelated) ... | 27 |
+| 7.3.1 | Introduction ..... | 27 |
+| 7.3.2 | Primitive interface (AP – TC SACF)..... | 27 |
+| 7.3.3 | Connection Oriented signalling procedures ..... | 27 |
+| 7.3.4 | Primitive contents ..... | 28 |
+| 8 | Single Association Control Function (SACF) – ISUP SACF ..... | 29 |
+| 8.1 | Introduction ..... | 29 |
+| 8.2 | Information flows related to messages sent by the node..... | 30 |
+| 8.3 | Information flows related to messages received by the node ..... | 30 |
+| 9 | Single Association Control Function (SACF) – TC SACF..... | 31 |
+| 9.1 | Introduction ..... | 31 |
+
+| | Page | |
+|--------|---------------------------------------------------------------------------------------------------------------------|----|
+| 9.2 | Information flows related to operations sent by the node ..... | 31 |
+| 9.3 | Information flows related to operations received by the node ..... | 32 |
+| 10 | PSS1 ASE (PSS1 ASE)..... | 32 |
+| 10.1 | Primitive interface ..... | 32 |
+| 10.2 | Signalling procedures..... | 32 |
+| 10.2.1 | Public Initiating Node ..... | 32 |
+| 10.2.2 | Public Addressed Node..... | 33 |
+| 10.2.3 | Signalling congestion..... | 33 |
+| 10.3 | Primitive contents..... | 33 |
+| 11 | Connection Oriented PSS1 ASE (COPSS1 ASE)..... | 34 |
+| 11.1 | TC-user sequence ..... | 34 |
+| 11.2 | Interface COPSS1-ASE/SACF..... | 35 |
+| 11.3 | Supported operations..... | 36 |
+| 11.4 | ASE procedures..... | 36 |
+| 11.4.1 | Relationship between the COPSS1-ASE and TCAP ..... | 37 |
+| 11.4.2 | Operations ..... | 37 |
+| 11.4.3 | Expiry of timers..... | 39 |
+| 11.4.4 | Signalling congestion..... | 39 |
+| 11.5 | Primitive contents..... | 39 |
+| 11.6 | Abstract syntax, general ..... | 39 |
+| 11.7 | Subsystem number ..... | 40 |
+| 11.8 | ASN.1 module ..... | 40 |
+| 12 | TCAP (TC ASE) ..... | 43 |
+| 12.1 | Interface TCAP/SACF..... | 43 |
+| 12.1.1 | Primitives ..... | 43 |
+| 12.1.2 | Use of TCAP ..... | 43 |
+| 13 | SCCP ..... | 43 |
+| 13.1 | Interface SCCP/SACF ..... | 43 |
+| 13.2 | Use of SCCP..... | 44 |
+| 13.3 | Routing in the SCCP network ..... | 44 |
+| 13.4 | Number information used for routing ..... | 44 |
+| 14 | VPNTransport – Formats and codes of application data..... | 44 |
+| 14.1 | Private network specific information elements to be transported within the
Application Transport Parameter ..... | 45 |
+| 14.2 | NNI specific information to be transported in the Application Transport Parameter | 45 |
+
+| | | Page |
+|------|-------------------------|-------------|
+| 15 | Timers..... | 46 |
+| 15.1 | Timers in TC-user ..... | 47 |
+
+
+
+## Recommendation Q.765.1
+
+## SIGNALLING SYSTEM No. 7 – APPLICATION TRANSPORT MECHANISM – SUPPORT OF VPN APPLICATIONS WITH PSS1 INFORMATION FLOWS
+
+(Geneva, 1998)
+
+## 1 Scope
+
+This Recommendation describes the extensions required for the support of VPN applications over the public Network Node Interface (NNI). This application makes use of the Application Transport Mechanism described in Recommendation Q.765 for bearer related signalling, and the Transaction Capability (TCAP) for signalling involving no bearer. This Recommendation specifies the respective users (i.e. APM-user, TC-user) to support the PSS1 information flows continuity in VPN applications (Transparent transfer of PSS1 information flows between PINX entities). The public NNI provides transparency to the services of the private network.
+
+The private network functionality is defined by ISO in its series of Standards for Private Integrated Services Network. In addition, the concept of a "Relay node" is introduced by this Recommendation.
+
+This Recommendation supports a number of network options. These are summarized in Table 1.
+
+**Table 1/Q.765.1 – Network options**
+
+| Option | Values | |
+|----------------------------------------------------------------------|-----------------|------------------------------------------------------|
+| Support of GFP functionality at transit PINX nodes
(See 6.2.5) | Full support | |
+| | Partial support | Not applicable in the international network (Note 1) |
+| Support of GFP functionality at gateway PINX nodes
(See 6.2.6) | Full support | |
+| | No support | (Note 1) |
+| Continuation of calls with no application association
(See 6.2.6) | Supported | (Note 2) |
+| | Not supported | (Note 3) |
+| Relocation of gateway function
(See 6.2.6) | Supported | |
+| | Not supported | |
+
+NOTE 1 – Use of these options might result in certain private network supplementary services behaving in an unexpected manner or not working at all.
+NOTE 2 – In this case, VPN calls must be routed using a mechanism which can correctly route the call to the terminating access without use of the VPN procedures specified in this Recommendation.
+NOTE 3 – In this case, it is required that the VPN procedures are only used on calls which are routed to addresses which are known to support the VPN application via signalling which supports the APM; otherwise, the call will be released.
+
+## 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] ISO/IEC 11574:1994, *Information technology – Telecommunications and information exchange between systems – Private Integrated Services Network – Circuit-mode 64 kbit/s bearer services – Service description, functional model and information flows.*
+- [2] ISO/IEC 11572:1997, *Information technology – Telecommunications and information exchange between systems – Private Integrated Services Network – Circuit mode bearer services – Inter-exchange signalling procedures and protocol.*
+- [3] ISO/IEC 11582:1995, *Information technology – Telecommunications and information exchange between systems – Private Integrated Services Network – Generic functional protocol for the support of supplementary services – Inter-exchange signalling procedures and protocol.*
+- [4] ISO/IEC 11579-1:1994, *Information technology – Telecommunications and information exchange between systems – Private integrated services network – Part 1: Reference configuration for PISN Exchanges (PINX).*
+- [5] ISO/IEC 15055:1997, *Information technology – Telecommunications and information exchange between systems – Private Integrated Services Network – Specification, functional model and information flows – Transit counter additional network feature.*
+- [6] ISO/IEC 15056:1997, *Information technology – Telecommunications and information exchange between systems – Private Integrated Services Network – Inter-exchange signalling protocol – Transit counter additional network feature.*
+- [7] ITU-T Recommendation Q.711 (1993), *Signalling System No. 7 – Functional description of the signalling connection control part.*
+- [8] ITU-T Recommendation Q.712 (1993), *Signalling System No. 7 – Definition and function of SCCP messages.*
+- [9] ITU-T Recommendation Q.713 (1993), *Signalling System No. 7 – SCCP formats and codes.*
+- [10] ITU-T Recommendation Q.714 (1993), *Signalling System No. 7 – Signalling connection control part procedures.*
+- [11] ITU-T Recommendation Q.715 (1996), *Signalling connection control part user guide.*
+- [12] ITU-T Recommendation Q.716 (1993), *Signalling System No. 7 – Signalling Connection Control Part (SCCP) performance.*
+- [13] ITU-T Recommendation Q.763 (1997), *Signalling System No. 7 – ISDN User Part formats and codes.*
+- [14] ITU-T Recommendation Q.764 (1997), *Signalling System No. 7 – ISDN User Part signalling procedures.*
+- [15] CCITT Recommendation Q.767 (1991), *Application of the ISDN user part of CCITT Signalling System No. 7 for international ISDN interconnection.*
+- [16] ITU-T Recommendation Q.771 (1993), *Functional description of transaction capabilities.*
+
+- [17] ITU-T Recommendation Q.772 (1993), *Transaction capabilities information element definitions*.
+- [18] ITU-T Recommendation Q.773 (1993), *Transaction capabilities formats and codes*.
+- [19] ITU-T Recommendation Q.774 (1993), *Transaction capabilities procedures*.
+- [20] ITU-T Recommendation Q.775 (1993), *Guidelines for using transaction capabilities*.
+- [21] ITU-T Recommendation Q.931 (1998), *ISDN user-network interface layer 3 specification for basic call control – Annex M: Additional basic call signalling requirements for the support of private network interconnection for virtual private network applications*.
+- [22] ITU-T Recommendation Q.932 (1998), *Digital Subscriber Signalling System No. 1 – Generic procedures for the control of ISDN supplementary services – Annex D: Enhancements for virtual private networks*.
+- [23] ITU-T Recommendation Q.765 (1998), *Signalling System No. 7 – Application transport mechanism*.
+- [24] ITU-T Recommendation Q.1400 (1993), *Architecture framework for the development of signalling and OA&M protocols using OSI concepts*.
+- [25] ITU-T Recommendations X.680 to X.683 (1994), *Specification of Abstract Syntax Notation One (ASN.1)*.
+
+## 3 Definitions
+
+Reference to PINX functionality within this Recommendation refers to "virtual PINX" functionality implemented on the public NNI.
+
+Within the scope of this Recommendation, "VPN" refers to a Virtual Private Network with the support of PSS1 information flows.
+
+## 4 Abbreviations
+
+This Recommendation uses the following abbreviations.
+
+| | |
+|----------|--------------------------------------------------|
+| ACM | Address Complete Message |
+| AE | Application Entity |
+| AEI | Application Entity Invocation |
+| ALS | Application Layer Structure |
+| ANM | Answer Message |
+| AP | Application Process |
+| APM | Application Transport Mechanism |
+| APM-user | Application Transport Mechanism User Application |
+| APP | Application Transport Parameter |
+| ASE | Application Service Element |
+| CLIP | Calling Line Identification Presentation |
+| CLIR | Calling Line Identification Restriction |
+| CNID | Corporate Telecommunications Network Identifier |
+
+| | |
+|--------|-----------------------------------------------------------|
+| COLP | Connected Line Identification Presentation |
+| COLR | Connected Line Identification Restriction |
+| CON | Connect Message |
+| COPSS1 | Connection Oriented PSS1 |
+| CPG | Call Progress Message |
+| DPINX | Destination PINX |
+| GFP | Generic Functional Protocol |
+| IAM | Initial Address Message |
+| IN | Intelligent Network |
+| ISDN | Integrated Services Digital Network |
+| ISUP | ISDN User Part |
+| LE | Local Exchange |
+| M/O | Mandatory/Optional |
+| MACF | Multiple Association Control Function |
+| MTP-3 | Message Transfer Part |
+| NFE | Network Facility Extension |
+| NI | Network Interface |
+| NNI | Network Node Interface |
+| OPINX | Originating PINX |
+| PAN | Public Addressed Node |
+| PIN | Public Initiating Node |
+| PINX | Private Integrated Services Network Exchange |
+| PRI | Pre-Release Information Message |
+| PSS1 | Private Network Q Reference Point Signalling System No. 1 |
+| REL | Release Message |
+| SACF | Single Association Control Function |
+| SAO | Single Association Object |
+| SCCP | Signalling Connection Control Part |
+| SDL | Specification and Description Language |
+| SID | Signalling Identifier |
+| SSN | Subsystem Number |
+| STP | Signalling Transfer Point |
+| TC | Transaction Capabilities |
+| TE | Transit Exchange |
+| TPINX | Transit PINX |
+| UCEH | Unidentified Context and Error Handling |
+
+| | |
+|-----|-------------------------|
+| UNI | User-Network Interface |
+| VPN | Virtual Private Network |
+
+## 5 Recommendation structure
+
+The description of the ISDN User Part and the TC-user procedures in this Recommendation are structured according to the model described in 6.2. The description is thus divided into two main parts:
+
+- Protocol functions.
+- Non-protocol functions, i.e. exchange nodal functions; this is referred to as the "Application Process".
+
+This Recommendation describes only the part of the total Application Process and Protocol functions in the exchange, that relates to NNI enhancements for the support of private network interconnection in VPN application.
+
+The protocol functions are subdivided into two areas: signalling associations with a bearer (ISUP), and signalling associations without a bearer (Connection Oriented TC-user). For calls with a bearer, it describes the use of the services provided by the APM [23]. For signalling requiring no bearer, it describes the services provided by TCAP.
+
+The signalling association with a bearer is subdivided into three parts: PSS1 Applications Protocol (PSS1 ASE), Application Transport Mechanism (APM ASE) and ISUP Basic Call (ISUP ASE). These are coordinated by the Single Association Coordination Function (SACF).
+
+The Connection Oriented signalling association without a bearer is subdivided into two parts: Connection Oriented PSS1 (COPSS1 ASE), and Transaction Capability (TC ASE). These are coordinated by the Single Association Coordination Function (SACF).
+
+The Application Process (AP) contains all Call Control functions; however, this Recommendation will only describe the enhancements required to support VPN applications. The Application Process relevant to private network functionality can be found in other Recommendations (reference [1] and reference [2]), as can that for the public ISUP basic call [14].
+
+The service primitive technique, used to define the ASEs and the SACF specific to the application's signalling needs is a way of describing how the services offered by an ASE, or SACF, – the provider of (a set) of service(s) – can be accessed by the user of the service(s) – the SACF or the Application Process (AP), respectively.
+
+The service primitive interface is a conceptual interface and is not a testable or accessible interface. It is a descriptive tool. The use of service primitives at an interface does not imply any particular implementation of that interface, nor does it imply that an implementation must conform to that particular service primitive interface to provide the stated service. All conformance to the ISUP and TC specifications is based on the external behaviour at a node, i.e. on the generation of the correct message structure (as specified in reference [13])/operation structure (as specified in this Recommendation) and in the proper sequence (as specified in reference [14] and this Recommendation).
+
+The structure and examples of its usage are illustrated diagrammatically in 6.2.
+
+The relationship between the private network functionality and the Application Transport Mechanism services provided by the public NNI is described as a network model in 6.1. The APM ASE provides the enhancements to the ISUP capabilities such that the services available to the APM-user (VPN application in this context) for a signalling association requiring a bearer are similar to those offered by TCAP where no bearer is required.
+
+The private network specifications (reference [1]) make a reference to specific private network primitives between Call Control and Protocol Control representing the PSS1 information flows. The Application Process in this Recommendation describes the relationship between these primitives and how they relate to the suitable primitives in the ALS model for the transport of the PSS1 information flows.
+
+Examples of the bearer unrelated signalling mechanism can be found in 11.1.
+
+## 6 Modelling
+
+The models described in this clause introduce concepts and terminology used in this specification of the VPN application's use of the capability of the Application Transport Mechanism (APM) for bearer related signalling and the use of Transaction Capability (TC) for bearer unrelated signalling.
+
+### 6.1 Network model
+
+
+
+Diagram of a private network PINX topology. It shows a sequence of nodes: OPINX (Originating PINX) connected via a UNI to TPINX (Transit PINX). This TPINX is connected to a Public Transit Node (s). Below this TPINX is an LE PIN. The Public Transit Node (s) is connected to another TPINX. Below this TPINX are two components: TE PAN and TE PIN. This TPINX is connected to a third TPINX. Below this TPINX is an LE PAN. The third TPINX is connected via a UNI to DPINX (Destination PINX). A dashed line connects the first TPINX to the second TPINX. A solid line connects the first TPINX to the Public Transit Node (s), which is connected to the second TPINX, which is connected to the third TPINX, which is connected to the DPINX. The diagram is labeled 'T1197950-97' in the bottom right corner.
+
+Network model
+
+**Figure 1/Q.765.1 – One example of a private network PINX topology and its relationship with the public NNI's PIN/PAN concept**
+
+This subclause illustrates the relationship between the VPN and the public network, that provides a service. Figure 1 provides an example of a call from an originating PINX to a destination PINX via transit PINXs. The Transit PINXs in this case are implemented within the public network infrastructure. The public network also provides the service of providing a link between the transit PINXs. In this example, the link is via another public transit node.
+
+The Public Initiating Node (PIN) and Public Addressed Node (PAN) concept is introduced in reference [23] to assist in the description of the APM. The PIN represents the point in the network where an APM-user, in this case VPN, application for the support of PSS1 information flows entity (PIN) wishes to initiate communications towards a peer APM-user application located at an addressed location (PAN) in the network. A VPN application for the support of PSS1 information flows may result in the establishment of a signalling and bearer association, in which case it will use the services of the public basic call.
+
+The PINX functionality requests the services of the public network in order to establish a signalling associating with the subsequent PINX in the virtual private network. The initiating PINX application supplies a normal public E.164 number which is used to route through the public network, thus establishing an association between the Public Initiating Node (PIN) and the Public Addressed Node (PAN). The PAN identifies the particular APM-user application by the Context Identifier value carried within the Application Transport Parameter (APP), in this case "PSS1 ASE (VPN)". The PAN identifies the particular PINX application related to a specific corporate network identified by a Corporate Telecommunications Network Identity (e.g. CNID parameter).
+
+The nature of the PINX functionality (i.e. Originating PINX, Destination PINX, Transit PINX or Gateway PINX) is independent of the mechanism described here and is solely dependent on the topology of the virtual private network.
+
+The public basic call mechanism is employed to provide an association between the PIN and the PAN. In routing through the public network, the call may pass through intermediate public nodes with or without the ability to support the private functionality; however, as the private application is not addressed by the particular call instance, it will behave as a normal intermediate public node.
+
+Figure 2 illustrates an example of a public message sequence for a call requiring a bearer (ISUP) in the scenario of Figure 1. Figure 3 illustrates the public operation sequence (TC) for a call not requiring a bearer.
+
+
+
+The diagram illustrates a sequence of messages for a call requiring a bearer (ISUP). The entities involved are OPINX, TPINX (PIN), Transit, TPINX (PAN/PIN), TPINX (PAN), and DPINX. The interfaces are UNI (User Network Interface) and NNI (Network Network Interface). The message sequence is as follows:
+
+- Setup:** OPINX sends a Setup message to TPINX (PIN) via UNI.
+- SetupAck:** TPINX (PIN) sends a SetupAck message back to OPINX via UNI.
+- IAM:** TPINX (PIN) sends an IAM (Initial Address Message) to Transit via NNI.
+- IAM:** Transit sends an IAM message to TPINX (PAN/PIN) via NNI.
+- IAM:** TPINX (PAN/PIN) sends an IAM message to TPINX (PAN) via NNI.
+- Setup:** TPINX (PAN) sends a Setup message to DPINX via UNI.
+- SetupAck:** DPINX sends a SetupAck message back to TPINX (PAN) via UNI.
+- Alerting:** TPINX (PAN) sends an Alerting message to TPINX (PAN/PIN) via NNI.
+- ACM:** TPINX (PAN/PIN) sends an ACM (Address Complete Message) to Transit via NNI.
+- ACM:** Transit sends an ACM message to TPINX (PIN) via NNI.
+- Alerting:** TPINX (PIN) sends an Alerting message back to OPINX via UNI.
+
+Sequence diagram showing a public message sequence for a call with bearer. The diagram shows interactions between OPINX, TPINX (PIN), Transit, TPINX (PAN/PIN), TPINX (PAN), and DPINX. Messages include Setup, IAM, ACM, Alerting, and SetupAck across UNI and NNI interfaces.
+
+T1197960-97
+
+**Figure 2/Q.765.1 – One example of a message sequence for call with bearer**
+
+
+
+Sequence diagram for call without a bearer. The diagram shows the interaction between OPINX, TPINX, STP, PAN, PIN, and DPINX. The sequence starts with a 'Setup' message from OPINX to TPINX. TPINX sends 'Call Proceeding' back to OPINX. TPINX then sends 'Setup.inv' to STP. STP forwards 'Setup.inv' to PAN. PAN sends 'Setup.inv' to TPINX. TPINX sends 'Setup' to DPINX. DPINX sends 'Call Proceeding' back to TPINX. TPINX sends 'Setup.rr' to PAN. PAN sends 'Setup.rr' to STP. STP sends 'Setup.rr' to TPINX. TPINX sends 'Connect' to OPINX. TPINX sends 'Connect.inv' to STP. STP sends 'Connect.inv' to PAN. PAN sends 'Connect.inv' to TPINX. TPINX sends 'Connect' to DPINX. DPINX sends 'Connect' back to TPINX. TPINX sends 'Connect' to OPINX. The diagram is labeled T1197970-97.
+
+**Figure 3/Q.765.1 – One example of an operation sequence for call without a bearer**
+
+### 6.2 Specification model
+
+#### 6.2.1 Introduction
+
+The model used to structure the description of ISUP and TC-USER application procedures is based on the OSI Application Layer Structure (ALS) model (see reference [24]). This subclause presents the model, gives a general description of its operation and shows the generalized model for the "Exchange Application Process" for the support of PSS1 information flows in virtual private networks and in VPN application for the support of PSS1 information flows over the public Network Node Interface (NNI). It shows how the application makes use of the Application Transport Mechanism (APM) which is described in detail in reference [23].
+
+#### 6.2.2 General model
+
+The generalized model for the bearer related (ISUP)/bearer unrelated (TC) VPN Application Process is shown in Figure 4. This figure does not represent the situation at any specific point during ISUP/TC procedures, but instead it shows the full picture of the architecture. The specific application of this model is discussed below. Figure 4 shows the primitive interfaces between the functional blocks, as used in the body of this Recommendation for calls with a bearer (ISUP)/without a bearer (TC).
+
+The definition of the interfaces (a) to (k) are:
+
+- (a) Interface between the Application Process nodal functions (AP) and the SACF for the support of PSS1 information flows in VPN applications over the NNI: see 7.2.2.
+
+- (b) Interface to PSS1 ASE which defines the formats and codes in the APP for the support of PSS1 information flows in VPN applications: see 10.1.
+- (c) Interface between SACF and UCEH ASE representing the handling of unidentified context identifier values and error cases associated with the Application Transport mechanism: reference [23].
+- (d) Interface between SACF and APM ASE representing enhancements of the public (ISUP) functionality for providing a transportation mechanism for the support of various applications (APM-user) over the NNI: (this interface is out of the scope of this Recommendation): reference [23].
+- (e) Interface to public ISUP basic call signalling ASE : (this interface is out of the scope of this Recommendation): reference [23].
+- (f) Interface between SACF and NI function: (this interface is out of the scope of this Recommendation): reference [23].
+- (g) Interface to MTP-3: (this interface is out of the scope of this Recommendation): reference [23].
+- (h) Interface between TC SACF and AP: see 7.3.2.
+- (i) Interface between TC SACF and COPSS1 ASE which performs the function of the protocol control for bearer unrelated Connection Oriented signalling: see 11.1.
+- (j) Interface between TC SACF and TC ASE which provides the services defined in reference [16]: see 12.1.
+- (k) Interface between TC SACF and SCCP which provides the services defined in reference [7]: see 13.1.
+
+
+
+```
+
+graph TD
+ subgraph Exchange_Application [Exchange Application]
+ Nodal_functions[Nodal functions]
+ end
+ subgraph ISUP_AEI [ISUP AEI]
+ ISUP_SAO[ISUP SAO]
+ SACF_ISUP[SACF]
+ PSS1_ASE[PSS1 ASE]
+ UCEH_ASE[UCEH ASE]
+ APM_ASE[APM ASE]
+ ISUP_ASE[ISUP ASE]
+ end
+ subgraph TC_AEI [TC AEI]
+ TC_SAO[TC SAO]
+ SACF_TC[SACF]
+ COPSS1_ASE[COPSS1 ASE]
+ TC_ASE[TC ASE]
+ end
+ NI[NI]
+ SCCP[SCCP]
+ MTP3[MTP-3]
+
+ Nodal_functions -- a --> ISUP_SAO
+ Nodal_functions -- h --> TC_SAO
+ ISUP_SAO -- b --> PSS1_ASE
+ ISUP_SAO -- c --> UCEH_ASE
+ ISUP_SAO -- d --> APM_ASE
+ ISUP_SAO -- e --> ISUP_ASE
+ ISUP_ASE -- f --> NI
+ TC_SAO -- i --> COPSS1_ASE
+ TC_SAO -- j --> TC_ASE
+ TC_ASE -- k --> SCCP
+ NI -- g --> SCCP
+ SCCP --> MTP3
+
+```
+
+Figure 4/Q.765.1 – ISUP and Connection Oriented signalling specification model. The diagram shows a layered architecture for signalling. At the top is the 'Exchange Application' containing 'Nodal functions'. Below this are two parallel paths: the ISUP path and the TC path. The ISUP path includes an 'ISUP AEI' containing 'ISUP SAO', 'SACF', 'PSS1 ASE', 'UCEH ASE', 'APM ASE', and 'ISUP ASE'. The TC path includes a 'TC AEI' containing 'TC SAO', 'SACF', 'COPSS1 ASE', and 'TC ASE'. Both paths converge to a common 'NI' (Network Interface) block, which connects to 'SCCP' (Signalling Connection Control Part), which in turn connects to 'MTP-3' (Message Transfer Part level 3). Interfaces are labeled with letters a through k.
+
+T1197980-97
+
+**Figure 4/Q.765.1 – ISUP and Connection Oriented signalling specification model**
+
+With respect to Figure 4, all functions also have an interface to a "Management application", this is not defined as a formal primitive interface.
+
+The term "Exchange Application Process" is used to describe all the Application functionality in an exchange. ISUP is a part of the Exchange Application Process. Thus the ISUP Nodal functions shown on the model are referred to as the ISUP Application Process functions in the body of this Recommendation. Similarly, the bearer unrelated Transaction Capability Nodal functions shown on the model are referred to as the TC Application Process functions in the body of this Recommendation.
+
+The ISUP/TC AEI provides all the communication capabilities required by the ISUP/TC Nodal functions. For simplicity an ISUP/TC AEI is defined as containing just one SAO; this avoids the
+
+need to specify a Multiple Association Control Function (MACF). Thus all coordination of ISUP signalling associations are performed via the ISUP Nodal functions. Similarly, the coordination of the TC signalling associations are performed via the TC Nodal Functions.
+
+The SACF has the responsibility of coordinating the flow of primitives between its interfaces in the appropriate manner.
+
+The ISUP ASE is defined by reference [14]. Its main responsibilities are basic call procedures and the handling of protocol errors and unrecognized information handling. The monolithic nature of these Recommendations means that both Public Call Control and Protocol Control functionality are defined together. It is not the intention of this Recommendation to redefine reference [14] in ALS format, therefore it is referenced *en bloc* within this Recommendation as the ISUP ASE. Conceptually, this should be considered to represent a logical division between the protocol control functionality within the ISUP ASE and its associated call control functionality within the Application Process. The modelling and interfaces with respect to this are outside the scope of this Recommendation. (See reference [23].)
+
+The APM ASE provides the means for the transfer of information between nodes for signalling requiring a bearer, and provides generic services to applications, while being independent of any of these. It is responsible for the enhancements to the NNI (ISUP) for the support of a mechanism which allows various applications to transport their information flows via the NNI. Its main responsibility is to provide message segmentation/reassembly in order to provide the APM-user the ability to transport up to 2048 octets of application information. The APM ASE is able to support multiple APM-users where each is treated independently and provided with the same level of service. It consists of two distinct sets of functions: one set used as the Public Addressed Node (PAN) and one set used as the Public Initiating Node (PIN) (supporting the signalling association towards to PAN). The PIN/PAN concept is explained in 6.1/Q.765 [23].
+
+The UCEH ASE provides a compatibility mechanism for the case where various levels of application (context) support exists within network nodes as well as APM reassembly error handling. The UCEH ASE is responsible for the procedures related to the reception of an Application Transport parameter referencing an unidentified context identifier and the corresponding handling of a notification that a particular context identifier is not supported at a remote node. (See reference [23].) It is also responsible for the handling of APM reassembly error cases.
+
+The PSS1 ASE is a user of the services offered by the APM ASE. It is responsible for preparing the private signalling information in a form that can be transported by the public Application Transport Mechanism (APM).
+
+The TC ASE provides the means for the transfer of information between nodes for signalling without a bearer, and provides generic services to applications, while being independent of any of these. The TC ASE is defined in references [16] to [20].
+
+The COPSS1 ASE is a user of the services offered by the TC ASE. It consists of two distinct sets of functions related to the Public Addressed Node (PAN) and Public Initiating Node (PIN) of Connection Oriented bearer unrelated signalling (TC dialogue).
+
+To handle any particular ISUP/TC function, the Exchange Application Process creates an instance of the required ISUP/TC Nodal functions. The AP will create instances, as required, of the ISUP/TC AEI. The Network Interface (NI) function exists to distribute messages received from the MTP-3 to the appropriate instance of the ISUP AEI. There is only one instance of the NI in an exchange. Messages are distributed to the appropriate TC AEI based on the SSN and the TC dialogue ID. The NI is described in detail in reference [23].
+
+The SCCP interface is described in references [7] to [12].
+
+The SAO contained in the ISUP AE is one of the following types:
+
+##### a) *Public Initiating Node*
+
+This contains:
+
+- Outgoing ISUP ASE, Initiating APM ASE, Initiating UCEH ASE, Outgoing PSS1 ASE and ISUP SACF.
+
+##### b) *Public Addressed Node*
+
+This contains:
+
+- Incoming ISUP ASE, Addressed APM ASE, Addressed UCEH ASE, Incoming PSS1 ASE and ISUP SACF.
+
+The SAO contained in the TC AE for Connection Oriented bearer unrelated signalling is one of the following types:
+
+##### a) *Public Initiating Node*
+
+This contains:
+
+- Outgoing COPSS1 ASE, TC ASE and TC SACF.
+
+##### b) *Public Addressed Node*
+
+This contains:
+
+- Incoming COPSS1 ASE, TC ASE and TC SACF.
+
+#### 6.2.3 Dynamic primitive flows
+
+##### 6.2.3.1 Bearer related signalling flows
+
+Figures 5 and 6 illustrate the dynamic primitive flows for a VPN call with PSS1 information flow support being supported over the NNI (ISUP) for the case that a call control message is coincident with the application information flow. Figure 5 shows the case when a message is being sent, Figure 6 shows the case when a message is being received.
+
+
+
+The diagram shows an 'Application Process' box at the top. Below it is a large rectangular frame containing three stacked boxes: 'PSS1 ASE', 'APM ASE', and 'ISUP ASE'. Arrows from the 'Application Process' point to each of these three boxes. A large curved arrow originates from the 'Application Process', passes through the three stacked boxes, and points downwards, exiting the frame. The text 'T1197990-97' is located below the 'ISUP ASE' box.
+
+Diagram illustrating dynamic primitive flows for a VPN call. An Application Process is shown at the top, with arrows pointing down to three stacked boxes labeled PSS1 ASE, APM ASE, and ISUP ASE. A large curved arrow originates from the Application Process and points down to the bottom of the stack, passing through the boxes. The text T1197990-97 is visible below the ISUP ASE box.
+
+Figure 5/Q.765.1
+
+
+
+Diagram of Figure 6/Q.765.1 showing an Application Process connected to a large rectangular box. Inside the box are three stacked boxes: PSS1 ASE, APM ASE, and ISUP ASE. Arrows point from the Application Process to each of these three boxes. A return arrow points from the bottom of the large box back to the Application Process. A label 'T1198000-97' is below the ISUP ASE box.
+
+**Figure 6/Q.765.1**
+
+Figures 7 and 8 illustrate the dynamic primitive flows for the NNI support of the PSS1 information flow in a VPN call where no call control messages are sent coincidentally. That is, the APM ASE initiates a primitive towards the ISUP ASE which in turn sends an APM message which will provide a mechanism for supporting the information flow.
+
+
+
+Diagram of Figure 7/Q.765.1 showing an Application Process connected to a large rectangular box. Inside the box are three stacked boxes: PSS1 ASE, APM ASE, and ISUP ASE. An arrow points from the Application Process to the PSS1 ASE. Curved arrows show a flow from PSS1 ASE to APM ASE, and from APM ASE to ISUP ASE. A return arrow points from the bottom of the large box back to the Application Process. A label 'T1198010-97' is below the ISUP ASE box.
+
+**Figure 7/Q.765.1**
+
+
+
+Diagram of Figure 8/Q.765.1 showing an Application Process connected to a large rectangular box. Inside the box, three smaller boxes are stacked vertically: PSS1 ASE, APM ASE, and ISUP ASE. Arrows point from the Application Process to each of these three boxes. A return arrow points from the bottom of the large box back to the Application Process. The text 'T1198020-97' is located below the ISUP ASE box.
+
+Figure 8/Q.765.1
+
+##### **6.2.3.2 Bearer unrelated signalling flows**
+
+Figures 9 and 10 illustrate the dynamic primitive flows for a VPN signalling connection without a bearer being supported over the NNI (TC).
+
+
+
+Diagram of Figure 9/Q.765.1 showing an Application Process connected to a large rectangular box. Inside the box, two smaller boxes are stacked vertically: COPSS1 ASE and TC ASE. Arrows point from the Application Process to each of these two boxes. A return arrow points from the bottom of the large box back to the Application Process. The text 'T1198030-97' is located below the TC ASE box.
+
+Figure 9/Q.765.1
+
+
+
+Diagram showing the interaction between an Application Process and two ASEs (COPSS1 ASE and TC ASE) within a PINX. The Application Process is at the top, connected to a large rectangular box representing the PINX. Inside the PINX, there are two smaller boxes: COPSS1 ASE and TC ASE. Arrows indicate the flow of information: from the Application Process to the COPSS1 ASE, from the COPSS1 ASE to the TC ASE, and from the TC ASE back to the Application Process. A label 'T1198040-97' is present below the TC ASE box.
+
+**Figure 10/Q.765.1**
+
+#### 6.2.4 Basic call
+
+The public network can be considered as a virtual Transit PINX in the establishment of VPN calls requesting support of PSS1 information continuity, thus meeting the functional requirements defined in PSS1 basic call for a Transit PINX.
+
+In case a fall-back situation occurs inside the VPN (i.e. a loss of PSS1 information flows continuity) then the public network provides Gateway PINX functionality, similarly to the behaviour of a Gateway PINX inside a private network interconnecting PINX to a public network.
+
+#### 6.2.5 Transit PINX function – Generic functional protocol
+
+Two cases must be distinguished to describe the public network behaviours for VPN calls or bearer unrelated VPN signalling connections supporting the functional continuity of PSS1-GF procedures (i.e. PSS1 Generic functional protocol for the support of private network supplementary services).
+
+- 1) Full support of GFP functionality: The VPN provides full Transit PINX functionality as defined in PSS1-GF (reference [3]), which includes analysis of the NFE field of the received Facility information elements.
+- 2) Partial support of GFP functionality: The VPN node performs the same functions as in option 1 except for the handling of the Facility information element with the protocol profile set to "networking extensions". The VPN node would pass on PSS1-GF information received in a Facility information element, with the protocol profile set to "networking extensions", transparently between two PINXs that are directly connected to the VPN.
+
+The use of option 2 in a network may result in the incorrect operation of some network services. In order to avoid this problem, it is necessary to take into account a network topology so that such a node is not used in conjunction with such services.
+
+Across the international interface, option 1 capability must be used and supported and the use of option 2 can be agreed to be supported across the international interface through bilateral agreements between network operators.
+
+#### 6.2.6 Gateway PINX function
+
+The Gateway PINX (GPINX) functionality is invoked when it is determined that the continuity of PSS1 information flows cannot be maintained. The GPINX can be invoked as a result of analysis
+
+where it is determined that the destination does not support PSS1 information flows (see Note), or through an indication that the intermediate network signalling does not support the transport of the PSS1 information flows, or through an indication that the APM or APM-user is not supported in the PAN (see 7.2.3.2.5).
+
+NOTE – This includes the situation where the PAN is the DLE acting as a Transit PINX with an outgoing access which supports PSS1 information flows but the call is released by the PAN before sending the call establishment request to the outgoing access.
+
+In the case where it is determined that the PSS1 information flow continuity cannot be maintained, there are two options:
+
+- 1) allow the call to continue (choose to perform the gateway function or request that it be performed elsewhere);
+- 2) release the call.
+
+If the call is allowed to continue, it is necessary that the public basic call information used to route the VPN call is sufficient to allow the call to proceed and terminate successfully. The use of these options is a network-operators choice based on the level of service being offered to the private network owner.
+
+The support of the Generic Functional Protocol (GFP) as part of the Gateway PINX functionality is optional according to ISO/IEC 11582 [3]. It is therefore a network operator's option to support the Generic Functional Protocol handling procedures. It must be noted that some services may behave in a less than desirable manner if the GFP is not supported.
+
+In order to reduce the effect of network signalling load resulting from the support of the PSS1 information flows in the VPN, it is a network operator's option to support the mechanism for moving the GPINX functionality as close as possible to the originating end of the call path. There are two possibilities:
+
+- a) Gateway PINX function provided at point of "break-out":
+
+This is when the Gateway PINX function is performed at the point in the network where it is determined that the gateway is required.
+
+- b) Gateway PINX function provided by cooperation between nodes (movement of the gateway functionality to an earlier point in the call path):
+
+This is when the node that determines that a gateway PINX function is required performs the "basic call" gateway function (and the GF gateway function if it supports it) for the IAM message. If that node was informed that a previous node is capable of providing the gateway functionality (Gateway transformation capability indication received in the IAM, sent by an earlier node in the call path), then it sends a request backwards to do so. When the node with the capability to transform into a gateway PINX receives the request, it then performs the gateway functionality (basic call and GF, if supported) from that time onwards for that call.
+
+## 7 Application Process functions
+
+### 7.1 General
+
+The modelling of the Application Process (AP) is outside the scope of this Recommendation; however, in order to appreciate the role of the AP for the purposes of this Recommendation, it can be considered to consist of three different types of functionality that are relevant to the support of private networks over the public network nodal interface. These are Public network Application Transport Mechanism (as defined in reference [23] and ISUP basic call [14]) and the Virtual Private
+
+Network (VPN) applications for the support of PSS1 functionality, as defined in this Recommendation.
+
+The aspect of the Application Process that this Recommendation introduces is the required coordination between the public and VPN (for the support of PSS1 information flows) Application Process functionality in order to provide the appropriate transportation of PSS1 information flow via:
+
+- the combination of public ISUP basic call and the Application Transport Mechanisms;
+- using transaction capability mechanisms.
+
+The private network functionality being provided by the VPN is described in 6.2.4, 6.2.5 and 6.2.6. In order to show the relationship between the VPN AP and the PSS1 Call Control logic, this Recommendation defines the mapping between the Call Control/Protocol Control [2] and the SACF interface (a) primitives. It also describes the additional VPN specific procedures. The description of either the public or PINX Application Processes are outside the scope of this Recommendation.
+
+The definition of the primitive interface at the Application Process/SACF for the public Application Transport Mechanism is outside the scope of this Recommendation.
+
+### **7.2 VPN Application Process functions – Connection with call (bearer related)**
+
+#### **7.2.1 Introduction**
+
+The function of the Public NNI support of VPN applications aspect of the Application Process (AP) is to coordinate between the private network (PSS1) Application Process and the public Application Process functionality. When the private application requires to establish a signalling association with a bearer, the AP converts the private address information into the form that the public Application Process can use for routing the call from the Public Initiating Node (PIN) to the appropriate exchange in the public network, Public Addressed Node (PAN), which contains the adjacent PINX functionality. The PIN/PAN concept is described in reference [23]. The specific private network use of the concept is described in 6.1. Details of the Public basic call routing information requirements can be found in reference [14]. The conversion of private information to a form suitable for routing through the public network is outside the scope of this Recommendation. It is network specific as to how the appropriate public routing information is generated (e.g. it may be a result of local analysis or IN mechanisms may be employed).
+
+It is not the intention of this Recommendation to redefine the PSS1 PINX functionality, therefore the call control defined in reference [1] applies. The purpose of this Recommendation is to describe how, together with the ISUP basic call and APM, the services expected by PSS1 at the Call Control (CC)/Protocol Control (PC) interface (defined in reference [2]) are fulfilled in a VPN, thus achieving PSS1 information flow continuity over the public NNI.
+
+It is the responsibility of the VPN Application Process to ensure that the public basic call and PSS1 Call Control states remain aligned.
+
+The PSS1 primitive interface between Call Control and Protocol Control (see ISO/IEC model in reference [2]) and that between Generic Functional Transport-Control (GFT) and Protocol Control (see ISO/IEC model in reference [3]) are not seen on any interface in the ALS. It is not the intention of this Recommendation to model the AP, however to illustrate the relationship between this Recommendation and the PINX functionality defined by ISO Standards, Figure 11 can be used. The relevancy of the PSS1-Call control and PSS1-Generic Functional Protocol shown in Figure 11 is dependent upon the PINX functionality being provided by a node.
+
+
+
+Diagram showing the relationship between PSS1 primitive interfaces and the ALS model. The diagram consists of three stacked layers. The top layer contains two boxes: 'PSS1 – Call Control' on the left and 'PSS1 – Generic Functional Protocol' on the right. The middle layer contains a single box labeled 'VPN, APM and ISUP basic call application Process'. The bottom layer contains a box labeled 'SACF'. Double-headed vertical arrows connect 'PSS1 – Call Control' to the middle box, 'PSS1 – Generic Functional Protocol' to the middle box, and the middle box to the 'SACF' box.
+
+T1198050-97
+
+**Figure 11/Q.765.1 – Relationship between PSS1 primitive interfaces and ALS model**
+
+In order for the PSS1 information flow continuity to be maintained in a virtual private network, it is necessary to introduce additional procedures that allow VPNs to coexist in the public network and to handle scenarios that are specific to the support of these over the public network. These procedures include the possible use of a Corporate Telecommunications Network Identifier (CNID) to uniquely identify a corporate network, the transfer of VPN identities and the appropriate setting of Application Transport Instruction Indicators (ATII) in order to cater for error cases.
+
+At call establishment the PINX functionality located at the PAN will determine that additional private digits may need to be received (overlap sending of private digits). In this case, it is necessary for the PAN to send back towards the PIN a "setup acknowledgement" indication in order to confirm the signalling association through the network such that the PIN can reliably send additional digits towards the PAN.
+
+In order for the VPN calls requesting PSS1 information flows support to operate correctly, it is necessary that the signalling capability of intermediate public nodes between the PIN and PAN are able to transport the APP. If the subsequent link(s) does not support the APM and hence the transport of the VPN information is lost, or if the addressed node does not have the APM or PINX functionality, then the node shall invoke the Gateway PINX functionality described in 6.2.6. This signalling capability may not be fulfilled if the call is routed through nodes such as a Q.767 ISUP [15], a public gateway node or a non-ISUP protocol. To cater for the case when the intermediate nodes and their associated signalling capabilities cannot support the transport of PSS1 information flows using the Application Transport Mechanism, or the case when the call addresses a node without the APM or without the PSS1 PINX functionality and is allowed to continue (network option), it is necessary to have a mechanism to confirm that the VPN call supports PSS1 information flows ["VPN feature transparency capability" (VTI) indication] and to inform the preceding PINX that Gateway PINX functionality is required to be invoked. The mechanism to have the Gateway function invoked must work in an implicit manner by invoking the GPINX functionality:
+
+- on the non-reception of a positive confirmation that PSS1 information flow continuity is supported [VPN feature transparency capability (VTI) indication];
+- on reception of a notification "unidentified context";
+- on reception of a confusion message with a diagnostic field indicating that the Application Transport parameter has been discarded.
+
+The node must make a decision whether to release the call immediately or to allow it to continue (network operator's option based on the level of service being offered to the private network owner).
+
+If the call is allowed to continue, then it is necessary that the public basic call information is sufficient to allow the call to be terminated successfully.
+
+When it is determined that Gateway PINX functionality must be invoked, the "node determining gateway PINX functionality is required" may (as a network option) request a PINX located closer to the originating end of the call, "node capable of gateway PINX transformation", to perform the Gateway function thereby reducing the signalling load on the public network resulting from the private network signalling. A mechanism has been introduced to allow this transformation of an earlier Originating PINX or Transit PINX in the call path to an Outgoing Gateway PINX. The mechanism relies on the node sending forward an indication that it is able to perform the transformation and a subsequent node, on determining that a Gateway function is required, sending backwards a request to transform into a gateway PINX.
+
+#### 7.2.2 Primitive interface (AP – ISUP SACF)
+
+The primitive interface [interface (a) in Figure 4] between the AP and the ISUP SACF consists of primitives required to support the public network basic call functionality, and those to support the Virtual Private Network (VPN) functionality. The primitives related to the public network functionality are outside the scope of this Recommendation, although references are made to them through functional inferences within the text. The public basic call Recommendation is not described using ALS concepts, hence the need for functional inferences to the public basic call functionality rather than specific references to primitives. The primitives related to the VPN functionality are described in this Recommendation. See Table 2.
+
+**Table 2/Q.765.1 – Primitives between AP and ISUP SACF
+(Virtual Private Network Support)**
+
+| Primitive name | Types | Direction (Note) |
+|-------------------------------------------------------------------------------|--------------------|------------------|
+| PSS1_Data | Indication/Request | ➔/➔ |
+| PSS1_Error | Indication | ➔ |
+| Remote_Status | Indication | ➔ |
+| NOTE – Primitive flow from SACF to AP: ➔
Primitive flow from AP to SACF: ➔ | | |
+
+#### 7.2.3 Procedures
+
+##### 7.2.3.1 PSS1 information flows
+
+The private network service descriptions are defined by ISO in the series of International Standards describing the Private Integrated Services Network. These services are built upon the Circuit-mode 64 kbit/s bearer services Standard references [1] and [2], and the Generic functional protocol for the support of supplementary services Standard [3]. The support of the private network services in a virtual private network is achieved through the transport of the necessary information flows over the public network signalling between entities that support the private network service descriptions. Tables 3, 4 and 5 describe how the PSS1 information flows are distributed across primitives on the AP/SACF interface.
+
+**Table 3/Q.765.1 – Mapping between PSS1 primitives defined in reference [2] and AP/ISUP SACF primitives**
+
+| Primitives to/from CC Interface
(reference [2]) | | Flow | ISUP Messages | Primitives to/from AP/SACF
Interface (PSS1 ASE) |
+|----------------------------------------------------|------|------|---------------|----------------------------------------------------|
+| PC_SETUP | REQ | ➔ | IAM | +PSS1_DATA.Req |
+| | IND | ➔ | IAM | +PSS1_DATA.Ind |
+| | RES | ➔ | ANM/CON | +PSS1_DATA.Req |
+| | CONF | ➔ | ANM/CON | +PSS1_DATA.Ind |
+| PC_MORE_
INFORMATION | REQ | ➔ | APM/ACM | +PSS1_DATA.Req |
+| | IND | ➔ | APM/ACM/CPG | +PSS1_DATA.Ind |
+| PC_INFORMATION | REQ | ➔ | APM | +PSS1_DATA.Req |
+| | IND | ➔ | APM | +PSS1_DATA.Ind |
+| PC_PROCEED | REQ | ➔ | ACM/CPG | +PSS1_DATA.Req |
+| | IND | ➔ | ACM/CPG | +PSS1_DATA.Ind |
+| PC_ALERTING | REQ | ➔ | ACM/CPG | +PSS1_DATA.Req |
+| | IND | ➔ | ACM/CPG | +PSS1_DATA.Ind |
+| PC_PROGRESS | REQ | ➔ | ACM/CPG | +PSS1_DATA.Req |
+| | IND | ➔ | ACM/CPG | +PSS1_DATA.Ind |
+| PC_REJECT | REQ | ➔ | PRI/REL | +PSS1_DATA.Req (PRI only) |
+| | IND | ➔ | PRI/REL | +PSS1_DATA.Ind (PRI only) |
+| PC_DISCONNECT | REQ | ➔ | PRI/REL | +PSS1_DATA.Req (PRI only) |
+| | IND | ➔ | PRI/REL | +PSS1_DATA.Ind (PRI only) |
+| PC_RELEASE | REQ | ➔ | PRI/REL | +PSS1_DATA.Req (PRI only) |
+| | IND | ➔ | PRI/REL | +PSS1_DATA.Ind (PRI only) |
+| DL_RESET | IND | | n/a | |
+
+**Table 4/Q.765.1 – Mapping between PSS1 primitives defined in reference [5] and AP/ISUP SACF primitives**
+
+| Primitives to/from CC Interface
(reference [5]) | | Flow | ISUP
Messages | Primitives to/from AP/SACF
Interface (PSS1 ASE) |
+|----------------------------------------------------|-----|------|------------------|----------------------------------------------------|
+| PC_TRANSIT_COUNTER | REQ | ➔ | IAM | +PSS1_DATA.Req |
+| | IND | ➔ | IAM | +PSS1_DATA.Ind |
+
+**Table 5/Q.765.1 – Mapping between PSS1 primitives defined in reference [3] and AP/ISUP SACF primitives**
+
+| Primitives to/from
CC Interface
(reference [3]) | | Flow | ISUP Messages | Primitives to/from
AP/SACF Interface
(PSS1 ASE) |
+|-------------------------------------------------------|-----|------|-----------------------------|-------------------------------------------------------|
+| PC_DATA | REQ | ➔ | IAM/ACM/ANM/CON/CPG/PRI/APM | +PSS1_DATA.Req |
+| | IND | ➔ | IAM/ACM/ANM/CON/CPG/PRI/APM | +PSS1_DATA.Ind |
+| PC_NOTIFY | REQ | ➔ | IAM/ACM/ANM/CON/CPG/PRI/APM | +PSS1_DATA.Req |
+| | IND | ➔ | IAM/ACM/ANM/CON/CPG/PRI/APM | +PSS1_DATA.Ind |
+
+##### **7.2.3.2 NNI indications and procedures**
+
+In order to support the PSS1 information flows across the public network, it is necessary to introduce additional procedures and information flows to allow the virtual private network to coexist in the public network environment.
+
+###### **7.2.3.2.1 Handling of address information**
+
+###### **Procedures at the PIN**
+
+The called party number sent in the PSS1\_Data request primitive sent at call establishment is also, as a national option, transferred in the ISUP generic number parameter with the Number qualifier indicator coded "additional called party number" in the IAM message.
+
+The calling party number sent in the PSS1\_Data request primitive sent at call establishment is, as a national option, also transferred in the ISUP generic number parameter with the Number qualifier indicator coded "additional calling party number" without taking into account the public CLIR and CLIP supplementary services.
+
+The connected number received in the PSS1\_Data indication primitive received in conjunction with the primitive corresponding to the CON or ANM message and the connected subaddress received according to the public basic call procedures are transferred to the access signalling system without taking into account the public COLP and COLR supplementary services.
+
+###### **Procedures at the PAN**
+
+The calling party number received in the PSS1\_Data indication primitive received in conjunction with the IAM message and the calling party subaddress received according to the public basic call procedures are transferred to the access signalling system without taking into account any possible public CLIP and CLIR supplementary service.
+
+The connected number sent in the PSS1\_Data request primitive sent in conjunction with the primitive corresponding to the CON or ANM message is transferred without taking into account the public COLP and COLR supplementary services in the primitive corresponding to the CON or ANM message.
+
+The connected subaddress is transferred according to the public basic call procedures without taking into account the public COLP and COLR supplementary services.
+
+###### **7.2.3.2.2 Corporate Telecommunications Network Identifier**
+
+The Corporate Telecommunications Network Identifier (CNID) is either supplied over the incoming User-Network Interface (UNI) access, or it has an implicit value tied to the incoming access. The CNID is only required for call establishment [IAM message (ISUP)] and is mandatory over the international interface and has global significance. It is an operator's network option to employ an alternative mechanism for identifying a Corporate Telecommunications Network within their own domain. On receipt of a CNID that is not recognized by the PAN, then the call shall be released with cause 63 (service or option not available – unspecified) and the management function notified.
+
+###### **7.2.3.2.3 Application Transport Instruction Indicators**
+
+The Application Transport Instruction Indicators (ATII) are required to be sent in conjunction with any private network specific information in order to handle error cases such as an unidentified context at the PAN or reassembly errors. They are to be set according to the particular needs of the application. That is, if the requested functionality is essential to the call, then the ATII should be set to release the call. Alternatively if actions are required to be performed to gracefully handle the case that the communication is not successful but the call is to continue, then a notification should be
+
+requested. If there is no real need to indicate an unsuccessful communication with the PAN, then no actions need to be requested in the ATII.
+
+###### **7.2.3.2.4 Acknowledgement from peer application (Overlap sending)**
+
+###### **Procedures at the PAN**
+
+On reception of the PC\_More\_Information.Request primitive, the AP will send a PSS1\_Data.request primitive indicating "Setup Acknowledgement" causing an APM message to be sent towards the PIN.
+
+###### **Procedures at the PIN**
+
+On reception of the PSS1\_Data.indication primitive indicating "Setup Acknowledgement", the AP will send PC\_More\_Information.Indication primitive. The PIN shall send the remainder of the private Called party number digits (if any) in the Called party number parameter of one or more PSS1\_Data Request primitives resulting in one or more APM messages. The Sending Complete parameter may also be sent according to the PSS1 Call Control overlap procedures.
+
+###### **7.2.3.2.5 Subsequent node does not support APM/VPN**
+
+###### **Procedures at the PAN**
+
+When a call is being established with PSS1 feature transparency capability, it implicitly requests this capability by the presence of the APP parameter with Application Context Identifier coded "PSS1 ASE (VPN)" in the IAM message. If the PAN determines that the VPN call supports PSS1 information flows continuity, the PAN shall include in the first backwards message the "Call with VPN feature transparency capability"(VTI) indication in an APP parameter.
+
+###### **Procedures at the PIN**
+
+On reception of the "Call with VPN feature transparency capability (VTI)" indication at the PIN in an ACM, CPG, CON, ANM, PRI or APM message, the PIN shall apply the procedures defined for VPN calls with PSS1 information flows continuity. After the sending of an IAM, the PIN shall not send APP parameters (containing Facility "Networking extensions" information elements or notifications) before receipt of the "Call with VPN feature transparency capability" (VTI) indication. Such information may be discarded.
+
+If the option to continue calls with no application association is supported, then the Gateway PINX functionality shall be invoked in the following cases. The gateway PINX is described in 6.2.6:
+
+- In the case that ISUP receives a Confusion message containing a cause parameter non-existent or not implemented, discarded (99) with diagnostics indicating the APP, then the APM is not supported in a subsequent node.
+- On reception of a notification that the peer APM user was not present at the PAN [APP parameter with Application Context Identifier field coded "Unidentified Context and Error Handling (UCEH) ASE" and with the Application Transport Notification information coded "PSS1 ASE (VPN)" (APM-user Context Identifier field) and "unidentified context" (Reason field), received in an ACM, CON, ANM, CPG, APM or PRI message].
+- On receipt of the primitive corresponding to the CON message without any APP parameter coded "PSS1 ASE (VPN)" (ACI field) and a previous message with the indication of "call with VPN feature transparency capability" has not been received.
+- On receipt of the primitive corresponding to the ANM message without any APP parameter coded "PSS1 ASE (VPN)" (ACI field) and a previous message with the indication of "call with VPN feature transparency capability" has not been received.
+
+- On receipt of the primitive corresponding to the REL message if the "call with VPN feature transparency capability" indication has not been received in a previous message.
+- On receipt of the primitive corresponding to the ACM message indicating "subscriber free", without any APP parameter coded "PSS1 ASE (VPN)" (ACI field) and a previous message with the indication of "call with VPN feature transparency capability" has not been received.
+- On receipt of the primitive corresponding to the CPG message indicating "Alerting", without any APP parameter coded "PSS1 ASE (VPN)" (ACI field) and a previous message with the indication of "call with VPN feature transparency capability" has not been received.
+
+If the option to continue calls with no application association is not supported, then on the receipt of the above indications that the call does not support the PSS1 information flows continuity, the call shall be released with cause 63 (service or option not available – unspecified) and the management function notified.
+
+###### **7.2.3.2.6 Gateway PINX transformation request mechanism (network option)**
+
+It should be noted that the use of this mechanism has the effect of removing intermediate transit PINXs between the "node capable of gateway PINX transformation" and the "node determining gateway PINX functionality is required", therefore the network topology must be taken into account when using this feature.
+
+Receipt of the "Gateway PINX Transformation Request" indication takes precedence over the procedures described in 7.2.3.2.5 which may be invoked on reception of the "VPN feature transparency capability (VTI)" indication.
+
+###### **Node capable of gateway PINX transformation**
+
+A node with PINX functionality that has the capability of transforming from either an Originating PINX or Transit PINX into a Gateway PINX, ("node capable of gateway PINX transformation"), shall indicate "PINX with gateway transformation capability" in the forward direction in the initial setup message.
+
+On receiving a "Gateway PINX transformation request" indication in an ACM, CPG, CON, ANM, PRI or APM message, a node shall check the note in memory to determine if a previous node has the capability to transform into a Gateway PINX. If not, then the node shall transform its PINX functionality to behave as an Outgoing Gateway PINX for all subsequent private network specific information received. Procedures as described in 7.2.3.2.5 for the PAN when the Gateway PINX function is invoked shall apply, in particular the sending in the backwards direction of the "Call with VPN feature transparency capability (VTI)" indication if not already sent.
+
+###### **Intermediate node**
+
+Any node with PINX functionality subsequent to the "node capable of gateway PINX transformation" shall make a note in memory that a previous node has the capability and also indicates the same in the forward direction.
+
+On receiving a "Gateway PINX transformation request" indication, a node shall check the note in memory to determine if a previous node has the capability to transform into a Gateway PINX. If so, then the request shall be passed unchanged.
+
+The node shall continue as a Transit PINX for any subsequent PSS1 information received. Such information may continue to be received until the Gateway PINX transformation request has been processed by the "node capable of gateway PINX transformation".
+
+###### Node determining gateway PINX functionality is required
+
+A node with PINX functionality that determines that an Outgoing gateway PINX functionality must be invoked ("node determining gateway PINX functionality is required") shall perform the appropriate actions on the private network specific information received as defined by ISO (see 6.2.6).
+
+It shall then, as a network option, check the note in memory to determine if a previous node has the capability to transform into a Gateway PINX. If the capability is available, the node shall indicate "Gateway PINX transformation request" in the backwards direction and shall send the "VPN feature transparency capability (VTI)" indication set to "no indication".
+
+The node shall continue as a Gateway PINX for any subsequent PSS1 information received. Such information may continue to be received until the Gateway PINX transformation request has been processed by the "node capable of gateway PINX transformation".
+
+##### 7.2.3.4 Relay node
+
+The Relay node functionality distinguishes VPN calls, and relays such calls to designated PINX functionality emulated by the public network equipment, or to a designated physical PINX. This may be via other Relay node functionality which includes transparent handling of private networking information.
+
+A Relay node allows a network to provide PINX functionality remotely from a UNI access. A Relay node does not have PINX functionality, rather it provides a transparent link between an access and the node containing the PINX functionality within the network.
+
+When the Relay node requires to establish a signalling association with a bearer, the AP generates public routing information in the form that the public Application Process can use for routing the call from the Public Initiating Node (PIN) to the appropriate exchange in the public network, Public Addressed Node (PAN), which contains the PINX functionality. Details of the Public basic call routing information requirements can be found in reference [14]. The public routing information is implicitly tied to the particular Corporate Telecommunications Network Identifier associated with the access.
+
+The Relay node performs the interworking of PSS1 information flows between the User-Network Interface (UNI) and the Network Node Interface (NNI) protocols. The private network specific information is passed transparently and distributed to primitives on the AP/ISUP SACF interface in the same manner as if the information was received from the private call control logic, hence the private network specific information flow transparency is achieved.
+
+The Relay node can be considered as illustrated in Figure 12.
+
+
+
+```
+graph LR
+ subgraph UNI
+ OPINX[OPINX] --- Relay
+ end
+ subgraph NNI
+ Relay --- Transit
+ Transit --- TPINX
+ end
+ subgraph Relay
+ LE_PIN[LE PIN]
+ end
+ subgraph TPINX
+ TE[TE]
+ PAN[PAN]
+ end
+```
+
+Diagram illustrating a Relay node interworking the UNI and NNI protocols. The diagram shows three main components: OPINX (left), Relay (center), and TPINX (right). The Relay node is connected to the OPINX via a UNI interface and to the TPINX via an NNI interface. The Relay node contains two sub-components: LE PIN and Transit. The LE PIN is connected to the UNI interface, and the Transit is connected to the NNI interface. The TPINX contains two sub-components: TE and PAN. The TE is connected to the NNI interface, and the PAN is connected to the Transit. The diagram is labeled T1198060-97.
+
+**Figure 12/Q.765.1 – Illustration of a Relay node interworking the UNI and NNI protocols thereby interfacing between two PINX functions**
+
+#### 7.2.4 Exceptional procedures
+
+#### 7.2.5 Error indication primitive
+
+On reception of a PSS1\_Error primitive containing an error notification indicating "unidentified context", if the option to continue calls with no application association is supported (see 6.2.6) then the node shall invoke gateway PINX functionality (see 7.2.3.2.5). If this option is not supported, then the call shall be released and the management function shall be notified.
+
+On reception of a PSS1\_Error primitive containing an error notification indicating "reassemble error", the management function shall be notified.
+
+On reception of a PSS1\_Error indication primitive containing an error notification indicating "unrecognized information", then a call will be allowed to proceed if possible, else the call shall be released.
+
+On reception of a PSS1\_Error indication primitive containing an error notification indicating "unrecognized mandatory information", the call shall be released with cause code 111 – Protocol error, unspecified.
+
+#### 7.2.6 Primitive contents
+
+Tables 6 and 7 contain the list of parameters in the primitives.
+
+Table 8 shows the contents of the PSS1\_Data primitive sent in conjunction with ISUP messages in a VPN call with support of PSS1 information flows continuity.
+
+Mandatory/Optional (M/O) indications are provided as well as a reference for a detailed description of the parameters.
+
+**Table 6/Q.765.1 – Contents of the PSS1\_Data Ind/Req primitive**
+
+| Parameter | Mandatory/Optional |
+|------------------------------------------|--------------------|
+| ATII | M |
+| VPN feature transparency indication | O |
+| Gateway PINX transformation capability | O |
+| CNID | O |
+| Gateway PINX request | O |
+| SetupAcknowledgment | O |
+| Calling party number | O |
+| Called party number | O |
+| Connected number | O |
+| Facility (Note) | O |
+| Notification indicator (Note) | O |
+| Sending Complete | O |
+| Transit counter | O |
+| NOTE – These parameters may be repeated. | |
+
+**Table 7/Q.765.1 – Contents of the PSS1\_Error Ind primitive**
+
+| Parameter | Mandatory/Optional |
+|--------------------|---------------------------|
+| Error Notification | M |
+
+**Table 8/Q.765.1 – Contents of the PSS1\_Data Req/Ind primitives sent in conjunction with ISUP messages in a VPN call with support of PSS1 information flows continuity**
+
+| ISUP message | PSS1_Data Req/ind primitive parameters (Mandatory/Optional) |
+|------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | - • Called party number (M)
- • ATII (M)
- • Gateway PINX transformation capability (O)
- • CNID (O)
- • Calling party number (O)
- • Facility (O) (Note)
- • Notification indicator (O) (Note)
- • Sending Complete (O)
- • Transit counter (O)
|
+| ACM | - • ATII (M)
- • VPN feature transparency indication (O)
- • Facility (O) (Note)
- • Notification indicator (O) (Note)
|
+| CPG | - • ATII (M)
- • VPN feature transparency indication (O)
- • Facility (O) (Note)
- • Notification indicator (O) (Note)
|
+| ANM | - • ATII (M)
- • VPN feature transparency indication (O)
- • Connected number (O)
- • Facility (O) (Note)
- • Notification indicator (O) (Note)
|
+| CON | - • ATII (M)
- • VPN feature transparency indication (O)
- • Connected number (O)
- • Facility (O) (Note)
- • Notification indicator (O) (Note)
|
+| PRI | - • ATII (M)
- • VPN feature transparency indication (O)
- • Facility (O) (Note)
- • Notification indicator (O) (Note)
|
+| APM | - • ATII (M)
- • Called party number (O)
- • SetupAcknowledgement (O)
- • VPN feature transparency indication (O)
- • Facility (O) (Note)
- • Notification indicator (O) (Note)
- • Sending Complete (O)
|
+| NOTE – These parameters may be repeated. | |
+
+### 7.3 VPN Application Process functions – Connection without call (bearer unrelated)
+
+#### 7.3.1 Introduction
+
+The function of the Public NNI support of VPN applications aspect of the Application Process (AP) is to coordinate between the private network (VPN) Application Process and the public Application Process functionality. When the private application requires to establish a signalling association without a bearer, the AP converts the private address information into the form that the public Application Process can use for routing from the Public Initiating Node (PIN) to the appropriate node in the public network, Public Addressed Node (PAN), which contains the adjacent PINX functionality. The PIN/PAN concept is described in reference [23]. The specific private network use of the concept is described in 3.1. The conversion of private information to a form suitable for routing through the public network is outside the scope of this Recommendation.
+
+It is not the intention of this Recommendation to redefine the PSS1 PINX functionality. The purpose of this Recommendation is to describe how, through the use of TC and SCCP, the services expected by PSS1 at the Generic Functional Transport (GFT) /Protocol Control (PC) interface (defined in reference [3]) are fulfilled in a VPN, thus achieving PSS1 information flows continuity over the public NNI.
+
+The PSS1 primitive interface between GFT and PC (see ISO/IEC model in reference [3]) is not seen on any interface in the ALS. It is not the intention of this Recommendation to model the AP; however, to illustrate the relationship between this Recommendation and the PINX functionality defined by ISO, Figure 11 can be used.
+
+Connectionless signalling is not supported by this Recommendation.
+
+#### 7.3.2 Primitive interface (AP – TC SACF)
+
+The VPN application uses the services provided by the TC SACF primitive interface [interface (h) in Figure 4] as listed in Table 9.
+
+**Table 9/Q.765.1 – Primitives between AP and TC SACF**
+
+| Primitive name | Types | Direction (Note) |
+|-------------------------------------------------------------------------------|------------------------------------------|------------------|
+| PSS1_Setup | Indication/Request/Response/Confirmation | ➔/⬅/⬅/➔ |
+| PSS1_Release | Indication/Request | ➔/⬅ |
+| PSS1_Reject | Indication/Request | ➔/⬅ |
+| PSS1_Facility | Indication/Request | ➔/⬅ |
+| PSS1_SetupAck | Indication/Request | ➔/⬅ |
+| NOTE – Primitive flow from SACF to AP: ➔
Primitive flow from AP to SACF: ⬅ | | |
+
+#### 7.3.3 Connection Oriented signalling procedures
+
+The protocol control procedures that describe the mapping of the Generic Functional Transport (GFT) primitives to transaction (TC) operations over the public NNI are described here with reference to reference [3]. The procedural aspects of the PINX functionality are outside the scope of this Recommendation (see 6.2.5 for the functionality provided by the VPN). In order to describe the relationship between the primitives on the GFT/PC interface to the operations used over TC, this Recommendation defines the mapping between the primitives referred to in reference [3] and the suitable AP/TC SACF interface primitives. See Table 10.
+
+Primitives related to the private application functionality are outside the scope of this Recommendation (see reference [3]).
+
+**Table 10/Q.765.1 – Mapping between primitives used in reference [3] and AP/TC SACF primitives**
+
+| COLUMN A
Primitives used at GFT/PC interface
as defined in reference [3] | COLUMN B
Primitives used on AP/TC SACF interface |
+|-----------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|
+| PC_SETUP request/indication | PSS1_SETUP request/indication |
+| PC_SETUP response/confirmation | PSS1_SETUP response/confirmation |
+| | |
+| PC_RELEASE request/indication | PSS1_RELEASE request/indication |
+| PC_REJECT request/indication | PSS1_REJECT request/indication |
+| PC_DATA request/indication | PSS1_FACILITY request/indication |
+| (Not applicable) | PSS1_SetupAck request/indication |
+
+##### 7.3.3.1 Corporate Telecommunications Network Identifier
+
+The Corporate Telecommunications Network Identifier (CNID) is either supplied over the incoming User-Network Interface (UNI) access, or it has an implicit value tied to the incoming access. The CNID is only required for call establishment [SETUP operation (TC)] and is mandatory over the international interface and has global significance. It is an operator's network option to employ an alternative mechanism for identifying a Corporate Telecommunications Network within their own domain. On receipt of a (CNID) that is not recognized by the PAN, the connection shall then be released with cause 63 (service or option not available – unspecified) and the management function notified.
+
+##### 7.3.3.2 Relay node
+
+See 7.2.3.4.
+
+#### 7.3.4 Primitive contents
+
+Tables 11 to 15 contain the list of parameters in the primitive.
+
+The primitive PSS1\_SetupAck is empty.
+
+Mandatory/Optional (M/O) indications are provided as well as a reference for a detailed description of the parameters.
+
+**Table 11/Q.765.1 – Contents of the PSS1\_SETUP Ind/Req**
+
+| Parameter | Mandatory/Optional |
+|-------------------------------------------------|---------------------------|
+| Public Called Party Number | M |
+| Called Party Number | M |
+| Calling Party Number | O |
+| Corporate Telecommunications Network Identifier | O |
+| Facility (Note) | O |
+| Transit Counter | O |
+| NOTE – These parameters may be repeated. | |
+
+**Table 12/Q.765.1 – Contents of the PSS1\_SETUP Res/Conf primitive**
+
+| Parameter | Mandatory/Optional |
+|------------------------------------------|---------------------------|
+| Connected Number | O |
+| Facility (Note) | O |
+| NOTE – These parameters may be repeated. | |
+
+**Table 13/Q.765.1 – Contents of the PSS1\_RELEASE Ind/Req primitive**
+
+| Parameter | Mandatory/Optional |
+|------------------------------------------|---------------------------|
+| Cause | M |
+| Facility (Note) | O |
+| NOTE – These parameters may be repeated. | |
+
+**Table 14/Q.765.1 – Contents of the PSS1\_REJECT Ind/Req primitive**
+
+| Parameter | Mandatory/Optional |
+|------------------------------------------|---------------------------|
+| Cause | M |
+| Facility (Note) | O |
+| NOTE – These parameters may be repeated. | |
+
+**Table 15/Q.765.1 – Contents of the PSS1\_FACILITY Ind/Req primitive**
+
+| Parameter | Mandatory/Optional |
+|------------------------------------------|---------------------------|
+| Facility (Note) | M |
+| NOTE – These parameters may be repeated. | |
+
+## **8 Single Association Control Function (SACF) – ISUP SACF**
+
+### **8.1 Introduction**
+
+The main objective of ISUP SACF is to receive/deliver primitives from/to the appropriate entity and to perform a distribution function where appropriate for the ISUP AEI. The flow of information is from the AP [interface (a) in Figure 4] towards NI [interface (f) in Figure 4] or vice versa, therefore the SACF is also responsible to ensure that when multiple primitives are generated by the ASEs towards the AP, that they are delivered across the interface together to ensure the correct associations are maintained. The SACF described here only defines the mapping and functions related to the NNI support of VPN applications aspect of the model. The SACF functionality related to the public APM functionality is outside the scope of this Recommendation. The mapping of primitives in Tables 16 and 19 are in reference [23] and are included here for informative purposes only.
+
+The interfaces referenced herein are illustrated in 6.2, Figure 4. Examples of the "Dynamic primitive flows" can be found in 6.2.3.
+
+The primitives on the interface between SACF and the AP, interface (a), are defined in 7.2.2.
+
+The parameters in these primitives are listed in Tables 6 to 8.
+
+The primitives on the interface between SACF and PSS1 ASE, interface (b), are defined in 10.1.
+
+The parameters in these primitives are listed in Tables 24 to 25.
+
+The primitives on the interface between SACF and UCEH ASE, interface (c), can be found in reference [23] and are therefore outside the scope of this Recommendation.
+
+The primitives on the interface between SACF and APM ASE, interface (d), can be found in reference [23] and are therefore outside the scope of this Recommendation.
+
+The primitives on the interface between SACF and ISUP ASE, interface (e), can be found in reference [23] and are therefore outside the scope of this Recommendation.
+
+The primitives on the interface between SACF and NI, interface (f), can be found in reference [23] and are therefore outside the scope of this Recommendation.
+
+### 8.2 Information flows related to messages sent by the node
+
+On receipt of a primitive (request or response) from the Application Process (AP) [interface (a) in Figure 4], the SACF issues appropriate primitive(s) to the ASEs, populating the parameters in the generated primitives from the appropriate subset of the parameters received from the AP. The SACF also performs distribution of the responding primitives received from the ASEs prior to sending the resulting primitive to NI [interface (f) in Figure 4].
+
+**Table 16/Q.765.1 – Mapping between PSS1 ASE and APM ASE primitives**
+
+| Interface (b), from PSS1 ASE | Interface (d), APM ASE |
+|-------------------------------------|-------------------------------|
+| APM_U_Data | APM_Data |
+
+**Table 17/Q.765.1 – Mapping between AP and PSS1 ASE primitives**
+
+| Interface (a), from AP | Interface (b), PSS1 ASE |
+|-------------------------------|--------------------------------|
+| PSS1_Data | PSS1_Data |
+
+### 8.3 Information flows related to messages received by the node
+
+These procedures are described in reference [23] where the APM-user ASE corresponds with the PSS1 ASE.
+
+**Table 18/Q.765.1 – Mapping between PSS1 ASE and AP primitives**
+
+| Interface (b), PSS1 ASE | Interface (a), from AP |
+|--------------------------------|-------------------------------|
+| PSS1_Data | PSS1_Data |
+| PSS1_Error | PSS1_Error |
+
+**Table 19/Q.765.1 – Mapping between APM ASE and PSS1 ASE primitives**
+
+| Interface (d), from APM ASE | Interface (b), PSS1 ASE |
+|------------------------------------|--------------------------------|
+| APM_Data | APM_U_Data |
+
+**Table 20/Q.765.1 – Mapping between UCEH ASE and PSS1 ASE primitives**
+
+| Interface (c), from UCEH ASE | Interface (b), PSS1 ASE |
+|------------------------------|-------------------------|
+| APM_Error | APM_U_Error |
+
+## **9 Single Association Control Function (SACF) – TC SACF**
+
+### **9.1 Introduction**
+
+The main objective of TC SACF is to receive/deliver primitives from/to the appropriate entity for the TC AEI. The SACF described here only defines the mapping and functions related to the NNI support of VPN applications aspect of the model.
+
+Four interfaces (shown in Figure 4) are described by this Recommendation:
+
+- AP/SACF;
+- SCCP/SACF;
+- COPSS1/SACF;
+- TC ASE/SACF.
+
+The interfaces referenced herein are illustrated in 6.2, Figure 4. Subclause 6.2.3 also provides examples of the "Dynamic primitive flows".
+
+The primitives received from the AP, on interface h), are mapped as shown in 7.3.2 and 7.4.2. The parameters in these primitives are listed in 7.3.5.
+
+The primitives on the interface between SACF and COPSS1 ASE, interface (i), are listed in 11.1.
+
+The primitives on the interface between SACF and TCAP, interface (j), are listed in references [16] to [20]. (See clause 12.)
+
+The primitives on the interface between SACF and SCCP, interface (k), are listed in references [7] to [12]. (See clause 13.)
+
+### **9.2 Information flows related to operations sent by the node**
+
+On receipt of a primitive (request or response) from the AP [interface (h) in Figure 4], the SACF issues appropriate primitive(s) to the ASEs, populating the parameters in the generated primitives from the appropriate subset of the parameters received from the AP. The SACF also performs the distribution of the responding primitives received from the ASEs prior to sending the succeeding primitive. With regard to the interface between SACF and TCAP, all the TC primitives exchanged between the COPSS1 ASE and the TCAP pass through the SACF unchanged. See Table 21.
+
+**Table 21/Q.765.1 – Mapping between AP and COPSS1 ASE primitives**
+
+| Interface (h), from AP | Interface (i), COPSS1 ASE |
+|------------------------|---------------------------|
+| PSS1_Setup | PSS1_Setup |
+| PSS1_SetupAck | PSS1_SetupAck |
+| PSS1_Release | PSS1_Release |
+| PSS1_Reject | PSS1_Reject |
+| PSS1_Facility | PSS1_Facility |
+
+### 9.3 Information flows related to operations received by the node
+
+On receipt of a N\_DATA indication primitive from the SCCP, the SACF analyses the User Data field of this primitive according to the rules in reference [9]. It then proceeds to perform the function of distribution. See Table 22.
+
+**Table 22/Q.765.1 – Mapping between COPSS1 ASE and AP primitives**
+
+| Interface (i), COPSS1 ASE | Interface (h), from AP |
+|---------------------------|------------------------|
+| PSS1_Setup | PSS1_Setup |
+| PSS1_SetupAck | PSS1_SetupAck |
+| PSS1_Release | PSS1_Release |
+| PSS1_Reject | PSS1_Reject |
+| PSS1_Facility | PSS1_Facility |
+
+## 10 PSS1 ASE (PSS1 ASE)
+
+The PSS1 ASE is responsible for the signalling aspects of the VPN application for the support of PSS1 information flows and for preparing the information in the appropriate form that can be passed to the APM for transportation.
+
+### 10.1 Primitive interface
+
+Table 23 lists the primitive interface between the PSS1 ASE and ISUP SACF, [interface (b) in Figure 4].
+
+**Table 23/Q.765.1 – Primitives between ISUP SACF and PSS1 ASE (APM)**
+
+| Primitive name | Types | Direction (Note) |
+|-------------------------------------------------------------------------------------------|--------------------|------------------|
+| APM_U_Data | Indication/Request | ➔/➔ |
+| APM_U_Error | Indication | ➔ |
+| PSS1_Error | Indication | ➔ |
+| PSS1_Data | Indication/Request | ➔/➔ |
+| NOTE – Primitive flow from SACF to PSS1 ASE: ➔
Primitive flow from PSS1 ASE to SACF: ➔ | | |
+
+### 10.2 Signalling procedures
+
+#### 10.2.1 Public Initiating Node
+
+##### 10.2.1.1 Sending procedures
+
+On reception of the PSS1\_Data.request primitive, its contents are prepared in the appropriate format (see clause 14) and the context identifier value set to "PSS1 ASE (VPN)". The result is sent in the APM\_U\_Data.request primitive.
+
+##### 10.2.1.2 Receiving procedures
+
+On reception of the APM\_U\_Data.indication primitive, its contents are checked for correct format and coding (see clause 14). If the check is passed, the received information is transferred and sent in the PSS1\_Data.indication primitive. If the check is failed, then also send the PSS1\_Error.indication primitive with the results and indicating "unrecognized information". If an unrecognized value is received for the CNID indicator field, then the Error Notification sent in the PSS1\_Error indication primitive shall indicate "unrecognized mandatory information".
+
+##### 10.2.1.3 APM\_U\_Error Primitive
+
+On reception of the APM\_U\_Error.indication primitive, the contents should be passed unchanged in the PSS1\_Error primitive.
+
+#### 10.2.2 Public Addressed Node
+
+See 10.2.1.
+
+#### 10.2.3 Signalling congestion
+
+In order to avoid congestion in the No. 7 signalling network, it is necessary that applications that contribute signalling load towards a congested destination limit their signalling traffic in a controlled manner. As the AP makes use of the ISUP ASE, the ISDN User Part signalling congestion control procedure [14] may reduce traffic towards an affected destination. As such new call attempts may temporarily be rejected.
+
+### 10.3 Primitive contents
+
+Tables 24 and 25 list the mandatory and optional contents for the PSS1 ASE service primitives. These primitives are defined in reference [23] and are included here for informative purposes only.
+
+The contents of the PSS1\_Error and PSS1\_Data primitives are defined at the AP/SACF interface in 7.2.6
+
+Mandatory/Optional (M/O) indications are provided.
+
+**Table 24/Q.765.1 – Contents of the APM\_U\_Data Ind/Req primitive**
+
+| Parameter | Mandatory/Optional |
+|----------------------------------------------|--------------------|
+| Application Context Identifier | M |
+| Application Transport Instruction Indicators | M |
+| Application Data | M |
+
+**Table 25/Q.765.1 – Contents of the APM\_U\_Error Ind primitive**
+
+| Parameter | Mandatory/Optional |
+|--------------|--------------------|
+| Notification | M |
+
+## 11 Connection Oriented PSS1 ASE (COPSS1 ASE)
+
+This COPSS1 ASE is responsible for the signalling aspects of the VPN application for the support of PSS1 information flows and for preparing the information in the appropriate form that can be passed to the TC for transportation.
+
+### 11.1 TC-user sequence
+
+### Signalling flow for call setup and teardown
+
+In Figure 13, a signalling flow is given for the setup and release of a dialogue to support bearer unrelated (Connection Oriented) private network information transfer. The UNI information elements are transferred over the NNI using TC messages. The following operations are defined to allow the transfer of the relevant UNI information flows: ***Setup, Connect, Release, VpnFacility***. The Setup operation is of class 3 and the remaining operations are of class 4.
+
+Two timers supervise the release of the TC dialogue. Timer T3 shall be started in the PIN on receipt of the Setup return result operation and timer T4 shall be started in the PAN on sending the Setup return result operation. Both timers are restarted on sending/receipt of an operation.
+
+A class 3 operation called ***ActivityTest*** is sent to check whether the remote application is still alive. This operation shall be generated in the PIN on expiry of timer T3. Timer T2 shall supervise the receipt of the return result. On receipt of the ActivityTest operation the PAN shall restart timer T4 and on receipt of the return result the PIN shall stop timer T2 and start timer T3.
+
+On expiry of timer T1, T2 or T4, the PIN shall send a TC-U-ABORT (abort the dialogue) and inform the management function.
+
+
+
+The diagram illustrates a signalling sequence between two private networks, A and B, through intermediate nodes OLEX and DLEX. The sequence of messages is as follows:
+
+- Private Network A** (OPINX) sends a **SETUP** message to **OLEX** (TPINX PIN).
+- OLEX** sends a **TC-BEGIN (setup inv)** message to **DLEX** (TPINX PAN).
+- DLEX** sends a **SETUP** message to **Private Network B** (DPINX).
+- Private Network B** sends a **CALL PROCEEDING** message back to **DLEX**.
+- DLEX** sends a **TC-CONTINUE (setup rr)** message back to **OLEX**.
+- OLEX** sends a **CALL PROCEEDING** message back to **Private Network A**.
+- Private Network B** sends a **CONNECT** message to **DLEX**.
+- DLEX** sends a **TC-CONTINUE (connect)** message back to **OLEX**.
+- OLEX** sends a **CONNECT** message back to **Private Network A**.
+- Private Network A** sends a **FACILITY** message to **OLEX**.
+- OLEX** sends a **TC-CONTINUE (VPNFacility)** message to **DLEX**.
+- DLEX** sends a **FACILITY** message to **Private Network B**.
+- Private Network A** sends a **RELEASE** message to **OLEX**.
+- OLEX** sends a **TC-CONTINUE (activityTest inv)** message to **DLEX**.
+- DLEX** sends a **TC-CONTINUE (activityTest rr)** message back to **OLEX**.
+- OLEX** sends a **RELEASE COMPLETE** message back to **Private Network A**.
+- DLEX** sends a **TC-END (release)** message back to **OLEX**.
+- OLEX** sends a **RELEASE COMPLETE** message back to **Private Network A**.
+- Private Network B** sends a **RELEASE** message to **DLEX**.
+- DLEX** sends a **RELEASE COMPLETE** message back to **Private Network B**.
+
+Switch symbols (circles with an 'X') are shown on the signal lines between the networks and the nodes, indicating switching points. The nodes OLEX and DLEX have internal switching symbols (T1, T2, T3, T4) shown on their respective signal paths.
+
+Sequence diagram illustrating a bearer unrelated signalling sequence between Private Network A and Private Network B via OLEX and DLEX nodes.
+
+T1198070-97
+
+**Figure 13/Q.765.1 – Example of a bearer unrelated signalling sequence**
+
+### 11.2 Interface COPSS1-ASE/SACF
+
+Table 26 lists the primitive interface between the COPSS1-ASE and TC SACF, [interface (i) in Figure 4].
+
+Other primitives on this interface correspond to the TC-user interface as defined in references [16] and [17].
+
+**Table 26/Q.765.1 – Primitives between COPSS1-ASE and TC SACF (Protocol Control)**
+
+| Primitive name | Types | Direction (Note) | Corresponding operation(s) |
+|-----------------------------------------------------------------------------------------------|-----------------------|------------------|----------------------------|
+| PSS1_SETUP | Indication/Request | ➔/➔ | Setup.Invoke |
+| PSS1_SETUP | Response/Confirmation | ➔/➔ | Connect.Invoke |
+| PSS1_REJECT | Indication/Request | ➔/➔ | Setup.ReturnResult |
+| PSS1_SETUPACK | Indication/Request | ➔/➔ | Setup.ReturnResult |
+| PSS1_FACILITY | Indication/Request | ➔/➔ | VpnFacility.Invoke |
+| PSS1_RELEASE | Indication/Request | ➔/➔ | Release.Invoke |
+| NOTE – Primitive flow from SACF to COPSS1 ASE: ➔
Primitive flow from COPSS1 ASE to SACF: ➔ | | | |
+
+### 11.3 Supported operations
+
+The ASE supports the following Operations:
+
+- Setup (Class 3).
+- Connect (Class 4).
+- VpnFacility (Class 4).
+- Release (Class 4).
+- ActivityTest (Class 3).
+
+Invocation of the above-mentioned Operations can generate the following components:
+
+- Setup
+ - Setup.Invoke
+ - Setup.ReturnResult
+- Connect
+ - Connect.Invoke
+- VpnFacility
+ - VpnFacility.Invoke
+- Release
+ - Release.Invoke
+- ActivityTest
+ - ActivityTest.Invoke
+ - ActivityTest.ReturnResult
+
+### 11.4 ASE procedures
+
+The COPSS1 ASE is responsible for coordinating the information received in primitives and preparing it according to the operation definition and TCAP primitive interface requirements.
+
+#### **11.4.1 Relationship between the COPSS1-ASE and TCAP**
+
+The dialogue defined for the PSS1 information flows support between the peer-to-peer entities (TC-Users) is a structured dialogue. The dialogue ID parameter is used in both operation handling and transmission (dialogue) handling primitives to determine which component(s) pertain(s) to which dialogue.
+
+Each TC-User has its own reference for a given dialogue. These references are local references and mapping of these local references into protocol references transaction ID, included in the messages, is done by TC.
+
+All the operations below belong to the same dialogue.
+
+Class 3 and 4 operations are used.
+
+Each TC message conveys only a single operation.
+
+##### **11.4.1.1 Dialogue beginning**
+
+The PIN establishes the dialogue by using a TC-BEGIN.request primitive with TC-INVOKE.request primitive to transmit a Setup (class 3) operation invoke component to the PAN. The PAN responds by:
+
+- Using the TC-CONTINUE.request primitive with TC-RESULT-L.request primitive to transmit a Setup.ReturnResult component, confirm the dialogue, and indicate that the Setup.request operation was successful. No parameter is included in this case in the Setup.ReturnResult.
+- Using the TC-END.request primitive with TC-RESULT-L.request primitive to transmit a Setup.ReturnResult component, end the dialogue, and indicate that the Setup.request operation failed. The cause parameter shall be included in this case. In addition, one or more Facility "Networking extensions" information elements may be included in the VPNTransport parameter.
+
+##### **11.4.1.2 Dialogue continuing**
+
+The continuation of the dialogue is assumed by the Connect (class 4), VpnFacility (class 4) and ActivityTest (class 3) operations using TC-CONTINUE primitives.
+
+##### **11.4.1.3 Dialogue end**
+
+###### **11.4.1.3.1 Basic end**
+
+A dialogue end is requested by either the PIN or PAN using TC\_END.request primitive with TC-INVOKE.request primitive to transmit a Release operation invoke component.
+
+###### **11.4.1.3.2 Abnormal end**
+
+When the TC-user determines that it will abort the dialogue, it does so with the TC-U-ABORT primitive. On receipt of a TC-NOTICE or a TC-P-ABORT indication primitive, the TC dialogue shall be terminated.
+
+#### **11.4.2 Operations**
+
+##### **11.4.2.1 Setup operation**
+
+On reception of the PSS1\_SETUP.request primitive, its contents are loaded into and sent from the PIN with the Setup.invoke operation. Timer T1 is started. On reception of the operation at the PAN, its contents are sent in a PSS1\_SETUP.indication primitive. In case the signalling connection request can be accepted by the AP at the PAN (the COPSS1 ASE receives a PSS1\_SETUPACK request), it
+
+responds towards the PIN with the Setup.ReturnResult operation and starts timer T4. On reception of the return result operation at the PIN, its contents are sent in a PSS1\_SETUPACK.indication, timer T1 is stopped, and timer T3 is started. In case the signalling connection request cannot be accepted by the AP at the PAN (the COPSS1 ASE receives a PSS1\_REJECT request), it responds towards the PIN with the Setup.ReturnResult operation. On reception of the return result operation at the PIN, its contents are sent in a PSS1\_REJECT indication and timer T1 is stopped.
+
+##### **11.4.2.2 Connect operation**
+
+On reception of the first PSS1\_SETUP.response primitive, its contents are loaded into and sent from the PAN with the Connect.invoke. Timer T4 is restarted. On reception of the operation at the PIN, the contents are passed in the PSS1\_SETUP.confirmation primitive, timer T3 is restarted.
+
+##### **11.4.2.3 VpnFacility operation**
+
+The VpnFacility operation may be sent from either PIN to PAN or vice versa after sending/receipt of the Connect invoke operation.
+
+PIN to PAN: On reception of the PSS1\_FACILITY.request primitive, its contents are loaded into and sent from the PIN with the VpnFacility.invoke operation. Timer T3 is restarted. On reception of the operation at the PAN, the contents are passed in the PSS1\_FACILITY.indication primitive, and timer T4 is restarted.
+
+PAN to PIN: On reception of the PSS1\_FACILITY.request primitive, its contents are loaded into and sent from the PAN with the VpnFacility.invoke. Timer T4 is restarted. On reception of the operation at the PIN, the contents are passed in the PSS1\_FACILITY.indication primitive, and timer T3 is restarted.
+
+##### **11.4.2.4 ActivityTest operation**
+
+On expiry of timer T3, the PIN sends an ActivityTest.invoke operation and starts timer T2. On reception of the operation, the PAN sends the ActivityTest.returnresult operation in response and restarts timer T4. On reception of the response at the PIN, timer T2 is stopped and timer T3 started.
+
+##### **11.4.2.5 Release operation**
+
+The Release operation may be sent from either PIN to PAN or vice versa.
+
+PIN to PAN: On reception of the PSS1\_RELEASE.request primitive, its contents are loaded into and sent from the PIN with the Release.invoke operation. Timer T3 is stopped. On reception of the operation at the PAN, the contents are passed in the PSS1\_RELEASE.indication primitive, and timer T4 is stopped.
+
+PAN to PIN: On reception of the PSS1\_RELEASE.request primitive, its contents are loaded into and sent from the PAN with the Release.invoke operation. Timer T4 is stopped. On reception of the operation at the PIN, the contents are passed in the PSS1\_RELEASE.indication primitive, and timer T3 is stopped.
+
+##### **11.4.2.6 Exceptional procedures**
+
+On receipt of either a TC-P-ABORT, a TC-U-ABORT, a TC-U-REJECT, a TC-L-CANCEL or a TC-NOTICE primitive, the dialogue is released with cause "normal unspecified".
+
+#### **11.4.3 Expiry of timers**
+
+##### **11.4.3.1 T1**
+
+On expiry of timer T1, the dialogue shall be aborted using the TC-U-ABORT primitive and the PSS1\_REJECT indication primitive shall be sent to the Application Process with cause "normal unspecified".
+
+##### **11.4.3.2 T2**
+
+On expiry of timer T2, the dialogue shall be aborted using the TC-U-ABORT primitive and the PSS1\_RELEASE indication primitive shall be sent to the Application Process with cause "normal unspecified".
+
+##### **11.4.3.3 T3**
+
+On expiry of timer T3, the activity test procedures shall be initiated (see 11.4.2.4).
+
+##### **11.4.3.4 T4**
+
+On expiry of timer T4, the dialogue shall be aborted using the TC-U-ABORT primitive and the PSS1\_RELEASE indication primitive shall be sent to the Application Process with cause "normal unspecified".
+
+#### **11.4.4 Signalling congestion**
+
+In order to avoid congestion in the No. 7 signalling network, it is necessary that applications that contribute signalling load towards a congested destination limit their signalling traffic in a controlled manner. As the AP makes use of the TC ASE, the COPSS1 ASE shall take appropriate action on receipt of a TC-NOTICE primitive indicating signalling congestion. Similar to the procedures for the ISDN User Part signalling congestion control [14], the AP should reduce the establishment of new transactions towards the affected destination.
+
+### **11.5 Primitive contents**
+
+The contents of the primitives are described in 7.3.4.
+
+### **11.6 Abstract syntax, general**
+
+Subclause 11.8 specifies the abstract syntax for the COPSS1 ASE protocol using the Abstract Syntax Notation One (ASN.1) [25].
+
+The set of values each of which is a value of the ASN.1 type TCAPMessages, MessageType as defined in references [16] to [20] with the ANY DEFINED BY definitions resolved by the operations and errors definitions included in 11.8 form the abstract syntax for the COPSS1 ASE protocol.
+
+The set of encoding rules which are applicable to this abstract syntax are defined by references [16] to [20]. The mapping of the OPERATION and ERROR MACROs to TC components is also described in references [16] to [20].
+
+The ASN.1 data type which follows the keywords "PARAMETER" or "RESULT" (for OPERATION and ERROR) is always optional from a syntactic point of view. However, except for specific mention, it has to be considered as mandatory from a semantic point of view.
+
+When a mandatory element is missing in any component or inner data structure, a reject component is returned (if the dialogue still exists). The problem cause to be used is "Mistyped parameter".
+
+### 11.7 Subsystem number
+
+The SSN value of 0000 1011 "ISDN supplementary services" will be used.
+
+### 11.8 ASN.1 module
+
+The following ASN.1 module specifies the protocol elements defined for the COPSS1 ASE. It shows the definition of the operations, errors and types required for the Connection Oriented, bearer unrelated signalling for the support of PSS1 information flows using ASN.1 as defined by reference [25] and using the OPERATION and ERROR macros as defined by references [16] to [20].
+
+The formal definition of the component types to encode these operations, errors and types is provided in references [16] to [20].
+
+**COPSS1 -Protocol {itu-t Recommendation q 765 1 modules(2) operations-and-errors(1) version1(1)}**
+
+**DEFINITIONS IMPLICIT TAGS ::=**
+
+**BEGIN**
+
+**IMPORTS OPERATION, ERROR**
+
+**FROM TCAP Messages {ccitt Recommendation q 773 modules(2) messages(1) version2(2)};**
+
+**==
+-- TYPE DEFINITIONS FOR OPERATIONS
+==**
+
+**--Specification of Setup
+-- =====**
+
+**--Direction: OLEX → DLEX**
+
+**--Class: 3**
+
+**--Timer: T1**
+
+**--Purpose: Used for the establishment of a signalling association between a PIN and a PAN for a bearer unrelated signalling connection.**
+
+**SetUp ::= OPERATION**
+
+**ARGUMENT**
+
+**SetUpArg**
+
+**RESULT**
+
+**SetUpResultArg**
+
+**--Specification of Connect
+-- =====**
+
+**--Direction: DLEX → OLEX**
+
+**--Class: 4**
+
+--Purpose: *Indicates that the signalling connection has reached the active state.*
+
+**Connect ::= OPERATION**
+
+**ARGUMENT**
+
+**ConnectArg**
+
+--Specification of Release
+
+-- =====
+
+--Direction: *OLEX → DLEX and DLEX → OLEX*
+
+--Class: 4
+
+--Purpose: *Used for releasing a signalling association between a PIN and a PAN.*
+
+**Release ::= OPERATION**
+
+**ARGUMENT**
+
+**ReleaseArg**
+
+--Specification of VpnFacility
+
+-- =====
+
+--Direction: *OLEX → DLEX and DLEX → OLEX*
+
+--Class: 4
+
+--Purpose: *Used for transporting PSSI information flows during the active phase of a signalling connection.*
+
+**VpnFacility ::= OPERATION**
+
+**ARGUMENT**
+
+**VpnFacilityArg**
+
+--Specification of ActivityTest
+
+-- =====
+
+--Direction: *OLEX → DLEX*
+
+--Class: 3
+
+--Timer: T2
+
+--Purpose: *Used to determine if the signalling association remains established between a PIN and a PAN.*
+
+**ActivityTest ::= OPERATION**
+
+#### RESULT
+
+---
+
+---
+
+--TYPE DEFINITIONS FOR ERRORS
+
+---
+
+---
+
+-
+
+---
+
+---
+
+-- TYPE DEFINITIONS FOR ARGUMENT DATA
+
+---
+
+---
+
+**SetUpArg** ::= **SEQUENCE** {
+
+**calledPartyNumber** **CalledPartyNumber**,
+
+**vpntransport** **VPNTransport**,
+
+...
+
+}
+
+**SetUpResultArg** ::= **SEQUENCE** {
+
+**cause** [0] **Cause** **OPTIONAL**,
+
+**vpntransport** [1] **VPNTransport** **OPTIONAL**,
+
+...
+
+}
+
+**ConnectArg** ::= **VPNTransport**
+
+**ReleaseArg** ::= **SEQUENCE** {
+
+**cause** **Cause**,
+
+**vpntransport** [0] **VPNTransport** **OPTIONAL**,
+
+...
+
+}
+
+**VpnFacilityArg** ::= **VPNTransport**
+
+---
+
+---
+
+--TYPE DEFINITIONS FOR DATA
+
+---
+
+---
+
+**CalledPartyNumber** ::= **OCTET STRING (SIZE (1..maxcdPlength))**
+
+--The *CalledPartyNumber* is coded as described in Recommendation Q.763 [13].
+
+--The ISUP parameter name and length octets are not included.
+
+**VPNTransport** ::= **OCTET STRING (SIZE (0..maxLength))**
+
+--The *VPNTransport* is coded as described in clause 14/Q.765.1.
+
+**Cause** ::= **OCTET STRING (SIZE (1..maxCauseLength))**
+
+--The *Cause* is coded as described in ISO/IEC 11572 [2]/ Q.931 Annex M [21]
+
+--The information element identifier and length octets are not included.
+
+#### --- --- --DEFINITION OF RANGE CONSTANTS --- ---
+
+| | | |
+|----------------|---------|----------------------|
+| maxCauseLength | INTEGER | ::= 30 |
+| maxLength | INTEGER | ::= 2048 |
+| maxcdPlength | INTEGER | ::= Network specific |
+
+---
+
+---
+
+#### --DEFINITION OF OBJECT IDENTIFIER PATH --- ---
+
+| | | |
+|-----------|-------------------|-------------------------------------------------------------|
+| COPSS1OID | OBJECT IDENTIFIER | ::= {itu-t Recommendation q 765 1 operations-and-errors(1)} |
+|-----------|-------------------|-------------------------------------------------------------|
+
+---
+
+---
+
+#### --ASSIGNMENTS FOR OPERATION VALUES --- ---
+
+| | | |
+|--------------|--------------|---------------------------------------------|
+| setUp | SetUp | ::= globalValue {COPSS1OID setUp(1)} |
+| connect | Connect | ::= globalValue {COPSS1OID connect(2)} |
+| release | Release | ::= globalValue {COPSS1OID release(3)} |
+| vpnFacility | VpnFacility | ::= globalValue {COPSS1OID vpnFacility(4)} |
+| activityTest | ActivityTest | ::= globalValue {COPSS1OID activityTest(5)} |
+
+---
+
+---
+
+#### --ASSIGNMENTS FOR ERROR VALUES --- ---
+
+-
+
+END--of COPSSI-Protocol
+
+## 12 TCAP (TC ASE)
+
+The SACF uses the services provided by the TCAP primitive interface. The definition of TCAP is outside the scope of this Recommendation. For details refer to references [16] to [20].
+
+### 12.1 Interface TCAP/SACF
+
+#### 12.1.1 Primitives
+
+The primitives at this interface that support the services offered by TCAP are defined in references [16] to [20].
+
+#### 12.1.2 Use of TCAP
+
+This application uses TCAP for structured dialogues.
+
+The peer-to-peer dialogue established by the COPSS1 ASE, as a TC-user, is a structured dialogue. The dialogue ID parameter is used in both operation handling and transmission (dialogue) handling primitives to determine which component(s) pertain(s) to which dialogue. Each TC-user has its own reference for a given dialogue. These references are local references and mapping of these local references into protocol references transaction ID, included in the messages, is done by TCAP. The class used by each operation is defined in the ASN.1 definition.
+
+## 13 SCCP
+
+### 13.1 Interface SCCP/SACF
+
+The TC-SACF uses the services provided by the SCCP primitive interface. The definition of SCCP is outside the scope of this Recommendation. For details refer to the SCCP references [7] to [12].
+
+### 13.2 Use of SCCP
+
+- SCCP Class 1 service (Sequenced Connectionless Service) is used by this application.
+- The SCCP message return option will always be used.
+- A minimum of 1992 version of SCCP to be used, but preferably 1996/97 version of SCCP [7] to [12] to be used.
+
+### 13.3 Routing in the SCCP network
+
+For routing on the international interface and for routing based on the GT translation mechanism within national networks, the coding of the called party address and the calling party address in SCCP shall comply with the following restrictions:
+
+| | | |
+|-------------------|-----------|----------------------------------------------------------------------------------|
+| SSN indicator | 1 | (SSN for ISDN supplementary services is always included) |
+| GT indicator | 0100 | (includes translation type numbering plan encoding scheme and nature of address) |
+| Translation Type | 0001 0001 | (translation table) |
+| Numbering plan | 0001 | (ISDN/Telephony Numbering Plan E.164) |
+| Routing indicator | 0 | (Routing on global title) |
+
+Alternatively, for routing within a national network, the SCCP addressing method based on SPCs may apply. However, within large national networks, it would be advisable to use a hybrid addressing method based on SPCs for regional traffic and GT translation mechanism for long distance traffic, to keep the SS No. 7 routing data manageable.
+
+### 13.4 Number information used for routing
+
+The exchange which initiates a dialogue using the GT translation mechanism shall give an E.164 address as GT in the SCCP calling address field which will uniquely identify it. For routing on the international interface, the number information used for GT translation shall comply to the E.164 numbering schemes for Country code and National destination code.
+
+## 14 VPNTransport – Formats and codes of application data
+
+The following defines the formats and codes for the support of the VPN application for the support of PSS1 information flows as an APM-user. The information structure defined here is passed as Application Data to the underlying transport mechanism (APM) in the APM\_U\_Data primitive. The Application Context Identifier field of the Application Transport Parameter (APP) shall be coded "PSS1 ASE (VPN)".
+
+The Encapsulated Application Information field within the APP and the VPNTransport are coded identically. The format is such that it can provide a service of transparent transport of information (see 14.1) as well as having the ability of passing additional network related information (see 14.2) within the public network. The Application information is structured such that the first octet is a pointer to the PSS1 information to be transported transparently (see 14.1). The pointer value (in binary) gives the number of octets between the pointer octet itself (included) and the first octet (not included) of transparent PSS1 data. The pointer value of zero is used to indicate that, no transparent PSS1 data is present. The range of octets between the pointer octet and the first octet of
+
+transparent PSS1 data (to which the pointer octet points) contains the network related information (see 14.2) to be passed between VPN applications residing within the public network.
+
+### 14.1 Private network specific information elements to be transported within the Application Transport Parameter
+
+The transparent transport of PSS1 information flows within the APP is achieved by transporting the information elements in Table 27.
+
+**Table 27/Q.765.1 – Information elements transported within the APP**
+
+| Information Element | Ref. | Type | Length |
+|------------------------------------------------------------------------------|-------------------|------|--------|
+| Calling party number | [2]/[21] (Note 1) | O | 4-* |
+| Called party number | [2]/[21] (Note 1) | O | 4-* |
+| Connected number | [2]/[21] (Note 1) | O | 4-* |
+| Facility with protocol profile value set to "Networking extensions" (Note 2) | [3]/[22] (Note 1) | O | 3-* |
+| Notification indicator (Note 2) | [3]/[22] (Note 1) | O | 3-* |
+| Locking Shift | [3]/[21] (Note 1) | O | 1 |
+| Non-locking Shift | [3]/[21] (Note 1) | O | 1 |
+| Sending Complete | [2]/[21] (Note 1) | O | 1 |
+| Transit counter | [6]/[21] (Note 1) | O | 3 |
+
+NOTE 1 – The definition of these information elements by ISO/IEC [2]/[3]/[6] and by ITU-T [21]/[22] are identical and therefore equally applicable.
+NOTE 2 – These information elements may be repeated.
+NOTE 3 – The information elements carried in the Application Transport Parameter are taken into account whatever the order of receipt is with the exception of the Locking and Non-locking shift information elements which operate in the specific way.
+
+### 14.2 NNI specific information to be transported in the Application Transport Parameter
+
+The NNI specific information for the VPN application is carried within the APP in the following manner.
+
+| | | | | | | | | | | |
+|----|-------------|-------|----------------|---|-----|----|----|-----|--|--|
+| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | |
+| 1 | Ext. | Spare | CNID indicator | | SAI | GR | GT | VTI | | |
+| 2 | CNID length | | | | | | | | | |
+| 3 | CNID | | | | | | | | | |
+| : | | | | | | | | | | |
+| 14 | | | | | | | | | | |
+
+- a) VPN feature transparency indication (VTI)
+ - 0 No indication
+ - 1 Call with VPN feature transparency capability
+- b) Gateway PINX Transformation capability (GT)
+ - 0 No indication
+ - 1 PINX with Gateway transformation capability
+
+- c) Gateway PINX request indication (GR)
+ - 0 No indication
+ - 1 Gateway PINX transformation request
+- d) Setup Acknowledgement Indicator (SAI)
+ - 0 No indication
+ - 1 Setup acknowledgement
+- e) Corporate Telecommunications Network Identifier Indicator (CNID indicator)
+ - 00 Not included (Network option)
+ - 01 Network specific (Network option)
+ - 10 Global Value
+ - 11 Spare
+- f) Extension indicator (Ext)
+ - 0 Information continues through the next octet
+ - 1 Last octet
+- g) Corporate Telecommunications Network Identifier length (CNID length)
+
+
+Number of octets containing CNID
+
+When the CNID indicator is coded 00 "Not included", then CNID length is omitted
+- h) Corporate Telecommunications Network Identifier (CNID)
+
+
+Binary value
+
+When the CNID indicator is coded 00 "Not included", octets 3-14 are omitted.
+
+When the CN indicator is set to "global", the CN identifier contains the binary representation of the CN identifier. The CN identifier starts with the BCD (Binary Coded Decimal) representation of the E.164 country code digits of the country where the CN was initially assigned. The remainder of the CN identifier is country specific.
+
+## 15 Timers
+
+This clause specifies all the Application Process and Protocol timers relevant for VPN applications. For each timer the time-out value, cause or initiation of that timer, normal termination event(s) for the timer, and actions to be performed on expiry of the timer, are given. Furthermore, in the last column reference to the relevant Application Process description, or ASE description, is given, where a full description of the procedure is to be found.
+
+### 15.1 Timers in TC-user
+
+See Table 28.
+
+**Table 28/Q.765.1 – Timers in TC-user**
+
+| Symbol | Time-out value | Cause for initiation | Normal termination | At expiry | Reference |
+|--------|------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|-----------|
+| T1 | 1-5 sec | Sending of SETUP.Invoke | Reception of SETUP.ReturnResult | Abort dialogue
Send TC-U-ABORT
Inform management function | 11.4.3.1 |
+| T2 | 1-5 sec | Sending of ActivityTest.invoke | Reception of ActivityTest.ReturnResult | Abort dialogue
Send TC-U-ABORT
Inform management function | 11.4.3.2 |
+| T3 | 10-60 min | Reception of Setup.ReturnResult
Connect.Invoke
VPNFacility.Invoke
ActivityTest.ReturnResult
Sending of VPNFacility.Invoke | Reception of Connect.Invoke
VPNFacility.Invoke
Release.Invoke
Sending of ActivityTest.Invoke | Send ActivityTest.Invoke | 11.4.3.3 |
+| T4 | 10-60 min
(Note T4 must be greater than T3) | Reception of VPNFacility.Invoke
Sending of Setup.ReturnResult
Connect.Invoke
VPNFacility.Invoke
ActivityTest.ReturnResult | Reception of ActivityTest.Invoke
Sending of Connect.Invoke
VPNFacility.Invoke
Release.Invoke | Abort dialogue
Send TC-U-ABORT
Inform management function | 11.4.3.4 |
+
+
+
+# ITU-T RECOMMENDATIONS SERIES
+
+- Series A Organization of the work of the ITU-T
+- Series B Means of expression: definitions, symbols, classification
+- Series C General telecommunication statistics
+- Series D General tariff principles
+- Series E Overall network operation, telephone service, service operation and human factors
+- Series F Non-telephone telecommunication services
+- Series G Transmission systems and media, digital systems and networks
+- Series H Audiovisual and multimedia systems
+- Series I Integrated services digital network
+- Series J Transmission of television, sound programme and other multimedia signals
+- Series K Protection against interference
+- Series L Construction, installation and protection of cables and other elements of outside plant
+- Series M TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits
+- Series N Maintenance: international sound programme and television transmission circuits
+- Series O Specifications of measuring equipment
+- Series P Telephone transmission quality, telephone installations, local line networks
+- Series Q Switching and signalling**
+- Series R Telegraph transmission
+- Series S Telegraph services terminal equipment
+- Series T Terminals for telematic services
+- Series U Telegraph switching
+- Series V Data communication over the telephone network
+- Series X Data networks and open system communications
+- Series Y Global information infrastructure
+- Series Z Programming languages
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.766-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.766-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6dc25a442f8f5a40c50db8d49bf8a3aa117ceaa1
--- /dev/null
+++ b/marked/Q/T-REC-Q.766-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:94533211da22eb461c78639db7437dfa6ab7735b048f94babcd006fb4eb604bb
+size 8203
diff --git a/marked/Q/T-REC-Q.766-199303-I_PDF-E/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg b/marked/Q/T-REC-Q.766-199303-I_PDF-E/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0981915d144422380e5240318dd48e89c5798272
--- /dev/null
+++ b/marked/Q/T-REC-Q.766-199303-I_PDF-E/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:037ed98c02b7b065956e93ffbdf98807c0bf56e6abb408be9eeb57bfb82381c8
+size 41290
diff --git a/marked/Q/T-REC-Q.766-199303-I_PDF-E/raw.md b/marked/Q/T-REC-Q.766-199303-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..064afcb22521fc008f0f7c5d8d6f07a97b9f6383
--- /dev/null
+++ b/marked/Q/T-REC-Q.766-199303-I_PDF-E/raw.md
@@ -0,0 +1,213 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**Q.766**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(03/93)
+
+**SPECIFICATIONS OF SIGNALLING SYSTEM No. 7
+ISDN USER PART**
+
+---
+
+**PERFORMANCE OBJECTIVES
+IN THE INTEGRATED SERVICES
+DIGITAL NETWORK APPLICATION**
+
+**ITU-T Recommendation Q.766**
+
+(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.766 was revised by the ITU-T Study Group XI (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993).
+
+# --- NOTES
+
+1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector.
+
+In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms "CCITT, CCIR or IFRB" or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure.
+
+2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+# CONTENTS
+
+*Page*
+
+| | | |
+|-----|----------------------------------------------------------------|---|
+| 1 | Introduction ..... | 1 |
+| 2 | Signalling availability ..... | 1 |
+| 2.1 | Signalling route set availability ..... | 1 |
+| 2.2 | Signalling network availability ..... | 1 |
+| 3 | Signalling dependability ..... | 1 |
+| 3.1 | General ..... | 1 |
+| 3.2 | Probability of signalling malfunction ..... | 2 |
+| 4 | Signalling delay ..... | 2 |
+| 4.1 | Functional reference points and transfer time components ..... | 2 |
+| 4.2 | Delays ..... | 2 |
+| 4.3 | Answer delay ..... | 3 |
+| 4.4 | Influence of new ISDN applications on performance ..... | 3 |
+| 5 | Signalling system limitations ..... | 3 |
+| 5.1 | Labelling potential ..... | 3 |
+| 5.2 | Number of ISDN call identities at a signalling point ..... | 4 |
+| | References ..... | 4 |
+
+
+
+# **PERFORMANCE OBJECTIVES IN THE INTEGRATED SERVICES DIGITAL NETWORK APPLICATION**
+
+*(Malaga-Torremolinos 1984; modified at Helsinki, 1993)*
+
+# **1 Introduction**
+
+This Recommendation gives the requirements of the Integrated Services Digital Network (ISDN) application call control service supported by Signalling System No. 7 (SS No. 7).
+
+The MTP supports the ISDN application of Signalling System No. 7. In Recommendation Q.706, the Message Transfer Part (MTP) performance is described. The provision of a signalling network to support the ISDN application must take account of the performance of the MTP and the requirements of the ISDN application. For example, taking account of the message transfer times in Recommendation Q.706 and the requirements for message transfer times between two ISDN exchanges, a figure may be derived for the total permissible number of signalling links in tandem for a particular call.
+
+The Recommendations E.721 [3] and I.352 [4] also relate to ISDN performance.
+
+# **2 Signalling availability**
+
+## **2.1 Signalling route set availability**
+
+The availability of a signalling route set is determined by the availability of the individual components of the signalling network (signalling links and the signalling points) and by the structure of a signalling network.
+
+The availability of a signalling route set (according to 1.1/Q.709) should not be less than 0.99998. This corresponds to a total downtime for a user signalling relation of ten minutes per year maximum.
+
+## **2.2 Signalling network availability**
+
+The availability of the signalling network should be sufficiently high as to meet the signalling route set downtime objectives stated in 2.1. The signalling network architecture selected will strongly influence the availability. In general, the greater the number of link sets in tandem in a signalling route set the more redundant signalling paths that will be needed to meet the availability objective for the signalling route set or user signalling relation.
+
+# **3 Signalling dependability**
+
+## **3.1 General**
+
+The ISDN application is different from other applications, such as telephony and data, in that there may be multiple paths involved for any given ISDN call. There may be several circuits (e.g. telephone conferencing) for either telephony or data and non-circuit related connections for access to data bases or for terminal-to-terminal control. This diverse set of uses may require closer control of the signalling network resources than might be required for other more simple applications.
+
+### **3.1.1 Probability of false operation**
+
+By means of error detection (see Recommendation Q.703) as well as transmission fault indication (see Recommendations G.732 [1] and G.733 [2]), it is ensured that, overall, not more than one in $10^8$ of all signal units transmitted is accepted that, due to errors, will cause false operation.
+
+## 3.2 Probability of signalling malfunction
+
+Unsuccessful calls may be caused by undetected errors, loss of messages, or messages delivered out of sequence (during emergency situations within the signalling network) and may result in:
+
+- incomplete call set-up;
+- misrouted calls (e.g. connection of wrong numbers);
+- calls routed correctly but mishandled (e.g. false clearing);
+- inability to access a data base.
+
+Considering the above conditions and the performance for the MTP, no more than 2 in $10^5$ (provisional value) of all ISDN calls should be unsuccessful due to signalling malfunction.
+
+NOTE – No more than 1 in $10^5$ of all ISDN circuit connections should be unsuccessful due to signalling malfunction.
+
+# 4 Signalling delay
+
+## 4.1 Functional reference points and transfer time components
+
+Figure 1 shows the time components associated with the handling and transfer of ISUP messages at a transit exchange.
+
+
+
+The diagram illustrates the flow of an ISUP message through seven functional blocks representing different layers of the signalling system. The blocks are arranged horizontally and labeled from left to right: 'Signalling data link functions (Level 1)', 'Signalling link functions (Level 2)', 'Signalling message handling functions (Level 3)', 'User functions (Level 4)', 'Signalling message handling functions (Level 3)', 'Signalling link functions (Level 2)', and 'Signalling data link functions (Level 1)'. Three time intervals are indicated by double-headed arrows below the blocks: $T_{mr}$ spans from the start of Level 2 to the start of Level 4; $T_{hu}$ spans from the start of Level 4 to the start of the second Level 3; $T_{ms}$ spans from the start of the second Level 3 to the start of the final Level 1. The total duration from the start of the first Level 2 to the start of the final Level 1 is labeled $T_{cu}$ . A small code 'T1158690-94/d01' is visible in the bottom right corner of the diagram area.
+
+Diagram of transit exchange cross-office transfer time components showing seven levels of functions and three time intervals: T\_mr, T\_hu, and T\_ms, with the total T\_cu.
+
+FIGURE 1/Q.766
+Transit exchange cross-office transfer time components
+
+## 4.2 Delays
+
+$T_{mr}$ and $T_{ms}$ are defined in 4.3.2/Q.706.
+
+### 4.2.1 cross-office transfer time, $T_{cu}$
+
+$T_{cu}$ is the period which starts when the last bit of the signal unit leaves the incoming signalling data link and ends when the last bit of the signal unit enters the outgoing signalling data link for the first time. It includes the user handling time $T_{hu}$ . It also includes the queuing delay in the absence of disturbances but not the additional queuing delay caused by retransmission. It does not include the data channel propagation time.
+
+### 4.2.2 user handling time, $T_{hu}$
+
+$T_{hu}$ is the period which starts when the last bit of the message has entered the upper layer functions and ends when the last bit of the derived message has left the upper layer functions.
+
+### 4.2.3 Objectives for cross-office transfer time, $T_{cu}$
+
+The figures in Table 1 are the objectives for the cross-office transfer time $T_{cu}$ for the ISDN signalling points in the signalling network. These figures are related to a signalling bit rate of 64 kbit/s.
+
+TABLE 1/Q.766
+
+#### **Transit exchange cross-office transfer time, $T_{cu}$ 1)**
+
+| Message type | Exchange call attempt loading | $T_{cu}$ (ms) | |
+|---------------------------------|-------------------------------|---------------|-----|
+| | | Mean | 95% |
+| Simple (e.g. answer) | Normal | 110 | 220 |
+| | +15% | 165 | 330 |
+| | +30% | 275 | 550 |
+| Processing intensive (e.g. IAM) | Normal | 180 | 360 |
+| | +15% | 270 | 540 |
+| | +30% | 450 | 900 |
+| 1) Provisional values. | | | |
+
+Delays concerning data base query functions are not included at this time. The delays corresponding to those functions are for further study.
+
+A processing intensive message is one that arrives at an exchange and requires detailed examination (and possibly modification) before it is transmitted to the next exchange.
+
+A simple message is one that requires little or no examination or modification (typically only label translation) before it is transmitted to the next exchange.
+
+## 4.3 Answer delay
+
+As a consequence of correction by retransmission, not more than one in $10^4$ signals should be delayed more than 300 ms as a long-term average. This requirement refers to each signalling link.
+
+This requirement is laid down in order to ensure satisfactory answer delays.
+
+Further study is required to determine if this value is sufficient if satellite working is used.
+
+## 4.4 Influence of new ISDN applications on performance
+
+Delays relating to data base query functions have not been included. These delays, and the relationship between them are for further study, but information relating to these delays can be found in 7/Q.709.
+
+If the load on the links is mixed with messages of significantly different lengths (e.g. from other User Parts) then the increase in the outgoing link delay $T_{od}$ as shown in 5/Q.706, has to be taken into consideration. If satellite links are used in this case, the relevant increase is shown in 3/Q.706.
+
+# 5 Signalling system limitations
+
+## 5.1 Labelling potential
+
+### 5.1.1 Signalling points
+
+The label of the SS No. 7 for the ISDN application provides the potential to identify 16 384 signalling points.
+
+### 5.1.2 Number of circuits in a user signalling relation
+
+There may be up to 4096 circuits (4096 channels in each direction) for each user signalling relation.
+
+### **5.1.3 Number of SCCP connections in a user signalling relation**
+
+There may be up to $2^{24}$ SCCP connections available at an ISDN signalling point. All of these may be available for any given user signalling relation, but must be shared over all signalling relations.
+
+## **5.2 Number of ISDN call identities at a signalling point**
+
+There may be up to $2^{24}$ (value for further study) simultaneous ISDN calls at a signalling point with the $2^{24}$ call identities available. The use of ISDN call identities is for further study.
+
+# **References**
+
+- [1] CCITT Recommendation *Characteristics of primary PCM multiplex equipment operating at 2048 kbit/s*, Rec. G.732.
+- [2] CCITT Recommendation *Characteristics of primary PCM multiplex equipment operating at 1544 kbit/s*, Rec. G.733.
+- [3] CCITT Recommendation *Network GOS parameters and target values for circuit-switched services in the evolving ISDN*, Rec. E.721.
+- [4] CCITT Recommendation *Network performance objectives for connection processing delays in an ISDN*, Rec. I.352.
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/057e0fadbc74743547d314f6fd0ff686_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/057e0fadbc74743547d314f6fd0ff686_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8e3dda4f8e46b8d24e1f66f69638a79ad64467ce
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/057e0fadbc74743547d314f6fd0ff686_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:52076e9c2791e069bd6e1524b7ecad18d402240a8aeb3ea07df0aa425025dfcd
+size 216281
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..baee4307b5cc9b209a451c49ce7f06624e425d89
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6d39db465bb356bb60f6916369a0cb2478ea2af0c8cca0d157f0f2107f95087c
+size 157431
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/0d24f2158deb9583a562cd9a81579e9e_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/0d24f2158deb9583a562cd9a81579e9e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..207b1688691538f941aaed97d433d4575641a781
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/0d24f2158deb9583a562cd9a81579e9e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:61bcff8e33bf912fa1e439a527d211f2da4956797778562a0604ab294a867816
+size 209929
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a8882a108592ff4252249fdd02774ce43d1d98bd
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:566a53801b3ceccc6f5451c44d5949efed86ce2cafccdd066def7e5fe6f0e1cd
+size 27718
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/0fca2efbeef5c006cbab2fd86aca84d8_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/0fca2efbeef5c006cbab2fd86aca84d8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..54ef4dd45af31606ff7124158a1d04b8b8d50aab
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/0fca2efbeef5c006cbab2fd86aca84d8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:82237e5d8da28cca9dc03bdc88d5e53505c3a66b267ae4a25df372b61282fd19
+size 145794
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d263fd64538603afc9e74c6115b476fe56f3e5b2
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:80ef078f665f3d2a0f1d2c7ee0b913f7772159538d67c958685a95d46603819c
+size 39979
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/2171e482ce2956fa624f1d51098d5ac9_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/2171e482ce2956fa624f1d51098d5ac9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..536e1ddaf1072b9d940595666309af60348cadb1
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/2171e482ce2956fa624f1d51098d5ac9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9302a7dbeb7121ca363bb1dcca6f5118ad26f01ef75e0d1c1bb20a5f3f1daaad
+size 228879
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/255efa1d461fc79b4ed367aaec11637f_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/255efa1d461fc79b4ed367aaec11637f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e7e3ae1537d9d1b022d3b15613a8284ac6c5dff2
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/255efa1d461fc79b4ed367aaec11637f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b6eb14310a4c1264aa0aaa29b5a1b16bdcc5f9eab87d79089cd82290fe6267df
+size 156842
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/2bcc7de24074ca97717d10c8c4bfe3ba_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/2bcc7de24074ca97717d10c8c4bfe3ba_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..546e93209e89b2b26e25cb5bae06262520b6dd2d
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/2bcc7de24074ca97717d10c8c4bfe3ba_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:219e8ef30e6ee20fbcf2c097ad8bb018d5e9139c65f279604e04e1f5fd26189d
+size 194336
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4eb5559e66fcdb4d86474f432ddb74d2ccaffe41
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c0fc6466e55745a7f7c2019d9af5274c4b139d123652eec2f1d2dcd7c41e635
+size 28517
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a7da83ecb82b51a4cef7694858eef2c35f1986ff
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d77a478c5b78d330a2a6abbd32e7d0ac053d8b9c1ffe8a96476214afa6ddf7ae
+size 8196
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/33859177822cce0c1b03fd3d37de14f6_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/33859177822cce0c1b03fd3d37de14f6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3fb8510f605555aab104482046f591e53d508d0c
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/33859177822cce0c1b03fd3d37de14f6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8a8927bf6ce8bd4c89a3b6fa6fe3e44b75f93ef29c0183d00e4f7743a9b50616
+size 169328
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f9a83befa4497316ea4550c1c307719cae58f904
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eefa992733d11f248c3bd9176fda846927330068c695d0a8160643b5bad1fb4b
+size 150150
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/3c99312f83459559d9a301148555d7b9_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/3c99312f83459559d9a301148555d7b9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..082febe85886f4843ea31b5566fa5e253d2d6e98
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/3c99312f83459559d9a301148555d7b9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:de04c3fb4c12084b3de4dbe2f14b1e09914a99191796ec06570b13c537d84dab
+size 163677
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/40135f3a8f5a6789225806e70870256d_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/40135f3a8f5a6789225806e70870256d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0c5fd8d2aff4b3c4578730dcabeeb0debdca27c8
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/40135f3a8f5a6789225806e70870256d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e2c95037c95e089df1e82d062761611dc5143c12ac3680282c9e946ae72790c3
+size 234500
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/408c4798ea60469e0728a7cbbd598668_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/408c4798ea60469e0728a7cbbd598668_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d468cd0f8b2e7599e704447398eb41035dbbaf98
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/408c4798ea60469e0728a7cbbd598668_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:80363c7a32688fdd0357026dc63d6988e78a2331b922464b4f47da34a6519d99
+size 155201
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/40ebe9179df298f1b6d76822f28d90aa_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/40ebe9179df298f1b6d76822f28d90aa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..50e3faf65a100b1cbfacc7988b9f3e009a86c5a8
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/40ebe9179df298f1b6d76822f28d90aa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:12214f554f40647467f18caf4e84d0d059eb80705358f254d6eed245b89b616a
+size 161603
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7fc788dc3bfccf9c3bf8d71958b00462fa87c2c1
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:173f92398bc0ecf7cc615f0015f63dfda50c706f58a0294a70f9e0a4e1054935
+size 45564
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d42b20efa5b2685730707a169c39c839e0e83be6
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f836bec4a292ae3bc177f118eb8c18d701325dd364249309e3599b2696baf63a
+size 144585
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..20b27e6fe54176704d97ebea9c9de1cafc494d55
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d946542b3db7ecdf91b319f29c531cea18fb80b48025f55efeadd25b9b928d14
+size 27802
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/4842f073775fb1e84d101c02fd74e59e_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/4842f073775fb1e84d101c02fd74e59e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7b6461f7b5e405d9fb411238a5c0e2d6d2fa3ea1
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/4842f073775fb1e84d101c02fd74e59e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1da523f6e938589ff8b63a358e91ee68e2e071456ee973a4c361772ad96dce27
+size 179653
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/4847c98185bc52e8786b78738bc52b45_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/4847c98185bc52e8786b78738bc52b45_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1a2a9ad6b965f72b18749479a9813966b1b3487c
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/4847c98185bc52e8786b78738bc52b45_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7be12fa855a043355e75f88a31bf556b55346731a09aa59645aefc6aafdfcefc
+size 152955
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/4a2cf844c794745df47d39c6f7aee42b_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/4a2cf844c794745df47d39c6f7aee42b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8784ad29b76c62990fe6930322146aa062da7c82
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/4a2cf844c794745df47d39c6f7aee42b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6c777872067c6f3b2a00c5c77e28b40b33df7cec8773e04bc4fb24eabd7e2be7
+size 147587
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/4a5e39746c38baaf73cbecd5aaba9afb_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/4a5e39746c38baaf73cbecd5aaba9afb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c2498fddfd068ef568fce9b1d20e9313fe693133
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/4a5e39746c38baaf73cbecd5aaba9afb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b441ef4383e6ee975a308e620aae45789b80581444678d9d9c7b6f2804c3cbcb
+size 192241
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/4c4cd9cc5afb43f9e3111e1ba45e701a_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/4c4cd9cc5afb43f9e3111e1ba45e701a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7eb5d47b94a49b60028a29093359fadc8aa064eb
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/4c4cd9cc5afb43f9e3111e1ba45e701a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e24d6359dc3f614fa80fb3194b0aa09fb165b2f04cb61843bf977ec33ad7017
+size 94618
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/51501a01b2c29ac95e126882508f8831_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/51501a01b2c29ac95e126882508f8831_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b0f01a1b8d9c13e75451f41fc1f32bedfb1e723d
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/51501a01b2c29ac95e126882508f8831_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8357d68647dbcf9226fc5b9c2b4c9167441bfb680a0321980e03d691e60ea348
+size 126349
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/52c40e2f443985dc63f45dec57d90c8c_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/52c40e2f443985dc63f45dec57d90c8c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1122e80ea0617380edf3d33bfee3724af471894c
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/52c40e2f443985dc63f45dec57d90c8c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:37607fb9c09e7b166c52f38470bb4fbb141b067120775ad576842b102d1899c3
+size 192492
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/5e787be3a9da44aa97f5fcdcd41c0123_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/5e787be3a9da44aa97f5fcdcd41c0123_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..79eb940bf2c92b79dd6100bc7607d42ee34efbc4
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/5e787be3a9da44aa97f5fcdcd41c0123_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:898bededf2011bed4200368f3c5c0c354ee4321cd6049365b643da8cb7c430c4
+size 146651
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/60b089b85e598003112e72e9d4f19c5c_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/60b089b85e598003112e72e9d4f19c5c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7b7891a4e087f519674b1cd31a4d2d325cde3eb7
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/60b089b85e598003112e72e9d4f19c5c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a4cb47dac9dca4026e0ec3bc9d3168af85a9035cb3794fa38e08a66b51bdce5
+size 177405
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/6470d350326789d5306eabcb76533951_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/6470d350326789d5306eabcb76533951_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..70d1675846b3897966d935486dfd88145f6c9f2c
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/6470d350326789d5306eabcb76533951_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3663f1555599d8edfcbcdc75d1f68ee53c3b2197f46fd4f8687043423d4e3133
+size 146808
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/6ab36474772ce6a61e97fd5d19770270_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/6ab36474772ce6a61e97fd5d19770270_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ebd39ced6667a563af8ce62e14f3420f94b62936
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/6ab36474772ce6a61e97fd5d19770270_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c0c0306e09455a675bc1c8305a9cc52fd682559bf66c9709ee94a84188f148d7
+size 157374
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/6f7323b820d2c28a31e1161ca131cf03_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/6f7323b820d2c28a31e1161ca131cf03_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1687dd4a4239759a5281fb89ede1de9a67fd8000
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/6f7323b820d2c28a31e1161ca131cf03_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d6388651c7d04fa23275619c078b35579b38a94e68e802949d5793e1b7b6b918
+size 159262
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/768662ed52466041c8f43e005b48f501_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/768662ed52466041c8f43e005b48f501_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cd13d5a1c142ec1fbf6948a460898b79e65f9731
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/768662ed52466041c8f43e005b48f501_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:63da8ab3761aa6c5f96af03690b405c50303aa0a433f8b7b31016c740077e8ff
+size 162762
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..23b61e247aa6eba4b3146c123ef6f91bbf0910e3
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc5126b7962cb6752da7dce8c8db1dfd55601c30fa24bef044c2025c5ccf823d
+size 26907
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/78151e5dd542eada99ead8203dfce76b_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/78151e5dd542eada99ead8203dfce76b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..531ac4b39a6e1345b33de9a37cc1622876f928bc
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/78151e5dd542eada99ead8203dfce76b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:691d3a9588f5da674516681099c1c73c1f120856a4270bf0005113819a443cb6
+size 169212
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/7beca7f8804a7b96d70e59e4b9034085_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/7beca7f8804a7b96d70e59e4b9034085_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..788ea90a2b82e8306e795ecdbc73658720933c4d
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/7beca7f8804a7b96d70e59e4b9034085_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d59dc6c613464ca054b22a4530d5e6b7068db4b4d7c99440e47d6314ca126427
+size 250548
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/82fbb97c1145cac89ac72dd080fad17a_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/82fbb97c1145cac89ac72dd080fad17a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8f1970373a1d829dad7f35ca7def969afef47fce
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/82fbb97c1145cac89ac72dd080fad17a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b9dde94de3e28d937de55fb924a38118a345089d194f555984c2cafe8b42db33
+size 143346
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/834fb96b114b8fdc001625e1ae28e8b1_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/834fb96b114b8fdc001625e1ae28e8b1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..56677164e691e2fa847e842cdba893d754f34485
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/834fb96b114b8fdc001625e1ae28e8b1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5796398c2e6cb28c1c7be1f1fc14c52526bd5515ee38d647aa297d2a60fb6a3e
+size 143304
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/86bd357c573c9696393f5bde4d4cce4f_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/86bd357c573c9696393f5bde4d4cce4f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..722253e2a0b783242bd8607656373fb1237a45fb
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/86bd357c573c9696393f5bde4d4cce4f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8fd7648b272fc7b0987ddcfcf8ff02e1aa2dfa85329f4d5fd7ac827195cd35d4
+size 137964
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/89d5117b5c8c5209f100f1f0bf8ef540_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/89d5117b5c8c5209f100f1f0bf8ef540_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aa44747a1b68b5c721add05e9a93571eace6e7c5
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/89d5117b5c8c5209f100f1f0bf8ef540_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:58d2d8268dc9e335cc02922867da3ce6facb7ce1fc80ca819efc3e0da88640cf
+size 157815
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8a8df40b66a75c77373f7e3ca649828e238ab0c4
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6edbb2a43b98b0118de5cd762ba7c083feab08a94c209406252231a23c8a7f24
+size 57117
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2066df7d273dff4cca99eabc10d6f9370f591a11
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:560e624f9c5f20d2218168ce5a77d774bfe6abee0a797c0bdf802b1996ee5dfd
+size 27300
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/a0bf1e4e2765bf05e8009f39007df772_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/a0bf1e4e2765bf05e8009f39007df772_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..06128ebfd4b9b1d38a6ccff90a32c60900f1f6ca
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/a0bf1e4e2765bf05e8009f39007df772_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2ed83439222c883b2052848cb3ad94406726d6ff06c059e0958756af3a43743b
+size 187442
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/a4bfa2343d75076b79f7e33d93915e00_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/a4bfa2343d75076b79f7e33d93915e00_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c45535ebe76dac5e4beb0071c60d056969547c9f
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/a4bfa2343d75076b79f7e33d93915e00_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e110028709a538b40a0b6c3e84d99c469ca85b0c72b964a52cf4d39cc3e99c43
+size 188634
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..78072d72a1497934ac4d8ef097eea80ab9a9a2f1
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/b235edb1dbe659e2782c9a0e47775ca4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cecf0b9871310170c1fbdbdfd9d4f5e3500af14a779fa3063fe404d5b3973123
+size 166241
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/b43ec8e53bbe827c4572d9fd80ebc21a_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/b43ec8e53bbe827c4572d9fd80ebc21a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1936108fc38ebfa7d490146388c166de0ff4bea6
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/b43ec8e53bbe827c4572d9fd80ebc21a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e0dd0e3a5b18dc7f699db1036cf3099c6690503e6c2b03004219485a9e68884
+size 177914
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/b4cbe4bfe7868be70d1549b983749783_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/b4cbe4bfe7868be70d1549b983749783_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a7f4d1110d01639a83d94de716de3421e6b9ef09
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/b4cbe4bfe7868be70d1549b983749783_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ad77f23d8120b62f3c2f5358fca9532135f842dddbf34f6b7b318517871f180e
+size 157493
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/c916a9fb4d2c440522379dedf3f76119_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/c916a9fb4d2c440522379dedf3f76119_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d6a21db54fb199ba1b6c5da5a36027dab53423b1
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/c916a9fb4d2c440522379dedf3f76119_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:23c9301cf77cbcd7214179246e0a4c8056b6a3bbdcf3553c642be2e39d595b45
+size 59095
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/cb86a44ccb06c552d4c8c1d8374aaeae_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/cb86a44ccb06c552d4c8c1d8374aaeae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5f7650d5248cc1577f8d700eb0c7f666d20961aa
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/cb86a44ccb06c552d4c8c1d8374aaeae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5e4796cf44c16970f9104cad893011d3d947a1d872d418adc817933663d417ce
+size 176655
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/cfb616f789aa01c087849ad7701e64d7_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/cfb616f789aa01c087849ad7701e64d7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..be51893097cc66b9f1d5a9a7ff623acd2b1ea321
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/cfb616f789aa01c087849ad7701e64d7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e14ff436c05196180da3b91ec9266edebfcbafcf4b3ed1c3ec841986fc5ecfd6
+size 158075
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/d0dd433695a01d364ac98f846f68bc8f_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/d0dd433695a01d364ac98f846f68bc8f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c14c609f270a173c98bab87d20f1d960252d7cea
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/d0dd433695a01d364ac98f846f68bc8f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:705208770bbdc6e94a30e5dae10786ff605ac0494077dabbdd7fe578644fc5f8
+size 228636
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/d36508ae73a5197d96f5c0773261515a_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/d36508ae73a5197d96f5c0773261515a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a1cbd08b5c12d6a0d917f6400cce6ef4a522b8da
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/d36508ae73a5197d96f5c0773261515a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bc7516f2aa2c35dfef00a5185b1a00d22fb8f9e127c41d4cd9401847ec32dd05
+size 122230
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8ee5d64aff5c3fe197390f6faa46c1c779281afb
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e8e9699754d5f3e4790d0042625648136702a101e6f8824be2bd9b1fa3cc091b
+size 29688
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3a35ae4c7fdb28cf44e5ce038ad4933978ca2992
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2eb20544351d5c21ac656f4acbe7088b314b59481d399ed796a55131268f7f2a
+size 27603
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/e05434e963901d7e9c0bf5a6758200ed_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/e05434e963901d7e9c0bf5a6758200ed_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0d9aa9ece70e537b10682fd80c91a30d3e547dbd
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/e05434e963901d7e9c0bf5a6758200ed_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f0c389968610e8b00ebe90472c78d4d17ac8e4558136d90770c483523b010903
+size 141378
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/e38f0349f1b6094626cbfeab7105f029_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/e38f0349f1b6094626cbfeab7105f029_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..85860b9084e72e90f6ec1ddda0af52fca07cb1fc
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/e38f0349f1b6094626cbfeab7105f029_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:54a4c9bc68eb226bce588ec172d7aed8ad598dea09e036d7665bc600c94a59f0
+size 149134
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/ea86187ab53b9415c91cce31d7c7626a_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/ea86187ab53b9415c91cce31d7c7626a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8f6aa53faaee8e2493c022984e6d01ecdf973023
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/ea86187ab53b9415c91cce31d7c7626a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:222242de9b6f3bc5806457d6f58f041e7b45a1203139197afc6202484fd67bc7
+size 117259
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/f0a97d0d3818a253c1d2a009966081b1_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/f0a97d0d3818a253c1d2a009966081b1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..656b9d85e1a7abadd969f8ab16cc3d9c60742b9f
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/f0a97d0d3818a253c1d2a009966081b1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c678f4a09d5286a46b810d1de8c292bdad0a3244643b42328fb1d6d934a81ed2
+size 150013
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/f18e5c74883bf40027b353a61ffc3f9f_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/f18e5c74883bf40027b353a61ffc3f9f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2be4e558efc0d2a9ee63e8d3cce20589e9862580
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/f18e5c74883bf40027b353a61ffc3f9f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:abc86c11681fd4acc4095f8cd44fcb65425d043270855192f970b77ff65324ba
+size 154273
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg b/marked/Q/T-REC-Q.788-199706-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ec052b856ff811a45a9aa130ef16595d856dae5b
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5ef41302d32ec17b32fa16e2722cf47d841ba1871f4ec4f31046d2a6b36d9d89
+size 145742
diff --git a/marked/Q/T-REC-Q.788-199706-I_PDF-E/raw.md b/marked/Q/T-REC-Q.788-199706-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c8aae84035dc203bcd44ec1803c8684335d37188
--- /dev/null
+++ b/marked/Q/T-REC-Q.788-199706-I_PDF-E/raw.md
@@ -0,0 +1,7564 @@
+
+
+
+
+ITU logo: A globe with the letters ITU and a lightning bolt.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.788**
+
+(06/97)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Specifications of Signalling System No. 7 – Test
+specification
+
+---
+
+**User-network-interface to user-network-
+interface compatibility test specifications for
+ISDN, non-ISDN and undetermined accesses
+interworking over international ISUP**
+
+ITU-T Recommendation Q.788
+
+(Previously CCITT Recommendation)
+
+---
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## **SWITCHING AND SIGNALLING**
+
+| | |
+|------------------------------------------------------------|--------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 |
+| General | Q.700 |
+| Message transfer part (MTP) | Q.701–Q.709 |
+| Signalling connection control part (SCCP) | Q.711–Q.719 |
+| Telephone user part (TUP) | Q.720–Q.729 |
+| ISDN supplementary services | Q.730–Q.739 |
+| Data user part | Q.740–Q.749 |
+| Signalling System No. 7 management | Q.750–Q.759 |
+| ISDN user part | Q.760–Q.769 |
+| Transaction capabilities application part | Q.770–Q.779 |
+| Test specification | Q.780–Q.799 |
+| Q3 interface | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| General | Q.850–Q.919 |
+| Data link layer | Q.920–Q.929 |
+| Network layer | Q.930–Q.939 |
+| User-network management | Q.940–Q.949 |
+| Stage 3 description for supplementary services using DSS 1 | Q.950–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+
+For further details, please refer to ITU-T List of Recommendations.
+
+## **ITU-T RECOMMENDATION Q.788**
+
+# **USER-NETWORK-INTERFACE TO USER-NETWORK-INTERFACE COMPATIBILITY TEST SPECIFICATIONS FOR ISDN, NON-ISDN AND UNDETERMINED ACCESSES INTERWORKING OVER INTERNATIONAL ISUP**
+
+## **Summary**
+
+This Recommendation contains the User-Network Interface (UNI) to UNI testing principles and test specifications for interworking ISDN, non-ISDN and undetermined accesses over international ISUP (ISUP'92 or Q.767).
+
+It is intended for tests with ISUP'92, but it is also applicable for combinations between ISUP'92 and ISUP Q.767. For the test scripts, an informal description method is used.
+
+### **Source**
+
+ITU-T Recommendation Q.788 was revised by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 5th of June 1997.
+
+## FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
+
+The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+### NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+### INTELLECTUAL PROPERTY RIGHTS
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, the ITU had/had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 1998
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+## CONTENTS
+
+| | | Page |
+|-----|-------------------------------------------------|-------------|
+| 1 | Scope ..... | 1 |
+| 2 | References ..... | 1 |
+| 3 | Terminology ..... | 4 |
+| 3.1 | Definitions ..... | 4 |
+| 3.2 | Abbreviations ..... | 4 |
+| 4 | Objective of the test specification ..... | 6 |
+| 5 | Scope of UNI-to-UNI compatibility testing ..... | 7 |
+| 6 | General principles of UNI-to-UNI tests ..... | 8 |
+| 6.1 | General pre-test conditions ..... | 8 |
+| 7 | Test environments ..... | 9 |
+| 8 | UNI-to-UNI Compatibility Test List ..... | 12 |
+
+
+
+### Recommendation Q.788
+
+# USER-NETWORK-INTERFACE TO USER-NETWORK-INTERFACE COMPATIBILITY TEST SPECIFICATIONS FOR ISDN, NON-ISDN AND UNDETERMINED ACCESSES INTERWORKING OVER INTERNATIONAL ISUP
+
+*(revised in 1997)*
+
+## 1 Scope
+
+This Recommendation contains User-Network-Interface (UNI) to User-Network-Interface test specifications required to verify the overall compatibility of ISDN, non-ISDN and undetermined accesses interworking over international ISUP between networks.
+
+UNI-to-UNI testing will assure that for each bit and octet of feature request that passes between an ISDN subscriber and the local exchange equivalent, information must be passed across the international ISUP (ISUP'92 or Q.767) interface. Therefore, the compatibility testing boundaries are extended beyond the existing ISC's international ISUP interfaces as currently specified in Recommendations Q.784 and Q.785. Furthermore, those Recommendations do not cover the interworking between ISDN, non-ISDN and undetermined access signalling. As international ISUP is implemented, testing to ensure the integrity of undetermined access and other embedded capabilities is also required.
+
+The test specifications in this Recommendation do not attempt to verify the interoperability of Terminal Equipment (TE) or to replace end-to-end service testing.
+
+It is assumed that DSS 1 and ISUP customer acceptance, and protocol validation testing (Q.784 for ISUP) of each network have been successfully completed. ISC-to-ISC circuit supervision testing per Recommendation Q.784 is also a prerequisite to these UNI-to-UNI compatibility tests.
+
+A given test specification from this Recommendation is only applicable when the networks can provide the information requested by the tests. Otherwise the test is limited to verifying the proper call disposition.
+
+## 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 current valid ITU-T Recommendations is regularly published.
+
+- [1] ITU-T Recommendation Q.118 (1993), *Special release arrangements*.
+- [2] CCITT Recommendation Q.699 (1988), *Interworking between the digital Subscriber Signalling System layer 3 protocol and the Signalling System No. 7 ISDN User Part*.
+- [3] ITU-T Recommendation Q.730 (1993), *ISDN supplementary services*.
+
+- [4] ITU-T Recommendation Q.731.3 (1993), *Stage 3 description for number identification supplementary services using Signalling System No. 7: Calling Line Identification Presentation (CLIP)*.
+- [5] ITU-T Recommendation Q.731.4 (1993), *Stage 3 description for number identification supplementary services using Signalling System No. 7: Calling Line Identification Restriction (CLIR)*.
+- [6] ITU-T Recommendation Q.731.5 (1993), *Stage 3 description for number identification supplementary services using Signalling System No. 7: Connected Line Identification Presentation (COLP)*.
+- [7] ITU-T Recommendation Q.731.6 (1993), *Stage 3 description for number identification supplementary services using Signalling System No. 7: Connected Line Identification Restriction (COLR)*.
+- [8] ITU-T Recommendation Q.731.7 (1997), *Stage 3 description for number identification supplementary services using Signalling System No. 7: Malicious Call Identification (MCID)*.
+- [9] CCITT Recommendation Q.731.8 (1992), *Stage 3 description for number identification supplementary services using Signalling System No. 7: Sub-addressing*.
+- [10] ITU-T Recommendation Q.732.2 (1993), *Stage 3 description for call offering supplementary services using Signalling System No. 7: Call forwarding busy*.
+- [11] ITU-T Recommendation Q.732.3 (1993), *Stage 3 description for call offering supplementary services using Signalling System No. 7: Call forwarding no reply*.
+- [12] ITU-T Recommendation Q.732.4 (1993), *Stage 3 description for call offering supplementary services using Signalling System No. 7: Call forwarding unconditional*.
+- [13] ITU-T Recommendation Q.732.5 (1993), *Stage 3 description for call offering supplementary services using Signalling System No. 7: Call deflection*.
+- [14] CCITT Recommendation Q.733.1 (1992), *Stage 3 description for call completion supplementary services using Signalling System No. 7: Call Waiting (CW)*.
+- [15] ITU-T Recommendation Q.733.2 (1993), *Stage 3 description for call completion supplementary services using Signalling System No. 7: Call Hold (HOLD)*.
+- [16] ITU-T Recommendation Q.733.4 (1993), *Stage 3 description for call completion supplementary services using Signalling System No. 7: Terminal Portability (TP)*.
+- [17] ITU-T Recommendation Q.734.1 (1993), *Stage 3 description for multiparty supplementary services using Signalling System No. 7: Conference calling*.
+- [18] ITU-T Recommendation Q.734.2 (1993), *Stage 3 description for multiparty supplementary services using Signalling System No. 7: Three-party service*.
+- [19] ITU-T Recommendation Q.735.1 (1993), *Stage 3 description for community of interest supplementary services using Signalling System No. 7: Closed User Group (CUG)*.
+- [20] ITU-T Recommendation Q.735.3 (1993), *Stage 3 description for community of interest supplementary services using Signalling System No. 7: Multilevel precedence and preemption*.
+
+- [21] ITU-T Recommendation Q.737.1 (1993), *Stage 3 description for additional information transfer supplementary services using Signalling System No. 7: User-to-User Signalling (UUS)*.
+- [22] ITU-T Recommendation Q.761 (1993), *Functional description of the ISDN user part of Signalling System No. 7*.
+- [23] ITU-T Recommendation Q.762 (1993), *General function of messages and signals of the ISDN user part of Signalling System No. 7*.
+- [24] ITU-T Recommendation Q.763 (1993), *Formats and codes of the ISDN user part of Signalling System No. 7*.
+- [25] ITU-T Recommendation Q.764 (1993), *ISDN user part signalling procedures*.
+- [26] CCITT Recommendation Q.767 (1991), *Applications of ISUP for international ISDN interconnections*.
+- [27] ITU-T Recommendation Q.780 (1995), *Signalling System No. 7 test specification – General description*.
+- [28] CCITT Recommendation Q.784 (1991), *ISUP basic call test specification*.
+- [29] CCITT Recommendation Q.785 (1991), *ISUP test specification for supplementary services*.
+- [30] ITU-T Recommendation Q.850 (1993), *Use of cause and location in the digital subscriber Signalling System No. 1 and Signalling System No. 7 ISDN user part*.
+- [31] ITU-T Recommendation Q.931 (1993), *ISDN user-network interface layer 3 specification for basic call control*.
+- [32] ITU-T Recommendation Q.939 (1993), *Typical DSS 1 service indicator codings for ISDN telecommunications services*.
+- [33] ITU-T Recommendation Q.950 (1993), *Digital Subscriber Signalling System No. 1 (DSS 1) – Supplementary services protocols, structure and general principles*.
+- [34] ITU-T Recommendation Q.951.3 (1993), *Stage 3 description for number identification supplementary services using DSS 1: Calling Line Identification Presentation (CLIP)*.
+- [35] ITU-T Recommendation Q.951.4 (1993), *Stage 3 description for number identification supplementary services using DSS 1: Calling Line Identification Restriction (CLIR)*.
+- [36] ITU-T Recommendation Q.951.5 (1993), *Stage 3 description for number identification supplementary services using DSS 1: Connected Line Identification Presentation (COLP)*.
+- [37] ITU-T Recommendation Q.951.6 (1993), *Stage 3 description for number identification supplementary services using DSS 1: Connected Line Identification Restriction (COLR)*.
+- [38] ITU-T Recommendation Q.951.7 (1997), *Stage 3 description for number identification supplementary services using DSS 1: Malicious Call Identification (MCID)*.
+- [39] CCITT Recommendation Q.951.8 (1992), *Stage 3 description for number identification supplementary services using DSS 1: Sub-addressing*.
+- [40] CCITT Recommendation Q.953.1 (1992), *ISDN stage 3 description for call completion supplementary services using DSS 1: Call waiting*.
+- [41] ITU-T Recommendation Q.953.2 (1993), *ISDN stage 3 description for call completion supplementary services using DSS 1: Call hold*.
+
+- [42] ITU-T Recommendation Q.953.4 (1995), *ISDN stage 3 description for call completion supplementary services using DSS 1: Terminal portability.*
+- [43] ITU-T Recommendation Q.954.2 (1995), *Stage 3 description for multiparty supplementary services using DSS 1: Three-party service.*
+- [44] CCITT Recommendation Q.955.1 (1992), *Stage 3 description for community of interest supplementary services using DSS 1: Closed user group.*
+- [45] ITU-T Recommendation Q.955.3 (1993), *Stage 3 description for community of interest supplementary services using DSS 1: Multilevel precedence and preemption.*
+- [46] ITU-T Recommendation Q.957.1 (1993), *Stage 3 description for additional information transfer supplementary services using DSS 1: User-to-User Signalling (UUS).*
+
+## 3 Terminology
+
+### 3.1 Definitions
+
+This Recommendation defines the following terms:
+
+- 3.1.1 ISDN access:** Access using DSS 1 interworking directly with ISUP.
+- 3.1.2 non-ISDN access:** Access using any signalling protocol other than DSS 1 interworking directly with ISUP.
+- 3.1.3 undetermined access:** Any type of access (ISDN or non-ISDN) interworking with ISUP over a non-ISDN network.
+
+### 3.2 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|--------|--------------------------------------------|
+| 3PTY | Three-Party Service |
+| ACM | Address Complete Message |
+| ANM | Answer Message |
+| asynch | asynchronous |
+| ATP | Access Transport |
+| BC | Bearer Capability |
+| BCI | Backward Call Indicator |
+| CCBS | Call Completion to Busy Subscriber |
+| CLI | Calling Line Identity |
+| CLIP | Calling Line Identification Presentation |
+| CLIR | Calling Line Identification Restriction |
+| COL | Connected Line Identity |
+| COLP | Connected Line Identification Presentation |
+| COLR | Connected Line Identification Restriction |
+
+COMM Communication
+ CON Connect Message
+ CONF Conference Calling
+ CONFIG Configuration
+ COT Continuity message
+ CPG Call Progress message
+ CUG Closed User Group
+ CW Call Waiting
+ FAA Facility Accepted message
+ FAR Facility Request message
+ FCI Forward Call Indicator
+ FRJ Facility Reject message
+ GenNot Generic Notification
+ HLC High Layer Compatibility
+ HOLD Call Hold
+ IAM Initial Address Message
+ IDR Identification Request message
+ IE Information Element
+ Ind Indicator
+ Info Information
+ IPI ISUP Preference Indicator
+ IRS Identification Response Message
+ ISC International Switching Centre
+ ISDN Integrated Services Digital Network
+ ISUP ISDN User Part
+ LFB Look For Busy
+ LLC Low Layer Compatibility
+ MCID Malicious Call Identification
+ MLPP Multi-level Precedence and Preemption
+ NCI Nature of Connection Indicator
+ OBCI Optional Backward Call Indicator
+ OFCI Optional Forward Call Indicator
+ PI Progress Indicator
+ PROG Progress message
+
+| | |
+|---------|------------------------------------------|
+| REF | Reference |
+| REL | Release message |
+| RES | Resume message |
+| RLC | Release Complete message |
+| RnNbRes | Redirection Number Restriction indicator |
+| SGM | Segmentation Message |
+| SUB | Sub-addressing |
+| SUS | Suspend message |
+| synch | synchronous |
+| TMR' | Transmission Medium Requirement Prime |
+| TMR | Transmission Medium Requirement |
+| TMU | Transmission Medium Used |
+| TP | Terminal Portability |
+| UDI | Unrestricted Digital Information |
+| UNI | User Network Interface |
+| USI' | User Service Information Prime |
+| USI | User Service Information |
+| USR | User-to-User Information Message |
+| UUI | User-to-User Information |
+| UUIInd | User-to-User Indicator |
+| UUS | User-to-User Signalling |
+| UUS1 | User-to-User Signalling service 1 |
+| UUS2 | User-to-User Signalling service 2 |
+| UUS3 | User-to-User Signalling service 3 |
+
+## 4 Objective of the test specification
+
+The objective of these test specifications is to assure the compatibility of the protocol mappings and call control in a user-to-user ISDN/non-ISDN/undetermined access signalling relation, i.e. Network A access (ISDN, non-ISDN, undetermined), Network A transit ISUP (Q.764 or equivalent), International ISUP, Network B transit ISUP (Q.764 or equivalent), and Network B access (ISDN, non-ISDN, undetermined). In some test cases, there is additionally a Network C access (ISDN), Network C transit ISUP (Q.764 or equivalent), and a Network D transit ISUP (Q.764 or equivalent), and Network D access (ISDN) interconnected via the international ISUP to Network B. These test specifications are based on Recommendations Q.699 [2], Q.767 [26], Q.761 to Q.764 [22]-[25], Q.931 [31], Q.73x-Series [3]-[21], and the Q.950-Series of Recommendations [33]-[46]. Call control and transmission, as well as signalling protocols, are integral parts of these tests.
+
+As currently specified, the ISUP protocol contains many implementations choices, with optional parameters and even within mandatory parameters. Given that it is unlikely that two Administrations have made the same implementation choices, testing must be performed to check the compatibility of the implementations. The national access protocols can be even more disparate. Many Administrations have access protocols based on earlier versions of Recommendation Q.931 to 932. The mapping of signalling information from UNI-to-UNI to meet Recommendations Q.761 to 764 or Q.767 and to accommodate interworking signalling protocols is partially addressed in Recommendation Q.699.
+
+In order to ascertain that these test specifications meet the above objectives, the following criteria are used:
+
+- 1) All tests should add value in meeting the objective above. For example, the testing of timers of which the only function is to alert maintenance staff on expiration may not be useful.
+- 2) These test specifications are not intended to provide exhaustive testing of all aspects of the signalling relation.
+- 3) The proposed compatibility test specifications for interworkings between ISDN, non-ISDN, and undetermined accesses over international ISUP assume that each DSS 1 access implementation is equivalent to Recommendation Q.931, each transit ISUP implementation is modelled after Recommendation Q.764, and the international ISUP follows Recommendations Q.761 to Q.764, or Q.767.
+- 4) Test specifications are arranged in four sections. The first section contains ISDN basic call control. The second section contains ISDN supplementary services. The third section contains undetermined access interworking. The last section contains non-ISDN access interworking.
+- 5) Interactions between supplementary services are not subject of this Recommendation. Therefore only very few cases of interactions are described.
+- 6) The ISUP'92 supplementary services described within this Recommendation are the services listed in Table 1/Q.761. All additional services are out of the scope of this Recommendation.
+
+## **5 Scope of UNI-to-UNI compatibility testing**
+
+The compatibility testing principle is to test from UNI to UNI. It verifies that signalling information is mapped correctly octet by octet during interworking between national accesses, national networks, and the international network protocols. See Figure 1.
+
+
+
+```
+
+graph LR
+ subgraph Left_Network [National network]
+ direction TB
+ NN1((National network)) --- Access1[Access
+(ISDN, non-ISDN,
+undetermined)]
+ end
+ subgraph Right_Network [National network]
+ direction TB
+ NN2((National network)) --- Access2[Access
+(ISDN, non-ISDN,
+undetermined)]
+ end
+ NN1 --- ISC1[ISC]
+ ISC1 --- ISUP1[ISUP]
+ ISUP1 --- ISC2[ISC]
+ ISC2 --- ISUP2[ISUP]
+ ISUP2 --- NN2
+ T1182440-96
+
+```
+
+Diagram of UNI-to-UNI test configuration showing two National networks connected via two ISUP/ISC nodes. Each National network is connected to an Access unit (ISDN, non-ISDN, undetermined).
+
+**Figure 1/Q.788 – UNI-to-UNI test configuration**
+
+The testing is initiated by generating appropriate stimuli by an access tester at the UNI (e.g. DSS 1 S/T interface) and monitoring resulting message signalling unit traffic on each of the components of the signalling relation. Simulators or TE may be used to generate the appropriate stimuli needed for the test.
+
+When there are multiple possible message flows for a test, the possible variations are labelled **Case a, Case b**, etc.
+
+## 6 General principles of UNI-to-UNI tests
+
+This Recommendation covers only ISUP functionality. SCCP/TC functionalities which are also used for some of the supplementary services e.g. CUG, MLPP etc. are not considered with the described tests.
+
+For some supplementary services more than two networks can be involved. For practical reasons, it may be useful to have only two networks included for all tests. For example UNI B should belong to Network B. UNI A, UNI C and UNI D should all belong to Network A.
+
+The correct behaviour of the echo control devices is not checked within this Recommendation. It is assumed that the echo control devices work correctly after being checked during Compatibility testing (Recommendation Q.784 [28]).
+
+The description of the dynamic echo control procedure is out of the scope of this Recommendation. Even if the dynamic echo control procedure is in use during the tests, special codings and procedures are not described within the test descriptions.
+
+The parameters and parameter values used for the Compatibility procedure are also not described in the test sheets. Possible reactions caused by this procedure are not described.
+
+### 6.1 General pre-test conditions
+
+For all tests it is assumed that there are general pre-test conditions. In exceptional cases the deviations to these pre-test conditions are handled under the point **Pre-test conditions** in each test description.
+
+- 1) The circuits which will be used for the test calls should always be in the idle state.
+- 2) The called terminal shall be free.
+
+- 3) All of the ISDN access to ISDN access tests assume that ISUP signalling is used from UNI-to-UNI.
+- 4) The terminals or simulators used to perform the tests should support all features of the service needed for the special test case.
+
+## **7 Test environments**
+
+This clause shows the nine test configurations referenced in the individual test specifications.
+
+In Figures 2 to 10 the designation "ISUP" means either ISUP'92 or Recommendation Q.767.
+
+
+
+This diagram illustrates the ISDN access to ISDN access test environment for two networks, labeled Network A and Network B. The sequence of components from left to right is: ISDN access, a bracket labeled UNI, an oval labeled National ISUP, a bracket labeled ISUP, a rectangle labeled ISC, a bracket labeled ISUP, an oval labeled National ISUP, a bracket labeled UNI, and ISDN access. Asterisks (\*) are placed between each component. The label 'T1182450-96' is located at the bottom right.
+
+Diagram of ISDN access to ISDN access test environment for two networks (Figure 2).
+
+Figure 2/Q.788 – ISDN access to ISDN access test environment
+
+
+
+This diagram illustrates the ISDN access to ISDN access test environment for three networks, labeled Network A, Network B, and Network C. The sequence of components from left to right is: ISDN access, a bracket labeled UNI, an oval labeled National ISUP, a bracket labeled ISUP, a rectangle labeled ISC, a bracket labeled ISUP, a rectangle labeled ISC, a bracket labeled ISUP, an oval labeled National ISUP, a bracket labeled ISUP, a rectangle labeled ISC, a bracket labeled ISUP, an oval labeled National ISUP, a bracket labeled UNI, and ISDN access. Asterisks (\*) are placed between each component. The label 'T1182460-96' is located at the bottom right.
+
+Diagram of ISDN access to ISDN access test environment for three networks (Figure 3).
+
+Figure 3/Q.788 – ISDN access to ISDN access test environment
+
+
+
+This diagram illustrates the ISDN access to ISDN access test environment for three networks, labeled Network A, Network B, and Network C. The sequence of components from left to right is: ISDN access, a bracket labeled UNI, an oval labeled National ISUP, a bracket labeled ISUP, a rectangle labeled ISC, a bracket labeled ISUP, a rectangle labeled ISC, a bracket labeled ISUP, an oval labeled National ISUP, a bracket labeled ISDN access, a bracket labeled UNI, a bracket labeled ISDN access, a bracket labeled UNI, an oval labeled National ISUP, a bracket labeled ISUP, a rectangle labeled ISC, a bracket labeled ISUP, an oval labeled National ISUP, a bracket labeled UNI, and ISDN access. Asterisks (\*) are placed between each component. The label 'T1182470-96' is located at the bottom right.
+
+Diagram of ISDN access to ISDN access test environment for three networks with an intermediate access point (Figure 4).
+
+Figure 4/Q.788 – ISDN access to ISDN access test environment
+
+
+
+This diagram illustrates a test environment for ISDN access to ISDN access. It features four networks (A, B, C, and D) connected via a common ISUP/ISC backbone. Each network consists of an ISDN access unit connected to a National ISUP node via a UNI interface. The National ISUP nodes are interconnected by ISC (Intermediate Switching Center) nodes, which are further connected to an ISUP node. The ISUP nodes are all connected to a single common ISUP node at the top. Asterisks (\*) are placed at various interfaces to indicate test points. A reference code T1182480-96 is shown in the bottom right corner.
+
+Diagram of ISDN access to ISDN access test environment (Figure 5/Q.788).
+
+**Figure 5/Q.788 – ISDN access to ISDN access test environment**
+
+
+
+This diagram shows a test environment for ISDN access to an undetermined access. Network A contains an ISDN access unit connected to a National ISUP node via a UNI interface. Network B contains a National non-ISUP node connected to an undetermined access via a UNI interface. The National ISUP node in Network A is connected to an ISC node, which is connected to another ISC node, which is then connected to the National non-ISUP node in Network B. ISUP nodes are associated with each ISC node. Asterisks (\*) mark test points at the UNI interfaces and between the ISC nodes. A reference code T1182490-96 is located in the bottom right corner.
+
+Diagram of ISDN access to undetermined access test environment (Figure 6/Q.788).
+
+**Figure 6/Q.788 – ISDN access to undetermined access test environment**
+
+
+
+This diagram depicts a test environment for undetermined access to undetermined access. Network A contains a National non-ISUP node connected to an undetermined access via a UNI interface. Network B also contains a National non-ISUP node connected to an undetermined access via a UNI interface. The National non-ISUP node in Network A is connected to an ISC node, which is connected to another ISC node, which is then connected to the National non-ISUP node in Network B. ISUP nodes are associated with each ISC node. Asterisks (\*) mark test points at the UNI interfaces and between the ISC nodes. A reference code T1182500-96 is located in the bottom right corner.
+
+Diagram of undetermined access to undetermined access test environment (Figure 7/Q.788).
+
+**Figure 7/Q.788 – Undetermined access to undetermined access test environment**
+
+
+
+Figure 8/Q.788 – ISDN access to non-ISDN access test environment. The diagram shows a signalling path from an ISDN access on the left to a Non-ISDN access on the right. The path consists of: ISDN access | UNI | \* (National ISUP) | \* (ISUP ISC) | \* (ISUP ISC) | \* (National ISUP) | UNI | Non-ISDN access. The first part (ISDN access to the first ISC) is bracketed and labeled 'Network A'. The second part (second ISC to Non-ISDN access) is bracketed and labeled 'Network B'. A reference code 'T1182510-96' is at the bottom right.
+
+**Figure 8/Q.788 – ISDN access to non-ISDN access test environment**
+
+
+
+Figure 9/Q.788 – Undetermined access to non-ISDN access test environment. The diagram shows a signalling path from an Undetermined access on the left to a Non-ISDN access on the right. The path consists of: Undetermined access | (\*) (National non-ISUP) | (ISUP ISC) | \* (ISUP ISC) | \* (National ISUP) | UNI | Non-ISDN access. The first part (Undetermined access to the first ISC) is bracketed and labeled 'Network A'. The second part (second ISC to Non-ISDN access) is bracketed and labeled 'Network B'. A reference code 'T1182520-96' is at the bottom right.
+
+**Figure 9/Q.788 – Undetermined access to non-ISDN access test environment**
+
+
+
+Figure 10/Q.788 – Non-ISDN access to non-ISDN access test environment. The diagram shows a signalling path from a Non-ISDN access on the left to another Non-ISDN access on the right. The path consists of: Non-ISDN access | UNI | \* (National ISUP) | \* (ISUP ISC) | \* (ISUP ISC) | \* (National ISUP) | UNI | Non-ISDN access. The first part (Non-ISDN access to the first ISC) is bracketed and labeled 'Network A'. The second part (second ISC to Non-ISDN access) is bracketed and labeled 'Network B'. A reference code 'T1182530-96' is at the bottom right.
+
+**Figure 10/Q.788 – Non-ISDN access to non-ISDN access test environment**
+
+In each figure above, \* indicates a component of the signalling relation where ISUP/DSS 1 messages can be verified. (\*) indicates a component of the signalling relation where DSS 1 messages may be verified.
+
+## 8 UNI-to-UNI Compatibility Test List
+
+An "x" in the column "ISUP'92" in the list below means that all of the involved networks (ISC, national network) use ISUP'92; in test cases with ISDN accesses and/or non-ISDN accesses, ISUP'92 is used between the involved local exchanges.
+
+An "x" in the column "Comb" means that at least one of the networks (ISC, national network) uses ISUP'92 and at least one other network (ISC, national network) uses ISUP Recommendation Q.767 (*Blue Book*). In test cases with ISDN accesses and/or non-ISDN accesses this means that not all involved UNIs will receive information derived from ISUP'92 information.
+
+The test list has a new format: the titles of the tests were compared.
+
+| Title | ISUP'92 | Comb |
+|------------------------------------------------------------------|---------|------|
+| 1 ISUP/ISDN Basic Call Control | | |
+| 1.1 Successful call set-up | | |
+| 1.1.1 Basic Call set-up (BC) | X | X |
+| 1.1.2 Transport of Progress Indicator information element | | |
+| 1.1.2.1 SETUP | X | X |
+| 1.1.2.2 PROGRESS/ALERT | X | X |
+| 1.1.2.3 CONNECT | X | X |
+| 1.1.3 Transport of BC/HLC/LLC information elements | | |
+| 1.1.3.1 BC/HLC/LLC combinations | X | X |
+| 1.1.3.2 BC = 64 kbit/s with rate adaptation | X | X |
+| 1.1.3.3 BC = 56 kbit/s | X | X |
+| 1.1.4 Fallback | | |
+| 1.1.4.1 Fallback successfully performed | X | |
+| 1.1.4.2 Fallback does not occur | X | |
+| 1.1.4.3 Fallback performed by Network A's ISC | X | X |
+| 1.1.5 Segmentation | | |
+| 1.1.5.1 Simple Segmentation successful | X | |
+| 1.1.5.2 Segment discarded | X | X |
+| 1.1.6 Multirate connection types | | |
+| 1.1.6.1 Successful call set-up | X | |
+| 1.1.6.2 Unsuccessful call set-up | X | X |
+| 1.2 Normal call release | | |
+| 1.2.1 Calling party clears before answer | X | X |
+| 1.2.2 Calling party clears after answer | X | X |
+| 1.2.3 Called party clears after answer | X | X |
+| 1.3 Unsuccessful call set-up | | |
+| 1.3.1 All circuits busy at the destination network | X | X |
+| 1.3.2 Dialling of an unallocated number | X | X |
+| 1.3.3 No route to destination | X | X |
+| 1.3.4 Calling to a busy subscriber | X | X |
+| 1.3.5 Address incomplete | X | X |
+
+| Title | ISUP'92 | Comb |
+|-------------------------------------------------------------------------------------------------------|---------|------|
+| 1.4 Abnormal situation during call | | |
+| 1.4.1 No response from the called party | x | x |
+| 1.4.2 No answer from the called party (T9/Q.764 expiration) | x | x |
+| 2 ISUP/ISDN Call Control with supplementary services | | |
+| 2.1 Calling Line Identification (CLI) | | |
+| 2.1.1 CLIP – network provided, without calling party subaddress | x | x |
+| 2.1.2 CLIP – network provided | x | x |
+| 2.1.3 CLIP – user provided, verified and passed | x | x |
+| 2.1.4 CLIP – user provided, not verified | x | x |
+| 2.1.5 CLIR – network provided, without calling party subaddress | x | x |
+| 2.1.6 CLIR – network provided | x | x |
+| 2.1.7 CLIR – user provided, verified and passed | x | x |
+| 2.1.8 CLIR – user provided, not verified | x | x |
+| 2.2 Sub-addressing (SUB) | | |
+| 2.2.1 Transport of called party subaddress | x | x |
+| 2.3 Connected Line Identification (COL) | | |
+| 2.3.1 COL – request | x | x |
+| 2.3.2 COLP – network provided | x | x |
+| 2.3.3 COLP – user provided, verified and passed | x | x |
+| 2.3.4 COLP – user provided, not verified | x | x |
+| 2.3.5 COLR – network provided | x | x |
+| 2.3.6 COLR – user provided, verified and passed | x | x |
+| 2.3.7 COLR – user provided, not verified | x | x |
+| 2.3.8 COL received but not requested | x | x |
+| 2.3.9 COL not available | x | x |
+| 2.4 Closed User Group (CUG) – Decentralized | | |
+| 2.4.1 CUG call with outgoing access allowed (both UNIs belong to the same CUG) | x | x |
+| 2.4.2 CUG call with outgoing access allowed (called party not in a CUG) | x | x |
+| 2.4.3 CUG call with outgoing access allowed (one network supports CUG) | x | x |
+| 2.4.4 CUG call with outgoing access not allowed, to a network offering CUG (called party in same CUG) | x | x |
+| 2.4.5 CUG call with outgoing access not allowed, to a network offering CUG (called party outside CUG) | x | x |
+
+| Title | | ISUP'92 | Comb |
+|--------|-------------------------------------------------------------------------------------------------------------------------------------------|---------|------|
+| 2.4.6 | CUG call with outgoing access allowed, to a network offering CUG (called party in a different CUG, no incoming access allowed) | x | x |
+| 2.4.7 | CUG call with outgoing access allowed, to a network offering CUG (called party in a different CUG, incoming access allowed) | x | x |
+| 2.4.8 | CUG call with outgoing access not allowed, to a network offering CUG (called party in same CUG, incoming calls barred at Network B's UNI) | x | x |
+| 2.4.9 | CUG call with outgoing access not allowed, to a network not offering CUG | x | x |
+| 2.4.10 | Non-CUG call towards a CUG destination with incoming access not allowed | x | x |
+| 2.4.11 | Non-CUG call towards a CUG destination with incoming access allowed | x | x |
+| 2.5 | Malicious Call Identification (MCID) | | |
+| 2.5.1 | Successful request | x | |
+| 2.5.2 | Unsuccessful request, MCID information not available or not supported | x | |
+| 2.5.3 | Unsuccessful request, no response to IDR | x | x |
+| 2.6 | Call Forwarding Busy (CFB) | | |
+| 2.6.1 | Call Forwarding Busy (network determined) – full notification | x | x |
+| 2.6.2 | Call Forwarding Busy (network determined) – no notification | x | x |
+| 2.6.3 | Call Forwarding Busy (user determined) – full notification | x | x |
+| 2.6.4 | Call Forwarding Busy (user determined) – Unsuccessful | x | x |
+| 2.7 | Call Forwarding No Reply (CFNR) | | |
+| 2.7.1 | Call Forwarding No Reply (option A, late release) – full notification | x | x |
+| 2.7.2 | Call Forwarding No Reply (option A, late release) – no notification | x | x |
+| 2.7.3 | Call Forwarding No Reply (option B, immediate release) – full notification | x | x |
+| 2.7.4 | Call Forwarding No Reply (option A, late release) – Unsuccessful | x | x |
+| 2.7.5 | Call Forwarding No Reply (option B, immediate release) – Unsuccessful | x | x |
+| 2.8 | Call Forwarding Unconditional (CFU) | | |
+| 2.8.1 | Call Forwarding Unconditional – Successful – full notification | x | x |
+| 2.8.2 | Call Forwarding Unconditional – Successful – no notification | x | x |
+| 2.8.3 | Call Forwarding Unconditional – Unsuccessful | x | x |
+
+| | Title | ISUP'92 | Comb |
+|--------|--------------------------------------------------------------------------------------|---------|------|
+| 2.9 | Call Deflection (CD) | | |
+| 2.9.1 | Call Deflection during alerting (option B, immediate release) – full notification | x | x |
+| 2.9.2 | Call Deflection during alerting (option B, immediate release) – no notification | x | x |
+| 2.9.3 | Call Deflection immediate response (option B, immediate release) – full notification | x | x |
+| 2.9.4 | Call Deflection during alerting (option A, late release) – full notification | x | x |
+| 2.9.5 | Call Deflection during alerting (option B, immediate release) – Unsuccessful | x | x |
+| 2.9.6 | Call Deflection immediate response (option B, immediate release) – Unsuccessful | x | x |
+| 2.9.7 | Call Deflection during alerting (option A, late release) – Unsuccessful | x | x |
+| 2.10 | Call Waiting (CW) | | |
+| 2.10.1 | Call Waiting successful | x | x |
+| 2.10.2 | Call Waiting rejection | x | x |
+| 2.10.3 | Call Waiting ignored | x | x |
+| 2.11 | Call Hold (HOLD) | | |
+| 2.11.1 | Hold and Retrieve during waiting for ANM | x | x |
+| 2.11.2 | Hold call and clear before Retrieve during waiting for ANM | x | x |
+| 2.11.3 | Hold and Retrieve during active phase | x | x |
+| 2.11.4 | Hold during active phase; served user clears call during held state | x | x |
+| 2.11.5 | Hold during active phase; non-served user clears call during held state | x | x |
+| 2.12 | Terminal Portability (TP) | | |
+| 2.12.1 | Successful | x | x |
+| 2.12.2 | Unsuccessful, Timer expiry | x | x |
+| 2.13 | Conference Calling (CONF) | | |
+| 2.13.1 | Establishment of a conference and termination of the conference | x | x |
+| 2.13.2 | Isolation, Reattachment and Disconnection of one party of the conference | x | x |
+| 2.13.3 | Splitting and Adding of a party | x | x |
+| 2.13.4 | Floating of a conference (explicit request) | x | x |
+| 2.13.5 | Call clearing by served user when floating is allowed | x | x |
+| 2.14 | Three-Party Service (3PTY) | | |
+| 2.14.1 | Invocation and splitting of a Three-party conversation | x | x |
+| 2.14.2 | Served user disconnects one of the remote users | x | x |
+| 2.14.3 | Disconnect sent by one of the remote users | x | x |
+| 2.14.4 | Disconnect of the entire call | x | x |
+
+| Title | ISUP'92 | Comb |
+|---------------------------------------------------------------------------------------------|---------|------|
+| 2.15 User-to-User Signalling service 1 (UUS1) | | |
+| 2.15.1 Implicit request – Successful – UUI in the forward and backward messages | x | x |
+| 2.15.2 Implicit request – Discard of UUI by the network | x | x |
+| 2.15.3 Explicit request – Successful – UUI in the forward and backward messages | x | |
+| 2.15.4 Explicit request (not-essential) – Implicit rejection by the network | x | x |
+| 2.15.5 Explicit request (not-essential) – Explicit rejection by the network | x | |
+| 2.15.6 Explicit request (essential) – Explicit rejection by the network | x | |
+| 2.15.7 Explicit request (essential) – Explicit rejection by the called user | x | |
+| 2.16 User-to-User Signalling service 2 (UUS2) | | |
+| 2.16.1 Successful – UUI in the forward and the backward direction | x | |
+| 2.16.2 Not-essential – Implicit network rejection | x | x |
+| 2.16.3 Not-essential – Explicit network rejection | x | |
+| 2.16.4 Essential – Explicit rejection | x | |
+| 2.16.5 Essential – Explicit rejection – multipoint | x | |
+| 2.17 User-to-User Signalling service 3 (UUS3) | | |
+| 2.17.1 Successful – UUI in both directions, request during call establishment | x | |
+| 2.17.2 Not essential – Implicit network rejection, request during call establishment | x | x |
+| 2.17.3 Not essential – Explicit rejection, request during call establishment | x | |
+| 2.17.4 Essential – Explicit network rejection request during call establishment | x | |
+| 2.17.5 Request during call – Successful – UUI in both directions – Request during call | x | |
+| 2.17.6 Implicit rejection – Request during call | x | x |
+| 2.17.7 Explicit rejection – Request during call | x | |
+| 2.18 Multi-level Precedence and Preemption (MLPP) | | |
+| 2.18.1 Invocation with no circuit congestion to MLPP subscriber | x | |
+| 2.18.2 Invocation with no circuit congestion to non-MLPP subscriber | x | x |
+| 2.18.3 Invocation when congestion encountered, release of circuit reserved for re-use | x | |
+| 2.18.4 Invocation when congestion encountered, release of circuit not reserved for re-use | x | |
+| 2.18.5 Invocation when congestion encountered, unsuccessful search for preemptable circuits | x | |
+| 2.18.6 Invocation when congestion encountered, precedence too low to preempt | x | |
+
+| Title | ISUP'92 | Comb |
+|-----------------------------------------------------------|---------|------|
+| 3 Undetermined Access Interworking | | |
+| 3.1 ISDN Access → Undetermined Access | | |
+| 3.1.1 Normal call release | | |
+| 3.1.1.1 Calling party clears before answer | x | x |
+| 3.1.1.2 Calling party clears after answer | x | x |
+| 3.1.1.3 Called party suspends after answer | x | x |
+| 3.1.1.4 Called party suspends after answer, expiry of T6 | x | x |
+| 3.1.1.5 Called party suspends after answer, expiry of T38 | x | x |
+| 3.1.2 Unsuccessful call set-up | | |
+| 3.1.2.1 All circuits busy at destination network | x | x |
+| 3.1.2.2 Dialling of an unallocated number | x | x |
+| 3.1.2.3 Calling to a busy subscriber | x | x |
+| 3.1.3 Abnormal situation during a call | | |
+| 3.1.3.1 No answer from the called party – user alerted | x | x |
+| 3.2 Undetermined Access → ISDN Access | | |
+| 3.2.1 Normal call release | | |
+| 3.2.1.1 Calling party clears before answer | x | x |
+| 3.2.1.2 Calling party clears after answer | x | x |
+| 3.2.1.3 Called party clears after answer | x | x |
+| 3.2.2 Unsuccessful call set-up | | |
+| 3.2.2.1 All circuits busy at destination network | x | x |
+| 3.2.2.2 Dialling of an unallocated number | x | x |
+| 3.2.2.3 No route to destination | x | x |
+| 3.2.2.4 Calling to a busy subscriber | x | x |
+| 3.2.2.5 Address incomplete | x | x |
+| 3.2.3 Abnormal situation during call | | |
+| 3.2.3.1 No response from the called party | x | x |
+| 3.3 Undetermined Access → Undetermined Access | | |
+| 3.3.1 Normal call release | | |
+| 3.3.1.1 Calling party clears after answer | x | x |
+| 4 Non-ISDN Access Interworking | | |
+| 4.1 ISDN Access → Non-ISDN Access | | |
+| 4.1.1 Normal call release | | |
+| 4.1.1.1 Calling party clears after answer | x | x |
+
+| Title | ISUP'92 | Comb |
+|--------------------------------------------------|----------------|-------------|
+| 4.2 Non-ISDN Access → ISDN Access | | |
+| 4.2.1 Normal call release | | |
+| 4.2.1.1 Calling party clears after answer | x | x |
+| 4.3 Undetermined Access → Non-ISDN Access | | |
+| 4.3.1 Normal call release | | |
+| 4.3.1.1 Calling party clears after answer | x | x |
+| 4.4 Non-ISDN Access → Undetermined Access | | |
+| 4.4.1 Normal call release | | |
+| 4.4.1.1 Calling party clears after answer | x | x |
+| 4.5 Non-ISDN Access → Non-ISDN Access | | |
+| 4.5.1 Normal call release | | |
+| 4.5.1.1 Calling party clears after answer | x | x |
+
+## 9 UNI-to-UNI test descriptions
+
+**Test number:** 1.1.1 **Ref.:** 2.1/Q.764, D.2.1/Q.767, 4.5.5/Q.931.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Successful Call Set-up – Basic Call Set-up (BC)
+
+**Purpose:** To verify that Basic calls can be set-up.
+
+**Pre-test conditions:**
+
+### Expected message sequence
+
+| Network A | | Network B | |
+|-------------------|---|---------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) | |
+| COT | → | Optional message | |
+| Case a | ← | ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM | |
+| Case b | ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG | Event Info: alerting (0000001) |
+| | ← | ANM | |
+| Case c | ← | CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ⇐ COMMUNICATION ⇑ | | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) | |
+| | ← | RLC | |
+
+#### Test description (ISUP'92, Comb):
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check the propriety of digital data transmission or speech.
+3. Clear the call from Network A's UNI.
+4. Check that all resources are released.
+5. Repeat the test for speech and 3.1 kHz audio bearers.
+6. Repeat steps 1-5 with Networks A and B interchanged.
+
+**Test number:** 1.1.2.1 **Ref.:** 3.3/Q.763, 4.3.2/Q.767, 3.1.16/Q.931.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Successful Call Set-up – Transport of Progress indicator IE – SETUP
+
+**Purpose:** To verify that progress information can be transported correctly.
+
+**Pre-test conditions:** Arrange the stimulus such that the IAM message contains Progress Information in the Access Transport parameter.
+
+#### Expected message sequence
+
+
+
+| | Network A | Network B |
+|-------------------|-----------|----------------------------------------------------------------------------------------------------------------------------------------|
+| | ← | IAM FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), ATP: Progress information |
+| | ← | COT Optional message |
+| Case a | ACM → | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ANM → | |
+| Case b | ACM → | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | CPG → | Event Info: alerting (0000001) |
+| | ANM → | |
+| Case c | ACM → | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | CPG → | |
+| | ANM → | |
+| ⇐ COMMUNICATION ⇒ | | |
+| | REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### Test description (ISUP'92, Comb):
+
+1. Make a 64 kbit/s call from Network B's UNI to Network A's UNI.
+2. Check the presence of the PI in the SETUP message at Network A's UNI.
+3. Check the propriety of digital data transmission or speech.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 1.1.2.2 **Ref.:** 3.3/Q.763, 4.3/Q.767, 3.1.1/Q.931 and 3.1.10/Q.931.
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+**Title:** Successful Call Set-up – Transport of Progress indicator IE – PROG/ALERT
+**Purpose:** To verify that progress information can be transported correctly.
+**Pre-test conditions:** Arrange the stimulus such that the ACM/CPG message contains Progress Information in the Access Transport parameter.
+
+#### **Expected message sequence**
+
+
+
+| | Network A | | Network B |
+|---------------|-----------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | ← | IAM FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| | | ← | COT Optional message |
+| Case a | ACM | → | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), ATP: Progress information |
+| | ANM | → | |
+| Case b | ACM | → | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) ATP: Progress information |
+| | CPG | → | Event Info: alerting (0000001) |
+| | ANM | → | |
+| Case c | ACM | → | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | CPG | → | Event Info: alerting (0000001), ATP: Progress information |
+| | ANM | → | |
+
+⇐ COMMUNICATION ⇒
+
+| | | | |
+|--|-----|---|-----------------------------------------------------------------|
+| | | ← | REL Cause Ind.: Normal call clearing (16), location user (0000) |
+| | RLC | → | |
+
+#### **Test description (ISUP'92, Comb):**
+
+- Make a 64 kbit/s call from Network B's UNI to Network A's UNI.
+- Check the presence of the PI in the ALERT/PROG message at Network B's UNI.
+- Check the propriety of digital data transmission or speech.
+- Clear the call from Network B's UNI.
+- Check that all resources are released.
+- Repeat the test for speech and 3.1 kHz audio bearers.
+- Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 1.1.2.3 **Ref.:** 3.3/Q.763, 4.3.2/Q.767, 3.1.4/Q.931.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Successful Call Set-up – Transport of Progress indicator IE – CONNECT
+
+**Purpose:** To verify that Progress information can be transported correctly.
+
+**Pre-test conditions:** Arrange the stimulus such that the ANM/CON message contains Progress Information in the Access Transport parameter.
+
+#### Expected message sequence
+
+
+
+| | Network A | Network B |
+|-------------------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | ← | IAM FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| | ← | COT Optional message |
+| Case a | ACM → | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ANM → | ATP: Progress information |
+| Case b | ACM → | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | CPG → | Event Info: alerting (0000001) |
+| | ANM → | ATP: Progress information. |
+| Case c | CON → | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), ATP: Progress information |
+| ← COMMUNICATION → | | |
+| | ← | REL Cause Ind.: Normal call clearing (16), location user (0000) |
+| | RLC → | |
+
+#### Test description (ISUP'92, Comb):
+
+1. Make a 64 kbit/s call from Network B's UNI to Network A's UNI.
+2. Check the presence of the PI in the CON message at Network B's UNI.
+3. Check the propriety of digital data transmission or speech.
+4. Clear the call from Network B's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 1.1.3.1 **Ref.:** 3.3/Q.763, 4.3.2/Q.767, 4.5.5/Q.931, 4.5.16/Q.931 and 4.5.18/Q.931.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Successful Call Set-up – Transport of BC/HLC/LLC IE – BC/HLC/LLC Combinations
+
+**Purpose:** To verify that BC/HLC/LLC can be transported correctly as described in Recommendations Q.931/Q.939.
+
+**Pre-test conditions:** Arrange the stimulus such that the USI (BC) = Speech and Access transport parameter contains HLC = Telephony; LLC = Speech.
+
+#### **Expected message sequence**
+
+
+
+| | Network A | Network B |
+|-------------------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), USI (BC), ATP (HLC, LLC) – see Note |
+| | COT → | Optional message |
+| Case a | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← ANM | |
+| Case b | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← CPG | Event Info: alerting (0000001) |
+| | ← ANM | |
+| Case c | ← CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ⇐ COMMUNICATION ⇑ | | |
+| | REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← RLC | |
+
+#### **Test description (ISUP'92):**
+
+- Make a call from Network A's UNI to Network B's UNI with correct BC/HLC/LLC.
+- Check the BC/HLC/LLC in the SETUP message at Network B's UNI.
+- Check the propriety of digital data transmission or speech.
+- Clear the call from Network A's UNI.
+- Check that all resources are released.
+- Repeat the test for at least the following BC/HLC/LLC combinations:
+
+
+| | | |
+|------------------|-------------------------------|-------------------------|
+| 64/G4 Fax/64 | 64/Teletex/64 | 64/Videotex/64 |
+| 64/Mixed-mode/64 | 3.1/G2-G3 fax/3.1 | 64pref/telephony/64pref |
+| Videotelephony: | 1. 64pref/audio visual/64pref | 2. 64/audio visual/64 |
+- Repeat steps 1-6 with Networks A and B interchanged.
+
+#### **Test description (Comb):**
+
+1. Make a call from Network A's (ISUP'92) UNI to Network B's (Q.767) UNI with correct BC/HLC/LLC.
+2. Check the BC/HLC/LLC in the SETUP message at Network A's UNI.
+3. Check the propriety of digital data transmission or speech.
+
+NOTE – For ISUP'92, it is also possible that the HLC parameter is transported in the user teleservice information additionally.
+
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for all supported services either in Network A or in Network B or in both Networks, at least for the following BC/HLC/LLC combinations:
+
+| | | |
+|------------------|-------------------|----------------|
+| 64/G4 Fax/64 | 64/Teletex/64 | 64/Videotex/64 |
+| 64/Mixed-mode/64 | 3.1/G2-G3 fax/3.1 | |
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 1.1.3.2 **Ref.:** 3.3/Q.763, 4.3.3/Q.767, 4.5.5/Q.931 and 4.5.18/Q.931.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Successful Call Set-up – Transport of BC/LLC IE – BC = 64 kbit/s with rate adaption
+
+**Purpose:** To verify that BC = 64 kbit/s with rate adaption can be transported correctly.
+
+**Pre-test conditions:** Arrange the stimulus such that the USI (BC) = 64 kbit/s and ATP (LLC) = user rate 1.2 kbit/s asynch.
+
+#### Expected message sequence
+
+| Network A | Network B |
+|-------------------|-------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), USI (BC), ATP (LLC) |
+| COT → | Optional message |
+| Case a ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← ANM | |
+| Case b ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← CPG | Event Info: alerting (0000001) |
+| ← ANM | |
+| Case c ← CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← COMMUNICATION → | |
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | |
+
+#### Test description (ISUP'92, Comb):
+
+1. Make a call from Network A's UNI to Network B's UNI with correct BC/LLC.
+2. Check the BC/LLC in the SETUP message at Network B's UNI.
+3. Check the propriety of digital data transmission.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for at least the following LLC combinations:
+2.4 kbit/s asynch 4.8 kbit/s asynch 9.6 kbit/s asynch
+14.4 kbit/s asynch 19.2 kbit/s asynch 19.2 kbit/s synch
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 1.1.3.3 **Ref.:** 3.3/Q.763, 4.3.3/Q.767, 4.5.5/Q.931 and 4.5.18/Q.931, 6.1.2.3/Q.939.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Successful Call Set-up – Transport of BC IE – BC = 56 kbit/s
+
+**Purpose:** To verify that a 56 kbit/s call can be established correctly.
+
+**Pre-test conditions:** Arrange the stimulus such that the USI (BC) = 56 kbit/s.
+
+#### **Expected message sequence**
+
+| Network A | | Network B | |
+|---------------|---|-------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), USI – see Note | |
+| COT | → | Optional message | |
+| Case a | ← | ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1) |
+| | ← | ANM | |
+| Case b | ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG | Event Info: alerting (0000001) |
+| | ← | ANM | |
+| Case c | ← | CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+
+⇐ COMMUNICATION ⇒
+
+| | | |
+|-----|---|-------------------------------------------------------------|
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+NOTE – The indication for 56 kbit/s may also be transported in the LLC element additionally.
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a call from Network A's UNI to Network B's UNI with correct BC combination.
+2. Check the BC in the SETUP message at Network B's UNI.
+3. Check the propriety of digital data transmission.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat steps 1-5 with Networks A and B interchanged.
+
+**Test number:** 1.1.4.1 **Ref.:** 2.5/Q.764, 4.5.5/Q.931.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Fallback – Fallback successfully performed
+
+**Purpose:** To verify that the call can be established after Fallback.
+
+**Pre-test conditions:**
+
+1. Arrange routing in Network A such that Fallback does not occur.
+2. Arrange routing in Network B such that Fallback occurs.
+
+#### Expected message sequence
+
+| | Network A | Network B |
+|---------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | IAM → | TMR: 64kbit/s pref, TMR': speech, USI: speech, USI': 7 kHz, FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| | COT → | Optional message |
+| Case a | ← ACM | TMU: speech, BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← ANM | |
+| Case b | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← ANM | TMU: speech |
+| Case c | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← CPG | Event Info: alerting (0000001), TMU: speech |
+| | ← ANM | |
+| Case d | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← CPG | Event Info: alerting (0000001) |
+| | ← ANM | TMU: speech |
+| Case e | ← CON | TMU: speech, BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+
+⇐ COMMUNICATION ⇒
+
+| | | |
+|--|-------|-------------------------------------------------------------|
+| | REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← RLC | |
+
+#### Test description (ISUP'92):
+
+1. Make a call from Network A's UNI to Network B's UNI with BC = UDI with tones and announcements and BC = speech in the same SETUP.
+2. Check that the call is established with BC = speech.
+3. Check the propriety of speech.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat steps 1-5 with Networks A and B interchanged.
+
+**Test number:** 1.1.4.2 **Ref.:** 2.5/Q.764, 4.5.5/Q.931.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Fallback – Fallback does not occur
+
+**Purpose:** To verify that TMR', TMR, USI' and USI can be transported correctly.
+
+**Pre-test conditions:** Arrange exchange data in both networks such that Fallback does not occur.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-------------------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | TMR: 64kbit/s pref, TMR': speech, USI: speech, USI': 7 kHz, FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ⇐ COMMUNICATION ⇑ | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92):**
+
+1. Make a call from Network A's UNI to Network B's UNI with BC = UDI with tones and announcements and BC = speech in the same SETUP.
+2. Check that the call is established with BC = UDI with tones and announcements.
+3. Check the propriety of the communication.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat steps 1-5 with Networks A and B interchanged.
+
+**Test number:** 1.1.4.3 **Ref.:** 2.5/Q.764, 4.5.5/Q.931.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Fallback – Fallback performed by Network A's ISC
+
+**Purpose:** To verify that Network A's ISC can perform Fallback due to an ISUP version in Network B not supporting Fallback.
+
+**Pre-test conditions:**
+
+1. Only Network A supports Fallback.
+2. Arrange the routing in Network A such that Fallback occurs in Network A.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-------------------|---|-----------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | TMR: speech, USI: speech, FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ⇐ COMMUNICATION ⇒ | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a call from Network A's UNI to Network B's UNI with BC = UDI with tones and announcements and BC = speech in the same SETUP.
+2. Check that the call is established with BC = speech.
+3. Check that TMU is generated in Network A's ISC.
+4. Check the propriety of speech.
+5. Clear the call from Network A's UNI.
+6. Check that all resources are released.
+
+**Test number:** 1.1.5.1 **Ref.:** 2.1.12/Q.764, 5/Q.931.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Segmentation – Simple Segmentation successful
+
+**Purpose:** To verify that information can be transported in a SGM.
+
+**Pre-test conditions:**
+
+1. Both Networks support Segmentation.
+2. Arrange a call set-up such that the content of the international IAM exceeds 272 octets.
+
+#### Expected message sequence
+
+| Network A | Network B |
+|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), OFCI: additional information will be sent (1) |
+| COT → | Optional message |
+| SGM → | |
+| ← Case a | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← | ANM |
+| ← Case b | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← | CPG Event Info: alerting (0000001) |
+| ← | ANM |
+| ← Case c | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← COMMUNICATION ⇒ | |
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← | RLC |
+
+#### Test description (ISUP'92):
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that all the information is received at Network B's UNI.
+3. Check the propriety of digital data transmission or speech.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 1.1.5.2 **Ref.:** 2.1.12/Q.764, 5/Q.931.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Segmentation – Segment discarded
+
+**Purpose:** To verify that a call can be successfully established, even if SGM is discarded.
+
+**Pre-test conditions:**
+
+1. Only Network A supports Segmentation.
+2. Arrange a call set-up such that the content of the international IAM exceeds 272 octets.
+
+#### Expected message sequence
+
+| Network A | | Network B |
+|-------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), OFCI: additional information will be sent (1) |
+| COT | → | Optional message |
+| SGM | → | |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ⇐ COMMUNICATION ⇒ | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### Test description (ISUP'92, Comb):
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that SETUP is received at Network B's UNI.
+3. Check the propriety of digital data transmission or speech.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+
+**Test number:** 1.1.6.1 **Ref.:** 2.1/Q.764, 4.5.5/Q.931.
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+**Title:** Multirate connection types – Successful call set-up
+**Purpose:** To verify that multirate connection type calls can be successfully established.
+**Pre-test conditions:** Both networks support multirate connection types.
+
+#### **Expected message sequence**
+
+
+
+| Network A | | Network B |
+|---------------|---|-----------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), TMR, USI (BC) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+
+⇐ COMMUNICATION ⇒
+
+| | | |
+|-----|---|-------------------------------------------------------------|
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92):**
+
+1. Make a 2\*64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check the propriety of digital data transmission.
+3. Clear the call from Network A's UNI.
+4. Check that all resources are released.
+5. Repeat the test for bearers 384 kbit/s, 1536 kbit/s and 1920 kbit/s.
+6. Repeat steps 1-5 with Networks A and B interchanged.
+
+**Test number:** 1.1.6.2 **Ref.:** 2.3/Q.764, 4.1/Q.767, 4.5.5/Q.931.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Multirate connection types – Unsuccessful call set-up
+
+**Purpose:** To verify that the call will be successfully released, if the connection type is not supported in Network B.
+
+**Pre-test conditions:** Only Network A supports multirate connection types.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-----------|---|-------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), TMR, USI (BC) |
+| COT | → | Optional message |
+| | ← | REL Cause Ind.: Bearer capability not implemented (65), location transit network (0011) or international network (0111) |
+| RLC | → | |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a 2\*64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that all resources are released.
+3. Repeat the test for bearers 384 kbit/s, 1536 kbit/s and 1920 kbit/s.
+
+**Test number:** 1.2.1 **Ref.:** 2.3.1/Q.764, 5.3.3/Q.931.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Normal Call Release – Calling party clears before answer
+
+**Purpose:** To verify that the calling party can successfully release a call prior to receipt of answer.
+
+#### **Pre-test conditions:**
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|---------------|---|-----------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Do not answer the call at Network B's UNI.
+3. Clear the call from Network A's UNI.
+4. Check that all resources are released.
+5. Repeat the test for speech and 3.1 kHz audio bearers.
+6. Repeat steps 1-5 with Networks A and B interchanged.
+
+**Test number:** 1.2.2 **Ref.:** 2.3.1/Q.764, 5.3.3/Q.931.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Normal Call Release – Calling party clears after answer
+
+**Purpose:** To verify that the calling party can successfully release a call after answer.
+
+**Pre-test conditions:**
+
+#### **Expected message sequence**
+
+
+
+| Network A | | Network B |
+|-------------------|---|-----------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ⇐ COMMUNICATION ⇒ | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check the propriety of digital data transmission or speech.
+3. Clear the call from Network A's UNI.
+4. Check that all resources are released.
+5. Repeat the test for speech and 3.1 kHz audio bearers.
+6. Repeat steps 1-5 with Networks A and B interchanged.
+
+**Test number:** 1.2.3 **Ref.:** 2.3.2/Q.764, 5.3.3/Q.931.
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+**Title:** Normal Call Release – Called party clears after answer
+**Purpose:** To verify that a call can be successfully released in the backward direction.
+**Pre-test conditions:**
+
+#### **Expected message sequence**
+
+
+
+| | Network A | Network B |
+|---------------|-----------|-------------------------------------------------------------------------------------------------------------------------------|
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| | COT → | Optional message |
+| Case a | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← ANM | |
+| Case b | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← CPG | Event Info: alerting (0000001) |
+| | ← ANM | |
+| Case c | ← CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+
+⇐ COMMUNICATION ⇒
+
+| | | |
+|--|-------|-------------------------------------------------------------|
+| | ← REL | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | RLC → | |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check the propriety of digital data transmission or speech.
+3. Clear the call from Network B's UNI.
+4. Check that all resources are released.
+5. Repeat the test for speech and 3.1 kHz audio bearers.
+6. Repeat steps 1-5 with Networks A and B interchanged.
+
+**Test number:** 1.3.1 **Ref.:** 2.2/Q.764, 5.2.3.1/Q.931.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Unsuccessful call set-up – All circuits busy at the destination network
+
+**Purpose:** To verify that the call will be successfully released when all circuits are busy.
+
+**Pre-test conditions:** All circuits are busy in international, national or access circuit groups.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|---------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | REL Cause Ind.: No circuit available (34), location transit network (0011) or public network serving remote user (0100) or private network serving remote user (0101) or international network (0111) |
+| RLC | → | |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | REL Cause Ind.: No circuit available (34), location private network serving remote user (0101) |
+| RLC | → | |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that all resources are released.
+3. Repeat the test for speech and 3.1 kHz audio bearers.
+4. Repeat steps 1-3 with Networks A and B interchanged.
+
+**Test number:** 1.3.2 **Ref.:** 2.2/Q.764, 5.2.4/Q.931.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Unsuccessful call set-up – Dialing of an unallocated number
+
+**Purpose:** To verify that the call will be successfully released when an unallocated number is dialed.
+
+**Pre-test conditions:** Called number is an unallocated subscriber number.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|---------------|---|------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | REL Cause Ind.: Unallocated number (1), location public network serving remote user (0100) or private network serving remote user (0101) |
+| RLC | → | |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | REL Cause Ind.: Unallocated number (1), location public network serving remote user (0100) or private network serving remote user (0101) |
+| RLC | → | |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that all resources are released.
+3. Repeat the test for speech and 3.1 kHz audio bearers.
+4. Repeat steps 1-3 with Networks A and B interchanged.
+
+**Test number:** 1.3.3 **Ref.:** 2.2/Q.764, 5.2.4/Q.931.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Unsuccessful call set-up – No route to destination
+
+**Purpose:** To verify that the call will be successfully released when there is no route to destination.
+
+**Pre-test conditions:** Called party number has invalid country or national destination code.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-----------|---|--------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| | ← | REL Cause Ind.: No route to destination (3), location transit network (0011) or international network (0111) |
+| RLC | → | |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that all resources are released.
+3. Repeat the test for speech and 3.1 kHz audio bearers.
+4. Repeat steps 1-3 with Networks A and B interchanged.
+
+**Test number:** 1.3.4 **Ref.:** 2.2/Q.764, 5.2.5.1/Q.931.
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+**Title:** Unsuccessful call set-up – Calling to a busy subscriber
+**Purpose:** To verify that the call will be successfully released when dialing a busy subscriber.
+
+**Pre-test conditions:** The called termination is busy.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|---------------|-------|---------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← REL | Cause Ind.: User busy (17), location user (0000) or public network serving remote user (0100) or private network serving remote user (0101) |
+| RLC | → | |
+| Case b | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← REL | Cause Ind.: User busy (17), location user (0000) or public network serving remote user (0100) or private network serving remote user (0101) |
+| RLC | → | |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that all resources are released.
+3. Repeat the test for speech and 3.1 kHz audio bearers.
+4. Repeat steps 1-3 with Networks A and B interchanged.
+
+**Test number:** 1.3.5 **Ref.:** 2.2/Q.764, 5.2.4/Q.931.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Unsuccessful call set-up – Address incomplete
+
+**Purpose:** To verify that the call will be successfully released when the called number is incomplete.
+
+**Pre-test conditions:** The dialed number should be incomplete.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-----------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| | ← REL | Cause Ind.: Address incomplete (28), location international network (0111), transit network (0011), public network serving remote user (0100) or private network serving remote user (0101) |
+| RLC | → | |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that all resources are released.
+3. Repeat the test for speech and 3.1 kHz audio bearers.
+4. Repeat steps 1-3 with Networks A and B interchanged.
+
+**Test number:** 1.4.1 **Ref.:** 2.2/Q.764, 5.2.5.4/Q.931.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Abnormal situation during call – No response from the called party
+
+**Purpose:** To verify that the call will be successfully released when there is no response to the SETUP message from the called party.
+
+**Pre-test conditions:** Send no response to the SETUP message from called side.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|---------------|---|-------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | REL Cause Ind.: No user responding (18), location public network serving remote user (0100) or private network serving remote user (0101) |
+| RLC | → | |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | REL Cause Ind.: No user responding (18), location public network serving remote user (0100) or private network serving remote user (0101) |
+| RLC | → | |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that all resources are released after time equal to twice T303 (Q.931 network side).
+3. Repeat the test for speech and 3.1 kHz audio bearers.
+4. Repeat steps 1-3 with Networks A and B interchanged.
+
+**Test number:** 1.4.2 **Ref.:** 2.1.4/Q.764, 5.2.5.4/Q.931.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Abnormal situation during call – No answer from the called party (T9/Q.764 expiration)
+
+**Purpose:** To verify that the call will be successfully released when the T9/Q.764 wait for answer timer expires.
+
+**Pre-test conditions:** Arrange the stimulus such that the wait for answer timer will expire.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|---------------|---|-----------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| REL | → | Cause Ind.: No answer from user (19), location public network serving remote user (0100) or international network (0111) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that all resources are released.
+3. Repeat the test for speech and 3.1 kHz audio bearers.
+4. Repeat steps 1-3 with Networks A and B interchanged.
+
+**Test number:** 2.1.1 **Ref.:** 3/Q.731, 3.5.2.1.1.2/Q.951.
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+**Title:** Calling Line Identification – CLIP – network provided without calling party subaddress
+**Purpose:** To verify that CLI (network provided) can be correctly transferred in the Calling Party Number parameter.
+**Pre-test conditions:** 1. Arrange the stimulus such that the IAM generated contains a CLI-coded network provided and does not contain a calling party subaddress.
+ 2. Arrange the exchange data such that the requested CLIP is supported.
+
+#### **Expected message sequence**
+
+
+
+| Network A | | Network B |
+|---------------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number: network provided (11), Presentation allowed (00), calling party number present |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+
+⇐ COMMUNICATION ⇒
+
+| | | |
+|-----|---|-------------------------------------------------------------|
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify the calling party number IE in the SETUP message at Network B's UNI.
+3. Check the propriety of digital data transmission or speech.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 2.1.2 **Ref.:** 3/Q.731, 3.5.2.1.1.2/Q.951.
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+**Title:** Calling Line Identification – CLIP – network provided
+**Purpose:** To verify that CLI (network provided) and the calling party subaddress can be correctly transferred in the Calling Party Number and the Access Transport parameters.
+**Pre-test conditions:** 1. Arrange the stimulus such that the IAM generated contains a CLI-coded network provided and a calling party subaddress.
+2. Arrange the exchange data such that the requested CLIP is supported.
+
+#### **Expected message sequence**
+
+
+
+| Network A | Network B | |
+|--------------------------------------------------------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number: network provided (11), Presentation allowed (00), calling party number present, ATP: calling party subaddress |
+|
| | |
+| COT | → | Optional message |
+|
| | |
+| Case a | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+|
| | |
+| | ← ANM | |
+|
| | |
+| Case b | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+|
| | |
+| | ← CPG | Event Info: alerting (0000001) |
+|
| | |
+| | ← ANM | |
+|
| | |
+| Case c | ← CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ⇐ COMMUNICATION ⇒ | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+|
| | |
+| RLC | ← | |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify the calling party number and the calling party subaddress IEs in the SETUP message at Network B's UNI.
+3. Check the propriety of digital data transmission or speech.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 2.1.3 **Ref.:** 3/Q.731, 3.5.2.1.1.2/Q.951.
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+**Title:** Calling Line Identification – CLIP – user provided, verified and passed
+**Purpose:** To verify that CLI (user provided, verified and passed) and calling party subaddress can be correctly transferred in the Calling Party Number and Access Transport parameter.
+**Pre-test conditions:** 1. Arrange the stimulus such that the IAM generated contains a CLI-coded user provided, verified and passed and a calling party subaddress.
+ 2. Arrange exchange data such that the requested CLIP is supported.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-------------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | ➔ | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number: user provided, verified and passed (01), Presentation allowed (00), calling party number present, ATP: calling party subaddress |
+| COT | ➔ | Optional message |
+| Case a | ⬅ | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ⬅ | ANM |
+| Case b | ⬅ | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ⬅ | CPG Event Info: alerting (0000001) |
+| | ⬅ | ANM |
+| Case c | ⬅ | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ⇐ COMMUNICATION ⇒ | | |
+| REL | ➔ | Cause Ind.: Normal call release (16), location user (0000) |
+| | ⬅ | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+- Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+- Verify the calling party number and the calling party subaddress IEs in the SETUP message at Network B's UNI.
+- Check the propriety of digital data transmission or speech.
+- Clear the call from Network A's UNI.
+- Check that all resources are released.
+- Repeat the test for speech and 3.1 kHz audio bearers.
+- Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 2.1.4 **Ref.:** 3/Q.731, 3.5.2.1.1.3/Q.951.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Calling Line Identification – CLIP – user provided, not verified
+
+**Purpose:** To verify that CLI (network provided), the additional Calling Party Number (user provided, not verified) and the calling party subaddress can be correctly transferred in the Calling Party Number, Generic Number and Access Transport parameters.
+
+**Pre-test conditions:**
+
+1. Arrange the stimulus such that the IAM generated contains a CLI-coded user provided, not verified and a calling party subaddress.
+2. Arrange exchange data such that the requested CLIP is supported.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number: network provided (11), Presentation allowed (00), calling party number present, Generic number: number qualifier indicator: additional calling party number (0000110), user provided, not verified (00), Presentation allowed (00), generic number present, ATP: calling party subaddress |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← COMMUNICATION ⇒ | | |
+| REL | → | Cause Ind.: Normal call release (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify the calling party number IE with the content of the generic number and the calling party subaddress IE and possibly a second calling party number IE in the SETUP message at Network B's UNI.
+3. Check the propriety of digital data transmission or speech.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+#### **Test description (Comb):**
+
+1. Make a 64 kbit/s call from Network A's (ISUP'92) UNI to Network B's (Q.767) UNI.
+2. Verify the calling party number and the calling party subaddress IEs in the SETUP message at Network B's UNI.
+3. Check the propriety of digital data transmission or speech.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+
+**Test number:** 2.1.5 **Ref.:** 4/Q.731, 4.5.2.2.1/Q.951.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Calling Line Identification – CLIR – network provided – without calling party subaddress
+
+**Purpose:** To verify that a restricted CLI (network provided) can be correctly transferred in the Calling Party Number parameter and that its contents will not be presented at Network B's UNI.
+
+**Pre-test conditions:**
+
+1. Arrange the stimulus such that the IAM generated contains a CLI network provided.
+2. Arrange exchange data such that the requested CLIR is supported.
+
+#### **Expected message sequence**
+
+
+
+| Network A | | Network B |
+|---------------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number: network provided (11), Presentation restricted (01), calling party number present |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+
+⇐ COMMUNICATION ⇒
+
+| | | |
+|-----|---|-------------------------------------------------------------|
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify that the calling party number IE indicates presentation restricted and does not contain any number digit in the SETUP message at Network B's UNI.
+3. Check the propriety of digital data transmission or speech.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 2.1.6 **Ref.:** 4/Q.731, 4.5.2.2.1/Q.951.
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+**Title:** Calling Line Identification – CLIR – network provided
+**Purpose:** To verify that a restricted CLI (network provided) and calling party subaddress can be correctly transferred in the Calling Party Number and Access Transport parameter and that its contents will not be presented at Network B's UNI.
+**Pre-test conditions:**
+
+1. Arrange the stimulus such that the IAM generated contains a CLI-network provided, and the calling party subaddress.
+2. Arrange exchange data such that the requested CLIR is supported.
+
+#### **Expected message sequence**
+
+
+
+| Network A | | Network B |
+|---------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number: network provided (11), Presentation restricted (01), calling party number present, ATP: calling party subaddress |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+
+⇐ COMMUNICATION ⇒
+
+| | | |
+|-----|---|-------------------------------------------------------------|
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify that the calling party number IE indicates presentation restricted and does not contain any number digit and calling party subaddress IE in the SETUP message at Network B's UNI.
+3. Check the propriety of digital data transmission or speech.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 2.1.7 **Ref.:** 4/Q.731, 4.5.2.2.1/Q.951.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Calling Line Identification – CLIR – user provided, verified and passed
+
+**Purpose:** To verify that a restricted CLI (user provided, verified and passed) and calling party subaddress can be correctly transferred in the Calling Party Number and Access Transport parameter.
+
+**Pre-test conditions:**
+
+1. Arrange the stimulus such that the IAM generated contains a CLI user provided, verified and passed and calling party subaddress.
+2. Arrange exchange data such that the requested CLIR is supported.
+
+#### **Expected message sequence**
+
+
+
+| Network A | | Network B |
+|---------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | ➔ | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number: user provided, verified and passed (01), calling party number present, Presentation restricted (01), ATP: calling party subaddress |
+| COT | ➔ | Optional message |
+| Case a | ⬅ | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ⬅ | ANM |
+| Case b | ⬅ | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ⬅ | CPG Event Info: alerting (0000001) |
+| | ⬅ | ANM |
+| Case c | ⬅ | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+
+⇐ COMMUNICATION ⇒
+
+| | | |
+|-----|---|-------------------------------------------------------------|
+| REL | ➔ | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ⬅ | RLC |
+
+#### **Test description(ISUP'92, Comb):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify that the calling party number IE indicates presentation restricted and does not contain any number digit and calling party subaddress IE in the SETUP message at Network B's UNI.
+3. Check the propriety of digital data transmission or speech.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 2.1.8 **Ref.:** 4/Q.731, 4/Q.951.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Calling Line Identification – CLIR – user provided, not verified
+
+**Purpose:** To verify that a restricted CLI (user provided, not verified), the additional Calling Party Number and the calling party subaddress can be correctly transferred in the Calling Party Number, Generic number and Access Transport parameter.
+
+- Pre-test conditions:**
+1. Arrange the stimulus such that the IAM generated contains a CLI-network provided, a generic number user provided, not verified and a calling party subaddress.
+ 2. Arrange exchange data such that the requested CLIR is supported.
+
+#### **Expected message sequence**
+
+
+
+| Network A | Network B |
+|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number: network provided (11), Presentation restricted (01), calling party number present, Generic number: number qualifier indicator: additional calling party number (0000110), user provided, not verified (00), generic number present, Presentation restricted (01), ATP: calling party subaddress |
+| COT → | Optional message |
+| ← Case a | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← | ANM |
+| ← Case b | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← | CPG Event Info: alerting (0000001) |
+| ← | ANM |
+| ← Case c | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+
+← COMMUNICATION →
+
+| | |
+|-------|-------------------------------------------------------------|
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← | RLC |
+
+#### **Test description (ISUP'92):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify that the calling party number IE indicates presentation restricted and does not contain any number digit and calling party subaddress IE in the SETUP message at Network B's UNI.
+3. Check the propriety of digital data transmission or speech.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+#### **Test description (Comb):**
+
+1. Make a 64 kbit/s call from Network A's (ISUP'92) UNI to Network B's (Q.767) UNI.
+2. Verify that the calling party number IE indicates presentation restricted and does not contain any number digit and calling party subaddress IE in the SETUP message at Network B's UNI.
+3. Check the propriety of digital data transmission or speech.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+
+**Test number:** 2.2.1 **Ref.:** 8/Q.731, 8/Q.951.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Subaddressing – Transport of called party subaddress
+
+**Purpose:** To verify that called party subaddress can be transferred in the Access Transport parameter.
+
+- Pre-test conditions:**
+1. Arrange the stimulus such that the IAM generated contains called party subaddress.
+ 2. Arrange exchange data such that the requested subaddressing is supported.
+
+#### Expected message sequence
+
+
+
+| | Network A | Network B |
+|---------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------|
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), ATP: called party subaddress |
+| | COT → | Optional message |
+| Case a | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← ANM | |
+| Case b | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← CPG | Event Info: alerting (0000001) |
+| | ← ANM | |
+| Case c | ← CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+
+← COMMUNICATION →
+
+| | | |
+|--|-------|-------------------------------------------------------------|
+| | REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← RLC | |
+
+#### Test description (ISUP'92, Comb):
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify the called party subaddress IE in the SETUP message at Network B's UNI.
+3. Check the propriety of digital data transmission or speech.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 2.3.1 **Ref.:** 5/Q.731, 5/Q.951.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Connected Line Identification – COL – Request
+
+**Purpose:** To verify that a request for COL can be correctly transferred in the Optional Forward Call Indicators parameter.
+
+**Pre-test conditions:**
+
+1. Arrange exchange data such that the IAM generated contains a request for COL.
+2. Arrange exchange data such that the requested COLP is supported.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-------------------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), OFCI: COL requested (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM Connected Number: Presentation allowed (00), network provided (11), connected number present |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM Connected Number: Presentation allowed (00), network provided (11), connected number present |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), Connected Number: Presentation allowed (00), network provided (11), connected number present |
+| ← COMMUNICATION → | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify that the COL is requested in Optional FCI parameter in the IAM.
+3. Check the propriety of digital data transmission or speech.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 2.3.2 **Ref.:** 5/Q.731, 5/Q.951.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Connected Line Identification – COLP – network provided
+
+**Purpose:** To verify that a COL (network provided) and a connected subaddress can be correctly transferred in the Connected Number and Access Transport parameters.
+
+- Pre-test conditions:**
+1. Arrange exchange data such that the IAM generated contains a request for COL.
+ 2. Arrange the stimulus such that the ANM (CON) generated contains a COL – network provided, presentation allowed and the connected subaddress.
+ 3. Arrange exchange data such that the requested COLP is supported.
+
+#### **Expected message sequence**
+
+
+
+| Network A | | Network B | |
+|---------------|---|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | ➔ | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), OFCI: COL requested (1) |
+| COT | ➔ | | Optional message |
+| Case a | ⬅ | ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ⬅ | ANM | Connected Number: Presentation allowed (00), network provided (11), connected number present, ATP: connected subaddress |
+| Case b | ⬅ | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ⬅ | CPG | Event Info: alerting (0000001) |
+| | ⬅ | ANM | Connected Number: Presentation allowed (00), network provided (11), connected number present, ATP: connected subaddress |
+| Case c | ⬅ | CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), Connected Number: Presentation allowed (00), network provided (11), connected number present, ATP: connected subaddress |
+
+⇐ COMMUNICATION ⇑
+
+| | | | |
+|-----|---|-----|-------------------------------------------------------------|
+| REL | ➔ | | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ⬅ | RLC | |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI .
+2. Check the propriety of digital data transmission or speech.
+3. Check the presence of the connected number and the connected subaddress IEs in the CONNECT message at Network A's UNI.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 2.3.3 **Ref.:** 5/Q.731, 5/Q.951.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Connected Line Identification – COLP – user provided, verified and passed
+
+**Purpose:** To verify that a COL (user provided, verified and passed) and a connected subaddress can be correctly transferred in the Connected Number and Access Transport parameters.
+
+**Pre-test conditions:**
+
+1. Arrange exchange data such that the IAM generated contains a request for COL.
+2. Arrange exchange data such that the ANM (CON) generated contains a COL user provided, verified and passed and the connected subaddress.
+3. Arrange exchange data such that the requested COLP is supported.
+
+#### **Expected message sequence**
+
+
+
+| Network A | | Network B | |
+|---------------|---|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | ➔ | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), OFCI: COL requested (1) |
+| COT | ➔ | | Optional message |
+| Case a | ⬅ | ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ⬅ | ANM | Connected Number: Presentation allowed (00), user provided, verified and passed (01), connected number present, ATP: connected subaddress |
+| Case b | ⬅ | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ⬅ | CPG | Event Info: alerting (0000001) |
+| | ⬅ | ANM | Connected Number: Presentation allowed (00), user provided, verified and passed (01), connected number present, ATP: connected subaddress |
+| Case c | ⬅ | CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), Connected Number: Presentation allowed (00), user provided, verified and passed (01), connected number present, ATP: connected subaddress |
+
+⇐ COMMUNICATION ⇒
+
+| | | | |
+|-----|---|-----|-------------------------------------------------------------|
+| REL | ➔ | | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ⬅ | RLC | |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI .
+2. Check the propriety of digital data transmission or speech.
+3. Check the presence of the connected number and the connected subaddress IEs in the CONNECT message at Network A's UNI.
+4. Clear the call from Network A's UNI.
+
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 2.3.4 **Ref.:** 5/Q.731, 5/Q.951.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Connected Line Identification – COLP – user provided, not verified
+
+**Purpose:** To verify that a COL (network provided), an additional connected number (user provided, not verified) and a connected subaddress can be correctly transferred in the Connected Number, Generic Number and Access Transport parameters.
+
+- Pre-test conditions:**
+1. Arrange exchange data such that the IAM generated contains a request for COL.
+ 2. Arrange the stimulus such that the ANM (CON) generated contains a COL network provided, a generic number user provided, not verified and a connected subaddress.
+ 3. Arrange exchange data such that the requested COLP is supported.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|---------------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | ➔ | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), OFCI: COL requested (1) |
+| COT | ➔ | Optional message |
+| Case a | ⬅ | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ⬅ | ANM Connected Number: Presentation allowed (00), network provided (11), connected number present, Generic number: number qualifier indicator: additional connected number (0000101), presentation allowed (00), user provided, not verified (00), generic number present, ATP: connected subaddress |
+| Case b | ⬅ | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ⬅ | CPG Event Info: alerting (0000001) |
+| | ⬅ | ANM Connected Number: Presentation allowed (00), network provided (11), connected number present, Generic number: number qualifier indicator: additional connected number (0000101), presentation allowed (00), user provided, not verified (00), generic number present, ATP: connected subaddress |
+| Case c | ⬅ | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), Connected Number: Presentation allowed (00), network provided (11), connected number present, Generic number: number qualifier indicator: additional connected number (0000101), presentation allowed (00), user provided, not verified (00), generic number present, ATP: connected subaddress |
+
+⬅ COMMUNICATION ➔
+
+| | | |
+|-----|-----|-------------------------------------------------------------|
+| REL | ➔ | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ⬅ | RLC | |
+
+#### **Test description (ISUP'92):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check the propriety of digital data transmission or speech.
+3. Check the presence of the connected number, user provided, not verified and the connected subaddress IEs in the CONNECT message at Network A's UNI.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+#### **Test description (Comb):**
+
+1. Make a 64 kbit/s call from Network A's (ISUP'92) UNI to Network B's (Q.767) UNI.
+2. Check the propriety of digital data transmission or speech.
+3. Check the presence of the connected number, network provided and the connected subaddress IEs in the CONNECT message at Network A's UNI.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+
+**Test number:** 2.3.5 **Ref.:** 6/Q.731, 6/Q.951.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Connected Line Identification – COLR – network provided
+
+**Purpose:** To verify that a restricted COL (network provided) and a connected subaddress can be correctly transferred in the Connected Number and Access Transport parameters.
+
+- Pre-test conditions:**
+1. Arrange exchange data such that the IAM generated contains a request for COL.
+ 2. Arrange the stimulus such that the ANM (CON) generated contains a COL network provided and a connected subaddress.
+ 3. Arrange exchange data such that the requested COLR is supported.
+
+#### Expected message sequence
+
+| Network A | | Network B | |
+|---------------|---|----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), OFCI: COL requested (1) | |
+| COT | → | Optional message | |
+| Case a | ← | ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM | Connected Number: Presentation restricted (01), network provided (11), connected number present, ATP: connected subaddress |
+| Case b | ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG | Event Info: alerting (0000001) |
+| | ← | ANM | Connected Number: Presentation restricted (01), network provided (11), connected number present, ATP: connected subaddress |
+| Case c | ← | CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), Connected Number: Presentation restricted (01), network provided (11), connected number present, ATP: connected subaddress |
+
+⇐ COMMUNICATION ⇒
+
+| | | | |
+|-----|---|-------------------------------------------------------------|--|
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) | |
+| | ← | RLC | |
+
+#### Test description (ISUP'92, Comb):
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check the propriety of digital data transmission or speech.
+3. Verify that the connected number IE indicates presentation restricted and does not contain any number digit and connected subaddress in the CONNECT at Network A's UNI.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 2.3.6 **Ref.:** 6/Q.731, 6/Q.951.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Connected Line Identification – COLR – user provided, verified and passed
+
+**Purpose:** To verify that a restricted COL (user provided, verified and passed) and a connected subaddress can be correctly transferred in the Connected Number and Access Transport parameter.
+
+- Pre-test conditions:**
+1. Arrange exchange data such that the IAM generated contains a request for COL.
+ 2. Arrange the stimulus such that the ANM (CON) generated contains a COL user provided, verified and passed and a connected subaddress.
+ 3. Arrange exchange data such that the requested COLR is supported.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|---------------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), OFCI: COL requested (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM Connected Number: Presentation restricted (01), user provided, verified and passed (01), connected number present, ATP: connected subaddress |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM Connected Number: Presentation restricted (01), user provided, verified and passed (01), connected number present, ATP: connected subaddress |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), Connected Number: Presentation restricted (01), user provided, verified and passed (01), connected number present, ATP: connected subaddress |
+
+⇐ COMMUNICATION ⇒
+
+| | | |
+|-----|---|-------------------------------------------------------------|
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI .
+2. Check the propriety of digital data transmission or speech.
+3. Verify that the connected number IE indicates presentation restricted and does not contain any number digit and connected subaddress in the CONNECT at Network A's UNI.
+
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 2.3.7 **Ref.:** 6/Q.731, 6/Q.951.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Connected Line Identification – COLR – user provided, not verified
+
+**Purpose:** To verify that a restricted COL (network provided), an additional connected number (user provided, not verified) and a connected subaddress can be correctly transferred in the Connected Number, the Generic Number and the Access Transport parameter.
+
+- Pre-test conditions:**
+1. Arrange exchange data such that the IAM generated contains a request for COL.
+ 2. Arrange the stimulus such that the ANM (CON) generated contains a COL network provided, a generic number user provided, not verified and a connected subaddress.
+ 3. Arrange exchange data such that the requested COLR is supported.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-------------------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), OFCI: COL requested (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM Connected Number: Presentation restricted (01), network provided (11), connected number present, Generic number: number qualifier indicator: additional connected number (0000101), presentation restricted (01), user provided, not verified (00), generic number present, ATP: connected subaddress |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM Connected Number: Presentation restricted (01), network provided (11), connected number present, Generic number: number qualifier indicator: additional connected number (0000101), presentation restricted (01), user provided, not verified (00), generic number present, ATP: connected subaddress |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), Connected Number: Presentation restricted (01), network provided (11), connected number present, Generic number: number qualifier indicator: additional connected number (0000101), presentation restricted (01), user provided, not verified (00), generic number present, ATP: connected subaddress |
+| ⇐ COMMUNICATION ⇑ | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check the propriety of digital data transmission or speech.
+3. Verify that the connected number IE indicates presentation restricted and does not contain any number digit and connected subaddress in the CONNECT at Network A's UNI.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+#### **Test description (Comb):**
+
+1. Make a 64 kbit/s call from Network A's (ISUP'92) UNI to Network B's (Q.767) UNI.
+2. Check the propriety of digital data transmission or speech.
+3. Verify that the connected number IE indicates presentation restricted and does not contain any number digit and connected subaddress in the CONNECT at Network A's UNI.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+
+**Test number:** 2.3.8 **Ref.:** 5/Q.731, 5/Q.951.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Connected Line Identification – COL received but not requested
+
+**Purpose:** To verify that if a COL is received when it was not requested, the call is not rejected.
+
+- Pre-test conditions:**
+1. Arrange exchange data such that the IAM generated does not contain a request for COL.
+ 2. Arrange the stimulus such that the ANM (CON) generated contains a COL.
+ 3. Arrange exchange data such that the requested COL is supported.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM Connected Number: Presentation indicator (xx), screening indicator (xx), connected number present |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM Connected Number: Presentation indicator (xx), screening indicator (xx), connected number present |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), Connected Number: Presentation indicator (xx), screening indicator (xx), connected number present |
+| ← COMMUNICATION → | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check the propriety of digital data transmission or speech.
+3. Clear the call from Network A's UNI.
+4. Check that all resources are released.
+5. Repeat the test for speech and 3.1 kHz audio bearers.
+6. Repeat steps 1-5 with Networks A and B interchanged.
+
+**Test number:** 2.3.9 **Ref.:** 5/Q.951.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Connected Line Identification – COL not available
+
+**Purpose:** To verify that an "address not available" COL can be correctly transferred in the Connected Number parameter.
+
+- Pre-test conditions:**
+1. Arrange exchange data such that the IAM generated contains a request for COL.
+ 2. Arrange the stimulus such that the ANM (CON) generated contains COL not available.
+ 3. Arrange exchange data such that the requested COLP is supported.
+
+#### Expected message sequence
+
+| Network A | | Network B |
+|-------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), OFCI: COL requested (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM Connected Number: Address not available (10), network provided (11) |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM Connected Number: Address not available (10), network provided (11) |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), Connected Number: Address not available (10), network provided (11) |
+| ⇐ COMMUNICATION ⇒ | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### Test description (ISUP'92, Comb):
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI .
+2. Check the propriety of digital data transmission or speech.
+3. Check the connected number not available information at Network A's UNI.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 2.4.1 **Ref.:** 1/Q.735, 1/Q.955.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Closed User Group – Decentralized – CUG call with outgoing access allowed (both UNIs belong to the same CUG)
+
+**Purpose:** To verify that the parameters necessary for a CUG call with OFCI: Outgoing access allowed can be correctly transferred and that the call is successful.
+
+**Pre-test conditions:** Arrange exchange data such that the requested CUG is supported and both parties belong to the same CUG.
+
+#### Expected message sequence
+
+| Network A | Network B |
+|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) OFCI: CUG Call Indicator Outgoing access allowed (10), CUG interlock code included |
+| COT → | Optional message |
+| Case a ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← ANM | |
+| Case b ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← CPG | Event Info: alerting (0000001) |
+| ← ANM | |
+| Case c ← CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ⇐ COMMUNICATION ⇒ | |
+| REL → | Cause Ind.: Normal Call Clearing (16), location user (0000) |
+| ← RLC | |
+
+#### Test description (ISUP'92, Comb):
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check the propriety of digital data transmission or speech.
+3. Clear the call from Network A's UNI.
+4. Check that all resources are released.
+5. Repeat the test for speech and 3.1 kHz audio bearers.
+6. Repeat steps 1-5 with Networks A and B interchanged.
+
+**Test number:** 2.4.2 **Ref.:** 1/Q.735, 1/Q.955.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Closed User Group – Decentralized – CUG call with outgoing access allowed (called party not in a CUG)
+
+**Purpose:** To verify that the parameters necessary for a CUG call with OFCI: Outgoing access allowed can be correctly transferred and that the call is successful.
+
+**Pre-test conditions:** Arrange exchange data such that the requested CUG is supported and only UNI A belongs to this CUG.
+
+#### **Expected message sequence**
+
+
+
+| Network A | Network B |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|
+| → IAM FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) OFCI: CUG Call Indicator Outgoing access allowed (10), CUG interlock code included | |
+| → COT Optional message | |
+| Case a | ← ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← ANM |
+| Case b | ← ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← CPG Event Info: alerting (0000001) |
+| | ← ANM |
+| Case c | ← CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ⇐ COMMUNICATION ⇐ | |
+| → REL Cause Ind.: Normal Call Clearing (16), location user (0000) | |
+| ← RLC | |
+
+#### **Test description (ISUP'92, Comb):**
+
+- 1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+- 2. Check the propriety of digital data transmission or speech.
+- 3. Clear the call from Network A's UNI.
+- 4. Check that all resources are released.
+- 5. Repeat the test for speech and 3.1 kHz audio bearers.
+- 6. Repeat steps 1-5 with Networks A and B interchanged.
+
+**Test number:** 2.4.3 **Ref.:** 1/Q.735, 1/Q.955.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Closed User Group – Decentralized – CUG call with outgoing access allowed (one network supports CUG)
+
+**Purpose:** To verify that the parameters necessary for a CUG call with OFCI: Outgoing access allowed can be correctly transferred.
+
+**Pre-test conditions:** Only Network A supports CUG.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-------------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), OFCI: CUG Call Indicator: Outgoing access allowed (10), CUG interlock code included |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← COMMUNICATION → | | |
+| REL | → | Cause Ind.: Normal Call Clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check the propriety of digital data transmission or speech.
+3. Clear the call from Network A's UNI.
+4. Check that all resources are released.
+5. Repeat the test for speech and 3.1 kHz audio bearers.
+
+**Test number:** 2.4.4 **Ref.:** 1/Q.735, 1/Q.955.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Closed User Group – Decentralized – CUG call with outgoing access not allowed, to a network offering CUG (called party in same CUG)
+
+**Purpose:** To verify that the parameters necessary for a CUG call with Outgoing access not allowed can be correctly transferred.
+
+**Pre-test conditions:**
+
+1. Both networks must offer CUG.
+2. Arrange exchange data such that the requested CUG is supported and the called party is in same CUG.
+3. Arrange exchange data such that no incoming calls barred on both ends.
+
+#### Expected message sequence
+
+| Network A | | Network B |
+|-------------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), ISUP required all the way (10), OFCI: CUG Call Indicator: Outgoing access not allowed (11), CUG interlock code included |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← COMMUNICATION → | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### Test description (ISUP'92, Comb):
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check the propriety of digital data transmission or speech.
+3. Clear the call from Network A's UNI.
+4. Check that all resources are released.
+5. Repeat the test for speech and 3.1 kHz audio bearers.
+6. Repeat steps 1-5 with Networks A and B interchanged.
+
+**Test number:** 2.4.5 **Ref.:** 1.5.2.5.1/Q.735, 1/Q.955.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Closed User Group – Decentralized – CUG call with outgoing access not allowed, to a network offering CUG (called party outside CUG)
+
+**Purpose:** To verify that the parameters necessary for a CUG call with Outgoing access not allowed can be correctly transported.
+
+**Pre-test conditions:**
+
+1. Both networks must offer CUG.
+2. Arrange exchange data such that the requested CUG is supported and the called party is not in CUG.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-----------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), ISUP required all the way (10), OFCI: CUG Call Indicator: Outgoing access not allowed (11), CUG interlock code included |
+| COT | → | Optional message |
+| | ← | REL Cause Ind.: User not member of CUG (87), location public network serving remote user (0100) |
+| RLC | → | |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that the connection is released from Network B.
+3. Check that all resources are released.
+4. Repeat the test for speech and 3.1 kHz audio bearers.
+5. Repeat steps 1-4 with Networks A and B interchanged.
+
+**Test number:** 2.4.6 **Ref.:** 1.5.2.5.1/Q.735, 1/Q.955.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Closed User Group – Decentralized – CUG call with outgoing access allowed, to a network offering CUG (called party in a different CUG, no incoming access allowed)
+
+**Purpose:** To verify that the parameters necessary for a CUG call with Outgoing access allowed can be correctly transported and that the call is rejected by Network B.
+
+- Pre-test conditions:**
+1. Both networks must offer CUG.
+ 2. Arrange exchange data such that the requested CUG is supported and the called party belongs to a different CUG.
+ 3. Arrange exchange data such that incoming access is not allowed at Network B's UNI.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-----------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), OFCI: CUG Call Indicator: Outgoing access allowed (10), CUG interlock code included |
+| COT | → | Optional message |
+| | ← | REL Cause Ind.: User not member of CUG (87), location public network serving remote user (0100) |
+| RLC | → | |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that the connection is released from Network B.
+3. Check that all resources are released.
+4. Repeat the test for speech and 3.1 kHz audio bearers.
+5. Repeat steps 1-4 with Networks A and B interchanged.
+
+**Test number:** 2.4.7 **Ref.:** 1/Q.735, 1/Q.955.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Closed User Group – Decentralized – CUG call with outgoing access allowed, to a network offering CUG (called party in a different CUG, incoming access allowed)
+
+**Purpose:** To verify that the parameters necessary for a CUG call with OFCI: Outgoing access allowed can be correctly transferred and the call is successful.
+
+**Pre-test conditions:**
+
+1. Both networks support CUG.
+2. Arrange exchange data such that Network B's UNI belongs to a different CUG.
+3. Arrange exchange data such that incoming access is allowed at Network B's UNI.
+
+#### Expected message sequence
+
+
+
+| Network A | | Network B | |
+|---------------|---|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), OFCI: CUG Call Indicator: Outgoing access allowed (10), CUG interlock code included |
+| COT | → | | Optional message |
+| Case a | ← | ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM | |
+| Case b | ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG | Event Info: alerting (0000001) |
+| | ← | ANM | |
+| Case c | ← | CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+
+⇐ COMMUNICATION ⇒
+
+| | | | |
+|-----|---|-----|-------------------------------------------------------------|
+| REL | → | | Cause Ind.: Normal Call Clearing (16), location user (0000) |
+| | ← | RLC | |
+
+#### Test description (ISUP'92, Comb):
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check the propriety of digital data transmission or speech.
+3. Clear the call from Network A's UNI.
+4. Check that all resources are released.
+5. Repeat the test for speech and 3.1 kHz audio bearers.
+6. Repeat steps 1-5 with Networks A and B interchanged.
+
+**Test number:** 2.4.8 **Ref.:** 1.5.2.5.1/Q.735, 1/Q.955.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Closed User Group – Decentralized – CUG call with outgoing access not allowed, to a network offering CUG (called party in same CUG, incoming calls barred at Network B's UNI)
+
+**Purpose:** To verify that the parameters necessary for a CUG call with Outgoing access not allowed can be correctly transferred and that the call is rejected.
+
+**Pre-test conditions:**
+
+1. Both networks must offer CUG.
+2. Arrange exchange data such that the requested CUG is supported and the called party is in the same CUG.
+3. Arrange exchange data such that incoming calls are barred at Network B's UNI.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-----------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), ISUP required all the way (10), OFCI: CUG Call Indicator: Outgoing access not allowed (11), CUG interlock code included |
+| COT | → | Optional message |
+| | ← | REL Cause Ind.: Incoming calls barred within CUG (55), location public network serving remote user (0100) |
+| RLC | → | |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that call is rejected at Network B.
+3. Check that all resources are released.
+4. Repeat the test for speech and 3.1 kHz audio bearers.
+5. Repeat steps 1-4 with Networks A and B interchanged.
+
+**Test number:** 2.4.9 **Ref.:** 1.5.2.4.2/Q.735, 1/Q.955.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Closed User Group – Decentralized – CUG call with outgoing access not allowed, to a network not offering CUG.
+
+**Purpose:** To verify that the parameters necessary for a CUG call with Outgoing access not allowed can be correctly transferred and that call is rejected by Network B.
+
+**Pre-test conditions:**
+
+1. Only Network A must offer CUG.
+2. Arrange the exchange data such that Network A's UNI is member of a CUG.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-----------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), ISUP required all the way (10), OFCI: CUG Call Indicator: Outgoing access not allowed (11), CUG interlock code included |
+| COT | → | Optional message |
+| | ← | REL Cause Ind.: Facility rejected (29), location international network (0111) – see Note |
+| RLC | → | |
+
+NOTE – For ISUP'92 the diagnostic parameter "CUG without outgoing access" is included in the REL.
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that the connection is released from Network B's ISC.
+3. Check that all resources are released.
+4. Repeat the test for speech and 3.1 kHz audio bearers.
+
+**Test number:** 2.4.10 **Ref.:** 1.5.2.5.1/Q.735, 1/Q.955.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Closed User Group – Decentralized – Non-CUG call towards a CUG destination with incoming access not allowed
+
+**Purpose:** To verify that the call is rejected in Network B.
+
+- Pre-test conditions:**
+1. Arrange exchange data such that the requested CUG is supported in Network B and the called party belongs to a CUG.
+ 2. Arrange exchange data such that incoming access is not allowed at Network B's UNI.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-----------|---|---------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| | ← | REL Cause Ind.: User not member of CUG (87), location public network serving remote user (0100) |
+| RLC | → | |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that the connection is released by Network B.
+3. Check that all resources are released.
+4. Repeat the test for speech and 3.1 kHz audio bearers.
+5. Repeat steps 1-4 with Networks A and B interchanged.
+
+**Test number:** 2.4.11 **Ref.:** 1/Q.735, 1/Q.955.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Closed User Group – Decentralized – Non-CUG call towards a CUG destination with incoming access allowed
+
+**Purpose:** To verify that the call can be successfully established.
+
+**Pre-test conditions:**
+
+1. Arrange exchange data such that the requested CUG is supported in Network B.
+2. Arrange exchange data such that incoming access is allowed at Network B's UNI.
+
+#### Expected message sequence
+
+
+
+| | Network A | Network B |
+|-------------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------|
+| | IAM | → FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| | COT | → Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← COMMUNICATION → | | |
+| | REL | → Cause Ind.: Normal Call Clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### Test description (ISUP'92, Comb):
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check the propriety of digital data transmission or speech.
+3. Clear the call from Network A's UNI.
+4. Check that all resources are released.
+5. Repeat the test for speech and 3.1 kHz audio bearers.
+6. Repeat steps 1-5 with Networks A and B interchanged.
+
+**Test number:** 2.5.1 **Ref.:** 7/Q.731, 7/Q.951.
+
+**Config.:** Multiple ISDN Accesses (See Figure 2)
+
+**Title:** Malicious Call Identification – Successful request
+
+**Purpose:** To verify that in case of MCID request the appropriate parameters are received at Network B's local exchange.
+
+**Pre-test conditions:**
+
+1. Arrange the exchange data such that the requested MCID is supported at Network B's UNI.
+2. CLI should not be included in the IAM.
+
+#### Expected message sequence
+
+| Network A | | Network B |
+|-------------------|---|-----------------------------------------------------------------------------------------------------------------------------------|
+| IAM | ➔ | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), No CLI is included |
+| COT | ➔ | Optional message |
+| | ⬅ | IDR MCID request indicator: MCID requested (1) |
+| IRS | ➔ | MCID response indicator: MCID included (1), Calling party number included, ATP included, Generic number included |
+| Case a | ⬅ | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ⬅ | ANM |
+| Case b | ⬅ | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ⬅ | CPG Event Info: alerting (0000001) |
+| | ⬅ | ANM |
+| Case c | ⬅ | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ⬅ COMMUNICATION ➔ | | |
+| REL | ➔ | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ⬅ | RLC |
+
+#### Test description (ISUP'92):
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that IDR is received at Network A's local exchange.
+3. Check that IRS is received at Network B's local exchange.
+4. Verify that Network B's UNI is alerted.
+5. Check the propriety of data transmission or speech.
+6. Invoke MCID service at Network B's UNI if appropriate and check that the invocation was initiated.
+7. Check that information of IRS are registered in Network B.
+
+8. Check that information of IRS is not available at Network B's UNI.
+9. Clear the call from Network A's UNI.
+10. Check that all resources are released.
+11. Repeat the test for speech and 3.1 kHz audio bearers.
+12. Repeat steps 1-11 with invocation during disconnect state and with permanent registration.
+13. Repeat steps 1-12 with Networks A and B interchanged.
+
+**Test number:** 2.5.2 **Ref.:** 7/Q.731, 7/Q.951.
+
+**Config.:** Multiple ISDN Accesses (See Figure 2)
+
+**Title:** Malicious Call Identification – Unsuccessful request, MCID information not available or not supported
+
+**Purpose:** To verify that in case of MCID request, the IRS message is received at Network B's local exchange without MCID information.
+
+- Pre-test conditions:**
+1. Arrange the exchange data such that the requested MCID is supported at Network B's UNI.
+ 2. CLI should not be included in the IAM.
+ 3. MCID information is not available at Network A.
+
+#### Expected message sequence
+
+| Network A | | Network B |
+|-------------------|---|-----------------------------------------------------------------------------------------------------------------------------------|
+| IAM | ➔ | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), No CLI is included |
+| COT | ➔ | Optional message |
+| | ⬅ | IDR MCID request indicator: MCID requested (1) |
+| IRS | ➔ | MCID response indicator: MCID not included (0) |
+| Case a | ⬅ | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ⬅ | ANM |
+| Case b | ⬅ | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ⬅ | CPG Event Info: alerting (0000001) |
+| | ⬅ | ANM |
+| Case c | ⬅ | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ⬅ COMMUNICATION ➔ | | |
+| REL | ➔ | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ⬅ | RLC |
+
+#### Test description (ISUP'92):
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that IDR is received at Network A's local exchange.
+3. Check that IRS is received at Network B's local exchange.
+4. Verify that Network B's UNI is alerted.
+5. Check the propriety of data transmission or speech.
+6. Invoke MCID service at Network B's UNI if appropriate and check that the invocation was initiated.
+
+7. Clear the call from Network A's UNI.
+8. Check that no information is included in IRS.
+9. Check that all resources are released.
+10. Repeat the test for speech and 3.1 kHz audio bearers.
+11. Repeat steps 1-10 with invocation during disconnect state and with permanent registration.
+12. Repeat steps 1-11 with Networks A and B interchanged.
+
+**Test number:** 2.5.3 **Ref.:** 7/Q.731, 7/Q.951.
+
+**Config.:** Multiple ISDN Accesses (See Figure 2)
+
+**Title:** Malicious Call Identification – Unsuccessful request, no response to IDR
+
+**Purpose:** To verify that the call continues according to the basic call procedures after $T_{MCID}$ (T39) expired.
+
+- Pre-test conditions:**
+1. Arrange the exchange data such that the requested MCID is supported at Network B's UNI.
+ 2. CLI should not be included in the IAM.
+ 3. Network A should not reply to IDR.
+
+#### Expected message sequence
+
+
+
+| Network A | Network B |
+|---------------------|-------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), No CLI is included |
+| COT → | Optional message |
+| ← IDR | MCID request indicator: MCID requested (1) |
+| Case a ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← ANM | |
+| Case b ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← CPG | Event Info: alerting (0000001) |
+| ← ANM | |
+| Case c ← CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ⇐ COMMUNICATION ⇒ | |
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | |
+
+#### Test description (ISUP'92):
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that IDR is sent by Network B.
+3. Verify that Network B's UNI is alerted.
+4. Check that the call establishment continues after T39 expiry.
+5. Check the propriety of data transmission or speech.
+6. Invoke MCID service at Network B's UNI if appropriate and check that the invocation was initiated.
+7. Clear the call from Network A's UNI.
+8. Check that all resources are released.
+9. Repeat the test for speech and 3.1 kHz audio bearers.
+10. Repeat steps 1-9 with invocation during disconnect state and with permanent registration.
+11. Repeat steps 1-10 with Networks A and B interchanged.
+
+#### **Test description (Comb):**
+
+1. Make a 64 kbit/s call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check that IDR is sent by Network B.
+3. Verify that Network B's UNI is alerted.
+4. Check that the call establishment continues after T39 expiry.
+5. Check the propriety of data transmission or speech.
+6. Invoke MCID service at Network B's UNI if appropriate and check that the invocation was initiated.
+7. Clear the call from Network A's UNI.
+8. Check that all resources are released.
+9. Repeat the test for speech and 3.1 kHz audio bearers.
+10. Repeat steps 1-9 with invocation during disconnect state and with permanent registration.
+
+**Test number:** 2.6.1 **Ref.:** 2/Q.732, 2/Q.952 and 5.5.2.3.2/Q.952.
+
+**Config.:** Multiple ISDN Accesses (See Figure 3)
+
+**Title:** Call Forwarding Busy (network determined) – full notification
+
+**Purpose:** To verify that a call can be forwarded correctly if Network B encounters busy UNI B.
+
+- Pre-test conditions:**
+1. Arrange the exchange data such that the requested Call Forwarding busy is supported at Network B.
+ 2. Arrange exchange data such that all number parameters and notifications are delivered to the involved UNIs.
+ 3. Network B's UNI is busy.
+
+#### Expected message sequence
+
+| Network A | Network B | Network C |
+|---------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number present, Presentation allowed (00) |
+| COT → | | Optional message |
+| ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), GenNot: Call is diverting (1111011); Redirection number present, Call diversion Info: Notification subscription option, Presentation allowed with redirection number (010), Redirection reason user busy (0001) |
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Redirection Info: Redirecting ind. call diverted (011), Redirection counter (001), Redirecting reason user busy (0001); Redirecting number present, Presentation allowed (00); Original called number present, Presentation allowed (00); Calling party number present, Presentation allowed (00) |
+| | COT → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+| ← | CPG | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | ← | ANM |
+| ← | ANM | |
+
+Network A Network B Network C
+
+| | | | |
+|-------------------|-------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Case b | ← ACM | | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← CPG | | Optional message Event Info: Progress (0000010) |
+| | | ← CPG | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | ← CPG | | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | | ← ANM | |
+| | ← ANM | | |
+| Case c | ← CON | | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+| | ← ANM | | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+| ⇐ COMMUNICATION ⇒ | | | |
+| | REL → | | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | | REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← RLC | | |
+| | | ← RLC | |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that the call is diverted to Network C's UNI.
+3. Check that notification *Call forwarding on busy* is received at Network A's UNI.
+4. Check that the *Redirection number* and *call diversion information* parameters are correctly received at Network A's UNI.
+5. Check that the *Redirection information*, the *Original called number* and the *Redirecting number* parameters are correctly received at Network C's UNI.
+6. Check that call is established between Network A's UNI and Network C's UNI.
+7. Check the propriety of data transmission or speech.
+8. Clear the call from Network A's UNI.
+9. Check that all resources are released.
+10. Repeat the test for speech and 3.1 kHz audio bearers.
+11. Repeat steps 1-10 with Networks A and C interchanged.
+12. Repeat steps 1-11 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check that the call is diverted to Network C's (Q.767) UNI
+3. Check that call is established between Network A's UNI and Network C's UNI.
+4. Check the propriety of data transmission or speech.
+5. Clear the call from Network A's UNI.
+6. Check that all resources are released.
+7. Repeat the test for speech and 3.1 kHz audio bearers.
+8. Repeat steps 1-7 with Networks A and C interchanged.
+
+**Test number:** 2.6.2 **Ref.:** 2/Q.732, 2/Q.952 and 5.5.2.3.2/Q.952.
+
+**Config.:** Multiple ISDN Accesses (See Figure 3)
+
+**Title:** Call Forwarding Busy (network determined) – no notification
+
+**Purpose:** To verify that a call can be forwarded correctly if Network B encounters busy UNI B.
+
+- Pre-test conditions:**
+1. Arrange the exchange data such that the requested Call Forwarding busy is supported at Network B.
+ 2. Arrange exchange data such that no number parameters and notifications are delivered to the involved UNIs.
+ 3. Network B's UNI is busy.
+
+#### **Expected message sequence**
+
+| Network A | Network B | Network C |
+|---------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number present, Presentation restricted (01) |
+| COT → | | Optional message |
+| ← ACM | | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), GenNot: Call is diverting (1111011); Redirection number present, Call diversion Info: Notification subscription option, Presentation not allowed (001), Redirection reason user busy (0001) |
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Redirection Info: Redirecting ind. call diverted, all redirection info presentation restricted (100), Redirection counter (1), Redirecting reason user busy (0001); Redirecting number present, Presentation restricted (01); Original called number present, Presentation restricted (01); Calling party number present, Presentation restricted (01) |
+| | COT → | Optional message |
+| Case a | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation restricted (01) |
+| ← CPG | | Event Info: alerting (0000001), RnNbRes: Presentation restricted (01) |
+| | ← ANM | |
+| ← ANM | | |
+
+Network A Network B Network C
+
+| | | |
+|---------------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Case b | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← CPG | Optional message Event Info: Progress (0000010) |
+| | ← CPG | Event Info: alerting (0000001), RnNbRes: Presentation restricted (01) |
+| | ← CPG | Event Info: alerting (0000001), RnNbRes: Presentation restricted (01) |
+| | ← ANM | |
+| | ← ANM | |
+| Case c | ← CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation restricted (01) |
+| | ← ANM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation restricted (01) |
+
+⇐ COMMUNICATION ⇒
+
+| | |
+|-------|-------------------------------------------------------------|
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | |
+| ← RLC | |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that the call is diverted to Network C's UNI.
+3. Check that no notification *Call forwarding on busy* is received at Network A's UNI.
+4. Check that the *Redirection number* and *call diversion information* parameters are not received at Network A's UNI.
+5. Check that the *Redirection information*, the *Original called number* and the *Redirecting number* parameters are not received at Network C's UNI.
+6. Check that call is established between Network A's UNI and Network C's UNI.
+7. Check the propriety of data transmission or speech.
+8. Clear the call from Network A's UNI.
+9. Check that all resources are released.
+10. Repeat the test for speech and 3.1 kHz audio bearers.
+11. Repeat steps 1-10 with Networks A and C interchanged.
+12. Repeat steps 1-11 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check that the call is diverted to Network C's (Q.767) UNI.
+3. Check that call is established between Network A's UNI and Network C's UNI.
+4. Check the propriety of data transmission or speech.
+5. Clear the call from Network A's UNI.
+6. Check that all resources are released.
+7. Repeat the test for speech and 3.1 kHz audio bearers.
+8. Repeat steps 1-7 with Networks A and C interchanged.
+
+**Test number:** 2.6.3 **Ref.:** 2/Q.732, 2/Q.952 and 5.5.2.3.3/Q.952.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Call Forwarding Busy (user determined) – full notification
+
+**Purpose:** To verify that a call can be forwarded correctly if Network B encounters busy UNI B.
+
+- Pre-test conditions:**
+1. Arrange the exchange data such that the requested Call Forwarding busy is supported at Network B.
+ 2. Arrange exchange data such that all number parameters and notifications are delivered to the involved UNIs.
+ 3. Called termination is busy, one B-channel is free.
+
+#### Expected message sequence
+
+| Network A | Network B | Network C |
+|-----------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number present, Presentation allowed (00) |
+| COT → | | Optional message |
+| Case a ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), GenNot: Call is diverting (1111011); Redirection number present, Call diversion Info: Notification subscription option, Presentation allowed with redirection number (010), Redirection reason user busy (0001) |
+| Case b ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| ← | CPG | Event Info: Progress (0000010); GenNot: Call is diverting (1111011); Redirection number present; Call diversion Info: Notification subscription option, Presentation allowed with redirection number (010), Redirection reason user busy (0001) |
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Redirection Info: Redirecting ind. call diverted (011), Redirection counter (001), Redirecting reason user busy (0001); Redirecting number present, Presentation allowed (00); Original called number present, Presentation allowed (00); Calling party number present, Presentation allowed (00) |
+| | COT → | Optional message |
+
+Network A Network B Network C
+
+| | | |
+|---------------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Case A | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+| | ← CPG | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | ← ANM | |
+| | ← ANM | |
+| Case B | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← CPG | Optional message Event Info: Progress (0000010) |
+| | ← CPG | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | ← CPG | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | ← ANM | |
+| | ← ANM | |
+| Case C | ← CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+| | ← ANM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+
+⇐ COMMUNICATION ⇒
+
+| | |
+|-------|-------------------------------------------------------------|
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | |
+| ← RLC | |
+
+#### Test description (ISUP'92):
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that a SETUP is sent to Network B's UNI and a REL user busy is received at Network B.
+3. Check that the call is diverted to Network C's UNI.
+4. Check that notification *Call forwarding on busy* is received at Network A's UNI.
+5. Check that the *Redirection number* and *call diversion information* parameters are correctly received at Network A's UNI.
+6. Check that *Redirection information*, the *Original called number* and the *Redirecting number* parameters are correctly received at Network C's UNI.
+7. Check that call is established between Network A's UNI and Network C's UNI.
+8. Check the propriety of data transmission or speech.
+
+9. Clear the call from Network A's UNI.
+10. Check that all resources are released.
+11. Repeat the test for speech and 3.1 kHz audio bearers.
+12. Repeat steps 1-11 with Networks A and C interchanged.
+13. Repeat steps 1-12 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check that the call is diverted to Network C's (Q.767) UNI.
+3. Check that call is established between Network A's UNI and Network C's UNI.
+4. Check the propriety of data transmission or speech.
+5. Clear the call from Network A's UNI.
+6. Check that all resources are released.
+7. Repeat the test for speech and 3.1 kHz audio bearers.
+8. Repeat steps 1-7 with Networks A and C interchanged.
+
+**Test number:** 2.6.4 **Ref.:** 2/Q.732, 2/Q.952 and 5.5.2.3.3/Q.952.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Call Forwarding Busy (user determined) – Unsuccessful
+
+**Purpose:** To verify that a call is released correctly if CFB was not successful.
+
+- Pre-test conditions:**
+1. Arrange the exchange data such that the requested Call Forwarding busy is supported at Network B.
+ 2. Arrange exchange data such that all number parameters and notifications are delivered to the involved UNIs.
+ 3. Called termination is busy, one B-channel is free.
+ 4. Network C's UNI is user determined user busy.
+
+#### **Expected message sequence**
+
+| | Network A | Network B | Network C |
+|---------------|-----------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number present, Presentation allowed (00) |
+| | COT → | | Optional message |
+| Case a | ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), GenNot: Call is diverting (1111011); Redirection number present, Call diversion Info: Notification subscription option, Presentation allowed with redirection number (010), Redirection reason user busy (0001) |
+| Case b | ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| | ← | CPG | Event Info: Progress (0000010); GenNot: Call is diverting (1111001); Redirection number present; Call diversion Info: Notification subscription option, Presentation allowed with redirection Number (010), Redirection reason user busy (0001) |
+| | | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Redirection Info: Redirecting ind. call diverted (011), Redirection counter (001), Redirecting reason user busy (0001); Redirecting number present, Presentation allowed (01); Original called number present, Presentation allowed (01); Calling party number present, Presentation allowed (01) |
+| | | COT → | Optional message |
+| Case A | | ← REL | Cause Ind.: User busy (17), location user (0000) |
+| | ← | REL | Cause Ind.: User busy (17), location user (0000) |
+| | | RLC → | |
+| | RLC → | | |
+
+| | Network A | Network B | Network C |
+|---------------|-----------|-----------|-----------------------------------------------------------------------------------------------------------------------------|
+| Case B | | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← CPG | | Optional message Event Info: Progress (0000010) |
+| | | ← REL | Cause Ind.: User busy (17), location user (0000) |
+| | ← REL | | Cause Ind.: User busy (17), location user (0000) |
+| | | RLC → | |
+| | RLC → | | |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that a SETUP is sent to Network B's UNI and a RELEASE user busy is received at Network B.
+3. Check that the call is diverted to Network C's UNI.
+4. Check that notification *Call forwarding on busy* is received at Network A's UNI.
+5. Check that *Redirection number* and *call diversion information* parameters are correctly received at Network A.
+6. Check that the call is released by Network C's UNI.
+7. Check that all resources are released.
+8. Repeat the test for speech and 3.1 kHz audio bearers.
+9. Repeat steps 1-8 with Networks A and C interchanged.
+10. Repeat steps 1-9 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check that a SETUP is sent to Network B's UNI and a RELEASE user busy is received at Network B.
+3. Check that the call is diverted to Network C's (Q.767) UNI.
+4. Check that the call is released by Network C's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and C interchanged.
+
+**Test number:** 2.7.1 **Ref.:** 2/Q.732, 3/Q.952 and 5.5.2.3.4/Q.952.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Call Forwarding No Reply (option A, late release) – full notification
+
+**Purpose:** To verify that a call can be forwarded correctly if Network B's UNI does not answer the call.
+
+- Pre-test conditions:**
+1. Arrange the exchange data such that the requested Call Forwarding No Reply is supported at Network B.
+ 2. Arrange exchange data such that all number parameters and notifications are delivered to the involved UNIs.
+ 3. Network B's UNI should not answer the call.
+
+#### **Expected message sequence**
+
+| Network A | Network B | Network C |
+|-----------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number present, Presentation allowed (00) |
+| COT → | | Optional message |
+| Case a ← | ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| Case b ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| ← | CPG | Event Info: alerting (00000001) |
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Redirecting number present, Presentation allowed (00); Redirection Info: Redirecting ind. call diverted (011), Redirection counter (001), Redirecting reason no reply (0010); Original called number present, Presentation allowed (00); Calling party number present, Presentation allowed (00) |
+| | COT → | Optional message |
+| Case A ← | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+| ← | CPG | Event Info: alerting (00000001); GenNot: Call is diverting (1111011); Call diversion Info: Notification subscription option Presentation allowed with redirection number (010), Redirection reason no reply (0010); Redirection number present, RnNbRes: Presentation allowed (00) |
+| | ← ANM | |
+| ← | ANM | |
+| Case B ← | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+
+Network A Network B Network C
+
+| | | |
+|-------------------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | ← CPG | Optional message Event Info: Progress (0000010) |
+| | ← CPG | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | ← CPG | Event Info: alerting (0000001), GenNot: Call is diverting (1111011); Call diversion Info: Notification subscription option, Presentation allowed with redirection number (010), Redirection reason no reply (0010); Redirection number present, RnNbRes: Presentation allowed (00) |
+| | ← ANM | |
+| | ← ANM | |
+| Case C | ← CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+| | ← ANM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1); GenNot: Call is diverting (1111011); Call diversion Info: Notification subscription option, Presentation allowed with redirection Number (010), Redirection reason no reply (0010); Redirection number present; Rn NbRes:Presentation allowed (00) |
+| ← COMMUNICATION ⇒ | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | REL | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← RLC | |
+| | ← RLC | |
+
+#### Test description (ISUP'92):
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that Network B's UNI is alerted and the number parameters are correctly received.
+3. Check that the ACM contains the OBCI: call diversion may occur.
+4. Check that call is diverted to Network C's UNI after no reply timer expired.
+5. Check that notification *Call forwarding no reply* is received at Network A's UNI.
+6. Check that the *Redirection number* and *call diversion information* parameters are correctly received at Network A's UNI.
+7. Check that Network C's UNI is alerted.
+8. Check that the *Redirection information*, the *Original called number* and the *Redirecting number* parameters are correctly received at Network C's UNI.
+9. Check that Network B's UNI is released.
+10. Check that notification *Call is diverting* is received at Network A's UNI.
+11. Check that all number parameters are correctly received at Network A's UNI.
+12. Check that all number parameters are correctly received at Network C's UNI.
+13. Check that call is established between Network A's UNI and Network C's UNI.
+
+14. Check the propriety of data transmission or speech.
+15. Clear the call from Network A's UNI.
+16. Check that all resources are released.
+17. Repeat the test for speech and 3.1 kHz audio bearers.
+18. Repeat steps 1-17 with Networks A and C interchanged.
+19. Repeat steps 1-18 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check that Network B's UNI is alerted.
+3. Check that call is diverted to Network C's (Q.767) UNI after no reply timer expired.
+4. Check that Network C's UNI is alerted.
+5. Check that Network B's UNI is released.
+6. Check that call is established between Network A's UNI and Network C's UNI.
+7. Check the propriety of data transmission or speech.
+8. Clear the call from Network A's UNI.
+9. Check that all resources are released.
+10. Repeat the test for speech and 3.1 kHz audio bearers.
+11. Repeat steps 1-10 with Networks A and C interchanged.
+
+**Test number:** 2.7.2 **Ref.:** 2/Q.732, 3/Q.952 and 5.5.2.3.4/Q.952.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Call Forwarding No Reply (option A, late release) – no notification
+
+**Purpose:** To verify that a call can be forwarded correctly if Network B's UNI does not answer the call.
+
+- Pre-test conditions:**
+1. Arrange the exchange data such that the requested Call Forwarding No Reply is supported at Network B.
+ 2. Arrange exchange data such that no number parameters and notifications are delivered to the involved UNIs.
+ 3. Network B's UNI should not answer the call.
+
+#### Expected message sequence
+
+| Network A | Network B | Network C |
+|-----------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number present, Presentation restricted (01) |
+| COT → | | Optional message |
+| ← | ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| ← | CPG | Event Info: alerting (0000001) |
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Redirection Info: Redirecting ind. call diverted, all redirection info presentation restricted (100), Redirection counter (001), Redirecting reason no reply (0010); Redirecting number present, Presentation restricted (01); Original called number present, Presentation restricted (01); Calling party number present, Presentation restricted (01) |
+| | COT → | Optional message |
+| | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation restricted (01) |
+| | ← CPG | Event Info: alerting (0000001); GenNot: Call is diverting (1111011); Call diversion Info: Notification subscription option Presentation not allowed (001), Redirectionreason no reply (0010); Redirection number present, RnNbRes: Presentation restricted (01) |
+| | ← ANM | |
+| ← | ANM | |
+
+Network A Network B Network C
+
+| | | | |
+|-------------------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Case B | ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG | Optional message Event Info: Progress (0000010); |
+| | ← | CPG | Event Info: alerting (0000001), RnNbRes: Presentation restricted (01) |
+| | ← | CPG | Event Info: alerting (0000001), GenNot: Call is diverting (1111011); Call diversion Info: Notification subscription option Presentation not allowed (001), Redirection reason no reply (0010); Redirection number present, Presentation restricted (01), RnNbRes: Presentation restricted (01) |
+| | ← | ANM | |
+| | ← | ANM | |
+| Case C | ← | CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation restricted (01) |
+| | ← | ANM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), GenNot: Call is diverting (1111011); Call diversion Info: Notification subscription option Presentation not allowed (001), Redirection reason no reply (0010); Redirection number present, RnNbRes: Presentation restricted (01) |
+| ← COMMUNICATION ⇒ | | | |
+| | REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | | REL | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC | |
+| | | ← | RLC |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that Network B's UNI is alerted and the number parameters are correctly received.
+3. Check that the ACM contains the OBCI: call diversion may occur.
+4. Check that call is diverted to Network C's UNI after no reply timer expired.
+5. Check that no notification *Call forwarding no reply* is received at Network A's UNI.
+6. Check that the *Redirection number* and *call diversion information* parameters are not received at Network A's UNI.
+7. Check that Network C's UNI is alerted.
+8. Check that the *Redirection information*, the *Original called number* and the *Redirecting number* parameters are not received at Network C's UNI.
+9. Check that Network B's UNI is released.
+10. Check that notification *Call is diverting* is not received at Network A's UNI.
+
+11. Check that no number parameters are received at Network A's UNI.
+12. Check that no number parameters are received at Network C's UNI.
+13. Check that call is established between Network A's UNI and Network C's UNI.
+14. Check the propriety of data transmission or speech.
+15. Clear the call from Network A's UNI.
+16. Check that all resources are released.
+17. Repeat the test for speech and 3.1 kHz audio bearers.
+18. Repeat steps 1-17 with Networks A and C interchanged.
+19. Repeat steps 1-18 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check that Network B's UNI is alerted.
+3. Check that call is diverted to Network C's (Q.767) UNI after no reply timer expired.
+4. Check that Network C's UNI is alerted.
+5. Check that Network B's UNI is released.
+6. Check that call is established between Network A's UNI and Network C's UNI.
+7. Check the propriety of data transmission or speech.
+8. Clear the call from Network A's UNI.
+9. Check that all resources are released.
+10. Repeat the test for speech and 3.1 kHz audio bearers.
+11. Repeat steps 1-10 with Networks A and C interchanged.
+
+**Test number:** 2.7.3 **Ref.:** 2/Q.732, 3/Q.952 and 5.5.2.3.4/Q.952.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Call Forwarding No Reply (option B, immediate release) – full notification
+
+**Purpose:** To verify that a call can be forwarded correctly if Network B's UNI does not answer the call.
+
+- Pre-test conditions:**
+1. Arrange the exchange data such that the requested Call Forwarding No Reply is supported at Network B.
+ 2. Arrange exchange data such that all number parameters are delivered to the involved UNIs.
+ 3. Network B's UNI should not answer the call.
+
+#### Expected message sequence
+
+| Network A | Network B | Network C |
+|-----------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number present, Presentation allowed (00) |
+| COT → | | Optional message |
+| ← | ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| ← | CPG | Event Info: alerting (0000001) |
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Redirection Info: Redirection counter (001), Redirecting reason no reply (0010), Redirecting ind.: call diverted (011), Original called number present, Presentation allowed (00), Calling party number present, Presentation allowed (00), Redirecting number present, Presentation allowed (00) |
+| | COT → | Optional message |
+| ← | CPG | Event Info: Progress (0000010), GenNot: Call is diverting (1111011), Call diversion Info: Redirection reason no reply (0010), Redirection number present |
+| ← | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+| ← | CPG | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | ← ANM | |
+| ← | ANM | |
+
+Network A Network B Network C
+
+| | | | |
+|-------------------|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Case B | ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG | Optional message Event Info: Progress (0000010) |
+| | ← | CPG | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | ← | CPG | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | ← | ANM | |
+| | ← | ANM | |
+| Case C | ← | CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+| | ← | ANM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+| ⇐ COMMUNICATION ⇨ | | | |
+| | REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | | REL | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC | |
+| | | ← | RLC |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that Network B's UNI is alerted and the number parameters are correctly received.
+3. Check that the ACM contains the OBCI: call diversion may occur.
+4. Check that Network B's UNI is released.
+5. Check that call is diverted to Network C's UNI after no reply timer expired.
+6. Check that Network C's UNI is alerted.
+7. Check that notification *Call is diverting* is received at Network A's UNI.
+8. Check that all number parameters are correctly received at Network A's UNI.
+9. Check that all number parameters are correctly received at Network C's UNI.
+10. Check that call is established between Network A's UNI and Network C's UNI.
+11. Check the propriety of data transmission or speech.
+12. Clear the call from Network A's UNI.
+13. Check that all resources are released.
+14. Repeat the test for speech and 3.1 kHz audio bearers.
+15. Repeat steps 1-14 with Networks A and C interchanged.
+16. Repeat steps 1-15 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check that Network B's UNI is alerted.
+3. Check that Network B's UNI is released.
+4. Check that call is diverted to Network C's (Q.767) UNI after no reply timer expired.
+5. Check that Network C's UNI is alerted.
+6. Check that call is established between Network A's UNI and Network C's UNI.
+7. Check the propriety of data transmission or speech.
+8. Clear the call from Network A's UNI.
+9. Check that all resources are released.
+10. Repeat the test for speech and 3.1 kHz audio bearers.
+11. Repeat steps 1-10 with Networks A and C interchanged.
+
+**Test number:** 2.7.4 **Ref.:** 2/Q.732, 3/Q.952 and 5.5.2.3.4/Q.952.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Call Forwarding No Reply (option A, late release) – Unsuccessful
+
+**Purpose:** To verify that the call is released correctly if CFNR was not successful.
+
+- Pre-test conditions:**
+1. Arrange the exchange data such that the requested Call Forwarding No Reply is supported at Network B.
+ 2. Arrange exchange data such that all number parameters are delivered to the involved UNIs.
+ 3. Network B's UNI should not answer the call.
+ 4. Network C's UNI is user determined user busy.
+
+#### **Expected message sequence**
+
+| Network A | Network B | Network C |
+|-----------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number present, Presentation allowed (00) |
+| COT → | | Optional message |
+| Case a ← | ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| Case b ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| ← | CPG | Event Info: alerting (0000001) |
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Redirection Info: Redirection counter (1), Redirecting reason no reply (0010), Redirecting ind.: call diverted (011), Original called number present, Presentation allowed (00), Calling party number present, Presentation allowed (00), Redirecting number present, Presentation allowed (00) |
+| | COT → | Optional message |
+| Case A ← | REL | Cause Ind.: User busy (17), location user (0000) |
+| | RLC → | |
+| Case B ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← | CPG | Optional message Event Info: Progress (0000011) |
+| ← | REL | Cause Ind.: User busy (17), location user (0000) |
+| | RLC → | |
+| REL → | | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← | RLC | |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that Network B's UNI is alerted and the number parameters are correctly received.
+3. Check that the ACM contains the OBCI: call diversion may occur.
+4. Check that call is diverted to Network C's UNI after no reply timer expired.
+5. Network C's UNI clears the call to Network B's UNI.
+6. Check that Network B's UNI is still alerted.
+7. Clear the call from Network A's UNI.
+8. Check that all resources are released.
+9. Repeat the test for speech and 3.1 kHz audio bearers.
+10. Repeat steps 1-9 with Networks A and C interchanged.
+11. Repeat steps 1-10 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check that Network B's UNI is alerted.
+3. Check that call is diverted to Network C's (Q.767) UNI after no reply timer expired.
+4. Network C's UNI clears the call to Network B's UNI.
+5. Check that Network B's UNI is still alerted.
+6. Clear the call from Network A's UNI.
+7. Check that all resources are released.
+8. Repeat the test for speech and 3.1 kHz audio bearers.
+9. Repeat steps 1-8 with Networks A and C interchanged.
+
+**Test number:** 2.7.5 **Ref.:** 2/Q.732, 3/Q.952 and 5.5.2.3.4/Q.952.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Call Forwarding No Reply (option B, immediate release) – Unsuccessful
+
+**Purpose:** To verify that the call is released correctly if CFNR was not successful.
+
+- Pre-test conditions:**
+1. Arrange exchange data such that the requested Call Forwarding No Reply is supported at Network B.
+ 2. Arrange exchange data such that all number parameters are delivered to the involved UNIs.
+ 3. Network B's UNI should not answer the call.
+ 4. Network C's UNI is user determined user busy.
+
+#### **Expected message sequence**
+
+| Network A | Network B | Network C |
+|-----------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number present, Presentation allowed (00) |
+| COT → | | Optional message |
+| ← ACM | | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| ← ACM | | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| ← CPG | | Event Info: alerting (00000001) |
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Redirection Info: Redirection counter (1), Redirecting reason no reply (0010), Redirecting ind.: call diverted (011), Original called number present, Presentation allowed (00), Calling party number present, Presentation allowed (00), Redirecting number present, Presentation allowed (00) |
+| | COT → | Optional message |
+| ← CPG | | Event Info: Progress (0000010), GenNot: Call is diverting (1111011), Call diversion Info: Redirection reason no reply (0010), Redirection number present |
+| ← ← REL | | Cause Ind.: User busy (17), location user (0000) |
+| ← REL | | Cause Ind.: User busy (17), location user (0000) |
+| RLC → | | |
+| RLC → | | |
+
+Network A Network B Network C
+
+| | | | |
+|---------------|-------|-------|-----------------------------------------------------------------------------------------------------------------------------|
+| Case B | | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← CPG | | Optional message Event Info: Progress (0000010) |
+| | | ← REL | Cause Ind.: User busy (17), location user (0000) |
+| | ← REL | | Cause Ind.: User busy (17), location user (0000) |
+| | | RLC → | |
+| | RLC → | | |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that Network B's UNI is alerted.
+3. Check that the ACM contains the OBCI: call diversion may occur.
+4. Check that call is diverted to Network C's UNI after no reply timer expired.
+5. Check that Network B's UNI is released.
+6. Check that the call is cleared from Network C's UNI.
+7. Check that all resources are released.
+8. Repeat the test for speech and 3.1 kHz audio bearers.
+9. Repeat steps 1-8 with Networks A and C interchanged.
+10. Repeat steps 1-9 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI
+2. Check that Network B's UNI is alerted.
+3. Check that call is diverted to Network C's (Q.767) UNI after no reply timer expired.
+4. Check that Network B's UNI is released.
+5. Check that the call is cleared from Network C's UNI.
+6. Check that all resources are released.
+7. Repeat the test for speech and 3.1 kHz audio bearers.
+8. Repeat steps 1-7 with Networks A and C interchanged.
+
+**Test number:** 2.8.1 **Ref.:** 2/Q.732, 2/Q.952 and 5.5.2.3.1/Q.952.
+
+**Config.:** Multiple ISDN Accesses (See Figure 3)
+
+**Title:** Call Forwarding Unconditional – Successful – full notification
+
+**Purpose:** To verify that a call can be forwarded correctly in case of CFU.
+
+**Pre-test conditions:**
+
+1. Arrange exchange data such that the requested Call Forwarding Unconditional is supported at Network B.
+2. Arrange exchange data such that all number parameters are delivered to the involved UNIs.
+
+#### **Expected message sequence**
+
+| Network A | Network B | Network C |
+|---------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number present, Presentation allowed (00) |
+| COT → | | Optional message |
+| ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), GenNot: Call is diverting (1111011), Call diversion Info: Notification subscription option, Presentation allowed with redirection number (010), Redirection reason unconditional (0011), Redirection number present |
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Redirection Info: Redirection counter (1), Redirecting reason unconditional (0011), Redirecting ind.: call diverted (011), Original called number present, Presentation allowed (00), Calling party number present, Presentation allowed (00), Redirecting number present, Presentation allowed (00) |
+| | COT → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+| ← | CPG | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | ← | ANM |
+| ← | ANM | |
+
+Network A Network B Network C
+
+| | | | |
+|---------------|---|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Case b | ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG | Optional message Event Info: Progress (0000010) |
+| | ← | CPG | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | ← | CPG | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | ← | ANM | |
+| | ← | ANM | |
+| Case c | ← | CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+| | ← | ANM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+
+⇐ COMMUNICATION ⇒
+
+| | | | |
+|-----|-----|-----|-------------------------------------------------------------|
+| REL | → | | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC | |
+| | | ← | RLC |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that there is no reaction at UNI B.
+3. Check that call is diverted to Network C's UNI.
+4. Check that notification *Call forwarding unconditional* is received at Network A's UNI.
+5. Check that all number parameters are correctly received at Network A's UNI.
+6. Check that all number parameters are correctly received at Network C's UNI.
+7. Check that call is established between Network A's UNI and Network C's UNI.
+8. Check the propriety of data transmission or speech.
+9. Clear the call from Network A's UNI.
+10. Check that all resources are released.
+11. Repeat the test for speech and 3.1 kHz audio bearers.
+12. Repeat steps 1-11 with Networks A and C interchanged.
+13. Repeat steps 1-12 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's (Q.767) UNI to Network B's(ISUP'92) UNI.
+2. Check that there is no reaction at UNI B.
+3. Check that call is diverted to Network C's (Q.767) UNI.
+4. Check that call is established between Network A's UNI and Network C's UNI.
+5. Check the propriety of data transmission or speech.
+6. Clear the call from Network A's UNI.
+7. Check that all resources are released.
+8. Repeat the test for speech and 3.1 kHz audio bearers.
+9. Repeat steps 1-8 with Networks A and C interchanged.
+
+**Test number:** 2.8.2 **Ref.:** 2/Q.732, 2/Q.952 and 5.5.2.3.1/Q.952.
+
+**Config.:** Multiple ISDN Accesses (See Figure 3)
+
+**Title:** Call Forwarding Unconditional – Successful – no notification
+
+**Purpose:** To verify that a call can be forwarded correctly in case of CFU.
+
+**Pre-test conditions:**
+
+1. Arrange the exchange data such that the requested Call Forwarding Unconditional is supported at Network B.
+2. Arrange exchange data such that no number parameters are delivered to the involved UNIs.
+
+#### **Expected message sequence**
+
+| Network A | Network B | Network C |
+|-----------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number present, Presentation restricted (01) |
+| COT → | | Optional message |
+| ← ACM | | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), GenNot: Call is diverting (1111011), Call diversion Info: Notification subscription option, Presentation not allowed (001), Redirection reason unconditional (0011), Redirection number present |
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Redirection Info: Redirection counter (1), Redirecting reason unconditional (0011), Redirecting ind.: call diverted, all redirection info presentation restricted (100), Original called number present, Presentation restricted (01), Calling party number present, Presentation restricted (01), Redirecting number present, Presentation restricted (01) |
+| | COT → | Optional message |
+| | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation restricted (01) |
+| ← CPG | | Event Info: alerting (0000001), RnNbRes: Presentation restricted (01) |
+| | ← ANM | |
+| ← ANM | | |
+
+Network A Network B Network C
+
+| | | | |
+|---------------|---|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Case b | ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG | Optional message Event Info: Progress (0000010) |
+| | ← | CPG | Event Info: alerting (0000001), RnNbRes: Presentation restricted (01) |
+| | ← | CPG | Event Info: alerting (0000001), RnNbRes: Presentation restricted (01) |
+| | ← | ANM | |
+| | ← | ANM | |
+| Case c | ← | CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation restricted (01) |
+| | ← | ANM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation restricted (01) |
+
+⇐ COMMUNICATION ⇨
+
+| | | | |
+|-----|-----|-----|-------------------------------------------------------------|
+| REL | → | | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC | |
+| | | ← | RLC |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that there is no reaction at UNI B.
+3. Check that call is diverted to Network C's UNI.
+4. Check that no notification *Call forwarding unconditional* is received at Network A's UNI.
+5. Check that no number parameters are received at Network A's UNI.
+6. Check that no number parameters are received at Network C's UNI.
+7. Check that call is established between Network A's UNI and Network C's UNI.
+8. Check the propriety of data transmission or speech.
+9. Clear the call from Network A's UNI.
+10. Check that all resources are released.
+11. Repeat the test for speech and 3.1 kHz audio bearers.
+12. Repeat steps 1-11 with Networks A and C interchanged.
+13. Repeat steps 1-12 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check that there is no reaction at UNI B.
+3. Check that call is diverted to Network C's (Q.767) UNI.
+4. Check that call is established between Network A's UNI and Network C's UNI.
+5. Check the propriety of data transmission or speech.
+6. Clear the call from Network A's UNI.
+7. Check that all resources are released.
+8. Repeat the test for speech and 3.1 kHz audio bearers.
+9. Repeat steps 1-8 with Networks A and C interchanged.
+
+**Test number:** 2.8.3 **Ref.:** 2/Q.732, 4/Q.952 and 5.5.2.3.1/Q.952.
+
+**Config.:** Multiple ISDN Accesses (See Figure 3)
+
+**Title:** Call Forwarding Unconditional – Unsuccessful
+
+**Purpose:** To verify that a call is released correctly if CFU was not successful.
+
+- Pre-test conditions:**
+1. Arrange the exchange data such that the requested Call Forwarding Unconditional is supported at Network B.
+ 2. Arrange exchange data such that all number parameters are delivered to the involved UNIs.
+ 3. Network C's UNI is user determined user busy.
+
+#### **Expected message sequence**
+
+| Network A | Network B | Network C |
+|---------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number present, Presentation allowed (00) |
+| COT → | | Optional message |
+| | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), GenNot: Call is diverting (1111011), Call diversion Info: Notification subscription option, Presentation allowed with redirection number (010), Redirection reason unconditional (0011), Redirection number present |
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Redirection Info: Redirection counter (1), Redirecting reason unconditional (0011), Redirecting ind.: call diverted (011), Original called number present, Presentation allowed (00), Calling party number present, Presentation allowed (00), Redirecting number present, Presentation allowed (00) |
+| | COT → | Optional message |
+| Case a | ← REL | Cause Ind.: User busy (17), location user (0000) |
+| ← REL | | Cause Ind.: User busy (17), location user (0000) |
+| RLC → | | |
+| RLC → | | |
+| | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← CPG | | Optional message Event Info: Progress (0000010) |
+| | ← REL | Cause Ind.: User busy (17), location user (0000) |
+| ← REL | | Cause Ind.: User busy (17), location user (0000) |
+| | RLC → | |
+| RLC → | | |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that there is no reaction at UNI B.
+3. Check that call is forwarded to Network C's UNI.
+4. Check that notification *Call forwarding unconditional* is received at Network A's UNI.
+5. Check that all number parameters are correctly received at Network A.
+6. Check that call is released by Network C's UNI.
+7. Check that all resources are released.
+8. Repeat the test for speech and 3.1 kHz audio bearers.
+9. Repeat steps 1-8 with Networks A and C interchanged.
+10. Repeat steps 1-9 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check that there is no reaction at UNI B.
+3. Check that call is forwarded to Network C's (Q.767) UNI.
+4. Check that call is released by Network C's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and C interchanged.
+
+**Test number:** 2.9.1 **Ref.:** 2/Q.732, 5/Q.952 and 5.5.2.3.5/Q.952.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Call Deflection during alerting (option B, immediate release) – full notification
+
+**Purpose:** To verify that a call can be deflected correctly by Network B's UNI.
+
+**Pre-test conditions:**
+
+1. Arrange exchange data such that the requested Call Deflection is supported at Network B.
+2. Arrange exchange data such that all number parameters are delivered to the involved UNIs.
+
+#### **Expected message sequence**
+
+| | Network A | Network B | Network C |
+|---------------|-----------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number present, Presentation allowed (00), |
+| | COT → | | Optional message |
+| Case a | ← | ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| Case b | ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| | ← | CPG | Event Info: alerting (0000001) |
+| | | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Redirection Info: Redirection counter (1), Redirecting reason deflection during alerting (0100), Redirecting ind.: call diverted (011), Original called number present, Presentation allowed (00), Calling party number present, Presentation allowed (00), Redirecting number present, Presentation allowed (00) |
+| | | COT → | Optional message |
+| | ← | CPG | Event Info: Progress (0000010), GenNot: Call is diverting (1111011), Call diversion Info: Notification subscription option Presentation allowed with redirection number (010), Redirection reason deflection during alerting (0100), Redirection number present |
+| Case A | | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+| | ← | CPG | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | | ← ANM | |
+| | ← | ANM | |
+
+Network A Network B Network C
+
+| | | |
+|---------------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Case B | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← CPG | Optional message Event Info: Progress (0000010) |
+| | ← CPG | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | ← CPG | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | ← ANM | |
+| | ← ANM | |
+| Case C | ← CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+| | ← ANM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+
+⇐ COMMUNICATION ⇒
+
+| | |
+|-------|-------------------------------------------------------------|
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | |
+| ← RLC | |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that Network B's UNI is alerted and all number parameters are correctly received.
+3. Initiate Call Deflection at Network B's UNI.
+4. Check that Network B's UNI is released.
+5. Check that call is deflected to Network C's UNI.
+6. Check that notification *Call deflection during alerting* is received at Network A's UNI.
+7. Check that all number parameters are correctly received at Network A's UNI.
+8. Check that all number parameters are correctly received at Network C's UNI.
+9. Check that Network C's UNI is alerted.
+10. Check that call is established between Network A's UNI and Network C's UNI.
+11. Check the propriety of data transmission or speech.
+12. Clear the call from Network A's UNI.
+13. Check that all resources are released.
+14. Repeat the test for speech and 3.1 kHz audio bearers.
+15. Repeat steps 1-14 with Networks A and C interchanged.
+16. Repeat steps 1-15 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check that Network B's UNI is alerted.
+3. Initiate Call Deflection at Network B's UNI.
+4. Check that Network B's UNI is released.
+5. Check that call is deflected to Network C's (Q.767) UNI.
+6. Check that Network C's UNI is alerted.
+7. Check that call is established between Network A's UNI and Network C's UNI.
+8. Check the propriety of data transmission or speech.
+9. Clear the call from Network A's UNI.
+10. Check that all resources are released.
+11. Repeat the test for speech and 3.1 kHz audio bearers.
+12. Repeat steps 1-11 with Networks A and C interchanged.
+
+**Test number:** 2.9.2 **Ref.:** 2/Q.732, 5/Q.952 and 5.5.2.3.5/Q.952.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Call Deflection during alerting (option B, immediate release) – no notification
+
+**Purpose:** To verify that a call can be deflected correctly by Network B's UNI.
+
+**Pre-test conditions:**
+
+1. Arrange the exchange data such that the requested Call Deflection is supported at Network B.
+2. Arrange exchange data such that no number parameters are delivered to the involved UNIs.
+
+#### **Expected message sequence**
+
+| | Network A | Network B | Network C |
+|---------------|-----------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number present, Presentation restricted (01) |
+| | COT → | | Optional message |
+| Case a | ← | ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| Case b | ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| | ← | CPG | Event Info: alerting (0000001) |
+| | | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Redirection Info: Redirection counter (1), Redirecting reason deflection during alerting (0100), Redirecting ind.: call diverted, all redirection info presentation restricted (100), Original called number present, Presentation restricted (01), Calling party number present, Presentation restricted (01), Redirecting number present, Presentation restricted (01) |
+| | | COT → | Optional message |
+| | ← | CPG | Event Info: Progress (0000010), GenNot: Call is diverting (1111011), Call diversion Info: Notification subscription option Presentation not allowed (001), Redirection reason deflection during alerting (0100), Redirection number present |
+| Case A | | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation restricted (01) |
+| | ← | CPG | Event Info: alerting (0000001), RnNbRes: Presentation restricted (01) |
+| | | ← | ANM |
+| | ← | ANM | |
+
+Network A Network B Network C
+
+| | | |
+|---------------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Case B | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← CPG | Optional message Event Info: Progress (0000010) |
+| | ← CPG | Event Info: alerting (0000001), RnNbRes: Presentation restricted (01) |
+| | ← CPG | Event Info: alerting (0000001), RnNbRes: Presentation restricted (01) |
+| | ← ANM | |
+| | ← ANM | |
+| Case C | ← CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation restricted (01) |
+| | ← ANM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation restricted (01) |
+
+⇐ COMMUNICATION ⇒
+
+| | |
+|-------|-------------------------------------------------------------|
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | |
+| ← RLC | |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that Network B's UNI is alerted and all number parameters are correctly received.
+3. Initiate Call Deflection at Network B's UNI.
+4. Check that Network B's UNI is released.
+5. Check that call is deflected to Network C's UNI.
+6. Check that no notification *Call deflection during alerting* is received at Network A's UNI.
+7. Check that no number parameters are received at Network A's UNI.
+8. Check that no number parameters are received at Network C's UNI.
+9. Check that Network C's UNI is alerted.
+10. Check that call is established between Network A's UNI and Network C's UNI.
+11. Check the propriety of data transmission or speech.
+12. Clear the call from Network A's UNI.
+13. Check that all resources are released.
+14. Repeat the test for speech and 3.1 kHz audio bearers.
+15. Repeat steps 1-14 with Networks A and C interchanged.
+16. Repeat steps 1-15 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check that Network B's UNI is alerted.
+3. Initiate Call Deflection at Network B's UNI.
+4. Check that Network B's UNI is released.
+5. Check that call is deflected to Network C's (Q.767) UNI.
+6. Check that Network C's UNI is alerted.
+7. Check that call is established between Network A's UNI and Network C's UNI.
+8. Check the propriety of data transmission or speech.
+9. Clear the call from Network A's UNI.
+10. Check that all resources are released.
+11. Repeat the test for speech and 3.1 kHz audio bearers.
+12. Repeat steps 1-11 with Networks A and C interchanged.
+
+**Test number:** 2.9.3 **Ref.:** 2/Q.732, 5/Q.952 and 5.5.2.3.5/Q.952.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Call Deflection immediate response (option B, immediate release) – full notification
+
+**Purpose:** To verify that a call can be deflected correctly by Network B's UNI.
+
+**Pre-test conditions:**
+
+1. Arrange exchange data such that the requested Call Deflection is supported at Network B.
+2. Arrange exchange data such that all number parameters are delivered to the involved UNIs.
+
+#### **Expected message sequence**
+
+| Network A | Network B | Network C |
+|-----------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number present, Presentation allowed (00) |
+| COT → | | Optional message |
+| Case a ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), GenNot: Call is diverting (1111011) |
+| Case b ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Redirection Info: Redirection counter (1), Redirecting reason deflection immediate response (0101), Redirecting ind.: call diverted (011), Original called number present, Presentation allowed (00), Calling party number present, Presentation allowed (00), Redirecting number present, Presentation allowed (00) |
+| | COT → | Optional message |
+| ← | CPG | Event Info: Progress (0000010), GenNot: Call is diverting (1111011), Call diversion Info: Redirection reason deflection immediate response (0101), Redirection number present |
+| Case A ← | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+| ← | CPG | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | ← ANM | |
+| ← | ANM | |
+
+Network A Network B Network C
+
+| | | | |
+|---------------|---|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Case B | ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG | Optional message Event Info: Progress (0000010) |
+| | ← | CPG | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | ← | CPG | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | ← | ANM | |
+| | ← | ANM | |
+| Case C | ← | CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+| | ← | ANM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+
+⇐ COMMUNICATION ⇒
+
+| | | | |
+|-----|-----|-------|-------------------------------------------------------------|
+| REL | → | | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC | |
+| | | ← RLC | |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Initiate Call Deflection after SETUP at Network B's UNI.
+3. Check that Network B's UNI is not alerted and that UNI B is released.
+4. Check that call is deflected to Network C's UNI.
+5. Check that notification *Call deflection immediate response* is received at Network A's UNI.
+6. Check that all number parameters are correctly received at Network A's UNI.
+7. Check that all number parameters are correctly received at Network C's UNI.
+8. Check that Network C's UNI is alerted.
+9. Check that call is established between Network A's UNI and Network C's UNI.
+10. Check the propriety of data transmission or speech.
+11. Clear the call from Network A's UNI.
+12. Check that all resources are released.
+13. Repeat the test for speech and 3.1 kHz audio bearers.
+14. Repeat steps 1-13 with Networks A and C interchanged.
+15. Repeat steps 1-14 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Initiate Call Deflection after SETUP at Network B's UNI.
+3. Check that Network B's UNI is not alerted and that UNI B is released.
+4. Check that call is deflected to Network (Q.767) C's UNI.
+5. Check that Network C's UNI is alerted.
+6. Check that call is established between Network A's UNI and Network C's UNI.
+7. Check the propriety of data transmission or speech.
+8. Clear the call from Network A's UNI.
+9. Check that all resources are released.
+10. Repeat the test for speech and 3.1 kHz audio bearers.
+11. Repeat steps 1-10 with Networks A and C interchanged.
+
+**Test number:** 2.9.4 **Ref.:** 2/Q.732, 5/Q.952 and 5.5.2.3.5/Q.952.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Call Deflection during alerting (option A, late release) – full notification
+
+**Purpose:** To verify that a call can be deflected correctly by Network B's UNI.
+
+**Pre-test conditions:**
+
+1. Arrange exchange data such that the requested Call Deflection is supported at Network B.
+2. Arrange exchange data such that all number parameters are delivered to the involved UNIs.
+
+#### **Expected message sequence**
+
+| | Network A | Network B | Network C |
+|---------------|-----------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number present, Presentation allowed (00) |
+| | COT → | | Optional message |
+| Case a | ← | ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| Case b | ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| | ← | CPG | Event Info: alerting (00000001) |
+| | | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Redirection Info: Redirection counter (1), Redirecting reason deflection during alerting (0100), Redirecting ind.: call diverted (011), Original called number present, Presentation allowed (00), Calling party number present, Presentation allowed (00), Redirecting number present, Presentation allowed (00) |
+| | | COT → | Optional message |
+| Case A | | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+| | ← | CPG | Event Info: alerting (00000001), GenNot: Call is diverting (1111011), Call diversion Info: Redirection reason deflection during alerting (0100), Redirection number present, RnNbRes: Presentation allowed (00) |
+| | | ← ANM | |
+| | ← | ANM | |
+
+Network A Network B Network C
+
+| | | |
+|---------------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Case B | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← CPG | Optional message Event Info: Progress (0000010) |
+| | ← CPG | Event Info: alerting (0000001), RnNbRes: Presentation allowed (00) |
+| | ← CPG | Event Info: alerting (0000001), GenNot: Call is diverting (1111011), Call diversion Info: Redirection reason deflection during alerting (0100), Redirection number present, Presentation allowed (00), RnNbRes: Presentation allowed (00) |
+| | ← ANM | |
+| | ← ANM | |
+| Case C | ← CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), RnNbRes: Presentation allowed (00) |
+| | ← ANM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), GenNot: Call is diverting (1111011)
Call diversion Info: Redirection reason deflection during alerting (0100), Redirection number present, Presentation allowed (00), RnNbRes: Presentation allowed (00) |
+
+⇐ COMMUNICATION ⇒
+
+| | |
+|-------|-------------------------------------------------------------|
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | |
+| ← RLC | |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that Network B's UNI is alerted and all number parameters are correctly received
+3. Initiate Call Deflection at Network B's UNI.
+4. Check that call is deflected to Network C's UNI.
+5. Check that notification *Call deflection during alerting* is received at Network A's UNI.
+6. Check that all number parameters are correctly received at Network A's UNI.
+7. Check that all number parameters are correctly received at Network C's UNI.
+8. Check that Network C's UNI is alerted.
+9. Check that Network B's UNI is released.
+10. Check that call is established between Network A's UNI and Network C's UNI.
+11. Check the propriety of data transmission or speech.
+12. Clear the call from Network A's UNI.
+13. Check that all resources are released.
+
+14. Repeat the test for speech and 3.1 kHz audio bearers.
+15. Repeat steps 1-14 with Networks A and C interchanged.
+16. Repeat steps 1-15 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check that Network B's UNI is alerted.
+3. Initiate Call Deflection at Network B's UNI.
+4. Check that call is deflected to Network C's (Q.767) UNI.
+5. Check that Network C's UNI is alerted.
+6. Check that Network B's UNI is released.
+7. Check that call is established between Network A's UNI and Network C's UNI.
+8. Check the propriety of data transmission or speech.
+9. Clear the call from Network A's UNI.
+10. Check that all resources are released.
+11. Repeat the test for speech and 3.1 kHz audio bearers.
+12. Repeat steps 1-11 with Networks A and C interchanged.
+
+**Test number:** 2.9.5 **Ref.:** 2/Q.732, 5/Q.952 and 5.5.2.3.5/Q.952.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Call Deflection during alerting (option B, immediate release) – Unsuccessful
+
+**Purpose:** To verify that a call is released correctly if Call Deflection was not successful.
+
+- Pre-test conditions:**
+1. Arrange exchange data such that the requested Call Deflection is supported at Network B.
+ 2. Arrange exchange data such that all number parameters are delivered to the involved UNIs.
+ 3. Network C's UNI is user determined user busy.
+
+#### **Expected message sequence**
+
+| Network A | Network B | Network C |
+|-----------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number present, Presentation allowed (00) |
+| COT → | | Optional message |
+| ← ACM | | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| ← ACM | | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| ← CPG | | Event Info: alerting (0000001) |
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Redirection Info: Redirection counter (1), Redirecting reason deflection during alerting (0100), Redirecting ind.: call diverted (011), Original called number present, Presentation allowed (00), Calling party number present, Presentation allowed (00), Redirecting number present, Presentation allowed (00) |
+| | COT → | Optional message |
+| ← CPG | | Event Info: Progress (0000010), GenNot: Call is diverting (1111011), Call diversion Info: Redirection reason deflection during alerting (0100), Redirection number present |
+| ← ← REL | | Cause Ind.: User busy (17), location user (0000) |
+| ← REL | | Cause Ind.: User busy (17), location user (0000) |
+| | RLC → | |
+| RLC → | | |
+
+Network A Network B Network C
+
+| | | | |
+|---------------|-------|-------|-----------------------------------------------------------------------------------------------------------------------------|
+| Case B | ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG | Optional message Event Info: Progress (0000010) |
+| | ← | REL | Cause Ind.: User busy (17), location user (0000) |
+| | ← | REL | Cause Ind.: User busy (17), location user (0000) |
+| | | RLC → | |
+| | RLC → | | |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that Network B's UNI is alerted and all number parameters are correctly received.
+3. Initiate Call Deflection at Network B's UNI.
+4. Check that Network B's UNI is released.
+5. Check that call is deflected to Network C's UNI.
+6. Check that notification *Call deflection during alerting* is received at Network A's UNI.
+7. Check that all number parameters are correctly received at Network A.
+8. Check that call is released by Network C's UNI.
+9. Check that all resources are released.
+10. Repeat the test for speech and 3.1 kHz audio bearers.
+11. Repeat steps 1-10 with Networks A and C interchanged.
+12. Repeat steps 1-11 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check that Network B's UNI is alerted.
+3. Initiate Call Deflection at Network B's UNI.
+4. Check that Network B's UNI is released.
+5. Check that call is deflected to Network C's (Q.767) UNI.
+6. Check that call is released by Network C's UNI.
+7. Check that all resources are released.
+8. Repeat the test for speech and 3.1 kHz audio bearers.
+9. Repeat steps 1-8 with Networks A and C interchanged.
+
+**Test number:** 2.9.6 **Ref.:** 2/Q.732, 5/Q.952 and 5.5.2.3.5/Q.952.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Call Deflection immediate response (option B, immediate release) – Unsuccessful
+
+**Purpose:** To verify that a call is released correctly if Call Deflection was unsuccessful.
+
+- Pre-test conditions:**
+1. Arrange exchange data such that the requested Call Deflection is supported at Network B.
+ 2. Arrange exchange data such that all number parameters are delivered to the involved UNIs.
+ 3. Network C's UNI is user determined user busy.
+
+#### **Expected message sequence**
+
+| Network A | Network B | Network C |
+|---------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number present, Presentation allowed (00) |
+| COT → | | Optional message |
+| ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Redirection Info: Redirection counter (1), Redirecting reason deflection immediate response (0101), Redirecting ind.: call diverted (011), Original called number present, Presentation allowed (00), Calling party number present, Presentation allowed (00), Redirecting number present, Presentation allowed (00) |
+| | COT → | Optional message |
+| ← | CPG | Event Info: Progress (0000010), GenNot: Call is diverting (1111011), Call diversion Info: Redirection reason deflection immediate response (0101), Redirection number present |
+| Case a | ← | REL Cause Ind.: User busy (17), location user (0000) |
+| | RLC → | |
+| ← | REL | Cause Ind.: User busy (17), location user (0000) |
+| RLC → | | |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← | CPG | Optional message Event Info: Progress (0000010) |
+| | ← | REL Cause Ind.: User busy (17), location user (0000) |
+| | RLC → | |
+| ← | REL | Cause Ind.: User busy (17), location user (0000) |
+| RLC → | | |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that call is deflected immediately after receiving SETUP at Network B's UNI.
+3. Check that Network B's UNI is not alerted and that UNI B is released.
+4. Check that notification *Call deflection immediate response* is received at Network A's UNI.
+5. Check that all number parameters are correctly received at Network A.
+6. Check that call is released from Network C's UNI.
+7. Check that all resources are released.
+8. Repeat the test for speech and 3.1 kHz audio bearers.
+9. Repeat steps 1-8 with Networks A and C interchanged.
+10. Repeat steps 1-9 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check that call is deflected immediately after receiving SETUP at Network B's UNI.
+3. Check that Network B's UNI is not alerted and that UNI B is released.
+4. Check that call is released from Network C's (Q.767) UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and C interchanged.
+
+**Test number:** 2.9.7 **Ref.:** 2/Q.732, 5/Q.952 and 5.5.2.3.5/Q.952.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Call Deflection during alerting (option A, late release) – Unsuccessful
+
+**Purpose:** To verify that a call is released correctly if Call Deflection was not successful.
+
+- Pre-test conditions:**
+1. Arrange exchange data such that the requested Call Deflection is supported at Network B.
+ 2. Arrange exchange data such that all number parameters are delivered to the involved UNIs.
+ 3. Network C's UNI is user determined user busy.
+
+#### **Expected message sequence**
+
+| Network A | Network B | Network C |
+|---------------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Calling party number present, Presentation allowed (00) |
+| COT → | | Optional message |
+| ← ACM | | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| ← ACM | | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: call diversion may occur (1) |
+| ← CPG | | Event Info: alerting (0000001) |
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), Redirection Info: Redirection counter (1), Redirecting reason deflection during alerting (0100), Redirecting ind.: call diverted (011), Original called number present, Presentation allowed (00), Calling party number present, Presentation allowed (00), Redirecting number present, Presentation allowed (00) |
+| | COT → | Optional message |
+| Case A | ← REL | Cause Ind.: User busy (17), location user (0000) |
+| | RLC → | |
+| Case B | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← CPG | | Optional message Event Info: Progress (0000010) |
+| ← REL | | Cause Ind.: User busy (17), location user (0000) |
+| | RLC → | |
+| REL → | | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | | |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that Network B's UNI is alerted and all number parameters are correctly received.
+3. Initiate Call Deflection at Network B's UNI.
+4. Check that call is deflected to Network C's UNI.
+5. Check that *notification call deflection during alerting* is received at Network A.
+6. Check that call is released by Network C's UNI.
+7. Check that Network B's UNI is still alerted.
+8. Clear the call from Network A's UNI.
+9. Check that all resources are released.
+10. Repeat the test for speech and 3.1 kHz audio bearers.
+11. Repeat steps 1-10 with Networks A and C interchanged.
+12. Repeat steps 1-11 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Initiate a 64 kbit/s call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check that Network B's UNI is alerted.
+3. Initiate Call Deflection at Network B's UNI.
+4. Check that call is deflected to Network (Q.767) C's UNI.
+7. Check that call is released by Network C's UNI.
+6. Check that Network B's UNI is still alerted.
+7. Clear the call from Network A's UNI.
+8. Check that all resources are released.
+9. Repeat the test for speech and 3.1 kHz audio bearers.
+10. Repeat steps 1-9 with Networks A and C interchanged.
+
+**Test number:** 2.10.1 **Ref.:** 1/Q.733, 1/Q.953.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Call Waiting successful
+
+**Purpose:** To verify that a call can be established after Call Waiting.
+
+**Pre-test conditions:**
+
+1. Arrange exchange data such that the requested Call Waiting is supported at Network B.
+2. One channel available at Network B's UNI (all other channels are busy).
+
+#### **Expected message sequence**
+
+| Network A | Network B | Network C | |
+|-------------------|-------------------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | Simplified call establishment | | |
+| ← ACM | | | |
+| ← ANM | | | |
+| ⇐ COMMUNICATION ⇒ | | | |
+| | ← IAM | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| | ← COT | | Optional message |
+| Case a | ACM → | | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), GenNot: Call is a waiting call (1100000) |
+| Case b | ACM → | | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | CPG → | | GenNot: Call is a waiting call (1100000), Event Info: alerting (0000001) |
+| ← REL | | | Cause Ind.: Normal call clearing (16), location user (0000) |
+| RLC → | | | |
+| | ANM → | | |
+| ⇐ COMMUNICATION ⇒ | | | |
+| | ← REL | | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | RLC → | | |
+
+#### **Test description (ISUP'92):**
+
+1. Make a speech call from Network A's UNI to Network B's UNI.
+2. Check the propriety of speech.
+3. Make a speech call from Network C's UNI to Network B's UNI.
+4. Check that notification is received at Network C's UNI.
+5. Clear the active call from Network B's UNI.
+6. Check that Network B's UNI is alerted.
+7. Network B's UNI answers the call from Network C's UNI.
+
+8. Check the propriety of speech.
+9. Clear the call from Network C's UNI.
+10. Check that all resources are released.
+11. Repeat the test for bearer 3.1 kHz audio.
+12. Repeat steps 1-11 with Networks A and C interchanged.
+13. Repeat steps 1-12 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Make a speech call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check the propriety of speech.
+3. Make a speech call from Network C's (Q.767) UNI to Network B's UNI.
+4. Clear the active call from Network B's UNI.
+5. Check that Network B's UNI is alerted.
+6. Network B's UNI answers the call from Network C's UNI.
+7. Check the propriety of speech.
+8. Clear the call from Network C's UNI.
+9. Check that all resources are released.
+10. Repeat the test for bearer 3.1 kHz audio.
+11. Repeat steps 1-10 with Networks A and C interchanged.
+
+**Test number:** 2.10.2 **Ref.:** 1/Q.733, 2/Q.953.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Call Waiting rejection
+
+**Purpose:** Verify that a waiting call can be rejected.
+
+- Pre-test conditions:**
+1. Arrange exchange data such that the requested Call Waiting is supported at Network B's UNI.
+ 2. One channel available at UNI B (all other channels are busy).
+
+#### **Expected message sequence**
+
+
+
+| Network A | Network B | Network C | |
+|----------------------------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|
+| IAM →
← ACM
← ANM | | | Simplified call establishment |
+| ← COMMUNICATION ⇒ | | | |
+| ← IAM
← COT Optional message | | | |
+| Case a | ACM → | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), GenNot: Call is a waiting call (1100000) | |
+| Case b | ACM → | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) | |
+| | CPG → | GenNot: Call is a waiting call (1100000), Event Info: alerting (0000001) | |
+| | REL → | Cause Ind.: Call rejected (21), location user (0000) | |
+| | ← RLC | | |
+| ← COMMUNICATION ⇒ | | | |
+| | ← REL | Cause Ind.: Normal call clearing (16), location user (0000) | |
+| | RLC → | | |
+
+#### **Test description (ISUP'92):**
+
+1. Make a speech call from Network A's UNI to Network B's UNI.
+2. Check the propriety of speech.
+3. Make a speech call from Network C's UNI to Network B's UNI.
+4. Check that notification is received at Network C's UNI.
+5. Reject the waiting call at Network B's UNI.
+6. Check that all network resources between Network B and Network C and UNI C are released.
+7. Check that the active call is still established.
+8. Clear the active call from Network A's UNI.
+
+9. Check that all resources are released.
+10. Repeat the test for bearer 3.1 kHz audio.
+11. Repeat steps 1-10 with Networks A and C interchanged.
+12. Repeat steps 1-11 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Make a speech call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check the propriety of speech.
+3. Make a speech call from Network C's (Q.767) UNI to Network B's UNI.
+4. Reject the waiting call at Network B's UNI.
+5. Check that all network resources between Network B and Network C and UNI C are released.
+6. Check that the active call is still established.
+7. Clear the active call from Network A's UNI.
+8. Check that all resources are released.
+9. Repeat the test for bearer 3.1 kHz audio.
+10. Repeat steps 1-9 with Networks A and C interchanged.
+
+**Test number:** 2.10.3 **Ref.:** 1/Q.733, 1/Q.953.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Call Waiting ignored
+
+**Purpose:** Verify that a waiting call is released after the call waiting supervision timer or T9/Q.764 expired.
+
+**Pre-test conditions:**
+
+1. Arrange exchange data such that the requested Call Waiting is supported at Network B's UNI.
+2. One channel available at UNI B (all other channels are busy).
+
+#### **Expected message sequence**
+
+
+
+| Network A | Network B | Network C | |
+|----------------------------------------|---------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM →
← ACM
← ANM | | | Simplified call establishment |
+| ⇐ COMMUNICATION ⇒ | | | |
+| ← IAM
← COT Optional message | | | |
+| Case a | ACM → | | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), GenNot: Call is a waiting call (1100000) |
+| Case b | ACM → | | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | CPG → | | GenNot: Call is a waiting call (1100000), Event Info: alerting (0000001) |
+| Case A | ↓ T9/ Q.764 ← REL | | Cause Ind.: No answer from user (19), location public network serving remote user (0100) |
+| | RLC → | | |
+| Case B | T301/ Q.931 ↓ REL → | | Cause Ind.: No answer from user (19), location public network serving remote user (0100) |
+| | ← RLC | | |
+| ⇐ COMMUNICATION ⇒ | | | |
+| | ← REL | | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | RLC → | | |
+
+#### **Test description (ISUP'92):**
+
+1. Make a speech call from Network A's UNI to Network B's UNI.
+2. Check the propriety of speech.
+3. Make a speech call from Network C's UNI to Network B's UNI.
+4. Check that notification is received at Network C's UNI.
+5. Check that waiting call is released after Timer expiry.
+
+6. Check that all network resources between Network B and Network C, and UNI C are released.
+7. Check that the active call is still established.
+8. Clear the active call from Network A's UNI.
+9. Check that all resources are released.
+10. Repeat the test for bearer 3.1 kHz audio.
+11. Repeat steps 1-10 with Networks A and C interchanged.
+12. Repeat steps 1-11 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Make a speech call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check the propriety of speech.
+3. Make a speech call from Network C's (Q.767) UNI to Network B's UNI.
+4. Check that waiting call is released after Timer expiry.
+5. Check that all network resources between Network B and Network C, and UNI C are released.
+6. Check that the active call is still established.
+7. Clear the active call from Network A's UNI.
+8. Check that all resources are released.
+9. Repeat the test for bearer 3.1 kHz audio.
+10. Repeat steps 1-9 with Networks A and C interchanged.
+
+**Test number:** 2.11.1 **Ref.:** 2/Q.733, 2/Q.953.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Call Hold – Hold and Retrieve during waiting for ANM
+
+**Purpose:** To verify that Call Hold can be initiated, a notification is transferred and the call can be retrieved.
+
+**Pre-test conditions:** Arrange exchange data such that the requested Call Hold is supported at Network A's UNI.
+
+#### **Expected message sequence**
+
+
+
+| Network A | | Network B |
+|---------------|---|-----------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| CPG | → | GenNot: Remote hold (1111001), Event Info: Progress (0000010) |
+| CPG | → | GenNot: Remote retrieve (1111010), Event Info: Progress (0000010) |
+| | ← | ANM |
+
+⇐ COMMUNICATION ⇒
+
+| | | |
+|-----|---|-------------------------------------------------------------|
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92):**
+
+- Make a speech call from Network A's UNI to Network B's UNI.
+- Verify that Network B's UNI is alerted.
+- Initiate Call Hold from Network A's UNI.
+- Check that notification *remote hold* is received at Network B's UNI.
+- Check that call is in held state.
+- Initiate Retrieve from Network A's UNI.
+- Check that notification *remote retrieval* is received at Network B's UNI.
+- Check the propriety of speech.
+- Clear the call from Network A's UNI.
+- Check that all resources are released.
+- Repeat the test for bearer 3.1 kHz audio.
+- Repeat steps 1-11 with Networks A and B interchanged.
+
+#### **Test description (Comb):**
+
+1. Make a speech call from Network A's (ISUP'92) UNI to Network B's (Q.767) UNI.
+2. Verify that Network B's UNI is alerted.
+3. Initiate Call Hold from Network A's UNI.
+4. Check that call is in held state.
+5. Initiate Retrieve from Network A's UNI.
+6. Check the propriety of speech.
+7. Clear the call from Network A's UNI.
+8. Check that all resources are released.
+9. Repeat the test for bearer 3.1 kHz audio.
+
+**Test number:** 2.11.2 **Ref.:** 2/Q.733, 2/Q.953.
+
+**Config.:** Multiple ISDN Accesses (See Figure 2)
+
+**Title:** Call Hold – Hold call and clear before Retrieve during waiting for ANM
+
+**Purpose:** To verify that the call can be released after hold is initiated and before it is retrieved.
+
+**Pre-test conditions:** Arrange exchange data such that the requested Call Hold is supported at Network A's UNI.
+
+#### Expected message sequence
+
+| Network A | Network B |
+|-----------|-----------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT → | Optional message |
+| ← Case a | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← Case b | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← CPG | Event Info: alerting (0000001) |
+| CPG → | GenNot: Remote hold (1111001), Event Info: Progress (0000010) |
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | |
+
+#### Test description (ISUP'92):
+
+1. Make a speech call from Network A's UNI to Network B's UNI.
+2. Verify that Network B's UNI is alerted.
+3. Initiate Call Hold from Network A's UNI.
+4. Check that notification *remote hold* is received at Network B's UNI.
+5. Check that call is in held state.
+6. Clear the call from Network A's UNI.
+7. Check that all resources are released.
+8. Repeat the test for bearer 3.1 kHz audio.
+9. Repeat steps 1-8 with Networks A and B interchanged.
+
+#### Test description (Comb):
+
+1. Make a speech call from Network A's (ISUP'92) UNI to Network B's (Q.767) UNI.
+2. Verify that Network B's UNI is alerted.
+3. Initiate Call Hold from Network A's UNI.
+4. Check that call is in held state.
+5. Clear the call from Network A's UNI.
+6. Check that all resources are released.
+7. Repeat the test for bearer 3.1 kHz audio.
+
+**Test number:** 2.11.3 **Ref.:** 2/Q.733, 2/Q.953.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Call Hold – Hold and Retrieve during active phase
+
+**Purpose:** To verify that Call Hold can be initiated, a notification is transferred and the call can be retrieved during active phase.
+
+**Pre-test conditions:** Arrange exchange data such that the requested Call Hold is supported at Network A's and Network B's UNIs.
+
+#### Expected message sequence
+
+
+
+| | Network A | Network B |
+|-------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------|
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| | COT → | Optional message |
+| Case a | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← ANM | |
+| Case b | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← CPG | Event Info: alerting (0000001) |
+| | ← ANM | |
+| ⇐ COMMUNICATION ⇒ | | |
+| Note | CPG → | GenNot: Remote hold (1111001), Event Info: Progress (0000010) |
+| | CPG → | GenNot: Remote retrieve (1111010), Event Info: Progress (0000010) |
+| ⇐ COMMUNICATION ⇒ | | |
+| | ← CPG | GenNot: Remote hold (1111001), Event Info: Progress (0000010) |
+| | ← CPG | GenNot: Remote retrieve (1111010), Event Info: Progress (0000010) |
+| ⇐ COMMUNICATION ⇒ | | |
+| Note | CPG → | GenNot: Remote hold (1111001), Event Info: Progress (0000010) |
+| | ← CPG | GenNot: Remote hold (1111001), Event Info: Progress (0000010) |
+| | CPG → | GenNot: Remote retrieve (1111010), Event Info: Progress (0000010) |
+| | ← CPG | GenNot: Remote retrieve (1111010), Event Info: Progress (0000010) |
+| ⇐ COMMUNICATION ⇒ | | |
+| | REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← RLC | |
+
+NOTE – Only relevant for ISUP'92 in both networks.
+
+#### Test description (ISUP'92):
+
+1. Make a speech call from Network A's UNI to Network B's UNI.
+2. Check the propriety of speech.
+3. Initiate Call Hold from Network A's UNI.
+4. Check that notification *remote hold* is received at Network B's UNI.
+
+5. Check that call is in held state.
+6. Initiate Retrieve from Network A's UNI.
+7. Check that notification *remote retrieval* is received at Network B's UNI.
+8. Check the propriety of speech.
+9. Initiate Call Hold from Network B's UNI
+10. Check that notification *remote hold* is received at Network A's UNI.
+11. Check that call is in held state.
+12. Initiate Retrieve from Network B's UNI.
+13. Check that notification *remote retrieval* is received at Network A's UNI.
+14. Check the propriety of speech.
+15. Initiate Call Hold from Network A's UNI.
+16. Initiate Call Hold from Network B's UNI.
+17. Initiate Retrieve from Network A's UNI.
+18. Check that the call is still in held state.
+19. Initiate Retrieve from Network B's UNI.
+20. Check the propriety of speech.
+21. Clear the call from Network A's UNI.
+22. Check that all resources are released.
+23. Repeat the test for bearer 3.1 kHz audio.
+24. Repeat steps 1-23 with Networks A and B interchanged.
+
+#### **Test description (Comb):**
+
+1. Make a speech call from Network A's (Q.767) UNI to Network B's (ISUP'92) UNI.
+2. Check the propriety of speech.
+3. Initiate Call Hold from Network B's UNI.
+4. Check that call is in held state.
+5. Initiate Retrieve from Network B's UNI.
+6. Check the propriety of speech.
+7. Clear the call from Network A's UNI.
+8. Check that all resources are released.
+9. Repeat the test for bearer 3.1 kHz audio.
+
+**Test number:** 2.11.4 **Ref.:** 2/Q.733, 2/Q.953.
+
+**Config.:** Multiple ISDN Accesses (See Figure 2)
+
+**Title:** Call Hold – Hold during active phase; served user clears call during held state
+
+**Purpose:** To verify that the call can be released in held state.
+
+**Pre-test conditions:** Arrange exchange data such that the requested Call Hold is supported at Network A's UNI.
+
+#### Expected message sequence
+
+| Network A | | Network B |
+|-------------------|---|-----------------------------------------------------------------------------------------------------------------------------------|
+| IAM | ➔ | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | ➔ | Optional message |
+| Case a | ⬅ | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ⬅ | ANM |
+| Case b | ⬅ | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ⬅ | CPG Event Info: alerting (0000001) |
+| | ⬅ | ANM |
+| ⇐ COMMUNICATION ⇒ | | |
+| CPG | ➔ | GenNot: Remote hold (1111001), Event Info: Progress (0000010) |
+| REL | ➔ | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ⬅ | RLC |
+
+#### Test description (ISUP'92):
+
+1. Make a speech call from Network A's UNI to Network B's UNI.
+2. Check the propriety of speech.
+3. Initiate Call Hold from Network A's UNI.
+4. Check that notification remote hold is received at Network B's UNI.
+5. Check that call is in held state.
+6. Clear the call from Network A's UNI.
+7. Check that all resources are released.
+8. Repeat the test for bearer 3.1 kHz audio.
+9. Repeat steps 1-8 with Networks A and B interchanged.
+
+#### **Test description (Comb):**
+
+1. Make a speech call from Network A's (ISUP'92) UNI to Network B's (Q.767) UNI.
+2. Check the propriety of speech.
+3. Initiate Call Hold from Network A's UNI.
+4. Check that call is in held state.
+5. Clear the call from Network A's UNI.
+6. Check that all resources are released.
+7. Repeat the test for bearer 3.1 kHz audio.
+
+**Test number:** 2.11.5 **Ref.:** 2/Q.733, 2/Q.953.
+
+**Config.:** Multiple ISDN Accesses (See Figure 2)
+
+**Title:** Call Hold – Hold during active phase; non-served user clears call during held state
+
+**Purpose:** To verify that the call can be released in held state.
+
+**Pre-test conditions:** Arrange exchange data such that the requested Call Hold is supported at Network A's UNI.
+
+#### Expected message sequence
+
+
+
+| Network A | Network B |
+|-------------------|-----------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT → | Optional message |
+| ← Case a | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← | ANM |
+| ← Case b | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← | CPG Event Info: alerting (0000001) |
+| ← | ANM |
+| ← COMMUNICATION → | |
+| CPG → | GenNot: Remote hold (1111001), Event Info: Progress (0000010) |
+| ← | REL Cause Ind.: Normal call clearing (16), location user (0000) |
+| RLC → | |
+
+#### Test description (ISUP'92):
+
+1. Make a speech call from Network A's UNI to Network B's UNI.
+2. Check the propriety of speech.
+3. Initiate Call Hold from Network A's UNI.
+4. Check that notification remote hold is received at Network B's UNI.
+5. Check that call is in held state.
+6. Clear the call from Network B's UNI.
+7. Check that all resources are released.
+8. Repeat the test for bearer 3.1 kHz audio.
+9. Repeat steps 1-8 with Networks A and B interchanged.
+
+#### **Test description (Comb):**
+
+1. Make a speech call from Network A's(ISUP'92) UNI to Network B's (Q.767) UNI.
+2. Check the propriety of speech.
+3. Initiate Call Hold from Network A's UNI.
+4. Check that call is in held state.
+5. Clear the call from Network B's UNI.
+6. Check that all resources are released.
+7. Repeat the test for bearer 3.1 kHz audio.
+
+**Test number:** 2.12.1 **Ref.:** 4/Q.733, 4/Q.953.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Terminal Portability – Successful
+
+**Purpose:** To verify that Terminal Portability can be initiated on both sides; transportation of Suspend and Resume.
+
+**Pre-test conditions:** Arrange exchange data such that the requested Terminal Portability is supported in both Networks.
+
+#### Expected message sequence
+
+| Network A | | Network B |
+|-------------------|---|-----------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| ← COMMUNICATION → | | |
+| SUS | → | Suspend/Resume Ind.: ISDN subscriber initiated (0) |
+| RES | → | Suspend/Resume Ind.: ISDN subscriber initiated (0) |
+| ← COMMUNICATION → | | |
+| | ← | SUS Suspend/Resume Ind.: ISDN subscriber initiated (0) |
+| | ← | RES Suspend/Resume Ind.: ISDN subscriber initiated (0) |
+| ← COMMUNICATION → | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### Test description (ISUP'92, Comb):
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check the propriety of speech.
+3. Initiate Suspend from Network A's UNI.
+4. Check that Notification *remote user suspended* is received at Network B's UNI.
+5. Initiate Resume from Network A's UNI.
+6. Check that Notification *remote user resumed* is received at Network B's UNI.
+7. Check the propriety of speech.
+
+8. Initiate Suspend from Network B's UNI.
+9. Check that Notification *remote user suspended* is received at Network A's UNI.
+10. Initiate Resume from Network B's UNI.
+11. Check that Notification *remote user resumed* is received at Network A's UNI.
+12. Check the propriety of speech.
+13. Clear the call from Network A's UNI.
+14. Check that all resources are released.
+15. Repeat the test for speech and 3.1 kHz audio bearers.
+16. Repeat steps 1-15 with Networks A and B interchanged.
+
+**Test number:** 2.12.2 **Ref.:** 4/Q.733, 4/Q.953.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** Terminal Portability – Unsuccessful, Timer expiry
+
+**Purpose:** To verify that the call will be successfully released by the Network, if Timer T2 expired.
+
+**Pre-test conditions:** Arrange exchange data such that the requested Terminal Portability is supported.
+
+#### Expected message sequence
+
+| Network A | | Network B |
+|-------------------|---|-----------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| ⇐ COMMUNICATION ⇒ | | |
+| SUS | → | Suspend/Resume Ind.: ISDN subscriber initiated (0) |
+| REL | → | Cause Ind.: Recovery on Timer expiry (102), location public network serving remote user (0100) |
+| | ← | RLC |
+
+#### Test description (ISUP'92, Comb):
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check the propriety of speech.
+3. Initiate Suspend from Network A's UNI.
+4. Check that Notification *remote user suspended* is received at Network B's UNI.
+5. Check that call is released after Timer T2 expired.
+6. Check that all resources are released.
+7. Repeat the test for speech and 3.1 kHz audio bearers.
+8. Repeat steps 1-7 with Networks A and B interchanged.
+
+**Test number:** 2.13.1 **Ref.:** 1/Q.734, 1/Q.954.
+
+**Config.:** Multiple ISDN Accesses (See Figure 5)
+
+**Title:** Conference Calling – Establishment of a conference and termination of the conference
+
+**Purpose:** To verify that a conference can be established and terminated by the served user.
+
+- Pre-test conditions:**
+1. Arrange exchange data such that the requested Conference Calling Supplementary Service is supported at Network B.
+ 2. Floating is not allowed.
+
+#### **Expected message sequence**
+
+
+
+| Network A | Network B | Network C | Network D | |
+|----------------------------------------|-----------|-----------|-----------|--------------------------------------------------------------------------|
+| ← IAM
ACM →
ANM →
| | | | Simplified call establishment |
+| ← COMMUNICATION → | | | | |
+| ← CPG | | | | |
+| | | | | GenNot: Conference established (1000010), Event Info: Progress (0000010) |
+| IAM → | | | | Simplified call establishment |
+| ← ACM | | | | |
+| ← ANM | | | | |
+| CPG → | | | | GenNot: Conference established (1000010), Event Info: Progress (0000010) |
+| ← CPG | | | | GenNot: Other party added (1000100), Event Info: Progress (0000010) |
+| ← CONFERENCE COMMUNICATION → | | | | |
+| IAM → | | | | Simplified call establishment |
+| ← ACM | | | | |
+| ← ANM | | | | |
+| CPG → | | | | GenNot: Conference established (1000010), Event Info: Progress (0000010) |
+| ← CPG | | | | GenNot: Other party added (1000100), Event Info: Progress (0000010) |
+| CPG → | | | | GenNot: Other party added (1000100), Event Info: Progress (0000010) |
+
+Sequence diagram for simplified call establishment between Network A and Network D. Network A sends IAM to Network B, which returns ACM and ANM. Network B then sends CPG to Network D.
+
+Network A Network B Network C Network D
+
+⇐ CONFERENCE COMMUNICATION ⇒
+
+
+
+| | | |
+|-------|-------|----------------------------------------------------------------|
+| ← REL | | Cause Ind.: Normal call clearing (16),
location user (0000) |
+| RLC → | | |
+| REL → | | Cause Ind.: Normal call clearing (16),
location user (0000) |
+| | ← RLC | |
+| REL → | | Cause Ind.: Normal call clearing (16),
location user (0000) |
+| | ← RLC | |
+
+#### **Test description (ISUP'92):**
+
+1. Make a speech call from Network B's UNI to Network A's UNI.
+2. Check the propriety of speech.
+3. Request a conference at Network B's UNI.
+4. Check that notification *conference established* is received at Network A's UNI.
+5. Make a speech call from Network B's UNI to Network C's UNI.
+6. Request to add a new conferee to the conference.
+7. Check that notification *conference established* is received at Network C's UNI.
+8. Check that notification *other party added* is received at Network A's UNI.
+9. Check the propriety of speech for the whole conference.
+10. Make a speech call from Network B's UNI to Network D's UNI.
+11. Request to add a new conferee to the conference.
+12. Check that notification *conference established* is received at Network D's UNI.
+13. Check that notification *other party added* is received at Network A's UNI and Network C's UNI.
+14. Check the propriety of speech for the whole conference.
+15. Other parties may be added in the same way until the maximum number of conferees is reached.
+16. Request the termination of the whole conference.
+17. Check that no notifications are sent to either terminal.
+18. Check that all resources are released.
+19. Repeat the test for bearer 3.1 kHz audio.
+20. Repeat steps 1-19 with Networks A, C and D interchanged.
+21. Repeat steps 1-20 with Networks A, C and D in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Make a speech call from Network B's (ISUP'92) UNI to Network A's (Q.767) UNI.
+2. Check the propriety of speech.
+3. Request a conference at Network B's UNI.
+4. Make a speech call from Network B's UNI to Network C's (Q.767) UNI.
+5. Request to add a new conferee to the conference.
+6. Check the propriety of speech for the whole conference.
+7. Make a speech call from Network B's UNI to Network D's (Q.767) UNI.
+8. Request to add a new conferee to the conference.
+9. Check the propriety of speech for the whole conference.
+10. Other parties may be added in the same way until the maximum number of conferees is reached.
+11. Request the termination of the whole conference.
+12. Check that no notifications are sent to either terminal.
+13. Check that all resources are released.
+14. Repeat the test for bearer 3.1 kHz audio.
+15. Repeat steps 1-14 with Networks A, C and D interchanged.
+
+**Test number:** 2.13.2 **Ref.:** 1/Q.734, 1/Q.954.
+
+**Config.:** Multiple ISDN Accesses (See Figure 5)
+
+**Title:** Conference Calling – Isolation, Reattachement and Disconnection of one party of the conference
+
+**Purpose:** To verify that one party can be isolated and reattached and that one party can be disconnected by the served user.
+
+**Pre-test conditions:** Arrange exchange data such that the requested Conference Calling Supplementary Service is supported at Network B.
+
+#### **Expected message sequence**
+
+Network A Network B Network C Network D
+
+| | |
+|--------------------------|-------------------------------|
+| ————— ← IAM ————— | Simplified call establishment |
+| ACM → ————— | |
+| ANM → ————— | |
+
+⇐ COMMUNICATION ⇨
+
+| | |
+|--------------------------|--------------------------------------------------------------------------|
+| ————— ← CPG ————— | GenNot: Conference established (1000010), Event Info: Progress (0000010) |
+| ————— IAM → | Simplified call establishment |
+| ————— ← ACM | |
+| ————— ← ANM | |
+| ————— CPG → | GenNot: Conference established (1000010), Event Info: Progress (0000010) |
+| ← CPG ————— | GenNot: Other party added (1000100), Event Info: Progress (0000010) |
+
+⇐ CONFERENCE COMMUNICATION ⇨
+
+| | |
+|--------------------------|--------------------------------------------------------------------------|
+| ————— IAM ————— → | Simplified call establishment |
+| ————— ← ————— ACM | |
+| ————— ← ————— ANM | |
+| ————— CPG ————— → | GenNot: Conference established (1000010), Event Info: Progress (0000010) |
+| ← ————— CPG ————— | GenNot: Other party added (1000100), Event Info: Progress (0000010) |
+| ————— CPG ————— → | GenNot: Other party added (1000100), Event Info: Progress (0000010) |
+
+⇐ CONFERENCE COMMUNICATION ⇨
+
+| | |
+|--------------------------|------------------------------------------------------------------------|
+| ————— ← CPG ————— | GenNot: isolated (1000101), Event Info: Progress (0000010) |
+| ————— CPG ————— → | GenNot: Other party isolated (1000111), Event Info: Progress (0000010) |
+| ————— CPG ————— → | GenNot: Other party isolated (1000111), Event Info: Progress (0000010) |
+
+Network A Network B Network C Network D
+
+⇐ CONFERENCE COMMUNICATION ⇒
+
+| | |
+|-------|--------------------------------------------------------------------------|
+| ← CPG | GenNot: reattached (1000110), Event Info: Progress (0000010) |
+| CPG → | GenNot: Other party reattached (1001000), Event Info: Progress (0000010) |
+| CPG → | GenNot: Other party reattached (1001000), Event Info: Progress (0000010) |
+
+⇐ CONFERENCE COMMUNICATION ⇒
+
+| | |
+|-------|----------------------------------------------------------------------------|
+| ← REL | Cause Ind.: Normal call clearing (16), location user (0000) |
+| RLC → | |
+| CPG → | GenNot: Other party disconnected (1001010), Event Info: Progress (0000010) |
+| CPG → | GenNot: Other party disconnected (1001010), Event Info: Progress (0000010) |
+
+⇐ CONFERENCE COMMUNICATION ⇒
+
+| | |
+|-------|-------------------------------------------------------------|
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | |
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | |
+
+#### **Test description (ISUP'92):**
+
+1. Make a speech call from Network B's UNI to Network A's UNI.
+2. Check the propriety of speech.
+3. Request a conference at Network B's UNI.
+4. Check that notification *conference established* is received at Network A's UNI.
+5. Make a speech call from Network B's UNI to Network C's UNI.
+6. Request to add a new conferee to the conference.
+7. Check that notification *conference established* is received at Network C's UNI.
+8. Check that notification *other party added* is received at Network A's UNI.
+9. Check the propriety of speech for the whole conference.
+10. Make a speech call from Network B's UNI to Network D's UNI.
+11. Request to add a new conferee to the conference.
+12. Check that notification *conference established* is received at Network D's UNI.
+13. Check that notification *other party added* is received at Network A's UNI and Network C's UNI.
+14. Check the propriety of speech for the whole conference.
+15. Request the isolation of Network A's UNI.
+16. Check that notification *isolated* is received at Network A's UNI.
+
+17. Check that notification *other party isolated* is received at Network C's UNI and Network D's UNI.
+18. Check that no communication in either direction is possible at Network A's UNI.
+19. Request the reattaching of Network A's UNI.
+20. Check that notification *reattached* is received at Network A's UNI.
+21. Check that notification *other party reattached* is received at Network C's UNI and Network D's UNI.
+22. Check that communication for Network A's UNI is possible in either direction.
+23. Clear the call to Network A's UNI from Network B's UNI.
+24. Check that notification *other party disconnected* is received at Network C's UNI and Network D's UNI.
+25. Check that the conference is still established.
+26. Terminate the conference.
+27. Check that all resources are released.
+28. Repeat the test for bearer 3.1 kHz audio.
+29. Repeat steps 1-28 with Networks A, C and D interchanged.
+30. Repeat steps 1-29 with Networks A, C and D in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Make a 64 kbit/s call from Network B's (ISUP'92) UNI to Network A's (Q.767) UNI.
+2. Check the propriety of speech.
+3. Request a conference at Network B's UNI.
+4. Make a speech call from Network B's UNI to Network C's (Q.767) UNI.
+5. Request to add a new conferee to the conference.
+6. Check the propriety of speech for the whole conference.
+7. Make a speech call from Network B's UNI to Network D's (Q.767) UNI.
+8. Request to add a new conferee to the conference.
+9. Check the propriety of speech for the whole conference.
+10. Request the isolation of Network A's UNI.
+11. Check that no communication in either direction is possible at Network A's UNI.
+12. Request the reattaching of Network A's UNI.
+13. Check that communication for Network A's UNI is possible in either direction.
+14. Clear the call to Network A's UNI from Network B's UNI.
+15. Check that the conference is still established.
+16. Terminate the conference.
+17. Check that all resources are released.
+18. Repeat the test for bearer 3.1 kHz audio.
+19. Repeat steps 1-18 with Networks A, C and D interchanged.
+
+**Test number:** 2.13.3 **Ref.:** 1/Q.734, 1/Q.954.
+
+**Config.:** Multiple ISDN Accesses (See Figure 5)
+
+**Title:** Conference Calling – Splitting and Adding of a party
+
+**Purpose:** To verify that one party can be split and added.
+
+**Pre-test conditions:** Arrange exchange data such that the requested Conference Calling Supplementary Service is supported at Network B.
+
+#### **Expected message sequence**
+
+Network A Network B Network C Network D
+
+
+
+| | | |
+|-------------------------------------|--|---------------------------------------------------------------------------|
+| ← IAM | | Simplified call establishment |
+| ACM → | | |
+| ANM → | | |
+| ← COMMUNICATION → | | |
+| ← CPG | | GenNot: Conference established (1000010), Event Info: Progress (0000010) |
+| IAM → | | Simplified call establishment |
+| ← ACM | | |
+| ← ANM | | |
+| CPG → | | GenNot: Conference established (1000010), Event Info: Progress (0000010) |
+| ← CPG | | GenNot: Other party added (1000100), Event Info: Progress (0000010) |
+| ← CONFERENCE COMMUNICATION → | | |
+| IAM → | | Simplified call establishment |
+| ← ACM | | |
+| ← ANM | | |
+| CPG → | | GenNot: Conference established (1000010), Event Info: Progress (0000010) |
+| ← CPG | | GenNot: Other party added (1000100), Event Info: Progress (0000010) |
+| CPG → | | GenNot: Other party added (1000100), Event Info: Progress (0000010) |
+| ← CONFERENCE COMMUNICATION → | | |
+| ← CPG | | GenNot: conference disconnected (1000011), Event Info: Progress (0000010) |
+| CPG → | | GenNot: Other party split (1001001), Event Info: Progress (0000010) |
+| CPG → | | GenNot: Other party split (1001001), Event Info: Progress (0000010) |
+
+Network A Network B Network C Network D
+
+← COMMUNICATION ⇒ ← COMMUNICATION ⇒
+
+| | |
+|-------|--------------------------------------------------------------------------|
+| ← CPG | GenNot: Conference established (1000010), Event Info: Progress (0000010) |
+| CPG → | GenNot: Other party added (1000100), Event Info: Progress (0000010) |
+| CPG → | GenNot: Other party added (1000100), Event Info: Progress (0000010) |
+
+← CONFERENCE COMMUNICATION ⇒
+
+| | |
+|-------|----------------------------------------------------------------------------|
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | |
+| CPG → | GenNot: Other party disconnected (1001010), Event Info: Progress (0000010) |
+| CPG → | GenNot: Other party disconnected (1001010), Event Info: Progress (0000010) |
+
+← CONFERENCE COMMUNICATION ⇒
+
+| | |
+|-------|----------------------------------------------------------------------------|
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | |
+| CPG → | GenNot: Other party disconnected (1001010), Event Info: Progress (0000010) |
+
+← COMMUNICATION ⇒
+
+| | |
+|-------|-------------------------------------------------------------|
+| ← REL | Cause Ind.: Normal call clearing (16), location user (0000) |
+| RLC → | |
+
+#### Test description (ISUP'92):
+
+1. Make a speech call from Network B's UNI to Network A's UNI.
+2. Check the propriety of speech.
+3. Request a conference at Network B's UNI.
+4. Check that notification *conference established* is received at Network A's UNI.
+5. Make a speech call from Network B's UNI to Network C's UNI.
+6. Request to add a new conferee to the conference.
+7. Check that notification *conference established* is received at Network C's UNI.
+8. Check that notification *other party added* is received at Network A's UNI.
+9. Check the propriety of speech for the whole conference.
+10. Make a speech call from Network B's UNI to Network D's UNI.
+11. Request to add a new conferee to the conference.
+12. Check that notification *conference established* is received at Network D's UNI.
+13. Check that notification *other party added* is received at Network A's UNI and Network C's UNI.
+14. Check the propriety of speech for the whole conference.
+
+15. Request the splitting of Network A's UNI.
+16. Check that notification *conference disconnected* is received at Network A's UNI.
+17. Check that notification *other party split* is received at Network C's UNI and Network D's UNI.
+18. Check that private communication between Network A's UNI and Network B's UNI is possible.
+19. Check that a conference call between Network C's UNI and Network D's UNI is possible.
+20. Request the reattaching of Network A's UNI and Network B's UNI.
+21. Check that notification *conference established* is received at Network A's UNI.
+22. Check that notification *other party added* is received at Network C's UNI and Network D's UNI.
+23. Check that communication within the whole conference is possible.
+24. Clear the call from Network A's UNI.
+25. Check that notification *other party disconnected* is received at Network C's UNI and Network D's UNI.
+26. Check that the conference is still established.
+27. Clear the call from Network B's UNI to Network D's UNI.
+28. Check that notification *other party disconnected* is received at Network C's UNI.
+29. Check that the conference is still established.
+30. Clear the call from Network C's UNI.
+31. Check that all resources are released.
+32. Repeat the test for bearer 3.1 kHz audio.
+33. Repeat steps 1-32 with the Networks A, C and D interchanged.
+34. Repeat steps 1-33 with Networks A, C and D in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Make a 64 kbit/s call from Network B's (ISUP'92) UNI to Network A's (Q.767) UNI.
+2. Check the propriety of speech.
+3. Request a conference at Network B's UNI.
+4. Make a speech call from Network B's UNI to Network C's (Q.767) UNI.
+5. Request to add a new conferee to the conference.
+6. Check the propriety of speech for the whole conference.
+7. Make a speech call from Network B's UNI to Network D's (Q.767) UNI.
+8. Request to add a new conferee to the conference.
+9. Check the propriety of speech for the whole conference.
+10. Request the splitting of Network A's UNI.
+11. Check that private communication between Network A's UNI and Network B's UNI is possible.
+12. Check that a conference call between Network C's UNI and Network D's UNI is possible.
+13. Request the reattaching of Network A's UNI and Network B's UNI.
+14. Check that communication within the whole conference is possible.
+
+15. Clear the call from Network A's UNI.
+16. Check that the conference is still established.
+17. Clear the call from Network B's UNI to Network D's UNI.
+18. Check that the conference is still established.
+19. Clear the call from Network C's UNI.
+20. Check that all resources are released.
+21. Repeat the test for bearer 3.1 kHz audio.
+22. Repeat steps 1-21 with Networks A, C and D interchanged.
+
+**Test number:** 2.13.4 **Ref.:** 1/Q.734, 1/Q.954.
+
+**Config.:** Multiple ISDN Accesses (See Figure 5)
+
+**Title:** Conference Calling – Floating of a conference (explicit request)
+
+**Purpose:** To verify that it is possible to disconnect the served user.
+
+- Pre-test conditions:**
+1. Arrange exchange data such that the requested Conference Calling Supplementary Service is supported at Network B.
+ 2. Floating is allowed.
+
+#### **Expected message sequence**
+
+
+
+| Network A | Network B | Network C | Network D | |
+|----------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|-----------|----------------------------------------------------------------------------------|
+| ← IAM
ACM →
ANM →
| | | | Simplified call establishment |
+| ← COMMUNICATION → | | | | |
+| ← CPG
| | | | |
+| IAM →
← ACM
← ANM
| | | | Simplified call establishment |
+| CPG →
| | | | |
+| ← CPG
| | | | |
+| ← CONFERENCE COMMUNICATION → | | | | |
+| IAM →
← ACM
← ANM
| | | | Simplified call establishment |
+| CPG →
| | | | |
+| ← CPG
CPG →
| | | | |
+| ← CONFERENCE COMMUNICATION → | | | | |
+| ← CPG
CPG →
| | | | GenNot: conference floating (1001011),
Event Info: Progress (0000010)
|
+| CPG →
| | | | GenNot: conference floating (1001011),
Event Info: Progress (0000010)
|
+
+Network A Network B Network C Network D
+
+⇐ CONFERENCE COMMUNICATION ⇒
+
+| | | | |
+|--|---|-----|----------------------------------------------------------------------------|
+| | ← | REL | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | → | RLC | |
+| | → | CPG | GenNot: Other party disconnected (1001010), Event Info: Progress (0000010) |
+| | ← | CPG | GenNot: Other party disconnected (1001010), Event Info: Progress (0000010) |
+
+⇐ CONFERENCE COMMUNICATION ⇒
+
+| | | | |
+|--|---|-----|----------------------------------------------------------------------------|
+| | ← | REL | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | → | RLC | |
+| | ← | CPG | GenNot: Other party disconnected (1001010), Event Info: Progress (0000010) |
+| | ← | REL | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | → | RLC | |
+
+#### Test description (ISUP'92):
+
+1. Make a speech call from Network B's UNI to Network A's UNI.
+2. Check the propriety of speech.
+3. Request a conference at Network B's UNI.
+4. Check that notification *conference established* is received at Network A's UNI.
+5. Make a speech call from Network B's UNI to Network C's UNI.
+6. Request to add a new conferee to the conference.
+7. Check that notification *conference established* is received at Network C's UNI.
+8. Check that notification *other party added* is received at Network A's UNI.
+9. Check the propriety of speech for the whole conference.
+10. Make a speech call from Network B's UNI to Network D's UNI.
+11. Request to add a new conferee to the conference.
+12. Check that notification *conference established* is received at Network D's UNI.
+13. Check that notification *other party added* is received at Network A's UNI and Network C's UNI.
+14. Check the propriety of speech for the whole conference.
+15. Network B's UNI invokes floating.
+16. Check that notification *conference floating* is received at Networks A's, C's and D's UNI.
+17. Check that all network resources between Network B's UNI and the conference bridge are released.
+18. Check that communication within the conference is possible.
+19. Clear the call from Network D's UNI.
+
+20. Check that notification *other party disconnected* is received at Network A's UNI and Network C's UNI.
+21. Check that the conference is still established.
+22. Clear the call from Network C's UNI.
+23. Check that notification *other party disconnected* is received at Network A's UNI.
+24. Check that the originating local switch clears the call between Network A's UNI and the conference bridge.
+25. Check that all resources are released.
+26. Repeat the test for bearer 3.1 kHz audio.
+27. Repeat steps 1-26 with Networks A, C and D interchanged.
+28. Repeat steps 1-27 with Networks A, C and D in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Make a 64 kbit/s call from Network B's (ISUP'92) UNI to Network A's (Q.767) UNI.
+2. Check the propriety of speech.
+3. Request a conference at Network B's UNI.
+4. Make a speech call from Network B's UNI to Network C's (Q.767) UNI.
+5. Request to add a new conferee to the conference.
+6. Check the propriety of speech for the whole conference.
+7. Make a speech call from Network B's UNI to Network D's (Q.767) UNI.
+8. Request to add a new conferee to the conference.
+9. Check the propriety of speech for the whole conference.
+10. Network B's UNI invokes floating.
+11. Check that all network resources between Network B's UNI and the conference bridge are released.
+12. Check that communication within the conference is possible.
+13. Clear the call from Network D's UNI.
+14. Check that the conference is still established.
+15. Clear the call from Network C's UNI.
+16. Check that the originating local switch clears the call between Network A's UNI and the conference bridge.
+17. Check that all resources are released.
+18. Repeat the test for bearer 3.1 kHz audio.
+19. Repeat steps 1-18 with Networks A, C and D interchanged.
+
+**Test number:** 2.13.5 **Ref.:** 1/Q.734, 1/Q.954.
+
+**Config.:** Multiple ISDN Accesses (See Figure 5)
+
+**Title:** Conference Calling – Call clearing by served user when floating is allowed
+
+**Purpose:** To verify that floating is possible after clearing by served user.
+
+- Pre-test conditions:**
+1. Arrange exchange data such that the requested Conference Calling Supplementary Service is supported at Network B.
+ 2. Floating is allowed.
+
+#### **Expected message sequence**
+
+
+
+| Network A | Network B | Network C | Network D | |
+|------------------------------------------|-----------|-----------|-----------|--------------------------------------------------------------------------|
+| ← IAM
| | | | Simplified call establishment |
+| ACM →
| | | | |
+| ANM →
| | | | |
+| ⇒ COMMUNICATION ⇒ | | | | |
+| ← CPG
| | | | GenNot: Conference established (1000010), Event Info: Progress (0000010) |
+| IAM →
| | | | Simplified call establishment |
+| ← ACM
| | | | |
+| ← ANM
| | | | |
+| CPG →
| | | | GenNot: Conference established (1000010), Event Info: Progress (0000010) |
+| ← CPG
| | | | GenNot: Other party added (1000100), Event Info: Progress (0000010) |
+| ⇒ CONFERENCE COMMUNICATION ⇒ | | | | |
+| IAM →
| | | | Simplified call establishment |
+| ← ACM
| | | | |
+| ← ANM
| | | | |
+| CPG →
| | | | GenNot: Conference established (1000010), Event Info: Progress (0000010) |
+| ← CPG
| | | | GenNot: Other party added (1000100), Event Info: Progress (0000010) |
+| CPG →
| | | | GenNot: Other party added (1000100), Event Info: Progress (0000010) |
+| ⇒ CONFERENCE COMMUNICATION ⇒ | | | | |
+| ← CPG
| | | | GenNot: conference floating (1001011), Event Info: Progress (0000010) |
+| CPG →
| | | | GenNot: conference floating (1001011), Event Info: Progress (0000010) |
+| CPG →
| | | | GenNot: conference floating (1001011), Event Info: Progress (0000010) |
+
+Network A Network B Network C Network D
+
+⇐ CONFERENCE COMMUNICATION ⇒
+
+
+
+| | | |
+|-------|-------|-------------------------------------------------------------------------------|
+| | ← REL | Cause Ind.: Normal call clearing (16),
location user (0000) |
+| | RLC → | |
+| | CPG → | GenNot: Other party disconnected
(1001010), Event Info: Progress (0000010) |
+| ← CPG | | GenNot: Other party disconnected
(1001010), Event Info: Progress (0000010) |
+
+⇐ CONFERENCE COMMUNICATION ⇒
+
+| | | |
+|-------|--|-------------------------------------------------------------------------------|
+| ← REL | | Cause Ind.: Normal call clearing (16),
location user (0000) |
+| RLC → | | |
+| ← CPG | | GenNot: Other party disconnected
(1001010), Event Info: Progress (0000010) |
+| ← REL | | Cause Ind.: Normal call clearing (16)
location user (0000) |
+| RLC → | | |
+
+#### Test description (ISUP'92):
+
+1. Make a speech call from Network B's UNI to Network A's UNI.
+2. Check the propriety of speech.
+3. Request a conference at Network B's UNI.
+4. Check that notification *conference established* is received at Network A's UNI.
+5. Make a speech call from Network B's UNI to Network C's UNI.
+6. Request to add a new conferee to the conference.
+7. Check that notification *conference established* is received at Network C's UNI.
+8. Check that notification *other party added* is received at Network A's UNI.
+9. Check the propriety of speech for the whole conference.
+10. Make a speech call from Network B's UNI to Network D's UNI.
+11. Request to add a new conferee to the conference.
+12. Check that notification *conference established* is received at Network D's UNI.
+13. Check that notification *other party added* is received at Network A's UNI and Network C's UNI.
+14. Check the propriety of speech for the whole conference.
+15. The served user clears the call.
+16. Check that conference is floating.
+17. Check that notification *conference floating* is received at Networks A's, C's and D's UNI.
+18. Check that all network resources between Network B's UNI and the conference bridge are released.
+19. Check that communication within the conference is possible.
+20. Clear the call from Network D's UNI.
+
+21. Check that notification *other party disconnected* is received at Network A's UNI and Network C's UNI.
+22. Check that the conference is still established.
+23. Clear the call from Network C's UNI.
+24. Check that notification *other party disconnected* is received at Network A's UNI.
+25. Check that the originating local switch clears the call between Network A's UNI and the conference bridge.
+26. Check that all resources are released.
+27. Repeat the test for bearer 3.1 kHz audio.
+28. Repeat steps 1-27 with Networks A, C and D interchanged.
+29. Repeat steps 1-28 with Networks A, C and D in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Make a 64 kbit/s call from Network B's (ISUP'92) UNI to Network A's (Q.767) UNI.
+2. Check the propriety of speech.
+3. Request a conference at Network B's UNI.
+4. Make a speech call from Network B's UNI to Network C's (Q.767) UNI.
+5. Request to add a new conferee to the conference.
+6. Check the propriety of speech for the whole conference.
+7. Make a speech call from Network B's UNI to Network D's (Q.767) UNI.
+8. Request to add a new conferee to the conference.
+9. Check the propriety of speech for the whole conference.
+10. The served user clears the call.
+11. Check that conference is floating.
+12. Check that all network resources between Network B's UNI and the conference bridge are released.
+13. Check that communication within the conference is possible.
+14. Clear the call from Network D's UNI.
+15. Check that the conference is still established.
+16. Clear the call from Network C's UNI.
+17. Check that the originating local switch clears the call between Network A's UNI and the conference bridge.
+18. Check that all resources are released.
+19. Repeat the test for bearer 3.1 kHz audio.
+20. Repeat steps 1-19 with Networks A, C and D interchanged.
+
+**Test number:** 2.14.1 **Ref.:** 2/Q.734, 2/Q.954.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Three-party service – Invocation and splitting of a Three-party conversation
+
+**Purpose:** To verify that a Three-party conversation can be invoked and split.
+
+**Pre-test conditions:** Arrange the exchange data such that the requested Three-party service is supported at Network B.
+
+#### **Expected message sequence**
+
+
+
+| Network A | Network B | Network C | |
+|----------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|---------------------------------------------------------------------------|
+| ← IAM
ACM →
ANM →
| | | Simplified call establishment |
+| ⇐ COMMUNICATION ⇒ | | | |
+| ← CPG
| | | GenNot: Remote hold (1111001), Event Info: Progress (0000010) |
+| IAM →
← ACM
← ANM
| | | Simplified call establishment |
+| ⇐ COMMUNICATION ⇒ | | | |
+| CPG →
| | | GenNot: Conference established (1000010), Event Info: Progress (0000010) |
+| ← CPG
| | | GenNot: Conference established (1000010), Event Info: Progress (0000010) |
+| ⇐ Three-Party COMMUNICATION ⇒ | | | |
+| CPG →
| | | GenNot: Conference disconnected (1000011), Event Info: Progress (0000010) |
+| ← CPG
| | | GenNot: Conference disconnected (1000011), Event Info: Progress (0000010) |
+| ⇐ COMMUNICATION ⇒ | | | |
+| REL →
| | | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC
| | | |
+| ← CPG
| | | GenNot: Remote retrieval (1111010), Event Info: Progress (0000010) |
+| ⇐ COMMUNICATION ⇒ | | | |
+| ← REL
| | | Cause Ind.: Normal call clearing (16), location user (0000) |
+| RLC →
| | | |
+
+#### **Test description (ISUP'92):**
+
+1. Make a speech call from Network B's UNI to Network A's UNI.
+2. Check the propriety of speech.
+3. Initiate Call Hold at Network B's UNI.
+4. Check that notification *remote hold* is received at Network A's UNI.
+5. Check that call is in held state.
+6. Make a speech call from Network B's UNI to Network C's UNI.
+7. Check the propriety of speech.
+8. Establish Three-Party communication.
+9. Check that notification *conference established* is received at Network A's UNI and Network C's UNI.
+10. Check the propriety of the Three-Party communication.
+11. Split the Three-Party communication.
+12. Check that notification *conference disconnected* is received at Network A's UNI and Network C's UNI.
+13. Check that call between Network A's UNI and Network B's UNI is in held state.
+14. Check the propriety of speech between Network B's UNI and Network C's UNI.
+15. Clear the active call from Network B's UNI.
+16. Check that all resources between UNI B and UNI C are released.
+17. Initiate call retrieval from Network B's UNI.
+18. Check that notification *remote retrieval* is received at Network A's UNI.
+19. Check the propriety of speech.
+20. Clear the call from Network B's UNI.
+21. Check that all resources are released.
+22. Repeat the test for bearer 3.1 kHz audio.
+23. Repeat steps 1-22 with Networks A and C interchanged.
+24. Repeat steps 1-23 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Make a speech call from Network B's (ISUP'92) UNI to Network A's (Q.767) UNI.
+2. Check the propriety of speech.
+3. Initiate Call Hold at Network B's UNI.
+4. Check that call is in held state.
+5. Make a speech call from Network B's UNI to Network C's (Q.767) UNI.
+6. Check the propriety of speech.
+7. Establish Three-Party communication from Network B's UNI.
+8. Check the propriety of the Three-Party communication.
+9. Split the Three-Party communication.
+10. Check that the call between Network A's UNI and Network B's UNI is in held state.
+11. Check the propriety of speech between Network B's UNI and Network C's UNI.
+12. Clear the active call from Network B's UNI.
+
+13. Check that all resources between UNI B and UNI C are released.
+14. Initiate call retrieval from Network B's UNI.
+15. Check the propriety of speech.
+16. Clear the call from Network B's UNI.
+17. Check that all resources are released.
+18. Repeat the test for bearer 3.1 kHz audio.
+19. Repeat steps 1-18 with Networks A and C interchanged.
+
+**Test number:** 2.14.2 **Ref.:** 2/Q.734, 2/Q.954.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Three-party service – Served user disconnects one of the remote users
+
+**Purpose:** To verify that a Three-party conversation can be invoked and the served user can disconnect one of the remote users during Three-Party communication.
+
+**Pre-test conditions:** Arrange the exchange data such that the requested Three-party service is supported at Network B.
+
+#### Expected message sequence
+
+
+
+| Network A | Network B | Network C |
+|-------------------------------|-----------|---------------------------------------------------------------------------|
+| ← IAM | | Simplified call establishment |
+| ACM → | | |
+| ANM → | | |
+| ⇐ COMMUNICATION ⇒ | | |
+| ← CPG | | GenNot: Remote hold (1111001), Event Info: Progress (0000010) |
+| IAM → | | Simplified call establishment |
+| ← ACM | | |
+| ← ANM | | |
+| ⇐ COMMUNICATION ⇒ | | |
+| CPG → | | GenNot: Conference established (1000010), Event Info: Progress (0000010) |
+| ← CPG | | GenNot: Conference established (1000010), Event Info: Progress (0000010) |
+| ⇐ Three-Party COMMUNICATION ⇒ | | |
+| REL → | | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | | |
+| ← CPG | | GenNot: Conference disconnected (1000011), Event Info: Progress (0000010) |
+| ← CPG | | GenNot: Remote retrieval (1111010), Event Info: Progress (0000010) |
+| ⇐ COMMUNICATION ⇒ | | |
+| ← REL | | Cause Ind.: Normal call clearing (16), location user (0000) |
+| RLC → | | |
+
+#### Test description (ISUP'92):
+
+1. Make a speech call from Network B's UNI to Network A's UNI.
+2. Check the propriety of speech.
+3. Initiate Call Hold at Network B's UNI.
+4. Check that notification *remote hold* is received at Network A's UNI.
+
+5. Check that call is in held state.
+6. Make a speech call from Network B's UNI to Network C's UNI.
+7. Check the propriety of speech.
+8. Establish Three-Party communication.
+9. Check that notification *conference established* is received at Network A's UNI and Network C's UNI.
+10. Check the propriety of the Three-Party communication.
+11. Clear the call between Network B's UNI and Network C's UNI from Network B's UNI.
+12. Check that all resources between UNI B and UNI C are released.
+13. Check that notification *conference disconnected* is received at Network A's UNI.
+14. Retrieve call from Network B's UNI.
+15. Check that notification *remote retrieval* is received at Network A's UNI.
+16. Check the propriety of speech.
+17. Clear the call between Network B's UNI and Network A's UNI.
+18. Check that all resources are released.
+19. Repeat the test for bearer 3.1 kHz audio.
+20. Repeat steps 1-19 with Networks A and C interchanged.
+21. Repeat steps 1-20 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Make a speech call from Network B's (ISUP'92) UNI to Network A's (Q.767) UNI.
+2. Check the propriety of speech.
+3. Initiate Call Hold at Network B's UNI.
+4. Check that call is in held state.
+5. Make a speech call from Network B's UNI to Network C's (Q.767) UNI.
+6. Check the propriety of speech.
+7. Establish Three-Party communication from Network B's UNI.
+8. Check the propriety of the Three-Party communication.
+9. Clear the call between Network B's UNI and Network C's UNI from Network B's UNI.
+10. Check that all resources between UNI B and UNI C are released.
+11. Retrieve call from Network B's UNI.
+12. Check the propriety of speech.
+13. Clear the call between Network B's UNI and Network A's UNI.
+14. Check that all resources are released.
+15. Repeat the test for bearer 3.1 kHz audio.
+16. Repeat steps 1-15 with Networks A and C interchanged.
+
+**Test number:** 2.14.3 **Ref.:** 2/Q.734, 2/Q.954.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Three-party service – Disconnect sent by one of the remote users
+
+**Purpose:** To verify that a Three-party conversation can be invoked and one remote user sends disconnect during Three-Party communication.
+
+**Pre-test conditions:** Arrange the exchange data such that the requested Three-party service is supported at Network B.
+
+#### Expected message sequence
+
+
+
+| Network A | Network B | Network C | |
+|-------------------------------|-----------|---------------------------------------------------------------------------|-------------------------------------------------------------|
+| ← IAM | | Simplified call establishment | |
+| ACM | → | | |
+| ANM | → | | |
+| ⇐ COMMUNICATION ⇨ | | | |
+| ← CPG | | GenNot: Remote hold (1111001), Event Info: Progress (0000010) | |
+| IAM → | | Simplified call establishment | |
+| ← ACM | | | |
+| ← ANM | | | |
+| ⇐ COMMUNICATION ⇨ | | | |
+| CPG → | | GenNot: Conference established (1000010), Event Info: Progress (0000010) | |
+| ← CPG | | GenNot: Conference established (1000010), Event Info: Progress (0000010) | |
+| ⇐ Three-Party COMMUNICATION ⇨ | | | |
+| REL | → | | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | | | |
+| CPG → | | GenNot: Conference disconnected (1000011), Event Info: Progress (0000010) | |
+| ⇐ COMMUNICATION ⇨ | | | |
+| REL → | | Cause Ind.: Normal call clearing (16), location user (0000) | |
+| ← RLC | | | |
+
+#### Test description (ISUP'92):
+
+1. Make a speech call from Network B's UNI to Network A's UNI.
+2. Check the propriety of speech.
+3. Initiate Call Hold at Network B's UNI.
+4. Check that notification *remote hold* is received at Network A's UNI.
+5. Check that call is in held state.
+6. Make a speech call from Network B's UNI to Network C's UNI.
+
+7. Check the propriety of speech.
+8. Establish Three-Party communication.
+9. Check that notification *conference established* is received at Network A's UNI and Network C's UNI.
+10. Check the propriety of the Three-Party communication.
+11. Clear the call between Network B's UNI and Network A's UNI from Network A's UNI.
+12. Check that all resources between UNI A and UNI B are released.
+13. Check that notification *conference disconnected* is received at Network C's UNI.
+14. Check the propriety of speech.
+15. Clear the call between Network B's UNI and Network C's UNI.
+16. Check that all resources are released.
+17. Repeat the test for bearer 3.1 kHz audio.
+18. Repeat steps 1-17 with Networks A and C interchanged.
+19. Repeat steps 1-18 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Make a speech call from Network B's (ISUP'92) UNI to Network A's (Q.767) UNI.
+2. Check the propriety of speech.
+3. Initiate Call Hold at Network B's UNI.
+4. Check that call is in held state.
+5. Make a speech call from Network B's UNI to Network C's (Q.767) UNI.
+6. Check the propriety of speech.
+7. Establish Three-Party communication from Network B's UNI.
+8. Check the propriety of the Three-Party communication.
+9. Clear the call between Network B's UNI and Network A's UNI from Network A's UNI.
+10. Check that all resources between UNI A and UNI B are released.
+11. Check the propriety of speech.
+12. Clear the call between Network B's UNI and Network C's UNI.
+13. Check that all resources are released.
+14. Repeat the test for bearer 3.1 kHz audio.
+15. Repeat steps 1-14 with Networks A and C interchanged.
+
+**Test number:** 2.14.4 **Ref.:** 2/Q.734, 2/Q.953.
+
+**Config.:** Multiple ISDN Accesses (See Figure 4)
+
+**Title:** Three-party service – Disconnect of the entire call
+
+**Purpose:** To verify that a Three-party conversation can be invoked and the entire call can be disconnected.
+
+**Pre-test conditions:** Arrange the exchange data such that the requested Three-party service is supported at Network B.
+
+#### **Expected message sequence**
+
+Network A Network B Network C
+
+| | |
+|-------------------------------|---------------------------------------------------------------------------|
+| ← IAM | Simplified call establishment |
+| ACM → | |
+| ANM → | |
+| ⇐ COMMUNICATION ⇨ | |
+| ← CPG | GenNot: Remote hold (1111001), Event Info: Progress (0000010) |
+| IAM → | Simplified call establishment |
+| ← ACM | |
+| ← ANM | |
+| ⇐ COMMUNICATION ⇨ | |
+| CPG → | GenNot: Conference established (1000010), Event Info: Progress (0000010) |
+| ← CPG | GenNot: Conference established (1000010), Event Info: Progress (0000010) |
+| ⇐ Three-Party COMMUNICATION ⇨ | |
+| Case a ← REL | Cause Ind.: Normal call clearing (16), location user (0000) |
+| RLC → | |
+| CPG → | GenNot: Conference disconnected (1000011), Event Info: Progress (0000010) |
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | |
+| Case b REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | |
+| ← CPG | GenNot: Conference disconnected (1000011), Event Info: Progress (0000010) |
+| ← REL | Cause Ind.: Normal call clearing (16), location user (0000) |
+| RLC → | |
+
+#### **Test description (ISUP'92):**
+
+1. Make a speech call from Network B's UNI to Network A's UNI.
+2. Check the propriety of speech.
+3. Initiate Call Hold at Network B's UNI.
+4. Check that notification *remote hold* is received at Network A's UNI.
+5. Check that call is in held state.
+6. Make a speech call from Network B's UNI to Network C's UNI.
+7. Check the propriety of speech.
+8. Establish Three-Party communication.
+9. Check that notification *conference established* is received at Network A's UNI and Network C's UNI.
+10. Check the propriety of the Three-Party communication.
+11. Clear the entire call from Network B's UNI.
+12. Check that notification *conference disconnected* is received at one of the remote UNIs.
+13. Check that all resources are released.
+14. Repeat the test for bearer 3.1 kHz audio.
+15. Repeat steps 1-14 with Networks A and C interchanged.
+16. Repeat steps 1-15 with Networks A and C in the role of Network B.
+
+#### **Test description (Comb):**
+
+1. Make a speech call from Network B's (ISUP'92) UNI to Network A's (Q.767) UNI.
+2. Check the propriety of speech.
+3. Initiate Call Hold at Network B's UNI.
+4. Check that call is in held state.
+5. Make a speech call from Network B's UNI to Network C's (Q.767) UNI.
+6. Check the propriety of speech.
+7. Establish Three-Party communication from Network B's UNI.
+8. Check the propriety of the Three-Party communication.
+9. Clear the entire call from Network B's UNI.
+10. Check that all resources are released.
+11. Repeat the test for bearer 3.1 kHz audio.
+12. Repeat steps 1-11 with Networks A and C interchanged.
+
+**Test number:** 2.15.1 **Ref.:** 1.1.5.2.1.1/Q.737, 1.5.2.1.1/Q.957.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** User-to-User Signalling service 1 – Implicit request – Successful – UUI in the forward and backward messages
+
+**Purpose:** To verify that user-to-user information can be correctly transferred in both directions.
+
+- Pre-test conditions:**
+1. Arrange the stimulus such that the IAM and REL messages contain the UUI parameter with the maximum number of octets in the UUI.
+ 2. Arrange exchange data such that the requested UUS is supported.
+ 3. Arrange the stimuli such that the backward messages generated contain a UUI parameter.
+
+#### Expected message sequence
+
+| Network A | | Network B |
+|-------------------|---|------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | ➔ | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), UUI present |
+| COT | ➔ | Optional message |
+| Case a | ⬅ | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), UUI present |
+| | ⬅ | ANM UUI present |
+| Case b | ⬅ | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ⬅ | CPG Event Info: alerting (0000001), UUI present |
+| | ⬅ | ANM UUI present |
+| Case c | ⬅ | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), UUI present |
+| ⬅ COMMUNICATION ➔ | | |
+| REL | ➔ | UUI present, Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ⬅ | RLC |
+
+#### Test description (ISUP'92, Comb):
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify the UUI in the appropriate messages.
+3. Check the propriety of digital data transmission or speech.
+4. Clear the call from Network A's UNI.
+5. Verify the UUI in the appropriate messages.
+6. Check that all resources are released.
+7. Repeat the test for speech and 3.1 kHz audio bearers.
+8. Repeat steps 1-7 with Networks A and B interchanged.
+
+**Test number:** 2.15.2 **Ref.:** 1.1.5.2.5.2.3/Q.737, 1.5.2.1.1/Q.957.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** UUS service 1 – Implicit request – Discard of UUI by the network
+
+**Purpose:** To verify that UUI can be discarded by the network without disrupting normal call handling.
+
+**Pre-test conditions:**
+
+1. Arrange the stimulus such that the IAM message contains the UUI parameter.
+2. The requested UUS is not supported in Network B.
+
+#### **Expected message sequence**
+
+
+
+| Network A | | Network B |
+|-------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), UUI present |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), UUIInd.: UUI discarded by the network |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), UUIInd.: UUI discarded by the network |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), UUIInd.: UUI discarded by the network |
+| ← COMMUNICATION → | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify the UUI in the SETUP and IAM in Network A.
+3. Verify that the call is completed after UUI is discarded.
+4. Check that notification UUI discarded by the network is received at Network A's UNI.
+5. Check the propriety of digital data transmission or speech.
+6. Clear the call from Network A's UNI.
+7. Check that all resources are released.
+8. Repeat the test for speech and 3.1 kHz audio bearers.
+
+- Test number:** 2.15.3 **Ref.:** 1.1.5.2.1.1.2/Q.737, 1.5.2.1.1.2/Q.957.
+- Config.:** ISDN Access → ISDN Access (See Figure 2)
+- Title:** UUS service 1 – Explicit request – Successful – UUI in the forward and backward messages
+- Purpose:** To verify that the user-to-user information can be correctly transferred in both directions.
+- Pre-test conditions:**
+1. Arrange the stimulus such that the IAM generated contains an UUI parameter.
+ 2. Only one terminal at Network B's UNI should react to the incoming SETUP.
+ 3. Arrange exchange data such that the requested UUS1 is supported.
+ 4. Arrange the stimulus such that the backward messages generated contain a UUI parameter.
+
+#### **Expected message sequence**
+
+
+
+| Network A | | Network B |
+|-------------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), UUInd.: UUS1 request – not-essential (10) or essential (11), UUI present – see Note |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), UUI present, UUInd.: UUS1 provided (10) |
+| | ← | ANM UUI present |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001), UUI present, UUInd.: UUS1 provided (10) |
+| | ← | ANM UUI present |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) UUI present, UUInd.: UUS1 provided (10) |
+| ⇐ COMMUNICATION ⇒ | | |
+| | ← | REL Cause Ind.: Normal call clearing (16), location user (0000), UUI present |
+| RLC | → | |
+
+NOTE – FCI: ISUP required all the way (10) is set in case of an essential request.
+
+#### **Test description (ISUP'92):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify the UUI and the UUInd in the appropriate messages.
+3. Check the propriety of digital data transmission or speech.
+
+4. Clear the call from Network B's UNI.
+5. Verify the UUI in the appropriate messages.
+6. Check that all resources are released.
+7. Repeat the test for speech and 3.1 kHz audio bearers.
+8. Repeat steps 1-7 with Networks A and B interchanged.
+
+**Test number:** 2.15.4 **Ref.:** 1.1.5.2.5.2.2/Q.737, 1.5.2.1.1.2/Q.957.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** User-to-User Signalling service 1 – Explicit request (not-essential) – Implicit rejection by the network
+
+**Purpose:** To verify that the UUS service 1 Explicit request can be correctly rejected.
+
+**Pre-test conditions:**
+
+1. Arrange the stimulus such that the IAM generated contains a UUI parameter.
+2. The requested UUS1 is implicitly rejected in Network B.
+
+#### **Expected message sequence**
+
+
+
+| Network A | | Network B |
+|-------------------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), UUIInd.: UUS1 request – not-essential (10), UUI present |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ⇐ COMMUNICATION ⇒ | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify that UUI is discarded in Network B.
+3. Verify that the call is completed.
+4. Check the propriety of digital data transmission or speech.
+5. Clear the call from Network A's UNI.
+6. Check that all resources are released.
+7. Repeat the test for speech and 3.1 kHz audio bearers.
+
+**Test number:** 2.15.5 **Ref.:** 1.1.5.2.5.2.2/Q.737, 1.5.2.1.1.2/Q.957.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** User-to-User Signalling service 1 – Explicit request (not-essential) – Explicit rejection by the network
+
+**Purpose:** To verify that the UUI is explicitly discarded without disrupting the call establishment.
+
+- Pre-test conditions:**
+1. Arrange the stimulus such that the IAM generated contains a UUI parameter.
+ 2. Arrange exchange data such that the requested UUS1 is explicitly rejected in Network B.
+
+#### **Expected message sequence**
+
+
+
+| | Network A | | Network B | |
+|-------------------|-----------|---|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | IAM | → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), UUInd.: UUS1 request – non-essential (10), UUI present |
+| | COT | → | | Optional message |
+| Case a | | ← | ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), UUInd.: UUS1 not provided (01) |
+| | | ← | ANM | |
+| Case b | | ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), UUInd.: UUS1 not provided (01) |
+| | | ← | CPG | Event Info: alerting (0000001) |
+| | | ← | ANM | |
+| Case c | | ← | CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), UUInd.: UUS1 not provided (01) |
+| ⇐ COMMUNICATION ⇒ | | | | |
+| | REL | → | | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | | ← | RLC | |
+
+#### **Test description (ISUP'92):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check that UUI is discarded in Network B.
+3. Check that the indication for UUS1 not provided is received at Network A's UNI.
+4. Verify that the call is completed after UUI is discarded.
+5. Check the propriety of digital data transmission or speech.
+6. Clear the call from Network A's UNI.
+7. Check that all resources are released.
+8. Repeat the test for speech and 3.1 kHz audio bearers.
+9. Repeat steps 1-8 with Networks A and B interchanged.
+
+**Test number:** 2.15.6 **Ref.:** 1.1.5.2.5.2.2/Q.737, 1.5.2.1.4.1/Q.957.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** User-to-User Signalling service 1 – Explicit request (essential) – Explicit rejection by the network
+
+**Purpose:** To verify that the UUS1 explicit network rejection can be correctly handled.
+
+**Pre-test conditions:**
+
+1. Arrange the stimulus such that the IAM generated contains a UUI parameter.
+2. Arrange exchange data such that the requested UUS1 is explicitly rejected in Network B.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-----------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), ISUP required all the way (10), UUInd.: UUS1 request – essential (11), UUI present |
+| COT | → | Optional message |
+| | ← | REL Cause Ind.: Facility rejected (29) or requested facility not implemented (69), location transit network (0011) or public network serving remote user (0100) or international network (0111), Diagnostic: UUInd name (00101010) |
+| RLC | → | |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify that the call is released.
+3. Check that all resources are released by Network B.
+4. Repeat the test for speech and 3.1 kHz audio bearers.
+5. Repeat steps 1-4 with Networks A and B interchanged.
+
+**Test number:** 2.15.7 **Ref.:** 1.1.5.2.5.2.2/Q.737, 1.5.2.1.4.2/Q.957.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** User-to-User Signalling service 1 – Explicit request (essential) – Explicit rejection by the called user
+
+**Purpose:** To verify that the UUS1 explicit rejection can be correctly handled.
+
+- Pre-test conditions:**
+1. Arrange the stimulus such that the IAM generated contains a UUS request.
+ 2. Only one terminal at Network B's UNI should react to the incoming SETUP.
+ 3. Arrange the stimulus such that the requested UUS1 is rejected by the terminal at Network B's UNI.
+
+#### Expected message sequence
+
+| Network A | | Network B |
+|---------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), ISUP required all the way (10), UUInd.: UUS1 request – essential (11) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | REL Cause Ind.: Requested facility not implemented (69), location user (0000) |
+| RLC | → | |
+| Case b | ← | REL Cause Ind.: Requested facility not implemented (69), location user (0000) |
+| RLC | → | |
+
+#### Test description (ISUP'92):
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify that the call is released by Network B's UNI.
+3. Check that all resources are released.
+4. Repeat the test for speech and 3.1 kHz audio bearers.
+5. Repeat steps 1-4 with Networks A and B interchanged.
+
+**Test number:** 2.16.1 **Ref.:** 1.2.5.2.1.1/Q.737, 1.5.2.2/Q.957.
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+**Title:** User-to-User Signalling service 2 – Successful – UUI in the forward and the backward direction
+**Purpose:** To verify that the UUInd and the UUI can be correctly transferred.
+**Pre-test conditions:**
+
+1. Arrange the stimulus such that the IAM message contains the UUI request.
+2. Arrange exchange data such that the requested UUS2 is supported in both networks.
+3. Arrange the stimulus such that the ACM/CPG generated contain an UUIndicator.
+
+#### **Expected message sequence**
+
+
+
+| Network A | | Network B | |
+|-------------------|---|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), ISUP required (10), Originating access ISDN (1), UUInd.: UUS2 request – not essential (10) or essential (11) – see Note |
+| COT | → | | Optional message |
+| Case a | ← | ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), UUInd.: UUS2 provided (10) |
+| USR | → | | UUI present |
+| | ← | USR | UUI present |
+| | ← | ANM | |
+| Case b | ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG | Event Info: alerting (0000001), UUInd.: UUS 2 provided (10) |
+| USR | → | | UUI present |
+| | ← | USR | UUI present |
+| | ← | ANM | |
+| ⇐ COMMUNICATION ⇑ | | | |
+| REL | → | | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC | |
+
+NOTE – FCI: ISUP required all the way (10) is set in case of an essential request.
+
+#### **Test description (ISUP'92):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify the UUI in the USR messages.
+3. Check the propriety of digital data transmission or speech.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 2.16.2 **Ref.:** 1.2.5.2.5.2.1/Q.737, 1.5.2.2/Q.957.
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+**Title:** User-to-User Signalling service 2 – Not essential – Implicit network rejection
+**Purpose:** To verify that the UUS2 implicit network rejection can be correctly handled.
+**Pre-test conditions:** 1. Arrange the stimulus such that the IAM generated contains a UUS2 request (not essential).
+ 2. Arrange exchange data such that the requested UUS2 is implicitly rejected by Network B.
+
+#### **Expected message sequence**
+
+
+
+| | Network A | Network B |
+|---------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), UUIInd.: UUS2 request – not essential (10) |
+| | COT → | Optional message |
+| Case a | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← ANM | |
+| Case b | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← CPG | Event Info: alerting (0000001) |
+| | ← ANM | |
+| Case c | ← CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+
+⇐ COMMUNICATION ⇒
+
+| | | |
+|--|-------|-------------------------------------------------------------|
+| | REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← RLC | |
+
+#### **Test description (ISUP'92):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify the UUS2 request in Network B.
+3. Verify that the call completes after UUS2 request is discarded.
+4. Check the propriety of digital data transmission or speech.
+5. Clear the call from Network A's UNI.
+6. Check that all resources are released.
+7. Repeat the test for speech and 3.1 kHz audio bearers.
+
+#### **Test description (Comb):**
+
+1. Make a 64 kbit/s call from Network A's (ISUP'92) UNI to Network B's (Q.767) UNI.
+2. Verify the UUS2 in Network B.
+3. Verify that the call completes after UUS2 request is discarded.
+4. Check the propriety of digital data transmission or speech.
+5. Clear the call from Network A's UNI.
+6. Check that all resources are released.
+7. Repeat the test for speech and 3.1 kHz audio bearers.
+
+**Test number:** 2.16.3 **Ref.:** 1.2.5.2.5.2.1/Q.737, 1.5.2.2/Q.957.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** User-to-User Signalling service 2 – Not essential – Explicit network rejection
+
+**Purpose:** To verify that the UUS2 explicit network rejection can be correctly handled.
+
+**Pre-test conditions:**
+
+1. Arrange the stimulus such that the IAM generated contains a UUS2 request.
+2. Arrange exchange data such that the requested UUS2 is explicitly rejected by Network B.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-------------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), UUInd.: UUS2 request – not essential (10) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), UUInd.: UUS2 not provided (01), Terminating access ISDN (1) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), UUInd.: UUS2 not provided (01), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| Case c | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001), UUInd.: UUS2 not provided (01) |
+| | ← | ANM |
+| | ← | UUInd |
+| ⇐ COMMUNICATION ⇒ | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify that the UUS2 is rejected in Network B.
+3. Verify that the call completes.
+4. Check the propriety of digital data transmission or speech.
+5. Clear the call from Network A's UNI.
+6. Check that all resources are released.
+7. Repeat the test for speech and 3.1 kHz audio bearers.
+8. Repeat steps 1-7 with Networks A and B interchanged.
+
+**Test number:** 2.16.4 **Ref.:** 1.2.5.2.5.2.1/Q.737, 1.5.2.2/Q.957.
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+**Title:** User-to-User Signalling service 2 – Essential – Explicit rejection
+**Purpose:** To verify that the UUS2 explicit network rejection can be correctly handled.
+**Pre-test conditions:** 1. Arrange the stimulus such that the IAM generated contains a UUS2 request.
+ 2. Arrange exchange data such that the requested UUS2 is rejected by Network B.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-----------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), ISUP required all the way (10), UUInd.: UUS2 request – essential (11) |
+| COT | → | Optional message |
+| | ← | REL Cause Ind.: Facility rejected (29) or requested facility not implemented (69), location transit network (0011) or public network serving remote user (0100) or international network (0111), Diagnostic: UUInd name (00101010) |
+| RLC | → | |
+
+#### **Test description (ISUP'92):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify that the call is released in Network B.
+3. Check that all resources are released.
+4. Repeat the test for speech and 3.1 kHz audio bearers.
+5. Repeat steps 1-4 with Networks A and B interchanged.
+
+**Test number:** 2.16.5 **Ref.:** 1.2.5.2.5.2.1/Q.737, 1.5.2.2/Q.957.
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+**Title:** User-to-User Signalling service 2 – Essential – Explicit rejection – multipoint
+**Purpose:** To verify that the UUS2 explicit network rejection can be correctly handled.
+**Pre-test conditions:** 1. Arrange the stimulus such that the IAM generated contains a UUS2 request.
+ 2. Arrange exchange data such that the requested UUS2 is rejected in Network B.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-----------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), ISUP required all the way (10), UUInd.: UUS2 request – essential (11) |
+| COT | → | Optional message |
+| | ← | REL Cause Ind.: incompatible destination (88), location public network serving remote user (0100), Diagnostic: UUInd name (00101010) |
+| RLC | → | |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify that the call is released in Network B.
+3. Check that all resources are released.
+4. Repeat the test for speech and 3.1 kHz audio bearers.
+5. Repeat steps 1-4 with Networks A and B interchanged.
+
+**Test number:** 2.17.1 **Ref.:** 1.3.5.2.1.1/Q.737, 1.5.2.3/Q.957.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** User-to-User Signalling service 3 – Successful – UUI in both directions, request during call establishment
+
+**Purpose:** To verify that UUI can be correctly transferred in both directions.
+
+**Pre-test conditions:**
+
+1. Arrange the stimulus such that the IAM contains the UUS3 request.
+2. Arrange exchange data such that the requested UUS3 is supported in both networks.
+
+#### Expected message sequence
+
+| Network A | | Network B |
+|-------------------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), UUInd.: UUS3 request – not essential (10) or essential (11) – see Note |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM UUInd.: UUS3 provided (10) |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM UUInd.: UUS3 provided (10) |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), UUInd.: UUS3 provided (10) |
+| USR | → | UUI present |
+| | ← | USR UUI present |
+| ⇐ COMMUNICATION ⇑ | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+NOTE – FCI: ISUP required all the way (10) is set in case of an essential request.
+
+#### Test description (ISUP'92):
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check the propriety of digital data transmission or speech.
+3. Verify the UUI in the USR messages.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 2.17.2 **Ref.:** 1.3.5.2.5.2.1/Q.737, 1.5.2.3/Q.957.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** User-to-User Signalling service 3 – Not essential – Implicit network rejection, request during call establishment
+
+**Purpose:** To verify that the UUS3 implicit network rejection can be correctly handled.
+
+- Pre-test conditions:**
+1. Arrange the stimulus such that the IAM generated contains a UUS3 request.
+ 2. Arrange exchange data such that the requested UUS3 is only supported in Network A.
+ 3. Arrange exchange data such that the requested UUS3 is implicitly rejected by Network B.
+
+#### Expected message sequence
+
+| Network A | Network B |
+|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), UUIInd.: UUS3 request – not essential (10) |
+| COT → | Optional message |
+| Case a ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← ANM | |
+| Case b ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← CPG | Event Info: alerting (0000001) |
+| ← ANM | |
+| Case c ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ⇐ COMMUNICATION ⇒ | |
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | |
+
+#### Test description (ISUP'92):
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify that the UUS3 is rejected in Network B.
+3. Verify that the call completes after UUS3 request is ignored.
+4. Check the propriety of digital data transmission or speech.
+5. Clear the call from Network A's UNI.
+6. Check that all resources are released.
+7. Repeat the test for speech and 3.1 kHz audio bearers.
+
+#### **Test description (Comb):**
+
+1. Make a 64 kbit/s call from Network A's (ISUP'92) UNI to Network B's (Q.767) UNI.
+2. Verify that the UUS3 is rejected in Network B.
+3. Verify that the call completes after UUS3 request is ignored.
+4. Check the propriety of digital data transmission or speech.
+5. Clear the call from Network A's UNI.
+6. Check that all resources are released.
+7. Repeat the test for speech and 3.1 kHz audio bearers.
+
+**Test number:** 2.17.3 **Ref.:** 1.3.5.2.5.2.1/Q.737, 1.5.2.3/Q.957.
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+**Title:** User-to-User Signalling service 3 – Not essential – Explicit rejection, request during call establishment
+**Purpose:** To verify that the UUS3 explicit network rejection can be correctly handled.
+**Pre-test conditions:** 1. Arrange the stimulus such that the IAM generated contains a UUI parameter.
+ 2. Arrange exchange data such that the requested UUS3 is explicitly rejected in Network B.
+
+#### **Expected message sequence**
+
+
+
+| | Network A | Network B |
+|---------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), UUInd.: UUS3 request – not essential (10) |
+| | COT → | Optional message |
+| Case a | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← ANM | UUInd.: UUS3 not provided (01) |
+| Case b | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← CPG | Event Info: alerting (0000001) |
+| | ← ANM | UUInd.: UUS3 not provided (01) |
+| Case c | ← CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), UUInd.: UUS3 not provided (01) |
+
+⇐ COMMUNICATION ⇒
+
+| | | |
+|--|-------|-------------------------------------------------------------|
+| | REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← RLC | |
+
+#### **Test description (ISUP'92):**
+
+- Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+- Verify that the UUS3 is rejected in Network B.
+- Verify that the call completes after UUS3 request is rejected.
+- Check the propriety of digital data transmission or speech.
+- Clear the call from Network A's UNI.
+- Check that all resources are released.
+- Repeat the test for speech and 3.1 kHz audio bearers.
+- Repeat steps 1-7 with Networks A and B interchanged.
+
+**Test number:** 2.17.4 **Ref.:** 1.3.5.2.5.2.1/Q.737, 1.5.2.3/Q.957.
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+**Title:** User-to-User Signalling service 3 – Essential – Explicit network rejection, request during call establishment
+**Purpose:** To verify that the UUI can be correctly rejected and that the call is released.
+**Pre-test conditions:**
+
+1. Arrange the stimulus such that the IAM generated contains a UUS request.
+2. Arrange exchange data such that the requested UUS is explicitly rejected in Network B.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-----------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), ISUP required all the way (10), UUInd.: UUS3 request – essential (11) |
+| COT | → | Optional message |
+| | ← | REL Cause Ind.: Facility rejected (29) or requested facility not implemented (69), location transit network (0011) or public network serving remote user (0100) or international network (0111), Diagnostic: UUInd name (00101010) |
+| RLC | → | |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Verify the UUS3 request in the IAM message.
+3. Check that the call is released in Network B.
+4. Check that all resources are released.
+5. Repeat the test for speech and 3.1 kHz audio bearers.
+6. Repeat steps 1-5 with Networks A and B interchanged.
+
+**Test number:** 2.17.5 **Ref.:** 1.3.5.2.1.1.2/Q.737, 1.5.2.3/Q.957.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** User-to-User Signalling service 3 – Successful – UUI in both directions – Request during call
+
+**Purpose:** To verify that information can be correctly transferred in both directions.
+
+- Pre-test conditions:**
+1. Arrange the stimulus such that the FAR message contains the UUS3 request.
+ 2. Arrange exchange data such that the requested UUS3 is supported.
+ 3. Arrange the stimulus such that the FAA message generated contains a UUInd parameter.
+ 4. Arrange the stimulus such that the USR messages contain UUI parameters.
+
+#### **Expected message sequence**
+
+
+
+| Network A | | Network B |
+|---------------|---|-----------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+
+⇒ COMMUNICATION ⇐
+
+| | | |
+|-----|---|-----------------------------------------------------------------------------------------------|
+| FAR | → | Facility indicator: user-to-user service (0000010), UUInd.: UUS3 request – not essential (10) |
+| | ← | FAA Facility indicator: user-to-user service (0000010), UUInd.: UUS3 provided (10) |
+| USR | → | UUI present |
+| | ← | USR UUI present |
+
+⇒ COMMUNICATION ⇐
+
+| | | |
+|-----|---|-------------------------------------------------------------|
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check the propriety of digital data transmission or speech.
+3. Verify the UUInd and the Facility Indicator in the FACILITY REQUEST and FACILITY ACCEPTED messages.
+4. Verify the UUI in the USR messages.
+5. Clear the call from Network A's UNI.
+6. Check that all resources are released.
+7. Repeat the test for speech and 3.1 kHz audio bearers.
+8. Repeat steps 1-7 with Networks A and B interchanged
+
+**Test number:** 2.17.6 **Ref.:** 1.3.5.2.5.2.2/Q.737, 1.5.2.3/Q.957.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** User-to-User Signalling service 3 – Implicit rejection – Request during call
+
+**Purpose:** To verify that UUS3 can be correctly rejected and that the call is still established.
+
+- Pre-test conditions:**
+1. Arrange the stimulus such that the FAR message contains the UUS3 request.
+ 2. Arrange exchange data such that the requested UUS3 is only supported in Network A and that UUS3 is explicitly rejected in Network B.
+
+#### Expected message sequence
+
+
+
+| | Network A | Network B |
+|-------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------|
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| | COT → | Optional message |
+| Case a | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← ANM | |
+| Case b | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← CPG | Event Info: alerting (0000001) |
+| | ← ANM | |
+| Case c | ← CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| ← COMMUNICATION → | | |
+| | FAR → | Facility indicator: user-to-user service (0000010), UUInd.: UUS3 request – not essential (10) |
+| ← COMMUNICATION → | | |
+| | REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← RLC | |
+
+#### Test description (ISUP'92):
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check the propriety of digital data transmission or speech.
+3. Verify the UUInd and the Facility Indicator in the FACILITY REJECTED messages.
+4. Verify the UUS3 request in the FACILITY REQUEST message.
+5. Clear the call from Network A's UNI.
+6. Check that all resources are released.
+7. Repeat the test for speech and 3.1 kHz audio bearers.
+
+#### **Test description (Comb):**
+
+1. Make a 64 kbit/s call from Network A's (ISUP'92) UNI to Network B's (Q.767) UNI.
+2. Check the propriety of digital data transmission or speech.
+3. Verify the UUS3 request in the FACILITY REQUEST message.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+
+**Test number:** 2.17.7 **Ref.:** 1.3.5.2.5.2.2/Q.737, 1.5.2.3/Q.957.
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+**Title:** User-to-User Signalling service 3 – Explicit rejection – Request during call
+**Purpose:** To verify that UUS3 can be correctly rejected and that the call is still established.
+**Pre-test conditions:**
+
+1. Arrange the stimulus such that the FAR message contains the UUS3 request.
+2. Arrange exchange data such that the requested UUS3 is explicitly rejected in Network B.
+
+#### **Expected message sequence**
+
+
+
+| | Network A | Network B |
+|---------------|-----------|-------------------------------------------------------------------------------------------------------------------------------|
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| | COT → | Optional message |
+| Case a | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← ANM | |
+| Case b | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← CPG | Event Info: alerting (0000001) |
+| | ← ANM | |
+| Case c | ← CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+
+⇐ COMMUNICATION ⇒
+
+| | | |
+|--|-------|-----------------------------------------------------------------------------------------------|
+| | FAR → | Facility indicator: user-to-user service (0000010), UUInd.: UUS3 request – non essential (10) |
+| | ← FRJ | Facility indicator: user-to-user service (0000010), UUInd.: UUS3 not provided (01) |
+
+⇐ COMMUNICATION ⇒
+
+| | | |
+|--|-------|-------------------------------------------------------------|
+| | REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← RLC | |
+
+#### **Test description (ISUP'92):**
+
+1. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+2. Check the propriety of digital data transmission or speech.
+3. Verify the UUInd and the Facility indicator in the FACILITY REQUEST and FACILITY REJECT messages.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 2.18.1 **Ref.:** 3.5.2.2.1/Q.735, 3/Q.955.
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+**Title:** MLPP – Invocation with no circuit congestion to MLPP subscriber
+**Purpose:** To verify that the parameters for an MLPP call can be correctly transferred.
+**Pre-test conditions:**
+
+1. Arrange the stimulus such that the IAM message contains the MLPP parameter.
+2. Both networks must offer MLPP.
+3. Arrange exchange data such that the called party belongs to the same MLPP service domain.
+
+#### **Expected message sequence**
+
+
+
+| | Network A | Network B |
+|---------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), MLPP: LFB Not Allowed (10), Precedence Level, Service Domain present |
+| | COT → | Optional message |
+| Case a | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: MLPP User (1) |
+| | ← ANM | |
+| Case b | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: MLPP User (1) |
+| | ← CPG | Event Info: alerting (0000001) |
+| | ← ANM | |
+| Case c | ← CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: MLPP User (1) |
+
+⇐ COMMUNICATION ⇒
+
+| | |
+|-------|-------------------------------------------------------------|
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | |
+
+#### **Test description (ISUP'92):**
+
+1. Make a 64 kbit/s MLPP call from Network A's UNI to Network B's UNI.
+2. Verify the MLPP indication in the SETUP and IAM messages.
+3. Verify the MLPP indication in the CONNECT and ACM/CON messages.
+4. Check the propriety of digital data transmission or speech.
+5. Clear the call from Network A's UNI.
+6. Check that all resources are released.
+7. Repeat the test for speech and 3.1 kHz audio bearers.
+8. Repeat steps 1-7 with Networks A and B interchanged.
+
+**Test number:** 2.18.2 **Ref.:** 3.5.2.2.1/Q.735, 3/Q.955.
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+**Title:** MLPP – Invocation with no circuit congestion to non-MLPP subscriber
+**Purpose:** To verify that the parameters for an MLPP call can be correctly transferred.
+**Pre-test conditions:** 1. Arrange the stimulus such that the IAM message contains the MLPP parameter.
+ 2. Arrange exchange data such that the called party is a non-MLPP subscriber.
+
+#### **Expected message sequence**
+
+
+
+| Network A | | Network B |
+|---------------|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), MLPP: LFB Not Allowed (10), Precedence Level, Service Domain present |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI if present : No indication (D = 0) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI if present : No indication (D = 0) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI if present : No indication (D = 0) |
+
+⇐ COMMUNICATION ⇒
+
+| | | |
+|-----|---|-------------------------------------------------------------|
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92):**
+
+- Make a 64 kbit/s MLPP call from Network A's UNI to Network B's UNI.
+- Verify the MLPP indication in the SETUP and IAM messages.
+- Verify the MLPP indication in the CONNECT and ACM/CON messages if present.
+- Check the propriety of digital data transmission or speech.
+- Clear the call from Network A's UNI.
+- Check that all resources are released.
+- Repeat the test for speech and 3.1 kHz audio bearers.
+- Repeat steps 1-7 with Networks A and B interchanged.
+
+#### **Test description (Comb):**
+
+1. Make a 64 kbit/s MLPP call from Network A's (ISUP'92) UNI to Network B's (Q.767) UNI.
+2. Verify the MLPP indication in the SETUP and IAM messages.
+3. Check the propriety of digital data transmission or speech.
+4. Clear the call from Network A's UNI.
+5. Check that all resources are released.
+6. Repeat the test for speech and 3.1 kHz audio bearers.
+
+- Test number:** 2.18.3 **Ref.:** 3.5.2.2.3.1/Q.735, 3/Q.955.
+- Config.:** ISDN Access → ISDN Access (See Figure 2)
+- Title:** MLPP – Invocation when congestion encountered, release of circuit reserved for re-use
+- Purpose:** To verify that the busy circuit is preempted and reserved for re-use.
+- Pre-test conditions:**
+1. Arrange the stimulus such that the IAM message contains the MLPP parameter.
+ 2. Arrange that circuit congestion is encountered in Network A after the first MLPP call is established.
+ 3. Arrange that precedence level of the second MLPP call is higher than precedence level of the first MLPP call and both belong to the same service domain.
+ 4. Arrange exchange data such that the released circuit will be used to complete the second (preempting) call.
+
+#### **Expected message sequence**
+
+
+
+| Network A | | Network B |
+|---------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), MLPP: LFB Not Allowed (10), Precedence Level, Service Domain present |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: MLPP user (1) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: MLPP user (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| Case c | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: MLPP user (1) |
+
+⇐ COMMUNICATION ⇒
+
+| | | |
+|---------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| REL | → | Cause Ind.: Preemption – circuit reserved for re-use (9), location public network serving remote user (0100) |
+| | ← | RLC |
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), MLPP: LFB Not Allowed (10), Precedence Level, Service Domain present |
+| COT | → | Optional message |
+| Case A | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: MLPP user (1) |
+| | ← | ANM |
+
+
+
+| | Network A | Network B |
+|---------------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Case B | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: MLPP user (1) |
+| | ← | CPG Event Info: alerting (0000001) |
+| | ← | ANM |
+| Case C | ← | CON BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: MLPP user (1) |
+
+⇐ COMMUNICATION ⇒
+
+| | | |
+|-----|---|-------------------------------------------------------------|
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← | | RLC |
+
+#### **Test description (ISUP'92):**
+
+1. Make a 64 kbit/s MLPP call from Network A to Network B.
+2. Make a second 64 kbit/s MLPP call from Network A's UNI to Network B's UNI.
+3. Verify that the first call is preempted and that the released circuit is reserved for re-use.
+4. Verify the MLPP indication in the SETUP and IAM messages.
+5. Verify the MLPP indication in the CONNECT and ACM/CON messages.
+6. Check the propriety of digital data transmission or speech.
+7. Clear the call from Network A's UNI.
+8. Check that all resources are released.
+9. Repeat the test for speech and 3.1 kHz audio bearers.
+10. Repeat steps 1-9 with Networks A and B interchanged.
+
+**Test number:** 2.18.4 **Ref.:** 3.5.2.2.3.1/Q.735, 3/Q.955.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** MLPP – Invocation when congestion encountered, release of circuit not reserved for re-use
+
+**Purpose:** To verify that the busy circuit is preempted and can be used for an ordinary call (or a MLPP call).
+
+- Pre-test conditions:**
+1. Arrange the stimulus such that the IAM message contains the MLPP parameter.
+ 2. Arrange that circuit congestion is encountered in Network B after the first MLPP call is established
+ 3. Arrange that precedence level of the second MLPP call is higher than precedence level of the first MLPP call and both belong to the same service domain.
+ 4. Arrange exchange data such that the circuit not reserved for re-use will be used to complete the ordinary call.
+
+#### **Expected message sequence**
+
+| | Network A | Network B | Network C | |
+|-------------------|-----------|-----------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | IAM → | IAM → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), MLPP: LFB Not Allowed (10), Precedence Level, Service Domain present |
+| | COT → | COT → | | Optional message |
+| Case a | ← | ACM ← | ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: MLPP user (1) |
+| | ← | ANM ← | ANM | |
+| Case b | ← | ACM ← | ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: MLPP user (1) |
+| | ← | CPG ← | CPG | Event Info: alerting (0000001) |
+| | ← | ANM ← | ANM | |
+| Case c | ← | CON ← | CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: MLPP user (1) |
+| ⇐ COMMUNICATION ⇒ | | | | |
+| | | REL → | | Cause Ind.: Preemption – circuit reserved for re-use (9), location public network serving remote user (0100) |
+| | | ← RLC | | |
+| | ← | REL | | Cause Ind.: Preemption (8), location public network serving remote user (0100) |
+| | RLC → | | | |
+
+| Network A | Network B | Network C |
+|---------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | IAM → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), MLPP: LFB Not Allowed (10), Precedence Level, Service Domain present |
+| | COT → | Optional message |
+| Case A | ← ACM | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: MLPP user (1) |
+| | ← ANM | |
+| Case B | ← ACM | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: MLPP user (1) |
+| | ← CPG | Event Info: alerting (0000001) |
+| | ← ANM | |
+| Case C | ← CON | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), OBCI: MLPP user (1) |
+
+⇐ COMMUNICATION ⇒
+
+| | |
+|-----------|-------------------------------|
+| IAM → | Simplified call establishment |
+| ← ACM | |
+| ← ANM | |
+
+⇐ COMMUNICATION ⇒
+
+| | |
+|-----------|-------------------------------------------------------------|
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | |
+| REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| ← RLC | |
+
+#### Test description (ISUP'92):
+
+1. Make a 64 kbit/s MLPP call from Network A to Network C via Network B.
+2. Make a second 64 kbit/s MLPP call from Network B to Network C.
+3. Verify that the circuit between Network A and Network B is preempted and not reserved for re-use.
+4. Make a 64 kbit/s call from Network A's UNI to Network B's UNI.
+5. Check the propriety of digital data transmission or speech for the call between Network A's UNI and Network B's UNI.
+6. Clear the ordinary call from Network A's UNI.
+7. Clear the MLPP call from Network B's UNI.
+8. Check that all resources are released.
+9. Repeat the test for speech and 3.1 kHz audio bearers.
+10. Repeat steps 1-9 with Networks A and B interchanged.
+
+**Test number:** 2.18.5 **Ref.:** 3.5.2.2.5.2/Q.735, 3/Q.955.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** MLPP – Invocation when congestion encountered, unsuccessful search for preemptable circuits
+
+**Purpose:** To verify that the MLPP call attempt can be rejected correctly in case of no available preemptable circuit.
+
+- Pre-test conditions:**
+1. Arrange the stimulus such that the IAM message contains the MLPP parameter.
+ 2. Arrange that circuit congestion is encountered in Network B.
+ 3. Arrange exchange data such that there is no preemptable circuit available of the requested bearer capability in Network B.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-----------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), MLPP: LFB Not Allowed (10), Precedence Level, Service Domain present |
+| COT | → | Optional message |
+| | ← | REL Cause Ind.: Precedence call blocked (46), location transit network (0011) or public network serving remote user (0100) or private network serving remote user (0101) or international network (0111) |
+| RLC | → | |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s MLPP call from Network A's UNI to Network B's UNI.
+2. Verify the MLPP indication in the SETUP and IAM messages.
+3. Check that the call is released from Network B.
+4. Check that all resources are released.
+5. Repeat the test for speech and 3.1 kHz audio bearers.
+6. Repeat steps 1-5 with Networks A and B interchanged.
+
+**Test number:** 2.18.6 **Ref.:** 3.5.2.2.2/Q.735, 3/Q.955.
+
+**Config.:** ISDN Access → ISDN Access (See Figure 2)
+
+**Title:** MLPP – Invocation when congestion encountered, precedence level too low to preempt
+
+**Purpose:** To verify that the MLPP call attempt can be correctly rejected if the precedence level is too low to preempt.
+
+**Pre-test conditions:**
+
+1. Arrange the stimulus such that the IAM message contains the MLPP parameter.
+2. Arrange that circuit congestion is encountered in Network B.
+3. Arrange exchange data such that all preemptable circuits in the MLPP service domain have a higher or the same precedence level than the new call.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-----------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | ➔ | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1), MLPP: LFB Not Allowed (10), Precedence Level, Service Domain present |
+| COT | ➔ | Optional message |
+| | ⬅ | REL Cause Ind.: Precedence call blocked (46), location public network serving remote user (0100) or private network serving remote user (0101) |
+| RLC | ➔ | |
+
+#### **Test description (ISUP'92):**
+
+1. Initiate a 64 kbit/s MLPP call from Network A's UNI to Network B's UNI.
+2. Verify the MLPP indication in the SETUP and IAM messages.
+3. Check that the call is released from Network B.
+4. Check that all resources are released.
+5. Repeat the test for speech and 3.1 kHz audio bearers.
+6. Repeat steps 1-5 with Networks A and B interchanged.
+
+**Test number:** 3.1.1.1 **Ref.:** 2.1.1.1/Q.764, 5.1.6/Q.931, 3.3.2/Q.699.
+
+**Config:** ISDN Access → Undetermined Access (See Figure 6)
+
+**Title:** Normal call release – Calling party clears before answer
+
+**Purpose:** To verify that the calling party can successfully release a call prior to receipt of an answer.
+
+#### **Pre-test conditions:**
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|---------------|---|---------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking encountered (1), ISDN User Part not used all the way (0), Terminating access non-ISDN (0) |
+| Case b | ← | ACM BCI: No indication (00), Interworking encountered (1), ISDN User Part not used all the way (0), Terminating access non-ISDN (0) |
+| | ← | CPG Optional message Event Info: alerting (0000001) |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a speech call from Network A's UNI to Network B's UNI.
+2. Clear the call from Network A's UNI.
+3. Check that all resources are released.
+4. Repeat the test for 3.1 kHz audio bearer.
+5. Repeat steps 1-4 with Networks A and B interchanged.
+
+**Test number:** 3.1.1.2 **Ref.:** 2.1.1.1/Q.764, 5.1.6/Q.931, 4.3.2/Q.699.
+
+**Config.:** ISDN Access → Undetermined Access (See Figure 6)
+
+**Title:** Normal call release – Calling party clears after answer
+
+**Purpose:** To verify that the calling party can successfully release a call after receipt of answer.
+
+#### **Pre-test conditions:**
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-------------------|---|---------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking encountered (1), ISDN User Part not used all the way (0), Terminating access non-ISDN (0) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking encountered (1), ISDN User Part not used all the way (0), Terminating access non-ISDN (0) |
+| | ← | CPG Optional message Event Info: alerting (0000001) |
+| | ← | ANM |
+| ⇐ COMMUNICATION ⇒ | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a speech call from Network A's UNI to Network B's UNI.
+2. Check the propriety of speech.
+3. Clear the call from Network A's UNI.
+4. Check that all resources are released.
+5. Repeat the test for 3.1 kHz audio bearer.
+6. Repeat steps 1-5 with Networks A and B interchanged.
+
+**Test number:** 3.1.1.3 **Ref.:** 2.4.1/Q.764, 5.1.6/Q.931, 4.3.2/Q.699.
+
+**Config.:** ISDN Access → Undetermined Access (See Figure 6)
+
+**Title:** Normal call release – Called party suspends after answer
+
+**Purpose:** To verify that the calling party can successfully clear a call after the called party suspended the call.
+
+#### **Pre-test conditions:**
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-------------------|---|--------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01) Interworking encountered (1), ISDN User Part not used all the way (0), Terminating access non-ISDN (0) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking encountered (1), ISDN User Part not used all the way (0), Terminating access non-ISDN (0) |
+| | ← | CPG Optional message Event Info: alerting (0000001) |
+| | ← | ANM |
+| ⇐ COMMUNICATION ⇒ | | |
+| | ← | SUS network initiated (1) |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a speech call from Network A's UNI to Network B's UNI.
+2. Check the propriety of speech.
+3. Suspend the call from Network B's UNI.
+4. Clear the call from Network A's UNI after receiving the suspend indication from Network B's UNI.
+5. Check that all resources are released.
+6. Repeat the test for 3.1 kHz audio bearer.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 3.1.1.4 **Ref.:** 2.4.3/Q.764, 5.1.6/Q.931, 4.3.2/Q.699.
+
+**Config.:** ISDN Access → Undetermined Access (See Figure 6)
+
+**Title:** Normal call release – Called party suspends after answer, expiry of T6
+
+**Purpose:** To verify that timer T6 in Network A works correctly.
+
+**Pre-test conditions:**
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-------------------|---|---------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking encountered (1), ISDN User Part not used all the way (0), Terminating access non-ISDN (0) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking encountered (1), ISDN User Part not used all the way (0), Terminating access non-ISDN (0) |
+| | ← | CPG Optional message Event ind.: alert (0000001) |
+| | ← | ANM |
+| ⇐ COMMUNICATION ⇒ | | |
+| | ← | SUS network initiated (1) |
+| REL | → | Cause Ind.: Recovery on timer expiry (102), location public network serving the remote user (0100) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a speech call from Network A's UNI to Network B's UNI.
+2. Check the propriety of speech.
+3. Suspend the call from Network B's UNI.
+4. Check that the call is released from Network A after expiry of T6.
+5. Check that all resources are released.
+6. Repeat the test for 3.1 kHz audio bearer.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 3.1.1.5 **Ref.:** 2.4.3/Q.764, 5.1.6/Q.931, 4.3.2/Q.699.
+
+**Config.:** ISDN Access → Undetermined Access (See Figure 6)
+
+**Title:** Normal call release – Called party suspends after answer, expiry of T38
+
+**Purpose:** To verify that timer T38 in Network B works correctly.
+
+**Pre-test conditions:** Arrange in Network A such that T6 does not expire before T38 in Network B expires.
+
+#### Expected message sequence
+
+| Network A | | Network B |
+|-------------------|---|---------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking encountered (1), ISDN User Part not used all the way (0), Terminating access non-ISDN (0) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking encountered (1), ISDN User Part not used all the way (0), Terminating access non-ISDN (0) |
+| | ← | CPG Optional message Event ind.: alert (0000001) |
+| | ← | ANM |
+| ⇐ COMMUNICATION ⇒ | | |
+| | ← | SUS network initiated (1) |
+| | ← | REL Cause Ind.: Recovery on timer expiry (102), location international network (0111) |
+| RLC | → | |
+
+#### Test description (ISUP'92, Comb):
+
+1. Make a speech call from Network A's UNI to Network B's UNI.
+2. Check the propriety of speech.
+3. Suspend the call from Network B's UNI.
+4. Check that the call is released from Network B after expiry of T38.
+5. Check that all resources are released.
+6. Repeat the test for 3.1 kHz audio bearer.
+7. Repeat steps 1-6 with Networks A and B interchanged.
+
+**Test number:** 3.1.2.1 **Ref.:** 2.2/Q.764, 5.3.4.1/Q.931.
+
+**Config.:** ISDN Access → Undetermined Access (See Figure 6)
+
+**Title:** Unsuccessful call set-up – All circuits busy at destination network
+
+**Purpose:** To verify that the call will be successfully released when all circuits are busy.
+
+**Pre-test conditions:** All circuits are busy at Network B.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|---------------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← REL | Cause Ind.: No circuits available (34), location transit network (0011) or beyond interworking point (1010) or public network serving remote user (0100) or international network (0111) |
+| RLC | → | |
+| Case b | ← ACM | BCI: No indication (00), Interworking encountered (1), ISDN User Part not used all the way (0), Terminating access non-ISDN (0) |
+| | ← REL | Cause Ind.: No circuits available (34), location transit network (0011) or beyond interworking point (1010) or public network serving remote user (0100) or international network (0111) |
+| RLC | → | |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a speech call from Network A's UNI to Network B's UNI.
+2. Check that all resources are released.
+3. Repeat the test for 3.1 kHz audio bearer.
+4. Repeat steps 1-3 with Networks A and B interchanged.
+
+**Test number:** 3.1.2.2 **Ref.:** 2.2/Q.764, 5.3.4.1/Q.931.
+
+**Config.:** ISDN Access → Undetermined Access (See Figure 6)
+
+**Title:** Unsuccessful call set-up – Dialing of an unallocated number
+
+**Purpose:** To verify that a call will be successfully released when dialing an unallocated number.
+
+**Pre-test conditions:** Unallocated national destination code or subscriber number in Network B.
+
+#### **Expected message sequence**
+
+| Network A | | Network B | |
+|---------------|---|---------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) | |
+| COT | → | Optional message | |
+| Case a | ← | REL | Cause Ind.: Unallocated number (1), location beyond an interworking point (1010) public network serving remote user (0100) |
+| RLC | → | | |
+| Case b | ← | ACM | BCI: No indication (00), Interworking encountered (1), ISDN User Part not used all the way (0), Terminating access non-ISDN (0) |
+| | ← | REL | Cause Ind.: Unallocated number (1), location beyond an interworking point (1010) public network serving remote user (0100) |
+| RLC | → | | |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a speech call from Network A's UNI to Network B's UNI.
+2. Check that all resources are released.
+3. Repeat the test for 3.1 kHz audio bearer.
+4. Repeat steps 1-3 with Networks A and B interchanged.
+
+**Test number:** 3.1.2.3 **Ref.:** 2.2/Q.764, 5.3.4.1/Q.931.
+
+**Config.:** ISDN Access → Undetermined Access (See Figure 6)
+
+**Title:** Unsuccessful call set-up – Calling to a busy subscriber
+
+**Purpose:** To verify that the call can be successfully released when dialing a busy termination.
+
+**Pre-test conditions:** The called termination is busy, the interworking point is able to generate REL user busy.
+
+#### **Expected message sequence**
+
+Network A Network B
+
+| | | | | |
+|---------------|-----|---|-----|---------------------------------------------------------------------------------------------------------------------------------|
+| | IAM | → | | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| | COT | → | | Optional message |
+| Case a | | ← | REL | Cause Ind.: user busy (17), location beyond interworking point (1010) |
+| | RLC | → | | |
+| Case b | | ← | ACM | BCI: No indication (00), Interworking encountered (1), ISDN User Part not used all the way (0), Terminating access non-ISDN (0) |
+| | | ← | REL | Cause Ind.: user busy (17), location beyond interworking point (1010) |
+| | RLC | → | | |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a speech call from Network A's UNI to Network B's UNI.
+2. Check that all resources are released.
+3. Repeat the test for 3.1 kHz audio bearer.
+4. Repeat steps 1-3 with Networks A and B interchanged.
+
+**Test number:** 3.1.3.1 **Ref.:** 2.1.4/Q.764, 5.3.4.1/Q.931.
+
+**Config.:** ISDN Access → Undetermined Access (See Figure 6)
+
+**Title:** Abnormal situation during a call – No answer from user – user alerted
+
+**Purpose:** To verify that the call can be successfully released when T9/Q.764 wait for answer timer expires.
+
+**Pre-test conditions:** The called party doesn't answer.
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|---------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking encountered (1), ISDN User Part not used all the way (0), Terminating access non-ISDN (0) |
+| Case b | ← | ACM BCI: No indication (00), Interworking encountered (1), ISDN User Part not used all the way (0), Terminating access non-ISDN (0) |
+| | ← | CPG Optional message Event Info: alerting (00000001) |
+| REL | → | Cause Ind.: No answer from user (user alerted) (19), location transit network (0011) or public network serving remote user (0100) or international network (0111) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a speech call from Network A's UNI to Network B's UNI.
+2. Check that all resources are released.
+3. Repeat the test for 3.1 kHz audio bearer.
+4. Repeat steps 1-3 with Networks A and B interchanged.
+
+**Test number:** 3.2.1.1 **Ref.:** 2.3.1/Q.764, 5.2.6/Q.931, 4.3.1/Q.699.
+
+**Config:** Undetermined Access → ISDN Access (See Figure 6)
+
+**Title:** Normal call release – Calling party clears before answer
+
+**Purpose:** To verify that the calling party can successfully release a call prior to receipt of an answer.
+
+#### **Pre-test conditions:**
+
+#### **Expected message sequence**
+
+| Network A | | Network B | |
+|---------------|-------|-----------------------------------------------------------------------------------------------------------------------------------|--|
+| | ← | IAM FCI: Interworking encountered (1), ISDN User Part not used all the way (0), Originating access non-ISDN (0) – see Note | |
+| | ← | COT Optional message | |
+| Case a | ACM → | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) | |
+| Case b | ACM → | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) | |
+| | CPG → | Event Info: alerting (0000001) | |
+| | ← | REL Cause Ind.: Normal call clearing (16), location public network serving remote user (0100) or beyond interworking point (1010) | |
+| | RLC → | | |
+
+NOTE – In case of calls to a non-ISUP Signalling System No. 7 system, the interworking indicator is coded interworking not encountered (0).
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a call from Network B's UNI to Network A's UNI.
+2. Clear the call from Network B's UNI.
+3. Check that all resources are released.
+4. Repeat the test for 3.1 kHz audio bearer.
+5. Repeat steps 1-4 with Networks A and B interchanged.
+
+**Test number:** 3.2.1.2 **Ref.:** 2.3.1/Q.764, 5.2.6/Q.931, 4.3.1/Q.699.
+
+**Config.:** Undetermined Access → ISDN Access (See Figure 6)
+
+**Title:** Normal call release – Calling party clears after answer
+
+**Purpose:** To verify that the calling party can successfully release a call after receipt of answer.
+
+#### **Pre-test conditions:**
+
+#### **Expected message sequence**
+
+| | Network A | Network B |
+|-------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | ← | IAM FCI: Interworking encountered (1), ISDN User Part not used all the way (0), Originating access non-ISDN (0) – see Note |
+| | ← | COT Optional message |
+| Case a | ACM → | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ANM → | |
+| Case b | ACM → | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | CPG → | Event Info: alerting (0000001) |
+| | ANM → | |
+| ⇐ COMMUNICATION ⇒ | | |
+| | ← | REL Cause Ind.: Normal call clearing (16), location user (0000) or public network serving remote user (0100) or private network serving remote user (0100) or beyond interworking point (1010) |
+| | RLC → | |
+
+NOTE – In case of calls to a non-ISUP Signalling System No. 7 system, the interworking indicator is coded interworking not encountered (0).
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a call from Network B's UNI to Network A's UNI.
+2. Check the propriety of speech.
+3. Clear the call from Network B's UNI.
+4. Check that all resources are released.
+5. Repeat steps 1-4 with Networks A and B interchanged.
+
+**Test number:** 3.2.1.3 **Ref.:** 2.3.1/Q.764, 5.2.6/Q.931, 4.3.1/Q.699.
+
+**Config.:** Undetermined Access → ISDN Access (See Figure 6)
+
+**Title:** Normal call release – Called party clears after answer
+
+**Purpose:** To verify that the called party can successfully release a call after receipt of answer.
+
+#### **Pre-test conditions:**
+
+#### **Expected message sequence**
+
+| | Network A | Network B |
+|-------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------|
+| | ← | IAM FCI: Interworking encountered (1), ISDN User Part not used all the way (0), Originating access non-ISDN (0) – see Note |
+| | ← | COT Optional message |
+| Case a | ACM → | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ANM → | |
+| Case b | ACM → | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | CPG → | Event Info: alerting (0000001) |
+| | ANM → | |
+| ⇐ COMMUNICATION ⇒ | | |
+| | REL → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+NOTE – In case of calls to a non-ISUP Signalling System No. 7 system, the interworking indicator is coded interworking not encountered (0).
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a call from Network B's UNI to Network A's UNI.
+2. Check the propriety of speech.
+3. Clear the call from Network A's UNI.
+4. Check that all resources are released.
+5. Repeat steps 1-4 with Networks A and B interchanged.
+
+**Test number:** 3.2.2.1 **Ref.:** 2.3.1/Q.764, 5.2.6/Q.931.
+
+**Config:** Undetermined Access → ISDN Access (See Figure 6)
+
+**Title:** Unsuccessful call set-up – All circuits busy at destination network
+
+**Purpose:** To verify that the call will be successfully released, if all circuits are busy.
+
+**Pre-test conditions:** All circuits are busy in international, national or access circuit groups.
+
+#### **Expected message sequence**
+
+| | Network A | | Network B |
+|---------------|-----------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | ← | IAM FCI: Interworking encountered (1), ISDN User Part not used all the way (0), Originating access non-ISDN (0) – see Note |
+| | | ← | COT Optional message |
+| Case a | REL | → | Cause Ind.: No circuit available (34), location public network serving remote user (0100) or private network serving remote user (0101) or transit network (0011) or international network (0111) |
+| | | ← | RLC |
+| Case b | ACM | → | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | REL | → | Cause Ind.: No circuit available (34), location public network serving remote user (0100) or private network serving remote user (0101) |
+| | | ← | RLC |
+
+NOTE – In case of calls to a non-ISUP Signalling System No. 7 system, the interworking indicator is coded interworking not encountered (0).
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a call from Network B's UNI to Network A's UNI.
+2. Check that all resources are released.
+3. Repeat steps 1-2 with Networks A and B interchanged.
+
+**Test number:** 3.2.2.2 **Ref.:** 2.3.1/Q.764, 5.2.6/Q.931.
+
+**Config:** Undetermined Access → ISDN Access (See Figure 6)
+
+**Title:** Unsuccessful call set-up – Dialling of an unallocated number
+
+**Purpose:** To verify that the call will be successfully released, when dialling an unallocated number.
+
+**Pre-test conditions:** Unallocated subscriber number in Network A.
+
+#### **Expected message sequence**
+
+| | Network A | Network B |
+|---------------|-----------|------------------------------------------------------------------------------------------------------------------------------|
+| | ← | IAM FCI: Interworking encountered (1), ISDN User Part not used all the way (0), Originating access non-ISDN (0) – see Note |
+| | ← | COT Optional message |
+| Case a | REL → | Cause Ind.: Unallocated number (1), location public network serving remote user (0100) |
+| | ← | RLC |
+| Case b | ACM → | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1), |
+| | REL → | Cause Ind.: Unallocated number (1), location public network serving remote user (0100) |
+| | ← | RLC |
+
+NOTE – In case of calls to a non-ISUP Signalling System No. 7 system, the interworking indicator is coded interworking not encountered (0).
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a call from Network B's UNI to Network A's UNI.
+2. Check that all resources are released.
+3. Repeat steps 1-2 with Networks A and B interchanged.
+
+**Test number:** 3.2.2.3 **Ref.:** 2.3.1/Q.764, 5.2.6/Q.931.
+
+**Config:** Undetermined Access → ISDN Access (See Figure 6)
+
+**Title:** Unsuccessful call set-up – No route to destination
+
+**Purpose:** To verify that the call will be successfully released when there is no route to destination.
+
+**Pre-test conditions:** Called party number has invalid country or national destination code.
+
+#### **Expected message sequence**
+
+| Network A | Network B |
+|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | ← IAM FCI: Interworking encountered (1), ISDN User Part not used all the way (0), Originating access non-ISDN (0) – see Note |
+| | ← COT Optional message |
+| REL → | Cause Ind.: No route to destination (3), location transit network (0011) or international network (0111) or private network serving remote user (0101) |
+| | ← RLC |
+
+NOTE – In case of calls to a non-ISUP Signalling System No. 7 system, the interworking indicator is coded interworking not encountered (0).
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a call from Network B's UNI to Network A's UNI.
+2. Check that all resources are released.
+3. Repeat steps 1-2 with Networks A and B interchanged.
+
+**Test number:** 3.2.2.4 **Ref.:** 2.3.1/Q.764, 5.2.6/Q.931.
+
+**Config:** Undetermined Access → ISDN Access (See Figure 6)
+
+**Title:** Unsuccessful call set-up – Calling to a busy subscriber
+
+**Purpose:** To verify that the call will be successfully released when dialling a busy termination.
+
+**Pre-test conditions:** The called termination is busy.
+
+#### **Expected message sequence**
+
+| | Network A | Network B |
+|---------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------|
+| | ← | IAM FCI: Interworking encountered (1), ISDN User Part not used all the way (0), Originating access non-ISDN (0) – see Note |
+| | ← | COT Optional message |
+| Case a | REL → | Cause Ind.: User busy (17), location user (0000) or public network serving remote user (0100) or private network serving remote user (0101) |
+| | ← | RLC |
+| Case b | ACM → | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | REL → | Cause Ind.: User busy (17), location user (0000) or public network serving remote user (0100) or private network serving remote user (0101) |
+| | ← | RLC |
+
+NOTE – In case of calls to a non-ISUP Signalling System No. 7 system, the interworking indicator is coded interworking not encountered (0).
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a call from Network B's UNI to Network A's UNI.
+2. Check that all resources are released.
+3. Repeat steps 1-2 with Networks A and B interchanged.
+
+**Test number:** 3.2.2.5 **Ref.:** 2.2.5/Q.764, 5.2.6/Q.931.
+
+**Config:** Undetermined Access → ISDN Access (See Figure 6)
+
+**Title:** Unsuccessful call set-up – Address incomplete
+
+**Purpose:** To verify that the call will be successfully released, if called number is incomplete.
+
+**Pre-test conditions:** Called number is incomplete.
+
+#### **Expected message sequence**
+
+| Network A | Network B | |
+|-----------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------|
+| | ← IAM | FCI: Interworking encountered (1), ISDN User Part not used all the way (0), Originating access non-ISDN (0) – see Note |
+| | ← COT | Optional message |
+| REL → | | Cause Ind.: Address incomplete (28), location public network serving remote user (0100) or transit network (0011) or international network (0111) |
+| | ← RLC | |
+
+NOTE – In case of calls to a non-ISUP Signalling System No. 7 system, the interworking indicator is coded interworking not encountered (0).
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a call from Network B's UNI to Network A's UNI.
+2. Check that all resources are released.
+3. Repeat steps 1-2 with Networks A and B interchanged.
+
+**Test number:** 3.2.3.1 **Ref.:** 2.3.1/Q.764, 5.2.6/Q.931.
+**Config:** Undetermined Access → ISDN Access (See Figure 6)
+**Title:** Abnormal situation during a call – No response from called party
+**Purpose:** To verify that the call will be successfully released when the T303 timer expires.
+
+**Pre-test conditions:** Called party does not respond.
+
+#### **Expected message sequence**
+
+| | Network A | Network B |
+|---------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------|
+| | ← | IAM FCI: Interworking encountered (1), ISDN User Part not used all the way (0), Originating access non-ISDN (0) – see Note |
+| | ← | COT Optional message |
+| Case a | REL → | Cause Ind.: No user responding (18), location public network serving remote user (0100) or private network serving remote user (0101) |
+| | ← | RLC |
+| Case b | ACM → | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | REL → | Cause Ind.: No user responding (18), location public network serving remote user (0100) or private network serving remote user (0101) |
+| | ← | RLC |
+
+NOTE – In case of calls to a non-ISUP Signalling System No. 7 system, the interworking indicator is coded interworking not encountered (0).
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Initiate a call from Network B's UNI to Network A's UNI.
+2. Check that all resources are released.
+3. Repeat steps 1-2 with Networks A and B interchanged.
+
+**Test number:** 3.3.1.1 **Ref.:** 2.3.1/Q.764, 5.2.6/Q.931, 5.3.1/Q.699.
+
+**Config.:** Undetermined Access → Undetermined Access (See Figure 7)
+
+**Title:** Normal call release – Calling party clears after answer
+
+**Purpose:** To verify that the calling party can successfully release a call after receipt of answer.
+
+#### **Pre-test conditions:**
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking encountered (1), ISDN User Part not used all the way (0), Originating access non-ISDN (0) – see Note |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking encountered (1), ISDN User Part not used all the way (0), Terminating access non-ISDN (0) – see Note |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking encountered (1), ISDN User Part not used all the way (0), Terminating access non-ISDN (0) – see Note |
+| | ← | CPG Optional message Event Info: alerting (0000001) |
+| | ← | ANM |
+| ← COMMUNICATION → | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location beyond interworking point (1010) |
+| | ← | RLC |
+
+NOTE – In case of calls to a non-ISUP Signalling System No. 7 system, the interworking indicator is coded interworking not encountered (0).
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a call from Network A's UNI to Network B's UNI.
+2. Check the propriety of speech.
+3. Clear the call from Network A's UNI.
+4. Check that all resources are released.
+5. Repeat steps 1-4 with Networks A and B interchanged.
+
+**Test number:** 4.1.1.1 **Ref.:** 2.3.1/Q.764, 5.1.6/Q.931, 6.3.1/Q.699.
+
+**Config.:** ISDN Access → Non-ISDN Access (See Figure 8)
+
+**Title:** Normal call release – Calling party clears after answer
+
+**Purpose:** To verify that the calling party can successfully release a call after receipt of answer.
+
+#### **Pre-test conditions:**
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-------------------|---|---------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access ISDN (1) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access non-ISDN (0) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access non-ISDN (0) |
+| | ← | CPG Optional message Event Info: alerting (0000001) |
+| | ← | ANM |
+| ⇐ COMMUNICATION ⇒ | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) or private network serving remote user (0100) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a speech call from Network A's UNI to Network B's UNI.
+2. Check the propriety of speech.
+3. Clear the call from Network A's UNI.
+4. Check that all resources are released.
+5. Repeat steps 1-4 with Networks A and B interchanged.
+
+**Test number:** 4.2.1.1 **Ref.:** 2.3.1/Q.764, 5.2.6/Q.931, 6.3.2/Q.699.
+
+**Config.:** Non-ISDN Access → ISDN Access (See Figure 8)
+
+**Title:** Normal call release – Calling party clears after answer
+
+**Purpose:** To verify that the calling party can successfully release a call after receipt of answer.
+
+#### **Pre-test conditions:**
+
+#### **Expected message sequence**
+
+
+
+| | Network A | Network B |
+|-------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------|
+| | | ← IAM FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access non-ISDN (0) |
+| | | ← COT Optional message |
+| Case a | ACM → | BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ANM → | |
+| Case b | ACM → | BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | CPG → | Event Info: alerting (0000001) |
+| | ANM → | |
+| ⇐ COMMUNICATION ⇒ | | |
+| | ← REL | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | RLC → | |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a call from Network B's UNI to Network A's UNI.
+2. Check the propriety of speech.
+3. Clear the call from Network B's UNI.
+4. Check that all resources are released.
+5. Repeat steps 1-4 with Networks A and B interchanged.
+
+**Test number:** 4.3.1.1 **Ref.:** 2.3.1/Q.764, D.2.1.4.1/Q.764, 7.3.1/Q.699.
+
+**Config.:** Undetermined Access → Non-ISDN Access (See Figure 9)
+
+**Title:** Normal call release – Calling party clears after answer
+
+**Purpose:** To verify that the calling party can successfully release a call after receipt of answer.
+
+#### **Pre-test conditions:**
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-------------------|---|-------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking encountered (1), ISDN User Part not used all the way (0), Originating access non-ISDN (0) – see Note |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access ISDN (1) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access non-ISDN (0) |
+| | ← | CPG Optional message Event Info: alerting (0000001) |
+| | ← | ANM |
+| ⇐ COMMUNICATION ⇒ | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location beyond interworking point (1010) |
+| | ← | RLC |
+
+NOTE – In case of calls to a non-ISUP Signalling System No. 7 system, the interworking indicator is coded interworking not encountered (0).
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a call from Network A's UNI to Network B's UNI.
+2. Check the propriety of speech.
+3. Clear the call from Network A's UNI.
+4. Check that all resources are released.
+5. Repeat steps 1-4 with Networks A and B interchanged.
+
+**Test number:** 4.4.1.1 **Ref.:** 2.3.1/Q.764, D.2.1.4.1/Q.764, 7.3.2/Q.699.
+
+**Config.:** Non-ISDN Access → Undetermined Access (See Figure 9)
+
+**Title:** Normal call release – Calling party clears after answer
+
+**Purpose:** To verify that the calling party can successfully release a call after receipt of answer.
+
+#### **Pre-test conditions:**
+
+#### **Expected message sequence**
+
+| | Network A | Network B |
+|-------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | ← | IAM FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access non-ISDN (0) |
+| | ← | COT Optional message |
+| Case a | ACM → | BCI: Subscriber free (01), Interworking encountered (1), ISDN User Part not used all the way (0), Terminating access non-ISDN (0) – see Note |
+| | ANM → | |
+| Case b | ACM → | BCI: No indication (00), Interworking encountered (1), ISDN User Part not used all the way (0), Terminating access non-ISDN (0) – see Note |
+| | CPG → | Optional message Event Info: alerting (0000001) |
+| | ANM → | |
+| ⇐ COMMUNICATION ⇒ | | |
+| | ← | REL Cause Ind.: Normal call clearing (16), location user (0000) or public network serving remote user (0100) or private network serving remote user (0101) |
+| | RLC → | |
+
+NOTE – In case of calls to a non-ISUP Signalling System No. 7 system, the interworking indicator is coded interworking not encountered (0).
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a call from Network B's UNI to Network A's UNI.
+2. Check the propriety of speech.
+3. Clear the call from Network B's UNI.
+4. Check that all resources are released.
+5. Repeat steps 1-4 with Networks A and B interchanged.
+
+**Test number:** 4.5.1.1 **Ref.:** 2.3.1/Q.764, D.2.1.4.1/Q.764, 8.3.1/Q.699.
+
+**Config.:** Non-ISDN Access → Non-ISDN Access (See Figure 10)
+
+**Title:** Normal call release – Calling party clears after answer
+
+**Purpose:** To verify that the calling party can successfully release a call after receipt of answer.
+
+#### **Pre-test conditions:**
+
+#### **Expected message sequence**
+
+| Network A | | Network B |
+|-------------------|---|---------------------------------------------------------------------------------------------------------------------------------------|
+| IAM | → | FCI: Interworking not encountered (0), ISDN User Part used all the way (1), Originating access non-ISDN (0) |
+| COT | → | Optional message |
+| Case a | ← | ACM BCI: Subscriber free (01), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access non-ISDN (0) |
+| | ← | ANM |
+| Case b | ← | ACM BCI: No indication (00), Interworking not encountered (0), ISDN User Part used all the way (1), Terminating access non-ISDN (0) |
+| | ← | CPG Optional message Event Info: alerting (0000001) |
+| | ← | ANM |
+| ⇐ COMMUNICATION ⇒ | | |
+| REL | → | Cause Ind.: Normal call clearing (16), location user (0000) |
+| | ← | RLC |
+
+#### **Test description (ISUP'92, Comb):**
+
+1. Make a call from Network A's UNI to Network B's UNI.
+2. Check the propriety of speech.
+3. Clear the call from Network A's UNI.
+4. Check that all resources are released.
+5. Repeat steps 1-4 with Networks A and B interchanged.
+
+
+
+# ITU-T RECOMMENDATIONS SERIES
+
+- Series A Organization of the work of the ITU-T
+- Series B Means of expression: definitions, symbols, classification
+- Series C General telecommunication statistics
+- Series D General tariff principles
+- Series E Overall network operation, telephone service, service operation and human factors
+- Series F Non-telephone telecommunication services
+- Series G Transmission systems and media, digital systems and networks
+- Series H Audiovisual and multimedia systems
+- Series I Integrated services digital network
+- Series J Transmission of television, sound programme and other multimedia signals
+- Series K Protection against interference
+- Series L Construction, installation and protection of cables and other elements of outside plant
+- Series M TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits
+- Series N Maintenance: international sound programme and television transmission circuits
+- Series O Specifications of measuring equipment
+- Series P Telephone transmission quality, telephone installations, local line networks
+- Series Q Switching and signalling**
+- Series R Telegraph transmission
+- Series S Telegraph services terminal equipment
+- Series T Terminals for telematic services
+- Series U Telegraph switching
+- Series V Data communication over the telephone network
+- Series X Data networks and open system communication
+- Series Z Programming languages
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.81.7-199706-I_PDF-E/raw.md b/marked/Q/T-REC-Q.81.7-199706-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..de199573ba86b57fcccce4f2038b3aa0d21b0635
--- /dev/null
+++ b/marked/Q/T-REC-Q.81.7-199706-I_PDF-E/raw.md
@@ -0,0 +1,25 @@
+
+
+# STAGE 2 DESCRIPTION FOR NUMBER IDENTIFICATION SUPPLEMENTARY SERVICES
+
+Recommendation Q.81.7
+
+## MALICIOUS CALL IDENTIFICATION
+
+For further study.
+
+\* \* \*
+
+Recommandation Q.81.7
+
+### IDENTIFICATION DES APPELS MALVEILLANTS
+
+Reste à étudier.
+
+\* \* \*
+
+Recomendación Q.81.7
+
+## IDENTIFICACIÓN DE LLAMADAS MALICIOSAS
+
+Queda en estudio.
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.811-200402-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Q/T-REC-Q.811-200402-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4606e47f749609d72234e7ec5b7b28c07f06e686
--- /dev/null
+++ b/marked/Q/T-REC-Q.811-200402-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:97566828919f920d1b449e5150c9521ecec8140c8b86c632c4dc08e8d6551769
+size 117099
diff --git a/marked/Q/T-REC-Q.811-200402-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.811-200402-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30
--- /dev/null
+++ b/marked/Q/T-REC-Q.811-200402-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359
+size 8245
diff --git a/marked/Q/T-REC-Q.811-200402-I_PDF-E/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg b/marked/Q/T-REC-Q.811-200402-I_PDF-E/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1d54593b95ef5a7a136ea346c2071d556efbd0c7
--- /dev/null
+++ b/marked/Q/T-REC-Q.811-200402-I_PDF-E/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:71c037729beab8e2cb1220d291316c682c9a35a80de129d1bc6ec67297283df2
+size 26077
diff --git a/marked/Q/T-REC-Q.811-200402-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.811-200402-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c8f320240eeb19d6bc5754246ddb2ccd25ec1262
--- /dev/null
+++ b/marked/Q/T-REC-Q.811-200402-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0909e66673467d639278fd72eb9c83e7944ef839b87d40d500950a9f4433daae
+size 105395
diff --git a/marked/Q/T-REC-Q.811-200402-I_PDF-E/raw.md b/marked/Q/T-REC-Q.811-200402-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..840f640b46105602d408ab3597288be3d2c2cb2d
--- /dev/null
+++ b/marked/Q/T-REC-Q.811-200402-I_PDF-E/raw.md
@@ -0,0 +1,1589 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.811**
+
+(02/2004)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Q3 interface
+
+---
+
+**Lower layer protocol profiles for the Q and X
+interfaces**
+
+ITU-T Recommendation Q.811
+
+---
+
+# 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 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## **ITU-T Recommendation Q.811**
+
+# **Lower layer protocol profiles for the Q and X interfaces**
+
+## **Summary**
+
+This Recommendation provides the lower layer protocol profiles for the Q and X interfaces as defined in ITU-T Rec. M.3010. It also provides a method for interworking.
+
+## **Source**
+
+ITU-T Recommendation Q.811 was approved on 13 February 2004 by ITU-T Study Group 4 (2001-2004) under the ITU-T Recommendation A.8 procedure.
+
+# FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2004
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+# CONTENTS
+
+###### Page
+
+| | | |
+|------------|--------------------------------------------------------------------------------|----|
+| 1 | Scope ..... | 1 |
+| 2 | References ..... | 1 |
+| 3 | Abbreviations ..... | 6 |
+| 4 | DCN model..... | 8 |
+| 4.1 | CONS1 ..... | 8 |
+| 4.2 | CONS2, CONS3, CLNS3 ..... | 8 |
+| 4.3 | CLNS1..... | 8 |
+| 4.4 | CLNS2..... | 8 |
+| 4.5 | CONS6 ..... | 9 |
+| 4.6 | IP ..... | 9 |
+| 5 | Lower layer protocol profiles: Overview ..... | 9 |
+| 6 | Requirements for network layer/transport layer interface..... | 9 |
+| 7 | Defined protocol profiles..... | 9 |
+| 7.1 | Connectionless-mode protocol profiles..... | 9 |
+| 7.2 | Connection-mode protocol profiles..... | 10 |
+| 7.3 | CL-LAN profile (CLNS1)..... | 11 |
+| 7.4 | CL-WAN profile (CLNS2) ..... | 16 |
+| 7.5 | ISDN protocol profile (CLNS3)..... | 21 |
+| 7.6 | IP protocol profiles..... | 22 |
+| 7.7 | Ethernet profile..... | 23 |
+| 7.8 | X.25/LAPB protocol profile (CONS1) ..... | 23 |
+| 7.9 | Packet mode bearer service on the D-channel (CONS2) ..... | 26 |
+| 7.10 | Packet mode bearer service on the B-channel (CONS3) ..... | 27 |
+| 7.11 | Signalling System No. 7 networks (CONS5)..... | 27 |
+| 7.12 | Connection oriented LAN (CONS6)..... | 27 |
+| 7.13 | Conformance requirements ..... | 28 |
+| 8 | Network layer service..... | 29 |
+| 8.1 | Network layer profiles..... | 29 |
+| 8.2 | Internetworking ..... | 30 |
+| Annex A | – Protocol stack for information transfer over ISDN transparent B-channel..... | 32 |
+| A.1 | Introduction ..... | 32 |
+| A.2 | Network profile CONS4..... | 32 |
+| Annex B | – Examples of NSAP structures for CLNP ..... | 35 |
+| Appendix I | – Changes to ISP conformance requirements ..... | 36 |
+
+
+
+# Lower layer protocol profiles for the Q and X interfaces
+
+# 1 Scope
+
+This Recommendation is a part of a series of Recommendations dealing with the transfer of information for the management of telecommunications systems. This Recommendation defines the requirements of lower layer protocol profiles for the Q and X interfaces1, as defined in ITU-T Rec. M.3010 [1] and in other M.3000-series Recommendations. The companion ITU-T Rec. Q.812 [2] defines the requirements of the upper layer protocol profiles for the Q and X interfaces. The Q and X interfaces will support bidirectional data transfer for the management of telecommunications systems.
+
+The need for security functionality is recognized, but is not fully addressed in this Recommendation and is for further study. Users may need to use mechanisms outside this Recommendation in order to address their specific security needs. Security mechanisms chosen may depend on the network configuration being used.
+
+If new operational requirements are developed that imply distinctions to be made here between the Q and X interfaces, future versions of this Recommendation, or possibly new Recommendations, will reflect these differences.
+
+This Recommendation defines:
+
+- the layer service profiles for the defined supported networks;
+- the layer protocol profiles for the defined supported networks;
+- the requirements at the layer 3/layer 4 service boundary for any network used to support the Q and X interfaces of the TMN.
+
+This Recommendation conforms to the "T" profiles in framework for International Standardized Profiles (ISP) as specified in ISO/IEC TR 10000-1 [63] and ISO/IEC TR 10000-2 [64]. Profiles in this Recommendation align with equivalent ISPs (as specified in conformance clause) if available. It is the intention to align those profiles for which there are no equivalent ISPs at present to ISPs as they are standardized by ISO SGFS.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [1] ITU-T Recommendation M.3010 (2000), *Principles for a telecommunications management network*.
+- [2] ITU-T Recommendation Q.812 (2004), *Upper layer protocol profiles for the Q and X interfaces*.
+- [3] ITU-T Recommendation X.200 (1994) | ISO/IEC 7498-1:1994, *Information technology – Open Systems Interconnection – Basic Reference Model: The basic model*.
+
+---
+
+1 This protocol is also applicable to the Qx interface when a full seven layer stack is required.
+
+- [4] ISO/IEC 8802-3:2000, *Information technology – Telecommunications and information exchange between systems – Local and metropolitan area networks – Specific requirements – Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications.*
+- [5] ISO/IEC 8802-2:1998, *Information technology – Telecommunications and information exchange between systems – Local and metropolitan area networks – Specific requirements – Part 2: Logical link control.*
+- [6] ITU-T Recommendation X.213 (2001) | ISO/IEC 8348:2002, *Information technology – Open Systems Interconnection – Network service definition.*
+- [7] ITU-T Recommendation X.233 (1997) | ISO/IEC 8473-1:1998, *Information technology – Protocol for providing the connectionless-mode network service: Protocol specification.*
+- [8] ISO/IEC 8473-2:1996, *Information technology – Protocol for providing the connectionless-mode network service – Part 2: Provision of the underlying service by an ISO/IEC 8802 subnetwork.*
+- [9] ITU-T Recommendation X.622 (1994) | ISO/IEC 8473-3:1995, *Information technology – Protocol for providing the connectionless-mode Network service: Provision of the underlying service by an X.25 subnetwork.*
+- [10] ITU-T Recommendation X.623 (1994) | ISO/IEC 8473-4:1995, *Information technology – Protocol for providing the connectionless-mode Network service: Provision of the underlying service by a subnetwork that provides the OSI data link service.*
+- [11] ITU-T Recommendation X.625 (1996) | ISO/IEC 8473-5:1997, *Information technology – Protocol for providing the connectionless-mode Network service: Provision of the underlying service by ISDN circuit-switched B-channels.*
+- [12] ITU-T Recommendation X.25 (1996), *Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit.*
+- [13] ISO/IEC 7776:1995, *Information technology – Telecommunications and information exchange between systems – High-level data link control procedures – Description of the X.25 LAPB-compatible DTE data link procedures.*
+- [14] ISO/IEC 8880-3:1990, *Information technology – Telecommunications and information exchange between systems – Protocol combinations to provide and support the OSI Network Service – Part 3: Provision and support of connectionless-mode Network Service.*
+- [15] ISO 8648:1988, *Information processing systems – Open Systems Interconnection – Internal organization of the Network Layer.*
+- [16] ISO/IEC 8208:2000, *Information technology – Data communications – X.25 Packet Layer Protocol for Data Terminal Equipment.*
+- [17] ITU-T Recommendation X.223 (1993) | ISO/IEC 8878:1992, *Use of X.25 to provide the OSI connection-mode Network service for ITU-T applications.*
+- [18] ITU-T Recommendation E.164 (1997), *The international public telecommunication numbering plan.*
+- [19] ITU-T Recommendation X.121 (2000), *International numbering plan for public data networks.*
+- [20] ITU-T Recommendation X.244 (1988), *Procedure for the exchange of protocol identification during virtual call establishment on packet switched public data networks.*
+
+- [21] ISO/IEC TR 9577:1999, *Information technology – Protocol identification in the network layer.*
+- [22] ITU-T Recommendation I.430 (1995), *Basic user-network interface – Layer 1 specification.*
+- [23] ITU-T Recommendation I.431 (1993), *Primary rate user-network interface – Layer 1 specification.*
+- [24] ITU-T Recommendation Q.921 (1997), *ISDN user-network interface – Data link layer specification.*
+- [25] ITU-T Recommendation X.31 (1995), *Support of packet mode terminal equipment by an ISDN.*
+- [26] ISO/IEC 8878:1992, *Information technology – Telecommunications and information exchange between systems – Use of X.25 to provide the OSI Connection-mode Network Service.*
+- [27] ITU-T Recommendation Q.702 (1988), *Signalling data link.*
+- [28] ITU-T Recommendation Q.703 (1996), *Signalling link.*
+- [29] ITU-T Recommendation Q.704 (1996), *Signalling network functions and messages.*
+- [30] ITU-T Recommendation Q.711 (2001), *Functional description of the signalling connection control part.*
+- [31] ITU-T Recommendation Q.712 (1996), *Definition and function of signalling connection control part messages.*
+- [32] ITU-T Recommendation Q.713 (2001), *Signalling connection control part formats and codes.*
+- [33] ITU-T Recommendation Q.714 (2001), *Signalling connection control part procedures.*
+- [34] ITU-T Recommendation Q.716 (1993), *Signalling System No. 7 – Signalling Connection Control Part (SCCP) performance.*
+- [35] ITU-T Recommendation V.24 (2000), *List of definitions for interchange circuits between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE).*
+- [36] ITU-T Recommendation V.28 (1993), *Electrical characteristics for unbalanced double-current interchange circuits.*
+- [37] ITU-T Recommendation V.36 (1988), *Modems for synchronous data transmission using 60-108 kHz group band circuits.*
+- [38] ISO 2110:1989, *Information technology – Data communication – 25-pole DTE/DCE interface connector and contact number assignments.*
+- [39] ISO/IEC 2593:2000, *Information technology – Telecommunications and information exchange between systems – 34-pole DTE/DCE interface connector mateability dimensions and contact number assignments.*
+- [40] ITU-T Recommendation X.612 (1992) | ISO/IEC 9574:1992, *Information technology – Provision of the OSI connection-mode network service by packet-mode terminal equipment connected to an Integrated Services Digital Network (ISDN).*
+- [41] ITU-T Recommendation X.214 (1995) | ISO/IEC 8072:1996, *Information technology – Open Systems Interconnection – Transport service definition.*
+
+- [42] ITU-T Recommendation X.224 (1995) | ISO/IEC 8073:1997, *Information technology – Open Systems Interconnection – Protocol for providing the connection-mode transport service.*
+- [43] ISO/IEC 8881:1989, *Information processing systems – Data communications – Use of the X.25 packet level protocol in local area networks.*
+- [44] ISO/IEC ISP 10608:1992, *Information technology – International Standardized Profile TAnnnn – Connection-mode Transport Service over Connectionless-mode Network Service.*
+ - Part 1: *General overview and subnetwork-independent requirements.*
+ - Part 2: *TA51 profile including subnetwork-dependent requirements for CSMA/CD Local Area Networks (LANs).*
+ - Part 5: *TA1111/TA1121 profiles including subnetwork-dependent requirements for X.25 packet-switched data networks using virtual calls.*
+- [45] ISO/IEC ISP 10609:1992, *Information technology – International Standardized Profiles TB, TC, TD and TE – Connection-mode Transport Service over connection-mode Network Service.*
+ - Part 1: *Subnetwork-type independent requirements for Group TB.*
+ - Part 5: *Definition of Profiles TB1111/TB1121.*
+ - Part 9: *Subnetwork-type dependent requirements for Network Layer, Data Link Layer and Physical Layer concerning permanent access to a packet switched data network using virtual calls.*
+- [46] ISO 9542:1988, *Information processing systems – Telecommunications and information exchange between systems – End system to Intermediate system routeing exchange protocol for use in conjunction with the Protocol for providing the connectionless-mode network service.*
+- [47] ISO/IEC 10589:2002, *Information technology – Telecommunications and information exchange between systems – Intermediate system to Intermediate system intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode network service.*
+- [48] ISO/IEC 10747:1994, *Information technology – Telecommunications and information exchange between systems – Protocol for exchange of inter-domain routeing information among intermediate systems to support forwarding of ISO 8473 PDUs.*
+- [49] ITU-T Recommendation X.75 (1996), *Packet-switched signalling system between public networks providing data transmission services.*
+- [50] ITU-T Recommendation I.550/X.325 (1996), *General arrangements for interworking between Packet-Switched Public Data Networks (PSPDNs) and Integrated Services Digital Networks (ISDNs) for the provision of data transmission services.*
+- [51] ITU-T Recommendation X.326 (1988), *General arrangements for interworking between Packet-Switched Public Data Networks (PSPDNs) and Common Channel Signalling Network (CCSN).*
+- [52] ITU-T Recommendation X.327 (1993), *General arrangements for interworking between Packet-Switched Public Data Networks (PSPDNs) and private data networks for the provision of data transmission services.*
+- [53] ITU-T Recommendation X.211 (1995) | ISO/IEC 10022:1996, *Information technology – Open Systems Interconnection – Physical service definition.*
+
+- [54] ISO/IEC 11570:1992, *Information technology – Telecommunications and information exchange between systems – Open Systems Interconnection – Transport protocol identification mechanism.*
+- [55] ISO/IEC 10177:1993, *Information technology – Telecommunications and information exchange between systems – Provision of the connection-mode Network internal layer service by intermediate systems using ISO/IEC 8208, the X.25 Packet Layer Protocol.*
+- [56] ISO/IEC 10028:1993, *Information technology – Telecommunications and information exchange between systems – Definition of the relaying functions of a Network layer intermediate system.*
+- [57] ITU-T Recommendation Q.708 (1999), *Assignment procedures for international signalling point codes.*
+- [58] ITU-T Recommendation X.273 (1994) | ISO/IEC 11577:1995, *Information technology – Open Systems Interconnection – Network layer security protocol.*
+- [59] ISO/IEC 11575:1995, *Information technology – Telecommunications and information exchange between systems – Protocol mappings for the OSI Data Link service.*
+- [60] ITU-T Recommendation X.212 (1995) | ISO/IEC 8886:1996, *Information technology – Open Systems Interconnection – Data link service definition.*
+- [61] ITU-T Recommendation Q.931 (1998), *ISDN user-network interface layer 3 specification for basic call control.*
+- [62] ITU-T Recommendation I.320 (1993), *ISDN protocol reference model.*
+- [63] ISO/IEC TR 10000-1:1998, *Information technology – Framework and taxonomy of International Standardized Profiles – Part 1: General principles and documentation framework.*
+- [64] ISO/IEC TR 10000-2:1998, *Information technology – Framework and taxonomy of International Standardized Profiles – Part 2: Principles and Taxonomy for OSI Profiles.*
+- [65] ISO 4902:1989, *Information technology – Data communication – 37-pole DTE/DCE interface connector and contact number assignments.*
+- [66] ISO 4903:1989, *Information technology – Data communication – 15-pole DTE/DCE interface connector and contact number assignments.*
+- [67] ITU-T Recommendation V.10/X.26 (1993), *Electrical characteristics for unbalanced double-current interchange circuits operating at data signalling rates nominally up to 100 kbit/s.*
+- [68] ITU-T Recommendation V.11/X.27 (1996), *Electrical characteristics for balanced double-current interchange circuits operating at data signalling rates up to 10 Mbit/s.*
+- [69] IETF RFC 2401 (1998), *Security Architecture for the Internet Protocol.*
+- [70] IETF RFC 2460 (1998), *Internet Protocol, Version 6 (IPv6) Specification.*
+- [71] IETF RFC 2402 (1998), *IP Authentication Header.*
+- [72] IETF RFC 2406 (1998), *IP Encapsulating Security Payload (ESP).*
+- [73] ITU-T Recommendation G.7712/Y.1703 (2003), *Architecture and specification of data communication network.*
+- [74] IETF RFC 1122 (1989), *Requirements for Internet Hosts – Communication Layers.*
+- [75] ITU-T Recommendation M.3030 (2002), *Telecommunications Markup Language (tML) framework.*
+
+- [76] IETF RFC 894 (1984), *A Standard for the Transmission of IP Datagrams over Ethernet Networks*.
+- [77] IETF RFC 826 (1982), *An Ethernet Address Resolution Protocol*.
+
+# 3 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|-------|-----------------------------------------------|
+| AFI | Authority and Format Identifier |
+| AH | Authentication Header |
+| BIS | Border Intermediate System |
+| CD | Collision Detection |
+| CLNP | Connectionless-mode Network layer Protocol |
+| CLNS | Connectionless-mode Network layer Service |
+| Conf | Confirm |
+| CONP | Connection-mode Network layer Protocol |
+| CONS | Connection-mode Network layer Service |
+| COTS | Connection-mode Transport Service |
+| CSMA | Carrier Sense Multiple Access |
+| CUG | Closed User Group |
+| DCE | Data Communication Equipment |
+| DCF | Data Communication Function |
+| DCN | Data Communication Network |
+| DIS | Draft International Standard |
+| DLC | Data Link Connection |
+| DLS | Data Link Service |
+| DSP | Domain Specific Part |
+| DTE | Data Terminal Equipment |
+| ES | End System |
+| ESP | Encapsulation Security Payload |
+| HDLC | High-level Data Link Control |
+| IDI | Initial Domain Identifier |
+| IDP | Initial Domain Part |
+| IDRP | Inter Domain Routing (or Routeing) Protocol |
+| IETF | Internet Engineering Task Force |
+| Ind | Indication |
+| IP | Internetworking Protocol |
+| IPSec | Security Infrastructure for Internet Protocol |
+| IS | Intermediate System |
+
+| | |
+|--------|------------------------------------------------|
+| ISDN | Integrated Services Digital Network |
+| ISO | International Organization for Standardization |
+| ISP | International Standardized Profile |
+| IW | Interworking Unit |
+| LLC | Logical Link Control |
+| LME | Layer Management Entity |
+| LSP | Link State Protocol Data Unit |
+| MAC | Media Access Control |
+| MD | Mediation Device |
+| MTP | Message Transfer Part |
+| NDM | Normal Disconnect Mode |
+| NE | Network Element |
+| NLR | Network Layer Relay |
+| NPDU | Network Protocol Data Unit |
+| NS | Network Service |
+| NSAP | Network Service Access Point |
+| OS | Operations System |
+| OSI | Open Systems Interconnection |
+| PDU | Protocol Data Unit |
+| Ph | Physical |
+| PhC | Physical Connection |
+| PhS | Physical Service |
+| PICS | Protocol Implementation Conformance Statement |
+| PVC | Permanent Virtual Circuit |
+| QA | Q Adapter |
+| QoS | Quality of Service |
+| Req | Request |
+| Res | Result |
+| RFC | Request For Comments |
+| SAP | Service Advertising Protocol |
+| SAPI | Security Application Program Interfaces |
+| SCCP | Signalling Connection Control Part |
+| SCF | Service Control Function |
+| SGFS | Special Group on Functional Standards |
+| SLP | Service Location Profile |
+| SND CF | Subnetwork Dependent Convergence Function |
+| SNP | Sequence Numbers Protocol Data Unit |
+
+| | |
+|------------------|---------------------------------------|
+| SNPA | Subnetwork Point of Attachment |
+| SVC 2 | Switched Virtual Circuit |
+| TCP | Transmission Control Protocol |
+| TMN | Telecommunications Management Network |
+| VC | Virtual Circuit |
+
+# 4 DCN model
+
+Table 20 identifies the lower layer protocols for interfaces requiring interworking as well as the interworking method.
+
+The following briefly describes the individual lower layer protocol profiles:
+
+- CONS1: A connection-mode packet interface using ITU-T Rec. X.25.
+- CONS2: A connection-mode packet interface using ITU-T Rec. X.31 on an ISDN D-channel.
+- CONS3: A connection-mode packet interface using ITU-T Rec. X.31 on an ISDN B-channel.
+- CONS6: A connection-mode packet interface X.25 over LAN.
+- CLNS1: A connectionless-mode interface using ISO/IEC 8802-2 type LANs using CSMA/CD.
+- CLNS2: A connectionless-mode interface using ISO CLNP over a connection-mode X.25 protocol.
+- CLNS3: A connectionless-mode interface using ISO CLNP over ISDN B-channels (see 7.5).
+- IP: Internet Protocol for use in the TMN (see 7.6).
+
+This clause provides typical examples of the application of these profiles at the Q and X interfaces. Other fields of application are not precluded by this Recommendation. The differences between the following profiles will be further discussed in ITU-T Rec. Q.812.
+
+## 4.1 CONS1
+
+CONS1 is applied to the reference point between PSPDN and OS/MD/QA/NE which communicates with OS accommodated in PSPDN and ISDN.
+
+## 4.2 CONS2, CONS3, CLNS3
+
+CONS2 and CONS3 are applied to the reference point between ISDN and OS/MD/QA/NE which communicates with OS accommodated in PSPDN or ISDN.
+
+## 4.3 CLNS1
+
+CLNS1 is applied to the reference point between LAN and OS/MD/QA/NE which communicates with OS accommodated in LAN or PSPDN.
+
+## 4.4 CLNS2
+
+CLNS2 is applied to the reference point between PSPDN and OS/MD/QA/NE which communicates with OS accommodated in LAN.
+
+---
+
+2 Switched Virtual Circuit corresponds to "Virtual call" used in ITU-T Rec. X.25.
+
+## **4.5 CONS6**
+
+CONS6 is applied to OS/MD/QA/NE which is connected to the reference point on connection-mode oriented LAN.
+
+## **4.6 IP**
+
+IP is applied to OS/MD/QA/NE and LANs which communicate with OS using IP accommodated in the LAN.
+
+# **5 Lower layer protocol profiles: Overview**
+
+The communication services and protocol referred to in this Recommendation are in accordance with the Open Systems Interconnection (OSI) reference model [3].
+
+The protocols for the different layers are based on ITU-T Recommendations and/or ISO/IEC Standards.
+
+The protocol profiles can be applied to DCN, as defined by ITU-T Rec. M.3010 [1].
+
+Any Administration may use any existing network that meets the requirements at the layer 3/layer 4 service boundary.
+
+For the Protocol Profiles defined in this Recommendation, interoperability mechanisms are to be defined as a part of this Recommendation. For networks not using these profiles, it is the responsibility of the individual Administration to solve any interoperability problems that may exist.
+
+# **6 Requirements for network layer/transport layer interface**
+
+See clause 8 and its subclauses.
+
+# **7 Defined protocol profiles**
+
+## **7.1 Connectionless-mode protocol profiles**
+
+### **7.1.1 LAN (see Figure 2)**
+
+NOTE – Figure 3/Q.811 (1993), **Protocol profile for network management**, has been deleted.
+
+### 7.1.2 WAN, LAN (see Figure 2)
+
+### 7.1.3 ISDN (see Figure 2)
+
+## 7.2 Connection-mode protocol profiles
+
+### 7.2.1 X.25/LAPB [see Figure 1 (1), (3), (2), (5)]
+
+
+
+The diagram illustrates five connection (CONS) profiles, each showing a stack of protocols. All profiles share a common top layer: ITU-T Rec. Q.812 upper layers.
+
+- (1) CONS1:**
+ - ITU-T Rec. Q.812 upper layers
+ - X.25 PLC ISO/IEC 8208 (ISO/IEC 8878)
+ - X.25 LAPB ISO/IEC 7776 SLP
+ - Recs X.27, X.21 X.21 bis V.11/X.27/V.36 V.28/V.24
+- (2) CONS2:**
+ - ITU-T Rec. Q.812 upper layers
+ - ITU-T Rec. X.612 | ISO/IEC 9574
+ - C-Plane: Q.931 procedures used as described in Rec. X.31
+ - U-Plane: ISO/IEC 8878 / ISO/IEC 8208 DTE/DCE operations
+ - Rec. Q.921 (SAPI = 16)
+ - Q.921 Layer 2 multiplexer
+ - D-channel
+ - I.430 (BA) or I.431 (PRA)
+- (3) CONS3:**
+ - ITU-T Rec. Q.812 upper layers
+ - ITU-T Rec. X.612 | ISO/IEC 9574
+ - C-Plane: Q.931 procedures used as described in Rec. X.31
+ - U-Plane: ISO/IEC 8878 / ISO/IEC 8208 DTE/DCE operations
+ - ITU-T Rec. X.212 / ISO/IEC 7776 SLP-DTE/DCE operation
+ - Rec. Q.921 (SAPI = 0)
+ - D-channel
+ - B-channel
+ - I.430 (BA) or I.431 (PRA)
+- (5) CONS6:**
+ - ITU-T Rec. Q.812 upper layers
+ - ISO/IEC 8208 / ISO/IEC 8881
+ - ISO/IEC 8802-2 LLC (Type 2) / ISO/IEC 8802-3 MAC CSMA/CD
+ - Not specified
+
+Figure 1/Q.811 – Connection (CONS) profiles diagram showing five profiles (CONS1 to CONS6) with their respective protocol stacks.
+
+NOTE – Further study is needed for the function of SCCP at the boundary of Network layer and Transport Layer.
+
+Q.811\_F01
+
+Figure 1/Q.811 – Connection (CONS) profiles
+
+
+
+The diagram illustrates the Connectionless (CLNS) profiles. At the top is a box labeled "ITU-T Rec. Q.812 upper layers". Below it, a box labeled "ITU-T Rec. X.233 | ISO/IEC 8473-1 CLNP (ITU-T Rec X.213 | ISO/IEC 8348 CLNS)" spans across the first three columns. To the right of this box is a box labeled "IP". Below the CLNP box, the first three columns are labeled "(4) CLNS1", "(7) CLNS2", and "(8) CLNS3" respectively. The fourth column is labeled "IP".
+
+- (4) CLNS1:** Below the CLNP box is a box labeled "ISO/IEC 8473-2". Below that is a box labeled "ISO/IEC 8802-2 LLC (Type 1)" with a dashed line below it labeled "ISO/IEC 8802-3 MAC CSMA/CD". Below that is a box labeled "Not specified".
+- (7) CLNS2:** Below the CLNP box is a box labeled "ITU-T Rec. X.622 | ISO/IEC 8473-3" with a dashed line below it labeled "X.25 PLP (ISO/IEC 8208)". Below that is a box labeled "X.25 LAPB ISO/IEC 7776 SLP". Below that is a box labeled "Recs X.27, X.21 X.21 bis V.11/X.27/V.36 V.28/V.24".
+- (8) CLNS3:** Below the CLNP box is a box labeled "ITU-T Rec. X.625 | ISO/IEC 8473-5". Below that, the box is split into three columns: "ITU-T Rec. Q.931", "ITU-T Rec. X.623 | ISO/IEC 8473-4", and "ITU-T Rec. X.622 | ISO/IEC 8473-3" with a dashed line below it labeled "ISO/IEC 8208". Below the first two columns is a box labeled "Rec. Q.921" with a dashed line below it labeled "ISO/IEC 11575" and "ISO/IEC 7776". Below the third column is a box labeled "Not specified". Below these is a box labeled "D-channel or B-channel I.430 (BA) or I.431 (PRA)".
+- IP:** Below the top "IP" box is a box labeled "Ethernet". Below that is a box labeled "Not specified".
+
+Diagram of Connectionless (CLNS) profiles showing four columns: (4) CLNS1, (7) CLNS2, (8) CLNS3, and IP. The diagram shows the hierarchy of protocols from ITU-T Rec. Q.812 upper layers down to the physical layer for each profile.
+
+Q.811\_F02
+
+**Figure 2/Q.811 – Connectionless (CLNS) profiles**
+
+## 7.3 CL-LAN profile (CLNS1)
+
+### 7.3.1 Physical layer profile
+
+#### 7.3.1.1 Service profile
+
+The service definition for the Physical layer shall comply with that specified in clause 6 of ISO/IEC 8802-3 [4].
+
+All of the primitives defined and listed in Table 1 are mandatory.
+
+**Table 1/Q.811 – Primitives of the Physical layer**
+
+| Primitive |
+|------------------------|
+| PLS-DATA-request |
+| PLS-DATA-indication |
+| PLS-CARRIER-indication |
+| PLS-SIGNAL-indication |
+
+#### 7.3.1.2 Protocol profile
+
+The possible bit rate will be 1 Mbit/s, 10 Mbit/s, or higher.
+
+#### 7.3.1.3 Physical interface
+
+Administrations will select the appropriate physical medium, e.g., coaxial cable, screened pairs, optical fibre according to technological and operational requirements.
+
+### 7.3.2 Data link layer profile
+
+The Data Link layer provides the unacknowledged connectionless-mode service. The access method employed is Carrier Sense Multiple Access with Collision Detection (CSMA/CD).
+
+#### 7.3.2.1 Media Access Control (MAC) profile
+
+The services and protocol of the CSMA/CD access method shall comply with those specified in ISO/IEC 8802-3 [4].
+
+The address length used at the MAC sub-layer shall be 48 bits.
+
+#### 7.3.2.2 Logical Link Control (LLC) profile
+
+The definition of the unacknowledged connectionless-mode LLC service shall comply with that specified in ISO/IEC 8802-2 [5]. All of the primitives defined for "Type 1" operation shall be supported.
+
+The protocol used to provide the unacknowledged connectionless-mode LLC service shall be as specified in ISO/IEC 8802-2 [5]. All of the commands and responses defined for "Type 1" operation shall be supported.
+
+### 7.3.3 Network layer profile
+
+#### 7.3.3.1 Services profile
+
+The definition of the connectionless-mode Network service shall comply with that specified in ITU-T Rec. X.213 | ISO/IEC 8348 [6]. Address formats supported shall also conform to ITU-T Rec. X.213 | ISO/IEC 8348 [6].
+
+The Network layer shall provide the N-UNITDATA service as specified in ITU-T Rec. X.213 | ISO/IEC 8348 [6].
+
+#### 7.3.3.2 Protocol profile
+
+The protocol shall be in accordance with the full protocol subset of category "Type 1" functions, as specified in ITU-T Rec. X.233 | ISO/IEC 8473-1 [7].
+
+#### 7.3.3.3 Network layer attributes
+
+Characteristics of the connectionless-mode Network layer service and the connectionless-mode Network layer protocol shall be as shown in Table 2.
+
+**Table 2/Q.811 – Connectionless-mode network layer service/protocol parameters**
+
+| | |
+|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| a | Destination and Source Addresses used by this Protocol shall conform to one of the Network Service Access Points (NSAPs) address formats specified in ITU-T Rec. X.213 ISO/IEC 8348 [6].
The Destination and Source Addresses are of variable length. The Destination and Source Address fields shall be as Network Protocol Address Information using the preferred Binary Encoding specified in ITU-T Rec. X.213 ISO/IEC 8348 [6]. |
+| b | The setting of Error Reporting Flag (E/R) shall be a local matter (Note). |
+| c | Partial Source Routing shall NOT be supported. A defect exists with this option which can cause PDUs to loop in the network until their lifetime expires. |
+| d | Inactive Subset – Implementations shall not transmit PDUs encoded using the ITU-T Rec. X.233 ISO/IEC 8473-1 inactive subset. Received PDUs encoded with the inactive subset shall be discarded. |
+| e | Segmentation – The non-segmentation subset shall NOT be used. However, implementations shall be capable of receiving and correctly processing PDUs which do not contain the segmentation part. |
+
+**Table 2/Q.811 – Connectionless-mode network layer service/protocol parameters**
+
+| | |
+|--------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| f | Segmentation Permitted Flag – Implementations shall NOT generate data PDUs without a segmentation part, i.e., the Segmentation Permitted Flag (SP) shall be set to 1 and the segmentation part shall be included. |
+| g | Lifetime Control – The lifetime parameter shall be used as specified in 6.4 of ITU-T Rec. X.233 ISO/IEC 8473-1. This parameter shall have an initial value of at least three times the network span (number of network entities) or three times the maximum transmission delay (in units of 500 milliseconds), whichever is greater. The default initial PDU lifetime control shall be 10 seconds. |
+| h | Quality of Service (QoS) – The use of the QoS Maintenance Parameter shall be dependent upon the QoS requirements of the subnetworks supporting an instance of OS-NE communications. When QoS is used, it shall comply with the specifications in 6.16, 6.19, and 7.5.6 of ITU-T Rec. X.233 ISO/IEC 8473-1. It is recommended that Quality of Service Maintenance be supported and that the globally unique QoS format be used which includes the Congestion Experienced (CE) bit used by the Congestion Notification option. |
+| i | Reassembly timer – The reassembly timer must be less than the largest value of all the lifetime parameters contained in all derived PDUs. The default Reassembly timer shall be 12 seconds. |
+| j | Congestion Notification – The use of Congestion Notification option is recommended. The default value should be 0 when originating PDUs. For NEs and MDs that act as ISs, it is recommended that Congestion Notification be supported so that end systems can take appropriate action to avoid and recover from network congestion. |
+| NOTE – The use of error Reporting and setting the E/R flag to 1 may lead to excessive network traffic. | |
+
+#### 7.3.3.4 ES-IS routing
+
+TMN entities that use the CLNP shall support the ISO 9542 [46] for ES-IS routing exchange. The ES-IS protocol is provisioned as either an End System (ES) role, or an Intermediate System (IS) role. The Data Communication Function (DCF) within the TMN entities must therefore be provisioned in accordance with their role(s).
+
+The ES-IS protocol subsets: Configuration Information (CI) and Redirection Information (RI) shall be supported in accordance with the type of subnetwork, as shown in Table 3. Tables 4 and 5 give the timer values and options for the ES and IS roles, respectively.
+
+**Table 3/Q.811 – ES-IS subsets**
+
+| Protocol subset | Type of subnetwork | | |
+|---------------------------------------------------------------------------------|-------------------------|--------------------|---------------------------|
+| | Point-to-point (Note 1) | Broadcast (Note 2) | General topology (Note 3) |
+| Configuration Information (CI) | M | M | NS |
+| Redirection Information (RI) | NS | | M |
+| M Mandatory support | | | |
+| NS Not supported | | | |
+| NOTE 1 – An example of a point-to-point subnetwork is the SDH DCC. | | | |
+| NOTE 2 – An example of a broadcast subnetwork is a CSMA/CD LAN. | | | |
+| NOTE 3 – An example of a general topology subnetwork is an X.25 packet network. | | | |
+
+**Table 4/Q.811 – ES-IS protocol timers and options for the end system role**
+
+| | Value/Range/Option | Default |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|--------------------------------------|
+| Timers:
Configuration Timer
Holding Timer | 1-200 s
1-500 s | (50 s)
(105 s) |
+| Functions:
PDU Header Checksum Generation
Configuration Notification (Notes 1, 3)
Refresh Redirect (Note 2)
Address and SNPA Mask Processing (Note 2) | Optional, use, non-use
Optional, use, non-use
Use, non-use
Optional, use, non-use | (Non-use)
(Use)
(Use)
(Use) |
+| Supplemental Functions per Annex B of ISO/IEC 9542:
Optimization (Note 4)
Rapid Configuration | Optional, use, non-use
Optional, use, non-use | (Use)
– |
+| NOTE 1 – Applies to Configuration Information (CI) subset.
NOTE 2 – Applies to the Redirection Information (RI) subset.
NOTE 3 – See recommendation in 6.7 of ISO/IEC 9542.
NOTE 4 – See B.4 of ISO/IEC 9542. | | |
+
+**Table 5/Q.811 – ES-IS protocol timers and options for the intermediate system role**
+
+| | Value/Range/Option | Default |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|-----------------------------|
+| Timers:
Configuration Timer
Holding Timer | 1-200 s
1-500 s | (10 s)
(25 s) |
+| Functions:
PDU Header Checksum Generation
Configuration Notification (Notes 1, 3)
Address and SNPA Mask Processing (Note 2) | Optional, use, non-use
Optional, use, non-use
Optional, use, non-use | (Non-use)
(Use)
(Use) |
+| Supplemental Functions per Annex B of ISO/IEC 9542:
Rapid Configuration | Optional, use, non-use | – |
+| NOTE 1 – Applies to Configuration Information (CI) subset.
NOTE 2 – Applies to the Redirection Information (RI) subset.
NOTE 3 – See recommendation in 6.7 of ISO/IEC 9542. | | |
+
+#### 7.3.3.5 IS-IS intra-domain routing
+
+ISO/IEC 10589 [47], the IS-IS intra-domain protocol for use with the CLNP, shall be used by TMN entities that operate as Intermediate Systems for the purpose of routing connectionless NPDUs.
+
+Each IS within the TMN must be capable of routing within their area and therefore must provide the functionality of a Level 1 IS. Additionally, an IS may be provisioned as a Level 2 IS, which provides the capability of routing from one area to another and therefore contains routing information about ISs outside a specific area. The functionality of a Level 2 IS is not needed in each IS within the TMN. An example of a Level 2 IS might be a gateway NE. Details for use of ISO/IEC 10589 for TMN applications are found in Tables 6 through 11.
+
+**Table 6/Q.811 – IS-IS general protocol functions**
+
+| Protocol function | Value/Range/Option | Default |
+|--------------------------|---------------------------|----------------|
+| Authentication | Optional, use, non-use | (Non-use) |
+| Delay Metric | Optional, use, non-use | (Non-use) |
+| Expense Metric | Optional, use, non-use | (Non-use) |
+| Error Metric | Optional, use, non-use | (Non-use) |
+
+**Table 7/Q.811 – IS-IS general processes**
+
+| Function | Value/Range/Option | Default |
+|-------------------|---------------------------|----------------|
+| Decision Process: | | |
+| Equal Cost Paths | Optional, use, non-use | (Non-use) |
+| Down Stream Paths | Optional, use, non-use | (Non-use) |
+
+**Table 8/Q.811 – IS-IS Level 1 specific functions**
+
+| Function | Value/Range/Option | Default |
+|-------------------------------------------------------------------------------------|---------------------------|----------------|
+| Protocol Summary: | | |
+| Maximum Area Addresses (Note) | 0-12 | (3) |
+| Area IS Count (Note) | 1-512 | (512) |
+| NOTE – These numbers are preliminary and are subject for study and possible change. | | |
+
+**Table 9/Q.811 – IS-IS Level 2 specific functions**
+
+| Function | Value/Range/Option | Default |
+|---------------------------------------------------------------------------------------|---------------------------|----------------|
+| Protocol Summary: | | |
+| L2 IS (Note 2) | Optional, use, non-use | (Non-use) |
+| L2 IS Count (Note 1) | 1-512 | (256) |
+| IS Count (Note 3) | 1-512 | (512) |
+| Reachable Address Prefix | Optional, use, non-use | (Non-use) |
+| External Metrics (Note 4) | Use, non-use | (Non-use) |
+| Partition Repair | Optional, use, non-use | (Non-use) |
+| Decision Process: | | |
+| L2 Attached Flag (Note 3) | Optional, use, non-use | (Non-use) |
+| L2 Partition DIS Election (Note 5) | Use, non-use | (Non-use) |
+| L2 Partition Area Addresses | Use, non-use | (Non-use) |
+| Computation (Note 5) | | |
+| L2 DIS Partition Repair (Note 5) | Use, non-use | (Non-use) |
+| Forward/Receive Process | | |
+| L2 NPDU Encapsulation (Note 5) | Use, non-use | (Non-use) |
+| L2 NPDU Decapsulation (Note 5) | Use, non-use | (Non-use) |
+| NOTE 1 – These numbers are preliminary and are subject for study and possible change. | | |
+| NOTE 2 – These functions only apply when the IS is a level 2 IS. | | |
+| NOTE 3 – This function is mandatory when the Level 2 functions are supported. | | |
+| NOTE 4 – This function is mandatory when Reachable Address Prefixes are supported. | | |
+| NOTE 5 – This function is mandatory when the Partition repair function is supported. | | |
+
+**Table 10/Q.811 – Level 2 subnetwork dependent functions**
+
+| Function | Value/Range/Option | Default |
+|-------------------------------------|------------------------|-----------|
+| ISO/IEC 8208 Dynamic Assignment: | | |
+| Call Establishment Metric Increment | Optional, use, non-use | (Non-use) |
+| Reverse Path Cache | Optional, use, non-use | (Non-use) |
+
+**Table 11/Q.811 – IS-IS parameter values and timers**
+
+| Type | Value/Range/Option | Default |
+|-------------------------------------|--------------------|----------|
+| Parameter Values: | | |
+| Default Metric | 1-63 | (20) |
+| Max Path Metric | 1023 | – |
+| Minimum LSP Receive Buffer Size | 1492 octets | – |
+| IS-IS Holding Multiplier | 10 | – |
+| Max Path Splits | 1-32 | (2) |
+| Max Virtual Adjacencies | 0-32 | (2) |
+| Timers: | | |
+| Max Age | 1200 s | – |
+| Zero Age Lifetime | 60 s | – |
+| IS-IS Hello Timer | 0-3 s | (3 s) |
+| Complete SNP Interval Timer | 0-10 s | (10 s) |
+| Max LSP Generation Interval Timer | 0-15 min | (15 min) |
+| Min LSP Generation Interval Timer | 0-30 s | (30 s) |
+| Min LSP Transmission Interval Timer | 0-5 s | (5 s) |
+| Partial SNP Interval Timer | 0-2 s | (2 s) |
+| Poll ES Hello Rate Timer | 0-50 s | (50 s) |
+| Waiting Timer | 0-60 s | (60 s) |
+| Reserve Timer | 2-6 s | (6 s) |
+
+#### 7.3.3.6 IS-IS inter domain routing
+
+Border Intermediate Systems (BISs), using the ISO/IEC 10747 Inter Domain Routing Protocol (IDRP) [48], may be employed for routing ITU-T Rec. X.233 | ISO/IEC 8473-1 CLNP PDUs between Administrative Domains as defined in ITU-T Rec. X.213 | ISO/IEC 8348.
+
+## 7.4 CL-WAN profile (CLNS2)
+
+### 7.4.1 Physical layer profile
+
+#### 7.4.1.1 Service profile
+
+The Physical layer service shall be as defined in ITU-T Rec. X.211 | ISO/IEC 10022 [53].
+
+#### 7.4.1.2 Protocol profile
+
+The protocol of the Physical layer of Protocol Profile CLNS2 shall comply with the following specifications:
+
+- X.21 interface in accordance with 1.1/X.25 [12];
+- X.21 *bis* interface in accordance with 1.2/X.25;
+- V-series interface in accordance with 1.3/X.25.
+
+##### 7.4.1.2.1 Bit rate
+
+The supported bit rates are: 1200, 2400, 4800, 9600, 19 200, and 64 000 bit/s. The bit rates 48 000 bit/s and 56 000 bit/s may be used for an interim period (see Note 1 to Table 18).
+
+#### 7.4.1.3 Connector
+
+Table 12 lists the connectors to be used in accessing the X.21 and X.21 *bis* interfaces. Tables 13, 14, and 15 list respectively the pin descriptions of ISO 2110 [38], ISO/IEC 2593 [39], ISO 4902 [65] and ISO 4903 [66].
+
+**Table 12/Q.811 – X.21/X.21 *bis* connectors**
+
+| Data signalling rate | X.21 bis | X.21 |
+|----------------------|------------------------------|--------------|
+| 2 400 bit/s | ISO 2110 | ISO 4903 |
+| 4 800 bit/s | ISO 2110 | ISO 4903 |
+| 9 600 bit/s | ISO 2110 | ISO 4903 |
+| 19 200 bit/s | ISO 2110 | ISO 4903 |
+| 48 000 bit/s | ISO/IEC 2593
ISO/IEC 4902 | ISO 4903 |
+| 56 000 bit/s | ISO/IEC 2593 | ISO/IEC 2593 |
+| 64 000 bit/s | ISO 4902 | ISO 4903 |
+
+**Table 13/Q.811 – ISO 2110 [38] pin description (see Note 6)**
+
+| Pin | V.24 [35]
circuit | Description | Notes |
+|-----|----------------------|------------------------------------------------|-------|
+| 1 | 101 | Protective ground (Shield) | 1 |
+| 7 | 102 | Signal Ground | 2 |
+| 2 | 103 | Transmitted Data | 2 |
+| 3 | 104 | Received Data | 2 |
+| 4 | 105 | Request to Send | 2 |
+| 5 | 106 | Clear to Send | 2 |
+| 6 | 107 | Data Set Ready (DCE Ready) | 2 |
+| 20 | 108.2 | Data terminal Ready (DTE Ready) | 3 |
+| 22 | 125 | Ring Indicator | 3 |
+| 8 | 109 | Received Line Signal Detector | 2 |
+| 24 | 113 | Transmitter Signal Element Timing (DTE to DCE) | 4 |
+| 15 | 114 | Transmitter Signal Element Timing (DCE to DTE) | 5 |
+
+NOTE 1 – Equipment: removable strap to frame ground or other equivalent grounding arrangement.
+Cable: connected to shield.
+
+NOTE 2 – Basic interchange circuits, all systems.
+
+NOTE 3 – Additional interchange circuits required for switched service.
+
+NOTE 4 – Circuit 113 is not used in OS-MD/NE interfaces.
+
+NOTE 5 – Additional interchange circuits required for synchronous channel.
+
+NOTE 6 – Duplex, interface type D.
+
+NOTE 7 – Circuits are grouped by function: ground, data, control, and timing.
+
+NOTE 8 – For further information see ITU-T Recs V.24 [35], V.28 [36] and ISO 2110 [38].
+
+**Table 14/Q.811 – V.36 [37], ISO/IEC 2593 [39] pin description (see Note 3)**
+
+| Pin | Circuit | Description | Notes |
+|-----|---------|--------------------------------------------------|-------|
+| A | 101 | Protective Ground | 1 |
+| B | 102 | Signal Ground | |
+| P | 103 | Transmitted Data A-wire | 2 |
+| S | 103 | Transmitted Data B-wire | 2 |
+| R | 104 | Received Data A-wire | 2 |
+| T | 104 | Received Data B-wire | 2 |
+| C | 105 | Request to Send | |
+| D | 106 | Ready for Sending | |
+| E | 107 | Data Set Ready | |
+| F | 109 | Data Channel Receive Line Signal Detector | |
+| Y | 114 | Transmitter Signal Element Timing A (DCE to DTE) | 2 |
+| AA | 114 | Transmitter Signal Element Timing B (DCE to DTE) | 2 |
+| V | 115 | Receiver Signal Element Timing A (DCE to DTE) | 2 |
+| X | 115 | Receiver Signal Element Timing B (DCE to DTE) | 2 |
+
+NOTE 1 – Equipment: removable strap to frame ground or other equivalent grounding arrangement.
+Cable: connected to shield.
+
+NOTE 2 – The electrical characteristics of the interchange circuits 103, 104, 114, and 115 shall be balanced double-current, conforming to ITU-T Rec. V.36 [37].
+All other circuits shall conform to ITU-T Rec. V.28 [36].
+
+NOTE 3 – The mode is synchronous at 64 000 bit/s.
+Some countries may use 56 000 bit/s for an interim period of time.
+
+NOTE 4 – Circuits are grouped by function: ground, data, control and timing.
+
+NOTE 5 – For further information, see ITU-T Recs V.36 [37], V.24 [35], V.28 [36] and ISO/IEC 2593 [39].
+
+**Table 15/Q.811 – ISO 4903 [66] pin description (see Note 2)**
+
+| Pin | X.21 circuit | Description | Notes |
+|-----|--------------|--------------------------------|-------|
+| 1 | – | Protective ground | 1 |
+| 8 | G | Signal ground or common return | |
+| 2 | T | Transmit A-wire | |
+| 9 | T | Transmit B-wire | |
+| 4 | R | Receive A-wire | |
+| 11 | R | Receive B-wire | |
+| 3 | C | Control A-wire | |
+| 10 | C | Control B-wire | |
+| 5 | I | Indication A-wire | |
+| 12 | I | Indication B-wire | |
+| 6 | S | Signal element timing A-wire | |
+| 13 | S | Signal element timing B-wire | |
+
+NOTE 1 – Equipment: removable strap to frame ground or other equivalent grounding arrangement.
+Cable: connected to shield.
+
+NOTE 2 – Circuits are grouped by functions: ground, data, control and timing.
+
+NOTE 3 – For further information: see ITU-T Recs V.10/X.26 [67], V.11/X.27 [68], X.21 and ISO 4903.
+
+### **7.4.2 Data link layer profile**
+
+It is mandatory that the Data Link layer conforms to LAPB as defined in ITU-T Rec. X.25 [12]. In addition, provision shall be made for connection between Data Terminal Equipment without an intervening packet switched network. The interface shall conform to ISO/IEC 7776 [13].
+
+#### **7.4.2.1 Service profile**
+
+The Data Link layer service shall be as defined in ITU-T Rec. X.212 | ISO/IEC 8886 [60].
+
+#### **7.4.2.2 Protocol profile**
+
+##### **7.4.2.2.1 Equipment type during link set-up and reset**
+
+When a packet switched network is used to connect systems, they are each designated "Data Terminal Equipment" (DTE) and the network acts as a "Data Circuit-terminating Equipment" (DCE). When a dedicated or dial-up link is provided, other means must be used to supply the DCE role.
+
+At the Physical layer the modems will provide the DCE interface, supplying bit synchronization.
+
+At the link level, the procedures specified in ISO/IEC 7776 [13] shall be followed. A system must be able to start the set-up or reset of the link (a DCE function in ITU-T Rec. X.25 [12]). In addition, provision must be made for assignments of the A/B addresses. This mandatory option is to be field-settable and stored in non-volatile memory. Equipment which meets this requirement is compatible with connection to either a DCE or remote DTE.
+
+##### **7.4.2.2.2 Window**
+
+Support of modulo 8 is mandatory. The window for unacknowledged frames is to be optional between 1 and 7 frames and 1 to 127 with modulo 128. The standard default is 7. For efficient operation over satellite links modulo 128 operation is required, with a default window size of 35.
+
+##### **7.4.2.2.3 User information**
+
+The user information is to be arranged in an integral number of octets.
+
+The maximum length of the user information shall be user settable, consistent with the range of values for the N1 parameter as shown in Table 16. Maximum information field lengths that shall be supported are 131 and 259 octets with 515, 1027, 2051, and 4099 octets optional. These values provide for three packet header octets and maximum length of User Data Field of 128, 256, 512, 1024, 2048, and 4096 octets, respectively.
+
+##### **7.4.2.2.4 Other frame parameters**
+
+Certain other frame parameters shall be set by the user to be consistent with the bit rate, frame size and characteristics of the connecting network. A system design should be sufficiently flexible to accommodate parameter sets for diverse networks, both as order options and later reconfigurations. The range of parameters is shown in Table 16. These options, like those of the Physical layer, are to be set at installation, changeable by the user, and non-volatile.
+
+**Table 16/Q.811 – LAPB Protocol – Octet aligned – Single Link Procedure (SLP) – LAPB data link layer attributes**
+
+| Parameter | Function | Range | Default |
+|-----------|------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|
+| K | I-Frames Window | 1 to 7 (with Modulo 8)
1 to 127 (with optional Modulo 128)
1 to 127 (Modulo 128 with satellite operations) | (7)
(7)
(35) |
+| T1 | Waiting Acknowledgment (Retry) timer a)
For up to 9600 bit/s
For 56 000 bit/s | 2 to 20 seconds
0.2 to 20 seconds | (3)
(3) |
+| T2 | Response delay par a) | Not greater than 0.3 seconds | |
+| T3 | Disconnect Timer | T3 >> T4 b) | |
+| T4 | No activity Timer | 4 to 120 seconds | (20) |
+| N1 | Bits per I-Frame, excluding flags and zero bit insertion for transparency c) | 1080, 2104 (with Modulo 8)
optional: 4152, 8248, 16440, 32824 (with Modulo 8) d)
1096, 2120 (with Modulo 128)
optional: 4168, 8264, 16456, 32840 (with Modulo 128) d) | (2104)
(2120) |
+| N2 | Retransmission Count | 2 to 16 | (7) |
+| A/B | Address Assignment | Selectable by the user | |
+
+a) Further guidelines on the use of T1 and T2 can be found in ITU-T Rec. X.25 [12] and ISO/IEC 7776 [13]. The Transport layer T1 timer should always be greater than the link layer T1 timer.
+
+b) The value of timer T3, the disconnect timer, is not critical for successful interworking of OSs and NEs. Therefore no value is specified.
+
+c) In some cases, users may need to choose a maximum information field length of 259 octets (N1 = 2104 for Modulo 8 or N1 = 2120 for Modulo 128) with a 128 octets packet data unit in order to accommodate call request packets containing 128 octets user data fields in addition to the packet header and facility fields. These values are based on Modulo 8 or Modulo 128 operation at both link and packet layer.
+
+d) Optional.
+
+The default values shall be part of a vendor's offering. That is, unless otherwise specified by the user, the default parameters shall be the initial values supplied. They can be subsequently changed by the user within the specified range.
+
+### 7.4.3 Network layer profile
+
+#### 7.4.3.1 Service profile
+
+The connectionless-mode Network layer service shall be as specified in ITU-T Rec. X.213 | ISO/IEC 8348.
+
+#### 7.4.3.2 Protocol profiles
+
+The protocols for the Network layer shall be identical to the Network layer protocol of Protocol Profile CONS1 (see 7.8) with the inclusion of ITU-T Rec. X.233 | ISO/IEC 8473-1 [7] as specified in clause 4 of ISO/IEC 8880-3 [14], to provide the connectionless-mode Network service over the connection-mode Network service.
+
+For those instances of communication requiring interworking between a connection-mode service (CONS) and a connectionless-mode service (CLNS), ITU-T Rec. X.200 | ISO/IEC 7498-1 [3] and
+
+ISO 8648 [15] provide an OSI compatible interworking capability. This capability is known as a Network Layer Relay (NLR) and utilizes the ITU-T Rec. X.233 | ISO/IEC 8473-1 [7] protocol to provide this service.
+
+#### **7.4.3.3 Network layer attributes**
+
+Characteristics of the connectionless-mode Network layer service, and the connectionless-mode Network layer protocol shall be as shown in Table 2.
+
+## **7.5 ISDN protocol profile (CLNS3)**
+
+### **7.5.1 ISDN protocol profile for connectionless-mode network service**
+
+This clause defines a Protocol Profile for operation of ITU-T Rec. X.224 | ISO/IEC 8073 [42] Transport layer protocol over ITU-T Rec. X.233 | ISO/IEC 8473-1 [7] CLNP over ISDN circuit switched B-channels. This profile is based on the Subnetwork Dependent Convergence Function (SND CF) defined in ITU-T Rec. X.625 | ISO/IEC 8473-5 [11].
+
+### **7.5.2 Network layer**
+
+#### **7.5.2.1 B-channel**
+
+Requirements for the topmost sub-layer (ITU-T Rec. X.233 | ISO/IEC 8473-1) of the Network layer in the B-channel are identical with those defined in 7.3.3 (and its subclauses) for the CLNS1 and CLNS2 Protocol Profile cases.
+
+##### **7.5.2.1.1 Subnetwork dependent convergence function**
+
+On the B-channel a connection may be provisioned to provide either an OSI Data Link service, or an X.25 packet service.
+
+###### **7.5.2.1.1.1 B-channel OSI data link service**
+
+For B-channels providing the OSI Data Link service defined in ITU-T Rec. X.212 | ISO/IEC 8886 [60], the SND CF shall be as defined in ITU-T Rec. X.623 | ISO/IEC 8473-4 [10] and ITU-T Rec. X.625 | ISO/IEC 8473-5.
+
+###### **7.5.2.1.1.2 B-Channel X.25 packet service**
+
+For B-channels providing the X.25 packet service defined in ISO/IEC 8208 [16], the SND CF shall be as defined in ITU-T Rec. X.622 | ISO/IEC 8473-3 [9] and ITU-T Rec. X.625 | ISO/IEC 8473-5.
+
+#### **7.5.2.2 D-channel**
+
+ITU-T Rec. Q.931 [61] shall be used over the D-channel for the purpose of ISDN connection establishment.
+
+### **7.5.3 Data link layer**
+
+#### **7.5.3.1 B-channel**
+
+ISO/IEC 7776 [13], used in accordance with ITU-T Rec. X.273 | ISO/IEC 11577 [58], shall be used in the B-channel.
+
+#### **7.5.3.2 D-channel**
+
+ITU-T Rec. Q.921 [24] shall be used in the D-channel.
+
+### **7.5.4 Physical layer**
+
+Either ITU-T Rec. I.430 [22] (basic rate) or ITU-T Rec. I.431 [23] (primary rate) shall be used in the Physical layer.
+
+## 7.6 IP protocol profiles
+
+This clause defines additional protocol profiles for use as TMN lower layer protocols. These profiles are based on the use of Internet Protocols defined by the Internet Engineering Task Force (IETF). The way these documents can be referenced in this Recommendation is for further study. The protocol stack is shown in Figure 3 and uses the following.
+
+The functions to be supported by the DCF within a TMN entity operating as a router shall meet the requirements specified in 7.1.6/G.7712/Y.1703 [73] sections for Network Layer PDU forwarding function and 7.1.10/G.7712/Y.1703 for Network Layer Routing Function.
+
+### 7.6.1 IPv4 profile
+
+- For Layer 3 – STD0005 "Internet Protocol", September 1981. (Includes RFC 791, RFC 950, RFC 919, RFC 922, RFC 792, RFC 1112.)
+- The lower layers are defined in the Ethernet Profile.
+
+### 7.6.2 IPv4 with IPSec profile
+
+This profile defines an additional option of this protocol profile for use as TMN lower layer protocols. This profile is based on the use of Secure Internet Protocols [69] defined by the Internet Engineering Task Force (IETF). IPSec uses two protocols to provide traffic security – Authentication Header (AH) [71] and Encapsulating Security Payload (ESP) [72]. Each protocol supports two modes of use: transport mode and tunnel mode.
+
+Support of ESP is mandatory. Support of AH is optional. Both transport mode and tunnel mode must be supported for each protocol.
+
+Lower layers are defined in the Ethernet Profile.
+
+### 7.6.3 IPv6 profile
+
+- For Layer 3 – RFC 2460 "Internet Protocol, Version 6 (IPv6) Specification" [70].
+- The lower layers are specified in the Ethernet Profile.
+
+Note that it is mandatory to implement IPSec with IPv6.
+
+
+
+The diagram illustrates the protocol stacks for different IP profiles. At the top, a single box labeled "Upper layers See ITU-T Rec. Q.812" is connected to two separate paths. The left path descends through a dashed box labeled "IPSec RFC 2401" to a box labeled "IPv4". The right path descends through a box labeled "IPv6" which contains a smaller box labeled "IPSec". Both the "IPv4" box and the "IPv6" box are connected to a single, wide box at the bottom labeled "Ethernet". The label "Q.811\_F03" is located at the bottom right of the diagram.
+
+Diagram of IP profiles showing protocol stacks for IPv4 and IPv6 over Ethernet.
+
+**Figure 3/Q.811 – IP profiles**
+
+## **7.7 Ethernet profile**
+
+When the DCF within the TMN entities supports Ethernet interfaces, the following functions are required to support Ethernet Physical Layer Termination Function and [Network Layer PDU into Ethernet Frame] Encapsulation Function.
+
+### **7.7.1 Ethernet physical termination function**
+
+An Ethernet Physical Termination Function terminates the physical Ethernet interface.
+
+One or more of the following rates shall be supported: 1 Mbit/s, 10 Mbit/s, 100 Mbit/s.
+
+### **7.7.2 [Network Layer PDU into Ethernet Frame] encapsulation function**
+
+This function encapsulates and unencapsulates a Network Layer PDU into an 802.3 or Ethernet (version 2) frame.
+
+It shall encapsulate Network Layer PDUs into 802.3 or Ethernet (version 2) frames according to the following rules:
+
+- It shall encapsulate and unencapsulate CLNP, ISIS, and ESIS PDUs into 802.3.
+- It shall encapsulate and unencapsulate IP packets into Ethernet (version 2) frames as per RFC 894 [76].
+- IP addresses shall be mapped to Ethernet MAC addresses utilizing the Address Resolution Protocol in RFC 826 [77].
+
+It shall determine the received frame type (802.3 or Ethernet version 2) as per section 2.3.3 in RFC 1122 [74].
+
+## **7.8 X.25/LAPB protocol profile (CONS1)**
+
+### **7.8.1 Physical layer profile**
+
+See 7.3.1.
+
+### **7.8.2 Data link layer profile**
+
+See 7.3.2.
+
+### **7.8.3 Network layer profile**
+
+It is mandatory that the packet layer conforms to ITU-T Rec. X.25 [12]. In addition, the packet layer must provide for connection of data terminal equipments without an intervening packet network; the required interface for this purpose conforms to ISO/IEC 8208 [16]. In addition, the provisions of ISO/IEC 8878 [26] and ITU-T Rec. X.223 [17] shall apply.
+
+The attributes which must be supported are summarized in Tables 17 and 18. Note in particular that these tables show the different attributes needed to support PVCs [the X.25 Permanent Virtual Circuit (PVC) procedures] and Switched Virtual Circuits (SVCs) (the X.25/SVC procedures).
+
+**Table 17/Q.811 – X.25 [12] packet layer attributes for permanent virtual circuits**
+
+| Feature | Range | Default |
+|------------------------------------|--------------------------------------------|---------|
+| Extended Packet Sequence Numbering | Modulo 128 optional | |
+| Packet size (octets) | 128, 256
512, 1024, 2048, 4096 optional | (128) |
+| Window size | 1-7 (with Modulo 8) | (2) |
+| Extended Sequence Number option | 1-127 (with optional Modulo 128) | (2) |
+| Interrupt packets | Optional | |
+
+NOTE 1 – The default values shall be part of a vendor's offering. That is, unless otherwise specified by the user, the default parameters shall be the initial values supplied. They can be subsequently changed by the user within the specified range.
+
+NOTE 2 – The attributes which are not marked optional are mandatory.
+
+NOTE 3 – The ranges specified for negotiated parameters in no way affect the normal negotiation rules specified in the International Standards.
+
+**Table 18/Q.811 – X.25 [12] packet layer attributes for switched virtual circuits**
+
+| Feature | Range | Default |
+|----------------------------------------------|------------------------------------|------------|
+| Flow Control Parameter | 128, 256 | 128 |
+| Packet size (octets) | 512 optional | |
+| Window size | 1-7 (with Modulo 8) | 2 |
+| Extended Sequence Number Option | 1-127 (with optional Modulo 128) | 2 (Note 5) |
+| Throughput Class (Note 1) | 1200, 2400, 4800, 9600, 19 200 and | 2400 |
+| Bit rate (bit/s) | 64 000 | |
+| Expedited Data Negotiation | | |
+| Closed User Group | | |
+| Closed User Group Selection | | |
+| Basic Format | 2 decimal digits | |
+| Bilateral Closed User Group Selection | Optional | |
+| Fast Select | 128 octets | |
+| Fast Select Acceptance | | |
+| Hunt Group | Optional | |
+| Transit Delay Selection and Indication | | |
+| Calling Address Extension | | |
+| Called Address Extension | | |
+| Minimum Throughput Class Negotiation | | |
+| End-to-End Transit Delay Negotiation | | |
+
+**Table 18/Q.811 – X.25 [12] packet layer attributes for switched virtual circuits**
+
+NOTE 1 – Some countries may use 56 000 bit/s for an interim period of time. In addition to the codes specified in the table in 7.3.2.2/X.25, 56 000 bit/s shall be encoded as binary 1 100. 48 000 bit/s is encoded as binary 1 100 in that table, but when 56 000 bit/s is supported, the code shall stand for 56 000 bit/s.
+
+NOTE 2 – The default values shall be part of a vendor's offering. That is, unless otherwise specified by the user, the default parameters shall be the initial values supplied. They can be subsequently changed by the user within the specified range.
+
+NOTE 3 – The attributes which are not marked optional are mandatory.
+
+NOTE 4 – The ranges specified for negotiated parameters in no way affect the normal negotiation rules specified in the International Standards.
+
+NOTE 5 – The default window size for satellite operations is 35.
+
+#### **7.8.3.1 Numbering plans**
+
+To support communications over public networks, public numbering plans may be used on the packet-switched network between OSs and MDs/QAs/NEs. The 1988 versions of ITU-T Recs E.164 [18] and X.121 [19] specify public numbering plans. Equipment may be assigned numbers in accordance with either of these international Recommendations. The escape code values of "0" and "9" shall be supported as specified in Table 2/X.121. Where a public numbering plan is not necessary, a private numbering plan may be used.
+
+Network layer addressing as specified in ITU-T Rec. X.213 | ISO/IEC 8348 [6] shall be supported.
+
+Additional numbering plans, such as ITU-T Rec. Q.708 for SS7 [57], may be supported in the future as the evolution of new subnetwork technologies require.
+
+##### **7.8.3.1.1 CLNP (ITU-T Rec. X.233 | ISO/IEC 8473-1) communication**
+
+When an instance of data communications involves use of the ITU-T Rec. X.233 | ISO/IEC 8473-1 CLNP, a Network Service Access Point (NSAP) address scheme shall be used. For examples of possible NSAP structures, refer to Annex B.
+
+#### **7.8.3.2 Services profile**
+
+##### **7.8.3.2.1 Expedited data negotiation**
+
+The initiator shall be capable of proposing the non-use of the expedited data service. Responders shall be capable of receiving requests for the expedited data service, but shall be capable of responding with non-use of the service. The expedited data service is neither required nor precluded by this Recommendation.
+
+##### **7.8.3.2.2 Receipt confirmation negotiation**
+
+The initiator shall be capable of setting bit 7 of the General Format Identifier to 0. Responders shall be capable of receiving bit 7 set to 1, but shall be capable of responding with bit 7 set to 0. The Receipt Confirmation Service is neither required nor precluded by this Recommendation.
+
+##### **7.8.3.2.3 Throughput class**
+
+When the end system requires only one Network layer connection on a physical access port, support of throughput classes up to the access line transmission rate is required. When multiple Network layer connections are required, support of the throughput class equal to the access line transmission rate is optional. Further study of Throughput Class range and default values at various access line rates is needed.
+
+##### **7.8.3.2.4 Packet size negotiation**
+
+Interoperability is achieved by having the initiator propose a packet size from the set specified in Tables 17 and 18 and by the responder selecting the most appropriate packet size between 128 and the proposed packet size. The rules for negotiation of the size of the packet to be used in a given instance of communication are specified in ISO/IEC 8208 [16].
+
+The choice of packet size is a local issue which can depend on, for example, the overall Quality of Service requested or needed by the user or Application Layer, and the subnetwork characteristics.
+
+#### **7.8.3.3 Protocol profile**
+
+##### **7.8.3.3.1 Equipment type during restart**
+
+When the packet level X.25 interface is used, automatic selection of the DCE/DTE role during restart is required, as specified in ISO/IEC 8208 [16].
+
+##### **7.8.3.3.2 Other features and parameters**
+
+The packet layer attributes are summarized in Tables 17 and 18.
+
+##### **7.8.3.3.3 User data field**
+
+When layers above X.25 are used, the initial octets of (N)-DATA primitive and the corresponding user data field are used for peer-to-peer protocol data for those layers.
+
+In following the procedures of ITU-T Rec. X.244 [20], ISO/IEC TR 9577 [21], and Annex B of ITU-T Rec. X.224 | ISO/IEC 8073 [42], the initial octets of the user data field of the call request packet may only be used for protocol identification. For those cases in which the fast select feature is used, the call request packet may contain a call user data field of up to 128 octets.
+
+## **7.9 Packet mode bearer service on the D-channel (CONS2)**
+
+### **7.9.1 Physical layer profile**
+
+The Physical layer conforms to ITU-T Recs I.430 [22] for basic rate access and I.431 [23] for primary rate access.
+
+### **7.9.2 Link layer C-plane profile**
+
+The link layer C-plane conforms to ITU-T Rec. Q.921 [24] with the default parameters specified for links within the SAP identified by SAPI = 0.
+
+### **7.9.3 Network layer C-plane profile**
+
+The Network layer C-plane conforms to ITU-T Rec. Q.931 [61]. Q.931 procedures are used as described in ITU-T Rec. X.31 [25] with encodings for information elements according to ITU-T Rec. X.31.
+
+### **7.9.4 Link layer U-plane profile**
+
+The link layer U-plane profile conforms to ITU-T Rec. Q.921 [24] with the default parameters specified for links within the SAP identified by SAPI = 16.
+
+### **7.9.5 Network layer U-plane profile**
+
+The Network layer U-plane conforms to International Standard ISO/IEC 8208 for DTE-DCE operation. The throughput class corresponds to the access-line bit rate of the D-channel which is 16 kbit/s. The Network layer attributes are specified in Table 18.
+
+### **7.9.6 Provision of OSI-CONS**
+
+ITU-T Rec. X.612 | ISO/IEC 9574 [40] provides the connection-mode Network service to packet mode terminal equipment connected to ISDN.
+
+## **7.10 Packet mode bearer service on the B-channel (CONS3)**
+
+### **7.10.1 Physical layer profile**
+
+The Physical layer conforms to ITU-T Recs I.430 [22] for basic rate access and I.431 [23] for primary rate access.
+
+### **7.10.2 Link layer C-plane profile**
+
+The link layer C-plane conforms to ITU-T Rec. Q.921 with the default parameters specified for links within the SAP identified by SAPI = 0.
+
+### **7.10.3 Network layer C-plane profile**
+
+The Network layer C-plane conforms to ITU-T Rec. Q.931. Q.931 procedures are used as described in ITU-T Rec. X.31 with encodings for information elements according to ITU-T Rec. X.31.
+
+### **7.10.4 Link layer U-plane profile**
+
+The link layer U-plane conforms to International Standard ISO/IEC 7776 for Single Link Procedures (SLPs) in DTE-DCE operation. The link layer attributes are specified in Table 16.
+
+### **7.10.5 Network layer U-plane profile**
+
+The Network layer U-plane conforms to International Standard ISO/IEC 8208 for DTE-DCE operation. The throughput class corresponds to the access-line bit rate of the B-channel which is 64 kbit/s. The Network layer attributes are specified in Table 18.
+
+### **7.10.6 Provision of OSI-CONS**
+
+ITU-T Rec. X.612 | ISO/IEC 9574 [40] provides the connection-mode Network service to packet mode terminal equipment connected to ISDN.
+
+## **7.11 Signalling System No. 7 networks (CONS5)**
+
+- Layer 1 conforms to MTP (Level 1) [27].
+- Layer 2 conforms to MTP (Level 2) [28].
+- Layer 3 conforms to MTP (Level 3) [29] and SCCP [30] to [34].
+
+NOTE – Further study is needed for the function of SCCP at the boundary of Network layer and Transport layer.
+
+- Layer 4 – OSI Transport layer per ITU-T Rec. X.214 | ISO/IEC 8072 [41] and ITU-T Rec. X.224 | ISO/IEC 8073 [42].
+
+## **7.12 Connection oriented LAN (CONS6)**
+
+### **7.12.1 Physical layer profile**
+
+See 7.3.1.
+
+### **7.12.2 Data link layer profile**
+
+See 7.3.2, and *replace* "Type 1" by "Type 2".
+
+### **7.12.3 Network layer profile**
+
+For further study.
+
+## 7.13 Conformance requirements
+
+This clause specifies the conformance requirements for each profile by reference to its equivalent ISP (when it exists).
+
+The default values shall be part of a vendor's offering. That is, unless otherwise specified by the user, the default parameters shall be the initial values supplied. They can be subsequently changed by the user within the specified range.
+
+The attributes that are not marked optional are mandatory. See Table 19.
+
+**Table 19/Q.811 – Summary of ISP-based protocol profile conformance requirements**
+
+| Protocol profile | Protocol layer | Requirements | Q.811 references | |
+|------------------|-------------------------------------|---------------------------------------------------------------------------------------------------------|--------------------------------|-------------------------------------------------------|
+| | | | Clause/Figure | Table |
+| CONS1 | | | 4.1, Figure 1, 7.8, 7.13.3 | Table 20 |
+| | Network
ISO/IEC 8208
X.25 PLP | ISO/IEC ISP 10609-9 [45]
Subnetwork Dependent Requirements (TB1111/TB1121) as modified by Table I.1. | 7.8.3 and subclauses | Tables 17, 18 and I.1 |
+| CONS1 | Data Link | ISO/IEC ISP 10609-9 Subnetwork Dependent Requirements (TB1111/TB1121) as modified by Table I.2. | 7.8.2 (7.4.2) | Tables 16 and I.2 |
+| | Physical | ISO/IEC ISP 10609-9 Subnetwork Dependent Requirements (TB1111/TB1121). | 7.8.1 (7.4.1 and subclauses) | Tables 12, 13, 14 and 15 |
+| CLNS1 | | | 4.3, Figure 2, 7.3, 7.13.1 | Table 20 |
+| | Network
ISO/IEC 8473 CLNP | ISO/IEC ISP 10608-1 Subnetwork Independent Requirements as modified by Table I.4. | 7.3.3 | Table 2, Tables 3 to 11 (where applicable), Table I.4 |
+| | Data Link | ISO/IEC ISP 10608-2 (TA51) [44]. | 7.3.2 | |
+| | Physical | ISO/IEC ISP 10608-2 (TA51). | 7.3.1 | Table 1 |
+| CLNS2 | | | 4.4, Figure 2, 7.4, 7.13.2 | Table 20 |
+| | Network
ISO/IEC 8473 CLNP | ISO/IEC ISP 10608-1 Subnetwork Independent Requirements as modified by Table I.4. | 7.4.3, 7.4.3.2, 7.4.3.3 | Table 2, Tables 3 to 11 (where applicable) |
+| | Network
ISO/IEC 8208 X.25 PLP | ISO/IEC ISP 10608-5 (TA1111/TA1121) as modified by Tables I.1 and I.3. | 7.4.3.2 (7.8.3 and subclauses) | Tables I.1 and I.3 |
+| | Data Link | ISO/IEC ISP 10608-5 (TA1111/TA1121) as modified by Table I.2. | 7.4.2 | Tables 16 and I.2 |
+| | Physical | ISO/IEC ISP 10608-5 (TA1111/TA1121). | 7.4.1 | Tables 12, 13, 14 and 15 |
+| CLNS1/ | Network | ISO/IEC ISP 10613-7, 10613-8, | | |
+
+**Table 19/Q.811 – Summary of ISP-based protocol profile conformance requirements**
+
+| Protocol profile | Protocol layer | Requirements | Q.811 references | |
+|--------------------|----------------|-----------------------------------------------------------------------------------------------------------------------|------------------|-------|
+| | | | Clause/Figure | Table |
+| CLNS2
Int'work | | 10613-9 (RA51.11x1). | | |
+| IPv4 | Network | STD0005 "Internet Protocol", J. September 1981. (Includes RFC 791, RFC 950, RFC 919, RFC 922, RFC 792, RFC 1112.) | 7.6.1 | |
+| IPv4 with
IPSec | Network | RFC 2401 (1998) "Security Architecture for the Internet Protocol" with additional required specified in section 7.6.2 | 7.6.2 | |
+| IPv6 | Network | RFC 2460 "Internet Protocol, Version 6 (IPv6) Specification" [70] | 7.6.3 | |
+| Ethernet | Data Link | RFC 1122 | – | |
+
+### 7.13.1 CL-LAN profile (CLNS1)
+
+Network layers shall conform to ISO/IEC ISP 10608, Part 1, as modified by Table I.4. Physical and Data link layers shall conform to ISO/IEC ISP 10608, Part 2 (TA51).
+
+### 7.13.2 CL-WAN profile (CLNS2)
+
+Network (CLNP) layers shall conform to ISO/IEC ISP 10608, Part 1, as modified by Table I.4. Packet layer shall conform to ISO/IEC ISP 10608-5 as modified by Tables I.1 and I.3. Physical and Data link layers shall conform to ISO/IEC ISP 10608, Part 5 (TA1111/TA1121).
+
+### 7.13.3 X.25/LAPB profile (CONS1)
+
+Packet layer shall conform to ISO/IEC ISP 10609-9, as modified by Table I.1. Data link and Physical layer profiles shall conform to ISO/IEC ISP 10609-9 (TB1111/TB1121), as modified by Table I.2.
+
+### 7.13.4 Connection oriented LAN (CONS6)
+
+Network shall conform to ISO/IEC ISP 10609-9.
+
+Data link (LLC and MAC) and Physical layers shall conform to ISO/IEC ISP 10609-10.
+
+# 8 Network layer service
+
+## 8.1 Network layer profiles
+
+The following subclauses will describe three ways in which the lower three layers of the Protocol Profiles may be viewed as transparent to the Transport (layer 4) and the upper layers (5, 6 and 7).
+
+NOTE – Table 10/Q.811 (1993), **Homogeneous lower layer protocol profiles**, has been deleted.
+
+### 8.1.1 Existing lower layer profiles
+
+The group of subnetworks described in clause 7 have been chosen so that the services provided by the respective Network layer protocols will ensure operation of the OSI Transport protocol. The services of the Transport layer, in turn, are those required for operation of the higher OSI layers (i.e., layers five to seven).
+
+### **8.1.2 Network layer service description for new subnetworks**
+
+On a forward going basis, any subnetwork developed must meet the criteria provided for the Network layer service as viewed by the Transport layer. There are two services provided by the Network layer, the Connection-mode Network layer Service (CONS), and the Connectionless-mode Network layer Service (CLNS).
+
+These services are described in ITU-T Rec. X.213 | ISO/IEC 8348.
+
+### **8.1.3 Non-conforming Network layer profile**
+
+For a subnetwork which does not, by itself, provide the CLNS, the addition of ITU-T Rec. X.233 | ISO/IEC 8473-1 with the proper choice of SNDPCP will provide a combination that will meet the Network layer service description.
+
+Subnetwork Dependent Convergence Protocols (SNDPCPs) are described for the use of ITU-T Rec. X.233 | ISO/IEC 8473-1 over ISO/IEC 8208/X.25 networks, ISO/IEC 8802-2 subnetworks [5], subnetworks that provide the OSI Data Link service [10], and ISDN circuit-switched B-channels [11].
+
+### **8.1.4 Security**
+
+ITU-T Rec. X.273 | ISO/IEC 11577 [58] specifies security features for the OSI Network layer, and some security capabilities are available in the Network layer protocols [e.g., mandatory Closed User Groups (CUGs) and optional bilateral CUGs in the X.25 packet protocol].
+
+## **8.2 Internetworking**
+
+This clause describes the technical principles for interworking between DCNs within a TMN, and between TMNs using different protocol stacks. In some cases interworking units have to be supplied between the different DCNs. It is the responsibility of the two TMN Administrations to determine which Administration shall provide the IWU. This interworking procedure is known as Network Layer Relay (NLR).
+
+When networks of different types, such as connection-mode and connectionless-mode, wish to transfer information across the boundary, internetworking principles are stated in ITU-T Rec. X.200 | ISO/IEC 7498-1 [3] and ISO 8648 [15]. These standards state that internetworking should occur within the Network layer. The Transport layer and higher layers operate on a peer-to-peer basis between the communicating end systems. A family of subnetwork dependent convergence protocols has been developed [8] to [11] that provide for the operation of ITU-T Rec. X.233 | ISO/IEC 8473-1 over different subnetworks. Thus, in the example above, ITU-T Rec. X.233 | ISO/IEC 8473-1 would operate over both the connection-mode subnetworks and over the connectionless-mode subnetworks. The Transport layer, ITU-T Rec. X.224 | ISO/IEC 8073 [42], would provide for operation over both the connection-mode subnetworks and the connectionless-mode subnetworks. In this example, the Transport layer would operate in the Class 4 mode. Thus, the internetworking between dissimilar subnetworks would be achieved and the Transport layer and higher layers of the end systems would operate on a peer-to-peer basis.
+
+There are three basic principles to be followed in adopting interworking solutions between Q/X protocol stacks.
+
+The three principles are:
+
+- 1) interworking should be done in the Network layer;
+- 2) existing standards should be applied for interworking functions; e.g., X.300-series Recommendations should be applied for interworking between certain types of CONS-based networks; and NLR using ITU-T Rec. X.233 | ISO/IEC 8473-1 and associated SNDPCFs should be used for interworking between CLNS-based networks;
+
+- 3) new interworking functions should be specified only if existing standards for interworking cannot meet requirements of new network capabilities.
+
+Definition of the relaying functions of a CONS-CONS Network layer intermediate system is given in ISO/IEC 10028 [56]. How the Network internal layer service is provided for relaying between X.25 packet systems is given in ISO/IEC 10177 [55].
+
+A general guide to interworking between the various Transport profile groups is given in ISO/IEC TR 10000-2 [64].
+
+How relaying is performed between CLNS-based subnetworks is defined in ITU-T Rec. X.233 | ISO/IEC 8473-1 [7].
+
+Table 20 shows Protocol Profiles which are to be applied to a reference point which has interworking, and defines internetworking methods.
+
+NOTE – Table 11/Q.811 (1993), **Internetworking functions for Q lower layers**, has been deleted.
+
+**Table 20/Q.811 – Interworking between protocol profiles**
+
+| Protocol profile | CONS1 X.25 LAPB | CONS2 ISDN X.25 (D) | CONS3 ISDN X.25 (B) | CONS5 SS7 | CONS6 CO-LAN | CLNS1 LAN | CLNS2 WAN | CLNS3 ISDN | ISO TP0/TCP/IP |
+|------------------|-------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------|-----------------|------------|------------|------------|----------------|
+| CONS1 | Rec. X.75 [49] | Rec. I.550/X.325 [50] | Rec. I.550/X.325 [50] | Rec. X.326 [51] | Rec. X.327 [52] | Non-OSI | Non-OSI | Non-OSI | Non-OSI |
+| CONS2 | | OSI (CONS) | OSI (CONS) | OSI (CONS) | OSI (CONS) | Non-OSI | Non-OSI | Non-OSI | Non-OSI |
+| CONS3 | | | OSI (CONS) | OSI (CONS) | OSI (CONS) | Non-OSI | Non-OSI | Non-OSI | Non-OSI |
+| CONS5 | | | | OSI (CONS) | OSI (CONS) | Non-OSI | Non-OSI | Non-OSI | Non-OSI |
+| CONS6 | | | | | OSI (CONS) | Non-OSI | Non-OSI | Non-OSI | Non-OSI |
+| CLNS1 | | | | | | OSI (CLNS) | OSI (CLNS) | OSI (CLNS) | Non-OSI |
+| CLNS2 | | | | | | | OSI (CLNS) | OSI (CLNS) | Non-OSI |
+| CLNS3 | | | | | | | | OSI (CLNS) | Non-OSI |
+| IP | | | | | | | | | See 8.2.1 |
+| Non-OSI | Interworking above the Network layer may be required. | | | | | | | | |
+| OSI | Interworking is either connectionless-mode (CLNS) or connection-mode (CONS) within the Network layer. | | | | | | | | |
+| NLR | Interworking is within the Internet Network layer (i.e., the IP layer). | | | | | | | | |
+
+### 8.2.1 Interworking between TMN entities supporting OSI only with entities supporting IP
+
+Two functions as defined by ITU-T Rec. G.7712/Y.1703 shall be supported by TMN entity when IP is connected to an entity with OSI only for interworking. These are Network Layer PDU interworking and IP Routing Interworking. The PDU interworking is supported using Network Layer PDU Encapsulation function (see 7.1.8/G.7712/Y.1703) and Network Layer PDU tunnelling function (see 7.1.9/G.7712/Y.1703). The IP Routing Interworking function is supported using Integrated IS-IS routing as defined in 7.1.10/G.7712/Y.1703.
+
+# Annex A
+
+## Protocol stack for information transfer over ISDN transparent B-channel
+
+## A.1 Introduction
+
+This annex describes a protocol stack for connection between data terminal equipment without an intervening packet switched network. End systems are making use of the 64 kbit/s unrestricted circuit-mode bearer service offered by an ISDN. The OSI connection-mode service (OSI-CONS) over ISDN transparent B-channel defined in this annex is identified as CONS4 at the Q and X interfaces.
+
+The CONS4 lower layer protocol profile provides for a connection-mode interface using ISDN transparent B-channel.
+
+## A.2 Network profile CONS4
+
+### A.2.1 Physical layer profile
+
+The Physical layer conforms to ITU-T Recs I.430 for basic rate access and I.431 for primary rate access.
+
+### A.2.2 Link layer C-plane profile
+
+The link layer C-plane conforms to ITU-T Rec. Q.921 with the default parameters specified for links within the SAP identified by SAPI = 0.
+
+### A.2.3 Network layer C-plane profile
+
+The Network layer C-plane conforms to ITU-T Rec. Q.931 for circuit-switched call control procedures using codings of information element as in Table A.1.
+
+**Table A.1/Q.811 – Q.931 Information element encodings in support of CONS4**
+
+| | |
+|--------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Bearer Capability (BC) information element codings | |
+| Coding standard (octet 3) | ITU-T |
+| Information transfer capability (octet 3) | Unrestricted digital information |
+| Transfer mode (octet 4) | Circuit mode |
+| Information transfer rate (octet 4) | 64 kbit/s |
+| Called party number information element codings | |
+| Type of number (octet 3) | International/national/subscriber |
+| Numbering plan identification (octet 3) | ISDN/telephony numbering plan (ITU-T Rec. E.164) |
+| Called/calling party subaddress information element codings | |
+| Type of number (octet 3) | NSAP |
+| Low Layer Compatibility (LLC) information element codings | |
+| Coding standard (octet 3) | ITU-T |
+| Information transfer capability (octet 3) | Unrestricted digital information |
+| Transfer mode (octet 4) | Circuit mode |
+| Information transfer rate (octet 4) | 64 kbit/s |
+| User information Layer 1 protocol | Not applicable (omit octet 5) |
+| User information Layer 2 protocol (octet 6) | ISO/IEC 7776 DTE-DTE operation |
+| – Mode of operation (octet 6a) | Normal/extended (selectable by user whereby normal is a mandatory mode while extended is an optional mode) |
+| – Window size (k) (octet 6b) | 1-7 (for modulo 8) (default 7)
1-127 (for modulo 128) (default 7)
1-127 (for modulo 128) (default 35 for satellite operations)
ISO/IEC 8208 DTE-DTE operation |
+| User information layer 3 protocol (octet 7) | Normal (modulo 8)/extended (modulo 128) |
+| – Mode of operation (octet 7a) | 128, 256, 512 octets (default 128) |
+| – Default packet size (octet 7b) | 1-7 (for modulo 8)(default 2) |
+| – Packet window size (k) (octet 7c) | 1-127 (for modulo 128)(default 2) |
+
+### A.2.4 Supplementary services
+
+The supplementary service Sub-addressing (SUB) is required in order to convey the called and calling NSAP address in the called and calling party subaddress information element, respectively. In addition, the supplementary service Closed User Group (CUG) may be used to restrict, in a public Data Communication Network (DCN), access of end systems which are the members of a TMN.
+
+### A.2.5 Link layer U-plane profile
+
+The link layer U-plane conforms to ISO/IEC 7776 for Single Link Procedures (SLPs) in DTE-DTE operation. The link layer attributes are specified in Table 16.
+
+### A.2.6 Network layer U-plane profile
+
+The Network layer U-plane conforms to ISO/IEC 8208 for DTE-DTE operation over circuit-switched connections.
+
+Determining "DTE" or "DCE" characteristics is based on restart procedure:
+
+- a) acts as "DCE" when receiving RESTART INDICATION packet with the restarting cause field "DTE originated" and no restart collision occurred;
+- b) acts as "DTE" when a RESTART REQUEST packet is subsequently confirmed with a RESTART CONFIRMATION packet (no restart collision occurred);
+- c) re-initiates a restart procedure when a randomly-chosen time has elapsed following the detection of a restart collision.
+
+The Network layer attributes specified in Table 18 apply with the additions contained in Table A.2.
+
+**Table A.2/Q.811 – Additional U-plane network layer attributes and parameters in support of CONS4**
+
+| | | |
+|-----|---------------------------------------------------------------------------------------------------|----------------|
+| – | The throughput class corresponds to the access-line bit rate of the B-channel which is 64 kbit/s. | |
+| – | The Network layer parameters which apply are: | |
+| T20 | Restart requires response timer | 180 seconds |
+| T21 | Call request response timer | 200 seconds |
+| T22 | Reset request response timer | 180 seconds |
+| T23 | Clear request response timer | 180 seconds |
+| T24 | Window status transmission timer | Not applicable |
+| T25 | Window rotation timer | Not applicable |
+| T26 | Interrupt response timer | 180 seconds |
+| T27 | Reject response timer | Not applicable |
+| T28 | Registration request response timer | Not applicable |
+| R20 | Restart request retransmission count | 1 |
+| R22 | Reset request retransmission count | 1 |
+| R23 | Clear request retransmission count | 1 |
+| R25 | Data packet retransmission count | Not applicable |
+| R27 | Reject retransmission count | Not applicable |
+| R28 | Registration request retransmission count | Not applicable |
+
+### A.2.7 Provision of OSI-CONS
+
+The Synchronization and Coordination Function (SCF) (see ITU-T Rec. I.320 [62]) provides the connection-mode Network service to the Network service user.
+
+# Annex B
+
+## Examples of NSAP structures for CLNP
+
+This annex summarizes four examples of NSAP structure. Figures B.1, B.2, and B.3 show NSAP structures based on ISO-DCC. Figure B.4 shows an NSAP structure based on ISO-ICD.
+
+| IDP | | DSP | | | |
+|------------------|-----|------|------|--------|-----|
+| AFI | IDI | | | | |
+| 39 | a) | JDI# | AREA | SYSTEM | SEL |
+| Number of octets | 1 | 2 | 3 | n | 6 |
+| | | | | | 1 |
+
+a) ISO DCC (value of 392 as Japan).
+
+# JDI (value of 100009 as NTT)
+
+n Range of value = 1-7
+
+**Figure B.1/Q.811 – DCC type NSAP address format in Japan Standard**
+
+| IDP | | DSP | | | |
+|------------------|-----|-----|------|--------|-----|
+| AFI | IDI | | | | |
+| 39 | a) | ORG | AREA | SYSTEM | SEL |
+| Number of octets | 1 | 2 | 3 | 2 | 0-6 |
+| | | | | | 1 |
+
+a) ISO DCC.
+
+ORG Organization Identifier
+
+AREA Subnetwork Identifier
+
+SYSTEM Subnetwork address
+
+**Figure B.2/Q.811 – ECMA 117 NSAP format**
+
+| IDP | | DSP | | | | | | |
+|------------------|-----|-----|-----|-----|----|------|--------|-----|
+| AFI | IDI | DFI | | | | | | |
+| 39 | a) | 128 | org | res | rd | AREA | SYSTEM | SEL |
+| Number of octets | 1 | 2 | 1 | 3 | 2 | 2 | 2 | 6 |
+| | | | | | | | | 1 |
+
+a) ISO DCC.
+
+DFI The DSP Format Identifier
+
+org Organization Identifier
+
+res Reserved
+
+rd Routing domain prefix
+
+**Figure B.3/Q.811 – ANSI NSAP address format**
+
+| IDP | | DSP | | | |
+|------------------|-----|-----|----|----|-----|
+| AFI | IDI | | | | |
+| 47 | a) | DI | FI | TI | SEL |
+| Number of octets | 1 | 2 | 3 | 1 | 12 |
+
+- a) ISO ICD.
+DI Domain Identifier
+FI Format Identifier
+TI Terminal Identifier
+SEL NSAP selector
+
+**Figure B.4/Q.811 – ICD type NSAP address format for AOTC-Australia**
+
+# Appendix I
+
+## Changes to ISP conformance requirements
+
+The "Identifier", "Feature", and "Status" fields under "Base Reference Standard" refer to the PICS for the particular base standard protocol; whereas the "Clause" field refers to the base protocol specification.
+
+Notation:
+
+### a) *Base standard status notation*
+
+#### 1) Base standard type or range:
+
+- M Mandatory.
+- O Optional.
+- Not applicable.
+- O. Optional, but support of at least one of the group of options labelled by the same numeral is required.
+- : This predicate symbol means that the status following applies only when the PICS states that one or more of the items identified by the index is supported. In the simplest case, is the identifying tag of a single PICS item. may also be a Boolean expression composed of several indices.
+- :: When this group predicate is true the associated clause should be completed.
+
+### b) *Q.811 status notation*
+
+The status column in Tables I.1 to I.4 uses either a one- or two-character notation. The one-character notation indicates the static requirements only. For the two-character notation, the first character is the static requirements and the second character is the dynamic requirements.
+
+#### 1) Static:
+
+- m Mandatory, mandatory to be implemented.
+- i Out of scope. Not relevant to this profile.
+- o Optional, optional to be implemented.
+- & Same as Base Standard.
+
+#### 2) Dynamic:
+
+- m Mandatory (use is mandatory).
+x Excluded (use is prohibited within the context of this profile).
+– Not applicable.
+
+**Table I.1/Q.811 – Network layer**
+
+| Base standard | | | | ISP | ITU-T Rec. Q.811 | |
+|---------------|-------------------------------------------|-----------------------------|------------------------|---------------------|----------------------|------------------|
+| Ident. | Feature | Clause | Status | Status | Clause | Status |
+| Et/d | DTE/DTE with dynamic role selection | 4.5 | Vs: O.2 | oi | 7.8.3.3.1 | mm |
+| M128 | Modulo 128 (extended) | 13.2,
12.1.1,
Table 3 | O.3 | ox | Table 18 | oo |
+| V2s | Default window sizes supported, sending | 16.2.2.6 | M8: 1-7
M128: 1-127 | M8: 1-7
M128: o- | Table 18
Table 18 | M8: 2
M128: 2 |
+| V2r | Default window sizes supported, receiving | 16.2.2.6 | M8: 1-7
M128: 1-127 | M8: 1-7
M128: o- | Table 18
Table 18 | M8: 2
M128: 2 |
+| V10s | Window sizes supported, sending | 15.2.2.1.2 | M128: 1-127 | M128: o- | Table 18 | M128:
1-127 |
+| V10r | Window sizes supported, receiving | 15.2.2.1.2 | M128: 1-127 | M128: o- | Table 18 | M128: 1-1 |
+| T24 | Window Status Transmission Timer | | O | ox | Table 18 | oo |
+| T25 | Window Rotation Timer | | O | ox | Table 18 | oo |
+| FS5
FR5 | Bilateral Closed User Group Selection | 13.15
15.2.2.5 | O | | Table 18 | oo |
+
+**Table I.2/Q.811 – Data link layer**
+
+| Base standard | | | | ISP | ITU-T Rec. Q.811 | |
+|---------------|-------------------------------------------------------|---------------------|--------|--------|------------------|--------|
+| Ident. | Feature | Clause | Status | Status | Clause | Status |
+| I | DTE/DTE Interworking | – | – | oi | 7.4.2.2.1 | m |
+| T2 | Parameter T2 procedure | 5.7.1.2,
5.7.1.1 | O | | Table 16 | m |
+| T3 | Parameter T3 procedure | 5.7.1.3 | O | | Table 16 | m |
+| T4 | Parameter T4 procedure | 5.7.1.4,
5.3.2 | O | | Table 16 | m |
+| SP8 | If Modulo 8 was checked with SLP ( $N1 \geq 1080$ ) | 5.7.3 | M | | Table 16 | m |
+| SP128 | If Modulo 128 was checked with SLP ( $N1 \geq 1088$ ) | | M | | Table 16 | m |
+
+NOTE for Tables I.1 and I.2 – The referenced ISP is ISO/IEC ISP 10609, Parts 1 and 9 (TB1111/TB1121) [45].
+
+**Table I.3/Q.811 – CLNS2 protocol case – Packet layer**
+
+| Base standard | | | | ISP | ITU-T Rec. Q.811 | |
+|---------------|-------------------------------------|--------|---------|--------|------------------|--------|
+| Ident. | Feature | Clause | Status | Status | Clause | Status |
+| Vp | PVC | | O.1 | i | | & |
+| Vs | VC | | O.1 | mm | | & |
+| Et/d | DTE/DTE with dynamic role selection | 4.5 | Vs: O.2 | Vs: i | 7.5.3 | mm |
+
+**Table I.4/Q.811 – CLNS2 and CLNS1 protocol cases –
+ITU-T Rec. X.233 | ISO/IEC 8473-1 CLNP**
+
+| Base standard | | | | ISP | ITU-T Rec. Q.811 | |
+|---------------|-----------------|--------|--------|--------|------------------|--------|
+| Ident. | Feature | Clause | Status | Status | Clause | Status |
+| | QoS Maintenance | 7.5.6 | O | i | Table 2 | mm |
+
+NOTE for Tables I.3 and I.4 – Reference is to ISO/IEC ISP 10608, Parts 1, 2 (TA51), and Part 5 (TA1111/TA1121) [44].
+
+
+
+# SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure, Internet protocol aspects and Next Generation Networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8d00235a076f1609131e033f98fd1119ab992a28
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2bfb93f63c578ecc0a6729240f4cc276e9d726fa70acc1b55abc784ecf98b4cc
+size 52017
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c2b3b13af491f34a9b90a2f686778c628e3205e1
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:69a1196e0b060d8da2bc1de779a2206717243efc04c1674b6c4ef7a2460ce76b
+size 45511
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ea793e9b7af18f434098999683d326bf31556339
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:56cb6f9d8652f70aeab65a9f553c37281f1f2b7858363007925fe7a193049c8a
+size 44907
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/19e2fdfdf050c05ce74925211913c2c3_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/19e2fdfdf050c05ce74925211913c2c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0ad7606b64bfb925e9145a8a44f41ade4a99be7c
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/19e2fdfdf050c05ce74925211913c2c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:059da1c30b9293aaf3fe39fc9c7b39c1201d759b5ae94e73928c2b85c1bb4c0c
+size 33585
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ab2cbdd4af6bc1ea9ffa8cca87f9d455eb147008
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:94ee226724314e8b36ac3c73e99f9ed2a4fbb4786e0c7f3f43c1debd5966aa00
+size 8239
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4ac0faf69bc31ca7e7a2dd110d56abf3a4e37067
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b3d85167f2413a1f2e28909d6ee0b296dfc1133b469868d9bbb7d4dd325e802d
+size 45772
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c8831313bdc47e5b75ee717b1d12384111bd07d5
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:36e022f4a3ede4089297e5060570bb55b955fa2f7d4835d40315b377b970dea0
+size 42504
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/4c731b7bb6a5851992b8b7440b4e9356_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/4c731b7bb6a5851992b8b7440b4e9356_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..095e4b8a0682511fda033800ade87d9de8c2d59a
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/4c731b7bb6a5851992b8b7440b4e9356_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da88bf24724b629e48b6eca3ddd8e835889b827897c047c5a9e96776ac67679a
+size 36518
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fb532694091d819d58b75a204dd26d6ac0e3383e
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6f480037432e09099048ad6c72aa653a5948743339cefe1bf22f2193cfbbdd7e
+size 34586
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9b3667814d1522e58ddc9ad25c002337f7151bc0
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0d3ddff61b64049f55b8a7c9d76d8a6ec15668b352e6dfd9ef69f895dcf4ed56
+size 43210
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/9ed248b025d766251d58be10b01a1cc0_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/9ed248b025d766251d58be10b01a1cc0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..204df87701297bc81c7507e97cabaa6060410938
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/9ed248b025d766251d58be10b01a1cc0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cf59f7bc51b968b7301cdb637d12edc4e694d5d812239f286779afd7f99a24ef
+size 19582
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c4ad530ba08017d848116ee9cbec554ba3d17696
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ec361716ba74f690bb9c8b08db7287e4035e5931f0f0ead33d58d25a3208c40d
+size 46735
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bc87fd534e5b341c6b8545e2cda4b1581316e8b5
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf3842f64d3a052e9918b9b4947f3090104956bb8b95b4eb32d86f9207d28795
+size 43230
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b2f753111f8e156eb1a32b4a7a4b67a50c7f3128
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9ad490e1737dad5bae196df44f68c77bb44fafffa2bc03f04bbb61f3b9c444ce
+size 38982
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2bc1f5c634972f49cdf908fb2e3d79a639e950ad
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c571188d314ff9f630e3d131186d0c6050c594c6f09cac4db1e933b995303024
+size 29111
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fdc03ceccad2acfc4d19c13abb0e1fc954ebdd6c
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3cc038ac9fcb43c41d3185d579c68b5a695b314fa6865dfab1ad87aa3af81ce1
+size 41706
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/c85b57b2414f341860dfc338e1cf2509_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/c85b57b2414f341860dfc338e1cf2509_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0b5e27f8fda6afdba3cefce986a8feaf91e72640
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/c85b57b2414f341860dfc338e1cf2509_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0a91e690da8c9af0c9d1461d5e60eed8b16ab485534c7ac454f7b3aa34c8b83b
+size 38551
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..25508c38158e8094d18f6b4a22047def68577a4b
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:69e9f2cfe023eecd3b9e03d9764f2715bd3d849785c8aabc395ab51891f82946
+size 42368
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0ee0ac64ee6182ba6927720e8d5660e9a73243d5
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3e247f86e491f614bc0b0aeee09b4d90d107e334180ef574718571d234f50ae2
+size 36572
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/ddee3e67e0dfc22e25188fa635a19558_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/ddee3e67e0dfc22e25188fa635a19558_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..13fc103c79ff671660da576bc190798fbc650e70
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/ddee3e67e0dfc22e25188fa635a19558_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1ec35a807652eba884359f168ac786ab71e3cacef07b01a6ec30685dceb82d33
+size 38699
diff --git a/marked/Q/T-REC-Q.821-200002-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/Q/T-REC-Q.821-200002-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a175c912400c2a3b48ee4eee0213c34b552b88a0
--- /dev/null
+++ b/marked/Q/T-REC-Q.821-200002-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1274ab57050aca09103bed7f83d6e6772dbb20db92c8ebf1cc66d2a5dff01d76
+size 83775
diff --git a/marked/Q/T-REC-Q.822-199404-I_PDF-E/raw.md b/marked/Q/T-REC-Q.822-199404-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..47a4eb05f188469145dc01f50f90b405d2cf42a5
--- /dev/null
+++ b/marked/Q/T-REC-Q.822-199404-I_PDF-E/raw.md
@@ -0,0 +1,2644 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**Q.822**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(04/94)
+
+**SPECIFICATIONS OF
+SIGNALLING SYSTEM No.7**
+
+---
+
+**STAGE 1, STAGE 2 AND STAGE 3
+DESCRIPTION FOR THE Q3 INTERFACE –
+PERFORMANCE MANAGEMENT**
+
+**ITU-T Recommendation Q.822**
+
+(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.822 was prepared by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 7th of April 1994.
+
+---
+
+# NOTE
+
+In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+# CONTENTS
+
+*Page*
+
+| | | |
+|----------|----------------------------------------------------------|----|
+| 1 | Scope, purpose, and field of application ..... | 1 |
+| 1.1 | Scope ..... | 1 |
+| 1.2 | Purpose ..... | 1 |
+| 1.3 | Field of application ..... | 1 |
+| 2 | References ..... | 1 |
+| 2.1 | Recommendations referred to in this Recommendation ..... | 1 |
+| 3 | Terms and definitions, abbreviations ..... | 2 |
+| 3.1 | Terms and definitions ..... | 2 |
+| 3.2 | Abbreviations ..... | 3 |
+| 4 | Performance management ..... | 4 |
+| 4.1 | Performance management functions ..... | 4 |
+| 4.1.1 | Performance management data collection functions ..... | 4 |
+| 4.1.2 | Performance management data storage functions ..... | 4 |
+| 4.1.3 | Performance management thresholding functions ..... | 5 |
+| 4.1.4 | Performance management data reporting functions ..... | 5 |
+| 4.2 | Performance management model ..... | 5 |
+| 4.3 | Performance management information ..... | 7 |
+| 4.3.1 | Managed object classes ..... | 7 |
+| 4.3.1.1 | Current data ..... | 9 |
+| 4.3.1.2 | History data ..... | 10 |
+| 4.3.1.3 | Threshold data ..... | 10 |
+| 4.3.2 | Package definitions ..... | 11 |
+| 4.3.2.1 | Counter threshold list package ..... | 11 |
+| 4.3.2.2 | Filter suppression package ..... | 11 |
+| 4.3.2.3 | Gauge threshold list package ..... | 11 |
+| 4.3.2.4 | History data measurement list package ..... | 12 |
+| 4.3.2.5 | History data suspect interval flag package ..... | 12 |
+| 4.3.2.6 | History retention package ..... | 12 |
+| 4.3.2.7 | Maximum number of suppressed intervals package ..... | 12 |
+| 4.3.2.8 | Measurement list package ..... | 13 |
+| 4.3.2.9 | Number of suppressed intervals package ..... | 13 |
+| 4.3.2.10 | Object delete notification package ..... | 13 |
+| 4.3.2.11 | Observed managed object package ..... | 13 |
+| 4.3.2.12 | Scheduled performance monitoring report package ..... | 14 |
+| 4.3.2.13 | Threshold package ..... | 14 |
+| 4.3.2.14 | Threshold verification package ..... | 15 |
+| 4.3.2.15 | Zero suppression package ..... | 16 |
+| 4.3.3 | Attribute definitions ..... | 16 |
+| 4.3.3.1 | Counter threshold attribute list ..... | 16 |
+| 4.3.3.2 | Elapsed time ..... | 16 |
+| 4.3.3.3 | Gauge threshold attribute list ..... | 16 |
+| 4.3.3.4 | History data Id ..... | 17 |
+| 4.3.3.5 | History retention ..... | 17 |
+
+| | Page |
+|-----------------------------------------------------------------------------------|-------------|
+| 4.3.3.6 Maximum suppressed intervals..... | 17 |
+| 4.3.3.7 Measurement list..... | 18 |
+| 4.3.3.8 Monitored entity types ..... | 18 |
+| 4.3.3.9 Number of suppressed intervals..... | 18 |
+| 4.3.3.10 Observed object class..... | 18 |
+| 4.3.3.11 Report all attributes..... | 18 |
+| 4.3.3.12 Period end time ..... | 19 |
+| 4.3.3.13 Suppress additional thresholds..... | 19 |
+| 4.3.3.14 Suspect interval flag..... | 19 |
+| 4.3.3.15 Threshold data Id ..... | 20 |
+| 4.3.3.16 Threshold data instance..... | 20 |
+| 4.3.4 Name binding definitions..... | 20 |
+| 4.3.5 Abstract syntax productions..... | 21 |
+| 4.3.6 Support objects from other CCITT Recommendations..... | 22 |
+| 4.3.6.1 Support objects from the summarization function ..... | 22 |
+| 4.3.6.2 Support objects from definition of management information..... | 22 |
+| 4.3.7 Performance management control..... | 22 |
+| 4.4 Performance management service definition..... | 23 |
+| 4.5 Functional unit definitions..... | 23 |
+| 5 Protocol ..... | 23 |
+| 5.1 Abstract syntax ..... | 23 |
+| 5.1.1 Managed objects ..... | 23 |
+| 5.1.1.1 Referenced managed objects..... | 23 |
+| 5.1.1.2 Defined managed objects ..... | 23 |
+| 5.1.2 Attributes..... | 23 |
+| 5.1.2.1 Attributes imported from the metric objects and attributes function ..... | 23 |
+| 5.1.2.2 Attributes imported from the summarization function..... | 24 |
+| 5.1.2.3 Attributes imported from definition of management information..... | 24 |
+| 5.1.2.4 Attributes defined in this Recommendation..... | 24 |
+| 5.1.3 Notifications..... | 24 |
+| 5.1.3.1 Referenced notifications ..... | 24 |
+| 5.2 Negotiation of functional units ..... | 25 |
+| 6 Relationship with other Recommendations..... | 25 |
+| 7 Conformance ..... | 25 |
+| 7.1 General conformance class requirements ..... | 25 |
+| 7.1.1 Static conformance..... | 25 |
+| 7.1.2 Dynamic conformance ..... | 26 |
+| 7.2 Dependent conformance class requirements..... | 26 |
+| 7.2.1 Static conformance..... | 26 |
+| 7.2.2 Dynamic conformance ..... | 26 |
+| 7.3 Conformance to support managed object definitions..... | 26 |
+| Annex A – Performance monitoring parameters ..... | 27 |
+| A.1 Abbreviations..... | 27 |
+| A.2 Performance monitoring parameters attribute templates ..... | 28 |
+| A.2.1 Alarm indication signal second (AISS)..... | 28 |
+| A.2.2 Alarm indication signal second far end (AISSFE)..... | 28 |
+| A.2.3 Controlled slip second (CSS)..... | 29 |
+| A.2.4 Controlled slip second far end (CSSFE)..... | 29 |
+| A.2.5 Code Violation (CV)..... | 29 |
+| A.2.6 Code violation, CP-bit parity (CVCP)..... | 29 |
+| A.2.7 Code violation, CP-bit parity far end (CVCPFE) ..... | 29 |
+| A.2.8 Code violation, cyclic redundancy check (CVCRC) ..... | 29 |
+| A.2.9 Code violation, cyclic redundancy check far end (CVCRCFE)..... | 30 |
+| A.2.10 Code violation far end (CVFE)..... | 30 |
+| A.2.11 Code violation, P-bit (CVP)..... | 30 |
+| A.2.12 Errored second (ES)..... | 30 |
+
+| | Page | |
+|------------------------------------------------------------------|-----------------------------------------------------------------------------|----|
+| A.2.13 | Errored second, type A (ESA) ..... | 30 |
+| A.2.14 | Errored second, type A, CP-bit (ESACP) ..... | 31 |
+| A.2.15 | Errored second, type A, CP-bit far end (ESACPFE) ..... | 31 |
+| A.2.16 | Errored second, type A, CRC (ESACRC) ..... | 31 |
+| A.2.17 | Errored second, type A, CRC far end (ESACRCFE)..... | 31 |
+| A.2.18 | Errored second, type A, far end (ESAFE) ..... | 31 |
+| A.2.19 | Errored second, type A, P-bit (ESAP) ..... | 32 |
+| A.2.20 | Errored second, type B (ESB)..... | 32 |
+| A.2.21 | Errored second, type B, CP-bit (ESBCP) ..... | 32 |
+| A.2.22 | Errored second, type B, CP-bit far end (ESBCPFE)..... | 32 |
+| A.2.23 | Errored second, type B, CRC (ESBCRC)..... | 32 |
+| A.2.24 | Errored second, type B, CRC far end (ESBCRCFE) ..... | 33 |
+| A.2.25 | Errored second, type B, far end (ESBFE)..... | 33 |
+| A.2.26 | Errored second, type B, P-bit (ESBP)..... | 33 |
+| A.2.27 | Errored second, CP-bit parity (ESCP) ..... | 33 |
+| A.2.28 | Errored second, CP-bit parity far end (ESCPFE)..... | 33 |
+| A.2.29 | Errored second, cyclic redundancy check (ESCRC)..... | 34 |
+| A.2.30 | Errored second, cyclic redundancy check far end (ESCRCFE)..... | 34 |
+| A.2.31 | Errored second far end (ESFE) ..... | 34 |
+| A.2.32 | Errored second, P-bit (ESP) ..... | 34 |
+| A.2.33 | Loss of signal second (LOSS)..... | 34 |
+| A.2.34 | Protection switching count (PSC) ..... | 35 |
+| A.2.35 | Protection switching duration (PSD) ..... | 35 |
+| A.2.36 | SEF/AIS severely errored framing alarm indication signal second (SAS) ..... | 35 |
+| A.2.37 | SEF/AIS second, far end (SASFE) ..... | 35 |
+| A.2.38 | Severely errored second (SES) ..... | 35 |
+| A.2.39 | Severely errored second, CP-bit (SESCP) ..... | 36 |
+| A.2.40 | Severely errored second, CP-bit far end (SESCPFE) ..... | 36 |
+| A.2.41 | Severely errored second, CRC (SESCRC)..... | 36 |
+| A.2.42 | Severely errored second, CRC far end (SESCRCFE)..... | 36 |
+| A.2.43 | Severely errored second far end (SESFE)..... | 36 |
+| A.2.44 | Severely errored second-path (SESP) ..... | 37 |
+| A.2.45 | Unavailable second (UAS) ..... | 37 |
+| A.2.46 | Unavailable second far end (UASFE)..... | 37 |
+| Annex B – Performance management information model overview..... | | 37 |
+| B.1 | Introduction ..... | 37 |
+| B.2 | Overview of the performance management information model ..... | 37 |
+| B.2.1 | Collection of current PM data ..... | 38 |
+| B.2.2 | History records..... | 38 |
+| B.2.3 | Scheduled report ..... | 39 |
+| B.2.4 | Setting and reporting of PM thresholds ..... | 39 |
+| B.2.4.1 | Thresholds applying to a single managed object ..... | 39 |
+| B.2.4.2 | Thresholds applying to multiple managed objects..... | 40 |
+| B.2.5 | Historical retention of PM data..... | 42 |
+| B.2.6 | Scheduled summary or statistical reports..... | 42 |
+| Annex C – PM model alternative ..... | | 44 |
+| C.1 | Performance management model..... | 44 |
+| C.2 | Performance management information..... | 44 |
+| C.2.1 | Difference scanner ..... | 44 |
+| C.2.2 | Performance data component..... | 45 |
+| C.3 | Attribute definitions..... | 46 |
+| C.3.1 | Difference report list ..... | 46 |
+| C.4 | Name binding definitions..... | 46 |
+| C.5 | Guidelines for the use of the model ..... | 46 |
+
+# **ABSTRACT**
+
+This Recommendation provides a Stage 1, Stage 2 and Stage 3 Description for the Q3 Interface in a Telecommunication Management Network. Its focus is the parameter collection and storage, and the thresholding aspects of Performance Management. Included in this Description are specifications of the functions, management information, services, functional units, and protocols related to Performance Management. Significant re-use of OSI system Management specifications is described in the X.700-Series Recommendations.
+
+This Recommendation may be applicable to other TMN-related interfaces.
+
+# **KEYWORDS**
+
+Abstract syntax, attribute, function, functional unit, object class, parameter, performance management, performance monitoring, protocol, service.
+
+# **STAGE 1, STAGE 2 AND STAGE 3 DESCRIPTION FOR THE Q3 INTERFACE – PERFORMANCE MANAGEMENT**
+
+*(Geneva, 1994)*
+
+# **1 Scope, purpose, and field of application**
+
+## **1.1 Scope**
+
+This Recommendation provides a Stage 1, Stage 2 and Stage 3 Description (see Recommendation Q.68) for the parameter collection and thresholding aspects of Performance Management.
+
+This Recommendation is part of a series of Recommendations that specify the Q3 interface (defined in Recommendation M.3010) requirements for communication:
+
+- between an Operations System (OS) and a Network Element (NE);
+- between an OS and a Mediation Device (MD);
+- between an OS and a Q Adaptor (QA); and
+- between Operations Systems in a Telecommunication Management Network (TMN).
+
+## **1.2 Purpose**
+
+Current telecommunications networks are populated by a large and increasing number of OSs and NEs supplied by different vendors. Both the number and variety of networks and services have grown, creating a diversity of management needs. This growth has resulted in the proliferation of unique communication interfaces between OSs and NEs. The telecommunications industry stands to benefit from the standardization of these interfaces, designed to achieve interoperability between a broad range of OSs and NE/QAs using MDs where appropriate, and between OSs.
+
+The primary purpose of this document is to provide a set of application messages and associated support objects for the parameter collection and thresholding aspects of Performance Management. Because of the desirability of providing common TMN solutions, these messages and support objects are expected to be applicable to other TMN or TMN-related interfaces.
+
+## **1.3 Field of application**
+
+This Recommendation defines an information model based on the specification of Managed Object classes. These Managed Object classes are supported through the interactive services specified in ITU-T Recommendation Q.812.
+
+# **2 References**
+
+The following Recommendations contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations are subject to revision, and parties to agreements based on this Recommendation are encouraged to investigate the possibility of applying the most recent edition of the Recommendations listed below.
+
+## **2.1 Recommendations referred to in this Recommendation**
+
+- CCITT Recommendation M.3010, *Principles for a telecommunication management network (TMN)*.
+- CCITT Recommendation M.3020, *TMN interface specification methodology*.
+
+- CCITT Recommendation M.3100, *Generic network information model*.
+- CCITT Recommendation M.3200, *TMN management services: overview*.
+- ITU-T Recommendation Q.68, *Overview of methodology for developing management services*.
+- ITU-T Recommendation Q.812, *Upper layer protocol profiles for the Q3 interface*.
+- ITU-T Recommendation Q.821, *Stage 2 and Stage 3 description for the Q3 interface – Alarm surveillance*.
+- CCITT Recommendation X.208, *Specification of Abstract Syntax Notation One (ASN.1)*.
+- CCITT Recommendation X.209, *Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1)*.
+- CCITT Recommendation X.216, *Presentation service definition for open systems interconnection for CCITT applications*.
+- CCITT Recommendation X.701, *Systems management overview*.
+- CCITT Recommendation X.710, *Management information service definition – Common management information service definition*.
+- CCITT Recommendation X.711, *Management information protocol specification – Common management information protocol*.
+- CCITT Recommendation X.721, *Definition of management information*.
+- CCITT Recommendation X.722, *Guidelines for the definition of managed objects*.
+- CCITT Recommendation X.730, *Object management function*.
+- CCITT Recommendation X.731, *State management function*.
+- CCITT Recommendation X.733, *Alarm reporting function*.
+- CCITT Recommendation X.734, *Event report management function*.
+- CCITT Recommendation X.735, *Log control function*.
+- ITU-T Recommendation X.738, *Summarization function*.
+- ITU-T Recommendation X.739, *Metric Objects and Attributes*.
+
+# 3 Terms and definitions, abbreviations
+
+## 3.1 Terms and definitions
+
+This Recommendation makes use of the following terms defined in CCITT Recommendation M.3010:
+
+- a) performance management;
+- b) telecommunications management network (TMN).
+
+This Recommendation makes use of the following terms defined in CCITT Recommendation M.3020:
+
+TMN management function.
+
+This Recommendation makes use of the following terms defined in CCITT Recommendation X.216:
+
+application context.
+
+This Recommendation makes use of the following terms defined in CCITT Recommendation X.700:
+
+- a) managed object class;
+- b) object instance.
+
+This Recommendation makes use of the following terms defined in CCITT Recommendation X.701:
+
+- a) agent;
+- b) dependent conformance;
+- c) general conformance;
+- d) managed object class;
+- e) managed system;
+- f) management information;
+- g) management support object;
+- h) manager;
+- i) managing system;
+- j) notification.
+
+This Recommendation makes use of the following terms defined in CCITT Recommendation X.710:
+attribute.
+
+This Recommendation makes use of the following terms defined in CCITT Recommendation X.720:
+
+- a) inheritance;
+- b) conditional package;
+- c) name binding;
+- d) package;
+- e) relative distinguished name.
+
+This Recommendation makes use of the following terms defined in CCITT Recommendation X.721:
+alarm record (object class).
+
+This Recommendation makes use of the following terms defined in CCITT Recommendation X.722:
+template.
+
+This Recommendation makes use of the following terms defined in CCITT Recommendation X.733:
+Quality of service alarm (notification).
+
+This Recommendation makes use of the following terms defined in CCITT Recommendation X.735:
+
+- a) Log (managed object class);
+- b) Log record (managed object class).
+
+This Recommendation makes use of the following terms defined in ITU-T Recommendation X.738:
+
+- a) Scan Report (notification);
+- b) Statistical Report (notification).
+
+This Recommendation makes use of the following terms defined in ITU-T Recommendation X.739:
+Scanner (managed object class).
+
+## 3.2 Abbreviations
+
+- ASN.1 Abstract Syntax Notation One
+- CCITT International Telephone and Telegraph Consultative Committee
+- GDMO Guidelines for the definition of managed objects
+
+| | |
+|-------|------------------------------------------------|
+| IEC | International Electrotechnical Commission |
+| ISO | International Organization for Standardization |
+| MAPDU | Management Application Protocol Data Unit |
+| MD | Mediation Device |
+| NE | Network Element |
+| OS | Operations System |
+| OSI | Open Systems Interconnection |
+| PM | Performance Management |
+| PMN | Performance Monitoring |
+| RDN | Relative Distinguished Name |
+| QA | Q Adaptor |
+| TMN | Telecommunications Management Network |
+
+# 4 Performance management
+
+## 4.1 Performance management functions
+
+The following clauses describe the TMN Management functions for Performance Management that are being considered in this Recommendation. These TMN Management functions are defined in accordance with the TMN interface specification methodology in Recommendation M.3020.
+
+### 4.1.1 Performance management data collection functions
+
+PM data collection refers to the ability for the NE to collect the various PM data relating to a single monitored entity in that NE. The following specific functions are associated with the collection activity:
+
+- a) *Assign PM data collection interval* – The TMN manager instructs the NE about the duration of the PM data collection interval for a given entity or set of entities.
+- b) *Suspend/Resume PM data collection* – The TMN manager instructs the NE to suspend/resume the performance monitoring data collection activity for a given monitored entity or set of monitored entities.
+- c) *Reset PM data* – The TMN manager instructs the NE to reset the performance monitoring counters for a given monitored entity or set of monitored entities.
+- d) *Schedule PM data collection* – The TMN manager instructs the NE to schedule the data collection activity for a given monitored entity or set of monitored entities to take place within specified time periods.
+
+### 4.1.2 Performance management data storage functions
+
+PM data storage refers to the optional capability for the NE to store historical PM data on each monitored entity for a prescribed time duration. The NE can also store summarized or statistical data derived from various monitored entities. The following specific functions are associated with the storage activity:
+
+- a) *Assign PM history duration* – The TMN manager instructs the NE to establish the duration during which to maintain a specific record of PM historical data.
+
+- b) *Screen PM data storage* – The TMN manager instructs the NE to originate historical data based on some screening criteria (e.g. suppress “all-zero” data).
+- c) *Remove PM history data* – The TMN manager instructs the NE to remove specific historical PM data.
+
+### 4.1.3 Performance management thresholding functions
+
+PM thresholding refers to the ability for the NE to inform the TMN manager of any threshold crossing. It also provides the TMN manager with the means for establishing thresholding criteria. The following specific functions are associated with the thresholding activity:
+
+- a) *Assign PM threshold* – The TMN manager instructs the NE to establish the thresholding criteria for PM data of a given monitored entity or set of monitored entities.
+- b) *Report PM threshold violation* – The NE informs the TMN manager of a PM parameter threshold violation having occurred in a specific monitored entity.
+
+### 4.1.4 Performance management data reporting functions
+
+PM data reporting refers to the optional capability for the NE to report PM data on a scheduled basis, or as a result of a spontaneous request from the TMN manager. A report may contain data from a given monitored entity, or it can contain summarized data or data derived statistically from a set of monitored entities. The following specific functions are associated with the reporting activity:
+
+- a) *Request PM data* – The TMN manager issues a spontaneous request to the NE for current or historical PM data information on a given monitored entity or set of monitored entities.
+- b) *Report PM data* – The NE issues a scheduled report to the TMN manager with current or historical PM data information from a given monitored entity or set of monitored entities.
+- c) *Allow/Inhibit PM data reports* – The TMN manager allows/inhibits the emission of scheduled reports in the NE.
+- d) *Screen PM data reports* – The TMN manager instructs the NE to issue PM data reports to the TMN manager based on some screening criteria (e.g. suppress “all-zero” data).
+
+## 4.2 Performance management model
+
+This subclause is intended to provide a conceptual framework for understanding how the various managed object classes are used to provide the performance monitoring services described in this Recommendation. A more detailed description of the model and examples of different possible configurations are provided in Annex B.
+
+The object model for Performance Management is shown in Figure 1. Current PM data is collected for a Monitored Object by a *currentData* object class or its subclasses. Instances of the *currentData* object class or its subclasses are contained by the monitored object. At the end of each performance interval, the duration of which is determined by the *granularityPeriod* attribute, a summary report (*scanReport*) may be issued and a *historyData* object may be created to record the performance measurements for that interval. Thresholds may be established by use of the *thresholdData* object. When a threshold is violated by a performance measurement an alarm is emitted by the *currentData* object and logged as required. Performance measurements can be aggregated or statistically summarized by use of Scanner objects as defined in Recommendation X.738.
+
+NOTE 1 – Existing system management Standards and Recommendations allow the PM attributes to be included within the monitored managed object (e.g. OSI Network and Transport layer objects in ISO/IEC 10733 and ISO/IEC 10737). The intention of this Recommendation is not to invalidate the continued use of such models. However, the model provided in this Recommendation encourages the specification of application-specific performance attributes within a separate managed object.
+
+
+
+```
+
+graph TD
+ MO[Monitored object] --- C1{C}
+ C1 --- CD[1 day
+15 min
+currentData]
+ CD --> TD[thresholdData]
+ CD --> HD[historyData]
+ CD -- Scans --> S[Scanner]
+ CD -- Emits --> QSN[Quality of service alarm notification]
+ CD -- Emits --> SRN[Scan report notification]
+ S -- "Emits scan reporta)" --> C2{C}
+ C2 --- L[log]
+ C2 --- SRR[scan ReportRecord]
+ SRR --- QAR[qos AlarmRecord]
+ style MO fill:none,stroke:#000
+ style CD fill:none,stroke:#000
+ style TD fill:none,stroke:#000
+ style HD fill:none,stroke:#000
+ style S fill:none,stroke:#000
+ style L fill:none,stroke:#000
+ style SRR fill:none,stroke:#000
+ style QAR fill:none,stroke:#000
+
+```
+
+The diagram illustrates the object model for performance management. A 'Monitored object' is linked via a containment relationship (diamond 'C') to 'currentData', which handles '15 min' and '1 day' intervals. 'currentData' relates to 'thresholdData' and 'historyData' (shown as stacked boxes). It also interacts with a 'Scanner' (labeled 'Scans') and emits 'Quality of service alarm notification' and 'Scan report notification'. The 'Scanner' emits a 'scan reporta)', which is linked via another containment diamond 'C' to a 'log' and a 'scan ReportRecord'. The 'scan ReportRecord' is associated with a 'qos AlarmRecord'. The reference 'T1150950-93/d01' appears at the bottom right.
+
+Object model diagram showing relationships between Monitored object, currentData, thresholdData, historyData, Scanner, log, scan ReportRecord, and qos AlarmRecord.
+
+- a) The scan reports may include: an aggregation of measurements over time for a single monitored object, or across a number of monitored objects; an aggregation of measurements from a single interval across a number of monitored objects; or statistics for a single or multiple intervals across a single or multiple monitored objects.
+
+FIGURE 1/Q.822
+
+### **Objet model**
+
+The specific objects in the model are:
+
+- *Monitored Object* – This object is the managed object for which the performance measurements are being collected. It represents the resource being measured (e.g. Trail Termination Point).
+- *currentData Object* – This object contains the measurements for the resource being monitored for a specified time interval (e.g. 15 min.). In most cases the instantiated managed object will be an instance of a subclass of currentData. This subclass will have performance measurement attributes appropriate to the resource represented by the class of the monitored object (e.g. SDH performance measurements). At the end of each interval the currentData object may emit a scanReport notification which may result in a
+
+corresponding Event Report being sent to a managing system (it is not mandatory that the discriminator construct in the Log be configured such that this notification is logged). Also, at the end of each interval a historyData object may be created containing the same attributes as the currentData object with values of the performance measurements at the end of the interval.
+
+The currentData object may contain a pointer to a thresholdData object. If any of the thresholds (defined in the referenced thresholdData object) are violated a Quality of Service (QOS) alarm notification is emitted by the currentData object. The resulting alarm record may be logged.
+
+The generic currentData object class shall not be used for technology specific interfaces where standardized technology specific subclasses of currentData exist.
+
+- *historyData Object* – This object will contain a copy of the performance management and other selected attributes that are present in the currentData object at the end of the current interval (e.g. 15 min.). A new instance of this object class is created at the end of each interval.
+- *thresholdData Object* – This object contains a set of threshold values which correspond to a set of measurements defined for one or more classes of currentData. The thresholdData object is referenced from the currentData object by a pointer. If any of the thresholds specified in the thresholdData object are violated by the measurements in the referencing currentData object, the currentData object immediately issues a Quality of Service alarm notification.
+- *Scanners* – Any of the scanner objects which are defined in Recommendation X.738 may be used to scan the contents of either the currentData or historyData objects. These scanners may be used to aggregate sets of measurements from a number of currentData objects representing a number of different Monitored Objects and/or a number of historyData objects for one or more monitored entities. These scanner objects may simply aggregate the measurements into a scanReport notification for bulk transfer to a managing system, or they may be used to perform statistics on the measurements (e.g. mean, variance, etc.) for inclusion in a scanReport which can be sent to the managing system or stored in the log.
+
+Scanners used to aggregate measurements include: simpleScanner and dynamicSimpleScanner. Those used to perform statistics include: meanScanner, meanVarianceScanner and minMaxScanner.
+
+NOTE 2 – The historyData object provides more flexible access to performance measurements than the scanReport, since the measurements are held in individual attributes rather than a single complex attribute. The use of historyData also provides a closer association of the contained information with the monitored object that does the scanReport. In the generic log there is no mechanism to restrict log records in a similar way to historyData (which may be implicitly deleted after a number of intervals).
+
+## 4.3 Performance management information
+
+This Recommendation provides generic definitions of managed objects and attributes associated with Performance Management.
+
+### 4.3.1 Managed object classes
+
+The following support object classes (or their subclasses) support the Performance Management functions specified in this Recommendation. Definitions are provided in GDMO template form, as specified in CCITT Recommendation X.722. The inheritance hierarchy for these support objects is shown in Figure 2 below and the naming hierarchy is shown in Figure 3.
+
+
+
+```
+
+graph TD
+ Top[Top] --> Scanner["Scanner (X. 738)"]
+ Top --> thresholdData[thresholdData]
+ Top --> historyData[historyData]
+ Scanner --> currentData[currentData]
+ currentData --> TSCurrentData["Technology specific currentData"]
+ historyData --> TSHistoryData["Technology specific historyData"]
+ style TSCurrentData fill:none,stroke:none
+ style TSHistoryData fill:none,stroke:none
+
+```
+
+T1150960-93/d02
+
+Object inheritance diagram showing Top as the root, with Scanner (X. 738), thresholdData, and historyData as children. Scanner has currentData, which has Technology specific currentData. historyData has Technology specific historyData.
+
+a) These objects will be defined in other Recommendations.
+
+FIGURE 2/Q.822
+**Object inheritance**
+
+
+
+```
+
+graph TD
+ ManagedElement[Managed element] --> MonitoredObject[Monitored object]
+ MonitoredObject --> currentData[currentData]
+ currentData --> historyData[historyData]
+ currentData --> thresholdData[thresholdData]
+ style MonitoredObject fill:#ccc,stroke:none
+
+```
+
+T1150970-93/d03
+
+Object inheritance diagram showing Managed element as the root, with Monitored object, currentData, historyData, and thresholdData as children. Monitored object is shaded.
+
+FIGURE 3/Q.822
+**Naming hierarchy**
+
+#### 4.3.1.1 Current data
+
+##### **currentData MANAGED OBJECT CLASS**
+
+**DERIVED FROM "Recommendation X.739:1993": scanner;**
+
+**CHARACTERIZED BY currentDataPkg PACKAGE**
+
+**BEHAVIOUR currentDataBehaviour BEHAVIOUR**
+
+**DEFINED AS**
+
+"The currentData object class is a class of managed support objects that contain the current performance data. This object class is a particular type of scanner (see ITU-T Recommendation X.739) that scans its own attributes.
+
+*-- In this Recommendation an instance of current data is assumed to be contained in the managed object being monitored (such as the trailTerminationPointSink managed object defined in Recommendation M.3100) and has performance data pertaining to the containing managed object.*
+
+Performance parameters are modelled as attributes. These attributes either appear explicitly in the definition of subclasses of currentData or the measurementListPkg is used for this purpose if the instantiated object class is currentData.
+
+Typically, the performance attributes may be derived from the **counter** attribute or may be derived from the **gauge** attribute. Both the counter and gauge attributes are defined in CCITT Recommendation X.721. All attributes with a 'Count' type syntax (e.g. errored seconds) shall be locally cleared (reset) at the end of the granularity period following the scanning function. To provide continuous counters, the granularityPeriod can be set to an arbitrarily large value using the dials CHOICE.
+
+If the administrativeState is locked or the operationalState is disabled or the currentData object is scheduled off-duty, the values of the counters are undefined and historyData objects, if supported, are not created at the end of the granularityPeriod."
+
+;;
+
+##### **ATTRIBUTES**
+
+**suspectIntervalFlag**
+
+**REPLACE-WITH-DEFAULT**
+
+**DEFAULT VALUE Q822-PM-ASN1Module.defaultCurrentDataSuspectIntervalFlag**
+
+**GET,**
+
+**elapsedTime**
+
+**GET;**
+
+;;
+
+##### **CONDITIONAL PACKAGES**
+
+###### **filterSuppressionPkg**
+
+**PRESENT IF "an instance supports it and the zeroSuppressionPkg is not present",**
+
+###### **historyRetentionPkg**
+
+**PRESENT IF "historyData objects are to be created at the end of an interval.",**
+
+###### **maxSuppressedIntervalsPkg**
+
+**PRESENT IF "an instance supports it and at least one of zeroSuppressionPkg or filterSuppressionPkg is present.",**
+
+###### **measurementListPkg**
+
+**PRESENT IF "an instance supports it or the object class is currentData",**
+
+###### **numSuppressedIntervalsPkg**
+
+**PRESENT IF "suppression counts are required and the filterSuppressionPkg or the zeroSuppressionPkg is present.",**
+
+###### **observedManagedObjectPkg**
+
+**PRESENT IF "an instance supports it.",**
+
+**scheduledPMReportPkg**
+PRESENT IF "scheduled notifications are to be emitted.",
+
+**thresholdPkg**
+PRESENT IF "a Quality of Service Alarm Notification is to be emitted for threshold crossing.",
+
+**zeroSuppressionPkg**
+PRESENT IF "an instance supports it and the filterSuppressionPkg is not present.";
+
+**REGISTERED AS {q822ObjectClass 1};**
+
+#### 4.3.1.2 History data
+
+**historyData MANAGED OBJECT CLASS**
+DERIVED FROM "Recommendation X.721:1992": top;
+CHARACTERIZED BY historyDataPkg PACKAGE
+BEHAVIOUR historyDataBehaviour BEHAVIOUR
+DEFINED AS
+
+Measurement attributes in the historyData object are an exact copy of the attributes in the corresponding currentData object at the end of the interval.
+
+The time at the end of the interval is indicated by the value of the attribute periodEndTime.
+
+;;
+**ATTRIBUTES**
+historyDataId
+GET,
+periodEndTime
+GET,
+"Recommendation X.739:1993": granularityPeriod
+GET;;;
+**CONDITIONAL PACKAGES**
+historyDataMeasurementListPkg
+PRESENT IF "the measurementListPkg is present in the corresponding currentData instance",
+historyDataSuspectIntervalFlagPkg
+PRESENT IF "an instance supports it.",
+numSuppressedIntervalsPkg
+PRESENT IF "this package is present in the corresponding currentData instance.",
+objectDeleteNotificationPkg
+PRESENT IF "an instance supports it.",
+observedManagedObjectPkg
+PRESENT IF "this package is present in the corresponding currentData instance.";
+**REGISTERED AS {q822ObjectClass 2};**
+
+#### 4.3.1.3 Threshold data
+
+**thresholdData MANAGED OBJECT CLASS**
+DERIVED FROM "Recommendation X.721:1992": top;
+CHARACTERIZED BY thresholdDataPkg PACKAGE
+BEHAVIOUR thresholdDataBehaviour BEHAVIOUR
+DEFINED AS
+
+"The thresholdData object class is a class of managed support objects that contains the values of the threshold settings for the PM parameters. At least one of the counterThresholdListPkg or the gaugeThresholdListPkg must be instantiated."
+
+```
+
+;;
+ATTRIBUTES
+ thresholdDataId
+ GET;
+
+;;
+CONDITIONAL PACKAGES
+
+counterThresholdListPkg
+ PRESENT IF "an instance supports it and the gaugeThresholdListPkg is not present.",
+
+gaugeThresholdListPkg
+ PRESENT IF "an instance supports it and the counterThresholdListPkg is not present",
+
+thresholdVerificationPkg
+ PRESENT IF "an instance supports it.",
+
+"Recommendation M.3100:1992": attributeValueChangeNotificationPackage
+ PRESENT IF "an instance supports it.",
+
+"Recommendation M.3100:1992": createDeleteNotificationsPackage
+ PRESENT IF "an instance supports it.";
+
+REGISTERED AS {q822ObjectClass 3};
+
+```
+
+### 4.3.2 Package definitions
+
+#### 4.3.2.1 Counter threshold list package
+
+```
+
+counterThresholdListPkg PACKAGE
+ ATTRIBUTES
+ counterThresholdAttributeList
+ GET-REPLACE
+ ADD-REMOVE;
+ REGISTERED AS {q822Package 1};
+
+```
+
+#### 4.3.2.2 Filter suppression package
+
+```
+
+filterSuppressionPkg PACKAGE
+ BEHAVIOUR filterSuppressionPkgBehaviour BEHAVIOUR
+ DEFINED AS
+
+```
+
+"The discriminatorConstruct attribute is used to suppress the creation of historyData objects. The behaviour of the discriminatorConstruct is defined in 8.1.1.2 CCITT Rec. X.734. If the discriminatorConstruct evaluates to FALSE for the filtering criteria on the attributes specified in the discriminatorConstruct, no historyData objects are created. An empty discriminator construct will evaluate to TRUE, thus allowing the creation of historyData objects. Any attribute of the object which includes this package may be used in defining the discriminator construct."
+
+```
+
+;;
+ ATTRIBUTES
+ "Recommendation X.721:1992": discriminatorConstruct
+ DEFAULT VALUE Attribute-ASN1Module.defaultDiscriminatorConstruct
+ GET-REPLACE;
+ REGISTERED AS {q822Package 2};
+
+```
+
+#### 4.3.2.3 Gauge threshold list package
+
+```
+
+gaugeThresholdListPkg PACKAGE
+ ATTRIBUTES
+ gaugeThresholdAttributeList
+ GET-REPLACE
+ ADD-REMOVE;
+ REGISTERED AS {q822Package 3};
+
+```
+
+#### **4.3.2.4 History data measurement list package**
+
+**historyDataMeasurementListPkg PACKAGE**
+
+**ATTRIBUTES**
+
+**measurementList**
+
+**GET;**
+
+**REGISTERED AS {q822Package 4};**
+
+#### **4.3.2.5 History data suspect interval flag package**
+
+**historyDataSuspectIntervalFlagPkg PACKAGE**
+
+**BEHAVIOUR historyDataSuspectIntervalFlagPkgBehaviour BEHAVIOUR**
+
+**DEFINED AS**
+
+"The historyDataSuspectIntervalFlagPkg shall be instantiated in the historyData object only if there are one or more suspected performance measurements in the corresponding accumulation interval."
+
+;;
+
+**ATTRIBUTES**
+
+**suspectIntervalFlag**
+
+**GET;**
+
+**REGISTERED AS {q822Package 5};**
+
+#### **4.3.2.6 History retention package**
+
+**historyRetentionPkg PACKAGE**
+
+**BEHAVIOUR historyRetentionPkgBehaviour BEHAVIOUR**
+
+**DEFINED AS**
+
+"At the end of each interval a historyData object instance is created if the historyData creation has not been suppressed (i.e. by zero or filter suppression). The class of the historyData object will correspond to the class of the creating currentData object; an instance of the historyData object will be instantiated if there is an instance of the currentData object. The behaviour in subclasses of currentData should specify the subclass of historyData that may be instantiated. The values of the historyData measurement attributes are a copy of the values of the corresponding attributes of the currentData measurement attributes at the end of the interval.
+
+Once the new historyData object is created, it will be retained in the NE for at least the duration equivalent to the number of intervals specified in the historyRetention attribute."
+
+;;
+
+**ATTRIBUTES**
+
+**historyRetention**
+
+**GET-REPLACE;**
+
+**REGISTERED AS {q822Package 6};**
+
+#### **4.3.2.7 Maximum number of suppressed intervals package**
+
+**maxSuppressedIntervalsPkg PACKAGE**
+
+**ATTRIBUTES**
+
+**maxSuppressedIntervals**
+
+**GET-REPLACE;**
+
+**REGISTERED AS {q822Package 7};**
+
+#### 4.3.2.8 Measurement list package
+
+**measurementListPkg PACKAGE**
+
+**BEHAVIOUR measurementListPkgBehaviour BEHAVIOUR**
+
+**DEFINED AS**
+
+"The measurementList attribute contains performance management measurements (each measurement is in the form of an attribute identifier and its value) for a specific monitored object. Typically, the performance attributes may be derived from the **counter** attribute or may be derived from the **gauge** attribute. Both the counter and gauge attributes are defined in CCITT Recommendation X.721. All attributes with a 'Count' type syntax (e.g. ES) shall be locally cleared (reset) at the end of the granularity period following the scanning function.
+
+The measurement list shall not contain parameters which have already been defined as an attribute of that currentData object subclass.
+
+The measurementList is only used when technology specific (currentData subclass) is not available. Typical, but not restrictive use of this package is as a home for not yet standardized performance parameters. This package should not be used as an escape from standardizing technology specific currentData subclasses.
+
+NOTE – Measurements in the measurement list cannot be individually reset to zero."
+
+;;
+
+**ATTRIBUTES**
+
+**measurementList**
+
+**GET-REPLACE;**
+
+**REGISTERED AS {q822Package 8};**
+
+#### 4.3.2.9 Number of suppressed intervals package
+
+**numSuppressedIntervalsPkg PACKAGE**
+
+**ATTRIBUTES**
+
+**numSuppressedIntervals**
+
+**GET;**
+
+**REGISTERED AS {q822Package 9};**
+
+#### 4.3.2.10 Object delete notification package
+
+**objectDeleteNotificationPkg PACKAGE**
+
+**BEHAVIOUR objectDeleteNotificationBehaviour BEHAVIOUR**
+
+**DEFINED AS**
+
+"An objectDeletion notification shall not be emitted when a historyData object is deleted as a result of the expiry of the historyRetention duration."
+
+;;
+
+**NOTIFICATIONS**
+
+**"Recommendation X.721:1992": objectDeletion;**
+
+**REGISTERED AS {q822Package 10};**
+
+#### 4.3.2.11 Observed managed object package
+
+**observedManagedObjectPkg PACKAGE**
+
+**ATTRIBUTES**
+
+**observedObjectClass**
+
+**GET,**
+
+**"Recommendation X.739:1993": observedObjectInstance**
+
+**GET;**
+
+**REGISTERED AS {q822Package 11};**
+
+#### 4.3.2.12 Scheduled performance monitoring report package
+
+**scheduledPMReportPkg PACKAGE**
+
+**BEHAVIOUR scheduledPMReportPkgBehaviour BEHAVIOUR**
+
+**DEFINED AS**
+
+"Instances of the currentData object emit the scanReport notification containing the performance monitoring data, at the end of each performance interval, as indicated by the granularityPeriod attribute.
+
+Each performance monitoring attribute is included in the scanReport if its identifier is listed in the scanAttributeIdList or the numericAttributeIdArray. In the latter case, measurements must be included in the scanReport in the same order as specified in the numericAttributeIdArray attribute and valueOnly (in the NumericMeasure choice type) should be the only choice used to report such measurements.
+
+Performance monitoring attributes (parameters) in the measurementList attribute are included in the scanReport as if they were individually scanned attributes of a scanned object. That is, the measurementList is scanned as if each measurement in the list were a separate attribute of the currentData object. The measurementList is not included in the scanReport as a single attribute.
+
+Specific measurement attributes of subclasses of currentData may be included in the scanReport notification if their identifier is listed in either the scanAttributeIdList or the numericAttributeIdArray.
+
+In order to guarantee their inclusion in an event report, the attribute ids for the following attributes of currentData (if instantiated in currentData) must appear in the onceReportAttributeIdList attribute:
+
+- The granularityPeriod attribute.
+- The suspectIntervalFlag attribute.
+- The numSuppressedIntervals attribute, if present.
+- The observedObjectClass and observedObjectInstance attributes, if present."
+
+;;
+
+**ATTRIBUTES**
+
+**"Recommendation X.738:1993": scanAttributeIdList**
+
+**GET-REPLACE**
+
+**ADD-REMOVE,**
+
+**"Recommendation X.738:1993": numericAttributeIdArray**
+
+**GET-REPLACE**
+
+**"Recommendation X.738:1993": onceReportAttributeIdList**
+
+**GET-REPLACE**
+
+**ADD-REMOVE;**
+
+**NOTIFICATIONS**
+
+**"Recommendation X.738:1993": scanReport;**
+
+**REGISTERED AS {q822Package 12};**
+
+#### 4.3.2.13 Threshold package
+
+**thresholdPkg PACKAGE**
+
+**BEHAVIOUR thresholdPkgBehaviour BEHAVIOUR**
+
+**DEFINED AS**
+
+"This package is used to report threshold violations on performance data. The thresholdDataInstance attribute is a pointer to a thresholdData object that contains threshold limits for performance parameters. Whenever the value of a PM parameter violates its threshold setting, a qualityofServiceAlarm notification is emitted. The attribute violating the threshold has to be reported using the thresholdInfo field of the alarm.
+
+New thresholds resulting from modifying the thresholdDataInstance attribute or from changing a threshold value in the referenced thresholdData object, should take effect immediately. If an alarm condition exists previous to the occurrence of a threshold value change (i.e. an old threshold had been violated), and the new threshold value is outside of the range of the old threshold value (e.g. in the case of an increasing counter, the new threshold value is greater than the old threshold value), and the current value of the measurement is within the allowable range of the new threshold value, then a QOS Alarm notification is emitted with a severity of 'clear'. If the new threshold value is set within the range of the old threshold value, such that the new threshold is violated, a QOS Alarm notification is emitted if an alarm condition is not already outstanding.
+
+An alarm report which contains a Perceived Severity parameter with a value of 'cleared' and a Correlated Notifications parameter shall only indicate the clearing of those alarms whose Notification Identifiers are included in the set of Correlated Notifications. An alarm report which contains a Perceived Severity parameter with a value of 'cleared', but no Correlated Notifications parameter, shall indicate the clearing of alarms based on the value of the Alarm Type, Probable Cause, and Specific Problems parameters."
+
+;;
+
+##### ATTRIBUTES
+
+**reportAllAttributes**
+
+**DEFAULT VALUE** Q822-PM-ASN1Module.defaultReportAllAttributes
+
+**GET-REPLACE,**
+
+**suppressAdditionalThresholds**
+
+**DEFAULT VALUE** Q822-PM-ASN1Module.defaultSuppressAdditionalThresholds
+
+**GET-REPLACE,**
+
+**thresholdDataInstance**
+
+**GET-REPLACE**
+
+**ADD-REMOVE**
+
+##### NOTIFICATIONS
+
+**"Recommendation X.721:1992":** qualityofServiceAlarm
+
+**"Recommendation Q.821:1992":** logRecordIdParameter
+
+**"Recommendation Q.821:1992":** correlatedRecordNameParameter
+
+**"Recommendation Q.821:1992":** suspectObjectListParameter;
+
+**REGISTERED AS** {q822Package 13};
+
+#### 4.3.2.14 Threshold verification package
+
+**thresholdVerificationPkg PACKAGE**
+
+**BEHAVIOUR** thresholdVerificationPkgBehaviour **BEHAVIOUR**
+
+**DEFINED AS**
+
+"This package allows for the agent to validate that the threshold settings defined in a created thresholdData object are reasonable. Since the attributes to which a threshold may be applied and the permissible threshold values are dependent on the type of entity being monitored and the granularity period, the agent must be aware of this information. This package provides the monitoredEntityTypes and granularityPeriod attributes needed to verify that the threshold values set in the counterthresholdAttributeList or gaugethresholdAttributeList are reasonable. If the thresholdData object receives a request to set the values in the counterthresholdAttributeList or gaugethresholdAttributeList it may reject the M-SET service request by returning an Error reply of setListError if the values are not appropriate for the monitored entity type and interval combination. In some cases the actual values set in the counterthresholdAttributeList or gaugethresholdAttributeList may be different from the requested values for the threshold. In this case, the next lowest threshold value supported by the managed system is used. This value is returned in the Reply to a confirmed M-SET service request.
+
+The values used for the granularityPeriod attribute and monitoredEntityTypes attribute shall be consistent with the actual values of granularityPeriod used in the system and with the class of actual monitored objects."
+
+```
+;;
+ATTRIBUTES
+"Recommendation X.739:1993": granularityPeriod
+GET,
+monitoredEntityTypes
+GET;
+REGISTERED AS {q822Package 14};
+```
+
+#### 4.3.2.15 Zero suppression package
+
+```
+zeroSuppressionPkg PACKAGE
+ BEHAVIOUR zeroSuppressionPkgBehaviour BEHAVIOUR
+ DEFINED AS
+```
+
+"When this package is present and an interval terminates with 'all-zeros' performance measurements, there is no scanReport notification issued and no historyData object is created."
+
+```
+;;
+REGISTERED AS {q822Package 15};
+```
+
+### 4.3.3 Attribute definitions
+
+#### 4.3.3.1 Counter threshold attribute list
+
+```
+counterThresholdAttributeList ATTRIBUTE
+ WITH ATTRIBUTE SYNTAX Q822-PM-ASN1Module.CounterThresholdAttributeList;
+ MATCHES FOR EQUALITY;
+ BEHAVIOUR counterThresholdAttributeListBehaviour BEHAVIOUR
+ DEFINED AS
+```
+
+"This attribute contains a set of threshold settings for performance attributes of the counter type (e.g. errored seconds). Each threshold setting consists of the attribute identifier, the threshold value and (optionally) the severity of the threshold-exceeded event."
+
+```
+;;
+REGISTERED AS {q822Attribute 1};
+```
+
+#### 4.3.3.2 Elapsed time
+
+```
+elapsedTime ATTRIBUTE
+ WITH ATTRIBUTE SYNTAX Q822-PM-ASN1Module.ElapsedTime;
+ MATCHES FOR EQUALITY;
+ BEHAVIOUR elapsedTimeBehaviour BEHAVIOUR
+ DEFINED AS
+```
+
+"This attribute represents the difference between the current time and the start of the present summary interval."
+
+```
+;;
+REGISTERED AS {q822Attribute 2};
+```
+
+#### 4.3.3.3 Gauge threshold attribute list
+
+```
+gaugeThresholdAttributeList ATTRIBUTE
+ WITH ATTRIBUTE SYNTAX Q822-PM-ASN1Module.GaugeThresholdAttributeList;
+ MATCHES FOR EQUALITY;
+ BEHAVIOUR gaugeThresholdAttributeListBehaviour BEHAVIOUR
+ DEFINED AS
+```
+
+"This attribute contains a set of threshold settings for performance attributes of the gauge type. Each threshold setting consists of the attribute identifier, the threshold value and (optionally) the severity of the threshold-exceeded event."
+
+```
+;;
+REGISTERED AS {q822Attribute 3};
+```
+
+#### 4.3.3.4 History data Id
+
+##### **historyDataId ATTRIBUTE**
+
+**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType;**
+
+**MATCHES FOR EQUALITY;**
+
+**BEHAVIOUR historyDataIdBehaviour BEHAVIOUR**
+
+**DEFINED AS**
+
+"This attribute is used as the RDN attribute for instances of the historyData object class."
+
+;;
+
+**REGISTERED AS {q822Attribute 4};**
+
+#### 4.3.3.5 History retention
+
+##### **historyRetention ATTRIBUTE**
+
+**WITH ATTRIBUTE SYNTAX Q822-PM-ASN1Module.HistoryRetention;**
+
+**MATCHES FOR EQUALITY, ORDERING;**
+
+**BEHAVIOUR historyRetentionBehaviour BEHAVIOUR**
+
+**DEFINED AS**
+
+"This attribute specifies the minimum number of intervals that the historyData object instance (just being created) must be preserved."
+
+;;
+
+**REGISTERED AS {q822Attribute 5};**
+
+#### 4.3.3.6 Maximum suppressed intervals
+
+##### **maxSuppressedIntervals ATTRIBUTE**
+
+**WITH ATTRIBUTE SYNTAX Q822-PM-ASN1Module.MaxSuppressedIntervals;**
+
+**MATCHES FOR EQUALITY;**
+
+**BEHAVIOUR maxSuppressedIntervalsBehaviour BEHAVIOUR**
+
+**DEFINED AS**
+
+"In conjunction with record compression, the maxSuppressedIntervals attribute limits the maximum number of suppressed intervals that will be collected without creating an instance of the historyData object."
+
+For example, consider an instance of (a subClass of) currentData with maxSuppressedIntervals set to 32, and the interval set to 15 minutes. For record compression, it means that after 32 consecutive suppressed (e.g. all-zero) intervals (8 hours) at least one historyData record (with all zero PM Parameters) will be generated with a count of 32. This ensures that at least one historyData record per maxSuppressedIntervals will be created.
+
+If the numSuppressedIntervalsPkg is present, the value of this attribute cannot exceed the maximum possible value of the numSuppressedIntervals attribute (this maximum value is a local matter). If a request to modify the value of this attribute exceeds this maximum values then a CMIP error of invalid Attribute Value is returned."
+
+;;
+
+**REGISTERED AS {q822Attribute 6};**
+
+#### 4.3.3.7 Measurement list
+
+**measurementList ATTRIBUTE**
+**WITH ATTRIBUTE SYNTAX Q822-PM-ASN1Module.AttributeList;**
+**MATCHES FOR EQUALITY, SET-COMPARISON, SET-INTERSECTION;**
+**BEHAVIOUR measurementListBehaviour BEHAVIOUR**
+**DEFINED AS**
+
+"This attribute contains a set of performance parameter measurements for a monitored object. Each measurement is represented by the attribute identifier (e.g. errored seconds) and its value. Measurements may only be included in this list if they do not already exist as explicit measurement attributes of an instance of a subclass of currentData or of an instance of a subclass of historyData."
+
+;;
+**REGISTERED AS {q822Attribute 7};**
+
+#### 4.3.3.8 Monitored entity types
+
+**monitoredEntityTypes ATTRIBUTE**
+**WITH ATTRIBUTE SYNTAX Q822-PM-ASN1Module.MonitoredEntityTypes;**
+**MATCHES FOR EQUALITY;**
+**BEHAVIOUR monitoredEntityTypesBehaviour BEHAVIOUR**
+**DEFINED AS**
+
+"This attribute specifies the monitored entities to which the specified thresholds apply."
+
+;;
+**REGISTERED AS {q822Attribute 8};**
+
+#### 4.3.3.9 Number of suppressed intervals
+
+**numSuppressedIntervals ATTRIBUTE**
+**WITH ATTRIBUTE SYNTAX Q822-PM-ASN1Module.NumSuppressedIntervals;**
+**MATCHES FOR EQUALITY, ORDERING;**
+**BEHAVIOUR numSuppressedIntervalsBehaviour BEHAVIOUR**
+**DEFINED AS**
+
+"This attribute, if present, is used to count the number of consecutive intervals for which suppression (i.e. non-emission of a scanReport notification and non-creation of a historyData instance) has occurred. This attribute reflects performance measurements up to, but not including, the current interval. This attribute gets incremented at the end of an interval if suppression has occurred, otherwise, the attribute is reset."
+
+;;
+**REGISTERED AS {q822Attribute 9};**
+
+#### 4.3.3.10 Observed object class
+
+**observedObjectClass ATTRIBUTE**
+**WITH ATTRIBUTE SYNTAX Q822-PM-ASN1Module.ObjectClass;**
+**MATCHES FOR EQUALITY;**
+**BEHAVIOUR observedObjectClassBehaviour BEHAVIOUR**
+**DEFINED AS**
+
+"This attribute identifies the managed object class of the managed object that is being observed for the purpose of Performance Management."
+
+;;
+**REGISTERED AS {q822Attribute 10};**
+
+#### 4.3.3.11 Report all attributes
+
+**reportAllAttributes ATTRIBUTE**
+**WITH ATTRIBUTE SYNTAX Q822-PM-ASN1Module.ReportAllAttributes;**
+**MATCHES FOR EQUALITY;**
+**BEHAVIOUR reportAllAttributesBehaviour BEHAVIOUR**
+**DEFINED AS**
+
+"This attribute is used to indicate whether all of the measurement attributes in a currentData instance are returned in the Monitored attributes field of the Quality of Service alarm. If the value of this attribute is True, all attribute values are returned. If the value of this attribute is FALSE (default), the Quality of Service alarm does not contain the monitored attributes field."
+
+;;
+**REGISTERED AS {q822Attribute 11};**
+
+#### **4.3.3.12 Period end time**
+
+**periodEndTime ATTRIBUTE**
+**WITH ATTRIBUTE SYNTAX Q822-PM-ASN1Module.PeriodEndTime;**
+**MATCHES FOR EQUALITY;**
+**BEHAVIOUR periodEndTimeBehaviour BEHAVIOUR**
+**DEFINED AS**
+
+"This attribute records the time at the end of the interval."
+
+;;
+**REGISTERED AS {q822Attribute 12};**
+
+#### **4.3.3.13 Suppress additional thresholds**
+
+**suppressAdditionalThresholds ATTRIBUTE**
+**WITH ATTRIBUTE SYNTAX Q822-PM-ASN1Module.SuppressAdditionalThresholds;**
+**MATCHES FOR EQUALITY;**
+**BEHAVIOUR suppressAdditionalThresholdsBehaviour BEHAVIOUR**
+**DEFINED AS**
+
+"This attribute is used to indicate whether additional threshold crossing notifications will be emitted by the currentData object. The value of true for this attribute indicates that no further threshold crossing notifications will be emitted until the end of the interval."
+
+;;
+**REGISTERED AS {q822Attribute 13};**
+
+#### **4.3.3.14 Suspect interval flag**
+
+**suspectIntervalFlag ATTRIBUTE**
+**WITH ATTRIBUTE SYNTAX Q822-PM-ASN1Module.SuspectIntervalFlag;**
+**MATCHES FOR EQUALITY ;**
+**BEHAVIOUR suspectIntervalFlagBehaviour BEHAVIOUR**
+**DEFINED AS**
+
+"This attribute is used to indicate that the performance data for the current period may not be reliable. Some reasons for this to occur are:
+
+- Suspect data were detected by the actual resource doing data collection.
+- Transition of the administrativeState attribute to/from the 'lock' state.
+- Transition of the operationalState to/from the 'disabled' state.
+- Scheduler setting that inhibits the collection function.
+- The performance counters were reset during the interval.
+- The currentData (or subclass) object instance was created during the monitoring period."
+
+;;
+**REGISTERED AS {q822Attribute 14};**
+
+#### 4.3.3.15 Threshold data Id
+
+##### **thresholdDataId ATTRIBUTE**
+
+**WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.NameType;**
+**MATCHES FOR EQUALITY;**
+**BEHAVIOUR thresholdDataIdBehaviour BEHAVIOUR**
+**DEFINED AS**
+
+"This attribute is used as the RDN attribute for instances of the thresholdData object class."
+
+;;
+
+**REGISTERED AS {q822Attribute 15};**
+
+#### 4.3.3.16 Threshold data instance
+
+##### **thresholdDataInstance ATTRIBUTE**
+
+**WITH ATTRIBUTE SYNTAX Q822-PM-ASN1Module.ThresholdDataInstance;**
+**MATCHES FOR EQUALITY;**
+**BEHAVIOUR thresholdDataInstanceBehaviour BEHAVIOUR**
+**DEFINED AS**
+
+"This attribute identifies an instance of the thresholdData object class which contains the threshold settings used by the currentData instance."
+
+;;
+
+**REGISTERED AS {q822Attribute 16};**
+
+### 4.3.4 Name binding definitions
+
+No name bindings for the currentData object class are provided in this Recommendation because of the variety of monitored objects for which the performance management data can be collected. Users of this Recommendation are expected to specify name bindings for currentData or its subclasses to make them instantiable. The rules governing the automatic creation of instances of managed objects are outside the scope of this Recommendation.
+
+#### **historyData-currentData NAME BINDING**
+
+**SUBORDINATE OBJECT CLASS historyData AND SUBCLASSES;**
+**NAMED BY SUPERIOR OBJECT CLASS currentData AND SUBCLASSES;**
+**WITH ATTRIBUTE historyDataId;**
+**DELETE**
+**DELETES-CONTAINED-OBJECTS;**
+
+**REGISTERED AS {q822NameBinding 1};**
+
+NOTE – In a given application, the naming of historyData objects shall be consistent for all instances of historyData (i.e. all shall be named from the monitored entity or all shall be named from the currentData or its subclasses).
+
+#### **thresholdData-managedElement NAME BINDING**
+
+**SUBORDINATE OBJECT CLASS thresholdData AND SUBCLASSES;**
+**NAMED BY SUPERIOR OBJECT CLASS**
+**"Recommendation M.3100:1992": managedElement AND SUBCLASSES;**
+**WITH ATTRIBUTE thresholdDataId;**
+**CREATE**
+**WITH-REFERENCE-OBJECT,**
+**WITH-AUTOMATIC-INSTANCE-NAMING;**
+**DELETE**
+**ONLY-IF-NO-CONTAINED-OBJECTS;**
+
+**REGISTERED AS {q822NameBinding 2};**
+
+### 4.3.5 Abstract syntax productions
+
+Q822-PM-ASN1Module {ccitt(0) recommendation(0) q(17) q822(822) asn1Module(2)
+q822ASN1Module(0)}
+
+DEFINITIONS IMPLICIT TAGS ::=
+
+BEGIN
+
+-- EXPORTS *everything*
+
+IMPORTS
+
+AttributeId, ObjectInstance, ObjectClass,
+
+FROM
+
+CMIP-1 {joint-iso-ccitt ms(9) cmip(1) version1(1) protocol(3)}
+
+AttributeList
+
+FROM Attribute-ASN1Module {joint-iso-ccitt ms(9) smi(3) part2(2) asn1Module(2) 1}
+
+SeverityIndicatingThreshold, SeverityIndicatingGaugeThreshold
+
+FROM
+
+MetricModule {joint-iso-ccitt ms(9) function(2) part11(11) asn1Module(2) 0}
+
+TimeInterval
+
+FROM
+
+Q821-ASN1Module {ccitt(0) recommendation(0) q(17) q821(821) ans1Module(2)
+q821ASN1Module(0)};
+
+q822InformationModel OBJECT IDENTIFIER ::=
+{ccitt(0) recommendation(0) q(17) q822(822) informationModel(0)}
+
+q822ObjectClass OBJECT IDENTIFIER ::=
+{q822InformationModel managedObjectClass(3)}
+
+q822Package OBJECT IDENTIFIER ::=
+{q822InformationModel package(4)}
+
+q822Attribute OBJECT IDENTIFIER ::=
+{q822InformationModel managedObjectClass(7)}
+
+q822NameBinding OBJECT IDENTIFIER ::=
+{q822InformationModel nameBinding(6)}
+
+defaultCurrentDataSuspectIntervalFlag
+SuspectIntervalFlag ::= FALSE
+
+defaultReportAllAttributes
+ReportAllAttributes ::= FALSE
+
+defaultSuppressAdditionalThresholds
+SuppressAdditionalThresholds ::= FALSE
+
+CounterThresholdAttributeList ::= SET OF CounterThresholdSetting
+
+CounterThresholdSetting ::= SEQUENCE {
+ attributeId AttributeId,
+ severityIndicatingThreshold SeverityIndicatingThreshold
+}
+
+ElapsedTime ::= CHOICE {
+ elapsedTime TimeInterval,
+ notAvailable NULL
+}
+
+GaugeThresholdAttributeList ::= SET OF GaugeThresholdSetting
+
+GaugeThresholdSetting ::= SEQUENCE {
+ attributeId AttributeId,
+ severityIndicatingGaugeThreshold SeverityIndicatingGaugeThreshold
+}
+
+```
+
+}
+
+HistoryRetention ::= INTEGER
+
+MaxSuppressedIntervals ::= INTEGER
+
+MonitoredEntityTypes ::= SET OF ObjectClass
+
+NumSuppressedIntervals ::= INTEGER
+
+PeriodEndTime ::= GeneralizedTime
+
+ReportAllAttributes ::= BOOLEAN
+
+SuppressAdditionalThresholds ::= BOOLEAN
+
+SuspectIntervalFlag ::= BOOLEAN
+
+ThresholdDataInstance ::= SET OF ObjectInstance
+
+END
+
+```
+
+### 4.3.6 Support objects from other CCITT Recommendations
+
+The following object classes defined in Recommendations X.738, Summarization Function, X.734, Event Report Management Function and X.735, the Log Management Function, can be used to support the Performance Management functions specified in this Recommendation.
+
+#### 4.3.6.1 Support objects from the summarization function
+
+The following object classes defined in ITU-T Recommendation X.738 can be used to support the Performance Management functions specified in this Recommendation:
+
+- dynamicScanner;
+- meanScanner;
+- meanVarianceScanner;
+- minMaxScanner;
+- simplecanner;
+- scanReportRecord.
+
+#### 4.3.6.2 Support objects from definition of management information
+
+The following support object classes (or their subclasses), defined in CCITT Recommendation X.721, can be used to support the Performance Management functions specified in this Recommendation:
+
+- discriminator;
+- eventForwardingDiscriminator;
+- eventLogRecord;
+- log;
+- logRecord.
+
+### 4.3.7 Performance management control
+
+The Performance Management Control object may be required to accomodate the following requirement which has been specified:
+
+On a per NE basis provide an alarm if the minimum designed duration is about to be violated with retention of the last n records for each object instance.
+
+The definition of this object is for further study.
+
+## **4.4 Performance management service definition**
+
+This Recommendation does not define any new services.
+
+## **4.5 Functional unit definitions**
+
+The following functional units defined in CCITT Recommendation X.730 may be negotiated for the purpose of managing the objects defined in this Recommendation:
+
+- control;
+- monitor;
+- objectEvents.
+
+The following functional units defined in CCITT Recommendation X.731 may be negotiated for the purpose of managing the objects defined in this Recommendation:
+
+- stateChangeReporting.
+
+The following functional units defined in CCITT Recommendation X.733 may be negotiated for the purpose of managing the objects defined in this Recommendation:
+
+- alarmReporting.
+
+The following functional units defined in CCITT Recommendation X.738 may be negotiated for the purpose of managing the objects defined in this Recommendation:
+
+- summarization event reporting functional unit.
+
+# **5 Protocol**
+
+## **5.1 Abstract syntax**
+
+### **5.1.1 Managed objects**
+
+#### **5.1.1.1 Referenced managed objects**
+
+This Recommendation references the following support managed objects for which the abstract syntax is specified in ITU-T Recommendation X.739:
+
+scanner.
+
+This Recommendation references the following support managed objects for which the abstract syntax is specified in CCITT Recommendation X.721:
+
+top.
+
+#### **5.1.1.2 Defined managed objects**
+
+This Recommendation defines the following managed objects:
+
+- a) currentData;
+- b) historyData;
+- c) thresholdData.
+
+### **5.1.2 Attributes**
+
+#### **5.1.2.1 Attributes imported from the metric objects and attributes function**
+
+This Recommendation references the following management attributes defined in ITU-T Recommendation X.739:
+
+granularityPeriod.
+
+#### **5.1.2.2 Attributes imported from the summarization function**
+
+This Recommendation references the following management attributes defined in ITU-T Recommendation X.738:
+
+- a) numericAttributeIdArray;
+- b) onceReportAttributeIdList;
+- c) scanAttributeIdList.
+
+#### **5.1.2.3 Attributes imported from definition of management information**
+
+This Recommendation references the following management attributes, the abstract syntax of which is specified in CCITT Recommendation X.721:
+
+discriminatorConstruct.
+
+#### **5.1.2.4 Attributes defined in this Recommendation**
+
+This Recommendation defines the following management attributes, the abstract syntax of which is specified in 4.3.3:
+
+- a) counterThresholdAttributeList;
+- b) elapsedTime;
+- c) gaugeThresholdAttributeList;
+- d) historyDataId;
+- e) historyRetention;
+- f) maxSuppressedIntervals;
+- g) measurementList;
+- h) monitoredEntityTypes;
+- i) numSuppressedIntervals;
+- j) observedObjectClass;
+- k) reportAllAttributes;
+- l) periodEndTime;
+- m) suppressAdditionalThresholds;
+- n) suspectIntervalFlag;
+- o) thresholdDataId;
+- p) thresholdDataInstance.
+
+### **5.1.3 Notifications**
+
+#### **5.1.3.1 Referenced notifications**
+
+This Recommendation references the following events defined in CCITT Recommendation X.730:
+
+- a) objectCreation;
+- b) objectDeletion;
+- c) attributeValueChange.
+
+This Recommendation references the following events defined in CCITT Recommendation X.731:
+
+stateChange.
+
+This Recommendation references the following events defined in CCITT Recommendation X.733 and used as described in 4.3.2.13:
+
+qualityofServiceAlarm.
+
+This Recommendation references the following events defined in ITU-T Recommendation X.738:
+
+scanReport.
+
+## 5.2 Negotiation of functional units
+
+Within the Systems management application context, the mechanism for negotiating the functional units is described by CCITT Recommendation X.701.
+
+NOTE – This subject requires further study.
+
+# 6 Relationship with other Recommendations
+
+This Recommendation uses definitions from CCITT Recommendation X.721.
+
+This Recommendation uses services defined in CCITT Recommendation X.730 for the creation and deletion of managed objects, the retrieval and update of attributes, the notifications on object creation, object deletion and attribute value changes.
+
+This Recommendation uses services defined in CCITT Recommendation X.731 for the notification of state changes.
+
+This Recommendation uses services defined in ITU-T Recommendation X.733 for the reporting of alarms.
+
+This Recommendation uses definitions and services from ITU-T Recommendation X.738.
+
+The incorporation of the metric objects as defined in ITU-T Recommendation X.739 is for further study.
+
+# 7 Conformance
+
+There are two conformance classes: general conformance class and dependent conformance class. A system claiming to implement the elements of procedure for system management services referenced by this Recommendation shall comply with the requirements for either the general or the dependent conformance class as defined in the following clauses. The supplier of the implementation shall state the class to which the conformance is claimed.
+
+NOTE – The use of the two terms “general conformance class” and “dependent conformance class”, is under review. However, this Recommendation continues to use these terms in order to be consistent with CCITT Rec. X.701 | ISO/IEC 10040 and other Recommendations and Standards under the general title Information Technology – Open Systems Interconnection – Systems Management. When a final answer to ISO/IEC JTC1 SC21 Question Q1/49.9 (on the long term solution to general and dependent conformance) has been approved, it is intended to clarify and/or correct this conformance clause together with the related clauses in those other Standards.
+
+## 7.1 General conformance class requirements
+
+A system claiming general conformance shall support this function for all managed object classes that import the management information defined in this Recommendation.
+
+NOTE – This is applicable to all subclasses of the management support object classes defined in this Recommendation.
+
+### 7.1.1 Static conformance
+
+The system shall:
+
+- a) support the role of manager or agent or both, with respect to the pmControl functional unit;
+- b) for each supported package defined in 4.3, support the transfer syntax derived from the encoding rules specified in CCITT Recommendation X.209 and named {joint-iso-ccitt asn1(1) basicEncoding(1)}, for the purpose of generating and/or interpreting the MAPDUs defined by the abstract data types referenced in 5.1.2 and 5.1.3 for the role supported in a) above;
+- c) when acting in the agent role, support at least one or more instances of the currentData managed object class or any of its subclasses;
+- d) a system need not support sending all of the named types within ITU-T Recommendation X.739 MetricModule.TimePeriod CHOICE.
+
+### 7.1.2 Dynamic conformance
+
+The system shall, in the role(s) for which conformance is claimed, support the elements of procedure defined in:
+
+- CCITT Recommendation X.730, for the PT-GET, PT-CREATE, PT-DELETE, PT-SET services.
+- ITU-T Recommendation X.738, for the emission of scan reports, if the scheduledPMReportPkg is supported.
+- CCITT Recommendation X.733, for the quality of service alarm reporting and used as described in 4.3.2.13, if the thresholdPkg is supported.
+- CCITT Recommendation X.730 | ISO/IEC 10164-1 for the Object creation reporting and Object deletion reporting, if the create delete notifications package is supported.
+- CCITT Recommendation X.730 | ISO/IEC 10164-1 for the Attribute value change reporting services, if the attribute value change notification package is supported.
+- CCITT Recommendation X.731 | ISO/IEC 10164-2 for the State change reporting service, if the state change notification package is supported.
+
+## 7.2 Dependent conformance class requirements
+
+### 7.2.1 Static conformance
+
+The system shall:
+
+- a) for each supported package defined in 4.3, support the transfer syntax derived from the encoding rules specified in CCITT Recommendation X.209 and named {joint-iso-ccitt asn1(1) basicEncoding(1)}, for the purpose of generating and/or interpreting the MAPDUs defined by the abstract data types referenced in 5.1.2 and 5.1.3, as required by a referencing specification;
+- b) support one or more instances of the PM object classes defined in this Recommendation or any of their subclasses, when acting in the agent role;
+- c) a system need not support sending all of the named types within the MetricModule.TimePeriod CHOICE.
+
+### 7.2.2 Dynamic conformance
+
+The system claiming dependent conformance shall support the elements of procedure referenced by this Recommendation, as required by the referencing specification to implement the specified subset of functionality.
+
+## 7.3 Conformance to support managed object definitions
+
+The performance management objects supported by the open system shall comply with the specification in clause 4. For minimum conformance to the support managed objects defined in this Recommendation, at least one of the following packages: historyRetentionPkg, measurementListPkg, scheduledPMReportPkg or thresholdPkg of the currentData object
+
+# Annex A
+
+## Performance monitoring parameters
+
+(This annex does not form an integral part of this Recommendation)
+
+This Annex is provided as a guide and contains examples of how performance parameters could be defined as managed object attributes. Any specification that requires to use any of the examples provided here needs to formally include the attribute definition in that specification before it can be used.
+
+## A.1 Abbreviations
+
+| | |
+|----------|-------------------------------------------------|
+| AISS | Alarm Indication Signal Second |
+| AISSFE | Alarm Indication Signal Second Far End |
+| AVA | Attribute Value Assertion |
+| CSS | Controlled Slip Second |
+| CSSFE | Controlled Slip Second Far End |
+| CV | Code Violation |
+| CVCP | Code Violation, CP-bit Parity |
+| CVCPFE | Code Violation, CP-bit Parity Far End |
+| CVCRC | Code Violation, Cyclic Redundancy Check |
+| CVCRCFE | Code Violation, Cyclic Redundancy Check Far End |
+| CVFE | Code Violation Far End |
+| CVP | Code Violation, P-bit |
+| ES | Errored Second |
+| ESA | Errored Second, type A |
+| ESACP | Errored Second, type A, CP-bit |
+| ESACPF | Errored Second, type A, CP-bit Far End |
+| ESACRC | Errored Second, type A, CRC |
+| ESACRCFE | Errored Second, type A, CRC Far End |
+| ESAFE | Errored Second, type A, Far End |
+| ESAP | Errored Second, type A, P-bit |
+| ESB | Errored Second, type B |
+| ESBCP | Errored Second, type B, CP-bit |
+| ESBCPF | Errored Second, type B, CP-bit Far End |
+| ESBCRC | Errored Second, type B, CRC |
+| ESBCRCFE | Errored Second, type B, CRC Far End |
+| ESBFE | Errored Second, type B, Far End |
+| ESBP | Errored Second, type B, P-bit |
+
+| | |
+|----------|-----------------------------------------------------------------|
+| ESCP | Errored Second, CP-bit Parity |
+| ESCPFE | Errored Second, CP-bit Parity Far End |
+| ESCRC | Errored Second, Cyclic Redundancy Check |
+| ESCRCFE | Errored Second, Cyclic Redundancy Check Far End |
+| ESFE | Errored Second Far End |
+| ESP | Errored Second, P-bit |
+| LOSS | Loss of Signal Second |
+| PSC | Protection Switching Count |
+| PSD | Protection Switching Duration |
+| SAS | SEF/AIS Severely Errored Framing Alarm Indication Signal Second |
+| SASFE | SAS Far End |
+| SES | Severely Errored Second |
+| SESCP | Severely Errored Second, CP-bit |
+| SESCPFE | Severely Errored Second, CP-bit Far End |
+| SESCRC | Severely Errored Second, CRC |
+| SESCRCFE | Severely Errored Second, CRC Far End |
+| SESFE | Severely Errored Second Far End |
+| SESP | Severely Errored Second-Path |
+| UAS | Unavailable Second |
+| UASFE | Unavailable Second Far End |
+
+## A.2 Performance monitoring parameters attribute templates
+
+### A.2.1 Alarm indication signal second (AISS)
+
+#### aISS ATTRIBUTE
+
+**DERIVED FROM "Recommendation X.721:1992": counter;**
+**MATCHES FOR EQUALITY, ORDERING;**
+**BEHAVIOUR aISSBehaviour BEHAVIOUR**
+**DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing one or more AIS defects.”
+
+;;
+**REGISTERED AS {xx};**
+
+### A.2.2 Alarm indication signal second far end (AISSFE)
+
+#### aISSFE ATTRIBUTE
+
+**DERIVED FROM "Recommendation X.721:1992": counter;**
+**MATCHES FOR EQUALITY, ORDERING;**
+**BEHAVIOUR aISSFEBehaviour BEHAVIOUR**
+**DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing one or more AISs which were received by the far end terminal.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.3 Controlled slip second (CSS)**
+
+#### **cSS ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR cSSBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing one or more controlled slips.”
+
+**::
+REGISTERED AS {xx};**
+
+### **A.2.4 Controlled slip second far end (CSSFE)**
+
+#### **cSSFE ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR cSSFEBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing one or more controlled slips which were received by the far end terminal.”
+
+**::
+REGISTERED AS {xx};**
+
+### **A.2.5 Code Violation (CV)**
+
+#### **cV ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR cVBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing one or more code violations.”
+
+**::
+REGISTERED AS {xx};**
+
+### **A.2.6 Code violation, CP-bit parity (CVCP)**
+
+#### **cVCP ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR cVCPBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute is counted when a CP-bit parity violation is detected in an M-frame.”
+
+**::
+REGISTERED AS {xx};**
+
+### **A.2.7 Code violation, CP-bit parity far end (CVCPFE)**
+
+#### **cVCPFE ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR cVCPFEBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute is counted when a CP-bit parity violation is detected in an M-frame which was received by the far end terminal.”
+
+**::
+REGISTERED AS {xx};**
+
+### **A.2.8 Code violation, cyclic redundancy check (CVCRC)**
+
+#### **cVCRC ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR cVCRCBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute is counted when a CRC-9 violation is detected over 3 consecutive M-frames.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.9 Code violation, cyclic redundancy check far end (CVRCFE)**
+
+#### **cVRCFE ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR cVRCFEBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute is counted when a CRC-9 violation is detected over 3 consecutive M-frames and received by the far end terminal.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.10 Code violation far end (CVFE)**
+
+#### **cVFE ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR cVFEBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing one or more code violations which were received by the far end terminal.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.11 Code violation, P-bit (CVP)**
+
+#### **cVP ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR cVPBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute is counted when a P-bit parity violation is detected in an M-frame.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.12Errored second (ES)**
+
+#### **eS ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing one or more digital transmission errors.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.13 Errored second, type A (ESA)**
+
+#### **eSA ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSABehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing one and only one digital transmission error.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.14 Errored second, type A, CP-bit (ESACP)**
+
+#### **eSACP ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSACPBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing one and only one CP-bit parity error.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.15 Errored second, type A, CP-bit far end (ESACPFE)**
+
+#### **eSACPFE ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSACPFEBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing one and only one CP-bit parity error, which was received by the far end terminal.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.16 Errored second, type A, CRC (ESACRC)**
+
+#### **eSACRC ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSACRCBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing one and only one CRC-9 error.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.17 Errored second, type A, CRC far end (ESACRCFE)**
+
+#### **eSACRCFE ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSACRCFEBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing one and only one CRC-9 error and received by the far end terminal.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.18 Errored second, type A, far end (ESAFE)**
+
+#### **eSAFE ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSAFEBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing one and only one digital transmission error which was received by the far end terminal.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.19 Errored second, type A, P-bit (ESAP)**
+
+#### **eSAP ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSAPBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing one and only one P-bit parity error.”
+
+**::
+REGISTERED AS {xx};**
+
+### **A.2.20 Errored second, type B (ESB)**
+
+#### **eSB ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSBBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing no less than two, and no more than X digital transmission errors.”
+
+**::
+REGISTERED AS {xx};**
+
+### **A.2.21 Errored second, type B, CP-bit (ESBCP)**
+
+#### **eSBCP ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSBCPBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing no less than two, and no more than X CP-bit parity errors.”
+
+**::
+REGISTERED AS {xx};**
+
+### **A.2.22 Errored second, type B, CP-bit far end (ESBCPFE)**
+
+#### **eSBCPFE ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSBCPFEBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing no less than two, and no more than X CP-bit parity errors, which were received by the far end terminal.”
+
+**::
+REGISTERED AS {xx};**
+
+### **A.2.23 Errored second, type B, CRC (ESBCRC)**
+
+#### **eSBCRC ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSBCRCBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing no less than two, and no more than X CRC-9 errors.”
+
+**::
+REGISTERED AS {xx};**
+
+### **A.2.24 Errored second, type B, CRC far end (ESBCRCFE)**
+
+#### **eSBCRCFE ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSBCRCFEBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing no less than two, and no more than X CRC-9 errors and received by the far end terminal.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.25 Errored second, type B, far end (ESBFE)**
+
+#### **eSBFE ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSBFEBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing no less than two, and no more than X digital transmission errors which were received by the far end terminal.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.26 Errored second, type B, P-bit (ESBP)**
+
+#### **eSBP ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSBPBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing no less than two, and no more than X P-bit parity errors.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.27 Errored second, CP-bit parity (ESCP)**
+
+#### **eSCP ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSCPBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute is a count of one second intervals containing the occurrence of one or more CVCP.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.28 Errored second, CP-bit parity far end (ESCPFE)**
+
+#### **eSCPFE ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSCPFEBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute is a count of one second intervals containing the occurrence of one or more CVCP, which was received at the far-end.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.29 Errored second, cyclic redundancy check (ESCRC)**
+
+#### **eSCRC ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSCRCBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute is a count of one second intervals containing the occurrence of one or more CVCRC.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.30 Errored second, cyclic redundancy check far end (ESCRCFE)**
+
+#### **eSCRCFE ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSCRCFEBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute is a count of one second intervals containing the occurrence of one or more CVCRC and received by the far end terminal.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.31 Errored second far end (ESFE)**
+
+#### **eSFE ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSFEBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing one or more digital transmission errors which were received by the far end terminal.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.32 Errored second, P-bit (ESP)**
+
+#### **eSP ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR eSPBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute is a count of one second intervals containing the occurrence of one or more CVP.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.33 Loss of signal second (LOSS)**
+
+#### **LOSS ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR LOSSBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing one or more loss of signal indicators.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.34 Protection switching count (PSC)**
+
+#### **pSC ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR pSCBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of the number of times a monitored resource is switched to protection. Although this attribute is not currently assigned to any specific object class, this attribute could be included as a member of the Additional Attribute List.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.35 Protection switching duration (PSD)**
+
+#### **pSD ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR pSDBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies the number of seconds that service was removed from the monitored resource. Although this attribute is not currently assigned to any specific object class, this attribute could be included as a member of the Additional Attribute List.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.36 SEF/AIS severely errored framing alarm indication signal second (SAS)**
+
+#### **sAS ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR sASBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute identifies a count of one second intervals containing one or more Severely Errored Framing (SEF) events.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.37 SEF/AIS second, far end (SASFE)**
+
+#### **sASFE ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR sASFEBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This Attribute identifies a count of one second intervals containing one or more Severely Errored Framing (SEF) events which were received by the far end terminal.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.38 Severely errored second (SES)**
+
+#### **sES ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR sESBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This Attribute identifies a count of one second intervals containing more than X digital transmission errors or a Severely Errored Framing (SEF) event.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.39 Severely errored second, CP-bit (SESCP)**
+
+#### **sESCP ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR sESCPBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This Attribute identifies a count of one second intervals containing more than X CP-bit parity errors or a Severely Errored Framing (SEF) event..”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.40 Severely errored second, CP-bit far end (SESCPFE)**
+
+#### **sESCPFE ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR sESCPFEBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This Attribute identifies a count of one second intervals containing more than X CP-bit parity errors or a Severely Errored Framing (SEF) event, which were received by the far end terminal.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.41 Severely errored second, CRC (SESCRC)**
+
+#### **sESCRC ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR sESCRCBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This Attribute identifies a count of one second intervals containing more than X CRC-9 errors or a Severely Errored Framing (SEF) event.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.42 Severely errored second, CRC far end (SESCRCFE)**
+
+#### **sESCRCFE ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR sESCRCFEBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This Attribute identifies a count of one second intervals containing more than X CRC-9 errors or a Severely Errored Framing (SEF) event and received by the far end terminal.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.43 Severely errored second far end (SESFE)**
+
+#### **sESFE ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR sESFEBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This Attribute identifies a count of one second intervals containing more than X digital transmission errors or a Severely Errored Framing (SEF) event received by the far end termination.”
+
+**REGISTERED AS {xx};**
+
+### **A.2.44 Severely errored second-path (SESP)**
+
+#### **sESP ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR sESPBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute is a count of one second intervals containing the occurrence of any of the following events: more than x CVs, one or more SEFs, one or more AISs. Candidate values of x are 447, 44 and 6 which correspond to BER threshold of $10^{-5}$ , $10^{-6}$ , and $1.5 \times 10^{-7}$ respectively. The default value of x is 44.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.45 Unavailable second (UAS)**
+
+#### **uAS ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR uASBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This Attribute identifies a count of one second intervals during which resource service was unavailable.”
+
+;;
+**REGISTERED AS {xx};**
+
+### **A.2.46 Unavailable second far end (UASFE)**
+
+#### **uASFE ATTRIBUTE**
+
+**DERIVED FROM "Recommendation X.721:1992": counter;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR uASFEBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This Attribute identifies a count of one second intervals during which resource service was unavailable which were received by the far end termination.”
+
+;;
+**REGISTERED AS {xx};**
+
+# **Annex B**
+
+## **Performance management information model overview**
+
+(This annex does not form an integral part of this Recommendation)
+
+## **B.1 Introduction**
+
+This annex provides a tutorial overview description of the Performance Management information model.
+
+## **B.2 Overview of the performance management information model**
+
+This overview intended to provide a conceptual framework for understanding how the various managed object classes are used to provide the performance management services described in the body of this recommendation. This subclause is not intended to be a comprehensive description of the model. The actual managed object class and attribute definitions are found in the body of this Recommendation. The figures in this appendix are used to illustrate concepts only and do not incorporate many details present in the managed object class and attribute definitions found in the Performance Management Model.
+
+The following list contains some of the capabilities provided by the PM information model:
+
+- *Notification of threshold crossing violation* – A *qualityOfServiceAlarm* notification may be emitted by the *currentData* object.
+- *History of threshold crossing data* – The *qualityOfServiceAlarm* notification may be stored in the log as an *alarmRecord* object for future retrievals.
+- *History of Performance Management data* – A *historyData* that mirrors the performance data information in the *currentData* object may be created at the end of each performance interval.
+- *Summary reporting of performance parameters* – A *simpleScanner* object may be used to scan multiple *historyData* or *currentData* objects to provide a summary report using a *scanReport* notification.
+- *Statistical reporting of performance parameters* – A statistical scanner object may be used to scan multiple *historyData* or *currentData* objects to provide a statistical report using a *statisticalReport* notification.
+- *Individual performance attributes retrieval capability* – The *currentData* class may be refined by specifying a technology specific subclass, e.g. V4 TTP, that contains technology specific performance attributes, e.g. ES.
+- *Measurement List retrieval capability* – For an instantiated *currentData* object (no subclassing) the *measurementList* attribute is used for the collection of performance parameters. For an instantiated subclass of the *currentData* object the *measurementList* attribute may be used to collect additional performance parameters.
+- *Notification of performance parameters* – A *scanReport* notification containing performance data may be emitted by the *Currentdata* object at the end of each performance interval.
+
+### **B.2.1 Collection of current PM data**
+
+Current PM data is collected from a managed object by use of the managed object class *currentData* or its subclasses. Instances of the *currentData* object class or its subclasses are contained within the managed object being observed. Each *currentData* object class or its subclasses is self-contained in that it specifies data collection aspects such as the collection interval, and the types of measurement data to be collected. The measurement data found in *currentData* object class or its subclasses represents the current state of the counters and indicators of PM data. The values of the attributes may change over the duration of the collection interval and those attributes that represent counter type measurements are reset at the end of the interval. The collection of PM data from a managed object is depicted in Figure B.1.
+
+### **B.2.2 History records**
+
+At the end of each collection interval, instances of *historyData* (or its subclasses) may be created that mirror the performance data information in a *currentData* instance (or its subclasses). The collection interval is specified in the attribute *granularityPeriod* inherited by the *currentData* class. The retention period (duration) of the created instance of *historyData* or its subclasses is denoted by the attribute *historyRetention*. When a new instance of *historyData* or a subclass is created, the oldest existing instance of the *historyData* object or a subclass may be deleted, provided that it has been retained for at least the duration prescribed.
+
+
+
+Diagram of PM data collection from a managed object. A large box labeled 'Managed Object being observed' contains a nested box for 'currentData or its subclasses'. This nested box lists attributes: 'scannerId', 'granularityPeriod', 'suspectFlag', 'Various PM attributes', and an ellipsis with the text '(Not all attributes shown)'. To the right of the 'currentData' box, lines connect its bottom edge to a second, slightly offset box, which in turn connects to a third box, also containing an ellipsis and '(Not all attributes shown)'. A small code 'T1150980-93/d04' is at the bottom right of the diagram.
+
+FIGURE B.1/Q.822
+**PM data collection from a managed object**
+
+### **B.2.3 Scheduled report**
+
+Instances of currentData or its subclasses may emit scheduled reports that contain performance data at the end of each collection interval. The collection interval is specified in the attribute granularityPeriod inherited by the currentData class. The performance data to be included in these reports are specified in the scanAttributeIdList and the numericAttributeIdArray attributes.
+
+### **B.2.4 Setting and reporting of PM thresholds**
+
+Thresholds are established by use of the managed object class thresholdData. The thresholdData objects specify the thresholds being applied. Threshold values in a thresholdData object may apply to multiple currentData objects and thresholdData objects are pointed to by currentData objects The currentData object or its subclasses indicates the collection interval used with the threshold. A qualityOfServiceAlarm notification is generated whenever a threshold is crossed. These notifications shall pass through an eventForwardingDiscriminator object to be reported and through the log object to be logged as an alarmRecord object.
+
+#### **B.2.4.1 Thresholds applying to a single managed object**
+
+A threshold may be specific to a single managed object. In this case, the thresholdData object is contained within the managed object being observed. A currentData object within the managed object points to a thresholdData object. This linkage is needed for consistency with the multiple managed object case. Figure B.2 illustrates thresholding for a single managed object instance.
+
+
+
+The diagram illustrates the structure of a threshold crossing notification. It consists of four main class boxes:
+
+- Log**: Contains attributes `logId` and `discriminatorConstruct`. It includes a nested box for `alarmRecord` with attributes `recordId` and `eventTime`, and a list of additional attributes. A note indicates "(Not all attributes shown)".
+- Managed Object Being Observed**: Contains a nested box for `currentData or its subclasses` with attributes `scannerId`, `granularityPeriod`, `suspectFlag`, `thresholdDataInstance`, and `Various PM Attributes`. It also has a list of additional attributes and a note "(Not all attributes shown)".
+- eventForwardingDiscriminator**: Contains attributes `discriminatorConstruct`, `destinationAddress`, `beginTime`, `endTime`, and `administrativeState`, followed by a list of additional attributes and a note "(Not all attributes shown)".
+- thresholdData**: Contains attributes `thresholdDataId` and `thresholdAttributeList`, followed by a list of additional attributes and a note "(Not all attributes shown)".
+
+Relationships and flow:
+
+- An arrow labeled "Quality of Service Alarm Notification" points from the `thresholdDataInstance` attribute in the `Managed Object Being Observed` class to the `alarmRecord` box in the `Log` class.
+- An arrow points from the `thresholdDataInstance` attribute in the `Managed Object Being Observed` class to the `thresholdData` class.
+- An arrow points from the `discriminatorConstruct` attribute in the `Log` class to the `eventForwardingDiscriminator` class.
+- A downward arrow from the `eventForwardingDiscriminator` class is labeled "M-Event Report of threshold crossing".
+- The text "T1150990-93/d05" is located in the bottom right corner.
+
+UML Class Diagram showing the relationship between Log, Managed Object Being Observed, eventForwardingDiscriminator, and thresholdData classes for a threshold crossing notification.
+
+FIGURE B.2/Q.822
+**Threshold for a single managed object**
+
+#### **B.2.4.2 Thresholds applying to multiple managed objects**
+
+It is sometimes desirable to have a threshold apply to a group of managed objects. In this case, the `thresholdData` object is external to the managed object being observed. It may be contained within the `managedElement` object. The `thresholdData` object is pointed to by all the `currentData` objects to which it applies. Figure B.3 illustrates a threshold applied to a group of managed objects. The historical retention of threshold crossing data is similar to the previous example and it is not shown in the Figure.
+
+
+
+```
+
+classDiagram
+ class thresholdData {
+ thresholdDataId
+ thresholdAttributeList
+ }
+ class ManagedObjectBeingObserved_1 [Managed Object Being Observed] {
+ currentData or its subclasses
+ scannerId
+ granularityPeriod
+ suspectFlag
+ thresholdDataInstance
+ Various PM Attributes
+ ...
+ (Not all attributes shown)
+ }
+ class ManagedObjectBeingObserved_2 [Managed Object Being Observed] {
+ or its subclasses
+ ...
+ riod
+ ...
+ alInstance
+ ...
+ ttributes
+ }
+ class eventForwardingDiscriminator {
+ discriminatorConstruct
+ destinationAddress
+ beginTime
+ endTime
+ administrativeState
+ ...
+ (Not all attributes shown)
+ }
+
+ thresholdData <|-- ManagedObjectBeingObserved_1
+ thresholdData <|-- ManagedObjectBeingObserved_2
+ ManagedObjectBeingObserved_1 --> eventForwardingDiscriminator : Quality of Service Alarm Notification
+ eventForwardingDiscriminator --> M_Event_Report : M-Event Report of threshold crossing
+
+```
+
+The diagram illustrates the relationship between a **thresholdData** class and a group of managed objects. The **thresholdData** class at the top left contains attributes **thresholdDataId** and **thresholdAttributeList**. It has two inheritance relationships with the **Managed Object Being Observed** class. The first **Managed Object Being Observed** class (left) contains attributes: **currentData or its subclasses**, **scannerId**, **granularityPeriod**, **suspectFlag**, **thresholdDataInstance**, and **Various PM Attributes**, with a note "(Not all attributes shown)". The second **Managed Object Being Observed** class (right) contains attributes: **or its subclasses**, **riod**, **alInstance**, and **ttributes**. Below these is the **eventForwardingDiscriminator** class, which contains attributes: **discriminatorConstruct**, **destinationAddress**, **beginTime**, **endTime**, and **administrativeState**, with a note "(Not all attributes shown)". An arrow labeled "Quality of Service Alarm Notification" points from the first **Managed Object Being Observed** class to the **eventForwardingDiscriminator** class. A final arrow points from the **eventForwardingDiscriminator** class to the text "M-Event Report of threshold crossing".
+
+UML Class Diagram showing thresholdData, Managed Object Being Observed, and eventForwardingDiscriminator classes and their relationships.
+
+T115 1000-93/d06
+
+FIGURE B.3/Q.822
+**Thresholds applied to a group of managed objects**
+
+### **B.2.5 Historical retention of PM data**
+
+The data found in the currentData object class or its subclasses consists of counters and measurements which are in the process of accumulating and changing during the interval. It is often useful to access the last completed interval. The data from the last completed interval, along with any data from preceding intervals, is termed historical data. A managed system may create an historyData object for each observed object at the end of each performance interval. Historical retention using historyData object is illustrated in Figure B.4.
+
+
+
+The diagram illustrates the structure of a 'Managed Object Being Observed'. It contains two main object classes: 'currentData or its subclasses' and 'historyData or its subclasses'. The 'currentData' object includes attributes: scannerId, granularityPeriod, suspectFlag, thresholdDataInstance, and 'Various PM Attributes'. A note '(Not all attributes shown)' is present. The 'historyData' object includes attributes: historyDataId, 'Various PM Attributes', and a note '(Not all attributes shown)'. The 'historyData' objects are shown as a stack of overlapping boxes, indicating multiple instances over time. A note '(Not all attributes shown)' is also present at the bottom left of the main container.
+
+Diagram showing the structure of 'currentData' and 'historyData' objects under 'Managed Object Being Observed'. 'currentData' includes scannerId, granularityPeriod, suspectFlag, thresholdDataInstance, and various PM attributes. 'historyData' includes historyDataId, various PM attributes, and a note '(Not all attributes shown)'.
+
+T1151010-93/d07
+
+FIGURE B.4/Q.882
+**History retention of PM data**
+
+### **B.2.6 Scheduled summary or statistical reports**
+
+Data produced by instances of the currentData class or its subclasses may be compiled into summary or statistical reports. The data collected by these objects at the end of each collection interval is stored in historyData objects. The simpleScanner managed object scans the common attributes to be observed in each of the selected objects according to a specified schedule and produces an aggregated report. In addition, the statistical scanners perform a statistical calculation and report its results. The schedule for scanning and reporting may be specified as part of the scanner objects. The notifications generated by the scanner may be processed by an event forwarding discriminator for reporting to the managing system. The generation of PM summarized or statistical reports is depicted in Figure B.5.
+
+
+
+The diagram illustrates the process of PM data summary or statistical reporting. It consists of three main components connected by arrows:
+
+- Managed Object Being Observed:** A large box containing a stack of smaller boxes representing *historyData or its subclasses*. Each subclass box contains *historyDataId* and *Various PM Attributes* (indicated by three dots). Below the stack of boxes are three more dots and the text "(Not all attributes shown)".
+- Simple or statistical scanner:** A box containing the following attributes: *scannerId*, *discriminatorConstruct*, *baseScanTimePeriod*, and *scanAttributeList*. The *scanAttributeList* contains three dots and the text "(Not all attributes shown)". An arrow labeled "Scan Attributes" points from the *Various PM Attributes* in the Managed Object to the *scanAttributeList*.
+- eventForwardingDiscriminator:** A box containing the following attributes: *discriminatorConstruct*, *destinationAddress*, *beginTime*, and *endTime*. Below these are three dots and the text "(Not all attributes shown)".
+
+Flow: An arrow labeled "scanReport or statisticalReport notification" points from the **Simple or statistical scanner** to the **eventForwardingDiscriminator**. A final arrow points from the bottom of the **eventForwardingDiscriminator** to the text "M-Event Reports of summarized Data or statistical Data".
+
+T1151020-93/d08
+
+Diagram showing the flow of PM data from a Managed Object Being Observed through a Simple or statistical scanner to an eventForwardingDiscriminator, resulting in M-Event Reports. The diagram includes nested boxes for historyData and various PM attributes, and lists of attributes for the scanner and discriminator.
+
+FIGURE B.5/Q.822
+**PM data summary or statistical reporting**
+
+# Annex C
+
+## PM model alternative
+
+(This annex does not form an integral part of this Recommendation)
+
+An alternative method of providing performance management is described in this non-normative annex. This alternative requires the instantiation of fewer object instances.
+
+The incorporation of this alternative into the standard is for further study.
+
+## C.1 Performance management model
+
+The key part in this proposal is a new scanner, hereafter called Difference Scanner. For each scanned attribute the difference scanner can report the current observed attribute value or the difference between the current observed value and the previous interval value. The difference scanner can be used to scan current data and history data.
+
+Because the difference scanner can scan non-resetable counters the scanned attributes can be defined in a Performance Data Component (PDC). This proposal does not require the use of currentData or historyData object classes. Furthermore the need for creation of current data and history data for different time intervals is eliminated because the time intervals are defined in the difference scanner.
+
+The PDC object class is not intended to be instantiated. Technology specific subclasses can be instantiated or incorporated into technology specific managed objects via single or multiple inheritance. Instantiated subclasses will be contained in the managed objects in the same way as the current data (CD) object.
+
+The PDC object class and the CD object class without any conditional packages in which the time interval is set to "infinity" are very similar.
+
+The PDC object class uses the same mechanism for thresholding as the CD object class except that for each thresholded counter type attribute a corresponding resetable attribute must be defined.
+
+This proposal introduces additional tools for performance monitoring. Guidelines are therefore proposed to aid the developers of technology specific standards, in choosing an alternative. It is proposed that the approach be decided on an MO class by MO class basis. For a given managed object class the options are:
+
+- 1) This MO class only allows PM using the CD mechanism.
+- 2) This MO class only allows PM using the PDC mechanism.
+- 3) Each Administration may decide (for this MO class) which method to use (it is an MO option).
+
+## C.2 Performance management information
+
+The major additions to Recommendation Q.822 for this proposal are the following support objects and associated management information.
+
+### C.2.1 Difference scanner
+
+#### **differenceScanner MANAGED OBJECT CLASS**
+
+**DERIVED FROM "Recommendation X.738:1992": homogeneousScanner;
+CHARACTERIZED BY differenceScannerPkg PACKAGE
+BEHAVIOUR differenceScannerBehaviour BEHAVIOUR
+DEFINED AS**
+
+“The differenceScanner is a class of managed support objects that makes observations of the same set of attributes across all managed object instances selected. For each attribute scanned, the value of that attribute may be reported or the difference between the current value and the value at the previous interval may be reported. Handling of counter overflow is a system internal matter.
+
+The difference scanner generates notifications. The notification includes the observed values or calculated difference values. If the attribute is listed in the differenceReport attribute list then the difference between the current observed value and the previous interval value is reported. If the attribute is not present in the differenceReport attribute list then observed value of the attribute is reported. The difference value can only be computed for attributes with INTEGER or REAL syntaxes.
+
+The observed values or computed difference values for attributes specified by the scan attribute identifier list are included in the notification paired with their attribute identifiers. Observed values or computed difference values for attributes specified by the numeric attribute identifier array are included in the notification without their attribute identifiers.
+
+The difference scanner generates the Scan Report Notification.
+
+If either the scan attribute identifier list or the numeric attribute identifier array is empty, then the corresponding parameter is not included in the summary report.
+
+The values of the numeric attribute identifier array, the difference report list, the once report attribute Id list, and the time stamp report mode attributes may only be modified by the manager system if the administrative state attribute has a value of "locked". If the attribute value change notification package is present, modification of these attributes shall result in an attribute value change notification.
+
+The attributes in the lists of attribute identifiers (scan attribute identifier list and numeric attribute identifier array) are scanned and their value or difference value is included in the report. At least one of these lists shall always be specified. When the selected managed object does not have the attribute in the scan identifier list, the attribute value is absent in the result. If any attribute in the numeric attribute identifier array is absent, a value of NULL shall be present.
+
+If a difference operation is required on an attribute and the value at the previous interval is not known, a value of NULL shall be reported. If the difference scanner was disabled or inactive and the previous interval was not scanned, a difference value of NULL shall be returned.
+
+If the once report attribute Id list package is present, then its associated reporting behaviour is exhibited.
+
+A scan report notification with the name of the scanned objects and observed or computed values is emitted at the end of each scan."
+
+;;
+
+#### ATTRIBUTES
+
+**numericAttributeIdArray GET-REPLACE,
+differenceReportList GET-REPLACE;
+NOTIFICATIONS
+scanReport;;;**
+
+#### CONDITIONAL PACKAGES
+
+**once ReportAttributeListPackage PRESENT IF "once report is supported";**
+
+**REGISTERED AS {q822ObjectClass x};**
+
+### C.2.2 Performance data component
+
+#### **performanceDataComponent MANAGED OBJECT CLASS**
+
+**DERIVED FROM "Recommendation X.721:1992": top
+CHARACTERIZED BY performanceDataPkg PACKAGE
+BEHAVIOUR performanceDataBehaviour BEHAVIOUR
+DEFINED AS**
+
+"The performanceDataComponent is a class of managed objects that contain the current performance data. This object class is not intended to be instantiated. Subclasses of this object class can be instantiated or incorporated into technology specific managed objects via single or multiple inheritance.
+
+Typically, the performance attributes may use the syntax type of either the counter attribute (with 'Count' syntax type) or it should be derived from the gauge attribute. Both the counter and gauge attributes are defined in CCITT Recommendation X.721. Typically counters are monotonically increasing.
+
+Thresholding cannot be used with monotonically increasing counters. Thresholding may only be applied to gauges or counters with built-in resetting intervals. Any internal resetting intervals must be specified explicitly in the behavior of the attribute as the counters cannot be reset externally.
+
+;;
+
+## **CONDITIONAL PACKAGES**
+
+### **thresholdPkg**
+
+**PRESENT IF "a Quality of Service Alarm Notification is to be emitted for threshold crossing:";**
+
+**REGISTERED AS {q822ObjectClass x};**
+
+## **C.3 Attribute definitions**
+
+### **C.3.1 Difference report list**
+
+#### **differenceReportList ATTRIBUTE**
+
+**WITH ATTRIBUTE SYNTAX DifferenceReportList;
+MATCHES FOR EQUALITY, SET-COMPARISON, SET-INTERSECTION;
+BEHAVIOUR differenceReportListBehaviour BEHAVIOUR
+DEFINED AS**
+
+“This attribute is a list of identifiers of attributes for which difference operations are to be performed. The identified attributes must be of either the integer or real type.”
+
+;;
+
+**REGISTERED AS {q822Attribute x};**
+
+## **C.4 Name binding definitions**
+
+### **differenceScanner-managedElement NAME BINDING**
+
+**SUBORDINATE OBJECT CLASS differenceScanner and SUBCLASSES;
+NAMED BY SUPERIOR OBJECT CLASS
+"Recommendation M.3100:1992": managedElement AND SUBCLASSES;
+WITH ATTRIBUTE scannerId;
+CREATE
+WITH-REFERENCE-OBJECT
+WITH-AUTOMATIC-INSTANCE-NAMING;
+DELETE
+ONLY-IF-NO-CONTAINED-OBJECTS;**
+
+**REGISTERED AS {q822NameBinding x};**
+
+## **C.5 Guidelines for the use of the model**
+
+This subclause will give some guidance on how technology specific standards should use the model. It should also give information on relevant factors in selecting options (particularly between the two major alternatives).
+
+This standard is generic. This means that in order to apply the model to a specific technology, it may be necessary to subclass the managed objects and add technology specific attributes. Different technologies will have different requirements for performance management. Different Administrations may have different philosophies for performance management. In particular, some technologies and Administrations may require extensive and sophisticated performance management capabilities. Other technologies and Administrations may require more rudimentary performance management capabilities.
+
+In order to accommodate those technologies and administrations requiring sophisticated performance management requirements and those with simpler performance management requirements, two approaches have been provided.
+
+The first approach involves collecting of performance data using the current data managed object (or its subclasses). This model provides considerable flexibility. It also requires three times the number of object instances (assuming history data is used). The second approach is based on the Performance Data Component (PCD) object class. Technology specific subclasses can be instantiated or incorporated in the managed Object by single or multiple inheritance. Using this approach entails the acceptance of some restrictions.
+
+The second approach is only applicable to the monitoring of managed object classes fitting the following restrictions:
+
+- 1) Current data and history data are not an explicit requirement. The MOD approach does not provide for structured retention of data (so that you can go back later and retrieve individual items). It does permit the logging of complete reports.
+- 2) The organization standardizing the monitored managed object class is willing to subclass the managed object class to inherit the necessary PM attributes.
+- 3) The monitored attributes are of the gauge or simple counter type. More complex counter types (mean values, etc.) or counters with special behavior (unavailable seconds) require the CD approach.
+- 4) Scheduled pm notifications directly from the managed object are not required.
+- 5) Only limited thresholding activity is required. Thresholding is allowed on gauges. If thresholds are used on event counters, then the thresholding interval must be built into the monitored object definition or attribute definition.
+- 6) Zero suppression is not required.
+- 7) Open pm attribute lists are not required (no measurementListPkg). All monitored attributes must be explicitly defined.
+- 8) Statistical operations on the counters (mean, min-max, etc.) are not supported in the present proposal.
+- 9) The counters cannot be reset or locked administratively. They are read only. They cannot be disabled independently of the monitored object.
+
+If these conditions are acceptable to a given technology, then the second approach is viable.
+
+In specifying the technology specific standard, three approaches can be taken for each monitored object:
+
+- 1) The monitored object can only be monitored using current data. In this case only the appropriate subclass of current and history data would be defined.
+- 2) The monitored object can only be monitored by instantiated or inherited subclass of the PDC object.
+- 3) Both approaches are provided. The monitoring approach is determined at object class instantiation. Both the current data subclass and the PDC subclass must be defined and included in the managed object as mutually excluding conditional packages. This approach provides maximum flexibility to an Administration, but could provide a challenge for the managing OS. In order to make the situation manageable, a restriction should be added that all instances of a managed object class within a given NE should adopt the same approach.
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.822.1-200110-I_PDF-E/raw.md b/marked/Q/T-REC-Q.822.1-200110-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..636b17db7027127bfc47aa793533630235b8d6cd
--- /dev/null
+++ b/marked/Q/T-REC-Q.822.1-200110-I_PDF-E/raw.md
@@ -0,0 +1,2940 @@
+
+
+
+
+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.822.1**
+
+(10/2001)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Q3 interface
+
+---
+
+**CORBA-based TMN performance management
+service**
+
+ITU-T Recommendation Q.822.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 AND No. 5 | Q.120-Q.249 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 |
+| DIGITAL EXCHANGES | Q.500-Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 |
+| General | Q.700 |
+| Message transfer part (MTP) | Q.701-Q.709 |
+| Signalling connection control part (SCCP) | Q.711-Q.719 |
+| Telephone user part (TUP) | Q.720-Q.729 |
+| ISDN supplementary services | Q.730-Q.739 |
+| Data user part | Q.740-Q.749 |
+| Signalling System No. 7 management | Q.750-Q.759 |
+| ISDN user part | Q.760-Q.769 |
+| Transaction capabilities application part | Q.770-Q.779 |
+| Test specification | Q.780-Q.799 |
+| Q3 INTERFACE | Q.800-Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 |
+| General | Q.850-Q.919 |
+| Data link layer | Q.920-Q.929 |
+| Network layer | Q.930-Q.939 |
+| User-network management | Q.940-Q.949 |
+| Stage 3 description for supplementary services using DSS1 | Q.950-Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 |
+| INTELLIGENT NETWORK | Q.1200-Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 |
+| BROADBAND ISDN | Q.2000-Q.2999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# **CORBA-based TMN performance management service**
+
+# **Summary**
+
+This Recommendation defines an information model to be used in telecommunications performance management (PM) based on CORBA. It defines in Interface Definition Language (IDL) a set of interfaces, notifications, and constants. The intent of this Recommendation is to define a CORBA/IDL model similar to that defined in ITU-T Recs. X.739 and Q.822 using CMISE. This Recommendation is compliant with CORBA modelling standards in ITU-T X.780, X.780.1, Q.816, Q.816.1 and M.3120.
+
+## **Source**
+
+ITU-T Recommendation Q.822.1 was prepared by ITU-T Study Group 4 (2001-2004) and approved under the WTSA Resolution 1 procedure on 7 October 2001.
+
+# FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2002
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU.
+
+# CONTENTS
+
+###### Page
+
+| | | |
+|-------|------------------------------------------------------|----|
+| 1 | Scope..... | 1 |
+| 2 | References..... | 1 |
+| 3 | Abbreviations..... | 2 |
+| 4 | Overview of the Performance Management Service ..... | 2 |
+| 4.1 | Requirements ..... | 2 |
+| 4.1.1 | Functional Requirements..... | 2 |
+| 4.1.2 | Design Requirements..... | 4 |
+| 4.2 | Service Modelling..... | 4 |
+| 4.2.1 | Scope ..... | 4 |
+| 4.2.2 | UML Model..... | 4 |
+| 4.2.3 | Containment Relationship ..... | 8 |
+| 4.3 | Service Interface Description..... | 8 |
+| 4.3.1 | Scanner ..... | 8 |
+| 4.3.2 | CurrentData ..... | 9 |
+| 4.3.3 | ThresholdData ..... | 11 |
+| 4.3.4 | HistoryDataFile ..... | 12 |
+| 4.3.5 | AbstractHistoryDataScanner ..... | 13 |
+| 4.3.6 | ListHistoryDataScanner..... | 13 |
+| 4.3.7 | ClassHistoryDataScanner ..... | 14 |
+| 4.3.8 | ScopedFilteredHistoryDataScanner..... | 15 |
+| 5 | Performance Management Service IDL ..... | 15 |
+| 5.1 | Imports ..... | 15 |
+| 5.2 | Forward Declarations..... | 16 |
+| 5.3 | Structures and Typedefs..... | 17 |
+| 5.4 | Exceptions..... | 18 |
+| 5.5 | Interfaces – Fine-grained ..... | 18 |
+| 5.5.1 | Scanner ..... | 19 |
+| 5.5.2 | CurrentData ..... | 20 |
+| 5.5.3 | ThresholdData ..... | 23 |
+| 5.5.4 | HDFile (HistoryDataFile)..... | 24 |
+| 5.5.5 | AbstractHDScanner (AbstractHistoryDataScanner) ..... | 25 |
+| 5.5.6 | ListHDScanner ..... | 26 |
+| 5.5.7 | ClassHDScanner..... | 27 |
+| 5.5.8 | ScopedFilteredHDScanner ..... | 28 |
+| 5.6 | Interfaces – Facade ..... | 29 |
+| 5.6.1 | Scanner_F ..... | 29 |
+
+| | Page |
+|--------------------------------------------------------------------------------------------------|-------------|
+| 5.6.2 CurrentData_F ..... | 30 |
+| 5.6.3 ThresholdData_F ..... | 32 |
+| 5.6.4 HDFile_F (HistoryDataFile)..... | 33 |
+| 5.6.5 AbstractHDScanner_F (AbstractHistoryDataScanner) ..... | 34 |
+| 5.6.6 ListHDScanner_F ..... | 35 |
+| 5.6.7 ClassHDScanner_F ..... | 35 |
+| 5.6.8 ScopedFilteredHDScanner_F ..... | 36 |
+| 5.7 Notifications..... | 37 |
+| 5.8 Name Binding ..... | 37 |
+| 5.8.1 ThresholdData ..... | 37 |
+| 5.8.2 HDFile ..... | 37 |
+| 5.8.3 AbstractHDScanner ..... | 38 |
+| 5.9 HDFileFormatConst..... | 38 |
+| Annex A – File Format ..... | 39 |
+| A.1 Text File Format BNF ..... | 39 |
+| A.2 Text File Format Description..... | 41 |
+| Annex B – CORBA File Format Convention ..... | 43 |
+| Appendix I – Example of CurrentDataValueType and HistoryDataValueType inheritance
usage ..... | 43 |
+
+# **CORBA-based TMN performance management service**
+
+# **1 Scope**
+
+This Recommendation defines a support service to be used in telecommunications performance management (PM) based on CORBA. It defines in Interface Definition Language (IDL) a set of interfaces in both fine-grained and facade version, data types, and constants. The intent of this Recommendation is to define a CORBA/IDL specification similar to that defined in ITU-T Recs. X.739 and Q.822 using CMISE. This Recommendation is compliant with proposed CORBA modelling standards in ITU-T Recs. X.780, X.780.1, Q.816, Q.816.1 and M.3120.
+
+# **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] OMG Document formal/99-10-07, *The Common Object Request Broker: Architecture and Specification*, Revision 2.3.1.
+- [2] OMG Document formal/2000-06-20, *Notification Service Specification*, Version 1.0.
+- [3] ITU-T Recommendation Q.816 (2001), *CORBA-based TMN services*.
+- [4] ITU-T Recommendation Q.816.1 (2001), *CORBA-based TMN services extensions to support coarse-grained interfaces*.
+- [5] ITU-T Recommendation X.780 (2001), *TMN guidelines for defining CORBA managed objects*.
+- [6] ITU-T Recommendation X.780.1 (2001), *TMN guidelines for defining coarse-grained CORBA managed objects interfaces*.
+- [7] ITU-T Recommendation M.3120 (2001), *CORBA Generic Network and NE Level Information Model*.
+- [8] ITU-T Recommendation X.721 (1992), *Information technology – Open systems interconnection – Structure of management information: Definition of management information*.
+- [9] ITU-T Recommendation X.738 (1993), *Information technology – Open Systems Interconnection – Systems management: Summarization function*.
+- [10] ITU-T Recommendation X.739 (1993), *Information technology – Open Systems Interconnection – Systems management: Metric objects and attributes*.
+- [11] ITU-T Recommendation Q.822 (1994), *Stage 1, stage 2 and stage 3 description for the Q3 interface – Performance management*.
+- [12] ITU-T Recommendation Q.823 (1996), *Stage 2 and stage 3 functional specifications for traffic management*.
+
+# **3 Abbreviations**
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|-------|--------------------------------------------------|
+| CMIP | Common Management Information Protocol |
+| CORBA | Common Object Request Broker Architecture |
+| DN | Distinguished Name |
+| FDN | Fully Distinguished Name |
+| GDMO | Guidelines for the Definition of Managed Objects |
+| NE | Network Element |
+| PM | Performance Management |
+| QoS | Quality of Service |
+| RDN | Relative Distinguished Name |
+| SNMP | Simple Network Management Protocol |
+| TL1 | Transaction Language 1 |
+| TMN | Telecommunications Management Network |
+| UML | Unified Modelling Language |
+
+# **4 Overview of the Performance Management Service**
+
+## **4.1 Requirements**
+
+### **4.1.1 Functional Requirements**
+
+Performance Measurement is used in two ways in TMN. One way is in the measurement of the performance of transport and protocol entities. In this use the measurements are subjected to thresholding and are collected for engineering and service history on a time scale that is not real time critical. This is the use supported by ITU-T Rec. Q.822 and technology-specific standards directly based on it. The other use of performance measurement is in support of network traffic management. In this application the measurements are not subjected to thresholding, but are collected periodically on a time scale that is needed to support the application of network management controls. The typical time scale for this collection has historically been 5 minutes. This is the use supported by ITU-T Rec. Q.823. ITU-T Rec. Q.823 reuses the mechanisms of ITU-T Rec. Q.822 together with the generic simple scanner of ITU-T Rec. X.738 to produce a single scan report that summarized the previous granularity period and is reported to a network management OS. These two uses of performance measurement are summarized in the Use Cases shown in Figure 1.
+
+
+
+```
+
+graph TD
+ subgraph TopRow [ ]
+ direction LR
+ A1((Administer Traffic Report))
+ A2((Administer PM))
+ A3((Report PM Data))
+ end
+
+ subgraph MiddleRow [ ]
+ direction LR
+ B1((Traffic Manager))
+ B2((Performance Manager))
+ end
+
+ subgraph BottomRow [ ]
+ direction LR
+ C1((Report traffic))
+ C2((Periodic Report Traffic))
+ C3((Monitor Performance))
+ end
+
+ B1 -- "request traffic report" --> C1
+ C2 -- "traffic report" --> B1
+ B1 -- "QOS threshold crossed" --> C3
+ B2 -- "get historical PM data" --> A3
+ C3 -- "QOS threshold crossed" --> B2
+ B1 --> A1
+ B2 --> A2
+
+ style TopRow fill:none,stroke:none
+ style MiddleRow fill:none,stroke:none
+ style BottomRow fill:none,stroke:none
+
+```
+
+T0415900-02
+
+Figure 1/Q.822.1 – Use cases for performance measurement. A diagram showing the interaction between TMN Management functions (Traffic Manager and Performance Manager) and various use cases (Administer Traffic Report, Administer PM, Report PM Data, Report traffic, Periodic Report Traffic, Monitor Performance).
+
+**Figure 1/Q.822.1 – Use cases for performance measurement**
+
+In summary, the TMN Management functions for performance management include data collection, data storage, thresholding, and data reporting.
+
+Performance data collection refers to the ability for a NE to collect the various PM data relating to a single monitored entity in that NE. This function allows a TMN manager to assign PM data collection interval, to suspend/resume PM data collection process, and to reset the performance monitoring counters.
+
+PM data storage refers to the capability for a NE to store historical PM data on each monitored entity for prescribed time duration. This function allows a TMN manager to establish a duration during which to maintain a specific record of PM historical data, to optionally screen historical data based on some criteria (e.g. suppress "all-zero" data), and to remove historical PM data at the end of time interval.
+
+PM thresholding refers to the ability for a NE to inform a TMN manager of any threshold crossing. It also provides the TMN manager with the means for establishing thresholding criteria.
+
+PM data reporting refers to the capability for a NE to report PM data on a scheduled basis, or as a result of a spontaneous request from the TMN manager. A report may contain data from a given monitored entity, or it can contain summarized data from a set of monitored entities. This function allows a TMN manager to request PM data, to allows/inhibits the emission of scheduled reports in the NE, and to screen the PM data reports on some criteria (e.g. suppress "all-zero" data).
+
+### 4.1.2 Design Requirements
+
+This Recommendation follows the information modelling guidelines defined in ITU-T Rec. X.780. In addition, this Recommendation tries to keep the model practical, simple and to make sense to users and manufacturers.
+
+## 4.2 Service Modelling
+
+### 4.2.1 Scope
+
+To support the functional requirements the performance management service needs `currentData` to collect performance measurements, `historyData` to store the collected measurements, `thresholdData` to specify the thresholds, and some specific scanner to report history data. Since `currentData` is inherited from `Scanner`, the model also needs `Scanner`.
+
+However, based on the modelling guidelines and the needs from existing and current PM applications, not all the capabilities defined for these managed objects in ITU-T Recs. X.739 and Q.822 are necessary at this point in time. As a result, some of the optional packages are not included in this model. In the future, if the need for a capability arises, the relevant package(s) will be reconsidered for inclusion.
+
+For most managed objects identified above, their IDL model can be derived from a translation of the X.739 and Q.822 GDMO. For `historyData`, however, direct translation may result in a potentially large number of managed objects. These entities are read only as historical data stores of current data and do not need to be CORBA interfaces. Instead, it is proposed that they be defined as CORBA valuetypes. The Q.822 translation will define a base valuetype for `historyData`, called `HistoryDataValueType`. This valuetype `HistoryDataValueType` will be accessible through methods on the `CurrentData` interface. When a current data is subclassed it is intended that the corresponding `HistoryDataValueType` be subclassed along with it.
+
+Since the data that needs to be stored is not in CORBA interfaces but `HistoryDataValueTypes`, to report history data, simply translating the GDMO homogeneous and simple scanners will not work. Instead, a new kind of scanner is needed – one that collects data from the `HistoryDataValueTypes`. This model attempts to keep the interfaces strongly typed whenever possible. This is because the collection of traffic data is computationally intensive since large amount of data must be collected and processed by the network manager in a short period of time.
+
+For this purpose, `HistoryDataScanner` is designed to retrieve history data saved under the relevant `CurrentData` objects. A file transfer mechanism is used in `HistoryDataScanner` for retrieving large amount of data since other techniques are likely to be both slower and to consume more computing and communication resources. The recommended mechanism supports the ability to control the generation of the file, the selection of the format of the file, and file production notification to the user, along with such information as is needed to obtain the file. However, specific file transfer mechanism and file administrations are outside the scope of this Recommendation.
+
+### 4.2.2 UML Model
+
+This clause illustrates the UML model for performance management. The model covers `Scanner`, `CurrentData`, `HistoryData` (represented as `HistoryDataValueType`), `ThresholdData`, and `HistoryDataScanner`. Since the model cannot fit onto one page, it is displayed in Figures 2, 3 and 4.
+
+The resulting model described in UML is shown in the next clause. The UML diagrams only show the model in the fine-grained approach, but these diagrams apply to both fine-grained and facade approaches. The facade IDL interface is mechanically translated from the fine-grained IDL interface as defined in ITU-T Rec. X.780.1.
+
+
+
+```
+
+classDiagram
+ class ManagedObject {
+ <>
+ ManagedObject
+ }
+ class ThresholdData {
+ <>
+ ThresholdData
+ counterThresholdListGet()
+ counterThresholdListSet()
+ counterThresholdListAdd()
+ counterThresholdListRemove()
+ gaugeThresholdListGet()
+ gaugeThresholdListSet()
+ gaugeThresholdListAdd()
+ gaugeThresholdListRemove()
+ }
+ class Scanner {
+ <>
+ Scanner
+ }
+ class CurrentData {
+ <>
+ CurrentData
+ supspectIntervalFlagGet()
+ supspectIntervalFlagSetDefault()
+ elapsedTimeGet()
+ historyRetentionGet()
+ historyRetentionSet()
+ getMostRecent()
+ getBetween()
+ }
+ class thresholdPackage {
+ <>
+ thresholdPackage
+ thresholdDataInstanceGet()
+ thresholdDataInstanceSet()
+ }
+ class ZeroSuppCurrentData {
+ <>
+ ZeroSuppCurrentData
+ numSuppressedIntervalsGet()
+ maxSuppressedIntervalsGet()
+ maxSuppressedIntervalsSet()
+ }
+ class thresholdCrossingEvent {
+ <>
+ thresholdCrossingEvent
+ qosAlarm()
+ }
+ class HistoryDataValueType {
+ <>
+ HistoryDataValueType
+ peroidEndTime : GeneralizedTimeType
+ grandularityPeriod : TimePeriodType
+ supspectIntervalFlag : boolean
+ numsupressedIntervals : numSupressedIntevalsType...
+ }
+
+ ManagedObject <|-- ThresholdData
+ ManagedObject <|-- Scanner
+ Scanner <|-- CurrentData
+ CurrentData --> thresholdPackage : 0..1 {if thresholding is supported}
+ CurrentData --> ZeroSuppCurrentData : 0..1 {if supported and filterSuppressionPkg is not present}
+ CurrentData ..> HistoryDataValueType : 0..historyRetention
+ ThresholdData --> thresholdPackage : 0..1
+ ThresholdData --> thresholdDataInstance : 1..n
+ thresholdPackage --> thresholdCrossingEvent : <>
+
+```
+
+UML Class diagram for CurrentData, HistoryData, and ThresholdData. The diagram shows ManagedObject as the base class for ThresholdData and Scanner. ThresholdData is associated with thresholdDataInstance (1..n) and thresholdPackage (0..1). CurrentData is associated with thresholdPackage (0..1) and ZeroSuppCurrentData (0..1). HistoryDataValueType is a value type associated with CurrentData (0..historyRetention).
+
+T0415910-02
+
+Figure 2/Q.822.1 – Class diagram for CurrentData, HistoryData, and ThresholdData
+
+
+
+```
+
+classDiagram
+ class ManagedObject {
+ getName()
+ objectClassGet()
+ objectKindGet()
+ packageGet()
+ creationSourceGet()
+ deletePolicyGet()
+ }
+ class Scanner {
+ granularityPeriodGet()
+ granularityPeriodSet()
+ operationalStateGet()
+ administrativeStateGet()
+ administrativeStateSet()
+ periodSynchronizationTimeGet()
+ periodSynchronizationTimeSet()
+ }
+ class AbstractHistoryDataScanner
+ class objectCreateDelete
+ class stateChangeNotification
+ class attributeValueChangNotification
+ class periodSync
+ class createDeleteEvent {
+ objectCreation()
+ objectDeletion()
+ }
+ class stateChangeEvent {
+ statechange()
+ }
+ class attributeValueChangeEvent {
+ avc()
+ }
+
+ ManagedObject <|-- Scanner
+ ManagedObject <|-- AbstractHistoryDataScanner
+ Scanner "0..1" *--> "0..1" objectCreateDelete : {if supported}
+ Scanner "0..1" *--> "0..1" stateChangeNotification : {if supported}
+ Scanner "0..1" *--> "0..1" attributeValueChangNotification : {if supported}
+ Scanner "0..1" *--> "0..1" periodSync : {if synchronizing granularity to a starting ti...}
+ objectCreateDelete --> createDeleteEvent : <>
+ stateChangeNotification --> stateChangeEvent : <>
+ attributeValueChangNotification --> attributeValueChangeEvent : <>
+
+```
+
+The diagram illustrates the class structure for a scanner. At the top is the **ManagedObject** class with methods: `getName()`, `objectClassGet()`, `objectKindGet()`, `packageGet()`, `creationSourceGet()`, and `deletePolicyGet()`. Below it, the **Scanner** class inherits from **ManagedObject** and includes methods: `granularityPeriodGet()`, `granularityPeriodSet()`, `operationalStateGet()`, `administrativeStateGet()`, `administrativeStateSet()`, `periodSynchronizationTimeGet()`, and `periodSynchronizationTimeSet()`. At the bottom, **AbstractHistoryDataScanner** also inherits from **ManagedObject**. The **Scanner** class has associations with four packages, each with a multiplicity of 0..1 and a guard condition: **objectCreateDelete** (if supported), **stateChangeNotification** (if supported), **attributeValueChangNotification** (if supported), and **periodSync** (if synchronizing granularity to a starting ti...). Each package has a corresponding **NotifyDispatch** class: **createDeleteEvent** (with `objectCreation()` and `objectDeletion()`), **stateChangeEvent** (with `statechange()`), **attributeValueChangeEvent** (with `avc()`), and **periodSync** (with `periodSynchronizationTimeGet()` and `periodSynchronizationTimeSet()`). Arrows labeled **<>** connect each package to its respective **NotifyDispatch** class. A small code **T0415920-02** is visible near the bottom right.
+
+UML Class diagram for scanner. It shows ManagedObject, Scanner, AbstractHistoryDataScanner, and several packages (objectCreateDelete, stateChangeNotification, attributeValueChangNotification, periodSync) and their relationships.
+
+Figure 3/Q.822.1 – Class diagram for scanner
+
+
+
+```
+
+classDiagram
+ class ManagedObject
+ class Scanner
+ class HistoryDataFile {
+ fileFormatGet()
+ fileLocationGet()
+ periodEndTimeGet()
+ fileRetentionDurationGet()
+ createHistoryDataFileMo()
+ hdFileDurationExpires()
+ }
+ class AbstractHistoryDataScanner {
+ supportedFileFormatListGet()
+ hdFileFormatGet()
+ hdFileFormatSet()
+ hdFileRetentionDurationGet()
+ hdFileRetentionDurationSet()
+ beginRelativeTimeGet()
+ beginRelativeTimeSet()
+ endRelativeTimeGet()
+ endRelativeTimeSet()
+ returnReport()
+ generateHDFileNow()
+ granularityPeriodExpires()
+ }
+ class ListHistoryDataScanner {
+ cdInstanceListGet()
+ cdInstanceListSet()
+ cdInstanceListAdd()
+ cdInstanceListRemove()
+ }
+ class ClassHistoryDataScanner {
+ cdClassSelectionListGet()
+ cdClassSelectionListSet()
+ cdClassSelectionListAdd()
+ cdClassSelectionListRemove()
+ }
+ class ScopedFilteredHistoryDataScanner {
+ baseGet()
+ baseSet()
+ scopeGet()
+ scopeSet()
+ filterGet()
+ filterSet()
+ languageGet()
+ languageSet()
+ }
+ class NotifyDispatch {
+ objectCreation
+ }
+
+ ManagedObject <|-- Scanner
+ ManagedObject <|-- HistoryDataFile
+ Scanner <|-- AbstractHistoryDataScanner
+ AbstractHistoryDataScanner <|-- ListHistoryDataScanner
+ AbstractHistoryDataScanner <|-- ClassHistoryDataScanner
+ AbstractHistoryDataScanner <|-- ScopedFilteredHistoryDataScanner
+ HistoryDataFile "0..n" --> AbstractHistoryDataScanner : <>
+ HistoryDataFile --> NotifyDispatch : <>
+
+```
+
+**Managed Object: ManagedObject**
+
+**Managed Object: Scanner**
+
+**Managed Object: HistoryDataFile**
+
+- fileFormatGet()
+- fileLocationGet()
+- periodEndTimeGet()
+- fileRetentionDurationGet()
+- create history data file mo()
+- hdFile Duration Expires()
+
+**Managed Object: AbstractHistoryDataScanner**
+
+- supportedFileFormatListGet()
+- hdFileFormatGet()
+- hdFileFormatSet()
+- hdFileRetentionDurationGet()
+- hdFileRetentionDurationSet()
+- beginRelativeTimeGet()
+- beginRelativeTimeSet()
+- endRelativeTimeGet()
+- endRelativeTimeSet()
+- returnReport()
+- generateHDFileNow()
+- granularity period expires()
+
+**Managed Object: ListHistoryDataScanner**
+
+- cdInstanceListGet()
+- cdInstanceListSet()
+- cdInstanceListAdd()
+- cdInstanceListRemove()
+
+**Managed Object: ClassHistoryDataScanner**
+
+- cdClassSelectionListGet()
+- cdClassSelectionListSet()
+- cdClassSelectionListAdd()
+- cdClassSelectionListRemove()
+
+**Managed Object: ScopedFilteredHistoryDataScanner**
+
+- baseGet()
+- baseSet()
+- scopeGet()
+- scopeSet()
+- filterGet()
+- filterSet()
+- languageGet()
+- languageSet()
+
+**NotifyDispatch: objectCreation**
+
+UML Class diagram for HistoryDataScanner and HistoryDataFile. The diagram shows a hierarchy of managed objects. At the top is ManagedObject. Below it are Scanner and HistoryDataFile. AbstractHistoryDataScanner inherits from Scanner. ListHistoryDataScanner, ClassHistoryDataScanner, and ScopedFilteredHistoryDataScanner inherit from AbstractHistoryDataScanner. HistoryDataFile has a 0..n association with AbstractHistoryDataScanner labeled '<>'. HistoryDataFile also has a '<>' association with NotifyDispatch objectCreation. Methods are listed for each class.
+
+T0415930-02
+
+Figure 4/Q.822.1 – Class diagram for HistoryDataScanner and HistoryDataFile
+
+### 4.2.3 Containment Relationship
+
+This clause illustrates the containment relationship of the CORBA interfaces defined in this Recommendation.
+
+
+
+```
+classDiagram
+ class ManagedElement["<> ManagedElement"]
+ class MonitoredObject["<> MonitoredObject"]
+ class CurrentData["<> CurrentData"]
+ class ThresholdData["<> ThresholdData"]
+ class AbstractHistoryDataScanner["<> AbstractHistoryDataScanner"]
+ class HistoryDataFile["<> HistoryDataFile"]
+
+ ManagedElement <|-- MonitoredObject : <>
+ ManagedElement <|-- ThresholdData : <>
+ ManagedElement <|-- AbstractHistoryDataScanner : <>
+ MonitoredObject <|-- CurrentData : <>
+ AbstractHistoryDataScanner <|-- HistoryDataFile : <>
+```
+
+T0415940-02
+
+UML diagram showing containment relationships between ManagedObject classes. ManagedElement is the root. MonitoredObject, ThresholdData, and AbstractHistoryDataScanner are contained by ManagedElement. CurrentData is contained by MonitoredObject. HistoryDataFile is contained by AbstractHistoryDataScanner.
+
+Figure 5/Q.822.1 – Containment relationship
+
+## 4.3 Service Interface Description
+
+### 4.3.1 Scanner
+
+A managed object of this interface represents the ability to retrieve values of attributes of managed objects and produce summary information from those values. This summary information may be made available in attributes, notifications, action replies, or some combination of these. Summary information may consist of observed attribute values or statistics calculated from these values (either over time or over managed objects).
+
+Observed attribute values are retrieved during a "scan" which is initiated periodically, at the end of each granularity period, provided that the granularity period is non-zero.
+
+The granularity period attribute indicates the length of the granularity period. The granularity period in the scanner object shall not be modified unless the value of the administrative state is 'locked'. If the period synchronization package is not present, the time at which a granularity period starts after the scanner is unlocked is a local matter.
+
+The administrative state attribute is used to suspend or resume the scanning function. If the administrative state has the value 'unlocked', the scanner is administratively permitted to perform scans. If the administrative state has the value 'locked', the scanner is administratively prohibited from performing scans.
+
+The operational state attribute represents the operational capability of the scanner to perform its functions.
+
+If the attribute value change notification package is present, then changes to the granularity period or period synchronization time shall cause attribute value change notifications to be emitted. If the state change notification package is present then changes to the operational state or administrative state shall cause state change notifications to be emitted. If the object create/delete notification package is present, then the creation or deletion of an object of scanner's subclass shall emit the corresponding create or delete notification.
+
+The following attributes are defined in the entity:
+
+- *administrativeState* – is used to activate and deactivate (administratively suspend and resume) the function performed by the scanner.
+- *granularityPeriod* – specifies the length of time during which the "scan" is performed.
+- *operationalState* – identifies whether or not the scanning function represented by this object is capable of performing its normal functions.
+
+The periodSynchronizationPackage is present if configurable agent internal synchronization of repeating time periods is required.
+
+The following attribute is defined in the periodSynchronizationPackage:
+
+- *periodSynchronizationTime* – contains the time to which a repeating time period is synchronized. The start of each time period is an integral number of periods before or after the time specified by this attribute.
+
+The Scanner interface is not instantiable.
+
+### 4.3.2 CurrentData
+
+#### 4.3.2.1 CurrentData
+
+The CurrentData object class, inherited from scanner, is a class of managed support objects that record the current performance data for monitoring purpose. The performance data (measurements) of monitored resources are modeled as attributes in the definition of subclasses of CurrentData since CurrentData cannot be instantiated. The objects that represent monitored resources contain the corresponding CurrentData objects in the name binding relationship.
+
+The measurements are collected for a time interval (e.g. 5 min.) specified by the granularityTime attribute. At the end of each interval, the elapsedTime attribute will be updated to the difference between the current time and the start of the present monitoring interval. The measurements, granularityTime, and suspectIntervalFlag are copied into a corresponding history data structure (represented as HistoryDataValueType). Furthermore, the periodEndTime of the history data structure is assigned to the current time.
+
+If historyRetention is greater than zero, then history data structures will be retained in the managed system for at least the duration equivalent to the number of intervals specified in the historyRetention attribute. During that time, history data can be accessed via a set of operations:
+
+- *getMostRecent* – will retrieve the most recent history data. The "most recent" means the most recent history data record saved, which may be several intervals before the current time because the historyRetention may be set to zero, or the measurements collected are all zero. It is possible the getMostRecent may not be able to retrieve any data. For example, all measurements are zeros (no history data is saved) or historyRetention has been set to zero.
+
+The boolean value returned by `getMostRecent` method indicates the availability of the data. True means the out parameter contains the data, and false, that the parameter is undefined.
+
+- `getBetween` – will retrieve a set of history data within a time window specified by start and end time parameters. The `resultIterator` is used to transfer large chunks of data. If `howMany` is not provided, then the initial amount of data returned is a local matter.
+
+The following attributes are defined in the entity:
+
+- `suspectIntervalFlag` – is used to indicate that the performance data for the current period may not be reliable. Some reasons for this occurring are:
+ - Suspect data were detected by the actual resource doing data collection.
+ - Transition of the `administrativeState` attribute to/from the 'lock' state.
+ - Transition of the `operationalState` to/from the 'disabled' state.
+ - The performance counters were reset during the interval.
+ - The `CurrentData` (or subclass) object instance was created during the monitoring period.
+- `elapsedTime` – represents the difference between the current time and the start of the present monitoring interval.
+- `historyRetention` – specifies the minimum number of intervals that the history data structure (just created) must be preserved.
+
+If `thresholdPackage` is present, the `CurrentData` object contains at least a pointer to a `ThresholdData` object. If any of the thresholds (defined in the referenced `ThresholdData` object) are violated, a Quality of Service (QoS) alarm notification is emitted by the `CurrentData` object. The `thresholdInfo` field of the alarm shall contain the measurement attribute which violates the threshold. If additional threshold crossing(s) occur during the current time interval then additional alarms shall be emitted as well.
+
+The `thresholdDataInstanceList` attribute contains a set of pointers to `ThresholdData` objects specified by managing system(s). Therefore, more than one QoS Alarm notification might be emitted for a single monitored attribute, and it is possible that the notifications might be conflicting. For example, one notification indicates alarm is on, the other cleared. It is the managing systems' responsibility to maintain the notification consistency.
+
+New thresholds resulting from modifying the `thresholdDataInstanceList` attribute, or from changing a threshold value in the referenced `ThresholdData` object, should take effect immediately. If an alarm condition exists previous to the occurrence of a threshold value change (i.e. an old threshold had been violated), and the new threshold value is outside the range of the old threshold value (e.g. in the case of an increasing counter, the new threshold value is greater than the old threshold value), and the current value of the measurement is within the allowable range of the new threshold value, then a QoS Alarm notification is emitted with a severity of 'clear'. If the new threshold value is set within the range of the old threshold value, such that the new threshold is violated, a QoS Alarm notification is emitted if an alarm condition is not already outstanding.
+
+The following attribute is defined in the `thresholdPackage`:
+
+- `thresholdDataInstanceList` – is a "list" attribute in which each item is a pointer to a `ThresholdData` object that contains threshold limits for performance parameters.
+
+The `zeroSuppressionPackage` is a conditional package of `CurrentData`. When this package is present and an interval terminates with 'all-zeros' performance measurements, no history data structure is created.
+
+The following attributes are defined in the zeroSuppressionPackage:
+
+- *numSuppressedIntervals* – is used to count the number of consecutive intervals for which suppression (i.e. non-creation of a history data structure) has occurred. This attribute reflects performance measurements up to, but not including, the current interval. This attribute gets incremented at the end of an interval if suppression has occurred. Otherwise, the attribute is reset. Or if it reaches maxSuppressedIntervals, a history data record is created and the attribute will be reset.
+- *maxSuppressedIntervals* – limits the maximum number of suppressed intervals that will be collected without creating a structure of the history data. The default value *-1* means that there is no limit on the number of consecutive suppressed intervals. On the other hand, the maxSuppressedIntervals is effectively equal to infinity.
+
+For example, consider an instance of (a subclass of) zero suppression CurrentData with maxSuppressedIntervals set to 32, and the interval set to 15 minutes. For record compression, it means that after 32 consecutive suppressed (e.g. all-zero) intervals (8 hours) at least one history data record (with all zero PM Parameters) will be generated with a count of 32. This ensures that at least one history data record per maxSuppressedIntervals will be created.
+
+The CurrentData interface is not instantiable.
+
+#### 4.3.2.2 HistoryData
+
+HistoryData, represented as HistoryDataValueType, will contain a copy of the performance measurements and other selected attributes that are present in a current data object at the end of the current interval (e.g. 5 min.). A new record of this valuetype structure is created at the end of each interval if historyRetention attribute in the current data object is greater than zero. This record will then be retained in the NE for at least the duration equivalent to the number of intervals specified in the historyRetention attribute.
+
+This generic valuetype models the history data. Specific current data objects (e.g. SDH/SONET current data objects) will be defined with specific history valuetypes, which are inherited from this generic HistoryDataValuetype valuetype.
+
+The following attributes are defined in the entity:
+
+- *periodEndTime* – indicates the time at the end of the interval.
+- *granularityPeriod* – is used to copy the same attribute from the CurrentData object.
+- *suspectIntervalFlag* – is used to copy the same attribute from the CurrentData object.
+- *numSuppressedIntervals* – indicates the number of suppressed intervals has occurred before the creation of this history valuetype record. It has default value 0. When copying from CurrentData object, the default value is used. When copying from CurrentData with ZeroSuppressionPackage, the corresponding attribute value is used.
+
+### 4.3.3 ThresholdData
+
+The ThresholdData object class is a class of managed support objects that contains the values of the threshold settings for the PM parameters. At least one of the counterThresholdListPackage or the gaugeThresholdListPackage must be instantiated.
+
+Thresholds are established by use of the managed object class ThresholdData. The ThresholdData objects specify the thresholds being applied. Threshold values in a ThresholdData object may apply to multiple CurrentData objects and ThresholdData objects are pointed to by CurrentData objects. The CurrentData (or its subclasses) object indicates the collection interval used with the threshold. A qualityOfServiceAlarm notification is generated whenever a threshold is crossed.
+
+A threshold may be specific to a single managed object. In this case, the `ThresholdData` object is contained within the managed object being observed. A `CurrentData` object within the managed object points to a `ThresholdData` object. This linkage is needed for consistency with the multiple managed object case.
+
+It is sometimes desirable to have a threshold apply to a group of managed objects. In this case, the `ThresholdData` object is external to the managed object being observed. It may be contained within the `ManagedElement` object. The `ThresholdData` object is pointed to by all the `CurrentData` objects to which it applies.
+
+If `createDeleteNotificationsPackage` is present, the creation or deletion of a threshold object will cause an `objectCreation` or `objectDeletion` notification to be emitted.
+
+If `attributeValueChangeNotificationPackage` is present, then any threshold change will cause an `attributeValueChange` notification being emitted.
+
+The `counterThresholdListPackage` is present if an instance supports it and the `gaugeThresholdListPackage` is not present.
+
+The following attribute is defined in the `counterThresholdListPackage`:
+
+- *counterThresholdList* – contains a set of threshold settings for performance attributes of the counter type (e.g. errored seconds). Each threshold setting consists of the attribute identifier, the threshold value and (optionally) the severity of the threshold-exceeded event.
+
+The `gaugeThresholdListPackage` is present if an instance supports it and the `counterThresholdListPackage` is not present.
+
+The following attribute is defined in the `gaugeThresholdListPackage`:
+
+- *gaugeThresholdList* – contains a set of threshold settings for performance attributes of the gauge type. Each threshold setting consists of the attribute identifier, the threshold value and (optionally) the severity of the threshold-exceeded event.
+
+### 4.3.4 HistoryDataFile
+
+`HistoryDataFile` is a subclass of `ManagedObject`. It maps to history data file one-to-one. Each history data file has one associated `HistoryDataFile` object. Each `HistoryDataFile` object has one underlying history data file. The `HistoryDataFile` object is created only after history data file is produced. The `HistoryDataFile` object is deleted immediately after history data file is purged.
+
+The managed system shall control the life-cycle of the `HistoryDataFile`. However, a destroy behavior that purges the history data file if `HistoryDataFile` object is deleted, is provided if the managing system wants to clean the history data file before expiration of file retention period.
+
+The `HistoryDataFile` object has the following attributes:
+
+- *fileLocation* – identifies file location in URL format. The time between reuse of same *fileLocation* for two different files shall be sufficiently beyond any possibility for confusion.
+- *fileFormat* – indicates which file format used.
+- *periodEndTime* – indicates the time at the end of the file generation.
+- *fileRetentionDuration* – indicates file retention period before the file is purged due to garbage collection of the managed system.
+
+When a history data file is generated and a `HistoryDataFile` object is created, an `objectCreation` notification will be sent from managed system to inform the managing system of the availability of the history data file. When a history data file is removed and the associated `HistoryDataFile` object is deleted, an `objectDeletion` notification could be sent from the managed system to the managing system if `objectDeleteNotificationPackage` is supported.
+
+Even though there is a HistoryDataFileFactory, a HistoryDataFile object shall never be created by the managing system. The HistoryDataFileFactory is meant to be used by the managed system.
+
+### 4.3.5 AbstractHistoryDataScanner
+
+AbstractHistoryDataScanner is a subclass of Scanner and a superclass of all other history data scanners. It is the collection of common attributes and operations of history data scanners. The AbstractHistoryDataScanner is not instantiable.
+
+History data scanners support scanning and reporting history data by providing the ability to control the generation of the history data file, the selection of the format of the file, and the notification of user when the file is produced.
+
+The AbstractHistoryDataScanner object has the following attributes:
+
+- *supportedFileFormatList* – indicates the supported file formats of the managed system since it may support more than one file format.
+- *hdFileFormat* – indicates which file format to use.
+- *fileRetentionDuration* – indicates the file retention period for all the history data files generated by this scanner.
+- *beginRelativeTime* – the begin time relative to the current time together with the end relative time defining a window to select history data. The negative value of begin relative time means past time.
+- *endRelativeTime* – the end time relative to the current time. The negative value of end relative time means past time. The zero value means no ending time which would result in periodical file generation until stopped by the managing system.
+- *granularityPeriod* (*inherited from Scanner*) – sets a time window so that the history data, with time stamps that fall into this window, will be reported within a file.
+
+Before setting any values to these attributes, the administrativeState has to be set to lock. And when the administrativeState is set to 'unlock', the periodical file generation begins. If the granularity period is zero, then there is no periodic file generation.
+
+At the end of each granularity period of the scanner, the history data scanner scans the historical data from a set of current data objects specified in the detailed scanner, collects any data if its period end time falls within the current granularity time interval, and generates a data file in a format indicated in hdFileFormat. When the file is produced, a HistoryDataFile object is created by the managed system and an objectCreation notification is emitted to the managing system. The source of objectCreation notification is the HistoryDataFile object that has just been created.
+
+The history data scanner has two operations for non-periodic history data reporting:
+
+- *returnHDReport* – returns a sequence of history data value types which period end-time falls between now and the end of last granularity period of the scanner.
+- *generateHDFFileNow* – generates history data file immediately instead of waiting till the end of next granularity period of the scanner. The period end-time of history data value type in this file shall be in between now and the end of last granularity period.
+
+### 4.3.6 ListHistoryDataScanner
+
+The ListHistoryDataScanner is a specialized history data scanner and subclass of AbstractHistoryDataScanner. It returns history data reports and files based on a simple object list.
+
+The ListHistoryDataScanner object has the following attribute:
+
+- *cdInstancesList* – contains a set of current data objects whose historical data needs to be scanned/reported to a file.
+
+Figure 6 diagram depicts a simple use case of ListHistoryDataScanner:
+
+
+
+```
+
+sequenceDiagram
+ participant hds1 as hds1 : ListHistoryDataScanner
+ participant cd1 as cd1 : CurrentData
+ participant cd2 as cd2 : CurrentData
+ participant hdf1 as hdf1 : HistoryDataFile
+ participant os as : operating system file
+ participant cde as : createDeleteEvent
+
+ Note left of hds1: granularity period expires()
+ hds1->>hds1:
+ hds1->>cd1: getBetween( , Integer, out HistoryDataIterator)
+ activate cd1
+ hds1->>os: write data to file()
+ deactivate cd1
+ hds1->>cd2: getBetween( , Integer, out HistoryDataIterator)
+ activate cd2
+ hds1->>os: write data to file()
+ deactivate cd2
+ Note right of hds1: continue until done with list
+ hds1->>cd2: getBetween( , Integer, out HistoryDataIterator)
+ activate cd2
+ hds1->>os: write data to file()
+ deactivate cd2
+ hds1->>hdf1: create history data file mo()
+ activate hdf1
+ hdf1->>cde: objectCreation()
+ activate cde
+ deactivate cde
+ Note left of hdf1: hdFile Duration Expires()
+ hdf1->>hdf1:
+ hdf1->>os: delete file()
+ activate os
+ deactivate os
+ hdf1->>cde: objectDeletion()
+ activate cde
+ deactivate cde
+ deactivate hdf1
+
+```
+
+UML Sequence diagram showing the interaction for a ListHistoryDataScanner use case. Lifelines: hds1 : ListHistoryDataScanner, cd1 : CurrentData, cd2 : CurrentData, hdf1 : HistoryDataFile, : operating system file, and : createDeleteEvent. The sequence starts with a self-call on hds1 (granularity period expires()), followed by getBetween() calls to cd1 and cd2. write data to file() messages are sent to the OS file lifeline. A loop labeled 'continue until done with list' contains another getBetween() and write data to file() call. After the loop, hds1 calls create history data file mo() on hdf1. hdf1 then calls objectCreation() on the createDeleteEvent lifeline. A self-call on hdf1 (hdFile Duration Expires()) is followed by a delete file() call to the OS file lifeline. Finally, hdf1 calls objectDeletion() on the createDeleteEvent lifeline.
+
+Figure 6/Q.822.1 – Use case of ListHistoryDataScanner
+
+### 4.3.7 ClassHistoryDataScanner
+
+The ClassHistoryDataScanner is a specialized history data scanner and subclass of AbstractHistoryDataScanner. It returns history data reports and files based on an object class list.
+
+The ClassHistoryDataScanner object has the following attribute:
+
+- *cdClassSelectionList* – contains a set of current data classes grouped by the containing ManagedObject (e.g. network equipment). The current data objects whose historical data needs to be scanned/reported to a file are those instances of the specified current data classes contained by the respective ManagedObject.
+
+Before the ClassHistoryDataScanner generates a new report or file, it shall re-evaluate matching current data instances for any added or deleted current data instances since the last scanning.
+
+### 4.3.8 ScopedFilteredHistoryDataScanner
+
+The ScopedFilteredHistoryDataScanner is a specialized history data scanner and subclass of AbstractHistoryDataScanner. It returns history data reports and files based on scoping and filtering.
+
+The ScopedFilteredHistoryDataScanner object has the following attributes:
+
+- *base* – base-managed object used for scoping.
+- *scope* – scope value as defined in ITU-T Rec. Q.816.
+- *filter* – constraint filter expression that is used to evaluate the matching objects.
+- *language* – a string indicating the language in which the filter expression is written.
+
+The current data objects whose historical data needs to be scanned/reported to a file are those current data objects selected through scoping and filtering operation. Before the ScopedFilteredHistoryDataScanner generates a new report or file, it shall re-apply the scoping and filtering operation to select the latest set of current data objects.
+
+# 5 Performance Management Service IDL
+
+```
+#ifndef _itut_q822_1_idl_
+#define _itut_q822_1_idl_
+
+#include
+#include
+#include
+#include
+#include
+#include
+
+#pragma prefix "itu.int"
+
+/**
+This IDL code is intended to be stored in a file named "itut_q822_1.idl"
+located in the search path used by IDL compilers installed on your system.
+*/
+
+/**
+This module, itut_q822dl, contains IDL definition based on objects defined
+in ITU-T Rec. Q.822. The IDL definitions in this file are the object interfaces.
+*/
+module itut_q822dl
+{
+
+/**
+
+5.1 Imports
+
+*/
+
+/**
+Types imported from itut_x780
+*/
+ typedef itut_x780::AdministrativeStateType AdministrativeStateType;
+ typedef itut_x780::DeletePolicyType DeletePolicyType;
+ typedef itut_x780::GeneralizedTimeType GeneralizedTimeType;
+ typedef itut_x780::Istring Istring;
+```
+
+```
+
+typedef itut_x780::IstringSetType IstringSetType;
+typedef itut_x780::MONameType MONameType;
+typedef itut_x780::MONameSetType MONameSetType;
+typedef itut_x780::NameBindingType NameBindingType;
+typedef itut_x780::OperationalStateType OperationalStateType;
+typedef itut_x780::PerceivedSeverityType PerceivedSeverityType;
+typedef itut_x780::ScopedNameSetType ScopedNameSetType;
+typedef itut_x780::UIDType UIDType;
+
+/**
+Types imported from itut_x780ct
+*/
+ typedef itut_x780ct::SeverityIndicatingThresholdType
+ SeverityIndicatingThresholdType;
+ typedef itut_x780ct::SeverityIndicatingGaugeThresholdSetType
+ SeverityIndicatingGaugeThresholdSetType;
+ typedef itut_x780ct::TimeIntervalType TimeIntervalType;
+ typedef itut_x780ct::TimePeriodType TimePeriodType;
+
+/**
+Types imported from itut_q816
+*/
+ typedef itut_q816::ScopeType ScopeType;
+ typedef itut_q816::FilterType FilterType;
+ typedef itut_q816::LanguageType LanguageType;
+
+/**
+Types imported from itut_m3120
+*/
+ typedef itut_m3120::ManagedElementNameType ManagedElementNameType;
+/**
+Interfaces imported from itut_x780
+
+itut_x780::ManagedObject
+itut_x780::ManagedObjectFactory
+*/
+
+/**
+
+```
+
+## 5.2 Forward Declarations
+
+```
+
+*/
+
+/**
+Interface forward declarations
+*/
+ interface Scanner;
+ interface HistoryDataIterator;
+ interface CurrentData;
+ interface ThresholdData;
+ interface HDFile;
+ interface AbstractHDScanner;
+ interface ListHDScanner;
+ interface ClassHDScanner;
+ interface ScopedFilteredHDScanner;
+
+/**
+Valuetype forward declarations
+*/
+
+```
+
+```
+
+valuetype ScannerValueType;
+valuetype CurrentDataValueType;
+valuetype HistoryDataValueType;
+valuetype ThresholdDataValueType;
+valuetype HDFileValueType;
+valuetype AbstractHDScannerValueType;
+valuetype ListHDScannerValueType;
+valuetype ClassHDScannerValueType;
+valuetype ScopedFiltedHDScannerValueType;
+
+```
+
+```
+/**
+```
+
+```
+Interface forward declarations
+```
+
+```
+*/
+```
+
+```
+
+typedef MONameType ScannerNameType;
+typedef MONameType CurrentDataNameType;
+typedef MONameType ThresholdDataNameType;
+typedef MONameType HDFileNameType;
+typedef MONameType AbstractHDScannerNameType;
+typedef MONameType ListHDScannerNameType;
+typedef MONameType ClassHDScannerNameType;
+typedef MONameType ScopedFiltedHDScannerNameType;
+
+```
+
+```
+/**
+```
+
+## 5.3 Structures and Typedefs
+
+```
+*/
+```
+
+```
+/**
+```
+
+```
+This data type defines a sequence of HistoryDataValueType. The order is significant.
+```
+
+```
+*/
+```
+
+```
+typedef sequence HistoryDataSeqValueType;
+```
+
+```
+typedef sequence CurrentDataNameSetType;
+```
+
+```
+typedef UIDType HDFileFormatType;
+```
+
+```
+typedef sequence HDFileFormatSetType;
+```
+
+```
+typedef Istring URLType;
+```
+
+```
+
+struct CounterThresholdSettingType
+{
+ string attributeName;
+ SeverityIndicatingThresholdType threshold;
+};
+
+```
+
+```
+/**
+```
+
+```
+The order is insignificant.
+```
+
+```
+*/
+```
+
+```
+typedef sequence CounterThresholdSetType;
+```
+
+```
+
+struct GaugeThresholdSettingType
+{
+ string attributeName;
+ SeverityIndicatingGaugeThresholdSetType threshold;
+};
+
+```
+
+```
+/**
+```
+
+```
+The order is insignificant.
+```
+
+```
+*/
+```
+
+```
+typedef sequence
+ GaugeThresholdSetType;
+
+/**
+This data structure represents all the CurrentData classes contained by a
+containing object through either direct or indirect containment.
+*/
+struct CDClassSelectionType
+{
+ MONameType containingObject;
+ ScopedNameSetType cdClassList;
+};
+
+typedef sequence CDClassSelectionSetType;
+```
+
+/\*\*
+
+## 5.4 Exceptions
+
+\*/
+
+/\*\*
+Exceptions and Constants for Conditional Package
+\*/
+
+```
+exception NOcounterThresholdListPackage {};
+
+exception NOdeleteNotificationPackage {};
+
+exception NOgaugeThresholdListPackage {};
+
+exception NOperiodSynchronizationPackage {};
+
+exception NOthresholdPackage {};
+
+const string counterThresholdListPackage =
+ "itut_q822d1::counterThresholdListPackage";
+const string deleteNotificationPackage =
+ "itut_q822d1::deleteNotificationPackage";
+const string gaugeThresholdListPackage =
+ "itut_q822d1::gaugeThresholdListPackage";
+const string periodSynchronizationPackage =
+ "itut_q822d1::periodSynchronizationPackage";
+const string thresholdPackage =
+ "itut_q822d1::thresholdPackage";
+```
+
+/\*\*
+Exceptions for Performance Management
+\*/
+
+/\*\*
+
+## 5.5 Interfaces – Fine-grained
+
+\*/
+
+/\*\*
+
+### 5.5.1 Scanner
+
+See 4.3.1 for behaviour.
+
+This interface contains the following CONDITIONAL PACKAGES.
+
+- periodSynchronizationPackage: present if configurable agent internal synchronization of repeating time periods is required.
+
+The Scanner interface is not instantiable.
+
+```
+*/
+valuetype ScannerValueType: itut_x780::ManagedObjectValueType
+{
+ public AdministrativeStateType administrativeState;
+ // GET-REPLACE
+ public OperationalStateType operationalState;
+ // GET
+ public TimePeriodType granularityPeriod;
+ // GET-REPLACE
+ public GeneralizedTimeType periodSynchronizationTime;
+ // conditional
+ // periodSynchronizationPackage
+ // GET-REPLACE
+}; // valuetype ScannerValueType
+
+interface Scanner: itut_x780::ManagedObject
+{
+ AdministrativeStateType administrativeStateGet ()
+ raises (itut_x780::ApplicationError);
+
+ void administrativeStateSet
+ (in AdministrativeStateType administrativeState)
+ raises (itut_x780::ApplicationError);
+
+ OperationalStateType operationalStateGet ()
+ raises (itut_x780::ApplicationError);
+
+ TimePeriodType granularityPeriodGet ()
+ raises (itut_x780::ApplicationError);
+
+ void granularityPeriodSet
+ (in TimePeriodType granularityPeriod)
+ raises (itut_x780::ApplicationError);
+
+ GeneralizedTimeType periodSynchronizationTimeGet ()
+ raises (itut_x780::ApplicationError,
+ NOperiodSynchronizationPackage);
+
+ void periodSynchronizationTimeSet
+ (in GeneralizedTimeType periodSyncTime)
+ raises (itut_x780::ApplicationError,
+ NOperiodSynchronizationPackage);
+
+ CONDITIONAL_NOTIFICATION(
+ itut_x780::Notifications, objectCreation,
+ createDeleteNotificationsPackage)
+ CONDITIONAL_NOTIFICATION(
+ itut_x780::Notifications, objectDeletion,
+ createDeleteNotificationsPackage)
+```
+
+```
+
+ CONDITIONAL_NOTIFICATION(
+ itut_x780::Notifications, attributeValueChange,
+ attributeValueChangeNotificationPackage)
+ CONDITIONAL_NOTIFICATION(
+ itut_x780::Notifications, stateChange,
+ stateChangeNotificationPackage)
+
+ }; // interface Scanner
+
+```
+
+```
+/**
+```
+
+### 5.5.2 CurrentData
+
+See 4.3.2.1 for behaviour.
+
+This interface contains the following CONDITIONAL PACKAGES.
+
+- thresholdPackage: present if a Quality of Service Alarm Notification is to be emitted for threshold crossing.
+- zeroSuppressionPackage: present if an instance supports it.
+
+The CurrentData interface is not instantiable.
+
+```
+*/
+```
+
+```
+/**
+```
+
+#### 5.5.2.1 CurrentDataValueType
+
+```
+*/
+```
+
+```
+
+valuetype CurrentDataValueType: ScannerValueType
+{
+ public boolean suspectIntervalFlag;
+ // GET REPLACE-WITH-DEFAULT
+ public TimeIntervalType elapsedTime;
+ // GET
+ public short historyRetention;
+ // Mandatory now (used to be conditional)
+ // GET-REPLACE
+ public MONameSetType thresholdDataInstanceList;
+ // conditional
+ // thresholdPackage
+ // GET-REPLACE ADD-REMOVE
+ public short numSuppressedIntervals;
+ // conditional
+ // zeroSuppressionPackage
+ // GET
+ public short maxSuppressedIntervals;
+ // conditional
+ // zeroSuppressionPackage
+ // GET-REPLACE
+}; // valuetype CurrentDataValueType
+
+```
+
+```
+/**
+```
+
+#### 5.5.2.2 HistoryDataValueType
+
+See 4.3.2.2 for behaviour.
+
+```
+*/
+```
+
+```
+
+valuetype HistoryDataValueType
+{
+ public GeneralizedTimeType periodEndTime;
+
+```
+
+```
+
+ // GET
+ public TimePeriodType granularityPeriod;
+ // GET
+ public boolean suspectIntervalFlag;
+ // GET
+ public short numSuppressedIntervals;
+ // GET
+ }; // valuetype HistoryDataValueType
+
+```
+
+/\*\*
+
+#### 5.5.2.3 HistoryDataIterator
+
+HistoryDataIterator is used for iteratively transferring a large chunk of history data.
+
+```
+
+ */
+ interface HistoryDataIterator
+ {
+ /**
+ This method is used to return the next howMany history data. howMany is the
+ maximum number of history data for which results should be returned in the first
+ batch; it must be non-zero. historyDataList is a sequence of history data
+ records.
+ The method will return true if there is data in out parameter, false otherwise.
+ */
+ boolean getNext
+ (in unsigned short howMany,
+ out HistoryDataSeqValueType historyDataList)
+ raises (itut_x780::ApplicationError);
+
+ /**
+ This method is used to destroy the iterator and release its resources. This must
+ be done by the application.
+ */
+ void destroy ();
+
+ }; // interface HistoryDataIterator
+
+```
+
+/\*\*
+
+#### 5.5.2.4 CurrentData
+
+```
+
+ */
+ interface CurrentData: Scanner
+ {
+ /**
+ Define default value for suspectIntervalFlag
+ */
+ const boolean suspectIntervalFlagDefault = FALSE;
+
+ /**
+ Define default value for maxSuppressedIntervals. The default value -1 means that
+ there is no limit on the number of consecutive suppressed intervals. On the other
+ hand, the maxSuppressedIntervals is effectively equal to infinity.
+ */
+ const short maxSuppressedIntervalsDefault = -1;
+
+ boolean suspectIntervalFlagGet ()
+ raises (itut_x780::ApplicationError);
+ }
+
+```
+
+```
+
+void suspectIntervalFlagDefaultSet
+ (in boolean suspectIntervalFlag)
+ raises (itut_x780::ApplicationError);
+
+TimeIntervalType elapsedTimeGet ()
+ raises (itut_x780::ApplicationError);
+
+short historyRetentionGet ()
+ raises (itut_x780::ApplicationError);
+
+void historyRetentionSet
+ (in short intervalNum)
+ raises (itut_x780::ApplicationError);
+
+MONameSetType thresholdDataInstanceListGet ()
+ raises (itut_x780::ApplicationError,
+ NOthresholdPackage);
+
+void thresholdDataInstanceListSet
+ (in MONameSetType dataInstanceList)
+ raises (itut_x780::ApplicationError,
+ NOthresholdPackage);
+
+void thresholdDataInstanceListAdd
+ (in MONameSetType dataInstanceList)
+ raises (itut_x780::ApplicationError,
+ NOthresholdPackage);
+
+void thresholdDataInstanceListRemove
+ (in MONameSetType dataInstanceList)
+ raises (itut_x780::ApplicationError,
+ NOthresholdPackage);
+
+boolean getMostRecent
+ (out HistoryDataValueType historyData)
+ raises (itut_x780::ApplicationError);
+
+HistoryDataSeqValueType getBetween
+ (in GeneralizedTimeType startTime,
+ in GeneralizedTimeType endTime,
+ in unsigned short howMany,
+ out HistoryDataIterator resultIterator)
+ raises (itut_x780::ApplicationError);
+
+/**
+ */
+short numSuppressedIntervalsGet ()
+ raises (itut_x780::ApplicationError);
+
+short maxSuppressedIntervalsGet ()
+ raises (itut_x780::ApplicationError);
+
+void maxSuppressedIntervalsSet
+ (in short maxSuppInterval)
+ raises (itut_x780::ApplicationError);
+
+CONDITIONAL_NOTIFICATION(
+ itut_x780::Notifications, qualityOfServiceAlarm,
+ NOthresholdPackage)
+
+}; // interface CurrentData
+
+/**
+ */
+
+```
+
+### 5.5.3 ThresholdData
+
+See 4.3.3 for behaviour.
+
+This interface contains the following CONDITIONAL PACKAGES.
+
+- counterThresholdListPackage: present if an instance supports it and the gaugeThresholdListPackage is not present.
+
+- gaugeThresholdListPackage: present if an instance supports it and the counterThresholdListPackage is not present
+
+```
+*/
+valuetype ThresholdDataValueType: itut_x780::ManagedObjectValueType
+{
+ public CounterThresholdSetType counterThresholdList;
+ // conditional
+ // counterThresholdListPackage
+ // GET-REPLACE ADD-REMOVE
+ public GaugeThresholdSetType gaugeThresholdList;
+ // conditional
+ // gaugeThresholdListPackage
+ // GET-REPLACE ADD-REMOVE
+}; // valuetype ThresholdDataValueType
+
+interface ThresholdData: itut_x780::ManagedObject
+{
+ CounterThresholdSetType counterThresholdListGet ()
+ raises (itut_x780::ApplicationError,
+ NOcounterThresholdListPackage);
+
+ void counterThresholdListSet
+ (in CounterThresholdSetType counterThresholdList)
+ raises (itut_x780::ApplicationError,
+ NOcounterThresholdListPackage);
+
+ void counterThresholdListAdd
+ (in CounterThresholdSetType counterThresholdList)
+ raises (itut_x780::ApplicationError,
+ NOcounterThresholdListPackage);
+
+ void counterThresholdListRemove
+ (in CounterThresholdSetType counterThresholdList)
+ raises (itut_x780::ApplicationError,
+ NOcounterThresholdListPackage);
+
+ GaugeThresholdSetType gaugeThresholdListGet ()
+ raises (itut_x780::ApplicationError,
+ NOgaugeThresholdListPackage);
+
+ void gaugeThresholdListSet
+ (in GaugeThresholdSetType gaugeThresholdList)
+ raises (itut_x780::ApplicationError,
+ NOgaugeThresholdListPackage);
+
+ void gaugeThresholdListAdd
+ (in GaugeThresholdSetType gaugeThresholdList)
+ raises (itut_x780::ApplicationError,
+ NOgaugeThresholdListPackage);
+
+ void gaugeThresholdListRemove
+ (in GaugeThresholdSetType gaugeThresholdList)
+ raises (itut_x780::ApplicationError,
+ NOgaugeThresholdListPackage);
+}
+```
+
+```
+
+ CONDITIONAL_NOTIFICATION(
+ itut_x780::Notifications, objectCreation,
+ createDeleteNotificationsPackage)
+ CONDITIONAL_NOTIFICATION(
+ itut_x780::Notifications, objectDeletion,
+ createDeleteNotificationsPackage)
+ CONDITIONAL_NOTIFICATION(
+ itut_x780::Notifications, attributeValueChange,
+ attributeValueChangeNotificationPackage)
+
+}; // interface ThresholdData
+
+interface ThresholdDataFactory: itut_x780::ManagedObjectFactory
+{
+ itut_x780::ManagedObject create
+ (in NameBindingType nameBinding,
+ in MONameType superior,
+ in string reqID, // auto naming if null
+ out MONameType name,
+ in IstringSetType packageNameList,
+ in CounterThresholdSetType counterThresholdList,
+ // conditional
+ // counterThresholdListPackage
+ // GET-REPLACE ADD-REMOVE
+ in GaugeThresholdSetType gaugeThresholdList)
+ // conditional
+ // gaugeThresholdListPackage
+ // GET-REPLACE ADD-REMOVE
+ raises (itut_x780::ApplicationError,
+ itut_x780::CreateError);
+
+}; // interface ThresholdDataFactory
+
+/**
+
+```
+
+### 5.5.4 HDFile (HistoryDataFile)
+
+See 4.3.4 for behaviour.
+
+This interface contains the following CONDITIONAL PACKAGES.
+
+- objectDeleteNotificationPackage: present if an instance supports it.
+\*/
+
+```
+
+valuetype HDFileValueType: itut_x780::ManagedObjectValueType
+{
+ public HDFileFormatType fileFormat;
+ // GET, SET-BY-CREATE
+ public URLType fileLocation;
+ // GET, SET-BY-CTEATE
+ public GeneralizedTimeType periodEndTime;
+ // GET, SET-BY-CREATE
+ public TimePeriodType fileRetentionDuration;
+ // GET, SET-BY-CREATE
+}; // valuetype HDFileValueType
+
+```
+
+```
+
+interface HDFile: itut_x780::ManagedObject
+{
+ HDFileFormatType fileFormatGet ()
+ raises (itut_x780::ApplicationError);
+
+```
+
+```
+
+ URLType fileLocationGet ()
+ raises (itut_x780::ApplicationError);
+
+ GeneralizedTimeType periodEndTimeGet ()
+ raises (itut_x780::ApplicationError);
+
+ TimePeriodType fileRetentionDurationGet ()
+ raises (itut_x780::ApplicationError);
+
+ MANDATORY_NOTIFICATION(
+ itut_x780::Notifications, objectCreation)
+ CONDITIONAL_NOTIFICATION(
+ itut_x780::Notifications, objectDeletion,
+ deleteNotificationPackage)
+
+}; // interface HDFile
+
+interface HDFileFactory: itut_x780::ManagedObjectFactory
+{
+ itut_x780::ManagedObject create
+ (in NameBindingType nameBinding,
+ in MONameType superior,
+ in string reqID, // auto naming if empty string
+ out MONameType name,
+ in HDFileFormatType fileFormat,
+ in URLType fileLocation,
+ in GeneralizedTimeType periodEndTime,
+ in TimePeriodType fileRetentionDuration)
+ raises (itut_x780::ApplicationError,
+ itut_x780::CreateError);
+
+}; // interface HDFileFactory
+
+/**
+```
+
+### 5.5.5 AbstractHDScanner (AbstractHistoryDataScanner)
+
+See 4.3.5 for behaviour.
+
+```
+
+*/
+valuetype AbstractHDScannerValueType: ScannerValueType
+{
+ public HDFileFormatSetType supportedFileFormatList;
+ // GET
+ public HDFileFormatType hdFileFormat;
+ // GET, SET
+ public TimePeriodType hdFileRetentionDuration;
+ // GET, SET
+ public TimePeriodType beginRelativeTime;
+ // GET, SET
+ public TimePeriodType endRelativeTime;
+ // GET, SET
+}; // valuetype HDScannerValueType
+
+interface AbstractHDScanner: Scanner
+{
+
+ HDFileFormatSetType supportedFileFormatListGet ()
+ raises (itut_x780::ApplicationError);
+
+/**
+The hdFileFormat must be one of the supported file formats.
+```
+
+```
+
+*/
+ HDFileFormatType hdFileFormatGet ()
+ raises (itut_x780::ApplicationError);
+
+ void hdFileFormatSet
+ (in HDFileFormatType hdFileFormat)
+ raises (itut_x780::ApplicationError);
+
+ TimePeriodType hdFileRetentionDurationGet ()
+ raises (itut_x780::ApplicationError);
+
+ void hdFileRetentionDurationSet
+ (in TimePeriodType hdFileRetentionDuration)
+ raises (itut_x780::ApplicationError);
+
+ TimePeriodType beginRelativeTimeGet ()
+ raises (itut_x780::ApplicationError);
+
+ void beginRelativeTimeSet
+ (in TimePeriodType beginRelativeTime)
+ raises (itut_x780::ApplicationError);
+
+ TimePeriodType endRelativeTimeGet ()
+ raises (itut_x780::ApplicationError);
+
+ void endRelativeTimeSet
+ (in TimePeriodType endRelativeTime)
+ raises (itut_x780::ApplicationError);
+
+ HistoryDataSeqValueType returnHDReport
+ (in unsigned short howMany,
+ out HistoryDataIterator resultIterator)
+ raises (itut_x780::ApplicationError);
+
+ void generateHDFileNow ()
+ raises (itut_x780::ApplicationError);
+
+}; // interface AbstractHDScanner
+
+/**
+
+
+
+### 5.5.6 ListHDScanner
+
+
+
+See 4.3.6 for behaviour.
+*/
+valuetype ListHDScannerValueType: AbstractHDScannerValueType
+{
+ public CurrentDataNameSetType cdInstanceList;
+ // GET, SET
+}; // valuetype ListHDScannerValueType
+
+interface ListHDScanner: AbstractHDScanner
+{
+ CurrentDataNameSetType cdInstanceListGet ()
+ raises (itut_x780::ApplicationError);
+
+ void cdInstanceListSet
+ (in CurrentDataNameSetType instanceList)
+ raises (itut_x780::ApplicationError);
+
+ void cdInstanceListAdd
+ (in CurrentDataNameSetType instanceList)
+
+```
+
+```
+
+ raises (itut_x780::ApplicationError);
+
+ void cdInstanceListRemove
+ (in CurrentDataNameSetType instanceList)
+ raises (itut_x780::ApplicationError);
+
+}; // interface ListHDScanner
+
+interface ListHDScannerFactory: itut_x780::ManagedObjectFactory
+{
+ itut_x780::ManagedObject create
+ (in NameBindingType nameBinding,
+ in MONameType superior,
+ in string reqID, // auto naming if empty string
+ out MONameType name,
+ in CurrentDataNameSetType cdInstanceList,
+ in HDFileFormatType fileFormat,
+ in TimePeriodType fileRetentionDuration,
+ in TimePeriodType beginRelativeTime,
+ in TimePeriodType endRelativeTime,
+ in AdministrativeStateType administrativeState,
+ in TimePeriodType granularityPeriod,
+ in GeneralizedTimeType periodSynchronizationTime)
+ // conditional
+ // periodSynchronizationPackage
+ raises (itut_x780::ApplicationError,
+ itut_x780::CreateError);
+
+}; // interface ListHDScannerFactory
+
+```
+
+### 5.5.7 ClassHDScanner
+
+See 4.3.7 for behaviour.
+
+```
+
+/**
+ *
+ */
+valuetype ClassHDScannerValueType: AbstractHDScannerValueType
+{
+ public CDClassSelectionSetType cdClassSelectionList;
+ // GET, SET
+}; // valuetype ClassHDScannerValueType
+
+interface ClassHDScanner: AbstractHDScanner
+{
+ CDClassSelectionSetType cdClassSelectionListGet ()
+ raises (itut_x780::ApplicationError);
+
+ void cdClassSelectionListSet
+ (in CDClassSelectionSetType classList)
+ raises (itut_x780::ApplicationError);
+
+ void cdClassSelectionListAdd
+ (in CDClassSelectionSetType classList)
+ raises (itut_x780::ApplicationError);
+
+ void cdClassSelectionListRemove
+ (in CDClassSelectionSetType classList)
+ raises (itut_x780::ApplicationError);
+
+}; // interface ClassHDScanner
+
+```
+
+```
+
+interface ClassHDScannerFactory: itut_x780::ManagedObjectFactory
+{
+ itut_x780::ManagedObject create
+ (in NameBindingType nameBinding,
+ in MONameType superior,
+ in string reqID, // auto naming if empty string
+ out MONameType name,
+ in CDClassSelectionSetType cdClassSelectionList,
+ in HDFileFormatType fileFormat,
+ in TimePeriodType fileRetentionDuration,
+ in TimePeriodType beginRelativeTime,
+ in TimePeriodType endRelativeTime,
+ in AdministrativeStateType administrativeState,
+ in TimePeriodType granularityPeriod,
+ in GeneralizedTimeType periodSynchronizationTime)
+ // conditional
+ // periodSynchronizationPackage
+ raises (itut_x780::ApplicationError,
+ itut_x780::CreateError);
+
+}; // interface ClassHDScannerFactory
+
+```
+
+/\*\*
+
+### 5.5.8 ScopedFilteredHDScanner
+
+See 4.3.8 for behaviour.
+
+\*/
+
+```
+
+valuetype ScopedFiltedHDScannerValueType: AbstractHDScannerValueType
+{
+ public MONameType base;
+ // GET, SET
+ public ScopeType scope;
+ // GET, SET
+ public FilterType filter;
+ // GET, SET
+ public LanguageType language;
+ // GET, SET
+}; // valuetype ScopedFiltedHDScannerValueType
+
+```
+
+```
+
+interface ScopedFiltedHDScanner: AbstractHDScanner
+{
+ MONameType baseGet ()
+ raises (itut_x780::ApplicationError);
+
+ void baseSet
+ (in MONameType base)
+ raises (itut_x780::ApplicationError);
+
+ ScopeType scopeGet ()
+ raises (itut_x780::ApplicationError);
+
+ void scopeSet
+ (in ScopeType scope)
+ raises (itut_x780::ApplicationError);
+
+ FilterType filterGet ()
+ raises (itut_x780::ApplicationError);
+
+ void filterSet
+ (in FilterType filter)
+
+```
+
+```
+
+ raises (itut_x780::ApplicationError);
+
+ LanguageType languageGet ()
+ raises (itut_x780::ApplicationError);
+
+ void languageSet
+ (in LanguageType language)
+ raises (itut_x780::ApplicationError);
+
+ }; // interface ScopedFiltedHDScanner
+
+ interface ScopedFiltedHDScannerFactory:
+ itut_x780::ManagedObjectFactory
+ {
+ itut_x780::ManagedObject create
+ (in NameBindingType nameBinding,
+ in MONameType superior,
+ in string reqID, // auto naming if empty string
+ out MONameType name,
+ in MONameType base,
+ in ScopeType scope,
+ in FilterType filter,
+ in LanguageType language,
+ in HDFileFormatType fileFormat,
+ in TimePeriodType fileRetentionDuration,
+ in TimePeriodType beginRelativeTime,
+ in TimePeriodType endRelativeTime,
+ in AdministrativeStateType administrativeState,
+ in TimePeriodType granularityPeriod,
+ in GeneralizedTimeType periodSynchronizationTime)
+ // conditional
+ // periodSynchronizationPackage
+ raises (itut_x780::ApplicationError,
+ itut_x780::CreateError);
+
+ }; // interface ScopedFiltedHDScannerFactory
+
+```
+
+/\*\*
+
+## 5.6 Interfaces – Facade
+
+The facade history data scanners are defined here as per ITU-T Rec. X.780.1. However the fine-grained history data scanners would be sufficient for facade implementation.
+
+\*/
+
+/\*\*
+
+### 5.6.1 Scanner\_F
+
+See 4.3.1 for behaviour.
+
+This interface contains the following CONDITIONAL PACKAGES.
+
+- periodSynchronizationPackage: present if configurable agent internal synchronization of repeating time periods is required.
+
+The Scanner interface is not instantiable.
+
+\*/
+
+```
+
+ interface Scanner_F: itut_x780::ManagedObject_F
+ {
+
+```
+
+```
+
+AdministrativeStateType administrativeStateGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+void administrativeStateSet
+ (in MONameType name,
+ in AdministrativeStateType administrativeState)
+ raises (itut_x780::ApplicationError);
+
+OperationalStateType operationalStateGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+TimePeriodType granularityPeriodGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+void granularityPeriodSet
+ (in MONameType name,
+ in TimePeriodType granularityPeriod)
+ raises (itut_x780::ApplicationError);
+
+GeneralizedTimeType periodSynchronizationTimeGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError,
+ NOperiodSynchronizationPackage);
+
+void periodSynchronizationTimeSet
+ (in MONameType name,
+ in GeneralizedTimeType periodSyncTime)
+ raises (itut_x780::ApplicationError,
+ NOperiodSynchronizationPackage);
+
+CONDITIONAL_NOTIFICATION(
+ itut_x780::Notifications, objectCreation,
+ createDeleteNotificationsPackage)
+CONDITIONAL_NOTIFICATION(
+ itut_x780::Notifications, objectDeletion,
+ createDeleteNotificationsPackage)
+CONDITIONAL_NOTIFICATION(
+ itut_x780::Notifications, attributeValueChange,
+ attributeValueChangeNotificationPackage)
+CONDITIONAL_NOTIFICATION(
+ itut_x780::Notifications, stateChange,
+ stateChangeNotificationPackage)
+
+}; // interface Scanner_F
+
+```
+
+/\*\*
+
+### 5.6.2 CurrentData\_F
+
+See 4.3.2.1 for behaviour.
+
+This interface contains the following CONDITIONAL PACKAGES.
+
+- thresholdPackage: present if a Quality of Service Alarm Notification is to be emitted for threshold crossing.
+- zeroSupressionPackage: present if an instance supports it.
+
+The CurrentData interface is not instantiable.
+
+\*/
+
+```
+
+interface CurrentData_F: Scanner_F
+{
+ /**
+ * Define default value for suspectIntervalFlag
+ */
+ const boolean suspectIntervalFlagDefault = FALSE;
+
+ /**
+ * Define default value for maxSuppressedIntervals. The default value -1 means that
+ * there is no limit on the number of consecutive suppressed intervals. On the other
+ * hand, the maxSuppressedIntervals is effectively equal to infinity.
+ */
+ const short maxSuppressedIntervalsDefault = -1;
+
+ boolean suspectIntervalFlagGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+ void suspectIntervalFlagDefaultSet
+ (in MONameType name,
+ in boolean suspectIntervalFlag)
+ raises (itut_x780::ApplicationError);
+
+ TimeIntervalType elapsedTimeGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+ short historyRetentionGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+ void historyRetentionSet
+ (in MONameType name,
+ in short intervalNum)
+ raises (itut_x780::ApplicationError);
+
+ MONameSetType thresholdDataInstanceListGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError,
+ NOthresholdPackage);
+
+ void thresholdDataInstanceListSet
+ (in MONameType name,
+ in MONameSetType dataInstanceList)
+ raises (itut_x780::ApplicationError,
+ NOthresholdPackage);
+
+ void thresholdDataInstanceListAdd
+ (in MONameType name,
+ in MONameSetType dataInstanceList)
+ raises (itut_x780::ApplicationError,
+ NOthresholdPackage);
+
+ void thresholdDataInstanceListRemove
+ (in MONameType name,
+ in MONameSetType dataInstanceList)
+ raises (itut_x780::ApplicationError,
+ NOthresholdPackage);
+
+ boolean getMostRecent
+ (in MONameType name,
+ out HistoryDataValueType historyData)
+ raises (itut_x780::ApplicationError);
+}
+
+```
+
+```
+
+HistoryDataSeqValueType getBetween
+ (in MONameType name,
+ in GeneralizedTimeType startTime,
+ in GeneralizedTimeType endTime,
+ in unsigned short howMany,
+ out HistoryDataIterator resultIterator)
+ raises (itut_x780::ApplicationError);
+
+short numSuppressedIntervalsGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+short maxSuppressedIntervalsGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+void maxSuppressedIntervalsSet
+ (in MONameType name,
+ in short maxSuppInterval)
+ raises (itut_x780::ApplicationError);
+
+CONDITIONAL_NOTIFICATION(
+ itut_x780::Notifications, qualityOfServiceAlarm,
+ NOthresholdPackage)
+
+}; // interface CurrentData_F
+
+/**
+
+```
+
+### 5.6.3 ThresholdData\_F
+
+See 4.3.3 for behaviour.
+
+This interface contains the following CONDITIONAL PACKAGES.
+
+- counterThresholdListPackage: present if an instance supports it and the gaugeThresholdListPackage is not present.
+- gaugeThresholdListPackage: present if an instance supports it and the counterThresholdListPackage is not present.
+
+```
+
+*/
+interface ThresholdData_F: itut_x780::ManagedObject_F
+{
+ CounterThresholdSetType counterThresholdListGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError,
+ NOcounterThresholdListPackage);
+
+ void counterThresholdListSet
+ (in MONameType name,
+ in CounterThresholdSetType counterThresholdList)
+ raises (itut_x780::ApplicationError,
+ NOcounterThresholdListPackage);
+
+ void counterThresholdListAdd
+ (in MONameType name,
+ in CounterThresholdSetType counterThresholdList)
+ raises (itut_x780::ApplicationError,
+ NOcounterThresholdListPackage);
+}
+
+```
+
+```
+
+void counterThresholdListRemove
+ (in MONameType name,
+ in CounterThresholdSetType counterThresholdList)
+ raises (itut_x780::ApplicationError,
+ NOcounterThresholdListPackage);
+
+GaugeThresholdSetType gaugeThresholdListGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError,
+ NOgaugeThresholdListPackage);
+
+void gaugeThresholdListSet
+ (in MONameType name,
+ in GaugeThresholdSetType gaugeThresholdList)
+ raises (itut_x780::ApplicationError,
+ NOgaugeThresholdListPackage);
+
+void gaugeThresholdListAdd
+ (in MONameType name,
+ in GaugeThresholdSetType gaugeThresholdList)
+ raises (itut_x780::ApplicationError,
+ NOgaugeThresholdListPackage);
+
+void gaugeThresholdListRemove
+ (in MONameType name,
+ in GaugeThresholdSetType gaugeThresholdList)
+ raises (itut_x780::ApplicationError,
+ NOgaugeThresholdListPackage);
+
+CONDITIONAL_NOTIFICATION(
+ itut_x780::Notifications, objectCreation,
+ createDeleteNotificationsPackage)
+CONDITIONAL_NOTIFICATION(
+ itut_x780::Notifications, objectDeletion,
+ createDeleteNotificationsPackage)
+CONDITIONAL_NOTIFICATION(
+ itut_x780::Notifications, attributeValueChange,
+ attributeValueChangeNotificationPackage)
+
+}; // interface ThresholdData_F
+
+/**
+
+```
+
+### 5.6.4 HDFile\_F (HistoryDataFile)
+
+See 4.3.4 for behaviour.
+
+This interface contains the following CONDITIONAL PACKAGES.
+
+- objectDeleteNotificationPackage: present if an instance supports it.
+\*/
+
+```
+
+interface HDFile_F: itut_x780::ManagedObject_F
+{
+ HDFileFormatType fileFormatGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+ URLType fileLocationGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+};
+
+```
+
+```
+
+ GeneralizedTimeType periodEndTimeGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+ TimePeriodType fileRetentionDurationGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+ MANDATORY_NOTIFICATION(
+ itut_x780::Notifications, objectCreation)
+ CONDITIONAL_NOTIFICATION(
+ itut_x780::Notifications, objectDeletion,
+ deleteNotificationPackage)
+
+}; // interface HDFile_F
+
+```
+
+/\*\*
+
+### 5.6.5 AbstractHDScanner\_F (AbstractHistoryDataScanner)
+
+See 4.3.5 for behaviour.
+
+\*/
+
+```
+
+interface AbstractHDScanner_F: Scanner_F
+{
+
+ HDFileFormatSetType supportedFileFormatListGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+ /**
+ The hdFileFormat must be one of supported file format.
+ */
+ HDFileFormatType hdFileFormatGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+ void hdFileFormatSet
+ (in MONameType name,
+ in HDFileFormatType hdFileFormat)
+ raises (itut_x780::ApplicationError);
+
+ TimePeriodType hdFileRetentionDurationGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+ void hdFileRetentionDurationSet
+ (in MONameType name,
+ in TimePeriodType hdFileRetentionDuration)
+ raises (itut_x780::ApplicationError);
+
+ TimePeriodType beginRelativeTimeGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+ void beginRelativeTimeSet
+ (in MONameType name,
+ in TimePeriodType beginRelativeTime)
+ raises (itut_x780::ApplicationError);
+
+ TimePeriodType endRelativeTimeGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+```
+
+```
+
+ void endRelativeTimeSet
+ (in MONameType name,
+ in TimePeriodType endRelativeTime)
+ raises (itut_x780::ApplicationError);
+
+ HistoryDataSeqValueType returnHDReport
+ (in MONameType name,
+ in unsigned short howMany,
+ out HistoryDataIterator resultIterator)
+ raises (itut_x780::ApplicationError);
+
+ void generateHDFileNow
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+}; // interface AbstractHDScanner_F
+
+```
+
+/\*\*
+
+### 5.6.6 ListHDScanner\_F
+
+See 4.3.6 for behaviour.
+
+\*/
+
+```
+
+interface ListHDScanner_F: AbstractHDScanner_F
+{
+ CurrentDataNameSetType cdInstanceListGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+ void cdInstanceListSet
+ (in MONameType name,
+ in CurrentDataNameSetType instanceList)
+ raises (itut_x780::ApplicationError);
+
+ void cdInstanceListAdd
+ (in MONameType name,
+ in CurrentDataNameSetType instanceList)
+ raises (itut_x780::ApplicationError);
+
+ void cdInstanceListRemove
+ (in MONameType name,
+ in CurrentDataNameSetType instanceList)
+ raises (itut_x780::ApplicationError);
+
+}; // interface ListHDScanner_F
+
+```
+
+/\*\*
+
+### 5.6.7 ClassHDScanner\_F
+
+See 4.3.7 for behaviour.
+
+\*/
+
+```
+
+interface ClassHDScanner_F: AbstractHDScanner_F
+{
+ CDClassSelectionSetType cdClassSelectionListGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+ void cdClassSelectionListSet
+ (in MONameType name,
+ in CDClassSelectionSetType classList)
+ raises (itut_x780::ApplicationError);
+
+```
+
+```
+
+ void cdClassSelectionListAdd
+ (in MONameType name,
+ in CDClassSelectionSetType classList)
+ raises (itut_x780::ApplicationError);
+
+ void cdClassSelectionListRemove
+ (in MONameType name,
+ in CDClassSelectionSetType classList)
+ raises (itut_x780::ApplicationError);
+
+}; // interface ClassHDScanner_F
+
+```
+
+/\*\*
+
+### 5.6.8 ScopedFilteredHDScanner\_F
+
+See 4.3.8 for behaviour.
+
+\*/
+
+```
+
+interface ScopedFilteredHDScanner_F: AbstractHDScanner_F
+{
+ MONameType baseGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+ void baseSet
+ (in MONameType name,
+ in MONameType base)
+ raises (itut_x780::ApplicationError);
+
+ ScopeType scopeGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+ void scopeSet
+ (in MONameType name,
+ in ScopeType scope)
+ raises (itut_x780::ApplicationError);
+
+ FilterType filterGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+ void filterSet
+ (in MONameType name,
+ in FilterType filter)
+ raises (itut_x780::ApplicationError);
+
+ LanguageType languageGet
+ (in MONameType name)
+ raises (itut_x780::ApplicationError);
+
+ void languageSet
+ (in MONameType name,
+ in LanguageType language)
+ raises (itut_x780::ApplicationError);
+
+}; // interface ScopedFilteredHDScanner_F
+
+```
+
+/\*\*
+
+## 5.7 Notifications
+
+No model specific notifications defined in this Recommendation.
+\*/
+
+/\*\*
+
+## 5.8 Name Binding
+
+\*/
+
+/\*\*
+
+The following module contains name-binding information.
+
+\*/
+
+```
+module NameBinding
+{
+```
+
+/\*\*
+
+### 5.8.1 ThresholdData
+
+This name binding is used to name the ThresholdData object to a Managed Element object.
+
+\*/
+
+```
+module ThresholdData_ManagedElement
+{
+ const string superiorClass =
+ "itut_m3120::ManagedElement";
+ const boolean superiorSubclassesAllowed = TRUE;
+ const string subordinateClass =
+ "itut_q822dl::ThresholdData";
+ const boolean subordinateSubclassesAllowed = TRUE;
+ const boolean managerCreatesAllowed = TRUE;
+ const DeletePolicyType deletePolicy =
+ itut_x780::deleteOnlyIfNoContainedObjects;
+ const string kind = "ThresholdData";
+}; // module ThresholdData_ManagedElement
+```
+
+/\*\*
+
+### 5.8.2 HDFile
+
+This name binding is used to name the HDFile object to an AbstractHDScanner object.
+
+\*/
+
+```
+module HDFile_AbstractHDScanner
+{
+ const string superiorClass =
+ "itut_q822dl::AbstractHDScanner";
+ const boolean superiorSubclassesAllowed = TRUE;
+ const string subordinateClass =
+ "itut_q822dl::HDFile";
+ const boolean subordinateSubclassesAllowed = TRUE;
+ const boolean managerCreatesAllowed = FALSE;
+ const DeletePolicyType deletePolicy =
+ itut_x780::deleteOnlyIfNoContainedObjects;
+ const string kind = "HDFile";
+```
+
+```
+}; // module HDFile_AbstractHDScanner
+```
+
+```
+/**
+```
+
+### 5.8.3 AbstractHDScanner
+
+This name binding is used to name the AbstractHDScanner object to a ManagedElement.
+
+```
+*/
+module AbstractHDScanner_ManagedElement
+{
+ const string superiorClass =
+ "itut_m3120::ManagedElement";
+ const boolean superiorSubclassesAllowed = TRUE;
+ const string subordinateClass =
+ "itut_q822d1::AbstractHDScanner";
+ const boolean subordinateSubclassesAllowed = TRUE;
+ const boolean managerCreatesAllowed = TRUE;
+ const DeletePolicyType deletePolicy =
+ itut_x780::deleteOnlyIfNoContainedObjects;
+ const string kind = "HDScanner";
+}; // module AbstractHDScanner_ManagedElement
+
+}; // module NameBinding
+```
+
+```
+/**
+```
+
+## 5.9 HDFileFormatConst
+
+This module contains constant values identifying history data file formats.
+
+```
+*/
+module HDFileFormatConst
+{
+ const string moduleName =
+ "itut_q822d1::HDFileFormatConst";
+
+ const short unknown = 0;
+
+ const short q822d1FileText = 1;
+
+ const short q822d1FileXML = 2;
+
+}; // HDFileFormatConst
+
+}; // module itut_q822d1
+```
+
+```
+#endif // _itut_q822_1_idl_
+```
+
+# ANNEX A
+
+## File Format
+
+This annex describes the format of a performance measurement data file, named q822d1FileText.
+
+### A.1 Text File Format BNF
+
+The BNF in this annex defines the format of performance measurement data file, named "q822d1FileText".
+
+```
+ := #file
+ #endfile
+
+ :=
+
+ :=
+
+ :=
+
+ :=
+
+ :=
+ |
+
+ := #node
+ #endnode
+
+ :=
+
+ :=
+ |
+
+ :=
+ |
+
+ :=
+ |
+ |
+
+ := #idalias
+
+ :=
+
+ :=
+
+ := #table #endtable
+
+ := #header
+ #endheader
+
+ :=
+
+ :=
+
+ :=
+ |
+
+ := #dataset
+ suspect
+ #enddataset
+
+ :=
+```
+
+```
+
+ :=
+
+ :=
+|
+
+ :=
+
+ :=
+|
+
+ := #period
+| #endperiod
+
+ :=
+
+ :=
+|
+
+ :=
+
+ := // can be aliased and prefixed
+
+ :=
+|
+
+ :=
+
+ :=
+
+ :=
+|
+
+ :=
+
+ :=
+|
+|
+|
+|
+|
+|
+
+ := : // field delimiter
+
+ := \
+
+ := '\n' // line delimiter
+
+ :=
+
+ :=
+
+ :=
+
+ :=
+
+ :=
+
+ :=
+
+ :=